A FHIR Bundle is a container resource that groups multiple FHIR resources together into a single document or message. It serves as the packaging mechanism for transmitting complete sets of healthcare data — such as a lab report with all its individual test results — in a single transaction. Bundles are essential for maintaining the integrity and completeness of clinical data as it moves between systems.
FHIR defines several types of Bundles for different use cases. A "document" Bundle packages a complete clinical document with a Composition resource as its first entry. A "transaction" Bundle groups multiple create, update, or delete operations into an atomic unit. A "searchset" Bundle contains the results of a FHIR search query. For lab reports, "document" and "transaction" Bundles are the most commonly used, wrapping a DiagnosticReport resource together with its referenced Observations, Patient, Practitioner, and Organization resources.
The Bundle structure ensures that all the resources needed to interpret a lab report travel together. Without Bundles, a system receiving a DiagnosticReport would need to make separate API calls to retrieve each referenced Observation, the Patient, and the performing Organization. With a Bundle, everything arrives in a single payload, making it self-contained and immediately usable. This is particularly important for document exchange scenarios where the receiving system may not have access to the sender's FHIR server.
In lab report digitization pipelines, the final output is typically a FHIR Bundle containing a DiagnosticReport, its associated Observations (each coded with LOINC and valued with UCUM units), and contextual resources like Patient and Organization. This Bundle represents the complete transformation of an unstructured paper document into a structured, standards-compliant, and interoperable clinical data package ready for consumption by any FHIR-capable system.