\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.74140465,{"description":3186,"labels":3187,"number":3188,"owner":3178,"repository":3179,"state":3180,"title":3189,"updated_at":3190,"url":3191,"score":3192},"**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.7649037,{"description":3194,"labels":3195,"number":3196,"owner":3178,"repository":3179,"state":3180,"title":3197,"updated_at":3198,"url":3199,"score":3200},"Description:\nWhile checking the bed layout for a location, the bed order is displayed in reverse. For example, in an ICU with 30 beds, the first view shows beds from 30 down to 20 instead of starting from 1 upwards.\n\nSteps to Reproduce:\n\nClick on a location.\n\nClick on a ward (e.g., 10-bed ICU).\n\nNotice that the beds are listed starting from the last bed number instead of the first.\n\nCurrent Behavior:\n\nBed list is ordered last-to-first.\n\nExample: ICU with 30 beds shows 30–20 on the first screen.\n\nExpected Behavior:\n\nBed list should start from the first bed (e.g., 1–10, then 11–20, and so on).\n\nThis will make it intuitive for users who usually admit patients from the first beds.\n\nImpact:\n\nUsers have to navigate to the last page to find the first beds, which slows down workflow.\n\nIn emergency situations, this creates unnecessary delays in locating and admitting patients.\n\nSuggested Fix:\n\nReverse the ordering so that bed view starts from the first bed number.",[],13822,"Bed view order shows in reverse (last-to-first) instead of first-to-last","2025-09-24T04:36:31Z","https://github.com/ohcnetwork/care_fe/issues/13822",0.7738732,{"description":3202,"labels":3203,"number":3209,"owner":3178,"repository":3179,"state":3180,"title":3210,"updated_at":3211,"url":3212,"score":3213},"**Is your feature request related to a problem? Please describe.**\nThe mentioned option is unavailable in these fields. which is important because when a patient gets shifted from a ward to ICU within same hospital, it's termed \"trans in\" and from the ICU to the ward, it's \"trans out\"\n\n**Describe the solution you'd like**\nTrans In & Trans Out options in Admit Source and Discharge Disposition, respectively\n\n**Steps to reproduce**\n[https://care.coronasafe.in/facility/d95bf507-055d-403f-acd3-3d331c735140/patient/043edc74-22b9-4efe-b8d7-2695eacb6917/encounter/131ed06a-abbc-4ed9-b9df-ca594e58148c/questionnaire/encounter](url)\n\n1. Click on above URL\n2. Use the Login Credentials:\n Username: jamesnurse\n password: James@123\n3. Go to Hospitalization Details.\n4. Click on Admit Source.\n____SS____\n\n\n\n5. Click on \"Mark as Discharge\" and hit proceed\n6. Go to Hospitalization Details. \n7. Click on Discharge Disposition\n____SS____\n\n\n\n@gigincg \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",[3204,3205,3208],{"name":3172,"color":3173},{"name":3206,"color":3207},"discussion required","05EFF8",{"name":3175,"color":3176},12774,"Trans In & Trans Out options in Admit Source and Discharge Disposition, respectively","2025-08-18T08:07:27Z","https://github.com/ohcnetwork/care_fe/issues/12774",0.7802991,{"description":3215,"labels":3216,"number":3217,"owner":3178,"repository":3179,"state":3180,"title":3218,"updated_at":3219,"url":3220,"score":3221},"**Is your feature request related to a problem? Please describe.**\n\n- [ ] OPD slip Needs to be generated - this is generated,billed and given out to the patients at the time of registraton. \n\n* Currently the opd slips contains a barcode. so the staff in the hospital can locate or retrieve patient file easily at any counter (Pharmacy,Lab,Billing etc) \n\n\u003Cimg width=\"288\" height=\"377\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ffd81394-0a8d-41e9-9c52-38f2e85a6b10\" />\n\n- [ ] Billing for OPD slip ( Rs.10/- for all the Govt hospitals) \n\n- [ ] Pharmacy service is free for all the OP patients in government hospitals. - need to plan for dispense medicines workflow without billing option \n\n- [ ] Avail search by patient identifier option on Billing,Lab,Pharmacy modules\n\n@amjithtitus09 \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",[],13176,"OPD request from HMIS pilot states","2025-07-31T08:59:03Z","https://github.com/ohcnetwork/care_fe/issues/13176",0.7831894,{"description":3223,"labels":3224,"number":3225,"owner":3178,"repository":3179,"state":3226,"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,"closed","Loading skeleton doesn't match Bed availability dashboard.","2025-09-22T08:32:46Z","https://github.com/ohcnetwork/care_fe/issues/13777",0.7049817,{"description":3232,"labels":3233,"number":3234,"owner":3178,"repository":3179,"state":3226,"title":3235,"updated_at":3236,"url":3237,"score":3238},"if a bed is planned to be free in ICU, how to plan which patient needs to be prioritised to be shifted to that bed. also this flow must enable to plan on the possible availability of patients that could be moved out of ICU. similar use cases will be there in specific wards like maternity wards and among other ward.\n\nWe need a location management system within a hospital as per the different types of wards, rooms and other specific locations like dialysis room, chemo therapy room etc",[],13759,"Need to create a bed flow in the hospital for tracking patient flow.","2025-09-18T18:13:59Z","https://github.com/ohcnetwork/care_fe/issues/13759",0.7223342,{"description":3240,"labels":3241,"number":3247,"owner":3178,"repository":3179,"state":3226,"title":3248,"updated_at":3249,"url":3250,"score":3251},"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\" />",[3242,3243,3246],{"name":3172,"color":3173},{"name":3244,"color":3245},"blocked","e50620",{"name":3175,"color":3176},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.7467356,{"description":3253,"labels":3254,"number":3255,"owner":3178,"repository":3179,"state":3226,"title":3256,"updated_at":3257,"url":3258,"score":3259},"**Is your feature request related to a problem? Please describe.**\nIn the **My Schedule → Availability section**, the UI currently uses the **CareLoading** component while data is being fetched. However, across the rest of the app, we use **TableSkeleton** for consistency.\n\n**Describe the solution you'd like**\nReplace CareLoading with TableSkeleton in the Availability section to ensure consistent loading states across the platform\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**\n\nhttps://github.com/user-attachments/assets/d1bebed5-5b7b-4c35-b659-89df1b94638c\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",[],13837,"Replace CareLoading with TableSkeleton in Availability Section","2025-09-30T10:57:45Z","https://github.com/ohcnetwork/care_fe/issues/13837",0.7540658,{"description":3261,"labels":3262,"number":3263,"owner":3178,"repository":3179,"state":3226,"title":3264,"updated_at":3265,"url":3266,"score":3267},"**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.7616969,["Reactive",3269],{},["Set"],["ShallowReactive",3272],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fzfOxSnmoggxIkqphkqenxzGREt8ycppzhOrDGzZJXrw":-1},"/ohcnetwork/care_fe/13756"]