Fast Healthcare Interoperability Resources combines the best features of HL7's v2 , HL7 v3 and Clinical Document Architecture (CDA) product lines while leveraging the latest web standards and applying a tight focus on implementability.
Fast Healthcare Interoperability Resources solutions are built from a set of modular components called "Resources". These resources can easily be assembled into working systems that solve real world clinical and administrative problems at a fraction of the price of existing alternatives. Fast Healthcare Interoperability Resources is suitable for use in a wide variety of contexts – mobile phone apps, cloud communications, EHR-based data sharing, server communication in large institutional healthcare providers, and much more.
Why Fast Healthcare Interoperability Resources is better #FHIR offers many improvements over existing standards:
- A strong focus on implementation – fast and easy to implement (multiple developers have had simple interfaces working in a single day)
- Multiple implementation libraries, many examples available to kick-start development
- Specification is free for use with no restrictions
- Interoperability out-of-the-box– base resources can be used as is, but can also be adapted for local requirements
- Evolutionary development path from HL7 Version 2 and CDA – standards can co-exist and leverage each other
- Strong foundation in Web standards– XML, JSON, HTTP, OAuth, etc.
- Support for RESTful architectures, seamless exchange of information using messages or documents, and service based architectures
- Concise and easily understood specifications
- A human-readable serialization format for ease of use by developers
- Solid ontology-based analysis with a rigorous formal mapping for correctness
Fast Healthcare Interoperability Resources and Authentication#FHIR servers should authenticate the clients. The server may choose to authenticate the client system and trust it, or to authenticate the individual user by a variety of techniques. For web-centric use, OpenID Connect may be used to authenticate users and OAuth may be used to authenticate and/or authorize the users. The Smart-On-FHIR profile on OAuth is tightly integrated with FHIR and is the preferred method for using OAuth.
The HEART Profile is a set of privacy and security specifications that enable an individual to control the authorization of access to RESTful health-related data sharing APIs, and to facilitate the development of interoperable implementations of these specifications by others.
Fast Healthcare Interoperability Resources Classifications#Fast Healthcare Interoperability Resources is a resource that are classified into 6 sections:
- Clinical - The content of a Clinical Data
- Identification - Supporting entities involved in the care process
- Workflow - Manage the healthcare process
- Financial - Resources that support the billing and payment parts of FHIR
- Conformance - Resources use to manage specification, development and testing of FHIR solutions
- Infrastructure - General functionality, and resources for internal FHIR requirements
Fast Healthcare Interoperability Resources Type#We may not have all the Fast Healthcare Interoperability Resources Types but these seemed to be of the most interest.
|Fast Healthcare Interoperability Resources||Description||Link|
|Patient||Demographic information about the patient||http://www.hl7.org/fhir/stu3/patient.html|
|MedicationRequest||Information about requests for medications for patients||http://www.hl7.org/fhir/stu3/medicationrequest.html|
|MedicationDispense||Information about supply of medications to a patient||http://www.hl7.org/fhir/stu3/medicationdispense.html|
|MedicationAdministration||Information about medications consumption or other administration||http://www.hl7.org/fhir/stu3/medicationadministration.html|
|MedicationStatement||Information about the believed state of a medication||http://www.hl7.org/fhir/stu3/medicationstatement.html|
|Observation||Information about observations performed by a healthcare provider||http://www.hl7.org/fhir/stu3/observation.html|
|Appointment||Information about scheduled appointments||http://www.hl7.org/fhir/stu3/appointment.html|
|AllergyIntolerance||Information about allergies and drug intolerance||http://www.hl7.org/fhir/stu3/allergyintolerance.html|
|Condition||Information about a patient's condition||http://www.hl7.org/fhir/stu3/condition.html|
|Immunization||Information about a patient's immunizations||http://www.hl7.org/fhir/stu3/immunization.html|
|CarePlan||Information about a patient's care plan||http://www.hl7.org/fhir/stu3/careplan.html|
|*||Wildcard representing all available resources under the given context.|
Fast Healthcare Interoperability Resources Tense#One of the most fundamental aspects of a Fast Healthcare Interoperability Resources is tense - where it fits into the timeline. Some Fast Healthcare Interoperability Resources are records of past events, some are plans for the future, etc. This table summarizes the categories:
|Past||A record of an event that has happened|
|Present||A record that serves an exchange in real time|
|Future||A record that describes a future intent|
|Ongoing||A record that is maintained over time that tracks the state of a patient|
|Unrelated||A record that doesn't relate to time (e.g. a fixed entity)|
More Information#There might be more information for this subject on one of the following:
- FHIR Resource
- Health Level Seven
- Health Relationship Trust
- Privacy Consent Directive
- Smart-On-FHIR profile
- Web Blog_blogentry_050116_1