Patent Grant
11194810
None.
The invention relates to systems and methods for utilizing information generated by remote medical device management systems from multiple medical institutions and/or facilities. More particularly, the present invention relates to providing aggregated data, including but not limited to configuration information and activity information regarding medical devices, such as medication delivery pumps, to remote medical institutions and/or facilities for device configuration library development and/or benchmarking purposes.
Modern medical care often involves the use of electronic medical devices such as medication delivery pumps and/or patient condition monitors. Electronic medical pumps, for example, can be electronically loaded or configured with a customizable “drug library” containing certain drug delivery information or parameters, as disclosed in U.S. Pat. Nos. 5,681,285 and 6,269,340. Medication management systems for configuring, controlling, and monitoring medication delivery devices have been disclosed. For example, commonly owned U.S. patent application Ser. No. 10/930,358, which published as US20050144043A1 on Jun. 30, 2005 and U.S. patent application Ser. No. 10/783,573, which published as US20050278194A1 on Dec. 15, 2005, disclose a medication management system in which a user-customizable drug library or medical device configuration information is prepared using a drug library editor (DLE) program and module of a medication management unit (MMU). The MMU downloads the customizable drug library to the medication delivery pump and receives status or activity information from the pump. Commonly owned U.S. patent application Ser. No. 10/783,877, which also published as WO2005050526A2 on Jun. 2, 2005, discloses how the drug library or medical device configuration information is created, edited, stored and communicated to a medication delivery device in the context of a medication management system to deliver substances, such as fluids and/or fluid medication to patients. According to the above-mentioned commonly owned published patent applications, a typical medication management system includes a MMU in communication with one or more medication delivery devices. The MMU is a computer, typically a server, with an associated memory that stores the customized drug library or information for configuring the medication delivery devices and the activity information received from the medication delivery devices.
In the past, the activity and configuration information collected by an individual medication management system was stored in one or more computers at each individual institution and/or facility or in one or more computers set up by the vendor of the system. Other institutions or facilities did not have access to the activity and configuration information for comparison or other purposes.
One of the more difficult and time-consuming tasks for a medical institution to accomplish in order to implement a medication management system is the development of a customized drug library or set of medical device configuration information. Vendors of medication management systems or medical devices are typically not permitted to practice medicine and can only make recommendations that authorized medical personnel at the individual medical institution must review, modify if necessary and approve. Furthermore, medical institutions usually want to customize their drug library or medical device configuration information to best suit the particular needs, medical judgments and practices of their institution. However, the process of developing and approving a drug library or medical device configuration information for an institution can take months and often involves medical personnel from many areas of the institution. To facilitate and expedite the creation, development, and continued maintenance of a drug library or medical device configuration information, a need exists for institutions to understand and compare how other institutions have organized their customized medical device configuration information and what specific values they have used for various parameters or variables, both before and after an institution has installed and implemented a medication management system.
Another difficult task is evaluating the enormous amount of activity information that a medical device management system or medication management system generates. With existing medical device management systems or medication management systems, various reports can be generated by the system to allow the medical institution and/or facility to track various measures. However, it is often hard to draw meaningful conclusions about the data or the reports in the abstract. A need exists to allow an individual medical institution and/or facility to compare their activity information to the activity information of other institutions and/or facilities.
Knowledge in the area of medicine and delivery of medication is not static; it is dynamic and constantly evolving. There is a demand to make continuing improvements in the areas of patient safety, caregiver productivity, and standards of care. Thus, there is a need to have medical device configuration and activity information that is dynamic, up-to-date and based on actual recent experience in medical institutions. It is also desirable for medical institutions and/or facilities to be able to consider what their peers, based on one or more similarity or level of performance factors, are doing relative to medical device configuration and activity information.
One objective of the present invention is the provision of a method and system for aggregating medical device configuration information from multiple medical institutions and/or facilities for the purposes of benchmarking and drug library or medical device configuration information development.
A further objective of the present invention is the provision of a method and system for aggregating medical device activity information generated by one or more medical device management systems at multiple medical institutions and/or facilities for benchmarking or other purposes.
A further objective of the present invention is the provision of medical device configuration and activity information that is dynamic, up-to-date and based on actual recent experience in medical institutions.
A further objective of the present invention is the provision of a method and system that allows medical institutions and/or facilities to select a peer group whose recent medical device configuration and activity information is of interest to them.
A further object of the present invention is the provision of a system and method for being able to remotely develop and/or create configuration libraries, in particular when an institution/facility has purchased a medication delivery system, but the medication delivery system, or portions thereof, has not been installed yet or the installation has not yet been completed.
The present invention is provided to solve the problems discussed above and, to provide advantages and aspects not provided by prior medical pumps, as well as achieve other objects not explicitly stated above. A full discussion of the features, advantages and objects of the present invention is deferred to the following detailed description, which proceeds with reference to the accompanying drawings.
The invention relates to systems and methods for utilizing information generated by medical device management systems from multiple medical institutions and/or facilities. A medical device management system such as a medication delivery system can include a medication management unit (MMU). The MMU is in communication with one or more medical devices, such as medication delivery pumps or infusers for example. Other types of medical devices including but not limited to patient condition monitors, vital signs monitors, diagnostic devices, imaging devices, and laboratory devices can communicate with, be configured by, and be monitored by the MMU so as to provide information for use with this invention.
The MMU translates the delivery information and/or the medication order, such as the medication to be delivered and the infusion rate, into delivery programming code or information suitable for programming the designated pump or infuser. The MMU can also communicate to the pump a variety of drug library parameters including but not limited to device specific configuration parameters and hard and/or soft limits for medication delivery rates. These drug libraries and/or other configuration parameters can be considered as configuration information, which can include any other information used to configure the medication delivery pump. Thus, these libraries or configuration libraries can include drug libraries and other configuration information. Each medical institution and/or facility can use a configuration information and/or drug library editor (DLE) module of the MMU to customize or make configuration information institution specific and may update the configuration information from time to time. Different clinical care areas (CCA) exist within a medical institution and/or facility, and each area can have different configuration information, such as drug libraries, for downloading into each of the medication delivery pumps within each clinical care area. A configuration information editor deployed as a part of the MMU, its console, or on a separate computer, enables the institution and/or facility user to import, export and edit configuration information, such as whole drug libraries and individual drug library values, to control and customize the configuration information, such as a drug library, according to hospital preferences and clinical care area preferences. The medication delivery pump can replace an existing configuration library in the memory of the medication delivery pump with an updated configuration library that it receives from the MMU.
The MMU can be configured by an institution and/or facility user at the MMU console to monitor and store in memory the activity of each of the medication delivery pumps, such as alarms, events and pump user interface inputs. This and other information relating to the activity of the medication delivery pumps can be stored as activity information in memory within each medication delivery pump or within the MMU and/or within a central institution's and/or facility information system. The MMU console can also be used to generate reports and control the distribution of configuration libraries to one or more of the medical devices.
Thus, in one embodiment, the present invention is directed to a system and method of aggregating and using medication delivery pump information from a plurality of remote institutions and/or facilities. The system and method electronically receives at a central computer system a plurality of established medication delivery data, each of the plurality of established medication delivery data being received from a respective remote medication delivery system and each of the respective remote medication delivery systems having a respective plurality of medication delivery pumps associated therewith and utilized therein. Each of the respective remote medication delivery systems is associated with and implemented within a respective remote institution and/or facility of the plurality of remote institutions/facilities. The system and method further electronically combines and stores the plurality of established medication delivery data from each of the plurality of remote institutions and/or facilities within a central memory, and electronically provides a remote institution and/or facility remote access to a central reporting application. The central reporting application is adapted to electronically receive search parameters from the remote institution and/or facility for querying the combined established medication delivery data and electronically provides summary information to the remote institution and/or facility about the medication delivery data.
In one embodiment, the established medication delivery data includes medication delivery pump configuration information and medication delivery pump activity information. In one embodiment, the established medication delivery data includes medication delivery pump configuration information and medication delivery pump activity information. The configuration information can include drug library information and medication delivery device specific configuration settings. The drug library information can include, but is not limited to, medication name, generic medication name, medication concentration, medication dosing unit, lower hard limit, lower soft limit, upper soft limit, and upper hard limit.
The device or infuser specific configuration information can include, but is not limited to, medication lockout duration, default occlusion pressure, minimum patient weight, maximum patient weight, maximum dose rate, alarm sounds and nurse callback settings. The activity information can include data which is indicative of how the pump is operating, such as delivery or event data and usage information. The delivery or event data can include, but is not limited to, pump type, user keystrokes to operate the medical device, date and time recorded for each event or activity, alarms, alerts, medication name and clinical care area name. The usage information can include, but is not limited to, compliance information, pump utilization information, user response to alarms and alert information and detailed information related to the user activity or response to the operation of the medical device, such as keystrokes and date and time of such response, including responses to soft and hard limit alerts and pump configuration editing information. The search parameters which a user can select or enter to perform at least searching and reporting functions can include, but are not limited to, entity type, bed size (number of beds), pump type, time frame, service line, and/or generic drug name. The summary information can be used for at least one of assisting the remote institution and/or facility user in generating new and/or modified medication delivery parameters and/or assisting the remote institution and/or facility user in implementing new and/or modified institution and/or facility behaviors and/or practices.
In one embodiment, specific institution and/or facility names are withheld from being identified within the summary information. In another embodiment, each established medication delivery data for each remote institution can include a plurality of distinct clinical care specific medication databases established and utilized with a plurality of distinct clinical care areas within each remote institution. Each of the plurality of distinct clinical care areas can have a clinical care area specific set of medication delivery parameters within the respective established medication delivery data for downloading to a medication delivery pump within the specific clinical care area.
In one embodiment, the summary information relating to the medication delivery pump configuration information and/or the medication delivery pump activity information can be provided and made viewable for a specific medication delivery pump from various interface screen displays of the configuration/activity information application. The central computer system and the configuration/activity information can also be configured to provide statistical information through interface screen displays for various aspects of the configuration and/or activity information within the memory. In one embodiment, the central computer system can be configured to compare at least one of the limits within the configuration information for an institution with limits within at least one of configuration information for a peer group for the institution, for another peer group than the peer group of the institution, and/or for all peer groups. The central computer system can then generate statistical information based on the comparison, including a percent of time the limit is used within the configuration information for the peer group for the institution, for another peer group than the peer group of the institution, and/or for all peer groups. The above statistical and other configuration/activity information in summary form or other form for a medical device data can be displayed over predefined time frames and/or over configurable time frames, including at least one of monthly, quarterly, number of days, number of weeks, number of months, number of years, and/or an interval designated by a beginning date and an ending date.
In a further embodiment, the central computer system can compare activity information received from one institution with activity information received from one or more other institutions for providing a comparison result, and can determine if the comparison result satisfies a predetermined condition. If the condition is met, the central computer system can be configured to communicate an alert to the institution. For example, a specific percentage of times a medical device configuration library information is edited during programming of a medical device within the institution in relation the average number of times medical device configuration library information is edited during programming of medical devices within other institutions, can be compared to determine if an alert should be communicated to an institution. The institution can then review if any action is warranted, such as making an adjustment to configuration information for the medical devices within their institution. The communication can be sent in various ways, such as by e-mail, text message, and/or a page.
In a further embodiment of the present invention, a method of assisting a medical institution in developing an institution-specific customized configuration library for configuring at least one medical device at the institution is provided. The method includes providing a configuration library database comprising medical device configuration information and granting a configuration library developing institution access to view a portion of the configuration library database if access criteria are satisfied. The access criteria can be selected from a group of criteria consisting of active customer status, contract status, subscriber status, data-sharing status, prospect status, user ID match and password match. The developing institution is provided access to copy part of the viewed portion of the configuration library database into an institution-specific customized configuration library database, through remote access to an Internet web site, which can be sponsored by a manufacturer of a medical device. The configuration library database can include drug dosing limits and infuser master settings. The configuration library database can be established by receiving at a central computer system a plurality of previously-established medical device configuration libraries from a corresponding plurality of geographically remote data-sharing institutions at given time. A peer group category designation can be assigned to each of the received previously-established medical device configuration libraries, which can be based on at least facility/entity type, number of beds, medical device type, and/or service line. A searchable relational database can be created including the peer group category designation, from the previously-established medical device configuration libraries. The previously-established configuration libraries can be received at the central computer system at regular time intervals, such as daily, weekly, monthly, quarterly and/or yearly intervals. The central reporting application allows institutions to query the relational database by at least peer group category designation, including being provided access to configuration library information of institutions within the same peer group, other peer groups and/or all peer groups.
In a further embodiment, a method of tracking and comparing activity information for a medical device within an institution is provided. The method includes comparing at a central computer system activity information received from one remote institution, for providing a comparison result, determining if the comparison result satisfies a predetermined condition, and communicating an alert to the institution if the predetermined condition is satisfied. The predetermined condition can include a specific percentage of a number of times a medical device configuration library information is edited during programming in relation to a number of times the medical device is programmed.
In another embodiment, the central computer system and/or the applications therein can be configured to transfer at least a portion of the configuration/activity information database query search results and/or the aggregation of the plurality of established medical device data associated with the search result, to a local storage medium at a remote institution/facility for use within the respective remote medication delivery system. As indicated above, the established medication data can include configuration information including a drug library having a plurality of rule sets for a respective plurality of drugs. Thus, the central computer system and/or applications therein can be configured to transfer at least rule sets for respective drugs to the local storage medium at the remote institution/facility, for at least assisting in the population of new drug entries in a master formulary list and/or CCA sub-list. The transfer can take place through directly importing of the portion of the search result and/or the aggregation of the plurality of established medical device data to a configuration information reporting application, through selecting transfer data using a .csv process, and/or through selecting the portion of the search result and/or the aggregation of the plurality of established medical device data, into a wish list or shopping cart.
Other features and advantages of the invention will be apparent from the following specification taken in conjunction with the following drawings.
To understand the present invention, it will now be described by way of example, with reference to the accompanying drawings in which:
While this invention is susceptible of embodiments in many different forms, there is shown in the drawings and will herein be described in detail preferred embodiments of the invention with the understanding that the present disclosure is to be considered as an exemplification of the principles of the invention and is not intended to limit the broad aspect of the invention to the embodiments illustrated.
As indicated above, a medication delivery system within an institution and/or facility can include configuration information programming systems and/or activity information gathering systems, such as medication management units (MMU). As used herein, an institution can include a health system which has one or more buildings or separate facilities that are owned, leased or managed by a central organization. A facility can be an individual hospital or health care provider. For embodiments in which a facility is a stand alone hospital or health care provider, the facility is also considered a health system or institution. Thus, in one embodiment, multiple facilities will be assigned to one institution. In another embodiment, only one facility will be assigned to an institution. In addition, the term entity is used generically throughout this specification, and includes facilities and health system identification names such as institution, which can also be an institution name, as indicated above.
In this context, an institution can implement one or more MMUs for each facility locally, or an institution can implement MMUs at a remote institution or vendor data center which houses one or more servers or virtual servers that act as MMUs for each facility within the institution. As will be described in the context of at least
The RCLDA server(s) 182 can be configured according to various known techniques. For example, each institution can be provided its own remote server 182 and have a separate instance of an RCLDA 182 installed therein and running thereon for access and use by a customer through a client 150′ or other computer system, through a firewall 128′ and/or through a Front End RCLDA server 180. Alternatively, each institution would not be provided with its own server, and institutions would “share” each server 182. In this embodiment, each RCLDA server 182 can be configured to have multiple “virtual servers” running within each physical server, with separate instances of an RCLDA installed within each “virtual” configured segment of memory of the each server, and running therein, again for access and use by a customer through a client 150′ or other computer systems, through a firewall 128′ and/or through a Front End RCLDA server 180. As a further alternative, a single server 182 can be used in a true application service provider (ASP) arrangement, wherein a single instance of an RCLDA can be installed in the RCLDA server 182, and running therein, again for access and use by a customer through a client 150′ or other computer systems, through a firewall 128′ and/or through a Front End RCLDA server 180. Server and application installation, including such tasks as login procedure techniques and data separation techniques would need to be configured differently, depending on the particular server and application arrangement chosen from the above alternatives, as one of ordinary skill in the art would understand. For example, in an ASP environment, data and tables for data would need to have at least one additional header, such as a facility or institution header, to differentiate each piece of data as belonging to a particular institution. In the other configurations, this additional header or data identifier would not be needed, as once a customer logged into their separate “server”, either physical and/or virtual server, all data related to the RCLDA installed and running therein would be for such particular facility and/or institution. Other configuration differences necessary for each type of installation of RCLDAs would understood by one of ordinary skill in the art, including the configuration of the RCLDA database(s) 184. Each remote configuration library development application (RCLDA) can have similar functionality as existing HOSPIRA MEDNET application functionality, provided by HOSPIRA, INC., the assignee of the present invention. In one embodiment, each “HOSPIRA MEDNET” server can run SQL SERVER software for database creation, having similar database tables as described herein, from client sites throughout the country or the world, via the Internet 1524, as provided above. In a virtual server configuration using VMware's ESX Server, each physical server mentioned above can be configured to run at least six virtual HOSPIRA MEDNET/SQL servers on each physical server.
As provided in one or more of the above and below-referenced patents and/or patent applications, MMUs be used to configure the medical devices, such as medication delivery pumps, as well as store activity information regarding the activity of each of the medical devices. The activity information can be stored in memory within each medication device and/or within the MMUs and/or within a central institution and/or facility information system. The MMU console can also be used to generate reports and control the distribution of the configuration information with the medical devices. Different facility clinical care areas exist within a hospital facility or institution, and each area can have different configuration information, such as drug libraries, for downloading into each of the medical devices within each clinical care area. A configuration information or drug library editor (DLE) deployed as a part of the MMU, its console, or on a separate computer, enables the institution and/or facility user to import, export and edit configuration information, such as whole drug libraries and individual configuration library values, to control and customize a set of configuration information, such as a drug library, according to hospital preferences and clinical care area preferences. Other features, functions and advantages of medication delivery systems and MMUs are shown and described in U.S. patent application Ser. Nos. 10/930,358; 10/783,573; and 10/783,877 which are hereby incorporated by reference herein in their entirety and are commonly owned along with the present invention.
As provided above, DLEs and associated software necessary for creating, editing, developing, and/or maintaining configuration libraries, such as drug libraries, can be implemented in a remote environment as RCLDAs running on a remote server(s) 182, as shown in
As provided above herein, and as provided within referred to patents and applications identified herein, MMUs and HOSPIRA MEDNET applications can be implemented locally at institutions, within remote institution data centers, and/or within remote vendor data centers 120′. In all of these potential implementations, the MMUs and HOSPIRA MEDNET applications are configured to gather, track, and store various configuration information and/or activity information. Referring to
In one embodiment, the central vendor/provider computer system 120, 120′ can include an FTP server 124, 124′ for receiving the configuration information/activity information from each customer institution/facility server 108, 108′ therein. In the embodiment of
The central vendor/provider computer system or vendor data center 120, 120′ can also have a configuration/activity information access server and/or cluster 136, 136′ in communication with the configuration/activity information aggregation server 132, 132′, for receiving aggregated configuration information/activity information, and for storing the aggregated configuration information/activity information within a multi-institutional configuration/activity information memory or central configuration/activity data repository 140, 140′. The repository or memory 140, 140′ can be configured as a relational database for use by customer institutions/facilities, as will be described in greater detail below. A configuration/activity information application or central reporting application can reside and execute on the configuration/activity application server 136, 136′ or web access server 160, 160′ for allowing a customer access to the aggregated configuration information/activity information stored in the multi-institutional configuration/activity information repository 140, 140′. It should be understood that the multi-institutional configuration/activity information repository 140. 140′ can be a single storage device 140, 140′, such as a hard drive, or multiple storage devices 140, 140′. When the multiple storage devices 140, 140′ are utilized, the information contained therein can be separated out into the separate storage devices 140, 140′, such as one storage device 140, 140′ comprising configuration information and another storage device comprising activity information. As described herein below, a BENCHMARKING software application, which in one embodiment is a part of the configuration/activity information application, and associated activity information, including analysis, reporting and/or other activity information can be provided. Likewise, an RXRULES software application, which is also known as HOSPIRA MEDNETMEDS, which in one embodiment is a part of the configuration/activity information application, and associated configuration information, including analysis, reporting, and other configuration information can be provided. In one embodiment, the activity information, including analysis, reporting and/or other activity information can be stored in one storage device 140, 140′ and the configuration information, including analysis, reporting, and other configuration information can be stored in another, separate, storage device 140, 140′. Preferably, the configuration/activity information application will reside on the web access server 160, 160′.
The configuration/activity information application can include a database engine, such as SQL SERVER, for storing the configuration information/activity information in a relational structure within the repository 140, 140′, and for use in responding to data requests for the relationally stored configuration information activity information. The central vendor/provider computer system 120, 120′ can also have a web access server 160, 160′ and a second firewall computer and/or second firewall application 170, 170′ to receive requests and respond to requests from the customer institution/facility client computer 150, 150′ to obtain access to the multi-institutional configuration/activity information repository 140, 140′ and aggregated configuration information/activity information stored therein. The configuration/activity information application can also include a web user interface portion for generating interface screen displays, such as shown in
Specifically, with reference again to
Aggregation may still be necessary in a remote vendor data center 120′ environment when a separate physical or virtual server is used for each institution/facility. In a pure ASP environment described herein, when implemented in a the RHCS 182, if appropriate database tables are implemented similar to the database tables described herein, configuration/activity information aggregation can be extracted or called directly from the RHCS 182 and associated RHCS database 184 into the configuration/activity information access server 136′, for use by a customer through a client computer 150′ in a similar manner as described with respect to a customer using the remote customer client computer 150 described herein with respect to
These remotely hosted vendor data center 120′ embodiments can also be implemented with the embodiment of
When a customer institution/facility user is interested in obtaining access to the aggregated configuration information/activity information stored in the repository 140, 140′, the user can access the web interface screen displays of the configuration/activity information application through the remote customer client computers 150, 150′. The web access server 160, 160′ is in communication with configuration/activity information access or database server 136, 136′, to receive and respond to requests from the remote institution client computer 150′, 150′ through which the configuration/activity information application can be utilized by the customer institution/facility user. Thus, in one embodiment, the configuration/activity application is a web application that is used to provide an online monitoring/reporting service for at least viewing and reporting on existing institutions and their respective configuration information/activity information for medical devices, such as for medication delivery pumps used within such institutions/facilities. The central vendor/provider computer system or data center 120, 120′ and configuration/activity application therein can be hosted by an actual vendor of the medical devices, such as medication delivery pumps and/or medication delivery systems and/or portions thereof, to the customer institutions and facilities therein. Alternatively, the vendor/provider computer system 120, 120′ and configuration/activity application therein can be hosted by a third party application service provider.
The multi-institutional medical device/medication delivery pump configuration information and/or activity information gathering, comparing and reporting system 100, 100′ and the applications therein, can be implemented in software, firmware, hardware, or a combination thereof. In one mode, the multi-institutional medication delivery pump configuration information and/or activity information gathering, comparing and reporting system 100, 100′ is implemented in software, as one or more executable programs or applications, and is executed by one or more special or general purpose digital computer(s), such as a personal computer (PC; IBM-compatible, APPLE-compatible, or otherwise), personal digital assistant, workstation, minicomputer, server, and/or mainframe computer. Therefore, the centralized computers 124, 124′, 128, 128′, 132, 132′, 136136′, 160, 160′, 170, 170′, 180, and 182 of the central vendor/provider computer system or data center 120, 120′, as well as the remote computers 108, 108′, 150, and 150′ of each customer institution, may be representative of any computers in which the applications of the multi-institutional configuration information and/or activity information gathering, comparing and reporting system 100, 100′, and/or central vendor/provider computer system 120, 120′, resides or partially resides.
Generally, in terms of hardware architecture, as shown in
The processors are hardware devices for executing software, particularly software stored in memory. The processors can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the computers 124, 124′, 128, 128′, 132, 132′, 136′, 160, 160′, 170, 170′, 180, and 182 of the central vendor/provider computer system 120, 120′, as well as the remote computers 108, 108′, 150, and 150′, a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, or generally any device for executing software instructions. Examples of suitable commercially available microprocessors are as follows: a PA-RISC series microprocessor from Hewlett-Packard Company, an 80×86 or Pentium series microprocessor from Intel Corporation, a PowerPC microprocessor from IBM, a Sparc microprocessor from Sun Microsystems, Inc., or a 68xxx series microprocessor from Motorola Corporation. The processors may also represent a distributed processing architecture such as, but not limited to, EJB, CORBA, and DCOM. In one embodiment, the FTP server 124 is a WINDOWS based server or series of servers, the configuration information/activity information aggregation server 132 is a WINDOWS based server or series of servers, the configuration information/activity information access server 136 is a WINDOWS based server or series of servers hosting MICROSOFT SQL SERVER, and the web access server 160 is a WINDOWS based server or series of servers.
Each memory of each computer 124, 124′, 128, 128′, 132, 132′, 136′, 160, 160′, 170, 170′, 180, and 182 of the central vendor/provider computer system 120, 120′ as well as the remote computers 108, 108′, 150, and 150′, as well as the multi-institutional configuration/activity information memory or central configuration/activity data repository 140, 140′ can include any one or a combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, these memories may incorporate electronic, magnetic, optical, and/or other types of storage media. The memories can have a distributed architecture where various components are situated remote from one another, but are still accessed by the processors of the computers 124, 124′, 128, 128′, 132, 132′, 136′, 160, 160′, 170, 170′, 180, and 182 of the central vendor/provider computer system 120, 120′, as well as the remote computers 108, 108′, 150, and 150′.
The software within one or more of the above referenced memories may include one or more separate programs. The separate programs comprise ordered listings of executable instructions for implementing logical functions. In the examples of
The configuration/activity information aggregation application and/or the configuration information application, and other source programs within the multi-institutional configuration information and/or activity information gathering, comparing and reporting system 100, 100′ and/or central vendor/provider computer system 120, 120′ may be a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed. When a source program, the program needs to be translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the memories, so as to operate properly in connection with the O/S. Furthermore, these applications can be written as (a) an object oriented programming language, which has classes of data and methods, or (b) a procedural programming language, which has routines, subroutines, and/or functions, for example but not limited to, VB.Net, C#, C, C++, Pascal, Basic, Fortran, Cobol, Perl, Java, and Ada. In one embodiment, the configuration/activity information aggregation application is written in VB.Net and the configuration information application is written in T-SQL.
The I/O devices referred to above may include input devices, for example input modules for PLCs, a keyboard, mouse, scanner, microphone, touch screens, interfaces for various medical devices, bar code readers, stylus, laser readers, radio-frequency device readers, etc. Furthermore, the I/O devices may also include output devices, for example but not limited to, output modules for PLCs, a printer, bar code printers, displays, etc. Finally, the I/O devices may further include devices that communicate both inputs and outputs, for instance but not limited to, a modulator/demodulator (modem; for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, and a router.
If the computers 124, 124′, 128, 128′, 132, 132′, 136′, 160, 160′, 170, 170′, 180, and 182 of the central vendor/provider computer system 120, 120′ as well as the remote computers 108, 108′, 150, and 150′, are a PC, workstation, PDA, or the like, the software in the respective memories may further include a basic input output system (BIOS) (not shown in
When the computers 124, 124′, 128, 128′, 132, 132′, 136′, 160, 160′, 170, 170′, 180, and 182 of the central vendor/provider computer system 120, 120′, as well as the remote computers 108, 108′, 150, and 150′, are in operation, the processors therein are configured to execute software stored within respective memories, to communicate data to and from memories, and to generally control operations of the computers 124, 124′, 128, 128′, 132, 132′, 136′, 160, 160′, 170, 170′, 180, and 182 of the central vendor/provider computer system 120, 120′, as well as the remote computers 108, 108′, 150, and 150′, pursuant to the software. The configuration/activity information aggregation application and the configuration information applications, and the O/S, in whole or in part, but typically the latter, are read by respective processors, perhaps buffered within the processors, and then executed.
When the multi-institutional medical device configuration information and/or activity information gathering, comparing and reporting system 100 and/or the central vendor/provider computer system 120, 120′ are implemented in software, as is shown in
In another embodiment, where the multi-institutional medical device configuration information and/or activity information gathering, comparing and reporting system 100, 100′ and/or the central vendor/provider computer system 120, 120′ are implemented in hardware, these systems can be implemented with any, or a combination of, the following technologies, which are each well known in the art: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.
In the context of medication management units (MMUs), a remote institution/facility user of the system through the client computer 150, 150′ can see at least “peer” institution pump configuration and activity information, including but not limited to “peer” institution configuration libraries such as drug libraries used in medication delivery pumps or infusers. The institutions/facilities can use this information as a setup guide for their own institutions/facilities, and/or can directly use at least portions of the configuration libraries to define the clinical care areas and configuration libraries. The central configuration/activity data repository 140 and database therein, includes many database files and/or tables for storing and recalling of configuration/activity information about the customer institutions, facilities, and infusers in each facility as well as other information.
For each such existing customer institution and/or related facilities or standalone facility, the configuration information and/or activity information is aggregated at a main server at each institution/facility. A FTP program can be installed and run on the main server at each institution/facility, and the FTP program can be adapted to gather and send the configuration information and/or activity information, to the central FTP server 124, 124′. In one embodiment, the files can be sent in a flat file format, which includes all configuration information and/or activity information residing within the institution. In particular, referring again to
Likewise, a second main server 216, or customer institution server 108 from
Likewise, a third main server 230, or customer institution server 108 from
As will be described below, institutions, such as hospitals have customer identifiers (IDs) and server identifiers (IDs), and the files which are transferred from an institution server 200, 216 to the central server 124, 124′ each can use the customer identifier and server identifier to allow the central FTP server 124, 124′ to map and associate the received files with the correct customer institution. In addition, each infuser has an infuser ID and the configuration/activity information for a particular infuser can be associated with the infuser ID. Each infuser can be tied to a location where the infuser is located and communicating. This location can be used to match with location descriptions assigned by each institution by the administrator, as will be understood from the below description. As each institution's information passes into the configuration/activity information aggregation server 132, 132′, the server 132, 132′ will match the location description of each infuser within each file that is received with the location description assigned by the administrator within the configuration information/activity information application.
As mentioned, an FTP program can be installed within the medication delivery computer at each institution and/or facility, and can run on daily or some other predetermined time interval basis to extract the configuration information and activity information in a file format, and FTP the files to the central FTP server 124, 124′. Another application on the configuration/activity information aggregation server 132, 132′ on daily or some other predetermined time interval basis receives the already FTPed configuration information and activity information files from the central FTP server 124, 124′, and pushes the aggregated configuration information and activity information, and other information into the configuration information/activity information database within repository 140, 140′. In one embodiment described in relation to
Referring to
As a part of the extraction/file transfer process, the systems 120, 120′ can be configured to include additional steps as follows: the FTP server 124, 124′, front end server 180 or other server can be configured to automatically generate a reminder, such as by sending an e-mail reminder, to remind the customer to manually upload their drug libraries from the medical devices into the customer server 108, 108′, used to extract/FTP configuration/activity data from. In some settings, this is a useful and potentially necessary action to obtain current configuration/activity information, as some “hard wired” medical devices into the network of devices must be manually controlled to cause uploads of configuration/activity information into the customer server 108, 108′ to occur. In addition, a generic names cleanup routine can be performed to make sure that generic names used within the configuration/activity information databases 108, 108′ at each institution match the generic names used within the configuration/activity information database 140, 140′. This routine can be run at each institution prior to data extraction or transfer or can be run within the central vendor/provider computer system 120, 120′. Particular rules are used to ensure that data is properly matched can be implemented, such as generic names shall not contain dosage amounts; generic names shall be in lower case; generic names shall not contain a display name. With respect to use of this generic name data cleaning functionality through central vendor/provider computer system 120, 120′, the system will attempt to match the user's configuration information, such as drug library entries to a generic entry for drugs when importing configuration information into the system 120, 120′ and/or exporting configuration information from the system 120, 120′. The system 120, 120′ can be configured to automatically identify common generic names and common generic name errors. The system can be configured to allow a user to establish a common generic name errors table for entering into such table common generic name errors for automatically mapping such errors onto the correct generic name in the automated cleaning process. During the automated cleaning process, if a generic name error cannot be found in a mapping table, then system will add or write such unfound error into an error file for later review by an administrator (vendor or customer). This and other generic name cleaning processes can be integrated into the shopping cart functionality described herein.
In one embodiment, the following file format names can be used: <customerID>_<serverID>_<timestamp>_<sequence number>_<type of file>.txt. Various checks can be done to ensure that correct files are being received by the aggregation server 132 and aggregation application therein. First, the aggregation application can make sure that the FTP server received the correct files by checking the customer ID and server ID for each file. Next, the aggregation application can make sure that no file is missed. This is accomplished on the aggregation server by extracting the sequence number stored inside the file itself, and verifying the number is in sequence. The processing will fail if any of the files come out of sequence. A central or vendor administrator at the vendor location can be provided with the ability to notify the subject institution, if needed, as will be explained below within the description of the administrator maintenance interface screens.
In one embodiment of the aggregation process, a user type table is generated to store the user types within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a user profile table is generated to store the user profiles within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a track user usage table is generated to store the history of user interaction with the system. This is stored within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a user history table is generated to store all user profile changes within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a health system detail table is generated to store a health system details within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a facility detail table is generated to store the facility detail within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a user health system facility detail table is generated to store the user/health system/facility mapping within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a user health system server detail table is generated to store the health system server detail within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a peer group master table is generated to store the peer group definitions within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a peer group type table is generated to store the peer group types within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a peer group size table is generated to store the peer group sizes within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a general parameter table is generated to store general parameters within the database 140, as will be understood from at least the administrator interface screen description below. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a “benchmark” or activity information summary table is generated to store summary results of activity information within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, an asset location table is generated to store institutional asset location information within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, an asset table is generated to store institutional asset information within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a device table is generated to store the infusers/pumps associated to a server within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, an event type table is generated to store the types of events, such as an “alarm” type of event, within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, an event log table is generated to store a log of the infuser activity within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, an event parameter data table is generated to store the parameter data for the events within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, an event parameter type table is generated to store the types of event parameters within the database 140. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a generic medication or configuration table is generated to store the generic configuration data, such as generic drug data, within the database 140. This table can be built from the input data in the configuration library. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a service line table is generated to store the service line identifiers and descriptions within the database 140. This table can also be built from the input data in the configuration library. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a clinical care area (CCA) detail table is generated to store the clinical care areas mapped to service lines within the database 140. This table can also be built from the input data in the configuration library. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a device type table is generated to store the types of devices within the database 140. This table can also be built from the input data in the configuration library. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a configuration library table is generated to store the generic drug/service line/CCA mapping of configuration libraries from each institution within the database 140. The following table provides the example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a configuration library detail parameterized table is used to store configuration library details, such as drug library details for each device type in each institution in the database 140. This table can also be built from the input data in the configuration library. The following table provides an example of some of the details of what can be stored in this table:
In one embodiment of the aggregation process, a ship to table is used to store institution ship to identifiers in database 140. The following table provides an example of some of the details of what can be stored in this table:
As mentioned above, as a part of building the above and other permanent tables from the configuration information and activity information received from each of the institutions and medication delivery systems therein, various temporary tables are also generated each time an institution sends new information. The temporary tables are updated with each of the respective data which is appropriate for the table in question, from each of the institutional configuration information, activity information and other information, one institution and/or one specific table at a time. Once all of the information from all of the institutions has been processed or aggregated into the temporary tables, permanent tables are loaded with the information from the temporary tables. In one embodiment, temporary tables are created before loading the permanent tables for at least the following permanent tables: asset, asset location, device, event log, event parameter type, event parameter data, event type, and configuration library, such as drug library.
After all the data available in the uploaded institution files are moved into the temporary tables, the aggregation application will process the uploaded institutional/facility data and update certain master tables, benchmark or activity information tables, and configuration library tables. Specifically, the following master tables are updated (if there is new information to update the tables with): infuser, infuser type, service line, and generic drug. In one embodiment, the aggregation application selects a distinct customer ID (institution) from the event log table to update the “benchmark” or activity information summary information. The existing benchmark summary information for the selected institution for a particular date will be deleted from the benchmark summary table and new details will be inserted. For each benchmark report, described below, the summary information will be calculated and will be updated in the benchmark summary table.
Referring to
From the main user screen for BENCHMARK user types, which appears after login is successful, the user can select the BENCHMARK option, and two further options can then be provided for the user to select from. Specifically, the user can be provided with a “Summary—Last Available Month” (summary activity information) option and a “Peer Group Comparison Trend” or peer group activity information. In order to view summary activity device/pump information on devices/pumps within the selected facility from within preferences interface display screen, the user can select the Summary—last available month (summary activity information) option. Once this option is selected, the user is presented with a summary screen for the entity results they desire to view, pre-loaded based on their user preferences, the user is then provided with a dropdown menu to select a device/pump type. The previously selected device/pump type from the default infuser type drop down menu 412 within the preferences interface screen display appears. However, the user can change this selection. Once the user selects the device/pump type for which the user would like to run the report, the user can select a show report button and the interface screen display similar to that which is shown in
The summary report 500 shown in
Specifically, the summary report 550 shown in
As mentioned, a BENCHMARK user type user can also be provided with a “Peer group comparison—Trend” information or peer group activity information option. This option will provide an institutional/facility user with the ability to compare device/pump activity information for their selected institution to all of the peer institutions within the selected entity's peer group. After selecting this option, the user will be provided with a summary screen display which allows the user to select a time frame drop down selection menu allowing display of summarized data by quarter, by month or some other time frame to be defined later. The user can be provided with a show report button on this screen as well. If the user selects the show report button, the user will be provided with an interface screen display similar to that which is shown in
The interface screen display shown in
Specifically, interface screen display shown in
If the configuration information/activity information application 136, 136′ determines that the amount of data received and stored in the configuration/activity information database 140, 140′ meets (greater than/greater than or equal to) the predetermined input level (such as data from five (5) institutions from an FTP process or data extraction referred to herein), then the configuration information/activity information application 136, 136′ will run the report including generating the chart for the received report preferences or parameters. In a further embodiment, instead issuing a data warning 664, even when the amount of data received and stored in the configuration/activity information database 140, 140′ meets (greater than/greater than or equal to) the predetermined input level relating to the requested preferences/parameters for the report, when the report and chart(s) is generated, a data warning 664 can be issued which indicates the number of institutions which were used to generate the information with the chart. Thus, a data warning 664 can be displayed for each chart indicating the level of data used to generate such chart. Further, when the configuration information/activity information application 136, 136′ generates each report and/or chart therein, the configuration information/activity information application 136, 136′ can also calculate statistical information, such as a “P Value”, an “R Value”, and/or a standard deviation, and display such statistical information within each report and/or proximate each chart for which such statistical information is calculated.
In the context of the data warning 664 issuing under the circumstances described herein, in the process of the configuration information/activity information application 136, 136′ determining if sufficient data has been received and stored to generate a reliable report based on the received preferences or parameters, the configuration information/activity information application 136, 136′ can also or instead, calculate statistical information and compare the statistical information to one or more predetermined minimum statistical reliability thresholds. The predetermined minimum statistical reliability thresholds can be a “P Value”, “R Value”, standard deviation, and/or some other statistical threshold, which can be set by the customer or user. If one or more of the predetermined minimum statistical reliability thresholds are not met, then the configuration information/activity information application 136, 136′ can be configured to generate a data warning 664, in the place of one or more report charts within the generated report or in addition to the chart(s) for which the predetermined minimum statistical reliability threshold has not been met. In this embodiment, the data warning 664 can include the one or more of the calculated statistical information as reasons for the warning. For example, the warning can include the following: “Warning—the P Value for the data used to generate this chart is X. Therefore, the amount of data used to generate this chart may not be reliable and this chart should not be used to make administrative decisions.” “X” can be a numerical value. Other statistical information can be presented instead of this example or in addition to this example.
Within the above and other “BENCHMARKING” interface screens and respective reports, charts and other forms of presenting the activity information provided through such interface screens from use of the configuration information/activity information application 136, 136′, such activity information is typically being provided to a customer for a customer's own institution. However, in one further embodiment, the configuration information/activity information application 136, 136′ can be configured to allow a customer to view and run reports on another institution's activity information, such as allowing a customer to run the above and other reports about another institution's activity information. The configuration information/activity information application 136, 136′ can also be configured to allow a customer to view and run reports on other details about such other institution(s), such as the number of beds, the peer group such other institution falls within, etc., to allow a customer to compare the other institution's activity information with their own. In one preferred embodiment, such other institution's identity will not be provided to the customer. In a further embodiment, the configuration information/activity information application 136, 136′ can also be configured to allow a customer to obtain this and other activity information about another institution, and to allow such a customer to compare such other institution's activity information against an the entire database of all of the institutions' activity information for the preferences requested by the customer, compare such other institution's activity information against the entire database of all of the institutions' activity information for one peer group for the preferences requested by the customer. Using this feature, a customer may be able to more readily “benchmark” the activity information, and thus their own configuration information, for their institution against the activity information, and thus the configuration information, of other institutions.
After activity information and/or configuration information is transferred from and/or extracted from institution/facility servers, and transferred to the configuration/activity information aggregation server 132, 132′, as a part of the aggregation process or after the aggregation process of the configuration/activity information from all of the institutions into the multi-institutional configuration/activity information database 140, 140′, a cleaning process can be performed by the aggregation server and/or application 132, 132′ or by the configuration/application server/application 136, 136′. This cleaning process includes removing all institution/facility identifying information which would allow a user of the configuration information/activity information application 136, 136′ to otherwise identify the name, location or other information about any of the institutions which would allow a user to determine the identity of such institution/facility for which activity information/configuration information had been included within the activity/configuration information database 140, 140′. Fake or generic institution/facility/other names and/or identifiers could be substituted for actual institution/facility/other names and/or identifiers during the cleaning process. Without such actual institution/facility identifying information, the activity/configuration information database 140, 140′ could be made available to third parties that are not an institution/facility and that are not a vendor. The vendor could lease and/or sell the “cleaned” database to such third parties for access by such third parties for allowing such third parties to run reports and perform comparisons described herein and run other reports and perform other comparisons. In one embodiment, this distribution of the “cleaned” database of configuration/activity information to third parties can be included with the leasing and/or sale of a modified version (third-party version) of the configuration information/activity information application, which would otherwise allow a third party to run the BENCHMARKING and/or RXRULES reports, and other reports. The modifications could include at least reduced administration functions, which for example would not need to include file transfer/extraction processes, settings, and interface screens to provide such settings. In one embodiment, the “cleaned” database of configuration/activity information, as well as the modified version (third-party version) of the configuration information/activity information application can be included within an RCLDA 182 or as a part of the HOSPIRA MEDNET application implemented within an institution server 108, 108′ for use by a customer to assist the customer is setting up configuration information, such as a drug library, for the customer institution, as described herein.
In addition to the reports and information that can be provided through and/or within the interface screens shown in
The configuration information/activity information application 136, 136′ can further be configured to generate a medical device button press count report in chart or other form which conveys how many times a user or caregiver presses buttons on a medical device, such as an infusion pump, when the user is programming the medical device for each set of programming actions (for one (1) programming). Like the other information for which reports can be run and information provided therein, this information is tracked and stored as a part of the activity information for each medical device. Specifically, which buttons are pressed, when such buttons are pressed, which caregiver pressed such buttons, during which programming, and other information is tracked and stored. The medical device button press count report can be run by time frame, by peer group for all users (or all peer groups), by CCA, and/or by some other preference. A comparison can then be performed for a user's information vs. all users in a CCA vs. all users in a particular peer group, and/or vs. some other preference to determine how well that user is performing. A further comparison can then be performed for a user's information vs. the number of alarms, alerts and/or errors that occurred for such programmings in relation to alarms, alerts, and/or errors that occurred for similar types of programmings by others, overall, by peer group, by CCA, and/or by some other preferences, to determine whether such user programmings are indicative a particular user being more susceptible to errors in programming. Statistical information can be calculated for each of the reports to assist in determining whether the reported information is quantitatively significant and the level of significance of such information. The configuration information/activity information application 136, 136′ can be configured to also generate other reports, such as a caregiver level report, in chart or other form, which conveys a high, low, average, and/or median number of alerts (soft limit exceeded) and/or alarm (hard limit exceeded) for medical device programmings for each caregiver level, by time frame, by peer group (or all peer groups), by CCA, and/or by some other preference. Comparisons can be performed between or against certain or all CCAs, peer groups, and/or other target groups, as is shown and described for other reports herein. This caregiver level report will allow a user to determine where training may be needed, for junior and/or more senior caregivers, broken down by CCA and other criteria mentioned above.
Certain medication when delivered through a medical device such as an infusion pump, are considered to be “high alert” medications. For example, the ISMP has designated at least the following medications as high alert medications: amiodarone, colchicine, heparin, insulin, lidocaine, magnesium sulfate, nesiritide, nitroprusside, potassium chloride, potassium phosphate, propofol, and sodium chloride (hypertonic—above 0.9% concentration). As such, the configuration information/activity information application 136, 136′ can be configured to also generate a “high alert” medications report, in chart or other form, which can convey one or more or the following information: 1) soft limit overrides for a particular, or all, high alert medication(s) as a percent of total programs (programmings) of the particular high alert medication and/or all high alert medications; 2) soft limit edits for a particular, or all, high alert medication(s) as a percent of total programs (programmings) of the particular high alert medication and/or all high alert medications; 3) hard limit overrides for a particular, or all, high alert medication(s) as a percent of total programs (programmings) of the particular high alert medication and/or all high alert medications; and 4) hard limit edits for a particular, or all, high alert medication(s) as a percent of total programs (programmings) of the particular high alert medication and/or all high alert medications. Similar to all other activity/configuration information reporting herein, high, low, average, and/or median information can be provided for the activity information. Also similar to all other activity/configuration information reporting herein, such reporting can be provided for each caregiver level, by time frame, by peer group (or all peer groups), by CCA, and/or by some other preference. Comparisons can be performed between or against certain or all CCAs, peer groups, and/or other target groups, as is shown and described for other reports herein. Further, similar to all other activity/configuration information reporting herein, statistical and other useful information can be calculated for the reported activity/configuration information, and can be used by the configuration information/activity information application 136, 136′ to further issue warnings and/or further alerts on the interface screen of the report, by email notification, or by some other electronic means, to provide warnings related to the activity/configuration information for which the calculations were performed. As explained and contemplated by the various embodiments described herein, once a customer/user runs a report herein, as an option in the reports or as provided through some other interface mechanism, the configuration information/activity information application 136, 136′ can provide the user with a “show medication library” or “show library entry(s)” icon (not shown) a listing of the drug library entries which are directly related to the results of the report. Such a “show medication library” or “show library entry(s)” icon (not shown) can be provided for each chart within a report, for the set or subset of activity/configuration information resulting from the parameters/preferences used to generate the report. For example, if a user runs a report for a particular type of infusion pump, a particular CCA, and a particular peer group and is provided with information such as is shown in one or more of
Instead of or in addition to focusing in on “high alert” ISMP medications, the configuration information/activity information application 136, 136′ can be also be configured to allow a user to enter preferences and run reports on medications which are used the most within all institutions, within peer groups, within CCAs, etc. For example, the configuration information/activity information application 136, 136′ can be also be configured to allow a user to request reporting on the “Top X” medications. The configuration information/activity information application 136, 136′ can be configured to receive a value for X, through user selection from a drop down menu or through some other interface means. Thus, if the user selects 20 for X, the configuration information/activity information application 136, 136′, similar to the “high alert” medications reporting, can be configured to generate a top medications report, in chart or other form, which can convey one or more or the following information: 1) soft limit overrides for the 20 most used medications as a percent of total programs; 2) soft limit edits for the 20 most used medications as a percent of total programs; 3) hard limit overrides for the 20 most used medications as a percent of total programs; and 4) hard limit edits for the 20 most used medications as a percent of total programs, which can be broken down and utilized in a similar manner as the “high alert” medicine reported information, including at least comparisons, calculation of additional/statistical information, and listing of directly related drug library entries for use in development of new drug libraries and/or editing existing drug libraries.
Some medical devices are arranged or built in a modular configuration. For example, some medical devices can include a central interface module having at least processor, memory, a display, soft and hard keys for a user to interface with the display and program the medical device, a communications interface, as well as software to control the operation of the central interface module and to interface and control the operation of specific purpose modules which can be included in the same housing with the central interface module, removably attached to the central interface module, connected to the central interface module, or merely in communication with the central interface module. One specific purpose module can include a first infusion line control module which acts as a single line infusion pump for infusing a fluid, such as medication, to a patient. The first infusion line control module can have its own processor, memory, software, communications interface, a display and control keys, such as hard and soft keys. Another specific purpose module can include a second infusion line control module which acts as an additional single line infusion pump for infusing a fluid, such as medication, to a patient. A third or additional infusion line control module can be in communication with, connected to or removably attached to the central interface module as well. Other types of modules can operate in conjunction with the central interface module. When this type of medical device is implemented in conjunction with the present invention, activity information and configuration information for each of the modules together, yet separately grouped, can be captured and stored at an MMU or similar server, extracting/transferred, and then aggregated into the configuration/activity information database 140, 140′. The configuration information/activity information application 136, 136′ can be configured to allow a customer/user to run reports on activity information for all second infusion line control modules and/or third infusion line control modules, etc., such as for example how often such line is used, for an institution, for all institutions, for all institutions within a peer group, for a particular CCA within all institutions or within a particular peer group, etc., as would be understood from the reporting techniques described herein. If a user obtained access to the configuration information/activity information application 136, 136′ prior to making purchasing decisions about how many second infusion line control modules, third infusion line control modules, etc. to purchase, this information could be used to assist such user in determining how many second infusion line control modules, third infusion line control modules, etc. to purchase at the outset, saving time in making such decisions, saving money in not over purchasing, and preventing a shortage of medical device equipment from occurring at some point in time in the future. The configuration information/activity information application 136, 136′ can further be configured to suggest how many second infusion line control modules, third infusion line control modules, etc., and other modules and/or medical device equipment based on this and other reports which come to mind based on the present description. Other reports are contemplated by the present description.
After a successful login, an RXRULES or configuration user type user is provided with a welcome screen shown in
From the main user screen for RxRules user types shown in
The interface screen display of
Once the above initial search parameters are selected, the user can select a “match opportunities” button 816 and the user will be provided with an interface screen display similar to that which is shown in
If the user selects the search button, the user will be provided with an interface screen display similar to that which is shown in
When an RXRULES or configuration information user type chooses the RxRules—Dosage Limits option, the user will be provided with an interface screen display similar to that which is shown in
Once the above initial search parameters are selected, the user can select a “Search” button 1221 and the user will be provided with preliminary search results table 1300. The interface screen display of
The configuration/activity information application and the interface screen display of
In addition or alternatively, the configuration/activity information application and the interface screen display of
Within the central configuration/activity database stored in the central repository 140, 140′ several institution maintenance database tables are provided for storing institution configuration information, such as health care system/facility ID, customer ID, AHA (American Hospital Association) number, HIN (Hospital Identification Number), health care system/facility name, health care system/facility address, city, state, zip code, country, phone number, e-mail address, contact name, registration date, FTP (or extraction) sequence number, peer group, number of beds in the health care system/facility, whether the health care system/facility is active, a health care system/facility server list (identification of all servers within the health care system/facility), and, if applicable, a facility list (all facilities which are a part of the health care system). When the institution maintenance interface screens are used to enter and/or modify this information, the institution maintenance database tables are respectively modified according to the administrator's key strokes. After each FTP action or other extraction to upload an institution's configuration/activity information to the central vendor computer system, the FTP or extraction sequence number is incremented to keep track of the uploads that have occurred. The bed size of a health care system is the sum of all of the beds at all of the facilities within a health care system.
In one embodiment, old configuration information and activity information database tables and data therein will not retained for more than a predetermined period of time within the configuration/activity information aggregation server 132. Old records will be archived within the aggregation server 132, 132′ and will be copied to offline storage periodically, such as onto tape or other storage media backup. The configuration information, such as the drug libraries will be deleted and reloaded fully every time for each institution and device type. One reason for using this embodiment is that typically only one configuration library is used within one device/pump, and, at most, only one configuration library, per device type, can be created and active within an institution at any time. In one embodiment, raw data within the aggregation server 132, 132′ FTP server 124, 124′ or other computer, is retained indefinitely. In other embodiments, summarized results, as provided herein, can be retained for eighteen months or indefinitely.
In a further embodiment, when the customer runs a configuration information report, such as a CCA distribution or dosage limits report within the RXRULES application described herein, the configuration information/activity information application 136, 136′ can be configured to allow a customer run a comparison, similar to BENCHMARKING comparisons described herein, of one or more of the results of the configuration report vs. configuration information from within other groupings or cumulative groupings of configuration information, and related activity information to such other configuration information. For example, referring to
It should be understood that the present set of configuration information/activity information application 136, 136′ functions, such as the BENCHMARKING and/or RXRULES functions described herein, can be utilized for configuration/activity information for other types of infusion devices, as well as for monitoring devices, ventilators, syringe pumps, and other medication delivery and/or monitoring devices.
Referring to
Referring to
If an administrator selects the server list field within the institution maintenance interface screen, an additional server list table (not shown) appears which lists all of the servers for the institution. The administrator can select an “edit” button to modify the listed servers or select an “add” button to enter new servers for the institution. Each server listing provides a server ID number, a configuration information sequence number (the number of uploads which have occurred for configuration information) and an activity information sequence number (the number of uploads which have occurred for activity information). The configuration information sequence number and the activity information sequence number are typically the same, and would be the same if the configuration information and the activity information had been uploaded together each time an FTP/extraction activity had occurred. However, in one embodiment, FTP activity, extraction or upload can occur for each type of information separately, which would likely cause the sequence numbers to be different.
If an administrator selects the facility list field within the institution maintenance interface screen, an additional facility list table (not shown, but is similar to
Referring to
If an administrator selects the users list field within the facility maintenance interface screen, an additional users list table (not shown, but is similar to
If an administrator selects the infusers list field within the facility maintenance interface screen, an additional infusers list table (not shown, but is similar to
Referring to
Referring to
Referring to
Referring to
Referring to
The administrator can also be provided with access to a user expiration report (not shown). A link or button can be provided to launch the user expiration report, which can identify the users and the respective user account information, in table format, that are set to expire in the next week or within the next month, or some other user selectable time frame. The results can be provided in a manner that will allow the administrator to select a specific user and call up the user account information for a particular user by selecting a link (on a user ID or some other location). The administrator can then extend the expiration of such user as the administrator sees fit. Of course, the vendor/provider administrator may choose to delegate or allow the institutional user rights to modify or maintain some of their own information, settings, profiles, etc.
In one embodiment of the present invention, a notification, such as by e-mail or other communication, can be provided to customer institutions and/or facilities based on an institution's pre-defined alert limits. For example, the configuration information/activity information application or other application within the central vendor or provider computer system 120, 120′ can be adapted to perform regular comparisons of activity information and/or configuration information of devices such as pumps within one institution or facility with activity information and/or configuration information of devices such as pumps within a particular peer group or other group designated by the institution and/or facility. The institution/facility can provide the configuration information/activity information application or other application with alert criteria, such that when the comparison result is out of range in relation to the alert criteria, a communication to the institution or facility can automatically be generated by the configuration information/activity information application or other application and sent to an administrator's or user's e-mail within the database 140 for the institution/facility. Thus, an institution and/or facility user can enter, store and have one or more of the applications described herein execute and/or generate medication practice alert notifications based on an institution's and/or facilities pre-defined alert limits. In one example, an institution could assign a predetermined value, such as 10% to the pre-defined alert of “percentage of edits as a percentage of total programs.” For this example, whenever the institution/facility exceeds this predetermined value (set at 10%), a notification is sent, such as by e-mail, text message, pager, etc. to inform a user, such as an administrator or pharmacist that an issue may exist with respect to the rule set(s) for the configuration library. In another example, assume a medication library has an entry for a particular medication, such as Heparin, that has an upper hard limit of a predetermined value, such as 25000 units/hr. If the predetermined value, such as 25000 units/hr. falls outside of the statistical norm or pre-defined threshold, a notification can be sent to appropriate personnel, such as an administrator or pharmacist for resolution.
The performed comparison can also be statistical analysis with peers or with other groupings. In one example, an alert can be generated if the device/pump activity information indicates that the institution/facility has a drug library utilization rate, soft limit override rate, etc. that is more than specified number of standard deviations in separation from their peers. The same principle could be applied to configuration information, such as drug library limits or other infuser configuration settings that may be contained within the configuration library or elsewhere. The administrator and/or user could establish their own specific alert criteria or the system could offer a plurality of selectable criteria in drop down menus, as one of skill in the art would understand from the present description. Alternatively, the system administrator may establish the alert criteria to be applied for all subscribers or the programming code may use predefined criteria.
In a further embodiment, and as introduced previously herein in relation to
It should be appreciated that the RCLDA and the central vendor or provider computer system 120 of
In addition, functions from each of these applications can be combined in a manner to allow for efficient reporting, benchmarking and development functions to occur on one interface display screen or closely related screens, providing for effective use of the reporting and benchmarking functions described above to be used for creating, editing, developing, and/or maintaining of configuration libraries. Specifically, as shown and described in relation to
Once the pharmacy or other institution/facility user has completed the configuration library development/changes, the library can be downloaded directly to an institution facility's medication delivery system or via an import list. Thus, a pharmacist or user at the institution/facility or elsewhere can use the remote configuration library development application to develop configuration libraries without having a medication delivery system, MMU, medical devices, medication delivery pump or other parts of a medication delivery system installed at their institution/facility. This is particularly useful when an institution/facility has purchased a medication delivery system, but it has not been installed yet or the installation has not yet been completed. While the installation is taking place, the user can begin and complete the development and creation of the configuration libraries using the remote configuration library development application, as well as using the reporting and benchmarking functions of the present invention described herein. As soon as the installation is completed, the configuration libraries, such as drug libraries, which are likely already ready for use in view of ability to use the benchmarking and/or reporting functions described herein as a part of the library development, will be ready for downloading into the medical devices, such as medication delivery pumps, for fast and efficient start-up and use of the medication delivery system, MMUs and medical devices associated therewith. Thus, configuration libraries, such as drug libraries, developed using the RCLDA 182, and residing in the RCLDA database 184 can be downloaded through the first firewall application/server 128′ and through the Front End RCLDA server 180 and into a customer server/database 108′ for use by the customer in operation of the customer institution's medication delivery system. Likewise, in the context of one embodiment of
Referring again to
In one embodiment, the user will have selected a shopping cart medications list name or file name to add items drug entries to, and will have selected one or more medication entries to add to such medications list, within the above or other interface screens, by highlighting one or more drug entries and then clicking on an “add to shopping cart” button. Once all selections have been completed, additional shopping cart functionality can be provided by selecting on a shopping cart icon or link (not shown) in the main RXRULES menu, such menu being shown in the left hand column of
In a further embodiment, as a user is creating one or more rule sets from scratch or by using existing rule sets from existing medical device configuration information in the memory 140, a user may wish to compare a proposed rule set against established rule sets that are in use in another facility or other facilities within a user's own institution or another facility and/or other facilities outside of the user's institution. A proposed rule set interface screen within the configuration/activity information application or RCLDA 182, provided for example by way of the direct link 190 between the RCLDA 182 and the configuration/activity information application 136′, can be provided to either allow a user to enter a proposed rule set or copy and paste a rule set from a configuration information library that is in the process of being developed, and use comparison functions, such as the BENCHMARKING functions described herein, to compare a proposed rule set to existing configuration and/or activity information data. For example, a user may wish to know statistically whether the proposed rule set or portion thereof, for the user's entity falls desired ranges within their peer group. In one example, the user can enter a proposed upper limit and request comparison using drop down selection menus described herein, and the system may provide an output as follows: The entered Upper Soft Limit is in the top 50th percentile of the Upper Soft Limits currently in use by other institutions and/or facilities (in your peer group/for all peer groups/for a particular CCA/for all CCAs/etc.).
In a further embodiment, the configuration/activity information application, the interface screen display of
The configuration information/activity information application 136, 136′ as well as the aggregation application 132, 132′, and other applications described herein, can be provided for use in English and other languages. In one embodiment, although the “front end” or visual interface screen aspects of the various applications can still be in English, configuration/activity information data from institutions within foreign (non-US) countries can be received and aggregated and included with the configuration/activity information database 140, 140′. Thus, when BENCHMARKING, RXRULES and other functionality described here in provided to a user/customer, such functionality can be provide results which encompass the configuration/activity information data from institutions within the foreign countries. Likewise, a country preference/parameter can be provided to allow a user to select and run reports and receive configuration/activity information from institutions only in such countries.
It should further be noted that while graphical reporting of configuration/activity information has been shown in the figures and described herein, more basic text reporting can be provided in addition to or instead of such graphical reporting.
When a user/customer at an institution is using the interface screens described herein to create and/or edit configuration information for a medication delivery system, such as a drug library for downloading into and use within medical devices, such a user may need help in performing this and other functionality provided through such interface screens. The vendor can provide a vendor telephone “hotline” to customers to talk to a vendor personnel to assist such a user in performing these and other functions. Specifically, the user can call a predetermined number provided within a user manual, through the interface screen(s), and/or through a link to a vendor website through which the user can be provided a telephone number for the “hotline.” When the user calls the “hotline” number, the vendor personnel can assist the user by logging into the user's account and viewing exactly what the user is viewing through the interface screen(s). The vendor personnel can also view exactly what actions the user is taking (movements and actions of the cursor/arrow and keystrokes) and can determine if the user is taking any incorrect actions. The vendor personnel can inform the user how to take actions, if the user is making any mistakes or asks the vendor personnel how to perform such actions. Moreover, using existing software provided by companies such as CITRIX, the vendor personnel can take over control of the user's interface screens and perform the user actions for the user, while the user watches the vendor personnel take such actions. In one embodiment, the vendor personnel can be a vendor pharmacist and the user can be a customer trying to obtain summary information, such as BENCHMARKING and/or RXRULES reports, for the configuration/activity information database 140, 140′ through the configuration information/activity information application 136, 136′. For example, the user may wish to view how other institutions within their own peer group have set up dosage limits for particular drugs. The vendor pharmacist can help the user obtain this information through the configuration information/activity information application 136, 136′, and assist the user in selecting one or more drug entries to create and/or modify the user's institution's own configuration information, such as the institution's drug library. In view of the present description, many other examples come to mind for how the vendor personnel, such as a pharmacist, can assist a user in using the various interface screens, systems, and applications described herein, through the “hotline”, with or without the vendor personnel viewing and/or taking over control of the customer's interface screens.
While the above-described embodiments of the invention were applied to medical devises such as infusion pumps, it will be understood by those skilled in the art that are medical devised that are capable of electronically reporting activity information and/or are configurable with configuration information can be sued with the system of the present invention. For example, a medical device for monitoring patient physiological or biochemical conditions, including but not limited to SpO2, capnography, EEG, EKG, blood pressure, and/or heart rate monitors, can be included in the system of the present invention. There are substantial benefits to institutions/facilities in having access to aggregated configuration information and/or activity information of monitoring devices alone or in conjunction with infusion pumps.
It should be emphasized that the above-described embodiments of the present invention are examples of implementations, and are merely set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiment(s) of the invention without substantially departing from the principles of the invention. All such modifications are intended to be included herein within the scope of this disclosure and by the following claims.
This application is a continuation of U.S. patent application Ser. No. 14/528,907, filed Oct. 30, 2014, now U.S. Pat. No. 10,242,060, which is a continuation of U.S. patent application Ser. No. 11/873,269, filed Oct. 16, 2007, which claims the benefit of priority to United States Provisional Patent Application Ser. No. 60/851,971, filed Oct. 16, 2006, and entitled “System And Method For Comparing And Utilizing Activity Information And Configuration Information From Multiple Medical Device Management Systems,” the entirety of the foregoing applications are all hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4024864 | Davies et al. | May 1977 | A |
| 4055175 | Clemens et al. | Oct 1977 | A |
| 4151845 | Clemens | May 1979 | A |
| 4213454 | Shim | Jul 1980 | A |
| 4240438 | Updike et al. | Dec 1980 | A |
| 4280494 | Cosgrove et al. | Jul 1981 | A |
| 4308866 | Jeliffe | Jan 1982 | A |
| 4370983 | Lichtenstein et al. | Feb 1983 | A |
| 4373527 | Fischell | Feb 1983 | A |
| 4392849 | Petre et al. | Jul 1983 | A |
| 4395259 | Prestele et al. | Jul 1983 | A |
| 4457751 | Rodler | Jul 1984 | A |
| 4464170 | Clemens | Aug 1984 | A |
| 4469481 | Kobayashi | Sep 1984 | A |
| 4475901 | Kraegen et al. | Oct 1984 | A |
| 4494950 | Fischell | Jan 1985 | A |
| 4498843 | Schneider et al. | Feb 1985 | A |
| 4515584 | Abe et al. | May 1985 | A |
| 4526568 | Clemens et al. | Jul 1985 | A |
| 4529401 | Leslie et al. | Jul 1985 | A |
| 4543955 | Schroeppel | Oct 1985 | A |
| 4551133 | Zegers de Beyl et al. | Nov 1985 | A |
| 4553958 | LeCocq | Nov 1985 | A |
| 4559037 | Franetzki et al. | Dec 1985 | A |
| 4613937 | Batty | Sep 1986 | A |
| 4624661 | Arimond | Nov 1986 | A |
| 4633878 | Bombardieri | Jan 1987 | A |
| 4634426 | Kamen | Jan 1987 | A |
| 4634427 | Hannula et al. | Jan 1987 | A |
| 4674652 | Aten et al. | Jun 1987 | A |
| 4676776 | Howson et al. | Jun 1987 | A |
| 4679562 | Luksha | Jul 1987 | A |
| 4685903 | Cable et al. | Aug 1987 | A |
| 4695954 | Rose | Sep 1987 | A |
| 4696671 | Epstein et al. | Sep 1987 | A |
| 4714462 | DiDomenico | Dec 1987 | A |
| 4722734 | Kolin | Feb 1988 | A |
| 4731051 | Fischell | Mar 1988 | A |
| 4741732 | Crankshaw et al. | May 1988 | A |
| 4756706 | Kerns et al. | Jul 1988 | A |
| 4776842 | Franetzki et al. | Oct 1988 | A |
| 4785969 | McLaughlin | Nov 1988 | A |
| 4803625 | Fu et al. | Feb 1989 | A |
| 4835372 | Gombrich et al. | May 1989 | A |
| 4838275 | Lee | Jun 1989 | A |
| 4838856 | Mulreany et al. | Jun 1989 | A |
| 4838857 | Strowe et al. | Jun 1989 | A |
| 4854324 | Hirschman et al. | Aug 1989 | A |
| 4857716 | Gombrich et al. | Aug 1989 | A |
| 4858154 | Anderson et al. | Aug 1989 | A |
| 4898578 | Rubalcaba, Jr. | Feb 1990 | A |
| 4908017 | Howson et al. | Mar 1990 | A |
| 4933873 | Kaufman et al. | Jun 1990 | A |
| 4943279 | Samiotes et al. | Jul 1990 | A |
| 4946439 | Eggers | Aug 1990 | A |
| 4953745 | Rowlett | Sep 1990 | A |
| 4978335 | Arthur, III | Dec 1990 | A |
| 5000739 | Kulisz et al. | Mar 1991 | A |
| 5010473 | Jacobs | Apr 1991 | A |
| 5014698 | Cohen | May 1991 | A |
| 5016172 | Dessertine | May 1991 | A |
| 5026084 | Paisfield | Jun 1991 | A |
| 5034004 | Crankshaw | Jul 1991 | A |
| 5041086 | Koenig et al. | Aug 1991 | A |
| 5058161 | Weiss | Oct 1991 | A |
| 5078683 | Sancoff et al. | Jan 1992 | A |
| 5084828 | Kaufman et al. | Jan 1992 | A |
| 5088981 | Howson et al. | Feb 1992 | A |
| 5097505 | Weiss | Mar 1992 | A |
| 5100380 | Epstein et al. | Mar 1992 | A |
| 5102392 | Sakai et al. | Apr 1992 | A |
| 5104374 | Bishko et al. | Apr 1992 | A |
| 5109850 | Blanco et al. | May 1992 | A |
| 5131816 | Brown | Jul 1992 | A |
| 5142484 | Kaufman et al. | Aug 1992 | A |
| 5153827 | Coutre et al. | Oct 1992 | A |
| 5157640 | Backner | Oct 1992 | A |
| 5161222 | Montejo et al. | Nov 1992 | A |
| 5177993 | Beckman et al. | Jan 1993 | A |
| 5181910 | Scanlon | Jan 1993 | A |
| 5190522 | Wocicki et al. | Mar 1993 | A |
| 5199439 | Zimmerman et al. | Apr 1993 | A |
| 5200891 | Kehr et al. | Apr 1993 | A |
| 5216597 | Beckers | Jun 1993 | A |
| 5221268 | Barton et al. | Jun 1993 | A |
| 5230061 | Welch | Jul 1993 | A |
| 5243982 | Möstl et al. | Sep 1993 | A |
| 5244463 | Cordner, Jr. et al. | Sep 1993 | A |
| 5249260 | Nigawara et al. | Sep 1993 | A |
| 5256156 | Kern et al. | Oct 1993 | A |
| 5256157 | Samiotes et al. | Oct 1993 | A |
| 5261702 | Mayfield | Nov 1993 | A |
| 5317506 | Coutre et al. | May 1994 | A |
| 5319355 | Russek | Jun 1994 | A |
| 5319363 | Welch et al. | Jun 1994 | A |
| 5330634 | Wong et al. | Jul 1994 | A |
| 5338157 | Blomquist | Aug 1994 | A |
| 5341476 | Lowell | Aug 1994 | A |
| 5364346 | Schrezenmeir | Nov 1994 | A |
| 5366346 | Danby | Nov 1994 | A |
| 5368562 | Blomquist et al. | Nov 1994 | A |
| 5373454 | Kanda et al. | Dec 1994 | A |
| 5376070 | Purvis et al. | Dec 1994 | A |
| 5378231 | Johnson et al. | Jan 1995 | A |
| 5389071 | Kawahara et al. | Feb 1995 | A |
| 5389078 | Zalesky et al. | Feb 1995 | A |
| 5417222 | Dempsey et al. | May 1995 | A |
| 5423748 | Uhala | Jun 1995 | A |
| 5429602 | Hauser | Jul 1995 | A |
| 5431627 | Pastrone et al. | Jul 1995 | A |
| 5432777 | Le Boudec et al. | Jul 1995 | A |
| 5445621 | Poli et al. | Aug 1995 | A |
| 5447164 | Shaya et al. | Sep 1995 | A |
| 5455851 | Chaco et al. | Oct 1995 | A |
| 5461365 | Schlager et al. | Oct 1995 | A |
| 5464392 | Epstein et al. | Nov 1995 | A |
| 5465082 | Chaco | Nov 1995 | A |
| 5485408 | Blomquist | Jan 1996 | A |
| 5486286 | Peterson et al. | Jan 1996 | A |
| 5493430 | Lu et al. | Feb 1996 | A |
| 5496273 | Pastrone et al. | Mar 1996 | A |
| 5505828 | Wong et al. | Apr 1996 | A |
| 5507288 | Bocker et al. | Apr 1996 | A |
| 5507786 | Morgan et al. | Apr 1996 | A |
| 5508499 | Ferrario | Apr 1996 | A |
| 5515713 | Saugues et al. | May 1996 | A |
| 5520637 | Pager et al. | May 1996 | A |
| 5522798 | Johnson et al. | Jun 1996 | A |
| 5547470 | Johnson et al. | Aug 1996 | A |
| 5554013 | Owens et al. | Sep 1996 | A |
| 5562615 | Nassif | Oct 1996 | A |
| 5577169 | Prezioso | Nov 1996 | A |
| 5582323 | Kurtenbach | Dec 1996 | A |
| 5582593 | Hultman | Dec 1996 | A |
| 5594786 | Chaco et al. | Jan 1997 | A |
| 5598519 | Narayanan | Jan 1997 | A |
| 5620608 | Rosa et al. | Apr 1997 | A |
| 5630710 | Tune et al. | May 1997 | A |
| 5636044 | Yuan et al. | Jun 1997 | A |
| 5643212 | Coutre et al. | Jul 1997 | A |
| 5651775 | Walker et al. | Jul 1997 | A |
| 5658131 | Aoki et al. | Aug 1997 | A |
| 5658250 | Blomquist et al. | Aug 1997 | A |
| 5665065 | Colman et al. | Sep 1997 | A |
| 5669877 | Blomquist | Sep 1997 | A |
| 5672154 | Sillén et al. | Sep 1997 | A |
| 5681285 | Ford et al. | Oct 1997 | A |
| 5685844 | Marttila | Nov 1997 | A |
| 5687717 | Halpern et al. | Nov 1997 | A |
| 5689229 | Chaco et al. | Nov 1997 | A |
| 5697899 | Hillman et al. | Dec 1997 | A |
| 5699509 | Gary et al. | Dec 1997 | A |
| 5713856 | Eggers et al. | Feb 1998 | A |
| 5718562 | Lawless et al. | Feb 1998 | A |
| 5719761 | Gatti et al. | Feb 1998 | A |
| 5733259 | Valcke et al. | Mar 1998 | A |
| 5738102 | Lemelson | Apr 1998 | A |
| 5744027 | Connell et al. | Apr 1998 | A |
| 5752621 | Passamante | May 1998 | A |
| 5754111 | Garcia | May 1998 | A |
| 5764034 | Bowman et al. | Jun 1998 | A |
| 5764159 | Neftel et al. | Jun 1998 | A |
| 5772635 | Dastur et al. | Jun 1998 | A |
| 5774865 | Glynn | Jun 1998 | A |
| 5778256 | Darbee | Jul 1998 | A |
| 5778345 | McCartney | Jul 1998 | A |
| 5781442 | Engleson et al. | Jul 1998 | A |
| 5782805 | Meinzer et al. | Jul 1998 | A |
| 5788669 | Peterson | Aug 1998 | A |
| 5797515 | Liff et al. | Aug 1998 | A |
| 5800387 | Duffy et al. | Sep 1998 | A |
| 5814015 | Gargano et al. | Sep 1998 | A |
| 5822544 | Chaco et al. | Oct 1998 | A |
| 5822715 | Worthington et al. | Oct 1998 | A |
| 5827179 | Lichter et al. | Oct 1998 | A |
| 5832448 | Brown | Nov 1998 | A |
| 5836910 | Duffy et al. | Nov 1998 | A |
| 5850344 | Conkright | Dec 1998 | A |
| 5867821 | Ballantyne et al. | Feb 1999 | A |
| 5870733 | Bass et al. | Feb 1999 | A |
| 5871465 | Vasko | Feb 1999 | A |
| 5873731 | Predergast | Feb 1999 | A |
| 5885245 | Lynch et al. | Mar 1999 | A |
| 5897493 | Brown | Apr 1999 | A |
| 5897498 | Canfield, II et al. | Apr 1999 | A |
| 5910252 | Truitt et al. | Jun 1999 | A |
| 5912818 | McGrady et al. | Jun 1999 | A |
| 5915240 | Karpf | Jun 1999 | A |
| 5920054 | Uber, III | Jul 1999 | A |
| 5920263 | Huttenhoff et al. | Jul 1999 | A |
| 5924074 | Evans | Jul 1999 | A |
| 5931764 | Freeman et al. | Aug 1999 | A |
| 5935099 | Peterson et al. | Aug 1999 | A |
| 5935106 | Olsen | Aug 1999 | A |
| 5941846 | Duffy et al. | Aug 1999 | A |
| 5956501 | Brown | Sep 1999 | A |
| 5957885 | Bollish et al. | Sep 1999 | A |
| 5960085 | de la Huerga | Sep 1999 | A |
| 5961448 | Swenson et al. | Oct 1999 | A |
| 5967559 | Abramowitz | Oct 1999 | A |
| 5971594 | Sahai et al. | Oct 1999 | A |
| 5975081 | Hood et al. | Nov 1999 | A |
| 5990838 | Burns et al. | Nov 1999 | A |
| 5997476 | Brown | Dec 1999 | A |
| 6000828 | Leet | Dec 1999 | A |
| 6003006 | Colella et al. | Dec 1999 | A |
| 6012034 | Hamparian et al. | Jan 2000 | A |
| 6017318 | Gauthier et al. | Jan 2000 | A |
| 6021392 | Lester et al. | Feb 2000 | A |
| 6024539 | Blomquist | Feb 2000 | A |
| 6032155 | de la Huerga | Feb 2000 | A |
| 6032676 | Moore | Mar 2000 | A |
| 6039251 | Holowko et al. | Mar 2000 | A |
| 6073106 | Rozen et al. | Jun 2000 | A |
| 6104295 | Gaisser et al. | Aug 2000 | A |
| 6112182 | Akers et al. | Aug 2000 | A |
| RE36871 | Epstein et al. | Sep 2000 | E |
| 6115390 | Chuah | Sep 2000 | A |
| 6122536 | Sun et al. | Sep 2000 | A |
| 6126637 | Kriesel et al. | Oct 2000 | A |
| 6135949 | Russo et al. | Oct 2000 | A |
| 6150942 | O'Brien | Nov 2000 | A |
| 6151643 | Cheng et al. | Nov 2000 | A |
| 6157914 | Seto et al. | Dec 2000 | A |
| 6159147 | Lichter et al. | Dec 2000 | A |
| 6167567 | Chiles et al. | Dec 2000 | A |
| 6182667 | Hanks et al. | Feb 2001 | B1 |
| 6189105 | Lopes | Feb 2001 | B1 |
| 6195589 | Ketcham | Feb 2001 | B1 |
| 6208974 | Campbell et al. | Mar 2001 | B1 |
| 6222323 | Yamashita et al. | Apr 2001 | B1 |
| 6223440 | Rashman | May 2001 | B1 |
| 6226277 | Chuah | May 2001 | B1 |
| 6227371 | Song | May 2001 | B1 |
| 6234176 | Domae et al. | May 2001 | B1 |
| 6241704 | Peterson et al. | Jun 2001 | B1 |
| 6248067 | Causey, III et al. | Jun 2001 | B1 |
| 6249705 | Snell | Jun 2001 | B1 |
| 6257265 | Brunner et al. | Jul 2001 | B1 |
| 6259355 | Chaco et al. | Jul 2001 | B1 |
| 6269340 | Ford et al. | Jul 2001 | B1 |
| 6270455 | Brown | Aug 2001 | B1 |
| 6271813 | Palalau | Aug 2001 | B1 |
| 6277072 | Bardy | Aug 2001 | B1 |
| 6280380 | Bardy | Aug 2001 | B1 |
| 6283761 | Joao | Sep 2001 | B1 |
| 6285665 | Chuah | Sep 2001 | B1 |
| 6292860 | Cochcroft, Jr. | Sep 2001 | B1 |
| 6312378 | Bardy | Nov 2001 | B1 |
| 6327254 | Chuah | Dec 2001 | B1 |
| 6330008 | Razdow et al. | Dec 2001 | B1 |
| 6339718 | Zatezalo et al. | Jan 2002 | B1 |
| 6346886 | de la Huerga | Feb 2002 | B1 |
| 6363282 | Nichols et al. | Mar 2002 | B1 |
| 6371719 | Hildebrandt | Apr 2002 | B1 |
| 6377548 | Chuah | Apr 2002 | B1 |
| 6388951 | Matsumoto et al. | May 2002 | B1 |
| 6406426 | Reuss et al. | Jun 2002 | B1 |
| 6408330 | de la Huerga | Jun 2002 | B1 |
| 6418334 | Unger et al. | Jul 2002 | B1 |
| 6427088 | Bowman et al. | Jul 2002 | B1 |
| 6428483 | Carlebach | Aug 2002 | B1 |
| 6442432 | Lee | Aug 2002 | B2 |
| 6469991 | Chuah | Oct 2002 | B1 |
| 6475180 | Peterson et al. | Nov 2002 | B2 |
| 6482158 | Mault | Nov 2002 | B2 |
| 6485418 | Yasushi et al. | Nov 2002 | B2 |
| 6494694 | Lawless et al. | Dec 2002 | B2 |
| 6494831 | Koritzinsky | Dec 2002 | B1 |
| 6497680 | Holst et al. | Dec 2002 | B1 |
| 6514460 | Fendrock | Feb 2003 | B1 |
| 6517482 | Eiden et al. | Feb 2003 | B1 |
| 6519569 | White et al. | Feb 2003 | B1 |
| 6520930 | Critchlow et al. | Feb 2003 | B2 |
| 6540672 | Simonsen et al. | Apr 2003 | B1 |
| 6542902 | Dulong et al. | Apr 2003 | B2 |
| 6544212 | Galley et al. | Apr 2003 | B2 |
| 6544228 | Heitmeier | Apr 2003 | B1 |
| 6546350 | Hartmann et al. | Apr 2003 | B1 |
| 6551276 | Mann et al. | Apr 2003 | B1 |
| 6554798 | Mann et al. | Apr 2003 | B1 |
| 6558320 | Causey et al. | May 2003 | B1 |
| 6558351 | Steil et al. | May 2003 | B1 |
| 6565509 | Say et al. | May 2003 | B1 |
| 6567416 | Chuah | May 2003 | B1 |
| 6571294 | Simmon et al. | May 2003 | B2 |
| 6572542 | Houben et al. | Jun 2003 | B1 |
| 6572545 | Knobbe et al. | Jun 2003 | B2 |
| 6578002 | Derzay et al. | Jun 2003 | B1 |
| 6581117 | Klein et al. | Jun 2003 | B1 |
| 6587034 | Heiman et al. | Jul 2003 | B1 |
| 6589229 | Connelly et al. | Jul 2003 | B1 |
| 6599281 | Struys et al. | Jul 2003 | B1 |
| 6602191 | Quy | Aug 2003 | B2 |
| 6605072 | Struys et al. | Aug 2003 | B2 |
| 6628809 | Rowe et al. | Sep 2003 | B1 |
| 6631353 | Davis et al. | Oct 2003 | B1 |
| 6640246 | Gardy, Jr. et al. | Oct 2003 | B1 |
| 6641533 | Causey, III et al. | Nov 2003 | B2 |
| 6647299 | Bourget | Nov 2003 | B2 |
| 6652455 | Kocher | Nov 2003 | B1 |
| 6653937 | Nelson et al. | Nov 2003 | B2 |
| 6659947 | Carter et al. | Dec 2003 | B1 |
| 6669630 | Joliat et al. | Dec 2003 | B1 |
| 6671563 | Engleson et al. | Dec 2003 | B1 |
| 6673033 | Sciulli et al. | Jan 2004 | B1 |
| 6674403 | Gray et al. | Jan 2004 | B2 |
| 6681003 | Linder et al. | Jan 2004 | B2 |
| 6689091 | Bui et al. | Feb 2004 | B2 |
| 6692241 | Watanabe et al. | Feb 2004 | B2 |
| 6694191 | Starkweather et al. | Feb 2004 | B2 |
| 6694334 | DuLong et al. | Feb 2004 | B2 |
| 6721286 | Williams et al. | Apr 2004 | B1 |
| 6721582 | Trepagnier et al. | Apr 2004 | B2 |
| 6725200 | Rost | Apr 2004 | B1 |
| 6731989 | Engleson et al. | May 2004 | B2 |
| 6740072 | Starkweather et al. | May 2004 | B2 |
| 6751651 | Crockett | Jun 2004 | B2 |
| 6752787 | Causey, III et al. | Jun 2004 | B1 |
| 6753830 | Gelbman | Jun 2004 | B2 |
| 6758810 | Lebel et al. | Jul 2004 | B2 |
| 6773396 | Flach et al. | Aug 2004 | B2 |
| 6774786 | Havekost et al. | Aug 2004 | B1 |
| 6775577 | Cmkovich et al. | Aug 2004 | B2 |
| 6780156 | Haueter et al. | Aug 2004 | B2 |
| 6790198 | White et al. | Sep 2004 | B1 |
| 6796956 | Hartlaub et al. | Sep 2004 | B2 |
| 6799149 | Hartlaub | Sep 2004 | B2 |
| 6809653 | Mann et al. | Oct 2004 | B1 |
| 6811534 | Bowman, IV et al. | Nov 2004 | B2 |
| 6816605 | Rowe et al. | Nov 2004 | B2 |
| 6839753 | Biondi et al. | Jan 2005 | B2 |
| 6852104 | Blomquist | Feb 2005 | B2 |
| 6859134 | Heiman et al. | Feb 2005 | B1 |
| 6871211 | Labounty et al. | Mar 2005 | B2 |
| 6873268 | Lebel et al. | Mar 2005 | B2 |
| 6876303 | Reeder et al. | Apr 2005 | B2 |
| 6885881 | Leonhardt | Apr 2005 | B2 |
| 6891525 | Ogoro | May 2005 | B2 |
| 6892278 | Ebergen | May 2005 | B2 |
| 6899695 | Herrera | May 2005 | B2 |
| 6915170 | Engleson et al. | Jul 2005 | B2 |
| 6923763 | Kovatchev et al. | Aug 2005 | B1 |
| 6924781 | Gelbman | Aug 2005 | B1 |
| 6928338 | Buchser et al. | Aug 2005 | B1 |
| 6936029 | Mann et al. | Aug 2005 | B2 |
| 6945954 | Hochman et al. | Sep 2005 | B2 |
| 6948492 | Wemeling et al. | Sep 2005 | B2 |
| 6958677 | Carter | Oct 2005 | B1 |
| 6958691 | Anderson et al. | Oct 2005 | B1 |
| 6958705 | Lebel et al. | Oct 2005 | B2 |
| 6961448 | Nichols et al. | Nov 2005 | B2 |
| 6969352 | Chiang et al. | Nov 2005 | B2 |
| 6969865 | Duchon et al. | Nov 2005 | B2 |
| 6974437 | Lebel et al. | Dec 2005 | B2 |
| 6979326 | Mann et al. | Dec 2005 | B2 |
| 6980958 | Surwit et al. | Dec 2005 | B1 |
| 6985870 | Martucci et al. | Jan 2006 | B2 |
| 6986347 | Hickle | Jan 2006 | B2 |
| 6997880 | Carlebach et al. | Feb 2006 | B2 |
| 6997920 | Mann et al. | Feb 2006 | B2 |
| 6998984 | Zittrain | Feb 2006 | B1 |
| 7017293 | Riley | Mar 2006 | B2 |
| 7025743 | Mann et al. | Apr 2006 | B2 |
| 7029455 | Flaherty | Apr 2006 | B2 |
| 7038584 | Carter | May 2006 | B2 |
| 7060031 | Webb et al. | Jun 2006 | B2 |
| 7060059 | Keith et al. | Jun 2006 | B2 |
| 7069552 | Lindberg et al. | Jun 2006 | B2 |
| 7072725 | Bristol et al. | Jul 2006 | B2 |
| 7079035 | Bock et al. | Jul 2006 | B2 |
| 7092943 | Roese et al. | Aug 2006 | B2 |
| 7096072 | Engleson et al. | Aug 2006 | B2 |
| 7099809 | Dori | Aug 2006 | B2 |
| 7103419 | Engleson et al. | Sep 2006 | B2 |
| 7103578 | Beck et al. | Sep 2006 | B2 |
| 7107106 | Engleson et al. | Sep 2006 | B2 |
| 7108680 | Rohr et al. | Sep 2006 | B2 |
| 7109878 | Mann et al. | Sep 2006 | B2 |
| 7117041 | Engleson et al. | Oct 2006 | B2 |
| 7136645 | Hanson et al. | Nov 2006 | B2 |
| 7137964 | Flaherty | Nov 2006 | B2 |
| 7142190 | Martinez | Nov 2006 | B2 |
| 7150741 | Erickson et al. | Dec 2006 | B2 |
| 7153289 | Vasko | Dec 2006 | B2 |
| 7154397 | Zerhusen et al. | Dec 2006 | B2 |
| 7156807 | Carter et al. | Jan 2007 | B2 |
| 7161484 | Tsoukalis et al. | Jan 2007 | B2 |
| 7167755 | Seeberger et al. | Jan 2007 | B2 |
| 7167920 | Traversat | Jan 2007 | B2 |
| 7171277 | Engleson et al. | Jan 2007 | B2 |
| 7171492 | Borella et al. | Jan 2007 | B1 |
| 7181493 | English et al. | Feb 2007 | B2 |
| 7185288 | McKeever | Feb 2007 | B2 |
| 7193514 | Ritson | Mar 2007 | B2 |
| 7197025 | Chuah | Mar 2007 | B2 |
| 7201734 | Hickle | Apr 2007 | B2 |
| 7204823 | Estes et al. | Apr 2007 | B2 |
| 7213009 | Pestotnik | May 2007 | B2 |
| 7216802 | de la Huerga | May 2007 | B1 |
| 7220240 | Struys et al. | May 2007 | B2 |
| 7224979 | Singhal et al. | May 2007 | B2 |
| 7229430 | Hickle et al. | Jun 2007 | B2 |
| 7230529 | Ketcherside | Jun 2007 | B2 |
| 7236936 | White et al. | Jun 2007 | B2 |
| 7238164 | Childers et al. | Jul 2007 | B2 |
| 7247154 | Hickle | Jul 2007 | B2 |
| 7248239 | Dowling | Jul 2007 | B2 |
| 7250856 | Havekost et al. | Jul 2007 | B2 |
| 7255683 | Vanderveen et al. | Aug 2007 | B2 |
| 7256888 | Staehr et al. | Aug 2007 | B2 |
| 7258534 | Fathallah et al. | Aug 2007 | B2 |
| 7263213 | Rowe | Aug 2007 | B2 |
| 7267664 | Rizzo | Sep 2007 | B2 |
| 7267665 | Steil et al. | Sep 2007 | B2 |
| 7275156 | Balfanz et al. | Sep 2007 | B2 |
| 7278983 | Ireland et al. | Oct 2007 | B2 |
| 7289815 | Gfeller et al. | Oct 2007 | B2 |
| 7289948 | Mohri | Oct 2007 | B1 |
| 7293107 | Hanson et al. | Nov 2007 | B1 |
| 7295119 | Rappaport et al. | Nov 2007 | B2 |
| 7295556 | Roese et al. | Nov 2007 | B2 |
| 7301451 | Hastings | Nov 2007 | B2 |
| 7308300 | Toews et al. | Dec 2007 | B2 |
| 7315825 | Rosenfeld et al. | Jan 2008 | B2 |
| 7319386 | Collins, Jr. et al. | Jan 2008 | B2 |
| 7324000 | Zittrain et al. | Jan 2008 | B2 |
| 7327705 | Fletcher et al. | Feb 2008 | B2 |
| 7343224 | DiGianfilippo et al. | Mar 2008 | B2 |
| 7346025 | Bryson | Mar 2008 | B2 |
| 7347836 | Peterson et al. | Mar 2008 | B2 |
| 7354420 | Steil et al. | Apr 2008 | B2 |
| 7369897 | Boveja et al. | May 2008 | B2 |
| 7369948 | Ferenczi et al. | May 2008 | B1 |
| 7383088 | Spinelli et al. | Jun 2008 | B2 |
| 7384410 | Eggers et al. | Jun 2008 | B2 |
| 7398183 | Holland et al. | Jul 2008 | B2 |
| 7398279 | Muno, Jr. et al. | Jul 2008 | B2 |
| 7399277 | Saidara et al. | Jul 2008 | B2 |
| 7402153 | Steil et al. | Jul 2008 | B2 |
| 7420472 | Tran | Sep 2008 | B2 |
| 7432807 | Schmitt | Oct 2008 | B2 |
| 7447643 | Olson | Nov 2008 | B1 |
| 7454314 | Holland et al. | Nov 2008 | B2 |
| 7457804 | Uber, III et al. | Nov 2008 | B2 |
| 7464040 | Joao | Dec 2008 | B2 |
| 7471994 | Ford et al. | Dec 2008 | B2 |
| 7483756 | Engleson et al. | Jan 2009 | B2 |
| 7489808 | Gerder | Feb 2009 | B2 |
| 7490021 | Holland et al. | Feb 2009 | B2 |
| 7490048 | Joao | Feb 2009 | B2 |
| 7491187 | Van Den Berghe et al. | Feb 2009 | B2 |
| 7519905 | Kougiouris et al. | Apr 2009 | B2 |
| 7523401 | Aldridge | Apr 2009 | B1 |
| 7524304 | Genosar | Apr 2009 | B2 |
| 7551078 | Carlson | Jun 2009 | B2 |
| 7559321 | Wermeling et al. | Jul 2009 | B2 |
| 7565197 | Haulbrich et al. | Jul 2009 | B2 |
| 7572230 | Neumann et al. | Aug 2009 | B2 |
| 7578802 | Hickle | Aug 2009 | B2 |
| 7621009 | Elhabashy | Nov 2009 | B2 |
| D606533 | De Jong et al. | Dec 2009 | S |
| 7636718 | Steen et al. | Dec 2009 | B1 |
| 7640172 | Kuth | Dec 2009 | B2 |
| 7645258 | White et al. | Jan 2010 | B2 |
| 7647237 | Malave et al. | Jan 2010 | B2 |
| 7662124 | Duchon et al. | Feb 2010 | B2 |
| 7668731 | Martucci et al. | Feb 2010 | B2 |
| 7671733 | McNeal et al. | Mar 2010 | B2 |
| 7678071 | Lebel et al. | Mar 2010 | B2 |
| 7687678 | Jacobs | Mar 2010 | B2 |
| 7697994 | VanDanacker et al. | Apr 2010 | B2 |
| 7698239 | Lieuallen | Apr 2010 | B2 |
| 7705727 | Pestotnik | Apr 2010 | B2 |
| 7724147 | Brown et al. | May 2010 | B2 |
| 7739126 | Cave | Jun 2010 | B1 |
| 7746218 | Collins, Jr. | Jun 2010 | B2 |
| 7766873 | Moberg et al. | Aug 2010 | B2 |
| 7776029 | Whitehurst et al. | Aug 2010 | B2 |
| 7776031 | Hartlaub et al. | Aug 2010 | B2 |
| 7785313 | Mastrototaro | Aug 2010 | B2 |
| 7806852 | Jurson | Oct 2010 | B1 |
| 7806886 | Kanderian, Jr. et al. | Oct 2010 | B2 |
| 7826981 | Goode, Jr. et al. | Nov 2010 | B2 |
| 7835927 | Schlotterbeck et al. | Nov 2010 | B2 |
| 7836314 | Chieu | Nov 2010 | B2 |
| 7856276 | Ripart et al. | Dec 2010 | B2 |
| 7860583 | Condurso et al. | Dec 2010 | B2 |
| 7868754 | Salvat, Jr. | Jan 2011 | B2 |
| 7871394 | Halbert et al. | Jan 2011 | B2 |
| 7886231 | Hopermann et al. | Feb 2011 | B2 |
| 7895053 | Holland et al. | Feb 2011 | B2 |
| 7896842 | Palmroos et al. | Mar 2011 | B2 |
| 7899546 | Sieracki et al. | Mar 2011 | B2 |
| 7905710 | Wang et al. | Mar 2011 | B2 |
| 7920061 | Klein et al. | Apr 2011 | B2 |
| 7933780 | de la Huerga | Apr 2011 | B2 |
| 7938796 | Moubayed | May 2011 | B2 |
| 7945452 | Fathallah et al. | May 2011 | B2 |
| 7974714 | Hoffberg | Jul 2011 | B2 |
| 7976508 | Hoag | Jul 2011 | B2 |
| 7996241 | Zak | Aug 2011 | B2 |
| 8034026 | Grant | Oct 2011 | B2 |
| 8038593 | Friedman et al. | Oct 2011 | B2 |
| 8048040 | Kiani | Nov 2011 | B2 |
| 8060576 | Chan et al. | Nov 2011 | B2 |
| 8065161 | Howard et al. | Nov 2011 | B2 |
| 8066672 | Mandro | Nov 2011 | B2 |
| 8075514 | Butterfield et al. | Dec 2011 | B2 |
| 8078983 | Davis et al. | Dec 2011 | B2 |
| 8082018 | Duchon et al. | Dec 2011 | B2 |
| 8082312 | Chan et al. | Dec 2011 | B2 |
| 8147448 | Sundar et al. | Apr 2012 | B2 |
| 8149131 | Blornquist | Apr 2012 | B2 |
| 8169914 | Bajpai | May 2012 | B2 |
| 8171094 | Chan et al. | May 2012 | B2 |
| 8172798 | Hungerford et al. | May 2012 | B2 |
| 8185322 | Schroeder et al. | May 2012 | B2 |
| 8195478 | Petersen et al. | Jun 2012 | B2 |
| 8206350 | Mann et al. | Jun 2012 | B2 |
| 8219413 | Martinez et al. | Jul 2012 | B2 |
| 8231578 | Fathallah et al. | Jul 2012 | B2 |
| 8234128 | Martucci et al. | Jul 2012 | B2 |
| 8267892 | Spencer et al. | Sep 2012 | B2 |
| 8271106 | Wehba et al. | Sep 2012 | B2 |
| 8287495 | Michaud et al. | Oct 2012 | B2 |
| 8291337 | Gannin et al. | Oct 2012 | B2 |
| 8298184 | DiPerna et al. | Oct 2012 | B2 |
| 8312272 | Serenyl et al. | Nov 2012 | B1 |
| 8352290 | Bartz et al. | Jan 2013 | B2 |
| 8359338 | Butterfield et al. | Jan 2013 | B2 |
| 8380536 | Howard et al. | Feb 2013 | B2 |
| 8387112 | Ranjan et al. | Feb 2013 | B1 |
| 8394077 | Jacobson et al. | Mar 2013 | B2 |
| 8398592 | Leibner-Druska | Mar 2013 | B2 |
| 8403908 | Jacobson et al. | Mar 2013 | B2 |
| 8435206 | Evans et al. | May 2013 | B2 |
| 8449523 | Brukalo et al. | May 2013 | B2 |
| 8452953 | Buck et al. | May 2013 | B2 |
| 8453645 | Figueiredo et al. | Jun 2013 | B2 |
| 8480648 | Burnett et al. | Jul 2013 | B2 |
| 8489427 | Simpson et al. | Jul 2013 | B2 |
| 8494879 | Davis et al. | Jul 2013 | B2 |
| 8504179 | Blomquist | Aug 2013 | B2 |
| 8517990 | Teel et al. | Aug 2013 | B2 |
| 8518021 | Stewart et al. | Aug 2013 | B2 |
| 8543416 | Palmroos et al. | Sep 2013 | B2 |
| 8551038 | Tsoukalis et al. | Oct 2013 | B2 |
| 8560345 | Wehba et al. | Oct 2013 | B2 |
| 8577692 | Silkaitis et al. | Nov 2013 | B2 |
| 8579884 | Lanier et al. | Nov 2013 | B2 |
| 8626530 | Tran et al. | Jan 2014 | B1 |
| 8655676 | Wehba et al. | Feb 2014 | B2 |
| 8660860 | Wehba et al. | Feb 2014 | B2 |
| 8662388 | Belkin | Mar 2014 | B2 |
| 8666769 | Butler et al. | Mar 2014 | B2 |
| 8700421 | Feng et al. | Apr 2014 | B2 |
| 8731960 | Butler et al. | May 2014 | B2 |
| 8768719 | Wehba et al. | Jul 2014 | B2 |
| 8771251 | Ruchti et al. | Jul 2014 | B2 |
| 8777894 | Butterfield et al. | Jul 2014 | B2 |
| 8777895 | Hsu et al. | Jul 2014 | B2 |
| 8799012 | Butler et al. | Aug 2014 | B2 |
| 8876793 | Ledford et al. | Nov 2014 | B2 |
| 8922330 | Moberg et al. | Dec 2014 | B2 |
| 8936565 | Chawla | Jan 2015 | B2 |
| 8952794 | Bloomquist et al. | Feb 2015 | B2 |
| 8998100 | Halbert et al. | Apr 2015 | B2 |
| 9026370 | Rubalcaba et al. | May 2015 | B2 |
| 9069887 | Gupta et al. | Jun 2015 | B2 |
| 9077544 | Baker et al. | Jul 2015 | B2 |
| 9089642 | Murphy et al. | Jul 2015 | B2 |
| 9114217 | Sur et al. | Aug 2015 | B2 |
| 9123077 | Silkaitis et al. | Sep 2015 | B2 |
| 9192712 | DeBelser et al. | Nov 2015 | B2 |
| 9240002 | Hume et al. | Jan 2016 | B2 |
| 9381296 | Arrizza et al. | Jul 2016 | B2 |
| 9393362 | Cozmi et al. | Jul 2016 | B2 |
| 9498583 | Sur et al. | Nov 2016 | B2 |
| 9539383 | Kohlbrecher | Jan 2017 | B2 |
| 9572923 | Howard et al. | Feb 2017 | B2 |
| 9594875 | Arrizza et al. | Mar 2017 | B2 |
| 9604000 | Wehba et al. | Mar 2017 | B2 |
| 9641432 | Jha et al. | May 2017 | B2 |
| 9649431 | Gray et al. | May 2017 | B2 |
| 9662436 | Belkin et al. | May 2017 | B2 |
| 9690909 | Stewart et al. | Jun 2017 | B2 |
| 9707341 | Dumas, III et al. | Jul 2017 | B2 |
| 9724470 | Day et al. | Aug 2017 | B2 |
| 9764082 | Day et al. | Sep 2017 | B2 |
| 9886550 | Lee et al. | Feb 2018 | B2 |
| 9943269 | Muhsin et al. | Apr 2018 | B2 |
| 9971871 | Arrizza et al. | May 2018 | B2 |
| 9995611 | Ruchti et al. | Jun 2018 | B2 |
| 10022498 | Ruchti et al. | Jul 2018 | B2 |
| 10042986 | Ruchti et al. | Aug 2018 | B2 |
| 10046112 | Oruklu et al. | Aug 2018 | B2 |
| 10166328 | Oruklu et al. | Jan 2019 | B2 |
| 10238799 | Kohlbrecher | Mar 2019 | B2 |
| 10238801 | Wehba et al. | Mar 2019 | B2 |
| 10242060 | Butler et al. | Mar 2019 | B2 |
| 10300194 | Day et al. | May 2019 | B2 |
| 10311972 | Kohlbrecher et al. | Jun 2019 | B2 |
| 10314974 | Day et al. | Jun 2019 | B2 |
| 10333843 | Jha et al. | Jun 2019 | B2 |
| 10430761 | Hume et al. | Oct 2019 | B2 |
| 10434246 | Silkaitis et al. | Oct 2019 | B2 |
| 10463788 | Day | Nov 2019 | B2 |
| 10617815 | Day et al. | Apr 2020 | B2 |
| 10646651 | Day et al. | May 2020 | B2 |
| 10692595 | Xavier et al. | Jun 2020 | B2 |
| 10741280 | Xavier et al. | Aug 2020 | B2 |
| 10757219 | Moskal | Aug 2020 | B2 |
| 10765799 | Belkin et al. | Sep 2020 | B2 |
| 10799632 | Kohlbrecher | Oct 2020 | B2 |
| 10812380 | Jha et al. | Oct 2020 | B2 |
| 10861592 | Xavier et al. | Dec 2020 | B2 |
| 10898641 | Day et al. | Jan 2021 | B2 |
| 20010016056 | Westphal et al. | Aug 2001 | A1 |
| 20010031944 | Peterson et al. | Oct 2001 | A1 |
| 20010032099 | Joao | Oct 2001 | A1 |
| 20010037060 | Thompson et al. | Nov 2001 | A1 |
| 20010044731 | Coffman et al. | Nov 2001 | A1 |
| 20010048027 | Walsh | Dec 2001 | A1 |
| 20010051787 | Haller et al. | Dec 2001 | A1 |
| 20010056358 | Dulong et al. | Dec 2001 | A1 |
| 20020010595 | Kapp | Jan 2002 | A1 |
| 20020013551 | Zaitsu et al. | Jan 2002 | A1 |
| 20020013723 | Mise | Jan 2002 | A1 |
| 20020015018 | Shimazu et al. | Feb 2002 | A1 |
| 20020019584 | Schulze et al. | Feb 2002 | A1 |
| 20020026103 | Norris et al. | Feb 2002 | A1 |
| 20020029776 | Blomquist | Mar 2002 | A1 |
| 20020032583 | Joao | Mar 2002 | A1 |
| 20020040208 | Flaherty et al. | Apr 2002 | A1 |
| 20020040282 | Bailey et al. | Apr 2002 | A1 |
| 20020082728 | Mueller et al. | Jun 2002 | A1 |
| 20020087115 | Hartlaub | Jul 2002 | A1 |
| 20020087116 | Hartlaub | Jul 2002 | A1 |
| 20020095486 | Bahl | Jul 2002 | A1 |
| 20020103675 | Vanelli | Aug 2002 | A1 |
| 20020123905 | Goodroe et al. | Sep 2002 | A1 |
| 20020143580 | Bristol et al. | Oct 2002 | A1 |
| 20020152239 | Bautista-Lloyd et al. | Oct 2002 | A1 |
| 20020173702 | Lebel et al. | Nov 2002 | A1 |
| 20020173875 | Wallace et al. | Nov 2002 | A1 |
| 20020194329 | Alling | Dec 2002 | A1 |
| 20030009244 | Engleson | Jan 2003 | A1 |
| 20030013959 | Grunwald et al. | Jan 2003 | A1 |
| 20030014222 | Klass et al. | Jan 2003 | A1 |
| 20030014817 | Gallant et al. | Jan 2003 | A1 |
| 20030025602 | Medema et al. | Feb 2003 | A1 |
| 20030028082 | Thompson | Feb 2003 | A1 |
| 20030036683 | Kehr et al. | Feb 2003 | A1 |
| 20030036744 | Struys et al. | Feb 2003 | A1 |
| 20030047126 | Tomaschko | Mar 2003 | A1 |
| 20030050621 | Lebel et al. | Mar 2003 | A1 |
| 20030059750 | Bindler et al. | Mar 2003 | A1 |
| 20030060688 | Ciarniello et al. | Mar 2003 | A1 |
| 20030069963 | Jayant et al. | Apr 2003 | A1 |
| 20030079746 | Hickle | May 2003 | A1 |
| 20030097529 | Arimilli et al. | May 2003 | A1 |
| 20030104982 | Wittmann et al. | Jun 2003 | A1 |
| 20030106553 | Vanderveen | Jun 2003 | A1 |
| 20030115358 | Yun | Jun 2003 | A1 |
| 20030120384 | Haitin et al. | Jun 2003 | A1 |
| 20030125662 | Bui | Jul 2003 | A1 |
| 20030130616 | Steil | Jul 2003 | A1 |
| 20030135087 | Hickle et al. | Jul 2003 | A1 |
| 20030139701 | White et al. | Jul 2003 | A1 |
| 20030140928 | Bui et al. | Jul 2003 | A1 |
| 20030140929 | Wilkes et al. | Jul 2003 | A1 |
| 20030141981 | Bui et al. | Jul 2003 | A1 |
| 20030143746 | Sage, Jr. | Jul 2003 | A1 |
| 20030144878 | Wilkes et al. | Jul 2003 | A1 |
| 20030158749 | Olchanski et al. | Aug 2003 | A1 |
| 20030187338 | Say et al. | Oct 2003 | A1 |
| 20030200116 | Forrester | Oct 2003 | A1 |
| 20030204416 | Acharya | Oct 2003 | A1 |
| 20030204781 | Peebles et al. | Oct 2003 | A1 |
| 20030212364 | Mann et al. | Nov 2003 | A1 |
| 20030212379 | Bylund et al. | Nov 2003 | A1 |
| 20030212821 | Gillies et al. | Nov 2003 | A1 |
| 20030217962 | Childers et al. | Nov 2003 | A1 |
| 20040015132 | Brown | Jan 2004 | A1 |
| 20040019607 | Moubayed et al. | Jan 2004 | A1 |
| 20040030323 | Ullestad et al. | Feb 2004 | A1 |
| 20040039257 | Hickle | Feb 2004 | A1 |
| 20040057226 | Berthou et al. | Mar 2004 | A1 |
| 20040064341 | Langan et al. | Apr 2004 | A1 |
| 20040064342 | Browne et al. | Apr 2004 | A1 |
| 20040064435 | Moubayed et al. | Apr 2004 | A1 |
| 20040073811 | Sanin | Apr 2004 | A1 |
| 20040077934 | Massad | Apr 2004 | A1 |
| 20040078231 | Wilkes et al. | Apr 2004 | A1 |
| 20040078236 | Stoodley et al. | Apr 2004 | A1 |
| 20040104271 | Martucci et al. | Jun 2004 | A1 |
| 20040122530 | Hansen | Jun 2004 | A1 |
| 20040128162 | Schlotterbeck et al. | Jul 2004 | A1 |
| 20040128163 | Goodman et al. | Jul 2004 | A1 |
| 20040133441 | Brady et al. | Jul 2004 | A1 |
| 20040139004 | Cohen et al. | Jul 2004 | A1 |
| 20040145480 | Despotis | Jul 2004 | A1 |
| 20040147034 | Gore et al. | Jul 2004 | A1 |
| 20040167464 | Ireland et al. | Aug 2004 | A1 |
| 20040167465 | Kohler | Aug 2004 | A1 |
| 20040167804 | Simpson | Aug 2004 | A1 |
| 20040172222 | Simpson et al. | Sep 2004 | A1 |
| 20040172283 | Vanderveen | Sep 2004 | A1 |
| 20040172301 | Mihai et al. | Sep 2004 | A1 |
| 20040172302 | Martucci et al. | Sep 2004 | A1 |
| 20040176667 | Mihai et al. | Sep 2004 | A1 |
| 20040176980 | Bulitta et al. | Sep 2004 | A1 |
| 20040176984 | White et al. | Sep 2004 | A1 |
| 20040181314 | Zaleski | Sep 2004 | A1 |
| 20040189708 | Larcheveque et al. | Sep 2004 | A1 |
| 20040193325 | Bonderud | Sep 2004 | A1 |
| 20040193328 | Butterfield et al. | Sep 2004 | A1 |
| 20040193453 | Butterfield et al. | Sep 2004 | A1 |
| 20040204673 | Flaherty et al. | Oct 2004 | A1 |
| 20040215278 | Stegink et al. | Oct 2004 | A1 |
| 20040220517 | Starkweather et al. | Nov 2004 | A1 |
| 20040225252 | Gillespie et al. | Nov 2004 | A1 |
| 20040236240 | Kraus et al. | Nov 2004 | A1 |
| 20040243438 | Mintz | Dec 2004 | A1 |
| 20040254434 | Goodnow et al. | Dec 2004 | A1 |
| 20050010269 | Lebel et al. | Jan 2005 | A1 |
| 20050020886 | Hutchinson et al. | Jan 2005 | A1 |
| 20050021006 | Tonnies | Jan 2005 | A1 |
| 20050027560 | Cook | Feb 2005 | A1 |
| 20050027567 | Taha | Feb 2005 | A1 |
| 20050038311 | Kuth | Feb 2005 | A1 |
| 20050038669 | Sachdeva et al. | Feb 2005 | A1 |
| 20050038680 | McMahon | Feb 2005 | A1 |
| 20050040226 | Al-Sheikh | Feb 2005 | A1 |
| 20050043620 | Fallows et al. | Feb 2005 | A1 |
| 20050049910 | Lancaster et al. | Mar 2005 | A1 |
| 20050055242 | Bello et al. | Mar 2005 | A1 |
| 20050055244 | Mullan et al. | Mar 2005 | A1 |
| 20050065465 | Lebel et al. | Mar 2005 | A1 |
| 20050065817 | Mihai et al. | Mar 2005 | A1 |
| 20050075544 | Shapiro et al. | Apr 2005 | A1 |
| 20050080801 | Kothandaraman et al. | Apr 2005 | A1 |
| 20050086071 | Fox, Jr. et al. | Apr 2005 | A1 |
| 20050086072 | Fox | Apr 2005 | A1 |
| 20050090808 | Malave et al. | Apr 2005 | A1 |
| 20050099624 | Staehr | May 2005 | A1 |
| 20050102162 | Blumenfeld | May 2005 | A1 |
| 20050102165 | Oshita et al. | May 2005 | A1 |
| 20050102167 | Kapoor | May 2005 | A1 |
| 20050102669 | Marney et al. | May 2005 | A1 |
| 20050107923 | Vanderveen | May 2005 | A1 |
| 20050108057 | Cohen et al. | May 2005 | A1 |
| 20050117529 | Ramos-Escano | Jun 2005 | A1 |
| 20050119788 | Engleson et al. | Jun 2005 | A1 |
| 20050119914 | Batch | Jun 2005 | A1 |
| 20050131739 | Rabinowitz et al. | Jun 2005 | A1 |
| 20050135306 | McAllen et al. | Jun 2005 | A1 |
| 20050137522 | Aoki | Jun 2005 | A1 |
| 20050137573 | McLaughlin | Jun 2005 | A1 |
| 20050144043 | Holland et al. | Jun 2005 | A1 |
| 20050154769 | Eckart et al. | Jul 2005 | A1 |
| 20050160057 | Wefers et al. | Jul 2005 | A1 |
| 20050171503 | Van Den Berghe et al. | Aug 2005 | A1 |
| 20050171815 | Vanderveen | Aug 2005 | A1 |
| 20050177096 | Bollish et al. | Aug 2005 | A1 |
| 20050177395 | Blomquist | Aug 2005 | A1 |
| 20050182306 | Sloan | Aug 2005 | A1 |
| 20050182355 | Bui | Aug 2005 | A1 |
| 20050187950 | Parker | Aug 2005 | A1 |
| 20050192557 | Brauker et al. | Sep 2005 | A1 |
| 20050197554 | Polcha | Sep 2005 | A1 |
| 20050197621 | Poulsen et al. | Sep 2005 | A1 |
| 20050210037 | Wefers et al. | Sep 2005 | A1 |
| 20050216479 | Wefers et al. | Sep 2005 | A1 |
| 20050216480 | Wefers et al. | Sep 2005 | A1 |
| 20050223045 | Funahashi et al. | Oct 2005 | A1 |
| 20050224083 | Crass | Oct 2005 | A1 |
| 20050234746 | Funahashi | Oct 2005 | A1 |
| 20050240305 | Bogash et al. | Oct 2005 | A1 |
| 20050246416 | Blomquist | Nov 2005 | A1 |
| 20050251418 | Fox, Jr. et al. | Nov 2005 | A1 |
| 20050261660 | Choi | Nov 2005 | A1 |
| 20050273059 | Mernoe et al. | Dec 2005 | A1 |
| 20050273367 | Nourie et al. | Dec 2005 | A1 |
| 20050277873 | Stewart et al. | Dec 2005 | A1 |
| 20050277890 | Stewart et al. | Dec 2005 | A1 |
| 20050277911 | Stewart et al. | Dec 2005 | A1 |
| 20050278194 | Holland et al. | Dec 2005 | A1 |
| 20060004772 | Hagan et al. | Jan 2006 | A1 |
| 20060009727 | O'Mahony et al. | Jan 2006 | A1 |
| 20060009734 | Martin | Jan 2006 | A1 |
| 20060010098 | Goodnow et al. | Jan 2006 | A1 |
| 20060026205 | Butterfield et al. | Feb 2006 | A1 |
| 20060042139 | Mendes | Mar 2006 | A1 |
| 20060047270 | Shelton | Mar 2006 | A1 |
| 20060053036 | Coffman et al. | Mar 2006 | A1 |
| 20060064020 | Burnes et al. | Mar 2006 | A1 |
| 20060074633 | Mahesh et al. | Apr 2006 | A1 |
| 20060074920 | Wefers et al. | Apr 2006 | A1 |
| 20060079831 | Gilbert | Apr 2006 | A1 |
| 20060089854 | Holland et al. | Apr 2006 | A1 |
| 20060089855 | Holland et al. | Apr 2006 | A1 |
| 20060100746 | Leibner-Druska | May 2006 | A1 |
| 20060100907 | Holland et al. | May 2006 | A1 |
| 20060106649 | Eggers et al. | May 2006 | A1 |
| 20060111943 | Wu | May 2006 | A1 |
| 20060116904 | Brem | Jun 2006 | A1 |
| 20060116907 | Rhodes et al. | Jun 2006 | A1 |
| 20060122481 | Sievenpiper et al. | Jun 2006 | A1 |
| 20060122867 | Eggers et al. | Jun 2006 | A1 |
| 20060129140 | Todd et al. | Jun 2006 | A1 |
| 20060129429 | Moubayed et al. | Jun 2006 | A1 |
| 20060129434 | Smitherman et al. | Jun 2006 | A1 |
| 20060129435 | Smitherman et al. | Jun 2006 | A1 |
| 20060136266 | Tarassenko et al. | Jun 2006 | A1 |
| 20060136271 | Eggers et al. | Jun 2006 | A1 |
| 20060143051 | Eggers et al. | Jun 2006 | A1 |
| 20060173260 | Gaoni et al. | Aug 2006 | A1 |
| 20060173406 | Hayes et al. | Aug 2006 | A1 |
| 20060173715 | Wang et al. | Aug 2006 | A1 |
| 20060173927 | Beyer et al. | Aug 2006 | A1 |
| 20060190302 | Eggers et al. | Aug 2006 | A1 |
| 20060195022 | Trepagnier et al. | Aug 2006 | A1 |
| 20060200007 | Brockway et al. | Sep 2006 | A1 |
| 20060200369 | Batch et al. | Sep 2006 | A1 |
| 20060211404 | Cromp et al. | Sep 2006 | A1 |
| 20060224141 | Rush et al. | Oct 2006 | A1 |
| 20060229557 | Fathallah et al. | Oct 2006 | A1 |
| 20060229918 | Fotsch et al. | Oct 2006 | A1 |
| 20060258985 | Russell | Nov 2006 | A1 |
| 20060259327 | Hoag | Nov 2006 | A1 |
| 20060264895 | Flanders | Nov 2006 | A1 |
| 20060265186 | Holland et al. | Nov 2006 | A1 |
| 20060265246 | Hoag | Nov 2006 | A1 |
| 20060267753 | Hussey et al. | Nov 2006 | A1 |
| 20060268710 | Appanna et al. | Nov 2006 | A1 |
| 20060277206 | Bailey et al. | Dec 2006 | A1 |
| 20060287885 | Frick | Dec 2006 | A1 |
| 20070015972 | Wang et al. | Jan 2007 | A1 |
| 20070016443 | Wachman et al. | Jan 2007 | A1 |
| 20070027506 | Stender et al. | Feb 2007 | A1 |
| 20070060796 | Kim | Mar 2007 | A1 |
| 20070060870 | Tolle et al. | Mar 2007 | A1 |
| 20070060871 | Istoc | Mar 2007 | A1 |
| 20070061393 | Moore | Mar 2007 | A1 |
| 20070065363 | Dalal et al. | Mar 2007 | A1 |
| 20070073419 | Sesay | Mar 2007 | A1 |
| 20070078314 | Grounsell | Apr 2007 | A1 |
| 20070083870 | Kanakogi | Apr 2007 | A1 |
| 20070088333 | Levin et al. | Apr 2007 | A1 |
| 20070093786 | Goldsmith et al. | Apr 2007 | A1 |
| 20070100665 | Brown | May 2007 | A1 |
| 20070100667 | Bardy | May 2007 | A1 |
| 20070106126 | Mannheimer et al. | May 2007 | A1 |
| 20070112298 | Mueller et al. | May 2007 | A1 |
| 20070116037 | Moore | May 2007 | A1 |
| 20070118405 | Campbell et al. | May 2007 | A1 |
| 20070135866 | Baker | Jun 2007 | A1 |
| 20070136098 | Smythe et al. | Jun 2007 | A1 |
| 20070142822 | Remde | Jun 2007 | A1 |
| 20070156282 | Dunn | Jul 2007 | A1 |
| 20070156452 | Batch | Jul 2007 | A1 |
| 20070169008 | Varanasi et al. | Jul 2007 | A1 |
| 20070179448 | Lim et al. | Aug 2007 | A1 |
| 20070186923 | Poutiatine et al. | Aug 2007 | A1 |
| 20070191817 | Martin | Aug 2007 | A1 |
| 20070191973 | Holzbauer et al. | Aug 2007 | A1 |
| 20070213598 | Howard et al. | Sep 2007 | A1 |
| 20070213657 | Jennewine et al. | Sep 2007 | A1 |
| 20070213684 | Hickle et al. | Sep 2007 | A1 |
| 20070214003 | Holland et al. | Sep 2007 | A1 |
| 20070215545 | Bissler et al. | Sep 2007 | A1 |
| 20070229249 | McNeal et al. | Oct 2007 | A1 |
| 20070232867 | Hansmann | Oct 2007 | A1 |
| 20070233035 | Wehba et al. | Oct 2007 | A1 |
| 20070233049 | Wehba et al. | Oct 2007 | A1 |
| 20070233206 | Frikart | Oct 2007 | A1 |
| 20070233520 | Wehba et al. | Oct 2007 | A1 |
| 20070251835 | Mehta et al. | Nov 2007 | A1 |
| 20070253021 | Mehta et al. | Nov 2007 | A1 |
| 20070254593 | Jollota et al. | Nov 2007 | A1 |
| 20070255125 | Moberg et al. | Nov 2007 | A1 |
| 20070257788 | Carlson | Nov 2007 | A1 |
| 20070258395 | Jollota et al. | Nov 2007 | A1 |
| 20070299687 | Palmer et al. | Dec 2007 | A1 |
| 20070299695 | Jung et al. | Dec 2007 | A1 |
| 20080004904 | Tran | Jan 2008 | A1 |
| 20080009684 | Corsetti et al. | Jan 2008 | A1 |
| 20080033361 | Evans et al. | Feb 2008 | A1 |
| 20080033966 | Wahl | Feb 2008 | A1 |
| 20080034323 | Blomquist | Feb 2008 | A1 |
| 20080041942 | Aissa | Feb 2008 | A1 |
| 20080052704 | Wysocki | Feb 2008 | A1 |
| 20080065007 | Peterson et al. | Mar 2008 | A1 |
| 20080065417 | Jung et al. | Mar 2008 | A1 |
| 20080071217 | Moubayed et al. | Mar 2008 | A1 |
| 20080071251 | Moubayed et al. | Mar 2008 | A1 |
| 20080091466 | Butler et al. | Apr 2008 | A1 |
| 20080095339 | Elliott | Apr 2008 | A1 |
| 20080097289 | Steil et al. | Apr 2008 | A1 |
| 20080126969 | Blomquist | May 2008 | A1 |
| 20080139907 | Rao et al. | Jun 2008 | A1 |
| 20080149117 | Raghuram | Jun 2008 | A1 |
| 20080154177 | Moubayed et al. | Jun 2008 | A1 |
| 20080172337 | Banfield et al. | Jul 2008 | A1 |
| 20080184219 | Matsumoto | Jul 2008 | A1 |
| 20080188796 | Steil et al. | Aug 2008 | A1 |
| 20080200870 | Palmroos et al. | Aug 2008 | A1 |
| 20080214919 | Harmon et al. | Sep 2008 | A1 |
| 20080243055 | Fathallah et al. | Oct 2008 | A1 |
| 20080246748 | Cassidy et al. | Oct 2008 | A1 |
| 20080256305 | Kwon | Oct 2008 | A1 |
| 20080259926 | Tavares et al. | Oct 2008 | A1 |
| 20080262469 | Bristol et al. | Oct 2008 | A1 |
| 20080269714 | Mastrototaro et al. | Oct 2008 | A1 |
| 20080269723 | Mastrototaro et al. | Oct 2008 | A1 |
| 20080275384 | Mastrototaro et al. | Nov 2008 | A1 |
| 20080300572 | Rankers et al. | Dec 2008 | A1 |
| 20080320387 | Sasaki et al. | Dec 2008 | A1 |
| 20080320466 | Dias | Dec 2008 | A1 |
| 20090005703 | Fasciano | Jan 2009 | A1 |
| 20090005728 | Weinert et al. | Jan 2009 | A1 |
| 20090006061 | Thukral et al. | Jan 2009 | A1 |
| 20090006129 | Thukral | Jan 2009 | A1 |
| 20090006133 | Weinert | Jan 2009 | A1 |
| 20090018495 | Panduro | Jan 2009 | A1 |
| 20090051560 | Manning et al. | Feb 2009 | A1 |
| 20090054743 | Stewart | Feb 2009 | A1 |
| 20090054754 | McMahon et al. | Feb 2009 | A1 |
| 20090057399 | Sajkowsky | Mar 2009 | A1 |
| 20090063187 | Johnson et al. | Mar 2009 | A1 |
| 20090069785 | Miller et al. | Mar 2009 | A1 |
| 20090099867 | Newman | Apr 2009 | A1 |
| 20090135196 | Holland et al. | May 2009 | A1 |
| 20090143662 | Estes et al. | Jun 2009 | A1 |
| 20090149743 | Barron et al. | Jun 2009 | A1 |
| 20090150174 | Buck et al. | Jun 2009 | A1 |
| 20090150439 | Gejdos et al. | Jun 2009 | A1 |
| 20090150878 | Pathak et al. | Jun 2009 | A1 |
| 20090156991 | Roberts | Jun 2009 | A1 |
| 20090157695 | Roberts | Jun 2009 | A1 |
| 20090158274 | Roberts | Jun 2009 | A1 |
| 20090177146 | Nesbitt et al. | Jul 2009 | A1 |
| 20090177769 | Roberts | Jul 2009 | A1 |
| 20090177992 | Rubalcaba et al. | Jul 2009 | A1 |
| 20090183147 | Davis et al. | Jul 2009 | A1 |
| 20090209938 | Aalto-Setala | Aug 2009 | A1 |
| 20090210250 | Prax et al. | Aug 2009 | A1 |
| 20090221890 | Saffer et al. | Sep 2009 | A1 |
| 20090231249 | Wang et al. | Sep 2009 | A1 |
| 20090270833 | DeBelser | Oct 2009 | A1 |
| 20090275886 | Bloomquist et al. | Nov 2009 | A1 |
| 20090275896 | Kamen et al. | Nov 2009 | A1 |
| 20090284691 | Marhefka et al. | Nov 2009 | A1 |
| 20090292340 | Mass et al. | Nov 2009 | A1 |
| 20090326340 | Wang | Dec 2009 | A1 |
| 20090326516 | Bangera et al. | Dec 2009 | A1 |
| 20100022988 | Wochner | Jan 2010 | A1 |
| 20100036310 | Hillman | Feb 2010 | A1 |
| 20100056992 | Hayter | Mar 2010 | A1 |
| 20100095229 | Dixon et al. | Apr 2010 | A1 |
| 20100121170 | Rule | May 2010 | A1 |
| 20100121415 | Skelton et al. | May 2010 | A1 |
| 20100121654 | Portnoy et al. | May 2010 | A1 |
| 20100121752 | Banigan et al. | May 2010 | A1 |
| 20100130933 | Holland et al. | May 2010 | A1 |
| 20100131434 | Magent et al. | May 2010 | A1 |
| 20100138523 | Umess et al. | Jun 2010 | A1 |
| 20100146137 | Wu et al. | Jun 2010 | A1 |
| 20100156633 | Buck et al. | Jun 2010 | A1 |
| 20100160854 | Gauthier | Jun 2010 | A1 |
| 20100160860 | Celentano et al. | Jun 2010 | A1 |
| 20100174266 | Estes | Jul 2010 | A1 |
| 20100191525 | Rabenko et al. | Jul 2010 | A1 |
| 20100198034 | Thomas et al. | Aug 2010 | A1 |
| 20100198196 | Wei | Aug 2010 | A1 |
| 20100200506 | Ware et al. | Aug 2010 | A1 |
| 20100209268 | Davis | Aug 2010 | A1 |
| 20100212675 | Walling et al. | Aug 2010 | A1 |
| 20100217621 | Schoenberg | Aug 2010 | A1 |
| 20100234708 | Buck et al. | Sep 2010 | A1 |
| 20100250732 | Bucknell | Sep 2010 | A1 |
| 20100271479 | Heydlauf | Oct 2010 | A1 |
| 20100273738 | Valcke et al. | Oct 2010 | A1 |
| 20100274218 | Yodfat et al. | Oct 2010 | A1 |
| 20100280486 | Khair et al. | Nov 2010 | A1 |
| 20100292634 | Kircher | Nov 2010 | A1 |
| 20100298765 | Budiman et al. | Nov 2010 | A1 |
| 20100318025 | John | Dec 2010 | A1 |
| 20110001605 | Kiani et al. | Jan 2011 | A1 |
| 20110021898 | Wei et al. | Jan 2011 | A1 |
| 20110040158 | Katz et al. | Feb 2011 | A1 |
| 20110060758 | Schlotterbeck et al. | Mar 2011 | A1 |
| 20110071844 | Cannon et al. | Mar 2011 | A1 |
| 20110072379 | Gannon | Mar 2011 | A1 |
| 20110078608 | Gannon et al. | Mar 2011 | A1 |
| 20110093284 | Dicks et al. | Apr 2011 | A1 |
| 20110099313 | Bolanowski | Apr 2011 | A1 |
| 20110125095 | Lebel et al. | May 2011 | A1 |
| 20110138185 | Ju et al. | Jun 2011 | A1 |
| 20110175728 | Baker, Jr. | Jul 2011 | A1 |
| 20110178462 | Moberg et al. | Jul 2011 | A1 |
| 20110196748 | Caron et al. | Aug 2011 | A1 |
| 20110231216 | Fyke et al. | Sep 2011 | A1 |
| 20110257496 | Terashima et al. | Oct 2011 | A1 |
| 20110257798 | Ali et al. | Oct 2011 | A1 |
| 20110259954 | Bartz et al. | Oct 2011 | A1 |
| 20110264043 | Kotnick et al. | Oct 2011 | A1 |
| 20110264044 | Bartz et al. | Oct 2011 | A1 |
| 20110266221 | Ware et al. | Nov 2011 | A1 |
| 20110270045 | Lebel et al. | Nov 2011 | A1 |
| 20110275904 | Lebel et al. | Nov 2011 | A1 |
| 20110286457 | Ee | Nov 2011 | A1 |
| 20110289497 | Kiaie et al. | Nov 2011 | A1 |
| 20110295196 | Chazot et al. | Dec 2011 | A1 |
| 20110295341 | Estes et al. | Dec 2011 | A1 |
| 20110296051 | Vange | Dec 2011 | A1 |
| 20110296411 | Tang et al. | Dec 2011 | A1 |
| 20110313789 | Karmen et al. | Dec 2011 | A1 |
| 20110319813 | Kamen et al. | Dec 2011 | A1 |
| 20110320049 | Chossat et al. | Dec 2011 | A1 |
| 20120005680 | Dolby et al. | Jan 2012 | A1 |
| 20120011253 | Friedman et al. | Jan 2012 | A1 |
| 20120016305 | Jollota | Jan 2012 | A1 |
| 20120029941 | Malave et al. | Feb 2012 | A1 |
| 20120036102 | Fletcher et al. | Feb 2012 | A1 |
| 20120066501 | Xiong | Mar 2012 | A1 |
| 20120070045 | Vesper et al. | Mar 2012 | A1 |
| 20120095437 | Hemmerling | Apr 2012 | A1 |
| 20120112903 | Kaib et al. | May 2012 | A1 |
| 20120130198 | Beaule | May 2012 | A1 |
| 20120130308 | Silkaitis et al. | May 2012 | A1 |
| 20120143116 | Ware et al. | Jun 2012 | A1 |
| 20120150556 | Galasso et al. | Jun 2012 | A1 |
| 20120157920 | Flachbart et al. | Jun 2012 | A1 |
| 20120179135 | Rinehart et al. | Jul 2012 | A1 |
| 20120179136 | Rinehart et al. | Jul 2012 | A1 |
| 20120203177 | Lanier | Aug 2012 | A1 |
| 20120245554 | Kawamura | Sep 2012 | A1 |
| 20120259978 | Petersen et al. | Oct 2012 | A1 |
| 20120277716 | Ali et al. | Nov 2012 | A1 |
| 20120283630 | Lee et al. | Nov 2012 | A1 |
| 20120284734 | McQuaid et al. | Nov 2012 | A1 |
| 20120323212 | Murphy | Dec 2012 | A1 |
| 20130006666 | Schneider | Jan 2013 | A1 |
| 20130006702 | Wu | Jan 2013 | A1 |
| 20130012877 | Debelser et al. | Jan 2013 | A1 |
| 20130012879 | Debelser et al. | Jan 2013 | A1 |
| 20130012880 | Blomquist | Jan 2013 | A1 |
| 20130015980 | Evans et al. | Jan 2013 | A1 |
| 20130036403 | Geist | Feb 2013 | A1 |
| 20130036412 | Birtwhistle et al. | Feb 2013 | A1 |
| 20130066265 | Grant | Mar 2013 | A1 |
| 20130072872 | Yodfat et al. | Mar 2013 | A1 |
| 20130085689 | Sur et al. | Apr 2013 | A1 |
| 20130096444 | Condurso et al. | Apr 2013 | A1 |
| 20130096648 | Benson | Apr 2013 | A1 |
| 20130102963 | Marsh et al. | Apr 2013 | A1 |
| 20130138452 | Cork et al. | May 2013 | A1 |
| 20130144206 | Lee et al. | Jun 2013 | A1 |
| 20130150824 | Estes et al. | Jun 2013 | A1 |
| 20130158504 | Ruchti et al. | Jun 2013 | A1 |
| 20130167245 | Birtwhistle et al. | Jun 2013 | A1 |
| 20130173473 | Birtwhistle et al. | Jul 2013 | A1 |
| 20130191770 | Bartz et al. | Jul 2013 | A1 |
| 20130204188 | Kamen et al. | Aug 2013 | A1 |
| 20130218080 | Peterfreund et al. | Aug 2013 | A1 |
| 20130261993 | Ruchti et al. | Oct 2013 | A1 |
| 20130274669 | Stempfle et al. | Oct 2013 | A1 |
| 20130275539 | Gross et al. | Oct 2013 | A1 |
| 20130291116 | Homer | Oct 2013 | A1 |
| 20130296823 | Melker et al. | Nov 2013 | A1 |
| 20130296984 | Burnett et al. | Nov 2013 | A1 |
| 20130317753 | Kamen et al. | Nov 2013 | A1 |
| 20130346108 | Kamen et al. | Dec 2013 | A1 |
| 20140025392 | Chandrasenan | Jan 2014 | A1 |
| 20140039446 | Day | Feb 2014 | A1 |
| 20140163517 | Finan et al. | Jun 2014 | A1 |
| 20140180711 | Kamen et al. | Jun 2014 | A1 |
| 20140257251 | Bush et al. | Sep 2014 | A1 |
| 20140266790 | Al-Ali et al. | Sep 2014 | A1 |
| 20140266794 | Brown et al. | Sep 2014 | A1 |
| 20140269643 | Sun | Sep 2014 | A1 |
| 20140276571 | Ludolph | Sep 2014 | A1 |
| 20140288947 | Simpson et al. | Sep 2014 | A1 |
| 20140297329 | Rock | Oct 2014 | A1 |
| 20140350513 | Oruklu et al. | Nov 2014 | A1 |
| 20140358077 | Oruklu et al. | Dec 2014 | A1 |
| 20140366878 | Baron | Dec 2014 | A1 |
| 20150005935 | Bae et al. | Jan 2015 | A1 |
| 20150066531 | Jacobson et al. | Mar 2015 | A1 |
| 20150100038 | McCann et al. | Apr 2015 | A1 |
| 20150134265 | Kohlbrecher et al. | May 2015 | A1 |
| 20150141955 | Ruchti et al. | May 2015 | A1 |
| 20150151051 | Tsoukalis | Jun 2015 | A1 |
| 20150161354 | Blomquist | Jun 2015 | A1 |
| 20150199192 | Borges et al. | Jul 2015 | A1 |
| 20150230760 | Schneider | Aug 2015 | A1 |
| 20150317891 | Day et al. | Nov 2015 | A1 |
| 20150328396 | Adams et al. | Nov 2015 | A1 |
| 20150371004 | Jones | Dec 2015 | A1 |
| 20150379237 | Mills et al. | Dec 2015 | A1 |
| 20160015885 | Pananen et al. | Jan 2016 | A1 |
| 20160034655 | Gray et al. | Feb 2016 | A1 |
| 20160045661 | Gray et al. | Feb 2016 | A1 |
| 20160051749 | Istoc | Feb 2016 | A1 |
| 20160051751 | Silkaitis et al. | Feb 2016 | A1 |
| 20160103960 | Hume et al. | Apr 2016 | A1 |
| 20160228633 | Welsch et al. | Aug 2016 | A1 |
| 20160241391 | Fenster | Aug 2016 | A1 |
| 20160285876 | Perez et al. | Sep 2016 | A1 |
| 20160350513 | Jacobson et al. | Dec 2016 | A1 |
| 20170024534 | Arrizza et al. | Jan 2017 | A1 |
| 20170246388 | Kohlbrecher | Aug 2017 | A1 |
| 20170262590 | Karakosta et al. | Sep 2017 | A1 |
| 20170274140 | Howard et al. | Sep 2017 | A1 |
| 20170286637 | Arrizza et al. | Oct 2017 | A1 |
| 20170319780 | Belkin et al. | Nov 2017 | A1 |
| 20170331735 | Jha et al. | Nov 2017 | A1 |
| 20180008772 | Wehba et al. | Jan 2018 | A1 |
| 20180028742 | Day et al. | Feb 2018 | A1 |
| 20180043094 | Day et al. | Feb 2018 | A1 |
| 20180121613 | Connely, IV et al. | May 2018 | A1 |
| 20180181712 | Ensey et al. | Jun 2018 | A1 |
| 20180247712 | Muhsin et al. | Aug 2018 | A1 |
| 20180322948 | Drost et al. | Nov 2018 | A1 |
| 20190006044 | Brask | Jan 2019 | A1 |
| 20190096518 | Pace | Mar 2019 | A1 |
| 20190132196 | Trivedi et al. | May 2019 | A1 |
| 20190147998 | Ruchti et al. | May 2019 | A1 |
| 20190228863 | Dharwad et al. | Jul 2019 | A1 |
| 20190240405 | Wehba et al. | Aug 2019 | A1 |
| 20190245942 | Moskal | Aug 2019 | A1 |
| 20190311803 | Kohlbrecher et al. | Oct 2019 | A1 |
| 20190348160 | Heavelyn et al. | Nov 2019 | A1 |
| 20190392929 | Gassman | Dec 2019 | A1 |
| 20200027541 | Xavier et al. | Jan 2020 | A1 |
| 20200027543 | Xavier et al. | Jan 2020 | A1 |
| 20200027548 | Xavier et al. | Jan 2020 | A1 |
| 20200027549 | Xavier et al. | Jan 2020 | A1 |
| 20200027550 | Xavier et al. | Jan 2020 | A1 |
| 20200027551 | Xavier et al. | Jan 2020 | A1 |
| 20200028837 | Xavier et al. | Jan 2020 | A1 |
| 20200028914 | Xavier et al. | Jan 2020 | A1 |
| 20200035355 | Xavier et al. | Jan 2020 | A1 |
| 20200054825 | Kamen et al. | Feb 2020 | A1 |
| 20200206413 | Silkaitis et al. | Jul 2020 | A1 |
| 20200282139 | Susi | Sep 2020 | A1 |
| 20200306443 | Day | Oct 2020 | A1 |
| 20200330685 | Day | Oct 2020 | A1 |
| 20200335194 | Jacobson et al. | Oct 2020 | A1 |
| 20200353167 | Vivek et al. | Nov 2020 | A1 |
| 20200353168 | Keenan et al. | Nov 2020 | A1 |
| 20210050097 | Xavier et al. | Feb 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 060 151 | Aug 1997 | CA |
| 2 125 300 | Oct 1999 | CA |
| 2 898 825 | Jul 2014 | CA |
| 31 12 762 | Jan 1983 | DE |
| 34 35 647 | Jul 1985 | DE |
| 198 44 252 | Mar 2000 | DE |
| 199 32 147 | Jan 2001 | DE |
| 103 52 456 | Jul 2005 | DE |
| 0 319 267 | Jun 1989 | EP |
| 0 380 061 | Aug 1990 | EP |
| 0 384 155 | Aug 1990 | EP |
| 0 460 533 | Dec 1991 | EP |
| 0 564 127 | Jun 1993 | EP |
| 0 633 035 | Jan 1995 | EP |
| 0 652 528 | May 1995 | EP |
| 0 672 427 | Sep 1995 | EP |
| 0 683 465 | Nov 1995 | EP |
| 0 880 936 | Dec 1998 | EP |
| 1 157 711 | Nov 2001 | EP |
| 1 174 817 | Jan 2002 | EP |
| 0 664 102 | Apr 2002 | EP |
| 1 197 178 | Apr 2002 | EP |
| 0 830 775 | Aug 2002 | EP |
| 1 500 025 | Apr 2003 | EP |
| 2 113 842 | Nov 2009 | EP |
| 2 228 004 | Sep 2010 | EP |
| 2 243 506 | Oct 2010 | EP |
| 2 410 448 | Jan 2012 | EP |
| 2 742 961 | Jun 2014 | EP |
| 2 717 919 | Sep 1995 | FR |
| 2 285 135 | Jun 1995 | GB |
| 04-161139 | Jun 1992 | JP |
| 07-502678 | Mar 1995 | JP |
| 11-500643 | Jan 1999 | JP |
| 2000-316820 | Nov 2000 | JP |
| 2002-531154 | Sep 2002 | JP |
| 2003-016183 | Jan 2003 | JP |
| 2003-296173 | Oct 2003 | JP |
| 2005-021463 | Jan 2005 | JP |
| 2005-527284 | Sep 2005 | JP |
| 2005-284846 | Oct 2005 | JP |
| 2006-047319 | Feb 2006 | JP |
| 2006-520949 | Sep 2006 | JP |
| 2007-518479 | Jul 2007 | JP |
| 2007-525256 | Sep 2007 | JP |
| 2008-080036 | Apr 2008 | JP |
| 2008-516303 | May 2008 | JP |
| 2008-158622 | Jul 2008 | JP |
| 2008-529675 | Aug 2008 | JP |
| 2009-163534 | Jul 2009 | JP |
| 2010-502361 | Jan 2010 | JP |
| 2011-506048 | Mar 2011 | JP |
| 2012-011204 | Jan 2012 | JP |
| 2012-070991 | Apr 2012 | JP |
| 2012-523895 | Oct 2012 | JP |
| 2014-068283 | Apr 2014 | JP |
| WO 84001719 | May 1984 | WO |
| WO 91016416 | Oct 1991 | WO |
| WO 92010985 | Jul 1992 | WO |
| WO 92013322 | Aug 1992 | WO |
| WO 94005355 | Mar 1994 | WO |
| WO 96008755 | Mar 1996 | WO |
| WO 96025186 | Aug 1996 | WO |
| WO 98012670 | Mar 1998 | WO |
| WO 98019263 | May 1998 | WO |
| WO 99051003 | Oct 1999 | WO |
| WO 00013580 | Mar 2000 | WO |
| WO 00053243 | Sep 2000 | WO |
| WO 01014974 | Mar 2001 | WO |
| WO 01033484 | May 2001 | WO |
| WO 01045014 | Jun 2001 | WO |
| WO 02005702 | Jan 2002 | WO |
| WO 02036044 | May 2002 | WO |
| WO 02049153 | Jun 2002 | WO |
| WO 02049279 | Jun 2002 | WO |
| WO 02069099 | Sep 2002 | WO |
| WO 02081015 | Oct 2002 | WO |
| WO 02088875 | Nov 2002 | WO |
| WO 03006091 | Jan 2003 | WO |
| WO 03050917 | Jun 2003 | WO |
| WO 03091836 | Nov 2003 | WO |
| WO 03094092 | Nov 2003 | WO |
| WO 2004060455 | Jul 2004 | WO |
| WO 2004070557 | Aug 2004 | WO |
| WO 2004070562 | Aug 2004 | WO |
| WO 2004072828 | Aug 2004 | WO |
| WO 2005036447 | Apr 2005 | WO |
| WO 2005050526 | Jun 2005 | WO |
| WO 2005057175 | Jun 2005 | WO |
| WO 2005066872 | Jul 2005 | WO |
| WO 2007087443 | Aug 2007 | WO |
| WO 2007117705 | Oct 2007 | WO |
| WO 2007127879 | Nov 2007 | WO |
| WO 2007127880 | Nov 2007 | WO |
| WO 2008057729 | May 2008 | WO |
| WO 2008067245 | Jun 2008 | WO |
| WO 2008082854 | Jul 2008 | WO |
| WO 2008088490 | Jul 2008 | WO |
| WO 2008097316 | Aug 2008 | WO |
| WO 2008103915 | Aug 2008 | WO |
| WO 2008124478 | Oct 2008 | WO |
| WO 2008134146 | Nov 2008 | WO |
| WO 2009016504 | Feb 2009 | WO |
| WO 2009023406 | Feb 2009 | WO |
| WO 2009023407 | Feb 2009 | WO |
| WO 2009023634 | Feb 2009 | WO |
| WO 2009036327 | Mar 2009 | WO |
| WO 2009049252 | Apr 2009 | WO |
| WO 2010017279 | Feb 2010 | WO |
| WO 2010033919 | Mar 2010 | WO |
| WO 2010053703 | May 2010 | WO |
| WO 2010075371 | Jul 2010 | WO |
| WO 2010099313 | Sep 2010 | WO |
| WO 2010114929 | Oct 2010 | WO |
| WO 2010119409 | Oct 2010 | WO |
| WO 2010124127 | Oct 2010 | WO |
| WO 2010130992 | Nov 2010 | WO |
| WO 2010135646 | Nov 2010 | WO |
| WO 2010135654 | Nov 2010 | WO |
| WO 2010135686 | Nov 2010 | WO |
| WO 2011005633 | Jan 2011 | WO |
| WO 2011022549 | Feb 2011 | WO |
| WO 2012048833 | Apr 2012 | WO |
| WO 2012049214 | Apr 2012 | WO |
| WO 2012049218 | Apr 2012 | WO |
| WO 2012120078 | Sep 2012 | WO |
| WO 2012140547 | Oct 2012 | WO |
| WO 2012164556 | Dec 2012 | WO |
| WO 2012170942 | Dec 2012 | WO |
| WO 2013045506 | Apr 2013 | WO |
| WO 2014100736 | Jun 2014 | WO |
| WO 2014131729 | Sep 2014 | WO |
| WO 2014131730 | Sep 2014 | WO |
| WO 2015124569 | Aug 2015 | WO |
| WO 2017176928 | Oct 2017 | WO |
| WO 2019219290 | Nov 2019 | WO |
| Entry |
|---|
| Akridge, Jeannie, “New Pumps Outsmart User Error”, Healthcare Purchasing News, Apr. 2011, pp. 10, http://web.archive.org/web/20110426122450/http://www.hpnonline.com/inside/2011-04/1104.OR-Pumps.html. |
| Alur et al., “Formal Specifications and Analysis of the Computer-Assisted Resuscitation Algorithm (CARA) Infusion Pump Control System”, International Journal on Software Tools for Technology Transfer, Feb. 2004, vol. 5, No. 4, pp. 308-319. |
| Aragon, Daleen RN, Ph.D., CCRN, “Evaluation of Nursing Work Effort and Perceptions About Blood Glucose Testing in Tight Glycemic Control”, American Journal of Critical Care, Jul. 2006, vol. 15, No. 4, pp. 370-377. |
| ASHP Advantage, “Improving Medication Safety in Health Systems Through Innovations in Automation Techology”, Proceedings of Educational Symposium and Educational Sessions during the 39th ASHP Midyear Clinical Meeting, Dec. 5-9, 2004, Orlando, FL, pp. 28. |
| Beard et al., “Total Quality Pain Management: History, Background, Resources”, Abbott Laboratories, TQPM Survey History, available Feb. 2015 or earlier, pp. 1-3. |
| Bektas et al., “Bluetooth Communication Employing Antenna Diversity”, Proceedings of Eight IEEE International Symposium on Computers and Communication, Jul. 2003, pp. 6. |
| Bequette, Ph.D., “A Critical Assessment of Algorithms and Challenges in the Development of a Closed-Loop Artificial Pancreas”, Diabetes Technology & Therapeutics, Feb. 28, 2005, vol. 7, No. 1, pp. 28-47. |
| Bequette, B. Wayne, Ph.D., “Analysis of Algorithms for Intensive Care Unit Blood Glucose Control”, Journal of Diabetes Science and Technology, Nov. 2007, vol. 1, No. 6, pp. 813-824. |
| Braun, “Infusomat® Space and Accessories”, Instructions for Use, Nov. 2010, pp. 68. http://corp.bbraun.ee/Extranet/infusioonlpumbad/Kasutusiuhendid/Vanad/Kasutusiuhend-Infusomat_Space(vers688J.inglise_k).pdf. |
| Brownlee, Seth, “Product Spotlight: The Plum A+ with Hospira MedNet Infusion System”, PP&P Magazine, Dec. 2005, vol. 2, No. 7, pp. 2. |
| Cannon, MD et al., “Automated Heparin-Delivery System to Control Activated Partial Thromboplastin Time”, Circulation, Feb. 16, 1999, vol. 99, pp. 751-756. |
| Cardinal Health, “Alaris® Syringe Pumps” Technical Service Manual, Copyright 2002-2006, Issue 9, pp. 1-88, http://www.frankshospitalworkshop.com/equipment/documents/infusion_pumps/service_manuals/Cardinal_Alaris_-_Service_Manual.pdf. |
| “CareAware® Infusion Management”, Cerner Store, as printed May 12, 2011, pp. 3, https://store.cerner.com/items/7. |
| Chen et al., “Enabling Location-Based Services on Wireless LANs”, The 11th IEEE International Conference on Networks, ICON 2003, Sep. 28-Oct. 1, 2003, pp. 567-572. |
| “Computer Dictionary”, Microsoft Press, Third Edition, Microsoft Press, 1997, pp. 430 & 506. |
| Crawford, Anne J., MSN, RNC, “Building a Successful Quality Pain Service: Using Patient Satisfaction Data and the Clinical Practice Guideline”, USA, 1995, pp. 1-6. |
| Crocker et al., “Augmented BNF for Syntax Specifications: ABNF”, Network Working Group, Standards Track, Jan. 2008, pp. 16. |
| Davidson et al., “A Computer-Directed Intravenous Insulin System Shown to be Safe, Simple, and Effective in 120,618 h of Operation”, Diabetes Care, Oct. 2005, vol. 28, No. 10, pp. 2418-2423. |
| Davies, T., “Cordless Data Acquisition in a Hospital Environment”, IEE Colloquium on Cordless Computing—Systems and User Experience, 1993, pp. 4. |
| Dayhoff et al., “Medical Data Capture and Display: The Importance of Clinicians' Workstation Design”, AMIA, Inc., 1994, pp. 541-545. |
| Diabetes Close Up, Close Concerns AACE Inpatient Management Conference Report, Consensus Development Conference on Inpatient Diabetes and Metabolic Control, Washington, D.C., Dec. 14-16, 2003, pp. 1-32. |
| EAST PhD et al., “Digital Electronic Communication Between ICU Ventilators and Computers and Printers”, Respiratory Care, Sep. 1992, vol. 37, No. 9, pp. 1113-1122. |
| Einhorn, George W., “Total Quality Pain Management: A Computerized Quality Assessment Tool for Postoperative Pain Management”, Abbott Laboratories, Chicago, IL, Mar. 2, 2000, pp. 1-4. |
| Eskew et al., “Using Innovative Technologies to Set New Safety Standards for the Infusion of Intravenous Medications”, Hospital Pharmacy, 2002, vol. 37, No. 11, pp. 1179-1189. |
| Philips, “IntelliSpace Event Management and IntelliVue Patient Monitoring”, Release 10, 2011, http://incenter.medical.philips.com/doclib/enc/fetch/2000/4504/577242/577243/577247/582646/583147/8359175/Philips_Patient_Monitoring_and_IntelliSpace_Event_Management_Interoperability.pdf%3tnodeid%3d8508574%26vernum%3d-2, pp. 2. |
| Felleiter et al., “Data Processing in Prehospital Emergency Medicine”, International journal of Clinical Monitoring and Computing, Feb. 1995, vol. 12, No. 1, pp. 37-41. |
| Fogt et al., Development and Evaluation of a Glucose Analyzer for a Glucose-Controlled Insulin Infusion System (Biostator®), Clinical Chemistry, 1978, vol. 24, No. 8, pp. 1366-1372. |
| Gabel et al., “Camp: A Common API for Measuring Performance”, 21st Large Installations System Administration Conference (LISA '07), 2007, pp. 49-61. |
| Gage et al., “Automated Anesthesia Surgery Medical Record System”, International Journal of Clinical Monitoring and Computing, Dec. 1990, vol. 7, No. 4, pp. 259-263. |
| Galt et al., “Personal Digital Assistant-Based Drug Information Sources: Potential to Improve Medication Safety”, Journal of Medical Library Association, Apr. 2005, vol. 93, No. 2, pp. 229-236. |
| Gardner, Ph.D. et al., “Real Time Data Acquisition: Recommendations for the Medical Information Bus (MIB)”, 1992, pp. 813-817. |
| “General-Purpose Infusion Pumps”, Health Devices, EXRI Institute, Oct. 1, 2002, vol. 31, No. 10, pp. 353-387. |
| Givens et al., “Exploring the Internal State of User Interfaces by Combining Computer Vision Techniques with Grammatical Inference”, Proceedings of the 2013 International Conference on Software Engineering, San Francisco, CA, May 18-26, 2013, pp. 1165-1168. |
| Glaeser, “A Hierarchical Minicomputer System for Continuous Post-Surgical Monitoring”, Computers and Biomedical Research, Aug. 31, 1975, pp. 336-361. |
| Goldberg et al., “Clinical Results of an Updated Insulin Infusion Protocol in Critically III Patients”, Diabetes Spectrum, 2005, vol. 18, No. 3, pp. 188-191. |
| Gomez et al., “CLAM: Connection-Less, Lightweight, and Multiway Communication Support for Distributed Computing”, Computer Science, 1997, vol. 1199, pp. 227-240. |
| “GPS Tracker for Medical Equipment”, http://www.trackingsystem.com/forbusinesses/corporate-trackingsystem/1098-gps-tracker-formedicalequipment.html, Mar. 15, 2015, pp. 2. |
| Graseby, “Model 3000/500 and Micro 3100/505: Volumetric Infusion Pump”, Technical Service Manual, Graseby Medical Ltd., Apr. 2002, Issue A, pp. 160. |
| Graseby, “Model 3000/500 and Micro 3100/505: Volumetric Infusion Pump: Illustrated Parts List for Pump Serial Numbers from 3000 to 59,999”, Technical Service Manual, Graseby Medical Ltd., Apr. 2002, Issue A, pp. 71. |
| Halpern et al., “Changes in Critical Care Beds and Occupancy in the United States 1985-2000: Differences Attributable to Hospital Size”, Critical Care Medical, Aug. 2006, vol. 34, No. 8, pp. 2105-2112. |
| Hamann et al., “PUMPSIM: A Software Package for Simulating Computer-Controlled Drug Infusion Pumps”, Annual International Conference of the IEEE Engineering in Medicine and Biology Society, 1990, vol. 12, No. 5, pp. 2019-2020. |
| Hasegawa et al., “On a Portable Memory Device for Physical Activities and Informations of Maternal Perception”, Journal of Perinatal Medicine, 1988, vol. 16, No. 4, pp. 349-356. |
| Hawley et al., “Clinical Implementation of an Automated Medical Information Bus in an Intensive Care Unit”, Proceedings of the Annual Symposium on Computer Application in Medical Care, Nov. 9, 1988, pp. 621-624. |
| Hayes-Roth et al., “Guardian: A Prototype Intelligent Agent for Intensive-Care Monitoring”, Artificial Intelligence in Medicine, vol. 4, Dec. 31, 1992, pp. 165-185. |
| Hospira, GemStar® Pain Management Infusion System 9-084-PR1-2-2, www.hospira.com/products/gemstar_painmanagement.aspx, Jan. 28, 2010, pp. 1-2. |
| Introducing Abbott TQPM (Total Quality Pain Management), Abbott Laboratories, Abbott Park, IL, May 2000, pp. 1-4. |
| “Infusion Pump”, Wikipedia.org, http://web.archive.org/web/20140703024932/https://en.wikipedia.org/wiki/Infusion_pump, as last modified Mar. 27, 2014, pp. 3. |
| Isaka et al., “Control Strategies for Arterial Blood Pressure Regulation”, IEEE Transactions on Biomedical Engineering, Apr. 1993, vol. 40, No. 4, pp. 353-363. |
| Johnson et al., “Using BCMA Software to Improve Patient Safety in Veterans Administration Medical Centers”, Journal of Healthcare Information Management, Dec. 6, 2004, vol. 16, No. 1, pp. 46-51. |
| Kent Displays, “Reflex™ Electronic Skins”, Product Brief 25127B, 2009, pp. 2. |
| Kent Displays, “Reflex Electronic Skins Engineering Evaluation Kit”, 25136A, Mar. 10, 2009. |
| Lefkowitz et al., “A Trial of the Use of Bar Code Technology to Restructure a Drug Distribution and Administration System”, Hospital Pharmacy, Mar. 31, 1991, vol. 26, No. 3, pp. 239-242. |
| Lenssen et al., “Bright Color Electronic Paper Technology and Applications”, IDS '09 Publication EP1-2 (Phillips Research), 2009, pp. 529-532. |
| Leveson, Nancy, “Medical Devices: The Therac-25”, Appendix A, University of Washington, 1995, pp. 49. |
| Linkens, D.A. “Computer Control for Patient Care”, Computer Control of Real-Time Processes, IEE Control Engineering Series 41, 1990, Ch. 13, pp. 216-238. |
| Mako Hill et al., “The Official Ubuntu Book”, Shoeisha Co., Ltd., 1st Edition, Jun. 11, 2007, pp. 115 to 125. |
| Marshall, et al., “New Microprocessor-Based Insulin Controller”, IEEE Transactions on Biomedical Engineering, Nov. 1983, vol. BME-30, No. 11, pp. 689-695. |
| Martino et al., “Automation of a Medical Intensive Care Environment with a Flexible Configuration of Computer Systems”, Proceedings of the Annual Symposium on Computer Application in Medical Care, Nov. 5, 1980, vol. 3, pp. 1562-1568. |
| Matsunaga et al., “On the Use of Machine Learning to Predict the Time and Resources Consumed by Applications”, 2010 10th IEEE/ACM International Conference on Cluster, Cloud and Grid Computing (CCGrid), May 17-20, 2010, pp. 495-504. |
| Mauseth et al., “Proposed Clinical Application for Tuning Fuzzy Logic Controller of Artificial Pancreas Utilizing a Personalization Factor”, Journal of Diabetes Science and Technology, Jul. 2010, vol. 4, No. 4, pp. 913-922. |
| Medfusion™, “Medfusion Syringe Infusion Pump Model 4000”, Operator's Manual, Software Version V1.1, Sep. 2011, p. 154. http://www.medfusionpump.com/assets/literature/manuals/Operators_Manal_4000_40-5760-51A.pdf. |
| Metnitz et al., “Computer Assisted Data Analysis in Intensive Care: the ICDEV Project-Development of a Scientific Database System for Intensive Care”, International Journal of Clinical Monitoring and Computing, Aug. 1995, vol. 12, No. 3, pp. 147-159. |
| Micrel Medical Devices, “MP Daily +” http://web.archive.org/web/20130803235715/http://www.micrelmed.com/index.aspx?productid=9 as Archived Aug. 3, 2013 in 1 page. |
| Moghissi, Etie, MD, FACP, FACE, “Hyperglycemia in Hospitalized Patients”, A Supplement to AGP Hospitalist, Jun. 15, 2008, pp. 32. |
| Murray, Jr. et al., “Automated Drug Identification System (during surgery)”, IEEE Proceedings of Southeastcon '91, Apr. 7-10, 1991, pp. 265. |
| Nicholson et al., “‘Smart’ Infusion Apparatus for Computation and Automated Delivery of Loading, Tapering, and Maintenance Infusion Regimens of Lidocaine, Procainamide, and Theophylline”, Proceedings of the Seventh Annual Symposium on Computer Applications in Medical Care, Oct. 1983, pp. 212-213. |
| Nolan et al., “The P1073 Medical Information Bus Standard: Overview and Benefits for Clinical Users”, 1990, pp. 216-219. |
| Omnilink Systems, Inc., “Portable Medical Equipment Tracking”, http://www.omnilink.com/portablemedicalequipmenttracking/, Mar. 15, 2015, pp. 2. |
| O'Shea, Kristen L., “Infusion Management: Working Smarter, Not Harder”, Hospital Pharmacy, Apr. 2013, vol. 48, No. 3, pp. S1-S14. |
| Package Management in Debian GNU/Linux, Debian GNU/Linux Expert Desktop Use Special, Giutsu-Hyohron Co., Ltd., First Edition, Sep. 25, 2004, pp. 183-185. |
| Passos et al., “Distributed Software Platform for Automation and Control of General Anaesthesia”, Eighth International Symposium on Parallel and Distributed Computing, ISPDC '09, Jun. 30-Jul. 4, 2009, pp. 8. |
| Pretty et al., “Hypoglycemia Detection in Critical Care Using Continuous Glucose Monitors: An in Silico Proof of Concept Analysis”, Journal of Diabetes Science and Technology, Jan. 2010, vol. 4, No. 1, pp. 15-24. |
| Rappoport, Arthur E., “A Hospital Patient and Laboratory machine-Readable Identification System (MRIS) Revisited”, Journal of Medical Systems, Apr. 1984, vol. 8, Nos. 1/2, pp. 133-156. |
| Ritchie et al., “A Microcomputer Based Controller for Neuromuscular Block During Surgery”, Annals of Biomedical Engineering, Jan. 1985, vol. 13, No. 1, pp. 3-15. |
| Saager et al., “Computer-Guided Versus Standard Protocol for Insulin Administration in Diabetic Patients Undergoing Cardiac Surgery”, Annual Meeting of the American Society of Critical Care Anesthesiologists, Oct. 13, 2006. |
| Sanders et al., “The Computer in a Programmable Implantable Medication System (PIMS)”, Proceedings of the Annual Symposium on Computer Application in Medical Care, Nov. 2, 1982, pp. 682-685. |
| Schilling et al., “Optimizing Outcomes! Error Prevention and Evidence-Based Practice with IV Medications”, A Pro-Ce Publication, Hospira, Inc., Feb. 6, 2012, pp. 56. |
| Schulze et al., “Advanced Sensors Technology Survey”, Final Report, Feb. 10, 1992, pp. 161. |
| Scott, et al., “Using Bar-Code Technology to Capture Clinical Intervention Data in a Hospital with a Stand-Alone Pharmacy Computer System”, Mar. 15, 1996, American Journal of Health-System Pharmacy, vol. 53, No. 6, pp. 651-654. |
| Sebald et al., “Numerical Analysis of a Comprehensive in Silico Subcutaneous Insulin Absorption Compartmental Model”, 31st Annual International Conference of the IEEE Engineering in Medicine and Biology Society, Sep. 2-6, 2009, pp. 3901-3904. |
| Shabot, M. Michael, “Standardized Acquisition of Bedside Data: The IEEE P1073 Medical Information Bus”, International Journal of Clinical Monitoring and Computing, vol. 6, Sep. 27, 1989, pp. 197-204. |
| Sheppard, Louis, Ph.D., “Automation of the Infusion of Drugs Using Feedback Control”, Journal of Cardiothoracic and Vascular Anesthesia, Feb. 28, 1989, vol. 3, No. 1, pp. 1-3. |
| Sheppard, Louis, Ph.D., “Computer Control of the Infusion of Vasoactive Drugs”, Annals of Biomedical Engineering, Jul. 1980, vol. 8, No. 4-6, pp. 431-444. |
| Sheppard, Louis, Ph.D., “The Application of Computers to the Measurement, Analysis, and Treatment of Patients Following Cardiac Surgical Procedures”, The University of Alabama in Birmingham, Oct. 31, 1977, pp. 297-300. |
| Sheppard, Louis, Ph.D., “The Computer in the Care of Critically III Patients”, Proceedings of the IEEE, Sep. 1979, vol. 67, No. 9, pp. 1300-1306. |
| “Sigma Spectrum: Operator's Manual”, Oct. 2009, pp. 72. http://static.medonecapital.com/manuals/userManuals/Sigma-Spectrum-Operator-Manual-October-2009.pdf. |
| Simonsen, Michael Ph.D., POC Testing, New Monitoring Strategies on Fast Growth Paths in European Healthcare Arenas, Biomedical Business & Technology, Jan. 2007, vol. 30, No. 1, pp. 1-36. |
| Siv-Lee et al., “Implementation of Wireless ‘Intelligent’ Pump IV Infusion Technology in a Not-for-Profit Academic Hospital Setting”, Hospital Pharmacy, Sep. 2007, vol. 42, No. 9, pp. 832-840. http://www.thomasland.com/hpi4209-832.pdf. |
| Slack, W.V., “Information Technologies for Transforming Health Care”, https://www.andrew.cmu.edu/course/90-853/medis.dir/otadocs.dir/03ch2.pdf, Ch. 2, 1995, pp. 29-78. |
| Smith, Joe, “Infusion Pump Informatics”, CatalyzeCare: Transforming Healthcare, as printed May 12, 2011, pp. 2. |
| Sodder, Lisa, “A Center Keeps Medicine in Right Hands”, Dec. 4, 1999, pp. 1-2. |
| Stitt, F.W., “The Problem-Oriented Medical Synopsis: a Patient-Centered Clinical Information System”, Proceedings of the Annual Symposium on Computer Application in Medical Care, 1994, pp. 88-92. |
| Stokowski, Laura A. RN, MS, “Using Technology to Improve Medication Safety in the Newborn Intensive Care Unit”, Advances in Neonatal Care, Dec. 2001, vol. 1, No. 2, pp. 70-83. |
| Sutton et al., “The Syntax and Semantics of the PROforma Guideline Modeling Language”, Journal of the American Medical Informatics Association, Sep./Oct. 2003, vol. 10, No. 5, pp. 433-443. |
| Szeinbach et al., “Automated Dispensing Technologies: Effect on Managed Care”, Journal of Managed Care Pharmacy (JMCP), Sep./Oct. 1995, vol. 1, No. 2, pp. 121-127. |
| Szolovits et al., “Guardian Angel: Patient-Centered Health Information Systems”, Technical Report MIT/LCS/TR-604, Massachusetts Institute of Technology Laboratory for Computer Science, May 1994, pp. 39. |
| Van Den Berghe, M.D., Ph.D., et al., “Intensive Insulin Therapy in Critically III Patients”, The New England Journal of Medicine, Nov. 8, 2001, vol. 345, No. 19, pp. 1359-1367. |
| Van Den Berghe, M.D., Ph.D., et al., “Intensive Insulin Therapy in the Medical ICU”, The New England Journal of Medicine, Feb. 2, 2006, vol. 354, No. 5, pp. 449-461. |
| Van Der Maas et al., “Requirements for Medical Modeling Languages”, Journal of the American Medical Informatics Association, Mar./Apr. 2001, vol. 8, No. 2, pp. 146-162. |
| Villalobos et al., “Computerized System in Intensive Care medicine”, Medical Informatics, vol. 11, No. 3, 1986, pp. 269-275. |
| Wilkins et al., “A Regular Language: The Annotated Case Report Form”, PPD Inc., PharmaSUG2011—PaperCD18, 2011, pp. 1-9. |
| Ying et al., “Regulating Mean Arterial Pressure in Postsurgical Cardiac Patients. A Fuzzy Logic System to Control Administration of Sodium Nitroprusside”, IEEE Engineering in Medicine and Biology Magazine, vol. 13, No. 5, Nov.-Dec. 1994, pp. 671-677. |
| Yue, Ying Kwan, “A Healthcare Failure Mode and Effect Analysis on the Safety of Secondary Infusions”, Thesis, Institute of Biomaterials and Biomedical Engineering, University of Toronto, 2012, pp. 168. |
| Yurkonis et al., “Computer Simulation of Adaptive Drug Infusion”, IEEE Transactions on Biomedical Engineering, vol. BME-34, No. 8, Aug. 1987, pp. 633-635. |
| Zakariah et al., “Combination of Biphasic Transmittance Waveform with Blood Procalcitonin Levels for Diagnosis of Sepsis in Acutely III Patients”, Critical Care Medicine, 2008, vol. 36, No. 5, pp. 1507-1512. |
| Official Communication in Japanese Patent Application No. 2009-0533485, dated Jan. 15, 2013 in 5 pages. |
| International Search Report and Written Opinion received in PCT Application No. PCT/US2007/081549, dated Aug. 18, 2008 in 14 pages. |
| International Preliminary Report on Patentability and Written Opinion received in PCT Application No. PCT/US2007/081549, dated Apr. 22, 2009 in 12 pages. |
| “Context-Free Grammar”, Wikipedia.org, as last modified Mar. 5, 2010 in 11 pages, https://en.wikipedia.org/w/index.php/?title=Context-free_grammar&oldid=347915989. |
| “Download”, Free On-Line Dictionary of Computing, as archived Jun. 16, 2010 in 1 page, http://web.archive.org/web/20100616010314/https://foldoc.org/download. |
| Edworthy, Judy, “Medical Audible Alarms: A Review”, Journal of the American Medical Informatics Association, vol. 20, No. 3, 2013, pp. 584-589. |
| “File Verification”, Wikipedia.org, as last modified Oct. 11, 2011 in 2 pages, https://en.wikipedia.org/w/index.php?title=File_verification&oldid=455048290. |
| “McKesson Automation and ALARIS Medical Systems Developing Point-of-Care Bar Coding Solution to Improve IV Medication Safety”, PR Newswire, NY, Dec. 9, 2002, pp. 4. |
| “Software Versioning”, Wikipedia.org, dated Oct. 16, 2011 in 11 pages, https://en.wikipedia.org/w/index.php?title=Software_versioning&oldid=455859110. |
| Number | Date | Country | |
|---|---|---|---|
| 20190243829 A1 | Aug 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60851971 | Oct 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14528907 | Oct 2014 | US |
| Child | 16266528 | US | |
| Parent | 11873269 | Oct 2007 | US |
| Child | 14528907 | US |
