AWS HealthImaging releases

The following table shows when features and updates were released for the AWS HealthImaging service and documentation. For more information on a release, see the linked topic.

Change	Description	Date
Lossy support for StartDICOMImportJob	HealthImaging supports importing and storing DICOM lossy files (1.2.840.10008.1.2.4.203, 1.2.840.10008.1.2.4.91, 1.2.840.10008.1.2.4.50) and binary segmentation files in their original format. For more information, see Supported transfer syntaxes.	November 1, 2024
Lossy support for DICOMweb retrieval services	HealthImaging supports retrieving images and instances stored in 1.2.840.10008.1.2.4.203, 1.2.840.10008.1.2.4.91, 1.2.840.10008.1.2.4.50, and 1.2.840.10008.1.2.1 (binary segmentation only) in their original format or in Explicit VR Little Endian (1.2.840.10008.1.2.1). For more information, see Supported transfer syntaxes and Retrieving DICOM data.	November 1, 2024
Faster imports for digital pathology	HealthImaging supports up to 6x faster import jobs for DICOM digital pathology (WSI).	November 1, 2024
Binary segmentation support	HealthImaging supports both ingestion and retrieval of DICOM binary segmentation files. For more information, see Supported transfer syntaxes.	November 1, 2024
Revert to a previous image set version ID	HealthImaging provides the revertToVersionId parameter to revert to a previous image set version ID. For more information, see revertToVersionId in the AWS HealthImaging API Reference.	July 24, 2024
Force functionality for image set modification	HealthImaging provides the Overrides data type with the optional forced request parameter. Setting this parameter forces the UpdateImageSetMetadata and CopyImageSet actions, even if Patient, Study, or Series level metadata are mismatched. For more information, see Overrides in the AWS HealthImaging API Reference. UpdateImageSetMetadata force functionality—HealthImaging introduces the optional force request parameter for updating the following attributes: Tag.StudyInstanceUID, Tag.SeriesInstanceUID, Tag.SOPInstanceUID, and Tag.StudyID Adding, removing, or updating instance level private DICOM data elements For more information, see UpdateImageSetMetadata in the AWS HealthImaging API Reference. CopyImageSet force functionality—HealthImaging introduces the optional force request parameter for copying image sets. Setting this parameter forces the CopyImageSet action, even if Patient, Study, or Series level metadata are mismatched across the sourceImageSet and destinationImageSet. In these cases, the inconsistent metadata remains unchanged in the destinationImageSet. For more information, see CopyImageSet in the AWS HealthImaging API Reference.	July 24, 2024
Copy subsets of SOP Instances	HealthImaging enhances the CopyImageSet action so you can pick one or more SOP Instances from a sourceImageSet to copy to a destinationImageSet. For more information, see Copying an image set.	July 24, 2024
GetDICOMInstanceMetadata for returning DICOM instance metadata	HealthImaging provides the GetDICOMInstanceMetadata service to return DICOM Part 10 metadata (.json file). For more information, see Getting instance metadata.	July 11, 2024
GetDICOMInstanceFrames for returning DICOM instance frames (pixel data)	HealthImaging provides the GetDICOMInstanceFrames service to return DICOM Part 10 frames (multipart request). For more information, see Getting instance frames.	July 11, 2024
Enhanced support for non-standard DICOM data imports	HealthImaging provides support for data imports that include deviations from the DICOM standard. For more information, see DICOM element constraints. The following DICOM data elements can be up to 256 characters in max length: Patient's Name (0010,0010) Patient ID (0010,0020) Accession Number (0008,0050) The following syntax variations are permitted for Study Instance UID, Series Instance UID, Treatment Session UID, Manufacturer’s Device Class UID, Device UID, and Acquisition UID: The first element of any UID can be zero UIDs can start with one or more leading zeros UIDs can be up to 256 characters in length	June 28, 2024
Event notifications	HealthImaging integrates with Amazon EventBridge to support event-driven applications. For more information, see Using EventBridge.	June 5, 2024
GetDICOMInstance for returning DICOM instance data	HealthImaging provides the GetDICOMInstance service to return DICOM Part 10 instance data (.dcm file). For more information, see Getting an instance.	May 15, 2024
Cross-account import	HealthImaging provides support for data imports from Amazon S3 buckets located in other supported Regions. For more information, see Cross-account import.	May 15, 2024
Search enhancements for image sets	HealthImaging SearchImageSets action supports the following search enhancements. For more information, see see Searching image sets. Additional support for searching on UpdatedAt and SeriesInstanceUID Search between start time and end time Sort search results by Ascending or Descending DICOM Series parameters are returned in responses	April 3, 2024
Maximum file size for imports increased	HealthImaging supports a 4 GB maximum file size for each DICOM P10 file in an import job. For more information, see Service quotas.	March 6, 2024
Transfer syntaxes for JPEG Lossless and HTJ2K	HealthImaging provides support for the following transfer syntaxes for job imports. For more information, see Supported transfer syntaxes. 1.2.840.10008.1.2.4.57 — JPEG Lossless Non-Hierarchical (Process 14) 1.2.840.10008.1.2.4.201 — High-Throughput JPEG 2000 Image Compression (Lossless Only) 1.2.840.10008.1.2.4.202 — High-Throughput JPEG 2000 with RPCL Options Image Compression (Lossless Only) 1.2.840.10008.1.2.4.203 — High-Throughput JPEG 2000 Image Compression	February 16, 2024
Tested code examples	HealthImaging documentation provides tested code examples for AWS CLI and AWS SDKs for Python, JavaScript, Java, and C++. For more information, see see Code examples.	December 19, 2023
Maximum file number for imports increased	HealthImaging supports up to 5,000 files for a single import job. For more information, see Service quotas.	December 19, 2023
Nested folders for imports	HealthImaging supports up to 10,000 nested folders for a single import job. For more information see Service quotas.	December 1, 2023
Faster imports	HealthImaging provides 20X faster imports in all supported Regions. For more information, see Service endpoints.	December 1, 2023
AWS CloudFormation support	HealthImaging supports infrastructure as code (IaC) for provisioning data stores. For more information, see Creating HealthImaging resources with AWS CloudFormation.	September 21, 2023
General availability	AWS HealthImaging is available to all customers in the US East (N. Virginia), US West (Oregon), Europe (Ireland), and Asia Pacific (Sydney) Regions. For more information, see Service endpoints.	July 26, 2023