Children's Hospital of Philadelphia
Founded in 1855 as the first hospital in the United States dedicated to the healthcare of children, Children's Hospital of Philadelphia (CHOP) is a 692-bed flagship pediatric academic medical center affiliated with the University of Pennsylvania Perelman School of Medicine. CHOP records roughly 1.63 million outpatient visits and 34,829 admissions per year and operates one of the largest pediatric research enterprises in the world through its Research Institute and the Center for Data Driven Discovery in Biomedicine (D3b). From an API perspective, CHOP runs a production Epic-backed HL7 FHIR R4 endpoint at `https://epicnsproxy.chop.edu/fhir/api/FHIR/R4` exposing CMS-9115-F Patient Access and Provider Directory resources, US Core 6.1.0, SMART on FHIR, and HL7 Bulk Data. CHOP additionally publishes 320+ public repositories across the `chop-dbhi` (Department of Biomedical and Health Informatics) and `d3b-center` GitHub organizations, plus shared research data platforms including RADIANT, CAVATICA, PedcBioPortal, the Children's Brain Tumor Network, and the Kids First Data Resource Center.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Children's Hospital of Philadelphia the way a machine reads it — 47 machine-readable artifacts across 8 APIs, 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 — Children's Hospital of Philadelphia scores 54.1/100 (developing), with a separate agent-readiness read of 41/100 (agent aware). 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 Children's Hospital of Philadelphia
Each block below is one kind of artifact we hold for Children's Hospital of Philadelphia. 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 8
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.
MyCHOP Patient Portal
MyChart-based patient portal that gives patients, parents and guardians access to virtual medical records, lab results, secure messaging, telehealth visits, medication refills, ...
Link2CHOP Referring Physician Portal
Internet-based portal for referring physician offices that provides real-time, read-only access to the CHOP Epic EMR. Surfaces discharge notes, operative reports, progress notes...
D3b Data Sharing Platforms
The Center for Data Driven Discovery in Biomedicine (D3b) at CHOP operates the open research data infrastructure for pediatric cancer and rare disease. Programs include RADIANT ...
DBHi Biomedical and Health Informatics
CHOP's Department of Biomedical and Health Informatics (DBHi) maintains 168 public repositories covering health data infrastructure, EHR integration, and SMART on FHIR tools. No...
Children's Hospital of Philadelphia Bulk Data API
HL7 FHIR Bulk Data Access (Flat FHIR) Group-level export.
Children's Hospital of Philadelphia Patient Access API
Patient-mediated clinical and claims data resources required under CMS-9115-F.
Children's Hospital of Philadelphia Provider Directory API
Public provider, organization, location, and endpoint resources required under CMS-9115-F.
Children's Hospital of Philadelphia SMART API
SMART on FHIR launch and discovery endpoints.
Scroll within the panel for all 8 ·
Open Collections 1
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).
Children's Hospital of Philadelphia FHIR R4 API
OPEN COLLECTIONFeatures 5
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
Capability statement advertises 59 resource types covering clinical, administrative, and financial data, including AllergyIntolerance, Condition, Observation, MedicationRequest,...
Open-Source Health Informatics Tools
168 public DBHi repositories and 153 public D3b repositories spanning ETL, anonymization, biorepository analytics, and SMART apps.
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.
Spectral 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.
JSON 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.
CHOP FHIR Observation
JSON SCHEMACHOP FHIR Organization
JSON SCHEMACHOP FHIR Patient
JSON SCHEMACHOP 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.
Chop Fhir Patient Example
EXAMPLESecurity 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
Parents and guardians download their child's full clinical and claims history into third-party PHR apps via SMART on FHIR.
Care-Coordination Apps
Approved EHR-launched and standalone SMART apps surface CHOP data inside referring-provider and care-coordination tools.
Population Analytics
Approved system-level clients run Group-level $export to extract de-identified cohorts for research and quality measurement.
Pediatric Cancer Research Collaboration
D3b platforms (RADIANT, CAVATICA, PedcBioPortal, CBTN) enable multi-site sharing of pediatric oncology and rare-disease data.
Referring Provider Read-Only EMR Access
Link2CHOP gives credentialed referring physicians live access to discharge notes, labs, imaging, medications, and diagnoses 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
CHOP'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 CHOP (Organization ID 332).
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.
ARPA-H
Funding partner for the RADIANT pediatric data-sharing platform.
NIH Common Fund
Funds the Gabriella Miller Kids First Data Resource Center, coordinated by D3b.
University of Pennsylvania
Academic affiliate (Perelman School of Medicine).
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.
Provider Directory
CMS-mandated public provider directory surface.
Bulk Data Analytics
Population-scale data extraction for approved partners.
Open Research Data
D3b platforms for pediatric cancer and rare-disease research collaboration.
Resources
Every other property we hold for Children's Hospital of Philadelphia — 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 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/childrens-hospital-of-philadelphia · machine-readable index on apis.io