marcelvanherk Enlightened

  • Member since Jan 4th 2007
  • Last Activity:
Posts
5,686
Likes Received
28
Points
28,965
Profile Hits
1,071

  • Hi Marcel


    I hope you can assist me with the following conquest error below


    In my case i need delay transfer and after few second delete study but study never destroy


    I put this line In my dicom.ini


    [lua]

    ImportConverter2 = script('forward study to DAIPRINT after 10";destroy');



    Many thanks

    Mikel

    • Hi Mikel,


      destroy would destoy the image so that it is not stored. So if it works (I think there is a syntax error with a ") you cannot delayed forward the study. The best course of action is to use nightly cleanup to delete.


      Marcel

    • Hi Marcel,


      I think I have not explained myself well, I do not speak much English


      In my case I use it as a router. The mode that you send me does not allow me to send all the images at the moment and what interests me is to delay the sending. After spending this time, it is not necessary to keep the study.


      But if there is a failure and the study is sent again if it has not been deleted, the images are sent in duplicate, because i need destroy images after send



      Many thanks

    • Hi,


      you cannot delay with an ImportConverter and destroy - "forward to" is done from memory "forward study to" is done from disk. Destroy clears the image before it is stored on disk.


      In sequence:


      Receive

      Import Converter like 'forward to AE'

      Import Converter like 'forward study to AE' saves the command in a cache, not the data

      If not destroyed:

      Store to disk

      Run export converters

      After NN seconds process the cache


      So if you destroy the commands in tha cache refer to non-extistant images.


      Marcel

  • Hi Marcel


    I hope you can assist me with then meaning of the following prompt that I get on conquest dicom server when trying to access dicom files.


    I have an installation of Conquest dicom server 1.4.17d and am getting the following error " missing file MAGO ………"


    Many thanks

    Leroux

    • Hi,


      MAG0 is the data store, e.g., c:\dicomserver\data. If somebeody has moved or deleted image data without taking it out the database that is what you would get.


      Marcel

  • Hi Marcel


    I hope you can assist me with the following conquest error below


    I have an installation of Conquest dicom server 1.4.17d and am getting the following error on server startup "The server is not running properly: no connection Probable cause: NT service failed to start (check account and password."


    Many thanks

    Leroux

    • Hi,


      is it installed as service, than start with uninstalling it as service. Then run the GUI again and see what error messages comes. Or you may be running multiple instances by chance. Close all instances and see if dgate(64).exe runs in task manager and kill it. Alternative would be to reboot the machine.


      Marcel

  • Hi. If you click on search in k-pacs without specifying any parameters, then the dgate process is on the server.exe starts to consume a lot of RAM 1-2 GB until it completely collapses. I guess that's because there's a very large number of records in the database and he's trying to give it away. The question in the following how to limit the number of displayed records for example do not look for more than 100 records, it may force users to write more detailed search queries. Operating system windows server 2012, version of Conquest server 1.4.15. Thanks.

    • Hi Alex,


      can you use posts rather than the wall?


      There is no limit mechanism built-in for DICOM queries. I assume it searched studies, how many are there in total?


      The simplest option is to add a script that detects your query and rejects it. We did a similar thing in Amsterdam.


      Marcel

    • Forgive me I could not find how to publish a post)))). not activated account, on this and not found as create post. )) Let me ask you where you want to add the script?

    • Sorry you are having an issue with the account. A script could be like (added to end of dicom.ini):


      Code
      1. [lua]
      2. QueryConverter0 = if Data.QueryRetrieveLevel=='STUDY' and (Data.StudyInstanceUID=='' and Data.PatientID=='' and Data.StudyData=='') then script('reject') end


      Not tested nor checked for spelling. This should reject an empty query. If you can log what is in the query that you need to reject you can tailor the code. There is only ONE QueryConverter so everything must be on one line.


      Marcel

  • can you help me ?

    I've tried multiple times to activate an account and I'm not receiving any email correspondence, and have double checked spam filters. Is there someone I can call or email ?


    Thoughts are greatly appreciated.

  • Hi Marcel,


    I'm facing some issue while trying to connect to my local Conquest server remotely. It's throwing error that association is not established and throws socket error:


    java.net.SocketTimeoutException: connect timed out

    at java.net.PlainSocketImpl.socketConnect(Native Method)[:1.8.0_65]

    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)[:1.8.0_65]

    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)[:1.8.0_65]

    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)[:1.8.0_65]

    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)[:1.8.0_65]

    at java.net.Socket.connect(Socket.java:589)[:1.8.0_65]




    We have an application running on Linux machine and the ConQuest is running on a Linux machine. While I can send data from my conquest system to the linux system, it's not allowing the other way around and throwing socket error. I've checked the Windows firewall and it allows all the ports for conquest. I created a rule to allow port 5678 specifically to all application.


    Please let me know your thoughts.

  • Hi

    Great software and excellent work.

    My question is Does Conquest Dicom support ultrasound videos.

    How to receive them in conquest as when i send videos to the conquest from machine and error is generated.


    regards

    Das

    • Hi,


      Conquest does not support MPEG bacause it has no codec. So unfortunately no. Uncompressed videos can be stored.


      Marcel

  • Bonjour Marcel

    Merci Pour vos souhaits de bienvenue

    Pourriez vous me dire si vous pourriez m'aider et me dire comment supprimer un Problème quand j'ouvre la fenêtre pour l'envoie de mes courriers je me retrouve avec une phrase pré-écrite du genre le plus grand centre commercial

    si vous avez une explication sur ce phénomène et comment supprimer ce genre de pré-Ecriture non désiré merci de résoudre votre problème

    Cordialement

    Pierre VIALLE

  • Hello Marcel,

    Can you help me? I'm trying to use auto-routing in IQ-View, but the autorouting.ini file is not being generated. Can you pass me the contents of it, so you can manually create the file? Thank you

  • Hi Marcel


    Firstly I want to say that thanks for ConquestDicomServer such a great software. I already deploy ConquestDicomServer as PACS DICOM Server in my organization and It is running fine,Here more then 50 modality machines are connected with it and working fine. Now I want to configured ConquestDicomServer as Modality Worklist Server . Here firstly I working as testing on my person Laptop as PACS Server , Here I installed CONQUESTDICOM Server , I am using here mysql, here it is running fine.I entered 1/2 records in database in worklist table manually. I am also using a Toshiba Echo Machine for testing here, I have also configure both side all data HostName,IP,Port and both side DICOM ECHO is successfully. I have got some help from this forum as your discussion with Mr.Hammad , but I can't successfully here. On echo machine side no data fetched from ConquestDicom Server.

    When I click the GetWorkList ,some response is shown on server status screen, but no any record are received in machine side.. Kindly Guide me.. where I am going wrong...


    here is my worklist table details.


    { 0x0008, 0x0050, "AccessionNumber", 16, SQL_C_CHAR, DT_STR, "OBR.3" },

    { 0x0010, 0x0020, "PatientID", 64, SQL_C_CHAR, DT_STR, "PID.4" },

    { 0x0010, 0x0010, "PatientName", 64, SQL_C_CHAR, DT_STR, "PID.5" },

    { 0x0010, 0x0030, "PatientBirthDate", 8, SQL_C_DATE, DT_DATE, "PID.7" },

    { 0x0010, 0x0040, "PatientSex", 16, SQL_C_CHAR, DT_STR, "PID.8" },

    { 0x0008, 0x0020, "StudyDate", 8, SQL_C_DATE, DT_DATE,"PID.8.DATE" },

    { 0x0008, 0x0030, "StudyTime", 16, SQL_C_CHAR, DT_TIME,"PID.8.TIME" },


    { 0x0010, 0x2000, "MedicalAlerts", 64, SQL_C_CHAR, DT_STR, "---" },

    { 0x0010, 0x2110, "ContrastAllergies", 64, SQL_C_CHAR, DT_STR, "---" },

    { 0x0020, 0x000d, "StudyInstanceUID", 64, SQL_C_CHAR, DT_UI, "---" },

    { 0x0032, 0x1032, "ReqPhysician", 64, SQL_C_CHAR, DT_STR, "OBR.16" },

    { 0x0032, 0x1060, "ReqProcDescription", 64, SQL_C_CHAR, DT_STR, "OBR.4.1" },


    { 0x0040, 0x0100, "--------", 0, SQL_C_CHAR, DT_STARTSEQUENCE, "---" },

    { 0x0008, 0x0060, "Modality", 16, SQL_C_CHAR, DT_STR, "OBR.21" },

    { 0x0032, 0x1070, "ReqContrastAgent", 64, SQL_C_CHAR, DT_STR, "---" },

    { 0x0040, 0x0001, "ScheduledAE", 16, SQL_C_CHAR, DT_STR, "---" },

    { 0x0040, 0x0002, "StartDate", 8, SQL_C_DATE, DT_DATE, "OBR.7.DATE" },

    { 0x0040, 0x0003, "StartTime", 16, SQL_C_CHAR, DT_TIME, "OBR.7.TIME" },

    { 0x0040, 0x0006, "PerfPhysician", 64, SQL_C_CHAR, DT_STR, "---" },

    { 0x0040, 0x0007, "SchedPSDescription", 64, SQL_C_CHAR, DT_STR, "---" },

    { 0x0040, 0x0009, "SchedPSID", 16, SQL_C_CHAR, DT_STR, "OBR.4" },

    { 0x0040, 0x0010, "SchedStationName", 16, SQL_C_CHAR, DT_STR, "OBR.24" },

    { 0x0040, 0x0011, "SchedPSLocation", 16, SQL_C_CHAR, DT_STR, "---" },

    { 0x0040, 0x0012, "PreMedication", 64, SQL_C_CHAR, DT_STR, "---" },

    { 0x0040, 0x0400, "SchedPSComments", 64, SQL_C_CHAR, DT_STR, "---" },

    { 0x0040, 0x0100, "---------", 0, SQL_C_CHAR, DT_ENDSEQUENCE, "---" },


    { 0x0040, 0x1001, "ReqProcID", 16, SQL_C_CHAR, DT_STR, "OBR.4.0" },

    { 0x0040, 0x1003, "ReqProcPriority", 16, SQL_C_CHAR, DT_STR, "OBR.27 }



    Regarsd ;

    Ghulam Mustafa

    • Hi Ghulam,


      The machine typically expects certain elements to be filled, such as StudyIntanceUID, ScheduledAE and StartDate for the elements to show up. You can get a clue of what it wants by looking at a debug log of the worklist query or ask help from your vendor.


      Marcel

    • Hi Dear Marcle


      Hopefully you will be fine, thanks for reply, as your replied I had contacted with my vendor for getting help regarding ModalityWorklist deploying from echo machine side, He come and checked all things from echo machine side, and He said that all things are fine in machine configuration setting , no issue in machine side.


      Here I am described some detail for you that, I had not installed any HL7 software in my PC's where ConquestDicomServer are installed, Is there any requirement of HL7 software for ModalityWorklist functionality with ConquestDicomServer .


      Here I want to attached some screenshot , but how can i atteched snapsshotes here i can not see any icon/button for adding/attechemnet.

    • Hi Marcel


      Here I want to share some details with you that.


      here is echo machine registration at ConquestDicomServer Side


      CONQUESTSRV1 127.0.0.1 5678 un

      NICVD-KHI-11 10.0.4.42 11660 un (Echo Machine info at dicomserver side)




      I had show All column in database of dicomworklist table.


      I had entered some data in worklist table as manually here are details.


      AccessionN = ECHO/2018/026130

      PatientID = 2018/277286

      PatientNam = MR FALAK SHER

      PatientSex = M

      StudyDate = 20180118

      ReqPhysici = DR HABIBA

      Modality = US


      Then I also run command prompt for StudyInstanceUID at the running time of ConquestDicomServer , here are output command Prompt


      E:\PACS_TEST>dgate64 --genuid:

      1.2.826.0.1.3680043.2.135.737075.48079395.6.1547971702.218.0

      E:\PACS_TEST>


      and here is output response on the ConquestDicomServer Server Status sceen

      01/18/2019 12:44:39 PM [PACSTEST2] Monitoring for files in: e:\pacs_test\data\incoming\

      01/18/2019 12:44:39 PM [PACSTEST2] DGATE (1.4.19, build Thu Feb 9 11:28:20 2017, bits 64) is running as threaded server

      01/18/2019 12:44:39 PM [PACSTEST2] Database type: native MySQL connection

      01/18/2019 12:44:39 PM [PACSTEST2] User interface test: local server is running!

      01/18/2019 12:45:29 PM [PACSTEST2] Re-reading acrnema.map from GUI

      01/18/2019 12:47:17 PM [PACSTEST2] Server command sent using DGATE -- option

      01/18/2019 12:47:25 PM [PACSTEST2] Re-reading acrnema.map from GUI

      01/18/2019 12:57:43 PM [PACSTEST2]

      01/18/2019 12:57:43 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 12:57:43 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 12:57:43 PM [PACSTEST2] UPACS THREAD 49: ENDED AT: Fri Jan 18 12:57:43 2019

      01/18/2019 12:57:43 PM [PACSTEST2] UPACS THREAD 49: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 12:58:05 PM [PACSTEST2] Re-reading acrnema.map from GUI

      01/18/2019 12:59:46 PM [PACSTEST2]

      01/18/2019 12:59:46 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 12:59:46 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 12:59:46 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 12:59:46 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 12:59:46 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 12:59:46 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 12:59:46 PM [PACSTEST2] UPACS THREAD 101: ENDED AT: Fri Jan 18 12:59:46 2019

      01/18/2019 12:59:46 PM [PACSTEST2] UPACS THREAD 101: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:00:55 PM [PACSTEST2]

      01/18/2019 1:00:55 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:00:55 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:00:55 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:00:55 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.1.1" 1

      01/18/2019 1:00:55 PM [PACSTEST2] C-Echo

      01/18/2019 1:00:55 PM [PACSTEST2] UPACS THREAD 103: ENDED AT: Fri Jan 18 13:00:55 2019

      01/18/2019 1:00:55 PM [PACSTEST2] UPACS THREAD 103: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:03:39 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:03:39 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:03:39 PM [PACSTEST2]

      01/18/2019 1:03:39 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:03:39 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:03:39 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:03:39 PM [PACSTEST2] UPACS THREAD 107: ENDED AT: Fri Jan 18 13:03:39 2019

      01/18/2019 1:03:39 PM [PACSTEST2] UPACS THREAD 107: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:04:38 PM [PACSTEST2]

      01/18/2019 1:04:38 PM [PACSTEST2] UPACS THREAD 109: STARTED AT: Fri Jan 18 13:04:38 2019

      01/18/2019 1:04:38 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:04:38 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:04:38 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:04:38 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:04:38 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:04:38 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:04:38 PM [PACSTEST2] UPACS THREAD 109: ENDED AT: Fri Jan 18 13:04:38 2019

      01/18/2019 1:04:38 PM [PACSTEST2] UPACS THREAD 109: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:05:59 PM [PACSTEST2]

      01/18/2019 1:05:59 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:05:59 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:05:59 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:05:59 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:05:59 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:05:59 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:05:59 PM [PACSTEST2] UPACS THREAD 111: ENDED AT: Fri Jan 18 13:05:59 2019

      01/18/2019 1:05:59 PM [PACSTEST2] UPACS THREAD 111: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:06:09 PM [PACSTEST2]

      01/18/2019 1:06:09 PM [PACSTEST2] UPACS THREAD 112: STARTED AT: Fri Jan 18 13:06:09 2019

      01/18/2019 1:06:09 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:06:09 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:06:09 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:06:09 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:06:09 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:06:09 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:06:09 PM [PACSTEST2] UPACS THREAD 112: ENDED AT: Fri Jan 18 13:06:09 2019

      01/18/2019 1:06:09 PM [PACSTEST2] UPACS THREAD 112: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:07:22 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:07:22 PM [PACSTEST2]

      01/18/2019 1:07:22 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:07:22 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:07:22 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:07:22 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:07:22 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:07:22 PM [PACSTEST2] UPACS THREAD 115: ENDED AT: Fri Jan 18 13:07:22 2019

      01/18/2019 1:07:22 PM [PACSTEST2] UPACS THREAD 115: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:07:47 PM [PACSTEST2]

      01/18/2019 1:07:47 PM [PACSTEST2] UPACS THREAD 116: STARTED AT: Fri Jan 18 13:07:46 2019

      01/18/2019 1:07:47 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:07:47 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:07:47 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:07:47 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:07:47 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:07:47 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:07:47 PM [PACSTEST2] UPACS THREAD 116: ENDED AT: Fri Jan 18 13:07:47 2019

      01/18/2019 1:07:47 PM [PACSTEST2] UPACS THREAD 116: TOTAL RUNNING TIME: 1 SECONDS

      01/18/2019 1:10:09 PM [PACSTEST2]

      01/18/2019 1:10:09 PM [PACSTEST2] UPACS THREAD 119: ENDED AT: Fri Jan 18 13:10:09 2019

      01/18/2019 1:10:09 PM [PACSTEST2] UPACS THREAD 119: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:10:16 PM [PACSTEST2]

      01/18/2019 1:10:16 PM [PACSTEST2] UPACS THREAD 120: STARTED AT: Fri Jan 18 13:10:16 2019

      01/18/2019 1:10:16 PM [PACSTEST2] *** connection terminated

      01/18/2019 1:10:16 PM [PACSTEST2] UPACS THREAD 120: ENDED AT: Fri Jan 18 13:10:16 2019

      01/18/2019 1:10:16 PM [PACSTEST2] UPACS THREAD 120: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:12:20 PM [PACSTEST2]

      01/18/2019 1:12:20 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:12:20 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:12:20 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:12:20 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:12:20 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:12:20 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:12:20 PM [PACSTEST2] UPACS THREAD 124: ENDED AT: Fri Jan 18 13:12:20 2019

      01/18/2019 1:12:20 PM [PACSTEST2] UPACS THREAD 124: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:12:25 PM [PACSTEST2]

      01/18/2019 1:12:25 PM [PACSTEST2] UPACS THREAD 125: STARTED AT: Fri Jan 18 13:12:25 2019

      01/18/2019 1:12:25 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:12:25 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:12:25 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:12:25 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:12:25 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:12:25 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:12:25 PM [PACSTEST2] UPACS THREAD 125: ENDED AT: Fri Jan 18 13:12:25 2019

      01/18/2019 1:12:25 PM [PACSTEST2] UPACS THREAD 125: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:12:49 PM [PACSTEST2]

      01/18/2019 1:12:49 PM [PACSTEST2] UPACS THREAD 126: STARTED AT: Fri Jan 18 13:12:49 2019

      01/18/2019 1:12:49 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:12:49 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:12:49 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:12:49 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:12:49 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:12:49 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:12:49 PM [PACSTEST2] UPACS THREAD 126: ENDED AT: Fri Jan 18 13:12:49 2019

      01/18/2019 1:12:49 PM [PACSTEST2] UPACS THREAD 126: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:23:56 PM [PACSTEST2] UPACS THREAD 138: STARTED AT: Fri Jan 18 13:23:56 2019

      01/18/2019 1:23:56 PM [PACSTEST2]

      01/18/2019 1:23:56 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:23:56 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:23:56 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:23:56 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:23:56 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:23:56 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:23:56 PM [PACSTEST2] UPACS THREAD 138: ENDED AT: Fri Jan 18 13:23:56 2019

      01/18/2019 1:23:56 PM [PACSTEST2] UPACS THREAD 138: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:31:06 PM [PACSTEST2]

      01/18/2019 1:31:06 PM [PACSTEST2] UPACS THREAD 146: STARTED AT: Fri Jan 18 13:31:06 2019

      01/18/2019 1:31:06 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:31:06 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:31:06 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:31:06 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:31:06 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:31:06 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:31:06 PM [PACSTEST2] UPACS THREAD 146: ENDED AT: Fri Jan 18 13:31:06 2019

      01/18/2019 1:31:06 PM [PACSTEST2] UPACS THREAD 146: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:31:51 PM [PACSTEST2]

      01/18/2019 1:31:51 PM [PACSTEST2] UPACS THREAD 148: STARTED AT: Fri Jan 18 13:31:51 2019

      01/18/2019 1:31:51 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:31:51 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:31:51 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:31:51 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:31:51 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:31:51 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:31:51 PM [PACSTEST2] UPACS THREAD 148: ENDED AT: Fri Jan 18 13:31:51 2019

      01/18/2019 1:31:51 PM [PACSTEST2] UPACS THREAD 148: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:32:33 PM [PACSTEST2]

      01/18/2019 1:32:33 PM [PACSTEST2] UPACS THREAD 150: STARTED AT: Fri Jan 18 13:32:33 2019

      01/18/2019 1:32:33 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:32:33 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:32:33 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:32:33 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:32:33 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:32:33 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:32:33 PM [PACSTEST2] UPACS THREAD 150: ENDED AT: Fri Jan 18 13:32:33 2019

      01/18/2019 1:32:33 PM [PACSTEST2] UPACS THREAD 150: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:33:08 PM [PACSTEST2]

      01/18/2019 1:33:08 PM [PACSTEST2] UPACS THREAD 151: STARTED AT: Fri Jan 18 13:33:08 2019

      01/18/2019 1:33:08 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:33:08 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:33:08 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:33:08 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:33:08 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:33:08 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:33:08 PM [PACSTEST2] UPACS THREAD 151: ENDED AT: Fri Jan 18 13:33:08 2019

      01/18/2019 1:33:08 PM [PACSTEST2] UPACS THREAD 151: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:33:26 PM [PACSTEST2]

      01/18/2019 1:33:26 PM [PACSTEST2] UPACS THREAD 153: STARTED AT: Fri Jan 18 13:33:26 2019

      01/18/2019 1:33:26 PM [PACSTEST2] Calling Application Title : "APLIOI600 "

      01/18/2019 1:33:26 PM [PACSTEST2] Called Application Title : "PACSTEST "

      01/18/2019 1:33:26 PM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/18/2019 1:33:26 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:33:26 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:33:26 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:33:26 PM [PACSTEST2] UPACS THREAD 153: ENDED AT: Fri Jan 18 13:33:26 2019

      01/18/2019 1:33:26 PM [PACSTEST2] UPACS THREAD 153: TOTAL RUNNING TIME: 0 SECONDS

      01/18/2019 1:35:31 PM [PACSTEST2]

      01/18/2019 1:35:31 PM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/18/2019 1:35:31 PM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/18/2019 1:35:31 PM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/18/2019 1:35:31 PM [PACSTEST2] UPACS THREAD 156: ENDED AT: Fri Jan 18 13:35:31 2019

      01/18/2019 1:35:31 PM [PACSTEST2] UPACS THREAD 156: TOTAL RUNNING TIME: 0 SECONDS


      above are response of ConquestDicomServer Server Status sceen at time when from echo side I clicking "GetWorkList" button and fetching data from worlist table with patientID/AccessionN field.


      Kindly guide me where I am going wrong or either any thing are missing be me in serverside.

    • Hi,


      if you increase the debug level (arrows next to debug log button), you can see what the actual query is that the modality sends, apparently it requests a particular field that is not in your data, like the 'scheduledAE'. In any case conquest is returning returning 0 entries so the query does not match your data.


      Good luck


      Marcel

    • Hi Dear Marcle


      I am still not success in deploying ModalityWorklist.


      Here is data in worklist Table .


      AccessionN='ECHO/2018/026130',

      PatientID ='2018/277286',

      PatientNam ='MR FALAK SHER',

      PatientSex ='M',

      StudyDate ='20190118',

      StudyInsta ='1.2.826.0.1.3680043.2.135.737075.48079395.6.1548048393.31.0',

      //////(Optional, I tried with and Without this column data)

      ReqPhysici ='DR HABIBA',

      Modality ='US',

      ScheduledA ='KHI-ECHO-11' // this is Echo(Modality)machine AE TITLE

      ReqProcID ='64234' //// (Optional ,I tried with and Without this column data)



      //////////////////////////// This is Known DICOM provvider Page on ConquestDicomServer


      PACSTEST2 127.0.0.1 5679 jk

      KHI-ECHO-11 10.0.4.42 104 jk // also tried 'un'



      //////////////////////



      Still No any record fetched by echo modality machine by ModalityWorkList. still showed same output

      response on ConquestDicomServer Server Status.


      ConquestDicomServer Server Status.

      01/21/2019 11:50:44 AM [PACSTEST2] UPACS THREAD 131: STARTED AT: Mon Jan 21 11:50:44 2019

      01/21/2019 11:50:44 AM [PACSTEST2] Calling Application Title : "KHI-ECHO-11 "

      01/21/2019 11:50:44 AM [PACSTEST2] Called Application Title : "PACSTEST2 "

      01/21/2019 11:50:44 AM [PACSTEST2] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 64234

      01/21/2019 11:50:44 AM [PACSTEST2] Presentation Context 0 "1.2.840.10008.5.1.4.31" 1

      01/21/2019 11:50:44 AM [PACSTEST2] (ModalityWorkListQuery) search level:

      01/21/2019 11:50:44 AM [PACSTEST2] C-Find (Modality Work List) located 0 records

      01/21/2019 11:50:45 AM [PACSTEST2] UPACS THREAD 131: ENDED AT: Mon Jan 21 11:50:44 2019

      01/21/2019 11:50:45 AM [PACSTEST2] UPACS THREAD 131: TOTAL RUNNING TIME: 0 SECONDS


      ..need your guidance

  • Hello,

    How do I post to the forum. My account is already active and verified but I do not think the option to post or comment on the forum.


    I have a problem with the routing function and would like to post to the forum for help.


    I have 1 local conquest that I intend to configure to send all the exams to another remote conquest,

    I believe I have set up the dicom.ini and acrnema correctly but the routing does not occur


    #DICOM.INI LOCAL

    QueueSize = 1000

    ExportConverters = 1

    ExportConverter0 = forward to CONQUESTMASTER


    #ACRNEMA LOCAL

    CONQUESTSRV1 127.0.0.1 5678 un


    V* * 1234 un

    W* * 666 un

    S* * 5678 un

    * 127.0.0.1 5678 un

    CONQUESTMASTER 143.137.188.2 56789 un



    #LOG

    13/06/2018 14:53:14 [OWNIMAGE] UPACS THREAD 153: STARTED AT: Wed Jun 13 14:53:14 2018

    13/06/2018 14:53:14 [OWNIMAGE] Calling Application Title : "CONQUESTSRV1 "

    13/06/2018 14:53:14 [OWNIMAGE] Called Application Title : "CONQUESTMASTER "

    13/06/2018 14:53:14 [OWNIMAGE] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 32768

    13/06/2018 14:53:14 [OWNIMAGE] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.4" 1

    13/06/2018 14:53:14 [OWNIMAGE] Presentation Context 1 "1.2.840.10008.1.1" 1

    13/06/2018 14:53:14 [OWNIMAGE] Presentation Context 2 "1.2.840.10008.5.1.4.1.1.1" 1

    13/06/2018 14:53:14 [OWNIMAGE] Rewritten file: c:\ownimage\data\storage\20180613\PAULO_ROBSON_SOUZA_RODRIGUES\5\1.2.156.14702.3.3506.66049049054.20180613.8231659.21.

    13/06/2018 14:53:14 [OWNIMAGE] ExportConverter0.0: forward c:\ownimage\data\storage\20180613\PAULO_ROBSON_SOUZA_RODRIGUES\12\1.2.156.14702.3.3506.66049049054.20180613.8045225.8. to CONQUESTMASTER


    Nothing happens on the remote server.

    • Hi,


      is 56789


      the correct port number for CONQUESTMASTER?


      Marcel

    • The problem was the order in ACRNEMA


      Change

      CONQUESTSRV1 127.0.0.1 5678 un


      V* * 1234 un

      W* * 666 un

      S* * 5678 un

      * 127.0.0.1 5678 un

      CONQUESTMASTER 143.137.188.2 56789 un


      to


      CONQUESTSRV1 127.0.0.1 5678 un

      CONQUESTMASTER 143.137.188.2 56789 un


      V* * 1234 un

      W* * 666 un

      S* * 5678 un

      * 127.0.0.1 5678 un


      Work



      I am trying to write a tag in dicom but it is not working


      would this line be correct?




      ExportConverter0 = set 2100,0140 to "saojose"; forward to CONQUESTMASTER

    • Export converters work on the stored images; you cannot change them this way. Try this (the manual does list it):


      ExportConverter0 = forward to CONQUESTMASTER script set 2100,0140 to "saojose"


      The script command runs on the data as it is sent.


      Marcel

    • Is there any place where I can check what's queued to be routed?


      Thank you for your attention.

    • Hi,


      Queuing is logged; there can be a file like ExportFailure but it is binary,


      regards,


      Marcel

  • In server manual, "The Conquest DICOM server has functionality to route incoming DICOM images to other servers (DICOM router) and to forward incoming query/move requests to other servers (DICOM gateway or virtual server)."


    Could you please offer an example for scenario "to forward incoming query/move requests to other servers"? I am thinking a case forward Modality Worklist query to another DICOM server.


    Thanks in advance.

  • Hi


    Log from DICOM server

    [TERRASRV] UPACS THREAD 5: STARTED AT: Tue Feb 20 16:34:31 2018

    [TERRASRV] Calling Application Title : "findSCU "

    [TERRASRV] Called Application Title : "findSCU "

    [TERRASRV] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 65536

    [TERRASRV] Presentation Context 0 "1.2.840.10008.1.20.1" 0

    [TERRASRV] Transfer Syntax 0 "1.2.840.10008.1.2" 1

    [TERRASRV] Transfer Syntax 1 "1.2.840.10008.1.2.1" 1

    [TERRASRV] *** Association rejected: you may need to add the listed presentation context as sop to dgatesop.lst

    [TERRASRV] UPACS THREAD 5: ENDED AT: Tue Feb 20 16:34:32 2018

    [TERRASRV] UPACS THREAD 5: TOTAL RUNNING TIME: 1 SECONDS



    Any possibility to add support for this?

    • Yes,


      just edit dgatesop.lst and add 1.2.840.10008.1.20.1


      Marcel

    • Sorry,


      this is storage commitment, which must be coded - it is not in there. Tell your pacs to not use storage commitment with Conquest.


      Marcel

    • simens IRM worklist problem i can't guess where the problem please help




      07/12/2019 08:51:01 [CLINISYSWML] Queried item 0040 2010 is not in the database

      07/12/2019 08:51:01 [CLINISYSWML] Queried item 0040 2016 is not in the database

      07/12/2019 08:51:01 [CLINISYSWML] Queried item 0040 2017 is not in the database

      07/12/2019 08:51:01 [CLINISYSWML] Queried item 0040 2400 is not in the database

      07/12/2019 08:51:01 [CLINISYSWML] Queried item 0040 3001 is not in the database

      07/12/2019 08:51:01 [CLINISYSWML] Issue Query on Columns: DICOMWorkList.AccessionN, DICOMWorkList.PatientNam, DICOMWorkList.PatientID, DICOMWorkList.PatientBir, DICOMWorkList.PatientSex, DICOMWorkList.MedicalAle, DICOMWorkList.ContrastAl, DICOMWorkList.StudyInsta, DICOMWorkList.ReqPhysici, DICOMWorkList.ReqProcDes, DICOMWorkList.Modality, DICOMWorkList.ReqContras, DICOMWorkList.ScheduledA, DICOMWorkList.StartDate, DICOMWorkList.StartTime, DICOMWorkList.PerfPhysic, DICOMWorkList.SchedPSDes, DICOMWorkList.SchedPSID, DICOMWorkList.SchedStati, DICOMWorkList.SchedPSLoc, DICOMWorkList.PreMedicat, DICOMWorkList.SchedPSCom, DICOMWorkList.ReqProcID, DICOMWorkList.ReqProcPri

      07/12/2019 08:51:01 [CLINISYSWML] Values: DICOMWorkList.Modality = 'MR' and DICOMWorkList.ScheduledA = 'AWP41614' and DICOMWorkList.StartDate = '20191207' and DICOMWorkList.StartTime >= '000000' and DICOMWorkList.StartTime <= '235959'

      07/12/2019 08:51:01 [CLINISYSWML] Tables: DICOMWorkList

      07/12/2019 08:51:01 [CLINISYSWML] Sorting (DICOMWorkList.PatientNam) DoSort := 1

      07/12/2019 08:51:01 [CLINISYSWML] Query Distinct Tables: DICOMWorkList

      07/12/2019 08:51:01 [CLINISYSWML] Columns : DICOMWorkList.AccessionN, DICOMWorkList.PatientNam, DICOMWorkList.PatientID, DICOMWorkList.PatientBir, DICOMWorkList.PatientSex, DICOMWorkList.MedicalAle, DICOMWorkList.ContrastAl, DICOMWorkList.StudyInsta, DICOMWorkList.ReqPhysici, DICOMWorkList.ReqProcDes, DICOMWorkList.Modality, DICOMWorkList.ReqContras, DICOMWorkList.ScheduledA, DICOMWorkList.StartDate, DICOMWorkList.StartTime, DICOMWorkList.PerfPhysic, DICOMWorkList.SchedPSDes, DICOMWorkList.SchedPSID, DICOMWorkList.SchedStati, DICOMWorkList.SchedPSLoc, DICOMWorkList.PreMedicat, DICOMWorkList.SchedPSCom, DICOMWorkList.ReqProcID, DICOMWorkList.ReqProcPri

      07/12/2019 08:51:01 [CLINISYSWML] Where : DICOMWorkList.Modality = 'MR' and DICOMWorkList.ScheduledA = 'AWP41614' and DICOMWorkList.StartDate = '20191207' and DICOMWorkList.StartTime >= '000000' and DICOMWorkList.StartTime <= '235959'

      07/12/2019 08:51:01 [CLINISYSWML] Order : DICOMWorkList.PatientNam

      07/12/2019 08:51:01 [CLINISYSWML] Records = 0

      07/12/2019 08:51:01 [CLINISYSWML] C-Find (Modality Work List) located 0 records

      07/12/2019 08:51:01 [CLINISYSWML] UPACS THREAD 1644: ENDED AT: Sat Dec 07 08:51:00 2019

      07/12/2019 08:51:01 [CLINISYSWML] UPACS THREAD 1644: TOTAL RUNNING TIME: 1 SECONDS

      07/12/2019 08:51:08 [CLINISYSWML] Connected by address: 0100007f

      07/12/2019 08:51:08 [CLINISYSWML] Testing transfer: '1.2.840.10008.1.2' against list #0 = '1.2.840.10008.1.2'

      07/12/2019 08:51:08 [CLINISYSWML] 0000,0002 18 UI AffectedSOPClassUID "1.2.840.10008.1.1"

      07/12/2019 08:51:08 [CLINISYSWML] 0000,0100 2 US CommandField 48

      07/12/2019 08:51:08 [CLINISYSWML] 0000,0110 2 US MessageID 7

      07/12/2019 08:51:08 [CLINISYSWML] 0000,0800 2 US DataSetType 257

      07/12/2019 08:51:08 [CLINISYSWML] 0002,0010 17 UI TransferSyntaxUID "1.2.840.10008.1.2"

      07/12/2019 08:51:08 [CLINISYSWML] 9999,0400 6 LO ConquestConsoleComma "silent"

    • Well this query:


      Where : DICOMWorkList.Modality = 'MR' and DICOMWorkList.ScheduledA = 'AWP41614' and DICOMWorkList.StartDate = '20191207' and DICOMWorkList.StartTime >= '000000' and DICOMWorkList.StartTime <= '235959'


      returns 0 items, so this must be incomplete in the worklist database.

      Marcel