Standardize UI alerts: replace native alert() dialogs with ConfirmationService across Angular modules

[A-Chronicle]

Problem

Multiple Angular modules in AMRIT currently use native browser alert() dialogs for user notifications. This creates inconsistent UX, limits styling customization, and makes it difficult to manage error messaging during critical healthcare workflows.

Solution

Replace all instances of alert() with PrimeNG's ConfirmationService to:

• Provide consistent UI/UX across all modules
• Enable themed, accessible dialogs aligned with AMRIT design system
• Allow better error message formatting and actionability
• Improve user experience for healthcare workers

Impact

• Modules affected: MMU-UI, Telemedicine-UI, HWC-UI, Helpline104-UI, Helpline1097-UI, Admin-UI
• Type: Technical Debt / UX Improvement
• Priority: Medium
• Scope: Moderate (estimated 50+ alert instances)

Acceptance Criteria

• All alert() calls replaced with ConfirmationService
• Consistent confirmation/error dialog styling across modules
• Unit tests updated for affected components
• Visual regression testing completed
• Documentation updated

[A-Chronicle]

Hey @drtechie I'd like to work on this issue.

My Strategy & Vision

I plan to tackle this systematically:

Phase 1: Audit & Planning

• Audit all Angular modules to identify and catalog existing `alert()` instances
• Document current usage patterns and error messages
• Create a module-by-module breakdown

Phase 2: Implementation

• Implement `ConfirmationService` wrapper with standardized dialog patterns
• Replace `alert()` calls module by module, starting with high-impact services
• Ensure backward compatibility and consistent messaging

Phase 3: Testing & Polish

• Add/update unit tests for affected components
• Perform visual regression testing across modules
• Update documentation and add examples

Why I'm a Good Fit

• Strong Angular expertise with TypeScript
• Experience with PrimeNG component libraries
• Committed to maintaining code quality and healthcare platform reliability

I'm ready to dive in and would appreciate your approval to move forward. Happy to discuss approach details or adjust scope based on your guidance!

[A-Chronicle]

Interest in Contributing

Hey @drtechie maintainers! I'd like to work on this issue.

My Strategy & Vision

I plan to tackle this systematically:

Phase 1: Audit & Planning

• Audit all Angular modules to identify and catalog existing alert() instances
• Document current usage patterns and error messages
• Create a module-by-module breakdown

Phase 2: Implementation

• Implement ConfirmationService wrapper with standardized dialog patterns
• Replace alert() calls module by module, starting with high-impact services
• Ensure backward compatibility and consistent messaging

Phase 3: Testing & Polish

• Add/update unit tests for affected components
• Perform visual regression testing across modules
• Update documentation and add examples

Why I'm a Good Fit

• Strong Angular expertise with TypeScript
• Experience with PrimeNG component libraries
• Committed to maintaining code quality and healthcare platform reliability

I'm ready to dive in and would appreciate your approval to move forward. Happy to discuss approach details or adjust scope based on your guidance!

Looking forward to contributing to AMRIT! 🚀