Posts by marcelvanherk
-
-
This is controlled by a setting in dicom.ini:
ImportExportDragAndDrop = 1
Marcel
-
-
hm,
there goes my test plan. It might work if you carefully make sure the selection returns one item only. The command line version might work on the 1.4.16alpha3 version: it selects a study root move if appropriate.
marcel
-
the move button in the windows gui.
marcel
-
Hi,
basically, all queries work, but conquest does not display the results (known issue also with kodak). This means that you can now try move requests.
Marce
-
Hi,
conquest proposes a number of query types, including a worklist query. That this is rejected is normal, the others should be accepted. And the log shows that 17 responses are generated. So this seems OK to me. Are there any results shown on conquest? And is there a difference between a patient root query and a study root query?
Marcel
-
Try it from the windows GUI for one study; the level dropdown allows study root actions. Double clicking the series number label allows UID selection.
Marcel
-
Hi,
make sure the AE, IP and port of k-pacs are known to conquest: DICOM image retrieval uses a reverse connection..... In other words try to send from conquest to kpacs, if that works and the AE is set correctly you should be able to load images.
Marcel
-
Hi,
can you specify what is the speed problem you are encountering?
Marcel
-
Hi,
you need to write a batch file or program to do that which is not trivial, but requires basic programming skills. The GUI drag and drop feature should suffice for most users as you can drop an entire folder or CD at once.
Marcel
-
Hi,
Create a script that runs dgate --addimagefile:filename
for each DICOM image.
Marcel
-
Hi,
RADAERCH wont know local. You need to provide the correct conquest AE and it must be known to radarch. I.e.,
dgate --movestudies:RADARCH,CONQUESTSRV1,20020105
Marcel
-
Hi,
here are some anwers.
1. People say and they are using separate CONQUEST SERVER for storing images of every modality .i.e. CONQUEST SERVER -A for CT , CONQUEST SERVER - B for MRI and CONQUEST SERVER - C for CR/DR (separate server for every modality) whereas there is one master server that receive images and automatically route them to respective server on the basis of modality as well as AET. I want my Technicians from all modalities to send images to one main server (not on separate servers that are configured of each modality )that route the images to their respective servers. (How it can be done).
in dicom.ini:
ExportConverters = 2
ExportModality0 = CT
ExportConverter0 = forward series to SERVERA
ExportModality1 = MRI
ExportConverter1 = forward series to SERVERB
etc2. I want my Radiologist who is sitting on VOXAR, VITRAEA, EFILM and KODAK MX-R to query one CONQUEST SERVER not separately for each server. Because currently all the workstations are receiving images from all modalities as they are multi modality. (how this can be done in conquest server when i have configure separate server for every modality.)
in dicom.ini on master server:
VirtualServerFor0 = SERVERA
VirtualServerFor1 = SERVERB
etc3. Does your server offers prefetching????? (if yes, how it can be configured)
An ExportConverter can schedule "get study" or "get patient". This means that receiving an image of a patient can trigger collecting other (older) data from other servers.
4. It is possible to query one Conquest Server and if this server does not find anything route the query request to another Conquest Server and so on? If yes, how to do that? If the Radiologist Server - A for CT but there was no scan found , the query is route to MRI Server . Scans are found on there as well on CR/DR Server. The Radiologist see all the tests performed.
VirtualServerFor0 = SERVERA
VirtualServerFor1 = SERVERB
etc5. When Radiologist query one server , the query should be passed to all the servers and all the scans of that patient whether it has CT scan, MRi, CR/DR all should be visible to Radiologist and he can retrieve any scan of his choice. (How this can be done)
VirtualServerFor0 = SERVERA
VirtualServerFor1 = SERVERB
etc6. Can you if possible post my answers on the forum as well as email them on my email address as some of the forum sites are blocked by our Network Administrator.
Marcel
-
Hi Marcel Van Herk!
I am working as PACS Administrator and Manger in one of the hospitals in Pakistan and recently i had downloaded CONQUEST SERVER on the request of my friend as i need a simple dicom receiver. After running it for three (03) months in the testing phase i discover that this is not an ordinary dicom receiver it is a full fledge PACS with all the features you find in any of the commercial PACS that are available in the market now a days. I had successfully configured the CONQUEST SERVER on windows and now receiving images from CT, MRI and CR/DR modalities and the current image volume it is handling is almost around about 1TB.
Today while surfing the internet and the forum i discovered this new side of the conquest server. I will be grateful if you answer my following questions appended below:-1. People say and they are using separate CONQUEST SERVER for storing images of every modality .i.e. CONQUEST SERVER -A for CT , CONQUEST SERVER - B for MRI and CONQUEST SERVER - C for CR/DR (separate server for every modality) whereas there is one master server that receive images and automatically route them to respective server on the basis of modality as well as AET. I want my Technicians from all modalities to send images to one main server (not on separate servers that are configured of each modality )that route the images to their respective servers. (How it can be done).
2. I want my Radiologist who is sitting on VOXAR, VITRAEA, EFILM and KODAK MX-R to query one CONQUEST SERVER not separately for each server. Because currently all the workstations are receiving images from all modalities as they are multi modality. (how this can be done in conquest server when i have configure separate server for every modality.)
3. Does your server offers prefetching????? (if yes, how it can be configured)
4. It is possible to query one Conquest Server and if this server does not find anything route the query request to another Conquest Server and so on? If yes, how to do that? If the Radiologist Server - A for CT but there was no scan found , the query is route to MRI Server . Scans are found on there as well on CR/DR Server. The Radiologist see all the tests performed.
5. When Radiologist query one server , the query should be passed to all the servers and all the scans of that patient whether it has CT scan, MRi, CR/DR all should be visible to Radiologist and he can retrieve any scan of his choice. (How this can be done)
6. Can you if possible post my answers on the forum as well as email them on my email address as some of the forum sites are blocked by our Network Administrator.
Regards
Hammad
-
Thanks,
what was it?
Marcel
-
Hi,
the query issue is not due to limits but due to the PACS not returning empty or non defined elements the same for all search results. This is a violation with the DICOM standard that recently started showing up for several systems and it cannot be solved without an upgrade to our software. This is a known issue for a next release...
The transfer can be done using a batch file with dgate --movestudy: commands.
Marcel
-
Hi,
did you try other styles of query: double click series number; select study root queries. Incomplete server response may also indicate a problem with DICOM compliance in the answer. We have a similar problem with Kodak (see known bugs).
Marcel
-
Hi Pat,
Is this what you mean?
exportconverters = 2
exportconverter0 = forward series to ....
exportconverter1 = forward series to ....Marcel
-
Hi,
it is not. I will think about it.
Marcel
