20:00 UTC on Tuesday 11 December 2018 - 90 minutes.
- FHIR Terminology Services and Resources
|Notes & Actions
|Welcome and introductions
Recording & notes.
|Summary of previous week and previous fortnight
|Publication of FHIR Free Set
Considering question of 'who publishes what', RH thought SI should publish a refset as the authoritative source which HL7 could then use to derive FHIR friendly forms eg Concept Map.
Question for GG: What is the use case for the mapping? This gives context to the question of how (and by whom) the map is maintained.
Agreement being drafted this week for both FHIR and IPS Free Sets (but can be de-coupled if required).
On Hold / Maintenance
|SNOMED FHIR Implementation Guide
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.
|DL Enhancements on PCEs
How can we represent the definition of a concept as a Post Coordinated Expression given that NNF may not fully express the stated form.
MAG work item: DL Enhancements impact on Post Coordinated Expressions
Zulip enquiry has not yet suggested anyone using the returned expressions for anything more involved than straight forward display - although there's no way to be sure.
FHIR property lookup does allow for role grouping by using nested properties (candidate topic for implementation guide! PJ)
Languages group next meeting could be into the new year. MAG meeting 3rd week in January 2019.
|SNOMED with FHIR
All participants are invited to review this local copy of that page.
Update October 9
|Mechanism for working with Languages.
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 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
Language reference set could be an implicit code system supplement.
Update 11 September
Do we need a parameter for the expand operation for this - Reuben looking into this currently.
Any other business
Next Meeting: Tuesday 8 January 2019
Actions for next week: Any suggestions for San Antonio Connectathon January 13 2019?