Appointments, e-prescription, GST billing and ABHA linkage for solo clinics and polyclinics — without the hospital-ERP modules you'll never touch.
Most hospital ERPs are built around admission and discharge — beds, wards, OT scheduling, IPD nursing charts. A clinic or polyclinic runs almost entirely on OPD: a patient walks in, is seen, is prescribed, is billed, and leaves the same visit. Forcing that workflow through a hospital-shaped system means configuring modules you'll never use just to book a 10am slot.
The clinic segment in India isn't one buyer — it's at least three. A solo GP or dermatology practice needs the lightest possible setup: one doctor, one front desk, walk-in booking. A dental, eye, or single-specialty practice adds procedure billing and consumables tracking on top of OPD. A 3–10 doctor polyclinic spanning general medicine, paediatrics, and gynaecology needs multi-doctor scheduling, cross-referral between its own doctors, and one consolidated bill even when a patient sees two departments in the same visit. Software built for a 100-bed hospital serves none of these well out of the box.
The buyer is also usually without a dedicated IT person. The software has to work the day it's installed, on a tablet at the front desk, without a training week — which rules out most systems designed around a hospital's IT department doing the configuration.
Walk-in, phone or WhatsApp booking into a live slot grid — front desk shouldn't need a manual to use it.
Drug search, dosage, and a printable or WhatsApp-shareable prescription in the same consult screen.
Per-visit billing with correct GST treatment for consultation vs. procedure vs. pharmacy sale in one invoice.
Automatic recall for follow-ups, vaccination schedules or chronic-care reviews — the visits clinics lose without a system.
Consent-based record sharing so a patient's OPD history follows them to any ABDM-participating facility.
If the clinic adds beds or a second department, the same platform switches on IPD and billing modules — no migration.
| Capability | Basic practice-management app | OneCity clinic mode | Full hospital ERP |
|---|---|---|---|
| OPD appointment booking | ✓ | ✓ | ✓ |
| E-prescription | Often basic | ✓ full drug search | ✓ |
| GST-correct billing | Frequently missing | ✓ | ✓ |
| ABHA / ABDM linkage | Rare | ✓ | ✓ |
| IPD / bed management | ✗ | Switches on if needed | ✓ |
| Pharmacy inventory | ✗ | Optional add-on | ✓ |
| HR / payroll | ✗ | Optional add-on | ✓ |
| Pricing basis | Flat SaaS fee | Per doctor | Per bed |
Basic practice-management tools are typically fine for booking and reminders but weak on GST-correct billing and India-specific compliance. See our comparisons against Practo and DocPulse for how OneCity's clinic mode differs in practice.
OneCity's clinic configuration exposes only OPD, e-prescription, billing, and recall — the four screens a clinic touches daily. Because it's the same underlying 120-module platform as OneCity's hospital ERP, a growing polyclinic that adds a second location, an in-house pharmacy, or a few beds doesn't need to switch systems; the relevant modules simply switch on, and patient history carries forward.
Setup for a solo clinic is designed to take under a day: front-desk staff log in on a tablet, doctors are added with their specialty and consult template, and existing patient records can be imported from a spreadsheet or another system's export. A multi-doctor polyclinic account shares one patient database across specialties, so a patient seen by both a general physician and a gynaecologist in the same visit gets one consolidated bill rather than two separate invoices from two separate systems.
It depends on doctor count and specialty. A solo or 2-3 doctor clinic needs fast appointment booking, e-prescription and billing without hospital-grade overhead. A 5-10 doctor polyclinic adds multi-department scheduling and referral tracking. OneCity starts free for up to 5 doctors and scales into the same platform as its hospital ERP, so a growing clinic never has to migrate systems.
Yes, if the ERP forces you to configure unused modules like IPD, OT or blood bank just to book an appointment. A clinic needs OPD, e-prescription, billing and recall — nothing else. OneCity's clinic mode exposes only these modules, with the rest available later if the clinic adds beds.
The Clinical Establishments Act (or the state-specific equivalent) governs the facility's registration, not the software directly — but the software should produce the records an inspection asks for: patient register, staff qualifications, and standard treatment records. OneCity generates these automatically from routine OPD entries. See our Clinical Establishments Act registration guide.
Yes, where the clinic opts in. ABHA-linked OPD records let a patient's visit history follow them to any ABDM-participating facility. OneCity supports ABHA verification and consent-based record sharing from the same OPD screen used for a normal walk-in.
Hospital ERP pricing is usually per-bed. A clinic has no beds, so OneCity prices clinic mode per doctor instead — free up to 5 doctors, then a per-doctor rate above that. If the clinic later adds an IPD ward, billing switches to include a per-bed component for that ward alone.
Yes. A polyclinic account supports multiple doctors across different specialties under one front desk and one billing ledger, with each doctor's appointments, prescriptions and consult notes kept separate while sharing the same patient record.
No card, no setup fee, up to 5 doctors free. WhatsApp us and we'll walk you through it.
