This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "FHIR"

From HL7Wiki
Jump to navigation Jump to search
Line 11: Line 11:
 
* The current specification: [http://www.HL7.org/fhir/ http://www.HL7.org/fhir/]
 
* The current specification: [http://www.HL7.org/fhir/ http://www.HL7.org/fhir/]
 
* gForge home: [http://gforge.hl7.org/gf/project/fhir/ http://gforge.hl7.org/gf/project/fhir/]
 
* gForge home: [http://gforge.hl7.org/gf/project/fhir/ http://gforge.hl7.org/gf/project/fhir/]
 +
* List of Discussion pages:
 +
** [[:Category:Active FHIR Discussion|Active]]
 +
** [[:Category:FHIR Discussion|All]]
 +
 +
== Hot Topics ==
 +
The following discussions are likely to be of interest to most FHIR participants
 
* [[FHIR Project planning]]
 
* [[FHIR Project planning]]
 
* [[FHIR Resource Types]]
 
* [[FHIR Resource Types]]
Line 16: Line 22:
 
* [[FHIR Design Requirements Sources]]
 
* [[FHIR Design Requirements Sources]]
 
* [[FHIR license]]
 
* [[FHIR license]]
* Hot Topics
+
 
  
 
= Implementation Resources =
 
= Implementation Resources =

Revision as of 03:57, 26 May 2012

Introduction

Fast Healthcare Interoperability Resources (FHIR, pronounced "Fire" defines a set of "Resources" that represent granular clinical concepts. The resources can be managed in isolation, or aggregated into complex documents. This flexibility offers coherent solutions for a range of interoperability problems.

The simple direct definitions of the resources are based on thorough requirements gathering, formal analysis and extensive cross-mapping to other relevant standards. A workflow management layer provides support for designing, procuring, and integrating solutions.

Technically, FHIR is designed for the web; the resources are based on simple XML, with an http-based RESTful protocol where each resource has predictable URL. Where possible, open internet standards are used for data representation.

FHIR Development Links

Hot Topics

The following discussions are likely to be of interest to most FHIR participants


Implementation Resources

Workgroup pages