-
Notifications
You must be signed in to change notification settings - Fork 486
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
Able to create daily round update without a bed assigned through patient details page but not through consultation dashboard #7132
Comments
I want to work on this. Please assign this to me. |
@rithviknishad I'd like to handle this issue. Could you please assign it to me? I'll ensure the "Add consultation updates" button is appropriately disabled for active consultations without a bed assigned. |
Hey @younome71 any updates on this? |
@rithviknishad I was facing some issues initially setting up the environment, which got resolved just now. Will update shortly about the progress |
@rithviknishad Do it need to disallow as in show an error ? Or Remove the button itself if there is no bed assigned? |
same behaviour as how its there when we click log update from consultation dashboard. Show error notification and open bed assign dialog |
Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, @aparnacoronasafe, This issue has been automatically marked as stale because it has not had any recent activity. |
@rithviknishad I have created a PR on this issue #7303. Please review it! |
Describe the bug
When a consultation has no bed assigned, we are restricted from filing a log update if there is no bed assigned if the "Log update" button is clicked from the consultation dashboard.
However, if we go to the patient details page and click "Add consultation updates" we can still access the daily round form and we can file a Daily Round log update successfully. This should not be allowed.
Expected behavior
Disallow "Add consultation updates" button for active consultations without a bed assigned.
Screenshots
The text was updated successfully, but these errors were encountered: