Built for records that aren't yours to lose.

Patient records only under a signed business associate agreement.

• ClaimDoc handles protected health information for a clinic only under a business associate agreement with that clinic.
• Every provider that stores or processes patient records for ClaimDoc does so under its own business associate agreement with ClaimDoc. They're listed on the subprocessors page.

No clinic ever sees another clinic's cases.

• Every case, record and figure belongs to one clinic. The separation is built into the foundation, so a mistake on a screen can't open one clinic's data to another.
• Roles decide what each person can do. Owners and admins run the account, billers work cases, viewers only read. Anyone can be limited to the clinics they actually serve.
• Billing teams get one sign-in for every clinic they serve, and each clinic's cases, records and totals still stay apart.

Files stay private, and access never lingers.

• Uploaded records, finished packets and signatures are stored privately and encrypted. A file opens only for a signed-in person with rights to that clinic, and access closes again on its own.
• Patient details stay out of web addresses, logs, analytics and email. Downloads carry neutral file names.
• Two-step sign-in is available to every user, and an unattended session signs itself out.

Everything that happens to a case is on the record.

• Every view, export, change and applied signature is written to a ledger your owners and admins can read.
• Entries can't be edited or deleted from the product, by anyone.

Nothing unproven leaves.

• Source Trace ties every statement in the argument to a page of your records or a passage of published policy. A statement without a source isn't written.
• Before a packet exists, an independent check re-reads each statement against its source and re-checks every number and date. A statement that can't be proven doesn't go out.
• If a record or a claim detail changes afterward, the case is rebuilt and checked again before anything can be sent.
• When the record is missing something the payer requires, ClaimDoc stops and names it. It never writes around a gap.

A document can't talk ClaimDoc into anything.

• Uploaded pages are read as evidence only. Text planted inside a record to steer the result is flagged and ignored, and the letter can't rely on it.
• Payer rules come from the Policy Index, a maintained library that keeps each rule with its published source and date.
• Looking up the rules never involves the patient. Only the payer, the plan and the billing codes are used to find them.

Set up once, used only where a form asks for it.

• The clinic's signature is stored privately and applied only to that clinic's appeal letters and the payer forms that require one.
• Every use is written to the Ledger. An owner or admin can replace the signature or withdraw the authorization at any time.

Compliance officers and security teams can have ClaimDoc's security packet: how data moves, who processes it, and the policies behind it. Write to hello@claimdoc.co. The list of subprocessors is on the subprocessors page.