Upload DICOM instances to a DICOMweb server using STOW-RS

Steps

1. Authenticate to your DICOMweb server using the required method (Basic auth with YOUR_TOKEN, or OAuth bearer token) and confirm the server's STOW-RS endpoint URL from its WADO capabilities response or documentation
2. For each DICOM file, read the raw .dcm bytes; do not modify the file — the binary DICOM payload must be sent exactly as stored including all header and pixel data bytes
3. Construct a multipart/related HTTP POST request: set the Content-Type header to 'multipart/related; type="application/dicom"; boundary=BOUNDARY_STRING' and add each DICOM file as a separate part with Content-Type: application/dicom
4. POST the multipart request to the STOW-RS endpoint, typically structured as {base_url}/studies for a study-level store; include Authorization header with YOUR_TOKEN
5. Parse the response — HTTP 200 indicates all instances were accepted; HTTP 202 indicates partial success with some instances accepted and others failed; inspect the response body (DICOM XML or JSON) for per-instance success/failure status using the Referenced SOP Instance UID list
6. For failed instances, log the failure reason from the Failed SOP Sequence in the response and implement retry logic for transient failures (network errors) while routing persistent failures to a dead-letter queue for manual review