US Patent 8,315,886: What Is Claimed and How Broad Is the Enforcement Scope?

US Patent 8,315,886 claims a computer-controlled prescribing and dispensing workflow for a teratogenic drug where male patients are treated under a risk-mitigation program that requires pharmacy fill gating by an approval code generated only after patient-verified education and acknowledgements are captured in a computer-readable medium.

At the core, the patent is not claiming a teratogenic drug compound. It is claiming a process: registration, eligibility checks tied to patient comprehension, delivery of warnings (including contraception failure risk and barrier contraception), collection of acknowledgements, and then a code-based gate that a pharmacy must query or retrieve before dispensing.

What Does Claim 1 Cover (Core Independent Claim Scope)?

Claim 1 is a “method of treating” plus a controlled dispensing gate

Claim 1 requires all of the following elements working together:

Treating a male patient with a disease or condition responsive to a teratogenic drug.
The system permits prescriptions to be filled only after the pharmacy retrieves an approval code.
Approval code generation is defined by steps (a) through (g) and includes (h) administering the drug.

Step-by-step mechanics embedded in Claim 1

The claim is highly specific about what must happen before an approval code exists:

(a) Register prescriber and pharmacy with a distributor via a computer readable storage medium.
(b) Determine whether the patient can understand and carry out instructions.
(c) If the patient can do so, provide verbal and written warnings about:
- the hazard of taking the drug and exposing a fetus (even though patient is male, the claim uses “fetus” risk framing).
(d) Provide verbal and written warnings about:
- risk of possible contraception failure
- need to use barrier contraception when having sexual intercourse with women of child bearing potential.
(e) Obtain acknowledgement of the warnings from the patient.
(f) Register the patient with the distributor.
(g) Generate a prescription approval code via a computer readable storage medium only after the acknowledgements and registrations exist.
(h) Pharmacy must retrieve the approval code before the prescription is filled, and then the drug is administered to the patient.

Claim 1’s functional dependency

Claim 1 is structured so that:

No approval code can be generated absent the required educational content and patient acknowledgement.
No fill is authorized unless the pharmacy has retrieved that code.

That creates a strong “systems integration” posture: it is not enough to educate; the code retrieval gate is required. It is also not enough to code-gate; the content and patient acknowledgement steps are required.

How Narrow or Broad Is Claim 1 in Practice?

Breadth is in the process architecture, not in the drug identity

The claim uses “a teratogenic drug” broadly, without naming a specific active ingredient in the text you provided. That gives scope to any teratogenic drug implemented with a similar male-patient contraception-risk workflow.

Breadth is limited by required procedural content

Even if a competitor uses an approval code, it must also satisfy:

male patient treated with a disease responsive to the teratogenic drug;
verbal and written warnings (both formats are required);
specific warnings on:
- contraception failure risk
- barrier contraception requirement tied to sexual intercourse with women of childbearing potential;
patient acknowledgement of those warnings;
computer-readable medium steps for registration and code generation;
pharmacy retrieval of the approval code prior to dispensing.

The claim is not a generic REMS concept

Although the subject matter resembles REMS-like mitigation programs, Claim 1 is constrained to a code-based pharmacy fill gating tied to a particular sequence of steps in a computer-readable medium, with both warning content and patient acknowledgement as required prerequisites.

What Additional Coverage Exists in Dependent Claims?

Claim 2: Expands what counts as “acknowledgement”

Claim 2 narrows and clarifies the content of patient acknowledgement. It provides that acknowledgement requires understanding of one or more specified items. The list includes at least these categories:

must not take drug if unprotected sex cannot be avoided
understanding of potential birth defects
advised need for barrier contraception by prescriber
obligation to inform prescriber if partner is suspected of becoming or being pregnant
drug is for patient use only and must not be shared
patient has read brochure or viewed information film
semen or blood must not be donated during treatment
patient inquiries answered by prescribing physician
participation in survey and patient registry is required

Practical enforcement effect: A system that uses a generic consent form may not meet Claim 2 if it does not capture the specific comprehension and commitments enumerated here.

Claim 3: Adds side-effect warning content

Claim 3 adds a further step before code generation:

provide warnings of non-teratogenic side effects.

This is a content requirement beyond the fetal hazard and contraception failure/barrier contraception warnings in Claim 1.

Enforcement effect: Even if warnings exist, missing “non-teratogenic side effects” messaging can avoid full capture of Claim 3.

Claim 4: Adds prescriber written authorization

Claim 4 requires:

written authorization by the prescriber prior to generation of the approval code.

Enforcement effect: In a competitor workflow where the code is generated automatically upon registration and acknowledgement without a distinct prescriber authorization step, Claim 4 coverage may not be met.

Claim 5: Approval code retrieval from a computer readable storage medium

Claim 5 limits or clarifies:

the prescription approval code is retrieved from a computer-readable medium.

This aligns with Claim 1 but further reinforces the technological requirement.

Claim 6 and Claim 7: Informed consent form mechanics

Claim 6: acknowledgement is a written informed consent.
Claim 7: written informed consent is registered in the medium prior to code generation.

Enforcement effect: Systems that collect acknowledgement electronically but do not establish it as written informed consent registered prior to code generation risk non-infringement of Claims 6-7.

Claim Chart Style Mapping: What Would Infringe?

Below is a compliance-to-claim checklist mapping key elements to the dependent layers. A system must satisfy the independent claim for baseline infringement; to capture dependent claims, it must also include the added features.

System element	Claim 1 requirement	Claim 2 add-on	Claim 3 add-on	Claim 4 add-on	Claim 6-7 add-on
Pharmacy fill gated by approval code	Yes: retrieval before fill	Not relevant	Not relevant	Not relevant	Not relevant
Prescriber and pharmacy registration with distributor	Yes (via computer-readable medium)	Not relevant	Not relevant	Not relevant	Not relevant
Patient comprehension check	Yes	Not relevant	Not relevant	Not relevant	Not relevant
Verbal and written hazard warnings	Yes (hazard of taking drug and exposing fetus)	Not relevant	Not relevant	Not relevant	Not relevant
Contraception failure + barrier contraception warnings	Yes	Not relevant	Not relevant	Not relevant	Not relevant
Patient acknowledgement captured	Yes	Yes (must include one or more enumerated items)	Not relevant	Not relevant	Acknowledgement must be written informed consent
Patient registration with distributor	Yes	Not relevant	Not relevant	Not relevant	Not relevant
Approval code generated after acknowledgement	Yes	Not relevant	Not relevant	Not relevant	Consent must be registered before code generation
Prescriber written authorization step	Not required by Claim 1 (but required by Claim 4)	Not relevant	Not relevant	Yes	Not relevant
Side-effect warnings (non-teratogenic)	Not required by Claim 1	Not relevant	Yes	Not relevant	Not relevant
Written informed consent as acknowledgement	Not required by Claim 1	Not relevant	Not relevant	Not relevant	Yes (Claims 6-7)

What Parts of the Claim Are Most Likely to Create Non-Infringement Levers?

1) Removing or changing the pharmacy approval code gate

If dispensing does not require retrieval of a distributor-generated prescription approval code, the architecture in Claim 1 breaks.

2) Replacing verbal plus written warnings with alternate formats

Claim 1 explicitly requires verbal and written warnings. A system using only electronic-only or only written may avoid capturing Claim 1.

3) Changing the content of contraception-risk warnings

Claim 1 requires warnings about:

risk of possible contraception failure
need for barrier contraception with intercourse with women of childbearing potential.

A workflow that uses different wording but does not convey these specific concepts may still be argued as not meeting the required warning content.

4) Changing the acknowledgement type and timing

Claims 6-7 create a strong procedural requirement:

acknowledgement is written informed consent
written informed consent is registered in the medium prior to code generation

Systems that use oral consent, non-written acknowledgements, or written forms that are not registered prior to code issuance may avoid Claims 6-7.

5) Missing “non-teratogenic side effects” warning step

Claim 3 is an add-on. If the program limits warnings to teratogenic and contraception risk only, it can avoid Claim 3 while still potentially satisfying Claim 1.

Patent Landscape: What This Claim Structure Signals About Enforcement Strategy

Likely enforcement targets

Because Claim 1 is process-based and tied to:

distributor registration
computer-readable medium workflows
code retrieval gating at pharmacies
standardized warning and acknowledgement steps

The enforcement posture typically targets:

REMS administrators and distribution-side IT systems
pharmacy dispensing workflow integrations
program vendors that implement the code gate and acknowledgement capture

Claim architecture suggests “system implementation” infringement theories

Process claims like this are designed to fit:

a regulated REMS-like program environment
centralized distributor control of a code and pharmacy access
audit trails in computer-readable systems

That tends to shift potential infringement focus away from prescriber training programs alone and toward the technical control plane that issues and retrieves codes.

Male-patient framing affects design-around

This patent is written for male patients in the method of treating. A program built exclusively around female-patient pregnancy prevention steps may not map onto the “male patient” limitations in Claim 1.

Still, a competitor that extends a male-patient mitigation program to mirror the same code gate and warning content risks overlapping the claim.

Scope Summary: What the Patent Covers Versus What It Does Not

Covers

A teratogenic drug treatment workflow for male patients where:
- pharmacies cannot fill without retrieving a code
- the code exists only after distributor registrations, patient comprehension determination, verbal and written hazard plus contraception-risk warnings
- patient acknowledgement is captured and patient is registered
- code is generated via computer-readable medium
Expanded dependent coverage for:
- specific acknowledgement items (including brochure/film, no sharing, no semen donation, registry/survey)
- non-teratogenic side-effect warnings
- prescriber written authorization before code generation
- written informed consent registered prior to code issuance

Does not cover (based on claim limitations)

A model with no approval code gate for pharmacies
A model where warnings and acknowledgement do not match the required content and format (verbal and written) in Claim 1
A model where “written informed consent registered prior to code generation” is not used for Claims 6-7
A model that omits the computer-readable medium mechanics for registration and code generation (Claim 1’s structure relies on it)

Key Takeaways

US 8,315,886 claims a specific controlled dispensing workflow for male patients using teratogenic drugs, where pharmacies must retrieve an approval code before filling.
Claim 1’s breadth is process-level, not drug-level: it covers any teratogenic drug implemented with the required registration, patient comprehension check, verbal and written warnings, contraception failure and barrier contraception messaging, patient acknowledgement, and code generation in a computer-readable medium.
Dependent claims materially tighten requirements: enumerated acknowledgement content (Claim 2), non-teratogenic side-effect warnings (Claim 3), prescriber written authorization (Claim 4), and written informed consent registration before code generation (Claims 6-7).
The most direct design-around levers are: removing the code gate, changing required warning format/content, or altering the consent type/timing and computer-readable medium registration mechanics.

FAQs

1) Is US 8,315,886 a drug-compound patent?
No. The claims are directed to a method of treating using a teratogenic drug with a gated prescribing/dispensing process that includes approval code generation and retrieval.

2) What specifically must be included in the patient warnings under Claim 1?
The claim requires verbal and written warnings covering hazard and fetus risk framing, plus warnings about contraception failure and the need for barrier contraception when having intercourse with women of childbearing potential.

3) Does the patent require pharmacy participation?
Yes. The pharmacy must retrieve the prescription approval code before filling, and the pharmacy is also involved in registration with the distributor via a computer-readable medium.

4) How does Claim 2 change the consent requirements?
Claim 2 specifies what the patient acknowledgement must include, listing items such as understanding of birth defects, barrier contraception advice, no sharing, brochure/film review, semen donation prohibition, and registry participation.

5) Which dependent claims add extra procedural steps beyond Claim 1?
Claim 3 adds non-teratogenic side-effect warnings, Claim 4 adds prescriber written authorization, and Claims 6-7 require written informed consent registered before code generation.

References

[1] United States Patent and Trademark Office. US Patent No. 8,315,886. (Claims as provided in the prompt).

Country	Patent Number	Estimated Expiration	Supplementary Protection Certificate	SPC Country	SPC Expiration
Australia	1437201	⤷ Start Trial
Australia	2005201675	⤷ Start Trial
Australia	780486	⤷ Start Trial
Brazil	0016903	⤷ Start Trial
Canada	2352629	⤷ Start Trial
>Country	>Patent Number	>Estimated Expiration	>Supplementary Protection Certificate	>SPC Country	>SPC Expiration

Details for Patent: 8,315,886

Summary for Patent: 8,315,886