Penn Medicine
Penn Medicine is the University of Pennsylvania Health System (UPHS) plus the Perelman School of Medicine. It is an $11.9 billion enterprise powered by nearly 49,000 faculty and staff, operating six hospitals (Hospital of the University of Pennsylvania, Penn Presbyterian Medical Center, Chester County Hospital, Lancaster General Health, Princeton Health, and Pennsylvania Hospital — the first hospital in the United States, chartered in 1751) plus Penn Medicine at Home, Good Shepherd Penn Partners Rehabilitation, Lancaster Behavioral Health Hospital, and Princeton House Behavioral Health. The Perelman School of Medicine was awarded $580 million in NIH funding in fiscal year 2023. From an API perspective, Penn Medicine runs a production Epic-backed HL7 FHIR R4 endpoint at `https://ssproxy.pennhealth.com/PRD-FHIR/api/FHIR/R4` (Epic Organization ID 346, implementation description "University of Pennsylvania Health Systems FHIR Server"). The CapabilityStatement instantiates `us-core-server|6.1.0` and the HL7 Bulk Data Access IG, exposes 59 FHIR resource types covering Patient Access (clinical + claims) and Provider Directory per CMS-9115-F, and protects them with OAuth 2.0 / SMART-on-FHIR. Penn Medicine also operates the MyPennMedicine MyChart patient portal and the PhysicianLink referring-provider portal, and publishes open-source informatics work through several Perelman School of Medicine GitHub orgs (Penn-Medicine-CHCI, pennsignals, PMACS, pennbiobank).
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Penn Medicine the way a machine reads it — 55 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Penn Medicine scores 55.7/100 (strong), with a separate agent-readiness read of 30/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Penn Medicine's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/penn-medicine/"
title="Penn Medicine on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/penn-medicine.svg"
alt="Penn Medicine Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/penn-medicine/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/penn-medicine/"
title="Penn Medicine on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/penn-medicine/card.svg"
alt="Penn Medicine Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Penn Medicine
Each block below is one kind of artifact we hold for Penn Medicine. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 7
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
MyPennMedicine Patient Portal
MyChart-based patient portal that gives Penn Medicine patients access to medical records, lab results, secure messaging with their care team, telehealth visits, medication refil...
PhysicianLink Referring Physician Portal
EpicLink-based portal for community and referring physicians that provides secure access to Penn Medicine patient records: clinical notes, lab and imaging results, medication li...
Penn Medicine Open Source Health Informatics
Penn Medicine and the Perelman School of Medicine publish open-source health-informatics software across several GitHub organizations: Penn Medicine Center for Health Care Innov...
Penn Medicine Bulk Data API
HL7 FHIR Bulk Data Access (Flat FHIR) Group-level export.
Penn Medicine Patient Access API
Patient-mediated clinical and claims data resources required under CMS-9115-F.
Penn Medicine Provider Directory API
Public provider, organization, location, and endpoint resources required under CMS-9115-F.
Penn Medicine SMART API
SMART on FHIR launch and discovery endpoints.
Scroll within the panel for all 7 ·
Open Collections 6
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONPenn Medicine FHIR R4 Bulk Data API
OPEN COLLECTIONPenn Medicine FHIR R4 API
OPEN COLLECTIONPenn Medicine FHIR R4 Bulk Data Patient Access API
OPEN COLLECTIONPenn Medicine FHIR R4 Bulk Data Provider Directory API
OPEN COLLECTIONPenn Medicine FHIR R4 Bulk Data SMART API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Penn Medicine Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Penn Medicine Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
CMS-Compliant Patient Access FHIR API
HL7 FHIR R4 server with US Core 6.1.0 conformance and SMART on FHIR authorization, fulfilling CMS-9115-F Patient Access requirements.
Public Provider Directory
Unauthenticated FHIR resources for Practitioner, PractitionerRole, Organization, Location, and Endpoint.
HL7 Bulk Data Access
Group-level $export per the HL7 Bulk Data IG; supports backend services (client_credentials) authentication.
59 FHIR Resource Types
CapabilityStatement advertises 59 resource types covering clinical, administrative, and financial data including AllergyIntolerance, Condition, Observation, MedicationRequest, I...
MyPennMedicine Patient Portal
MyChart-based portal that fronts the FHIR surface for patients and their authorized apps.
PhysicianLink for Referring Providers
EpicLink portal for community physicians referring patients into UPHS.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Penn Medicine Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Penn Medicine API Rules
SPECTRALPenn Medicine API Rules
SPECTRALJSON Schema 4
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Penn Medicine FHIR Observation
JSON SCHEMAPenn Medicine FHIR Organization
JSON SCHEMAPenn Medicine FHIR Patient
JSON SCHEMAPenn Medicine FHIR Practitioner
JSON SCHEMAExamples 5
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Patient-Mediated Data Download
Patients authorize third-party PHR and care-coordination apps to pull their complete clinical and claims history from Penn Medicine via SMART on FHIR.
Care-Coordination Apps
Approved EHR-launched and standalone SMART apps surface Penn Medicine clinical data inside referring-provider, payer, and longitudinal-care tools.
Population Analytics
Approved system-level clients run Group-level $export to extract de-identified cohorts for quality measurement, research, and risk modeling.
Provider Directory Distribution
Payers, referral platforms, and health information exchanges consume the public Provider Directory bundle without authentication.
Referring Provider EMR Access
PhysicianLink gives credentialed community physicians read access to UPHS records for shared patients.
Integrations 8
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Epic EHR
UPHS's underlying EHR; the FHIR endpoint is served by Epic November 2025.
Epic on FHIR
Third-party app developers register apps at fhir.epic.com and target Penn Medicine (Organization ID 346).
SMART App Launch
SMART on FHIR launch protocols for EHR-integrated and standalone apps.
HL7 FHIR Bulk Data IG
Backend-services authentication and Group-level export.
HL7 US Core 6.1.0
CapabilityStatement instantiates us-core-server profile.
Apple Health
Penn Medicine participated in Apple's 2018 launch of Health Records on iPhone, allowing patients to view FHIR-formatted records.
Carequality
National interoperability framework Penn Medicine participates in for record retrieval across networks.
Care Everywhere
Epic-to-Epic record exchange for connecting providers.
Scroll within the panel for all 8 ·
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Patient Access
CMS-mandated patient-mediated data access surface for UPHS patients.
Provider Directory
CMS-mandated public provider directory surface.
Bulk Data Analytics
Population-scale FHIR data extraction for approved partners.
Connected Mental Health (Cobalt)
Open-source Cobalt platform from Penn Medicine CHCI delivering employee mental health and well-being services.
Resources
Every other property we hold for Penn Medicine — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
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 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/penn-medicine · machine-readable index on apis.io
This is an independent, third-party profile of Penn Medicine, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.