Difference between revisions of "FHIR"
| Line 13: | Line 13: | ||
* [[FHIR Resource Types]] | * [[FHIR Resource Types]] | ||
* [[FHIR Governance]] | * [[FHIR Governance]] | ||
| + | * [[FHIR Design Requirements Sources]] | ||
* Hot Topics | * Hot Topics | ||
| − | |||
= Implementation Resources = | = Implementation Resources = | ||
* [[Publicly Available FHIR Servers for testing]] | * [[Publicly Available FHIR Servers for testing]] | ||
Revision as of 18:47, 15 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
- The current specification: http://www.HL7.org/fhir/
- gForge home: http://gforge.hl7.org/gf/project/fhir/
- FHIR Resource Types
- FHIR Governance
- FHIR Design Requirements Sources
- Hot Topics
