Somebody in an imaging department has probably said some version of this sentence in the last week: “Try burning it to a CD.” A referring physician cannot open a portal link that expired sometime after lunch. A patient shows up at a specialist’s office holding a disc that will not read on anything built in the last five years. A front desk answers the same question for the third time today: yes, the study was sent, no, nobody can say why it has not shown up yet.
None of this is really about images, or even image sharing as a checkbox feature. It is about how much of a clinic’s day quietly disappears into getting an image from one place to another, and how often the fix is a phone call instead of the software simply working.
That gap, between how simple sharing a study should be and how hard it usually is, is where OmniPACS put some of its heaviest investment in rebuilding Condor. Sharing is the moment an imaging workflow stops being internal and becomes someone else’s problem too: a referring provider trying to make a decision, a specialist prepping for a consult, a patient who just wants their own scan. A system that makes that handoff smooth, instead of adding a step of its own, earns its keep in that moment more than almost anywhere else in a PACS.
The Real Cost of a Broken Sharing Workflow
It is tempting to file bad image sharing under “annoying” and move on. The costs are more concrete than that, and they compound. Every CD that will not open, every link that has quietly expired, every referring office that has to call and ask, is staff time pulled away from the next patient.
It is a specialist’s read waiting on a study that was technically “sent” an hour ago but has not actually arrived anywhere useful. Multiply that across every study a busy imaging center shares in a week, and sharing friction stops looking like a minor irritation. It behaves like an operating cost with no line item of its own.
The Cost That Never Shows Up on a Complaint Log
The harder cost to see is what gets lost outright rather than just delayed. That loss has a name in healthcare operations: referral leakage, patients and referrals that quietly go somewhere else because something in the handoff broke down. A referring provider who cannot open a study rarely calls to complain about it. More often, the next patient just gets routed somewhere the images show up without a fight.
That is not a hypothetical specific to imaging. It is the same general failure mode: friction in a handoff quietly becomes a lost relationship, not merely a delayed one.
The CD Is Still the Norm, Not the Exception
The industry has also been slow to close this gap on its own. A recent analysis of the nation’s largest hospital systems found that 72 percent still routinely rely on CDs to share patient imaging, despite years of secure digital alternatives already existing. None of the fifty systems in that analysis had eliminated CD use entirely.
That is not a story about clinicians who prefer old technology. It is a story about how hard sharing has historically been to fix properly, and how much of the industry has settled for a workaround instead of a real fix.
What Good Image Sharing Actually Requires
Fixing this is not primarily a matter of bolting on a “share” button. Most PACS platforms already have one, including older versions of OmniPACS. It is a matter of what has to be true for sharing to stop generating support tickets and start being something a person does without a second thought, in the middle of everything else they are already doing.
The clearest way to see the shape of what Condor set out to build is to watch it directly.
That training overview covers the current Condor experience end to end, sharing included, for anyone who wants the full picture rather than a description of it, and it is a faster way to judge the “few clicks instead of a support ticket” claim than reading about it here. Anyone who would rather try it firsthand can always see the new Condor experience directly. What follows in this section is the reasoning behind the rebuild rather than a tour of a screen: the conditions a sharing flow has to meet before that claim is anything more than a slogan.
The Sender Should Never Have to Leave Their Work
Historically, sharing a study has often meant stepping out of the worklist entirely: opening a separate tool, hunting for the right export option, then coming back and hoping nothing got lost in the handoff. Every one of those context switches is a place where momentum breaks and mistakes creep in. Sharing has to live inside the same place the work already happens, as an action on a study rather than a detour away from one.
The Recipient Should Not Need an Account, a Plugin, or a CD Drive
The person receiving a shared study is very often not an OmniPACS customer at all. A referring physician’s office, a specialist across town, a patient on their own laptop: none of them should have to install anything, create credentials in advance, or own the right hardware just to open what was sent to them. Every extra requirement on the receiving end is another reason a study ends up back on a disc or stuck behind a “call us and we’ll walk you through it.”
Access Should Be Scoped and Expire on Purpose
Sending a study to someone should not mean handing over a permanent, unlimited copy of it. Good sharing grants exactly the access a specific handoff calls for, to a specific study, for as long as that handoff actually needs it, and closes automatically once that window has passed. That is a deliberate design choice, not a limitation: access that expires on its own is access nobody has to remember to revoke later.
The Sender Should Be Able to See What Happened Next
A share that disappears into silence is not meaningfully different from a fax nobody confirms was received. Whoever sent a study should be able to tell whether it was actually opened, without picking up the phone to ask. That single piece of visibility is what turns sharing from a one-way action into something closer to a conversation, and it is the detail that connects sharing to the rest of a well-run imaging workflow.
Controlled Access and Audit Posture
None of the above works without a real posture behind it. Scoped, expiring access only means something if every grant, every view, and every download is logged in a way that holds up to scrutiny later, whether that scrutiny comes from a compliance review, a security incident, or simply a patient asking who has seen their images. That posture, deliberate limits plus a dependable record of what happened, is the quiet infrastructure underneath a sharing experience that feels effortless on the surface.
Getting the implementation details right here is its own discipline, and OmniPACS has covered that ground directly elsewhere. For the technical practices that keep a DICOM transmission secure end to end, see our guide to secure DICOM sharing best practices. For what it takes to open that access safely across separate organizations rather than inside one, our walkthrough on enabling secure sharing across facilities covers the cross-organization side in depth.
This article is about why that posture matters to the person doing the sharing. Those two cover how to build it.
Sharing and Notifications: Closing the Loop
A rebuilt sharing flow solves one half of a very old problem. The other half is how anyone finds out something happened without having to go check. The old pattern in most imaging workflows was polling: refresh the worklist, call the front desk, ask a colleague if a study came through yet.
Tying sharing to a notification the moment something is opened, or a study arrives, or a report is ready, replaces that polling with an actual signal. The goal is not more alerts. It is fewer phone calls, which is a theme worth its own closer look and one we will come back to directly.
Why This Is Everyone’s Problem
Search is mostly a tech’s problem, and the worklist is mostly a scheduling problem, but sharing touches nearly every role that ever comes near a PACS.
A practice manager feels it as staff time and referral relationships. A records team feels it as the volume of “can you resend that” calls on a given day. A referring physician feels it as whether a decision gets made today or gets pushed to tomorrow because a study would not open. A patient feels it as whether their own scan is something they can actually get to, or something they have to physically go pick up.
That breadth is exactly why sharing got the attention it did in the Condor rebuild. Making the boring things easier, the core idea behind the entire platform rebuild, matters most in the places the largest number of people actually touch, and few things in a PACS get touched by more people than a shared study. The full story behind that rebuild covers why OmniPACS took on a platform rewrite of this size in the first place, sharing included among the reasons.
Sharing That Does Not Need a Follow-Up Call
The measure of good image sharing is almost boring by design: the right person gets the right study, quickly, without anyone needing to pick up a phone to confirm it happened. That is the standard OmniPACS held Condor’s sharing flow to, easier and more intuitive, because the honest goal was never to impress anyone mid-handoff. It was to get out of the way of care that is already waiting on an answer.
A referring office that stops calling to check on a study, a specialist who opens a link without a second thought, a patient who pulls up their own scan without driving anywhere to get it: that is what the fix is supposed to look like from the outside, and the fastest way to find out whether it actually does is to see the new Condor experience directly. Questions about how any of that behaves on a specific site are best routed to support@omnipacs.com, where the people who built it can actually answer them.
Frequently Asked Questions
Can I send MRI images via email?
Standard email is not a safe way to send MRI images or other protected health information, since most email is not encrypted end to end and messages can sit in inboxes indefinitely. A secure sharing link or a dedicated medical image sharing platform accomplishes the same goal without that exposure.
How do I send a DICOM file?
Most modern PACS platforms let you share a DICOM study directly from the worklist through a secure link, rather than exporting it manually first. Older or on-premise systems may still require exporting the study to a folder or disc before uploading it elsewhere. The direct route is faster and better documented.
How do I open a DICOM file?
DICOM files need a viewer built to read that format, since standard photo or PDF software will not display them correctly. When a study is shared through a proper medical image sharing platform, the recipient typically opens it directly in a browser-based viewer, with no separate software to install on their end.
What is considered a breach of patient confidentiality?
A breach of patient confidentiality happens when protected health information, including medical images, is accessed, shared, or viewed by someone without proper authorization. This covers everything from a lost unencrypted CD to a shared link left open too long. Access controls, expiration, and audit logging exist to keep an ordinary handoff from turning into one.