| Created: | 11/29/06 13:18:05 |
| Modified: | 07/16/07 20:18:06 |
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 Sealing status is successfully changed and stored on PSIS.
Note. The Information may also have its status changed locally assuming the original information is held on the same local system. |
| Description | 2. Description | Approved | This Use Case describes how information can have it's status changed retrospectively.
This is essentially the same process as retrospective Sealing, but it modelled separately for for clarity. The possible scenarios are: Sealed to Unsealed |
| Trigger | 3. Trigger | Approved | Patient requests Sealed information is unsealed
|
| Pre-Condition | 4. Pre-condition | Approved | The User has access to CSA
The User has an Legitimate Relationship with the Patient. The User has the correct Sealing RBAC |
| Successful Post-Condition | 5.Post-condition | Approved | Unsealing message stored on Spine
|