Orion Health · Rate Limits

Orion Rate Limits

Orion Health does not publish public per-second or per-minute rate-limit numbers for its FHIR, Population Health, HIE, or Rhapsody Integration APIs. Deployments are typically customer-managed (on-premises or customer cloud) or Orion-hosted with rate limits agreed in the underlying customer contract. Throughput on the Rhapsody integration engine is capacity-planned per deployment.

Orion Rate Limits is the machine-readable rate-limit profile for Orion Health on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring varies and messages_per_second.

The profile also includes 4 backoff/retry policies defined and response codes documented for unauthorized, forbidden, notFound, serverError, and serviceUnavailable.

Tagged areas include FHIR, Healthcare, HIE, Interoperability, and Rate Limiting.

4 Limits
FHIRHealthcareHIEInteroperabilityRate Limiting

Limits

FHIR API Throughput deployment
varies
bound by deployment sizing
Throughput is governed by the deployed Orion Health environment (Orion-hosted or customer-managed) rather than a public per-tenancy rate.
Population Health API Throughput deployment
varies
bound by deployment sizing
HIE API Throughput deployment
varies
bound by deployment sizing
Rhapsody Integration Throughput deployment
messages_per_second
bound by Rhapsody engine sizing
Rhapsody throughput is capacity-planned per engine deployment and depends on the configured routes, filters, and downstream destinations.

Policies

Capacity-Bound Throttling
Throughput limits are determined by the deployment sizing (Orion-hosted or customer-managed) rather than a public per-tenancy rate-limit table.
Backoff Strategy
Clients should implement exponential backoff with jitter on 5xx responses; honor any Retry-After header when present.
HL7 / FHIR Bulk Patterns
For large-population data exchange use FHIR Bulk Data ($export) or Rhapsody batch routes rather than transactional FHIR REST calls.
Customer Agreement
Specific rate-limit numbers, SLAs, and capacity commitments are defined in the underlying customer agreement and operations runbook for each deployment.

Sources