\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",[],13022,"Make Buttons on User Dashboard responsive for mobile view","2025-07-21T18:35:02Z","https://github.com/ohcnetwork/care_fe/issues/13022",0.7315214,{"description":3043,"labels":3044,"number":3045,"owner":3019,"repository":3020,"state":3021,"title":3046,"updated_at":3047,"url":3048,"score":3049},"**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.73725694,{"description":3051,"labels":3052,"number":3053,"owner":3019,"repository":3020,"state":3021,"title":3054,"updated_at":3055,"url":3056,"score":3057},"\n\n\u003Cimg width=\"1440\" height=\"897\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/725b6347-d7e4-433b-ae5e-b5b5415d4e72\" />\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Go to any live encounter\n- go to medication request question\n- see the error for tablet screen size \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",[],13095,"Medication Request Question UI is breaking on tablet screens","2025-07-25T18:35:09Z","https://github.com/ohcnetwork/care_fe/issues/13095",0.74848366,{"description":3059,"labels":3060,"number":3073,"owner":3019,"repository":3020,"state":3074,"title":3075,"updated_at":3076,"url":3077,"score":3078},"**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",[3061,3064,3067,3070],{"name":3062,"color":3063},"good first issue","7057ff",{"name":3065,"color":3066},"question","d876e3",{"name":3068,"color":3069},"stale","688388",{"name":3071,"color":3072},"needs-triage","ededed",12556,"closed","Make URL in Address Field Clickable in Patient Registration Form","2025-07-18T07:05:05Z","https://github.com/ohcnetwork/care_fe/issues/12556",0.55241895,{"description":3080,"labels":3081,"number":3082,"owner":3019,"repository":3020,"state":3074,"title":3083,"updated_at":3084,"url":3085,"score":3086},"**Is your feature request related to a problem? Please describe.**\nThe buttons are all congested and sometimes fall outside the viewport on mobile. Even when they are within the viewport, they can be misaligned and look awkward.\n\n**Additional context**\n\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",[],12526,"Enhance the UI of the patient encounters file menu for mobile screens","2025-06-06T05:25:50Z","https://github.com/ohcnetwork/care_fe/issues/12526",0.69922996,{"description":3088,"labels":3089,"number":3094,"owner":3019,"repository":3020,"state":3074,"title":3095,"updated_at":3096,"url":3097,"score":3098},"**Is your feature request related to a problem? Please describe.**\nCurrently, on the encounter listing page:\n\n1. Clicking the patient name navigates to the patient’s profile.\n\n2. Clicking the \"View Details\" button navigates to the encounter details.\n\nHowever, this behavior is not immediately intuitive for users. It would be clearer and more user-friendly to have explicitly labeled buttons for both actions.\n\n**Describe the solution you'd like**\nAdd two clearly labeled buttons for each encounter row:\n1. \"Visit Patient Profile\"\n2. \"Visit Encounter Details\"\n\nUse icons or color differentiation (optional) to help users quickly recognize actions.\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",[3090,3091],{"name":3062,"color":3063},{"name":3092,"color":3093},"P1","519BFE",12555,"Add Clear Action Buttons for \"Visit Patient Profile\" and \"Visit Encounter\" on Encounter Listing Page","2025-06-16T13:43:59Z","https://github.com/ohcnetwork/care_fe/issues/12555",0.71750647,{"description":3100,"labels":3101,"number":3102,"owner":3019,"repository":3020,"state":3074,"title":3103,"updated_at":3104,"url":3105,"score":3106},"**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,"Position Patient Registration form at centre","2025-07-16T14:58:32Z","https://github.com/ohcnetwork/care_fe/issues/12894",0.722507,{"description":3108,"labels":3109,"number":3110,"owner":3019,"repository":3020,"state":3074,"title":3111,"updated_at":3112,"url":3113,"score":3114},"**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.72290176,["Reactive",3116],{},["Set"],["ShallowReactive",3119],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fKEKcuum0pgouvxmySyJh-89-ZGU6qApN-TpQtX7GIVE":-1},"/ohcnetwork/care_fe/12407"]