NA-MIC Project Weeks
Back to Projects List
Implement support of external DICOM servers in Kaapana
Key Investigators
- Vamsi Thiriveedhi (Brigham and Women's Hospital, Boston)
- Mikulas Bankovic (DKFZ, Germany)
- Andrey Fedorov (Brigham and Women's Hospital, Boston)
Project Description
The goal of this project is to enhance the capabilities of Kaapana, an open-source platform, by enabling it to work seamlessly with DICOM data stored in Google Cloud’s HealthCare API DICOM stores. Currently, Kaapana relies on an internal dcm4chee DICOM, which means all of the data needs to be managed on the same VM as Kaapana itself, and in the situation where data already exists in an external DICOM store, it needs to be replicated to the Kaapana dcm4chee. We would like to make it possible to reuse existin Google Healthcare DICOM store without copying its content. Building upon the previous project week’s progress, we aim to further improve the connectivity and compatibility of Kaapana with Google’s Healthcare API.
Objective
- Build on the progress done by Miki from Kaapana team on the PR in progress
- Review GCP authentication’s procedure currently implemented
Approach and Plan
- Evaluate the current state of the feature by building docker images from the outstanding PR
- Impement GCP authentication by asking the user to upload a service account key file with necessary permissions
Progress and Next Steps
- Currently authentication is handled by supplying a service account key as a string
- Miki mentioned that the PR is now ready for testing.
- Vamsi created and tested an airflow workflow to send dicom files from local storage to GCP Dicom store with GCP’s dicomweb package
- Adapting to kaapana architechture is pending
- Vamsi is going to build and deploy from Miki’s git branch to test
Illustrations
Created a form for collecting the info about the GCP DICOM store