STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times). See the Directory of published versions

FHIR is a platform specification that defines a set of capabilities use across the healthcare process, in all jurisdictions, and in lots of different context. While the basics of the FHIR specification are relatively straight-forward (see the Overviews: General, Developers, Clinical, and Architects), it can still be difficult to know where to start when implementing a solution based on FHIR.

This page provides some guidance to help get new implementers started on their path to successful implementation. Beyond reading the overviews (previous paragraph), where should an implementer start? Generally, an implementer needs to resolve:

The remaining sections provide guidance on specific areas (Foundation, Implementer Support, Security and Privacy, Conformance, Terminology, Linked Data, Administration, Clinical, Diagnostics, Medications, Workflow, Financial and Clinical Reasoning).

In order to help implementers find their way around the specification and answer these questions, it is organised into a set of "modules". Each module represents a different functional area of the specification, and contains:

  • Scope and Index:A description of the content covered by the module, and an index of the important content
  • Use cases: guidance for common uses of the module, and how to approach them. This is a key resource for implementers familiarizing themselves with the FHIR specification
  • Security / Privacy: information
  • Roadmap: Where the content covered by the module is in terms of overall progress (see also, for general information: FHIR Timelines

Broadly, the modules are organized into 3 groups:

  • Infrastructure (bottom rung, and bottom row of boxes)
  • Content (middle rung, and top row of boxes)
  • Reasoning (top rung)

Level 1 Basic framework on which the specification is build

Level 2 Supporting Implementation, and binding to external specifications

Level 3 Linking to real world concepts in the healthcare system

Level 4 Record-keeping and Data Exchange for the healthcare process

Level 5 Providing the ability to reason about the healthcare process

Clinical Reasoning

Decision Support, Clinical Quality Measures

Dependencies between the modules are mainly downwards, with some horizontal dependencies. Implementers should choose the content modules to engage with based on their requirements, and should only engage with the reasoning module if they need to do clinical decision support, and/or Quality Measures.

In addition to the use case based assistance in the modules, these additional documentation pages may be useful:

  • Common Use Cases: Personal Health Record, Document Sharing (XDS) and Decision Support
  • Resource Guide: Further information about the resources and the relationship between them

Finally, one important place to look is the registry of implementation guides , to see whether similar (or identical) requirements have been met.