Hospital Logistics

CSCC01 - UTSC

Group Members:
Currently:
Xiaoran Yu
Darren Guerina
Catherine Qu

Originally:
(Unfortunately, two teammates dropped the course on Jun 16 and one teammate dropped the course on Jun 13.)
William Lam
Travis Shao
Xiaoran Yu
Zhuolin Fu
Darren Guerina
Catherine Qu

Introduction

Hospitals have the duty of saving lives and serving patients by providing the best care possible. It is crucial to equip a powerful management system for hospitals because any management error may cause serious consequences such as delays in patients' treatment or even patient deaths. Therefore, our team aimed to build an ideal management system for hospitals that can be referenced by future developers who will build an actual one.

Our system supports the following functionalities:

• Patient Directory
• Physian Directory
• Patient Profile
• Patient Profile
• Medical Equipment Availability
• Bed Availability
• Staff Member Shifts Management
• Inventory Management
• Previous/New workplaces for staff
• Patient Scheduler/Categorizer
• Medicine Registry (might be removed)

Installation

Git: Version control system.
Node.js and npm: JavaScript runtime and package manager.
MongoDB: NoSQL database.
Express.js: Backend framework.
React: Frontend framework.
Visual Studio Code: Source-code editor.
Postman/ThunderClient: API testing tool.
Webpack: Module bundler.
ESLint: Linting tool.
Prettier: Code formatter.
Enzyme (Optional: React testing utility.
Redux (optional): State management.
Docker (optional): Containerization platform.

To run the app:

• backend: node server.js
• Frontend: npm start

Technology Stack

MERN Tech stack
M - MongoDB
E - Express.js
R - ReactJs
N - Nodejs

Contribution

• We use Git Flow.
• Pull requests will be used to review potential merges of branches when features are being done.
• The typical naming conventions (i.e feat, bugfix, etc) will be used when naming branches. An example would be "feat/user-authentication".
• Hyphens will be used to separate words when naming branches and '/' will be used to categorize branches heirarchically.
• We use Jira as our ticketing website.
• Each commit message starts with a keyword, followed by a detailed description of the changes made. For example, "chore: prettier".