Overview
A FHIR Resource is the fundamental unit of healthcare data exchange in FHIR. Each resource is a self-contained structured representation of a single healthcare entity: a Patient resource describes an individual, an Observation resource describes a single clinical observation, a MedicationRequest resource describes a single prescription, a Claim resource describes a single insurance claim. FHIR R4 defines approximately 145 resource types spanning clinical, administrative, financial, workflow, and conformance domains.
Each resource type has a formal specification describing its structure, cardinality rules (which fields are required, optional, or repeating), value bindings (what coded terminology applies to coded fields), and extensions (places where implementations can add custom content). Implementers follow the specification to ensure interoperability. Implementation Guides (US Core, PDex, Da Vinci IGs) constrain and extend base resources for specific use cases.
Resource identity is a core concept. Each resource has a unique identifier (id) within its server, and references between resources use this id to link related entities. A MedicationRequest references the Patient (the subject) and the Practitioner (the requester) via these identifiers. Identity conventions vary — some servers use UUIDs, some use meaningful IDs, some use business identifiers — and cross-server reference resolution is handled through external identifier namespaces.
Resource versioning is tracked automatically. Each update to a resource produces a new version, and the version history is accessible through FHIR history operations. Version-specific references (pointing to a specific version of a resource rather than the current version) are supported for use cases requiring historical snapshotting.
The resource catalog covers many domains. Clinical resources (Patient, Condition, Observation, Procedure, MedicationRequest, AllergyIntolerance, Immunization, DiagnosticReport) support care delivery. Administrative resources (Encounter, Appointment, Practitioner, Organization, Location) support workflow. Financial resources (Coverage, Claim, ExplanationOfBenefit, Invoice) support revenue-cycle integration. Workflow resources (Task, ServiceRequest, CommunicationRequest) support coordination. Conformance resources (StructureDefinition, CapabilityStatement, ValueSet) support interoperability metadata.
Not all resources are equally mature. Normative resources (Patient, Observation, Condition, etc. as of R4) have stable structure guaranteed not to break across releases. Trial-use resources may evolve with breaking changes across releases. Implementers should check the maturity level of each resource they rely on.
For healthtech developers, mastering FHIR resources means understanding the catalog and knowing which resources serve which use cases. A claims-adjudication integration uses Claim and ExplanationOfBenefit; a patient-data-aggregation app uses Patient, Condition, MedicationRequest, and Observation; a prior-authorization workflow uses Task, ServiceRequest, and Claim. The resource catalog is the interoperability language.
Compliance programs treat FHIR Resource as a recurring audit trigger rather than a one-time policy exercise. The practical approach is a quarterly FHIR Resource self-audit tied into the broader compliance calendar, with findings tracked against fhir r4 and fhir api so a FHIR Resource gap cannot silently persist from one audit cycle to the next. Reviewers on this site pair every FHIR Resource reference with the corresponding regulatory citation so the policy owner can trace the requirement back to its authoritative source.
Industry benchmark
FHIR R4: ~145 resource types. ~50 are normative (stable structure guaranteed). ~95 are trial-use (may evolve). US Core profiles approximately 20 of the most common clinical resource types.
Worked example
An app requesting a patient's recent lab results queries the FHIR API for Observation resources filtered by category=laboratory and patient=[id]. The server returns a searchset bundle of Observation resources, each representing a single lab result with value, unit, date, performer, and related metadata.
Frequently asked questions — FHIR Resource
How many FHIR resources exist?
Approximately 145 in R4. The number grows slowly as new resources are added for emerging use cases; existing resources evolve but only additively to preserve interoperability.
What is a normative resource?
A resource whose structure is guaranteed not to break across future FHIR releases. Normative status provides stability for regulated production use; trial-use resources may evolve.
How do resources reference each other?
Through identifier-based references. A MedicationRequest references its Patient via Reference(Patient/[id]). Servers resolve references using identifier conventions and external namespace registries.
Disclaimer
This glossary entry is operational reference for revenue-cycle and medical-billing professionals. It is not legal, clinical, or contractual advice. Industry benchmarks cite named public sources where available; always verify against the current guidance from the authority body before relying on a number in a contract, policy, or compliance filing.