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-90-NL] for Update Client actor

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

ITI-90-NL; Dutch profile of the IHE ITI mCSD ITI-90 endpoint. Note that this CapabilityStatement excludes nearly all search parameters. This search interaction SHOULD only be used to retrieve the latest state of all resources of a specific type. For the initial load the server SHALL page results: it SHALL include Bundle.link with relation next until all results are returned, enforcing a maximum page size (advertised by the server; value in the LRZa SLA).

Raw OpenAPI-Swagger Definition file | Download

Language: en

Directory capability [ITI-90-NL] for Update Client 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-90-NL; Dutch profile of the IHE ITI mCSD ITI-90 endpoint. Note that this CapabilityStatement excludes nearly all search parameters. This search interaction SHOULD only be used to retrieve the latest state of all resources of a specific type.

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

Supported Profiles

NL Generic Functions Organization Profile

Documentation

.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLidentifiertoken
 
Core FHIR Resource
Location
Reference Policy
Interaction summary
  • SHALL support search-type, read.

Supported Profiles

NL Generic Functions Location Profile

Documentation

.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLidentifiertoken
 
Core FHIR Resource
HealthcareService
Reference Policy
Interaction summary
  • SHALL support search-type, read.

Supported Profiles

NL Generic Functions HealthcareService Profile

Documentation

.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLidentifiertoken
 
Core FHIR Resource
Endpoint
Reference Policy
Interaction summary
  • SHALL support search-type, read.

Supported Profiles

NL Generic Functions Endpoint Profile

Documentation

.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLidentifiertoken
 
Core FHIR Resource
OrganizationAffiliation
Reference Policy
Interaction summary
  • SHALL support search-type, read.

Supported Profiles

NL Generic Functions OrganizationAffiliation Profile

Documentation

.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLidentifiertoken
 
Core FHIR Resource
Provenance
Reference Policy
Interaction summary
  • SHALL support search-type, read.

Documentation

Provenance records are only present when a Data Source has signed its mutations (see ITI-130-NL). When present, they are synchronized to the local replica during the initial load so that replica operators, auditors or supervisors that wish to verify the origin and integrity of accepted mutations. Signing is not mandatory; as a growth path it may become mandatory.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLidentifiertoken