\n\n**Describe the solution you'd like**\n- If the Medicines list is empty in the encounter, display an “Add” button instead of “Edit”.\n- If medicines are already present, continue showing the “Edit” button as usual.\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",[2907],{"name":2908,"color":2909},"good first issue","7057ff",12727,"ohcnetwork","care_fe","open","Show “Add” button instead of “Edit” in Prescription section of Encounter when no medicines are listed","2025-06-26T10:23:18Z","https://github.com/ohcnetwork/care_fe/issues/12727",0.80180025,{"description":2919,"labels":2920,"number":2921,"owner":2911,"repository":2912,"state":2913,"title":2922,"updated_at":2923,"url":2924,"score":2925},"**Describe the bug**\n\nDue to uncontrolled width in Medication table, it is overflowing in the view causing whole screen scrolling horizontally which is bad for UI and UX and enable to fully access the button like Print and Edit \n\n- Ongoing tab in Medicines also has little bit of horizontal scroll which needs to fix\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go any Encounter \n2. Go to Medication Tab\n3. Add some medications if not present\n4. See error for medicines and ongoing medicines \n\n**Expected behavior**\nmake the width within the screen and only scroll table rows not the whole screen\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/ac93c792-8975-46df-bd75-998fab7b2999\n\n**Desktop (please complete the following information):**\n\n- OS: macOS\n- Browser : Arc \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",[],12732,"Medication table overflowing in Encounter Medication Section","2025-06-27T05:49:15Z","https://github.com/ohcnetwork/care_fe/issues/12732",0.81274235,{"description":2927,"labels":2928,"number":2929,"owner":2911,"repository":2912,"state":2913,"title":2930,"updated_at":2931,"url":2932,"score":2933},"The request form’s status labels are not fully translated. statuses like \"Approved\" and \"Cancelled\" etc...display correctly, the following statuses appear in their raw key form instead of translated text:\n\n* transportation_to_be_arranged\n* transfer_in_progress\n\n\n1. Go to \"Encounters\" -> Click on any patients -> \"Requests\".\n\n\n",[],12519,"Missing Translations for Request Statuses","2025-06-05T05:39:01Z","https://github.com/ohcnetwork/care_fe/issues/12519",0.82253414,{"description":2935,"labels":2936,"number":2937,"owner":2911,"repository":2912,"state":2913,"title":2938,"updated_at":2939,"url":2940,"score":2941},"**Is your feature request related to a problem? Please describe.**\nYes. Currently, when a user encounters a validation error while prescribing medicine, the error messages are either too generic or unclear. This makes it difficult for users to identify what exactly went wrong and how to correct it, leading to frustration and potential workflow delays.\n\n**Describe the solution you'd like**\nWe would like to see specific, descriptive validation error messages that clearly indicate the nature of the issue when prescribing medication\n\n\n\n**Additional context**\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",[],12661,"Clearly Define Validation Errors When Prescribing Medicine","2025-06-19T13:54:30Z","https://github.com/ohcnetwork/care_fe/issues/12661",0.8233383,{"description":2943,"labels":2944,"number":2945,"owner":2911,"repository":2912,"state":2913,"title":2946,"updated_at":2947,"url":2948,"score":2949},"**Is your feature request related to a problem? Please describe.**\nIn the questionnaire editor, when editing a specific section or question, there is no visual indication of which element is currently active. This makes it difficult to keep track of the editing context, especially in large or complex forms.\n\n**Describe the solution you'd like**\n- Visually highlight the section/question currently being edited (e.g., with a border, background color, or subtle glow).\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",[],12550,"Highlight Active Section/Question Being Edited in Questionnaire Editor","2025-06-09T09:23:51Z","https://github.com/ohcnetwork/care_fe/issues/12550",0.8250699,{"description":2951,"labels":2952,"number":2953,"owner":2911,"repository":2912,"state":2913,"title":2954,"updated_at":2955,"url":2956,"score":2957},"Currently enable when UI is not as user friendly, as it expects the user to type in the dependent question Id.\n\n\u003Cimg width=\"800\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/84f1e791-9e36-4a6c-9244-8ee43ff0e842\" />\n\n\u003Cimg width=\"800\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/10454c54-243c-4d2d-b0be-f8d9ac8b010e\" />\n\nApart from that, answers are all text based, rather than being based on the type of the dependent question.\n\nTasks\n\n- [ ] Convert the enable when question link id input box (highlighted in dark blue) to a drop down\n- [ ] Said drop down should be populated with link Ids of other questions + question text.\n - Don't include questions of type structured/display\n - structured need to be handled separately in future (cc: Aravind).\n - So in the screenshot 2, dropdown should contain 1. nihal as a possible option.\n- [ ] Convert the answer text input (highlighted in light blue) to drop down for:\n - should be dependent on the choice from question link drop down\n - boolean and choice types\n - maintain text input for other types\n\nMake sure existing functionality works as is.\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",[],12448,"Modify Enable When UI For Questionnaires","2025-05-29T07:09:54Z","https://github.com/ohcnetwork/care_fe/issues/12448",0.82786095,{"description":2959,"labels":2960,"number":2961,"owner":2911,"repository":2912,"state":2913,"title":2962,"updated_at":2963,"url":2964,"score":2965},"**Describe the bug**\n\nA validation error is thrown when trying to administer a medicine at the same time it is added.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to live encounter\n2. Medicine\n3. Add a medicine and administor it on the same time\n4. See error\n\n**Expected behavior**\n\nThe medicine should be successfully administered if the administration time matches the time it was added, without triggering a validation error.\n\n**Screenshots**\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",[],12693,"Modify the medicine administration validation to be on or after date of medicine added","2025-06-23T12:19:30Z","https://github.com/ohcnetwork/care_fe/issues/12693",0.83487403,{"description":2967,"labels":2968,"number":2975,"owner":2911,"repository":2912,"state":2913,"title":2976,"updated_at":2977,"url":2978,"score":2979},"**Is your feature request related to a problem? Please describe.**\nUsing Popover for tag selection on mobile devices is not user-friendly in questionnaire for searching tags.\n\n**Describe the solution you'd like**\nUsing Sheet component that slides up from the bottom on mobile devices instead of Popover .This will be more user-friendly.\n\nExpected Output.\n\nhttps://github.com/user-attachments/assets/e6178a32-f47d-4c40-83ed-91aeff477a44\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",[2969,2972],{"name":2970,"color":2971},"question","d876e3",{"name":2973,"color":2974},"needs-triage","ededed",12503,"Enhance Mobile UX: Implement Bottom Sheet for Tag Selector","2025-06-05T05:42:51Z","https://github.com/ohcnetwork/care_fe/issues/12503",0.8351319,{"description":2981,"labels":2982,"number":2983,"owner":2911,"repository":2912,"state":2913,"title":2984,"updated_at":2985,"url":2986,"score":2987},"**Describe the bug**\n\n- When filling structured questions like Diagnosis, Symptoms, etc., on mobile devices, some buttons are clipped and not fully visible. due to improper calculation of the view port\n- After submitting data in a structured questions in forms like the Community Nursing Form, instead of displaying the submitted response within the questionnaire, the interface scrolls to the next question.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to live encounter\n2. Click on add questionnaire and select community nurse form\n3. Submit a symptom or diagnosis \n4. See error\n\n**Expected behavior**\n\n- All UI elements, including buttons, should be fully visible and functional on mobile devices.\n- After submitting structured questionnaire responses, the submitted data should be displayed inline within the current question instead of moving to the next one automatically.\n\n**Screenshots**\n\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",[],12739,"Mobile UI issues with structured questionnaire input and submissions","2025-06-27T13:19:21Z","https://github.com/ohcnetwork/care_fe/issues/12739",0.83656436,{"description":2989,"labels":2990,"number":2991,"owner":2911,"repository":2912,"state":2992,"title":2993,"updated_at":2994,"url":2995,"score":2996},"**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,"closed","Improve the questionnaire visualisation on patient dashboard","2025-06-09T06:41:24Z","https://github.com/ohcnetwork/care_fe/issues/12223",0.7877148,["Reactive",2998],{},["Set"],["ShallowReactive",3001],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fv9Xh_sriXHseo5UqKl8wosDLKv1X04q0HvSyDuMzXjA":-1},"/ohcnetwork/care_fe/12711"]