Medical Breakthroughs

Why Encrypted DICOM Remains Switched Off in Hospitals

Listen to this article · 7 min listen

Improving cybersecurity always seems to clash with the messy reality of the equipment you already have, and nowhere is that truer than in hospital imaging networks. Encrypted DICOM, the secure version of the 30-year-old medical imaging standard, is the obvious way to protect patient data as it flies around the network. Yet almost no one uses it. For imaging directors and health IT security leads, turning this on isn’t just flipping a switch. It’s a messy calculation involving compatibility nightmares, operational headaches, and the constant work of keeping everything both secure and actually running.

Why Secure DICOM Stays Switched Off

Medcrypt’s engineering blog digs into why secure DICOM has such poor uptake, and they nail it. The problem is that encryption was bolted onto the DICOM standard decades after it was established, which makes the whole thing a compatibility story. The core challenge is that every single piece of gear in an imaging workflow, from the MRI scanner to the PACS archive and the doctor’s workstation, must speak the exact same encrypted “dialect.” If even one node in that chain, say, an older modality that the vendor no longer supports, can’t handle encrypted DICOM, the entire workflow either breaks or just falls back to sending everything unencrypted anyway. This gets worse when you look at the typical imaging department’s mix of hardware from a dozen different vendors, bought over twenty years. Trying to patch or upgrade every single machine is a massive project that risks system meltdowns and weird interoperability bugs. Faced with that, the known, immediate cost and disruption of an upgrade project often seems much worse than the theoretical, future cost of a data breach.

The Imaging Networks Running on Unencrypted Data

This is the environment where advanced AI is now being deployed. Companies like Viz.ai which has tools for Cardiology, Radiology, and Oncology and pushes Multi-Modal AI, plug their platforms directly into these imaging networks. Their AI reads the scans and provides critical information, all of it depending on a smooth, uninterrupted flow of DICOM images. This shows the strange paradox we’re in: the same systems using the latest AI to help doctors are often the ones sending patient images across the hospital network without any end-to-end encryption. In practice, images have to move fast. Any delay or hiccup directly slows down patient care, diagnosis, and treatment. For an imaging director, the risk of a system-wide meltdown caused by trying to enable encryption feels a lot more real and immediate than the risk of a hacker getting inside the network (especially if they’ve never been breached before). The pitch for secure DICOM has to get past security theory and start answering the practical operational questions that keep these directors up at night.

What Infrastructure Material Would Need to Be Measured

Before more hospitals start adopting encrypted DICOM, imaging directors and IT security leads need some real numbers. The fact that adoption is so low tells you there’s a big gap in the data that would justify the cost and effort. To make a business case, they need answers to a few key questions:

  • Compatibility Costs: This is the big one. What’s the real-world cost, per device, per vendor, to upgrade the firmware, software, or even the hardware itself to get it to support encrypted DICOM? That’s not just the vendor’s invoice. It’s your own IT staff’s time for testing, validation, and managing the potential downtime. Industry report on medical device upgrade costs
  • Downtime Risk: What’s the real probability of an outage if we try to make this switch, and how long would it last? You’d have to account for testing windows, rollback plans, and the inevitable surprise incompatibilities. You have to be able to quantify the impact of even a few hours of downtime on patient appointments and department revenue.
  • Breach Exposure vs. Mitigation: HIPAA says protect the data, sure, but the risk of unencrypted DICOM traffic inside the hospital’s own network needs to be quantified. What’s the actual likelihood of a breach targeting this specific data in transit? What’s the average cost of that kind of breach, once you add up the fines, reputational hit, and patient notification? You have to weigh that number against the cost of turning on encryption. HHS guidance on HIPAA security rule
  • Performance Impact: Does turning on encryption add any noticeable lag to image transmission or retrieval? For a busy hospital, even a tiny delay on every single image adds up and can bog down the whole workflow.
  • Vendor Support and Guarantees: What kind of support are vendors actually offering for this? Are they guaranteeing interoperability and performance when their box is connected to another vendor’s box? The hospital is always the one stuck holding the bag and trying to make disparate systems work together, so clear commitments from vendors are essential. Without hard figures on these points, the choice to enable secure DICOM is based more on a gut feeling about security best practices than a solid risk-benefit analysis.

    What Would Move Adoption

To get more people to use secure DICOM, the equation has to change. We need to shift who carries the cost and the risk. The central question is, who pays for the upgrade, and who is on the hook if they don’t? Right now, the hospital pays for the expensive implementation, takes on the operational risk of things breaking, and also carries the long-term risk of a breach if they do nothing. For adoption to pick up, a few things need to happen:

  • Standardized Implementation Roadmaps: We need industry groups or even regulators to publish clear, step-by-step guides for implementation, complete with best practices and validated setups for the most common combinations of vendor equipment.
  • Vendor-Driven Solutions: Device makers and PACS vendors have to start shipping products with encrypted DICOM as a default, easy-to-use feature, not a complex, expensive add-on. That means providing simple upgrade paths and making sure their new gear can still talk to older systems when necessary.
  • Quantified Risk Assessments: Insurance companies and cybersecurity firms could create a direct financial incentive by offering more specific risk assessments that tie the lack of encrypted DICOM directly to higher insurance premiums or liability.
  • Regulatory Pressure with Support: While HIPAA requires security, more specific guidance or incentives around encrypted DICOM could push things along. But that has to come with resources and frameworks to help hospitals implement it, not just another unfunded mandate. NIST cybersecurity framework for healthcare
  • Case Studies with ROI: We need early adopters to publish their success stories, detailing what they actually spent, the benefits they saw (like cleaner security audits), and how they handled the operational risks. That would give other hospitals something concrete to follow. Until those numbers are tracked and the financial and operational math clearly favors turning it on, encrypted DICOM is going to stay switched off. That leaves a huge vulnerability right in the middle of healthcare’s digital infrastructure. Moving forward will take a real effort from vendors, regulators, and providers working together to make adoption less risky and to show that the benefits are worth the cost.

Frequently Asked Questions

What is the primary reason encrypted DICOM is not widely adopted in hospitals?

The main issue is compatibility. DICOM was established before encryption was a standard consideration, meaning all components in an imaging workflow, from scanners to workstations, must support encrypted DICOM. If even one device cannot, the entire workflow may revert to unencrypted transmission or halt.

What are the main challenges in upgrading existing imaging infrastructure to support encrypted DICOM?

Hospitals typically have diverse imaging equipment from multiple vendors and generations. Upgrading every piece of equipment is a monumental task, risking system instability and interoperability issues. The immediate costs and operational disruptions often seem to outweigh the future, less tangible costs of a data breach.

What key data points are needed to make an informed decision about implementing encrypted DICOM?

Decision-makers need concrete data on compatibility costs per device and vendor, including direct costs, IT labor, and potential downtime. They also need to quantify downtime risk, the specific likelihood and cost of a breach targeting unencrypted imaging data, and any potential performance impact of encryption.

Share
Was this article helpful?

Editorial Team

The Editorial Team at Vertical AI Health Leaders is a group of writers and editors who cover health, workplace wellness, and everyday care. They research each story and publish under a shared desk byline — experts in their fields, working as one team.