\n\n\n**Expected behavior**\nRefer to resizable feature present for organization subtabs in Admin Dashboard page\n\n\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",[],13057,"ohcnetwork","care_fe","open","Add Resizable feature for Dept/team listing page","2025-07-23T10:06:36Z","https://github.com/ohcnetwork/care_fe/issues/13057",0.76829547,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"Redesign the facility organization selector according to new UI. Do ensure that existing functionality works.\n\nRefer to figma here: https://www.figma.com/design/Z93EYKSa1MdBmXndsMBJSQ/Care?node-id=14787-31983&p=f\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",[],12792,"Facility Organization Selector Redesign","2025-07-04T07:18:01Z","https://github.com/ohcnetwork/care_fe/issues/12792",0.76831275,{"description":3188,"labels":3189,"number":3196,"owner":3172,"repository":3173,"state":3174,"title":3197,"updated_at":3198,"url":3199,"score":3200},"**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",[3190,3193],{"name":3191,"color":3192},"question","d876e3",{"name":3194,"color":3195},"needs-triage","ededed",13372,"Sorting Encounters","2025-08-18T08:08:01Z","https://github.com/ohcnetwork/care_fe/issues/13372",0.7805221,{"description":3202,"labels":3203,"number":3204,"owner":3172,"repository":3173,"state":3205,"title":3206,"updated_at":3207,"url":3208,"score":3209},"**Is your feature request related to a problem? Please describe.**\nCurrently, the system only supports rescheduling a patient’s appointment to another date/time with the same practitioner. This limitation becomes a bottleneck when the originally scheduled practitioner is unavailable, and the patient needs to be reassigned to a different doctor or medical professional.\n\n\n**Describe the solution you'd like**\nAllow users to reschedule appointment to a different user\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.",[],12499,"closed","Allow Rescheduling of appointment to a different practitioner","2025-06-04T13:32:41Z","https://github.com/ohcnetwork/care_fe/issues/12499",0.6463688,{"description":3211,"labels":3212,"number":3213,"owner":3172,"repository":3173,"state":3205,"title":3214,"updated_at":3215,"url":3216,"score":3217},"_Feature Requested from production in care feedback group_\n\n**Issue:** Currently, we only support rescheduling of a appointments within a user's schedule\n\n**Feature request:** Add support to reschedule a existing care to any doctor / nurse in the facility\n\n",[],12377,"Add support to reschedule a existing care slot to another doctor / nurse within the facility","2025-07-30T14:15:55Z","https://github.com/ohcnetwork/care_fe/issues/12377",0.6923282,{"description":3219,"labels":3220,"number":3221,"owner":3172,"repository":3173,"state":3205,"title":3222,"updated_at":3223,"url":3224,"score":3225},"\u003Cimg width=\"909\" height=\"511\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8d11a570-0e28-4ce4-9b72-56fc1d475ceb\" />\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",[],13336,"Make the title \"Book Appointment\" display only once on Schedule Appointment","2025-08-11T17:49:53Z","https://github.com/ohcnetwork/care_fe/issues/13336",0.7374483,{"description":3227,"labels":3228,"number":3229,"owner":3172,"repository":3173,"state":3205,"title":3230,"updated_at":3231,"url":3232,"score":3233},"**Is your feature request related to a problem? Please describe.**\nThe current appointment booking flow is not intuitive and poses accessibility challenges. Users face friction when selecting a practitioner across departments.\n\nNew redesigned flow will improve the user experience by making the selection of practitioner, departments and slots easier. \n\n\n**Describe the solution you'd like**\nLink to the Figma File\nhttps://www.figma.com/design/Z93EYKSa1MdBmXndsMBJSQ/Care?node-id=22778-8984\n\n\n**Describe alternatives you've considered**\nNA\n\n**Additional context**\nNA\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",[],13421,"Redesign Appointment Booking Flow for Improved Usability & Accessibility","2025-08-19T08:32:08Z","https://github.com/ohcnetwork/care_fe/issues/13421",0.7498003,{"description":3235,"labels":3236,"number":3237,"owner":3172,"repository":3173,"state":3205,"title":3238,"updated_at":3239,"url":3240,"score":3241},"**Describe the bug**\nWhen a encounter is created and then the appointment is rescheduled, the encounter is removed from the appointment details page\nBut when using the page's link and accessing it in another tab, it shows the patient's encounter in appointment details page\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Appointment Details'\n2. Click on 'Add encounter'\n3. Scroll down to 'Reschedule'\n4. See error\n\n**Expected behavior**\nEither the encounter should be removed completely when rescheduling, or should not be removed and be transferred to the rescheduled slot\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/08a5543e-9a10-447b-ace7-3e97a133dbb3\n\n**Desktop (please complete the following information):**\n\n- OS: Win 10\n- Browser Opera\n- Version Latest\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",[],13688,"Patient Encounter not working properly","2025-09-11T13:38:06Z","https://github.com/ohcnetwork/care_fe/issues/13688",0.7514548,{"description":3243,"labels":3244,"number":3247,"owner":3172,"repository":3173,"state":3205,"title":3248,"updated_at":3249,"url":3250,"score":3251},"- Create a schedule for a user with multiple sessions\n- Update the existing session\n- Check the added session is available for scheduling appointments\n\nExample : you can write the code flat, without following the POM approach and the data-cy element IDs\n\n\n",[3245,3246],{"name":3191,"color":3192},{"name":3194,"color":3195},10351,"Feat: Add E2E tests for creating and updating availability by a doctor.","2025-09-30T07:08:30Z","https://github.com/ohcnetwork/care_fe/issues/10351",0.75892,{"description":3253,"labels":3254,"number":3255,"owner":3172,"repository":3173,"state":3205,"title":3256,"updated_at":3257,"url":3258,"score":3259},"In appointments, would be easier to navigate if view patient profile button is available if there is an active encounter.\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",[],13156,"View Patient profile button in appointments","2025-07-31T10:59:14Z","https://github.com/ohcnetwork/care_fe/issues/13156",0.7701438,["Reactive",3261],{},["Set"],["ShallowReactive",3264],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fhGqySq68c9HveMVuoNeMAH7-z07UxAYOCPD3GHwA9KY":-1},"/ohcnetwork/care_fe/11987"]