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

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

CapabilityStatement: Directory capability [ITI-130-NL] for a Data Source actor

Official URL: http://minvws.github.io/generiekefuncties-docs/CapabilityStatement/nl-gf-directory-for-ITI-130-NL Version: 0.10.0
Active as of 2025-08-28 Computable Name:

ITI-130-NL; Dutch profile of the IHE ITI-130 endpoint

Raw OpenAPI-Swagger Definition file | Download

Language: en

Directory capability [ITI-130-NL] for a Data Source actor

  • Implementation Guide Version: 0.10.0
  • FHIR Version: 4.0.1
  • Supported Formats: application/fhir+xml, application/fhir+json
  • Published on: 2025-08-28
  • 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

ITI-130-NL; Dutch profile of the IHE ITI-130 endpoint

Summary of System-wide Interactions
  • SHALL support the transactioninteraction.

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 TypeProfileRSUCSearches_include_revincludeOperations
HealthcareServiceSupported Profiles
  NL Generic Functions HealthcareService Profile		YY
LocationSupported Profiles
  NL Generic Functions Location Profile		YY
OrganizationSupported Profiles
  NL Generic Functions Organization Profile		YY
EndpointSupported Profiles
  NL Generic Functions Endpoint Profile		YY
OrganizationAffiliationSupported Profiles
  NL Generic Functions OrganizationAffiliation Profile		YY
Provenance Y
Core FHIR Resource
HealthcareService
Reference Policy
Interaction summary
  • SHALL support create, update.

Supported Profiles

NL Generic Functions HealthcareService Profile

Documentation

.

Core FHIR Resource
Location
Reference Policy
Interaction summary
  • SHALL support create, update.

Supported Profiles

NL Generic Functions Location Profile

Documentation

.

Core FHIR Resource
Organization
Reference Policy
Interaction summary
  • SHALL support create, update.

Supported Profiles

NL Generic Functions Organization Profile

Documentation

.

Core FHIR Resource
Endpoint
Reference Policy
Interaction summary
  • SHALL support create, update.

Supported Profiles

NL Generic Functions Endpoint Profile

Documentation

.

Core FHIR Resource
OrganizationAffiliation
Reference Policy
Interaction summary
  • SHALL support create, update.

Supported Profiles

NL Generic Functions OrganizationAffiliation Profile

Documentation

.

Core FHIR Resource
Provenance
Reference Policy
Interaction summary
  • SHALL support create.

Documentation

A Data Source MAY submit a signed Provenance that references the stored resource version(s). When submitted, the LRZa Directory SHALL verify the signature against the relevant trust chain (e.g. an UZI/PKIo-certificate) and reject an invalid signature with an OperationOutcome. Provenance records are stored and synchronized to local replicas (ITI-90-NL/ITI-91-NL). The LRZa Directory SHALL NOT require a signature to accept a mutation.