",[],13664,"ohcnetwork","care_fe","open","Rename Discharge Disposition field to Discharge Reason","2025-09-09T06:42:45Z","https://github.com/ohcnetwork/care_fe/issues/13664",0.67334896,{"description":3180,"labels":3181,"number":3188,"owner":3172,"repository":3173,"state":3174,"title":3189,"updated_at":3190,"url":3191,"score":3192},"**Is your feature request related to a problem? Please describe.**\nCurrently, the encounters in the \"ALL STATUS\" which is circled red in the shared picture below, are not sorted. As a result, nurses have to scroll through the entire list to locate an active patient, especially if the patient has been in the ICU for a long time. While this may be manageable for us, it adds unnecessary extra work for the nursing staff.\n\n**Describe the solution you'd like**\n1. Active patients should always be displayed at the top, irrespective of their creation date.\n2. Completed encounters, which are marked yellow in the shared picture, should always be displayed below the active ones.\nThis will make it easier for nursing staff to quickly locate and manage active cases.\n\n**Additional**\nThere are options to view the encounters separately based on their status, which are highlighted in green in the shared picture. However, by default, the first page that opens is the \"ALL Status\" view, and requiring one extra click adds unnecessary effort for the nursing staff.\n\n**Screenshot**\n\u003Cimg width=\"1812\" height=\"880\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/9f05ffae-4e9c-473d-bb59-21416b9e0b98\" />\n\n\n@gigincg \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",[3182,3185],{"name":3183,"color":3184},"question","d876e3",{"name":3186,"color":3187},"needs-triage","ededed",13372,"Sorting Encounters","2025-08-18T08:08:01Z","https://github.com/ohcnetwork/care_fe/issues/13372",0.7409567,{"description":3194,"labels":3195,"number":3201,"owner":3172,"repository":3173,"state":3174,"title":3202,"updated_at":3203,"url":3204,"score":3205},"**Is your feature request related to a problem? Please describe.**\nThe mentioned option is unavailable in these fields. which is important because when a patient gets shifted from a ward to ICU within same hospital, it's termed \"trans in\" and from the ICU to the ward, it's \"trans out\"\n\n**Describe the solution you'd like**\nTrans In & Trans Out options in Admit Source and Discharge Disposition, respectively\n\n**Steps to reproduce**\n[https://care.coronasafe.in/facility/d95bf507-055d-403f-acd3-3d331c735140/patient/043edc74-22b9-4efe-b8d7-2695eacb6917/encounter/131ed06a-abbc-4ed9-b9df-ca594e58148c/questionnaire/encounter](url)\n\n1. Click on above URL\n2. Use the Login Credentials:\n Username: jamesnurse\n password: James@123\n3. Go to Hospitalization Details.\n4. Click on Admit Source.\n____SS____\n\n\n\n5. Click on \"Mark as Discharge\" and hit proceed\n6. Go to Hospitalization Details. \n7. Click on Discharge Disposition\n____SS____\n\n\n\n@gigincg \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",[3196,3197,3200],{"name":3183,"color":3184},{"name":3198,"color":3199},"discussion required","05EFF8",{"name":3186,"color":3187},12774,"Trans In & Trans Out options in Admit Source and Discharge Disposition, respectively","2025-08-18T08:07:27Z","https://github.com/ohcnetwork/care_fe/issues/12774",0.7530241,{"description":3207,"labels":3208,"number":3209,"owner":3172,"repository":3173,"state":3174,"title":3210,"updated_at":3211,"url":3212,"score":3213},"**Is your feature request related to a problem? Please describe.**\nWith the introduction of the new Clinical History page within the encounter module (which shows the timeline of clinical history), the existing Health Profile section on the patient profile page has become irrelevant and is no longer useful.\n\n**Describe the solution you'd like**\nHide or remove the Health Profile section from the patient profile page.\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",[],13432,"Hide/Remove health profile from patient profile page","2025-08-20T05:55:38Z","https://github.com/ohcnetwork/care_fe/issues/13432",0.7608173,{"description":3215,"labels":3216,"number":3217,"owner":3172,"repository":3173,"state":3174,"title":3218,"updated_at":3219,"url":3220,"score":3221},"**Describe the bug**\nOn initiate encounter page future dates are selectable for all the status types, but it should be applicable only when selecting status as \"Planned\", not when the status is selected as \"In Progress\".\n\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to 'search patient'\n2. Click on 'add new patient'\n3. Fill in the patient details then save\n4. Then click on \"create encounter\"\n5. Then initiate encounter option will pop up\n6. There when selecting dates, future dates are selectable for all status type.\n \n**Expected behavior**\nFuture date should be selectable only when the status type is selected as \"Planned\"\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",[],13293,"On initiate patient encounter option, future dates are selectable for all the status types.","2025-08-07T06:22:16Z","https://github.com/ohcnetwork/care_fe/issues/13293",0.7691186,{"description":3223,"labels":3224,"number":3228,"owner":3172,"repository":3173,"state":3229,"title":3230,"updated_at":3231,"url":3232,"score":3233},"**Description:**\n\nCurrently, the fields ward, municipality, and panchayat are marked as mandatory in CARE software.\n\n**During patient registration:**\n\n1. ICU staffs/nurses are unaware of the exact ward/municipality/panchayat of the patient.\n2. Patients or their attendants also do not know this information themselves.\n3. So, staff are selecting random options from the dropdown list just to proceed.\n\n**Problem:**\n\nThis random selection creates incorrect location data, which reduces the overall data quality while doing the patient registration.\n\n**Proposed Solution:**\n\n1. Change these fields to optional.\n2. Alternatively, provide an \"Unknown / Not provided\" option in the dropdown to allow data entry without random selection.\n\n**Impact:**\n\n1. Reduce data inconsistency caused by random selections.\n2. Make patient registration faster and more accurate.\n\n**Reference :**\nAccording to FHIR implementation guide line this fields are not mandatory, please visit the link provided below for reference. \n\nhttps://hl7.org/fhir/R4/datatypes.html#Address\nhttps://build.fhir.org/conformance-rules.html#cardinality\n\n@gigincg \n\n\n\n \n\n\n\n \n",[3225],{"name":3226,"color":3227},"stale","688388",13360,"closed","Make ward/municipality/panchayat fields optional","2025-10-01T10:36:18Z","https://github.com/ohcnetwork/care_fe/issues/13360",0.72954535,{"description":3235,"labels":3236,"number":3240,"owner":3172,"repository":3173,"state":3229,"title":3241,"updated_at":3242,"url":3243,"score":3244},"**Is your feature request related to a problem? Please describe.**\nMake \"ward\" field optional in the patient demography page. Currently the field is mandatory and hospital staff having trouble to fill the field when the patient is not aware about the ward number. \n\n\u003Cimg width=\"294\" height=\"92\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c562cc62-3d08-46d5-ac21-5e89d6471d53\" />\n\n**Describe the solution you'd like**\nMake the ward field optional in the patient registration page\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",[3237,3238,3239],{"name":3183,"color":3184},{"name":3226,"color":3227},{"name":3186,"color":3187},13034,"Make \"Ward\" field optional in Patient Demography (Registration Page)","2025-08-18T09:29:59Z","https://github.com/ohcnetwork/care_fe/issues/13034",0.73552245,{"description":3246,"labels":3247,"number":3249,"owner":3172,"repository":3173,"state":3229,"title":3250,"updated_at":3251,"url":3252,"score":3253},"**Describe the bug**\nDischarge summary not generated.\n\n**To Reproduce**\n\n1. Go to a patient dashboard \n2. Click on update \n3. Select Discharge summary \n4. Click on generate discharge summary \n5. See pop up notification Discharged summary will be generated soon.\nWhich doesn't generate at all after refreshing the page or wait for a while.\n\n\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",[3248],{"name":3226,"color":3227},12363,"Discharge summary not generating on Manipur care instance.","2025-07-31T05:42:48Z","https://github.com/ohcnetwork/care_fe/issues/12363",0.7459503,{"description":3255,"labels":3256,"number":3260,"owner":3172,"repository":3173,"state":3229,"title":3261,"updated_at":3262,"url":3263,"score":3264},"**Describe the bug**\nFor patients who are already discharged and marked as complete for those patients, when we try to open the general info page an error message pops up saying patient not found.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to patients profile who has been discharged and is marked as completed\n2. Click on small square shaped button with an arrow, right next to the patients name.\n3. See error\n\n**Expected behavior**\nThe general info page should open up.\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",[3257,3258,3259],{"name":3183,"color":3184},{"name":3226,"color":3227},{"name":3186,"color":3187},12781,"For patients who are marked as completed, the general info page is not accessible.","2025-08-13T06:56:57Z","https://github.com/ohcnetwork/care_fe/issues/12781",0.75297284,{"description":3266,"labels":3267,"number":3270,"owner":3172,"repository":3173,"state":3229,"title":3271,"updated_at":3272,"url":3273,"score":3274},"**Describe the bug**\nThe Date of Birth fields (Day, Month, Year) in the Add Patient Details form are required but do not display the required field indicator (*). This misleads users into thinking the field is optional until an error is shown after form submission.\n\n**To Reproduce**\nSteps to reproduce the behavior:\n\n1. Go to Search Patients\n2. Click on Add New Patient\n3. Scroll down to the Date of Birth section.\n4. Observe that Day, Month, and Year fields do not have an asterisk (*).\n5. Submit the form without filling DOB.\n6. See error: \"Date of birth must be present\".\n\n**Expected behavior**\nRequired fields (like Date of Birth) should show an asterisk (*) or a visual indicator to denote they are mandatory, just like other required fields (e.g., Blood Group, Pincode).\n\n**Screenshots**\nCurrent UI without asterisk:\n\u003Cimg width=\"1272\" height=\"1260\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b21ea2bc-d7aa-451e-a236-cf4df6968eaa\" />\n\nValidation error after submit:\n\u003Cimg width=\"1318\" height=\"1258\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/cdf21c0f-7cde-4b26-aa6c-5e41f1838e6b\" />\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",[3268,3269],{"name":3183,"color":3184},{"name":3186,"color":3187},12971,"Required indicator (*) missing for Date of Birth fields in Add Patient form","2025-07-18T06:05:34Z","https://github.com/ohcnetwork/care_fe/issues/12971",0.7547087,["Reactive",3276],{},["Set"],["ShallowReactive",3279],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$frnCSHJJF-_xfdBw67ytLlAgJcx-Y1e9URfz_8bUQc48":-1},"/ohcnetwork/care_fe/13663"]