HIPAA-oriented architecture
The product is designed for healthcare operations data. We do not use “HIPAA Certified.”
Security
Securityhow access is granted, not a badge wall
HIPAA-oriented architecture and BAA-ready infrastructure. This page walks the invite, role, and review process you see in the product — not a certification stamp.
We do not claim HIPAA Certified, SOC 2, GDPR, or HITRUST on this site.
On this page
Twelve sections on the access process
Public language first, then the invite screen, roles, separate apps, and what happens before any patient data moves.
What we will say in public
BAA-ready infrastructure
A Business Associate Agreement is discussed before patient data is processed in the apps.
Role-based access
Office, field team, and household surfaces are not one shared inbox.
Audit trail
Who changed the board is part of the operations product, not a slogan.
Team Settings
Invites happen in the product, not in a shared password
The New Administrator dialog collects name, work email, and a role. An invitation email is sent so the person sets their own password. Names in this preview are sample UI, not real records.
- Choose Administrator or Super Administrator on the invite
- The product sends the email — no shared password in chat
- They appear as Invited until they accept, then Active
How an administrator is added
The same path as the screen above — office staff stays on the admin host.
- 01
Open Team Settings
Invite Members is where the current admin starts. Roles & Permissions and Audit Logs sit next to it.
- 02
Choose a role
Administrator is standard access. Super Administrator can manage other admins.
- 03
Send the invite
The product sends an invitation email. The new person sets their own password.
- 04
They appear on the list
Status shows Invited until they accept, then Active. Actions stay with an admin.
Two admin roles on that dialog
These are product roles in Team Settings. They are not compliance certifications.
Administrator
Standard access to run the day’s board: visits, teams, and routes on the admin host.
Super Administrator
Full access, including managing other administrators. Selected on the invite when that is the intent.
Field team
Providers work from the mobile app host — not the same login as the office board.
Household
Patients can book and see an ETA on a separate patient host. That is not an admin seat.
Three surfaces, three hosts
Admin
Office command center: schedule, map, team settings, and invites.
Med-team
Provider app for the people who actually run the stops.
Patient
Household booking and ETA. Not a shared inbox with the office.
This website
Marketing and demo intake only. Organization and workflow — no PHI.
This marketing site versus the product apps
fieldrounds.ai (this site)
- Public copy and a demo form
- No patient addresses or charts
- Indexable pages for buyers
- Not the compliance packet
Admin / med-team / patient hosts
- Where operations data lives after a BAA
- Role-based logins and the audit trail
- Those apps should remain noindex
- Questionnaires belong on a demo, not this form
How a security review usually runs
01
Book a demo
Walk Team Settings and the invite dialog with sample UI — not a live patient list.
02
Send the questionnaire
We answer from architecture and contracting language. We will not invent badges to fill a cell.
03
Discuss a BAA
A Business Associate Agreement is part of the conversation before patient data moves.
04
Then the apps
Access is provisioned on the product hosts. This website still does not collect PHI.
What we will say versus what we will not
| Capability | FieldRounds | We will not say |
|---|---|---|
| Architecture | HIPAA-oriented | HIPAA Certified |
| Contracting | BAA-ready infrastructure | SOC 2 or GDPR badge |
| Access | Role-based invites and separate apps | One shared inbox for office and field |
| History | Audit trail in the product | HITRUST or invented attestations |
What the audit trail is for
Team Settings includes Audit Logs next to Roles & Permissions. We describe the operations record — not a certified logging product.
Who was invited
A new administrator appears as Invited, then Active. The invite is an email they complete themselves.
Who changed a role
Moving someone between Administrator and Super Administrator is an admin action, not a chat-thread edit.
Who changed the board
Visit and team changes sit on the same operations record buyers ask to see on a demo.
What it is not
An audit trail is not a substitute for a BAA, and it is not a certification we print as a badge.
PHI stays off this website
Do not send here
- Patient names or addresses
- Charts, photos, or visit notes
- Real phone numbers from a roster
- Anything that belongs only in the product apps
Fine for the demo form
- Organization name and your role
- How the field day is scheduled today
- Whether a doctor, nurse, and driver share a stop
- When you want to walk Team Settings
What to bring to a security conversation
Your questionnaire
We fill it from public language plus a product walk — we do not invent missing badges.
Who provisions access
Ask to see Invite Members, the two admin roles, and the invitation-email path.
Where apps will live
Admin, med-team, and patient hosts stay separate from this marketing site.
When a BAA starts
Before patient data is processed in the apps — not before a first demo.
Walk Team Settings on a demo — then send the questionnaire.
FAQ
Security questions we hear first
Is FieldRounds HIPAA Certified?
We do not claim HIPAA Certified, SOC 2, or GDPR badges. We describe HIPAA-oriented architecture and BAA-ready infrastructure.
What does BAA-ready mean here?
A Business Associate Agreement is part of the contracting conversation before patient data moves. This marketing site does not collect PHI.
How do administrators get access?
An existing admin opens Team Settings, chooses a role, and sends an invitation email. The new administrator sets their own password.
What roles exist?
The product UI distinguishes Administrator (standard access) and Super Administrator (manages other admins). Field and household users sit on separate apps.
Is there an audit trail?
Who changed the board, who invited a user, and who changed a role is part of the operations product — including an Audit Logs area in Team Settings. That is not a certification badge.
Where do product apps live?
On separate hosts (admin, med-team, patient). Those apps should remain noindex.
Can I send PHI in the demo form?
No. Use organization and workflow details only.
Is this page the compliance packet?
No. It is public copy. Detailed questionnaires happen after a demo.
Book a FieldRounds demo
Tell us about the field team. Do not include patient names or other protected health information in this form.
Ask security questions on a demo
Bring your questionnaire. We will not invent badges to fill gaps.