Specification Requirements

The written description requirement ensures the applicant possessed the claimed invention at the time of filing: LEGAL STANDARD: the specification must describe the invention in sufficient detail to show that the inventor had possession of the claimed subject matter as of the filing date; the test is objective: would a person of ordinary skill in the art (POSITA) recognize that the inventor possessed the claimed subject matter?; SEPARATE FROM ENABLEMENT: the written description requirement is separate from the enablement requirement; Ariad Pharmaceuticals v. Eli Lilly (Fed. Cir. 2010 en banc): confirmed that § 112 first paragraph contains a separate written description requirement independent of enablement; this was a significant clarification after years of debate; WHEN WRITTEN DESCRIPTION ISSUES ARISE: continuation/divisional applications with new or broader claims added after the original filing; claims directed to genera when only specific species are disclosed; functional claims that cover more than what is specifically disclosed; priority claims: if a later-filed application claims priority to an earlier application, the earlier specification must support the claims under written description; POSSESSION TEST: a written description may take the form of: actual reduction to practice (physical prototype described); constructive reduction to practice (detailed description sufficient to enable); structural definition (for chemical or biological claims); correlation of structure to function; GENUS CLAIMS: for claims covering a genus (class of compounds, class of devices), the specification must show representatives sufficient to convey possession of the genus; random selection of species without showing representative variety = inadequate; ANTIBODY CLAIMS: Centocor Ortho Biotech v. Abbott Laboratories (Fed. Cir. 2011): functional descriptions of antibodies by their target antigen alone are insufficient; structural features of the antibody itself must be disclosed.

Enablement requires that a POSITA could make and use the full scope of the claimed invention: LEGAL STANDARD: 35 U.S.C. § 112(a): the specification must enable 'any person skilled in the art' to make and use the invention 'without undue experimentation'; the specification need not describe every possible implementation — it must provide sufficient guidance to enable the claimed scope; WANDS FACTORS (In re Wands, Fed. Cir. 1988): eight factors courts use to assess 'undue experimentation': (1) quantity of experimentation necessary; (2) amount of direction or guidance presented; (3) presence or absence of working examples; (4) nature of the invention; (5) state of the prior art; (6) relative skill of those in the art; (7) predictability of the art; (8) breadth of the claims; no single factor is dispositive — weighed together; AMGEN v. SANOFI (S.Ct. 2023): landmark Supreme Court decision strengthening enablement for broad functional claims; case involved antibody claims defined functionally by their ability to bind to PCSK9 (a cholesterol-related protein) and block it; the claims covered millions of possible antibodies; Amgen had disclosed only 26 working examples; the Supreme Court unanimously held the claims invalid for lack of enablement; RULE FROM AMGEN: claims must enable a POSITA to make and use the full scope of the claimed invention without undue experimentation; broad functional claims that cover a genus of products (such as antibodies) must enable the full scope; 'hunting for workable candidates' across the claimed scope = undue experimentation; IMPACT ON PHARMA/BIOTECH: Amgen dramatically increased the specification requirements for broad genus claims in pharma and biotech; applicants must now include many more working examples; functional claims defined only by desired function (not structure) are particularly vulnerable; PREDICTABLE ARTS: in mechanical or electrical arts where the relationship between structure and function is predictable, a single working example may enable a broad claim; in unpredictable arts (chemistry, biology), more examples are needed.

The best mode requirement historically required inventors to disclose their preferred way of practicing the invention: PRE-AIA BEST MODE: 35 U.S.C. § 112(a) required the inventor to set forth the 'best mode contemplated by the inventor of carrying out the invention'; failure to disclose the best mode was grounds for patent INVALIDITY; the test was subjective: did the inventor (at the time of filing) have a preferred mode of practicing the invention? if yes, was it disclosed?; WHAT BEST MODE COVERS: best mode must disclose what the inventor believed was the best way to practice the invention at the filing date; if an inventor had a preferred material, process step, or configuration, it must be disclosed; the inventor's subjective belief is examined at the time of filing; AIA CHANGE (effective March 16, 2013): the AIA amended 35 U.S.C. § 282(b)(3): failure to disclose best mode is no longer grounds for invalidity in a civil action; BUT: the best mode disclosure requirement still exists in § 112(a); applicants must still disclose the best mode; the consequence of not disclosing the best mode changed from invalidity to: not a ground for cancellation or invalidity in litigation; can still be basis for rejection during prosecution; PRACTICAL EFFECT: the AIA change significantly reduced the practical importance of best mode in US patent litigation; before AIA: defendants routinely searched for best mode evidence (laboratory notebooks, emails) to invalidate patents; after AIA: the same investigation is less productive since invalidity on this ground is blocked; INTERNATIONAL CONTRAST: EPO and many other jurisdictions do not have a best mode requirement; PCT applications do not require best mode disclosure; best mode is primarily a US-specific requirement; TRADE SECRET INTERACTION: inventors sometimes withheld trade secret information that was part of the best mode; post-AIA, the concern about invalidity is reduced, but full disclosure is still the better practice.

The new matter prohibition prevents adding technical disclosure to an application after filing: LEGAL BASIS: 35 U.S.C. § 132: 'No amendment shall introduce new matter into the disclosure of the invention'; WHAT IS NEW MATTER: any technical disclosure that was not expressly or inherently described in the original application as filed; not just new claims — new matter in the specification itself is also prohibited; INHERENT DISCLOSURE: a compound or element is inherently disclosed if a POSITA would necessarily understand it to be present based on the original disclosure, even if not explicitly stated; CONSEQUENCES OF NEW MATTER: the new matter is rejected or required to be cancelled; claims supported only by the new matter receive the later filing date (the amendment date) not the original filing date; loss of priority to the original application for claims relying on the new matter; CONTINUATION APPLICATIONS AND NEW MATTER: continuation applications claim priority to the parent application; any claims in the continuation that are not supported by the parent specification receive only the continuation's filing date; if a continuation adds new matter to the specification (which becomes a continuation-in-part or CIP), the new subject matter has the CIP filing date; PRACTICAL IMPORTANCE: filing date determines priority against prior art; adding new matter inadvertently can create prior art problems for the new claims; COMMON NEW MATTER ISSUES: adding specific dimensions, materials, or percentages not in the original filing; adding working examples prepared after the filing date; adding claims to later-discovered applications of the invention; changing the description of an element from 'optional' to 'required' or vice versa; PROSECUTION STRATEGY: to avoid new matter issues: file the original application with a complete disclosure; if new technical developments occur, file a continuation-in-part with new matter or a new non-provisional application.

Section 112 rejections and defenses are common in both examination and validity disputes: DURING PROSECUTION — USPTO REJECTIONS: § 112(a) rejection for insufficient written description: examiner asserts claims broader than the specification supports; response: point to specific disclosures in the specification supporting the claims; consider claim narrowing; add dependent claims that define supported scope; § 112(a) rejection for lack of enablement: examiner asserts POSITA cannot make/use the full scope without undue experimentation; response: provide technical arguments addressing Wands factors; submit declarations (Rule 132 affidavits) from experts; provide experimental data demonstrating enablement; § 112(b) rejection for indefiniteness: claim language is not reasonably certain in scope; response: amend claims to clarify; argue that the claim language has an established meaning in the art; § 112(f) — MEANS-PLUS-FUNCTION CLAIMS: 'means for' language invokes § 112(f)/formerly § 112(6); claim is limited to corresponding structure disclosed in the specification plus equivalents; if no corresponding structure disclosed, claim is indefinite (Noah Systems, Fed. Cir. 2012); DURING LITIGATION — INVALIDITY DEFENSE: § 112 issues are a common invalidity defense; clear and convincing evidence standard (Microsoft v. i4i, S.Ct. 2011) applies in district court; in IPR/PGR proceedings: preponderance of the evidence; claim construction affects § 112 analysis: broadly construed claims are more vulnerable to written description and enablement attacks; INDEFINITENESS — NAUTILUS (S.Ct. 2014): claims are invalid if they fail to inform with 'reasonable certainty' a POSITA of the scope of the invention; Nautilus, Inc. v. Biosig Instruments: revised the prior 'insolubly ambiguous' standard to 'reasonable certainty'; STRATEGIES FOR APPLICANTS: draft specifications with multiple examples across the claimed scope; include detailed examples, representative data, and prophetic examples; avoid over-broad functional claiming; use dependent claims to provide narrower fall-back positions.