Meeting Introduction

@Peter Williams

5

Start recording

Group membership update.

April meeting April 2020 - SNOMED International Business Meetings

1 x solo session 1330 Tuesday (overlap with GA)

1 x joint with Editorial and TRAG 0900 Wednesday

Expected Attendance - arrive Monday night, leave Wednesday.

Travel budget has been approved, please proceed to book travel and accommodation. See also updated Travel Policy.

Concrete Domains 

@Peter Williams

20

Concrete Domains

SNOMED International Proposal for Representing Concrete Domains in RF2

Roadmap: Specification sign off at the April Business Meeting. implementation ready for Jan 2021 targeting the July 2021 release. Technical preview in Jan 2021.

Guillermo didn't think that Concrete Domains would have too much impact to existing implementations so better to get new work out ASAP to avoid people starting to use concepts as numbers solution.

PH "Not" cases (eg drug that does not contain paracetamol) that does not helped by having booleans in OWL when disjointness is being described. ML: Negation is independent of concrete domains

Recommendations for historical ECL

@Peter Williams

20

Historical Analytics

Volunteers: @Kai Kewley @michael lawley , @Yongsheng Gao , @Daniel Karlsson (Unlicensed) , @Guillermo Reynoso (with an EAG hat on)

YG Suggested that a service could be provided to make implementers lives easier here.

YG: Editorial group are looking at historical associations.

Sorting order for MRCM

@Yongsheng Gao

10

Internal tooling will support maintenance and publication of MRCM Refset. Sorting will help with consistent representation and identifying duplicates. Looking to use the same approach as per OWL expression sorting. See also canonical normalization process documentation.

Specifically the order in which attributes appear (20:40)

Default view will be to go ahead as per precedent set by OWL unless there are strong opinions.

Diagram for MRCM

@Ed Cheetham

20

MRCM diagrams

Deliverables for April Meeting

@Peter Williams

5

Concrete Domains Specification

Concrete Domain Roadmap

Completed Historical Analytics page

Agenda especially for joint session

Any suggestions from MAG members that they think is important - by 15 March please.

GR interested to see a more complete concept model drawing together various parts - Editorial Guide, OWL, MRCM

BFO SubGroup

@Former user (Deleted), @stefan.schulz (Unlicensed) , @Daniel Karlsson (Unlicensed) , @michael lawley , @Yongsheng Gao

15

BFO compatibility of Findings / Disorders / Role Groups

Consolidation internally prior to taking back to BFO.

AOB / Topics for April

0

@Former user (Deleted) annotating concepts in OWL

Consistent interpretation of Role Groups

YG Annotations in OWL and RF2 (link to concept metadata more generally)

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.