4.2.1. Storage Application Entity Specification¶
4.2.1.1. SOP Classes¶
The Storage Application Entity provides Standard Conformance to the following SOP Class(es) :
SOP Class Name |
SOP Class UID |
SCU |
SCP |
|---|---|---|---|
Verification SOP Class |
1.2.840.10008.1.1 |
Yes |
Yes |
Storage Commitment Push Model SOP Class |
1.2.840.10008.1.20.1 |
No |
Yes |
Image Storage SOP Classes: |
|||
Computed Radiography Image Storage |
1.2.840.10008.5.1.4.1.1.1 |
No |
Yes |
Digital X-Ray Image Storage - For Presentation |
1.2.840.10008.5.1.4.1.1.1.1 |
No |
Yes |
Digital X-Ray Image Storage - For Processing |
1.2.840.10008.5.1.4.1.1.1.1.1 |
No |
Yes |
Digital Mammography X-Ray Image Storage - For Presentation |
1.2.840.10008.5.1.4.1.1.1.2 |
No |
Yes |
Digital Mammography X-Ray Image Storage - For Processing |
1.2.840.10008.5.1.4.1.1.1.2.1 |
No |
Yes |
Digital Intra-Oral X-Ray Image Storage - For Presentation |
1.2.840.10008.5.1.4.1.1.1.3 |
No |
Yes |
Digital Intra-Oral X-Ray Image Storage - For Processing |
1.2.840.10008.5.1.4.1.1.1.3.1 |
No |
Yes |
CT Image Storage |
1.2.840.10008.5.1.4.1.1.2 |
No |
Yes |
Enhanced CT Image Storage |
1.2.840.10008.5.1.4.1.1.2.1 |
No |
Yes |
Legacy Converted Enhanced CT Image Storage |
1.2.840.10008.5.1.4.1.1.2.2 |
No |
Yes |
Ultrasound Multi-frame Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.3 |
No |
Yes |
Ultrasound Multi-frame Image Storage |
1.2.840.10008.5.1.4.1.1.3.1 |
No |
Yes |
MR Image Storage |
1.2.840.10008.5.1.4.1.1.4 |
No |
Yes |
Enhanced MR Image Storage |
1.2.840.10008.5.1.4.1.1.4.1 |
No |
Yes |
Enhanced MR Color Image Storage |
1.2.840.10008.5.1.4.1.1.4.3 |
No |
Yes |
Legacy Converted Enhanced MR Image Storage |
1.2.840.10008.5.1.4.1.1.4.4 |
No |
Yes |
Nuclear Medicine Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.5 |
No |
Yes |
Ultrasound Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.6 |
No |
Yes |
Ultrasound Image Storage |
1.2.840.10008.5.1.4.1.1.6.1 |
No |
Yes |
Enhanced US Volume Storage |
1.2.840.10008.5.1.4.1.1.6.2 |
No |
Yes |
Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7 |
No |
Yes |
Multi-frame Grayscale Byte Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7.2 |
No |
Yes |
Multi-frame Grayscale Word Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7.3 |
No |
Yes |
Multi-frame True Color Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7.4 |
No |
Yes |
X-Ray Angiographic Image Storage |
1.2.840.10008.5.1.4.1.1.12.1 |
No |
Yes |
Enhanced XA Image Storage |
1.2.840.10008.5.1.4.1.1.12.1.1 |
No |
Yes |
X-Ray Radiofluoroscopic Image Storage |
1.2.840.10008.5.1.4.1.1.12.2 |
No |
Yes |
Enhanced XRF Image Storage |
1.2.840.10008.5.1.4.1.1.12.2.1 |
No |
Yes |
X-Ray Angiographic Bi-Plane Image Storage (Retired) |
1.2.840.10008.5.1.4.1.1.12.3 |
No |
Yes |
X-Ray 3D Angiographic Image Storage |
1.2.840.10008.5.1.4.1.1.13.1.1 |
No |
Yes |
X-Ray 3D Craniofacial Image Storage |
1.2.840.10008.5.1.4.1.1.13.1.2 |
No |
Yes |
Breast Tomosynthesis Image Storage |
1.2.840.10008.5.1.4.1.1.13.1.3 |
No |
Yes |
Breast Projection X-Ray Image Storage - For Presentation |
1.2.840.10008.5.1.4.1.1.13.1.4 |
No |
Yes |
Breast Projection X-Ray Image Storage - For Processing |
1.2.840.10008.5.1.4.1.1.13.1.5 |
No |
Yes |
Intravascular Optical Coherence Tomography Image Storage - For Presentation |
1.2.840.10008.5.1.4.1.1.14.1 |
No |
Yes |
Intravascular Optical Coherence Tomography Image Storage - For Processing |
1.2.840.10008.5.1.4.1.1.14.2 |
No |
Yes |
Nuclear Medicine Image Storage |
1.2.840.10008.5.1.4.1.1.20 |
No |
Yes |
VL Image Storage - Trial (Retired) |
1.2.840.10008.5.1.4.1.1.77.1 |
No |
Yes |
VL Multi-frame Image Storage - Trial (Retired) |
1.2.840.10008.5.1.4.1.1.77.2 |
No |
Yes |
VL Endoscopic Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.1 |
No |
Yes |
VL Microscopic Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.2 |
No |
Yes |
VL Slide-Coordinates Microscopic Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.3 |
No |
Yes |
VL Photographic Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.4 |
No |
Yes |
Ophthalmic Photography 8 Bit Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.5.1 |
No |
Yes |
Ophthalmic Photography 16 Bit Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.5.2 |
No |
Yes |
Ophthalmic Tomography Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.5.4 |
No |
Yes |
Wide Field Ophthalmic Photography Stereographic Projection Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.5.5 |
No |
Yes |
Wide Field Ophthalmic Photography 3D Coordinates Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.5.6 |
No |
Yes |
Ophthalmic Optical Coherence Tomography En Face Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.5.7 |
No |
Yes |
Ophthalmic Optical Coherence Tomography B-scan Volume Analysis Storage |
1.2.840.10008.5.1.4.1.1.77.1.5.8 |
No |
Yes |
VL Whole Slide Microscopy Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.6 |
No |
Yes |
Dermoscopic Photography Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.7 |
No |
Yes |
Ophthalmic Thickness Map Storage |
1.2.840.10008.5.1.4.1.1.81.1 |
No |
Yes |
Corneal Topography Map Storage |
1.2.840.10008.5.1.4.1.1.82.1 |
No |
Yes |
Positron Emission Tomography Image Storage |
1.2.840.10008.5.1.4.1.1.128 |
No |
Yes |
Legacy Converted Enhanced PET Image Storage |
1.2.840.10008.5.1.4.1.1.128.1 |
No |
Yes |
Enhanced PET Image Storage |
1.2.840.10008.5.1.4.1.1.130 |
No |
Yes |
RT Image Storage |
1.2.840.10008.5.1.4.1.1.481.1 |
No |
Yes |
Enhanced RT Image Storage |
1.2.840.10008.5.1.4.1.1.481.23 |
No |
Yes |
Enhanced Continuous RT Image Storage |
1.2.840.10008.5.1.4.1.1.481.24 |
No |
Yes |
Private Fuji CR Image Storage |
1.2.392.200036.9125.1.1.2 |
No |
Yes |
Private GE Dicom CT Image Info Object |
1.2.840.113619.4.3 |
No |
Yes |
Private GE Dicom Display Image Info Object |
1.2.840.113619.4.4 |
No |
Yes |
Private GE Dicom MR Image Info Object |
1.2.840.113619.4.2 |
No |
Yes |
Private Philips CT Synthetic Image Storage |
1.3.46.670589.5.0.9 |
No |
Yes |
Private Philips CX Image Storage |
1.3.46.670589.2.4.1.1 |
No |
Yes |
Private Philips CX Synthetic Image Storage |
1.3.46.670589.5.0.12 |
No |
Yes |
Private Philips MR Color Image Storage |
1.3.46.670589.11.0.0.12.3 |
No |
Yes |
Private Philips MR Synthetic Image Storage |
1.3.46.670589.5.0.10 |
No |
Yes |
Private Philips Perfusion Image Storage |
1.3.46.670589.5.0.14 |
No |
Yes |
Private PixelMed Floating Point Image Storage |
1.3.6.1.4.1.5962.301.9 |
No |
Yes |
Private PixelMed Legacy Converted Enhanced CT Image Storage |
1.3.6.1.4.1.5962.301.1 |
No |
Yes |
Private PixelMed Legacy Converted Enhanced MR Image Storage |
1.3.6.1.4.1.5962.301.2 |
No |
Yes |
Private PixelMed Legacy Converted Enhanced PET Image Storage |
1.3.6.1.4.1.5962.301.3 |
No |
Yes |
Private PMOD Multi-frame Image Storage |
2.16.840.1.114033.5.1.4.1.1.130 |
No |
Yes |
Private Toshiba US Image Storage |
1.2.392.200036.9116.7.8.1.1.1 |
No |
Yes |
Video Storage SOP Classes: |
|||
Video Endoscopic Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.1.1 |
No |
Yes |
Video Microscopic Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.2.1 |
No |
Yes |
Video Photographic Image Storage |
1.2.840.10008.5.1.4.1.1.77.1.4.1 |
No |
Yes |
Structured Report Storage SOP Classes: |
|||
Spectacle Prescription Report Storage |
1.2.840.10008.5.1.4.1.1.78.6 |
No |
Yes |
Macular Grid Thickness and Volume Report Storage |
1.2.840.10008.5.1.4.1.1.79.1 |
No |
Yes |
Basic Text SR Storage |
1.2.840.10008.5.1.4.1.1.88.11 |
No |
Yes |
Enhanced SR Storage |
1.2.840.10008.5.1.4.1.1.88.22 |
No |
Yes |
Comprehensive SR Storage |
1.2.840.10008.5.1.4.1.1.88.33 |
No |
Yes |
Comprehensive 3D SR Storage |
1.2.840.10008.5.1.4.1.1.88.34 |
No |
Yes |
Extensible SR Storage |
1.2.840.10008.5.1.4.1.1.88.35 |
No |
Yes |
Procedure Log Storage |
1.2.840.10008.5.1.4.1.1.88.40 |
No |
Yes |
Mammography CAD SR Storage |
1.2.840.10008.5.1.4.1.1.88.50 |
No |
Yes |
Key Object Selection Document Storage |
1.2.840.10008.5.1.4.1.1.88.59 |
No |
Yes |
Chest CAD SR Storage |
1.2.840.10008.5.1.4.1.1.88.65 |
No |
Yes |
X-Ray Radiation Dose SR Storage |
1.2.840.10008.5.1.4.1.1.88.67 |
No |
Yes |
Radiopharmaceutical Radiation Dose SR Storage |
1.2.840.10008.5.1.4.1.1.88.68 |
No |
Yes |
Colon CAD SR Storage |
1.2.840.10008.5.1.4.1.1.88.69 |
No |
Yes |
Implantation Plan SR Storage |
1.2.840.10008.5.1.4.1.1.88.70 |
No |
Yes |
Acquisition Context SR Storage |
1.2.840.10008.5.1.4.1.1.88.71 |
No |
Yes |
Simplified Adult Echo SR Storage |
1.2.840.10008.5.1.4.1.1.88.72 |
No |
Yes |
Patient Radiation Dose SR Storage |
1.2.840.10008.5.1.4.1.1.88.73 |
No |
Yes |
Planned Imaging Agent Administration SR Storage |
1.2.840.10008.5.1.4.1.1.88.74 |
No |
Yes |
Performed Imaging Agent Administration SR Storage |
1.2.840.10008.5.1.4.1.1.88.75 |
No |
Yes |
Enhanced X-Ray Radiation Dose SR Storage |
1.2.840.10008.5.1.4.1.1.88.76 |
No |
Yes |
Other Storage SOP Classes: |
|||
Stored Print Storage SOP Class (Retired) |
1.2.840.10008.5.1.1.27 |
No |
Yes |
Hardcopy Grayscale Image Storage SOP Class (Retired) |
1.2.840.10008.5.1.1.29 |
No |
Yes |
Hardcopy Color Image Storage SOP Class (Retired) |
1.2.840.10008.5.1.1.30 |
No |
Yes |
MR Spectroscopy Storage |
1.2.840.10008.5.1.4.1.1.4.2 |
No |
Yes |
Multi-frame Single Bit Secondary Capture Image Storage |
1.2.840.10008.5.1.4.1.1.7.1 |
No |
Yes |
Standalone Overlay Storage (Retired) |
1.2.840.10008.5.1.4.1.1.8 |
No |
Yes |
Standalone Curve Storage (Retired) |
1.2.840.10008.5.1.4.1.1.9 |
No |
Yes |
12-lead ECG Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.1.1 |
No |
Yes |
General ECG Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.1.2 |
No |
Yes |
Ambulatory ECG Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.1.3 |
No |
Yes |
Hemodynamic Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.2.1 |
No |
Yes |
Cardiac Electrophysiology Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.3.1 |
No |
Yes |
Basic Voice Audio Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.4.1 |
No |
Yes |
General Audio Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.4.2 |
No |
Yes |
Arterial Pulse Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.5.1 |
No |
Yes |
Respiratory Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.6.1 |
No |
Yes |
Multi-channel Respiratory Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.6.2 |
No |
Yes |
Routine Scalp Electroencephalogram Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.7.1 |
No |
Yes |
Electromyogram Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.7.2 |
No |
Yes |
Electrooculogram Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.7.3 |
No |
Yes |
Sleep Electroencephalogram Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.7.4 |
No |
Yes |
Body Position Waveform Storage |
1.2.840.10008.5.1.4.1.1.9.8.1 |
No |
Yes |
Standalone Modality LUT Storage (Retired) |
1.2.840.10008.5.1.4.1.1.10 |
No |
Yes |
Standalone VOI LUT Storage (Retired) |
1.2.840.10008.5.1.4.1.1.11 |
No |
Yes |
Grayscale Softcopy Presentation State Storage SOP Class |
1.2.840.10008.5.1.4.1.1.11.1 |
No |
Yes |
Color Softcopy Presentation State Storage SOP Class |
1.2.840.10008.5.1.4.1.1.11.2 |
No |
Yes |
Pseudo-Color Softcopy Presentation State Storage SOP Class |
1.2.840.10008.5.1.4.1.1.11.3 |
No |
Yes |
Blending Softcopy Presentation State Storage SOP Class |
1.2.840.10008.5.1.4.1.1.11.4 |
No |
Yes |
XA/XRF Grayscale Softcopy Presentation State Storage |
1.2.840.10008.5.1.4.1.1.11.5 |
No |
Yes |
Grayscale Planar MPR Volumetric Presentation State Storage |
1.2.840.10008.5.1.4.1.1.11.6 |
No |
Yes |
Compositing Planar MPR Volumetric Presentation State Storage |
1.2.840.10008.5.1.4.1.1.11.7 |
No |
Yes |
Advanced Blending Presentation State Storage |
1.2.840.10008.5.1.4.1.1.11.8 |
No |
Yes |
Volume Rendering Volumetric Presentation State Storage |
1.2.840.10008.5.1.4.1.1.11.9 |
No |
Yes |
Segmented Volume Rendering Volumetric Presentation State Storage |
1.2.840.10008.5.1.4.1.1.11.10 |
No |
Yes |
Multiple Volume Rendering Volumetric Presentation State Storage |
1.2.840.10008.5.1.4.1.1.11.11 |
No |
Yes |
Parametric Map Storage |
1.2.840.10008.5.1.4.1.1.30 |
No |
Yes |
Raw Data Storage |
1.2.840.10008.5.1.4.1.1.66 |
No |
Yes |
Spatial Registration Storage |
1.2.840.10008.5.1.4.1.1.66.1 |
No |
Yes |
Spatial Fiducials Storage |
1.2.840.10008.5.1.4.1.1.66.2 |
No |
Yes |
Deformable Spatial Registration Storage |
1.2.840.10008.5.1.4.1.1.66.3 |
No |
Yes |
Segmentation Storage |
1.2.840.10008.5.1.4.1.1.66.4 |
No |
Yes |
Surface Segmentation Storage |
1.2.840.10008.5.1.4.1.1.66.5 |
No |
Yes |
Tractography Results Storage |
1.2.840.10008.5.1.4.1.1.66.6 |
No |
Yes |
Real World Value Mapping Storage |
1.2.840.10008.5.1.4.1.1.67 |
No |
Yes |
Surface Scan Mesh Storage |
1.2.840.10008.5.1.4.1.1.68.1 |
No |
Yes |
Surface Scan Point Cloud Storage |
1.2.840.10008.5.1.4.1.1.68.2 |
No |
Yes |
Stereometric Relationship Storage |
1.2.840.10008.5.1.4.1.1.77.1.5.3 |
No |
Yes |
Lensometry Measurements Storage |
1.2.840.10008.5.1.4.1.1.78.1 |
No |
Yes |
Autorefraction Measurements Storage |
1.2.840.10008.5.1.4.1.1.78.2 |
No |
Yes |
Keratometry Measurements Storage |
1.2.840.10008.5.1.4.1.1.78.3 |
No |
Yes |
Subjective Refraction Measurements Storage |
1.2.840.10008.5.1.4.1.1.78.4 |
No |
Yes |
Visual Acuity Measurements Storage |
1.2.840.10008.5.1.4.1.1.78.5 |
No |
Yes |
Ophthalmic Axial Measurements Storage |
1.2.840.10008.5.1.4.1.1.78.7 |
No |
Yes |
Intraocular Lens Calculations Storage |
1.2.840.10008.5.1.4.1.1.78.8 |
No |
Yes |
Ophthalmic Visual Field Static Perimetry Measurements Storage |
1.2.840.10008.5.1.4.1.1.80.1 |
No |
Yes |
Basic Structured Display Storage |
1.2.840.10008.5.1.4.1.1.131 |
No |
Yes |
Encapsulated PDF Storage |
1.2.840.10008.5.1.4.1.1.104.1 |
No |
Yes |
Encapsulated CDA Storage |
1.2.840.10008.5.1.4.1.1.104.2 |
No |
Yes |
Encapsulated STL Storage |
1.2.840.10008.5.1.4.1.1.104.3 |
No |
Yes |
Encapsulated OBJ Storage |
1.2.840.10008.5.1.4.1.1.104.4 |
No |
Yes |
Encapsulated MTL Storage |
1.2.840.10008.5.1.4.1.1.104.5 |
No |
Yes |
Standalone PET Curve Storage (Retired) |
1.2.840.10008.5.1.4.1.1.129 |
No |
Yes |
Text SR Storage Trial (Retired) |
1.2.840.10008.5.1.4.1.1.88.1 |
No |
Yes |
Audio SR Storage Trial (Retired) |
1.2.840.10008.5.1.4.1.1.88.2 |
No |
Yes |
Detail SR Storage Trial (Retired) |
1.2.840.10008.5.1.4.1.1.88.3 |
No |
Yes |
Comprehensive SR Storage Trial (Retired) |
1.2.840.10008.5.1.4.1.1.88.4 |
No |
Yes |
Content Assessment Results Storage |
1.2.840.10008.5.1.4.1.1.90.1 |
No |
Yes |
Microscopy Bulk Simple Annotations Storage |
1.2.840.10008.5.1.4.1.1.91.1 |
No |
Yes |
CT Performed Procedure Protocol Storage |
1.2.840.10008.5.1.4.1.1.200.2 |
No |
Yes |
XA Performed Procedure Protocol Storage |
1.2.840.10008.5.1.4.1.1.200.8 |
No |
Yes |
RT Dose Storage |
1.2.840.10008.5.1.4.1.1.481.2 |
No |
Yes |
RT Structure Set Storage |
1.2.840.10008.5.1.4.1.1.481.3 |
No |
Yes |
RT Beams Treatment Record Storage |
1.2.840.10008.5.1.4.1.1.481.4 |
No |
Yes |
RT Plan Storage |
1.2.840.10008.5.1.4.1.1.481.5 |
No |
Yes |
RT Brachy Treatment Record Storage |
1.2.840.10008.5.1.4.1.1.481.6 |
No |
Yes |
RT Treatment Summary Record Storage |
1.2.840.10008.5.1.4.1.1.481.7 |
No |
Yes |
RT Ion Plan Storage |
1.2.840.10008.5.1.4.1.1.481.8 |
No |
Yes |
RT Ion Beams Treatment Record Storage |
1.2.840.10008.5.1.4.1.1.481.9 |
No |
Yes |
RT Physician Intent Storage |
1.2.840.10008.5.1.4.1.1.481.10 |
No |
Yes |
RT Segment Annotation Storage |
1.2.840.10008.5.1.4.1.1.481.11 |
No |
Yes |
RT Radiation Set Storage |
1.2.840.10008.5.1.4.1.1.481.12 |
No |
Yes |
C-Arm Photon-Electron Radiation Storage |
1.2.840.10008.5.1.4.1.1.481.13 |
No |
Yes |
Tomotherapeutic Radiation Storage |
1.2.840.10008.5.1.4.1.1.481.14 |
No |
Yes |
Robotic-Arm Radiation Storage |
1.2.840.10008.5.1.4.1.1.481.15 |
No |
Yes |
RT Radiation Record Set Storage |
1.2.840.10008.5.1.4.1.1.481.16 |
No |
Yes |
RT Radiation Salvage Record Storage |
1.2.840.10008.5.1.4.1.1.481.17 |
No |
Yes |
Tomotherapeutic Radiation Record Storage |
1.2.840.10008.5.1.4.1.1.481.18 |
No |
Yes |
C-Arm Photon-Electron Radiation Record Storage |
1.2.840.10008.5.1.4.1.1.481.19 |
No |
Yes |
Robotic Radiation Record Storage |
1.2.840.10008.5.1.4.1.1.481.20 |
No |
Yes |
RT Radiation Set Delivery Instruction Storage |
1.2.840.10008.5.1.4.1.1.481.21 |
No |
Yes |
RT Treatment Preparation Storage |
1.2.840.10008.5.1.4.1.1.481.22 |
No |
Yes |
RT Patient Position Acquisition Instruction Storage |
1.2.840.10008.5.1.4.1.1.481.25 |
No |
Yes |
RT Beams Delivery Instruction Storage |
1.2.840.10008.5.1.4.34.7 |
No |
Yes |
RT Brachy Application Setup Delivery Instruction Storage |
1.2.840.10008.5.1.4.34.10 |
No |
Yes |
Private Agfa Arrival Transaction |
1.2.124.113532.3500.8.1 |
No |
Yes |
Private Agfa Basic Attribute Presentation State |
1.2.124.113532.3500.7 |
No |
Yes |
Private Agfa Dictation Transaction |
1.2.124.113532.3500.8.2 |
No |
Yes |
Private Agfa Report Approval Transaction |
1.2.124.113532.3500.8.4 |
No |
Yes |
Private Agfa Report Transcription Transaction |
1.2.124.113532.3500.8.3 |
No |
Yes |
Private ERAD Practice Builder Report Dictation Storage |
1.2.826.0.1.3680043.293.1.0.2 |
No |
Yes |
Private ERAD Practice Builder Report Text Storage |
1.2.826.0.1.3680043.293.1.0.1 |
No |
Yes |
Private GE 3D Model Storage |
1.2.840.113619.4.26 |
No |
Yes |
Private GE Collage Storage |
1.2.528.1.1001.5.1.1.1 |
No |
Yes |
Private GE eNTEGRA Protocol or NM Genie Storage |
1.2.840.113619.4.27 |
No |
Yes |
Private GE PET Raw Data Storage |
1.2.840.113619.4.30 |
No |
Yes |
Private GE RT Plan Storage |
1.2.840.113619.4.5.249 |
No |
Yes |
Private Philips 3D Object Storage |
1.3.46.670589.5.0.2.1 |
No |
Yes |
Private Philips 3D Object Storage (Retired) |
1.3.46.670589.5.0.2 |
No |
Yes |
Private Philips 3D Presentation State Storage |
1.3.46.670589.2.5.1.1 |
No |
Yes |
Private Philips Composite Object Storage |
1.3.46.670589.5.0.4 |
No |
Yes |
Private Philips HP Live 3D 01 Storage |
1.2.840.113543.6.6.1.3.10001 |
No |
Yes |
Private Philips HP Live 3D 02 Storage |
1.2.840.113543.6.6.1.3.10002 |
No |
Yes |
Private Philips Live Run Storage |
1.3.46.670589.7.8.1618510092 |
No |
Yes |
Private Philips MR Cardio Analysis Storage |
1.3.46.670589.5.0.11.1 |
No |
Yes |
Private Philips MR Cardio Analysis Storage (Retired) |
1.3.46.670589.5.0.11 |
No |
Yes |
Private Philips MR Cardio Profile Storage |
1.3.46.670589.5.0.7 |
No |
Yes |
Private Philips MR Cardio Storage |
1.3.46.670589.5.0.8.1 |
No |
Yes |
Private Philips MR Cardio Storage (Retired) |
1.3.46.670589.5.0.8 |
No |
Yes |
Private Philips MR Examcard Storage |
1.3.46.670589.11.0.0.12.4 |
No |
Yes |
Private Philips MR Series Data Storage |
1.3.46.670589.11.0.0.12.2 |
No |
Yes |
Private Philips MR Spectrum Storage |
1.3.46.670589.11.0.0.12.1 |
No |
Yes |
Private Philips Perfusion Storage |
1.3.46.670589.5.0.13 |
No |
Yes |
Private Philips Reconstruction Storage |
1.3.46.670589.7.8.16185100130 |
No |
Yes |
Private Philips Run Storage |
1.3.46.670589.7.8.16185100129 |
No |
Yes |
Private Philips Specialised XA Storage |
1.3.46.670589.2.3.1.1 |
No |
Yes |
Private Philips Surface Storage |
1.3.46.670589.5.0.3.1 |
No |
Yes |
Private Philips Surface Storage (Retired) |
1.3.46.670589.5.0.3 |
No |
Yes |
Private Philips Volume Set Storage |
1.3.46.670589.2.11.1.1 |
No |
Yes |
Private Philips Volume Storage |
1.3.46.670589.5.0.1.1 |
No |
Yes |
Private Philips Volume Storage (Retired) |
1.3.46.670589.5.0.1 |
No |
Yes |
Private Philips VRML Storage |
1.3.46.670589.2.8.1.1 |
No |
Yes |
Private Philips X-Ray MF Storage |
1.3.46.670589.7.8.1618510091 |
No |
Yes |
Private Siemens AX Frame Sets Storage |
1.3.12.2.1107.5.99.3.11 |
No |
Yes |
Private Siemens CSA Non Image Storage |
1.3.12.2.1107.5.9.1 |
No |
Yes |
Private Siemens CT MR Volume Storage |
1.3.12.2.1107.5.99.3.10 |
No |
Yes |
Private TomTec Annotation Storage |
1.2.276.0.48.5.1.4.1.1.7 |
No |
Yes |
These are the default SOP Classes supported. By altering the configuration it is possible to support additional or fewer SOP Classes.
4.2.1.2. Association Policies¶
4.2.1.2.1. General¶
The Storage Application Entity can both accept and propose Association Requests. The Storage Application Entity will accept Association Requests for the Verification, Storage, and Storage Commitment Push Model Services. It will propose Associations only for the Storage Commitment Push Model Service.
The DICOM standard Application Context Name for DICOM 3.0 is always accepted and proposed:
Application Context Name |
1.2.840.10008.3.1.1.1 |
4.2.1.2.2. Number of Associations¶
The Storage Application Entity can support multiple simultaneous Associations requested by peer AEs. The maximum total number of simultaneous Associations accepted from peer AEs is configurable. It is unlimited by default.
The Storage Application Entity initiates up to 5 Associations at a time for sending Storage Commitment Push Model N-EVENT-REPORTs to peer AEs.
Maximum number of simultaneous Associations requested by peer AEs |
No Maximum Limit (Configurable) |
Maximum number of simultaneous Associations initiated by the Storage Application Entity |
5 |
4.2.1.2.3. Asynchronous Nature¶
The Storage Application Entity supports asynchronous communication (multiple outstanding transactions over a single Association). The maximum number of outstanding asynchronous transactions is configurable. It is unlimited by default.
Maximum number of outstanding asynchronous transactions |
No Maximum Limit (Configurable) |
There is no limit on the number of outstanding Storage Commitment Push Model Requests that can be received and acknowledged before the Storage Application Entity has responded with the corresponding N-EVENT-REPORT Notifications.
4.2.1.2.4. Implementation Identifying Information¶
The implementation information for the Storage Application Entity is:
Implementation Class UID |
1.2.40.0.13.1.3 |
Implementation Version Name |
dcm4che-5.xx.yy |
All Application Entities of dcm4che DICOM Archive 5 use the same Implementation Version Name. This Version Name is updated with each new release of the product software.
4.2.1.3. Association Initiation Policies¶
4.2.1.3.1. Activity - Send Storage Commitment Notification Over New Association¶
4.2.1.3.1.1. Description and Sequencing of Activity¶
The Storage Application Entity does not support to send the Storage Commitment Notification over the same Association over which it received the Storage Commitment Push Model (N-ACTION) request from the remote AE. It always initiates a new Association to the remote AE that sent the Storage Commitment Push Model request for sending the corresponding Storage Commitment Notification (N-EVENT-REPORT).
If any type of error occurs during transmission (either a communication failure or indicated by a Status Code returned by the remote AE), the Storage Application Entity will attempt to resend an N-EVENT-REPORT. The maximum number of attempts to resend an N-EVENT-REPORT is configurable, along with the amount of time to wait between attempts to resend.
Fig. 4.8 Remote AE Requests Storage Commitment¶
4.2.1.3.1.2. Proposed Presentation Contexts¶
The Storage Application Entity will propose Presentation Contexts for the Storage Commitment Push Model SOP Class. The list of proposed Transfer Syntaxes for the Storage Commitment Push Model SOP Class is configurable. By default, only the Transfer Syntax Implicit VR Little Endian will be proposed.
Presentation Context Table |
|||||
|---|---|---|---|---|---|
Abstract Syntax |
Transfer Syntax |
Role |
Ext. Neg. |
||
Name |
UID |
Name |
UID |
||
Storage Commitment Push Model |
1.2.840.10008.1.20.1 |
Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
4.2.1.3.1.3. SOP Specific Conformance for Storage Commitment Push Model SOP Class¶
The Storage Application Entity only accepts Storage Commitment Push Model N-ACTION Requests from Remote AEs which AE Title is configured.
The Storage Application Entity takes the list of Composite SOP Instance UIDs specified in a Storage Commitment Push Model N-ACTION Request and checks if they are present in the database. Each present Composite SOP Instance will be fetched from the storage recalculating its checksum. The Storage Application Entity will only commit to responsibility for SOP Instances which recalculated checksum matches the value from the database, which was calculated on receive of the SOP Instance.
Once the Storage Application Entity has checked for the existence and matching of the checksum of the specified Composite SOP Instances, it will then attempt to send the Notification request (N-EVENT-REPORT-RQ) over a new Association. The Storage Application Entity will request a new Association with the peer AE that made the original N-ACTION Request.
The Storage Application Entity will not cache Storage Commitment Push Model N-ACTION Requests that specify Composite SOP Instances that have not yet been transferred to dcm4che DICOM Archive 5. If a remote AE sends a Storage Commitment Push Model N-ACTION Request before the specified Composite SOP Instances, the Storage Application Entity will not commit to responsibility for such SOP Instances.
The amount of time to take responsibility for the safekeeping of an objects is independent of the successful commitment to store the object, but depends on other configuration options, particularly on the configured Study Retention Policy. It is even possible to accept storage commitment requests when acting as a cache archive, which deletes least recent accessed studies according configured thresholds of the storage backend.
The Storage Application Entity does not support the optional Storage Media File-Set ID & UID attributes in the N-ACTION and in the N-EVENT-REPORT.
The Storage Application Entity supports the optional Retrieve AE Title (0008,0054) Attribute in the N-EVENT-REPORT.
The Storage Application Entity supports Storage Commitment Push Model requests for SOP Instances of any Storage SOP Class.
4.2.1.4. Association Acceptance Policy¶
4.2.1.4.1. Activity - Receive Images and Storage Commitment Requests¶
4.2.1.4.1.1. Description and Sequencing of Activities¶
The Storage Application Entity can be configured to only accept Associations with certain hosts (using TCP/IP address) and/or Application Entity Titles.
4.2.1.4.1.2. Accepted Presentation Contexts¶
The Storage Application Entity will accept Presentation Contexts for all SOP Classes listed in Table 4.2.1.1-1 by default. The list of accepted Transfer Syntaxes for each accepted Abstract Syntax - as the list of accepted Abstract Syntaxes itselfs - is configurable.
Presentation Context Table |
|||||
|---|---|---|---|---|---|
Abstract Syntax |
Transfer Syntax |
Role |
Ext. Neg. |
||
Name |
UID |
Name |
UID |
||
Verification |
1.2.840.10008.1.1 |
Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
Storage Commitment Push Model |
1.2.840.10008.1.20.1 |
Implicit VR Little Endian |
1.2.840.10008.1.2 |
SCP |
None |
Image Storage SOP Classes in SOP Classes for Storage Application Entity (SCP) |
SCP |
None |
|||
Video Storage SOP Classes in SOP Classes for Storage Application Entity (SCP) |
SCP |
None |
|||
SR Storage SOP Classes in SOP Classes for Storage Application Entity (SCP) |
SCP |
None |
|||
Other Storage SOP Classes in SOP Classes for Storage Application Entity (SCP) |
SCP |
None |
|||
Transfer Syntax Name |
UID |
|---|---|
Implicit VR Little Endian |
1.2.840.10008.1.2 |
Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
JPEG Baseline (Process 1) |
1.2.840.10008.1.2.4.50 |
JPEG Extended (Process 2 & 4) |
1.2.840.10008.1.2.4.51 |
JPEG Lossless, Non-Hierarchical (Process 14) |
1.2.840.10008.1.2.4.54 |
JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]) |
1.2.840.10008.1.2.4.70 |
JPEG-LS Lossless |
1.2.840.10008.1.2.4.80 |
JPEG-LS Lossy (Near-Lossless) |
1.2.840.10008.1.2.4.81 |
JPEG 2000 (Lossless Only) |
1.2.840.10008.1.2.4.90 |
JPEG 2000 |
1.2.840.10008.1.2.4.91 |
High-Throughput JPEG 2000 (Lossless Only) |
1.2.840.10008.1.2.4.201 |
High-Throughput JPEG 2000 with RPCL (Lossless Only) |
1.2.840.10008.1.2.4.202 |
High-Throughput JPEG 2000 |
1.2.840.10008.1.2.4.203 |
RLE Lossless |
1.2.840.10008.1.2.5 |
Transfer Syntax Name |
UID |
|---|---|
JPEG Baseline (Process 1) |
1.2.840.10008.1.2.4.50 |
MPEG2 Main Profile @ Main Level |
1.2.840.10008.1.2.4.100 |
Fragmentable MPEG2 Main Profile @ Main Level |
1.2.840.10008.1.2.4.100.1 |
MPEG2 Main Profile @ High Level |
1.2.840.10008.1.2.4.101 |
Fragmentable MPEG2 Main Profile @ High Level |
1.2.840.10008.1.2.4.101.1 |
MPEG-4 AVC/H.264 High Profile / Level 4.1 |
1.2.840.10008.1.2.4.102 |
Fragmentable MPEG-4 AVC/H.264 High Profile / Level 4.1 |
1.2.840.10008.1.2.4.102.1 |
MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 |
1.2.840.10008.1.2.4.103 |
Fragmentable MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 |
1.2.840.10008.1.2.4.103.1 |
MPEG-4 AVC/H.264 High Profile / Level 4.2 For 2D Video |
1.2.840.10008.1.2.4.104 |
Fragmentable MPEG-4 AVC/H.264 High Profile / Level 4.2 For 2D Video |
1.2.840.10008.1.2.4.104.1 |
MPEG-4 AVC/H.264 High Profile / Level 4.2 For 3D Video |
1.2.840.10008.1.2.4.105 |
Fragmentable MPEG-4 AVC/H.264 High Profile / Level 4.2 For 3D Video |
1.2.840.10008.1.2.4.105.1 |
MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 |
1.2.840.10008.1.2.4.106 |
Fragmentable MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 |
1.2.840.10008.1.2.4.106.1 |
HEVC/H.265 Main Profile / Level 5.1 |
1.2.840.10008.1.2.4.107 |
HEVC/H.265 Main 10 Profile / Level 5.1 |
1.2.840.10008.1.2.4.108 |
Transfer Syntax Name |
UID |
|---|---|
Implicit VR Little Endian |
1.2.840.10008.1.2 |
Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
Deflated Explicit VR Little Endian |
1.2.840.10008.1.2.1.99 |
Transfer Syntax Name |
UID |
|---|---|
Implicit VR Little Endian |
1.2.840.10008.1.2 |
Explicit VR Little Endian |
1.2.840.10008.1.2.1 |
If multiple Transfer Syntaxes are proposed per Presentation Context the order of Transfer Syntax preference is defined by the order in the proposed Presentation Context.
4.2.1.4.1.3. SOP Specific Conformance for Verification SOP Class¶
The Storage Application Entity provides standard conformance to the Verification SOP Class as an SCP.
4.2.1.4.1.4. SOP Specific Conformance for Storage SOP Class¶
The associated Activity with the Storage service is the storage of medical image data received over the network on a designated hard disk. The Storage Application Entity will return a failure status if it is unable to store the images on to the hard disk.
The Storage Application Entity does not have any dependencies on the number of Associations used to send images to it. Images belonging to more than one Study or Series can be sent over a single or multiple Associations. Images belonging to a single Study or Series can also be sent over different Associations. There is no limit on either the number of SOP Instances or the maximum amount of total SOP Instance data that can be transferred over a single Association.
The Storage Application Entity retains the original DICOM data in DICOM Part 10 compliant file format. The Storage Application Entity is Level 2 (Full) conformant as a Storage SCP. In addition, all Private and SOP Class Extended Elements are maintained in the DICOM format files.
In addition to saving all Elements in files, a subset of the Elements are stored in the archive database to support query and retrieval requests and also allow updating of Patient, Study, and Series information by user input, or demographic and Study related messages.
The behavior for handling duplicate SOP Instances is configurable by selecting one of 5 available Overwrite Policies:
- NEVER:
Never overwrite stored Instances on receive of a different Instance with equal SOP Instance UID. Ignore the received instance silently - returning a success status.
- ALWAYS:
Always overwrite stored Instances by subsequently received Instances with equal SOP Instance UID.
- SAME_SOURCE (default):
Only overwrite stored Instances by subsequently received Instances with equal SOP Instance UID, if the new Instance was sent from the same Source Application Entity or HTTP client as the previous received Instance. Otherwise ignore the received instance silently - returning a success status.
- SAME_SERIES:
Only overwrite stored Instances by subsequently received Instances with equal SOP Instance UID, if the new Instance belongs to the same Series as the previous received Instance (= if beside the SOP Instance UID, also Study and Series Instance UID are equal). Otherwise store the received instance additionally to the previous received Instance.
- SAME_SOURCE_AND_SERIES:
Only overwrite stored Instances by subsequently received Instances with equal SOP Instance UID, if the new Instance was sent from the same Source Application Entity or HTTP client as the previous received Instance, and if the new Instance belongs to the same Series as the previous received Instance (= if beside the SOP Instance UID, also Study and Series Instance UID are equal). Otherwise ignore the received instance silently or store the received instance additionally to the previous received Instance, dependent if it belongs to the same Series or not.
The behavior for updating Patient, Study and Series Attributes in the archive database, if there values differs between received Instances of the same Patient, Study and Series is configurable for each Entity Level by selecting one of 4 Attribute Update Policies:
- NONE:
Do not update the Attributes of the Entity in the database from its initial values extracted from the first received Instance of the Entity.
- SUPPLEMENT (default for Patient Attributes):
Supplement the Attributes of the Entity in the database with Attributes of subsequently received Instances which were not present or had no value in previous received Instances of the same Entity.
- MERGE (default for Study and Series Attributes):
Overwrite the Attributes of the Entity in the database with non-empty Attributes from subsequently received Instances of the same Entity.
- OVERWRITE:
Overwrite the Attributes of the Entity in the database with all Attributes from subsequently received Instances of the same Entity.
The Storage Application Entity can be configured to compress uncompressed received Image SOP Instances, dependent on the Source Application Entity or HTTP client and dependent of DICOM Attribute values of received SOP Instances, using one of following Transfer Syntaxes:
Transfer Syntax Name |
UID |
|---|---|
JPEG Baseline (Process 1) |
1.2.840.10008.1.2.4.50 |
JPEG Extended (Process 2 & 4) |
1.2.840.10008.1.2.4.51 |
JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]) |
1.2.840.10008.1.2.4.70 |
JPEG-LS Lossless |
1.2.840.10008.1.2.4.80 |
JPEG 2000 (Lossless Only) |
1.2.840.10008.1.2.4.90 |
JPEG 2000 |
1.2.840.10008.1.2.4.91 |
By default, no image compression is configured.
Service Status |
Further Meaning |
Error Code |
Error Comment |
Behaviour |
|---|---|---|---|---|
Success |
Success |
0000 |
The Composite SOP Instance was successfully received, verified, and stored in the system database. |
|
Refused |
Out of Resources |
A700 |
Indicates that there was not enough disk space to store the image. Error message is output to the Service Log. The SOP Instance will not be saved. |
|
Duplicate Rejection Note |
A770 |
Rejection Note [uid={SOP Instance UID}] already received. |
Indicates that rejection note was already received. |
|
Subsequent Occurrence of Rejected Object |
A771 |
Subsequent occurrence of rejected Object [uid={SOP Instance UID}, rejection={Rejection Note Code}] |
Indicates that there was a subsequent occurrence of a rejected object during store operation. |
|
Rejection Failed - No Such Instance |
A772 |
Failed to reject Instance[uid={SOP Instance UID}] - no such Instance. |
Indicates that one or more objects were not previously stored in archive to be rejected. |
|
Rejection Failed - Class Instance Conflict |
A773 |
Failed to reject Instance[uid={SOP Instance UID}] - class-instance conflict. |
Indicates that there was a conflict in SOP Class UIDs of object (between that of the previously received object and the one referenced in the current rejection note) to be rejected. |
|
Rejection Failed - Already Rejected |
A774 |
Failed to reject Instance[uid={SOP Instance UID}] - already rejected. |
Indicates that the rejected object was already rejected. |
|
Rejection for Retention Policy Expired not Authorized |
A775 |
Rejection for Retention Policy Expired not authorized. |
Indicates that rejection of objects with type as Retention Expired are not allowed by LDAP configuration. |
|
Retention Period of Study not yet Expired |
A776 |
Retention Period of Study not yet expired. |
Indicates that rejection of objects is not allowed as Study Retention Period has not expired yet. |
|
No Patient ID (from trusted Assigning Authority) in object. |
A777 |
Storage denied as Patient ID missing in object. |
Indicates that the Patient ID is missing in the object or is not from a trusted Assigning Authority. |
|
Conflicting Patient ID in Object |
A778 |
Patient ID in incoming object does not match with that of patient associated with study. |
Indicates that the Patient ID in incoming object does not match with that of patient associated with study. |
|
Conflicting Patient Attributes in Object |
A779 |
Patient differs from previous received object in attribute {Keyword <Tag>}. |
Indicates that the Patient in incoming object has differing attributes with that of same patient associated with previous received object. |
|
Different Study Instance UID |
C409 |
Study Instance UID differs from Accepted Study Instance UID. |
Indicates that Accepted Study Instance UID varies from the Study Instance UID received in the request body. |
|
Failed to parse DICOM stream |
C499 |
Receive of non(-valid) DICOM stream |
Indicates that non(-valid) DICOM stream was received in the request body. |
|
Not Authorized |
0124 |
Storage denied. |
Indicates that the storage is denied. |
|
Error |
Data Set does not match SOP Class |
A900 |
Indicates that the Data Set does not encode a valid instance of the SOP Class specified. This status is returned if the DICOM Object stream can be successfully parsed but does not contain values for one or more mandatory Elements of the SOP Class. The STORAGE-SCP AE does not perform a comprehensive check, as it only checks a subset of required Elements. In addition, if the SOP Class is for a type of image but the SOP Instance does not contain values necessary for its display then this status is returned. Error message is output to the Service Log. The system can be configured to temporarily save such Data Sets in order to aid problem diagnosis. |
|
Cannot understand |
C000 |
Indicates that the STORAGE-SCP AE cannot parse the Data Set into Elements. Error message is output to the Service Log. The system can be configured to temporarily save such Data Sets in order to aid problem diagnosis. |
||
Failed to parse DICOM stream |
C499 |
Indicates that the STORAGE-SCP AE failed to parse received object. |
||
Warning |
Coercion of Data Elements |
B000 |
Indicates that one or more Element values were coerced. Refer to the Attributes defined in Annex for a list of those that can be coerced. Note that return of this status is disabled by default, as some SCUs treat it as an Error code rather than a Warning. |
Note : If a failure condition does occur when handling an Association then all images previously received successfully over the Association are maintained in the DCM4CHEE archive database. No previously successfully received images are discarded. Even if an image is successfully received but an error occurs transmitting the C-STORE Response then this final image is maintained rather than discarded. If the loss of an Association is detected then the Association is closed. In the above table, some references to rejection error codes in Refused Service Status is due to the fact that, when objects are rejected the rejection notes are stored in the database for further processing.
The Behavior of Storage Application Entity during communication failure is summarized in the following table:
Exception |
Reason |
|---|---|
Timeout expiry for an expected DICOM Message Request (DIMSE level timeout). I.e. The STORAGE-SCP AE is waiting for the next C-STORE Request on an open Association but the timer expires. |
The Association is aborted by issuing a DICOM A-ABORT. Error message is output to the Service Log. If some Composite SOP Instances have already been successfully received then they are maintained in the database. They are not automatically discarded because of a later failure. |
Timeout expiry for an expected DICOM PDU or TCP/IP packet (Low-level timeout). I.e. The STORAGE-SCP AE is waiting for the next C-STORE Data Set PDU but the timer expires. |
The Association is aborted by issuing a DICOM A-ABORT. Error message is output to the Service Log. If a C-STORE Data Set has not been fully received then the data already received is discarded. If some Composite SOP Instances have already been successfully received over the Association then they are maintained in the database. |
Association aborted by the SCU or the network layers indicate communication loss (i.e., low-level TCP/IP socket closure) |
Error message is output to the Service Log. If some Composite SOP Instances have already been successfully received then they are maintained in the database. They are not automatically discarded because of a later failure. |
4.2.1.4.1.5. SOP Specific Conformance for Storage Commitment SOP Class¶
The associated Activity with the Storage Commitment Push Model service is the communication by the Storage Application Entity to peer AEs that it has committed to permanently store Composite SOP Instances that have been sent to it. It thus allows peer AEs to determine whether the DCM4CHEE archive has taken responsibility for the archiving of specific SOP Instances so that they can be flushed from the peer AE system. The Storage Application Entity takes the list of Composite SOP Instance UIDs specified in a Storage Commitment Push Model N-ACTION Request and checks if they are present in the DCM4CHEE archive database. As long as the Composite SOP Instance UIDs are present in the database, the Storage Application Entity will consider those Composite SOP Instance UIDs to be successfully archived. The Storage Application Entity does not require the Composite SOP Instances to actually be successfully written to archive media in order to commit to responsibility for maintaining these SOP Instances. Once the Storage Application Entity has checked for the existence of the specified Composite SOP Instances, it will then attempt to send the Notification request (N-EVENT-REPORT-RQ). The default behavior is to attempt to send this Notification over the same Association that was used by the peer AE to send the original N-ACTION Request. If the Association has already been released or Message transfer fails for some reason then the Storage Application Entity will attempt to send the N-EVENT-REPORT-RQ over a new Association. The Storage Application Entity will request a new Association with the peer AE that made the original N-ACTION Request. The Storage Application Entity can be configured to always open a new Association in order to send the Notification request. The Storage Application Entity will not cache Storage Commitment Push Model N-ACTION Requests that specify Composite SOP Instances that have not yet been transferred to the DCM4CHEE archive. If a peer AE sends a Storage Commitment Push Model N-ACTION Request before the specified Composite SOP Instances are later sent over the same Association, the Storage Application Entity will not commit to responsibility for such SOP Instances. The Storage Application Entity does not support the optional Storage Media File-Set ID & UID attributes in the N-ACTION. The DCM4CHEE archive never automatically deletes Composite SOP Instances from the archive. The absolute persistence of SOP Instances and the maximum archiving capacity for such SOP Instances is dependent on the archiving media and capacity used by the DCM4CHEE archive and is dependent on the actual specifications of the purchased system. It is necessary to check the actual system specifications to determine these characteristics. The Storage Application Entity will support Storage Commitment Push Model requests for SOP Instances of any of the Storage SOP Classes that are also supported by the Storage Application Entity as given in 4.2.1.1-1.: SOP Classes for Storage Application Entity (SCP)
The Storage Application Entity will return the following Status Code values in N-ACTION Responses:
Service Status |
Further Meaning |
Error Code |
Behaviour |
|---|---|---|---|
Success |
Success |
0000 |
The SCP has successfully received the Storage Commitment Push Model N-ACTION Request and can process the commitment request for the indicated SOP Instances. |
Error |
Processing Failure |
0110 |
Indicates that the Storage Commitment Push Model N-ACTION Request cannot be parsed or fully processed due to a database or system failure. |
The Storage Application Entity will exhibit the following Behavior according to the Status Code value returned in an N-EVENT-REPORT Response from a destination Storage Commitment Push Model SCU:
Service Status |
Further Meaning |
Error Code |
Behaviour |
|---|---|---|---|
Success |
Success |
0000 |
The SCU has successfully received the Storage Commitment Push Model N-EVENT-REPORT Request. Success indication message is output to the Service Logs. No message is posted to the User Interface. |
Warning |
Attribute List Error |
0107 |
Transmission of Storage Commitment Push Model N-EVENT-REPORT Request is considered successful. Warning indication message is output to the Service Logs. No message is posted to the User Interface. |
Any other status code. |
This is treated as a permanent Failure. Error indication message is output to the Service Logs. No message is posted to the User Interface. |
All Status Codes indicating an error or refusal are treated as a permanent failure. The Storage Application Entity can be configured to automatically reattempt the sending of Storage Commitment Push Model N-EVENT-REPORT Requests if an error Status Code is returned or a communication failure occurs. The maximum number of times to attempt sending as well as the time to wait between attempts is configurable.