Skip to content

Status and roadmap

Published with its real status — including the unflattering parts.

Every feature carries one of four statuses. This page lists what is proposed and, more importantly, what is not built. It is the section that actually recruits.

0

Live

Works in the product

0

Engine

Engine built and tested, screen not wired

0

Designed

Designed or schema only

0

Proposed

Proposed, not started

Global caveat

Nothing persists to a database yet. The whole product runs on in-memory state. Persistence is the current milestone.

Proposed · 1 of 3

Deadline-driven

Regulatory shifts give hospitals a reason to look again at their software — not proof that anyone must switch.

Proposed Not started. Sequenced after persistence.
#29 High conviction

DPDP compliance spine

Consent workflow, retention logging aligned to the notified requirements, role-based access, and operationalised patient rights — access, correction, withdrawal, grievance. DPDP’s principal obligations are scheduled for May 2027, with Consent Manager registration provisions activating from November 2026 (not a blanket hospital integration deadline). Section 17(3) leaves room for notified exemptions for certain entity classes, and a hospital retains responsibility for its own data processing regardless of its software vendor. We already hold some of the primitives: consent records, record-access log, e-signatures, retention batches.

#30 High conviction

The three-hour cashless discharge clock

IRDAI has published a three-hour cashless-claim expectation tied to NHCX; the exact trigger event and current circular need confirming before we build a compliance claim on top of it. Our seven-gate discharge clearance and NHCX-shaped insurance stages are already the right shape for a live countdown per case and a “what is blocking the clock” view, once that is confirmed.

#31 Proposed

NABH Entry Level as a packaged outcome

NABH’s revised Entry Level programme is reported to include a PMJAY incentive for certified hospitals; chapter count, evidence-period requirements and exact terms need verification against the current programme manual before we build to them. Once confirmed, we would ship the objective-element checklist, a patient-rights display, standardised consent forms and an evidence trail on top of the QMS loop we already have.

#32 Proposed

ABDM with the certification burden owned by us

The ABHA creation flow is small work; the real value is that FHIR R4 conversion, sandbox certification and consent management sit with the vendor so the hospital never sees them. Sequenced after persistence — NHA milestone certification is calendar time, not engineering time.

Proposed · 2 of 3

Pain-point-driven

Why deals in this segment often die, based on the market research behind this roadmap.

Proposed Not started. Sequenced after persistence.
#33 High conviction

Degraded-network mode

Poor connectivity is a commonly cited cause of HMIS failure in non-metro India. Local-first with sync is hard, and therefore defensible — but full bidirectional sync also introduces real conflicts in patient identity, bed allocation, inventory and billing that need their own design before we can claim it works.

#34 Proposed

A published click budget

Doctors reject software that needs too many clicks. The goal: admit a patient in three clicks or fewer, record a dose in two — measured against realistic inputs and the hospital’s required checks, then published on the features page.

#35 Proposed

Self-serve onboarding and migration

Small hospitals often report that vendor training lasts about a week, then support disappears. Extend the existing getting-started checklist into guided setup plus Excel and legacy import, so a hospital can run without us.

#36 Proposed

Roles built for people who do three jobs

Small hospitals have no dedicated data-entry operators; the receptionist is also billing and also pharmacy. One combined shift-worker view instead of three role-shaped silos.

#37 Proposed

Triage acuity scoring (ESI or Manchester)

A standards-based five-level engine — auditable, not a model. We did not find this in the vendors we reviewed, and it is often the first question a clinical buyer asks. Any adopted scoring system would need qualified clinicians to select and validate it before use.

Proposed · 3 of 3

AI — tiered by defensibility

Proposed AI work, ordered by how defensible it would be once real data exists. None of it runs today.

Proposed Not started. Sequenced after persistence.
#38 High conviction

Boarding and length-of-stay prediction

A research direction: whether boarding, escalation and suitability event data — once persistence ships and a pilot generates volume — can usefully predict which patients will still be boarding in four hours and which bed frees first. No dataset exists yet, and no competitor’s data access has been established either way.

#39 Proposed

Discharge summary drafting

Highest value, lowest clinical risk — the structured inputs already exist in admission, diagnosis, MAR, orders and results. Draft it, a clinician reviews and signs, and it would feed the three-hour cashless clock once that rule is confirmed. Generated text would not independently issue a discharge.

#40 Proposed

Pre-submission claim scrub and denial prediction

For India this means TPA-specific document completeness and pre-auth gap detection before submission — a deterministic checklist first. Industry reports (not independently verified by us for the Indian market) describe denial-prevention programmes cutting denial rates 30–40%; we would not present that figure as our own result without measuring it.

#41 Proposed

Coding and PMJAY package assistance

Suggesting a candidate PMJAY package, for a trained reviewer to confirm against documentation and eligibility, is a direct revenue lever once NABH incentive terms above are confirmed.

#42 Proposed

Roster optimisation

The constraint engines already exist — rest hours, consecutive nights, credential validity, exact cost. Suggesting the cheapest compliant roster within those hard constraints is an optimisation problem we can start on now, not a research problem.

#43 Proposed

Hinglish OPD scribe — with the caveat stated

Reported (not independently verified by us) word error rates of 15–25% on Indian accents and code-switching are a real reason for caution, and always-on cloud assumptions fail on hospital connectivity; patient audio is also DPDP-scoped. If built, it would run on-premise or in-country, ship as an assistive draft requiring sign-off, and we would publish our own measured error rate rather than borrow someone else’s.

Explicitly not building

Anything diagnostic, or triage acuity assigned by a model. Regulatory exposure — and it repels precisely the clinically literate partner we are recruiting.

What isn’t built

The section that actually recruits.

Four empty boxes. For a partner with hospital relationships, the last one is the most valuable thing on this page.

Two clinicians in white coats talking in a hospital
Designed

Persistence

The entire hospital domain runs in memory; the first Emergency migration exists and nothing consumes it. The DPDP compliance milestone (May 2027, per the notified schedule) is roughly eight months out from today. Persistence is the block between us and being ready for it.

Designed

Clinical validation

No practising clinician has reviewed the triage flows, MLC handling or drug rules. The rule packs carry an explicit unverified_demo flag and read “verify before use”, deliberately, so nothing poses as a legal citation it hasn’t earned.

Designed

Regulatory verification

NABH mapping, Drugs & Cosmetics Rules schedule assignments and retention rules are modelled but unverified by anyone qualified to sign them off.

Designed

Pilot hospital, revenue and distribution

No pilot site, no paying customer, no go-to-market. For a partner with hospital relationships, this is the most valuable empty box on the page.

We are looking for

A clinical partner who has run a small hospital, and a distribution partner who knows fifty of them.

If you have argued with a management report about boarding patients, or watched a vendor vanish after training week, we would like to talk.

Start the conversation

Persistence is the current milestone.

Founding hospitals shape the order after that. Tell us which deadline matters most to you — DPDP, the three-hour clock or NABH Entry Level.

Talk to the founder See pricing

Or try the demo yourself