integrations

This page details some integrations of dwv. These PACS integrations use the Web Access to Dicom Object (WADO-URI) protocol (see conformance). The PACS handles the searching and once the data is found allows the user to launch the viewer.

Quick summary: Orthanc ✅, Google ✅, Conquest ✅, dcm4chee ✅

Other type: WordPress ✅

Orthanc

Orthanc: "Orthanc aims at providing a simple, yet powerful standalone DICOM server. Orthanc can turn any computer running Windows or Linux into a DICOM store (in other words, a mini-PACS system). Its architecture is lightweight, meaning that no complex database administration is required, nor the installation of third-party dependencies." (entry on idoimaging). License: GPL (see Licensing on the download page).

Follow the steps described on the dwv-orthanc-plugin page.

Operational since dwv v0.8.0beta and issue #110.

DICOM-web support since v0.31.0. Check it using this example 'unsafe' dicom web configuration (json):

{
  "Name": "${ORTHANC_NAME} in Docker Compose",
  "RemoteAccessAllowed": true,
  "Plugins": ["/usr/local/share/orthanc/plugins"],
  "DicomWeb": {
    "Servers": {
      "self": {
        "Url": "http://localhost:8042/dicom-web/",
        "Username": "orthanc",
        "Password": "orthanc",
        "HasDelete": true
      }
    }
  },
  "ServeFolders": {
    "/dwv": "/usr/local/dwv"
  }
}

DWV is served via the ServeFolders to allow it to request files (and not create CORS errors). This configuration is then passed (as orthanc-config.json) to the folowing example docker compose (yaml):

version: "3.1"
services:
  orthanc:
    image: jodogne/orthanc-plugins:1.9.7
    command: [/run/secrets/, --trace-dicom]
    ports:
      - 4242:4242
      - 8042:8042
    secrets:
      - orthanc.json
    environment:
      - ORTHANC_NAME=OrthancTest
    volumes:
      - /home/yves/dev/src/github/dwv:/usr/local/dwv
secrets:
  orthanc.json:
    file: orthanc-config.json

Adapt this to the folder containing the dwv code under the volumes setting.

Launch it with: sudo docker-compose up

You can then access orthanc at explorer. DWV provides a test page to do QIDO and launch the viewer: dcmweb (do not forget to modify the test viewer for it to set the multipart header with the _dicomWeb flag).

Google

Available via the dwv-jqmobile project.

  • Google Drive web: right click on a DICOM file and choose Open with. DWV should appear in the Suggested apps, if not, choose Connect more apps, search for 'dwv' and connect it (see managing drive apps for details)
  • Google Chrome store: dwv app (see the chrome apps help for details)

Conquest

Conquest: "a full featured DICOM server based on the public domain UCDMC DICOM code" (entry on idoimaging). License: Public Domain (see medfloss).

Tested version: 1.4.17. See this thread on the Conquest forum and the issue #15. Operational since dwv v0.3.0, available in the dwv-jqmobile, dwv-jqui and dwv-simplistic demos.

To setup DWV, follow the instructions written in the lua files of the respective demos resources/scripts folder.

Conquest installation details:

  • Under Fedora 18: install under ubuntu linux after installing apache
    • the g++ fedora package is called gcc-c++
    • the cgi-bin folder is in /var/www
    • launching services is done using systemctl: for example systemctl start httpd.service and systemctl start mysqld.service
  • Under Windows7:
    • using wamp5 (install as admin, see forum), the cgi bin folder is in wamp/bin/apache/apache##/cgi-bin
    • to launch the PACS: start the wamp service and run the ConquestDICOMServer.exe, you can then access the web interface at http://127.0.0.1/cgi-bin/dgate.exe?mode=top.

Dcm4chee

dcm4che: "DICOM archive and image manager, forming the server side of a PACS system" (entry on idoimaging). License: GPL (see license).

Follow the steps described on the dwv-dcm4chee-web page.

Operational since dwv v0.7.0 and issue #1.

WordPress

See dicom-support plugin and a demo.