ArogyaKosh ▶ Live demo ↗ An invitation to partner
CubixCode CubixCode Technologies · An invitation to partner

The trusted record between
Bharat's doctors and labs

A working product, a clear business, and a wide-open window — right as the government hands the whole sector a tailwind. We're looking for doctor- and lab-partners to build and grow the network with us.

Prepared by CubixCode · for prospective doctor & lab partners

The Problem

A disconnected market: doctors can't see the data, labs can't reach the doctors

The doctor's side

  • A patient's reports pile up across many labs over years — arriving as PDFs, scans & photos, every lab a different layout.
  • At the desk the doctor flips paper: no trends, no longitudinal view → repeat tests, missed patterns.

The lab's side

  • Small & off-grid labs are starved of referrals and have no digital link to the doctors who send them work.
  • Results go out on paper / WhatsApp; big labs' APIs are gated B2B, and ABDM interop is patchy — the long tail has none.
Two halves of one broken market: the doctor prescribes a test and the lab produces the data — but nothing connects them, and no one holds the unified record. That missing connection is the opportunity.
The reframe that drives everything

The moat is not OCR — and no longer the EMR

OCR is commoditising (LLMs / cloud OCR). The durable value is normalised + longitudinal + trusted + point-of-care data, aggregated across fragmented sources.

Multi-channel ingestion

Lab API where it exists → ABDM/ABHA where connected → PDF/OCR as the always-works fallback. OCR is just one channel.

Normalisation is the hard part

Units, reference ranges, test names & codes vary per lab. Cross-lab normalisation is the real moat (and the real grind).

Trust is the asset

Source links, verification status & plausibility flags — provenance is the currency that earns the doctor's confidence.

And now a third commoditiser: the government just made the basic clinic EMR a near-free utility (₹299/mo — next slide). So features aren't the moat either. The moat is the network that connects doctors to labs and the trusted, longitudinal data that flows through it — neither of which a commodity EMR holds.
Why now · The government just moved

The govt validated the category — and commoditised the EMR

On 29 June 2026 the Centre launched e-Sushrut Clinic (built by C-DAC): a cloud clinic system for small clinics & PHCs — ₹299–499/month, first 3 months free, ABDM-native, ~800 facilities live on day one.

Tailwind

Category validated, awareness funded

The government is now evangelising cloud clinic software to exactly our users — driving ABHA adoption and digitisation at its own expense. We ride that wave.

Reality check

The EMR is now a utility

A subsidised ₹299 product puts a price floor under basic EMR. Competing as "another cloud EMR" is a race to zero against the government. So we don't.

Our move

Sit above it, on the same rails

e-Sushrut has no doctor–lab network and no research pipeline. We interoperate via ABDM and become the value layer — addressable even to clinics already on e-Sushrut.

The lesson isn't "build a cloud EMR too." It's that value has moved off the EMR and onto the network + the data. The government just proved the demand and handed us the rails — our job is to own the layer it doesn't.
The opportunity · Why now

A huge market — and the timing window is open

1.4M+

doctors in Bharat

Registered allopathic doctors — most in small private clinics, exactly our long-tail wedge.

~25%/yr

digital-health growth

Bharat's digital-health market is ~$15B today → ~$100B by 2033 — software the fastest-growing slice.

100 cr

ABHA-linked records

Doubled in 15 months; 90 cr national health IDs created — the rails are already here.

Why now: the government has laid the rails at record scale — but usage at the point of care is still low. Records are being linked, not used. The desk layer that turns all this into something a doctor opens every day doesn't exist yet — and ABDM mandates + the digitisation wave make adoption a tailwind. The window is now.
Business Model

A neutral network: doctors get the software, labs pay for demand

  • The doctor is distribution, not the payer — software is free/cheap so it spreads. Every clinic that adopts generates lab orders.
  • Labs are the payer — small & off-grid labs pay for the one thing they lack: digital reach to referring doctors. A payer the ₹299 government EMR never touches.
  • We are neutral — unlike Tata 1mg / Practo, we don't own a lab or pharmacy, so we never compete with the labs on our own network. That neutrality is the moat.
  • The compounding prize: the consented, de-identified longitudinal record we accumulate — research-grade data no one else holds.

The two-sided network

Patients bring the data & the consent; choose their lab.

Doctors get cheap software → prescribe tests. Our reach.

Labs pay to receive referrals + feed results back. Our payer.

Colleges & pharma license de-identified research data. Our upside.

Build from day one: the consent + de-identification plumbing that turns the network into a legal, poolable data asset — and route all value lab → platform, never lab → doctor (see the revenue slide). Keep data in Bharat; interoperate via ABDM.
★ A rail, not a marketplace: we're a prescription-driven fulfillment rail inside the clinic workflow — not a consumer lab/pharmacy app like 1mg / Practo. Listings are neutral (no pay-to-rank), the patient picks the lab, and a hard consent firewall keeps the commercial rail separate from the de-identified research corpus. The rail is the engine, the data is the moat — one flywheel, not two businesses.
Revenue Model

Labs fund the network · data compounds the value

Primary · Now

Labs pay for reach

A connected-lab subscription + a small per-result technology fee for every report routed & delivered through the network. Labs pay for demand, not software.

Fuel

Doctor software: free / near-free

Flat, low, independent of referral volume (see the legal note). It's customer-acquisition — the more doctors, the more lab orders, the more labs pay.

Compounding

Research-data licensing

De-identified, longitudinal datasets to colleges, pharma & CROs. High-margin, defensible — a second revenue leg once the data exists.

The legal line — non-negotiable

Money flows lab → platform, never lab → doctor

Bharat.s law (MCI/NMC code) bars any cut, rebate or referral fee to the doctor ("cut practice"). So: the doctor's price is flat, the lab pays the platform, and the patient picks the lab from connected options — the doctor prescribes the test, not the lab.

Premium tier · On-prem

Self-hosted / larger-clinic licences for the privacy-first minority. Not the volume play — a margin add-on on top of the network.

The second engine · Real-world evidence

Pharma is already asking — the network mints research-grade data

Every verified, ABHA-linked report — tied to diagnosis, medication & outcome from the clinic side — is real-world data. Used well, the network is a data refinery: scarce, Bharat-specific, longitudinal, provenance-checked. This isn't a someday prize — it's exactly what pharma buys today.

Start here · lowest lift

RWD → RWE

De-identified RWE for safety, label expansion, market access & comparative effectiveness — increasingly accepted by regulators (CDSCO / FDA / EMA). Sold as datasets & analytics.

Pharma-funded

Disease registries

Condition cohorts (diabetes, CKD, oncology…) with structured longitudinal follow-up. Sponsors pay us to stand them up on the network — recurring & defensible.

Enable, don't operate

Trial enablement

Patient/site identification, recruitment, decentralised capture & external / synthetic control arms from our RWD. Picks-and-shovels — never a CRO (CDSCO-regulated).

Why our data is credible

Verification-at-source (auditable quality) · ABHA linkage (longitudinal, cross-provider — what most of Bharat.s RWD lacks) · clinical context from the CMS turns lab numbers into evidence. Labs are the spine; context compounds it.

Who pays for it

Pharma (RWE / HEOR / market access) · academic & clinical research · public-health & epidemiology · insurers · diagnostics-AI training. Bharat.s real-world data is scarce → distinctly valuable.

Guardrails (non-negotiable): only de-identified, consented, aggregate data is sold; patient-level needs explicit consent (DPDP + ABDM). An ethics committee via our medical-college partner governs it, and pharma stays walled-off — a data customer, never a say over prescriptions or the fulfilment rail. The flywheel: more verified data → more research value → free datasets & access for colleges → citations & habituation → future customers.
Future upside · A government tailwind

The government pays clinics, labs and us to go digital

Bharat's ABDM runs a Digital Health Incentive Scheme: cash for every lab report digitised and linked to a patient's national health ID (ABHA). It pays every side of the network:

The clinic earns

₹10 / report

A subsidy that pays the clinic to adopt digital records — i.e. to adopt us. The tool helps pay for itself.

The lab earns

₹15 / txn

Diagnostic labs earn per ABHA-linked report (above 500/mo, KYC-verified). The govt subsidises the exact data labs feed our network.

We earn

₹5 / report

As the DSC / LMIS behind the record — on top of lab fees, scaling with volume.

Why it fits us: this is the “enable others · ride the rail” road we already chose — and our data is already the right shape (FHIR), ABHA-ready by design. A subsidy that pays clinics and labs to adopt us is a tailwind under our sail — not a different boat.
Future upside · Disciplined timing

Designed for it — deliberately not yet

Why we wait
  • Full compliance is a real program: ABDM v3 APIs, a security cert (WASA), DSC registration.
  • The economics only clear at scale — break-even is hundreds of GP clinics, or ~35 diagnostic centres.
  • Earning it means records enter the national exchange — consent + compliance work we must get right before we switch it on.
Why we're ready
  • FHIR-native model · ABHA-optional from day one · the read-API seam → a build-later, not a rebuild.
  • Cloud-default makes ABDM linkage natural; the on-prem tier claims the same incentive via an opt-in, consent-gated bridge.
  • When: once ABDM compliance is table-stakes, or reach makes ₹5×volume material — starting with diagnostic centres.
The principle: build the hooks now (nearly free), build the machine later (only when it pays). The subsidy is a reason to design for ABDM — never a reason to rebuild the product around it.
Future upside · The break-even

Worth it at what scale? Run the numbers

DHIS pays us ₹5/diagnostic report linked to a KYC-verified ABHA, above a 100/month baseline per clinic — only if we carry the compliance machine. Drag the dials; every figure is rough & editable.

Scenario
DHIS revenue /mo
Compliance cost /mo
fixed run-rate
DHIS net /mo
incentive − cost
Break-even clinics
at this profile
DHIS
Compliance
Market · Competitive Landscape

A contested space — but the neutral doctor–lab network is open

Category & playersTheir strengthThe gap we exploit
AI health records / report parsing
Eka Care closest
ABHA + AI report parsing; consumer & doctor reach.Cloud-first, broad consumer play — not on-prem / trust-first for the long tail. We go deep on point-of-care multi-lab trends + local trust.
Clinic EMR / management
Practo · HealthPlix · DocOn (Reliance)
Full clinic management, scale, brand.Heavy & cloud; aim at larger practices. Weak on multi-lab longitudinal report aggregation + verification.
Consumer lab aggregators
1mg · PharmEasy · Healthians · Redcliffe
Booking + in-app report storage; consumer scale.Consumer-facing and they own their own labs/pharmacy → they compete with the local lab. We're neutral — we connect independent doctors & labs, taking no side.
Govt cloud EMR
e-Sushrut Clinic · C-DAC new
Subsidised (₹299/mo), ABDM-native, government reach & awareness.Basic EMR only — no doctor–lab network, no research pipeline. It commoditises the EMR and drives ABHA adoption → we sit above it on the same rails.
The national rail
ABDM / ABHA
Government interoperability standard & consent rails.A rail, not a product; adoption patchy → ride it, don't fight it (FHIR-aligned by design).
Our wedge

The neutral doctor–lab network

We connect independent doctors & independent labs and hold the trusted longitudinal record between them — neutral by design, with PDF/OCR as the universal fallback where no API or ABDM reaches.

Risk & defence

Could the EMR layer absorb us?

Govt/funded EMRs own the desk — but not the two-sided network or the data asset. Our moat: neutrality + the accumulated verified record + geographic network density.

See it working

Every lab, every year — one screen at the deskrunning today

Not a mockup. This is the working product on the clinic's own computer: a patient's whole lab history, pulled from reports across different labs and years into one trended view.

One patient, every lab, years

Reports from any lab land in a single timeline — no flipping paper, no re-typing.

Normal band shaded in

Each value is plotted against its reference range, so a drift out of range jumps out at a glance.

Change since last visit

Latest reading and the delta vs the previous one, on every parameter card.

Approaches — How we build it

Built in two clean halves — cloud‑first, with an on‑prem tier

Kept

Two clean halves

One half turns documents into clean data; the other shows it to the doctor. They talk through a standard health-data format (FHIR), so each can improve on its own.

Now default · Cloud

Cloud-first, so the network can exist

Cross-doctor history, lab-fed results and pooled research only work with a shared cloud node. Bharat-hosted, encrypted, consent-gated — the market (and the government) already accept cloud.

Premium tier · On-prem

Self-host for the privacy-anxious

The on-prem build we already have lives on as a paid premium tier for larger or privacy-first clinics. Privacy becomes an up-sell, not a constraint.

Why this matters: the same two-halves design means the de-identified data half is exactly the shared research corpus, and the same bones serve cloud SaaS and the self-host tier — without rebuilding. The earlier on-prem work isn't thrown away; it becomes the premium option.
Architecture — How the two halves fit

Two products, one contract — cloud or on-prem

🖱 Click any block — a product, the API seam in the middle, or the installer frame — for its role, why it matters, and the critical points.

Approaches — Trust & Verification

Centralise extraction · localise verification

  • Verification = transcription fidelity ("does it match the source?") — clerical, done by existing clinic staff in spare minutes.
  • Confidence-tiered: clean & plausible auto-passes; only flagged/low-confidence gets a full check. The cost lever and a pricing lever.
  • Clinical validation stays with the doctor — passively, at the point of care.
Rejected

Doctor as steady-state verifier

Kills the "free the desk" value & the status problem. Bootstrap only — recruit believer design-partner doctors to seed trust.

Already built

The trust machinery

Source-page deep-links · verified/unverified flags · plausibility flags · page-anchored verify screen.

The trust flow end to end — flag → track → confirm against the source. Click any screen to enlarge.

Guardrails: scope the "verified" stamp to transcription, not clinical truth (clean liability) · light QA sampling to prevent rubber-stamping.
Trust — certified, not just claimed

Match the bar on security — then lead on privacy

Doctors trust certified data-handlers. Peers set the bar at ISO 27001 + HIPAA. We match it — then go further on privacy, the one thing our whole product is built around. A sequenced roadmap, not a wall of logos.

Foundation

The security floor

ISO 27001 · HIPAA · DPDP Act compliance. The recognised baseline — what the market already expects.

Our edge · privacy

Certify what we claim

ISO 27701 (privacy management). Privacy-first is our brand — so we certify it, not just say it. Pairs naturally with DPDP.

As we scale

Interoperability & cloud

ABDM Milestone + WASA · SOC 2. Sequenced to the ABDM and hosting steps — earned when they're needed, not before.

Two layers of trust: the product proves it (source links · staff verification · Bharat-hosted, encrypted & consent-gated — with on-prem for those who want it) and the paper certifies it (the standards above). We never ask a doctor for blind trust.
Trust — borrowed credibility

Built with clinicians · validated by a medical college

In healthcare, trust is the gate — and the fastest way through it is to borrow an institution's. A research partner whose name a wary doctor already respects does more than any feature list.

Research partner

A medical college

"Research partner: XYZ Medical College" earns instant trust, gives us an ethics committee for the data play, and feeds the student flywheel.

Clinical pilot

A teaching hospital

A real-world testbed + clinical design input — so "built with clinicians" is a claim we can then make truthfully.

Guardrails

Keep it neutral & honest

Prefer non-competing colleges over corporate chains (protects our neutrality); structure as an MoU, not equity; market a name only once signed; say "research partner", never imply a clinical/device endorsement.

Two kinds of trust, stacked: the certifications prove our security; a college research partner vouches for our credibility & science — and doubles as distribution into the next generation of doctors.
Go-to-Market

Two speeds: labs & MRs fund now, colleges compound later

Now-revenue engine

Labs · MRs · pharma reps

MRs visit clinics daily and own the doctor relationship. Small & off-grid labs onboard fastest — they have nothing to migrate.

Cold-start fix

Saturate one geography

Two-sided networks die spread thin. Densely wire the doctors + labs of one city → referrals actually flow, support is feasible, and it becomes the reference case.

Long-game moat

Colleges & fresh doctors

Free student access + research datasets → citations + habituation → they open clinics as customers. Low CAC, compounding, funded by the network.

Switching cost is the incumbents' wall — so we go where it's zero: greenfield labs with no system, and new doctors with no habits. Pharma stays walled-off — distribution + consented data only, never any say over prescriptions or access to individual patients.
The Roadmap

Stand up the network; the data follows

✓ Built & working

  • Patient records & side-by-side compare
  • Auto-read values & plot trends
  • Out-of-range safety-net + auto-track
  • Staff verify-against-source screen
  • Full clinic system (visits · Rx · billing · pharmacy)
  • Two-product split over a standard (FHIR) data layer
  • On-prem build — now the premium tier

◆ Now — stand up the network

  • Cloud hosting (Bharat, encrypted, consent-gated)
  • Doctor→lab referral + result feed
  • ABDM / ABHA interop

↗ Later

  • Research-data licensing + college program
  • DHIS incentive machine at scale
  • Patient app

The sequence

Saturate one region's doctors + labs → make referrals flow → light up the data asset → colleges & DHIS at scale. Depth in one geography before breadth.

Parked — don't miss

Do the numbers

Lab willingness-to-pay × referrals/clinic × onboarding cost × churn → does the lab-funded model clear at regional density?

The ask · Build it with us

We've built the product. We want doctors and labs to build the network with us.

Doctor-partner

What a doctor brings

Clinical credibility peers trust · real-desk product input · and the cheapest channel there is — doctor-to-doctor referral across your region.

Lab-partner

What a lab brings

The other side of the network — become a connected lab, feed results digitally, and get referrals from every doctor we sign in your area.

What we bring

The build muscle

A working product, the engineering, the data architecture & the strategy — already running. Plus a founding-partner stake (equity and/or revenue-share) for early believers.

The ask: doctors — try it today on your own patients' reports. Labs — let's connect you to the doctors already sending you work. We saturate one region first, so a believer doctor and a believer lab in the same city is exactly how this starts. → Let's start the conversation.
The invitation

Connect the doctor and the lab.
Own the record — and the data — between them.

A working product, a clear path, and a government tailwind that just opened the window. Come build Bharat's neutral doctor–lab network with us.

Let's talk  ·  CubixCode Technologies  ·  [ your email · phone ]

Screenshot