DICOM PS3.2 2016c - Conformance

J.4 Networking
Prev | J Conformance Statement Sample STOW Service (Informative) | Next

## J.4 Networking

### J.4.1 Implementation Model

#### J.4.1.1 Application Data Flow

Example STOW Service

Figure J.4.1-1. Application Data Flow Diagram

The STOW-RS Service Application receives STOW requests from a remote AE. These requests are HTTP POST requests. It is associated with the local real-world activity "Store Instances". It converts these requests into internal functions to store the given SOP Instances. It returns a summary HTTP status line, including a status code and an associated textual phase, followed by an XML message indicating success, warning, or failure for each instance to the requesting remote AE.

#### J.4.1.2 Functional Definition of AEs

##### J.4.1.2.1 Functional Definition of STOW Service Application

The reception of a STOW-RS POST request will activate the STOW-RS Service. The storage request is based upon the accept headers in the STOW-RS POST request. The response includes an HTTP status line, including a status-code and its associated textual phrase, followed by an XML message indicating success, warning, or failure for each instance stored by the STOW-RS service.

Prev | Up | Next
J.3.3 Additional Remarks for This Example | Home | J.4.2 AE Specifications

DICOM PS3.2 2016c - Conformance