1 Introduction

1.1 Background

SNOMED CT terminology provides a common language that enables a consistent way of indexing, storing, retrieving, and aggregating clinical data across specialties and sites of care.

SNOMED International maintains the SNOMED CT technical design, the content architecture, the SNOMED CT content (includes the concepts table, the descriptions table, the relationships table, a history table, and ICD mappings), and related technical documentation.

1.2 Purpose

This document provides a summarized description of the content changes included in the January 2018 release of SNOMED Clinical Terms^® (SCT) International Release.

It also includes technical notes detailing the known issues which have been identified. These are content or technical issues where the root cause is understood, and the fix has been discussed and agreed, but has yet to be implemented.

This document is available alongside the January 2018 International Edition release.

1.3 Scope

This document is written for the purpose described above and is not intended to provide details of the technical specifications for SNOMED CT or encompass every change made during the release.

1.4 Audience

The audience includes National Release Centers, WHO-FIC release centers, vendors of electronic health records, terminology developers and managers who wish to have an understanding of changes that have been incorporated into the January 2018 International Edition release.

2 Content Development Activity

2.1 Summary

Continuous quality improvement and enhancement of existing content is ongoing based on requests received via the Content Request System (CRS). A review of the pre-coordination patterns that are blocking CRS tickets from progressing has commenced and will continue into 2018. Where decisions on the pattern have been made the CRS requests are being processed according to the outcome of the decision and the normal request management process.

A review of requests currently in the 'In Inception' status in the CRS tool is underway and where it is feasible to progress a request prior to resolving the tracker issue, the request is being identified for progression. Given this work (and the pre-coordination patterns review) the number of requests in 'In Inception' status has decreased by just over 1000. This work will continue into 2018.

The January 2018 International Release has seen a continuation of the work driven by contributions from: Kaiser Permanente Convergent Medical Terminology (CMT), Global Medical Device Nomenclature Agency (GMDNA), World Health Organization (WHO) ICD-11 Beta and International Classification for Nursing Practice ( ICNP®) to add new content to SNOMED CT.  

Additionally, member-identified priority projects, have driven enhancements in the anatomy hierarchy, while other project-driven changes have resulted in new content additions and enhancements to existing content detailed below.

2.2 Content Quality Improvement

4979 new concepts were added

2.2 Content Quality Improvement

4979 new concepts were added

21080 changes were made to existing content

2.2.1 Anatomy 

New anatomy concepts: 571

1. • • 462 new
lateralised
2. • • lateralized body structure concepts and nearly 1000 new
lateralised
3. • • lateralized findings, disorders and procedures. There are over 5,000
lateralised content
4. • • lateralized concepts in SNOMED CT.
     • 30 new concepts
for
5. • • for 736503009 | Structure of mucous membrane of nasal cavity and/or nasal sinus
|,
6. • • (body structure)| and descendants and refined the existing hierarchical relationships.
     • New concepts for transplanted cardiac values and structure of vertebral column and/or spinal cord to support concept modeling from ICD-11 content.

Reviewed and updated IS A relationships for 1,255 skin structure concepts according to the new anatomy model

:

1. • • Identified and added 329 new IS A relationships. 
     • Inactivated 136 redundant or incorrect IS A relationships.

Updates for SEP refsets and Lateralizable body structure refset:

• • • • 42 changes to the SE refset.
      • 4 changes to the SP refset.
      • 42 new members for
    lateralisable
    • • lateralizable body structure refset and 10 inactivations.

2.2.2 Clinical finding

New concepts for clinical findings and disorders: 2005

Work completed on the following Content Projects:

• • • • IHTSDO-418 - 84017003 | Bursitis
    (disorder) with concepts remodeled with primitive parent and changes to relationship groups where required also incorporated review of 128200000|Complex regional pain syndrome
    • • (disorder)
    | and subtypes
    • • .
      • IHTSDO-772 - Suspected - findings / disorders, should be situations.

      • IHTSDO-412 - Intra-operative complication.

3. Work commenced on the following Content Projects:

• • • • IHTSDO-451 - Has definitional manifestation
    : Work has started on remodelling the concepts that are defined in this way. Any existing |Has definitional manifestation | which has a Finding as a value, may be considered for replacement with Interprets/Has interpretation paired values. Any existing |Has definitional manifestation | which has a Disorder as a value may be considered for replacement with suitable IS A relationship.
    • IHTSDO-703 - The inactivation of 'unilateral' concepts with creation of lateralised replacement concepts where not already present in the terminology has commenced. This work will continue into 2018.
    • IHTSDO-614 - Rework hierarchy 441457006|Cyst (disorder)|

4. Other content quality improvements:

• • • • .
      • IHTSDO-703 - Inactivation of 'unilateral' concepts.
      • IHTSDO-614 - Rework hierarchy 441457006|Cyst (disorder)|.

Other content quality improvements:

• • • • Remodel and fully define 63491006|Intermittent claudication (finding) and subtypes.
      • Review and remodel of 128200000|Complex regional pain syndrome (disorder)| and subtypes.
        
      • 7 new laboratory finding concepts added along with 30 changes made to existing laboratory concepts.
      • Revision
    • Remodel and fully define 63491006|Intermittent claudication (finding) and subtypes
    • 7 new laboratory finding concepts added along with 30 changes made to existing laboratory concepts.
    Revision
    • • of spinal injury content - many concepts were primitives and represented as flat list under 26738009|Spinal cord injury without spinal bone injury (disorder)|. This sub-hierarchy has been reviewed and 85 concepts have been remodeled. Most concepts have been defined based on complete, incomplete injuries and levels. These changes have also addressed the reported duplication issues.
      • Remodel 3238004|Pericarditis (disorder)| and subtypes with primitive parent and changes to relationship groups where required to achieve consistency, approximately 100 concepts were remodeled.

2.2.3 Convergent Medical Terminologies (CMT)

New CMT concepts: 766

These were added across 3 domains:

• • • • CMT Neurology
      • CMT Musculoskeletal
      • CMT Radiology

2.2.4 Procedure Hierarchy

New concepts for procedure hierarchy: 911

Diagnostic Imaging - approximately 363 new concepts added including:

1. • • MRI 53
     • CT 38
     • Plain X-ray 15
     • Fluoroscopy 73
     • Imaging guided procedure (various modalities) 102
     • Ultrasonography 82

Work completed on the following Content Projects: 

• • • • IHTSDO-111 - Review of hierarchy 23968004|Colectomy (procedure) with inactivation of duplicate content, concepts remodeled with primitive parent and changes to relationship groups where required.
      • IHTSDO-691 - Remodel content 243185007 | Advanced life support (procedure) and subtypes.

4. Other content quality improvements:

1. • • Remodel and fully define 180081001|Correction of congenital deformity of hand (procedure)| and its descendants.

     • Fixed MRCM rule violation for 156 Evaluation procedures and removed Observable entities as values for Component Attribute.

     • Care program approach - realm specific concepts inactivated from International release.

2.2.5 Collaboration/Harmonization Projects

2.2.5.1 Orphanet

As a result of collaboration with Orphanet (http://www.orpha.net/consor/cgi-bin/index.php) 12 new SNOMED CT concepts have been created to represent rare diseases in the disorder hierarchy.

2.2.5.2 ICD-11 Harmonization plan

Added 1100 concepts equivalent to ICD-11 Mortality and Morbidity Statistics (ICD-11-MMS codes) codes; review and additions are ongoing based on updates to to ICD-11-MMS.

2.2.

5.3 LOINC

105 new SNOMED CT concepts created for LOINC - SNOMED collaboration project.

2.2.

5.4 International Classification for Nursing Practice ( ICNP®)

74 new SNOMED CT concepts created as a requirement for the ICNP-SNOMED CT Equivalence Table.

2.2.5.

5 Global Medical Device Nomenclature Agency (GMDNA)

165 new SNOMED CT concepts created in the Physical object hierarchy to support the GMDN collaboration agreement.

2.2.

6 Morphologic Abnormality

New concepts added: 22

There are 8 updates for the ICD-O maps in 2018 January release.

2.2.

7 Observable Entity

New concepts added: 52

Content quality improvements:

• • • • Inactivated 704318007 |Property type (attribute)| and replaced it with 370130000 |Property (attribute) for 162 modeled Observable entity concepts which had previously used 704318007 |Property type (attribute)|. Updated related MRCM rules and Editorial Guide.
        

2.2.

8 Organism

New organism concepts added: 236

Changes to 29 existing concepts in the organism hierarchy.

2.2.

9 Pharmaceutical / biologic product

Added >??????? new descriptions with "medication" where "drug" was already used

Summary of changes

2.2.11 Physical objects

2.2.12 Situation with Explicit Context

2.2.10 Veterinary Extension

2 concepts were moved to the Veterinary Extension. 

2.4 SNOMED CT derived products

2.4.1 ICD-10 map

The SNOMED CT to the International Statistical Classification of Diseases and Related Health Problems, Tenth Revision (© World Health organisation 1994) 2016 Version map (SNOMED CT to ICD-10 Map) is included in the SNOMED CT International release as a Baseline. The SNOMED CT to ICD-10 Map was created to support the epidemiological, statistical and administrative reporting needs of SNOMED International member countries and WHO Collaborating Centres.

The SNOMED CT to ICD-10 Map is released in Release Format 2 (RF2) only. It is located in the file der2_iisssccRefset_ExtendedMapFull_INT_20170131.txt, which is in the Map folder under Refset, in each of the three RF2 Release Type folders.

The SNOMED CT to ICD-10 Map is released as Refset 447562003 |ICD-10 complex map reference set (foundation metadata concept)|.

2.4.1.1 Content development activity summary

The map is a directed set of relationships from SNOMED CT source concepts to ICD-10 target classification codes.  The SNOMED CT source domains for the MAP are limited to subtypes of 404684003 |clinical finding|, 272379006 |event| and 243796009 |situation with explicit context|.  The target classification codes are ICD-10 2016 release.

2.4.1.2 Mapped content for January 2018

The map provided for the January 2018 release has been updated, and now represents a complete map from SNOMED CT International release to ICD-10 2016 version.

• 2207 new concepts added

We would welcome feedback on any issues that users of the map may detect when using the map. Issues should be submitted via mapping@snomed.org

2.4 SNOMED CT derived products

2.4.1 ICD-10 map

The SNOMED CT to the International Statistical Classification of Diseases and Related Health Problems, Tenth Revision (© World Health organisation 1994) 2016 Version map (SNOMED CT to ICD-10 Map) is included in the SNOMED CT International release as a Baseline. The SNOMED CT to ICD-10 Map was created to support the epidemiological, statistical and administrative reporting needs of SNOMED International member countries and WHO Collaborating Centres.

The SNOMED CT to ICD-10 Map is released in Release Format 2 (RF2) only. It is located in the file der2_iisssccRefset_ExtendedMapFull_INT_20170131.txt, which is in the Map folder under Refset, in each of the three RF2 Release Type folders.

The SNOMED CT to ICD-10 Map is released as Refset 447562003 |ICD-10 complex map reference set (foundation metadata concept)|.

2.4.1.1 Content development activity summary

The map is a directed set of relationships from SNOMED CT source concepts to ICD-10 target classification codes.  The SNOMED CT source domains for the MAP are limited to subtypes of 404684003 |clinical finding|, 272379006 |event| and 243796009 |situation with explicit context|.  The target classification codes are ICD-10 2016 release.

2.4.1.2 Mapped content for January 2018

The map provided for the January 2018 release has been updated, and now represents a complete map from SNOMED CT International release to ICD-10 2016 version.

• • 2207 new concepts added

We would welcome feedback on any issues that users of the map may detect when using the map. Issues should be submitted via mapping@snomed.org

3 Technical notes

3.1 Known Issues

Known Issues are content or technical issues where the root cause is understood, and the resolution has been discussed and agreed but has yet to be implemented.  This can be due to a number of reasons, from lack of capacity within the current editing cycle, to the risk of impact to the stability of SNOMED CT if the fix were to be deployed at that stage in the Product lifecycle.  

For the Snomed CT January 2018 International edition, the following Known Issues were identified, and agreed to be resolved in the next editing cycle (to be published in July 2018):

3.2 Resolved Issues

Resolved issues are Known Issues which were not fixed as part of the previous release lifecycle, but which have now been resolved in the latest release - in this case the January 2018 International Edition.  They can also be issues found during the Alpha and Beta testing of the current release, which were resolved before the final deployment of the associated Member release.  Finally they can be issues which were reported or found during the testing phase, but which have been closed without any action taken.  

The Resolved Issues for the Snomed CT January 2018 International edition can be found here

3 Technical notes

3.1 Known Issues

Known Issues are content or technical issues where the root cause is understood, and the resolution has been discussed and agreed but has yet to be implemented.  This can be due to a number of reasons, from lack of capacity within the current editing cycle, to the risk of impact to the stability of SNOMED CT if the fix were to be deployed at that stage in the Product lifecycle.  

For the Snomed CT January 2018 International edition, the following Known Issues were identified, and agreed to be resolved in the next editing cycle (to be published in January 2018):

3.

Resolved issues are Known Issues which were not fixed as part of the previous release lifecycle, but which have now been resolved in the latest release - in this case the January 2018 International Edition.  They can also be issues found during the Alpha and Beta testing of the current release, which were resolved before the final deployment of the associated Member release.  Finally they can be issues which were reported or found during the testing phase, but which have been closed without any action taken.  

The Resolved Issues for the Snomed CT January 2018 International edition can be found here:

3.3 Technical updates

3.3.1  Update to case significance assignment, in line with the RF2 specification

3 Technical updates

3.3.1  Association Reference set naming convention

The naming convention of the Association Reference file is being improved for the January 2018 International Edition.

It will no longer be named using this convention:

'der2_cRefset_AssociationReferenceSnapshot_INT_[date].txt'

Instead it will be named as follows:

'der2_cRefset_AssociationSnapshot_INT_[date].txt'

Therefore, the three files in the January 2018 International Edition release package will be called:

• der2_cRefset_AssociationDelta_INT_20180131.txt
  
• der2_cRefset_AssociationFull_INT_20180131.txt
  
• der2_cRefset_AssociationSnapshot_INT_20180131.txt
  

3.3.2  RF2 package naming convention

In order to differentiate between the different versions of the Production release package, the fourth element in the naming convention of will now state "MEMBER" for Member releases, and "PRODUCTION" for the final Public releases.

Thus the Member release published on 31st December 2017 for the January 2018 International Edition will be called:

SnomedCT_InternationalRF2_MEMBER_20180131T120000Z.zip

Whilst the Public release published on 31st January 2018 for the January 2018 International Edition will be called:

SnomedCT_InternationalRF2_PRODUCTION_20180131T120000Z.zip 

3.3.3  RF2 package format

For future reference, the RF2 package convention dictates that it contains all relevant files, regardless of whether or not there is content to be included in each particular release.  Therefore, the package contains a mixture of files which contain both header rows and content data, and also files that are intentionally left blank (including only a header record).  The reason that these files are not removed from the package is to draw a clear distinction between

1. ...files that have been deprecated (and therefore removed from the package completely), due to the content no longer being relevant to RF2 in this or future releases, and 
2. ...files that just happen to contain no data in this particular release (and are therefore included in the package but left blank, with only a header record), but are still relevant to RF2, and could therefore potentially contain data in future releases.

This allows users to easily distinguish between files that have purposefully been removed or not, as otherwise if files in option 2 above were left out of the package it could be interpreted as an error, rather than an intentional lack of content in that release.

3.3.

4  Early visibility of impending change in the

July 2018 International edition

Please see the following page for details of all upcoming changes planned for January July 2018 and beyond:  January 2020 Early Visibility Release Notices - Planned improvements changes to upcoming SNOMED International Release packages