Anonymisation of DICOM Objects

DicomObjects is commonly and successfully used for Anonymisation and all the required data changes are easy using DicomObjects - the real problem is working out what needs changing! This subject is a real "Pandora's box", and whilst changing IDs, names etc. is easy, the more you look into it, the more "Hidden" patient information you find e.g.:

Measurement Units

The ROIDistanceUnits property of a DicomLabel varies according to the attribute used to obtain the scaling information, for which there are 5 possibilities. Normally only one of these should be present, but should there be >1 then the first in this list is used. In all cases of course, the values returned by other ROI functions (ROILength etc.) are in matching units.


Custom Print Formats

Medical Connections Public DICOM Server

Medical Connections maintains a public DICOM server for those wishing to test their DICOM implementations whether based on DicomObjects or other toolkits.

Details can be found on the server itself at

Relational Queries

Relational Queries have been in the DICOM standard since the start, but are supported by only about half the PACS in the world. They are negotiated using Extended_Negotiation and if requested by the SCU and accepted by the SCP then they remove several of the normal C-FIND rules, namely:

Planar configuration

The Planar Configuration attribute (0028,0006) is only used in DICOM colour images, and specifies how the pixel data are arranged.

  • If the value is 0, then they are grouped by location, e.g.
  • If the value is 1, then they are grouped by sample, e.g.

In this latter case, they are still grouped by frame in a multi-frame image, so the order would be:

Comparison of MoveImages MoveSync GetUsingMove and Move

The COM_version of DicomObjects provides 4 different mechanisms for initiating C-MOVE operations, and we are often asked about the differences and relative benefits. This page is therefore a summary of the differences.

Private SOP class

A Private SOP Class is an object constructed and transmitted in the same basic way as an official DICOM SOP_Class but with the contents defined by the creator of the private SOP class, rather than by DICOM. Typically a piece of equipment which uses a private SOP class will try to negotiate both a Private SOP class and an official DICOM SOP Class for the images they send to a PACS, on the basis that only a PACS from the same manufacturer will accept the private one, with everyone else accepting only the DICOM one.


Subscribe to RSS - General-DICOM