Do I need FDA clearance to add vitals tracking to my app?

The explosion of digital health has placed a powerful wellness and monitoring tool in nearly every pocket: the smartphone. For digital health founders, telehealth product managers, and hospital IT leaders, the temptation to add vital signs tracking to an application is immense. It promises deeper engagement, better data, and more personalized user experiences. However, this path is fraught with regulatory complexities. The central question that emerges is not one of technical feasibility, but of regulatory compliance: does adding this feature require a formal review process with the U.S. Food and Drug Administration (FDA)? The answer depends entirely on the app's "intended use."

"The global market for Software as a Medical Device (SaMD) is projected to reach $86.5 billion by 2027, with a compound annual growth rate of 21.9%. This growth is driven by an increasing number of health apps that provide diagnostic or treatment recommendations, putting them squarely in the category of regulated medical devices." - 2023 Global Digital Health Market Report

The regulatory maze: general wellness vs. medical device

Navigating the FDA's regulatory landscape can feel daunting, but it boils down to a core distinction: is your product a "general wellness" tool or a "medical device"? The FDA's primary concern is protecting public health, so its oversight focuses on products that diagnose, treat, mitigate, cure, or prevent disease. If your app is intended for these purposes, it is a medical device. If it is intended only for promoting a healthy lifestyle, it may fall into the lower-risk "general wellness" category, for which the FDA exercises enforcement discretion.

The line is crossed when the software's output moves from informing the user about their general state of health to providing information that could be used to make a clinical decision. An app that simply displays a heart rate reading for fitness tracking is different from one that claims to detect atrial fibrillation. This is where many developers run into trouble. Adding features without a clear understanding of the regulatory implications can lead to a requirement for an FDA clearance vitals app submission, a process that demands significant time, resources, and expertise. This distinction is formally detailed in the FDA's guidance document, "General Wellness: Policy for Low Risk Devices," published in 2019.

Criteria	General Wellness App	Software as a Medical Device (SaMD)
Primary Purpose	To promote, track, or encourage a healthy lifestyle.	To diagnose, cure, mitigate, treat, or prevent a specific disease or condition.
Intended Use Examples	Tracking activity for fitness goals, monitoring sleep patterns, logging calorie intake, displaying heart rate during exercise.	Analyzing ECG data to detect arrhythmia, measuring blood oxygen to manage COPD, calculating insulin dosage from glucose readings.
Data Interpretation	Presents raw data or general insights for user awareness and motivation. Does not interpret data for medical decision-making.	Interprets user-specific data to provide a diagnosis, a risk assessment, or a specific treatment recommendation.
FDA Oversight	Generally subject to FDA "enforcement discretion." No 510(k) or PMA required if it meets low-risk criteria.	Requires a formal regulatory submission, such as a 510(k) premarket notification, De Novo classification, or Premarket Approval (PMA).

Industry Applications

The distinction between wellness and medical device functionality has significant implications across the digital health spectrum.

For telehealth platforms

A telehealth platform that integrates vitals tracking must be acutely aware of its intended use. If the platform simply receives and displays data from a patient's device for a clinician to interpret, the platform itself may not be the regulated device. However, if the platform's software analyzes that data to flag potential issues or provide diagnostic suggestions, it becomes Software as a Medical Device (SaMD). According to research from the DiMe Society (2023), this is a critical consideration for platforms seeking to scale.

For corporate wellness

Corporate wellness programs often use apps to encourage employee health and reduce insurance costs. These apps are a prime example of general wellness products. They may track steps, heart rate, or stress levels.

• Encouraging employees to reach a certain heart rate zone during exercise.
• Gamifying activity with leaderboards and rewards.
• Providing educational content about healthy living.

The key is that these apps do not claim to diagnose or treat any medical condition. They are motivational and informational tools designed to support a healthy lifestyle.

Current research and evidence

The FDA has been actively refining its stance on digital health tools for years. The agency's thinking is outlined in several key guidance documents. The "Mobile Medical Applications" guidance, updated in 2019, clarifies which software functions fall under device regulation. It specifically states that apps that use a mobile platform's built-in features (like a camera) to perform medical functions can be considered medical devices.

Further clarification comes from the International Medical Device Regulators Forum (IMDRF), whose risk-based framework for SaMD has been influential in the FDA's own classifications. The IMDRF framework (IMDRF/SaMD WG/N12 FINAL:2014) categorizes SaMD based on the seriousness of the healthcare situation and the significance of the information provided by the software. An app that provides information to "treat or diagnose" a "critical" condition falls into the highest risk category.

The future of digital health regulation

The regulatory environment is not static. The FDA is continuously adapting to the pace of technological innovation. The rise of artificial intelligence and machine learning (AI/ML) in SaMD has led to new frameworks, such as the proposed Predetermined Change Control Plan (PCCP), which would allow manufacturers to get pre-authorization for future modifications to their algorithms.

For founders and product managers, this means that the question of an FDA clearance vitals app is not a one-time decision. It is an ongoing strategic consideration. As your app evolves and adds features, its regulatory status may change. Building a robust Quality Management System (QMS) and having a clear regulatory strategy from the outset is no longer optional for ambitious digital health companies.

Frequently asked questions

What is the first step to determine if my app needs an FDA review? The first step is to define your app's "intended use." Document precisely what your app does, what it claims to do in your marketing, and how a user is expected to use it. Compare this intended use against the FDA's definition of a medical device.

Does using a third-party API for vitals affect my FDA status? Yes. If you integrate a third-party, device-grade API to power your app's vitals monitoring, you must understand the regulatory status of that API. If the API provides a medical-grade measurement, the way your app uses and presents that data determines your own regulatory burden.

What is the difference between "FDA registered" and having formal clearance? "FDA registered" means a company has listed its facility and devices with the FDA. It does not mean the FDA has reviewed or provided a decision on the device itself. A formal clearance, like a 510(k), means the FDA has reviewed the device and found it substantially equivalent to a legally marketed predicate device.

Can I market my app for wellness first and add medical claims later? You can, but this requires a careful, phased regulatory strategy. You would launch as a general wellness product, then, when ready, submit a formal application to the FDA for the new medical-device version of your product. You cannot make medical claims until you receive the appropriate authorization.

Adding vitals tracking to an app can be a powerful driver of growth and user value, but it requires a deep understanding of the regulatory landscape. For companies that want to use the power of camera-based vitals without shouldering the entire regulatory burden themselves, partnering with a white-label technology provider can be a strategic accelerator. Circadify's platform handles the underlying compliance, allowing you to focus on your brand and your users. To learn more about a custom build, explore our partnership options at circadify.com/custom-builds.