DICOM Transfer Error to Google Healthcare DICOM Adapter

26 views
Skip to first unread message

Imran Haider

unread,
May 6, 2024, 9:05:14 AM5/6/24
to GCP Healthcare Discuss
Hello All,

I have no issue transferring DICOM images from the PacsOne DICOM server to the Google Healthcare API - DICOM Store.

However, I am encountering the following error in the Google Healthcare API when trying to transfer DICOM images from the Orthanc server to the Google Healthcare API - DICOM Store:

[dulfsm.c,1165 20240428 15:07:43,426] DUL Action: 9
[dulfsm.c,1167 20240428 15:07:43,426] DUL Action :lame: DT 2 Indicate P DATA POO Received
[dulfsm.c,1169 20240428 15:07:43,426] DUL Reid State: 6 (clulfsm.c,1171 20240428 15:07:43,426)
[dulfsm.c,2510 20240428 15:07:43,426] P.DATA-TF Command PDU Size (Length+6): 136 (0x88) srv2.c,752 20240428 15:07:43,426 ERROR: C-STORE-RIP Command received with FAILURE/REFUSED status:(0x0110): Processing Failure
[srv2.c,759 20240428 15:07:43,426] ERROR: Contents of C-STORE-RIP DIOCM Command: Time of this message: Sun Apr 28 2024 15:07:43
[dcm.c,0 20240428 15:07:43,426] (0000,0100) [U5/2] -0x8001 (C-STORE-R50- ; CPU Command Field
[dcm.c,0 20240428 15:07:43,426] (0000,0120) [US/2] 1 ; CPO Message ID Responded t
[dcm.c,0 20240428 15:07:43,426] (0000,0800) [U5/2] '0x0101 (Null Data Set)" • CMD Data Set T
[dcm.c,0 20240428 15:07:43,426] (0000,0900) [U5/2)-000110" ; CM0 Status
[dcm.c,0 20240428 15:07:43,426] (0000 0902 10/64 "tom. le.cloud.healthcare.IDicomidebClientSDicomWebExce•tion: S' • CND Error Comment
[srv2.c,764 20240428 15:07:43,426)
[storage.c,746 20240428 15:07:43,426) Took 500.000 as for SCU to receive (-STORE-Mg, Coamand from the SCP.
[storage.c,831 20240428 15:07:43,426] Took a total of 531.000 ms to complete C-STORE Requests.
[storage.c,837 20240428 15:07:43,426] This included 515.000 as to complete the followin DICOM Messa in communication: [storage.c,842 20240428 15:07:43,426] 0.000 as to send a C-STORE-RQ Command.
[storage.c,845 20240428 15:07:43,426] 15.000 ms to send a C-STORE-RQ Data Set.
[storage.c,848 20240428 15:07:43,426] 500.000 as to receive a C-STORE-RIP Command.
[ut.c,2018 20240428 15:07:43,426] utget_longlongpath_size ("I:\ali\site\log\rropri 1.1 - 0019E844 called
[ut.c,2067 20240428 15:07:43,426] "I:\ali\site\log\rropri_l.log' is not a Directory.
[ut.c,2095 20240428 15:07:43,426] ut_get_longlong_path_size ("I:\ali\site\log\rropri_l.log-, (00000000,040130c528) 19973416) returned ERROR AT [ALISenderAgent.m,707] ON 20240428 15:07:43,426 IN 'OicomSend' INFORM 'log' TITLE 'C-STORE INCOMPLETE': Call to distoreSCU_store_object_with_transfer() returne ERROR AT [ALISenderAgent.m,792] ON 20240428 15:07:43,426 IN 'alidcmsendagent' INFORM 'log' TITLE 'STATUS FAILURE': C-STORE failed ration. Status - 0x0110 Processin [ALISendlobError.m,74 20240428 15:07:43,426] In the method intNithErrorCode. Error Code found: 19 [ALISenderAgent.m,3277 20240428 15:07:43,426] Closing DICOM object [ALISenderagent.m,3286 20240428 15:07:43,426] Closing OICOM meta inforsation header [ALISenderAgent.m,3886 20240428 15:07:43,426] No temp path to delete ALISender•ent.m 3574 20240428 15:07:43 426 DO send job cleanup
[ALISenderAgent.m,3608 20240428 15:07:43,426] Closing association

Truc Le

unread,
May 6, 2024, 2:12:15 PM5/6/24
to GCP Healthcare Discuss
Hi Imran Haider,

Thanks for reaching out to us. From the error message you posted, the core error is:
  • C-STORE-RP Command received with FAILURE/REFUSED status: (0x0110): Processing Failure
This error indicates that the PACS server did not process the C-STORE operation sent by the client. Unfortunately, error logs from the client will not help diagnose the root cause further. You will need to see the adapter logs to understand the problem. The troubleshoot section of our guide has more details (https://cloud.google.com/healthcare-api/docs/how-tos/dicom-connect-pacs#troubleshoot). The logs will be available in Cloud Logging.

For the next steps, I recommend you follow the “Connect a PACS to the Cloud Healthcare API” guide (https://cloud.google.com/healthcare-api/docs/how-tos/dicom-connect-pacs) to ensure you have configured the adapter correctly. I also suggest you test the adapter with DICOM instances without PII such that we can reproduce the issue. Google makes some datasets publicly available, see https://cloud.google.com/healthcare-api/docs/how-tos/dicom-connect-pacs#import_dicom_images_to_the_dicom_store for more information.

If you still have errors after following the configuration guide, you can post the adapter errors and we can help investigate those.
Reply all
Reply to author
Forward
0 new messages