LEADTOOLS Medical (Leadtools.Medical.Workstation.Loader assembly)
For pointers to sample programs that demonstrate many features, see the following table:
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 Add-ins. 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.AddIns.dll - Leadtools.Medical.Workstation.AddIns |
Provides classes, methods, properties, events, and fields for the AddIns for the High-Level PACS server portion of the Medical Workstation Viewer. All DICOM requests are delegated to the add-ins. The workstation add-ins include:
|
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. |
Library | Description | Dependencies |
---|---|---|
Leadtools.Medical.Workstation.Loader.dll | Core Library |
Leadtools.dll |
NuGet Package | Description | |
Leadtools.Medical.Workstation.dll | This package is unlisted and meant only for advanced users of LEADTOOLS. |
Name | Path | Description |
---|---|---|
Customizing Worklist DAL Demo | \Examples\Medical\DotNet\CustomizingWorklistDAL | Demonstrates how to customize the Modality Worklist Database used by the DICOM MWL demos.
|
DataAccessLayers | \Examples\Medical\DotNet\DataAccessLayers | |
DataAccessLayers.Core | \Examples\Medical\DotNet\DataAccessLayers.Core | |
Dicom.Server.Manager | \Examples\Medical\DotNet\Dicom.Server.Manager | |
DICOM High Level Client Demo | \Examples\Medical\DotNet\DicomHighlevelClientDemo | Demonstrates implementation of a DICOM client.
|
DICOM High Level MWL SCU Demo | \Examples\Medical\DotNet\DicomHighLevelMWLScuDemo | Demonstrates creating a DICOM Modality Worklist SCU example that will query a MWL SCP for a worklist and copy data from the MWL response attributed to the requested IOD class. |
DICOM High Level Patient Updater Demo | \Examples\Medical\DotNet\DicomHighlevelPatientUpdaterDemo | Demonstrates updating existing patient information in the Storage Server database using custom DICOM N-ACTION commands. |
DICOM High Level Storage SCU Demo | \Examples\Medical\DotNet\DicomHighlevelStoreDemo | Demonstrates implementation of a DICOM storage client (SCU).
|
Medical.Ae.Configuration | \Examples\Medical\DotNet\Medical.Ae.Configuration | |
Medical.AeManagement.DataAccessLayer | \Examples\Medical\DotNet\Medical.AeManagement.DataAccessLayer | |
Medical.AutoCopy.AddIn | \Examples\Medical\DotNet\Medical.AutoCopy.AddIn | |
Medical.ExportLayout.AddIn | \Examples\Medical\DotNet\Medical.ExportLayout.AddIn | |
Medical.ExportLayout.DataAccessLayer | \Examples\Medical\DotNet\Medical.ExportLayout.DataAccessLayer | |
Medical.ExternalStore.Addin | \Examples\Medical\DotNet\Medical.ExternalStore.Addin | |
Medical.ExternalStore.AmazonS3.Addin | \Examples\Medical\DotNet\Medical.ExternalStore.AmazonS3.Addin | |
Medical.ExternalStore.Atmos.Addin | \Examples\Medical\DotNet\Medical.ExternalStore.Atmos.Addin | |
Medical.ExternalStore.Azure.Addin | \Examples\Medical\DotNet\Medical.ExternalStore.Azure.Addin | |
Medical.Forward.AddIn | \Examples\Medical\DotNet\Medical.Forward.AddIn | |
Medical.Forward.DataAccessLayer | \Examples\Medical\DotNet\Medical.Forward.DataAccessLayer | |
Medical.Gateway.AddIn | \Examples\Medical\DotNet\Medical.Gateway.AddIn | |
Medical.HL7.DataAccessLayer | \Examples\Medical\DotNet\Medical.HL7.DataAccessLayer | |
Medical.HL7MWL.AddIn | \Examples\Medical\DotNet\Medical.HL7MWL.AddIn | |
Medical.HL7PatientUpdate.AddIn | \Examples\Medical\DotNet\Medical.HL7PatientUpdate.AddIn | |
Medical.License.Configuration | \Examples\Medical\DotNet\Medical.License.Configuration | |
Medical.Logging.AddIn | \Examples\Medical\DotNet\Medical.Logging.AddIn | |
Medical.Media.AddIns | \Examples\Medical\DotNet\Medical.Media.AddIns | |
Medical.Options.DataAccessLayer | \Examples\Medical\DotNet\Medical.Options.DataAccessLayer | |
Medical.PatientRestrict.AddIn | \Examples\Medical\DotNet\Medical.PatientRestrict.AddIn | |
Medical.PatientUpdater.AddIn | \Examples\Medical\DotNet\Medical.PatientUpdater.AddIn | |
Medical.PermissionsManagement.DataAccessLayer | \Examples\Medical\DotNet\Medical.PermissionsManagement.DataAccessLayer | |
Medical.Rules.AddIn | \Examples\Medical\DotNet\Medical.Rules.AddIn | |
Medical.SearchOtherPatientIds.Addin | \Examples\Medical\DotNet\Medical.SearchOtherPatientIds.Addin | |
Medical.Security.AddIn | \Examples\Medical\DotNet\Medical.Security.AddIn | |
Medical.Storage.AddIns | \Examples\Medical\DotNet\Medical.Storage.AddIns | |
Medical.UserManagementDataAccessLayer | \Examples\Medical\DotNet\Medical.UserManagementDataAccessLayer | |
Medical.WinForms | \Examples\Medical\DotNet\Medical.WinForms | |
Medical.Worklist.AddIns | \Examples\Medical\DotNet\Medical.Worklist.AddIns | |
MedicalMainMenu | \Examples\Medical\DotNet\MedicalMainMenu | |
Medical Workstation Customization Demo | \Examples\Medical\DotNet\MedicalWorkstationCustomizationDemo | Demonstrates how to customize the Medical Workstation.
|
Medical Workstation DICOM Directory Demo | \Examples\Medical\DotNet\MedicalWorkstationDicomDirDemo | Demonstrates how to view a DICOM directory with the Medical Workstation. |
Medical Workstation Main Demo | \Examples\Medical\DotNet\MedicalWorkstationMainDemo | Demonstrates building a fully featured PACS Workstation application using the LEADTOOLS Medical Workstation Framework.
|
Modality Worklist WCF Demo | \Examples\Medical\DotNet\ModalityWorklistWCFDemo | Demonstrates working with a Modality Worklist server. |
Modality Performed Procedure Step WCF Demo | \Examples\Medical\DotNet\MPPSWCFDemo | Demonstrates editing a MPPS instance on a Modality Worklist server. |
PACS Configuration Demo | \Examples\Medical\DotNet\PACSConfigDemo | The LEADTOOLS PACS Configuration Demo is used to configure the PACS Framework demos. |
PACS Database Configuration Demo | \Examples\Medical\DotNet\PACSDatabaseConfigurationDemo | The LEADTOOLS PACS Database Configuration Demo is used to configure the PACS Framework databases. |
Print to PACS Demo | \Examples\Medical\DotNet\PrintToPACSDemo | Demonstrates combining capture options such as Virtual Printer Driver, Screen Capture, TWAIN or WIA with the PACS Framework.
|
AddIn.Find | \Examples\Medical\DotNet\SampleAddIns\AddIn.Find | |
AddIn.Move | \Examples\Medical\DotNet\SampleAddIns\AddIn.Move | |
AddIn.Sample.Events | \Examples\Medical\DotNet\SampleAddIns\AddIn.Sample.Events | |
AddIn.Security | \Examples\Medical\DotNet\SampleAddIns\AddIn.Security | |
AddIn.StorageCommit | \Examples\Medical\DotNet\SampleAddIns\AddIn.StorageCommit | |
AddIn.Store | \Examples\Medical\DotNet\SampleAddIns\AddIn.Store | |
Configuration.Logging | \Examples\Medical\DotNet\SampleAddIns\Configuration.Logging | |
Medical.ExternalStore.Sample.Addin | \Examples\Medical\DotNet\SampleAddIns\Medical.ExternalStore.Sample.Addin | |
Storage Server Manager | \Examples\Medical\DotNet\StorageServerManager | This is a Fully Functional OEM-ready DICOM Storage server application with source code that includes the following features:
|
SupportFiles | \Examples\Medical\DotNet\Tutorials\SupportFiles | |
My.Medical.Storage.Configuration | \Examples\Medical\DotNet\Tutorials\My.Medical.Storage.Configuration | |
My.Medical.Storage.DataAccessLayer | \Examples\Medical\DotNet\Tutorials\My.Medical.Storage.DataAccessLayer |
Getting Started (Guide to Example Programs)