The intent of this example is the same as presented in Section B.27, namely the scenario to request storage commitment for two SOP Instances, where for one it succeeds, and for one it fails. The differences are in the synchronicity (in this case it is synchronous), the syntax (in this case using XML), and the structure (in this case using the hierarchical study-series-SOP Class-instance structure, starting with a Referenced Study Sequence (0008,1110); see Table J.1-1 for more details on this structure).

Step 1:

POST /radiology/commitment-requests/1.1.99999.20220901 HTTP/1.1
Host: www.hospital-stmarco
Content-Type: application/dicom+xml

<?xml version="1.0" encoding="UTF-8"?>
<NativeDicomModel>
  <DicomAttribute Tag="00081110" VR="SQ" Keyword="ReferencedStudySequence">
  <Item number="1">
    <DicomAttribute Tag="0020000D" VR="UI" Keyword="StudyInstanceUID">
      <Value number="1">1.2.250.1.59.40211.12345678.678910</Value>
    </DicomAttribute>
    <DicomAttribute Tag="00081115" VR="SQ" Keyword="ReferencedSeriesSequence">
    <Item number="1">
      <DicomAttribute Tag="0020000E" VR="UI" Keyword="SeriesInstanceUID">
        <Value number="1">1.2.250.1.59.40211.789001276.14556172.67789</Value>
      </DicomAttribute>
      <DicomAttribute Tag="00081112" VR="SQ" Keyword="ReferencedInstancesBySOPClassSequence">
      <Item number="1">
        <DicomAttribute Tag="00081150" VR="UI" Keyword="ReferencedSOPClassUID">
          <Value number="1">1.2.840.10008.5.1.4.1.1.2</Value>
        </DicomAttribute>
        <DicomAttribute Tag="0008114A" VR="SQ" Keyword="ReferencedInstanceSequence">
        <Item number="1">
          <DicomAttribute Tag="00081155" VR="UI" Keyword="ReferencedSOPInstanceUID">
            <Value number="1">1.3.12.2.1107.5.99.3.30000012031310075961300000059</Value>
          </DicomAttribute>
        </Item>
        <Item number="2">
          <DicomAttribute Tag="00081155" VR="UI" Keyword="ReferencedSOPInstanceUID">
            <Value number="1">1.3.12.2.1107.5.99.3.30000012031310075961300000060</Value>
          </DicomAttribute>
        </Item>
        </DicomAttribute>
      </Item>
      </DicomAttribute>
    </Item>
    </DicomAttribute>
  </Item>
  </DicomAttribute>
</NativeDicomModel>

In the above, the applicable Study is identified by its Study Instance UID (0020,000D) with value 1.2.250.1.59.40211.12345678.678910. The applicable Series is identified by its Series Instance UID (0020,000E) with value 1.2.250.1.59.40211.789001276.14556172.67789. SOP Class UIDs and SOP Instance UIDs are the same as the example given in Section B.27.

Step 2:

HTTP/1.1 200 OK
Content-Length: 2910
Content-Type: application/dicom+xml

<?xml version="1.0" encoding="UTF-8"?>
<NativeDicomModel>
  <DicomAttribute Tag="00081110" VR="SQ" Keyword="ReferencedStudySequence">
  <Item number="1">
    <DicomAttribute Tag="0020000D" VR="UI" Keyword="StudyInstanceUID">
      <Value number="1">1.2.250.1.59.40211.12345678.678910</Value>
    </DicomAttribute>
    <DicomAttribute Tag="00081115" VR="SQ" Keyword="ReferencedSeriesSequence">
    <Item number="1">
      <DicomAttribute Tag="0020000E" VR="UI" Keyword="SeriesInstanceUID">
        <Value number="1">1.2.250.1.59.40211.789001276.14556172.67789</Value>
      </DicomAttribute>
      <DicomAttribute Tag="00081112" VR="SQ" Keyword="ReferencedInstancesBySOPClassSequence">
      <Item number="1">
        <DicomAttribute Tag="00081150" VR="UI" Keyword="ReferencedSOPClassUID">
          <Value number="1">1.2.840.10008.5.1.4.1.1.2</Value>
        </DicomAttribute>
        <DicomAttribute Tag="0008114A" VR="SQ" Keyword="ReferencedInstanceSequence">
        <Item number="1">
          <DicomAttribute Tag="00081155" VR="UI" Keyword="ReferencedSOPInstanceUID">
            <Value number="1">1.3.12.2.1107.5.99.3.30000012031310075961300000059</Value>
          </DicomAttribute>
        </Item>
        </DicomAttribute>
      </Item>
      </DicomAttribute>
    </Item>
    </DicomAttribute>
  </Item>
  </DicomAttribute>
  <DicomAttribute Tag="0008119B" VR="SQ" Keyword="FailedStudySequence">
  <Item number="1">
    <DicomAttribute Tag="0020000D" VR="UI" Keyword="StudyInstanceUID">
      <Value number="1">1.2.250.1.59.40211.12345678.678910</Value>
    </DicomAttribute>
    <DicomAttribute Tag="00081115" VR="SQ" Keyword="ReferencedSeriesSequence">
    <Item number="1">
      <DicomAttribute Tag="0020000E" VR="UI" Keyword="SeriesInstanceUID">
        <Value number="1">1.2.250.1.59.40211.789001276.14556172.67789</Value>
      </DicomAttribute>
      <DicomAttribute Tag="00081112" VR="SQ" Keyword="ReferencedInstancesBySOPClassSequence">
      <Item number="1">
        <DicomAttribute Tag="00081150" VR="UI" Keyword="ReferencedSOPClassUID">
          <Value number="1">1.2.840.10008.5.1.4.1.1.2</Value>
        </DicomAttribute>
        <DicomAttribute Tag="0008114A" VR="SQ" Keyword="ReferencedInstanceSequence">
        <Item number="1">
          <DicomAttribute Tag="00081155" VR="UI" Keyword="ReferencedSOPInstanceUID">
            <Value number="1">1.3.12.2.1107.5.99.3.30000012031310075961300000060</Value>
          </DicomAttribute>
          <DicomAttribute Tag="00081197" VR="UI" Keyword="FailureReason">
            <Value number="1">274</Value>
          </DicomAttribute>
        </Item>
        </DicomAttribute>
      </Item>
      </DicomAttribute>
    </Item>
    </DicomAttribute>
  </Item>
  </DicomAttribute>
</NativeDicomModel>

The Failed Study Sequence (0008,119B) has the same structure as the Referenced Study Sequence, except that it adds a Failure Reason (0008,1197) to each Referenced SOP Instance UID, indicating why the origin server could not commit to safely store that referenced SOP Instance.