The new "unified" licensing type covers all clinic needs at once, dividing access to the Web Viewer into four independent streams:
This is the classic access for your staff specialists — by authorizing in the system with their unique credentials, the user gets access to their personal storage and can connect to PACS servers. It does not depend on other limits, providing guaranteed access to a specific internal user.
An internal user authorizes in the system, gets access to their personal storage, and can connect to PACS servers, but the number of such internal users working simultaneously is limited by the concurrent connections limit in the license — ideally suited for users working in multiple shifts.
An internal user can easily add new DICOM studies to the storage (and then send them to the PACS server) directly from their device. This can be a work computer (for example, if the data is on a CD/DVD) or even a mobile phone, as the system has a web interface.
A universal tool for working without a login and password. Suitable for both issuing results (e.g., through the organization's personal portal account) and for external (remote) users, obtaining a "second opinion", as well as for internal employees using HIS (or another management system) as an interface when searching and opening studies in a continuous workflow. This is an ideal option for scenarios where the functions of a full-fledged workplace are not required (Type 1 and Type 2). The number of such simultaneously opened links is limited by the license quota. If the limit is exhausted, a new user will have to wait for a connection to become available.
This provides guaranteed access to critical studies. A server-signed link will always open, even if all regular quotas (Type 1 and Type 2 or Type 3) are already occupied. It is limited only by the total number of generated signed links (purchased in a pool in multiples of 10,000 units).
You can generate links in three ways depending on the business process:
An internal user working in full mode (Type 1 or Type 2, after authorization by login and password) clicks the "Create link" button directly in the Web Viewer and sends it to a colleague or client.
Your Hospital Information System (HIS) or the organization's personal portal account independently generates the necessary links (for external users, "second opinion", or viewing by a client) in the background by accessing the Web Viewer server.
An external system constructs the link independently simply by substituting study identifiers into an address bar template.
Scenario: An internal user opens a patient's electronic medical record (EMR) in the HIS. The HIS sends an API request to the Web Viewer, passing the studyUid, and instantly receives a link. The internal user clicks the "Open study" button and immediately proceeds to the Web Viewer. Similarly, the HIS can attach these links to reports for external (remote) users.
Scenario: A client authorizes on the organization's portal to view their CT results. The portal server requests an anonymized link (anonymized_link_query) or a link with permission to download the archive (download_link_query) via API. The client views the images directly in the browser or saves them to a local storage device.
Scenario: Upon payment for a service in the accounting system, a study request is generated. After it is conducted, the accounting system saves a direct generated link (formed via URL parameters if link_by_params_policy = allowed) in the rendered service card. This allows staff members to proceed to DICOM data with one click from the accounting system to verify the quality of the rendered service.
Scenario: A background Python script runs in the organization's IT infrastructure. As soon as an employee sends a new study to the PACS, the script captures this event, makes a POST request to the Web Viewer API with the flag "sign": true (to obtain a guaranteed signed link), and automatically sends it to the internal user and/or external user (e.g., the client) via messenger or email along with a text report.
In the administrator panel, license resources are divided into four independent limits covering various IT scenarios.
Provides guaranteed access to a specific user regardless of other limits. Allows using personal storage and connecting to PACS.
Limits the maximum number of internal users (accounts with a login and password) who can work simultaneously in the system. Allows using personal local storage and connecting to PACS. The total number of registered system users can exceed the limit of free connections.
A pool of simultaneous sessions for viewing studies without authorization — via generated URLs. It is used to route studies to external (remote) users, telemedicine consultation organizations ("second opinion"), and to display images in the personal account on the organization's portal.
A strict limit on the generation of tokenized ("signed") links. Opening a signed link ignores the restrictions of concurrent sessions and always guarantees access to the study.
An authorized internal user creates links using the built-in functionality of the Web Viewer: the "Create link" button on the studies panel or in the viewing tab.
POST /api/link)X-Api-Key header or the apikey query parameter.|
|
An object with identifiers (studyUid [required], seriesUid [optional], user / pacsServer [source indication]). |
|
and
|
Optional objects with DICOM metadata (Full name, gender, birth date, accessionNumber, etc.). |
|
|
Link signing flag (creating a priority link). |
anonymized_link_query (without personal data), download_link_query (downloading the archive is allowed), link_query (standard viewing), and the signed status.http(s)://<server_address>/viewer/<image|3d|mpr>?<returned_link_query>Generating links by compiling parameters in the address bar (without a preliminary POST request).
Configuration: Disabled by default. To enable, you must change the link_by_params_policy parameter in the configuration file (renderserverconfig.json).
Allowed policy values: forbidden, anonymized, allowed, download.
URL Syntax: http://<server_name>/viewer/<viewing_mode>?<parameters> (where parameters are user, pacsServer, studyUid, seriesUid).