
For AI & Software Vendors
Build on an open radiology platform.
Sirona is building the app platform for radiology: unified data access, deploy-once distribution, and HIPAA-ready infrastructure for AI companies and software vendors. The RadOS SDK is coming soon for partners.
How Sirona is Different
Unified data, in one layer.
Every AI vendor today integrates with fragments: DICOM from the PACS, HL7 from the EHR, worklist status from a proprietary system. Sirona's unified data model holds it in one layer: pixels, structured and free-text reports, prior history, worklist context, and demographics. Sirona's own AI is built on that layer today, and the RadOS SDK is designed to open it to partners. No stitching, no ETL, no reconciliation.
Build on infrastructure designed for radiology AI
The RadOS SDK is being built to give developers API access to unified data, orchestration, and deployment infrastructure.
RadOS SDK
Coming soon for partners and developers: API access to unified DICOM data, reports, and workflow events, with an event-driven architecture for workflow integration.
Learn About SDKAI Orchestration
Routes studies to algorithms by modality, anatomy, and clinical context, and coordinates multiple algorithms on a single study. Sirona's own AI and integrated partner algorithms run this way today, and the catalog keeps growing.
Explore OrchestrationUnified Data Access
Planned: query DICOM pixels, reports, priors, worklist status, and clinical context through one API. No stitching, no reconciliation.
Explore Data ModelSecurity & Compliance
Deploy to Sirona's HIPAA-ready infrastructure, backed by an active SOC 2 Type II program. Encryption, audit logging, and role-based access control are part of the platform.
Review ComplianceReimbursement & Revenue
Some third-party, FDA-cleared AI algorithms carry their own CPT codes. Sirona does not build reimbursable AI; we integrate the partners who do, so your algorithm's usage stays visible alongside the study.
SDK visionDeveloper Documentation
On the roadmap: API references, code samples, testing tools, integration guides, and a sandbox environment for development — with partner success team support throughout.
Talk to our teamBuilt for the vendors who build on it
Sirona is building the infrastructure layer, so you can focus on algorithms.
The Platform
Data, orchestration, and distribution, by design
Sirona is building a platform that provides unified data, an orchestration layer that routes studies, HIPAA-ready infrastructure, and distribution to radiologists across the platform. Your job is building great algorithms.
Planned: unified DICOM, reports, and context in one API
Designed so the orchestration layer routes studies to your algorithm
Deploy to HIPAA-ready infrastructure (active SOC 2 Type II program)
Practice-side deployment handled by Sirona
Algorithm marketplace, on the roadmap
The Opportunity
Why now: reimbursement, scale, agentic AI
Some third-party, FDA-cleared AI algorithms are now eligible for separate CPT codes, which opens a reimbursement pathway for the vendors who build them. Traditional integration takes years to reach a handful of practices; Sirona is designed so one integration reaches radiologists across the platform. And unified data with an event-driven architecture is meant to let you build what fragmented stacks make hard.
Separate CPT codes exist for some third-party, FDA-cleared algorithms
One integration designed to reach every practice on Sirona
Build on images, reports, and clinical context from one data layer
Event-driven architecture designed for agentic automations
Planned: modular, versioned plugin architecture
The Ecosystem (Coming Soon)
What one SDK is designed to support
One SDK is meant to cover the breadth of what vendors build: diagnostic algorithms, workflow tools, integration platforms. All on the same RadOS SDK, deployed to the same infrastructure, reaching the same customer base. Third-party AI is integrated in Sirona today, and the catalog keeps growing; the partner program is taking shape now.
Diagnostic algorithms share one data layer
Workflow tools collaborate through event streams
Integration platforms access unified context
One customer base for every partner
How to Get Started
How to get started
It starts with a conversation. The RadOS SDK isn't available yet, so there is no public sign-up. Tell us what you've built and who it's for, and we'll map the path: integration, testing against representative data, partnership review, and deployment to the Sirona customer base.
Talk to our team about your application
Integrate via the SDK as it becomes available
Test against representative data
Submit for partnership review and certification
Deploy to the Sirona customer base
Why build on Sirona
1
integration designed to reach every practice on Sirona
Coming Soon
the RadOS SDK, for partners and developers
510(k)
clearance for the Sirona Advanced Imaging Suite, October 2025: a regulated app built on RadOS
Partners on RadOS
“Through Sirona's platform, Everlight will be able to build and deploy AI-powered automations across clinical, administrative, and operational workflows. This partnership will fundamentally transform how our radiologists practice, and position Everlight at the forefront of AI-enabled diagnostic medicine globally.”
Jeff Oakman
Global Chief Operating Officer, Everlight Radiology
Partnership Story: Embedded, Real-Time 3rd Party AI with RadOS
Making 3rd party AI embedded, real-time, and responsive within radiologists' existing reading environment has been a Holy Grail problem for years. Here, RevealDX's CEO, Chris Wood, and Sirona's founder and president, Cameron Andrews, discuss how RadOS can make third-party AI applications more valuable to physicians through deep integration and custom, customizable user interfaces via our RadOS SDK platform.
FAQs
What is the RadOS SDK and how is it different from traditional PACS integrations?
What data can my algorithm access through RadOS SDK?
How does Sirona's orchestration benefit my algorithm?
How does reimbursement work?
Do I need to be HIPAA-compliant?
How quickly can I reach radiologists after launching?