V2-FHIR Mapping - Segment: OBX[Media] - Orders & Observations (2024)

HL7 V2
HL7 FHIR
CommentsNameDefinitionData TypeMapping Rules
NameDefinitionData TypeMapping Rules
OBX-01.00.00 -Set ID - OBXThis field contains the sequence number.

SI








This field doesn't warrant mappingOBX-02.00.00 - Value TypeThis field defines the data type of OBX-5, Observation ValueID

Media.type??Classification of media as image, video, or audiocode

Can we tell an image from a video by OBX-2 or is OBX-3 more appropriate?

Will there ever be a value other than RP that maps to Media?

OBX-03.00.00 - Observation IdentifierThis field contains a unique identifier for the observation.CWE

Media.type??

or

Media.modality

or

Media.view

Classification of media as image, video, or audio

or

The type of acquisition equipment/process

or

Imaging view, e.g. Lateral or Antero-posterior

code

or

CodeableConcept

or

CodeableConcept




OBX-04.00.00 - Observation Sub-IDThis field is used to distinguish between multiple OBX segments with the same observation ID organized under one OBR. Starting with V2.8.2 the data type was changed from ST to OG to enable improved structured grouping of observation segmentsOG







OBX-05.00.00 - Observation ValueThis field contains the value observed by the observation producerVaries

Media.content.urlUri where the data can be founduri

If the data type is RP, additional mappings to the Attachment data type are possibleOBX-06.00.00 - UnitsThis field contains the units of measurement for the value in OBX-5CWE






n/a for a media OBX segmentOBX-07.00.00 - References Range
ST






n/a for a media OBX segmentOBX-08.00.00 - Interpretation CodesOne or more codes specifying a categorical assessment of the observation value (OBX.5)CWE







OBX-09.00.00 - ProbabilityThis field contains the probability of a result being true for results with categorical values.NM







OBX-10.00.00 - Nature of Abnormal TestThis field contains the nature of the abnormal test.ID







OBX-11.00.00 - Observation Result StatusThis field contains the observation result statusID

Media.statusThe current state of the {{title}}.codeWill need a translation table
Most OBXs are likely to have a status of F which likely maps to completedOBX-12.00.00 - Effective Date of Reference RangeThis field contains the date (and, optionally, the time) on which the values in OBX-7-reference range went into effect.DTM






n/a for a media OBX segmentOBX-13.00.00 - User Defined Access ChecksThis field permits the producer to record results-dependent codes for classifying the observation at the receiving system. This field should be needed only rarely, because most classifications are fixed attributes of the observation ID and can be defined in the associated observation master fileST






No apparent mapping as this is a fairly broad fieldOBX-14.00.00 - Date/Time of the ObservationThe physiologically relevant date-time or the closest approximation to that date-timeDTM

Media.content.creationDate attachment was first createddateTime

This isn't an exact mapping, but it seems to be better than Media.issuedOBX-15.00.00 - Producer's IDThis field contains a unique identifier of the responsible producing serviceCWE

Media.operator?The person who generated the image


Media.operator can map to a variety of resources. A single mapping might difficult. OBX-15 and -16 might combine to a Practitioner resourceOBX-16.00.00 - Responsible ObserverWhen required, this field contains the identifier of the individual directly responsible for the observationXCN

Media.operator?The person who generated the image



OBX-17.00.00 - Observation MethodThis optional field can be used to transmit the method or procedure by which an observation was obtained when the sending system wishes to distinguish among one measurement obtained by different methods and the distinction is not implicit in the test ID.CWE






This might contribute to Media.type and/or Media.modality and/or Media.viewOBX-18.00.00 - Equipment Instance IdentifierThis field identifies the Equipment Instance (e.g., Analyzer, Analyzer module, group of Analyzers, etc.) responsible for the production of the observationEI

Media.device.identifier

and/or

Media.deviceName

Observing Device

Reference

or

string




OBX-19.00.00 - Date/Time of the AnalysisThis field is used to transfer the time stamp associated with generation of the analytical result by the instrument specified in Equipment Instance IdentifierDTM






Would this be better for Media.content.creation than OBX-11?OBX-20.00.00 - Observation SiteThis field typically contains the body site(s) where the measurement being reported was obtained. This field should not be used for a specimen source or specimen collection site.CWE

Media.bodySiteObserved body partCodeableConceptSee CWE mapping

OBX-21.00.00 - Observation Instance Identifier

This field contains a unique identifier for this observation. This instance identifier is persistent between messages. At this time, there are no documented use cases for this field in the context of messages as described in this chapter.

EI

Media.identifier

or

Media.id






OBX-22.00.00 - Mood CodeThis field identifies the actuality of the observation (e.g., intent, request, promise, event). At this time, there are no documented use cases for this field in the context of messages as described in this chapter.CNE






No good mapping, but could it contribute to Media.status?OBX-23.00.00 - Performing Organization NameThis field contains the name of the organization/service responsible for performing the service.XON

Media.operatorThe person who generated the imageReference (including to an Organization)

Only one operator (0..1) can be included in the Media resourceOBX-24.00.00 - Performing Organization Address

This field contains the address of the organization/service responsible for performing the service.

XAD

Media.operatorThe person who generated the imageReference (including to an Organization)

Only one operator (0..1) can be included in the Media resourceOBX-25.00.00 - Performing Organization Medical DirectorThis field contains the medical director of the organization/service responsible for performing the service.XCN






No apparent mappingOBX-26.00.00 - Patient Results Release CategoryThis field contains instructions on whether to share the results with the patient, and if so how.ID






Could be related to security labelsOBX-27.00.00 - Root CauseThis element contains the reason code indicating the root cause for the reissue of a previously released lab report.CWE






No apparent mappingOBX-28.00.00 - Local Process ControlThis element contains information intended to be used for locally defined processing, particularly process control/status type informationCWE






No apparent mappingOBX-29.00.00 - Observation TypeThis field indicates the type of observation to enable systems to distinguish between observations sent along with an order, versus observations sent as the result to an order.ID






No apparent mappingOBX-30.00.00 - Observation Sub-TypeThe result sub-type provides further classification of OBX-29 Observation Type.ID






No apparent mapping
V2-FHIR Mapping - Segment: OBX[Media] - Orders & Observations (2024)

FAQs

What is the OBX segment in HL7 V2? ›

HL7-Definition V2

The OBX segment is used to transmit a single observation or observation fragment. It represents the smallest indivisible unit of a report. The OBX segment can also contain encapsulated data, e.g., a CDA document or a DICOM image.

What is the OBX segment in a message? ›

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.

What is the difference between HL7 FHIR and V2? ›

FHIR is the newest standard that addresses healthcare interoperability problems, whereas HL7 V2 is used for communication within different systems in a healthcare establishment. Adopting FHIR is necessary for providers who want to comply with industry standards.

What is obx 3 in HL7? ›

OBX. 3 - Observation Identifier Field (HL7 v2. 5)

What is the HL7 standard V2? ›

HL7 Version 2

HL7v2 is the most widely used healthcare messaging standard for exchanging clinical and patient information between systems. The goal of HL7v2 was to provide enterprise-wide interoperability between health information systems using standardized messages representing clinical event information.

What is an obx HL7 message? ›

In the context of HL7 messages, the "OBX" segment is used to convey observation results or other observations that are made about a patient or specimen. The "OBX" segment is used to provide information about an observation in a structured way, including the observation identifier, value, and units of measure.

What are the 2 groups called in OBX? ›

On the island there are two types of people split into social categories, there are the “Kooks” who are the wealthier class, and the “Pogues” which are the working class.

What is a summary of OBX? ›

The show follows a group of Pogue teenagers who live at The Cut and are determined to find out what happened to the missing father of the group's ringleader, John B. Along the way, they discover a legendary treasure that is tied to John B's father.

What does OBX consist of? ›

The real Outer Banks consists of three main islands: Northern Beaches, Roanoke Island & Dare Mainland, and Hatteras Island. Read more about the layout of the land here.

Are FHIR and HL7 the same thing? ›

Understanding HL7 and FHIR

In essence, HL7 is an international standard for exchanging healthcare data, while FHIR is an open standard that facilitates the exchange of data between new applications and legacy systems.

Can FHIR replace HL7? ›

FHIR can meet the needs covered by HL7 V2, V3, and CDA, and provide further benefits for ease of interoperability.

What is the difference between an API and FHIR? ›

APIs can be simple, with rigid definitions of data structure, or complex, with different data structures for a wide array of interactions. The FHIR API mainly involves the access and exchange of data. Many modern applications, both desktop and mobile, use APIs to retrieve, store, and update data.

What is obx 5? ›

OBX-5: Observation Value (Varies) 00573. Definition: This field contains the value observed by the observation producer. OBX-2-value type contains the data type for this field according to which observation value is formatted.

How is FHIR related to HL7? ›

What Is HL7® FHIR®? is a next-generation interoperability standard created by the standards development organization Health Level 7 (HL7®). FHIR is designed to enable health data, including clinical and administrative data, to be quickly and efficiently exchanged.

What is OBR and OBX in HL7? ›

The OBX segment mainly carry clinical report data. It is mainly used in ORU message and rarely with ORM , ADT and other. This segment is optional and can be repeated in message. The OBR segment mainly carry placer and filler order numbers (used as identifiers), exam information etc.

What is the airport code for OBX? ›

OBX, IATA airport code of Obo Airport (Papua New Guinea)

What can the obx-8 field contain? ›

This field contains a table lookup indicating the normalcy status of the result. We strongly recommend sending this value when applicable. (See ASTM 1238 - review for more details).

What is the message subcomponent separator in HL7? ›

An ampersand character separates adjacent subcomponents of data fields where allowed by the HL7 standard. If there are no subcomponents, then you can omit this character. A tilde character separates multiple occurrences of components or subcomponents in a field where allowed by the HL7 standard.

References

Top Articles
Latest Posts
Article information

Author: Arielle Torp

Last Updated:

Views: 6140

Rating: 4 / 5 (41 voted)

Reviews: 80% of readers found this page helpful

Author information

Name: Arielle Torp

Birthday: 1997-09-20

Address: 87313 Erdman Vista, North Dustinborough, WA 37563

Phone: +97216742823598

Job: Central Technology Officer

Hobby: Taekwondo, Macrame, Foreign language learning, Kite flying, Cooking, Skiing, Computer programming

Introduction: My name is Arielle Torp, I am a comfortable, kind, zealous, lovely, jolly, colorful, adventurous person who loves writing and wants to share my knowledge and understanding with you.