Leadtools.Dicom.Common Introduction

Summary

The Leadtools.Dicom.Common assembly provides features that make working with the LEADTOOLS DicomDataset class easier.

Key Features:

Extension Methods
- Get - Allows you to retrieve information from a DicomDataset with one line of code.
- Set - Allows you to set information in a DicomDataset with one line of code.
- SaveXml - Saves DicomDataset to an XML representation. The output XML is customizable by the user.
- SaveJson - Saves DicomDataset to a JSON model format. The output is customizable by the user.
- LoadXml - Loads XML data into a DicomDataset.
- Compare - Allows you to compare two DICOM data sets and get the differences between them.
- .NET classes that work with the Set/Get extension methods.
- These classes already have the necessary attributes defined for extracting DICOM information from a DicomDataset.

DICOM Editing Namespace

Developers can use the DICOM Editing namespace to simplify modifying an application to have a graphic user interface for displaying the content of a DICOM data set and for editing DICOM tags in an organized manner. It leverages the LEADTOOLS internal DICOM dictionaries (e.g. IOD table and Tag table) to provide the user the following information:

Visual information about the requirements for a specific tag (Type1, Type 2 etc.) with respect to the IOD Class.
The data types allowed.
Additional information about the use of the tag.

A user can also associate a set of predefined values that are allowed for a tag based on DICOM-standard-imposed restrictions (e.g. defined terms or enumerated values in an IOD definition) or implementation-specific restrictions (i.e. site-specific possible performed procedure step codes).

The developer has full control over user interaction with the DICOMPropertyGrid and can extend its capabilities. For instance, it is possible to add more tags (private or standard tags) to a data set for editing.

Developers can use the Leadtools.Dicom.Common assembly to simplify data set generation (and other processes), and to ensure data validation.

As an example, when creating a modality station the Leadtools.Dicom.Common assembly can be used to allow the end-user to enter information related to performed procedures as part of data set generation.

Other examples include generating a DICOM data set such that users at imaging or viewing stations can obtain Key Image notes, Presentation States, Structure reports, perform Secondary Capture, etc.

Supported Environments