503Pharma Compliance Intelligence

JOIN FREE MEMBERS AREA | COMPLIANCE TRAINING | FORMULA LIBRARY

Welcome back to 503Pharma Compliance Intelligence.

This week’s edition: a California 503B outsourcing facility with a December 2025 warning letter. The issue isn't sterility or aseptic technique. It's what happened after a patient got hurt — and the report that never reached the FDA in time.

Let's get into it.

📋 THIS WEEK'S CASE

A 503B outsourcing facility in California, owned by a major telehealth company. FDA inspection May–June 2025. Warning letter issued December 2025. The central violation: failure to report a serious adverse event within the required timeframe.

WHAT HAPPENED

This facility compounds sterile drug products — including semaglutide injection — distributed to telehealth patients across the country.

During the inspection, FDA reviewed the facility's complaint records. One complaint documented a patient who experienced severe gastrointestinal issues and a three-night hospital stay after using a compounded semaglutide injection.

Under Section 503B, outsourcing facilities are required to submit reports of serious adverse events to the FDA within 15 days. This one wasn't reported on time.

The Core Violations

1. A serious adverse event went unreported.

The adverse event tied to Complaint Log #C25004 was not submitted to FDA as required. A serious adverse event — by regulation — includes outcomes like hospitalization. A three-night inpatient stay qualifies.

2. The facility's own procedures didn't define "serious."

FDA found that the facility's written adverse event reporting procedures did not adequately define what constitutes a "serious" adverse event under 21 CFR 310.305(b). Without a clear definition, staff had no reliable trigger for when the 15-day clock starts.

3. Retroactive reporting wasn't enough.

The facility did submit some adverse event reports retroactively — before the inspection. FDA acknowledged this. But the agency still found the underlying procedures deficient because they didn't clearly define reporting criteria or timelines going forward.

The Other Finding: Insects in the Production and Incubator Areas

The Form 483 also cited the facility for insanitary conditions — and the specifics matter.

Investigators observed a live spider in the production area where all active pharmaceutical ingredients are stored in refrigerators, including the semaglutide injection API. They also found a dead cricket in the middle of the incubator room — the room housing the incubators used for media fill vials and for environmental and personnel monitoring samples collected during production.

The facility corrected these conditions before the warning letter was issued, so they weren't cited in the final letter. But they're in the official inspection record — and they raise the same question the adverse event finding does: if the monitoring environment itself has insects in it, what confidence is there in the data coming out of it?

WHY THIS MATTERS FOR ALL OF US

1. Adverse event reporting is a condition of your 503B exemption.

This is easy to overlook. Sterility, potency, aseptic technique — those dominate the conversation. But for 503B facilities, timely adverse event reporting is a statutory condition under Section 503B. Miss it, and your products may lose their exemption status entirely.

2. A procedure that doesn't define "serious" can't be followed.

If your written procedure doesn't clearly define what counts as a serious adverse event, your staff are left guessing. Hospitalization, death, life-threatening events, disability, congenital anomaly, or an event requiring intervention to prevent permanent impairment — these are the regulatory benchmarks. Your SOP should name them.

3. The 15-day clock is specific.

Serious and unexpected adverse events must reach FDA within 15 calendar days. That's not 15 business days, and it's not "when you get to it." The clock starts when you receive the information.

4. Retroactive fixes don't close the gap.

Submitting late reports before an inspection is better than not submitting them. But FDA still evaluates whether your system will catch the next one. A reactive fix doesn't demonstrate a reliable process.

5. This applies to 503A pharmacies too — through MedWatch.

While the 15-day 503B requirement is specific to outsourcing facilities, every pharmacy should have a clear adverse event process. 503A pharmacies report through MedWatch. The principle is the same: know what's reportable, know the timeline, and document that you acted.

🛡️ BUILDING SYSTEMS THAT CATCH THIS

Adverse event reporting fails when no one's sure what counts or when the clock starts. A clear definition and a defined workflow turn a judgment call into a process.

Here's how CompoundLearn helps you stay ahead:

Training Modules Build competency in quality oversight with M7: Incident Reporting & Quality Mindset and DP-4: Quality Assurance Program — so your team knows what a serious adverse event is, when it's reportable, and who's responsible for filing.

SOP Library Access ready-to-use procedures for adverse event reporting, complaint handling, and deviation investigations — with clear definitions and timelines built in. Don't reinvent the wheel — customize proven templates.

Competencies Assign and track role-specific qualifications. Ensure the person handling complaints knows what triggers a 15-day report. Document who's trained on what.

Templates Generate adverse event report forms, complaint logs, and investigation records. Audit-ready documentation that takes seconds to create.

Assessments Verify that your team can identify a reportable event and act within the required timeframe. Document the results automatically.

One unified system for training, documentation, and compliance.

A warning letter for a report you never filed. Or a system that flags it the moment the complaint comes in.

[Explore CompoundLearn →]

✅ THIS WEEK'S ACTION ITEM

Pull your adverse event reporting SOP. Check three things:

1. Does it clearly define what makes an adverse event "serious"? (Death, life-threatening, hospitalization, disability, congenital anomaly, or intervention to prevent permanent impairment.)

2. Does it state the reporting timeline — and when the clock starts?

3. Does it name who is responsible for filing?

If any of those are missing, your procedure won't hold up — and neither will your response when an event comes in.

Reply and tell us: Was this useful? What would make it better?

✉️ That’s your 503Pharma Intel Brief. Our mission is to keep compounding professionals informed, prepared, and ahead of the curve.