Penn Medicine · Rate Limits

Penn Medicine Rate Limits

Machine-readable rate-limit scaffold for the Penn Medicine FHIR R4 API. UPHS does not publish formal per-key rate-limit numbers; the values below capture the Epic platform's typical patient-app and backend-services governance behavior plus the underlying HL7 Bulk Data Access IG semantics. Real limits are confirmed during app registration / data-sharing agreements.

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

It captures 3 rate-limit definitions, across the patient-access, provider-directory, and bulk-data tiers, measuring requests_per_minute and concurrent_jobs.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Healthcare, Hospital, FHIR, Rate Limiting, and Throttling.

3 Limits Throttle: 429
HealthcareHospitalFHIRRate LimitingThrottling

Limits

Patient App Default app-client
requests_per_minute · minute
60
Public Provider Directory ip
requests_per_minute · minute
30
Backend Services Bulk Export contract
concurrent_jobs · instance
1

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter, honoring the Retry-After header when present.
Bulk Export Polling
Per the HL7 Bulk Data Access IG, clients poll the Content-Location URL using Retry-After hints; aggressive polling will be throttled.
Patient Consent
All patient-context reads require an active OAuth access token; revoked tokens immediately stop returning data regardless of rate limits.
Fair Use
Sustained traffic that materially impacts UPHS clinical operations may be throttled or revoked outside the documented limits.