2018-02-20 - SNOMED on FHIR Meeting (TS)
Date
20:00 UTC on Tuesday 20 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, @Peter Williams, @Jane Millar, @Former user (Deleted), @Anne Randorff Højen, Carmela Couderc, @Former user (Deleted), @Former user (Deleted), @Former user (Deleted), @Michael Hosking, @Peter Jordan, @Reuben Daniels, Anil Patel, @Former user (Deleted)
Apologies
@Daniel Karlsson, @Dion McMurtrie
Meeting Recording
Discussion items
Description | Mins | Owner | Notes & Actions | |
|---|---|---|---|---|
| 1 | Welcome and introductions | 5 | @Peter Williams @Rob Hausam | 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 | @Daniel Karlsson |
Next resource: Specimen |
| 3 | Review of Terms of Reference | 10 | @Jane Millar | @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. No further comments received. Jane will proceed to Member Forum. |
| 4 | Review of "Using SNOMED with FHIR" page
Dicom's usage. | 40 | @Peter Williams | All participants are invited to review this local copy of that page. Suggestion for text since "Legacy SNOMED Identifiers" has been removed: "Please note that antecedant SNOMED codes (e.g. ...) may not be used with the http://snomed.info/sct code system. Please refer to <insert link> for more information." 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. Final Content deadline April 1. Target initial content deadline two weeks prior. Note that http://build.fhir.org/codesystem-snomedct.html has no maturity level and a number of blanks. Also the question of SNOMED CT Attributes updating each release and how could this page/resource be updated? Answer: Resource would be expected to track SNOMED CT ie be updated as required. For next meeting: @Peter Williams See Rory D re suggestion to pull various national editions into separate page since it will change over time. New section for Codes and Displays - pull in Linda P discussion with Michael L. Put forward recommendation for removing "Expressions SHOULD NOT contain terms" Section 4.2.1.0.5 suggestion that we remove both Normal Form properties (Peter J disagreed). Clarity needed on which Normal Form is being represented (eg breaking sufficiently defined concepts down to their primitive components, unlike what is supplied in the browser). Further discussion needed on what these properties are being used for. Perhaps only 1 is necessary since terms can be added/removed as required. GG Suggested separate section for expressions where we'd make the point that original terms should be captured. |
| 5 | CodeSystem & ValueSet identification. | 10 | @Dion McMurtrie | @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 |
| 6 | 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. |
| 7 | Review of proposals for possible Terminology Services and Resources collaborative work | 5 | @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. |
| 8 | Topic for next meeting | 5 | @Peter Williams | Plan for following fortnight:
|
| 9 | Any other business | 0 | @Peter Williams |
|
Meeting Files
Copyright © 2025, SNOMED International