\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",[],13305,"ohcnetwork","care_fe","open","Validation Errors Not Displayed as Expected for Schedule Edit Form ","2025-08-10T18:45:31Z","https://github.com/ohcnetwork/care_fe/issues/13305",0.76623553,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Is your feature request related to a problem? Please describe.**\nActive encounters for a patient is set to 5, that number could go up as there are different departments and they all need to add single or maybe multiple encounters for the same patient. \n\n**Describe the solution you'd like**\nIncrease the active encounter limit to 20.\n\n**Additional context**\nSaw this limitation at Arike.\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",[],13198,"Increase the number of active encounters for a single patient","2025-08-01T10:12:45Z","https://github.com/ohcnetwork/care_fe/issues/13198",0.7678194,{"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.7750656,{"description":3202,"labels":3203,"number":3204,"owner":3172,"repository":3173,"state":3174,"title":3205,"updated_at":3206,"url":3207,"score":3208},"**Describe**\n\n\u003Cimg width=\"1440\" height=\"846\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/551d6d23-583c-49ae-b64b-206b02f1ff7e\" />\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,"Add Resizable feature for Dept/team listing page","2025-07-23T10:06:36Z","https://github.com/ohcnetwork/care_fe/issues/13057",0.77795154,{"description":3210,"labels":3211,"number":3212,"owner":3172,"repository":3173,"state":3174,"title":3213,"updated_at":3214,"url":3215,"score":3216},"**Is your feature request related to a problem? Please describe.**\nCurrently we use care Loading components in patient Search bar we can replace with TableSketelon loading\n\nhttps://github.com/user-attachments/assets/66be993b-4305-429f-8036-be11ff55c51e\n\n**Describe the solution you'd like**\nuse custom tableSketelon loading component\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",[],13813,"Replace Loading in the patient search bar with tableSketelon","2025-09-23T13:46:03Z","https://github.com/ohcnetwork/care_fe/issues/13813",0.78095376,{"description":3218,"labels":3219,"number":3220,"owner":3172,"repository":3173,"state":3174,"title":3221,"updated_at":3222,"url":3223,"score":3224},"Description\nCurrently, our system disallows duplicate diagnosis and symptom entries entirely. However, this strict check creates unnecessary limitations when the same diagnosis or symptom legitimately appears more than once over time.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Go to any live encounter in facility \n- click on add diagnosis or add symptom \n- See the error for diagnosis and symptom question\n\n\nslack conversation : https://rebuildearth.slack.com/archives/C010GQBMFJ9/p1752585579887739\n\nExpected Behavior: **Wanted it for all three Allergy, diagnosis and symptom**\n- The duplicate check should only apply to unsaved (newly added) items.\n- Once saved, the same allergy, diagnosis or symptom can be added again in the future\n- The main goal is to prevent accidental duplicate entries while adding, not to block valid clinical updates.\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",[],12949,"Allow duplicate Allergy, diagnosis and symptoms if already saved , prevent only during new entry","2025-07-16T06:10:05Z","https://github.com/ohcnetwork/care_fe/issues/12949",0.7868872,{"description":3226,"labels":3227,"number":3228,"owner":3172,"repository":3173,"state":3229,"title":3230,"updated_at":3231,"url":3232,"score":3233},"**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.6712867,{"description":3235,"labels":3236,"number":3239,"owner":3172,"repository":3173,"state":3229,"title":3240,"updated_at":3241,"url":3242,"score":3243},"Currently, when rescheduling an appointment, the reassignment can only be made to the originally assigned user. There is no option to assign it to a different team member during the reschedule process. Requesting the ability to reassign appointments to another team member at the time of rescheduling to improve operational flexibility.\n\n@aravindm4 \n\n\u003Cimg width=\"1543\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b8d80df9-ac76-4145-a462-67c219ff7c24\" />",[3237,3238],{"name":3191,"color":3192},{"name":3194,"color":3195},11987,"Reassigning Rescheduled Appointments","2025-06-15T07:46:53Z","https://github.com/ohcnetwork/care_fe/issues/11987",0.69992846,{"description":3245,"labels":3246,"number":3249,"owner":3172,"repository":3173,"state":3229,"title":3250,"updated_at":3251,"url":3252,"score":3253},"- 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",[3247,3248],{"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.7573647,{"description":3255,"labels":3256,"number":3262,"owner":3172,"repository":3173,"state":3229,"title":3263,"updated_at":3264,"url":3265,"score":3266},"**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",[3257,3258,3261],{"name":3191,"color":3192},{"name":3259,"color":3260},"stale","688388",{"name":3194,"color":3195},11969,"Add Request Letter support in the care 3.0","2025-08-13T06:27:26Z","https://github.com/ohcnetwork/care_fe/issues/11969",0.7622041,["Reactive",3268],{},["Set"],["ShallowReactive",3271],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fre00RlEsvG8meO_AUtol9mesIuIiCoGj0wDWgqKsxyU":-1},"/ohcnetwork/care_fe/12377"]