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

Marking Death on patient profile #6022

Closed
2 tasks done
aparnacoronasafe opened this issue Aug 7, 2023 · 2 comments · Fixed by #8123 or ohcnetwork/care#2293
Closed
2 tasks done

Marking Death on patient profile #6022

aparnacoronasafe opened this issue Aug 7, 2023 · 2 comments · Fixed by #8123 or ohcnetwork/care#2293
Assignees
Labels
Backend P1 breaking issue or vital feature

Comments

@aparnacoronasafe
Copy link
Member

aparnacoronasafe commented Aug 7, 2023

Is your feature request related to a problem? Please describe.
In CARE an expired patient can be re-admitted in another encounter. This must not be allowed. A patient, once marked dead, the record must not be editable.

Describe the solution you'd like

  • Once the patient is discharged marked as expired, the patient file must not be transferred to another hospital/ must not be able to have another encounter on top of it.
    In the patient transfer form, the dropdown to select patient, an expired patients name should appear disabled (in grey) with "(expired)"added against the name
    Screenshot 2024-07-08 at 10 29 24 AM

  • show a message stating that expired patient data cannot be edited later. In discharge pop-up, when Expired is selected in reason for discharge, change the text "Caution: this action is irreversible" to "Caution: Once a patient is marked as expired, the patient file cannot be transferred or edited. Please proceed with caution". Make this text appear in red colour.

Screenshot 2024-07-08 at 10 33 56 AM

@gigincg Please comment

@rithviknishad
Copy link
Member

@gigincg can we unblock this? seems pretty straight forward.

@nihal467 nihal467 assigned khavinshankar and unassigned gigincg Jul 8, 2024
@nihal467 nihal467 added the P1 breaking issue or vital feature label Jul 8, 2024
Copy link

github-actions bot commented Jul 8, 2024

⚠️ Refrain from assigning this issue to yourself if you have another P1 issue assigned that is not yet closed.
@khavinshankar kindly acknowledge this message by commenting 'Acknowledged' below.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backend P1 breaking issue or vital feature
Projects
Archived in project
5 participants