Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Patient Information Management System (PIMS) Steven Edward Department of Computer Science, The University of Dodoma
November 24, 2011
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
Outline 1
Introduction
2
Literature review
3
Methodology
4
Requirement engineering
5
System analysis and design
6
Conclusion
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
Outline 1
Introduction
2
Literature review
3
Methodology
4
Requirement engineering
5
System analysis and design
6
Conclusion
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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 test results.
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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 test results.
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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.
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
Problem Statement
Hospitals are facing a lot of problems such as Loosing patients’ details. Poor doctor- patient schedule management. Mixing up of patient’s prescription data and others. Lacks privacy and integrity of records because records are stored in files.
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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 Records To Simplify tracking of Patients’ report.
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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 Records To Simplify tracking of Patients’ report.
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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.
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
Outline 1
Introduction
2
Literature review
3
Methodology
4
Requirement engineering
5
System analysis and design
6
Conclusion
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
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
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
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
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
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
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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, HIPAA Security and accounts receivable. It offers a fully comprehensive system which now offers tools like
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
Outline 1
Introduction
2
Literature review
3
Methodology
4
Requirement engineering
5
System analysis and design
6
Conclusion
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
Methodology
Methods Waterfall Model Unified Modeling Language (UML) Tools Tools for capturing requirements are Observation, Questionnaires, Review documents and Interviewing
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
Outline 1
Introduction
2
Literature review
3
Methodology
4
Requirement engineering
5
System analysis and design
6
Conclusion
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Users and their roles Designatio tion
Roles
Rece Re cept ptio ioni nist st
Regist Regi ster er a pa pati tien entt to th the e syst system em,, take fee and schedule the appointment. To assist the patient in the ward by updating his/her status To attend a patient and prescribe the laboratory test and medicine Request for appointment. Add Add an and d acti activ vat ate e user user acco accoun unts ts also generate system backups. Giv Gives th the e pa pati tien entt prop proper er me medi dici cine ne prescribed by the Doctor.
Nurse Doctor Patient Admi Admini nist stra rato torr Pharm Pharmac acis istt
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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,
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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,
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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,
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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,
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
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,
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
Non Functional requirements 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
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
Non Functional requirements 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
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
Non Functional requirements 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
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
Non Functional requirements 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
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
Outline 1
Introduction
2
Literature review
3
Methodology
4
Requirement engineering
5
System analysis and design
6
Conclusion
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Use case modeling
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Use case modeling
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Use case modeling
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Refined Use case
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Class diagram
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Sequence diagram
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Sequence diagram
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Sequence diagram
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Interface Design
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Interface Design
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Interface Design
Requirementt engineering Requiremen
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
Outline 1
Introduction
2
Literature review
3
Methodology
4
Requirement engineering
5
System analysis and design
6
Conclusion
System analysis and design
Conclusion
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
Conclusion
From the evaluation, the system can be viewed as very useful and a success. It is necessary though to carry out the 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.
Introduction
Literature review
Methodology
Requirementt engineering Requiremen
System analysis and design
Conclusion
Thats very kind of you
Conclusion
