HL7 OML_O21 Laboratory Order
OML_O21 is the laboratory order message introduced for more explicit lab and automation workflows. It still has the familiar order pieces, but it gives specimen and container detail first-class structure through groups such as specimen, container, prior result, and observation request.
If ORM_O01 is the broad old workhorse, OML_O21 is the lab-aware version you reach for when specimen identity, specimen type, collection details, container IDs, and lab automation matter. Many modern lab interfaces prefer OML because it avoids overloading OBR fields with specimen facts that deserve their own segments.
A small OML lab order example
What workflow it represents
The sender is normally an ordering system, EHR, or middleware. The receiver is a LIS, lab automation system, specimen processing system, or integration engine in front of those systems. The receiver creates the order and ties it to one or more specimens, containers, and tests.
The practical distinction from ORM is that the specimen is not an afterthought. SPM identifies the specimen and its type. SAC can identify the container. That becomes critical when the same order has multiple specimens, aliquots, tubes, or automation steps.
How to read the structure
The patient group is optional in the abstract structure but common in real interfaces. PID identifies the patient, PV1 ties the order to a visit when needed, and insurance or guarantor groups appear when the lab needs billing context.
The required order group starts with ORC. The observation request group usually contains OBR, notes, diagnosis, order-level OBX observations, then specimen groups. Prior result groups can carry history that helps the lab interpret or process the order.
Specimens and containers
Use SPM for specimen identity and specimen characteristics. Do not bury specimen type and collection details in a local OBR note if both systems can handle SPM. Container identifiers belong in SAC when the workflow tracks tubes, plates, trays, or automation containers.
Implementation guides sometimes map older OBR specimen fields into SPM fields during migrations from ORM to OML. That is fine as a transition plan, but the long-term model should make specimen and container information explicit.
Reference notes
Caristix describes OML_O21 as a laboratory and other order message that is required for lab automation use cases in older HL7 versions. Public lab-order implementation guides also show practical mappings from ORM-style OBR specimen details into OML/SPM structures.