DSTU2 STU 3 Ballot
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is

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

1.7 2.1 Introducing HL7 FHIR Introducing HL7 FHIR

FHIR® – Fast Healthcare Interoperability Resources (hl7.org/fhir) – is a next generation standards framework created by HL7. FHIR combines the best features of HL7's v2
FHIR Infrastructure FHIR Infrastructure Work Group Work Group Maturity Level : N/A Maturity Level : N/A Ballot Status : DSTU 2 Ballot Status : STU 3

FHIR® – Fast Healthcare Interoperability Resources (hl7.org/fhir) – is a next generation standards framework created by HL7. FHIR combines the best features of HL7's v2 , HL7 v3 , HL7 v3 and CDA and CDA product lines while leveraging the latest web standards and applying a tight focus on implementability. FHIR solutions are built from a set of modular components called "Resources". These resources can easily be assembled into working systems that solve real world clinical and administrative problems at a fraction of the price of existing alternatives. FHIR is suitable for use in a wide variety of contexts – mobile phone apps, cloud communications, EHR-based data sharing, server communication in large institutional healthcare providers, and much more. product lines while leveraging the latest web standards and applying a tight focus on implementability.

FHIR solutions are built from a set of modular components called "Resources". These resources can easily be assembled into working systems that solve real world clinical and administrative problems at a fraction of the price of existing alternatives. FHIR is suitable for use in a wide variety of contexts – mobile phone apps, cloud communications, EHR-based data sharing, server communication in large institutional healthcare providers, and much more.

1.7.1 2.1.1 Why FHIR is better Why FHIR is better FHIR offers many improvements over existing standards: A strong focus on implementation – fast and easy to implement (multiple developers have had simple interfaces working in a single day) Multiple implementation libraries, many examples available to kick-start development Specification is free for use with no restrictions Interoperability out-of-the-box– base resources can be used as is, but can also be adapted for local requirements Evolutionary development path from HL7 Version 2 and CDA – standards can co-exist and leverage each other Strong foundation in Web standards– XML, JSON, HTTP, OAuth, etc. Support for RESTful architectures and also seamless exchange of information using messages or documents Concise and easily understood specifications A Human-readable wire format for ease of use by developers Solid ontology-based analysis with a rigorous formal mapping for correctness

FHIR offers many improvements over existing standards:

  • A strong focus on implementation – fast and easy to implement (multiple developers have had simple interfaces working in a single day)
  • Multiple implementation libraries, many examples available to kick-start development
  • Specification is free for use with no restrictions
  • Interoperability out-of-the-box– base resources can be used as is, but can also be adapted for local requirements
  • Evolutionary development path from HL7 Version 2 and CDA – standards can co-exist and leverage each other
  • Strong foundation in Web standards– XML, JSON, HTTP, OAuth, etc.
  • Support for RESTful architectures and also seamless exchange of information using messages or documents
  • Concise and easily understood specifications
  • A Human-readable wire format for ease of use by developers
  • Solid ontology-based analysis with a rigorous formal mapping for correctness

1.7.2 Flexibility 2.1.2 Flexibility A central challenge for healthcare standards is how to handle variability caused by diverse healthcare processes. Over time, more fields and optionality are added to the specification, gradually adding cost and complexity to the resulting implementations. The alternative is relying on custom extensions, but these create many implementation problems too. FHIR solves this challenge by defining a simple framework for extending and adapting the existing resources. All systems, no matter how they are developed, can easily read these extensions and extension definitions can be retrieved using the same framework as retrieving other resources. In addition, each resource carries a human-readable text representation using html as a fallback display option for clinical safety. This is particularly important for complex clinical information where many systems take a simple textual/document based approach.

A central challenge for healthcare standards is how to handle variability caused by diverse healthcare processes. Over time, more fields and optionality are added to the specification, gradually adding cost and complexity to the resulting implementations. The alternative is relying on custom extensions, but these create many implementation problems too.

FHIR solves this challenge by defining a simple framework for extending and adapting the existing resources. All systems, no matter how they are developed, can easily read these extensions and extension definitions can be retrieved using the same framework as retrieving other resources.

In addition, each resource carries a human-readable text representation using html as a fallback display option for clinical safety. This is particularly important for complex clinical information where many systems take a simple textual/document based approach.

1.7.3 2.1.3 Example Resource: Patient Example Resource: Patient This simple example shows the important parts of a resource: a local extension, the human readable HTML presentation, and the standard defined data content. FHIR has resources for administrative concepts such as patient, provider, organization and device as well as a wide variety of clinical concepts covering problems, medications, diagnostics, care plans, financial concerns and more.

This simple example shows the important parts of a resource: a local extension, the human readable HTML presentation, and the standard defined data content.

FHIR has resources for administrative concepts such as patient, provider, organization and device as well as a wide variety of clinical concepts covering problems, medications, diagnostics, care plans, financial concerns and more.

1.7.4 2.1.4 The FHIR development process The FHIR development process FHIR is published as a Draft Standard for Trial Use. During the Trial Use phase, HL7 actively monitors implementations in order to continue to improve the specification, and is able to be responsive to their needs. Due to the many advantages FHIR offers, trial use is already beginning right now. http://hl7.org/fhir . Follow us on Twitter using #FHIR

FHIR is published as a Draft Standard for Trial Use. During the Trial Use phase, HL7 actively monitors implementations in order to continue to improve the specification, and is able to be responsive to their needs. Due to the many advantages FHIR offers, trial use is already beginning right now.

http://hl7.org/fhir © HL7.org 2011+. FHIR DSTU2 (v1.0.2-7202) generated on Sat, Oct 24, 2015 07:44+1100. Links: Search . Follow us on Twitter using #FHIR | Version History | Table of Contents | Compare to DSTU1