\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",[],13274,"ohcnetwork","care_fe","open","Fix the spacing in the patient notes post submission ( Patient encounter & details page )","2025-08-06T07:02:56Z","https://github.com/ohcnetwork/care_fe/issues/13274",0.7075392,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"## Describe \nOn referring to video attached below, you would observe there is unnecessary blank space present only for Notes tab on Patient home page which can be filled \n\nhttps://github.com/user-attachments/assets/dfe108f5-3152-4c81-b0e7-19d2b7f45417\n\n## Expected \nEither we can show Actions like we are showing for every other tab or increase the width of messaging block to cover the space \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",[],13224,"Blank space on right side of notes tab in patient home page","2025-08-03T10:41:42Z","https://github.com/ohcnetwork/care_fe/issues/13224",0.71542114,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**Describe the bug**\nIn patient home page, there is a `Patient Home` which is redundant as user is already in patient home\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Search Patient'\n2. Click on 'any patient'\n3. Scroll down to 'Patient Home'\n4. See error\n\n**Expected behavior**\nRemove the dummy button\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/91356053-40b3-477c-ad60-0ca9aad3cc97\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",[],14009,"Dummy button in patient details page","2025-10-08T23:43:54Z","https://github.com/ohcnetwork/care_fe/issues/14009",0.72430736,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**Describe the bug**\nUnnecessary whole page scroll is coming up for medium screen despite having enough space and it is fine for smaller and large screen \n\n**To Reproduce**\nSteps to reproduce the behaviour:\n\n1. Go to any facility\n2. Go to Encounters tab\n3. Click on View Patient for any encounter\n4. See error\n\n**Expected behaviour**\nRemove this unnecessary scrolling\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/b317823c-9d8d-4d47-95df-e81f28b23edd\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",[],12960,"Remove unnecessary scroll for patient detail page on medium screen","2025-07-16T19:58:11Z","https://github.com/ohcnetwork/care_fe/issues/12960",0.72675586,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3207,"title":3208,"updated_at":3209,"url":3210,"score":3211},"**Describe the bug**\nCurrently, Patient registration form is not positioned at centre which doesn't look good as per UI and also cause a lot of empty space at right side of it \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'search patient tab'\n2. Click on 'Add patient'\n3. See error\n\n**Screenshots**\n\n\u003Cimg width=\"1440\" height=\"900\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2b09b374-442b-4b82-9288-e74bcbf7680f\" />\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",[],12894,"closed","Position Patient Registration form at centre","2025-07-16T14:58:32Z","https://github.com/ohcnetwork/care_fe/issues/12894",0.6726216,{"description":3213,"labels":3214,"number":3218,"owner":3172,"repository":3173,"state":3207,"title":3219,"updated_at":3220,"url":3221,"score":3222},"**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",[3215],{"name":3216,"color":3217},"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.67902195,{"description":3224,"labels":3225,"number":3226,"owner":3172,"repository":3173,"state":3207,"title":3227,"updated_at":3228,"url":3229,"score":3230},"**Describe the bug**\nIn the **Patient Create Form**, the following required fields:\n- Name\n- Current Address \n- Permanent Address\n\nare accepting whitespace-only input (e.g. `\" \"`). Despite being marked as required, the form still allows submission and creates the patient record, saving empty looking values for those fields.\n\nThis breaks the required field validation logic.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Patient Section\n2. Click on Add New patient\n3. Fill the form \n4. See error\n\n**Expected behavior**\nIf a user enters only whitespace in any required field, it should be treated the same as leaving it empty:\n- A validation error should appear (e.g. “This field is required”)\n- The form should not be submitted until valid text is entered\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/eb0cbc78-093f-460a-9b46-a393e4533e7e\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",[],12948,"Whitespace Bypasses Required Validation in Patient Form Fields","2025-07-21T08:05:07Z","https://github.com/ohcnetwork/care_fe/issues/12948",0.69417167,{"description":3232,"labels":3233,"number":3234,"owner":3172,"repository":3173,"state":3207,"title":3235,"updated_at":3236,"url":3237,"score":3238},"**Describe the bug**\nIn the **Patient Identifier Config** form and **Tag Config** Form, required fields like `Display`, `Description`, `System` and `Slug` accept only whitespace as valid input. This results in entries that appear blank but still pass validation.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Log in as Super admin\n2. Go to Patient Identifier Config Form or Tag Config Form\n3. Add whitespaces to required field\n4. See error\n\n**Expected behavior**\nWhitespace-only input should be treated as empty. These fields should trigger a **\"Required\"** validation error if the input contains only spaces.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/6df1a10f-c285-44a0-b62a-2a3d23340b8f\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",[],13312,"Whitespace Bypasses Validation in Required Fields in Config Forms","2025-08-22T11:20:01Z","https://github.com/ohcnetwork/care_fe/issues/13312",0.6957889,{"description":3240,"labels":3241,"number":3242,"owner":3172,"repository":3173,"state":3207,"title":3243,"updated_at":3244,"url":3245,"score":3246},"**Describe the bug**\nIn the newly created appointments view, the badge text spacing is not even. There is more space in the top compare to the bottom.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Appointments'\n2. See error\n\n**Expected behavior**\nThe y-space should be equal.\n\n**Screenshots**\n\n\u003Cimg width=\"1338\" height=\"406\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/41525077-93c0-48dc-a531-26fd89b29bf1\" />\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",[],13051,"Uneven Vertical Padding in Badge Text on Appointments View","2025-08-13T18:01:02Z","https://github.com/ohcnetwork/care_fe/issues/13051",0.70423025,{"description":3248,"labels":3249,"number":3256,"owner":3172,"repository":3173,"state":3207,"title":3257,"updated_at":3258,"url":3259,"score":3260},"**Describe the bug**\nThe **Date of Birth** input component currently allows users to enter unrestricted character lengths (e.g., more than 2 digits for day or month, and more than 4 digits for year). \n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Facility' > 'Patient' > 'Search patient'\n2. Click on 'Add New Patient'\n3. Scroll down to 'Date of Birth'\n4. Type as much as digits you want in that DD MM YY fields.\n\n**Expected behavior**\n\n- The \"Day\" input should restrict input to 2 digits only.\n- The \"Month\" input should also restrict to 2 digits.\n- The \"Year\" input should be limited to 4 digits, ideally up to the current year.\n- After entering 2 digits in Day and Month fields, the cursor should automatically move to the next input field to improve UX.\n\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/6eb06855-70dd-447c-a7f5-fa4c0e10aac8\n\n**Desktop (please complete the following information):**\n\n- OS: Windows 11\n- Browser chrome\n- Version 115+\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**\nAdditionally will have to add auto-focus behavior between fields so that the cursor automatically move to \"MM\", and then to \"YYYY\", otherwise it will affects user experience.\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",[3250,3253],{"name":3251,"color":3252},"question","d876e3",{"name":3254,"color":3255},"needs-triage","ededed",13289,"Bug: Date of Birth (DOB) Inputs Allow Unlimited Characters - In Create New Patient Form","2025-08-08T04:12:59Z","https://github.com/ohcnetwork/care_fe/issues/13289",0.7089963,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fii7y3I45vqwEYr7_00_KIE1J6ory7CkXE-DZVoGM9ck":-1},"/ohcnetwork/care_fe/13824"]