Back to all articles
Case StudiesNew

Case Study: The Software Behind ELDA BrainTech's Neurodiagnostic Device

ELDA BrainTech needed the software side of a neurodiagnostic medical device: real-time data acquisition from FPGA-based hardware and the interfaces their team uses every day. Here is how that engagement ran, and what it looks like when the stack is stable and on its way to the FDA.

October 1, 2026·7 min read·case study, medical devices, FPGA, embedded software, FDA

ELDA BrainTech is building a neurodiagnostic medical device — the kind of product where the electronics, the physics, and the regulatory pathway are all hard at the same time. inteRFace R&D built the software behind it: the real-time data acquisition path that reads from the device's FPGA-based hardware, and the graphical interfaces ELDA's team works in every day. That stack is now stable and on its way to the FDA. This post is about what the work actually involved, because "we built the software" hides most of what matters on a project like this.

The brief

The device's signal chain ends in FPGA-based hardware; the value of the product lives in what happens after that — acquiring that data in real time without losing any of it, and putting it in front of people in a form they can actually work with. ELDA needed a software partner who could sit directly against the hardware team, keep up as the device itself evolved, and build to the standard a regulated submission eventually demands. Not a prototype that demos well: a stack that behaves the same way every day, in other people's hands.

Why medical-device software is a different job

Most software ships with the assumption that the occasional glitch is survivable — you log it, you patch it, nobody remembers. A diagnostic device does not get that assumption. The questions that dominate ordinary product work (how fast can we add features?) are replaced by harder ones:

  • Acquisition has to be dependable in real time — a dropped buffer is not a bug report, it is a hole in clinical data.
  • Every behaviour needs to be explainable. When a regulator or a clinician asks why the screen showed what it showed, "that's just how the framework does it" is not an answer.
  • The software and the hardware are moving at the same time. The interface to an FPGA that is still being revised is a negotiation, not a datasheet — it demands a working relationship with the hardware team, not a spec thrown over a wall.
  • Stability is a feature you prove, not declare. The path to a submission runs through the boring work: testing, reproducing, hardening, and the discipline not to touch what has been verified.

We have written separately about what regulation does to the hardware side in Medical Device PCB Design: FDA Class II Pathway, DFM Checklist, and 60601-1 Compliance. The software side carries the same weight with less visibility — nobody photographs a verification matrix.

What we delivered

  • The real-time acquisition path from the device's FPGA-based hardware into the application layer — the part of the stack where timing is physics, not preference.
  • The graphical interfaces ELDA's team uses daily to operate the device and work with what it measures.
  • The long tail that separates a demo from a device: stabilisation, edge-case behaviour under disconnection and fault conditions, and the verification passes behind the word "stable".

How the engagement ran

This was not a fixed-scope, throw-it-over-the-wall contract. We worked as ELDA's software team over an extended period — senior engineers in direct contact with the people building the hardware, reviewing against real device behaviour rather than assumptions, with the scope evolving as the device did. That shape matters for a startup: it means paying for the engineering the product needs this month, not for a guess made a year ago about what it would need.

It is the same engagement shape we describe in Hardware for Startups — one accountable team, senior people only, and the honest version of what things cost.

Where it stands

The software stack is stable and the device is on its way to the FDA. For a regulated product, that sentence is the milestone — it means the exploratory phase is over, the system behaves the same way every time, and the remaining work is the pathway itself. We are proud to have our work inside a machine that, if it does its job, will matter to people who never hear either company's name.

If you are building something like this

The pattern transfers beyond medical: any product where an FPGA or custom silicon feeds real-time data into software that humans rely on — test equipment, industrial monitoring, scientific instruments — has the same shape and the same failure modes. If that is the gap in your team, start with Hardware for Startups for how a first engagement works, or bring the hard question to a free 30-minute technical call. A mutual NDA comes before any technical detail, and you keep 100% of the IP — ELDA does.

Wondering what your project would cost?
Two minutes, honest ranges in engineering hours, the units we price in. You get a written quote with phases before any work starts.
Try the free estimator

Building something hardware-shaped?

We help hardware founders go from sketch to certified product. Bring the spec, or just the idea, to a free 30-minute call with a senior engineer. Prefer email? A senior engineer reads every one.