Hello, I have a great favor. Importing a few years from another PACS and still face the problem out 1500 studies on one sheet as the period-to let me choose not nearly a month. Is it possible somewhere to allow permit-limit eg 3000 - 5000 studies (DICOM ae - query / retrive) one question, it would lead to significant time savings gradual copy after about 15 days ...
Much please. Hw has about 12 GB of RAM and enough computing power available. I am a licensed user.
Thanks to M.
Limit all to 1500
Details
This is me DICOM AE menu -> select the appropriate server -> Query / Retrieve
Search Remote Application Entity
And here, for example, list all Patients receive only 1500 results. I understand the need to limit the often voluminous answers the query.
But where I really burn this limit is Study Date (from - to), there I Leafs have a maximum of 1500 results which will not cover even a month, you could limit this to do something, eventually. is setting the limit somewhere in mysql data, respectively. it is compiled into the bin pacsone and it would be necessary to translate from you again?
Thanks a lot M.
Search Remote Application Entity
And here, for example, list all Patients receive only 1500 results. I understand the need to limit the often voluminous answers the query.
But where I really burn this limit is Study Date (from - to), there I Leafs have a maximum of 1500 results which will not cover even a month, you could limit this to do something, eventually. is setting the limit somewhere in mysql data, respectively. it is compiled into the bin pacsone and it would be necessary to translate from you again?
Thanks a lot M.
Looks like you are query a remote AE configured in the Dicom AE table of PacsOne Server and if that's the case, the matching results are returned by that remote AE which is NOT controlled by PacsOne Server.
If there are too many matching results returned by this remote AE, then you should make your querying key attributes less general. For example, if you are using the Study Date as the querying key, then trying using a specific date instead of a range of dates for the Study Date key attributes. You should then get a lot less matching results returned, unless this remote AE was really busy on that date with 1000+ studies which does not seem likely.
If there are too many matching results returned by this remote AE, then you should make your querying key attributes less general. For example, if you are using the Study Date as the querying key, then trying using a specific date instead of a range of dates for the Study Date key attributes. You should then get a lot less matching results returned, unless this remote AE was really busy on that date with 1000+ studies which does not seem likely.