Peter G. Williams

Rob Hausam

Recording & notes.

Peter G. Williams

Rob Hausam

• 2018-12-04 - SNOMED on FHIR Meeting (TB)
• 2018-11-27 - SNOMED on FHIR Meeting (TS)

Peter G. Williams

Free SNOMED CT set for FHIR

• Rob Hausam reach out to Jay and Keith at the VA to elicit use cases / requirements - any update?

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

Peter G. Williams

Collaborative Work

On Hold / Maintenance

• Terminology Binding - Maintenance
• Terminology Services - Maintenance
  • $validate-code behaviour
  • Review and maintenance of Using SNOMED CT with FHIR page
    • 4.2.1.0 Using SNOMED CT with FHIR
      • 4.2.1.0.3 Display
    • Known SNOMED CT Edition Modules
    • Simple map refsets available in SNOMED CT-AU
  • SNOMED CT, post coordination and ValueSet $expand

Peter G. Williams

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.

Peter G. Williams

Peter Jordan

Michael Lawley

Revisit 4.2.1.0 Using SNOMED CT with FHIR

All participants are invited to review this local copy of that page.

• Section 4.2.1.0.5 Clarity needed on which Normal Form is being represented (eg breaking sufficiently defined concepts down to their primitive components, unlike what is supplied in the browser). Further discussion needed on what these properties are being used for. Perhaps only 1 is necessary since terms can be added/removed as required. Update 28 Aug: A link to the definition of NNF is desirable (MAG - define what this should be for PCEs?)
• Supplements are a possible way to allow language reference set type functionality.

Update October 9

• SNOMED Query Language? Language group meeting again after October meeting.
• Links for NNF
  • https://confluence.ihtsdotools.org/display/DOCOWL/2.5.+Generating+Necessary+Normal+Form+Relationships+from+the+OWL+Refsets
  • https://confluence.ihtsdotools.org/display/DOCGLOSS/necessary+normal+form

• Peter G. Williams move into Maintenance section. Further discussion could be cross pollinated with the implementation guide. Outstanding question about the guidance on NNF? SnoChilliesserver does return this value, for example.
• Michael Lawley raise tracker item for the removal of this section (link here).
• Rob Hausam to progress.

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.

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?

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.

Next Meeting: Tuesday 8 January 2019

Actions for next week: Any suggestions for San Antonio Connectathon January 13 2019?