\n",[],13978,"ohcnetwork","care_fe","open","Request of changes on address section of patient registration page.","2025-10-07T10:12:16Z","https://github.com/ohcnetwork/care_fe/issues/13978",0.6801895,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"Currently, after setting an encounter status to Discharged, the Discharge Disposition field appears, but the form can still be submitted without selecting any value.\n\nThis creates a gap in data quality, as every patient discharge must have a corresponding reason (discharge disposition). In practice, we have observed that some users (e.g., nurses) skip selecting a discharge disposition and submit the form directly.\n\nTo ensure accurate clinical and operational records, we propose making the Discharge Disposition field mandatory whenever a patient is marked as discharged. This change will:\n\nPrevent incomplete discharge records.\nImprove data consistency for reporting and audits.\nAlign with best practices where discharge reasons are always documented.\n\nProposed Solution :\nMaking Discharge Disposition option a mandatory field, so that the Discharge Disposition field cannot be left blank when encounter status is set to Discharged.\n\n\u003Cimg width=\"890\" height=\"766\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/6ae8d9f7-02d1-4800-bbcd-d592d4f3f5a4\" />",[],13663,"Make Discharge Disposition a mandatory field when marking a patient as discharged","2025-09-09T06:39:31Z","https://github.com/ohcnetwork/care_fe/issues/13663",0.75463825,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"When creating a new Healthcare Service, the Name field label turns red if left blank, while other required fields (e.g., Location) only show the error message below the input. This causes inconsistency in the UI.\n\nhttps://github.com/user-attachments/assets/4b0fdaa0-2a19-40cf-a764-9ba0b1d8ee1e\n\n**Steps to Reproduce**\n1. Go to Healthcare Services → Create new.\n2. Leave all fields empty.\n3. Click Create.\n\n**Expected Behavior**\n- All required fields should behave consistently. Labels should remain neutral, and missing input should be indicated only by the error message below the field.\n\n**Actual Behavior**\n- Name → Label turns red + error message shown.\n- Location → Label stays neutral + error message shown.\n\n---\n🚨 DO NOT EDIT BELOW THIS LINE 🚨\nInstructions for Requesting Assignment:\nTo request assignment, please clearly outline your solution and timeline by commenting on the issue using the format below:\n\nDescribe 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\nExpected Timeline:\n\nEnd date: [Expected submission date of a completed Pull Request]\nAdditional 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\n",[],13485,"Inconsistent Label Highlighting for Required Fields","2025-08-23T14:56:18Z","https://github.com/ohcnetwork/care_fe/issues/13485",0.756892,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**Describe the bug**\n\nCreate a new healthcare service with no location and the custom icon, and try to edit the healthcare services in the facility, the validation error will be thrown for empty fields\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to a facility and create a healthcare services with location and icons as empty\n2. edit the newly created healthcare services other than location or icon field\n3. see the error message\n\n**Expected behavior**\n\nOnly throw validation error on submission for mandatory field or whereever necessary\n\n**Screenshots**\n\n\u003Cimg width=\"1165\" height=\"825\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cf5dd63b-e05f-4ec3-8d3b-88e110003390\" />\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",[],13989,"Validation is malfunctioning in the healthcare service edit page","2025-10-07T13:03:03Z","https://github.com/ohcnetwork/care_fe/issues/13989",0.7635209,{"description":3204,"labels":3205,"number":3215,"owner":3172,"repository":3173,"state":3216,"title":3217,"updated_at":3218,"url":3219,"score":3220},"**Is your feature request related to a problem? Please describe.**\nMake \"ward\" field optional in the patient demography page. Currently the field is mandatory and hospital staff having trouble to fill the field when the patient is not aware about the ward number. \n\n\u003Cimg width=\"294\" height=\"92\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c562cc62-3d08-46d5-ac21-5e89d6471d53\" />\n\n**Describe the solution you'd like**\nMake the ward field optional in the patient registration page\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**\nAdd any other context or screenshots about the feature request here.\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",[3206,3209,3212],{"name":3207,"color":3208},"question","d876e3",{"name":3210,"color":3211},"stale","688388",{"name":3213,"color":3214},"needs-triage","ededed",13034,"closed","Make \"Ward\" field optional in Patient Demography (Registration Page)","2025-08-18T09:29:59Z","https://github.com/ohcnetwork/care_fe/issues/13034",0.6612954,{"description":3222,"labels":3223,"number":3224,"owner":3172,"repository":3173,"state":3216,"title":3225,"updated_at":3226,"url":3227,"score":3228},"**Is your feature request related to a problem? Please describe.**\nThe current patient registration form includes too many mandatory fields, creating friction for call center users in patient registration. Fields from Address till geo org to be made non mandatory \n\n\n**Describe the solution you'd like**\nA clear and concise description of what you want to happen.\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**\nAdd any other context or screenshots about the feature request here.\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",[],12699,"Reduce Number of Mandatory Fields in Patient Registration (For Arike Instance)","2025-06-25T12:04:21Z","https://github.com/ohcnetwork/care_fe/issues/12699",0.72718245,{"description":3230,"labels":3231,"number":3233,"owner":3172,"repository":3173,"state":3216,"title":3234,"updated_at":3235,"url":3236,"score":3237},"**Describe the bug**\nIn the **\"Add Patient Details\"** form, there are two issues:\n1. **Confusing Validation with Address Checkbox**\nWhen the checkbox **\"Use this address for permanent address\"** is selected, and the **Current Address** field is left empty, the form throws a “Required” validation error for **both Current and Permanent Address fields**.\nThis is confusing because the user has opted to use the current address as permanent, yet the validation message make it seem like they are still required to fill both fields manually.\n\n2. **Misaligned \"Required\" Label**\nThe **\"Required\"** label for the **State** field appears visually misaligned compared to other fields in the form.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to \"Add Details of Patient\" form.\n2. Leave the Current Address field empty.\n3. Check the box **\"Use this address for permanent address\"**.\n4. See error\n\n**Expected behavior**\n- If the checkbox is selected, only the Current Address field should show that validation message\n- The **\"Required\"** label for the State field should be properly aligned with the others.\n\n**Screenshots**\n\n\u003Cimg width=\"1012\" height=\"421\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/53514cf7-5581-4143-bd13-1c5cd83b139e\" />\n\n\u003Cimg width=\"917\" height=\"367\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8207c67e-4615-41dd-81c2-0f7798413842\" />\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",[3232],{"name":3210,"color":3211},13303,"Checkbox logic & UI misalignment issues in \"Add Patient Details\" form","2025-10-01T10:37:54Z","https://github.com/ohcnetwork/care_fe/issues/13303",0.74414474,{"description":3239,"labels":3240,"number":3241,"owner":3172,"repository":3173,"state":3216,"title":3242,"updated_at":3243,"url":3244,"score":3245},"**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.75249964,{"description":3247,"labels":3248,"number":3255,"owner":3172,"repository":3173,"state":3216,"title":3256,"updated_at":3257,"url":3258,"score":3259},"**Is your feature request related to a problem? Please describe.**\nIn the patient registration form, users sometimes paste Google Maps URLs into the address field for precise location sharing. However, the URL currently appears as plain text and is not clickable, requiring users to manually copy-paste it into a browser.\n\n**Describe the solution you'd like**\n- Detect if the address field contains a valid URL.\n- Automatically render it as a clickable hyperlink in the patient profile.\n- Optionally, open the link in a new tab to avoid navigation disruption.\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**\nAdd any other context or screenshots about the feature request here.\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",[3249,3252,3253,3254],{"name":3250,"color":3251},"good first issue","7057ff",{"name":3207,"color":3208},{"name":3210,"color":3211},{"name":3213,"color":3214},12556,"Make URL in Address Field Clickable in Patient Registration Form","2025-07-18T07:05:05Z","https://github.com/ohcnetwork/care_fe/issues/12556",0.7535261,{"description":3261,"labels":3262,"number":3263,"owner":3172,"repository":3173,"state":3216,"title":3264,"updated_at":3265,"url":3266,"score":3267},"**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.76216334,["Reactive",3269],{},["Set"],["ShallowReactive",3272],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fiX2-mGLWwsvDJJ9C7BlCiW7JxagjDc9PSYRaOjkN09U":-1},"/ohcnetwork/care_fe/13360"]