Date
20:00 UTC on Tuesday 12 June 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
Dion McMurtrie, Rob Hausam, Peter G. Williams, Jane Millar, Linda Bird, Andrew Perry, Michael Lawley, David Sperzel, Peter Jordan, et al.
Apologies
Meeting Recording
https://snomed.zoom.us/recording/share/-lyfY28XbVbjHF9oHjw2MhKH_YjHxSkEmq-WSMPGhRuwIumekTziMw
Discussion items
Item | Description | Mins | Owner | Notes & Actions |
---|---|---|---|---|
1 | Welcome and introductions | 5 | Recording, notes & attendance. Inclusion of HL7 (Rob Hausam) and SI (Jane Millar) working group representatives. Swapping weeks when missing a week eg July 24 - (ask this on the TB stream also). | |
2 | Summary of previous week | 5 | ||
3 | Zulip discussion on Post Coordinated expressions | 50 | Summary: Expressions filter on CodeSystem Resource - Dion asked Graham about origin of these two items. GG clarified true = permit PCE eg for use in validate-code and similarly for expand. Default = true also. Suggested that expand call should then return every possible post coordinated expression (!!) which is a) hard and b) probably not useful. Such expressions could be available if an expression library had been implemented. However, validate code should handle arbitrary PCEs since this will be a finite set. Note that people do post coordination for other code systems eg UCUM and MIME. Suggestions:
Questions
| |
4 | $validate-code behaviour | 20 | Current behaviour doesn't allow for distinction to be made in responding to quality of term queried. Note: Since server returns display term, if the query just checks for membership then the client could check its term against that returned. This waters down the usefulness of the server but would simplify if functionality is not in the 80% of features required. See GForge issue #17218 (ML's). Also #16586.
| |
5 | Main item for discussion | 60 | SNOMED CT Canonical CodeSystem resource
| |
6 | Current items | 10 |
| |
7 | Review of "Using SNOMED with FHIR" page | 5 | All participants are invited to review this local copy of that page.
| |
8 | Review of TS Collaborative Work | 5 | Collaborative Work | |
9 | Any other business | Next Meeting: Tuesday 26 June Questions for next week: |
Meeting Files