An EMR decision is not a software comparison. It is a clinical, operational and financial decision that will shape how the organisation works for the next decade or longer.
The demonstrations will all look good. The roadmaps will all look credible. The harder questions are what happens after the contract is signed: how the platform fits the clinical model, what has to integrate around it, how much local capability the organisation needs, where the implementation risk really sits, and which promises survive contact with a live hospital.
I advise hospitals, health systems, governments and investors through that decision independently. No platform commission. No implementation revenue attached to the recommendation. The objective is to make the right decision before it becomes expensive to reverse.
Most selection processes become feature comparisons too early.
That is understandable. Vendors are good at demonstrating what their platforms can do. The more important question is what the organisation actually needs the platform to do, under its own clinical workflows, regulatory environment, integration landscape, operating model and budget.
A strong selection process starts before the shortlist.
A replacement EMR is sometimes the right answer. Sometimes the existing platform is capable of considerably more than the organisation is getting from it.
Before starting procurement, I look at whether the problem is genuinely the platform or whether it sits in workflow design, configuration, integration, adoption, governance or operating capability.
Replacing the technology without understanding that distinction can turn an optimisation problem into a multi-year transformation programme.
Requirements should reflect how care is actually delivered, not become a catalogue of every feature every department would like.
The work is identifying what is genuinely differentiating: patient flow, medication management, theatre, emergency care, specialty workflows, revenue cycle, diagnostics, interoperability, digital access and the regulatory requirements the platform has to support.
The aim is not the longest requirements document. It is knowing which requirements should change the decision.
No enterprise clinical platform operates alone.
Laboratory, pharmacy, radiology, PACS, medical devices, ERP, revenue cycle, digital patient platforms, national exchanges and increasingly AI all sit around it.
A platform can score well functionally and still create the wrong architecture for the organisation around it.
For organisations deciding whether to optimise, replace or deploy an EMR for the first time.
I assess the existing environment, clinical and operational priorities, technology constraints, regulatory requirements and internal capability before defining what the platform decision actually needs to achieve.
Outcome: A clear decision frame before vendors enter the process.
Translate clinical, operational, technical and financial priorities into an evaluation model that can distinguish between vendors rather than giving every platform a passing score.
That includes evaluation criteria, weighting, demonstration scenarios, reference-site questions, architecture requirements and the issues that need deeper validation before selection.
Outcome: A defensible evaluation process built around how the organisation will operate, not how well a vendor presents.
Assess the platforms that are realistic for the organisation's scale, market, clinical model, digital maturity and budget.
Experience spans enterprise environments including Oracle Health, alongside open-source and mid-market options relevant to organisations where the largest global platform is neither necessary nor economically sensible.
The right answer is not automatically the biggest platform.
Technology selection and commercial negotiation should not be separate conversations.
Implementation scope, interface assumptions, environments, third-party dependencies, upgrade models, data access, resource requirements and change requests all affect the real economics of the decision.
I help challenge what sits behind the commercial proposal and where the organisation needs greater certainty before signing.
Legal interpretation remains with your counsel. The technology and operating implications are where I sit.
Selection is not the finish line.
Before implementation begins, I assess whether the organisation has the governance, clinical ownership, informatics capability, integration capacity, decision rights and internal programme structure needed to succeed.
A good platform implemented into an organisation that is not ready for it is still a bad outcome.
For greenfield hospitals, health systems and markets establishing core digital capability.
The focus is foundational: selecting an architecture that fits the clinical model today without creating unnecessary constraints tomorrow, building internal capability early, and avoiding long-term dependency on whichever vendor happens to arrive first.
For organisations carrying years of workflows, interfaces, data, workarounds and institutional memory.
The question is not only what the new platform can do. It is what must be preserved, what should deliberately change, what technical debt should not be migrated, and whether the organisation has accurately understood the cost of transition.
Replacement is an operating-model change disguised as a technology programme.
I have no commercial relationship with an EMR vendor, implementation partner or technology reseller.
That boundary is deliberate.
I have spent 18 years operating healthcare technology environments and enough time on the buyer side of technology negotiations to know where vendor roadmaps are credible, where assumptions need to be challenged, what tends to become a change request later, and which decisions look small during procurement but become difficult to undo in production.
If the best decision is to keep and optimise the existing platform, that should remain an available answer.
An EMR decision touches far more than the clinical record.
My operating experience spans clinical workflows, Oracle Health, laboratory, pharmacy, radiology and PACS, revenue cycle, FHIR and HL7 integration, digital patient platforms, ERP and supply chain, cloud infrastructure and enterprise AI.
That matters during selection because a platform does not succeed on the strength of its feature list. It succeeds in the environment around it.
Forty-plus hospitals. Government, semi-government and private health systems. GCC, India and APAC.
The perspective is from the organisation that has to make all of it work after the selection team has gone home.
I can structure the selection, define requirements, challenge architecture, evaluate vendor responses, support commercial discussions and assess readiness.
I do not receive implementation commission and I do not need a particular platform to win.
Once selected, your internal programme team and implementation partner own the build. I can remain on the hospital side to provide independent governance and challenge through implementation where that is useful.
The distinction keeps the advice where it should be: aligned to the organisation making the decision.
Whether you are replacing a legacy EMR, selecting a first HMIS, planning a greenfield hospital or questioning whether a platform change is necessary at all, the useful conversation usually starts before the RFP.
Thank you. Your message has been sent.
You will hear back directly, usually within a couple of days.
Prefer email? rajiv.ganapathy@nirvaanadvisory.com