CHIA D Flashcards

1
Q

What do leaders do? (7)

A

Leaders:
• Realistically appraise the leadership scenario and the forces at play.
• Think ahead
• Set directions and accept responsibility for them.
• Communicate with, motivate, empower, align and assign people, and instil a culture.
• Remove barriers and create connections.
• Build critical mass, and get things done through others.
• Keep their eye on the main game.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What characteristics do leaders have? (7)

A

Leaders:
• Trust and are trusted. They earn respect rather than expecting it.
• Demonstrate empathy and other forms of emotional intelligence.
• Engender confidence and hope, including through volatile situations.
• Build shared beliefs and commitment to a cause.
• Are self-aware, reflect, and adapt their style as required.
• Appreciate and nurture talent and diversity.
• Are resourceful and value resourcefulness in others.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Where skills do leaders have? (7)

A

Leaders are skilled at:
• Identifying what needs to happen.
• Taking action.
• Listening and providing feedback. Communicating and influencing.
• Thinking critically and making decisions.
• Building relationships and collaborating.
• Setting goals.
• Motivating and mentoring.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Exemplary (or authentic) followers:

A

• Are knowledgeable and enthusiastic individuals with the capacity to engage in the decision-making process, embrace change and responsibility, and establish trust and enduring relationships.
• Follow and trust a leader and challenge the leader to bring their shared vision to life.
• Distinguish themselves as proactive, responsible and independent members of a team.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

the 4 Robert Kelly Role based followers

A
  1. Exemplary (Active + Independent)
  2. Alienated (Passive + Independent)
  3. Passive (Passive + Dependant)
  4. Conformist (Active + Dependant)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Limited evidence suggests that engaged staff provide:

A

safer, higher quality care and are associated with greater patient satisfaction and health outcomes in addition to productivity factors such as absenteeism and turnover

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Micro level leadership stratergies

A

The micro-level concerns the strategies that an individual uses to lead effectively. These include painting a clear picture of the future, engaging and connecting stakeholders, communicating, and developing others.

The crucial factor at the micro-level is to actively select a context-appropriate leadership strategy based on scenario analysis rather than taking a ‘this is how I lead’ approach. In other words, the choice of leadership strategies must be cognisant of the characteristics of the followers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Macro level leadership stratergies

A

The macro-level involves creating a leadership map – a strategic pathway that ensures sufficient and effective leadership and followership capabilities will be available as and when needed. Examples of macro-level leadership strategies include building collaboration amongst leaders, developing leadership culture, and optimising balances between leaders and followers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Steps in undertaking a micro level leadership scenario analysis include:

A

• Understanding the followers as individuals and a team. Who are they, what motivates and influences them, what values they hold, what attributes they have, and what relationships they have?
• Understanding the organisational context. What is being asked of the team, how much scope will it have to make choices, will it be supported from above, below and by peer groups, how complex will the structural, process and people challenges be, what dependencies are there?
• Understanding the digital health initiative. What’s required, how precise are the requirements, how widely ‘owned’ are they, how big a leap will it be?
• Understanding yourself. How well do the leadership requirements align with your leadership strengths, how will you build up areas of weakness, are you relying on self-awareness or 3600 feedback?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Steps in undertaking a macro level leadership scenario analysis include:

A

• How many leaders are required, where, and with what qualities?
• The specific leadership knowledge, skills and experience needed to implement the business strategy.
• The collective capabilities required from the organisation’s leaders when they act together.
• The desired leadership culture.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Anderson and Ackerman Anderson identify three types of change occurring in organisations today.

A

• Developmental change – improving the status quo (e.g., improving workflows to improve efficiency).
• Transitional change – replacing the status quo with something new but known (e.g., decommissioning an existing EHR and implementing a new one with greater functionality but which does essentially the same).
• Transformational change – radical change to a new and unknown future (e.g., shifting from a ‘bricks and mortar, face-to-face’ provider to digital/virtual first). This requires inventing the future.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

IT governance (2)

A

• Is the responsibility of the board of directors, under the leadership of the chairperson (though specific governance responsibilities may be delegated, particularly in larger, more complex enterprises).
• Ensures stakeholder needs are evaluated to determine agreed enterprise objectives, direction is set through prioritisation and decision making, and performance and compliance are monitored

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

COBIT 2019‘s IT governance model comprises seven components

A

• Organisational structures – the enterprise’s key decision-making entities for IT governance. These include the Board and relevant board subcommittees, the executive V3.03 June 2023 271
team, key personnel such as the chief digital/information/technology officer, and relevant steering committees.
• Culture, ethics and behaviours – the intrinsic factors that influence why and how people act.
• Principles, policies and procedures – the articulation of governance requirements.
• People, skills and competencies – the enterprise’s human capabilities.
• Processes – the organised set of practices via which governance activities are performed.
• Information – the information required for the effective functioning of the governance system.
• Services, infrastructure and applications – the technologies and resources used for IT governance.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

SEI capability maturity model

A
  1. Initial - Unpredictable, poorly controlled, and reactive. Organisations in this stage have an unpredictable environment that leads to increased risks and inefficiency.
  2. Managed - Governance components are in place, but governance is frequently reactive.
  3. Defined - Governance is well-characterised and well-understood. The organisation is more proactive than reactive, and organisation-wide standards provide guidance.
  4. Quantitatively managed - Governance is measured and controlled. The organisation uses quantitative data to implement predictable processes that meet organisational goals.
  5. Optimising - Governance is stable and flexible. The organisational focus is on continued improvement and responding to changes.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Some common and resounding priorities from the literature on IT governance include (6)

A

• IT is a major contributor to organisational performance from value and risk perspectives. Therefore, IT governance needs to be explicitly on the agendas of organisations’ highest levels of executive oversight.
• Responsibilities at these highest levels include Articulating IT governance responsibilities and assigning them to competent people, Formulating IT plans and policies and ensuring that IT activities align with the organisation’s objectives, capabilities and contexts, Articulating strategic and regulatory compliance requirements associated with / impacted by IT and ensuring these are met, Ensuring that IT value propositions are articulated and delivered in line with expectations, Understanding the organisation’s level of IT governance maturity and ensuring that this aligns with expectations.
• Robust governance processes are required to ensure that there is clear alignment between business goals, priorities and activities and ICT projects and service provision, including:
• Alignment of planning processes is essential
• IT service and project performance level requirements must be clearly articulated and communicated to all relevant stakeholders. Business continuity must be protected.
• IT performance must be measured and managed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Ethical principles commonly cited in health care include: (7)

A

• Autonomy. This holds that all persons have a fundamental right to self-determination and is based on respect for individuals’ ability to make informed decisions about personal matters.
• Equality and justice. This holds that all persons are equal and have a right to be treated accordingly.
• Beneficence holds that all persons have a duty to advance the good of others where the nature of this good is in keeping with the fundamental and ethically defensible values of the affected party.
• Non-malfeasance holds that all persons must prevent harm to other persons insofar as it lies within their power to do so without undue harm to themselves.
• Impossibility. This holds that all rights and duties are subject to the condition that it is possible to meet them under the applicable circumstances.
• Integrity holds that whoever has an obligation has a duty to fulfil that obligation to the best of their ability.
• Honesty holds that all persons should be honest (candid and truthful) in all communications and actions since honesty is the cornerstone of trust.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Ethical principles commonly cited in health informatics: (7)

A

• Information privacy and disposition holds that all persons have a fundamental right to privacy, hence controlling the collection, storage, access, use, communication, manipulation, and disposition of data about themselves.
• Openness holds that the collection, storage, access, use, communication, manipulation, and disposition of personal data must be disclosed in an appropriate and timely fashion to the subject of those data.
• Security holds that data legitimately collected about a person should be protected by all reasonable and appropriate measures.
• Access holds that the subject of an electronic record is entitled to access to that record and correct the record for accuracy, completeness, and relevance.
• Legitimate infringement holds that the fundamental right of control over the management of personal data is conditioned only by the legitimate, appropriate and relevant data needs of a free, responsible and democratic society and by the equal and competing rights of other persons.
• The least intrusive alternative holds that any infringement of a person’s privacy and/or control rights may only occur in the least invasive fashion and with a minimum of interference with the affected person’s rights.
• Accountability holds that any infringement of the privacy and/or control rights of a person must be justified to the affected person in a timely and appropriate fashion.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

The Seven-Step Method for Analysing Ethical Situations (Hamilton, 1990) provides a framework for assessing and resolving ethical dilemmas. The method involves answering seven questions – what or who are the

A

.• Facts?
• Ethical issues?
• Alternatives?
• Stakeholders?
• Ethics of the alternatives?
• Practical constraints?
• Actions that could be taken?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

5 Ethical perspectives

A

The utilitarian approach
Utilitarianism was conceived in the 19th century to help legislators determine which laws were morally best. The most ethical actions provide the greatest balance of good over ‘evil’. Analysis via the utilitarian approach involves asking who will be affected by each action and what benefits or harms will be derived and choosing the action that will produce the greatest benefits for the greatest number and the least harm.

The rights approach
This approach focuses on the individual’s right to choose for themself. It is important to question whether or not the action undertaken respects the moral rights of everyone. Actions are wrong to the extent that they violate the rights of individuals, and the more serious the violation, the more wrongful the action.

The fairness or justice approach
This approach is based on Aristotle’s view that ‘equals should be treated equally and unequals unequally’. The primary measure of this approach is how fair it is as an action: does it treat everyone in the same way, or does it show favouritism/discrimination?

The common-good approach
This approach to ethics assumes a society comprising individuals whose own good is inextricably linked to the community’s interest. Community members are bound by the pursuit of shared values and goals. The focus of this approach is on ensuring benefit to all.

The virtue approach
This approach assumes there are certain ideals toward which all should strive., Questioning via this approach considers: what kind of people/community are we?

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

ICT -Business streatergy Alignment is a complex task that must consider that:

A

• Business and information systems strategies require “vertical coherence” – they must be internally consistent.
• Alignment is likely to be required at multiple levels.
• Alignments work in both directions – ICT advances can enable business strategy shifts and respond to them.
The whole strategic environment is fluid, although fundamentally, the business should lead ICT.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

The Strategic Alignment Maturity (SAM) model views business-IT alignment as “a continuous process of adjusting activities across multiple dimensions that together results in improved/better alignment” (Luftman, Lyytinen & ben Zvi, 2017, p.31). It posits that six governance activities collectively contribute to business-IT alignment and improve organisational performance.

A

• Communication – the intensity and quality of the dialogue between IT and business personnel. Listening is key.
• Value analytics – the use of metrics to validate the contributions of IT and the IT organisation to the business in terms that both business and IT personnel understand and respect.
• IT Governance – see chapter D.2.
• Partnering – the nature and level of the relationship between business and IT personnel. Partnerships are typically characterised by mutual trust, commitment to shared goals, and shared risk-taking.
• Dynamic IT scoping – the generation of shared activities that allow IT the agility to enable timely business changes.
• Business and IT skill development – ensuring the organisation’s readiness for change, learning capability, and ability to leverage new ideas.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

benefits associated with effective stakeholder engagement include (7)

A

• Discovery of important relationships.
• Opportunities to discover and validate needs, identify the likely best ways forward and identify and deal with potential barriers.
• Overall, cost and time savings – stakeholder engagement requires resources but can mitigate the likelihood of errors, dead ends, and rework.
• Improved identification and mitigation of risks.
• Improved expectation management.
• Long-term relationship building.
• Enhanced reputation/brand.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

principles underpinning effective stakeholder engagement and relationship management 10)

A

• Purpose – every stakeholder engagement process begins with a clear understanding of the achievements desired.
• Inclusiveness – relevant stakeholders are identified, and strategies are implemented to facilitate their engagement, noting that some stakeholders may be harder to reach than others. Power imbalances between stakeholders are acknowledged and their potential impacts mitigated.
• Diversity of stakeholders and their views is valued.
• Timeliness – stakeholders are engaged from the beginning, and their input is obtained within timeframes that permit its due consideration.
• Transparency – stakeholder engagement is open and honest, and the expectations of all concerned are clear.
• Integrity – relationships feature consistency in decision-making and action-taking.
• Respect – stakeholders’ expertise, perspectives, and needs are acknowledged, respected, clarified, and validated.
• Reciprocity – relationships require that time, effort, risk etc., committed by one party are reciprocated by the other(s).
• Autonomy – relationships require that parties make their own decisions, free of coercion.
• Confidentiality is respected.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

AccountAbility (2015) recommends a four-stage process for stakeholder engagement

A
  1. Plan
  2. Prepare
  3. Implement
  4. Act, review, improve
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

Planning for stakeholder engagement typically involves activities such as:

A

• Identifying, profiling, and mapping stakeholders.
• Determining which stakeholders are the most important to engage with, given the context at hand.
• Determining the desired level of engagement with each stakeholder and the most appropriate methods for achieving this.
• Developing and reviewing an engagement plan tas well as performance measures

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

Preparing for stakeholder engagement typically involves activities such as:

A

• Mobilising resources and building the capacities required for effective engagement.
• Undertaking risk analysis and mitigating identified risks.
• Setting and managing realistic expectations.
• Ensuring that stakeholder engagement will be meaningful, fair, and contribute to relationship building.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

Implementing the stakeholder engagement plan includes

A

• Inviting stakeholders, providing them with sufficient time and information to permit meaningful engagement.
• Determining and communicating the ‘rules of engagement’ (procedural and behavioural rules that should apply to all stakeholders).
• Engaging – obtaining the required stakeholder input.
• Documenting the engagement appropriately (consistent with the rules of engagement) and developing and documenting resulting outputs, plans, intentions, actions, timeframes, etc.
• Communicating the outputs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

Acting, reviewing, and improving the stakeholder engagement plan

A

• Actioning agreed plans and iterating as appropriate.
• Monitoring the implementation of the plan and dealing with issues arising. This includes communicating progress and ensuring comprehensive completion.
• Evaluating the stakeholder engagement, communicating lessons learned, and incorporating improvements into subsequent planning.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

Some barriers to stakeholder engagement (4)

A

• Poor allocation of resources to engagement is often related to low prioritisation (including competition amongst priorities). Some stakeholders may be resource-poor, but this should be identified and catered for in the planning and preparation stages.
• Lack of flexibility in and accessibility to stakeholder engagement processes. Some processes and timeframes may disadvantage some stakeholders (e.g., duty cultural, linguistic or availability issues).
• Failure to secure appropriate representation – e.g., identifying some stakeholders or securing the most appropriate (knowledgeable, empowered) representatives. This may be caused either at the engager or consultee end. For example, some stakeholders may be suffering from consultation fatigue or disillusionment.
• Inappropriate engagement processes that fail to elicit all relevant issues, hear all voices equally, build trust, etc., or are perceived by stakeholders as inappropriate.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

Advantages of organising a set of activities as a project include (8)

A

• Explicit recognition that the activities to be undertaken are not ‘business as usual’ (BAU) informs all stakeholders that change is afoot – that the future state will be different to the current one. Projects typically introduce change.
• The ability to work across BAU lines of organisational management to act on cross-cutting interests.
• The ability to aggregate and secure resources beyond BAU levels.
• The ability to isolate the requisite workstreams from those associated with business as usual may enable fast-tracking, different (more advantageous) reporting channels, and alternate decision-making processes.
• The ability to elevate the visibility of the activities concerned and the capabilities delivered.
• The ability to constrain the associated activities if required – e.g., by terminating the project, changing its scope, or scaling it up or down.
• The ability to measure, research and evaluate a discrete set of activities and learn from them before attempting something comparable elsewhere.
• Provision of a common language for understanding and communicating what is happening when it is outside the norms of business as usual.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

General steps in project management

A

Initiation, planning, controlling/executing, monitoring, closure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

PRINCE2 as a project management method

A

PRINCE2 is a generic methodology that guides project management practitioners on what to do to undertake a project. However, it does not prescribe how to undertake the project work itself. Therefore, PRINCE2 requires expertise to implement and tailor to the specific circumstances at hand.
PRINCE2 is output-oriented – each step has inputs, outputs and specific goals and activities that lead to the project’s deliverables as defined in its business case. Deviations from the business case are either challenges or opportunities.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

PMBOK as a project management method

A

Driven by specific processes
It recognises 47 processes under five groupings and ten knowledge areas.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

PRISM as a project management method

A

PRISM aims to integrate project processes with sustainability initiatives to achieve business objectives while decreasing negative environmental impacts
The critical feature of PRiSM that differentiates it from other approaches is its Sustainability Management Plan, covering five measured elements - People, Planet, Profit, Process and Product. In addition,

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

Agile as a project management method

A

The steps involved in an agile approach are similar to those discussed above – the project must be defined, planned, executed, monitored and controlled – but the emphasis is on communication, collaboration and responsiveness rather than processes
In Agile project planning, the project team works with stakeholders to schedule a series of time-boxed iterations via which outputs will be delivered, building a roadmap for delivery. However, change is assumed to be the norm in Agile projects and planning frequently results in reprioritisation as new requirements emerge or existing requirements and delivery capabilities are better understood. As a result, project delivery can involve multiple iterations.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

Considerations when choosing a project management method (6)

A
  1. The stability of/degree of confidence that can be placed in the requirements. Are they likely to evolve significantly over the course of the project?
  2. The degree of confidence that can be placed in estimation. Even if requirements are reasonably well known, is this also the case for the organisation’s capabilities to meet them?
  3. The nature of the end-user base for information system development projects. Are they a known group? A bounded one (e.g., a finite group such as employees)? Or are they potentially anyone (e.g., for a community facing product)?
  4. The agressiveness of timelines
  5. The scale of hte project and the nature of the scal
  6. The project management knowledge, skills, experience and infrastructure of the organisation. If there is already has a substantial investment in a methodology or set of methods, including access to expert practitioners, then attempting to introduce a new and different approach may elevate rather than reduce risk.
37
Q

Project management tools - Work breakdowns

A

Work breakdown structures are essentially tree and branch representations of the subdivision of activities required to achieve a project objective, such as planning the project, building a capability or delivering an output.

• Meaningful to stakeholders and governance, e.g., project phases and outputs.
• Commonly interpretable and communicate what will be done to progress the project.
• Scaled to demonstrate progress and the satisfaction of expectations.
• Reflective of the responsibilities of different parties so that under-performing areas can be identified.
• Digestible – avoiding too much detail as well as providing enough.

38
Q

Project management tools - Gantt charts

A

Gantt chart is a bar chart named after its developer16, which depicts a project schedule. Figure D.11 shows an example. It is organised around project activities (the work breakdowns) and may incorporate a wide variety of information about those activities such as:
• Levels – summary tasks and successive breakdowns.
• Start and end dates, duration and extent of completion.
• Dependencies between activities.
• Resources involved.

39
Q

Project management tools - Critical path

A

used for scheduling project activities.

Identifying the critical path (the collection of activities that determine the shortest time in which the project can be completed) requires a list of all project activities, the duration of each activity, identification of the dependencies between activities, and identification of the endpoints such as milestones or outputs.
Using these parameters, the critical path method (CPM) calculates the longest routes to the endpoints of interest and the earliest and latest that each activity can start and finish without extending the overall duration.

40
Q

Project management tools - PERT

A

Booz Allen Hamilton and Lockheed developed program Evaluation and Review Technique (PERT) in a project for the US Navy. PERT is also used to identify the critical path, but where CPM relies on known activity times, PERT allows for activity times to be uncertain or varied. PERT is a statistical technique that is typically more complex

41
Q

Project governance functions include ensuring that (8)

A

• Project requirements remain aligned with organisational priorities, are clear to and consistent between all stakeholders, and justify the investment.
• Project resources are available in forms and quantities consistent with the organisation’s project expectations.
• Stakeholders, project resources and contracts are managed appropriately.
• Relevant constraints (legal, policy, standards, ethics, etc.) are articulated and adhered to.
• Controls are established appropriate to the project and are applied in ways that provide the organisation with the levels of accountability and assurance it requires. For example, controls are needed for cost, risk, quality, communications, time, change, procurement and human resources.
• The organisation endorses the achievement of milestones and delivery of outputs.
• Known and emergent risks and issues are identified and dealt with effectively, and opportunities are recognised and leveraged.
• Lessons learned via the project are captured and translated into better practices for the future.

42
Q

Difference between project and program management

A
  1. Program management is longer-term than project management
  2. Program management is more strategic goals, whereas project management tends to be tactical goals.
    3.Program management is concerned with delivering business value, while project management provides the capabilities to realise business value,
  3. Program management is a large role as programs are inherently large than projects
  4. Program scope is broader and more flexible as programs are inherently larger and contexts change
43
Q

Kotter’s 8-step change model

A

Step 1: Establish a sense of urgency

Step 2: Create the guiding coalition
Encompassing - Positional power, expertise, credibility, leadership

Step 3: Develop a change vision
Must be - imaginable, desirable, feasible, focused, flexible, communicatable

Step 4: Communicatio the vision for buy in
must be - simple, vivid, repeatable, invitational

Step 5: Empower broad ased action
remove barriers

Step 6: Generate short term wins
visible unambiguous sucesss, rewards and increses sense of urgency and optimisim

Step 7:Never let up
use momentum

Step 8: incoprorate change into culture

44
Q

The three main components to the Prosci methodology –

A
  1. the 3-phase process
    Preparing the approach, managing the change, sustaining the outcomes
  2. the PCT model
    4 critical aspects of success - definition of success, leadership, project management & change management
  3. the ADKAR model
    Awareness, Desire, Knowldge, Ability, Reinforcement
45
Q

Change curve as a change methodology

A

The basic premises of change curve models are that when substantive change takes place in an organisation:
• Individuals tend to experience these reactions to change.
• They experience them at different rates and degrees, depending on their personal characteristics and the nature of the changes, which can have varying impacts on different parts of the organisation.
• Change leaders need to recognise that they themselves will react to the changes and people need time and support to progress through the curve.
Change management strategies are then based on these stages and their reasons. For example:
• Shock and denial can be caused by lack of information and fear of the unknown, so strategies include communication and contextualisation.
• Anger and depression can be caused by a lack of trust and a lack of control over one’s destiny, so strategies include recognising that reactions are normal, trust-building, and opportunities to shape at least some aspects of the changes.
• Acceptance and integration can be associated with excitement at recognising new opportunities and relief that disruption is subsiding, so strategies include celebration, support for experimentation and continued communication. It is crucial in these stages to keep the support levels up to prevent regression.

46
Q

The Change Leader’s Roadmap is a nine-phase process model for planning, designing, and implementing content and people changes.

A
  1. Prepare to lead change
  2. Create vision, comittimnent and capabilty
  3. Assess situation
  4. Design desired state
  5. Analyse impacts
  6. Plan and organise
  7. Implement change
  8. Celebrate success
  9. Learn and iterate
47
Q

3 stage change

A
  1. Unfreeze
    Why change is needed, how to change, stakeholders, vision and challenges
  2. Changing
    communicate, prepare, empower, engage, short term wims
  3. Refreezing
    anchor to culture, indentify enablers, continue training/support celebrate success
48
Q

Approaches to conflict resolution incorporate

A

• Ensuring that good relationships are the priority – this requires calmness, courtesy, constructiveness and efforts to build mutual respect.
• Keeping people and problems separate.
• Paying attention to the interests that are being presented – this requires real listening and understanding where the other person is coming from before defending your own position.
• Agreeing and establishing objective, observable elements that impact the situation.
• Jointly exploring options.

49
Q

Some tips for managing conflict, from various sources, include

A

• Defining acceptable behaviours – and unacceptable ones.
• Being respectful of differences. Be mindful of language.
• Maintaining a positive outlook; keeping an open mind.
• Asking for solutions.
• Articulating conflict resolution pathways, including the potential pathways to escalation, mediation, etc.
• Addressing conflict, don’t assume it will go away, but avoid conflict for the sake of conflict.
• Understanding the “What’s in it for Me” factors.
• Viewing conflict as an opportunity. Many conflicts hold learning potential.
• Following through to resolution.

50
Q

The risks associated with a project can be inherent, acquired, or contextual, define these

A

• Inherent risks are associated with the nature of the project objectives and scope. For example, a “big bang” approach to a health information system deployment may carry the risk that the scale of change required is too large for the associated timeframe organisational experience base).
• Acquired risks result from the selected organisation, approach, technology, methods, tools, techniques, skills, and experience applied to the project. For example, choosing a software product that is significantly different from others on the market and is not yet deployed anywhere risks inability to meet requirements in situ and lack of implementation experience with the product).
• Contextual risks result from events, circumstances or inter-relationships outside or across the project or system boundary and impact aspects of the project. For example, a change of government may bring the risk of substantive changes to health policy and or funding which could impact the project).

51
Q

Key processes in risk management

A
  1. establishing the context/risk management planning
  2. risk identification
  3. qualitative risk analysis/ evaluation
  4. quantitative risk analysis/ evaluation
  5. risk response planning/ risk treatment
  6. risk monitoring and control
52
Q

The preffered way to state a risk is:

A

‘There is a risk that will cause that impacts ’.

53
Q

risk assessment entails

A

• Identifying contributors by asking, for each identified source of risk, questions such as: “How could this scenario arise?”, “Under what circumstances might this happen?” and “Have we seen this scenario before, and if so, what was going on then?”
• Attempting to identify leading indicators by asking questions such as “How would we know if this risk source was in the process of materialising?”, “What timeframe would likely be involved if the risk source did materialise (e.g. if key project staff are contractually obliged to give at least 4-weeks’ notice – is that enough?) and “What may be our blind spots?”
• Categorising risks in ways that are meaningful to the project, the organisation and risk management
• Developing likelihood groupings meaningful to the project, organisation and risk management. In general: The more quantifiable a risk source, the better.The earlier a risk source can be quantified, the better.
• Assessing the likelihood of each risk source arising. The greater degree of precision with which this can be undertaken, the better.
• Developing consequence groupings meaningful to the project, organisation and risk management.
• Assessing each identified consequence against the consequence scales.
• Assessing the impacts of existing organisational controls to estimate their effects on both the likelihood and consequences of the risk sources and taking these into account, modifying the assessments if appropriate.
• Identifying scenarios in which cascading risks could occur – i.e. where the manifestation of one risk source could lead to other risks arising, taking these into account and adjusting the risk assessments if warranted.
• Validating the risk assessments by seeking stakeholder feedback, independent review, etc.
• Producing a risk matrix that maps risk sources in terms of their likelihood and consequences and denotes overall risk levels as a result

54
Q

Risk evalutiion is

A

Risk evaluation directs the identified risks to a set of treatment categories
The responsibilities associated with risk monitoring need to be clearly articulated and allocated. All risks requiring treatment must be assigned to and accepted by a risk owner, whose responsibilities include developing the treatment plan for that risk.

55
Q

Common risk treament / mitigation strategies include:

A

• Avoiding. This usually entails avoiding the activities that give rise to the risk, which may require changes to the scope of and/or approaches to the project.
• Accepting. This involves the risk owner advising that treatment options are not feasible and that the consequences will need to be managed (e.g., via business continuity or disaster recovery planning).
• Transferring. This generally involves either sharing or outsourcing the risk or insuring against it. For example, arrangements may be made with a supplier to share risk via either payment penalties or incentive arrangements. Some activities may be entirely outsourced to a third party with greater capability, or compensation may be arranged in the event of particular risks (e.g., via insurance or legal arrangements).
• Controlling. This involves directly intervening to moderate likelihood or consequences and may involve Preventive strategies , Corrective strategies, Directive strategies designed to manage towards specific outcomes if a risk eventuates , Contingency strategies
• Terminating. This is a more aggressive option than avoiding as it entails retreat from an already underway activity.

56
Q

factors associated with risk management success: (6)

A

• Strong and visible commitment from the CEO down.
• Open and transparent communication, consultation and collaboration between all relevant stakeholders/stakeholder groups.
• Effective policies and procedures congruent and well-integrated with the organisation’s ethos, directions and control systems.
• Risk ownership at the levels with the requisite motivation, capabilities and authorities.
• Continuity, in at least two senses. Firstly, risk management is a continuous and iterative process that must be sustained throughout the project and the system or data life cycle. Secondly, factors such as changes in staff (e.g., risk owner) must not be allowed to disrupt project risk management.
• Appropriate resourcing.

57
Q

Quality management’ refers to

A

any activity to maintain or improve quality, and a ‘quality management system’ is a system put in place to implement policies, objectives and processes to improve quality (Keen, 2019).

58
Q

ISO defines a quality management system as

A

a set of interrelated or interacting elements to establish the overall intentions and direction of an organisation related to quality as formally expressed by top management and to achieve those objectives”

59
Q

The ISO 9001:2015 quality management principles are

A

• Customer focus – quality management aims to meet customer requirements and exceed their expectations.
• Leadership – leaders create the conditions via which quality is delivered.
• People – staff and agents at all levels must be competent, empowered, and engaged in delivering quality.
• Processes – processes must be effective and efficient to deliver quality.
• Improvement – the quest for quality never stops, nor does the need for improvement.
• Evidence-based decision making – decisions based on evidence are more likely to deliver quality.
• Relationship management – relationships (e.g., suppliers) are also key to delivering quality and must be managed appropriately.

60
Q

The essential ISO 9001:2015 quality management processes are

A

• Articulate the organisational context. This includes analysing quality and quality management within the specific context and circumstances of the organisation, understanding stakeholder needs and expectations, and exploring the nature and scope of the requisite quality management system.
• Leading – ensuring roles and responsibilities for quality management are articulated, understood and accepted, and building a culture based on quality and stakeholders. Leadership also includes the development of quality policies.
• Planning and risk management – identifying specific quality objectives and performance measures, developing and implementing plans to fulfil these, thereby controlling quality, and identifying and managing risks.
• Supporting the quality management system, for example, by ensuring the availability of appropriate resources and capabilities, communicating, and managing.
• Operating the quality management system, including adjusting requirements as appropriate from time to time.
• Evaluating the performance of the quality management system.
• Continuously improving the quality management system.

61
Q

Lean Six Sigma is a combination of two improvement methodologies

A

• Lean focuses on creating the value required using fewer resources and generating less waste while
• Six Sigma aims to increase customer satisfaction by streamlining operations, improving quality and eliminating defects.
While these two methodologies have significant synergies – e.g., both are underpinned by a definition of value based on customer experiences, use flow mapping, and are process-oriented – they also have differences. While Lean focuses on waste and uses visual techniques, Six Sigma focuses on variability and statistical analysis. However, these differences provide multiple pathways for problem-solving rather than conflict.
Lean Six Sigma commences with a strong customer orientation

62
Q

Quality improvement involves five steps (the DMAIC cycle):

A

• Defining the problem – identifying stakeholders and their needs, articulating the problem and specifying the improvement goals.
• Measuring – identifying appropriate and effective measures, determining current performance, and articulating the gaps between current and desired performance.
• Analysing – closely examining the processes involved and their contexts (people, infrastructure and other resources, regulations, etc.), identifying the range of possible contributors to suboptimal performance and hypothesising their causes, testing the hypotheses and validating the actual reasons. This step focuses on the problems, not the solutions.
• Improving – brainstorming solutions and analysing the consequences of their use, agreeing on those to be tested/adopted, developing measures to test improvements, and operationalising the improvements.
• Controlling – sustaining the improvements and the improvement ethic, harvesting the lessons learned, assessing the potential of the solutions used for wider application, and celebrating success.

63
Q

Total Quality Management (TQM) is “a management technique based on the idea that all employees continuously improve their ability to provide on-demand products and services that customers will find of particular value” (Lucid, n.d.). It is based on eight principles:

A
  1. Customer focus. Once again, quality is defined from a customer/user perspective. Accordingly, crucial quality elements include understanding and aligning stakeholder needs and expectations and managing relationships.
  2. Total employee commitment, which requires engagement, capability building, adequate resourcing, and culture building.
  3. Process approach. The crux of TQM methods is understanding, measuring and improving processes.
  4. Integrated systems. This principle recognises that organisations comprise many different parts and that optimising organisational performance requires optimising the way these interact rather than the parts in isolation.
  5. Strategic and systemic approach. This includes prioritising strategically important issues and taking a reasoned approach to dealing with them.
  6. Continual improvement – quality is an everyday, long-term issue. Projects may be used to improve quality, but continuous attention to quality by everybody is the real requirement.
  7. Fact-based decision-making requires a focus on data and its appropriate usage and dissemination.
  8. Communications. If everybody is to be involved and engaged, then the criticality of good communication cannot be overlooked.
64
Q

General princples for quality management

A

• Commence with customer expectations as a basis for quality.
• Identify a problem – or, more specifically, an opportunity for quality improvement.
• Assess the current scenario/measure current performance.
• Undertake causal analysis.
• Develop and implement solutions leading to improvement.
• Measure, monitor and evaluate the progress.
• Sustain, modify or promulgate the solution and the approach is appropriate.

65
Q

There are various ways to categorise benefits and dis-benefits, but three important ones are by

A

source, impact versus likelihood, and stakeholder impacts.

66
Q

Some common sources of benefits and dis-benefits for health informatics projects are

A

Access
Effectiveness
Effeciency
Equity
Improved decision making
Interoperabilyt
patient centricity
privacy
revenue
rright sighting
safety and quality
secondary uses

67
Q

Impact versus Likelihood when reviewing benefits and dis-benefits for heath informatics projects

A

• Impact – the extent to which benefits are critical to business operations (clinical, managerial, etc.) and the magnitude of the benefits.
• Likelihood – the probability of achieving the benefit, considering dependencies

68
Q

Stakeholder impact when reviewing benefits and dis-benefits for heath informatics projects

A

consider extent of change required vs potential impact and adapt uptake and adoption stratergies accordingly

69
Q

Gerald Bradley advocates a six-step approach to benefits realisation

A
  1. Set the vision and objectives – this includes mapping the relationships between intermediate and ultimate objectives.
  2. Identify benefits and changes – this involves working back from the primary objectives, identifying the specific benefits associated with them and the changes required to generate those benefits. Mapping the relationships between these benefits and changes to form cause-and-effect relationships is also crucial.
  3. Define the initiatives (actions) required to generate the requisite changes and benefits.
  4. Optimise the initiatives – determining which ones will have the most impact relative to their cost.
  5. Manage the chosen initiatives and the relationships between them.
  6. Manage performance across the whole portfolio of activities associated with benefits realisation.
70
Q

The NSW Government’s benefites framework comprises a set of principles and a set of processes, together with advice concerning their use. The principles include:

A

• Benefits must be aligned to the organisation’s strategic goals.
• Benefits are the reason an investment is made.
• Benefits must be measurable and evidence-based to demonstrate that an investment provides value.
• Benefits can only be realised through change, and change can only be sustained by realising benefits.
• Benefits need to be owned by appropriate sponsors and managers, not the program/project manager.
• Intermediate benefits are required to realise end benefits (and are just as important).
• Benefits are dynamic; they need to be regularly reviewed and updated.
• Keep the number of benefits monitored and reported to a sensible, manageable number.
• Benefits management should be integrated with other organisational processes, including project management.

71
Q

The NSW Government’s benefits framework has 4 phases

A
  1. Understand
  2. Plan
  3. Manage and report
  4. Evalutate
72
Q

Many issues and challenges arise in benefits realisation, including

A

• Poor definition of benefits or ambiguities amongst stakeholders/stakeholder groups as to the benefits.
• A “crossed fingers” approach benefits realisation, otherwise known as poor leadership and management.
• Treating a business case as a one-off rather than as the basis for accountability throughout the system life cycle.
• Recognition of only those benefits that can be monetised, which is not always easy in health.
• Multiple initiatives claiming the same benefits, which guarantees that they will all underachieve.

73
Q

Value management is concerned with

A

“improving and sustaining a desirable balance between the needs and wants of stakeholders and the resources needed to satisfy them. Stakeholder value judgements vary, and value management reconciles differing priorities to deliver optimum value for all stakeholders”

74
Q

The key principles of value management have been described as

A

• A value mindset – an “unending quest” for enhancing, measuring, monitoring and controlling value for the organisation.
• Clear definition of objectives and targets before seeking solutions.
• A focus on the functions that optimise value and critical success factors.

75
Q

The three overarching phases comprising value management are

A

• Value planning. This typically focuses on identifying objectives and developing approaches to meeting these. This is where the varying requirements of different stakeholders are balanced and ranked.
• Value engineering. This is undertaken after design alternatives have been developed but before selecting a preferred choice. Value engineering maximises value by quantifying and comparing options throughout the project life-cycle.
• Value analysis is retrospective. It “analyses or audits a project’s performance by comparing a completed, or nearly completed, design or project against predetermined objectives”

76
Q

defines Business Process Re-engineering (BPR)

A

Business Process Reengineering involves the radical redesign of core business processes to achieve dramatic improvements in productivity, cycle times and quality

77
Q

Stages of process engineering (6)

A
  1. Planning
  2. Agree
  3. Discover
  4. Map and model
  5. Implrement
  6. Monitor and review
78
Q

Stages of process engineering - Planning

A

Aim: To develop the business case for change.
Involves: Articulating the context and drivers for change; identifying stakeholder expectations and likely barriers; assessing the capability and readiness of the organisation to undertake process change.
Outputs: A persuasive case for the project supported by key stakeholders, including clear articulation of the way forward.

79
Q

Stages of process engineering - Agreement

A

Aim: To obtain stakeholder agreement on how, what, when, where, and by whom the project will be undertaken.
Involves: Establishing governance structures and mechanisms; agreeing on standards and tools for both process analysis and design and workplace change; ensuring that all relevant stakeholders and engaged; initiating communication strategies.
Outputs: Key stakeholder and governance support for the way redesign will be undertaken.

80
Q

Stages of process engineering - Discovery

A

Aim: To identify good/best practices relevant to the processes(es) concerned
Involves: Gathering internal and external hard data; desk research; exemplar reviews (e.g. via site visits), stakeholder consultations.
Outputs: Understanding of good/best practices and the gaps between these and the organisation’s current practice.

81
Q

Stages of process engineering - Mapping and Modelling

A

Aim: To describe in detail the current and new processes. This is the crux of the set of stages.
Involves: Current process mapping; process and workflow analysis; process and workflow modelling; scenario analysis; gap and implementation analyses.
Outputs: Agreed new process(es) and a clear understanding of how to bridge gaps.

82
Q

Stages of process engineering - Implementation

A

Aim: To implement the re-engineered processes sustainably.
Involves: Extensive change management (see Chapter 27); capturing change metrics; communications.
Outputs: New processes.

83
Q

Stages of process engineering - Monitoring and Review

A

Aim: To ensure that the changes align with expectations and capture learnings.
Involves: Analysing, interpreting and responding to change metrics; evaluating.
Outputs: Lessons to be incorporated in future initiatives.

84
Q

ways to undertake process mapping and modelling in process engineering

A

• Using the standards, methods and levels of detail agreed in the “Agreement” stage, and if a variation to these appears desirable, reiterating through the agreement process.
• Constraining the exercise to the domain, boundaries and start and end points agreed in the “Agreement” stage.
• Using all available sources (documentation, literature, experts, all relevant stakeholders, observation) to extract details of the current processes and testing apparent conflicts arising from different sources.
• Subsequently adding formality – using the agreed mapping notations and adding in known measurements (e.g. numbers of patients/clients flowing through the process, times taken), actively searching for other issues, then re-validating with key stakeholders, resolving any conflicts and obtaining consensus.
• Modelling alternatives, supporting evidence bases and potential implications (including improvement targets).
• Validating, resolving modelling conflicts and obtaining consensus regarding the new.

85
Q

contributors to effective process improvement include

A

• Benchmarking and establishing performance targets, including cost, quality and safety.
• Establishing clinical teams for each high-variance clinical area, providing the teams with training and tools to enable them to function with high-performing.
• Incorporating changes into clinical guidelines, clinical decision support tools and order sets.
• Monitoring performance and sharing the outcomes with work teams regularly.
• Ensuring the right people are in the right roles for the project. Creating and utilising champions.
• Recognising that system transformation may be best accomplished by balancing many well-chosen rapid-cycle and system projects..
• Communicating.
• Creating a culture of accountability and continuous improvement.
• Recognising that immediate rewards are important as incentives for improving and aligning corporate and employee goals.
• Aligning organisational and staff goals.
• Securing strong stakeholder and executive commitment.
• Assigning responsibilities.

86
Q

impacts of information culture on organisations’ and individuals’ performance

A

there is a correlation between business success and information culture. Therefore, the attitudes, norms and how the employees value organizational information, impacts its efficient use and management’
The dimensions of patient safety culture can act to influence information processing in organisations because they foster not only communication and coordination, but also shared values, attitudes, and patterns of behaviour”

87
Q

Dimensions of information culture that have been examined in the literature and found to be significant contributors to good information outcomes (as defined in the studies concerned) include

A

• Sharing (willingness to make information available to others).
• Pro-activeness (diligence in obtaining and applying new knowledge).
• Transparency (desire to report on errors and failures).
• Integrity (use of information in a trustful and principled manner).
• Formality/informality (the degree to which formal (institutional) versus informal information sources are preferred/tolerated).
• Control (the degree to which information is used to manage and monitor performance).
• Commitment to training and communication concerning the effective use of information.

88
Q

Commonly cited keys to cultural change include

A

• Formulating a clear strategic vision that clearly articulates why culture change is required and the differences. This, of course, implies also knowing where the organisation is at present – which is not always obvious, and espoused values and behaviours are not always the actual ones - and identifying the gaps between current and desired.
• Displaying top-management commitment. This requires leadership by example – half-heartedness is always obvious!
• Modelling culture change at the highest level by visibly adhering to the desired behaviours and practices.
• Modifying the organisation (and its systems) to support organisational change. The status quo has been designed to be just that – the status quo. It is reflective of the current culture. This includes training required to instil new ways of seeing, thinking and behaving.
• Selecting and socialising newcomers and ‘terminating deviants’.
• Developing ethical, professional and legal sensitivity. Changes in culture can lead to tensions between organisational and individual interests – for example, between the health organisation’s intentions and clinicians’ professional values and norms.

89
Q

Examples of principles relevant to information culture include

A

Maximise Benefit to the Enterprise
Data is an Asset