Rework Shifting Process for "Complete" stage

[Ashesh3]

Fixes #7684
Backend: ohcnetwork/care#2114

This pull request includes changes to the Shifting Process for the "Complete" stage. It introduces the ability to set a discharge reason when the status is "PATIENT EXPIRED" or "COMPLETED". Additionally, it adds a new prop disabled to the FacilitySelect component.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
care-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 10, 2024 1:16pm

[netlify]

✅ Deploy Preview for care-egov-staging ready!

Name	Link
🔨 Latest commit	136b82c
🔍 Latest deploy log	https://app.netlify.com/sites/care-egov-staging/deploys/6666fc94a698da0008afb9ef
😎 Deploy Preview	https://deploy-preview-7697--care-egov-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[cypress]

Passing run #2737 ↗︎

0

124

0

0

0

Details:

Rework Shifting Process for "Complete" stage
Project: CARE	Commit: 136b82c10e
Status: Passed	Duration: 02:55 💡
Started: Jun 10, 2024 1:20 PM	Ended: Jun 10, 2024 1:23 PM

Review all test suite changes for PR #7697 ↗︎

[github-actions]

👋 Hi, @Ashesh3,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.

---

This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

[github-actions]

Hi, This pr has been automatically marked as stale because it has not had any recent activity. It will be automatically closed if no further activity occurs for 7 more days. Thank you for your contributions.

[github-actions]

Hi, @coronasafe/care-frontend-maintainers, This PR has been automatically closed due to inactivity. Thank you for your contributions. Feel free to re-open the PR.

[nihal467]

@aparnacoronasafe

• When you are marking a patient complete, the destination facility is mandatory, then only we can successfully discharge a patient in the shifting module
• But at the same time, the referred to discharge pop-up destination facility is an optional field, so it will throw an error, since we are trying to reuse the discharge pop-up here

Similar operation but different approach can be confusing, but can you comment on this issue how to handle it @aparnacoronasafe

[nihal467]

@khavinshankar the validation for shifting form destination facility is skipped, when we mark the complete and submit the form. So modify the PR to ensure that the shifting form validation is passed first then only the discharge pop-up should comes into the screen

[nihal467]

LGTM

[github-actions]

@Ashesh3 Your efforts have helped advance digital healthcare and TeleICU systems. 🚀 Thank you for taking the time out to make CARE better. We hope you continue to innovate and contribute; your impact is immense! 🙌