One system for the
whole hospital

India-native compliance

The real cost of running separate systems is not the license fees, it is the staff time spent reconciling data that should already agree. A billing clerk re-entering patient demographics that the front desk already captured. A pharmacist checking a handwritten prescription against a lab result open in a different browser tab. A quality coordinator pulling infection-control data from three spreadsheets into a fourth one for the NABH assessor. Every manual handoff between systems is a point where data gets delayed, duplicated, or dropped, and in a hospital those errors have clinical consequences, not just administrative ones. A unified system does not fix bad processes, but it removes the excuse that the data lived somewhere the person who needed it could not reach in time.

For a 50 to 200 bed hospital running on tight margins, the arithmetic is specific. Two data-entry staff spending 90 minutes a day re-keying records across OPD, pharmacy, and billing is roughly 45 hours a month of paid labour producing zero clinical or financial value. That time is the recurring cost a single-database system eliminates on day one, before any workflow improvement, before any compliance benefit, just by making the same record available everywhere without re-entry.

Every compliance mandate handled inside the workflow

Who this is for

Indian hospitals face a compliance stack that no other country quite matches: ABDM (ABHA verification, HFR registration, health record exchange via HIP and HIU roles), NABH (quality indicators, incident reporting, structured discharge summaries), FSSAI (canteen licensing with perpetual validity and annual FSCR filing), AERB (equipment-level radiation safety licensing), BMW Rules 2016 (colour-coded segregation, CPCB manifest logs), PCPNDT (Form F for every ultrasound, permanent retention), GST (exemptions on room rent below ₹5,000, e-invoicing for taxable supplies), DPDP Act 2023 (consent management, data retention justification, breach notification within 72 hours), and Clinical Establishment Act or state equivalents like KPME in Karnataka. Each one has its own register, its own renewal or filing cycle, and its own inspection authority. A hospital tracking these in separate spreadsheets is not managing compliance, it is managing the risk of forgetting which spreadsheet to check this month.

Built for the hospitals that enterprise vendors ignore

Recently launched

Enterprise hospital software in India is priced and designed for 500-bed metro hospitals with a dedicated IT department, a reliable 50 Mbps fibre line, and a budget that treats ₹25 to 50 lakh in annual license fees as a line item. A 75-bed district hospital in Hubli, a 40-bed maternity hospital in Madurai, or a 120-bed multi-specialty in Raipur does not operate in that environment. The internet drops for hours at a time, the IT staff is one person who also manages the CCTV system, and the budget for all software combined is what the enterprise vendor charges for the pharmacy module alone.

OneCity is built for that second hospital. The system runs on 2 Mbps, syncs when connectivity returns, and works on the Android tablets the staff already carry. Pricing starts at ₹999 per month, scales by bed count and active doctors, and publishes every number on the pricing page rather than hiding it behind a "contact sales" form. The free tier covers up to 5 doctors with no time limit, no card, and no setup fee, so a hospital can run a real pilot on its own data before committing anything.

Modules hospitals are deploying now

Common questions

What hospitals ask before switching

Three questions come up in almost every evaluation call. First: can we migrate our existing data, or do we start from scratch? OneCity imports patient master records, stock data, and financial ledgers from any system that can export a CSV or a database dump. The migration runs in parallel while the old system stays live, and the hospital cuts over only after verifying the imported data matches. Second: what happens if the internet goes down mid-shift? The system is offline-capable. Registrations, prescriptions, and billing continue on the local device and sync automatically when connectivity returns, with conflict resolution handled by timestamp rather than overwrite. Third: what if we need a module you have not built yet? The product roadmap is public, and custom module requests from paying hospitals go into a quarterly prioritisation cycle with a documented SLA on delivery timelines.

The question hospitals should ask but usually do not: what are the exit terms? OneCity's contract includes a full data export clause, your data in open formats (CSV, HL7 FHIR, PDF), delivered within 30 days of a termination notice, at no additional charge. A hospital that cannot get its own data out of a vendor's system is not a customer, it is a captive. That distinction matters more than any feature comparison.

Frequently Asked Questions