Make RIS Adoption Stick in the First 60 Days
Imaging teams can make it through kickoff, configuration, testing, and training, then still lose momentum once real work begins. The first 45 to 60 days after go live often decide whether a new platform becomes part of the workflow or another layer people work around.
Jump to a chapter10 chapters
What You Will Learn in This Episode
In this episode of Keeping Up With AbbaDox, Ruben joins host Pierre-Antoine Tricen to share:
See how it comes together
Ruben Gonzalez walks through the full conversation.
The Challenge: Go Live Is Not the Same as Adoption
Imaging teams can make it through kickoff, configuration, testing, and training, then still lose momentum once real work begins. The first 45 to 60 days after go live often decide whether a new platform becomes part of the workflow or another layer people work around.
As Ruben Gonzalez explains, the problem is rarely just technical. Every center has its own habits, pressures, and definition of what “working” looks like. If implementation teams focus only on setup, they miss the human side of adoption: trust, fit, and follow through.
The Solution: Implementation Built Around Real Workflows
At AbbaDox, solutions delivery is not about forcing every center into the same process. It starts with understanding how the site already works, what pain points slow staff down, and where the platform can remove friction quickly.
Ruben brings nearly a decade of implementation experience at AbbaDox and more than two decades in imaging. His team uses discovery, configuration, testing, training, and on-site go lives to shape CareFlow around the center instead of asking the center to adapt blindly.
I try to make myself feel like as if I worked for them inside their center.
Manager, Solutions Delivery at AbbaDox.
“During the sales process we chase executive buy-in, but that’s not really where the adoption leads.”
Ruben is naming the gap that kills rollouts: the people who buy the software are not the people who have to live in it. So implementation runs on milestones that must be met before go-live is even called, worklists and communication flows are configured around how that center actually works, and the team keeps refining 40 to 60 days after launch, watching whether users are really using it as trained, not whether the project closed.
How AbbaDox Approaches Implementation with CareFlow
Select one below to explore how it comes together.
