Independent design assurance · Minneapolis, MN

Design assurance for catheter programs that have to clear.

A risk-based design process that starts with the user. Usability, safety, and efficacy are built in from the first user need — so the path to regulatory approval is set from the start, not reconstructed at the end.

Scope of practiceRev A
DevicesCatheters, guidewires, delivery systems, vascular access & accessories
Pathway510(k) · PMA · international approvals
StandardsISO 14971 · ISO 13485 · IEC 62366 · ISO 10993
EngagementFractional, project, or embedded

Services

The work between a working prototype and a defensible DHF.

Most programs don't fail on the bench. They fail on paper — a protocol that can't support its own acceptance criteria, a risk file that doesn't trace, a report an FDA reviewer can't follow. That paper is the job.

DV / DVALPR · TM · RPT

Design verification & validation

Protocols, execution oversight, and reports that state what was tested, why the sample size holds, and what the statistics actually show.

  • Verification plans traced to design inputs
  • Validation against user needs, including usability
  • Reports written for the reviewer, not the file cabinet
ISO 14971RMP · RMF · RMR

Risk management files

Hazard analysis, use-related risk, design and process FMEAs, and benefit-risk conclusions built to ISO 14971 — and kept alive through change.

  • Risk management plan through report
  • Controls verified, not just listed
  • Post-market feedback loop defined
21 CFR 820DRD · TRACE · DR

Design controls & DHF

Requirements that can be tested, traceability that closes, and design reviews with real decisions in the minutes. Remediation when a DHF grew up without them.

  • Design requirements documents
  • Trace matrices and gap assessments
  • DHF audit-readiness and remediation
TMMETHOD · MSA

Test method development

Fixtures, procedures, and measurement-system analysis for the things catheters have to prove: tensile, torque, kink, burst, trackability, coating integrity.

  • Method design and fixture concepts
  • Gage R&R and method validation
  • Characterization studies before DV
510(k)STRATEGY · RTA

Submission test strategy

Which tests, which standards, which predicate — decided before the bench work starts. Support drafting the performance sections and answering deficiencies.

  • Predicate and special-controls analysis
  • Performance testing plan and rationale
  • Additional-information responses
DCRQC · REDLINE

Document QC & change control

Independent review of controlled documents before release: cross-references checked, numbers reconciled, redlines delivered as tracked changes with a findings memo.

  • Pre-release QC of SOPs, specs, protocols, reports
  • Change-order packages
  • Findings memos with rationale and citation

How an engagement runs

Scoped like a protocol. Closed like a report.

Every engagement has a written scope, a named deliverable list, and a release step. You always know what's in, what's out, and what "done" means.

Step1 / 4

Scope

A short discovery call, a look at the current DHF, and a fixed-scope proposal with deliverables listed by document number.

Step2 / 4

Plan

User needs, design inputs, risk, and the regulatory test strategy aligned before anything goes to the bench. Sample sizes and statistics justified up front.

Step3 / 4

Execute

Protocols authored, execution supported, data reviewed against the datasheets — not the summary — and deviations dispositioned in writing.

Step4 / 4

Release

Reports, risk file, and trace matrix QC'd independently and delivered ready for your change order, your auditor, and your reviewer.

Usability

Designed around the people who use the device and the places they use it. Use-related risks are found early and designed out — not discovered in a summative study.

Safety

Risk management drives the design rather than documenting it afterward. Every hazard traces to a control, and every control is verified.

Efficacy

The device has to do what the user needs, every time. Performance is defined in measurable design inputs and proven through verification and validation.

Experience

Built on the operating side of the table.

Nick Ellering brings more than 20 years of medical-device development, helping teams earn dozens of FDA 510(k) clearances, PMA approvals, and international regulatory approvals.

That experience was earned building devices, not just reviewing them. It shapes how every program starts: with the user. Clinicians, patients, and the environment they work in define the user needs. Those needs become measurable design inputs. Those inputs drive design outputs that can be built, tested, and traced all the way back to the person the device is for.

Risk analysis runs alongside every step, so usability, safety, and efficacy are designed in — and the evidence a reviewer needs exists the moment the design does.

20+Years in medical-device development
Dozensof 510(k) clearances, PMA approvals, and international approvals
300+Interventional cases supported
Nick Ellering
Principal · Design Assurance
Design control flowTraced end to end
01 · UN
User needs
Who uses the device, where, and for what. Gathered from clinicians, patients, and the use environment — including how it could be misused.
02 · DI
Design inputs
Each need translated into a measurable, testable requirement, informed by hazard analysis and the applicable standards.
03 · DO
Design outputs
Drawings, specifications, and processes that meet the inputs and define the device as built.
04 · V&V
Verification & validation
Outputs verified against inputs; the finished device validated against user needs, including usability.
05 · REG
Regulatory approval
A submission assembled from evidence that already traces — 510(k), PMA, or international.
21 CFR 820 / QMSRISO 13485ISO 14971IEC 62366ISO 10555ISO 10993ISO 11607ASTM F2394

Contact

Tell me where the program is stuck.

A DV report due before a submission, a risk file that predates the current design, a DHF that needs to survive an audit — send a few lines and you'll get a straight answer on whether and how we can help, usually within one business day.

Based inMinneapolis, Minnesota · working with teams across the U.S.

No newsletters, no automated follow-up. Your message goes to Nick's inbox.