In i2b2 a user who is able to run queries and is only allowed to see aggregated results is known as an obfuscated user. An example of an aggregated result is Number of patients; this analysis type will only return the a patient set size - no patient data is returned. The obfuscated user is limited to the number of times he / she can run the same query in a project within a specified time period. If the user exceeds the maximum number of times then their account will be locked and only an administrator can unlock it.
The setfinder query - lockout properties enable you to customize this feature to what will work best for you and your users. These properties are defined in the CRC setfinder query lockout parameter section of the crc.properties file.
Explanation of lockout properties
The following table provides a brief explanation of the different lockout property values and what they mean.
In the i2b2 Web Client, obfuscated results will appear in Query Status with a +/- 3 next to the count. This +/- 3 is defined in the Web Client code; The client never looks to the CRC properties to determine what to display. Therefore, changes made to the edu.harvard.i2b2.crc.setfinderquery.obfuscation.minimum.value property will have no effect on the +/- value that displays in the Web Client. This property is simply used by the CRC during the obfuscation process to determine the set size that will be returned to the clients as the obfuscated result.
Steps to set the CRC setfinder query lockout properties
1. In the crc.properties file scroll to the section called CRC setfinder query lockout parameter.
2. Edit the properties to reflect how you would like the lockout feature to work in your environment.
3. Save your changes. You can close the file if you do not want to edit any more of the optional properties defined in the next few sections.