FHIR Resource
Bundle / Transaction
FHIR R4Send groups of FHIR resources together using batch and transaction Bundle interactions.
Authentication
OAuth 2.0
Bearer token
Scope
healthcare.read
Required
Standard
HL7 FHIR R4
FHIR R4
Rate limit
600 requests / min
Default
Response
Bundle / JSON
application/fhir+json
Bundle types
| Type | Purpose |
|---|---|
| searchset | Search results |
| batch | Independent operations |
| transaction | Atomic set of operations |
| history | Version history |
Transaction behavior
A transaction Bundle succeeds atomically or fails as a unit for the supported resource set.
Atomicity
Do not assume every external side effect is part of the FHIR database transaction; workflow actions are documented separately.
Entry requests
| Field | Purpose |
|---|---|
| request.method | GET/POST/PUT/DELETE |
| request.url | Relative FHIR endpoint |
| fullUrl | Temporary or canonical resource reference |
Example transaction
Transaction Bundle
{
"resourceType":"Bundle",
"type":"transaction",
"entry":[
{"resource":{"resourceType":"Patient"},"request":{"method":"POST","url":"Patient"}},
{"resource":{"resourceType":"Observation"},"request":{"method":"POST","url":"Observation"}}
]
}Response bundle
Each entry receives a response containing status, location and version metadata where applicable.
Limits
Transaction size and supported resource combinations are bounded. Consult the CapabilityStatement and production contract.