\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",[3171,3174],{"name":3172,"color":3173},"question","d876e3",{"name":3175,"color":3176},"needs-triage","ededed",13372,"ohcnetwork","care_fe","open","Sorting Encounters","2025-08-18T08:08:01Z","https://github.com/ohcnetwork/care_fe/issues/13372",0.68776566,{"description":3186,"labels":3187,"number":3188,"owner":3178,"repository":3179,"state":3180,"title":3189,"updated_at":3190,"url":3191,"score":3192},"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.7782029,{"description":3194,"labels":3195,"number":3196,"owner":3178,"repository":3179,"state":3197,"title":3198,"updated_at":3199,"url":3200,"score":3201},"**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,"closed","Redesign Appointment Booking Flow for Improved Usability & Accessibility","2025-08-19T08:32:08Z","https://github.com/ohcnetwork/care_fe/issues/13421",0.7641668,{"description":3203,"labels":3204,"number":3210,"owner":3178,"repository":3179,"state":3197,"title":3211,"updated_at":3212,"url":3213,"score":3214},"**Is your feature request related to a problem? Please describe.**\nA clear and concise description of what the problem is. Ex. I'm always frustrated when [...]\n\n**Describe the solution you'd like**\nA clear and concise description of what you want to happen.\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",[3205,3206,3209],{"name":3172,"color":3173},{"name":3207,"color":3208},"stale","688388",{"name":3175,"color":3176},12098,"Make SortIndex a Generic Reusable Component not just location specfic.","2025-07-30T09:45:14Z","https://github.com/ohcnetwork/care_fe/issues/12098",0.76557493,{"description":3216,"labels":3217,"number":3224,"owner":3178,"repository":3179,"state":3197,"title":3225,"updated_at":3226,"url":3227,"score":3228},"**Is your feature request related to a problem? Please describe.**\nCurrently, there is no dashboard to provide a real-time, visual overview of bed availability at the facility (hospital) level. Hospital staff and administrators need a clear way to monitor which beds are available, occupied, or reserved in order to make efficient assignments and improve patient flow.\n\n**Describe the solution you'd like**\nDevelop a Facility Level Bed Availability Dashboard for Hospitals. This dashboard should:\n- Display a real-time overview of bed availability across all wards/units within a hospital facility.\n- Integrate with the existing locations API (already in use for assigning patients to available beds) to fetch up-to-date bed status.\n- Visually distinguish between available, occupied, and reserved beds, possibly with color coding or icons.\n- Allow staff to quickly identify which wards/units have the most/least capacity.\n- Optionally, provide filters for ward/unit, bed type, and availability status.\n\n**Describe alternatives you've considered**\n- Manual monitoring or spreadsheet tracking, which is not scalable or real-time.\n- External dashboard tools, but direct integration within the app using the locations API is preferred for data accuracy and seamless workflow.\n\n**Additional context**\n- The locations API is already leveraged for bed assignment workflows.\n- This dashboard will support operational efficiency and patient care.\n",[3218,3221],{"name":3219,"color":3220},"enhancement","a2eeef",{"name":3222,"color":3223},"UI Component","fef2c0",13756,"Build Facility Level Bed Availability Dashboard for Hospitals","2025-09-18T16:02:44Z","https://github.com/ohcnetwork/care_fe/issues/13756",0.7703045,{"description":3230,"labels":3231,"number":3236,"owner":3178,"repository":3179,"state":3197,"title":3237,"updated_at":3238,"url":3239,"score":3240},"**Is your feature request related to a problem? Please describe.**\nUI Update for 'Book Appointment' to be implemented in care\n\n\u003Cimg width=\"803\" height=\"642\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/66456bbc-8e53-491b-8bcb-8d53f5a10c72\" />\n\nURL: https://www.figma.com/design/Z93EYKSa1MdBmXndsMBJSQ/Care?node-id=22778-8984&p=f&t=2Lhj10iQTbP0nO8o-0\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",[3232,3235],{"name":3233,"color":3234},"redesign","B8F850",{"name":3207,"color":3208},13409,"UI Update for 'Book Appointment' to be implemented","2025-09-11T08:40:18Z","https://github.com/ohcnetwork/care_fe/issues/13409",0.7703583,{"description":3242,"labels":3243,"number":3244,"owner":3178,"repository":3179,"state":3197,"title":3245,"updated_at":3246,"url":3247,"score":3248},"_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.7754078,{"description":3250,"labels":3251,"number":3255,"owner":3178,"repository":3179,"state":3197,"title":3256,"updated_at":3257,"url":3258,"score":3259},"The system now show all departments and team while an encounter is created, a better UX would be to default to all encounters they have access too, this would be our 90% of the workflow. \n\nFor the remaning 10% that involves inter-department transfers and connections, lets have a better UX in place",[3252,3253,3254],{"name":3172,"color":3173},{"name":3207,"color":3208},{"name":3175,"color":3176},11157,"Default to departments they have access to while creating an encounter","2025-08-13T05:57:58Z","https://github.com/ohcnetwork/care_fe/issues/11157",0.7764579,{"description":3261,"labels":3262,"number":3263,"owner":3178,"repository":3179,"state":3197,"title":3264,"updated_at":3265,"url":3266,"score":3267},"if a bed is planned to be free in ICU, how to plan which patient needs to be prioritised to be shifted to that bed. also this flow must enable to plan on the possible availability of patients that could be moved out of ICU. similar use cases will be there in specific wards like maternity wards and among other ward.\n\nWe need a location management system within a hospital as per the different types of wards, rooms and other specific locations like dialysis room, chemo therapy room etc",[],13759,"Need to create a bed flow in the hospital for tracking patient flow.","2025-09-18T18:13:59Z","https://github.com/ohcnetwork/care_fe/issues/13759",0.7812133,{"description":3269,"labels":3270,"number":3271,"owner":3178,"repository":3179,"state":3197,"title":3272,"updated_at":3273,"url":3274,"score":3275},"**Describe**\nRedesign Departments List View like tabular design of location more cleaner and less space consuming making more departments to be shown on single page\n\nCurrent Dept Design \n\n\u003Cimg width=\"1166\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/12345786-feba-4891-a7dd-c71dea35e028\" />\n\nCurrent Location list Design\n\n\u003Cimg width=\"1166\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/bee6246f-fbd0-4406-bea3-5100d8eaee59\" />\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",[],12474,"Redesign Departments List View like tabular design of location","2025-06-13T12:11:38Z","https://github.com/ohcnetwork/care_fe/issues/12474",0.7832303,["Reactive",3277],{},["Set"],["ShallowReactive",3280],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f29Pgxf4iBBhdmX6aNYcn47M8GOo23DiMpaY3oVGCUhA":-1},"/ohcnetwork/care_fe/11593"]