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 NL Edition is a combination of the full June 2022 SNOMED CT International Edition and the NL 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 NL Edition is developed and maintained by the NL NRC and is available to authorized 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.
1.1. Background
This document provides a summarized description of the content changes included in the September 2022 release of the SNOMED Clinical Terms® NL 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 2022 NL Edition release.
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 2022 International Edition - SNOMED International Release notes.
1.3. Changes to the release format
Since the last release, our SNOMED NRC has changed to a new authoring platform. This has necessitated a number of changes in our release. These changes are described in sections 3.3 & 3.4. Please read these sections carefully, as they may require you to change your import script.
1.4. National Terminology Server
The National Terminology Server provides an easy method of accessing the latest SNOMED edition in the FHIR R4 format. Using this server is free of charge. More information can be found at https://www.nictiz.nl/standaardisatie/terminologiecentrum/nationale-terminologieserver/ and https://github.com/terminologieserver.
2. Content Development Activity
2.1. Summary
The September 2022 SNOMED CT NL Edition contains content authoring tooling and release production provided by SNOMED International Managed Service. Quality assurance of the release was completed by both the NL NRC and SNOMED International.
2.1.1. September 2022 NL Edition of SNOMED CT Statistics
These statistics include the content from the June 2022 International Edition and the September 2022 NL Edition.
Release |
Concept Count |
Description Count |
Relationship Count |
---|---|---|---|
NL Edition of SNOMED CT | 13,534 | 986,574 | 84,051 |
These statistics include the content from the September 2022 NL Edition.
Statistics for September 2022 NL Edition of SNOMED CT | |
|
#total |
---|---|
Number of new active NL concepts | 328 |
Number of new active descriptions | 16,318 |
Number of new active relationships | 4,426 |
Number of newly inactivated concepts | 145 |
Total number of active translated concepts | 270,883 |
2.2. SNOMED CT derived products
2.2.1. New reference sets
Reference set | Content | RefsetId |
---|---|---|
Dutch simple reference set of causative pathogens in sepsis and meningitis |
Pathogens that can cause sepsis or meningitis. |
210041000146107 |
Dutch simple reference set of causative pathogens in congenital infection |
Pathogens that can cause congenital infections. | 210051000146105 |
Patient-friendly Dutch at B1 reading level language reference set | Language reference set for patient-friendly descriptions at B1 reading level. | 160161000146108 |
2.2.2. Changed reference sets
Dutch contact allergen simple reference set |
Handpicked set of contact allergens. |
98051000146103 |
Dutch food allergen simple reference set |
Handpicked set of food allergens. |
98011000146102 |
Dutch total non-drug allergen simple reference set |
Intensional reference set which contains all allergens from our 5 handpicked allergen simple reference sets. |
98061000146100 |
Dutch implant registry simple reference set | Combination of handpicked set and intensional set of implants that need to be delivered to the national implant registry by the hospitals. | 52801000146101 |
Dutch implants reference set - extensional | Handpicked set of implants that need to be delivered to the national implant registry by the hospitals. | 117731000146100 |
Dutch implants reference set - intensional | Intensional set of implants that need to be delivered to the national implant registry by the hospitals. | 117721000146102 |
Dutch microorganism simple reference set |
>4,000 micro-organism concepts for registration in Dutch laboratories. |
2581000146104 |
Dutch obstetric procedures simple reference set |
List of obstetric procedures for primary health care |
146481000146103 |
Dutch pathology simple reference set |
Handpicked set of concepts for the Dutch PALGA thesaurus |
110851000146103 |
Dutch causes of death statistics simple reference set | Handpicked set of concepts for mortality registration, developed for CBS. | 51000146100 |
SNOMED CT allergen to drug excipient map reference set | Correlated map from SNOMED allergen concepts to G-standaard drug excipient codes | 148521000146104 |
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 June 2022 International Edition - SNOMED International Release notes), the following are Known Issues for the SNOMED CT NL 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 2022 NL 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 June 2022 International Edition - SNOMED International Release notes), the following Resolved Issues for the SNOMED CT September 2022 NL Edition:
3.3. Technical Updates
In addition to the Technical Updates reported in the following monthly Release Notes:
-
- SNOMED CT February 2022 International Edition - SNOMED International Release notes
- SNOMED CT March 2022 International Edition - SNOMED International Release notes
- SNOMED CT April 2022 International Edition - SNOMED International Release notes
- SNOMED CT May 2022 International Edition - SNOMED International Release notes
- SNOMED CT June 2022 International Edition - SNOMED International Release notes
- SNOMED CT July 2022 International Edition - SNOMED International Release notes
...the following technical updates pertain to the NL Edition:
3.3.1. Notice of changes to the NL Edition Release Package naming convention
3.3.1.1. Release Package naming convention standardised
From the September 2022 Release of the NL Edition onwards, the RF2 package naming convention will be standardised to bring it in line with the other extensions in the community, enabling better interoperability.. The format will therefore change from:
-
- SnomedCT_Netherlands_EditionRelease_PRODUCTION_[date]T[time]Z.zip
...to the following:
-
- SnomedCT_ManagedServiceNL_PRODUCTION_NL1000146_[date]T[time]Z.zip
So, for the September 2022 NL Edition Release, for example, the RF2 package would have originally been called:
-
- SnomedCT_Netherlands_EditionRelease_PRODUCTION_20220930T120000Z.zip
...whereas from now on it will instead be called:
-
- SnomedCT_ManagedServiceNL_PRODUCTION_NL1000146_20220930T120000Z.zip
3.3.1.2. Release File naming convention standardised
From the September 2022 Release of the NL Edition onwards, the File naming convention will be standardised to bring it in line with the other extensions in the community, enabling better interoperability. The format will therefore change from:
-
- [FileType]_[ContentType]_[ContentSubType]_[CountryCode]_[VersionDate].[FileExtension]
...to the following:
-
-
[FileType]_[ContentType]_[ContentSubType]_[CountryCode][CountryNamespace]_[VersionDate].[FileExtension]
-
So, for the September 2022 NL Edition Release, for example, the Concept file name would have originally been called:
-
- sct2_Concept_Snapshot_NL_20220930.txt
...whereas from now on it will instead be called:
-
- sct2_Concept_Snapshot_NL1000146_20220930.txt
3.3.2. Notice of changes to the International Edition Release Schedule
As you may already know SNOMED International have transitioned to a monthly delivery schedule for the International Edition of SNOMED CT. The move towards more frequent releases of SNOMED CT realizes several benefits, including:
-
- The potential to be able to get content changes into the terminology in a shorter time frame.
- The fostering of better interoperability, as a result of entities being able to consume release content that is more aligned with other organizations.
- The prevention of circular dependencies that occur in longer projects, due to the move towards smaller, more manageable authoring projects.
- More automated validation services, as a result of the inherent removal of the Alpha/Beta stages in the Release cycle.
Whilst most users will continue unaffected (as they can simply continue to download the releases every 6 months as always), this transition will necessarily involve a few changes to process/packages:
-
- Delta files have been removed from both International and Managed Service release packages, including the Sweden Extension. A Delta Generation service will be provided for those who need it. The Delta Generation Tool allows users to create their own Delta between two fixed release dates - you can find it here:
-
- The ICD-O/ICD-10 Maps will continue to be published in each Monthly International Edition release package (in line with that month's content) for the foreseeable future, unless we experience issues with the new process in Production, and they need to be removed at a later date.
The first monthly Release of the SNOMED CT International Edition was published on the 28th February 2022 with the Delta files having been removed, and therefore they have been removed from the NL Edition from the September 2022 Release onwards.
Please note - While the SNOMED CT International Edition is moving to monthly releases, the NL Edition of SNOMED CT will remain on the current bi-annual release schedule of March and September.
3.3.3. RF2 package format
Similar to the International Edition, the NL Edition will follow 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.4. Changes to the Release Package
Since the last release, our SNOMED NRC has changed to a new authoring platform. This has necessitated a number of changes in our releases:
-
- We now release only a single package with release files. This contains the entire Netherlands edition. We no longer publish the extension as a separate package.
- The patient-friendly descriptions have been moved into the standard Dutch module. They can still be identified using the patient-friendly language reference set; there is no longer be a separate patient-friendly package or even a separate patient-friendly module.
- Dutch and English descriptions and text definitions are now split in different files:
- sct2_Description_Snapshot_NL_20220930.txt
- sct2_Description_Snapshot_EN_20220930.txt
- sct2_ TextDefinition _Snapshot_NL_20220930.txt
- sct2_ TextDefinition _Snapshot_EN_20220930.txt
- The simple reference sets are no longer contained in a single file, but in a separate file for each reference set. It is now easier to import a single reference set, but to import all reference sets requires reading multiple files.
- An error was detected in the handling of UUIDs of the Module Dependency reference set (MDRS), which caused historical data that should have been limited to the FULL edition to appear in the SNAPSHOT. The error has been fixed retro-actively, which means the UUIDs in the FULL version of the MDRS, for previously published rows, have been changed. We deemed this a better solution than propagating the error, but please contact us if this change causes an issue for your import.
For those who previously relied on the package or moduleId to identify which terms are patient-friendly, please note that this approach must have given you incomplete results, and now produces no results at all. We urge you to start using the patient-friendly language reference set. More information can be found at https://www.nictiz.nl/standaardisatie/terminologiecentrum/referentielijsten/inbouwen-snomed-referentieset/, in the SNOMED CT Release File Specifications at http://snomed.org/rfs and in our how-to videos at https://www.nictiz.nl/standaardisatie/terminologiecentrum/trainingsaanbod/.
3.4. Feedback and suggestions
We welcome questions, comments or suggestions to improve the quality, accuracy and usability of the SNOMED CT NL Edition. Please send feedback to info@snomed.nl.
Approvals
Final Version |
Date |
Approver |
Comments |
---|---|---|---|
1.0 |
|
Feikje Hielkema-Raadsveld |
Approved |
Draft Amendment History
Version | Date | Editor | Comments |
---|---|---|---|
0.1 |
|
Andrew Atkinson | Initial draft created |
0.1 |
|
Feikje Hielkema-Raadsveld | Draft updates |
1.0 |
|
Andrew Atkinson | Final updates |
1.0 |
|
Feikje Hielkema-Raadsveld | Final updates |