1. HI-600: Analysis and Design of Health Information Systems
Systems Development Life Cycle
Planning – Analysis – Design – Implementation
2. Systems Development Life Cycle (SDLC)
Business
Need
Planning
Analysis
Design
Implemen-
tation
Maintenance
Evaluation
3. Systems Analyst
• Technical – Must understand the technical
environment, technical foundation, and technical
solution.
• Business – Must understand how IT can be applied to
business situations.
• Analytical – Must be problem solvers.
• Interpersonal – Need to communicate effectively.
• Management – Need to manage people and to
manage pressure and risks.
• Ethical - Must deal fairly, honestly, and ethically with
other project members, managers, and systems users.
4. Steps of the Planning Phase
• During project initiation, the system’s business
value to the organization is identified
• How will it lower costs or increase revenues?
• In healthcare, it is not all about the cost
• During project management, the project
manager creates a work plan, staffs the project,
and puts techniques in place to help the project
team control and direct the project through the
entire SDLC.
5. Steps of the Analysis Phase
• Analysis strategy: Guidance for the projects team’s
efforts that includes a study of the current system and
its problems and envisioning ways to design a new
system.
• Requirements gathering: The analysis of requirements
leads to the development of a concept for a new
system. It is used to build a set of analysis models.
• System proposal: Presented to the project sponsor
and other key individuals who decide whether the
project should continue to move forward.
6. Steps of the Design Phase
• Design Strategy: Clarifies whether the system
will be developed by the company or outside the
company.
• Architecture Design: Describes the hardware,
software, and network infrastructure that will be
used.
• Database and File Specifications: Define what
and where the data will be stored.
• Program Design: Defines what programs need
to be written and what they will do.
7. Steps of the Implementation Phase
• System Construction: The system is built or
purchased and tested to make sure it performs
as designed.
• Installation: The old system (if exists) is turned
off and the new one is turned on.
• Support Plan: Includes a post-implementation
review as well as a systematic way for
identifying changes needed for the system.
8. HI-600: Analysis and Design of Health Information Systems
Systems Development Life Cycle
Planning – Analysis – Design – Implementation
Notas del editor
In a previous video we discussed health information systems.
And now, let’s talk about the process of creating such systems, namely the systems development life cycle and its four phases as described in our textbook.
The systems development life cycle (SDLC) is the process of determining how an information system (IS) can support business needs, designing the system, building it, and delivering it to users.
The concepts included in the SDLC has been around for a long time; they are a guideline of bringing any new system online to any organization, especially larger organizations
These processes are critical to project management, programmers, and executives of the organization
And following these guidelines is the key to keeping the long term maintenance costs down, the work organized, and the processes monitored.
In SDLC, we start with identifying the business need ……
****
The textbook covers the same process in four stages.
Each of the phases is composed of steps, which rely on techniques that produce deliverables .
Let’s discuss the role of the system analyst, who manages the SDLC and steps involved in each phase of the SDLC
The key person in the SDLC is the systems analyst, who
analyzes the business situation,
identifies the opportunities for improvements,
and designs an Information Ssystem to implement the improvements.
There are several qualifications a business analyst must have;
The planning phase of the SDLC covers the fundamental process of understanding why an information system should be built and determining how the project team will go about building it.
There are typically two steps involved with the planning phase:
During project initiation, the system’s business value to the organization is identified; trying to determine how it will lower costs or increase revenues.
However, in healthcare, the business value is not always directly related to the finances; concepts such as patient safety and quality improvement are very important to health care organizations, although they may not always positively affect cost.
During project management, the project manager creates a work plan, staffs the project, and puts techniques in place to help the project team to control and direct the project through the entire SDLC.
In this phase, we are moving from the question of WHY and IF we need an information system to WHO, WHAT, WHERE, and WHEN: The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used.
During this phase the project team investigates the current system(s), if any, identifies improvement opportunities, and develops a concept for the new system.
During the analysis phase, with the analysis strategy, we first analyze the current systems, the workflow, and their problems. Based on that analysis we envision ways to design a new system.
Then the requirements for the system are gathered and analyzed, which leads to the development of a concept for a new system.
The results of this analysis is used to build a set of analysis models that lead to a system proposal, which is a document presented to the project sponsor and other key individuals who decide whether the project should move forward.
The design phase decides how the system will operate, in terms of
the hardware, software, and network infrastructure;
the user interface, forms, and reports that will be used;
and the specific programs, databases, and files that will be needed.
The desing phase uses the deliverables of the analysis phase and prepares the blueprint for the new information system to be built.
The first design step is the Design Strategy, which clarifies whether the system will be developed in-house or purchased from outside.
Then Architecture Design step describes the hardware, software, and network infrastructure that will be used.
After that, we define what data will be stored and where it will be stored by determining Database and File Specifications.
And lastly as part of the Program Design step, we determine what programs need to be written and what each will do.
As part of the implementation phase, the system is either developed or purchased (in the case of packaged software) and installed.
The implementation is usually the longest and most expensive part of the process.
During implementation, the system is built or purchased and then tested on a test platform to make sure it performs as designed.
Then, if there was an old system, it is turned off and the new one is turned as part of the Installation step
Finally, at the Support Plan Step a post-implementation review and a systematic way for identifying changes are performed and maintenance plans are finalized.
So, throughout the semester, we will cover these four phases of systems development as we study the analysis and design of health information systems.