Two companies that already knew this problem.
PROMETHEUS did not start as a product idea. It started as the same finding, arrived at twice — once from the revenue side, once from the encounter data itself.
Why this exists
PACE organizations run one of the most demanding models in American healthcare: full clinical and financial responsibility for a frail, nursing-home-eligible population, paid through a capitation that depends on documented, submitted and accepted diagnoses.
The category is small — roughly 200 programs and about 91,000 participants nationally, per the National PACE Association in 2026. Small enough that the analytics tools available to PACE were largely designed for Medicare Advantage and pointed at PACE afterwards. That matters more than it sounds: for CY2026, CMS scores PACE organizations on a blend of two risk models while Medicare Advantage runs fully on the newer one, and PACE carries a frailty adjustment MA does not. A tool that does not know that is not conservative — it is simply wrong, quietly, every month.
Meanwhile the encounter data telling CMS what happened travels through EDI infrastructure that most programs never see inside. Rejections, non-acknowledgements and silent drops happen there, and the revenue attached to them disappears without an alarm.
PROMETHEUS was built where those two facts meet: a risk-adjustment product that is calibrated to how PACE is actually paid, running on the same encounter rails the data already travels.
Who builds it
Renovatio Intl, Inc
Healthcare data and revenue-integrity work for government-program health plans. Renovatio brings the PACE risk-adjustment domain model, the reporting and analytics engineering, and the product itself.
Todd Singh — co-founder, product and platform.
VisibilEDI
EDI and encounter data management for government-program health plans — a gateway and clearinghouse operation whose stated purpose is turning EDI's black box into glass. VisibilEDI brings the encounter substrate PROMETHEUS reads, and decades of operating it.
Dean Hill — co-founder, encounter data and operations.
PROMETHEUS is developed by Prometheus LLC, a Wyoming company jointly held by the partners. It is a standalone product with its own roadmap, its own security posture and its own agreements — not a feature of somebody else's platform.
Four commitments we will be held to
Show the arithmetic
Every dollar figure in the product opens to the calculation behind it. If we cannot show you how a number was produced, we should not be showing you the number.
Generate, never submit
The software prepares and evidences; a person decides. We will not build a feature that files something to CMS on your behalf without an explicit human action.
Say what isn't built yet
Our security page names what is designed versus implemented. You should never learn the difference from a questionnaire response.
Small category, long memory
There are about 200 PACE programs. We intend to be in this category for a long time, which is a strong incentive to be straight with every one of them.
Current status
The application is complete enough to drive end to end and is demonstrated on a synthetic PACE dataset. The compliance layer that clears it for real participant data is specified in full and phased against a published roadmap, with a technical gate preventing live data before those controls are verified.
If you are a PACE program willing to be early, that is a conversation we want to have directly — including about what we would owe you for being first.
Talk to the people who built it.
No SDR queue, no discovery-call gauntlet. The founders take these meetings.