Page tree
Skip to end of metadata
Go to start of metadata

Date

20:00 UTC on Tuesday 19 May 2020 - 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)

Chatpublic-snomedintl.slack.com # snomed-hl7-fhir (ask for invite!)

Zulip Chat: https://chat.fhir.org/#narrow/stream/179202-terminology

Attendees

 Rob HausamPeter G. WilliamsPeter JordanMichael Lawley

Apologies

Meeting Recording

Discussion items

ItemDescription

Mins

OwnerNotes & Actions
1Welcome and introductions2

Recording, notes & attendance.


2Summary of previous week and previous fortnight5
3Other Meetings10

Upcoming events:

SNOMED International April Business Meeting may or may not happen. In the event of the slot being available, this meeting can go ahead.

San Antonio HL7 Meetings + Connectathon May 16 -17 Cancelled. Virtual connectathon being discussed. Update 7 April: See https://confluence.hl7.org/display/FHIR/2020-05+Terminology+Services+Track

April 14: HL7 FHIR Connectathon is going to run May 13-14-15, a 24 h event. Update 19 May: 677 participants, running continuously over 48 hours. Breakout sessions easier (and more numerous) due to separate Zoom calls. Steer from GG to try to make the designations extension we're working on applicable more broadly to other code systems. Code System Supplements discussed as an alternative mechanism for supplying patient friendly terms. Breakout on federated behaviour & pre-release codes (http://snomed.info/xsct ← this would apply to the version string, rather than the CodeSystem. Discussion continues with the Vocab Workgroup).

FHIR Dev Days also an online event June 15 - 17.

HL7 Baltimore Sept 19 - 25

SI Business + Expo October Lisbon. Discuss SNOMED on FHIR Presentation.

4Use of url parameter15

CodeSystem "class vs instance" in url parameter between CodeSystem and ValueSet operations

CodeSystem is understood.

In Valueset, url is the ValueSet url for example url = http://snomed.info/sct?fhir_vs= allows for the version URI to be used as stated in https://build.fhir.org/snomedct.html The base URL is either http://snomed.info/sct , or the URI for the edition version, in the format specified by SNOMED International in the SNOMED CT URI Specification.

The ValueSet version valueSetVersion is just some string identifier eg a timestamp or 0.1.0

5

GPS and FHIR value set url(s)

15https://chat.fhir.org/#narrow/stream/179202-terminology/topic/Indicating.20in.20a.20ValueSet.20.20SNOMED.20CT.20GPS.20.20Codes
6What module(s) to use for the Canadian Edition10Peter G. Williams
7ECL in the Valueset Expression Extension10

Check whether SNOMED ECL is (or should be) registered as a MIME type (as per RFC 4289/BCP 13), or alternatively added to the expression-language code system and value set, for use in the valueset-expression extension used with the ValueSet resource.

For example, HL7 have registered application/json+fhir

This is useful for a ValueSet extension which allows any language to be used to define the selection criteria for an intensional definition using a MIME type. This group has no current reason to use that extension given the existing core specification support for implicit ValueSet definition and the support within the compose element.

RDF community may have an interest.

8Behaviour on calling the base URL10https://temp-snowstorm.ihtsdotools.org/fhir
9Working with unversioned content15

Proposed example: http://localhost:8080/fhir/ValueSet/$expand?url=http://snomed.info/sct/45991000052106/version/UNVERSIONED?fhir_vs=isa/27624003&designation=sv

ML makes the case that unpublished content is not legitimate SNOMED and suggested using a not-SNOMED URI eg  http://snomed.info/xsct/45991000052106

10FHIR Server Federation

Use case for fall back lookup when server does not know the answer to any particular question eg a façade server which has knowledge of all services it could potentially delegate to.

11Behaviour on Lookup10

What properties are returned?

Discussion: Both Ontoserver and Snowstorm are returning EffectiveTime which is not listed here (unlike other SNOMED specifics): https://build.fhir.org/snomedct.html

Point of interest: Grahame's server returns a copyright property.

Update 7 April - Question about whether this is required / desirable?

12Language Reference Sets in FHIR45All

Mechanisms for working with Languages

Designation extension

Update 19 May: Suggestion that we work an example for SNOMED to discuss with Regenstrief (LOINC)

13SNOMED Family of Languages10

Impact of proposed changes (eg text searching in ECL) on FHIR. Questions around which language reference sets to use when there are multiple, especially partial/overriding context (referred to MAG for discussion)

14SNOMED FHIR Implementation Guide60

Implementation Guide for using SNOMED CT with FHIR.

Update 10 Dec: DK - main problem is URI/Ls which publisher has fixed ideas about. Publisher does not examine all folders - looks in profiles but not subfolders and doesn't seem to look in ValueSet folder.

Update 21 Jan: DK and RH have merged commits and these can be seen in the HL7 server build: http://build.fhir.org/ig/IHTSDO/snomed-ig/branches/new-template/ and build errors here: http://build.fhir.org/ig/IHTSDO/snomed-ig/branches/new-template/qa.html

Update 11 Feb: Grahame said that he'd show us how to set the URI so that it doesn't have to follow the base URI. Next person to try that can we fire a Zulip off to ask about it?

IG Documentation: http://build.fhir.org/ig/FHIR/ig-guidance/index.html

Also look at the sample IG https://github.com/fhir/sample-ig see build http://build.fhir.org/ig/FHIR/sample-ig/

15

Any other business



Next time: Progress worked Designation Extension example for SNOMED, to discuss with Regenstrief with a view to developing a terminology agnostic solution.

Revisit IG


Potential Items for Discussion

Description
OwnerNotes & Actions
API for FHIR Resource ↔ Post coordinated expression mapping

API for FHIR Resource to SNOMED Expression

  • Daniel Karlsson Thought there might be some documentation from CIMI on this. Also notes from DMarkwell about constructor bindings.
  • Peter G. Williams Pull these notes into confluence - can we mention it in the IG?
Looking up an SCTID in an unknown module

Problems when dependencies do not align. Multiple code system resources represent multiple editions / versions.

ML: See code parameter to code system search. Should return code systems (ie versions) where that code is defined. International concepts would appear in every edition known to the server.

eg /CodeSystem?system=htp://snomed.info/sct&code=12345678&_elements=version

GPS

See Discussion on Global Patient Set (GPS)
FHIR Shorthand
Michael Lawley

https://github.com/HL7/fhir-shorthand/wiki

https://build.fhir.org/ig/HL7/fhir-shorthand/FSHQuickReference.pdf

Tooling: https://github.com/FHIR/sushi

$lookup operation - properties returned
Peter Jordan

Using http://ontoserver.csiro.au/vstool/  I noticed that both Ontoserver and SnowStorm return a SNOMED CT $lookup property for effectiveTime, which I don't see listed, as one of the SNOMED CT properties in the FHIR R4 specification at http://hl7.org/fhir/snomedct.html. Should we create a Jira TIcket to add this?

Completed - https://jira.hl7.org/browse/FHIR-26555





Meeting Files

No files shared here yet.