RSNA 2026 · Booth 6327Most AI at RSNA reads images. Ours handles the faxes, calls and follow-ups.RSNA is two weeks out. Book your time at booth 6327 before your week fills up.Book booth 6327 before Thanksgiving. Nov. 29 – Dec. 2, North Hall, Level 3.RSNA opens Sunday. See Ora at booth 6327, North Hall, Level 3.Today at 11:30 a.m. CT: AbbaDox at the RSNA AI Theater, South Hall A. Then see it run at booth 6327.We’re at booth 6327 now, North Hall, Level 3. Walk-ups welcome.Missed us at RSNA? See the booth walkthrough on a call.CareFlow customer? See Ora, new features, portals or CRM at booth 6327.Your RSNA meeting isn’t booked yet. Your time may still be open.You’re on the list for booth 6327. Bringing a colleague?
What’s at the boothWhy a working system shows you only its mistakes, and what that does to a team that was never told to expect it.
For operations and imaging leaders, front-line managers, and teams preparing for a go-live.

Nick on what he hears after go-live: the queue holds only errors, so it “just keeps messing up.”
In radiology operations, AI often enters the conversation carrying baggage it did not create. Teams worry about job loss, black-box decisions, bad data, fragmentation, and failure rates before they have a clear baseline for the work already happening today. That makes adoption harder, even when the current process is overloaded, inconsistent, or already creating avoidable errors.
Nick Avossa has seen that pattern up close. As VP of AI Operations at AbbaDox, he works with leaders and front-line teams trying to modernize workflows while carrying years of habits, workarounds, and skepticism into the conversation. His point is not that fear is irrational. It is that fear alone is a poor benchmark for deciding what should change.
As Nick puts it, a system doing its job is the one you stop noticing, and that is exactly what makes it hard to trust.
In this episode of Keeping Up With AbbaDox, VP of AI Operations Nick Avossa argues that operational AI works best when it is grounded in context, transparency, and comparison. Teams need to know what the current process costs in time, throughput, and accuracy before they decide what good enough looks like.
They also need to understand where AI fits, where it does not, and when human review should stay in the loop. Real adoption happens when leaders show the data, prepare staff for what will change, and focus AI on the parts of the workflow where speed, consistency, and scale matter most.
if it's doing its job, it is invisible, and all you surface are the errors.
Runs AI operations at AbbaDox, working with centers on the floor rather than from a slide.
“If you do not prepare your staff for the idea that the things on their list are only errors now, they will give you the perception that it does not work.”
Nick's argument is that the tool is rarely the hard part. What decides adoption is a measured baseline to compare against, and staff who were told in advance that their queue would fill with exceptions only, so a system that is working does not arrive looking like a system that is broken.
Six things that decide whether it sticks. Select one to explore it.






Three questions for your next leadership meeting, each with the moment in the episode that answers it.
Measure accuracy and throughput now, then hold AI to the same benchmark you hold your staff to.
Once AI clears the routine work, the list holds only errors. Staff who are not told that will decide it does not work.
Keep a person on those, and give AI the routine work, where its errors are more consistent and easier to fix.
Want these answered for your center?
Watch the full talk, or bring your own numbers to the team that would be measuring against them.