One system for every location — correct GSTIN per site, a patient record that follows the patient, and a rollout sequence that doesn't repeat the same risk at every site simultaneously.
A hospital group running three locations doesn't need three separate installations of the same software, coordinated by spreadsheet. It needs one system that knows there are three locations, keeps each one's billing and compliance correctly scoped to itself, and still lets a group administrator see the whole picture without stitching reports together by hand.
| Stays location-specific | Can be shared or consolidated |
|---|---|
| GSTIN and tax invoices (per Section 25, CGST Act, 2017) | Group-level financial reporting and dashboards |
| Bed inventory and ward assignment | Patient master record, if the patient is treated across locations |
| Local KPME/state-specific registration details | Drug master, pricing templates, compliance configuration |
| Staff rostering and payroll per site | HR policy templates and role definitions |
Under Section 25 of the CGST Act, 2017, a business operating in more than one state needs a separate GST registration for each state. Locations within the same state typically operate under a single registration, though a group can choose separate registrations per location within a state as well. Either way, the billing module has to generate the correct GSTIN on every invoice at every location without an administrator manually switching a setting per patient, since a hospital chain operating in two or three states is running what are, for GST purposes, effectively separate registered entities under one brand.
A patient who visits the flagship location for a specialist consult and later goes to a satellite location for a follow-up shouldn't be treated as a new patient with no history. A genuinely unified ERP carries that record across locations; a group running separate installations per site, even of the same software, usually can't, unless someone built a custom integration between them, which is itself a maintenance burden the group now owns indefinitely.
The same phased, staggered discipline that applies to a single-hospital ERP implementation applies across locations, at a larger scale. A group's fastest, least disruptive path runs one location through the complete five-phase rollout, readiness audit, migration, training, staggered go-live, stabilisation, before starting the next location's Phase 1. The second location's rollout is typically faster than the first, since data-cleanup patterns, staff-training material, and configuration decisions carry over directly. Attempting all locations simultaneously repeats the same failure mode as a single-hospital big-bang go-live, at group scale: no location becomes a working reference point before the others depend on the same untested assumptions.
A single group-level AMC and managed support plan covering every location is usually more effective than negotiating separate contracts per site, both commercially and operationally, since a support team that already understands the group's configuration doesn't need to re-learn it at each location. The SLA still needs to account for real differences between sites, a flagship location with a 24/7 ER and a satellite OPD-only clinic don't need identical response-time tiers, but the underlying contract and support relationship can be one, not many.
Under Section 25 of the CGST Act, 2017, a separate GST registration is required for each state a hospital group operates in. Multiple locations within the same state can generally operate under one registration, though a group may also opt for separate registrations per location within a state if it prefers distinct place-of-business filings.
Yes, if the ERP is genuinely unified across locations rather than run as separate installations per site. This depends on the platform's architecture, not just its feature list.
No. A pilot-site-first approach, completing the full implementation at one location before starting the next, surfaces configuration and data issues once rather than simultaneously across every site.
A unified ERP can report consolidated financials at the group level while still generating location-specific, GSTIN-correct invoices at each site, since each location's GSTIN must appear correctly on its own patient bills.
No, a single group-level AMC covering all locations is more common and typically more cost-effective than separate per-site contracts, provided the SLA accounts for each site's connectivity and staffing differences.
Tell us how many locations and states you operate in.
Talk to OneCity