# Temple Health

**Canonical:** https://apis.io/providers/temple-health/  
**Website:** https://www.templehealth.org/  
**APIs profiled:** 10

Temple University Health System (Temple Health) is the Philadelphia-based academic health system affiliated with the Lewis Katz School of Medicine at Temple University. It operates Temple University Hospital (Main Campus, Jeanes, Episcopal, Northeastern, Women & Families), Temple Health Chestnut Hill Hospital, Fox Chase Cancer Center, and outpatient sites across the Philadelphia region. Its patient-facing electronic health record runs on Epic, branded myTempleHealth (MyChart), with CMS-mandated HL7 FHIR APIs published at epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/R4 (and a legacy DSTU2 endpoint at the same host) that expose USCDI-aligned clinical resources to third-party patient-access applications via SMART on FHIR and OAuth 2.0. Temple Health does not publish a separate commercial developer program; its API surface is regulatory-mandated and free at point of use.

## Kin Score — 59.8 / 100 (strong)

Scored 2026-08-21 under rubric 0.12.0. Trend: flat (+0.5 from 59.3).

| Facet | Score |
|---|---|
| Discoverability | 81.5 |
| Contract Quality | 61.1 |
| Governance | 59.1 |
| Contract Governance | 59.1 |
| Operational Transparency | 5.3 |
| Developer Ergonomics | 20.8 |
| Commercial Clarity | 78.9 |
| Access Clarity | 78.9 |

Regulatory layer — **Health**: 76.3 (matched via tags).

## Agent readiness — 41.8 (agent-ready)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | derived |
| Reversibility Documented | na |
| MCP Server | no |
| Auth Clarity | yes |
| Idempotency | na |
| Error Semantics | documented |
| OpenAPI Examples | documented |
| Rate Limit Signal | documented |
| Event Surface Described | no |
| Agent Skills | derived |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | na |

## Access

Free · Self-serve signup — onboarding: self-serve, pricing: free, trial: no (confidence: high).

## APIs (10)

- **Temple Health FHIR DSTU2 API** — The legacy Temple Health DSTU2 FHIR endpoint listed in Epic's public DSTU2 endpoint registry under the organization "TempleHealth". It remains available for backward compatibili...
- **Temple Health Allergy Intolerance API** — Risk of harmful or undesirable physiological response to a substance.
- **Temple Health Bulk Data API** — HL7 FHIR Bulk Data Access Group-level export.
- **Temple Health Condition API** — Detailed information about conditions, problems, or diagnoses.
- **Temple Health Document Reference API** — A reference to a document, often a CCDA or clinical note.
- **Temple Health Encounter API** — An interaction between a patient and healthcare provider(s).
- **Temple Health Medication Request API** — An order or request for both supply of the medication and the instructions for administration.
- **Temple Health Metadata API** — FHIR conformance and SMART configuration discovery.
- **Temple Health Observation API** — Measurements and simple assertions made about a patient.
- **Temple Health Patient API** — Demographics and other administrative information about an individual receiving care.

## MCP servers (1)

- **Candidate tool surface only — Temple Health hosts no MCP server (deployment mode: none)** — Temple Health ships no MCP server. This is a CANDIDATE tool surface derived from the operations the FHIR endpoint actually exposes, so that an integrator can see what an MCP wra...

## Agentic access (1)

- **Temple Health Agentic Access** — 11 operations

## Security (2)

- **Temple Health Authentication** — oauth2/openIdConnect · 1 scheme
- **Temple Health Domain Security** — TLSv1.3 · DMARC

## Plans (1)

- **Temple Health Plans Pricing**

## Tags

Academic Medical Center, CMS Interoperability, Cures Act, DSTU2, Epic, FHIR, Fox Chase Cancer Center, HL7, Healthcare, Hospital System, MyChart, Authentication, Patient Access, Price Transparency, R4, SMART on FHIR, Temple University, US Core, USCDI

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/temple-health/). Scores are computed from the provider's own public artifacts under a published rubric.