The document describes a pharmacy product management database system. The system aims to easily manage medicine inventory, create pharmacy sales reports, simplify identifying personnel on duty during sales, and record customer purchase histories. It involves entities like customers, employees, pharmacists, suppliers, medicines, and transactions. Relationship diagrams show how these entities relate to each other in the database system designed to organize pharmacy product data and management.

1. PHARMACY PRODUCT MANAGEMENT
DATABASE SYSTEM
primakara.ac.id
TEAM
3

2. Objective Ease Of Managing
Medicine Inventory
Ease in creating
pharmacy sales reports
Simplifying the
identification of the
personnel on duty during
medication sales
transactions
Recording buyers as
members to keep a
record of their medicine
purchases.
The goal is to organize the storage of product
data available in the pharmacy, along with the
management involving employees, administrators,
aiming to enhance efficiency in accessing relevant
information
Benefits
TEAM
3

3. Entity Relations
Diagram
• Customer
• Employee
• Pharmacist
• Supplier
as a buyer and prescriber of medicines to the pharmacist, their data is
recorded and they can become members
as a transaction system user to help serve customers and is tasked with
inputting sales data for products that have been sold
People who prescribe medicine according to the prescription given
As a medicines provider and is divided into several types from generic
medicine to medicine that must have a doctor's prescription.
E n t i t y
• Medicine
• Transaction
Contains basic information about the medicines available in the pharmacy,
like the name of the medicine, available stock, expiration date, medicine
description, price, unit, and medicine category
The activity or process of exchanging money or payment from customers to
employees to obtain medicine from the pharmacy, including the issuance of a
receipt that stores various attributes of related entities.
TEAM
3

4. Diagram
Entity Relations
TEAM
3

5. ATTRIBUTES
id_med
"id_med" functions as an identifier for a medicine, where it also functions as the
primary key.
name
"name" is used to provide the name for a medicine.
price
"price" is used to provide the price for a medicine
exp_date
"exp_date" is used to provide the information of expired date for a medicine
id_supp
"id_supp" functions as a foreign key referencing the supplier table.
description
"description" is used to provide the description for a medicine
stock_amt
“stock_amt” is used to specify the stock amount for a medicine.
MEDICINE
ENTITY
This entity serves as a data storage for available medicines and has relationships
with other entities such as pharmacists and suppliers, where suppliers provide
medicines and pharmacists compound a medicine.
TEAM
3

6. SUPPLIER
ENTITY
ATTRIBUTES
This entity serves as a data storage for suppliers, where these suppliers have
relationships with other entities such as medicines, which are supplied by the
supplier.
id_supplier
"id_supplier" serves as an identifier in a supplier, where it also functions as the primary key.
name
"name" is used to provide the name for a supplier.
address
"adress" is used to provide the address for a supplier
phone_num
"phone_num" is used to provide the phone number information for a supplier
TEAM
3

7. EMPLOYEE
ENTITY
Employees are workers who take care of general pharmacy operations, the
division is:
1. Cashier, tasked with serving customers who want to buy medicine, as well as
receiving medicine prescriptions from customers
2. Warehouse Section, tasked with managing medicine stock in the warehouse
as well as ordering medicine that have run out from suppliers
id_employee
name
ATTRIBUTES
"id_employee" serves as an identifier in a employee, where it also functions as the primary
key.
"name" is used to provide the name for an employee.
position
"position" as a marker of someone's position

8. PHARMACITES
ENTITY
Epharmacists are people who mix medicines according to medicine
prescriptions submitted by customers, as well as receiving and checking
medicines sent by suppliers.
id_pharmacits
name
ATTRIBUTES
"Id_pharmacites" serves as an identifier in a pharmacits, where it also functions as the
primary key.
"name" is used to provide the name for a pharmacits.
position
"position" as a marker of someone's position

9. TRANSACTION
ENTITY
A transaction is an event that occurs due to an interaction between a buyer and
a seller. In this context, a transaction can be evidenced by the existence of a
transaction receipt, for example a sales receipt.
id_trans
ATTRIBUTES
"id_transaction" A transaction ID is a unique code that is generated when a transaction
occurs. where it also functions as the primary key.
med_recipe
A prescription is a written order from a doctor or other qualified healthcare professional
that authorizes a patient to purchase a specific medication.
trans_date
The transaction date is the date on which a transaction takes place.
price
The price in this section is the price of a drug or item that is purchased during a
transaction.
id_med
"id_med" functions as an identifier for a medicine, where it also functions as the primary
key.
id_phar
"Id_pharmacites" serves as an identifier in a pharmacits, where it also functions as the
primary key.
id_emp
"id_employee" serves as an identifier in a employee, where it also functions as the primary
key.
id_cust
"id_employee" serves as an identifier in a employee, where it also functions as the primary
key.

10. CUSTOMER
ENTITY
as a buyer and prescriber of medicines to the pharmacist, their data is recorded
and they can become members. A customer entity in a program is a way to
represent a customer within the program's data model. It's essentially a
collection of attributes that define the characteristics of a customer.
id_cust
name
ATTRIBUTES
"id_employee" serves as an identifier in a customer, where it also functions as the primary
key.
"name" is used to provide the name for a supplier.
contact information
purchase history
Email address, phone number, physical address, etc.
A record of the customer's past purchases, including items purchased, dates, and amounts.

11. MEET OUR
EXPERT TEAM
Wisnu Ambara Rahayu Wulandari Santika Pradnyan
NIM: 2301020085
Prodi: Teknik Informatika
Githa Amyguna Gautama
TEAM
3
Nim: 2301020022
Prodi: Teknik Informatika
Nim: 2301031021
Prodi: Sistem Informas Akuntansi
Nim: 2301020012
Prodi: Teknik Informatika
Nim: 2301020008
Prodi: Teknik Informatika

12. THANK YOU
F O R Y O U R A T T E N T I O N
primakara.ac.id
TEAM
3