Announcement

Collapse
No announcement yet.

Ultrasound CINE Loop Images - Dicom Storage

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Ultrasound CINE Loop Images - Dicom Storage

    I am having a hard time with this.

    With the power of VMware, I have two matching systems with matching channels. One system has a SQL DB backend and the other system is using Derby.

    Both systems process Dicom images with little issue, however when we send a Ultrasound Cine Loop file, that is where it gets hairy.

    With the Derby backend system, the image passes through Mirth and onto the end destination fine. However, when we send the image through the SQL backend system, we see corrupt image data on the end system.

    I'm not sure if this is truly a DB issue, or what not. I can attach channel information if needed, but like I said, they are literally the same config, line and setting for line and setting.

    Thanks in advance for any insight.

    -Jim

  • #2
    What is your field types in your DBs?

    Comment


    • #3
      Originally posted by cory_cole View Post
      What is your field types in your DBs?
      We are using the default Mirth DB. Nothing has been modified.

      Comment

      Working...
      X