PACS Framework — .NET

Assembly – Class/Namespace

Comments

Help Files

Demo Project Source Code

Leadtools.Dicom.Scu.dll - Leadtools.Dicom.Scu

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

Leadtools.Dicom.Scu Help

\Examples\PACSFramework\CS\CSDicomHighLevelStoreDemo
\Examples\PACSFramework\CS\CSDicomHighLevelClientDemo
\Examples\PACSFramework\VB\CSDicomHighLevelStoreDemo
\Examples\PACSFramework\VB\CSDicomHighLevelClientDemo

Leadtools.Dicom.Server.Admin.dll - Leadtools.Dicom.Server.Admin

Provides classes and methods that implement DICOM Server Administration.

 

Leadtools.Dicom.Server.Admin Help

\Examples\PACSFramework\CS\CSDicomServerManager
\Examples\PACSFramework\VB\CSDicomServerManager

 

Leadtools.Dicom.AddIn.dll - Leadtools.Dicom.AddIn

Provides classes and methods that implement DICOM AddIns.

Leadtools.Dicom.AddIn Help

\Examples\PACSFramework\CS\Sample AddIns
\Examples\PACSFramework\VB\Sample AddIns

Leadtools.AddIn.DicomLog - Implements the INotifyReceiveMessage & INotifySendMessages interfaces. This allows the addin to log all incoming and outgoing DICOM Messages. The logging is handled by the Microsoft Enterprise Library logging. The addin 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 addin 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 addin 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 addin implements a DICOM Query service. This addin supports the following service classes:

  • Patient Root Query Find
  • Study Root Query Find

This addin makes use of the same database that is created by the Store addin. If the database does not exist when this addin 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 addin implements a DICOM Retrieve service. This addin supports the following service classes:

  • Patient Root Query Find
  • Study Root Query Find

This addin makes use of the same database that is created by the Store addin. If the database does not exist when this addin is called it will be created. Therefore, it does not matter if you attempt a find before doing a store.

Leadtools.AddIn.MWLFind - Implements the IProcessCFind interface. This addin supports the following service classes:

  • Modality Worklist Find

This addin creates a SQLCE 3.5 Database(MWLSCP.sdf) in the server directory. In addition, this addin creates an Option Dialog that allows you to edit the database from the Server Manager.

Leadtools.AddIn.StorageCommit - Implements the IProcessNAction interface. This addin supports the following service classes:

  • Storage Commitment Push Model Class

This addin makes use of the SQLCE 3.5 Database created by the storage addin. 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 addin to the originating client.