20:00 UTC on Tuesday 12 June 2018 - 90 minutes.
- FHIR Terminology Services and Resources
|Owner||Notes & Actions|
|1||Welcome and introductions||5|
|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.
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|
Review of "Using SNOMED with FHIR" page
All participants are invited to review this local copy of that page.
|8||Review of TS Collaborative Work||5||Collaborative Work|
Any other business
Next Meeting: Tuesday 26 June
Questions for next week: