About
Last year we found a problem nobody was solving.
Tony Ferullo and Alex Burgos were the first two engineers at Diameter Health, building clinical data infrastructure for the country's largest payers over the better part of a decade. After Availity acquired the company, they started asking a question nobody in provider operations was focused on: what actually happens after you submit a roster update to a payer?
What we kept hearing
Every credentialing team described the same experience: submit the file, then wait. No confirmation. No tracking. No proof.
Our story
What we found
No two payers work the same way.
Every payer has their own roster template, their own field rules, their own submission channel. Your team reformats the same provider data for each one. Once it's sent, there's no shared record and usually no confirmation. Visibility disappears at the point of submission.
What we're building
One process. Every payer. Full visibility.
Rota formats your roster to each payer's specs, delivers through their required channel, and tracks confirmation through every available signal. Your team submits once and sees exactly where every update stands.
The Team
A decade of healthcare data infrastructure, pointed at a new problem.
We built clinical data systems at enterprise scale. The roster problem turned out to be the same kind of challenge underneath: messy data, no standards, dozens of formats. Exactly what we've been solving.
Tony Ferullo
CEO
First engineer at Diameter Health. Built and led the clinical data platform through enterprise scale and Availity's acquisition. Now pointed at the hardest data problem on the provider side.
Alex Burgos
Founding Engineer
Second engineer at Diameter Health. A decade building the payer data systems that sit on the other end of every roster submission.
Next step
See how this maps to your workflow.
The first conversation is practical. Which payers cause the most pain, where the trail disappears after submission, and what it costs you.