The evaluation concluded the potential root cause is a configuration issue (opal-rad side).Customer sites (site a and site b) requested a destination change during a conference call with a kmha engineering employee for vpn/forwarder services, which potentially contributed to the workflow disruption as concomitant devices.Workflow started with site a (mri modality and worklist) and expected to transfer to site b with multiple opportunities for disruption.Opal has a special transfer syntax "xferobject" utilized when transferring from opal-to-opal system.Opal-rad sending to exa utilizing the transfer syntax 'xferobject' caused zero (0) data files to be generated.The files queued in the receiver on exa causing the service to remain in a continuous transfer loop.Kmha is implementing a future code improvement for exa to ensure if the misconfigure occurs in the future, the transfer is rejected immediately.
|