This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR"
Jump to navigation
Jump to search
JohnMoehrke (talk | contribs) |
|||
| Line 36: | Line 36: | ||
** [[FHIR for Clinical Users]] - an introduction to FHIR for non-technical people that will migrate to the specification in the future | ** [[FHIR for Clinical Users]] - an introduction to FHIR for non-technical people that will migrate to the specification in the future | ||
**[[FHIR User Group]] | **[[FHIR User Group]] | ||
| + | **[[FHIR for Consumers]] | ||
* Social Media on FHIR | * Social Media on FHIR | ||
**FHIR blogs [http://fhirblog.com/ David Hay], [http://thefhirplace.com/ Ewout Kramer], [http://www.healthintersections.com.au/ Grahame Grieve], [http://motorcycleguy.blogspot.com/search/label/FHIR Keith Boone], [https://brianpos.com/ Brian Postlethwaite] | **FHIR blogs [http://fhirblog.com/ David Hay], [http://thefhirplace.com/ Ewout Kramer], [http://www.healthintersections.com.au/ Grahame Grieve], [http://motorcycleguy.blogspot.com/search/label/FHIR Keith Boone], [https://brianpos.com/ Brian Postlethwaite] | ||
Revision as of 21:14, 28 March 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 |
|
|
|
