2017-11-07 - SNOMED on FHIR Meeting
Date
20:00 UTC on Tuesday 7th November 2017
Objectives
To identify overlapping areas of national interest
To consider options for handling semantic overlap
To agree on next steps
Meeting Details
Online: https://snomed.zoom.us/my/snomedhl7
Phone: See https://zoom.us/zoomconference for available phone numbers (meeting id 242-348-6949)
Chat: https://chat.snomedtools.org/channel/snomed-fhir
(instructions and guide here - Getting Started with Rocket Chat)
Attendees
@Former user (Deleted), @Jane Millar, @Rob Hausam
Apologies
Discussion items
Item | Description | Owner | Notes |
|---|---|---|---|
1 | Welcome and introductions | @Former user (Deleted), @Rob Hausam |
|
2 | Background of collaboration and recap of meeting in Bratislava | @Former user (Deleted), @Jane Millar and @Rob Hausam |
|
3 | Review Member Sharing Page and consider national priorities | SNOMED Members |
|
4 | Identify overlap in national interests | SNOMED Members |
|
5 | Consider options for handling semantic overlap | All |
|
6 | Next steps | @Former user (Deleted), @Rob Hausam |
|
Meeting Files
Here's a suggested starting point.
We could define a series of
work items (where we know we need to do something) and
discussions (where we just need to talk, or talk more before we determine if we need to do something).
I'd suggest that these discussions and work items can all happen in parallel and people can sink effort where they have knowledge or interest and time. Different people will be involved in one or more different items/discussions at any given time. I don't think we can use the whole group serially on items/discussions because the areas covered by the union of the various items/discussions is too broad.
We can meet as a whole group to regularly review these work items, create new ones, close existing ones and review progress. The individual items can hopefully be done mostly via the collaborative technologies (wiki and chat), but there's no reason why meetings couldn't be organised for specific topics if the people working on them feel it would help.
The wiki can become a record of how we arrived at the positions we arrived at, and there'll be other places where anything formal we arrive at gets published. Those publications may be part of the FHIR specification changes (e.g. Using SNOMED CT with FHIR) or SNOMED International documentation.
Work items
Review and maintenance of Using SNOMED CT with FHIR page
Changes to SNOMED CT to improve usage through Terminology Services (e.g. implicit ConceptMap metadata)
CodeSystem and ValueSet resource naming and versioning
ConceptMaps for FHIR code systems to SNOMED CT where applicable
Principles and guidance for profiling/binding with SNOMED CT
Reviewing existing base resource bindings
Sharing/collaboration on profiles, ValueSet definitions and bindings - prioritised on Member activity and high maturity resources. This is probably the biggest task and the hardest to manage. It will likely focus on different resources at any given moment.
Create base resource profiles binding SNOMED CT wherever possible, but isn't done in the base resources
Discussions
Setting up and operating centralised (e.g. national, organisational) FHIR terminology repositories
Medication resources for representing drug terminologies
Content syndication
Intensional reference set with simple ValueSet versus intensional ValueSet definition
Maybe we should start adding discussion items and add some work items as tasks that we agree on and have people interested in working on? Then coordinate all this work via this wiki space?