HomeSecurity
Patient data stays inside your organization. Every person's access is approved by an administrator and limited by their role.
How access works
Four steps between a new account and any patient data.
Step 1Create an accountA staff member signs up with their work email or Google.
Step 2Request to joinThey enter the organization ID their administrator gave them.
Step 3Administrator approvesAn admin reviews the request and approves or denies it.
Step 4Role decides accessPrivileges decide which tools and data the person sees.
Safeguards
Built into every module, not added later.
Separated by organizationEvery record belongs to one organization and is isolated from all others.
Approved access onlyNo one sees patient data until an administrator approves them.
Role-based privilegesPeople see only the tools and records their role allows.
Account lockoutRepeated failed sign-ins pause the account automatically.
HIPAA safeguardsDesigned around HIPAA administrative and technical safeguards.
No PHI in notificationsAlerts and toasts never display patient details.
Security questions
Where is patient data stored?
In a managed database with each organization's records separated. We'll share hosting and encryption details under NDA.
Do you sign a BAA?
Ask us during your demo and we'll walk through our agreement.
Can we remove someone's access right away?
Yes. Administrators can remove a member or change their role at any time, and the change applies on their next request.
Give your team the day back.
Bring one workflow, like reminder calls or fax intake. We'll walk through it in Newbula with your data.
Or write to hello@newbula.ai