Use Case DescriptionOMaR Project

Use Case Description”OMaR Project

Use Case Name : Update Treatment
Use Case Purpose: The purpose of this use case is to update the Treatment for a Resident.
Point of Contact:  
Date Modified:  
Preconditions: The Access Clinical Records use case has been successfully executed.
Postconditions: The treatment is updated.
Limitations: Based on security privileges the actor's ability to change Treatment varies.
Assumptions: None identified.

Basic Flow:

A. The actor reviews the Clinical Records via the Access Clinical Records use case.
B. The actor authorizes recommended Treatments if appropriate.
C. The actor recommends new Treatments.
D. The actor reviews recommended Orders.
E. The actor authorizes recommended Orders.
F. The actor reviews test results.
G. The actor writes new Treatments and related Orders.
H. The actor updates Progress Notes if applicable .

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