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

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

## CapabilityStatement: Localization Service - Local Metadata Register

Official URL: http://nuts-foundation.github.io/nl-generic-functions-ig/CapabilityStatement/nl-gf-localization-repository-lmr | Version: 0.2.0
Active as of 2025-08-28 | Computable Name:

Dutch profile of the CapabilityStatement for a Localization Service - Local Metadata Register

Raw OpenAPI-Swagger Definition file | Download

## Localization Service - Local Metadata Register

- Implementation Guide Version: 0.2.0
- FHIR Version: 4.0.1
- Supported Formats: `application/fhir+xml`, `application/fhir+json`
- Published on: 2025-08-28
- Published by: Stichting Nuts

> 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 Type | Profile | R | S | U | C | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Patient |  | Y |  |  |  |  |  |  |

#### Resource Conformance: SHALL Patient

Core FHIR Resource
Patient
Reference Policy
Interaction summary

- SHALL support `read`.

Documentation

> HTTP Method HEAD SHALL be supported to check for the existence of -and access to- a Patient resource, without returning the actual resource.