Humanitarian Use Device (HUD): IRB Rules

The single point that determines everything else about how an institution handles a Humanitarian Use Device (HUD): using an FDA-approved HUD within its approved indication is clinical care, not research — yet it is one of only a handful of clinical-care activities in U.S. medicine that legally cannot proceed without prospective Institutional Review Board (IRB) approval. That combination trips up research offices and clinical departments alike, because everyone’s default assumption runs one of two ways: either “the IRB only reviews research, so this doesn’t need an IRB,” or “the IRB is reviewing it, so this must be research, so it needs a protocol and a consent form built like a study.” Both defaults are wrong. This guide works through the actual rule, the point in a HUD’s use where it genuinely can tip into research, and the operational mechanics — submission content, continuing review, emergency use, billing — that a research administrator or IRB coordinator needs to run this correctly.

For the underlying regulatory definitions — the 8,000-patient threshold, the “probable benefit” approval standard, the profit restriction, and how HDE compares to PMA, 510(k), and orphan drug designation — see CASRAI’s Humanitarian Use Device (HUD) dictionary entry. This guide assumes that background and focuses on what happens after a device is already HDE-approved and a clinician at your institution wants to use it.

The core distinction: clinical care that requires IRB approval anyway

Under the Common Rule and FDA’s human subjects regulations, IRB review exists to protect people enrolled in research — a systematic investigation designed to develop or contribute to generalizable knowledge. Using an FDA-approved device to treat an identified patient, following its approved labeling, applying the clinician’s own judgment about that patient’s care, is the textbook definition of clinical practice, not research. CASRAI’s human subjects research determination guide and 45 CFR 46 overview cover that boundary in general terms.

HUD use breaks the usual pattern that follows from that distinction. Regulation specific to this pathway — 21 CFR 814.124(a) — states plainly that “a HUD may be administered only if such use has been approved by an IRB,” and requires the HDE holder to ensure the device is used only at facilities with IRB oversight, “including continuing review of use of the device.” That requirement exists independent of whether the use is research. It attaches because of what an HDE approval actually is: FDA has found “probable benefit,” not the “reasonable assurance of effectiveness” a standard Premarket Approval (PMA) requires. The IRB is the substitute check that a use is clinically appropriate for a given patient, functioning here as an ongoing local-oversight body for a category of product FDA approved on a lower evidentiary bar — a role no other approved, on-label device use requires from an IRB.

Practically, this means a HUD sits in a category by itself: clinical, but IRB-gated. Get the classification wrong in either direction and something breaks — treat it as ordinary clinical care and the use is unauthorized under FDA regulation the moment it happens without IRB sign-off; treat it as full human subjects research and you build a protocol, consent, and reporting structure the regulation doesn’t actually call for and that slows a patient’s access to a device FDA has already approved for exactly this use.

Is my HUD use research? A decision framework

The determining question is not “is an IRB involved” — the IRB is involved either way. The determining question is whether the specific use is systematic and generalizable, or an individualized clinical decision for one patient guided by the device’s approved labeling.

Clinical use (IRB approval required, not human subjects research): A physician selects an HDE-approved device for an individual patient whose condition matches the device’s approved indication, using it per its labeling, exercising the same clinical judgment involved in prescribing any approved therapy. This is the ordinary case the HDE pathway was built for. It requires IRB approval under 814.124(a) and falls under the IRB’s clinical-oversight function for HUDs specifically, not its human-subjects-research function.
Human subjects research (full IRB human-subjects review, and possibly an IDE): The use tips into research when it stops being an individualized clinical decision and becomes a systematic investigation intended to generate generalizable knowledge — for example, a planned case series analyzing outcomes across patients for publication, a comparison against an alternative treatment, a protocol specifying a fixed evaluation schedule and endpoints applied uniformly regardless of individual clinical need, or any use outside the device’s FDA-approved indication. Off-label use of an HUD, or a systematic study of on-label use for a generalizable purpose, needs to go through the institution’s standard human-subjects-research determination process, and if the device is being studied rather than simply used, may separately require an Investigational Device Exemption (IDE) application — a different, “before it’s marketed” pathway covered in CASRAI’s IDE and significant risk determination guide. An HDE is a marketing authorization; an IDE authorizes a device for clinical investigation. A device can pass through both at different points in its life, but they answer different questions and neither substitutes for the other.
The gray middle: retrospective review and quality tracking. Reviewing a HUD’s outcomes across the patients who received it at your site — which the IRB will need for continuing review regardless — is not automatically research. Whether a retrospective look at that data becomes a research project (for a publication, say) turns on the same generalizable-knowledge test and should go through your institution’s quality-improvement-versus-research screening; CASRAI’s retrospective chart review and IRB requirements guide works through that screening in detail.

When the answer is genuinely unclear, route it through the same human-subjects-research determination process used for any borderline clinical-versus-research question at your institution, and document the determination in writing regardless of outcome — that documentation is what an auditor or FDA inspector will ask for later, not a verbal judgment call nobody wrote down.

What an IRB submission for HUD use needs to contain

Because HUD review sits outside standard human-subjects protocol review, many IRB submission templates don’t fit it well out of the box, and institutions that treat every HUD request as a full new-study protocol create unnecessary friction for what is, substantively, a clinical-use authorization. At minimum, a complete submission should include:

The FDA HDE approval order and approved labeling for the specific device, establishing the approved indication, contraindications, and the boundaries of on-label use.
A description of the intended clinical use at your site — which service or department will use the device, the patient population it will be offered to, and confirmation that the intended use matches the FDA-approved indication (or, if not, a clear flag that this is off-label and needs to be routed as research/IDE consideration instead).
The physician(s) or service authorized to use the device, since IRB approval attaches to a specific facility’s oversight, not to the device generally.
The patient information/consent process the treating clinician will use. Because a HUD’s effectiveness has not been demonstrated to the standard a PMA device has — only probable benefit — good practice is to document that this status was disclosed to the patient as part of routine informed clinical decision-making, even though HUD clinical use is not human subjects research and therefore isn’t governed by the Common Rule’s consent requirements. Many institutional policies require this documentation as a condition of local approval; check your own HRPP policy rather than assuming either way.
A plan for the continuing-review reporting described below — how the site will track and report the number of uses, and any adverse outcomes, at each review cycle.
The institution’s process for emergency use without prior approval, referenced below, so that if it happens, the notification obligation is already understood rather than discovered under time pressure.

Initial review, continuing review, and the expedited-review option

FDA and IRB guidance treat initial and ongoing HUD review differently:

Initial approval is expected to go through a convened IRB meeting, not an expedited or administrative path — this is the point at which the board is establishing, for the first time, that the device’s approved use is appropriate for your patient population and that your institution’s oversight structure meets 814.124(a).
Continuing review is required at least annually under the general IRB continuing-review requirements of 21 CFR Part 56, consistent with CASRAI’s Common Rule overview of how continuing review works generally. FDA guidance allows continuing review of a HUD used solely for clinical purposes to proceed through the IRB’s expedited review procedure rather than requiring a full board meeting every cycle — a meaningful administrative relief, but one the IRB has to affirmatively decide to use; it isn’t automatic.
What continuing review actually has to report is narrower than a typical study’s continuing review: at minimum, the number of times the device was used, whether each use fell within the FDA-approved indication and any IRB-imposed limitations, and any adverse events or outcomes of note. An IRB coordinator building a HUD-tracking form should design it around that reporting requirement specifically, rather than reusing a generic study continuing-review form built for enrollment and protocol-deviation tracking that doesn’t apply here.
Central IRB option. The 21st Century Cures Act opened the door to using a single central IRB for HDE oversight across multiple sites of use, instead of requiring separate local-IRB review at every site — the same direction the field has moved for multi-site device and drug trials generally. An institution using a HUD that’s also in use elsewhere should check whether the HDE holder has an existing central-IRB arrangement before defaulting to a full local review from scratch.

Emergency use without prior IRB approval

21 CFR 814.124(a) carves out one narrow exception to the “must have prior IRB approval” rule: if a physician determines, in an emergency situation, that IRB approval cannot be obtained in time to prevent serious harm or death to a patient, the HUD may be administered without prior IRB approval. The physician then has five days from the use of the device to provide written notification to the IRB chair, and that notification has to include the patient’s identification, the date the device was used, and the reason for the emergency use.

This is narrower than it sounds in practice: it is not a general “we didn’t have time to submit paperwork” exception, and it does not apply where the device’s use was foreseeable and IRB review could reasonably have been sought in advance. It exists for the genuine emergency case — the device is on hand, the patient’s condition doesn’t allow for the normal review timeline, and a delay would risk serious harm or death. Institutions running any program likely to use a given HUD should have this notification pathway built into their IRB’s operating procedures before the first emergency use happens, not improvised afterward under time pressure.

Separately, if an IRB withdraws its approval for a HUD’s use, the HDE holder is required to notify FDA of that withdrawal within five working days of being informed — a reporting obligation that runs from the device’s sponsor to FDA, distinct from the physician’s emergency-use notification to the IRB chair.

Who at an institution actually approves and administers this

A HUD request typically touches more offices than a standard new-therapy adoption, because it combines a device-procurement decision with a clinical-oversight determination that most other approved devices never trigger:

The IRB / Human Research Protection Program (HRPP) office holds the core statutory role — initial convened-board approval and continuing review under 814.124(a). This is the one step that cannot be skipped or delegated elsewhere, regardless of how the rest of the institution structures the request.
A device or new-technology committee (institutions vary in naming this a medical device committee, value analysis committee, or similar) commonly handles the procurement and clinical-service-adoption decision — whether the hospital will stock and offer the device at all — which is a separate question from IRB approval of its use and typically happens on a parallel or preceding track.
Risk management and the medical staff office are typically involved in credentialing which physicians or services are authorized to use the device, and in documenting the informed-clinical-decision conversation described above.
Billing and health information management need to be looped in early, given the coverage picture below — a HUD authorized clinically and approved by the IRB is not automatically a billable, covered service.

For an institution using a HUD for the first time, the most common operational failure is treating this purely as a procurement or purely as an IRB question, when it genuinely needs both tracks moving, with the IRB track gating the point at which the device can actually be used on a patient.

Billing and coverage: FDA approval does not mean Medicare coverage

An HDE approval is a marketing authorization from FDA. It is not a coverage determination, and the two run on entirely separate tracks that institutions new to HUDs frequently conflate. Under Medicare’s general “reasonable and necessary” standard (Social Security Act §1862(a)(1)(A)), an HDE-designated device is evaluated for coverage at the claim level — there is no advance national coverage determination specific to most HUDs, and traditional Medicare (Parts A/B) has no process for obtaining prior approval before use. Coverage is not guaranteed: contractors evaluate HDE claims individually against the reasonable-and-necessary standard on pre- or post-payment review, and denial is common enough that billing and case-management staff should treat “will this be covered” as a genuinely open question for each case, not an assumption. Medicare Administrative Contractors publish local coverage guidance specific to the HUD/HDE process (for example, Novitas Solutions’ LCD L36238 and its companion billing-and-coding article A57659) that billing staff handling device claims should review directly, since the applicable contractor and its specific guidance depend on jurisdiction.

Practically, this means a research administrator or clinical department planning to bring a HUD into use should loop in billing and revenue-cycle staff during the same planning conversation as the IRB submission, not after the device has already been used on a patient — a denied claim after the fact is a much harder problem than a documented coverage conversation before the fact. Private payers vary further still, and typically require their own case-by-case review; there is no substitute for checking with the specific payer for a specific device and patient.

Frequently asked questions

Does a HUD need informed consent like a research study does?

Not under the Common Rule, because on-label clinical use of a HUD is not human subjects research. That said, because the device’s effectiveness hasn’t been demonstrated to a PMA standard — only probable benefit — sound clinical practice, and many institutional HRPP policies, call for documenting that this status was disclosed to the patient as part of ordinary informed clinical decision-making. Check your institution’s specific policy; it varies.

Can a HUD be used off-label?

Using it outside its FDA-approved indication moves the activity out of the “clinical care with IRB oversight” category covered by 814.124(a) and into human-subjects-research territory, which needs to go through your standard research-determination process and may require an IDE if it constitutes a clinical investigation of the device. It is not simply a broader version of the same clinical authorization.

Does every use need a new IRB submission, or does one approval cover ongoing use?

One IRB approval covers ongoing clinical use at that site, subject to continuing review at least annually (which can typically proceed via expedited review for solely-clinical use, at the IRB’s discretion) rather than a fresh submission for every patient. The continuing-review cycle is where the IRB checks that use has stayed within the approved indication and any conditions it set.

What happens if a device is used in an emergency before IRB approval exists at all, not just before a particular review cycle?

21 CFR 814.124(a)’s emergency-use exception is about avoiding a delay in an individual patient’s care when time-sensitive harm is at stake; it presumes IRB oversight of the device generally is either already in place or being sought promptly, not that the institution can adopt a HUD with no IRB engagement at all and rely on repeated emergency-use notifications going forward. Standing use of a HUD needs standing IRB approval; the emergency exception is for the individual time-sensitive case, not a substitute for establishing that approval.

Is HDE approval the same as Medicare or insurance coverage?

No. FDA marketing authorization and payer coverage are decided independently. Traditional Medicare has no prior-approval process for HDE devices and evaluates claims individually against the reasonable-and-necessary standard; many HDE claims are denied. Confirm coverage expectations with billing and the relevant payer before assuming an FDA-approved HUD is a reimbursable one.

How is a HUD different from a device used under compassionate use or the Right to Try Act?

Those pathways cover access to a device or drug that has not yet been FDA-approved, for a patient who doesn’t qualify for a clinical trial. A HUD, by contrast, is already FDA-approved for its labeled indication under the HDE pathway — the regulatory question isn’t pre-approval access, it’s the IRB oversight condition attached to an already-approved product. See CASRAI’s Right to Try Act guide for how that separate pathway works and how it differs from expanded access.

Related CASRAI resources

Last verified: August 21, 2026, against 21 CFR 814.124 (IRB requirements for HUDs) via eCFR, FDA’s HUD/HDE program guidance, and CMS Medicare coverage guidance for the HUD/HDE process (LCD L36238 and Billing and Coding Article A57659). Regulatory and coverage guidance is updated periodically; verify current text directly against eCFR and the applicable Medicare Administrative Contractor before relying on any procedural detail here for a live IRB submission or billing decision.

Further reading: Protocol Deviation classification — When a major (important) protocol deviation happens, the study team’s response follows a specific sequence: address any immediate safety issue first, then document, classify, notify the sponsor and IRB, and close the loo.

Related reading: IRB Approval timeline — Typical IRB review timelines by review type (exempt, expedited, full board), what actually extends them, and how to plan a study timeline around IRB review realistically.

Related reading: FDA Approval for Gene Therapy — Gene therapy products are licensed via BLA (not approved via NDA), reviewed by CBER (not CDER), and often pursue RMAT designation. For more on this, see CASRAI’s guide to expanded access vs. compassionate use.

Humanitarian Use Device (HUD) and HDE: IRB Approval, Research vs. Clinical Care, and Billing

Ask about Humanitarian Use Device (HUD) and HDE: IRB Approval, Research vs. Clinical Care, and Billing