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

Error Page When Viewing Appointment details of a patient via Organization . #11266

Open
Vikaspal8923 opened this issue Mar 12, 2025 · 1 comment
Labels
needs-triage question Further information is requested

Comments

@Vikaspal8923
Copy link
Contributor

Vikaspal8923 commented Mar 12, 2025

Describe the bug
When accessing the system via an organization, navigating to the Patients tab, selecting a patient, and then clicking on View Appointment for any of their appointments, an error page appears instead of displaying appointment details.

When accessing a patient through the Organization → Patients tab, there is no facility_id available in the URL or context.
Since the backend requires facility_id to fetch appointment details, this results in an error when trying to view an appointment details

To Reproduce
Steps to reproduce the behavior:

1.Go to the Organization .
2.Click on the Patients tab.
3.Select any patient from the list.
4.Navigate to the Appointments section for that patient.
5.Click on View Appointment for any listed appointment.
6.Observe that an error page is displayed instead of the appointment details.

Expected behavior
The system should correctly display the appointment details instead of an error page.

Screenshots

20250312-1944-34.3821201.mp4

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.


🚨 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.

@Vikaspal8923
Copy link
Contributor Author

Vikaspal8923 commented Mar 12, 2025

@Jacobjeevan @rithviknishad Sir, when navigating to the appointment tab of a patient through an organization, we do not have the facility id, which prevents us from viewing the appointment details when clicking on "View" in the appointment list. currently, fetching appointment details requires both the facility id and the appointment id. However, since we access the patient through an organization, the facility id is missing.

To resolve this, we have three possible approaches:

  1. Backend Modification: Update the backend to allow fetching appointment details using either the facility id or the organization id. although it is not a good approach.
  2. Frontend Adjustment: When clicking on a patient card to navigate to the Patient Details page, we can redirect to the following URL format: /facility/{facility_id}/patient/{patient_id} instead of: /patient/{patient_id} . but this also need one backend modification that when we send data of patients in patients tab we also have to include facility id of each patient ddetails. so that we add that facility id in the route . i think second approach will be better from first as it need less change in backend .
  3. If modifying the backend is not feasible, we can disable the "View" button when accessing the appointment tab through the organization route to preventing users from attempting to fetch appointment details without a facility id.

if this is valid issue then i want to work on this issue . although only these approch come in my mind currently .but if there is other approch please let me know .

@github-actions github-actions bot added needs-triage question Further information is requested labels Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant