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
Sundar and I were discussing this and it would be great to be able to Query the DICOM receiver for Orthanc to verify it received all the images. Do we think this is possible?
The text was updated successfully, but these errors were encountered:
I asked about the Orthanc receiver web interface (via nginx) on the rady server?
@youngmd clarifies that yes we do have this but it won't help @mparamas because we pull data (more accurately, metadata) off immediately on arrival so one can't look at reception status on the Orthanc web UI.
Sundar asks about the Orthanc DB itself? Mike clarifies again that we store nothing right now.
Sundar wonders if looking at CTP is the only status check he can do.
Mike wants more info on what Sundar is trying to do. We had planned on adding more dataflow monitoring anyway.
Sundar clarifies: I want to be able to verify when I send N images, I find M on CTP, how many made it for real to SCA? Preferably would script status checks + datasends including throttling what is sent to CTP so as to not overwhelm
Mike thinks offering an API that lists data reception that Sundar can query against could work. Sundar agrees. However, John clarifies this is likely only necessary during resends. Arvind wonders if Tableau work we are doing could cater to this requirement?
Arvind wonders if this can be tabled (into the icebox) since we don't plan any major resends. Sundar concurs we should table until a future time.
Besides tabling this for onw, we will also plan on doing smaller resends into batches + we will hold off if there are reception issues on the SCA end.
Sundar and I were discussing this and it would be great to be able to Query the DICOM receiver for Orthanc to verify it received all the images. Do we think this is possible?
The text was updated successfully, but these errors were encountered: