A malpractice attorney’s office needs a patient’s imaging on disc by end of day, not after a portal invitation that may or may not get opened before a deadline. A patient is discharged to a rehab facility across town that has no way to pull the study electronically. A records team fields the request it fields most weeks: can you burn this to a DICOM CD?
None of that is an edge case. It is a Tuesday in a records department, and it has been a Tuesday in records departments for longer than most PACS vendors like to admit.
OmniPACS rebuilt its platform from the ground up this year, replacing a decade-old PHP application with a modern Python and Django backend and a React front end. The new platform is called Condor, and it is fast enough to build on that the first feature to ship since the rebuild did not sit in a backlog waiting for a slow quarter to clear. It shipped. That feature is creating an ISO image, a disc-ready file, directly from the worklist.
The Requests to Burn a DICOM CD Never Stopped Coming
Physical media has absorbed enough “any day now” predictions about its demise that the predictions themselves have started to look dated. A 2026 review of the largest hospital by bed count in every U.S. state found that 72 percent still routinely burn CDs to move imaging between institutions. Another 16 percent were in transition.
Not one of the fifty had eliminated the practice entirely. That is not a story about laggard hospitals refusing to modernize. It is a story about how many situations genuinely still call for a disc, no matter how modern the software producing it gets.
Where a Disc Still Beats a Portal Link
A malpractice or workers’ compensation attorney requesting a patient’s imaging rarely wants a portal invitation with a login and an expiration date attached to it. They want a file they can hand to an expert witness, unlocked from any particular vendor’s viewer.
A patient transferring between two facilities that do not share a network or an exchange partner needs the study to arrive in a format the receiving system can actually open, not a link that assumes a compatible viewer on the other end. A smaller practice without an established exchange rail into the sending system’s network has exactly one format everyone involved can reliably read: DICOM on a disc. And a plain records request, someone who simply wants their own study for their own files, does not always come with a preferred cloud platform attached to it.
None of these scenarios are going away because the industry wishes they would. They are why medical imaging CD requests remain a routine line item in records departments rather than a leftover habit from an earlier decade of PACS software, and why records staff still burn a DICOM CD on a normal week without thinking of it as unusual.
What Patients Are Owed, and How Fast
Records requests are not just an operational inconvenience to route around. They are a right, and a timed one.
Under HIPAA, a patient generally has the right to access and receive a copy of their health information, diagnostic imaging included, in a reasonably requested format. Covered entities get up to 30 days to comply, with a possible 30-day extension in specific circumstances. That is the legal floor, not a standard worth being proud of clearing.
A patient imaging records release that takes weeks because producing a disc means someone has to leave their actual job, walk to a separate workstation, and run a separate process is not breaking the law. It is just leaving goodwill on the table for a request that, in a lot of cases, should not take longer than it takes to finish charting the study in the first place. Any OmniPACS site whose records team wants a second set of eyes on how a specific request should be handled can start that conversation at support@omnipacs.com.
An Action on the Study, Not a Separate Errand
That gap, between what a records request should take and what it has historically taken, is exactly what changes when ISO creation moves onto the worklist itself. The old way of doing this on Alpha, OmniPACS’s original platform, meant leaving the study a tech or a records specialist was already looking at and running a separate process somewhere else to produce a disc. It worked, the way Alpha worked for years. It also meant a context switch every single time: a small tax paid by whoever happened to be handling the request that day, paid again the next time, and the time after that.
On Condor, it is an action on the study rather than a separate process, the same discipline OmniPACS applied to search, sharing, and notifications elsewhere in the rebuild: find the thing already in front of you, and let the task happen from there instead of sending someone on an errand to a different tool. That is not a claim that the software got more powerful. It is the same standard behind everything else in the rebuild, easier and more intuitive, applied to a task that happens to involve burning a DICOM CD instead of finding or sharing a study.
For sites still finishing their move onto Condor, or working out what a rebuilt worklist changes about a task like this one, the more useful next step is often to talk to us about your site’s rollout rather than read a feature description, since whether this fits how a specific records team works depends on specifics a general description cannot cover.
The Receipt for the Velocity Claim
There is a reason this is the feature worth writing about first, and it is not because burning a disc is glamorous work. OmniPACS made a specific claim when it explained the rebuild: a modern, API-first architecture means new capability can ship in weeks rather than quarters, because a service can be built, tested, and released without waiting on the rest of a decade-old codebase to catch up. That is an easy claim to make in a blog post. It is a harder one to actually back up.
ISO creation on the worklist is the backup. It is the first feature built and shipped since the July 2026 cutover, and it exists in this form because the architecture underneath it made that possible in a way the old PHP application never quite did. Enterprise user management, deeper reporting, an iPad app, and worklist prioritization are all still ahead, still directional, still without a locked date attached to them here. But the pattern only needed to hold once to stop being a claim and start being evidence, and this is that one time.
One Shipped Feature, Not the Last One
None of that changes what a records team deals with day to day. An ISO is still an ISO: a disc image an attorney’s office, a receiving facility, or a patient can open without asking OmniPACS, or anyone else, for help first. What changed is where the work to produce one happens, and how much of a detour it takes out of a day that was already busy before the request came in. Records teams still finishing a rollout, or wondering what else changes once they are fully on Condor, can talk to us about your site’s rollout rather than guess from a description on a page.
That is one shipped feature. It will not be the last one this piece points back to. The next few things on the roadmap are still just a roadmap, but the worklist already proved it can absorb a new capability without anyone needing to leave it to use one. That is worth remembering the next time a vendor promises something is coming eventually.
Frequently Asked Questions
Can you still burn medical images to a CD?
Yes. A recent review of the largest hospital in every U.S. state found most still routinely burn CDs to move imaging between institutions, and DICOM CD creation remains a standard, expected capability in any modern PACS. Legal requests, patient transfers, and records releases are the everyday scenarios that keep the format in active use.
Do patients have a right to get a copy of their imaging records?
Yes. Under HIPAA, patients generally have the right to access and receive a copy of the protected health information a provider holds about them, including diagnostic imaging, in a reasonably requested format. Providers can charge a limited, cost-based fee, and can deny a request only on narrow, specifically defined grounds.
How long does a medical records request take to fulfill?
HIPAA gives covered entities up to 30 days to respond to an access request, with a possible 30-day extension in specific circumstances. That is the legal ceiling, not a target. Departments that can produce imaging directly from the worklist rather than routing it through a separate process often move considerably faster.
What is the proper process for releasing a patient’s imaging to a third party?
A provider first confirms the requester’s identity and authorization, whether that is the patient, a personal representative, or another party with a signed release. Once verified, the imaging is produced in the requested format, logged as a disclosure, and delivered on disc, electronically, or both, depending on what the request specifies.