Use Case DescriptionOMaR Project

Use Case Description”OMaR Project

Use Case Name :	Verify Security Permissions
Use Case Purpose:	The purpose of this use case is to verify that the actor requesting access to Clinical Records information is permitted to have access to such information. This use case is included in other use cases.
Point of Contact:
Date Modified:
Preconditions:	None identified.
Postconditions:	None identified
Limitations:	None identified.
Assumptions:	None identified.

Basic Flow:

A.	The actor enters identification information.
B.	The actor's identity is verified .
C.	The actor's permission set is retrieved.
D.	The actor's permission set is provided to the including use case.

Alternate Flow:

Condition Triggering Alternate Flow:   OMaR does not recognize the actor as having access to the system.

A1.	If verification of the actor identification has failed three times, OMaR will disable this data entry interface. OMaR logs these attempts in the security log. This use case then terminates.
A2.	If verification of the actor's identification has not yet failed three times, OMaR asks the actor to reenter identification.
A3.	OMaR returns to step A in the Basic Flow.