Overview of Current Notices
For additional Relevant links with regards to Content Development Information please click here Content Development Information
| Items | Proposed improvement | Planned Release date (*this is provisional only and is subject to change) | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Replacement of the Stated Relationship files with the new OWL Axiom refset files Following on from all of the previous announcements providing early visibility of the transition plan, SNOMED International would now like to provide technical details of the planned migration from Stated Relationships to OWL files. This plan has been discussed and agreed with numerous stakeholders from the community, and will be implemented over the course of the next two International Releases, as follows: January 2019:
July 2019:
The inferred relationship file will maintain the same format and structure, though it will no longer contain all necessary and sufficient conditions. The inferred relationship file is represented in Necessary Normal Form for distribution of relationships. It is a collection of all the necessary conditions and represents a subset of the full semantics from the 2018 July release and onwards. Most users will benefit from the improvements in the inferred relationships without requiring changes to their existing systems. A set of documentations has been developed to support the Logic Profile Enhancements.
Users should carefully analyse any potential impact to their systems (upload routines, etc) and make provisions for these changes urgently (if not already done), in order to prevent any issues when these changes come into effect in January 2019. Please contact SNOMED International at support@snomed.org with “OWL Axiom refset files implementation question” in the subject line. | January 2019 International Release + July 2019 International Release | |||||||||||
| 2 | LOINC timeline changes - please refer to Roadmap link here LOINC | July 2018 and potentially other future releases - On hold | |||||||||||
| 3 | Revision of IS A relationships for anatomy concepts The new anatomy concept model implemented the enhanced Description Logic features, e.g. reflexive and transitive properties, additional axioms, for consistent logical modeling. The inferred IS A relationships from the OWL anatomy ontology have been reviewed and the changes have been implemented in the production. The potential impact to other hierarchies, such as disorders, procedures, observables, situations etc are also reviewed as part of the project. The revision of sub-hierarchy 26107004|Structure of musculoskeletal system (body structure)| has been planned for the January 2019 release. The rest body systems will be revised in the future releases. The subject area for revision of IS A relationships will be determined and updated in the following confluence page. | July 2019 International Release | |||||||||||
| 4 | Improvement for the representation of role groups It is important to clearly indicate if an attribute is grouped or not because role grouping has impact to semantics and classification results. The majority of the Modeling Advisory Group members recommended explicit representation for role groups. There will be two key improvements for representation in the July 2019 release. The changes are demonstrated in the January 2019 Demo release package. Firstly, role groups are explicitly stated and represented by the concept 609096000|Role group (attribute)| as an object property in the OWL axiom refset. Secondly, for the inferred relationship file, role group 0 will be only applied to attributes that are not logically grouped, e.g. not a value of 609096000|Role group (attribute)| in an OWL axiom or grouped = 0 in the MRCM. This addresses the potential confusion whether an attribute is grouped or not in the role group 0. The improvements will provide consistent representation for role groups in the OWL axioms, inferred relationship file, and diagramming of the concept model. | July 2019 International Release | |||||||||||
| 5 | MRCM Changes | July 2019 International Release | An update on changes for the January 2020 release will be posted here as soon as it is available. | January 2020 International Release | |||||||||
| 6 | Quality Initiative Information about the project can found here - Quality Initiative - Progress Note: There are changes to the Service Level Agreement for the CRS as a result of the Quality Initiative: | January 2020 International Release | |||||||||||
| 76 | Planned changes to 'Co-occurrent and due to' pattern During the implementation of the new Description Logic features a conflict was uncovered between the modeling of 'Co-occurrent and due to' and General Concept Inclusions (GCIs). This has resulted in the need to reconsider the modeling of "Co-occurrent and due' and update the Editorial Guide for this area. There are a number of new concepts in the January 2019 release that are based upon the existing guidance for 'Co-occurrent and due to'. The plan is to update the Editorial Guide and all concepts that are currently modeled as 'Co-occurrent and due to' for starting from the July 2019 release. | July 2019 International January 2020 International Release | |||||||||||
| 7 | Planned changes to 432119003 | Aneurysm (disorder) and descendants Review of the hierarchy with parent concept of 432119003 | Aneurysm (disorder) |
The number of concepts using either unruptured, non-ruptured or nonruptured were 13/1/4 respectively. There are 97 'Aneurysm of xxx artery' concepts. A decision was taken to inactivate those concepts of the form 'unruptured/non-ruptured/nonruptured aneurysm of xxx artery' as duplicates and point to their 'aneurysm of xxx artery' equivalents where available and to create new concepts where they were not. | July 2019 International Release | |||||||||||
| 8 | Planned Inactivation of 186005001|Other ethnic non-mixed (NMO)| 186005001|Other ethnic non-mixed (NMO)| and children will be inactivated with a status of MOVED ELSEWHERE. | July 2019 International Release | |||||||||||
| 9 | Summary of Substances Changes
| July 2019 International Release | |||||||||||
| 10 | Summary of Changes for the Drug Project For 2019-January, CDs that had not yet been sufficiently defined were relocated to be descendants of 770654000 |TEMPORARY parent for CDs that are not updated (product)| (n≈2700). Concepts that could not be mapped to a corresponding dm+d or RxNorm concept have been inactivated as Outdated for the 2019-July Release with a historical relationship to a corresponding MPF-only concept (or to a MP-only concept if no appropriate MPF-only concept existed at the time of inactivation). (n≈870). The remainder of the concepts (n≈1800) being reviewed and most are expected to be sufficiently defined for the 2019-July Release. Further early visibility updates will be provided as work progresses. | July 2019 International Release | |||||||||||
| 11 | Summary of Organism Changes
| July 2019 International Release | |||||||||||
| 12 | Quality Initiative Information about the project can found here - Quality Initiative - Progress Note: There are changes to the Service Level Agreement for the CRS as a result of the Quality Initiative: | July 2019 International Release | |||||||||||
| 8 | WAS_A Inactivation reason of LIMITED/WAS_A is not allowed for any new content inactivations after the July 2018 release. The WAS_A association refset has not been updated thereafter. At the Editorial Advisory Group meeting in April 2019, agreement was reached to discontinue the maintenance of WAS_A relationships when inactivating concepts that have a historical association to an inactive concept. When changes are made to a historical relationship for a concept that was previously inactivated using WAS_A, effort will be made to assign a new historical relationship that facilitates traceability of the concept (e.g. DUPLICATE or AMBIGUOUS) as opposed to NON-CONFORMANCE TO EDITORIAL POLICY. Existing WAS_A relationships will be inactivated in a future release once a plan for batch reassignment of historical relationships has been developed. Until then, SNOMED International will not continue to use or maintain WAS_A relationships. | January 2020 International Release and future releases | |||||||||||
| 9 | Known Content Issues July 2019 Release Approximately 149 text definitions are missing either a US or GB spelling variation. These are all legacy issues that will be rectified in the January 2020 release. A small set of disorder concepts have been identified with descendants that have a semantic tag of clinical finding. A further small set of concepts have been identified that have a semantic tag of disorder but are not descendants of 64572001|Disease (disorder)|. These concepts are all legacy issues that will be rectified in the January 2020 release. Release validation rules have been enhanced to prevent recurrence of legacy issues for future content additions. | January 2020 International Release | |||||||||||
| 10 | Over the Counter Concepts referring to “over the counter” status have been inactivated. Concepts referring to regulatory status or characterization (e.g. over the counter) are out of scope for the International Release since the meaning may vary by jurisdiction and is not consistent internationally. | January 2020 International Release | |||||||||||
| 11 | Vaccine Poisoning Concepts referring to vaccine poisoning have been inactivated with historical relationships to the corresponding Adverse reaction caused by X vaccine and to Adverse reaction caused by vaccine constituent. The notion of vaccine poisoning has persisted in ICD 10 under T50 but it is not included in ICD-11; the poisoning aspect seemingly referred to the adjuvants and carriers that are included in the vaccines as opposed to the biological component itself. | January 2020 International Release | |||||||||||
| 12 | Revision of 298180004 |Finding of range of joint movement (finding) The concepts under the subhierarchy 298180004 |Finding of range of joint movement (finding)| are being remodeled to represent the finding site of <<785818007 |Structure of joint region (body structure)| instead of <<39352004 |Joint structure (body structure)|. Range of movement of a joint region can be impacted by both bone and soft tissues, therefore the use of 39352004 |Joint structure (body structure)| was too restrictive and caused issues in other areas of the terminology. These changes will be made over the course of two releases due to the number of affected concepts. | July 2019 International Release January 2020 International Release | |||||||||||
| 13 | Planned changes to Implantation and Insertion procedures Work commenced on content tracker IHTSDO-175 Ongoing structural changes for the Procedure concepts related to the content tracker: It was agreed that not all Insertion and Implantation procedures are surgical. As a result, further work in the hierarchy under 129284003 |Surgical action (qualifier value)| has been undertaken for the January 2020 release and this includes: Work on this project will continue for future releases after January 2020. | January 2020 | 13 | Abrasion As a result of changes made during the QI project for the January 2019 release, there are now 2 concepts which have the same preferred term. 781488002 |Abrasion of foot (finding) and 211402004 |Abrasion of foot (disorder) 782201009 |Abrasion (finding)| and 399963005 |Abrasion (disorder)| These concepts will be addressed as part the QI project for the July 2019 release. | July 2019 International Release | ||||||||
| 14 | Concrete domains and numeric representation Numerics are represented by concepts in the Medicinal product concept model in SNOMED CT, which is an interim solution before the implementation of concrete domains to support data types, such as decimal, integer, string and date/time. The implementation of concrete domains depends on the OWL expression reference set and the update of inferred relationship file. The first complete OWL expression refset will be available in the July 2019 international release. It will take time to update the specification for the inferred relationship file and consult with the community of practice. When they are ready, strength in medicinal product model can be transformed to concrete domains. The transformation will be completed by technical changes without impact to classification results. | July 2019 International Release | |||||||||||
| 15 | Replacement of OWL conversion script with a link to the open source directory In January 2017 the original OWL conversion script (a.k.a. the "Spackman OWL script") was removed from the International Edition package, and has since been published as a separate artefact alongside each Release. Because this script does not recognize the two new OWL refsets (see section 3.3.2 of these Release Notes), the Terminology Release Advisory Group has determined that the script should no longer be distributed. Going forward, Release Notes will now include a link to the new open source OWL conversion toolkit that can be found in the following repository (including documentation on its use): https://github.com/IHTSDO/snomed-owl-toolkit Please contact SNOMED International at support@snomed.org if you would like to provide any feedback on ways to extend and improve the new toolkit. | July 2018 International Release | |||||||||||
| 16 | Deprecation of the Technical Guide Exemplars document from the International Edition release package The Terminology Release Advisory Group has confirmed that there should be no impact from removing this almost entirely static document from the International Edition release package, and hosting it instead in a Confluence Page. From the July 2018 International release then, we will deprecate this file (doc_Icd10MapTechnicalGuideExemplars_[date].xlsx) from the Release package, and instead provide a link in the Release Notes to the new Confluence Page. Please see section 2.4.1.3 of the Release Notes for the relevant link. | July 2018 International Release |