Built Like It Holds Your Patients' Records.
Because It Does.
The first question a careful owner asks is the right one: who can see my patients' records? Here's the plain answer, and how it's enforced.
Only the People Whose Job Requires It.
You already hold your staff to a standard: the front desk doesn't read billing, billing doesn't read charts, and everyone signs in as themselves. The Hub holds itself to the same standard — and writes down every look, so you can check.
Everything below applies to the Hub, where your staff work. This website is separate: it never touches patient data at all.
Four Checks, Every Time
Before anyone sees a single patient record, the Hub runs the same four steps. None of them can be skipped.
Your Own Accounts
Staff sign in with the accounts your practice already manages, with two-factor sign-in enforced by your Google Workspace. On a shared exam-room iPad, each person uses their own PIN, so every recording is tied to a real person.
Closed by Default
Every screen checks the person's role, department and locations first. Anything not explicitly allowed is refused — a locked door, not a hidden tab.
Every Look Written Down
Each time anyone opens patient information, the Hub records who, what and when — in a log that can be added to but never edited or erased.
Scoped to Your Practice
Every request is limited to your practice's data by the server itself, not merely hidden on screen. One practice can never see another's.
What That Means in Practice
Each Team Sees Its Own Work
Billing can't open clinical worklists; the front desk can't open billing. Compliance can read across departments for audits, but can't change anyone's work.
Both Names on the Record
When a supervisor covers a shift or steps in to troubleshoot, the log records both people — the one covering and the one covered. No disguises.
Read-Only, Always
The Hub never writes into your EHR. Corrections are prepared in the Hub for your staff to enter, so your chart stays yours.
This Website Never Touches Patient Data
What you're reading now is a public website on its own infrastructure. It holds no patient information, ever — not a name, not a date of birth, not a claim line.
The Hub is a separate application that runs on AWS under a signed Business Associate Agreement, with encryption, role-based access and access logging. Where we handle protected health information for a practice, we do it as that practice's business associate under HIPAA.
AI With a Human Signature
The Hub's AI runs inside the same AWS agreement that covers your patient data. Rule checks run first; the AI cites the line it relied on; a person on your team confirms every draft before it counts.
Asked & Answered
Who on my staff can see what?
Each person sees their own role's work, for their own department and locations — nothing more. You decide the roles. Your practice administrator and our two partners can see across the practice; compliance can read across departments for audits but can't change anything.
Does the Hub write into my EHR?
No, never. The Hub reads; your staff write. Anything the Hub prepares — a correction, an addendum — is entered in your EHR by a person on your team.
Is my patients' data used to train AI?
No. Your data is used to run your practice and nothing else — never shared, never benchmarked publicly, never used as marketing, and never used to train AI models. The AI runs through AWS under the same signed agreement that covers your records.
Where can I read the policy itself?
Our privacy policy covers this website and how patient information is protected in our client work. Our browser extension has its own policy.
Ask us the hard ones.
Bring your compliance officer to the walkthrough. You'll get straight answers from a partner, not a sales sequence.
Book the Walkthrough →We respond within one business day