Medical Devices

Device Verification Test Review

Develop AI Agent Skills from how verification specialists assess an unexpected result using the tested configuration, method suitability, and differences between comparable runs. Help an agent assemble a test-review brief that preserves the original result, compares run conditions, and identifies questions for investigation.

A white polymer connector held in a mechanical test fixture with steel jaws and warm ochre instrument accents.
The people

Verification engineers, laboratory specialists, and device quality teams

The moment

A verification test produces a result the team did not expect

The opportunity

Carry the test conditions with the test result

The work behind the work

A failed result needs its full experimental context

A connector fails a mechanical test after an earlier version passed. The device revision, fixture setup, and test software have all changed since that run. The lab needs to preserve the result and explain which comparisons are meaningful before anyone proposes a repeat test.

Inside the reasoning

Bring the result, configuration, and method into one review

An unexpected connector result is a starting point for investigation. Make the differences between runs visible without assuming the cause.

Raw resultsDevice versionTest setupInvestigationReview brief
Explore the context an expert would bring to the next decision.
The skill to develop

Preserve what the test actually showed

Keep the original data, acceptance criteria, observed failure, and protocol deviations together. Separate measured observations from explanations proposed after the result was known.

Ask the expert

What did the approved test measure, and where did the observation depart from the expectation?

The skill to develop

Establish whether the runs are comparable

Compare specimen history, device revision, fixture alignment, calibration status, environmental conditions, and software version. Capture the specialist’s reasoning about which differences could affect the measurement.

Ask the expert

Which difference prevents a direct comparison with the earlier passing run?

The skill to develop

Prepare the question before proposing a retest

Document competing explanations and the evidence needed to distinguish them. A repeat result does not erase the original failure. Keep investigation and retest decisions with the authorized test and quality owners.

Ask the expert

What would another run resolve that the current evidence cannot?

The test lead and quality reviewer determine the investigation, any authorized retest, and acceptance against the approved protocol.

From expertise to an AI Agent Skill

Preserve the reasoning behind a credible test comparison

Review an unexpected result with the laboratory specialist who investigated it. Capture how they separated a possible device issue from method and setup questions. Use that explanation to develop a skill for preparing future verification reviews.

Explore AI Skill Engineering
CasesSourcesExperienceExpert reasoningReviewed skill
Connect the source, preserve the explanation, review the conditions for reuse.
Start with
  • Approved protocol, acceptance criteria, and raw results
  • Device configuration, sample history, and fixture setup
  • Instrument calibration, test-software version, and deviation records
One case is a useful beginning

Bring a test result that needed investigation

Start with the original data, the approved protocol, and two runs worth comparing. Include the specialist who can explain the limits of that comparison.

RapidKT Plain Text Website