2017-10-17 - SNOMED on FHIR Planning Meeting

Date

9:00am - 12:00pm on Tuesday 17th October 2017 (Bratislava local time)

Meeting Details

Venue: Crowne Plaza, Bratislava, Slovak Republic
Online: https://snomed.zoom.us/my/snomedhl7
Chat: https://chat.snomedtools.org/channel/snomed-fhir
(instructions and guide here - Getting Started with Rocket Chat)

Attendees

Former user (Deleted), Dion McMurtrie, Jane Millar, Rob Hausam, Former user (Deleted), Liara Tutina, Former user (Deleted), Andrew Perry (Unlicensed), Jeremy Rogers (Unlicensed), Lotti Barlow (Unlicensed), Former user (Deleted), Former user (Deleted), Former user (Deleted), Former user (Deleted), Former user (Deleted), Elaine Wooler Ian Spiers, michael lawley, Linda Parisien, Former user (Deleted), Olof Mattsson (Unlicensed), Former user (Deleted), Alejandro Lopez Osornio, Former user (Deleted), Former user (Deleted), Doris McGinness (Unlicensed), Former user (Deleted), Former user (Deleted), Jorn Andre Jorgensen (Unlicensed), Former user (Deleted), Former user (Deleted), Manisha Mantri, Theresa Barry, Kirstine Rosenbeck Gøeg (Unlicensed), Kurt Helenelund, Karl Holmberg, Yongsheng GaoElaine WoolerPeter Williams, Rory Davidson, Jon Zammit, Anne Randorff Højen.

Online / remote: Peter Jordan (Unlicensed), Former user (Deleted), Reuben Daniels, Former user (Deleted), Former user (Deleted)

Apologies

Objectives

To plan, scope and progress collaborative work between SNOMED International Members relating to the use of SNOMED CT with HL7 FHIR

Discussion items

Item	Description	Owner	Notes

Item	Description	Owner	Notes
1	Welcome, introductions and apologies	Former user (Deleted) and Dion McMurtrie	General introductions and welcome
2	Review existing and planned work	Former user (Deleted) and Dion McMurtrie	Members to report on existing and planned work with using SNOMED in HL7 FHIR HL7 International and SNOMED International to report on existing and planned work with using SNOMED in HL7 FHIR
3	Collaborative deliverables and plans	Former user (Deleted) and Dion McMurtrie	Discuss the proposed scope of collaborative deliverables, for example: What format will the deliverables take? Are we providing general guidance for SNOMED CT use, or specific guidance for each resource (or both)? Consider what existing or planned work can be leveraged Who will be doing (and coordinating) the collaborative work? Collaborative platforms for sharing the work as it progresses Communication and meeting requirements
4	Implementation Guidance Principles	Former user (Deleted) and Dion McMurtrie	Discuss the principles we should follow in developing the collaborative deliverables. For example: Is the goal to provide homogeneous population of the resources for interoperability or permissive guidance to cater for a greater degree of localisation? Do we restrict value sets (in a computable way) to ensure that the same information cannot be represented in 2 different ways - for example: The same semantics can/can't be represented both precoordinated and in separate fields The same semantics can/can't be represented in more than one resource (e.g. Condition, Observation, Family History, Allergy Intolerance) How widely do we require/recommend SNOMED CT to be used across the data elements within each resource, versus permitting other code systems to be used? E.g. vital signs, statuses Which are the following are potentially in scope? Restricting existing SNOMED CT value sets already bound to a FHIR resource to subhierarchies that are more semantically appropriate to the relevant data element Defining new SNOMED CT value sets for data elements that do not currently use SNOMED CT Unless they have a required binding to another code system? Restricting the cardinality of data elements (e.g. body site) to reduce ambiguity Splicing data elements to more closely align with the SNOMED CT concept model (only where necessary to avoid ambiguity?) Providing mappings between FHIR value sets (e.g. statuses) and SNOMED CT codes (including context) Providing SNOMED CT expression templates to allow implementations to transform between different ways of populating the same semantics in a FHIR resource
5	Progress work	Former user (Deleted) and Dion McMurtrie	Progress specific work related to SNOMED CT use in FHIR artifacts, for example the SNOMED CT Implementation Guide for the Observation Resource
6	Next steps	Former user (Deleted) and Dion McMurtrie	Discuss next steps, including future meetings and work items