soc-pe-bot
commented
7 months ago Team's Response
Under Guidelines for the dev team to follow when triaging PE bugs in PE Preparation, Restrictions, it is noted that such symbols should be allowed if the app is expected to match the legal name of the person:
In MediSync, there are no requirements for a legal name. It is purely meant for the user to track Nurses, Doctors, and Patients under their own accord. In retrospect, we can look to allow the lifting of this restriction in the future so that there can be more flexibility for users.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: I must respectfully disagree with your response regarding the restrictions on name inputs in the MediSync application. The decision to not allow special characters or non-Latin scripts, such as Chinese characters or the common Indian notation 's/o' (son of), overlooks a critical aspect of usability of your application.
Firstly since your target group is on Head nurses in hospitals and did not specify the context of which country or size of hospital. It is fair to assume that your application should be able to serve the purpose of all hospitals of any sizes (especially since your application is able to organize nurses and doctors into specializations anyways so it seems that the dev team intended the application to be used on quite a large scale). In such diverse environments, encountering names with special characters or non-Latin scripts is common and should be expected. By not accommodating these variations, MediSync may fail to meet the basic needs of accurate and inclusive record-keeping in many healthcare settings.
Secondly, in the medical profession, the precise identification of individuals is paramount. In a hospital or medical setting, the use of full and accurate names is not just a formality but a crucial requirement. Nurses and doctors often encounter patients with the same or similar names. The need to use full legal names, including those with special characters or non-Latin scripts, is essential for reducing the risk of misidentification, which can have serious consequences in healthcare. Hospitals routinely encounter patients from diverse backgrounds (especially with tourist patients), and it's essential to accurately record their names to avoid mix-ups and ensure proper care. This is particularly important in environments like Singapore, where multiculturalism is the norm, and names often include special characters or non-Latin scripts.
The purpose of MediSync, as you’ve described, is to track Nurses, Doctors, and Patients. In real-world usage, this tracking would inevitably involve dealing with a variety of names that don't conform to a restrictive naming standard. By not accommodating these names, the application limits its usefulness and fails to meet the realistic needs of its users. Considering the intention for MediSync to be used in different countries and by users of varied backgrounds (due to its target group stated in both UG and DG), there is a need for the application to support legal names , which include supporting special characters and names in other languages.
In fact, I am sure that no matter which hospital you go to, medical professionals universally refer to patients using their full names. This practice is not a mere formality but a critical aspect of patient care and safety. Any medical professional will tell you that the accurate and complete recording of a patient's name is paramount in healthcare settings. This is to avoid misidentification and clarity and consistency across various departments and services within the hospital. Hospitals also have legal and ethical obligations to maintain accurate patient records. Inaccurate or incomplete naming could lead to legal complications and breaches of patient rights. Thus, Medisync, if intended to be built to aid head nurses in management, must be able to support legal names of all formats.
Hence, since not supporting legal names in the medical profession is a major inconvenience to users as stated above. Thus, this should still be a Feature Flaw.
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.High`] - [x] I disagree **Reason for disagreement:** The dev team did not provide any justification on why the severity should be lowered. As argued from my previous text related to this bug, the target group is on **Head nurses in hospitals** and did not specify the context of which country or size of hospital. It is fair to assume that your application should be able to serve the purpose of all hospitals of any sizes (especially since your application is able to organize nurses and doctors into specializations anyways so it seems that the dev team intended the application to be used on quite a large scale). In such diverse environments, encountering names with special characters or non-Latin scripts is common and should be expected. The inability to accurately record these names due to restrictive input limitations is not a rare occurrence but a frequent challenge that directly impacts the core functionality of the application. By not accommodating these variations, MediSync may fail to meet the basic needs of accurate and inclusive record-keeping in many healthcare settings. I must respectfully disagree with the decision to classify the issue of restrictive name inputs in the MediSync application as a low-severity bug. Given the application's target user base and the global nature of healthcare, this issue warrants a higher severity rating. Considering the application is designed to organize nurses and doctors and track patients, the accuracy and inclusivity of name inputs are crucial. The restriction on special characters and non-Latin scripts could lead to significant operational issues in hospitals, affecting patient identification and care coordination. This issue goes beyond occasional inconvenience; it fundamentally compromises the application's usability in diverse healthcare settings, making it almost unusable for a significant portion of its intended user base. Inaccurate or incomplete recording of patient names can lead to serious safety concerns in healthcare settings, including the risk of misidentification and errors in patient care. This elevates the issue from a minor inconvenience to a major safety concern, impacting the integrity and reliability of the application in a medical environment. Given these considerations, the severity of this issue should be reassessed. It is not merely a low-severity flaw but a significant concern that affects the application’s usability, safety, and adaptability in a global healthcare context. I strongly suggest reclassifying this as a high-severity bug, reflecting its substantial impact on most users and the potential major problems it can cause. Since most head nurses cannot effectively manage their patients, doctors and nurses without the functionality of supporting a diverse format of names (especially considering that there are tourist patients as well) , I find that the application is unusable for the intended target group if it does not support legal full names and thus is still determined that this bug is of severity high. In fact, I am sure that no matter which hospital you go to, medical professionals universally refer to patients using their full names. This practice is not a mere formality but a critical aspect of patient care and safety. Any medical professional will tell you that the accurate and complete recording of a patient's name is paramount in healthcare settings. This is to avoid misidentification and clarity and consistency across various departments and services within the hospital. Hospitals also have legal and ethical obligations to maintain accurate patient records. Inaccurate or incomplete naming could lead to legal complications and breaches of patient rights. Thus, Medisync, if intended to be built to aid head nurses in management, must be able to support legal names of all formats. 
Names cannot be chinese names or with special characters is very unrealistic for the application to be used for different countries (since ur target group is not specified) and patients that come from overseas
especially this case as singapore as indians with that