UNIVERSITY OF MYSORE

JSS COLLEGE FOR WOMEN

CHAMARAJANAGARA
Affiliated to the University of Mysore & Accredited by NAAC

DEPARTMENT OF COMPUTER SCIENCE

A Project Synopsis

ON

Online Pharmacy Management System

SUBMITTED TO:

Vinay kumar B.sc, M.sc SUBMITTED FROM:

Asst. prof in Computer Science 1.ShazeeyaBanu(U01DP22S0021)

Department of Computer Science 2.Sowmya N(U01DP22S0032)

3.Harshitha P(U01DP22S0034)

4. Ivin(U01DP22S0035)
 CONTENTS

PARTICULARS PAGE NO

01 Introduction 03

02 Objectives 05

03 Problem Statement 05

04 Scope 06

05 Methodology 08

06 System design 10

07 Expected outcomes 10

08 Project Timeline 11

09 Resource Required 12

10 References 13
 Online pharmacy management system
Introduction
The proposed Pharmacy Management System is a web-based
application that enables pharmacists to efficiently manage their
pharmacy operations. The system will include modules for:
1.Inventory Management-Tracking stock levels, adding medicines, ad
notifying low stock
2.Prescription Management-Storing and verifying prescription from
doctors.
3.Sale & Billing-Generating invoice and managing customer purchases.
4.Supplier Management-Keeping records medicine suppliers and
purchase history.
5.User Management-managing different user roles like admin,
pharmacists, and customer.

Background Information.

Background A Pharmacy Management System is a software solution

designed to streamline and automate the operations of a pharmacy. It
helps manage inventory, prescriptions, sales, billing, and customer
records efficiently, reducing errors and improving service quality.it is a
system that consists of data entry, retrieval and monitoring stack,
sales, customer records and management administrator’s and
determination of quantity of each drug. PMS is developed to select the
medicine for managing all of the medicine and pharmacy and other
activities related with a pharmacy. this system also managing the
selling process, customer records and user records.
Importance pharmacy management system.
1. Enhances operational Efficiency.
2. Improve inventory Management.
3. Reduce human error.
4. Enhance customer service.
5. Ensures regulatory compliance.
6. Provides data security & user access control
7. Facility decision making.
Objectives:
1. User objects
• Admin: manage the entire system, including users,
inventory, and reports.
• Pharmacist: Handles medicine stock, sales, and
prescription.
• Customer: purchases medicines and views prescription.
• Supplier: provides medicines to the pharmacy.

2. Inventory Objects
• Medicine: Represents medicines with details like name,
batch number, expiry date, price.
• Category: Groups medicines based on their type
• Stock: Tracks medicine availability and low stock alerts.

3. Transactional Objects
• Sales: Represents customer purchases, including
medicines details and billing.
• Purchase order: tracks medicine procurement from
suppliers.
• Invoice: Generated for both customers and suppliers.
• Payment: Manages transactions, payment modes.
 4. Prescription management
• Doctor: Issues prescription for customer.
• Prescription: Contains prescribed medicines, dosage, and
duration.

Problem Statement
Pharmacies plays a crucial role in the healthcare system by ensuring
the availability and proper distribution of medicines. However, many
pharmacies still rely on manual or outdated systems, leading to
inefficiency such as:
1. Prescription Handling Challenges: errors in reading,
verifying and managing prescription can Inventory
Management issues: difficulty in tracking medicines stock,
expiry date, and shortages, leading to wastage or
unavailability of essential drug.
2. result in incorrect medications dispensing.
3. Billing and Sales Errors: Manual billing process or prone to
miscalculation and delay transactions, and record keeping
errors.
4. Lock of real time reporting: without automated reports,
pharmacy owners to struggle to track sales trends, stack
levels, and financial records.
5. Regulatory compliance issues: Managing and maintaining
records for audits, regulatory compliance, and taxation
manually is time-consuming and error-prone.
Scope
Inclusions:
• Inventory management (patient records, medication history,
prescription tracking)
• Sales and Billing (transaction processing, invoice generation,
sales reports)
 • User management (Roles and permissions for pharmacy
staff).
• Reporting (inventory, sales, prescription reports)
• Prescription management module (entry, verification,
dispensing).
Exclusive:
• Integration with external medical devices.
• Advanced financial accounting features beyond basic sales
and billing
• Mobile application development (focus is on a web -based
system)
• It will not replace the professional judgement of a
pharmacist or physician.
• The system will not directly integrate with medical devices
(e.g., blood pressure monitors, glucose meters) for real -time
data collection.
• The system will manage the medications that are received
from suppliers, and will not manage the manufacturing of
medications.

Methodology:
• A methodology is the combination of logically related
methods step by step techniques for successful planning,
control and delivery of the project. It is scientifically-proven,
systematic and disciplined approach to project
development and implementation.

1. Technologies used
The tools we are used in developing this system is
• Sublime
 • Xamppserver

• Microsoft word for project synopsis and project

documentation
• HTML
• PHP
• MYSQL
• Hardware Requirements
• Personal computer with at least
• At least 4GB of RAM
• At least Hard disk (300GB, 500GB.etc.)
• At least processor 2.7GHZ
1. System Architecture
• Presentation layer(front-end)
> Technology: HTML
> Function:
o User friendly and accessible interface.
o Forms for medicine management, billing, and
reports.
• Business logic layer (Back-end)
> Technology: PHP
> Functions:
o Manages authentication and authorization
(Admin, Pharmacist, Customer).
o Implements pharmacy workflows
o Ensure accessibility features like text – to –
speech integration.
• Data layer (Database)
> Technology: MYSQL
> Functions:
o Store medicine details, inventory, sales,
truncations, and user information.
 o Implements data relationship between
customers, prescription, and pharmacists.
Ensures data integrity and security.

• Development process:
> Methodology: Briefly mention the development
methodology you plan to use (e, g., agile, waterfall).

> Tools and technologies: list the programming languages,

frameworks, and database systems you plan to use.

> Timeline: provide a rough timeline for each phase of the

development process.

> Emphasis on testing: Highlighting the importance of

through testing to ensure a reliable system.

> Scalability: If applicable, mention any consideration for

future scalability.

> Security: Briefly address security concerns and how you

plan to mitigate them.

• System design
✓ High level architecture
▪ Presentation layer (front end)- user interface for
interaction.
▪ Business logic layer (back end)- processes user
requests and manages workflows.
▪ Data layer(database)-stores and retrieves
pharmacy data securely.
• Function modules
✓ User management
▪ Role- based access: Admin, Pharmacist,
customer.
▪ User authentication and authorization.

▪ Role- based access: Admin, Pharmacist,

customer
▪ User authentication and authorization
• Inventory management
▪ Stock management
▪ Expiry date tracking and alerts
▪ Supplier management

• Sales and billing

▪ Prescription- based sales
▪ Invoice generation
▪ Payment processing

• Prescription handling
▪ Upload and verify prescription
▪ Digital prescription storage

• Data base design

▪ Entity relationship diagram

o User (Admin, Pharmacist, Customer, Doctor,

PWD)

o Medicines (Name, Category, Price, Stock)

 o Prescription (Doctor_ ID, Customer_ ID,
Medicine_ ID, Dosage)
o Orders (Order_ ID, Customer_ ID, Quantity,
Total_ Price)

o Accessibility_ Settings (User_ id, Font_ size,

Color_ contrast, Screen_ Reader_ Enabled)

• System flow diagram

✓ Typical use cases
▪ Admin adds a pharmacist:
o Admin login-> Navigates to user
o Management->adds Pharmacist details saves.
▪ Pharmacist Manages Medicines:
o Pharmacist login-> Adds/ Updates medicine
details-> Save changes.
▪ Customer places an order
o Customer login in-> Searches medicine ->add to
cart -> Place holder->Payment-> Processed
• Doctor Prescribes Medicine
o Doctor login in-> Selects patient-> Prescribes
medicine -> Pharmacist verifies
• Expected Outcomes
• Faster prescription Processing: Reduced time for data
entry and prescription fulfillment.
> Minimized wait times for patient.

• Enhanced Inventory management:

> Accurate tracking of stock levels, preventing
stockouts and overstocking.
> Automated recording processes.
 • Reduce Medication Errors: Automated checks for drug
interaction and allergis

• Accurate Financial Reporting: Detailed sales reports and

transaction logs.
> Improved records.
> Increased patient loyalty: Personalized service
and improved customer satisfaction.
> Loyalty programs and discounts

• Faster prescription processing

> Electronic prescription entry and retravel
> Automated checks for drug interaction and
allergies.
> Reduce dispensing errors

Planning And Analysis (week -4)

• Week 1: Project initiation and Requirements Gathering:

Define goals and objectives.
• Week 2: System Analysis and Design: Analyze current
pharmacy workflows.
• Week 3: Vendor Selection & Planning: Research and
evaluate potential pharmacy.
• Week 4: Risk assessment and mitigation: Identify
potential risk and challenges.
Development and Configuration (week 5-12)
 • Week 5-8: System Development/Configaration: Develop
or configure the pharmacy management system
• Week 9-10: Testing: Conduct unit testing, integration
testing and system testing.
• Week 11-12: Data migration and preparation: Migrate
existing patient, inventory, and prescription data.
Implementation and Training (Week 13-16):

• Week 13: Staff training: Provide hands-on training and

support.
• Week 14: System Go- live: Implement the pharmacy
management system.
• Weeks 15-16: Post- Implementation support and
evaluation: provide ongoing support and
troubleshooting
Resource requirement

1. Human resource:
• Project manger
• System analyst/ Business analyst.
• Software Analyst
• Database Administrator
• Pharmacy staff

2. Hardware resources:
• Servers
• Workstation/ computer.
• Barcode scanners
• Printers
• Network equipment
• Backup systems
 3. Software resources:
• Pharmacy management system software
• Database management system
• Operating system
• Network security software
• Data migration tools.

4. Other resources
• Project management tools
• Testing environment

References:
[1]. “Online Pharmacy Management system” on date May
2016 “European Scientific Journal” Author= “Ernest
Onuiri”.
[2]. “Hospital Pharmacy Management” on date 2012
“Management Science of Health” Author= “Carlisl
George”.
[3]. “The Walgreens App Makes Life Easter” on date 2015
Author= “Walgreens” .
[4]. “Rapid application Development” on date 1991 Author
= “Martin.J.”
[5]. “Mobile Text Messaging for Pharmaceutical Care in
Hospital in China” on date 2008 Authors= “Mao.y,
Zhang.y, Zhal.s”.