AU eRequesting
0.1.0-ci-build - ci-build
AU eRequesting
0.1.0-ci-build - ci-build
AU eRequesting, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 0.1.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-erequesting/ and changes regularly. See the Directory of published versions
This page contains the use cases for AU eRequesting for the first release of the TDG Implementation Guide (R1). This is a working page and will reflect the current state of agreement by the TDG as well as the current draft of the use case material.
Feedback on these use cases is requested. In particular we are seeking assistance to refine the detailed description of the use cases (the non-bolded text). Please provide feedback including improvement suggestions at this page: AU eRequesting R1 use cases.
| ID | Description | Actors | Systems | Data Groups |
|---|---|---|---|---|
| D01 | Request for diagnostic imaging (generic data collection requirements) A requesting clinician requires diagnostic imaging for a patient, following a consultation about an affected body part. The request contains information such as: Patient demographics (including sex and gender), Targeted body part, Type of imaging required, Reason for requesting imaging, relevant clinical history, any precautions about the patient’s other conditions such as device implants/allergies/medicines/related pathology results, destination(s) where the results need to be sent back to (including Copy To/Carbon Copy/copy to practitioners, as well as the original requestor), and information to support billing. |
Patient Requesting Practitioner (e.g. GP) |
Requesting System | Patient Details Requestor Details Requested Service Details Relevant Clinical Details Billing Details Preferred Reporting Clinician |
| D02 | Request for diagnostic imaging (Assigned request) A requesting clinician decides that an MRI head scan is indicated for a patient. The clinician and patient agree upon a local diagnostic imaging service provider and the clinician submits the eRequest for the scan directly to that provider. The patient is not required to present an eRequest token to the provider when they make a booking or attend the test. |
Patient Requesting Practitioner (e.g. GP) Diagnostic imaging service provider |
Requesting System Service provider booking system |
Patient Details Requestor Details Requested Service Details Relevant Clinical Details Billing Details Provider Details |
| D03 | Request for diagnostic examination (Unassigned request) A requesting clinician requires a chest X-Ray for a patient, following a consultation about pain in their torso. The clinician creates the eRequest, then generates a token and gives this to the patient. The patient researches local diagnostic imaging service providers and makes a booking with one of them. When the patient makes a booking or attends the appointment, they present the token to the service provider who uses it to download the eRequest information into their booking system. |
Patient Requesting Practitioner (e.g. GP) Diagnostic imaging service provider |
Requesting System Service provider booking system Token management system |
Patient Details Requestor Details Requested Service Details Relevant Clinical Details Billing Details Token Identifier |
| D04 | Request for diagnostic examination (Reassigned request) A requesting clinician requires a CT Brain scan (with contrast) for a patient, following a consultation about neurological symptoms. The clinician and patient agree upon a local diagnostic imaging service provider and the clinician submits the eRequest for the scan to that provider. Before the patient is due to attend the provider, the patient changes their mind and elects to have the test performed by a different provider. The patient makes a booking with the new provider and when they attend the appointment they present a token to the service provider who uses it to download the eRequest information into their booking system. |
Patient Requesting Practitioner (e.g. GP) Diagnostic imaging service provider |
Requesting System Service provider booking system Token management system |
Patient Details Requestor Details Requested Service Details Relevant Clinical Details Billing Details Provider Details (initial provider) Token Identifier? |
| ID | Description | Actors | Systems | Data Groups |
|---|---|---|---|---|
| P10 | Request for a pathology test (generic data collection requirements) A requesting clinician requires a pathology test for a patient, following a consultation. The request contains information such as: Patient demographics (including sex and gender), Specimen type, Type of test required, Reason for requesting, any precautions about the patient’s other conditions such as device implants/allergies/medicines/related pathology results, destination(s) where the results need to be sent back to (including Copy To/Carbon Copy/copy to practitioners, as well as the original requestor), and information to support billing. |
Patient Requesting Practitioner (e.g. GP) Pathology service provider |
Requesting System | Patient Details Requestor Details Requested Service Details Relevant Clinical Details Billing Details Preferred Reporting Clinician |
| P02 | Request for a pathology test (Assigned request) A requesting clinician requires a Liver Function Test to be performed on a patient to assist with diagnosing a condition. The clinician creates the request and after discussing service providers with the patient, sends it directly to a pathology service that the clinician and patient agree upon. |
Patient Requesting Practitioner (e.g. GP) Pathology service provider |
Requesting System Service provider booking system |
Patient Details Requestor Details Requested Service Details Relevant Clinical Details Billing Details Provider Details |
| P01 | Request for a pathology test (Unassigned request) A requesting clinician requires a Full Blood Count test to be performed on a patient to assist with diagnosing a condition. The clinician creates the eRequest, then generates a token and gives this to the patient. The patient researches local pathology service providers and selects one to perform the test. The patient presents the token to the service provider who uses it to download the eRequest information into their Collection system or Laboratory Information System (LIS). |
Patient Requesting Practitioner (e.g. GP) Pathology service provider |
Requesting System Service provider booking system Token management system |
Patient Details Requestor Details Requested Service Details Relevant Clinical Details Billing Details Token identifier |
| P03 | Request for a pathology test (Reassigned request) A requesting clinician requires a Thyroid Stimulating Hormone (TSH) test to be performed on a patient. The clinician creates the request and after discussing service providers with the patient, sends it directly to a pathology service that the clinician and patient agree upon. After leaving the clinician's office, the patient changes their mind and elects to have the test performed by a different provider. The patient proceeds directly to the new provider and presents a token for the request, which the provider uses to download the eRequest information into their testing management system. |
Patient Requesting Practitioner (e.g. GP) Pathology service provider |
Requesting System Service provider booking system |
Patient Details Requestor Details Requested Service Details (includes site to be tested) Relevant Clinical Details Billing Details Provider Details (initial provider) Token Identifier? |
| P09 | Rule 3 INR Test A clinician requests an ongoing International Normalized Ratio (INR) test specifying a "Rule 3 Exemption" for a patient undergoing anticoagulant therapy. The requester requires 6 INR tests to be performed over the next 6 months. |
Patient Requesting Practitioner (e.g. GP) Pathology service provider |
Patient Requesting System Service Provider's LIS system |
Patient Details Requestor Details Requested Service Details Relevant Clinical Details Billing Details |
| ID | Description | Actors | Systems | Data Groups |
|---|---|---|---|---|
| G01 | Tracking fulfilment of a Service Request A GP checks the status of a requested test for a patient, e.g. Accepted, Cancelled, Pending, Collected, Preliminary, Completed, etc. |
Requesting Practitioner (e.g. GP) | Requesting System EHR |
Provider Details Token Identifier? Patient Identifiers? |
| G02 | Cancelling an eRequest (requestor) An eRequest is revoked/cancelled by the requesting health care professional because the requested service is no longer required. |
Requesting Practitioner (e.g. GP) | Requesting System EHR |
Provider Details Token Identifier? Patient Identifiers? |
| G03 | Cancelling an eRequest (provider) An eRequest is revoked/cancelled by the service provider because they are no longer able to provide the requested service for the patient. This cancellation has occurred before the provider has started the service (e.g. before the patient has attended the provider), hence it is not considered a non-fulfilment of the service. |
Service Provider | EHR | Requestor Details Token Identifier? Patient Identifiers? |
| G07 | Specification of results to be copied to another clinician A hospital clinician requests diagnostic imaging for a patient after they have been discharged from the hospital, as a follow-up test. The results are requested to be sent to the hospital clinician and the patient's GP. |
Hospital Clinician / Specialist GP / Specialist Service Provider |
Requesting System Service provider booking system |
Patient Details Requestor Details Requested Service Details Relevant Clinical Details Billing Details Results Copy To |
IG © 2024 HL7 Australia. Package hl7.fhir.au.erequesting#0.1.0-ci-build based on FHIR 4.0.1. Generated 2024-04-30
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change