\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to '...'\n2. Click on '....'\n3. Scroll down to '....'\n4. See error\n\n**Expected behavior**\nA clear and concise description of what you expected to happen.\n\n**Screenshots**\nIf applicable, add screenshots to help explain your problem.\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],13636,"Bug : caret icon shown in collapsed sidebar in Patient sidebar","2025-09-07T16:00:24Z","https://github.com/ohcnetwork/care_fe/issues/13636",0.75244313,{"description":3194,"labels":3195,"number":3196,"owner":3178,"repository":3179,"state":3180,"title":3197,"updated_at":3198,"url":3199,"score":3200},"**Describe the bug**\n\n- [ ] Issue 1: Active Tab Not Highlighted in Expanded Sidebar: When the sidebar is in an expanded state, and a user selects a sub-tab (e.g., Locations under Settings) and then closes the sub-tab view, the parent tab (Settings) does not show as active.\nThis behavior works correctly in the collapsed sidebar state, but not when expanded.\n\n- [ ] Issue 2: Active Tab Missing in Sub-Sub Navigation: When navigating into deeper nested levels (e.g., clicking on Encounters, then selecting a specific Patient Encounter), the active tab highlighting is lost. The sidebar fails to show the current tab or section as active, leading to confusion about the current context.\n\n- [ ] Issue 3: Both Product and Product Knowledge being shown as active in-closed sidebar when you select 'Product Knowledge'.\n\n> Note: Refer to the attached screen recording for a visual demonstration of both issues.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\nFor Issue 1:\n\t1.\tEnsure the sidebar is in expanded state.\n\t2.\tClick on Settings, then select Locations (or any sub-item).\n\t3.\tClose the sub-tab view.\n\t4.\tObserve that Settings is no longer highlighted as active, even though you’re still in a Settings-related route.\n\nFor Issue 2:\n\t1.\tClick on Encounters.\n\t2.\tSelect any Patient Encounter from the list.\n\t3.\tObserve that no tab is highlighted in the sidebar, even though you’re inside the Encounters module.\n\nFor Issue 3:\n\t1.\tClick on setting while the sidebar is closed.\n\t2.\tSelect 'Product Knowledge'\n\t3. Observe that both product and Product Knowledge being highlighted.\n\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/63b5feee-2e03-4676-88a1-41dde698e67c\n\n\u003Cimg width=\"443\" height=\"474\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3591c71d-096c-4dd7-8978-eb77b02620b3\" />\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],12097,"Sidebar Active Tab Highlight Issues in Expanded and Nested Views","2025-08-02T09:20:36Z","https://github.com/ohcnetwork/care_fe/issues/12097",0.7533716,{"description":3202,"labels":3203,"number":3206,"owner":3178,"repository":3179,"state":3180,"title":3207,"updated_at":3208,"url":3209,"score":3210},"**Is your feature request related to a problem? Please describe.**\nCurrently, the encounters in the \"ALL STATUS\" which is circled red in the shared picture below, are not sorted. As a result, nurses have to scroll through the entire list to locate an active patient, especially if the patient has been in the ICU for a long time. While this may be manageable for us, it adds unnecessary extra work for the nursing staff.\n\n**Describe the solution you'd like**\n1. Active patients should always be displayed at the top, irrespective of their creation date.\n2. Completed encounters, which are marked yellow in the shared picture, should always be displayed below the active ones.\nThis will make it easier for nursing staff to quickly locate and manage active cases.\n\n**Additional**\nThere are options to view the encounters separately based on their status, which are highlighted in green in the shared picture. However, by default, the first page that opens is the \"ALL Status\" view, and requiring one extra click adds unnecessary effort for the nursing staff.\n\n**Screenshot**\n\u003Cimg width=\"1812\" height=\"880\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/9f05ffae-4e9c-473d-bb59-21416b9e0b98\" />\n\n\n@gigincg \n---\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[3204,3205],{"name":3172,"color":3173},{"name":3175,"color":3176},13372,"Sorting Encounters","2025-08-18T08:08:01Z","https://github.com/ohcnetwork/care_fe/issues/13372",0.75794196,{"description":3212,"labels":3213,"number":3214,"owner":3178,"repository":3179,"state":3180,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### Description\nDesign and document an Avatar component to be added to the Design System with the following requirements:\n\n#### Shape Usage Guidelines\n\n1. Patients – Rounded rectangle avatar\n2. Healthcare staff – Circle avatar\n3. Facility – Squircle avatar (preferred, but check with dev.)\n\n> **Squircle Implementation Notes:**\n> Confirm with dev team if squircle can be implemented using SVG clip-path or CSS mask-image.\n> Ensure compatibility with mobile browsers.\n> If not feasible or reliable across browsers, fallback to rounded rectangle for Facility avatars.\n\n\n**Fallback Behavior**\nIf no profile image is available: Show two-letter initials (first letter of first & last name).\n\n**Checklist**\n- [ ] Avatar component added to the Design System with all three shape options.\n- [ ] Usage guidelines documented in Figma and design documentation.\n- [ ] Dev feasibility check for squircle completed and decision documented.\n- [ ] Link Figma component to the Design System library",[],13344,"Add Avatar Component – Shape Variations, Usage Guidelines & Fallbacks","2025-08-12T05:42:47Z","https://github.com/ohcnetwork/care_fe/issues/13344",0.77285576,{"description":3220,"labels":3221,"number":3222,"owner":3178,"repository":3179,"state":3180,"title":3223,"updated_at":3224,"url":3225,"score":3226},"**Description**\nThis issue addresses UI inconsistencies in the Patient Tag drop down menu of \"Add Patient Details\" page:\n\n- Tag Menu Dropdown: The height of the search input as well as the menu items need to be adjusted to align with our design system.\n\n- Keyboard Shortcuts: The size of the keyboard shortcuts is inconsistent and needs to be fixed.\n\n- The padding for each tag option within the dropdown should be consistent with the provided Figma file, ensuring proper alignment and spacing.\n\n**Steps to Reproduce**\n\n1. Navigate to Add Patient's details page.\n\n2. Scroll down to the Patient Tags field.\n\n3. Open the dropdown menu.\n\n4. Observe the current option height.\n\n**Expected Behaviour**\n\n- The tag menu dropdown should adhere to the following specifications:\n\n - The search input field at the top of the dropdown should have a fixed height of 40 pixels.\n\n - The padding for each tag option within the dropdown should be consistent with the provided Figma file, ensuring proper alignment and spacing. \n\n- Keyboard Shortcuts\n\n - The size of the keyboard shortcut indicators should match the design specifications. They currently appear smaller than intended. \n\n- Add a secondary button to complete the action.\n\n\n**Visual Reference**\n\n\u003Cimg width=\"752\" height=\"710\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/23009867-03c6-44c4-acd4-4adfbffcb3d4\" />\n\u003Cimg width=\"743\" height=\"705\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7f098772-6e61-4754-a5e5-b94b509b11fb\" />\n\u003Cimg width=\"730\" height=\"636\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/990db087-0e47-4f6d-83b5-b90be8ac1d0a\" />\n\n**Proposed Solution**\nAttached screenshot for reference\n\u003Cimg width=\"1110\" height=\"1210\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/94e1fa1c-2e40-48f9-a230-14043a90198d\" />\nRefer the figma file for the correct dimensions https://www.figma.com/design/Z93EYKSa1MdBmXndsMBJSQ/Care?node-id=26304-10329&t=AskluDORl8G3ixs5-1\n\n---\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[],13732,"Enhance usability by solving the UI inconsistencies on the \"Add Patient Details\" page","2025-09-17T11:43:03Z","https://github.com/ohcnetwork/care_fe/issues/13732",0.7735495,{"description":3228,"labels":3229,"number":3236,"owner":3178,"repository":3179,"state":3237,"title":3238,"updated_at":3239,"url":3240,"score":3241},"**Is your feature request related to a problem? Please describe.**\nCurrently, on the encounter listing page:\n\n1. Clicking the patient name navigates to the patient’s profile.\n\n2. Clicking the \"View Details\" button navigates to the encounter details.\n\nHowever, this behavior is not immediately intuitive for users. It would be clearer and more user-friendly to have explicitly labeled buttons for both actions.\n\n**Describe the solution you'd like**\nAdd two clearly labeled buttons for each encounter row:\n1. \"Visit Patient Profile\"\n2. \"Visit Encounter Details\"\n\nUse icons or color differentiation (optional) to help users quickly recognize actions.\n\n**Describe alternatives you've considered**\nA clear and concise description of any alternative solutions or features you've considered.\n\n**Additional context**\nAdd any other context or screenshots about the feature request here.\n\n---\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[3230,3233],{"name":3231,"color":3232},"good first issue","7057ff",{"name":3234,"color":3235},"P1","519BFE",12555,"closed","Add Clear Action Buttons for \"Visit Patient Profile\" and \"Visit Encounter\" on Encounter Listing Page","2025-06-16T13:43:59Z","https://github.com/ohcnetwork/care_fe/issues/12555",0.74364406,{"description":3243,"labels":3244,"number":3246,"owner":3178,"repository":3179,"state":3237,"title":3247,"updated_at":3248,"url":3249,"score":3250},"**Describe the bug**\nCurrently, there is inconsistency in how users are rendered across different parts of the app.\nIn some places, we display the username, while in others, we display the user’s full name.\n\n**To Reproduce**\nFile an encounter and update diagnosis, symptom medication and allergies. \n\n\n**Expected behavior**\nRending user's full name across the app wherever Logged By is captured.\n\n**Screenshots**\n\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[3245],{"name":3231,"color":3232},12118,"Make User Rendering Consistent Across the App","2025-07-23T15:16:41Z","https://github.com/ohcnetwork/care_fe/issues/12118",0.7467815,{"description":3252,"labels":3253,"number":3256,"owner":3178,"repository":3179,"state":3237,"title":3257,"updated_at":3258,"url":3259,"score":3260},"**Describe the bug**\nOn the User Information page, when editing the password fields (Current Password, New Password, and Confirm New Password), I noticed that two eye icons appear inside the input field, one from our code and one injected by the browser (likely default). Both perform the same toggle, but it looks redundant and might confuse users.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Navigate to the User Information page.\n2. Go to the Reset Password section.\n3. Start typing into any of the password fields (Current Password, New Password, or Confirm New Password).\n4. Observe that two \"eye\" icons appear for toggling password visibility.\n\n**Expected behavior**\nOnly one visibility toggle icon should appear per password field, which toggles the visibility of that specific field.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/66d6b3b8-c118-4f01-ab35-4ede3b442a0a\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[3254,3255],{"name":3172,"color":3173},{"name":3175,"color":3176},12877,"Duplicate Password Visibility Toggle Icons Appearing","2025-07-14T08:12:40Z","https://github.com/ohcnetwork/care_fe/issues/12877",0.74987507,{"description":3262,"labels":3263,"number":3269,"owner":3178,"repository":3179,"state":3237,"title":3270,"updated_at":3271,"url":3272,"score":3273},"**Describe the bug**\nIn the Patient Encounters page, the search by **Encounter ID** displays a toast error saying `\"Not found\"` when there are no matching results. However, when searching by **Patient Name** or **External Identifier**, no toast is shown, only the \"No encounters found\" message in the UI. This inconsistency in behavior can confuse users.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Patient Encounters Page\n2. Click on Search bar\n3. see error\n\n**Expected behavior**\nRemove the toast for Encounter ID search so that all search types display only the **\"No encounters found\"** message for consistency\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/89efbe3a-c052-430e-a5fd-f93f89bae79e\n\n**Desktop (please complete the following information):**\n\n- OS: [e.g. iOS]\n- Browser [e.g. chrome, safari]\n- Version [e.g. 22]\n\n**Smartphone (please complete the following information):**\n\n- Device: [e.g. iPhone6]\n- OS: [e.g. iOS8.1]\n- Browser [e.g. stock browser, safari]\n- Version [e.g. 22]\n\n**Additional context**\nAdd any other context about the problem here.\n\n---\n\n### 🚨 DO NOT EDIT BELOW THIS LINE 🚨\n\n### Instructions for Requesting Assignment:\n\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\n**Describe your solution clearly:**\nProvide 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.\n\n**Expected Timeline:**\n- End date: [Expected submission date of a completed Pull Request]\n\n**Additional Context:**\nInclude any other relevant context, links, screenshots, or resources that support your proposed solution.\n\n> 🚨 Your assignment may be unassigned if there is no activity or progress within the stated timeline unless communicated clearly and agreed upon.\n",[3264,3265,3268],{"name":3172,"color":3173},{"name":3266,"color":3267},"stale","688388",{"name":3175,"color":3176},13351,"Inconsistent \"Not found\" toast behavior in Patient Encounters search","2025-10-01T10:36:01Z","https://github.com/ohcnetwork/care_fe/issues/13351",0.7515392,["Reactive",3275],{},["Set"],["ShallowReactive",3278],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fYpVPxy5q9hXV5grv5gqPvDHg_O11rWV_mylC9l2Y4zU":-1},"/ohcnetwork/care_fe/9777"]