Someone Is on the Other Side of My Reviewing Eye — Perspective-Taking as a Way of Using Knowledge

You have read the rules. You have memorized the guidelines. But if the sense that the material in front of you feeds directly into someone's prescribing decision — and behind that decision, a patient's body — never quite lands, review stays at the level of formal verification. Perspective-taking is not a feeling of sympathy. It is a cognitive habit of asking, "Who receives this material?" It builds a bridge between knowledge and judgment, grounding abstract rules in someone's concrete situation.

So What / So Why — The Core of This Lens

So what (what changes)  Perspective-taking converts the text of a rule into something a person experiences. In promotional material review, that means replacing the question “Does this safety information comply with the guideline?” with: “A physician reads this material and makes a prescribing decision. A patient then takes that drug. Is the information in the physician’s hands at that moment sufficient?” Compliance with rules and what actually reaches the reader are not the same thing. The gap matters most in gray zones — where formal requirements are technically met but whether an abbreviated disclosure actually functions is impossible to judge by text-matching alone.

So why (why review needs it)  When review stops at formal checking, the reviewer has not traced the downstream impact of the material they approved. Safety information placed in a single line at the bottom gets logged as “present.” Whether a physician actually reads that line, whether it enters the prescribing decision at all — those questions go unasked. The absence of perspective-taking is not a precision problem. It changes what review is for. The MHLW guidelines on promotional activity for prescription drugs require that “negative information also be provided” because those on the receiving end need protection for their judgment. If the reviewer has never once stood in that recipient’s position, the rule stays abstract, a line to check off rather than a purpose to serve.

This is why perspective-taking pairs with the rule-based lens. The rule-based eye asks what must be written. The perspective-taking eye asks what actually gets through. Only when both are active does review function in substance, not just form.

Inside the Lens — What / Where / Why / How

What (what this lens looks at)  It internalizes the subjective situation of the material’s recipients — patients, family members, prescribing physicians, pharmacists. The exercise is to imagine being in a position where this information is all you have, then read the material from there. Concretely: does the volume, order, and emphasis of safety information function in the recipient’s actual cognitive context?

Where (when to apply it)  When judging whether safety information is adequately disclosed. When checking the information balance between patient-facing and healthcare-provider-facing materials. The lens is most useful in the gray zone — where formal requirements are met but substantive function is in doubt. A material where RMP key risks appear only as a single closing sentence; a slide deck that substitutes “please refer to the package insert” for naming any adverse event — those are the judgment calls where this lens earns its place.

Why (why this lens is necessary)  Rules define what must be written; they do not define how much writing is enough for the information to land. Answering that requires imagination about the recipient’s situation. The gap between a formally present disclosure and information that actually functions is invisible without standing in the recipient’s position. “If I were this physician, could I make a prescribing decision on this information alone?” — that question turns text-matching into meaning-checking.

How (the concrete practice)  After a first read, ask again: “Has the patient prescribed this drug been given enough information to choose to take it knowing the risks?” “Could the physician who attended this session learn that this product’s negative data exists?” Carrying these questions into a second read is how perspective-taking enters the review process as a step, not just a disposition. No emotional disturbance is required. Temporarily borrowing a position — a cognitive operation — is enough.

Entering the Perspective — Standing in That Position

What follows reconstructs the situation from multiple parties’ standpoints, based on documented deviation cases. Read it not as assertion but as an illustration of how to borrow a viewpoint — “from this position, here is what you see.”

The patient’s position

Your hay fever worsened that spring, and your doctor prescribed a new antiallergic drug. “It works well,” the doctor said. You have no way of knowing whether you have any contraindications. You also have no way of knowing that in the 20-minute web seminar the prescribing physician attended, information on the drug’s contraindications and precautions for careful use was handled by displaying the package insert on screen for about 10 seconds at the final slide. If the physician later realizes that the contraindication check was insufficient, that process never reaches you. You take the drug as “the one the doctor chose.”

The question to hold: if you were this patient, would you accept a review record that reads “safety information: present”?

The family member’s position

Your father was prescribed a new cardiovascular drug. The physician told him: “International trial data confirm reduced risk of cardiovascular events.” You were relieved. But your father is Japanese. The possibility that the drug’s effect on slowing progression to renal failure may be weaker in Japanese patients, and the fact that initial regulatory approval was withheld, were never mentioned — because the company representative did not raise those points in the online hearing for the hospital formulary committee. The physician might say, “I didn’t know that data existed.” You still don’t know what was missing from that decision.

The question to hold: if you were this family member, would you accept the explanation that “information was disclosed (and questions would have been answered)”?

The prescribing physician’s position

You scheduled an online hearing for the formulary committee. You set aside the time. The company representative explained efficacy data. International trials showed statistically significant risk reduction — that was the message. After the hearing ended, you opened the electronic package insert yourself and found: “In Japanese patients, the effect on slowing progression to renal failure may be weaker.” If the representative’s logic is that it was not mentioned because no one asked, what basis do you have to report to the formulary committee? What do you use to anchor the next prescribing decision?

Standing in the position of this physician — making a decision while uninformed — the omission of safety information is visible not as a technical violation but as an act that corrupts someone’s judgment. That is how the perspective-taking eye works.

Reading Past Deviations Through This Lens

The deviations recorded by the monitoring program, re-read through perspective-taking — not as descriptions of rule violations but as answers to the question “whose judgment was distorted?”

Case 1 — Safety information reduced to the “last 10 seconds” of a 20-minute web seminar (2020 published report)

Case 2 — Japanese patient data left unspoken in a formulary committee hearing (2023 published report)

What both cases share is that the deviation functioned as information that never reached anyone. The rule-based eye ends at “safety information was not provided.” The perspective-taking eye sees a chain: “that physician made a prescribing decision without knowing,” “that patient had no opportunity to learn the risk.” A reviewer who can imagine that chain asks of any formally present disclosure: is this enough?