Posts by hammad

    Hi


    How can i configure conquest to delete Patient Data or Patient Study that is :-


    1. Not accessed for last 30 days
    2. Delete Studies or Patient that are 15 days old.


    I want this to be done automatically by conquest no human interaction. Please guide.


    --HM

    I am using it in production environment with Patient data of 40TB. But some of the doctors raised questions. As, the mentioned URL was fwded to me by some of the doctors thats why i ping you.


    --HM

    Hi


    But i want to add that save to doesn't work for me but copy to with %f did....


    Can you tell me the short code for following as i cannot find them in the manual


    1. Patient Name :
    2. Concat Patient name and Patient ID using Import Converter for making directory structure Patient Name-Patient ID (Tom-123)



    --HM

    I tried to use the following command but it doesn't work.


    1. System mkdir E:\backup\ This command doesn't work for me on windows.
    ImportConvertor0 = system mkdir 'E:\backup\'


    2. I want to create folders in the backup in the same way it is created on the PRODUCTION. So that both PRODUCTION and BACKUP are sync.


    ImportConverter0 = copy %f to E:\backup\%studydate\%id-(%name)\%VSeriesDescription\%series%counter.dcm


    This command doesn't work instead it gives me error.
    HPACS] Importconverter0.0 executes: copy E:\images\10801\1.2.392.200036.9125.3.25153170193106.64743043577.6206085_1001_001001_14391859480000.dcm to E:\studies\10801d\10801
    [HPACS] *** Exportconverter0.0: Failed to copy E:\images\10801\1.2.392.200036.9125.3.25153170193106.64743043577.6206085_1001_001001_14391859480000.dcm to E:\studies\10801d\10801

    Hi

    Following Modalities are installed/configured in our hospital.


    1. CT Scan : 4
    2. MRI : 3
    3. CR : 8
    4. OPG : 2
    5. USG : 15
    6. Floro : 2


    I am populating worklist table with hl7 messages. But i want to restrict the worklist entries on the based of Modality AET. For example, If CT Scan A (AET: CTA) comes to conquest for worklist then only entries that are booked for CTA should be visible to CT Scan A not of other machines.


    On searching the internet i found an old toolkit dcmtk that uses DICOM modality Worklist service Class Provider and the worklist files created by the dcmtk toolkit are modality based. But i cannot load these wl files in conquest.


    Please guide me what changes should i made in the current tables or i should use the other approach.


    --Hammad

    My dicom.ini file is pasted below:-




    # This file contains configuration information for the DICOM server
    # Do not edit unless you know what you are doing


    [sscscp]
    MicroPACS = sscscp
    Edition = Personal


    # Network configuration: server name and TCP/IP port#
    MyACRNema = HPACS
    TCPPort = 104


    # Reference to other files: known dicom servers; database layout; sops
    ACRNemaMap = acrnema.map
    kFactorFile = dicom.sql
    SOPClassList = dgatesop.lst


    # Host, database, username and password for MySql database
    SQLHost = localhost
    SQLServer = HPACS
    Username = root
    Password = 1111
    MySql = 1
    DoubleBackSlashToDB = 1
    UseEscapeStringConstants = 0


    # Configure database
    TruncateFieldNames = 10
    MaxFieldLength = 254
    MaxFileNameLength = 255
    FixPhilips = 0
    FixKodak = 0
    KeepAlive = 0
    LargeFileSizeKB = 100000
    PrintSquareLandscape = 0
    UseKpacsDecompression = 1
    ZipTime = 05:
    UIDPrefix = 1.2.826.0.1.3680043.2.135.735812.82623288
    EnableReadAheadThread = 1
    PatientQuerySortOrder =
    StudyQuerySortOrder =
    SeriesQuerySortOrder =
    ImageQuerySortOrder =
    EnableComputedFields = 1
    IndexDBF = 1
    PackDBF = 0
    LongQueryDBF = 1000
    TCPIPTimeOut = 300
    FailHoldOff = 60
    RetryDelay = 100
    RetryForwardFailed = 0
    ImportExportDragAndDrop = 0
    QueueSize = 128
    WorkListMode = 0
    WorkListReturnsISO_IR_100 = 1
    DebugLevel = 0
    Prefetcher = 0
    LRUSort =
    AllowTruncate =
    DecompressNon16BitsJpeg = 1
    UseBuiltInJPEG = 1
    LossyQuality = 95
    IgnoreOutOfMemoryErrors = 0
    NoDICOMCheck = 0
    PadAEWithZeros = 0
    AllowEmptyPatientID = 0
    FileNameSyntax = 4


    # Configuration of compression for incoming images and archival
    DroppedFileCompression = un
    IncomingCompression = un
    ArchiveCompression = as


    # Names of the database tables
    PatientTableName = DICOMPatients
    StudyTableName = DICOMStudies
    SeriesTableName = DICOMSeries
    ImageTableName = DICOMImages
    WorkListTableName = DICOMWorkList
    DMarkTableName = DICOMAccessUpdates
    RegisteredMOPDeviceTable = RegisteredMOPIDs
    UIDToMOPIDTable = UIDToMOPID
    UIDToCDRIDTable = UIDToCDRID


    # Banner and host for debug information
    PACSName = HPACS
    OperatorConsole = 127.0.0.1


    # Configure email of error messages
    MailHost =
    MailPort = smtp
    MailSignon =
    MailFromName =
    MailRcptName1 =
    MailCollectTime = 1
    MailWaitTime = 10


    # Configuration of disk(s) to store images
    MAGDeviceThreshhold = 0
    MAGDeviceFullThreshHold = 30
    IgnoreMAGDeviceThreshold = 0
    MAGDevices = 1
    MAGDevice0 = E:\images\
    NightlyCleanThreshhold = 0

    Hi Marcel


    I tried to install and configure the latest release to give it a test run. Everything went fine during the installation as well as configuration part. But on BROWSE PATIENT Tab i get following error [Microsoft][OBDC Driver Manager] Data Source Name not found and no default driver specified. Error Screenshot attached


    I am using Microsoft Windows 7 and mysql as Database. When i query the database i can see the records of patient available but they are not view able on screen using application.


    Firstly if possible , please do provide the updated User Manual as the Manuals under the Manual folder are old Manual and there is lot of difference in the current release and previous one both in terms of GUI and definitely functionality.


    Secondly, please do provide the fixes and features that are in cooperated in this release.


    --HM

    Files

    • Error.png

      (40.5 kB, downloaded 1,494 times, last: )

    Nicolas some strange happens. Server was abnormally shutdown due to power. On resuming the updated version of Weasis was up and running. :D
    Still confused why this happened :idea: As, no change in configuration or anything was made.



    Thanks for your patience and support. :D

    I updated my version of Weasis from 2.0.3 to 2.0.4. After the update Weasis stop working and i cannot view images. No changes in the configuration was mdae. Oted.nly weasis.war file was replaced and Tomcat server was restarted.


    On java console i got following log



    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    30.06.2015 06:35:54.831 *ERROR* [pool-12-thread-2]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    30.06.2015 06:35:54.831 *ERROR* [pool-12-thread-4]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with proxy=DIRECT
    network: Connecting http://127.0.0.1:80/ with proxy=DIRECT
    network: Connecting http://127.0.0.1:80/ with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    30.06.2015 06:35:54.835 *ERROR* [pool-12-thread-3]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with proxy=DIRECT
    network: Connecting http://127.0.0.1:80/ with proxy=DIRECT
    30.06.2015 06:35:54.837 *ERROR* [pool-12-thread-1]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    30.06.2015 06:35:54.838 *ERROR* [pool-12-thread-4]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    network: Connecting http://127.0.0.1:80/ with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with proxy=DIRECT
    30.06.2015 06:35:54.839 *ERROR* [pool-12-thread-2]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    network: Connecting http://127.0.0.1:80/ with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with proxy=DIRECT
    network: Connecting http://127.0.0.1:80/ with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    30.06.2015 06:35:54.844 *ERROR* [pool-12-thread-1]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    30.06.2015 06:35:54.845 *ERROR* [pool-12-thread-3]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with proxy=DIRECT
    30.06.2015 06:35:54.845 *ERROR* [pool-12-thread-4]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    network: Connecting http://127.0.0.1:80/ with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with proxy=DIRECT
    network: Connecting http://127.0.0.1:80/ with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with proxy=DIRECT
    network: Connecting http://127.0.0.1:80/ with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    30.06.2015 06:35:54.848 *ERROR* [pool-12-thread-2]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    network: Connecting http://127.0.0.1:80/ with proxy=DIRECT
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    network: Connecting http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom with cookie "__qca=P0-485005983-1418609728740"
    30.06.2015 06:35:54.852 *ERROR* [pool-12-thread-3]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    30.06.2015 06:35:54.854 *ERROR* [pool-12-thread-1]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    30.06.2015 06:35:54.854 *ERROR* [pool-12-thread-4]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    30.06.2015 06:35:54.855 *ERROR* [pool-12-thread-2]() org.weasis.dicom.explorer.wado.LoadSeries Http Response error 404 for http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom
    30.06.2015 06:35:54.902 *INFO* [AWT-EventQueue-2]() org.weasis.dicom.explorer.DicomModel Remove Patient: BRAINIX
    30.06.2015 06:35:54.902 *INFO* [AWT-EventQueue-2]() org.weasis.dicom.explorer.DicomModel Remove Study: Dec 1, 2006 2:16:45 PM
    cache: MemoryCache: removed entry http://172.16.12.190:8080/weas…172.16.12.190:8080/weasis


    When i tried to open the URL http://127.0.0.1/cgi-bin/dgate…tType=application%2Fdicom. 140KB file was downloaded.


    Please guide..


    --HM

    Hi Marcel


    I had added port 80 in WADO Port but the problem remains the same. Please find my Server Log with debug status =4 (Cannot upload txt, log or pdf extension, SO have to place it on Google Drivehttps://drive.google.com/file/…IbkhFVU0/view?usp=sharing).


    On reviewing the log i found some messages like


    [PACS] 20150510 20:49:13 Query On Study
    [PACS] 20150510 20:49:13 Queried item 0008 0080 is not in the database
    [PACS] 20150510 20:49:13 Queried item 0020 000e is not in the database
    [PACS] 20150510 20:49:13 Queried item 0020 0011 is not in the database
    [PACS] 20150510 20:49:13 Queried item 0020 0013 is not in the database


    [PACS] 20150510 20:49:16 Query On Series
    [PACS] 20150510 20:49:16 Testing transfer: '1.2.840.10008.1.2.1' against list #0 = '1.2.840.10008.1.2'
    [PACS] 20150510 20:49:16 Testing transfer: '1.2.840.10008.1.2' against list #0 = '1.2.840.10008.1.2'
    [PACS] 20150510 20:49:16 Queried item 0020 1206 is not in the database
    [PACS] 20150510 20:49:16 Queried item 0020 1208 is not in the database



    [PACS] 20150510 20:49:17 Query On Image
    [PACS] 20150510 20:49:17 Queried item 0020 1206 is not in the database
    [PACS] 20150510 20:49:17 Queried item 0020 1208 is not in the database
    [PACS] 20150510 20:49:17 Queried item 0020 4000 is not in the database


    I think some mandatory attributes such as Series Instance UID cannot be ignored since those attributes are used to uniquely identify the individual series and images of a study. These attributes should be stored in the database when the images are received by PACS and they should not be empty/null /non-unique.


    Please guide. I am also looking at other postings in the forum.


    --HM

    Can you explain me the concept and use of VIRTUAL SERVER and VIRTUAL QUERIES in conquest? I had read the manual and forum but its still unclear to me.


    What are the use of Virtual Server and Queries in our real world and how can we benefit from them on our setups.


    When i setup Virtual Server, the Doctor query the main server (the front server), Virtual Server A and B were configured and defined in known workstations/modalities page. Request made goes to both server A & B. And if Study is found then images are first copied to Main Server and then they are pushed to client. This whole process takes too much time. And once the study is served to the doctor the copied study remains on the main server and you have to delete it manually.


    Also tell me after images are pushed to requested workstation, the images should be deleted automatically from the main server


    --HM

    Hi Mracel


    How can i setup conquest server as a cache server? I had two conquest servers. One server is the main archive server and other will work as cache server. The cache server will listens for the scheduled exams (read data from conquest worklist table) and retrieves comparison images for the scheduled patient from the archive on basis of study description. Please tell me how can i make the cache server to be fast in terms of image retrieval.


    I had tested the prefetch option you told me earlier that sometimes hang the whole server and most of the times didn't fetch any result. And Secondly i want that prefetched studies can be forwarded to designated Workstations with the Current Exam so that doctors don't need to pull the old scans.



    --HM

    Hi Marcel!


    Can i apply Compression based on body part or modality type? Like JPG for CT Scan, JPG2000 for MRI etc.


    Is it possible that i save the same version of image in different compression ratios. For slow network or clinics, highly compressed images must be available and for Radiologist raw images with zero compression should be available. I must have the option to define which AETs come under slow network and which should query raw images.


    --HM