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®), 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.
2 Background
This document provides a summarized description of the content changes included in the September 2019 March 2020 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® July 2019 January 2020 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 release contains translation corrections and improvements to existing content as well as minor technical corrections made as a result of upgrading the extension to use the SNOMED CT® July 2019 CT® January 2020 International Edition release.
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.
| Jira |
|---|
| server | IHTSDO JIRA |
|---|
| columns | key,summary,description,priority |
|---|
| maximumIssues | 100 |
|---|
| jqlQuery | filter = "MS (DK) 20190930 20200331 - KNOWN ISSUES" ORDER BY key ASC |
|---|
| serverId | b202d822-d767-33be-b234-fec5accd5d8c |
|---|
|
4.2 Technical Issues
Resolved Issues
| Jira |
|---|
| server | IHTSDO JIRA |
|---|
| columns | key,summary,description,priority |
|---|
| maximumIssues | 100 |
|---|
| jqlQuery | filter = "MS (DK) 20190930 20200331 - RESOLVED ISSUES" ORDER BY key ASC |
|---|
| serverId | b202d822-d767-33be-b234-fec5accd5d8c |
|---|
|
