\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.7372917,{"description":3186,"labels":3187,"number":3188,"owner":3178,"repository":3179,"state":3180,"title":3189,"updated_at":3190,"url":3191,"score":3192},"**Describe the bug**\n\nWhen we're adding patient notes with number pointer and proper spaces, its been trim and visible with unwanted spacing and breaks. For Example :\n\n1. HOw are you\n\nIf we submit this, post submission it will be reflected as :\n\n1. \n\nHow are you\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to patient encounter\n2. Open the notes, and type the data as mentioned in the screenshot\n3. See error\n\n**Expected behavior**\n\n- post submission, the note should be visible, similar to the submission from the user input\n\n**Screenshots**\n\n\u003Cimg width=\"1120\" height=\"732\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0b5b6862-1c75-47f7-b2ad-e6a54d7a5556\" />\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",[],13274,"Fix the spacing in the patient notes post submission ( Patient encounter & details page )","2025-08-06T07:02:56Z","https://github.com/ohcnetwork/care_fe/issues/13274",0.79900366,{"description":3194,"labels":3195,"number":3196,"owner":3178,"repository":3179,"state":3180,"title":3197,"updated_at":3198,"url":3199,"score":3200},"**Describe the bug**\nIn any purchase order's details page, the items in the table are cut short and not good for viewing\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Inventory'\n2. Click on 'Purchase Orders'\n3. Scroll down to 'View Details' of any purchase order\n4. See error\n\n**Expected behavior**\nThe elements should be properly aligned and the words should not be cut in middle\n\n**Screenshots**\n\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: j7 max\n- OS: android 8\n- Browser chrome\n- Version latest\n\n**Additional context**\nMaybe adding overflox-x-auto could resolve this and make the items scrollable having required width for each column\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",[],13656,"UI issue in Purchase Order details page in mobile view","2025-09-08T13:26:59Z","https://github.com/ohcnetwork/care_fe/issues/13656",0.80173594,{"description":3202,"labels":3203,"number":3209,"owner":3178,"repository":3179,"state":3210,"title":3211,"updated_at":3212,"url":3213,"score":3214},"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\" />",[3204,3205,3208],{"name":3172,"color":3173},{"name":3206,"color":3207},"blocked","e50620",{"name":3175,"color":3176},13515,"closed","Feature Request: Bed Number Not Highlighted in Inpatient Encounter Page","2025-09-09T10:20:06Z","https://github.com/ohcnetwork/care_fe/issues/13515",0.7043159,{"description":3216,"labels":3217,"number":3218,"owner":3178,"repository":3179,"state":3210,"title":3219,"updated_at":3220,"url":3221,"score":3222},"**Describe the bug**\nWhen adding beds on the home page of Locations, it's successfully created but can only be seen using the \"map\" view. Not visible on the \"list view\"\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Settings' > 'Locations'\n2. Click on 'Add Location'\n3. Scroll down and add beds\n4. See that it's shown on Map view but not on List View \n\n**Expected behavior**\nBoth the list view and map view should be consistent with each other.\n\n**Video Demo**\n\nhttps://github.com/user-attachments/assets/0e9e34ae-221e-4597-9954-5d067b9a63d1\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",[],12444,"Bug: Locations page inconsistency between list and map view","2025-05-30T03:14:25Z","https://github.com/ohcnetwork/care_fe/issues/12444",0.7452935,{"description":3224,"labels":3225,"number":3226,"owner":3178,"repository":3179,"state":3210,"title":3227,"updated_at":3228,"url":3229,"score":3230},"**Is your feature request related to a problem? Please describe.**\nCurrent Dashboard uses `CardGridSkeleton` which doesn't match the layout. Implement a better loading skeleton for this page.\n\n\n\nhttps://github.com/user-attachments/assets/da60bbbf-7a82-4352-a668-690cc030d231\n\n**To reproduce**\n\n1. go to \"overview\".\n2. go to \"Bed availability dashboard\".\n3. click refresh.\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",[],13777,"Loading skeleton doesn't match Bed availability dashboard.","2025-09-22T08:32:46Z","https://github.com/ohcnetwork/care_fe/issues/13777",0.75394017,{"description":3232,"labels":3233,"number":3234,"owner":3178,"repository":3179,"state":3210,"title":3235,"updated_at":3236,"url":3237,"score":3238},"**Describe the bug**\nunnecessary details in the observation list and files upload info are coming up on discharge summary. \n\n- [ ] Remove the LOINC code link from the observation\n\n- [ ] vitals format should be changed.\n- [ ] Medication name is not showing. \n- [ ] Remove file upload info from the annex\n\n\u003Cimg width=\"221\" height=\"260\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b4a612d1-42d8-4220-9846-e9fe5e2f5c4e\" />\n\n\u003Cimg width=\"215\" height=\"92\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/bfabfadd-5e19-4442-9b01-59ea11beacac\" />\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Patients\n2. Select any patient and update vitals and files\n3. Select the discharge summary and generate\n4. See error\n\n**Expected behavior**\n\n**Screenshots**\nIf applicable, add screenshots to help explain your problem.\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",[],13072,"Unnecessary details are reflecting on Discharge Summary","2025-08-17T08:29:56Z","https://github.com/ohcnetwork/care_fe/issues/13072",0.7762821,{"description":3240,"labels":3241,"number":3248,"owner":3178,"repository":3179,"state":3210,"title":3249,"updated_at":3250,"url":3251,"score":3252},"**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",[3242,3245],{"name":3243,"color":3244},"enhancement","a2eeef",{"name":3246,"color":3247},"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.7784301,{"description":3254,"labels":3255,"number":3256,"owner":3178,"repository":3179,"state":3210,"title":3257,"updated_at":3258,"url":3259,"score":3260},"**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.7800832,{"description":3262,"labels":3263,"number":3269,"owner":3178,"repository":3179,"state":3210,"title":3270,"updated_at":3271,"url":3272,"score":3273},"**Describe the bug**\nUnnecessary whole page scroll is coming up for medium screen despite having enough space and it is fine for smaller and large screen \n\n**To Reproduce**\nSteps to reproduce the behaviour:\n\n1. Go to any facility\n2. Go to Encounters tab\n3. Click on View Patient for any encounter\n4. See error\n\n**Expected behaviour**\nRemove this unnecessary scrolling\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/b317823c-9d8d-4d47-95df-e81f28b23edd\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",[3264,3265,3268],{"name":3172,"color":3173},{"name":3266,"color":3267},"stale","688388",{"name":3175,"color":3176},12960,"Remove unnecessary scroll for patient detail page on medium screen","2025-10-10T11:15:03Z","https://github.com/ohcnetwork/care_fe/issues/12960",0.7811868,["Reactive",3275],{},["Set"],["ShallowReactive",3278],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fdzEcnbpwcAkMoonKDtVAEBIpYWcj3uHNDi5BvvBLztw":-1},"/ohcnetwork/care_fe/13822"]