Teleradiology Network Diagram
Teleradiology lets a remote group read studies overnight, at weekends or for subspecialty work. This diagram shows the standard connection between a hospital and a teleradiology provider: the hospital PACS auto-routes studies to a DICOM router, which sends them over a site-to-site VPN to the provider’s PACS; the remote radiologist reads there, and the report returns to the hospital RIS over HL7.
Free, no sign-up. The builder runs in your browser; nothing is uploaded.
What this diagram shows
Both sides of the link are on one page, which makes it a useful attachment for the security review and interface specification that every teleradiology contract needs.
Components
Hospital modalities and PACS
Acquire and store images as usual.
DICOM router
Applies routing rules (time of day, modality, priority), compresses where agreed, and forwards studies plus relevant priors to the provider.
Firewall / VPN
Site-to-site IPsec tunnel, or DICOM over TLS, limited to the router’s and provider’s hosts and ports.
Teleradiology PACS
The provider’s archive and reading worklist.
Remote reader
Radiologist workstation at the provider, often in another time zone.
Hospital RIS and provider reporting
Exchange orders (ORM) and final reports (ORU) so the report lands in the hospital record.
How the data flows
Acquire and store
The modality sends images to the hospital PACS with C-STORE.
Route
PACS forwards qualifying studies to the router, which adds relevant priors.
Transmit
The router sends studies over the VPN to the provider PACS with C-STORE, using lossless compression where both sides support it.
Order context
The hospital RIS sends ORM orders so the provider has history, reason for exam and the accession number.
Read and report
The remote radiologist reads and reports; the signed report returns as ORU^R01 to the hospital RIS and on to the EHR.
Interfaces in this diagram
Every connection in the diagram, ready to copy into an interface register or test plan.
| # | From | To | Protocol | Detail |
|---|---|---|---|---|
| 1 | Modalities (Hospital) | →PACS (Hospital) | DICOM | C-STORE |
| 2 | PACS (Hospital) | →DICOM Router (Rules · Compress) | DICOM | Auto-route |
| 3 | DICOM Router (Rules · Compress) | →Firewall / VPN (Site-to-site) | DICOM | C-STORE |
| 4 | Firewall / VPN (Site-to-site) | →Telerad PACS (Provider) | VPN | IPsec / TLS |
| 5 | Telerad PACS (Provider) | →Remote Reader (Radiologist) | WADO-RS | — |
| 6 | RIS (Hospital) | ↔Telerad Reporting (Provider RIS) | HL7 | ORM · ORU |
Design considerations
- Agree which patient identifier and accession number come back in the ORU, or reports will fail to match.
- Send priors with the current study — remote readers cannot query your archive unless you allow it.
- Restrict the VPN to specific hosts and ports, and log every DICOM association for audit.
- Monitor end-to-end turnaround (acquisition to report received), not only network transfer time.
- Plan for provider downtime: decide who reads if the link or the provider is unavailable.
Related reference
Frequently asked questions
How does teleradiology work technically?
Images are routed from the hospital PACS to the teleradiology provider over a secure link (VPN or DICOM over TLS). The provider’s radiologists read them in their own PACS and send the report back to the hospital RIS over HL7, where it is matched to the original order.
Is a VPN required for teleradiology?
Patient data must be encrypted in transit. A site-to-site IPsec VPN is the most common approach; DICOM over TLS and secure cloud gateways are alternatives. Whichever you use, restrict access to the specific systems involved.
Should images be compressed for teleradiology?
Lossless compression (for example JPEG 2000 lossless or JPEG-LS) reduces transfer time without affecting diagnostic quality. Lossy compression should only be used where the reading radiologists and local regulations accept it.
Make it match your site
Rename systems, add your AE titles and message types, then export PNG, SVG or PDF — or send a colleague a share link.