Claims Liquidity Exchange · Verified Health Record · India
Bridge Cure turns a hospital's insurer-approved claim into cash from a regulated lender within days — because the claim travels with a hospital-signed, patient-consented record that the insurer verifies before it pays. Bridge Cure never holds anyone's money and never holds a record it can read.
The problem
Authorisation is no longer the bottleneck — nine in ten pre-authorisations clear within the hour. The pain has moved to the interval after approval, and to the word "rejected". Three of the four stated grounds for repudiation are evidence problems, not medical ones.
It is the ninth of the month at a 40-bed hospital. Salaries were due on the seventh. Six approved cashless claims sit unpaid — one for 61 days, four marked "rejected — documentation". Every rupee is for a patient already treated and discharged.
Forty days after an angioplasty, the TPA pays ₹1,12,000 of a ₹1,60,000 authorisation and cites an incomplete discharge summary. The patient has no copy, no record of what was sent, and no idea a deduction happened until the hospital calls.
A credit committee is asked to finance approved claims. Its first question is what share is later short-paid, and how anyone would know. Today the answer is a promise.
The platform
The Claims Liquidity Exchange and the Verified Health Record are one product: the record is what makes the claim safe to finance, and the financing is what makes the record worth issuing. Every flow leaves an artefact the next flow relies on — linked by identifiers and hashes, not by trust.
Entity KYC under four-eyes approval. The tenant, its first admin and its DPDP notice are created in one transaction.
Claims enter from the billing desk, the HIS, NHCX or paper with human-verified OCR. A three-way match certifies the claim; the lender advances against it.
At discharge the treating hospital signs the episode's FHIR record. It lands encrypted in the patient's locker and on their device, hash-anchored.
The insurer — or the next hospital — requests the record through the consent manager. The patient approves purpose, scope and expiry. Every view is logged.
The insurer pays a collection account; a standing instruction repays the advance. Any shortfall is netted gently over 45 days, never clawed back in one stroke.
| What | Issuing hospital | Patient's device | Bridge Cure servers | Transparency log | Insurer / next hospital |
|---|---|---|---|---|---|
| Clinical record (readable) | Yes — its own duty | Yes — encrypted under the device key | Never | Never | Only for the consent window, within scope |
| Record ciphertext & signed hash | — | Yes | Yes | Hash only | — |
| Consent artefact | Copy | Signed here | Verified and enforced | Hash | Copy |
| Claim (financials, no clinical columns) | Source | Summary view | Yes | Ledger head hash | Via NHCX / TPA |
| Money | Bank account | — | Never | Never | Bank / escrow account |
| Ledgers (financing, consent, access, audit) | — | — | Append-only, hash-chained | Anchored | — |
| TOTAL held by Bridge Cure in readable form: 0 clinical records · 0 record keys · ₹0 of anyone's money | |||||
Sign in with ABHA. Hold your hospital-signed records encrypted on your phone. See every rupee approved, paid and deducted — with the reason. Grant and revoke access in one tap.
The business app for hospital owners, billing, finance and admins — and for lender credit, operations and risk. Issue records at the bedside, sign facilities, draw advances, countersign within limits.
The verification surface for insurers, TPAs and auditors. Scoped, time-boxed access to the signed record under the patient's consent, with the signature and anchor checked for you.
Bridge Cure's own desk: human-in-the-loop document review with SLA countdowns, maker-checker compliance approvals, and capability switches that no single person — and no code path — can flip alone.
Who it's for
A pre-sanctioned facility from a regulated lender, drawn claim by claim against certified receivables. The shortfall, when it comes, is absorbed over a rolling window so a single deduction never costs a salary run.
Every advance references a claim certified against a hospital-signed record, with the insurer's verification bound to it. Your book is yours alone — isolated by row-level security, not by promise.
Under the patient's consent, see the hospital-signed record for the episode, with the issuer's signature and the transparency-log anchor already checked. Pay within the regulator's fifteen-day window, and prove you saw the record before you did.
Sign in with ABHA; Bridge Cure issues no password and keeps no profile. Your hospital signs your record at discharge; it is held encrypted on your phone under a key only you hold. Nobody reads it without your consent — including Bridge Cure.
The Verified Health Record
The record is the platform's evidence layer. The hospital is the author. The patient is the custodian. Bridge Cure holds ciphertext and signed hashes — and can show any auditor or regulator every act in an unbroken chain.
The treating facility signs the episode as an ABDM-conformant FHIR R4 bundle with a key bound to its Health Facility Registry entry. A correction is a new record naming the one it supersedes; both remain, and every reader sees the chain.
Each record is encrypted under a per-record key wrapped by the patient's device key, derived on the phone and never sent anywhere. Release happens on the device, for one consent, to one named requester, for a fixed time.
An insurer's verification is bound to the claim — who, when, consent ID, record hash, outcome — and appears on the patient's access log within seconds. Access ends when the consent does.
Facility key in the hospital's secure enclave or HSM — never on Bridge Cure's servers.
Certification carries the record hash and the consent ID it was read under.
Records open on the patient's device with MPIN or biometrics, no network required.
The next hospital pulls verified prior history under consent — before it files pre-authorisation.
Trust & compliance
Ten business principles are binding on every requirement Bridge Cure builds. Each is a business decision with a structural consequence, and the consequence is what gets built.
Funds move bank to bank through licensed nodal and escrow accounts. No Bridge Cure-controlled account is in any money path. Bridge Cure is a lending service provider — not a lender, aggregator or exchange.
Plaintext exists on the issuing hospital's system and the patient's device. Bridge Cure's servers hold ciphertext and signed hashes; no Bridge Cure-held key opens a record.
Records are issued and signed by a registered facility. Nobody edits after issue. The patient grants and revokes access and cannot write.
Artefacts are issued through the ABDM consent manager. Bridge Cure verifies and enforces them and can never mint one. The signing key is generated on the device and never leaves it.
Missing authorisation means refusal. An unknown figure is shown as unknown — never as zero or a dash. A regulated capability is born OFF and switches ON only against a maker-checker record code cannot forge.
Table constraints, absent columns, row-level security and composite keys — double-financing, self-granted roles and same-person approvals are unrepresentable.
Every amount in paise, every rate in basis points. Every ledger hash-chained with no update or delete grant to any role.
No model or rule auto-settles, blocks or gates a consequential decision. A named human adjudicates, and the adjudication is recorded.
A figure is computed once on the server and shown identically to the hospital, the lender, the payer and the operator. Nothing is derived in the browser.
No document, deck or contract claims a property the built and gated system does not have. This website is held to the same rule.
ABDM certification (M1–M3, functional testing, CERT-In audit, NHA production keys) and NHCX participation follow the published paths and are obtained on the way to production. Bridge Cure does not claim a certification it has not been granted.
National health identity and federated record exchange with a defined Health Locker role, FHIR R4 and end-to-end Fidelius encryption.
patient identity without a Bridge Cure credential; the consent artefact; the regulatory slot for the Verified Health Record.
The national claims exchange on FHIR — payers and providers on one wire, with a ₹500 per-claim incentive to hospitals.
the structured claim envelope to which a record reference and consent ID attach; payers already integrated.
Consent must be free, specific, informed, unambiguous and withdrawable; purpose limitation; breach notification; registered, independent consent managers.
the consent model, the reason Bridge Cure is not the consent manager, and its retention and purge obligations.
A written non-custodial lending-service-provider standard, multi-lender disclosure norms, and co-lending rules a credit committee can underwrite against.
the non-custodial structure, the facility and escrow design, and the disclosures a lender needs.
Compound-interest penalties for late settlement and network delisting for cashless abuse — an insurer now pays for delay and must justify denial.
the insurer's reason to pay for verified evidence and to settle on time.
Pricing
Four revenue lines that grow together. Financing is volume revenue; verification, subscription and analytics are infrastructure revenue. Rates below are indicative and are set in each agreement.
Hospital-to-hospital prior-history pulls are bundled with the financing relationship. Advance rates, discount, tenor and fees are set by the lender in the facility terms the hospital signs. Every amount on the platform is stored in paise; every rate in basis points.
One claim, end to end
A fictional cast on illustrative dates: Sunrise Multispeciality Hospital (40 beds, Nashik), patient Ramesh Patil, insurer Bharat Suraksha via MedAssist TPA, and Deccan Finance, an RBI-registered NBFC.
Compliance checker approves; tenant, first admin and DPDP notice created in one transaction.
₹50,00,000 limit at 110 bps per 30 days, 60-day tenor. Dr Joshi signs; Deccan's credit officer countersigns the same terms digest.
FHIR bundle signed by the facility key on the hospital's device. Record hash 4c1e…9a. Ramesh signs consent on his phone five minutes later. Batch #8842 anchored at 16:31.
Invoice SUN/2026/10/0418 — ₹1,85,000 billed, ₹1,60,000 pre-authorised. Three-way match certifies against the record at 10:42. Advance drawn at 11:05.
₹1,28,000 advanced + ₹500 fee · due 15 DecBank to bank. The ₹41 lakh problem is now a ₹39.7 lakh problem — and fourteen more claims follow that week.
Under a 7-day consent: signature valid, anchor confirmed, supersession chain of two shown. The adjudicator reads that hypertension was first diagnosed after policy inception. View logged to Ramesh's app.
Verification fee metered: ₹75MedAssist pays ₹1,12,000 into the collection account; the standing instruction sweeps it to Deccan. Variance ₹48,000 recorded; ₹16,500 remains outstanding, to be netted at 20% of the next remittance.
Citing the signed procedure note, the admission history and MedAssist's own verification view. Dr Joshi reviews and submits.
Next remittance of ₹3,40,000 netted at 20%: ₹16,500 closes the advance; ₹3,23,500 flows to Sunrise. No salary run lost.
A further ₹46,400. The variance ledger records the recovery; Sunrise's variance with this payer falls.
Without the record, this episode ends on 24 November with a 30% variance, ₹48,000 unresolved, a facility stop a month later, and a patient who never knew why.
Why now
Market figures are secondary-source and directional; Bridge Cure verifies them against primary IRDAI, NHA and MeitY publications before any investor or bank use.
Company
That is the vision. Bridge Cure does not claim to be the first to finance hospital receivables. Its position is different in kind: the only platform on which the record that verifies the claim, the consent that releases it, the certification the lender funds against, and the settlement that repays the advance are one chain of evidence. Lenders and lending-service providers are participants on the rail, not rivals to it.
Founded by Rohit Kumar Lakra (CEO), Roshni Gowdanar (CTO) and Shivani Anand (COO) — three founders, deliberately three, and deliberately these three. Meet the team and get in touch →
Get in touch
Tell us who you are and we will come back with a demo on your own scenario — a hospital's month of receivables, a lender's underwriting question, or a payer's verification workflow.