This document describes a hospital management system that was designed to improve management of hospital operations. The system allows for registration of patients, storing patient details, computerized billing, and searching for patient and doctor availability. It aims to support decision making, administration, and financial accounting. The system was designed to be easy to use, flexible, and provide real benefits to hospitals. A feasibility study was conducted to analyze the economic, technical, and operational feasibility of replacing an existing paper-based system with the new management system.
This document describes a hospital management system that was designed to improve management of hospital operations. The system allows for registration of patients, storing patient details, computerized billing, and searching for patient and doctor availability. It aims to support decision making, administration, and financial accounting. The system was designed to be easy to use, flexible, and provide real benefits to hospitals. A feasibility study was conducted to analyze the economic, technical, and operational feasibility of replacing an existing paper-based system with the new management system.
This document describes a hospital management system that was designed to improve management of hospital operations. The system allows for registration of patients, storing patient details, computerized billing, and searching for patient and doctor availability. It aims to support decision making, administration, and financial accounting. The system was designed to be easy to use, flexible, and provide real benefits to hospitals. A feasibility study was conducted to analyze the economic, technical, and operational feasibility of replacing an existing paper-based system with the new management system.
Keywords: Hospital management system, data support effective decision making for structures, HTML, PHP patient care, hospital administration and critical financial accounting, in a seamless Abstract flow. Hospital Management System is a software product suite designed to 1.Introduction improve the quality and management of 1.1 Basic Introduction hospital management in the areas of clinical process The project Hospital Management system 1.3 Modules includes registration of patients, storing their details into the system, and also analysis and activity-based costing. Hospital ∙ computerized billing in the pharmacy, and Management System enables you to ∙ labs. The software has the facility to give develop your organization and improve its ∙ a unique id for every patient and stores the effectiveness and quality of work. details of every patient and the staff Managing the key processes efficiently is 2. automatically. It includes a search facility critical to the success of the hospital helps to know the current status of each room. you manage your processes 2.1 User can search availability of a doctor Hos and the details of a patient using the id. for The Hospital Management System can be 1.2 Problem Introduction the entered using a username and password. It crit is accessible either by an administrator or (a)Lack of immediate retrievals: - info receptionist. Only they can add data into The information is very difficult to retrieve num the database. The data can be retrieved spre easily. The interface is very user- and to find particular information like- E.g. man friendly.The data are well protected for - To find out about the patient’s history, the infr personal use and makes the data inco processing very fast. user has to go through various registers. man Hospital Management System is This results in inconvenience and wastage stan powerful, flexible, and easy to use and is of time. betw designed and developed to deliver real (b)Lack of immediate information com conceivable benefits to hospitals. storage: - that Hospital Management System is designed The information generated by various cop for multispecialty hospitals, to cover a transactions takes time and efforts to be hos wide range of hospital administration and data management processes. It is an stored at right place. stor integrated end-to-end Hospital (c)Lack of prompt updating: - Management System that provides Various changes to information like patient 2.2 relevant information across the hospital to details or immunization details of child are The difficult to make as paper work is involved. Three key considerations involved in the (d)Error prone manual calculation: - designed feasibility for any analysis hospital are:to replace their Manual calculations are error prone and existing 3.3.1 manual Economic paper based system. The Feasibility new system is to control the information take a lot of time this may result in incorrect of This study is carried out to check the patients. Doctor’s economic impactdetails, common will have on the system information. For example, calculation of will have on the organization. The amount diseases patient’s bill based on various treatments. andoftheir fundcauses that the andcompany symptoms.can These pour into the (e)Preparation of accurate and prompt services research are and to bedevelopment provided in ofanthe system is efficient, reports: - costlimited. effective The manner,expenditures with the goalmust of be justified. This becomes a difficult task as information reducing Thusand the time theresources developed system as currently well for is difficult to collect from various register. required within such the tasks.budget and this was ∙Appointment achieved because most of the technologies ∙Ambulance used are freely available. Only the ∙Addition of Doctor’s name customized products have to be ∙Diseases purchased. 3.3 Feasibility study 3.3.2 Technical Feasibility The feasibility of the project is analyzed in this phase and business proposal is put This study is carried out to check the forth with a very general plan for the technical feasibility, that is, the technical project and some cost estimates. During requirements of the system. Any system system analysis developed must not have a high demand on the available technical resources. This will lead to high demands being placed on the client. The developed system must have a modest requirement, as only minimal or null changes for the implementing this system.
3.3.3 Operational Feasibility
The aspect of study is to check the level of
acceptance of the system by the user. This includes the process of training the user to use the system efficiently. The user must not feel threatened by the system, instead must accept it as a necessity. The level of the feasibility study of the proposed acceptance by the users solely depends on system is to be carried out. This is to the methods that are employed to educate ensure that the proposed system is not a the user about the system and to make him burden to the company. For feasibility familiar with it. His level of confidence analysis, some understanding of the major must be raised so that he is also able to requirements for the system is essential. make some constructive criticism, which is welcomed, as he is the final user of the system.
3. Design Before we started writing the code for the program, we needed to have a clear idea of how to work through the problem set. So for that purpose, we decided to draw some diagrams.
functionality provided by a system in
terms of actors, their goals (represented as use cases), and any dependencies between those use cases. Fig1: Use Case diagram A Collaboration Diagram also called a A use case diagram in the is a type of communication diagram or interaction behavioral diagram defined by and created diagram, is an illustration of the from a use-case analysis. Its purpose is to relationships and interactions among present a graphical overview of the software objects. The concept is more than a decade old although it has been refined as modeling paradigms have evolved. Fig2: Collaboration Diagram desktop Client Printer
Hospital Local Server
Database Server
Fig3: Deployment Diagram
A Deployment Diagram shows the
configuration of run-time processing nodes and the components that live on them. Deployment diagrams address the static deployment view of architecture. They are related to component diagrams in that a node typically encloses one or more components.
The state diagram shows the states of an
object and represents activities as arrows connecting the states. The Activity Diagram highlights the activities. Each 5.1.2 Integration Testing activity is represented by a rounded Fig4: State Diagram rectangle- narrower and more oval- 4. System Implementation shapedthan the state icon. An arrow problem will take huge space, it has not represents the transition from the one been included in this report. activity to the next. The activity diagram has a starting point represented by filled- in circle, and an end point represented by 5. Testing bull’s eye. The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. It provides a way to check the functionality of components, sub- assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of ensuring that the Software system meets its requirements and user expectations and does not fail in an unacceptable manner. There are various types of test. Each test type addresses a specific testing requirement. 5.1 Types of Testing 5.1.1 Unit testing by successfully unit testing, the Unit testing involves the design of test combination of components is correct and cases that validate that the internal consistent. Integration testing is program logic is functioning properly, and specifically aimed at exposing the that program inputs produce valid outputs. problems that arise from the combination All decision branches and internal code of components. flow should be validated. It is the testing Before functional testing is complete, of individual software units of the additional tests are identified and the application. It is done effective value of current tests is a determined. fter the completion of an individual unit Implementation is the stage of the Test objectives project before integration. This is a ∙All field entries must work properly. structural when the theoretical design is turned out testing, that relies on ∙Pages must be activated from the identified knowledge of its into a working system. link. Thus it can be construction and is invasive. Unit tests considered to be the ∙The entry screen, messages and responses most critical stage in perform basic tests at must not be delayed. component level and achieving a 5.1.3Functional test successful new system and in test a specific business process, Functional test: application, giving the user, confidence Functional tests provide systematic that the new and/or system configuration. demonstrations that functions tested are Unit tests system will work and be available as specified by the business and effective. The ensure that each unique technical requirements, system documentation, and user manuals. path of a business implementation stage Functional testing is centered on the involves careful process performs following items: accurately to the planning, investigation Valid Input: identified classes of valid of the existing documented specifications input must be accepted. and contains Invalid Input: identified classes of invalid system and its constraints on clearly input must be rejected. defined inputs and expected results. implementation, designing of methods to Functions: identified functions must be exercised. achieve changeover and evaluation of Output: identified classes of application changeover methods. As the code of the outputs must be exercised. Integration tests are designed to test Systems/Procedures: interfacing systems integrated software components to or procedures must be invoked. determine if they actually run as one program. Testing is event driven and is Organization and preparation of more concerned with the basic outcome of functional tests is focused on screens or fields. Integration tests requirements, key functions, or special test demonstrate that although the components cases. In addition, systematic coverage were individually satisfaction, as shown pertaining to identify Business process flows; data fields, predefined processes, allotment for the admitted patients and the and successive processes must be stock details of medicines in the considered for testing. pharmacy. Providing such features enable Features to be tested the users to include more comments into the system ∙Verify that the entries are of the correct format Acknowledgements ∙No duplicate entries should be allowed It is indeed with a great pleasure and ∙All links should take the user to the correct immense sense of gratitude that we acknowledge the help DR Himanshu page. Chaudhary for giving us the opportunity to make this project. Test Results: ∙All the test cases mentioned above passed References successfully. No defects encountered. www.w3school.com www.tutorialpoint.com 6.Conclusions The Hospital Management System is a great improvement over the manual system using case fields and paper. The computerization of the system has sped up the process. In the current system, the front office managing is very slow. The hospital managing system was thoroughly checked and tested with dummy data and thus is found to be very reliable ADVANTAGES: ∙It is fast, efficient and reliable ∙Avoids data redundancy and inconsistency ∙Web-based ∙Number of personnel required is considerably less ∙Provides more security and integrity to data Future Enhancements: The proposed system is Hospital Management System. We can enhance this system by including more facilities like billing system, inpatient room