Difference between revisions of "FHIR"

From HL7Wiki
Jump to navigation Jump to search
Line 73: Line 73:
 
** [[FHIR Ballot Prep]] - tasks for the next ballot and milestone dates
 
** [[FHIR Ballot Prep]] - tasks for the next ballot and milestone dates
 
** [[FHIR Build Process]] - Setting up and running the FHIR build process
 
** [[FHIR Build Process]] - Setting up and running the FHIR build process
 +
** [[FMG Implementation Guide QA Requirements]] - The requirements for FMG to approve an implementation for publishing
 
** [[FHIR Guide to Authoring Resources|How to create resources]] (and [[FHIR Guide to Authoring Types|How to create types]])
 
** [[FHIR Guide to Authoring Resources|How to create resources]] (and [[FHIR Guide to Authoring Types|How to create types]])
 
** Materials: [http://gforge.hl7.org/gf/project/fhir/ gForge issue tracker], [http://github.com/hl7/fhir Source on GitHub]
 
** Materials: [http://gforge.hl7.org/gf/project/fhir/ gForge issue tracker], [http://github.com/hl7/fhir Source on GitHub]
 
*** 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 [[:Category:FHIR_IG_Proposal|Implementation Guide proposals]] - for new resources & implementation guides
+
** [[:Category:FHIR_Resource_Proposal|FHIR resource]] and [[:Category:FHIR_IG_Proposal|Implementation Guide proposals]] - for new resources & implementation guides
 
** [[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 Change requests]] - Process for managing and resolving
 
** [[FHIR Change requests]] - Process for managing and resolving

Revision as of 17:33, 4 October 2018

Temporary FHIR logo

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