// blog

How to View a PACS From a Web App: Three Ways to Connect

There are three common ways to show PACS images in a web app: call the archive’s own DICOMweb services (QIDO-RS, WADO-RS) through your back end and show them in a browser viewer such as the open-source OHIF; put a gateway in front of an archive that only speaks classic DICOM networking, for example an Orthanc server with its DICOMweb plugin; or launch the PACS vendor’s own web viewer with a link. Whichever you choose, keep the archive off the internet and let your back end handle sign-in and access.

Last updated 2 min read

View a PACS from a web app: a PACS speaking DIMSE, a gateway or plugin, and a browser receiving DICOMweb over HTTPS

A referral portal, a research tool, a patient app: sooner or later a web project needs images that live in a hospital’s PACS. DICOMweb vs classic DICOM covered the protocols. This is how to wire it up.

Way 1: the archive’s own DICOMweb

Many current archives offer DICOMweb. Then:

text
browser viewer  →  your back end (HTTPS, sign-in, access checks)  →  PACS DICOMweb
  • Your back end searches with QIDO-RS and retrieves with WADO-RS, passing on only what the user may see.
  • The browser shows it in a viewer: your own, or an open-source one such as OHIF (MIT license), which speaks DICOMweb natively.

Cleanest option, if the archive supports it and the hospital lets you use it.

Way 2: a gateway in front of a DIMSE-only archive

Older archives only speak classic DICOM networking (C-FIND, C-MOVE). Put a gateway between them and your app:

text
browser  →  your back end  →  gateway (DICOMweb)  ⇄  PACS (DIMSE)
  • An archive as gateway: an Orthanc server, for example, with its DICOMweb plugin (WADO-URI, WADO-RS, STOW-RS, QIDO-RS), receives studies from the PACS and serves them over DICOMweb. Note the plugin’s AGPL license.
  • Your own service that runs C-FIND and C-MOVE or C-GET with a DICOM library (DCMTK’s findscu, movescu and getscu show the calls) and exposes what your app needs.

The gateway also needs an AE title the PACS knows, so C-MOVE can deliver to it.

Way 3: launch the vendor’s viewer

Most PACS vendors have a web viewer that opens a study from a link. Your app finds the study and opens the vendor’s viewer with it. Little to build, but the look, the features and the sign-in are the vendor’s.

Whichever you choose

  • Keep the PACS off the internet. Only your back end talks to it, over the hospital’s network or a VPN.
  • Check access per study on the server, every time.
  • Fetch what you show: one series, or single frames, not whole studies.
  • Mind the encoding. Browsers can’t decode JPEG lossless, JPEG 2000 or JPEG-LS themselves; have the server deliver an encoding the viewer can show, or use a viewer that brings its own decoders, as ours does for JPEG lossless and JPEG 2000.
  • Log every view for the audit trail.

Key takeaways

  • DICOMweb archive: your back end in front, a browser viewer like OHIF on top.
  • DIMSE-only archive: a gateway (an Orthanc server, or your own service) translates.
  • To try DICOMweb from a browser first, open a study from a PACS in our free viewer.
  • Vendor viewer launch: quickest, least control.
  • Never expose the PACS; check access on the server; fetch only what you show.

We’re glad to share what we know. When you want your web app connected to a PACS, we’ll put all of it to work on your project, and because we build with AI-assisted development, it costs far less than you might expect. Let’s talk.

Frequently asked questions

Can the browser call the PACS directly?

For an app that many people use, better not: put your own back end in between, to sign users in, check which studies each one may see and keep the archive's address and credentials off the internet. For staff looking at their own archive, a browser viewer can ask the PACS directly with the PACS's own login, as our free DICOM viewer does.

Do I need to copy the images into my own system?

Not usually. A viewer can read from the archive on demand. A cache helps for speed, but keep one source of truth.

What about licenses?

Check each component. For example, OHIF's viewer is MIT-licensed, while the Orthanc DICOMweb plugin is AGPL, which has obligations if you change it and offer it over a network.

Sources

  1. OHIF Viewers on GitHub (MIT)
  2. Orthanc DICOMweb plugin README (AGPL; WADO-URI, WADO-RS, STOW-RS, QIDO-RS)
  3. DICOM PS3.18: Web Services (DICOMweb)