Date
20:00 UTC on Tuesday 24 March 2020 - 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!)
Zulip Chat: https://chat.fhir.org/#narrow/stream/179202-terminology
Discussion items
Item | Description | Mins | Owner | Notes & Actions |
---|---|---|---|---|
1 | Welcome and introductions | 2 | Recording, notes & attendance. | |
2 | Summary of previous week and previous fortnight | 5 | ||
3 | Other Meetings | 10 | 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. FHIR DevDays - June 16-18, 2020 Cleveland, OH (Update 10 March: RD: Go/No Go decision 10 May. DK: US expected to peak late April) SI Business + Expo October | |
4 | Subsumption across code systems | 10 | $subsumes : Snowstorm currently validates (ensures) that codingA and codingB have the same (or no) codesystem. Is subsumption across different code systems a thing? Is there a use case? Answer: Only if there was a map, and even then the proposed restrictions to "broader/narrower" would not allow you to do that. How about between two different editions of SNOMED? Tricky. Other implementations require the module and the version to be the same. $closure however could allow managment of codes from different CodeSystems. | |
5 | Behaviour on Lookup | 10 | 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. | |
6 | Language Reference Sets in FHIR | 45 | All | |
7 | SNOMED Family of Languages | 10 | 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) | |
8 | 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. 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/
| |
9 | Any other business |
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) | ||
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