20:00 UTC on Tuesday 12 February 2019 - 90 minutes.
- FHIR Terminology Services and Resources
Daniel Karlsson (CMAG collision)
|Owner||Notes & Actions|
|1||Welcome and introductions||5|
Recording, notes & attendance. Note HIMMS (Florida) this week.
Note no TB meeting next week, meetings will skip a week.
|2||Summary of previous week and previous fortnight||5|
|4||Publication of FHIR Free Set||20|
On Hold / Maintenance
|6||SNOMED FHIR Implementation Guide||10|
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.
ALL Pitch in to Implementation Guide for using SNOMED CT with FHIR
|7||Mechanism for working with Languages.||15||Reuben Daniels|
ML: Supplement would hopefully only add additional descriptions that are not described in the base content.
Precedence (fallback) for multiple language reference sets only really discussed in Languages Group for ECL - other use cases not yet brought to light.
Update 28 Aug: Keen to see an implementation using Supplements to see how it would actually work. Option to explore this at Baltimore Connectathon?
Update 11 September: Do we need a parameter for the expand operation for this - Reuben looking into this currently.
Update 11 Dec: HTTP Headers RFC 5646 (Tags for identifying languages). Suggestion that where dialects are to be referenced which do no have a standard code, one could be constructed, either using new letters or the language reference set id directly eg en-nz-x-12345601 Note also that requested language/dialect could be an ordered list for gradual fallback where descriptions may or may not be available.
Can also be passed in the language parameter passed to an expansion operation.
Language reference set could be an implicit code system supplement.
Update 8 Jan: Note that SNOMED CT Language Reference sets do not indicate if they relate to a dialect, language or context of use. GG suggested FHIR could address that more directly than using a reference set SCTID to supply that desired context. Include someone in a non-English speaking country!
Any other business
Next Meeting: Tuesday 5 March 2019
Jeff Wilkie (Virg. Tech - Organisms)