nus-pe-bot
commented
5 years ago Team's Response
Thanks for reporting.
It is unlikely for a real world patient to share the exact full name with another patient, but on the off chance, we should be prepared for that. The Person implementation in the underlying structure does not allow us to easily uniquely identify a dataset, hence the limitation of only having the name to work with as a new appointment.
An additional problem that has been reported regarding this is the inability to add more than one appointment, be it Reminder or Follow-up, with the same text. This is also due to the data structure (HashMap) that saves the appointments to the user preference, which is inherited from the underlying application structure.
We will add a note under the User Guide that Appointments have to have a unique text string in the interim, ahead of the v2.0 update that will account for this.
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Medium].
Originally [severity.High].
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
:question: Issue type
Team chose [type.FeatureFlaw].
Originally [type.FunctionalityBug].
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
Users are not allowed to add appointments for patients with the same name but different details. This is a problem as doctors can have patients with the same names and may need to do follow-up for both patients separately.