Participant and Case Security (Secure Client) needs are not handled by the OOTB functionality

This is an enhancement request against the base C�ram application so some of the customer's business security needs can be handled by the OOTB functionality.

The customer's current systems allow them to secure client records and specify who has access to view and update a client's information (both case and participant information).

See attachment for business case.

Can the following requirements be considered for inclusion in a FMR of C�ram?

* The ability to secure a client so only specified users have read access to the client's participant and case information.
* The ability to secure a client so only specified users have update access to a client's participant and case information.
* The ability to record a reason why a client was made secure.
* The ability to specify time constraints around how long a client's record is secured for (start and end dates).
* The ability to un-secure a client's record based on access rights (this could be based on SID security or could use some sort of sensitivity rating).
* The ability to specify time constraints around how long a user has access to a specific client record (start and end dates/times).
* The ability to remove a user from having access to a specific client.
* The ability to deny access to a specific client for certain users but allow all other users access the record (the reverse of the first 2 requirements).
* The information stored about a client's security constraints should be cached to prevent having to re-read the constraints from the database as a user navigates through all the Participant and Case screens.