This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR"
Jump to navigation
Jump to search
| Line 70: | Line 70: | ||
**[[: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 (see also [[Profile Tooling]]) | ** [[FHIR Profile authoring]] - Creating and maintaining FHIR profiles (see also [[Profile Tooling]]) | ||
| + | ** [[FHIR Implementation Guide Authoring]] - Guidelines for setting up a new guide | ||
** [[FHIR Change requests]] - Process for managing and resolving | ** [[FHIR Change requests]] - Process for managing and resolving | ||
** [[FHIR_gForge_Tracker]] - Guidance for using the gForge tracker, including for ballot reconciliation | ** [[FHIR_gForge_Tracker]] - Guidance for using the gForge tracker, including for ballot reconciliation | ||
Revision as of 10:54, 19 November 2015
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 |
|
|
|
