\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",[],13956,"ohcnetwork","care_fe","open","Search Patients – Incorrect \"No Records Found\" Message","2025-10-06T05:25:11Z","https://github.com/ohcnetwork/care_fe/issues/13956",0.746578,{"description":3180,"labels":3181,"number":3188,"owner":3172,"repository":3173,"state":3174,"title":3189,"updated_at":3190,"url":3191,"score":3192},"**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",[3182,3185],{"name":3183,"color":3184},"question","d876e3",{"name":3186,"color":3187},"needs-triage","ededed",13372,"Sorting Encounters","2025-08-18T08:08:01Z","https://github.com/ohcnetwork/care_fe/issues/13372",0.7520156,{"description":3194,"labels":3195,"number":3196,"owner":3172,"repository":3173,"state":3174,"title":3197,"updated_at":3198,"url":3199,"score":3200},"**Description**: The UI can be improved in the Mobile View\n\n\u003Cimg width=\"325\" height=\"414\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c5466bd8-b3f0-48b4-a49d-18e46a10dc59\" />\n\n\u003Cimg width=\"325\" height=\"414\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/9b96dcca-aa4f-4cdb-85ae-6b3bb2773688\" />\n\n**Steps To Reproduce:**\n- Go to Patients from the sidebar\n- All encounter -> View Encounter of any patient",[],13691,"Improve UI of View Encounter Page in Mobile View","2025-09-12T02:12:32Z","https://github.com/ohcnetwork/care_fe/issues/13691",0.7539725,{"description":3202,"labels":3203,"number":3210,"owner":3172,"repository":3173,"state":3211,"title":3212,"updated_at":3213,"url":3214,"score":3215},"**Is your feature request related to a problem? Please describe.**\nCurrently, on the encounter listing page:\n\n1. Clicking the patient name navigates to the patient’s profile.\n\n2. Clicking the \"View Details\" button navigates to the encounter details.\n\nHowever, this behavior is not immediately intuitive for users. It would be clearer and more user-friendly to have explicitly labeled buttons for both actions.\n\n**Describe the solution you'd like**\nAdd two clearly labeled buttons for each encounter row:\n1. \"Visit Patient Profile\"\n2. \"Visit Encounter Details\"\n\nUse icons or color differentiation (optional) to help users quickly recognize actions.\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",[3204,3207],{"name":3205,"color":3206},"good first issue","7057ff",{"name":3208,"color":3209},"P1","519BFE",12555,"closed","Add Clear Action Buttons for \"Visit Patient Profile\" and \"Visit Encounter\" on Encounter Listing Page","2025-06-16T13:43:59Z","https://github.com/ohcnetwork/care_fe/issues/12555",0.7017655,{"description":3217,"labels":3218,"number":3219,"owner":3172,"repository":3173,"state":3211,"title":3220,"updated_at":3221,"url":3222,"score":3223},"**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.7150175,{"description":3225,"labels":3226,"number":3229,"owner":3172,"repository":3173,"state":3211,"title":3230,"updated_at":3231,"url":3232,"score":3233},"**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",[3227,3228],{"name":3183,"color":3184},{"name":3186,"color":3187},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.7288557,{"description":3235,"labels":3236,"number":3239,"owner":3172,"repository":3173,"state":3211,"title":3240,"updated_at":3241,"url":3242,"score":3243},"**Is your feature request related to a problem? Please describe.**\nYes, Just like we have `Schedule Appointment` button add a `Create Encounter`\n\nhttps://github.com/user-attachments/assets/2d70d927-23bf-4c70-814e-d6592c45b8ec\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",[3237,3238],{"name":3183,"color":3184},{"name":3186,"color":3187},13399,"Add `Create Encounter` button in Encounter tab in patient detail page","2025-08-18T02:37:43Z","https://github.com/ohcnetwork/care_fe/issues/13399",0.73151284,{"description":3245,"labels":3246,"number":3252,"owner":3172,"repository":3173,"state":3211,"title":3253,"updated_at":3254,"url":3255,"score":3256},"**Describe the bug**\nFor patients who are already discharged and marked as complete for those patients, when we try to open the general info page an error message pops up saying patient not found.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to patients profile who has been discharged and is marked as completed\n2. Click on small square shaped button with an arrow, right next to the patients name.\n3. See error\n\n**Expected behavior**\nThe general info page should open up.\n\n**Screenshots**\n\n\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",[3247,3248,3251],{"name":3183,"color":3184},{"name":3249,"color":3250},"stale","688388",{"name":3186,"color":3187},12781,"For patients who are marked as completed, the general info page is not accessible.","2025-08-13T06:56:57Z","https://github.com/ohcnetwork/care_fe/issues/12781",0.73280567,{"description":3258,"labels":3259,"number":3265,"owner":3172,"repository":3173,"state":3211,"title":3266,"updated_at":3267,"url":3268,"score":3269},"Description:\nCurrently, in the Inpatient encounter view, the bed number is only available inside the Location tab. However, it is not displayed/highlighted on the main Encounter page, where nurses and doctors usually interact. This makes it inconvenient for staff and increases the risk of negligence in patient care.\n\nWhy this is Important:\n1. Nurses and doctors often do not go into the Location tab to verify bed details. \n2. Bed number should be prominently shown in the Encounter Details section (or a highlighted field in the overview) to:\n . Easily identify the patient’s bed during admission and rounds.\n . Support smooth patient shifting workflows.\n . Enable accurate tele-consultancy (Hub ↔ Spoke) communication.\n . Avoid negligence when no bed is assigned — a clear message should appear (e.g., “No Bed Assigned”).\n\nSteps to Reproduce:\n1. Admit a patient with an Inpatient encounter.\n2. Check the Encounter Details section on the main page.\n3. Observe that bed number is missing, though it exists under the Location tab.\n\nExpected Behavior:\n1. Bed number should be visible and highlighted directly on the Encounter page (Encounter Details section).\nI2. f a patient is not assigned to any bed, show a clear warning message: “No Bed Assigned”.\n\nActual Behavior:\n1. Bed number is only visible under the Location tab.\n2. No warning is shown when the patient has not been assigned a bed.\n\n\u003Cimg width=\"1303\" height=\"598\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cdf18a99-c0bd-415d-9842-164850b79a33\" />",[3260,3261,3264],{"name":3183,"color":3184},{"name":3262,"color":3263},"blocked","e50620",{"name":3186,"color":3187},13515,"Feature Request: Bed Number Not Highlighted in Inpatient Encounter Page","2025-09-09T10:20:06Z","https://github.com/ohcnetwork/care_fe/issues/13515",0.73285425,{"description":3271,"labels":3272,"number":3273,"owner":3172,"repository":3173,"state":3211,"title":3274,"updated_at":3275,"url":3276,"score":3277},"**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.73500544,["Reactive",3279],{},["Set"],["ShallowReactive",3282],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f6Et_84m2g3MfEQhamCH58SR4Af4yI7fAgYqGSh7arzI":-1},"/ohcnetwork/care_fe/12647"]