MajwareMAJWARE
General

(0008,1195)

Transaction UID

Keyword: TransactionUID

Identifies one Storage Commitment request. The SCU sends it in the N-ACTION request and the SCP returns the same value in its N-EVENT-REPORT, so the answer can be matched to the request.

Tag Attributes

Tag ID
(0008,1195)
Compact
00081195
Keyword
TransactionUID
VR
UI — Unique Identifier (UID)
VM
1
Required
Type 1 — required, with a value
PS3.15
Basic Profile action U
Retired
No

Defined in

Storage Commitment Push Model

What Transaction UID contains

Once the SCP has sent the N-EVENT-REPORT for a transaction, that Transaction UID is no longer active and must not be reused. Storage Commitment uses it; Modality Performed Procedure Step does not.

Group 0008 holds general identifying information: what kind of object this is, when it was made, and by which equipment and people.

Value format: UI (Unique Identifier (UID)), VM 1

(0008,1195) TransactionUID has Value Representation UI (Unique Identifier (UID)) and Value Multiplicity 1, which means exactly one value.

UI — Unique Identifier (UID)

A globally unique identifier made of numeric components separated by periods, for example 1.2.840.10008.1.2.1. An odd-length value is padded with one trailing NULL byte.

Length
64 bytes maximum
Characters
The digits 0–9 and the period.

Example value

2.25.329800735698586629295641978511506172918

Format mistakes to avoid

  • A component may not start with a zero unless it is the single digit 0, so 1.2.03 is invalid.
  • Letters, spaces and values longer than 64 bytes are invalid.

Where TransactionUID appears

Defined inTypeMeaning
Storage Commitment Push ModelPS3.4 J.3.21Required, and it must have a value.Usage 1/1 (SCU/SCP) in the N-ACTION request; the SCP returns the same value in the N-EVENT-REPORT.

A module lists the attributes an object must or may carry. Many IODs (CT Image, MR Image, Secondary Capture and others) include the same module, and an IOD-specific module can make an attribute stricter than the general one.

De-identification (PS3.15)

PS3.15 Table E.1-1 gives Transaction UID the Basic Profile action U: replace it with a new UID that stays consistent across every instance in the de-identified set.

With the Retain UIDs Option, the action is K: keep it unchanged (a sequence is kept but cleaned item by item).

To see how de-identification changes your own files, try the free DICOM Anonymizer, which runs in the browser and uploads nothing.

In archives and migrations

When studies move between archives, the objects should arrive with this attribute exactly as it was sent. Compare a sample of objects on both sides after the transfer rather than assuming nothing changed.

Common errors and how to fix them

Troubleshooting: If commitment results cannot be matched to requests, check that the SCU creates a new Transaction UID for every N-ACTION and keeps it until the N-EVENT-REPORT arrives, which can come on a different association.

Check a file in seconds with the free DICOM Validator: it reads the header in your browser, lists the tags with their values, and flags missing or malformed key attributes.

Transaction UID: frequently asked questions

What is DICOM tag (0008,1195) Transaction UID?

Identifies one Storage Commitment request. The SCU sends it in the N-ACTION request and the SCP returns the same value in its N-EVENT-REPORT, so the answer can be matched to the request.

What VR and VM does Transaction UID (0008,1195) have?

(0008,1195) TransactionUID has Value Representation UI (Unique Identifier (UID)) and Value Multiplicity 1, which means exactly one value. A globally unique identifier made of numeric components separated by periods, for example 1.2.840.10008.1.2.1. An odd-length value is padded with one trailing NULL byte. Maximum length: 64 bytes maximum.

Is Transaction UID (0008,1195) required?

In the Storage Commitment Push Model (PS3.4 J.3.2) it is Type 1: required, and it must have a value. Usage 1/1 (SCU/SCP) in the N-ACTION request; the SCP returns the same value in the N-EVENT-REPORT.

How is Transaction UID handled when de-identifying DICOM files?

PS3.15 Table E.1-1 gives Transaction UID the Basic Profile action U: replace it with a new UID that stays consistent across every instance in the de-identified set. With the Retain UIDs Option, the action is K: keep it unchanged (a sequence is kept but cleaned item by item).

How do I troubleshoot Transaction UID (0008,1195)?

If commitment results cannot be matched to requests, check that the SCU creates a new Transaction UID for every N-ACTION and keeps it until the N-EVENT-REPORT arrives, which can come on a different association.

Check TransactionUID in your files

The free DICOM Validator lists every header tag and flags problems. Files stay in your browser.

Open DICOM Validator →

Remove patient data before sharing

The free DICOM Anonymizer applies a de-identification profile in your browser, with no upload.

Open DICOM Anonymizer →

Sources

Checked against the DICOM standard, release 2026d. Module Types, query keys and de-identification actions come from these tables:

More General tags