Software Vendors & OEMs
Ready to integrate web DICOM PACS Viewer and connectivity solutions
DICOM VIEWER
INTEGRATION INTO
OPEN SOURCE
MedDream is HTML5 zero-footprint DICOM Viewer for PACS server that is aimed at making diagnoses, viewing, archiving and transmitting medical images. The DICOM Viewer can be integrated into any PACS server/VNA and open source, such: PacsOne PACS, dcm4chee, Orthanc Server, Conquest DICOM Software, ClearCanvas, Google Cloud Healthcare, Azure Health Data Services, etc.





The MedDream DICOM Viewer ensures a prompt and reliable way to search, view, analyze and diagnose medical images, signals and video files from anywhere and on any device. DICOM Viewer is web-based and developed using responsive design, that enables medical images to be accessed not only on computers, but also on tablets, smart phones or other devices with mobile view functionality.
MedDream is FDA cleared for diagnostic use and is CE Class IIb certified as a medical device that can be used for review purposes or even primary diagnosis. Read more about MedDream certifications.
As a diagnostic image viewer, MedDream consists of a Viewer component, which runs in a browser and does not require any installation on the client device, and a MedDream application server, which handles communication with the hospital systems (HIS/RIS/PACS/VNA and any other EMR) and prepares images for streaming to the MedDream DICOM Viewer.
MedDream, as an open source friendly DICOM Viewer, uses a flexible and open integration interface for connecting to HIS and/or EMR systems primarily based on URL calls, thus allowing it to be integrated into any medical application.

Integration of the web DICOM Viewer:
URL link examples for DICOM Viewer integration into Information System:
The MedDream DICOM Viewer supports the following DICOM files and formats: Implicit Little Endian, Explicit Little Endian, JPEG, JPEG-LS, JPEG 2000, RLE, MPEG-2 and MPEG-4 Transfer Syntaxes:
The html5 zero-footprint DICOM Viewer, MedDream, can be integrated into any PACS system/VNA including: MedDream PACS, PacsOne PACS Server, Orthanc PACS, open-source: dcm4chee PACS, Conquest DICOM Software, ClearCanvas, etc. MedDream also can be integrated into cloud DICOM services: Google Cloud Healthcare, Azure Health Data Services, Amazon AWS S3 storage, AWS HealthImaging, etc.
Available versions of the DICOM Viewer:
The MedDream DICOM Viewer also supports MultiPACS by PACS plugins: dcm4chee v2, dcm4chee v5, Orthanc, PacsOne, DICOM QueryRetrieve, FileSystem.
Watch the video tutorial about multi storage support:
The MedDream application server connectivity to the PACS can be achieved using:
Depending on each specific installation, the preliminary hardware sizing information may vary slightly based on the modalities used in the institution. The minimum hardware requirements for the MedDream Application Server are described in Minimal server side requirements page.
For more information about DICOM Viewer integration, please read more about the MedDream WEB DICOM Viewer.
Is the MedDream DICOM Viewer an open-source product?
+No, MedDream is a commercial, certified medical device. However, it is highly ‘open-source friendly’ and explicitly engineered as a vendor-neutral viewer designed to integrate seamlessly with popular open-source PACS archives.
Are open-source viewers safe for clinical diagnosis?
+Free, fully open-source viewers generally lack FDA clearance or CE certification, making them legally unsafe for primary diagnosis. Integrating MedDream ensures the viewing component of your stack meets all legal and regulatory medical device standards.
Which open-source PACS servers work with MedDream?
+MedDream provides native compatibility and robust integration with leading open-source image management systems, including dcm4chee (v2 and v5), Orthanc PACS, PacsOne, Conquest DICOM Software, and ClearCanvas.
Why pair a commercial viewer with an open-source PACS?
+Pairing an open-source PACS (for cost-effective storage) with the commercial MedDream viewer provides hospitals with FDA-cleared and CE-certified diagnostic visualization tools, bridging the gap between free archiving and compliant clinical diagnosis.
How does MedDream integrate with Orthanc and dcm4chee?
+MedDream connects to Orthanc, dcm4chee, and other archives via standard DICOMweb protocols (WADO-RS, QIDO-RS), direct database/file system access, or specialized Gateway PACS plugins to ensure rapid image retrieval and streaming.
Which open-source PACS servers are compatible with MedDream DICOM Viewer?
+As a vendor-neutral viewer, MedDream connects with popular open-source PACS solutions including dcm4chee, Orthanc, PacsOne, Conquest, and ClearCanvas, as well as proprietary commercial PACS and VNAs.
Is there a web DICOM viewer compatible with open-source PACS like Orthanc or dcm4chee?
+Yes. MedDream acts as a universal viewer and supports ready-to-use integrations with popular open-source image management systems, including Orthanc PACS, dcm4chee (v2 and v5), PacsOne, Conquest, and ClearCanvas, or any other open-source archives which support: DICOMweb, WADO RESTful services (QIDO-RS, WADO-RS, WADO-URI), DICOM Q/R on Study Level (C-FIND, C-MOVE, C-STORE) or other integration options.
Does the viewer support Multi-PACS environments?
+Yes. A single MedDream application server can simultaneously query and visualize DICOM studies from multiple disparate open-source and proprietary PACS servers, creating a unified enterprise visualization portal.
Do I need to migrate data from my open-source PACS?
+No data migration is required. MedDream functions as a zero-footprint web layer that queries and streams images directly from your existing open-source repository without altering the underlying archive structure.
Can developers customize the MedDream UI for open-source projects?
+Yes, MedDream offers a flexible open integration API and white-labeling capabilities. Developers can customize the graphical user interface, color schemes, and system name to match their custom open-source healthcare platforms.
What DICOM file formats and transfer syntaxes are supported by MedDream?
+MedDream is highly versatile, supporting a wide range of transfer syntaxes including Implicit Little Endian, Explicit Little Endian, JPEG, JPEG-LS, JPEG 2000, RLE, MPEG-2, and MPEG-4. Users can also export studies to portable DICOM formats or save them locally as JPEG, TIFF, or MP4 files.
What are the hardware requirements to run the MedDream Application Server?
+Because MedDream relies on a zero-footprint client architecture (client-side rendering), the end-user device requires no special hardware – only a modern web browser. The MedDream Application server requires very minimal server-side hardware, which scales dynamically depending on number of the studies opened at the time, making it highly resource-efficient compared to heavy client-side applications.
For more information read: Minimal Server-Side Requirements page.
How does URL token integration work with EMRs?
+MedDream uses a flexible URL-based integration interface. Developers can embed the viewer into open-source EMRs (like OpenEMR) by passing secure URL calls containing a Study UID, Patient ID, or Accession Number to instantly launch patient images.
Is client-side rendering utilized for open-source PACS?
+Yes, MedDream leverages advanced client-side rendering and HTML5 streaming. This optimizes performance by offloading heavy image processing to the client’s web browser, minimizing the bandwidth and processing load on the open-source server.