DICOM File Meta Information Header

A header that is added to a DICOM Instance when it is saved to file. The DICOM Meta information header is not part of the DICOM Instance itself. It adds information required for parsing the file correctly and identifying the application that saved the file. The DICOM file meta info was added [...]


Web Access to DICOM Objects. Part 18 of the DICOM standard details an interface to DICOM Objects using HTTP. WADO enables, for example, retrieving DICOM images as JPEG  using an HTTP GET request. The importance and acceptance of WADO increased dramatically together with the internet revolution and increasing use of cloud services and PACS [...]


Extensible Markup Language. A markup language that defines a set of rules for encoding documents in a format which is both human-readable and machine-readable. Unlike HTML, XML's set of rules is not chosen, but defined by its writer. A properly written XML document has a ‘tree’ structure, in which each branch represents a data entity, [...]


Acronym for “Cross Enterprise Document Sharing”. XDS is an IHE Integration Profile that specifies a method for sharing document across enterprise boundaries.


Value Representation. The DICOM Data Type. VR’s are named as two letter codes. E.g. UI is the UID. PN is Person Name.


Acronym for Vendor Neutral Archive. A digital archive for medical documents, including images, that stores documents of multiple standards and formats and provide access through a variety of protocols. Many times VNA is compared with PACS. Both terms, VNA and PACS, are used widely for digital archive systems. While PACS provide services using the [...]


Value Multiplicity. A DICOM Element may have multiple values. String values are separated by \ while the VM of binary values is determined by dividing the element length in bytes by the size of one value. For example the VM of a data element of type US (Unsigned Short) that has a length of 6 [...]


Acronym for “Unique  Identifier”. UID’s are widely used in DICOM and are assigned to objects, classes, transfer syntaxes, special services, and specific data elements. NEMA registers DICOM UID’s and every instance of a DICOM application should have a UID prefix that it can use to generate new UID’s from.

Transfer Syntax

Defines how data elements are serialized in three (3) aspects: (1) Byte order (Little/Big endian) (2) Explicit or Implicit Value Representation and (3) If and what type of compression is used for the image pixel data element. Represented as a pre-defined UID. Transfer syntax is negotiated for every service in the association setup phase and [...]

SCM – Storage Commitment Management

A DICOM Service that is used to “pass the ownership” on DICOM Instances from one application to another. It confirms that a DICOM Application stores a set of DICOM Instances in a similar way to the “commit” SQL command. When receiving successful commit result, an application can assume that the instances are safely stored by [...]