Netherlands - Generic Functions for data exchange Implementation Guide
0.2.0-ballot - ci-build

Netherlands - Generic Functions for data exchange Implementation Guide, published by Ministerie van Volksgezondheid, Welzijn en Sport. This guide is not an authorized publication; it is the continuous build for version 0.2.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/minvws/generiekefuncties-docs/ and changes regularly. See the Directory of published versions

## Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

### Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

Directory capability [ITI-130-NL] for a Data Source actor | ITI-130-NL; Dutch profile of the IHE ITI-130 endpoint
Directory capability [ITI-90-NL] for a Query Client actor | ITI-90-NL; Dutch profile of the IHE ITI mCSD ITI-90 endpoint. Note that this CapabilityStatement excludes all search parameters. This search interaction SHOULD only be used to retrieve the latest state of all resources of a specific type.
Directory capability [ITI-91-NL] for an Update Client actor | ITI-91-NL; Dutch profile of the IHE ITI mCSD ITI-91 endpoint.
Localization Service (List) | Dutch profile of the CapabilityStatement for a Localization Service using the List resource.

### Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

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

### Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

NL Generic Functions Device Profile | The details of a device, such as a software application, used in the context of healthcare data exchange.
NL Generic Functions Endpoint Profile | Endpoint profile for electronic services, aligned with IHE mCSD Endpoint constraints and extended with a value set constraint on payloadType and connectionType.
NL Generic Functions HealthcareService Profile | 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.
NL Generic Functions Localization List Profile | 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.
NL Generic Functions Location Profile | Location profile based on NL Core Location and aligned with IHE mCSD Location constraints, with a required custodian-assigned identifier.
NL Generic Functions Organization Profile | Organization profile based on NL Core Healthcare Provider Organization and aligned with IHE mCSD Organization constraints, extended with CBS Standaard Bedrijfsindeling (SBI) typing.
NL Generic Functions OrganizationAffiliation Profile | 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.
NL Generic Functions Practitioner Profile | Practitioner profile based on NL Core HealthProfessional Practitioner and aligned with IHE mCSD Practitioner constraints.
NL Generic Functions PractitionerRole Profile | PractitionerRole profile based on NL Core HealthProfessional PractitionerRole and aligned with IHE mCSD PractitionerRole constraints, with a required custodian-assigned identifier.
NL Generic Functions Task Profile for FHIR STU3 | A task to be performed, such as a referral or order, with additional details specific to FHIR STU3.

### Structures: Data Type Profiles

These define constraints on FHIR data types for systems conforming to this implementation guide.

Custodian Assigned Identifier | 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.
Custodian Assigned URN Identifier | 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.
NVI Identifier | Identifier for pseudonymized Dutch citizen service numbers (BSN).

### Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

HealthcareService for Task in STU3 | The healthcare service where the task is performed.
Location for Task in STU3 | The location where the task is performed.
NL Generic Functions Device Endpoint | A reference to an endpoint associated with this device.
NL Generic Functions Device Identifier | An identifier for a device, such as a software application.
NL Generic Functions Localization Custodian | The organization responsible for the localization record, identified by URA number.
Supported ActivityDefinitions and PlanDefinitions by HealthcareServices | ActivityDefinitions or PlanDefinitions to specify the codeable concepts in HealthcareService.type.

### Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

AORTA Data Categories ValueSet | The data categories defined in the AORTA code system.
NL GF Authorization Type ValueSet | Authorization types supported by NL Generic Functions.
NL GF Connection Types ValueSet | Authorization and endpoint connection type codes supported by NL Generic Functions.
NL GF Data exchange capabilities | The data exchange capabilities supported
NL GF Organization Types ValueSet | The Organization Types supported by the NL Generic Functions.
NL GF Patient Information Data Categories ValueSet | Data categories (a.k.a. zorgcontext) that map to FHIR resource types containing patient-related clinical or personal health information.
NL GF Service Types ValueSet | The Service Types supported by the NL Generic Functions.

### Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

AORTA Data Categories CodeSystem | Local code system for data categories in AORTA.
NL GF Authorization Server CodeSystem | Local code system for authorization and security protocol flavors used on endpoints in NL Generic Functions. Inspired by endpoint-connection-type style coding.
NL GF Authorization Type CodeSystem | Local code system for authorization types used in NL Generic Functions for managing authorization and access control
NL GF Data Categories CodeSystem | Local code system for data categories in NL Generic Functions.
NL GF Standaard Bedrijfsindeling 2025 | 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.
NL GF WLZ Zorgprofielen CodeSystem | Local code system for NL Generic Functions WLZ Zorgprofielen.

### Terminology: Naming Systems

These define identifier and/or code system identities used by systems conforming to this implementation guide.

kvk-nummer | This identifier system represents KvK identifiers.
kvk-vestigingsnummer | This identifier system represents KvK vestigingsnummers.
nvi-identifier | This Patient identifier is specific for the NVI and represents a pseudonymized BSN.

### Terminology: Structure Maps

These define transformations to convert between data structures used by systems conforming to this implementation guide.

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

### Terminology: Concept Maps

These define transformations to convert between codes by systems conforming with this implementation guide.

AORTA to NL GF Data Categories | 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: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Authorization: Organization 1 authorizes PharmaPartners | Example: Authorization: Organization 1 authorizes PharmaPartners
Authorization: Organization 2 authorizes Nedap | Example: Authorization: Organization 2 authorizes Nedap
Authorization: Organization 3 authorizes Gerimedica | Example: Authorization: Organization 3 authorizes Gerimedica
Bundle of personal health information in HIS of Organization 1 | This bundle contains all personal health information for Patient Jaantje Merkens in Organization 1
Condition hypercalciëmie |
Example NL Generic Functions Localization List | 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)
Gerimedica Device for Organization 3 | Example: Gerimedica Device for Organization 3
LRZa - Organization 1 - Organization | Example: LRZa - Organization 1 - Organization
LRZa - Organization 2 - Organization | Example: LRZa - Organization 2 - Organization
LRZa - Organization 3 - Organization | Example: LRZa - Organization 3 - Organization
Nedap Device for Organization 2 | Example: Nedap Device for Organization 2
Organisation 2 - ServiceRequest Nursing | Request from Organization 2 for nursing care
Organization 1 - Endpoint | Example: Organization 1 - Endpoint
Organization 1 - PractitionerRole Harry Arts | Example: Organization 1 - PractitionerRole Harry Arts
Organization 2 - Endpoint DICOM-WADO-RS | Example: Organization 2 - Endpoint DICOM-WADO-RS
Organization 2 - Endpoint FHIR R4 | Example: Organization 2 - Endpoint FHIR R4
Organization 2 - Endpoint FHIR STU3 | Example: Organization 2 - Endpoint FHIR STU3
Organization 2 - HealthcareService Geriatrie | Example: Organization 2 - HealthcareService Geriatrie
Organization 2 - HealthcareService Interne Geneeskunde | Example: Organization 2 - HealthcareService Interne Geneeskunde
Organization 2 - HealthcareService Neurochirurgie | Example: Organization 2 - HealthcareService Neurochirurgie
Organization 2 - HealthcareService Orthopedie | Example: Organization 2 - HealthcareService Orthopedie
Organization 2 - HealthcareService Polikliniek 't Vaatje | Example consultation healthcare service named Polikliniek 't Vaatje at Organization 2.
Organization 2 - HealthcareService Urologie | Example: Organization 2 - HealthcareService Urologie
Organization 2 - PractitionerRole Cardioloog Caroline van Dijk at Organization 2 | Example: Organization 2 - PractitionerRole Cardioloog Caroline van Dijk at Organization 2
Organization 2 - Task for ServiceRequest Nursing | Task created by Organization 2 to fulfill the ServiceRequest for nursing care at Nursing department at Organization 3
Organization 3 - Endpoint FHIR R4 | Example: Organization 3 - Endpoint FHIR R4
Organization 3 - Endpoint FHIR STU3 | Example: Organization 3 - Endpoint FHIR STU3
Organization 3 - HealthcareService Geriatrie | Example: Organization 3 - HealthcareService Geriatrie
Organization 3 - HealthcareService Verpleging | Example: Organization 3 - HealthcareService Verpleging
Organization 3 - Location Main Building | Example: Organization 3 - Location Main Building
Organization 3 - Location Verpleeghuis Weltevree | Example location Verpleeghuis Weltevree managed by the nursing department of Organization 3.
Organization 3 - Organization Nursing department | Nursing department at Organization 3
Organization 3 - PractitionerRole Klinisch Geriater John Doe | Example: Organization 3 - PractitionerRole Klinisch Geriater John Doe
Patient Jaantje Merkens | Patient Jaantje Merkens in EHR of Organization 2
PharmaPartners Device for Organization 1 | Example: PharmaPartners Device for Organization 1
Practitioner Caroline van Dijk at Organization 2 | Example practitioner for Organization 2
Practitioner Harry Arts at Organization 1 | Example practitioner for Organization 1
Practitioner John Doe at Organization 3 | Example practitioner for Organization 3
Software Vendor - Gerimedica | Example: Software Vendor - Gerimedica
Software Vendor - Nedap | Example: Software Vendor - Nedap
Software Vendor - PharmaPartners | Example: Software Vendor - PharmaPartners