PACS Framework Demo Installation

The LEADTOOLS PACS Framework includes six example add-ins, as follows:

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

2. Leadtools.AddIn.Store -

   Implements the IProcessCStore interface. This add-in implements a StorageSCP. The following storage classes are supported:

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

   The following transfer syntaxes are supported:

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

   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.

3. Leadtools.AddIn.Find -

   Implements the IProcessCFind interfaces. This add-in implements a DICOM Query service. This add-in supports the following service classes:

   • Patient Root Query Find
   • Study Root Query Find

   This add-in makes use of the same database that is created by the storage 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.

4. Leadtools.AddIn.Move -

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

   • Patient Root Query Find
   • Study Root Query Find

   This add-in makes use of the same database that is created by the storage 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.

5. Leadtools.AddIn.MWLFind -

   Implements the IProcessCFind interface. This add-in supports the following service classes:

   • Modality Worklist Find

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

6. Leadtools.AddIn.StorageCommit -

   Implements the IProcessNAction interface. This add-in supports the following service classes:

   • Storage Commitment Push Model Class

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. After the commit request is finalized, a request is sent on behalf of the add-in to the originating client.