Security
Safe for your patients. Simple for your team.
Built for a medical practice from the first day. Here’s the short version, in plain words.
Five short answers
Where patient information lives
In a HIPAA-eligible Amazon Web Services (AWS) environment, under a signed Business Associate Agreement. Where we handle patient information for a practice, we do it as that practice’s business associate under HIPAA.
Who sees what
Everyone signs in as themselves and sees what their role needs: their own work, for their own department and locations. If a role hasn’t been given access to something, it stays closed. The person who runs the practice and our team can see across it, and every look they take is logged like anyone else’s.
Every look at patient information, recorded
Each time anyone opens patient information, including us, it’s recorded: who, what and when, in a log that can be added to but never edited or erased. When someone covers for a colleague, both names are on the record.
Drafts, checked by a person
The AI runs inside the same AWS environment, through Amazon Bedrock. Rule checks run first, every finding points to where it came from, and nothing reaches a chart or a claim until a person on your team confirms it.
Sign-in
Staff sign in with the accounts your practice already manages, with two-step verification enforced by your practice’s own sign-in provider (such as Google Workspace).
Your EHR stays.
Your EHR remains your record, and your team keeps charting where it does today. Grand Vision One works alongside it, bringing the follow-ups, plan reports, lists and portal checks into one place. Anything it prepares for the chart is entered by a person on your team.
This website and the system are separate.
What you’re reading is a public website, hosted on its own. It holds no patient information, ever. The system your team works in runs separately on AWS, covered by the agreement above. Please don’t put patient names or details in our contact form.
For your IT or compliance lead
- Four checks whenever patient information is involved. Sign-in as a named person; a role and location permission check that is closed by default; a line in the record of every look at patient information; and a practice boundary enforced by the server, so one practice can never see another’s data.
- Covering staff. When a supervisor covers a shift or steps in to troubleshoot, the log records both people.
- Compliance view. Compliance staff can read across departments for audits but can’t change anyone’s work.
- The EHR connection. A read-only connection. Anything we prepare for the chart, such as a correction or an addendum, is entered in the EHR by a person on your team.
- Where patient information stays. Inside AWS services covered by the Business Associate Agreement. None of it goes to analytics, marketing or any other outside service.
- AI. Amazon Bedrock, inside the same AWS environment and agreement. Rule checks run before any model is asked anything. Every finding cites its source. Nothing reaches a chart or a claim until a person confirms it.
- Bookkeeping link. If we keep your books, only de-identified figures travel to them.
- This website. Hosted separately, holds no patient information, and its contact form is for contact details only.
- Certifications. We don’t claim certifications we don’t hold. Ask us about our controls directly.
- Policies. Website privacy policy · Browser extension policy
- Security questions. nate@grandvision.co
Bring your compliance questions to the first conversation.
Bring your compliance officer, too. We like the hard questions.
Nothing to prepare · Nothing to sign · You decide after