Patient Forms and Assignment Flows

[KaustubhK98]

Description

• Fixed issue where the same nurse was appearing twice.
• Fixed crash on the patient details page caused by a null pointer reference.
• Fixed age calculation based on date of birth.
• Added input validations for both Add Patient and Edit Patient pages.
• Improved the UI of the Add Patient page.
• Added Edit Patient functionality and its UI page.
• Added Assign Nurse functionality and its UI.
• Fixed assigned nurse not showing correctly on the Patient Details page, including cases where it displayed “No activities found”.
• Fixed bugs causing inconsistencies in patient portals.

Todos

• Tested and working locally
• Code follows the style guidelines of this project
• I have performed a self-review of my code
• Code changes documented
• Requested review from >= 2 devs on the team (one frontend and one backend recommended)

How to test

1. Run the app locally and log in with a user account that has access to patient and caretaker flows.

2. Test Add Patient:

   • Open the Add Patient page.
   • Try submitting with empty or invalid inputs and verify validation errors are shown.
   • Enter valid patient details and save.
   • Confirm the patient is created successfully.

3. Test Edit Patient:

   • Open an existing patient from the patient list/details page.
   • Use the menu option to open the Edit Patient page.
   • Verify the existing values are pre-filled correctly.
   • Try invalid inputs and confirm validations are shown.
   • Update the patient with valid data and save.
   • Confirm the updated details are reflected correctly.

4. Test Age calculation:

   • Add or edit a patient with a known DOB.
   • Verify the displayed age is calculated correctly from DOB.

5. Test Assign Nurse:

   • Open a patient and use the Assign Nurse option.
   • Assign a nurse from the caretaker flow/profile.
   • Confirm assignment completes successfully.

6. Test Patient Details page:

   • Open the same patient’s details page after nurse assignment.
   • Verify the assigned nurse is displayed correctly.
   • Verify the page no longer crashes due to null data.
   • Verify it does not show duplicate nurses.
   • Verify it does not incorrectly display “No activities found” when a nurse is assigned.

Associated MS Planner Tasks

Patient Forms and Assignment Flows (https://teams.microsoft.com/l/entity/com.microsoft.teamspace.tab.planner/planner.v1.1c7aff73-bd5d-4eaf-844f-a0f0914d35b0_p_obnY9eRGNEGXqjBUOhDWKcgAFWt1?tenantId=d02378ec-1688-46d5-8540-1c28b5f470f6&webUrl=https%3A%2F%2Ftasks.teams.microsoft.com%2Fteamsui%2FpersonalApp%2Falltasklists&context=%7B%22subEntityId%22%3A%22%2Fv1%2Fplan%2FobnY9eRGNEGXqjBUOhDWKcgAFWt1%2Fview%2Fboard%2Ftask%2F8luVWErlNkuuvY932ClKscgANKiu%22%2C%22channelId%22%3A%2219%3A02e7479536e247c5a85093cf6dcaca4c%40thread.tacv2%22%7D)

Known Issues

• No known issues identified at the time of testing.

[Rnk56]

The new version supports alternate field names from the API (user.kt file). The Assign Nurse screen; loads a list of nurses, lets user pick one and sends API request to assign that nurse to a patient (AssignNurseActivity.kt). Further more as described in the description, can confirm that the assign nurse functionality, edit patient functionality and its UI has been added. Correctly implements the Edit Patient flow with validation, age calculation, and update API handling. Overall, the code logic is good. Testing needed locally.

[KudratAroraa]

Approved.

I reviewed the PR and also resolved the final merge-readiness issues from the reviewer side so the branch could be brought into a stable state. The core work in this PR remains the contributor’s feature work around patient forms and assignment flows, and from the scope side it is a meaningful contribution. From my review side, I addressed the remaining cleanup and integration issues needed to make the branch merge-ready, including conflict resolution and final build-related fixes.

At this stage, the intended add patient, edit patient, assign nurse, and patient details improvements are in place, and the branch is now in a much better state for integration. Approving from the reviewer side after validating the latest resolved version.