15 Digital Health Implementation Flashcards

(30 cards)

1
Q

What makes digital health implementation different?

A

Digital tools change work invisibly as well as visibly. Hidden workflow impacts and tight coupling to systems mean small interface changes can have large downstream effects.

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

Why do many digital tools fail after launch?

A

Because usability and workflow fit were underestimated. Technical success does not equal implementation success, and burden often emerges later.

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

What is the most common digital health myth?

A

That automation reduces workload by default. Work often shifts rather than disappears, creating new monitoring and shadow work.

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

What determinant most strongly predicts digital adoption?

A

Perceived usefulness in real work, such as time saved or errors reduced. If value is not felt immediately, adoption stalls.

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

Why is usability critical in digital health?

A

Because cognitive load accumulates quickly in environments with interruptions and multitasking. Usability failures are often mislabelled as user resistance.

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

What does workflow integration mean digitally?

A

The tool fits naturally into existing task sequences at the right time and place. Extra logins and screens kill momentum.

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

Why do pilots overestimate digital success?

A

Because pilots receive extra support and tolerance, with fewer competing demands. Pilots hide scale-related friction.

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

What is alert fatigue?

A

Desensitisation caused by excessive or low-value alerts. Noise overwhelms signal and attention degrades.

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

Why are defaults powerful in digital systems?

A

Because most users accept pre-set options. Defaults reduce decision load and silently shape behaviour, for better or worse.

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

What is a common digital workflow failure mode?

A

Designing for happy paths only. Ignoring edge cases leads to workarounds, where real work actually lives.

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

Why does interoperability matter for implementation?

A

Because fragmentation increases workload and error risk through duplicate entry and lost information. Non-integrated tools feel optional and fragile.

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

What is the risk of partial digitalisation?

A

Creating hybrid workflows that are slower than either option. Double documentation and confusion are common.

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

Why is data quality an implementation issue?

A

Because poor data undermines trust and usefulness. Garbage in leads to garbage out, eroding confidence and adoption.

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

What does design for failure mean digitally?

A

Assuming systems will go down or behave unexpectedly. Downtime plans and safe fallbacks are essential for trust.

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

Why is digital training often insufficient?

A

Because systems, not memory, should support correct use. Training decays, but design persists.

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

What role does trust play in digital health adoption?

A

Users must trust accuracy, intent, and consequences. Clinical risk and liability concerns slow use even when tools are accurate.

17
Q

Why do digital tools increase perceived surveillance?

A

Because data visibility changes accountability dynamics. Performance anxiety and defensive behaviour can distort use.

18
Q

What is a digital workaround?

A

An informal practice to bypass system friction, such as screenshots or parallel notes. Workarounds signal misfit, not ingenuity.

19
Q

Why must digital adaptation be governed?

A

Because small changes can have large effects. Uncontrolled tweaks cause version drift and hidden risk.

20
Q

What determinant often limits digital sustainment?

A

Ongoing maintenance burden, including updates and support load. Without ownership, decay is inevitable.

21
Q

Why is vendor dependency a risk?

A

Because vendor and organisational priorities may diverge over time. Update cycles and feature creep require governance.

22
Q

How does digital health amplify inequity risk?

A

Because access and literacy vary widely. Device access and language barriers mean digital reach is never uniform.

23
Q

What is technology-induced error?

A

Error created or amplified by system design, including poor interfaces and automation surprises.

24
Q

Why must evaluation be continuous for digital tools?

A

Because systems evolve through updates and use. Static evaluation misses drift and new failure modes.

25
What signals healthy digital adoption?
Routine use without extra support or escalation. Few workarounds and stable performance indicate success.
26
Why do digital rollouts need phased strategies?
Because learning and stabilisation take time. Big-bang launches magnify defects.
27
What role does OHFE play in digital implementation?
Making invisible work and risk visible through usability insight and workflow mapping. HF bridges technology and real work.
28
Why is user resistance a weak explanation digitally?
Because resistance often reflects rational adaptation to system pressure. Listen before labelling.
29
What is the biggest digital implementation mistake?
Treating go-live as the finish line. Support drops and learning stops, but go-live is only the beginning.
30
In one line, what determines digital health success?
Whether the technology reliably makes real work easier and safer.