BSNCHCIS.doc

Chapter 1

PROJECT OVERVIEW

Background of the Study

Technology, in all phase of man’s 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 people’s 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 to scientific discovery, health care, education,

entertainment and environmental management. Information

Technology is indispensable and will continue to fuel further advances

in all facets of human endeavors. At the same time IT provides a

powerful foundation for tackling many problems that we face in the

21st century. These includes data modelling and prediction to help

manage deforestation of resource exploration. The people witnessed

rapid advances in IT recent years, and further advances in IT will help

solve many problems in the future.

Project Overview | 2

In addition, (L.Schneider et al, 2009) said that computerization

becomes a major contribution to the growth of many nations in the

world. Computers do things fast especially in acquiring and managing

information. The success of organization depends on its ability to

acquire accurate and timely data about its operation, to manage this

data effectively, and to analyse its own activities for decision making

purpose.

Computers are also used in the various fields of specialization

most especially in medical researches, patient records. The computers

are used in preparing inventories of drugs and medical equipment.

According to Kavita Medical Centre, Lucknow (K. M. C) is a

prestigious hospital situated in the heart of HazratGanj, Lucknow, India

with a very large patient capacity. Its rich medical store serves to the

purpose of the medicines of the patients who visit the hospital. The

medical store is facing problems in maintaining its inventory and

keeping its relations up-to-date with its suppliers. The medical store

issues medicines to the patients and also receives the unused

medicines in good condition from the patients to minimize wastage.

With increasing number t patients this record keeping has become a

burden and is no longer sustainable with the current manual system.

It, therefore, badly needs an improved and efficient computerized

system for maintaining its inventory and purchase activities.

Brgy. San Nicolas Community Health Center Information System


The hospital treats both indoor patients and outdoor patients. It

has to maintain full information of the indoor patients as well as

outdoor patients for the purpose of historical use. Doctors who serve to

the hospital are the regular employees of the hospital; however,

sometimes external doctors are used to handle complicated cases. So

the hospital needs to maintain its doctor’s records separately along

with the records of its other employees. All these operations are

getting unmanageable day by day because of their stiff rise in data.

The senior management of the hospital invest into a computerized

hospital management and information system which keep the records

of its patients, employees, medical store, doctors etc. and also to able

handle its complete accounting.

In the Philippines setting, the computing history of the Philippine

Heart Center has proven its capacity to maintain its vision to be

premiere institution to take care of the cardiovascular problems and

related disease. Ever since, it has constantly expanded and utilized

technology in providing better services to its clientele. The Philippine

Heart Center for Asia (PHCA) has been using a computer for its

business operations, particularly for its patients billing. With the

purchase of its first general-purpose computer, programs were

developed to automate the process of Discharging of Check-up

Package/Medical Patients, Notice of Directory (G. Manzano et al, 2007).



Another hospital, the Makati Medical Center (MMC), the

Philippines premier hospital started operations in 1969, and is now a

469-bed tertiary hospital that provides sophisticated diagnostic,

medical and surgical facilities. With patient wellness in mind, they

provide high-quality healthcare services through integrated specialty

centers operated by highly qualified physicians and nurses, as well as

technical and management staff, sustained by well-developed research

and training programs and enabled by state-of-the-art professional

equipment and specialized tools. MMC upgraded their HMIS to further

improve the quality service both its patients and hospital professionals

(Indra IT multinational, 2012).

Meanwhile at province hospitals, the Nazareth General Hospital

is one of the competitive hospital in Dagupan City that provides state

of the art medical equipment, better and sufficient services and well

trained medical personnel. The institution always aims to be the edge

of technology and opportunities for enhancement and change. This

institution has grabbed the opportunity of its technology compliance

for patients with the computer based system. The online Patient’s

Information System with Computerized Medical Transcription provides

better solutions on the current procedures of the hospital’s personnel

and generate a long term benefits between their patients and clients

(B. Almerol, 2007).



Urdaneta Sacred Heart Hospital is the largest private hospital in

Eastern Pangasinan. In the year 2008, Urdaneta Sacred Heart acquired

the Hospital Information Management System (HIMS) after

encountering problems from the past years. HIMS is a comprehensive

solution that automates the clinical, administrative and supply-chain

function and enables the healthcare provides to improve operational

effectiveness, consequently reducing cost and medical errors, while

enhancing quality of care. HIMS cover billing and administration,

clinical systems, supply chain modules and business intelligence. The

clinical system comprises an electronic patient record which forms the

core of the system and links all other departments in the hospital.

Hospital Management System includes discharge summary with

reports or diagnostic test, vitals, doctor’s notes along with medication

administered and billing information (Reyes et.al. 2009).

Furthermore, Patients Information System of Region 1 Medical

Center is utilized as part of the study regarding usability of the system.

The system covers the in-patient and out-patient registration, medical

records, medical report and survey of diseases. The system evaluated

by using the usability questionnaire or WAMMMI or Website Analysis

and Measurement Inventory (A. Jestoni, 2007)

The Barangay Health Center in San Nicolas, Villasis, Pangasinan

is a community-based and patient-directed organization. Its goal is to



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 the patient that could fasten the process of 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 patient’s information.

With the used of the proposed study it will eliminate or lessen

the problems concern of Barangay San Nicolas Community Health

Center.

Statements of the Objectives

The main objective of the study is to develop a Community

Health Information System for Barangay San Nicolas, Villasis,

Pangasinan that would relieve the Community Health Center in

accuracy and deficiencies of records.



The study will provide faster and easier process which in turn would

lead on improved services to the patients.

1. Determine the current process of health center along the

following areas:

a. Adding Patient’s Information

b. Editing Patient’s Information

c. Searching Patient’s Records

d. Backing-up patient’s medical records

e. Medicine inventory

2. Identify the problems encountered in the existing process of

health center along the following areas:

a. Adding Patient’s Information

b. Editing Patient’s Information

c. Searching Patient’s Records

d. Backing-up patient’s medical records

e. Medicine inventory

3. Specify the Functional and Non-Functional Requirements of the

proposed system.

4. Identify the System Requirements and Specification of the

proposed system.

Importance of the Study



The Barangay San Nicolas Community Health Center Information

System will not only be beneficial to the organization but also to the

patients and the institution. In undertaking this proposed study, the

proponents also take consideration to the other beneficiaries as well.

To Community Health Center. This proposed system once

implemented will not only promote the institution as a highly

competitive institution when it comes to information technology but

also help in promoting health care. They will have a fast and reliable

data presented to the patients.

To the Barangay Health Worker. The system could be of great

help to the Barangay San Nicolas, Villasis, Pangasinan Health Center

especially to the Barangay Health Workers. The previously stated

problem encountered in use of manual system would be addressed

levelling the quality and standard of their work, meeting the patient’s

expectation and needs. These would boost their performance bringing

the better service and causing a constant and consistent progress.

To the Patient. This will help the patient have a faster transaction

on different processes in Barangay Community Health Center.

To the Proponents. Through the proposed system, the

proponents will be able to learn not just by theories but through

applications. The proposed study allowed the proponents to determine



the appropriate methodology, tools and features in developing a

system.

To the Future Proponents. In undertaking this proposed system,

the proponents also take in consideration the future students who will

undertake the same proposed study or related studies and use for their

future references.

Scope and Delimitations

The main purpose of the proposed system is to develop an Information

System of Barangay San Nicolas Community Health Center and to

enhance the company’s performance in giving a quality service to the

people.

This study focuses primarily on monitoring patient’s information

including the Administrator management, Patient management,

Medical record and Inventory Management. The system generates

reports to monitor the number of in-patient and out-patient records

and searching patient’s profile/records such as patient’s visit history

and medical records. The system generates reports to monitor the

number of in-patient and out-patient every day.

On the other hand, medicine inventory are also included in the

proposed system wherein it can monitor the stocks of the medicine



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.



Information Technology. It refers to anything related to the

computer technology, such as networking, hardware, software,

internet, or the people that work with these technologies.

Manual System. A system involving data processing which does

not make use of stored-program equipment.

Medical Records. It refers to the systematic documentation of a

single patient’s medical history and care across time within one

particular health care provider’s jurisdiction.

Out-Patient. It is a person who is admitted to the hospital or clinic

that does not require an overnight stay.

Patient. It refers to any recipient of health care services, it is

often ill or injured and in need of treatment by a physician.

Patient Information. From the root word itself “Patient

Information”, it is the information of the patients that will be needed on

every transactions.

Record. It is a collection of data, a collection of related items of

information treated as unit by a computer.

System. Is a set of interacting or interdependent components

forming an integrated whole.

Transaction. It is an agreement, contract, exchange,

communication, or transfer of cash that occurs between two or more

parties and establishes a legal obligation. It also refers in an action



that adds, removes, or changes data in a database or in the proposed

study.


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

development. This approach emphasizes the rapid delivery of an

application in complete functional components. Rather than creating

tasks and schedules, all time is “time-boxed” into phases called

“sprints.” Each sprint has a defined duration (usually in weeks) with a

running list of deliverables, planned one sprint in advance.

Deliverables are prioritized by business value as determined by the

customer. If all planned work for the sprint cannot be completed, work

is reprioritized and the information is used for future sprint planning.

As work is completed during each sprint, it is continuously reviewed

and evaluated by the customer, who may be considered the most

Methodology | 13

critical member of the agile team. As a result, Agile relies on a very

high level of customer involvement throughout the project.

The proponents start off with a simplistic project design, and

then begin to work on small modules. The work on these modules is

done in weekly or monthly sprints, and at the end of each sprint,

project priorities are evaluated and tests are run. These sprints allow

for bugs to be discovered, and customer feedback to be incorporated

into the design before the next sprint is run.

The process, with its lack of initial design and steps, is often

criticized for its collaborative nature that focuses on principles rather

than process.

Agile Unified Process (AUP) is a simplified version of the Rational

Unified Process (RUP) developed by Scott Ambler. It describes a simple,

easy to understand approach to developing business application

software using agile techniques and concepts yet still remaining true

to the RUP. The AUP applies agile techniques including test-driven

development (TDD), Agile Modeling (AM), agile change management,

and database refactoring to improve productivity.

In 2011 the AUP accounted for one percent of all the Agile

Methodologies used. In 2012 the AUP was superseded by

Disciplined (DAD). Since then work has ceased on evolving AUP.


http://en.wikipedia.org/wiki/Database_refactoring

http://en.wikipedia.org/wiki/Agile_Modeling

http://en.wikipedia.org/wiki/Test-driven_development

http://en.wikipedia.org/wiki/Test-driven_development

http://en.wikipedia.org/wiki/Scott_Ambler

http://en.wikipedia.org/wiki/Rational_Unified_Process

http://en.wikipedia.org/wiki/Rational_Unified_Process

Methodology | 14

Figure 2.1 Agile Unified Process

Model. Understand the business of the organization, the problem

domain being addressed by the project, and identify a viable solution

to address the problem domain.

In this phase, the proponents conducted initial data gathering to

determine the client’s needs with the use of the existing system and to

define the objectives of the proposed system. The proponents went to

the Health Center to interview the Midwife and observe them while

they are having their transactions with their clients. The proponents

ask for the list of medicines and also the copy of their patient’s list. The

proponents surf the internet to look for some information related to the

proposed system. The proponents were required to gather all possible

data during this phase in order to properly design the system.

Implementation . Transform model(s) into executable code and

perform a basic level of testing, in particular unit testing.

On receiving system design documents, the work is divided in

modules/units and actual coding is started. The system first developed


http://en.wikipedia.org/wiki/Unit_testing

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 a result that is already successfully met the required

specifications. The system can now be delivered to the Health Center

and will be maintain in the last phase of the model.

Deployment . Plan for the delivery of the system and to execute

the plan to make the system available to end users.


Methodology | 16

In this phase, the proponents studied that these activities can

occur at the producer side or at the consumer side or both. Because

every software system is unique, the

precise processes or procedures within each activity can hardly be

defined. Therefore it should be interpreted as a general process that

has 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,

processes, and resources required to successfully develop and support

a complex system.

Project Management . Direct the activities that take place within

the project. This includes managing risks, directing people (assigning


http://en.wikipedia.org/wiki/Project_Management

http://en.wikipedia.org/wiki/System

http://en.wikipedia.org/wiki/Configuration_Management

http://en.wikipedia.org/wiki/Algorithm

http://en.wikipedia.org/wiki/Process_(computing)

http://en.wikipedia.org/wiki/Software_system

http://en.wikipedia.org/wiki/User_(computing)

Methodology | 17

tasks, tracking progress, etc.), and coordinating with people and

systems outside the scope of the project to be sure that it is delivered

on time and within budget.

In this phase, the proponents execute projects effectively and

efficiently.

Environment . Support the rest of the effort by ensuring that the

proper process, guidance (standards and guidelines), and tools

(hardware, software, etc.) are available for the team as needed.

In this phase, it is intended to improve software quality and

responsiveness 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.

Data Gathering Techniques

This identifies the details of the system functions such as: the

people who are involved, the business activity that had taken place,

and on the system procedures had been performed.

Interview. An interview is "a formal face-to-face meeting,

especially, one arranged for the assessment of the qualifications of an

applicant, as for employment or admission.... A conversation, as one


Methodology | 18

conducted by a reporter, in which facts, or statements are elicited from

another." (The American Heritage Dictionary, Second College Edition)

The proponents prepared a request letter signed by the team’s adviser

and also signed by the dean of the College of Computer Studies,

addressed to the Barangay Health Center of San Nicolas to conduct an

interview to the Midwife and Barangay Health Workers of the Health

Center on how the process and flow of the system will going to work,

and on how the Health Center can be a part of the system. The

proponents used this method to gather relevant information from the

Head Nurse/Midwife together with the Barangay Health Workers, and

some patients from Barangay San Nicolas Community Health Center.

Data Analysis. Is a process of inspecting, cleaning, transforming,

and modeling data with the goal of discovering useful information,

suggesting conclusions, and supporting decision-making. Data analysis

has multiple facets and approaches, encompassing diverse techniques

under a variety of names, in different business, science, and social

science domains.

This method of data gathering was made through analyzing the

information gathered in early collection of files used in the manual

system. The proponents gathered manual forms such as out-patient

medical records, admission/discharge forms, information file and other


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


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 FrequencyMidwife 1Barangay Health Worker 5Patient 10Total 16

Tools for Data Analysis

Data analysis is the process of evaluating data using analytical

and logical reasoning to examine each component of the data

provided. The following are the tools for the proponents will be using:

Use Case Diagram. Use Case Diagram is a graphic depiction of

the interactions among the elements of a system which provides a

crystal clear presentation which enable the system analyst to see all

the user goals (use cases) and related and-users (actors).

The proponents used this because it is simple and easy to

understand that it can portray the different types of users in a system

in a approachable manner and to get the various ways that will enable


Methodology | 21

interaction with the system. Then, helping the proponents come up

with an overall view of the system.

Gantt chart. A Gantt chart is a type of bar chart, developed by

Henry Gantt in the 1910s, that illustrates a project schedule. Gantt

charts illustrate the start and finish dates of the terminal elements and

summary elements of a project. Terminal elements and summary

elements comprise the work breakdown structure of the project.

This tool will help the proponents to create a chart to show the

scheduled and completed work over a period of time wherein the

proponents will make a time frame from start date, duration and end

date of the activities for the proposed system.

Entity-Relationship Diagram. An entity-relationship diagram to a

data modelling technique that creates a graphical representation of

the entities, and the relationships between entities, within an

information system (Rouse, 2007).

The proponents utilized this because it is easy to use with

regards on describing the database relation. Furthermore, with the

help of this tool, the proponents can provide images on how the tables

should connect, and what fields are going to be on each table.

Data Flow Diagram. The data flow diagram is a graphical

representation of the data flow through an information system. It

enables you to represent this process in your information systems from


Methodology | 22

the viewpoint of data. It lets you visualize how the system operates,

what system accomplishes and how it will be implemented, when it is

refined with further specification.

The proponents usually begin withdrawing a context diagram, a

simple representation of the whole system. To elaborate further from

that, proponents drill down to a level 1 diagram with additional

information about the major functions of the system. This could

continue to evolve to become a level 2 diagram when further analysis

is requirements.

Database Schema. Is a collection of meta-data that describes the

relations in a database. A schema can be simply described as the

"layout" of a database or the blueprint that outlines the way data is

organized into tables. Schema are normally described using SQL as a

series of create statements that may be used to replicate the schema

in a new database (M. Chapple, 2014).

This tool will help the proponents to create a blueprint on how to

construct or develop the database of the system.


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

functionality that define what a system is supposed to accomplish.

Behavioral requirements describing all the cases where the system

uses the functional requirements are captured in use cases.

The non-functional requirement is a requirement that specifies

criteria that can be used to judge the operation of a system, rather

than specific behaviors. This should be contrasted with functional

requirements that define specific behavior or functions. The plan for

implementing functional requirements is detailed in the system design.

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)

http://en.wikipedia.org/wiki/Systems_design

http://en.wikipedia.org/wiki/Functional_requirements

http://en.wikipedia.org/wiki/Functional_requirements

http://en.wikipedia.org/wiki/Requirement

http://en.wikipedia.org/wiki/Use_case

http://en.wikipedia.org/wiki/System

The Proposed System | 24

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 that are registered in the system. This

requirements would allow the administrator to delete an existing

account in the system.

Add patient and medical record. This requirements would allow

the user to add patient and its medical record in the system.

Update the patient medical record. This requirements would

allow the user update the patient’s record.

Add medicine. This requirements would allow the user to add

medicine in the inventory system.

Update the medicine inventory. This requirements would allow

the user update the medicine inventory.

Non-Functional Requirements

Non-functional requirements specify additional properties of the

system to be build, other than functionality. Non-functional

requirements can be subcategorized into categories such as external

interface requirements, performance requirements, design constraints,

logical database requirements, and ‘characteristics” that don’t fit



neatly unto any of the other categories. Non-functional requirements

include: (1) security; (2) performance; and (3) maintainability.

Security. The develop system has security module to avoid

unauthorized access of system.

Performance. (1) Response time – application loading, screen

open and refresh times, etc. (2) Processing times – functions, imports,

exports. (3) Query and Reporting times – initial loads and subsequent

loads.

Maintainability. Conformance to architecture standards – what

are the standard it needs to conform to or have exclusion from?

Availability. 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 doctor’s side like findings, treatments,

prescriptions, consultation. Plate 3.1 shows the Create Account

Module.

Plate 3.1 Create Account Module

This plates show where the admin can create username and

password for the user of the system. Plate 3.2 shows the Log-In

Module.



Plate 3.2 Log-In Module

This is the log in module. There are 3 types of users in this

system: the Administrator, the Midwife and the BHW. The user must

enter a valid username and password before the user can start using

the system. Plate 3.3 shows the main menu form. Plate 3.3 shows the

Main Module.



Plate 3.3 Main Module

This is the main module of the system. It will appear after a

successful login. The five buttons on the left of the page is a

navigation that is use to access different forms of the system. On right

top is a log out text. Once the user clicks it, the main page will be

closed and the login module will be displayed. The exit button on the

right side is a function that closes the system once it is clicked. Plate

3.4 shows the Create Out-Patient Adding Module.



Plate 3.4 Out-Patient Adding Module

This plate show where the user will fill up for the patient’s

information such as the last name, first name, middle name, gender,

birthday, age, address place of birth, nationality, contact no. and other

basic information which is relevant for the patient’s personal

information and will save to the database. Plate 3.5 shows the Out-

Patient Medical Record Adding Module.



Plate 3.5 Out-Patient Medical Record Adding Module

This plate shows the adding of medical diagnosis and

medicine record for the patient. The medical diagnosis is consist of the

findings about the patient’s current condition. The medical records is

the complete information about the patient’s blood pressure, pulse

rate, respiratory rate, temperature, prescribe medicine. Plate 3.6

shows the Out Patient’s Medical Record Module.



Plate 3.6 Out Patient’s Medical Record Module

This plate shows the patient information. Personal and

medical information. In order to access the desired information he

must first search using the last name or the id no. of the patient. After

searching the patient basic information and medical records will be

show. The medical records is consists of the patient’s blood pressure,

pulse rate, respiratory rate, temperature, prescribe medicine, chief

complain, findings and diagnosis. Plate 3.7 shows the Pregnant Patient

Adding Module.



Plate 3.7 Pregnant Patient Adding Module



birthday, age, address place of birth, nationality, contact no., last

menstruation period, age of gestation (A.O.G.) and other basic

information which is relevant for the patient’s personal information

and will save to the database. Plate 3.8 shows the Pregnant Patient

Medical Record Adding Module.



Plate 3.8 Pregnant Patient Medical Record Adding Module

This plate shows the adding of medical diagnosis and medicine

record for the patient. The medical diagnosis is consist of the findings

about the patient’s current condition. The medical records is the

complete information about the patient’s blood pressure, pulse rate,

respiratory rate, temperature, prescribe medicine. Plate 3.9 shows the

Pregnant Patient’s Medical Record Module.



Plate 3.9 Pregnant Patient’s Medical Record Module

This plate shows the patient information. Personal and medical

information. In order to access the desired information he must first

search using the last name or the id no. of the patient. After searching

the patient basic information and medical records will be show. The

medical records is consists of the patient’s blood pressure, pulse rate,

respiratory rate, temperature, prescribe medicine, family health

history, no. of live birth, no. of still birth, chief complain, findings and

diagnosis. 3.10 shows the Infant Patient Adding Module.



Plate 3.10 Infant Patient Adding Module



birthday, age, address place of birth, nationality and other basic

information which is relevant for the patient’s personal information

and will save to the database. 3.11 shows the Infant Patient Medical

Record Adding Module.



Plate 3.11 Infant Patient Medical Record Adding Module

This plate shows the adding of medical diagnosis and medicine

record for the infant patient. The medical diagnosis is consist of the

findings about the patient’s current condition. The medical records is

the complete information about the patient’s blood pressure, pulse

rate, respiratory rate, temperature, prescribe medicine. 3.12 shows the

Infant Patient’s Medical Record Module.



Plate 3.12 Infant Patient’s Medical Record Module

This plate shows the patient information. Personal and medical

information. In order to access the desired information he must first

search using the last name or the id no. of the patient. After searching

the patient basic information and medical records will be show. The

medical records is consists of the patient’s blood pressure, pulse rate,

respiratory rate, temperature and prescribe medicine. 3.13 shows the

Infant Patient’s Medical Record Module.



Plate 3.13 Adding of Medicne Module

This plate show the user will fill up for the adding

information of medicine and together the quantity and dosage of a

certain medicine in the inventory and will save to the database.

System Requirements and Specification

Following are the recommended hardware and software

requirements to use in the proposed system entitled Brgy. San Nicolas

Community Health Center Information System.



Hardware Requirement

In this portion, the proponents discussed the hardware

requirements and specification. These requirements ensure the quality

of performance that the system will performed.

Table 3.1 Hard Requirements

Computer Hardware Components SpecificationProcessor 2.0 GHz processorMemory 2 GB RAM or HigherMonitor LCD monitor with at least

1366x768Keyboard/Mouse PS2/USB mouseHard Drive 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 SpecificationsProgramming Microsoft Visual Studio 2010

.Net Framework 2.0Operating System Windows 7 / Windows VistaGraphics/DesignDatabase

Adobe Flash Professional CS5Mysql


Appendices

Appendix A

Communication Letter

Appendix B

Appendices | 41

Sample Form

Appendix C


Appendices | 42

Gantt chart

LEGEND:

Done

Ongoing

Appendix D

Entity Relationship Diagram


Appendices | 43

Appendix E

Use Case


Appendices | 44

Appendix F

Data Flow Diagram


Appendices | 45

Context Data Flow Diagram of the Proposed System


Appendices | 46

Top Level Diagram of the Proposed System


Appendices | 47

Exploded Diagram of Administrator Management


Appendices | 48

Exploded Diagram of Patient Information Management


Appendices | 49

Exploded Diagram of Medical Record Management


Appendices | 50

Exploded Diagram of Inventory Management


Appendices | 51

Appendix G

Database Schema

Table G.1 Database SchemaTable Name Attributesinfantmedanddiag

Id (Primary Key)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

pregnantpatientinfo

PatientId (Primary Key)Lastname, Firstname, Middlename, Gender, CivilStatus, BirthDate, Age, Address, PoB, Nationality, Occupation, ContactNo, AOG, EDD, NoLB, NoSB, Drinking, Smoking, FHH


Appendices | 52

tbluser UserId (Primary Key)Firstname, Lastname, Email, UserRole, Username, Password

Appendix H

Database Instance

Table H.1 UserField Name Datatype Description

UserId int(11) AI PKPrimary key & User id

Firstname varchar(50) User’s First Name Lastname varchar(50) User’s Last Name Email varchar(50) User’s Email

UserRole varchar(20)User’s Level of Security

Username varchar(20) User’s UsernamePassword varchar(20) User’s Password

Table H.2 Out-Patient InformationField Name Datatype Description

PatientId int(10) AI PKPrimary Key & Patient Id

Lastname varchar(50) Patient’s Last NameFirstname varchar(50) Patient’s First Name

Middlename varchar(50)Patient’s Middle Name

Gender varchar(10) Patient’s Gender

CivilStatus varchar(10)Patient’s Civil Status

Birthdate varchar(20) Patient’s Birth DateAge int(5) Patient’s AgeAddress varchar(150) Patient’s Address

PoB varchar(150)Patient’s Place of Birth

Nationality varchar(20) Patient’s Nationality

Occupation varchar(20)Patient’s Occupation


Appendices | 53

ContactNo varchar(20)Patient’s Contact Number

Table H.3 Out-Patient Medical RecordField Name Datatype Description

Id int(10) AI PKPrimary Key & Medical Record Id

PatientId int(11) FKForeign Key & Patient’s Id

BloodPressure int(10)Patient’s Blood Pressure

PRPerMin int(10)Patient’s Pulse Rate

RRPerMin int(10)Patient’s Respiratory Rate

Temperature int(10)Patient’s Temperature

Medicine varchar(20)Patient’s Prescribe Medicine

Dosage varchar(20)Patient’s Medicine Dosage

Quantity varchar(5)Patient’s Medicine Quantity

FindingsAndDiagnosis varchar(255) Patient’s Diagnosis

ChiefComplain varchar(255)Patient’s Chief Complain

Table H.4 MedField Name Datatype Description

Id int(2) AI PKPrimary Key & Medicine Id

InfantId int(11) FK Infant’s Patient Id PatientId int(11) FK Patient’s Id

PregId int(11) FFPregnant Patient’s Id

Med_Name varchar(100) Medicine NameMed_Dosage varchar(50) Medicine DosageMed_Quantity int(5) Medicine Quantity

Table H.5 Pregnant Patient InformationField Name Datatype Description


Appendices | 54

PregId int(10) AI PKPrimary Key & Pregnant Patient Id

Lastname varchar(50)Pregnant Patient’s Last Name

Firstname varchar(50)Pregnant Patient’s First Name

Middlename varchar(50)Pregnant Patient’s Middle Name

CivilStatus varchar(10)Pregnant Patient’s Civil Status

Birthdate varchar(10)Pregnant Patient’s Birth Date

Age int(5)Pregnant Patient’s Age

Address varchar(150)Pregnant Patient’s Address

PoB varchar(150)Pregnant Patient’s Place of Birth

Occupation varchar(20)Pregnant Patient’s Nationality

Nationality varchar(20)Pregnant Patient’s Occupation

ContactNo varchar(15)Pregnant Patient’s Contact Number

LastMens varchar(10)Pregnant Patient’s Last Menstrual Period

AOG varchar(10)Pregnant Patient’s Age of Gestation

EDD varchar(10)Pregnant Patient’s Expected Date of Delivery

NoLB varchar(5)Pregnant Patient’s Number of Live Birth

NoSB varchar(5)Pregnant Patient’s Number of Still Birth

FHH varchar(255)Pregnant Patient’s Family Health History

Table H.6 Infant Patient Information


Appendices | 55

Field Name Datatype Description

InfantId int(11) AI PKInfant Primary Key & Patient Id

Lastname varchar(50)Infant Patient’s Last Name

Firstname varchar(50)Infant Patient’s First Name

Middlename varchar(50)Infant Patient’s Middle Name

Gender varchar(10)Infant Patient’s Gender

Birthdate varchar(15)Infant Patient’s Birth Date

Age varchar(5) Infant Patient’s Age

Address varchar(150)Infant Patient’s Address

FLastname varchar(50)Infant Patient’s Father Last Name

FFirstname varchar(50)Infant Patient’s Father First Name

FMiddlename varchar(50)Infant Patient’s Father Middle Name

FAge varchar(5)Infant Patient’s Father Age

MLastname varchar(50)Infant Patient’s Mother Last Name

MFirstname varchar(50)Infant Patient’s Mother First Name

MMiddlename varchar(50)Infant Patient’s Mother Middle Name

MAge varchar(5)Infant Patient’s Mother Age

FPoB varchar(150)Infant Patient’s Father Place Of Birth

FContactNo varchar(15)Infant Patient’s Father Contact Number

FOccupation varchar(20)Infant Patient’s Father Occupation

FNationality varchar(20) Infant Patient’s


Appendices | 56

Father Nationality

MPoB varchar(150)Infant Patient’s Mother Place Of Birth

MContactNo varchar(15)Infant Patient’s Mother Contact Number

MOccupation varchar(20)Infant Patient’s Mother Occupation

MNationality varchar(20)Infant Patient’s Mother Nationality

FHH varchar(255)Infant Patient’s Family Health History

Table H.7 Infant Patient Medical Record Field Name Datatype Description

Id int(11) AI PKInfant Primary Key & Medical Record Id

PRPerMin varchar(10)Infant Patient’s Pulse Rate

RRPerMin varchar(10)Infant Patient’s Respiratory Rate

Temperature varchar(10)Infant Patient’s Temperature

Medicine varchar(20)Infant Patient’s Prescribe Medicine

Dosage varchar(10)Infant Patient’s Medicine Dosage

Quantity varchar(10)Infant Patient’s Medicine Quantity

Immunization varchar(20) Infant Patient’s Prescribe Immunization

IDosage varchar(10) Infant Patient’s Medicine Dosage

Findings varchar(255) Infant Patient’s Diagnosis

ChiefComplain varchar(255) Infant Patient’s Chief Complain


Appendices | 57

Table H.8 Pregnant Patient Medical RecordField Name Datatype DescriptionId int(10) AI PK Primary Key &

Medical Record IdPregId int(11) Foreign Key &

Pregnant Patient’s Id

BloodPressure varchar(10) Patient’s Blood Pressure

PRPerMin varchar(10) Patient’s Pulse RateRRPerMin varchar(10) Patient’s

Respiratory RateTemperature varchar(10) Patient’s

TemperatureMedicine varchar(20) Patient’s Prescribe

MedicineDosage varchar(10) Patient’s Medicine

DosageQty varchar(10) Patient’s Medicine

QuantityFindings varchar(255) Patient’s Diagnosis


BSNCHCIS.doc

Documents

Transcript of BSNCHCIS.doc