Deployment evaluation · 13

Authorised intended use

Verify the current primary regulatory record before relying on a product page, hospital announcement or research paper.

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

FUURAA thesis

Regulatory status is jurisdiction-, configuration- and claim-specific.

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

Record

Capture authority, pathway, decision date, identifier and holder.

02

Scope

Extract indication, population, operator, environment and contraindications.

03

Configuration

Match model, software, accessories, instruments and labeling revision.

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

    Is the record current and primary?

  2. 02

    Does the marketed name match the authorised model?

  3. 03

    Is use off-label or investigational?

  4. 04

    What conditions attach to use?

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

    Regulatory record snapshot

  2. 02

    Evidence package 2

    Label-to-claim comparison

  3. 03

    Evidence package 3

    Configuration and jurisdiction matrix

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.