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@examplesoft.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 cp1-test.example.org address : https://cp1-test.example.org/fhir
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 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-07-15
Links: Table of Contents | QA Report
web snomed.info    408467006
web snomed.info    394577000
web snomed.info    394578005
web snomed.info    421661004
web snomed.info    408462000
web snomed.info    394579002
web snomed.info    394804000
web snomed.info    394580004
web snomed.info    394803006
web snomed.info    408480009
web snomed.info    408454008
web snomed.info    394809005
web snomed.info    394592004
web snomed.info    394600006
web snomed.info    394601005
web snomed.info    394581000
web snomed.info    408478003
web snomed.info    394812008
web snomed.info    408444009
web snomed.info    394582007
web snomed.info    408475000
web snomed.info    410005002
web snomed.info    394583002
web snomed.info    419772000
web snomed.info    394584008
web snomed.info    408443003
web snomed.info    394802001
web snomed.info    394915009
web snomed.info    394814009
web snomed.info    394808002
web snomed.info    394811001
web snomed.info    408446006
web snomed.info    394586005
web snomed.info    394916005
web snomed.info    408472002
web snomed.info    394597005
web snomed.info    394598000
web snomed.info    394807007
web snomed.info    419192003
web snomed.info    408468001
web snomed.info    394593009
web snomed.info    394813003
web snomed.info    410001006
web snomed.info    394589003
web snomed.info    394591006
web snomed.info    394599008
web snomed.info    394649004
web snomed.info    408470005
web snomed.info    394585009
web snomed.info    394821009
web snomed.info    422191005
web snomed.info    394594003
web snomed.info    416304004
web snomed.info    418960008
web snomed.info    394882004
web snomed.info    394806003
web snomed.info    394588006
web snomed.info    408459003
web snomed.info    394607009
web snomed.info    419610006
web snomed.info    418058008
web snomed.info    420208008
web snomed.info    418652005
web snomed.info    418535003
web snomed.info    418862001
web snomed.info    419365004
web snomed.info    418002000
web snomed.info    419983000
web snomed.info    419170002
web snomed.info    419472004
web snomed.info    394539006
web snomed.info    420112009
web snomed.info    409968004
web snomed.info    394587001
web snomed.info    394913002
web snomed.info    408440000
web snomed.info    418112009
web snomed.info    419815003
web snomed.info    394914008
web snomed.info    408455009
web snomed.info    394602003
web snomed.info    408447002
web snomed.info    394810000
web snomed.info    408450004
web snomed.info    408476004
web snomed.info    408469009
web snomed.info    408466002
web snomed.info    408471009
web snomed.info    408464004
web snomed.info    408441001
web snomed.info    408465003
web snomed.info    394605001
web snomed.info    394608004
web snomed.info    408461007
web snomed.info    408460008
web snomed.info    394606000
web snomed.info    408449004
web snomed.info    418018006
web snomed.info    394604002
web snomed.info    394609007
web snomed.info    408474001
web snomed.info    394610002
web snomed.info    394611003
web snomed.info    408477008
web snomed.info    394801008
web snomed.info    408463005
web snomed.info    419321007
web snomed.info    394576009
web snomed.info    394590007
web snomed.info    409967009
web snomed.info    408448007
web snomed.info    419043006
web snomed.info    394612005
web snomed.info    394733009
web snomed.info    394732004
web github.com The directory therefore does not carry per-Endpoint terms of use, authentication or security policy. Transport security for publishing to the LRZa Directory is covered under Security ; the broader authentication and security requirements for invoking endpoints are addressed in the dedicated security and authentication tracks (see epics security (#854) and authentication means (#855) ).
web github.com The directory therefore does not carry per-Endpoint terms of use, authentication or security policy. Transport security for publishing to the LRZa Directory is covered under Security ; the broader authentication and security requirements for invoking endpoints are addressed in the dedicated security and authentication tracks (see epics security (#854) and authentication means (#855) ).
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 Versioning of information standards / implementation guides per Endpoint (e.g. which zib release or IG package) is to be elaborated in alignment with the national choice of standards ( epic standaardenkeuze ); the NDH fhir-ig extension is a candidate mechanism.
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 .
web www.rfc-editor.org Canonicalization: http://hl7.org/fhir/canonicalization/json#static — the FHIR static JSON canonicalization. This recursively removes Resource.meta and every narrative ( .text ) element, and then applies the JSON Canonicalization Scheme (JCS), RFC 8785 . Removing meta makes the signature robust as the resource moves from the LRZa Directory to replicas (where meta.versionId , meta.lastUpdated and tags differ).
web www.rfc-editor.org Canonicalize the stripped resource with the JSON Canonicalization Scheme (RFC 8785) . Object keys are sorted, insignificant whitespace is removed, and strings/numbers are serialized deterministically. You can reproduce this with any JCS implementation, e.g. the online JSON Canonicalizer . The canonical form (a single line, shown wrapped here) is:
web toolsbase.dev Canonicalize the stripped resource with the JSON Canonicalization Scheme (RFC 8785) . Object keys are sorted, insignificant whitespace is removed, and strings/numbers are serialized deterministically. You can reproduce this with any JCS implementation, e.g. the online JSON Canonicalizer . The canonical form (a single line, shown wrapped here) is:

Internal Images

../assets/images/nld.svg
../assets/images/nld.svg
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