Implementation Guide for using SNOMED CT with FHIR

Assumptions and Audience

Introducing SNOMED to a FHIR audience and FHIR to a SNOMED Audience!Explanation of 4 levels of binding.

Code, Coding, Codeable Concept as specific to SNOMED CT (include link to introduction and points about display terms & multiple languages).

Introduction to using SNOMED with FHIR

• Link to benefits of using SNOMED CT
• Interoperability (synergy in using two world leading standards).
• Distinction between Terminology Services and Binding 
• Linda Bird 's material on choices to be made in selecting elements eg conflict resolution due to overlapping semantics.

• Peter G. Williams copy material from Linda's PPT

SNOMED specific behaviours

• Emphasise use of Code field.
• Links to other SNOMED using profiles (held elsewhere)
• Considerations that were made as part of these profiles
• Pull summary from Dion's validate code page

• Peter G. Williamspull Dion's validate code work.

• Validate code (Valuset and CodeSystem)
• Expand (Valueset)
• Lookup (CodeSystem)
• Search
• Terminology Capabilities Resource (check latest release of HAPI for support?).
  
  

SNOMED Specific profiles (clinical resources)

http://build.fhir.org/profiling.html

Test Suites for using SNOMED with FHIR Servers

• Examples of REST calls and their expected results (using SNOMED where possible), with narrative including any associated business logic.   
• Be sure to make FHIR version and SNOMED CT Edition for each test clear
• Pick SNOMED concepts that aren't likely to be retired any time soon.   Some tests will be more vulnerable than others eg checking the number of concepts subsumed.
• Suggested to use and extend the test scripts used in previous Connectathons.
• Potential to save resources from "Postman" as an aide.

• Peter Jordan please provide examples from previous events as discussed.
  
• Peter Jordan  & Michael Lawley update on in-week discussion.