HealthImaging manages cloud-native image sets, not a generic file bucket
AWS HealthImaging is the imaging-domain service in the AWS health portfolio. Its job is to ingest DICOM P10 data, organize it into service-managed image sets, and preserve the patient-study-series context that imaging systems depend on.
That service boundary matters for migration and viewer design. HealthImaging automatically organizes imported data by patient, study, and series, and the image sets correspond to DICOM series. The service is not just a raw object store for PACS exports, and it is not the same thing as a FHIR datastore with image attachments.
HealthImaging image-set boundary
Loading diagram...
What is AWS HealthImaging?
Official service overview for HealthImaging, including the managed ingest, storage, and retrieval model.
Read the service overviewUnderstanding image sets in AWS HealthImaging
Official HealthImaging guide for how imported DICOM studies become image sets while preserving patient, study, and series context.
Review image-set organizationHealthImaging exposes DICOMweb-conformant responses at the retrieval edge
AWS documents HealthImaging's web access as DICOMweb-conformant representations. That distinction is subtle but important. You still retrieve DICOM semantics through web-native APIs, but the service's system boundary remains HealthImaging image sets and cloud-native actions.
The AWS documentation also states that these DICOMweb representations are not offered through AWS CLI or AWS SDKs. Architects should therefore separate two concerns: AWS control-plane automation for datastore and import operations, and DICOMweb client behavior for search, metadata retrieval, and image access.
That viewer-side contract is also getting more explicit. AWS now documents authorization of DICOMweb requests and image frame retrieval with OIDC tokens, which matters for browser viewers and federated identity designs because web retrieval no longer has to be described as an implicit private-network-only pattern.
Control plane versus viewer plane in HealthImaging
Loading diagram...
Do not confuse standards compatibility with identical API surfaces
HealthImaging is standards-aware and DICOMweb-conformant, but the operational platform still has AWS-specific control-plane behavior around imports, datastores, events, and access management.
Accessing image sets with AWS HealthImaging
Official HealthImaging guide explaining cloud-native image-set actions and DICOMweb representations for viewers.
Review image-set accessAuthorizing DICOMweb requests with OIDC
Official HealthImaging guide for OIDC-token authorization of DICOMweb requests and image frame retrieval.
Review OIDC authorizationImport jobs are the audit spine of a HealthImaging migration
A serious imaging migration needs more than a success message. HealthImaging import jobs write an audit trail to S3, including a job-output-manifest.json file and SUCCESS, FAILURE, and WARNING outputs. AWS also documents special handling when incoming data conflicts with an existing primary image set, which can result in non-primary image sets and EventBridge notifications.
HealthImaging import-job control flow
Loading diagram...
Representative HealthImaging import summary
Simplified JSON aligned to the documented manifest concepts used to audit import outcomes and locate detailed result files.
Click on an annotation to highlight it in the JSON
Operational outcomes to monitor after import
| Signal | What it means | Why it matters |
|---|---|---|
| SUCCESS output | Image sets were imported without recorded failure or warning | Baseline throughput and migration progress measurement |
| WARNING output | Import completed but some conditions require investigation | Prevents silent acceptance of questionable studies |
| FAILURE output | Import could not create the expected image-set outcome | Requires reprocessing or source-data correction |
| EventBridge isPrimary: False | Incoming data conflicted with an existing primary image set | Supports downstream reconciliation and governed review |
Start a DICOM import job
Official guide for initiating HealthImaging import jobs with S3 input and output locations.
Read the import-job guideUnderstanding import jobs
Official import-job behavior guide covering primary versus non-primary image sets, manifests, and SUCCESS / FAILURE / WARNING outputs.
Review import outcomesKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.