PATIENT MANAGEMENT SYSTEM

PATIENT MANAGEMENT SYSTEM

Abstract

     In a given day, number of patients visits a hospital or a clinic. Many hospitals in India still manage the patient data manually.

     Hospitals will be able to save money and time if they have a good software program for managing patient’s data.

     The idea is to develop web based patient management software that can be used to keep track of the patients registering in a hospital or clinic.

     Doctors and the rooms available in a hospital can be managed using this system.

      Also, this system should support accessing the previous visit histories of any patient, search for patients by name etc.

A few points to be noted about the system we are developing here

·        A patient can be categorized as “In patient” or “Out Patient”.  If patient type is "In Patient", a bed will be assigned to the patient.

·        A doctor will be assigned to each patient before the patient meets the doctor. Only one doctor can be assigned to a patient at a given time.

·        A patient can visit the hospital any number of times

The important roles associated with the system would be:

Administrator: Administrator will have complete control of the system. She/he cans Add/Edit/Delete patients, Add/Edit/Delete Doctors, Add/Edit/Delete Beds, Search for patients, Assign patients to doctors.

Doctor: Doctor can access a patient’s record and update his observations about the patient in that particular visit.

Reports: The following reports can be generated. You can implement more reports which you think can be useful.

·        Utilization of doctors

·        List of Patients diagnosed by a disease

·        List of patients who visited during a given time period

EXISTING SYSTEM:

Ø Cannot Upload and Download the latest updates.

Ø No use of Web Services and Removing.

Ø Risk of mismanagement and of data when the project is under development.

Ø Less Security.

Ø No proper coordination between different Applications and Users.

Ø Fewer Users - Friendly.

PROPOSED SYSTEM:

             

                    The development of the new system contains the following activities, which try to automate the entire process keeping in view of the database integration approach.

Ø User friendliness is provided in the application with various controls.

Ø The system makes the overall project management much easier and flexible.

Ø Readily upload the latest updates, allows user to download the alerts by clicking the URL.

Ø There is no risk of data mismanagement at any level while the project development is under process.

Ø It provides high level of security with different level of authentication.

MODULES:                                             

1.           Administration

2.           Employee

3.           Doctor

4.           Reports

5.           Authentication

FEATURES:    

         

                   Create a web based Patient Management System (PMS) for a hospital with the following features

·        Registration - This feature allows to add/edit/delete patients in the system.

·        Patient Management - Before we let a user to visit a doctor, we should classify whether he is an in-patient or an outpatient. Then basic symptoms should be captured and entered in the system.  Existing patients can be searched by name, admission date, patient ID etc.

·        Patient Visit History - Previous visit histories of the patient can be accessed

·        Assign Doctor - Assign a patient to a doctor based on the basic information of the patient’s problems. Based on the specialization and availability of the doctors, patients should be assigned.

·        Doctor Management – Add / Edit / Delete the doctors working in the hospital.

·        Bed/Room Management – The beds or rooms in a hospital can be managed. Add / Edit / Update the rooms with details. Check availability and assign a room to in-patients.

·        Doctors can update the patient’s record with their observations

 Keywords:

·        Generic Technology Keywords: Databases, User Interface, Programming

·        Specific Technology Keywords: ASP.Net, C#.Net, MS SQL Server

·        Project Type Keywords: Analysis, Design, Implementation, Testing

·        SDLC Keywords: Presentation, Business, Data Access Layers

Environment:

·        Servers:

·                    Operating System Server: - Microsoft Windows 2000 or Higher

·                    Data Base Server: Microsoft SQL Server 2000/2005

·        Clients: Microsoft Internet Explorer,

·        Tools: Microsoft Visual Studio .Net

·        User Interface: ASP.NET with AJAX

·        Code Behind: VC#.NET

 Requirements:

·  Hardware requirements:

Number	Description
1	PC with 2 GB hard-disk and 256 MB RAM

·  Software requirements:

Number	Description
1	Windows 2000/ XP/ or Higher with MS-office
2.	MS-SQL server2000/2005
3.	MS-Visual Studio .Net 2005
4.	MS-Internet Explorer

·  Manpower requirements:

3To 4 Developers can complete this in 3-4 months.

Milestones:

No.	Milestone Name	Milestone Description	Remarks
1	Requirements Specification	Complete specification of the system including defining hierarchies constitutes this milestone. A document detailing the same should be written and a presentation on that be made.	Attempt should be made to add some more relevant functionality other than those that are listed in this document.
2	Technology familiarization	Understanding of the technology needed to implement the project.	The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.
3	Database creation	A database of at least 10 entries of users with at least 1 should application admin.	It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself.
4	High-level and Detailed  Design	Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario.	The scenarios should map to the requirement specification
5	Development of front end functionalities.	Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options	During this milestone period, it would be a good idea for the team to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.
6	Integrating the front-end with the database	The front-end developed in the earlier milestone will now be able to update the database. Other features should be functional at this stage. In short, the system should be ready for integration testing.
7	Integration Testing	The system should be thoroughly tested by running all the test cases written for the system (from milestone 5).	Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.
8	Final Review	Issues found during the previous milestone are fixed and the system is ready for the final review.	During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled

The following steps will be helpful to start off the project:

·        Study and be comfortable with technologies such as: ASP.Net with C#, and SQL Server.

·        Gather some knowledge of product hierarchies and maintenance before starting the design.

·        Create a user database with different access levels.

·        Start with creating the login screen.

·        Create menus for navigation and group the functionalities as sub menus.

·        Create the help-pages of the application in the form of FAQ. This will helps user.