Difference between revisions of "FHIR"
| Line 5: | Line 5: | ||
[[File:FHIR.png|right|200px|Temporary FHIR logo]] | [[File:FHIR.png|right|200px|Temporary FHIR logo]] | ||
Fast Healthcare Interoperability Resources (FHIR, pronounced "Fire") defines a set of "[[Resource]]s" that represent granular clinical concepts. The resources can be managed in isolation, or aggregated into complex documents. This flexibility offers coherent solutions for a range of interoperability problems. The simple direct definitions of the resources are based on thorough requirements gathering, formal analysis and extensive cross-mapping to other relevant standards. A workflow management layer provides support for designing, procuring, and integrating solutions. Technically, FHIR is designed for the web; the resources are based on simple XML, with an http-based RESTful protocol where each resource has predictable URL. Where possible, open internet standards are used for data representation. | Fast Healthcare Interoperability Resources (FHIR, pronounced "Fire") defines a set of "[[Resource]]s" that represent granular clinical concepts. The resources can be managed in isolation, or aggregated into complex documents. This flexibility offers coherent solutions for a range of interoperability problems. The simple direct definitions of the resources are based on thorough requirements gathering, formal analysis and extensive cross-mapping to other relevant standards. A workflow management layer provides support for designing, procuring, and integrating solutions. Technically, FHIR is designed for the web; the resources are based on simple XML, with an http-based RESTful protocol where each resource has predictable URL. Where possible, open internet standards are used for data representation. | ||
| + | |||
| + | FHIR™ is a registered HL7 Trademark. | ||
= Agendas = | = Agendas = | ||
Revision as of 21:20, 11 February 2013
Contents
Introduction
Welcome to the FHIR™ wiki - the home for the FHIR development team.
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. This flexibility offers coherent solutions for a range of interoperability problems. The simple direct definitions of the resources are based on thorough requirements gathering, formal analysis and extensive cross-mapping to other relevant standards. A workflow management layer provides support for designing, procuring, and integrating solutions. Technically, FHIR is designed for the web; the resources are based on simple XML, with an http-based RESTful protocol where each resource has predictable URL. Where possible, open internet standards are used for data representation.
FHIR™ is a registered HL7 Trademark.
Agendas
FHIR Development Links
FHIR development discussions take place on the FHIR email list FHIR email list subscription instructions, and here on this wiki:
- The current specification: http://www.HL7.org/fhir/
- gForge home: http://gforge.hl7.org/gf/project/fhir/ (subversion: http://gforge.hl7.org/svn/fhir/trunk)
- FHIR Development Process documents FHIR methodology
- Process to create: FHIR resource proposals
- List of Discussion pages:
Governance
Hot Topics
The following discussions are likely to be of interest to most FHIR participants
- FHIR Project planning
- FHIR Resource Considerations
- FHIR Resource Types
- FHIR Governance
- FHIR Design Requirements Sources
- FHIR license
- FHIR Principles
Implementation Resources
- Publicly Available FHIR Servers for testing
- Open Source FHIR implementations
- FHIR Connectathon 2 (Jan 12/13, 2013)
- FHIR Connectathon 3 (May 4/5, 2013)
- Skype conversation for implementers (email with skype id to be added) [1]
