SNOMED on FHIR

Space shortcuts

Page tree

Versions Compared

Old Version 1

changes.mady.by.user Linda Bird

Saved on

compared with

New Version Current

changes.mady.by.user Linda Bird

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

19:00pm 00am - 312:00 pm 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

Linda Bird, Dion McMurtrie, Jane Millar, Rob Hausam, Pim Volkert, Liara Tutina,  Mikael Collin, Andrew Perry, Jeremy Rogers, Lotti Barlow, Ross Boswell, Monika Geletová, Patricia Khandlova, Libor Seidl, Agnieszka Suchodolska, Elaine Wooler, Ian Spiers, Michael Lawley, Linda Parisien, Ron Parker, Olof Mattsson, Mikael Collin, Alejandro Lopez Osornio, Harold Solbrig, Olivier Bodenreider, Doris McGinness, Philip Chuang,  Marianne Bartvedt van Os, Jorn Andre Jorgensen, user-4474d, Johannes Gnaegi, Manisha Mantri, Theresa Barry, Kirstine Rosenbeck Gøeg, Kurt Helenelund, Karl Holmberg, Yongsheng Gao, Peter G. Williams, Rory Davidson, Jon Zammit, Anne Randorff Højen.

Online / remote: Peter Jordan, Grahame Grieve, Reuben Daniels, Wong Leong Hui, Alexander Henket

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

ItemDescriptionOwnerNotes
1Welcome, introductions and apologies

Linda Bird and Dion McMurtrie

  •  General introductions and welcome
2Review existing and planned work

Linda Bird

Review the scope of

and Dion McMurtrie

  • Members to report on existing and planned work
by Members
  • with using SNOMED in HL7 FHIR
  • HL7 International and SNOMED International to report on
Review the scope of
  • existing and planned work
by HL7 International and SNOMED International
  • with using SNOMED in HL7 FHIR
3Collaborative deliverables and plans

Linda Bird 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
4Implementation Guidance Principles

Linda Bird 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
(precoordinated or in separate fields
    • - 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
5Progress work

Linda Bird 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
6Next steps

Linda Bird and Dion McMurtrie

  • Discuss next steps, including future meetings and work items

 

Meeting Files

Attachments

 

Previous Meetings

Content Report Table
maxResults12
showCommentsCounttrue
spaces@self
labelsmeeting-agenda