Knowledge Areas
Requirements
Roles & Responsibilities
Acronyms
Plans
Change is Hard
PM Random
100

this knowledge area focuses on what a stakeholder does to achieve the fundamental objectives of the project

realization page 198

100

What is a high-level user requirement?

a general description of features and functions that a system must perform to meet user needs. (page 121)

100

a register of who is accountable for the achievement of each objective

an objectives responsibility list

100

EHR

electronic health record

100

a description of how an organization plans, controls, and closes continuous improvement of an innovation

optimization management plan page 232

100

What are the 5 properties established to address why organizational leadership tends to resist change

measurability, predictability, accountability, respectability, suitability

slide 5/ch 5

100

SaaS addresses what. (x3)

architecture, performance and reliability, and security 

table 4.11

200

how many knowledge areas are there for change management and where do they come from?

5 they do not come from any standards like PMBOK or SWEBOK

200

provide one of the ways a project team can create a requirements baseline

expert information, bottom up, top down, reference project (page 124)

200

who is responsible for preparing FAQ's, videos, handouts, scenario-based examples, skills assessments etc. 

training manager page 228

200

UML

unified modeling language page 128

200

a timetable that identifies when the project will achieve outcomes

an outcome delivery schedule page 200

200

Why is change management essential?

prevents project failure

helps add value to projects

helps solve problems

slide 3/ch 5

200

The installation of network cables, wireless networks, or power-supply upgrades are examples of what

facility modification (4.4)

300

this knowledge area involves technical maintenance of the system after cutover

support management page 185

300

What might a detailed user requirement include?

page 128-129

300

this is a listing of all groups affected by the project classified according to their level of influence and support for the project

stakeholder map page 217

300
SMART

specific, measurable, achievable, relevant, timebound 

300

a description of how an organization plans to move and/or transform data from an existing manual or automated system to a new system

conversion plan page 149

300

What are the 2 fundamental reasons why someone would resist change

change is incredibly challenging and change management is relatively new

slide 3/ch 5

300

Name a describe a meeting norm

requiring attendance

stopping digressions

getting unstuck

conducting purposeful interruptions

controlling

awakening shy participants

ending distractions

Page 126-127

400

This knowledge area involves planning, executing, controlling, and closing system access

security management page 165

400

These should define only the specific technology that is mandatory.

high-level technology requirements page 138

400

What is a security role?

the list of system functions for a specific user or user type--it identifies who does what in a system page 166

400

HDO

healthcare delivery organization

400

a description of how an organization identifies, schedules, and completes changes to its facilities to accommodate a new system.

facility modification plan page 140

400

software configuration generally takes one of two forms. what are the two forms?

configuration

modification

400

A grouping of activities by actor into parallel lanes. 

a swim lane diagram

500

This knowledge area involves implementation of information exchanges between two systems. 

interface management page 169

500

This is a written verification that completed data cleansing meets requirements for conversion and subsequent system use

data cleansing confirmation

500

this is a description of the position and function assigned to each person responsible for support

roles and responsibilities matrix page 185

500

CRT

change requirements team page 186

500

what steps does a project team complete to prepare a workflow management plan?

define current workflow

review completed configuration requirements

prepare a future state workflow

identify the gap between current and future

develop a schedule for SME's to prepare and document workflow changes that close the gap

 page 161

500

What is the first step to enable and encourage the stakeholders to begin the journey of changes?

establish a sense of urgency page 162

500

What is a process that may be included in system cutover?

page 183

600

which knowledge area involves mentoring a project's most senior leader?

sponsorship management

600

what must be included in defining configuration requirements?

these are like creating a data dictionary or instruction manual.

page 158-159

description of custom fields, decisions, display choices/options, may include annotated screenshots. 

600

What is a cutover team and what are they responsible for?

page 181-182

600

SME

subject matter expert

600

a training plan template includes several components what are 2?

page 227

target audience

training levels

training modality

curriculum

schedule

feedback

logistics

standards

deliverable

resources

deadline

600

change manager, change agent, and stakeholders are all participants of the 

change team page 216

600

what is a data conversion map?

page 151-153

700

How many IT knowledge areas are there and where do they come from?

10 from SWEBOK

700

What is an example of a security requirement?

page 167

700

vendor support staff may be available in a number of different ways such as?

online instructions

online video

schedule specific training

technical support calls and email

knowledge base consisting of templates, guidelines, configurations, and other implementation, management, and technical information 

page 187

700

JAD

joint application design (page 124)

700

what are the 4 steps to a software confirguration plan?

identify and train project team

identify and document configuration requirements

complete configuration

review, confirm, and update configuration

page 157-158

700

clinicians almost always go through a period of what after cutover?

decreased productivity page 197

700

the process of identifying and resolving corrupt or inaccurate information so that it will convert properly to a new system.

data cleansing page 154

800

What knowledge area would you find white box testing in?

test management page 177

800

A description of what an organization and vendor will do to address issue logging, escalation and resolution, and system updates. 

system support requirement

800

this individual is a trusted leader who influences other people's behaviour. 

opinion leader page 215

800

SaaS

software as a service

800

What plan is a description of how an organization plans to successfully identify and manage stakeholder system needs?

a user requirements management plan

800

often resistance to change comes simply from what

misunderstanding page 214

800

what are the 5 rights?

collection of measures that hold a healthcare practitioner accountable. 

right drug

right patient

right does

right route

right time

page 200

M
e
n
u