How a Wearable Medical Device Goes from Idea to FDA Clearance
Most of the things we wear every day never have to go through a regulatory process. A smartwatch that counts steps is one thing. A device that monitors a heart rhythm, detects a physiological change, or alerts someone to a potential medical condition is something else entirely. Once a company claims its device can monitor, detect, or help manage a medical condition, the FDA becomes part of the process. And before people can rely on it, the company has to demonstrate that the device is safe and performs as intended.
Having worked around wearable medical devices, I have come to realize that the regulatory process is often misunderstood, particularly by engineers. It is easy to think of FDA documentation as something that comes after the design is complete, another set of documents to prepare before a product can ship. But regulatory requirements influence engineering decisions long before a design is finalized. They affect what we build, how we test it, what we document, and sometimes even how we approach the problem in the first place.
From an electrical and hardware engineering perspective, these requirements can influence decisions at nearly every stage of development.
1. Electrical safety and power architecture
A wearable may initially be designed around battery life, size, and cost. But electrical safety requirements can influence battery charging architecture, protection circuits, leakage current, power paths, and how the device behaves when connected to a charger while being worn. Decisions about battery chemistry, charging current, voltage regulation, protection mechanisms, and power management may have to be reconsidered to meet safety and performance requirements.
2. Electromagnetic compatibility (EMC)
A sensor may perform well on the bench but become noisy when Bluetooth or Wi-Fi is transmitting. Regulatory EMC testing can drive changes to PCB layout, grounding, shielding, filtering, cable routing, power decoupling, and even the placement of components. Engineers may need to redesign a board to ensure the device maintains reliable measurements in the presence of electromagnetic interference and does not create unacceptable emissions.
3. Sensor accuracy and signal integrity
A sensor that works reliably under controlled laboratory conditions may behave differently when worn by a patient. Motion, temperature, sweat, contact pressure, electrical noise, component tolerances, and variations between users can all affect measurements. Those factors may influence sensor selection, analog front-end design, electrode placement, filtering, calibration algorithms, mechanical interfaces, and how the device validates its measurements.
4. Component selection and traceability
The cheapest or smallest component may not always be the best choice. Engineers may need to consider component tolerances, operating temperature, reliability, availability, documented specifications, and how a component's failure could affect the device. Replacing a component late in development may also require additional verification to demonstrate that the change does not affect performance, safety, or reliability.
5. Battery and thermal management
Battery capacity is not the only consideration when designing a wearable. Charging while worn, fault conditions, battery protection, thermal behavior, charging current, and enclosure temperature can all influence the design. This can affect the battery chemistry, charging IC, temperature sensing, PCB layout, enclosure materials, firmware limits, and charging behavior.
6. Design for verification and validation
Sometimes the biggest hardware design change is not related to the circuit's functionality at all. Engineers may need to add test points, debug interfaces, measurement access, diagnostic capabilities, or ways to inject known signals into the system. Without those features, it may become unnecessarily difficult to verify that the device meets its requirements or investigate failures during testing.
These are just a few examples of how regulatory expectations can influence hardware decisions before a design is finalized. But the engineering requirements alone do not define the regulatory pathway. That starts with a much more fundamental question.
What is this device actually intended to do?
The intended use defines the purpose of the device, the population it is designed for, and the conditions under which it will be used. It may sound like a product description, but it carries much more weight than that. A device intended to monitor a patient in a hospital may face different considerations from one designed to be worn continuously at home. Even seemingly small differences in the intended use can affect the regulatory pathway, testing requirements, and overall design. This is one of those decisions that deserves to be made carefully, not rushed through a product brief.
Once the intended use is established, the next step is determining how the FDA classifies the device. The FDA generally categorizes medical devices into three classes based on risk. Many wearable medical devices fall under Class II, which often means pursuing a 510(k) submission.
Through this pathway, a company demonstrates that its device is substantially equivalent to an already legally marketed device, commonly referred to as a predicate. This involves establishing that the new device has the same intended use and sufficiently comparable technological characteristics, or that any differences do not raise different questions of safety and effectiveness.
Not every device has an appropriate predicate. In those cases, the De Novo pathway may be an option for novel devices that present low to moderate risk and do not require the higher level of regulatory review associated with Class III devices. Class III devices, generally those associated with the highest risk, typically require Premarket Approval (PMA), which involves a substantially more demanding process.
Then comes the question everyone eventually asks: How long does it take?
The FDA's stated review timeline for a traditional 510(k) is generally 90 calendar days, but that does not necessarily mean a company will receive clearance within 90 days of submitting its application. Requests for additional information can pause the review clock while the company prepares its response. And those requests are not always minor. They may require additional testing, clarification of design decisions, more documentation, or even changes to the product itself. The submission timeline is only one part of the process. Preparing a complete submission, addressing questions, and coordinating testing can extend the overall timeline considerably.
Meanwhile, the engineering work continues. Design controls, risk analysis, verification, and validation are not separate activities that can simply be checked off at the end. They are part of the development process itself. The team has to demonstrate that the design meets its requirements, that risks have been identified and addressed, and that the device performs as intended under the conditions in which it will actually be used.
For wearables, this can involve electrical safety, electromagnetic compatibility, mechanical reliability, biocompatibility for materials that contact the skin, and software verification and validation. If the device communicates with a phone, connects to a cloud platform, or handles sensitive patient information, cybersecurity becomes another important part of the design and regulatory documentation. Each of these areas introduces its own requirements, testing, and potential challenges.
In my experience, some of the biggest delays are not necessarily caused by the complexity of the technology itself. They often come from decisions made too late. The intended use is not clearly defined, making it difficult to identify an appropriate predicate. Testing is planned after the design has already been finalized, leaving the team scrambling to collect data that was never part of the original plan. Software documentation is rushed because hardware development took longer than expected. Or the team receives a request for additional information that could have been anticipated much earlier.
These are not always technical failures. Sometimes they are planning failures.
The more I think about it, the more I believe regulatory requirements should be treated as an engineering input from the beginning, rather than a hurdle at the end. Define the intended use early. Understand the regulatory pathway before committing to an architecture. Identify the predicate and relevant FDA guidance. Plan verification and validation around the requirements that need to be demonstrated. And document the decisions along the way, while the reasoning is still fresh.
Doing this does not necessarily make the process shorter, but it makes it more predictable. It also reduces the likelihood of having to revisit decisions that were made months earlier, when changing them was much easier.
FDA clearance is not the end of the engineering process. It is evidence that a device has been evaluated against the requirements associated with its intended use. But behind that clearance are countless engineering decisions, tests, tradeoffs, failures, corrections, and lessons learned.
Ultimately, the device is not being built for a submission or a review. It is being built for someone who will wear it, trust it, and depend on it. And that is probably the most important requirement of all.