Uploading files

Every model takes files: a flat list of file references. The platform groups them into series and runs, so a model never needs a special input mode.

What a files entry can be

Entry	Behaviour
file_… from /v1/uploads	Single or multi-frame DICOM, zip/tar(.gz) of folders and CD exports (DICOMDIR honoured, viewer software and duplicates skipped), PNG/JPEG, MP4, PDF
https://… URL	MedRun fetches it when the request starts, for example a signed S3 or GCS link

Uploading

1. POST /v1/uploads with {filename, bytes, media_type, relative_path?}. For many small files (a CT series), use POST /v1/uploads/batch.
2. Send the bytes to the returned target: one PUT up to 100 MB, or multipart part URLs above that.
3. POST the complete_url (with part ETags for multipart), then use file.id in input.files.

relative_path keeps a dropped folder's layout (DICOM/PA1/ST1/IM0001), which helps grouping CD exports.

Retention

Uploaded files and results are working copies kept for 7 days, then deleted. Inputs are also archived to improve MedRun models, as described in the data use page.

Files are processed as received

MedRun does not de-identify, rewrite UIDs or shift dates. Outputs (SR, SEG) reference your own UIDs, so they open next to the originals in your viewer.