specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Humana providerId: humana created: '2026-05-04' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35. method: generated modified: '2026-05-05' reconciled: true tags: - FinOps - FOCUS - FHIR - Healthcare - CMS description: 'FOCUS-aligned FinOps for Humana FHIR APIs: regulatory free access (no vendor invoice), cost surface is the consumer''s own infrastructure (request volume, data egress, identity / consent flow, member outreach) rather than per-call API charges from Humana.' sources: - https://developers.humana.com/ - https://www.cms.gov/regulations-and-guidance/guidance/interoperability/index 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/ publisherName: Humana Inc. serviceCategory: Healthcare Interoperability billingModel: pricingCategory: Regulatory Free Access (no fee) billingFrequency: N/A billingCurrency: USD chargeCategories: - Usage focusColumns: ServiceName: Humana FHIR APIs ServiceCategory: Healthcare Interoperability ProviderName: Humana PublisherName: Humana Inc. InvoiceIssuerName: N/A (no Humana invoice for API access) BillingCurrency: USD ChargeCategory: Usage meters: - name: patient_access_requests description: Member-authorized FHIR R4 queries against Patient Access endpoints; not billed but tracked for capacity and rate-limit purposes. unit: request aggregation: sum dimensions: - resource_type - app - name: provider_directory_requests description: Public Provider Directory FHIR queries. unit: request aggregation: sum dimensions: - resource_type - app - name: drug_formulary_requests description: Public Drug Formulary FHIR queries. unit: request aggregation: sum dimensions: - resource_type - app - name: oauth_member_authorizations description: SMART on FHIR consent flows initiated and completed; useful for measuring application activation. unit: authorization aggregation: sum dimensions: - app - name: data_egress description: PHI / FHIR resource bytes returned; informs the consumer's own storage and processing cost. unit: GB aggregation: sum dimensions: - resource_type - app principles: - name: Visibility description: Humana does not invoice for API access. Track request and member-authorization volumes via your application's own logging (token issuance, FHIR request audit). Reconcile against Humana CapabilityStatement and any sandbox vs production rate-limit guidance. - name: Allocation description: Tag FHIR requests with the originating product feature (member portal, claims explorer, care management workflow) so that downstream storage and processing cost can be allocated. - name: Optimization description: Use bulk-data ($export) operations where supported to amortize request overhead. Cache reference data (Provider Directory, Drug Formulary) since they do not require member consent. Use _summary and _elements parameters to reduce payload size and downstream egress cost. - name: Accountability description: Even though API access is free, operational risk is real - mishandled member PHI triggers HIPAA exposure. Establish clear data-retention windows and a periodic audit of which member tokens are still active. maintainers: - FN: Kin Lane email: kin@apievangelist.com