Publication Build: This will be filled in by the publication tooling

• Content
• Detailed Descriptions
• Mappings
• JSON
• History

Resource Profile: ObservationImagingResultEcho - Mappings

Draft as of 2025-06-13

Mappings for the ObservationImagingResultEcho resource profile.

Mappings for Veterans Health Information Systems Technology and Architecture (VistA) ()

ObservationImagingResultEcho
Observation
identifier
system	1617-1: fixed value = http://va.gov/identifiers/$Sta3n/691	generated from mapParameter line 1
value	1617: source value based on ECHO - IEN (691-.001)
status	1621: terminologyMaps using VF_ImageStatus on ECHO - RELEASE CODE (691-1506)
category (imaging)	1624: fixed value = http://terminology.hl7.org/CodeSystem/observation-category#imaging
code	2194: target not supported	auto added because of must-support
subject	1631: reference based on ECHO - MEDICAL PATIENT > MEDICAL PATIENT - NAME (691-1 > 690-.01)
effective[x] (effectiveDateTime)	1634: source value based on ECHO - DATE/TIME (691-.01)
issued	1637: source value based on ECHO - DATE OF VERIFIED (691-1508)
performer	1640: reference based on ECHO - CARDIOLOGY ATTENDING (691-39)
value[x] (valueString)	1643: source value based on ECHO - FINDINGS > FINDINGS - FINDINGS (691-37 > 691.06-.01)	Should Doppler findings be included? (691-34) Can have only 1 value in US Core.
dataAbsentReason	1796: target not supported	Always has data
interpretation	1648: terminologyMaps using VF_ImageInterpretation on ECHO - SUMMARY (691-.03)
note	1650: source value based on ECHO - OTHER CONCLUSION (691-38)

Mappings for Workflow Pattern (http://hl7.org/fhir/workflow)

ObservationImagingResultEcho
Observation	Event
identifier	Event.identifier
basedOn	Event.basedOn
partOf	Event.partOf
status	Event.status
code	Event.code
subject	Event.subject
encounter	Event.context
effective[x]	Event.occurrence[x]
effective[x] (effectiveDateTime)	Event.occurrence[x]
performer	Event.performer.actor

Mappings for SNOMED CT Concept Domain Binding (http://snomed.info/conceptdomain)

ObservationImagingResultEcho
Observation	< 363787002 |Observable entity|
status	< 445584004 |Report by finality status|
code	< 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
value[x]	< 441742003 |Evaluation finding|
value[x] (valueString)	< 441742003 |Evaluation finding|
interpretation	< 260245000 |Findings values|
bodySite	< 123037004 |Body structure|
specimen	< 123038009 |Specimen|
device	< 49062001 |Device|
referenceRange
type	< 260245000 |Findings values| OR < 365860008 |General clinical state finding| OR < 250171008 |Clinical history or observation findings| OR < 415229000 |Racial group| OR < 365400002 |Finding of puberty stage| OR < 443938003 |Procedure carried out on subject|
appliesTo	< 260245000 |Findings values| OR < 365860008 |General clinical state finding| OR < 250171008 |Clinical history or observation findings| OR < 415229000 |Racial group| OR < 365400002 |Finding of puberty stage| OR < 443938003 |Procedure carried out on subject|
component
code	< 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
value[x]	363714003 |Interprets| < 441742003 |Evaluation finding|
interpretation	< 260245000 |Findings values|

Mappings for HL7 v2 Mapping (http://hl7.org/v2)

ObservationImagingResultEcho
Observation	OBX
identifier	OBX.21 For OBX segments from systems without OBX-21 support a combination of ORC/OBR and OBX must be negotiated between trading partners to uniquely identify the OBX segment. Depending on how V2 has been implemented each of these may be an option: 1) OBR-3 + OBX-3 + OBX-4 or 2) OBR-3 + OBR-4 + OBX-3 + OBX-4 or 2) some other way to uniquely ID the OBR/ORC + OBX-3 + OBX-4.
use	N/A
type	CX.5
system	CX.4 / EI-2-4
value	CX.1 / EI.1
period	CX.7 + CX.8
assigner	CX.4 / (CX.4,CX.9,CX.10)
basedOn	ORC
partOf	Varies by domain
status	OBX-11
code	OBX-3
subject	PID-3
focus	OBX-3
encounter	PV1
effective[x]	OBX-14, and/or OBX-19 after v2.4 (depends on who observation made)
effective[x] (effectiveDateTime)	OBX-14, and/or OBX-19 after v2.4 (depends on who observation made)
issued	OBR.22 (or MSH.7), or perhaps OBX-19 (depends on who observation made)
performer	OBX.15 / (Practitioner) OBX-16, PRT-5:PRT-4='RO' / (Device) OBX-18 , PRT-10:PRT-4='EQUIP' / (Organization) OBX-23, PRT-8:PRT-4='PO'
value[x]	OBX.2, OBX.5, OBX.6
value[x] (valueString)	OBX.2, OBX.5, OBX.6
dataAbsentReason	N/A
interpretation	OBX-8
note	NTE.3 (partner NTE to OBX, or sometimes another (child?) OBX)
bodySite	OBX-20
method	OBX-17
specimen	SPM segment
device	OBX-17 / PRT -10
referenceRange	OBX.7
low	OBX-7
high	OBX-7
type	OBX-10
appliesTo	OBX-10
text	OBX-7
hasMember	Relationships established by OBX-4 usage
derivedFrom	Relationships established by OBX-4 usage
component	containment by OBX-4?
code	OBX-3
value[x]	OBX.2, OBX.5, OBX.6
dataAbsentReason	N/A
interpretation	OBX-8
referenceRange	OBX.7

Mappings for RIM Mapping (http://hl7.org/v3)

ObservationImagingResultEcho
Observation	Entity. Role, or Act, Observation[classCode=OBS, moodCode=EVN]
text	Act.text?
contained	N/A
extension	N/A
modifierExtension	N/A
identifier	id
id	n/a
extension	n/a
use	Role.code or implied by context
type	Role.code or implied by context
system	II.root or Role.id.root
value	II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
period	Role.effectiveTime or implied by context
assigner	II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
basedOn	.inboundRelationship[typeCode=COMP].source[moodCode=EVN]
partOf	.outboundRelationship[typeCode=FLFS].target
status	status Amended & Final are differentiated by whether it is the subject of a ControlAct event with a type of "revise"
category	.outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="EVN"].code
category (imaging)	.outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="EVN"].code
code	code
subject	participation[typeCode=RTGT]
focus	participation[typeCode=SBJ]
encounter	inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
effective[x]	effectiveTime
effective[x] (effectiveDateTime)	effectiveTime
issued	participation[typeCode=AUT].time
performer	participation[typeCode=PRF]
value[x]	value
value[x] (valueString)	value
dataAbsentReason	value.nullFlavor
interpretation	interpretationCode
note	subjectOf.observationEvent[code="annotation"].value
bodySite	targetSiteCode
method	methodCode
specimen	participation[typeCode=SPC].specimen
device	participation[typeCode=DEV]
referenceRange	outboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]
id	n/a
extension	n/a
modifierExtension	N/A
low	value:IVL_PQ.low
high	value:IVL_PQ.high
type	interpretationCode
appliesTo	interpretationCode
age	outboundRelationship[typeCode=PRCN].targetObservationCriterion[code="age"].value
text	value:ST
hasMember	outBoundRelationship
derivedFrom	.targetObservation
component	outBoundRelationship[typeCode=COMP]
id	n/a
extension	n/a
modifierExtension	N/A
code	code
value[x]	value
dataAbsentReason	value.nullFlavor
interpretation	interpretationCode
referenceRange	outboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]

Mappings for FiveWs Pattern Mapping (http://hl7.org/fhir/fivews)

ObservationImagingResultEcho
Observation
identifier	FiveWs.identifier
status	FiveWs.status
category	FiveWs.class
category (imaging)	FiveWs.class
code	FiveWs.what[x]
subject	FiveWs.subject[x], FiveWs.subject
focus	FiveWs.subject[x], FiveWs.subject
encounter	FiveWs.context
effective[x]	FiveWs.done[x]
effective[x] (effectiveDateTime)	FiveWs.done[x]
issued	FiveWs.recorded
performer	FiveWs.actor
component
code	FiveWs.what[x]

Mappings for SNOMED CT Attribute Binding (http://snomed.org/attributebinding)

ObservationImagingResultEcho
Observation
code	116680003 |Is a|
value[x]	363714003 |Interprets|
value[x] (valueString)	363714003 |Interprets|
interpretation	363713009 |Has interpretation|
bodySite	718497002 |Inherent location|
specimen	704319004 |Inherent in|
device	424226004 |Using device|
component
value[x]	363714003 |Interprets|
interpretation	363713009 |Has interpretation|