Reported Reactions

Adverse event reports that FDA received

  • Search
  • Watch list

Phenprocoumon adverse event reports that FDA received

Name type
Product name as reported

What a report is

A report is not proof that the drug was the cause of the event.

FDA says:

Adverse event reports submitted to FDA do not undergo extensive validation or verification. Therefore, a causal relationship cannot be established between product and reactions listed in a report. While a suspected relationship may exist, it is not medically validated and should not be the sole source of information for clinical decision making or other assumptions about the safety or efficacy of a product. Additionally, it is important to remember that adverse event reports represent a small percentage of total usage numbers of a product. Common products may have a higher number of adverse events due to the higher total number of people using the product.

Source: openFDA, Drug Adverse Event Overview, section "Responsible use of the data". The site read the page on . The data have the reports that FDA received through .

FDA also says:

There is no certainty that the reported event (adverse event or medication error) was actually due to the product. FDA does not require that a causal relationship between a product and event be proven, and reports do not always contain enough detail to properly evaluate an event. The information in these reports has not been scientifically or otherwise verified as to a cause and effect relationship and cannot be used to estimate the incidence of these events.

Source: openFDA, Drug Adverse Event Overview. The site read the page on .

Do not rely on openFDA to make decisions regarding medical care. While we make every effort to ensure that data is accurate, you should assume all results are unvalidated.

Source: openFDA, Response of the drug event API (meta.disclaimer). The site read the page on .

Not medical advice. This site counts what was reported to FDA. Questions about a medicine or device belong with a pharmacist or clinician.

Drug reports received through . Device reports have a separate cutoff, 30 Sep 2026. Why a report count is not a rate.

Reports on file

From March 2004 to June 2026, FDA received 951 adverse event reports that name Phenprocoumon. The name is as reporters wrote it. In these reports the drug is a suspect or interacting product.

In the same period, 1,849 further reports name it only as a concomitant medicine. The counts on this page do not include these reports.

FDA received 5 reports in the 12 months to June 2026 and 13 in the 12 months before. FDA releases FAERS data every quarter, so the newest months are not complete. They grow in later releases.

Of the 1,332,454 drug reports that FDA received in the 12 months to June 2026, 5 (under 0.1%) name Phenprocoumon. Reports for patients 75 and over were 48.5% of the reports that name Phenprocoumon and 9.5% of all drug reports.

The number of people who use the product is not in the data. A count is not a rate. A count of reports is not a count of events or of patients, because one event can have more than one report.

There are many instances of duplicative reports and some reports do not contain all the necessary information.

Source: FDA, FDA Adverse Event Monitoring System (AEMS) Public Dashboard. Content current as of . The site read the page on .

Suspect product

FDA records each drug in a report as suspect, concomitant or interacting. This page counts the reports in which Phenprocoumon is suspect or interacting. FDA says:

Any number of the drugs may be marked as suspect if thought to be responsible for one or more of the reactions, but that information is not validated.

Source: openFDA, Drug Adverse Event Overview. The site read the page on .

Data version

openFDA FAERS release of 29 Oct 2026. Reports received through 30 Jun 2026.

Since the last update

FDA says:

Many factors can influence whether or not an event will be reported, such as the time a product has been marketed and publicity about an event.

Source: openFDA, Drug Adverse Event Overview. The site read the page on .

The information in these reports cannot be used to estimate the incidence (occurrence rates) of the events reported.

Source: FDA, FDA Adverse Event Monitoring System (AEMS) Public Dashboard. Content current as of . The site read the page on .

The latest update of the FDA data, recorded on , changed no count of this page.

  • In April to June 2026, FDA received 2 reports that name Phenprocoumon.
  • In January to March 2026, FDA received 1.
  • In April to June 2025, FDA received 2.

April to June 2026 is the latest closed quarter in the data. A closed quarter is a quarter for which the FDA files have most of the reports.

All updatesFeed of updates (RSS)

Reaction lookup

These are the reaction terms that the reports record, with the number of reports for each term. Type a term or a plain word to find its count.

What this list leaves out

The table lists the 202 reaction terms that 5 or more reports record. A term with fewer than 5 reports is not in the table.

The site keeps reaction terms for 908 of the 951 reports (95.5%).

The reports of the other years are not in the counts.

So a count in the table can be lower than the count of FDA.

The table shows the first 50 of 202 terms.

Reaction terms in the reports that name Phenprocoumon, most reports first
Reaction term (MedDRA) and plain meaningReportsShare of the 951 reports
Anaemialow red blood cells17818.7%
General physical health deteriorationgeneral decline in health12413%
Haematocheziablood in the stool12112.7%
Drug interactionan interaction between medicines11111.7%
Dyspnoeashortness of breath768%
Haematomaa collection of blood under the skin or in tissue727.6%
Product monitoring error707.4%
Falla fall697.3%
Product prescribing error697.3%
Overdosea dose above the recommended amount636.6%
International normalised ratio increasedblood clotting slower than intended (raised INR)616.4%
Gastrointestinal haemorrhagebleeding in the stomach or bowel576%
Haematuriablood in the urine454.7%
Hypotensionlow blood pressure454.7%
Pallor454.7%
Dizzinesslight-headedness or unsteadiness414.3%
Labelled drug-drug interaction medication error343.6%
Toxicity to various agentspoisoning or toxic effect of one or more substances343.6%
Dehydration333.5%
International normalised ratio abnormal333.5%
Nauseafeeling sick333.5%
Vomitingbeing sick333.5%
Haemoglobin decreasedlow haemoglobin313.3%
Atrial fibrillationan irregular heart rhythm303.2%
Fatiguetiredness272.8%
Acute kidney injurysudden loss of kidney function262.7%
Epistaxisnosebleed262.7%
Astheniaweakness or lack of energy252.6%
Oedema peripheralswelling of the legs, ankles or hands252.6%
Tachycardiafast heart rate252.6%
Melaenablack tarry stools242.5%
Angina pectoris232.4%
Haemoptysiscoughing up blood232.4%
Skin haemorrhage232.4%
Diarrhoealoose or frequent stools222.3%
Respiratory tract haemorrhage222.3%
Stevens-Johnson syndromea severe skin and mucous-membrane reaction222.3%
Depressed level of consciousness212.2%
Pruritusitching212.2%
Circulatory collapsecollapse of the circulation202.1%
Electrolyte imbalance202.1%
Subdural haematoma202.1%
Abdominal painstomach or belly pain192%
Balance disorderproblems with balance192%
Hyponatraemialow blood sodium192%
Off label useused for a purpose or in a way not on the label192%
Coma181.9%
Toxic epidermal necrolysisa severe skin reaction with peeling181.9%
Bradycardiaslow heart rate171.8%
Prothrombin time prolonged171.8%

Download all 202 terms of Phenprocoumon (CSV)

The counts add to more than 951 reports, because one report can record more than one term. FDA says:

No individual drug is connected to any individual reaction. When a report lists multiple drugs and multiple reactions, there is no way to conclude from the data therein that a given drug is responsible for a given reaction.

Source: openFDA, Drug Adverse Event Overview. The site read the page on .

The CSV file has the same rows and the same limits. Its last row is a note that says so.

MedDRA term

The person who codes a report selects the preferred term that agrees best with the description of the reporter. The words under a term are the plain meaning that this site gives.

Not the label

The FDA-approved label of a product lists its adverse reactions. See the official pages at the end of this page.

Outcomes by year

The table gives the outcomes that the reporters gave, in the terms of FDA.

Outcomes in the reports that name Phenprocoumon, by the year of the openFDA file that holds the report

The table continues to the right.

Year of the openFDA fileReportsSeriousDeathLife-threateningHospitalization (initial or prolonged)Disability or Permanent DamageCongenital Anomaly/Birth DefectOther Serious (Important Medical Events)Not serious
2004222212211050
20051090050051
2006661130100
2007121233110040
20081818106150030
2009111123110020
2010232308180040
2011151512110260
20122323421310110
2013161640501110
20141919241310100
2015232322219070
20161717261520110
201740404222701200
2018102102189510190
201988878107401271
20201491487913910541
2021105105689801300
202218418451715511930
20232424152200100
20242828262410160
2025880670080
2026881770060

An outcome in a report is not proof that the drug was the cause. The reporter gives the outcome, and FDA does not verify it. FDA says:

The information in these reports has not been scientifically or otherwise verified as to a cause and effect relationship and cannot be used to estimate the incidence of these events.

Source: openFDA, Drug Adverse Event Overview. The site read the page on .

The six headings with the names of FDA are the outcome terms of FDA. A report can have more than one outcome. The columns Serious and Not serious are the two values of the openFDA field serious. For the value serious, openFDA gives this description:

The adverse event resulted in death, a life threatening condition, hospitalization, disability, congenital anomaly, or other serious condition

Source: openFDA, Drug adverse event fields (YAML reference). The site read the page on .

The year is the year of the openFDA file that holds the latest version of the report. It is not always the year in which FDA first received the report. The chart of the next section uses the year of first receipt. The latest year is not complete.

Reports by year and month

Reports that name Phenprocoumon, by the year in which FDA received them
0100200200420082012201620202024

The column of 2026 has an outline, because the year is not complete. It has the reports that FDA received through June 2026 only.

Show the figures of the chart as a table
Reports that name Phenprocoumon, by the year in which FDA received them
YearReports
200421
200512
20067
200712
200819
200911
201025
201119
201228
201317
201413
201524
201625
201739
2018105
201990
2020152
2021117
2022166
202316
202424
20256
20263
Reports that name Phenprocoumon, by month, five years to June 2026
0255020222023202420252026

FDA releases FAERS data every quarter, so the newest months are not complete. They grow in later releases.

Why a count moves

A count moves for many reasons. The guide gives FDA's words about them.

Patients and reporters

Age of the patient in the reports that name Phenprocoumon
AgeReportsShareShare as a bar
Under 210.1%
2 to 1110.1%
12 to 17101.1%
18 to 44474.9%
45 to 6411211.8%
65 to 7417318.2%
75 and over46148.5%
Age not given14615.4%
Sex of the patient in the reports that name Phenprocoumon
SexReportsShareShare as a bar
Female39641.6%
Male45247.5%
Unknown or not given10310.8%
Type of reporter in the reports that name Phenprocoumon
ReporterReportsShareShare as a bar
Physician35136.9%
Pharmacist22023.1%
Other health professional28329.8%
Lawyer00%
Consumer or non-health professional747.8%
Not given232.4%

Age and sex are as the report gives them. The reporter is the primary source in the report. 1.5% of the reports give the United States as the country.

Reason for use

Reason for use (indication) that the reports of Phenprocoumon record
Indication as recorded (MedDRA)ReportsShare
Atrial fibrillation828.6%
Anticoagulant therapy576%
Thrombosis prophylaxis141.5%
Aortic valve replacement101.1%
Suicide attempt50.5%
Peripheral arterial occlusive disease30.3%

The reporter fills in the indication, and the field is often empty. Each share is of all 951 reports.

Drugs in the same reports

Other drugs that the reports of Phenprocoumon name, in any role, in order of name
DrugReports that name the two
Allopurinol160
Aspirin125
Atorvastatin140
Clopidogrel136
Metoprolol175
Pantoprazole124
Ramipril220
Simvastatin173
Torasemid110
Torsemide129

The table has the 10 drug names that these reports name most. Two names in one report says only that the report recorded the two. It says nothing about the part of a product in the event.

FDA says:

Additionally, it is important to remember that adverse event reports represent a small percentage of total usage numbers of a product. Common products may have a higher number of adverse events due to the higher total number of people using the product.

Source: openFDA, Drug Adverse Event Overview. The site read the page on .

Importantly, the AEMS data by themselves are not an indicator of the safety profile of the drug or biologic.

Source: FDA, FDA Adverse Event Monitoring System (AEMS) Public Dashboard. Content current as of . The site read the page on .

Pages near this one

These links are for navigation. No count selected them.

Official pages

The site checked these addresses on . The links open in a new tab.

Cite this page

Reported Reactions. Phenprocoumon: adverse event reports that FDA received. https://reportedreactions.com/drug/phenprocoumon/ Source: U.S. Food and Drug Administration, openFDA Drug Adverse Event (FAERS) files, release of . Reports received through .

Where the data come from

The counts come from the openFDA Drug Adverse Event (FAERS) bulk files, release of 29 Oct 2026. The files have the reports that FDA received through 30 Jun 2026. A drug name is the name on the report. The site matches it to a brand name or a generic name of the National Drug Code Directory of 2 Nov 2026. A class is the pharmacologic class (EPC) of the FDA label.

A report is in the count when it names Phenprocoumon as a suspect or interacting product. The 1,849 reports that name it only as a concomitant medicine are not in the count. The site does not publish a report narrative, a lot number, a detail of a patient or the identity of a reporter. The record of FDA is the authority. See how the site counts reports, the data sources and the corrections page.

Questions

Do these reports show that Phenprocoumon was responsible for the reactions?

No. FDA says:

For any given report, there is no certainty that a suspected drug caused the event.

Source: FDA, FDA Adverse Event Monitoring System (AEMS) Public Dashboard. Content current as of . The site read the page on .

A reaction can relate to the condition that the drug treats, to other medicines, or to something else.

Is this the list of reactions on the label of Phenprocoumon?

No. It is a count of what people reported to FDA: 951 reports from March 2004 to June 2026. The FDA-approved label of a product lists its adverse reactions. The official pages at the end of this page link to the labels.

Who sent these reports?

Physician (36.9%), other health professional (29.8%) and pharmacist (23.1%). These are the types of reporter for the reports that name this drug.

If a manufacturer receives an adverse event report, it is normally required to send the report to FDA.

Source: openFDA, Drug Adverse Event Overview. The site read the page on .

How does a person report an adverse event?

FDA runs MedWatch, a program that takes voluntary reports from health professionals, patients and consumers. The guide on how to report has the links.