Prerequisites

FTSnext requires access to gICS, gPAS and a redis compatible key-value store e.g. Valkey.

Furthermore, gPAS needs three preset domains. One for the mappings:

• patient ID to pseudonyms (PID -> sPID)
• resource IDs to salt values for hashing (RID -> salt)
• patient ID to date shift seed value (PID -> date shift seed)

As the keys are namespaced, it is possible to use one domain for all mappings.

Please see here for further explanation.

Prerequisites

The Trust Center Agent is configured to work with gICS for consent management and gPAS for pseudonym management and a redis compatible key-value store e.g. Valkey.

Important: Pre-configured domains required

You must ensure that any domains referenced in your FTSnext configuration (such as in cohortSelector and deidentificator settings) are already created and properly configured in the respective backend systems:

• The domain referenced in cohortSelector.trustCenterAgent.domain must exist in your consent management system
• The domains referenced in deidentificator.deidentifhir.trustCenterAgent.domains must exist in your pseudonym management system for:
  • pseudonym - For patient ID pseudonymization
  • salt - For resource ID salting
  • dateShift - For date shifting seed values

Note for gPAS implementations: In gPAS, you can use a single domain for all three pseudonymization functions (pseudonym, salt, and dateShift). The keys are namespaced internally by FTSnext, so one domain can serve all three purposes if desired.

Please see here for further explanation on how these domains are used in the deidentification process.