Ambiki Release Note: Cleaner Goal Auditing, Smarter Patient Imports, and Better Evaluation Visibility
Stay up to date on new features and improvements to Ambiki - Ambiki release notes is where the Ambitious Idea Labs team publicly communicates new functionality added to Ambiki so that our users can stay on top of everything that is new.
Samuel Okoth 7 days ago
Date: 02/04/2026
Summary by Persona (Grouped by Role)
π©ββοΈ Clinicians / Therapists
- Goal comment handling is now cleaner behind the scenes, reducing noisy system-generated text showing up as user-visible comments (backend-only change).
π§βπΌ Admins
- Patient CSV importer is clearer and safer: better error handling, direct links to issues, green checks for resolved items, import blocked until all errors are fixed, upload limit of 200, and an updated importer guide.
- Evaluations record center now includes a diagnosis codes column (and export includes it too).
π³ Billers / Guardians
- No direct changes.
π οΈ Fix - Goal comments no longer store system-generated messages; audit context handled separately
π₯ Audience: Therapists, Admins
π Date range affected: Ongoing
β Issue: System-generated messages (e.g. βGoal automatically marked activeβ¦β) were being stored in user-visible goal comments, and audit context like document UUIDs had no dedicated place to live. Additionally, initial goal creation still does not reliably persist status comments.
β Action Steps: No action required. This is a backend change only. Users may still need to edit goal comments after initial creation as a temporary workaround.
π Date range affected: Ongoing
β Issue: System-generated messages (e.g. βGoal automatically marked activeβ¦β) were being stored in user-visible goal comments, and audit context like document UUIDs had no dedicated place to live. Additionally, initial goal creation still does not reliably persist status comments.
β Action Steps: No action required. This is a backend change only. Users may still need to edit goal comments after initial creation as a temporary workaround.
π οΈ Fix - Patient CSV importer error handling and limits improved
π₯ Audience: Admins
β Issue: Patient CSV uploads showed confusing error messages about non-existent patients (e.g., "errors for patients 7-50" when only 6 patients were uploaded). This was caused by empty Excel rows being included in the CSV file. A patient upload limit of 200 has also been implemented. In addition any errors that appear are now links that will take you directly to the issue. Any fixed errors will appear with a green checkmark and the error list count will decrease. The ability to process the import is now disabled until all errors have been addressed. The importer guide has also been updated to reflect these changes.
β Action Steps: None.
β Issue: Patient CSV uploads showed confusing error messages about non-existent patients (e.g., "errors for patients 7-50" when only 6 patients were uploaded). This was caused by empty Excel rows being included in the CSV file. A patient upload limit of 200 has also been implemented. In addition any errors that appear are now links that will take you directly to the issue. Any fixed errors will appear with a green checkmark and the error list count will decrease. The ability to process the import is now disabled until all errors have been addressed. The importer guide has also been updated to reflect these changes.
β Action Steps: None.
π οΈ Polish - Diagnosis codes column added to Evaluations record center and export
π₯ Audience: Admins
β Issue: A diagnosis codes column has been added to the Evaluations record center as well as to the export
β Action Steps: Navigate to the Evaluations record center to view the new diagnosis codes column
Thank you for choosing Ambiki.
β Issue: A diagnosis codes column has been added to the Evaluations record center as well as to the export
β Action Steps: Navigate to the Evaluations record center to view the new diagnosis codes column
Thank you for choosing Ambiki.