Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

 This page contains the recommendations and final decisions for topics presented and discussed at the Editorial Advisory Group conference calls and face-to-face meetings.  Where decisions have been modified over time, a brief history of the changes will be included. 

TopicDates of discussionRecommendationActionAction Status
Laterality

2015-10-27

  1. Restrictions on laterality be relaxed.

  2. IHTSDO should add lateralized concepts as needed and not proactively pre-coordinate every laterality.

  3. The AG unanimously recommended laterality Option 4, which is essentially the same idea as option 3 but implemented with a new attribute like “has laterality” that users add to the same role group instead of having it outside the same role group.

The early decision was reviewed at a number of the following EAG conference calls and it was decided to use the current capabilities in the terminology to support lateralized content.

Decision: The addition of pre-coordinated structures using the existing "LATERALITY" attribute was approved in light of the timeframe for support of nesting.

  • Editors to add pre-coordinated lateralized body structures to the terminology as needed to fully define concepts in other hierarchies
Implemented and ongoing
Phyiscal object as Specimen substance2015-10-27

Currently, Device specimen is a subtype of specimen; however not all physical objects that may be specimen substances may be devices. Recommendation to relax the range to include all physical objects.

Tracker item: DRUGS-49 - Getting issue details... STATUS

2015-12-10: The suggested modeling change will be managed as part of the effort to create clarity re: use of substance vs product concept as attribute values to define concepts in other hierarchies (associated with the Drug - International Release Model and Content project). Details can be found on the following Confluence site:
https://confluence.ihtsdotools.org/display/DIRMC

Pending

New attributes to describe temporal context

2015-10-27

Discussion related to the need for representing temporal context beyond the existing AFTER relationship. Initial proposal was to add temporal values to the OCCURRENCE range. This was not accepted.

Later discussion included the creation of new temporal attributes to distinguish between causality and temporality of combined disorders.

  • Create specific temporal concepts under ASSOCIATED WITH, including:

TEMPORALLY RELATED TO

BEFORE

DURING

Add AFTER as a subtype of TEMPORALLY RELATED TO

  • Update MRCM to support the new attributes and ranges
Completed
Application of ECE guidance retrospectively: maintenance of existing descriptions that may be ambiguous2015-10-27Presentation outlined existing issues with content that does not conform to proposed naming and modeling for combined disorders as recommended by ECE
  • Content will be incrementally updated based on approved combined disorder editorial guidance, as discovered.
In progress
Unilateral Concepts

2015-10-27

2015-11-30

No decision at the 2015-10-27 meeting. Additional input from implementers will be sought.

2015-11-30 discussion

  1. Retire the concepts as ambiguous (and this was the most radical solution).
  2. Add them to the findings hierarchy but keep them as siblings to the lateralized structures, which unlinks them from bilateral, left and right.
  3. Leave them where they are.


  • Inactivate existing unilateral concepts, replacing them with specific lateralized content
In progress
SNOMED CT Interface or Reference Terminology?2015-10-27As part of the SNOMED CT design, interface terminology is wholly supported by SNOMED CT and the may be represented as a dialect. The way one should implement an interface terminology is by implementing a dialect of SNOMED CT, not by doing an ongoing mapping that would never be semantically sound and that would cause a number of other problems.
    • Jim Case to develop a policy statement on Interface terminology, including patient-friendly descriptions. Link to policy available.
Completed
WAS-A relationships2015-11-30Add to the Editorial Guide guidance on retirement of WAS-A relationships. The WAS-A should be removed and the target concept should be linked to the next proximal higher concept in the hierarchy.
  • Inactivate WAS-A relationships and point to next higher concept as an IS-A relationship
Pending batch update
Need for description that matches FSN2016-01-22

This is an "english-language" issue as it does not affect translations. While it has been the standard for SNOMED CT for over 10 years, recent changes to the FSN naming patterns has resulted in a large number of "non-user-friendly" FSNs, especially for combined disorders. The addition of descriptions with these terms was proposed as being of little value.

The determination of when a description matching the FSN provided value would be left up to the editor. The authoring tool would still create one when a new concept was created, but the retention of that description would not be mandatory

  • Have the technical services group update the validation rules of the authoring tool to allow for a concept to be saved without a description matching the FSN.
Complete
Use of URLs in concept definitions2016-01-22

More evaluation is needed because it was about more than just URLs. There were a lot of issues around text definitions that need to be discussed.

Discussion page created.

  • Jim Case to collect options for representing external definitions for concepts.
Pending
Use of Slashes in FSNs2016-02-29JCA said the final recommendation on use of slashes in FSNs was documented on the discussions page. 
  • Editorial guide to be updated reflecting the policy on the use of slashes in FSNs. See section 7.2.2.6
Complete
Use of the Oxford comma in FSNs2016-04-19

The Oxford comma is a comma added after the penultimate term in a list, e.g. For example "Disorder of head, neck, and shoulders". The purpose if its use is to make explicit the fact that the terms are part of a list. The editorial guide is silent about its use, but the example provided does not use the Oxford comma.

There are currently 347 FSNs in SNOMED CT that use the Oxford comma. Most of these are terms obtained from other terminology, such as ICD and nursing. There are 2500 that contain comma delimited lists but do not use the Oxford comma.

Should SNOMED CT be consistent in the use of this grammar mark or maintain fidelity to the original source of the terms that do use it?


Pending
Evaluation of the use of DUE TO2016-04-19Based on work done by the ECE, there is a need to do a historical review of the use of the DUE TO relationship to ensure that the causality is supported by the current literature.
  • Jim Case to create a tracker item to add to the quality improvement plan for SNOMED CT
Pending
Addition of "grouper" terms to hierarchies2016-04-19

Acknowledged that for primitive hierarchies, grouper terms are necessary to navigate and organize the hierarchy.

Decision: Primitive groupers may be added to top level hierarchies that d not have a supporting concept model.

For hierarchies with a concept model the usefulness of fully defined groupers is limited to convenience groupings based on preferred classifications (e.g. disorder by site), Primitive intermediate groupers, while discouraged, are sometimes necessary when the concept model is not robust enough to support the full definition of a subset of terms. However, they add a substantial management burden.

Decision: Fully defined intermediate groupers may be added if they provide demonstrable benefit to organizing and navigating the terminology. Intermediate primitive groupers will only be added on a case by case basis and by approval from the Head of Terminology or the Principle Terminologist.

Pending
Use of Non-ASCII characters2016-04-19Use of non-ASCII characters, such as "em-dash" and "en-dash" in descriptions was discussed and general consensus was that these should be supported.
  • Jim Case To follow up with Technical services on needed changes to tooling to support the use of non-ASCII characters.
Pending
Moving concepts between hierarchies without replacement2016-04-19Agreed that a simple editorial policy regarding conditions under which concepts could be moved without inactivation and replacement. Examples include Findings to Situation, Evaluation procedures to Observable entity, etc.
Pending
Word order variants2016-04-19There is no general policy for acceptance of word order variants, although it is discussed in a number of areas of the Editorial Guide. A section under 7.4 General rules for naming conventions for specific hierarchies should be added to specify when word order variants are allowed.
  • Editorial tracker item needed.

Lymphadenopathy2016-04-19 Clinical interpretation/usage of terms vs. way they were represented in the terminology is causing inference issues.
  • Tracker item created - IHTSDO - 834
















Modeling of "Complications and sequela"

2017-03-30

2017-04-25

A proposal for review and revision of the following types of disorders was discussed:

  • Disorders DUE TO another disorder
  • Disorders AFTER another disorder
  • Disorders AFTER a procedure
  • Disorders DUE TO a procedure
  • Disorders DURING a procedure

The initial document was taken through a number of revisions and approved by the Head of Terminology in September, 2017

Complete


In process

Proposed policy: Allowance of Extensions to Modify Core Content

2017-03-30

2017-04-25

Extensive discussion on the interpretation of Clause 4.1 of the SNOMED CT® AFFILIATE LICENSE AGREEMENT. Based on discussions by the EAG members and input from extension managers, a substantial relaxation of the changes extensions may apply to the core, provided the changes are represented in RF2 within the extension moduleID. The essential requirement of no direct changes to the core content components was not changed
  • Jim Case to develop an explanatory document describing what changes are allowed within extensions and the requirement for NRCs to publish disclaimers when potential changes to core content within an edition (combined extension and core content) are present
In process
Policy on acceptance of "Patient-friendly terms" into the International release2017-03-30General agreement that patient-friendly terms are not universal and that the current "dialect " capabilities in SNOMED allow for extension of the core content to accommodate this type of content.
Complete
Combined disorder modeling2016-10-25 to 2017Multiple reviews by the EAG as well as testing of patterns by the editorial staff has been performed. While there are still some difficulties in the consistent representation of combined disorders, due to their very nature, the patterns are being applied to existing content.
Complete
  • No labels