1. Introduction

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. The SNOMED CT US Edition is a combination of the full July 2024 SNOMED CT International Edition and the US Extension of SNOMED CT.

The International Health Terminology Standards Development Organisation (IHTSDO^®), trading as 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. The SNOMED CT US Edition is developed and maintained by the United States National Library of Medicine and is available to authorized Unified Medical Language System (UMLS) Metathesaurus Licensees. This material includes SNOMED CT which is used by permission of the IHTSDO. All rights reserved.

SNOMED CT was originally created by the College of American Pathologists. "SNOMED" and "SNOMED CT" are registered trademarks of IHTSDO. You must have a UMLS Metathesaurus license to access SNOMED CT US Edition data files. License information is available from NLM (https://www.nlm.nih.gov/healthit/snomedct/snomed_licensing.html). 

1.1. Background

This document provides a summarized description of the content changes included in the September 2024 release of the SNOMED Clinical Terms® US Edition.

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 as a web resource as well as alongside the September 2024 US Edition release (https://www.nlm.nih.gov/healthit/snomedct/us_edition.html). 

1.2. 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. These Release Notes should be used in combination with the SNOMED CT July 2024 International Edition Release notes. 

2. Content Development Activity 

2.1. Summary

The September 2024 SNOMED CT US Edition marks the fourteenth release with content authoring tooling and release production provided by SNOMED International Managed Service. Quality assurance of the release was completed by both NLM and SNOMED International. Additionally, in October 2017, NLM sunset the United States SNOMED CT Content Request System and migrated to the SNOMED International hosted and maintained US CRS (https://us-request.ihtsdotools.org). 

2.1.1. September 2024 US Edition of SNOMED CT Statistics 

These statistics include the active content from the July 2024 International Edition and the September 2024 US Edition.

These statistics include the content from the September 2024 US Extension.

2.2.  Quality Initiative

The Quality Initiative (QI) project is the implementation of the Quality Strategy. After a successful pilot project for the July 2018 release the next stage has been implemented for subsequent releases including July 2024.

Quality improvement tasks are being deployed to improve internal structural consistency and ensure compliance with editorial policy related to the stated modeling of content. Additionally, correction or addition of defining relationships is being carried out to accurately reflect current clinical knowledge and ensure the semantic reliability of descriptions associated with a concept. 

To see the QI improvement tasks from the July 2024 International Edition, please see the July 2024 International Edition release notes.

The following QI tasks have been undertaken and/or completed in the US Extension:

2.2.1. Concepts used for modeling promoted to the International Edition

The US Extension contained a small number of concepts in the body structure (11 Concepts) and Morphologic Abnormality (17 concepts). These concepts were reviewed and, where possible, promoted to the International Edition. Concepts not eligible for promotion or used in modeling of other concepts were inactivated.

2.2.2. Pressure Injury/ulcer description updates

Several pressure injury concepts in the US extension were original modeled to include a synonym for pressure ulcer for non-stageable and stage I concepts. This does not align with current editorial policy. The erroneous descriptions have been inactivated.

2.2.3. Proximal and intermediate proximal Primitive modeling

Concepts modeled with a sufficiently defined IS A parent concept have been reviewed and modeling updates implemented to transition as many of these concepts to proximal or intermediate proximal primitive model as possible. This work will be completed on an ongoing basis as changes are made to the International Edition.

2.2.4. Exposure to <x> modeling updates

Approximately 21 US Extension concepts representing Exposure to <substance> have been remodeled to include a causative agent attribute relationship.

2.2.5.  Procedure declined/refused description update

Procedure declined concepts contained within the situation with explicit context hierarchy were reviewed and descriptions updated to align with current editorial policy. The fully specified name (FSN) was updated to represent “procedure <x> declined” with a synonym of “procedure <x> refused”. 

2.2.6. Microbiology Project Group work

Work continues by SNOMED International to promote concepts from the 415671008 |Domain Eukarya (organism)| hierarchy from the four participating national extensions. Work is scheduled to be completed by December 2024.

2.3. SNOMED CT derived products 

2.3.1. SNOMED CT to ICD-10-CM 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. All current pre-coordinated SNOMED CT concepts from the US Edition (US Extension + International release) within three hierarchies, (Clinical findings, Events, and Situations with Explicit Context) are potentially in scope for mapping to ICD-10-CM. 

The SNOMED CT to ICD-10-CM map is released in RF2 format within the US Edition, as well as a standalone download (https://www.nlm.nih.gov/research/umls/mapping_projects/snomedct_to_icd10cm.html). The map is also available in a human readable format (tls_Icd10cmHumanReadableMap_US1000124_YYYYMMDD.tsv) contained within a standalone download - SNOMED_CT_to_ICD-10-CM_Resources_YYYYMMDD.zip.

The SNOMED CT to ICD-10-CM map is released as Refset 6011000124106 | ICD-10-CM extended map reference set (foundation metadata concept)|. The map data are in the file xder2_iisssccRefset_ExtendedMapSnapshot_US1000124_YYYYMMDD.txt, which is in the Map folder under Refset in the Snapshot Release Type folder. 

PLEASE NOTE: Starting with the 2019 September SNOMED CT US Edition (20190301) release, the SNOMED CT to ICD-10-CM map refset data will be maintained as per the SNOMED CT RF2 specifications. 

Additional map refset information can be found in the SNOMED CT to ICD-10-CM Release Notes (doc_Icd10cmMapReleaseNotes_Current-en-US_US1000124_YYYYMMDD.pdf) found in the standalone download or online. Technical information (doc_Icd10cmMapTechnicalSpecifications_Current-en-US_US1000124_YYYYMMDD.pdf) for the map can also be found in the standalone download. 

On September 26, 2019, an updated version of the map (6011000124106 | ICD-10-CM complex map reference set (foundation metadata concept)| ) was released. This updated version included an appending of the previously released mapping refset data, originally pulled from the 20190301 release. The newly released version, which includes all of the previously released data, now includes 260,749 mapped records. This is now considered the baseline for the SNOMED CT to ICD-10-CM map. 

2.3.2. Route of administration

The NLM maintained Route of Administration reference set (442311000124105 | Route of administration reference set) has been in static status since 2014 September US Edition release (20140901) and was deprecated from the US Edition release package as of the September 2023 US Edition release onwards. The Route of Administration reference set is located in the file der2_Refset_Simple(Snapshot, Delta, Full)_US1000124_YYYYMMDD.txt, which is in the Content folder under Refset, in each of the three RF2 Release Type folders. The refset contains a set of terms related to the location of administration for clinical therapeutics. The purpose of the Route of Administration refset is to define a portion of which can be used in the Drug Listing section of Structured Product Labeling (SPL), or for documentation and encoding of clinical information regarding substance administrations. Only concepts that are subtypes of the concept 284009009 | Route of administration value (qualifier value) are included in the refset.

The concept "442311000124105 |Route of administration reference set (foundation metadata concept)|" + relates components (including the refsetDescriptor record) remains active, however all 144 records that comprise this refset are inactivated in the SimpleRefset file: der2_Refset_SimpleSnapshot_US1000124_20230901.txt

In order to preserve the historical audit trail within the US Edition release package, the records have been inactivated (set the "active=0") rather than being deleted from the package completely.

The Route of Administration concepts are maintained as an intensional value set in the NLM Value Set Authority Center (VSAC) (https://vsac.nlm.nih.gov/valueset/2.16.840.1.113762.1.4.1018.98/expansion). Users are required to have a UMLS account to access VSAC. If you don't have a UMLS account, you can request one here: https://uts.nlm.nih.gov/uts/signup-login

2.3.3. Transitive closure file

NLM provides a transitive closure script and generated transitive closure table within the SNOMED CT US Edition release. The transitive closure is the complete set of relationships between every concept and each of its super-type concepts (parents and ancestors). The transitive closure files can be used to support SQL queries when created and stored as a table in a relational database. If applied in a full release, it will contain the full history and allow for subsumption queries to be applied based on any release. The NLM transitive closure script provides a comprehensive view of all of the supertype ancestors of a concept derived by traversing all the 116680003 | is a | relationships between that concept and the root concept. The transitive closure table represents the transitive closure of the 116680003 | is a | relationships of all active concepts. NLM provides the transitive closure table in the US Edition release to provide support for easier implementation and a reference against which to check alternative algorithms. 

As of the September 2020 release, the Transitive Closure script, tls2_TranstiveClosure_US1000124_YYYYMMDD.pl, and the Transitive Closure table res2_TransitiveClosure_US1000124_YYYYMMDD.txt, are located in a separate bundled zip file (SnomedCT_TransitiveClosureResourcesRF2_PRODUCTION_YYYYMMDDT120000Z.zip) on the NLM US Edition page. For the table, the superTypeId is the id of the concept playing the supertype role, set to an Identifier of a concept. The subTypeId - Id of the concept playing the subtype role. Set to an Identifier of a concept. 

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.

In addition to the Known Issues reported by the IHTSDO for SNOMED CT International Edition (SNOMED CT July 2024 International Edition Release notes), the following are Known Issues for the SNOMED CT September 2024 US Edition that have been identified and will be resolved in the next editing and production cycle: 

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 for this September 2024 US Edition. These can be issues found during the Pre-Production or Production phases of the testing of the current release, which were resolved before the final deployment of the final production release. Finally these can be issues which were reported or found during the testing phase, but which have been closed without any action taken. 

In addition to the Resolved Issues reported by the IHTSDO for SNOMED CT International Edition (SNOMED CT July 2024 International Edition Release notes), the following Resolved Issues for the SNOMED CT September 2024 US Edition:

3.3. Technical Updates

In addition to the Technical Updates reported in the following monthly Release Notes:

• • https://confluence.ihtsdotools.org/display/RMT/SNOMED+CT+January+2024+International+Edition+-+SNOMED+International+Release+notes
  • https://confluence.ihtsdotools.org/display/RMT/SNOMED+CT+February+2024+International+Edition+-+SNOMED+International+Release+notes 
  • https://confluence.ihtsdotools.org/display/RMT/SNOMED+CT+March+2024+International+Edition+-+SNOMED+International+Release+notes 
  • https://confluence.ihtsdotools.org/display/RMT/SNOMED+CT+April+2024+International+Edition+-+SNOMED+International+Release+notes 
  • https://confluence.ihtsdotools.org/display/RMT/SNOMED+CT+May+2024+International+Edition+-+SNOMED+International+Release+notes 
  • https://confluence.ihtsdotools.org/display/RMT/SNOMED+CT+June+2024+International+Edition+-+SNOMED+International+Release+notes 
  • https://confluence.ihtsdotools.org/display/RMT/SNOMED+CT+July+2024+International+Edition+-+SNOMED+International+Release+notes 

...the following technical updates pertain to the US Edition:

3.3.1. RF2 package naming conventions

3.3.1.1. US Edition package naming convention

Please be aware that as of the March 2023 Release of the US Edition onwards, the RF2 package naming convention has been changed in order to bring it in line with the naming standards across all Managed Service products. This is being changed from:

• • SnomedCT_USEditionRF2_PRODUCTION_[date]T[time]Z.zip

...to the following:

• • SnomedCT_ManagedServiceUS_PRODUCTION_US1000124_[date]T[time]Z.zip

So, for the March 2023 Release of the US Edition, for example, the RF2 package would have originally been called:

• • SnomedCT_USEditionRF2_PRODUCTION_20230301T120000Z.zip

...whereas from now on it will instead be called:

• • SnomedCT_ManagedServiceUS_PRODUCTION_US1000124_20230301T120000Z.zip

Note: The change to the naming convention only effects the zip package name and the top two folders in the unzipped package. No other folder or file name contained in the release package will be impacted.

3.3.1.2. Transitive Closure Resources package naming convention

Please be aware that as of the March 2023 Release of the US Edition onwards, the Transitive Closure Resources package naming convention has been changed in order to bring it in line with the naming standards. This is being changed from:

• • SnomedCT_TransitiveClosureResourcesRF2_PRODUCTION_[date]T[time]Z.zip

...to the following:

• • SnomedCT_ManagedServiceUSTransitiveClosure_PRODUCTION_US1000124_[date]T[time]Z.zip

So, for the March 2023 Release of the US Edition, for example, the RF2 package would have originally been called:

• • SnomedCT_TransitiveClosureResourcesRF2_PRODUCTION_20230301T120000Z.zip

...whereas from now on it will instead be called:

• • SnomedCT_ManagedServiceUSTransitiveClosure_PRODUCTION_US1000124_20230301T120000Z.zip

Note: The change to the naming convention only effects the zip package name and the top two folders in the unzipped package. No other folder or file name contained in the release package will be impacted.

3.3.2. RF2 package format

Similar to the International Edition, the US Edition follows the technical specifications for RF2 packaging 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.3. Deprecation of the ICD10 Exemplar file

Due to the perceived lack of audience for this file, the US have deprecated it by removing it from the ICD10CM Map Resources package from the September 2023 US Edition Release onwards.  Please let the US NRC know if this causes any specific problems for you or your users.

• • doc_Icd10MapTechnicalGuideExemplars_Current-en-US_US1000124_20230301.xlsx

3.3.4. Changes to the Identifier file format

In line with the proposals documented here:  https://confluence.ihtsdotools.org/mag/snomed-international-proposal-to-change-the-rf2-identifier-file-specification - the US Edition Release will from now on include the following changes to the format of the Identifier files:

• • < identifierSchemeId    alternateIdentifier    effectiveTime    active    moduleId    referencedComponentId           ...to
  • > alternateIdentifier    effectiveTime    active    moduleId    identifierSchemeId    referencedComponentId

These improvements are introduced in the September 2023 US Edition release, and will be used in all future US Edition releases until further notice.

3.3.5. Notice of changes to the US Edition Release package

In line with the refined implementation of Annotations, we are updating all Extensions in order to align them with the updated version of the refsets in the International Edition Release package (which were first published in June 2024).

• • The languageCode field was specified as the two characters of ISO-639-1 code for the language of the annotation text. The change includes support for specifying dialect when it is applicable by adhering to RFC 5646, which allows the combination of two characters of ISO 639-1 code and two uppercase letters of country code (ISO 3166) separated by a hyphen.  The changes apply to both the Member Annotations String Value Reference Set + Component Annotation String Value reference set:
    • The column "languageCode" has therefore been changed to "languageDialectCode".
      • Component Annotations (1292992004)
        • OLD:    id    effectiveTime    active    moduleId    refsetId    referencedComponentId    languageCode    typeId    value
        • NEW:   id    effectiveTime    active    moduleId    refsetId    referencedComponentId    languageDialectCode    typeId    value
      • Member Annotations (1292995002)
        • OLD:   id    effectiveTime    active    moduleId    refsetId    referencedComponentId    referencedMemberId    languageCode    typeId    value
        • NEW:  id    effectiveTime    active    moduleId    refsetId    referencedComponentId    referencedMemberId    languageDialectCode    typeId    value

• • Changes to the RefsetDescriptor records - In line with the changes to the Annotations refsets, the following refinements have also been made to the RefsetDescriptor records:

    • 1. The AttributeType for the (attributeOrder=0) refsetDescriptor record for both Member + Component Annotations has been changed from:
      • 900000000000461009 |Concept type component|        to       900000000000460005 |Component type (foundation metadata concept)|
      • (eg)
        • OLD:     6cc1d4ca-32fd-44cb-8ad3-e49f23ec7760    20231201    1    900000000000012004    900000000000456007    1292992004    900000000000518009    900000000000461009    0
          
        • NEW:    6cc1d4ca-32fd-44cb-8ad3-e49f23ec7760    20240601    1    900000000000012004    900000000000456007    1292992004    900000000000518009    900000000000460005    0
          
        • OLD:     f6d9647b-6ee6-400d-9c7f-77818fa1f986    20231201    1    900000000000012004    900000000000456007    1292995002    900000000000518009    900000000000461009    0
          
        • NEW:    f6d9647b-6ee6-400d-9c7f-77818fa1f986    20240601    1    900000000000012004    900000000000456007    1292995002    900000000000518009    900000000000460005    0
    • 2. The languageDialect column for a) the (attributeOrder=2) refsetDescriptor record for Member Annotations + b) the (attributeOrder=1) refsetDescriptor record for Component Annotations has been changed from:
      • 1296895003 |Language code (foundation metadata concept)|       to the new concept       1304275002 |Language or dialect code (foundation metadata concept)|
      • (eg)

        • OLD:     2c0d0378-c28c-4705-b8af-f5f0f8276dfd    20231201    1    900000000000012004    900000000000456007    1292992004    1296895003    900000000000465000    1

        • NEW:    2c0d0378-c28c-4705-b8af-f5f0f8276dfd    20240601    1    900000000000012004    900000000000456007    1292992004    1304275002    900000000000465000    1

        • OLD:     afe9824b-1323-4407-a0b7-a028ae2b780a    20231201    1    900000000000012004    900000000000456007    1292995002    1296895003    900000000000465000    2

        • NEW:    afe9824b-1323-4407-a0b7-a028ae2b780a    20240601    1    900000000000012004    900000000000456007    1292995002    1304275002    900000000000465000    2

    • 3. The AttributeType for a) the (attributeOrder=4) refsetDescriptor record for Member Annotations (1292995002) + b) the (attributeOrder=3) refsetDescriptor record for Component Annotations (1292992004), needs to be changed from:
      • 900000000000459000 (AttributeType)         to        900000000000465000 (String)
      • (eg) 
        • OLD:     54af9962-2a35-4538-86f3-a8c38de9200b    20231201    1    900000000000012004    900000000000456007    1292995002    900000000000519001    900000000000459000    4
        • NEW:    54af9962-2a35-4538-86f3-a8c38de9200b    20240601    1    900000000000012004    900000000000456007    1292995002    900000000000519001    900000000000465000    4
        • OLD:     b46405ec-5ff1-46a3-a9cc-b2ef2bba23cc    20231201    1    900000000000012004    900000000000456007    1292992004    900000000000519001    900000000000459000    3
          
        • NEW:    b46405ec-5ff1-46a3-a9cc-b2ef2bba23cc    20240601    1    900000000000012004    900000000000456007    1292992004    900000000000519001    900000000000465000    3

    
    

3.4. Feedback and suggestions

We welcome questions, comments or suggestions to improve the quality, accuracy and usability of the SNOMED CT US Edition. Please send feedback to NLM Customer Support https://support.nlm.nih.gov/.