Two structured reports can have the same Study UID, different series UID

Issue #114 resolved
Ed McDonagh created an issue

A Siemens CT scanner produced two structured reports - the first after an aborted study and the second after the study had been started again. Both had the same Study UID, but different Series UIDs. The protocol page listed the all events, each structured report listed only half.

Current behaviour is that the second SR is ignored as it has the same UID as the first. Suggest checking series UID and maybe event UIDs as an improvement.

Comments (26)

  1. Ed McDonagh reporter

    Newer Siemens CT software sends an RDSR at the end of each event, rather than when the study is closed. This is not configurable.

    This has been found on

    • Siemens Confidence (an RT scanner) software version VA62A
    • Siemens Definition Edge, software version VA48A (behaviour changed without any corresponding change in software version, and no recorded engineer intervention.)
  2. Ed McDonagh reporter

    Starting to work out how to deal with multiple cumulative radiation dose structured reports to ref #114. Currently just extracts event UIDs from CT RDSR.

    → <<cset 16e69133507e>>

  3. Ed McDonagh reporter

    Siemens RDSR has a study time, series time and content time. Study time is constant between RDSRs for a study, the other two change. Now using that to spot later RDSRs. Refs #114

    → <<cset d8f5dd9b03d6>>

  4. Ed McDonagh reporter
    • changed status to open

    Need to check behaviour of exports. I thought I'd fixed it so that studies being deleted during export were handled, but I have errors in my logs...

  5. Ed McDonagh reporter

    Reworked the duplicate RDSR study instance UID code so it should work for cumulative RDSRs, continuation RDSRs and duplicate RDSRs. Should also avoid issue of time() being called on a NoneType. Refs #625, #114

    → <<cset 87382c2fba58>>

  6. Log in to comment