2026-04-15 Full MAG Vienna Hybrid Meeting
Date: Wednesday 15 April 2026 - 0700 UTC (0900 CEST)
Upper Belvedere 2-3
See full schedule here: https://conf.spaces.snomed.org/wiki/spaces/FT/pages/602800143
Breaktime 10:30 CEST
Objectives
Review and agree actions on all currently active work items.
Zoom Details
https://snomed.zoom.us/j/535528933?pwd=clh0d0tPZ1lZcmltaUkzWWlYZmhMdz09
Password: 57851 (not required if using link above)
Attendees
Recording
Discussion items
Description | Owner | Time | Notes |
| |
|---|---|---|---|---|---|
| 1 | Meeting Introduction
| @Peter Williams | 10 | Share Screen. Start recording. Housekeeping - Mics and Movement, New AI Transcript + Summary policy : AI enabled summaries are have been activated and are required as a course of SI business. All summaries will be de-identified in terms of inclusion in post event reports. Previous meeting Membership Changes. Thanks to Kin Wah and Ronald Cornet for their contributions! Welcome to Nicholas Seah (Singapore). Also welcome back Keng Ling Wallin & Jeff Peirson. Communication - ensure members are “watching” the MAG Spaces and Forums. |
|
| 2 | Machine Readable Concept Model | @Peter Williams @Yongsheng Gao | 30 | Discussion on extensions extending the Machine Readable Concept Model. Please read and comment here: https://docs.google.com/document/d/1IB64Jl-jBaTkdW5PhMnGApVwkLg_RYHQZg6S0otAG5w/edit?tab=t.0#heading=h.u1kecoygyvyr See also RF2 Specification: https://docs.snomed.org/snomed-ct-specifications/snomed-ct-release-file-specification/reference-set-release-file-specification/5.2-reference-set-types/5.2.4-metadata-reference-sets/5.2.4.5-mrcm-attribute-domain-reference-set @Yongsheng Gao : Update to Guide URL in MRCM General Agreement that it would simplify SNOMED CT if we removed the Module Scope Refset. | @Peter Williams Progress removal of template column (CC @Chris Swires ) @Peter Williams Discuss broken Guide URLs. Update: Raised https://projects.jira.snomed.org/browse/INFRA-17269 |
| 3 | Fingers vs. Digits of Hand | @Yongsheng Gao | 30 | The early draft of https://docs.google.com/document/d/1nINRoqp2iowWLYNoNw7SLVJkoOTcvUAiwgAKnqafN40/edit?usp=sharing |
|
| 4 | Morphology Hierarchy | Stefan Schulz @Yongsheng Gao Daniel Karlsson | 20 | Ontological Remodelling of the SNOMED CT Morphology Hierarchy https://docs.google.com/document/d/1zFg5AJiNptOrWFz1_4-wQc_UY_S-NXy8tctjsiDeMfA/edit?usp=sharing | @Peter Williams |
| 5 | Coffee Break 10:30 CEST |
| |||
| 6 | Draft Deprecation Policy | @Andrew Atkinson @Suzy Roy | 10 | RESTART RECORDING  |
|
| 7 | Module Dependency Reference Set | @Peter Williams | 30 | Presentation on using the Module Dependent Reference Set: https://docs.google.com/presentation/d/1x2peJDSYmQHGN7anzLUWkRVK2pV7odB-nCo7cktF7VQ/edit?slide=id.g3ce5dcdb046_0_45#slide=id.g3ce5dcdb046_0_45 MDRS Viewer: https://ihtsdo.github.io/sct-implementation-demonstrator/#/mdrs-viewer Community/Product Extensions
|
|
| 8 | Drug Model Discussion | @Yongsheng Gao @Guillermo Reynoso | 45 | Drug Model Discussions https://forums.snomed.org/t/dose-form-intended-sites-vs-routes-of-administration/305 https://docs.google.com/presentation/d/1bVErAvpYiKnFpANVpF0Ipxd-gZN811w03AdmRFAh5ss/edit?usp=sharing |
|
| 9 | Planned Changes, not necessarily prioritized | @Peter Williams | 5 |
|
|
| 10 | Quality Measurement | @Peter Williams | 2 | Question on how we measure quality
| @Peter Williams Create forum post for discussion. |
| 11 | Any Other Business | @Peter Williams | 2 | See topics suggested for the next Joint Advisory Group Meeting. |
|
Items for the Joint Advisory Group meeting October 2026 in Sydney
Description | Owner | Time | Notes |
| |
|---|---|---|---|---|---|
| 1 | Inactivating non-International Concepts | @Peter Williams |
| Reactivating (or inactivating) an international concept in an extension (needs internal discussion first) https://forums.snomed.org/t/non-international-concepts-to-inactivate/1056 Decision criteria? An important use case for inactivating non-international concepts is that some countries are required to translate ALL SNOMED concepts, so this is a unnecessary financial burden, and also linguistically challenging to translate something that may not have an equivalent outside of the originating country. |
|
Related & Future Discussion
Description | Owner | Time | Notes | Action | |
|---|---|---|---|---|---|
| 1 | AOB / Items outstanding | @Peter Williams | 5 | Concept model for a condition without condition (@Jim Case and @Yongsheng Gao) ------------------------------------------ Role Grouping (in the context of BFO harmonization), see Reubmitted Manuscript Post Coordination (impact of DL changes), further ECL filtering. Concept model for conditions caused by substances or products - to be circulated before January @Yongsheng Gao (incl. other AGs and Member Forum) Yong's further items to discuss (quick chat if time allow, or create page to continue)
|
|
| 2 | Refset Descriptor Refset - Mandatory / Optional / Transitivity | @Peter Williams |
| 5.2.4.1 Reference Set Descriptor (Generate page for discussion) |
|
| 3 | Draft Design for Template Publication | @Peter Williams |
| Work in progress: https://docs.google.com/spreadsheets/d/1hOKOu9kxTFvqlgY_Gzc3T-sn8Z-b-d1bH5-Ocn9Sz90/edit?usp=sharing Production templates here: https://github.com/IHTSDO/snomed-templates GR Major Use cases:
DK Points out complexity of generating terms in non-English languages. We agreed to look at additional use cases although existing design allows for use of RegEx and even small chunks of JScript so already quite flexible. GR Description rules are most useful when used with sufficiently defined content. Templated descriptions used with existing International Content could pick up elements from other languages eg use template to help parse the English term parts and translate those in context. GR Would like to see refset sample based on current production templates as per GitHub repo. To be discussed internally @Rory Davidson @Andrew Atkinson |
|
| 4 | Future enhancements to the logic profile |
|
| Negation Disjunction Calculation not currently faster under M1 chip architecture. Note that most of the time taken up by the classification service end-to-end process goes into generating the NNF, which is single threaded. |
|
| 5 | 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 |
|
| 6 | 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 # @Peter Williams Write parent page to capture various options in one place. Add pros/cons. Notify @Andrew Atkinson @Andrew Atkinson to update critical incident policy to list actions based on particular use cases. | Use cases: Two groups: where audit is desired (eg technical issue) and where it is not (IP, un-processable characters)
|