Tebra | Modernizing legacy reporting systems in healthcare

Tebra logo

Overview

Tebra is a healthcare technology company that has been in the market for over a decade. As their platform evolved over the years, they accumulated a mix of legacy technologies including JSPs, Angular, and various React implementations, creating inconsistent UX across their platform.

Searching in the grid is an absolute killer feature for us. Everything loads to the client-side, and now you can search anything—and the search is so fast and amazing.
– Ronen Akiva, Senior Director of Engineering

Ronen leads the teams responsible for embedding MUI components into their design system and managing billing and payments infrastructure. With nearly six years at the company, Ronen spearheaded the initiative to modernize Tebra's reporting capabilities and create a unified design system.

Challenge

Tebra faced several critical challenges with their legacy reporting system:

Fragmented technology stack - The platform consisted of multiple technology generations - JSPs, Angular, and different React implementations - all trying to maintain the same look and feel but with vastly different behaviors and codebases.
Static, limited reporting - Their existing reports were largely static HTML pages or basic tables with minimal functionality. Users couldn't filter, search, sort, or group data effectively, capabilities that had been standard in desktop applications for fifteen years.
Maintenance overhead - Implementing new features across multiple technology stacks required separate implementations in different places, increasing development costs and introducing more bugs.
Inconsistent UX - Users encountered dramatically different experiences depending on which part of the platform they accessed - some screens felt "old and antiquated" while others offered modern functionality.
Performance constraints - The team had to implement complex throttling and pagination systems to manage large datasets, creating architectural constraints that limited reporting capabilities.

Solution

Here's how Tebra adopted the Data Grid as the cornerstone of their modernization strategy and solved the aforementioned challenges:

Unified design system - They built a comprehensive design system using MUI components, with the Data Grid serving as the foundation for all reporting experiences across the platform.
Advanced grid capabilities - The team implemented sophisticated features including:
- Dynamic filtering with custom external filter components
- Fast client-side search across up to 10,000 rows
- Grouping and summarization functionality
- Customizable row density for improved readability
- Advanced sorting capabilities
Architectural optimization - They moved from database-heavy pagination to client-side data loading, enabling lightning-fast search and filtering while maintaining performance through strategic data limits.
Custom enhancements - Tebra extended the base functionality with:
- Reusable filter components with business logic
- Adjustable row height controls for user preference
- Integration with their existing style sheets and branding

Results

The implementation improved the UX across Tebra's entire ecosystem. Reports evolved from static displays to interactive interfaces that users expect in contemporary applications. The unified design system enabled teams to migrate legacy experiences seamlessly, speeding up development cycles. The Data Grid served as a catalyst in this process thanks to its built-in client-side search, with the improved data loading capabilities providing instantaneous search results while maintaining a high level of performance. This enabled the team to completely eliminate the complex throttling mechanisms they had previously relied upon.

Beyond immediate technical benefits, the standardized component library created a foundation for accelerated AI-assisted development workflows. The architecture is now well prepared for advanced features like lazy loading, which will further simplify the handling of larger datasets. Tebra is actively exploring additional features like Pivot Tables for their upcoming analytics dashboards.

Developer Experience

Exceptional documentation - Ronen praised MUI's documentation as "phenomenal," enabling teams to test and demo features without writing custom code, and helping sell the component capabilities to non-technical stakeholders.

Seamless integration - Since Tebra was already using the open-source MUI libraries, adopting the Data Grid was a natural progression that avoided vendor proliferation.

The team values the ongoing relationship with MUI and the ability to influence the product roadmap through feedback and potential feature requests.