SNOMED CT Editorial Advisory Group

Page tree

Versions Compared

Old Version 1

changes.mady.by.user Jim Case

Saved on

compared with

New Version 2

changes.mady.by.user Jim Case

Saved on

Key

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

Date: 2019-10-24

0900-1700 MYT (Malaysia time)

1300-1700 UTC

1800 2019-10-27 to 0200 2019-10-28 PDT

Zoom Meeting Details:

Topic: SNOMED Editorial Advisory Group Zoom Meetings

Time: April 8, 2019 1330 UTC

https://snomed.zoom.us/j/3306923098

Time: April 9, 2019 0900 UTC

https://snomed.zoom.us/j/958363815


Attendees

Chair:

AG Members

AG Subgroup chairs






Observers:

Apologies

Meeting Files


Meeting recording

The folder containing the meeting recordings is located here.

Edited transcripts are located here


Discussion items

ItemDescriptionTimeOwnerNotes and DiscussionAction

April 8, 2019

1

Call to order and role call

Notice of recording

Conflicts of Interest

0900-0905 h

Jim Case




Agenda review and approval0905-0910 hJim Case
  •  2019-04 Agenda approved

ECE Update0910-hBruce Goldberg
  • Follow-up discussion of injury, traumatic and non-traumatic

Injury_damage_traumatic_nontraumatic.pptx

EAG agreed that use of DUE TO Event was a preferred way to represent "Traumatic injury"

Additional discussion on approach to handle "non-traumatic injury" needed

  • Secondary disorders

Secondary disorders including gout caused by drug.pptx

Qry_Bruce usage report.xlsx

  •  BGO to write up proposal to use DUE TO Event to model "Traumatic injury"
  •  BGO to test use of GCIs to represent "Secondary disease"
  •  BGO to test alternative model for gout removing the relationship to hyperuricemia.

Clinical content "Sources of truth"1420 - 1500h

Bruce Goldberg

Jeff Pierson

  • Need to revisit the policy on adding text definitions from other sources
    • Do we need to reference them if we paraphrase?
  • Combined definitions from multiple sources may be required to fulfill the needs of SNOMED
  • SNOMED definitions are not normative, but used to define the meaning of a concept as represented in SNOMED CT.

Break1030-1100 h





1100- hToni Morrison
  • Recognized that some product roles are needed to define other procedures and clinical findings
  • Those needed existing roles can be temporarily modeled using additional axioms
  • Warning language that this is a temporary situation while a more permanent solution is devised will be communicated to the community of practice, MF, CMAG, User-support group and GA(?)
  •  Toni Morrison - to inactivate product roles that are not used to define other concepts.
  •  Toni Morrison to work with KKU to develop a communication plan for existing product roles

Device project introduction1600 - 1615hToni MorrisonSee slides attached

Concept inactivation work group updateh

Paul Amos

Jeff Pierson

  • ething and all of a sudden his favorite concept has disappeared.
  •  Jim Case to work with SI tech team to inactivate existing WAS A relationships
  •  Jim Case to communicate to content team that WAS A relationships no longer have to be maintained
  •  Anne Randorff Højen, Jeff Pierson and Brian Carlsen to begin to develop use cases of concept life cycles and needed historical relationships
  •  Jeremy Rogers to provide examples of existing historical relationships of questionable correctness

Use of hypernyms as descriptionshJeremy Rogers

Concern has been expressed about inactivation and replacement terms that from their modeling indicate that they are hypernyms to the replacement concept. The example given was the inactivation of 398042001|Accidental dural puncture (disorder)| as MAY BE 781129002|Accidental puncture of dura during anesthesia (disorder) | due to its positioning under 33211000|Complication of anesthesia (disorder)|, but without addition of the existing description "Accidental dural puncture".

Editorial guidelines from 2010 provided for hypernyms as long as they were noted in the language refset as "near synonymous (depending on context of use)"; however, the notion of near synonymy was not implemented in RF2 and thus there is currently no way to designate descriptions as broader than.

Current editorial policy states that broader descriptions should be inactivated as "not semantically equivalent" or added with the context of use specified.

Current editorial policy is supported by a position paper (SNOMED International Position on the addition of “Patient-friendly terms” (PFT) to the International release of SNOMED CT)