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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Next »

Introduction to using SNOMED with FHIR

General Implementation Considerations

SNOMED specific behaviours

Implementing Terminology Services with SNOMED CT

FHIR Frequently Asked Questions

Design Notes specific to Client Applications

Option for "pass-through" terminology requests so that FHIR server acts as proxy for Terminology Server.   Operations such as Expand may need to make calls on to Terminology before collating results.

SNOMED Specific profiles (clinical resources)

Terminology Binding

Test Suites for using SNOMED with FHIR Servers

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

Existing Documentation to Pull In Using SNOMED CT with FHIR

SNOMED CT canonical CodeSystem resource

Comparable Implementation Guides

See also

Child Documents

Feedback for HL7

19 March 2019

These two pages seem to be very similar?

Publishing Notes

4 June - group agreed to target R4 in the first instance but to indicate any future changes inline.   Also (PJ) suggested section on major changes from STU3 to R4 where relevant to SNOMED eg $compose is now $find-matches

2 July - PJ: question over specific content for different stakeholders (FHIR spec does this) and how we present that - separate pages for developers (details) vs architect (integration, general 'use' of terminology services eg off the shelf solution.  Why use the FHIR API at all?) vs business level?

16 July - PJ suggested initial page to target specific stakeholders (jumping off pages).  Compare with FHIR "Getting Started" Page - "see the Overviews: GeneralDevelopersClinical, and Architects"

ML suggestion that we introduce SNOMED "through the lens of FHIR", so stay away from language reference sets and stick with what can be seen directly from FHIR resources.  (But we can have links to the detail & implementation course - PJ)

  • No labels