\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",[],13056,"ohcnetwork","care_fe","open","Prevent Duplicate selection for Patient Preparation in Specimen definition form","2025-07-23T09:58:37Z","https://github.com/ohcnetwork/care_fe/issues/13056",0.7676445,{"description":3029,"labels":3030,"number":3031,"owner":3021,"repository":3022,"state":3023,"title":3032,"updated_at":3033,"url":3034,"score":3035},"**Describe the bug**\n\n- WHEN YOu fill all the data in the form and swap the selection for a field with an enable_when condition, the questionnaire is throwing an error upon submission\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",[],12810,"Questionnaire submission is failing for enable when condition","2025-07-07T10:19:06Z","https://github.com/ohcnetwork/care_fe/issues/12810",0.77543116,{"description":3037,"labels":3038,"number":3039,"owner":3021,"repository":3022,"state":3023,"title":3040,"updated_at":3041,"url":3042,"score":3043},"**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.7810231,{"description":3045,"labels":3046,"number":3047,"owner":3021,"repository":3022,"state":3023,"title":3048,"updated_at":3049,"url":3050,"score":3051},"**Describe the bug**\nWhen cancelling an appointment, if the user enters only spaces in the \"Note\" field, It accepts it and submits the cancellation. \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Encounters' -> \"View Patients\" -> \"Appointments\"\n2. Click on ''Cancel Appointment\"\n3. See error, it accepts a note with spaces.\n\nhttps://github.com/user-attachments/assets/3a5b849a-58ff-4770-b6fe-53e96f7865f5\n\n**Expected behavior**\nThe reason should never appear as empty after cancelling an appointment.\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",[],13025,"Note Field Accepts Spaces as Valid Input","2025-07-22T04:34:44Z","https://github.com/ohcnetwork/care_fe/issues/13025",0.7859216,{"description":3053,"labels":3054,"number":3055,"owner":3021,"repository":3022,"state":3023,"title":3056,"updated_at":3057,"url":3058,"score":3059},"Next to Emergency Contact field, need a field to add a another contact point.\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",[],13153,"Option to add Contact Point details in Patient profile page","2025-07-30T08:06:39Z","https://github.com/ohcnetwork/care_fe/issues/13153",0.78972226,{"description":3061,"labels":3062,"number":3069,"owner":3021,"repository":3022,"state":3070,"title":3071,"updated_at":3072,"url":3073,"score":3074},"**Describe the bug**\nWhen an appointment structured questionnaire is added to a questionnaire, by default it is set as a mandatory question and the questionnaire cannot be submitted without scheduling an appointment.\n\nExpected behaviour \n\nUnless it is set as required , it should not be set mandatory ",[3063,3066],{"name":3064,"color":3065},"question","d876e3",{"name":3067,"color":3068},"needs-triage","ededed",11620,"closed","When appointment structured question is added to a questionnaire by default it is set as mandatory.","2025-06-17T15:08:56Z","https://github.com/ohcnetwork/care_fe/issues/11620",0.6466422,{"description":3076,"labels":3077,"number":3081,"owner":3021,"repository":3022,"state":3070,"title":3082,"updated_at":3083,"url":3084,"score":3085},"**Describe the bug**\nWhen adding or editing a question in the questionnaire form:\n- Selecting a structure_type (e.g., MedicationRequest) initially is not saved correctly.\n- If the question's type is later changed to one that should not have a structure_type, the previously selected structure_type is still sent to the backend and saved, even though it should be cleared.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Admin dashboard \n2. Create questionnaire form:\n3. Add question \n4. select question type structure and structure_type (don't save)\n5. then change type of question\n6. See error**Expected behavior**\nA clear and concise description of what you expected to happen.\n\n**Screenshots**\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**\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",[3078],{"name":3079,"color":3080},"stale","688388",12182,"structure_type persists incorrectly when changing question type in Questionnaire Form","2025-07-30T11:09:22Z","https://github.com/ohcnetwork/care_fe/issues/12182",0.7487725,{"description":3087,"labels":3088,"number":3095,"owner":3021,"repository":3022,"state":3070,"title":3096,"updated_at":3097,"url":3098,"score":3099},"\nMedication Statement, Allergy, Symptom, Diagnosis records with entered-in-error status need not be disabled during edit\n\n\n\n**Describe the bug**\nA clear and concise description of what the bug is.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to '...'\n2. Click on '....'\n3. Scroll down to '....'\n4. See error\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",[3089,3092,3093,3094],{"name":3090,"color":3091},"good first issue","7057ff",{"name":3064,"color":3065},{"name":3079,"color":3080},{"name":3067,"color":3068},11966,"Structured records uneditable when in entered-in-error status","2025-06-23T16:50:34Z","https://github.com/ohcnetwork/care_fe/issues/11966",0.7537187,{"description":3101,"labels":3102,"number":3106,"owner":3021,"repository":3022,"state":3070,"title":3107,"updated_at":3108,"url":3109,"score":3110},"**Description:**\nTextArea in the Appointment Question is not accepting white spaces while typing.\n\n**Expected Behaviour**\nSpaces should be allowed so users can enter complete sentence.",[3103],{"name":3104,"color":3105},"P1","519BFE",12673,"Unable to Enter Spaces in Appointment Question Reason for visit field","2025-06-20T18:29:24Z","https://github.com/ohcnetwork/care_fe/issues/12673",0.76220727,{"description":3112,"labels":3113,"number":3114,"owner":3021,"repository":3022,"state":3070,"title":3115,"updated_at":3116,"url":3117,"score":3118},"**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.7718008,["Reactive",3120],{},["Set"],["ShallowReactive",3123],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fL90TYaZDrdJdGvhko_1ufI-hEjj6y7PwNqeOe_j2kws":-1},"/ohcnetwork/care_fe/12537"]