UML for Database Design

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:
Date Modified:
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 ...