PACS Framework — .NET

The LEADTOOLS .NET PACS Framework consists of assemblies and example projects that implement PACS services. For a description of the assemblies and available example projects, refer to the information below.

Leadtools.Dicom.Scu.dll

Provides classes and methods that implement DICOM Storage Service and DICOM Query/Retrieve Service.

Demo Project Source Code

• \Examples\Medical\DotNet\DicomHighlevelPatientUpdaterDemo
• \Examples\Medical\DotNet\DicomHighlevelStoreDemo
• \Examples\Medical\DotNet\DicomHighlevelClientDemo

Leadtools.Dicom.Server.Admin.dll

Provides classes and methods that implement DICOM Server Administration. |

Demo Project Source Code

• \Examples\Medical\DotNet\StorageServerManager
• \Examples\Medical\DotNet\Dicom.Server.Manager

Leadtools.Dicom.AddIn .dll

Provides classes and methods that implement DICOM add-ins. For more information, refer to LEADTOOLS DICOM Add-ins.

Demo Project Source Code

• \Examples\Medical\DotNet\SampleAddIns

Leadtools.Medical.Workstation.dll

Demo Project Source Code

Provides classes, methods, properties, enumerations and events to implement all the user interface controls (the Viewer control, the Search control, the Configuration control, etc.)

Demo Project Source Code

• \Examples\Medical\DotNet\MedicalWorkstationMainDemo

Leadtools.Medical.Workstation.Client.dll

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.

Demo Project Source Code

• \Examples\Medical\DotNet\MedicalWorkstationMainDemo

Leadtools.Medical.Workstation.DataAccessLayer.dll

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.

Demo Project Source Code

• \CS\MedicalWorkStationDataAccessLayerExample
• \Examples\Medical\DotNet\MedicalWorkstationMainDemo

Leadtools.Medical.Workstation.Loader.dll

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.

Demo Project Source Code

• \Examples\Medical\DotNet\MedicalWorkstationMainDemo

LEADTOOLS 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 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.

Leadtools.AddIn.Store

Implements the IProcessCStore interface, in order to implement a StorageSCP. The following storage classes are supported:

• CR Image Storage
• CT Image Storage
• DX Image Storage
• Hemodynamic Waveform Storage
• MR Image Storage
• NM Image Storage
• SC Image Storage
• US Image Storage
• US Multiframe Image Storage
• Video Endoscopic Image Storage
• Video Microscopic Image Storage
• XA Image Storage
• XRay Radiofluoroscopic Image Storage

The following transfer syntaxes are supported:

• Explicit VR Big Endian
• Explicit VR Little Endian
• Implicit VR Little Endian
• JPEG 2000
• JPEG Baseline 1
• JPEG Lossless No Hierarchical 14
• JPEG Lossless No Hierarchical 14B
• JPEG Lossless Only

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 data sets received at the server.

Leadtools.AddIn.Find

Implements the IProcessCFind interfaces. It implements a DICOM Query service and supports the following service classes:

• Patient Root Query Find
• Study Root Query Find

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 whether you attempt a find before doing a store.

Leadtools.AddIn.Move

Implements the IProcessCMove interface. This add-in implements a DICOM Retrieve service. The Leadtools.AddIn.Move add-in supports the following service classes:

• Patient Root Query Find
• Study Root Query Find

The Leadtools.AddIn.Move 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 whether you attempt a find before doing a store.

Leadtools.AddIn.MWLFind

Implements the IProcessCFind interface. It supports the following service class:

• Modality Worklist Find

The Leadtools.AddIn.MWLFind 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 the database to be edited from the Server Manager.

Leadtools.AddIn.StorageCommit

Implements the IProcessNAction interface. It supports the following service class:

• Storage Commitment Push Model 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 request is sent on behalf of the add-in to the originating client.