CMS Blue Button 2.0 · FinOps Profile

Cms Blue Button Finops

FinOps view of Blue Button 2.0 spend. The API is a free U.S. government service operated by the Centers for Medicare & Medicaid Services - there is no invoice from CMS at any usage level, in sandbox or production. The real costs of consuming Blue Button 2.0 sit on the consumer side - engineering time to pass CMS production approval (privacy policy, terms of service, demo), infrastructure to run the OAuth consent flow and store beneficiary-consented FHIR data, and the compliance overhead of handling Medicare claims data (breach notification, dormant-account, and third-party vendor obligations from the CMS terms).

Cms Blue Button Finops is the FinOps profile for CMS Blue Button 2.0 on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 4 billable meters, billed in USD, on a none cycle, and pricing category free.

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

Tagged areas include Blue Button, CARIN, Medicare, FHIR, and Claims Data.

Category: Healthcare Data Pricing: Free Billing: None FOCUS v1.3
Blue ButtonCARINMedicareFHIRClaims DataFinOpsCost ManagementFOCUS

Framework Alignment

Framework
Data Spec

FOCUS Columns

BillingCurrency
USD
ChargeCategory
None
InvoiceIssuerName
None (free government service)
PricingCategory
Free
ProviderName
Centers for Medicare & Medicaid Services
PublisherName
Centers for Medicare & Medicaid Services
ServiceCategory
Healthcare Data
ServiceName
Blue Button 2.0

Meters

authorized_beneficiaries
Unit: users
Number of Medicare beneficiaries who have authorized the application; drives consumer-side storage and sync compute, not a CMS charge.
fhir_requests
Unit: requests
FHIR API requests to ExplanationOfBenefit, Patient, and Coverage endpoints; free, but drives consumer-side compute and polling architecture.
token_refreshes
Unit: tokens
OAuth token grants and refreshes; one-hour access tokens and one-time-use refresh tokens shape sync scheduling.
compliance_overhead
Unit: hours
Internal cost of meeting CMS terms - privacy policy upkeep, breach notification readiness, dormant-account handling, vendor reviews.

Sources