Clinic Management System
Clinic Management System
Name:
Student ID:
Instructor’s Name:
AGENDA:
1. Introduction
Briefly Introduction Of The Project
Problems Identification And Solutions
2. Scope Of The Project
3. Objectives
4. Deliverables
5. Milestones
6. Technical Requirements
7. Limits And Exclusions
8. WBS
9. Gantt Chart
10.Implementation, Testing And Deployment
11.Conclusions
Introduction
In the era of technology, where everything needs to be done efficiently and
effectively the existences of Clinic Management System (CMS) become necessary.
The used of CMS can enhance the services and also the work flow of all activity
that happens in hospitals where it helps in reducing the workload of medical staff,
the number of man power needed and it also make hospitals management become
more manageable and easier to control.
Currently, there is a huge number of private and public hospitals that keep their
patients records in books and store them manually. it’s a very formal way of
storing data and records but the demerit of storing data in this manner is poor
handling of the books may lead to lose of data , the books are not that much secure
and are easily perishable furthermore books have no back up once lost cannot be
retrieved. Applying this system in such institutions will help manage these records
and preserve the information for longer periods of time and also make its access far
much simpler and easier; it also ensures accuracy and openness of the patient’s
details / records.
Scope of CMS:
The system has been facing problems due to its paper-based appointment system.
With the increase in the number of patients visiting, it has become difficult to
manage the appointment system manually. Recording of appointments and creating
registers by pen and paper has become a tedious task. And also it’s difficult to
manage huge number of patient database.
OBJECTIVES:
Employees are the core entity in ensuring maximum and sufficient service.
The problem is in the supervision, where employees are bound to get away
with anything without the institution’s notice. The new system will have a
record of all stake holders involved in the institution, including employees.
This will establish a clear strategy that will ensure easy employee
supervision.
Since a single system will be set to monitor and process loads of the
institution’s operation, this will cut down on the unnecessary spending. The
rest of the capital will help in improving the institution facilities and other
amenities.
Reducing errors. Our software will provide proper validation techniques that
will collectively reduce errors done when recording data.
Increase revenue
Large space usage. Use of paper to record data requires large space for storage
over time. This can be seen in many places where analogue systems are in use.
Inefficient back up methods. Old systems especially that which are analogue do
not provide effective ways to back up data and as a result data can be permanently
lost in the event data is damaged or misplaced. This may lead to the collapse of the
institution.
.Analogue systems do not allow efficient supervision of its users and thus
employees are likely to commit fraud undetected and get away with it.
Deliverables:
The final system that will be delivered at the completion of the project will
contain the following:
1. A complete working website with a Login (authentication) system.
2. Documentation on the use of the system.
Milestones:
The different stages or checkpoints in the development cycle of (CMS)
The software development cycle for a hospital management system generally
consists of the following stages:
Planning and requirements gathering: This is the first stage in the development
cycle, where the various stakeholders involved in the project (e.g. hospital staff,
administration, etc.) come together to discuss the goals and objectives of the
system. This stage also includes developing a high-level requirements document
that will serve as a blueprint for the rest of the project.
Design: In this stage, the software architects and developers work together to
design the overall structure and individual components of the system. This includes
both functional and non-functional aspects such as usability, performance,
scalability, etc.
Implementation: Once the design is complete, it is time to start coding! The actual
implementation can be done by in-house developers or by external vendors,
depending on the size and complexity of the project.
Testing: An important part of any software development project, testing helps
ensure that the system meets all the requirements specified in the earlier stages.
Testing can be done manually or using automated tools, and usually happens
concurrently with implementation.
Utilization: Once everything has been tested and found to be working as expected,
it is time to deploy the system into production. This stage typically involves some
amount of user training as well so that everyone knows how to use the new system
effectively.
i) Feasibility study
2. Economic Feasibility:
A network-based system requires a lot of equipment such as cables, hubs etc.
This requires a lot of initial capital to install the network. On the other hand, it
allows sharing of resources and information and centralized administration hence
cheaper.
3. Technical Feasibility
4. Time Feasibility
The system is a small one and hence the time frame of three months allocated for
development is enough hence there is time feasibility.
From the above we choose to use a network based database system because as
compared to the other strategies, it more feasible. It will contain an interface that is
distributed in the network and is connected to a central data-base.
Feasibility study involves cost/benefit analysis. In the process, the cost and
benefits are estimated with greater accuracy. If cost and benefit should be
quantified to make a good system that is affordable.
Technical Requirements:
Hardware Minimum specification Use
Processor 1 gigahertz (GHz) or For development purposes
faster
RAM 256 megabytes (MB) and For development purposes
above.
Hard disk space 16 GB (32-bit) or 20 GB For development purposes
(64-bit)
Testing
a) Unit testing
b) Integrated testing
Delivery
Train staff
Deliver documentation
Budget and schedule
CONCLUSIONS
I believe I have done enough research on the Project and am ready to start and
complete the project over the period specified and also make the delivery. A lot of
research and survey, as well as the documentation analysis need to be done in order
to make sure that the information are accurate and the system is more efficient and
also systematic. The research that had been done is concluding in the Literature
Review. Analysis is done to make sure that the data can be used as a guideline for
developing this system. There are existing systems which involve in this chapter.
The existing system tells about how they work and what the requirements that need
from their users are. This kind of information is gathered and an analysis is done to
select the appropriate features to be developed to the new system (Development of
clinic Management System for School Clinic).
References:
1. Seidler, K. (2011, January 27). Apache friends - xampp. Apache friends -
very easy apache, mysql, php and perl installation without hassles.
Retrieved January 2, 2013, from
http://www.apachefriends.org/en/xampp.htm
2. Valade, J., Ballad, T., & Ballad, B. (2008).PHP & MySQL web development
all-in-one desk reference for dummies. Hoboken, NJ: Wiley.