Contract implementation infrastructure

Runvalue-basedhealthcarecontractswithprogrammableescrowandpayout.

For payers, providers, and digital health teams already piloting value-based contracts and needing a way to automate payouts, verification, and audit trails.

Escrow Vault

LIVE

CHF 0

Status

Waiting for Digital Biomarker Verification...

Release conditions

  • HbA1c reduction > 0.5%
  • 90-day adherence > 80%
  • Third-party verification complete

Verified by:Third-Party Lab API

Operational characteristics

100% transparent

Open contract logic

Transparent, auditable contract rules

Immutable logs

Audit trail by design

Every action logged and verifiable

ISO 27001

Swiss-engineered controls

Enterprise-grade security standards

REST + Webhooks

API-first integration

Connect any system in minutes

Open-source

EDEN-based methodology

Research-backed contract patterns

Featured in

Backed by leading Swiss innovation programs

VentureKick
InnoBooster
Venturelab
SFTA
Kick Foundation

Our Mission

We are changing how the world funds health. Instead of waiting for people to get sick, we are building a financial engine that makes staying healthy an investable asset class.

Why this matters

The execution gap in value-based care

Most outcome-based models fail at the operational layer. Teams agree on clinical outcomes but lack the escrow, verification, and payout operations to run them in production.

01

Unpriced payer risk

Outcome-based deals often fail because payers cannot mathematically price unverified promises. Without enforceable mechanisms, every deal is a leap of faith.

SanaFin approach

Escrow-backed contracts transfer risk to verifiable code, allowing payers to price outcomes with 100% confidence.

02

9-month payout delays

Providers face crippling administrative delays and cash flows that rely on manual reconciliation and patient behavior outside their direct control.

SanaFin approach

Automated, rules-based payouts release funds within 2 hours of verification — reducing payment cycles by up to 95%.

03

Operational scale bottleneck

Technical teams can pilot one deal manually, but they lack the infrastructure to scale risk-sharing contracts across multiple counterparties.

SanaFin approach

Standardized contract templates and APIs let you integrate once and scale to unlimited payers without increasing headcount.

Implementation reality

How a pilot works

We move from commercial assessment to production-ready infrastructure in 4 weeks. Most first conversations focus on procurement and operational sign-off.

01

Contract and workflow assessment

Week 1: Define contract type, stakeholders, and payout logic. Deliverable: Operational scope document and procurement roadmap.

02

Verification and exception design

Week 2: Map data sources (labs, devices, registries) and define fallback paths for edge cases. Deliverable: Verification source map.

03

Workflow configuration

Week 3–4: Configure contract logic, roles, and audit trail requirements. Deliverable: Production-ready contract environment.

04

Automated execution

Ongoing: Funds are locked in escrow, outcomes are verified, and payouts are triggered automatically. Deliverable: Real-time audit trail.

contract.jsonAPI
{
"contract_id": "sf_ctr_2024_001",
"escrow_amount": 100000,
"currency": "CHF",
"risk_share_ratio": 0.8,
"outcome_rules": [
{
"metric": "hba1c_reduction",
"threshold": 0.5,
"source": "lab_api",
},
{
"metric": "adherence_90d",
"threshold": 0.8,
"source": "device_api",
}
],
"payout_timing": "2_hours",
}
POST /v1/contracts200 OK

Who It Is For

Designed for institutional stakeholders

SanaFin aligns the conflicting needs of finance, technology, and legal teams into a single high-integrity automated workflow.

Economic Buyer

Payer Innovation Lead / CFO

Needs to price and manage unverified promises. Requires enforceable mechanisms to transfer risk from balance sheet to verifiable outcomes.

Primary Value

Quantifiable risk reduction and budget certainty.

Technical Buyer

Implementation / Product Lead

Needs a scalable way to link data sources to payouts without custom engineering every new contract or partner.

Primary Value

Standardized APIs and 95% reduction in manual ops.

Legal & Procurement

Compliance / Legal Counsel

Requires audit trails, role-based controls, and Swiss-engineered data handling to clear regulatory and operational hurdles.

Primary Value

Audit-ready logs and compliant Swiss design baseline.

Ecosystem Integration

The infrastructure for trustless healthcare operations.

SanaFin bridges clinical data and financial settlement with a secure, automated baseline for value-based contracts.

Instant Verification

Real-time outcome validation from clinical or claims data.

Multi-Party Governance

Rules-based workflows shared between payers and providers.

Institutional Security

Swiss-hosted, GDPR-compliant with immutable audit trails.

SanaFin

Escrow Vault

$
$

Payer / CFO

Initial Deposit

Provider

Payout Liquidity

User / Patient

Outcome Evidence

ISO 27001 Certified Environment
Verified Node

Transaction Latency: < 200ms

SanaFin Institutional Framework

Use cases

SanaFin in practice

SanaFin is designed for any healthcare contract where payment depends on verified outcomes.

DTx01

Outcomes-based digital therapeutics

Structure payment contracts where DTx providers are paid based on patient engagement or clinical improvement.

Contract: Outcomes-based reimbursement. Trigger: Verified engagement and clinical thresholds. Benefit: Automated revenue recognition for providers.

Prevention02

Prevention program funding

Enable insurers to fund prevention initiatives with payouts tied to measurable health improvements.

Contract: Value-based prevention funding. Trigger: Readmission reduction rates. Benefit: Payer budget certainty through verified risk transfer.

Value-Based03

Provider performance contracts

Create performance-based contracts that reward providers for achieving specific quality metrics.

Contract: Quality-based incentives. Trigger: Patient satisfaction and outcome thresholds. Benefit: Scalable incentive distribution with zero manual reconciliation.

Risk-Share04

Multi-stakeholder risk-sharing

Launch multi-stakeholder pilots where risk and reward are distributed based on verified outcomes.

Contract: Multi-party risk-share. Trigger: Oncology care pathway results. Benefit: Coordinated payout across pharma, payer, and provider.

“We had done three outcome-based deals manually before. SanaFin let us automate the fourth in a fraction of the time — and with full audit trail.”
H

Healthcare Innovation Lead

Swiss Digital Health Company (pilot phase)

Open methodology

Built on the EDEN Framework

EEnforceable
Legally binding outcomes
DDeterministic
Predictable execution
EEvidence-based
Data-driven decisions
NNeutral
Unbiased arbitration

SanaFin is built on EDEN - a set of research-informed contract design patterns for enforceable, outcome-based healthcare contracts. EDEN defines how outcomes should be specified, how verification should work, and how contracts should be structured for auditability and fairness.

The framework is open-source and designed to be reviewed, critiqued, and improved by the healthcare, legal, and fintech communities.

Informed by research from

Peer reviewed

ETH Zurich

Health economics research

Outcome verification methodology
01

University of St. Gallen

Healthcare management studies

Contract design patterns
02

Research-backed methodology

3+

Years of research

12

Published papers

100%

Open source

Common questions

Frequently asked questions

01

Who holds the funds, and when are they released?

Contract funds are deposited into an escrow account at contract start. Release is rule-based: once agreed outcomes are verified within the contract window, payout is executed automatically according to the contract terms.

02

Which verification sources are supported?

Any source that can deliver structured evidence can be integrated: laboratory systems, registries, provider systems, and approved device APIs. Verification sources are explicitly whitelisted in each contract.

03

What happens when source data is missing or disputed?

Contracts define fallback behavior up front, including alternative sources, grace periods, and exception workflows. High-risk or disputed events can be routed to human review before payout.

04

What is your compliance scope?

The platform is designed with Swiss legal principles in mind and supports GDPR-aware data handling. Legal and regulatory review is still required for each deployment jurisdiction and use case.

05

How long does implementation usually take?

A typical pilot implementation includes contract and workflow assessment, verification and exception design, and configuration of approval, escrow, and audit steps. This usually spans 2–4 weeks.

06

Is the first call a sales call or technical workshop?

The first call is a commercial and operational scoping conversation. It is designed for active opportunities, contract planning, or RFP assessment rather than a generic product demo.

Get started

Ready to automate a value-based contract?

This implementation review will map your active contract concept, verification sources, and procurement timeline.

Contract-ready assessmentVerification source mapping4-week deployment roadmap