Error parsing IP fragment: unable to parse character reference ' Conditions in https://www.whocc.no/use_of_atc_ddd/'' (last text = '
' at line 13 column 272
|
Type
|
Reference
|
Content
|
|
web
|
cp2-test.example.org
|
https://cp2-test.example.org/fhirr4
|
|
web
|
tel:+3131599991
|
+3131599991
|
|
web
|
cp2-test.example.org
|
https://cp2-test.example.org/dicom-wado-rs
|
|
web
|
auth.cp1-test.example.org
|
https://auth.cp1-test.example.org/.well-known/oauth-authorization-server
|
|
web
|
cp1-old.example.org
|
https://cp1-old.example.org/fhir
|
|
web
|
cp3-test.example.org
|
https://cp3-test.example.org/fhirr4
|
|
web
|
cp2-test.example.org
|
https://cp2-test.example.org/fhirstu3
|
|
web
|
cp1-test.example.org
|
https://cp1-test.example.org/fhir
|
|
web
|
cp1-test.example.org
|
https://cp1-test.example.org/fhirr4
|
|
web
|
cp3-test.example.org
|
https://cp3-test.example.org/fhirstu3
|
|
web
|
tel:+31301234567
|
+31301234567
|
|
web
|
tel:+31612345678
|
+31612345678
|
|
web
|
www.minvws.nl
|
IG © 2026+ Ministerie van Volksgezondheid, Welzijn en Sport
.
Package nl.generiekefuncties.fhir#26.0.0 based on FHIR 4.0.1
.
Generated
2026-10-30
Links: Table of Contents |
QA Report
|
|
web
|
www.omg.org
|
ServD
|
|
web
|
www.omg.org
|
ServD
|
|
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
|
www.generiekefuncties.nl
|
Note:
This page is based on version 1.0.0 of the Functional and Technical Design Documents of the Generic Function Addressing (Generieke Functie Adressering). The current and previous versions of this document are available at www.generiekefuncties.nl/adressering
.
|
|
img
|
raw.githubusercontent.com
|
|
|
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
|
www.generiekefuncties.nl
|
www.generiekefuncties.nl/adressering
|
|
web
|
www.generiekefuncties.nl
|
www.generiekefuncties.nl/lokalisatie
|
|
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
|
www.generiekefuncties.nl
|
Note:
This page is based on version 0.9.0 of the Functional and Technical Design Documents of the Generic Function Localization (Generieke Functie Lokalisatie). The current and previous versions of this document are available at www.generiekefuncties.nl/lokalisatie
.
|
|
web
|
github.com
|
The Pseudonym Registration Service (PRS) provides OPRF evaluations used by clients to derive recipient-scoped pseudonyms from patient identifiers using HKDF and OPRF protocols. See GF Pseudonymization
for the full specification and the reference implementation
.
|
|
web
|
eur-lex.europa.eu
|
The Localization Search Client's access token SHALL include care provider and practitioner details in the authorization_details
object (as required for EU-cross-border exchange by EHDS Implementing Act 2026/2099, Annex 1
).
|
|
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
|
www.rfc-editor.org
|
The client SHALL blind the 32-byte HKDF output with the Blind
function of RFC 9497
, OPRF mode ( modeOPRF
), with ciphersuite ristretto255-SHA512
. This yields two 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
|
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 1.0.0
Significant changes/Closed issues:
|
|
web
|
github.com
|
Source code
|
|
web
|
github.com
|
Compare this version to 0.9.0-ballot
Significant changes/Closed issues:
|
|
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
|
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:
|
