
For IT Leaders
Zero infrastructure. Maximum control.
Sirona runs in AWS with enterprise security and standard integrations: no servers, no storage arrays, no maintenance windows. Updates are automatic and audit logging is built in, so IT moves beyond firefighting.
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, disaster recovery appliances, firmware updates, and maintenance windows. Everything runs in AWS, with progressive image streaming over a global CDN. Your IT team doesn't manage DICOM archive storage, failover redundancy, or infrastructure scaling. We do. Data is replicated automatically 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 moreZero Hardware to Manage
No PACS servers. No SAN arrays. No disaster recovery appliances. No procurement cycles every 3–5 years.
Learn moreAutomatic Updates, Zero Downtime
Feature releases and security patches roll out continuously without taking the system offline.
Learn moreRole-Based Access Control
Define roles once in Sirona, with granular permissions across organization, clinic, and facility scopes. Single sign-on is available through our identity-provider integration, configured per organization during onboarding.
Learn moreAudit Logging
Changes to clinical information are logged to durable, access-controlled storage. Traceability for compliance audits. HIPAA audit trail is native, not a bolt-on.
Learn moreStandard Integration Framework
Standards-based DICOM and HL7 integration — we handle the integration engineering for every site.
Learn moreHow 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 your archive holds years of studies, 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
Audit logging is built in, not bolted on
HIPAA audits typically find that PACS audit logs are incomplete or scattered across systems. Sirona logs changes to clinical information — 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; the attestation is available under NDA. Beyond the audit trail, Sirona captures detailed application event data, including session replays of how the application was used. We are making more of that data available through the Dashboard, and over time through the SDK and APIs.
Active SOC 2 Type II program — attestation available under NDA
Built-in audit trail — no separate logging appliance to run
Role-based access control, with single sign-on configured per organization
Encryption at rest (AES-256) and in transit (TLS 1.2+)
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 a standard HL7 interface, they can work with Sirona — and Sirona's integration team does the engineering on our side for every site.
DICOM and HL7 v2 — industry standards, not proprietary formats
Interface engineering handled by Sirona for every site
Orders in, signed reports back — over standard HL7 messages
Migration
A migration without a cutover weekend
Legacy PACS replacements commonly run 6–12 months. Go-lives typically fall between 1 and 9 months, with most of that range driven by data-migration requirements. there is no on-prem procurement and no site-by-site hardware staging. We ingest your archive via DICOM, configure workflows, and train teams in parallel, while your legacy PACS keeps running — so clinical users switch without a cutover weekend.
Go-lives typically run 1–9 months, driven mostly by data migration
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
HL7 + DICOM
standards-based integration — Sirona does the interface engineering for every site
IT leaders see the difference
Built Different: the architecture behind RadOS
Partnership Story: Embedded, Real-Time 3rd Party AI with RadOS
FAQs
Do we really not need any on-premise infrastructure?
How does Sirona handle disaster recovery?
How do security updates and patches work?
How does Sirona integrate with our EMR?
What about HIPAA compliance and audit logging?
What's the migration path from our existing PACS?