specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Cigna
providerId: cigna
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: false
tags:
  - CMS Interoperability
  - FHIR
  - Healthcare
  - Patient Access
  - FinOps
  - FOCUS
description: 'FOCUS-aligned FinOps for Cigna FHIR APIs: there is no commercial billing surface — the
  endpoints are CMS-mandated and provided at no charge to compliant third-party applications.
  Cost-of-ownership for the Cigna engineering team manifests as internal infrastructure spend
  (cloud, gateway, identity) tracked by Cigna FinOps, not as customer-facing line items.'
notes: Cigna does not bill external developers for FHIR API access. The FinOps shape below describes
  Cigna's internal cost surface for operating the developer platform.
sources:
  - https://developer.cigna.com/
  - https://developer.cigna.com/docs/service-apis
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: Cigna Health and Life Insurance Company
serviceCategory: Healthcare / Health Insurance
billingModel:
  pricingCategory: No Customer Charge (Regulatory)
  billingFrequency: N/A
  billingCurrency: N/A
  chargeCategories:
    - Adjustment
focusColumns:
  ServiceName: Cigna Developer FHIR APIs
  ServiceCategory: Healthcare / Interoperability
  ProviderName: Cigna
  PublisherName: Cigna Health and Life Insurance Company
  InvoiceIssuerName: N/A
  BillingCurrency: N/A
  ChargeCategory: Adjustment
  PricingCategory: No Charge (Regulatory)
meters:
  - name: api_requests
    description: FHIR API request volume (operational signal — not a customer billing meter)
    unit: request
    aggregation: sum
    dimensions:
      - api
      - application
      - environment
  - name: token_issuance
    description: SMART on FHIR / OAuth 2.0 token issuance events
    unit: token
    aggregation: sum
    dimensions:
      - application
  - name: registered_applications
    description: Distinct third-party applications registered against the developer portal
    unit: application
    aggregation: max
    dimensions:
      - environment
  - name: bytes_egressed
    description: Bytes of FHIR Bundle data returned to clients (network cost signal)
    unit: GB
    aggregation: sum
    dimensions:
      - api
principles:
  - name: Visibility
    description: Track FHIR API usage internally through API gateway logs, the OAuth issuer, and the
      developer portal. Surface the operational cost back to interoperability and compliance teams.
  - name: Allocation
    description: Allocate developer-platform infrastructure cost to interoperability / regulatory
      compliance and to the digital member-experience program rather than to a customer cost center.
  - name: Optimization
    description: Cache Provider Directory and Drug Formulary FHIR responses, scale gateway capacity to
      the diurnal Patient Access curve, and decommission stale registered applications.
  - name: Accountability
    description: Compliance / regulatory affairs owns rule conformance; digital health engineering
      owns FHIR platform uptime; security owns SMART on FHIR consent and token issuance.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com