References ▼
The LEADTOOLS .NET Medical Workstation Framework consists of assemblies and example projects that implement DICOM services. For a description of the assemblies and available example projects, refer to the information below.
Provides classes and methods that implement DICOM Storage Service and DICOM Query/Retrieve Service.
Provides classes and methods that implement DICOM Server Administration.
Provides classes and methods that implement DICOM add-ins. For more information, see the LEADTOOLS DICOM Add-ins section below.
Leadtools.Medical.Storage.AddIns.dll, Leadtools.Medical.Worklist.AddIn.dll, and Leadtools.Medical.Media.AddIn.dll Source Code Only .
Provides classes, methods, properties, events, and fields for the add-ins for the High-level PACS server portion of the Medical Workstation Viewer. For more information, refer to the LEADTOOLS High-level PACS Server Add-ins section below.
All DICOM requests are delegated to the add-ins. Source code is provided for the DLLs.
Provides classes, methods, properties, enumerations and events to implement all the user interface controls (the Viewer control, the Search control, the Configuration control, etc.).
Provides classes, methods, properties, enumerations, events and delegates that can use the add-ins to query the local database, retrieve images from the local database, and store images to the local database.
Provides classes, methods, properties, enumerations and events to create a layer of abstraction between the database provider and the Medical Workstation viewer. This layer is easily customized to allow the Medical Workstation application to use any database or database provider, with minimal code changes.
Provides classes, methods, properties, events, enumerations, and delegates that can be used to retrieve study, series, and image information to load into the medical viewer control.
\Examples\Medical\DotNet\MedicalWorkstationMainDemo
Implements the INotifyReceiveMessage and INotifySendMessages interfaces, which allow the add-in to log all incoming
and outgoing DICOM Messages. The logging is handled by Microsoft Enterprise Library logging. The add-in creates a Log directory in the DICOM server directory.
All log information is written to an "output.log" file. If data set saving is enabled, they are written to Log\Datasets.
The file name of the saved data set is the SOP Instance UID.
Implements the IProcessCStore interface in order to implement a StorageSCP.
The following storage classes are supported:
The following transfer syntaxes are supported:
When the Leadtools.AddIn.Store add-in loads, it creates a new SQLCE 3.5 database (Dicom.sdf) in the server directory. In addition, it creates an Images directory in the server directory that will contain all the DICOM datasets received at the server.
Implements the IProcessCFind interfaces which implement a DICOM Query service. This add-in supports the following service classes:
The Leadtools.AddIn.Find add-in makes use of the same database that is created by the Store add-in. If the database does not exist when this add-in is called
it will be created. Therefore, it does not matter if you attempt a find before doing a store.
Implements the IProcessCMove interface, used to implement a DICOM Retrieve service. It supports the following service classes:
The Leadtools.AddIn.Move add-in makes use of the same database that is created by the Leadtools.AddIn.Store add-in.
If the database does not exist when this add-in is called, it will be created.
Implements the IProcessCFind interface. This add-in supports the following service class:
The Leadtools.AddIn.MWLFind add-in creates a SQLCE 3.5 Database(MWLSCP.sdf) in the server directory.
In addition, it creates an Option Dialog that allows the database to be edited from the Server Manager.
Implements the IProcessNAction interface and supports the following service class:
The Leadtools.AddIn.StorageCommit add-in makes use of the SQLCE 3.5 Database created by the storage add-in. It expects the database to be already created.
If the database is not available the Commitment request will generate a ResourceLimitation error.
If the database is present the commitment request is processed in another thread and a response is immediately sent back to the client.
Once the commit request is finalized a notification is sent on behalf of the add-in to the originating client.
The workstation add-ins include:
Source code is provided for these DLLs.