Skip to main content
Quality AssuranceApril 20262 min read

When the OEM Said "Pass", VERIFLUX Said Otherwise

An NHS teaching hospital trusted its longitudinal data. The coil was already failing.

A major NHS teaching hospital in the north of England runs functional MRI on a 3T system, with scanner stability monitored through the VERIFLUX platform from Gold Standard Phantoms, using the fBIRN-compatible Veriflux phantom. In early 2026, two consecutive scans failed.

224
SNR: lowest in site history
4.69
RDC: ~4.5 correlated voxels
360 mm³
Tissue with questionable independence
18 mo
Longitudinal baseline

The team also ran their scanner manufacturer's own inbuilt fMRI stability QA, which passed. So: the OEM says the scanner is fine. VERIFLUX says it isn't. Who do you believe?

Scanner manufacturer QA
Pass

Inbuilt fMRI stability check, smaller-diameter liquid sphere phantom of unknown fill. No longitudinal context.

VERIFLUX
Fail

fBIRN protocol, synthetic polymer gel phantom, 18 months of site-specific history. Two consecutive failures.

The response

A phone call, not a ticket number

When the hospital raised the discrepancy, Prof Xavier Golay, Ph.D., CEO of Gold Standard Phantoms, reviewed the stability reports himself and wrote back with a technical analysis.

The last two uploaded scans failed because the first one had an SNR of 224, which is much lower than any of the measurements uploaded so far, and the second one had a very bad RDC of 4.69.
Prof Xavier Golay, Ph.D., CEO of Gold Standard Phantoms

He explained why the OEM result was unreliable: the manufacturer's phantom is a smaller-diameter liquid sphere with unknown fill. SNR measured on it cannot be compared directly to VERIFLUX results. He also flagged that the RDC figure indicated something was physically wrong, regardless of how SNR was being calculated. An RDC of 4.69 means correlated noise across roughly 4.5 voxels, leading to a patch of over 360 mm³ of tissue within which independence of activation will remain questionable.

What they found

The engineer visit

Two channels in the RF coil were faulty. One had a blown fuse. The root cause: a known bug in an earlier firmware version allowed B1 amplitude to be set too high for the coil on another sequence parameter card, damaging the hardware over time.

A replacement coil was ordered. The team confirmed they would run a full VERIFLUX QA before accepting it into service.

Finally had engineers on site today. They found that 2 channels were at fault with one of them having a blown fuse… So we're grateful once again to have access to Veriflux.
Lead MRI Clinical Scientist and MR Safety Expert, NHS Trust
The gap

Why OEM QA missed it

Scanner manufacturers build QA tools for routine servicing. They use their own phantoms with their own metrics. There is no longitudinal baseline, no independent reference, and no incentive to surface failures that generate expensive call-outs.

VERIFLUX tracks each site against its own history, using the internationally established fBIRN protocol. A single low SNR reading might be noise. The same reading plotted against 18 months of stable data is a red flag. That context is exactly what the OEM tool lacks.

And when the flag goes up, GSP's response is not automated. It is a scientist who knows the physics, reviewing your specific data and telling you what it means.

Bring this to your site

Run independent, longitudinal QA with VERIFLUX.

Cloud-based fBIRN analysis for longitudinal fMRI scanner stability QA.