|FHIR Infrastructure Work Group||Maturity Level : N/A||Ballot Status : Informative|
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 organized into a set of "modules". Each module represents a different functional area of the specification, and contains:
Broadly, the modules are organized into 3 groups:
Level 1 Basic framework on which the specification is built
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
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:
Finally, one important place to look is the registry of implementation guides , to see whether similar (or identical) requirements have been met.