Two structured reports can have the same Study UID, different series UID
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)
-
reporter -
reporter -
assigned issue to
-
assigned issue to
-
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.)
-
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>>
-
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>>
-
reporter Forgot to have an exit if new not newer than old :-) Refs
#114→ <<cset 878ec522dce6>>
-
reporter Works, after ensuring new time was time not datetime. Refs
#114→ <<cset 208fa6f0ab85>>
-
reporter Test files for the RDSR import adaptation for multiple RDSRs. Refs
#114→ <<cset cece65c10a95>>
-
reporter Test for ref
#114→ <<cset d04c196f09c9>>
-
reporter Additional test for ref
#114→ <<cset 906f85f4d674>>
-
reporter Changes for ref
#114→ <<cset c734ca3f4995>>
-
reporter Codacy fixes from ref
#114PR, mainly tidying up imports→ <<cset 7d053ee1d916>>
-
reporter Addressing Codacy issues with the test file (as reviewed by @dplatten's Codacy config, ignored by mine!). Refs
#114→ <<cset 641d976d789e>>
-
reporter Added in clause to allow new RDSRs to be imported over existing ones imported before this code. Refs
#114→ <<cset d18e26e36e7c>>
-
reporter Adding a space to the debug message. Refs
#114→ <<cset 965da74f7d86>>
-
reporter - changed status to resolved
Merged in issue114multiplerdsrversions (pull request #150)
Issue114multiplerdsrversions
Fixes
#114→ <<cset e6f4205627db>>
-
reporter Start of docs for ref
#585,#114. WIP→ <<cset 1aea760ca6bd>>
-
reporter Spelling error in file name. Refs
#585,#114.→ <<cset 2a0d8dfa5c84>>
-
reporter A little more progress, still WIP. Refs
#585,#114.→ <<cset b513203c6dca>>
-
reporter First complete draft. Refs
#585,#114.→ <<cset 09b412adf72e>>
-
reporter Merged in charset branch to make use of the slightly revamped troubleshooting section. Refs
#585,#114.→ <<cset 18d0d073267a>>
-
reporter Merged in issue585document114multipleRDSR (pull request #169)
→ <<cset d93bc6bc2858>>
-
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...
-
reporter - changed status to resolved
Fix in issue
#614instead. -
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>>
-
reporter Adding tests for continuation CT RDSRs. Refs
#625,#114→ <<cset dd41685c3d50>>
- Log in to comment
Issue
#576was marked as a duplicate of this issue.