Netherlands - Generic Functions for data exchange Implementation Guide
0.3.0 - ci-build Netherlands

Netherlands - Generic Functions for data exchange Implementation Guide, published by Stichting Nuts. This guide is not an authorized publication; it is the continuous build for version 0.3.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/nuts-foundation/nl-generic-functions-ig/ and changes regularly. See the Directory of published versions

## CodeSystem: NL GF Data exchange capabilities (Experimental)

Official URL: http://nuts-foundation.github.io/nl-generic-functions-ig/CodeSystem/nl-gf-data-exchange-capabilities | Version: 0.3.0
Active as of 2026-01-28 | Computable Name: NlGfDataExchangeCapabilitiesCS

Local code system for NL Generic Functions.

This Code system is referenced in the content logical definition of the following value sets:

- NlGfDataExchangeCapabilitiesVS

This code system `http://nuts-foundation.github.io/nl-generic-functions-ig/CodeSystem/nl-gf-data-exchange-capabilities` defines the following codes:

Code | Display
http://nuts-foundation.github.io/nl-generic-functions-ig/CapabilityStatement/nl-gf-admin-directory-update-client | Care Services Directory for Update Client
http://nuts-foundation.github.io/nl-generic-functions-ig/CapabilityStatement/nl-gf-query-directory-query-client | Care Services Directory for Query Client
http://nuts-foundation.github.io/nl-generic-functions-ig/CapabilityStatement/nl-gf-query-directory-query-client-reads | Care Services Directory for Query Client for only Read operations
eOverdracht-notification | Transfer of Care - eOverdracht Notification
Twiin-TA-notification | Twiin - TA Notification
Nuts-OAuth | Nuts OAuth endpoint
http://nictiz.nl/fhir/CapabilityStatement/eOverdracht-servercapabilities | Transfer of Care - eOverdracht Server
http://nictiz.nl/fhir/CapabilityStatement/bgz2017-servercapabilities | BGZ Server
http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.RetrieveServe | Minimal requirements for a server to fulfill the 'Serve medication data' transaction (system role: MP-MGB).
http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationData.SendReceive | Minimal requirements for a server to fulfill the 'Receive medication data' transaction (system role: MP-MGO).
http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.RetrieveServe | Minimal requirements for a server to fulfill the 'Serve medication overview' transaction (system role: MP-MOB).
http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationOverview.SendReceive | Minimal requirements for a server to fulfill the 'Receive medication overview' transaction (system role: MP-MOO).
http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescription | Minimal requirements for a server to fulfill the 'Receive medication prescription' transaction (system role: MP-VOO).
http://nictiz.nl/fhir/CapabilityStatement/mp-MedicationPrescriptionProcessing | Minimal requirements for a server to fulfill the 'Receive medication prescription processing' transaction (system role: MP-VAO).
http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalDispenseRequest | Minimal requirements for a server to fulfill the 'Receive proposal dispense request' transaction (system role: MP-VVO).
http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalDispenseRequest | Minimal requirements for a server to fulfill the 'Receive reply proposal dispense request' transaction (system role: MP-VVS).
http://nictiz.nl/fhir/CapabilityStatement/mp-ProposalMedicationAgreement | Minimal requirements for a server to fulfill the 'Receive proposal medication agreement' transaction (system role: MP-VMO).
http://nictiz.nl/fhir/CapabilityStatement/mp-ReplyProposalMedicationAgreement | Minimal requirements for a server to fulfill the 'Receive reply proposal medication agreement' transaction (system role: MP-VMS).