jivesh / pe Goto Github PK

Feature problem

To add an appointment, one needs to know both the patient index as well. For a clinic employee with many patients and many doctors, the flow would be:
(assuming they start on patients page)

1. find PATIENT_NAME -> because if list is too long, it's too slow to manually scroll and find
2. Remember the patient index
3. toggle -> to show the doctors page
4. find DOCTOR_NAME -> same if doctor list is too long
5. Then do appt -a p/PATIENT_INDEX d/DOCTOR_INDEX s/DATE_AND_TIME

This collectively is very taxing when creating appointments on the regular - users can't be expected to remember indexes so easily

Steps to reproduce

1. Enter appt
   

Problem

The correct format is -d INDEX_OF_APPOINTMENT, not -dINDEX_OF_PATIENT. Any clinic employee who sees this will be misled on two levels:

1. Their delete initially won't work because of the lack of spacing
2. They will delete the wrong appointment because they think they need to use the index of patient.
   This is a major bug, since it might result in the loss of data (ie deleting the wrong appointment)

Steps to reproduce

1. add n/John Doe hp/98765432 eml/[email protected] a/John street, block 123,#01-01 dob/25/12/1999
2. add n/John Doe hp/98775432 eml/[email protected] a/John street, block 123,#01-01 dob/25/12/1999

Problem

For a busy clinic employee, they might easily make typos in one field. The application will then think that the typo is an indication that a different patient is being added. This can cause many duplicates in the clinic's system. This is a major feature flaw. If almost all the fields are the same except for one minute difference, then there is duplication.

Below is the DG description of the Edit Appointment command.

While it is correct that the command accepts at least one of the stated parameters, it omits that it is necessary for the first parameter to be a valid index.

Steps to reproduce

1. Enter appt -a
2. Observe the error message

Problem

Extraneous git after s/DATE_AND_TIME

Steps to reproduce

1. Enter the command add n/Bjørn hp/98238134 eml/[email protected] a/Sweden dob/12/12/2000

Problem

Both the user guide and the error message states that fields should accept only alphanumeric characters. The letter ø does count as alphanumeric, albeit not in English. However, nowhere in the app is it specified that fields are restricted to English alphanumeric characters. So, this ends up as unexpected behaviour.

Steps to reproduce

1. add n/John Doe hp/98765432 eml/[email protected] a/John street, block 123,#01-01 dob/25/12/1999
2. add n/john doe hp/98765432 eml/[email protected] a/John street, block 123,#01-01 dob/25/12/1999

Problem

When dealing with patients or doctors, it does not make sense to be case-sensitive when dealing with names. Nowhere in the user guide is it specified that when adding, the name field is case-sensitive. Busy clinic employees will be slowed down because different cases might cause duplication.

Steps to reproduce

1. Enter appt

Problem

Both the instructions for filtering all appointments as well as upcoming appointments omit the space after the flag, so clinic employees will face problems when they follow the correction in the error message.

Hard to see the labels on the diagram.

This use-case needs a toggle between the patient and doctor state, which is omitted here.

Test

Screen Recording 2021-11-12 at 4.31.22 PM.mov

Steps to reproduce

1. Open the application.
2. If Patients window is open, try clicking Doctors tab. If Doctors window is open, try clicking Patients tab.

Problem

While the app is supposed to be optimized for fast typers, it is jarring to the user experience when alternate tabs, which tend to be clickable in every application in day-to-day life, are not clickable.