Section 1 of Chapter 4 of the Guidelines on Sales Information Activities for Prescription Drugs is brief — two sentences. Yet those two sentences distill the entire philosophy of the Guidelines, and they are the direct source of the theme this site returns to throughout: the absence of an explicit prohibition is not permission.

Chapter 4, Section 1 (text): "Regarding matters not stipulated in these Guidelines, companies shall not hold the mistaken belief that the absence of a prohibition equals freedom to act. Instead, companies shall use as the axis of judgment the fundamental question of what duties are properly expected of pharmaceutical companies, and shall conduct activities only after holding themselves to strict self-discipline."

01The "Not Prohibited, Therefore Permitted" Fallacy

Laws and regulations often draw boundaries by listing what is prohibited. Readers therefore become accustomed to the interpretation: "not on the prohibited list = allowed." In civil or criminal law contexts, this reasoning has some validity. In the context of pharmaceutical sales information activities, it is a critical error.

The Guidelines are not a list of prohibitions. They articulate what proper information provision looks like for a pharmaceutical company. When a situation arises that the Guidelines do not explicitly address, the right question is not "Is this prohibited?" but "Is this consistent with the duty that is properly expected of us?"

So what (what it means): The Guidelines are a declaration of expected conduct, not an exhaustive list of things to avoid. Silence in the text is not permission — it is a space where companies must apply their own judgment, anchored to the original duty.

So why (why it is written this way): No regulation can enumerate every possible activity in advance. If "not written = permitted" were accepted, companies would routinely find ingenious ways to act within the technical gaps while violating the regulation's purpose. The spirit of the rule must itself serve as the rule.

02What Is the "Fundamental Duty"?

When the Guidelines refer to the "fundamental duty expected of pharmaceutical companies," Chapter 1 provides the answer. Companies provide information to healthcare professionals in order to support appropriate use of medicines and protect patient health. Any activity that drifts from this purpose — even if no individual provision explicitly bars it — is inconsistent with the fundamental duty.

Consider a concrete scenario: a medical representative proactively brings data suggesting effects beyond the approved indication, framing it as "available if you have questions." Whether or not this triggers any single provision of the Guidelines, it cannot survive the test of "having held oneself to strict self-discipline." The intention is promotional; the framing is designed to appear responsive to an inquiry that has not yet been made.

So what (what it means): The axis of judgment is not "which provision applies" but "does this serve appropriate drug use and patient safety?" Checking the text is a necessary condition; it is not sufficient on its own.

So why (why it is written this way): If compliance is reduced to "clearing the text," activities that are technically lawful but substantively inappropriate become normal. In healthcare, activities of that kind can cause patient harm. The Guidelines require more than textual compliance.

03Building "Strict Self-Discipline" into Practice

The requirement sounds abstract, but it can be translated into concrete judgment steps. When planning a new communication activity or information delivery format, the following sequence of questions provides a practical framework.

So what (what it means): "Self-discipline" cannot rest on individual virtue alone. It must be embedded in organizational processes. A compliance system that relies on each person's goodwill is structurally fragile.

So why (why it is written this way): Well-intentioned individuals making reasonable-seeming judgment calls can, in aggregate, accumulate into an inappropriate organizational practice. Without institutional mechanisms, this requirement remains aspirational rather than operational.

04Why This Site Returns to "Not Written Does Not Mean Permitted"

The recurrent theme of this site — "the absence of an explicit prohibition is not permission" — has its textual origin in Chapter 4, Section 1. But the concern runs deeper than one provision. It reflects a structural feature of the pharmaceutical industry.

Information about drug efficacy and safety is inherently asymmetric. Companies hold large bodies of data; healthcare professionals see a portion of it; patients see less still. If companies exercise the "freedom to act in unwritten spaces" within that information gap, the quality of information provision degrades reliably.

The posture the Guidelines require is one of filling the regulatory "white space" voluntarily — acting as if the spirit of the rule applied even where the text does not reach. Trust in the pharmaceutical industry is not earned by meeting the minimum floor of legal compliance; it is earned by what a company does above that floor.

So what (what it means): Chapter 4, Section 1 does not define a floor of compliance. It mandates a posture of reflection. The difference between a company that follows the text and a company that embodies its spirit is captured in this provision.

So why (why it is written this way): Law represents the minimum agreement society has reached, not the ceiling of ethical conduct. For pharmaceutical companies to earn and maintain social trust, the relevant question is how far above that floor they choose to operate. This provision makes the obligation to keep asking that question explicit.