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
(Created page with "Resources for Health (RFH) is a "fresh look" proposal by Grahame Grieve, made on August 18th, 2011. Resources for Healthcare (RFH) defines a set of "Resources" that represen...")
 
Line 1: Line 1:
 
Resources for Health (RFH) is a "fresh look" proposal by Grahame Grieve, made on August 18th, 2011.
 
Resources for Health (RFH) is a "fresh look" proposal by Grahame Grieve, made on August 18th, 2011.
  
Resources for Healthcare (RFH) 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.  
+
Resources for Healthcare (RFH) defines a set of "[[Resource]]s" 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.  
 
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.  

Revision as of 09:37, 18 August 2011

Resources for Health (RFH) is a "fresh look" proposal by Grahame Grieve, made on August 18th, 2011.

Resources for Healthcare (RFH) 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, RFH 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.

The definition can be found here.