DICOM PS3.2 2025d - Conformance
N.7.3.3.8 Modality Performed Procedure Step Service
N.7.3.3.8.1 Create Transaction As Origin Server

Table N.7.3.3.8.1-1 lists the Status Codes that an origin server supports for the Create Transaction of the Modality Performed Procedure Step Service and the condition in which any of the listed Status Codes is sent.

[Describe below the condition in which the application sends the specific Status Codes in the Create Transaction response as origin server.]

Table N.7.3.3.8.1-1. Status Codes of Origin Server for Create Transaction

Status

Code

Condition

Success

201 (Created)

The origin server has created the requested Modality Performed Procedure Step with the provided attributes

Failure

400 (Bad Request)

The origin server cannot handle the create request because of errors in the request headers or parameters

409 (Conflict)

The origin server cannot create the target Modality Performed Procedure Step because the provided Modality Performed Procedure Step UID is already in use

503 (Service Unavailable)

The origin server cannot handle the creation of the Modality Performed Procedure Step; this may be a temporal or permanent state


N.7.3.3.8.2 Create Transaction As User Agent

Table N.7.3.3.8.2-1 lists the Status Codes that a user agent supports for the Create Transaction of the Modality Performed Procedure Step Service and defines the application behavior, when encountering any of the listed Status Codes.

[Describe below the behavior of the application when it receives various Status Codes in the Create Transaction response]

Table N.7.3.3.8.2-1. Status Codes of User Agent for Create Transaction

Status

Code

Behavior

Success

201 (Created)

Continue

Failure

400 (Bad Request)

Reformat the request to proper HTTP

409 (Conflict)

Create another MPPS UID and try again

503 (Service Unavailable)

Try again later

*

Any other code

Do further analysis


N.7.3.3.8.3 Update Transaction As Origin Server

Table N.7.3.3.8.3-1 lists the Status Codes that an origin server supports for the Update Transaction of the Modality Performed Procedure Step Service and the condition in which any of the listed Status Codes is sent.

[Describe below the condition in which the application sends the specific Status Codes in the Update Transaction response as origin server.]

Table N.7.3.3.8.3-1. Status Codes of Origin Server for Update Transaction

Status

Code

Condition

Success

200 (OK)

The origin server has updated the Modality Performed Procedure Step with the provided attributes

Failure

400 (Bad Request)

The origin server cannot handle the update request because of errors in the request headers or parameters

404 (Not Found)

The origin server has no knowledge about the target Modality Performed Procedure Step

409 (Conflict)

The origin server cannot update the target Modality Performed Procedure Step, for instance because the changes provided are incompatible with the data of the target Modality Performed Procedure Step

410 (Gone)

The origin server knows that the target Modality Performed Procedure Step did exist but has been deleted

503 (Service Unavailable)

The origin server cannot handle the creation of the Modality Performed Procedure Step; this may be a temporal or permanent state


N.7.3.3.8.4 Update Transaction As User Agent

Table N.7.3.3.8.4-1 lists the Status Codes that a user agent supports for the Update Transaction of the Modality Performed Procedure Step Service and defines the application behavior, when encountering any of the listed Status Codes.

[Describe below the behavior of the application when it receives various Status Codes in the Update Transaction response]

Table N.7.3.3.8.4-1. Status Codes of User Agent for Update Transaction

Status

Code

Behavior

Success

200 (OK)

Continue

Failure

400 (Bad Request)

Reformat the request to proper HTTP

404 (Not Found)

See whether an error was made in the UID

409 (Conflict)

Retrieve the MPPS and analyze what created this issue

410 (Gone)

Create a new MPPS and retry with this new UID

503 (Service Unavailable)

Try again later

*

Any other code

Do further analysis


N.7.3.3.8.5 Retrieve Transaction As Origin Server

Table N.7.3.3.8.5-1 lists the Status Codes that an origin server supports for the Retrieve Transaction of the Modality Performed Procedure Step Service and the condition in which any of the listed Status Codes is sent.

[Describe below the condition in which the application sends the specific Status Codes in the Retrieve Transaction response as origin server.]

Table N.7.3.3.8.5-1. Status Codes of Origin Server for Retrieve Transaction

Status

Code

Condition

Success

200 (OK)

The origin server returned the target Modality Performed Procedure Step

Failure

400 (Bad Request)

The origin server cannot handle the retrieve request because of errors in the request headers or parameters

404 (Not Found)

The origin server has no knowledge about the target Modality Performed Procedure Step

410 (Gone)

The origin server knows that the target Modality Performed Procedure Step did exist but has been deleted

503 (Service Unavailable)

The origin server cannot handle the retrieval of the target Modality Performed Procedure Step; this may be a temporal or permanent state


N.7.3.3.8.6 Retrieve Transaction As User Agent

Table N.7.3.3.8.6-1 lists the Status Codes that a user agent supports for the Retrieve Transaction of the Modality Performed Procedure Step Service and defines the application behavior, when encountering any of the listed Status Codes.

[Describe below the behavior of the application when it receives various Status Codes in the Retrieve Transaction response]

Table N.7.3.3.8.6-1. Status Codes of User Agent for Retrieve Transaction

Status

Code

Behavior

Success

200 (OK)

Continue

Failure

400 (Bad Request)

Reformat the request to proper HTTP

404 (Not Found)

See whether an error was made in the UID

410 (Gone)

Perform error recovery

503 (Service Unavailable)

Retry again later

*

Any other code

Do further analysis


DICOM PS3.2 2025d - Conformance