Get SR in QR if empty image level query returned

Issue #732 resolved
Ed McDonagh created an issue

One PACS is returning an empty response at image level when interrogating SR series to see which type of SR they are.

Instead of dropping the SR from the response in this circumstance we would do better to get it and drop it in import if not appropriate.

Comments (28)

  1. Ed McDonagh reporter

    @David Platten I'm trying to think through the logic of this one.

    Simple case:

    • SR series found in RF/XA study
    • Image level query returns nothing for SR series
    • Get SR series anyway, just in case it is useful

    Not so simple case:

    • SR series found in mammo or DX/CR study
    • Image level query returns nothing for SR series
    • Get SR series in preference to images? (would normally be the case if we know it is an RDSR)
    • Get images because we don't know what the SR is (current behaviour)
    • Get both?

    CT:

    • How do we ensure we do the right thing if a PACS has SR radiologists reports in, returns empty to the image level query, and we want to trigger Philips or Toshiba legacy behaviour?

    Also, if we know a particular PACS behaves properly in this respect (i.e. most of them), do we maintain the current behaviour (i.e. ignore empty SR series), and just have a flag for naughty PACS in the QR node configuration?

  2. David Platten

    I was thinking of an implementation like your last point: have a command-line flag to try and retrieve empty SR series, otherwise just use current behaviour.

    For CT my intention is to run a query with the --toshiba flag first, and then run another with a --try_empty_SR flag to obtain the SR data.

  3. Ed McDonagh reporter

    So if we use this flag as a second query, do we make it behave as though empty SRs are RDSRs and if we find one we drop all other responses, ie images.

    Is that what you were proposing?

  4. David Platten

    Hi Ed. Yes, that's more-or-less what I was thinking. I don't want any images returned when I make this sort of query, just SRs.

  5. David Platten

    As it's just qrscu.py that's changed I could test it on my live system to query PACS, or would that be a really bad idea?

  6. Ed McDonagh reporter

    I think that would be fine. I think the worst that could happen is that the query returns not quite the right results.

    I'm never quite sure whether just switching out the file will automatically make the commands available via the executable script. I think it will.

  7. David Platten

    @Ed McDonagh I'm very pleased to report that the qrscu.py retrieves SRs from the "empty" series perfectly. I'll report back here tomorrow once some "regular" queries have also been carried out. Thanks.

    In setting up a new PowerShell script to run a -emptysr query in the early hours of every morning I noticed that there's an error in the https://docs.openrem.org/en/latest/netdicom-qr.html documentation. It currently includes the line:

    The above PowerShell script could be run on a regular basis by adding a task to the Windows Task Scheduler that executes the powershell program with an argument of -file C:\\path\\to\\script.ps1.

    However, the double backslashes are not required; it should read:

    The above PowerShell script could be run on a regular basis by adding a task to the Windows Task Scheduler that executes the powershell program with an argument of -file C:\path\to\script.ps1.

  8. Ed McDonagh reporter

    Do you have time to throw that into the other branch and issue and then it can go out with the docs update?

    I haven't had a chance to digest Richards suggestion, so if you want to implement that too, be my guest!

    We can then merge into the docs branch then merge that back into latest.

  9. Ed McDonagh reporter

    I did it on the train this morning, but forgot to push it when I got in. Then when I turned on the laptop this afternoon, the screen is dead again. Aaarrrrgggghhhh!

  10. David Platten

    Note: the link to "DICOM store and query retrieve documentation" under the docs menu on the queryremote page doesn't work.

  11. Log in to comment