Working with DICOM Tables

The internal DICOM tables have been moved from the Leadtools.Dicom.dll to a dedicated Leadtools.Dicom.Tables.dll. This makes the main DICOM DLL (Leadtools.Dicom.dll) significantly smaller in size, and offers developers several new options for accessing and tailoring DICOM tables to the specific requirements of their applications.

There are five DICOM tables that are defined and stored internally in the DICOM toolkit:

DICOM toolkit users now have several options for using and tailoring the DICOM tables to meet the needs of their applications.

These four tables can easily be tailored. For example, to add new UIDs, elements, IODs, or context groups, developers can edit any one of these files with any text editor. Also, the tables can be easily combined into a single table.

Developers can easily remove those items from tables that will not be used. For example, the DICOM IOD table contains more than 60 IOD definitions and more than 300 module definitions, which comes to more than 18000 lines in the dicTableIodModule.xml file. If a particular DICOM application does not use IODs, then the application footprint can be significantly reduced by not including these IODs at all. Or if you are doing basic DICOM communication, you can include only those IODs that you need, and remove all others. For example, your application might use only the following IODs:

For more information on UIDs, Dicom Elements, IODs, and Context Groups, refer to

For more information on UIDs, Dicom Elements, IODs, and Context Groups, refer to

Working with Unique Identifiers (uids)

Working with Tags

Working with Information Object Definitions Working with Context Groups

Help Version 19.0.2017.10.19
Products | Support | Contact Us | Copyright Notices
© 1991-2017 LEAD Technologies, Inc. All Rights Reserved.
LEADTOOLS Imaging, Medical, and Document