slug: penn-medicine
provider: Penn Medicine
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Healthcare Providers
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Bulk Data
  spec_file: penn-medicine-bulk-data-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.8
  evidence: GET /Group/{id}/$export  Export Group Bulk Data; "conforms to US Core 6.1.0 and the HL7 FHIR
    Bulk Data Access (Flat FHIR) capability statement"
  reason: A provider-operated FHIR server exposing bulk export of patient cohorts is health information
    exchange / FHIR endpoint operation, i.e. healthcare interoperability operations run by the health
    system.
- tag: Patient Access
  spec_file: penn-medicine-patient-access-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.8
  evidence: '"exposing CMS-mandated Patient Access and Provider Directory data"; GET /Patient  searchPatient;
    GET /DiagnosticReport  searchDiagnosticReport'
  reason: These are the health system's CMS Patient Access FHIR APIs — patient-initiated sharing of clinical
    records to third-party apps, which is interoperability operations rather than direct care delivery
    or portal product management.
- tag: Provider Directory
  spec_file: penn-medicine-provider-directory-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.75
  evidence: GET /Practitioner  searchPractitioner; GET /Endpoint  searchEndpoint; "CMS-mandated Patient
    Access and Provider Directory data"
  reason: Publishing Practitioner/PractitionerRole/Organization/Location/Endpoint over FHIR is the regulator-mandated
    provider directory interoperability surface, which the interoperability-operations sub-capability
    explicitly covers. It is not credentialing (no verification or privileging operations).