20:00 UTC on Tuesday 6 February 2018 - 90 minutes.
- FHIR Terminology Services and Resources
|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|
|3||Review of "Using SNOMED with FHIR" page||5|
All participants are invited to review this local copy of that page prior to our next Terminology Services meeting.
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.
This weeks Star Topic
Attempt to achieve conclusion:
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.
|6||Review of proposals for possible Terminology Services and Resources collaborative work||10|
See Collaborative Work :
|7||Topic for next meeting||5|
Plan for following fortnight: Focus on 188.8.131.52 Using SNOMED CT with FHIR
|8||Any other business||0|