Krishna
Founder, ShylCare
A hospital group in Pune told me something last year that stuck with me. They have three branches — two in the city, one in a nearby town. Every month-end, their accountant spends four days reconciling numbers across branches. Four days. Because each branch runs a different billing system, pharmacy stock is tracked in separate spreadsheets, and nobody agrees on what the actual consolidated revenue is.
"We built a 100-bed hospital group," the owner said, "but we still run like three independent clinics."
This is more common than anyone admits.
The first branch runs on whatever software was available — maybe Tally for billing and a local EMR someone installed. It works well enough.
When the second branch opens, someone makes a reasonable-sounding decision: "Let's use the same software." But the second branch has different departments, different doctors, slightly different workflows. Someone installs a separate instance. Now you have two databases that don't talk to each other.
By the third branch, there's usually a mix — one branch on the original software, one on a different system someone recommended, one still using paper and Excel for half its processes.
Each branch is functional in isolation. Together, they're a mess.
Consolidated reporting is fiction. When each branch has its own database, "group revenue" means someone exports data from three places, pastes it into Excel, and hopes the column names match. Want to compare OPD volume by branch for the last quarter? That's a two-hour project. Want to see which branch is more profitable? You'll need a week and an accountant who doesn't mind crying.
Pharmacy stock is a black hole. Branch A is sitting on 200 strips of Azithromycin that are expiring in two months. Branch C ran out last week and placed a fresh purchase order. Nobody knows because stock lives in separate systems. I've seen hospital groups where expired stock write-offs at one branch exceed ₹50,000 a month while another branch is doing emergency purchases of the same drugs at retail price.
Stock transfers are untracked. "Bhaiya, Khamla branch se 50 strips bhejwa do" — this happens over WhatsApp. Sometimes it gets entered into the system. Sometimes it doesn't. At month-end, neither branch's inventory matches physical count. Who lost the stock? Nobody knows. Everybody suspects everybody.
Patient history doesn't travel. A patient who usually visits your Vashi branch shows up at your Panvel branch because it's closer to their office. The doctor there has no access to their previous prescriptions, lab results, or medical history. So they start from scratch — new consultation, repeat diagnostics, sometimes contradictory medication because they don't know what the patient is already taking.
Doctor schedules across branches are manual. If a specialist visits two branches on different days, coordinating their appointments means phone calls between receptionists. Double-bookings happen. Patients show up to find the doctor is at the other branch today.
Every multi-branch hospital goes through what I call the spreadsheet phase. Someone — usually a frustrated admin — creates a master Excel file that pulls data from all branches. They spend hours maintaining it. It's always slightly out of date. It becomes a single point of failure (what happens when that person goes on leave?). And slowly, the spreadsheet itself becomes the source of truth, which means the actual software systems are now secondary.
This is backwards, but it happens because the underlying systems weren't designed for multi-branch operation.
The fix isn't "better data integration" between separate systems. That's a band-aid. The fix is a single platform with branch-level isolation.
Here's what that means in practice:
One database, branch-level access control. Every branch's data lives in the same system. But staff at Branch A only see Branch A's patients, billing, and stock by default. Managers and owners see everything. The data is unified, but the day-to-day experience is scoped to each location.
Unified patient records. When a patient visits any branch, their full history is available. Previous prescriptions, lab results, allergies, billing — everything. The doctor at your second branch sees exactly what the doctor at your first branch saw. No phone calls, no file transfers, no "can you WhatsApp me the reports?"
Consolidated reporting that's instant. Revenue by branch, by department, by doctor — it's a filter, not a four-day Excel project. You can compare branch performance in real time instead of post-hoc.
Pharmacy stock with transfer tracking. Stock transfers between branches are recorded transactions with approval workflows. You know what went where, when, and who authorised it. Consolidated stock views mean you can see group-wide inventory and redistribute before things expire.
Centralised master data. Drug lists, service rate cards, doctor profiles — maintained once, available across all branches. When you update the consultation fee for a service, it updates everywhere. No branch-by-branch data entry.
Hospital owners who move to a unified platform always tell me the same thing: the biggest benefit wasn't the reporting or the stock tracking. It was that they stopped having arguments about numbers. When everyone is looking at the same data, meetings become about decisions instead of about whose spreadsheet is right.
That alone is worth more than any software license.
If any of this sounds familiar, we'd love to show you how ShylCare handles it. Book a demo.
We'll walk through your actual workflows — no generic demo, no slide deck.