Unattributed Code Systems

Copyright Fragment

This fragment is not visible to the reader

This publication includes IP covered under the following statements.

Copyright and Registered Trademark Uses

External References

Type Reference Content
web tel:+3131599991 contact : +3131599991 , info@nedap.example.org
web cp2-test.example.org address : https://cp2-test.example.org/fhirr4
web cp2-test.example.org address : https://cp2-test.example.org/dicom-wado-rs
web cp1-old.example.org address : https://cp1-old.example.org/fhir
web tel:+3131599991 contact : +3131599991 , info@example.org
web cp3-test.example.org address : https://cp3-test.example.org/fhirr4
web cp2-test.example.org address : https://cp2-test.example.org/fhirstu3
web tel:+3131599991 contact : +3131599991 , info@cp1.example.org
web cp1-test.example.org address : https://cp1-test.example.org/fhirr4
web cp3-test.example.org address : https://cp3-test.example.org/fhirstu3
web tel:+31301234567 telecom : +31301234567 , info@organization3.nl
web tel:+3131599991 telecom : +3131599991 , info@cp1.example.org
web tel:+31301234567 telecom : +31301234567 , info@cp2.example.org
web tel:+31612345678 +31612345678
web tel:+31301234568 telecom : +31301234568 , john.doe@cp3.example.org , https://matrix.to/#doctorno:cp3.example.org
web matrix.to telecom : +31301234568 , john.doe@cp3.example.org , https://matrix.to/#doctorno:cp3.example.org
web github.com 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.10.0 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
web www.minvws.nl IG © 2026+ Ministerie van Volksgezondheid, Welzijn en Sport . Package hl7.fhir.nl.gf#0.10.0 based on FHIR 4.0.1 . Generated 2026-06-24
Links: Table of Contents | QA Report
web github.com A Data Source actor SHALL use mTLS for transport layer security. Qualified certificates from Qualified Trusted Service Providers (like PKIoverheid) should be trusted. ( GF-Adressering, ADR#178 ). The LRZa-Directory SHALL only support creation/updates of OrganizationAffiliations by Care Providers, not by the parties that are being authorized (the .participatingOrganization ).
web github.com Open issues and Architectural Decision Records (ADRs) can be found in the GitHub repository
web minvws.github.io Implementation Guide
web github.com Source code
web github.com Compare version current to 0.9.0-ballot
web github.com Source code
web github.com Compare this version to v0.1.0

Significant changes/Closed issues:
web github.com Source code
web www.rfc-editor.org The NL Generic Functions IG uses the normative keywords SHALL , SHALL NOT , SHOULD , SHOULD NOT and MAY as defined in RFC 2119 and the IHE conformance conventions . In short: SHALL is an absolute requirement, SHALL NOT an absolute prohibition, SHOULD / SHOULD NOT a recommendation that may be deviated from with the implications understood and weighed, and MAY is truly optional. Consistent with IHE, this guide uses SHALL rather than "MUST". Keywords carry this meaning only when written in upper case; the same words in lower case are descriptive, not normative.
web profiles.ihe.net The NL Generic Functions IG uses the normative keywords SHALL , SHALL NOT , SHOULD , SHOULD NOT and MAY as defined in RFC 2119 and the IHE conformance conventions . In short: SHALL is an absolute requirement, SHALL NOT an absolute prohibition, SHOULD / SHOULD NOT a recommendation that may be deviated from with the implications understood and weighed, and MAY is truly optional. Consistent with IHE, this guide uses SHALL rather than "MUST". Keywords carry this meaning only when written in upper case; the same words in lower case are descriptive, not normative.
web profiles.ihe.net GF-Localization is based on the IHE MHD profile and follows the choices made by the MinvWS Localization working group, see GF-Lokalisatie, ADR's . This guide specifies the choices made. Most impactful/striking choice are:
web github.com GF-Localization is based on the IHE MHD profile and follows the choices made by the MinvWS Localization working group, see GF-Lokalisatie, ADR's . This guide specifies the choices made. Most impactful/striking choice are:
web profiles.ihe.net using IHE MHD profile to publish and find Localization records (transactions ITI-65 and ITI-66 ). As a pseudonimization service is used, the FHIR profiles and transactions are compatible with the IHE MHD profile, but not directly compliant.
web profiles.ihe.net using IHE MHD profile to publish and find Localization records (transactions ITI-65 and ITI-66 ). As a pseudonimization service is used, the FHIR profiles and transactions are compatible with the IHE MHD profile, but not directly compliant.
web profiles.ihe.net using IHE MHD profile to publish and find Localization records (transactions ITI-65 and ITI-66 ). As a pseudonimization service is used, the FHIR profiles and transactions are compatible with the IHE MHD profile, but not directly compliant.
web github.com For more detail on the topology of GF-Localization, see GF-Lokalisatie, ADR-2 . Each component, data model, and transaction will be discussed in more detail.
web github.com For detailed OPRF integration requirements, see GF Pseudonymisation and the reference implementation .
web github.com Within GF-Localization the NL-gf-localization-List profile is used to register, search, and validate localization records ( NL-GF-IG, ADR#10 ). This data model basically states "Care provider X has data of type Y for Patient Z" . It contains the following elements:
web www.rfc-editor.org OPRF + HKDF. Pseudonyms are derived using HKDF with SHA-256 ( RFC 5869 ) and blinded using an OPRF protocol. The PRS only ever sees blinded values.
web github.com A full reference flow including the call to the PRS is available in the gfmodules-nationale-verwijsindex-registratie-service repository .

Internal Images

careservices-datamodel.png
careservices-datamodel.png
careservices-overview-transactions.png
careservices-overview-transactions.png
localization-overview-transactions.png
localization-overview-transactions.png
tree-filter.png
tree-filter.png