Working with DICOM Tables (API)

Starting with the release of version 17.5, the internal DICOM tables have been moved from the ltdicu.dll to a dedicated LtDicTablesu.dll. This makes the main DICOM dll Ltdicu.dll significantly smaller in size, and offers the developer several new options for accessing and tailoring the DICOM tables to the specific requirements of their application.  

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

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

  1. Developers can include ltdicu.dll and LtDicTablesu.dll in their distributables.  LtDicTablesu.dll includes all UID's, Element tags, IOD's, and DICOM Context Groups from the 2008 DICOM specification.  This is the easiest way of using the DICOM tables.

  2. Developers can choose not to include LtDicTablesu.dll in their redistributables.  In this case, developers should call the appropriate L_DicomLoadXml function to load the DICOM tables that they want to load.  As part of the toolkit, four human-readable DICOM table XML files are now installed in the LEADTOOLS Sample Images directory:

  3. dicTableUid.xml -used with L_DicomLoadXmlUID

  4. dicTableElement.xml -used with L_DicomLoadXmlTag

  5. dicTableIodModule.xml - used with L_DicomLoadXmlIOD

  6. dicTableContextGroup.xml - used with L_DicomLoadXmlContextGroup

These four tables can easily be tailored to your needs.  For example, to add new UID's, elements, IOD's, 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 items from these 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 the 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

Working with Unique Identifiers (UIDs)

Working with Tags

Working with Information Object Definitions

Working with Context Groups

An Overview of the DICOM File Format or the DICOM Standard.

Products | Support | Contact Us | Copyright Notices
© 1991-2017 LEAD Technologies, Inc. All Rights Reserved.
Click or drag to resize