FHIR Implementation Guide: GP care and Paramedical care 0.1.0-dev
|
|
This FHIR IG is currently under development and can not be considered stable and ready for use. |
1 Introduction
This is the implementation guide for the information standard GP Care and Paramedical care (Dutch: Huisartsenzorg en Paramedische Zorg). This standard is described in this functional specification and implemented here using HL7 FHIR R4. This implementation guide assumes that the reader is familiar with both the functional specification and the FHIR standard.
|
|
Currently this IG covers the use case "General practitioner refers to paramedic" and specifically just the referral and not the transfer of a medical record. As development moves on, more use cases will be added. |
Apart from this document, the guidelines as specified in general FHIR Implementation Guide apply.
2 Actors involved
| Actors | Systems | FHIR CapabilityStatements | |||
|---|---|---|---|---|---|
| Name | Description | Name | Description | Name | Description |
| General practitioner | The general practitioner who sends a referral message for a patient to a paramedic | Sending XIS | Healthcare information system of the sending organization | n/a | FHIR requirements for sending XIS |
| Paramedic | The paramedic that receives the referral message | Receiving XIS | Healthcare information system of the receiving organization | n/a | FHIR requirements for receiving XIS |
3 Workflow and message structure
3.1 Overview
The information standards contains various use cases that are not always isolated. For instance, when a general practitioner sends a referral to a paramedic, the paramedic might return an update about the patients treatment process to the general practitioner. A ServiceRequest resource is used to represent the referral in combination with a Task resource to track the request. In a later stage, more resource profiles will be added for the transfer of the medical record.
3.2 ServiceRequest
The requirements for the ServiceRequest resource in the context of this information standard are specified using the [n/a] profile. This profile SHALL be used in referral use cases.
3.3 Task
The requirements for the Task resource in the context of this information standard are specified using the [n/a] profile. This profile SHALL be used for the workflow.