Welcome and introductions

2

@Peter Williams

@Rob Hausam

Recording, notes & attendance.

Summary of previous week and previous fortnight

10

@Peter Williams

@Rob Hausam

• 2020-01-28 - SNOMED on FHIR Meeting (TB)

• 2020-01-21 - SNOMED on FHIR Meeting (TS)

Other Meetings

10

@Peter Williams

Update: 2 - 3 Connectathon Feb 2020 HL7 Sydney (followed by Business meeting)

Upcoming events:

PJ: R5 may have to wait for San Antonio in May 2020. Suggested breakout session for working with languages (DK expressed interest in dial in for that session). PJ only available on the Sunday.

ML suggested adding in client focus items eg SNOMED UI Demo http://snomed.org/ui

SNOMED International Business Meeting April 5 - 8 SNOMED on FHIR meeting Sunday 5 April

San Antonio HL7 Meetings + Connectathon May 16 -17

FHIR DevDays - June 16-18, 2020 Cleveland, OH

SI Business + Expo October

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

Concept Map - Mapping Relationship

15

@Rob Hausam

See ConceptMap

Update 26 Nov: HL7 close to concluding change. Codes that have a meaning change will have value changed to make the direction clearer. PJ: Will any changes be included in the reference libraries in time for the Sydney meeting?

Update 10 Dec: Topic being decided at the workgroup level for inclusion in R5. New values already in place. Narrower → "Broader than" so we'll now read source to target. ML suggested either "source" or "target" should be included to avoid assumption of direction being necessary and that "Narrower than target" would avoid reversing the words used.

Update 11 Feb: FHIR does not allow ICD-10 map 'rules' to be included, say as annotations.

Relevant tracker: https://jira.hl7.org/browse/FHIR-22632

See also https://jira.hl7.org/projects/FHIR/issues/FHIR-16364?filter=allopenissues

Note Vocab WG meet every 2 weeks, alternating with FHIR Tracker calls.

Licence conditions of GPS

5

@Daniel Karlsson

Are translations of GPS available? SR: Not official ones, see https://ihtsdo.freshdesk.com/support/solutions/articles/4000146029-can-the-gps-be-translated.

Point made that SI have rights to use extension content as they see fit.

Users of GPS are free to translate as they see fit (it is free to use!) however this will not be endorsed by SI. We could have a discussion about publishing a translation where an member edition already exists.

Spanish and German (being developed by Switzerland and Austria) possible cases for a desirable.

SNOMED FHIR Implementation Guide

60

@Peter Williams

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/

Mechanism for working with Languages.

15

@Reuben Daniels

Mechanisms for working with Languages

11 Feb See Designation extension

Any other business

Next meeting 21 January 2020.

API for FHIR Resource ↔ Post coordinated expression mapping

@Peter Williams

API for FHIR Resource to SNOMED Expression

Looking up an SCTID in an unknown module

@Peter Williams

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)