Security and privacy
How clinic data is handled.
Missing Revenue Finder handles a clinic's visit notes only under signed agreements. This page says what protects those notes today, who can reach them, what the AI model receives, and what is not done yet.
Before any note moves
The demo uses our charts. Your own charts start with signed agreements and a written go-ahead.
The fifteen-minute demo runs on example charts we wrote, so you share no patient data to see the software work.
No visit note of yours moves until our services agreement and a business associate agreement are signed and we have confirmed to you in writing that everything they require before patient information is in place. Template setup comes first, from sample or de-identified exports in your EHR's format, so no patient information is needed to set it up.
Notes reach us as PDF exports from your EHR. There is no EHR integration, nothing installed on your systems, and no standing connection into your records.
- Example charts in the demo, so nothing of yours is shared
- Agreements first, then our written confirmation, then notes, in that order
- PDF export only: no integration and no connection to your EHR
-
Your clinic
Exports and uploads
- A PDF export of the visit note
- Uploaded over an encrypted connection
- Only after the agreements are signed and go-live is confirmed in writing
-
Missing Revenue Finder
Reads and suggests
- Stored encrypted, in one US region
- Each clinic's data closed to every other clinic
- Nothing submitted on your behalf
-
Your reviewers
Decide every code
- Sign in with a password and a second factor
- See their own clinic's visits only
- Accept or dismiss; billing stays in your system
In transit and at rest
Encrypted on the way in, and encrypted where it sits.
Each line below describes a setting as we read it from our systems, not from a policy document. We can walk you through any of them. What we must keep in place once you sign is set in the agreements.
- Encrypted upload
Every connection to the application uses TLS 1.2 or newer. A plain HTTP request is redirected to HTTPS.
- Encrypted at rest
Stored chart files and the database are encrypted at rest with AES-256.
- No public access
The database has no public address and accepts connections only from inside our private network. The chart store blocks every form of public access; reaching it takes our cloud account's credentials. Our own services that process notes run on private networks inside our cloud account.
- Encrypted inside the platform too
The database rejects any connection that is not encrypted, including connections from our own services.
- One region, in the United States
Our platform runs in a single Amazon Web Services region, in Oregon. Where the AI vendor processes the text it reads is stated in the list of subcontractors attached to the business associate agreement.
- Credentials kept out of the code
Database credentials and API keys are held in AWS Secrets Manager and handed to the services when they start.
Who can reach clinic data
Clinic accounts see one clinic. Every sign-in to the application needs a second factor.
Including ours: the last item below is about our own staff.
- One clinic per account
Each clinic account belongs to one clinic. A request from it for another clinic's data is refused and recorded.
- Roles, checked on every request
Accounts carry a role, such as provider, coder or clinic admin, and the application checks it on every request. An account whose role cannot be read gets the least access, never the most.
- A second factor on every account
Signing in takes a password and an authenticator code. An account that has not enrolled a second factor can reach only the enrolment screens.
- Lockouts
Repeated failed sign-ins lock out further attempts for a growing interval, and sign-ins and failed attempts are recorded.
- Our own access
Our administrators can reach clinic data in the application, and each administrator account needs a second factor to sign in. Under our services agreement, they do not open your clinic's notes or results to help with a support request unless your clinic approves it in writing for that request, naming the visits and how long the access lasts. You can withdraw an approval at any time, and each access is logged. Approval runs by email until in-app approval is built. The agreement lists the exceptions, such as a security incident or a legal requirement. Outside the application, the people who run the platform can also reach the systems that hold clinic data through our cloud account, to keep it running.
The AI model
A third-party AI model reads the text of your notes. It has no account, no screen and no standing access.
The software uses a large language model from a third-party AI vendor to read the text of a note and propose codes for your reviewer to decide. The vendor is named, with where it processes that text, in the list of subcontractors attached to the business associate agreement.
No clinic note is sent to that vendor until it is under a signed business associate agreement with us, and every condition its agreement sets before patient information may be sent has been met and confirmed in writing. That is a condition written into our agreements, not something we assume.
The model proposes. It never makes the coding decision, submits nothing and changes no code. Your reviewer's accept or dismiss is the coding decision, and it is recorded.
Records and backups
What is recorded, and what is backed up.
- Sign-in records
Sign-ins, failed attempts and second-factor events are recorded against the account and the clinic they belong to.
- Account activity
Every change to our cloud account's configuration, users and permissions is recorded in a trail that covers every region and validates its own log files, kept in encrypted, versioned storage.
- Network records
Load-balancer access logs and network flow logs are kept in encrypted storage.
- Backups
The database is backed up automatically every day, with point-in-time recovery, and deletion protection is switched on.
- Versioned chart storage
The chart store keeps prior versions of each file, so an accidental overwrite or deletion can be recovered.
Not done yet
What is not in place yet, said plainly.
These items are open today, and none has a date. Each is to be done before any clinic's notes reach us, unless the item says how we work until it is done.
- In-app approval of support access
Your clinic admin approves each support request's access in the app, sees which visits it covers and for how long, and can end it, and the clinic sees a log of every view made under it. Until it is built, approval runs by email under our services agreement.
- Counsel's review of our security policies
Our security policies, risk analysis and retention schedule exist as dated drafts. They go to a healthcare attorney before we rely on them.
- A tested purge
A per-clinic deletion procedure for the end of an agreement, tested on a sample clinic before any real one, with written confirmation of what was destroyed and of anything the agreement lets us keep, such as security logs.
- A tested restore
The database restored from its backups, with the result written down.
- Every vendor condition met, in writing
No chart content goes to a vendor until that vendor is under a signed business associate agreement and every condition the agreement sets before patient information may be sent has been met and confirmed in writing.
- What we do not claim
No third-party certification or attestation, and no badge. HIPAA is a law that applies to us as a business associate once we handle a clinic's patient information, not a label anyone issues. What is in place is listed on this page, item by item, beside what is not. What we commit to is in the agreements we sign.
This website
This website collects no health information.
The booking form asks for your name, clinic and email, plus optional answers about your practice. Answers go to a spreadsheet and an email inbox in our company's Google Workspace account, and we reply by email. Please do not send patient information through this site.
Analytics cookies are set only if you accept them. Before you choose, or if you decline, no analytics cookie is set, though Google may still receive basic information about the page visit, as the privacy notice explains. The form uses Cloudflare Turnstile to tell people from bots. The site is served over HTTPS, and a plain HTTP request is redirected.
The privacy notice says what we keep and how to see, correct or delete it.
The settings on this page were read from our systems in October 2026.
Book a fifteen-minute demo
Fifteen minutes on example charts, start to finish. Bring your security questions, or your questionnaire.