Académique Documents
Professionnel Documents
Culture Documents
This report is submitted in partial fulfillment of the requirements for the Bachelor of
Computer Science (Software Development)
ABSTRACT
INTRODUCTION
1.1
Project Background
The surgical department is one of the organizations that provide services for
cases that need laparoscopic or open surgery. This department also receives
references from nearby districts such as from Jasin, Alor Gajah, Tampin, Tangkak,
and Segamat. The services that are given such as inpatient surgical treatment,
operation day, endoscopy, clinic day for the SOPD, breast clinic, palliatives care and
etc.
This system will use in the healthcare industry which is in the Unit Rekod
Perubatan (URP). The existing system is using manual system which is at this time,
all the data about patient has key in using Dbase. However, the calculation and some
of the task have done manually. Therefore, this is difficult task and sometimes gives
a problem. "Putting on the shoes of the people you've created, and looking at their
problems and solutions through their eyes" (Kuniavsky 2003). This system that will
develop is to improve the current system about the patient information database.
There was data redundancy about the patient admission record which one patient
takes many storage spaces in the database. For example, if the patient has been
admitted six (6) times in the different or same ward, he or she will have six (6)
different databases based on their R/N (reference number).
The main problem that faced are data redundancy. The existing system that
use have many databases record for one patient based on their admission. For
example, if the patient have admitted for eight (8) times in the different ward
although the same ward, she or he will also have eight (8) databases based on their
RN. Therefore, by using this new system it can generate one database record for
one patient. That's mean; this will decrease the storage place. Besides that, the lost
of the patient record also can be reduced. For the Surgical patient record, currently
the patient record is only recorded in the paper. Sometimes, the lost of patient record
happened most probably because of the misplaced of the record.
Another problem is about the unmonitored borrowing record. For the URP,
there is no system for recording borrowed information of the patient by the doctors.
When the doctor wants to borrow the record, the URP Bilik Kad's staff will always
spend a lot of time finding the record in the record room as they did not know if the
record is available or not. Sometimes, the person who borrowed the record did not
return it back personally to the record room after finished using. Therefore, it will
contribute to the unavailability of patient record at record room. And the staff at the
record room will spend a lot of time to find the unavailable record and this is such a
waste less work.
1.3
Objectives
1.4
Scope
This system will be developed for Unit Rekod Perubatan in the Surgery
department. These system has two level or different user which is administrator and
user. For administrator level, it will have their own password which can modify the
patient record and has the authority to all the module while the user only can view
the data. This system will not replace the note or description stated by the specialist
but as a guide to track or monitor the movement of the patient's file.
The functions of the system included:
a. Patient record management
1. Registration module
This feature is for the patient registration. The patient information
will insert to the database.
2. Add
This feature is for user to add new data into the database
3. Modify/ Update
This feature is for user to change the existence data in the program
4. Delete
This feature is for user to delete any existence data from the program
5. Save
This feature is for user to save a new data into the database
6. Find
b. Borrowing record
All the information will recorded in the database such as the person
who borrowed the patient record, the date and the reason. So, the
system will automatically calculate the duration. If the record has
borrowed more than two weeks, the system will print the reminder
letter (suratperingatan). This will reduce the lost or missing record
and unknown person who borrowed the record.
c. Report calculation
At the end of the month, this system will produce a report which
calculate the patient record and discharge information. This include
the total new record and the borrowing record.
d. Database integration
This system has network sharing which mean that if one administrator
key in or update the patient record, the record at the another computer
also updated. So, this will decrease the data redundancy and
duplicated.
1.5
Project significance
The management of the Unit Rekod Perubatan can manage all the patients'
records for surgical department effectively and clearly by using this system. The
data redundancy or lost of the data about patient records also will not happened
anymore.
1.6
Expected Output
The expected output is the computerized surgical patient record management for
Unit Rekod Perubatan in Surgery department is successfully implement and running
without problems.
1.7
Conclusion
From a proper planning and development, hopefully that this system is going
to solve the problems arise in the Patient Record Unit in the Surgery Department.
This system will make the staff works much more efficient to give service to the
people needed.
2.1
Introduction
To develop a new effective system, the research about literature review, about
the area and previous development must be done without doubt. Literature review
means searching, collecting, analyzing, and drawing conclusion from all debates and
issues raised in relevant body of literature. Based on Oxford Advanced Learner's
Dictionary, "literature" mean writings that are valued as works of art especially
fiction, drama and poetry while "review" means that a survey or report of a subject
or of past events. The source that we can get the literature review such as journal
articles, books, conference proceedings, government and corporate reports,
newspapers, theses and dissertations, technical reports, anonymous reference,
publication of international bodies or agencies, internet, CD-ROM,.and magazines.
Using a methodology helps with the management of the whole project by
breaking down the development process into small tasks, specifying the order in
which they should be done and the interdependencies of the tasks. This helps with
planning, scheduling and monitoring the progress of the system.
2.2
order to get a crystal clear about the system that going to be developed. A
comparison table between these case studies is show to see its similarities,
advantages and disadvantages.
replace human doing the routine and tedious paper work. All the calculation and
paper work will be replacing by the new system.
Besides the benefit on behalf of the staff, the new system can enhance
company marketing by providing online computerization insurance claim system.
By promoting this new system, we can attract other Manage Care Organization joint
us develop the new potential market. The slogan been used is "Online Insurance
Claim in A Minutes". This system will help company to get more and more
customer because we able to provides effective online insurance claim services.
Cost reducing is another benefit given by the new system. Previously
insurance claim process has to go through few persons, from admission department,
the claim for been pass to the clinic assistance to waiting attending doctor filling the
medical report. Later on the report has to fax to insurance company and the phone
call have to make to confirm insurance company have receives it. All of this process
can be reduce by implement healthcare guarantee system. Admission department
will register patient in the system and the attending doctor will fill in the medical
report immediately. Healthcare guarantee system will make the decision whether
this particular case will be cover by insurance company or decline. All this process
does not need fax, phone or paper. Besides this it also reduce work force the
company. The methodology chosen to develop the Healthcare Guarantee System is
categorized under structured design methodology. It is a set of procedure for
examining an existing information system and identifying the requirement for any
new system (Penny, 1897). It users a formal step-by-step approach to development
the system and move logically from one phase to the next phase. This methodology
used covers four main phases, namely system analysis, system design, system
development, and system testing.
oriented design method is able to indicate the impact of changes in clinic structure
using patient and doctor waiting times in clinic as endpoint measures. The effects of
changes in clinic size, consultation time, patient mix, appointment scheduling and
non-attendance were examined. We found that patient waiting time could be
shortened considerably by using an optimizing appointment scheduler to determine
appointment intervals. Clinic mix influences patient waiting time, which was shorter
with a 1 in 4 ratio of new to follow-up patients. In mixed clinics, new patient's
appointments are optimally spread throughout the clinic to reduce patient waiting
time. In all new or all follow-up clinics, waiting time is improved if the appointment
interval reflects the consultation time. Computer modeling can help in optimizing
clinic management so improving the delivery of care in outpatient services.
problem is that there is rarely sufficient communication to link these areas together.
Only a hospital-wide mission-driven effort will be effective at managing the coming
changes. This approach will require a level of teamwork never before demanded of
physicians, administrators, hospital staff, researchers, and teaching institutions.
Case study of Managing patients with identical names in the same ward
Correct patient identification remains one of the most essential steps of
safeguarding patient safety in healthcare (Emergency Care Research Institute
(ECRI), 2003). Errors in patient identification may lead to the unneeded exposure of
a patient to diagnostic or therapeutic procedure, the omission of the needed
procedures to another patient, or the failure of linking pathology specimens to the
correct patient. The greatest risk concerns acute care hospitals where a wide range of
clinical interventions take place in complex settings amidst a rapid turnover of
patients and staff who work in shifts. The Joint Commission on Accreditation of
Healthcare Organizations has identified the improvement of accuracy of patient
identification as the first goal in its National Patient Safety Goals (Joint Commission
on Accreditation of Healthcare Organizations, 2004). In particular, the National
Patient Safety Goals specify the use of at least two patient identifiers whenever blood
samples are taken from a patient, or when medications or blood products are
administered to the patient. Among these identifiers, patients' names are probably
the most convenient and the most frequent parameter used for patient identification.
Table 2.1: Summary of Case study (Managing patients with identical names in the
same ward)
Purpose
Findings
Originality/value
2.3
Project Methodology
With reference to Britton and Doake (1996), a methodology will prescribe in
great detail what tasks are involved in each step, the nature of each task, the order in
which the tasks need to be done, what documents are produced at each stage and
what documents are required as input to each stage. In fact, it provides a detailed
plan for producing a system. Methodology is a collection of processes, methods and
tools for accomplishing an objective. Methodologies provide a checklist of key
deliverables and activities to avoid missing key tasks.
SDLC Summary
- .-..
Ke
=M
v
Quallty Assurance Throughout
v
v
User needs
Proposed system
Systems Development Life Cycle (SDLC)
The system that will be developed is using SDLC (System Development Life
Cycle) approach. The SDLC approach has a similar set of four fundamental phases:
planning, analysis, design and implementation. Different projects may emphasize
different part of the SDLC or approach the SDLC phases in different ways, but all
projects have elements of these four phases.
Ti
Planning
Task Identification
Work Breakdown
Structure
Pert Chart
GAN'TT Chart
Scope Management
Staff project
Project Staffing
Staffing Plan
Project Charter
Control and Direct
Project
CASE Repository
Standard List
Standards
Risk Assessment
Documentation
Risk Management
Analysis
Develop Analysis
Business Process
Strategy
Automation
System Proposal
Business Process
Improvement
Business Process
Reengineering
Interview,
Determine Business
Observation,
Requirement
Requirements
Questionnaires
definition
Use case
Model Process
DFD
Process Models
Model Data
ERD
Data Model
Alternative
Design Physical
Design
system
Design Selection
Matrix
Physical Process
DFD
Models
Physical Data
ERD
Models
Architecture
Design Architecture
Implementation
Design Interface
Use Scenario
Interface Design
Data Format
Data Storage
File
Selection
Design
Design Program
Construct System
Programming
Test Plan
Install System
software Testing
Conversion Plan
Maintain System
Support Selection
Support Plan
Post
Post
implementation
implementation
Audit
Audit Report
Post implementation
There are several models under the SDLC approach and the model that will
be used to develop this system is waterfall model. The waterfall model has many
attractive features:
Clearly defined deliverables at the end of each phase, so that the client can
take decisions on continuing the project.
Incremental resource commitment. The client does not have to make a full
commitment on the project at the beginning.
Isolation of the problem early in the process.
Fe a s i b n l ~
A
halysis
bDesign
3
Kmplemenl7
Test
b
Maintain
Feasibility
The feasibility study is used to determine if the project should get the go-ahead. If
the project is to proceed, the feasibility study will produce a project plan and budget
estimates for the future stages of development.
Implementation
In this phase, the designs are translated into code. Computer programs are written
using a conventional programming language or an application generator.
Programming tools like Compilers, Interpreters, Debuggers are used to generate the
code. Different high level programming languages like C, C++, Pascal, Java are
used for coding. With respect to the type of application, the right programming
language is chosen.
Testing
In this phase the system is tested. Normally programs are written as a series of
individual modules, these subjects to separate and detailed test. The system is then
tested as a whole. The separate modules are brought together and tested as a
complete system. The system is tested to ensure that interfaces between modules
work (integration testing), the system works on the intended-platformand with the
expected volume of data (volume testing) and that the system does what the user
requires (acceptancebeta testing).
Maintenance
Inevitably the system will need maintenance. Software will definitely undergo
change once it is delivered to the customer. There are many reasons for the change.
Change could happen because of some unexpected input values into the system. In
addition, the changes in the system could directly affect the software operations. The
software should be developed to accommodate changes that could happen during the
post implementation period.
Table 2.3: System Development Life Cycle Phase- waterfall model
Phase
Problem definition :
Deliverables
Problem statement
manuals.
2.4
Project Requirements
2.4.1
Software Requirement
Table 2.4: Software Requirement
Requirements
Software
Description
i.
ii.
SWiSH v2.0
i.
i.
i.
language
c. Processor: Pentium 4
The Pentium 4 processor - Intel's "next generation" of processor to succeed
the Pentium III and Celeron processors. It is the most powerful processor available
for PC.
2.5
PHASE
TASK
START
END
DATE
DATE
DELIVERABLE
Define a project
Inception
- Project title /
Prepare project
proposal
- Background,
scope and objective
8/5/2006
11/5/2006
company
- Project proposal
the project.
- Find the
requirement of the
project
Project planning
- Prepare
architecture and
presentation of the
project.
Project estimation
- Create task
- Project Proposal
Project scheduling
Planning
- Specify the
resource of the
12/5/2006
26/5/2006
- Milestone of
project
project
Resource
allocation
- Planning of
Project
monitoring
Project control
Project risk
management
Analysis
and Design
Develop Analysis
-Requirement
Strategy
Definition
- Business Process
27/5/2006
Automation (BPA)
- Architecture
Determine
report