\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",[3199,3200],{"name":3172,"color":3173},{"name":3178,"color":3179},13372,"Sorting Encounters","2025-08-18T08:08:01Z","https://github.com/ohcnetwork/care_fe/issues/13372",0.7688396,{"description":3207,"labels":3208,"number":3209,"owner":3181,"repository":3182,"state":3183,"title":3210,"updated_at":3211,"url":3212,"score":3213},"**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.7847194,{"description":3215,"labels":3216,"number":3217,"owner":3181,"repository":3182,"state":3183,"title":3218,"updated_at":3219,"url":3220,"score":3221},"**Is your feature request related to a problem? Please describe.**\nYes, on the registration of patient, under address section \nnot all patient party or reception have ideas about which local body they are from so which will result in capturing wrong information due to random selection of local body.\nopd queue are large an it will cause problem to the hospital ticket counter.\n\nDescribe the solution you'd like\n1.State should be auto selected to its state.\n2.Ward field should contain all the available ward data of the state.\n3.Based upon this selection i.e ward, **District and Local body** fill box are to be fetched/autopopulated as per the selection based on Ward field .\n\n\u003Cimg width=\"710\" height=\"286\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/79df9ae6-cacf-408b-8446-4492ef5b5356\" />\n",[],13978,"Request of changes on address section of patient registration page.","2025-10-07T10:12:16Z","https://github.com/ohcnetwork/care_fe/issues/13978",0.7953724,{"description":3223,"labels":3224,"number":3225,"owner":3181,"repository":3182,"state":3183,"title":3226,"updated_at":3227,"url":3228,"score":3229},"**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.80044615,{"description":3231,"labels":3232,"number":3233,"owner":3181,"repository":3182,"state":3183,"title":3234,"updated_at":3235,"url":3236,"score":3237},"## Background / Context\n\nCurrently, some workflows in CARE use Sheets for selecting items from a list. While this works, the UX is not optimal for mobile devices.\n- Drawer is a more intuitive pattern for mobile.\n- Command provides a faster and more scalable experience for larger screens.\n\nThis issue aims to standardise all item-selection interactions to use Drawer (on mobile) and Command (on desktop).\n\n- [ ] Identify all usage of Sheets for item selection.\n- [ ] Migrate usages (link sub-issues here)\n\n## Component Checklist\n- [x] [src/components/Questionnaire/ValueSetSelect.tsx](https://github.com/ohcnetwork/care_fe/blob/b33d79b52c528d6086cc177dce85219bf1b106b3/src/components/Questionnaire/ValueSetSelect.tsx#L75).\n- [x] [/src/components/ui/autocomplete.tsx](https://github.com/ohcnetwork/care_fe/blob/93675acdb37759e2957bd299518e6cecdac2f09b/src/components/ui/autocomplete.tsx#L240)\n- [x] [/src/components/Common/RequirementsSelector.tsx](https://github.com/ohcnetwork/care_fe/blob/b33d79b52c528d6086cc177dce85219bf1b106b3/src/components/Common/RequirementsSelector.tsx#L144) -> ( check once with Gigin)\n- [x] [/src/components/Questionnaire/EntitySelectionSheet.tsx](https://github.com/ohcnetwork/care_fe/blob/b33d79b52c528d6086cc177dce85219bf1b106b3/src/components/Questionnaire/EntitySelectionSheet.tsx#L161) -> (check with Gigin) -> This actually uses the `ValueSetSelect` inside and render form inside the sheet.\n- [ ] [/src/components/CareTeam/CareTeamSheet.tsx](https://github.com/ohcnetwork/care_fe/blob/b33d79b52c528d6086cc177dce85219bf1b106b3/src/components/CareTeam/CareTeamSheet.tsx#L219) -> Check with gigin.\n- [ ] [/src/pages/Encounters/AssociateDeviceSheet.tsx](https://github.com/ohcnetwork/care_fe/blob/b33d79b52c528d6086cc177dce85219bf1b106b3/src/pages/Encounters/AssociateDeviceSheet.tsx#L60).\n- [ ] [/src/pages/Facility/settings/organizations/components/FacilityOrganizationSelector.tsx#L424](https://github.com/ohcnetwork/care_fe/blob/b33d79b52c528d6086cc177dce85219bf1b106b3/src/pages/Facility/settings/organizations/components/FacilityOrganizationSelector.tsx#L424)\n- [x] [/src/components/Questionnaire/QuestionnaireSearch.tsx#L123](https://github.com/ohcnetwork/care_fe/blob/41a0118bf0b0d7e6231c8cabf22d4ddd2e7e6b7e/src/components/Questionnaire/QuestionnaireSearch.tsx#L123)\n- [ ] [/src/components/Questionnaire/MedicationValueSetSelect.tsx#L313](https://github.com/ohcnetwork/care_fe/blob/93675acdb37759e2957bd299518e6cecdac2f09b/src/components/Questionnaire/MedicationValueSetSelect.tsx#L313)\n\n\n",[],13754,"Convert all Sheet components used for item selection into Drawer (Mobile) and Popover (Desktop)","2025-10-06T14:08:48Z","https://github.com/ohcnetwork/care_fe/issues/13754",0.80389583,{"description":3239,"labels":3240,"number":3247,"owner":3181,"repository":3182,"state":3248,"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",[3241,3244],{"name":3242,"color":3243},"enhancement","a2eeef",{"name":3245,"color":3246},"UI Component","fef2c0",13756,"closed","Build Facility Level Bed Availability Dashboard for Hospitals","2025-09-18T16:02:44Z","https://github.com/ohcnetwork/care_fe/issues/13756",0.7027131,{"description":3254,"labels":3255,"number":3261,"owner":3181,"repository":3182,"state":3248,"title":3262,"updated_at":3263,"url":3264,"score":3265},"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\" />",[3256,3257,3260],{"name":3172,"color":3173},{"name":3258,"color":3259},"blocked","e50620",{"name":3178,"color":3179},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.7706879,{"description":3267,"labels":3268,"number":3272,"owner":3181,"repository":3182,"state":3248,"title":3273,"updated_at":3274,"url":3275,"score":3276},"From administrative view point, when a nursing supervisor is scheduling care for 'X' number of nurses, nursing supervisor needs to see who all have how many cares already assigned to in a single flow rather than going into each staff's filter. \n\nHence we need a sorting system to have an overall view of all nurses or multiselected nurses and be able to edit in the same view. . \n\n\n\n\u003Cimg width=\"1216\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7a552d8c-96a0-4044-b19a-9e8b528d586d\" />\n\n\u003Cimg width=\"1212\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/9433413d-e6fc-4e1d-a822-51a5b64578a1\" />\n\n ",[3269],{"name":3270,"color":3271},"stale","688388",11593,"Sort/ grouping - for appointments - Administrative perspective","2025-07-30T08:11:13Z","https://github.com/ohcnetwork/care_fe/issues/11593",0.7730442,["Reactive",3278],{},["Set"],["ShallowReactive",3281],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fzLUJm5fSt8KK5MAHfGz_qWwsmEW_VZDKXBmRn0VsEx0":-1},"/ohcnetwork/care_fe/13759"]