Page tree

Versions Compared

Key

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

Date

08/xx/2019

 1900-2100 UTC 

2019-08-28

 1700-1830 UTC

 1800-1930 BST

 1000-1130 PDT 

GoToMeeting Details

Topic: SNOMED EAG Conference Call
Time: Aug 28, 2019 10:00 AM Pacific Time (US and Canada)

Join from PC, Mac, Linux, iOS or Android:
https://snomed.zoom.us/j/941587975

Meeting ID: 941 587 975

International numbers available: https://zoom.us/u/aNKqXbcBe

GoToMeeting Details



Meeting Files:


Meeting minutes:

The call recording is located here.

The edited transcript is located here.

Objectives

  • Obtain consensus on agenda items

Discussion items

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 epidemiological 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 (<)

Discussion:

Given that "devices" submitted as specimens are sufficiently defined by using the relationship SPECIMEN SOURCE IDENTITY = <<Device, extending the range of SPECIMEN SOURCE IDENTITY to include <Physical object would allow for new specimen concepts that were not devices to be modeled.
ItemDescriptionOwnerNotesAction
1Call to order and role callJCA


 

2Conflicts of interestJCANone. 
3Approval of minutes from April 2019 Business meetingJCAAs of the start of the meeting quorum did not exist. Could not approve.

 

4TMO

Drug Model Editorial Guide

Received 51 comments from six countries on the initial draft of the editorial guidelines for modeling and terming drugs. All issues identified were resolved or deferred.

Second iteration of guidelines released in early March.

 

5Substance redesign document reviewJCA/TMO

Substance hierarchy redesign

Substance disposition proposal (see attached document)

Comments from EAG regarding the proposal were sought.

BGO had a question about the use of the HAS DISPOSITION relationship; where would it be used? JCA stated it would be solely used for substances. WRT to substances associated with allergens, how would these be used when the substance had a disposition other than allergen. A substance has a disposition, whether it is being used in another context or not. Disposition is a defining attribute for substances.

  •  Jim Case will prepare a briefing note for the MF to inform them of the proposed changes
6Guidance for creation of new anatomy conceptsJCA

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

Image Removed

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.

Discussion: PAM supported this approach by email. BGO supports this change as well. YGA was asked about his support and he also supported the new guidance.

  •  Jim Case will send a edit to the Editorial guide editor to get this guidance implemented.
  •  Monica Harry to work with technical writer to add this proposed (and accepted) wording to the guide where appropriate.
7Editorial 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

The grouping patterns are currently being defined in the groups of templates, but there has been no general guidance for how relationships should/must be grouped. This would define mandatory grouping as well as addressing exceptions to grouping in particular subhierarchies. These would provide guidance for the templates being created.

This is project that is currently not resourced, but will be put on the list of needed edits for the revision of the editorial guide.

  •  Jim Case will address this when the technical writer comes on board to begin the comprehensive editorial guide review.
8"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 and 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.

Related issue: IHTSDO-407 Frequencies and Courses

Discussion:

BGO reviewed the document and asked about the relationship of remission to "disposition". He sees overlap between those notions. Favors making disease in remission as a subtype of the disease. Also favored a separate "disease in remission" hierarchy (primitive parent). Needs additional discussion in London.

  •  Jim Case A summary of the options for "Disease in remission" from the Inception document and the pros and cons for each including modeling examples will be developed for additional review.
9Extension of range of SPECIMEN SUBSTANCE to physical objectJCA
Edited transcripts are located here
  •   Approval of minutes
4Device project update

View file
nameDevices Project for EAG 28 August 2019.pdf
height250

Discussion:

  • A question arose as to whether attributes that would represent origin/destination or in/out relationships could be generalized for other uses as well. Not always a 1:1 relationship in anatomy.
  • So far, no resolution on how to distinguish between "device" and "equipment". Put on hold for now. Bruce Goldberg recommended getting rid of the distinction within SNOMED CT.


5ECE updateBruce Goldberg

Discussion:

  • Simple co-occurrence - three scenarios where the use of the pattern can be justified. The distinction between syndromes and diseases with multisystem involvement requires that intermediate primitives be used in the latter. The definition being developed was discussed and the scope of what should be included as an approved co-occurrence pattern.
  • Traumatic and non-traumatic injury -
  •  Bruce Goldberg to submit co-occurrence edits to the ed.guide
  •  Bruce Goldberg to test the use of DUE TO "event" and full modeling of condition for pathologic fractures as a result of an underlying condition (e.g. osteoporosis)
6Observables updateDaniel Karlsson
  • What do we mean by "function" in Observable entities?



  • Use of observables to define define findings

Continued to next call...


7

Clinical core content identificationJim Case

At the April London business meeting, it was determined that an approach to the identification of the recommended content of the proposed clinical core be determined by a set of both inclusion and exclusion criteria.

Agreed inclusion criteria:

  • global applicability
  • contextless
  • clinically oriented (including content from foundation hierarchies needed to define concepts)
  • supported by a clinical use case
  • used to align with other terminology standards (e.g. ICD)

Exclusion criteria include:

  • administrative, operational or status concepts
  • situations with explicit context
  • combined disorders
  • Implicit or explicit negations/absence
  • Inverse concepts (cooperative vs uncooperative)
  • Pre-coordination of laterality
  • Pre-coordination of severity
  • Specific top-level hierarchies - all except Pharmaceutical/biological product and Substance are currently passively maintained
    • Environment or geographical location (environment / location)
    • Organism (organism)
    • Pharmaceutical / biologic product (product)
    • Physical force (physical force)
    • Physical object (physical object)
    • Record artifact (record artifact)
    • Social context (social concept)
    • Staging and scales (staging scale)
    • Substance (substance)

Discussion: Additional high level exclusion criteria

  • Need to specifically define what is meant by "clinically-oriented" - again, might be easier to exclude what is not clinically oriented. Focus should relate directly to the "life phase" of the patient or procedures that address the "life-phase" of the patient.
  • How much of the foundation should be actively maintained as part of the clinical core?
  • How much of the international release is empirically defined?
  • Is the potential membership of the "problem list" candidates for the clinical core?
  • Suggested that we focus on those concepts that can have full DL definitions, consistent with a single ontological view

8Findings/disorders and notes from the ICBO conferenceJim Case

Following a panel discussion at the ICBO conference in Buffalo Aug 1-2, an agreement in principle for SNOMED to collaborate with the OBO community was reached. Much of the discussion revolved around the current representation of diseases as subtypes of clinical findings. There is a clear, mutually exclusive separation in BFO and other disease ontologies based on BFO between "diseases", which are specifically dependent continuents and clinical observations (i.e. findings), which are considered occurrents. The challenges in implementing this notion in SNOMED is explained in https://www.academia.edu/26897896/Scalable_representations_of_diseases_in_biomedical_ontologies.

As we had initially discussed, one differentiating feature of what we are calling findings is the notion of temporality, i.e a findings is made at a point in time (an occurrence) whereas a disease is persistent. This is similar to the notions in BFO, but they (and all other disease ontologies) refer to diseases as dispositions (i.e. a realizable entity that is manifested as some abnormal process or structure. For terminologies like SNOMED that do not seek to define diseases, but to identify when a realization of the disease disposition occurs in a patient, this logical representation breaks down.

At the ICBO conference, a paper was presented in which an attempt was made to "BFOize" ICD-10. It was clear to the authors of that paper of the conundrum we face, i.e. that the use of the terms in ICD-10 as dispositions was not appropriate because they had been realized and so they modeled their ICD-10 ontology as processes (i.e. occurrents). This was criticized by a number of the ontologists, but no practical solution to the need for representation of realized dispositions in clinical recording were proposed.

Regardless, it would be of some benefit, in light of our desire to resolve the findings/disorders issue, to attempt to align as closely as possible with top level ontologies. One area where this would be of great use is the move by SNOMED to improve coverage of genomics. This would be greatly enhanced by an ability to integrate with the genome ontology.

A draft document is being developed by members of the MAG as a response to the issues surrounding the lack of alignment between SNOMED and BFO: https://docs.google.com/document/d/1HcBj5bVIg8lB_uyORZU9A_FWKFsw0sxmB6Xg4UYKygk/edit

Discussion:

Neuralgia – finding or disorder.pptx

Findings and Disorders thread.doc

Comments:

Keith Campbell expressed concern regarding "the notion that finding vs diseases may be differentiated by the notion of temporality, I believe there will be great difficulty applying such rules, and it will result in a false dichotomy… And will also result in no practical benefit the use of SNOMED in any way…"



Continued to next call...


9Potential agenda items for KLEAGContinued to next call...
10Next meetingEAG TBD
  •  JCA to test the use of subtypes of Physical object as values for SPECIMEN SOURCE IDENTITY.
10ECE UpdateBGO

Update on ongoing issues with ECE

Discussion:

Complications and Sequellae

Proposal made by BGO to model both "Complications" and "Sequellae" using the combined disorder patterns and following the FSN naming conventions for those concepts. Add descriptions that include the terms "Complication" or "Sequellae" as synonyms (or preferred terms where required) and retire the top level concepts of "Complication" and "Sequellae". This is still being discussed within the ECE. JCA leaned towards eliminating the primitive concept "Complication" due to its inconsistent use and to also look at the relationship of these to "Secondary disorders". Whether this fits with Sequellae needs more discussion. Bruce will update after the next ECE call.

Allergy model:

A revision to the proposed allergy model using the application of the HAS REALIZATION attribute to model "Allergy to X". A quesion about how the current concept model for Substances might impact this proposed model. BGO said he did not think it would have a deleterious effect. There would be some value is using the HAS DISPOSiTION attribute in substances to limit which substances might be used as values for "Allergy to X"; however, this might be an unnecessary complication.

Awaiting additional input from Stefan Shultz on the representation of the top level concepts of hypersensitivity condition, allergic condition and pseudoallergic condition.

 

 

11Aligning 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) 
12Next meetingEAG