\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.7335671,{"description":3186,"labels":3187,"number":3188,"owner":3178,"repository":3179,"state":3180,"title":3189,"updated_at":3190,"url":3191,"score":3192},"**Describe the bug**\nCurrent design needs a change which would fix some UI issues and make it consistent with overall design \n\n\n\nhttps://github.com/user-attachments/assets/09c690f9-e5b5-4b8a-8476-6980f8d3f94d \n\nLike mobile view and also fix this below ss with red pen - it should take full height irrespective wheather content is present or not \n\n\u003Cimg width=\"1440\" height=\"846\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7516b336-9c24-4a8b-99e7-fb5a90c29d4d\" />\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Login as superadmin/admin\n- Go to Admin Dashboard\n- Go to Organization Tab\n- See the current UI \n\n\n\n**Expected Design**\n >[!TIP]\nRefer to desing for dept/team under any facility and match the exact design like table and card\n\nhttps://github.com/user-attachments/assets/1b63cc23-5d85-4477-b0c0-32776bb811bf\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",[],13042,"Update the design for Goverance, Supplier and Roles under Organization tab","2025-07-28T05:44:38Z","https://github.com/ohcnetwork/care_fe/issues/13042",0.7773164,{"description":3194,"labels":3195,"number":3196,"owner":3178,"repository":3179,"state":3197,"title":3198,"updated_at":3199,"url":3200,"score":3201},"**Describe*\nCurrently, when assigning a Location to an Encounter, users can only pick from existing Locations. This improvement will allow users to create a new Location directly within the same workflow, without leaving the Encounter form or navigating to a separate screen. This is especially helpful when all existing Locations are occupied and a new Location needs to be added immediately, ensuring a smoother and faster user experience\n\n\nhttps://github.com/user-attachments/assets/cdfd5bb3-a548-435e-b10d-4ac5349e79bb\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",[],12873,"closed","Allow users to create a new Location directly when assigning a Location to an Encounter","2025-07-14T08:14:50Z","https://github.com/ohcnetwork/care_fe/issues/12873",0.7434632,{"description":3203,"labels":3204,"number":3205,"owner":3178,"repository":3179,"state":3197,"title":3206,"updated_at":3207,"url":3208,"score":3209},"It’d help if there’s clear distinction of encounters based on their encounter class when listing them rather than just a filter.\n\n### Proposed Solution\nfor each encounter class, add a sidebar item “{encounter class} encounters”. upon opening this, it should open the encounters list page filtered by the encounter class.\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",[],13496,"Improve flow for viewing encounters list","2025-09-01T06:48:49Z","https://github.com/ohcnetwork/care_fe/issues/13496",0.7447725,{"description":3211,"labels":3212,"number":3213,"owner":3178,"repository":3179,"state":3197,"title":3214,"updated_at":3215,"url":3216,"score":3217},"When an encounter is completed, we should navigate to the verified patient page, instead of the patient details page where a new encounter can be created. This will improve the workflow for healthcare providers who need to create follow-up encounter",[],12647,"Navigate to verified patient page after encounter completion","2025-06-24T11:49:17Z","https://github.com/ohcnetwork/care_fe/issues/12647",0.754896,{"description":3219,"labels":3220,"number":3221,"owner":3178,"repository":3179,"state":3197,"title":3222,"updated_at":3223,"url":3224,"score":3225},"**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.754932,{"description":3227,"labels":3228,"number":3231,"owner":3178,"repository":3179,"state":3197,"title":3232,"updated_at":3233,"url":3234,"score":3235},"**Description**\nA 'Back' button is needed on the Encounters page to improve user navigation and overall experience.\n\n**Problem**\nCurrently, there is no clear and consistent way for a user to return to the previous page from the Encounters page without relying on the browser's back button. This can be confusing for some users and may lead to a broken or unpredictable app flow.\n\n\u003Cimg width=\"2048\" height=\"1128\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7fe0e7d4-44c8-496e-8a9d-5c01f6acfa59\" />\n\n**Proposed Solution**\n\n1. Add a Medium (Height=32px) Tertiary 'Back' button with left arrow icon as leading icon to the top-left of the Encounters page header. Use an existing 'Back' button component exists in our design system.\n\n2. The button's action should navigate the user to the previous screen. For example, if a user came from the Patient's overview page, the 'Back' button should return them to that 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",[3229,3230],{"name":3172,"color":3173},{"name":3175,"color":3176},13208,"Feature: Add 'Back' button to Encounters page for improved navigation","2025-08-04T05:09:19Z","https://github.com/ohcnetwork/care_fe/issues/13208",0.7560795,{"description":3237,"labels":3238,"number":3241,"owner":3178,"repository":3179,"state":3197,"title":3242,"updated_at":3243,"url":3244,"score":3245},"When creating a new questionnaire, the system automatically selects encounter as subject type by default. Thus reducing manual input and streamlining the process.",[3239,3240],{"name":3172,"color":3173},{"name":3175,"color":3176},12369,"Select encounter by default as subject type while creating a new questionnaire","2025-06-13T14:22:43Z","https://github.com/ohcnetwork/care_fe/issues/12369",0.75700295,{"description":3247,"labels":3248,"number":3249,"owner":3178,"repository":3179,"state":3197,"title":3250,"updated_at":3251,"url":3252,"score":3253},"**Describe the bug**\n The recent design update of EncounterInfoCard works correctly in EncounterList, but it breaks the layout where it’s used to show an encounter’s association with an occupied location (bed).\n\n**To Reproduce**\nSteps to reproduce the behaviour:\n\n1. Go to `location` under patient main tab \n2. See for already occupied location if any present \n3. If not assign a location to any encounter\n4. See error\n\n\n**Screenshots**\n\n\u003Cimg width=\"1440\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/599812dd-92fd-4d68-88ea-cd51939dd8c9\" />\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",[],12635,"EncounterInfoCard UI Update Breaks Location Association Display","2025-06-17T15:12:26Z","https://github.com/ohcnetwork/care_fe/issues/12635",0.7580721,{"description":3255,"labels":3256,"number":3257,"owner":3178,"repository":3179,"state":3197,"title":3258,"updated_at":3259,"url":3260,"score":3261},"**Description:** The patient Home appears congested. Key information, action buttons, and navigation tabs feel cramped, making the interface less user-friendly.\n\n\u003Cimg width=\"911\" height=\"401\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/620e581a-7f84-4f48-aa7c-36edc9fb7974\" />\n\n\n**Steps to Reproduce:**\n- Goto encounters from the sidebar\n- Select any patient\n- Navigate to Patient Home\n\n---\n🚨 DO NOT EDIT BELOW THIS LINE 🚨\nInstructions for Requesting Assignment:\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\nDescribe 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\nExpected Timeline:\n\nEnd date: [Expected submission date of a completed Pull Request]\nAdditional 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.",[],13838,"Enhancement of Patient Home Via Encounter","2025-09-26T06:10:23Z","https://github.com/ohcnetwork/care_fe/issues/13838",0.760291,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHtX9zao2No47G3T6EcogU5DFR0Mgj7QdZxU6QQxUg-Q":-1},"/ohcnetwork/care_fe/11157"]