Secondary Capture is a DICOM Information Object Definition (IOD) that standardizes the storage of images generated outside the primary imaging modality's native acquisition pipeline. These images are typically produced by digitizing analog film, capturing a video output signal from a medical device, or converting a non-DICOM raster image format (like JPEG or TIFF) into a DICOM-compliant object. The defining characteristic of a Secondary Capture image is that it represents a rendered, screen-level view rather than the raw, unprocessed detector data, meaning the original acquisition parameters and proprietary raw data are often discarded.
Glossary
Secondary Capture

What is Secondary Capture?
A DICOM SOP Class for images converted from non-DICOM formats or captured from analog video signals, typically lacking the full technical acquisition context of the original modality.
Unlike a native CT Image Storage or MR Image Storage SOP Class, a Secondary Capture instance lacks the rich technical context—such as precise acquisition geometry, pulse sequence parameters, or detector calibration data—required for advanced post-processing. The Conversion Type attribute (0008,0064) explicitly documents the transformation pathway, distinguishing between digitized film output (DF) and workstation screen captures (WSD). This distinction is critical for integration engineers, as secondary capture objects are generally unsuitable for quantitative analysis or 3D reconstruction but remain essential for documenting legacy studies and non-imaging device outputs within a unified PACS archive.
Key Characteristics of Secondary Capture
Secondary Capture defines how images originating outside the standard DICOM acquisition pathway are converted and stored, preserving visual information while acknowledging the loss of original modality context.
Definition and Purpose
A Secondary Capture Image is a DICOM SOP Class for images converted from a non-DICOM format or captured from a video signal. It serves as a container for digitized film, screen captures, scanned documents, or imported JPEGs. The primary purpose is to integrate these external images into a PACS or VNA workflow, ensuring they can be stored, queried, and retrieved using standard DICOM services, even though they lack the rich acquisition parameters of a primary modality like CT or MR.
Loss of Acquisition Context
The defining characteristic of a Secondary Capture instance is the absence of detailed technical acquisition data. Unlike a primary CT Image Storage SOP Class, which contains tags for kVp, exposure time, and slice thickness, a Secondary Capture object typically lacks these modality-specific attributes. The DICOM Tag (0008,0060) Modality is set to 'OT' (Other) or a specific secondary capture value, explicitly signaling that the image is a converted representation, not raw acquisition data.
Conversion Process and Pixel Data
The conversion process involves rendering a non-DICOM image into a DICOM-compliant pixel data format. This often requires specifying a Transfer Syntax for encoding, such as JPEG lossy compression. The original pixel data is encapsulated, and critical DICOM header information, like the Patient Name (0010,0010) and Study Instance UID, is manually or automatically populated. The result is a valid DICOM Part 10 file, but the pixel data is a facsimile of the original, not the raw detector output.
Multi-Frame vs. Single-Frame
Secondary Capture SOP Classes exist for both single-frame and multi-frame images. Multi-frame Secondary Capture is used for converting video loops, such as an ultrasound cine clip exported from a non-DICOM system, into a single DICOM object. Each frame of the video becomes a frame in the DICOM instance, allowing the entire dynamic sequence to be managed as one entity within a PACS, preserving the temporal relationship between frames.
Burned-in Annotations and PHI Risk
A significant risk with Secondary Capture images is the presence of Burned-in Annotations. Since the image is a screen capture or a scan of a printout, patient demographics or hospital identifiers may be permanently rendered into the pixel data itself. This creates a major challenge for DICOM De-identification, as standard header anonymization is insufficient. Automated optical character recognition (OCR) and image masking are required to remove this Protected Health Information (PHI) before secondary use.
Role in Modality Workflow
Secondary Capture plays a crucial role in integrating non-DICOM devices into a digital workflow. For example, a surgical microscope that outputs only an HDMI video signal can be connected to a frame grabber. The capture software packages the video stream into Secondary Capture Image Storage SOP Instances and uses STOW-RS or DIMSE C-STORE to send them to the PACS. This allows the images to be associated with the correct patient study via the Modality Worklist, even though the microscope itself has no DICOM capability.
Secondary Capture vs. Native Modality Objects
A feature-level comparison between DICOM Secondary Capture images and native modality SOP Classes, highlighting the loss of acquisition context and quantitative precision.
| Feature | Secondary Capture | Native CT Image | Native MR Image |
|---|---|---|---|
Acquisition Context | |||
Raw Detector Data | |||
Modality-Specific Tags | |||
Hounsfield Unit Fidelity | |||
Multi-Frame Support | |||
Spatial Registration | |||
Window Width/Level Preservation | |||
Pixel Data Provenance | Converted from non-DICOM source | Direct from CT detector array | Direct from MR k-space data |
Frequently Asked Questions
Clear answers to the most common technical questions about the DICOM Secondary Capture SOP Class, its limitations, and its role in enterprise imaging workflows.
A DICOM Secondary Capture (SC) image is a DICOM SOP Class that represents an image converted from a non-DICOM format or captured from an analog video signal, rather than being natively acquired by a primary imaging modality. The defining characteristic of an SC object is that it lacks the full technical acquisition context—such as exact geometric parameters, radiation dose, or raw detector data—that is present in a native modality object like a CT or MR Image Storage SOP Class. SC images are typically generated by frame grabbers, screen capture software, or document scanners, and they serve as a standardized container for integrating external visual data into a PACS or VNA environment. The SOP Class UID for the most common form is 1.2.840.10008.5.1.4.1.1.7 for Secondary Capture Image Storage.
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
Understanding Secondary Capture requires familiarity with the broader DICOM ecosystem and the SOP Classes it interacts with during image conversion and storage workflows.
DICOM SOP Class
The fundamental unit of DICOM interoperability, defined as the union of a specific Information Object Definition (IOD) and a DIMSE Service Group. Secondary Capture is a specific SOP Class (UID 1.2.840.10008.5.1.4.1.1.7) that defines the structure for converted images. During Association Negotiation, systems must agree on this SOP Class to successfully exchange secondary capture instances.
DICOM Transfer Syntax
Defines how DICOM data is serialized into a byte stream. Secondary Capture images often use JPEG Lossy or JPEG Lossless Transfer Syntaxes for compression. The choice of Transfer Syntax is critical during conversion:
- Explicit VR Little Endian: Uncompressed, universal baseline.
- JPEG Baseline (1.2.840.10008.1.2.4.50): Common for color video captures.
- JPEG-LS Lossless: Used when diagnostic fidelity must be preserved.
DICOM Conformance Statement
A mandatory document from every medical device vendor detailing exactly which SOP Classes are supported. When integrating a Secondary Capture workflow, the conformance statement reveals:
- Whether the device acts as an SCU (sending captures) or SCP (receiving them).
- Which Transfer Syntaxes are negotiated.
- Whether Burned-in Annotations are recognized and handled.
DICOM Structured Report
Encodes clinical observations as machine-readable text with coded concepts rather than free-text. While Secondary Capture stores pixel data, a DICOM SR object can reference that image as evidence for a specific finding. This linkage is essential for building auditable diagnostic records where a captured ultrasound frame supports a structured measurement.
DICOM De-identification Profile
Standardized rules from DICOM Part 15 for removing Protected Health Information (PHI). Secondary Capture images are high-risk for containing PHI in Burned-in Annotations rendered into the pixel data itself. The de-identification process must:
- Strip header tags like Patient Name (0010,0010).
- Detect and redact text burned into the image raster.
- Clean private tags that may contain identifying information.
DICOM Modality LUT
A Look-Up Table that transforms stored pixel values into standard units (e.g., Hounsfield Units for CT). A key limitation of Secondary Capture is that this transformation is often already applied and the original raw data is lost. The Modality LUT in a Secondary Capture IOD is typically an identity transform, meaning the pixel data is presentation-ready but not suitable for quantitative analysis.

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