UPMC
A world-renowned health care provider and insurer headquartered in Pittsburgh, Pennsylvania. One of the largest nonprofit health systems in the United States, operating hospitals, physician practices, and a health insurance division (UPMC Health Plan) serving millions of members. UPMC Health Plan exposes an ONC 21st Century Cures Act Developer API for patient-authorized access to clinical and claims data over HL7 FHIR.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles UPMC the way a machine reads it — 12 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 — UPMC scores 10.6/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile UPMC
Each block below is one kind of artifact we hold for UPMC. 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 1
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.
UPMC Health Plan ONC 21st Century Cures Act Developer API
The UPMC Health Plan Developer API is the payer-side FHIR API mandated by the ONC 21st Century Cures Act and the CMS Interoperability and Patient Access Final Rule. It allows re...
Features 4
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.
Patient Access FHIR API
Member-authorized access to clinical (USCDI) and claims data per CMS Interoperability and Patient Access Final Rule
Provider Directory API
Public machine-readable provider directory required by CMS Interoperability rules
SMART-on-FHIR Authorization
OAuth 2.0 / SMART-on-FHIR app authorization flow for patient-mediated access
HL7 FHIR R4 Data Model
USCDI-aligned FHIR R4 resources for clinical and claims data exchange
Security Posture 1
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.
Use Cases 4
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 Data Portability
Members move their clinical and claims data into third-party apps for personal use
Care Coordination
Authorized clinical applications retrieve member records to improve care coordination across providers
Health Apps and PHRs
Consumer-facing personal health record and wellness apps connect to UPMC member data with patient consent
Provider Directory Lookups
Apps and portals discover in-network UPMC Health Plan providers through the public provider directory API
Integrations 2
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
SMART App Launch
Apps register with UPMC Health Plan as SMART-on-FHIR clients to authenticate members
USCDI Clinical Data
USCDI-aligned clinical resources flow to member-authorized third-party applications
Resources
Every other property we hold for UPMC — 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.
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/upmc · machine-readable index on apis.io