Skip to content

leaf1191/2024_SolutionChallenge_EmergencyMate

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

30 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

2024_SolutionChallenge_EmergencyMate

🎯 Introduction

A patient died of cardiac arrest at a university hospital in South Korea after waiting for a long time.The hospital allegedly lefted the patient because he appeared to be sleeping. This case highlights the difficulty of managing long waiting lists in busy hospitals, and is a very serious issue that can lead to patient death in the worst case scenario. The hospital's solution to this problem is to increase nursing staffing, as well as CCTV and monitoring. However, nursing staffing is already understaffed, making round-the-clock staffing inefficient, and CCTV monitoring can't really detect patients in cardiac arrest.

EmergencyMate can detect when a patient really needs help by utilizing the call bell function, allowing nursing staff to focus their attention on that moment, enabling efficient nursing staff utilization and patient care. EmergencyMate also utilizes an Arduino device to check the actual heart rate and make an immediate call in case of a problem to actually solve the problem.

πŸ“½ Demo Video

youtube

πŸ›  Architecture

architecture

❓️ How To Use

1. Login

You can sign in to Google Social with the sign-in button in the center.

2. Select

Select a role type. Selecting Patient will take you to the Patient page, and selecting Admin will take you to the Admin page. Once you make a selection, you can't change it back until you log out.

3. Patient Page

The patient main page supports logging out and navigating to various pages. The following are the main features of the patient page

3.1. Heart Beat

This is the heart rate measurement page. Click the Bluetooth button at the bottom to connect with your Bluetooth device. If it is successfully connected, it detects your heart rate in real time and calls the administrator if there is a problem. A warning sound will sound when it is called.

3.2. Wait Info

This is the waiting information confirmation page. The left screen appears when you are not registered and the right screen appears when you are registered, and you can check your input information and waiting number.

3.3. Call Bell

This is the call bell. It's designed to be pressed for 3 seconds to activate, to prevent curious or accidental presses from causing confusion. A loud beep sounds when you call it. It must be registered to be called.

3.4. When Admin Call

This is the screen that the admin goes to when the patient is called. Patients cannot move themselves, but can only log out. When you log out, you are deleted from the admin list, and the patient is notified that it's their turn, which helps to keep things running smoothly.

4. Admin Page

This is the administrator screen. In addition to the logout button, you can check the registered patients in the grid system, call the patient's turn, and delete the patient from the grid. Click a patient to see their registered information. Click Add at the top to add unregistered patients.

4.1. Patient Register

This is the Add unregistered patient screen. Click the field in the list to go to the creation page and register details on the creation page. Once successfully registered, they will be added to the waiting grid.

4.2. When Patient Call

This is the screen that changes when a patient calls in. If even one patient is paged, a beep sounds and you can end the call by confirming the patient.

πŸ“˜ Execution Guide

For Android

You can download our apk at Releases.

For iOS

We will plan to expand our project can include ios users.

πŸ’‘ Contributors

μ‹¬μ’…μš° κΉ€μ§€ν˜„ κ°•ν˜œλ¦Ό μ΄λ‚˜μ—°
Flutter, Firebase Spring, Firebase Spring, Firebase Arduino, Video Editing

About

for solution challenge 2024

Resources

Stars

Watchers

Forks

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •