VivaLNK · FinOps Profile

Vivalink Finops

FinOps view of VivaLNK (Vivalink) spend. VivaLNK is a commercial, contact-sales connected-health vendor: cost is a blend of hardware (medical-grade wearable biosensors and disposable adhesives), the Biometrics Data Platform / cloud data services (scoped by subjects, devices, and data volume), and SDK / Developer Program licensing for API access. There is no public list price or self-service tier, so per-unit rates are not reconciled here. Dominant cost drivers are the number of monitored subjects, the number and type of deployed sensors, disposables consumed over time, and the volume of biometric data ingested, stored, and exported.

Vivalink Finops is the FinOps profile for VivaLNK on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 4 billable meters, billed in USD, on a custom cycle, and pricing category contract-based.

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

Tagged areas include Connected Health, Remote Patient Monitoring, Wearables, Biometrics, and FinOps.

Category: Connected Health and Remote Patient Monitoring Pricing: Contract-Based Billing: Custom FOCUS v1.3
Connected HealthRemote Patient MonitoringWearablesBiometricsFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

PurchaseUsageAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
VivaLNK
PricingCategory
Contract-Based
ProviderName
VivaLNK
PublisherName
VivaLNK
ServiceCategory
Connected Health and Remote Patient Monitoring
ServiceName
VivaLNK Biometrics Data Platform

Meters

monitored_subjects
Unit: subjects
Number of subjects (patients / participants) enrolled and monitored on the platform.
deployed_devices
Unit: devices
Number of VivaLNK wearable biosensors deployed, by type (ECG, temperature, SpO2, BP).
disposables
Unit: units
Disposable adhesives / consumables used with reusable sensors over time.
data_volume
Unit: bytes
Volume of biometric data ingested, stored, and exported through the platform.

Sources