Modality Worklist...

    I have successfully loaded the Conquest Modality worklist and set up our Fujitsu DR machine to initiate the c-find to pull information from the Modality Worklist into the Fujitsu Modality. The worklist on the Fujitsu side looks good, but when we seclect a paitent to initiate a study, nothing happens. I have tried to work with Fujitsu to get assistance, but have had little luck. They don't really know much Dicom. I know it is a long shot, but I'm wondering if you have any ideas of what I may be missing to complete the process on the Fujitsu side.


    I did create a worklist for Fujitsu using our eRad pacs pulling records from the Conquest MWL then Fujitsu initiated a c-Find -Rsp to the eRad instead of Pacs. (I know that sounds redundant, but we were trying various angles.) The Fujitsu DX was able to initiate a study from that worklist. Unfortunately, eRad only pulls from Conquest every 1/2 hour which doesn't meet our needs (long story). Supposedly eRad cannot change that interval. Anyway, eRad pacs must do something that Conquest doesn't or vice-versa.


    I'm using Conquest version 1.4.16.


    Here is a copy of the log where the Fujitsu (FDX-CSL) pulls info from Conquest. The record does end up in Fujitsu, but when we try to double-click the patient name to initiate the study, nothing happens.


    8/23/2011 12:33:04 PM [CONQUESTSRV1] Connected by address: f90d000a
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Testing transfer: '1.2.840.10008.1.2' against list #0 = '1.2.840.10008.1.2'
    8/23/2011 12:33:04 PM [CONQUESTSRV1]
    8/23/2011 12:33:04 PM [CONQUESTSRV1] UPACS THREAD 3: STARTED AT: Tue Aug 23 12:33:04 2011
    8/23/2011 12:33:04 PM [CONQUESTSRV1] A-ASSOCIATE-RQ Packet Dump
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Calling Application Title : "FDX-CSL "
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Called Application Title : "CONQUESTSRV1 "
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 32768
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Number of Proposed Presentation Contexts: 1
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Server Command := 0020
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Message ID := 0003
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0000,0002 22 UI AffectedSOPClassUID "1.2.840.10008.5.1.4.31"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0000,0100 2 US CommandField 32
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0000,0110 2 US MessageID 3
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0000,0700 2 US Priority 0
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0000,0800 2 US DataSetType 258
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] (ModalityWorkListQuery) search level:
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0008,0005 0 CS SpecificCharacterSet (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0008,0050 0 SH AccessionNumber (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0010,0010 0 PN PatientName (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0010,0020 0 LO PatientID (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0010,0030 0 DA PatientBirthDate (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0010,0040 0 CS PatientSex (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0020,000d 0 UI StudyInstanceUID (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0032,1032 0 PN RequestingPhysician (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0040,0100 0 SQ ScheduledProcedureSt Sequence Item
    8/23/2011 12:33:04 PM [CONQUESTSRV1] >0008,0060 2 CS Modality "DX"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] >0040,0001 8 AE ScheduledStationAETi "FDX-CSL "
    8/23/2011 12:33:04 PM [CONQUESTSRV1] >0040,0002 0 DA ScheduledProcedureSt (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] >0040,0003 0 TM ScheduledProcedureSt (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] >0040,0006 0 PN ScheduledPerformingP (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] >0040,0007 0 LO ScheduledProcedureSt (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] >0040,0009 0 SH ScheduledProcedureSt (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0040,1001 0 SH RequestedProcedureID (empty)
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Query On Modality WorkList
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Queried item 0008 0005 is not in the database
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Issue Query on Columns: DICOMWorkList.AccessionN, DICOMWorkList.PatientNam, DICOMWorkList.PatientID, DICOMWorkList.PatientBir, DICOMWorkList.PatientSex, DICOMWorkList.StudyInsta, DICOMWorkList.ReqPhysici, DICOMWorkList.Modality, DICOMWorkList.ScheduledA, DICOMWorkList.StartDate, DICOMWorkList.StartTime, DICOMWorkList.PerfPhysic, DICOMWorkList.SchedPSDes, DICOMWorkList.SchedPSID, DICOMWorkList.ReqProcID
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Values: DICOMWorkList.Modality = 'DX' and DICOMWorkList.ScheduledA = 'FDX-CSL'
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Tables: DICOMWorkList
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Sorting (DICOMWorkList.PatientNam) DoSort := 1
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Query Distinct Tables: DICOMWorkList
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Columns : DICOMWorkList.AccessionN, DICOMWorkList.PatientNam, DICOMWorkList.PatientID, DICOMWorkList.PatientBir, DICOMWorkList.PatientSex, DICOMWorkList.StudyInsta, DICOMWorkList.ReqPhysici, DICOMWorkList.Modality, DICOMWorkList.ScheduledA, DICOMWorkList.StartDate, DICOMWorkList.StartTime, DICOMWorkList.PerfPhysic, DICOMWorkList.SchedPSDes, DICOMWorkList.SchedPSID, DICOMWorkList.ReqProcID
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Where : DICOMWorkList.Modality = 'DX' and DICOMWorkList.ScheduledA = 'FDX-CSL'
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Order : DICOMWorkList.PatientNam
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0008,0050 14 SH AccessionNumber "9999TST212352 "
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0010,0010 8 PN PatientName "TEST^TWO"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0010,0020 8 LO PatientID "9999TST2"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0010,0030 8 DA PatientBirthDate "19670219"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0010,0040 2 CS PatientSex "M "
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0020,000d 54 UI StudyInstanceUID "1.2.392.200036.9125.2.188489116722356.9999212352.2222"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0032,1032 6 PN RequestingPhysician "VIZZI "
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Coding sequence (0040,0100), level=1
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0008,0060 2 CS Modality "DX"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0040,0001 8 AE ScheduledStationAETi "FDX-CSL "
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0040,0002 8 DA ScheduledProcedureSt "20110810"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0040,0003 6 TM ScheduledProcedureSt "154500"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0040,0006 6 PN ScheduledPerformingP "VIZZI "
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0040,0007 4 LO ScheduledProcedureSt "XRAY"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0040,0009 4 SH ScheduledProcedureSt "XRAY"
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0040,1001 6 SH RequestedProcedureID "72170 "
    8/23/2011 12:33:04 PM [CONQUESTSRV1] Records = 1
    8/23/2011 12:33:04 PM [CONQUESTSRV1] First record of cleaned response:
    8/23/2011 12:33:04 PM [CONQUESTSRV1] 0008,0005 10 CS SpecificCharacterSet "ISO_IR 100"
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0008,0050 14 SH AccessionNumber "9999TST212352 "
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0008,1110 0 SQ ReferencedStudySeque Sequence Item
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0008,1120 0 SQ ReferencedPatientSeq Sequence Item
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0010,0010 8 PN PatientName "TEST^TWO"
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0010,0020 8 LO PatientID "9999TST2"
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0010,0030 8 DA PatientBirthDate "19670219"
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0010,0040 2 CS PatientSex "M "
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0020,000d 54 UI StudyInstanceUID "1.2.392.200036.9125.2.188489116722356.9999212352.2222"
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0032,1032 6 PN RequestingPhysician "VIZZI "
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0040,0100 0 SQ ScheduledProcedureSt Sequence Item
    8/23/2011 12:33:05 PM [CONQUESTSRV1] >0008,0060 2 CS Modality "DX"
    8/23/2011 12:33:05 PM [CONQUESTSRV1] >0040,0001 8 AE ScheduledStationAETi "FDX-CSL "
    8/23/2011 12:33:05 PM [CONQUESTSRV1] >0040,0002 8 DA ScheduledProcedureSt "20110810"
    8/23/2011 12:33:05 PM [CONQUESTSRV1] >0040,0003 6 TM ScheduledProcedureSt "154500"
    8/23/2011 12:33:05 PM [CONQUESTSRV1] >0040,0006 6 PN ScheduledPerformingP "VIZZI "
    8/23/2011 12:33:05 PM [CONQUESTSRV1] >0040,0007 4 LO ScheduledProcedureSt "XRAY"
    8/23/2011 12:33:05 PM [CONQUESTSRV1] >0040,0009 4 SH ScheduledProcedureSt "XRAY"
    8/23/2011 12:33:05 PM [CONQUESTSRV1] 0040,1001 6 SH RequestedProcedureID "72170 "
    8/23/2011 12:33:05 PM [CONQUESTSRV1] C-Find (Modality Work List) located 1 records
    8/23/2011 12:33:05 PM [CONQUESTSRV1] UPACS THREAD 3: ENDED AT: Tue Aug 23 12:33:05 2011
    8/23/2011 12:33:05 PM [CONQUESTSRV1] UPACS THREAD 3: TOTAL RUNNING TIME: 1 SECONDS
    8/23/2011 12:47:56 PM [CONQUESTSRV1] Connected by address: fa0d000a


    Thanks for any assistance.

    Hi,


    if you compare the query:


    0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"
    0008,0005 0 CS SpecificCharacterSet (empty)
    0008,0050 0 SH AccessionNumber (empty)
    0010,0010 0 PN PatientName (empty)
    0010,0020 0 LO PatientID (empty)
    0010,0030 0 DA PatientBirthDate (empty)
    0010,0040 0 CS PatientSex (empty)
    0020,000d 0 UI StudyInstanceUID (empty)
    0032,1032 0 PN RequestingPhysician (empty)
    0040,0100 0 SQ ScheduledProcedureSt Sequence Item
    >0008,0060 2 CS Modality "DX"
    >0040,0001 8 AE ScheduledStationAETi "FDX-CSL "
    >0040,0002 0 DA ScheduledProcedureSt (empty)
    >0040,0003 0 TM ScheduledProcedureSt (empty)
    >0040,0006 0 PN ScheduledPerformingP (empty)
    >0040,0007 0 LO ScheduledProcedureSt (empty)
    >0040,0009 0 SH ScheduledProcedureSt (empty)
    0040,1001 0 SH RequestedProcedureID (empty)


    With the response:


    0008,0005 10 CS SpecificCharacterSet "ISO_IR 100"
    0008,0050 14 SH AccessionNumber "9999TST212352 "
    0008,1110 0 SQ ReferencedStudySeque Sequence Item
    0008,1120 0 SQ ReferencedPatientSeq Sequence Item
    0010,0010 8 PN PatientName "TEST^TWO"
    0010,0020 8 LO PatientID "9999TST2"
    0010,0030 8 DA PatientBirthDate "19670219"
    0010,0040 2 CS PatientSex "M "
    0020,000d 54 UI StudyInstanceUID "1.2.392.200036.9125.2.188489116722356.9999212352.2222"
    0032,1032 6 PN RequestingPhysician "VIZZI "
    0040,0100 0 SQ ScheduledProcedureSt Sequence Item
    >0008,0060 2 CS Modality "DX"
    >0040,0001 8 AE ScheduledStationAETi "FDX-CSL "
    >0040,0002 8 DA ScheduledProcedureSt "20110810"
    >0040,0003 6 TM ScheduledProcedureSt "154500"
    >0040,0006 6 PN ScheduledPerformingP "VIZZI "
    >0040,0007 4 LO ScheduledProcedureSt "XRAY"
    >0040,0009 4 SH ScheduledProcedureSt "XRAY"
    0040,1001 6 SH RequestedProcedureID "72170 "


    You see that these are quite the same. Only, there are two empty sequences generated by conquest:


    0008,1110 0 SQ ReferencedStudySeque Sequence Item
    0008,1120 0 SQ ReferencedPatientSeq Sequence Item


    and the query has extra:


    0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"


    You could add to the end of dicom.ini:


    [lua]
    ModalityWorkListQueryResultConverter0 = Data.ReferencedStudySequence = nil; Data.ReferencedPatientSequence = nil;


    to clear the two extra sequences and make the response more like the query. Similarly (use one or the other not both):


    [lua]
    ModalityWorkListQueryResultConverter0 = Data.ReferencedStudySequence = nil; Data.ReferencedPatientSequence = nil; Data.TransferSyntaxUID = '1.2.840.10008.1.2'


    would make the response totally equal to the query.


    Or you could use a network sniffer like the one from DVTk:


    http://dicom.dvtk.org/modules/…+Analyzer&cmenu=downloads


    to see the response from eRad. This would also tell us what to do.


    Good luck,


    Marcel

    I tried the changes and although the log inidcated the sequences would be removed, it did not make a difference on the Fuji side. (I called it Fujitsu before, but was mixing up my 'F' Japanese companies.) I tried to attach 2 log files from Fuji that show the conquest then the erad, but I don't seem to have permission to attach files.


    Fuji did email me yesterday asking I turn off their request for certain tags. I tried that to no avail, but need to send them a capture of the log files. Still working on that.


    Earlier in the month, their field engineer compared the eRad and Conquest log files and highlighted the differences for me. I also tried to paste that in, but I can't. These tags were on Conquest's response but not on eRad's. Only the first tag actually had data:
    (0008,0005) - "ISO_IR_100"
    (0008,0052)
    (0008,1110) - we addressed with the ini file
    (0008,1120) - we addressed with the ini file
    (0032,1060)
    (0040,0007) - I think the log you looked at had this field. I tried with and without it
    (0040,0009) - I think the log you looked at had this field. I tried with and without it
    (fffe,e00d) - ?
    (fffe,e0dd) - ?
    (0040,0001) - I think the log you looked at had this field. I tried with and without it


    This tag was on both systems but with different data. This tag is not on the log I send on the initial post. We did try turning off some tags on the Fuji side so perhaps this is the result of one of those since I can't find it on a more recent log.
    (fffe,e000) -1(Oxffffffff) NO - eRad had: (fffe,e000) 54(0x36) NO


    Thanks again for your assistance.


    Jeanne

    Hi Jeanne,


    with the scripting I shown you can delete any tag from the response and create addirional tag to create exactly the same response as eRad's. fffe,e000 is a sequence delimitor, to signal a part of a sequence. Hope this helps a bit.


    Marcel

    One thing I did notice when comparing the eRad and Conquest logs is that eRad changed the StudyUID from what I had in the WORKLIST to something else. I don't really understand how Study UID's are created, but Fuji does have the setting on that they would generate the Study UID so I didn't worry too much about it. Should I be using the prefix defined in the dicom.ini file? How should I generate the suffix?


    Thanks,


    Jeanne

    Hoi Jeanne,


    maybe Fuji rejects the worklist because the studyuid is used before. Try adding some random digits to it and see what happens. I have no option yet to generate a UID, however, there is a server command to do this that may work from lua.


    Marcel

    Marcel,


    This was Fuji's reply:


    Here is what Japan said this morning in our conference call. Tag 0040,0100 is Scheduled Procedure Step Sequence, that's the one that's causing the problem. You see below in the excerpt, Conquest is sending a -1 value.
    We think that the cause of this problem is Conquest side.
    Conquest sends SQ tag with undefined length.
    However, this format was incorrect.

    CL send format is as follows,
    2011/08/09 17:22:28 CONQUESTSRV1 S <1164> (0040,0100) -1(0xffffffff) SQ
    2011/08/09 17:22:28 CONQUESTSRV1 S <1164> (fffe,e000) -1(0xffffffff) NO

    Conquest send format is as follows,
    2011/08/09 17:22:29 CONQUESTSRV1 R <1164> (0040,0100) 0(0x0) SQ
    2011/08/09 17:22:29 CONQUESTSRV1 R <1164> (fffe,e000) -1(0xffffffff) NO
    This format is incorrect.
    Please request to correct format to RIS side.

    How would I code it to send a explicit length or something other than -1?
    eRad sent:
    (0040,0100) 62(0x3e) SQ
    (fffe,e000) 54(0x36) NO


    Thanks again for your help.



    Jeanne

    Marcel,


    Thanks for your help and I feel bad taking up anymore time, but I wanted to leave the post with an update so other readers would know where I left off.


    I tried deleting and recreating the sequence using the importconverter - WorklistQueryConverter0. I also tried the ModalityWorklistQueryResultConverter0, but neither worked. It deleted the sequence but Fuji wants it there. They just want a valid length.


    It seems as though Conquest returns the delimitor (fffe,e000) back just the way they sent it rather than changing it like the (0040,0100) was changed from (0040,0100)-1(0xfffffff) SQ to (0040,0100) 0 (0x0) SQ.


    I have gone through the forum and documentation, but don't really see how to change the length on the specific delimiter on the fly before we return the results.


    I'm going to see if perhaps Fuji can send the delimiter as (fffe,e000)0(0x0) NO instead of (fffe,e000)-1(0xffffffff) NO. I doubt I'll get far with that, but perhaps.


    Thanks again for your prompt responses. Sorry I couldn't get further!


    Jeanne

    I do populate the sequence with a few fields. Below is a copy of Fuji's log because it shows the delimiters and the Conquest's log doesn't.



    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> -> "VIZZI"
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (0040,0100) 0(0x0) SQ
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (fffe,e000) -1(0xffffffff) NO
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (0008,0060) 2(0x2) CS
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> -> "DX"
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (0040,0001) 7(0x7) AE
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> -> "FDX-CSL"
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (0040,0002) 8(0x8) DA
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> -> "20110913"
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (0040,0003) 6(0x6) TM
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> -> "154500"
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (0040,0006) 5(0x5) PN
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> -> "VIZZI"
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (0040,0007) 0(0x0) LO
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (0040,0009) 0(0x0) SH
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (fffe,e00d) 0(0x0) NO
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (fffe,e0dd) 0(0x0) NO
    2011/09/13 09:33:16 CONQUESTSRV1 R <f50> (0000,0000) 4(0x4) UL -> 70(0x46)



    Interesting to me is Conquest returns the sequence just as Fuji sent it. Here is an excerpt from Fuji's query. Fuji claims Conquest's undefined length on fffe,e000 doesn't follow standard.


    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0040,0000) 4(0x4) UL -> 152(0x98)
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0040,0100) -1(0xffffffff) SQ
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (fffe,e000) -1(0xffffffff) NO
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0008,0000) 4(0x4) UL -> 8(0x8)
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0008,0060) 0(0x0) CS
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0040,0000) 4(0x4) UL -> 64(0x40)
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0040,0001) 7(0x7) AE
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> -> "FDX-CSL"
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0040,0002) 8(0x8) DA
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> -> "20110913"
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0040,0003) 0(0x0) TM
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0040,0006) 0(0x0) PN
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0040,0007) 0(0x0) LO
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (0040,0009) 0(0x0) SH
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (fffe,e00d) 0(0x0) NO
    2011/09/13 09:33:16 CONQUESTSRV1 S <f50> (fffe,e0dd) 0(0x0) NO


    Thanks.

    Hi,


    I face exactly the same issue using conquest with a fuji CR and i can't start a study on the Fuji, although the worklist query works fine.
    Is there any workaround to make the worklist works with a fuji CR device ?


    Thanks.

    Hi,


    the sequence coder in conquest always generates an variable length of -1. I believe this is proper DICOM. I am afraid there is no simple fix other than changing the dicom encoding which is a very comlicated bit of code. I will prototype this change later if you are willing to test it. On which system do you work? Linux, win32 or win64?


    Marcel

    Marcel,


    I use a Windows 2003 / win32 server.
    Of course, i'm ready to test some code if necessary.
    I thought a workaround would have been possible using lua or with some change in dicom.sql but i'm sorry this is not that simple. :?


    Many thanks for your answer.

    Hi,


    I just started and this requires is a fairly major code change, because the length has to be transmitted before the data and has to be calculated correctly. I need several hours to code this that I do not have now. In addition, not accepting an undefined length is a violation of the DICOM standard. Are you sure I have to fix this on my side?


    Marcel

    Hi Marcel,


    I don't want to make you waste your time, so i'm going to do some testing today, and if the WL still not work i will try to call again the Fuji support team.
    I already spent some time with them trying to solve this issue whitout success and i'm afraid this is dead end, but i'd rather waste their time than yours.
    They have to give their customers some support, and they have to respect DICOM standard.
    Please, don't start to do major fix in your code, i will try to have it solved on Fujis side, ans if i really can't manange with their help, i will keep you informed and might ask for your help.


    Many thanks.


    Emmanuel

    Marcel,


    I found Fuji system refuse to process because off a missing study instance UID.
    It seems that i had to put in as a field in ZDS section in my HL7 file.
    But when using a ZDS section in HL7, worklist query does not work anymore. Conquest refuse HL7 file if this section is present, and it make the worklist to be unusable.


    Do you have any explanation about that ?


    Thanks !

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login