Netherlands - Generic Functions for data exchange Implementation Guide
0.2.0 - ci-build
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
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| Administration Directory for Administration Client |
Dutch profile of the CapabilityStatement for Administration Directory Actor that should be able to work with an Administration Client |
| Administration Directory for Update Client |
Dutch profile of the CapabilityStatement for Administration Directory Actor that should be able to work with an Update Client. |
| Query Directory for Query Client |
Dutch profile of the CapabilityStatement for Query Directory Actor that should be able to work with an Query Client. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| NL Generic Functions CareTeam Profile for Patient Care Team |
A care team for a (single)patient with multiple care providers and/or care givers. |
| NL Generic Functions Endpoint Profile |
The technical details of an endpoint that can be used for electronic services, such as for web services providing access to FHIR resources. |
| NL Generic Functions HealthcareService Profile |
The technical details of a healthcare service that can be used in referrals, requests and orders |
| NL Generic Functions Location Profile |
Physical location details for healthcare services, organizations, and practitioners. |
| NL Generic Functions Organization Profile |
The organizational hierarchy and details for healthcare organizations. |
| NL Generic Functions OrganizationAffiliation Profile |
The details of an affiliation/relationship between two organizations, such as a healthcare provider and a software vendor. |
| NL Generic Functions Practitioner Profile |
The details of a healthcare practitioner, such as a doctor or nurse, who is directly or indirectly involved in the provisioning of healthcare. |
| NL Generic Functions PractitionerRole Profile |
The details of a healthcare practitioner's role within an organization. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Replaced By Endpoint |
Points to a new (updated) Endpoint. This can be used if this endpoint.address is (partially) replaced by a new one |
| Supported ActivityDefinitions and PlanDefinitions by HealthcareServices |
ActivityDefinitions or PlanDefinitions to specify the codeable concepts in HealthcareService.type. |
These define sets of codes used by systems conforming to this implementation guide.
| NL GF Payload Types |
The payload types supported by the NL Generic Functions. |
These define new code systems used by systems conforming to this implementation guide.
| NL GF Code System |
Local code system for NL Generic Functions. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Patient1 |