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 | Browse Content Changes for the January 2020 Release The daily build is available to review changes made to content for the January 2020 release https://dailybuild.ihtsdotools.org/ Forthcoming concept inactivations, new concepts and changes to existing concepts can be reviewed using the tab 'Daily build.' | January 2020 International Release | ||||||||
| 2 | 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 cardiovascular, digestive and genitourinary systems have been included in the July 2019 release. The respiratory, nervous, integumentary, endocrine, immune, sensory organs, lymphoreticular, hematological systems will be revised in the January 2020 International release. Information about revision of IS_A relationships can be viewed here: Update case significance assignment following the RF2 specification The incorrect assignment of case significance for descriptions needs to be fixed according to the RF2 specification. The issue is that the value 900000000000448009 |Entire term case insensitive| has not been used due to the data migration from RF1 and limitation of authoring tool. In fact, a majority of SNOMED CT descriptions should be ‘Entire term case insensitive’. These terms can be freely switched to lower or upper case without impact to meaning. The technical batch changes will be made to the case significance value to address the issue. Please see detail in the document at https://confluence.ihtsdotools.org/display/ IHTSDO1/IHTSDO-950+Updatecasesignificanceassignment+following+the+RF2+specification | July 2017 International Edition | January 2020 International Release | |||||||
| 3 | MRCM Changes Please see: | January 2020 International Release | ||||||||
| 4 | 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 | ||||||||
| 5 | 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' starting from the July 2019 release. | January 2020 International Release and future releases | ||||||||
| 6 | 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 | ||||||||
| 7 | 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 | ||||||||
| 8 | Changes for 'On examination' (O/E) and 'Complaining of' (C/O) concepts Jan 2020 release:
July 2020 release:
Content being inactivated will use the reason - component moved elsewhere. Note: some concepts will not have a replacement concept as they are groupers. For example: | January 2020 International Release July 2020 International Release | ||||||||
| 9 | Inactivation of 33359002 |Degeneration (morphologic abnormality)| In order to distinguish the degenerative process from the structure, 33359002 |Degeneration (morphologic abnormality)| has been inactivated as a DUPLICATE, SAME AS 107669003 |Degenerative abnormality (morphologic abnormality)|. All morphologies in the disorder hierarchy have been replaced accordingly. 107669003 |Degenerative abnormality (morphologic abnormality)| 33359002 |Degeneration (morphologic abnormality)| | January 2020 International Release | ||||||||
| 10 | Inactivation of 23583003 |Inflammation (morphologic abnormality) In order to distinguish inflammatory process from structure, 23583003 |Inflammation (morphologic abnormality)| has been Inactivated as DUPLICATE, SAME AS 409774005 |Inflammatory morphology (morphologic abnormality)|. All concepts in the Inflammatory disorder hierarchy have been remodeled accordingly. | January 2020 International Release | ||||||||
| 11 | ICD-O project work IACR have released ICD-O-3.2 as a listing of all new additions, changes and revisions to ICD-O-3.1 in Excel format. The new version, ICD-O-3.2, is recommended for use from 2020. ICD-O-3.2 is not yet available online or in book format. In preparation for the update, the changes have been divided into types and are being investigated/addressed in the ICD-O-3.2 update project. The priority is being given to those that have an impact on clinical safety, e.g., changes of behaviour (benign, malignant etc.) and adding new content for SNOMED CT morphologies, this refers to the 400177003 |Neoplasm and/or hamartoma (morphologic abnormality)| hierarchy. The descriptions with [obs] have been inactivated as outdated because they are artefacts of descriptions from the ICD-O-3 print version for their history tracking. The maps to ICD-O-3.1 are being updated only for error correction purposes for the January 2020 release. The maps to ICD-O-3.2 are out of scope for the January 2020 release and are planned for a future release. | January 2020 International Release | ||||||||
| 12 | 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 | ||||||||
| 13 | 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 | ||||||||
| 14 | 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 | ||||||||
| 15 | 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 International Release | ||||||||
| 16 | Replacement of the Stated Relationship files with the new OWL Axiom refset files A set of documentations has been developed to support the Logic Profile Enhancements.
For any questions, please contact SNOMED International at support@snomed.org with “OWL Axiom refset files implementation question” in the subject line. | 2 | Improvement to the Release package naming convention In order to bring the current naming convention into line with the ISO8601 standard, we will add a "Z" suffix to all release package names (but not to internal file names). This will ensure that the time in the release package name is set in the correct context, namely UTC. For example therefore, instead of the July 2017 International Edition release package being called: SnomedCT_InternationalRF2_Production_20170731T120000.zip It will instead be called: SnomedCT_InternationalRF2_Production_20170731T120000Z.zip | July 2017 International Edition