0% found this document useful (0 votes)
61 views53 pages

1child Birth Records Management System

child Birth Records Management System submitted at cavendish university Uganda. by Gloris Mbula

Uploaded by

yannick baze
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
61 views53 pages

1child Birth Records Management System

child Birth Records Management System submitted at cavendish university Uganda. by Gloris Mbula

Uploaded by

yannick baze
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 53

CHILD BIRTH RECORDS MANAGEMENT SYSTEM

A CASE OF NSAMBYA HOSPITAL.

BY
STUDENT ID:

E-mail:
MOBILE PHONE NO

A RESEARCH REPORT SUBMITTED TO THE FACULTY OF


SCIENCE AND TECHNOLOGY IN PARTIAL FULFILLMENT
OF THE REQUIREMENTS FOR THE AWARD OF
A BACHELOR DEGREE IN INFORMATION
TECHNOLOGY OF CAVENDISH
UNIVERSITY UGANDA.

JANUARY, 2020
DECLARATION

I …….., hereby declare that this report is an original composition and a true record of the
activities I was involved in during my research project work. This report is not a duplicate
of any academic document submitted at any institution for any academic award.

Signature: ______________ Date: ______________

i
APPROVAL
This is to certify that my approval has been given for this research report to be submitted to the
faculty of science and technology in partial fulfillment for the award of a bachelor degree of
information technology of Cavendish University Uganda.

Signature: ______________ Date: ______________

Mr. MOSES BALIRWA


SUPERVISOR

ii
DEDICATION

This report is dedicated to my beloved family, I also dedicated it to my friends for the guidance
and financial they rendered to me during the study.
I further dedicated this to all the personnel staffs of Cavendish University Uganda especially
those dealing with computer studies and information technology.

iii
ACKNOWLEDGEMENT

I would like to thank Almighty God for giving me the opportunity, ability, health and wisdom to
successfully complete this project research work.
I register my sincere gratitude to my beloved parents, for the spiritual, moral and financial support
accorded to me throughout the course of my education.
I acknowledge my supervisor Mr. Moses balirwa for his great support, patience and guidance
throughout the accomplishment of this project.
Finally, I would like to express my gratitude to all the staff of Cavendish University, especially
the staff of Faculty of Computer Science and Information Technology for the assistance that they
have accorded me throughout my studies at the University.
May the good Lord richly bless everyone who has in one way or another contributed to this
Research Project.

iv
TABLE OF CONTENTS
DECLARATION ...................................................................................................................... i
APPROVAL ............................................................................................................................. ii
DEDICATION ........................................................................................................................ iii
ACKNOWLEDGEMENT ...................................................................................................... iv
Table of figures ...................................................................................................................................................... viii
LIST OF ACRONYMS ........................................................................................................... ix
CHAPTER ONE ...................................................................................................................... 1
INTRODUCTION .................................................................................................................... 1
1.0 Introduction .........................................................................................................................................................1
1.1 Background of the Study .....................................................................................................................................1
1.2 Problem Statement ...............................................................................................................................................3
1.3 Objectives of the Study ........................................................................................................................................3
1.3. 1 Main objective .................................................................................................................................................3
1.3.2 Specific objectives ............................................................................................................................................3
1.4 Research questions ...........................................................................................................................................3
1.5 Scope of the Study ...............................................................................................................................................3
1.5.1 Content scope ...................................................................................................................................................3
1.5.2 Time scope ........................................................................................................................................................4
1.5.3 Geographic bounds ...........................................................................................................................................4
1.6 Significance of the study .....................................................................................................................................4
CHAPTER TWO...................................................................................................................... 5
LITERATURE REVIEW ......................................................................................................... 5
2.0 Introduction .........................................................................................................................................................5
2.1 Related system.................................................................................................................... 5
2.2 Web Services ...................................................................................................................... 5
2.2.3 Access Control Models .....................................................................................................................................6
2.3 Flexible Authorization Framework ......................................................................................................................6
2.4 Birth registration in Nigeria .................................................................................................................................7
2.5 Child motility in Nigeria ......................................................................................................................................7
2.6 Analyzing the existing systems ............................................................................................................................8
2.7 Information system .............................................................................................................................................8
2.7.1 Operational Challenges .....................................................................................................................................9
2.8 Web based application ......................................................................................................................................9
2.8.1 Advantages of web based application ............................................................................................................. 10
2.9 The System Development Life Cycle ................................................................................................................ 11
2.9.1 Advantages of system development life cycle ................................................................................................ 12

v
2.9.2 There are always disadvantages with everything ............................................................................................ 13
2.10 Database application ........................................................................................................................................ 13
2.11 Chapter Summary ............................................................................................................................................ 13
CHAPTER THREE ................................................................................................................ 14
RESEARCH METHODOLOGY ........................................................................................... 14
3.0 Introduction ....................................................................................................................................................... 14
3.1 Study investigation ............................................................................................................................................ 14
3.2 Target population ............................................................................................................................................... 14
3.2.1 Sample size ..................................................................................................................................................... 14
3.2.2 Table of sample size. ...................................................................................................................................... 15
3.3 Data Collection .................................................................................................................................................. 15
3.3.1 Interview .................................................................................................................................................... 15
3.3.2 Observation method ........................................................................................................................................ 15
3.3.3 Questionnaire Guide ....................................................................................................................................... 16
3.4 Data analysis ...................................................................................................................................................... 16
3.5 System study ...................................................................................................................................................... 16
3.5.1 System study and findings .............................................................................................................................. 16
3.6 System implementation ..................................................................................................................................... 17
3.6.1 implementation tool ........................................................................................................................................ 17
3.6.2 System testing ................................................................................................................................................. 17
CHAPTER FOUR .................................................................................................................. 18
SYSTEM ANALYSIS AND REQUIREMENTS .................................................................. 18
4.0 Introduction ....................................................................................................................................................... 18
4.4 System design ................................................................................................................................................. 18
4.4.1. Data flow diagram ......................................................................................................................................... 18
4.4.2 Entity relationship diagram ............................................................................................................................. 18
4.5 Design Tools ...................................................................................................................................................... 18
4.6 Logical design.................................................................................................................................................... 19
4.7 Nonfunctional requirements .............................................................................................................................. 19
4.8 Software requirements ....................................................................................................................................... 19
4.9 Context Flow Diagram ...................................................................................................................................... 20
Fig 2: Context flow diagram level One ................................................................................ 20
Fig 3: Data flow diagram level two ........................................................................................ 21
4.4.4 Physical Design .............................................................................................................................................. 21
4.4.5 Architectural design ........................................................................................................................................ 21
Fig 4: System Architecture..................................................................................................... 22
Table 2 Child birth registration table ..................................................................................... 23
4.5 System presentation.......................................................................................................... 23

vi
Table 3: Child medical form .................................................................................................. 24
Table 4: Child Details ............................................................................................................ 25
CHAPTER FIVE .................................................................................................................... 26
SYSTEM DESIGN AND IMPLEMENTATION .................................................................. 26
5.0 Introduction .................................................................................................................. 26
5.1 System implementation ................................................................................................ 26
Figure 1 Home page ............................................................................................................... 26
Figure 2 Admin Login page ................................................................................................... 27
Figure 3 Hospital Registration page ....................................................................................... 27
Figure 4 Hospital login ........................................................................................................... 28
Figure 5 Registration Form .................................................................................................... 28
Figure 6 Number of registration babies................................................................................. 29
Figure 7 Birth certificate page ................................................................................................ 29
5.2 Database Design and development results ......................................................................................................... 30
Figure 8 Parents table ............................................................................................................. 30
Figure 9 Child table ................................................................................................................ 31
Figure 10 Admin table............................................................................................................ 31
Figure 11 Hospital table ......................................................................................................... 32
5 2 System Testing and Validation .......................................................................................................................... 32
CHAPTER SIX ...................................................................................................................... 33
CONCLUSIONS AND RECOMMENDATIONS ................................................................ 33
6.0 Introduction ....................................................................................................................................................... 33
6.1 Achievements of the study ........................................................................................... 33
6.2 Limitations ..................................................................................................................................................... 33
6.4 Recommendation .............................................................................................................. 34
6.5 Conclusion........................................................................................................................ 34
REFERENCES ....................................................................................................................... 35
APPENDIX ONE: INTERVIEW .......................................................................................... 37
APPENDIX TWO: TIME/ACTIVITY SCHEDULES .......................................................... 38
APPENDIX THREE: BUDGET ESTIMATE ....................................................................... 39
APPENDIX FOUR: SAMPLE CODE ................................................................................... 40

vii
Table of figures
Figure 1 Home page .................................................................................................................................................... 26
Figure 2 Admin Login page ......................................................................................................................................... 27
Figure 3 Hospital Registration page ............................................................................................................................ 27
Figure 4 Hospital login ................................................................................................................................................ 28
Figure 5 Registration Form .......................................................................................................................................... 28
Figure 6 Number of registration babies ...................................................................................................................... 29
Figure 7 Birth certificate page ..................................................................................................................................... 29
Figure 8 Parents table .................................................................................................................................................. 30
Figure 9 Child table ..................................................................................................................................................... 31
Figure 10 Admin table ................................................................................................................................................. 31
Figure 11 Hospital table .............................................................................................................................................. 32

viii
LIST OF ACRONYMS

A.C.L Access Control List

DAC Discretionary Access Control

DFD Data flow diagrams

E.R.D Entity relationship diagrams

ECHR Electronic Child Health Record

FAF Flexible Authorization Framework

Html Hypertext markup language

IT Information Technology

ICT Information and Communication Technology


NGO Non-Government Organization
PHP Hypertext preprocessor
RDBMS Relation Database Management Systems

SDLC System Development Life Cycle

SQL Structured query language

UML Unified Modeling Language

UNICEF United Nations International Children’s Emergency fund

WHO World Health Organization

ix
CHAPTER ONE

INTRODUCTION
1.0 Introduction
Nationally representative estimates of under-five mortality can be derived from a number of
different sources, including public registration and sample surveys, but excluding demographic
surveillance sites and Nsambya Hospital data, which are rarely representative. The preferred
source of data is a civil registration system which records births and deaths on a continuous basis.
If registration is complete and the system functions efficiently, the resulting estimates was be
accurate and timely. However, in the developing world most countries do not have well-
functioning vital registration systems, and household surveys, such as the UNICEF supported
Multiple Indicator Cluster Surveys (MICS), the USAID supported Demographic and Health
Surveys (DHS) and periodic population censuses have become the primary source of data on under
five and infant mortality in developing countries. These surveys ask women about the survival of
their children, and it is these reports that provide the basis of child mortality estimates for a
majority of developing countries.

1.1 Background of the Study


Records Management Act recognizes that creating comprehensive records and preserving them
forever would be an impossibly expensive burden. Instead, the Act creates a mechanism for the
orderly and accountable disposition of records in the form of the Records Disposition Panel. The
Act also makes the state’s Department of Administration (the Information Policy Analysis
Division specifically) responsible for overseeing the records management process.

Child birth registration is the continuous, permanent, compulsory, and universal recording within
the civil registry of the occurrence and characteristics of births in accordance with the legal
requirements of a country (UNICEF, 2013). Civil registration is a system where the occurrence
and characteristics of vital events pertaining to the population like births, deaths, marriages and
divorces are recorded in a continuous, permanent and universal manner. The purpose of civil
registration is primarily for establishing the legal documents provided by the law. These records
serve also as a primary source of vital statistics.

1
Birth registration is crucial for the implementation of national policies and legislation
establishing minimum age for work, military conscription and marriage, certificate of birth is
fundamental to the realization of a number of rights and practical needs such as:- Ensure that
children enroll in school at the right age, To prevent child labor by enforcing laws relating to
minimum age for employment, To effectively counter the problem of forced marriage for
girls before they are legally eligible without proof of age, Getting an educational, health
and or insurance policy cover for a child, Protecting a child orphan from being
disinherited by guardians/ relatives, Ensure that children in conflict with the law are given
special protection and not treated (legally) practically as adults.

In 2011, through a public-private partnership between Kenya Telecom and Unicef, the
electronic birth and death registration system known as the Mobile Vital Records System
(Mobile VRS) was developed. Mobile VRS enables birth notifications to be sent by mobile
phones to the server and enables health and government officials who have access to the
internet and a printer to register and print birth certificates in real time. Mobile VRS has
been designed to work in both healthcare and non-healthcare environments. For example, in a
healthcare setting where a child is born in a Nsambya Hospital, local administrators. Simply
enter and upload birth details to a web-based registration portal with connectivity delivered
through Kenya Telecom's existing 3G network. Data is transferred almost instantaneously,
and it cuts the uncertainty about whether records was reach the national.

At Nsambya Hospital offers capture mother’s details by using hand aided tools to record the
mother’s details these include pens, hand books, rulers and pencils this method of data
processing is challenged with many challenge these include. Time consuming as in compiling
birth records in a week, month and year, loss of data since all the data is recorded in paper based
files they can easily be burnt, stolen by internal or external individuals, human errors many
errors are likely to happen during the process of data entering because most of the data
processing is done by human beings who can make .error at any point and less information can
be stored by the paper based file as compared to computerized database in addition paper base
files requires a lot of space and furniture.

2
1.2 Problem Statement
Nsambya Hospital covers a wide catchment area of districts within Kampala; due to the increasing
number of birth mortality records becomes unmanageable with the manual data processing
method. Manual data process method is associated with the number of problems like time
consuming in retrieving child records, less information can be stored with the help of manual data
processing method, many errors are made when processing which require a lot of time to process
Simple tasks, lack of data integration, Data can easily be lost through theft of documents, fire,
floods etc. Basing on the above problems there is a need to develop a Web based Child
Records Management System which can capture child mortality records more efficiency and
effectively.

1.3 Objectives of the Study

1.3. 1 Main objective


To develop a child birth records management system.

1.3.2 Specific objectives


i. To determine the requirements for developing web based child records management system
ii. To design a web based system for child records management system.
iii. To implement the system so as to transform the design into a working system
iv. To test the system

1.4 Research questions


i.What are the system requirements needed for the new system?
ii.How can the child records management system be designed?
iii.How can the designed system be implemented?
iv.How can the new online child birth management system be tested and validated?

1.5 Scope of the Study

1.5.1 Content scope

The study only looked at the design of a child records management systems using tools such as
MYSQL, HTML and PHP.

3
1.5.2 Time scope
The period of the coverage of the study was August-November 2019

1.5.3 Geographic bounds


The research will be carried out at Nsambya Hospital located in Makindye division

1.6 Significance of the study


I. Web based child records managements system will promote data sharing between the
government sectors and Nsambya Hospital for budgeting and planning of the future
generation.

II. The proposed will improve data security since it has access control limit which will
restrict unauthorized users from accessing system resources.

III. The proposed will improve data storage as results of developing central database which
provides a central point for child birth records storage.

IV. New system can assist in generating birth certificate hence solve the challenge of
delaying child certificate in addition this was the government to verify child birth
everywhere by using child Id-number

4
CHAPTER TWO

LITERATURE REVIEW
2.0 Introduction
This chapter looks into related studies carried out in line with the research topic, a web based child
records management system for Nsambya hospital in Kigali Rwanda and other literature about
the subject was be reviewed. In this review, the major focus was be to establish issues that have
not been adequately addressed by the previous researchers

2.1 Related system


An electronic child health record (ECHR), or electronic child medical record (ECMR), refers to
the systematized collection of patient and population electronically-stored health information in a
digital format. These records can be shared across different health care settings. Records are shared
through network-connected, enterprise-wide information systems or other information networks
and exchanges. ECHRs may include a range of data, including demographics, medical history,
medication and allergies, immunization status, laboratory test results, radiology images, vital
signs, personal statistics like age and weight, and billing information.
ECHR systems are designed to store data accurately and to capture the state of a patient across
time. It eliminates the need to track down a patient's previous paper medical records and assists
in ensuring data is accurate and legible. It can reduce risk of data replication as there is only one
modifiable file, which means the file is more likely up to date, and decreases risk of lost paperwork.
Due to the digital information being searchable and in a single file, ECMR's are more effective
when extracting medical data for the examination of possible trends and long term changes in a
patient. Population-based studies of medical records may also be facilitated by the widespread
adoption of ECHR's and ECMR's.

2.2 Web Services


According to Gellersen, and Gaedke. (2005), Web services provide a standard means of
interoperating between deferent software applications running on a variety of platforms and frame
works. Web services are applications that expose their business logic, data and processes through
programmatic interface. Unlike traditional Client/Server models, Web services generally use
HTTP as the underlying communication protocol which allows messages to go through most

5
of the recalls (most of the recalls' setting allow the access to HTTP port). Web services do
not provide users with GUI (Graphic User Interface). However, developers can add Web
services into their Web page or applications and other users with GUI which contains the
functionalities of the Web services.

2.2.3 Access Control Models


This subsection focused on related work on access control models that can be applied to e- Health
portals. The access control matrix is an early access control model which can be represented
by a triple subject, object, and right. The object is an entity (such as le, process etc.) that to be
protected and the subject is the entity (such as user, process etc.) who wishes to access the objects.
The right species the operations that a subject is allowed to perform on the desired object.
According to Gokhale, Kumar, (2001), access control lists (ACLs) is a common way to implement
the ACM. Each object is associated with an ACL to indicate the access right that each subject is
authorized to perform action on the object. In discretionary access control (DAC), accesses are
assigned by the owner of objects. DAC also allows a subject to pass its access permissions to
another subject. Upon acquiring the permission either directly or indirectly, this subject is
authorized to access these objects.

2.3 Flexible Authorization Framework


Many access control policies have been proposed and are widely applied in information systems.
However, in practice, only a specific policy (such as closed policy or open policy) can be applied
in a system, which cannot satisfy increasing access control requirements. Thus, Flexible
Authorization Framework. (FAF) is proposed to allow multiple access control policies to be
applied within a single system. FAF allows positive, negative and hybrid (both positive and
negative) policies to be species to allow or deny an access in a powerful, declarative and exile way.
It also employs meta-policy to solve the ICT resolution problem when hybrid policy is species.
FAF employs four tiers of policies to manage access control. The last stage includes the description
of subject and object hierarchies, and a set of authorizations according to the protection
requirements. In this stage, ICT problems may occur since both positive and negative
authorizations may be derived for executing an action on a given object, thus a subject could be
authorized and denied to perform the action at the same time. To solve this problem, in the second

6
stage ICT resolution policies are enforced. However, it is possible that access is neither authorized
nor denied.

2.4 Birth registration in Nigeria


Birth registration is the official recording of the birth of a child by some administrative level of
the state and coordinated by a particular branch of government. It is a permanent and official record
of a child’s existence. Ideally, birth registration is part of an effective civil registration system that
acknowledges the existence of the person before the law, establishes the child's family ties and
tracks the major events of an individual's life, from live birth (see box) to marriage and death.
A fully functional civil registration system should be compulsory, universal, permanent and
continuous and should ensure the confidentiality of personal data. It should collect, transmit and
store data in an effective way and guarantee their quality and integrity. It should have two main
objectives: legal and statistical. Such a system, and its instrumental value in safeguarding human
rights, contributes to the normal functioning of any society. The registration of a child’s
birth enables that child to obtain a birth certificate. In some cases, the issuing of a certificate
automatically follows birth registration, while in others a separate application must be made.
In either case, a birth certificate is a personal document issued to an individual by the state

2.5 Child motility in Nigeria


Silva, (2012) Indicators of child health and mortality show mixed progress over the past decade
and acceleration is required to reach the target for reduction in child mortality. The under-five
mortality rate has fallen from 156 per 1,000 live births in 1995 to 152 in 2001 and further to 137
in 2006. The infant mortality rate, which measures deaths among children younger than 1 year
of age, rose between 1995 and 2001, from81 to 88 per 1,000 live births, and fell again to 76 in
2006.
Also, mortality levels are much higher in rural areas than in urban areas. Cavendish has the lowest
level of mortality compared to the north, West Nile and southwest, which have the highest levels.
The inequality in child health outcomes is also clear across different wealth categories. The levels
of both infant and child mortality are about 40% lower in the wealthiest 20% of households in
Nigeria compared to the poorest 20%. However, the gap between the wealthiest and poorest
households has narrowed in recent years despite the fact that the gap remains wide relative to the

7
MDG target. Hence, it is a key priority of the Government of Nigeria to sustain and accelerate
attainment of MDG 4, especially among the poorest.
The proportion of 1-year-old children immunized. Against measles declined between 1995
and2001 from 82% to 63%. Following implementation of the 2001-2005 immunization
revitalization strategic plans, measles immunization rose again in 2006 to 89%. The same pattern
is evident in the provision of DPT3 vaccines, a combination of vaccines against three infectious
diseases: diphtheria, pert us sis (whopping cough) and tetanus. In 2009, the measles immunization
rate was81 %, which is below the 90% national target.

2.6 Analyzing the existing systems


Analyzing the existing system is a problem solving technique that decomposes a system into its
component pieces for the purpose of the studying how well those component parts work and
interact to accomplish their purpose" According to the Merriam-Webster dictionary, systems
analysis is "the process of studying a procedure or business in order to identify its goals and
purposes and create systems and procedures that was achieve them in an efficient way". Analysis
and synthesis, as scientific methods, always go hand in hand; they complement one another. Every
synthesis is built upon the results of a preceding analysis, and every analysis requires a subsequent
synthesis in order to verify and correct its results. This field is closely related to requirements
analysis or operations research. It is also "an explicit formal inquiry carried out to help someone
(referred to as the decision maker) identify a better course of action and make a better decision
than she might otherwise have made.

2.7 Information system


According to Sharma (2003). An information system (IS) is any organized system for the
collection, organization, storage and communication of information. More specifically, it is the
study of complementary networks that people and organizations use to collect, filters, and process,
create and distribute data. A computer information system is a system composed of people and
computers that processes or interprets information. The term is also sometimes used in more
restricted senses to refer to only the software used to run a computerized database or to refer to
only a computer system. Information system is an academic study of systems with a specific
reference to information and the complementary networks of hardware and software that
people and organizations use to collect, filter, process, create and also distribute data. An

8
emphasis is placed on an Information System having a definitive Boundary, Users,
Processors, Stores, Inputs, Outputs and the aforementioned. Communication networks.
Basing on the above argument child records management information system was have
the basic components of computer-based information systems are: Hardware- these are the
devices like the monitor, processor, printer and keyboard, all of which work together to
accept, process, show data and information. Software- is the programs that allow the hardware
to process the data. Databases- are the gathering of associated files or tables containing related
data. Networks- are a connecting system that allows diverse computers to distribute
resources. Procedures- are the commands for combining the components above to process
information and produce the preferred output.

2.7.1 Operational Challenges


According to Bulgacs, (2013) Operational challenges have become even more demanding. Some
of the key operational challenges facing today's information systems development include:
i. Bad Communication: Lack of understanding/planning for customer, organization and other
stakeholder’s requirements/needs for the project.
ii. Unclear Requirements: When requirements are not clearly identified, this was lead to change
of requirements during middle of the project which was increase project delivery time and
anger many customers.
iii. Increasing Cost: All of this was lead to added labor and project cost. Thus making the project
less profitable and takes away interest from stakeholders.
iv. Delayed Project Delivery: The result of what mentioned above was cause project
milestones to be pushed back and potential software with less functionality than what agreed
upon in the beginning agreement with the client.

2.8 Web based application


A Web-based application refers to any program that is accessed over a network connection using
HTTP, rather than existing within a device's memory. Web-based applications often run inside a
Web browser. However, Web-based applications also may be client-based, where a small part of
the program is downloaded to a user’s desktop, but processing is done over the Internet on an
external server.

9
2.8.1 Advantages of web based application
Cost effective development
With web-based applications, users access the system via a uniform environment-the web browser.
While the user interaction with the application needs to be thoroughly tested on different
web browsers, the application itself needs only be developed for a single operating system. There’s
no need to develop and test it on all possible operating system versions and configurations. This
makes development and troubleshooting much easier, and for web applications that use a flash
front end, testing and troubleshooting is even easier.
Accessible anywhere
Unlike traditional applications, web systems are accessible anytime, anywhere, via a PC with an
Internet connection, putting the user in charge of where and when they access the application.
Easily customizable
The user interface of web-based applications is easier to customize than it is in desktop
applications. This makes it easier to update the look and feel of the application, or to customize
the presentation of information to different user groups.

Accessible for a range of devices


In addition to customizing content for user groups, content can also be customized for
presentation on any device connected to the internet, including PDAs, mobile phones, etc.,
further extending the user's ability to receive and interact with information.
Improved interoperability
Using internet technologies based on industry-wide standards, it’s possible to achieve a far greater
level of interoperability between applications than with isolated desktop systems. For example, it
is much easier to integrate a web-based shopping cart system with a web-based accounting package
than it is to get two proprietary systems to talk to each other. Web-based architecture makes it
possible to rapidly integrate enterprise systems, improving work-flow and other business
processes.
Easier installation and maintenance
Installation and maintenance becomes less complicated. Once a new version or upgrade is
installed on the host server, all users can access it straight away. There is no need to upgrade each
client PC. Rolling out new software can be accomplished more easily, requiring only that users

10
have up-to-date browsers and plug-in. And as the upgrades are only performed by an experienced
professional to a single server, the results are more predictable and reliable.
Adaptable to increased workload

Increasing processor capacity also becomes a far simpler operation. If an application requires more
power to perform tasks, only the server hardware needs to be upgraded. The capacity of web-based
software can be increased by "clustering" or running the software on several servers
simultaneously. As workload increases, new servers can be added to the system easily-Google, for
example, runs on thousands of inexpensive Linux servers. If a server fails, it can be replaced
without affecting the overall performance of the application.
Security
Web-based applications are typically deployed on dedicated servers, which are monitored and
maintained by experienced server administrators. This is far more effective than monitoring
hundreds or even thousands of client computers, as is the case with new desktop applications.
Flexible core technologies
Any of three core technologies can be used for building web-based applications, depending on the
requirements of the application. The Java-based solutions (J2EE) from Sun Microsystems involve
technologies such as JSP and Servlets. The newer Microsoft .NET platform uses Active Server
Pages, SQL Server and .NET scripting languages. The third option is the Open Source platform
(predominantly PHP and MySQL), which is best suited to smaller websites and lower budget
applications.

2.9 The System Development Life Cycle


According to George, (2010), system development life cycle is the overall process of developing,
implementing, and retiring information systems through a multistep process from initiation,
analysis, design, implementation, and maintenance to disposal. There are many different SDLC
models and methodologies, but each generally consists of a series of defined steps or phases.

For any SDLC model that is used, information security must be integrated into the SDLC to ensure
appropriate protection for the information that the system was transmit, process, and store.

11
Initiation Phase, during the initiation phase, the organization establishes the need for a system and
documents its purpose. Security planning should begin in the initiation phase with the
identification of key security roles to be carried out in the development of the system. The
information to be processed, transmitted, or stored is evaluated for security requirements, and all
stakeholders should have a common understanding of the security considerations.

Development/Acquisition Phase, during this phase, the system is designed, purchased,


programmed, developed, or otherwise constructed. A key security activity in this phase is
conducting a risk assessment and using the results to supplement the baseline security controls.
In addition, the organization should analyze security requirements; perform functional and
security testing; prepare initial documents for system certification and accreditation; and design
the security architecture.

Implementation Phase. In the implementation phase, the organization configures and enables
system security features, tests the functionality of these features, installs or implements the system,
and obtains a formal authorization to operate the system. Design reviews and system tests should
be performed before placing the system into operation to ensure that it meets all required security
specifications. Operations/Maintenance Phase. In this phase, systems and products are in place
and operating, enhancements and/or modifications to the system are developed and tested,
and hardware and software components are added or replaced. Disposal Phase. In this phase, plans
are developed for discarding system information, hardware, and software and making the transition
to a new system. The information, hardware, and software may be moved to another system,
archived, discarded, or destroyed.

2.9.1 Advantages of system development life cycle


i. Formal review is created at the end of each stage allowing maximum
management control.
ii. This approach creates considerable system documentation.
iii. This documentation ensures that system requirements can be traced back to
stated business requirements.
iv. It produces many intermediate products that can be reviewed to see whether

12
they meet the user’s needs and conform to standards. These can be further worked on if
they require tweaks to be made, ensuring that the business gets exactly what it needs.

2.9.2 There are always disadvantages with everything


Users get a system that meets the need as understood by the developers; this may not be what was
really needed for them. There may be a loss in translation.

Documentation is expensive and time-consuming to create. It is also difficult to keep current. What
may be current this month may not be the same this time next year!

Users cannot easily review intermediate products and evaluate whether a particular product (e.g.,
data flow diagram) meets their business requirements.

Another disadvantage of a program or software that follows the SDLC program is it encourages
stiff implementation instead of creativity. There are requirements that must be met and that is all
that developers complete.

2.10 Database application


Cannoly and Begg (2005) argues that database application development cycle stages as being
Database planning, System definition, Requirements collection and analysis, Database design,
DBMS selection, Application design, Prototyping, Implementation, Data conversion and loading,
Testing, and Operational maintenance. In our database development we intend to use some of
Cannoly and Begg' s database development life cycle stages which was include; Database
planning, system definition, requirements collection and analysis, database design, DBMS
selection, application design, implementation and testing.

2.11 Chapter Summary

This chapter has looked at the literature that gives this study on the theoretical basis. It has
specifically discussed literature about health systems, web-based system, and database and
system development.

13
CHAPTER THREE

RESEARCH METHODOLOGY

3.0 Introduction
This chapter describes the methods that were used in data collection, analysis, specification and
development. It consists of research design, target population, sample size, sampling techniques,
data collection methods and analysis techniques.

3.1 Study investigation


In this phase the overall child records process study of the desired system is done. The child
requirements are specified at a high level and the information requirements out of the system are
identified. Once this is done, the basic architectural framework of the desired system is prepared
by the researcher.
The researcher took a feasibility study as the first stage in system life cycle with an aim of
understanding the existing system and this stage, where the research determined whether the
proposed system was to work or not basing on the five main factors like economic, legal,
operation, schedule and technical feasibility study. In this stage the researcher identified major
entities and user requirements of the proposed system.

3.2 Target population


The population size for this study was 164 people including staff, administrators and people from
community. The choice of child's parents was be made since the study is focused on child motility
and staff those are people who delivery the service to clients.

3.2.1 Sample size


The researcher used both purposive and random sampling to ensure the sample reflects the required
categories. In purposive the researcher chooses the sample based on who they think would be
appropriate for the study. This was used primarily when there are a limited number of people that
have expertise in the area being researched. Random sample the researcher chose from a larger a
population. Each individual was chosen randomly and entirely by chance, such that each individual
had the same probability of being chosen at any stage during the sampling process.

14
3.2.2 Table of sample size.
Table 3. 1 Sample Size

Population Number Sample size (100%)

Staff 40 25

Administer 4 2

Clients/mothers 120 73

Total 164 100

3.3 Data Collection


The researcher used the following data collection methods to collection data that was necessary to
develop the proposed system

3.3.1 Interview
One of the data gathering tools that was used in this research is an interview . An interview
is a formal or informal meeting between two or more people with an intention of obtaining
information about something in particular, thus the researcher collected information from the
individual(s) through face-to-face interaction . The interview guide was used in this project
consisted of oral questions where the researcher asked direct questions through the use of mouth
to the respondent. This was done to obtain classification of information depending on the
interviewee's response to the specific set of questions in the guide. The researcher asked open-
ended questions to allow the interviewee to respond in any way that seems appropriate.

3.3.2 Observation method


The researcher took a watch over the activities involved in the existing system this helped the
researcher to understand how child records being recorded at Nsambya hospital . The researcher
decided to use this technique because of the following reasons:
i. The researcher was able to study the existing system in its natural setting, there by
understanding the subject.

15
ii. The observation guide was used by the researcher to review certain problems on their
own.
iii. Observation technique provided less biased description than other methods.

3.3.3 Questionnaire Guide


The researcher used both same structured and structured questionnaires. A questioner guide was
prepared and sent to the respondents in time such that they can tick the collect answer and send
back these questions was in form of yes or no, structured questions the respondents filled the
questioner guide and this helped the research to get the necessary information to develop the
proposed system Below are the reasons why the researcher decided to use this method:
Questionnaire guide enabled the researcher to get large amount of information collected from large
number of people in a short period of time and in a relatively cost effective way.

3.4 Data analysis


Analysis of data is a process of inspecting, cleaning, transforming, and modeling data with the
goal of discovering useful information, suggesting conclusions, and supporting decision-making
The researcher used different tool to analyses data SPSS, Micro excel and among others these
tool was help the researcher to sort data, to represent data on chats like pie chart, bar graph etc.

3.5 System study


The current system being used at NSAMBYA hospital is completely manual/paper based system.
According to the research carried out it shoes that the current system is insufficient to facilitate
quick service delivery. The medical officers are given the form to fill by the hospital
administrators; the medical officers take the paper based file to the doctors for medical
examinations and then the doctor document medical observations on the child form as shown in
the diagram below.
Manual based system for child birth records management system

3.5.1 System study and findings


The hospital administrator’s medical officers and mothers were interviewed in order to get a better
understanding of both manual and computerized system. Self- administered questionnaires were
also used to collect views and options from different mothers and medical officers. These findings

16
were from (interview, questionnaire and observation) have been analyzed using excel and a pie-
chat was generated to give clear understanding of all these systems as shown below in the table
Table 4. 3 system study findings

Respondents Result "


System Respondents Percentages
Computerized based 35 70%
system
Manual based system 10 20%
Others 5 10%
Total 50 100%
The high percentages (70%) of the respondents are in favor of the computerized child birth
records management system since it eases child records processing while 20% of the
respondents

Implementing child records management system


Requirements 4: Dreamweaver8 extended
This component is a developing tool that support languages such HTML, PHP, JAVA, CSS
The named script language was used for this system development.

3.6 System implementation

3.6.1 implementation tool


The researcher used HTML to develop the graphical user interface which enabled the system user
to interact with the system. MySQL, PHP and WAMP were used to design and link a database for
data storage during her project development. This database was easy to run, edit and update for
easier and better information retrieval. Fireworks and Adobe Photoshop was also used to create
and edit still images for a better end user interface in project design and implementation,
Wampserver2.0i and Apache For the project to run effectively, the researcher used the above
software to run on her server machine.

3.6.2 System testing


Testing included program testing, that ensured the individual programs work correctly in isolation
and system integration testing ensured that the programs work together correctly as a complete system.
The analyst carried out both these types of testing. The final stage is acceptance testing, which was
carried out by the user to ensure that the system meets the specified requirements.

17
CHAPTER FOUR

SYSTEM ANALYSIS AND REQUIREMENTS

4.0 Introduction
This chapter gives the description of child birth records management system, it also light on
system analysis, design and provide both conceptual and physical design. It describes
data/information flow in the system with help of context diagram, data flow diagram (DFD), data
dictionary (data base schemes) and the architectural design.

4.4 System design


This is the process or art of defining the architecture, component, modules, interfaces and that are
needed for a system to satisfy specified requirements. This comprises of tool and methods
especially diagrams. Used to analyze the design and implement the system such as entity
relationship diagrams (ERD) and data flow diagrams (DFD). They help in identifying the major
entities and their attributes as well as relationship between entities.

4.4.1. Data flow diagram


Data flow diagrams were developed to represent the input or output of data to or from a process in
the system. The researcher used the data flow diagrams symbols like process, entities, data store
and data flow

4.4.2 Entity relationship diagram


Entity relationship diagram was developed to represent relationships entities in the database. Entity
relationship diagram helped the researcher to determine the degree of a relationship the degree of
relationship was one too many or many to many depending on the entities.

4.5 Design Tools


Microsoft Visio was used or designing the data flow diagrams that show how data is transformed
at different processes, various external entities involved in the system and data stores. Data
dictionaries have also been used to give further details and meaning to the data, processes and
data stores of the system.

18
Entity Relationship Diagram were used in data modeling to show the different relationships
between entity types in the system and their associated relationship type in child records to come
up with logical design of Child Birth Records Management System.

4.6 Logical design


The logical design of a system shows an abstract representation of the data flows, inputs and
outputs of the system. This is often conducted using modeling, which involves a graphical
representation of an actual system. In the context 'of system design, modeling undertakes Data
flow diagrams and Entity Relationship as further seen below
Security
The child birth records management system restrict unauthorized users from accessing system
resources by verifying user name and passwords of users.

Search records
Child birth records management system allows system users to search individual record by
using a search criterion (child number).

4.7 Nonfunctional requirements


The nonfunctional requirement that the system provides are:
Usability
The system is easy to deal with and gives easy interaction, the system provides menu for all
system users.
Performance
The system is reasonably speedy according to the technology used and sends child records and
access other information on confirmed at the same time.

4.8 Software requirements


The software requirements, the system mainly needs these software products is shown in table
below.

19
Table 4. 1 Software requirements
Table 1 software requirements

List of requirements Description


Requirements 1: Operating Windows 10 professional for management computer hardware
System and Child birth records management system.
Requirements 2: Database MYSQL database this component stores child's data
Requirements 3: This component is open source software which was used
Wampservver2.0 for designing
Xampserver v3.2.2

4.9 Context Flow Diagram


The data flow diagram describes how data processed by the system in terms of inputs
and outputs and the processes involved. The diagram below shows the interaction between
external entities with processes and data store (database).

Fig 2: Context flow diagram level One

20
Fig 3: Data flow diagram level two

4.4.4 Physical Design


The physical design relates to the actual input and output processes of the system. This is
laid down in terms of how data is input into a system, how it is verified/authenticate,
how it is processed, and how it is displayed as output.
It is the detailed design of the system that included modules, the databases' hardware and
software specification of the' system. A personal computer’s physical design involves
input using a keyboard, processing within the central processing unit and output using a
monitor and printer. It would not concern the actual layout of the tangible hardware, which
for a personal computer would be a monitor, central processing unit, motherboard, hardware,
modem, video/graphical card and universal serial bus slots.

4.4.5 Architectural design


This involves decomposing the system into various subsystems. It shows how the database, child
records management system and graphical user interface communicate with each other. The
graphical user interface is linked to the database by use PHP. The database communicates with the
child records management system by use of My SQL. The system uses HTML and PHP to
communicate with the user through the graphical user interface as shown in diagram below

21
Fig 4: System Architecture

4.4.6 Database management system


MySQL version 2.0 was run by the use of open source software called wampserver2.0 which
is used for managing the system database. MySQL has some better qualities which makes it
preferable compared to other relational database management software. It is multithread, multi•
user database management software, supports all know platform including windows based
platform, requires less hardware resources for storage a well as for execution. Much faster,
support Unicode character storage and more than that, it further has a free version product. PHP
is an implementation of the Microsoft Dreamweaver was used to connect MySQL
relational database with front end web pages is the industry standard for database independent
connectivity between HTM and PHP programming language and a wide range of
databases. PHP connector file is laced in a folder.
4.4. 7 Database Tables
The database consists of several tables and these tables are used to store attributes of child
records. The database was designed and implemented using Wampserver2.0 MYSQL console
version2.0. It is accessed using MYSQL. The data base design using MYSQL statements.

22
Table 4. 2 Childbirth registration
Table 2 registration

Child_reg_Surname Varc(35)
Child_reg_Surname Varc(35)
Child_ Varc(35)
Child_ reg_nationality Varc(35)
reg_nationality
Child_ reg_dbate Date
Child_ reg_dbate Date Varc(20)
Child_ reg_regno PK
reg_regno
Child_ reg_mwork Varc(35)
Child_ reg_mwork Varc(35)
Varc(20) Varc(40)
Varc(35)
Child_ reg_fwork Varc(35)
Child_ reg_fwork
Child_ reg_subcounty Varc(40)
Child_ Varc(35)
Child_ reg_county Varc(35)
Varc(35)
Child_ reg_subcounty
reg_county Varc(35)
Child_ reg_district Varc(35)
Child_ Child_ reg_parish Varc(35)
reg_district
Child_
Table 2 Child birth registration table
reg_parish

4.5 System presentation


4.5.1 An index page for all user login
All users was have to use this very page as their startup page. One was click on the
corresponding link as his or her duty goes.
CHILD BIRTH RECORDS MANAGEMENT SYSTEM
Birth registration
IBirth registration interface enables the system user to input child birth details in the table

called birth registration. Finally the data stored in the table used to generate both demand
and periodic report.
Birth registration individual report
Child birth registration generates individual report by using child registration number,
individual report is printed out by a system user and therefore the mother receives hard
copy of birth Registration

23
Table 3: Child medical form
Table 3 child medication form

CH1LD RECORDS MANAGEMENT INFFORMATION SYSTEM

Child Details

Child
Name:
Amenu Child's Nationality
Congolese Registration Date of Birth
Number.445 :06·Jan·2019

Child's Nationality:
Health unit: Date:06·Jan·2019
Congolese

Parents Details

Name of the father:


Amenu Ahmad Father's telephone: Father's Occupation:
0704136480 Programmer

Mother’s child's Name


Mother's Telephone: Other's
Aishatu Muhammed 08034171643 08077383940
Physical address
District : Gombe Parish: Dawaki Sub-county: North East Division: Bauchi

The doctor use child birth registration number to search child details from the
registration table and child registration number is a primary key which identifies one
child from another child then the doctor adds medical records. Finally submits
medical records in medical table.

24
Table 4: Child Details
Table 4 child details

Child birth certificate

Child birth registration allows data sharing between local and hospital,
government the

government use child birth registration to generate birth certificate, for this case the
primary key is very important because it help to extra details of individual child from
the registration table. Finally register child birth certificate in birth certificate table.

25
CHAPTER FIVE

SYSTEM DESIGN AND IMPLEMENTATION

5.0 Introduction
This section describes the structure design of the system. It includes the screenshots for the system
and the description of the system functionality.

5.1 System implementation

Figure 1 Home page

The figure above illustrates the nature of the system. The page contains user controls that
can give users access to other pages. For example, a user can create an admin account log
and access all user control panels for the system.

26
Figure 2 Admin Login page

After successful creating an account, the administrators have been provided with clear
control panels that can allow to proceed with using the system to fulfill their request.

Figure 3 Hospital Registration page

after logging in an admin should create an Hospital account so that he/she will be able to
access the system registration

27
Figure 4 Hospital login

in this page the admin should login by using the hospital account and access the
registration form

Figure 5 Registration Form

From the forms identified above, the user (administrator) makes a request by either
submitting in information he or she need.

28
Figure 6 Number of registration babies

The above records described the number of registered babies

Figure 7 Birth certificate page

The above page allows the admin to request and print out the birth certificate

29
5.2 Database Design and development results
After the database design decisions, the right model for the database was modeled and exported to
the server and the database tables appear as show below

Figure 8 Parents table


below is how it looks on the server

30
Figure 9 Child table
below is how it looks on the server

Figure 10 Admin table


all admins are stored in this table, the structure of this table is shown below;

31
Hospital table, this is where all hospitals data is stored, below is how its structure looks on the
server;

Figure 11 Hospital table

5 2 System Testing and Validation


Testing and validation is the process of checking that a software system meets its specifications
and that if fulfills its intended objectives.
In this phase, both unit and integration testing were carried out to examine the System in order to;
Determine whether all the system requirements had been represented
Rectify errors
Find out whether the system does what it’s supposed to do.
Unit testing involved examining each module of the system to find out whether they were working
properly. The modules where assembled to form a complete system and thereafter, integration
testing was carried out to ensure a properly working system.
Verification and Validation were done in this phase; verification was used to find out whether the
right system was built. I.e. The system should conform to its specification as described in the
System Requirements Specification Document whereas validation helped to know whether the
built system is the right product. I.e. The software should do what the user requires.

32
CHAPTER SIX

CONCLUSIONS AND RECOMMENDATIONS

6.0 Introduction
This chapter present the conclusion and the recommendations. The conclusion was explained
according to the study achieved goals, according to the objectives of the study.

6.1 Achievements of the study


Child birth registration system was developed as results of identifying and
analyzing the weaknesses of the paper based system, child birth registration system
facilities government to integrate child records from the hospital and use it to process
birth certificate and the system also promotes electronic data sharing by use of internet
and web server.

6.2 Limitations
The implementation of child birth Management System faced numerous challenges among
which include the following.
i. Limited Internet facilities mainly for making research and hosting the database
which led the researcher end up using local hosting technology which is easy to
adopt and always free financial constraint. The study being self-sponsored activity,
the research would sometimes face some problems to finance some activities
involved in the study like transport to Focus Logistics Agencies and writing
materials.
ii. Through all the study, availability of electricity power was not on the
researcher’s side it would go off leaving the work on stand still.
iii. Limited time space given, a variety of technologies involved in the
development of the system which made it difficult to choose the one that can best
suite the users since all users have different experience and knowledge to
computer usage.

33
6.3 Future Works

i. To improve the system for future use various child birth system such as management
Information System (MIS) can be integrated for the system to be more comprehensive.
ii. Child birth management system should be further integrated with other functionalities
that were outside the scope of this study.
iii. There is need for child birth management to match the current technology trends. This
implies that the hospitals will need to undertake a number of reforms and changes in the
organizational policies to ensure a more effective and efficient way of service delivery
especially with online patients.

6.4 Recommendation
If the system is to be used· efficiently the users have to be familiar with the existing system: its
strengths, its weaknesses and also be educated about the new system and its advantages and
most importantly the benefits of child birth records management systems. Also the users must
be taught to recognize the need of this particular information system in as much as simplifying
their duties with time the system should be improved to facilitate other regional referral
hospitals in Nigeria. This was ease sharing of information especially in department of child
medical health and as such allows joint decision making that was improve child medical health.

6.5 Conclusion
This study identified the major problems faced by the existing child birth records management
system in Nigeria and attempted to solve them by developing child birth records management
system to manage records that consist of the following: A web-based application that can
therefore be accessed from any computer that is connected to the Internet thus making it online.
Edit, update and delete operations on exiting information in the database by the systems
administrator. The main objective of the study, which was to develop a system that can be used
by Nsambya hospital to capture child records, was achieved.

34
REFERENCES

Alkema L, New JR (2013). Estimating levels and trends in under-5 mortality: an assessment of
biases in data series and an improved estimation method. Paper to be presented at the XXVII
IUSSP International Population Conference, Busan, Republic of Korea.

An International Journal of Obstetrics and Gynaecology, 2001, 108:1237-45.

Curbera, F., Nagy, W. and Weerawaran, S. (2001). Web services. Why and How.

Estimates Using Full Birth Histories and Summary Birth Histories. PLoS Med 9(8): el 001296.
doi: 10.1371/journal.pmed.1001296

Gellersen, H. and Gaedke. (2005). An Object-Oriented Model for the Web Application
Development Process, IEEE Internet Computing.

Geoffrey Elliott & Josh Strachan (2004) Global Business Information Technology. p.87

Guillot M, Gerland P, Pelletier F, Saabneh A (2012) Child Mortality Estimation: A Global


Overview of Infant and Child Mortality Age Patterns in Light of New Empirical Data. PLoS Med
9(8): e1001299. doi:10.1371/journal.pmed.1001299

James Taylor (2004). Managing Information Technology Projects. p.39

Kingkade WW and Cheryl CC. Infant Mortality in Eastern Europe and the Former Soviet Union
Before and After the Breakup. Population Division, US Bureau of the Census, Washington, DC
20233. (Prepared for presentation at the 2001 Meetings of the International Union for the Scientific
Study of Population, Salvador de Bahia, Brazil, August 19-24. Available at
www.iussp.org/Brazil2001/s40/S44_02_kingkade.pdf)

Kramer MS et al. Registration Artifacts in International Comparisons of Infant Mortality.


Paediatric and Perinatal Epidemiology, 2002, 16 (Issue 1): p. 21.

Marakas, James A . O'Brien, George M (2010). Management information systems (10th ed.).
New York: McGraw-Hill/Irwin. pp. 485-489. ISBN 0073376817.

35
Parag C. Pendharkara, James A. Rodgerb, Girish H Subramanian (November 2008). ‘‘An
empirical study of the Cobb-Douglas production function properties of software development.

Post, G., & Anderson, D (2006). Management information systems: Solving business problems
with information technology. (4th ed.). New York: McGraw-Hill Irwin.

Radack. S. (n.d.). The system development life cycle (sdlc). Retrieved from
http://csrc.nist.gov/publications/nistbul/april2009 _system-development-life-cycle. pdf

Sawyer CC (2012) Child Mortality Estimation: Estimating Sex Differences in Childhood Mortality
since the 1970s. PLoS Med 9(8): e1001287. doi: 10.1371/joumal.pmed. l 001287

Silva R (2012) Child Mortality Estimation: Consistency of Under-Five Mortality Rate

U.S. House of Representatives (1999). Systems Development Life-Cycle Policy. p.13

UNAIDS. 2012 UNAIDS Report on the Global AIDS Epidemic. Geneva, UNAIDS, 2012.

Walker N, Hill K, Zhao F (2012) Child Mortality Estimation: Methods Used to Adjust for Bias
due to AIDS in Estimating Trends in Under-Five Mortality. PLoS Med 9(8): el 001298. Doi:
10.1371/journal.pmed.1001298

Workshop on object-Oriented Web Services OOPSLA Tampa, Florida, USA.

Zeitlin J and Wildman K. Indicators for Monitoring and Evaluating Perinatal Health in Europe.
European Union Health Monitoring Programme, 2000. (8) Graafmans WC et al. Comparability
of Published Perinatal Mortality Rates in Western Europe: The Quantitative Impact of Differences
in Gestational Age and Birthweight Criteria. BMOJ:

36
APPENDIX ONE: INTERVIEW

1. What is current system used in the hospital?

2. Are there any challenges with the existing system?

3. If any. What are the problems faced?

4. Give any suggestions on how the problems faced with the existing system can be
solved.

5. If the system is to be improved, what changes would you suggest to be made?

37
APPENDIX TWO: TIME/ACTIVITY SCHEDULES

Table 5 time frame

Activity Aug Sept Oct Nov Dec Jan Feb


Topic verification

Review relevant litterature of the topic proposal


writing and printing
Data collection process, data analysis and discussion

Data/ information processing

Final information, coding and editing

Preparation of draft report and final report

Submission of final report

38
APPENDIX THREE: BUDGET ESTIMATE

Table 6 BUDGET ESTIMATE

NO ITEM AMOUNT(Ugx)

1. photocopy 20.000

2. printing 40.000

3. binding 40,000

4. Transport 250.000

5. Internet 100.000

6. Airtime 50.000

TOTAL 500.000 Ugx

39
APPENDIX FOUR: SAMPLE CODE
<?php (6, 'Hoima'),
ob_start(); // Initiate the output buffer to avoid header (7, 'Gulu'),
problem while redirecting (8, 'Tororo'),
(9, 'Kiboga'),
// Start the session (10, 'Kotido'),
session_start(); (11, 'Ishaka'),
?> (12, 'Kiruwura'),
<!DOCTYPE html> (13, 'Moroto'),
<html> (14, 'Kuumi'),
<head> (15, 'Ntungamo'),
<title>BCIS</title> (16, 'Kasese');";
<link rel="stylesheet" type="text/css" $connection->query($sql);
href="bith.css"> }
<?php
// Database connection
require 'db.php'; ?>

?> <!--Navigation bar -->


<nav class="nav-extended light-blue accent-4">
<link
href="https://fonts.googleapis.com/icon?family=Mate <div class="nav-wrapper">
rial+Icons" rel="stylesheet"> <a href="#" class="brand-logo center">Birth
<!--Import materialize.css--> Registration System</a>
<link rel="stylesheet" href="materialize.min.css"> </div>

<!--Let browser know website is optimized for <div class="nav-content">


mobile--> <!-- tabs -->
<meta name="viewport" content="width=device- <ul class="tabs tabs-transparent">
width, initial-scale=1.0"/> <li class="tab">
<a class="active" href="#addAdmin">Add
<!--script for UI --> Admin</a>
<script type="text/javascript" src="jquery- </li>
3.2.1.min.js"></script> <li class="tab">
<script src="materialize.min.js"></script> <a href="#adminLogin">Admin Login</a>
</li>
</head> <li class="tab">
<body class="grey lighten-4"> <a href="#hospitalDataEntry">Hospital
Login</a>
<?php </li>
<li class="tab">
// Create city to store the details of cities <a href="#requestCertificate">Birth
$sql = "CREATE TABLE IF NOT EXISTS city ( Certificate Request Page</a>
cityID INT PRIMARY KEY, </li>
cityName VARCHAR(20) NOT </ul>
NULL UNIQUE </div>
);"; </nav>

if ($connection->query($sql)) { <!-- First Tab -->


$sql = "INSERT IGNORE INTO city VALUES <div id="addAdmin" class="col s12">
(1, 'Kampala'), <div class="container">
(2, 'Wakiso'), <div class="row">
(3, 'Jinja'), <form action="<?php echo
(4, 'Mityana'), htmlspecialchars($_SERVER["PHP_SELF"]); ?>"
(5, 'Mubende'), method="POST" autocomplete="off"

40
displayModal("Problem Signing in", setcookie("hospital_login_status",
"Username or Password incorrect!"); "logged_in", time() + (86400 * 30), "/"); // 86400 = 1
echo "<script type=\"text/javascript\"> day
window.location.href = 'index.php#adminLogin'; setcookie("hospital_user", $username,
</script>"; time() + (86400 * 30), "/");
} // Redirect to hospitalDataEntry page
} else { echo "<script type=\"text/javascript\">
// Failure window.location.href = 'hospitalDataEntry.php';
displayModal("Error", "Username doesn't </script>";
exists!"); } else {
echo "<script // Password don't match
type=\"text/javascript\">window.location.href = displayModal("Problem Signing in",
'index.php#adminLogin'; </script>"; "Username or Password incorrect!");
} echo "<script type=\"text/javascript\">
window.location.href =
} else { 'index.php#hospitalDataEntry'; </script>";
displayModal("Error", "Problem getting data }
from user"); } else {
echo "<script type=\"text/javascript\"> // Failure
window.location.href = 'index.php#adminLogin'; displayModal("Error", "Username doesn't
</script>"; exists!");
} echo "<script
} type=\"text/javascript\">window.location.href =
'index.php#hospitalDataEntry'; </script>";
}
/*
* hospitalLogin php } else {
* displayModal("Error", "Problem getting data
*/ from user");
echo "<script type=\"text/javascript\">
// When hospitalLoginSubmit button clicked window.location.href =
if (isset($_POST['hospitalLoginSubmit'])) { 'index.php#hospitalDataEntry'; </script>";
if (!(empty($_POST['hospitalUserName']) ||
empty($_POST['hospitalPassword']))) { }
$username = }
testInput($_POST['hospitalUserName']);
$password =
testInput($_POST['hospitalPassword']); /*
* birth certificate request page php
// Check if username and password is correct *
$sql = "SELECT `password` */
FROM `hospitals`
WHERE `username`=?;"; // When birthCertificateRequest button clicked
$result = $connection->prepare($sql); if (isset($_POST['birthCertificateRequest'])) {
$result->bind_param('s', $username); if (!(empty($_POST['childID']) ||
empty($_POST['hospitalID']) ||
if ($result->execute()) { empty($_POST['gender']) || empty($_POST['date']) ||
$result->store_result(); empty($_POST['time']) ||
empty($_POST['childName']) ||
// Store result in $storedPassword variable empty($_POST['fathersAadharNumber']) ||
$result->bind_result($storedPassword); empty($_POST['mothersAadharNumber']))) {
$result->fetch();
$childID = testInput($_POST['childID']);
if (password_verify($password, $hospitalID = testInput($_POST['hospitalID']);
$storedPassword)) { $gender = testInput($_POST['gender']);
// Success $date = testInput($_POST['date']);

42
$time = testInput($_POST['time']); WHERE aadharNo = ?";
$childName = testInput($_POST['childName']); $result = $connection->prepare($sql);
$fathersAadharNumber = $result->bind_param('s',
testInput($_POST['fathersAadharNumber']); $mothersAadharNumber);
$mothersAadharNumber = $result->execute();
testInput($_POST['mothersAadharNumber']);
$address = testInput($_POST['address']); // Get result from database
$res = $result->get_result();
// Check if hospital is selected or not
if ($hospitalID == "default") { // Convert it to associative array and get
displayModal("Error", "Please select the the name
Hospital"); $row = $res->fetch_assoc();
echo "<script type=\"text/javascript\"> $mother = $row['name'];
window.location.href =
'index.php#requestCertificate'; </script>"; // Get city
} else { $sql = "SELECT city.cityName
// Check if child is registered FROM hospitals, city
$sql = "SELECT childID WHERE hospitals.cityID =
FROM birth_details city.cityID AND
WHERE childID = ? AND username = ?";
gender = ? AND $result = $connection->prepare($sql);
dob = ? AND $result->bind_param('s', $hospitalID);
time = ? AND $result->execute();
fAadharNumber = ? AND
mAadharNumber = ? AND // Get result from database
hospital = ?"; $res = $result->get_result();
$result = $connection->prepare($sql);
$result->bind_param('issssss', $childID, // Convert it to associative array and get
$gender, $date, $time, $fathersAadharNumber, the name
$mothersAadharNumber, $hospitalID); $row = $res->fetch_assoc();
$city = $row['cityName'];
if ($result->execute()) {
$result->store_result(); // Store the details in session array which
if ($result->num_rows == 1) { is used to generate pdf
// If entered details are correct, generate $_SESSION["hospital"] =
the birth certificate pdf strtoupper($hospitalID);
// Get father's name $_SESSION["name"] = $childName;
$sql = "SELECT name $_SESSION["gender"] = $gender;
FROM aadhar $_SESSION["dob"] = $date;
WHERE aadharNo = ?"; $_SESSION["city"] = $city;
$result = $connection->prepare($sql); $_SESSION["fName"] = $father;
$result->bind_param('s', $_SESSION["mName"] = $mother;
$fathersAadharNumber); $_SESSION["address"] = $address;
$result->execute();
// Generate pdf
// Get result from database header('Location: pdf.php');
$res = $result->get_result(); } else {
// If details not found
// Convert it to associative array and get displayModal("Error", "Data entered is
the name not correct.");
$row = $res->fetch_assoc(); echo "<script type=\"text/javascript\">
$father = $row['name']; window.location.href =
'index.php#requestCertificate'; </script>";
// Get mother's name }
$sql = "SELECT name } else {
FROM aadhar

43
displayModal("Error", "Problem getting }
data from database"); });
echo "<script type=\"text/javascript\"> </script>
window.location.href =
'index.php#requestCertificate'; </script>"; <!--script for date and time picker -->
} <script>
} $('.datepicker').pickadate({
selectMonths: true,
} else { selectYears: 15, // Creates a dropdown of 15
// Error getting data years to control year,
displayModal("Error", "Problem getting data today: 'Today',
from user"); clear: 'Clear',
echo "<script type=\"text/javascript\"> close: 'Ok',
window.location.href = closeOnSelect: false // Close upon selecting a
'index.php#requestCertificate'; </script>"; date,
} });
}
$('.timepicker').pickatime({
default: 'now', // Set default time: 'now',
?> '1:30AM', '16:30'
fromnow: 0, // set default time to *
<?php milliseconds from now (using with default = 'now')
// Close database connection twelvehour: false, // Use AM/PM or 24-hour
$connection->close(); format
?> donetext: 'OK', // text for done-button
cleartext: 'Clear', // text for clear-button
<!-- if logged in, then redirect to respective pages --> canceltext: 'Cancel', // Text for cancel-button
<script type="text/javascript"> autoclose: false, // automatic close timepicker
function readCookie(name) { ampmclickable: true, // make AM PM clickable
var nameEQ = name + "="; aftershow: function () {
var ca = document.cookie.split(';'); } //Function for after opening timepicker
for (var i = 0; i < ca.length; i++) { });
var c = ca[i];
while (c.charAt(0) == ' ') c = c.substring(1, </script>
c.length);
if (c.indexOf(nameEQ) == 0) return <!-- script to open modal -->
c.substring(nameEQ.length, c.length); <script>
} $(document).ready(function () {
return null; $('.modal').modal();
} $('#modal1').modal('open');

$('a[href="#adminLogin"]').click(function () { });
</script>
var cookie_value =
readCookie('admin_login_status'); </body>
if (cookie_value === 'logged_in') { </html>
window.location = "addHospitals.php";
}
});
$('a[href="#hospitalDataEntry"]').click(function ()
{

var cookie_value =
readCookie('hospital_login_status');
if (cookie_value === 'logged_in') {
window.location = "hospitalDataEntry.php";

44

You might also like