Medical Device Complaint Handling: What Counts, Who Logs It, and What Happens Next

Medical device complaint handling changed its legal address on February 2, 2026. On that date, FDA’s Quality Management System Regulation took effect. The familiar complaint rule, 21 CFR 820.198, no longer exists. However, many procedures, training decks, and call scripts still cite it. That gap matters, because complaints rarely arrive through the quality department. They arrive through a phone queue, a chat window, or a field technician.

This guide answers three practical questions. First, what counts as a complaint under the current medical device complaint handling process? Second, who has to log it, and how fast? Third, what happens once the record exists? Along the way, it separates complaint intake from medical device reporting, which runs on its own clock. It also draws an honest line around what a support team should never decide.

What Medical Device Complaint Handling Means Under the QMSR

For nearly three decades, FDA complaint handling requirements lived in one section of the Quality System Regulation. The QMSR final rule replaced that structure. Instead of writing its own text, FDA incorporated ISO 13485:2016 by reference. As a result, the current Part 820 now holds only six sections. The regulation did not get lighter. It moved house and left a forwarding address in Geneva.

QMSR complaint handling now sits in two places. Clause 8.2.2 of ISO 13485 sets the base process. In addition, 21 CFR 820.35(a) adds FDA’s own record requirements on top. Therefore, a procedure that still cites 820.198 points to a section that is gone. Auditors notice that kind of thing, usually on the first page.

Certification does not replace inspection, either. FDA’s QMSR FAQ is blunt on the point. “A certificate of conformance to ISO 13485 will not exempt a manufacturer from an FDA inspection.” Furthermore, the agency withdrew its old inspection technique on the same date. Investigators can now review management review, quality audit, and supplier audit reports. Consequently, your audit of an outsourced intake vendor can land on an investigator’s desk.

What Counts as a Complaint in Medical Device Complaint Handling

A complaint rarely introduces itself as one. Nobody calls to report a possible failure to meet specifications. They say the pump beeps at night for no reason. ISO 13485 defines the term broadly. In plain terms, it covers any written, electronic, or oral communication alleging a deficiency in a released device. That reaches quality, durability, reliability, usability, safety, and performance.

FDA’s record rule then names three targets. Under 820.35(a), manufacturers keep records for complaints “involving the possible failure of a device, labeling, or packaging.” Note the word possible. The caller does not need to be right, and the device does not need to be broken. Nothing needs proving at intake. Moreover, labeling and packaging count alongside the hardware. A confusing instruction sheet can therefore start a complaint record.

Complaint Sources and User Error

The channel does not matter. FDA’s MDR guidance for manufacturers lists telephone calls, faxes, letters, and email as complaint sources. That 2013 guidance predates the QMSR and still cites the old section number. However, its reporting logic rests on Part 803, which did not change. Chat and social messages arrive the same way today, and the ISO definition covers electronic communication.

User error deserves special attention, because intake teams dismiss it most easily. Part 803 lists user error among the ways a device may have “caused or contributed” to harm. In other words, a patient who admits a mistake has not closed the matter. The manufacturer still has to evaluate what happened. An agent who says “that one is on you” and ends the call has lost a record.

Complaint, Inquiry, or Service Issue: Worked Examples

The table below shows how common contacts tend to sort. It is illustrative only, and your written complaint handling procedure governs. When in doubt, the safer habit is simple: capture everything and let quality decide.

Notice how many rows start as ordinary support calls. For that reason, complaint detection belongs in technical support workflows, not only in quality. Similarly, durable medical equipment suppliers hear device problems daily during resupply and billing calls. Each of those conversations is a potential intake point.

Medical Device Complaint Handling and MDR Reporting Run on Different Clocks

Complaint handling and medical device reporting are related, but they are not the same duty. Every complaint needs evaluation, yet only some become reports to FDA. Under 21 CFR Part 803, a reportable event has two main forms. First, the device may have caused or contributed to a death or serious injury. Second, it malfunctioned in a way likely to cause such harm if it recurred.

The definition of malfunction is wider than most support teams assume. Part 803 calls it “the failure of a device to meet its performance specifications or otherwise perform as intended.” It then adds a sentence that marketing teams should read twice. “Performance specifications include all claims made in the labeling for the device.” Consequently, a device that works but falls short of a labeled claim can qualify.

The volume shows how much traffic the system carries. According to FDA, the agency receives “over two million medical device reports” each year. Those cover suspected deaths, serious injuries, and malfunctions. However, FDA also cautions that a report is not proof of fault. Submitting one “is not evidence that the device caused or contributed” to the outcome. Reporting is a surveillance duty, not a confession.

The MDR Reporting Clock Starts at Awareness

The MDR reporting deadlines are short. Manufacturers generally have 30 calendar days to report after they become aware of an event. That window shrinks to five work days when remedial action must prevent an unreasonable risk of substantial harm. The key phrase is “become aware.” For the 30-day report, the clock starts when “any of your employees becomes aware of a reportable event.” It does not wait for the quality team to open a ticket.

What about people who answer on your behalf? The regulation speaks of employees and stays silent on vendors. FDA’s guidance fills part of that gap. It says MDR procedures “should identify the roles and responsibilities of contractors or consultants” who process complaints. Therefore, the cautious approach is to treat the vendor’s first contact as your awareness date. Write that into the contract before anyone tests the alternative.

Who Logs It: Roles in the Medical Device Complaint Handling Process

The practical model has two halves. Anyone who receives possible complaint information forwards it. Designated quality and regulatory staff then evaluate it. FDA’s guidance states the first half plainly. Manufacturers should tell all employees to “immediately forward adverse event information to the appropriate person.” The guidance names marketing, sales, engineering, legal, installation, and service staff. In short, nobody may sit on a complaint because it arrived in the wrong inbox.

The second half belongs to the quality and regulatory roles your procedure names. They evaluate each complaint, decide whether to investigate, and determine reportability. Those calls need medical, technical, and regulatory judgment. A frontline agent should make none of them. Instead, the agent’s job is narrower and still essential: recognize, capture, and route.

Three Roles in Medical Device Complaint Handling

In practice, a workable complaint handling procedure splits into three roles. Intake recognizes a possible complaint and records the facts in the caller’s own words. Next, a complaint unit reviews the record, requests missing details, and classifies it. Finally, regulatory affairs makes the MDR decision and files where the rule demands it. Trouble starts when the first role quietly performs the second. An agent who decides something is “not a real complaint” has made a regulatory call without the authority.

Complaint intake rarely lives in one place. A medtech support operation typically runs phones, chat, email, and field service at once. Meanwhile, distributors and clinical educators hear problems that never reach a queue. Each channel needs the same trigger questions and the same route to quality. Otherwise, your complaint data reflects your org chart more than your product.

The split between intake and decision leads to the most practical point in this guide. You can outsource intake, but you cannot outsource accountability. A partner can recognize, capture, and route on your behalf. However, the evaluation and the reporting decision still answer to your quality system. The final section covers where that line sits.

What Happens Next: From Complaint Intake to MDR Decision

Logging is the start of the process, not the end. Once a record exists, four more questions follow, and each has a different owner. The table below shows the usual stages. Owners are typical, so your complaint handling procedure should name the actual roles.

One point in that table deserves care. The stages read as a neat sequence, but two of them overlap. The 30-day MDR clock runs from awareness, not from the end of the investigation. Therefore, regulatory affairs often has to assess reportability while the investigation is still open. Waiting for a root cause before asking the reporting question is how deadlines slip.

The Complaint Handling Record: Seven Fields in 21 CFR 820.35(a)

This is where the regulation gets usefully specific. Section 820.35(a) lists the information a manufacturer must record. The list applies to complaints that require an FDA report and to complaints the manufacturer investigates. Intake cannot know in advance which complaints those will be. Therefore, capture the fields every time. The table maps each requirement to what an agent actually does.

Where Complaint Records Fall Short

Two fields cause the most damage when they go missing. The first is the received date, because it anchors the reporting clock. The second is device identification, because investigation stalls without a lot or serial number. Moreover, a caller who has thrown the box away rarely calls back with the number. Ask for it while they are still on the line.

The same section also permits a shortcut, with a condition. If a similar complaint already received an investigation, another one is not necessary. However, the manufacturer must document the justification for skipping it. That decision belongs to quality, and it depends on consistent intake wording. Sloppy descriptions make similar complaints look different, and different ones look the same.

Where the Complaint Handling Process Breaks Down

FDA’s enforcement data shows where complaint systems have struggled. In its calendar 2016 quality system data, FDA recorded 3,027 inspection observations against Part 820. The corrective and preventive action subsystem drew 1,017 of them, or 34 percent. Complaint procedures alone accounted for 286 observations. Those figures are a decade old and cite the former section number. Still, they show where investigators have historically looked first.

A well-known example shows the cost of logging without analysis. In a May 2022 proposed order, FDA described how Philips Respironics handled foam degradation complaints. Philips’ own review confirmed 1,254 such complaints between 2014 and April 2021. Of those, 110 arrived between 2014 and 2017. FDA stated that Philips “failed to adequately evaluate this data and incorporate it into its CAPA system.” Those statements come from FDA’s proposed order, not from a court ruling. Even so, the lesson holds: the complaints sat in the system while the pattern went unread.

FDA’s own QMSR overview deck borrows a line it attributes to John Ruskin. “Quality is never an accident; it is always the result of intelligent effort.” Complaint handling is the least glamorous proof of that idea. It fails quietly, in small omissions, long before anyone issues a recall.

Four Intake Failures in Medical Device Complaint Handling

Four breakdowns tend to appear at the intake stage. First, agents resolve the issue and never record it, because a fixed problem feels finished. Second, no-fault-found returns close without a complaint review. A no-fault-found result describes the test bench, not necessarily the patient’s experience. Third, after-hours calls go to voicemail, and the received date slips by a weekend. Fourth, non-English callers get a shortened version of the script.

The language point deserves a sentence more. A complaint made in Spanish is still a complaint, and the clock does not pause for translation. Therefore, Spanish-language support needs the same trigger questions and the same record fields. Relaying the call through an interpreter adds a step where details vanish.

What an Outsourced Team Should and Should Not Do in Complaint Handling

Many manufacturers route first contact through an outside partner. That can work well, within limits. An inbound contact center can answer every channel, apply trigger questions, and capture the seven fields. It can also timestamp first contact and escalate the same day. Those are intake tasks, and trained agents perform them reliably at scale.

The limits matter more than the capabilities. An outsourced team should not decide whether a contact is a complaint. Nor should it judge reportability, assess causation, or close an investigation. In addition, it should never offer clinical advice or speculate about what went wrong. Those decisions stay with the manufacturer’s quality and regulatory functions. As noted earlier, the task can move, but the accountability stays on your letterhead.

What the Vendor Contract Should Cover

Because accountability stays put, the contract has to carry the detail. Define the escalation trigger, the route, and the maximum time from first contact to handoff. Specify who owns the recordings and how long the vendor keeps them. For reference, Part 803 requires MDR event files for two years or the device’s expected life, whichever is greater. In addition, plan to audit the vendor, since FDA can now review supplier audit reports. Ask for the scope behind each credential on a vendor’s certifications page, not just the logo.

Privacy needs a paragraph of its own. Complaint calls frequently include health details, because patients explain why they use the device. Whether HIPAA applies depends on the manufacturer’s role and the data flow. Either way, the record deserves the safeguards covered in our guide to HIPAA-compliant patient support. Collect what the complaint record needs and nothing more.

Where SkyCom Fits in Medical Device Complaint Handling

SkyCom works on the intake side of the line this guide draws. Our nearshore teams provide medical device support and complaint intake across phone, chat, and email, in English and Spanish. That work sits within our wider healthcare practice. We capture, timestamp, and route, and your quality team decides. That division is deliberate. It is also the only version we recommend.

Conclusion: Medical Device Complaint Handling Starts With the First Hello

Medical device complaint handling has a new legal home, but its logic has not changed. A complaint is any allegation that a released device, its labeling, or its packaging fell short. It counts whether it arrives by phone, chat, or a technician’s note. Furthermore, it counts even when the caller blames themselves.

The answer to who logs it is equally plain. Anyone who hears it forwards it, and intake records it the same way every time. Quality and regulatory affairs then decide what it means. Get the first step right, and every later step has something to work with. Get it wrong, and the best CAPA system in the industry is analyzing an empty file.

Frequently Asked Questions

What is medical device complaint handling?

It is the process a manufacturer uses to receive, record, evaluate, and investigate allegations about a released device. Under the QMSR, the process follows ISO 13485 Clause 8.2.2 and 21 CFR 820.35. It also feeds the separate decision on whether to report an event to FDA.

Is 21 CFR 820.198 still in effect?

No. The QMSR took effect on February 2, 2026 and restructured Part 820. FDA complaint handling requirements now come from ISO 13485 Clause 8.2.2, with record rules in 21 CFR 820.35. Procedures that still cite 820.198 need an update.

Does every complaint have to go to FDA?

No. Every complaint needs evaluation, but only reportable events go to FDA under Part 803. Those involve a death, a serious injury, or a malfunction likely to cause either if it recurred. The manufacturer’s regulatory function makes that determination.

How quickly must a manufacturer report a device event?

Manufacturers generally have 30 calendar days after becoming aware of a reportable event. The deadline drops to five work days when remedial action must prevent an unreasonable risk of substantial harm. Awareness can begin with any employee, so the first contact date matters.

Does user error count as a complaint?

It can. Part 803 includes user error among the ways a device may have caused or contributed to an event. FDA’s guidance says an event caused solely by user error, with no death or serious injury, needs no MDR. However, that conclusion belongs to the manufacturer after evaluation, not to the agent on the call.

Can a call center handle medical device complaints?

A call center can handle complaint intake. That means recognizing a possible complaint, capturing the required fields, and escalating promptly. It should not decide whether a contact is a complaint, whether it is reportable, or what caused it. The manufacturer stays accountable for the whole process, so the contract should define roles precisely.

What information must a complaint record include?

Section 820.35(a) lists seven items for investigated and reportable complaints. They cover the device name, received date, device identifiers, complainant contact details, complaint details, corrective action, and any reply. Capturing all seven at intake avoids chasing callers later.

How long must MDR records stay on file?

Part 803 requires manufacturers to keep MDR event files for two years from the event date. If the device’s expected life is longer, that longer period applies. Check your own procedure as well, because other record rules may extend it.