STARS Implementation Guide - Local Development build (v0.1.0). See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• XML
• JSON
• TTL

Resource Profile: CsiroStarsObservationSupportingInfoProfile - Mappings

Draft as of 2023-04-26

Mappings for the csiro-stars-observation-supportinginfo resource profile.

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

CsiroStarsObservationSupportingInfoProfile
Observation	Event
identifier	Event.identifier
basedOn	Event.basedOn
status	Event.status
code	Event.code
effective[x]	Event.occurrence[x]

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

CsiroStarsObservationSupportingInfoProfile
Observation	< 363787002 |Observable entity|
status	< 445584004 |Report by finality status|
code	< 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
value[x]	< 441742003 |Evaluation finding|
interpretation	< 260245000 |Findings values|
specimen	< 123038009 |Specimen|
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)

CsiroStarsObservationSupportingInfoProfile
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.
basedOn	ORC
status	OBX-11
code	OBX-3
effective[x]	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)
value[x]	OBX.2, OBX.5, OBX.6
dataAbsentReason	N/A
interpretation	OBX-8
note	NTE.3 (partner NTE to OBX, or sometimes another (child?) OBX)
specimen	SPM segment
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)

CsiroStarsObservationSupportingInfoProfile
Observation	Entity. Role, or Act, Observation[classCode=OBS, moodCode=EVN]
text	Act.text?
contained	N/A
extension	N/A
modifierExtension	N/A
identifier	id
basedOn	.inboundRelationship[typeCode=COMP].source[moodCode=EVN]
status	status Amended & Final are differentiated by whether it is the subject of a ControlAct event with a type of "revise"
code	code
effective[x]	effectiveTime
issued	participation[typeCode=AUT].time
value[x]	value
dataAbsentReason	value.nullFlavor
interpretation	interpretationCode
note	subjectOf.observationEvent[code="annotation"].value
specimen	participation[typeCode=SPC].specimen
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)

CsiroStarsObservationSupportingInfoProfile
Observation	clinical.diagnostics
identifier	FiveWs.identifier
status	FiveWs.status
code	FiveWs.what[x]
effective[x]	FiveWs.done[x]
issued	FiveWs.recorded
component
code	FiveWs.what[x]

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

CsiroStarsObservationSupportingInfoProfile
Observation
code	116680003 |Is a|
value[x]	363714003 |Interprets|
interpretation	363713009 |Has interpretation|
specimen	704319004 |Inherent in|
component
value[x]	363714003 |Interprets|
interpretation	363713009 |Has interpretation|