kpacs with cdmedicpacsweb

    Hey,


    Thanks for making such a good software with useful features.


    I downloaded the Kpacs , I have configured cdmedicpacsweb as my CTN server(available at the sourceforge.net).
    Now I want to pull the images from the cdmedicpacsweb server.I have configured AET ,Port No and Ip address for the Kpacs on the cdemdicpacsweb server and also have configure the Kpacs with cdmedicpacsweb AE ,Port No and Ip address.


    I can send the studies from the cdmedicpacsweb server to the kpacs workstation but kpacs is not able to pull the data from the cdmedicpacsweb.


    Does kpacs has such feature(pulling the data from the another DICOM Server) ?


    cdmedic entry
    AE : KPACS PORT 111 IP Address 192.168.1.50


    on Kpacs


    AE : PACS PORT 10004 IP Address 192.168.1.68



    I am not even able to query the DICOM server (cdmedicpacsweb) for any patient.


    For ex I select the cdmedicpacsweb in Query Dicom.I gave patient name as "ANONYMOUS" and then do th search it shows no study found.Whereas there about 7 studies with the name ANONYMOUS on the cdmedicpacsweb.



    Thanks & Regards


    Ankush Grover

    I personally have no experience with CDmedic but many users reported compatibilty with K-PACS. At first you should check if the settings in "dicom settings" for CDmedic are correct. Then try to query the server. Look at the logfiles of the server, here you might find the problem.
    Btw.: if you did not change the default settings, then the AET of K-Pacs is not KPACS but KPSERVER.


    Regards,
    Andreas

    Hey,


    When I tried to query the cdmedicpacs server through k-pacs the following output was generated.




    DUL FSM Table: State: 1 Event: 4
    DUL Event: Transport connection indication
    DUL Action: AE 5 Transport Connect Response
    Read PDU HEAD TCP: 01 00 00 00 01 05
    Read PDU HEAD TCP: type: 1, length: 261 (105)
    DUL FSM Table: State: 2 Event: 5
    DUL Event: A-ASSOCIATE-RQ PDU (on tranport)
    DUL Action: AE 6 Examine Associate Request
    PDU Type: Associate Request PDU Length: 267
    01 00 00 00 01 05 00 01 00 00 50 41 43 53 20 20
    20 20 20 20 20 20 20 20 20 20 4b 50 61 63 73 51
    52 20 20 20 20 20 20 20 20 20 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
    00 00 00 00 00 00 00 00 00 00 10 00 00 15 31 2e
    32 2e 38 34 30 2e 31 30 30 30 38 2e 33 2e 31 2e
    31 2e 31 20 00 00 66 01 00 ff 00 30 00 00 1b 31
    2e 32 2e 38 34 30 2e 31 30 30 30 38 2e 35 2e 31
    2e 34 2e 31 2e 32 2e 32 2e 31 40 00 00 13 31 2e
    32 2e 38 34 30 2e 31 30 30 30 38 2e 31 2e 32 2e
    31 40 00 00 13 31 2e 32 2e 38 34 30 2e 31 30 30
    30 38 2e 31 2e 32 2e 32 40 00 00 11 31 2e 32 2e
    38 34 30 2e 31 30 30 30 38 2e 31 2e 32 50 00 00
    3a 51 00 00 04 00 00 40 00 52 00 00 1b 31 2e 32
    2e 32 37 36 2e 30 2e 37 32 33 30 30 31 30 2e 33
    2e 30 2e 33 2e 35 2e 32 55 00 00 0f 4f 46 46 49
    53 5f 44 43 4d 54 4b 5f 33 35 32
    Parsing an A-ASSOCIATE PDU
    PDU type: 1 (A-ASSOCIATE RQ), PDU Length: 261
    DICOM Protocol: 1
    Called AP Title: PACS
    Calling AP Title: KPacsQR
    Parsing remaining 193 bytes of A-ASSOCIATE PDU
    Next item type: 10
    Subitem parse: Type 10, Length 21, Content: 1.2.840.10008.3.1.1.1
    Successfully parsed Application Context
    Parsing remaining 168 bytes of A-ASSOCIATE PDU
    Next item type: 20
    Parsing Presentation Context: (20), Length: 102
    Presentation Context ID: 1
    Parsing remaining 98 bytes of Presentation Ctx
    Next item type: 30
    Subitem parse: Type 30, Length 27, Content: 1.2.840.10008.5.1.4.1.2.2.1
    Successfully parsed Abstract Syntax
    Parsing remaining 67 bytes of Presentation Ctx
    Next item type: 40
    Subitem parse: Type 40, Length 19, Content: 1.2.840.10008.1.2.1
    Successfully parsed Transfer Syntax
    Parsing remaining 44 bytes of Presentation Ctx
    Next item type: 40
    Subitem parse: Type 40, Length 19, Content: 1.2.840.10008.1.2.2
    Successfully parsed Transfer Syntax
    Parsing remaining 21 bytes of Presentation Ctx
    Next item type: 40
    Subitem parse: Type 40, Length 17, Content: 1.2.840.10008.1.2
    Successfully parsed Transfer Syntax
    Successfully parsed Presentation Context
    Parsing remaining 62 bytes of A-ASSOCIATE PDU
    Next item type: 50
    Parsing user info field (50), Length: 58
    Parsing remaining 58 bytes of User Information
    Next item type: 51
    Maximum PDU Length: 16384
    Successfully parsed Maximum PDU Length
    Parsing remaining 50 bytes of User Information
    Next item type: 52
    Subitem parse: Type 52, Length 27, Content: 1.2.276.0.7230010.3.0.3.5.2
    Parsing remaining 19 bytes of User Information
    Next item type: 55
    Subitem parse: Type 55, Length 15, Content: OFFIS_DCMTK_352
    Successfully parsed User Information
    70172 Application title KPacsQR not found in database in DMAN_LookupApplicati
    on
    e0172 Failed to lookup application (KPacsQR) in DMAN_LookupApplication
    Incorrect Association Request
    DUL_Reject Association RQ
    DUL FSM Table: State: 3 Event: 7
    DUL Event: A-ASSOCIATE resp prim (reject)
    DUL Action: AE 8 Send Associate RJ
    DUL FSM Table: State: 13 Event: 17
    DUL Event: ARTIM timer expired (rej/rel)
    DUL Action: AA 2 Close Transport
    REJECTED (KPacsQR ankush.sunupdelhi.net ) (PACS ) 20050621 161806.000000 0
    70172 Application title KPacsQR not found in database in DMAN_VerifyApplicati
    on
    50172 Failed to verify application (KPacsQR, ankush.sunupdelhi.net) in DMAN_V
    erifyApplication
    2fff2 APP Illegal service parameter (name Calling AE Title, value KPacsQR)
    5fff2 APP One or more service parameters were incorrect
    7fff5 APP Failed to establish Association
    DUL_Receive Association RQ



    I checked the status on the cdmedicpacsweb it can ping the K-pacs server
    Below is the output of the status command available with cdmedicpacsweb.


    Status
    ping: ankush
    0% packet loss
    dicom_echo: KPServer
    Successful operation



    ping: pacs
    0% packet loss
    dicom_echo: PACS
    Successful operation


    Can you help me in querying cdmedicpacsweb from k-pacs.


    Thanks & Regards


    Ankush Grover

    Hey ,


    It is now working fine.Means I can query the cdmedicpacsweb from k-pacs.


    What i did is that I added AE Title,IP address/Hostname and port number of KPacsQR, KPServer and KPacsMove on the cdmedicpacsweb dicom server and also added cdmedicpacsweb AE Title,IP and Port number in K-pacs .


    Now I am able to query the cdmedicpacsweb from k-pacs.


    Thanks & Regards


    Ankush Grover

Participate now!

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

Register Yourself Login