An eight-point checklist for a 20–100 bed Indian hospital — bandwidth, price, KPME, NABH 6th edition, vernacular UX — and where OneCity fits.
India's hospital software market splits by buyer. Large private chains — Apollo, Fortis, Max, Manipal — run custom or heavily-configured systems. Global names like Epic and Cerner appear only at a handful of premium sites. The largest segment by count is the tier-2/3 hospital and the single-specialty nursing home, and most of it still runs on paper or a thin practice-management tool. That is the buyer this guide is for.
The right system for a 20–100 bed hospital is not a shrunken enterprise suite. It is a product designed around the real constraint: patchy bandwidth, Android tablets, staff who work in Kannada or Hindi, a ₹5-lakh-a-year budget, and Indian compliance — KPME, ABArK/PMJAY, NABH 6th edition, BMW 2016, DPDP 2023 — that a bigger tool treats as an afterthought.
The buying mistake tier-2/3 administrators make most often is evaluating hospital ERP the same way a 300-bed chain would: RFP against a feature checklist built for enterprise procurement, then discovering post-purchase that half the modules assume an IT department that doesn't exist on-site. The right evaluation starts from the operating constraint — bandwidth, staff literacy with software, and which compliance filings the hospital actually has to produce this quarter — and works outward to features, not the other way round.
Does it work offline-first at 2 Mbps? A cloud-only system that freezes when the line drops is unusable in Kalaburagi or Hubballi.
Per-bed or per-doctor pricing, not an enterprise licence. A 20-bed hospital should pay for 20 beds.
Does it handle your state's registration (KPME in Karnataka) and scheme claims (ABArK, PMJAY) natively, or bolt them on?
EMR, ABDM linkage, quality indicators in 6th-edition format — effective January 2025. Paper scores lower now.
Front-desk and nursing staff work in the regional language. English-only screens slow every shift.
Can one person set it up on a tablet, or does it need an IT team you do not have?
One system for BMW 2016, DPDP 2023, GST e-invoice, ABDM — not four vendors and a spreadsheet.
Can it import your existing patient, billing and inventory data without a six-month project?
| Requirement | Enterprise hospital ERP | Tier-2/3-built system (OneCity) |
|---|---|---|
| Offline-first operation | Usually assumes reliable connectivity | ✓ built for 2 Mbps |
| Pricing basis | Quote-based, sized for 200+ beds | Per-bed / per-doctor, from ₹999/month |
| KPME / state scheme handling | Often a custom add-on project | ✓ native |
| NABH 6th edition evidence | Depends on configuration effort | ✓ built in |
| Vernacular front-desk UX | Rare | ✓ Kannada/Hindi |
| Setup effort | Needs an implementation team | Tablet, same-day for OPD |
| Migration from legacy data | Formal, often lengthy project | Scoped against your export on a demo call |
This isn't a claim that enterprise suites are bad — they're built for a different buyer. A 250-bed chain with an IT department gets real value from that depth. A 20–100 bed hospital paying enterprise pricing for enterprise complexity it can't staff is the mismatch this checklist exists to catch.
OneCity is a Bengaluru-built hospital ERP that treats the 20–100 bed hospital as the design centre. It runs offline-first on an Android tablet, prices from a ₹999 entry SKU, handles KPME and ABArK natively, is NABH 6th-edition and ABDM-ready, and covers BMW 2016, DPDP 2023 and GST e-invoice in one codebase. It is pre-launch, moving toward a free pilot at a small number of Karnataka hospitals — which is exactly the moment to shape it around your workflow.
Setup follows the same one-day pattern as OneCity's clinic configuration: front-desk staff log in on a tablet, wards and beds are configured against the hospital's actual floor plan, and existing patient and billing records import from a spreadsheet or a competing system's export rather than starting from a blank database.
There is no single best system for every hospital — fit depends on bed count, bandwidth, language and budget. For a tier-2/3 hospital of 20–100 beds on patchy connectivity, the best fit is a product designed offline-first, priced per-bed, and native to Indian compliance (KPME, ABArK/PMJAY, NABH 6th edition, BMW 2016). OneCity is built to that constraint at a ₹999 entry SKU.
Costs range widely — roughly ₹50,000 to over ₹10 lakh a year depending on hospital size and features. Enterprise suites are quote-based and scoped for larger hospitals. OneCity starts at a ₹999/month entry SKU with per-bed and per-doctor tiers, aimed at the tier-2/3 buyer.
Rarely for tier-2/3. Epic and Cerner are deployed at a small number of premium Indian sites and are built for US health-system workflows and payer models. They do not fit a 20–100 bed Karnataka hospital without heavy, expensive customisation. An India-built system aligned to ABDM and state schemes fits better.
At minimum: state registration (KPME in Karnataka), scheme claims (ABArK, PMJAY), NABH 6th edition, Bio-Medical Waste Rules 2016, DPDP Act 2023, GST e-invoice, and ABDM/ABHA. OneCity covers these in one codebase rather than across several vendors.
Enterprise hospital ERP is typically quote-based and licensed per facility, scoped for 200+ bed chains. A tier-2/3 hospital should look for per-bed or per-doctor pricing instead, so a 30-bed hospital pays for 30 beds — not an enterprise licence sized for ten times that capacity.
A proper migration path imports existing patient records, billing history and inventory data rather than starting from zero. Ask any vendor to scope the migration against your current system's actual export format before signing — a vendor unwilling to commit to this is signalling a harder switch than they're letting on.
OneCity is heading into free pilots at a few Karnataka hospitals. WhatsApp us to be one of them.
