Patient Portal System Design Project
SYSTEMS DESIGN PROJECT ASSIGNMENT INSTRUCTIONS
OVERVIEW
For your final assignment in this course, you will create a project using the requirements outlined below. You may use your own place of business (preferred) or an existing business that will allow you to perform these exercises. Answers such as “Yes” or “No” are not sufficient to respond to these questions. This project should be supported by both the textbook and peer reviewed research that addresses relevant systems analysis and design. Scholarly research should exist performed within the last few years that develop timely and appropriate procedures for an information systems analysis and design. In addition, your project should follow the general steps you learned within the textbook and your mini case assignments. This includes appropriate business requirements methods, appropriate systems analysis and associated diagrams, and appropriate systems design and associated diagrams.
INSTRUCTIONS
General requirements:
a. APA formatted paper using APA current edition and placing the appropriate margins, double-spacing, appendixes for tables and diagrams, and a references page
b. Approximately 10-15 APA formatted pages. Page count excludes cover page, table of contents, references, and appe1ndix pages (all tables and diagrams should be in an appendix).
c. 5 peer reviewed references with appropriate systems analysis and design supporting processes, procedures, and diagrams
d. Include the following 4 Phases (Planning, Analysis, Design, Implementation)
1. Planning Phase (Chapters 1-4)
a. Create an entire SDLC process that will bring added value to a business.
b. Identify the project—what is it supposed to do?
c. Determine the methodology to be used; describe, in detail, why you chose this methodology
d. Define/determine business requirements and describe the techniques you will use to gather this information
e. Work breakdown structure that details the project
b) Analysis Phase (Chapters 5-8)
a. Appropriate supporting frameworks and models
b. Describe how this project will bring added value to the business. This should be in the form of an actual presentation outline, such as one would read while doing
a Power Point presentation to the Board
i. Determine who the key players are
ii. Describe any known or possible issues that might arise as to why the project will not be approved
c. Along with the outline, justify, support, and develop a minimum of 5 different and unique analysis diagrams that use appropriate UML syntax. In other words, 5
CSIS 351
Page 2 of 2
diagrams of the same type is insufficient to show the entire analysis process.
Select 5 different diagrams from the following options:
i. Use cases and use case descriptions
ii. Activity diagrams
iii. CRC cards with your use cases
iv. Class diagrams
v. Entity relationship diagrams for any necessary databases
vi. Object diagrams
vii. Sequence diagrams
viii. Decision Trees
ix. Functional Decomposition Diagram
x. State machine diagrams
xi. Communication diagrams
c) Design Phase(Chapters 9-11)
a. Determine the hardware and software requirements
i. Will the existing infrastructure support the project?
1. If not, describe in detail what will be needed.
ii. Is new hardware required?
iii. Is new software required?
1. If new software is required, how will it be obtained?
2. Is the existing database adequate?
b. Design your information system with a minimum of 2 diagrams and/or graphical user interfaces. You can choose from the following diagrams:
i. A front-end UI proto-type (the back-end code is not necessary)
1. You can use a web language to design the web front-end
2. You can use a VB, C#, Java, or alternative programming IDE to design your front-end, the code is unnecessary, only the UI design
3. You can use Adobe Photoshop or a similar front-end design application
ii. Package diagrams
iii. Infrastructure diagram / hardware / data center / network model
1. You can use Visio or a similar application for designs that involve networks or systems, for example
d) Implementation Phase (Chapters 12 & 13)
a. Describe how the system is to be implemented; Phased? Turn key? Mirrored? Parallel?
b. Describe why the implementation you chose is the best for this project.
Note: Your assignment will be checked for originality via the Turnitin plagiarism tool
Patient Portal System Design Project
Student's Name
Institutional Affiliation
Instructor
Date
Planning Phase
Scope of the Project
The patient portal system design project is an effort to create a web-based platform that enables patients to communicate with healthcare practitioners, access their medical records, and manage their healthcare needs. The portal system aims to develop a comprehensive platform that provides patients with access to their medical records, appointment schedules, prescription information, lab results, and other important health information. The platform should also enable secure communication between patients and healthcare providers.
Objectives of the Project
First, the patient portal system is expected to empower patients to self-manage their healthcare needs by providing them with convenient and easy access test results, medical records, and other health information. Second, the patient portal system should facilitate communication between patients and healthcare providers, allowing patients to easily message their healthcare providers with questions or concerns, request prescription refills, or schedule appointments. Also, the system should enable healthcare providers to coordinate care more effectively by providing them with real-time access to patient medical records and other relevant information. Lastly, the patient portal system aims to enhance the patient experience by providing a user-friendly interface, easy navigation, and personalized information.
Methodology
The Agile methodology will be suitable for the Patient Portal System Design project. Agile is a flexible and iterative methodology that facilitates ongoing collaboration and feedback from stakeholders across the development process (Salza et al., 2019). It involves breaking down the project into smaller, more manageable phases or sprints, which allows for more frequent releases and faster delivery of working software. This approach emphasizes flexibility and adaptability to changing requirements and allows for continuous improvement.
Reasons for Choosing the Agile Methodology
First, the Agile methodology emphasizes ongoing collaboration and feedback from stakeholders throughout the development process, which is critical for a project like the Patient Portal System Design. This allows for frequent opportunities to validate the design and functionality with both patients and healthcare providers. Second, the Agile methodology allows for flexibility and adaptability. The approach is highly flexible and adaptable, allowing for changes to be made quickly and easily as new requirements emerge. This is important for the Patient Portal System Design project, as requirements may change over time as the patient needs and healthcare regulations evolve.
Another reason is its ability for faster delivery. The Agile approach involves breaking down the project into smaller, more manageable phases or sprints, which allows for more frequent releases and faster delivery of working software. This is important for the Patient Portal System Design project, as patients and healthcare providers may require access to the system as soon as possible. Also, the Agile methodology allows for risk management to be integrated into the development process, ensuring that potential risks and issues are identified and addressed early on in the project. This is important for the Patient Portal System Design project, as there may be significant security and privacy risks associated with the system.
Techniques for Determining the Business Requirement
The first approach is to conduct interviews with key stakeholders, including patients, healthcare providers, and administrative staff, to gather their input on the requirements for the patient portal system. Open-ended questions will be designed to encourage discussion and elicit detailed responses. The interviews will be recorded for later analysis. Next, surveys and questionnaires will be used to gather feedback from a larger group of stakeholders. These surveys would be distributed online and would focus on key areas such as user experience, security, and privacy. The responses would be analyzed and used to inform the design of the patient portal system.
Also, focus groups will be used to gather feedback from a specific subset of stakeholders, such as patients with a particular condition or healthcare providers with a specific specialty. These focus groups would allow for in-depth discussion and would provide valuable insights into the specific needs and requirements of these stakeholders (Gundumogulam, 2020). The last technique to determine business requirements is a thorough analysis of the existing Systems and Data Sources. An analysis of the existing systems is useful in identifying integration points and data requirements for the patient portal system. This analysis would involve reviewing existing system documentation, data models, and process flows.
Work Breakdown Structure of the Project
1 Project Planning 1.1. Define Project Objectives 1.2. Identify Key Stakeholders 1.3. Establish Project Team 1.4. Develop Project Schedule 1.5. Develop Project Budget 1.6. Define Project Management Plan 1.7. Obtain Project Approval
2 Requirements Gathering and Analysis 2.1. Conduct Stakeholder Interviews 2.2. Distribute Surveys and Questionnaires 2.3. Organize Focus Groups 2.4. Conduct Requirements Workshops 2.5. Analyze Existing Systems and Data Sources 2.6. Review Regulatory Compliance Requirements
3 System Design 3.1. Define System Architecture 3.2. Develop Data Model 3.3. Define User Interface 3.4. Develop System Components 3.5. Define System Integration Points 3.6. Develop System Security Plan
4 System Development and Testing 4.1. Develop System Components 4.2. Conduct Unit Testing 4.3. Conduct System Integration Testing 4.4. Conduct User Acceptance Testing
5 System Deployment 5.1. Develop Deployment Plan 5.2. Deploy System Components 5.3. Conduct User Training 5.4. Conduct System Maintenance
6 Project Management and Control 6.1. Monitor Project Progress 6.2. Control Project Changes 6.3. Report Project Status 6.4. Manage Project Risks
The Analysis Phase
Appropriate Frameworks and Models
The first framework that will be applied in this project is the Service-Oriented Architecture (SOA). It is based on the concept of services, which are modular, reusable components that can be combined to create complex systems. The SOA framework can be used to design a patient portal system that is flexible, scalable, and interoperable with other healthcare systems (Niknejad, 2020). By using services to encapsulate business logic, the patient portal system can be designed to support new features and functionality as they become available.
The Agile Framework is also appropriate for this project because it helps organizations adapt quickly to changing requirements and deliver software systems promptly. The Agile framework emphasizes collaboration, rapid prototyping, and iterative development, which can be employed to design a patient portal system that meets evolving user needs and regulatory requirements (Reichwein, 2020). By using Agile methodologies, the patient portal system can be designed to deliver value to users and stakeholders continuously.
Human-Centered Design (HCD) is another framework that focuses on designing systems that are intuitive, user-friendly, and meet the needs of the end-users. The HCD framework can be used to design a patient portal system that is easy to use, accessible to all users, and provides a seamless experience across all devices (Wheelock, 2020). By involving users in the design process, the patient portal system can be designed to meet their specific needs and preferences.
Expected Value of the System to the Business
Implementing a patient portal system can bring added value to a healthcare business in several ways. The first importance of the system is improved patient experience. A patient portal system allows patients to schedule appointments, access their health information, communicate with healthcare providers online, and request prescription refills. This can improve the overall patient experience by providing convenience, flexibility, and faster access to healthcare services.
The system is aimed at increasing the efficiency of the services in the business. A patient portal system can help healthcare practitioners streamline administrative tasks, including managing medical records, scheduling appointments, and processing prescription requests. This can increase efficiency and productivity, allowing healthcare providers to focus on providing quality care to patients.
Another value is cost savings. A patient portal system can reduce the cost of printing, mailing, and storing paper medical records, and lower the amount of time spent on administrative tasks. Additionally, patients may be more likely to schedule preventative care appointments and manage chronic conditions if they have easy access to their health information, potentially reducing healthcare costs over time.
The Key Players in the Patient Portal System
A patient portal system design typically involves several key players, including patients, healt...