Page tree
Skip to end of metadata
Go to start of metadata

Date

20:00 UTC on Tuesday 23 April 2019 - 90 minutes.   

Objectives

  • FHIR Terminology Services and Resources

Meeting Details

Onlinehttps://snomed.zoom.us/my/snomedhl7

Phone: See https://zoom.us/zoomconference for available phone numbers (meeting id 242-348-6949)

Chatpublic-snomedintl.slack.com # snomed-hl7-fhir (ask for invite!)


Discussion items

ItemDescription

Mins

OwnerNotes & Actions
1Welcome and introductions2

Recording, notes & attendance.


2Summary of previous week and previous fortnight5
3Other Meetings0

Montreal May

Redmond June

4Publication of FHIR Free Set2

Free SNOMED CT set for FHIR

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.

5SNOMED FHIR Implementation Guide60

****************

*******************

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.

6Mechanism for working with Languages.15Reuben Daniels
7Ongoing items10
  • SNOMED CT Canonical CodeSystem resource
    • Outstanding question of whether this is the Canonical CodeSystem for the International Edition, or some base set of properties for all Editions.
    • How is this distinct from the Terminology Capabilities Resource?
    • Review and attempt to resolve detail questions
    • Update 28 Aug: Official endpoint should be hosted somewhere (SI?)
    • Update 13 Nov: (ML) We should publish as part of the IG - possibly two - a) International and b) a template as guidance for implementers. In the event of a choice of versions, suggest the default is to return the most recent available.
  • 4.2.1.0 Using SNOMED CT with FHIR

Collaborative Work

On Hold / Maintenance

8

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


Meeting Files

  File Modified
Microsoft Excel Spreadsheet FHIR Connectathon 18 Terminology Formal Tests Version Parameters.xlsx 2019-Apr-23 by Peter G. Williams
Microsoft Excel Spreadsheet FHIR Connectathon 16 - Additional Terminology Server Tests.xlsx 2019-Apr-23 by Peter G. Williams
Microsoft Excel Spreadsheet FHIR Connectathon 17 - Additional Terminology Server Tests.xlsx 2019-Apr-23 by Peter G. Williams
PNG File image2019-1-29_20-18-40.png 2019-Apr-23 by Peter G. Williams
PNG File image2019-1-29_20-15-2.png 2019-Apr-23 by Peter G. Williams