HL7 terms: In the HL7 Standard, an order (ORM) is any request for materials (e.g., 500 ml of 2.5% saline) or services (e.g., a range of motion study, an EKG, a lipid panel, etc.).
Orders are usually for a particular patient, but they can also be for a department (e.g., floor stock) or for a non-patient (e.g., an environment study where no specific patient is involved.)
The transmission of clinical orders occurs between the application placing the order (the placer) and the clinical application filling the order (the filler).
Typically, the caregiver (e.g., physician) is entering orders on the HIS application which acts as the placer application in HL7 messaging parlance. The system to which the order is targeted (e.g., the lab in the case of a complete blood count order) is the filler of the order.
Health Standards
Latest posts by Health Standards (see all)
- Will web APIs and HL7 FHIR change our views on data interoperability? - July 11, 2017
- [#HITsm chat 11.18.16] Celebrate Passing the #HITsm Torch - November 15, 2016
- Passing the #HITsm torch - November 10, 2016
Pingback: ORM vs. RDE for HL7 Pharmacy Orders()
Pingback: What Is an OBX?()
Pingback: How Widely Adopted Is HL7?()
Pingback: Placer Order Number vs. Filler Order Number()
Pingback: Integrating EMRs with Reference Labs()
Pingback: Comparing HL7 Messages to HL7 Documents()
Pingback: What Is an ORM Message?()
Pingback: ORM vs. RDE for HL7 Pharmacy Orders | HL7 Standards()
Pingback: Integrating EMRs with Reference Labs | HL7 Standards()
Pingback: Procedure Code Mapping for Imaging Centers with HL7 | HL7 Standards()
Pingback: Confluence: Lynx()