Hi,
If you are on windows you can check the query move page. However, if you are on linux you have limited options.
Marcel
Hi,
If you are on windows you can check the query move page. However, if you are on linux you have limited options.
Marcel
Hi,
I believe the correct action is to refuse. However, it does not refuse on the same image UID but on an image with the same image UID and a different SeriesUID. This image would be orphaned as explained in the "change patient ID" post.
Marcel
Hi,
first make sure a direct send or query from conquest to URI works. I guess there is a configuration error.
Marcel
Hi,
this works, as long as you are sure that no two copies of the same image with different patient IDs come together in one server. So delete and repush is OK.
Marcel
Hi,
please try to send directly from conquest to URI to check the configuration.
Marcel
Hi,
there must be a configuation error. Is MySQL set to 1 in dicom.ini?
Marcel
Hi,
This must be a system in your department doing this - it is definitively not conquest itself. You can enable debug logging and put it to the highest level. Maybe some other items will give some insight into the culprit.
Marcel
Hi.
You probably do not need to do anything to upgrade except replace the files, although I am adding some stuff and settings to the web pages.
Marcel
Hi,
this is a runtime computed element and conquest does not support it (yet). So no luck.
Marcel
Hi,
Exportconverters = 2
Exportconverter0 = ...
Exportconverter1 = ....
Marcel
Hi,
the bug was not confirmed: the browser with native mysql it works in 1.4.14beta. BrowsethroughDBF works too but is not necessary.
Marcel
Hi,
ConquestPACS.doc was split (and re-ordered) into windowsmanual.pdf (install and config) and DicomConformance_FilesLST_Changes.pdf (technical). Linuxmanual.pdf is mostly new stuff for linux users. If you know the previous version well, there should be little surprises. I would, however, suggest to install 1.4.14beta (on the forum). Its bugs are well known and it is very stable. 1.4.14 is expected in a short while.
Marcel
Hi,
MyODBC seems to have several issues. Try to switch to the native mysql driver of 1.4.14beta. This should be possible without a regen.
Marcel
Hi,
for the database, I believe i would go would mysql now, it needs less maintenance to keep going for very large table sizes. The main issue is how you are going to backup the main storage and the database. I have seen raid systems fail catastrophically, so we still put stuff on tape for backup.
Marcel
Hi,
is there a way to find out which images where not tranferred? Maybe they are not accepted by the recieving server? Transfer accepts only sop classed listed in dgatesop.lst, while drag and drop accepts anything. Interesting is to repeat the transfer and see if the problem is reproducible.
Marcel
Probably you can use quotes around the directory name.
Marcel
Hi,
you can add almost any field in any database (see the DICOM standard for a list of items). However, DICOM command fields such as sending AE are forbidden to add: they would actually work and be saved. But if you ahve for instance having the AE in the database this would block queries from all but that AE (all others would not match).
Marcel
Hi,
you can edit DICOM.SQL to add any field, except the sending AE. Do not modify the first and the last entry of a database definition. But referring physician (I looked it up in dgate.dic to be 0008,0090) is already there:
From *study*
{ 0x0008, 0x0090, "ReferPhysician", 64, SQL_C_CHAR, DT_STR },
groep, element, database field name, length, SQL type (SQL_C_CHAR or SQL_C_DATE) and dicom type (mostly DT_STR).
When done, you need to restart the server and regenerate the database.
Marcel
Hi,
Sure, you can use a number of predefined tags like %f (filename) and %i (patient ID) in the converter string, but also any entry in the DICOM header (%V0010,0010), this is the patient name. Just look the syntax up in the manual.
Marcel
With exportconverters you can surely do this! Just slightly edited the post.
Marcel