PTAB
Advanced fields
1 decision · 480msnewest first
  • PTAB · Nov 18, 2015 · CBM2014-00143 · APJ Richard E Rice · CBM · Final written decision

    Claims 1–20 are unpatentable under § 101 as directed to ineligible subject matter; obviousness was not shown for claims 1–3, 5, 8, 11–13, 15, 17, 18, and 20.

    RulingsFinal written decision
    • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownOther

      “Neither party proposes any change to the interpretations set forth above, and our review of the evidence does not indicate that any change is necessary. Consequently, we maintain our interpretations. Patent Owner proposes constructions for two additional claim terms— “rule” and “database.” PO Resp. 10. With respect to “rule,” Patent Owner proposes the definition set forth expressly in the Specification, i.e., “a rule is coded logic that evaluates data and then performs an action.” Id. (citing Ex. 1001, 5:59–60). Petitioner does not dispute Patent Owner’s proposed construction of “rule,” and we agree that it is the broadest reasonable interpretation consistent with the Specification. For the claim term “database,” Patent Owner relies on Mr. Goodin’s statement, based on a dictionary definition, that a “database” is a “collection of data with a given structure for accepting, storing, and providing, on demand, data for multiple users.” Id. (citing Ex. 2012 ¶ 44); see Ex. 2015, 21. We note Mr. Goodin’s additional testimony that a POSA “would understand a ‘database’ is a stored collection of data” (Ex. 2012 ¶ 45), and that the Specification “contrasts a database, consisting of stored data, which can be updated on demand, with a set of rules that are hard coded into a software application” (id. ¶ 46, citing Ex. 1001, 6:27–28). Petitioner does not propose a construction for “database” or challenge Mr. Goodin’s testimony, discussed above. Based on the above, we determine that the broadest reasonable interpretation consistent with the Specification of “database” is a stored collection of data that can be updated on demand.” slip op. at 9

    • Skill levelSkill level board ownDecided for petitioner

      “Petitioner’s Declarant, Dr. Bergeron, provides the following definition of a person of ordinary skill in the art (“POSA”): [A] POSA in the 2000 time frame would have had a Bachelor’s degree in computer science or the equivalent, or commensurate industry experience of at least four to five years of experience with computer programming and general knowledge of database technologies and networking or similar fields. A POS[A] in the 2000 time frame would also have at least two years of experience in the healthcare, or healthcare-related, industry. Ex. 1013 ¶ 16. Patent Owner’s Declarant, Dr. Goodin, agrees with Dr. Bergeron’s definition (Ex. 2012 ¶ 41). We agree with and adopt this definition for the purposes of our Final Written Decision.” slip op. at 8

    • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionUnpatentable

      “On this record, we are persuaded that claims 1–20 are directed to the broad concept of scrubbing medical claims before submission, i.e., pre- processing medical claims to identify and correct errors. See Pet. 16; Pet. Reply 3. In particular, the patent claims all require automatically interacting with the completed claim submission by the medical practice management server to correct an error in the completed claim submission, wherein the error is resolved by the medical practice client before processing the completed claim submission, by applying one or more rules from a class of rules associated with the payor server, wherein the one or more rules comprises a new rule, an updated rule, or both received from the payor server. Ex. 1001, 20:12–20 (claim 1), 22:24–32 (claim 18), 23:11–19 (claim 20) (emphases added). Further, the concept of scrubbing medical claims before submission is consistent with the ’116 Patent Specification, which explains: “Given the extent of wasted time and money associated with the process [for filing and processing health insurance claims], there exists a need to manage a medical practice in a more efficient manner and [to] provide insurance claims with fewer or no errors.” Id. at 1:64–67. According to the Specification, “[t]he present invention automatically and repeatedly interacts with an insurance company system and/or applies rules to efficiently manage a medical practice and provide insurance claims with a reduced number of errors.” Id. at 2:3–6. In a preferred embodiment, rules engine 60 applies rules to the claim entry form and thereby “scrubs” the claim before submission. Id. at 13:31–59; see Ex. 1001, 13:33–34, Fig. 3F (“The rules engine 60 ‘scrubs’ the claim (step 390), or examines the claim for claim errors.”); Pet. 28 n.2. Given these disclosures, we are unpersuaded that any specific claim limitations need to be added to the above articulated abstract concept, as we discern that they merely provide support to the abstract concept of scrubbing medical claims before submission. Despite Patent Owner’s arguments to the contrary, we see little difference between scrubbing medical claims before submission and the type of fundamental economic practice considered to be an abstract idea by the Supreme Court in Alice.1 As established by the record, scrubbing medical claims before submission is a practice that existed long before the ’116 Patent. See, e.g., Ex. 1001, 1:31–40; Ex. 1012, 2:27–39; Ex. 1013 ¶¶ 33–34; Ex. 1024,2 107–108; Ex. 1029 ¶¶ 10–12, 14, 27. That the claims recite using a database of updated rules, multiple computers, and a claim edit screen, for scrubbing medical claims before submission, does not render the claims any less abstract. See Intellectual Ventures I LLC v. Capital One Bank (US), 792 F.3d 1363, 1367 (Fed. Cir. 2015) (holding that “while the claims recite budgeting using a ‘communication medium’ (broadly including 1 In Alice, the Supreme Court determined that the claims at issue were “drawn to the concept of intermediated settlement,” i.e., the use of a third party to mitigate settlement risk. 134 S. Ct. at 2356. The Supreme Court also determined that “[l]ike the risk hedging in Bilski [Bilski v. Kappos, 561 U.S. 593 (2010)], the concept of intermediated settlement is ‘a fundamental economic practice long prevalent in our system of commerce.’” 134 S. Ct. at 2356 (citations omitted). With respect to the first step of the “Mayo framework,” the Supreme Court concluded in Alice that “there is no meaningful distinction between the concept of risk hedging in Bilski and the concept of intermediated settlement” in Alice, and that “[b]oth are squarely within the realm of ‘abstract ideas’ as we have used that term.” Alice., 134 S. Ct. at 2357. 2 Bringing Health Care Online: The Role of Information Technologies, U.S. Congress, Office of Technology Assessment (Sept. 1995). the Internet and telephone networks), that limitation does not render the claims any less abstract”). We conclude, therefore, that Petitioner has demonstrated that the ʼ116 Patent claims, like the claims in Alice, are directed to an abstract idea, namely, scrubbing medical claims before submission.” slip op. at 14

    • Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptUnpatentable

      “For reasons that parallel those articulated by the Federal Circuit in Intellectual Ventures I, we determine, contrary to Patent Owner’s arguments, that claims 1–20 of the ’116 Patent do not incorporate an inventive concept. See Alice, 134 S. Ct. at 2355; Intellectual Ventures I, 792 F.3d at 1368–70. Rather, the steps and limitations in the claims, whether considered individually or as an ordered combination, amount to a mere instruction to implement the abstract idea on a computer. See Alice, 134 S. Ct. at 2358. Like the claims at issue in Alice and Intellectual Ventures I, the ’116 Patent claims all recite generic computer elements (servers, rules, database, interactive screen, etc.) performing generic computer tasks such as storing rules in a database, receiving data, performing automated operations, and transmitting data. See, e.g., Ex. 1001, 20:2–42 (claim 1); see Alice, 134 S. Ct. at 2359; Intellectual Ventures I, 792 F.3d at 1368, 1370; Ex. 1001, 4:27–57 (servers), 5:60–61 (rule), 5:66–6:8 (rules database), 14:62–65 (interactive screen); Ex. 1013 ¶¶ 54, 56, 57, 62; Ex. 1029 ¶¶ 22– 27; Ex. 2011, 158:23–159:5; Ex. 2024, 94:4–17. Patent Owner’s argument, on page 76 of the Response, that the claims” slip op. at 21

    Patent outcomesUS 7,617,116 unpatentable
    Claim construction§ 101 eligibility§ 103 obviousnesscites Alice · Mayo · Bilski · KSR · Graham
    Patents in suitUS 7,617,116

Holdings, summaries, rulings, issues, outcomes, winners and claim constructions shown for a decision were generated by a large language model reading the opinion. They are a guide to the decision, not the decision. Confirm every one against the court's own text before relying on it. Outcomes read from the patent owner’s side. Party names are extracted from the decision and are missing on about 900 short Director denials and scans, which carry the trial number instead.