WGU C790 NURSING INFORMATICS STUDY
GUIDE 2026 PRACTICE QUESTION SET TWO
◉ project dashboard. Answer: allows all types of project information
to be posted and viewed by Web browsers
◉ project iteration schedule. Answer: the list of iterations and use
cases or user stories assigned to each iteration
◉ detailed work schedule. Answer: the schedule that lists, organizes,
and describes the dependencies of the detailed work tasks
◉ Work Breakdown Structure (WBS). Answer: the list or hierarchy
of activities and tasks of a project; used to estimate the work to be
done and to create a detailed work schedule
◉ Gantt chart. Answer: a bar chart that portrays the schedule by the
length of horizontal bars superimposed on a calendar
◉ critical path. Answer: a sequence of tasks that can't be delayed
without causing the entire project to be delayed
,◉ retrospective. Answer: a meeting held by the team at the end of an
iteration to determine what was successful and what can be
improved
◉ Core Process 1. Answer: the objective of which is to identify the
business need and to get the project initiated. These activities
include:
▪ Identifying the problem
▪ Extending the project approval factors
▪ Performing risk and feasibility analysis
▪ Reviewing with the client and obtaining approval
◉ Tall Man Lettering. Answer: mixed case lettering
ie NiFEDipine
◉ scope creep. Answer: occurs when requirements are added after
the initial project is defined and those added requirements are
substantial enough to affect the project timeline.
◉ Best of Breed implementation of EHR. Answer: involves reviewing
several vendors for their "best" module or application, such as an
admission, discharge, and transfer (ADT) system or emergency
,department module. Then multiple modules are purchased from
different vendors to create a full suite of functions.
◉ Integrated Health System. Answer: an electronic health record
system that includes a suite of modules to support care. It is typically
easier to install and easier to support and usually has a similar-
looking user interface across modules, which helps users to learn
the EHR more quickly.
◉ Systems Life Cycle SLC. Answer: Analyze: The existing
environment and systems are evaluated. Major problems and
deficiencies are identified using informal or formal methods. A
needs assessment is developed. Gaps are noted and current
capabilities and limitations are outlined. Initial user and system
requirements are formulated.
•Plan: The proposed system is planned comprehensively. Planning
includes strategic levels, such as whether the system will be
developed internally, purchased and tailored, or designed and
developed jointly with a vendor.
•Develop or purchase: At this stage either the system is purchased
or the new system development begins. New components and
programs are obtained and installed. For vendor-supported
solutions, extensive tailoring occurs.
, •Test: At this stage extensive testing occurs just before Stage 5 and
"go" or "no go" decisions are made about deadlines. Toward the end
of this phase, marketing and communication efforts are accelerated
to make users aware of the impending change.
•Implement or go-live: The system is implemented using a selected
method best suited to the organization and its tolerance for risk.
User training is completed.
•Maintain and evolve: Once the system has been formally
acknowledged as passing user acceptance testing, typically at 90 or
120 days after go-live, it enters a maintenance phase.
•Evaluate: Activities in each phase are assessed for their quality and
effectiveness.
◉ workaround. Answer: a method used to circumvent a problem
without solving it
◉ ADT Testing. Answer: ADT testing involves testing for every
possible type of ADT transaction used in the organization for
inpatients, outpatients, serial patients, and preadmits. These
transactions include admit; discharge; transfer; cancel admit; cancel
discharge; cancel transfer; change beds, rooms, or departments;
merge accounts; etc.
GUIDE 2026 PRACTICE QUESTION SET TWO
◉ project dashboard. Answer: allows all types of project information
to be posted and viewed by Web browsers
◉ project iteration schedule. Answer: the list of iterations and use
cases or user stories assigned to each iteration
◉ detailed work schedule. Answer: the schedule that lists, organizes,
and describes the dependencies of the detailed work tasks
◉ Work Breakdown Structure (WBS). Answer: the list or hierarchy
of activities and tasks of a project; used to estimate the work to be
done and to create a detailed work schedule
◉ Gantt chart. Answer: a bar chart that portrays the schedule by the
length of horizontal bars superimposed on a calendar
◉ critical path. Answer: a sequence of tasks that can't be delayed
without causing the entire project to be delayed
,◉ retrospective. Answer: a meeting held by the team at the end of an
iteration to determine what was successful and what can be
improved
◉ Core Process 1. Answer: the objective of which is to identify the
business need and to get the project initiated. These activities
include:
▪ Identifying the problem
▪ Extending the project approval factors
▪ Performing risk and feasibility analysis
▪ Reviewing with the client and obtaining approval
◉ Tall Man Lettering. Answer: mixed case lettering
ie NiFEDipine
◉ scope creep. Answer: occurs when requirements are added after
the initial project is defined and those added requirements are
substantial enough to affect the project timeline.
◉ Best of Breed implementation of EHR. Answer: involves reviewing
several vendors for their "best" module or application, such as an
admission, discharge, and transfer (ADT) system or emergency
,department module. Then multiple modules are purchased from
different vendors to create a full suite of functions.
◉ Integrated Health System. Answer: an electronic health record
system that includes a suite of modules to support care. It is typically
easier to install and easier to support and usually has a similar-
looking user interface across modules, which helps users to learn
the EHR more quickly.
◉ Systems Life Cycle SLC. Answer: Analyze: The existing
environment and systems are evaluated. Major problems and
deficiencies are identified using informal or formal methods. A
needs assessment is developed. Gaps are noted and current
capabilities and limitations are outlined. Initial user and system
requirements are formulated.
•Plan: The proposed system is planned comprehensively. Planning
includes strategic levels, such as whether the system will be
developed internally, purchased and tailored, or designed and
developed jointly with a vendor.
•Develop or purchase: At this stage either the system is purchased
or the new system development begins. New components and
programs are obtained and installed. For vendor-supported
solutions, extensive tailoring occurs.
, •Test: At this stage extensive testing occurs just before Stage 5 and
"go" or "no go" decisions are made about deadlines. Toward the end
of this phase, marketing and communication efforts are accelerated
to make users aware of the impending change.
•Implement or go-live: The system is implemented using a selected
method best suited to the organization and its tolerance for risk.
User training is completed.
•Maintain and evolve: Once the system has been formally
acknowledged as passing user acceptance testing, typically at 90 or
120 days after go-live, it enters a maintenance phase.
•Evaluate: Activities in each phase are assessed for their quality and
effectiveness.
◉ workaround. Answer: a method used to circumvent a problem
without solving it
◉ ADT Testing. Answer: ADT testing involves testing for every
possible type of ADT transaction used in the organization for
inpatients, outpatients, serial patients, and preadmits. These
transactions include admit; discharge; transfer; cancel admit; cancel
discharge; cancel transfer; change beds, rooms, or departments;
merge accounts; etc.
