Synchronized display of screen content on networked devices

Description

TECHNICAL FIELD

This disclosure relates to the field of networked devices, and particularly to techniques for synchronizing the screen content displayed on a plurality of networked devices.

BACKGROUND

Networked devices capable of displaying information are commonplace in modern network environments. Such networked devices may each include a display screen configured to display information generated by the networked device such as a status of the networked device, an error encountered by the networked device, etc. Based on the information displayed on the display screens, users may determine whether any action needs to be taken with respect to the networked devices.

SUMMARY

Various techniques for providing a synchronized display of screen content on a plurality of networked devices are described herein. Although many of the examples are described in the context of a hospital environment, the techniques described herein can be applied to any network environment including multiple networked devices. The networked devices described herein may include infusion pumps, other medical devices, or non-medical devices, or any combination thereof. The screen content described herein may be drug delivery metrics, other medical device screen content, other display screen content, or any combination thereof. The synchronization of the screen content displayed on multiple networked devices may be performed without having a centralized server communicate with each networked device to coordinate the content and/or timing of the displayed screen content. In some cases, synchronization of the screen content displayed on multiple networked devices is performed based on synchronizing the internal clocks of the respective networked devices with a reference time. In other cases, synchronization of the screen content displayed on multiple networked devices occurs without synchronizing the internal clocks of the respective networked devices and without utilizing a centralized server to synchronize the displays of the multiple networked devices. These and other embodiments are described in greater detail below with reference to FIGS. 1-7.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments described herein are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like references indicate similar elements.

FIG. 1 is a schematic diagram of an example network environment including one or more networked devices in accordance with aspects of this disclosure.

FIG. 2 is a block diagram illustrating components of an example network environment in accordance with aspects of the present disclosure.

FIG. 3 illustrates a general architecture of an example networked device in accordance with aspects of this disclosure.

FIG. 4 illustrates example networked devices in network environments in accordance with aspects of this disclosure.

FIG. 5 illustrates an example screen content update method in accordance with aspects of this disclosure.

FIG. 6 illustrates an example synchronized metric switching method in accordance with aspects of this disclosure.

FIG. 7 illustrates an example user interface for specifying the screen content management rules in accordance with aspects of this disclosure.

DETAILED DESCRIPTION
Introduction

A network environment may include multiple electronic devices. One example of such an environment is a hospital network environment, where a centralized server communicates with multiple medical devices such as patient care monitors and infusion pumps. In the hospital network environment, the centralized server may control how the medical devices in the hospital network environment operate and what kind of information is presented via the medical devices. For example, several patients may share a single room in a hospital, and the patients may each be assisted by a number of medical devices. Such medical devices may each include a display screen through which various physiological metrics, warnings, measurements, and other information may be presented to the caregiver or patient.

As the number of such networked devices displaying and updating screen content increases, viewing and understanding the displayed information becomes more difficult. For example, a caregiver may wish to quickly scan an array of 10 infusion pumps to determine whether the infusion pumps are functioning properly, infusing the medications at the correct rate, how much time it will be until the medication delivery is complete, etc. However, if the 10 infusion pumps are each cycling through multiple metrics on their displays (e.g., rate, dose, time remaining, volume infused, volume to be infused, etc.) at different times, the caregiver may find that distracting and inefficient. As another example, a system administrator may wish to scan an array of monitors to ensure that all of the servers are performing properly. However, if the monitors are cycling through different server statistics out of sync, it may be difficult for the system administrator to gather the necessary information from the monitors. Thus, an improved method of synchronizing the displays of such networked devices is desired.

Synchronizing Screen Content Displayed on Networked Devices

In some implementations, the networked devices described above (e.g., infusion pumps, monitors, etc.) in a network environment cause their respective screen content to be changed in response to a signal received from a server. For example, the server may transmit a “heartbeat” signal to each networked device every 15 seconds, indicating that the networked device should change the displayed content or switch to the next content in a given display order. Such a signal from the server may also indicate which content the networked device should display (e.g., by including a content identifier in the signal transmitted to the networked device). In such implementations, the signal would be received and processed by the individual networked devices at approximately the same time, and the content displayed on their displays would be synchronized as a result.

However, such use of heartbeat signals can consume valuable network resources (e.g., bandwidth) and overwhelm the network, especially if the network includes a large number of such networked devices. Further, processing such heartbeat signals from the server may require a sophisticated processor on the networked device and/or consume valuable processing power. In view of these technical considerations, in some cases, it may be beneficial to display and cycle through screen content without relying on such a heartbeat signal. In another implementation, the screen content may be displayed based on an internal clock maintained by the individual networked devices and without communicating with the server each time new screen content needs to be displayed. In such implementations, the amount of data transmitted across the network environment may be significantly reduced and valuable network resources and/or processing power can be preserved for other uses. The techniques for synchronizing the screen content displayed on networked devices in this manner are described in greater detail below with reference to FIGS. 2-7.

In yet another implementation, the individual networked devices locally store a fixed schedule of which metric to display at what time. In such an implementation, a networked device may store a table that specifies, for each controlling variable (e.g., clinical care area of an infusion pump), which metric should be displayed at a given time of day. For example, the table may specify that for networked devices in the intensive care unit should display metric #1 for the first 10 minutes of every hour, metric #2 for the second 10 minutes, metric #3 for the third 10 minutes, and so on, and for networked devices in the operating room should display metric #3 for the first 30 minutes of every hour, and metric #4 for the second 30 minutes of every hour. As another example, the table may specify, for each 5-second interval in the 24 hours of a given date, the metric to be displayed for the 5-second interval. However, locally storing such a table would consume a large amount of memory or disk space, which may not be desired for networked devices having limited memory/storage. Further, even if such a table is accessed from a remote network location, accessing the table over the network can consume valuable network resources (e.g., bandwidth) and overwhelm the network, especially if the network includes a large number of such networked devices. As discussed above, displaying the screen content based on an internal clock maintained by the individual networked devices and without storing or accessing large amounts of data specifying the screen content to be displayed at any given interval may provide certain technical benefits such as reducing the amount of storage space needed and/or data transmitted across the network environment and allowing valuable storage/network resources to be preserved for other uses.

With reference to FIG. 1, an example network environment in which one or more of the display synchronization techniques of the present disclosure may be utilized is described. Following the discussion of FIG. 1, specific details of the various embodiments of the present disclosure are described with reference to FIGS. 2-7.

Overview of Example Network Environment

FIG. 1 illustrates one embodiment of a system for administering medication via an infusion pump in a network environment 100. The medication management system (MMS) shown in FIG. 1 includes a medication management unit (MMU) server 3108 and a medical device, such as infusion pump 3130, operating in conjunction with one or more information systems or components of a hospital environment.

Intravenous (IV) fluid(s) and/or medication(s) 3100 in containers 3102 may be administered to a patient 3104 using the system shown in FIG. 1. Although the system shown in FIG. 1 utilizes barcodes and a barcode reader as apparatus to input and read machine-readable information, those skilled in the art will appreciate that other apparatus for reading or inputting information may be utilized. Moreover, a point of care (POC) client 3126 may include an identification receiver 32 adapted to recognize such indicia that may be provided in the MMS.

In certain aspects, the IV fluids and/or medications 3100 in container 3102 may be provided with new or supplemental labels with a unique infusion order identifying barcode by a pharmacist according to certain hospital practices. Specifically, drug container specific identification information, such as barcoded information on the container 3102 may include patient identification information, medication identification information, universal identification information, medical device delivery information, and/or medication order information. The IV fluids and/or medications 3100 in barcode-identified containers 3102 may be supplied to hospitals by various vendors, with preexisting unique barcode identifiers, which include medication information and other information, such as a National Disease Center (NDC) code, expiration information, drug interaction information, and the like.

In some aspects of the disclosure, the universal identification information on the container 3102 may be a unique medication order identifier that, by itself, identifies the order associated with the container. In other aspects, the identification information on the container 3102 may be a composite patient/order code that contains both a patient ID (such as a medical record number) and an order ID unique only within the context of the patient. In certain aspects, the identification information on the container 3102 may include a medication ID. The system identified in FIG. 1 may include a drug library editor (DLE) client 3106, such as a notebook, desktop or server computer. The DLE client 3106 may include DLE software. As described above, the MMU server 3108 may have MMU software that is installed and runs on the MMU server 3108. The drug library and other databases may be stored on the MMU server 3108, on a separate server, and/or in remote locations.

Hospital information systems (HIS) 3110 may include one or more computers connected by cabling, interfaces, and/or Ethernet connections. Alternatively, wireless connections and communications may be used in whole or in part. Servers provide processing capability and memory for storage of data and various application programs or modules, including but not limited to an admissions-discharge-and-transfer (ADT) module or computer 3112, a computerized physician order entry (CPOE) module or computer 3114, and a pharmacy information system (PIS) module or computer 3116. Hospital personnel, such as admission clerks 3118, physicians 3120, and pharmacists 3122, respectively, may be authorized to access these modules through client workstations connected to the servers in order to enter data, access information, run reports, and complete other tasks.

In the embodiment shown in FIG. 1, the HIS 3110 may also include a POC system 3125 including a server or POC computer 3124 (sometimes referred to as a barcode point of care server or computer), or the POC computer 3124 may be separate from the HIS 3110. The POC computer 3124 may act as a part of the POC system 3125 (sometimes referred to as the barcode point of care system or BPOC) and may be able to wirelessly communicate through a plurality of wireless communication nodes located throughout the hospital, utilizing a wireless communications protocol, such as IEEE 801.11, IEEE 802.11, or Bluetooth. The POC computer 3124 may communicate wirelessly with a portable thick client, POC client 3126, carried by a caregiver. The POC client 3126 may be a personal digital assistant (PDA) that includes significant memory, display, and processing capabilities. The POC client device may execute a variety of programs stored in its memory in some degree independently of the POC computer 3124.

In one embodiment of FIG. 1, the MMU server 3108 may be hard-wired to the DLE client 3106 and to a MMU client 3128. Alternatively, the MMU and DLE client functions may be combined onto a single client computer/workstation or may reside together with the MMU server 3108 on a single combined MMU/DLE server. The MMU server 3108 may reside in a location remote from the patient's room or treatment area. For instance, the MMU server 3108 may reside in a secure, climate controlled information technology room with other hospital servers, and computer equipment and its client terminals may be located in the pharmacy, biomedical engineering area, nurse station, or ward monitoring area. One MMU server 3108 may monitor, coordinate, and communicate with many infusion pumps 3130. For example, in one embodiment, the MMU software running on the MMU server 3108 may support up to one thousand infusion pumps concurrently.

In embodiment of FIG. 1, the POC client 3126 in the POC system 3125 may communicate through the POC server 3124 with the MMU server 3108. The MMU server 3108 may interface or communicate wirelessly with the infusion pump 3130 through the same wireless nodes utilized by the POC system 3125 and a connectivity engine and antenna on or in the infusion pump 3130. Communication between the infusion pump 3130 and the POC client 3126 may take place through the MMU server 3108 and POC server 3124. The MMU server 3108 may store in an associated memory both the logical ID and the network ID or Internet Protocol (IP) address of the infusion pump(s) 3130, such that only the MMU server 3108 may communicate in a direct wireless manner with the infusion pump 3130. Alternatively, the MMU server 3108 may provide the IP address and other information about the infusion pump 3130 to the POC system 3125 to facilitate direct communication between the POC system 3125 and the infusion pump 3130.

Upon admission to the hospital, the admission clerk 3118 or similar personnel may enter demographic information about each patient 3104 into an associated memory of the ADT module or computer 3112 of an HIS database stored in an associated memory of the HIS 3110. Each patient 3104 may be issued a patient identification wristband, bracelet, or tag 112 that may include an identifier 3103, such as a barcode or RFID tag, identifying the patient. The wristband, bracelet, or tag 112 may also include other information, in machine readable or human-readable form, such as the name of the patient's doctor, blood type, allergies, and the like.

The patient's doctor 3120 may prescribe medical treatment by entering a medication order into the CPOE module or computer 3114 within the HIS 3110. The medication order may specify a start time, stop time, a range of allowable doses, physiological targets, route, and site of administration. In the case of an order for infusion of fluids or medication, the order may be written in various formats, and may include the patient's name, patient ID number, a unique medication order or prescription number, a medication name, medication concentration, a dose or dosage, frequency, and/or a time of desired delivery. This information may be entered into the memory of the CPOE module or computer 3114, and may be stored in a memory associated with at least the POC server 3124.

The medication order may also be delivered electronically to the PIS module or computer 3116 in the pharmacy and may be stored in an associated memory. The pharmacist 3122 may screen the prescribed order, translate it into an order for dispensing medication, and prepare the medication or fluids with the proper additives and/or necessary diluents. The pharmacist 3122 may prepare and affix a label 102 with drug container specific identifying information 3101 to the medication or drug container 3102. The label may include in machine-readable and/or human-readable form medical device specific delivery information including but not limited to the dispense ID number, patient ID, drug name, drug concentration, container volume, volume-to-be-infused (“VTBI”), rate, duration, and the like. Only two of the three variables VTBI, rate, and duration may be defined as the third may be calculated when the other two are known. The labeled medication may be delivered to a secure, designated staging location or mobile drug cart on the ward or floor near the patient's room or treatment area. The medication order pending dispensing or administration may be posted to a task list in the HIS 3110 and POC system 3125 and stored in an associated memory.

The caregiver 3132 (e.g., a nurse) may use the identification receiver 32 associated with the POC client 3126 to scan the caregiver specific identification information 3133 or barcode on his/her caregiver identification badge 116 and enter a password, which logs the caregiver into the system and authorizes the caregiver to access a nurse's task list from the POC system 3125 through the POC client 3126. The caregiver 3132 may view from the task list that IV drugs are to be administered to certain patients 3104 in certain rooms. The caregiver 3132 obtains the necessary supplies, including medications, from the pharmacy and/or a staging area in the vicinity of the patient's room.

The caregiver 3132 may take the supplies to a patient's bedside, turn on the infusion pump 3130, verify that the network connection icon on the infusion pump 3130 indicates a network connection (for example, a wireless connection such as Wi-Fi or the like) is present, select the appropriate clinical care area (CCA) on the infusion pump 3130, and mount the IV bag, container, or vial 3102 and any associated tube set as required in position relative to the patient 3104 and infusion pump 3130 for infusion. Another connection icon on the infusion pump 3130 or pump user interface screen can indicate that a wired or wireless connection to the MMU server 3108 is present. Using the identification receiver/reader integral to the POC client 3126, the caregiver 3132 may scan the barcode on the patient's identification wristband, bracelet, or tag 112 or other patient identification device. A task list associated with that particular patient may appear on the POC client 3126 screen. The task list, which may also include orders to give other forms of treatment or medication by other routes (oral, topical, etc.), may be obtained from the HIS 3110 via the POC server 3124 and communicated wirelessly to the POC client 3126. In one embodiment, the list is generated by matching the scanned patient ID with the patient ID for orders in memory within the POC server 3124. In another embodiment, the order information may be obtained by scanning the drug container specific identification information for associated orders in memory within the POC server 3124, through the following step(s).

The caregiver 3132 may scan the medication barcode label 102 containing medication container specific identification information 3101 on the medication container 3102 with the POC client 3126. The POC client 3126 may highlight the IV administration task on the task list and send the scanned medication container specific identification information, such as dispense ID information, from the medication container 3102, to the POC server 3124. The POC server may use the medication container specific identification information to pull together the rest of the order details and send them back to the POC client 3126. The POC client 3126 may then display an IV Documentation Form on its screen. One side of the IV Documentation Form screen may show the order details as “ordered” and the other side may be reserved for a status report from the infusion pump 3130. The status report from the infusion pump 3130 may be transmitted to the POC client 3126 through the POC server 3124 and MMU server 3108. The lower portion of the IV Documentation Form screen may provide the caregiver 3132 with instructions (like to scan the infusion pump 3130 barcode) or identify whether the pump is running or stopped.

The caregiver 3132 may then scan the barcode label 92 associated with the infusion pump 3130 (or pump channel if the pump is a multi-channel pump). The barcode label 92 may contain medical device specific identification information 3131, such as the logical name and/or logical address of the device or channel. The POC system 3125 then automatically bundles the information into a program pump request containing the “order details” and in one embodiment, without further interaction with the caregiver 3132, transmits this information to the MMU server 3108.

The program pump request may include at least some of the following information (in HIS/POC system format): a Transaction ID, which may include a Logical Pump ID, a Pump Compartment, a Pump Channel ID, a Reference Device Address, a Caregiver ID, a Caregiver Name, a Patient/Person ID (HIS identifier), a Patient Name, a Patient Birth Date & Time, a Patient Gender, a Patient Weight, a Patient Height, and an Encounter ID which may include a Room, a Bed, and a Building (including CCA). The program pump request may also include Order Information or “order details”, including an Order ID, a Start Date/Time, a Stop Date/Time, a Route of Administration, a Rate, a Duration of Infusion (Infuse Over), a Total Volume to be Infused (VTBI), an Ad Hoc Order Indicator, and Ingredients including HIS Drug Name or HIS Generic Drug Name, HIS Drug Identifier or HIS Generic Drug ID, Rx Type (Additive or Base), Strength w/units, and Volume w/units. The program pump request may further include Patient Controlled Analgesia (PCA) Orders Only information, such a PCA Mode-PCA only, Continuous only, or PCA and Continuous, a Lockout Interval (in minutes), a PCA Continuous Rate, a PCA Dose, a Loading Dose, a Dose Limit, a Dose Limit Time w/units, a Total Volume in vial or syringe, and Order Comments.

The MMU server 3108 may map or convert the wide range of expressions of units allowed by the HIS 3110 or POC system 3125 for POC client 3126 requests into the much more limited set of units allowed in the MMU server 3108 and infusion pump 3130. For example, the POC client 3126 request may express “g, gm, gram, or grams” whereas the MMU server 3108 and/or infusion pump 3130 may accept “grams” only. Infusion pump 3130 delivery parameters or infusion pump 3130 settings are mapped or converted from corresponding order information or “order details” of the program pump request.

The MMU server 3108 may store in an associated memory a mapping or translation table that keep track of the logical ID, serial number or other identifier of an infusion pump 3130 and the corresponding current network (static or dynamic) address (Internet Protocol (IP) address) or ID of the infusion pump 3130 on the network, which in this example is a wireless network. The MMU server 3108 may be able to translate or associate a given identifier of the infusion pump 3130 with its network address in the translation table and provide the network IP address to the requesting POC system 3125 or device. The MMU server 3108 may also store in an associated memory and/or look up the drug library applicable to the scanned infusion pump 3130 and/or convert the Drug ID and Strength from the pump program request into an index number of the medication at the desired strength or concentration from the drug library. The duration of the infusion may come from the POC system 3125 in hours and minutes and may be converted to just minutes for the infusion pump 3130 to recognize it. Volume or VTBI may be rounded to provide a value-specific and infuser-specific number of digits to the right of the decimal point. Units (of drug) may be converted to million units where appropriate. Patient weight may be converted and either rounded according to infuser-specific rules or not sent to the infuser.

Once the MMU server 3108 transforms the information from the program pump request into infusion pump settings or delivery parameters and other information in a format acceptable to the infusion pump 3130, the MMU server 3108 may wirelessly download a command message to the infusion pump 3130. If the infusion pump 3130 is not already equipped with the latest appropriate version of the hospital-established drug library, the MMU server 3108 may also automatically download a drug library to the infusion pump 3130. The hospital-established drug library may be maintained in a separate process undertaken by the biomedical engineer or pharmacist 3122 to place limits on the programming of the infusion pump 3130, as well as other infusion pump operating parameters such as default alarm settings for air in the line, occlusion pressure, and the like. The drug library may set up acceptable ranges or hard and/or soft limits for various drug delivery parameters in the infusion pump 3130.

The MMU server 3108 may also download to the infusion pump new versions, patches, or software updates of the infusion pump's internal operating system software. The infusion settings or delivery parameters and other information from the MMU server 3108 may be entered into the memory of the infusion pump 3130 and the infusion pump 3130 settings may automatically populate the programming screen(s) of the infusion pump 3130, just as if the caregiver 3132 had entered the information and settings manually. The infusion pump 3130 screen may populate with the name of the drug and drug concentration based on the drug library index number, patient weight, rate, VTBI, and/or duration. Further, the MMU server 3108 may transmit one or more synchronization signals or screen content display rules/parameters to the infusion pump 3130, as described in greater detail below with reference to FIGS. 2-7. A return message of confirmation signal may be sent to the MMU server 3108 by the infusion pump 3130 to indicate that the command message has been received. At this point, if necessary, the caregiver 3132 may manually enter any additional infusion settings or optional information that was not included in the command message.

The infusion pump 3130 may then prompt the caregiver 3132 to start the infusion pump 3130 by pressing the start button. When the caregiver 3132 presses the start button, a confirmation screen with the infusion settings programmed may be presented for confirmation and an auto-program acknowledgment message can be sent to the MMU server 3108 to forward without request (i.e., pushed in a near real-time manner) or provide to the POC system 3125 when requested or polled. When the caregiver 3132 presses the button to confirm, the infusion pump 3130 may begin delivering fluid according to the programmed settings. The infusion pump 3130 may send a status message to the MMU server 3108 indicating that the infusion pump 3130 was successfully auto-programmed, confirmed and started by the caregiver 3132, and is now delivering fluid. This information may also be displayed at the infusion pump. The MMU server 3108 may continue to receive logs and status messages wirelessly from the infusion pump 3130 periodically as the infusion progresses or when alarms occur.

The MMU server 3108 may report a portion of the initial status message to the POC client 3126 through the POC server 3124 (in MMU format) to indicate that the infusion pump 3130 has been auto-programmed and the caregiver 3132 has confirmed the settings. The MMU server 3108 may communicate to the POC system 3125 and/or at the infusion pump 3130 the actual Rate, VTBI, and Duration. A notation at the bottom of the screen of the POC client and/or the infusion pump may indicate that the infusion pump 3130 is running. The infusion pump 3130 may compare and give a visual, audio, or other type of affirmative signal if the pump information matches or acceptably corresponds with the ordered information. An initial determination of whether the pump information matches the order may be done in the MMU server 3108 and communicated to the POC client 3126 through the POC server 3124. Alternatively, the POC server 3124 or the infusion pump 3130 may make the necessary comparisons. If the pump information does not match the order, the infusion pump 3130 at the display 88 may output a visual, audio, or other type of negative signal, which may include an error message.

The caregiver 3132 may be prompted to review and press a save button on the infusion pump 3130 if the order has been begun as desired or any variations are acceptable. The MMU server 3108 may receive status, event, differences, and variation information from the infusion pump 3130 and pass such information to the POC system 3125. In a separate subsequent step, the nurse may electronically sign the record and presses a send button on the POC client 3126 to send the information to the patient's electronic medication record (EMR) or medication administration record (MAR).

Other Environments

FIG. 1 illustrates one example environment in which the various display synchronization techniques of the present disclosure may be utilized. However, the embodiments described herein are not limited to such an environment, and may be applied to any network environment including one or more networked devices having a display. An example system that may be implemented in one or more of such network environments to provide synchronized display of screen content is described below with reference to FIG. 2.

System Overview

FIG. 2 is a block diagram of an example network environment 200, which includes an arrangement of computer hardware and software components that may be used to implement aspects of the present disclosure. The network environment 200 may include many more (or fewer) elements and/or sub-elements than those shown in FIG. 2. It is not necessary, however, that all of these elements be shown in order to provide an enabling disclosure. As illustrated in FIG. 2, the network environment 200 includes a server 202 and networked devices 204A-C (collectively referred to herein as networked device 204 or networked devices 204).

Server

The server 202 includes a device manager 202A configured to manage the networked devices 204, screen content management rules 202B governing how screen content displayed and changed on networked devices 204, and a server clock 202C configured to maintain a reference time for the network environment 200. The server 202 may include additional components not illustrated in FIG. 2. In some embodiments, the server 202 may omit one or more of the components illustrated in FIG. 2.

The device manager 202A may be a software module or application that is configured to perform certain control functions with respect to the networked devices 204. In some embodiments, the device manager 202A is a computing device including circuitry for executing computer instructions and performs one or more functions described herein (e.g., sending clock information to the individual networked devices, sending screen content settings or parameters to the individual networked devices, etc.). The device manager 202A generally initiates, performs, coordinates, and/or controls various management operations with respect to the networked devices 204.

The screen content management rules 202B may include one or more parameters to be used to control the screen content display at the individual networked devices. For example, the screen content management rules 202B may specify which information, metrics, or other screen content should be displayed and the order in which such information should be displayed on the individual networked devices. In a clinical care setting, the screen content management rules 202B may specify that the networked devices in Clinical Care Area X (e.g., emergency room) should display metrics A, B, and D for 5 seconds each (e.g., display A for 5 seconds, then display B for 5 seconds, then display D for 5 seconds, and then display A again for 5 seconds, etc.), and that networked devices in Clinical Care Area Y (e.g., intensive care unit) should display metrics A and E, 10 seconds each (e.g., display A for 10 seconds, then display E for 10 seconds, then display A again for 10 seconds, etc.).

The server clock 202C may be a clock that keeps track of a reference time to which the individual networked devices in the network environment are synchronized. For example, the reference time according to the server clock 202C may be transmitted to the networked devices 204 according to a schedule (e.g., periodically), based on a user input received by the server 202, or in response to a request received from the individual networked devices 204. For example, a screen content manager of the networked device 204 may be configured to request the reference time from the server 202 according to a schedule (e.g., every 24 hours, every week, every month, etc.) or based on a user input received by the networked device 204.

Although the server 202 is illustrated in FIG. 2 as including the server clock 202C that keeps track of the reference time for the networked devices 204, in other embodiments, the network environment 200 may not include the server 202, and the networked device 204 may synchronize or calibrate its internal clock by communicating an entity outside the network environment 200. In some cases, the networked device 204 does not synchronize or calibrate its internal clock by communicating with another entity.

Networked Device

The networked device 204A includes a screen content manager 206A, screen content settings 208A, an internal clock 210A, and screen content 212A. The networked device 204B includes a screen content manager 206B, screen content settings 208B, an internal clock 210B, and screen content 212B. The networked device 204C includes a screen content manager 206C, screen content settings 208C, an internal clock 210C, and screen content 212C. In the present disclosure, networked devices 204A-C may individually or collectively be referred to as networked device 204 or networked devices 204, screen content managers 206A-206C may individually or collectively be referred to as screen content manager 206 or screen content managers 206, screen content settings 208A-208C may individually or collectively be referred to as screen content settings 208, internal clock 210A-210C may individually or collectively be referred to as internal clock 210 or internal clocks 210, and screen contents 212A-212C may individually or collectively be referred to as screen content 212 or screen contents 212. The networked device 204 may include additional components not illustrated in FIG. 2. For example, the networked device 204 may include one or more components configured to perform a medical function such as delivering a drug to a patient or monitoring such delivery. In some embodiments, the networked device 204 may omit one or more of the components illustrated in FIG. 2.

The screen content manager 206 may be a software module or application that is configured to perform certain functions described herein as being performed by the networked devices 204. In some embodiments, the screen content manager 206 includes circuitry for executing computer instructions and performs one or more functions described herein.

The screen content settings 208 may include one or more parameters to be used to control the screen content display at the individual networked devices. Such parameters may be received from the server 202 or inputted at the networked device 204.

The internal clock 210 may be a clock maintained by the networked device 204, and the internal clock 210 in the individual networked devices may periodically be synchronized with the server clock 202C at the server 202. Such synchronization may occur according to a schedule (e.g., periodically), based on a user input received by the server 202, or based on a user input received by the networked device 204. For example, the screen content manager 206 may be configured to request the reference time from the server 202 according to a schedule (e.g., every 24 hours, every week, every month, etc.) or based on a user input received by the networked device 204.

In some embodiments, the internal clock 210 of the individual networked devices are synchronized with the server clock 202C dynamically based on how quickly the internal clock 210 becomes out of sync. For example, when the networked device 204A sends a clock synchronization request to the server 202, and the server 202 transmits a clock synchronization signal to the networked device 204A, the networked device 204A may update the internal clock 210A using the received clock synchronization signal. In some cases, instead of updating the internal clock 210A, the networked device 204 may calculate an offset between the server clock 202C and the internal clock 210A, and apply the offset when determining the current time (e.g., for identifying the screen content to be displayed). Additionally, the networked device 204A may calculate the difference between the time according to the internal clock 210A prior to the synchronization and the time indicated by the clock synchronization signal (or the time according to the server clock 202C). If the difference is greater than a threshold amount (e.g., 1 second, 5 seconds, 10 seconds, etc.), the networked device 204A may increase the frequency at which the networked device 204A requests synchronization of the internal clock 210A with the server clock 202C. For example, if the time elapsed between the last two synchronizations was 5 days, and the time difference was 2 seconds, the networked device 204A may request the next synchronization 2 or 3 days (e.g., less than 5 days) after the most recent synchronization. If the networked device 204A determines that, after synchronizing the clocks 2 days after the most recent synchronization, the time difference fell below the threshold amount of drift (e.g., 1 second), then the networked device 204A may continue to request synchronization every 2 days. If the time difference was still above the threshold amount of drift, the networked device 204A may further increase the synchronization frequency (e.g., to 1 day, to 12 hours, or some other duration less than 2 days).

In some embodiments, the individual networked devices each have a different synchronization schedule. For example, the networked device 204A may request synchronization every 2 days, the networked device 204B may request synchronization every 3 days, and the networked device 204C may request synchronization every 5 days. In such cases, the time at which the individual networked devices are synchronized with the server clock 202C may not be identical or may not overlap with each other. In some embodiments, the schedule at which the individual networked devices are synchronized with the server clock 202C is non-periodic. In some cases, the threshold amount of drift is set to a value that is substantially lower than the content display period (e.g., 1%, 5%, 10%, etc.). For example, if the metrics are rotated every 10 seconds, the difference of 0.1 second among the display times of the networked devices may be acceptable or negligible (e.g., the networked device 204A switching from “volume infused” to “rate” at 11:20:00.01 in reference time and the networked device 204B switching from “volume infused” to “rate” at 11:20:00.00 in reference time, where the networked devices continue to display “rate” until 11:20:10.01 and 11:20:10.00 in reference time, respectively). Although some examples of clock synchronization were described as being requested by the networked devices, in other examples, the clock synchronization may be requested by the server 202.

Time according to the internal clocks of the individual networked devices may be measured from the same reference point. For example, each internal clock is configured to output a current time indicative of the number of seconds elapsed since year 1900 (e.g., over 3 million seconds). In some embodiments, the reference point shared by the internal clocks is periodically updated so that time-based calculations involve smaller numbers. Although some clock synchronization techniques described with reference to FIG. 2 uses a server clock 202C, in some implementations, the internal clocks 210 may be synchronized using a network time protocol (NTP). In such implementations, the networked devices 240 may communicate with an NTP server to update their internal clocks 210 (e.g., periodically or aperiodically). Alternatively or additionally, the networked devices 240 may synchronize the internal clocks 210 using an atomic clock.

The screen content 212 may include one or more metrics calculated or maintained by the individual networked devices. For example, such metrics may include the volume of the medication infused so far, the volume of the medication to be infused, the rate at which the medication is being infused, and the like. The metrics may also include any other metrics or parameters described herein.

Centralized Display

In some embodiments, the network environment 200 of FIG. 2 may include a centralized display that can display the screen content associated with multiple networked devices 204. For example, the screen of the centralized display may be divided into multiple portions that can each display the screen content associated with a specific networked device 204. In some cases, the multiple networked device 204 whose screen content is displayed on the centralized display may be from multiple geographic locations (e.g., two or three different CCAs) and as a result may be configured to cycle through different metrics in different display order. In some embodiments, the centralized display may display the same metric for each networked device 204 whose screen content is displayed on the centralized display. For example, if the networked devices 204 in an emergency room are configured to cycle through rate and time, and the networked device 204 in an intensive care unit are configured to cycle through rate and dose, the centralized display configured to display the screen content associated with all of the networked devices 204 in the emergency room and the intensive care unit may cycle through rate, time, and dose for all such networked devices 204 (e.g., a union of the different sets of metrics). In some cases, the centralized display may cycle through all of the available metrics regardless of the characteristics of the individual networked devices 204. Alternatively, the centralized display may not display the same metric for each networked device 204, and cycle through rate and time for the networked devices 204 in the emergency room and cycle through rate and dose for the networked devices 204 in the intensive care unit. In some implementations, the centralize display provides an indication of the CCA associated with the individual metrics displayed on the centralized display. For example, the metrics associated with the networked devices 204 in the emergency room may look different from the metrics associated with the networked devices 204 in the intensive care unit (e.g., in location, in size, in color, based on presence of indicators, etc.). The centralized display may be connected to the server 202, or to another server not illustrated in FIG. 2 that is in network communication with the server 202.

Architecture of Networked Device

With reference to FIG. 3, the components of an example networked device are described in greater detail. The example architecture of the networked device 304 depicted in FIG. 3 includes an arrangement of computer hardware and software modules that may be used to implement aspects of the present disclosure. The networked device 304 may include many more (or fewer) elements and/or sub-elements than those shown in FIG. 3. It is not necessary, however, that all of these elements be shown in order to provide an enabling disclosure.

As illustrated, the networked device 304 includes a display 306, a processor 308, a network interface 310, and a memory 312, all of which may communicate with one another by way of a communication bus. The display 306 may display information generated or stored by the networked device 304 or any other information associated with the networked device 304. For example, the networked device may be an infusion pump being used to deliver medication to a patient. In such a case, the display 306 may display the volume of the medication infused so far, the volume of the medication to be infused, the rate at which the medication is being infused, and the like. The processor 308 may receive information and instructions from other computing systems or services via a network. The processor 308 may also transmit information to and receive information from the memory 312 and further provide content to the display 306 for display. The network interface 310 may provide connectivity to one or more networks or computing systems in the network environment described herein. For example, the network interface 310 may be a serial port, a parallel port, or any other communication interface that can enable or facilitate wired or wireless communication according to any communication protocols such as Zigbee (e.g., IEEE 802.15.4), Bluetooth, Wi-Fi (e.g., IEEE 802.11), Near Field Communication (NFC), and the like.

The memory 312 may contain computer program instructions (grouped as modules in some embodiments) that the processor 308 can execute in order to implement one or more aspects of the present disclosure. The memory 312 may include RAM, ROM, and/or other persistent, auxiliary, or non-transitory computer-readable media. In some embodiments, the memory 312 stores an operating system that provides computer program instructions for use by the processor 308 in the general administration and operation of the networked device 304. As illustrated in FIG. 3, the memory 312 may include a clock synchronization module 312A, a current time determination module 312B, a screen content identifier calculation module 312C, and screen content data 312D. In some embodiments, the clock synchronization module 312A, the current time determination module 312B, and the screen content identifier calculation module 312C may, when executed by the processor 308, individually or collectively implement various aspects of the present disclosure. Although shown as distinct modules, in some embodiments, the division of the modules into the clock synchronization module 312A, the current time determination module 312B, and the screen content identifier calculation module 312C is logical in nature, and a single software application executing on the networked device 304 may, when executed by the processor 308, perform some or all of the steps described as being performed by the modules. For example, each of the clock synchronization module 312A, the current time determination module 312B, and the screen content identifier calculation module 312C may be part of the screen content manager 206.

The clock synchronization module 312A facilitates synchronization between the server clock 202C and the internal clocks maintained by the individual networked devices 204. The current time determination module 312B facilitates determination of the current time associated with the internal clock 210. For example, the current time determination module 312B may determine the current time indicated by the internal clock 210 maintained and updated by the clock synchronization module 312A. The screen content identifier calculation module 312C facilitates determination of the screen content to be displayed at any given time. For example, the screen content identifier calculation module 312C calculates a screen content identifier based on the current time determined by the current time determination module 312B.

Although not shown in FIG. 3, the networked device 304 may further include one or more input devices such as a touch screen, mechanical buttons, or a voice recognition system. Further, the networked device 304 may include one or more additional storage devices for storing data generated by the networked device 304 or other data utilized in implementing aspects of the present disclosure.

Near View and Far View

Graphical user interfaces for medical devices that display patient and treatment information have improved clinician efficiency when caring for patients. However, a challenge for designing graphical user interfaces is balancing the amount of information displayed with readability and user-friendliness. Presenting too much information may impede the interaction between the user and the device. In some embodiments, two screen modes may be utilized to present more information when the user is interacting with the device in one mode (e.g., “near view”), and to present less information when the user is simply viewing the device from far away (e.g., “far view”). Near view screens may present user interface buttons, fields, and keys to allow the user to input various commands, whereas far view screens may simply show a single metric that the user may be interested in reviewing from far away. Far view screens may be activated after a period of inactivity (e.g., lack of user input) and may cycle through numerous metrics that are relevant to the clinical setting.

Comparison of Synchronized and Non-Synchronized Displays

With reference now to FIG. 4, example network environments 400A and 400B will be described. The network environment 400A includes networked devices 402A and 404A that are positioned side by side, and the network environment 400B includes networked devices 402B and 404B that are positioned side by side.

In the top row in FIG. 4, the display of the networked device 402A shows the rate at which the medication is being delivered to the patient, and the display of the networked device 404A shows the time remaining until the medication delivery is finished. As shown, the displays of the networked devices 402A and 40A are not in sync with each other, since the screen content (e.g., the type of metric displayed) of the networked device 402A does not match the screen content (e.g., the type of metric displayed) of the networked device 404A. When the displays of the networked devices are not in sync, it is difficult for the caregiver (e.g., doctor or nurse) to quickly scan the displays and gather relevant information from multiple networked devices, especially if a large number of networked devices are present in the room.

In FIG. 4, the arrows between the rows in FIG. 4 indicate the passage of time (e.g., 1 second, 5 seconds, 1 minute, etc.). After some time has passed, in the middle row, the display of the networked device 402A continues to show the rate, whereas the display of the networked device 404A switches to displaying the volume infused. As illustrated, not only are the two displays out of sync, they also switch at different times.

After some additional time has passed, in the bottom row, the display of the networked device 402A switches to displaying the time remaining, whereas the display of the networked device 404A continues to show the volume infused. When the displays of the networked devices switch to different screen content at different times, it is difficult for the caregiver (e.g., doctor or nurse) to quickly scan the displays and gather relevant information from multiple networked devices, especially if a large number of networked devices are present in the room.

In contrast, as illustrated in FIG. 4, the displays of the networked devices 402B and 404B of the network environment 400B are in sync with each other (e.g., both displaying the rate in the top row, the time remaining in the middle row, and the volume infused in the bottom row). Further, the displays of the networked devices 402B and 404B switch to the next metric at the same time (or at substantially the same time). Thus, the displays of the networked devices 402B and 404B are much easier for a caregiver to scan, especially from afar in a room filled with a large number of such networked devices.

Screen Content Update Method

With reference now to FIG. 5, an example screen content update method 500 will be described. The example method 500 may be carried out, for example, by the networked device 204 of FIG. 2 (or one or more components thereof) or the networked device 304 of FIG. 3 (or one or more components thereof). The method 500 illustrates an example algorithm that may be programmed, using any suitable programming environment or language, to create machine code capable of execution by a CPU or microcontroller of the networked device 204. Various embodiments may be coded using assembly, C, OBJECTIVE-C, C++, JAVA, or other human-readable languages and then compiled, assembled, or otherwise transformed into machine code that can be loaded into read-only memory (ROM), erasable programmable read-only memory (EPROM), or other recordable memory of the networked device 204 that is coupled to the CPU or microcontroller and then then executed by the CPU or microcontroller. For convenience, the steps of the example method 500 are described as being performed by the networked device 204.

At block 502, the networked device 204 determines delivery metric display data from the server 202. The delivery metric display data may include information needed or used to identify the screen content to be displayed on the networked device 204. For example, the delivery metric display data may include the identity and type of delivery metrics to be displayed and the duration for which each delivery metric is to be displayed. In some embodiments, the server 202 has a record of the CCA in which the networked device 204 is located, and the server 202 transmits, based on the CCA associated with the networked device 204, data indicative of which one(s) of the available metrics should be displayed on the networked device 204. For example, the networked device 204 may transmit data indicative of the CCA of the networked device 204 to the server 202 upon entry (e.g., by a caregiver) or detection (e.g., using one or more sensors on the networked device 204) of the CCA. Alternatively, some or all of the delivery metric display data may not be received, and a corresponding default value may be used. For example, if the delivery metric display data received from the server 202 includes an indication of the identity of the delivery metrics to be displayed, but does not include the duration for which each delivery metric is to be displayed, a default value stored on the networked device 204 may be used (e.g., 5 seconds, 10 seconds, or any other value). In some cases, the delivery metric display data may be provided to the networked device 204 by other means such as manual input from a user, copied from a storage device, and so on. The networked device 204 may receive the delivery metric display data from the server 202 according to a predetermined schedule, periodically or aperiodically. In some embodiments, the networked device 204 may receive the delivery metric display data from another source, such as an internal or external storage device or via a manual input from the user of the networked device 204.

At block 504, the networked device 204 determines a first current time based on the internal clock 210. For example, the networked device 204 may determine the current time in response a determination that the screen content should be changed. Such a determination may be made by the networked device 204 in response to detecting a period of inactivity (e.g., when the networked device 204 is switching to screen saver mode). Alternatively or additionally, such a determination may be made by the networked device 204 according to a schedule (e.g., every 5 seconds, every 10 seconds, every minute, etc.). The current time determined using the internal clock 210 may be in the traditional hh:mm:ss format. In other cases, the current time is represented in hours, minutes, seconds, milliseconds, or another unit of time.

At block 506, the networked device 204 identifies a first delivery metric to be displayed on the display of the networked device 204. Identifying the first delivery metric may involve calculating a delivery metric index value and determining the first delivery metric using the delivery metric index value (e.g., by indexing into a list of delivery metrics). For example, if the calculated delivery metric index value is 3, and the list of delivery metrics maintained by the networked device 204 is {dose, rate, volume infused, volume to be infused, time remaining}, the networked device 204 may identify “volume to be infused” as the first delivery metric. Although relevant metrics for an infusion pump are used in this example, any other number and type of metrics, statistics, or information may be cycled through via the display of the networked device 204.

In some embodiments, the delivery metric index value is calculated as follows:

(delivery metric index value)=trunc((T_{elapsed_seconds_in_system_time}mod (N_{metrics_available}*T_{display_period_length}))/T_{display_period_length}) Equation(1)
(delivery metric index value)=trunc((T_{elapsed_seconds_in_system_time}mod (N_{metrics_available}*T_{display_period_length}))/T_{display_period_length})+1 Equation (2)

In Equation (1), T_{elapsed_seconds_in_system_time}represents the number of seconds elapsed according to the internal clock maintained by the networked device 204, N_{metrics_available}represents the number of metrics available for display, and T_{display_period_length}represents the length of each content display period in seconds.

“trunc” represents the truncation operation, which removes the digits right of the decimal point. For example, trunc (3.5) would equal 3. “mod” represents the modulo operation, which finds the remainder after division of one number by another. For example, 7 mod 3 would equal 1, since 7 divided by 3 would leave a quotient of 2 and a remainder of 1.

Equation (2) is a variation of Equation (1), and the only difference is that 1 is added such that the lowest value of (delivery metric index value) is 1 instead of 0. In Equation (1), “delivery metric index value” of 0 corresponds to the first one of the available metrics, and in Equation (2), “delivery metric index value” of 1 corresponds to the first one of the available metrics.

Although T_{elapsed_seconds_in_system_time}is used in Equation (1), in some embodiments, the current time used to identify the first delivery metric is not in seconds but in a different unit (e.g., milliseconds, minutes, hours, or some other temporal unit). In some cases, N_{metrics_available}represents the number of all metrics that the networked device 204 is configured to display. For example, if the networked device 204 is configured to cycle through {dose, rate, volume infused, volume to be infused, time remaining} every time, the networked device 204 may determine that N_{metrics_available}is equal to 5. In other cases, N_{metrics_available}represents the number of metrics in a subset that includes some but not all of the metrics that the networked device 204 is configured to display. The metrics in such a subset may be determined based on one or more conditions (e.g., location of the networked device 204, CCA, class or type of medication, or any other parameter associated with the networked device 204). For example, based on a determination that the CCA associated with the networked device 204 is “neonatal intensive care unit” and based on a determination that only {dose, volume infused, volume to be infused} should be displayed for “neonatal intensive care unit,” the networked device 204 may determine that the number of metrics in the subset is 3 (e.g., out of 5 metrics). In some embodiments, the networked device 204 downloads the number and type of metrics to be displayed for a given CCA and the length of the content display period for the given CCA from the server 202. Such a download may take place upon the CCA of the networked device 204 being entered or changed by a user of the networked device 204 (e.g., caregiver, administrator, operator, etc.).

Table 1 illustrates example calculations for identifying screen content to be displayed. For this particular networked device 204, three metrics are to be displayed in sequence for 2 seconds each. As shown in Table 1, for the 2000^thand 2000 seconds (e.g., from 2000.00 seconds in system time through 2001.99 in system time), the metric corresponding to an index value of “1” is displayed, for the 2002^ndand 2003^rdseconds, the metric corresponding to an index value of “2” is displayed, and for the 2004^thand 2005^thseconds, the metric corresponding to an index value of “0” is displayed, and for the 2006^thand 2007^thseconds, the metric corresponding to an index value of “1” is displayed again, for the 2008^thsecond, the metric corresponding to an index value of “2” is displayed again, and so on. According, in the example of Table 1, three variables (labeled A, B, and C) are used to identify the screen content to be displayed at a given point in time.

TABLE 1

Example calculations for identifying screen content to be displayed

A: number of metrics
3

B: content display period (in seconds)
2

C: current time (in seconds)
2000
2001
2002
2003
2004
2005
2006
2007
2008

C mod (A*B)
2
3
4
5
0
1
2
3
4

(C mod (A*B))/B
1
1.5
2
2.5
0
0.5
1
1.5
2

trunc ((C mod (A*B))/B)
1
1
2
2
0
0
1
1
2

At block 508, the networked device 204 displays the first delivery metric identified at block 506. The display of the first delivery metric may occur at a first time and may continue for the duration (e.g., content display period) specified by the delivery metric display data (or a default duration). Based on the duration for which the first delivery metric is to be displayed, the networked device 204 may perform the following steps such that the display of the delivery metric to be displayed immediately subsequent to the first delivery metric (e.g., the second delivery metric identified at block 512) occurs at a second time that is a specific time period equal to the duration away from the first time at which the first delivery metric was displayed. In some embodiments, none of blocks 504-508 is performed in response to a request, instruction, signal, or communication from the server 202. Alternatively, in some other embodiments, one or more of blocks 504-508 are performed in response to a request, instruction, signal, or communication from the server 202.

At block 510, the networked device 204 determines a second current time based on the internal clock 210. For example, the networked device 204 may determine the current time in response a determination that the screen content should be changed. The determination that the screen content should be changed may be made periodically (e.g., at every second, before each second expires, etc.). In some cases, the networked device 204 may start a timer (e.g., an event timer based on a hardware interrupt or a software interrupt) at the first time at which the first delivery metric is displayed for the duration for which the first delivery metric is to be displayed. When the timer expires, the networked device 204 may determine the second current time. In some cases, the networked device 204 may determine the second current time a specific time period (e.g., 1 second, 5 seconds, or any other time period) before the timer expires. Alternatively, the networked device 204 may set the timer for a duration that is shorter than the duration for which the first delivery metric is to be displayed by a specific time period (e.g., 1 second, 5 seconds, or any other time period). In some cases, the networked device 204 may set the timer at the time of determining the first delivery metric. In some other cases, the networked device 204 may calculate the second current time by adding the duration for which the first delivery metric is to be displayed to the first current time determined at block 504. In such cases, the networked device 204 may determine the current time based on the internal clock 210 once in connection with the initially displayed screen content, and determine the timing of each subsequent screen content by (without accessing the internal clock 210) adding the content display period (e.g., 5 seconds) to the time at which the initially displayed screen content is to be replaced with the next screen content (which can be, for example, 3 seconds from the time the screen content is initially displayed). The networked device 204 may determine the display order based on the predetermined order in which the different screen contents or metrics are arranged (e.g., in the order that the delivery metrics appear in FIG. 7, or in some other order). By not having to re-calculate the display metric index at every second or at every content display period, processing power and other computing resources used to update the screen content can be reduced. Alternatively, by accessing the internal clock 210 at every second or at every content display period, the screen content update process can be more fault-tolerant (e.g., if the networked device 240 for some reason displays the wrong screen content for one content display period, the networked device 240 can still display the correct screen content at the next content display period because the networked device 240 does not rely on any determinations from the previous content display period.)

At block 512, the networked device 204 identifies a second delivery metric to be displayed on the display of the networked device 204. In some embodiments, the networked device 204 determines the second delivery metric using one or more techniques described above in connection with block 506. In other embodiments, the networked device 204 identifies the second delivery metric by determining the next delivery metric in a list that includes all the delivery metrics to be displayed (e.g., cycled through) by networked device 204. For example, in the example illustrated in Table 1, after determining that the delivery metric to be displayed for the 2000^thsecond is delivery metric “1”, the networked device 204 may determine that the second delivery metric is the next one in the list of delivery metrics (e.g., delivery metric “2” if the list contains more than 2 items, or delivery metric “0” if the list contains only two items).

At block 514, the networked device 204 replaces the first delivery metric displayed on the display with the second delivery metric identified at block 512. Although not illustrated in FIG. 5, blocks 510-514 may be repeated to identify and display additional delivery metrics on the networked device 204. The method 500 may end upon detecting a user input on the networked device 204, upon detecting an error or interrupt routine, upon finishing a given task (e.g., infusion pump finishing the delivery of medication to the patient) or after a predetermined time period. In some embodiments, none of blocks 510-514 is performed in response to a request, instruction, signal, or communication from the server 202. Alternatively, in some other embodiments, one or more of blocks 510-514 are performed in response to a request, instruction, signal, or communication from the server 202.

In the method 500, one or more of the blocks shown in FIG. 5 may be removed (e.g., not performed) and/or the order in which the method 500 is performed may be switched. In some embodiments, additional blocks may be added to the method 500. For example, although not shown in FIG. 5, the networked device 204 may receive reference time information from the server 202 and synchronize its internal clock based on the received information. Although the method 500 is described in the context of displaying delivery metrics, the techniques described herein can be extended to displaying other screen content. The embodiments of the present disclosure are not limited to or by the example shown in FIG. 5, and other variations may be implemented without departing from the spirit of this disclosure.

Examples of Networked Devices

Although some embodiments of the present disclosure are described with respect to infusion pumps, the techniques described herein may be extended to other medical devices or networked devices. For example, one or more networked devices describe herein may be patient care monitors configured to display blood pressure, heart rate, blood oxygenation, and the like. Additionally or alternatively, one or more networked devices described herein may be a smartphone or tablet executing an application configured to display the screen content according to one or more aspects of the present disclosure (e.g., based on an internal clock of the smartphone or tablet and based on parameters received from the server 202 or another centralized server). Displaying such screen content may be synchronized with one or more other networked devices in the network environment.

Synchronized Metric Switching Method

With reference now to FIG. 6, an example synchronized metric switching method 600 will be described. The example method 600 may be carried out, for example, by the networked device 204 of FIG. 2 (or one or more components thereof) or the networked device 304 of FIG. 3 (or one or more components thereof). The method 600 illustrates an example algorithm that may be programmed, using any suitable programming environment or language, to create machine code capable of execution by a CPU or microcontroller of the networked device 204. Various embodiments may be coded using assembly, C, OBJECTIVE-C, C++, JAVA, or other human-readable languages and then compiled, assembled, or otherwise transformed into machine code that can be loaded into read-only memory (ROM), erasable programmable read-only memory (EPROM), or other recordable memory of the networked device 204 that is coupled to the CPU or microcontroller and then then executed by the CPU or microcontroller. For convenience, the steps of the example method 600 are described as being performed by the first networked device and/or the second networked device. In some embodiments, the first and second networked devices share one or more characteristics (e.g., CCA, medication, class of medication, patient, network environment, and/or others).

At block 602, the first networked device enters screen saver mode. The first networked device may enter screen saver mode upon detecting inactivity (or no activity) at the first networked device for a specific time period (e.g., inactivity for 1 minute, for 5 minutes, or for any other duration). Inactivity may include not receiving any user input on the first networked device.

At block 604, the first networked device displays metric #1. For example, the first networked device may identify metric #1 using one or more techniques described above in connection with the method 500. The first networked device may determine, upon entering screen saver mode, the current time associated with its internal clock 210, calculate the metric index value associated with the metric to be displayed, and display the identified metric on its display.

At block 606, the first networked device switches to metric #2. For example, the first networked device may identify metric #2 using one or more techniques described above in connection with the method 500, and replace metric #1 with metric #2.

At block 608, while the first networked device is displaying metric #2, the second networked device enters screen saver mode. The second networked device may enter screen saver mode upon detecting inactivity (or no activity) at the second networked device for a specific time period (e.g., inactivity for 1 minute, for 5 minutes, or for any other duration). Inactivity may include not receiving any user input on the second networked device.

At block 610, the second networked device displays metric #2. For example, the second networked device may identify metric #2 using one or more techniques described above in connection with the method 500. The second networked device may determine, upon entering screen saver mode, the current time associated with its internal clock 210, calculate the metric index value associated with the metric to be displayed, and display the identified metric on its display. Even though the first networked device displayed metric #1 after entering screen saver mode, by the time the second networked device has entered screen saver mode, the internal clocks 210 of the first and second networked devices have reached a time period during which metric #2 should be displayed on both of the first and second networked devices. At the time the second networked device displays metric #2, both of the first and second networked devices are di splaying metric #2.

At block 612, the first networked device switches to metric #3 after displaying metric #2 for a specific time period (e.g., duration for which the first networked device is configured to display metric #2 or each metric). Further, the second networked device switches to metric #3 after displaying metric #2 for another time period that is shorter than the specific time period for which the first networked device displayed metric #2. In some embodiments, the first networked device and the second networked device do not rely on a signal transmitted by the server 202 to determine when to switch to the next metric and the first networked device and the second networked device do not communicate with each other to synchronize the metric switching. In such embodiments, even without such signal from the server 202 or inter-device communication, the first and second networked devices switch to metric #3 at the same time (or at substantially the same time). Alternatively, in some other embodiments, the first networked device and the second networked device do rely on a signal transmitted by the server 202 to determine when to switch to the next metric and/or the first networked device and the second networked device do communicate with each other to synchronize the metric switching.

In some cases, the time at which the first networked device switches to metric #3 is different from the time at which the second networked device switches to metric #3 due to the difference in the internal clock of the first networked device and the internal clock of the second networked device. For example, the time difference may be a non-zero value that is less than 1 second. In some embodiments, a first time difference between the time at which the first networked device switches to metric #3 and the time at which the second networked device switches to metric #3 is equal to a second time difference between the time at which the first networked device subsequently switches from metric #3 to metric #4 and the time at which the second networked device subsequently switches from metric #3 to metric #4. Alternatively, in some other embodiments, a first time difference between the time at which the first networked device switches to metric #3 and the time at which the second networked device switches to metric #3 is different from a second time difference between the time at which the first networked device subsequently switches from metric #3 to metric #4 and the time at which the second networked device subsequently switches from metric #3 to metric #4 (e.g., due to the internal clocks becoming out of sync with the server clock 202C at different rates). Although not illustrated in FIG. 6, blocks 510-514 of FIG. 5 may be performed by each of the first and second networked devices to identify and display additional metrics.

In the method 600, one or more of the blocks shown in FIG. 6 may be removed (e.g., not performed) and/or the order in which the method 600 is performed may be switched. In some embodiments, additional blocks may be added to the method 600. Although the method 600 is described in the context of screen saver mode, the techniques described herein can be extended to screen content switching in any other mode (e.g., when the networked device is turned on, upon detecting user input indicating that the networked device should begin displaying and cycling through screen content, and so on). The embodiments of the present disclosure are not limited to or by the example shown in FIG. 6, and other variations may be implemented without departing from the spirit of this disclosure.

Example User Interface

FIG. 7 illustrates an example user interface 700 for specifying the screen content management rules for a given CCA. As shown, the user interface 700 includes a checkbox for indicating whether screen saver mode is to be enabled for the given CCA, and additional checkboxes for specifying which metrics are to be cycled through in screen saver mode. Further, the user interface 700 includes a field for specifying the content display period (e.g., the duration for which each metric is to be displayed before switching to the next metric). The specified screen content management rules may be transmitted to all of the individual networked devices in the network environment, or only to those associated with the given CCA.

Although the user interface 700 is described in the context of a CCA-specific screen content display scheme, in other embodiments, the screen content display can be specific to one or more other characteristics of the networked device. For example, the number and type of metrics to be cycled through may be drug-specific (e.g., infusion pumps delivering drug “A” may cycle through different type and number of metrics than infusion pumps delivering drug “B”), drug-class-specific (e.g., infusion pumps delivering vasoactive drugs may cycle through different type and number of metrics than infusion pumps delivering anti-infective drugs), CCA-specific (e.g., infusion pumps in operating rooms may cycle through different type and number of metrics than infusion pumps in emergency rooms), patient-specific (e.g., infusion pumps connected to patient “X” may cycle through different type and number of metrics than infusion pumps connected to patient “Y”) or any combination-specific such as CCA-drug-specific, CCA-drug-class-specific, and so on (e.g., infusion pumps in operating rooms and delivering vasoactive drugs may cycle through different type and number of metrics than infusion pumps in operating rooms and delivering anti-infective drugs, etc.).

In some embodiments, one or more metrics may not be available for a given drug or drug-class. For example, if the screen content switching is set to be CCA-specific, and networked devices in emergency rooms are configured (e.g., based on the parameters/settings downloaded from the server 202) to cycle through rate, dose, and volume infused. In a particular emergency room, there are two infusion pumps delivering drug “A” and drug “B,” respectively. However, if drug “B” cannot be or typically is not administered in a dose-fashion, the infusion pump delivering drug “B” may display the rate for the duration during which the dose is supposed to be displayed. For example, if the screen content switching interval is 10 seconds, the infusion pump delivering drug “A” may display the rate for 10 seconds, the dose for 10 seconds, and the volume infused for 10 seconds and so on. In contrast, the infusion pump delivering drug “B” may display the rate for 20 seconds and the volume infused for 10 seconds and so on (based on the inability to display the dose for drug “B”).

Technical Advantages

As described above, in some embodiments, the individual networked devices in the network environment cause their respective screen content to be changed in response to a heartbeat signal received from the server. For example, the server may transmit a heartbeat signal to each networked device every 5 minutes, indicating that the networked device should change the displayed content or display the next content in a given display order. The heartbeat signal may also indicate which content the networked device should display (e.g., by including a content identifier in the heartbeat signal transmitted to the networked device). However, such use of heartbeat signals can consume valuable network resources (e.g., bandwidth) and overwhelm the network, especially if the network includes a large number of such networked devices. Further, processing such heartbeat signals from the server may require a sophisticated processor on the networked device and/or consume valuable processing power. Displaying the screen content based on an internal clock maintained by the individual networked devices and without communicating with the server each time new screen content needs to be displayed, the amount of data transmitted across the network environment may be significantly reduced and valuable network resources and/or processing power can be preserved for other uses.

In other embodiments, the individual networked devices locally store a fixed schedule of which metric to display at what time. In such embodiments, a networked device may store a table that specifies, for each CCA, which metric to display at a given time of day. For example, the table may specify that for networked devices in the ICU should display metric #1 for the first 10 minutes of every hour, metric #2 for the second 10 minutes, metric #3 for the third 10 minutes, and so on, and for networked devices in the OR should display metric #3 for the first 30 minutes of every hour, and metric #4 for the second 30 minutes of every hour. As another example, the table may specify, for each 5-second interval in the 24 hours of a given date, the metric to be displayed for the 5-second interval. However, locally storing such a table would consume a large amount of memory or disk space, which may not be desired for networked devices having limited memory/storage. Also, accessing such a table that is stored remotely over a network can consume valuable network resources (e.g., bandwidth) and overwhelm the network, especially if the network includes a large number of such networked devices. Displaying the screen content based on an internal clock maintained by the individual networked devices and without storing or accessing large amounts of data specifying the screen content to be displayed at any given interval, the amount of storage space needed and/or data transmitted across the network environment may be significantly reduced and valuable storage/network resources can be preserved for other uses.

Example Embodiments

One aspect of the disclosure provides an apparatus configured to deliver medication to patients. The apparatus may include a display, a processor, and a memory. The memory may store an internal clock data according to which one or more delivery metrics are to be displayed on the display. The memory may further store instructions that, when executed by the processor, configure the processor to: receive delivery metric display data from a server in network communication with the apparatus, wherein the delivery metric display data includes a screen change time interval and an indication of one or more delivery metrics to be displayed; in response to a period of inactivity, determine a first current time based on the internal clock data; identify a first delivery metric based on inputting the first current time into a delivery metric determination function, wherein the delivery metric determination function is configured to identify one of a plurality of delivery metrics to be displayed on the display based on the screen change time interval and the indication of the one or more delivery metrics received from the server; cause the first delivery metric to be displayed on the display at a first time; within the screen change time interval from the first time, determine a second current time based on the internal clock data; identify a second delivery metric different from the first delivery metric based on inputting the second current time into the delivery metric determination function; and cause the first delivery metric displayed on the display to be replaced with the second delivery metric at a second time that is not later than the first time by a time period equal to the screen change time.

The apparatus can further include any sub-combination of one or more of the following features: where the instructions, when executed by the processor, further configure the processor to transmit a clock synchronization request to the server, receive a clock synchronization signal from the server, and update the internal clock data based on the clock synchronization signal; where the instructions, when executed by the processor, further configure the processor to transmit the clock synchronization request to the server according to a predefined schedule; where wherein the instructions, when executed by the processor, further configure the processor to determine that a user input has not been received for a threshold amount of time, and in response to the determination that the user input has not been received for the threshold amount of time, determine the first current time based on the internal clock data; where the instructions, when executed by the processor, further configure the processor to calculate a first delivery metric index value based on the first current time and the screen change time interval, and identify the first delivery metric based on the first delivery metric index and the indication of the one or more delivery metrics to be displayed; where the instructions, when executed by the processor, further configure the processor to calculate the first delivery metric index value based on a modulo operation including the screen change time interval and a number of metrics included in the indication of the one or more delivery metrics to be displayed; where the instructions, when executed by the processor, further configure the processor to determine the second current time before an amount of time equal to the screen change time interval has elapsed since the first time; where the instructions, when executed by the processor, further configure the processor to determine the second current time at a time that precedes the second time by a predefined amount of time; where the instructions, when executed by the processor, further configure the processor to within the screen change time interval from the second time, determine a third current time based on the internal clock data, identify a third delivery metric different from the second delivery metric based on inputting the third current time into the delivery metric determination function, and cause the second delivery metric displayed on the display to be replaced with the third delivery metric at a third time that is not later than the second time by the time period equal to the screen change time interval, such that a first time difference between the first time and the second time is shorter than a second time difference between the second time and the third time; and where the second time difference is equal to the screen change time interval, and the first time difference is shorter than the screen change time interval.

One aspect of the disclosure provides a method of providing synchronized screen content. The method may include: receiving, by a networked device in network communication with a server, metric display data from the server, the metric display data including a screen change time interval and an indication of one or more metrics to be displayed; in response to detecting a period of inactivity, determining a first current time associated with an internal clock of the networked device; calculating a first metric index value based on the first current time and the screen change time interval; displaying a first metric associated with the first metric index value on a display of the networked device at a first time; within the screen change time interval from the first time, determining a second current time associated with the internal clock of the networked device; calculating a second metric index value different from the first metric index value based on the second current time; and replacing the first metric displayed on the display of the networked device with a second metric associated with the second metric index value at a second time that is not later than the first time by a time period equal to the screen change time interval.

The method can further include any sub-combination of one or more of the following features: where the method further includes transmitting a clock synchronization request to the server, receiving a clock synchronization signal from the server, and updating the internal clock based on the clock synchronization signal; where the method further includes transmitting the clock synchronization request to the server according to a predefined schedule; where the method further includes determining that a user input has not been received for a threshold amount of time, and in response to determining that the user input has not been received for the threshold amount of time, determining the first current time associated with the internal clock; where the method further includes calculating the first metric index value based on a modulo operation including the screen change time interval and a number of metrics included in the indication of the one or more metrics to be displayed; where the method further includes determining the second current time before an amount of time equal to the screen change time interval has elapsed since the first time; where the method further includes determining the second current time at a time that precedes the second time by a predefined amount of time; where the method further includes, within the screen change time interval from the second time, determining a third current time associated with the internal clock, calculating a third metric index value different from the second metric index value based on the third current time, and replacing the second delivery metric displayed on the display with a third metric associated with the third metric index value at a third time that is not later than the second time by the time period equal to the screen change time interval, such that a first time difference between the first time and the second time is shorter than a second time difference between the second time and the third time; and where the second time difference is equal to the screen change time interval, and the first time difference is shorter than the screen change time interval.

One aspect of the disclosure provides a system adapted to provide synchronized screen content. The system may include a server and a plurality of networked devices in network communication with the server. Each networked device of the plurality of networked devices may be configured to: receive metric display data from the server, the metric display data including a screen change time interval and an indication of one or more metrics to be displayed; in response to a period of inactivity, determine a first current time associated with an internal clock of the networked device; calculate a first metric index value based on the first current time and the screen change time interval; display a first metric associated with the first metric index value on a display of the networked device at a first time; within the screen change time interval from the first time, determine a second current time associated with the internal clock of the networked device; calculate a second metric index value different from the first metric index value based on the second current time; and replace the first metric displayed on the display of the networked device with a second metric associated with the second metric index value at a second time that is not later than the first time by a time period equal to the screen change time interval.

The system can further include any sub-combination of one or more of the following features: where the networked device is further configured to transmit a clock synchronization request to the server, receive a clock synchronization signal from the server, and update the internal clock based on the clock synchronization signal; where the networked device is further configured to transmit the clock synchronization request to the server according to a predefined schedule; where the networked device is further configured to determine that a user input has not been received for a threshold amount of time, and in response to the determination that the user input has not been received for the threshold amount of time, determine the first current time associated with the internal clock; where the networked device is further configured to calculate the first metric index value based on a modulo operation including the screen change time interval and a number of metrics included in the indication of the one or more metrics to be displayed; where the networked device is further configured to determine the second current time before an amount of time equal to the screen change time interval has elapsed since the first time; where the networked device is further configured to determine the second current time at a time that precedes the second time by a predefined amount of time; where the networked device is further configured to, within the screen change time interval from the second time, determine a third current time associated with the internal clock, calculate a third metric index value different from the second metric index value based on the third current time, and replace the second delivery metric displayed on the display with a third metric associated with the third metric index value at a third time that is not later than the second time by the time period equal to the screen change time interval, such that a first time difference between the first time and the second time is shorter than a second time difference between the second time and the third time; and where the second time difference is equal to the screen change time interval, and the first time difference is shorter than the screen change time interval.

One aspect of the disclosure provides a system adapted to provide synchronized screen content. The system may include a server and a plurality of infusion pumps configured to deliver medications to one or more patients and in network communication with the server. Each respective infusion pump of the plurality of infusion pumps networked devices may include (i) a display configured to display one or more metrics of a plurality of metrics maintained by the respective infusion pump and (ii) a memory configured to store internal clock data usable to determine a current time associated with the respective networked device. The respective infusion pump is configured to: receive a clock synchronization data from the server, wherein the clock synchronization data is indicative of a reference time associated with the server; update the internal clock data based on the clock synchronization data; receive metric display data from the server, wherein the metric display data comprises a metric display period and an indication of two or more metrics to be displayed on the display of the respective networked device; based on a determination that a user input has not been received for a threshold amount of time, determine a first current time associated with the internal clock data; calculate a first metric index based on the first current time, the metric display period, and the indication of the two or more metrics received from the server; determine a first metric of the plurality of metrics that is associated with the first metric index; cause the first metric to be displayed on the display of the respective infusion pump at a first time; within at least the metric display period from the first time, determine a second current time associated with the internal clock data; calculate a second metric index based on the second current time, the metric display period, and the indication of the two or more metrics received from the server; determine a second metric of the plurality of metrics that is associated with the second metric index; and cause the first metric displayed on the display of the respective infusion pump to be replaced with the second metric at a second time that is not later than the first time by a time period equal to the metric display period.

The system can further include any sub-combination of one or more of the following features: where the respective infusion pump is further configured to calculate the first metric index value based on a modulo operation comprising a length of the metric display period and a count of the two or more metrics included in the indication received from the server; and where the respective infusion pump is further configured to, within the metric display period from the second time, determine a third current time associated with the internal clock data, calculate a third metric index based on the third current time, the metric display period, and the indication of the two or more metrics received from the server, determine a third metric of the plurality of metrics that is associated with the third metric index, and cause the second metric displayed on the display of the respective infusion pump to be replaced with the third metric at a third time that is not later than the second time by the time period equal to the metric display period, where a first time difference between the first time and the second time is shorter than a second time difference between the second time and the third time.

One aspect of the disclosure provides an apparatus adapted to provide synchronized screen content. The apparatus may include a display, a processor in communication with the display, and a memory storing an internal clock data according to which one or more metrics are to be displayed on the display. The memory may further store instructions that, when executed by the processor, configure the processor to: determine a first current time based on the internal clock data; identify a first one of a plurality of screen contents to be displayed on the display based on (i) the first current time, (ii) a content display period length indicative of a duration for which the first screen content is to be displayed on the display, and (iii) a screen content count indicative of a count of the plurality of screen contents to be displayed on the display; and cause the first screen content to be displayed on the display at a first time for a first duration that is less than or equal to the content display period length.

The apparatus can further include any sub-combination of one or more of the following features: where the instructions, when executed by the processor, further configure the processor to determine that a user input has not been received for a threshold amount of time, in response to the determination that the user input has not been received for the threshold amount of time, determine the first current time based on the internal clock data; where the instructions, when executed by the processor, further configure the processor to calculate a screen content index based on the first current time and the content display period length, and identify the first screen content based on the calculated screen content index; where the instructions, when executed by the processor, further configure the processor to calculate the screen content index based on a modulo operation comprising the content display period length and the screen content count; where the instructions, when executed by the processor, further configure the processor to determine a second current time before an amount of time equal to the content display period length has elapsed since the first time, identify a second one of the plurality of screen contents based on (i) the second current time, (ii) the content display period length, and (iii) the screen content count, cause the second screen content to be displayed on the display at a second time for a second duration that is equal to the content display period length; where the instructions, when executed by the processor, further configure the processor to cause the first screen content and the second screen content to be displayed on the display such that the first duration for which the first screen content is displayed on the display is shorter than the second duration for which the second screen content is displayed on the display; where the instructions, when executed by the processor, further configure the processor to determine the second current time at a time that precedes the second time by a predefined amount of time; where the instructions, when executed by the processor, further configure the processor to receive a clock synchronization data from a server in network communication with the apparatus, and update the internal clock data based on the clock synchronization data; where the instructions, when executed by the processor, further configure the processor to transmit a clock synchronization request to the server according to a predefined schedule.

One aspect of the disclosure provides a method of providing synchronized screen content. The method may include: determining a first current time associated with a medical device based on an internal clock associated with the medical device; identifying a first one of a plurality of screen contents to be displayed on a display of the medical device based on (i) the first current time, (ii) a content display period length indicative of a duration for which the identified screen content is to be displayed on the display, and (iii) a screen content count indicative of a count of the plurality of screen contents to be displayed on the display; and displaying the identified screen content on the display at a first time for a duration that is less than or equal to the content display period length.

The method can further include any sub-combination of one or more of the following features: where the method further includes determining that a user input has not been received for a threshold amount of time, and in response to determining that the user input has not been received for the threshold amount of time, determining the first current time based on the internal clock data; where the method further includes calculating a screen content index based on the first current time and the content display period length, and identifying the first screen content based on the calculated screen content index; where the method further includes calculating the screen content index based on a modulo operation comprising the content display period length and the screen content count; where the method further includes determining a second current time before an amount of time equal to the content display period length has elapsed since the first time, identifying a second one of the plurality of screen contents based on (i) the second current time, (ii) the content display period length, and (iii) the screen content count, displaying the second screen content on the display at a second time for a second duration that is equal to the content display period length; where the method further includes displaying the first screen content and the second screen content such that the first duration for which the first screen content is displayed is shorter than the second duration for which the second screen content is displayed; where the method further includes receiving a clock synchronization data from a server in network communication with the medical device, and updating the internal clock data based on the clock synchronization data; where the method further includes transmitting a clock synchronization request to the server according to a predefined schedule.

ADDITIONAL EXAMPLE EMBODIMENTS (EEs)

EE 1. A system configured to provide synchronized screen content, the system comprising: a server; and a plurality of infusion pumps configured to deliver medications to one or more patients and in network communication with the server, wherein each respective infusion pump of the plurality of infusion pumps comprises (i) a display configured to display one or more metrics of a plurality of metrics maintained by the respective infusion pump and (ii) a memory configured to store internal clock data usable to determine a current time associated with the respective networked device, wherein the respective infusion pump is configured to: receive a clock synchronization data from the server, wherein the clock synchronization data is indicative of a reference time associated with the server; update the internal clock data based on the clock synchronization data; receive metric display data from the server, wherein the metric display data comprises a metric display period and an indication of two or more metrics to be displayed on the display of the respective networked device; based on a determination that a user input has not been received for a threshold amount of time, determine a first current time associated with the internal clock data; calculate a first metric index based on the first current time, the metric display period, and the indication of the two or more metrics received from the server; determine a first metric of the plurality of metrics that is associated with the first metric index; cause the first metric to be displayed on the display of the respective infusion pump at a first time; within at least the metric display period from the first time, determine a second current time associated with the internal clock data; calculate a second metric index based on the second current time, the metric display period, and the indication of the two or more metrics received from the server; determine a second metric of the plurality of metrics that is associated with the second metric index; and cause the first metric displayed on the display of the respective infusion pump to be replaced with the second metric at a second time that is not later than the first time by a time period equal to the metric display period.

EE 2. The system of EE 1, wherein the respective infusion pump is further configured to calculate the first metric index value based on a modulo operation comprising a length of the metric display period and a count of the two or more metrics included in the indication received from the server.

EE 3. The system of EE 1, wherein the respective infusion pump is further configured to: within the metric display period from the second time, determine a third current time associated with the internal clock data; calculate a third metric index based on the third current time, the metric display period, and the indication of the two or more metrics received from the server; determine a third metric of the plurality of metrics that is associated with the third metric index; and cause the second metric displayed on the display of the respective infusion pump to be replaced with the third metric at a third time that is not later than the second time by the time period equal to the metric display period, wherein a first time difference between the first time and the second time is shorter than a second time difference between the second time and the third time.

EE 4. An apparatus configured to provide synchronized screen content of at least one medical device, the apparatus comprising: a display; a processor in communication with the display; a memory storing an internal clock data according to which one or more metrics are to be displayed on the display, the memory further storing instructions that, when executed by the processor, configure the processor to: determine a first current time based on the internal clock data; identify a first one of a plurality of medical device screen contents to be displayed on the display based on (i) the first current time, (ii) a content display period length indicative of a duration for which the first medical device screen content is to be displayed on the display, and (iii) a screen content count indicative of a count of the plurality of medical device screen contents to be displayed on the display; and cause the first medical device screen content to be displayed on the display at a first time for a first duration that is less than or equal to the content display period length.

EE 5. The apparatus of EE 4, wherein the instructions, when executed by the processor, further configure the processor to: determine that a user input has not been received for a threshold amount of time; and in response to the determination that the user input has not been received for the threshold amount of time, determine the first current time based on the internal clock data.

EE 6. The apparatus of EE 4, wherein the instructions, when executed by the processor, further configure the processor to: calculate a screen content index based on the first current time and the content display period length; and identify the first medical device screen content based on the calculated screen content index.

EE 7. The apparatus of EE 6, wherein the instructions, when executed by the processor, further configure the processor to calculate the screen content index based on a modulo operation comprising the content display period length and the screen content count.

EE 8. The apparatus of EE 4, wherein the instructions, when executed by the processor, further configure the processor to: determine a second current time before an amount of time equal to the content display period length has elapsed since the first time; identify a second one of the plurality of medical device screen contents based on (i) the second current time, (ii) the content display period length, and (iii) the screen content count; and cause the second medical device screen content to be displayed on the display at a second time for a second duration that is equal to the content display period length.

EE 9. The apparatus of EE 8, wherein the instructions, when executed by the processor, further configure the processor to cause the first medical device screen content and the second medical device screen content to be displayed on the display such that the first duration for which the first medical device screen content is displayed on the display is shorter than the second duration for which the second medical device screen content is displayed on the display.

EE 10. The apparatus of EE 8, wherein the instructions, when executed by the processor, further configure the processor to determine the second current time at a time that precedes the second time by a predefined amount of time.

EE 11. The apparatus of EE 4, wherein the instructions, when executed by the processor, further configure the processor to: receive a clock synchronization data from a server in network communication with the apparatus; and update the internal clock data based on the clock synchronization data.

EE 12. The apparatus of EE 11, wherein the instructions, when executed by the processor, further configure the processor to transmit a clock synchronization request to the server according to a predefined schedule.

EE 13. A method of providing synchronized screen content of at least one medical device, the method comprising: determining a first current time associated with a medical device based on an internal clock associated with the medical device; identifying a first one of a plurality of medical device screen contents to be displayed on a display of the medical device based on (i) the first current time, (ii) a content display period length indicative of a duration for which the identified medical device screen content is to be displayed on the display, and (iii) a screen content count indicative of a count of the plurality of medical device screen contents to be displayed on the display; and displaying the identified medical device screen content on the display at a first time for a duration that is less than or equal to the content display period length.

EE 14. The method of EE 13, further comprising: determining that a user input has not been received for a threshold amount of time; and in response to determining that the user input has not been received for the threshold amount of time, determining the first current time based on the internal clock data.

EE 15. The method of EE 13, further comprising: calculating a screen content index based on the first current time and the content display period length; and identifying the first medical device screen content based on the calculated screen content index.

EE 16. The method of EE 15, further comprising calculating the screen content index based on a modulo operation comprising the content display period length and the screen content count.

EE 17. The method of EE 13, further comprising: determining a second current time before an amount of time equal to the content display period length has elapsed since the first time; identifying a second one of the plurality of medical device screen contents based on (i) the second current time, (ii) the content display period length, and (iii) the screen content count; and displaying the second medical device screen content on the display at a second time for a second duration that is equal to the content display period length.

EE 18. The method of EE 17, further comprising displaying the first medical device screen content and the second medical device screen content such that the first duration for which the first medical device screen content is displayed is shorter than the second duration for which the second medical device screen content is displayed.

EE 19. The method of EE 13, further comprising: receiving a clock synchronization data from a server in network communication with the medical device; and updating the internal clock data based on the clock synchronization data.

EE 20. The method of EE 19, further comprising transmitting a clock synchronization request to the server according to a predefined schedule.

OTHER CONSIDERATIONS

It is to be understood that not necessarily all objects or advantages may be achieved in accordance with any particular embodiment described herein. Thus, for example, those skilled in the art will recognize that certain embodiments may be configured to operate in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other objects or advantages as may be taught or suggested herein.

Many other variations than those described herein will be apparent from this disclosure. For example, depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. In addition, different tasks or processes can be performed by different machines and/or computing systems that can function together.

The various illustrative logical blocks, modules, and algorithm elements described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and elements have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.

The various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor can include electrical circuitry configured to process computer-executable instructions. In another embodiment, a processor includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor may also include primarily analog components. For example, some or all of the signal processing algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.

The elements of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module stored in one or more memory devices and executed by one or more processors, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art. An example storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The storage medium can be volatile or nonvolatile. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.

Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Further, the term “each,” as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term “each” is applied.

Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.

Unless otherwise explicitly stated, articles such as “a”, “an”, or “the” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B, and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.

While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, certain embodiments described herein can be implemented within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. All such modifications and variations are intended to be included herein within the scope of this disclosure. Further, additional embodiments created by combining any two or more features or techniques of one or more embodiments described herein are also intended to be included herein within the scope of this disclosure.

Claims

1. An apparatus comprising: one or more processors; andone or more memories storing instructions that, when executed by the one or more processors, configure the one or more processors to: determine a current time;determine a display period length associated with at least one displayable metric;determine, based at least in part on the current time and the display period length, a first metric to be displayed;cause the first metric to be displayed on a display; andbefore the first metric is displayed for the display period length, cause the display to transition from displaying the first metric to displaying a second metric that is different from the first metric.
2. The apparatus of claim 1, wherein the first metric is one of dose, rate, volume infused, volume to be infused, or time remaining, and the second metric is another one of dose, rate, volume infused, volume to be infused, or time remaining.
3. The apparatus of claim 1, wherein the instructions, when executed by the one or more processors, further configure the one or more processors to determine the current time in response to a determination that the apparatus has not received a user input for at least a threshold amount of time.
4. The apparatus of claim 1, wherein the instructions, when executed by the one or more processors, further configure the one or more processors to cause an internal clock of the apparatus to be synchronized based at least in part on a signal received from a server in networked communication with the apparatus.
5. The apparatus of claim 1, wherein the instructions, when executed by the one or more processors, further configure the one or more processors to cause an internal clock of the apparatus to be synchronized based at least in part on a signal received from an atomic clock.
6. The apparatus of claim 1, wherein the instructions, when executed by the one or more processors, further configure the one or more processors to, after the second metric is displayed for at least a duration indicated by the display period length, cause the display to transition from displaying the second metric to displaying a third metric that is different from the first metric and the second metric.
7. The apparatus of claim 1, wherein the instructions, when executed by the one or more processors, further configure the one or more processors to cause the first metric to be displayed (i) in a specific size, (ii) in a specific color, or (iii) along with a specific indicator, wherein the specific size, the specific color, or the specific indicator provides additional information other than that indicated by a displayed value of the first metric.
8. A method comprising: determining a current time associated with a networked device;determining a display period length associated with at least one displayable metric;determining, based at least in part on the current time and the display period length, a first metric to be displayed;displaying the first metric on a display; andbefore the first metric is displayed for the display period length, causing the display to transition from displaying the first metric to displaying a second metric that is different from the first metric.
9. The method of claim 8, wherein the first metric is one of dose, rate, volume infused, volume to be infused, or time remaining, and the second metric is another one of dose, rate, volume infused, volume to be infused, or time remaining.
10. The method of claim 8, further comprising determining the current time in response to determining that the networked device has not received a user input for at least a threshold amount of time.
11. The method of claim 8, further comprising synchronizing a clock based at least in part on a signal received from a server in networked communication with the networked device.
12. The method of claim 8, wherein the networked device is in networked communication with a server, the method further comprising synchronizing a clock based at least in part on a signal received from other than the server.
13. The method of claim 8, further comprising, after the second metric is displayed for at least a duration indicated by the display period length, transitioning from displaying the second metric on the display to displaying a third metric on the display, wherein the third metric is different from the first metric and the second metric.
14. The method of claim 8, further comprising displaying the first metric (i) in a specific size, (ii) in a specific color, or (iii) along with a specific indicator, wherein the specific size, the specific color, or the specific indicator provides additional information other than that indicated by a displayed value of the first metric.
15. A system comprising: a server; anda plurality of networked devices in networked communication with the server, wherein a first networked device of the plurality of networked devices is configured to at least: determine a current time;determine a display period length associated with at least one displayable metric;determine, based at least in part on the current time and the display period length, a first metric to be displayed;cause the first metric to be displayed on a display; andbefore the first metric is displayed for the display period length, cause the display to transition from displaying the first metric to displaying a second metric that is different from the first metric.
16. The system of claim 15, wherein the first networked device is further configured to determine the current time in response to a determination that the first networked device has not received a user input for at least a threshold amount of time.
17. The system of claim 15, wherein the server is configured to transmit a set of infusion pump settings or delivery parameters to the first networked device, the first networked device further configured to cause a clock to be synchronized based at least in part on a signal received from the server.
18. The system of claim 15, wherein the server is configured to transmit a set of infusion pump settings or delivery parameters to the first networked device, the first networked device further configured to cause a clock to be synchronized based at least in part on a signal received from other than the server.
19. The system of claim 15, wherein the first networked device is further configured to, after the second metric is displayed for at least a duration indicated by the display period length, cause the display to transition from displaying the second metric to displaying a third metric that is different from the first metric and the second metric.
20. The system of claim 15, wherein the first networked device is further configured to cause the first metric to be displayed (i) in a specific size, (ii) in a specific color, or (iii) along with a specific indicator, wherein the specific size, the specific color, or the specific indicator provides additional information other than that indicated by a displayed value of the first metric.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

This application is a continuation of U.S. application Ser. No. 16/848,649, filed Apr. 14, 2020, which is a continuation of U.S. application Ser. No. 16/058,799, filed Aug. 8, 2018, which is a continuation of U.S. application Ser. No. 15/861,204, filed Jan. 3, 2018, which claims priority to U.S. Provisional Application No. 62/610,742, filed on Dec. 27, 2017. Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated herein by reference in their entirety under 37 CFR 1.57.

US Referenced Citations (1636)

Number	Name	Date	Kind
3401337	Beusman et al.	Sep 1968	A
3484681	Grady, Jr. et al.	Dec 1969	A
3699320	Zimmerman et al.	Oct 1972	A
3727074	Keller et al.	Apr 1973	A
3731679	Wilhelmson et al.	May 1973	A
3768084	Haynes	Oct 1973	A
3770354	Tsuruta et al.	Nov 1973	A
3778702	Finger	Dec 1973	A
3806821	Niemeyer et al.	Apr 1974	A
3838565	Carlyle	Oct 1974	A
3854038	McKinley	Dec 1974	A
3886459	Hufford et al.	May 1975	A
3890554	Yoshitake et al.	Jun 1975	A
3894431	Muston et al.	Jul 1975	A
3898637	Wolstenholme	Aug 1975	A
3901231	Olson	Aug 1975	A
3909693	Yoshitake et al.	Sep 1975	A
3910701	Henderson	Oct 1975	A
3911343	Oster	Oct 1975	A
3919608	Usami et al.	Nov 1975	A
3921622	Cole	Nov 1975	A
3930404	Ryden, Jr.	Jan 1976	A
3933431	Trujillo et al.	Jan 1976	A
3935876	Massie et al.	Feb 1976	A
3944963	Hively	Mar 1976	A
3966358	Heimes et al.	Jun 1976	A
3971980	Jungfer et al.	Jul 1976	A
3974681	Namery	Aug 1976	A
3974683	Martin	Aug 1976	A
3985467	Lefferson	Oct 1976	A
3990444	Vial	Nov 1976	A
3997888	Kremer	Dec 1976	A
4005724	Courtot	Feb 1977	A
4014206	Taylor	Mar 1977	A
4038982	Burke	Aug 1977	A
4039269	Pickering	Aug 1977	A
4048474	Olesen	Sep 1977	A
4049954	Da Costa Vieira et al.	Sep 1977	A
4055175	Clemens et al.	Oct 1977	A
4057228	Völker et al.	Nov 1977	A
4068521	Cosentino et al.	Jan 1978	A
4078562	Friedman	Mar 1978	A
4089227	Falgari et al.	May 1978	A
4094318	Burke	Jun 1978	A
4105028	Sadlier et al.	Aug 1978	A
4114144	Hyman	Sep 1978	A
4151845	Clemens	May 1979	A
4155362	Jess	May 1979	A
4173224	Marx	Nov 1979	A
4181610	Shintani et al.	Jan 1980	A
4183244	Kohno et al.	Jan 1980	A
4195515	Smoll	Apr 1980	A
4210138	Jess et al.	Jul 1980	A
4213454	Shim	Jul 1980	A
4217993	Jess et al.	Aug 1980	A
4240294	Grande	Dec 1980	A
4240438	Updike et al.	Dec 1980	A
4244365	McGill	Jan 1981	A
4256437	Brown	Mar 1981	A
4261356	Turner et al.	Apr 1981	A
4264861	Radu et al.	Apr 1981	A
4265240	Jenkins	May 1981	A
4270532	Franetzki et al.	Jun 1981	A
4277226	Archibald et al.	Jul 1981	A
4278085	Shim	Jul 1981	A
4280495	Lampert	Jul 1981	A
4282872	Franetzki et al.	Aug 1981	A
4286202	Clancy et al.	Aug 1981	A
4290346	Bujan	Sep 1981	A
4291692	Bowman et al.	Sep 1981	A
4292405	Mascoli	Sep 1981	A
4298357	Permic	Nov 1981	A
4308866	Jeliffe	Jan 1982	A
4312341	Zissimopoulos	Jan 1982	A
4319568	Tregoning	Mar 1982	A
4322201	Archibald	Mar 1982	A
4323849	Smith	Apr 1982	A
4324662	Schnell	Apr 1982	A
4328800	Marx	May 1982	A
4328801	Marx	May 1982	A
4333045	Oltendorf	Jun 1982	A
4343316	Jespersen	Aug 1982	A
4344429	Gupton et al.	Aug 1982	A
4346707	Whitney et al.	Aug 1982	A
4360019	Portner et al.	Nov 1982	A
4366384	Jensen	Dec 1982	A
4367736	Gupton	Jan 1983	A
4370983	Lichtenstein et al.	Feb 1983	A
4373527	Fischell	Feb 1983	A
4379452	DeVries	Apr 1983	A
4381005	Bujan	Apr 1983	A
4384578	Winkler	May 1983	A
4385247	Satomi	May 1983	A
4391598	Thompson	Jul 1983	A
4392849	Petre et al.	Jul 1983	A
4394862	Shim	Jul 1983	A
4395259	Prestele et al.	Jul 1983	A
4397194	Soltz	Aug 1983	A
4399362	Cormier et al.	Aug 1983	A
4407659	Adam	Oct 1983	A
4411651	Schulman	Oct 1983	A
4418565	St. John	Dec 1983	A
4432699	Beckman et al.	Feb 1984	A
4432761	Dawe	Feb 1984	A
4432762	Dawe	Feb 1984	A
4443218	Decant, Jr. et al.	Apr 1984	A
4444546	Pazemenas	Apr 1984	A
4447191	Bilstad et al.	May 1984	A
4447224	Decant, Jr. et al.	May 1984	A
4453931	Pastrone	Jun 1984	A
4457751	Rodler	Jul 1984	A
4463301	Moriguchi et al.	Jul 1984	A
4464170	Clemens	Aug 1984	A
4467654	Murakami et al.	Aug 1984	A
4468222	Lundquist	Aug 1984	A
4468601	Chamran et al.	Aug 1984	A
4469481	Kobayashi	Sep 1984	A
4475666	Bilbrey et al.	Oct 1984	A
4475901	Kraegen et al.	Oct 1984	A
4477756	Moriguchi	Oct 1984	A
4479760	Bilstad et al.	Oct 1984	A
4480218	Hair	Oct 1984	A
4480483	McShane	Nov 1984	A
4483202	Ogua et al.	Nov 1984	A
4487601	Lindemann	Dec 1984	A
4492909	Hartwig	Jan 1985	A
4496346	Mosteller	Jan 1985	A
4498843	Schneider et al.	Feb 1985	A
4501531	Bilstad et al.	Feb 1985	A
4504263	Steuer	Mar 1985	A
4507112	Hillel	Mar 1985	A
4510266	Eertink	Apr 1985	A
4515584	Abe et al.	May 1985	A
4519792	Dawe	May 1985	A
4521212	Ruschke	Jun 1985	A
4525163	Slavik et al.	Jun 1985	A
4526568	Clemens et al.	Jul 1985	A
4526574	Pekkarinen	Jul 1985	A
4529401	Leslie et al.	Jul 1985	A
4533350	Danby et al.	Aug 1985	A
4543955	Schroeppel	Oct 1985	A
4551134	Slavik et al.	Nov 1985	A
4553958	LeCocq	Nov 1985	A
4559036	Wunsch	Dec 1985	A
4559037	Franetzki et al.	Dec 1985	A
4559044	Robinson	Dec 1985	A
4559454	Kramer	Dec 1985	A
4565500	Jeensalute et al.	Jan 1986	A
4583981	Urquhart et al.	Apr 1986	A
4587473	Turvey	May 1986	A
4607520	Dam	Aug 1986	A
4617014	Cannon et al.	Oct 1986	A
4624661	Arimond	Nov 1986	A
4627835	Fenton, Jr.	Dec 1986	A
4633878	Bombardieri	Jan 1987	A
4634426	Kamen	Jan 1987	A
4634427	Hannula et al.	Jan 1987	A
4636144	Abe et al.	Jan 1987	A
4637813	DeVries	Jan 1987	A
4645489	Krumme	Feb 1987	A
4648869	Bobo, Jr.	Mar 1987	A
4652260	Fenton, Jr. et al.	Mar 1987	A
4658244	Meijer	Apr 1987	A
4668216	Martin	May 1987	A
4668945	Aldrovandi et al.	May 1987	A
4673334	Allington et al.	Jun 1987	A
4673389	Archibald et al.	Jun 1987	A
4676776	Howson et al.	Jun 1987	A
4677359	Enami et al.	Jun 1987	A
4678979	Hori	Jul 1987	A
4678998	Muramatsu	Jul 1987	A
4679562	Luksha	Jul 1987	A
4683428	Gete	Jul 1987	A
4685903	Cable et al.	Aug 1987	A
4690673	Blomquist	Sep 1987	A
4691153	Nishimura	Sep 1987	A
4692145	Weyant	Sep 1987	A
4696671	Epstein et al.	Sep 1987	A
4697129	Enami et al.	Sep 1987	A
4702675	Aldrovandi et al.	Oct 1987	A
4705506	Archibald et al.	Nov 1987	A
4710106	Iwata et al.	Dec 1987	A
4714462	DiDomenico	Dec 1987	A
4714463	Archibald et al.	Dec 1987	A
4718576	Tamura et al.	Jan 1988	A
4720636	Benner	Jan 1988	A
4722224	Scheller et al.	Feb 1988	A
4722734	Kolin	Feb 1988	A
4731051	Fischell	Mar 1988	A
4731057	Tanaka et al.	Mar 1988	A
4737711	O'Hare	Apr 1988	A
4739346	Buckley	Apr 1988	A
4741732	Crankshaw et al.	May 1988	A
4741736	Brown	May 1988	A
4748857	Nakagawa	Jun 1988	A
4751445	Sakai	Jun 1988	A
4756706	Kerns et al.	Jul 1988	A
4758228	Williams	Jul 1988	A
4763525	Cobb	Aug 1988	A
4764166	Spani et al.	Aug 1988	A
4764697	Christiaens	Aug 1988	A
4769001	Prince	Sep 1988	A
4776842	Franetzki et al.	Oct 1988	A
4781687	Wall	Nov 1988	A
4784576	Bloom et al.	Nov 1988	A
4785184	Bien et al.	Nov 1988	A
4785799	Schoon et al.	Nov 1988	A
4785969	McLaughlin	Nov 1988	A
4786800	Kamen	Nov 1988	A
4789014	DiGianfilippo	Dec 1988	A
4797655	Orndal et al.	Jan 1989	A
4803389	Ogawa et al.	Feb 1989	A
4803625	Fu et al.	Feb 1989	A
4818186	Pastrone et al.	Apr 1989	A
4820281	Lawler	Apr 1989	A
4821558	Pastrone et al.	Apr 1989	A
4828545	Epstein et al.	May 1989	A
4828693	Lindsay	May 1989	A
4829448	Balding et al.	May 1989	A
4838856	Mulreany et al.	Jun 1989	A
4838857	Strowe et al.	Jun 1989	A
4840542	Abbott	Jun 1989	A
4842584	Pastrone et al.	Jun 1989	A
4845487	Frantz et al.	Jul 1989	A
4846792	Bobo et al.	Jul 1989	A
4850805	Madsen et al.	Jul 1989	A
4851755	Fincher	Jul 1989	A
4854324	Hirschman et al.	Aug 1989	A
4856339	Williams	Aug 1989	A
4857048	Simons et al.	Aug 1989	A
4857050	Lentz et al.	Aug 1989	A
4858154	Anderson et al.	Aug 1989	A
4863425	Slate et al.	Sep 1989	A
4865584	Epstein et al.	Sep 1989	A
4869722	Heyman	Sep 1989	A
4874359	White et al.	Oct 1989	A
4881413	Georgi et al.	Nov 1989	A
4882575	Kawahara	Nov 1989	A
4884013	Jackson et al.	Nov 1989	A
4884065	Crouse et al.	Nov 1989	A
4886422	Takeuchi et al.	Dec 1989	A
4898576	Philip	Feb 1990	A
4898578	Rubalcaba, Jr.	Feb 1990	A
4906103	Kao	Mar 1990	A
4908017	Howson et al.	Mar 1990	A
4908019	Urquhart et al.	Mar 1990	A
4910475	Lin	Mar 1990	A
4919595	Likuski et al.	Apr 1990	A
4919596	Slate et al.	Apr 1990	A
4925444	Orkin et al.	May 1990	A
4927411	Pastrone et al.	May 1990	A
4930358	Motegi et al.	Jun 1990	A
4936820	Dennehey	Jun 1990	A
4936828	Chiang	Jun 1990	A
4938079	Goldberg	Jul 1990	A
4943279	Samiotes et al.	Jul 1990	A
4946439	Eggers	Aug 1990	A
4947856	Beard	Aug 1990	A
4950235	Slate et al.	Aug 1990	A
4950244	Fellingham	Aug 1990	A
4959050	Bobo, Jr.	Sep 1990	A
4966579	Polaschegg	Oct 1990	A
4968941	Rogers	Nov 1990	A
4972842	Korten et al.	Nov 1990	A
4976687	Martin	Dec 1990	A
4978335	Arthur, III	Dec 1990	A
4979940	Lapp et al.	Dec 1990	A
4981467	Bobo et al.	Jan 1991	A
5000663	Gorton	Mar 1991	A
5000739	Kulisz et al.	Mar 1991	A
5006050	Cooke et al.	Apr 1991	A
5010473	Jacobs	Apr 1991	A
5014714	Millay et al.	May 1991	A
5014798	Glynn	May 1991	A
5018945	D'Silva	May 1991	A
5026348	Venegas	Jun 1991	A
5028857	Taghezout	Jul 1991	A
5032112	Fairchild et al.	Jul 1991	A
5034004	Crankshaw	Jul 1991	A
5035143	Latimer et al.	Jul 1991	A
5040699	Gangemi	Aug 1991	A
5041086	Koenig et al.	Aug 1991	A
5043706	Oliver	Aug 1991	A
5045069	Imparato	Sep 1991	A
5049047	Polaschegg et al.	Sep 1991	A
5052230	Lang	Oct 1991	A
5053747	Slate et al.	Oct 1991	A
5055761	Mills	Oct 1991	A
5056992	Simons	Oct 1991	A
5058161	Weiss	Oct 1991	A
5059171	Bridge	Oct 1991	A
5063603	Burt	Nov 1991	A
5064412	Henke et al.	Nov 1991	A
5078683	Sancoff et al.	Jan 1992	A
5084663	Olsson	Jan 1992	A
5084828	Kaufman et al.	Jan 1992	A
5088981	Howson et al.	Feb 1992	A
5096385	Georgi et al.	Mar 1992	A
5097505	Weiss	Mar 1992	A
5100380	Epstein et al.	Mar 1992	A
5102392	Sakai et al.	Apr 1992	A
5103211	Daoud et al.	Apr 1992	A
5104374	Bishko et al.	Apr 1992	A
5108367	Epstein et al.	Apr 1992	A
5109850	Blanco et al.	May 1992	A
5116203	Nartwick et al.	May 1992	A
5116312	Blakenship et al.	May 1992	A
5116316	Sertic	May 1992	A
5123275	Daoud et al.	Jun 1992	A
5124627	Okada	Jun 1992	A
5125499	Saathoff et al.	Jun 1992	A
5131816	Brown	Jul 1992	A
5132603	Yoshimoto	Jul 1992	A
5153827	Coutre et al.	Oct 1992	A
5158441	Aid	Oct 1992	A
5161222	Montejo et al.	Nov 1992	A
5174472	Raque et al.	Dec 1992	A
5176631	Koenig	Jan 1993	A
5176646	Kuroda	Jan 1993	A
5179340	Rogers	Jan 1993	A
5180287	Natwick et al.	Jan 1993	A
5181910	Scanlon	Jan 1993	A
5186057	Everhart	Feb 1993	A
5188603	Vaillancourt	Feb 1993	A
5190522	Wocicki et al.	Mar 1993	A
5191795	Fellingham et al.	Mar 1993	A
5192340	Grant et al.	Mar 1993	A
5194796	Domeki et al.	Mar 1993	A
5198776	Carr	Mar 1993	A
5200090	Ford	Apr 1993	A
5205819	Ross et al.	Apr 1993	A
5206522	Danby et al.	Apr 1993	A
5207642	Orkin et al.	May 1993	A
5211626	Frank et al.	May 1993	A
5213573	Sorich et al.	May 1993	A
5215450	Tamari	Jun 1993	A
5216597	Beckers	Jun 1993	A
5219099	Spence et al.	Jun 1993	A
5219327	Okada	Jun 1993	A
5221268	Barton et al.	Jun 1993	A
5229713	Bullock et al.	Jul 1993	A
5232476	Grant	Aug 1993	A
5233571	Wirtschafter	Aug 1993	A
5237309	Frantz et al.	Aug 1993	A
5242406	Gross et al.	Sep 1993	A
5242408	Jhuboo et al.	Sep 1993	A
5243982	Möstl et al.	Sep 1993	A
5244463	Cordner, Jr. et al.	Sep 1993	A
5244568	Lindsay et al.	Sep 1993	A
5254096	Rondelet et al.	Oct 1993	A
5256155	Yerlikaya et al.	Oct 1993	A
5256156	Kern et al.	Oct 1993	A
5256157	Samiotes et al.	Oct 1993	A
5260665	Goldberg	Nov 1993	A
5257206	Hanson	Dec 1993	A
5267980	Dirr et al.	Dec 1993	A
5274316	Evans et al.	Dec 1993	A
5276610	Maeda et al.	Jan 1994	A
5280728	Sato et al.	Jan 1994	A
5283510	Tamaki et al.	Feb 1994	A
5287851	Beran et al.	Feb 1994	A
5292306	Wynkoop et al.	Mar 1994	A
5295967	Rondelet et al.	Mar 1994	A
5298021	Sherer	Mar 1994	A
5303585	Lichte	Apr 1994	A
5304126	Epstein et al.	Apr 1994	A
5304216	Wallace	Apr 1994	A
5308333	Skakoon	May 1994	A
5317506	Coutre et al.	May 1994	A
5319363	Welch et al.	Jun 1994	A
5319979	Abrahamson	Jun 1994	A
5321392	Skakoon et al.	Jun 1994	A
5325170	Bornhop	Jun 1994	A
5325728	Zimmerman et al.	Jul 1994	A
5328460	Lord et al.	Jul 1994	A
5330634	Wong et al.	Jul 1994	A
5333497	Braend et al.	Aug 1994	A
5336051	Tamari	Aug 1994	A
5338157	Blomquist	Aug 1994	A
5342298	Michaels	Aug 1994	A
5343734	Maeda et al.	Sep 1994	A
5343885	Grant	Sep 1994	A
5346466	Yerlikaya et al.	Sep 1994	A
5356378	Doan et al.	Oct 1994	A
5359271	Husher	Oct 1994	A
D352778	Irvin et al.	Nov 1994	S
5364346	Schrezenmeir	Nov 1994	A
5366346	Danby	Nov 1994	A
5368562	Blomquist et al.	Nov 1994	A
5374865	Yoshimura et al.	Dec 1994	A
5376070	Purvis et al.	Dec 1994	A
5378231	Johnson et al.	Jan 1995	A
5382232	Hague et al.	Jan 1995	A
5383369	Khuri-Yakub et al.	Jan 1995	A
5389071	Kawahara et al.	Feb 1995	A
5389078	Zalesky et al.	Feb 1995	A
5392638	Kawahara	Feb 1995	A
5394732	Johnson et al.	Mar 1995	A
5395320	Padda et al.	Mar 1995	A
5399171	Bowman et al.	Mar 1995	A
5406954	Tomita	Apr 1995	A
5408326	Priestley	Apr 1995	A
5415528	Ogden et al.	May 1995	A
5417119	Smoll	May 1995	A
5417222	Dempsey et al.	May 1995	A
5417395	Fowler et al.	May 1995	A
5418443	Kikuchi	May 1995	A
5421208	Packard et al.	Jun 1995	A
5423748	Uhala	Jun 1995	A
5423749	Merte et al.	Jun 1995	A
5423759	Campbell	Jun 1995	A
5428284	Kaneda et al.	Jun 1995	A
5429485	Dodge	Jul 1995	A
5429601	Conley	Jul 1995	A
5429602	Hauser	Jul 1995	A
5431627	Pastrone et al.	Jul 1995	A
5434508	Ishida	Jul 1995	A
5437624	Langley et al.	Aug 1995	A
5444316	Ohya et al.	Aug 1995	A
5444378	Rogers	Aug 1995	A
5445621	Poli et al.	Aug 1995	A
5450758	Smoll	Sep 1995	A
5451881	Finger	Sep 1995	A
5455423	Mount et al.	Oct 1995	A
5455851	Chaco et al.	Oct 1995	A
5463906	Spani et al.	Nov 1995	A
5464392	Epstein et al.	Nov 1995	A
5465082	Chaco	Nov 1995	A
5469851	Lipschutz	Nov 1995	A
5473948	Moss et al.	Dec 1995	A
5480294	Di Perna et al.	Jan 1996	A
5482438	Anderson et al.	Jan 1996	A
5485408	Blomquist	Jan 1996	A
5486286	Peterson et al.	Jan 1996	A
5489265	Montalvo et al.	Feb 1996	A
5495566	Kwatinetz	Feb 1996	A
5496273	Pastrone et al.	Mar 1996	A
5505696	Miki	Apr 1996	A
5505828	Wong et al.	Apr 1996	A
5507288	Bocker et al.	Apr 1996	A
5507412	Ebert et al.	Apr 1996	A
5520637	Pager et al.	May 1996	A
5522798	Johnson et al.	Jun 1996	A
5522799	Furukawa	Jun 1996	A
5527630	Nagata	Jun 1996	A
5533389	Kamen et al.	Jul 1996	A
5537853	Finburgh et al.	Jul 1996	A
5542040	Chang et al.	Jul 1996	A
5545140	Conero et al.	Aug 1996	A
5547470	Johnson et al.	Aug 1996	A
5551850	Williamson et al.	Sep 1996	A
5554013	Owens et al.	Sep 1996	A
5554115	Thomas et al.	Sep 1996	A
5558638	Evers et al.	Sep 1996	A
5562615	Nassif	Oct 1996	A
5563486	Yamamoto et al.	Oct 1996	A
5572105	Nojima et al.	Nov 1996	A
5573502	LeCocq et al.	Nov 1996	A
5583280	Mo et al.	Dec 1996	A
5584667	Davis	Dec 1996	A
5584806	Amano	Dec 1996	A
5586868	Lawless et al.	Dec 1996	A
5590653	Aida et al.	Jan 1997	A
5594786	Chaco et al.	Jan 1997	A
5600073	Hill	Feb 1997	A
5601420	Warner et al.	Feb 1997	A
5609575	Larson et al.	Mar 1997	A
5609576	Voss	Mar 1997	A
5611784	Barresi et al.	Mar 1997	A
5616124	Hague et al.	Apr 1997	A
5620312	Hyman et al.	Apr 1997	A
5620608	Rosa et al.	Apr 1997	A
5626140	Feldman et al.	May 1997	A
5626151	Linden	May 1997	A
5626563	Dodge et al.	May 1997	A
5627443	Kimura et al.	May 1997	A
5628309	Brown	May 1997	A
5628731	Dodge et al.	May 1997	A
5630710	Tune et al.	May 1997	A
5634896	Bryant et al.	Jun 1997	A
5637095	Nason et al.	Jun 1997	A
5640075	Brasseur et al.	Jun 1997	A
5640150	Atwater	Jun 1997	A
5643212	Coutre et al.	Jul 1997	A
5648710	Ikeda	Jul 1997	A
5649536	Ogura et al.	Jul 1997	A
5651775	Walker et al.	Jul 1997	A
5657000	Ellingboe	Aug 1997	A
5658133	Anderson et al.	Aug 1997	A
5658250	Blomquist et al.	Aug 1997	A
5659234	Cresens	Aug 1997	A
5661245	Svoboda et al.	Aug 1997	A
5662612	Niehoff	Sep 1997	A
5665065	Colman et al.	Sep 1997	A
5669877	Blomquist	Sep 1997	A
5672154	Sillén et al.	Sep 1997	A
5672832	Cucci et al.	Sep 1997	A
5681285	Ford et al.	Oct 1997	A
5681286	Niehoff	Oct 1997	A
5685844	Marttila	Nov 1997	A
5685866	Lopez	Nov 1997	A
5687717	Halpern et al.	Nov 1997	A
5689229	Chaco et al.	Nov 1997	A
5691613	Gutwillinger	Nov 1997	A
5695464	Viallet	Dec 1997	A
5695473	Olsen	Dec 1997	A
5697899	Hillman et al.	Dec 1997	A
5697916	Schraga	Dec 1997	A
5712795	Layman et al.	Jan 1998	A
5713856	Eggers et al.	Feb 1998	A
5714691	Hill	Feb 1998	A
5718562	Lawless et al.	Feb 1998	A
5718569	Holst	Feb 1998	A
5720721	Dumas et al.	Feb 1998	A
5722417	Rudolph	Mar 1998	A
5728074	Castellano et al.	Mar 1998	A
5728948	Bignell et al.	Mar 1998	A
5733257	Stemby	Mar 1998	A
5733259	Valcke et al.	Mar 1998	A
5734464	Gibbs	Mar 1998	A
5738659	Neer et al.	Apr 1998	A
5743856	Oka et al.	Apr 1998	A
5744027	Connell et al.	Apr 1998	A
5744929	Miyazaki	Apr 1998	A
5745378	Barker et al.	Apr 1998	A
5752813	Tyner et al.	May 1998	A
5752918	Fowler et al.	May 1998	A
5752919	Schrimpf	May 1998	A
5755691	Hilborne	May 1998	A
5758643	Wong et al.	Jun 1998	A
5761072	Bardsley, Jr. et al.	Jun 1998	A
5764034	Bowman et al.	Jun 1998	A
5766155	Hyman et al.	Jun 1998	A
5772635	Dastur et al.	Jun 1998	A
5778256	Darbee	Jul 1998	A
5781442	Engleson et al.	Jul 1998	A
5782805	Meinzer et al.	Jul 1998	A
5788669	Peterson	Aug 1998	A
5788674	McWilliams	Aug 1998	A
5789923	Shimoyama et al.	Aug 1998	A
5792069	Greenwald et al.	Aug 1998	A
5793211	Shimoyama et al.	Aug 1998	A
5795327	Wilson et al.	Aug 1998	A
5798934	Saigo et al.	Aug 1998	A
5800387	Duffy et al.	Sep 1998	A
5803712	Davis et al.	Sep 1998	A
5803917	Butterfield	Sep 1998	A
5805455	Lipps	Sep 1998	A
5807322	Lindsey et al.	Sep 1998	A
5810770	Chin et al.	Sep 1998	A
5813972	Nazarian et al.	Sep 1998	A
5814004	Tamari	Sep 1998	A
5814015	Gargano et al.	Sep 1998	A
5816779	Lawless et al.	Oct 1998	A
5822715	Worthington et al.	Oct 1998	A
5827179	Lichter et al.	Oct 1998	A
5827223	Butterfield	Oct 1998	A
5832448	Brown	Nov 1998	A
5836910	Duffy et al.	Nov 1998	A
5841261	Nojima et al.	Nov 1998	A
5841284	Takahashi	Nov 1998	A
5843035	Bowman	Dec 1998	A
5848971	Fowler et al.	Dec 1998	A
5850344	Conkright	Dec 1998	A
5857843	Leason et al.	Jan 1999	A
5864330	Haynes	Jan 1999	A
5865805	Ziemba	Feb 1999	A
5867821	Ballantyne et al.	Feb 1999	A
5871465	Vasko	Feb 1999	A
5872453	Shimoyama et al.	Feb 1999	A
5875195	Dixon	Feb 1999	A
5882300	Malinouskas et al.	Mar 1999	A
5882339	Beiser et al.	Mar 1999	A
5885245	Lynch et al.	Mar 1999	A
5889379	Yanagi et al.	Mar 1999	A
5891051	Han et al.	Apr 1999	A
5894209	Takagi et al.	Apr 1999	A
5897493	Brown	Apr 1999	A
5897498	Canfield, II et al.	Apr 1999	A
5898292	Takemoto et al.	Apr 1999	A
5899665	Makino et al.	May 1999	A
5901150	Jhuboo et al.	May 1999	A
5904666	DeDecker et al.	May 1999	A
5904668	Hyman et al.	May 1999	A
5905207	Schalk	May 1999	A
5906598	Giesier	May 1999	A
5910252	Truitt et al.	Jun 1999	A
5915240	Karpf	Jun 1999	A
5920263	Huttenhoff et al.	Jul 1999	A
5923159	Ezell	Jul 1999	A
5924074	Evans	Jul 1999	A
5927349	Martucci	Jul 1999	A
5932119	Kaplan et al.	Aug 1999	A
5932987	McLoughlin	Aug 1999	A
5935099	Peterson et al.	Aug 1999	A
5935106	Olsen	Aug 1999	A
5938634	Packard	Aug 1999	A
5938636	Kramer et al.	Aug 1999	A
5941846	Duffy et al.	Aug 1999	A
5944660	Kimball et al.	Aug 1999	A
5947911	Wong et al.	Sep 1999	A
5954527	Jhuboo et al.	Sep 1999	A
5954696	Ryan et al.	Sep 1999	A
5956023	Lyle et al.	Sep 1999	A
5956501	Brown	Sep 1999	A
5957885	Bollish et al.	Sep 1999	A
5957890	Mann et al.	Sep 1999	A
5971594	Sahai et al.	Oct 1999	A
5973497	Bergk et al.	Oct 1999	A
5975081	Hood et al.	Nov 1999	A
5989222	Cole et al.	Nov 1999	A
5990838	Burns et al.	Nov 1999	A
5991525	Shah et al.	Nov 1999	A
5993393	Ryan et al.	Nov 1999	A
5994876	Canny et al.	Nov 1999	A
5997476	Brown	Dec 1999	A
6000828	Leet	Dec 1999	A
6003006	Colella et al.	Dec 1999	A
6003388	Oeftering	Dec 1999	A
6012034	Hamparian et al.	Jan 2000	A
6017318	Gauthier et al.	Jan 2000	A
6017493	Cambron	Jan 2000	A
6021392	Lester et al.	Feb 2000	A
6023977	Langdon et al.	Feb 2000	A
6024539	Blomquist	Feb 2000	A
6027441	Cantu	Feb 2000	A
6028412	Shine et al.	Feb 2000	A
6032676	Moore	Mar 2000	A
6033561	Schoendorfer	Mar 2000	A
6036017	Bayliss, IV	Mar 2000	A
6068612	Bowman	May 2000	A
6068615	Brown et al.	May 2000	A
6073106	Rozen et al.	Jun 2000	A
6077246	Kullas et al.	Jun 2000	A
6083206	Molko	Jul 2000	A
6089104	Chang	Jul 2000	A
6104295	Gaisser et al.	Aug 2000	A
6110152	Kovelman	Aug 2000	A
6110153	Davis	Aug 2000	A
RE36871	Epstein et al.	Sep 2000	E
6120459	Nitzan et al.	Sep 2000	A
6122536	Sun et al.	Sep 2000	A
6142008	Cole et al.	Nov 2000	A
6150942	O'Brien	Nov 2000	A
6157914	Seto et al.	Dec 2000	A
6158288	Smith	Dec 2000	A
6158965	Butterfield et al.	Dec 2000	A
6159147	Lichter et al.	Dec 2000	A
6159186	Wickham et al.	Dec 2000	A
6164921	Moubayed et al.	Dec 2000	A
6168561	Cantu	Jan 2001	B1
6178827	Feller	Jan 2001	B1
6182667	Hanks et al.	Feb 2001	B1
6186141	Pike et al.	Feb 2001	B1
6189105	Lopes	Feb 2001	B1
6192752	Blaine	Feb 2001	B1
6195589	Ketcham	Feb 2001	B1
6202711	Martucci	Mar 2001	B1
6203528	Deckert	Mar 2001	B1
6208107	Maske et al.	Mar 2001	B1
6212936	Meisberger	Apr 2001	B1
6213972	Butterfield	Apr 2001	B1
6231320	Lawless et al.	May 2001	B1
6234176	Domae et al.	May 2001	B1
6236326	Murphy et al.	May 2001	B1
6237398	Porat et al.	May 2001	B1
6241704	Peterson et al.	Jun 2001	B1
6248067	Causey, III et al.	Jun 2001	B1
6250132	Drzewiecki	Jun 2001	B1
6259355	Chaco et al.	Jul 2001	B1
6259587	Sheldon et al.	Jul 2001	B1
6261065	Nayak	Jul 2001	B1
6262946	Khuri-Yakub et al.	Jul 2001	B1
6267559	Mossman et al.	Jul 2001	B1
6267725	Dubberstein 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
6277099	Strowe et al.	Aug 2001	B1
6280380	Bardy	Aug 2001	B1
6280391	Olson et al.	Aug 2001	B1
6280408	Sipin	Aug 2001	B1
6283761	Joao	Sep 2001	B1
6285155	Maske et al.	Sep 2001	B1
6312378	Bardy	Nov 2001	B1
6322516	Masuda et al.	Nov 2001	B1
6330351	Yasunaga	Dec 2001	B1
6336053	Beatty	Jan 2002	B1
6337675	Toffolo et al.	Jan 2002	B1
6345539	Rawes et al.	Feb 2002	B1
6347553	Morris et al.	Feb 2002	B1
6349740	Cho et al.	Feb 2002	B1
6358225	Butterfield	Mar 2002	B1
6358387	Kopf-Sill et al.	Mar 2002	B1
6362591	Moberg	Mar 2002	B1
6385505	Lipps	May 2002	B1
6386050	Yin et al.	May 2002	B1
6394958	Bratteli et al.	May 2002	B1
6396583	Clare	May 2002	B1
6398760	Danby	Jun 2002	B1
6405076	Taylor et al.	Jun 2002	B1
6408679	Kline-Schoder et al.	Jun 2002	B1
6413238	Maget	Jul 2002	B1
6416291	Butterfield et al.	Jul 2002	B1
6418334	Unger et al.	Jul 2002	B1
6418535	Kulakowski et al.	Jul 2002	B1
6445053	Cho	Sep 2002	B1
6456245	Crawford	Sep 2002	B1
6457346	Kline-Schoder et al.	Oct 2002	B1
6463785	Kline-Schoder et al.	Oct 2002	B1
6467331	Kline-Schoder et al.	Oct 2002	B1
6468242	Wilson et al.	Oct 2002	B1
6475178	Krajewski	Nov 2002	B1
6481980	Vandlik	Nov 2002	B1
6482158	Mault	Nov 2002	B2
6482185	Hartmann	Nov 2002	B1
6485263	Bryant et al.	Nov 2002	B1
6485418	Yasushi et al.	Nov 2002	B2
6485465	Moberg et al.	Nov 2002	B2
6487916	Gomm et al.	Dec 2002	B1
6489896	Platt	Dec 2002	B1
6494694	Lawless et al.	Dec 2002	B2
6494831	Koritzinsky	Dec 2002	B1
6497680	Holst et al.	Dec 2002	B1
6503221	Briggs	Jan 2003	B1
6512944	Kovtun et al.	Jan 2003	B1
6516667	Broad et al.	Feb 2003	B1
6517482	Eiden et al.	Feb 2003	B1
6519569	White et al.	Feb 2003	B1
6529751	Van Driel et al.	Mar 2003	B1
6531708	Malmstrom	Mar 2003	B1
6539315	Adams et al.	Mar 2003	B1
6540672	Simonsen et al.	Apr 2003	B1
6544212	Galley et al.	Apr 2003	B2
6544228	Heitmeier	Apr 2003	B1
6558125	Futterknecht	May 2003	B1
6558351	Steil et al.	May 2003	B1
6562012	Brown et al.	May 2003	B1
6564825	Lowery et al.	May 2003	B2
6565509	Say et al.	May 2003	B1
6568416	Tucker et al.	May 2003	B2
6572542	Houben et al.	Jun 2003	B1
6572545	Knobbe et al.	Jun 2003	B2
6572576	Brugger et al.	Jun 2003	B2
6578422	Lam et al.	Jun 2003	B2
6578435	Gould et al.	Jun 2003	B2
6581117	Klein et al.	Jun 2003	B1
RE38189	Walker et al.	Jul 2003	E
6585675	O'Mahony et al.	Jul 2003	B1
6589229	Connelly et al.	Jul 2003	B1
6589792	Malachowski	Jul 2003	B1
6599281	Struys et al.	Jul 2003	B1
6599282	Burko	Jul 2003	B2
6602191	Quy	Aug 2003	B2
6605072	Struys et al.	Aug 2003	B2
6606047	Börjesson et al.	Aug 2003	B1
6609047	Lipps	Aug 2003	B1
6615674	Ohnishi	Sep 2003	B2
6616633	Butterfield et al.	Sep 2003	B1
6617564	Ockerse et al.	Sep 2003	B2
6618916	Eberle et al.	Sep 2003	B1
6622542	Derek	Sep 2003	B2
6622561	Lam et al.	Sep 2003	B2
D481121	Evans	Oct 2003	S
6629449	Kline-Schoder et al.	Oct 2003	B1
6634233	He	Oct 2003	B2
6640246	Gardy, Jr. et al.	Oct 2003	B1
6641533	Causey, III et al.	Nov 2003	B2
6641541	Lovett et al.	Nov 2003	B1
6648861	Platt et al.	Nov 2003	B2
6652455	Kocher	Nov 2003	B1
6653937	Nelson et al.	Nov 2003	B2
6659980	Moberg et al.	Dec 2003	B2
D485356	Evans	Jan 2004	S
6685668	Cho et al.	Feb 2004	B1
6685678	Evans et al.	Feb 2004	B2
6689069	Bratteli et al.	Feb 2004	B2
6689091	Bui et al.	Feb 2004	B2
6692241	Watanabe et al.	Feb 2004	B2
6716004	Vandlik	Apr 2004	B2
6719535	Rakestraw et al.	Apr 2004	B2
6721582	Trepagnier et al.	Apr 2004	B2
6722211	Ciobanu et al.	Apr 2004	B1
6725200	Rost	Apr 2004	B1
6725721	Venczel	Apr 2004	B2
6731989	Engleson et al.	May 2004	B2
6732595	Lynnworth	May 2004	B2
6738052	Manke et al.	May 2004	B1
6740072	Starkweather et al.	May 2004	B2
6741212	Kralovec et al.	May 2004	B2
6748808	Lam et al.	Jun 2004	B2
6749403	Bryant et al.	Jun 2004	B2
6752787	Causey, III et al.	Jun 2004	B1
6753842	Williams et al.	Jun 2004	B1
6759007	Westberg	Jul 2004	B1
6760643	Lipps	Jul 2004	B2
6768920	Lange	Jul 2004	B2
6773412	O'Mahony	Aug 2004	B2
6780156	Haueter et al.	Aug 2004	B2
6783328	Lucke et al.	Aug 2004	B2
6785573	Kovtun et al.	Aug 2004	B2
6786885	Hochman et al.	Sep 2004	B2
6789426	Yaralioglu et al.	Sep 2004	B2
6790198	White et al.	Sep 2004	B1
6793625	Cavallaro et al.	Sep 2004	B2
6801227	Bocionek et al.	Oct 2004	B2
6805671	Stergiopoulos et al.	Oct 2004	B2
6807965	Hickle	Oct 2004	B1
6809653	Mann et al.	Oct 2004	B1
6813964	Clark et al.	Nov 2004	B1
6814547	Childers	Nov 2004	B2
6824528	Faries	Nov 2004	B1
6830558	Flaherty et al.	Dec 2004	B2
6840113	Fukumura et al.	Jan 2005	B2
6846161	Kline	Jan 2005	B2
6852094	Beck	Feb 2005	B2
6852104	Blomquist	Feb 2005	B2
6854338	Khuri-Yakub et al.	Feb 2005	B2
6857318	Silber et al.	Feb 2005	B1
6869425	Briggs et al.	Mar 2005	B2
6873268	Lebel et al.	Mar 2005	B2
6883376	He	Apr 2005	B2
6885881	Leonhardt	Apr 2005	B2
6887216	Hochman et al.	May 2005	B2
6898301	Iwanaga	May 2005	B2
6907361	Molenaar	Jun 2005	B2
6907792	Ohnishi	Jun 2005	B2
6915170	Engleson et al.	Jul 2005	B2
6920795	Bischoff et al.	Jul 2005	B2
6923763	Kovatchev et al.	Aug 2005	B1
6928338	Buchser et al.	Aug 2005	B1
6929619	Fago et al.	Aug 2005	B2
6929751	Bowman	Aug 2005	B2
6932114	Sparks	Aug 2005	B2
6932796	Sage et al.	Aug 2005	B2
6935192	Sobek et al.	Aug 2005	B2
6936029	Mann et al.	Aug 2005	B2
6941005	Lary et al.	Sep 2005	B2
6942636	Holst et al.	Sep 2005	B2
6945954	Hochman et al.	Sep 2005	B2
6958705	Lebel et al.	Oct 2005	B2
6964204	Clark et al.	Nov 2005	B2
6973374	Ader	Dec 2005	B2
6974437	Lebel et al.	Dec 2005	B2
6975922	Duncan et al.	Dec 2005	B2
6978779	Haveri et al.	Dec 2005	B2
6979326	Mann et al.	Dec 2005	B2
6981960	Cho et al.	Jan 2006	B2
6984218	Nayak et al.	Jan 2006	B2
6985768	Hemming et al.	Jan 2006	B2
6985870	Martucci et al.	Jan 2006	B2
6986347	Hickle	Jan 2006	B2
6986753	Bui	Jan 2006	B2
6997905	Gillespie, Jr. et al.	Feb 2006	B2
6997920	Mann et al.	Feb 2006	B2
7006005	Nazarian et al.	Feb 2006	B2
7017623	Tribble et al.	Mar 2006	B2
7021148	Kuhn	Apr 2006	B2
7025743	Mann et al.	Apr 2006	B2
7029455	Flaherty	Apr 2006	B2
7029456	Ware et al.	Apr 2006	B2
7059184	Kanouda et al.	Jun 2006	B2
7060059	Keith et al.	Jun 2006	B2
7069793	Ishikawa et al.	Jul 2006	B2
7072725	Bristol et al.	Jul 2006	B2
7074209	Evans et al.	Jul 2006	B2
7080557	Adnan	Jul 2006	B2
7082843	Clark et al.	Aug 2006	B2
7087444	Wong et al.	Aug 2006	B2
7092796	Vanderveen	Aug 2006	B2
7092797	Gaines et al.	Aug 2006	B2
7093502	Kupnik et al.	Aug 2006	B2
7096729	Repko et al.	Aug 2006	B2
7103419	Engleson et al.	Sep 2006	B2
7104763	Bouton et al.	Sep 2006	B2
7104769	Davis	Sep 2006	B2
7108680	Rohr et al.	Sep 2006	B2
7109878	Mann et al.	Sep 2006	B2
7115113	Evans et al.	Oct 2006	B2
7117041	Engleson et al.	Oct 2006	B2
7137964	Flaherty	Nov 2006	B2
7141037	Butterfield et al.	Nov 2006	B2
7152490	Freund, Jr. et al.	Dec 2006	B1
7154397	Zerhusen et al.	Dec 2006	B2
7161488	Frasch	Jan 2007	B2
7162290	Levin	Jan 2007	B1
7162927	Selvan et al.	Jan 2007	B1
7171277	Engleson et al.	Jan 2007	B2
7174789	Orr et al.	Feb 2007	B2
7185288	Mckeever	Feb 2007	B2
7197943	Lee et al.	Apr 2007	B2
7201734	Hickle	Apr 2007	B2
7204823	Estes et al.	Apr 2007	B2
7206715	Vanderveen et al.	Apr 2007	B2
7213009	Pestotnik	May 2007	B2
7220240	Struys et al.	May 2007	B2
7229430	Hickle et al.	Jun 2007	B2
7230529	Ketcherside	Jun 2007	B2
7232430	Carlisle	Jun 2007	B2
7238164	Childers et al.	Jul 2007	B2
7247154	Hickle	Jul 2007	B2
7253779	Greer et al.	Aug 2007	B2
7254425	Lowery et al.	Aug 2007	B2
7258534	Fathallah et al.	Aug 2007	B2
7267664	Rizzo	Sep 2007	B2
7267665	Steil et al.	Sep 2007	B2
7272529	Hogan et al.	Sep 2007	B2
7278983	Ireland et al.	Oct 2007	B2
7291123	Baraldi et al.	Nov 2007	B2
7293461	Gimdt	Nov 2007	B1
7294109	Lovett et al.	Nov 2007	B2
7296482	Schaffer et al.	Nov 2007	B2
7300418	Zaleski	Nov 2007	B2
7305883	Khuri-Yakub et al.	Dec 2007	B2
7327273	Hung et al.	Feb 2008	B2
7338470	Katz	Mar 2008	B2
7347836	Peterson et al.	Mar 2008	B2
7347854	Shelton et al.	Mar 2008	B2
7354420	Steil et al.	Apr 2008	B2
7356382	Vanderveen	Apr 2008	B2
7360999	Nelson et al.	Apr 2008	B2
7364562	Braig et al.	Apr 2008	B2
7367942	Grage et al.	May 2008	B2
7369948	Ferenczi et al.	May 2008	B1
7384410	Eggers et al.	Jun 2008	B2
7397166	Morgan et al.	Jul 2008	B1
7398183	Holland et al.	Jul 2008	B2
7399277	Saidara et al.	Jul 2008	B2
7402153	Steil et al.	Jul 2008	B2
7402154	Mendez	Jul 2008	B2
7407489	Mendez	Aug 2008	B2
7414534	Kroll et al.	Aug 2008	B1
7415895	Kurisaki et al.	Aug 2008	B2
7426443	Simon	Sep 2008	B2
7430675	Lee et al.	Sep 2008	B2
7447566	Knauper et al.	Nov 2008	B2
7447643	Olson	Nov 2008	B1
7452190	Bouton et al.	Nov 2008	B2
7454314	Holland et al.	Nov 2008	B2
7471994	Ford et al.	Dec 2008	B2
7477997	Kaplit	Jan 2009	B2
7482818	Greenwald et al.	Jan 2009	B2
7483756	Engleson et al.	Jan 2009	B2
7490021	Holland et al.	Feb 2009	B2
7491187	Van Den Berghe et al.	Feb 2009	B2
7503903	Carlisle et al.	Mar 2009	B2
7517332	Tonelli et al.	Apr 2009	B2
7523401	Aldridge	Apr 2009	B1
7545075	Huang et al.	Jun 2009	B2
7556616	Fathallah et al.	Jul 2009	B2
7561986	Vanderveen et al.	Jul 2009	B2
7571024	Duncan et al.	Aug 2009	B2
7605730	Tomioka et al.	Oct 2009	B2
7645258	White et al.	Jan 2010	B2
7654127	Krulevitch et al.	Feb 2010	B2
7657443	Crass	Feb 2010	B2
7668731	Martucci et al.	Feb 2010	B2
7678048	Urbano et al.	Mar 2010	B1
7693697	Westenskow et al.	Apr 2010	B2
7699806	Ware et al.	Apr 2010	B2
7705727	Pestotnik	Apr 2010	B2
7766873	Moberg et al.	Aug 2010	B2
7775126	Eckhardt	Aug 2010	B2
7775127	Wade	Aug 2010	B2
7785284	Baralsi et al.	Aug 2010	B2
7785313	Mastrototaro	Aug 2010	B2
7786909	Udupa et al.	Aug 2010	B2
7806886	Kanderian, Jr. et al.	Oct 2010	B2
7826981	Goode, Jr. et al.	Nov 2010	B2
7847276	Carlisle	Dec 2010	B2
7860583	Condurso et al.	Dec 2010	B2
7871394	Halbert et al.	Jan 2011	B2
7876443	Bernacki	Jan 2011	B2
7895053	Holland et al.	Feb 2011	B2
7895882	Carlisle	Mar 2011	B2
7896834	Smisson, III	Mar 2011	B2
7896842	Palmroos et al.	Mar 2011	B2
7905710	Wang et al.	Mar 2011	B2
7933780	de La Huerga	Apr 2011	B2
7945452	Fathallah et al.	May 2011	B2
7976508	Hoag	Jul 2011	B2
7981073	Mollstam	Jul 2011	B2
7981082	Wang et al.	Jul 2011	B2
7998134	Fangrow	Aug 2011	B2
8002736	Patrick et al.	Aug 2011	B2
8034020	Dewey	Oct 2011	B2
8038593	Friedman et al.	Oct 2011	B2
8065161	Howard et al.	Nov 2011	B2
8067760	Carlisle	Nov 2011	B2
8075514	Butterfield et al.	Dec 2011	B2
8075546	Carlisle et al.	Dec 2011	B2
8078983	Davis et al.	Dec 2011	B2
8121857	Galasso et al.	Feb 2012	B2
8149131	Blomquist	Apr 2012	B2
8175668	Nabutovsky et al.	May 2012	B1
8177739	Cartledge et al.	May 2012	B2
8180440	McCombie et al.	May 2012	B2
8185322	Schroeder et al.	May 2012	B2
8197444	Bazargan et al.	Jun 2012	B1
8219413	Martinez et al.	Jul 2012	B2
8221395	Shelton et al.	Jul 2012	B2
8226597	Jacobson et al.	Jul 2012	B2
8231578	Fathallah et al.	Jul 2012	B2
8234128	Martucci et al.	Jul 2012	B2
8271106	Wehba et al.	Sep 2012	B2
8287514	Miller et al.	Oct 2012	B2
8291337	Gannin et al.	Oct 2012	B2
8313308	Lawless et al.	Nov 2012	B2
8317698	Lowery	Nov 2012	B2
8317750	Ware et al.	Nov 2012	B2
8317752	Cozmi et al.	Nov 2012	B2
8318094	Bayandorian et al.	Nov 2012	B1
8340792	Condurso et al.	Dec 2012	B2
8347731	Genosar	Jan 2013	B2
8359338	Butterfield et al.	Jan 2013	B2
8361021	Wang et al.	Jan 2013	B2
8378837	Wang et al.	Feb 2013	B2
8388598	Steinkogler	Mar 2013	B2
8398616	Budiman	Mar 2013	B2
8403908	Jacobson et al.	Mar 2013	B2
8409164	Fangrow	Apr 2013	B2
8449524	Braig et al.	May 2013	B2
8469942	Kow et al.	Jun 2013	B2
8477307	Yufa et al.	Jul 2013	B1
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
8522832	Lopez et al.	Sep 2013	B2
8523797	Lowery et al.	Sep 2013	B2
8539812	Stringham et al.	Sep 2013	B2
8543416	Palmroos et al.	Sep 2013	B2
8577692	Silkaitis et al.	Nov 2013	B2
8622990	Estes et al.	Jan 2014	B2
8630722	Condurso et al.	Jan 2014	B2
8665214	Forutanpour et al.	Mar 2014	B2
8666769	Butler et al.	Mar 2014	B2
8700421	Feng et al.	Apr 2014	B2
8706233	Su et al.	Apr 2014	B2
8721584	Braithwaite et al.	May 2014	B2
8728020	Caleffi et al.	May 2014	B2
8758306	Lopez et al.	Jun 2014	B2
8761906	Condurso et al.	Jun 2014	B2
8768719	Wehba et al.	Jul 2014	B2
8771251	Ruchti et al.	Jul 2014	B2
8792981	Yudovsky et al.	Jul 2014	B2
8821432	Unverdorben	Sep 2014	B2
8823382	Rondoni et al.	Sep 2014	B2
8857269	Johnson et al.	Oct 2014	B2
8858185	Johnson et al.	Oct 2014	B2
8905965	Mandro et al.	Dec 2014	B2
8964185	Luo et al.	Feb 2015	B1
9005150	Ware et al.	Apr 2015	B2
9026370	Rubalcaba et al.	May 2015	B2
9084855	Ware et al.	Jul 2015	B2
9114217	Sur et al.	Aug 2015	B2
9134735	Lowery et al.	Sep 2015	B2
9134736	Lowery et al.	Sep 2015	B2
9138526	Ware et al.	Sep 2015	B2
9190010	Vik et al.	Nov 2015	B2
9240002	Hume et al.	Jan 2016	B2
9272089	Jacobson et al.	Mar 2016	B2
9316216	Cook et al.	Apr 2016	B1
9333291	Jacobson et al.	May 2016	B2
9381296	Arrizza et al.	Jul 2016	B2
9393362	Cozmi et al.	Jul 2016	B2
9468718	Hung et al.	Oct 2016	B2
9498583	Sur et al.	Nov 2016	B2
9545475	Borges et al.	Jan 2017	B2
9707341	Dumas, III et al.	Jul 2017	B2
9764087	Peterfreund et al.	Sep 2017	B2
9852265	Treacy et al.	Dec 2017	B1
9883987	Lopez et al.	Feb 2018	B2
9943269	Muhsin	Apr 2018	B2
9995611	Ruchti et al.	Jun 2018	B2
10022498	Ruchti et al.	Jul 2018	B2
10046112	Oruklu et al.	Aug 2018	B2
10089055	Fryman	Oct 2018	B1
10099009	Anderson et al.	Oct 2018	B1
10166328	Oruklu et al.	Jan 2019	B2
10342917	Shubinsky et al.	Jul 2019	B2
10430761	Hume et al.	Oct 2019	B2
10463788	Day	Nov 2019	B2
10549248	Brown et al.	Feb 2020	B2
10578474	Ruchti et al.	Mar 2020	B2
10596316	Dumas, III et al.	Mar 2020	B2
10635784	Rubalcaba, Jr. et al.	Apr 2020	B2
10656894	Fryman	May 2020	B2
10682102	Declerck	Jun 2020	B2
10709885	Janders et al.	Jul 2020	B2
10850024	Day et al.	Dec 2020	B2
10874793	Oruklu et al.	Dec 2020	B2
11004035	Hume et al.	May 2021	B2
D923050	Kataoka et al.	Jun 2021	S
11029911	Fryman	Jun 2021	B2
D928813	Nurutdinov et al.	Aug 2021	S
D928840	Amit et al.	Aug 2021	S
11090431	Dumas, III et al.	Aug 2021	B2
D931884	Bryant et al.	Sep 2021	S
11135360	Jacobson et al.	Oct 2021	B1
11246985	Gylland et al.	Feb 2022	B2
11298456	Shubinsky et al.	Apr 2022	B2
11324888	Shubinsky et al.	May 2022	B2
11344668	Sileika et al.	May 2022	B2
11344673	Lindo et al.	May 2022	B2
11376361	Ruchti et al.	Jul 2022	B2
11378430	Ruchti et al.	Jul 2022	B2
11395875	Rubalcaba, Jr. et al.	Jul 2022	B2
11433177	Oruklu et al.	Sep 2022	B2
11596737	Dumas, III et al.	Mar 2023	B2
11599854	Hume et al.	Mar 2023	B2
11623042	Day	Apr 2023	B2
20010007636	Butterfield	Jul 2001	A1
20010014769	Bufe et al.	Aug 2001	A1
20010015099	Blaine	Aug 2001	A1
20010016056	Westphal et al.	Aug 2001	A1
20010032099	Joao	Oct 2001	A1
20010037060	Thompson et al.	Nov 2001	A1
20010041869	Causey et al.	Nov 2001	A1
20010044731	Coffman et al.	Nov 2001	A1
20020003892	Iwanaga	Jan 2002	A1
20020007116	Zatezalo et al.	Jan 2002	A1
20020013545	Soltanpour et al.	Jan 2002	A1
20020013551	Zaitsu et al.	Jan 2002	A1
20020015018	Shimazu et al.	Feb 2002	A1
20020018720	Carlisle et al.	Feb 2002	A1
20020029776	Blomquist	Mar 2002	A1
20020031838	Meinhart et al.	Mar 2002	A1
20020032583	Joao	Mar 2002	A1
20020040208	Flaherty et al.	Apr 2002	A1
20020044059	Reeder et al.	Apr 2002	A1
20020045806	Baker, Jr. et al.	Apr 2002	A1
20020082728	Mueller et al.	Jun 2002	A1
20020083771	Khuri-Yakub et al.	Jul 2002	A1
20020085952	Ellingboe et al.	Jul 2002	A1
20020087115	Hartlaub	Jul 2002	A1
20020093641	Ortyn et al.	Jul 2002	A1
20020095486	Bahl	Jul 2002	A1
20020099282	Knobbe et al.	Jul 2002	A1
20020099334	Hanson et al.	Jul 2002	A1
20020143580	Bristol et al.	Oct 2002	A1
20020147389	Cavallaro et al.	Oct 2002	A1
20020152239	Bautista-Lloyd et al.	Oct 2002	A1
20020168278	Jeon et al.	Nov 2002	A1
20020173703	Lebel et al.	Nov 2002	A1
20020183693	Peterson et al.	Dec 2002	A1
20030009244	Engleson	Jan 2003	A1
20030013959	Grunwald et al.	Jan 2003	A1
20030018289	Ng et al.	Jan 2003	A1
20030018308	Tsai	Jan 2003	A1
20030025602	Medema et al.	Feb 2003	A1
20030028082	Thompson	Feb 2003	A1
20030030001	Cooper et al.	Feb 2003	A1
20030045840	Burko	Mar 2003	A1
20030050621	Lebel et al.	Mar 2003	A1
20030060688	Ciarniello et al.	Mar 2003	A1
20030060765	Campbell et al.	Mar 2003	A1
20030065537	Evans	Apr 2003	A1
20030065589	Giacchetti	Apr 2003	A1
20030073954	Moberg et al.	Apr 2003	A1
20030079746	Hickle	May 2003	A1
20030083583	Kovtun et al.	May 2003	A1
20030091442	Bush et al.	May 2003	A1
20030104982	Wittmann et al.	Jun 2003	A1
20030106553	Vanderveen	Jun 2003	A1
20030125662	Bui	Jul 2003	A1
20030130616	Steil	Jul 2003	A1
20030135087	Hickle et al.	Jul 2003	A1
20030136193	Fujimoto	Jul 2003	A1
20030139701	White et al.	Jul 2003	A1
20030140928	Bui 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
20030158508	DiGianfilippo	Aug 2003	A1
20030160683	Blomquist	Aug 2003	A1
20030163789	Blomquist	Aug 2003	A1
20030173408	Mosher, Jr. et al.	Sep 2003	A1
20030186833	Huff et al.	Oct 2003	A1
20030187338	Say et al.	Oct 2003	A1
20030194328	Bryant et al.	Oct 2003	A1
20030200116	Forrester	Oct 2003	A1
20030204274	Ullestad et al.	Oct 2003	A1
20030204416	Acharya	Oct 2003	A1
20030212364	Mann et al.	Nov 2003	A1
20030212379	Bylund et al.	Nov 2003	A1
20030216682	Junker	Nov 2003	A1
20030217962	Childers et al.	Nov 2003	A1
20030233071	Gillespie, Jr. et al.	Dec 2003	A1
20040030277	O'Mahony et al.	Feb 2004	A1
20040047736	Nose et al.	Mar 2004	A1
20040057226	Berthou et al.	Mar 2004	A1
20040064342	Browne et al.	Apr 2004	A1
20040073125	Lovett et al.	Apr 2004	A1
20040073161	Tachibana	Apr 2004	A1
20040077996	Jasperson et al.	Apr 2004	A1
20040082908	Whitehurst	Apr 2004	A1
20040082918	Evans et al.	Apr 2004	A1
20040104271	Martucci et al.	Jun 2004	A1
20040119753	Zencke	Jun 2004	A1
20040120825	Bouton et al.	Jun 2004	A1
20040128162	Schlotterbeck et al.	Jul 2004	A1
20040128163	Goodman et al.	Jul 2004	A1
20040133166	Moberg et al.	Jul 2004	A1
20040145114	Ippolito et al.	Jul 2004	A1
20040147034	Gore et al.	Jul 2004	A1
20040149823	Aptekar	Aug 2004	A1
20040152970	Hunter et al.	Aug 2004	A1
20040158193	Bui et al.	Aug 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
20040172289	Kozic et al.	Sep 2004	A1
20040172301	Mihai et al.	Sep 2004	A1
20040172302	Martucci et al.	Sep 2004	A1
20040176984	White et al.	Sep 2004	A1
20040181314	Zaleski	Sep 2004	A1
20040193025	Steil et al.	Sep 2004	A1
20040193325	Bonderud	Sep 2004	A1
20040193328	Butterfield et al.	Sep 2004	A1
20040193453	Butterfield et al.	Sep 2004	A1
20040204638	Diab et al.	Oct 2004	A1
20040204673	Flaherty et al.	Oct 2004	A1
20040220517	Starkweather et al.	Nov 2004	A1
20040225252	Gillespie et al.	Nov 2004	A1
20040225409	Duncan et al.	Nov 2004	A1
20040232219	Fowler	Nov 2004	A1
20040247445	Nelson et al.	Dec 2004	A1
20040253123	Xie et al.	Dec 2004	A1
20040254434	Goodnow et al.	Dec 2004	A1
20040254513	Shang et al.	Dec 2004	A1
20050021006	Tonnies	Jan 2005	A1
20050021297	Hartlaub	Jan 2005	A1
20050022274	Campbell et al.	Jan 2005	A1
20050038680	McMahon	Feb 2005	A1
20050055242	Bello et al.	Mar 2005	A1
20050055244	Mullan et al.	Mar 2005	A1
20050065465	Lebel et al.	Mar 2005	A1
20050075544	Shapiro et al.	Apr 2005	A1
20050096593	Pope et al.	May 2005	A1
20050099624	Staehr	May 2005	A1
20050107923	Vanderveen	May 2005	A1
20050108057	Cohen et al.	May 2005	A1
20050119597	O'Mahony et al.	Jun 2005	A1
20050119914	Batch	Jun 2005	A1
20050131739	Rabinowitz et al.	Jun 2005	A1
20050137522	Aoki	Jun 2005	A1
20050143864	Blomquist	Jun 2005	A1
20050145010	Vanderveen et al.	Jul 2005	A1
20050171503	Van Den Berghe et al.	Aug 2005	A1
20050171815	Vanderveen	Aug 2005	A1
20050177045	Degertekin et al.	Aug 2005	A1
20050177096	Bollish et al.	Aug 2005	A1
20050182306	Sloan	Aug 2005	A1
20050182355	Bui	Aug 2005	A1
20050182366	Vogt et al.	Aug 2005	A1
20050187515	Varrichio et al.	Aug 2005	A1
20050192529	Butterfield et al.	Sep 2005	A1
20050192557	Brauker et al.	Sep 2005	A1
20050197554	Polcha	Sep 2005	A1
20050197621	Poulsen et al.	Sep 2005	A1
20050197649	Shelton et al.	Sep 2005	A1
20050204828	Lee et al.	Sep 2005	A1
20050209563	Hopping et al.	Sep 2005	A1
20050209793	Yamada	Sep 2005	A1
20050224083	Crass	Oct 2005	A1
20050235732	Rush	Oct 2005	A1
20050238506	Mescher et al.	Oct 2005	A1
20050240305	Bogash et al.	Oct 2005	A1
20050273059	Mernoe et al.	Dec 2005	A1
20050277890	Stewart et al.	Dec 2005	A1
20050279419	Tribble et al.	Dec 2005	A1
20060002799	Schann et al.	Jan 2006	A1
20060009727	O'Mahony et al.	Jan 2006	A1
20060009734	Martin	Jan 2006	A1
20060042633	Bishop et al.	Mar 2006	A1
20060047270	Shelton	Mar 2006	A1
20060053036	Coffman et al.	Mar 2006	A1
20060064020	Burnes et al.	Mar 2006	A1
20060064053	Bollish et al.	Mar 2006	A1
20060079768	Small et al.	Apr 2006	A1
20060079831	Gilbert	Apr 2006	A1
20060100746	Leibner-Druska	May 2006	A1
20060100907	Holland et al.	May 2006	A1
20060106649	Eggers et al.	May 2006	A1
20060116639	Russell	Jun 2006	A1
20060117856	Orr et al.	Jun 2006	A1
20060117867	Froehlich et al.	Jun 2006	A1
20060122867	Eggers et al.	Jun 2006	A1
20060135939	Brown	Jun 2006	A1
20060135940	Joshi	Jun 2006	A1
20060136095	Rob et al.	Jun 2006	A1
20060136271	Eggers et al.	Jun 2006	A1
20060140798	Kutsuzawa	Jun 2006	A1
20060143051	Eggers et al.	Jun 2006	A1
20060173260	Gaoni et al.	Aug 2006	A1
20060173406	Hayes et al.	Aug 2006	A1
20060180916	Wyland	Aug 2006	A1
20060181695	Sage, Jr.	Aug 2006	A1
20060187069	Duan	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
20060224140	Junker	Oct 2006	A1
20060224141	Rush et al.	Oct 2006	A1
20060224181	McEwen et al.	Oct 2006	A1
20060226088	Robinson et al.	Oct 2006	A1
20060226089	Robinson et al.	Oct 2006	A1
20060226090	Robinson et al.	Oct 2006	A1
20060229918	Fotsch et al.	Oct 2006	A1
20060235353	Gelfand et al.	Oct 2006	A1
20060255149	Retter et al.	Nov 2006	A1
20060258985	Russell	Nov 2006	A1
20060260416	Sage et al.	Nov 2006	A1
20060264895	Flanders	Nov 2006	A1
20060265246	Hoag	Nov 2006	A1
20060266128	Clark et al.	Nov 2006	A1
20060270971	Gelfand et al.	Nov 2006	A1
20060271286	Rosenberg	Nov 2006	A1
20060272421	Frinak et al.	Dec 2006	A1
20060275142	Bouton et al.	Dec 2006	A1
20070015972	Wang et al.	Jan 2007	A1
20070036511	Lundquist et al.	Feb 2007	A1
20070060796	Kim	Mar 2007	A1
20070060871	Istoc	Mar 2007	A1
20070060872	Hall et al.	Mar 2007	A1
20070060874	Nesbitt et al.	Mar 2007	A1
20070062250	Krulevitch et al.	Mar 2007	A1
20070065363	Dalal et al.	Mar 2007	A1
20070078314	Grounsell	Apr 2007	A1
20070083152	Williams, Jr. et al.	Apr 2007	A1
20070084286	Ajay et al.	Apr 2007	A1
20070084288	Thomas et al.	Apr 2007	A1
20070088271	Richards	Apr 2007	A1
20070088333	Levin et al.	Apr 2007	A1
20070093753	Krulevitcvh et al.	Apr 2007	A1
20070094045	Cobbs et al.	Apr 2007	A1
20070094046	Cobbs et al.	Apr 2007	A1
20070100222	Mastrototaro et al.	May 2007	A1
20070100665	Brown	May 2007	A1
20070112298	Mueller et al.	May 2007	A1
20070118405	Campbell et al.	May 2007	A1
20070129618	Goldberger et al.	Jun 2007	A1
20070142822	Remde	Jun 2007	A1
20070156452	Batch	Jul 2007	A1
20070156456	McGillin et al.	Jul 2007	A1
20070179436	Braig et al.	Aug 2007	A1
20070179437	Grage et al.	Aug 2007	A1
20070180916	Tian et al.	Aug 2007	A1
20070191770	Moberg et al.	Aug 2007	A1
20070191817	Martin	Aug 2007	A1
20070197963	Griffiths et al.	Aug 2007	A1
20070214003	Holland et al.	Sep 2007	A1
20070215545	Bissler et al.	Sep 2007	A1
20070233035	Wehba et al.	Oct 2007	A1
20070233049	Wehba et al.	Oct 2007	A1
20070240497	Robinson et al.	Oct 2007	A1
20070250339	Mallett et al.	Oct 2007	A1
20070255250	Moberg et al.	Nov 2007	A1
20070257788	Carlson	Nov 2007	A1
20070267945	Sudol	Nov 2007	A1
20070270747	Remde	Nov 2007	A1
20070274843	Vanderveen et al.	Nov 2007	A1
20070289384	Sakai et al.	Dec 2007	A1
20080009684	Corsetti et al.	Jan 2008	A1
20080028868	Konzelmann et al.	Feb 2008	A1
20080033361	Evans et al.	Feb 2008	A1
20080039777	Katz et al.	Feb 2008	A1
20080048211	Khuri-Yakub et al.	Feb 2008	A1
20080058773	John	Mar 2008	A1
20080060448	Wiest et al.	Mar 2008	A1
20080065420	Tirinato et al.	Mar 2008	A1
20080071210	Moubayed et al.	Mar 2008	A1
20080071496	Glascock	Mar 2008	A1
20080071580	Marcus et al.	Mar 2008	A1
20080077116	Dailey et al.	Mar 2008	A1
20080091466	Butler et al.	Apr 2008	A1
20080097288	Levin et al.	Apr 2008	A1
20080097289	Steil et al.	Apr 2008	A1
20080097317	Alholm et al.	Apr 2008	A1
20080098798	Riley et al.	May 2008	A1
20080119822	Knauper	May 2008	A1
20080125701	Moberg et al.	May 2008	A1
20080139907	Rao et al.	Jun 2008	A1
20080145249	Smisson	Jun 2008	A1
20080169044	Osborne et al.	Jul 2008	A1
20080172030	Blomquist et al.	Jul 2008	A1
20080177254	Shelton et al.	Jul 2008	A1
20080184784	Dam	Aug 2008	A1
20080188789	Galavotti et al.	Aug 2008	A1
20080188796	Steil et al.	Aug 2008	A1
20080208484	Butterfield et al.	Aug 2008	A1
20080214919	Harmon et al.	Sep 2008	A1
20080221521	Getz et al.	Sep 2008	A1
20080221522	Moberg et al.	Sep 2008	A1
20080262469	Bristol et al.	Oct 2008	A1
20080269663	Arnold 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
20090001908	Shubinsky et al.	Jan 2009	A1
20090005703	Fasciano	Jan 2009	A1
20090006061	Thukral et al.	Jan 2009	A1
20090006129	Thukral	Jan 2009	A1
20090006133	Weinert	Jan 2009	A1
20090015824	Shubinsky et al.	Jan 2009	A1
20090043171	Rule	Feb 2009	A1
20090054743	Stewart	Feb 2009	A1
20090054754	McMahon et al.	Feb 2009	A1
20090069743	Krishnamoorthy et al.	Mar 2009	A1
20090077248	Castellucci	Mar 2009	A1
20090082676	Bennison	Mar 2009	A1
20090088731	Campbell et al.	Apr 2009	A1
20090097029	Tokhtuev et al.	Apr 2009	A1
20090099866	Newman	Apr 2009	A1
20090105636	Hayter et al.	Apr 2009	A1
20090112155	Zhao	Apr 2009	A1
20090114037	Smith	May 2009	A1
20090119330	Sampath et al.	May 2009	A1
20090124963	Hogard et al.	May 2009	A1
20090124964	Leach et al.	May 2009	A1
20090126825	Eliuk et al.	May 2009	A1
20090131861	Braig et al.	May 2009	A1
20090135196	Holland et al.	May 2009	A1
20090143726	Bouton et al.	Jun 2009	A1
20090144025	Bouton et al.	Jun 2009	A1
20090144026	Bouton et al.	Jun 2009	A1
20090149743	Barron et al.	Jun 2009	A1
20090156922	Goldberger et al.	Jun 2009	A1
20090156975	Robinson et al.	Jun 2009	A1
20090177146	Nesbitt et al.	Jul 2009	A1
20090177188	Steinkogler	Jul 2009	A1
20090177248	Roberts	Jul 2009	A1
20090177769	Roberts	Jul 2009	A1
20090177992	Rubalcaba et al.	Jul 2009	A1
20090178485	Thomas et al.	Jul 2009	A1
20090183147	Davis et al.	Jul 2009	A1
20090192367	Braig et al.	Jul 2009	A1
20090198347	Kirzinger	Aug 2009	A1
20090205426	Balschat et al.	Aug 2009	A1
20090209938	Aalto-Setala	Aug 2009	A1
20090209945	Lobl et al.	Aug 2009	A1
20090212966	Panduro	Aug 2009	A1
20090221890	Saffer et al.	Sep 2009	A1
20090223294	Thomas et al.	Sep 2009	A1
20090227939	Memoe et al.	Sep 2009	A1
20090264720	Torjman et al.	Oct 2009	A1
20090270810	DeBelser	Oct 2009	A1
20090270833	DeBelser	Oct 2009	A1
20100022988	Wochner	Jan 2010	A1
20100280430	Caleffi et al.	Jan 2010	A1
20100036310	Hillman	Feb 2010	A1
20100056992	Hayter	Mar 2010	A1
20100057042	Hayter	Mar 2010	A1
20100069892	Steinbach et al.	Mar 2010	A1
20100077866	Graboi et al.	Apr 2010	A1
20100079760	Bernacki	Apr 2010	A1
20100094251	Estes et al.	Apr 2010	A1
20100106082	Zhou	Apr 2010	A1
20100114027	Jacobson et al.	May 2010	A1
20100121170	Rule	May 2010	A1
20100121415	Skelton et al.	May 2010	A1
20100130933	Holland et al.	May 2010	A1
20100131434	Magent et al.	May 2010	A1
20100141460	Tokhtuev et al.	Jun 2010	A1
20100147081	Thomas et al.	Jun 2010	A1
20100152554	Steine et al.	Jun 2010	A1
20100160854	Gauthier	Jun 2010	A1
20100168535	Robinson et al.	Jul 2010	A1
20100177375	Seyfried	Jul 2010	A1
20100185142	Kamen et al.	Jul 2010	A1
20100185182	Alme et al.	Jul 2010	A1
20100198034	Thomas et al.	Aug 2010	A1
20100198182	Lanigan et al.	Aug 2010	A1
20100198183	Lanigan et al.	Aug 2010	A1
20100211002	Davis	Aug 2010	A1
20100212407	Stringham et al.	Aug 2010	A1
20100212675	Walling et al.	Aug 2010	A1
20100217154	Deshmukh et al.	Aug 2010	A1
20100217621	Schoenberg	Aug 2010	A1
20100256562	Cartledge et al.	Oct 2010	A1
20100271218	Hoag et al.	Oct 2010	A1
20100271479	Heydlauf	Oct 2010	A1
20100273738	Valcke et al.	Oct 2010	A1
20100292634	Kircher	Nov 2010	A1
20100295686	Sloan et al.	Nov 2010	A1
20100298765	Budiman et al.	Nov 2010	A1
20100312039	Quirico et al.	Dec 2010	A1
20100317093	Turewicz et al.	Dec 2010	A1
20100317952	Budiman et al.	Dec 2010	A1
20100318025	John	Dec 2010	A1
20110000560	Miller et al.	Jan 2011	A1
20110001605	Kiani et al.	Jan 2011	A1
20110004186	Butterfield	Jan 2011	A1
20110009797	Kelly et al.	Jan 2011	A1
20110028885	Eggers et al.	Feb 2011	A1
20110040247	Mandro et al.	Feb 2011	A1
20110046558	Gravesen et al.	Feb 2011	A1
20110062703	Lopez et al.	Mar 2011	A1
20110064612	Franzoni et al.	Mar 2011	A1
20110071464	Palerm	Mar 2011	A1
20110071844	Cannon et al.	Mar 2011	A1
20110072379	Gannon	Mar 2011	A1
20110077480	Bloom et al.	Mar 2011	A1
20110078608	Gannon et al.	Mar 2011	A1
20110099313	Bolanowski	Apr 2011	A1
20110105983	Kelly et al.	May 2011	A1
20110106561	Eaton, Jr. et al.	May 2011	A1
20110107251	Guaitoli et al.	May 2011	A1
20110137241	DelCastillo et al.	Jun 2011	A1
20110144595	Cheng	Jun 2011	A1
20110152770	Diperna et al.	Jun 2011	A1
20110160649	Pan	Jun 2011	A1
20110162647	Huby et al.	Jul 2011	A1
20110172918	Tome	Jul 2011	A1
20110175728	Baker, Jr.	Jul 2011	A1
20110190598	Shusterman	Aug 2011	A1
20110190694	Lanier et al.	Aug 2011	A1
20110218514	Rebours	Sep 2011	A1
20110264006	Ali et al.	Oct 2011	A1
20110264043	Kotnick et al.	Oct 2011	A1
20110282321	Steil et al.	Nov 2011	A1
20110313390	Roy et al.	Dec 2011	A1
20110319728	Petisce et al.	Dec 2011	A1
20110320049	Chossat et al.	Dec 2011	A1
20120025995	Moberg et al.	Feb 2012	A1
20120059234	Barrett et al.	Mar 2012	A1
20120068001	Pushkarsky et al.	Mar 2012	A1
20120083760	Ledford et al.	Apr 2012	A1
20120089411	Srnka et al.	Apr 2012	A1
20120095433	Hungerford et al.	Apr 2012	A1
20120123322	Scarpaci et al.	May 2012	A1
20120143116	Ware et al.	Jun 2012	A1
20120180790	Montgomery	Jul 2012	A1
20120185267	Kamen et al.	Jul 2012	A1
20120191059	Cummings et al.	Jul 2012	A1
20120194341	Peichel et al.	Aug 2012	A1
20120203177	Lanier	Aug 2012	A1
20120222774	Husnu et al.	Sep 2012	A1
20120226350	Rudser et al.	Sep 2012	A1
20120245525	Pope et al.	Sep 2012	A1
20120259278	Hayes et al.	Oct 2012	A1
20120310204	Krogh et al.	Dec 2012	A1
20120323212	Murphy	Dec 2012	A1
20130006666	Schneider	Jan 2013	A1
20130009551	Knapp	Jan 2013	A1
20130012880	Blomquist	Jan 2013	A1
20130012917	Miller et al.	Jan 2013	A1
20130032634	McKirdy	Feb 2013	A1
20130041342	Bernini et al.	Feb 2013	A1
20130044111	VanGilder et al.	Feb 2013	A1
20130110538	Butterfield et al.	May 2013	A1
20130150766	Olde et al.	Jun 2013	A1
20130150821	Bollish et al.	Jun 2013	A1
20130184676	Kamen et al.	Jul 2013	A1
20130197930	Garibaldi et al.	Aug 2013	A1
20130201482	Munro	Aug 2013	A1
20130218080	Peterfreund et al.	Aug 2013	A1
20130116649	Kouyoumjian et al.	Sep 2013	A1
20130253430	Kouyoumjian et al.	Sep 2013	A1
20130253946	Broselow	Sep 2013	A1
20130274576	Amirouche et al.	Oct 2013	A1
20130281965	Kamen et al.	Oct 2013	A1
20130291116	Homer	Oct 2013	A1
20130296823	Melker et al.	Nov 2013	A1
20130296984	Burnett et al.	Nov 2013	A1
20130318158	Teng	Nov 2013	A1
20130322201	Hitchcock et al.	Dec 2013	A1
20130345658	Browne et al.	Dec 2013	A1
20130345666	Panduro et al.	Dec 2013	A1
20140067425	Dudar et al.	Mar 2014	A1
20140145915	Ribble et al.	May 2014	A1
20140180711	Kamen et al.	Jun 2014	A1
20140224829	Capone et al.	Aug 2014	A1
20140267563	Baca	Sep 2014	A1
20140303591	Peterfreund et al.	Oct 2014	A1
20140303754	Nixon et al.	Oct 2014	A1
20150025453	Ledford et al.	Jan 2015	A1
20150033073	Yang	Jan 2015	A1
20150065988	Holderle et al.	Mar 2015	A1
20150168958	Downie et al.	Jun 2015	A1
20150224252	Borges et al.	Aug 2015	A1
20150265765	Yavorsky et al.	Sep 2015	A1
20150338340	Jiang et al.	Nov 2015	A1
20150343141	Lindo et al.	Dec 2015	A1
20150371004	Jones	Dec 2015	A1
20160042264	Borges et al.	Feb 2016	A1
20160110088	Vik et al.	Apr 2016	A1
20160144101	Pananen	May 2016	A1
20160151560	Toro et al.	Jun 2016	A1
20160151562	Magers et al.	Jun 2016	A1
20160151601	Cardelius et al.	Jun 2016	A1
20160158437	Biasi et al.	Jun 2016	A1
20160175517	Sileika et al.	Jun 2016	A1
20160193604	McFarland et al.	Jul 2016	A1
20160253460	Kanada	Sep 2016	A1
20160256622	Day et al.	Sep 2016	A1
20160339167	Ledford et al.	Nov 2016	A1
20170043089	Handler	Feb 2017	A1
20170132867	Berg et al.	May 2017	A1
20170354941	Brown et al.	Dec 2017	A1
20180018440	Sugawara	Jan 2018	A1
20180028749	Dumas, III et al.	Feb 2018	A1
20180300994	Nelson et al.	Oct 2018	A1
20190091401	Ruchti et al.	Mar 2019	A1
20190101425	Ruchti et al.	Apr 2019	A1
20190117890	Oruklu et al.	Apr 2019	A1
20190196770	Fryman	Jun 2019	A1
20190262535	Shubinsky et al.	Aug 2019	A1
20190282757	Gylland et al.	Sep 2019	A1
20200069864	Shubinsky et al.	Mar 2020	A1
20200090122	Hume	Mar 2020	A1
20200113784	Lopez et al.	Apr 2020	A1
20200238007	Day	Jul 2020	A1
20200271499	Ruchti et al.	Aug 2020	A1
20200282137	Dumas, III et al.	Sep 2020	A1
20200324044	Gylland et al.	Oct 2020	A1
20200357500	Rubalcaba, Jr. et al.	Nov 2020	A1
20210170101	Cavendish, Jr. et al.	Jun 2021	A1
20210260283	Oruklu et al.	Aug 2021	A1
20220176037	Jacobson et al.	Jun 2022	A1
20220296806	Shubinsky et al.	Sep 2022	A1
20220305200	Gylland et al.	Sep 2022	A1
20220331518	Shubinsky et al.	Oct 2022	A1
20220362463	Lindo et al.	Nov 2022	A1
20230010290	Oruklu et al.	Jan 2023	A1
20230010638	Rubalcaba, Jr. et al.	Jan 2023	A1
20230017117	Sileika et al.	Jan 2023	A1
20230058662	Ruchti et al.	Feb 2023	A1
20230058894	Ruchti et al.	Feb 2023	A1

Foreign Referenced Citations (187)

Number	Date	Country
2013216679	Sep 2013	AU
PI0704229-9	Nov 2009	BR
2 113 473	Mar 1993	CA
2 551 817	Jul 2005	CA
107106042	Aug 2017	CN
31 12 762	Jan 1983	DE
34 35 647	Jul 1985	DE
35 30 747	Mar 1987	DE
37 20 664	Jan 1989	DE
38 27 444	Feb 1990	DE
197 34 002	Sep 1998	DE
199 01 078	Feb 2000	DE
198 40 965	Mar 2000	DE
198 44 252	Mar 2000	DE
199 32 147	Jan 2001	DE
102 49 238	May 2004	DE
103 52 456	Jul 2005	DE
0 282 323	Sep 1988	EP
0 291 727	Nov 1988	EP
0 319 272	Jun 1989	EP
0 319 275	Jun 1989	EP
0 335 385	Oct 1989	EP
0 337 092	Oct 1989	EP
0 341 582	Nov 1989	EP
0 370 162	May 1990	EP
0 387 724	Sep 1990	EP
0 429 866	Jun 1991	EP
0 441 323	Aug 1991	EP
0 453 211	Oct 1991	EP
0 462 405	Dec 1991	EP
0 501 234	Sep 1992	EP
0 516 130	Dec 1992	EP
0 519 765	Dec 1992	EP
0 643 301	Mar 1995	EP
0 683 465	Nov 1995	EP
0 431 310	Jan 1996	EP
0 589 439	Aug 1998	EP
0 880 936	Dec 1998	EP
0 954 090	Nov 1999	EP
0 960 627	Dec 1999	EP
1 174 817	Jan 2002	EP
1 177 802	Feb 2002	EP
1 197 178	Apr 2002	EP
1 500 025	Apr 2003	EP
1 813 188	Aug 2007	EP
1 490 131	Dec 2007	EP
2 062 527	May 2009	EP
2 228 004	Sep 2010	EP
2 243 506	Oct 2010	EP
2 381 260	Oct 2011	EP
254513	Oct 1981	ES
2 717 919	Sep 1995	FR
2 121 971	Jan 1984	GB
2 303 706	Feb 1997	GB
2 312 022	Oct 1997	GB
2 312 046	Oct 1997	GB
01-301118	Dec 1989	JP
01-308568	Dec 1989	JP
04-231966	Aug 1992	JP
07-502678	Mar 1995	JP
07-289638	Nov 1995	JP
11-128344	May 1999	JP
2000-111374	Apr 2000	JP
2000-510575	Aug 2000	JP
2000-515716	Nov 2000	JP
2001-356034	Dec 2001	JP
2002-506514	Feb 2002	JP
2002-131105	May 2002	JP
2003-038642	Feb 2003	JP
2003-050144	Feb 2003	JP
2005-021463	Jan 2005	JP
2005-524081	Mar 2005	JP
2006-517423	Jul 2006	JP
2007-071695	Mar 2007	JP
2007-518471	Jul 2007	JP
2007-520270	Jul 2007	JP
2007-275106	Oct 2007	JP
2008-249400	Oct 2008	JP
4322661	Jun 2009	JP
2009-148592	Jul 2009	JP
2010-063767	Mar 2010	JP
5716879	Mar 2015	JP
WO 84000690	Mar 1984	WO
WO 84000894	Mar 1984	WO
WO 90007942	Jul 1990	WO
WO 91000113	Jan 1991	WO
WO 91016087	Oct 1991	WO
WO 91016416	Oct 1991	WO
WO 93004284	Mar 1993	WO
WO 95016200	Jun 1995	WO
WO 95031233	Nov 1995	WO
WO 96008755	Mar 1996	WO
WO 96025186	Aug 1996	WO
WO 96028209	Sep 1996	WO
WO 96041156	Dec 1996	WO
WO 97010013	Mar 1997	WO
WO 97030333	Aug 1997	WO
WO 98004304	Feb 1998	WO
WO 98012670	Mar 1998	WO
WO 98014234	Apr 1998	WO
WO 98019263	May 1998	WO
WO 98044320	Oct 1998	WO
WO 98056441	Dec 1998	WO
WO 99015216	Apr 1999	WO
WO 99051003	Oct 1999	WO
WO 99052575	Oct 1999	WO
WO 00013580	Mar 2000	WO
WO 00013726	Mar 2000	WO
WO 00041621	Jul 2000	WO
WO 01014974	Mar 2001	WO
WO 01033484	May 2001	WO
WO 02005702	Jan 2002	WO
WO 02009795	Feb 2002	WO
WO 02027276	Apr 2002	WO
WO 02066101	Aug 2002	WO
WO 02087664	Nov 2002	WO
WO 03006091	Jan 2003	WO
WO 03053498	Jul 2003	WO
WO 03093780	Nov 2003	WO
WO 2004035115	Apr 2004	WO
WO 2004060455	Jul 2004	WO
WO 2004070556	Aug 2004	WO
WO 2004070994	Aug 2004	WO
WO 2004112579	Dec 2004	WO
WO 2005018716	Mar 2005	WO
WO 2005030489	Apr 2005	WO
WO 2005036447	Apr 2005	WO
WO 2005050526	Jun 2005	WO
WO 2005057175	Jun 2005	WO
WO 2005065146	Jul 2005	WO
WO 2005065749	Jul 2005	WO
WO 2005082450	Sep 2005	WO
WO 2005118015	Dec 2005	WO
WO 2006016122	Feb 2006	WO
WO 2006022906	Mar 2006	WO
WO 2007000426	Jan 2007	WO
WO 2007033025	Mar 2007	WO
WO 2007035567	Mar 2007	WO
WO 2007087443	Aug 2007	WO
WO 2008004560	Jan 2008	WO
WO 2008019016	Feb 2008	WO
WO 2008053193	May 2008	WO
WO 2008059492	May 2008	WO
WO 2008063429	May 2008	WO
WO 2008067245	Jun 2008	WO
WO 2008088490	Jul 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 2009039203	Mar 2009	WO
WO 2009039214	Mar 2009	WO
WO 2009049252	Apr 2009	WO
WO 2009127683	Oct 2009	WO
WO 2009141504	Nov 2009	WO
WO 2010017279	Feb 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 2010135646	Nov 2010	WO
WO 2010135654	Nov 2010	WO
WO 2010135670	Nov 2010	WO
WO 2010135686	Nov 2010	WO
WO 2010148205	Dec 2010	WO
WO 2011017778	Feb 2011	WO
WO 2011080188	Jul 2011	WO
WO 2011109774	Sep 2011	WO
WO 2012042763	Apr 2012	WO
WO 2012082599	Jun 2012	WO
WO 2012108910	Aug 2012	WO
WO 2012167090	Dec 2012	WO
WO 2013036854	Mar 2013	WO
WO 2013096769	Jun 2013	WO
WO 2015134478	Sep 2015	WO
WO 2017051271	Mar 2017	WO
WO 2017144366	Aug 2017	WO
WO 2017197024	Nov 2017	WO
WO 2017214441	Dec 2017	WO
WO 2019092680	May 2019	WO
WO 2020214717	Oct 2020	WO
WO 2021113259	Jun 2021	WO
WO 2022020184	Jan 2022	WO
WO 2022125471	Jun 2022	WO
WO 2023064662	Apr 2023	WO

Non-Patent Literature Citations (60)

Entry
Alaedeen et al., “Total Parenteral Nutrition-Associated Hyperglycemia Correlates with Prolonged Mechanical Ventilation and Hospital Stay in Septic Infants”, Journal of Pediatric Surgery, Jan. 2006, vol. 41, No. 1, pp. 239-244.
ALARIS® Medical Systems, “Signature Edition® GOLD—Single & Dual Channel Infusion System”, San Diego, CA, USA, date unknown, but believed to be at least as early as Nov. 29, 2008, pp. 2-88 & 2-91.
Allegro, “3955—Full-Bridge PWM Microstepping Motor Drive”, Datasheet, 1997, pp. 16.
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.
Baxter, “Baxter Receives 510(k) Clearance for Next-Generation SIGMA Spectrum Infusion Pump with Master Drug Library” Press Release, May 8, 2014, pp. 2. <http://web.archive.org/web/20160403140025/http://www.baxter.com/news-media/newsroom/press-releases/2014/05_08_14_sigma.page>.
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.
Binder et al., “Insulin Infusion with Parenteral Nutrition in Extremely Low Birth Weight Infants with Hyperglycemia”, Journal of Pediatrics, Feb. 1989, vol. 114, No. 2, pp. 273-280.
Bode et al., “Intravenous Insulin Infusion Therapy: Indications, Methods, and Transition to Subcutaneous Insulin Therapy”, Endocrine Practice, Mar./Apr. 2004, vol. 10, Supplement 2, pp. 71-80.
Buhrdorf et al., “Capacitive Micromachined Ultrasonic Transducers and their Application”, Proceedings of the IEEE Ultrasonics Symposium, Feb. 2001, vol. 2, pp. 933-940.
Cannon, MD et al., “Automated Heparin-Delivery System to Control Activated Partial Thromboplastin Time”, Circulation, Feb. 16, 1999, vol. 99, pp. 751-756.
“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.
Cheung et al., “Hyperglycemia is Associated with Adverse Outcomes in Patients Receiving Total Parenteral Nutrition”, Diabetes Care, Oct. 2005, vol. 28, No. 10, pp. 2367-2371.
Coley et al., “Performance of Three Portable Infusion-Pump Devices Set to Deliver 2 mL/hr”, American Journal of Health-System Pharmacy, Jun. 1, 1997, vol. 54, No. 11, pp. 1277-1280.
“Continually vs Continuously”, <https://web.archive.org/web/20090813092423/http://www.diffen.com/difference/Continually_vs_Continuously>, as accessed Aug. 13, 2009 in 4 pages.
“CritiCore® Monitor: Critical Fluid Output and Core Bladder Temperature Monitor”, BARD Urological Catheter Systems, Advertisement, 2005, pp. 2.
Daimiwal et al., “Wireless Transfusion Supervision and Analysis Using Embedded System”, IEEE, 2010 International Conference ICBBT, China, Apr. 2010, pp. 56-60.
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.
“Decision of the Administrative Council of Oct. 16, 2013 Amending Rule 135 and 164 of the Implementing Regulations to the European Patent Convention (CA/D 17/13)”, Official Journal EPO Nov. 2013, Nov. 2013, pp. 503-506. <http://archive.epo.org/epo/pubs/oj013/11_13/11_5033.pdf>.
“Decision of the Administrative Council of Oct. 27, 2009 Amending the Implementing Regulations to the European Patent Convention (CA/D 20/09)”, Official Journal EPO Dec. 2009, Dec. 2009, pp. 582-584. <http://archive.epo.org/epo/pubs/oj009/12_09/12_5829.pdf>.
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.
“Differential Pressure Transmitter, Series PD-39 X”, SensorsOne Ltd., Advertisement, Dec. 2005, pp. 2.
Dunster et al., “Flow Continuity of Infusion Systems at Low Flow Rates”, Anaesthesia and Intensive Care, Oct. 1995, vol. 23, No. 5, pp. 5.
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.
“Froth”, <http://www.merriam-webster.com/dictionary/froth>, as accessed May 13, 2015 in 1 page.
Goldberg et al., “Clinical Results of an Updated Insulin Infusion Protocol in Critically Ill Patients”, Diabetes Spectrum, 2005, vol. 18, No. 3, pp. 188-191.
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.
Hospira, “Plum A+™ Infusion System” as archived Dec. 1, 2012, pp. 2. <www.hospira.com/products_and_services/infusion_pumps/plum/index>.
Hospira, “Plum XL™ Series Infusion System” Technical Service Manual, Feb. 2005, Lake Forest, Illinois, USA, pp. i-vii, 5-14, 8-3.
Ilfeld et al., “Delivery Rate Accuracy of Portable, Bolus-Capable Infusion Pumps Used for Patient-Controlled Continuous Regional Analgesia”, Regional Anesthesia and Pain Medicine, Jan.-Feb. 2003, vol. 28, No. 1, pp. 17-23.
Ilfeld et al., “Portable Infusion Pumps Used for Continuous Regional Analgesia: Delivery Rate Accuracy and Consistency”, Regional Anesthesia and Pain Medicine, Sep.-Oct. 2003, vol. 28, No. 5, pp. 424-432.
International Search Report and Written Opinion received in PCT Application No. PCT Application No. PCT/US2018/066913, dated Mar. 8, 2019 in 15 pages.
JMS Co., Ltd., “Infusion Pump: OT-701”, Tokyo, Japan, 2002, pp. 4.
Kim, M.D., et al., “Hyperglycemia Control of the Nil Per Os Patient in the Intensive Care Unit: Introduction of a Simple Subcutaneous Insulin Algorithm”, Nov. 2012, Journal of Diabetes Science and Technology, vol. 6, No. 6, pp. 1413-1419.
Kutcher et al., “The Effect of Lighting Conditions on Caries Interpretation with a Laptop Computer in a Clinical Setting”, Elsevier, Oct. 2006, vol. 102, No. 4, pp. 537-543.
Lamsdale et al., “A Usability Evaluation of an Infusion Pump by Nurses Using a Patient Simulator”, Proceedings of the Human Factors and Ergonomics Society 49th Annual Meeting, Sep. 2005, pp. 1024-1028.
Logan et al., “Fabricating Capacitive Micromachined Ultrasonic Transducers with a Novel Silicon-Nitride-Based Wafer Bonding Process”, IEEE Transactions on Ultrasonics, Ferroelectrics, and Frequency Control, May 2009, vol. 56, No. 5, pp. 1074-1084.
Magaji et al., “Inpatient Management of Hyperglycemia and Diabetes”, Clinical Diabetes, 2011, vol. 29, No. 1, pp. 3-9.
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.
Maynard et al., “Subcutaneous Insulin Order Sets and Protocols: Effective Design and Implementation Strategies”, Journal of Hospital Medicine, Sep./Oct. 2008, vol. 3, Issue 5, Supplement 5, pp. S29-S41.
Merry et al., “A New, Safety-Oriented, Integrated Drug Administration and Automated Anesthesia Record System”, Anesthesia & Analgesia, Aug. 2001, vol. 93, No. 2 pp. 385-390.
Microchip Technology Inc., “MTA11200B; TrueGauge™ Intelligent Battery Management I.C.”, <https://www.elektronik.ropla.eu/pdf/stock/mcp/mta11200b.pdf>, 1995, pp. 44.
Moghissi, Etie, MD, FACP, FACE, “Hyperglycemia in Hospitalized Patients”, A Supplement to ACP Hospitalist, Jun. 15, 2008, pp. 32.
Nuckols et al., “Programmable Infusion Pumps in ICUs: An Analysis of Corresponding Adverse Drug Events”, Journal of General Internal Medicine, 2007, vol. 23, Supp. 1, pp. 41-45.
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.
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.
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.
SGS-Thomson Microelectronics, “L6219—Stepper Motor Drive”, Datasheet, Dec. 1996, pp. 10.
SGS-Thomson Microelectronics, “PBL3717A—Stepper Motor Drive”, Datasheet, Apr. 1993, pp. 11.
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.
Smith, Joe, “Infusion Pump Informatics”, CatalyzeCare: Transforming Healthcare, as printed May 12, 2011, pp. 2.
Tang et al., “Linear Dimensionality Reduction Using Relevance Weighted LDA”, Pattern Recognition, 2005, vol. 38, pp. 485-493, <http://staff.ustc.edu.cn/˜ketang/papers/TangSuganYaoQin_PR04.pdf>.
Thomas et al., “Implementation of a Tight Glycaemic Control Protocol Using a Web-Based Insulin Dose Calculator”, Anaesthesia, 2005, vol. 60, pp. 1093-1100.
Van Den Berghe, M.D., Ph.D., et al., “Intensive Insulin Therapy in Critically Ill 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.
Westbrook et al., “Errors in the Administration of Intravenous Medications in Hospital and the Role of Correct Procedures and Nurse Experience”, BMJ Quality & Safety, 2011, vol. 20, pp. 1027-1034.
Zakariah et al., “Combination of Biphasic Transmittance Waveform with Blood Procalcitonin Levels for Diagnosis of Sepsis in Acutely Ill Patients”, Critical Care Medicine, 2008, vol. 36, No. 5, pp. 1507-1512.
International Preliminary Report on Patentability and Written Opinion received in PCT Application No. PCT/US2018/066913, dated Jul. 9, 2020 in 8 pages.
Abbott Laboratories, “LifeCare® 5000, Plum®: Concurrent Flow Infusion System with DataPort™”, System Operating Manual, Version 1.6, Jul. 1998, pp. 76.

Related Publications (1)

	Number	Date	Country
	20210397396 A1	Dec 2021	US

Provisional Applications (1)

	Number	Date	Country
	62610742	Dec 2017	US

Continuations (5)

	Number	Date	Country
Parent	16848649	Apr 2020	US
Child	17302501		US
Parent	16058799	Aug 2018	US
Child	16848649		US
Parent	17302501		US
Child	16848649		US
Parent	16058799	Aug 2018	US
Child	17302501		US
Parent	15861204	Jan 2018	US
Child	16058799		US

Synchronized display of screen content on networked devices

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Term Extension

Abstract