DICOMWeb Import

How to configure DICOMWeb node

This page explains how to configure DICOMWeb nodes in Weasis for retrieving images remotely. While manual configuration in Weasis is covered here, you can also launch Weasis from a web context with automatic DICOMWeb parameters derived from the URL.

General Configuration Steps

  1. Open File > Preferences (Alt + P)
  2. Select “DICOM node list” from the left sidebar
  3. Click the “Add new” button to create a new node or select an existing one and click “Edit”

DICOMWeb nodes configuration DICOMWeb nodes configuration


Here are the steps for configuring a new DICOMWeb node:

  1. Create a new DICOMWeb node with a descriptive name
  2. Select one of the service types. The default one is DICOMWeb (all RESTful services) which covers all DICOMWeb services. If you want to use a specific service, select the corresponding one:
    • QIDO-RS: Query
    • STOW-RS : Store
    • WADO-URI (non-RS): legacy retrieval for one DICOM object (combines C-Find and WADO retrieve from query/retrieve)
    • WADO-RS (Retrieve): Retrieve
  3. Enter the service URL of the DICOMWeb server.
  4. Configure authentication by clicking the “Manager” button and then “Add”:
    • Either select a template from the list and click “Fill” to autofill some fields or fill them manually.
    • In the Provider panel, all the fields are mandatory.
    • In the Registration panel, the fields are optional. However, if you want to use the OAuth2 authentication, you need to fill in the Client ID, Client Secret, and the Scope. Audience is not mandatory but can be useful for some specific providers.
    • Click “OK” to save the authentication
  5. Optionally, add HTTP headers for the service URL. This can be used for authentication or other purposes.
  6. Click “OK” to save the authentication

Then open the DICOM Import dialog and select the node just created. You can now query the DICOMWeb server after logging in with your account into your browser when using OAuth2 authentication.

Supported DICOMWeb Providers (non-exhaustive list)

Google Cloud Healthcare API

Google Cloud provides a comprehensive DICOMWeb implementation through their Healthcare API.

Configuration steps:

  1. Create a new DICOMWeb node with a descriptive name
  2. Select DICOMWeb (all RESTful services)
  3. Enter the Google repository URL (must end with /dicomWeb)
  4. Configure authentication by clicking the Manager button and then Add:
    1. Select “Google Cloud Healthcare” template
    2. Click “Fill”
    3. Enter your Client ID and Client Secret
    4. Click “OK” to save the authentication
  5. Optionally, add HTTP headers for the Google API
  6. Click “OK” to save the authentication

Google node Google node


Google template Google template

Note

Currently, the DICOMWeb service for getting thumbnails doesn’t work in the Google API.

Orthanc WEB Server

Orthanc is a lightweight DICOM server with DICOMWeb capabilities.

The configuration in the image below is for the demo server without authentication. For a custom Orthanc server, you need to enter the URL of your Orthanc server and define the authentication method (see above).

https://demo.orthanc-server.com/dicom-web

Orthanc node Orthanc node


Note

Currently, the DICOMWeb service of Orthanc doesn’t support the thumbnail service.

dcm4chee-arc-light

dcm4chee-arc-light is a robust open-source Picture Archiving and Communication System (PACS) that supports DICOMWeb services.

To configure a dcm4chee-arc-light node:

  1. Add a new DICOMWeb node
  2. Enter a description (e.g., “DCM4CHEE Archive”)
  3. Select DICOMWeb service
  4. Enter the URL of your dcm4chee-arc-light server. The default endpoint typically follows this pattern: 
    http(s)://[server-address]:[8080|8443]/dcm4chee-arc/aets/[AE_TITLE]/rs (e.g., http://localhost:8080/dcm4chee-arc/aets/DCM4CHEE/rs)

If authentication is required in dcm4chee-arc-light, here are the steps to configure it for client access in Weasis:

In Weasis:

  1. Click on the Manager button
  2. Click Add to create a new authentication
  3. Select “Default Keycloak” from the templates and fill in the other required fields:
    • Name: dcm4chee-arc-light
    • Base URL: https://[server-address]:8843
    • Realm: dcm4che
    • Client ID: weasis
    • Client Secret: the secret you copied from Keycloak, see below
    • Scope: openid
    • Audience: leave empty

In Keycloak: Add the Weasis client for DICOMWeb access:

  1. Log in to the Keycloak Admin Console (typically for secure at https://[server-address]:8843/admin/dcm4che/console)

  2. To add the Weasis client:

    • Click on “Clients” in the left menu
    • Click the “Create” button

  3. Configure the new client in general settings:

    • Client Type: select “OpenID Connect”
    • Client ID: weasis

  4. Capability config:

    • Client authentication: ON
    • Standard flow: ON
    • Direct access grants: ON

  5. Login settings:

    • Root URL: leave empty
    • Valid Redirect URIs: add http://127.0.0.1*
    • Web Origins: add + to allow any origin that matches a Valid Redirect URI
    • Click “Save”
    • Copy the Client Secret from the “Credentials” tab

Amazon HealthLake

Amazon HealthLake is a fully managed service that enables healthcare organizations to store, transform, query, and analyze health data at scale.

With AHI DICOMWeb Proxy you can use the DICOMWeb API to access your data in Amazon HealthLake. Simply create a DICOMWeb node in Weasis with the following URL: 

http://[EC2 instance IP or EC2/ALB DNS]:8080/aetitle

See also the Weasis configuration at the end of this page.