Use Case Description—OMaR Project

Use Case Name: Update Clinical Records
Use Case Purpose: The purpose of this use case is to update a Clinical Record's data.
Point of Contact:  
Date Modified:  
Preconditions: The Access Clinical Records use case has been successfully executed.
Postconditions: The Clinical Record is updated.
Limitations: None identified.
Assumptions: None identified.

Basic Flow:

A. The Clinical Records User requests to update a specific Resident's Clinical Record.
B. The Clinical Record is retrieved.
C. The Clinical Records User updates the Clinical Record.

Alternate Flow:

Condition Triggering Alternate Flow: The update of the Clinical Record fails.

C1. OMaR tells the Clinical Records User that the update has failed.
C2. The ...

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.