Test Request

Purpose

Elements are included for the billing approach, TAT/SLA tracking and prioritisation. To confirm validity of urgency and apply lower level prioritisation. To know which test has been requested, which further tests are required within this request and how many patients are being tested within this request.

Notes

Mapped to ServiceRequest, extensions are still in review. CI and CITT codes for genomic tests are pending addition to SNOMED-CT

Mapping

Source Data item Target FHIR Element HL7v2.5.1 Mapping Description
Test request - Test request id ServiceRequest.identifier ORC-2 Unique id to identify this test request.
Test request - Payment status ServiceRequest.extension:coverage IN1-15 How the test request is funded. The current ValueSet for this field is pending addition to UK Core
Test request - Date and time request sent ServiceRequest.authoredOn ORC-9 Date and time the test request was made.
Test request - Reason for testing ServiceRequest.reasonCode ORC-16 The reason for a genomic test.
Test request - High level test identifier ServiceRequest.code.coding.code OBR-4.1 The high level id which identifies the requested test. Options provided by Test Directory.
Test request - High level test identifier description ServiceRequest.code.coding.display OBR-4.2 The high level id which identifies the requested test. Options provided by Test Directory.
Test request - Low level test identifier ServiceRequest.code.coding.code OBR-4.1 The low level id which identifies the requested test. Options provided by Test Directory.
Test request - Low level test identifier description ServiceRequest.code.coding.display OBR-4.2 The low level id which identifies the requested test. Options provided by Test Directory.
Test request - Low level multipurpose test identifier ServiceRequest.orderDetail.coding.code OBR-4.1 The low level code which identifies the test to be actioned when the CITT code is multipurpose.
Test request - Low level multipurpose test identifier description ServiceRequest.orderDetail.coding.display OBR-4.2 The low level name of the test to be actioned when the CITT code is multipurpose.
Test request - Count of patients to be tested N/A - Determined through number of Patients referenced in ServiceRequests in test order N/A - for HL7v2, each patient test request SHOULD be sent using a new OML^O21 message Count of patients to be tested.
Test request - Urgency reason ServiceRequest.extension:priorityReason N/A could possibly use TQ1-10 If urgent, the test request urgency reason.
Test request - Reason for reanalysis Additional ServiceRequest.reasonCode elements OBR-13 segment linked to ORC The reason for a genomic test.
Test request - Detail of reason for reanalysis ServiceRequest.supportingInfo elements (if structured, ServiceRequest.note if unstructured TBC) NTE segments linked to OBR segment for reanalysis reason The detail associated to the reason reanalysis has been requested.
Test request - Type of reanalysis ServiceRequest.orderDetail Additional NTE segments attached to OBR The type of reanalysis which has been requested.
Test request - DNA storage information ServiceRequest.orderDetail Additional NTE segments attached to OBR If the reason for testing is DNA storage, this captures further detail.
Test request - Is urgent ServiceRequest.priority TQ1-9 Confirmation if the test request is urgent.
Test request - Date report required by ServiceRequest.occurrenceDateTime OBR-8 The date a completed genomic report is required by.
Test request - Recipient ODS code ServiceRequest.performer Normally the recipient of the OML message, potentially could be recorded under ORC-3.2 ODS code of the first organisation which receives the genomic test request.