Announcement

Collapse
No announcement yet.

Mirth 2.2.X loses image data when sending DICOM

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

  • Mirth 2.2.X loses image data when sending DICOM

    Hi,

    i have a simple Problem (I hope).
    I created a BasicDicomObject with JavaScript within a FileOutputStream and tranformed it into a ByteArray.

    With this ByteArray I proceeded like followed:
    Code:
    connectorMap.put('DICOMMESSAGE',FileUtil.encode(fos.toByteArray()))
    You see, I used the variable DICOMMESSAGE to store my encoded DICOM bytearray in.
    So far, so good.
    My DICOM object contains Image data. Here is a partcial dump of the file when I write it to the filesystem:

    (0028,0008) IS [1] # 2, 1 NumberOfFrames
    (0028,0010) US 2339 # 2, 1 Rows
    (0028,0011) US 1654 # 2, 1 Columns
    (0028,0100) US 8 # 2, 1 BitsAllocated
    (0028,0101) US 8 # 2, 1 BitsStored
    (0028,0102) US 7 # 2, 1 HighBit
    (0028,0103) US 0 # 2, 1 PixelRepresentation
    (0032,1032) PN [^^] # 2, 1 RequestingPhysician
    (0038,0010) LO (no value available) # 0, 0 AdmissionID
    (0040,0253) SH (no value available) # 0, 0 PerformedProcedureStepID
    (0040,0254) SH (no value available) # 0, 0 PerformedProcedureStepDescription
    (0040,0280) ST [test comment(Physician 11.11.2013 09:04, Doctor Account / Final... # 174, 1 CommentsOnThePerformedProcedureStep
    (0040,2016) LO (no value available) # 0, 0 PlacerOrderNumberImagingServiceRequest
    (0040,2017) LO [59110000271] # 12, 1 FillerOrderNumberImagingServiceRequest
    (7fe0,0010) OB (PixelSequence #=2) # u/l, 1 PixelData
    (fffe,e000) pi (no value available) # 0, 1 Item
    (fffe,e000) pi ff\d8\ff\e0\00\10\4a\46\49\46\00\01\02\00\00\01\00 \01\00\00\ff\db... # 270964, 1 Item
    (fffe,e0dd) na (SequenceDelimitationItem) # 0, 0 SequenceDelimitationItem
    If I now send this via MIRTH DICOM Sender to a MIRTH DICOM Listener I lose this data. See the dump here:
    (0028,0008) IS [1] # 2, 1 NumberOfFrames
    (0028,0010) US 2339 # 2, 1 Rows
    (0028,0011) US 1654 # 2, 1 Columns
    (0028,0100) US 8 # 2, 1 BitsAllocated
    (0028,0101) US 8 # 2, 1 BitsStored
    (0028,0102) US 7 # 2, 1 HighBit
    (0028,0103) US 0 # 2, 1 PixelRepresentation
    (0032,1032) PN [^^] # 2, 1 RequestingPhysician
    (0038,0010) LO (no value available) # 0, 0 AdmissionID
    (0040,0253) SH (no value available) # 0, 0 PerformedProcedureStepID
    (0040,0254) SH (no value available) # 0, 0 PerformedProcedureStepDescription
    (0040,0280) ST (no value available) # 0, 0 CommentsOnThePerformedProcedureStep
    (0040,2016) LO (no value available) # 0, 0 PlacerOrderNumberImagingServiceRequest
    (0040,2017) LO [90670030896] # 12, 1 FillerOrderNumberImagingServiceRequest
    Now my question is, is the Sender or Receiver responsible for losing my data?
    Is there another way to do that?

    thank you very much!

  • #2
    got it,
    it is the Listener who loses it. I send it to another vendor DICOM Listener and the image data is still there.

    So therefor I am good.

    But anyway, is the image data gone for good when receiving this message within MIRTH or is there a way to get it?

    Comment


    • #3
      Is it possible to generate CCD documents using the free version of MirthConnect ?
      If so, are there any documentation for generating the CCD documents ?

      Comment

      Working...
      X