Table 15.5.3-1 shows some common status codes corresponding to this Transaction. See also Section 8.5 for additional status codes.
Table 15.5.3-1. Status Code Meaning
|
Status
|
Code
|
Meaning
|
|
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.
|
Note
When it is requested that attributes are to be updated while these have not been made available at creation time, a 409 (Conflict) can be returned; this is the case when Table F.7.2-1 in PS3.4
specifies that these attributes should have been made available at creation time.