AmeriHealth Caritas · FinOps Profile

Amerihealth Caritas Finops

FOCUS-aligned FinOps for the AmeriHealth Caritas FHIR APIs: regulatory free access (no vendor invoice). The cost surface is the consumer's own infrastructure (request volume, data egress, identity / consent flow, member outreach) rather than per-call API charges from AmeriHealth Caritas. This FinOps file does not attempt to model the underlying health-plan economics (Medicaid capitation, premiums, D-SNP MA payments, PerformRx PBM revenue) — those are commercial contracts with state Medicaid agencies, CMS, employers, and pharmacy clients rather than API-level charges.

Amerihealth Caritas Finops is the FinOps profile for AmeriHealth Caritas on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 6 billable meters, billed in USD, on a n/a cycle, and pricing category regulatory free access (no fee).

The profile maps 7 FOCUS columns for cost-allocation reporting.

Tagged areas include FinOps, FOCUS, FHIR, Healthcare, and CMS.

Category: Healthcare Interoperability Pricing: Regulatory Free Access (no fee) Billing: N/A FOCUS v1.3
FinOpsFOCUSFHIRHealthcareCMSMedicaidPatient Access

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

Usage

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
N/A (no AmeriHealth Caritas invoice for API access)
ProviderName
AmeriHealth Caritas
PublisherName
AmeriHealth Caritas
ServiceCategory
Healthcare Interoperability
ServiceName
AmeriHealth Caritas FHIR APIs

Meters

patient_access_requests
Unit: request
Member-authorized FHIR R4 queries against Patient Access endpoints; not billed but tracked for capacity and rate-limit purposes.
provider_directory_requests
Unit: request
Public Provider Directory FHIR queries.
drug_formulary_requests
Unit: request
Public Drug Formulary FHIR queries (MedicationKnowledge / List).
oauth_member_authorizations
Unit: authorization
SMART on FHIR consent flows initiated and completed; useful for measuring application activation.
refresh_token_uses
Unit: exchange
OAuth refresh token exchanges; useful for understanding member retention in the app.
data_egress
Unit: GB
PHI / FHIR resource bytes returned to the consumer; informs the consumer's own storage and processing cost.

Sources