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 G. Williams, Linda Bird, Lisa Anderson, Anne Randorff Højen, Brian Carlsen, David Sperzel, Grahame Grieve, Jane Millar, Jim Case, Mikael Collin, Peter Jordan, Reuben Daniels, Rory Davidson, Michael Lawley
Apologies
Meeting Recording
Discussion items
Item | Description | Mins | Owner | Notes & Actions |
---|---|---|---|---|
1 | Welcome and introductions | 5 | Recording + Notes. April Business Meeting - SNOMED on FHIR meeting - agenda items? | |
2 | Summary of previous week | 5 | Current focus: Specimen resource | |
3 | URIs for Edition Modules | 5 | Known SNOMED CT Edition Modules now available. It is the member's responsibility to keep SNOMED International updated when new modules are published.
| |
4 | Review of "Using SNOMED with FHIR" page | 60 | 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."
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.
Next meeting
| |
5 | ||||
6 | Any other business | 0 |
Meeting Files