Skip to content

Facility Doctors Missing, Archived Users Visible & No Recent Activity Sorting in Doctor Connect (TeleICU) #73

@santhosh-devale

Description

@santhosh-devale

Describe the bug
In the Doctor Connect module of care 3.0 , multiple issues are affecting the doctor/user selection experience:

Facility doctors are not visible
Deleted or archived users are still appearing in the dropdown
Recent active users are not prioritized (regression from care 2.0)

Previously in care 2.0, recently active users were shown at the top, helping stakeholders quickly identify active vs inactive doctors or nurses. This behavior is missing in care 3.0.

To Reproduce
Steps to Reproduce

Navigate to Doctor Connect
Open the doctor/user dropdown list
Observe the list of users and their order

Expected behavior
Facility doctors (on-site doctors) should be visible
Deleted/archived users should be excluded
Users should be sorted by recent activity (most recent first), similar to v2.0

Screenshots
https://drive.google.com/file/d/1BKR0kjrfUMefU-H4iBJVNd6PE9XSi7dP/view?usp=drive_link

https://drive.google.com/file/d/1aIDFNz9dUh1dgmKR1Hbm9JlYDMR9tnrF/view?usp=drive_link

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.

Metadata

Metadata

Labels

Type

No fields configured for Bug.

Projects

Status
Testing / Approval

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions