2019-07-15 - Full MAG Meeting (Conf call)

Meeting Introduction

@Peter Williams

8

Start recording

Group membership update.

DL Enhancements

@Yongsheng Gao

40

Implementation of punning

Update @Kai Kewley : The member release browser allows browsing stated form using only axioms - http://member-release-browser.ihtsdotools.org

Edition, Modules and Ontology Import Statement - explained in the OWL Guide.

Concrete Domains 

@Peter Williams

40

Concrete Domains

SNOMED International Proposal for Representing Concrete Domains in RF2

Uses Cases - Drug strength values, Singapore Drug model also uses Booleans for eg "is Manufactured / is Vaccine" (xsd standard states true ,false)

Potential Impact to vendors / NRCs: DM will continue to deliver existing reference set solution and will release new format in parallel. Differences in Drug Model causing more of a problem eg normalisation of concentration. BU: Not too much of an impact to Singapore and US. Singapore talking about changing existential restriction to assist with drug model.

Roadmap: Consultation Summer 2019 targeting first release July 2020 and concepts-as-numbers inactivation July 2021

DL Enhancements impact on Post Coordinated Expressions / ECL

@michael lawley

2

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

Will we start using self grouped attributes in ECL? Will "ungrouped" in ECL still match either grouped or ungrouped?

Answer: this is unchanged. Grouped ECL should already match any attribute type that is NOT "never group".

AOB / Topics for October

Top Level Ontology BFO discussion@Former user (Deleted)

Suggestion to have sub-group - @Former user (Deleted), @stefan.schulz (Unlicensed) , @Daniel Karlsson (Unlicensed) , @michael lawley , @Yongsheng Gao

Refset Metadata

This topic comes from SNOMED on FHIR

Also TRAG item: Reference set metadata See Agenda item 17 and consider in wider context of machine readable metadata item 11

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

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.

Where are we at with this? Checking with @Andrew Atkinson ...

Relationship Grouping

Google Document, editable

Presentation

OWL file with RGs interpreted as includes

Role group issues

Revisit "Negative Delta"

@Peter Williams

At request of EAG - need to revoke/delete a published component. Comments added to Negative Delta.

See TRAG agenda item #

Notify @Andrew Atkinson

Use cases:

Two groups: where audit is desired (eg technical issue) and where it is not (IP, un-processable characters)

1. Removing IP - suggestion to blank out particular field ("~") while leaving row.

2. Conflicting Rows ie no clear state (technical issue, not content) - suggestion to subsequent delta clarifying row.

3. Clinically dangerous historical error in before-previous release.

Review the representation for product role

2019-April-EAG-Product-Roles.pdf

Discussion of options eg move role concepts into a separate module.

General requirement for flexible composition.