How we handle your practice's data.

A signed Business Associate Agreement comes first.

HIPAA requires a BAA between a covered entity (your practice) and any business associate that handles protected health information on its behalf. We sign one before a single file moves, including before the free denial snapshot. It binds us to the same safeguards you are held to, and it gives you a written, enforceable record of exactly what we may and may not do.

Encryption in transit and at rest.

Files travel over TLS from your browser and land in encrypted storage. Nothing sits in an inbox, a shared drive, or a personal device. Internal access happens over authenticated, logged sessions.

The upload page: no EMR access, no software, no logins.

We do not connect to your practice management system or your EMR, and we do not ask for credentials to anything. Instead you get a private, encrypted upload page: a link, not an application. Your team drags the denial report onto it, and it goes straight from the browser into encrypted storage.

That's on purpose. An integration would give us far more access than this work requires, and it would put your IT staff on the hook for us. An upload page gives us only what we actually need.

Minimum-necessary access, scoped to flagged claims.

We start with the denial report you already run: claim numbers, dates of service, payers, denial codes, amounts. We request supporting clinical documentation only for the specific claims we intend to appeal, and only the portion that supports the appeal. We never ask for a full chart export, and we never ask for records on patients whose claims we are not working.

A complete audit trail of every claim we touch.

Every claim we open, every document we request, every appeal we build and file is logged with a timestamp. If you ever need to reconstruct what happened to a specific claim, whether for a payer, an auditor, or yourself, the record exists and it is yours.

A person reviews every packet before it leaves.

We use AI to read denials and draft appeals, which is the only reason claims this small are economical to work at all. It is not the last step. A human reviews every outbound packet against the chart and the payer's own published policy before anything is filed under your practice's name.

Your clinician signs anything clinical, as one short weekly batch.

No appeal that makes a clinical argument is filed without your clinician's approval. Those approvals arrive as a single weekly sheet listing each claim, the argument being made, and the chart basis for it, reviewed and approved in one sitting, at whatever time your clinician chooses. Clinicians are never asked to sign off one claim at a time.

Most appeals are administrative (coding, bundling, authorization technicalities) and need no clinical sign-off at all.

We never touch your money.

Payers pay the practice directly, into the same account they pay into today. Revalis has no lockbox, no trust account, and no ability to receive funds on your behalf. We invoice our share after a payer has paid you, never before, and never out of the payment itself.

US-based infrastructure, under a signed BAA.

Practice data is stored and processed on US-based cloud infrastructure, under a signed BAA with our cloud provider. Our subcontractor obligations flow down: anyone who could touch your data is bound by the same terms we are bound by, and we will name them on request.

Your data is never used to train AI models.

Not ours, and not a third party's. Your practice's data is used to work your practice's claims. That is the entire permitted purpose, and it is written into the BAA. We don't aggregate it, resell it, or use it to build anything that serves another practice.

Return or destruction when the relationship ends.

When you cancel, we return or destroy the protected health information we hold, per the BAA, and confirm in writing which one we did. No clause in our agreement lets us keep working your claims, or keep your data, after you cancel.