Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 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 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 hierarchiesImplemented
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:

Jira
serverIHTSDO JIRA
serverIdb202d822-d767-33be-b234-fec5accd5d8c
keyDRUGS-49

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
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 relationshipPending batch update