Connect Weasis to any PACS supporting WADO
weasis-pacs-connector provides the easiest way to launch the Weasis DICOM viewer from a web context (see URL examples) and to connect Weasis to any PACS supporting WADO-URI. If you want to make your own connector without weasis-pacs-connector, follow these instructions.
Note: A simpler configuration without weasis-pacs-connector is possible if the DICOM archive has DICOMWeb services (see examples here).
:heavy_exclamation_mark:As Java Webstart is deprecated, prefer to use the weasis protocol (defined below by the /weasis service) instead of Java Web Start because it has been removed from Java 11 release and because the end of public Oracle Java 8 updates from April 2019. It only works with Weasis 3.5 (or superior) installed on the system with a native installer.
This component gathers different services (:warning: => deprecated):
Service | Description |
---|---|
/weasis | new protocol to launch Weasis with requested images, replacing Java Webstart |
/viewer :warning: | launching Weasis with Java Webstart |
/IHEInvokeImageDisplay | launching Weasis at Patient and Study level, compliant to the IHE IID profile |
/manifest | building the xml manifest (containing the necessary UIDs) consumed by Weasis to retrieve all the images by WADO-URI requests |
/[template] :warning: | (default template: /weasis.jnlp) building a jnlp file from a template (jnlp template path, jnlp properties and jnp arguments can be passed via URL parameters, see the JNLP Builder documentation) |
Prerequisites: JDK 8 and Maven 3
Execute the maven command mvn clean package
in the root directory of the project and get the package from /target/weasis-pacs-connector.war. Official releases are available at here.
Use the loggerless profile for web application container which already embeds slf4j and log4j (like JBoss): mvn clean package -Ploggerless
The /weasis service uses the weasis protocol by redirecting the http://
request into weasis://
(because some web frameworks such as the wiki or the URL field of some browsers only support the standard protocols). It replaces the old /viewer service using Java Webstart.
Note: it is possible to limit the type of UIDs (patientID, studyUID, accessionNumber, seriesUID, objectUID) that can be called from services. See "request.ids" in this configuration file which enables to set which ID is allowed, by default all are allowed.
The Invoke Image Display Profile allows the user of an Image Display Invoker, typically a nonimage-aware system like an EHR, PHR or RIS, to request the display of studies for a patient, and have the display performed by an image-aware system like an Image Display (PACS).
Some Weasis preferences may be overridden in the URL parameters.
Property syntax (key and value must be URL encoded): &pro="key
%20value
"
To add parameters related to the launch configuration and user preferences without weasis-pacs-connector, refer to this page.
When the manifest is built outside weasis-pacs-connector and needs to be transmitted to the viewer.
Build an XML file containing the UIDs of the images which will be retrieved in Weasis. There is an XLS schema to validate the content of xml. This file can be either compressed in gzip or uncompressed. Here are examples:
It requires a web application container like Jetty, Tomcat or JBoss on the server side and an installation of Weasis (native installer) on the client side.
For installation with the dcm4chee user interface, see this page.
Go here and download these following files:
Note: If Weasis is not installed on the server side, the parameter cdb
with no value must be added to the URL (e.g. http://localhost:8080/weasis-pacs-connector/weasis?patientID=9702672&cdb) or the weasis.base.url
property in the weasis-pacs-connector configuration must be commented or set to null.
The default configurations works directly with dcm4chee-arc-light. To override the configuration of weasis-pacs-connector, download weasis-pacs-connector.properties. This file named weasis-pacs-connector.properties and dicom-dcm4chee.properties must be placed in the classpath of the application:
To add properties or arguments at launch, see Launch Weasis with other parameters.
Several archives can be used simultaneously in configuration by defining an archive file in which the property arc.activate
must be true
. Otherwise requires to have the archive ID in the request URL (e.g. http://host?patientID=9702672&archive=1000).
For dcm4chee-arc-light see the installation instructions.
There are different ways to treat the security aspects. Here are some: