Page tree

Versions Compared

Key

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

Date

20:00 UTC on Tuesday 21 January 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!)


Discussion items

ItemDescription

Mins

OwnerNotes & Actions
1Welcome and introductions2

Recording, notes & attendance.



2Summary of previous week and previous fortnight10
3Other Meetings10

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

Should we skip 4 February TS during HL7 Meeting? Yes, and we'll re-jig the meetings to bump TS to the 11th.

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

Terminology Services Track Proposal: https://confluence.hl7.org/display/FHIR/2020-02+Terminology+Services+Track

Business Meeting Agenda: https://confluence.hl7.org/display/VOC/Feb+2020+-+HL7+Sydney+WGM+Meeting+Agenda+for+Vocabulary

Priorities for Events: Working with languages, hosting the GPS legally, ConceptMap$translate (new relationship types)

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


4Concept Map - Mapping Relationship5

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.

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.


5Licence conditions of GPS
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 possible cases for a desirable.

  •  Peter G. Williams try out GPS expansion when GPS loaded on MAIN, in other languages.

6SNOMED 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

Discussion that URI is currently not to SI proposed standard eg <urlvalue="http://snomed.info/fhir/StructureDefinition/AllergyIntolerance-FindingFocused" /> (see GitHub)

Options:

  1. Investigate changes to HL7 build tooling (they're unlikely to want to drop the concept of a base URI)
  2. Speak to the SNOMED Languages Group
  3. Leave URI as proposed standard http://snomed.info/fhirX and accept/ignore tooling errors.
  4. Accept (ignore) use of http://snomed.info/fhir/X

Note that top level menu breaks when you drill down to profiles.

  •  Rob Hausam to merge new-template into master branch

Currently seeing 4.0.1 unrecognised - PGW to modify.


7Mechanism for working with Languages.15Reuben Daniels

Mechanisms for working with Languages

DK: Proposed solution for specifying LangRefset will move into the specification once we've proven the concept. ML: Need to tie down the fall back position.


8

Any other business



Next time: Check new language refset features in Snowstorm.

Next meeting 21 January 2020.



Potential Items for Discussion

DescriptionOwnerNotes & 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)

Meeting Files

Attachments