This page is part of the FHIR Specification (v4.5.0: R5 Preview #3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3
Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Not linked to any defined compartments |
Raw XML (canonical form + also see XML Format Specification)
SNOMED CT / ICD-10 mapping example (id = "103")
<?xml version="1.0" encoding="UTF-8"?> <ConceptMap xmlns="http://hl7.org/fhir"> <id value="103"/> <text> <status value="extensions"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2> SNOMED CT to ICD-10-CM mappings for fracture of ulna (http://hl7.org/fhir/ConceptMap/103)</h2> <p> Mapping from http://snomed.info/sct?fhir_vs to http://hl7.org/fhir/sid/icd-10-us</p> <p> DRAFT (not intended for production usage). Published on 2012-06-13 by HL7, Inc (FHIR project team (example): <a href="http://hl7.org/fhir">http://hl7.org/fhir</a> ). Creative Commons 0 </p> <div> <p> Example rule-based mappings between SNOMED CT to ICD-10-CM for fracture of ulna</p> </div> <br/> <table class="grid"> <tr> <td> <b> Source Code</b> </td> <td> <b> Relationship</b> </td> <td> <b> Destination Code</b> </td> <td> <b> Comment</b> </td> </tr> <tr> <td> 263204007 (Fracture of shaft of ulna)</td> <td> <a href="codesystem-concept-map-relationship.html#source-is-broader-than-target">maps to narrower target</a> </td> <td> S52.209A</td> <td> The target mapping to ICD-10-CM is 'source-is-broader-than-target', since additional patient data on the encounter (initial vs. subsequent) and fracture type is required for a valid ICD-10-CM mapping.</td> </tr> <tr> <td/> <td> <a href="codesystem-concept-map-relationship.html#source-is-broader-than-target">maps to narrower target</a> </td> <td> S52.209D</td> <td> The target mapping to ICD-10-CM is 'source-is-broader-than-target', since additional patient data on the encounter (initial vs. subsequent), fracture type and healing (for subsequent encounter) is required for a valid ICD-10-CM mapping.</td> </tr> </table> </div> </text> <url value="http://hl7.org/fhir/ConceptMap/103"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:uuid:53cd62ee-033e-414c-9f58-3ca97b5ffc3b"/> </identifier> <version value="4.5.0"/> <name value="SNOMED CT to ICD-10-CM mappings for fracture of ulna"/> <status value="draft"/> <experimental value="true"/> <date value="2012-06-13"/> <publisher value="HL7, Inc"/> <contact> <name value="FHIR project team (example)"/> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> </contact> <description value="Example rule-based mappings between SNOMED CT to ICD-10-CM for fracture of ulna"/> <jurisdiction> <coding> <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="840"/> <display value="United States of America"/> </coding> </jurisdiction> <purpose value="Show example rule based mappings"/> <copyright value="Creative Commons 0"/> <sourceCanonical value="http://snomed.info/sct?fhir_vs"/> <targetCanonical value="http://hl7.org/fhir/sid/icd-10-us"/> <group> <source value="http://snomed.info/sct"/> <sourceVersion value="March 2015 US Edition"/> <target value="http://hl7.org/fhir/sid/icd-10-us"/> <targetVersion value="2015"/> <element> <code value="263204007"/> <target> <code value="S52.209A"/> <relationship value="source-is-broader-than-target"/> <comment value="The target mapping to ICD-10-CM is 'source-is-broader-than-target', since additional patient data on the encounter (initial vs. subsequent) and fracture type is required for a valid ICD-10-CM mapping."/> </target> </element> <element> <target> <code value="S52.209D"/> <relationship value="source-is-broader-than-target"/> <comment value="The target mapping to ICD-10-CM is 'source-is-broader-than-target', since additional patient data on the encounter (initial vs. subsequent), fracture type and healing (for subsequent encounter) is required for a valid ICD-10-CM mapping."/> </target> </element> </group> </ConceptMap>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.