2018-02-06 - SNOMED on FHIR Meeting (TS)
Date
20:00 UTC on Tuesday 6 February 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, @Dion McMurtrie, @Peter Williams, @Jane Millar, @Former user (Deleted), @Daniel Karlsson, @Former user (Deleted), @Anne Randorff Højen, @Brian Carlsen, @Former user (Deleted), @Former user (Deleted), @Former user (Deleted), Evan Currie, @michael lawley, @Former user (Deleted), @Olof Mattsson, @Peter Jordan, @Reuben Daniels, @Susan Matney, Øyvind
Apologies
Meeting Recording
Discussion items
Description | Mins | Owner | Notes & Actions | |
|---|---|---|---|---|
| 1 | Welcome and introductions | 5 | @Peter Williams | Recording + Notes. Session at April Business Meeting https://www.snomed.org/participate/attend-our-events/ (8 - 11 April) Wed pm. |
| 2 | Summary of previous week | 5 | @Peter Williams | |
| 3 | Review of "Using SNOMED with FHIR" page | 5 | @Peter Williams | 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 20 February 2018. Potential to ballot for Normative Status. Query coming from Grahame G. about how implementable this is eg with cross field validation. Risk of introducing performance issues. Perhaps easier to introduce as "Best Practice" for those with the capability to implement. How constrained should our profiles be eg allowing for non-SNOMED coding? Dion suggested allowing cherry picking from options available. Rob suggested need for expectations of conformance. |
| 4 | 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 |
| 5 | 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? https://www.hl7.org/fhir/capabilitystatement.html vs http://build.fhir.org/terminologycapabilities.html
@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 Suggestion (GG) that we document the minimal acceptable capabilities of a SNOMED FHIR Server. |
| 6 | 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 Egarhos about above. @Peter Williams @Jane Millar @Former user (Deleted) to return to issue of identifiers for legacy versions of SNOMED and respond for 20 Feb. |
| 7 | Topic for next meeting | 5 | @Peter Williams | Plan for following fortnight: Focus on 4.2.1.0 Using SNOMED CT with FHIR
|
| 8 | Any other business | 0 | @Peter Williams | @Jane Millar working on draft Terms of Reference, to be reviewed by The Member Forum (meeting in February) All please review Terms of Reference prior to submission to Member Forum Meeting. @Peter Williams will be away Tuesday 13 February. |
Meeting Files
Copyright © 2025, SNOMED International