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 International Health Terminology Standards Development organisation (IHTSDO^®) 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.

2 Background

This document provides a summarized description of the content changes included in the June 2016 release of the SNOMED Clinical Terms^® Managed Service Denmark Extension package.

It will also includes technical notes detailing the known issues which have been identified (should any of these exist). 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 Denmark Extension package is dependent upon, and should therefore be consumed in conjunction with the SNOMED CT® January 2016 International Edition release.

2.1 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.

3 Content Development Activity

3.1 Summary

This editing cycle was predominantly spent transitioning to the new Managed Service.

3.2 New and Updated Content

This section will be updated from the next Release onwards.

4 Technical notes

4.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 Managed Service - Denmark Extension June 2016, the following Known Issues were identified, and agreed to be resolved in the next editing cycle:

4.2 Technical notes

The refsetDescriptor files were found to be inaccurate in previous packages, and so in this release we have removed the old records and reset the files, as follows:

• Historical data in the Full file rebuilt from previous release packages.
• All effectiveTimes updated to this release's effectiveTime, in order to clearly delineate between the erroneous history in the previous packages, and the corrected history in this one.
• Duplicate UUID's updated to enforce uniqueness.
• All records that were describing the redundant refsets (and whose files have now been removed from the release package) have now been removed from the refsetDescriptor file.
• All records that were describing refsets in the International edition (for example the EN-GB and EN-US language refsets) removed as these records already exist in the dependent International edition packages.

The moduleDependency files were corrected as follows:

• Historical data in the Full file rebuilt from previous release packages.
• Additional records added in order to call out the dependency of the Danish module (554471000005108) on the Model Component module (900000000000012004) as well as the Core module (900000000000207008).  The additional records have been assigned the original effectiveTimes (as if these records had always existed) in order to ensure that the historical audit trail is corrected, so that anyone wishing to use the file for previous releases is able to do so accurately.
• UUID's corrected to use the original UUID consistently throughout the history (as opposed to having a new UUID for each release) - as this file describes a new state of the same component for each release, and not an actual new component.
• Dependency of the original 20131018 Danish release corrected to show the dependency on the 20130731 International edition, instead of a circular reference to itself.