The OBX segment is primarily used to carry key clinical observation/results reporting information within report messages, which must be transmitted back to the requesting system, to another physician system (such as a referring physician or office practice system), or to an archival medical record system. In certain cases (such as ORM messages), the OBX segment may carry clinical information that might be needed by the receiving system to interpret the observation to be made, rather than actual information about observations and results.
The OBX segment is part of multiple message types that transmit patient clinical information. However this segment is most commonly utilized in ORU (Observational Report – Unsolicited) messages, and is sometimes utilized in ORM (Order) and ADT (Admit Discharge Transfer) messages. The OBX segment transmits a single observation or observation fragment, and can be used more than once in the message.
The fields in the OBX segment are as follows:
|1||4||SI||O||Set ID is a coded value data type. The value of such a field follows the formatting rules for a ST field except that it is drawn from a table of legal values. Examples of ID fields include religion and sex. – Obx|
|10||2||ID||O||Nature of Abnormal Test|
|11||1||ID||R||Observ Result Status|
|12||26||TS||O||Data Last Obs Normal Values|
|13||20||ST||O||User Defined Access Checks|
|14||26||TS||O||Date/Time of the Observation|
*Note: For the complete HL7 Standard, please go to the HL7 organization website.
OBX segments may, optionally, be followed by the NTE segment to provide notes and comments. In HL7 is a Standards Developing Organization accredited by the American National Standards Institute (ANSI) to author consensus-based standards representing a board view from healthcare system stakeholders. HL7 has compiled a collection of message form... pipe and hat format, the OBX segments (shown in red below) would look like this in an ORU-R01 message. In this example, the first OBX segment does not have any notes or comments, while the next three OBX segments do:
MSH|^~\&|LCS|LCA|Laboratory Information System (LIS) is an information system that receives, processes, and stores information generated by a medical laboratory processes. LIS is often interfaced with HIS and EMR applications. Synonyms: Laboratory Information System|TEST9999|199807311532||ORU^R01|3630|P|2.2
OBR|1|8642753100013^LIS|20923085580^LCS|083824^PANEL 083824^L|||19980728083600|||||| CH13380|19980728000000||||||20923085580||19980730041800|||F
OBX|1|NM|150001^HIV-1 ABS-O.D. RATIO^L|||||||N|X
OBX|2|CE|001719^HIV-1 ABS, SEMI-QN^L||HTN|||||N|F|19910123|| 19980729155700|BN
NTE|1|L|Result: NEGATIVE by EIA screen.
NTE|2|L|No antibodies to HIV-1 detected.
NTE|1|L|NOTE: Submission of serum
NTE|2|L|separator tube recommended
NTE|3|L|for this test. Thank you
NTE|4|L|for your cooperation if you
NTE|5|L|are already doing so.
ZPS|1|BN|LABCORP HOLDINGS|1447 YORK COURT^^BURLINGTON^NC^272152230|8007624344
How Corepoint Integration Engine works with HL7
The #1 Integration Engine Nine Consecutive Years
Customers have confidence in Corepoint Health’s history of focusing on healthcare interoperability, as evident by our #1 KLAS® ranking nine years in a row. Discover the power Corepoint Integration Engine offers healthcare providers of all sizes and specialties.