Cohort Selector Clinical Domain Agent Since 5.0

This document describes the configuration options available for managing cohort selection settings in the cohortSelector section of the project configuration file. These settings control how consent data is retrieved and filtered.

Example Configuration

The cohortSelector section allows different implementations to be used for selecting the transfer cohort, at the moment there is only one implementation available out-of-the-box: trustCenterAgent.

cohortSelector:
  trustCenterAgent:
    server:
      baseUrl: http://tc-agent:8080
      auth: [ ... ]
      ssl: [ ... ]
    domain: MII
    patientIdentifierSystem: "https://ths-greifswald.de/fhir/gics/identifiers/Pseudonym"
    # e.g.: https://simplifier.net/medizininformatikinitiative-modulconsent/2.16.840.1.113883.3.1937.777.24.5.3--20210423105554
    policySystem: "urn:oid:2.16.840.1.113883.3.1937.777.24.5.3" # MII CS Consent Policy
    policies:
    - 2.16.840.1.113883.3.1937.777.24.5.3.2    # IDAT erheben
    - 2.16.840.1.113883.3.1937.777.24.5.3.3    # IDAT speichern, verarbeiten
    - 2.16.840.1.113883.3.1937.777.24.5.3.6    # MDAT erheben
    - 2.16.840.1.113883.3.1937.777.24.5.3.7    # MDAT speichern, verarbeiten

Fields

trustCenterAgent Since 5.0

The TCA based implementation uses the connection to the trust center to select patient IDs for transfer.

server Since 5.0

• Description: Specifies connection settings for the Trust Center Agent server.
• Type: HttpClientConfig
• Example:

    server:
      baseUrl: http://custom-agent:9000
      auth: [ ... ]
      ssl: [ ... ]

domain Since 5.0

• Description: Defines the domain to search for consent, serving as a namespace for data segregation.
• Type: String
• Example:

    domain: ResearchDomain

• Important: This domain must already exist in gICS before FTSnext can use it. FTSnext cannot create or alter domains through the FHIR gateway.

patientIdentifierSystem Since 5.0

• Description: Filters patients based on their identifier system. Only patients with identifiers from this system will be included.
• Type: String
• Example:

    patientIdentifierSystem: "https://example.org/fhir/identifiers/Patient"

policySystem Since 5.0

• Description: Filters policies based on their system identifier. Only policies from this system will be considered valid.
• Type: String
• Example:

    policySystem: "urn:oid:2.16.840.1.113883.3.1937.777.24.5.3" # MII CS Consent Policy

policies Since 5.0

• Description: Specifies a list of required policies. Consent must explicitly include approval for all these policies to qualify.
• Type: Array of Strings
• Example:

    policies:
    - 2.16.840.1.113883.3.1937.777.24.5.3.2    # IDAT erheben

Notes

• The domain field should be chosen carefully to avoid overlapping data between namespaces.
• Ensure that domain is correctly configured in the trust center.
• The patientIdentifierSystem and policySystem fields must reference valid FHIR-based system URLs.
• When defining policies, ensure they align with the consent requirements of your organization.