Date
20:00 UTC on Tuesday 4 June 2019 - 90 minutes.
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: public-snomedintl.slack.com # snomed-hl7-fhir (ask for invite!)
Attendees
Michael Lawley,Peter Jordan,Rob Hausam, Peter G. Williams, Rory Davidson, Daniel Karlsson, Jane Millar, Jon Zammit, Reuben Daniels, Rhea Sward
Apologies
Meeting Recording
https://snomed.zoom.us/recording/share/dDDi7P0al679Dllx5O_USSBAUshgVVI9BcD-13FOXViwIumekTziMw
Discussion items
Item | Description | Mins | Owner | Notes & Actions |
---|---|---|---|---|
1 | Welcome and introductions | 2 | Recording, notes & attendance. | |
2 | Summary of previous week and previous fortnight | 10 | Note Daniel away for 3 weeks after the 11th so keen to have meeting despite overlap with FHIR Dev Days (FYI Jeremy Rogers ) Jane also away on the 11th | |
3 | Other Meetings | 10 | SNOMED Expo Oct 31 - Nov 1 Kuala Lumpur Thursday half hour session. Title of session: "SNOMED on FHIR" Content: Profiles (eg Allergy Intolerance), Free Set, Implementation Guide, discussing and sharing. | |
4 | Publication of FHIR Free Set | 2 | Green - Grahame to provide feedback for next week Amber - documents going to Patient Care Group (meeting next week)
Update 23 April: Terminology Binding group moving on to remaining Valuesets. | |
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? 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. 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 | Mechanisms for working with Languages Michael Lawley has raised ticket about the "use" field being limited to FSN/Synonym. Elsewhere in FHIR there is a "display" code that can be used to indicate other languages See 22490. Also 19960 - additional term for "Consumer Terms" ready for implementation R5 (Q4 2020 at the earliest). |
7 | Ongoing items | 10 |
On Hold / Maintenance | |
8 | Any other business | Next agenda item with Reuben Daniels : Proposed changes to ConceptMap resource Clarification of the reverse flag in ConceptMap $translate Follow up discussion on finding all refsets that a particular concept is a member of (relates to both ^( << languages refsets) |
Meeting Files