2018-03-20 - SNOMED on FHIR Meeting (TS)
Date
20:00 UTC on Tuesday 20 March 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), @Former user (Deleted), @Anne Randorff Højen, @Brian Carlsen, @Former user (Deleted), @Former user (Deleted), @Jane Millar, @Jim Case, @Former user (Deleted), @Peter Jordan, @Reuben Daniels, @Rory Davidson, @michael lawley
Apologies
Meeting Recording
Discussion items
Description | Mins | Owner | Notes & Actions | |
|---|---|---|---|---|
| 1 | Welcome and introductions | 5 | @Peter Williams @Rob Hausam | Recording + Notes. April Business Meeting - SNOMED on FHIR meeting - agenda items? |
| 2 | Summary of previous week | 5 | @Daniel Karlsson @Peter Williams @Rob Hausam | Current focus: Specimen resource |
| 3 | URIs for Edition Modules | 5 | @Peter Williams | Known SNOMED CT Edition Modules now available. It is the member's responsibility to keep SNOMED International updated when new modules are published. @Peter Williams confirm NZ Status |
| 4 | Review of "Using SNOMED with FHIR" page
| 60 | @Dion McMurtrie | 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. @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 terse 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. Next meeting @Former user (Deleted) to create a task for the HL7 Language group to add enhancements (to an expansion) to help with selecting sets of descriptions (LanguageReferenceSet like). @michael lawley suggested specifying an ordered list. https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15806 Supplements are a possible way to allow language reference set type functionality. @Peter Williams update @Rob Hausam re normalFormTerse being added back in. |
| 5 |
|
|
|
|
| 6 | Any other business | 0 | @Peter Williams |
|
Meeting Files
Copyright © 2025, SNOMED International