Use case name:

Medical Assistant Retrieve and Update Patient Record

Unique use case ID

UC_14

Primary actor(s)

Medical assistant  

Secondary actor(s)

Mammography technologist, Physician.

Goal

 

Medical stuff has logged into system and hit the “search or retrieve” function button. A search page displayed. She can have choice searching by patient name or id, which retrieves one particular patient record.

Preconditions:

Medical Assistant has logged into the system.

Flow of events:

1)      After logged on, the system displayed the functional feature to be

able to retrieve records.

2)      Medial staff selects “search” feature.

3)      The System displays a search query page.

a.       Search by Patient Medical Id.

b.       Search by Patient first name, last name.

4)      She choose Search By Patient Med Id

Or she choose Search By Name: first name, last name

5)      The System retrieves patient records based on the id or full name, then shows a most recent record of that patient. There are three functions applies to the record: “update” “print” and “audit”

6)      Medical staff chooses “update”.

7)      The System displays a full form view of the patient record.

8)      Medical scroll up and down the form and update some fields.

9)      Medical staff chooses “submit” feature.

10)   System pops up a message box to confirm with the user to make sure keeping a new copy for this record or not.

11)   Medical assistant chooses yes.

12)   System gives a confirm message and allows to go back to search page for another update action.

13)   The system writes this action, login name and login time into the audit history of that patient record.

 

Successful Post-condition:

The System confirms the action and goes to the page that the medial assistant directs.

Failed Post-condition:

Should no failure. Otherwise bug exists in the system.

Priority:

P3. Low. 2nd round feature.

Branches:

If medical staff selects “logout’ before “submit”, it goes back home page without writing a new record. Else it does.

Source:

2nd client meeting. It is an optional functionality.