Pharma space is a comprehensive and innovative platform designed to enhance the efficiency and accessibility of healthcare services. The system caters to the needs of patients, pharmacists, and administrators, providing a seamless experience for managing medical information, prescriptions, and medication inventory.
The motivation behind this project stems from a deep commitment to enhancing healthcare accessibility. By creating a centralized platform, the goal is to make healthcare services readily available to a wider audience, ensuring patients can easily connect with pharmacists and access vital medical information.
The project is currently in the development stage, progressing through milestones with continuous improvements in code implementation and execution. Notable learning curves were experienced during sprints 2 and 3, particularly in the areas of authentication and user login.
One prominent issue encountered was the slowness in fetching data from the backend to the frontend. Despite this challenge, the frontend functionality remains robust, albeit with some organizational improvements needed.
Looking ahead, the project will require deployment, likely through platforms such as Google Cloud or similar services, to ensure accessibility and scalability in the near future.
This project follows a specific code style to ensure consistency and readability across the codebase. Adopting a consistent coding style is important for collaboration and maintenance.
We adhere to the Standard Code Style Guide for this project. Please review the guide before contributing to ensure that your code aligns with our established conventions.
- MERN Stack (MongoDB, Express.js, React.js, Node.js)
- JavaScript
1. User Registration and Authentication:
- Guests can register as patients, providing essential details such as username, name, email, password, date of birth, gender, and emergency contact information.
- Pharmacists can submit requests for registration, including details like username, name, email, and professional qualifications.
2. User Management:
- Administrators have the ability to add or remove other administrators, ensuring smooth system operation.
- Removal of patients or pharmacists from the system is facilitated by administrators.
3. Medicine Information:
- Patients, pharmacists, and administrators can access a detailed list of available medicines, including images, prices, and descriptions.
- Pharmacists can view the quantity and sales data for each medicine.
4. Cart Management and Checkout:
- Patients can add both over-the-counter and prescription medicines to their cart.
- Multiple delivery addresses can be added and selected during the checkout process.
- Flexible payment options include wallet, credit card (using Stripe), or cash on delivery.
5. Order Management:
- Patients can view detailed order information, check the status, and cancel orders if needed.
- Pharmacies receive notifications for out-of-stock medicines and can manage inventory accordingly.
6. Reporting and Analysis:
- Administrators and pharmacists can generate total sales reports based on a chosen month.
- Pharmacists can filter sales reports based on specific medicines or dates.
7. Communication Features:
- A chat feature allows patients and pharmacists to communicate with each other.
- Pharmacists can also engage in doctor-patient communication.
8. Wallet and Refunds:
- Patients can view the amount in their wallet, including funds due to order cancellations.
- Pharmacists can track wallet funds related to monthly salary payments.
9. Additional Functionalities:
- Patients can view current and past orders, search for medicines, and explore alternatives for out-of-stock items.
- Pharmacists have the ability to archive and unarchive medicines, ensuring sales information is preserved.
These instructions will help you get a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
-
Click on
code
->Download ZIP
-
Extract the zip file and open it in visual studio code.
-
Navigate to the
server
folder using the terminal and run the following command:npm install
-
Next, navigate to the
client
folder in the terminal and run the following command:npm install
To launch the project locally, follow these steps:
Navigate to the server
folder using the terminal and run the following command:
npm start
Next, navigate to the client
folder in the terminal and run the following command:
npm start
1. Express.js(express
)
- Description: Web application framework for Node.js, used for building the backend server and handling HTTP requests.
- Documentation: Express.js Documentation
2. Mongoose(mongoose
)
- Description: Elegant Object Data Modeling (ODM) library for MongoDB and Node.js, streamlining interaction with MongoDB.
- Documentation: Mongoose Documentation
3. Axios(axios
)
- Description: Promise-based HTTP client for making HTTP requests, facilitating seamless communication with external APIs.
- Documentation: Axios Documentation
4. Bcrypt(bcrypt
)
- Description: Library for hashing and salting passwords, fortifying the project's password security.
- Documentation: Bcrypt Documentation
5. Cors(cors
)
- Description: Middleware for Express.js enabling Cross-Origin Resource Sharing (CORS), granting controlled access to server resources.
- Documentation: Cors Documentation
6. Dotenv(dotenv
)
- Description: Zero-dependency module seamlessly loading environment variables from a
.env
file intoprocess.env
. - Documentation: Dotenv Documentation
7. Jsonwebtokens(jsonwebtoken
)
- Description: Robust library for creating and verifying JSON Web Tokens (JWT), a cornerstone for user authentication.
- Documentation: Jsonwebtoken Documentation
8. Morgan(morgan
)
- Description: Express.js middleware providing an HTTP request logger, capturing essential information about incoming requests.
- Documentation: Morgan Documentation
9. Multer(multer
)
- Description: Middleware tailored for handling multipart/form-data, an essential tool for efficient file uploads.
- Documentation: Multer Documentation
10. Nodemailer(nodemailer
)
- Description: Powerful module for sending emails, often utilized for tasks like dispatching confirmation emails.
- Documentation: Nodemailer Documentation
11. Nodemon(nodemon
)
- Description: Intelligent utility monitoring changes in source code and autonomously restarting the server.
- Documentation: Nodemon Documentation
12. Socket.io(^4.7.2
)
- Description: Real-time bidirectional event-based communication library for Node.js. Facilitates real-time communication between web clients and servers.
- Documentation: Socket.IO Documentation
13. Stripe(@stripe/stripe-js
and stripe
)
- Description: Libraries dedicated to handling Stripe payments, a leading payment processing platform.
- Documentation:
For detailed information and usage instructions, refer to the official documentation linked above for each API.
To ensure the proper functioning of this project, you can perform various tests using tools like Postman. Below are some examples demonstrating how to test different aspects of the code.
Prerequisites
- Before running the tests, make sure you have Postman installed on your machine.
We welcome contributions from the community! If you'd like to contribute to the development of this project, follow these guidelines:
-
Fork the Repository: Click on the "Fork" button on the top right corner of this repository's page.
-
Clone the Repository: Clone the forked repository to your local machine using the following terminal command:
git clone https://github.com/your-username/your-forked-repo.git
-
Create a Branch: Create a new branch for your contributions:
git checkout -b feature/your-feature-name
-
Make Changes: Make your desired changes to the codebase.
-
Commit Changes: Commit your changes with a meaningful commit message:
git commit -m "Add your meaningful commit message here"
-
Push Changes: Push your changes to your forked repository:
git push origin feature/your-feature-name
-
Create a Pull Request (PR): Open a Pull Request against the main branch of the original repository. Provide a clear title and description for your changes.
-
Code Review: Participate in the code review process. Make any requested changes if needed.
-
Merge: Once your changes are approved, they will be merged into the main branch.
Thank you for contributing to our project! 🚀
-
YouTube Tutorial: Coding a video calling app with React
-
Youtube Tutorial: Used to get an overview and understand the concepts of the MERN stack
-
Youtube Tutorial: Used to learn Node.js
-
Youtube Tutorial: Used to learn react contexts and hooks
This project is licensed under the MIT License & Apache License