Retrospectively Patient Seal information (ProjShortCode004UC) : public usecase
Created: 11/29/06 14:57:55
Modified: 07/30/07 13:54:33
Project:
Advanced:
Element Source Role Target Role Details
User
Actor  
Name:  
 
Name:  
 
 
Constraint Type Status Detail
Goal 1. Goal Approved
The information is Sealed on the Spine.

Note. The Information may also be held sealed locally assuming the original information is held on the same local system.
Description 2. Description Approved
This Use Case describes the situation where information which has already been recorded, is now to be Sealed.

Retrospective Sealing of PSIS held information can be done via CSA. LSP systems must be able to offer retrospectiv sealing for locally held information and may provide functionality to retrospectively seal PSIS information.

This Use Case covers the following scenario.

Not Sealed to Sealed
Not Selaed to Sealed and Locked ( locally)
Sealed to Sealed and Locked (locally)
Sealed and Locked to Sealed (locally)


The process is the same regardless of whether or not the information is be Sealed or Sealed & Locked.
Trigger 3. Trigger Approved
The Patient Identifies to a Clinical User that they wish to Seal some existing clinical information.
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

The User is viewing information which isn't sealed.
Successful Post-Condition 5.Post-condition Approved
Message is stored on Spine
Guaranteed Post-Condition 5.Post-condition Approved
Spine stores the Refusal Message as a discrete event