INTRODUCTION OF MEDICINE INVENTORY MANAGEMENT SYSTEM

Are you looking for Medicine inventory management system for your final year project? We are here to help you. You can contact us

Everyone in this world, somewhere in the world and in time one has to face some kind of disease or injuries. The disease to cure we need some doctor to concern. As we go to the doctor he analyzes the problem with us and tell us the reason of problem and prescribe us some sort of medicines.

These medicines are available in medical stores. one needs a prescription to the store which the staff takes care and use that to see which medicines they need according to the name given to the medicine.

now, this becomes a bit tedious to locate the particular medicine. Now here come up with such a system which capable of recording that from where the medicines need to take out according to the name, brand, price in the racks, which are marked with the no . of them. Here the system helps the staff to manage the medicines in the racks and also useful in reinstalling the stock in the racks and easy to find.

Here system gives total according to the quantity of the medicines individually and from the order, they get the invoice of the medicines.

The prescription is taken care with great care as one needs to take care that few medicines are sophisticated to make it available to customers. Hence a useful system is capable of working and managing the medicines in a store.

MODULES OF MEDICINE INVENTORY MANAGEMENT SYSTEM

The system is made of the combination of modules which work with collaboration with each other and make it beneficial to accomplish the main aim of the system.

Order:

Here we have this interface for the user . in this he gets all his selected medicines and he can make orders accordingly after uploading the prescription of that from any renowned doctor.

Prescription Uploading

One can upload the prescription of the medicines after getting it from the doctor’s checkup. doctors write a needed prescription which they can cure the disease .this user needs to upload in the interface to get the approval of the order.

Payment:

The payment can be done by the user through the by their debit card in the account of the owner of the medicos they will get options for that in an integrated environment of the payments.

Medicines:

The medicines are kept in proper place so that they can be taken out fast as soon as they get the order. It helps the staff to search it from the interface that where it is located and where they will find it

Registration:

Users information have to be compelled to be registered within the system thus on establish every of them unambiguously and do the required group action as simple potential .like on the name of the bill are issued.

on the far side, this plenty of things require measure there wherever we will reference him. Without registration, there are few options and pages one user can see which are landing on the home page and taking the features read but he won’t be allowed to use those.

For use, he will have to register. One person needs to put his all the details properly and precisely as it will be helpful in identifying them and believing that he is the real person who has booked for the same.

It also includes driver license for them who is driving and parameter too.

Login:

After registration one will log within the system because the operator of the system either on the behalf of user. when this he has the opposite helpful interfaces accessible for any actions.

Here either bride or groom both have to log in with their unique identity and passwords. After this, they will be directed to the main user interface from where they have further options.

Forgot password:

This is quite often that people tend to forget the password they keep for the login. So this could be very tedious and hectic to recover the password manually in case if one needs to login in the emergency.

So to overcome this problem we have this module named ass forgot the password and using this module user can recover their password in seconds. So here we need to only put our registered email Id and hit the enter.

than one confirmation email will go to the email where he has the option to reset the password. In seconds one can use this module and get rid of forgetting password problem.

Admin:

Admin has the official powers to control the flow of the data from one part of the system to the other. He has the power to manipulate the access of the users to the data.

The main purpose of this account is to make the user data relevant and then giving the inputs to the other interface module and make it work optimistically and get the timetable according to the wish we want to create for a particular type of inputs.

Hence all the data will be reflected with clean and well data in the interfaces.

SYSTEM REQUIREMENT OF MEDICINE INVENTORY MANAGEMENT SYSTEM

Now, this method is intended in such the way that it takes fewer resources to figure out work properly. it’s its own type of minimum needs that we’d like to require care of :

The system wants a minimum of two GB of ram to run all the options sleek and unforeseen.

It wants a minimum 1.3 gigahertz processor to run sleek as else which will produce issues.

The system must be operated by some approved person as wrong hands will build it happy-go-lucky.

Rest is all up to the user’s usage can take care of hardware

For security opposing anti-virus is suggested.

The system is made properly and all the testing is done as per the requirements. So, the rest of the things depend on the user and no one can harm the data or the software if the proper care is done.

All the attributes are working perfectly and if any error is found then it can be removed easily.

SYSTEM DESIGN OF MEDICINE INVENTORY MANAGEMENT SYSTEM

 

SYSTEM DESIGN OF MEDICINE INVENTORY MANAGEMENT SYSTEM

 

Entity Order:

Primary Key Order_id:

This is system generated and unique, which can be referenced in any other entity.

Foreign Key Medicine_id:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

No of medicines:

The no of the user needs to buy is here

Quantity:

the quantity per medicine is here

Price per medicine:

Price per medicine according to the quantity is given here

Discount:

If any discount they are offering is eligible is counted here

Tax:

The taxes are added here

Grand Total:

the total of the medicines is given here.

Entity Medicine:

Primary Key Medicine_id:

This is system generated and unique, which can be referenced in any other entity.

Name:

The name of the medicine is given here

Manufacture date:

The date at which it was manufactured.

Expiry date:

The date at which it will get expired.

M r p:

The market price is printed here.

Formula content:

The content of the medicine which is comprised of is given here.

Used for:

For what purpose the medicine is given for.

Dosage:

No of dosage per day was given is noted down here.

Entity Prescription:

Primary Key Prescription_id:

This is system generated and unique, which can be referenced in any other entity.

Foreign Key User_id:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

Medicines:

Medicines are noted down here more than one is here.

Disease:

The disease for which the medicine is prescribed is given here with reason

Doctor name:

who issued the prescription the doctor name will come here.

Doctor qualification:

The doctor’s degree of education is here written.

Foreign Key Pic_id:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

Entity Pic:

Primary Key Pic_id:

This is system generated and unique, which can be referenced in any other entity.

Name:

Name of the pic

Length:

length of the pic

Width:

The width of the pic

Size:

Size in m b is given here

Doctor name:

name of the doctor is given here.

Foreign Key User_id:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

Entity Payment:

Primary Key Payment_id:

This is system generated and unique, which can be referenced in any other entity.

User_id:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

Prescription_id_id:

This is reference key from the other entity to link the data of that table.It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

Status:

Is the payment is done or not is given here.

Entity Staff:

Primary KeyStaff_id:

This is system generated and unique, which can be referenced in any other entity.

Staff name:

Staff name is taken from the user and fed into this it is properly validated so that no mistake happens.

Qualification:

qualification is taken as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

Number:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

Email:

email is taken to make member aware of new offers new events and for future reference, it is also relevant.

Type:

the type of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

Address:

The location of the user is also mentioned here to make it easy to the delivery and few other things too.

EntityUser:-

User data have to be saved in this entity and all fields are required for this purpose which taken from the user .proper validation is checked and the attributes are as follows:

Primary KeyUser_id:

This is system generated and unique, which can be referenced in any other entity.

Username:

Username is taken from the user and fed into this it is properly validated so that no mistake happens.

Qualification:

qualification is taken as to filter the events according to this so that user does not need to filter out the events to register it makes this system more reliable and useful.

Number:

The phone number is taken here to keep the member updated and for the confirmation of the event is also managed through this method.

Email:

email is taken to make member aware of new offers new events and for future reference, it is also relevant.

Type:

the type of user is mentioned here like is he a student, teacher or he is the vendor of any shop. According to this data, the discounts offers and other things are decided plus few other things of adjusting the task of the user also with this.

Address:

The location of the user is also mentioned here to make it easy to the delivery and few other things too.

Entity Admin:

Primary key admin:

This is the main supervisor of all task happening in the system for long. It is system generated unique identity number. This used to uniquely identify every table in the database and perform the crud operation on it.

It is used to reference that table to any other table or any interface to show the data of it and support other entities. It has all the power to make changes in the field of other tables. I grant the privileges to other users of the system that what kind of operations they can perform.

Logs:

The logs are saved here to analyze the system accordingly. The changes occur. For necessary changes.

Password:

A Strong password is recommended for this account as no one wants to get hacked and lose the sophisticated data.

Description:

Any important info. Regarding this account is attributed in this.

USE CASE DIAGRAM OF MEDICINE INVENTORY MANAGEMENT SYSTEM:

USE CASE DIAGRAM OF MEDICINE INVENTORY MANAGEMENT SYSTEM

This system has mainly three actors. first is user takes the prescription from the doctor upload the pic of that and staff brings out the medicine from the particular area and calculate the bill accordingly and give to the user.

Admin assigns the staff at the medicos and manages them accordingly.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF MEDICINE INVENTORY MANAGEMENT SYSTEM

Functional requirements of medicine inventory management system:-

The functional requirements are those requirements which are necessary to the eye of the user and the client. Here we try to make the module possible to accomplish the need of the desired function. few of its functional requirements are as follows-

Non-Functional requirements of medicine inventory management system:-

These requirements needs unit among the style of “system shall be “, associated overall property of the system as a full or of a particular aspect and not a particular operation.

The system’s overall properties remarkably mark the excellence between whether or not the event project has succeeded or unsuccessful.

Non-functional of the medicine inventory management system needs –

unit of measurement usually divided into 2 main categories:

Execution qualities, like security and quality, that unit evident at the runtime.

Evolution qualities, like liabilities, maintainability, flexibility and quantitative, that unit embodied among the static structure of the code.

Non-functional  of the medicine inventory management system needs place restrictions on the merchandise being developed, the event technique, and specify external constraints that the merchandise has to be compelled to meet

Our project qualifies all the factors of helpful and non-helpful consequently and the system is up to mark performance device.Here we’d prefer to need the care of few lots of things before heading towards the system.

the many sensible intuitive interfaces are usually created. that ultimately build interface easy to use for a lengthy time. in distinction to ancient vogue wherever the goal is to create the difficulty or application physically enticing, the goal of interface vogue is to create the user’s interaction expertise as simple and intuitive as double – what’s typically mentioned as user-centred vogue.

where smart graphic/industrial vogue is daring and eye-catching, smart interface vogue is sometimes delicate and invisible.

Keep things simple and consistent:-

Simple and Harmonic means that making u i is extraordinarily intuitive and needs to followed

observe the use of typography:-

The typography is taken care really strictly as the wish of the system.

Use colour and distinction properly:-

Color band of skin and dark is sweet means that stress and done well throughout this method

Consider feedback messages:-

feedback sort may well be an excellent means that taking feedback of forms and rising the system.

Simplified forms:-

The form is made simple to fill with a clean program.

MEDICINE INVENTORY MANAGEMENT SYSTEM PROJECT DOCUMENT

CONCLUSION OF MEDICINE INVENTORY MANAGEMENT SYSTEM

Finally, in the medicine inventory management system, we have a system where the user takes the prescription from the doctor upload the pic of that and staff brings out the medicine from the particular area and calculate the bill accordingly and give to the user. Admin assigns the staff at the medicos and manages them accordingly.