\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.7782157,{"description":3238,"labels":3239,"number":3240,"owner":3181,"repository":3182,"state":3213,"title":3241,"updated_at":3242,"url":3243,"score":3244},"**Is your feature request related to a problem? Please describe.**\nYes. Move the create/add button in the new line of these pages:\n\n- [ ] Specimen Definitions\n- [ ] Observation Definitions\n- [ ] Activity Definitions\n- [ ] Charge Item Definitions\n- [ ] Product Knowledge\n- [ ] Products\n\n**Describe the solution you'd like**\n\n**Current:**\n\n\u003Cimg width=\"295\" height=\"428\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e19ce449-17eb-4985-a8d2-25256efc23d3\" />\n\n**Expected:**\n\n\u003Cimg width=\"295\" height=\"428\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/6fe4652a-5269-4fb9-9d1c-39e4873c2612\" />\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",[],12924,"Improve UI by moving the create/add button of Definition Pages (Activity Definitions, Specimen Definitions etc) in a seperate line","2025-07-23T06:39:18Z","https://github.com/ohcnetwork/care_fe/issues/12924",0.7789025,{"description":3246,"labels":3247,"number":3250,"owner":3181,"repository":3182,"state":3213,"title":3251,"updated_at":3252,"url":3253,"score":3254},"**Is your feature request related to a problem? Please describe.**\n\nCurrently FileSubTab, DischargeSummarySubTab and FileQuestion are using pretty much the same code for the add_files dropdown menu. Its a lot of duplication\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",[3248,3249],{"name":3172,"color":3173},{"name":3178,"color":3179},13087,"Make add_files dropdown menu a reusable component","2025-07-25T13:11:04Z","https://github.com/ohcnetwork/care_fe/issues/13087",0.7825506,{"description":3256,"labels":3257,"number":3258,"owner":3181,"repository":3182,"state":3213,"title":3259,"updated_at":3260,"url":3261,"score":3262},"**Describe the bug**\nCurrently, if user navigates to any `facility/{facilityId}` route through an organization, the `facilityId` is `undefined` and causes an error toast.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to any Organization\n2. Click on patients\n3. Navigate to any patient\n4. Encounters Tab -> View Encounters\n5. Service Requests Tab / Consents -> View Consents / Diagnostic Report -> View Report all show error toast.\n\n**Expected behavior**\nThere should be no errors or undefined api calls made.\n\n**Screenshots**\nIf applicable, add screenshots to help explain your problem.\n\n\u003Cimg width=\"1470\" height=\"956\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/9f53bdb3-7e53-45f6-8d46-6bd82d6ef10c\" />\n\n\u003Cimg width=\"1470\" height=\"956\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/da58658c-ac81-4016-a6ef-f811b74d6da2\" />\n\n\u003Cimg width=\"848\" height=\"164\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e7b825a1-2758-4b86-89e6-29f8f600e541\" />\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",[],13590,"Remove GET Facility api calls when navigating through Organization","2025-09-03T13:52:07Z","https://github.com/ohcnetwork/care_fe/issues/13590",0.78414804,{"description":3264,"labels":3265,"number":3266,"owner":3181,"repository":3182,"state":3213,"title":3267,"updated_at":3268,"url":3269,"score":3270},"**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.78547627,["Reactive",3272],{},["Set"],["ShallowReactive",3275],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$foDwGjPpHkAGYu6Pg6jYaSnrFtJv7-V88Sx8Act4-ogI":-1},"/ohcnetwork/care_fe/12909"]