SNOMED on FHIR

Space shortcuts

Page tree

Date

20:00 UTC on Tuesday 28 August 2018 - 90 minutes.

Objectives

  • FHIR Terminology Services and Resources

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

Peter G. Williams, Dion McMurtrie, Rob Hausam, Daniel Karlsson, Michael Lawley, Reuben Daniels, Carmela Couderc, Charles E McDonald Jr. (cemcdonald), David Sperzel, Jim Case, Peter Jordan, Linda Bird, Jane Millar

Apologies

Meeting Recording

https://snomed.zoom.us/recording/share/lMuFoEOEczbiOy-vUGHgxPcOkgVr8TtHnooJjNp2qCmwIumekTziMw 

Discussion items

ItemDescription

Mins

OwnerNotes & Actions
1Welcome and introductions5

Peter G. Williams

Rob Hausam

Recording, notes & attendance.

SNOMED on FHIR meeting planned during the business meeting - closed session (observers space dependent).

2October Expo - Vancouver5

Jane Millar

Call for abstract - presentation on the work of this group (2 presenters max).

Update: Rob to do introduction (Jane to supply slides) then Jeremy and Dion to do joint presentation.

3Summary of previous week5

Rob Hausam

4Work suggestions from last meeting40

Dion McMurtrie

Proposals for expand

  • Dion McMurtrie to progress the proposal through Zulip
  • Rob Hausam to create tracker item to socialize this for the next FHIR Release (R5 2019 Q3?) Hold for Zulip discussion.

Options for validate code - mapping between various data issue scenarios and true/false result flag.

  • All to review options. Note that validate code applies to both ValueSet AND CodeSystem. Examples would be helpful, with expected responses (could be used to drive unit tests also).

Note that changes suggested are additive in nature, rather than "breaking".

5SNOMED with FHIR30Rob Hausam

Revisit 4.2.1.0 Using SNOMED CT with FHIR

All participants are invited to review this local copy of that page.

  • Section 4.2.1.0.5 Clarity needed on which Normal Form is being represented (eg breaking sufficiently defined concepts down to their primitive components, unlike what is supplied in the browser). Further discussion needed on what these properties are being used for. Perhaps only 1 is necessary since terms can be added/removed as required. Update 28 Aug: A link to the definition of NNF is desirable (MAG - define what this should be for PCEs?)
  • Supplements are a possible way to allow language reference set type functionality.
6Main item for discussion30

Dion McMurtrie

SNOMED CT Canonical CodeSystem resource
  • Review and attempt to resolve detail questions
  • Issue around extensions and what this CodeSystem resource actually represents

Update: URIs populated. Intention to provide short URLs for normalForm and normalFormTerse to point to appropriate definition of terms.

Update 28 Aug: Official endpoint should be hosted somewhere (SI?)

7Current items10

Dion McMurtrie

  • SNOMED CT "Universal" Edition
    • Definitely useful to have a catalogue of all concepts ever issued if not a proper edition which may be much harder?
    • Is this work for this group, or should this be handed on to a more appropriate SI group?
    • Update 14 Aug - Are we going to shelve this item as not currently practical? Hand to MAG/TRAG?
  • Check and fix ECL in the FHIR spec
    • Is there a way to systematically identify all ECL expressions in the FHIR spec?
    • If we run these through validation is there appetite/volunteers to review and fix them as feedback to the spec?
    • Is there a way to integrate ECL validation into the FHIR spec tooling to prevent recurrence?
  • Linda Bird to progress defining Terse Normal Form with the Family of Languages group (Rob Hausam confirms needed for July)
    • SLPG agreed that the Languages group is not the appropriate forum for this definition. Instead, we believe this should be defined in the DL subgroup of the Modelling Advisory Group.
    • Also agreed that the terms that need defining are "Canonical Normal Form" (which is terse by definition) and "Necessary Long Normal Form"

Update 14 August See draft (doesn't specify particular normal forms) :

8Mechanism for working with Languages.15Reuben Daniels

HL7 Vocab Item: https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15806

ML: Supplement would hopefully only add additional descriptions that are not described in the base content.

Precedence (fallback) for multiple language reference sets only really discussed in Languages Group for ECL - other use cases not yet brought to light.

Update 28 Aug: Keen to see an implementation using Supplements to see how it would actually work. Option to explore this at Baltimore Connectathon?

9

Daniel Karlsson

Daniel Karlsson's question about ValueSets also being published as Reference Sets with additional descriptions.

10

Any other business




Next Meeting: Tuesday 11 September

Actions for next week:



Meeting Files

  File Modified
No files shared here yet.