Skip to content

Repository files navigation

Temple Health (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.

APIs.json: https://raw.githubusercontent.com/api-evangelist/temple-health/refs/heads/main/apis.yml

Scope

  • Type: Index
  • Position: Consumer
  • Access: 3rd-Party

Tags

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

Timestamps

  • Created: 2026-05-23
  • Modified: 2026-05-23

APIs

Temple Health FHIR R4 API

The Temple Health FHIR R4 API is Temple University Health System's CMS Interoperability and Patient Access (CMS-9115-F) compliant HL7 FHIR Release 4.0.1 endpoint powered by Epic's August 2025 release. It is listed in Epic's public R4 endpoint registry under the organization "TempleHealth" and exposes USCDI-aligned clinical resources — including Patient, Observation, Condition, Encounter, MedicationRequest, AllergyIntolerance, DiagnosticReport, DocumentReference, Procedure, Immunization, and AllergyIntolerance — to third-party patient-access applications using SMART on FHIR and OAuth 2.0 with standalone-patient and EHR launch contexts. The same endpoint covers the Temple University Hospital campuses (Main, Jeanes, Episcopal, Northeastern, Women & Families), Temple Health Chestnut Hill Hospital, and Fox Chase Cancer Center under one Epic instance. Both XML and JSON FHIR payloads are supported.

Tags

  • CMS Interoperability
  • Cures Act
  • Epic
  • FHIR
  • HL7
  • Patient Access
  • R4
  • SMART on FHIR
  • US Core
  • USCDI

Properties

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 compatibility with older SMART on FHIR apps written against the FHIR DSTU2 (1.0.2) baseline that pre-dates the CMS Interoperability and Patient Access mandate; new integrations should target the R4 endpoint instead. Supported resources include AllergyIntolerance, Binary, CarePlan, Condition, Device, DiagnosticReport, DocumentReference, FamilyMemberHistory, Goal, Immunization, Medication, MedicationOrder, MedicationStatement, Observation, Patient, Practitioner, and Procedure.

Tags

  • DSTU2
  • Epic
  • FHIR
  • Legacy
  • SMART on FHIR

Properties

myTempleHealth MyChart Patient Portal

myTempleHealth is the patient-facing Epic MyChart deployment used by Temple Health patients to view test results, message providers, request prescription renewals, schedule appointments, pay bills, and grant third-party patient-access apps consent to retrieve their data through Temple Health's underlying FHIR R4 API.

Tags

  • Epic
  • MyChart
  • Patient Portal

Properties

Temple Health Hospital Price Transparency Machine-Readable Files

The Hospital Price Transparency dataset Temple Health publishes per the CMS Hospital Price Transparency Final Rule (45 CFR 180). Each Temple Health hospital files a CSV of standard charges (gross, payer- specific negotiated, de-identified min/max, discounted cash). One file is published per hospital campus and refreshed periodically under the YYYY-MM-prefixed path on templehealth.org.

Tags

  • CMS Price Transparency
  • CSV
  • Hospital Charges
  • Open Data

Properties

Common Properties