Add Consultation button is disabled after patient is discharged

[yash-learner]

Describe the bug
Can not add a consultation via UI after a patient is discharged as the Add Consultation button is disabled. It is can be still accessed via visiting the route.

To Reproduce
Steps to reproduce the behavior:

1. Go to patient with a consultation. - Visit consultation page
2. Click Manage Patient
3. Click Discharge from Care
4. Now, you can notice Add consultation button is disabled but you can still access the route.

Expected behavior
I think the button should be enabled and should be possible to add a new consultation.

Screenshots
If applicable, add screenshots to help explain your problem.

add_consultation_button_is_disabled.mp4

[Rishith25]

Can I work on this

[yash-learner]

@rithviknishad @Jacobjeevan 👆

[nihal467]

@yash-learner It is an expected behavior, once a patient is discharged, without readmission we shouldn't allow new consultation

[Sancharisingh]

Hello @nihal467
I noticed that the 'Add Consultation' button is disabled after a patient is discharged. Since this behavior is marked as expected, could you clarify if:

Is this the feature's final behavior, or is it still a work in progress?
Are there any specific conditions under which this functionality might change?
Thanks.

[Rustix69]

I would like work on this, if that's okay. And can you clarify the expected behavior.

[SwanandBhuskute]

I would like to work on this issue @rithviknishad @nihal467 , pls assign me

[rithviknishad]

As discussed, the "Add consultation" button has no use based on the following:

When a patient is registered to a facility, and a consultation has yet to be created, the "Create Consultation" banner present in "no consultation filed" is sufficient.
For re-admission purposes, there exists a workflow to properly validate a patient through the Add Patient Details form itself by matching the phone number and date of birth. Hence this "Add Consultation" button serves no use.

So we can remove "Add Consultation" button to avoid confusion.

cc: @nihal467