DATABASE MANAGEMENT

SYSTEMS

SUBMITTED TO

MAL GARBA MUHAMMAD

SUBMITTED BY

SN ADMISSION NUMBER

1 2010308084

2 2120308023

3 1910308015

4 1910308035

5 1910308060

6 1910308085

7 1910308111

8 1910308132

9 2010308021

10 2010308043

11 2010308066

12 2010308102

13 2010308124

14 1810308053
 INTRODUCTION TO NASIHA HOSPITAL

Over the past decade, NMCH&RC has established itself as a centre of

excellence providing comprehensive care free of cost to thousands of indigent

cancer patients. This pioneering, state-of-the-art hospital located in the heart of

the Gusau was founded by a councellor , one of Gusau’s most illustrious

advocator. As a charitable institute, it is funded predominantly from the

donations of friends and well-wishers from around the country and across the

world. The inspiration to build the Hospital came from the misfortune and

suffering of one individual, Anas Muhammad, the son of legendary captain of

zamfara’s club team, Muhammad bashir. His son's death and the personal

experience of dealing with cancer in a loved one convinced him of the need for

a state of the art cancer center with access to everyone, including those who

could not otherwise afford the expensive care. The result was the Nasiha

Memorial Cancer Hospital and Research Centre, in Gusau, the first and only

cancer hospital of international standards in Zamfara, dedicated to providing

first class treatment of cancer to all its patients, irrespective of their ability to

pay.
 PROBLEM

Our presentation is concerned with the database of doctors, medicine, patients,

and patient’s treatment wards of NASIHA HOSPITAL. The main purpose of

this report is to accommodate the user in such a way that he/she can easily enter

information, access it and maintain the database without the hassle of data

redundancy.

DATABASE is an organized collection of logically related data. DATABASE

MANAGEMENT SYSTEM (DBMS). A software system that is used to create,

maintains, and provides controlled access to user databases. DBMS manages

data resources like an operating system manages hardware resources.

CURRENT SYSTEM

Currently Nasiha is using Microsoft Excel to maintain the entire database of the

hospital. Microsoft Excel’s spreadsheet program provides an alternative

environment for many computations required for macro-investment analysis. Its

ubiquity and ease of use are among its more attractive features. However,

spreadsheets are notoriously dangerous, since the underlying logic of a set of

calculations is usually contained in formulas scattered around the sheets. Worse

yet, the formulas are usually hidden from sight, behind the numbers
 representing the results of their calculations. These disadvantages loom

especially large when an environment is to be chosen primarily as a means of

communication. Users must create subset directories fir data management.

Excel data can be lost when the application is broken down into files. Viruses

can be attached to an Excel file through macros. Macros are mini programs that

are written into an Excel spreadsheet.

PROPOSED SYSTEM

Excel may be in fine if an organisation only has a small amount of data, and if it

don’t have many attributes against each piece of data. It may be fine if an

organisation don’t have much in the way of relational data across multiple

worksheets. Once you start storing many attributes against each piece of data,

and perhaps you find yourself repeating information across multiple worksheets,

then it’s time to start using Access. If we need to work on a huge number of sets

of data, which we have to sort, filter, group and create subgroups on which to

calculate or extract values we are better off with

Access.

The process of creating groups and then performing calculations on those is way

more cumbersome with Excel. Excel on the other hand will be better for

analysing up to a few hundred records of data. Another important reason for

using Access over Excel is, if you need to generate a lot of queries and reports.

Access is much better suited for doing this compared to Excel. As Nasiha is a

huge organisation we proposed them to maintain their data in Access.

Database File: This is your main file that encompasses the entire database

and that is saved to your hard-drive or floppy disk.

TABLES: A table is a collection of data about a specific topic, such as student

or contacts. Using a separate table for each topic means that you store the data

only once, which makes your database more efficient, and reduces data-entry

errors.

FORMS: A form is a graphical representation of a table. A form is very good

to use when you have numerous fields in a table. This way you can see all the

fields in one screen.

QUERY: A question answered from the database as posed in a particular

querying language. The result of a query is a table in which the columns are the

attributes the user wants to see and the rows are different instances of those

attributes that satisfy the qualification entered by the user.

REPORTS: A report is an effective way to present your data in a printed

format. Because you have control over the size and appearance of everything on

a report, you can display the information the way you want to see it.
 NASIHA HOSPITAL

ENTITY RELATIONSHIP DIAGRAM

(ERD)
Entity Relationship Diagram

As seen in the Entity Relationship Diagram represent the patient receiving a

treatment from a doctor. When a patient arrives at the hospital a new customer

database is started by entering the detail of that patient (Patient ID, Name, NIC,

Admission date and Discharge date). The associativity entity type PATIENT

TREATMENT has the attributes (Patient ID, Doctor ID, Ward ID, Treatment

ID, Time and Results) values are recorded for these attributes for each instance

of PATIENT TREATMENT. The Patient was entered in the Ward(Ward ID,

Ward Name, Ward Charges) for the Treatment(Treatment ID, Medicine Name

and Medicine Dues). The associativity entity type RECEIPT has the attributes

(Receipt ID, Doctor ID, Patient ID, Ward ID, Medicine ID).

ENTITY

 INSTANCE

A person, place, object, event, or concept which often

corresponds to a row in a table of Microsoft access.

TYPE

A collection of entities which often corresponds to a table.

 ENTITIES OF NASIHA HOSPITAL

CANCER DATABASE

MAJOR ENTITIES

 Doctors
 Patients
 Wards
 Medicine
 Treatment
ASSOCIATIVE ENTITIES
 Patient_treatment
 Receipts

ATTRIBUTES:
Doctors
 Doctors ID
 Doctors number
 Doctors fee
Patients
 Patients ID
 Patients name
 Patients NIC
 Admission date
 Discharge date

Wards
 Ward ID
 Ward name
 Ward charges
Medicine
 Medicine ID
 Medicine name
 Medicine dues

Treatment
 Treatment ID
 Treatment description

Patient Treatment
 Patient ID
 Doctor ID
 Ward ID
 Treatment ID
 Results
 Time
 Date

Receipts
 Receipts ID
 Patient ID
 Doctor ID
 Ward ID
 Medicine ID
 TABLES IN DATABASE
DOCTOR TABLE
Primary key: doctors_id

FIELD NAME DATA TYPE FIELD SIZE

doctors_id Text 50

doctors_name Text 50

doctors_fee Currency
 MEDICINE TABLE

Primary key: medicine_id

FIELD NAME DATA TYPE FIELD SIZE

medicine_id Text 50

medicine_name Text 50

medicine_dues Currency

PATIENT TREATMENT TABLE

Primary key: patient_id, doctors_id, ward_id, treatment_id, time, date

FIELD NAME DATA TYPE FIELD SIZE

patient_id Text 50

doctors_id Text 50
ward_id Text 50

treatment_id Text 50

time Date/Time

Results Text 50
 PATIENT TABLE

Primary key: patient_id

FIELD NAME DATA TYPE FIELD SIZE

patient_id Text 50

patient_name Text 50

patient_NIC Text 50

admission_date Date/Time

discharge_date Date/Time

WARD TABLE

Primary key: ward_id

FIELD NAME DATA TYPE FIELD SIZE

ward_id Text 50

ward_number Text 50
ward_charges Currency 50
 RECEIPT TABLE

Primary key: receipt_id, patient_id, doctors_id, ward_id, medicine_id

FIELD NAME DATA TYPE FIELD SIZE

receipt_id Text 50

patient_id Text 50

doctors_id Text 50

ward_id Text 50

medicine_id Text 50

RECEIPT TABLE

Primary key: receipt_id, patient_id, doctors_id, ward_id, medicine_id

FIELD NAME DATA TYPE FIELD SIZE

receipt_id Text 50

patient_id Text 50
doctors_id Text 50

ward_id Text 50

medicine_id Text 50