- Newest
- Most votes
- Most comments
To access the studies you've imported into AWS HealthImaging through your OHIF Viewer setup, you'll need to integrate the AWS HealthImaging API with your viewer. The OHIF Viewer can be configured to use AWS HealthImaging as a data source, allowing you to search and view ImageSets stored in HealthImaging.
There's an open-source extension available for OHIF that enables integration with AWS HealthImaging. This extension allows users to search images by PatientID, Accession Number, Study UID, Study Instance UID, and Study Date, as well as view datastores, search ImageSets, and view ImageSet Metadata.
Regarding putting the HealthImaging endpoint behind a CloudFront distribution and adding it as a DataSource to the OHIF Viewer, this approach is not typically recommended or necessary. AWS HealthImaging already provides a secure, scalable API endpoint for accessing your medical imaging data. Instead of using CloudFront, you should directly configure the OHIF Viewer to use the AWS HealthImaging API endpoint as its data source.
To set this up:
- Ensure you have the necessary permissions to access AWS HealthImaging from your OHIF Viewer application.
- Install and configure the AWS HealthImaging extension for OHIF.
- In your OHIF Viewer configuration, specify the AWS HealthImaging API endpoint as the data source.
- Implement appropriate authentication and authorization mechanisms to ensure secure access to your HealthImaging data.
This setup will allow your OHIF Viewer to directly interact with AWS HealthImaging, retrieving and displaying the studies you've imported without the need for an additional CloudFront distribution for the HealthImaging endpoint.
Sources
Building a Scalable DICOM Ingestion Pipeline for AWS HealthImaging with CitiusTech | AWS Partner Network (APN) Blog
answered 2 years ago
