Why is accesionn the primary key in table dicomworklist?

    I am using Conquest DICOM 1.4.15, and PostgreSQL 8.3 as backend.


    I have seen that the field accesionn is declared as primary key of the table dicomworklist.


    Due to this, I can't insert two rows, each representing a "scheduled procedure step", associated with the same "requested procedure" and also the same "imaging service request".


    I also can't insert two rows, each representing a "scheduled procedure step", each one associated with a "requested procedure", but both associated with the same "imaging service request".


    This associations I'm referring to are represented on the diagram on page 27 of DICOM 3 Part 17 (ftp://medical.nema.org/medical…/2009/09_17pu.pdf#page=27).


    ¿Should I delete the primary key constraint? ¿Has anyone dealt with this?


    Thank you.

    Hi,


    the first field in a table in dicom.sql is the primary unique index - it is set to accessionnumber in the worklist table. You can assign another field as primry index by editing dicom.sql.


    Marcek

Participate now!

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

Register Yourself Login