Diagnostic Order
Diagnostic Order
Introduction
The Diagnostic Order data model is designed to comprehensively represent and manage diagnostic orders for patients, focusing on the OBR (Observation Request) segment of HL7 messages. It plays a critical role in healthcare data management, enabling healthcare systems to efficiently track, process, and document diagnostic orders and related information. This model provides developers with a structured framework for querying and utilizing diagnostic order data effectively within healthcare applications.
Use Case
Developers can leverage the Diagnostic Order data model for a variety of technical use cases, ensuring the efficient handling of diagnostic orders and associated data within healthcare systems
- Order Management: Developers can use this model to manage and monitor diagnostic orders, including querying filler order numbers, diagnostic IDs, and encounter IDs to track the status and progress of orders.
- Diagnostic Data Integration: This model enables the integration of diagnostic order data with electronic health records (EHRs) and other healthcare information systems. Developers can query patient IDs, diagnostic IDs, and specimen sources for seamless data integration.
- Order Scheduling: Developers can utilize the model's data elements, such as planned patient transport comments, observation datetime1, and transportation mode, to implement scheduling features for diagnostic procedures, ensuring efficient logistics.
- Billing and Claims Processing: Billing and claims processing systems can benefit from querying charge-to-practice, procedure codes, and diagnostic IDs to facilitate accurate billing and claims submission related to diagnostic services.
- Patient Diagnostic History: By querying patient IDs, encounter IDs, and visit numbers, developers can compile comprehensive diagnostic order histories for individual patients, supporting better-informed clinical decisions and patient care.
- Data Enrichment: Developers can enrich diagnostic order data by combining it with other healthcare data models, such as patient and provider data, to create comprehensive patient profiles, enabling personalized healthcare recommendations and treatment plans.
- Quality Assurance: Developers can use the model to monitor the quality and accuracy of diagnostic order data by querying result statuses and specimen sources, ensuring data integrity within healthcare systems.
- Diagnostic Data Analysis: Developers can query and analyze diagnostic order data to identify trends, patterns, and opportunities for quality improvement, ultimately enhancing the delivery of diagnostic services.
- Research Integration: Researchers can access diagnostic order data for research purposes through APIs and data interfaces provided by this model, enabling the development of research applications and tools.
- Compliance and Reporting: Developers can use the model to support compliance with healthcare regulations and reporting requirements by querying relevant fields for auditing and reporting purposes.
Data Fields
| Attribute Name | Description | HL7 Mapping | Data Type | Label | Use Case |
|---|---|---|---|---|---|
| transport_logistics_of_collected_sample | Transport Logistics of Collected Sample | OBR-38 | string | Transport Logistics of Collected Sample | This field contains instructions regarding the logistics and transportation of a collected sample. This may include information on the container, storage conditions, temperature requirements, or any specific handling instructions for the sample. |
| universal_service_identifier | Universal Service Identifier | OBR-5 | string | Universal Service Identifier | This field serves as a standardised identifier for the laboratory test or observation being requested. It ensures that there is a common code to represent the test, making it easier for systems and users to understand and process the request accurately. |
| filler_order_number | Filler Order Number | OBR-3, SCH-27, ORC-3 | string | Filler Order Number | This field provides a unique identifier for the laboratory or diagnostic test order associated with a specific result or observation. It's used to link the order to its corresponding result. |
| collection_volume | Collection Volume | OBR-9 | string | Collection Volume | This field contains information about the volume or quantity of the specimen that should be collected for the laboratory test. This is important for ensuring that an adequate sample size is obtained for accurate testing. |
| collector_comment | Collector's Comment | OBR-39 | string | Collector's Comment | This field can include specific instructions or comments related to the collection, handling, or transportation of the specimen. These instructions may address special precautions, sample stability, or any unique circumstances. |
| requested_datetime | Requested Date/Time | ORC-15, OBR-6 | date | Requested Date/Time | This field represents the date and time when an order (e.g., a lab test, medication, or procedure) is requested or ordered by a healthcare provider. It specifies when the order was placed. |
| transport_arrangement_responsibility | Transport Arrangement Responsibility | OBR-40 | string | Transport Arrangement Responsibility | This field designates whether the responsibility for arranging transportation of the specimen to the laboratory falls on the requesting healthcare provider, the performing laboratory, or another entity involved in the healthcare process. |
| transportation_mode | Transportation Mode | OBR-30 | string | Transportation Mode | This field provides information about how the specimen is physically transported from the location where it was collected (e.g., a healthcare facility) to the laboratory where testing will be performed. |
| quantity | Quantity | TQ1-2 | string | Quantity | This field provides information about how the specimen is physically transported from the location where it was collected (e.g., a healthcare facility) to the laboratory where testing will be performed. |
| result_handling | Result Handling | OBR-49 | string | Result Handling | This field indicates the desired method or process for handling and reporting the results of the ordered test or observation. It may specify where and how the results should be sent. |
| patient_id | Id of the patient | PID-3-1 | string | Patient ID | The patient ID is a unique identifier assigned to a patient within the healthcare system. It is used to accurately identify and link a patient's medical records, treatments, and history. |
| procedure_code_modifier | Procedure Code Modifier | OBR-45 | string | Procedure Code Modifier | This field may include modifiers that provide more specific information about the procedure or test requested. These modifiers can refine the nature of the procedure or its context. |
| placer_order_number | Filler Order Number | ORC-2 | string | Placer Order Number | This field is used to uniquely identify an order within the healthcare system. It helps in tracking and managing orders for various services or procedures. |
| parent | Parent | OBR-29 | string | Parent | This field is used to establish a hierarchical relationship between different tests or observations. It indicates that a child test or observation is associated with a parent test. |
| specimen_action_code | Specimen Action Code | OBR-11 | string | Specimen Action Code | This field specifies whether a specimen is to be collected ("C" for collect) for the associated test or observation. In this case, it indicates that a specimen should be obtained from the patient. |
| order_callback_phone_number | Order Callback Phone Number | OBR-17 | string | Order Callback Phone Number | This field is used to specify the phone number at which the ordering healthcare provider or facility can be reached for callback purposes. This is particularly important when the laboratory needs to communicate test results or other relevant information. |
| diagnostics_id | This is diagnostics_id attribute | ORC+MSH-10, SCH+MSH-10 | string | Diagnostics ID | This field often contains a code or identifier that uniquely represents the diagnostic test or procedure being requested. This code can be used to identify the test. |
| bundle_id | ID of bundle | MSH-10 | string | Bundle ID | “bundle ID" typically refers to a unique identifier assigned to a group or bundle of related messages or data elements. This identifier is used to associate multiple messages or pieces of information that are related to a specific patient, event, or transaction. |
| result_status | Result Status | OBR-25 | string | Result Status | This field is used to convey the status of a test result. It indicates whether the result is preliminary, final, amended, corrected, or has a different status. |
| escort_required | Escort Required | OBR-42 | string | Escort Required | This field is used to ensure the safety and well-being of patients who may have specific needs or limitations that require assistance or supervision during a medical procedure or test. |
| parent_result | Parent Result | OBR-26 | string | Parent Result | This field is used to ensure the safety and well-being of patients who may have specific needs or limitations that require assistance or supervision during a medical procedure or test. |
| results_datetime | Results Rpt/Status Chng - Date/Time | OBR-22 | date | Results Rpt/Status Chng - Date/Time | This field is used to timestamp when the results of a specific test or observation were generated. This information is critical for tracking the timing of the results. |
| number_of_sample_containers | Number of Sample Containers | OBR-37 | string | Number of Sample Containers | This field is used to track the number of physical sample containers collected for a specific test. This information is important for ensuring that all samples are accounted for and properly processed in the laboratory. |
| planned_patient_transport_comment | Planned Patient Transport Comment | OBR-43 | string | Planned Patient Transport Comment | This field is used to include specific comments or instructions regarding the planned transport of a patient from one location to another within a healthcare facility or between facilities. |
| encounter_id | Encounter ID | PV1+MSH-10 | string | Encounter ID | This unique identifier is used to associate various HL7 messages with a specific patient encounter or visit. It ensures that data and events are accurately linked to the correct patient's healthcare journey. |
| medically_necessary_duplicate_procedure_reason | Medically Necessary Duplicate Procedure Reason | OBR-48 | string | Medically Necessary Duplicate Procedure Reason | This field is used when a healthcare provider believes that a duplicate medical procedure or test is medically necessary. This can occur for various reasons, such as the need for confirmation, validation, or additional information. |
| batch_id | Batch id | System Generated | string | Batch ID | "batch ID" is a unique identifier assigned to a group of messages that are logically grouped together for processing or transmission. Batching messages is a common practice in healthcare systems to efficiently manage and transmit multiple messages as a single unit |
| observation_end_datetime | Observation End Date/Time | OBR-2 | date | Observation End Date/Time | This field provides temporal context by indicating when the observation or test concluded. It is especially important when the duration of the observation or test is relevant to the interpretation of results. |
| danger_code | Danger Code | OBR-12 | string | Danger Code | This field is used to convey safety-related information regarding the requested observation or test. It may indicate any known risks or dangers that healthcare providers should be aware of when performing the test. |
| relevant_clinical_information | Relevant Clinical Information | OBR-13 | string | Relevant Clinical Information | This fiel is used to provide essential clinical context or information that can assist healthcare providers in understanding why a specific observation or test is being requested. |
| specimen_received_datetime | Specimen Received Date/Time | SPM-18, OBR-14 | date | Specimen Received Date/Time | This field is used for tracking specimens from the point of collection to the laboratory and through the testing process. They ensure that the specimen's handling and testing are properly documented. |
| charge_to_practice | Charge to Practice | OBR-23 | string | Charge to Practice | This field is used to specify which medical practice or entity should be billed for the test or observation. |
| alternate_visit_id | Alternative visit id | PV1-50/PID-18 | string | Alternate Visit Id | This field provides an alternate identifier for a patient's visit. It is used for tracking and cross-referencing patient visits and records, especially in scenarios requiring multiple identifiers or references. This field is recorded during patient registration and aids in accurate record linkage. |
| diagnostic_serv_sect_id | Diagnostic Serv Sect ID | OBR-24 | string | Diagnostic Serv Sect ID | This field is used to specify the department or section within a laboratory or healthcare facility that will conduct the diagnostic service. This can include sections like chemistry, hematology, microbiology, radiology, etc. |
| reason_for_study | Reason for Study | OBR-31 | string | Reason for Study | This field is used to document the clinical reason or indication for ordering a particular test or study. It explains why the test is necessary from a diagnostic or clinical perspective. |
| priority | Priority | TQ1-9, OBR-5 | string | Priority | The "Priority" field is used to indicate the urgency or importance of a scheduled action or observation. |
| transport_arranged | Transport Arranged | OBR-41 | string | Transport Arranged | This field is used to specify whether arrangements have been made for the transportation of patients, specimens, or other items related to a medical order or observation. |
| lineage | This is lineage attribute | Fixed - HL7 | string | Lineage | "lineage" refers to the information about the origin or source of a message. It helps trace the path of the message, indicating where it originated, how it was transmitted, and any intermediate systems or components it passed through before reaching its destination. |
| timing | Timing | TQ1-7 | date | Timing | This field is used to define the timing or schedule for a scheduled action or observation. It indicates when the action is planned to occur. |
| scheduled_datetime | Scheduled Date/Time | OBR-36 | string | Scheduled Date/Time | This field is used to indicate the exact date and time at which a specific observation or test is scheduled to take place. |
| procedure_code | Procedure Code | OBR-39 | string | Procedure Code | This field is used to provide a standardised code that identifies the specific medical procedure or test that has been ordered. |
| xc_visit_id | XC visit id | Based on alternate_visit_id followed by visit_number followed by system generated ID | string | XC visit id | The "xc_visit_id" is a unique identifier used to group together all the interactions, procedures, tests, and check-ups associated with a single patient visit in a healthcare setting. This identifier helps in organising and managing various activities and data related to that specific patient encounter. |
| visit_number | Id of the visit | PV1-19-1 | string | Visit Number | The visit number serves as a unique identifier for a specific patient visit or encounter within a healthcare facility. It distinguishes one visit from another. |
| specimen_source | Specimen Source | SPM-4 | string | Specimen Source | This field is used to describe the location or source from which a biological specimen, such as blood, urine, or tissue, was collected. |
| observation_datetime | Observation Date/Time | OBR-7 | date | Observation Date/Time | This field is used to indicate the exact date and time when a specific observation or test was conducted or observed. |
Similar Models
Here are the models that are similar to the current data model