Companies still ask for a MedWatch 3500A alternative when the safety file is a PDF, a fax, or a form someone retypes. FDA’s current instructions for industry ICSRs point at two electronic routes into the FDA Adverse Event Monitoring System (AEMS), formerly the FDA Adverse Event Reporting System (FAERS). One is an E2B file through the Electronic Submissions Gateway Next Generation (ESG NextGen). The other is the Safety Reporting Portal. This page says what the cited FDA documents actually cover. It does not price a vendor, and it does not say FDA prefers one.
What Form FDA 3500A is, and who still uses it
MedWatch is FDA’s program for safety information and adverse event reports from health professionals, patients, and consumers. The program page says MedWatch receives those reports and, when appropriate, publishes safety alerts for medicines, biologics, devices, combination products, cannabinoid hemp products, and cosmetics. Tobacco, vaccines, and animal products use other portals. The program page, as cited here, does not define Form FDA 3500A field by field. Treat a downloaded blank as a form you still have to match to a current FDA instruction.
The AEMS electronic submissions page still names Form FDA 3500A in one place. For bioavailability and bioequivalence studies that are exempt from an IND, electronic submission of the ICSRs is voluntary. FDA says you may continue to submit those safety reports on Form FDA 3500A to the premarket safety reports mailbox listed on that page. That is a specific remaining use. Read it as written, for those studies.
Mandatory postmarketing ICSRs for human drug and biological products are described on the same page as electronic submissions to AEMS, formerly FAERS. If your team’s 3500A habit is a marketed product, the pages below are the ones to reconcile with your SOP. Confirm the mailbox and the form against the live FDA page before you change a study procedure. This article is not the FDA instruction.
The electronic submission rule
The AEMS page dates the electronic requirement to 10 June 2014, when FDA issued the final rule on postmarketing safety reports for human drug and biological products. FDA’s summary on that page: industry must submit those reports in an electronic format FDA can process, review, and archive. The 6 April 2026 notice, 91 FR 17284, repeats that the postmarketing regulations require electronic ICSRs, and it says FDA’s guidance on providing submissions in electronic format gives two options.
Those two options, in the notice, are direct submission through ESG NextGen, or submission through the Safety Reporting Portal. The notice says the portal is there so applicants, specified nonapplicants, and responsible persons who do not have ICH E2B(R3) capability can still submit ICSRs and attachments. The notice then limits its own E2B(R3) instruction: it applies to submission through ESG NextGen.
Beginning 1 October 2026, postmarketing ICSRs for human drug products, biological products, and combination products led by a drug or a biologic, sent through ESG NextGen, must use ICH E2B(R3) in the AEMS database, formerly FAERS. FDA says it will accept E2B(R2) through 30 September 2026 for companies that have not switched. After a company starts sending E2B(R3), later ICSRs are expected to use that standard. The AEMS page says companies submitting through the Safety Reporting Portal have no action item from this change.
The Safety Reporting Portal and an E2B(R3) file
The portal and the gateway solve different problems.
- Safety Reporting Portal. A person with an account types the ICSR into a web form. FDA says to contact the AEMS electronic submission address to say you intend to start, and that the account is activated in about 7 to 10 business days. The AEMS page limits this path to reporters who do not have E2B capability. A gateway partner, meaning a company that submits ICSRs through ESG NextGen, cannot use the portal for those ICSRs and attachments.
- ESG NextGen. The safety database sends XML. From 1 October 2026 that XML, for the postmarketing products named above, uses E2B(R3). FDA posts the regional implementation guide, the business rules, and a validator on the AEMS E2B(R3) data standards page. The notice lists examples of what changed from E2B(R2): new, changed, and expanded data elements; seriousness assessed at the event level rather than only for the case; attachments embedded in the ICSR rather than sent beside it.
Choosing the portal because a 3500A PDF feels familiar is a choice FDA describes for companies that do not have E2B capability. It is not a second door for a company that already has a gateway account. The E2B(R3) case preparation page on this site is about getting a reviewed case ready for the database that builds the file. The database remains the system of record.
Effort, without a price list
FDA does not publish a fee schedule for these paths on the pages cited here. This article will not invent a dollar comparison. The effort difference is in the steps those pages describe.
- A form someone fills by hand. The narrative is typed again, often from email. Attachments are separate. For marketed product ICSRs, the 2014 rule as summarized by FDA asks for an electronic format FDA can process, review, and archive. A leftover PDF habit has to be checked against that rule and against the two options in the 2026 notice.
- Safety Reporting Portal. Account request, about 7 to 10 business days, then manual entry of each ICSR. Fit for a company FDA describes as lacking E2B capability. Volume stays on the person at the keyboard. The 1 October 2026 E2B(R3) switch is not an action item for this path, according to the AEMS page.
- ESG NextGen. An account, an E2B(R3) file, and a check against FDA’s validator and business rules before 1 October 2026 if you will still be on this path that day. After you send the first E2B(R3) ICSR, FDA expects the later ones to match. You cannot keep the portal as a quiet backup once you are a gateway partner.
A large safety database can be more system than a first filing needs. That operational question is discussed in why Vault Safety and Argus can be more than an early program needs. It is a staffing question. It is not an FDA ranking of products.
From structured intake to an E2B(R3) file
Whichever route you use, the case starts as a report from a person. A 3500A alternative that only changes the last click still leaves the inbox as the record. Structured intake records the reporter, the patient, the suspect product, the event in the reporter’s words, and the date your company first received the information. That is the material the portal form asks someone to type, and the material an E2B(R3) file has to carry.
AE Connect is the intake workspace for that step. You paste or upload the source. A draft proposes the fields. A person accepts or overrides each one. The reviewed case can feed Oracle Argus, ArisGlobal LifeSphere, or Veeva Vault Safety, or AE Connect can hold the full ICSR and the E2B(R3) file. See the product page and book a demo if you want to watch a case, not a slide.
None of that is a statement that FDA endorses, approves, or partners with AE Connect. The MedWatch page, the AEMS page, and 91 FR 17284 do not name this product. Submission to AEMS, formerly FAERS, happens in the gateway or the portal your company is set up to use.
See the intake step
Open the workspace, paste a source, and review the draft. A company email starts a 14 day sandbox trial. The safety database remains the system of record when you use one.
FAQ
Is Form FDA 3500A still accepted for postmarketing ICSRs?
The AEMS electronic submissions page says postmarketing safety reports for human drugs and biological products have had to be electronic since the final rule of 10 June 2014. The two electronic options FDA describes are ESG NextGen and the Safety Reporting Portal. The same page still allows Form FDA 3500A for safety reports from bioavailability and bioequivalence studies that are exempt from an IND. That remaining use is specific. It is not a general paper path for marketed product ICSRs.
What is the difference between the Safety Reporting Portal and E2B(R3)?
E2B(R3) is the data standard for an ICSR file sent from a database through the Electronic Submissions Gateway Next Generation to AEMS, formerly FAERS. The Safety Reporting Portal is a web form for applicants and responsible persons who do not have E2B capability. A company that already submits through the gateway cannot use the portal for those ICSRs. The 1 October 2026 E2B(R3) requirement in 91 FR 17284 applies to ESG NextGen.
Does FDA prefer a vendor as a 3500A alternative?
The MedWatch page, the AEMS electronic submissions page, and the 6 April 2026 Federal Register notice do not name a preferred software vendor. AE Connect is an intake workspace. It is not Form FDA 3500A, it is not the Safety Reporting Portal, and it is not ESG NextGen.