Med Tracker ‐ Architecture - yuzhi-wang/med_tracker GitHub Wiki

Project and solutions overview

The proposed solution, MedTracker, is a comprehensive digital platform designed to revolutionize the operations of hospitals by enhancing patient care, optimizing management processes, and streamlining workflows. Our solution is characterized by its multi-faceted approach to addressing the needs of its primary users: patients, doctors, nurses, and hospital administrators.

Type of Application

MedTracker is a web-based application with a responsive design to ensure accessibility across various devices, including desktops, tablets, and smartphones. This ensures that all users have access to the platform anytime and anywhere, facilitating real-time updates and interactions.

Hosting

The platform will be hosted on a secure cloud infrastructure to ensure scalability, reliability, and security. Leveraging cloud services enables us to provide a seamless experience for users and ensures that the platform can handle varying loads, especially during peak usage times. The cloud environment also facilitates easy updates and maintenance without disrupting the service.

Types of Users

  • Patients: Patients can create patient accounts for themselves and use that to access the patient dashboard. Patients can use the Patient dashboard to access appointment schedules and to send medical appointments requests.
  • Doctors: Doctors have access to the Doctor Dashboard, which provides medical equipment status, appointment management and patient record management. This dashboard supports effective treatment planning and streamlines patient consultations.
  • Nurses: Nurses benefit from a dedicated interface for managing doctor schedules.
  • Hospital Administrators: Administrators use the Admin Dashboard to manage hospital operations efficiently. This includes tools for appointment management, staff management, and patient record management.

Technology Stack

Languages

JavaScript, JSX, html, css

Tools

React, Node, Firebase, Developer IDEs (VScode, Webstorm)

Infrastructure

Firebase, AWS

Solution Design

High-Level Context View

Container View

Architecture layer

Non-functional requirements

Addressing the non-functional requirements (NFRs) is crucial to ensure the solution not only meets its functional goals but also delivers a robust, reliable, and user-friendly experience. Here's how MedTracker addresses various NFRs:

  • Privacy and Security: Adheres to HIPAA guidelines, employing end-to-end encryption, and secure authentication to safeguard user data.
  • Quality and Testability: Embraces CI/CD with extensive testing to ensure high-quality releases, supported by automated and manual QA processes. Leveraging SonarCloud for continuous code quality and security inspections, and integrating it into our CI/CD pipeline to automatically analyze every commit for bugs, vulnerabilities, and code smells
  • Capacity and Scalability: Utilizes AWS to scale resources dynamically, supporting peak loads efficiently with plans for future expansion.
  • Availability and Reliability: Targets 99.9% uptime using AWS's Elastic Load Balancing and Auto Scaling, backed by regular data backups and a disaster recovery strategy.
  • Usability: Designed for ease of use across all user groups, incorporating user feedback.

Assumptions

We will mock an entire hospital database with specific information. This includes personal information about doctors, nurses, administrators and patients, and information about various medical devices.