Redox was home for more than seven years. Then I left. And now, a few weeks back in (or 394, depending on how you count it), I’m more energized than ever about what we can all collectively accomplish in the messy world of healthcare data interoperability.
I worked with some great organizations and spent just enough time on the golf course to confirm that my over-the-top swing is a permanent feature, not a bug. The time away was valuable. When the opportunity to return presented itself, the decision kept coming back to one question: Why would I go back?
It’s a fair question, and I sat with it for a while. The answer came down to three things that hadn’t changed, and one big thing that had.
What hasn’t changed: the people, culture, and vision
What hasn’t changed at Redox is the thing that’s hardest to replicate. It’s a company full of people who genuinely want to build something great and make a real dent in healthcare. That’s not a line. You feel it in how people work, how they handle hard problems, and how they treat customers. This team LIVES to help customers solve their thorniest interop challenges, and guide those who are new to the journey. The people and culture is what made seven years fly by the first time, and it’s what made coming back an easy call.
The vision hasn’t wavered either. Redox has always been focused on the hardest, least glamorous parts of healthcare data connectivity — the infrastructure that keeps clinical and operational data moving reliably across a deeply fragmented and siloed ecosystem. That mission doesn’t get old. In fact, with all the AI capabilities and tools now available to us, I’d argue it has become even more critical.
This team has built something worth believing in. When I looked at where Redox was heading, it was clear this wasn’t a company coasting on its history. It was one building toward something bigger.
What has changed: the platform is far more powerful
When I left, Redox was best known for connecting healthtech startups to EHRs. That reputation was earned, and it was (and still is), incredibly valuable. But the platform has evolved into something much more comprehensive, and that’s the real reason coming back made sense.
Today, Redox is an interoperability partner powering healthcare data exchange at scale — not just for startups, but for health systems, health plans, and enterprise healthtech companies navigating incredibly complex data problems.
Here’s what that actually means in practice. (No, this isn’t a sales pitch. But if you want the sales pitch, please call me, I’m more than happy to oblige.) During the rebound interview process, the team shared examples of recent complex workflows we’ve implemented for big name healthcare companies that weren’t possible before:
- For a major US health system, in just 4 weeks, we went live with a gen AI enabled fax routing process that automated a dreary, but crucial, manual paperwork process. Millions of faxes needed to be processed and routed across 1,200 possible destinations. Instead of quadrupling the size of the team who manually did this work, Redox & AWS designed and implemented a solution that significantly reduced operational costs while processing critical patient documents in seconds instead of days.
- For one of the largest payviders in the US, along with our partner IMO Health, we improved CCD data quality by 70%. You read that right. 70% of CCDs from a HIE were missing codes. Missing codes have a real impact on revenue and patient care.
- Databricks, another partner, is the bleeding edge adopter of the Redox MCP server (currently in beta at the time of publication; general release expected soon). Organizations that use Redox to get data into Databricks (and other cloud platforms), have a powerful new tool to do all kinds of things, of which we are just scratching the surface.
We are talking billions of transactions for some of the largest companies in healthcare that make a real impact. The vision of what Redox could be that originally drew me in is actually happening, at scale. And THAT is exciting.
It is worth calling out that the example solutions above all fall under the umbrella of data orchestration, one of the hottest topics in tech right now, and for good reason. Getting the right data where it needs to go, in real-time, with acceptable quality/security/compliance/audit trails, is non-trivial. There is a huge opportunity for agentic technology to positively impact data orchestration and reduce the load on integration teams, as long as it is paired with experienced oversight and guidance.
Previous posts from my colleagues Rachel Witalec (Chief Product Officer, Redox) and Sasi Mukkamala (Chief Technology Officer, Redox) go deeper on the technical architecture and where the AI vision is headed — worth reading if you want the full picture.
But from a sales and customer perspective, the short version is: this is no longer a point solution. It’s infrastructure.
What I’m seeing in the market: this is the right moment to be back
Just a few weeks in, and I’ve already had enough conversations to feel the shape of where the market is heading. A few things stand out.
1. The legacy interface engine conversation is real and accelerating. Health systems, payers, and enterprise organizations are not going to rip out their infrastructure — they can’t. But interop is plural and AI is systematically dismantling all of the historical limitations. Companies are realizing there is a way to build a data infrastructure layer across external vendors, legacy internal data silos, and the modern AI tools that sets them up for success.
2. The conversation has officially shifted from ‘how do I move data’ to ‘how do I make data actionable.’ Simply connecting to EHRs is no longer enough. I’m hearing about data quality needs and orchestration requests that never came up in past conversations. Almost everyone is experimenting with AI or actively running AI in production. However, security and compliance are critical requirements for AI adoption. Enterprise organizations have been talking about “breaking down data silos” for decades. It feels like we might actually be on the precipice of making that happen.
3. Speed, flexibility, scale, and deep interop experience are requirements. Enterprise organizations are looking for partners to help lighten their load, or take it off their hands entirely. As my colleague Sasi Mukkamala, Redox Chief Technology Officer, recently wrote, beware the “time-to-wow” vibe coding trap and make sure your partners have the experience to meet real-world needs.
The through-line is the same: organizations are done patching brittle integrations together one at a time. They want a foundation that not only scales, but also holds up as requirements change, as AI use cases multiply, and as the regulatory environment keeps shifting.
The decision to come back was easier than I expected
I started this post with a question: why go back? The honest answer is that I never stopped believing in what Redox was trying to do. The mission, the people, and the culture were always worth coming back for.
What made the timing right was watching the company grow into something that can meet the market where it actually is right now…and where it is going next. Redox Engine (the tech platform) evolution is what made the opportunity to come back attractive. Pairing the advanced technology with the expertise and services/support that has always set Redox apart made it a no-brainer.
Health systems, enterprise healthtech companies, and payers are all facing the same underlying problem: their data infrastructure wasn’t built for what they’re being asked to do today. Redox is one of the few places that can help them get there — not just by moving data, but by making it usable.
That’s a problem worth solving. Since becoming an above-average amateur golfer isn’t in my future, I’m stoked to be back working on it.
This post was written by Andy Pung, SVP of Sales at Redox.