Who sees and does what. Especially with AI.

Single sign-on is available through our identity-provider integration, configured per organization during onboarding. Users authenticate once through your existing identity provider and access Sirona without a separate password.

Not today. Roles are defined and managed directly in Sirona.

Sirona is extending its RBAC with permissions for AI model deployment (who can enable or disable algorithms), AI output visibility (who sees AI findings before radiologist review), AI configuration (who can modify model parameters), and AI analytics (who can access performance metrics), with every AI action written to the audit trail. These are in development; today's role model covers study access, reporting, worklist, facility scoping, and administration.

Yes. Roles can be scoped to the whole organization, a clinic, or a single facility. A radiologist at Hospital A sees only Hospital A studies. An administrator manages only their assigned locations. All enforced from a single admin interface.

Sirona logs changes to clinical information — including patient and order updates and study lifecycle events — to durable, access-controlled storage that supports HIPAA audit requirements.

Sirona runs an active SOC 2 Type II program, with the attestation available under NDA, and is HIPAA-compliant by design; you sign one BAA, with Sirona. Data is encrypted with AES-256 at rest and TLS 1.2+ in transit, and access is governed by the role model described on this page.

Legacy PACS typically offers basic login authentication with limited role granularity — often just 'radiologist' and 'admin.' Sirona provides granular permissions spanning study access, report editing, worklist management, and administrative functions, scoped to the organization, a clinic, or a single facility, with changes to clinical information written to a durable audit record.