AE reporter forms for patients and healthcare professionals

A patient emails the medical information address: "Started your drug Tuesday. Rash and swelling by Thursday. Went to urgent care." A nurse practitioner sends three lines about a hospitalization and leaves no callback number. Both messages are adverse event reports. Neither is yet a case a regulator can receive. The missing pieces are ordinary. Who can be contacted. Which person the event happened to. Which product. What happened, in the reporter's words. Biotechs that leave this in a mailbox lose those pieces, and the follow-up that would have supplied them starts late or never starts. A reaction that never becomes a valid case cannot be compared with the next one. That is the patient-safety problem inside a sloppy intake, before anyone argues about a file format.

This page is about the reporter. The PV case intake form is what the drug-safety team stores after the report arrives. AE and SAE reporting is the medical classification that comes after the facts are in one place. The question here is what a patient or a healthcare professional has to be asked, and which clock can start only when the answer is complete.

The reporter is a primary source

ICH E2D(R1), the post-approval safety-data guideline adopted at Step 4 on 15 September 2025, calls the person who provides the facts a primary source. Teams usually say "reporter." A healthcare professional, in that guideline, is medically qualified: a physician, dentist, pharmacist, nurse, or a coroner if medically trained, unless a region defines the term differently. A consumer is a primary source who is not a healthcare professional. The examples are the patient, a legal representative, a caregiver, a friend, or a relative. The person who later transmits the case to an authority is a sender. The sender is not the primary source.

EU GVP Module VI (Rev 2) is the practical test when the file is thin. Section VI.B.2. says a reporter is identifiable when the organization has enough evidence that the person exists: a name, initials, or an address, and an address can be an email or a phone number. For an individual case safety report to be valid for submission, the same section requires the reporter's qualification and country, drawing the qualification-and-country rule from ICH E2B. If qualification was never captured, treat the report as a consumer report by default. If the country is missing, use the country where the notification was received or where the review took place. Record contact details so follow-up is possible. If the reporter will not leave a contact, the case can still be valid when the organization is able to confirm it directly with that person.

Hearsay is a different failure. GVP says a second-hand report is not valid until someone verifies it with the patient, the patient's healthcare professional, or a reporter who had direct contact with the patient. "A colleague heard about a patient" does not pass. An email from the patient, with a name or a phone number, can.

Spontaneous, solicited, and the IND path

E2D(R1) defines a spontaneous report as a direct communication by a healthcare professional or a consumer to the company, a regulator, or another organization, describing an adverse event in a patient who was exposed to a medicinal product, and not gathered inside an organized data collection system. The company's ordinary pharmacovigilance mailbox is that kind of receipt. The guideline says an organized data collection system does not include the company's standard procedures for receiving spontaneous reports. A medical-information inbox, used as routine drug safety, is spontaneous intake.

A solicited report comes from an organized system. The examples in E2D(R1) include clinical trials, non-interventional studies, patient support programs, and market research programs. For reporting, solicited cases are classified as a report from study in the ICH E2B(R3) format, and they should carry a causality assessment. The guideline says a solicited report should be submitted only when the reporter or the company considers a causal relationship at least a reasonable possibility. Spontaneous reports, for purposes of reporting, already imply a suspected causal relationship. A patient support program that enrolls people and talks with them in both directions is solicited. A one-way coupon or delivery service, with no conversation and not part of a support program, is handled as spontaneous if an event shows up. The intake record should say which situation the report came from. Guessing at the time of submission changes the report type.

Investigator reports on an IND are a third receipt. 21 CFR 312.32 is the US expedited duty for suspected adverse reactions that are both serious and unexpected. SUSAR reporting walks through the three tests and the 7-calendar-day and 15-calendar-day clocks. A patient's post-marketing email and a site SAE can look alike on a screen. They are not the same obligation. The form should record the source so the wrong clock is not the one that gets tracked.

Four facts, then a date

E2D(R1) section 2.2 says an ICSR is eligible for submission when it has at least these minimum criteria:

• One adverse event or adverse reaction, or another observation the region requires as an ICSR.
• One suspect or interacting medicinal product. An interacting product is treated as suspect.
• An identifiable patient.
• An identifiable reporter.

A case missing any of those does not qualify for ICSR reporting. The company is expected to exercise due diligence to collect the missing criterion. That is follow-up, described in E2D(R1) section 6.4. It is not a reason to delete the email.

GVP Module VI.B.2. is more specific about the patient. One qualifying descriptor is enough: initials, a medical-record number, date of birth, age, age group, gestation period, or sex. The information should be as complete as local privacy law allows. A note that "several patients" had the event is not an identifiable patient until one person can be described with one of those descriptors.

Day zero, in E2D(R1) section 5.2, is the date any personnel of the marketing authorization holder first has enough information to decide that the minimum criteria are met. Personnel includes service providers and other contractors acting for the company. Expedited reports go as soon as possible and not later than 15 calendar days after that date. Serious and unexpected cases are the expedited class in the guideline. Whether a serious expected case is expedited depends on the region. Non-serious cases are normally outside the expedited clock, though a region can still require them as ICSRs on a longer timeline. When follow-up turns a non-serious case into a serious one, day zero for that expedited follow-up is the date the new information arrived.

GVP Module VI.B.7. states the same gate and is explicit about the calendar. Day zero is the first day the authority or the company knows of a valid ICSR, including when that day is a weekend or a public holiday. The timelines are calendar days. An unread Friday email does not wait until Monday to become Friday.

FDA's marketed-drug rule is related, and the sentence is different. 21 CFR 314.80 requires the applicant to report each adverse drug experience that is both serious and unexpected, foreign or domestic, as soon as possible but no later than 15 calendar days from initial receipt of the information. "Initial receipt" is the regulation's phrase. "Day zero, once the four criteria exist" is the ICH and EU phrase. A Friday email that names the product and the rash, and does not identify the patient, has a receipt date of Friday. It may not have a day zero until a later call supplies an age and initials. The procedure should record both dates. A data-entry date, typed on Monday from a thread nobody opened, is a third date, and it is the wrong one.

Follow-up has its own clock. E2D(R1) says that when medically relevant new information arrives on a case already reported, the clock starts again for the follow-up report. An internal correction, with no new information from outside, does not get a new day zero. What late intake does is the process description of the work that waits on a valid case. It is not a mortality estimate, and this page does not add one.

What the email drops

These are the fields a three-line message from a patient or a healthcare professional most often lacks. They do not replace medical review. They are what review needs before it can start. The drug safety inbox is where the same gaps show up as a pile of threads. The list here is the reporter's side of that pile.

• Qualification and a way back. Physician, pharmacist, nurse, patient, caregiver. A role with no name, or a name with no contact, is how follow-up dies. Ask for a phone or email. If the person refuses, write that down. Do not invent a number.
• One patient. Initials, age or age group, and sex are enough to be identifiable. The stored file does not need a full legal name when privacy rules say otherwise. It does need one person.
• The product in the reporter's words. The name they used, the dose if they know it, and the dates of use. Lot or batch helps and is often unknown. A missing lot does not erase the event.
• The event verbatim. Onset, whether it is still going on, and what happened next, including whether anyone was admitted. A patient checkbox labeled "serious" is a clue. Seriousness is a criterion a qualified person applies.
• The receipt stamp. The reporter cannot supply the company's receipt date. The system has to record when the message arrived, including Saturday.
• Other products and history. Concomitant medicines and the history that would change causality can be follow-up. They should not be filled in by guesswork to make the first screen look complete.

Seriousness uses the outcomes in ICH E2A and in 21 CFR 314.80: death, a life-threatening event, inpatient hospitalization or prolongation of hospitalization, persistent or significant disability, a congenital anomaly or birth defect, or a medically important event that may require intervention to prevent one of those outcomes. Life-threatening means the patient was at immediate risk of death from the event as it occurred. Severity, how bad it felt or how a scale graded it, is a separate fact. Store both if you have them. Do not collapse them into one checkbox.

If the same message describes a defect, a cracked pen, a cloudy liquid, a wrong tablet in the bottle, read it against product quality complaint reporting as well. Quality wants the lot. Drug safety wants to know whether a person was harmed. The reporter should not have to pick a department before finishing the story.

Reports that are not automatically an adverse event

E2D(R1) section 5.1.3 treats several observations as records the company should keep and, where needed, follow up. They become ICSRs when the region requires it, or when an adverse event is also present.

• Lack of effect. "It did not work," with no untoward occurrence, is an ICSR only where the region or the product class requires that. Vaccines, contraceptives, and medicines used in life-threatening conditions are the examples the guideline gives. An event that accompanies the lack of effect is reported as an adverse event.
• Medication error, overdose, misuse, abuse, occupational exposure. With no associated event, these are ICSRs only where required. A near miss that never reached a patient can still be reportable in some regions, and the identifiable-patient criterion has a specific exception in E2D(R1) for that situation. An error that harmed someone is an adverse event plus the error.
• Pregnancy or breastfeeding exposure. Exposure of a parent, with no adverse event in the parent or the child, is an ICSR only where required. An abnormal outcome, including a congenital anomaly, fetal death, or an event in the mother or newborn, is subject to ICSR reporting. The company is not expected to record uneventful exposure for a product specifically indicated in pregnancy.

The practical habit is the same for all three. Keep the reporter's words. Ask the follow-up that would show whether an event is hiding inside the sentence. Do not drop the message because the first reading failed the four-element test.

MedWatch is FDA's form

Health professionals, patients, and consumers may report voluntarily to FDA through MedWatch. FDA's MedWatch forms page points health professionals to Form FDA 3500 and patients and consumers to Form FDA 3500B. That reporting is voluntary. The instructions for Form FDA 3500 ask for the reporter's name, address, phone, and email so serious cases can be followed up, and they say the reporter's identity may be shared with the manufacturer unless the reporter asks otherwise. Form 3500A is the mandatory industry report. A patient does not complete 3500A.

A message a patient sends to the company is a report to the company. A MedWatch form is a report to FDA. A form the company uses to receive the story is the company's intake. What is worth taking from the FDA instructions is the content: who is reporting, whether they are a health professional and what their occupation is, the product, the event in their words, and a plain statement of what will happen to the contact details. The company's own privacy notice is the place for that statement.

After the report is in one record

Someone still has to judge seriousness, expectedness, and causality. Expectedness for a marketed product is a check against current labeling. In a trial it is a check against the investigator's brochure or the company core data sheet, including the version. AE Connect does not author or version that document. AI pharmacovigilance case processing is the draft of those judgments: a suggested MedDRA preferred term and system organ class, WHO-UMC causality, expectedness as a prompt to check the reference document, and a timeline, each with a short rationale. A person accepts or overrides every field. The draft is decision support. It does not make the regulatory call.

AE Connect is customizable electronic intake for that step, with AI triage. In the workspace, a reviewer pastes the narrative or uploads a PDF, Word file, text file, email, CSV, or image. Parsing runs in the browser. Only the extracted text is assessed. The intake form is the case screen. Patients and healthcare professionals are not sent to a separate consumer website, and the screen is not MedWatch.

The reviewed case can feed Oracle Argus, ArisGlobal LifeSphere, Veeva Vault Safety, IQVIA Vigilance, or another safety database. When the company uses one of those, it remains the system of record. AE Connect integrates with any safety database. For a biotech that is not implementing Veeva Vault Safety or Oracle Argus, AE Connect can itself be the safety database and build the full ICSR and the E2B(R3) file. That is a far cheaper way to hold the case than standing up either of those platforms. AE Connect does not submit or transmit the ICSR to a regulator. Submission stays with the process the pharmacovigilance plan names. E2B(R3) ICSR submissions describes the message. PSUR, PBRER, and DSUR are a later job, and this intake does not write them.

The AE and SAE intake form is the product page for the case screen. A company email requests the 14-day sandbox. Questions go to info@qfsnow.com or to a demo.

Why many reactions never become a report is the literature on healthcare professionals who do not report at all. An intake form cannot create a report that was never started. It can stop a report that was started from dying in a mailbox, with the patient identifier in one message and the product name in another, and no one left to call.

Sources

1. International Council for Harmonisation. E2D(R1) Post-Approval Safety Data: Definitions and Standards for Management and Reporting of Individual Case Safety Reports. Step 4, adopted 15 September 2025. ICH E2D(R1) PDF.
2. International Council for Harmonisation. E2A Clinical Safety Data Management: Definitions and Standards for Expedited Reporting. ICH E2A PDF.
3. International Council for Harmonisation. E2B(R3) Individual Case Safety Report specification. ICH E2B(R3) page.
4. European Medicines Agency. Guideline on good pharmacovigilance practices (GVP) Module VI (Rev 2). Collection, management and submission of reports of suspected adverse reactions. GVP Module VI PDF.
5. Code of Federal Regulations. 21 CFR 314.80, Postmarketing reporting of adverse drug experiences. eCFR 314.80.
6. Code of Federal Regulations. 21 CFR 312.32, IND safety reporting. eCFR 312.32.
7. U.S. Food and Drug Administration. MedWatch Forms for FDA Safety Reporting and Instructions for Completing Form FDA 3500. Forms. Form 3500 instructions.