This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR"
Jump to navigation
Jump to search
Mark Kramer (talk | contribs) |
|||
Line 57: | Line 57: | ||
**Connectathon Process | **Connectathon Process | ||
***[[FHIR Connectathon Track Process]] | ***[[FHIR Connectathon Track Process]] | ||
+ | ***[[:Category:201801_FHIR_Connectathon_Track_Proposals|Proposed connectathon tracks for New Orleans, USA - Jan 2018]] | ||
***[[:Category:201709_FHIR_Connectathon_Track_Proposals|Proposed connectathon tracks for San Diego, USA - Sept 2017]] | ***[[:Category:201709_FHIR_Connectathon_Track_Proposals|Proposed connectathon tracks for San Diego, USA - Sept 2017]] | ||
***[[:Category:201705_FHIR_Connectathon_Track_Proposals|Previous connectathon tracks for Madrid, Spain - May 2017]] | ***[[:Category:201705_FHIR_Connectathon_Track_Proposals|Previous connectathon tracks for Madrid, Spain - May 2017]] |
Revision as of 21:41, 4 October 2017
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.
Community Participation Rules: FHIR Code of Conduct, FHIR Intellectual Property Rules
FHIR Implementation | FHIR Development | Organizational |
|
|
|