\n\n**Desktop (please complete the following information):**\n\n- OS: macOS\n- Browser: ARC \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",[],12695,"Switch to use Table View for Questionnaire and ValueSet Listing Page for medium screen","2025-06-23T14:34:08Z","https://github.com/ohcnetwork/care_fe/issues/12695",0.84410167,{"description":3040,"labels":3041,"number":3045,"owner":3024,"repository":3025,"state":3026,"title":3046,"updated_at":3047,"url":3048,"score":3049},"We are moving towards a modular API structure by migrating all APIs from the centralized routes object to object-specific files like patientApi.ts, encounterApi.ts, etc.\n\nEach sub-task below should be handled in a separate PR, covering 2–3 related entities to keep reviews focused and maintain clarity in the migration process.\n\n\nMigration Checklist\n- [x] Move all Patient and Encounter APIs\nMove all patient-related routes (search, add user, tags, questionnaire, notes, etc.) to patientApi.ts. Move all encounter-related routes to encounterApi.ts. → #12937 \n- [ ] Move all Facility and Department APIs\nMove general facility routes to facilityApi.ts. Add a departmentApi.ts if department-specific APIs emerge. -> #13002 \n- [ ] Move all User and Schedule APIs\nMove user-related endpoints (currentUser, getUserDetails, deleteUser, etc.) to userApi.ts. and schedulable user routes to scheduleApi.ts\n- [ ] Move all Auth APIs\nMove login, logout, password reset/change, and token refresh routes to authApi.ts.\n- [ ] Move all File Upload APIs\nMove file upload-related routes (createUpload, editUpload, archiveUpload, etc.) to fileApi.ts.\n- [ ] Move Resource Request and Comments APIs\nMove all resource request routes and associated comment APIs to resourceApi.ts.\n- [ ] Move Questionnaire, Observation, and Notes APIs\nMove questionnaire response routes to questionnaireApi.ts, observation routes to observationApi.ts, and note/thread/message routes to notesApi.ts.\n- [ ] Move OTP-Based APIs\nMove all OTP-based login and patient creation routes to otpApi.ts.\n- [ ] Move ValueSet, BatchRequest, and PlugConfig APIs\nMove valueset.expand to valueSetApi.ts, batchRequest to batchApi.ts, and plug config routes to plugConfigApi.ts.\n⸻\n\nNotes\n- Ensure deprecated entries in routes are removed or commented with a deprecation notice once moved.\n- Maintain typings and consistent API schema format (TRes, TBody, etc.)\n- Reuse base request utility Type\u003CT>() and standardize where possible\n- Update any importing modules or utilities to use the new API files\n",[3042],{"name":3043,"color":3044},"Development/Refactor","6c7672",12909,"Refactor: Move Remaining APIs from Central `routes` to Object-Specific API Files","2025-07-28T11:45:10Z","https://github.com/ohcnetwork/care_fe/issues/12909",0.84466696,{"description":3051,"labels":3052,"number":3053,"owner":3024,"repository":3025,"state":3026,"title":3054,"updated_at":3055,"url":3056,"score":3057},"https://github.com/user-attachments/assets/f2c6d98c-0662-4642-98f9-1f5c2cfb9fa8\n\n\nSteps to Reproduce:\n- Go to 'Services'\n- Click on 'Laboratory Services'\n- Select any Available Location\n- Click on Location Switcher present in sidebar (refer to the video)\n- see the error \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.",[],13206,"Tooltip remains visible for pagination component","2025-08-01T18:31:47Z","https://github.com/ohcnetwork/care_fe/issues/13206",0.8453525,{"description":3059,"labels":3060,"number":3067,"owner":3024,"repository":3025,"state":3068,"title":3069,"updated_at":3070,"url":3071,"score":3072},"**Is your feature request related to a problem? Please describe.**\nAs of now, when a user who is not logged in tries to access an authenticated/protected route, the application renders the \u003CLogin /> component inline without changing the URL. This can be confusing to the user because the URL still shows the protected route, but the content displayed is the login form.\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",[3061,3064],{"name":3062,"color":3063},"question","d876e3",{"name":3065,"color":3066},"needs-triage","ededed",12669,"closed","Redirect unauthenticated users to /login instead of rendering Login component in-place","2025-06-27T03:25:39Z","https://github.com/ohcnetwork/care_fe/issues/12669",0.8213021,{"description":3074,"labels":3075,"number":3076,"owner":3024,"repository":3025,"state":3068,"title":3077,"updated_at":3078,"url":3079,"score":3080},"**Describe the bug**\n`batch_requests` errors are not properly handled in the frontend causing page crashes\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Settings > Locations > Add Location > Create Multiple Beds Locations'\n2. If you don't have permission you'll see page crash\n\n**Screenshots**\n\n\n\n**Desktop (please complete the following information):**\n- Chrome on Windows 11\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",[],11641,"Permission Errors causing Page Crash","2025-07-30T08:18:44Z","https://github.com/ohcnetwork/care_fe/issues/11641",0.8219467,{"description":3082,"labels":3083,"number":3086,"owner":3024,"repository":3025,"state":3068,"title":3087,"updated_at":3088,"url":3089,"score":3090},"**Describe the bug**\nThere is lack of responsiveness in some sections (Group Layout and Answer Options) of Questionnaire\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/admin/questionnaire/respiratory-support-/edit)\n2. Check different sections on Mobile View\n3. See error\n\n**Expected behavior**\nThere should be proper responsiveness for Mobile devices. Like we can add padding in Title of each field in 'Answer Options' section.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/01725d6b-9867-4b24-af1b-7d8aeaa25b51\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",[3084,3085],{"name":3062,"color":3063},{"name":3065,"color":3066},12486,"'Group Layout options' and 'Answer Options' of Questionnaire needs resposiveness","2025-06-19T05:30:36Z","https://github.com/ohcnetwork/care_fe/issues/12486",0.8230609,{"description":3092,"labels":3093,"number":3094,"owner":3024,"repository":3025,"state":3068,"title":3095,"updated_at":3096,"url":3097,"score":3098},"**Describe the bug**\nPrevent the creation of a Bed location unless a valid parent location is already selected. This ensures proper hierarchical structure and avoids orphaned Bed entries in the system.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to `Location` tab under setting nav\n2. Add on `Add Location` without selecting any parent location\n3. Create a bed type location\n4. See error \n\n**Expected behaviour**\nRemove the Bed form from form options when no parent is present\n\n> [!NOTE]\n> Expected behaviour could be different , this issue needs a review from core members\n\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/0bc62535-0af0-4bd3-97a0-4342e2566611\n\n\n> [!TIP]\n> GOOD FIRST ISSUE depends on expected behaviour decided 👍 \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",[],12664,"Restricting Creating Bed Location when no parent location is present","2025-06-19T19:11:09Z","https://github.com/ohcnetwork/care_fe/issues/12664",0.8240755,{"description":3100,"labels":3101,"number":3102,"owner":3024,"repository":3025,"state":3068,"title":3103,"updated_at":3104,"url":3105,"score":3106},"**Describe the bug**\nWe are able to create same devices multiple times. Since according to FHIR, the registered name for a Device does not have to be unique globally but we should add validations and make some fields required to solve this problem. \nId is generated by backend but we are not able to differentiate same registered name devices (as shown in the video).\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to '...'\n2. Click on '....'\n3. Scroll down to '....'\n4. See error\n\n**Expected behavior**\nWe should able to differentiate devices through id so that same registered name devices can be differentiated.\n\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/a2f2246b-7a11-4470-bcb0-8e4e04eb42db\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",[],12759,"Bug: Add validations to reduce redundancy for devices","2025-06-30T12:03:15Z","https://github.com/ohcnetwork/care_fe/issues/12759",0.824193,{"description":3108,"labels":3109,"number":3118,"owner":3024,"repository":3025,"state":3068,"title":3119,"updated_at":3120,"url":3121,"score":3122},"**Describe the bug**\nUser dropdown in the \"Assign User to Patient\" modal shows all users instead of filtering by current facility.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to '...'\n2. Click on '....'\n3. Scroll down to '....'\n4. See error\n\n**Expected behavior**\nUser dropdown should display only users associated with the current facility.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/c7b9f064-f712-47cd-9188-9b28fa7c40b1\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",[3110,3111,3114,3117],{"name":3062,"color":3063},{"name":3112,"color":3113},"discussion required","05EFF8",{"name":3115,"color":3116},"stale","688388",{"name":3065,"color":3066},12408,"Restrict User Dropdown to Current Facility Users Only in Assign User to Patient Modal","2025-07-31T14:21:54Z","https://github.com/ohcnetwork/care_fe/issues/12408",0.8261306,["Reactive",3124],{},["Set"],["ShallowReactive",3127],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f5xd3otYFEH0ouKj29lOmxWHkp8APw91WAN8Z3uTqGZE":-1},"/ohcnetwork/care_fe/12010"]