Peter G. Williams

Rob Hausam

Recording, notes & attendance.

Peter G. Williams

Rob Hausam

• 2019-04-16 - SNOMED on FHIR Meeting (TB)
• 2019-04-07 - SNOMED on FHIR Meeting (TS & TB)

Peter G. Williams

Montreal May

Redmond June

Jane Millar

Free SNOMED CT set for FHIR

Green - Grahame to provide feedback for next week

Amber - documents going to Patient Care Group (meeting next week)

• Peter G. Williams Capture Jim's feedback on Red items from meeting recording.

Update 23 April: Terminology Binding group moving on to remaining Valuesets.

Peter G. Williams

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

• ALL Pitch in to Implementation Guide for using SNOMED CT with FHIR

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

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).

• Peter G. Williams reference hosted build in Readme.

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)

• Peter G. Williams install Simplifier
  
• Rob Hausam suggest road map for where our focus should be. Pull in CodeSystem Resource page?
  

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.

Mechanisms for working with Languages

Peter Jordan

Michael Lawley

• 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

Next Meeting: Tuesday 14 May 2019 - Bumped one week due to skipping collision with Montreal

14 May Joint session on Genomics Pilot Michael Lawley