A DICOM Segmentation Object is a storage SOP Class that encodes pixel-level classification maps, where each segmented frame defines a specific region of interest (ROI)—such as a tumor, organ, or lesion—as a companion to the referenced source image series. Unlike a standard image that stores diagnostic pixel intensities, a segmentation object stores binary (0 or 1) or probabilistic fractional values indicating the presence or likelihood of a specific anatomical or pathological structure.
Glossary
DICOM Segmentation Object

What is a DICOM Segmentation Object?
A DICOM Segmentation Object is a specialized SOP Class that encodes binary or fractional segmentation maps as a companion object to reference source images, representing regions of interest such as tumors or organs.
The object leverages the DICOM Segmentation IOD and supports both binary and fractional segmentation types, enabling multi-frame encoding where each frame represents a single segment. It maintains spatial and temporal coherence with the source images through explicit referenced image sequences, ensuring that AI-generated contours and manual annotations remain precisely aligned with the original acquisition geometry for downstream quantitative analysis.
Key Features of the DICOM Segmentation Object
The DICOM Segmentation Object is a specialized SOP Class that encodes binary or fractional segmentation maps as companion objects to referenced source images, enabling interoperable storage and exchange of regions of interest such as tumors, organs, and lesions.
Binary and Fractional Segmentation Types
The Segmentation Object supports two distinct encoding types defined by the Segmentation Type attribute (0062,0001):
- BINARY: Each segment is a separate bit-plane in the pixel data, where a value of 1 indicates pixel membership in the region of interest. Multiple segments can be encoded in a single frame using bit-packed storage.
- FRACTIONAL: Each segment occupies an entire frame with grayscale values representing the probability or partial volume of tissue membership, typically ranging from 0 to 255 for 8-bit data.
The choice between binary and fractional encoding directly impacts storage efficiency and the clinical precision of boundary representation.
Multi-Frame Image Encoding
Unlike single-frame DICOM images, the Segmentation Object is inherently a multi-frame image where each frame represents a distinct segment or slice position:
- Frames are organized using the Dimension Organization module, which defines index sequences for spatial position, segment number, and temporal points.
- The Dimension Index Sequence (0020,9222) explicitly maps each frame to its corresponding segment number and spatial coordinates.
- This structure allows a single SOP Instance to contain hundreds of segments across a full volumetric dataset, dramatically reducing the number of objects that must be managed compared to storing each segmentation as a separate image.
Segment Attribute Macros
Each segmented region is described by a rich set of metadata using the Segment Sequence (0062,0002):
- Segment Number (0062,0004): Uniquely identifies the segment within the SOP Instance.
- Segment Label (0062,0005): A human-readable name such as "Liver" or "Tumor Core."
- Segmented Property Category Code Sequence (0062,0003): Maps the segment to a coded concept from controlled terminologies like SNOMED CT or FMA, ensuring semantic interoperability.
- Anatomic Region Sequence (0008,2218): Specifies the body part examined, enabling automated routing and hanging protocol selection.
- Tracking ID (0062,0020) and Tracking UID (0062,0021): Support longitudinal tracking of the same anatomical feature across multiple studies.
Referenced Image and Spatial Registration
The Segmentation Object maintains explicit spatial relationships to its source images through two critical mechanisms:
- Derivation Image Sequence (0008,9124): References all source SOP Instances from which the segmentation was derived, establishing provenance and enabling downstream audit trails.
- Spatial Registration via the Registration Sequence (0070,0308) within the Common Instance Reference Module: Defines the rigid or deformable transformation matrix that maps the segmentation's frame of reference to the referenced image's coordinate system.
- The Frame of Reference UID (0020,0052) ensures that the segmentation shares the same spatial coordinate space as the source images, critical for multi-modality fusion.
Surface Mesh Storage Alternative
Beyond pixel-based encoding, the Segmentation Object can store surface representations using the Surface Segmentation Module:
- Surface Sequence (0066,0002): Contains one or more surface meshes, each defined by vertex coordinates and triangle connectivity.
- Surface Points Sequence (0066,0011) and Surface Faces Sequence (0066,0027): Store the raw geometry data.
- Recommended Display Grayscale Value (0062,000C): Specifies the preferred display intensity for rendering the surface.
- Surface meshes are particularly valuable for surgical planning and 3D printing workflows, where explicit boundary geometry is required rather than voxel masks.
Segmentation SOP Class UIDs
The DICOM standard defines a specific SOP Class UID for the Segmentation Object:
- SOP Class UID: 1.2.840.10008.5.1.4.1.1.66.4
- This UID is negotiated during Association Negotiation between an SCU and SCP to confirm mutual support for segmentation storage.
- The corresponding Storage SOP Class is formally named "Segmentation Storage."
- When stored as a DICOM Part 10 file, the Media Storage SOP Class UID in the File Meta Information header must match this identifier to ensure correct parsing by any standards-compliant PACS or VNA.
Frequently Asked Questions
Clarifying the structure, purpose, and integration of the DICOM Segmentation SOP Class for encoding regions of interest.
A DICOM Segmentation Object is a specialized SOP Class that encodes binary or fractional segmentation maps as a companion object to referenced source images, rather than storing diagnostic pixel data for visual interpretation. Unlike a standard CT or MR Image Object that contains Hounsfield Units or signal intensities, a Segmentation Object stores a raster map where each pixel value represents a category label (e.g., '1' for tumor, '0' for background) or a fractional probability. The object references the source images via DICOM UID in the Derivation Image sequence, ensuring spatial alignment. Critically, the segmentation frames share the identical geometry—dimensions, pixel spacing, and orientation—of the referenced images, allowing direct overlay without registration. The object uses a Segmentation Type attribute (binary or fractional) and defines segments via the Segment Sequence, where each segment has a label, algorithm name, and coded anatomical category from DICOM Controlled Terminology.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Core concepts and companion objects that interact with the DICOM Segmentation Object to enable quantitative imaging workflows.
Segmentation Type and Fractional Encoding
The DICOM Segmentation Object supports binary (0 or 1) and fractional (probability maps) segmentation types. Binary segmentation uses a single bit per pixel to define a hard mask, while fractional encoding stores a continuous value between 0 and 1 per pixel, representing the probability of tissue membership. This is critical for storing the raw output of deep learning models before thresholding, preserving uncertainty information for downstream quantitative analysis.
Referenced Image and Spatial Registration
A Segmentation Object must explicitly reference the source DICOM images from which it was derived via the Referenced Series Sequence and Referenced SOP Instance UID. The spatial registration between the segmentation frames and the source images is defined using a rigid transformation matrix stored in the Registration Sequence or via identical Frame of Reference UID and Image Position/Orientation attributes, ensuring pixel-perfect overlay in a PACS viewer.
Segment Number and Anatomic Labeling
Each distinct region within a Segmentation Object is assigned a unique Segment Number (integer, starting at 1) and can be labeled with a coded anatomic concept from a controlled terminology such as SNOMED CT or RadLex. The Segmented Property Category Code Sequence and Segmented Property Type Code Sequence allow the object to self-describe that Segment 1 represents 'Lung' and Segment 2 represents 'Tumor', enabling automated ingestion by radiomics platforms.
DICOM Segmentation vs. RT Structure Set
While both encode regions of interest, the DICOM Segmentation Object stores results as a pixel-aligned raster mask, whereas the RT Structure Set stores contours as geometric planar coordinates. Key distinctions:
- Segmentation Object: Ideal for AI-generated voxel-wise output; supports fractional encoding; natively aligned to image grid.
- RT Structure Set: Ideal for human-drawn contours; supports non-axial planes; required for radiotherapy treatment planning systems. Conversion between the two formats is a common interoperability challenge.
Multi-Frame Organization and Per-Frame Metadata
A single DICOM Segmentation Object is a multi-frame SOP Instance where each frame corresponds to a single slice of a 3D volume. The Per-Frame Functional Groups Sequence allows each frame to carry its own spatial metadata, including Plane Position and Plane Orientation, enabling the segmentation to be correctly mapped to a non-uniform or tilted source acquisition. This structure efficiently packages an entire 3D organ mask into one manageable DICOM object.
Surface Segmentation and Mesh Storage
Beyond raster masks, the DICOM standard also defines a Surface Segmentation SOP Class for storing 3D surface meshes as triangulated point clouds. This is particularly useful for surgical planning and 3D printing applications where a lightweight geometric boundary representation is preferred over a dense volumetric mask. The surface mesh is stored using the Surface Mesh Module, which encodes vertex coordinates and triangle connectivity.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us