RevProof

Security and compliance

The product rules below are not preferences. They are how the software is built, and they are what an auditor will ask about.

The model never picks a code
The extraction schema has no field for a code or a level. A deterministic engine applies published rules and names each one it applied.
Code to documentation only
A prompt for a missing sentence appears only when the note shows the work was done. The software never suggests ordering a test or adding work to raise a level.
A person approves every change
Nothing is submitted automatically. Every suggestion keeps its quoted evidence, who approved it, and when.
Levels rise gradually
Each provider has a ramp target: a quarter of the gap per month. The software never recommends flipping a distribution.
Flat pricing
A flat fee per provider per month. A percentage of recovered revenue would pay the vendor to code higher, which is exactly the incentive auditors look for.
Sealed records hold hashes, not notes
Sealed by Authyr. The seal layer stores fingerprints and identifiers. Note text never leaves the practice's database for the seal or the public verify page.
Protected health information
Real patient data is handled only under a signed business associate agreement with every vendor in the path: database, model provider and hosting. Demonstrations run on synthetic data.
Tenant isolation
Every table is scoped to a practice with row-level security enforced by the database. A user of one practice cannot read another, and that isolation is tested in continuous integration.