docscan integration

Historical record of a forum that was for discussion of the setup, configuration, and use of OnePacs for research and educational purposes (non-clinical use).

Please direct any support inquiries through the standard OnePacs ticketing and support system.

The "Announcements" forum will continue to be active and contain announcements related to the OnePacs system.
Locked
mmazon
Posts: 41
Joined: Fri Mar 30, 2012 9:49 am
Location: São Paulo / Brazil
Contact:

docscan integration

Post by mmazon » Thu Nov 14, 2013 7:40 am

Hi. I´m trying to use pacsmatt docscan to scan forms and convert and upload it directly to a new series in a previous sent study.
After all aparently right configured, i´m getting the following error on server.log, and no image accepted.

2013-11-14 10:32:32,057 INFO DOCSCAN->PG-CPAPIR-RMT (TCPServer-1-6) [org.dcm4cheri.net.FsmImpl] received A-ABORT
source=0 - service-user
reason=0 - reason-not-specified
2013-11-14 10:32:32,057 INFO DOCSCAN->PG-CPAPIR-RMT (TCPServer-1-6) [org.dcm4chex.archive.mbean.FileSystemMgtService] Check available Disk Space
2013-11-14 10:32:32,057 INFO DOCSCAN->PG-CPAPIR-RMT (TCPServer-1-6) [org.dcm4cheri.net.FsmImpl] closing connection - Socket[addr=/192.168.1.40,port=4928,localport=4104]
2013-11-14 10:32:32,057 ERROR -> (TCPServer-1-6) [org.dcm4cheri.net.ActiveAssociationImpl] org.dcm4che.net.PDUException: Received A-ABORT
source=0 - service-user
reason=0 - reason-not-specified
2013-11-14 10:32:32,057 INFO -> (TCPServer-1-6) [org.dcm4cheri.server.ServerImpl] finished - Socket[addr=/192.168.1.40,port=4928,localport=4104]

Tried to do a storescu.exe test, using the following parameters:

C:\PACSMATT\DocScan\Resources\dcmtk>storescu -v -d +v -aet DOCSCAN -aec **mygatewayAET** 192.168.1.40 4104 test
where test is a file picked from one of onepacs stored study (a dicom image).

The storescu gives me the following error:

Requested Extended Negotiation: none
Accepted Extended Negotiation: none
Association Accepted (Max Send PDV: 16340)
--------------------------
Sending file: test
Transfer: JPEG2000 -> LittleEndianExplicit
Store SCU RQ: MsgID 1, (MR)
XMIT:DIMSE Warning: (DOCSCAN,PG-CPAPIR-RMT): sendMessage: unable to convert data
set
from 'JPEG 2000 (Lossless or Lossy)' transfer syntax to 'LittleEndianExplicit'.

storescu: Store Failed, file: test:
0006:020e DIMSE Failed to send message
storescu: SCU Failed:
0006:020e DIMSE Failed to send message
Aborting Association

Any ideas how to make this work ? What i need is to upload the forms of the user into a series in my sent studies.
Mário Arnaldo Mazon, Md
PersonalRad - Inovative Radiology Solutions
http://www.personalrad.com.br

justin
Posts: 371
Joined: Wed Nov 26, 2008 2:34 pm

Re: docscan integration

Post by justin » Thu Nov 14, 2013 10:36 am

Hi Mário,

Ok, you're trying to send scanned documents to your local OnePacs Gateway from a document scanning application. That shouldn't be a problem - we have a lot of users doing the same. I think it would help to see more of your server logs prior to the segment you posted. Could you please send via OnePacs message to "OnePacs Logs"? Please update this post once that's complete.

Also, your test appears to be failing on the docscan side. It's attempting to decompress the JPEG2000 compressed image you are referencing. I believe you can use the -xv and -xw options in dcmtk to negotiate the JPEG2000 transfer syntaxes so it sends as-is to the OnePacs Gateway.

Regards,

Justin

mmazon
Posts: 41
Joined: Fri Mar 30, 2012 9:49 am
Location: São Paulo / Brazil
Contact:

Re: docscan integration

Post by mmazon » Thu Nov 14, 2013 1:26 pm

Some of this log´s are from storescu.exe utility, hand-called by me with these parameters to test the process.
The application we are using does this in the background. Because the error in onepacs logs appears the same, and because the application documentation says anything about "the image is transformed to a DICOM object in Explicit Little Endian transfer syntax.", i think the problem was in the transfer.
What kind of transfer syntax onepacsgateway suports ?
By the way, can you recomend me wich doc scan application is suposed to work with OP ?

Thank you.
Mário Arnaldo Mazon, Md
PersonalRad - Inovative Radiology Solutions
http://www.personalrad.com.br

mmazon
Posts: 41
Joined: Fri Mar 30, 2012 9:49 am
Location: São Paulo / Brazil
Contact:

Re: docscan integration

Post by mmazon » Thu Nov 14, 2013 1:29 pm

If you wanna try, this is a free application, smaller and simpler, which can be downloaded and tested from http://www.pacsmatt.com/progs/docscan
If is possible, can you test it in your environment, please ?
Mário Arnaldo Mazon, Md
PersonalRad - Inovative Radiology Solutions
http://www.personalrad.com.br

justin
Posts: 371
Joined: Wed Nov 26, 2008 2:34 pm

Re: docscan integration

Post by justin » Thu Nov 14, 2013 2:24 pm

Hi Mário,

Any document scanning software that generates compliant DICOM should work. We don't certify individual products because there are thousands of them and the DICOM standard provides for interoperability.

The OnePacs Gateway does support Explicit Little Endian (as required by a DICOM C-STORE SCP).

Without seeing the rest of your logs, it's difficult to say what the problem is. But here's a guess. It looks like you're trying to have DOCSCAN send to the OnePacs Gateway using a called AE title of "PG-CPAPIR-RMT". That AE title doesn't appear to match with any of your facilities or the allowed aliases. My guess is that the Gateway is rejecting the association because of this. I would recommend just sending to the alias AE title of ONEPACS (case sensitive). Please give that a try and let us know if that fixes the problem.

Best,

Justin

mmazon
Posts: 41
Joined: Fri Mar 30, 2012 9:49 am
Location: São Paulo / Brazil
Contact:

Re: docscan integration

Post by mmazon » Fri Nov 22, 2013 9:32 am

Hi. I´ve sent the logs and the dicom file (encapsulated jpeg) to onepacs log account.
Thank you by your attention.
Mário Arnaldo Mazon, Md
PersonalRad - Inovative Radiology Solutions
http://www.personalrad.com.br

justin
Posts: 371
Joined: Wed Nov 26, 2008 2:34 pm

Re: docscan integration

Post by justin » Fri Nov 22, 2013 10:22 am

The error is coming from the SCU side - not the OnePacs side.

Code: Select all

XMIT:DIMSE Warning: (DOCSCAN,ONEPACS): CStoreRQ: AffectedSOPInstanceUID: bad size
storescu: Store Failed, file: c:\dicom.dcm:
My guess is that this is related to the illegal SOP instance UID value in the image you provided. It's value has a length of 65 characters whereas DICOM only permits a max of 64.

Justin

mmazon
Posts: 41
Joined: Fri Mar 30, 2012 9:49 am
Location: São Paulo / Brazil
Contact:

Re: docscan integration

Post by mmazon » Fri Nov 22, 2013 2:25 pm

No sucess.. I´ve corrected the SOP UID, but got the following error:

Sending file: dicom.dcm
Transfer: JPEGBaseline -> LittleEndianExplicit
Store SCU RQ: MsgID 1, (SC)
XMIT:DIMSE Warning: (DOCSCAN,PG-XXXXX-XXXXX [EDITED BY ONEPACS]): sendMessage: unable to convert da
taset
from 'JPEG Baseline' transfer syntax to 'LittleEndianExplicit'.

storescu: Store Failed, file: dicom.dcm:
0006:020e DIMSE Failed to send message
storescu: SCU Failed:
0006:020e DIMSE Failed to send message
Aborting Association

Tried to use -x=, -xs and -xe without sucess. Any idea ? The aet & aec are checked and correct.
Mário Arnaldo Mazon, Md
PersonalRad - Inovative Radiology Solutions
http://www.personalrad.com.br

justin
Posts: 371
Joined: Wed Nov 26, 2008 2:34 pm

Re: docscan integration

Post by justin » Fri Nov 22, 2013 3:45 pm

Well, I wouldn't say no success. You were having a problem with invalid UIDs, you fixed it, and you encountered a completely different error. That's progress!

Anyway, you appear to be sending JPEG baseline which is a transfer syntax for 8-bit lossy compression. None of the flags you tried matched that transfer syntax. You should try -xy

http://support.dcmtk.org/docs/storescu.html

Code: Select all

  -xy   --propose-jpeg8
          propose default JPEG lossy TS for 8 bit data
          and all uncompressed transfer syntaxes
Also, just to be clear. The problem is unrelated to OnePacs. Your SCU (dcmtk in this case) is unable to decode the imaging data and is not proposing the correct transfer syntax to match your image. OnePacs Gateway 1.9.x will accept JPEG baseline if proposed or LittleEndianExplicit if the data was decompressed.

Regards,

Justin

Locked