Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This page is under construction

SNOMED CT Editorial Advisory Group (AG) 

Teleconference via GoToMeeting

Attendees:

Chair: Jim Case (JCA)

AG members:

  • Bruce Goldberg (BGO)
  • Keith Campbell (KCA)
  • Paul Amos (PAM)

Presenter: Toni Morrison (TMO)

Observers: Monica Harry, others 

Apologies: 

AG member Guillermo Reynoso (GRE)

Minute-taker: Juliet Gole Krarup, from a recording.

Welcome

JCA welcomed the group. He encouraged everyone (including staff and observers) to go suggest April face-to-face topics via the Discussions page in Confluence. 

Laterality

JCA noted that Robert Turnbull had added some comments about adding QA to the document, and there had also been some comments from Olivier Bodenreider from NLM, to which JCA would respond. 

As only one out of four AG members was on the call at that point (BGO), JCA deferred discussion on laterality and asked TMO to present on Product Strength.

 

 

Product Strength

TMO showed some slides and noted that she, JCA and Ian Green had gone back and forth on various options. 

Early in the presentation, JCA interrupted her to say that KCA and PAM had just joined. 

Slides:

 

On Option #3, JCA said non-human content was moved to an active, non-maintained extension.

KCA said he supported Option #4. Option #5, he said, that would not add new concepts was a bad idea. On option 4, the team could minimize the editing burden by using content from RxNorm. The VA had invested in programs that took RxNorm and transformed it into an extension to SNOMED. It could be automated, though with human QA, and build upon the maintenance already going on with RxNorm. 

JCA asked if the tooling took variability in the naming and transformed it into something regular. KCA replied no, but it took naming from RxNorm that was regular. NLM was okay with their being overlap so the VA was not spending time on reconciling overlap, but the VA could update the FSNs with an algorithmically-generated name that was consistent. 

 

  • No labels