Professional Documents
Culture Documents
PROJECT OVERVIEW
Background of the Study
Technology, in all phase of mans activities, has become a vital
factor in satisfying man in ending needs and in achieving desirable
outputs with less effort but with more comfort compared with doing it
through traditional ways. Modern technologies are designed to provide
an interesting, accessible, convenient and more manageable time for
the user to help them do their work much easier. Thus, technology has
a big role in stimulating peoples work and making work much reliable
and acceptable.
Jinan Fiaidhi (2010) mentioned that Information Technology (IT)
has become an integral part of everyday life. From commerce to
government
entertainment
to
scientific
and
discovery,
environmental
health
care,
management.
education,
Information
Project Overview | 2
Project Overview | 3
Project Overview | 4
Another
hospital,
the
Makati
Medical
Center
(MMC),
the
Project Overview | 5
Hospital
Information
Management
System
(HIMS)
after
Project Overview | 6
provide first aid, maternal and child health care, diagnosis of social
diseases, and other basic health services to all the members of the
community it is serving.
One of the concerns of Barangay San Nicolas Community Health
Center is how to reduce number of paper works in having a transaction
with
admission,
discharging of patients.
The proponents proposed a Community Health Information
System of Barangay San Nicolas, Pangasinan that is intended to solve
the problems discovered along the areas of patients medical records
and medicine inventory which is greatly affect the hospital medical
services. Through the proposed study, the community health center
can easily manage and maintain the patients information.
With the used of the proposed study it will eliminate or lessen
the problems concern of Barangay San Nicolas Community Health
Center.
Information
System
for
Barangay
San
Nicolas,
Villasis,
Project Overview | 7
Project Overview | 8
Project Overview | 9
the
Administrator
management,
Patient
management,
Project Overview | 10
and it can identify the items that are in a critical state. However, the
proponents limit the features of the proposed system to the
Midwife/Nurse and Barangay Health workers only.
The study does not include the scheduling of appointments and
room management.
Definition of Terms
In order to fully understand the proposed system the following
terms were defined operationally and conceptually.
Current System. It refers to the existing system of Barangay San
Nicolas Community Health Center, which is manual system.
Data Flow Diagram. A graphical illustration that shows the flow of
data in the system.
Documentation. Detailed information based on the process used
in creating the system.
End-user. The person that will be using the system.
In-Patient. It is a patient who is admitted to a hospital or clinic for
treatment that requires at least overnight stay.
Information System. It refers to the specific application software
that is used to store Patients records in a computer system and
automated some of the information processing activities in the Health
Center.
Brgy. San Nicolas Community Health Center Information System
Project Overview | 11
technology,
such
as
networking,
hardware,
software,
Information.
From
the
root
word
itself
Patient
It
is
an
agreement,
contract,
exchange,
Project Overview | 12
Chapter 2
METHODOLOGY
Software Development Methodology
A software development Methodology or a system development
methodology in a software engineering is a framework that is used to
structure, plan, and control the process of developing an information
system.
A wide variety of such framework have evolved over the years,
each of this has strengths and weaknesses. Each methodology is best
suited to specific kind of projects based on various technical,
organizational and team considerations.
Agile
Approach is
an
iterative,
team-based
approach
to
list
of
deliverables,
planned
one
sprint
in
advance.
Methodology | 13
used.
In
2012
the
AUP
was
superseded
by
Methodology | 14
Methodology | 15
in small programs called units, which are integrated in the next phase.
Each unit is developed and tested for its functionality; this is referred
to as Unit Testing. Unit testing mainly verifies if the module/units meet
their specifications.
In this phase, the proponents started the actual coding. The
proponents studied and separated the design into a set of programs or
program units. These programs are significant in creating the study.
The codes are combined and defined its functions. Each code had its
own functions in developing the system. The codes will be tested in the
next phase.
Test. Perform an objective evaluation to ensure quality. This
includes finding defects, validating that the system works as designed,
and verifying that the requirements are met.
From coding, the proponents tested the system. In this phase,
the proponents run the system. The proponents tested the functions of
each program code. The proponents checked the system and came up
with
result
that
is
already
successfully
met
the
required
Methodology | 16
system is
unique,
the
to
be
customized
according
to
specific
requirements
or
characteristics.
Configuration Management. Manage access to project artifacts.
This includes not only tracking artifact versions over time but also
controlling and managing changes to them.
In this phase, the proponents practice of handling changes
systematically so that a system maintains its integrity over time.
Proponents implements the policies, procedures, techniques, and tools
that are required to manage, evaluate proposed changes, track the
status of changes, and to maintain an inventory of system and support
documents as the system changes. Proponents programs and plans
provide technical and administrative direction to the development and
implementation
of
the
procedures,
functions,
services,
tools,
Methodology | 17
to
changing
customer
requirements.
Generally,
problems with the system developed come up after its practical use
starts, so the issues related to the system are solved after deployment
of the system.
Methodology | 18
Methodology | 19
related files to be acquainted with the type of records and files created
and maintained by the staff in the Health Center.
Observation. This method involves examining procedures as they
are carried out. The analyst observes how work and procedures are
carried out with the existing system, and this enables the analyst to
witness first-hand how the work is actually done and what it involves.
In this method, the proponents did some observations regarding the
current process of profiling information of the patients in the Health
Center on how the flow of the manual system, to point what areas are
to be improved or changed through own experiences of the proponents
to be precise in making an accurate, reliable, and efficient system to
be applied.
Library Research. Library research is conducted in a library in a
university, college library where people can search catalogs, stacks,
book or magazines, or microfiche looking for information on all kinds of
topics to include in theses. Good luck.
The proponents did some research from the book of stored in the
library authored by previous group who took up Bachelor of Science in
Information Technology served as a guide and reference material for
the proponents.
Sources of Data
Brgy. San Nicolas Community Health Center Information System
Methodology | 20
This part explains where and how the data that are needed for
the development were gathered and analyzed by the proponents to be
able to answer the problems encountered by their respective office.
The primary sources of data were derived from the response
midwife and clients of Barangay San Nicolas Community Health Center
during the interview.
Table 2.1 Distribution of Respondents
Name Of The Respondent
Midwife
Barangay Health Worker
Patient
Total
Frequency
1
5
10
16
Methodology | 21
Methodology | 22
Chapter 3
THE PROPOSED SYSTEM
Functional and Non-Functional Requirements
The functional requirement defines a function of a system and its
components. A function is described as a set of inputs, the behavior,
and outputs. Functional requirements may be calculations, technical
details,
data
manipulation
and
processing
and
other
specific
Functional Requirements
Functional requirements define the required behavior of the
system to be built, as reported by a hypothetical observer envisioning
that the future system will accept and the outputs it will produce in
response to those inputs. Functional requirements includes: (1) view all
user of the system; (2) delete accounts that register in the system; (3)
add patient and medical record; (4) update the patients record; (5) add
medicine; (6) update medicine inventory.
View all the user of the system. This requirements would allow
the administrator to view all the account of the user who access the
system.
Delete accounts
This
to
be
build,
other
than
functionality.
Non-functional
This
requirements
was
implemented
by
the
developer in this study for the entire user to access it with some
requirements or security to maintain the availability and maintenance
of the system. The availability was created to achieve the common
goals of the researcher.
In this system, a user must have a log-in name and a password,
and users can be managed added, deleted and updated. Different
users will have access to specific modules. For instance, a midwife will
have a wider scope of access, even to all the modules, as the one who
must have interface with the patients. There will be accounts that will
not have access to other modules but will be limited only to account
management. Updating is not limited to the medical secretary but is
also
possible
on
the
doctors
side
like
findings,
treatments,
information
which
is
relevant
for
the
patients
personal
information and will save to the database. Plate 3.5 shows the OutPatient Medical Record Adding Module.
are
the
recommended
hardware
and
software
Hardware Requirement
In
this
portion,
the
proponents
discussed
the
hardware
Specification
2.0 GHz processor
2 GB RAM or Higher
LCD monitor with at least
1366x768
PS2/USB mouse
At least 1GB Hard Disk free space
Software Requirement
Software requirements are for the project building environment
of the proposed study. Within these requirements, developers have
begun and built, run and test the system. These are set of software
requirements for the configurations. And installations that have to be
configured and installed in the computer in order to use and access the
study.
Table 3.2 Software Requirements
Software Requirements
Programming
Operating System
Graphics/Design
Database
Specifications
Microsoft Visual Studio 2010
.Net Framework 2.0
Windows 7 / Windows Vista
Adobe Flash Professional CS5
Mysql
Appendices
Appendix A
Communication Letter
Appendix B
Appendices | 41
Sample Form
Appendices | 42
Appendix C
Gantt chart
LEGEND:
Done
Ongoing
Appendix D
Brgy. San Nicolas Community Health Center Information System
Appendices | 43
Appendix E
Appendices | 44
Use Case
Appendix F
Appendices | 45
Appendices | 46
Appendices | 47
Appendices | 48
Appendices | 49
Appendices | 50
Appendices | 51
Appendix G
Database Schema
Table G.1 Database Schema
Table Name
Attributes
infantmedanddia Id (Primary Key)
g
PRPerMin,
RRPerMin,
Temperature,
Medicine,
Dosage, Quantity, Immunization, IDosage, Findings,
ChiefComplain
infantpatientinfo InfantId (Primary Key)
Lastname,
Firstname,
Middlename,
Gender,
BirthDate, Age, Address, FLastName, FFirstname,
FMiddlename, FAge, MLastname, MFirstname,
MMiddlename,
MAge,
FPoB,
FContactNo,
FOccupation, FNationality, MPoB, MContactNo,
MOccupation, MNationality,FHH
meds
Id (Primary Key)
InfantId (Foreign Key)
PatientId (Foreign Key)
PregId (Foreign Key)
Med_Name, Med_Dosage, Med_Quantity
outmedanddiag5 Id (Primary Key)
PatientId (Foreign Key)
PRPerMin,
RRPerMin,
Temperature,
Medicine,
Dosage,
Quantity,
FindingsAndDiagnosis,
ChiefComplain
outpatientinfo
PatientId (Primary Key)
Lastname,
Firstname,
Middlename,
Gender,
CivilStatus,
BirthDate,
Age,
Address,
PoB,
Nationality,
Occupation,
ContactNo,
Drinking,
Smoking
pregmedanddiag Id (Primary Key)
PregId (Foreign Key)
PRPerMin,
RRPerMin,
Temperature,
Medicine,
Dosage,
Quantity,
FindingsAndDiagnosis,
ChiefComplain
pregnantpatienti PatientId (Primary Key)
nfo
Lastname,
Firstname,
Middlename,
Gender,
CivilStatus,
BirthDate,
Age,
Address,
PoB,
Nationality, Occupation, ContactNo, AOG, EDD,
NoLB, NoSB, Drinking, Smoking, FHH
Appendices | 52
tbluser
Appendix H
Database Instance
Table H.1 User
Field Name
Datatype
UserId
int(11) AI PK
Firstname
Lastname
Email
varchar(50)
varchar(50)
varchar(50)
UserRole
varchar(20)
Username
Password
varchar(20)
varchar(20)
int(10) AI PK
Lastname
Firstname
varchar(50)
varchar(50)
Middlename
varchar(50)
Gender
varchar(10)
CivilStatus
varchar(10)
Birthdate
Age
Address
varchar(20)
int(5)
varchar(150)
PoB
varchar(150)
Nationality
Occupation
varchar(20)
varchar(20)
Description
Primary key & User
id
Users First Name
Users Last Name
Users Email
Users Level of
Security
Users Username
Users Password
Description
Primary Key &
Patient Id
Patients Last Name
Patients First Name
Patients Middle
Name
Patients Gender
Patients Civil
Status
Patients Birth Date
Patients Age
Patients Address
Patients Place of
Birth
Patients Nationality
Patients
Appendices | 53
ContactNo
varchar(20)
int(10) AI PK
PatientId
int(11) FK
BloodPressure
int(10)
PRPerMin
int(10)
RRPerMin
int(10)
Temperature
int(10)
Medicine
varchar(20)
Dosage
varchar(20)
Quantity
varchar(5)
FindingsAndDiagnosis
varchar(255)
ChiefComplain
varchar(255)
Datatype
Id
int(2) AI PK
InfantId
PatientId
int(11) FK
int(11) FK
PregId
int(11) FF
Med_Name
Med_Dosage
Med_Quantity
varchar(100)
varchar(50)
int(5)
Occupation
Patients Contact
Number
Description
Primary Key &
Medical Record Id
Foreign Key &
Patients Id
Patients Blood
Pressure
Patients Pulse
Rate
Patients
Respiratory Rate
Patients
Temperature
Patients Prescribe
Medicine
Patients Medicine
Dosage
Patients Medicine
Quantity
Patients Diagnosis
Patients Chief
Complain
Description
Primary Key &
Medicine Id
Infants Patient Id
Patients Id
Pregnant Patients
Id
Medicine Name
Medicine Dosage
Medicine Quantity
Appendices | 54
Field Name
Datatype
PregId
int(10) AI PK
Lastname
varchar(50)
Firstname
varchar(50)
Middlename
varchar(50)
CivilStatus
varchar(10)
Birthdate
varchar(10)
Age
int(5)
Address
varchar(150)
PoB
varchar(150)
Occupation
varchar(20)
Nationality
varchar(20)
ContactNo
varchar(15)
LastMens
varchar(10)
AOG
varchar(10)
EDD
varchar(10)
NoLB
varchar(5)
NoSB
varchar(5)
FHH
varchar(255)
Description
Primary Key &
Pregnant Patient Id
Pregnant Patients
Last Name
Pregnant Patients
First Name
Pregnant Patients
Middle Name
Pregnant Patients
Civil Status
Pregnant Patients
Birth Date
Pregnant Patients
Age
Pregnant Patients
Address
Pregnant Patients
Place of Birth
Pregnant Patients
Nationality
Pregnant Patients
Occupation
Pregnant Patients
Contact Number
Pregnant Patients
Last Menstrual
Period
Pregnant Patients
Age of Gestation
Pregnant Patients
Expected Date of
Delivery
Pregnant Patients
Number of Live
Birth
Pregnant Patients
Number of Still
Birth
Pregnant Patients
Family Health
History
Appendices | 55
int(11) AI PK
Lastname
varchar(50)
Firstname
varchar(50)
Middlename
varchar(50)
Gender
varchar(10)
Birthdate
varchar(15)
Age
varchar(5)
Address
varchar(150)
FLastname
varchar(50)
FFirstname
varchar(50)
FMiddlename
varchar(50)
FAge
varchar(5)
MLastname
varchar(50)
MFirstname
varchar(50)
MMiddlename
varchar(50)
MAge
varchar(5)
FPoB
varchar(150)
FContactNo
varchar(15)
FOccupation
varchar(20)
Description
Infant Primary Key
& Patient Id
Infant Patients Last
Name
Infant Patients First
Name
Infant Patients
Middle Name
Infant Patients
Gender
Infant Patients
Birth Date
Infant Patients Age
Infant Patients
Address
Infant Patients
Father Last Name
Infant Patients
Father First Name
Infant Patients
Father Middle
Name
Infant Patients
Father Age
Infant Patients
Mother Last Name
Infant Patients
Mother First Name
Infant Patients
Mother Middle
Name
Infant Patients
Mother Age
Infant Patients
Father Place Of
Birth
Infant Patients
Father Contact
Number
Infant Patients
Father Occupation
Appendices | 56
FNationality
varchar(20)
MPoB
varchar(150)
MContactNo
varchar(15)
MOccupation
varchar(20)
MNationality
varchar(20)
FHH
varchar(255)
int(11) AI PK
PRPerMin
varchar(10)
RRPerMin
varchar(10)
Temperature
varchar(10)
Medicine
varchar(20)
Dosage
varchar(10)
Quantity
varchar(10)
Immunization
varchar(20)
IDosage
varchar(10)
Findings
varchar(255)
ChiefComplain
varchar(255)
Infant Patients
Father Nationality
Infant Patients
Mother Place Of
Birth
Infant Patients
Mother Contact
Number
Infant Patients
Mother Occupation
Infant Patients
Mother Nationality
Infant Patients
Family Health
History
Description
Infant Primary Key
& Medical Record Id
Infant Patients
Pulse Rate
Infant Patients
Respiratory Rate
Infant Patients
Temperature
Infant Patients
Prescribe Medicine
Infant Patients
Medicine Dosage
Infant Patients
Medicine Quantity
Infant Patients
Prescribe
Immunization
Infant Patients
Medicine Dosage
Infant Patients
Diagnosis
Infant Patients
Chief Complain
Appendices | 57
int(11)
BloodPressure
varchar(10)
PRPerMin
RRPerMin
varchar(10)
varchar(10)
Temperature
varchar(10)
Medicine
varchar(20)
Dosage
varchar(10)
Qty
varchar(10)
Findings
varchar(255)
Description
Primary Key &
Medical Record Id
Foreign Key &
Pregnant Patients
Id
Patients Blood
Pressure
Patients Pulse Rate
Patients
Respiratory Rate
Patients
Temperature
Patients Prescribe
Medicine
Patients Medicine
Dosage
Patients Medicine
Quantity
Patients Diagnosis