LEADTOOLS Medical (Leadtools.Medical.Workstation.Client assembly)
For pointers to sample programs that demonstrate many features, see the following table:
Path | Target Platform |
---|---|
<installdir>\Bin\net | .NET 6+ |
Assembly - Class/Namespace | Comments |
---|---|
Leadtools.Dicom.Scu.dll - Leadtools.Dicom.Scu |
Provides classes and methods that implement DICOM Storage Service and DICOM Query/Retrieve Service. |
Leadtools.Dicom.Server.Admin.dll - Leadtools.Dicom.Server.Admin |
Provides classes and methods that implement DICOM Server Administration. |
Leadtools.Dicom.AddIn.dll - Leadtools.Dicom.AddIn |
Provides classes and methods that implement DICOM AddIns. Leadtools.AddIn.DicomLog -Implements the INotifyReceiveMessage INotifySendMessages interfaces. This allows the add-in to log all incoming and outgoing DICOM Messages. The logging is handled by the 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 dataset saving is enabled they are written to Log\Datasets. The file name of the saved dataset is the SOP Instance UID. Leadtools.AddIn.Store - Implements the IProcessCStore interface. This add-in implements a StorageSCP. The following storage classes are supported:
The following transfer syntaxes are supported:
When the 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. Leadtools.AddIn.Find - Implements the IProcessCFind interfaces. This add-in implements a DICOM Query service. This add-in supports the following service classes:
This 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. Leadtools.AddIn.Move - Implements the IProcessCMove interface. This add-in implements a DICOM Retrieve service. This add-in supports the following service classes:
This 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. Leadtools.AddIn.MWLFind - Implements the IProcessCFind interface. This add-in supports the following service classes:
This add-in creates a SQLCE 3.5 Database(MWLSCP.sdf) in the server directory. In addition, this add-in creates an Option Dialog that allows you to edit the database from the Server Manager. Leadtools.AddIn.StorageCommit - Implements the IProcessNAction interface. This add-in supports the following service classes:
This 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. |
Leadtools.Medical.Workstation.dll - Leadtools.Medical.Workstation | Provides classes, methods, properties, enumerations and events to implement all of the user interface controls (the Viewer control, the Search control, the Configuration control, etc.). |
Leadtools.Medical.Workstation.Client.dll - Leadtools.Medical.Workstation.Client | 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. |
Leadtools.Medical.Workstation.DataAccessLayer.dll - Leadtools.Medical.Workstation.DataAccessLayer |
Provides classes, methods, properties, enumerations and events to create a layer of abstraction between the database provider and the LEADTOOLS 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. |
Leadtools.Medical.Workstation.Loader.dll - Leadtools.Medical.Workstation.Loader | 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. |
NuGet Package | Description | |
Leadtools.Medical.Workstation.dll | This package is unlisted and meant only for advanced users of LEADTOOLS. |
Demo Name | Source Code Path | Description |
---|---|---|
Medical AE Management Data Access Layer | \Examples\Medical\DotNet\Medical.AeManagement.DataAccessLayer\net | Implements the SQL database methods used in interacting with the Application Entity(AE) title. |
Demo Name | Source Code Path | Description |
---|---|---|
Medical Export Layout Data Access Layer | \Examples\Medical\DotNet\Medical.ExportLayout.DataAccessLayer\net | Implements the SQL database methods used in exporting viewer layout. |
Demo Name | Source Code Path | Description |
---|---|---|
Medical Forward Data Access Layer | \Examples\Medical\DotNet\Medical.Forward.DataAccessLayer\net | Implements the SQL database methods used in cleaning and forwarding images to the server. |
Demo Name | Source Code Path | Description |
---|---|---|
Medical HL7 Data Access Layer | \Examples\Medical\DotNet\Medical.HL7.DataAccessLayer\net | Implements the SQL database methods to add and process HL7 messages for the server. |
Demo Name | Source Code Path | Description |
---|---|---|
Medical Options Data Access Layer | \Examples\Medical\DotNet\Medical.Options.DataAccessLayer\net | Implements the SQL database methods that control user and role options for the server. |
Demo Name | Source Code Path | Description |
---|---|---|
Medical Permissions Management Data Access Layer | \Examples\Medical\DotNet\Medical.PermissionsManagement.DataAccessLayer\net | Implements the SQL database methods that manages permissions for server users. |
Demo Name | Source Code Path | Description |
---|---|---|
Medical User Management Data Access Layer | \Examples\Medical\DotNet\Medical.UserManagementDataAccessLayer\net | Demonstrates four implementations for the User Management Access Layer that provides SQL database methods for controlling user access, passwords, privileges, authentication, and verification. |
Demo Name | Source Code Path | Description |
---|---|---|
Find Addin | \Examples\Medical\DotNet\SampleAddIns\AddIn.Find\net | Implements an interface to create and process Find requests. |
Demo Name | Source Code Path | Description |
---|---|---|
Move Addin | \Examples\Medical\DotNet\SampleAddIns\AddIn.Move\net | Implements an interface to create and process Move requests. |
Demo Name | Source Code Path | Description |
---|---|---|
Sample Events Addin | \Examples\Medical\DotNet\SampleAddIns\AddIn.Sample.Events\net | Demonstrates how to handle server events with an example for handling role selection on the BeforeSendAssociateAccept() event. |
Demo Name | Source Code Path | Description |
---|---|---|
Security Addin | \Examples\Medical\DotNet\SampleAddIns\AddIn.Security\net | Implements an interface to manage a server's security and certificate options. |
Demo Name | Source Code Path | Description |
---|---|---|
Storage Commit Addin | \Examples\Medical\DotNet\SampleAddIns\AddIn.StorageCommit\net | Implements an interface to create and process Storage Commit requests. |
Demo Name | Source Code Path | Description |
---|---|---|
Dicom Communication Logging Addin | \Examples\Medical\DotNet\SampleAddIns\Configuration.Logging\net | Implements a logging channel interface to be loaded in the global logging channels of the DICOM service. |