Written Description--Little Used Perhaps, But Extremely Useful to Ensure Claims are Appropriately Scoped
Blog by Under Secretary of Commerce for Intellectual Property and Director of the USPTO David Kappos
The written description requirement remains alive and well! On March 22, 2010, the Federal Circuit issued an en banc decision in Ariad Pharmaceuticals, Inc v. Eli Lilly, upholding the written description doctrine. By a substantial majority vote, the Court explained that the written description requirement is called for in the language of 35 U.S.C. § 112, first paragraph. The majority also explained that the written description requirement applies to both original and amended claims. Finally, the majority explained that the test for written description is “possession as shown in the disclosure” and embraced past ways for judging the adequacy of the disclosure, including whether the specification discloses a representative number of species, sufficient structure, and/or a sufficient correlation of function to structure. These same principles are discussed in the USPTO's own 2001 Written Description Guidelines and exemplified in the 2008 Revised Written Description Training Materials.
The Ariad decision is important for the Office because written description is a critical tool for ensuring that an applicant does not claim more than she is entitled to claim. The Office recently conducted a survey of 6,865 final rejections issued over a 4.5 year period between 2005 and 2010. A written description rejection was made in about 9.7 percent of all applications during this time period. This data shows that the written description doctrine is essential to the Office’s ability to perform its basic examination function.
Even if some would consider 9.7 percent to be little used, "little used" should not be conflated with “useless.” Far from it, the written description requirement is an essential “backstop” against overclaiming. And the written description doctrine is particularly useful in examining claims that employ functional language, or that merely set forth a desired result without any indication of what achieves that result. I call these “result-orientated” or "results obtained" claims, and strongly support our examiners using the written description requirement to prevent issuance of such vastly overbroad recitations. Unless an applicant has devised every solution to a problem, the applicant is not entitled to patent every solution.
The majority in Ariad noted that functional claims have the potential to pose especially difficult problems, particularly when functional language is employed in a genus claim: “For example, a generic claim may define the boundaries of a vast genus of chemical compounds, and yet the question may still remain whether the specification, including original claim language, demonstrates that the applicant has invented species sufficient to support a claim to a genus. The problem is especially acute with genus claims that use functional language to define the boundaries of a claimed genus.”
Thus, when confronted with functional claims, as with results obtained claims, I encourage examiners to carefully consider whether such claims -- amended or original -- are adequately supported by the specification. And the essential tool in this inquiry -- the written description requirement. Little used perhaps, but extremely useful to protect the integrity of the patent system, and the public, against the issuance of overbroad patents.
What thoughts do you have about the use of the written description requirement?
Posted at 01:03PM May 05, 2010 in patents | Comments
Posted by Anon on May 05, 2010 at 01:25 PM EDT #
Posted by Nickolaus Leggett on May 06, 2010 at 06:09 AM EDT #
Posted by danne on May 09, 2010 at 06:54 AM EDT #
Posted by MaxDrei on May 11, 2010 at 06:24 AM EDT #
Posted by Joseph Reeves on June 22, 2010 at 02:56 AM EDT #
Posted by chitools on July 30, 2010 at 12:21 AM EDT #
Posted by tungsten wedding band on July 30, 2010 at 07:14 PM EDT #
Posted by Engagement Expert on October 01, 2010 at 09:31 AM EDT #