Page tree


20:00 UTC on Tuesday 7 January 2020 - 90 minutes.   


  • FHIR Terminology Services and Resources

Meeting Details


Phone: See for available phone numbers (meeting id 242-348-6949) # snomed-hl7-fhir (ask for invite!)


 Rob HausamPeter G. Williams,Michael Lawley


Peter Jordan

Meeting Recording

Discussion items



OwnerNotes & Actions
1Welcome and introductions2

Recording, notes & attendance.

2Summary of previous week and previous fortnight10
3Other Meetings10

Upcoming events: 2 - 3 Feb 2020 HL7 Sydney

SNOMED International involvement: Present Snowstorm, progress for IG & using SNOMED. What FHIR version are we targeting? Snowstorm will be dependent on HAPI implementation.

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

Terminology Services Track Proposal:

  • Peter G. Williams prioritise Terminology Capability Statement also to solve issues with IG publisher tooling issues.

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

San Antonio HL7 Meetings + Connectathon May 16 -17

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

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:

See also

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

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.

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.

  • Peter G. Williams arrange call for this week with DK and RH Tuesday afternoon (RH good before 16:00 UTC). Sample IG may provide clues as to folder location/naming that is publisher compatible.

Currently seeing 4.0.1 unrecognised - PGW to modify.

Daniel's build not generating ValueSets, reason unknown. Possibly related to directory structure not matching expectations in code.

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.


Any other business

Next meeting 21 January 2020. ML Vacation

See ePatient Dave -

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://

See Discussion on Global Patient Set (GPS)

Meeting Files

No files shared here yet.