Standalone On-Premises DICOM Server

What You Get, With Nothing Else Required

• Storage SCP – a DICOM Archive (PACS) that accepts studies from any DICOM-conformant modality.
• Storage Commitment SCP (SCM) – confirm to a modality that a study has been safely committed to storage before it clears its own local copy.
• Query/Retrieve SCP – search and retrieve stored studies from any DICOM-conformant workstation or viewer.
• Modality Worklist SCP (MWL) – serve scheduled procedures to modalities, populated manually or fed by the HL7 side later if you add it.
• MPPS SCP – track procedure status (in progress, completed, discontinued) as modalities report it.

Configured Through SQL, Not Code – Compatible With Any Device Vendor

DICOM is a standard, but every modality vendor implements it a little differently – the exact tags a device expects in a worklist response, or how it structures a query, vary from one manufacturer to the next. ZiKiT’s Storage, Query/Retrieve, and Modality Worklist services are all defined dynamically: through SQL database views and DICOM mapping rules, not compiled code. When a device needs data shaped differently, you change a view or a mapping rule to match it – you don’t wait on a code release.

That’s what lets one DICOM Server work across a multi-vendor fleet of modalities without a custom build per manufacturer – proven and field-tested across real multi-vendor deployments.

Runs on Whatever Windows Hardware You Have

ZiKiT’s DICOM Server is a Windows service. On the server side it runs on Windows Server 2016 and later; on the client/device side it runs on Windows 10 and Windows 11, including embedded Windows editions (Windows 10/11 IoT Enterprise – not Windows CE). It installs with a zero-configuration SQLite database by default, so it runs on genuinely light hardware, down to a single tablet or point-of-care device, as easily as it runs on a full server. For production PACS deployments, point it at MS SQL Server or MySQL instead, using the exact same configuration tooling.

Scales to Load-Balanced, Multi-Instance PACS

The same DICOM Server that runs standalone on a single tablet also runs load-balanced across multiple instances against a shared MS SQL Server database – handling tens of millions of records without changing products or re-architecting. Center for Vein Restoration has run ZiKiT this way in production for over a decade; read the full case study on the HRZ website.

Add HL7 Later, Without Re-Platforming

Because the DICOM Server and the HL7 Message Broker share one product and one database schema, adding HL7 integration later – connecting to a HIS/EMR, publishing the Modality Worklist from real orders – doesn’t mean switching products or migrating data. See how that bridge works in Bridging a HIS/EMR to Your PACS.