Patient Information Management System (PIMS)

8/3/2019 Patient Information Management System (PIMS)

1/46

Introduction Literature review Methodology Requirement engineering System analysis and design Conclusion

Patient Information ManagementSystem

(PIMS)

Steven Edward

Department of Computer Science,The University of Dodoma

November 24, 2011

Steven Edward Patient Information Management System (PIMS) 1/36
http://find/http://goback/


2/46


Outline

1 Introduction

2 Literature review

3 Methodology

4 Requirement engineering

5 System analysis and design

6 Conclusion



3/46


Outline

1 Introduction

2 Literature review

3 Methodology



6 Conclusion



4/46


General Introduction

Due to increase of population many Hospital think on how

to automate their manual system so that they can attend

many patient in a very short time.

Scope

It can be used in any Hospital, Clinic, Dispensary or

Pathology labs for maintaining patient details and their testresults.



5/46


General Introduction

Due to increase of population many Hospital think on how

to automate their manual system so that they can attend

many patient in a very short time.

Scope

It can be used in any Hospital, Clinic, Dispensary or

Pathology labs for maintaining patient details and their testresults.


I d i Li i M h d l R i i i S l i d d i C l i


6/46


Background

Hospitals provide facilities like

Consultation by Doctors on Diseases.

Diagnosis for diseases.

Providing treatment facility.

Facility for admitting Patients (providing beds, nursing,

medicines etc.)Immunization for Patients/Children.


I t d ti Lit t i M th d l R i t i i S t l i d d i C l i


7/46


Problem Statement

Hospitals are facing a lot of problems such as

Loosing patients details.Poor doctor- patient schedule management.

Mixing up of patients prescription data and others.

Lacks privacy and integrity of records because records

are stored in files.




8/46


Objectives

General Objectives

To help in Patient information management activities at the

Hospitals.

Specific Objectives

Patient will have ease way to get appointments.

To help Doctors in viewing Patient RecordsTo Simplify tracking of Patients report.




9/46


Objectives

General Objectives

To help in Patient information management activities at the

Hospitals.

Specific Objectives

Patient will have ease way to get appointments.

To help Doctors in viewing Patient RecordsTo Simplify tracking of Patients report.




10/46


Justification

It will require less number of Staff to cater more

patients in same time

PIMS will increase the profit of the organization.Hospitals will serve the rapidly growing number of

health care consumers in a cost-effective manner

Hospital administrators would be able to significantly

improve the operational control .It will improve the response time to the demands of

patient care




11/46


Justification

Doctors would spend his precious time more in clinical

activities than to put in clerical activities otherwise

The software interface would also save them a lot of

time for special jobs only

It will eliminate accounting complexity, since the

retrieval of information through it, will become virtually

on the tip of your fingers

Very important for some, the reduced cost of the

manpower would pay for the cost of developing the

software with in a short time after its implementation.




12/46


Outline

1 Introduction

2 Literature review

3 Methodology



6 Conclusion




13/46

gy q g g y y g

Feasibility study

Operational feasibility

Measure of how well a solution meets the identified system

requirements to solve the problem and take advantage of

the opportunities envisioned for the system

Organizational feasibility

Focuses on how well a proposed system supports the

strategic business priorities of the organization.

Economic feasibility

concerned with whether expected cost savings, increased

revenue, increased profits and reductions in required

investment and other types of benefit will exceed the costsof develo in and o eratin a ro osed s stemSteven Edward Patient Information Management System (PIMS) 11/36



14/46

gy q g g y y g

Feasibility study

Technical feasibility

Is the proposed technology or solution practical?

Do we currently process the necessary technology?

Do we possess the necessary technical expertise?

Cultural (or political) Feasibility

The willingness and ability of management, employees,

and others to operate, use, and support a proposed

system.

Test of feasibility study especially on economic feasibility

show that the project is feasible.




15/46

Feasibility study








system.






16/46

Feasibility study








system.






17/46

Other System

DHIS Open-source district health management

information system and data warehouse

HRHIS Open-source human resource for health

information system for management of human

resources for health developed by University of Dar es

Salaam, Department of Computer Science, for

Ministry of Health and Social Welfare (Tanzania)

ClearHealth covers the five major areas of practice

operations including scheduling, billing, EMR, HIPAASecurity and accounts receivable. It offers a fully

comprehensive system which now offers tools like

E-Prescribing, Drug Interactions, Electronic Labs and

Lab ordering. Steven Edward Patient Information Management System (PIMS) 13/36



18/46

Outline

1 Introduction

2 Literature review

3 Methodology



6 Conclusion




19/46

Methodology

Methods

Waterfall Model

Unified Modeling Language (UML)

Tools

Tools for capturing requirements are Observation,

Questionnaires, Review documents and Interviewing




20/46

Outline

1 Introduction

2 Literature review

3 Methodology



6 Conclusion




21/46

Users and their roles

Designation Roles

Receptionist Register a patient to the system,

take fee and schedule the appointment.

Nurse To assist the patient in the ward

by updating his/her status

Doctor To attend a patient and prescribe the

laboratory test and medicine

Patient Request for appointment.

Administrator Add and activate user accountsalso generate system backups.

Pharmacist Gives the patient proper medicine

prescribed by the Doctor.

Lab technician Take care of all the Test




22/46

Functional requirements

The system should allow Doctor, Patient, Nurse,

Pharmacist, Nurse, Receptionist to login

The system should Register the Patient if he is new to

the System

The system should allow doctor to be able to see

Schedule appoitments in day, month and year fashion

The system should allow doctor to be able to see any

medical alerts, reminders and schedule of the patient

for any tests.

The system should allow doctor to get in touch with the

patient or any of the associated caretakers via phone,

text messages, and email directly from System.




23/46

Functional requirements

The system should allow administrator to able to

Delete, Update and Add the Doctor/Nurse/Staff if they

are leaving the hospital, their detail changes or new

staff arrives at the hospital.

The system should allow Nurse to allocate Room or

Bed to the patient in case if patient is hospitalized.

The systems should allow receptionist to enter fee

collection records from the patient.

The system allows doctor to enter diagnoses and

Prescribes medicine.

The system should allow nurse to Log the patient data

and access doctor diagnoses.




24/46

Non Functional requirements

Storage

The system should be database management system

where the systems information are going to be kept in the

database including patient and staff information.

Performance

The system shall operate in a reasonable speed both to

use it and when accessing some data and information from

the database.

Portability

The system should be able to run in different environments,

such as Windows and the various flavors of UNIX.




25/46


Storage




Performance



the database.

Portability






26/46


Storage




Performance



the database.

Portability






27/46


Storage




Performance



the database.

Portability






28/46


Security

The system should protect itself from external attacks that

may be accidental or deliberate such as viruses,

unauthorized use of system services, and unauthorized

modification of the system or its data.

Robustness

The system should have the ability to continue to function

accurately even if the actor inputs wrong commands

Accessibility

The system should be accessible to all authorized users

using their usernames and password.Steven Edward Patient Information Management System (PIMS) 21/36



29/46


Security





Robustness



Accessibility





30/46


Security





Robustness



Accessibility





31/46


Security





Robustness



Accessibility





32/46

Outline

1 Introduction

2 Literature review

3 Methodology



6 Conclusion




33/46

Use case modeling




34/46

Use case modeling




35/46

Use case modeling




36/46

Refined Use case




37/46

Class diagram




38/46

Sequence diagram




39/46

Sequence diagram




40/46

Sequence diagram




41/46

Interface Design




42/46

Interface Design




43/46

Interface Design




44/46

Outline

1 Introduction

2 Literature review

3 Methodology



6 Conclusion




45/46

Conclusion

From the evaluation, the system can be viewed as very

useful and a success. It is necessary though to carry outthe qualitative measures again once the system has been

installed for the trial period. This will give an even more

conclusive evaluation of the project and determine whether

or not it will be fully implemented.




46/46

Conclusion

Thats very kind of you


Documents

Patient Information Management System (PIMS)