- SNOMED CT United States Edition
- SNOMED CT Latest Version
- Machine Readable Concept Model of SNOMED CT
- Clinical Terminology
- SNOMED CT
- Systematized Nomenclature of Medicine Clinical Terms
- Healthcare Terminology
- Electronic Health Records
- Machine Readable Concept Model
SNOMED Clinical Terminology to ICD-10-CM Full Map
The purpose of the SNOMED CT to ICD-10-CM map is to support semi-automated generation of ICD-10-CM codes from clinical data encoded in SNOMED CT for reimbursement and statistical purposes.
Get The Data
- ResearchNon-Commercial, Share-Alike, Attribution Free Forever
- CommercialCommercial Use, Remix & Adapt, White Label Log in to download
This dataset, alternatively named in SNOMED CT as “Extended map reference set” enables representation of maps where each SNOMED CT concept may map to one or more codes in a target scheme. It supports the general set of mapping data required to enable a target code to be selected at run-time from a number of alternate codes. It supports target code selection by accommodating the inclusion of machine readable rules and/or human readable advice. Extended map type reference set adds an additional field to allow categorization of maps.
SNOMED CT (SNOMED Clinical Terminology) provides a common language that assists with the electronic exchange of clinical health information. It enables a consistent way of indexing, storing, retrieving, and aggregating clinical data across specialties and sites of care. SNOMED CT Can be mapped to other coding systems, such as ICD-10, which helps facilitate semantic interoperability.
A Full release contains every version of every component that has ever been released prior to or in the specified Edition. This release provides a full historical record and can be used to obtain views of the state of any component at any point in time since its first release.
The March 2020 release contains relevant COVID-19 concepts including any applicable changes to descriptions. With this interim release, 24 records have been added, plus core concept descriptions added back in referencing March 2020.
With this release, clinicians, researchers and administrators globally are able to code, analyze and plan to address the Coronavirus effort with the most up to date terminology.
About this Dataset
John Snow Labs; International Health Terminology Standards Development Organisation (IHTSDO), U.S. National Library of Medicine (NLM);
|Source License URL|
|Source License Requirements||
Clinical Terminology, SNOMED CT, IHTSDO, Systematized Nomenclature of Medicine Clinical Terms, Healthcare Terminology, Electronic Health Records, Machine Readable Concept Model
SNOMED CT United States Edition, SNOMED CT Latest Version, Machine Readable Concept Model of SNOMED CT
|Reference_Set_Member_Id||A field, uniquely identifying this reference set member. Different versions of a reference set member share the same ID but have different Effective_Date. This allows a reference set member to be modified or made inactive (i.e. removed from the active set) at a specified time.||string||required : 1|
|Effective_Date||The inclusive date at which this version of the identified reference set member became the current version.||date||required : 1|
|Is_Active||The state of the identified reference set member as at the specified Effective_Date. If active= true, the reference set member is part of the current version of the set, if active=false, the reference set member is not part of the current version of the set.||boolean||required : 1|
|Module_Id||Identifies the SNOMED CT module that contains this reference set member as at the specified Effective_Date.||integer||level : Nominalrequired : 1|
|Refset_Id||Identifies the reference set to which this reference set member belongs.||integer||level : Nominalrequired : 1|
|Referenced_Component_Id||The identifier of the source component of the association.||integer||level : Nominalrequired : 1|
|Map_Group||An integer, grouping a set of complex map records from which one may be selected as a target code. Where a SNOMED CT concept maps onto 'n' target codes, there will be 'n' groups, each containing one or more complex map records.||integer||level : Nominalrequired : 1|
|Map_Priority||Within a Map_Group, the Map_Priority specifies the order in which complex map records should be checked. Only the first map record meeting the run - time selection criteria will be taken as the target code within the group of alternate codes.||integer||level : Nominalrequired : 1|
|Map_Rule||A machine-readable rule, (evaluating to either 'true' or 'false' at run-time) that indicates whether this map record should be selected within its map group.||string||required : 1|
|Map_Advice||Human-readable advice, that may be employed by the software vendor to give an end-user advice on selection of the appropriate target code from the alternatives presented to him within the group.||string||required : 1|
|Map_Target||The target code in the target terminology, classification or code system.||string||-|
|Correlation_Id||It is the SNOMED CT source code to target map code correlation value in the metadata hierarchy, identifying the correlation between the SNOMED CT concept and the target code.||integer||level : Nominalrequired : 1|
|Map_Category_Id||Identifies the SNOMED CT concept in the metadata hierarchy which represents the Map Category for the associated map member. The categories vary for different target code systems||integer||level : Nominalrequired : 1|
|Reference Set Member Id||Effective Date||Is Active||Module Id||Refset Id||Referenced Component Id||Map Group||Map Priority||Map Rule||Map Advice||Map Target||Correlation Id||Map Category Id|
|80004cdf-a114-59c8-88a2-b6f0283acf4f||2018-03-01||True||5991000124107||6011000124106||128041000119107||1||1||IFA 721617001 | Primary adenocarcinoma of lower third of esophagus due to Barrett esophagus |||IF PRIMARY ADENOCARCINOMA OF LOWER THIRD OF ESOPHAGUS DUE TO BARRETT ESOPHAGUS CHOOSE K22.70 | MAP OF SOURCE CONCEPT IS CONTEXT DEPENDENT||K22.70||447561005||447639009|
|80007b64-5a60-5556-88ce-22ef540a3ea5||2018-03-01||True||5991000124107||6011000124106||281801000009108||2||2||OTHERWISE TRUE||ALWAYS B96.89||B96.89||447561005||447637006|
|80009454-5531-5f78-b7c9-d288f2346d83||2015-07-31||True||449080006||447562003||301327002||1||1||TRUE||MAP SOURCE CONCEPT CANNOT BE CLASSIFIED WITH AVAILABLE DATA||447561005||447638001|
|80009454-5531-5f78-b7c9-d288f2346d83||2019-01-31||False||449080006||447562003||301327002||1||1||TRUE||MAP SOURCE CONCEPT CANNOT BE CLASSIFIED WITH AVAILABLE DATA||447561005||447638001|
|8000fff7-d0ac-5ad4-82eb-f8e0a37ebfc7||2018-03-01||True||5991000124107||6011000124106||292278006||1||1||TRUE||ALWAYS T43.595? | CONSIDER ADDITIONAL CODE TO IDENTIFY SPECIFIC CONDITION OR DISEASE | EPISODE OF CARE INFORMATION NEEDED | POSSIBLE REQUIREMENT FOR AN EXTERNAL CAUSE CODE||T43.595?||447561005||447637006|
|8000fff7-d0ac-5ad4-82eb-f8e0a37ebfc7||2019-03-01||True||5991000124107||6011000124106||292278006||1||1||TRUE||ALWAYS T43.595? | CONSIDER ADDITIONAL CODE TO IDENTIFY SPECIFIC CONDITION OR DISEASE | EPISODE OF CARE INFORMATION NEEDED||T43.595?||447561005||447637006|
|80010c58-f11f-572f-98f9-852cd301d5c0||2014-01-31||True||449080006||447562003||291710005||2||1||TRUE||ALWAYS X44 | POSSIBLE REQUIREMENT FOR PLACE OF OCCURRENCE||X44||447561005||447637006|