Krishna
Founder, ShylCare
A 120-bed multi-specialty hospital in Pune asked me this question last year, and it's one I've thought about a lot since: "Should we buy one system that does everything, or should we buy the best lab software, the best pharmacy software, the best billing software, and connect them together?"
It's a genuine dilemma. Both approaches have real advocates, real success stories, and real failure modes. The answer depends on your size, your IT capacity, and — honestly — your tolerance for pain.
The argument is intuitive: no single vendor is equally good at everything. The company that builds a great OPD workflow might build a mediocre LIS. The one with the best pharmacy module might have clunky billing. So why not pick the best in each category?
Specialised depth. A standalone LIS built by a team that only thinks about labs will have features that a general HMS lab module doesn't — analyser interfacing for 30+ machines, NABL compliance workflows, QC tracking, delta checks. If your lab processes 500+ samples a day, these features matter.
Flexibility. If your pharmacy module isn't working, you replace it without touching the rest of the system. You're not locked into one vendor's roadmap for everything.
Vendor accountability. When each system is owned by a specialist vendor, they compete on their specific domain. Your LIS vendor knows that if they don't perform, you'll switch to another LIS — not rebuild your entire hospital IT.
Now the other side.
Data flows without plumbing. When a doctor orders a lab test, it should appear in the lab's worklist. When the lab enters the result, it should appear in the doctor's EMR. When the pharmacy dispenses a drug, it should appear on the patient's bill. In an integrated system, this happens automatically — the data lives in one database, displayed in different views.
In a best-of-breed setup, every one of these handoffs is an integration point. Each integration point is a potential failure point, a potential data mismatch, and a definite maintenance burden.
The single patient record. This matters more than most IT discussions acknowledge. When a patient is admitted, their journey crosses departments — OPD consultation, lab tests, radiology, pharmacy, procedures, nursing, billing. In an integrated system, all of this is one record. In a best-of-breed setup, the patient exists as separate entities in separate systems, linked (hopefully) by an MRN that may or may not sync correctly.
When the discharge summary needs to pull together everything that happened during the stay — medications given, labs ordered, procedures performed, vitals recorded — an integrated system generates this from one source of truth. A best-of-breed setup requires pulling data from four different systems and hoping nothing was lost in translation.
One vendor to call. When something breaks at 11 PM on a Sunday, you call one number. In a best-of-breed setup, the lab system says it's a billing issue, the billing system says it's a data feed issue from the lab, and you're playing mediator between two vendors at midnight.
Lower total cost of ownership. This is counterintuitive — best-of-breed vendors often have lower individual licensing costs. But the total cost includes integration middleware, API maintenance, data reconciliation efforts, and the IT staff needed to keep it all running. For a hospital under 150 beds that doesn't have a dedicated IT team, this hidden cost is significant.
In theory, there's an elegant solution: use best-of-breed systems that all speak the same language. HL7 and FHIR are healthcare interoperability standards designed exactly for this — a common format for exchanging patient data, lab results, medication orders, and billing information.
In practice, in the Indian market in 2026, here's what actually happens:
HL7 support is claimed, not implemented. Many Indian HMS vendors list "HL7 compliant" on their website. What they mean is: "We can export data in a format that sort of resembles HL7 if you ask us nicely and pay for a custom integration." True real-time HL7 messaging — where an order placed in System A instantly appears as a worklist item in System B — is rare outside the top-tier hospital chains.
FHIR is even further away. FHIR is the modern, API-friendly successor to HL7. It's gaining adoption in the US and Europe. In India, ABDM (Ayushman Bharat Digital Mission) is pushing FHIR-based standards, and this will eventually change things. But right now, most Indian HMS vendors are still working on basic ABDM compliance, not offering plug-and-play FHIR APIs for inter-system communication.
Integration middleware exists but costs money and attention. Tools like Mirth Connect can bridge different systems. But someone needs to set them up, maintain the mappings, handle errors when messages fail, and update everything when either vendor changes their API. That someone is either an expensive consultant or your IT staff (if you have any).
The net result: interoperability is the correct long-term answer, but it's not a practical answer today for most Indian hospitals under 200 beds.
Here's my honest framework.
Under 50 beds: integrated system, no question. You don't have IT staff. You can't maintain integrations. You need one login, one vendor, one database. The integrated system won't be best-in-class at every module, but it'll be good enough at all of them, and — critically — the data will flow without you doing anything.
50-150 beds: integrated system with selective best-of-breed where it's critical. If your lab does high volume and needs analyser interfacing with 15 machines, get a standalone LIS and integrate it. If your pharmacy is a profit centre doing retail sales alongside inpatient dispensing, maybe a dedicated pharmacy system makes sense. But keep the core — EMR, IPD, billing, nursing — on one platform.
150+ beds: you have choices, but you also have IT staff. At this scale, you probably have (or should have) a dedicated IT team that can manage integrations. Best-of-breed becomes viable because you have the humans to maintain the plumbing. But even here, I'd argue that the core clinical workflow — doctor's EMR, nursing, IPD, OPD — should be one system. Departmental systems (LIS, RIS, pharmacy) can be separate if there's a strong reason.
In my experience, the hospitals agonising over this decision are almost always in the 30-150 bed range. And for them, the answer is almost always: start with an integrated system. Here's why.
The integration tax is real. Every time I've seen a sub-150-bed hospital try to run five different systems with custom integrations, they end up spending 30-40% of their IT budget just keeping the pipes connected. That's money and attention that should go toward actually using the software to improve patient care and billing efficiency.
And the depth gap between a good integrated system's lab module and a standalone LIS? It's smaller than the LIS vendor wants you to believe. Unless you're running a reference lab processing thousands of samples across specialised departments, the lab module in a decent integrated HMS will cover your needs.
ShylCare is an integrated platform — OPD, IPD, pharmacy, lab, radiology, billing, accounts — built as one system with one patient record. We made this architectural choice deliberately because our core market is the sub-150-bed hospital where integration tax is the silent killer of IT projects.
Every module talks to every other module natively. Doctor orders a test, it appears in the lab worklist. Lab enters results, the doctor sees them. Pharmacy dispenses, the bill updates. Discharge summary pulls from everything. One database, one login, one vendor to call.
For hospitals that do need a standalone LIS or pharmacy system alongside ShylCare, we're building toward standard interoperability. But we'd rather have you not need it.
Curious how ShylCare fits your setup? Let's talk.
We'll walk through your actual workflows — no generic demo, no slide deck.