Three tiers, one engine. Begin on de-identified data with no BAA and no clearinghouse enrollment — then unlock PHI look-ups and full revenue-cycle automation as you're ready. Upgrading adds capability; it never means re-implementing.
Prevention with no compliance friction. The deterministic scrubber, Code Review, note audit, denial-pattern learning, and — as the network grows — wider payer patterns as advisory alerts, all on de-identified code content. The fastest way to start.
Everything in Scrub, plus live patient look-ups: eligibility and benefits, coordination of benefits, prior-authorization checks with an authorization register, claim status, and Good Faith Estimates. Denial work and rebilling stay in your EHR or PM system; Provira advises and drafts.
Everything in Verify, plus the whole downstream: claim submission, ERA retrieval and auto-matching, the full claim-tracking lifecycle, underpayment detection against your contracted rates, and appeals drafted and rebilled inside Provira.
Setup: Scrub needs nothing — no BAA, no enrollment. Verify needs a signed BAA. Complete needs a BAA plus clearinghouse enrollment, which is where the setup time goes.
Compare
| Scrub | Verify | Complete | |
|---|---|---|---|
| National CMS rules — scrubber, Code Review, note audit (act immediately, no promotion) | ✓ | ✓ | ✓ |
| Denial-pattern learning + certified-coder promotion | ✓ | ✓ | ✓ |
| Wider payer intelligence (as the network grows; requires your coder's approval) | ✓ | ✓ | ✓ |
| Eligibility, COB, prior auth, claim status, Good Faith Estimate | — | ✓ | ✓ |
| Denial worklist and appeals | codes only | advisory · drafted | full · in-app |
| Where the correction and rebill happen | your system | your EHR / PM | in Provira |
| Claim submission, ERA auto-match, lifecycle, underpayments | — | — | ✓ |
| What it takes to start | nothing | a signed BAA | BAA + payer enrollment |
✓ included · — not in this tier. Want the full line-by-line matrix? We'll walk it in the demo.
Why the tiers work this way
Tier limits are enforced server-side. A PHI feature will not run without a signed BAA on file. That's also why Scrub is genuinely low-friction: it runs on code content only, so there's no BAA to negotiate and nothing to enroll before you see value.
Land and expand: start at Scrub, prove the wedge on your own denial data, then add the BAA for Verify and the clearinghouse for Complete. The engine and every rule it has learned carry forward.
Pricing
We aren't publishing prices, and we'd rather tell you why than show you a number that turns out to be wrong for your practice. Provira is priced against what it actually prevents and recovers for you — and until we've run your own data, neither of us knows what that is. A pilot answers it in weeks.
What you can expect:
Twenty minutes, and we'll tell you what a pilot would cost and exactly what it would measure.
We usually recommend starting at Scrub. Twenty minutes on a call and we'll tell you honestly which one is right for your size and your payer mix.
