specification: FinOps Framework specificationVersion: '1.0' alignedWith: framework: FinOps Foundation Framework frameworkUrl: https://www.finops.org/framework/ dataSpec: FOCUS dataSpecVersion: '1.3' dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/ provider: Penn Medicine providerId: penn-medicine publisherName: University of Pennsylvania Health System serviceCategory: API created: '2026-05-23' modified: '2026-05-23' tags: - Healthcare - Hospital - FHIR - FinOps - Cost Management - FOCUS description: | FinOps framework definition for the Penn Medicine FHIR R4 API. Penn Medicine does not charge third parties for FHIR access (CMS-9115-F prohibits fees for patient-app reads and the public Provider Directory), so the externalized "cost" surface is essentially zero. This document describes the *internal* cost-allocation model UPHS would use to attribute infrastructure spend on the FHIR endpoint across consuming services. principles: - name: Visibility description: Make FHIR consumption (apps, scopes, resource types) visible to clinical IT, security, and finance teams. - name: Allocation description: Tag every FHIR call with the registered app, scope set, resource type, and patient cohort so infrastructure cost can be allocated. - name: Optimization description: Continuously evaluate caching, conditional reads, and Bulk Data over polling for high-volume consumers. - name: Accountability description: Establish budget ownership inside UPHS IS&T for shared infrastructure powering the FHIR endpoint. domains: - name: Understand Usage and Cost capabilities: - Data Ingestion - Allocation - Reporting and Analytics - Anomaly Management - name: Quantify Business Value capabilities: - Planning and Estimating - Forecasting - Budgeting - Benchmarking - Unit Economics - name: Optimize Usage and Cost capabilities: - Architecting for Cloud - Rate Optimization - Workload Optimization - Cloud Sustainability - Licensing and SaaS - name: Manage the FinOps Practice capabilities: - FinOps Practice Operations - FinOps Education and Enablement - Invoicing and Chargeback - Onboarding Workloads - Intersecting Disciplines billingModel: pricingCategory: Internal Cost Allocation billingFrequency: Monthly billingCurrency: USD chargeCategories: - Usage - Purchase chargeFrequency: Recurring focusColumns: ServiceName: Penn Medicine FHIR R4 API ServiceCategory: Developer Tools / API ProviderName: Penn Medicine PublisherName: University of Pennsylvania Health System InvoiceIssuerName: University of Pennsylvania Health System PricingCategory: Internal Cost Allocation PricingUnit: request BillingCurrency: USD ChargeCategory: Usage meters: - name: fhir_requests description: Count of FHIR requests served by the Penn Medicine proxy unit: request aggregation: sum dimensions: - app - resource_type - scope_tier - interaction - name: bulk_export_jobs description: Number of Group-level $export jobs initiated unit: job aggregation: sum dimensions: - app - group - name: data_egress description: Bytes returned over the network in FHIR responses unit: GB aggregation: sum dimensions: - app - resource_type apis: - name: Penn Medicine FHIR R4 API baseURL: https://ssproxy.pennhealth.com/PRD-FHIR/api/FHIR/R4 tags: - FHIR - Patient Access - Provider Directory serviceName: Penn Medicine FHIR R4 API serviceCategory: API unitEconomics: - name: Infrastructure Cost per 1K FHIR Requests metric: infra_cost / (fhir_requests / 1000) target: TBD - name: Cost per Registered App metric: infra_cost / active_apps target: TBD maintainers: - FN: Kin Lane email: kin@apievangelist.com