This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR"
Jump to navigation
Jump to search
Line 20: | Line 20: | ||
**[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemBrowse&tracker_id=677 FHIR gForge Tracker] for change requests/corrections | **[http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemBrowse&tracker_id=677 FHIR gForge Tracker] for change requests/corrections | ||
**[[FHIR Tools Registry]] - a list of useful tools for FHIR implementers | **[[FHIR Tools Registry]] - a list of useful tools for FHIR implementers | ||
− | + | ** [[FHIR for Clinical Users]] - an introduction to FHIR for non-technical people that will migrate to the specification in the future | |
*FHIR Social media | *FHIR Social media | ||
**FHIR-themed blogs [http://fhirblog.com/ David Hay], [http://thefhirplace.com/ Ewout Kramer], [http://www.healthintersections.com.au/ Grahame Grieve] | **FHIR-themed blogs [http://fhirblog.com/ David Hay], [http://thefhirplace.com/ Ewout Kramer], [http://www.healthintersections.com.au/ Grahame Grieve] |
Revision as of 00:13, 28 March 2014
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. Technically, FHIR is designed for the web; the resources are based on simple XML or JSON structures, with an http-based RESTful protocol where each resource has predictable URL. Where possible, open internet standards are used for data representation.
FHIR Implementation | FHIR Development | Organizational |
|
|
|