\n\n1) Create a questionnaire with decimal / integer type \n2) Access the questionnaire from encounter section of patient.\n3) Try inputting the field of decimal and integer type with \"e\".\n4) It will show an error message as \" This field is required\" instead of \" Invalid input type \"\n\nEXPECTED BEHAVIOR\nThe system should return an error message like:\n“Please enter a valid number” or “Input must be an integer/decimal”\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",[],12970,"ohcnetwork","care_fe","open","Incorrect error message when wrong input type is entered in questionnaire (e.g., string in decimal/integer field)","2025-07-17T12:25:43Z","https://github.com/ohcnetwork/care_fe/issues/12970",0.6906871,{"description":3028,"labels":3029,"number":3030,"owner":3020,"repository":3021,"state":3022,"title":3031,"updated_at":3032,"url":3033,"score":3034},"**Is your feature request related to a problem? Please describe.**\nYes, as of now in the `Patient Identifier Config` and `Tag config`, while **creating** a new or **editing** the Patient Identifier Config Form and Tag config Form, even if there are no changes are made while editing or no values are entered or selected while creating the respective **Button** stays enables. This creates a false sense of action and could lead to confusion or unnecessary backend operations.\n\n**Describe the solution you'd like**\nWe should disable the button while creating and updating until any required changes are made\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/6e51e145-34f5-4120-b8d0-bd55fc5fc950\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",[],13115,"Disable Submit Button Until Valid Changes Are Made in Config Forms","2025-07-28T08:05:55Z","https://github.com/ohcnetwork/care_fe/issues/13115",0.72761786,{"description":3036,"labels":3037,"number":3038,"owner":3020,"repository":3021,"state":3022,"title":3039,"updated_at":3040,"url":3041,"score":3042},"**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\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",[],12774,"Trans In & Trans Out options in Admit Source and Discharge Disposition, respectively","2025-07-02T08:19:30Z","https://github.com/ohcnetwork/care_fe/issues/12774",0.7499531,{"description":3044,"labels":3045,"number":3046,"owner":3020,"repository":3021,"state":3022,"title":3047,"updated_at":3048,"url":3049,"score":3050},"**Describe the bug**\nWhen we are entering values in pricing components, it is expecting string values as input but it should be number.\n\nhttps://github.com/user-attachments/assets/c3fb6dfd-e92a-4f59-972f-925fab32ad35\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 add zod validation so that pricing component receive numbers as an input.\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",[],13148,"Bug: Add correct zod validation for pricing components in create charge item definition sheet","2025-07-30T06:03:22Z","https://github.com/ohcnetwork/care_fe/issues/13148",0.7510557,{"description":3052,"labels":3053,"number":3054,"owner":3020,"repository":3021,"state":3022,"title":3055,"updated_at":3056,"url":3057,"score":3058},"**Describe the bug**\nWhen we are removing a field and trying to add it back in patient information section, we are not able to add it.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/facility/2fbb0809-b62c-4c53-816e-f1404f096c5e/settings/reportbuilder/new)\n2. Click on Section Tab\n3. Remove a field and try to add it back\n4. See error\n\n**Expected behavior**\nUser should able to add field\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/26eece7a-a1aa-4425-9c19-06bd23612861\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",[],12477,"Bug: User is not able to add field in Patient Information section of Report Template Builder","2025-06-01T11:01:17Z","https://github.com/ohcnetwork/care_fe/issues/12477",0.75159746,{"description":3060,"labels":3061,"number":3062,"owner":3020,"repository":3021,"state":3022,"title":3063,"updated_at":3064,"url":3065,"score":3066},"**Describe the bug**\nIn the Patient details form when a user accidentally clicks on patient deceased checkbox and then toggles it after a validation error the form is not getting submitted. This creates confusion among users\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Patient Detail form\n2. See error\n\nhttps://github.com/user-attachments/assets/2d624192-0fa9-4a9d-b268-763df55dd02c\n\n**Expected behavior**\nWhen we click on the deceased checkbox accidentally and submit and then toggle the checkbox and then submit the form must get submitted and the validation error must be cleared on toggling the checkbox\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",[],13162,"Patient deceased date time validation error message is not getting cleared even after the deceased checkbox is not marked","2025-07-30T10:53:50Z","https://github.com/ohcnetwork/care_fe/issues/13162",0.75361407,{"description":3068,"labels":3069,"number":3070,"owner":3020,"repository":3021,"state":3022,"title":3071,"updated_at":3072,"url":3073,"score":3074},"**Describe the bug**\nWhen we are searching using different options, it is showing no entries with the phone number for all options.\nAlso Aadhar number is only numeric but user is able to enter text content.\n\nhttps://github.com/user-attachments/assets/4a003557-890b-4885-81c3-acaa38a542e8\n\n\n**Expected behavior**\nWe can render a generalize text for different options\nAadhar number should be restricted to numeric just like the phone number.\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",[],13006,"Bug: Generalise the text when there is no entry for a search input in Patient earch","2025-07-21T05:07:46Z","https://github.com/ohcnetwork/care_fe/issues/13006",0.75556445,{"description":3076,"labels":3077,"number":3078,"owner":3020,"repository":3021,"state":3079,"title":3080,"updated_at":3081,"url":3082,"score":3083},"**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.7186115,{"description":3085,"labels":3086,"number":3090,"owner":3020,"repository":3021,"state":3079,"title":3091,"updated_at":3092,"url":3093,"score":3094},"**Describe the bug**\nThe keyword field on the public patient registration page currently uses the normal keyboard on mobile devices, making it less user-friendly for numeric input. This causes friction for users expected to enter numbers for age\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Login as Patient with otp : 45612\n2. Click on `Book Appointment`\n3. Book a slot where you would see Add Patient button which opens up Registration page \n4. See error\n\n**Expected behavior**\nIt should have numpad (like numpad shown in video for date field) instead of normal keyword to prevent unwanted problems\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/f030b51f-1827-444e-a4d9-36f0d230a4b9\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",[3087],{"name":3088,"color":3089},"good first issue","7057ff",12682,"Update the input mode to numpad for Age Input in Public Patient Registration Form","2025-06-25T10:24:47Z","https://github.com/ohcnetwork/care_fe/issues/12682",0.7247317,{"description":3096,"labels":3097,"number":3098,"owner":3020,"repository":3021,"state":3079,"title":3099,"updated_at":3100,"url":3101,"score":3102},"**Describe the bug**\nUI is congested when we are enabling conditions in patient death form questionnaire. The three fields i.e. Question, Operator and Answer are degrading the user experience.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/admin/questionnaire/death-form12/edit)\n2. Go to Death Time Question and Click on 'Enable when conditions'\n3. See in mobile view\n4. See error\n\n**Expected behavior**\nAll three fields should be in separate line so that user can see what he is typing. \n\n**Screenshots**\n\n\u003Cimg width=\"254\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/4212fb65-a7cf-4b70-b20b-f779634e6a64\" />\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",[],12530,"Bug: Misalignment in fields of Death Time form of Patient Death Form Questionnaire","2025-06-09T02:34:27Z","https://github.com/ohcnetwork/care_fe/issues/12530",0.7297366,["Reactive",3104],{},["Set"],["ShallowReactive",3107],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fXOHz1_5XRCdZ7MtLv1v2BAQx-tfL0gYdd-Y9_1dyafQ":-1},"/ohcnetwork/care_fe/12775"]