Database Design Proposal

This proposal discusses the need for a Hospital Management System to manage all the tasks of a multi-specialty hospital. It includes entities like Doctors, Occupancy, Patient Information, Staffs, Supplies Control, Billing, Insurance, Laboratory/Radiology, Employees, Statistical Report, and telehealthcare.

Running Head: DATABASE DESIGN PROPOSAL
Database Design Proposal
Name of the Student
Name of the University
Author Note

1
DATABASE DESIGN PROPOSAL
Introduction:
Information Technology has revolutionized many unorganized sectors, including the medicinal
field. The ever-growing world with the growing population and medical needs requires Hospitals
to implement an Information storing system that will be able to manage all the tasks of a multi-
specialty hospital because it is hard to keep track of everything manually. To implement a
database design, the first thing to make sure of is the entities that need to be added to the design
(Asabe, Oye & Goji, 2013). The entities, in this case, include; Doctors, Occupancy, Patient
Information, Staffs, Supplies Control, Billing, Insurance, Laboratory/Radiology, Employees,
Statistical Report, and telehealthcare.
Case Study:
Manual registration and allocation in a hospital is a task in itself. It is a time consuming
and an energy-draining process. In today’s IT advanced world, there is a need to implement
HMS to create a support system that allowed the management to make vital decisions.
Proposed Solution Strategy and Requirement Analysis:
There have been cases of delays in patient’s information retrieval, and there is a need for
a health custodian for health facility to be appropriate. Hence, an imperative Hospital
Management System can be the initial point for improved medical care facilities. There would be
no need for traditional methods of paper filling, hours of waiting time as appointments could be
made in an instant with the help of a Database Management System, and other various
advantages. The proposed software solution is a Hospital Management System. This will be used
to gain data from the patients for future references and store information related to all the
Hospital entities (Atassi et al. 2014). The current system in use was a manual one that required

2
DATABASE DESIGN PROPOSAL
people to invest a lot of their time and energy. The purpose of this system is to increase
productivity with the increase in customers and reduce perquisite. Requirement specifications are
both functional and non-functional. Software requirements include use cases that describe
interactions to the patients they have with the software. Non-Functional requirements include
conditions on the designing and the implementation like standard quality, constrains on
designing and performance requirements.
Database Designing:
The main attributes of the proposed software solution should be a Reliable, Available at all
hours, Secured with required Cryptography, Portable, and Easy to Maintain. The software
solution design will consist of data types and Entity Relationships because everything is
interrelated.
Data types required will be Integer, Varchar, and Date/Time. Required tables for the
Database will be, Patient Table (consists of personal credentials), Doctor Table (availability and
appointments), Lab Table (Tests and diagnosis), Inpatient Table (patients under special care),
Outpatient table (discharged patients), Room Table (allocations) and Bill Table (charges). Entity
Relationship diagrams are used to illustrate the database with a structure that is logical (Coronel
& Morris,2016). ER depicts relationships among the entities considering the entire object as an
entity.
Resources to develop data model/hosting consideration:
The data model is the skeleton of the software solution being developed that holds everything
together and in the case of HMS Relational Model in the form of relations and tables. After the
conceptual design using an ER diagram, the conversion from a conceptual model to a relational

3
DATABASE DESIGN PROPOSAL
model that is implemented using ant RDBMS language like Oracle SQL, MySQL (Harrington,
2016).Aggregation of data is the main functionality while considering hosting the data model.
Analysis and dissemination of the information:
Breakdown of responsibilities among staff to analyze and dissipate the information is done using
the following components:
Survey Planning Survey Operation Survey Evaluation
Specify survey contents Creating a frame Check survey option
Establish Survey procedures
Sampling
Evaluation of feedback
metadata.
Design/Configure the data
processing system Collecting Data -
Input Processing Preparing data -
Data transformation Observations -
Output Processing Analysis and Estimations -
-
Dissemination and
Presentation
-

4
DATABASE DESIGN PROPOSAL
References:
Asabe, S. A., Oye, N. D., & Goji, M. (2013). Hospital patient database management system: A
case study of general hospital north-bank makurdi-nigeria. Compusoft, 2(3), 65.
Atassi, N., Berry, J., Shui, A., Zach, N., Sherman, A., Sinani, E., ... & Leitner, M. (2014). The
PRO-ACT database: design, initial analyses, and predictive features. Neurology, 83(19),
1719-1725.
Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management.
Cengage Learning.
Harrington, J. L. (2016). Relational database design and implementation. Morgan Kaufmann.