Difference between revisions of "FHIR"
| Line 18: | Line 18: | ||
* Each resource has extensive examples | * Each resource has extensive examples | ||
* There are a number of skype conversations about FHIR - one developed to implementers and very closely monitored (send a skype to david.hay25 to be added). This is good for urgent enquiries. | * There are a number of skype conversations about FHIR - one developed to implementers and very closely monitored (send a skype to david.hay25 to be added). This is good for urgent enquiries. | ||
| − | * We are starting to use the [http://stackoverflow.com Stack Overflow] on-line application (use the tag hl7-fhir) as this is a very common source of information for developers, and the information there is very easy to find | + | * We are starting to use the [http://stackoverflow.com/questions/tagged/hl7-fhir Stack Overflow] on-line application (use the tag hl7-fhir) as this is a very common source of information for developers, and the information there is very easy to find |
= Agendas = | = Agendas = | ||
Revision as of 21:03, 12 June 2013
Contents
Introduction
Welcome to the FHIR® wiki - the home for the FHIR development team.
If you're looking for the FHIR specification, you can find it here: http://hl7.org/fhir
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.
More help and Asking Questions
There are a number of ways that you can get specific help when using FHIR, in addition to the specification:
- There is a FHIR FAQ which addresses questions from both business and technical perspectives
- There is a lot of information in this wiki
- The HL7 List server is a good place to ask general questions
- Each resource in the specification has a Community page linked to it
- Each resource has extensive examples
- There are a number of skype conversations about FHIR - one developed to implementers and very closely monitored (send a skype to david.hay25 to be added). This is good for urgent enquiries.
- We are starting to use the Stack Overflow on-line application (use the tag hl7-fhir) as this is a very common source of information for developers, and the information there is very easy to find
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)
- FHIR Connectathon 4 (Sep 21/22, 2013)
- Skype conversation for implementers (email with skype id to be added) [1]
- Organizations interested in FHIR
