A Digital Platform for Renal Care

By leveraging these technologies, we implemented several vital features. Among them were:

1. Micro-front-ends. The monolithic structure was split into separate repositories using Webpack Module Federation. This required extensive code rewriting to enable interaction between modules, establish dependencies, configure deployment, and address security challenges. A dynamic global data store was created by our team to allow new modules to plug in additional storage on the fly. Routing and permissions were also modularized.
2. Offline capabilities. Andersen developed an offline mode initial version to enable data entry from dialysis machines even during Internet disruptions. Using IndexedDB transactions as an intermediary layer, data is saved locally before syncing with the server when connections resume. This demonstrates the potential for full offline support in the future.
3. Patient calendar. Grids were used by us to enable powerful and adaptable organizational features catered to different clinics’ scheduling needs and event types. Thanks to this feature, patient treatments and appointments are seamlessly coordinated.
4. Testing. A proxy server using Node and MSW was set up for more robust front-end testing. By manipulating server responses, real application requests can be made with substituted data to validate functionality and flows.

When working on this data management system project, our team successfully considered and overcame several specific challenges:

1. Complex requirements gathering: Compiling all necessary clinical, operational, and billing workflows proved challenging due to the uniqueness of these processes, as they demanded in-depth clinical knowledge and expertise. Constant cross-checks and validation were required because of the peculiarity of the medical domain and hemodialysis practice;
2. Rigorous testing, which is demanded due to the possible high cost of any future bugs or mistakes in clinical practice;
3. Excellent usability in specific clinical settings (such as during medical procedures, when gloves are often worn, as well as many others);
4. Managing two teams (RenalWorks' in-house team and Andersen's allocated team);
5. Team coordination spanning time zones. The blended onshore/offshore structure introduced some responsiveness issues across time zones;
6. Custom billing module development from scratch to align with specific reimbursement rules.

Critical success factors were:

1. Excellent Product Owner from RenalWorks' side, with software development and extensive clinical background and first-hand hemodialysis experience from clinical, administrative, and business perspectives, showing the utmost involvement in communication with Andersen's team;
2. As the requirements’ collection process was complex, the involvement of a seasoned Project Manager and a Business Analyst with medical education was key;
3. A comprehensive Discovery phase provided the project with a clear vision of the future solution, identifying key functionalities and potential challenges and laying the foundation for subsequent successful development;
4. The continuous refinement and clarification of requirements throughout the development process. Given the intricate nuances of the healthcare domain, having professionals with medical education and practical experience proved crucial. Their insights and domain knowledge contributed to a seamless collaboration between the technical team and medical experts;
5. Focus on usability by all team members guided by an experienced UI/UX specialist with cross-domain expertise;
6. Two-tier model of project management, where a healthcare-experienced Project Manager oversaw the technological processes. Meanwhile, a Delivery Manager ensured that specialists were getting timely support to resolve any bottlenecks, involving additional talent whenever needed and overseeing resources. Such management structure enabled smooth progress, keeping the project on track. Although the project members were located in different regions, smooth coordination across time zones kept all contributors aligned.