RyanNgWH / pe

0 stars 0 forks source link

User is not able to easily identify the participants in an appointment #13

Open RyanNgWH opened 2 months ago

RyanNgWH commented 2 months ago

image.png

Currently, only the NRIC of both patients and doctors are shown in the appointments. This might not be ideal as users would then be required to search for who the NRIC belongs to find the information about the patient or doctor.

Additionally, there is no way to search the contacts based on NRIC as only name searching is available and would be an inconvenience to the user.

Considering the scenario that the user would like to call the patient to remind them of their appointment, they would have to:

  1. Find the appointment
  2. Record down the NRIC of the patient
  3. List all patients in the application
  4. Manually match the NRIC to the list of patients

This would be very troublesome to the user, especially if there is a large number of patients which is highly possible for an application targeted at hospital management.

nus-pe-script commented 2 months ago

Team's Response

Thank you for bringing this up. Indeed, it would be an enhancement if we could show other information about the patient rather than just the NRIC. However, as it currently stands, the MediCLI app still functions as intended and hospital clerks can quickly find appointments with either the doctor's NRIC or the patient's NRIC.

Consider the scenario where a patient is checking with the hospital if an appointment has been made. The patient would call up the hospital clerk and the hospital clerk would ask the patient for their NRIC. A simple query command using the apptforpatient folllowed by the NRIC would suffice. Of course, if the doctor wanted to see whether a patient has an appointment with him without knowing the patient NRIC, the hospital clerk would need to do a patient query command first to get patient NRIC, followed by the apptforpatient command.

Whilst we do believe that the enhancement would make the MediCLI app even more efficient, we find that this is not too big of an issue in this version of the app (it is something we can include in the next version) and thus believe this is a NotInScope issue.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your explanation]