Closed
Milestone
Jul 1, 2022–Mar 6, 2024
Industrial Strength Imaging Platform: Performance Improvements, Scalability, Cloud Deployments
-
Create integrations for GCP and Azure that enables Sonador to run on all the major cloud providers. (AWS and on-premise via MinIO are already supported deployment profiles.) _ -
Google Storage Plugin and Dockerfile for Orthanc/Sonador container image
-
-
Deployment Improvements: Make it easier to setup and extend a Sonador cluster -
Incorporate functional testing into Sonador CI/CD to improve QA and vetting prior to releasesPushed to %Industrial Strength Imaging Platform Part 2: Monitoring, More Scalability Work, Additional Cloud Tuning. -
Extend Sonador's Orthanc plugin so that it is possible for an Orthanc server to self-register on startup.
-
-
Improve integration between Sonador and Orthanc - Add support for
ElasticSearchPostgreSQL so that it is possible to index and search all DICOM fields. Pushed to %Industrial Strength Imaging Platform Part 2: Monitoring, More Scalability Work, Additional Cloud Tuning. -
Make OHIF aware of user permissions so that it is able to hide/show features based on the role of the user -
Upload button only visible if "upload" permission -
Study list only visible if goblal "query" permission
-
- Add support for
-
Improve Orthanc performance for large medical imaging datasets -
Fix C++ compatibility issues with the Oak-Tree S3 storage plugin which prevent its deployment on Orthanc 1.10 and newer -
Upgrade Orthanc to version 1.11 and test the performance improvements provided by the new database cache, create sample config file which allows for Sonador OHIF to store field data in the database -
Implement request caching in Orthanc using Memcached or RedisPostgreSQL JSONB fields-
Add cache tables to Sonador Plugin using SQLAlchemy -
Create indexing methods that are able to update the cache as part of Orthanc's resource life cycle -
Create batch methods and queries that are able to refresh the cache outside of the resource life cycle (find resources which may have been updated without a callback or resources that were deleted) -
Create query endpoints for patient, study, and series so that the resource cache can be used via the API
-
-
Implement C-FIND method for DICOM clients that is able to use the resource cache
-
Loading
Loading
Loading
Loading