Dutch profile of the CapabilityStatement for Administration Directory Actor that should be able to work with an Administration Client

Dutch profile of the CapabilityStatement for Administration Directory Actor that should be able to work with an Update Client.

Dutch profile of the CapabilityStatement for a Localization Service.

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

Dutch profile of the CapabilityStatement for Query Directory Actor that should be able to work with an Query Client.

Dutch profile of the CapabilityStatement for Query Directory Actor that should be able to work with an Query Client for only Read operations.

Sub-Task created by the Placer to request cancellation of a Coordination Task that has reached 'in-progress'. Until then the Placer may cancel directly by setting the Coordination Task status to 'cancelled'. The Fulfiller accepts or rejects the CancellationRequest Task; on acceptance the Placer sets the Coordination Task to 'cancelled'.

Per-case Task hosted at the Placer that tracks the lifecycle of one Notified Pull order. Derived from the COW Coordination Task (identifier 1..*, businessStatus, code, focus on one of six order types are inherited). Task.for references the Patient at the Placer; Task.for.identifier carries the BSN once the Fulfiller may know it (per Fulfiller, per phase, as the use case defines).

Broad, long-lived Subscription from a Placer to a Fulfiller for Notified Pull. One Subscription covers all Coordination Tasks for a single use-case topic between the two partners. Creation of the Subscription (in-band or out-of-band) is use-case defined; the Placer MUST check that a Subscription exists for the Fulfiller before notifying.

The technical details of an endpoint that can be used for electronic services, such as for web services providing access to FHIR resources.

The technical details of a healthcare service that can be used in referrals, requests and orders

A DocumentReference profile for registering the availability of patient data at healthcare organizations for localization services. This profile is used to indicate that certain patient data is available at a specific organization and can be accessed for localization purposes.

Physical location details for healthcare services, organizations, and practitioners.

The organizational hierarchy and details for healthcare organizations.

The organizational hierarchy and details for healthcare organizations.

The details of an affiliation/relationship between two organizations, such as a healthcare provider and a software vendor.

The details of a healthcare practitioner, such as a doctor or nurse, who is directly or indirectly involved in the provisioning of healthcare.

The details of a healthcare practitioner's role within an organization.

A task to be performed, such as a referral or order, with additional details specific to FHIR STU3.

The healthcare service where the task is performed.

The location where the task is performed.

ActivityDefinitions or PlanDefinitions to specify the codeable concepts in HealthcareService.type.

The data exchange capabilities supported by the NL Generic Functions.

The WLZ Zorgprofielen supported by the NL Generic Functions.

Business-status codes used by this profile that the COW business-status value set does not define. COW's workflow state overview uses selected without defining it.

Local code system for NL Generic Functions.

Local code system for NL Generic Functions WLZ Zorgprofielen.

This Patient identifier represents a pseudonymized BSN.

Nictiz-hosted canonical dataset definition for BgZ. Referenced from a referral's ServiceRequest via instantiatesCanonical. Shown as a stub; the production version enumerates ~30 queries.

This bundle contains all care services for the Organization 3 Administration Directory example

This bundle contains all care services for the Organization 2 Administration Directory example

This bundle contains all care services for the Organization 1 Administration Directory example

This bundle contains all care services for the LRZa Administration Directory example

This bundle contains all care services from each Administration Directory for the Query Directory example

This bundle contains all personal health information for Patient Jaantje Merkens in Organization 3

This bundle contains all personal health information for Patient Jaantje Merkens in Organization 2

This bundle contains all personal health information for Patient Jaantje Merkens in Organization 1

Example instance of the NlGfLocalizationDocumentReference profile.

Request from Organization 2 for nursing care

Task created by Organization 2 to fulfill the ServiceRequest for nursing care at Nursing department at Organization 3

Nursing department at Organization 3

Nursing department at Organization 3

Patient Jaantje Merkens in EHR of Organization 2

Per-order workflow Task at the Placer. Task.for.identifier carries the BSN (the Placer chose to disclose it at creation); Task.input carries the trigger Observation and one supplemental query in addition to the BgZ dataset.

The Request resource describing what is ordered: a patient referral. instantiatesCanonical points at the BgZ dataset PlanDefinition. Per-order additions are on the Coordination Task.

Subscription to receive notifications of Task-instance-id's where Care provider 33333333 is the (proposed) owner.

Nictiz-hosted canonical dataset definition for eOverdracht. Shown as a stub.

Coordination Task offering the transfer to Fulfiller A. Correlated with the task offered to Fulfiller B through the shared Task.focus.

Parallel Coordination Task offering the same ServiceRequest to Fulfiller B. Same Task.focus as candidate A. The Placer will select the first to accept, cancelling the other with statusReason 'not selected'.

The transfer-of-care order. performer is intentionally absent: during solicitation the candidates are known via the Coordination Tasks (Task.owner), not via the ServiceRequest. performer MAY be set once a candidate is selected.