All Spotlights

Spotlight

Kerry Huntzberry

Client Site Leader, Continuous Services · Epic

Specialization Strategies of running a successful Epic Team · Clinical · Access & Interoperability · Database & Technical Layers
Experience 5+ years Healthcare IT, 3 years at Epic
Continuous Managed Services

The Moment

What I do when it matters most

Roughly three months after an Epic go-live is when you start to see the bigger issues in the system. End users are more aware of how to use it, so they start to do things their way, outside the norm. If the post-install processes aren’t set up yet, the backlog builds fast.

I came into a health system that had just gone live on Epic Enterprise after roughly 13 years on Epic. They were close to 3,000 tickets across their queues, a lot of the experienced install team was gone, and the environment was escalation-heavy. I knew everyone was firefighting issues, working as fast as possible to reduce that count and keep up within intake volume. My job was to confidently raise my hand to say hold on, we need to pause for a second, reset ourselves, and reprioritize.

An Epic go-live is hundreds of millions of dollars of investment. Once you get there, a lot of people are on edge anticipating what’s going to happen, and it is easy to get stuck in that culture of chaos. You need strong leadership to set the tone and the pace, and to say we need to think about this differently. This approach is critical so that you don’t burn out staff or operations.

“Once you get to the point of everything's escalated, then nothing's escalated...AI is here, but we do need that human verification because at the end of the day we’re talking about patient lives and patient care.”

700+

Original backlog reduction target, met on time

~3,000 to <1,500

total open tickets across queues (from intake to today). The lowest the queue has ever been.

The work

A Recent Engagement

This client was not new to Epic, but they were new to Epic Enterprise. They had all their workflows organized and their processes sorted before Enterprise, but the change they experienced was significant. They’d accumulated a large backlog, likely because their post-install processes weren’t set up. They were still very much in a go-live mindset, and they’d lost a lot of the experienced install team. Most of the remaining team members were fairly new with Epic and weren’t getting the fast resolution time the organization expected.

The initial ask was to build a team to reduce a net number of tickets in the backlog. However, when we got engaged, we noticed that a lot of the processes weren’t set up, teams were working siloed and missing that collaboration piece, and they were band-aiding the system rather than looking at root cause resolution paths.

Through our partnership, the initial backlog reduction effort began turning into something much larger. We began helping the client asses their organization, staffing methodology, processes, and even their workflows and configuration of the system as a whole.

Revenue Cycle is where we’ve seen some of the strongest outcomes so far. Their revenue cycle operations team is strong and has been heavily involved in the workflows since go-live, but there were root issues causing downstream effects. The biggest thing we did was put somebody with project management leadership experience in as the point person to take charge and organize, not to PM it, but to own the workflow. Without this oversight, analysts were having to manage these issues on their own. That decision kept a consistent flow of communication and updates to the operations team and stopped us from troubleshooting on the fly, which in the long run built a lot of trust with the leadership team and with our analysts. That trust is crucial to a successful IT team on Epic, and honestly on any EHR.

The other major gap we identified was the need to prioritize governance. Our team wanted to make sure we weren’t just building something because someone requested it. We want the right revenue cycle or clinical leadership sign-off to confirm it’s the correct thing to do organization-wide. Sometimes that means reprioritizing a ticket, deciding we’re not doing it right now, or bundling it into a larger initiative the client already has underway.

That work we’ve done, the consultative partnership we’ve established, and the value add we’ve provided to their operations has opened the door to supporting this client long term. I’m coming in with the mindset that we’re starting an Epic IT shop from scratch. We look at every single process in place today to evaluate what’s working and what’s not. That is also being balanced with the reality of where the client is today. There is still a backlog and governance adoption still needs to be prioritized. Change is good, but it needs to be done slowly for it to be accepted, and we have to have the client’s buy-in.

  • Attitude over tenure.

    You can be brand new to Epic, and if you have a good attitude, that can be more important than somebody with 25 years who doesn't want to talk to anybody else on the team. Be willing to learn and willing to jump in.

  • Prioritize your team, specifically.

    Give analysts the opportunity to speak and tell you what's working and what's not. Give them the trust to run with an idea, opportunities to cross-train, and a path to elevate themselves if they want it.

  • Make it safe to talk to anyone.

    People need to feel comfortable asking any person in leadership a question, regardless of titles, and to know there's no question too dumb to ask.

  • Listen, don't react.

    Make sure you're really listening and not just hearing. Take a second to think about it. You don't have to have an answer right away. It should be clear the response was thought about, not a quick reaction.

  • Bring a recommendation, not a decree.

    Instead of "here's what the process is going to be," come at it with "this is what we feel the process should be, these are the best practices we've experienced. What doesn't work? What do you feel is missing?" Clients want it to feel like a partnership.

  • Give it a shot and adjust.

    Keep reiterating that not everything is going to work the first time, but we can make adjustments along the way. If something isn't working right now, we don't lose anything by changing it.

what it takes

Advice for Success

At the end of the day, analysts are key to the success of any team. They're the ones getting the work done. Here's what I've noticed matters across every organization I've worked in:

Ready to put an expert like this on your next project?

Start the Conversation

More Moment Makers

See all

Moises Frois

EHR Integration Program Manager

MEDITECH and Epic

View Bio

Heather Pnakovich, MSN, RN

Clinical Informaticist

Oracle Health & Epic

View Bio

Jackie Piekarz

Lab Leader

Oracle Health

View Bio

Kathy Strobbe

Enterprise Resource Planning (ERP) Practice Leader

Workday, UKG, Oracle Fusion

View Bio