| Created: | 11/29/06 17:05:35 |
| Modified: | 12/21/06 10:08:58 |
Project: |
|
Advanced: |
|
| Element | Source Role | Target Role | Details |
|
User Actor |
Name: |
Name: |
|
|
Privacy Officer Actor |
Name: |
Name: |
| Constraint | Type | Status | Detail |
| Goal | 1. Goal | Approved | The goal of this Use Case is satisfy a Subject Access Request.
|
| Description | 2. Description | Approved | This Use Case describes the process of fulfilling a Subject Access Request with regard to Sealed information.
The logic is intended to describe the business rules as information encountered while the system progresses through the record set. The use case describes dealing with one item of information and implicitly must iterate until the record set is complete. |
| Trigger | 3. Trigger | Approved | A Subject Access Request is initiated.
|
| Pre-Conditions | 4. Pre-condition | Approved | The User has the necessary RBAC to view the Patient record.
The User has a Legitimate Relationship with the Patient. The Patient has Sealed Information. It is not envisaged that the User will have any automatic access rights to the Sealed Information. |
| Successful Post-Condition | 5.Post-condition | Approved | The information is included in the SAR
|
| Guaranteed Post-Condition | 5.Post-condition | Approved | Information isn't included in the SAR output.
|
| Object | Type | Connection | Notes |
| Patient Notification | UseCase | Extends |