What sharing an imaging study really means
Medical image sharing sounds like one thing and is really several. A study, the DICOM images plus the report, gets acquired in one place and then has to reach other people: the referring physician who ordered it, the patient who wants a copy, another facility taking over care, or a reading service doing the interpretation. The study does not change as it moves. What changes is who can open it, how they get in, and who still holds the authoritative copy afterward. Getting those three right is the whole job.
It helps to name the parties, because each wants something slightly different. A referring doctor wants to see the study and its status without chasing anyone. A patient wants their images in hand for a second opinion. A receiving facility wants the study loaded into their own PACS so it reads like any other. A teleradiology service wants the study pushed to wherever the interpreting radiologist sits. One method rarely serves all four well, which is why several coexist.
The methods, and where each one is going
There are five common ways a study gets shared, and they are not equal. The oldest is the physical disc, a CD or DVD burned at the front desk. It still happens, and it is dying for good reasons: discs get lost, arrive scratched, need a viewer the receiving machine may not run, and carry no audit trail once they leave the building. A patient walking a disc between clinics is a workflow nobody designed on purpose.
The rest are online. A patient portal gives the patient a login to view or download their own studies. A link-based share sends a recipient a controlled link to a single study, usually with access rules and an expiry so it does not stay open forever. Direct DICOM transfer moves the study machine to machine between two facilities over the standard imaging protocols, or serves it on request through query and retrieve, so the study lands directly in the receiving PACS. A cloud image exchange does the same across many organizations at once, acting as a shared broker between them.
| CD/DVD or third-party portal | Self-hosted PACS + referral portal | |
|---|---|---|
| How the study travels | Burned to disc or uploaded to an outside service | Served from your own archive, or pushed by DICOM |
| Who holds the source copy | Ambiguous; copies scatter as discs and uploads pile up | Your archive stays authoritative; recipients get access |
| Referring doctor access | Wait on a disc, or a login to someone else's system | Log in to the referral portal for study and status |
| Access control and expiry | None on a disc; varies on a third-party portal | Controlled access, on your terms and your audit log |
| Ongoing cost model | Media and handling, or per-study cloud fees | Fixed cost of the server you already run |
The direction of travel is clear enough. Discs are being retired, and sharing is moving to online methods that leave a record of who accessed what. The open question for any given facility is not whether to go online but which online method fits: a portal for referrers, DICOM transfer between facilities, or a cloud exchange when the sharing crosses many organizations.
The concerns that actually decide it
Three concerns sit underneath every sharing decision, and they matter more than which button gets clicked. The first is PHI and HIPAA handling. Any time a study moves, protected health information moves with it, so the channel has to be one the facility can stand behind rather than casual email or an unmanaged upload. The specifics of what any given tool does for HIPAA belong in that tool's own documentation; for MiniPACS, the in-page HIPAA note in the modal is the place to check, not an overclaim on a marketing page.
The second is keeping the sender's archive as the source of truth. Sharing should extend access to a study, not fragment the only copy of it. The safe pattern is that the acquiring facility keeps the authoritative study under its own backups and audit log, and the recipient gets access or a working copy. That keeps retention and accountability in one place instead of spread across other people's systems.
The third is access control and expiry. A share that never closes is a slow leak. Good sharing scopes who can open a study, for how long, and records it, so access can be reasoned about after the fact rather than assumed. These three concerns are why a disc, which fails all three, keeps losing ground to online methods that can meet them.
Where MiniPACS fits, and where it does not
MiniPACS is a self-hosted PACS, so its answer to sharing is grounded in two things rather than a consumer app. The first is the Vendo referral portal, where referring doctors send orders online and then access the resulting studies and their status without a disc or a phone call. That covers the most common sharing relationship a practice has, the one with the doctors who send it work. See referral management software for how that portal side works.
The second is standard DICOM transfer between facilities. Because MiniPACS speaks DICOM, studies move to and from other imaging systems over the same protocols everything else in imaging uses, and the study stays archived at the source. That is the honest scope: a self-hosted archive plus a referral channel plus standard DICOM sharing. What it is not is a branded patient-facing consumer image-sharing app, and it would be wrong to imply one. If that specific product is the requirement, a PACS is not it.
Choosing a sharing approach
- Name the party first. Referrer, patient, facility or reading service; each is best served by a different method, so decide who you are sharing with before you pick how.
- Prefer online over discs. A portal or DICOM transfer beats a burned disc on access control, audit and reliability. Discs are the fallback, not the plan.
- Keep the source authoritative. Confirm the method extends access rather than handing out the only copy, and that your archive stays the system of record.
- Check access control and expiry. A share should scope who gets in and for how long, and leave a record. A link that never closes is a liability.
- Mind the HIPAA channel. Move PHI on a channel you can stand behind. For MiniPACS specifics, read the in-page HIPAA note rather than assuming.
For how the archive itself works, see what is PACS. For where studies get hosted, weigh cloud vs onsite. For remote reading specifically, see teleradiology. For the referrer channel, see referral management software.
FAQ
What is medical image sharing?
Medical image sharing is moving an imaging study, the DICOM images and the report that goes with it, from the place that acquired it to whoever else needs to see it: a referring physician, the patient, another facility, or a reading service. The study itself does not change. What changes is who can open it and how. The methods range from burning a physical disc to a patient portal, a link to a single study, a direct DICOM transfer between two facilities, or a cloud exchange that sits between many of them.
Is emailing or texting a medical image to a patient allowed?
That is a HIPAA question rather than a technical one, and the honest answer is that it depends on how it is done, what safeguards are in place, and what the patient has been told. Casual email or text of protected health information carries real exposure, which is why most facilities move sharing onto controlled channels with access control and an audit trail instead. For how MiniPACS treats HIPAA specifically, see the HIPAA note in the in-page modal rather than a blanket claim here.
How do facilities share images without burning a CD?
The two durable answers are a portal and direct DICOM transfer. A portal, such as a referral portal, lets a referring doctor log in and open the study and its status online instead of waiting on a disc. Direct DICOM transfer moves the study machine to machine between two facilities over the standard imaging protocols, or serves it on request through query and retrieve. Cloud image exchanges do the same job across many organizations at once. All three avoid the disc, and all three keep a record of who accessed what.
Does MiniPACS have a consumer image-sharing app?
No, and it would be dishonest to imply otherwise. MiniPACS is a self-hosted PACS, and sharing centers on two things: the Vendo referral portal, where referring doctors send orders online and access studies and status, and standard DICOM transfer between facilities. There is no separate patient-facing consumer sharing product being claimed here. If your requirement is a self-hosted archive plus a referral channel, that is the fit; if you specifically need a branded consumer app, a PACS is not that.
Who keeps the original study when it is shared?
The safe model is that the sender's archive stays the source of truth. When a study is shared through a portal or a DICOM transfer, the acquiring facility still holds the authoritative copy under its own backups and audit log; the recipient gets access or a copy for their own use. This matters because it decides who is accountable for retention and who can hand the archive back if a relationship ends. Sharing should extend access to a study, not scatter the only copy of it across other people's systems.