Exporting Data

How data is delivered once you place an order:formats, timelines, and what to expect.

Demos & Guides

Latest Update:

July 7, 2026

How Data Delivery Works

Once you’ve placed a final DICOM order and the licensing agreement is executed:

‍

Delivery timeline: Full DICOM files are typically available within 2 business days of contract execution. For larger orders, our team provides a specific timeline.

Supported formats:

• DICOM: Standard medical imaging format with de-identified headers

• CSV

‍

All data has been de-identified in compliance with HIPAA Safe Harbor standards. Patient identifiers are removed from both DICOM headers and any associated clinical data.

‍

Connecting to BackBlaze

‍

Connecting to Backblaze — Data Transfer Guide

Before you start

Install the AWS CLI

This guide uses the AWS Command Line Interface to download your data. If you've used aws before, you can skip ahead. Otherwise, install it for your operating system:

macOS

With Homebrew:

brew install awscli

Or use the official .pkg installer.

Windows

Download and run the official .msi installer.

Run commands in Command Prompt or PowerShell.

Linux

Most package managers have it:

sudo apt install awscli

Or follow the official guide.

To confirm it's installed, run aws --version. You should see something like aws-cli/2.x.x.

Confirm network access

Before anything else, make sure your network allows connections to Backblaze. Open your terminal and run the command below. We're testing from the terminal because that's where you'll run the AWS commands later — so if this works, the rest will work too.

Terminal

curl -sS -o /dev/null -w "HTTP %{http_code} from %{remote_ip}\n" "https://s3.us-east-005.backblazeb2.com/"

If you see this, you're good

HTTP 403 from 203.0.113.x

A 403 response means your network can reach Backblaze — the server is rejecting an unauthenticated request, which is expected. Proceed to Step 01.

If you see any of these, you're blocked

Could not resolve host
Connection timed out / Connection refused
SSL certificate problem
An HTTP 200, 302, or 407 (a corporate proxy is intercepting)
Hangs for more than ~30 seconds

Contact your IT department and ask them to allow outbound HTTPS to *.backblazeb2.com, then re-run the command.

Retrieve your key from Openda

Sign in to Openda and open Account Settings → Profile. Find the Backblaze B2 Credentials section near the bottom of the page. You'll need three values from there, marked ①②③ in the screenshot:

The Backblaze B2 Credentials section in your Openda profile.

Enter the values below to generate your commands. Your values stay in this browser — nothing is sent anywhere.

① AWS Access Key ID

② AWS Secret Access Key

③ Directory

Local folder to download into

Create an authentication profile

Run this command in your terminal:

Terminal

aws configure --profile segmed-b2

When prompted, enter the following:

AWS Access Key ID — enter ① above —
AWS Secret Access Key — enter ② above —
Default region name leave empty, press Enter
Default output format leave empty, press Enter

‍

Connecting to Backblaze — Data Transfer Guide

Download your data

Run the sync command below. The command updates automatically as you fill in the fields above.

Terminal

The sync command can be re-run safely — it will only download files that are new or have changed since your last run.

If something goes wrong

Troubleshooting

Could not resolve host network

Your machine couldn't look up the Backblaze hostname. This is almost always a DNS or content-filter issue on your network. Run the network check from Step 00 again, and if it still fails, contact your IT department and ask them to allow outbound HTTPS to *.backblazeb2.com.

Connection timed out or hangs for a long time network

Your network is reaching the right place but a firewall is dropping the connection. This usually requires IT to allow traffic on port 443 to *.backblazeb2.com. If you're on a corporate VPN, try disconnecting briefly to confirm whether the VPN is the cause.

InvalidAccessKeyId or SignatureDoesNotMatch credentials

Your credentials weren't accepted. A few things to check:

Make sure you copied the Backblaze B2 Credentials, not the AWS S3 Credentials shown above them in Openda — they look similar but aren't interchangeable.
Re-run aws configure --profile segmed-b2 and re-enter the keys, watching for accidental whitespace at the start or end when pasting.
Check the Expiration Date shown beneath the credentials in Openda. If it's in the past, contact your Segmed representative for fresh credentials.

NoSuchBucket or AccessDenied credentials

Authentication worked, but the directory you specified doesn't exist or your key doesn't have access to it. Double-check that the value in field ③ matches the Directory shown in Openda exactly, including any hyphens or numbers. Don't include s3:// when entering it here — that's added automatically.

command not found: aws setup

The AWS CLI isn't installed, or your terminal hasn't picked it up yet. Revisit the Before you start section above. After installing, close and reopen your terminal window, then run aws --version to confirm.

Sync stops partway through or seems stuck runtime

For large datasets, the sync can take hours and may pause briefly between files — this is normal. If it has actually stopped (no progress for several minutes), interrupt with Ctrl + C and re-run the same command. The sync command resumes where it left off and will only re-download files that didn't complete.

SSL certificate problem network

This usually means a corporate firewall or antivirus is intercepting HTTPS connections (TLS inspection). Contact your IT department — they may need to add Backblaze to a TLS-inspection exclusion list, or install a corporate root certificate on your machine that covers Backblaze traffic.

Copied to clipboard

‍

If you have any questions, don’t hesitate to reach out to us at support@segmed.ai, or schedule a quick chat - we’d love to help you!