Stream: cda to fhir
Topic: ValueSet as CodeSystem
Peter Bernhardt (Feb 09 2017 at 18:21):
Question for CDA experts. I'm looking at a customer's CDA that has a section properly identified as vital signs, however, the components are using the OID for the vital signs as the codeSystem rather than LOINC. Is this legal?
Brett Marquard (Feb 09 2017 at 18:28):
creative, but no...
Peter Bernhardt (Feb 09 2017 at 18:29):
Thanks very much, Brett. I figured as much.
Here’s the offending component.
<component>
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.22.4.27" />
<id root="a583c8a5-0e88-4f4b-b89e-8daadfb30863" />
<code code="8480-6" codeSystem="2.16.840.1.113883.3.88.12.80.62" codeSystemName="HITSP Vital Sign Result Type" displayName="BP Systolic" />
<text><th align='left' scope="row" >BP Systolic</th><td>June 17, 2016 10:00:00 AM CDT</td><td><content ID='vitS1'>128 mm[Hg]</content></td></text>
<statusCode code="completed" />
<effectiveTime value="20160617100000-0500" />
<value xsi:type="PQ" value="128.0" unit="mm[Hg]" />
</observation>
</component>
Igor Sirkovich (Feb 13 2017 at 20:39):
@Peter Bernhardt This is a common mistake when people use Value Set rather Code System OIDs in HL7v3 & CDA messages. Value Set OIDs should never appear there, but many people get hard time understanding the difference between these 2 concepts.
Last updated: Apr 12 2022 at 19:14 UTC