Sn4807 - workaround to solve intermittent send issue between innova and ea v2.1/3.0, from INX100

Sn4807 - workaround to solve intermittent send issue between innova and ea v2.1/3.0, from INX100 Sn4807 - workaround to solve intermittent send issue between innova and ea v2.1/3.0, from INX100. 1 INTRODUCTION (OVERVIEW / PROBLEM / SYMPTOM) When anytime after the first series an INNOVA sends a series to EA V2.1 or EA V3.0, the DICOM association can time out because the EA is "processing" the data it is receiving from the first run or sequence, and therefore the subsequent sequence might not be accepted. This is due to the study-locking mechanism. The result can be that EA does not accept a 21 March 2008 SERVICE NOTE Page 1 of 6 Innova Systems SN 4807 Rev. 1 5308524-8EN WORKAROUND TO SOLVE INTERMITTENT SEND ISSUE BETWEEN INNOVA AND EA V2.1/3.0 1 INTRODUCTION (OVERVIEW / PROBLEM / SYMPTOM) When anytime after the first series an INNOVA sends a series to EA V2.1 or EA V3.0, the DICOM association can time out because the EA is "processing" the data it is receiving from the first run or sequence, and therefore the subsequent sequence might not be accepted. This is due to the study-locking mechanism. The result can be that EA does not accept any additional series of that study, so they remain unsent on the INNOVA, therefore a manual send from INNOVA is needed. This service note suggests a workaround for that problem. A workaround using asynchronous communication mode between EA and INNOVA (asynchronous C-STORE on EA) that was already installed on a number of sites might result in data loss when not configured correctly . The intent of this service note is to make it very clear under which conditions this workaround can be applied. - The preferred workaround is based on increasing DICOMPushTimeout setting on INNOVA if supported. - If DICOMPushTimeout is not configurable, the Asynchronous Mode should be used on EA if an INNOVA supports and has been configured for Storage Commitment. INNOVA Quality-Control personnel must then be sure that they view the status ARCHIVED on the INNOVA before deleting any studies on it when the INNOVA is in Storage Commit mode. - The default Normal mode should be used if an INNOVA does not support Storage Commitment. INNOVA Quality-Control personnel should then look for the status SENT prior to deleting any studies on the INNOVA. - In an environment in which some INNOVAs support and use Storage Commitment and others do not, the Normal mode should be used, and DICOMPushTimeout should be increased where possible. INNOVA Quality-Control personnel should then look for the status SENT prior to deleting any studies on the INNOVA