# 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 | | --- |--- |--- | | [Atomic study-level updates for `UpdateImageSetMetadata`](#releases) | HealthImaging adds the `--include-study-image-sets` flag to the `UpdateImageSetMetadata` action. When set, Patient and Study-level attribute changes made to the specified image set are automatically applied to all other primary image sets that share the same Study Instance UID within the datastore. For more information, see [Updating image set metadata](https://docs.aws.amazon.com/healthimaging/latest/devguide/update-image-set-metadata.html). | March 31, 2026 | | [Study-level fine-grained access control](#releases) | HealthImaging now supports granting permissions for DICOMweb APIs using DICOM Study Instance UIDs and Series Instance UIDs directly in IAM policies. For more information, see [Granting permissions based on Study Instance UID and Series Instance UID](https://docs.aws.amazon.com/healthimaging/latest/devguide/security-iam.html#security_iam_id-based-policy-examples-study-series-uid). | March 19, 2026 | | [Amazon CloudWatch metrics for HealthImaging](#releases) | HealthImaging publishes additional metrics to CloudWatch in the `AWS/HealthImaging` namespace, including resource usage metrics at both account and data store levels. For more information, see [Using Amazon CloudWatch with HealthImaging](https://docs.aws.amazon.com/healthimaging/latest/devguide/monitoring-cloudwatch.html). | February 12, 2026 | | [Service-linked role for HealthImaging](#releases) | HealthImaging now supports service-linked roles that allow the service to publish datastore metrics to CloudWatch on your behalf. The `AWSServiceRoleForHealthImaging` role can be created using the IAM console or AWS CLI. For more information, see [Using service-linked roles for HealthImaging](https://docs.aws.amazon.com/healthimaging/latest/devguide/security-iam-service-linked-roles.html). | February 9, 2026 | | [AWSHealthImagingServiceRolePolicy managed policy](#releases) | HealthImaging added a new managed policy `AWSHealthImagingServiceRolePolicy` for the service-linked role that provides permissions to manage service operations and publish service metrics to CloudWatch. For more information, see [AWSHealthImagingServiceRolePolicy](https://docs.aws.amazon.com/healthimaging/latest/devguide/security-iam-awsmanpol.html#security-iam-awsmanpol-AWSHealthImagingServiceRolePolicy). | February 9, 2026 | | [JPEG XL support for AWS HealthImaging data stores](#releases) | HealthImaging supports importing and storing DICOM lossy files in the JPEG XL transfer syntax (1.2.840.10008.1.2.4.112). For more information, see [ Supported transfer syntaxes](https://docs.aws.amazon.com/healthimaging/latest/devguide/supported-transfer-syntaxes.html). | February 2, 2026 | | [Enhanced DICOM import with warning support for non-conformant data](#releases) | HealthImaging now imports previously rejected DICOM data by accepting non-conformant files while providing detailed warnings through EventBridge events. Import jobs now generate a WARNING folder containing `warning.ndjson` files with specific warning reason codes for non-conformant data. The update adds searchable WarningReason (0008,1196) DICOM element support and introduces `transfer-syntax=*` parameter for retrieving instances in their stored format when transcoding isn't feasible. See [Understanding import jobs](https://docs.aws.amazon.com/healthimaging/latest/devguide/understanding-import-jobs.html) and [HealthImaging warning codes](https://docs.aws.amazon.com/healthimaging/latest/devguide/reference-warning-codes.html) for more information. | December 8, 2025 | | [JPEG 2000 Lossless support for AWS HealthImaging data stores](#releases) | AWS HealthImaging now supports native JPEG 2000 Lossless encoding for medical images, allowing you to create datastores that persist and retrieve lossless image frames in JPEG 2000 format without transcoding. This enables lower latency retrieval for applications that require JPEG 2000 Lossless format when you specify `—lossless-storage-format JPEG_2000_LOSSLESS` when [creating a data store](https://docs.aws.amazon.com/healthimaging/latest/devguide/create-data-store.html). | November 25, 2025 | | [QIDO-RS Search Enhancements Design](#releases) | HealthImaging now supports wildcard searching on key DICOM attributes (Patient Name, Referring Physician Name, Patient ID, Study Description, Modality, and Accession Number) and fuzzy search capabilities for Patient/Referring Physician Names to accommodate incomplete or misspelled terms. The update also expands QIDO-RS API query capabilities to include Patient Birthdate and Study Description searches, enhancing the ability to locate relevant studies and series. See [Searching DICOM data in HealthImaging](https://docs.aws.amazon.com/healthimaging/latest/devguide/dicomweb-search.html) for more information. | September 15, 2025 | | [OpenID Connect (OIDC) authorization for DICOMweb APIs](#releases) | HealthImaging now supports OpenID Connect (OIDC) bearer-token authorization across all DICOMweb APIs. This adds standards-based OAuth 2.0 interoperability with common viewers and toolkits (e.g., OHIF, SLIM, MONAI) by accepting IdP-issued JWTs in the `Authorization` header. See [OIDC authentication for DICOMweb APIs](https://docs.aws.amazon.com/healthimaging/latest/devguide/dicomweb-oidc.html) for more information. | September 3, 2025 | | [Support for DICOMweb data imports and DICOMweb Bulkdata](#releases) | HealthImaging HealthImaging supports storing DICOM P10 files via the DICOMweb STOW-RS protocol. See [Importing data](https://docs.aws.amazon.com/healthimaging/latest/devguide/dicomweb-import.html) for more details. Additionally, HealthImaging supports DICOM Bulkdata to ensure consistent, low latency metadata retrievals. See [Getting DICOM bulkdata](https://docs.aws.amazon.com/healthimaging/latest/devguide/dicom-retrieve-bulkdata.html) for more information. | June 30, 2025 | | [Automatic data organization, DICOMweb QIDO-RS search, and DICOMweb WADO-RS enhancements](#releases) | HealthImaging provides automatic organization of DICOM P10 data on import according to the Patient, Study, and Series level hierarchy of the DICOM standard. For more information see [Understanding import jobs](https://docs.aws.amazon.com/healthimaging/latest/devguide/understanding-import-jobs.html). HealthImaging supports rich search, per the DICOMweb QIDO-RS standard. See [Searching DICOM data in HealthImaging](https://docs.aws.amazon.com/healthimaging/latest/devguide/dicomweb-search.html) for more information. HealthImaging supports retrieving the metadata for all DICOM instances in a series via a single API action, as described in [Getting DICOM series metadata from HealthImaging](https://docs.aws.amazon.com/healthimaging/latest/devguide/dicomweb-retrieve-series-metadata.html). | May 22, 2025 | | [Image set creation uses fewer DICOM elements](#releases) | HealthImaging decreases the number of elements used when grouping incoming DICOM P10 objects into image sets. For more information, see [What is an image set?](https://docs.aws.amazon.com/healthimaging/latest/devguide/understanding-image-sets.html#what-is-image-set). | January 27, 2025 | | [Lossy support for StartDICOMImportJob](#releases) | 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](https://docs.aws.amazon.com/healthimaging/latest/devguide/reference-dicom-support.html#supported-transfer-syntaxes). | November 1, 2024 | | [Lossy support for DICOMweb retrieval APIs](#releases) | 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](https://docs.aws.amazon.com/healthimaging/latest/devguide/reference-dicom-support.html#supported-transfer-syntaxes) and [ Retrieving DICOM data](https://docs.aws.amazon.com/healthimaging/latest/devguide/dicomweb-retrieve.html). | November 1, 2024 | | [Faster imports for digital pathology](#releases) | HealthImaging supports up to 6x faster import jobs for DICOM digital pathology (WSI). | November 1, 2024 | | [Binary segmentation support](#releases) | HealthImaging supports both ingestion and retrieval of DICOM binary segmentation files. For more information, see [ Supported transfer syntaxes](https://docs.aws.amazon.com/healthimaging/latest/devguide/reference-dicom-support.html#supported-transfer-syntaxes). | November 1, 2024 | | [Revert to a previous image set version ID](#releases) | HealthImaging provides the `revertToVersionId` parameter to revert to a previous image set version ID. For more information, see [https://docs.aws.amazon.com/healthimaging/latest/APIReference/API_UpdateImageSetMetadata.html#healthimaging-UpdateImageSetMetadata-request-revertToVersionId](https://docs.aws.amazon.com/healthimaging/latest/APIReference/API_UpdateImageSetMetadata.html#healthimaging-UpdateImageSetMetadata-request-revertToVersionId) in the *AWS HealthImaging API Reference*. | July 24, 2024 | | [Force functionality for image set modification](#releases) | 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](https://docs.aws.amazon.com/healthimaging/latest/APIReference/API_Overrides.html) 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](https://docs.aws.amazon.com/healthimaging/latest/APIReference/API_UpdateImageSetMetadata.html) 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](https://docs.aws.amazon.com/healthimaging/latest/APIReference/API_CopyImageSet.html) in the *AWS HealthImaging API Reference*. | July 24, 2024 | | [Copy subsets of SOP Instances](#releases) | 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](https://docs.aws.amazon.com/healthimaging/latest/devguide/copy-image-set.html). | July 24, 2024 | | [`GetDICOMInstanceMetadata` for returning DICOM instance metadata](#releases) | HealthImaging provides the `GetDICOMInstanceMetadata` API to return DICOM Part 10 metadata (`.json` file). For more information, see [Getting instance metadata](https://docs.aws.amazon.com/healthimaging/latest/devguide/dicomweb-retrieve-instance-metadata.html). | July 11, 2024 | | [`GetDICOMInstanceFrames` for returning DICOM instance frames (pixel data)](#releases) | HealthImaging provides the `GetDICOMInstanceFrames` API to return DICOM Part 10 frames (`multipart` request). For more information, see [Getting instance frames](https://docs.aws.amazon.com/healthimaging/latest/devguide/dicomweb-retrieve-instance-frames.html). | July 11, 2024 | | [Enhanced support for non-standard DICOM data imports](#releases) | HealthImaging provides support for data imports that include deviations from the DICOM standard. For more information, see [ DICOM element constraints](https://docs.aws.amazon.com/healthimaging/latest/devguide/reference-dicom-support.html#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](#releases) | HealthImaging integrates with Amazon EventBridge to support event-driven applications. For more information, see [Using EventBridge](https://docs.aws.amazon.com/healthimaging/latest/devguide/event-notifications.html). | June 5, 2024 | | [`GetDICOMInstance` for returning DICOM instance data](#releases) | HealthImaging provides the `GetDICOMInstance` service to return DICOM Part 10 instance data (`.dcm` file). For more information, see [Getting an instance](https://docs.aws.amazon.com/healthimaging/latest/devguide/dicomweb-retrieve-instance.html). | May 15, 2024 | | [Cross-account import](#releases) | HealthImaging provides support for data imports from Amazon S3 buckets located in other supported Regions. For more information, see [Cross-account import](https://docs.aws.amazon.com/healthimaging/latest/devguide/cross-account-imports.html). | May 15, 2024 | | [Search enhancements for image sets](#releases) | HealthImaging `SearchImageSets` action supports the following search enhancements. For more information, see [Searching image sets](https://docs.aws.amazon.com/healthimaging/latest/devguide/search-image-sets.html). 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](#releases) | HealthImaging supports a 4 GB maximum file size for each DICOM P10 file in an import job. For more information, see [Service quotas](https://docs.aws.amazon.com/healthimaging/latest/devguide/endpoints-quotas.html#quotas). | March 6, 2024 | | [Transfer syntaxes for JPEG Lossless and HTJ2K](#releases) | HealthImaging provides support for the following transfer syntaxes for job imports. For more information, see [ Supported transfer syntaxes](https://docs.aws.amazon.com/healthimaging/latest/devguide/reference-dicom-support.html#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](#releases) | HealthImaging documentation provides tested code examples for AWS CLI and AWS SDKs for Python, JavaScript, Java, and C\$1\$1. For more information, see [Code examples](https://docs.aws.amazon.com/healthimaging/latest/devguide/service_code_examples.html). | December 19, 2023 | | [Maximum file number for imports increased](#releases) | HealthImaging supports up to 5,000 files for a single import job. For more information, see [Service quotas](https://docs.aws.amazon.com/healthimaging/latest/devguide/endpoints-quotas.html#quotas). | December 19, 2023 | | [Nested folders for imports](#releases) | HealthImaging supports up to 10,000 nested folders for a single import job. For more information see [Service quotas](https://docs.aws.amazon.com/healthimaging/latest/devguide/endpoints-quotas.html#quotas). | December 1, 2023 | | [Faster imports](#releases) | HealthImaging provides 20X faster imports in all supported Regions. For more information, see [Service endpoints](https://docs.aws.amazon.com/healthimaging/latest/devguide/endpoints-quotas.html#endpoints). | December 1, 2023 | | [CloudFormation support](#releases) | HealthImaging supports infrastructure as code (IaC) for provisioning data stores. For more information, see [ Creating HealthImaging resources with CloudFormation](https://docs.aws.amazon.com/healthimaging/latest/devguide/creating-resources-with-cloudformation.html). | September 21, 2023 | | [General availability](#releases) | 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](https://docs.aws.amazon.com/healthimaging/latest/devguide/endpoints-quotas.html#endpoints). | July 26, 2023 |