CareQuest

A load balancing platform for medical services aimed at bringing order to the chaos caused by COVID-19

Contents

1. Short description
2. Demo video
3. The architecture
4. Long description
5. Project roadmap
6. Getting started
7. Live demo
8. Built with
9. Contributing
10. Versioning
11. Authors
12. License
13. Acknowledgments

Short description

What's the problem?

COVID-19 has been on a rampage all across the globe since the past 5 months. From less than a million cases in February, and currently having more than 10 million cases across the globe. This has caused widespread panic and disorder. This panic is interfaring with not only the functioning of already established medical structure but also allocation of resources which can cost someone's life.

How can technology help?

With increasing reach of technology, relevant information can be extracted from concerned authorities. This information can be used in resource allocation to balance load on various authorities. Providing information can keep people informed about the current scenario and have a calming effect.

The idea

CareQuest aims to bring order to the chaos caused by COVID-19. To do so, CareQuest Services extracts information from its custom network of registered hospitals and government sources which is used in resource allocation and service recommendation with the aim of load balancing.

Demo video

The architecture

1. PushBot generates regular updates (new beds in hospitals, new plasma patients/donors, stat updates) to the user and pushes them as notification
2. IBM Watson provides assitance to the user as CareBot as it helps him/her guide through different features and functionalities
3. User accesses the domain using Heroku services
4. Heroku executes nodeJS to render the website
5. Server requests SendGrid to send mail after either of the plamsa forms is submitted
6. SendGrid sends mail to user that contains form data
7. Server sends requests to Firebase
8. Firebase Authentication manages user login, register, and verification services
9. Firebase sends all id card images to its Firebase Storage / Bucket
10. ID card image is then sent to Tesseract for OCR processing
11. Firebase registers all variables related to hospital and user and stores them in Firebase Realtime Database
12. HERE Map API (Track-a-Bed) sends hospital data to Firebase Realtime Database to link with user data
13. mongoDB sends all hospital data from its collection to HERE Map APIs to be displayed under Track-a-Bed

Long description

More detail is available here

Project roadmap

Getting started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.

Ways to host the project on localhost :

Step 1 : Download and Install NodeJS and NPM packages from nodejs.org, or just use the following commands in your terminal window :

                    sudo apt-get install nodejs
                    sudo apt-get install npm

Step 2 : Install the http-server package from npm. Use the following command in your command prompt or terminal window :

                    npm install -g http-server

Step 3 : Navigate to the project directory using the command line interface and use :

                    node app.js

Step 4 : Now, open your browser and navigate to http://localhost:31000/ to access the project.

Live demo

You can find a running system to test at care-quest.herokuapp.com

Built with

• IBM Watson - Chat Assistant : CareBot
• HERE Maps API - HERE Map API for Track-a-Bed
• Firebase - Database and Storage Used for Plasma Bank
• nodeJS - Server Runtime Environment
• Github - Version control
• Heroku - Cloud Hosting Service
• jQuery - JavaScript Library for handling AJAX
• mongoDB - NoSQL Database to handle data for Track-a-Bed
• Tesseract - OCR system for CareNet
• PushBot - Notifications
• SendGrid - Mailing Service
• AOS - Animation for landing and Plasma Bank pages
• Bootstrap - Frontend components
• Semantic UI - UI/UX Design

Contributing

Please read here for details on our code of conduct, and the process for submitting pull requests to us.

Versioning

We use github for versioning. Versions will be made available as tags on this repository.

Authors

• Prashant Jha - Backend - pjflux2001
• Sudhanshu Mohan Kashyap - Backend And Frontend - mightyjoe781
• Umang Barthwal - Backend And Frontend - barthwalumang
• Apoorv Garg - Frontend - ApEdu
• Aayush Kaushal - Frontend - Aayush-7

License

This project is licensed under the Apache 2 License - see the LICENSE file for details

Acknowledgments

• Based on Billie Thompson's README template.