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 March 2017 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 2017 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® January 2017 International Edition release.
3.2 New and Updated Content
New Concepts: 0
Inactivated Concepts: 0
Description Changes : 695
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 March 2017, there are no known issues.
4.2 Technical Issues
Resolved Issues
Approvals
Final Version | Date | Approver | Comments |
---|---|---|---|
1.0 |
| Terance Shird | Approved |
1.0 |
| Rory Davidson | Approved |
1.0 |
| Camilla Danielsen | Approved |
Download .pdf here:
Draft Amendment History
Version | Date | Editor | Comments |
---|---|---|---|
0.1 |
| Andrew Atkinson | Initial draft created |
0.2 |
| Terance Shird | Minor Updates |
7 Comments
Camilla Wiberg Danielsen
Hi Terance,
I do not seem to be able to search these in the SCA - what are they and why did they have a wrong moduleID?
Camilla
Terance Shird
I have asked the release team to respond.
Camilla Wiberg Danielsen
I know it has been there all the time, but should 4.2 Technical notes not be 4.2 Technical issues. Because there is a 4 Technical notes above.
Terance Shird
Thank you I will update.
Michael Chu
Hi Camilla,
These 12 attribute value refset components are description inactivation reasons which were added by the bulk update. These inactivation reasons are correct apart from the module id as the international module id(900000000000207008) was used instead of the DK module id (554471000005108). In the DK 20170331 release we have updated these 12 refset components to use the DK module id.
Thanks
Michael
Camilla Wiberg Danielsen
Thanks for the explanation. Would the text below explain the change better than the one presently in 4.2 Technical issues?
"The following 12 attribute value refset component description erroneously were found to have the SNOMED International core moduleID (900000000000207008) instead of the Danish moduleID (554471000005108). In the DK 20170331 release we have updated these 12 refset components to use the DK module id."
I do not have any other changes to the release notes.
Camilla Wiberg Danielsen
Hi Terance, did you update the DK browser with the new release yet? /Camilla