Micro-Level Reading — Knowing the Rules, and Why They Exist

The ability to point to which clause a material violates is a necessary starting point for reviewers. But it is not always sufficient. Rules are not strings of text — they are crystallizations of past harm and legislative intent. Why does the approval system reach into dosing instructions? What prompted the Sales Information Provision Guidelines in 2018? When you know the "why," the way you read a statute changes. Deviations that stay formally within the text while gutting the regulation's purpose are exactly what a micro-level reading catches — and what a text-only reading misses.

So What / So Why — The Core of This Perspective

"Knowing the statute" and "knowing why the statute is there" are categorically different capabilities in practice. With only the former, you can miss a material that navigates around the regulation's intent while appearing compliant on the surface. With the latter, you can evaluate against the motivation behind the text — what is being protected, and what is therefore prohibited.

The circumstances under which the Sales Information Provision Activity Guidelines were issued in September 2018 are documented explicitly in the fiscal 2025 monitoring report: "It became clear that acts such as those that are hard to leave evidence (oral explanations, etc.), acts that, while not clearly false or exaggerated, are considered to encourage inappropriate use, and acts involving the provision of materials (research papers, etc.) where the company's involvement is not immediately apparent and it is difficult to determine whether they constitute advertising, were taking place, and concern was raised that these acts could affect the appropriate use of prescription drugs." The direct trigger was an advertising scandal in which a major pharmaceutical company misused clinical research data. The guidelines were written specifically to cover the "gray-zone deviations" that existing advertising regulations could not capture. The stated objective is to "ensure appropriate use and thereby promote public health."

Knowing that origin makes certain things intuitive before you even locate the relevant clause: why the preface "it is off-label, but" does not constitute a disclaimer; why an explanation that helps a physician avoid reimbursement scrutiny is a problem. The guidelines are not designed only to prohibit "bad advertising" — they are designed to reach oral explanations that leave no paper trail and impression management that falls short of an outright lie. Knowing the "why" builds the lens for evaluating materials in line with that design.

What This Perspective Contains — What / Where / Why / How

What: What to look for in a material with this lens

The question is not "does this violate a clause" but "is what this clause protects actually being protected." Is the balance between efficacy and safety maintained (Guideline Section 3, Item 2(1))? Is the data source independently verifiable (the scientific evidence requirement)? Is the information structured to genuinely support a physician's prescribing judgment? These questions are assessed against the design logic of the approval system and post-marketing safety surveillance — not against the text alone.

Where: Where to apply this lens

Deviations do not live only in conspicuous language. They hide in the order of slides, the agenda framing of an oral explanation, the selection of a session title. Framing words like "for reference," "speaking generally," or "just to note" become transparent when traced back to legislative intent. The habit of asking, when you see such framing, "is this functioning as a workaround under the regulation's purpose?" — that habit is what it means to have this lens in place.

Why: Why understanding legislative intent matters

The approval system constrains dosing instructions because dosing intervals and prescribing conditions are preconditions for safety surveillance. A patient receiving a drug outside the approved regimen falls outside the post-marketing safety net. The reason explanations like "it won't get flagged at audit" or "other physicians at other hospitals use it that way" are serious is not procedural — it is that the conditions in the package insert exist to keep patients within the safety surveillance framework, not for the convenience of clinicians. A reviewer who knows that can ask "does this explanation move the patient outside safety surveillance?" before asking "is there evidence?"

How: How to develop this reading

A direct route: for each statute, once think through what would happen in a world where that regulation did not exist. Without Article 68 of the PMD Act (prohibition on advertising unapproved drugs), prescriptions based on anticipated pre-approval indications would spread, and when unexpected adverse effects emerged post-approval, the harm would be large. Without Article 66 (prohibition on exaggerated advertising), a drug that showed no significant difference on its primary endpoint could continue to be used as "the only option." Working through that exercise turns statutes from something to memorize into something to understand.

A Point of Entry Through the Patient's Position

The chart noted a diagnosis of chronic kidney disease in addition to chronic heart failure. The attending physician did not explain it that way, but looking into it later, the numbers that formed the basis for that diagnosis came from a prior test — in the "slightly abnormal" range. The medication prescribed did work. But when the side effects worsened, the person who noticed that the dosing might not align with the guidelines was not the physician, not the pharmacist, and not the pharmaceutical company.

This is a constructed patient scenario, but it sits directly on the continuum of cases documented by the Ministry of Health, Labour and Welfare's monitoring program in fiscal 2022. When a pharmaceutical sales representative explained to a physician that "a diagnosis of chronic kidney disease makes it easier to prescribe" an SGLT2 inhibitor for a heart failure indication that was not yet approved at the time, the patient in that room did not know they were becoming a subject of off-label use. The right to ask "what does off-label mean?" and "where is the safety data?" was, in effect, taken from them.

What the rules are protecting is not only prescribing appropriateness — it is this: the patient's right not to be moved outside safety surveillance without their knowledge. Once a reviewer has imagined that position, the question "which clause does this violate?" shifts to "will patients prescribed after a physician sees this material be under appropriate safety surveillance?" That question is reliably more sensitive to the deviations that stay inside the text.

Reading Past Incidents Through This Lens

Incident 1: "Half the dose, two tablets, 14 days" — the day a prescribing-day limit was rendered void (FY2021)

Within one year of approval for a drug used to treat insomnia, prescriptions exceeding 14 days were not permitted — a design intended to collect early real-world safety data on a new drug. The restriction was, in other words, an early safety information gathering mechanism. The representative proposed to the physician: "You can effectively prescribe 28 days' worth by prescribing half the dose, two tablets, for 14 days."

A text-only reading might conclude "the prescription is for 14 days" and find no violation. But read against the intent behind "ensuring appropriate use" in the guideline and the safety information obligation under Article 68-2 of the PMD Act, the long-term prescribing restriction had its purpose dismantled. If the representative had understood what the regulation was protecting rather than its wording, this proposal would not have been made. The full detail of this deviation is in Anatomy of a Misstep, Vol. 4: Presenting Unapproved Indications and Dosing.

Incident 2: Diagnosis manipulation as the hollowing-out of the approval framework (FY2022)

A representative for an SGLT2 inhibitor told physicians that "labeling the patient with a chronic kidney disease diagnosis makes it easier to prescribe" for an off-label heart failure indication (HFpEF at the time). By selecting a diagnosis that would pass reimbursement review, off-label use was made to look like on-label use. The data cited, moreover, came from a competitor's product.

"I never said it was off-label." "I stated no false facts." Read only as text, that argument holds. But knowing what the approval system exists for makes visible what was dismantled. An approved indication represents the confirmed range of efficacy and safety for that specific condition. Patients prescribed outside that range fall outside the design of post-marketing safety surveillance. Presented as "a way to get it through reimbursement," that single explanation effectively voided that design. Evaluating against legislative intent is the only method that catches acts of this type — those that observe the form of the statute while destroying its substance.

All cases in this category are collected in Anatomy of a Misstep, Vol. 4.