Hospital's Registration and Billing Management System

Submitted ByMr. Aashish RaiRoll no. : 8603

T.U. Reg. No. :

A Project Report Submitted ToMr. Nagendra Dangal

Nepal Commerce CampusTribhuwan University

In partial fulfillment of requirements for the course onDatabase Management System

For completion of 4th Semester, Bachelor's in Business Administration

KathmanduJuly 24, 2013

Acknowledgement

At the beginning, I like to ensure a hearty thanks to my mentor Mr. Nagendra Dangal, for equipping me with all the necessary concepts and tools to wrap up this project in such a beautiful report. Sincere thanks to OM Hospital and Research Center's unkown staff who listened and quenced my queries. Similarly, to the pharmacy of Shivatara Hospital, Mahalaxmisthan, I am indebted towards you. And finally, to the Tribhuwan Universtiy Teaching Hospital, where I realized how the database management system is implemented and it's necessity and helpfulness in real scenario where thousands of data are maintained each day.

Aashish Rai4th Semester, BBA

Nepal Commerce Campus

Table of Contents:

Content heads Page No.:

Acknowledgement I

Introduction 1

Relational schema 2

E-R Diagram 3

Schema Diagram 4

DDL Statements 5

Applicability options 8

Conclusion 9

Introduction:

With some facts and researches, the project “Hospital's Registration and Billing Management System” is an integrated management system that helps to record the patient’s expenses on different heads from three different expense points, namely pharmacy, cafeteria and tests, of a hospital. It is not in use in real time as a whole, but different parts of this system comprise the current practices in three existing Hospitals; OM Hospital, Chabahil, Teaching Hospital, Maharajgunj, and Shivatara Hospital, Mahalaxmisthan. This project tired to combine the bills of a patient in a single database, such that the necessary data can be easily accessed from the database.

The Database consists of 7 tables; employee, patient, doctor, check, pharmacy, cafeteria and tests. The table ‘employe’ consists of the information regarding the employee who had registered the patient. ‘patient’ consists of the basic data about the patient. ‘doctor’ consists of the information about doctor. ‘check’ consists information on which doctor checked which patient on which date. ‘pharmacy’ consists of data about the pharmaceuticals purchased on patient’s account. ‘cafeteria’ consists of data about the orders of food and drinks made on patient’s account. And finally, ‘tests’ table records the data about the test hired by the patient. In this way the entire billing system is integrated within a single database.

The database is practically applicable in the real time for hospitals which are likely to implement an integrated account of patient’s expenses within a single account.

Relational Schema:

employee(empID, empName, counterNo)

patient(patientNo, patientName, age, sex, address, deposite, regDate, disDate, remarks, empID)

doctor(docID, docName, address, contact, faculty)

check(patientNo, docID, checkdate, fee, remarks)

pharmacy(patientNo, buydate, particulars, rate, qty, amount)

cafeteria(patientNo, orderdate, particulars, rate, qty, amount)

test(patientNo, testdate, testhead, amount, remarks)

E-R Diagram:

doctor

docID

patient

docName

address

contact

faculty

check

employeeempID

counterNoempName

register

patientNo

patientName

deposite

age

checkdate

sex

remarks

address

fee

disDate

testheadremarks

regDate

test

remarks

amounttestdate

pharmacy

cafeteria

takes

buys

orders

qty

particulars

rate

amountbuydate

amount

qty

orderdate

rate

particulars

Schema Diagram:

empIDempNamecounterNo

empIDpatientNameagesexaddressdepositeregDatedisDateremarkspatientNo

docIDcheckdatefeeremarkspatientNo

docIDdocNameaddresscontactfaculty

patientNobuydateparticularsrateqtyamountpatientNo

orderdateparticularsrateqtyamount

patientNotestdatetestheadamountremarks

employee patient

pharmacy

test

check

cafeteria

doctor

DDL Statements:

For table "employee"

CREATE TABLE employee(empID int NOT NULL,empName varchar(100) NOT NULL,counterNo int NOT NULL,constraint pk_empID PRIMARY KEY (empID))

For table "patient"

CREATE TABLE patient(patientNo int NOT NULL,PatientName varchar(100) NOT NULL,age int,sex char,address varchar(100),deposite currency NOT NULL,regDate date,disDate date,remarks text,empID int NOT NULL,CONSTRAINT pk_patientNo PRIMARY KEY (patientNo),CONSTRAINT fk_empID FOREIGN KEY (empID) REFERENCES employee (empID))

For table "doctor"

CREATE TABLE doctor(docID int NOT NULL,docName varchar(100) NOT NULL,address varchar(100),contact varchar(30),faculty varchar(100),CONSTRAINT pk_docID PRIMARY KEY (docID))

For table "check"

CREATE TABLE check(docID int NOT NULL,patientNo int NOT NULL,checkDate date,fee currency,remarks text,CONSTRAINT fk_docID FOREIGN KEY (docID) REFERENCES doctor (docID),CONSTRAINT fk1_patientNo FOREIGN KEY (patientNo) REFERENCES patient (patientNO))

For table "pharmacy"

CREATE TABLE pharmacy(patientNo int NOT NULL ,buydate date NOT NULL,particulars varchar(100),rate currency,qty int,

amount currency,CONSTRATIN ph_patientNo FOREIGN KEY (patientNo) REFERENCES patient (patientNo))

For table "cafeteria"

CREATE TABLE cafeteria(patientNo int NOT NULL,orderdate date NOT NULL,particulars varchar(100),rate currency,qty int,amount currency,CONSTRAINT caf_patientNo FOREIGN KEY (patientNo) REFERENCES patient (patientNo),)

For table "test"

CREATE TABLE test(patientNo int NOT NULL,testdate date,testhead varchar(100),amount currency,remarks text,CONSTRATIN test_patientNo FOREIGN KEY (patientNo) REFERENCES patient (patientNo))

Applicability Options:The database can help in generating following information:

1. Patient's general information and medical history;2. Patient's stay time on hospital and deposit;3. Information on doctor's general information;4. Doctor's prescriptions and remarks on patient's health;5. Food habits of patient;6. Information on patient's total expenses for collective billing;7. Information on tests carried upon patient and medicines purchased on his

behalf.

Conclusion:The project is focused towards creating an integrated billing system for hospital's patient. It is partially used in different hospitals right at now, but the combined / integrating database system has not be fully developed. It is not imaginary project and holds real value if developed sincerely. In our country where database system is at it's infant phase, projects as such is a good sign of striving to move forward. The use of database at hospitals, especially in the government hospitals will surely make it more efficient and minimizes the errors that occur from traditional papering system. It is also a research tool for researchers, and it also helps to identify the subtle health epidemics.