|
Label: Nieuwe doorverwijzing |
| (27 tussenliggende versies door 2 gebruikers niet weergegeven) |
| Regel 1: |
Regel 1: |
| − | {{Vdraft/InformationBox|This FHIR IG is currently under development and can not be considered stable and ready for use.}}
| + | #REDIRECT [[hg:V1_FHIR_ELZ]] |
| − | __NOINDEX__
| |
| − | __NUMBEREDHEADINGS__
| |
| − | {{DISPLAYTITLE:FHIR Implementation Guide: GP care and Paramedical care 0.1.0-dev}}
| |
| − | | |
| − | <div class="toclimit-3">__TOC__</div>
| |
| − | | |
| − | =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 [[Ontwerp_Huisartsenzorg|this functional specification]] and implemented here using [https://www.hl7.org/fhir/R4/ 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 [[FHIR:V1.0_FHIR_IG_R4|general FHIR Implementation Guide]] apply.
| |
| − | | |
| − | =Workflow and message structure=
| |
| − | | |
| − | ==Overview==
| |
| − | The use cases described in this IG 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 more workflow and it is conceivable that the FHIR Task resource will be used to fulfill that. At this point in time, the ServiceRequest and Composition resources are sufficient for the use cases described in this IG. In a later stage, more (mostly zib based) resource profiles will be added for the transfer of the medical record.
| |
| − | | |
| − | ==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 [https://simplifier.net/nictiz-r4-gpcare-paramedicalcare/hgreferralservicerequest hg-ReferralServiceRequest] profile. This profile SHALL be used in referral use cases.
| |
| − | | |
| − | Each referral SHALL be captured by a dedicated ServiceRequest. When a referral is sent to multiple parties, each party receives it's own unique ServiceRequest. Revoking referrals after a certain period of time based on whether action is taken or not is out of scope of this information standard.
| |
| − | | |
| − | ===Actionable tag===
| |
| − | 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. When a ServiceRequest is created to send a referral, sending systems SHALL use {{fhir|meta.tag}} with {{fhir|.system}} = {{term|http://terminology.hl7.org/CodeSystem/common-tags}} and {{fhir|.code}} = {{term|actionable}}.
| |
| − | | |
| − | It is up to systems to determine how and when the transactions using the {{term|actionable}} tag are handled from a functional perspective. Systems may store the resource including the {{term|actionable}} tag or remove it either upon storing or when the request is acted upon. However, systems SHALL make sure the tag is removed when serving or sending the resource as part of an informative transaction.
| |
| − | | |
| − | ==Composition==
| |
| − | | |
| − | =Use cases=
| |
| − | {{Vdraft/InformationBoxSmall|Currently this IG only covers the [[#Use_case:_Referral_from_general_practitioner_to_paramedic]] and specifically just the referral and not the transfer of relevant medical record entries. As development moves on, more use cases will be added.}}
| |
| − | | |
| − | ==Use case: Referral from general practitioner to paramedic==
| |
| − | This is the technical counterpart of [[Ontwerp_Huisartsenzorg#Usecase:_Huisarts_verwijst_naar_paramedicus|use case 2.5 "Huisarts verwijst naar paramedicus"]] as described in the functional design.
| |
| − | | |
| − | ===Introduction===
| |
| − | | |
| − | ===Actors involved===
| |
| − | {| class="wikitable"
| |
| − | ! colspan="2" | Actors
| |
| − | ! colspan="2" | Systems
| |
| − | ! colspan="2" | 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
| |
| − | |}
| |
| − | | |
| − | ===Sequence diagrams===
| |
| − | {| class="wikitable"
| |
| − | !Normal flow
| |
| − | !Cancel referral
| |
| − | |- style="vertical-align: top;"
| |
| − | | [[Bestand:2022-08-01-HZP-Referral.svg|none|top|link=]]
| |
| − | | [[Bestand:2022-08-01-HZP-ReferralRevoke.svg|none|top|link=]]
| |
| − | |}
| |
| − | | |
| − | =FHIR profiles=
| |
