Product: Storage Commitment (SCU)
Overview
OmegaAI now introduces the Storage Commitment feature. It is a DICOM service where OmegaAI confirms whether a destination system has permanently stored received images.
What's New
1. Storage Commitment (SCU)
What changed:
Once images are transmitted successfully (C-STORE), OmegaAI sends a Storage Commitment request asking the destination system to confirm safe archival.
The destination responds with:
- Confirmation of successful storage
- Partial success (some images stored)
- Failure (images not stored)
- This ensures images are not only delivered but also diligently archived.
Benefits:
Enabling Storage Commitment SCU will aid when:
- Destination supports DICOM Storage Commitment
- Verified archiving is required
- You require audit-level confirmation of storage
- You have experienced silent image loss
Image transmission alone does not guarantee long-term storage.
Failures such as network issues or destination storage errors may go unnoticed, thus Storage Commitment provides:
- Verification: Confirms images are permanently stored
- Auditability: Full transaction tracking in logs
- Reliability: Automatic retry and resend mechanisms
- Compliance Support: Helps meet medical imaging retention requirements
Important Notes
Does this change image sending behaviour?
No. Only adds post-send verification.
Is historical data included?
No. Only new sends after enabling.
Does restart affect transactions?
No. Pending transactions resume automatically.
Can this be enabled per station? Yes.
What is Partial Commitment?
Some images stored, others failed or unconfirmed.
Can batch size be changed?
Yes. Default is recommended for most systems.
Timeout behaviour?
OmegaAI waits up to 24 hours before retry logic is triggered.
Where to Find It
Navigation path in the application:
User Guide → Getting Started → Adding Devices & Modalities (DICOM Stations) → Storage Commitment SCU
Updated Help Articles
Adding Devices & Modalities (DICOM Stations); Storage Commitment SCU