Imaging Systems

The Hardware Is Cleared. The Reconstruction Is the Product.

Regulatory strategy for imaging — scanners, detectors, and the software that turns signal into diagnosis, cleared as one system with performance data to match.

Where the value moved

You Sell a Magnet. What the Radiologist Buys Is an Image.

Imaging has quietly become a software category wearing hardware. The gantry, the magnet, the detector — all mature, all necessary, none of them where the differentiation lives. The claims that sell a modern system are reconstruction claims: faster scans at the same diagnostic quality, lower dose at the same confidence, denoising that lets you shorten a breath-hold. Every one of those is a software claim about diagnostic performance.

Which means the file changes shape. A hardware submission proves the machine is safe and performs to spec; a reconstruction claim has to prove that a clinician reading your images reaches the right answer — often with reader studies, always with performance data that survives across sites, scanners, and patient populations. We scope imaging files around the claim, not the chassis.

A radiologist reviewing MRI scan results
The reader is the endpoint

Image quality is a means. Diagnostic performance in a human reader is the claim.

The signature analysis

Five Links Between the Photon and the Diagnosis.

Each link has its own standard, its own evidence, and its own way of ending a review. The file has to close all five.

The chain is why imaging submissions surprise people. A company that has cleared scanners for thirty years can be stopped by link three, because a reconstruction claim invites the software framework, the change-control question, and — if the algorithm learns — a predetermined change control plan the hardware team has never heard of.

A clinician performing an ultrasound examination
Same signal, different world

Ultrasound moved to handhelds and phones — and took the whole regulatory frame with it.

The installed base problem

Your Scanner Will Outlive Three Generations of Its Own Software.

Imaging systems live in hospitals for a decade or more, on networks you do not control, running software you keep updating. That creates the category’s distinctive burden: every release has to be legal against the cleared configuration, every patch has to reach machines whose OS is older than the patch, and cybersecurity obligations now attach to a fleet that predates them.

Meanwhile the frontier moves in the other direction — handheld ultrasound on a phone, AI triage reading studies before a radiologist does, point-of-care imaging in clinics with no physicist. We build imaging programs that hold the installed base and the frontier at once, because the same quality system has to serve both.

The interior of a modern MRI scanner room in a hospital
A decade on the floor

An Imaging System Is a Ten-Year Platform, Not a Single Clearance.

Electronic performance standards, radiation dose, and the claim the software makes about the image — all of it is revisited across a service life measured in clinical generations.

The operating facts

What an Imaging Program Plans Around.

Three truths about a category whose product is increasingly not the machine.

System Specificationplatform-level
The claim
Sets the evidence. “Faster at equal quality” is a diagnostic performance claim and needs reader-level proof.
1020
The radiation performance standards your hardware answers to, independent of everything the software does.
10+ years
How long your systems stay in service — and how long you owe them patches, support, and a security position.
Where imaging programs stall

Six Failure Modes We Are Brought In to Prevent.

Most of them are a hardware organization meeting a software framework.

Recurring Findingsall remediable early
IMG-01the claim

Reconstruction claims without readers

“Equivalent diagnostic quality” asserted from phantom data, when the claim needed clinicians reading real studies.

IMG-02dose

AI in the pipeline, unacknowledged

A learned denoiser shipped as image processing — and the software, change control, and PCCP questions arriving all at once.

IMG-03software

Performance that doesn’t travel

Data from one site, one scanner, one population — then generalization questions the file cannot answer.

IMG-04cybersecurity

Display assumptions unstated

A claim that silently depends on calibrated monitors nobody in the field actually calibrates.

IMG-05legacy

Legacy fleet, modern threats

Ten-year-old consoles on hospital networks with no patch path and no security position — now a 524B-era liability.

IMG-06EU

Software releases outrunning clearance

A release cadence built for consumer software applied to a cleared configuration nobody re-assessed.

A medical technician assisting a patient with an imaging machine
The claim rides on the image. What the system says the picture means — detect, measure, quantify — is the intended use the whole file is built to support.
People who have cleared the system

Imaging Regulatory Leadership That Reads Physics and Software.

Our imaging leads have scoped reader studies, defended reconstruction claims, and kept installed fleets compliant through a decade of updates.

A gloved hand operating an imaging system control panel A well-equipped hospital X-ray room

“Nobody clears a magnet anymore. They clear a claim about what a radiologist can see — and that is a software submission with a scanner attached.”

The discipline we bring to CT, MR, ultrasound, and molecular imaging.

Reader study & MRMC design IEC 60601-2 & 21 CFR 1020 Reconstruction claim strategy AI in the imaging pipeline Installed-base change control Fleet cybersecurity posture

Clearing an Imaging System? Scope the File Around the Claim.

Bring senior imaging regulatory leadership in before the reconstruction claim outruns the evidence plan.

Senior-led. Embedded in your team. No junior hand-offs.