Importing data
Importing Instances
AWS HealthImaging offers a representation of the DICOMweb STOW-RS
The following table describes the HealthImaging representations of DICOMweb STOW-RS APIs available for importing data.
| Name | Description |
|---|---|
StoreDICOM |
Store one or more instances to a HealthImaging data store. |
StoreDICOMStudy |
Store one or more instances corresponding to a specified Study Instance UID to a HealthImaging data store. |
Data imported with the StoreDICOM and StoreDICOMStudy actions will be organized as new primary image sets, or added to existing primary image sets, using the same logic as asynchronous import jobs. If the metadata elements of newly imported DICOM P10 data conflict with existing primary image sets, the new data will be added to non-primary image sets.
Note
-
These actions support upload of up to 1GB of DICOM data per request.
-
The API response will be in the JSON format, conformant to the DICOMweb STOW-RS standard.
To initiate a StoreDICOM request
-
Collect your AWS region, HealthImaging
datastoreId, and DICOM P10 file name. -
Construct a URL for the request of the form:
https://dicom-medical-imaging.region.amazonaws.com/datastore/datastore-id/studies -
Determine the content length of the DICOM P10 file using your preferred command, for example
$(stat -f %z $FILENAME). -
Prepare and send your request.
StoreDICOMuses a HTTP POST request with AWS Signature Version 4 signing protocol.
Example 1: To store a DICOM P10 file using the StoreDICOM action
Example 2: To store a DICOM P10 file using the StoreDICOMStudy action
The only difference between StoreDICOM and StoreDICOMStudy is that a Study Instance UID is passed as a parameter to StoreDICOMStudy, and the uploaded instances must be members of the specified study.
Example 3: To store DICOM P10 files with a multi-part HTTP payload
