Before You Buy Another EHR Module, Ask These 10 Questions

The practice is struggling with a workflow: scheduling takes too long, prior authorizations pile up, referral follow-up is inconsistent, and staff document the same information in multiple places.

The immediate response is often that the practice needs another module.

Maybe. But healthcare organizations accumulate technology faster than they optimize it, and more technology does not automatically produce a better workflow. Sometimes the system genuinely lacks a capability. Just as often, the problem lives somewhere else and only looks like a technology failure from a distance:

• Technology problem. The system genuinely lacks the capability.
• Configuration problem. The capability exists but is not set up appropriately.
• Workflow problem. The technology works; the surrounding process does not.
• Training problem. Staff do not know how or when to use it.
• Adoption problem. Staff know how but do not use it consistently.
• Ownership problem. Nobody is accountable for maintaining the workflow.
• Measurement problem. It was implemented without defining success.

Before purchasing another solution, work through these ten questions.

1. What problem are we actually trying to solve?

Start with the operational problem, not the product. “Patients wait too long for appointments and staff spend hours manually coordinating schedules” is a problem you can investigate. “We need a scheduling module” is a purchase you have already decided on. A referral-management challenge may look like it requires a new platform when the actual issue is that referrals arrive through multiple channels, ownership is unclear, and there is no standard follow-up process.

• Common mistake: starting with a product instead of defining the problem.
• Ask: What specifically is not working, who is affected, how often does it happen, and what would improvement look like?

2. Is the problem really caused by the EHR?

EHR frustration can make almost every operational problem look like an EHR problem, but sometimes the system is functioning as designed. Prior authorizations may be slow because staff enter information into several systems. Scheduling may be difficult because providers follow inconsistent rules. Changing technology without addressing the underlying process just moves the problem.

• Common mistake: assuming a purchase will fix a poorly designed process.
• Ask: If the technology were removed from the equation, would the underlying process still be inefficient?

3. Does our current EHR already have this functionality?

EHRs often contain capabilities organizations are not using or use only partially, and across platforms like eClinicalWorks, athenahealth, Office Ally, and Elation Health, what is available depends on configuration, permissions, and implementation choices. A practice can buy a separate tool for something its existing system already does. Third-party tools have their place, but only after you understand the actual gap.

• Common mistake: buying functionality that already exists but was never discovered or operationalized.
• Ask: What can our current system already do, and what specifically can it not do?

4. Have we configured it correctly?

Having a feature is not the same as having a usable workflow, and poor configuration can make a capable system feel incapable. If staff are drowning in alerts, the fix is usually redesigned alert rules and a decision about which notifications require action, not another communication platform.

• Common mistake: treating configuration as a one-time implementation task.
• Ask: Has someone with both operational and system knowledge reviewed the configuration against the desired workflow?

5. Have staff been adequately trained?

Training has to go beyond showing people where to click. Staff need to know when the workflow applies, who owns each step, what information is required, and what to do when something goes wrong. A referral workflow can be technically implemented and still fail because front office, clinical staff, and providers hold different assumptions about ownership.

• Common mistake: equating a training session with successful implementation.
• Ask: Could everyone involved explain their role, the expected workflow, and the escalation process?

6. What percentage of users actually adopt it?

Implementation is not adoption. A practice can spend real money on a feature that only a small fraction of providers consistently use, which matters especially for AI tools, documentation technologies, and care management platforms. Track adoption by provider, location, and role. If adoption of current tools is low, another purchase just creates another underused application.

• Common mistake: declaring success because the technology was deployed.
• Ask: What percentage of intended users are using it consistently, as designed?

7. What happens to the workflow after implementation?

Every technology change creates downstream work. After a referral is submitted, where does the information go, who reviews it, who follows up, who closes the task, and what happens when the patient cannot be reached? Evaluate the entire workflow, not just the screen where the user meets the application.

• Common mistake: optimizing one step while creating problems downstream.
• Ask: Can the entire workflow be mapped end to end, including handoffs and exceptions?

8. Does the new solution create duplicate work?

If staff enter information into the EHR and then re-enter it into another platform, the organization has not eliminated work. It has redistributed it. The same applies to duplicate scheduling, documentation, and patient communication. Integrations help, but integrations require maintenance and ownership of their own.

• Common mistake: assuming that because two systems technically connect, the workflow is efficient.
• Ask: How many times will staff or providers have to enter, verify, reconcile, or document the same information?

9. How will we measure ROI?

“Better efficiency” is not a metric. Depending on the workflow, improvement might mean referral turnaround, appointment wait times, staff minutes per transaction, prior authorization turnaround, documentation completion, denial rates, or revenue captured. If a solution costs $50,000 a year and nobody can explain the measurable improvement it is expected to produce, the organization is not managing an investment. It is managing a subscription.

• Common mistake: measuring implementation instead of outcomes.
• Ask: What is the baseline, what is the target, and when will we decide whether the investment worked?

10. Who owns the workflow after implementation?

Someone has to be accountable for monitoring performance, updating SOPs, coordinating training, and escalating problems long after go-live. Without an owner, workflows decay quietly. New employees get trained differently, workarounds appear, reports stop being read, and the original process becomes tribal knowledge. Eventually the organization concludes the technology stopped working, when nothing about the technology changed.

• Common mistake: assigning ownership to an implementation team and assuming the job ends at go-live.
• Ask: Who is accountable for this workflow six months after implementation, and a year after that?

From accumulation to optimization

Before adding another module, AI solution, or integration, step back and look at the environment as a whole: what each application actually solves, who uses it, how well it is adopted, where functionality overlaps, and where technology is creating work instead of removing it. Then ask whether fewer applications could accomplish the same or more. A structured application rationalization review sorts the stack into what should be retained, optimized, consolidated, or retired, with decisions grounded in clinical operations and measurable value.

Sometimes the next technology investment is not another application. It is getting more value from the technology already in place.

Where I help

The pattern in this article is one I see in practice after practice: a real workflow problem, a purchased solution, then another one, until the practice is paying for more applications than anyone can list while staff still move information between systems by hand. By the time someone calls, nobody is sure which tools overlap, which are actually adopted, or what the last purchase was supposed to improve.

Today I work in partnership with HealthTECH Resources to help ambulatory practices and FQHCs step back before the next purchase. That might mean an application rationalization review, a configuration review of the current EHR, a workflow audit, or hands-on optimization of the tools your team already owns, across eClinicalWorks, athenahealth, and other ambulatory platforms.

HealthTECH can also connect organizations with experienced ambulatory EHR consultants for implementation, optimization, integration, reporting, and training.

But the work usually starts in the same place: finding out what your current system can already do, and what specifically it can’t.

Ready to Review Your Stack Before the Next Purchase?

If your team is paying for applications that overlap, entering the same information into two systems, or weighing a purchase nobody has scoped against the current EHR, that’s a useful place to begin.

1. I want to talk to Nicole before we buy. Email Nicole directly at nguevara@healthtech-resources.com with a brief description of your practice, your platforms, and the purchase you’re considering. No cost for an initial call.
2. I need an EHR consultant for a project. Send HealthTECH the job description, timeline, and platform details. We’ll have qualified candidates in your inbox within 48 to 72 hours. No contract required to see profiles.
3. I’m not sure what I need yet. Schedule a no-cost conversation with Nicole or another EHR SME on our team. Whether you’re weighing a new module, wondering what your EHR already includes, or trying to define ROI for the tools you have, we’re happy to talk, no obligation.

Connect on LinkedIn | Email Nicole | Contact HealthTECH