HEALTH CARE MANAGEMENT SYSTEM

Contents

1. INTRODUCTION
   1. Healthcare  Management System

• PROJECT PLAN
  • Feasibility study
    • Operation
    • Technical
    • Cost/Benefit Analysis
  • System Analysis
  • System Requirement
  • Data-Flow-Diagram
    • Context DFD
    • First Level DFD
    • Second Level DFD
  • System Design
  • Coding details / Application
  • System Testing

• WHY?
  • PHP
  • MY SQL SERVER

CONCLUSION AND FUTURE SCOPE

BIBLIOGRAPHY AND REFERENCES

Chapter 1

INTRODUCTION

Healthcare Management System

Introduction:

The main aim of the project is the management of the database of the pharmaceutical shop. This is done by creating a database of the available medicines in the shop. The database is then connected to the main program by using interconnection of the Visual Basic program and the database already created.

Application:

This program can be used in any pharmaceutical shops having a database to maintain. The software used can generate reports, as per the user’s requirements. The software can print invoices, bills, receipts etc. It can also maintain the record of supplies sent in by the supplier.

Chapter 2

PROJECT PLAN

2.1 Feasibility Study

A feasibility analysis involves a detailed assessment of the need, value and practicality of a proposed enterprise, such as systems development. The process of designing and implementing record keeping systems has significant accountability and resource implications for an organization. Feasibility analysis will help you make informed and transparent decisions at crucial points during the developmental process to determine whether it is operationally, economically and technically realistic to proceed with a particular course of action.

Most feasibility studies are distinguished for both users and analysts. First, the study often presupposes that when the feasibility document is being prepared, the analyst is in a position to evaluate solutions. Second, most studies tend to overlook the confusion inherent in system development – the constraints and the assumed attitudes.

2.1.1 Operational feasibility

People are inherently resistant to change, and computers have been known to facilitate change. An estimate should be made of how strong a reaction the user staff is likely to have toward the development of a computerized system. It is common knowledge that computer installations have something to do with turnover, transfers, retraining, and changes in employee job status. Therefore, it is understood that the introduction of a candidate system requires special effort to educate, sell and train the staff on new ways of conducting business.

2.1.2 Technical feasibility

Technical feasibility centers around the existing computer system (hardware, software, etc.) and to what extend it can support the proposed addition. For example, if the current computer is operating at 80 percent capacity – an arbitrary ceiling – then running another application could overload the system or require additional hardware. This involves financial considerations to accommodate technical enhancements. If the budget is a serious constraint, then the project is judged not feasible.

2.1.3 Cost/ Benefit analysis

Economic analysis is the most frequently used method for evaluating the effectiveness of a candidate system. More commonly known as cost benefit analysis, the procedure is to determine the benefits and savings that are expected from a candidate system and compare them with costs. If benefits over weigh costs, then the decision is made to design and implement the system. Otherwise, further justification or alterations in the proposed system will have to be made if it is to have a chance of being approved. This is an ongoing effort that improves in accuracy at each phase in the system life cycle.

payment