Heather Pnakovich, MSN, RN
Clinical Informaticist
Oracle Health & Epic
View BioThe Moment
When a health system absorbs a newly acquired organization onto Epic, the technology is rarely the hardest part. The hardest part is the moment critical clinical data won’t come out of the legacy system on schedule. On one recent Cerner-to-Epic conversion, that moment hit on day one: the radiology and lab data we needed wasn’t available, on a timeline that had no room to absorb the delay. I brought the interface analysts, application owners, and executive stakeholders into one room, we redesigned the sequencing around the highest clinical risk first, and that decision protected both the go-live timeline and the data clinicians would need to safely treat patients.
“Healthcare IT succeeds when people trust it.” “Tell me what you want. Let me advise you how to do it.”
This partnership went beyond a vendor playbook
following the hand off at the end of the project
The work
I joined this engagement as conversion and integration project manager after the project was already in flight. I was responsible for managing the conversion strategy and interface team for a large health system integrating a newly acquired organization onto Epic from Oracle Health Cerner. This project was running in the middle of a merger and an aggressive go-live timeline, so the stakes were extremely high. My role was to own the interface deployment plans, governance process, and implementation milestones, coordinating Epic counterparts, third-party vendors, interface analysts, and the incoming organization’s team. This allowed the client’s own technology manager and director to stay focused on the broader program. As a consultant, I wasn’t yet part of their core team, so the first job I needed to accomplish was earning their trust fast.
When the radiology and lab data delay put the timeline at risk, realigning the team around the highest-risk data first protected both the go-live date and the clinical information patients and clinicians needed on day one. Beyond that single engagement, it gave the client something more durable than a one-time fix. I provided them with a repeatable conversion methodology and standardized integration governance, with clear performance metrics defined around the value and usability of the data being converted. This partnership went beyond a vendor playbook handed off at the conclusion of a project.
This isn’t just the impacts to IT, but to every clinical and operational stakeholder the change touches.
Identify the informal influencers before you try to drive alignment.
I take the approach of thinking through three avenues: good, workable and fallback. This is to help the client make a decision instead of just reacting to a problem.
Platform knowledge is great, but in this partnership role, we must know what the technology actually means for the people using it.
what it takes
Being effective in this role means more than platform certification.