specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
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: Varian Medical Systems
providerId: varian-medical-systems
publisherName: Varian Medical Systems (Siemens Healthineers)
serviceCategory: Healthcare
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:
  - Healthcare
  - Oncology
  - Medical Devices
  - FinOps
  - FOCUS
description: 'FinOps shape for Varian Medical Systems: APIs run on premises inside customer hospital deployments of Aria/Eclipse/Velocity. Cost is bundled into the clinical-system license and maintenance contract rather than billed per API call.'
sources:
  - https://cancercare.siemens-healthineers.com/
notes: No public usage-based billing surface for Varian APIs. Costs flow through the Aria/Eclipse license, hardware, and maintenance contracts; FinOps does not apply as a per-call cost model.
billingModel:
  pricingCategory: Bundled with Clinical-System License
  billingFrequency: Per-Contract
  billingCurrency: USD
  chargeCategories:
    - Purchase
focusColumns:
  ServiceName: Varian Medical Systems
  ServiceCategory: Healthcare
  ProviderName: Varian Medical Systems
  PublisherName: Varian Medical Systems (Siemens Healthineers)
  InvoiceIssuerName: Siemens Healthineers
  BillingCurrency: USD
meters:
  - name: contracted_access
    description: API access provisioned under the Varian Developer Program; not metered as a developer billing line
    unit: varies
    aggregation: count
principles:
  - name: Visibility
    description: Usage is observable at the customer's on-prem deployment via Aria/Eclipse logs; Varian does not provide a vendor-side usage dashboard.
  - name: Allocation
    description: Cost is allocated through the radiation oncology department's capital and maintenance budget, not via API meters.
  - name: Optimization
    description: Optimization happens at the integration design level (HL7/FHIR scope, scheduled batch syncs, on-prem capacity planning) rather than per-call cost.
  - name: Accountability
    description: Owned by the hospital's radiation oncology IT team and the integration partner under the Developer Program agreement.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com