Access follows the practice boundary.
gBell signs a Business Associate Agreement before patient information moves. Access, support, patient links, and recordings each have their own control.
Security, live
Practice boundary
The BAA comes first.
gBell acts as a business associate when it handles protected health information for a practice. The BAA is signed before live patient data enters the service.
Follow the source through the work.
Each row is an inspectable state, not a promise floating above the product.
Clinic isolation
01One clinic boundary.
Each clinic account stays scoped to its own patients, calls, schedules, and staff.
Staff access
02Separate roles and sessions.
Owners, clinicians, front desk, billing, and read-only users receive separate permissions.
Support
03Time-limited and audited.
Approved support access has a reason, a window, and an audit trail.
Patient links
04A code stands between.
Patient detail stays behind a protected link and one-time access code.
Calls
05Disclosure comes first.
Sarah identifies herself as automated and says the call is recorded before the conversation continues.
Controls earn their place through evidence.
The site states current operating controls. Customer-specific security review and retention terms belong in the signed agreements for that practice.
Human review stays visible
Keep following the work.
gBell overviewgBell
Calls, scheduling, protected intake, coverage, posting, and staff handoffs stay connected as one piece of work.
gBell Scribe
gBell Scribe turns post-visit dictation into a case-specific draft, shows the exact words behind each claim, and asks before filling a gap.
Integrations
Sarah works around the practice’s phone number, schedule, rules, and record system. Full practice go-live is a separate release.
Bring us the work that keeps coming back.
Start with the workflow your team dreads seeing again. We’ll map where Sarah works and where your staff steps in.