A C-STORE request and a Storage Commitment request answer different questions. C-STORE asks a receiving application entity to accept transmitted SOP Instances; the DICOM Storage Service Class, as PS3.4 describes it, does not specify that the receiver explicitly takes responsibility for safekeeping the data, and there is no commitment that the SCP will do more than accept what was sent [1]. Storage Commitment exists to close that gap: it is an application-level class of service through which an SCU asks an SCP to commit to keeping referenced instances for an implementation-specific period so they can later be retrieved [1]. The practical consequence is that a successful C-STORE response and a successful Storage Commitment notification are not interchangeable evidence, and treating them as such is where integration assumptions usually begin.

Two Services, Two Different Records of Success

The Storage Service Class is a communication mechanism. PS3.4 states plainly that the mechanism currently defined for network-based storage of SOP Instances allows an SCU to transmit images and other Composite SOP Instances to an SCP, but does not specify that the SCP explicitly take responsibility for safekeeping into account [1]. A C-STORE response therefore records that an instance was accepted in a particular association, not that it will remain retrievable. That is a narrow but consequential boundary, because the sender's local retention policy often depends on what the receiver's response is taken to mean.

Storage Commitment is a separate normalized exchange. The Society for Imaging Informatics in Medicine describes the sequence as a modality issuing an N_ACTION command containing a list of images for which commitment is requested, with the receiver replying through an N_EVENT REPORT that names the objects it is committed to store and those it could not store [4]. PS3.2's conformance template mirrors this: an SCU of the Storage Commitment SOP Class uses the N-ACTION-RQ message to request commitment and in turn receives N-EVENT-REPORT-RQ [6]. The record of success is a notification about a set of referenced instances, not a per-instance transfer acknowledgement.

Who Owns the Promise, and for How Long

The commitment is defined by the SCP implementation, not by the standard. PS3.4 says the SCP defines how it provides its commitment: some SCPs may commit to permanently store instances, such as an archive system, while others may commit to storage for a limited amount of time [1]. The standard also requires the SCP to document the nature of its commitment in its Conformance Statement, including duration of storage, retrieve capabilities and latency, and capacity [1]. Those four disclosures are the operative content of a commitment claim; a product that supports the SOP Class but leaves them vague has told an integrator relatively little.

The standard also constrains what can count as commitment. Possession of a link to access pixel data is not sufficient for the SCP to commit to storage; a copy of the entire pixel data is required, a note PS3.4 attaches to the JPIP Referenced Pixel Data Transfer Syntax situation [1]. The AE where instances can later be retrieved may be the SCP that accepted commitment or a distinct entity [1]. That second point matters in architectures where a PACS fronts a long-term store: the entity answering the notification is not necessarily the entity holding the bytes.

Practical detail: the four questions to ask before deleting local copies

Before treating a Storage Commitment notification as permission to delete, ask the receiving SCP for its documented storage duration, retrieve capabilities and latency, and capacity, since PS3.4 requires those in the Conformance Statement [1]. Then confirm whether the AE that will serve retrieval is the committing SCP or a distinct entity [1], whether the notification arrived on the same or a new association and what happens if the association cannot be established [6], and whether the archive is configured for long-term retention at all, a limitation GE HealthCare states for Enterprise Archive 8 [8]. Record the Transaction UID so the notification can be matched to the request [4].

The Push Model and Its Retired Alternative

Storage Commitment requests travel through the Push Model. The SCU transmits SOP Instances to an SCP using an appropriate mechanism outside the scope of the service class, then initiates commitment by sending a request containing references to one or more SOP Instances, with success or failure indicated later by notification from the SCP [1]. PS3.4 notes that typical transfer mechanisms are found in the Storage Service Class, the Query/Retrieve Service Class, or Media Exchange [1]. The separation is deliberate: commitment is about references to instances already conveyed, not about the conveyance itself.

PS3.4 records that a Pull Model was defined in earlier versions but has been retired [1]. PS3.4 also requires that an SCP implementation of the Storage Commitment Service Class support the Storage Commitment Push Model SOP Class, and that support for SCP/SCU Role Selection Negotiation is mandatory while SOP Class Extended Negotiation shall not be supported [2]. For an integrator reading a conformance statement, the presence of the Push Model SOP Class is the baseline; the interesting variables sit in the timing, association and durability disclosures around it.

Timing, Associations and Asynchronous Replies

The reply need not arrive on the association that carried the request. SIIM notes the reply can be exchanged on the same or a different Association, and that the specific transaction reported on is identified by the Transaction UID specified in the request [4]. Orthanc's documentation states that Orthanc assumes storage commitment responses are sent asynchronously, which it describes as corresponding to most implementations, and its SCP workflow uses three associations: the C-STORE transfer, the commitment request, and the asynchronous response [5]. Orthanc has implemented storage commitment as both SCP and SCU since release 1.6.0 [5].

Vendor conformance statements show how much this varies. GE HealthCare's Enterprise Archive 8 conformance statement describes receiving N-ACTION requests from remote SCUs to confirm permanent storage of previously transmitted instances, evaluating whether requested instances are present and eligible, and returning the result through an N-EVENT-REPORT sent on a newly established association [8]. The same document lists a fixed behavior of asynchronous N-EVENT-REPORT on a new association, a configurable delay before sending N-ACTION-RQ, and a fixed immediate send of N-EVENT-REPORT once N-ACTION-RQ is received [8]. Those are implementation parameters, not standard requirements, and they belong in integration design.

What Conformance Statements Must Disclose, and What They Often Leave Out

PS3.2's template asks implementers to describe the actions and behavior that cause a product to issue N-ACTION requests and how that relates to the previous storage request, for example whether commitment is initiated right after a successful C-STORE or after all instances in the study have been stored [6]. It also asks about association initiation behavior for N-EVENT-REPORT, whether the request goes on the same association or a different one, and what the system does if it cannot establish an association with the SCU, including any retry mechanism and whether it is configurable [6]. These questions are the practical substance of a commitment interface.

The SCU side carries its own disclosure duty. PS3.4 states that once the SCP has committed to store the SOP Instances, the SCU may decide it is appropriate to delete its copies, and that these behaviors are outside the scope of the standard, but the SCU is required to document them in its Conformance Statement [1]. PS3.18, which specifies web services for managing and distributing DICOM Information Objects, defines a Storage Commitment Service that corresponds to the DIMSE service class in PS3.4 and has the same semantics, splitting the exchange into requesting commitment and, where the origin server cannot yet give a result, checking for the result [3]. A PACS may wait with its response until a VNA used for long-term storage has given commitment for the referenced instances [3].

A Validation Scenario for Integration Teams

Consider a hypothetical, suggested acceptance exercise rather than a documented test result. A modality sends a small study to an archive by C-STORE, then issues a Storage Commitment request referencing those SOP Instances by SOP Instance UID and SOP Class UID, as Orthanc describes for its SCP [5]. The team records which association carried the request, whether the notification arrived on the same or a new association, and how long the interval was. It then compares the notification's referenced instances against the original list, including any failures, and confirms whether the archive's conformance statement documents storage duration, retrieve latency and capacity as PS3.4 requires [1].

The exercise should also probe the boundary the standard leaves open. Because the SCP defines its commitment and may commit for a limited period [1], a team cannot infer permanence from a successful notification alone. GE HealthCare's Enterprise Archive 8 conformance statement states that EA may be configured without long-term archiving, which affects what successful storage commitment means in that configuration [8]. Reading that limitation alongside the same document's description of confirming permanent storage is the kind of check that separates a defensible retention policy from an assumption. The unresolved question for any site is what its own archive configuration actually promises, and only the operator and vendor can answer it.

Where the Comparison Actually Bites

The two services differ in record ownership. C-STORE produces a transfer-level response owned by the receiving Storage SCP; Storage Commitment produces a notification about a referenced set, tied to a Transaction UID and governed by the SCP's documented commitment [1][4]. Inputs differ too: C-STORE carries the instance data set, while a commitment request carries references to instances conveyed by some other mechanism [1]. Outputs differ in kind: an acceptance status versus a statement about safekeeping over an implementation-specific period, with the retrieve location possibly distinct from the committing SCP [1].

Deployment boundaries follow from that. Orthanc exposes storage commitment SCU behavior through REST routes introduced in release 1.6.0, including initiating a request against a configured remote modality, retrieving transaction status, and removing instances reported as successfully stored, with removal available only for fully successful reports [5]. GE HealthCare documents configurable calling and called AE Titles defaulting to the Storage service values, port 104 and TLS-secured port 2762 [8]. Neither set of details generalizes to other products. What remains unknown for any given deployment is the actual durability behind a commitment, which the conformance statement is supposed to state and which an integrator should read before deleting anything.