2018-10-09 - SNOMED on FHIR Meeting (TS)

2018-10-09 - SNOMED on FHIR Meeting (TS)

Date

20:00 UTC on Tuesday 9 October 2018 - 90 minutes.

Objectives

  • FHIR Terminology Services and Resources

Meeting Details

Onlinehttps://snomed.zoom.us/my/snomedhl7

Phone: See https://zoom.us/zoomconference for available phone numbers (meeting id 242-348-6949)

Chathttps://chat.snomedtools.org/channel/snomed-fhir
          (instructions and guide here - Getting Started with Rocket Chat)

 

Attendees

@Peter Williams@Dion McMurtrie@Jane Millar@Peter Jordan@Anne Randorff Højen@Former user (Deleted)@Jesse Efron

Apologies

@Rob Hausam,  @Former user (Deleted)

Meeting Recording

https://snomed.zoom.us/recording/share/B4EtnQP_VEULDPQYpw50GKNnYanjN4kk5-MQ3oxUDrGwIumekTziMw

Discussion items

Description

Mins

Owner

Notes & Actions

Description

Mins

Owner

Notes & Actions

1

Welcome and introductions

5

@Peter Williams

@Rob Hausam

Recording, notes & attendance.

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

2

October Business Meeting/

Expo - Vancouver

5

@Peter Williams

@Jane Millar

@Peter Williams work with @Rob Hausam to prepare agenda for Business meeting.

Suggestions for additional agenda items.

@Peter Williams to send out pre-meeting reading list with agenda.

3

Summary of previous week

5

@Peter Williams

4

Publication of FHIR Free Set

20

@Peter Williams

Free SNOMED CT set for FHIR

5

Work suggestions from last meeting

40

@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".

RH: FHIR Ballot currently open, closing on 24 September. Published late December/January.

6

SNOMED with FHIR

15

@Rob 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.

Update October 9

7

Main item for discussion

30

@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?)

8

Current items

10

@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?

@Rob Hausam to progress Michael's tracker item on this issue.

@michael lawley to follow up on URIs to Normal form and Normal Form Terse definition
@Rob Hausam to progress returning NormalFormTerse to the page.
  • @Former user (Deleted) 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) :

9

Mechanism for working with Languages.

15

@Reuben 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?

Language reference set could be an implicit code system supplement.

Update 11 September

Do we need a parameter for the expand operation for this - Reuben looking into this currently.

@Peter Jordan to supply material as offered for next meeting - thank you!
10

Valuesets / Refsets

5

 

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

@Daniel Karlsson Done?

11

Any other business

 

 

 

Next Meeting: Tuesday 30 October

Actions for next week:

 

 

Meeting Files

  File Modified
No files shared here yet.

Copyright © 2025, SNOMED International