Volunteering the Inconvenient — A Creed About the Duty to Tell

Twenty minutes on efficacy. Ten seconds on safety — if that. The structure isn't dishonest, but the information in the physician's hands is skewed. The excuses write themselves afterward: "They didn't ask." "We ran out of time." When a physician makes a flawed judgment because something was left unsaid, and a patient is harmed as a result, those excuses become a liability. The core of this creed is simple: volunteer the unfavorable. Not answer when asked — volunteer before being asked.

So What / So Why — Why This Creed Is Necessary

At the moment a physician decides to prescribe, the information in hand is all there is. A Risk Management Plan (RMP) may list lactic acidosis as an important potential risk — but if the term never comes up in the briefing, it never enters the physician's reasoning. The history that initial regulatory approval was withheld because the hazard ratio for renal failure events exceeded 1.0 in the Japanese subpopulation may be documented in the approval review report — but if twenty minutes pass without mentioning it, that history effectively does not exist. Information asymmetry is created not by what is said, but by what is left unsaid.

The Guidelines on Sales Information Provision Activities for Ethical Drugs require that "accurate, fact-based information on both efficacy and safety be provided," and go on to specify that "negative information must also be provided." The principle is explicit: omission is also a deviation. Conveying a product's value accurately and volunteering inconvenient data are not separable obligations — they are one.

The reason this problem recurs in the record is not a matter of individual character. The March 2022 monitoring report documented the same omission — failure to explain a domestic Phase III trial that did not reach significance — confirmed simultaneously across multiple healthcare institutions. That is not coincidence among individuals. It suggests an organizational decision that "this data is not disclosed." Leaving unfavorable information unsaid can become institutional policy without anyone ever stating it aloud.

The Creed — What I Want to Be

I want to be someone who manages evidence, not someone who persuades. I believe in the product I work with; I believe it can help patients. That is precisely why the pull to end on efficacy alone is real. Raising safety might make the physician hesitate. A patient who could have benefited may not get the prescription. That concern is genuine.

But that is where I stop. A physician is the person who prescribes — the person who weighs risk against benefit and reaches a judgment. My job is to make that judgment possible, not to steer the conclusion. If the RMP lists something as an important risk, I say the words. If there is negative data in the Japanese population, I put it on the table before I am asked. If there are contraindicated patients, I explain that with the same care I give to the indication. When leaving something unsaid allows the impression "this drug has no issues" to form in a physician's memory, I have become a participant in the outcome.

The doubt does not disappear. The calculation — "disclosing this will delay adoption" — is always running somewhere in the background. Even so, I want to keep one question for myself: when the briefing ends, can I say "I told them everything they needed to know"? I know that the moment that question breaks is when the choice to stay silent begins.

Daily Practice — Concrete Actions and Checks

A creed does nothing unless it translates into action. From preparation to close, these checks become habit.

Before the briefing

• Open the RMP and list every important potential risk and every important identified risk. Confirm whether each will be named aloud in this session.
• From the package insert's "Precautions for Use," select the one contraindication or cautionary condition most likely to be overlooked and build it into the flow.
• Review the approval history. If the review report notes "no significant difference shown in Japanese subpopulation," "conditional approval," or "approved contingent on a safety advisory," include that in the explanation.
• Check that the time set aside for safety information is comparable to the time allocated for efficacy.

Self-check during the briefing

• When the thought "this might make the physician hesitate" appears, stop. That is precisely the information to present first.
• "I could answer if asked" is not the standard. "I'm presenting it without being asked" is.
• If safety slides are positioned last, reconsider the order. Place a safety section before or in the middle of efficacy rather than after.

After the briefing — reflection

• Write down: "What does the physician who just heard this still not know?" If it is an important risk, follow up on the next visit.
• Answer honestly: "Did I tell them everything they needed to hear today?"

Where It Is Tested — Under Pressure

This creed is tested hardest when several pressures align to make silence look reasonable.

KPI pressure during launch In the months immediately after market entry, the whole organization chases adoption numbers. Weekly reports track "Hospital X — adoption: yes/no." In that structure, the incentive to proactively surface safety information that might slow adoption is structurally weak. The atmosphere that says "don't raise things that will worry the physician" settles in before anyone says it out loud. This is where numerical pressure and the duty to tell collide.

The pharmacy committee as a testing ground The pharmacy committee hearing — where adoption decisions are made — is one context where the duty to tell is tested in a different form. The March 2023 monitoring report (Reference No. 001272191) documented a case involving a cardiovascular drug. At the time of approval, questions had been raised about the drug's effect on renal failure progression in Japanese patients, and the package insert carried the advisory: "There is a possibility that the effect on suppressing renal failure progression is weaker in Japanese patients." In an online company hearing conducted for the hospital's pharmacy committee, that point was never raised. Only after a medical professional asked a direct question was data on the Japanese subpopulation shown — and it appeared not within the main slide set used in the initial explanation, but on a separate slide. The report assessed the situation as one "suspected of deliberately withholding negative information despite the hospital having secured sufficient explanation time." The fact that a question was answered exists. But volunteering information and making people extract it are different acts — and the quality of information that reaches physicians and pharmacists differs depending on which one is chosen.

The well-intentioned rationalization "If I emphasize safety, the physician may hesitate. Patients who could benefit won't get the drug." That reasoning looks like integrity. But the authority to reach that judgment belongs to the physician, not to me. What I am permitted to do is lay out the evidence; steering the conclusion is not my role. When motivated reasoning takes the shape of good intentions, the right response is to step back.

When a manager says "Lead more with efficacy" This is direct pressure — usually framed not as "cut the safety discussion" but as "push efficacy harder," with the same result: less time for safety. The response here is negotiation: "Shortening the efficacy explanation is difficult, but I can restructure the whole session to preserve time for safety." The duty to tell is a compliance requirement, not a negotiable preference — and that should be said plainly.

For a closer analysis of how this creed functions and how it erodes under pressure, see Under Pressure, Vol. 5: "The Choice Not to Speak — The Sin of Omission", which examines four psychological drivers that make silence look rational and describes how they operate.

An Anchor — Something to Return to When It Gets Hard

When "the duty to tell" starts going soft inside, there are fixed principles to return to.

The Guidelines on Sales Information Provision Activities require that "accurate information grounded in scientific evidence be provided for both efficacy and safety." They then specify that "negative information must also be provided." The phrase "also" is the load-bearing word. It is not "once efficacy is covered, move to safety" — the obligation to provide safety information exists independently, as its own requirement.

The guidelines further state that "companies must not provide information that lacks scientific and objective grounds." A skewed impression created by omission is functionally identical to information that lacks scientific and objective grounds. Selective omission produces the same outcome as a false claim.

The documented record deserves a second look. The March 2025 survey project report (Reference No. 001520054) recorded a case involving a cardiovascular drug: initial regulatory approval had been withheld because the hazard ratio for renal failure events in the Japanese subpopulation exceeded 1.0 for the study drug group, and the drug was eventually approved on the condition that a safety advisory be added to the package insert. In a twenty-minute product briefing, none of that history was mentioned. The report's assessment: "Explaining only the usefulness of a drug while not explaining risk information related to safety constitutes biased information provision." What was said and what was left unsaid over twenty minutes — that record exists.

The same report goes further: "There are cases where it is suspected that intentionally inappropriate information provision is being carried out on the calculation that an apology will suffice when the matter is pointed out. In such cases, the information provision is extremely malicious, and this program is monitoring it closely." When the choice to stay silent is made on the premise that an apology can handle the fallout, it is no longer a matter of individual conscience — it has become an organizational design. To avoid reaching that point, the question must be asked today, in the preparation stage, before the briefing begins.

For documented cases where efficacy and safety were treated equally — and cases where they were not, along with their consequences — see Learning from Past Incidents, Vol. 6: "Emphasizing Efficacy Only — Downplaying Safety Information." Seven consecutive years of recorded deviations, from the March 2019 report through the March 2025 report, make clear exactly where "I just didn't mention it" leads.