Reading method · 03

Separate evidence layers

Keep engineering verification, usability, clinical performance, regulatory status and operational outcomes distinct.

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

FUURAA thesis

Evidence travels only as far as its design, population, comparator and jurisdiction permit.

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

Technical

Measure accuracy, latency, force, reliability and software behaviour.

02

Clinical

Measure patient-important benefit and harm against relevant care.

03

Regulatory

Record jurisdiction, pathway, authorised wording and conditions.

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 exact question did the study answer?

  2. 02

    Was the comparator clinically relevant?

  3. 03

    Is the evidence independent and reproducible?

  4. 04

    Which claim remains unsupported?

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

    Claim-to-evidence matrix

  2. 02

    Evidence package 2

    Study protocol and complete results

  3. 03

    Evidence package 3

    Regulatory decision and labeling

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.