web stats
Mirth Recieving Tomosynthesis images - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 09-28-2017, 07:18 AM
dnoodles dnoodles is offline
What's HL7?
 
Join Date: Sep 2017
Location: Long Island, NY
Posts: 3
dnoodles is on a distinguished road
Talking Mirth Recieving Tomosynthesis images

Good Morning All,
I'm setting up Mirth as a DICOM router to build a CD Burning Application. I am having an issue while sending Tomo Images from my PACS I am getting failures. Mirth doesnt seem to throw an error but PACS gives an error stating:
"No appropriate Presentation Context negotiated for DICOM object"

SOPClassUID:
1.2.840.10008.5.1.4.1.1.13.1.3
Breast Tomosynthesis Image Storage

Any suggestions on how to handle these images?
Reply With Quote
  #2  
Old 10-01-2017, 11:17 AM
jackwhaines jackwhaines is offline
 
Join Date: May 2011
Location: Kansas City, Missouri
Posts: 168
jackwhaines is on a distinguished road
Send a message via Skype™ to jackwhaines
Default

Is the channel source data type set as a DICOM listener?
__________________

-= Jack Haines : Healthcare Integrations, LLC
-= jack.haines@HealthcareIntegrations.com
-= Mirth Connect (Advanced)-certified
-= Gold member of HL7.org
-= Available for Mirth Connect channel development and consultation! Schedule a call with me at https://integrations.as.me
Reply With Quote
  #3  
Old 10-02-2017, 03:07 AM
dnoodles dnoodles is offline
What's HL7?
 
Join Date: Sep 2017
Location: Long Island, NY
Posts: 3
dnoodles is on a distinguished road
Default

Yes, and I dont have any other issues with other studies it seems to be just the Tomo images.
Reply With Quote
  #4  
Old 10-02-2017, 06:12 AM
jackwhaines jackwhaines is offline
 
Join Date: May 2011
Location: Kansas City, Missouri
Posts: 168
jackwhaines is on a distinguished road
Send a message via Skype™ to jackwhaines
Default

And your data type is set to DICOM? What happens if you leave it RAW? Does it still error?
__________________

-= Jack Haines : Healthcare Integrations, LLC
-= jack.haines@HealthcareIntegrations.com
-= Mirth Connect (Advanced)-certified
-= Gold member of HL7.org
-= Available for Mirth Connect channel development and consultation! Schedule a call with me at https://integrations.as.me
Reply With Quote
  #5  
Old 10-02-2017, 06:23 AM
dnoodles dnoodles is offline
What's HL7?
 
Join Date: Sep 2017
Location: Long Island, NY
Posts: 3
dnoodles is on a distinguished road
Default

Yes my Data type is set to DICOM. Unfortunately when I changed to RAW I get the same result.
Reply With Quote
  #6  
Old 10-02-2017, 06:41 AM
jackwhaines jackwhaines is offline
 
Join Date: May 2011
Location: Kansas City, Missouri
Posts: 168
jackwhaines is on a distinguished road
Send a message via Skype™ to jackwhaines
Default

Sent you a PM.
__________________

-= Jack Haines : Healthcare Integrations, LLC
-= jack.haines@HealthcareIntegrations.com
-= Mirth Connect (Advanced)-certified
-= Gold member of HL7.org
-= Available for Mirth Connect channel development and consultation! Schedule a call with me at https://integrations.as.me
Reply With Quote
  #7  
Old 10-18-2017, 02:14 AM
Jose Raya Jose Raya is offline
What's HL7?
 
Join Date: Oct 2017
Location: Spain
Posts: 2
Jose Raya is on a distinguished road
Default

I have the same problem. I'm setting up Mirth as a DICOM router between two Pacs Servers (a External server and internal server).
I am having an error while receiving Breast Tomosynthesis Images from external PACS.

As in the case of @dnoodles, Mirth doesn't seem to throw an error but PACS gives an error:

2017-10-16 17:30:27,351 [DicomClient: 10.61.10.11:11114 Read [193]] INFO - Association Accepted from HDDDR1 to remote AE MIRTH_DES:10.61.10.11:11114
2017-10-16 17:30:27,351 [DicomClient: 10.61.10.11:11114 Read [193]] INFO - Association Accepted:
Application Context: ==DICOM Application Context Name
Implementation Class: 1.2.40.0.13.1.1
Implementation Version: dcm4che-2.0
Local Maximum PDU Size: 116794
Remote Maximum PDU Size: 16384
Called AE Title: MIRTH_DES
Calling AE Title: HDDDR1
Presentation Contexts: 2
Presentation Context 1 [Reject - Abstract Syntax Not Supported] Abstract: Breast Tomosynthesis Image Storage
Transfer: JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]): Default Transfer Syntax for Lossless JPEG Image Compression
Presentation Context 3 [Reject - Abstract Syntax Not Supported] Abstract: Breast Tomosynthesis Image Storage
Transfer: Explicit VR Little Endian
2017-10-16 17:30:27,351 [158] ERROR - Unable to transfer SOP 1.2.840.113681.3232238919.1508138835.5016.204.1 in study 1.3.6.1.4.1.25403.345052680071.3896.20171016080518 0311. Remote device does not accept Breast Tomosynthesis Image Storagein JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]): Default Transfer Syntax for Lossless JPEG Image Compression transfer syntax

Is any workaround for that case?
Reply With Quote
  #8  
Old 10-18-2017, 05:44 AM
Jose Raya Jose Raya is offline
What's HL7?
 
Join Date: Oct 2017
Location: Spain
Posts: 2
Jose Raya is on a distinguished road
Default

I have the same problem.
I'm setting up Mirth as a DICOM router to build a proxy between Pacs Servers (an external and internal).
I am having an issue (the same issue than dnoodles) while receiving a Breast Tomosynthesis Image from the external PACS server. Mirth doesnt seem to recibe nothing but PACS writes the following logs:

2017-10-16 17:30:27,351 [DicomClient: 10.61.10.11:11114 Read [193]] INFO - Association Accepted from HDDDR1 to remote AE MIRTH_DES:10.61.10.11:11114
2017-10-16 17:30:27,351 [DicomClient: 10.61.10.11:11114 Read [193]] INFO - Association Accepted:
Application Context: ==DICOM Application Context Name
Implementation Class: 1.2.40.0.13.1.1
Implementation Version: dcm4che-2.0
Local Maximum PDU Size: 116794
Remote Maximum PDU Size: 16384
Called AE Title: MIRTH_DES
Calling AE Title: HDDDR1
Presentation Contexts: 2
Presentation Context 1 [Reject - Abstract Syntax Not Supported] Abstract: Breast Tomosynthesis Image Storage
Transfer: JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]): Default Transfer Syntax for Lossless JPEG Image Compression
Presentation Context 3 [Reject - Abstract Syntax Not Supported] Abstract: Breast Tomosynthesis Image Storage
Transfer: Explicit VR Little Endian
2017-10-16 17:30:27,351 [158] ERROR - Unable to transfer SOP 1.2.840.113681.3232238919.1508138835.5016.204.1 in study 1.3.6.1.4.1.25403.345052680071.3896.20171016080518 0311. Remote device does not accept Breast Tomosynthesis Image Storagein JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]): Default Transfer Syntax for Lossless JPEG Image Compression transfer syntax


It's any workarround for that error?
Reply With Quote
  #9  
Old 10-18-2017, 04:41 PM
ricber ricber is offline
Mirth Guru
 
Join Date: Jun 2007
Location: Barcelona, Spain
Posts: 181
ricber
Default

Hi all,

usually PACS systems and, in this case MIrth, have a restricted list of abstract syntax (types of images sent from modalities). Common studies like ultrasound or mammogram are widely accepted, but more recent abstract syntax are not included.

Usually those PACS systems have a config file or database table where this list can be configured or expanded. I'm not a frequent dcm4che user and I don't know how to do that, but maybe any other user could help you.

Hoping this shine a light on your trouble!

Ricard
Reply With Quote
Reply

Tags
dicom, recieving, routing, tomo, tomosynthesis

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 02:22 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Mirth Corporation