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

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.2.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

NamingSystem: fhir-resource-url

Official URL: http://nuts-foundation.github.io/nl-generic-functions-ig/NamingSystem/fhir-resource-url Version: 0.2.0
Active as of 2025-11-05 Computable Name: FHIR resource URL

This identifier represents an URI and URL that is SHOULD resolve/redirect to a FHIR resource for a long term (10+ years); just like 'permalinks' or 'persistent URLs' are used in scientific literature.

Only authoritative sources, i.e. the (legal) custodian/data holder should assign these URLs.

The custodian is responsible for forwarding/redirecting the URL-host/domain to a specific software system or platform, ensuring long term persistence of the identifier or (external) reference that's pointing to this resource.

Summary

Defining URLhttp://nuts-foundation.github.io/nl-generic-functions-ig/NamingSystem/fhir-resource-url
Version0.2.0
NameFHIR resource URL
Statusactive
Definition

This identifier represents an URI and URL that is SHOULD resolve/redirect to a FHIR resource for a long term (10+ years); just like 'permalinks' or 'persistent URLs' are used in scientific literature.

Only authoritative sources, i.e. the (legal) custodian/data holder should assign these URLs.

The custodian is responsible for forwarding/redirecting the URL-host/domain to a specific software system or platform, ensuring long term persistence of the identifier or (external) reference that's pointing to this resource.

PublisherStichting Nuts

Identifiers

TypeValuePreferredComment
URIhttp://fhir.nl/fhir/NamingSystem/url/fhirtrueThe client system may use the Accept header to request a specific FHIR version, e.g. `Accept: application/fhir+json; fhirVersion=4.0`. See ['Managing Multiple FHIR Versions'](http://hl7.org/fhir/R4/versioning.html#mt-version) for more information. However, a specific FHIR version may not be supported for the intended +10 years, a server MAY ignore this header. If no version is specified, the server returns the default version.