An FDA 522 Order Is Not a Study Status: Rebuild the Full Surveillance Record
Connect an FDA Section 522 order, surveillance question, approved plan, milestones and reports before scoping postmarket study support.
Signals to watch
- A manufacturer mentions a 522 order number but cannot produce the current approved surveillance plan or FDA correspondence
- Enrollment, interim-report or completion language appears without the surveillance question and milestone dates that give it meaning
- A public database status is forwarded as if it were the entire study record, while the order, protocol and latest submission remain missing
A Section 522 order is the start of a surveillance obligation, not a complete description of the study. Before a medical-device postmarket consultancy scopes support, connect five objects: the FDA order, the public-health question, the FDA-approved surveillance plan, the dated milestones, and the interim or final reporting record. If any one is missing, “the 522 study is late” is still an allegation, not a reproducible status.
Section 522 postmarket surveillance is the active, systematic and scientifically valid collection, analysis and interpretation of information about a marketed device under an FDA order. The FDA 522 program page says the program covers study design, tracking, oversight and review. It is intended to answer surveillance questions and collect useful data about unforeseen adverse events or other information needed to protect public health.
This distinction matters to a medical-device postmarket consultancy practice lead who follows authorised regulatory-affairs, quality and postmarket-operations Telegram groups. A message such as “enrollment is behind and the next 522 update is due” can indicate a real study-support need. Seeing it a day late may mean another provider has already framed the protocol amendment, site-recovery or reporting work. It still does not reveal the manufacturer, device, order, approved enrollment target or due date.
The order defines why FDA required surveillance
Start with the signed order and its exact number. Under 21 U.S.C. 360l, FDA may require surveillance for a class II or class III device when specified criteria apply. These include a failure reasonably likely to have serious adverse health consequences, expected significant pediatric use, implantation for more than one year, or life-sustaining or life-supporting use outside a device user facility.
Device class, a recall, or a complaint trend does not independently prove that a 522 order exists. The order identifies the device scope and the surveillance requirement imposed by FDA. The program page also cautions that one device can have more than one requirement under an order. Record the order number, order date, manufacturer, device names and identifiers, statutory criterion, each surveillance question, and any later order modification.
The first unknown is often the most important: what question must the study answer? “Monitor long-term safety” is too broad. The order and approved plan may focus on a defined adverse outcome, durability question, pediatric use, real-world use condition or another device-specific uncertainty. That question controls the population, endpoints, follow-up period and useful-data test.
The plan converts the question into an executable study
The statute gives the manufacturer 30 days after receiving the order to submit a surveillance plan for FDA approval. FDA has 60 days after receiving the plan to determine whether the designated investigator is appropriately qualified and whether the plan will collect useful public-health data. Surveillance must commence no later than 15 months after FDA issues the order.
Those clocks should not be collapsed into one “study due date.” Keep the order date, plan-submission date, FDA receipt date, approval or disapproval correspondence, and commencement evidence separately. For most devices, FDA may require a prospective surveillance period of up to 36 months. A longer period ordinarily requires agreement or dispute resolution; for devices expected to have significant pediatric use, the statute permits FDA to order more than 36 months when necessary to assess growth, development or related effects.
An approved plan should be read as the operating specification. Capture the study design, population, inclusion criteria, sample size, endpoints, data sources, follow-up, enrollment milestones, report schedule, analysis method and named responsible parties. Then add every FDA-approved amendment as a dated layer. A draft protocol, contract scope or internal project plan cannot silently replace the current approved plan.
Milestones show whether the plan is operating as approved
Consider this illustrative fragment, not a customer statement or a real FDA record:
“522 enrollment is only about halfway there. Steering committee wants options before the next FDA update. Does anyone know a group that can rescue sites?”
The fragment exposes a possible service window but leaves the denominator unknown. “Halfway” could refer to screened subjects, enrolled subjects, completed follow-up, evaluable records or an internal forecast. It does not name the approved target, milestone date, attrition assumptions, device version, geographic scope or last FDA response.
Reconstruct the milestone line from the approved plan and subsequent correspondence. For each milestone, retain the planned value, reporting period, actual submitted value, submission date, FDA assessment and open corrective action. Separate recruitment shortfall from follow-up loss, data-query backlog, protocol deviation or analysis delay because each produces a different first engagement.
The FDA 522 database can be searched by manufacturer, device name or order number. FDA says it publishes study descriptions, interim and final result summaries, overall study status and reporting status for submissions due, and updates the database every Sunday. That makes it a strong discovery and cross-check source. It is not a substitute for the approved plan, complete FDA correspondence or the submission itself.
Reports connect work performed to FDA’s current assessment
Do not scope “write the interim report” until the reporting object is identified. Link each submission to the reporting period, plan milestone, data cut, study version and FDA response. Preserve whether the item is an interim report, final report, plan amendment, response to a deficiency, or another submission. A forwarded screenshot that only shows “overdue” or “inadequate” loses the submission it describes.
The evidence map should distinguish three statements:
- What the manufacturer submitted: the actual report, date, data cut and stated limitations.
- What FDA recorded: the public database status and any written assessment available to the authorised reviewer.
- What remains to be done: a missing submission, plan correction, enrollment recovery, analysis, response or closeout task with an owner and due date.
FDA explains that older database entries can retain legacy status terms until new information is reviewed. Copying a label without its update date can therefore produce a stale sales brief. The practice lead should date the public lookup and request the current native records before quoting.
A bounded first engagement starts with the missing object
The first engagement should repair one gap that can be verified. If the order and question are missing, begin with order retrieval and scope reconstruction. If the approved plan is available but milestones do not reconcile, build a milestone variance assessment. If the latest submission lacks traceable data, map the data cut and report sections. If FDA correspondence identifies deficiencies, scope the response against those specific comments.
TOP Prospect can surface related fragments from Telegram groups the user deliberately connected and is authorised to access, then preserve original text, source, time, summary and ranking reason for human review. A newly saved matching target stores configuration only; it does not automatically run or create candidates. The product cannot enter FDA systems, obtain confidential orders, read study data, judge plan adequacy, submit reports or contact message authors.
For an adjacent quality-system request, use the FDA QMSR and ISO 13485 gap-assessment boundary. If the question is which public FDA record can support a device claim, follow the MAUDE, recall and MedWatch source routing. The Telegram business-signal workflow explains how authorised fragments remain candidates until a qualified person checks the native evidence.
Key facts
- FDA can order Section 522 surveillance for specified class II or class III devices; class alone does not establish an order.
- A manufacturer must submit its surveillance plan within 30 days after receiving the order.
- FDA has 60 days after plan receipt for the statutory plan determination, and surveillance must commence within 15 months after the order.
- The usual prospective surveillance period can be up to 36 months; a pediatric device can require a longer period under the statutory condition.
- The FDA database publishes order and study-status information and is updated every Sunday, but native plans, amendments and reports remain necessary for a complete review.
- Routine complaints and other postmarket data may feed a study, but they do not replace the ordered surveillance question and approved plan.
FAQ
Is every class II or class III device subject to a Section 522 study?
No. FDA may order postmarket surveillance for specified devices that meet statutory criteria. Device class by itself does not prove that FDA issued an order.
How soon must a manufacturer submit a surveillance plan after receiving a 522 order?
The manufacturer must submit a plan for FDA approval within 30 days after receiving the order. FDA then has 60 days after receiving the plan to make the determination described in Section 522.
Does a 522 database status replace the approved plan or latest report?
No. The database supports discovery and status checking. The approved plan, amendments, milestone correspondence and submitted reports are needed to reproduce the current obligation and remaining work.
Is Section 522 surveillance the same as routine complaint trending?
No. Complaint trending may provide relevant postmarket evidence, but a 522 study answers a surveillance question imposed by an FDA order under an approved plan with defined milestones and reports.
Editorial review completed 21 August 2026 against the current FDA 522 program page, October 2022 FDA guidance, 21 U.S.C. 360l and 21 CFR Part 822. This article is not legal, regulatory or clinical advice.
Frequently asked questions
Is every class II or class III device subject to a Section 522 study?
No. FDA may order postmarket surveillance for specified class II or class III devices that meet statutory criteria. Device class alone does not prove that an order exists.
How soon must a manufacturer submit a surveillance plan after receiving a 522 order?
Section 522 requires the manufacturer to submit a plan for FDA approval within 30 days after receiving the order. FDA then has 60 days after receiving the plan to make the statutory determination described in the Act.
Does a 522 database status replace the approved plan or latest report?
No. The database helps identify the order and reported study or submission status, but the approved plan, amendments, milestone correspondence and submitted reports are needed to reproduce the current obligation.
Is Section 522 surveillance the same as routine complaint trending?
No. Routine postmarket systems may supply relevant evidence, but a 522 study answers a surveillance question under an FDA order and an approved plan with defined milestones and reports.
Sources and further reading
How a Signal worth attention is found
See how Top Prospect finds and organizes Signals worth checking, keeps the original Telegram context, removes duplicates, and helps you decide what to review first. You decide whether to follow up and what to do next.
