Skip to content

C1 UC2 Maintain Patient

Antonio Carvalho edited this page May 11, 2017 · 7 revisions

Version 0.3

Version Author Modification Date
0.1 Flávio / Leonardo Document created and C1UC2 added 29/03
0.2 Antonio / Flávio / Varley Simple and complete form and seach flow 12/04
0.3 Antonio Carvalho Update user case 11/05

C1UC2 - Maintain Patient

1. Brief Description

This use case describes how the Clinic Worker uses the System to manage the patient (animals) records.

2. Actors

  • Clinic Worker

3. Preconditions

3.1. The worker needs to be logged in on the system.
3.2. The worker must be accessing an Owner's page.

4. Basic Flow of Events

  1. The system shows all of the patients registered and the option to register a new one.

5. Alternative Flows

5.1. Worker wishes to register a patient

If in the step 1 of the basic flow, the worker wishes to create a new register:

  1. The worker selects the option to register a new patient.
  2. The system shows the patient registration form.
  3. The worker inserts the patient's name, species, breed, size, gender, birthday and coat.
  4. The system presents an option to either Register or Cancel the registration.
  5. The worker selects the Register option.
  6. The system displays a confirmation message.
  7. The worker confirms the registration.
  8. The system lists the form filled and the bath and grooming, vacination and appointment buttons.
  9. The use case ends successfully.

5.2. Worker wishes to update a patient.

If in the step 1 of the basic flow, the worker wishes to update one of the existing registrations:

  1. The worker selects the Update option on the desired patient's file.
  2. The system jumps to step 3 of the register form.

5.3. Worker wishes to delete a patient.

If in the step 1 of the basic flow, the worker wishes to delete one of the existing registrations:

  1. The worker selects the Delete option on the desired patient's file.
  2. The system displays a confirmation message.
  3. The worker confirms the operation.
  4. The user case ends.

5.4 Worker wishes to search a patient

If in the step 1 of the basic flow, the worker wishes to search an existing register:

  1. The worker search the patient name that he wants to see.
  2. The system open the patient form.
  3. The user case ends.

6. Invalid Alternative Flows

6.1 Missing information

6.1.1 Simple form

If in the step 3 of the basic register simple form flow the user miss any information and try to save the register:

  1. The system shows a message saying that for fields name, species and breed are required to accomplish at least the simple patient record.
  2. The system return to step 3.

6.1.2 Complete form

If in the step 3 of the basic register complete form flow the user miss any information and try to save the register:

  1. The system shows a message saying that for fields name, species, breed, size, gender, birthday and coat are required to accomplish the complete patient record.
  2. The system return to step 3.

7. Post-conditions

7.1. Successful Completion

The patient has been successfully registered and the system logs have been updated.

7.2. Failure Condition

The logs have been updated accordingly.

8. Special Requirements

[SR:C1UC2-1] - The System shall keep a log with the Worker that performed the registration, the patient that was registered, the date and time of the registration. SR: Special Requirement.

Clone this wiki locally