Page tree

Versions Compared

Key

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

Date

02/XX/2017

 UTC 

GoToMeeting Details

SNOMED Int'l Editorial Advisory group  
Feb XX, 2017   

 UTC

Please join my meeting from your computer, tablet or smartphone.  
https://global.gotomeeting.com/join/572559549  

You can also dial in using your phone.  
Denmark (Toll Free): 8090 1924  
United States: +1 (224) 501-3217  

Access Code: 572-559-549  

More phone numbers  
Australia: +61 2 9087 3604  
Belgium: +32 (0) 27 00 6378  
Canada: +1 (647) 497-9391  
Denmark: +45 32 72 03 82  
Netherlands: +31 (0) 207 941 377  
New Zealand: +64 9 280 6302  
Spain: +34 932 75 2004  
Sweden: +46 (0) 775 757 474  
United Kingdom: +44 (0) 330 221 0088  

First GoToMeeting? Try a test session: http://help.citrix.com/getready 

Observers:

 

Apologies

Meeting Files

 

View file
nameRelationship group zero.pptx
height250

View file
nameReview of SNOMED CT models for representing allergic conditions.docx
height250

Meeting minutes

Objectives

  • Obtain consensus on agenda items

Discussion items

ItemDescriptionOwnerNotesAction
1Call to order and role callJCA 

 

2Conflicts of interestJCANone. 
3Approval of minutes from 01/20/2017JCA 

 

 
4Drug Model deliverable reviewTMODrug Model Editorial Guide  
5Substance redesign document reviewJCA/TMO

Substance hierarchy redesign

 

 Guidance for creation of new anatomy conceptsJCA

Issue: In some casecases, the representation of FINDING SITE at the proper level of granularity requires multiple body structures. E.g.:

The proposal under consideration is:

"If two body structures are needed to fully define the finding site for a condition, then a combined anatomic structure shall be created to represent that body structure."

For example: A new body structure "Bone structure of distal phalanx of great toe (body structure)" would be created to support the modeling of the concept above.

 
 Editorial guidance on role groupingJCA

Create a table of mandatory grouping of relationships.  Rationale – needed for template based authoring, provides internal consistency of model patterns, allows for batch editing due to consistency.

See initial review from Daniel Karlsson and Yongshen Gao

 
 "X in remission"JCA

Existing tracker: "In remission" disorders

Hold over item from initial meeting in Uruguay. Has been brought up again with a large number of requests for addition of "X in remission" concepts.

Existing Inception document: Modeling "disease in remission"

Document definition: "The period in the course of a disease/condition during which there is temporary lessening or abatement of signs and/or symptoms of the disease."

Based on historical view of "Disease in remission" there are some assumptions:

  1. The disease condition is still present.
  2. The disease is chronic and/or progressive

Prior proposals:

  • Model as situations with the reactivation of 278174000 | Disease phase (attribute) | with allowed values >303105007 | Disease phases (qualifier value) | with necessary changes to this set to align with standard representation of disease phases
  • Leave the concepts in the disorder hierarchy and create a new attribute such as disease activity and include as its range, qualifier values that specifically represent disease activities such as remission, recurrent, relapsing, active, relapsing/remitting, etc.
  • Model disorder X in remission as a child of disorder X and a child of disorder in remission (the latter as a replacement for patient in remission).
  • Extend the set of values under "Courses" to include disease phases and model "Disease in remission" as a subtype of "Disease"

One related issue is the current overlap of concepts under "Courses" and "Disease phases".

Challenge is that disease phases differ with the "type" of disease.

  • Infectious disease
  • Malignant disease
  • Mental an behavioral disorders

Question: Pros and cons of creating type specific phases?

The result of this discussion should be extensible to other patterns of "Disease in X" (e.g. latent disease, relapse, etc.) for which there are several CRS requests outstanding.

 
 Extension of range of SPECIMEN SUBSTANCE to physical objectJCA

Initially discussed in Uruguay, postponed to future meeting

Existing tracker item: IHTSDO-604 Extend the range of "Specimen substance"

Use cases:

  • Physical object as a specimen for environmental and epidemiologcal testing
  • Pharmaceutical/biological products as specimens for sterility and quality assurance

Earlier discussion points:

  • "Device specimen" already allowed and fully defined but uses SPECIMEN SOURCE IDENTITY as the defining relationship. This scenario may work if the range for SPECIMEN SOURCE IDENTITY is extended to Physical object (<)
 
 ECE UpdateBGO

Update on ongoing issues with ECE

 

 

 Aligning SNOMED CT with clinical use casesKCA/JCACarried over from past meetings: High level discussion on whether SNOMED CT is appropriately organized to support the highly variable granularity of content the are influenced by current EHR applications (i.e. single code recording of pre-coordinated content) and newer initiatives that are focused on capturing more structured data (e.g. CIMI, FHIR) 
 Next meetingEAG