Fast Healthcare Interoperability Resources


Fast Healthcare Interoperability Resources (FHIR) is a fundamental concept within Fast Healthcare Interoperability Resources (FHIR).

A protected Fast Healthcare Interoperability Resources MUST document which version of FHIR applies to the resources it offers.

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 ResourcesDescriptionLink
PatientDemographic information about the patienthttp://www.hl7.org/fhir/stu3/patient.html
MedicationRequestInformation about requests for medications for patientshttp://www.hl7.org/fhir/stu3/medicationrequest.html
MedicationDispenseInformation about supply of medications to a patienthttp://www.hl7.org/fhir/stu3/medicationdispense.html
MedicationAdministrationInformation about medications consumption or other administrationhttp://www.hl7.org/fhir/stu3/medicationadministration.html
MedicationStatementInformation about the believed state of a medicationhttp://www.hl7.org/fhir/stu3/medicationstatement.html
ObservationInformation about observations performed by a healthcare providerhttp://www.hl7.org/fhir/stu3/observation.html
AppointmentInformation about scheduled appointmentshttp://www.hl7.org/fhir/stu3/appointment.html
AllergyIntoleranceInformation about allergies and drug intolerancehttp://www.hl7.org/fhir/stu3/allergyintolerance.html
ConditionInformation about a patient's condition http://www.hl7.org/fhir/stu3/condition.html
ImmunizationInformation about a patient's immunizationshttp://www.hl7.org/fhir/stu3/immunization.html
CarePlanInformation about a patient's care planhttp://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:
PastA record of an event that has happened
PresentA record that serves an exchange in real time
FutureA record that describes a future intent
OngoingA record that is maintained over time that tracks the state of a patient
UnrelatedA record that doesn't relate to time (e.g. a fixed entity)
Note that even future records end up in the past after the event they are concerned with passes.

More Information#

There might be more information for this subject on one of the following: