\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",[],13636,"ohcnetwork","care_fe","open","Bug : caret icon shown in collapsed sidebar in Patient sidebar","2025-09-07T16:00:24Z","https://github.com/ohcnetwork/care_fe/issues/13636",0.7652449,{"description":3180,"labels":3181,"number":3182,"owner":3172,"repository":3173,"state":3174,"title":3183,"updated_at":3184,"url":3185,"score":3186},"**Describe the bug**\nWhen toggling the Auto-fill slot duration switch in the schedule template form, the Number of slots input throws a React warning:\n\"Input contains an input of type number with both value and defaultValue props.\nInput elements must be either controlled or uncontrolled (specify either the value prop, or the defaultValue prop, but not both).\"\n\nThis happens because the Input component is being passed both value (from react-hook-form) and defaultValue simultaneously.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to overview → Users → Create Schedule Template.\n2. Scroll to the Auto-fill slot duration toggle and enable it.\n3. The Number of slots input becomes visible.\n4. Observe the console warning in DevTools.\n\n**Expected behavior**\nThe input field should work without throwing controlled/uncontrolled warnings. It should only use value (via react-hook-form) or defaultValue (but not both).\n\n**Screenshots**\n\n\u003Cimg width=\"1917\" height=\"994\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/961f8b18-057f-4586-b67a-6769967b5ef2\" />\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**\nThe issue is caused in FormField → Input usage:\n\n\u003CInput\n type=\"number\"\n min={1}\n defaultValue={1} // ❌ conflict\n {...field} // includes value + onChange\n/>\n\nThis passes both value and defaultValue, leading to the React error.\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",[],13574,"Bug: Input field throws controlled/uncontrolled warning when using auto-fill slot duration toggle","2025-08-31T10:24:24Z","https://github.com/ohcnetwork/care_fe/issues/13574",0.7670028,{"description":3188,"labels":3189,"number":3190,"owner":3172,"repository":3173,"state":3174,"title":3191,"updated_at":3192,"url":3193,"score":3194},"**Describe the bug**\n\n- [ ] Issue 1: Active Tab Not Highlighted in Expanded Sidebar: When the sidebar is in an expanded state, and a user selects a sub-tab (e.g., Locations under Settings) and then closes the sub-tab view, the parent tab (Settings) does not show as active.\nThis behavior works correctly in the collapsed sidebar state, but not when expanded.\n\n- [ ] Issue 2: Active Tab Missing in Sub-Sub Navigation: When navigating into deeper nested levels (e.g., clicking on Encounters, then selecting a specific Patient Encounter), the active tab highlighting is lost. The sidebar fails to show the current tab or section as active, leading to confusion about the current context.\n\n- [ ] Issue 3: Both Product and Product Knowledge being shown as active in-closed sidebar when you select 'Product Knowledge'.\n\n> Note: Refer to the attached screen recording for a visual demonstration of both issues.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\nFor Issue 1:\n\t1.\tEnsure the sidebar is in expanded state.\n\t2.\tClick on Settings, then select Locations (or any sub-item).\n\t3.\tClose the sub-tab view.\n\t4.\tObserve that Settings is no longer highlighted as active, even though you’re still in a Settings-related route.\n\nFor Issue 2:\n\t1.\tClick on Encounters.\n\t2.\tSelect any Patient Encounter from the list.\n\t3.\tObserve that no tab is highlighted in the sidebar, even though you’re inside the Encounters module.\n\nFor Issue 3:\n\t1.\tClick on setting while the sidebar is closed.\n\t2.\tSelect 'Product Knowledge'\n\t3. Observe that both product and Product Knowledge being highlighted.\n\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/63b5feee-2e03-4676-88a1-41dde698e67c\n\n\u003Cimg width=\"443\" height=\"474\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3591c71d-096c-4dd7-8978-eb77b02620b3\" />\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",[],12097,"Sidebar Active Tab Highlight Issues in Expanded and Nested Views","2025-08-02T09:20:36Z","https://github.com/ohcnetwork/care_fe/issues/12097",0.7682773,{"description":3196,"labels":3197,"number":3198,"owner":3172,"repository":3173,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"**Describe the bug**\nIn the Product Knowledge section, after editing an existing Product Knowledge entry and clicking Save, the page shows the updated Product Knowledge details along with a Back button. However, clicking Back currently redirects the user to the Edit Product Knowledge page instead of taking them back to the main Product Knowledge list. This makes navigation confusing and forces the user to manually go through multiple steps to return to the main Product Knowledge page.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Product Knowledge.\n2. Select an existing Product Knowledge and click on Edit.\n3. Make any changes and click Save.\n4. On the preview screen that appears, click Back.\n5. Notice that you are taken back to the Edit Product Knowledge screen instead of the Product Knowledge list.\n\n**Expected behavior**\nAfter saving and previewing an edited Product Knowledge, clicking Back should redirect the user to the main Product Knowledge page (list view), not back to the edit form.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/174789c1-61ef-4dc0-88fe-da363f1eed46\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",[],13988,"Fix incorrect navigation after editing Product Knowledge","2025-10-07T12:38:08Z","https://github.com/ohcnetwork/care_fe/issues/13988",0.7717063,{"description":3204,"labels":3205,"number":3206,"owner":3172,"repository":3173,"state":3207,"title":3208,"updated_at":3209,"url":3210,"score":3211},"**Describe the bug**\n\"Each child in a list should have a unique 'key' prop\" appears in the browser console. The warning is specific to the component's render method in NavMain component.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to any page with sidebar navigation\n2. Click on Open browser developer tools (F12)\n3. Check console\n4. See warning about missing key prop in list children\n\n**Expected behavior**\n1. No console warnings should appear\n2. Each child element in mapped lists should have a unique key prop\n3. React should properly track and update list items\n\n**Screenshots**\n\n\u003Cimg width=\"1894\" height=\"993\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/fee3037f-f122-47a0-a75a-25a74020f74a\" />\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**\nThe warning occurs in the sidebar navigation component where we're mapping over the Fragment wrapper (\u003C>) also needs a unique key since it's the direct child of the map function.\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",[],13551,"closed","Add unique 'key' prop to list items in NavMain component","2025-09-01T09:58:36Z","https://github.com/ohcnetwork/care_fe/issues/13551",0.56597704,{"description":3213,"labels":3214,"number":3215,"owner":3172,"repository":3173,"state":3207,"title":3216,"updated_at":3217,"url":3218,"score":3219},"**Describe the bug**\nWhen resizing the Organizations sidebar by dragging to a smaller width, the CSS styling becomes inconsistent and breaks the layout. This causes elements to overlap or display improperly, negatively affecting usability.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Organizations\n2. Click on Governace\n3. Change the width of the list of organizations\n4. See error\n\n**Expected behavior**\nThe sidebar should maintain consistent and responsive styling regardless of resizing, with all content properly aligned and visible.\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/5908acc2-dea4-474c-9b3d-161c35e914a2\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",[],13531,"Sidebar Resizing Causes Layout and Styling Issues in Organizations Section","2025-08-26T16:37:23Z","https://github.com/ohcnetwork/care_fe/issues/13531",0.7476612,{"description":3221,"labels":3222,"number":3226,"owner":3172,"repository":3173,"state":3207,"title":3227,"updated_at":3228,"url":3229,"score":3230},"**Describe the bug**\nA hydration error occurs because a \n\\\u003Cdiv> is rendered as a child of a \\\u003Cp> element, which is invalid HTML. This results in the following warning during development:\n\"Warning: validateDOMNesting(...): \\\u003Cdiv> cannot appear as a descendant of \\\u003Cp>\"\nThis breaks HTML semantics and can cause React hydration mismatches in server-side rendered environments (like Next.js or Remix), potentially leading to layout shifts or unexpected DOM behavior.\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Admin dashboard'.\n2. Click on 'valuesets page present in sidebar'.\n3. open console.\n4. See error\n\n**Expected behavior**\nThe component structure should respect valid HTML semantics. \\\u003CExpandableText> should not return a \\\u003Cdiv> if it's going to be used inside a \\\u003Cp>.\n\nEither:\n\n\\\u003CExpandableText> should return only inline/phrasing elements (\\\u003Cspan>, etc.), OR\n\nIt should be documented/validated that the component must not be used inside a \\\u003Cp>.\n\n**Screenshots**\n\n\u003Cimg width=\"1919\" height=\"995\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/20baacce-244b-4ce0-a1cc-4a64dc0e588e\" />\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**\n1. The invalid HTML can cause accessibility and SEO issues.\n\n2. This can be especially problematic in SSR environments due to DOM mismatch between server-rendered and hydrated versions.\n\n3. It also affects maintainability for contributors unaware of this subtle nesting rule.\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",[3223],{"name":3224,"color":3225},"stale","688388",13249,"Hydration warning due to \u003Cdiv> inside \u003Cp> in ExpandableText component","2025-10-03T14:16:28Z","https://github.com/ohcnetwork/care_fe/issues/13249",0.7507338,{"description":3232,"labels":3233,"number":3235,"owner":3172,"repository":3173,"state":3207,"title":3236,"updated_at":3237,"url":3238,"score":3239},"Describe the bug\nHydration error occurs when accessing admin organization pages, causing React to throw hydration mismatch warnings and potentially breaking client-side functionality.\n\nTo Reproduce\nSteps to reproduce the behavior:\n\nGo to http://localhost:4000/admin/organizations/govt/6f89e366-263f-4154-ae1d-a53761ec53d4\n\nOpen browser developer console\n\nRefresh the page\n\nSee hydration error in console\n\nExpected behavior\nThe organization page should load without hydration errors, displaying the organization hierarchy and details correctly without any console warnings.\n\nScreenshots\n\n\u003Cimg width=\"2559\" height=\"1087\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/60942e84-452e-4018-9b9f-dd4c823301f8\" />\n\nConsole shows hydration mismatch error indicating server-rendered HTML doesn’t match client-side React output.\n\nDesktop (please complete the following information):\n\nOS: Windows\n\nBrowser: Chrome / Firefox / Safari\n\nVersion: Latest\n\nSmartphone (please complete the following information):\n\nDevice: Any mobile device\n\nOS: iOS / Android\n\nBrowser: Mobile browsers\n\nVersion: Latest\n\nAdditional context\nThe hydration error is caused by the expandedOrganizations state in AdminOrganizationList.tsx being initialized differently on server vs client.\n\nOn server-side, it renders with an empty Set.\n\nOn client-side, useEffect auto-expands parent organizations.\nThis mismatch leads to DOM structure differences during hydration.\n\n---\n\n🚨 **DO NOT EDIT BELOW THIS LINE** 🚨\n\n### Instructions for Requesting Assignment:\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",[3234],{"name":3224,"color":3225},13552,"Hydration error on admin organization pages","2025-09-30T06:01:44Z","https://github.com/ohcnetwork/care_fe/issues/13552",0.7511027,{"description":3241,"labels":3242,"number":3243,"owner":3172,"repository":3173,"state":3207,"title":3244,"updated_at":3245,"url":3246,"score":3247},"**Describe the bug**\nWhile viewing valueset preview, in console it shows a error:\nhook.js:608 Warning: Missing `Description` or `aria-describedby={undefined}` for {DialogContent}.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'Valueset'\n2. Click on 'Valueset preview'\n3. Scroll down to 'console'\n4. See error\n\n**Expected behavior**\nConsole should not show this error\n\n**Screenshots**\n\nhttps://github.com/user-attachments/assets/2e4ba236-a7fe-43c1-9697-530fb19db54f\n\n**Desktop (please complete the following information):**\n\n- OS: Win 10\n- Browser Opera\n- Version Latest\n\n**Additional context**\nFor any other pages that show this error, it should be fixed\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",[],13700,"Minor issue: missing description for DialogContent","2025-09-26T06:54:09Z","https://github.com/ohcnetwork/care_fe/issues/13700",0.7582084,{"description":3249,"labels":3250,"number":3252,"owner":3172,"repository":3173,"state":3207,"title":3253,"updated_at":3254,"url":3255,"score":3256},"**Describe the bug**\nIn the Manage Organizations modal, when a user selects an organization from the dropdown, the organization gets visually selected (with a checkmark), but it does not appear in the \"Selected Organizations\" list displayed above.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n1. Go to 'edit questionnaire'\n2. Click on 'manage organizations'\n3. select one\n4. See error\n\n**Expected behavior**\nOnce an organization is selected from the dropdown, it should immediately be displayed in above list.\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",[3251],{"name":3224,"color":3225},12619,"Bug: Selected organization not appearing in 'Selected Organizations' list","2025-07-24T06:28:48Z","https://github.com/ohcnetwork/care_fe/issues/12619",0.76342607,["Reactive",3258],{},["Set"],["ShallowReactive",3261],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fssQftvP7YQYOERHtpxIgdZ6001WbtirK94FnRcGPITE":-1},"/ohcnetwork/care_fe/12542"]