Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues in the new branch of CARE do deployment #9471

Closed
9 of 11 tasks
nihal467 opened this issue Dec 17, 2024 · 14 comments
Closed
9 of 11 tasks

Issues in the new branch of CARE do deployment #9471

nihal467 opened this issue Dec 17, 2024 · 14 comments
Assignees
Labels

Comments

@nihal467
Copy link
Member

nihal467 commented Dec 17, 2024

Summary Of Features Implemented So Far In New DO Branch

  • Public search for facilities
  • Public facility page
  • Public appointment scheduling
  • Patient login
  • Scheduling and Availability for all resources
  • Services request support for patients
  • Support for dynamic questionnaires
  • HL7 complaint EMR modules for capturing and storing patient data and their views
  • Value set support and Snowmed, Loinc, ICD10 integration
  • A lot of cleanup in facility
  • Removed sample management fully

Workflow's

We are having multiple Workflows in places, use the below link to view bugs in each of them and entire workflow can be viewed using this link

Workflow 1 | Workflow 2 | Workflow 3 | Workflow 4 | Workflow 5 | Workflow 6 | Workflow 7 | Workflow 8 | Workflow 9


Login-Credential

Districtadmin: nihal-admin p/w : Test@123
Doctor: nibras-doctor p/w: Test@123
Nurse: ramya-nurse p/w: Test@123
Volunteer vaishnav-volunte p/w: Test@123

@nihal467 nihal467 changed the title Issues in the new branch of Issues in the new branch of CARE do deployment Dec 17, 2024
@nihal467 nihal467 self-assigned this Dec 17, 2024
@AdityaJ2305
Copy link
Contributor

Hey @nihal467, I’d like to pick up some issues from here. I’ve successfully branched out this branch locally.

@nihal467
Copy link
Member Author

nihal467 commented Dec 17, 2024

Workflow 1

Image


Users Login Page

Image

Major issue

  • The patient login using the phone number OTP is not being generated to the user

Note: the AWS sandbox services we are using require to register the number with the services first, then only the OTP generation will work in the CARE. For now, we can use the static OTP : 45612

  • Login with the static OTP is also not possible

Minor Issue

  • add the translation to the username and password error message in the staff login
  • add the translation to the OTP sent successfully notification for the patient login section

Image

  • Add proper error message for incorrect OTP-based patient login on the homepage

Facility Public Page

Image

Minor Issue

  • The Facility Type advanced filter on the Facility Public Page is not working because the facility type details are not shown on the card. We can either hide the filter or display the facility type details on the card and fix the related filter functionality.

Image

  • the pincode-based search is not working, as well as the pin code are not visible in the facility details page

Image

  • rephrase the sentence properly instructing the user to login

Enhancement

  • Add a back button to the facility public page, which users can use to go back to the initial district selection page
  • Add a login button of the right side top corner, so users can always go to the login page from the public page

Facility Details Page

Image

Minor Issue

  • Only show the doctor users in the facility detail public page for booking appointments, as they are the only users who will be requiring a appointment book (Product Discussion Required)

Enhancement

  • Add support to search the doctor's name / Qualification in the facility details page

Booking Appointment

Major Issue

Image

  • add a validation , to restrict users from deleting existing schedule, if already anyone of the available slots are in use

Image

  • We can use an invalid OTP such as 00000 to login to the appointment portal and register a patient, even though the frontend throws a 400 error, so handle the situation with proper validation and gracefully

Minor Issue

Image

  • Add fine text for age mentioning to the user that, only the year of birth will be saved if they are using the age field

Image

  • Add support to the current address field allowing users to type address in multiple lines

Image

  • Add validation for DD MM YYYY field to check whether each field is having respective number of digits for each input fields

User Details Page

Major Issue

Image

  • When we try to create an availability schedule for a user, without mentioning the weekly schedule, submitting the form crashes the page. Additionally, each time we open the Availability section on the user's detail page of the same user, the page kept on crashing

Image

  • When we try to create a schedule exception for a user, its throwing 404 error in the frontend

Minor Issue

Image

  • Replace the return to care button located under the no home facility icon with Return to Linked Facilities
  • Repositon the icon and button of no home facility so, we can avoid unwanted scroller in this page

Image

  • When there is no exception available for a user, the loader is keep on loading infinitely

Image

  • The weekly schedule field in the create schedule template form is not properly responsive

Image

  • the info card in the session section of create schedule template is not properly responsive

Image

  • the return to CARE button in the crashing page is not redirecting properly to the loginpage

Enhancement

Image

  • Add an option to edit the existing schedule template of the user

Image

  • Use color coding for the dates to clearly indicate their availability status—such as available, fully booked, nearly full, and unavailable—making it easier to understand availability at a glance without needing to click on each date.

@nihal467
Copy link
Member Author

nihal467 commented Dec 17, 2024

Workflow - 2

Image


Appointment Dashboard

Major

Image

  • Multiple schedule API's are failing in the appointment tab and throwing something went wrong in the frontend
  • the appointment dashboard cards are not filtered based on the selected doctor
  • The patient card in the dashboard should display the patient's DOB or age instead of "undefined."

Image

  • when we click on the appointment card, we are being redirected to a patient details page with no info, ideally user should be redirected to a page, where they can view details filled during appointment, view , edit or delete the appointment

Image

  • When we visit the doctor consultation page from the patient details page using the top-right corner button, the slot API fails to load the available slots for the day in the doctor consultation page

Minor

  • Currently, the view remains stuck on the board view and does not switch to the list view, even when attempting to change it.
  • The patient name-based search functionality in the dashboard is not working.

Enhancement

  • The appointment dashboard should allow users to filter the cards based on a date range.
  • Add support for special priority tokens based on factors such as age, post-operation revisits, or any other external reasons.

Patient Consultation Dashboard

Major

Image

  • The symptoms and diagnosis are not displayed on the patient consultation page, even though the data is available.

Image

  • the questionnaire present in the log update is not at all mobile responsive

Image

  • the questionnaire is not closing post-submission of the data

Image

  • Even though the data from the questionnaire is being saved, the related graph and reflections in the Patient Consultation Dashboard are not being populated with the data.

Minor

  • Add missing translations for no observation and no questionnaire

Image

  • We have no individual text box for each nursing care

@nihal467
Copy link
Member Author

nihal467 commented Dec 18, 2024

Workflow 3

Image


Major Issue

  • Add an option to update the resource category in the update details form
  • Add an option to cancel an existing request and add a note column as well to record why are they cancelling it

Minor Issue

Image
Image

  • Replace the colour of the resource request button to use primary colour to keep it consistent with other button
  • Replace the colour similarly in the resource request details page as well

Image

  • Add necessary translation to all options in the resource request form

@nihal467
Copy link
Member Author

nihal467 commented Dec 18, 2024

Workflow 4 {Work in progress}

Image

@nihal467
Copy link
Member Author

Workflow 5

Image

@nihal467
Copy link
Member Author

nihal467 commented Dec 18, 2024

Workflow 6

Image

@nihal467
Copy link
Member Author

nihal467 commented Dec 18, 2024

Workflow 7

Image

@nihal467
Copy link
Member Author

Workflow 8

Image

@nihal467
Copy link
Member Author

Workflow 9

Image

@nihal467 nihal467 added the EPIC label Dec 18, 2024
@rajku-dev
Copy link
Contributor

I would like to work on some of the issues mentioned here. @nihal467

@github-actions github-actions bot added needs-triage question Further information is requested labels Dec 18, 2024
@sanjayh-2022
Copy link

@bodhish , I would like to work on some of the issues in this . Can you please assign me some of the issues to me ?

@modamaan
Copy link
Contributor

@nihal467 i would like to work on Workflow 3

@bodhish
Copy link
Member

bodhish commented Jan 1, 2025

Resolved

@bodhish bodhish closed this as completed Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants