Hospital Management: Difference between revisions

From CS486wiki
Jump to navigationJump to search
Content deleted Content added
No edit summary   (change visibility)
No edit summary   (change visibility)
 
(21 intermediate revisions by the same user not shown)
Line 35: Line 35:
'''1. Administrator Level'''
'''1. Administrator Level'''


-Can change everyone’s user details
- Can change everyone’s user details


-Add new doctor
- Add new doctor


-Can see list of Patients
- Can see list of Patients


-Can see list of Doctors
- Can see list of Doctors


-Manage hospital rooms
- Manage hospital rooms


-Can see billing of every patient
- Can see billing of every patient


-Manage insurance methods (Top Private Hospital Cover, Medium Private Hospital Cover, Basic Private Hospital Cover, Public Hospital Cover)
- Manage insurance methods (Top Private Hospital Cover, Medium Private Hospital Cover, Basic Private Hospital Cover, Public Hospital Cover)
'''2. Patient Level'''
'''2. Patient Level'''


-Can change own user details
- Can change own user details


-Make appointment from available doctors
- Make appointment from available doctors


-See result of diagnose
- See result of diagnose


-Can pay bill of treatment
- Can pay bill of treatment


'''3. Doctor Level'''
'''3. Doctor Level'''


-Can change own user details
- Can change own user details


-Confim appointments
- Confim appointments


-Can write Diagnose and Cure to patient
- Can write Diagnose and Cure to patient


-Can admit or discharge patient from room
- Can admit or discharge patient from room


-Every doctor has qualifacition
- Every doctor has qualifacition


'''4. Login Page'''
'''4. Login Page'''


-Login
- Login


-New patient registeration
- New patient registeration


'''5. About Us'''
'''5. About Us'''


'''6.Contact Us'''
'''6. Contact Us'''


== '''Schedule of Progress''' ==

'''02.06.2015 - 02.20.2015'''

We have finalized Master Page to define common structure and interface markup elements for the Hospital Management Web site.
The interface of the modules has been completed. Required CSS implementations are done. Our login page is shown below;

[[File:1.PNG]]

'''02.20.2015 - 03.06.2015'''

We created database of the project. Each user will be logging in according to their level. These levels can been seen below in the Data Base Diagram.

[[File:EntityDesigner.jpg]]

The table hosUser keeps the register information; it holds attributes such as ID, Username, Password, Online, Lastseen. Online states if the user is online or not. Lastseen shows the last date that user logged in. ID is the private key.

The table hosPatietnt stands for patient information; it holds attributes such as ID, UserID, Name, Surname, Age, e-mail, Phone, InsuranceID. InsuranceID shows what kind of insurance the patient has.

The table hosDoctor stands for doctor information; it holds attributes such as ID, UserID, Name, Surname, Age, e-mail, Phone.

The table hosComplaint keeps the information of the patient’s complaint. It has attributes such as ID, PatientID, DoctorID, Title, Text and Status. Title and Text will be filled by the patient. Status will be changed once the doctor accepts the patients request and the patient claims the examination.

The table hosBooking keeps the information for the occupied rooms. Attributes are; ID, ComplaintID, RoomID, StartDate, EndDate and Status. Dates will show for how long the room will be occupied. Status will show if the room is available or not.

The table hosRoom keeps the information of the rooms such as number and status.

The table hosExamination keeps the information of the examinations such as; names, fee and needed rooms.

The table hosComplaintExamination keeps all the information about examination of patient. Attributes are ID, ComplaintID, ExaminationID, Date and Status.

The table hosPrescription keeps the information of the results of the patient’s examination. MedicationID holds the medication that needed. Comment will show how the medicine should be used.

The table hosMedication keeps the medication names such as; vitamin, aspirin etc.

The table hosDiagnosis keeps the diagnosis information according to examination results of patient.

The table hosDisease keeps the names of the diseases such as; flu, cancer etc.

The table hosTransaction keeps the billing information of the patient.


'''03.06.2015 - 03.27.2015'''

We have created functions for each controller pages such as; AdminController.cs, DoctorController.cs, HomeController.cs, PatientController.cs. By using these pages we manage processes of the whole program such as; transaction, booking, adding complaints/diagnoses, creating users, editing/saving information.

We have also designed pages for patients, doctors and admin. These pages will be directed once the user logged in. Designes of the pages can be seen below;

[[File:user.PNG]]

[[File:Examinations.PNG]]

'''03.27.2015 - 04.10.2015'''

We made the last adjustments on the project. We fixed some transition problems between web pages. Also we upgraded our design with a new template. We cleared up some defective buttons and made them runnable.


== '''Team Members''' ==

Team Members from left to right: '''Emre Aksu''', '''Alper Ekrem Yildirim'''

[[File:IMG_0903.JPG]]

Latest revision as of 14:34, 17 April 2015

Introduction

Some hospitals currently use a manual system for the management and maintenance of critical information. That system requires numerous paper forms, with data stores spread throughout the hospital management structure. Generally, information on forms is incomplete, or does not follow management standards. Forms are often lost in transit between departments requiring a comprehensive auditing process to ensure that no vital information is lost. Multiple copies of the same information exist in the hospital and may lead to inconsistencies in data in various data stores.

A significant part of the operation of any hospital involves the acquisition, management and timely retrieval of great volumes of information. This information typically involves; patient personal information and medical history, staff information, scheduling, staff scheduling, operating theater scheduling and various facilities waiting lists. All of this information must be managed in an efficient and cost wise fashion so that an institution's resources may be effectively utilized Hospital Management System will automate the management of the hospital making it more efficient and error free. It aims at standardizing data, consolidating data ensuring data integrity and reducing inconsistencies.

Hospital Management System is based on the database, object oriented and networking techniques. As there are many areas where most of the hospitals around the World keep the records in database such as SQL software which is one of the best and the easiest software to keep information and they are using C# as a programming language.

Hospital Management System is custom built to meet the specific requirement of the medium and large size hospitals across the globe. Many hospitals have lots of modules and features so I decided to add most important modules and features to project. Project covers all the required modules right from Patient Registration, Doctor Registration, Medicine details, Admin, Patient appointment, Record modification, Billing, Room occupation etc.


Required Technologies

-HTML5

-CSS3

-JavaScript

-C#

-SQL

-Visual Studio 2013


Modules and Features of Project

Our project consists of three levels of users which are Administrator level, Patient level and Doctor Level. At the Admininstrator level, person can add or delete patients, add or delete doctors, see everyone reports and appointments, change everyone user details. At the Patient level, person’s authority is restricted. Person just can change his/her own user details, make appointments from suitable doctors and see his/her old reports and new reports and can also set payment method. At the Doctor level, person can change his/her own user details, see requested appointments from patients and confirm/decline the requests, after that process doctor can diagnose and cure to patient and can conclude that request. If its needed, doctor can reserve room for the patients.

Project’s Module and Features are like at the below;

1. Administrator Level

- Can change everyone’s user details

- Add new doctor

- Can see list of Patients

- Can see list of Doctors

- Manage hospital rooms

- Can see billing of every patient

- Manage insurance methods (Top Private Hospital Cover, Medium Private Hospital Cover, Basic Private Hospital Cover, Public Hospital Cover)

2. Patient Level

- Can change own user details

- Make appointment from available doctors

- See result of diagnose

- Can pay bill of treatment

3. Doctor Level

- Can change own user details

- Confim appointments

- Can write Diagnose and Cure to patient

- Can admit or discharge patient from room

- Every doctor has qualifacition

4. Login Page

- Login

- New patient registeration

5. About Us

6. Contact Us


Schedule of Progress

02.06.2015 - 02.20.2015

We have finalized Master Page to define common structure and interface markup elements for the Hospital Management Web site. The interface of the modules has been completed. Required CSS implementations are done. Our login page is shown below;

02.20.2015 - 03.06.2015

We created database of the project. Each user will be logging in according to their level. These levels can been seen below in the Data Base Diagram.

The table hosUser keeps the register information; it holds attributes such as ID, Username, Password, Online, Lastseen. Online states if the user is online or not. Lastseen shows the last date that user logged in. ID is the private key.

The table hosPatietnt stands for patient information; it holds attributes such as ID, UserID, Name, Surname, Age, e-mail, Phone, InsuranceID. InsuranceID shows what kind of insurance the patient has.

The table hosDoctor stands for doctor information; it holds attributes such as ID, UserID, Name, Surname, Age, e-mail, Phone.

The table hosComplaint keeps the information of the patient’s complaint. It has attributes such as ID, PatientID, DoctorID, Title, Text and Status. Title and Text will be filled by the patient. Status will be changed once the doctor accepts the patients request and the patient claims the examination.

The table hosBooking keeps the information for the occupied rooms. Attributes are; ID, ComplaintID, RoomID, StartDate, EndDate and Status. Dates will show for how long the room will be occupied. Status will show if the room is available or not.

The table hosRoom keeps the information of the rooms such as number and status.

The table hosExamination keeps the information of the examinations such as; names, fee and needed rooms.

The table hosComplaintExamination keeps all the information about examination of patient. Attributes are ID, ComplaintID, ExaminationID, Date and Status.

The table hosPrescription keeps the information of the results of the patient’s examination. MedicationID holds the medication that needed. Comment will show how the medicine should be used.

The table hosMedication keeps the medication names such as; vitamin, aspirin etc.

The table hosDiagnosis keeps the diagnosis information according to examination results of patient.

The table hosDisease keeps the names of the diseases such as; flu, cancer etc.

The table hosTransaction keeps the billing information of the patient.


03.06.2015 - 03.27.2015

We have created functions for each controller pages such as; AdminController.cs, DoctorController.cs, HomeController.cs, PatientController.cs. By using these pages we manage processes of the whole program such as; transaction, booking, adding complaints/diagnoses, creating users, editing/saving information.

We have also designed pages for patients, doctors and admin. These pages will be directed once the user logged in. Designes of the pages can be seen below;

03.27.2015 - 04.10.2015

We made the last adjustments on the project. We fixed some transition problems between web pages. Also we upgraded our design with a new template. We cleared up some defective buttons and made them runnable.


Team Members

Team Members from left to right: Emre Aksu, Alper Ekrem Yildirim