throbber
Trials@uspto.gov
`Tel: 571-272-7822
`
`
`
`
`Paper 22
`Entered: January 28, 2014
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`_______________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_______________
`
`CARDIOCOM, LLC
`Petitioner
`
`v.
`
`ROBERT BOSCH HEALTHCARE SYSTEMS, INC.
`Patent Owner
`_______________
`
`Case IPR2013-00468
`Patent 7,516,192 B2
`_______________
`
`
`
`Before JUSTIN T. ARBES, BRYAN F. MOORE, and
`TRENTON A. WARD, Administrative Patent Judges.
`
`MOORE, Administrative Patent Judge.
`
`
`
`
`DECISION
`Institution of Inter Partes Review
`37 C.F.R. § 42.108
`
`
`
`I. INTRODUCTION
`
` A. Background
`
`Cardiocom, LLC (Petitioner) filed a Petition to institute an inter partes
`
`review of claims 1-19 of U.S. Patent No. 7,516,192 B2 (“the ‟192 patent”).
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`Paper 1. Robert Bosch Healthcare Systems, Inc. (Patent Owner) filed a
`
`Preliminary Response. Paper 11. We have jurisdiction under 35 U.S.C. § 314.
`
`The standard for instituting an inter partes review is set forth in 35 U.S.C.
`
`§ 314(a), which provides as follows:
`
`THRESHOLD -- The Director may not authorize an inter
`partes review to be instituted unless the Director
`determines that the information presented in the petition
`filed under section 311 and any response filed under
`section 313 shows that there is a reasonable likelihood
`that the petitioner would prevail with respect to at least
`1 of the claims challenged in the petition.
`
`Petitioner contends that the challenged claims are unpatentable under
`
`35 U.S.C. § 103 on the following specific grounds:
`
`Reference(s)
`
`Wright Jr., U.S. Patent No.
`5,704,029 (Ex. 1002)
`Wright Jr. and Goodman, U.S.
`Patent No. 5,827,180 (Ex. 1003)
`Goodman and Wahlquist, U.S.
`Patent No. 5,367,667 (Ex. 1004)
`
`
`
`Basis
`
`§ 103
`
`§ 103
`
`Claims
`challenged
`1-3, 6, 7, 11, 12,
`and 17-19
`1-19
`
`§ 103
`
`1-19
`
`For the reasons given below, we grant the Petition and institute an
`
`inter partes review of all claims challenged.
`
` 2
`
`
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`B. Additional Proceedings
`
`The ‟192 patent is the subject of co-pending district court litigation: Robert
`
`Bosch Healthcare Systems v. Cardiocom, LLC, Civil Action No. 2:13-cv-349 (E.D.
`
`Tex.). Pet. 1. Furthermore, at the time the Petition was filed, patents related to the
`
`‟192 patent were the subject of other district court litigation, ex parte
`
`reexamination, and inter partes review. Pet. 1-2.
`
`C. The ’192 Patent (Ex. 1001)
`
`The ‟192 patent, titled “Networked System for Interactive Communication
`
`and Remote Monitoring of Individuals,” issued on April 7, 2009. The ‟192 patent
`
`relates to “a networked system for remotely monitoring individuals and for
`
`communicating information to the individuals through the use of script programs.”
`
`Ex. 1001, col. 1, ll. 39-43.
`
`The ‟192 patent describes the need for remote monitoring of patients in
`
`out-patient or home healthcare programs. Id. at col. 1, ll. 45-50; col. 2, ll. 33-37.
`
`According to the patent, the use of personal computers, medical monitoring
`
`devices, and interactive telephone or video response systems for remote monitoring
`
`in the prior art had proved inadequate because of their expense, limited multimedia
`
`capability, or the complexity of managing non-compliant patients. Id. at col. 1, l.
`
`65 – col. 2, l. 32.
`
`One embodiment of the ‟192 patent, shown in Figure 1, reproduced below, is
`
`networked system 16 with server 18 connected to the Internet (communication
`
`network 24), where server 18 sends script programs to each remotely
`
`programmable apparatus 26. Id. at col. 4, ll. 18-35.
`
` 3
`
`
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`
`
`Figure 1 depicts a block diagram of networked system of the invention.
`
`According to Figure 1, system 16 may include any number of remotely
`
`programmable apparatuses 26 (in Figure 1, two are shown) for monitoring any
`
`number of patients. Id. at col. 4, ll. 42-44. In one preferred embodiment, each
`
`patient is provided with monitoring device 28 (such as a blood glucose meter),
`
`which produces measurements of a physiological condition of the patient (such as
`
`blood glucose concentrations in the patient) and transmits those measurements to
`
`the patient‟s remote apparatus 26 via standard cable 30. Id. at col. 4, ll. 45-61. In
`
`operation, remotely programmable apparatus 26 executes a script program received
`
`from server 18. Id. at col. 5, ll. 7-9. That script program includes “queries,
`
`reminder messages, information statements, useful quotations, or other information
`
`of benefit to the patient.” Id. at col. 5, ll. 9-11.
`
`Claim 1, the sole independent claim challenged, illustrates the claimed
`
`subject matter and is reproduced below:
`
`1. A monitoring system for communicating with at least
`one individual, the monitoring system comprising:
`
`
`
`
` 4
`
`
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`
`
`
`
`
`
`
`
`
`
`
`a computer configured to communicate with at least
`one remotely situated apparatus;
`
`a user interface in communication with the computer
`for entering, authoring, selecting, or any combination
`thereof, at least one of (i) one or more messages to be
`presented to the individual, (ii) one or more queries to
`be answered by the individual, (iii) one or more
`response choices corresponding to the one or more
`queries or (iv) any combination thereof;
`
`a data merge program configured to generate a
`customized script program by customizing a generic
`script program, wherein the customized script
`program is to be executed by the remotely situated
`apparatus and includes (i) a display command to
`present to the individual at least one of the one or
`more messages, the one or more queries, the one or
`more response choices corresponding to the one or
`more queries or any combination thereof and (ii) an
`input command to receive responses when the script
`program includes one or more queries to be presented;
`and
`
`one or more databases accessible by the data merge
`program for storing the generic script program and
`any responses received from the remotely situated
`apparatus.
`
`
`
`D. Claim Construction
`
`Consistent with the statute and the legislative history of the Leahy-Smith
`
`America Invents Act, Public Law No. 112-29, 125 Stat. 284 (September 16, 2011),
`
`the Board will interpret claims of an unexpired patent using the broadest
`
`reasonable construction in light of the specification of the patent. See Office
`
` 5
`
`
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,766 (Aug. 14, 2012); 37
`
`C.F.R. § 42.100(b).
`
`1.
`
`“script program”
`
`Claim 1 recites a script program. Petitioner provides a dictionary definition
`
`of the term as being “a type of program that consists of a set of instructions to an
`
`application or a utility program. A script usually consists of instructions expressed
`
`using the application‟s or utility‟s rules and syntax, combined with simple control
`
`structures such as loops and if/then expressions.” Ex. 1008 ¶ 25 (citing
`
`MICROSOFT PRESS COMPUTER DICTIONARY (3d ed. Microsoft Press 1997) (Ex.
`
`1009, 422-23)). Petitioner further argues that the term “script program” means “a
`
`program including at least one text command and [that] can be interpreted and
`
`performed by a device, such as a computer.” Pet. 12 (citing Declaration by Robert
`
`T. Stone (Ex. 1008) ¶ 25). Petitioner argues that a script program must include “at
`
`least one text command,” but Petitioner does not explain why a script program
`
`necessarily must include a text command in view of the definition of the “script,”
`
`above, that does not require a text command.
`
`Patent Owner argues that “script program” should mean “a set of
`
`instructions or commands written in a language that can be interpreted and
`
`executed by another program.” Prelim. Resp. 10. Hence, Patent Owner argues
`
`that a “script command” must be interpreted and executed by another program, as
`
`opposed to a device or computer. As Patent Owner notes, the ‟192 patent
`
`Specification discloses a microprocessor that stores firmware in memory, in which
`
`the firmware includes a script interpreter used by the microprocessor to execute
`
`script programs. Ex. 1001, col. 5, ll. 55-59. In other words, the ‟192 patent
`
`Specification discloses that a microprocessor executes script programs (by using a
`
`script interpreter). Patent Owner argues that a “script interpreter” as disclosed in
`
` 6
`
`
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`the Specification is “another program.” Patent Owner, however, does not
`
`demonstrate persuasively that the microprocessor, which executes the script
`
`program, is necessarily “another program” and not a device, such as a computer.
`
`In any event, Patent Owner does not demonstrate that claim 1 requires a script
`
`program that is not executed by a device or computer.
`
`Based on the definition of “script program,” as a set of instructions of a
`
`program and the disclosure that a script program is executed, we agree that under a
`
`broad, but reasonable, construction of the term, a “script program” is a program
`
`that contains a set of instructions that is capable of being executed and interpreted.
`
`2.
`
`“data merge program”
`
`Claim 1 recites a data merge program. Petitioner argues that the term “data
`
`merge program” should be construed to mean “a software module that combines
`
`two or more sets of items into one.” Pet 13 (citing Ex. 1008 ¶ 26). Petitioner
`
`further cites a dictionary definition of the term “merge” as meaning “combin[ing]
`
`two or more sets of items into one, usually in a specified sequence.” Pet. 13 (citing
`
`IEEE STANDARD DICTIONARY OF ELECTRICAL AND ELECTRONICS TERMS, 583 (The
`
`Institute of Electrical and Electronics Engineering, 4th ed. 1988) (Ex. 1010)). We
`
`note that the dictionary definition states that merging items is done “usually in a
`
`specified sequence,” which means that merged items are not required to be in a
`
`specified sequence. Therefore, we do not construe the “data merge program” as
`
`requiring merged items to be in a specified sequence.
`
`Patent Owner argues that the ‟192 patent Specification “refers to . . . a „mail
`
`merge application,‟ which is more specific than merging generally.” Therefore, “it
`
`is not reasonable to adopt a construction” of the term “data merge program” that
`
`“includes „merging‟ of any „items‟ and not only „data,‟ and includes any kind of
`
`„merging‟ and not only merging data into a template.” Prelim. Resp. 15. Thus,
`
` 7
`
`
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`Patent Owner argues that the term “data merge program” should be construed to
`
`mean “software that takes data and inserts the data into a script program or other
`
`template.” Prelim. Resp. 12-13.
`
`Although we agree with Patent Owner that the ‟192 patent Specification
`
`discloses “merging personal data with the script programs, much like a standard
`
`mail merge application” (Ex. 1001, col. 12, ll. 60-62), Patent Owner does not
`
`indicate that the ‟192 patent Specification also discloses that a data merge program
`
`contains specifically enumerated features of a “standard mail merge application”
`
`and what such specifically enumerated features of the mail merge application
`
`might be. Also, claim 1 recites “a data merge program configured to generate a
`
`customized script program” and, therefore, explicitly recites that the data merge
`
`program is for generating a script program. Incorporating explicitly recited
`
`features of the data merge program (i.e., for merging data with a script program)
`
`into the definition of the term would be redundant. Finally, claim 1 explicitly
`
`recites that “data” is to be merged rather than “items,” therefore, we agree that
`
`Petitioner‟s construction should include the term data, rather than item.
`
`Therefore, we construe the term “data merge program” broadly, but
`
`reasonably, and in light of the Specification to mean a program that combines two
`
`or more sets of data into one, as proposed by Petitioner.
`
`3.
`
`“pointer”
`
`Claims 2 and 5 recite a pointer. Petitioner argues that the term “pointer”
`
`should be construed to mean “an identifier that indicates the location of an item of
`
`data.” Pet. 14. Patent Owner does not propose a construction for this term.
`
`In accordance with a broad but reasonable construction of the term in light
`
`of the Specification, we adopt the Petitioner‟s construction of the term “pointer” to
`
`be “an identifier that indicates the location of an item.” Pet. 14.
`
` 8
`
`
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`
`
`4.
`
`“script assignment unit”
`
`Claims 2, 5, 8, and 10 recite a script assignor. Petitioner argues that the term
`
`“script assignment unit” should be construed to mean “a software module that
`
`associates a script program with an individual.” Pet. 13. Patent Owner does not
`
`propose a construction for this term. In accordance with a broad but reasonable
`
`construction of the term in light of the Specification, we adopt the Petitioner‟s
`
`construction of the term “script assignment unit” to be a program that associates a
`
`script program with an individual. Id.
`
`II. ANALYSIS
`
`A. Overview of Wright Jr. (Ex. 1002)
`
`Wright Jr. discloses a system for computerized form completion and
`
`processing. Ex. 1002, Abstract. In one embodiment, an electronic form is sent
`
`form a personal computer (PC) to a device, such as a personal digital assistant
`
`(PDA). Id. at col. 3, ll. 28-39. The PDA runs a forms engine that presents
`
`questions to a user and displays messages based on the response to a particular
`
`question. Id. at col. 3, ll. 40-51. The forms engine executes a script that, among
`
`other things, advances to the next question. Id.
`
`B. Overview of Goodman (Ex. 1003)
`
`Goodman discloses a system for monitoring the health of a patient in which
`
`a host computer is in communication with a health care provider‟s computer and a
`
`patient‟s computer. Ex. 1003, col. 1, ll. 11-13, col. 2, ll. 45-49. In one example,
`
`the host computer receives a treatment plan for a patient from the health care
`
`provider and generates an algorithm based on the treatment plan. Id. at col. 2, ll.
`
`54-57. The algorithm is programmed into a message device, which is in the
`
` 9
`
`
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`possession of the patient. Id. at col. 2, ll. 49-50, 57-58. The message device
`
`prompts the patient to measure and enter physiological data as dictated by the
`
`treatment plan. Id. at col. 2, ll. 59-61.
`
`C. Overview of Wahlquist (Ex. 1004)
`
`Wahlquist discloses a system for performing remotely, computer diagnostic
`
`tests on personal computers. Ex. 1004, col. 1, ll. 7-10. A computer user calls a
`
`customer service help desk to resolve a computer issue. Id. at col. 2, ll. 8-10, 17.
`
`A representative at the customer service help desk creates a computerized case file
`
`that includes a unique case identification number, user identification, and user‟s
`
`computer identification information. Id. at col. 4, ll. 41-50. The representative
`
`also selects diagnostic tests based on the user‟s request, the selection used to build
`
`a script file. Id. at col. 2, ll. 17-18, 22-23. The case file and the script file are
`
`submitted by the representative to a database manager computer and downloaded
`
`to the user‟s computer. Id. at col. 5, ll. 37-39, 63-66. The script file then is
`
`executed on the user‟s computer by a diagnostic program on the user‟s computer.
`
`Id. at col. 2, ll. 39-40, 42-43. The script file instructs the user‟s computer to
`
`execute desired test files and specifies the creation of various log files to record the
`
`results of the tests. Id. at col. 2, ll. 45-47.
`
`A. Obviousness over Wright Jr.1
`
`1. Claims 1-3, 6, 7, 11, 12, and 17-19
`
`Petitioner asserts that claims 1-3, 6, 7, 11, 12, and 17-19 are unpatentable
`
`under 35 U.S.C. § 103(a) over Wright Jr. Pet. 5.
`
`
`1 References to anticipation, on page 18 and the Table of Contents of the Petition,
`appear to be typographical errors, as the discussion on pages 18-20 and the detailed
`claim charts on pages 34-54 refer to obviousness.
`
`
`
`
`10
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`Petitioner argues that Wright Jr. provides teachings for sending customized
`
`script programs to remote computing devices for collecting and recording data.
`
`Pet. 16, 21-23. Patent Owner argues that Wright Jr. “does not teach a customized
`
`script program that includes a display command and an input command, because
`
`. . . [Wright Jr.] only teaches scripts that execute after questions are displayed to,
`
`and input is collected from, the user.” Prelim. Resp. 43.
`
`Claim 1 recites “the customized script program . . . includes (i) a display
`
`command to present to the individual . . . queries . . . and (ii) an input command to
`
`receive responses . . . .” Patent Owner argues that Wright Jr. teaches that “its
`
`„execute script‟ function is distinct from the functions that display queries and
`
`receive responses.” Prelim. Resp. 43 (citing Ex. 1002, col. 17, ll. 29-45).
`
`However, as noted above, for the purposes of this decision, we construe a “script
`
`program” to be a program that contains a set of instructions that is capable of being
`
`executed and interpreted. Wright Jr. teaches that a forms designer can create an
`
`electronic form that displays queries and provides user input responses. See Pet.
`
`37 (citing Ex. 1002, col. 9, l. 33 – col. 13, l. 23). Petitioner has demonstrated
`
`sufficiently that Wright Jr. discloses an executable form capable of executing
`
`“script” functions and that the executable form may be considered a “script
`
`program.”
`
`Patent Owner argues that Wright Jr. “does not teach „a data merge program
`
`configured to generate a customized script program by customizing a generic script
`
`program‟ because . . . [Wright Jr.] only teaches a user manually modifying a
`
`duplicated form to revise or modify it.” Prelim. Resp. 32-33. However, as noted
`
`above, for the purposes of this decision, we construe a “data merge program” to be
`
`a program that combines two or more sets of data into one. Petitioner has
`
`demonstrated sufficiently that Wright Jr. discloses a program in which a user can
`
`
`
`
`11
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`create a duplicate form by editing an existing form. Pet. 35. Further, claim 1 does
`
`not require that the data merge program automatically enter data. Claim 1 only
`
`requires that the data merge program generate a customized script program by
`
`customizing a generic script program. Claim 1 does not exclude the possibility
`
`that the data to be merged is provided by a user. For example, claim 1 recites “a
`
`data merge program configured to generate a customized script program by
`
`customizing a generic script program.” Claim 1 does not indicate how the
`
`customizing is to be done or that it must be done without user input of data. Thus,
`
`Patent Owner‟s argument is not commensurate in scope with the claim language.
`
`We are persuaded, based on the record before us, by Petitioner‟s argument that the
`
`field editor of Wright Jr. would result in the generation of a customized script from
`
`a generic script. See, e.g., Ex. 1002, col. 6, ll. 33-40; col. 9, ll. 51-60; col. 8, ll.
`
`32-38.
`
`Patent Owner argues Wright Jr. “does not teach at least the limitation „one or
`
`more databases . . . for storing the generic script program.‟” Prelim. Resp. 46.
`
`Petitioner explains that user responses are stored on the personal computer in a
`
`tab-delimited format for use with a database. Pet. 37-38 (citing Ex. 1002, col. 3, ll.
`
`28-40; col. 5, ll. 7-15; col. 14, ll. 1-10). Wright Jr. also teaches that a form can be
`
`selected from a list of existing forms. Id. It is not necessary for the cited art to
`
`teach precisely “the specific subject matter of the challenged claim, for a court can
`
`take account of the inferences and creative steps that a person of ordinary skill in
`
`the art would employ.” KSR Int'l Co. v. Teleflex, Inc., 550 U.S. 398, 418 (2007)
`
`(“KSR”). On the record before us, we are persuaded that Petitioner has shown
`
`sufficiently that an existing electronic form (generic script program) may be stored
`
`in a database.
`
`Petitioner provides explanations as to how each remaining claim limitation
`
`
`
`
`12
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`is disclosed or suggested by Wright Jr. and articulates, based on the current record,
`
`sufficient reasoning with a rational underpinning to support its obviousness
`
`challenge. Pet. 18-20, 34-54; see also KSR, 550 U.S. at 418. Upon consideration
`
`of Petitioner‟s analysis and supporting evidence, and taking into account Patent
`
`Owner‟s preliminary response, we determine that Petitioner‟s contentions have
`
`merit.
`
`Accordingly, on the record before us, we are persuaded that Petitioner has
`
`shown a reasonable likelihood that it will prevail in its assertion that independent
`
`claim 1 is unpatentable over Wright Jr. Additionally, we are persuaded, in
`
`connection with this ground, that Petitioner has shown a reasonable likelihood of
`
`unpatentability as to claims 2, 3, 6, 7, 11, 12, and 17-19, which ultimately depend
`
`from claim 1.
`
`D. Obviousness over Wright Jr. and Goodman
`
` Petitioner asserts that claims 1-19 are unpatentable under 35 U.S.C. §
`
`103(a) over Wright Jr. and Goodman. Pet. 5. Petitioner relies on the teachings of
`
`Goodman for certain limitations of claims 1-19. See Pet. 34-54. Petitioner asserts
`
`that it would have been obvious for a person of ordinary skill in the art to combine
`
`Wright Jr. and Goodman “because the script programs of Wright Jr. provide
`
`numerous advantages relating to flexibility and customized collection of user
`
`information.” Pet. 22 (citing Ex. 1008 ¶ 57).
`
`Patent Owner argues that Wright Jr. “does not teach all of the advantages of
`
`scripts that Cardiocom alleges,” and the “actual teachings of [Wright Jr.] offer no
`
`significant advantages to the system of Goodman.” Prelim. Resp. 50-51.
`
`
`
`Patent Owner argues that it would not have been obvious to one of ordinary
`
`skill in the art to combine the teachings of Wright Jr. and Goodman because,
`
`among other things, “there are significant differences between the system of
`
`
`
`
`13
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`Goodman and the system of Wright,” and Goodman‟s system does not use script
`
`programs. Prelim. Resp. 50-52.
`
`Goodman discloses a system in which a computer generates an algorithm at
`
`a device and programs the algorithm into another device (i.e., a message device).
`
`Ex. 1003, col. 2, ll. 49-50, 54-58. Wright Jr. also discloses a system in which a
`
`script file (or algorithm) is generated at a computer device and sent to and executed
`
`by another device (i.e., a PDA). Ex. 1002, col. 6, ll. 33-45, 62-67; col. 7, ll. 47-62.
`
`In other words, both Wright Jr. and Goodman disclose systems in which an
`
`algorithm or script file is generated at one device and sent to another device for
`
`execution. Patent Owner does not demonstrate persuasively that the combination
`
`of the known system of Wright Jr.2 and the known system of Goodman3 would
`
`have entailed any more than the combination of known systems to perform their
`
`known functions to achieve the predictable result of a system in which a device
`
`generates an algorithm and programs the algorithm into another device for
`
`execution on the other device. “The combination of familiar elements according to
`
`known methods is likely to be obvious when it does no more than yield predictable
`
`results.” KSR Int’l Co. v. Teleflex, Inc., 550 U.S. 398, 416 (2007).
`
`Petitioner provides explanations as to how each claim limitation is disclosed
`
`or suggested by the combination of Wright Jr. and Goodman and articulates, based
`
`on the current record, sufficient reasoning with a rational underpinning to support
`
`a conclusion of obviousness. Pet. 21-28, 34-54. Upon consideration of
`
`
`2 i.e., a device (i.e., computer) that generates a script file (or algorithm) and
`programs the script file (i.e., downloads the script file) to another device (i.e., a
`user‟s computer) for execution on the other device.
`3 i.e., a device that generates an algorithm and programs the algorithm into another
`device for execution.
`
`
`
`14
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`Petitioner‟s analysis and supporting evidence, and taking into account Patent
`
`Owner‟s preliminary response, we determine that Petitioner‟s contentions have
`
`merit.
`
`Accordingly, on the record before us, and for the foregoing reasons, we are
`
`persuaded that Petitioner has shown a reasonable likelihood that it will prevail in
`
`its assertion that independent claim 1 is unpatentable over Wright Jr. and
`
`Goodman. Additionally, we are persuaded, in connection with this ground, that
`
`Petitioner has shown a reasonable likelihood of unpatentability as to claims 2-19,
`
`which ultimately depend from claim 1.
`
`E. Obviousness over Goodman and Wahlquist
`
`Petitioner asserts that claims 1-19 are obvious under 35 U.S.C. § 103(a) over
`
`Wahlquist in combination with Goodman. Pet. 6.
`
`Claim 1 recites using a data merge program to generate a customized script
`
`program from a generic script program.
`
`Petitioner argues that Goodman discloses generating algorithms that are
`
`based on treatment plans developed specifically for a patient. Pet. 31, 35, 42, 43,
`
`50, 52, and 53. Patent Owner argues that “[b]ecause Goodman does not teach the
`
`claimed function of „generat[ing] a customized script program by customizing a
`
`generic script program,‟ Goodman cannot teach a „data merge program‟ that
`
`performs that function.” Prelim. Resp., 34-35.
`
`As Petitioner explains, Goodman discloses “logic sequences or algorithms
`
`. . . [that] are developed based on a treatment plan or guidelines for a specific
`
`patient. Ex. 1003, col. 8, ll. 38-40. However, Petitioner has not demonstrated
`
`sufficiently that Goodman also discloses a program that combines two or more sets
`
`of data into one (i.e., a “data merge program”). Based on the record before us,
`
`Petitioner has demonstrated that Goodman only discloses developing a treatment
`
`
`
`
`15
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`plan and does not disclose combining the treatment plan, or any other set of data,
`
`with at least one other set of data.
`
`Petitioner also argues that Wahlquist discloses selecting tests from a menu to
`
`build a script file. Pet. 30. Wahlquist discloses a representative creating a
`
`“computerized case file which includes . . . user identification information.” Ex.
`
`1004, col. 2, ll. 10-14. Wahlquist also discloses that the representative “selects
`
`various diagnostic tests from a menu . . . to build a high level . . . script file.” Id. at
`
`col. 2, ll. 18-23. Patent Owner argues that “the tests are not part of the script file,
`
`and they are only executed, not “combine[d]” as Cardiocom asserts.” Prelim.
`
`Resp. 37.
`
`As previously described, Petitioner explains that Wahlquist discloses
`
`creating a computerized case file and a (separate) script file. However, as Patent
`
`Owner points out, Petitioner does not demonstrate sufficiently that Wahlquist also
`
`discloses a program that combines two or more sets of data into one (i.e., a “data
`
`merge program”). Instead, Wahlquist merely discloses creating two separate files
`
`or sets of data (i.e., a computerized case file and a script file) but does not disclose
`
`combining the two separate sets of data into one.
`
`Petitioner argues that Wahlquist discloses that “the created script program
`
`and a case management file [are] sent to a user computer, thereby associating the
`
`script program with the case management file.” Pet. 36; Ex. 1008 ¶ 133. Even
`
`assuming that a case management file is “associated” with a script program in
`
`Wahlquist, Petitioner does not demonstrate that Wahlquist also discloses that two
`
`sets of data (i.e., the case management file and the script program) are combined
`
`into one. In other words, Petitioner does not demonstrate that a set of data that is
`
`“associated with” another set of data also is combined (or “merged”) with the other
`
`set of data.
`
`
`
`
`
`16
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`Petitioner argues that Wahlquist discloses that “the created script program
`
`and a case management file [are] to a user computer, thereby associating the script
`
`program with the case management file [and] information from the case
`
`management file [is used] to perform diagnostic tests and return results to a
`
`server.” Pet. 36; Ex. 1008 ¶ 133. In other words, Petitioner argues that the two
`
`separate sets of data (i.e., the script program and the case management file) of
`
`Wahlquist actually are “merged” (i.e., combined into one data set) because one set
`
`of data (i.e., the script file) uses the other set of data (i.e., the case management
`
`file) to perform tests. However, even assuming that the script file “uses” the case
`
`management file in Wahlquist, Petitioner does not demonstrate persuasively that
`
`one set of data “using” information from another set of data necessarily results in
`
`the two sets of data being combined into one set of data.
`
`Accordingly, on the record before us, and for the foregoing reasons, we are
`
`not persuaded that Petitioner has shown a reasonable likelihood that it will prevail
`
`in its assertion that independent claims 1 is unpatentable over the combination of
`
`Wahlquist and Goodman. Additionally, we are not persuaded in connection with
`
`any of these grounds of unpatentability as applied to claims 2-19, which ultimately
`
`depend from claim 1.
`
`III. SUMMARY
`
`Petitioner has demonstrated a reasonable likelihood of prevailing in showing
`
`that claims 1-19 of the ‟192 patent are unpatentable. The Board, however, has not
`
`made a final determination as to the patentability of these claims.
`
`The Petition is granted as to the following proposed grounds: obviousness
`
`of claims 1-3, 6, 7, 11, 12, and 17-19 over Wright Jr.; and obviousness of claims
`
`1-19 over Wright Jr. and Goodman.
`
`
`
`17
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`The Petition is denied as to all other grounds proposed.
`
`IV. ORDER
`
`For the reasons given, it is
`
`ORDERED that the Petition is granted as to claims 1-19;
`
`FURTHER ORDERED that pursuant to 35 U.S.C. § 314(a), inter partes
`
`review of the ʼ192 patent is hereby instituted, commencing on the entry date of this
`
`Order. Pursuant to 35 U.S.C. § 314(c) and 37 C.F.R. § 42.4, notice is hereby given
`
`of the institution of a trial;
`
`FURTHER ORDERED that the trial is limited to the grounds identified
`
`above. No other grounds are authorized; and
`
`FURTHER ORDERED that an initial conference call with the Board is
`
`scheduled for 2:00 PM Eastern Time on February 13, 2014. The parties are
`
`directed to the Office Trial Practice Guide, 77 Fed. Reg. 48,756, 48,765-66
`
`(Aug. 14, 2012) for guidance in preparing for the initial conference call, and
`
`should be prepared to discuss any proposed changes to the Scheduling Order
`
`entered herewith and any motions the parties anticipate filing during the trial.
`
`
`
`
`
`
`
`18
`
`
`
`

`

`IPR2013-00468
`Patent 7,516,192 B2
`
`
`
`
`PETITIONER:
`
`Daniel W. McDonald
`Andrew J. Lagatta
`MERCHANT & GOULD, P.C.
`dmcdonald@merchantgould.com
`alagatta@merchantgould.com
`
`
`PATENT OWNER:
`
`Don Daybell
`Davin M. Stockwell
`ORRICK, HERRINGTON & SUTCLIFFE LLP
`ddaybell@orrick.com
`dstockwell@orrick.com
`ptabdocket@orrick.com
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`19
`
`
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket