Most billing software uploads your clients' data to someone else's cloud. Med Claims Pro is built the other way: claim data stays in a local database on your computer, and our servers handle exactly three things — your account, your subscription, and your license.
Clients, claims, activities, notes, generated documents, payment records, reports — the entire billing database, stored locally, backed up automatically on every launch (last 14 copies kept).
Your email, subscription state, which computers are activated, and license events. That's the complete list. No claimant names, no claim numbers, no documents, no note text — ever.
Card details go directly to Stripe's PCI-certified systems via their hosted checkout — they never touch our servers either. Invoices and card management run on Stripe's hosted portal.
The app verifies a cryptographically signed license on your machine and renews it quietly when online. License checks carry your account and device identifiers and a version number — never billing content.
If your subscription lapses, the app becomes read-only: you can view and export everything, indefinitely. Your records are your records.
Generated documents land in your own Documents folders. If those folders sync to OneDrive under your Microsoft account, that's your storage under your control — the same as your workflow today, minus the retyping.
Diagnostics are off by default. If you opt in, reports carry the error type, app version, and OS — no file paths, no note text, no claim data.
All connections use TLS. Our servers run a minimal, firewalled stack with encrypted backups, key-only access, and continuous security patching.
You remain responsible for your own compliance posture (device encryption like BitLocker, screen locks, staff access). We provide the architecture that makes it tractable — and a BAA for support scenarios where you'd share data with us.
The honest answer: "HIPAA compliant software" isn't a certification that exists. What matters is that our architecture keeps claim data off our servers entirely — for the core product we never have access to it, which keeps us outside business-associate scope. Many workers'-comp-only practices aren't HIPAA covered entities at all, but we designed for the strict case anyway.
For the core product there's nothing to sign a BAA about — we never hold your PHI. For support scenarios where you choose to share files with us, we provide a countersignable BAA first.
Nothing. The database, the documents, and the app are on your computer; the app degrades to read-only at worst. Your data never depended on our servers existing.
The app keeps 14 rotating local backups automatically, and your generated documents live in your own (often OneDrive-synced) folders. For full disaster recovery, an optional encrypted off-site backup add-on is in development: your database backed up encrypted with keys only you hold, restorable to a new machine in minutes — opt-in, and priced as a small monthly add-on.
No. There is no sync, no upload, no remote access. Support is done with synthetic data and screenshots you choose to share.