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.
| Topic | Dates of discussion | Recommendation | Action | Action Status | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Laterality | 2015-10-27 |
The decision to add a new attribute was further discussed and the addition of pre-coordinated structures using the existing "LATERALITY" attribute was approved in light of the timeframe for support of nesting. | Add pre-coordinated lateralized body structures to the terminology as needed to fully define concepts in other hierarchies | Implemented | ||||||||
| Phyiscal object as Specimen substance | 2015-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:
| 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: | 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
| Completed | ||||||||
| Application of ECE guidance retrospectively: maintenance of existing descriptions that may be ambiguous | 2015-10-27 | Presentation 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 combine disorder editorial guidance as discovered. | Ongoing | ||||||||
| Unilateral Concepts | 2015-11-30 | No decision at the 2015-10-27 meeting. Additional input from implementers will be sought. 2015-11-30 discussion
|
| In progress | ||||||||
| SNOMED CT Interface or Reference Terminology? | 2015-10-27 | As 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. |
| Completed | ||||||||
| WAS-A relationships | 2015-11-30 | Add 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 FSN | 2016-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 |
| Complete | ||||||||
| Use of URLs in concept definitions | 2016-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. |
| Pending | ||||||||
| Use of Slashes in FSNs | 2016-02-29 | JCA said the final recommendation on use of slashes in FSNs was documented on the discussions page. |
| Complete | ||||||||