halfwhole / pe

0 stars 0 forks source link

Visits should really be editable #9

Open halfwhole opened 5 years ago

halfwhole commented 5 years ago

It's a common thing to want to edit your visits after you're done with them (not when they're ongoing), but I don't see a way to do so currently.

nus-pe-bot commented 5 years ago

Team's Response

Good points and I do agree that at first glance it may appear to be a significant feature flaw. However, this has been considered and it is so by design. Allow me to address this.

It’s a common thing to want to edit your visits after you’re done with them (not when they’re ongoing),

You are correct, but we expect that the nurse concludes the inputation of data by the time the visit is over, especially if she records data as she collects it during the visit. If need be, she can spend some time inputting the data before concluding the session, or for awhile after the session has concluded. The visit end date time does not need to be precise down to the second; so long as it can provide a rough estimation of when the visit ended, it is sufficient for its purposes.

The nurse should not be inputting data beyond this point, because it would mean that she is inputting data from her memory, which can result in inconsistencies or errors in the data. We want her to input the data as she is collecting it, or at least immediately after doing it.

This is consistent with how most healthcare professionals operate. Assume you visit a doctor, a physician or a psychiatrist; in each scenario, they will record the information during the session. Maybe they will continue typing even after you have left the room, but there is no reason for any of these healthcare professionals to suddenly decide "Oh, let me make some changes to the session data," an hour after the session has concluded. This is the same use case for our community nurses. The fact that they are mobile and visit the patients (instead of the patients visiting the doctor) does not change this use case.

It’s quite common however in practice for visits to only be entered after the actual visitation was done (it’s how many volunteers operate in real life).

As mentioned earlier, the application necessitates that the visit is recorded while it is ongoing to ensure data integrity. Nurses are not allowed to enter or modify data too long after the visit has occured to prevent memory errors (of the nurse) from occuring. This helps to ensure the correctness of any data recorded in these visit records. This is the reason why we have a checklist in the application: for nurses to check off items that they have to do, and use the application during the visit itself.

One reason why you might assume that many volunteers enter visit data after the visit is done is that they use desktops. In our case, the community nurses intend to use it on a laptop or any other mobile device that allows the nurse to use it while at the patient's home, rather than a desktop (See https://github.com/AY1920S1-CS2103-F10-1/main/issues/28).

It is for this reason that we do not allow the nurse to edit or delete any visit records, firstly to prevent these kind of memory errors introduced by the nurse, and secondly to ensure that any wrongdoings / mistakes performed by the nurse is also recorded and not erasable by the nurse. This is to ensure quality of service to the patients.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: [replace this with your reason]