Back to Home
earpieces

How Earpieces Crossed Into Regulated Hearing Aid Territory

The Hearing Access Profile and the FDA's OTC rule turned consumer earpieces into a regulated hearing aid category. Here is the technical path from LE Audio protocol stack to clinical-grade fitting.

How Earpieces Crossed Into Regulated Hearing Aid Territory
Disclosure: Some links in this article are affiliate links. If you purchase through them, we may earn a small commission at no extra cost to you. This helps support our independent editorial coverage.

How Earpieces Crossed Into Regulated Hearing Aid Territory

The FDA cleared Samsung's Galaxy Buds3 Pro and Galaxy Buds4 Pro as over-the-counter hearing aids in August 2026. Apple did the same for AirPods Pro two years earlier. Neither approval authorized a new piece of medical hardware. It authorized software.

The distinction matters. Under the FDA's OTC hearing aid rule, the regulated device is the fitting application, the signal processing pipeline, and the self-administered audiogram workflow. The earbuds are an "off-the-shelf wearable platform," in the agency's exact language, separate from the medical device. That separation has quietly rewritten what an earpiece can be.

The hardware is the vessel, the software is the device

Hardware and medical device live on the same silicon but answer to different authorities. When you place Galaxy Buds in your ears and run Samsung's Hearing Test, the smartphone orchestrates a clinical-grade pure-tone audiometry session, sweeping frequencies in each ear independently. The output is an audiogram. The fitting software feeds that audiogram into a NAL-NL2 prescription, the same fitting procedure that audiologists use for traditional hearing aids, to derive amplification targets per frequency. Then the earbuds produce sound.

This is not a wellness feature performing parlor-trick equalization. The 510(k) summary for Samsung's clearance, document K261187, lists specifications you would expect from a hearing aid, not a consumer earbud: maximum OSPL90 of 111.9 dB SPL, full-on gain of 31.5 dB, frequency response from 100 Hz to 9,030 Hz, total harmonic distortion at 1% or below, equivalent input noise of 24.9 dB, and 2.7 ms of latency. Those are clinical targets met on consumer hardware.

The clinical validation followed the same standard that governs prescription hearing aids. Samsung ran a prospective multicenter study across roughly 30 days with 103 participants in the mild-to-moderate hearing loss range. A self-fit group using the Hearing Aid Feature was compared against a clinician-fit group using the same NAL-NL2 procedure performed by a hearing healthcare professional. The self-fit group achieved non-inferior perceived benefit. The FDA also summarized a 367-participant Hearing Test validation reporting a median absolute difference of 3.75 dB between self-administered audiogram thresholds and clinical pure-tone audiometry. Consumer earpieces, run through fitting software, are now hitting the accuracy numbers regulated for the hearing aid industry.

ASHA is dead. HAP is the successor.

The path from earbud to regulated hearing aid was actually carved by Bluetooth audio engineers. The reason an AirPod Pro or a Galaxy Buds4 can even bid for hearing aid status is that LE Audio finally gave earpieces a stack designed for this kind of work. The Hearing Access Profile, HAP, sits inside LE Audio alongside TMAP, GMAP, and the rest of the profile suite. It is the only one of those profiles written specifically for the hearing aid ecosystem.

HAP replaces ASHA, Audio Streaming for Hearing Aids, the proprietary protocol Apple introduced in 2010 so that Made-for-iPhone hearing aids could stream audio directly over Bluetooth Classic. ASHA worked, but it was never an open standard. It locked the hearing aid industry into Apple's ecosystem and left Android users out entirely. HAP runs on Bluetooth LE, uses the LC3 codec, and is published by the Bluetooth SIG as a public specification. Any earpiece implementing HAP can expose the same hearing-aid-style controls to any smartphone, with no MFi licensing in between.

The protocol does not process audio itself. It defines the control surface. HAP exposes presets, the audio profiles a hearing aid stores for specific environments: restaurant, office, music, outdoors. It exposes mute. It exposes volume control outside the standard media-volume pipeline, which matters because a hearing aid user frequently needs to set amplification differently from music playback level. And it exposes pairing coordination so that two earpieces, each a separate Bluetooth LE Audio device, behave as one binaural set rather than two independent buds.

How the Hearing Access Service actually works

Under the hood, HAP runs over a GATT service called the Hearing Access Service, or HAS. The hearing aid is the GATT server. The phone, or any compatible controller, is the GATT client. The accessory publishes its capabilities, including supported presets and active preset index, and the client writes values back to switch configurations. A preset is not a simple on-off toggle. It is a stored signal-processing chain baked into the earpiece firmware: compression curves, noise reduction thresholds, directional microphone bias, feedback cancellation parameters, and frequency-dependent gain. Switching presets means loading a different DSP configuration, not changing a slider.

The roles defined in HAP reveal why this matters for earpieces. A Hearing Aid, HA, is the device producing sound. A Hearing Aid Remote Controller, HARC, is a separate device issuing commands, and the Hearing Aid Client, HAC, is the application on the user's phone. Traditional hearing aids assumed a dedicated remote. The architectural shift is that consumer earpieces now take on the HA role while a generic smartphone app takes on the HAC role, with no dedicated remote hardware required.

There is one subtlety that often gets missed. HAP does not require Auracast or any broadcast audio at all. It coordinates a unicast stream. Auracast is a separate capability riding on Broadcast Isochronous Streams, BIS, that lets public venues push audio to an unlimited number of receivers. HAP and Auracast compose well. A hearing aid can carry its personal amplification profile on one channel while listening to an airport gate announcement broadcast on another. But they solve different problems. HAP is your fit. Auracast is the venue's feed. Conflating the two leaves readers confused about what each specification actually does.

The fitting pipeline is the regulated part

Read the 510(k) summaries for Apple's DEN230081 and Samsung's K261187, and the regulated device becomes clear. Wide dynamic range compression, the algorithm that compresses loud sounds while amplifying quiet ones, is the heart of any hearing aid. Beamforming, steering the microphone's directional response toward the voice in front of you, is on the list. Feedback cancellation, the algorithm that prevents the howling tone you hear when amplified audio leaks back into the microphone, is on the list. Noise suppression, distinct from ANC, is on the list. Latency budgeting is on the list, because hearing aids have a hard ceiling at roughly 10 ms before the user notices an out-of-sync voice.

None of those signal processing blocks are new. What is new is that they run on Qualcomm S7 Pro or similar consumer-class audio SoCs at power levels compatible with all-day earbud battery life, they are tuned by a clinical prescription derived from a self-administered audiogram, and the resulting bundle has been reviewed by the FDA as a Class II regulated medical device. The earpiece firmware you already own can host a regulated feature, provided the manufacturer pays for the clinical study, the engineering work, and the submission.

The earpiece and hearing aid industries are now eating each other

The same Qualcomm Snapdragon S7 platform showing up in premium earbuds is also showing up in hearing aids. GN Hearing's ReSound Nexia line uses LE Audio and Auracast. Phonak's Infinio Sphere uses a dedicated AI co-processor in addition to its main audio DSP. The hardware cost gap between a $249 earbud and a $2,499 hearing aid is shrinking rapidly, because the silicon inside them is converging. What still separates the two categories is regulatory clearance, clinical tuning, and domain expertise in fitting algorithms.

For consumers, this convergence cuts both ways. On one side, earpieces are absorbing hearing aid features that were locked behind a prescription just three years ago. Self-administered audiometry, NAL-NL2 fitting, WDRC, and beamforming are all running on consumer silicon now. On the other side, the regulatory perimeter stops at mild-to-moderate loss. Severe and profound hearing loss remain outside the FDA's OTC category, and earpieces are not designed for that population. The hearing aid industry is not going away. It is specialising into the cases consumer earpieces cannot reach.

Where this goes from here

Expect two parallel tracks over the next two years. Premium earbuds from Apple, Samsung, Sony, and others will keep adding hearing aid clearance as a checkbox feature, hosted in software, validated through clinical studies, gated by FDA approval per country. Traditional hearing aid manufacturers will keep leaning into clinical differentiation: proprietary fitting algorithms, audiologist-led remote tuning, hardware-grade feedback cancellation that consumer earbuds cannot match under battery constraints.

The Bluetooth layer underneath is settled. HAP is published. Auracast deployment will continue at airports, theaters, and lecture halls. The next fight is not over the protocol. It is over the fitting software, the regulatory per-region authorization, and the question of whether a self-fit earpiece can deliver long-term benefit on par with a clinician-fit device. The FDA's own studies suggest it can, for mild-to-moderate loss. For severe loss, the answer remains the same as it has been for decades: see a specialist.

What makes this more than a marketing story is the convergence of three independent things: a regulatory pathway opened by the FDA's OTC rule in 2022, a Bluetooth protocol stack finished by the Bluetooth SIG in 2022, and audio SoCs capable of running clinical-grade DSP inside a sub-6-gram earbud. None of those were built for the others. The fact that they landed in the same window made the earpiece-as-hearing-aid category inevitable. The earpiece in your pocket is now, potentially, regulated medical hardware. Whether you use it that way depends on whether the manufacturer paid for the submission.

#Bluetooth#Earpieces#LE Audio#HAP#Hearing Access Profile#Hearing Aid#FDA#OTC#NAL-NL2#Auracast#Samsung Galaxy Buds#AirPods Pro#Qualcomm S7#WDRC#Beamforming

Related Articles

blutoof.com

Your premier source for Bluetooth technology news, reviews, and guides. From premium headphones to hands-free earpieces — we cover it all.

Affiliate Disclosure: Blutoof.com is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com. When you purchase through links on our site, we may earn an affiliate commission at no extra cost to you.

© 2026 Blutoof.com. All rights reserved.

Bluetooth® is a trademark of Bluetooth SIG, Inc.