name: Penn Medicine description: | 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). url: https://github.com/api-evangelist/penn-medicine image: https://www.pennmedicine.org/-/media/global/global-logo.svg created: '2026-05-23' modified: '2026-05-23' specificationVersion: '0.18' tags: - Healthcare - Hospital - Academic Medical Center - FHIR - SMART On FHIR - Patient Access - Provider Directory - CMS Interoperability - US Core - Bulk Data - Epic apis: - name: Penn Medicine FHIR R4 API description: | The University of Pennsylvania Health Systems FHIR Server. Epic (November 2025) on the back end, conforming to US Core 6.1.0 and the HL7 Bulk Data Access IG. Serves Patient Access (clinical + claims) and Provider Directory data per CMS-9115-F, exposing 59 FHIR resource types including Patient, AllergyIntolerance, Condition, Observation, MedicationRequest, Immunization, Procedure, Encounter, DiagnosticReport, DocumentReference, Coverage, ExplanationOfBenefit, Claim, Practitioner, PractitionerRole, Organization, Location, and Endpoint. App registration is performed through Epic on FHIR (https://fhir.epic.com) by selecting Penn Medicine (Organization ID 346) as the target. humanURL: https://www.pennmedicine.org/for-health-care-professionals/for-physicians/electronic-medical-records baseURL: https://ssproxy.pennhealth.com/PRD-FHIR/api/FHIR/R4 tags: - FHIR - SMART On FHIR - Patient Access - Provider Directory - Bulk Data - US Core properties: - type: Documentation url: https://www.pennmedicine.org/for-health-care-professionals/for-physicians/electronic-medical-records - type: APIReference url: https://ssproxy.pennhealth.com/PRD-FHIR/api/FHIR/R4/metadata - type: OpenAPI url: openapi/penn-medicine-fhir-r4-openapi.yml - type: JSONSchema url: json-schema/penn-medicine-fhir-patient-schema.json - type: JSONSchema url: json-schema/penn-medicine-fhir-organization-schema.json - type: JSONSchema url: json-schema/penn-medicine-fhir-practitioner-schema.json - type: JSONSchema url: json-schema/penn-medicine-fhir-observation-schema.json - type: Example url: examples/penn-medicine-fhir-patient-example.json - type: Example url: examples/penn-medicine-fhir-organization-example.json - type: Example url: examples/penn-medicine-fhir-practitioner-example.json - type: Example url: examples/penn-medicine-fhir-observation-example.json - type: Example url: examples/penn-medicine-fhir-bulk-export-example.json - type: Authentication url: https://ssproxy.pennhealth.com/PRD-FHIR/oauth2/authorize - type: Sandbox url: https://fhir.epic.com/Documentation?docId=testpatients - name: MyPennMedicine Patient Portal description: | MyChart-based patient portal that gives Penn Medicine patients access to medical records, lab results, secure messaging with their care team, telehealth visits, medication refills, prescription management, bill pay, and appointment scheduling across UPHS facilities. SMART apps approved via Epic on FHIR connect to the underlying Penn Medicine FHIR R4 API. humanURL: https://www.pennmedicine.org/patient-resources/mypennmedicine baseURL: https://secure.mypennmedicine.org tags: - Patient Portal - MyChart - Patient Access properties: - type: Portal url: https://secure.mypennmedicine.org/ - type: Documentation url: https://www.pennmedicine.org/patient-resources/mypennmedicine - name: PhysicianLink Referring Physician Portal description: | EpicLink-based portal for community and referring physicians that provides secure access to Penn Medicine patient records: clinical notes, lab and imaging results, medication lists, and the ability to refer patients and follow care for shared patients. humanURL: https://www.pennmedicine.org/for-health-care-professionals/for-physicians/electronic-medical-records/physicianlink baseURL: https://secure3.pennmedicine.org/EpicLink tags: - Referring Provider - EMR Access - Epic properties: - type: Portal url: https://secure3.pennmedicine.org/EpicLink/common/epic_login.asp - type: Documentation url: https://www.pennmedicine.org/for-health-care-professionals/for-physicians/electronic-medical-records/physicianlink - name: Penn Medicine Open Source Health Informatics description: | Penn Medicine and the Perelman School of Medicine publish open-source health-informatics software across several GitHub organizations: Penn Medicine Center for Health Care Innovation (Penn-Medicine-CHCI, behind the Cobalt mental-health platform — cobalt-api in Java and cobalt-web in TypeScript); Penn Signals / Penn Medicine Predictive Healthcare (pennsignals — Databricks MCP agent templates; historically the home of CHIME, the COVID-19 Hospital Impact Model); Penn Medicine Academic Computing Services (PMACS — 17 Rails libraries, JSON:API tools, Oracle adapters, and Slate API docs); and the Penn Medicine BioBank (pennbiobank). humanURL: https://github.com/pennmedicine tags: - Open Source - Health Informatics - GitHub properties: - type: GitHubOrganization url: https://github.com/Penn-Medicine-CHCI name: Penn Medicine Center for Health Care Innovation - type: GitHubOrganization url: https://github.com/pennsignals name: Penn Signals / Predictive Healthcare - type: GitHubOrganization url: https://github.com/PMACS name: Penn Medicine Academic Computing Services - type: GitHubOrganization url: https://github.com/pennbiobank name: Penn Medicine BioBank - type: GitHubOrganization url: https://github.com/pennmedicine name: Penn Medicine (canonical org) - type: GitHubRepository url: https://github.com/Penn-Medicine-CHCI/cobalt-api - type: GitHubRepository url: https://github.com/Penn-Medicine-CHCI/cobalt-web common: - type: Portal url: https://www.pennmedicine.org - type: DeveloperPortal url: https://fhir.epic.com name: Epic on FHIR (Penn Medicine — Organization ID 346) - type: GitHubOrganization url: https://github.com/Penn-Medicine-CHCI - type: GitHubOrganization url: https://github.com/pennsignals - type: GitHubOrganization url: https://github.com/PMACS - type: Blog url: https://www.pennmedicine.org/news - type: PrivacyPolicy url: https://www.pennmedicine.org/privacy-policy - type: TermsOfService url: https://www.pennmedicine.org/terms-of-use - type: Compliance url: https://www.pennmedicine.org/for-health-care-professionals/for-physicians/electronic-medical-records - type: Support url: https://www.pennmedicine.org/contact-us - type: LinkedIn url: https://www.linkedin.com/company/penn-medicine - type: SpectralRules url: rules/penn-medicine-fhir-rules.yml - type: NaftikoCapability url: capabilities/shared/penn-medicine-fhir-r4.yaml - type: NaftikoCapability url: capabilities/patient-access.yaml - type: NaftikoCapability url: capabilities/provider-directory.yaml - type: NaftikoCapability url: capabilities/bulk-cohort-export.yaml - type: JSONLD url: json-ld/penn-medicine-context.jsonld - type: Vocabulary url: vocabulary/penn-medicine-vocabulary.yml - type: Plans url: plans/penn-medicine-plans-pricing.yml - type: RateLimits url: rate-limits/penn-medicine-rate-limits.yml - type: FinOps url: finops/penn-medicine-finops.yml - type: Features data: - name: CMS-Compliant Patient Access FHIR API description: HL7 FHIR R4 server with US Core 6.1.0 conformance and SMART on FHIR authorization, fulfilling CMS-9115-F Patient Access requirements. - name: Public Provider Directory description: Unauthenticated FHIR resources for Practitioner, PractitionerRole, Organization, Location, and Endpoint. - name: HL7 Bulk Data Access description: Group-level $export per the HL7 Bulk Data IG; supports backend services (client_credentials) authentication. - name: 59 FHIR Resource Types description: CapabilityStatement advertises 59 resource types covering clinical, administrative, and financial data including AllergyIntolerance, Condition, Observation, MedicationRequest, Immunization, Procedure, Encounter, DiagnosticReport, DocumentReference, Coverage, ExplanationOfBenefit, and Claim. - name: MyPennMedicine Patient Portal description: MyChart-based portal that fronts the FHIR surface for patients and their authorized apps. - name: PhysicianLink for Referring Providers description: EpicLink portal for community physicians referring patients into UPHS. - type: UseCases data: - name: Patient-Mediated Data Download description: Patients authorize third-party PHR and care-coordination apps to pull their complete clinical and claims history from Penn Medicine via SMART on FHIR. - name: Care-Coordination Apps description: Approved EHR-launched and standalone SMART apps surface Penn Medicine clinical data inside referring-provider, payer, and longitudinal-care tools. - name: Population Analytics description: Approved system-level clients run Group-level $export to extract de-identified cohorts for quality measurement, research, and risk modeling. - name: Provider Directory Distribution description: Payers, referral platforms, and health information exchanges consume the public Provider Directory bundle without authentication. - name: Referring Provider EMR Access description: PhysicianLink gives credentialed community physicians read access to UPHS records for shared patients. - type: Integrations data: - name: Epic EHR description: UPHS's underlying EHR; the FHIR endpoint is served by Epic November 2025. - name: Epic on FHIR description: Third-party app developers register apps at fhir.epic.com and target Penn Medicine (Organization ID 346). - name: SMART App Launch description: SMART on FHIR launch protocols for EHR-integrated and standalone apps. - name: HL7 FHIR Bulk Data IG description: Backend-services authentication and Group-level export. - name: HL7 US Core 6.1.0 description: CapabilityStatement instantiates us-core-server profile. - name: Apple Health description: Penn Medicine participated in Apple's 2018 launch of Health Records on iPhone, allowing patients to view FHIR-formatted records. - name: Carequality description: National interoperability framework Penn Medicine participates in for record retrieval across networks. - name: Care Everywhere description: Epic-to-Epic record exchange for connecting providers. - type: Solutions data: - name: Patient Access description: CMS-mandated patient-mediated data access surface for UPHS patients. - name: Provider Directory description: CMS-mandated public provider directory surface. - name: Bulk Data Analytics description: Population-scale FHIR data extraction for approved partners. - name: Connected Mental Health (Cobalt) description: Open-source Cobalt platform from Penn Medicine CHCI delivering employee mental health and well-being services. maintainers: - FN: Kin Lane email: info@apievangelist.com