| Created: | 11/28/06 15:28:23 |
| Modified: | 07/12/07 13:44:34 |
Project: |
|
Advanced: |
|
| Element | Source Role | Target Role | Details |
|
Privacy Officer Actor |
Name: |
Name: |
| Element | Source Role | Target Role | Details |
|
User Actor |
Name: |
Name: |
| Constraint | Type | Status | Detail |
| Goal | 1. Goal | Approved | The goal of this Use Case is for a User who does not have automatic access right to a Patients Sealed information, to be able to see the sealed information.
Note. Sealed & Locked information can never be accessed in this way. |
| Description | 2. Description | Approved | This Use Case describes the steps a User will follow in order to be able see Sealed information, which they don't have automatic access.
Note. A User will have automatic access if they are in the sealing workgroup,or are the original author. |
| Trigger | 3. Trigger | Approved | User wishes to view Sealed Information to which they have no automatic right of access
|
| Pre-Condition | 4. Pre-condition | Approved | Query results have indicated that the Patient has Sealed information.
User has RBAC to override Patient Seal. User has a legitimate Relationship with Patient. |
| Successful Post-Condition | 5.Post-condition | Approved | Sealed information is displayed.
A alert is received by the organisation's Privacy Officer. |
| Guaranteed Post Condition | 5.Post-condition | Approved | No Sealed Information is displayed
|
| Object | Type | Connection | Notes |
| Patient Notification | UseCase | Includes |