Hello community
I have noticed that when a clinician records patient’s conditions under the Diagnosis tab, the captured conditions do not show on both the patient dashboard under conditions and the visit summary page. When I query the tables conditions and emrapi_conditions the added conditions are not being updated on these tables, in fact the last entry in these tables was in November 2023.
Clinician captures condition here
Dashboard does not show the captured condition
Can you share a screen-recording so we can troubleshoot?
Hello,
I tried to reproduce the issue on our standard environment as well as Lite but I couldn’t reproduce it. I am able to add the conditions and see it on patient dashboard as well as Visit page. Could you tell me what steps have you followed? The issue is most likely with your setup.
Most Likely Causes:
Database/Environment Issue (most common) — In BAH-3007, the exact same symptoms were caused by a failed DB refresh where the connection pool exceeded max connections during initialization. The fix was setting c3p0.max_pool_size=30 and re-initializing.
Missing CIEL Concepts — If the environment wasn’t properly loaded with CIEL concepts, conditions won’t persist correctly. After fixing the DB issue in BAH-3007, the environment was reloaded with CIEL concepts and diagnoses appeared again.
Outdated Module Versions — Per BAH-2216, deploying master branches of openmrs-module-bahmniapps resolved display issues in older environments.
Check OpenMRS logs for errors when saving conditions — look for DB connection or concept-related errors.
Verify the conditions REST endpoint works: GET /openmrs/ws/rest/v1/condition?patientUuid=<uuid> — if it returns empty, the problem is at the persistence layer.
Check concept dictionary — ensure the required condition concepts exist and are properly mapped.
Verify module versions — ensure bahmniapps, emrapi, and openmrs-module-emrapi are up to date.
Check DB connectivity — run SHOW PROCESSLIST in MySQL to see if connections are being exhausted.
The fact that the conditions and emrapi_conditions tables stopped updating in Nov 2023 strongly suggests a DB-level issue (connection pool exhaustion or a failed migration) rather than a UI bug.
@arshiya_sehzad I think it is a usability issue. Maybe @tapologo is not clicking the ‘Add’ button under Actions in the conditions row before clicking Save. A screen recording will help rule this out.
Thank you @arshiya_sehzad. Your detailed troubleshooting steps helped me pin-point the problem. Customisations and some manual tasks during migration caused the issue. I’m just shocked that it went unnoticed by users for this long. Thank you once again for your assistance
Happy to help.
