Step 1. Added new patients with identical other fields, the exceptionn was the name was lowercase (any character can be lowercase, meaning there are no.character ^ 2) ways of storing the same name
Step 2. Tried identifying a john as in I was a the front desk and am unable to locate the correct john, have to ask other detail to identify
Step 3. Other details allow duplicates, not reliable way of finding the records
There needs to be an identifying attribute that can have no duplicates. Name is a scenario where it must be case sensitive to accurately identify, especially for something importent like medical records.
This issue is known and can be solved with the addition of NRIC and MRC fields for patients and specialists respectively as mentioned in the "Planned Enhancement" section of the DG.
Step 1. Added new patients with identical other fields, the exceptionn was the name was lowercase (any character can be lowercase, meaning there are no.character ^ 2) ways of storing the same name
Step 2. Tried identifying a john as in I was a the front desk and am unable to locate the correct john, have to ask other detail to identify
Step 3. Other details allow duplicates, not reliable way of finding the records
There needs to be an identifying attribute that can have no duplicates. Name is a scenario where it must be case sensitive to accurately identify, especially for something importent like medical records.
[original: nus-cs2103-AY2324S1/pe-interim#1737] [original labels: severity.Low type.FeatureFlaw]