Details
Major Description
When an obfuscated user runs a query the results (including breakdowns) will have a ± and a pre-defined number to indicate the results are obfuscated.
In the i2b2 demo data obfuscated results will appear as follows:
Number of patients: 8±3
THE ISSUE:
The problem is this indicator does not appear if another user who is not an obfuscated user views the results of this query the obfuscation indicator does not appear in Show Query Status or Graph Results. The non-obfuscated user has no way of knowing those results are obfuscated.
For an obfuscated user the number of patients will appear as: 8±3
For a non-obfuscated user viewing the same previous query the results will appear as: 8
There needs to be some type of indicator to all users that the results are obfuscated; Not just obfuscated users.
In the i2b2 demo data obfuscated results will appear as follows:
Number of patients: 8±3
THE ISSUE:
The problem is this indicator does not appear if another user who is not an obfuscated user views the results of this query the obfuscation indicator does not appear in Show Query Status or Graph Results. The non-obfuscated user has no way of knowing those results are obfuscated.
For an obfuscated user the number of patients will appear as: 8±3
For a non-obfuscated user viewing the same previous query the results will appear as: 8
There needs to be some type of indicator to all users that the results are obfuscated; Not just obfuscated users.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 1.7.07 [ 10203 ] | |
| Reproduction Notes |
This can be reproduced in both the i2b2 demo and test environments.
STEPS TO REPRODUCE: 1. Log into the i2b2 as an obfuscated user (no role above obfuscated is associated to your user). 2. Run a query, making sure you check off all the breakdowns. 3. The results will be returned and the obfuscation indicator will appear correctly in the Show Query Results. 4. Now log into the i2b2 as a non-obfuscated user who is also a manager so you can see the previous query run by the obfuscated user. 5. Drag the obfuscated query to the Query Tool and drop it at Query Name. 6. The results of the previous query will display in Show Query Results and Graph Results. 7. Notice there is no indication that these results are obfuscated. |
|
| Assignee | Mike Mendis [ mem61 ] | |
| i2b2 Sponsored Project/s | i2b2 Web Client [ 10197 ] | |
| Status | New [ 10000 ] | Open [ 1 ] |
| Assignee | Mike Mendis [ mem61 ] | Nich [ nich ] |
| Component/s | CRC Cell [ 10035 ] | |
| Component/s | Web Client [ 10046 ] |
| Assignee | Nich [ nich ] | Mike Mendis [ mem61 ] |
| Resolution | Incomplete [ 4 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | 1.7.07 [ 10203 ] |
Re-opening issue to Move it to the i2b2 Core Project to be evaluated by the developer.
| Resolution | Incomplete [ 4 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Component/s | CRC Cell [ 10049 ] | |
| Component/s | CRC Cell [ 10035 ] | |
| Key | WEBCLIENT-128 | CORE-248 |
| Affects Version/s | 1.7.05 [ 10164 ] | |
| Affects Version/s | 1.7.05 [ 10163 ] | |
| Workflow | Web Client Issues Workflow [ 10851 ] | i2b2 Issues Workflow [ 11566 ] |
| Project | i2b2 Web Client [ 10033 ] | i2b2 Core Software [ 10034 ] |
| Fix Version/s | 1.7.09 [ 10306 ] |
| Fix Version/s | 1.7.09 [ 10306 ] |
| Fix Version/s | 1.7.12 [ 10901 ] |
| Fix Version/s | 1.7.13 [ 10902 ] | |
| Fix Version/s | 1.7.12 [ 10901 ] |
will be fixed as :
any query ran as obfuscated user will be flagged as obfuscated ( for any user view)
any query ran as obfuscated user will be flagged as obfuscated ( for any user view)
| Fix Version/s | TBD [ 11005 ] | |
| Fix Version/s | 1.7.13 [ 10902 ] |
There seems to be a defect in the CRC for a non-obfuscated user loading a previous query from an obfuscated user.