Frequently asked questions

MedOrbit is an AI-native hospital management system built for 24 types of Indian healthcare facility, from a solo clinic to a government hospital. ABDM-ready means ABHA creation, consent-managed record sharing and FHIR R4 exchange are built and waiting on National Health Authority certification — not live today, and any vendor who claims otherwise should be asked for the certificate. Compare us on the rails you actually run on: ABDM, NHCX claims, PM-JAY and CGHS desks, GST e-invoicing, DLT-compliant messaging and data residency in India.

Twenty-four today: clinics (solo, poly, dental, AYUSH, physio), diagnostics (pathology lab, imaging centre, diagnostic center), small inpatient (nursing home, maternity, day-care surgical, eye, IVF, dialysis), hospitals (single, multi and super-specialty, teaching, government) and networks (chains, blood banks, home healthcare, retail pharmacy). Each type is a real configuration rather than a label: the modules, role menus and dashboards change with it, and the server enforces the difference.

Not yet in full — published figures go on the pricing page once each edition's inclusions are verified. Until then, ask us for a written quote for your facility type; the drivers are the same ones the pricing page will show: edition, facility type and metered AI usage.

No. A facility type — clinic, lab, nursing home, hospital and so on — decides which modules and role menus you start with; an edition decides how many facility types and branches you can run. A single-branch nursing home and a hospital chain can both run on the HOSPITAL edition, configured differently by facility type.

Yes. MedOrbit ships one Flutter mobile app with separate doctor and patient experiences in a single binary, covering the same appointments, results, prescriptions and messaging the web portal offers.

Yes. The front-desk voice agent answers your hospital line around the clock, quotes queue status, and books, reschedules or cancels appointments straight into your schedule — in Hindi or English. Every booking action is cryptographically signed and every call is logged, so your staff opens the morning worklist knowing exactly what was said. The agent never diagnoses, and telephony is armed per facility, so you decide when it starts taking calls.

Every agent is flag-gated per tenant, reads only what its job requires, and writes every action to a tamper-evident audit trail. A human signs the note, approves the prescription, resolves the flag or files the appeal — the agent drafts, your staff decides, and each agent has its own kill switch.

Yes. MedOrbit runs in AWS ap-south-1 (Mumbai), and patient records, documents and backups stay in that region. Lab report PDFs are digitally signed and prescriptions carry a verifiable QR code, so a document can be checked outside the system. Access to patient data is logged per user.

Consent is recorded in a ledger rather than assumed, and data-principal requests — access, correction, erasure — are handled inside the system with an audit trail. Patient identifiers are redacted before any AI model call, and your data is not used to train models. Breach registers and grievance routing are part of the same tooling, so a request never depends on someone remembering to file it.

Access is role-based and tenant-scoped, with row-level security on the most sensitive PHI tables and app-layer tenant scoping throughout. Patient identifiers are redacted before any AI model call, every AI action is written to a tamper-evident audit trail, and each agent has a kill switch. Spending on AI is capped per facility per day, and clinical documents leave the system signed.

No. Patient identifiers are redacted before any AI model call, and your data is not used to train models. Records, documents and backups stay in AWS ap-south-1 (Mumbai) for the life of your account.

MedOrbit is priced per facility per month across five editions, so a solo clinic doesn't pay for a government network. Published figures go on the pricing page once each edition's inclusions are verified; until then, ask us for a written quote for your facility type and we will show you what drives it. AI agent usage is metered separately, under a daily spend cap you set per facility.

There are five editions, sized from a single practitioner to a multi-site government network. A clinic usually starts with OPD, billing and the front-desk agent; a hospital starts with IPD, diagnostics, pharmacy and claims included. An edition is a starting shape, not a ceiling — moving up switches modules on rather than moving your data.

Yes. Guided imports cover patients, staff, doctors, tariffs and stock, and HL7 v2, FHIR R4 and CSV pipelines bring historical records across. Plan the sequence with us — masters first, then balances, then history — so billing stays reconcilable from day one.

Training is role-based: receptionists, nurses, doctors, pharmacists, lab staff and billing each get a walkthrough of the screens they actually use. Go-live is supported by the team that builds the platform, and every facility has a named contact. AI agents come last and one at a time — you switch one on, watch it work in dry-run, then let it act.

Each edition switches on a different module set and role catalog — CLINIC_LITE for a solo or group practice, DIAGNOSTICS for a lab or imaging centre, HOSPITAL for inpatient care and claims, ENTERPRISE for a multi-branch chain, and PUBLIC_GOVT for a government facility. The gate is enforced server-side, not a hidden menu item, so moving up switches modules on rather than moving your data.

No. Guided imports bring patients, staff, doctors, tariffs and stock across first, then HL7 v2, FHIR R4 and CSV pipelines carry balances and history — sequenced with us so nothing is dropped and billing stays reconcilable from day one.

Yes. Every facility has a named contact from the team that builds the platform, not a ticket queue handed to a reseller. Role-based training happens before go-live, and AI agents are introduced one at a time afterward, in dry-run first.