RRemitGuard

SECURITY & PRIVACY

Payment review.
No medical charts required.

RemitGuard compares payer contracts with insurance payment statements to help your team understand potential payment differences. Start with fictional sample data, and know how your information is handled before using real records.

What information does RemitGuard use?

The supported payment-review workflow uses claim and payment identifiers, procedure codes and modifiers, service dates and units, payment amounts and adjustment details. RemitGuard does not require medical charts, clinical notes or diagnostic images.

Insurance payment statements may contain patient names, member identifiers and service information. This can be protected health information (PHI), even without a medical chart. The safeguards and permitted uses in your signed Business Associate Agreement (BAA) apply to those records.

Provide only what the review needs

Provide only the payer contracts and supported insurance payment records (EDI 835 files) needed for your review. Please leave out medical charts, clinical notes, diagnostic images and unrelated documents.

Less personal information leaves your device

For supported EDI 835 uploads through the browser, RemitGuard removes patient and subscriber names and identifiers from supported identity fields, along with supported personal reference, address and contact fields, before sending a prepared copy. The file receives a generated name. Unsupported file structures are blocked for review.

Claim and payment references, service dates, procedure codes, amounts and other information needed for comparison and payment matching remain. Supported banking and payment-routing fields also remain. Retained identifiers can still contain personal information. This reduces the information uploaded; it does not make the file anonymous or remove all PHI. Your BAA protections still apply.

Keep the original payer file securely for your records and any payer submission. This preparation does not redact contract PDFs, information you type, or previously stored records. Upload only records your practice is authorized to share.

Start with fictional sample data

Demos use fictional sample data we provide. You do not need to upload practice records to explore the software.

Contact us to discuss a guided pilot before uploading real practice records.

Before using real practice records

Both parties must sign the BAA and Services Agreement, and your practice workspace must be available through onboarding, before you upload real records containing patient information. Creating an account alone does not complete these steps.

Access belongs to your team

RemitGuard uses individual accounts, two-step verification and practice-scoped permissions. Administrators manage team access. Keep passwords and authenticator codes private.

You review and approve the results

AI-assisted contract interpretations cite their source so your team can check them. Authorized reviewers approve supported schedules before they are used in comparisons. A potential payment difference is a finding to investigate, not a determination of money owed. RemitGuard does not automatically submit appeals.

How your agreements protect your information

The BAA and Services Agreement set out the permitted uses and protections for your practice's information. The BAA limits use to the agreed services and does not authorize advertising, sale of patient information or general-purpose model training. Your signed copies record the commitments applicable to your practice.

Contact us for details about service providers, safeguards, retention and permitted processing before onboarding.

Your agreement copies

Your practice can review its agreements during onboarding. Accepted copies with your practice details and electronic signatures are saved to your account. Completed onboarding also provides an application guide.

Questions and support

Contact info@remitguardhealth.com for account and security questions. If you need to share sensitive records or incident details, ask us for an approved protected channel first. Please do not send patient records or passwords by ordinary email.

Request a demo or discuss a pilot