AWS – AWS HealthImaging supports cross account data imports

AWS HealthImaging now supports cross-account and cross-region import jobs. With this release, customers can directly import DICOM data from any S3 bucket owned by their organization, owned by collaborators, or from publicly available sources like the Registry of Open Data on AWS (RODA). Customers can import data from an S3 bucket in a different region than their data stores as long as that bucket is in a region where HealthImaging is available. To run cross-account DICOM import jobs, the S3 bucket owner must grant the data store owner list bucket and get object permissions, and the data store owner must add the bucket to their IAM ImportJobDataAccessRole. This makes it easy to load publicly available open data sets like the Imaging Data Commons (IDC) Collections.  Medical imaging SaaS products can now easily import DICOM data from their customers’ accounts. Large organizations can populate one HealthImaging data store from many S3 input buckets distributed across their multi-account environment and researchers can easily and securely share data across multi-institution clinical studies. AWS HealthImaging is a HIPAA-eligible service that empowers healthcare providers and their software partners to store, analyze, and share medical images at petabyte scale. With AWS HealthImaging, you can run your medical imaging applications at scale from a single, authoritative copy of each medical image in the cloud, while reducing infrastructure costs.  AWS HealthImaging is generally available in the following AWS Regions: US East (N. Virginia), US West (Oregon), Asia Pacific (Sydney), and Europe (Ireland). To learn more, visit AWS HealthImaging.

Read More for the details.