You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is a failure in transferring the data using this adapter between PACS to GCP DICOM Store (i.e. a failure in calling the GCP Healthcare API, the application crashes, there is a network outage, etc.) - does a standard PACS System pick up from where it last left off?
Is data persisted somewhere between retrieval and storage in DICOM? If not would it be possible to leverage some sort of persistent queue?
It is expected to understand how reliable this healthcare-dicom-dicomweb-adapter solution is prior to using it in a production environment.
Note, My concern is with consistency of data between the PACS system and the DICOM store when using google's open source GCP DICOM Adapter solution. If there is a failure to transfer data from PACS to GCP DICOM Adapter will there be a retry or will the stream continue without retrying?
Questions on the DICOM Adapter's reliability
GCP's PACS to DICOM Solution: Connecting a PACS system to the Healthcare API (DICOM store) - https://cloud.google.com/healthcare/docs/how-tos/dicom-connect-pacs
GCP's DICOM Adapter: https://github.com/GoogleCloudPlatform/healthcare-dicom-dicomweb-adapter
[1] https://github.com/GoogleCloudPlatform/healthcare-dicom-dicomweb-adapter/blob/master/import/src/test/java/com/google/cloud/healthcare/imaging/dicomadapter/cstore/backup/BackupUploadServiceTest.java#L209
The text was updated successfully, but these errors were encountered: