MonitorMe

Executive summary

This document presents an architectural proposal done by AchitectsEvolutionZone team for the O’Reilly Winter 2024 Architectural Katas contest. The architecture describes our approach and decisions for implementing MonitorMe, a software that will help healthcare professionals by leveraging the power of new devices to provide accurate, timely, and easy to read patient data. Helping them in diagnosing and choosing treatments will lead to faster, better, and informed decisions for healthcare professionals and faster recovery time for patients.” A thorough requirements analysis proses was used to identify architectural characteristics, user flows, C4 diagrams, sequence diagrams, infrastructure layout, user interface mockups, and ADRs were used to describe our vision on how MonitorMe can be designed and implemented.

Context and overview

StayHealthy, Inc. is a large successful medical software company that already has two popular cloud-based SAAS products on the market (MonitorThem and MyMedicalData). The next product they want to bring to life is MonitorMe, a product that will collect patient vital signs from various sources (like wearables and medical devices that measure heart rate, blood pressure, oxygen level, blood sugar, respiration rate, electrocardiogram (ECG), body temperature, and sleep status). This document intends to describe the architecture of MonitorMe, constraints, and considerations for building an easy-to-use, reliable, scalable, and secure system.

Video presentation

You can find a video presentation of our design process and proposed solution at this page.

Table of contents

1. MonitorMe story

2. MonitorMe system overview

2.1. Client Initial requirements

2.2. Requirements analysis

2.2.1. User journey - hospital admin

2.2.2. User journey - medical profesional

2.2.3. Requirements analysis conclusions

2.2.4. Glossary

2.3. Cross-functional requirements

2.4. Capabilities

2.4.1 Consolidated Monitoring Screen

2.4.1.1. Pacient Overview

2.4.1.2. Desktop UI

2.4.1.3. Entity Management

2.4.2 MonitorMe Mobile App

2.4.2.1 Launch UI

2.4.2.2 Pacient Overview

2.4.2.3 Alert

3. Architecture visualization

3.1. OnPremise infrastructure

3.2. C4 diagram

3.3. Sequence diagrams

3.4. Architecture style

3.5. Deployment

4. ADR

4.1. ADR001-WiredCommunicationGatewayToCMS

4.2. ADR002-HL7TransmissionToDeviceGateway

4.3. ADR003-WiredCommunicationGatewayToServer

4.4. ADR004-WLANDataRequestsToServer

4.5. ADR005-WLANReceiveAlertsFromServer

4.6. ADR006-DeviceGateway

4.7. ADR007-MessagingBrokerForDeviceGateway

4.8. ADR008-WiredCommunicationServerToCMS

4.9. ADR009-NoSQLOnPrem

4.10. ADR0010-InMemoryCaching

4.11. ADR0011-OnPremServerCluster

4.12. ADR0012-EventDrivenArchitecture

Contributors

• Alina Avram
• Ionut Burzo
• Hajni Burzo-Covaci
• Claudiu Cretu
• Mihai Todorut

We are a team of software professionals, keen to improve our software architecture practice so that we give projects clarity, transparency, predictability, and lower the risk of project failure (not in time, scope, and budget).

Contact Information: ArchitectsEvolutionZone@evozon.com