SNOMED CT / ICD-10 mapping example
{
"resourceType" : "ConceptMap",
"id" : "103",
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <h2>SNOMEDCTToICD10CMMappingsForFractureOfUlna (http://hl7.org/fhir/ConceptMap/103)</h2>\n <p>Mapping from http://snomed.info/sct?fhir_vs to (not specified)</p>\n <p>DRAFT (not intended for production usage). Published on 2012-06-13 by HL7, Inc (FHIR project team (example): \n <a href=\"http://hl7.org/fhir\">http://hl7.org/fhir</a>). Creative Commons 0\n </p>\n <div>\n <p>Example rule-based mappings between SNOMED CT to ICD-10-CM for fracture of ulna</p>\n\n </div>\n <br/>\n <p>\n <b>Group 1</b>Mapping from \n <a href=\"http://terminology.hl7.org/4.0.0/CodeSystem-v3-snomed-CT.html\">SNOMED CT International Edition</a> to \n <a href=\"http://terminology.hl7.org/4.0.0/CodeSystem-icd10CM.html\">International Classification of Diseases, 10th Revision, Clinical Modification (ICD-10-CM)</a>\n </p>\n <table class=\"grid\">\n <tr>\n <td>\n <b>Source Code</b>\n </td>\n <td>\n <b>Relationship</b>\n </td>\n <td>\n <b>Target Code</b>\n </td>\n <td>\n <b>Comment</b>\n </td>\n </tr>\n <tr>\n <td>263204007 (Fracture of shaft of ulna)</td>\n <td>\n <a href=\"codesystem-concept-map-relationship.html#source-is-broader-than-target\" title=\"source-is-broader-than-target\">is broader than</a>\n </td>\n <td>S52.209A (Unsp fracture of shaft of unsp ulna, init for clos fx)</td>\n <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>\n </tr>\n <tr>\n <td>263204007 (Fracture of shaft of ulna)</td>\n <td>\n <a href=\"codesystem-concept-map-relationship.html#source-is-broader-than-target\" title=\"source-is-broader-than-target\">is broader than</a>\n </td>\n <td>S52.209D (Unsp fx shaft of unsp ulna, subs for clos fx w routn heal)</td>\n <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>\n </tr>\n </table>\n </div>"
},
"url" : "http://hl7.org/fhir/ConceptMap/103",
"identifier" : [{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:oid:2.16.840.1.113883.4.642.14.7"
},
{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:uuid:53cd62ee-033e-414c-9f58-3ca97b5ffc3b"
}],
"version" : "5.0.0-draft-final",
"name" : "SNOMEDCTToICD10CMMappingsForFractureOfUlna",
"title" : "SNOMED CT to ICD-10-CM mappings for fracture of ulna",
"status" : "draft",
"experimental" : true,
"date" : "2012-06-13",
"publisher" : "HL7, Inc",
"contact" : [{
"name" : "FHIR project team (example)",
"telecom" : [{
"system" : "url",
"value" : "http://hl7.org/fhir"
}]
}],
"description" : "Example rule-based mappings between SNOMED CT to ICD-10-CM for fracture of ulna",
"jurisdiction" : [{
"coding" : [{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "840",
"display" : "United States of America"
}]
}],
"purpose" : "Show example rule based mappings",
"copyright" : "Creative Commons 0",
"sourceScopeCanonical" : "http://snomed.info/sct?fhir_vs",
"group" : [{
"source" : "http://snomed.info/sct",
"target" : "http://hl7.org/fhir/sid/icd-10-cm",
"element" : [{
"code" : "263204007",
"target" : [{
"code" : "S52.209A",
"relationship" : "source-is-broader-than-target",
"comment" : "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."
}]
},
{
"code" : "263204007",
"target" : [{
"code" : "S52.209D",
"relationship" : "source-is-broader-than-target",
"comment" : "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."
}]
}]
}]
}
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.