Use Case Description—OMaR Project

Use Case Name:	Access Clinical Records
Use Case Purpose:	The purpose of this use case is to allow the Clinical Record information to be accessed by the appropriate actors.
Point of Contact:	?/foNT>
Date Modified:	?/FONT>
Preconditions:	None identified.
Postconditions:	Clinical Records will remain locked until the Clinical Records User completes access and “releases?the Clinical Records.
Limitations:	Only the same Clinical Records User to whom the Clinical Records were released can provide updates or return the Clinical Records.
Assumptions:	None identified.

Basic Flow:

A.	The Clinical Records User identifies him- or herself to OMaR.
B.	INCLUSION: Perform Verify Security Permissions use case. OMaR verifies the Clinical Records User's security access, permissions, and so on.
C.	The Clinical Records User specifies the Clinical Record by Resident.
D.	The Clinical Record is made available for the Clinical Records User to view.
E.	If the Clinical Records User wants to update the Clinical Record, EXTENSION: Perform Update Clinical Records use case.
F.	If the Resident is being transferred out of the facility, update Records Closure Schedule and create a copy of the Clinical Records for the Clinical Records User.
G.	If the Clinical Records User wants to access additional records, go to step C.

Alternate Flow:

Condition Triggering Alternate Flow:? OMaR does not recognize the Clinical Records User as having permission to review the Clinical Records.

C1.	Access to the Clinical Records is denied.
C2.	OMaR tells the Clinical Records User that he or she does not have sufficient permission to review the Clinical Records.
C3.	OMaR returns to step A in the Basic Flow.

Condition Triggering Alternate Flow:? The requested Clinical Record is already being used and is locked out.

C1.	Access to the Clinical Records is denied.
C2.	OMaR tells the Clinical Records User that the Clinical Record requested is in use and locked out.
C3.	OMaR returns to step A in the Basic Flow.