Ledger Health
Value-based care creates settlement chains across providers, payers, and ancillary services that no current system reconciles in real time. Ledger Health is the cryptographic settlement layer underneath those chains.
01 · The problem
Multi-party settlement runs on email and spreadsheets
A single VBC episode touches three to six entities. Final reconciliation typically takes 90+ days, requires manual reconstruction of who did what when, and gives the patient no provable record of who accessed their data. Audit and compliance teams burn cycles reconstructing trails after the fact.
02 · The thesis
The first wave of healthcare blockchain tried to replace the rails. That was the mistake.
The 2017 cycle assumed health systems would migrate settlement onto a new chain. They never did, because the chain had nothing the rails did not. The cycle ended.
What's missing is not a new rail. It is a verifiable audit and settlement primitive that bolts onto the rails health systems already use. A permissioned, append-only ledger of who paid whom and who accessed what. Cryptographic where it has to be, boring where it can be.
03 · The product
What it does
Append-only settlement ledger
A permissioned ledger of multi-party reimbursement transactions across providers, payers, and ancillaries. Cryptographically signed, queryable, regulator-friendly.
Verifiable PHI access logs
Every read and write to patient data carries a signed record. Patient, provider, payer, and regulator each get a queryable view.
Reimbursement-split contracts
Encode the multi-party split logic once. Settlement happens concurrently across parties when encounter data is finalized, instead of sequentially over 90 days.
Regulator-native reporting
Audit becomes a query, not a forensic exercise. The same primitive serves HIPAA, OIG, and state Medicaid examiners.
04 · Why now
The timing case
- 1
VBC arrangements have moved from pilot to primary contract structure for most major payers, making multi-party settlement the default rather than the exception.
- 2
Permissioned distributed ledger technology has matured past the speculative-finance era. Production deployments in regulated industries are real.
- 3
Patient data access disclosure rules continue to expand under HIPAA and state-level privacy regimes. Cryptographic logs remove the trust-me problem.
05 · Why I see it
The view from inside the work
I sat inside the data layer of US healthcare clearinghouses long enough to see where settlement actually breaks. The opportunity is not on the rails. It is in the audit primitive underneath them.
06 · Comparable references
What's already in the market, and where the gap is
An honest read on the adjacent landscape. Not every comparable is a competitor. Some are partners. Some are the market the venture displaces.
07 · Key risks
What could break the thesis
Operator-grade pre-mortem. Surfaced because the buyers and partners worth talking to will surface them anyway.
Why a ledger and not an append-only Postgres table with signed Merkle roots?
Honest answer: for a single-payer, single-provider deployment, you don't need one. The ledger primitive only earns its keep across three or more parties without a trusted mediator. That is exactly the VBC topology, but the venture has to prove it on a multi-party design partner before claiming it generally.
Healthcare systems move slowly on novel infrastructure.
Land via a single high-pain VBC arrangement at a forward-leaning health system. Reference deployment first, network effects second.
Regulatory clarity on cryptographic audit logs is still evolving.
Engage HHS and state regulators on standards directly. Federal Reserve and HIMSS working-group access compresses the timeline.
08 · Proof of motion
What I've already shipped on this thesis
The artifacts that turn this from an essay into something with traction. Published work, working-group seats, operator scars.
- Multi-party settlement experience at Change HealthcareI directed reconciliation across providers, payers, and ancillaries inside the largest US clearinghouse. The 90-day reconciliation tail is not theory.filing
- HIMSS contributor work on healthcare data interoperabilityWorking-group access to the standards conversation that defines the audit primitive.advisory
- The Last Invoice (book, 2026)Chapter on multi-party reconciliation argues exactly this thesis. Chapter 1 is on-site.essay
09 · Questions partners ask
The next three follow-ups
Pre-empted because the buyers and partners worth talking to will surface them anyway.
Healthcare blockchain is a graveyard. Why try again?
Because the 2017 cycle tried to replace the rails. This bet does not. It adds a verifiable audit and settlement primitive on top of rails health systems already use. The buyer language is HIPAA and OIG, not Web3.
Why a chain at all? Why not a signed Postgres table?
For a single-payer, single-provider deployment, you don't need one. The ledger primitive only earns its keep across three or more parties without a trusted mediator. That is exactly the VBC topology. The venture has to prove it on a multi-party design partner before claiming it generally.
Hashed Health, Solve.Care, MediLedger all tried this. Why does it work now?
Three things changed. Permissioned ledger tech matured in regulated industries (Avaneer, Synaptic, multiple HIE pilots are real now, not slideware). VBC arrangements moved from pilot to primary contract structure for most major payers, so multi-party reconciliation is the default. And patient-data access disclosure rules expanded under HIPAA and state regimes, putting cryptographic logging on the regulatory roadmap. The first wave was early. This wave is overdue.
What's the first deployment look like?
A single high-pain VBC arrangement at a forward-leaning health system, with three to six counterparties already named. Settlement primitive first, audit primitive second, network effects third. We earn the right to talk about the chain by closing the 90-day reconciliation tail to two weeks on one named contract.
Status
Ledger Health is a published essay, not a stealth company. I am running Finexio. The thesis is here so the right operator or investor can find it and we can talk.
Of the eight ventures I've published, two are in discovery and I expect to operate one of them after Finexio. The rest, including this one, are pattern recognition I want in the open. If you read this and want to start it yourself, that is the outcome I'm hoping for.
Other concepts
Healthcare Adjudication
Apex Adjudication
AI claims-resolution engine for healthcare payers. Resolves manual denials at API speed.
Clearinghouse Automation
Clearing AI
Automated translation between legacy clearinghouse formats and modern APIs.
Healthcare ML
Vault Healthcare
Compliant data enclaves for collaborative healthcare ML training.