# Integration with AWS HealthImaging

**URL:** <https://discourse.slicer.org/t/integration-with-aws-healthimaging/42604>\
**Category:** Feature requests\
**Created:** [April 17, 2025, 2:48pm UTC](https://discourse.slicer.org/t/integration-with-aws-healthimaging/42604 "2025-04-17T14:48:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ksidis](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ksidis/32/65544_2.png) [@ksidis](https://discourse.slicer.org/u/ksidis)\
**Post date:** [April 17, 2025, 2:48pm UTC](https://discourse.slicer.org/t/integration-with-aws-healthimaging/42604/1 "2025-04-17T14:48:49Z")

</div>

Hello,

Thank you for providing this amazing tool.

I recently got involved in a PoT about AWS HealthImaging (AHI) service (formerly known as AWS HealthLake). After a quick look I realised that out of the box it only supports DICOMWeb WADO-RS. As a result, the only way to connect it to a running 3DSlicer is by deploying additional solutions that expose a DICOM QIDO endpoint on top of an AHI datastore. Am I correct in my assumption?

Currently, is there any other way (maybe via an extension) to connect to AHI, search and retrieve DICOM images? If not, is it on your roadmap, or you believe that the DICOMWeb capability is something that needs to be addressed from AWS team?

Thank you in advance,

Regards,  
Kostas

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [April 17, 2025, 3:26pm UTC](https://discourse.slicer.org/t/integration-with-aws-healthimaging/42604/2 "2025-04-17T15:26:23Z")

</div>

Hi - As it happens, yes, I did work with some folks at AWS a few years ago to make a prototype that worked well with AWS AHI with an abstraction that also works with standard DICOMweb in the Slicer DICOM database.

The key things this provides are async/parallel frame access and decompression plus virtualized access to large datasets (only the metadata is pulled onto your local machine and then image frames are pulled down on-demand.

We did enough of a proof of concept to show at RNSA but haven’t fully wrapped this up in a release version. It would be great if someone wants to pick up on this.

> **[GitHub - pieper/DICOMLogic: Essential logic for working with dicom data.](https://github.com/pieper/DICOMLogic)**
>
> Essential logic for working with dicom data.

---

<div class="post-metadata">

**Author:** ![ksidis](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ksidis/32/65544_2.png) [@ksidis](https://discourse.slicer.org/u/ksidis)\
**Post date:** [September 25, 2025, 9:09am UTC](https://discourse.slicer.org/t/integration-with-aws-healthimaging/42604/3 "2025-09-25T09:09:43Z")

</div>

Hi again. Could we maybe revisit this, since now AWS AHI has full DICOMweb support?

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [September 25, 2025, 12:19pm UTC](https://discourse.slicer.org/t/integration-with-aws-healthimaging/42604/4 "2025-09-25T12:19:05Z")

</div>

It would be great if someone can pick this up. It’s not currently a funded priority for me.

But I will say that the code I linked above does support Google’s DICOMweb so hopefully the AWS implementation would be quite similar and would simplify things a bit.

---

<div class="post-metadata">

**Author:** ![ksidis](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ksidis/32/65544_2.png) [@ksidis](https://discourse.slicer.org/u/ksidis)\
**Post date:** [November 20, 2025, 1:46pm UTC](https://discourse.slicer.org/t/integration-with-aws-healthimaging/42604/5 "2025-11-20T13:46:04Z")

</div>

@lassoan is there any plan to include AWS HealthImaging in the [DICOMwebBrowser extension](https://github.com/lassoan/SlicerDICOMwebBrowser)? After having a quick look at the repo I’ve noticed that it currently supports GoogleCloud.