20:00 UTC on Tuesday 20 February 2018 - 90 minutes.
- FHIR Terminology Services and Resources
Rob Hausam, Peter G. Williams, Jane Millar, Linda Bird, Anne Randorff Højen, Carmela Couderc, Clark Evans, David Sperzel, Mikael Collin, Michael Hosking, Peter Jordan, Reuben Daniels, Anil Patel, Douglas Deshazo
|Owner||Notes & Actions|
|1||Welcome and introductions||5|
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|
Next resource: Specimen
|3||Review of Terms of Reference||10|
Review of "Using SNOMED with FHIR" page
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.
For next meeting:
CodeSystem & ValueSet identification.
Overlap with FHIR Server capabilities / CodeSystem resource. How do we determine for a given FHIR Server which code systems and versions are supported?
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|
See Collaborative Work :
|8||Topic for next meeting||5|
Plan for following fortnight:
|9||Any other business||0|