Pharm.D is known as Doctor of pharmacy among all medicine universities. The pharmacy information system name and logo was inspired from this idea to simulate the database manegement system as Builder of Pharmacy as shown:
Pharmacy management software, — Pharm.B (Pharmacy Builder) — is to store important information about medications and patients in a much simpler way to ensure that the right prescriptions are given out at the right dosage. Furthermore, this new system is meant to be a multi-functional system that allows pharmacists to store the patient’s information and perpetuate the supply and organization of drugs. The system stores the patient’s information to perceive the allergies of the patient and guarantees that no patient would be prescribed a medication that would cause them to suffer from an allergic reaction. Moreover, the system will be very secure, up-to-date, and accurate, this is in order to decrease medication errors, increase patient safety, report drug usage, and track costs. The team members plan on implementing all this by adding inventory tracking, prescription filling and processing (taking all the necessary steps that should be taken to evaluate a prescription, verify its medical importance, benefits or side effects), and point of sale to the system. These three functions are the primary functions of any pharmacy information system; however, we developed some enhancements to it, making pharmacists’ and patients’ life much simpler, faster, and safer. Additionally, we are planning on adding a new feature to our system. Eventually, the development platform is utterly formal and organized. It will be structured by HTML, CSS, JavaScript and Tkinter.
This Software Requirement Specification (SRS) is intended for the pharmacy doctors ‘the admin of the system’ and pharmacists ‘the users’. This version of SRS covers the interface of release one of the Pharm-B (Builder of Pharmacy) system, which occurred at week 6 of the design process.
The system had UML (unified machine language) designs to simplfy the stalkholders' desire — the pharmacist and doctors — of each requirement they need.
The system architecture discusses the developed system’s modules and the underlying functions within each. The system is divided into 4 main modules: Information display module, Add product module, Search module, Payment module.
The " Information display module " carries out the functions necessary to display important information about the desired product Including some of the vital data such as the reference number to check its availability, the lot number to track any faulty drug patches in the pharmacy and other important details such as the issue date, expiry date and the usage details, in order to enhance the pharmacist/patient relation and help pharmacist know the patient's needs better and give the patient the best service. Medicine information:
- Medicine name
- Reference number: the medicine's code on the system in order to be found/handled throughout the process to check for its availability and quantity
- Company name: It is vital to keep record of the company name from whom the pharmacy buys the drugs/who is responsible for those drugs
- Type of medicine: Specifies the form in which the medicine comes in (Liquid, Tablet or Capsules)
- Lot number: the patch in which the drug came in to the pharmacy
- Issue date: For it's a must for the pharmacy to record the day the drug is added to the pharmacy
- Expiry date: The expiry date is a crucial information for the pharmacist and the patient
- Uses: It shows the pharmacist the health problems for which the medicine is mainly used for
- side effects
- Precautions and warnings: Important precautions related to the dosage/ allergies etc
- Dosage: For the pharmacist to give the right dosage of the drug to the patient
- Price
- Quantity
The " Adding new product module” is mainly responsible for adding the newly coming drug " quantity-wise " with referral to the reference number and lot number to specify the needed product, functions such as: Add, Update, Clear and Delete are included in the module. whereas:
- Add: Enters a newly arriving product to the system’s dataset..
- Update: Updates the name, lot, and referral numbers of the products in the system for a pre-existing product.
- Clear: Clear the entered data from the boxes whiteout adding.
- Delete: Delete an existing product.
This module is mainly responsible for handling the search process of drugs with multiple options to facilitate finding the required drug with reference to the expiry date for example. It also helps with adding and removing information about the drugs. The most important functions used are:
- Search: It searches for an entered drug name, referral number, or according to an option(s) selected from the “Search Options” function.
- Search Options: It is used to find the needed drug through filtration process such as the expiry date, the company’s name, the lot number...etc.
- Add Medicine: It allows the pharmacist to add a medicine to the system along with adding some required data about the drug in order to properly add it to the system.
- Delete: It deletes a selected drug from the dataset.
- Update: It updates the information of a specified drug on the dataset.
- Show All: It shows the whole dataset for preview.
- Exit: It exits the search process.
The patient has one method to pay with "cash”.
It divides the systems into sub modules as previously mentioned. It involves two parts: theoritical part and diagram attached with a table as shown.
The aim of the activity diagram is to explain all the activities of the whole system. Activity means any function provided by the system shuch as (Add- Delete- Pay - Update - Search ...).
The main idea of use cases is to simplify the connection between the useres and programmers regarding what the customer needs and what the programer should implement in the system. It has include and extend relations to know the exceptions and handling the errors.
The class diagram is so important in categorizing the system parts in an organized way. This helps to minimize the lines of codes by inheritance between the parent classes and child classes. For instance, instead of repeating a block of code for admin (doctor) and users(pharmacists) with a slight difference between both of them, we can make a parent class the has the abstraction of the main functions and extract two child classes from it. This is the main concept of OOP(Object Oriented Programming)
Class diagram based on interaction diagrams (sequence diagram and collaboration — communication — diagram)
There is a difference between the class diagram based on interaction diagrams and class diagram based on activity diagram and use cases. The one that based on the interaction diagram is more organized, specific after finishing a large part of technical coding journey and summarized.
the object diagram demonstrates the interactions between the objects.
The state machine diagram explains well every state in the system. The state has Do aspect which is the action done by the system user and a rounded rectangle to show the result of this action. The images below shows the state machine diagrams of the main parts of the system.
The package diagram clarifies the interactions between the classes and connections. Each class diagram is included into the package diagram with its methods and attributes in a hidden way.
The deployment diagram shows the hardware parts of the system in details.
The database was collected manually with credits was earned by Dr. Ahmed yahia pharmacy in Borg Al-Arab City, Egypt.
It shows the primary key which is reference number and secondary key which is the medicine name. It is required for any system whether it has a website interface or not. The primary key is the reference number because it is unique for each medicine and has no repeatitions.
