This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR"
Jump to navigation
Jump to search
Line 41: | Line 41: | ||
**[[:Category:FHIR_Connectathons|Historical Connectathons]] (list) | **[[:Category:FHIR_Connectathons|Historical Connectathons]] (list) | ||
**[[Organizations interested in FHIR]] | **[[Organizations interested in FHIR]] | ||
− | **[[Profile | + | **[[Profile Tooling]] |
|valign=top| | |valign=top| | ||
Line 54: | Line 54: | ||
*** For Commit privileges, send a request to lloyd@lmckenzie.com | *** For Commit privileges, send a request to lloyd@lmckenzie.com | ||
**[[:Category:FHIR_Resource_Proposal|FHIR resource and profile proposals]] - proposals for new resources & profiles | **[[:Category:FHIR_Resource_Proposal|FHIR resource and profile proposals]] - proposals for new resources & profiles | ||
− | ** [[FHIR Profile authoring]] - Creating and maintaining FHIR profiles | + | ** [[FHIR Profile authoring]] - Creating and maintaining FHIR profiles (see also [[Profile Tooling]]) |
* Guidelines | * Guidelines |
Revision as of 20:54, 14 September 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 |
|
|
|