The model of the Pharmacy Management System ER Diagram is shown in this ER (Entity Relationship) Diagram. It shows all of the database tables and the connections between customers, pharmacists, medicines, purchasing, sales, and reports.
It uses structured data and relationships between structured data groups. To define the functions of the Pharmacy Management System. The Pharmacy Management System’s main parts are the Pharmacy, the Medicines, the pharmacist, the customer, the Inventory, and the reports.
ER Diagram for Pharmacy Management System: Details
The table shows the overall description of the ER Diagram for Pharmacy Management Management System. It has a complete overview of the project’s information.
| Name: | Pharmacy Management Management System ER Diagram |
| Abstract: | The Pharmacy management system ER diagram depicts the relationship between various entities. It can be thought of as a blueprint for your system (project) structure. |
| Diagram: | ER Diagram is also known as Entity Relationship Diagram |
| Tools Used: | Diagraming tools that provide ER diagram symbols. |
| Designer: | ITSourceCode.com |
What is Pharmacy Management System?
A type of business application software called a pharmacy management system automates the operation of pharmacies. The organization and maintenance of the drug usage process within pharmacies are accomplished by storing data and enabling functionality.
It is a platform that controls the workflow in pharmacies and controls data and operations related to medications. The main purposes of pharmacy software are a point of sale, inventory tracking, and prescription filling and processing.
Pharmacy Management System Features
- Pharmacy Management – Pharmacy Management is the main feature of this system wherein ER diagram contains the basic details needed for managing medical records and inventory. This basic information was composed of medicine records, sales, counts, and inventories. This will also monitor or check the customers’ info and purchasing or order status.
- Customer Management – This feature plays a big role in the system because this gathers and manages the important information of the customer. This information was used to track their orders and purchasing records and other important matters regarding the system to assure that the services were given properly.
- Manage Medicines – The medicine management will be done by the admin to track the activities and sales of the pharmacy. This will also monitor the performance of the pharmacy as well as their basis for inventories.
- Manage Medicines Inventories – Its feature will manage and monitor the inventories of the medicines as well as their sales for a given period of time. The activity of this will include the monitoring of the purchased medicine, the type of medicine, and their prize.
What is an ER Diagram?
In DBMS, the ER Diagram of the pharmacy management system is also known as the system’s database design. It is the graphical depiction of relationships between all the entities involved in the system. Its major components are Entities, Attributes, and Relationships.
To build and troubleshoot relational databases, the pharmacy system ER Diagram is used. It works best with DFD (Data Flow Diagram), which is responsible for data movement. Developing the database design for the pharmacy management system would be much easier with the help of ER diagram.
ER Diagram for Pharmacy Management System
ER Diagram of Pharmacy Management System shows the system entity relationships in each entity and their supposed functions in each relationship.
Based on the image above, the Entity-Relationship Diagram for Pharmacy Management System tables were the following: customer, pharmacist, medicines, purchasing, sales, and reports.
The tables are made to meet the required specification of the system and provide much more specific details of each entity within the system.
Pharmacy Management System Database Design
This Pharmacy management system database design was made based on managing pharmacy requirements. The system can encode both customer and medicine information. Pharmacy admins can have access to the status and information of the medicine in terms of the number sold and remains to identify the inventories of sales and stocks.
The features included in the system ER diagram were the security and monitoring of the medicines’ information and status and customers’ order. These features were also listed and recorded in reports that served as the history of transactions done in the system.
Pharmacy Management System ER Diagram Tables
These tables below provide the complete database table details such as Field Name, Descriptions, data types, and character lengths. Each of these tables represents the characteristics and attributes of data storage.
The field column presents the names of each database’s attributes, the description column gives the complete thought of each attribute, the type column is their data type and the length is for their character lengths.
Table Name: Customer
| Field | Description | Type | Length |
| cust_ID (PK) | Customer ID | Int | 11 |
| fname | First Name | Varchar | 255 |
| lname | Last Name | Varchar | 255 |
| gender | Gender | Int | 11 |
| age | Age | Int | 11 |
| contact_add | Contact Address | Int | 11 |
| cust_email | Customer Email | Varchar | 255 |
| cust_pass | Customer Password | Varchar | 255 |
Table Name: Pharmacist
| Field | Description | Type | Length |
| phar_ID (PK) | Pharmacist ID | Int | 11 |
| fname | First Name | Varchar | 255 |
| lname | Last Name | Varchar | 255 |
| gender | Gender | Int | 11 |
| age | Age | Int | 11 |
| contact_add | Contact Address | Int | 11 |
| phar_email | Varchar | 255 | |
| phar_pass | Password | Varchar | 255 |
Table Name: Medicines
| Field | Description | Type | Length |
| med_ID (PK) | Medicine ID | Int | 11 |
| med_category | Medicine Category | Varchar | 30 |
| name | Name | Varchar | 30 |
| description | Description | Varchar | 30 |
| price | Price | Varchar | 30 |
Table Name: Purchasing
| Field | Description | Type | Length |
| purchase_ID (PK) | Purchase ID | Int | 11 |
| cust_ID (FK) | Customer ID | Int | 11 |
| med_ID (FK) | Medicine ID | Int | 11 |
| amount | Amount | Varchar | 255 |
| date | Date | Date |
Table Name: Sales
| Field | Description | Type | Length |
| sales_ID (PK) | Sales ID | Int | 11 |
| phar_ID (FK) | Pharmacist ID | Int | 11 |
| cust_ID (FK) | Customer ID | Int | 11 |
| med_ID (FK) | Medicine ID | Int | 11 |
| count | Medicine Count | Int | 11 |
| purchase_ID (FK) | Purchase ID | int | 11 |
| date | Date of Sale | Date | |
| total_amount | Total Amount | Varchar | 255 |
Table Name: Reports
| Field | Description | Type | Length |
| report_ID (PK) | Report ID | Int | 11 |
| purchase_ID (FK) | Purchase ID | Int | 11 |
| sales_ID (FK) | Sales Id | Int | 11 |
| cust_ID (FK) | Customer ID | Int | 11 |
| date | Date of Report | Date |
The tables given will be the basis for developers on how would they do the pharmacy management system database design. It has the complete description of the database and they will put this into the program or data storage the same as the names given to each of the tables. They will create a database with the attributes given as well as the value of each attribute.
Pharmacy Management System ER Diagram [PDF]
The ER Diagram for Pharmacy Management System in DBMS Pdf provides the information explaining the concepts of the project database. You may apply this information to your capstone project. You can also use it directly or modify its content depending on your project’s requirements.
How to create an Entity-Relationship (ER) Diagram
Time needed: 5 minutes
Steps in building the ER Diagram for Pharmacy Management System with Cardinality Ratio.
- Step 1: Familiarize the ER Diagram (Entity Relationship Diagram) Symbols and Cardinality
Entity Relationship Diagram – shows the structure of data types in a project. It uses symbols to clarify its parts and relationships. Their symbols and applications must be familiarized before you build the ER Diagram.
ER Diagram Symbols:
• Field – are the parts of a table that define the entity’s characteristics. In the database that the ERD models, attributes are commonly thought of as rows.
• Keys – is a technique to categorize data qualities. It is used to organize ER diagrams and assist users in modeling their databases to ensure that they are efficient. This is also used to connect different tables in a database.
– Primary Key: identifies a single entity instance which means a unique attribute or set of attributes.
– Foreign Key: is produced when data attributes have one too many relationships with other entities.
ER Diagram Cardinalities:
The styling of a line and its termination demonstrates cardinality and ordinality.
The greatest number of times an instance of one thing can be related to instances of another entity is referred to as cardinality.
While Ordinality refers to the fewest number of times a single entity instance can be linked to another. - Step 2: Finalize the entities included
Start designing your ER Diagram by finalizing the entities that must be included in your pharmacy management system. This entity is represented by a rectangle, and you’ll want to leave plenty of room for them in future phases so you may add them to your design.
An entity set is a group of similar entities with shared properties. A table or a table’s attribute is an entity in a database management system. As a result, by depicting relationships between tables and their characteristics, an ER diagram displays the whole logical structure of a database. - Step 3: Add the attributes of each entity
After finalizing the entities, think about the qualities you’ll need to characterize each entity. The details of the various entities outlined in a conceptual ER diagram are supplied as attributes. Characteristics of an entity, a many-to-many relationship, or a one-to-one relationship are all examples of attributes. Multivalued attributes can be assigned to several values.
The entity’s attributes were represented by ovals and can be seen in the tables of the pharmacy management system er diagram. These attributes can be a primary key or a foreign key in the database design of the project. Yoy ER diagram design could also be converted to the database of the system by declaring your right entities and their attributes. - Step 4: Describe the relationships (cardinality) between entities and attributes
To plot relationships between the ERD you will need the entities, their attributes, and relationships. You will base the data structure from the evaluated information to have the exact Entity Relationship Diagram.
A relationship is an association that describes how two entities interact. At the connector’s endpoints, the cardinality is indicated by a crow’s foot. One-to-one, one-to-many, and many-to-many are the three most common cardinal relationships. It’s the maximum number of times an instance of one entity can be linked to instances of another entity.
Conclusion:
ER (entity-relationship) diagram is only one of the diagrams used to design and develop the Pharmacy Management System. Each of the diagrams you design and create will help you in presenting your ideas and impart your abilities.
Creating the ER diagram will help you perceive the back end of the software which will hold all the data that’ll enter and exit the system. To learn more about the ER Diagrams and more, check out the related and recommended articles below.
Related Articles:
- Employee Management System ER Diagram
- Payroll Management System ER Diagram
- ER Diagram for Movie Ticket Booking System
- Car Rental System ER Diagram
- Railway Reservation System ER Diagram
Recommended Articles
Inquiries
If you have inquiries or suggestions about the Pharmacy Management System ER Diagram, just leave us your comments below. We would be glad to know to concerns and suggestions and be part of your learning.
Keep us updated and Good day!