Use Case DescriptionOMaR Project

Use Case Description”OMaR Project

Use Case Name : Establish Treatment
Use Case Purpose: The purpose of this use case is to create or update a Treatment for a Resident.
Point of Contact:  
Date Modified:  
Preconditions: The Access Clinical Records use case has been successfully executed.
Postconditions: Treatment is established.
Limitations: None identified.
Assumptions: None identified.

Basic Flow:

A. The Physician reviews the Clinical Records via the Access Clinical Records use case.
B. The Physician writes Orders to implement the Treatment.

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