...
For example 'ANOGPCode' could be transform input varchar(5) values into anonymous values composed of 3 digits and 2 characters with a suffix of _G.
Anonymisation occurs at ColumnInfo level during data load. Each ANOTable points to a corresponding table on an ANO server in which mappings are persisted. This server should be part of your normal backup strategy.
...
CatalogueItems can be tied to the underlying database via ExtractionInformation . This means that you can have multiple extraction transforms from the same underlying ColumnInfo e.g. PatientDateOfBirth / PatientYearOfBirth (each with different governance categories).
...
Describes in a single line of SELECT SQL. This can be either the fully qualified name or a transform upon an underlying ColumnInfo. Adding an ExtractionInformation to a CatalogueItem makes it extractable in a linkage Project.
...
Describes a relationship between 3 ColumnInfos in which 2 are from a lookup table (e.g. z_drugName), these are a primary key (e.g. DrugCode) and a description (e.g. HumanReadableDrugName). And a third ColumnInfo from a different table (e.g. Prescribing) which is a foreign key (e.g. DrugPrescribed).
...