Date
20:00 UTC on Tuesday 10 December 2019 - 90 minutes.
Objectives
- FHIR Terminology Services and Resources
Meeting Details
Online: https://snomed.zoom.us/my/snomedhl7
Phone: See https://zoom.us/zoomconference for available phone numbers (meeting id 242-348-6949)
Chat: public-snomedintl.slack.com # snomed-hl7-fhir (ask for invite!)
Discussion items
| Item | Description | Mins | Owner | Notes & Actions | |
|---|---|---|---|---|---|
| 1 | Welcome and introductions | 2 | Recording, notes & attendance. | ||
| 2 | Summary of previous week and previous fortnight | 10 |
| ||
| 3 | Other Meetings | 10 | 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 http://snomed.org/ui Terminology Services Track Proposal: https://confluence.hl7.org/display/FHIR/2020-02+Terminology+Services+Track
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 SNOMED on FHIR Christmas Break: Skip 24 + 31 Dec. Enjoy the break! | ||
| 4 | Concept Map - Mapping Relationship | 5 | 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/projects/FHIR/issues/FHIR-22632?filter=allopenissues 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. | ||
| 5 | Licence 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.
| ||
| 6 | SNOMED FHIR Implementation Guide | 60 | 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.
| ||
| 7 | Mechanism for working with Languages. | 15 | Reuben Daniels | ||
| 8 | Any other business | Next meeting 7 January 2020. PJ away. See ePatient Dave - https://www.ted.com/speakers/dave_debronkart |
Potential Items for Discussion
| Description | Owner | Notes & Actions |
|---|---|---|
| API for FHIR Resource ↔ Post coordinated expression mapping | API for FHIR Resource to SNOMED Expression
| |
| 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