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. 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.
Temple Health publishes 9 APIs on the APIs.io network, including Allergy Intolerance API, Bulk Data API, Condition API, and 6 more. Tagged areas include Academic Medical Center, CMS Interoperability, Cures Act, DSTU2, and Epic.
The Temple Health catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.
Temple Health’s developer surface includes authentication, GitHub presence, engineering blog, and 24 more developer resources.
Kin Score
APIs 10
Individual APIs this provider publishes, each with its own machine-readable definition.
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.
Scroll for all 10
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Temple Health FHIR R4 API
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Temple Health Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Temple Health Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Temple Health Context
JSON-LDSpectral Rules 2
Spectral governance rulesets for linting and validating these APIs.
Temple Health API Rules
SPECTRALTemple Health API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 1
JSON Structure definitions describing this provider's data shapes.
Temple Health Fhir Encounter Structure
JSON STRUCTUREExamples 4
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 6
Properties that don't map to a standard resource type