apiCommonsRateLimits: '0.1'
generated: '2026-08-15'
method: probed
source: Live unauthenticated responses from https://epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/R4
  (GET /metadata 200 and GET /Patient/example 401), header-inspected 2026-08-15; plus a search of every
  Temple Health web property for a published limits table, which found none.
limit_count: 0
method_note: limit_count:0 is the finding, not a gap in the research. Temple Health publishes no quantitative
  rate limits anywhere, and the endpoint emits no rate-limit headers. Concrete throttles are set per application
  during Epic on FHIR onboarding and are not disclosed publicly.
headers:
  ratelimit: []
  x_ratelimit: []
  retry_after: false
  observed_on:
  - 200 GET /metadata
  - 401 GET /Patient/example
  note: No RateLimit-*, X-RateLimit-* or Retry-After header appeared on any observed response. There is
    no runtime backpressure signal for a client to read — an integrator learns it is over quota only from
    the status code.
response_codes:
  throttled: presumed 429 — not documented and not observed
observed_response_headers:
- 'cache-control: no-cache,no-store'
- 'pragma: no-cache'
- 'expires: -1'
- 'strict-transport-security: max-age=31536000; includeSubDomains'
- 'www-authenticate: Bearer (401 only)'
- 'access-control-allow-origin: *'
- 'warning: 199 (RFC 7234 advisory, seen on a 200)'
info:
  title: Temple Health API Rate Limits
  description: Rate-limit and quota disclosures for Temple Health's published FHIR APIs. Temple Health
    does not publish per-endpoint quantitative rate-limit numbers (requests-per-minute, requests-per-day)
    on its public CMS-9115-F APIs. Limits are enforced at the network edge of Epic's FHIR interconnect
    proxy fronting the Temple Health endpoint and are governed by app registration agreements rather than
    a public throttle table.
  created: '2026-05-23'
  modified: '2026-08-15'
provider:
  name: Temple Health
  url: https://www.templehealth.org/
apis:
- id: temple-health-fhir-r4-api
  name: Temple Health FHIR R4 API
  baseURL: https://epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/R4
  policies:
  - type: per-app-throttle
    description: Per-application throttling enforced by Epic's interconnect proxy ("FhirProxyPrd"). Concrete
      limits are not publicly documented and are set during Temple Health app onboarding under the Epic
      on FHIR developer program.
    documented: false
    source: https://fhir.epic.com/Documentation
  - type: bulk-data-export
    description: HL7 FHIR Bulk Data Group $export jobs are queued and rate-controlled separately from
      synchronous reads; concurrency is typically capped per registered system.
    documented: false
- id: temple-health-fhir-dstu2-api
  name: Temple Health FHIR DSTU2 API
  baseURL: https://epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/DSTU2
  policies:
  - type: per-app-throttle
    description: Same Epic proxy-based throttling as the R4 endpoint; not publicly documented.
    documented: false
- id: price-transparency-mrf
  name: Temple Health Price Transparency Machine-Readable Files
  baseURL: https://www.templehealth.org/sites/default/files/file/
  policies:
  - type: anonymous-edge-throttle
    description: Public unauthenticated CSV downloads; per-IP throttling and bot mitigation apply at the
      website's CDN/WAF edge but specific limits are not published.
    documented: false
limits: []
notes:
- CMS-9115-F does not require publication of quantitative rate limits, only that the API be available
  to authorized patients.
- Production-scale integrations should contact Temple Health for negotiated quota agreements.