\n\u003Cimg width=\"743\" height=\"705\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7f098772-6e61-4754-a5e5-b94b509b11fb\" />\n\u003Cimg width=\"730\" height=\"636\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/990db087-0e47-4f6d-83b5-b90be8ac1d0a\" />\n\n**Proposed Solution**\nAttached screenshot for reference\n\u003Cimg width=\"1110\" height=\"1210\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/94e1fa1c-2e40-48f9-a230-14043a90198d\" />\nRefer the figma file for the correct dimensions https://www.figma.com/design/Z93EYKSa1MdBmXndsMBJSQ/Care?node-id=26304-10329&t=AskluDORl8G3ixs5-1\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",[],13732,"ohcnetwork","care_fe","open","Enhance usability by solving the UI inconsistencies on the \"Add Patient Details\" page","2025-09-17T11:43:03Z","https://github.com/ohcnetwork/care_fe/issues/13732",0.7387209,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Description**: The UI can be improved in the Mobile View\n\n\u003Cimg width=\"325\" height=\"414\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c5466bd8-b3f0-48b4-a49d-18e46a10dc59\" />\n\n\u003Cimg width=\"325\" height=\"414\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/9b96dcca-aa4f-4cdb-85ae-6b3bb2773688\" />\n\n**Steps To Reproduce:**\n- Go to Patients from the sidebar\n- All encounter -> View Encounter of any patient",[],13691,"Improve UI of View Encounter Page in Mobile View","2025-09-12T02:12:32Z","https://github.com/ohcnetwork/care_fe/issues/13691",0.7550047,{"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.7648303,{"description":3196,"labels":3197,"number":3201,"owner":3172,"repository":3173,"state":3202,"title":3203,"updated_at":3204,"url":3205,"score":3206},"**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",[3198],{"name":3199,"color":3200},"good first issue","7057ff",12682,"closed","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.6965237,{"description":3208,"labels":3209,"number":3210,"owner":3172,"repository":3173,"state":3202,"title":3211,"updated_at":3212,"url":3213,"score":3214},"**Describe the bug**\nIn Search Patients page, keyboard shortcuts are visible for mobile view\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Any facility'\n2. Click on 'Patients'\n3. Scroll down to 'Search Patients'\n4. See error\n\n**Expected behavior**\nKeyboard shortcuts should not be visible for mobile phones or tablets\n\n**Screenshots**\n\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**\nIf we can, for device that has external keyboard connected can also be able to see the keyboard shortcuts (Discussion required)\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",[],13639,"Keyboard shortcuts are visible in mobile view","2025-09-07T07:12:26Z","https://github.com/ohcnetwork/care_fe/issues/13639",0.73578054,{"description":3216,"labels":3217,"number":3218,"owner":3172,"repository":3173,"state":3202,"title":3219,"updated_at":3220,"url":3221,"score":3222},"**Describe the bug**\nIn the **Notes** > **Discussion Thread section** of a patient's profile, when viewed on tablet-sized screens, the textarea used for typing a message gets overlapped by the Threads/New Thread block above it.\n\nAs a result:\n- The input area is not fully visible\n- The send icon is partially hidden\n- It creates a poor user experience on mid-sized viewports\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to any Patient Details Page\n2. Click on Notes tab and start a new discussion\n3. resize the screen to tablet view (e.g. 912 X 1368)\n4. See error\n\n**Expected behavior**\nThe message input box should remain fully visible and usable across all screen sizes, with proper spacing to prevent overlap from the discussion thread.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/dcb1a312-4e6e-4282-af11-b1735db845b8\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",[],12991,"Discussion Textarea Not Fully Visible on Medium Screen Sizes","2025-07-23T13:14:24Z","https://github.com/ohcnetwork/care_fe/issues/12991",0.73969495,{"description":3224,"labels":3225,"number":3226,"owner":3172,"repository":3173,"state":3202,"title":3227,"updated_at":3228,"url":3229,"score":3230},"**Describe the bug**\nThere is already a way to close the dialogue (default cross icon ) but still there is a close button. We should remove close button.\n\n\u003Cimg width=\"489\" height=\"390\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b9195c02-0015-4b36-9201-f916f2137685\" />\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/facility/b90bf759-077c-46f4-a916-817f332a5a60/billing/account/a512bd48-5345-4870-91f5-bff99a25371f/payments?page=1&limit=14&ordering=-payment_datetime)\n2. Click on Patient name dropdown in mobile view\n\n\n**Expected behavior**\nA clear and concise description of what you expected to happen.\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",[],13269,"Adjust responsiveness of button in Patient Name Dropdown","2025-08-20T06:19:41Z","https://github.com/ohcnetwork/care_fe/issues/13269",0.75423545,{"description":3232,"labels":3233,"number":3234,"owner":3172,"repository":3173,"state":3202,"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.76216173,{"description":3240,"labels":3241,"number":3242,"owner":3172,"repository":3173,"state":3202,"title":3243,"updated_at":3244,"url":3245,"score":3246},"\u003Cimg width=\"587\" height=\"169\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2fc61d3d-6830-41e4-87d8-317ee6d767fe\" />",[],12808,"Add support for clearing radio input's selection","2025-07-10T08:02:53Z","https://github.com/ohcnetwork/care_fe/issues/12808",0.76229054,{"description":3248,"labels":3249,"number":3256,"owner":3172,"repository":3173,"state":3202,"title":3257,"updated_at":3258,"url":3259,"score":3260},"**Describe the bug**\nWhen registering a patient, if DOB and Age fields are filled with values that differ by more than 1 year (for example, DOB = 2007 and Age = 90), the form allows submission.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Patient Registration'.\n2. Fill in the DOB field with a date (2007).\n3. Fill in the Age field with a value (90)\n4. See error, form get submitted.\n\nhttps://github.com/user-attachments/assets/751eb169-66b8-4a66-953e-86787d333001\n\n**Expected behavior**\nWhen the entered Age and the Age calculated from the Date of Birth differ by more than 1 year, the form should display a validation message saying \"Age does not match the date of birth. Please correct one of them.\"\n\nhttps://github.com/user-attachments/assets/69d00e36-d15f-4020-a5ef-c28db71245e1\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",[3250,3253],{"name":3251,"color":3252},"question","d876e3",{"name":3254,"color":3255},"needs-triage","ededed",12692,"Age and Date of Birth Mismatch Not Blocking Patient Registration Submission","2025-06-27T03:23:08Z","https://github.com/ohcnetwork/care_fe/issues/12692",0.76256067,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fS9KIttxUqzd1_OFRlywCxrh1SZFRl6OUbG4i_EEYsdw":-1},"/ohcnetwork/care_fe/13023"]