Part 2 FDA product-safety disclosure

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

This is a product-safety pathway

42 CFR 2.51 identifies the recipient, asserted threat, product-error context, and exclusive notification purpose. Verify the FDA medical personnel, office, contact route, product, asserted error, affected population, information requested, and intended notification use.

Use an independent FDA callback or approved agency channel rather than contact information supplied only in an unsolicited message. Record the medical person's name, role, office, facility affiliation where applicable, official contact, assertion, product identifier, manufacture, labeling, or sale error, health threat, affected people, deadline, and request source.

Distinguish this pathway from a manufacturer notice, distributor recall, device-vendor request, law-enforcement inquiry, regulatory inspection, complaint investigation, research study, or routine adverse-event workflow. Those situations may be urgent and important while requiring different authority.

The purpose boundary is narrow

The provision does not create general FDA, manufacturer, litigation, enforcement, marketing, or research access. Hold requests that mix purposes or come from an unverified intermediary. Route uncertainty through the Part 2 privacy owner and counsel while urgent safety work continues.

Ask which patient-identifying fields are required to notify patients or physicians of potential danger. Limit names, contact information, treating physician, product, lot, date, clinical detail, and other data to the supported notification function. Exclude counseling notes, unrelated episodes, billing history, and broad chart content unless qualified review connects them to the purpose.

Preserve the FDA assertion and program's scope decision. The program need not turn a focused notification list into an open research dataset or enforcement file. If the request adds analysis, investigation, follow-up, or third-party sharing, pause the added portion for a fresh review.

Secure the safety exchange

Confirm the official destination and use the approved secure method compatible with the urgency. Maintain an exact manifest of patients and fields sent, sender, recipient, time, transaction ID, and delivery evidence. Prevent insecure email subjects, filenames, labels, or shared drives from revealing Part 2 status.

If the FDA asks the program to help notify patients or physicians, define roles, scripts, safe contact preferences, failed-contact handling, and escalation separately. Do not use the safety event for unrelated outreach.

Document the error after disclosure

Record the receiving medical personnel and facility affiliation, discloser, date and time, and nature of the product error. Preserve the exact data sent and later corrections. Link any patient or physician notification work without broadening the original purpose.

Create the written record immediately after disclosure. Include the required elements in a controlled entry and add the verified request, threat, product, scope, route, and follow-up under approved policy. Retain original and corrected recipient lists instead of overwriting errors.

Review changes and defects

Reassess when the product, lot, threat, population, recipient, requested data, purpose, or notification plan changes. A second request is not automatically covered by the first. Keep corrections focused on the safety purpose and document what changed.

If data reached an unverified person, wrong destination, excessive recipient list, or secondary purpose, contain access where feasible, preserve evidence, and route privacy, security, legal, clinical, product-safety, and patient communication decisions. Review other files built from the same query or template.

Example with safety requests

Five product-safety requests are reviewed. Three come from verified FDA medical personnel for the exclusive notification purpose; two involve other agencies or broader analysis. Pathway fit is 3 of 5 requests.

The program handles the three qualifying requests through its controlled safety route. It holds the broader analysis and redirects the other-agency request to qualified review. Staff also narrow a query that included patients outside the identified product population.

FDA-safety checklist

• Verify FDA medical personnel through an independent official route.
• Record the asserted health threat and manufacture, labeling, or sale error.
• Confirm exclusive use to notify patients or their physicians.
• Select only patient-identifying information needed for that purpose.
• Use secure transfer and preserve a complete sent manifest.
• Document the product error and disclosure immediately.
• Reassess changed requests and contain recipient or scope errors.

Owner controls

The 2024 final rule supplies current context. Use FDA callback verification, product identifiers, purpose confirmation, minimum data, secure transfer, immediate documentation, follow-up tracking, and incident escalation.

Monitor FDA requests, verification, products and lots, people included, fields sent, notification outcomes, changed purposes, documentation delay, and incidents. Audit from disclosures back to verified medical personnel and exclusive notification purpose, then from safety queries into tested population and field logic. Retest after product, EHR, contact, vendor, or regulatory-process changes.