On This Page:
|Fast Healthcare Interoperability Resources (FHIR™) defines a set of 'resources' to represent health and healthcare administration-related information. These resources express granular clinical and administrative concepts that can be electronically exchanged in order to quickly and effectively solve system interoperability problems in healthcare and related processes. The resources cover the basic elements of healthcare - patients, admissions, diagnostic reports, medications and problem lists - with their typical data elements and also support a range of richer and more complex clinical models. The simple direct definitions of the resources are based on thorough requirements gathering, formal analysis and extensive cross-mapping to other relevant standards.|
- If this is your first time here, read the high level summary and then the Roadmap / Introduction
- See how common scenarios are implemented using FHIR
- In addition to this web site, you can download a zip of the whole specification for off-line use, or access the book form
- Get a list of the resources defined by FHIR, or see the full table of contents
- Translations of FHIR: Japanese
- FHIR Schemas & Schematrons, XML Examples and JSON examples, and the Validator
- Reference implementations & processable definitions
- FHIR wiki - home for the FHIR development team. Implementation questions can be asked on Stack Overflow using the [hl7_fhir] tag (see here for guidance on when to use StackOverflow)
- Publicly Available Test Servers & Clients (note that the servers are not always current with this specification - cross-check the versions in their conformance statements with this spec (v0.09))
FHIR Resource definitions developed by HL7 are derived from the considerable collective experience of the HL7 membership and wide community feedback from the development and application of a spectrum of health care interoperability solutions. However, Resource definitions are generalized to support multiple contexts of use. It is the responsibility of the persons or organizations using these Resources to ensure their use is fit for the particular purpose in which they are used, including validation for clinical and operational use.
FHIR is being balloted as a Draft Standard for Trial Use. A complete description of the rules for DSTU can be found in HL7's Governance and Operations Manual. However, the essential points for implementers are covered below:
The purpose of this phase in the approval process is to gain real-world implementation experience based on a vetted, approved version of the specification prior to locking any particular aspect of the specification "in stone". This specification makes a number of statements about what HL7 will and will not do in future versions of this specification. These statements generally concern expectations around forward and backward compatibility and how the specification will evolve. However, these statements only hold once the specification is approved as a "normative" standard - the approval process that will occur subsequent to DSTU. Between different DSTU versions and between the DSTU and final approved normative version of the specification and its resources, these rules around compatibility and other issues will not be enforced. Elements may be renamed, moved, dropped or otherwise changed. Extensions may be promoted to core elements and core elements may be demoted to extensions. Wire syntax and invocation sequences may be changed. Other breaking changes may occur.
Major changes are not expected, however the risk does exist. If they occur, such changes will not be undertaken without good supporting rationale. However, long term implementability and usefulness of the specification will receive greater weight when evaluating change than impact on existing DSTU implementations. DSTU implementers should therefore provide flexibility in their architecture that will allow them to more easily accommodate changes to the specification. They should also consider how their implementations might peacefully coexist with implementations of future DSTU and normative versions that may not be fully compatible.
FHIR plain English license:
- FHIR is © and ® HL7. The right to maintain FHIR remains vested in HL7
- You can redistribute FHIR
- You can create derivative specifications or implementation-related products and services
- Derivative Specifications cannot redefine what conformance to FHIR means
- You can't claim that HL7 or any of its members endorses your derived [thing] because it uses content from this specification
- Neither HL7 nor any of the contributors to this specification accept any liability for your use of FHIR
Note: Why not use a standard open source license? We'd like to use Creative Commons or a license listed here, but none of them actually deliver on the plain English intent above in important ways. We aspire to meet these requirements from the Open Source Initiative, though patents are a problem.
While we resolve the questions around the long term license, the following license, adapted from the OMG (thanks for allowing this), applies:
Subject to all of the terms and conditions below, HL7 hereby grants you a fully-paid up, non-exclusive, non-transferable, perpetual, worldwide license (without the right to sublicense) to use this specification to create and distribute software and special purpose specifications that are based upon this specification and to use, copy and distribute this specification as provided under the United States Copyright Act; provided that:
- both the copyright notice identified above and this permission notice appear on any copies of this specification;
- the use of the specifications is for informational purposes and will not be resold or transferred for commercial purposes;
- no modifications are made to this specification.
This limited permission automatically terminates without notice if you breach any of these terms or conditions. Upon termination, you will destroy immediately any copies of the specifications in your possession or control.
Any unauthorized use of this specification may violate copyright laws, trademark laws, and communications regulations and statutes. This document contains information which is protected by copyright. All Rights Reserved. No part of this work covered by copyright herein may be reproduced or used in any form or by any means--graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and retrieval systems--without permission of the copyright owner.
WHILE THIS PUBLICATION IS BELIEVED TO BE ACCURATE, IT IS PROVIDED "AS IS" AND MAY CONTAIN ERRORS OR MISPRINTS. HL7 MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS PUBLICATION, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF TITLE OR OWNERSHIP, IMPLIED WARRANTY OF MERCHANTABILITY OR WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE OR USE. IN NO EVENT SHALL HL7 BE LIABLE FOR ERRORS CONTAINED HEREIN OR FOR DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, RELIANCE OR COVER DAMAGES, INCLUDING LOSS OF PROFITS, REVENUE, DATA OR USE, INCURRED BY ANY USER OR ANY THIRD PARTY IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
The entire risk as to the quality and performance of software developed using this specification is borne by you. This disclaimer of warranty constitutes an essential part of the license granted to you to use this specification.
HL7 is and shall at all times be the sole entity that may authorize developers, suppliers and sellers of computer software or specifications to use certification marks, trademarks or other special designations to indicate compliance with FHIR. Software developed under the terms of this license may claim compliance or conformance with FHIR if and only if the software compliance is of a nature fully matching the applicable conformance points as stated in the FHIR specification. Software developed only partially matching the applicable compliance points may claim only that the software was based on FHIR, but may not claim compliance or conformance with this specification. In the event that testing suites or processes are implemented or approved by HL7, Inc., software developed using this specification may claim compliance or conformance with the FHIR specification only if the software satisfactorily completes the testing suites.
FHIR is a specification produced by the HL7 Community. Many individuals contribute to the FHIR specification. Of particular note:
- The Editorial team is Grahame Grieve, Ewout Kramer, Lloyd Mckenzie
- The Govenance board is Ron Parker, Woody Beeler, Ewout Kramer, John Quinn and Grahame Grieve
- The Managment board is Lorraine Constable, Jean Duteau, Hugh Glover, David Hay, John Moehrke, Brian Pech, Lloyd McKenzie, Ron Parker and John Quinn
- The following organizations have helped by attending Connectathons: Health Intersections, Furore, Orion Healthcare, GE Healthcare, Mohawk College, Thrasys, HealthFire, Interfaceware, Gordon Point Informatics, NProgram, and Blue Wave
These are recognized outstanding tasks that are yet to be completed. There are many tasks still to be done that are not listed here.
- Improve summary material for non-technical users, particularly a clinically-orientated benefits summary
- Should a resource identify which profile(s) it conforms to? (why?) (related discussion: rules of handling and version dependency)
- What consistent life cycle patterns do we need for resources?
- How to do digital signatures in json? For servers that store json/bson?
- How do we define the Zed resource (or the resource with no name)
- Minor technical issues:
- issue with json lists and datatype choices
- de-anonymize div element?
- Fix problem with schematron paths capturing resources and datatypes used in extensions (by looking for valuexxx)?
- improve path display for schematrons
- Decide what our policy is on including formatting in Excel columns (e.g. italics in formal constraints)
- remove profile bindings from bindings summary (i.e. EntityNamePartQualifier)
- Many presentation improvements for presenting profiles
Additional open issues can be found throughout the text of the specification and on the FHIR active discussions wiki page.
(After 2nd Draft For Comment)
Archived Versions of FHIR
These archives only keep the more significant past versions of FHIR, and only the book form, and are provided for purposes of supporting html diff tools. A full archive history of everything is available through the HL7 gForge archives.
- Version 0.08, Connectathon 2013 May Atlanta. (Diff with current)
- Version 0.06, Second Draft for Comment. (Diff with current)
- Version 0.05, Version for first Draft for Comment ballot. (Diff with current)
- Version 0.01, First Archived Version (During Vancouver WGM), May 14, 2012. (Diff with current)
Warning: FHIR is a draft specification that is still undergoing development prior to balloting as a full HL7 standard
Implementers are welcome to experiment with the content defined here, but should note that the contents are subject to change without prior notice.
© HL7.org 2011 - 2012. FHIR v0.09 generated on Tue, Jun 18, 2013 23:25+1000. License