Penn Medicine · OAuth Scopes

Penn Medicine OAuth Scopes

OAuth 2.0 derived

Penn Medicine publishes 6 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Penn Medicine API on a user’s behalf.

Tokens are issued from https://ssproxy.pennhealth.com/PRD-FHIR/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

HealthcareHospitalAcademic Medical CenterFHIRSMART on FHIRPatient AccessProvider DirectoryCMS InteroperabilityUS CoreBulk DataEpic

Scopes: 6 Flows: authorizationCode, clientCredentials Method: derived

OAuth endpoints

Authorization URL
https://ssproxy.pennhealth.com/PRD-FHIR/oauth2/authorize

Token URL
https://ssproxy.pennhealth.com/PRD-FHIR/oauth2/token

Flows
authorizationCodeclientCredentials

Scopes (6)

Scope	Description	Flows
fhirUser	Current FHIR user identity	authorizationCode
launch	SMART app launch context	authorizationCode
offline_access	Refresh token issuance	authorizationCode
openid	OpenID Connect	authorizationCode
profile	User profile claims	authorizationCode
system/*.read	System-level read of all resources (Bulk Data)	clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/penn-medicine-fhir-r4-openapi.yml
schemes:
- name: smartOnFhir
  source: openapi/penn-medicine-fhir-r4-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://ssproxy.pennhealth.com/PRD-FHIR/oauth2/authorize
    tokenUrl: https://ssproxy.pennhealth.com/PRD-FHIR/oauth2/token
  - flow: clientCredentials
    tokenUrl: https://ssproxy.pennhealth.com/PRD-FHIR/oauth2/token
scopes:
- scope: fhirUser
  description: Current FHIR user identity
  flows:
  - authorizationCode
  sources:
  - openapi/penn-medicine-fhir-r4-openapi.yml
- scope: launch
  description: SMART app launch context
  flows:
  - authorizationCode
  sources:
  - openapi/penn-medicine-fhir-r4-openapi.yml
- scope: offline_access
  description: Refresh token issuance
  flows:
  - authorizationCode
  sources:
  - openapi/penn-medicine-fhir-r4-openapi.yml
- scope: openid
  description: OpenID Connect
  flows:
  - authorizationCode
  sources:
  - openapi/penn-medicine-fhir-r4-openapi.yml
- scope: profile
  description: User profile claims
  flows:
  - authorizationCode
  sources:
  - openapi/penn-medicine-fhir-r4-openapi.yml
- scope: system/*.read
  description: System-level read of all resources (Bulk Data)
  flows:
  - clientCredentials
  sources:
  - openapi/penn-medicine-fhir-r4-openapi.yml

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/penn-medicine-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.