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

Discharge diagnosis #8299

Closed
4 tasks
aparnacoronasafe opened this issue Aug 13, 2024 · 6 comments · Fixed by #8390
Closed
4 tasks

Discharge diagnosis #8299

aparnacoronasafe opened this issue Aug 13, 2024 · 6 comments · Fixed by #8390
Assignees

Comments

@aparnacoronasafe
Copy link
Member

Is your feature request related to a problem? Please describe.
When a patient is admitted, the diagnosis is marked by the doctor usually at the time of first consultation. This is then revised multiple times through the admission. Both the diagnosis itself or the diagnosis type alone may be updated during the term of admission.

It is important to prompt the user to update the diagnosis for a final time right before discharge.

This is important since the patient may not be completely disease-free at discharge. He may simply be free of the life-threatening condition but may still have many underlying chronic illnesses for which the doctor may have suggested some medication in the discharge prescription field.

Describe the solution you'd like
For an encounter with "Admission", based on the discharge reason, make the following edits in the discharge pop-up

  1. RECOVERED
  • Add a section for 'Diagnosis at discharge'- show the latest list of diagnoses (along with type) and allow user to make changes
  • reorder the form in the following way
  • Reason
  • date and time of discharge
  • Diagnosis at discharge
  • Discharge prescription
  • Discharge advice
  1. REFERRAL
  • Add 'Diagnosis at discharge' below date and time of discharge - show the latest list of diagnoses (along with type) and allow user to make changes
  1. LAMA
  • Add 'Diagnosis at discharge' below date and time of discharge - show the latest list of diagnoses (along with type) and allow user to make changes

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@JOSHIK27
Copy link
Contributor

I would like to work on this issue if the submission of the new field i.e 'Diagnosis at discharge' is handled by the backend api endpoint [ /api/v1/consultation/{id}/discharge_patient/ ] @rithviknishad

@rithviknishad
Copy link
Member

rithviknishad commented Aug 21, 2024

Yes @JOSHIK27

However, there's a reusable component EditDiagnosesBuilder. You could simply use that.

To populate it with initial value, you could use the useQuery hook with the pre-defined API route for fetching consultation diagnosis instead of manually calling the specified API.

Creation of new diagnosis entries and updating of existing diagnosis entries is handled automatically by the component itself. No need to write any API calls related logic for it.

@JOSHIK27
Copy link
Contributor

Sure. Thanks

Yes @JOSHIK27

However, there's a reusable component EditDiagnosesBuilder. You could simply use that.

To populate it with initial value, you could use the useQuery hook with the pre-defined API route for fetching consultation diagnosis instead of manually calling the specified API.

Creation of new diagnosis entries and updating of existing diagnosis entries is handled automatically handled by the component itself. No need to write any API calls related logic for it.

@JOSHIK27
Copy link
Contributor

JOSHIK27 commented Aug 21, 2024

Screen.Recording.2024-08-22.at.00.1.mp4

I have added the section 'Diagnosis at discharge' and changed the order as instructed above. I fetched the diagnosis from corresponding end point using useQuery hook as you told @rithviknishad. Let me know if its what you needed.

@rithviknishad
Copy link
Member

Yup! Raise the PR

@JOSHIK27
Copy link
Contributor

Here's the pr #8390 @rithviknishad

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

Successfully merging a pull request may close this issue.

3 participants