Trademark Registration for Health Tech Startups: Protecting Medical Device Names, App Names, and Service Marks

Health tech founders operate at the intersection of two regulatory regimes that most startup verticals never encounter: the U.S. Food and Drug Administration's naming rules and the U.S. Patent and Trademark Office's trademark examination process. A name that satisfies FDA reviewers can still get refused by USPTO examining attorneys—and vice versa. We've seen digital health companies invest months in FDA clearance, only to discover their product name faces a descriptiveness refusal at the trademark office, forcing an expensive rebrand right before launch. This guide walks through the classification strategy, FDA naming intersections, specimen requirements, timing decisions, and common pitfalls that health tech startups need to navigate when pursuing trademark registration.

The Class 10 vs. Class 42 vs. Class 44 Decision Tree

Trademark registration requires you to identify the specific goods or services your mark covers, and the USPTO assigns each application to one or more international classes under the Nice Classification system. For health tech startups, three classes do most of the heavy lifting, and choosing the wrong one can delay or derail your application.

The USPTO follows the Nice Classification, which is updated periodically—the current edition, NCL 13-2026, became effective on January 1, 2026, as noted on the USPTO's Guidance for Users page. Under this system, health tech products typically fall into one of three classes:

Class 10: Medical and Surgical Apparatus

Class 10 covers medical and surgical apparatus, instruments, and devices. If your startup makes a physical medical device—a wearable cardiac monitor, a surgical robot, a diagnostic instrument, an implantable sensor—Class 10 is where your trademark belongs. The key question is whether you're selling a tangible product that functions as medical equipment. If the answer is yes, you need Class 10 protection.

Class 42: Software and SaaS Services

Class 42 covers technology services, including software development and Software-as-a-Service (SaaS) platforms. A telehealth platform that runs as a web or mobile application—connecting patients with providers, managing health records, or providing AI-assisted triage—belongs in Class 42. Even if your software is used in a clinical setting, if you're licensing software rather than delivering clinical care or selling a physical device, Class 42 is the right home.

Class 44: Medical and Clinical Services

Class 44 covers medical services, including healthcare services provided by licensed professionals. If your startup directly delivers clinical care—virtual primary care, remote patient monitoring services staffed by clinicians, telehealth consultation services—Class 44 applies. Many health tech companies need Class 44 in addition to Class 42: the software platform (Class 42) is the delivery mechanism, but the actual service of providing medical care (Class 44) is a separate registrable offering.

Multi-Class Strategy Is Often Essential

Most health tech startups need protection in more than one class. A company that manufactures a connected glucose monitor (Class 10), offers a companion mobile app for data analysis (Class 42), and provides clinician-reviewed interpretation of that data as a service (Class 44) may need filings in all three. Each class requires its own filing fee and its own specimen showing use in commerce for that specific class of goods or services. As we discussed in our guide on why modern businesses need a deliberate trademark and brand protection strategy, filing strategically across classes is part of building a defensible brand portfolio from day one.

How FDA Naming Rules Collide With USPTO Trademark Strategy

Here's where health tech trademark strategy diverges from every other startup vertical: the FDA has its own naming requirements that can constrain what's registrable at the USPTO, and the two agencies don't coordinate. Understanding these intersections is critical to avoiding a scenario where you've invested in one naming path only to hit a wall at the other.

Established Names and the USAN System for Drugs

Under 21 CFR § 299.4, the FDA requires that drug labeling bear the drug's "established name"—defined as either an official name designated by the FDA, a compendial name, or the common or usual name of the drug. The FDA recognizes the U.S. Adopted Names (USAN) Council, a private organization sponsored by the AMA, USP, and APhA, as the primary body for assigning nonproprietary (generic) names to drugs. The FDA is represented on the USAN Council and cooperates with it, but the FDA retains authority to designate official names when it determines the USAN name is "unduly complex" or when multiple names have been applied to a single drug.

Here's the critical intersection: the USAN is the generic name. It cannot function as a trademark. If your health tech company is developing a pharmaceutical product, the USAN designation becomes the established name that must appear on labeling alongside (and in certain contexts, to the exclusion of) your proprietary brand name. The USAN Council's naming procedure requires that proposed names be conflict-free with existing generic and trade names, and the FDA reviews trade names separately from the USAN process. This means a drug's brand name must coexist with its USAN generic name without causing confusion—and the USPTO will refuse to register a mark that is merely the generic name with minor modifications.

Proprietary Name Review for Prescription Drugs

The FDA issued guidance on best practices for developing proprietary names for human prescription drug products, which outlines the agency's review process for brand names. The FDA evaluates proposed proprietary names for look-alike/sound-alike confusion, misleading name components, and "dosing"-related risks. A name that passes FDA review still must independently clear USPTO examination for distinctiveness and likelihood of confusion—and the standards differ. The FDA's concern is patient safety and medication errors; the USPTO's concern is consumer confusion as to source. A name might be safe from an FDA perspective but still face a likelihood-of-confusion refusal from a USPTO examining attorney who finds a similar registered mark in the same class.

Medical Device Naming Conventions

Unlike drugs, medical devices do not go through the USAN process. The USAN Council explicitly states that it does not assign names for medical devices. However, FDA device regulations (including 21 CFR Part 807 for device registration and listing) require specific naming conventions in 510(k) submissions, PMA applications, and device listing. The proprietary name you use in your FDA submission becomes the name associated with your device in FDA databases—and that same name needs to be distinctive enough to function as a trademark.

The trap here is that medical device founders often choose functional, descriptive names for their FDA submissions because descriptive names help reviewers understand the device quickly. But those same descriptive names face "merely descriptive" refusals under TMEP Section 1209, which governs the USPTO's examination of descriptiveness. A device called "CardiacMonitor Pro" may sail through FDA review, but the USPTO will likely refuse registration because the mark merely describes the product's function.

Specimen Requirements for Regulated Medical Products

To register a trademark based on use in commerce, you must submit a specimen showing how you actually use the mark with your goods or services. The USPTO's drawings and specimens guidance distinguishes between a drawing (which shows what the mark is) and a specimen (which shows how you're using it). For health tech companies, specimen requirements intersect with FDA regulatory requirements in ways that other industries don't face.

Class 10 Specimens: Labels and Packaging

For medical devices (Class 10), acceptable specimens typically include product labels, packaging, or instructional materials that show the mark used in connection with the goods. The catch is that FDA-regulated medical device labeling must comply with specific content and format requirements—indications for use, contraindications, warnings, and manufacturer information. Your trademark specimen must show the mark as it actually appears on the product or its packaging in a way that consumers would perceive it as a source identifier, not just as part of the regulatory text.

If your device has received 510(k) clearance or PMA approval, the labeling submitted to the FDA can often serve double duty as a trademark specimen—provided the mark is prominently displayed as a brand identifier, not merely as part of the required regulatory text. FDA-cleared marketing materials, product packaging with the brand name prominently displayed, and point-of-sale displays all can serve as acceptable specimens.

Class 42 Specimens: Screenshots and Marketing Materials

For software platforms and SaaS services (Class 42), specimens typically include screenshots of the software interface showing the mark, website screenshots where the mark is used to promote the service, or marketing materials. For a telehealth app, a screenshot of the app's home screen or login page displaying the brand name would qualify. The key is that the specimen must show the mark used in a way that consumers would associate it with the specific service identified in the application.

Class 44 Specimens: Service Promotional Materials

For clinical services (Class 44), specimens should show the mark used in advertising or promoting the medical services. This could include website pages describing the telehealth services, brochures, or print advertisements. The specimen must show the mark used in connection with the actual rendering of healthcare services, not just the technology platform.

Timing Strategy: Filing Before vs. After FDA Clearance

One of the most consequential decisions health tech founders face is when to file trademark applications relative to FDA regulatory milestones. The answer depends on your product type, funding timeline, and risk tolerance.

The Intent-to-Use Advantage

The USPTO allows applicants to file based on a "bona fide intent to use" the mark in commerce, even before the product is on the market. This is particularly valuable for health tech startups because FDA clearance can take months or years. By filing an intent-to-use application early, you establish a priority date that precedes your actual market entry. If your 510(k) review takes 90 days and your PMA process takes a year or more, filing the trademark application at the same time you begin your FDA submission locks in your priority date while regulatory review is underway.

However, intent-to-use applications require you to eventually file a Statement of Use demonstrating actual commercial use, and you have a limited window (with possible extensions) to do so. If FDA delays push your launch timeline beyond the USPTO's deadlines, you may need to request extensions—each with additional fees. Planning your trademark timeline alongside your regulatory timeline is essential.

The Risk of Filing Too Early

Filing before FDA clearance carries a risk: if the FDA requires you to change your product name during the review process, you may need to abandon your trademark application and refile under the new name. This is most common when the FDA's proprietary name review identifies concerns with a drug name, but it can also happen with device names if reviewers find the name misleading. Some founders mitigate this risk by filing the trademark application under a placeholder or provisional brand while finalizing the FDA submission, then amending or refiling once the name is locked.

The Risk of Filing Too Late

The opposite risk is waiting until after FDA clearance to file. If a competitor files a similar mark in the interim—or if the name becomes widely used in the industry through pre-launch publicity—you may find yourself blocked. Given that trademark examination at the USPTO currently takes several months from filing to first office action, and that office actions are common, waiting until after FDA clearance to start the trademark process can delay your ability to enforce your brand by six months or more after launch.

For most health tech startups, the optimal strategy is to file an intent-to-use application once the product name is reasonably finalized—typically after initial FDA submission or once the name has cleared preliminary FDA review feedback—but before final FDA clearance is granted. This balances the risk of a name change against the need to secure priority.

Common Pitfalls: Descriptive Device Names and Generic Health Terms

The Descriptiveness Trap

The most common refusal we see for health tech trademark applications is the "merely descriptive" refusal under Section 2(e)(1) of the Lanham Act. The USPTO refuses registration when a mark "consists of a term or terms that merely describe" the goods or services. In the health tech context, this happens frequently because founders naturally gravitate toward names that describe what the product does—which is exactly what the USPTO says trademarks shouldn't do.

In City of New York v. Henriquez, 98 F.4th 402 (2d Cir. 2024), the court affirmed that the mark "Medical Special Operations Conference" was inherently descriptive because the name corresponded so closely to the product it designated—a conference for individuals involved in medical special operations. The same logic applies to health tech: a name like "DiabetesTracker" for a glucose monitoring app, "TeleHealth Connect" for a telehealth platform, or "HeartMonitor AI" for a cardiac device will almost certainly face descriptiveness refusals.

To avoid this, aim for marks that are suggestive, arbitrary, or fanciful. "Oxaria" for an oxygen monitoring device, "Lumina" for a diagnostic imaging platform, or "Kovar" for a telehealth service are far more likely to clear USPTO examination than names that spell out the product's function. As we covered in our article on why trademark lifespan and renewals matter for serious brands, building a distinctive mark from the start protects your brand for the long term.

Generic Health Terms

Even worse than descriptive marks are generic ones—terms that name the category of goods or services themselves. "Telehealth" for a telehealth service, "Medical Device" for a medical device, or "Health App" for a health application are generic and can never function as trademarks. The USPTO will refuse these outright, and no amount of marketing investment can overcome a generic term's unregistrability.

The Compound Name Problem

For pharmaceutical health tech companies, the USAN system creates a specific compound-name problem. The USAN Council assigns generic names using a prefix-infix-stem system that communicates the drug's class and function. For example, the "-prazole" stem identifies proton pump inhibitors, and "-mab" identifies monoclonal antibodies. Your brand name must be distinct from the USAN generic name, and the USPTO will refuse any mark that is merely the generic name with minor variations. The FDA requires that both the established (generic) name and the proprietary (brand) name appear on labeling, so your trademark must be visually and phonetically distinct from the USAN to avoid both FDA confusion concerns and USPTO descriptiveness refusals.

Failing to Search Before Naming

A surprisingly common pitfall is failing to conduct a comprehensive trademark clearance search before settling on a name for FDA submissions. The USPTO's trademark database is searchable for free, and a knockout search before FDA submission can identify obvious conflicts. But a full clearance search—checking pending applications, state registrations, common law uses, and domain names—is essential before investing in regulatory submissions under a particular name. If you're also navigating telehealth licensure across state lines, you may also encounter state-level business name registration requirements that intersect with your trademark strategy.

Actionable Next Steps

Trademark registration for health tech startups requires coordinating your brand strategy with your regulatory timeline from the earliest stages. Here's what we recommend:

1. Conduct a trademark clearance search before FDA submission. Don't wait until after you've submitted your 510(k) or IND to discover your product name conflicts with an existing registration. A clearance search at the naming stage saves the cost and disruption of a rebrand after regulatory investment.
2. Choose a distinctive mark, not a descriptive one. Suggestive, arbitrary, and fanciful marks clear USPTO examination more easily and provide stronger, broader protection. Resist the temptation to name your device or platform after what it does.
3. Map your classification needs early. Determine whether you need Class 10 (devices), Class 42 (software/SaaS), Class 44 (clinical services), or a combination. File in all relevant classes to avoid gaps in protection.
4. File an intent-to-use application aligned with your regulatory timeline. Lock in your priority date while FDA review is underway, but ensure you have sufficient time to file the Statement of Use before USPTO deadlines expire.
5. Prepare your specimens with regulatory documents in mind. FDA-cleared labeling, product packaging, and marketing materials can serve as trademark specimens if the mark is displayed prominently as a source identifier.
6. For drug products, coordinate USAN and brand name selection. Ensure your proprietary name is distinct from the USAN generic name to satisfy both FDA and USPTO requirements.

Health tech founders face a trademark landscape that no other startup vertical encounters. The intersection of FDA naming rules and USPTO examination standards creates traps that can derail product launches and force expensive rebrands. By understanding the classification decision tree, coordinating your regulatory and trademark timelines, and choosing distinctive names from the start, you can build brand protection that survives both agencies' scrutiny.