System anatomy · 05

Clinical function and claim

Translate robotic positioning, navigation, manipulation or assistance into a bounded clinical function and measurable output.

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

FUURAA thesis

Architecture should follow the authorised clinical claim, not expand it by implication.

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

Input

Specify patient data, imaging, instruments and operator commands.

02

Function

Separate sensing, recommendation, constraint, execution and monitoring.

03

Output

Define accuracy, uncertainty, timing and required clinician interpretation.

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

    What function is medically necessary?

  2. 02

    What does the robot not decide?

  3. 03

    How is uncertainty shown?

  4. 04

    Which failure changes care?

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

    Function-and-claim specification

  2. 02

    Evidence package 2

    Input-output verification

  3. 03

    Evidence package 3

    Clinical interpretation protocol

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.