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.

Get UML for Database Design now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.