\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-08-05T05:55:59Z","https://github.com/ohcnetwork/care_fe/issues/13022",0.7289673,{"description":3128,"labels":3129,"number":3134,"owner":3083,"repository":3084,"state":3094,"title":3135,"updated_at":3136,"url":3137,"score":3138},"**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",[3130,3131],{"name":3103,"color":3104},{"name":3132,"color":3133},"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.72959954,{"description":3140,"labels":3141,"number":3144,"owner":3083,"repository":3084,"state":3094,"title":3145,"updated_at":3146,"url":3147,"score":3148},"**Is your feature request related to a problem? Please describe.**\ncurrently the Google Location (URL) in the patient update form is displayed as plain text and is not clickable.\n\n**Describe the solution you'd like**\nRender the Google Location (URL) as a clickable hyperlink in the patient update form\n\n**Additional context**\n\nhttps://github.com/user-attachments/assets/4da01e39-2b41-4a6f-a625-091bdd9a2dc2\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",[3142,3143],{"name":3106,"color":3107},{"name":3112,"color":3113},12407,"Make Google Location (URL) Clickable in Patient Update Form on Patient Details Page","2025-05-30T10:21:10Z","https://github.com/ohcnetwork/care_fe/issues/12407",0.73196614,{"description":3150,"labels":3151,"number":3152,"owner":3083,"repository":3084,"state":3094,"title":3153,"updated_at":3154,"url":3155,"score":3156},"**Is your feature request related to a problem? Please describe.**\n\nCurrently, the layout of questionnaire responses on the patient dashboard looks clumpy and difficult to read through. ( requested by NCG doctors)\n\n\u003Cimg width=\"518\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e9c68069-7991-4f9a-ba3a-383fedbb9bc4\" />\n\n**Describe the solution you'd like**\n\nThe question titles should be on the left and the responses should come on the right-hand side. refer the below picture\n\n\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**\nDoctors use the above mentioned section to understand the patient's clinical condition. this acts as a case summary for the patient. So the clubbed together format doesnt help them to asses it easily. Titles on left and contents on right format makes it better for the doctors to read through. \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",[],12223,"Improve the questionnaire visualisation on patient dashboard","2025-06-09T06:41:24Z","https://github.com/ohcnetwork/care_fe/issues/12223",0.74813765,{"description":3158,"labels":3159,"number":3166,"owner":3083,"repository":3084,"state":3094,"title":3167,"updated_at":3168,"url":3169,"score":3170},"**Is your feature request related to a problem? Please describe.**\nA clear and concise description of what the problem is. Ex. I'm always frustrated when [...]\n( Reqeusted by NCG doctor) \nImprove the radio button options on questionnaires. The current version on the users interface is not fully usefull on some scenarios. They are looking for a simple radio button options to select. \n\n**Describe the solution you'd like**\nA clear and concise description of what you want to happen.\n\n\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",[3160,3161,3164,3165],{"name":3106,"color":3107},{"name":3162,"color":3163},"discussion required","05EFF8",{"name":3109,"color":3110},{"name":3112,"color":3113},12175,"Improve radio button options on questionnaries","2025-06-20T14:59:43Z","https://github.com/ohcnetwork/care_fe/issues/12175",0.74859273,{"description":3172,"labels":3173,"number":3174,"owner":3083,"repository":3084,"state":3094,"title":3175,"updated_at":3176,"url":3177,"score":3178},"**Describe the bug**\nOn the Patient Identifier Config page, the “Add Patient Identifier Config” button is not responsive in mobile view.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. login as superadmin\n2. click on admin dashboard\n3. in sidebar , click on Patient Indenfier config\n4. Adjust the Screen view to the mobile view\n5. see error\n\n**Expected behavior**\nMove the Add Patient Identifier Config in the new line for mobile view\n\n**Screenshots**\n\n\u003Cimg width=\"703\" height=\"759\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7b7403b6-a1e4-45a6-bbd3-d1eb510319ff\" />\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",[],13027,"“Add Patient Identifier Config” Button Not Responsive on Mobile View","2025-07-23T16:32:22Z","https://github.com/ohcnetwork/care_fe/issues/13027",0.7513381,{"description":3180,"labels":3181,"number":3182,"owner":3083,"repository":3084,"state":3094,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Is your feature request related to a problem? Please describe.**\nYes. Move the create/add button in the new line of these pages:\n\n- [ ] Specimen Definitions\n- [ ] Observation Definitions\n- [ ] Activity Definitions\n- [ ] Charge Item Definitions\n- [ ] Product Knowledge\n- [ ] Products\n\n**Describe the solution you'd like**\n\n**Current:**\n\n\u003Cimg width=\"295\" height=\"428\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e19ce449-17eb-4985-a8d2-25256efc23d3\" />\n\n**Expected:**\n\n\u003Cimg width=\"295\" height=\"428\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/6fe4652a-5269-4fb9-9d1c-39e4873c2612\" />\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",[],12924,"Improve UI by moving the create/add button of Definition Pages (Activity Definitions, Specimen Definitions etc) in a seperate line","2025-07-23T06:39:18Z","https://github.com/ohcnetwork/care_fe/issues/12924",0.75136465,["Reactive",3188],{},["Set"],["ShallowReactive",3191],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fxltMly-7KHLG9H3Y34RE1MwwMaa1wDaj4olZde5axKk":-1},"/ohcnetwork/care_fe/13530"]