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
Release Notes
Version: current
- Implementation Guide
- Source code
- Compare version current to 1.0.0
Significant changes/Closed issues:
- Localization; localization records (NVI-pseudonyms) no longer contain a data-category code.
- Localization; data users search with a search context (zoekcontext) containing custodian characteristics, and the NVI only returns relevant custodians with an allow Authorization Decision (HEAD request on the custodian's FHIR API). Localization-Patients contain a custodian-assigned patient identifier.
- Care Services; added LRZa-managed elements, listing the Organization and Location elements and codes copied from the KvK and Dezi-register (including the Organization and Location created from a KvK vestiging to which a URA number is linked); the LRZa Directory refuses mutations of these elements by Data Sources. Documented the resources of the ITI-130-NL CapabilityStatement accordingly.
- Care Services; renamed the data category property
fhir-resourcetype-params to path-query-param: the relative path(s) and query parameters under the base URL in Endpoint.address at which a payload is offered. An authorization server Endpoint (connectionType from the NL-GF Authorization Server CodeSystem) points to the metadata endpoint of the authorization server and has payloadType none.
- Care Services; added the optional
HealthcareService.coverageArea, with example coverage-area Locations (provinces, cities and postal-code areas). A register/structure for coverage-area Locations is on the roadmap.
- Care Services;
Endpoint.connectionType is now primarily bound (extensible) to the NL-GF Connection Types value set, instead of through an additional binding, so codes from the NL-GF Authorization Server CodeSystem (e.g. oauth-nuts) no longer cause a binding warning against the NL-GF-Endpoint profile.
Version: 1.0.0
- Implementation Guide
- Source code
- Compare this version to 0.9.0-ballot
Significant changes/Closed issues:
- Pseudonymisation; added the pseudonymisation specification, including the requirement to use JSON Canonicalization Scheme (JCS) for PRS input.
- Care Services; clarified Endpoint lifecycle, period-based transitions and selection, and added machine-readable FHIR version guidance.
- Care Services; added synchronization requirements for paging, concurrency, retention and error handling, and expanded Endpoint management and directory support.
- Care Services; added Chamber of Commerce (KvK) data transformation guidance and support for publishing notification Endpoints.
- Localization; removed Device and used the OAuth client ID as the source.
- Authorization; added resource signing requirements and support for deletes.
- Terminology and interoperability; added subscription as a data category, a code system for care questions, and aligned the guide with EHDS.
Version: 0.9.0-ballot
- Implementation Guide
- Source code
- Compare this version to v0.1.0
Significant changes/Closed issues:
- Care-services; Simplified architecture and synchronization between directories.
- Care-services; Support for Endpoint-management for all organizations that own/operate endpoints (not just the service providers that supply an mCSD-Directory); added OrganizationAffiliations-profile and Device-profile
- Care-services & Localization; updated codesystem/valueset 'data categories' for (Care-services) Endpoint.payloadType and (Localization) List.code (a.k.a. 'zorgcontext'). 'Oauth'-endpoints are specified by connectionType (not PayloadType)
- Care-services; Renamed transactions and CapabilityStatements to, e.g., ITI-91-NL to reflect Generic Function Care Service Directory is the Dutch implementation of the IHE mCSD implementation Guide
- Care-services; Added structuremaps for Chamber-of-commerce (KvK) data transformation to FHIR Organization and Location resourcetypes
Version: v0.1.0