Vdraft/FHIR GPCare ParamedicalCare: verschil tussen versies
Regel 47: | Regel 47: | ||
==ServiceRequest== | ==ServiceRequest== | ||
A ServiceRequest resource is used to represent a (request for) referral. 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. | A ServiceRequest resource is used to represent a (request for) referral. 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. | ||
+ | |||
+ | To indicate that the ServiceRequest is a resource that has to be acted upon by the receiver, the {{term|actionable}} tag is used. [https://hl7.org/fhir/r4/resource.html#tag Tags] are {{datatype|Coding}} elements present in {{fhir|Resource.meta.tag}} used for workflow management. | ||
=Use cases= | =Use cases= |
Versie van 1 aug 2022 14:38
|
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.
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 user of a HIS | HIS | General practitioner information system | n/a | n/a |
Paramedic | The user of a PARIS | PARIS | Paramedic information system | n/a | n/a |
3 Workflow and message structure
3.1 Overview
The use cases described in this information standard are limited in sense of workflow: events are handled on a per use case basis where the sender does not explicitly requests a response (e.g. a status update). Future insights might require the addition of more workflow and it is conceivable that the FHIR Task resource will be used to fulfill that. At this point in time, the ServiceRequest resource is sufficient for the use cases. In a later stage, more resource profiles will be added for the transfer of the medical record.
3.2 ServiceRequest
A ServiceRequest resource is used to represent a (request for) referral. 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.
To indicate that the ServiceRequest is a resource that has to be acted upon by the receiver, the actionable tag is used. Tags are Coding elements present in Resource.meta.tag
used for workflow management.
4 Use cases
|
Currently this IG only covers the use case #Use_case:_Referral_from_general_practitioner_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. |
4.1 Use case: Referral from general practitioner to paramedic
This is the technical counterpart of use case 2.5 "Huisarts verwijst naar paramedicus" as described in the functional design.
4.1.1 Introduction
4.1.2 Sequence diagrams
Normal flow | Cancel referral |
---|---|