2019-01-14 - Full MAG Meeting (Conf call)

Start GTM Recording

Meeting Introduction and Agenda Review

@Peter Williams

10

Review:

• Items scheduled for April agenda (see section below)

• "Done" Items

Business Meeting, April in London

@Peter Williams

@Yongsheng Gao

10

We've been challenged to free up time and resources, we have the option to not hold a face to face meeting in April.

Closest overlap - Editorial AG?

Deliverables for April meeting:

• Feedback from January release eg are GCIs consumable and how are their editing capabilities progressing? User feedback perhaps via TRAG?

Demonstrating business value of open ended, future facing non-concrete discussion.

Option for single half day session for April, more time available in October.

Country capability matrix?

Secondary reasons to travel:

Also Dion - TRAG, Member Forum

DL Enhancements Feedback and Progress

@Yongsheng Gao

10

• In the July 2019 release all stated relationships from the previous release will be published as inactive and the complete OWL axiom refset will be the source of truth.

• Update re January release

• Update of SNOMED International Tooling Enhancements

• Archived Documents:

Description Logic Enhancements - Briefing Paper

Will distribute both OWL refsets in single file.

OWL Refset Specification

@Yongsheng Gao

10

Update :

1. Enhancement for syntax restriction

2. Representation of role group in OWL and inferred relationship file

• Current published version of document:

SNOMED CT OWL Guide

Specification for OWL file

@Former user (Deleted)

10

• Requirements and use cases

• Journal paper on SNOMED OWL

Definition status

@Yongsheng Gao

5

Concrete Domains Roadmap

@Yongsheng Gao

10

RoadMap for concrete domains: Concrete Domain

• Achievable timescale

• Changes required / impact to end users

  • External and technical requirements: Concrete Domains

Discuss April agenda

AOB

All

10

Guillermo: DL tooling changes causing issues - somewhat alleviated by use of SNOMED OWL Toolkit. MRCM Refsets are a pain point eg when a domain is widened by NRC - requires 4 new refsets, the changes of which will not update automatically from the International Edition. Interaction of MRCM with OWL classification somewhat "magical". Current process is not working due to lack of inheritance. YG observes that the MRCM input is only required during this transition from Stated Relationships to OWL and will not still be needed

DL Enhancements impact on Post Coordinated Expressions

Also concern for FHIR(TS) see agenda item 7.

Classification Service, SNOMED OWL Toolkit and generation of NNF

@Kai Kewley

@Yongsheng Gao

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)

Refset Metadata

@Peter Williams

This topic comes from SNOMED on FHIR

Also TRAG item: Reference set metadata

In fact, this metadata may be more widely useful when applied to a module.

Use cases: Public Library of Simple Refsets, ?

Two separate situations:

• Human information like what is the refset to be used for, who owns it, etc.

• Missing technical information eg what is the target code system of a map, keys vs data, machine searchable fields.
  
  

Suggestion that we could use the FHIR standard which already defines metadata. DM suggests a JSON format which would be extensible unlike a column based solution.

There is a more general desirable case to be able to annotate various components.

Proximal Primitive Parent modelling vs Immediate Parent

@Dion McMurtrie

@michael lawley

"Modeling Content Using More Than Proximal Primitives (201739)"

Terminology management evolution

@Yongsheng Gao

Items arising from Saturday meetings:

• Guidance for modularisation as a way to share content.

• Future work: Review specification for change set exchange ie content + metadata

• Terminology Server Content Exchange Interface

QA for that module would also need to be shared.

Facilitating Namespace owner lookups

@Peter Williams

Facilitating Namespace Lookups

Use cases:

• Extension maintainer wishes to raise modelling issue with originator of concept

Logic Profile Specification

@Dion McMurtrie

SNOMED CT Logic Profile Specification - Status: Published

Dion - happy with list of datatypes against common classifier capabilities?

Working with Historical Associations

@Peter Williams

Working with Historical Associations

See also TIG 5.2.1.4 Association Reference Set