Date
20:00 UTC on Tuesday 30 October 2018 - 90 minutes. NB One hour earlier in both Europe and North America compared to last month due to Summer Time ending!
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)
Discussion items
| Item | Description | Mins | Owner | Notes & Actions |
|---|---|---|---|---|
| 1 | Welcome and introductions | 5 | Recording & notes. | |
| 2 | Summary of previous week and previous fortnight | 5 | ||
| 3 | Publication of FHIR Free Set | 20 | Peter G. Williams |
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). |
| 4 | Options for Validate Code | 1 | Options for validate code - see final position 2018-10-30 - SNOMED on FHIR Meeting (TS) | |
| 5 | 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? https://github.com/IHTSDO/snomed-ig with the built view hosted by GitHub at https://ihtsdo.github.io/snomed-ig/ 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. | |
| 6 | DL Enhancements on PCEs | 10 | 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. | |
| 7 | Work suggestions from last meeting | 10 |
Do we need to park this item until we have some real world use case / examples? Jeremy Rogers ?
| |
| 8 | SNOMED with FHIR | 10 | Revisit 4.2.1.0 Using SNOMED CT with FHIR All participants are invited to review this local copy of that page.
Update October 9
| |
| 9 | Ongoing items | 10 |
| |
| 10 | Mechanism for working with Languages. | 15 | Reuben Daniels | HL7 Vocab Item: https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15806 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? 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.
|
| 11 | Any other business | Next Meeting: Tuesday 27 November Actions for next week: |
Meeting Files