Project Title

MediConnect :- Real-Time Online Pharmacy Platform with 24x7 Doorstep Delivery

Introduction and Objective of the Project

In India, access to timely medication can be a critical need, especially in emergencies. Currently, most online pharmacy
platforms provide delivery within 1-2 days, which often fails to meet urgent requirements. This project aims to develop
an online pharmacy platform that connects local pharmacies with customers for real-time, hyperlocal, 24x7 delivery of
medications. The system will ensure that customers can order medications and receive them within 1-2 hours or even
faster, mirroring the quick delivery models used by food delivery services like Zomato or Swiggy. This platform will focus
on providing an immediate, convenient, and reliable medication delivery service at any time of day or night.
The pharmaceutical sector is undergoing a transformation with the increasing adoption of e-commerce and online
services. This project focuses on creating an online pharmacy platform that connects local pharmacies to customers in
need of medications, offering 24x7 real-time doorstep delivery.
The primary aim is to provide fast, efficient, and reliable delivery of both prescription and over-the-counter medicines,
reducing the wait time from days to just a few hours, or even minutes in emergencies.

The objective of this project is to design and develop a comprehensive online pharmacy platform that:
 Connects customers with local pharmacies, allowing for real-time order fulfillment.
 Offers 24x7 delivery for prescription and over-the-counter medications.
 Provides express delivery for emergency orders, ensuring medications arrive within 1-2 hours.
 Implements real-time order tracking for customers, providing transparency and convenience.
 Ensures that customers can easily upload prescriptions for quick verification and fulfillment.

Key Features:
Simple UI: Easy navigation for browsing and ordering.

Prescription Upload: Verified by professionals before order processing.

Live Tracking: Real-time order updates from pickup to delivery.

Fast Delivery: Hyperlocal model for 1-2 hour delivery.

Emergency Option: Expedited delivery for urgent medications.

Multiple Payments: Secure options, including COD.

Pharmacy Sync: Real-time inventory updates for accurate stock.

Project Category (RDBMS / OOPS / Networking / AI / ML / Data Science / Image
Processing etc.)

RDBMS (Relational Database Management System) / OOPS (Object-Oriented Programming).

Requirement Specifications (Detailed Functional Requirements and Technical

Specifications)
Functional Requirements:
1. User Management (Customer, Pharmacy, Admin)
 Customer Features:
o Sign-up/login via email, phone, or social media.
o Profile management (addresses, payment methods).
o Order history, prescription uploads, and order tracking.
 Pharmacy Features:
o Registration with pharmacy details.
o Manage stock, update inventory, and process orders.
o Prescription validation for controlled medications.
 Admin Features:
o Manage users, pharmacies, and orders.
o Generate reports on sales, customer activity, and pharmacy performance.
2. Order Management
 Order Placement:
o Browse and order medications (prescription and over-the-counter).
o Add multiple medications and addresses.
 Order Tracking:
o Real-time tracking for customers and pharmacies.
o Order status updates (pending, dispatched, delivered).
 Order Cancellation:
o Ability for customers to cancel orders before processing.
3. Payment System
 Payment Methods:
o Scan QR
4. Delivery Management
 Delivery Options:
o Standard and emergency delivery (within 30 minutes to 1 hour).
5. Prescription Management
 Prescription Upload:
o Customers upload prescriptions for medications that require it.
6. Inventory Management
 Stock Updates:
o Pharmacies update medication stock in real time.
Technical Specifications :
1. Technology Stack
 Frontend:
o Web App: Html, CSS, JavaScript, React.
 Backend:
o Node.js with Express.js for API handling.
 Database:
o MySQL for structured data storage.
o MongoDB for handling real-time data (optional).
2. Security
 Data Encryption:
o SSL/TLS for secure communication.
o AES for encrypting sensitive data.
3. System Architecture
 Microservices:
o Scalable microservices for handling orders, payments, and deliveries.
 Load Balancer:
o Distribute requests for high availability and reliability.
 Caching:
o Redis or Memcached for caching frequently used data.

Analysis (DFD & ER)

A Data Flow Diagram (DFD) is a graphical representation of how whole data flows through a system. DFD shows the
processes, data stores, external entities (sources or destinations of data), and the data flows that connect among them.
Levels of DFD
1. Level 0 (Context Diagram):
 o High-level view showing the system as a single process with its external entities and data flows.
2. Level 1:
o Breaks down the main process into sub-processes for more detail.
3. Level 2 and Beyond:
o Further decomposition of Level 1 processes, providing even more detailed views.
Components of a DFD
1. External Entities:
o Represent sources or destinations of data outside the system.
o Notated as rectangles.
o Example: Customer, Pharmacy Manager, or third-party systems.
2. Processes:
o Represent actions or functions that transform data.
o Notated as circles or rounded rectangles.
o Example: "Medicine Order," "Verify Payment."
3. Data Stores:
o Represent places where data is stored.
o Notated as open-ended rectangles or parallel lines.
o Example: "Inventory Database," "Transaction Records."
4. Data Flows:
o Represent movement of data between entities, processes, and stores.
o Notated as arrows labeled with data names.
o Example: "Order Details," "Payment Confirmation."
Why Use a DFD?
 To understand the system’s workflow.
 To identify data inputs and outputs.
 To detect inefficiencies or redundancies.
 Useful in systems analysis and design phases.
For this project, we included in DFD
 Customers place orders.
 The system processes the orders.
 The data flows to inventory, delivery systems, and payment gateways.
Level-1-DFD
ER-Diagram
An Entity-Relationship (ER) Diagram is a visual representation of entities (objects) in a system, their attributes, and the
relationships between them. It is commonly used in database design to model the system's data structure and how
different data elements are connected.
Components:
1. Entities: Represent objects in the system, such as Customer, Order, and Product. These are drawn as rectangles.
o Each entity has attributes, like Customer Name, Email, or Product Price, which are drawn as ovals linked
to the entity.
2. Relationships: Show associations between entities, represented by diamonds. For example:
o A Customer "places" an Order.
o An Order "contains" multiple Products.
3. Cardinality: Defines the number of relationships between entities:
o One-to-On: One entity is related to one of another (e.g., Payment for an Order).
o One-to-Many: One entity is related to many of another (e.g., Customer can place multiple Orders).
o Many-to-Many: Multiple entities are related to multiple of another (e.g., Order contains multiple
Products, and a Product is part of many Orders).

ER Diagram For MediConnect

Project Modules
1. Customer Module
o Registration & Login.
o Medication Search & Order: Browse and order prescription and over-the-counter medicines.
o Order Tracking: Real-time tracking of orders and delivery status.
o Payment: Secure payment processing via QR Scan and COD(Cash on Delivery).

2. Pharmacy Module
o Pharmacy Registration & Inventory Management: Pharmacies register and manage their stock in real-time.
o Order Processing: Verify prescriptions, process orders, and prepare for delivery.
o Order Tracking: Monitor and update order status.

3. Admin Module
o User & Pharmacy Management: Admins oversee customer and pharmacy accounts.
o Monitoring Pharmacies: Monitor Pharmacies performance, can modify pharmacy list.

Technologies to be used
Software Technologies :

1. Frontend (User Interface)

 Web App:
o React.js (for creating a responsive and user-friendly web interface).
o HTML5/CSS3/JavaScript (for basic structure and styling).

2. Backend (Server-Side Logic)

 Node.js with Express.js:
o Used to handle the business logic, API development, and server-side functionality.
o RESTful APIs will be used for communication between the frontend and backend.

3. Database Technologies
 MySQL:
o Relational Databases for structured data like user profiles, orders, pharmacy details, and payment records.

Hardware Technologies:
 1. Mobile Devices (For Customers & Delivery Staff)
 Smartphones (Android/iOS devices) for both customers to place orders and for delivery staff to track and manage
deliveries.
2. Delivery Hardware
 Smartphones with GPS (for Delivery Personnel):
o Delivery staff will use smartphones with GPS to reach at pharmacy location and to deliver medicine at address of
receiver.
 Delivery Vehicles (optional but may be needed for larger operations):
o Bicycles, motorcycles, or scooters for last-mile delivery of medicines.

Future Scope and further enhancement of the Project

 AI-based Recommendations: Integrating AI for recommending medications based on customer history and
preferences.
 Telemedicine Integration: Allowing customers to consult healthcare professionals and receive prescriptions for
medications directly through the platform.
 AI-based Chatbot: Implement an AI-powered chatbot to provide instant support, answer common queries (e.g.,
medication information, delivery status), and assist with order management.
 Telemedicine Integration: Add telemedicine services within the platform, where customers can consult with doctors
online and receive prescriptions through the platform. After consultation, the prescription can be directly uploaded
to the system, and the customer can have the medication delivered.
 AI-Powered Prescription Validation: Implement AI-powered Optical Character Recognition (OCR) and Natural
Language Processing (NLP) for automated validation and extraction of prescription details.
 Personalized Health Recommendations: Integrate AI and data analytics to provide personalized health and wellness
recommendations based on customer purchase history, prescriptions, and health profiles.
 Mobile Application: Developing a mobile app version for both Android and iOS for easier access on-the-go.
References
https://www.sciencedirect.com/science/article/abs/pii/S0169409X21004919
https://dspace.nuph.edu.ua/handle/123456789/31282
Date, C. J. (2004). An Introduction to Database Systems (8th Edition). Pearson.
https://www.geeksforgeeks.org/courses?source
https://www.w3schools.com/software?analysis