2018-01-23 - SNOMED on FHIR Meeting (TS)
Date
20:00 UTC on Tuesday 23 January 2018 - 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: https://chat.snomedtools.org/channel/snomed-fhir
(instructions and guide here - Getting Started with Rocket Chat)
Attendees
@Rob Hausam, @Peter Williams, @Former user (Deleted), @Daniel Karlsson, Carmela Couderc, @Former user (Deleted), @Former user (Deleted), @Former user (Deleted), @Michael Hosking, @michael lawley, @Former user (Deleted), @Olof Mattsson, @Peter Jordan, @Reuben Daniels, Øyvind
Apologies
Meeting Recording
Discussion items
Item | Description | Mins | Owner | Notes & Actions |
|---|---|---|---|---|
1 | Welcome and introductions | 5 | @Peter Williams | Recording + Notes. Requests for calendar invites to pwi@snomed.org Session at April Business Meeting https://www.snomed.org/participate/attend-our-events/ ( 8 - 11 April ) Wed? |
2 | Summary of previous week | 5 | @Peter Williams | |
4 | Review of "Using SNOMED with FHIR" page | 5 |
| All participants are invited to review this local copy of that page prior to our next Terminology Services meeting. @Jane Millar please adjudicate on use of IHTSDO vs SNOMED International. Answer: Legal documents should refer to "IHTSDO". User documentation should use SNOMED International. @Rob Hausam advise on time lines and channel for response All comments to be received by 31 January 2018 |
5 | Deprecated SNOMED RT Identifiers | 10 |
| See URIs antecedent SNOMED versions . RH previously asked "Can we have this in place for the (late) May ballot? Languages group meeting next Wed - 17th." @Peter Williams to take /srt forward for discussion with SNOMED Languages Group (@Former user (Deleted)). |
6 | This weeks Star Topic | 40 | @Dion McMurtrie | Attempt to achieve conclusion: @Dion McMurtrie to ask @Liam Barnes to contribute what is being done for NCTS in Australia @Rob Hausam to provide tracker item for further discussion. GForge tracker #13820 Add explicit parameters to ValueSet $expand value set and code system version https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=13820 |
7 | Terminology Capabilities | 10 | @Dion McMurtrie | Overlap with FHIR Server capabilities / CodeSystem resource? How do we determine for a given FHIR Server which code systems and versions are supported?
@Rob Hausam to supply tracker item on this issue. GForge tracker #14539 The existence of a CodeSystem resource on a server should only be interpreted as a declaration of the code system properties, not as a declaration of server support and expected behavior https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14539&start=0 |
8 | Review of proposals for possible Terminology Services and Resources collaborative work | 10 | @Dion McMurtrie | See Collaborative Work : All - Invitation to fill in capabilities of known FHIR Implementations: Features of Known Servers ( @Linda Parisien ? ). Suggestion that this could be taken forward into SnomedInside (MHosking) @Peter Williams to speak to Nick E about above. |
9 | Topic for next meeting | 5 | @Peter Williams | Plan for following fortnight: CodeSystem.Supplements (ReubenD) eg descriptions in additional languages. Question over what is permissible under SNOMED licence conditions. Feedback from HL7 Meeting / Connectathon |
10 | Any other business | 0 | @Peter Williams | @Jane Millar working on draft Terms of Reference, to be reviewed by The Member Forum (meeting in February) |
Meeting Files
Copyright © 2025, SNOMED International