| Created: | 11/29/06 16:27:43 |
| Modified: | 07/16/07 19:50:11 |
Project: |
|
Advanced: |
|
| Element | Source Role | Target Role | Details |
|
«Host System» Local System Actor |
Name: |
Name: |
| Element | Source Role | Target Role | Details |
|
LSP User Actor |
Name: |
Name: |
| Constraint | Type | Status | Detail |
| Goal | 1. Goal | Approved | To successfully seal Patient Clinical information as it's being recorded..
|
| Description | 2. Description | Approved | This Use Case will allow Patients to Seal clinical information as it's being recorded.
It deals primarily with sending sealed information to the Spine - but also acknowledges that such information will also be stored locally. |
| Trigger | 3. Trigger | Approved | Patient requests information to be Sealed prior to consultation.
|
| Pre-Conditions | 4. Pre-condition | Approved | The Clinical Setting has Contemporaneous Sealing functionality.
The User has an Legitimate Relationship with the Patient. The User has the correct Sealing RBAC |
| Success Post-Condition | 5.Post-condition | Approved | The Spine stores message .
Note - If the information is not to be sent to the Spine, then the local system must still seal and store the information locally , using the same metadata. |
| Guaranteed Post Condition | 5.Post-condition | Approved | The Spine stores the refusal message as a discrete event.
Note. The Refusal will always be sent to the Spine - even if the information itself is not resident on the Spine. |