For IT Leaders

Zero infrastructure. Maximum control.

Sirona runs in AWS with enterprise security and standard integrations — no servers, no storage arrays, no VPNs, no maintenance windows. Your IT department finally moves beyond firefighting.

See Sirona in Action

How Sirona is Different

Cloud-native eliminates the entire on-prem stack

Sirona eliminates the entire on-premise PACS stack — servers, storage arrays, backup systems, VPNs, disaster recovery appliances, firmware updates, and maintenance windows. Everything runs in AWS with Netflix-style edge streaming deployed globally. Your IT team doesn't manage DICOM archive storage, failover redundancy, or infrastructure scaling. We do. Studies, reports, and analytics flow through a managed CDN with automatic replication across availability zones. Zero infrastructure debt. Zero hardware procurement cycles.

Built for IT operations from day one

Sirona's architecture solves the core problems that IT teams face managing legacy PACS infrastructure — not as an afterthought, but as the foundational design.

99.95% Uptime SLA

Multi-AZ AWS deployment with automatic failover — 99.99% historical uptime. No maintenance windows. No PACS downtime to plan around.

Learn more

Zero Hardware to Manage

No PACS servers. No SAN arrays. No disaster recovery appliances. No procurement cycles every 3–5 years.

Learn more

Automatic Updates, Zero Downtime

Feature releases and security patches roll out continuously without taking the system offline.

Learn more

Role-Based Access Control

Define roles once in Sirona, with SAML SSO for authentication. LDAP directory sync is on the roadmap. Full audit trail tracks every access automatically.

Learn more

Immutable Audit Logging

Every action logged in tamper-proof records. Full traceability for compliance audits. HIPAA audit trail is native, not a bolt-on.

Learn more

Standard Integration Framework

REST APIs, DICOM, HL7, FHIR. Connect to any EMR or third-party system without proprietary middleware.

Learn more

How IT teams eliminate infrastructure complexity

Infrastructure

Managed infrastructure means you stop being a systems administrator

Managing PACS today means managing servers — hardware, operating systems, patches, storage arrays, backup systems, disaster recovery configurations. Sirona inverts this: we run the infrastructure, you run the clinical workflows. Your IT team becomes a facilitator of clinical care, not a maintainer of hardware. When you're managing 50,000+ studies in your PACS archive, eliminating the hardware lifecycle removes an entire category of infrastructure cost.

AWS multi-AZ redundancy — no local backup hardware required

Automatic storage scaling — no SAN procurement cycles

Built-in disaster recovery — no separate failover planning

Zero maintenance windows — no coordination with clinical staff

Security & Compliance

Compliance is automated, not manual

HIPAA audits typically find that PACS audit logs are incomplete, untraceable, or not retained in tamper-proof format. Sirona changes the compliance model: audit logging is baked into the architecture. Every study access, every report modification, every login is captured in an immutable log. When an auditor asks for a complete user activity trail for the past year, the system generates it in minutes. Sirona is SOC 2 Type II certified, with security controls under continuous review.

SOC 2 Type II certified — six consecutive years, zero exceptions

Automatic HIPAA audit trail — no manual logging or retention management

Role-based access control with SAML SSO (LDAP sync on the roadmap)

Encryption at rest (AES-256) and in transit (TLS 1.3)

Integration

Integrations don't require specialized PACS consultants

Legacy PACS integration is a specialized skill. You need consultants who understand both DICOM and HL7, plus your specific EMR, plus your specific RIS. Sirona uses industry-standard interfaces that any healthcare IT professional can work with. If your EMR team can configure HL7 interfaces in Epic or Cerner, they can integrate Sirona. No proprietary middleware. No integration projects that take six months.

DICOM, HL7, FHIR — industry standards, not proprietary APIs

Direct integration with Epic, Cerner, Allscripts

Worklist synchronization in real time

REST APIs for custom integrations with your own systems

Migration

Go-live in weeks, not months

Legacy PACS migrations drag on for a year or more. Sirona's cloud-native architecture collapses that to weeks: no on-prem procurement, no site-by-site hardware staging, no parallel-run years. We ingest your archive via DICOM, stand up tenants in AWS, configure workflows, and train teams in parallel — so clinical users switch without a cut-over weekend.

Fast go-lives, even at enterprise scale

Archive migration via standard DICOM protocol

Legacy PACS remains read-only during gradual transition

No specialized PACS administrator required post-launch

IT operations impact

0

on-premise servers, storage arrays, or backup appliances required

99.95%

uptime SLA — 99.99% historical, automatic failover, zero maintenance windows

Complete

audit trail — immutable logging of every study access

IT leaders see the difference

RadOS architecture fireside — how Sirona is built

RadOS AI fireside — orchestrating AI across the platform

FAQs

Do we really not need any on-premise infrastructure?

Correct — Sirona requires no on-premise PACS servers, storage arrays, or dedicated appliances. The only requirement is standard internet connectivity from your sites to AWS. Studies and reports flow through AWS CloudFront CDN with geographic edge caching, so performance is fast even with modest bandwidth. Multiple sites all connect to the same cloud platform — no replication appliances, no site-to-site VPN complexity.

How does Sirona handle disaster recovery?

Disaster recovery is built into Sirona's architecture. Data is replicated across multiple availability zones automatically, with built-in failover that keeps studies and reports accessible. You don't need to procure a secondary PACS, configure replication appliances, or manually test failover — we validate recovery through regular drills. Broader cross-region disaster recovery is on our roadmap for H1 2027.

How do security updates and patches work?

Sirona applies security patches and feature updates continuously, without downtime. Updates roll out to the platform incrementally, not to individual customer installations. You don't schedule maintenance windows. You retain control over which deployment track you follow, and you can schedule when that track updates your environment, but that's a software configuration, not a maintenance window.

We use Epic / Cerner / Allscripts. How does Sirona integrate?

Sirona integrates directly with all major EMRs via standard HL7 and FHIR interfaces. Your EMR sends demographic data and order information via HL7 ADT and ORU messages. Sirona receives those messages, auto-creates worklists, and routes studies accordingly. When reporting is complete, Sirona sends results back to the EMR via standard HL7 messages.

What about HIPAA compliance and audit logging?

Sirona is HIPAA-compliant by architecture. Every study access, every report edit, every user action is captured in immutable audit logs. These logs satisfy HIPAA audit trail requirements automatically — no separate logging appliances, no manual log retention, no log rotation policies. The system is SOC 2 Type II certified, with six consecutive years of clean audits.

What's the migration path from our existing PACS?

Sirona ingests your existing PACS archive directly via DICOM protocol. Depending on archive size and network bandwidth, this typically takes weeks, not months. Once the historical archive is loaded, Sirona becomes your system of record for new studies while you keep your legacy PACS running read-only for edge cases. You can migrate gradually — no forced cutover weekend.