2018-08-29 - Full MAG Meeting (Conf call)

Start GTM Recording

Meeting Introduction

@Peter Williams

@Yongsheng Gao

5

Introducing Stefan Schulz.

Reminder to book travel for Vancouver.

DL Enhancements Feedback and Progress

@Yongsheng Gao

@Peter Williams

10

Description Logic Enhancements - Briefing Paper

Roadmap for the DL Enhancements.pptx

• Stated Relationships file becomes invalid in January 2019 although current timeline suggests available for 2 releases. Suggestion for making file available "On Request" ?

• As part of logic profile enhancement, plan for the solution development (including concrete domains), documentation and roadmap for implementation

Update: HS Asked about paper to more widely share the DL Enhancement work (eg for JAMIA, JBI - Add to October agenda)

Classification Service, SNOMED OWL Toolkit and generation of NNF

@Kai Kewley

@Yongsheng Gao

10

Classification Service with documentation available in GitHub

• Makes use of the Snomed Owl Toolkit which is capable of converting SNOMED CT Snapshot files into an OWL ontology file (functional syntax) for use in 3rd party tools such as Protégé.

• Review Necessary Normal Form for Inferred relationships (draft)

Logic Profile Specification

@Dion McMurtrie

10

SNOMED CT Logic Profile Specification

OWL Refset Specification

@Yongsheng Gao

5

OWL Reference Set Specification

OWL refsets preview

Concept model changes and potential impact to extensions

@Yongsheng Gao

10

Inactivation of "Part Of" additional relationships

Topics for the Vancouver Meeting

@Peter Williams

30

• Items from above (include potential paper)

• Universal/Global Edition from SNOMED on FHIR - but more generally relates to any situation where data might span jurisdictions. Major challenge is in unpicking the base dependencies if two or more extensions differed in the version they depend on. List of steps required, or allowances for not fully synchronizing.

• Terminology management evolution - sharing horizontally. Draft specification for terminology exchange format - focussed on editing within an authoring cycle. Next step is an API.

• Refset Metadata (from SNOMED on FHIR Valuesets and TRAG Reference set metadata - can we get use cases here eg Refset Library lookup, Map Reference sets explaining what their target field is pointing to (URI?)).

• Concrete Domains Roadmap View to removing reliance on "Concepts as numbers". After upheaval of moving to OWL Refset work, are we looking at July 2020? AU would wish to delay changes until full solution is available. Representation in the inferred relationship file / equivalent?

• Working with Historical Associations currently concept creators having to shoulder burden of updating all historical relationships to point to active concepts, to ease the complexity on end users.

• Facilitating Namespace Lookups

• Publishing in RDF format - a recommendation for what should be represented, especially for text definitions. Current implementations take different approaches. SI tooling uses FSN - see https://github.com/IHTSDO/snomed-owl-toolkit/tree/develop#stated-relationships-and-axioms. Languages and LangRefsets (assign to Harold).

• Update from the QI Project - moving towards templates, consistency and PPP modelling.

SNOMED URI use case - use module id for browser lookup. Watch that for a period in time a concept could be "live" in two editions during move.

AOB

@Peter Williams