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

Push score is not working properly in the critical care page of patient consultation page #3917

Closed
7 tasks
nihal467 opened this issue Nov 1, 2022 · 2 comments · Fixed by #3952
Closed
7 tasks
Assignees

Comments

@nihal467
Copy link
Member

nihal467 commented Nov 1, 2022

Describe the bug

  • Currently, the push sore are only been inputted in to the critical care section and it is not been reflected anywhere in the platform
  • when the patient as a push score of 12, the platform is showing a input of 1
  • once the part is selected and the pop-up comes in, the whole page become still and unable to scroll up or down the page
  • there is no way to proper see, the inputted data in the summary page

To Reproduce

https://deploy-preview-3914--care-net.netlify.app/facility/a658232e-254e-4fc1-88ac-3cde14f5da49/patient/7550498c-1c9f-4d80-9d73-98730e65160a/consultation

Expected behavior

image

  • change the badges from 1 to the push score of the patient

image

  • in the summary page, when someone hover over the body part, the inputted field along with push score value come as a pop-up

image

  • in the critical care form, when the pop-up arrive to input data, it should not freeze the page, and we should be able to scroll up and down the page
@nihal467 nihal467 changed the title Pressure summary page is not working properly in the critical care page of patient consultation page Push score is not working properly in the critical care page of patient consultation page Nov 1, 2022
@khavinshankar khavinshankar self-assigned this Nov 1, 2022
@nihal467 nihal467 removed the blocked label Nov 1, 2022
@github-actions
Copy link

Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, @aparnacoronasafe, This issue has been automatically marked as stale because it has not had any recent activity.

@github-actions github-actions bot added the stale label Nov 16, 2022
@nihal467 nihal467 removed the stale label Nov 17, 2022
@nihal467
Copy link
Member Author

a pr is been linked to the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants