Use Case DescriptionOMaR Project

Use Case Description”OMaR Project

Use Case Name : Create Clinical Record
Use Case Purpose: The purpose of this use case is to create a new Clinical Record for a Resident.
Point of Contact:  
Date Modified:  
Preconditions: None identified.
Postconditions: A new Clinical Record is created.
Limitations: None identified.
Assumptions: The incoming Clinical Record information is in the same or compatible format as that used in the OMaR system. If not, the information will have to be entered by hand.

Basic Flow:

A. INCLUSION: Perform Access Clinical Records use case.
B. The actor searches the Clinical Records to determine if the Resident has been in the Facility before. If the records are not found the actor searches the Archive. If the Resident is not found in either, the Resident is considered to be new to the Facility.
C. If the Resident is new to the facility, the actor creates an Internal Clinical Record and copies/enters the External Clinical Record information. Then this use case ends.
D. If the Resident has been in the facility before, and if the records are closed, EXTENSION: Perform Unarchive Clinical Records use case.
E. The actor creates an Internal Clinical Record and copies/enters the External Clinical Record information.
F. The actor then links the Internal Clinical Record to the closed Clinical Records via the Clinical Records case number from the closed records.
G. If the Resident has been in the Facility before, and if the records are not closed, remove the Clinical Records from the Records Closure Schedule.
H. The actor copies/enters incoming External Clinical Record information into the open Internal Clinical Records.

Alternate Flow:

Condition Triggering Alternate Flow:   None identified.



UML for Database Design
UML for Database Design
ISBN: 0201721635
EAN: 2147483647
Year: 2001
Pages: 90

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net