20:00 UTC on Tuesday 23 April 2019 - 90 minutes.
- FHIR Terminology Services and Resources
|Owner||Notes & Actions|
|1||Welcome and introductions||2|
Recording, notes & attendance.
|2||Summary of previous week and previous fortnight||5|
|4||Publication of FHIR Free Set||2|
|5||SNOMED FHIR Implementation Guide||60|
Progressing the SNOMED Implementation Guide and specific guidance of "Best Practice" of using SNOMED with FHIR. Can we include tests for 'correctness' - using existing FHIR Testing platforms?
Tooling: Current tooling appears to be solely command line based. See also Snapper for value set editing (currently STU3).
What is the scope of content for the guide? Targeting "Best Practice" for FHIR Implementers using SNOMED CT. Possible layered approach and potentially strict (for internal record keeping and communication) vs permissive profiles when . General guidance for bindings or specific details on each resource.
Audiences - Developer vs User of implemented services. ML Suggests single entry point document with multiple paths through the documentation.
8 January 2019 Update:
Tooling: Forge (doesn't support R4)
What do we want to say about how SNOMED should be used in FHIR? Eg On the Terminology Services side, start with a narrative and head towards a test script where a particular query is expected (formally) to return a given set of results. Then on the resource side, talking about what particular value sets should be used for specific resources - condition code being a high value. Will we insist that these are SNOMED code or could they be proxy codes eg where a medication is given on a problem list and - in it's presence - indicates the underlying condition but without specifying that explicitly.
Start with a Confluence page for collaborative work and once that's reached some stage of maturity it can be moved into the GitHub repository in a more structured form.
Are we looking at one implementation guide or two? Terminology Server vs Terminology Binding and Profiles.
|6||Mechanism for working with Languages.||15||Reuben Daniels|
On Hold / Maintenance
Any other business
Next Meeting: Tuesday 14 May 2019 - Bumped one week due to skipping collision with Montreal
14 May Joint session on Genomics Pilot Michael Lawley