Difference between revisions of "Procedure Referral Workgroup UseCases"

From Health Level 7 Belgium Wiki
Line 11: Line 11:
 
| Actors: || Healthcare party.
 
| Actors: || Healthcare party.
 
|-
 
|-
| Description: || The healthcare party creates a prescription for a certain procedure. Information that shall be available in the message concerns the:<br>
+
| Description: || The healthcare party creates a prescription for a certain procedure.
* Patient
 
* Practitioner
 
* PractitionerRole
 
Per specific use case these shall be defined:<br>
 
* ServiceRequest (describing the actual service)
 
* Supporting information (Per specific use case to decide)
 
 
Cfr. [[Procedure_Referral_Information_Model|Information model page]] for details.
 
Cfr. [[Procedure_Referral_Information_Model|Information model page]] for details.
 
|-
 
|-
Line 32: Line 26:
 
|-
 
|-
 
| Description: || The healthcare party creates a prescription for a diagnostic image.
 
| Description: || The healthcare party creates a prescription for a diagnostic image.
Information that shall be available in the message:<br>
+
Cfr. [[Procedure_Referral_Information_Model|Information model page]] for details on the content.
* The elements as defined in the generic use case +
 
* ServiceRequest
 
** Valueset to express what is requested?
 
* Supporting information:
 
** 0..n QuestionnnaireResponse
 
*** Can we refer to standardized questionnaires?
 
** 0..n Observation
 
** 0..n DocumentReference
 
** Others?
 
Cfr. [[Procedure_Referral_Information_Model|Information model page]] for details.
 
 
|-
 
|-
 
| Additional notes: || Specific use case. Motivations to define this use case are to have some common framework around the information that is expected when requesting diagnostic images. This will enhance the general quality of the message in efficiency and the quality of the care process.
 
| Additional notes: || Specific use case. Motivations to define this use case are to have some common framework around the information that is expected when requesting diagnostic images. This will enhance the general quality of the message in efficiency and the quality of the care process.

Revision as of 15:32, 15 April 2020

DISCLAIMER: EVERYTHING ON THIS PAGE SHALL BE CONSIDERED DRAFT AS LONG AS THIS DISCLAIMER REMAINS PRESENT. - THIS PAGE IS ONGOING DISCUSSED DURING THE PROCEDURE REFERRAL WG.

This page describes the high level use cases of this WG.

Name: Issue prescription for a service.
Goal: Send out a structured prescription document.
Actors: Healthcare party.
Description: The healthcare party creates a prescription for a certain procedure.

Cfr. Information model page for details.

Additional notes: The generic use case for the referral prescripion.
Name: Issue prescription for a diagnostic imaging.
Goal: Send out a structured request for a diagnostic image.
Actors: Healthcare party.
Description: The healthcare party creates a prescription for a diagnostic image.

Cfr. Information model page for details on the content.

Additional notes: Specific use case. Motivations to define this use case are to have some common framework around the information that is expected when requesting diagnostic images. This will enhance the general quality of the message in efficiency and the quality of the care process.
Name: Healthcare party issues a prescription for a physiotherapy service.
Goal:
Actors:
Description:
Additional notes: Specific use case.
Name: Healthcare party issues a prescription for a nursing service.
Goal:
Actors:
Description:
Additional notes: Specific use case.