Understanding DICOM Conformance Statements

  • A DICOM Conformance Statement defines the exact subset of DICOM services a vendor system implements.
  • Checking the AE specifications for SOP classes, operational roles, and transfer syntaxes confirms if two systems can communicate.
  • Communication requires reciprocal AE roles: if your system is an SCP receiver, the sender must act as the SCU.
  • A shared transfer syntax must exist between sender and receiver, or the presentation context negotiation fails.
  • A conformance statement is a baseline on paper, not a guarantee, since licensed features and settings vary per hospital.

A vendor DICOM Conformance Statement (DCS) is a formal document that specifies how a system implements the DICOM standard. To read one effectively, do not read it from cover to cover. Jump directly to the Application Entity (AE) specifications. You need to check 3 technical items: the supported Service-Object Pair (SOP) classes, the operational roles, and the transfer syntaxes.

Comparing these 3 items against your receiver specifications confirms if two systems can exchange data. You can verify this before writing any code.

What is a DICOM Conformance Statement?

A DICOM Conformance Statement defines the exact boundaries of a system DICOM interface. The standard allows vendors to implement a subset of services. A CT scanner needs storage services to send images. It does not need print management. DICOM PS3.2 Chapter 6 outlines the purpose of the document. It allows engineers to determine whether two implementations can communicate over a network.

The document follows a standardized structure defined in DICOM PS3.2 Annex N. It describes which network services the software runs. It shows how the software handles associations and encodes data elements on the wire.

Vendors often publish documents spanning 80 to 200 pages. Most pages describe private attributes, print profiles, or media storage on physical CDs. For network ingestion, you can ignore 80% of the text.

How do you triage a 100-page vendor document?

Hospital administrators often send a 100-page PDF for a scanner or Picture Archiving and Communication System (PACS). Do not start on page 1. Open the table of contents. Locate Section 4 or Section N.5: the Application Entity Specifications.

Follow this 4-step triage sequence:

  1. Find the Network Services table: Check the list of Application Entities and their high-level services. Look for Storage, Verification, and Query/Retrieve.
  2. Confirm operational roles: Check whether the vendor AE acts as a Service Class User (SCU), a Service Class Provider (SCP), or both.
  3. Cross-reference the SOP Class table: Verify that your target modalities appear with their official Unique Identifiers (UIDs).
  4. Inspect the Transfer Syntax table: Identify supported byte encodings. Note any compressed formats like JPEG Lossless or JPEG 2000.

After reviewing these 4 items, you know if the integration is viable. You can review network settings like timeouts and PDU limits later during connectivity tests.

Which Application Entity roles match your architecture?

DICOM networking relies on complementary roles. An Application Entity acts in one or both of 2 modes:

  • Service Class User (SCU): The client that initiates an association and requests an action, like sending a study via C-STORE.
  • Service Class Provider (SCP): The server that listens on a TCP port, accepts the association, and processes the request.

Communication requires reciprocal roles. If your service acts as an SCP receiver, the hospital scanner must be an SCU for that service. If you query a hospital archive, your service is the SCU and the hospital PACS is the SCP.

Watch out for systems with multiple AEs. Many PACS platforms split functions across separate AE titles. One AE might handle verification and storage on port 104. A separate AE might handle query and retrieval on port 11112. Read our guide on what a DICOM Application Entity title is to see how AE titles map to network endpoints.

Always note the vendor default Called AE title. Check if the system restricts connections by Calling AE title. Many modalities refuse associations if your Calling AE title is missing from their local allowlist.

How do you verify SOP Class and transfer syntax support?

The core of any conformance review is the Presentation Context table. A presentation context pairs a SOP Class with a Transfer Syntax. The SOP Class defines what clinical data you send. The Transfer Syntax defines how the bytes are encoded.

1. Verify the SOP Class UID

Look at the AE specification table for supported SOP Classes. Each entry lists the clinical name and its official UID. For example, CT Image Storage is 1.2.840.10008.5.1.4.1.1.2, defined in DICOM PS3.4 Annex B.

Do not rely on the plain English name alone. A vendor might write “Secondary Capture”. You must check whether they mean standard Secondary Capture (1.2.840.10008.5.1.4.1.1.7) or Multi-frame True Color Secondary Capture (1.2.840.10008.5.1.4.1.1.7.4). Always check the numeric UID.

2. Verify Transfer Syntax negotiation

Next, find the Transfer Syntaxes listed for that SOP Class. When an SCU requests an association, it proposes one or more transfer syntaxes for each SOP Class. The SCP selects one syntax or rejects the presentation context.

The table below shows a typical presentation context entry from a vendor statement:

Abstract Syntax (SOP Class) Transfer Syntax Name Transfer Syntax UID Role Extended Negotiation
CT Image Storage (1.2.840.10008.5.1.4.1.1.2) Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
CT Image Storage (1.2.840.10008.5.1.4.1.1.2) Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
CT Image Storage (1.2.840.10008.5.1.4.1.1.2) JPEG Lossless, Non-Hierarchical 1.2.840.10008.1.2.4.70 SCU None

Both systems must share at least one transfer syntax. We recommend requiring Explicit VR Little Endian as your baseline. It uses uncompressed pixel data and explicit data types. This avoids byte-ordering bugs.

If the vendor only proposes compressed formats like JPEG 2000 (1.2.840.10008.1.2.4.90) or JPEG-LS (1.2.840.10008.1.2.4.80), your receiver must decompress them. Missing codecs cause transfers to fail. Read our guide to DICOM SOP classes and transfer syntaxes explained for more details on wire encoding.

What network and association parameters must you check?

After checking SOP classes and syntaxes, review the communication settings in Section 6 or Section N.7:

  • Maximum PDU Size: The Protocol Data Unit (PDU) defines the maximum byte chunk sent over TCP. Modalities often default to 16,384 bytes (16 KB). Modern systems can negotiate 65,536 bytes or more. If a sender exceeds the receiver maximum PDU, the connection drops.
  • Concurrent Associations: Can the scanner send studies over 4 parallel connections? Or does it queue transfers through a single connection?
  • Association Timeouts: Check the network inactivity timeout. Scanners on busy hospital networks often drop connections if a receiver takes over 30 seconds to acknowledge C-STORE.
  • TLS Profile: Check if the device supports native Transport Layer Security (TLS) profiles. Many older scanners do not support TLS at all.

For help planning certificates and ports with hospital engineers, use our onboarding pre-flight checklist. If you use managed cloud endpoints, review our overview of endpoints and certificates.

Why can you not trust a conformance statement blindly?

A DICOM Conformance Statement shows what software can do on paper. It does not show how the system is configured in a live hospital.

Here are 3 common issues you will encounter:

  1. Unlicensed features: A vendor statement may list C-STORE SCU for 20 SOP classes. But the hospital may not have purchased the DICOM Export license from that vendor.
  2. Disabled transfer syntaxes: The software might support JPEG Lossless in the manual. But the local PACS administrator turned compression off to reduce CPU load on their archive.
  3. Private SOP Classes: Some scanners export 3D reconstructions with vendor-specific private SOP Class UIDs. These are documented in vendor annexes. Standard receivers will reject them.

Treat the statement as a baseline, not a guarantee. Use it to configure your listener rules. Then validate the setup with a live test. If an association fails, read our guide on debugging a failed DICOM association to decode wire errors. For setting up your first receiver pipeline, follow our guide to connecting a DICOM sender.

Dicomly builds infrastructure for healthcare software teams that receive DICOM studies from hospitals. Why we built Dicomly →

Sources

  1. DICOM Standard Part 2 (PS3.2, Chapter 6 — Purpose of a Conformance Statement) (dicom.nema.org)
  2. DICOM Standard Part 2 (PS3.2, Annex N — DICOM Conformance Statement Template) (dicom.nema.org)
  3. DICOM Standard Part 4 (PS3.4, Annex B — Storage Service Class) (dicom.nema.org)
  4. DICOM Standard Part 5 (PS3.5, Chapter 10 — Transfer Syntax) (dicom.nema.org)

Start receiving DICOM today.

Early access. No credit card. First endpoint free.