\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",[],13629,"ohcnetwork","care_fe","open","Gender field can be deselected, shows wrong error","2025-09-05T14:19:22Z","https://github.com/ohcnetwork/care_fe/issues/13629",0.7046167,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Describe the bug**\nThere are couple of bugs in the Product Knowledge form\n- currently `Name` field shows generic 'Required' instead of `Name is required` message\n- in the UI, `Base Unit` is marked as required field but when left empty, no required message shown in the UI.\n- even though `definitional` is optional, still while creating the form, `Dosage Form` shows required message. \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**\nA clear and concise description of what you expected to happen.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/10ec5758-79f1-439c-85b4-52f28a2e20e9\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",[],14023,"validation issues in Product Knowledge form","2025-10-09T18:15:22Z","https://github.com/ohcnetwork/care_fe/issues/14023",0.72149146,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**Describe the bug**\nOn the **Appointments** page, the Search Patients feature has two options:\n1. Search by Patient Name\n2. Search by Phone Number\n\nCurrently:\n- In Search by Phone Number, users can enter strings (letters/characters).\n- In Search by Patient Name, users can enter numbers (like phone numbers).\n\nThis causes confusion and allows invalid searches.\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Appointments → Search Patients.\n2. Select Search by Phone Number.\n3. Enter a string (e.g., \"abcd\").\n4. Observe that the input is accepted.\n5. Switch to Search by Patient Name and enter a number (e.g., \"9876543210\").\n6. Observe that the input is also accepted.\n\n**Expected behavior**\n- Search by Phone Number: Should restrict input to **digits** only.\n- Search by Patient Name: Should restrict input to **letters** only.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/bc154bf6-8c6b-45b1-8bcc-fe0cf38be727\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",[],13953,"Patient Search Input Allows Invalid Data Types","2025-10-03T16:20:16Z","https://github.com/ohcnetwork/care_fe/issues/13953",0.7296807,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**Describe the bug**\nThere are inconsistent and incorrect validation behaviors in the **Create Schedule Template form**:\n1. Whitespace bypasses required fields\n- Fields like Template Name and Session Title accept whitespace as valid input.\n- Example: entering `\" \"` clears the validation error `\"This field is required\"`.\n\n2. Numeric fields show technical error messages\n- Fields like Slot Duration and Patients per Slot display `\"Expected number, received null\"` when left empty.\n- This is confusing for users and not consistent with other required fields that show `\"This field is required\"`.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Open Create Schedule Template form.\n- Leave Template Name and Session Title empty → `\"This field is required\"` error appears.\n- Enter only spaces in these fields → error disappears incorrectly.\n- Leave Slot Duration or Patients per Slot empty → error shows `\"Expected number, received null\"`.\n\n**Expected behavior**\n- Whitespace-only input should be treated as empty and trigger `\"This field is required\"`.\n- Numeric fields should also display a user-friendly message like `\"This field is required\"` instead of technical error text.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/32c48372-f924-484d-8555-d868f78b6eea\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",[],13694,"Validation Issues in Create Schedule Template Form","2025-09-12T09:37:28Z","https://github.com/ohcnetwork/care_fe/issues/13694",0.7341028,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3207,"title":3208,"updated_at":3209,"url":3210,"score":3211},"**Describe the bug**\nWhen using number input fields (`type=\"number\"`), users can enter the scientific notation character 'e' (or 'E'), which is not desired behavior for fields like dates, pincodes, and age inputs.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to any form\n2. Click on number only input\n3. Type 'e'\n4. See error\n\n**Expected behavior**\n- Number input fields should only accept digits (0-9)\n- Scientific notation characters ('e', 'E') should be prevented\n- This is especially important for fields like dates, pincodes, and age where scientific notation is not meaningful\n\n**Screenshots**\n\n\n\n**Desktop (please complete the following information):**\n\n- OS: Fedora\n- Browser: Brave\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",[],12545,"closed","Bug: Scientific notation 'e' character can be entered in number input fields","2025-06-09T10:16:08Z","https://github.com/ohcnetwork/care_fe/issues/12545",0.66510975,{"description":3213,"labels":3214,"number":3215,"owner":3172,"repository":3173,"state":3207,"title":3216,"updated_at":3217,"url":3218,"score":3219},"**Describe the bug**\nVitals fields like respiratory rate, Pulse, Temperature, and blood pressure are taking a few characters as input along with an integer.\n----------SS----------------\n\n\n\nNot able to submit the form with a character as an input in these fields, but even after correcting that particular field, the \"Submit \" button is not available until we refresh the page, which will clear all the other entered data from the form.\n\n----------SS--------\n\n\n\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [https://care.coronasafe.in/facility/d95bf507-055d-403f-acd3-3d331c735140/patient/043edc74-22b9-4efe-b8d7-2695eacb6917/encounter/131ed06a-abbc-4ed9-b9df-ca594e58148c/questionnaire/icuconsultation](url)\n2. Use Credentials: Username: jamesnurse\n Password: James@123\n3. Scroll down to 'Vitals.'\n4. Give input character \"e\" in any fields from vitals.\n5. Add other mandatory fields and submit.\n6. See the error by scrolling to the bottom of the page.\n7. Correct these Vitals fields with integers only and submit again.\n8. \"Submit\" button wont work until the page is refreshed. \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",[],12775,"Vitals fields from ICU Consultation form is taking String as a input of instead of Integer only","2025-07-02T10:23:06Z","https://github.com/ohcnetwork/care_fe/issues/12775",0.6878517,{"description":3221,"labels":3222,"number":3226,"owner":3172,"repository":3173,"state":3207,"title":3227,"updated_at":3228,"url":3229,"score":3230},"**Describe the bug**\nWhen adding or editing a question in the questionnaire form:\n- Selecting a structure_type (e.g., MedicationRequest) initially is not saved correctly.\n- If the question's type is later changed to one that should not have a structure_type, the previously selected structure_type is still sent to the backend and saved, even though it should be cleared.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Admin dashboard \n2. Create questionnaire form:\n3. Add question \n4. select question type structure and structure_type (don't save)\n5. then change type of question\n6. See error**Expected behavior**\nA clear and concise description of what you expected to happen.\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",[3223],{"name":3224,"color":3225},"stale","688388",12182,"structure_type persists incorrectly when changing question type in Questionnaire Form","2025-07-30T11:09:22Z","https://github.com/ohcnetwork/care_fe/issues/12182",0.70185524,{"description":3232,"labels":3233,"number":3240,"owner":3172,"repository":3173,"state":3207,"title":3241,"updated_at":3242,"url":3243,"score":3244},"**Description:**\n\nWhile submitting a questionnaire form with all required and correctly formatted input fields, the application incorrectly showed a validation error to the user. However, upon checking the Network tab in Chrome DevTools, the actual API response showed:\n\nHTTP Status Code: 400\n\nResponse Body: Contains a server-side error message with a status code of 500\n\nThis suggests a discrepancy between front-end validation feedback and the actual server error, possibly due to improper error handling or response mapping.\n\n**Steps to Reproduce:**\n\n\u003Cimg width=\"1919\" height=\"852\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3b5539d9-83ec-4b98-8293-c261d72036f4\" />\n\nNavigate to the questionnaire submission page.\n\nFill in all fields with valid and required input.\n\nClick on the Submit button.\n\nObserve that a validation error is displayed on the UI.\n\nOpen DevTools (F12) → Go to the Network tab.\n\nCheck the failed API request related to the submission.\n\nNote:\n\nStatus shown in DevTools: 400 Bad Request\n\nAPI response body: contains a server error message with internal status 500\n\nExpected Behavior:\n\nThe questionnaire should submit successfully if all fields are valid. If there is a server-side failure, it should show an appropriate server error message.\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",[3234,3237],{"name":3235,"color":3236},"question","d876e3",{"name":3238,"color":3239},"needs-triage","ededed",12992,"Shown validation error while submitting a questionnaire","2025-07-31T13:22:53Z","https://github.com/ohcnetwork/care_fe/issues/12992",0.70468086,{"description":3246,"labels":3247,"number":3248,"owner":3172,"repository":3173,"state":3207,"title":3249,"updated_at":3250,"url":3251,"score":3252},"**Describe the bug**\nWhen a questionnaire is imported using a valid JSON file, the form fields appear to be populated correctly. However, upon clicking \"Save,\" the system displays validation errors in questions field even tho value is there, and the questionnaire cannot be saved. \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Click on \"Create Questionnaire\"\n2. Click on \"Import from URL\"\n3. Enter a raw JSON URL file, import and try to save it\n4. See error\n\n**Expected behavior**\nShould be able to save a successfully imported JSON.\n\n**Screenshots**\n\u003Cimg width=\"1447\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a57de29c-ae33-43bb-8e70-fb4dcd02416a\" />\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",[],12438,"Unable to Save Questionnaire After Importing from JSON File","2025-05-30T08:11:15Z","https://github.com/ohcnetwork/care_fe/issues/12438",0.7089909,{"description":3254,"labels":3255,"number":3258,"owner":3172,"repository":3173,"state":3207,"title":3259,"updated_at":3260,"url":3261,"score":3262},"**Describe the bug**\nWhen submitting the consent form without selecting a \"permit\" or \"deny\" decision, the application displays a generic or technical error message: Invalid enum value. Expected 'permit' | 'deny', received ''\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Consents in Encounters'\n2. Click on 'Add Consent'\n3. Deselect permit\n4. See error\n\n**Expected behavior**\nShould be an understandable error message\n\n**Screenshots**\nIf applicable, add screenshots to help explain your problem.\n\nhttps://github.com/user-attachments/assets/838ec357-20fe-49ec-8632-50a769d041df\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",[3256,3257],{"name":3235,"color":3236},{"name":3238,"color":3239},13323,"Technical error message shows up for Consent Decision","2025-08-11T10:29:41Z","https://github.com/ohcnetwork/care_fe/issues/13323",0.7128939,["Reactive",3264],{},["Set"],["ShallowReactive",3267],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fbt9i1xD-bB4FDpnFqBlX9KNDdOAkGAG92CfgHv19vmc":-1},"/ohcnetwork/care_fe/12970"]