References ▼
PACS Configuration Demo
This utility application (CSPACSConfigDemo) is provided to help the user quickly configure DICOM connection settings for the various LEADTOOLS PACS Framework client and server demos. The source code for this application is located in the folder: <INSTALLDIR>\Examples\DotNet\PACSFramework\CS\PacsConfigDemo
In order to establish a DICOM communication channel between two applications, both the service provider (i.e. server) and service user (client) must be aware of each other in advance. Each client and server applications should identify themselves using an Application Entity Title or AE Title. Please note that in a local PACS environment an AE Title will uniquely identify an application level service.
DICOM refers to Service Class User (SCU) for an application that requests DICOM services over a network and Service Class Provider (SCP) for an application that provides DICOM services over a network. LEADTOOLS often refers to SCU as a Client and SCP as a Server.
The AE Title is a string of characters containing no spaces and having a length of 16 characters or less. The Host Name/Host Address and Port combine to make up the TCP/IP network address for a listening server application to which a client can connect.
DICOM Server Settings
Main Server: This is the LEADTOOLS PACS Framework Main Server. This server is a provider (SCP/Server) of DICOM query/retrieve, storage, storage commitment, MWL, MPPS and Verification services.
Usage: When the LEADTOOLS PACS Framework Main Server service is running, any configured client application can consume the above-mentioned DICOM services.
Workstation Server: This is the LEADTOOLS Medical Workstation Server, which is a provider of the DICOM storage service for all standard storage objects. The LEADTOOLS Medical Workstation provides a user interface that uses this service to retrieve images from PACS. The Medical Workstation Viewer also uses this service to receive images (unattended) from remote DICOM applications (i.e. PACS pre-fetching or auto routing).
Usage: When the LEADTOOLS Medical Workstation Server service is running, it can receive images from any pre-configured clients. The LEADTOOLS setup will pre-configure the Router Server to forward images to the Medical Workstation Viewer. This service is also used while retrieving images from the PACS Framework Main Server.
Router Server(Deprecated): This is a rules-based auto image router. When it receives an image, it applies the pre-configured rules to evaluate the image and then based on the outcome, it forwards the image to a pre-configured PACS or Workstation server.
Usage: When the Router Server service is configured and running, any images stored to this server will be routed to Medical Workstation Viewer if the object satisfies the pre-configured rule.
Main Client: The same AE title is used to configure multiple client demos, which show the power of various high-level client components of the LEADTOOLS PACS Framework. Once configured, the following demos can be used for the following DICOM services:
DICOM High-level Client - Implements DICOM query/retrieve and storage services.
Usage: Use this demo to query, retrieve and store images (to/from) the PACS Framework Main Server.
DICOM High-level Store - Implements DICOM Storage Service.
Usage: Use this demo to store images to the PACS Framework Main Server.
DICOM High-level MWL SCU - Implements Modality Work-list (MWL) query and Modality Performed Procedure Step (MPPS) Services.
Usage: This demo simulates a typical DICOM modality station. Use this demo to query for Modality Work-list(MWL) data from the PACS Framework Main Server, associate DICOM Images with MWL and MPPS, store the generated images and create Modality Performed Procedure Steps (MPPS) instances on the PACS Framework Main Server.
Print To PACS - Converts print job data to DICOM and performs C-STORE to send the DICOM to a PACS. Uses C-FIND or Worklist Query to gather information necessary to create the DICOM dataset.
Usage: Use this demo to create DICOM datasets from data captured from 3rd party applications and store to PACS.
Workstation Client: This is the client component of the LEADTOOLS Medical Workstation Viewer, which is a full featured DICOM Viewer (2D and 3D), with dynamic DICOM query/retrieve and storage capabilities.
Usage: In addition to image display and 2D/3D manipulations, this application-like demo can be used for querying, retrieving and storing images on the PACS Framework Main Server.
PACS Framework Main Server
The LEADTOOLS PACS Framework Main Server demo uses the LEADTOOLS high level PACS Server Framework as a service application (daemon) and implements the following DICOM Services as a service class provider (SCP / Server):
In addition, the LEADTOOLS PACS Framework Main Server demo also implements the following real-world functionalities
The source code for this application is located in the folders:
All the above-mentioned features and services are implemented using the extensible interface (i.e., add-ins) of the LEADTOOLS PACS Framework. The source code (projects) for all of the above-mentioned add-ins are included with the toolkit for rapid customization (i.e., to meet the requirement of a specific install site or OEM branding).
Workstation Server
The LEADTOOLS PACS Framework Workstation Server demo uses the LEADTOOLS high level PACS Server Framework as a service application (daemon) and implements the following DICOM Services as a service class provider (SCP / Server):
In addition, the LEADTOOLS PACS Framework Workstation Server demo also implements the following real-world functionalities
The source code for this application is located in the folders:
All the above-mentioned features and services are implemented using the extensible interface (i.e., add-ins) of the LEADTOOLS PACS Framework. The source code (projects) for all of the above-mentioned add-ins are included with the toolkit for rapid customization (i.e., to meet the requirement of specific install site or OEM branding).
Router Server(Deprecated)
This demo implements rule based image routing or forwarding to PACS at remote geographic locations. It provides a DICOM Storage service for all standard DICOM
Storage objects and processes images that it receives from clients against pre-configured rules, and then based on the outcome, forwards the images to another pre-configured PACS or Workstation.
A rule script editor is provided to help define custom rules based on source application or attribute value(s) in any DICOM tags in the received object.
The demo also allows secure image forwarding using the TLS security profile of the DICOM standard.
This demo uses the LEADTOOLS PACS Framework and implements the routing and proxy storage via the extensible add-in interface. The source code (projects) for all of the above-mentioned add-ins are included with the toolkit for rapid customization (i.e. to meet the requirement of specific install site or OEM branding) and can be found in the folders:
PACS Components (binary only):
Leadtools.AddIn.StoreProxy.dll
Medical Workstation Viewer
The LEADTOOLS Medical Workstation Viewer implements 2D and 3D image viewing and DICOM communication functionalities that are typical of high-end Medical Workstations, such as radiology reading stations. This demo uses the high-level LEADTOOLS medical display container to provide various display layouts, stacking, cine, synchronized scrolling, reference lines and mouse level tools such as window level, zoom, pan, annotations, measurements and region of interest.
This demo uses the LEADTOOLS 3D engine to allow MIP, VRT and SSD 3D volume generation from 2D CT, MRI and PET stacks. The demo can also generate MPR planes, arbitrary single or double cut planes, and MIP slabs from 2D slices.
It also uses the LEADTOOLS PACS Framework components to dynamically query, retrieve and store DICOM studies to/from PACS. In addition, it runs an unattended application service for supporting the DICOM Storage Service for all Standard SOP Classes. This allows the demo to receive and pre-fetch studies from PACS. The source code for this project is included with the toolkit for rapid customization to meet the requirement of specific install site or OEM branding, and can be found in the folder: <INSTALLDIR>\Examples\DotNet\PACSFramework\CS\MedicalWorkstationMainDemo