ITI-130-NL; Dutch profile of the IHE ITI-130 endpoint

ITI-90-NL; Dutch profile of the IHE ITI mCSD ITI-90 endpoint. Note that this CapabilityStatement excludes nearly all search parameters. This search interaction SHOULD only be used to retrieve the latest state of all resources of a specific type.

ITI-91-NL; Dutch profile of the IHE ITI mCSD ITI-91 endpoint.

Dutch profile of the CapabilityStatement for a Localization Service using the List resource.

Logical model representing the KVK (Kamer van Koophandel) Basisprofiel API response structure as defined in the KVK API v1.4.0.

Logical model representing the KVK (Kamer van Koophandel) Vestigingsprofiel API response structure as defined in the KVK API v1.4.0.

The details of a device, such as a software application, used in the context of healthcare data exchange.

Endpoint profile for electronic services, aligned with IHE mCSD Endpoint constraints and extended with a value set constraint on payloadType and connectionType.

HealthcareService profile aligned with IHE mCSD HealthcareService constraints, with required value set bindings on type and specialty, support for ActivityDefinition/PlanDefinition references on type, and a required custodian-assigned identifier.

A List profile for registering the availability of patient data at healthcare organizations for localization services. This profile is used to indicate that certain patient data is available at a specific organization and can be accessed for localization purposes.

Location profile based on NL Core Location and aligned with IHE mCSD Location constraints, with a required custodian-assigned identifier.

Organization profile based on NL Core Healthcare Provider Organization and aligned with IHE mCSD Organization constraints, extended with CBS Standaard Bedrijfsindeling (SBI) typing.

OrganizationAffiliation profile aligned with IHE mCSD OrganizationAffiliation constraints, with a required custodian-assigned identifier and extended with a value set constraint on code and support for device identifiers in extensions.

Practitioner profile based on NL Core HealthProfessional Practitioner and aligned with IHE mCSD Practitioner constraints.

PractitionerRole profile based on NL Core HealthProfessional PractitionerRole and aligned with IHE mCSD PractitionerRole constraints, with a required custodian-assigned identifier.

A task to be performed, such as a referral or order, with additional details specific to FHIR STU3.

Data objects are frequently copied, federated, or accessed through intermediary platforms, which complicates provenance tracking, authenticity verification, and long-term traceability to the original source. To preserve provenance and avoid uncontrolled duplication, each original object SHALL be assigned an identifier by its original custodian (the accountable source). The custodian-assigned identifier uniquely identifies the resource and enables resolution to the originating organization when copies are stored in other systems. This pattern is used throughout this IG, including NL-GF-Organization and NL-GF-HealthcareService, and in example resources such as Organization (department), Condition, and Task.

Data objects are identified by an identifier that was assigned by the original custodian. The custodian is 'The entity that is accountable for maintaining a true an accurate copy of the original record'. I.e. this custodian is responsible for the 'single source of truth' for this data object. The 'custodian-assigned-identifier' is the unambiguous and persistent identifier for both the data object and the custodian.

Identifier for pseudonymized Dutch citizen service numbers (BSN).

The healthcare service where the task is performed.

The location where the task is performed.

A reference to an endpoint associated with this device.

An identifier for a device, such as a software application.

The organization responsible for the localization record, identified by URA number.

ActivityDefinitions or PlanDefinitions to specify the codeable concepts in HealthcareService.type.

The data categories defined in the AORTA code system.

Authorization types supported by NL Generic Functions.

Authorization and endpoint connection type codes supported by NL Generic Functions.

The data exchange capabilities supported

The Organization Types supported by the NL Generic Functions.

Data categories (a.k.a. zorgcontext) that map to FHIR resource types containing patient-related clinical or personal health information.

The Service Types supported by the NL Generic Functions.

Local code system for data categories in AORTA.

Local code system for authorization and security protocol flavors used on endpoints in NL Generic Functions. Inspired by endpoint-connection-type style coding.

Local code system for authorization types used in NL Generic Functions for managing authorization and access control

Local code system for data categories in NL Generic Functions.

Standaard Bedrijfsindeling (SBI) 2025 codes. Based on the Dutch SBI 2025 classification system, which is used to classify business activities in the Netherlands. The codes and descriptions are derived from the official SBI 2025 documentation provided by the Dutch government.

This identifier system represents KvK identifiers.

This identifier system represents KvK vestigingsnummers.

This Patient identifier is specific for the NVI and represents a pseudonymized BSN.

StructureMap die een KVK Basisprofiel API response transformeert naar een FHIR Organization resource.

StructureMap die een KVK Vestigingsprofiel API response transformeert naar een FHIR Location resource.

Concept map defining the equivalence between AORTA (Architecture for Organizing Trusted and Reliable Access) data categories and NL Generic Functions (NL-GF) data categories. This mapping enables interoperability between systems using the AORTA terminology and those conforming to the NL-GF framework for healthcare data exchange in the Netherlands.

Example: Authorization: Organization 1 authorizes PharmaPartners

Example: Authorization: Organization 2 authorizes Nedap

Example: Authorization: Organization 3 authorizes Gerimedica

This bundle contains all personal health information for Patient Jaantje Merkens in Organization 1

Example instance of the NlGfLocalizationList profile. It expresses an Organization with identifier (URA) 22222222 having a Medication request of a patient with a pseudonymised identifier (BSN)

Example: Gerimedica Device for Organization 3

Example: LRZa - Organization 1 - Organization

Example: LRZa - Organization 2 - Organization

Example: LRZa - Organization 3 - Organization

Example: Nedap Device for Organization 2

Request from Organization 2 for nursing care

Example: Organization 1 - Endpoint

Example: Organization 1 - PractitionerRole Harry Arts

Example: Organization 2 - Endpoint DICOM-WADO-RS

Example: Organization 2 - Endpoint FHIR R4

Example: Organization 2 - Endpoint FHIR STU3

Example: Organization 2 - HealthcareService Geriatrie

Example: Organization 2 - HealthcareService Interne Geneeskunde

Example: Organization 2 - HealthcareService Neurochirurgie

Example: Organization 2 - HealthcareService Orthopedie

Example consultation healthcare service named Polikliniek 't Vaatje at Organization 2.

Example: Organization 2 - HealthcareService Urologie

Example: Organization 2 - PractitionerRole Cardioloog Caroline van Dijk at Organization 2

Task created by Organization 2 to fulfill the ServiceRequest for nursing care at Nursing department at Organization 3

Example: Organization 3 - Endpoint FHIR R4

Example: Organization 3 - Endpoint FHIR STU3

Example: Organization 3 - HealthcareService Geriatrie

Example: Organization 3 - HealthcareService Verpleging

Example: Organization 3 - Location Main Building

Example location Verpleeghuis Weltevree managed by the nursing department of Organization 3.

Nursing department at Organization 3

Example: Organization 3 - PractitionerRole Klinisch Geriater John Doe

Patient Jaantje Merkens in EHR of Organization 2

Example: PharmaPartners Device for Organization 1

Example practitioner for Organization 2

Example practitioner for Organization 1

Example practitioner for Organization 3

Example: Software Vendor - Gerimedica

Example: Software Vendor - Nedap

Example: Software Vendor - PharmaPartners