Posts by AndreasKnopke

    It's not a bug but a misleading description. This function opens the directory where the files are located. You can copy them with standard windows shortcuts "CTRL+C" and paste them into any other location with "CTRL+V".


    Regards,
    Andreas

    Sure it does, try it out!


    There is a button called "Transfer" which "pushes" images to another location if your current table mode is "database" (the images are physically available on your harddisc). If you are in "network" mode, then the transfer button will "move" the images from source network node A to target network node B without routing them through your local K-PACS workstation.


    Regards,
    Andreas

    Thanks,
    we already have heard about this behaviour which is probably caused by a COM server lock up.
    Stangely, some machines with XP do not seem to have this problem.
    A bugfixed server version will be released soon.


    In the meantime you could do the following: Exchange the KPSERVER.exe file from the old 1.0 version with the 1.6 version. K-PACS should work anyway.


    Regards,
    Andreas

    Access to shared network path should work the same as in other windows applications (and does so for instance in my own installation) since K-PACS uses standard windows API objects and functions for this.
    There might be a specific problem in your case. Can you navigate to the shared folder in the Import dialog?


    Regards,
    Andreas

    Well, then the image itself seems to be the problem, maybe the transfer syntax is unsupported.
    Could you send me an example image or dump of the DICOM header in order to investigate further?


    Regards,
    Andreas

    Is this only happening with MAMMO images?
    Mabye your PACS requests extended negotiation or Storage Commitment which is not supported by K-PACS.
    The SOP Class Digital Mammography Image Storage - For Presentation is supported by K-PACS


    regards,
    Andreas

    Hi Georg,
    Sorry for the late response.
    I can not really figure out, what is causing the problem. Seems to be on GE site though.
    The PACS obviously reports to many sequences when querying on series level.


    You can turn off the query on series level in K-PACS which might solve the problem:
    Change the settings:
    NoFindBeforeMove to '1'
    DicomMoveOnSeriesLevel to '0'


    in the k-pacs.ini file.


    Regards,
    Andreas

    Hi Marcel,
    nice to here from you.


    I know that Conquest can map tags on export but can it map on import as well (e.g. map write "Institution name" into "Referering Physician" BEFORE database registration)?


    If so, could you give a short example, because I did not find anything in the manual.


    Regards,
    Andreas

    Hi Stacey,


    according to the DICOM Standard, "institution name" (0008,0080) is only an optional query attribute in a study level c-find request and is not supported by most archives. That's why, iQ-View and K-PACS do - unfortunately - not support this attribute. A workarround would be to use an interface software to map the institution name attribute to an unimportant attribute that can be query on study level like "referring physician" or "study description". I do not know if Conquest supports tag mapping on import. Our commercial software DICOM Router does so.


    Regards,
    Andreas

    The port numbers can all be the same, but AE-Titels must be different. An example setup could be:


    Workstation 1: AET KPSERVER1 Port 104
    Workstation 2: AET KPSERVER2 Port 104
    and so on...


    Regards,
    Andreas

    Did you click the button with the CD icon in case the automatic detection of the inserted medium's size failed?
    Could you give some more detail on your systems specification? Number of CD/DVD burners, device type, medium type?


    Regards,
    Andreas

    Hi larc,


    we lately detected the reason for the occasionally occuring crashes but it was to late to inlcude this fix into the 2.5b version. Therefore we will release a 2.5c version soon. It is already in pre-release testing phase. If you are interested, I could send you the pre-release version for verification that the crash issue is fixed.


    What do you mean with the Conquest compression issue? Could you specify it a little more?


    Regards,
    Andreas