The official FHIR specification is the only source of truth:
https://hl7.org/fhir/. This section is a practical
guide to get you productive quickly. We deliberately focus on certain parts of
the spec that are widely used and understood.
What is FHIR?
At its core, FHIR (Fast Healthcare Interoperability Resources) is a standard way to represent healthcare data as resources and exchange them over HTTP using a consistent REST API. Resources are the building blocks of FHIR. They represent a variety of healthcare entities, such as patients, encounters, observations, and more. They can be grouped into modules (you will see them on the landing page of the official FHIR spec).Data Exchange
As mentioned above, FHIR resources can be exchanged via HTTP in a RESTful manner. This is the most common way to exchange FHIR data. Most HTTP requests are one of these:- A single resource (like
Patient) - A
Bundle(usually search results) - An
OperationOutcome(errors and validation issues)
Try it (2 minutes)
If you have a FHIR server running (TLQ or any other), do these three tiny checks.1
1) Ask the server what it supports
The best “starting page” of any FHIR server is its CapabilityStatement:Look for:
- Supported resource types
- Supported interactions (
read,search-type,update, …) - Supported search parameters per type
2
2) Read one resource
Pick a resource type and ID you know exists and try a read:Two things to notice:
resourceTypetells you what you’re looking atmeta.versionIdandmeta.lastUpdatedtell you about history/versioning
3
3) Run your first search
Search returns a Skim the response for:
Bundle (type searchset):Bundle.entry[](the results)Bundle.total(if the server includes it)