This article describes different ways a DicomLabel object can be aligned inside a DicomViewer control using its properties in .NET and COM version of DicomObjects.
We have to admit the term “Bitmap” is a bit confusing for most people. It is actually a DICOM term for “map of bits”, not the common Bitmap graph. What you have for label type Bitmap is a collection of dots, positions of which are specified in the Points property of that label object:
There is a known issue in the Dicom Standard. SOP classes related to RT can legitimately be written / transferred using several different Transfer Syntaxes. HOWEVER The length of some of the attributes associated to RT is such that they can not be represented within a 32 bit word. As such it is imposable to represent them using an explicit Transfer Syntax.
Contents DicomObjects.NET DicomObjects.COM 32 BIT 64 BIT Sensible level values for logging DicomObjects log files are extremely important and useful for analysing DICOM network and query/retrieve problems. There are several ways to turn on logging in DicomObjects. DicomObjects.NET Use DicomGlobal.LogToFile method in your program. This should appear in a Form Load or similar startup method. DicomGlobal.LogToFile("C:\\DicomLogs",level); Alternatively, without having to modify your source code, you can use the DicomObjects.
It is possible to “Capture” an image as displayed on screen. This can be easily done in both .NET and COM version of DicomObjects.
Mask subtraction is very different in the COM and .NET versions of DicomObjects DicomObjects.COM In the COM version of DicomObjects, two DicomImage properties associated with the Mask Subtraction operations are sometimes found a bit confusing to developers: Mask & MaskFrame. Mask This functions as a switch to turn on/off the mask subtraction operation. If Mask Subtraction Sequence (0028, 6100) exists then DicomObjects will sets the default value of Mask to 1, otherwise 0.
The following diagram shows the relationship between DicomImage and DicomDataSet objects.
We are often asked how to retrieve the pixel data of a DicomImage into a Byte array. The following code will load an image and copy the pixel data into a byte array.
A Presentation State is an independent DICOM SOP Instance that contains information on how a particular image should be displayed. The Presentation State may contain label information(types of Label and Positions), windowing values, zoom value, scrolling (panning) values, rotations or any other visual display element that is defined within the DICOM standard. However Presentation States contain no Pixel Data as they are intended for use with an existing Dicom Image.
This page explains licensing structures and some of the frequently asked questions.
There are three types of Refresh in DicomObjects:
This routine fires automatically when any of the following display settings gets changed:
Many of the less commonly used features of DicomObjects are controlled by “registry” values, which can be specified in one of 2 ways: Using the “real” registry (only for the COM version, not .NET), a sample “.Reg” file can be downloaded here. Using DicomGlobal functions Set up registry keys in the COM version of DicomObjects Using the “real” registry (COM Only) There are 2 variations on this, depending on the architecture of your machine
There are two kinds of Rejection during association establishment, Association Rejection and Contexts Rejection.
Private Elements (or Tags) are perfectly legal in DICOM, details of the structure of Private DICOM Elements can be found in DICOM Private Elements.
Removing all Private elements from any DICOM instance is quite simple, following sample code shows you how to do it in DicomObjects.
This article explains what DicomObjects (both COM and .NET versions) supports in terms of DICOM Structured reporting. Of course, DicomObjects as always provides full access to the data within any DICOM instance that has been loaded and it can handle the reading, writing and network transmission of Structured reports just the same as it can for images or any other sort of DICOM instance.
Providing software toolkits and consultancy for healthcare integration with primary focus on DICOM & XDS
Company Number: 3680043
Founded by Dr. David Harvey
© 2019 Medical Connections Ltd
