Black box testing a remote DICOM Q/R server

I am wondering if anyone has ever tried to work on the following issue. I need to execute a series of test on a remote DICOM Q/R server. This would allow some easy DICOM Conformance Statement checking. As an implementation detail of the test suite, I am running the following (DCMTK style command): ``` $ findscu --study --cancel 1 --key 0020,0010=* --key 8,52=STUDY --aetitle MINE --call THEIR dicom.example.com 11112 ``` The goal here is to find a valid StudyID (later on I'll use that StudyID to execute lower key level C-FIND, and some related C-MOVE queries). Of course it would be much easier if I could upload my own dataset and try to fetch it back, but I cannot do that against a running PACS in a clinical environment. I need to define with a minimal number of queries how to find a valid StudyID. However I fear that some DICOM implementation may have `policies` where quering the entire database is forbidden. So I was wondering if anyone has written a list of those `policies`, and maybe describe a way to retrieve a valid StudyID from a remote server with a minimal number of C-FIND queries.