Segment OBX to Observation Map

Note that in Observation there is category field that depending on implementation guide and/or realm is required. MSH-9.2 Trigger Event, the MSH-3 Sending Application and OBX-3 Observation Identifier's code system ontology would inform how to value Observation.category.

IF: Map to Observation.partOf or Observation.hasMember or Observation.DerivedFrom according to the implementation guidance for the v2 message at hand, otherwise map to the extension-sub-id to enable the final destination to determine how to structure the observations.

OBX-4 Sub Identifier would determine how to use Observation.partOf or Observation.hasMember or Observation.DerivedFrom, but is highly dependent on the local implementation of OBX-4 or an implementation guide (e.g., LRI, Clinical Genomics). That is not known at the standard level, so we cannot provide specific mapping guidance here. However, if the mapper does not have access to the syntax used and its meaning, we need to be able to pass on OBX-4 Sub Identifier to the final destination that should know how to then structure it using FHIR attributes.

IF: Any markup in ST, FT or TX data may not present properly given that valueString is a string data type

= OBX-5.1+"-"+OBX-5.2

= OBX-5.1+" "+OBX-5.2+" "+OBX-5.3+" "+OBX-5.4" "OBX-6"

= OBX-5.1+" "+OBX-5.2+" "+OBX-5.3+" "+OBX-5.4" "OBX-6"

Note that OBX-5 and OBX-6 resolve to different components for the same Quantity data type.

= OBX-5.1+" "+OBX-5.2+" "+OBX-5.3+" "+OBX-5.4" "OBX-6"

IF: If line 19 through 23 all fail while OBX-2 = SN

Full guidance on how to populate SampledData based on a single vector or an array will be provided in a future version based on interest. Please submit a JIRA if you are interested.

= "https://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.valueAttachment"

We are for now addressing Base64 that cover .pdf, pictures and other binaries. If somebody does this, we will address those.

= "https://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.valueAttachment"

To be resolved when we resolve DocumentReference and valueAttachment

Note that OBX-5 and OBX-6 resolve to different components for the same Quantity data type.

Note that OBX-5 and OBX-6 resolve to different components for the same Quantity data type.

If OBX-7 is sufficiently parseable, then the low, high, type, appliesTo, and/or age may be used.

= "http://hl7.org/fhir/StructureDefinition/observation-nature-of-abnormal-test"

= "http://hl7.org/fhir/StructureDefinition/alternate-codes"

= "X"

= "http://terminology.hl7.org/CodeSystem/v2-0085"

= "not-asked"

= "http://terminology.hl7.org/CodeSystem/data-absent-reason"

We are mapping this to an identifier considering the definition (used for a unique identifier of the producer), although that does not fit the use of the CWE data type in HL7 v2. Depending on context (e.g., US CLIA or IHE LTW, or ILW) this may reflect a location (US CLIA) or an organization (IHE LTW or ILW).

= "responsibleObserver"

= "http://terminology.hl7.org/CodeSystem/practitioner-role"

The cardinality of Observation.method is 0..1 while the source allows for multiple methods. As we are not aware of anybody populating multiples in HL7 v2, we did not provide further mapping guidance. If you need to support multiples, please submit a gForge to OO for the HL7 v2 to FHIR mapping Implementation Guide.

"http://hl7.org/fhir/StructureDefinition/observation-analysis-date-time"

The cardinality of Observation.bodySite is 0..1 while the source allows for multiple body sites. As we are not aware of anybody populating multiples in HL7 v2, we did not provide further mapping guidance. If you need to support multiples, please submit a gForge to OO for the HL7 v2 to FHIR mapping Implementation Guide.

= "FILL"

= "MDIR"

= "http://terminology.hl7.org/CodeSystem/v2-0912"

= "http://hl7.org/fhir/StructureDefinition/observation-structure-type"

The sub type was necessary in v2 to distinguish purpose of the observation when it appears in a message in the same group (e.g., answers to ask at order entry questions with actual results ). Within FHIR flagging the observation may not be necessary, but that is not yet clear. Until then, we will keep the thought of needing an extension, but not create it yet.

= "http://hl7.org/fhir/StructureDefinition/observation-structure-type"

= "http://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.specimen"

Note that in v2 messages the observations that a calculated observation is derived from on and involve multiple specimens are typically not included with the message. To enable relating the calculated observation to the correct specimens it relates to, the v2 message should include the originating observations that in turn use OBX-33 to link to the correct specimens. Without that, and if there are multiple specimens in OBX-33, there is no standard method to correctly associate the observation with the correct specimens. The implementer will have to devise an appropriate method for that in their context.

= "http://hl7.org/fhir/5.0/StructureDefinition/extension-Observation.specimen"