A good Epic consultant researches a problem, asks useful questions, and raises blockers before they become bigger problems. Those are important habits.

The consultants who stand out also ask why a request keeps coming back. What is producing the issue? What happens to other teams if we make the requested change? Are we fixing the underlying problem, or making another adjustment around it?

One medication billing issue made that distinction especially clear to me.

The same kind of request kept returning

We were receiving frequent requests for medication billing overrides. Taken individually, each request could look like another medication record that needed attention.

But the pattern deserved a closer look. In the records we were examining, the medication's procedure-code field was blank, yet the output charge still had a code populated. Looking only at the medication record did not explain what we were seeing.

That discrepancy changed the investigation. Instead of treating every request as an isolated record issue, we needed to understand where the charge information was coming from.

Following it through led us to the charge router. A rule intended for one hospital was not restricted to that location, so it was also applying at another hospital.

The fix belonged at the rule, not on each record

I worked on the investigation and correction with Professional Billing, Hospital Billing, and the operational billing team. This was a joint effort, not something I could resolve well by looking only at my own part of the system.

The correction was to restrict the rule to the intended location rather than continue adding medication-by-medication overrides.

Afterward, the requests basically stopped. That is the qualitative result I remember from the work; I do not have a measured reduction or financial figure to attach to it.

What made the difference was changing the question. The individual requests pointed us toward medication records. Investigating why the same type of request kept appearing led us to a broader rule affecting more than its intended hospital.

What I look for in a strong consultant

Independent research matters. So does knowing when your investigation needs somebody else's expertise.

In this case, understanding the issue required people who could connect the medication side with billing configuration and operational billing needs. A consultant who treats the ticket as the full definition of the problem can miss those connections.

That does not mean every ticket needs an elaborate investigation. It means repeated symptoms, unexplained output, and requests for the same workaround are worth noticing. They are reasons to ask whether the problem has been defined narrowly enough to process, but too narrowly to solve.

A practical checklist for recurring issues

Here is a general approach I would use when the same kind of request keeps arriving:

  • Describe the pattern. What is repeating, where does it occur, and what do the requests have in common? Avoid assuming separate tickets necessarily represent separate causes.
  • Compare the request with the observed behavior. What does the requester want changed, and what evidence explains the current result? A mismatch is a useful lead, not something to skip past.
  • Trace beyond the first record. Within your authorized access and responsibilities, identify other rules or workflows that could influence the outcome. Bring in the appropriate owner when the investigation crosses your area.
  • Check the intended scope. Is a shared rule applying only where it should? Location was the key in this case; in another case, a different boundary may matter.
  • Involve the teams affected. Ask both technical and operational colleagues to help establish what should happen. Do not infer the right billing outcome from a technical field alone.
  • Agree on the correction and validation. Use the organization's change process. Plan checks for the intended workflow and any other locations or teams that could be affected, rather than assuming a narrower rule is automatically safe.
  • Watch for recurrence. After an approved change, look for whether the same requests return. Describe the outcome honestly, including when you have a qualitative observation rather than a measured result.

The value of asking one more question

Closing a ticket is useful. Finding the reason a whole category of tickets keeps appearing can be more useful still.

That takes curiosity, independent investigation, and a willingness to work across team boundaries. It also takes restraint: the goal is to understand the problem and make an appropriate correction, not to turn every request into an excuse for a bigger change.

If your team needs Epic consulting support, talk with BridgeLine Health about the problems you need someone to work through, the teams involved, and the experience that would help them contribute.