Placeholder
HL7-defined code system of abstract message structure codes. Each code identifies a specific message structure abstract syntax as published in the HL7 Version 2 standard. Used in HL7 Version 2.x messaging in the MSH segment.
Underlying Master Code System for V2 table 0354 (Message Structure)
Copyright HL7. Licensed under creative commons public domain
Version of HL7 in which the code was deprecated
this is a typo BRP_O30) and should be removed
Laboratory Fulfillment request with REL segment
Laboratory order message structure for fulfillment request with REL segment
An example is the IHE LCC profile describes this message in the LAB-7 transaction
Deprecated; was added erroneously in 2016
Identifier for the message structure for an OMQ message with a trigger event of General Order Message with Document Payload (O57)
Identifier for the message structure for an ORL message with a trigger event of - General Laboratory Order Acknowledgment Message (Patient Optional) (O53)
Identifier for the message structure for an ORL message with a trigger event of Laboratory Order Acknowledgment Message – Multiple Order Per Specimen (Patient Optional) (O54)
Identifier for the message structure for an ORL message with a trigger event of Laboratory Order Acknowledgment Message – Multiple Order Per Container of Specimen (Patient Optional) (O55)
Identifier for the message structure for an ORL message with a trigger event of Specimen Shipment Centric Laboratory Order Acknowledgment Message (Patient Optional) (O56)
Identifier for the message structure for an ORX message with a trigger event of General Order Message with Document Payload Acknowledgement Message (O58)
Identifier for the message structure for an OSU message with a trigger event of Order Status Update (O51)
Identifier for the message structure for an OSU message with a trigger event of Order Status Update Acknowledgement (O52)
Specimen Container Preparation and Specimen Collection Event
This message structure supports tracking of information related to preparations for specimen collection and the collection event.
It can be used to describe the container preparation for collection as wellasthe successful collection of one or more specimen(s).
This message structure supports tracking of information when specimen collection is not successful.
It can be used to describe the reason why a specimen collection was unsuccessful.
This message structure supports tracking of information related to the movements of specimens across locations, and placement in and out of storage.
It can be used to report on specimen departing, arriving, being accepted or rejected, including moving the specimen into storage or retrieving it from storage (e.g. in biobanking).
This message structure supports tracking of information to identify or de-identify specimens or at time of final disposal.
It can be used to report the de-and re-identification of specimen(s) as well as the final disposition of a specimen.
This message structure supports tracking of information related to processing of one or more specimen that may result in derived (child) specimen or not.
This message structure supports tracking of information when the processing of a specimen was unsuccessful.
It can be used to describe the reason why the specimen processing was unsuccessful.