System anatomy · 06

Human control and interface

Map clinician authority, feedback, critical tasks, automation surprises and emergency action in every mode.

Evidence statusClinical evidence framework · intended use, jurisdiction and care-pathway validation requiredLast reviewed: 15 August 2026
06

FUURAA thesis

A clinician-in-the-loop label is meaningful only when control, comprehension and response time are tested.

Engineering map

Turn the title into engineering objects that can be observed, measured and reviewed.

Each layer states the boundary to establish and the evidence needed for the next decision.

01

Authority

Assign initiate, modify, pause, override, abort and convert decisions.

02

Feedback

Expose mode, state, uncertainty, force, delay, alarm and loss of function.

03

Critical tasks

Test realistic users under representative workload and environment.

Verification questions

Write the questions first, then decide whether a demo, test, pilot or operating record can answer them.

Each question needs an object, conditions, denominator, threshold and accountable decision owner.

  1. 01

    Can the user detect the wrong mode?

  2. 02

    What requires immediate action?

  3. 03

    Can alarms be prioritised correctly?

  4. 04

    Does training transfer to emergencies?

Evidence to preserve

Enable the next reader to reconstruct conditions, results, failures and the decision.

A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.

  1. 01

    Evidence package 1

    Use-related risk analysis

  2. 02

    Evidence package 2

    Formative and validation study records

  3. 03

    Evidence package 3

    Mode and emergency-action test

Scope boundary

State what this evidence still cannot be generalised to.

Sources and evidence status

Read standards scope, measurement evidence and application conclusions separately.

Source dates and review status remain visible; external sources open in a new tab.