Skip to content

BUMETCS673/CS673OLSum25Team3

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

MyMedic

A secure, patient-centered health record platform.

Project Overview

MyMedic is a personal medical system designed to help patients by giving them secure and convenient access to their complete medical history. It centralizes patient health records, promotes efficient care coordination, and improves overall patient convenience.

Team Members & Roles

  • John Gutierrez – Team Lead, Requirements Lead, QA Lead, Design/Implementation Lead, Security Lead, Configuration Lead
  • Indra Sigicharla – Team Lead, Configuration Lead
  • Adriel Domingo – Requirements Lead
  • Tyler Gonsalves – Design/Implementation Lead, Configuration Lead
  • Mengliang Tan – QA Lead
  • Uzay Isin Alici – Security Lead
  • Hongcheng Ding – Design/Implementation Lead

Key Features

Essential

  • User Registration & Login
  • View and Edit Personal Information
  • Schedule and Add Appointments
  • Multi-Factor Authentication
  • Reset Password for safety
  • Download Medical Records

Desirable

  • Family Accounts
  • Notification System

Optional

  • Voice Assistant

Target Users

  • Patients managing personal or family health records
  • Healthcare Providers such as clinics and hospitals
  • Pharmacies for prescription and medication tracking

Technology Stack

  • Frontend: JavaScript
  • Backend: Python (Django)
  • Database: SQLite
  • Authentication: OAuth 2.0
  • Containerization: Docker

Development Strategy

Using TrunkFlow:

  • All production-ready code lives in the main branch.
  • Features, bug fixes, and hotfixes are developed in individual branches.
  • Changes are merged into main through pull requests with CI checks and code review.

Security Highlights

  • HIPAA Compliance: Protection of Personal Health Information (PHI)
  • Access Control: Role-based (patients, doctors, admins)
  • Authentication: Multi-factor authentication (MFA)
  • Encryption: HTTPS via SSL/TLS, encryption at rest and in transit
  • Vulnerability Scanning: Regular automated scans
  • Incident Response: Breach notification and containment procedures
  • Backup & Recovery: Daily secure backups and recovery plans

Tools & Infrastructure

  • GitHub (Version Control)
  • Google Drive (Collaboration)
  • Discord (Team Communication)
  • Docker (Containerization)

Risks & Challenges

Risks Identified:

  • Personnel & Communication
  • Incomplete Requirements
  • Lack of Tech Stack Proficiency
  • Security Concerns
  • Integration & Deployment Delays (High Priority)

Project Status

  • Critical Patient Features Implemented
  • Additional security features implemented
  • Testing and deployment scripts implemented

Next Steps

  • Essential features are all implemented.
  • Implement Doctor Features

About

Project repository for Team 3

Resources

Security policy

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Python 43.3%
  • HTML 30.4%
  • CSS 13.0%
  • JavaScript 11.5%
  • Shell 1.1%
  • Dockerfile 0.7%