Capstone Project assignment: Analysing Patient Management System

Question

Task:
Write a detailed and well-researched report on capstone project assignment on patient management system to support patient care at the consortium.

Answer

1. Executive Summary
The report reflects the analysis and design of patient management system local General practice consortium. The report provides a detailed description of the system. It also includes feasibility analysis of the system. According to the given analysis, system is essential for the organization to implement. The report also provides details of system requirement that will be later converted into system designs. The use case diagrams visualizes how the four users of the system will interact with it. Description of four use cases has also been included into the report. As per the architecture diagram, users of the application can access the system from desktop and mobile devices both.

2. Specification
Objective of the system is to support patient care at the consortium. The system will handle the appointment and prescription related information so that employees can focus on real work.

2.1 System Description
The following report deals with General consortium which come up three metro surgeries being located in Sydney. This consortium requires a system to keep a track of on-line records inclusive of written medicines along with patient booking system. This particular system will be involved in handling booking for three surgeries. It will even have features like adding new surgeries and registering of doctor through the system. If the expected doctors fail to reach, then patient should with booked appointment should be given an alternative one. In this system, patient can access details through mobile phone while both doctors and front desk staff will have access through desktop.

Patient management system is defined as collection of activities for the healthcare practices being used for management and delivery of growing expectation of patients. This stand out to be an approach used for fostering the relationship with patients instead of just treating the illness (Gia, Procedia Computer Science, 2017). Healthcare providers can understand the fact the patient can be treated more like consumer instead of sick people. The point should be noted that patient management will result in enhancing the overall health of patient, enhancing patient satisfaction with healthcare firm. Patient management system will enhance the overall accuracy within staff (minimizing the possible errors) which can benefit the bottom line of healthcare firms either through indirect or direct way (Alloghani M. A.-J., 2018, September). Proper patient management platform can improve the burden of staff with automation which can assure care being delivered in much timely way. The software is found to be useful in making the day-to-day operation much streamline.

2.2 Feasibility Analysis
It is generally related to two parameters mainly human organization and political. There is need for considering a list of points like

What possible changes can be brought within the system?
What exact organization structure can be distributed?
What new skills are required? Do the patient and staff members come up with these skills? If not, can both staff members and patient can be trained within the period of time?

Patient management system is found to be operational feasible as it is easy to use system from the perspective of End User to operate it (Nicolini, 2018). This specific system can only form major basic information regarding the windows platform.

2.2.1 Technical Feasibility
The complete study of resource availability tends to differ much with respect to ability for achieving the acceptable system (Foley, 2020). This specific evaluation can help in determining whether the required technology can be required for suggested system being available or not.

Can this work for project to be easily done with respect to present equipment based on software technology and available personal?
Can this system can be upgraded if this is developed anyhow?
If new kind of technology is required, then what exact thing can be developed?

It is much related to specify both equipment and software which can successfully meet the user requirement. The technical abilities of the system will comprise of

Front end and back-end selection: One of the vital factor behind project development is all about selecting the suitable front-end and back-end. When decision has been made regarding the development of this patient management system, there is need for some extensive study so that it can achieve the growing need of the firm (Samadi, 2018). This will again help in developing this patient management system. Some of the vital factors of Patient management system are

It requires to have a graphical user interface which can assist employees who are not from the information technology background.
Platform independent.
Helps in driving the facility of programming
Front end of the application tend to support some of the popular back end services like MS access.

Back-end Selection: There is need for selecting back-end selection for list of factors like

Multiple User support
Providing some inherent features which can be used for security purpose.
Easy to implement with the front-end
Compatible with operation system.

Taking into account the above stated features, MS-access has been considered as the backend option.

2.2.2 Economic Feasibility
Economic feasibility is just the bottom line of consideration being used for majority of system. It comprises of range of concern which comprise of cost benefit analysis. Both cost and benefit in relation to candidate system will help in analysing the main purpose of the firm like profit making (Kurtanovi?, 2017, September). The project is all about carrying out analysis and design stage. Both financial and economic question are used during the main investigation to verify a list of things like

Cost involved in carrying out investigation of the system
Overall cost of hardware and software required for class of application being used.
Benefits found in the form of minimized cost.
The suggested patient management system will provide minute information due to which the performance of system will improve.

The economic feasibility even checks whether the given system can be developed by making use of available funds. Patient management system does not require huge amount of money to be developed.

2.2.3 Organizational Feasibility
Economic feasibility is just the bottom line of consideration being used for majority of system. It comprises of range of concern which comprise of cost benefit analysis. Both cost and benefit in relation to candidate system will help in analysing the main purpose of the firm like profit making. The project is all about carrying out analysis and design stage (Becker, 2019). Both financial and economic question are used during the main investigation to verify a list of things like

Cost involved in carrying out investigation of the system
Overall cost of hardware and software required for class of application being used.
Benefits found in the form of minimized cost.
The suggested patient management system will provide minute information due to which the performance of system will improve.

The economic feasibility even checks whether the given system can be developed by making use of available funds. Patient management system does not require huge amount of money to be developed.

2.3 Requirements Specification
2.3.1 Functional
There are numerous kind of software requirements which needs to be included within patient management system comprising of process, registration, report generation and database.

Registration Process of patient management system

Adding up patients: Patient management system will allow the staff on front desk to have details of new patient.
Assigning a specific ID to the patients: This patient management system will help staff members to give unique ID for individual patient followed by adding up on the record sheet.

Checking out the patient management system

Deleting the patient ID: Staff within the administration department can easily delete the patient ID where patient can check out easily from hospital.
Adding up best on the list: Staff within administration section of the ward can put the bed in the list of available bed.

Generating reports

Detail information of the patients
Checking the availability of beds.

Database being for patient management system

Creating a mandatory right for patient information

Updating all the detail information of the patient.

2.3.2 Non-functional
There are numerous kind of software requirements which needs to be included within non-functional requirement for Patient Management System comprising of security, performance, reliability and maintainability.

Security
Patient Identification: In this system, patient management system needs to be considered for using the mobile phone.

Modification: Any kind of possible modification like inserting, deleting, update for database needs to be synchronized and executed at quick rate

Administrator rights: The administrator can either view or make an alternation in this patient management system.

Performance

Response time
Capacity
User-Interface
Conformity

Maintainability

Back-up of system.
Errors

Reliability

Availability

2.4 Use Cases
2.4.1 Use Case Diagrams

Use Case dia in capstone proj 1

Figure 1: Use Case Diagram of Receptionist Interaction
(Source: Created by Author)

Use Case dia in capstone proj 2

Figure 2: Use Case Diagram of Administrator Interaction
(Source: Created by Author)

Use Case dia in capstone proj 3

Figure 3: Use Case Diagram of Doctor Interaction
(Source: Created by Author)

Use Case dia in capstone proj 4

Figure 4: Use Case Diagram of Patient Interaction
(Source: Created by Author)

2.4.2 Use Case Descriptions

Use Case ID	Receptionist_UC_01
Use Case Name	Register Patient
Description	Receptionist at font desk will register a patient into the system. Receptionist collects data from patient and store those data into system. System automatically creates few necessary data like default password and share account credentials with student.
Actors	Receptionist
Stakeholders	Receptionist, Patient, local general practice consortium
Pre-condition	Patient must not be registered
Activities	User	System
	Receptionist open register patient form	System opens a form that includes all necessary form input boxes
	Receptionist enters collected data in each input	System checks if entered data is valid
	After all the necessary data is entered without any error, receptionist submits the form	System generates a default password and store all the data in the database.
Post-conditions	Patient login credentials are share through email and contact number
Exception	Patient forget email login credentials to check password

Use Case ID	Patient_UC_01
Use Case Name	Request Appointment
Description	A patient can request for an appointment through the mobile device. Patient has to select a doctor who he wants to visit and the date and time of visit for raising a request.
Actors	Patient
Stakeholders	Doctor, Patient, Receptionist and local general practice consortium
Pre-condition	Patient must be logged in
Activities	User	System
	Patient opens the request raise section	System provides a screen for requesting new appointment
	Patient selects a type of specialist required	System shows the doctor list with available dates in a calendar
	Patient selects a date and time	System raise a request for the patient on that date and time including the doctor
Post-conditions	A new request is sent to receptionist
Exception	Doctor cancelled all appointment in a date and patient raise a request before data could reflect on his/her screen

Use Case ID	Admin_UC_01
Use Case Name	Add Surgery
Description	Administrator can update the list of surgery by adding new surgeries to the system. As soon as a new surgery is added, receptionist can book that surgery for patient.
Actors	Administrator
Stakeholders	Administrator, Doctor, Patient, Receptionist and local general practice consortium
Pre-condition	Surgery must be unique
Activities	User	System
	Administrator opens the surgery add form	System provides a screen for adding new surgery
	Admin enters all the data and submit the form	System validates those data and store the data in database
	Admin can see the surgery in the list
Post-conditions	Patient can book surgery
Exception	Consortium does not have the facility to do the surgery

Use Case ID	Doctor_UC_03
Use Case Name	Add Prescription
Description	A doctor can add a prescription for an appointment. This prescription represents the suggested medication for that appointment. Doctor will provide name of medicine as well as other primary health status in the prescription.
Actors	Doctor
Stakeholders	Doctor, Patient, local general practice consortium
Pre-condition	Prescription can be added only after an appointment
Activities	User	System
	Doctor clicks on new prescription link	System opens a form that includes inputs for key health stats and medicine names
	Doctor will select the patient	System will shows all appointments of that patient in descending order of appointment date
	Doctor selects any one and fills other inputs with data	System verifies the entered data in real time
	Doctor submits the prescription	System store all the data in the database.
Post-conditions	Prescription will be accessed by patient through mobile phone
Exception	Prescription contains characters that system cannot read

Table 1: Use Case Descriptions

2.5 Context Model

Use Case dia in capstone proj 5

Figure 5: Context Diagram of Patient Management System
(Source: Created by Author)

3. Design
Primary objective of the design is to transform the requirements into suitable visual form. All the system requirements cannot be visualized through one specific diagram that is why multiple diagrams will be created in the report. The architecture diagram will provide idea on how the server-client communication will work and the mediums for communication. Entity relationship diagram will provide the information of data structure of the application.

3.1 Architectural Design

Use Case dia in capstone proj 6

Figure 6: Architecture Diagram of Patient Management System
(Source: Created by Author)

3.2 Hardware Specifications
The system will be hosted in a shared hosting server. That is why no hardware for server is required. However, to operate the system, few computers are required. The computer must have 320 GB SSD, 8GB ram, one Screen for output, required I/O devices, i3 or equivalent processor.

3.3 Database Structure

Use Case dia in capstone proj 7

Figure 7: Entity Relationship Diagram of Patient Management System
(Source: Created by Author)

3.4 Interface Design

Use Case dia in capstone proj 8

Figure 8: Wireframe Diagram New Patient Register
(Source: Created by Author)

Use Case dia in capstone proj 9

Figure 9: Wireframe Diagram New Surgery Add
(Source: Created by Author)

Use Case dia in capstone proj 10

Figure 10: Wireframe Diagram New Appointment Request
(Source: Created by Author)

Use Case dia in capstone proj 11

Figure 11: Wireframe Diagram New prescription Add
(Source: Created by Author)

3.5 Sequence Diagrams

Use Case dia in capstone proj 12

Figure 12: Sequence Diagram Appointment Request
(Source: Created by Author)

Use Case dia in capstone proj 13

Figure 13: Sequence Diagram New Prescription
(Source: Created by Author)

Use Case dia in capstone proj 14

Figure 14: Sequence Diagram New Surgery
(Source: Created by Author)

Use Case dia in capstone proj 15

Figure 15: Sequence Diagram Patient Register
(Source: Created by Author)

3.6 State Diagrams

Use Case dia in capstone proj 16

Figure 16: State Diagram Appointment Request
(Source: Created by Author)

Use Case dia in capstone proj 17

Figure 17: State Diagram New Prescription
(Source: Created by Author)

Use Case dia in capstone proj 18

Figure 18: State Diagram New Surgery
(Source: Created by Author)

Use Case dia in capstone proj 19

Figure 19: State Diagram Register New Patient
(Source: Created by Author)

References
Alloghani, M. A.-J. (2018, September). Data science to improve patient management system. In 2018 11th International Conference on Developments in eSystems Engineering (DeSE) (pp. 27-30). IEEE.

Becker, P. T. (2019). Applying an Improving Strategy that embeds Functional and Non-Functional Requirements Concepts. . Journal of Computer Science and Technology, , e15-e15.

Foley, M. O. (2020). From bench to bedside–development of an integrated COVID-19 patient flow management system. Journal of Hospital Infection, 106(1), 211-213.

Gia, T. N. (2017). Procedia Computer Science. IoT-based continuous glucose monitoring system: A feasibility study., 109, 327-334.

Kurtanovi?, Z. &. (2017, September). Automatically classifying functional and non-functional requirements using supervised machine learning. In 2017 IEEE 25th International Requirements Engineering Conference (RE) (pp. 490-495). IEEE.

Nicolini, A. F. (2018). Alterations of signaling pathways related to the immune system in breast cancer: New perspectives in patient management. International journal of molecular sciences,, 19(9), 2733.

Samadi, S. (2018). Theory of planned behavior and knowledge sharing among nurses in patient computer management system: The role of distributive justice. Management Science Letters, 8(5), 427-436.

Tags: capstone project critical analysis sydney project management

NEXT SAMPLE