Rijksoverheid Ministerie van Volksgezondheid,
Welzijn en Sport

Generic Functions for data exchange - Implementation Guide
26.0.0 - trial-use Netherlands flag

Generic Functions for data exchange - Implementation Guide - Local Development build (v26.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

CapabilityStatement: Localization Service (Patient)

Official URL: http://fhir.generiekefuncties.nl/CapabilityStatement/nl-gf-localization-repository-patient Version: 26.0.0
Active as of 2026-10-08 Computable Name:

Dutch requirements for a Localization Service that registers and searches localization records as Patient resources.

Raw OpenAPI-Swagger Definition file | Download

Language: en

Localization Service (Patient)

  • Implementation Guide Version: 26.0.0
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+json
  • Published on: 2026-10-08
  • Published by: Ministerie van Volksgezondheid, Welzijn en Sport

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

FHIR RESTful Capabilities

Mode: server

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)
Resource TypeProfileRSUCDSearches_include_revincludeOperations
PatientSupported Profiles
  NL Generic Functions Localization Patient Profile		YYYidentifier, organization, _source
Core FHIR Resource
Patient
Reference Policy
Interaction summary
  • SHALL support delete
    create

    SHALL support conditional create with If-None-Exist: identifier=[custodian-assigned identifier]&_source=[client URI], so a registering client cannot create duplicate registrations.

    search-type

    SHALL support data-user search using POST [base]/Patient/_search (application/x-www-form-urlencoded). This search SHALL include the NVI patient identifier and MAY combine it with managing-organization filters. SHALL support the standard chained searches organization:identifier, organization.type, organization.endpoint.payload-type, and organization._has:HealthcareService:organization:service-type; the NVI resolves managing-organization identifiers against its LRZa replica. SHALL return only matching Patient projections for which the Authorization Decision is allow, marked with the SUBSETTED tag and omitting all Patient.identifier values and meta.source. These projections SHALL NOT be used to update registrations. An authorized registering client MAY search its registrations by _source for maintenance; those results are distinct from data-user search results.

Supported Profiles

NL Generic Functions Localization Patient Profile

Documentation

A Patient resource represents one patient at one custodian, registered by one client. Registration and maintenance use direct Patient REST interactions; transaction Bundles SHALL NOT be used.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLidentifiertoken

The NVI patient pseudonym. SHALL support the NVI identifier system. A registering client MAY also search by the custodian-assigned identifier, combined with _source, for record maintenance and conditional create.

SHALLorganizationreference

SHALL support filtering on the managing Organization using its :identifier modifier and chained type, endpoint.payload-type, and _has:HealthcareService:organization:service-type parameters. SHALL also accept the equivalent type-qualified form organization.endpoint:Endpoint.payload-type. The Organization identifier is resolved against the LRZa replica.

SHALL_sourceuri

Search by the registering OAuth client URI in meta.source for record maintenance.