Describe the bug
Occasionally, after an encounter has been completed, it still appears under the Consultation status instead of transitioning to its Fulfilled state. The issue is intermittent and does not occur for every completed encounter.
To Reproduce
- Go to Surgery healthcare services in JNIMS
- Click on Appointments
- select date 23rd July 2026
- In the section In-Consultation, all 4 patients are completed encounter but somehow display in In-Consultation section.
Expected behavior
Once an encounter is completed, it should no longer appear in the Consultation list. It should move to the appropriate status (i.e., Fulfilled) .
Actual behavior
In some cases, the completed encounter remains in the Consultation list even though the encounter has been successfully completed.
Frequency
Intermittent (does not occur consistently).
Desktop (please complete the following information):
- OS: Windows 11
- Browser Chrome
Additional context
The issue appears to be intermittent and may be related to state synchronization, caching, or delayed status updates between the backend and frontend.
🚨 DO NOT EDIT BELOW THIS LINE 🚨
Instructions for Requesting Assignment:
To request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:
Describe your solution clearly:
Provide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.
Expected Timeline:
- End date: [Expected submission date of a completed Pull Request]
Additional Context:
Include any other relevant context, links, screenshots, or resources that support your proposed solution.
🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.
Describe the bug
Occasionally, after an encounter has been completed, it still appears under the Consultation status instead of transitioning to its Fulfilled state. The issue is intermittent and does not occur for every completed encounter.
To Reproduce
Expected behavior
Once an encounter is completed, it should no longer appear in the Consultation list. It should move to the appropriate status (i.e., Fulfilled) .
Actual behavior
In some cases, the completed encounter remains in the Consultation list even though the encounter has been successfully completed.
Frequency
Intermittent (does not occur consistently).
Desktop (please complete the following information):
Additional context
The issue appears to be intermittent and may be related to state synchronization, caching, or delayed status updates between the backend and frontend.
🚨 DO NOT EDIT BELOW THIS LINE 🚨
Instructions for Requesting Assignment:
To request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:
Describe your solution clearly:
Provide a detailed explanation of your proposed solution, including your approach, key implementation steps, and relevant examples or references. Mention any dependencies, assumptions, or risks you foresee that might affect your timeline or implementation.
Expected Timeline:
Additional Context:
Include any other relevant context, links, screenshots, or resources that support your proposed solution.