# Temple Health

> Temple University Health System (Temple Health) is the Philadelphia-based academic health
> system affiliated with the Lewis Katz School of Medicine at Temple University. Its
> patient-facing electronic health record runs on Epic (myTempleHealth / MyChart). Its entire
> API surface is regulatory: an HL7 FHIR R4 patient-access endpoint published under the CMS
> Interoperability and Patient Access Final Rule, a legacy DSTU2 endpoint at the same host, and
> CMS Hospital Price Transparency machine-readable files on the website. Temple Health runs no
> commercial developer program, publishes no developer portal of its own, and ships no SDKs.

Generated by API Evangelist on 2026-08-15 from live probes of the Temple Health endpoints and
the artifacts in this repository. Temple Health does not publish an llms.txt of its own —
https://www.templehealth.org/llms.txt returned HTTP 404 on 2026-08-15.

## What you can actually call

- [FHIR R4 base](https://epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/R4): HL7 FHIR 4.0.1. 59 resource types, 13 of them writable. All resource paths require an OAuth 2.0 bearer token.
- [FHIR R4 CapabilityStatement](https://epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/R4/metadata): anonymous, HTTP 200. The authoritative description of this server — read it first.
- [SMART configuration](https://epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/R4/.well-known/smart-configuration): anonymous, HTTP 200. Authorize/token endpoints, scopes, grant types, PKCE.
- [OpenID Connect discovery](https://epicaccess.templehealth.org/FhirProxyPrd/oauth2/.well-known/openid-configuration): anonymous, HTTP 200.
- [FHIR DSTU2 base](https://epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/DSTU2): legacy FHIR 1.0.2, 17 resource types. Still live; no SMART discovery document.
- [Price transparency index](https://www.templehealth.org/cms-hpt.txt): anonymous, HTTP 200, text/plain. CMS-mandated index of eight standard-charges CSVs, one per hospital campus.

## Authorization

- Flow: SMART App Launch (OAuth 2.0 authorization code + PKCE S256), or client_credentials with private_key_jwt for backend services.
- Authorize: https://epicaccess.templehealth.org/FhirProxyPrd/oauth2/authorize
- Token: https://epicaccess.templehealth.org/FhirProxyPrd/oauth2/token
- Apps register with Epic at https://fhir.epic.com/Developer/Apps and are then approved by Temple Health against the production endpoint. There is no self-service path to production data.
- An unauthenticated request returns HTTP 401 with a bare `WWW-Authenticate: Bearer` header and an empty JSON body — no OperationOutcome, no pointer to the authorization server.

## Handling PHI

Every clinical resource on this endpoint returns protected health information about a real,
identified patient. If you are an agent operating against this API: stay inside the patient
context granted by the token, never accept a patient identifier that the model produced,
never write a response body into a log or a transcript, and do not use `search_patient`-style
demographic search as a general lookup. The Bulk Data `Group/$export` path is population-scale
and is governed by a data-use agreement, not by patient authorization.

## Specifications in this repository

- [OpenAPI — Patient](openapi/temple-health-patient-api-openapi.yml)
- [OpenAPI — Observation](openapi/temple-health-observation-api-openapi.yml)
- [OpenAPI — Condition](openapi/temple-health-condition-api-openapi.yml)
- [OpenAPI — Encounter](openapi/temple-health-encounter-api-openapi.yml)
- [OpenAPI — AllergyIntolerance](openapi/temple-health-allergy-intolerance-api-openapi.yml)
- [OpenAPI — MedicationRequest](openapi/temple-health-medication-request-api-openapi.yml)
- [OpenAPI — DocumentReference](openapi/temple-health-document-reference-api-openapi.yml)
- [OpenAPI — Metadata](openapi/temple-health-metadata-api-openapi.yml)
- [OpenAPI — Bulk Data](openapi/temple-health-bulk-data-api-openapi.yml)

## Operating knowledge

- [Conventions](conventions/temple-health-conventions.yml): pagination, content negotiation, CORS, caching, why there is no idempotency contract.
- [Errors](errors/temple-health-problem-types.yml): the OperationOutcome envelope and the two places this server does not use it.
- [Authentication](authentication/temple-health-authentication.yml) and [scopes](scopes/temple-health-scopes.yml).
- [Conformance](conformance/temple-health-conformance.yml): US Core 6.1.0, Bulk Data, SMART, and the discovery RFCs this endpoint does not implement.
- [Data model](data-model/temple-health-data-model.yml): the 59-resource entity graph and its traversable edges.
- [Lifecycle](lifecycle/temple-health-lifecycle.yml): Epic release train, DSTU2 legacy status, and the absence of any change-notification channel.
- [Rate limits](rate-limits/temple-health-rate-limits.yml) and [plans](plans/temple-health-plans-pricing.yml): free at point of use, no published quotas.
- [Agent skills](skills/_index.yml): grounded operating instructions for the flows this API supports.
- [Well-known](well-known/temple-health-well-known.yml): what is served and what 404s.

## What does not exist

Checked on 2026-08-15 and genuinely absent — do not go looking:

- No MCP server (hosted or stdio). [Candidate tool surface only](mcp/temple-health-mcp.yml).
- No A2A agent card at either `/.well-known/agent-card.json` or `/.well-known/agent.json`, on any host.
- No security.txt, no vulnerability disclosure programme, no trust centre.
- No SDKs or client libraries in any registry; the GitHub org `Temple-Health` has zero public repos.
- No developer changelog, status page, SLA or deprecation policy. `templehealth.statuspage.io` redirects to Atlassian's marketing site — it is an unclaimed tenant, not a status page.
- No AsyncAPI, webhooks or event surface; the server declares no `Subscription` resource.

## Human pages

- [Temple Health](https://www.templehealth.org/)
- [myTempleHealth patient portal](https://my.templehealth.org/MyChartPRD/Authentication/Login)
- [Hospital pricing information](https://www.templehealth.org/patients-visitors/billing-financial/hospital-pricing-information)
- [Price transparency disclaimer and file downloads](https://www.templehealth.org/pricing-disclaimer)
- [Terms of use](https://hub.templehealth.org/web/guest/disclaimer_termsofuse.html)
- [Privacy and HIPAA notice](https://hub.templehealth.org/web/guest/privacy-hipaa.html)
- [Patient rights](https://hub.templehealth.org/web/guest/patientrights.html)
- [Web privacy policy](https://www.templehealth.org/web-privacy-policy)
- [Epic on FHIR developer program](https://fhir.epic.com/)
- [Epic R4 endpoint registry](https://open.epic.com/Endpoints/R4)