\n\u003Cimg width=\"1169\" height=\"813\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0f7c103c-c2d4-43e7-933b-6ecbad6d1622\" />\n\n\n\n### Describe\n\nRefer to above screenshots, see there is no any information present regarding Account and Patient for both detail page and print receipt \n\n### steps to Reproduce:\n- Go to any facility \n- Go to billing tab\n- Go to any payment view detail \n- see the error \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",[],13256,"ohcnetwork","care_fe","open","Bug: No Information regarding Account and Patient on Payment detail page and Print","2025-08-04T20:18:38Z","https://github.com/ohcnetwork/care_fe/issues/13256",0.8295113,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Description**\nThis issue addresses UI inconsistencies in the Patient Tag drop down menu of \"Add Patient Details\" page:\n\n- Tag Menu Dropdown: The height of the search input as well as the menu items need to be adjusted to align with our design system.\n\n- Keyboard Shortcuts: The size of the keyboard shortcuts is inconsistent and needs to be fixed.\n\n- The padding for each tag option within the dropdown should be consistent with the provided Figma file, ensuring proper alignment and spacing.\n\n**Steps to Reproduce**\n\n1. Navigate to Add Patient's details page.\n\n2. Scroll down to the Patient Tags field.\n\n3. Open the dropdown menu.\n\n4. Observe the current option height.\n\n**Expected Behaviour**\n\n- The tag menu dropdown should adhere to the following specifications:\n\n - The search input field at the top of the dropdown should have a fixed height of 40 pixels.\n\n - The padding for each tag option within the dropdown should be consistent with the provided Figma file, ensuring proper alignment and spacing. \n\n- Keyboard Shortcuts\n\n - The size of the keyboard shortcut indicators should match the design specifications. They currently appear smaller than intended. \n\n- Add a secondary button to complete the action.\n\n\n**Visual Reference**\n\n\u003Cimg width=\"752\" height=\"710\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/23009867-03c6-44c4-acd4-4adfbffcb3d4\" />\n\u003Cimg width=\"743\" height=\"705\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7f098772-6e61-4754-a5e5-b94b509b11fb\" />\n\u003Cimg width=\"730\" height=\"636\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/990db087-0e47-4f6d-83b5-b90be8ac1d0a\" />\n\n**Proposed Solution**\nAttached screenshot for reference\n\u003Cimg width=\"1110\" height=\"1210\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/94e1fa1c-2e40-48f9-a230-14043a90198d\" />\nRefer the figma file for the correct dimensions https://www.figma.com/design/Z93EYKSa1MdBmXndsMBJSQ/Care?node-id=26304-10329&t=AskluDORl8G3ixs5-1\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",[],13732,"Enhance usability by solving the UI inconsistencies on the \"Add Patient Details\" page","2025-09-17T11:43:03Z","https://github.com/ohcnetwork/care_fe/issues/13732",0.83030623,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**Describe the bug**\nThere are two issues observed in the Encounters page:\n\n1. **Validation bypass after removal**\n - When adding Allergy, Diagnosis, or Symptoms for the first time, the required validation for the main dropdown works correctly (e.g., \"This field is required\").\n- However, if an item is added and then removed, the user can submit the form again **without selecting anything**, and it still gets submitted without triggering the required validation.\n- This bypass happens for all three: Allergy, Diagnosis, and Symptoms.\n\n2. **Raw translation keys in Add Questionnaire**\n- When selecting the **\"Respiratory Status\"** questionnaire, under **\"Respiratory Support\"**, some options display raw translation keys (e.g., `oxygen_support`, `non_invasive`) instead of their proper localized labels.\n\n**To Reproduce**\nSteps to Reproduce (Issue 1 - Validation bypass):\n\n1. Go to Encounters → Add Allergy (same issue for Diagnosis/Symptoms).\n2. Try to submit without selecting anything → validation message appears (expected).\n3. Add any allergy and submit → works fine.\n4. Edit and remove that allergy → list becomes empty.\n5. Submit without adding anything again → submission still succeeds (unexpected).\n\nSteps to Reproduce (Issue 2 - Raw translation keys):\n\n1. Go to Encounters → Add Questionnaire → select \"Respiratory Status\".\n2. Under \"Respiratory Support\", check the options.\n3. Notice that raw translation keys like `oxygen_support`, `non_invasive`, etc., are shown instead of proper values.\n\n**Expected behavior**\n- For Issue 1: Required validation should trigger every time the list is empty, even after removing previously added items.\n- For Issue 2: All option labels should display their localized text instead of raw translation keys.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/58ca5faf-f7ec-4bf5-b1a9-707949d068ae\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",[],13349,"Validation bypass after removal in Add Allergy/Diagnosis/Symptoms & Raw translation keys in Add Questionnaire","2025-08-12T11:21:15Z","https://github.com/ohcnetwork/care_fe/issues/13349",0.83164585,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**Describe the bug**\nWhen we are removing a field and trying to add it back in patient information section, we are not able to add it.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to [link](https://care.ohc.network/facility/2fbb0809-b62c-4c53-816e-f1404f096c5e/settings/reportbuilder/new)\n2. Click on Section Tab\n3. Remove a field and try to add it back\n4. See error\n\n**Expected behavior**\nUser should able to add field\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/26eece7a-a1aa-4425-9c19-06bd23612861\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",[],12477,"Bug: User is not able to add field in Patient Information section of Report Template Builder","2025-06-01T11:01:17Z","https://github.com/ohcnetwork/care_fe/issues/12477",0.83235914,{"description":3204,"labels":3205,"number":3212,"owner":3172,"repository":3173,"state":3213,"title":3214,"updated_at":3215,"url":3216,"score":3217},"Module: Patient Encounter → Service Request → Body Site selection\n\nIssue:\nWhen selecting a body site in the Service Request form, the SNOMED dropdown list does not stay fixed within the screen viewport. On scrolling, the top section of the dropdown goes out of view and gets stuck, making it difficult to select options.\n\nSteps to Reproduce:\n\nGo to Patient Encounter → Service Request.\n\nAdd a new service request (e.g., CBC).\n\nClick on Select Body Site.\n\nScroll through the list of SNOMED terms.\n\nNotice that the top of the dropdown goes out of the visible screen and overlaps browser UI.\n\nExpected Behavior:\nThe dropdown list should remain properly aligned within the screen viewport and allow smooth scrolling without overlap.\n\nActual Behavior:\nThe dropdown content overlaps with the top browser UI and becomes partially hidden, making it hard to select terms.\n\nImpact:\n\nDoctors/Users face difficulty in selecting the correct body site.\n\nSlows down data entry in Service Requests.\n\n\u003Cimg width=\"1379\" height=\"747\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0cf81fa5-4354-4d1a-9a1f-d79bb11c36b8\" />\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],{"name":3207,"color":3208},"question","d876e3",{"name":3210,"color":3211},"needs-triage","ededed",13565,"closed","UI/UX bug : in service request of encounters of IP Pateint","2025-09-01T06:23:51Z","https://github.com/ohcnetwork/care_fe/issues/13565",0.7782897,{"description":3219,"labels":3220,"number":3221,"owner":3172,"repository":3173,"state":3213,"title":3222,"updated_at":3223,"url":3224,"score":3225},"**Describe the bug**\n\n\u003Cimg width=\"800\" height=\"277\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e42182dc-d904-4eb0-b9c9-7ab57424fd5e\" />\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n- Go to any facility \n- go to observation definition tab under setting main tab \n- go to form for the same \n- Add component \n- submit blank form \n- see error\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",[],13073,"Observation Definition form UI Issue on error message","2025-08-20T06:52:20Z","https://github.com/ohcnetwork/care_fe/issues/13073",0.80700946,{"description":3227,"labels":3228,"number":3229,"owner":3172,"repository":3173,"state":3213,"title":3230,"updated_at":3231,"url":3232,"score":3233},"**Describe the bug**\nOn the Encounter page, when the user clicks on \"Add Questionnaire\", the system incorrectly displays questionnaires with subject_type = \"patient\" along with those having subject_type = \"encounter\". \n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Create a new questionnaire with subject_type = \"patient\".\n2. Go to a patient's Encounter page. \n3. Click on \"Add Questionnaire\".\n4. Observe that the newly created patient-type questionnaire is visible, which is incorrect.\n\n**Expected behavior**\nOnly questionnaires with subject_type = \"encounter\" should be visible when accessed from the Encounter page..\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",[],12782,"Bug: \"Add Questionnaire\" on Encounter Page shows Patient-type Questionnaires","2025-07-14T06:24:48Z","https://github.com/ohcnetwork/care_fe/issues/12782",0.81464803,{"description":3235,"labels":3236,"number":3237,"owner":3172,"repository":3173,"state":3213,"title":3238,"updated_at":3239,"url":3240,"score":3241},"**Describe the bug**\n\nThe `EmptyState` messages in the Definitions pages are inconsistent. While the Activity Definitions page has the most relevant and clear empty state, other pages (Observation, Specimen, Charge) have mismatched titles or descriptions.\n\n**Pages Affected:**\n- Specimen Definitions\n- Observation Definitions\n- Charge Item Definitions\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Definitions Pages\n2. See error\n\n**Issues:**\n- Specimen definitions don’t specify “specimen” in the title.\n- Descriptions vary in wording (“Try adjusting your filters” vs. “Adjust filters to find what you’re looking for”).\n\n**Expected Behavior:**\nAll definitions pages should follow a **consistent empty state format** (title + description) like **Activity Definitions**:\n- Title: `No [definition type] definitions found`\n- Description: `Adjust [definition type] definition filters to find what you're looking for`\n\n\n**Screenshots**\n\n\u003Cimg width=\"1764\" height=\"472\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c91ad1b1-2fed-4ee5-9a98-00ba02d0b569\" />\n\nhow it should be ⬇️\n\n\u003Cimg width=\"1796\" height=\"510\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/09755bf2-531a-4acf-85c2-c88c93c52475\" />\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",[],13390,"Inconsistent Empty State Messages in Definition Pages","2025-08-29T09:15:29Z","https://github.com/ohcnetwork/care_fe/issues/13390",0.8203981,{"description":3243,"labels":3244,"number":3245,"owner":3172,"repository":3173,"state":3213,"title":3246,"updated_at":3247,"url":3248,"score":3249},"**Describe the bug**\nWhen creating a new Activity Definition, if the user creates an Observation Definition from within the Activity Definition form and then saves it, the Activity Definition itself gets saved and submitted prematurely.\n\nAs a result, the user is forced to reopen and edit the Activity Definition again in order to add the remaining fields. \n\n**To Reproduce**\nCreate an activity definition and create observation definition from within activity definition \n\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",[],13433,"Saving Observation Definition within Activity Definition causes unexpected submission","2025-08-20T08:30:16Z","https://github.com/ohcnetwork/care_fe/issues/13433",0.82126814,{"description":3251,"labels":3252,"number":3253,"owner":3172,"repository":3173,"state":3213,"title":3254,"updated_at":3255,"url":3256,"score":3257},"**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.82333285,["Reactive",3259],{},["Set"],["ShallowReactive",3262],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f0spE2dnGpBR-4OFtRmoud29oTrC2O8aSbB_RkMvk18I":-1},"/ohcnetwork/care_fe/13450"]