Intelligent medical escalation process

Description

INCORPORATION BY REFERENCE TO ANY RELATED APPLICATIONS

Any and all applications, if any, for which a foreign or domestic priority claim is identified in the Application Data Sheet of the present application are hereby incorporated by reference under 37 CFR 1.57.

BACKGROUND

Hospitals, nursing homes, and other patient care facilities typically include patient monitoring devices at one or more bedsides in the facility. Patient monitoring devices generally include sensors, processing equipment, and displays for obtaining and analyzing a medical patient's physiological parameters. Physiological parameters include, for example, respiratory rate, SpO₂level, pulse, and blood pressure, among others. Clinicians, including doctors, nurses, and certain other medical personnel use the physiological parameters obtained from the medical patient to diagnose illnesses and to prescribe treatments. Clinicians also use the physiological parameters to monitor a patient during various clinical situations to determine whether to increase the level of medical care given to the patient.

Patient monitors capable of measuring pulse oximetry parameters, such as SpO₂and pulse rate in addition to advanced parameters, such as HbCO, HbMet and total hemoglobin (Hbt) and corresponding multiple wavelength optical sensors are described in at least U.S. patent application Ser. No. 11/367,013, filed Mar. 1, 2006 and entitled Multiple Wavelength Sensor Emitters and U.S. patent application Ser. No. 11/366,208, filed Mar. 1, 2006 and entitled Noninvasive Multi-Parameter Patient Monitor, both assigned to Masimo Laboratories, Irvine, CA (Masimo Labs) and both incorporated by reference herein. Further, noninvasive blood parameter monitors and corresponding multiple wavelength optical sensors, such as Rainbow™ adhesive and reusable sensors and RAD-57™ and Radical-7™ monitors for measuring SpO₂, pulse rate, perfusion index, signal quality, HbCO and HbMet among other parameters are also available from Masimo Corporation, Irvine, CA (Masimo).

Advanced physiological monitoring systems may incorporate pulse oximetry in addition to advanced features for the calculation and display of other blood parameters, such as carboxyhemoglobin (HbCO), methemoglobin (HbMet) and total hemoglobin (Hbt or SpHb), as a few examples. Advanced physiological monitors and corresponding multiple wavelength optical sensors capable of measuring parameters in addition to SpO₂, such as HbCO, HbMet and Hbt are described in at least U.S. patent application Ser. No. 11/367,013, filed Mar. 1, 2006, titled Multiple Wavelength Sensor Emitters and U.S. patent application Ser. No. 11/366,208, filed Mar. 1, 2006, titled Noninvasive Multi-Parameter Patient Monitor, incorporated by reference herein. Further, noninvasive blood parameter monitors and corresponding multiple wavelength optical sensors, such as Rainbow™ adhesive and reusable sensors and RAD-57™ and Radical-7™ monitors for measuring SpO₂, pulse rate, perfusion index (PI), signal quality (SiQ), pulse variability index (PVI), HbCO and HbMet among other parameters are also available from Masimo.

SUMMARY

For purposes of summarizing the disclosure, certain aspects, advantages and novel features of several embodiments have been described herein. It is to be understood that not necessarily all such advantages can be achieved in accordance with any particular embodiment of the embodiments disclosed herein. Thus, the embodiments disclosed herein can be embodied or carried out in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other advantages as can be taught or suggested herein.

This disclosure describes embodiments of a medical network service that can replace or supplement some or all of an expensive internally staffed clinical facility network with a cloud-based networking service. The medical network service in certain embodiments can provide networking services via software as a service (SaaS) technologies, platform as a service (PaaS) technologies, and/or infrastructure as a service (IaaS) technologies. The medical network service can provide these services to large existing clinical facilities such as metropolitan hospitals as well as to smaller clinical facilities such as specialized surgical centers. The networking services provided by the medical network service can replace and/or supplement existing IT networks in hospitals and other clinical facilities and can therefore reduce costs and increase security and reliability of those networks. In addition, the medical network service can provide synergistic benefits that can improve patient outcomes and patient care.

In certain embodiments, a method of providing patient monitoring data over a network may include, by a medical edge router having one or more hardware processors, receiving input packets with the medical edge router, where the input packets include information related to patient monitoring data, analyzing the input packets to identify any patient monitoring alarms in the input packets, transmitting first ones of the input packets that do not correspond to a patient alarm over a first communications channel, and in response to detecting a patient monitoring alarm in second ones of the input packets, transmitting the second packets over multiple second communications channels.

In certain embodiments, a system for providing patient monitoring data over a network can include a medical edge router having one or more hardware processors. The medical edge router can include a traffic inspector that can receive input packets including information related to patient monitoring data and to analyze the input packets to identify any patient monitoring alarms in the input packets. Further, the medical edge router can include a routing module that can transmit first ones of the input packets that do not correspond to a patient alarm over a first communications channel and transmit second ones of the input packets over multiple second communications channels in response to detecting a patient monitoring alarm in the second input packets.

In certain embodiments, a method of providing patient monitoring data over a network can include, by a medical edge router having one or more hardware processors, receiving input data with the medical edge router. The input data can include information related to patient monitoring data. The method may also include attempting to transmit the input data over a first communications channel. Further, the method may include, in response to determining that the first communications channel is unavailable, attempting to transmit the input data over a second communications channel. Moreover, the method may include, in response to determining that the second communications channel is unavailable, transmitting a reduced form of the input data over a third communications channel.

In certain embodiments, a method of configuring a patient profile in a patient monitoring device can include, by a medical network service including one or more hardware processors, determining whether a patient admitted to a clinical facility is associated with an existing alarm settings profile stored with the medical network service. The method may also include, in response to determining that the patient is associated with the existing alarm settings profile, assigning the existing alarm settings profile to a monitoring device associated with the patient. Further, the method may also include, in response to determining that the patient is not associated with an existing alarm settings profile: identifying a matching alarm profile template that matches one or more attributes of the patient, and assigning the matching alarm profile template to the monitoring device.

The method of the preceding paragraph may include any combination of the following features. For instance, the method may further include obtaining the one or more attributes of the patient when the patient is admitted to the clinical facility. The one or more attributes of the patient can include one or more of the following attributes: age, gender, health condition, and medication associated with the patient. The identifying of the matching alarm profile template can include selecting a neonate alarm template in response to determining that the age of the patient corresponds to a neonate. The neonate alarm template can have different alarm settings than an adult alarm template. Further, the method may also include presenting the matching alarm profile template to a clinician for approval prior to assigning the matching alarm profile template to the monitoring device. The method may also include presenting the matching alarm profile template to a clinician for customization prior to assigning the matching alarm profile template to the monitoring device. The existing alarm settings profile may be generated at a second clinical facility different from the clinical facility and stored in computer storage for subsequent access.

In certain embodiments, a system for configuring a patient profile in a patient monitoring device can include a medical network service having one or more hardware processors. The medical network service can determine whether a patient admitted to a clinical facility is associated with an existing alarm settings profile stored with the medical network service. In response to determining that the patient is associated with the existing alarm settings profile, the medical network service can also assign the existing alarm settings profile to a monitoring device associated with the patient. In response to determining that the patient is not associated with an existing alarm settings profile, the medical network service can also identify a matching alarm profile template that matches one or more attributes of the patient and associating the matching alarm profile template with the patient.

The system of the preceding paragraph may include any combination of the following features. For instance, the medical network service may also obtain the one or more attributes of the patient when the patient is admitted to the clinical facility. The one or more attributes of the patient comprise one or more of the following attributes: age, gender, health condition, and medication associated with the patient. The medical network service can also identify the matching alarm profile template by at least selecting a neonate alarm template in response to determining that the age of the patient corresponds to a neonate. The neonate alarm template may have different alarm settings than an adult alarm template. The medical network service may also present the matching alarm profile template to a clinician for approval prior to associating the matching alarm profile template with the patient. The medical network service may also present the matching alarm profile template to a clinician for approval prior to associating the matching alarm profile template with the patient. The existing alarm settings profile may be generated at a second clinical facility different from the clinical facility and stored in computer storage for subsequent access.

BRIEF DESCRIPTION OF THE DRAWINGS

Throughout the drawings, reference numbers are re-used to indicate correspondence between referenced elements. The drawings are provided to illustrate embodiments of the inventions described herein and not to limit the scope thereof.

FIG. 1 depicts an embodiment of a computing environment in which various computing devices and patient monitoring devices can obtain network services from a medical network service.

FIG. 2 depicts a more detailed embodiment of the medical network service of FIG. 1.

FIG. 3 depicts an embodiment of a patient profile configuration process.

FIG. 4 depicts an embodiment of a device profile configuration process.

FIG. 5 depicts an example device configuration adjustment user interface.

FIG. 6 depicts an embodiment of a continuum of care process.

FIG. 7 depicts an embodiment of a situational alarm context process.

FIG. 8 depicts an embodiment of a situational escalation process.

FIG. 9 depicts another embodiment of a computing environment in which various computing devices and patient monitoring devices can obtain network services from a medical network service.

FIG. 10 depicts an embodiment of a medical edge router.

FIG. 11 depicts an embodiment of an edge router failover process.

FIG. 12 depicts an embodiment of an edge router alarm handling process.

DETAILED DESCRIPTION
I. Introduction

A trend in hospitals today is to move away from big box hospitals that provide all services typically provided by hospitals and to provide smaller community hospitals closer to people in suburban communities. The smaller community hospitals can be more specialized and may, for example, include surgical centers that specialize in a few types of surgery or even a single type of surgery. Smaller community hospitals can provide efficiency gains in time and healthcare costs by being closer to patients and by focusing on a few areas of specialties. However, a drawback from having such facilities is that these facilities tend not to have the same financial capability as larger hospital organizations and therefore tend not to be able to afford expensive information technology network infrastructure for communicating between patient monitoring devices and clinician devices. In addition, such facilities typically also may not have the resources to purchase an electronic medical records (EMR) system, paging systems, or other systems that can be useful in caring for patients.

Furthermore, such systems can be expense for large hospitals to maintain as well. Hospitals prefer to focus on caring for patients rather than managing information technology and hospital networks. However, due to the realities of modern medical practice, many large hospitals and other clinical facilities have entire information technology (IT) departments to deal with internal networking issues including, for example, server maintenance and wireless networking maintenance. Because hospitals have a core competency in providing care for patients, hospitals tend to hire qualified IT personnel to staff their IT departments. However, as hospitals tend to reduce costs to improve patient care while impacting patients less financially, there is a risk that hospitals may be forced to cut IT costs for their IT departments and, as a result, may unintentionally compromise security and ultimately patient safety due to lower reliability of hospital networks.

In addition, various embodiments of a medical edge router are described herein. The medical edge router can be an intelligent edge router or the like that provides redundant communications features for transmitting patient data to the medical network service.

II. Medical Network Service Embodiments

Turning to the Figures, FIG. 1 depicts an embodiment of a computing environment 100 in which various computing devices and patient monitoring devices can obtain network services from a medical network service 110. Various institutions 112, 114, 116 and devices 118, 120 are shown in the computing environment 100. These institutions include surgery centers/clinics/outpatient care centers (collectively referred to herein as small clinics 112), major hospitals 114, external entities such as government agencies 116. The example devices 118, 120 shown include home/mobile clinician devices 118, and home/mobile patient devices 120. The various institutions 112, 114, and 116 may each include internal networks of devices having computing devices and patient monitoring devices that communicate over networks 108 with the medical network service 110. The medical network service 110 can provide the users of the institutions 112, 114, and 116 with access to a variety of features that are typically included in an internal IT network installation at a hospital, some examples of which include electronic medical records or EMR, paging systems, wellness index computational services, and the like.

In addition, the MNS 110 can communicate with the home/mobile clinician devices 118 over a network 108 and the home mobile patient devices 120 of a network 108. The example networks 108 shown can be local area networks (LAN), wide area networks (WAN), the Internet, an intranet, combinations of the same or the like. Any type of clinician computing device 118 can communicate with the MNS 110 including, for example, laptops, desktops, servers, work stations, tablets, wireless handheld devices such as cell phones, smart phones, personal digital assistants and wireless pagers, combinations of the same or the like. Likewise, the MNS 110 can communicate with any type of patient monitoring device 120 including bedside devices, body worn devices, telemetry devices, and the like. Any of these patient devices 112 can output parameter data, trend data and/or alarms which can be provided to the MNS 110 over the network 108 and then re-routed by the MNS 110 to institutions 112, 114, or computers thereof, and mobile clinician devices 118.

Advantageously, in certain embodiments, by providing network services to the various entities shown, the MNS 110 can provide greater reliability, security and therefore patient safety compared to existing networks in hospitals and other clinical facilities. The MNS 110 may be implemented in one or more computing devices, such as servers, which may be geographically located, for example, in a data center, or which may be geographically disbursed, for example, in multiple data centers. The MNS 110 can include enterprise-class networking capabilities of any state of the art or currently available data center today including, for example, load balancing features, failover features, intelligent network problem detection and resolution features, and the like.

Thus for example, one benefit that the MNS 110 can provide in contrast with existing hospital networks is that if a switch or other network device were to fail at an existing hospital network, that network would then go down and deprive patients of necessary care. In contrast, in the MNS 110, if a component such as a switch goes down, the MNS 110 may be able to reroute network traffic through other switches and other components and continue or resume critical patient care services for the various institutions and devices shown.

Further, the MNS 110 can be configured such that service level agreements (SLAs) can be provided to institutions so that guarantees of service can be met by the MNS 110. An example SLA guarantee can be that alarms processed by the MNS 110 can be provided to clinician devices in the institutions 112, 114 within a specified period of time, such as a few seconds or the like. The MNS 110 may also provide uptime guarantees through SLAs or the like.

Moreover, by providing network services from the cloud, in certain embodiments, the MNS 110 can provide synergistic effects that are greater than the benefits of simply moving the networking services out of the hospital and into a centralized data center. Many examples of synergistic benefits are described in detail with respect to FIGS. 2-8 below. However, one example of a synergistic benefit of the MNS 110 in certain embodiments is that patient profiles from different institutions or clinical facilities can be maintained by the MNS 110 as a single patient profile. Thus, if a patient is in a first facility and has a profile that specifies alarm settings that are unique to that patient's health conditions, the MNS 110 can store these alarm settings in the patient's profile in the cloud. If this patient subsequently is admitted to a different facility, the MNS 110 can provide this second facility with access to the patient's profile, including the alarm settings that were previously set in the first facility. Patient profiles can enable clinicians to avoid having to re-establish useful alarm settings and/or other monitoring settings for the patient. Furthermore, the MNS 110 can enable these patient profiles to be updated and customized at the second facility.

In addition to these features, in certain embodiments any of the data collected by the MNS 110 can be anonymized and provided to the external entities 116 including, for example, government agencies or research institutions for demographic and healthcare research purposes, additional examples of which are described below with respect to FIG. 2.

Turning to FIG. 2, a more detailed embodiment of a medical network service (MNS) is shown, the MNS 210. The MNS 210 can have all of the features of the MNS 110 described above. In the depicted embodiment, the MNS has several subsystems or modules that can be implemented in hardware and/or software. The example modules or components shown group functionality of embodiments of the MNS 210 together under logical descriptions. It should be understood, however, that the various modules and systems shown in the MNS 210 or portions thereof could be implemented together in a single system. In addition, not all of the systems or modules shown need be implemented on the same computing device but could instead be implemented in separate computing devices.

The MNS 210 includes, for example, a network management module 202. The network management module 202 can manage network communications with other networks, including networks in hospitals and other facilities as well as communications with mobile patient devices and clinician devices. For example, the network management module 202 can communicate with devices in hospitals and outside of hospitals, or inside of facilities and outside of facilities. The network management module 202 can provide the networking services described above with respect to FIG. 1, such as load balancing, failover, and the like. In addition, if a patient is monitored in a facility that communicates with the network management module 202, and then the patient is discharged from the facility, the network management module 202 can maintain connectivity with a body-worn or other mobile medical device associated with the patient, for example, over cellular or Wi-Fi links. Additional example features of the network management module 202 are described below with respect to FIG. 6.

The MNS 210 also includes an EMR system 204 that can generally store patient data from any facility, including data collected from patient monitoring devices in patients' homes or while patients are mobile outside of their homes or out of facilities. For example, the EMR system 204 can include such information as parameter values, trend values, alarm histories, patient demographic data, patient condition data including diagnoses, patient medical histories, and patient medications, among a variety of other patient data. The data in the EMR 204 can advantageously be used by other components of the MNS 210 as described below to improve patient care.

A clinician portal 206 of the MNS 210 can provide a user interface or user interfaces that can be accessed by clinicians via their clinician devices to monitor the health status of their patients for whom they are responsible. The clinician portal 206 may, for example, be implemented in one or more web pages, mobile applications, or other network applications and may provide information about the wellness or relative wellness of each patient.

In one embodiment, a wellness score or index is computed for each patient by a risk analysis system 208 of the MNS 210, and the clinician portal 206 can depict these wellness indices among other parameter data, trend data and alarms for each patient. In one embodiment, the clinician portal 206 facilities triaging patients by providing functionality for patients to be ordered or ranked based on their wellness scores or indices as computed by the risk analysis system 208. Example features for computing wellness indices or risk assessments are described in Appendices IV and V. For example, the risk analysis system 208 can take into two or more parameters, such as any combination of the following parameters: oxygen saturation (e.g., SpO₂), respiratory rate, pulse rate, heart rate, total hemoglobin level, methemoglobin, carboxyemoglobin, blood pressure, ECG output, encephalography output, or the like. The risk analysis system 208 can combine data from such parameters and reduce this data to a single value or data representation of the combination of those parameters. The single value may be, for example, an index or score that is on a scale of 0 to 10, where 10 may represent a most healthy state, while 0 may represent a least healthy state. Thus, such scores could be used to rank the relative health state or acuity of patient sicknesses and such numerical rankings can be output for presentation to clinicians in the clinician portal 206, thereby enabling clinicians to quickly triage patients.

Advantageously, in certain embodiments, the risk analysis system 208 also leverages aspects of the cloud-based infrastructure of the MNS 210 to improve the wellness index calculation. For example, the risk analysis system 208 may be able to access patient profile data from the MNS 210 that comes from previous hospital visits or other clinical facility visits from a single facility or multiple facilities to compute historical wellness indices or to compute a current wellness index. The risk analysis system 208 can also personalize the wellness index based on patient attributes stored in the EMR system 204. For example, the risk analysis system 208 can personalize which parameters are weighted more heavily in the combination of parameters that are output as a wellness index based on previous patient conditions listed in EMR system 204. In currently available systems, different institutions typically do not share their EMR data, and EMRs therefore cannot be used to correlate patient data from multiple institutions together and thereby improve risk analysis and wellness indices. However, such advantages can be made possible in certain embodiments by the centralized cloud nature of the MNS 210.

The MNS 210 also includes a patient profile manager 211. The patient profile manager 211 can manage patient profiles, which can include information about patient demographics, patient alarm settings, including alarm settings from previous visits to potentially multiple different facilities, patient conditions and so forth, and example features of which are described in greater detail below with respect to FIG. 3. The MNS 210 further includes a device profile manager 212 that can manage and store device profiles for medical devices that interact with the MNS 210 as well as optionally other computing devices. The profiles may have information about rules that can be used to track the usage of these devices as well as a variety of other features, examples of which are described in greater detail below with respect to FIGS. 4 and 5.

The MNS 210 also includes an early warning system 216. The early warning system 216 can issue early warning alarms based on parameter measurements, indices such as the wellness index or other indices. The early warning system 216 can look for patterns in patients to facilitate detecting never events, including events that should occur never or rarely, like a patient dying in bed without any intervention, particularly when a patient is home and would not ordinarily be under the care of a hospital or have access to a system like the risk analysis system 208 or the early warning system 216.

An escalation module 218 of the MNS 210 can provide functionality for escalating alarms from a first or primary care provider to a second or subsequent care provider in case the primary care provider is unavailable. However, the escalation module 218 may also provide additional functionality such as obtaining information from a remote primary care provider and providing this information to a secondary local care provider who is local to the patient and can therefore intervene using the information provided by the first care provider. Such embodiments are described below in greater detail with respect to FIG. 8.

An information exchange system 220 of the MNS 210 facilitates communicating information about patients to government or research institutions 118 described above with respect to FIG. 1. One scenario where patient information may be submitted (anonymously) to government or research institutions is where a disease outbreak has occurred. For example, information may be provided that indicates several patients in a hospital have come down with the flu. The information exchange system 220 can report this occurrence to an external entity such as the CDC or the Center for Disease Control, or state or local government agency or national government agency or worldwide agency to alert such agencies other institutions of the potentiality of a disease outbreak. If multiple institutions are using the services of the MNS 210, then such information about patient conditions can be correlated and provided to these institutions as described above. More generally, the information exchange system 220 can provide data about changing patient conditions continuously or periodically to government or research organizations to enable such organizations to rapidly respond to changes in regional health issues.

Further, the data provided by the information exchange system 220 can be valuable to government agencies or research institutions to determine the effects of local conditions on health conditions. It may be discovered, for instance, that patients that go to a specific facility or set of facilities in a region are afflicted with disease related to nearby coal mining which can be ascertained by research institution or a government agency that has responsibility over such activities. Accordingly, the information exchange system 220 can provide value data that can provide reports that can be used by external entities to improve patient care.

A journaling module 222 of the MNS 210 can capture clinician interactions with medical devices that are in the institutions and/or that are in patients' homes or that are body worn in mobile situations. The interactions can include any type of button press, alarm setting change, RFID tag interaction, or the like and can be recorded for the purposes of determining clinician response times to alarms or other measures of the quality of a clinician's care. The journaling module 222 can further leverage the centralized monitoring capabilities of the MNS 210 to compare the quality of care as journaled or otherwise calculated amongst different institutions as an apples-to-apples comparison because some or all of the data from these institutions can be provided to the centralized MNS 210.

Further, the journal module 222 can facilitate comparing the quality of care between different units in a hospital or other facility including different floors or groups of clinicians or shifts, or the like. The journal module 222 can also facilitate comparing similar groups amongst different facilities, such as an ICU group in two different facilities, and can thereby enable an organization to identify gaps or deficiencies of care in different facilities that can be corrected. This information can be provided in real time or near-real time so that adverse patient care outcomes can be quickly addressed, in contrast to the past where information about quality of care is often analyzed well after an adverse care event has occurred (or even after a patient has been discharged). Further embodiments of journaling and detecting clinician interactions with devices (including via RFID tags) are described in greater detail in Appendices I through III.

A telemedicine module 224 of the MNS 210 can facilitate telecommunications between clinicians and patients, including telepresence communications where clinicians can diagnosis, treat, or otherwise attend to the needs of patients remotely using audio visual systems or the like. The telemedicine module 224 can also be used in conjunction with features of the escalation module 218 described below with respect to FIG. 8.

FIG. 3 depicts an embodiment of a patient profile configuration process 300. The patient profile configuration process 300 can be implemented by any of the medical network services described above, including the MNS 110 or 210. In addition, portions of the process 300 can be implemented by other devices in any of the institutions described above, or any of the medical devices or clinician devices described above. Thus the processing of the process 300 can be distributed amongst different devices. However, although different devices including devices other than those shown or described herein could implement the process 300, for convenience certain aspects of the process 300 are described as being implemented by the patient profile manager 211 of FIG. 2. Advantageously, in certain embodiments the patient profile configuration process 300 can facilitate improved monitoring of patients by maintaining patient profiles from visit to visit, a particular institution and/or from visit to visit amongst multiple institutions.

The process 300 begins at block 302 where a patient is admitted to a hospital. In the admission process, the patient may provide demographic information to the hospital, including the gender, age, weight, other health conditions that the patient has, medications that the patient is on and so forth. This information can be stored in the EMR described above with respect to FIG. 2. In another embodiment, when a patient is admitted, the patient provides insurance information or other identifying information that uniquely identifies the patient and thereby enables the patient profile manager 211 to look up the patient's profiled date stored in the MNS 210.

At block 304, the patient is assigned a monitoring device. The monitoring device may be a bedside device or a body worn device and could be used in an institution such as a hospital or at the patient's home or while the patient is mobile. At block 306 the patient profile manager 211 determines whether the patient has existing alarm settings profile in the MNS 210. An existing alarm settings profile may include customized alarm settings based on the demographics of the patient. Different types of patients may benefit better from different alarm settings. For instance, neonates or children may require different alarm settings from adults because their physiology differs from adults. Likewise, alarm settings can be based on gender, race due to physiological differences among races (however slight), as well as due to age and previous medical conditions or medications that a person is on or symptoms that the patient is reporting when admitted to the hospital.

If the patient has an existing alarm settings profile in the MNS, then the patient profile manager 211 transmits, uploads, or otherwise downloads the existing alarm settings profile to the monitoring device associated with the patient at block 308. Thus, it can be seen that an advantage in certain embodiments of the patient profile manager 211 is that the existing profile can be stored in the cloud and therefore accessed whenever that patient is readmitted to a hospital or other clinical facility. However, if the patient does not have an existing alarm profile, at block 310 the patient profile manager 211 can identify an alarm profile template that matches attributes of the patient, including any of the demographic attributes described above. So, for example, if the patient is a neonate, the patient profile manager 211 can access the stored template of alarm settings for neonate.

At block 312, the patient profile manager 211 outputs an option to use the alarm profile template to a clinician. The clinician can then decide whether to use that particular template, select a different template, or customize the template to meet the needs of the particular patient. Thus, continuing at decision block 314, the patient profile manager 211 determines whether the clinician accepts the template. If so, the patient profile manager 211 transmits, uploads, or otherwise downloads the alarm profile template to the monitoring device and provides options for the clinician to modify the template at block 318. Block 318 may also be reached after block 308 where the existing alarm settings profile is downloaded to the monitoring device. However, if the clinician does not accept the template 314 as described above, at block 320 the patient profile manager 211 can provide options for the clinician to manually adjust alarm settings or to select another template.

In alternative embodiments, instead of downloading or transmitting patient profiles to devices, each device may already have several patient profiles already installed, and the patient profile module 211 selects one and assigns it to the device for the particular patient.

FIG. 4 depicts an embodiment of a device profile configuration process 400. Like the process 300, the process 400 can be implemented by any of the MNSs as described above including the MNS 110 or 210, or any of the other devices described herein. In an embodiment the device profile configuration process 400 is implemented by the device profile manager 212 of FIG. 2. Accordingly, for ease of illustration the process 400 will be described as being implemented by the device profile manager 212 although it should be understood that any other device or system could implement the process 400. The process 400 can advantageously provide centralized management of patient monitoring devices by the MNS.

At block 402, the device profile manager 212 outputs a device configuration adjustment user interface. An example of such a user interface is shown in FIG. 5 and described in greater detail below. Generally speaking, the device configuration adjustment user interface can provide functionality for a user, such as a network professional, to monitor the configuration status of monitoring devices and/or adjust configuration status of such devices. Devices may have profiles associated with them that include information about alarm settings and other settings. Profiles can be patient profiles that are associated with devices, clinician profiles that are associated with devices and so forth. In addition, the user interface can enable users to update software on the monitoring devices.

At block 404, the device profile manager 212 receives a user selection of a patient monitoring device or other device in the network from the user interface. The user may select any device shown in the user interface to obtain more data about that device, e.g., to change settings on the device or to set policies or rules for the device. At block 406, the device profile manager 212 receives user updates to the device settings and pushes those updated device settings to the devices over the network at block 408.

Turning to FIG. 5, an example of a device configuration adjustment user interface 500 is shown. The example user interface 500 could be output by the device profile manager 212 according to the process 400. The user interface 500 can be implemented in a web browser or other application software that may or may not be implemented in a web browser.

The user interface 500 includes a device explorer 510, device configuration pane 520, and a current measurements pane 530. The device explorer 510 includes a tree 512 or hierarchy of facilities and devices, enabling users to select a facility, explore floors or subsections of that facility, and select devices within those floors or subsections. In the depicted embodiment, the tree 512 shown includes data representing a hospital that has an operating room floor, an intensive care unit (ICU) floor, and a general floor. The operating room floor option is expanded to show devices within the operating room floor. One of the devices 514 is shown selected by a user (e.g., using a mouse or touch screen input).

Advantageously, in certain embodiments, the user interface 500 can provide access to any device that connects to the MNS. Thus, network administrators can drill down into any device among several different facilities. In addition to a tree view, in some embodiments, other views of the devices can be shown, such as a topology view that shows interconnections between devices in the network.

Upon user selection of one of the devices 514, the device profile manager 212 can output details 522 of the device 514 in the device configuration pane 520. These details 522 include configuration settings about the device and possibly other information stored on the device, including patient profiles, device profiles, policies, what network the device is connected to (not shown), and optionally applications installed on the device and settings thereof (not shown). These details 522 can be selected by a user to adjust the configuration settings of the selected device 512. For example, a user can select specific patient profiles to add or remove to the device.

In one embodiment, each device can have one or more profiles. In one embodiment, each device has a single device profile that specifies where in the facility the devices belongs (such as what floor), what network the device is connected to, and so forth. Policies can also be associated with a device and may be part of a device's profile. Policies can include rules about how a device may be used and may be defined by users (including clinicians and/or network technicians or the manufacturer of the device). For example, a policy may be defined that states that a device is to be used for general floor monitoring and not intensive care or operating room monitoring. Accordingly, if a clinician attempts to associate the device with a patient in the ICU or operating room floor, software in the device (or in the MNS) can detect that the device is being used on the wrong floor and therefore may prevent operation of the device or issue an audio/visual warning to not use the device. The device or MNS can detect that the device is on the wrong floor, for instance, by analyzing network traffic to and from the device to determine where in the network the device is connected.

Another example of a policy is related to patient profiles. A user can define a policy that the device may be used only with neonates or only with adults. In another example scenario, a user can define a policy that the device will issue a warning if a user changes alarm limits on the device or changes alarm limits beyond certain thresholds. Another policy could be defined to state that alarm thresholds cannot be changed on the device unless the device is associated with an existing patient profile. Software on the device and/or the MNS can enforce the policies by warning users of violations and/or preventing operation of the device until the policies are complied with. Accordingly, the policies used in devices can improve patient care outcomes.

Advantageously, in certain embodiments, because the MNS may be implemented in a centralized cloud architecture, the user interface 500 can enable policies, profiles, and settings to be adjusted for a plurality of devices at once instead of one at a time. As a result, network and device maintenance can be streamlined. Likewise, the user interface 500 can facilitate pushing software updates to multiple of the devices at once. Example user interface controls 524 are shown, which are buttons in the depicted embodiment, for adding new profiles, policies, and updating devices.

Moreover, the device profile manager 212 can detect problems occurring in different devices and report these problems or a representation thereof on the user interface 500. In the depicted embodiment, a device health indicator 542 is shown that can reflect the health of a device on the network. The device health indicator 542 can be a light or graphic that is green, yellow, or red depending on whether a device is functioning well, functioning poorly, or not functioning at all. Other indicators may be used than a colored light, such as text, a graph, a number, 1-5 star ratings, or any combinations of the same or the like. The device profile manager 212 can score devices based on device performance and adjust the output of the indicator 542 accordingly. Instead of a separate indicator, a graphic for each device in the device explorer 510 could instead show colors for each device, corresponding to the health of each device.

The current measurements pane 530 depicts current measurements on the selected device 514 and is optional in some embodiments. A trend view button 532 can allow a user to see trends on these measurements. Like the device health indicator 542, a patient health indicator 544 is also shown that may have some or all of the same functionality as the device health indicator 542 except with respect to a patient. The patient health indicator 544 can also be displayed on a medical device associated with the patient, a clinician device remote from the medical device, or a nurse's workstation, to name a few examples. The patient health indicator 544 can reflect an overall health or wellness of the patient and may be based on the wellness index described above. In other embodiments, the patient health indicator 544 can include or be the wellness index.

FIG. 6 depicts an embodiment of a continuum of care process 600. Like the process 300, the process 600 can be implemented by the MNS 110 or 210, or any of the other devices described herein. In an embodiment, the process 600 can be implemented at least in part by the network management module 202 to facilitate continued patient monitoring when a patient leaves a hospital or other facility.

At block 602, the network management module 202 receives monitoring data of a patient at the MNS via WiFi, LAN, or other networking technologies of the clinical facility to which the patient is admitted. Once the patient is discharged, the patient may be outfitted with a wearable home monitoring device 604. The wearable monitoring device may be the same device used to monitor the patient in the clinical facility. In addition, the device may be a mobile device that need not be wearable in some embodiments. The device may, for instance, be any of the devices or variations thereof described in U.S. patent application Ser. No. 13/010,653, filed Jan. 20, 2011, titled “Wireless Patient Monitoring System,” the disclosure of which is hereby incorporated by reference in its entirety.

When a patient is discharged, the patient typically leaves the hospital network. Accordingly, in currently-available systems, there is a typically a period of time where the patient is not being monitored once the patient leaves the facility. However, the network management module 212 can facilitate continued monitoring of the patient by receiving monitoring data from the patient via a cellular or satellite network at block 606. Then, if an alarm condition is detected at block 608, the network management module 212 (or the early warning system 216 using the network management module 212) can pass a notification from the MNS to a care provider 610. Accordingly, the MNS can facilitate a continuum of care for a patient and continuous monitoring even when a patient has left a clinical facility.

FIG. 7 depicts an embodiment of a situational alarm context process 700. Like the process 300, the process 700 can be implemented by the MNS 110 or 210, or any of the other devices described herein. In an embodiment, the situational alarm context process 700 is implemented by the risk analysis system 218. The situational alarm context process 700 can take into account more than just the measured parameters of a patient when determining whether to alarm. The process 700 can also take into account the situational context of the patient, such as whether the patient is moving.

At block 702, the risk analysis system 718 receives parameter data from the patient monitor while the patient is in bed. When the patient is in bed, the patient is typically resting and may have a lower heart rate than when the patient is moving, all other factors being equal. However, when the patient moves, the patient's heart rate may elevate, and other parameters associated with the patient may change as well. It can be desirable to adjust patient monitoring to account for patient changes in movement or other situational context to avoid producing false alarms.

Thus, the location and/or motion of the patient are monitored at block 704. The location and/or motion of the patient may be monitored in several ways. One or more motion sensors may be included in the patient monitoring device, and the monitoring device may be worn on the patient. Thus, for example, the monitoring device may include a gyroscope, accelerometer, or the like that can determine whether the patient is moving, walking, or the like. Telemetry can also be used to ascertain where a patient is located and/or moving to. For instance, when a patient is wearing a patient monitor that communicates over wireless networks, the MNS can determine the patient's position by triangulation of nearby access points to which the patient's monitoring device is sending and receiving signals. In other situations, patients may take an assisted walk with a nurse or other clinician. The nurse or other clinician may have an RFID tag or the like that can be detected by the patient monitoring device (as described in Appendix III), giving a clue as to the movement and/or location of the patient.

Thus, the risk analysis system 218 determines at block 706 whether the patient is ambulatory or moving. If so, the risk analysis system 218 can adjust alarm settings for the patient due to the patient being ambulatory. For example, the risk analysis system 218 can increase a heart rate threshold limit that would trigger an alarm if it detects that the patient is ambulatory. If the patient is not ambulatory, the process loops back to block 704, where the patient is continued being monitored using existing alarm settings.

In other embodiments, the risk analysis system 218 may adjust patient monitoring differently. Instead of adjusting alarm settings, for example, the risk analysis module 218 can assign scores to patients based on their activity level and incorporate these scores into the wellness index described above. For instance, if the patient is walking, the risk analysis module 218 may lower the weight given to heart rate in calculating the wellness index so as to avoid an increased heart rate adversely impacting the wellness index calculation. The risk analysis module 218 can also take into account additional factors before determining whether to adjust the weight applied to the heart rate, however, such as the health conditions or diseases of the patient. If the patient has heart disease or some other condition, it may be prudent to alarm or indicate an adverse health condition whenever the patient's heart rate rises, no matter the activity level of the patient. Thus, the risk analysis module 218 may use the health condition of the patient to override other considerations such as patient movement.

FIG. 8 depicts an embodiment of a situational escalation process 800. Like the process 300, the process 800 can be implemented by the MNS 110 or 210, or any of the other devices described herein. As described above, alarms may be escalated from a primary provider (or group of providers) to a secondary provider (or group of providers) if the primary provider is unavailable to address an alarm. In an embodiment, the process 800 is implemented by the escalation module 218 and enables clinicians to remotely provide information useful to a secondary provider to whom an alarm is escalated.

At block 802, an alarm generated by a monitoring device is received by the escalation module 218. The escalation module 218 identifies a primary provider to be contacted by the alarm at block 804. The escalation module 218 may store a list of providers that are associated with a patient and may provide a user interface that enables users to adjust this list in certain embodiments. At block 806, the escalation module 218 determines the primary care provider's situational context. If the situational context of the primary care provider is that the provider is located far from the patient, the escalation module 218 may perform intelligent escalation as described below.

The situation where the primary provider is far removed from the patient may occur increasingly more commonly. In particular, as smaller clinics replace some functionality of larger hospitals, clinicians may not all be co-located in the same hospital. Further, modern travel conveniences make it possible for surgeons and other specialists to travel to patient sites and vice versa to perform patient care. Accordingly, a primary provider may be distant from several of his or her patients.

The escalation module 218 determines at block 808 whether the primary care provider is located remotely from the patient. If not, the escalation module 218 further determines at block 810 whether the primary care provider is available. The primary care provider may be off duty or unable to take a page, for example, in which case the escalation module 218 escalates the alarm to a secondary provider at block 814. Otherwise, the escalation module 218 can provide the alarm and optionally data from the monitoring device (such as trend data) the primary provider for possible in-person intervention at block 812.

However, in the scenario where the primary care provider is not located close by but may be available, the escalation module 218 can still provide the alarm and optionally data from the monitoring device to the primary provider for remote intervention at block 816. The primary provider may use telepresence technologies to interact with the patient, e.g., using the telemedicine module 224 of the MNS 210. The escalation module 218 can then receive instructions from the primary provider regarding an alarm response at block 818, e.g., through a user interface or telepresence technology. These instructions can include a diagnosis, recommended medication, or other recommended course of actions that the escalation module 218 can relay to the secondary provider along with the alarm at block 820.

Thus, in certain embodiments, the process 800 enables a remote primary care provider to provide instructions to a secondary, local care provider to better enable the secondary care provider to respond to an alarm. This process 800 can therefore improve upon currently-available processes, which typically require the secondary provider (who may be less familiar with the patient than the primary provider) to interpret the patient's alarm without guidance from the remote primary care provider.

III. Additional Medical Network Service Embodiments

In addition to the embodiments described above, in certain embodiments, clinician devices (including mobile devices) can interact with the MNS and/or with the patient monitoring devices directly. A clinician's mobile device, for instance, can receive alarms, trend data, parameter data, or any other data associated with a patient from the MNS or directly from the patient monitoring devices. The clinician's device may also receive data from multiple patients that are associated with the clinician, including features of the clinician portal described above. Thus, for example, the clinician's device may depict wellness indices for the various patients and thereby enable the clinician to triage alarms. The clinician device can also include the capability to silence alarms remotely (e.g., by transmitting an instruction input by the clinician to the patient monitoring device). In an embodiment, the clinician device communicates directly with the patient monitoring device using Bluetooth (e.g., if in the same room or nearby) or WiFi or another wireless technology. In another embodiment, the clinician device communicates with the patient monitoring device through MNS if the clinician (or the clinician's organization) is affiliated with the MNS (e.g., is a paying customer) but otherwise directly communicates with the patient monitoring device. In the scenario where the clinician is affiliated with the MNS, the clinician may be able to advantageously obtain trend data for a plurality of patients, whereas directly connecting to each patient device individually may or may not provide this functionality.

Further, in certain embodiments, each patient device includes a network communications module that enables the patient device to communicate with the MNS over a network. In anther embodiment, a gateway device (not shown) is provided in each room of a facility, or in a few rooms of a facility, which connects to the patient device and which communicates with a plurality of devices in the room or rooms. The gateway device may itself be a patient monitor that includes ports for connecting to other devices. The gateway device can receive data from these other medical devices and pass the data on to the MNS for storage in the EMR, analysis by the risk analysis module 218, and the like. Some examples of other devices in a typical clinical facility that can connect through the gateway device include ventilators, pumps, general oxygen equipment, and the like. An example gateway device that may be used with the features described herein is described in U.S. application Ser. No. 13/651,167, filed Oct. 12, 2012, titled “Medical Monitoring Hub,” the disclosure of which is hereby incorporated by reference in its entirety.

Moreover, any of the features described herein can be implemented in conjunction with features from any of the following applications, the disclosure of each of which is hereby incorporated by reference in their entirety: U.S. application Ser. No. 11/633,656, filed Dec. 4, 2006, titled “Physiological Alarm Notification System”; U.S. application Ser. No. 12/904,925, filed Oct. 14, 2010, titled “Systems and Methods for Storing, Analyzing, Retrieving, and Displaying Streaming Medical Data”; U.S. application Ser. No. 12/904,377, filed Oct. 14, 2010, titled “Medical Monitoring System”; U.S. application Ser. No. 13/269,296, filed Oct. 7, 2011, titled “Risk Analysis System”; and U.S. application Ser. No. 13/371,767, filed Feb. 13, 2012, titled “Medical Characterization System.”

IV. Medical Edge Router Embodiments

Turning to FIG. 9, another embodiment of a computing environment 900 is shown for providing clinicians with access to patient care data. The computing environment 900 is compatible with and can be used in conjunction with the features of the computing environment 100 described above, as well as with other embodiments described above. For example, the computing environment 900 can provide access to a medical network service, such as the MNS 110 or 210. The MNS can be implemented in one or more network operation centers 970, as shown. Each of the network operation centers 970 can be implemented in a separate data center in geographically dispersed locations so as to provide redundant access and access that is geographically proximate to users of the MNS.

One of the major challenges associated with providing network-based medical monitoring services for hospitals and other clinical facilities is network connectivity. Networks, including the Internet, are prone to network failure and therefore, it can be desirable to provide for redundancy in communication channels or pathways that access the MNS. Advantageously, in the depicted embodiment of FIG. 9, the computing environment 900 includes multiple redundant pathways to communicate data from point-of-care devices 912 to the MNS in the network operation centers 970, which will be described herein.

As shown, the point-of-care devices 912 are arranged in a patient area 910, which may be a hospital or a subset thereof. The point-of-care devices 912 can be patient monitoring devices, such as any of the patient monitoring devices described above, and can monitor any physiological parameter of a patient, such as oxygen saturation, blood pressure, heart rate, ECG parameters, respiratory rates, hemoglobin, and the like. The point-of-care devices 912 can be bedside devices or body-worn patient monitoring devices, and in general, may provide physiological parameter data, trend data, alarms and alerts to clinician devices over a network. Further, the point-of-care devices 912 can provide such data outside of a hospital network to clinician devices over the Internet 950 (or other wide-area network) through a medical edge router 920.

In the depicted embodiment, the medical edge router 920 communicates with the network operation centers 970 over multiple communication pathways, including multiple Internet Service Provider networks 940. For convenience, this specification generally refers to the Internet Service Provider networks 940 as ISPs. The medical edge router 920 can be an intelligent edge router that provides redundant communications for transmitting patient data, among other features. For instance, in one embodiment, the medical edge router 920 can attempt to send patient data, including physiological parameters, trends and/or alarms, to the MNS in a network operations center 970 over a first one of the ISPs 940. If the first ISP 940 is unavailable, the medical edge router 920 can attempt to communicate with the MNS through a second one of the ISPs 940, and so forth, until the medical edge router 920 has attempted to contact the MNS through most or all of the ISPs 940.

In one embodiment, if the ISPs are unavailable, then the medical edge router 920 can attempt to contact the MNS through a wireless ISP 944; for example, by communicating wirelessly through a local access point 942, which then communicates via the ISP 944. In other embodiments, the medical edge router 920 can attempt to first communicate through broadband mechanisms, such as wired LAN, WAN or wireless or satellite-based broadband, prior to using dial-up or lower bandwidth links. In yet another embodiment, the medical edge router 920 performs back-up communications to clinicians via cellular networks if the ISPs 940, 944 are unavailable. In such instances, the medical edge router 920 may, for instance, send a text message (via SMS) or email or other communication to one or more clinicians that includes some or all of the data obtained from one or more point-of-care devices 912. Since text messages and emails tend to be limited in length, the medical edge router 920 can instead summarize data obtained from the point-of-care devices 912 and send the summarized data over the cellular network or other network.

In some embodiments, the ISPs 940 or 944 may be available, but one or more of the network operation centers 970 that host the MNS may be down and unavailable. Accordingly, it can be useful in such circumstances for the medical edge router 920 to communicate via SMS or email over one of the ISPs 940 or cellular networks (not shown), to clinicians. In any case, when communicating via SMS or email, the medical edge router 920 can reduce the amount of data sent or selectively prioritize the data sent to clinicians, to send higher-priority data in view of the reduced bandwidth available, in such communication of channels. In one embodiment, for example, the medical edge router 920 can send a summary of the alarms or parameter values from the point-of-care devices 912 to a clinician via SMS or email or a similar mechanism, without sending trend data, which can consume a significant amount of bandwidth. In another example, medical edge router 920 prioritizes alarms over parameter values over trend data, such that if an alarm is to be transmitted, the medical edge router 920 can transmit the alarm to a clinician device, instead of more bandwidth-intensive data. If no alarms are to be transmitted, the medical edge router 920 can transmit more bandwidth-intensive data.

In yet another embodiment, the medical edge router 920 is also connected to an uninterruptible power supply or UPS 932 that can provide the medical edge router 920 with continued power, should mains power become available. The UPS 932 can also power other systems in the clinical facility, including the point-of-care devices 912 and a local server mirror appliance 930. The local server mirror appliance 930 can be a server or other computing device that includes some or all of the functionality of the MNS described above. In one embodiment, the local server mirror appliance 930 includes important or critical patient care functionality of the MNS. For example, the appliance 930 may include a portion of the functionality of the MNS and may operate in parallel with the MNS to calculate parameter values or a wellness index in case of failure or inability to contact the MNS over the network.

Also shown is a VPN 960 through which the point-of-care devices 912 can connect to the network operation centers 970. The VPN 960 can provide security for such communications, although the VPN 960 may be optional in some embodiments.

It should also be noted that in certain embodiments, the computing environment 900 of FIG. 9 can include multiple edge routers 920, which can be used for failover purposes within the hospital network. For instance, each point-of-care device 912 can be connected to two or more edge routers 920 and can send data over each edge router 920 to reduce the potential of having a single point of failure in the network.

Turning to FIG. 10, a more detailed example of a medical edge router 1020 is shown. The medical edge router 1020 can have some or all the functionality of the medical edge router 920 described above with respect to FIG. 9. Various components of the medical edge router 1020 shown can be implemented in hardware and/or software. The medical edge router 1020 receives input packets and forwards output packets, which the medical edge router 1020 can route to an appropriate destination in the network. The medical edge router 1020 can be placed at the edge of a network in or near a clinical facility (see, e.g., FIG. 9) and therefore may provide access to other networks outside of the clinical facility network.

The example medical edge router 1020 shown includes a data logger 1021 and a routing module 1022 that both receive the input packets. The data logger 1021 can be a packet-sniffer or the like that copies the input packets and thereby makes the input packets available to a traffic inspector 1023. The data logger 1021 may also store the packets for subsequent analysis, including analysis for determining conditions leading up to a network communications failure after the failure occurred. The traffic inspector 1023 can inspect the input packets logged by the data logger 1021 to determine whether any of the input packets include alarms. If an alarm is detected, the traffic inspector 1023 can notify the routing module 1022 of such an alarm condition, enabling the routing module 1022 to prioritize the distribution of packets that relate to include alarms (including optionally packets having parameter data associated with the alarms).

The routing module 1022 includes a failover module 1024 that can receive communications from the traffic inspector 1023 about alarms and can select destinations for the packets accordingly. The routing module 1022 also communicates with one or more routing tables 1025 that can be populated using any suitable routing protocol, such as the Border Gateway Protocol (BGP) commonly used in routers in the Internet. The routing module 1022 can route the input packets to appropriate routers or switches in the Internet (or other networks) based on the information stored in the routing tables 1025. The routing module 1022 can update the routing tables 1025 over time, using BGP or another protocol.

The failover module 1024 can provide the redundant failover features described above, at least in part, with respect to FIG. 9. For instance, the failover module 1024 can determine whether an ISP or other network channel is unavailable and can fail over or escalate communications to another ISP or communication channel when network channel failure is detected.

The routing module 1022 can prioritize alarms, as described above, when detected by the traffic inspector 1023. When an alarm is included in an input packet, as indicated by the traffic inspector 1023, the routing module can prioritize the alarm by broadcasting the alarm over multiple or all channels used by the routing module 1022. For instance, the routing module 1022 can broadcast such packets over multiple ISPs, or over both wired and wireless ISPs, or over both an ISP and a cellular network, or the like.

Packets are sent from the routing module 1022 to a network interface card 1030 that can implement the data link and/or physical layers of the TCP/IP network stack. The network interface 1030 includes, in the depicted embodiment, an Ethernet or wired modem 1032, a wireless (e.g., WiFi) radio 1034, and a cellular radio 1036. The network interface 1030 outputs the output packets based on instructions from the routing module 1022. For instance, if the routing module 1022 instructs the network interface 1030 to send packets over a wired ISP, the network interface 1030 can send such packets via the Ethernet or wired modem 1032. Conversely, if the routing module 1022 instructs the network interface 1030 to send such packets via a WiFi or wireless link, the wireless radio 1034 of the network interface 1030 can transmit such packets. Similarly, the cellular radio 1036 can transmit certain packets over cellular networks (such as SMS packets), as instructed by the routing module 1022. The components of the network interface 1030 are example components only and could be added to or removed from in other embodiments.

In the depicted embodiment, the medical edge router 1020 also includes a loudspeaker 1026 and a display 1027. The loudspeaker 1026 can output audible alarms when network connectivity is detected as being down by the medical edge router 1022. For instance, whenever an ISP becomes unavailable, or another network communications channel becomes unavailable, the routing module 1022 can cause the loud speaker 1026 to issue an audible alarm. Likewise, the display 1027 can output visual alarms in response to the routing module 1022 detecting a network communication path being unavailable, enabling network personnel to troubleshoot the medical edge router 1020 when needed. The medical edge router 1020 can also send SNMP packets to IT personnel to alert IT personnel of network failures, failover conditions, and the like.

In addition, the medical edge router 1020 can also include a precision time service 1028 that can apply time stamps to packets sent by the routing module 1022. This precision time service 1028 can be synchronized or substantially synchronized with time services used by other medical edge routers 1020 in the hospital network or in other hospital networks remote from the medical edge router 1020 shown. Accordingly, packets received by the MNS in any one of the network operation centers 970 can maintain a synchronous or time-ordered view of the packets. It can be beneficial to maintain a synchronous or time-ordered view of medical data received from the point-of-care devices 912 to ensure or attempt to ensure that alarms and other data are received in the proper time order, so that clinicians can take appropriate action based on such data.

In one embodiment, the precision time service 1028 communicates with one or more GPS satellites to obtain a precision time value. In another embodiment, the precision time service 1028 communicates with an atomic clock, or the like, to obtain a precision time value, although other techniques may be used to obtain precision time values.

The medical edge router 1020 can have many other features than those shown in FIG. 10 (or fewer features). For instance, the medical edge router 1020 can monitor or manage performance of the local clinical facility network. Multiple medical edge routers 1020 can be included in or in communication with a single facility, such as a single medical edge router 1020 for each hospital floor. Many other embodiments are possible.

Turning to FIG. 11, an example edge router failover process 1100 is shown. The edge router failure process 1100 can be implemented by the edge router 920 or 1020 described above and can advantageously provide for redundancy in hospital network communications. While the process 1100 will be described with respect to the medical edge router described above for convenience, it should be understood that the process 1100 could be implemented by any computing device or network device.

At block 1102, the edge router attempts to communicate with the medical network service (MNS) through a first ISP. At block 1104, the medical edge router determines whether the ISP is available. If so, the edge router is able to communicate its message to the MNS, and the process 1100 ends. However, if the ISP is not available, then the medical edge router determines at block 1106 whether all ISPs are unavailable, or whether the MNS is not responding. If all ISPs are unavailable, it may be helpful for the medical edge router to contact the MNS using another communication pathway, such as cellular or wireless. However, some ISPs may be available while the MNS is not responding, in which case it may also be useful to use a different communication pathway to provide patient information to clinicians.

If all ISPs are unavailable or the MNS is not responding, then the edge router can attempt to communicate with the MNS through the next ISP at block 1108, looping back to block 1104. However, if all ISPs are unavailable or the MNS is not responding, then the edge router can send reduced data to the clinicians via an alternative mechanism, such as email or SMS, at block 1110. For example, the edge router can transmit a summary of patient monitoring data over a cellular network or via email to clinicians. In one embodiment, in response to detecting that all IPSs are unavailable or the MNS is not responding, the routing module 1022 sends a request to the local server mirror appliance 930 or the point of care devices 912 for a summary of the patient monitoring data. Then, upon receipt of the summary data, the edge router can communicate the summarized data over an alternative communications channel. In other embodiments, the local server mirror appliance 930 and/or the point of care devices 912 send summary data to the edge router together with more verbose patient monitoring data so that the edge router can send the summary data without delay in case of communications pathways to the MNS or clinicians becoming unavailable.

Turning to FIG. 12, an example embodiment of an edge router alarm-handling process 1200 is shown. The edge router alarm-handling process 1200 can also be implemented by either of the edge routers 920 or 1020 described above, and for convenience, will be described with respect to the medical edge router, although the process 1200 could be implemented by any computing device or network device.

At block 1202, the edge router receives input packets, and at block 1204, analyses those input packets to identify any patient monitoring alarms. For instance, the traffic inspector 1023 of the edge router 1020 can identify any patient monitoring alarms in a given packet. In one embodiment, the traffic inspector 1023 searches for a particular payload in a packet that indicates that an alarm is in the packet, and in another embodiment, alarm information is included in a header of the packet.

If an alarm is detected at block 1206, the traffic inspector 1023 sends the alarm over multiple communication channels for redundancy at block 1208, such as over multiple ISPs, or over a wired ISP and a wireless ISP, or over an ISP and over a cellular network, combinations of the same, or the like. If an alarm is not detected at block 1206, then the process 1200 can loop back to 1204, effectively allowing the traffic inspector 1023 to continue to monitor for the presence of alarms.

V. Terminology

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 all together (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 steps 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 steps 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 processor can be a hardware processor comprising digital logic circuitry. Further, a 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 also be implemented as a combination of hardware 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, any of the signal processing algorithms described herein may be implemented in analog 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 personal organizer, a device controller, and a computational engine within an appliance, to name a few.

The steps of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, 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 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.

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 of the inventions described herein can be embodied 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.

Claims

1. A system for remotely escalating a patient monitoring alarm to provide a continuum of care to a patient after discharge from a hospital, the system comprising: a memory comprising processor-executable instructions stored thereon, the processor-executable instructions pertaining to alarm escalation; anda hardware processor configured to execute the processor-executable instructions pertaining to alarm escalation in response to remotely receiving an alarm and data from a patient monitoring device based on at least one physiological parameter of the patient, the patient monitoring device being assigned to the patient in response to the patient being admitted to the hospital, the hardware processor configured to output an alarm profile template matching attributes of the patient to a clinician and transmit customized alarm settings for the patient to the patient monitoring device in response to acceptance of the alarm profile template by the clinician, wherein the hardware processor is further configured to: designate, based on data stored in the memory, first and second care providers who have been previously associated with the patient in the memory, wherein the first care provider is a primary care provider of the patient and the second care provider is a non-primary care provider of the patient;electronically determine a situational context of the first care provider;in response to determining the situation context of the first care provider indicates the first care provider is available and local to the patient, transmit the alarm to the first care provider for possible in-person intervention;in response to determining the situational context of the first care provider indicates the first care provider is available but located remote from the patient, and that the second care provider is local to the patient: transmit, to the first care provider, the alarm and data received from the patient monitoring device for interaction with the patient via telepresence technologies;electronically receive a recommended course of action from the first care provider regarding the alarm based on the interaction with the patient via telepresence technologies; andescalate the alarm by transmitting the recommended course of action and the alarm to the second care provider; andin response to determining the situational context of the first care provider indicates that the first care provider is unavailable and that the second care provider is local to the patient, automatically escalate the alarm to the second care provider by transmitting the alarm to the second care provider for possible in-person intervention.
2. The system of claim 1, wherein the hardware processor is further configured to store an alarm setting associated with the patient in a cloud data store.
3. The system of claim 1, wherein the recommended course of action comprises a diagnosis and a medication recommendation.
4. The system of claim 1, wherein the hardware processor is further configured to, prior to receiving the alarm, adjust an alarm setting for the patient.
5. The system of claim 4, wherein adjusting the alarm setting for the patient is based on a received electronic indication that the patient is ambulatory.
6. The system of claim 4, wherein the at least one physiological parameter of the patient comprises a heart rate of the patient.
7. The system of claim 6, wherein adjusting the alarm setting for the patient comprises increasing a heart rate threshold limit at which the alarm occurs.
8. The system of claim 4, wherein adjusting the alarm setting for the patient is based on a health condition of the patient.
9. A system for remotely escalating a patient monitoring alarm to provide a continuum of care to a patient after discharge from a hospital, the system comprising: a hardware processor configured to: remotely receive an alarm and physiological data from a device monitoring the patient, the device being assigned to the patient in response to the patient being admitted to the hospital, the hardware processor configured to output an alarm profile template matching attributes of the patient to a clinician and transmit customized alarm settings for the patient to the device in response to acceptance of the alarm profile template by the clinician;designate first and second care providers associated with the patient, wherein the first care provider is a primary care provider of the patient and the second care provider is a non-primary care provider of the patient;electronically determine a situational context of the first care provider;in response to determining the situation context of the first care provider indicates the first care provider is available and local to the patient, transmit the alarm to the first care provider for possible in-person intervention;in response to determining the situational context of the first care provider indicates the first care provider is available but located remote from the patient and that the second care provider is local to the patient: transmit, to the first care provider, the alarm and data received from the patient monitoring device for interaction with the patient via telepresence technologies;electronically receive a recommended course of action from the first care provider regarding the alarm based on the interaction with the patient via telepresence technologies; andescalate the alarm by transmitting the recommended course of action and the alarm to the second care provider; andin response to determining the situational context of the first care provider indicates that the first care provider is unavailable and that the second care provider is local to the patient, automatically escalate the alarm to the second care provider by transmitting the alarm to the second care provider for possible in-person intervention.
10. The system of claim 9, wherein the physiological data comprises one or both of trend data and parameter data.
11. The system of claim 9, wherein the recommended course of action comprises a diagnosis or a medication recommendation.
12. The system of claim 9, wherein the hardware processor is further configured to transmit the recommended course of action and the alarm to a device of the second care provider using video technology.
13. The system of claim 9, wherein the hardware processor is further configured to, prior to receiving the alarm, adjust an alarm setting for the patient.
14. The system of claim 13, wherein adjusting the alarm setting for the patient is based on a received electronic indication that the patient is ambulatory and/or a health condition of the patient.
15. The system of claim 9, wherein the hardware processor is further configured to store an alarm setting associated with the patient in a cloud data store.
16. A method for remotely escalating a patient monitoring alarm to provide a continuum of care to a patient after discharge from a hospital, the method comprising: remotely receiving an alarm and physiological data from a device monitoring the patient, the device being assigned to the patient in response to the patient being admitted to the hospital, an alarm profile template matching attributes of the patient being outputted to a clinician and customized alarm settings for the patient being transmitted to the device in response to acceptance of the alarm profile template by the clinician;designating, based on data stored in a memory of an alarm escalation system, first and second care providers who have been previously associated with the patient in the memory, wherein the first care provider is a primary care provider of the patient and the second care provider is a non-primary care provider of the patient, the primary care provider being more familiar with a medical history of the patient than the non-primary care provider;electronically determining a situational context of the first care provider;in response to determining the situation context of the first care provider indicates the first care provider is available and local to the patient, transmit the alarm to the first care provider for possible in-person intervention;in response to determining the situational context of the first care provider indicates the first care provider is available but located remote from the patient, and that the second care provider is local to the patient: transmitting, to the first care provider, the alarm and data received from the patient monitoring device for interaction with the patient via telepresence technologies;electronically receiving a recommended course of action from the first care provider regarding the alarm based on the interaction with the patient via telepresence technologies; andescalating the alarm by transmitting the recommended course of action and the alarm to the second care provider; andin response to determining the situational context of the first care provider indicates that the first care provider is unavailable and that the second care provider is local to the patient, automatically escalating the alarm to the second care provider by transmitting the alarm to the second care provider for possible in-person intervention.
17. The method of claim 16, further comprising, prior to receiving the alarm, adjusting an alarm setting for the patient based on an electronic indication that the patient is ambulatory.
18. The method of claim 16, wherein said transmitting the recommended course of action and the alarm to the second care provider comprises using the telepresence technologies.
19. The system of claim 1, wherein the patient monitoring device is outfitted on the patient upon discharge from the hospital for monitoring of the patient.
20. The system of claim 1, wherein, in response to the clinician not accepting the alarm profile template, the hardware processor is configured to output options for the clinician to modify the alarm profile template.

US Referenced Citations (1812)

Number	Name	Date	Kind
3646606	Buxton et al.	Feb 1972	A
3690313	Weppner et al.	Sep 1972	A
3810102	Parks, III et al.	May 1974	A
3815583	Scheidt	Jun 1974	A
3972320	Kalman	Aug 1976	A
3978849	Geneen	Sep 1976	A
4108166	Schmid	Aug 1978	A
4231354	Kurtz et al.	Nov 1980	A
4589415	Haaga	May 1986	A
4662378	Thomis	May 1987	A
4827943	Bornn et al.	May 1989	A
4838275	Lee	Jun 1989	A
4852570	Levine	Aug 1989	A
4960128	Gordon et al.	Oct 1990	A
4964408	Hink et al.	Oct 1990	A
5041187	Hink et al.	Aug 1991	A
5069213	Polczynski	Dec 1991	A
5092340	Yamaguchi et al.	Mar 1992	A
5140519	Friesdorf et al.	Aug 1992	A
5159932	Zanetti et al.	Nov 1992	A
5161539	Evans et al.	Nov 1992	A
5163438	Gordon et al.	Nov 1992	A
5262944	Weisner et al.	Nov 1993	A
5277189	Jacobs	Jan 1994	A
5278627	Aoyagi et al.	Jan 1994	A
5282474	Valdes Sosa et al.	Feb 1994	A
5296688	Hamilton et al.	Mar 1994	A
5318037	Evans et al.	Jun 1994	A
5319355	Russek	Jun 1994	A
5331549	Crawford, Jr.	Jul 1994	A
5333106	Lanpher et al.	Jul 1994	A
5337744	Branigan	Aug 1994	A
5341805	Stavridi et al.	Aug 1994	A
5348008	Bornn et al.	Sep 1994	A
5358519	Grandjean	Oct 1994	A
D353195	Savage et al.	Dec 1994	S
D353196	Savage et al.	Dec 1994	S
5375599	Shimizu	Dec 1994	A
5375604	Kelly et al.	Dec 1994	A
5377676	Vari et al.	Jan 1995	A
5400794	Gorman	Mar 1995	A
D357982	Dahl et al.	May 1995	S
5416695	Stutman et al.	May 1995	A
D359546	Savage et al.	Jun 1995	S
5431170	Mathews	Jul 1995	A
5434611	Tamura	Jul 1995	A
5436499	Namavar et al.	Jul 1995	A
D361840	Savage et al.	Aug 1995	S
D362063	Savage et al.	Sep 1995	S
5452717	Branigan et al.	Sep 1995	A
D363120	Savage et al.	Oct 1995	S
5456252	Vari et al.	Oct 1995	A
5462051	Oka et al.	Oct 1995	A
5479934	Imran	Jan 1996	A
5482036	Diab et al.	Jan 1996	A
5483968	Adam et al.	Jan 1996	A
5490505	Diab et al.	Feb 1996	A
5494041	Wilk	Feb 1996	A
5494043	O'Sullivan et al.	Feb 1996	A
5503149	Beavin	Apr 1996	A
5505202	Mogi et al.	Apr 1996	A
5533511	Kaspari et al.	Jul 1996	A
5534851	Russek	Jul 1996	A
5537289	Dahl	Jul 1996	A
5544649	David et al.	Aug 1996	A
5553609	Chen et al.	Sep 1996	A
5558638	Evers et al.	Sep 1996	A
5561275	Savage et al.	Oct 1996	A
5562002	Lalin	Oct 1996	A
5566676	Rosenfeldt et al.	Oct 1996	A
5576952	Stutman et al.	Nov 1996	A
5579001	Dempsey et al.	Nov 1996	A
5590649	Caro et al.	Jan 1997	A
5602924	Durand et al.	Feb 1997	A
5619991	Sloane	Apr 1997	A
5632272	Diab et al.	May 1997	A
5638816	Kiani-Azarbayjany et al.	Jun 1997	A
5638818	Diab et al.	Jun 1997	A
5640967	Fine et al.	Jun 1997	A
5645440	Tobler et al.	Jul 1997	A
5671914	Kalkhoran et al.	Sep 1997	A
5685299	Diab et al.	Nov 1997	A
5685314	Geheb et al.	Nov 1997	A
5687717	Halpern et al.	Nov 1997	A
5694020	Lang et al.	Dec 1997	A
5724580	Levin et al.	Mar 1998	A
5724983	Selker et al.	Mar 1998	A
5725308	Smith et al.	Mar 1998	A
5726440	Kalkhoran et al.	Mar 1998	A
5734739	Sheehan et al.	Mar 1998	A
D393830	Tobler et al.	Apr 1998	S
5743262	Lepper, Jr. et al.	Apr 1998	A
5747806	Khalil et al.	May 1998	A
5750994	Schlager	May 1998	A
5752976	Duffin	May 1998	A
5754111	Garcia	May 1998	A
5758079	Ludwig et al.	May 1998	A
5758644	Diab et al.	Jun 1998	A
5760910	Lepper, Jr. et al.	Jun 1998	A
5769785	Diab et al.	Jun 1998	A
5772585	Lavin et al.	Jun 1998	A
5782757	Diab et al.	Jul 1998	A
5782805	Meinzer	Jul 1998	A
5785659	Caro et al.	Jul 1998	A
5791347	Flaherty et al.	Aug 1998	A
5801637	Lomholt	Sep 1998	A
5810734	Caro et al.	Sep 1998	A
5813403	Soller et al.	Sep 1998	A
5822544	Chaco et al.	Oct 1998	A
5822546	George	Oct 1998	A
5823950	Diab et al.	Oct 1998	A
5829723	Brunner	Nov 1998	A
5830131	Caro et al.	Nov 1998	A
5833618	Caro et al.	Nov 1998	A
5855550	Lai et al.	Jan 1999	A
5860919	Kiani-Azarbayjany et al.	Jan 1999	A
5876351	Rohde	Mar 1999	A
5890929	Mills et al.	Apr 1999	A
5904654	Wohltmann et al.	May 1999	A
5910139	Cochran et al.	Jun 1999	A
5919134	Diab	Jul 1999	A
5921920	Marshall et al.	Jul 1999	A
5924074	Evans	Jul 1999	A
5931160	Gilmore et al.	Aug 1999	A
5931791	Saltzstein et al.	Aug 1999	A
5934925	Tobler et al.	Aug 1999	A
5940182	Lepper, Jr. et al.	Aug 1999	A
5942986	Shabot et al.	Aug 1999	A
5951469	Yamaura	Sep 1999	A
5987343	Kinast	Nov 1999	A
5987519	Peifer et al.	Nov 1999	A
5995855	Kiani et al.	Nov 1999	A
5997343	Mills et al.	Dec 1999	A
6002952	Diab et al.	Dec 1999	A
6006119	Soller et al.	Dec 1999	A
6010937	Karam et al.	Jan 2000	A
6011986	Diab et al.	Jan 2000	A
6014346	Malone	Jan 2000	A
6018673	Chin et al.	Jan 2000	A
6024699	Surwit et al.	Feb 2000	A
6027452	Flaherty et al.	Feb 2000	A
6032678	Rottem	Mar 2000	A
6035230	Kang et al.	Mar 2000	A
6036642	Diab et al.	Mar 2000	A
6036718	Ledford et al.	Mar 2000	A
6040578	Malin et al.	Mar 2000	A
6045509	Caro et al.	Apr 2000	A
6045527	Appelbaum et al.	Apr 2000	A
6057758	Dempsey et al.	May 2000	A
6066204	Haven	May 2000	A
6067462	Diab et al.	May 2000	A
6081735	Diab et al.	Jun 2000	A
6088607	Diab et al.	Jul 2000	A
6093146	Filangeri	Jul 2000	A
6101478	Brown	Aug 2000	A
6106463	Wilk	Aug 2000	A
6110522	Lepper, Jr. et al.	Aug 2000	A
6115673	Malin et al.	Sep 2000	A
6124597	Shehada	Sep 2000	A
6128521	Marro et al.	Oct 2000	A
6129675	Jay	Oct 2000	A
6132218	Benja-Athon	Oct 2000	A
6139494	Cairnes	Oct 2000	A
6144868	Parker	Nov 2000	A
6151516	Kiani-Azarbayjany et al.	Nov 2000	A
6152754	Gerhardt et al.	Nov 2000	A
6157850	Diab et al.	Dec 2000	A
6165005	Mills et al.	Dec 2000	A
6167258	Schmidt et al.	Dec 2000	A
D437058	Gozani	Jan 2001	S
6168563	Brown	Jan 2001	B1
6171237	Avitall et al.	Jan 2001	B1
6175752	Say et al.	Jan 2001	B1
6183417	Gehab et al.	Feb 2001	B1
6184521	Coffin, IV et al.	Feb 2001	B1
6185448	Borovsky	Feb 2001	B1
6195576	John	Feb 2001	B1
6206830	Diab et al.	Mar 2001	B1
6221012	Maschke et al.	Apr 2001	B1
6224553	Nevo	May 2001	B1
6229856	Diab et al.	May 2001	B1
6230142	Benigno et al.	May 2001	B1
6232609	Snyder et al.	May 2001	B1
6236872	Diab et al.	May 2001	B1
6241683	Macklem et al.	Jun 2001	B1
6241684	Amano et al.	Jun 2001	B1
6251113	Appelbaum	Jun 2001	B1
6253097	Aronow et al.	Jun 2001	B1
6255708	Sudharsanan et al.	Jul 2001	B1
6256523	Diab et al.	Jul 2001	B1
6263222	Diab et al.	Jul 2001	B1
6267723	Matsumura et al.	Jul 2001	B1
6269262	Kandori et al.	Jul 2001	B1
6278522	Lepper, Jr. et al.	Aug 2001	B1
6280213	Tobler et al.	Aug 2001	B1
6280381	Malin et al.	Aug 2001	B1
6285896	Tobler et al.	Sep 2001	B1
6301493	Marro et al.	Oct 2001	B1
6304767	Soller et al.	Oct 2001	B1
6308089	von der Ruhr et al.	Oct 2001	B1
6312378	Bardy	Nov 2001	B1
6317627	Ennen et al.	Nov 2001	B1
6321100	Parker	Nov 2001	B1
6322502	Schoenberg et al.	Nov 2001	B1
6325761	Jay	Dec 2001	B1
6329139	Nova et al.	Dec 2001	B1
6332100	Sahai et al.	Dec 2001	B1
6334065	Al-Ali et al.	Dec 2001	B1
6338039	Lonski et al.	Jan 2002	B1
6343224	Parker	Jan 2002	B1
6349228	Kiani et al.	Feb 2002	B1
6352504	Ise	Mar 2002	B1
6354235	Davies	Mar 2002	B1
6360114	Diab et al.	Mar 2002	B1
6364834	Reuss et al.	Apr 2002	B1
6364839	Little et al.	Apr 2002	B1
6368283	Xu et al.	Apr 2002	B1
6371921	Caro et al.	Apr 2002	B1
6377829	Al-Ali	Apr 2002	B1
6385476	Osadchy et al.	May 2002	B1
6385589	Trusheim et al.	May 2002	B1
6388240	Schulz et al.	May 2002	B2
6397091	Diab et al.	May 2002	B2
6406426	Reuss et al.	Jun 2002	B1
6407335	Franklin-Lees	Jun 2002	B1
6411373	Garside et al.	Jun 2002	B1
6415167	Blank et al.	Jul 2002	B1
6430437	Marro	Aug 2002	B1
6430525	Weber et al.	Aug 2002	B1
6463311	Diab	Oct 2002	B1
6470199	Kopotic et al.	Oct 2002	B1
6470893	Boesen	Oct 2002	B1
6480505	Johansson et al.	Nov 2002	B1
6487429	Hockersmith et al.	Nov 2002	B2
6501975	Diab et al.	Dec 2002	B2
6505059	Kollias et al.	Jan 2003	B1
6515273	Al-Ali	Feb 2003	B2
6516289	David et al.	Feb 2003	B2
6519487	Parker	Feb 2003	B1
6524240	Thede	Feb 2003	B1
6525386	Mills et al.	Feb 2003	B1
6526300	Kiani et al.	Feb 2003	B1
6534012	Hazen et al.	Mar 2003	B1
6541756	Schulz et al.	Apr 2003	B2
6542764	Al-Ali et al.	Apr 2003	B1
6544173	West et al.	Apr 2003	B2
6544174	West et al.	Apr 2003	B2
6551243	Bocionek et al.	Apr 2003	B2
6570592	Sajdak et al.	May 2003	B1
6578428	Dromms et al.	Jun 2003	B1
6580086	Schulz et al.	Jun 2003	B1
6584336	Ali et al.	Jun 2003	B1
6587196	Stippick et al.	Jul 2003	B1
6587199	Luu	Jul 2003	B1
6595316	Cybulski et al.	Jul 2003	B2
6597932	Tian et al.	Jul 2003	B2
6597933	Kiani et al.	Jul 2003	B2
6606511	Ali et al.	Aug 2003	B1
6616606	Peterson et al.	Sep 2003	B1
6632181	Flaherty et al.	Oct 2003	B2
6635559	Greenwald et al.	Oct 2003	B2
6639668	Trepagnier	Oct 2003	B1
6640116	Diab	Oct 2003	B2
6640117	Makarewicz et al.	Oct 2003	B2
6641533	Causey et al.	Nov 2003	B2
6643530	Diab et al.	Nov 2003	B2
6646556	Smith et al.	Nov 2003	B1
6650917	Diab et al.	Nov 2003	B2
6650939	Takpke, II et al.	Nov 2003	B2
6654624	Diab et al.	Nov 2003	B2
D483872	Cruz et al.	Dec 2003	S
6658276	Kianl et al.	Dec 2003	B2
6661161	Lanzo et al.	Dec 2003	B1
6663570	Mott et al.	Dec 2003	B2
6671531	Al-Ali et al.	Dec 2003	B2
6678543	Diab et al.	Jan 2004	B2
6684090	Ali et al.	Jan 2004	B2
6684091	Parker	Jan 2004	B2
6694180	Boesen	Feb 2004	B1
6697656	Al-Ali	Feb 2004	B1
6697657	Shehada et al.	Feb 2004	B1
6697658	Al-Ali	Feb 2004	B2
RE38476	Diab et al.	Mar 2004	E
6699194	Diab et al.	Mar 2004	B1
6714804	Al-Ali et al.	Mar 2004	B2
RE38492	Diab et al.	Apr 2004	E
6719694	Weng et al.	Apr 2004	B2
6721582	Trepagnier et al.	Apr 2004	B2
6721585	Parker	Apr 2004	B1
6725075	Al-Ali	Apr 2004	B2
6725086	Marinello	Apr 2004	B2
6728560	Kollias et al.	Apr 2004	B2
6730026	Christ et al.	May 2004	B2
6735459	Parker	May 2004	B2
6738652	Mattu et al.	May 2004	B2
6745060	Diab et al.	Jun 2004	B2
6746406	Lia et al.	Jun 2004	B2
6750463	Riley	Jun 2004	B1
6751492	Ben-haim	Jun 2004	B2
6760607	Al-Ali	Jul 2004	B2
6766188	Soller	Jul 2004	B2
6770028	Ali et al.	Aug 2004	B1
6771994	Kiani et al.	Aug 2004	B2
6783492	Dominguez	Aug 2004	B2
6788965	Ruchti et al.	Sep 2004	B2
6790178	Mault et al.	Sep 2004	B1
6792300	Diab et al.	Sep 2004	B1
6795724	Hogan	Sep 2004	B2
6796186	Lia et al.	Sep 2004	B2
6804656	Rosenfeld	Oct 2004	B1
6807050	Whitehorn et al.	Oct 2004	B1
6813511	Diab et al.	Nov 2004	B2
6816241	Grubisic	Nov 2004	B2
6816741	Diab	Nov 2004	B2
6817979	Nihtila et al.	Nov 2004	B2
6822564	Al-Ali	Nov 2004	B2
6826419	Diab et al.	Nov 2004	B2
6830711	Mills et al.	Dec 2004	B2
6837848	Bonner et al.	Jan 2005	B2
6841535	Divita et al.	Jan 2005	B2
6850787	Weber et al.	Feb 2005	B2
6850788	Al-Ali	Feb 2005	B2
6852083	Caro et al.	Feb 2005	B2
6855112	Kao et al.	Feb 2005	B2
6860266	Blike	Mar 2005	B2
6861639	Al-Ali	Mar 2005	B2
6876931	Lorenz et al.	Apr 2005	B2
6893396	Schulze et al.	May 2005	B2
6897788	Khair et al.	May 2005	B2
6898452	Al-Ali et al.	May 2005	B2
6907237	Dorenbosch et al.	Jun 2005	B1
6915149	Ben-haim	Jul 2005	B2
6920345	Al-Ali et al.	Jul 2005	B2
6931268	Kiani-Azarbayjany et al.	Aug 2005	B1
6934570	Kiani et al.	Aug 2005	B2
6939305	Flaherty et al.	Sep 2005	B2
6943348	Coffin, IV	Sep 2005	B1
6950687	Al-Ali	Sep 2005	B2
6952340	Son et al.	Oct 2005	B2
6956649	Acosta et al.	Oct 2005	B2
6957107	Rogers et al.	Oct 2005	B2
6961598	Diab	Nov 2005	B2
6970792	Diab	Nov 2005	B1
6979812	Al-Ali	Dec 2005	B2
6980419	Smith et al.	Dec 2005	B2
6983179	Ben-haim	Jan 2006	B2
6985764	Mason et al.	Jan 2006	B2
6988989	Weiner et al.	Jan 2006	B2
6990087	Rao et al.	Jan 2006	B2
6990364	Ruchti et al.	Jan 2006	B2
6993371	Kiani et al.	Jan 2006	B2
6996427	Ali et al.	Feb 2006	B2
6997884	Ulmsten	Feb 2006	B2
6998247	Monfre et al.	Feb 2006	B2
6999904	Weber et al.	Feb 2006	B2
7003338	Weber et al.	Feb 2006	B2
7003339	Diab et al.	Feb 2006	B2
7015451	Dalke et al.	Mar 2006	B2
7024233	Ali et al.	Apr 2006	B2
7025729	de Chazal et al.	Apr 2006	B2
7027849	Al-Ali	Apr 2006	B2
7030749	Al-Ali	Apr 2006	B2
7033761	Shafer	Apr 2006	B2
7035686	Hogan	Apr 2006	B2
7039449	Al-Ali	May 2006	B2
7041060	Flaherty et al.	May 2006	B2
7042338	Weber	May 2006	B1
7044918	Diab	May 2006	B2
7044930	Stromberg	May 2006	B2
7048687	Reuss et al.	May 2006	B1
7063666	Weng et al.	Jun 2006	B2
7067893	Mills et al.	Jun 2006	B2
7079035	Bock et al.	Jul 2006	B2
D526719	Richie, Jr. et al.	Aug 2006	S
7096052	Mason et al.	Aug 2006	B2
7096054	Abdul-Hafiz et al.	Aug 2006	B2
D529616	Deros et al.	Oct 2006	S
7132641	Schulz et al.	Nov 2006	B2
7133710	Acosta et al.	Nov 2006	B2
7142901	Kiani et al.	Nov 2006	B2
7149561	Diab	Dec 2006	B2
7186966	Al-Ali	Mar 2007	B2
7188621	DeVries et al.	Mar 2007	B2
7190261	Al-Ali	Mar 2007	B2
7208119	Kurtock et al.	Apr 2007	B1
7215984	Diab	May 2007	B2
7215986	Diab	May 2007	B2
7221971	Diab	May 2007	B2
7225006	Al-Ali et al.	May 2007	B2
7225007	Al-Ali	May 2007	B2
RE39672	Shehada et al.	Jun 2007	E
7229415	Schwartz	Jun 2007	B2
7239905	Kiani-Azarbayjany et al.	Jul 2007	B2
7241287	Shehada et al.	Jul 2007	B2
7244251	Shehada et al.	Jul 2007	B2
7245373	Soller et al.	Jul 2007	B2
7245953	Parker	Jul 2007	B1
7252659	Shehada et al.	Aug 2007	B2
7254429	Schurman et al.	Aug 2007	B2
7254431	Al-Ali	Aug 2007	B2
7254433	Diab et al.	Aug 2007	B2
7254434	Schulz et al.	Aug 2007	B2
7256708	Rosenfeld	Aug 2007	B2
7261691	Asomani	Aug 2007	B1
7261697	Berstein	Aug 2007	B2
7264616	Shehada et al.	Sep 2007	B2
7267671	Shehada et al.	Sep 2007	B2
7272425	Al-Ali	Sep 2007	B2
7274955	Kiani et al.	Sep 2007	B2
D554263	Al-Ali	Oct 2007	S
7280858	Al-Ali et al.	Oct 2007	B2
7285090	Stivoric et al.	Oct 2007	B2
7289835	Mansfield et al.	Oct 2007	B2
7292141	Staats et al.	Nov 2007	B2
7292883	De Felice et al.	Nov 2007	B2
7295866	Al-Ali	Nov 2007	B2
7307543	Rosenfeld	Dec 2007	B2
7313423	Griffin et al.	Dec 2007	B2
7314446	Byrd et al.	Jan 2008	B2
7315825	Rosenfeld	Jan 2008	B2
7321862	Rosenfeld	Jan 2008	B2
7322971	Shehada et al.	Jan 2008	B2
7327219	Lederer	Feb 2008	B2
7328053	Diab et al.	Feb 2008	B1
7332784	Mills et al.	Feb 2008	B2
7340287	Mason et al.	Mar 2008	B2
7341559	Schulz et al.	Mar 2008	B2
7343186	Lamego et al.	Mar 2008	B2
D566282	Al-Ali et al.	Apr 2008	S
7355512	Al-Ali	Apr 2008	B1
7356178	Ziel et al.	Apr 2008	B2
7356365	Schurman	Apr 2008	B2
7371981	Abdul-Hafiz	May 2008	B2
7373193	Al-Ali et al.	May 2008	B2
7373194	Weber et al.	May 2008	B2
7376453	Diab et al.	May 2008	B1
7377794	Al Ali et al.	May 2008	B2
7377899	Weber et al.	May 2008	B2
7378975	Smith et al.	May 2008	B1
7382247	Welch et al.	Jun 2008	B2
7383070	Diab et al.	Jun 2008	B2
7390299	Weiner et al.	Jun 2008	B2
7395158	Monfre et al.	Jul 2008	B2
7395216	Rosenfeld	Jul 2008	B2
7402338	Weintritt	Jul 2008	B2
7411509	Rosenfeld	Aug 2008	B2
7413546	Agutter et al.	Aug 2008	B2
7415297	Al-Ali et al.	Aug 2008	B2
7419483	Shehada	Sep 2008	B2
7428432	Ali et al.	Sep 2008	B2
7433827	Rosenfeld	Oct 2008	B2
7438683	Al-Ali et al.	Oct 2008	B2
7439856	Weiner et al.	Oct 2008	B2
7440787	Diab	Oct 2008	B2
7454240	Diab et al.	Nov 2008	B2
7454359	Rosenfeld	Nov 2008	B2
7454360	Rosenfeld	Nov 2008	B2
7462151	Childre et al.	Dec 2008	B2
7467002	Weber et al.	Dec 2008	B2
7467094	Rosenfeld	Dec 2008	B2
7469157	Diab et al.	Dec 2008	B2
7471969	Diab et al.	Dec 2008	B2
7471971	Diab et al.	Dec 2008	B2
7475019	Rosenfeld	Jan 2009	B2
7483729	Al-Ali et al.	Jan 2009	B2
7483730	Diab et al.	Jan 2009	B2
7489250	Bock et al.	Feb 2009	B2
7489958	Diab et al.	Feb 2009	B2
7496391	Diab et al.	Feb 2009	B2
7496393	Diab et al.	Feb 2009	B2
D587657	Al-Ali et al.	Mar 2009	S
7497828	Wilk et al.	Mar 2009	B1
7499741	Diab et al.	Mar 2009	B2
7499835	Weber et al.	Mar 2009	B2
7500950	Al-Ali et al.	Mar 2009	B2
7509154	Diab et al.	Mar 2009	B2
7509494	Al-Ali	Mar 2009	B2
7510849	Schurman et al.	Mar 2009	B2
7514725	Wojtczuk et al.	Apr 2009	B2
7515043	Welch et al.	Apr 2009	B2
7515044	Welch et al.	Apr 2009	B2
7519406	Blank et al.	Apr 2009	B2
7523044	Rosenblood	Apr 2009	B2
7526328	Diab et al.	Apr 2009	B2
D592507	Wachman et al.	May 2009	S
7530942	Diab	May 2009	B1
7530949	Al Ali et al.	May 2009	B2
7530955	Diab et al.	May 2009	B2
7532919	Soyemi et al.	May 2009	B2
7549961	Hwang	Jun 2009	B1
7551717	Tome et al.	Jun 2009	B2
7559520	Quijano et al.	Jul 2009	B2
7563110	Al-Ali et al.	Jul 2009	B2
7577475	Consentino et al.	Aug 2009	B2
7590950	Collins et al.	Sep 2009	B2
7593230	Abul-Haj et al.	Sep 2009	B2
7596398	Al-Ali et al.	Sep 2009	B2
7597665	Wilk et al.	Oct 2009	B2
7606608	Blank et al.	Oct 2009	B2
7612999	Clark et al.	Nov 2009	B2
7616303	Yang et al.	Nov 2009	B2
7618375	Flaherty	Nov 2009	B2
7620674	Ruchti et al.	Nov 2009	B2
D606659	Kiani et al.	Dec 2009	S
7629039	Eckerbom et al.	Dec 2009	B2
7639145	Lawson et al.	Dec 2009	B2
7640140	Ruchti et al.	Dec 2009	B2
7647083	Al-Ali et al.	Jan 2010	B2
7650291	Rosenfeld	Jan 2010	B2
D609193	Al-Ali et al.	Feb 2010	S
7654966	Westinskow et al.	Feb 2010	B2
7671733	McNeal et al.	Mar 2010	B2
7684845	Juan	Mar 2010	B2
7689437	Teller et al.	Mar 2010	B1
RE41236	Seely	Apr 2010	E
D614305	Al-Ali et al.	Apr 2010	S
7693697	Westinskow et al.	Apr 2010	B2
7697966	Monfre et al.	Apr 2010	B2
7698105	Ruchti et al.	Apr 2010	B2
RE41317	Parker	May 2010	E
RE41333	Blank et al.	May 2010	E
7722542	Lia et al.	May 2010	B2
7729733	Al-Ali et al.	Jun 2010	B2
7734320	Al-Ali	Jun 2010	B2
7736318	Consentino et al.	Jun 2010	B2
7740590	Bernstein	Jun 2010	B2
7749164	Davis	Jul 2010	B2
7761127	Al-Ali et al.	Jul 2010	B2
7761128	Al-Ali et al.	Jul 2010	B2
7763420	Strizker et al.	Jul 2010	B2
7764982	Dalke et al.	Jul 2010	B2
D621515	Chua et al.	Aug 2010	S
D621516	Kiani et al.	Aug 2010	S
7766818	Iketani et al.	Aug 2010	B2
7774060	Westenskow et al.	Aug 2010	B2
7778851	Schoenberg et al.	Aug 2010	B2
7791155	Diab	Sep 2010	B2
7794407	Rothenberg	Sep 2010	B2
7801581	Diab	Sep 2010	B2
7806830	Bernstein	Oct 2010	B2
7820184	Strizker et al.	Oct 2010	B2
7822452	Schurman et al.	Oct 2010	B2
RE41912	Parker	Nov 2010	E
7831450	Schoenberg	Nov 2010	B2
7841986	He et al.	Nov 2010	B2
7844313	Kiani et al.	Nov 2010	B2
7844314	Al-Ali	Nov 2010	B2
7844315	Al-Ali	Nov 2010	B2
7848935	Gotlib	Dec 2010	B2
7858322	Tymianski et al.	Dec 2010	B2
7865222	Weber et al.	Jan 2011	B2
7865232	Krishnaswamy et al.	Jan 2011	B1
7873497	Weber et al.	Jan 2011	B2
7880606	Al-Ali	Feb 2011	B2
7880626	Al-Ali et al.	Feb 2011	B2
7881892	Soyemi et al.	Feb 2011	B2
7884314	Hamada	Feb 2011	B2
7890156	Ooi et al.	Feb 2011	B2
7891355	Al-Ali et al.	Feb 2011	B2
7894868	Al-Ali et al.	Feb 2011	B2
7899507	Al-Ali et al.	Mar 2011	B2
7899518	Trepagnier et al.	Mar 2011	B2
7904132	Weber et al.	Mar 2011	B2
7909772	Popov et al.	Mar 2011	B2
7910875	Al-Ali	Mar 2011	B2
7914514	Calderon	Mar 2011	B2
7919713	Al-Ali et al.	Apr 2011	B2
7937128	Al-Ali	May 2011	B2
7937129	Mason et al.	May 2011	B2
7937130	Diab et al.	May 2011	B2
7941199	Kiani	May 2011	B2
7942844	Moberg et al.	May 2011	B2
7951086	Flaherty et al.	May 2011	B2
7957780	Lamego et al.	Jun 2011	B2
7962188	Kiani et al.	Jun 2011	B2
7962190	Diab et al.	Jun 2011	B1
7963927	Kelleher et al.	Jun 2011	B2
7967749	Hutchinson et al.	Jun 2011	B2
7976472	Kiani	Jul 2011	B2
7978062	LaLonde et al.	Jul 2011	B2
7988637	Diab	Aug 2011	B2
7988639	Starks	Aug 2011	B2
7990382	Kiani	Aug 2011	B2
7991446	Al-Ali et al.	Aug 2011	B2
7991463	Kelleher et al.	Aug 2011	B2
7991625	Rosenfeld	Aug 2011	B2
8000761	Al-Ali	Aug 2011	B2
8008088	Bellott et al.	Aug 2011	B2
RE42753	Kiani-Azarbayjany et al.	Sep 2011	E
8019400	Diab et al.	Sep 2011	B2
8027846	Schoenberg	Sep 2011	B2
8028701	Al-Ali et al.	Oct 2011	B2
8029765	Bellott et al.	Oct 2011	B2
8033996	Behar	Oct 2011	B2
8036727	Schurman et al.	Oct 2011	B2
8036728	Diab et al.	Oct 2011	B2
8036736	Snyder et al.	Oct 2011	B2
8038625	Afonso et al.	Oct 2011	B2
8046040	Ali et al.	Oct 2011	B2
8046041	Diab et al.	Oct 2011	B2
8046042	Diab et al.	Oct 2011	B2
8048040	Kiani	Nov 2011	B2
8050728	Al-Ali et al.	Nov 2011	B2
8068104	Rampersad	Nov 2011	B2
8073707	Teller et al.	Dec 2011	B2
8094013	Lee et al.	Jan 2012	B1
RE43169	Parker	Feb 2012	E
8118620	Al-Ali et al.	Feb 2012	B2
8126528	Diab et al.	Feb 2012	B2
8128572	Diab et al.	Mar 2012	B2
8130105	Al-Ali et al.	Mar 2012	B2
8145287	Diab et al.	Mar 2012	B2
8150487	Diab et al.	Apr 2012	B2
D659836	Bensch et al.	May 2012	S
8170887	Rosenfeld	May 2012	B2
8175672	Parker	May 2012	B2
8175895	Rosenfeld	May 2012	B2
8180420	Diab et al.	May 2012	B2
8180650	Graves et al.	May 2012	B2
8182443	Kiani	May 2012	B1
8185180	Diab et al.	May 2012	B2
8190223	Al-Ali et al.	May 2012	B2
8190227	Diab et al.	May 2012	B2
8200308	Zhang et al.	Jun 2012	B2
8203438	Kiani et al.	Jun 2012	B2
8203704	Merritt et al.	Jun 2012	B2
8204566	Schurman et al.	Jun 2012	B2
8206312	Farquhar	Jun 2012	B2
8214007	Baker et al.	Jul 2012	B2
8219172	Schurman et al.	Jul 2012	B2
8224411	Al-Ali et al.	Jul 2012	B2
8224667	Miller	Jul 2012	B1
8228181	Al-Ali	Jul 2012	B2
8229532	Davis	Jul 2012	B2
8229533	Diab et al.	Jul 2012	B2
8233955	Al-Ali et al.	Jul 2012	B2
8235907	Wilk et al.	Aug 2012	B2
8239780	Manetta et al.	Aug 2012	B2
8241213	Lynn et al.	Aug 2012	B2
8244325	Al-Ali et al.	Aug 2012	B2
8249815	Taylor	Aug 2012	B2
8255026	Al-Ali	Aug 2012	B1
8255027	Al-Ali et al.	Aug 2012	B2
8255028	Al-Ali et al.	Aug 2012	B2
8260577	Weber et al.	Sep 2012	B2
8265723	McHale et al.	Sep 2012	B1
8274360	Sampath et al.	Sep 2012	B2
8280473	Al-Ali	Oct 2012	B2
8294588	Fisher et al.	Oct 2012	B2
8294716	Lord et al.	Oct 2012	B2
8298153	Boute et al.	Oct 2012	B2
8301217	Al-Ali et al.	Oct 2012	B2
8306596	Schurman et al.	Nov 2012	B2
8310336	Muhsin et al.	Nov 2012	B2
8311747	Taylor	Nov 2012	B2
8311748	Taylor et al.	Nov 2012	B2
8315683	Al-Ali et al.	Nov 2012	B2
8315812	Taylor	Nov 2012	B2
8315813	Taylor et al.	Nov 2012	B2
8315814	Taylor et al.	Nov 2012	B2
8321150	Taylor	Nov 2012	B2
RE43860	Parker	Dec 2012	E
8326649	Rosenfeld	Dec 2012	B2
8327002	Van Dussen et al.	Dec 2012	B1
8328793	Birkenbach et al.	Dec 2012	B2
8337403	Al-Ali et al.	Dec 2012	B2
8346330	Lamego	Jan 2013	B2
8353842	Al-Ali et al.	Jan 2013	B2
8355766	MacNeish, III et al.	Jan 2013	B2
8359080	Diab et al.	Jan 2013	B2
8360936	Dibenedetto et al.	Jan 2013	B2
8364223	Al-Ali et al.	Jan 2013	B2
8364226	Diab et al.	Jan 2013	B2
8374665	Lamego	Feb 2013	B2
8385995	Al-Ali et al.	Feb 2013	B2
8385996	Smith et al.	Feb 2013	B2
D679018	Fullerton et al.	Mar 2013	S
8388353	Kiani	Mar 2013	B2
8399822	Al-Ali	Mar 2013	B2
8401602	Kiani	Mar 2013	B2
8401874	Rosenfeld	Mar 2013	B2
8405608	Al-Ali et al.	Mar 2013	B2
8414499	Al-Ali et al.	Apr 2013	B2
8418524	Al-Ali	Apr 2013	B2
8423106	Lamego et al.	Apr 2013	B2
8423378	Goldberg	Apr 2013	B1
8428967	Olsen et al.	Apr 2013	B2
8430817	Al-Ali et al.	Apr 2013	B1
8437825	Dalvi et al.	May 2013	B2
8455290	Siskavich	Jun 2013	B2
8457703	Al-Ali	Jun 2013	B2
8457707	Kiani	Jun 2013	B2
8463349	Diab et al.	Jun 2013	B2
8466286	Bellot et al.	Jun 2013	B2
8471713	Poeze et al.	Jun 2013	B2
8473020	Kiani et al.	Jun 2013	B2
8483787	Al-Ali et al.	Jul 2013	B2
8489167	Buxton et al.	Jul 2013	B2
8489364	Weber et al.	Jul 2013	B2
8498684	Weber et al.	Jul 2013	B2
8504128	Blank et al.	Aug 2013	B2
8509867	Workman et al.	Aug 2013	B2
8515509	Bruinsma et al.	Aug 2013	B2
8523781	Al-Ali	Sep 2013	B2
8529301	Al-Ali et al.	Sep 2013	B2
8532727	Ali et al.	Sep 2013	B2
8532728	Diab et al.	Sep 2013	B2
D692145	Al-Ali et al.	Oct 2013	S
8547209	Kiani et al.	Oct 2013	B2
8548548	Al-Ali	Oct 2013	B2
8548549	Schurman et al.	Oct 2013	B2
8548550	Al-Ali et al.	Oct 2013	B2
8560032	Al-Ali et al.	Oct 2013	B2
8560034	Diab et al.	Oct 2013	B1
8565847	Buxton et al.	Oct 2013	B2
8570167	Al-Ali	Oct 2013	B2
8570503	Vo et al.	Oct 2013	B2
8571617	Reichgott et al.	Oct 2013	B2
8571618	Lamego et al.	Oct 2013	B1
8571619	Al-Ali et al.	Oct 2013	B2
8577431	Lamego et al.	Nov 2013	B2
8578082	Medina et al.	Nov 2013	B2
8579813	Causey, III et al.	Nov 2013	B2
8581732	Al-Ali et al.	Nov 2013	B2
8584345	Al-Ali et al.	Nov 2013	B2
8588880	Abdul-Hafiz et al.	Nov 2013	B2
8588924	Dion	Nov 2013	B2
8597287	Benamou et al.	Dec 2013	B2
8600467	Al-Ali et al.	Dec 2013	B2
8600777	Schoenberg	Dec 2013	B2
8606342	Diab	Dec 2013	B2
8612260	Hasan et al.	Dec 2013	B2
8620678	Gotlib	Dec 2013	B2
8626255	Al-Ali et al.	Jan 2014	B2
8630691	Lamego et al.	Jan 2014	B2
8634889	Al-Ali et al.	Jan 2014	B2
8641631	Sierra et al.	Feb 2014	B2
8652060	Al-Ali	Feb 2014	B2
8655680	Bechtel et al.	Feb 2014	B2
8663107	Kiani	Mar 2014	B2
8666468	Al-Ali	Mar 2014	B1
8667967	Al-Ali et al.	Mar 2014	B2
8670811	O'Reilly	Mar 2014	B2
8670814	Diab et al.	Mar 2014	B2
8676286	Weber et al.	Mar 2014	B2
8682407	Al-Ali	Mar 2014	B2
RE44823	Parker	Apr 2014	E
RE44875	Kiani et al.	Apr 2014	E
8688183	Bruinsma et al.	Apr 2014	B2
8690771	Wekell et al.	Apr 2014	B2
8690799	Telfort et al.	Apr 2014	B2
8694331	DeBelser et al.	Apr 2014	B2
8700112	Kiani	Apr 2014	B2
8702627	Telfort et al.	Apr 2014	B2
8706179	Parker	Apr 2014	B2
8712494	MacNeish, III et al.	Apr 2014	B1
8715206	Telfort et al.	May 2014	B2
8717909	Shekhar et al.	May 2014	B1
8718735	Lamego et al.	May 2014	B2
8718737	Diab et al.	May 2014	B2
8718738	Blank et al.	May 2014	B2
8720249	Al-Ali	May 2014	B2
8721541	Al-Ali et al.	May 2014	B2
8721542	Al-Ali et al.	May 2014	B2
8723677	Kiani	May 2014	B1
8740792	Kiani et al.	Jun 2014	B1
8754776	Poeze et al.	Jun 2014	B2
8755535	Telfort et al.	Jun 2014	B2
8755856	Diab et al.	Jun 2014	B2
8755872	Marinow	Jun 2014	B1
8758020	Burdea et al.	Jun 2014	B2
8761850	Lamego	Jun 2014	B2
D709846	Oswaks	Jul 2014	S
8764671	Kiani	Jul 2014	B2
8768423	Shakespeare et al.	Jul 2014	B2
8771204	Telfort et al.	Jul 2014	B2
8777634	Kiani et al.	Jul 2014	B2
8781543	Diab et al.	Jul 2014	B2
8781544	Al-Ali et al.	Jul 2014	B2
8781549	Al-Ali et al.	Jul 2014	B2
8788003	Schurman et al.	Jul 2014	B2
8790268	Al-Ali	Jul 2014	B2
8792950	Larsen et al.	Jul 2014	B2
8801613	Al-Ali et al.	Aug 2014	B2
8818477	Soller	Aug 2014	B2
8821397	Al-Ali et al.	Sep 2014	B2
8821415	Al-Ali et al.	Sep 2014	B2
8830054	Weiss	Sep 2014	B2
8830449	Lamego et al.	Sep 2014	B1
8831700	Schurman et al.	Sep 2014	B2
8840549	Al-Ali et al.	Sep 2014	B2
8847740	Kiani et al.	Sep 2014	B2
8849365	Smith et al.	Sep 2014	B2
8852094	Al-Ali et al.	Oct 2014	B2
8852994	Wojtczuk et al.	Oct 2014	B2
8866620	Amir	Oct 2014	B2
8868147	Stippick et al.	Oct 2014	B2
8868150	Al-Ali et al.	Oct 2014	B2
8870792	Al-Ali et al.	Oct 2014	B2
8873035	Yang et al.	Oct 2014	B2
8878888	Rosenfeld	Nov 2014	B2
8886271	Kiani et al.	Nov 2014	B2
8888539	Al-Ali et al.	Nov 2014	B2
8888708	Diab et al.	Nov 2014	B2
8892180	Weber et al.	Nov 2014	B2
8897847	Al-Ali	Nov 2014	B2
8907287	Vanderpohl	Dec 2014	B2
8909310	Lamego et al.	Dec 2014	B2
8909330	McCombie et al.	Dec 2014	B2
8911377	Al-Ali	Dec 2014	B2
8912909	Al-Ali et al.	Dec 2014	B2
8920317	Al-Ali et al.	Dec 2014	B2
8921699	Al-Ali et al.	Dec 2014	B2
8922382	Al-Ali et al.	Dec 2014	B2
8929964	Al-Ali et al.	Jan 2015	B2
8942777	Diab et al.	Jan 2015	B2
8948834	Diab et al.	Feb 2015	B2
8948835	Diab	Feb 2015	B2
8951248	Messerly et al.	Feb 2015	B2
8956292	Wekell et al.	Feb 2015	B2
8956294	McCombie et al.	Feb 2015	B2
8965471	Lamego	Feb 2015	B2
8983564	Al-Ali	Mar 2015	B2
8989831	Al-Ali et al.	Mar 2015	B2
8996085	Kiani et al.	Mar 2015	B2
8998809	Kiani	Apr 2015	B2
8998830	Halperin et al.	Apr 2015	B2
9028429	Telfort et al.	May 2015	B2
9037207	Al-Ali et al.	May 2015	B2
9041530	Sprigg et al.	May 2015	B2
9057689	Soller	Jun 2015	B2
9058635	Rybkin	Jun 2015	B1
9060721	Reichgott et al.	Jun 2015	B2
9066666	Kiani	Jun 2015	B2
9066680	Al-Ali et al.	Jun 2015	B1
9072474	Al-Ali et al.	Jul 2015	B2
9078560	Schurman et al.	Jul 2015	B2
9084569	Weber et al.	Jul 2015	B2
9095291	Soller	Aug 2015	B2
9095316	Welch et al.	Aug 2015	B2
9104789	Gross et al.	Aug 2015	B2
9106038	Telfort et al.	Aug 2015	B2
9107625	Telfort et al.	Aug 2015	B2
9107626	Al-Ali et al.	Aug 2015	B2
9113831	Al-Ali	Aug 2015	B2
9113832	Al-Ali	Aug 2015	B2
9119595	Lamego	Sep 2015	B2
9125578	Grunwald	Sep 2015	B2
9131881	Diab et al.	Sep 2015	B2
9131882	Al-Ali et al.	Sep 2015	B2
9131883	Al-Ali	Sep 2015	B2
9131917	Telfort et al.	Sep 2015	B2
9138180	Coverston et al.	Sep 2015	B1
9138182	Al-Ali et al.	Sep 2015	B2
9138192	Weber et al.	Sep 2015	B2
9142117	Muhsin et al.	Sep 2015	B2
9153112	Kiani et al.	Oct 2015	B1
9153121	Kiani et al.	Oct 2015	B2
9161696	Al-Ali et al.	Oct 2015	B2
9161713	Al-Ali et al.	Oct 2015	B2
9167995	Lamego et al.	Oct 2015	B2
9176141	Al-Ali et al.	Nov 2015	B2
9186102	Bruinsma et al.	Nov 2015	B2
9192312	Al-Ali	Nov 2015	B2
9192329	Al-Ali	Nov 2015	B2
9192351	Telfort et al.	Nov 2015	B1
9195385	Al-Ali et al.	Nov 2015	B2
D745167	Canas et al.	Dec 2015	S
9211072	Kiani	Dec 2015	B2
9211095	Al-Ali	Dec 2015	B1
9218454	Kiani et al.	Dec 2015	B2
9226696	Kiani	Jan 2016	B2
9241662	Al-Ali et al.	Jan 2016	B2
9245668	Vo et al.	Jan 2016	B1
9259185	Abdul-Hafiz et al.	Feb 2016	B2
9262586	Steiger et al.	Feb 2016	B2
9267572	Barker et al.	Feb 2016	B2
9277880	Poeze et al.	Mar 2016	B2
9289167	Diab et al.	Mar 2016	B2
9295421	Kiani et al.	Mar 2016	B2
9307928	Al-Ali et al.	Apr 2016	B1
9323894	Kiani	Apr 2016	B2
D755392	Hwang et al.	May 2016	S
9326712	Kiani	May 2016	B1
9333316	Kiani	May 2016	B2
9339220	Lamego et al.	May 2016	B2
9341565	Lamego et al.	May 2016	B2
9351673	Diab et al.	May 2016	B2
9351675	Al-Ali et al.	May 2016	B2
9364181	Kiani et al.	Jun 2016	B2
9368671	Wojtczuk et al.	Jun 2016	B2
9370325	Al-Ali et al.	Jun 2016	B2
9370326	McHale et al.	Jun 2016	B2
9370335	Al-ali et al.	Jun 2016	B2
9375185	Ali et al.	Jun 2016	B2
9384652	Gilham et al.	Jul 2016	B2
9386953	Al-Ali	Jul 2016	B2
9386961	Al-Ali et al.	Jul 2016	B2
9392945	Al-Ali et al.	Jul 2016	B2
9397448	Al-Ali et al.	Jul 2016	B2
9408542	Kinast et al.	Aug 2016	B1
9436645	Al-Ali et al.	Sep 2016	B2
9445759	Lamego et al.	Sep 2016	B1
9466919	Kiani et al.	Oct 2016	B2
9474474	Lamego et al.	Oct 2016	B2
9480422	Al-Ali	Nov 2016	B2
9480435	Olsen	Nov 2016	B2
9492110	Al-Ali et al.	Nov 2016	B2
9510779	Poeze et al.	Dec 2016	B2
9517024	Kiani et al.	Dec 2016	B2
9529762	Gisler et al.	Dec 2016	B2
9532722	Lamego et al.	Jan 2017	B2
9538949	Al-Ali et al.	Jan 2017	B2
9538980	Telfort et al.	Jan 2017	B2
9549696	Lamego et al.	Jan 2017	B2
9554737	Schurman et al.	Jan 2017	B2
9560996	Kiani	Feb 2017	B2
9560998	Al-Ali et al.	Feb 2017	B2
9566019	Al-Ali et al.	Feb 2017	B2
9579039	Jansen et al.	Feb 2017	B2
9591975	Dalvi et al.	Mar 2017	B2
9622692	Lamego et al.	Apr 2017	B2
9622693	Diab	Apr 2017	B2
D788312	Al-Ali et al.	May 2017	S
9636055	Al-Ali et al.	May 2017	B2
9636056	Al-Ali	May 2017	B2
9649054	Lamego et al.	May 2017	B2
9662052	Al-Ali et al.	May 2017	B2
9668679	Schurman et al.	Jun 2017	B2
9668680	Bruinsma et al.	Jun 2017	B2
9668703	Al-Ali	Jun 2017	B2
9675286	Diab	Jun 2017	B2
9687160	Kiani	Jun 2017	B2
9693719	Al-Ali et al.	Jul 2017	B2
9693737	Al-Ali	Jul 2017	B2
9697928	Al-Ali et al.	Jul 2017	B2
9717425	Kiani et al.	Aug 2017	B2
9717458	Lamego et al.	Aug 2017	B2
9724016	Al-Ali et al.	Aug 2017	B1
9724024	Al-Ali	Aug 2017	B2
9724025	Kiani et al.	Aug 2017	B1
9730640	Diab et al.	Aug 2017	B2
9743887	Al-Ali et al.	Aug 2017	B2
9749232	Sampath et al.	Aug 2017	B2
9750442	Olsen	Sep 2017	B2
9750443	Smith et al.	Sep 2017	B2
9750461	Telfort	Sep 2017	B1
9775545	Al-Ali et al.	Oct 2017	B2
9775546	Diab et al.	Oct 2017	B2
9775570	Al-Ali	Oct 2017	B2
9778079	Al-Ali et al.	Oct 2017	B1
9782077	Lamego et al.	Oct 2017	B2
9782110	Kiani	Oct 2017	B2
9787568	Lamego et al.	Oct 2017	B2
9788735	Al-Ali	Oct 2017	B2
9788768	Al-Ali et al.	Oct 2017	B2
9795300	Al-Ali	Oct 2017	B2
9795310	Al-Ali	Oct 2017	B2
9795358	Telfort et al.	Oct 2017	B2
9795739	Al-Ali et al.	Oct 2017	B2
9801556	Kiani	Oct 2017	B2
9801588	Weber et al.	Oct 2017	B2
9808188	Perea et al.	Nov 2017	B1
9814418	Weber et al.	Nov 2017	B2
9820691	Kiani	Nov 2017	B2
9833152	Kiani et al.	Dec 2017	B2
9833180	Shakespeare et al.	Dec 2017	B2
9839379	Al-Ali et al.	Dec 2017	B2
9839381	Weber et al.	Dec 2017	B1
9847002	Kiani et al.	Dec 2017	B2
9847749	Kiani et al.	Dec 2017	B2
9848800	Lee et al.	Dec 2017	B1
9848806	Al-Ali et al.	Dec 2017	B2
9848807	Lamego	Dec 2017	B2
9861298	Eckerbom et al.	Jan 2018	B2
9861304	Al-Ali et al.	Jan 2018	B2
9861305	Weber et al.	Jan 2018	B1
9867578	Al-Ali et al.	Jan 2018	B2
9872623	Al-Ali	Jan 2018	B2
9876320	Coverston et al.	Jan 2018	B2
9877650	Muhsin et al.	Jan 2018	B2
9877686	Al-Ali et al.	Jan 2018	B2
9891079	Dalvi	Feb 2018	B2
9895107	Al-Ali et al.	Feb 2018	B2
9924897	Abdul-Hafiz	Mar 2018	B1
9936917	Poeze et al.	Apr 2018	B2
9955937	Telfort	May 2018	B2
9965946	Al-Ali et al.	May 2018	B2
D820865	Muhsin et al.	Jun 2018	S
9986952	Dalvi et al.	Jun 2018	B2
D822215	Al-Ali et al.	Jul 2018	S
D822216	Barker et al.	Jul 2018	S
10010276	Al-Ali et al.	Jul 2018	B2
10086138	Novak, Jr.	Oct 2018	B1
10111591	Dyell et al.	Oct 2018	B2
D833624	DeJong et al.	Nov 2018	S
10123729	Dyell et al.	Nov 2018	B2
D835282	Barker et al.	Dec 2018	S
D835283	Barker et al.	Dec 2018	S
D835284	Barker et al.	Dec 2018	S
D835285	Barker et al.	Dec 2018	S
10149616	Al-Ali et al.	Dec 2018	B2
10154815	Al-Ali et al.	Dec 2018	B2
10159412	Lamego et al.	Dec 2018	B2
10188348	Kiani et al.	Jan 2019	B2
RE47218	Ali-Ali	Feb 2019	E
RE47244	Kiani et al.	Feb 2019	E
RE47249	Kiani et al.	Feb 2019	E
10205291	Scruggs et al.	Feb 2019	B2
10226187	Al-Ali et al.	Mar 2019	B2
10231657	Al-Ali et al.	Mar 2019	B2
10231670	Blank et al.	Mar 2019	B2
RE47353	Kiani et al.	Apr 2019	E
10279247	Kiani	May 2019	B2
10292664	Al-Ali	May 2019	B2
10299720	Brown et al.	May 2019	B2
10327337	Triman et al.	Jun 2019	B2
10327713	Barker et al.	Jun 2019	B2
10332630	Al-Ali	Jun 2019	B2
10383520	Wojitczuk et al.	Aug 2019	B2
10383527	Al-Ali	Aug 2019	B2
10388120	Muhsin et al.	Aug 2019	B2
D864120	Forrest et al.	Oct 2019	S
10441181	Telfort et al.	Oct 2019	B1
10441196	Eckerbom et al.	Oct 2019	B2
10448844	Al-Ali et al.	Oct 2019	B2
10448871	Al-Ali	Oct 2019	B2
10456038	Lamego et al.	Oct 2019	B2
10463340	Telfort et al.	Nov 2019	B2
10471159	Lapotko et al.	Nov 2019	B1
10505311	Al-Ali et al.	Dec 2019	B2
10524738	Olsen	Jan 2020	B2
10532174	Al-Ali	Jan 2020	B2
10537285	Sherim et al.	Jan 2020	B2
10542903	Al-Ali et al.	Jan 2020	B2
10555678	Dalvi et al.	Feb 2020	B2
10568553	O'Neil et al.	Feb 2020	B2
RE47882	Al-Ali	Mar 2020	E
10608817	Haider et al.	Mar 2020	B2
D880477	Forrest et al.	Apr 2020	S
10617302	Al-Ali et al.	Apr 2020	B2
10617335	Al-Ali et al.	Apr 2020	B2
10637181	Al-Ali et al.	Apr 2020	B2
D886849	Muhsin et al.	Jun 2020	S
D887548	Abdul-Hafiz et al.	Jun 2020	S
D887549	Abdul-Hafiz et al.	Jun 2020	S
10667764	Ahmed et al.	Jun 2020	B2
D890708	Forrest et al.	Jul 2020	S
10721785	Al-Ali	Jul 2020	B2
10736518	Al-Ali et al.	Aug 2020	B2
10750984	Pauley et al.	Aug 2020	B2
D897098	Al-Ali	Sep 2020	S
10779098	Iswanto et al.	Sep 2020	B2
10827961	Iyengar et al.	Nov 2020	B1
10828007	Telfort et al.	Nov 2020	B1
10832818	Muhsin et al.	Nov 2020	B2
10833983	Sampath et al.	Nov 2020	B2
10849554	Shreim et al.	Dec 2020	B2
10856750	Indorf	Dec 2020	B2
D906970	Forrest et al.	Jan 2021	S
D908213	Abdul-Hafiz et al.	Jan 2021	S
10918281	Al-Ali et al.	Feb 2021	B2
10932705	Muhsin et al.	Mar 2021	B2
10932729	Kiani et al.	Mar 2021	B2
10939878	Kiani et al.	Mar 2021	B2
10956950	Al-Ali et al.	Mar 2021	B2
D916135	Indorf et al.	Apr 2021	S
D917046	Abdul-Hafiz et al.	Apr 2021	S
D917550	Indorf et al.	Apr 2021	S
D917564	Indorf et al.	Apr 2021	S
D917704	Al-Ali et al.	Apr 2021	S
10987066	Chandran et al.	Apr 2021	B2
10991135	Al-Ali et al.	Apr 2021	B2
D919094	Al-Ali et al.	May 2021	S
D919100	Al-Ali et al.	May 2021	S
11006867	Al-Ali	May 2021	B2
D921202	Al-Ali et al.	Jun 2021	S
11024064	Muhsin et al.	Jun 2021	B2
11026604	Chen et al.	Jun 2021	B2
D925597	Chandran et al.	Jul 2021	S
D927699	Al-Ali et al.	Aug 2021	S
11076777	Lee et al.	Aug 2021	B2
11114188	Poeze et al.	Sep 2021	B2
D933232	Al-Ali et al.	Oct 2021	S
D933233	Al-Ali et al.	Oct 2021	S
D933234	Al-Ali et al.	Oct 2021	S
11145408	Sampath et al.	Oct 2021	B2
11147518	Al-Ali et al.	Oct 2021	B1
11185262	Al-Ali et al.	Nov 2021	B2
11191484	Kiani et al.	Dec 2021	B2
D946596	Ahmed	Mar 2022	S
D946597	Ahmed	Mar 2022	S
D946598	Ahmed	Mar 2022	S
D946617	Ahmed	Mar 2022	S
11272839	Al-Ali et al.	Mar 2022	B2
11289199	Al-Ali	Mar 2022	B2
RE49034	Al-Ali	Apr 2022	E
11298021	Muhsin et al.	Apr 2022	B2
D950580	Ahmed	May 2022	S
D950599	Ahmed	May 2022	S
D950738	Al-Ali et al.	May 2022	S
D957648	Al-Ali	Jul 2022	S
11382567	O'Brien et al.	Jul 2022	B2
11389093	Triman et al.	Jul 2022	B2
11406286	Al-Ali et al.	Aug 2022	B2
11417426	Muhsin et al.	Aug 2022	B2
11439329	Lamego	Sep 2022	B2
11445948	Scruggs et al.	Sep 2022	B2
D965789	Al-Ali et al.	Oct 2022	S
D967433	Al-Ali et al.	Oct 2022	S
11464410	Muhsin	Oct 2022	B2
11504058	Sharma et al.	Nov 2022	B1
11504066	Dalvi et al.	Nov 2022	B1
D971933	Ahmed	Dec 2022	S
D973072	Ahmed	Dec 2022	S
D973685	Ahmed	Dec 2022	S
D973686	Ahmed	Dec 2022	S
D974193	Forrest et al.	Jan 2023	S
D979516	Al-Ali et al.	Feb 2023	S
D980091	Forrest et al.	Mar 2023	S
11596363	Lamego	Mar 2023	B2
11627919	Kiani et al.	Apr 2023	B2
11637437	Al-Ali et al.	Apr 2023	B2
D985498	Al-Ali et al.	May 2023	S
11653862	Dalvi et al.	May 2023	B2
D989112	Muhsin et al.	Jun 2023	S
11678829	Al-Ali et al.	Jun 2023	B2
11692934	Normand et al.	Jul 2023	B2
20010011355	Kawai	Aug 2001	A1
20010031922	Weng et al.	Oct 2001	A1
20010034477	Mansfield et al.	Oct 2001	A1
20010039483	Brand et al.	Nov 2001	A1
20010046366	Susskind	Nov 2001	A1
20010051765	Walker et al.	Dec 2001	A1
20020010401	Bushmakin et al.	Jan 2002	A1
20020038392	De La Huerga	Mar 2002	A1
20020045836	Alkawwas	Apr 2002	A1
20020052311	Solomon et al.	May 2002	A1
20020058864	Mansfield et al.	May 2002	A1
20020062230	Morag et al.	May 2002	A1
20020063690	Chung et al.	May 2002	A1
20020099275	Schmidt et al.	Jul 2002	A1
20020133080	Apruzzese et al.	Sep 2002	A1
20020140675	Ali et al.	Oct 2002	A1
20020177758	Schoenberg	Nov 2002	A1
20020198445	Dominguez et al.	Dec 2002	A1
20030013975	Kiani	Jan 2003	A1
20030018243	Gerhardt et al.	Jan 2003	A1
20030027326	Ulmsten et al.	Feb 2003	A1
20030036683	Kehr et al.	Feb 2003	A1
20030052787	Zerhusen et al.	Mar 2003	A1
20030058838	Wengrovitz	Mar 2003	A1
20030144582	Cohen et al.	Jul 2003	A1
20030149598	Santoso et al.	Aug 2003	A1
20030156288	Barnum et al.	Aug 2003	A1
20030158466	Lynn et al.	Aug 2003	A1
20030172940	Rogers et al.	Sep 2003	A1
20030212312	Coffin, IV et al.	Nov 2003	A1
20030216670	Beggs	Nov 2003	A1
20040013647	Solomon et al.	Jan 2004	A1
20040059599	McIvor	Mar 2004	A1
20040106163	Workman, Jr. et al.	Jun 2004	A1
20040122787	Avinash et al.	Jun 2004	A1
20040126007	Ziel et al.	Jul 2004	A1
20040139571	Chang et al.	Jul 2004	A1
20040147818	Levy et al.	Jul 2004	A1
20040172222	Simpson et al.	Sep 2004	A1
20040172302	Martucci et al.	Sep 2004	A1
20040186357	Soderberg et al.	Sep 2004	A1
20040230118	Shehada et al.	Nov 2004	A1
20040230132	Shehada et al.	Nov 2004	A1
20040230179	Shehada et al.	Nov 2004	A1
20040243017	Causevic	Dec 2004	A1
20040249670	Noguchi et al.	Dec 2004	A1
20040254431	Shehada et al.	Dec 2004	A1
20040254432	Shehada et al.	Dec 2004	A1
20040267103	Li et al.	Dec 2004	A1
20050020918	Wilk et al.	Jan 2005	A1
20050038332	Saidara et al.	Feb 2005	A1
20050038680	McMahon	Feb 2005	A1
20050055242	Bello et al.	Mar 2005	A1
20050055244	Mullan et al.	Mar 2005	A1
20050055276	Kiani et al.	Mar 2005	A1
20050080336	Byrd et al.	Apr 2005	A1
20050096542	Weng et al.	May 2005	A1
20050113653	Fox et al.	May 2005	A1
20050124864	Mack et al.	Jun 2005	A1
20050125256	Schoenberg	Jun 2005	A1
20050143671	Hastings et al.	Jun 2005	A1
20050146431	Hastings et al.	Jul 2005	A1
20050148890	Hastings	Jul 2005	A1
20050164933	Tymianski et al.	Jul 2005	A1
20050190747	Sindhwani et al.	Sep 2005	A1
20050191294	Arap et al.	Sep 2005	A1
20050203775	Achan	Sep 2005	A1
20050234317	Kiani	Oct 2005	A1
20050268401	Dixon et al.	Dec 2005	A1
20050277872	Colby, Jr. et al.	Dec 2005	A1
20060049936	Collins, Jr. et al.	Mar 2006	A1
20060058647	Strommer et al.	Mar 2006	A1
20060073719	Kiani	Apr 2006	A1
20060089543	Kim et al.	Apr 2006	A1
20060094936	Russ	May 2006	A1
20060149393	Calderon	Jul 2006	A1
20060155175	Ogino et al.	Jul 2006	A1
20060161054	Reuss et al.	Jul 2006	A1
20060169773	Lyons et al.	Aug 2006	A1
20060189871	Al-Ali et al.	Aug 2006	A1
20060190833	SanGiovanni et al.	Aug 2006	A1
20060200009	Wekell et al.	Sep 2006	A1
20060217684	Shehada et al.	Sep 2006	A1
20060217685	Shehada et al.	Sep 2006	A1
20060224413	Kim et al.	Oct 2006	A1
20060235300	Weng et al.	Oct 2006	A1
20060253042	Stahmann et al.	Nov 2006	A1
20070000490	DeVries et al.	Jan 2007	A1
20070002533	Kogan et al.	Jan 2007	A1
20070021675	Childre et al.	Jan 2007	A1
20070027368	Collins et al.	Feb 2007	A1
20070032733	Burton et al.	Feb 2007	A1
20070055116	Clark et al.	Mar 2007	A1
20070055544	Jung et al.	Mar 2007	A1
20070060798	Krupnik et al.	Mar 2007	A1
20070073116	Kiani et al.	Mar 2007	A1
20070073555	Buist	Mar 2007	A1
20070088406	Bennett et al.	Apr 2007	A1
20070096897	Weiner	May 2007	A1
20070100222	Mastrototaro et al.	May 2007	A1
20070118399	Avinash et al.	May 2007	A1
20070140475	Kurtock et al.	Jun 2007	A1
20070156033	Causey et al.	Jul 2007	A1
20070157285	Frank et al.	Jul 2007	A1
20070159332	Koblasz	Jul 2007	A1
20070163589	DeVries et al.	Jul 2007	A1
20070180140	Welch et al.	Aug 2007	A1
20070185390	Perkins et al.	Aug 2007	A1
20070185739	Ober et al.	Aug 2007	A1
20070192140	Gropper	Aug 2007	A1
20070213600	John et al.	Sep 2007	A1
20070232941	Rabinovich	Oct 2007	A1
20070244377	Cozad et al.	Oct 2007	A1
20070244724	Pendergast et al.	Oct 2007	A1
20070254593	Jollota et al.	Nov 2007	A1
20070255114	Ackermann et al.	Nov 2007	A1
20070255116	Mehta et al.	Nov 2007	A1
20070255250	Moberg et al.	Nov 2007	A1
20070282478	Al-Ali et al.	Dec 2007	A1
20080000479	Elaz et al.	Jan 2008	A1
20080001735	Tran	Jan 2008	A1
20080003200	Arap et al.	Jan 2008	A1
20080015903	Rodgers	Jan 2008	A1
20080021854	Jung et al.	Jan 2008	A1
20080033661	Syroid et al.	Feb 2008	A1
20080039701	Ali et al.	Feb 2008	A1
20080053438	DeVries et al.	Mar 2008	A1
20080058657	Schwartz et al.	Mar 2008	A1
20080064965	Jay et al.	Mar 2008	A1
20080090626	Griffin et al.	Apr 2008	A1
20080091089	Guillory et al.	Apr 2008	A1
20080091090	Guillory et al.	Apr 2008	A1
20080091471	Michon et al.	Apr 2008	A1
20080094228	Welch et al.	Apr 2008	A1
20080097167	Yudkovitch et al.	Apr 2008	A1
20080099366	Niemiec et al.	May 2008	A1
20080119412	Tymianski et al.	May 2008	A1
20080138278	Scherz et al.	Jun 2008	A1
20080169922	Issokson	Jul 2008	A1
20080171919	Stivoric et al.	Jul 2008	A1
20080188795	Katz et al.	Aug 2008	A1
20080194918	Kulik et al.	Aug 2008	A1
20080201174	Ramasubramanian et al.	Aug 2008	A1
20080208912	Garibaldi	Aug 2008	A1
20080221396	Garces et al.	Sep 2008	A1
20080221418	Al-Ali et al.	Sep 2008	A1
20080228077	Wilk et al.	Sep 2008	A1
20080249804	Kim	Oct 2008	A1
20080275309	Stivoric et al.	Nov 2008	A1
20080281167	Soderberg et al.	Nov 2008	A1
20080281168	Gibson et al.	Nov 2008	A1
20080281181	Manzione et al.	Nov 2008	A1
20080287751	Stivoric et al.	Nov 2008	A1
20080292172	Assmann et al.	Nov 2008	A1
20080300020	Nishizawa et al.	Dec 2008	A1
20080319275	Chiu et al.	Dec 2008	A1
20080319354	Bell et al.	Dec 2008	A1
20090005651	Ward et al.	Jan 2009	A1
20090018808	Bronstein et al.	Jan 2009	A1
20090024008	Brunner et al.	Jan 2009	A1
20090036759	Ault et al.	Feb 2009	A1
20090043172	Zagorchev et al.	Feb 2009	A1
20090046837	Thiel	Feb 2009	A1
20090052623	Tome et al.	Feb 2009	A1
20090054735	Higgins et al.	Feb 2009	A1
20090054743	Wekell et al.	Feb 2009	A1
20090062682	Bland et al.	Mar 2009	A1
20090069642	Gao et al.	Mar 2009	A1
20090093687	Telfort et al.	Apr 2009	A1
20090095926	MacNeish, III	Apr 2009	A1
20090099480	Salgo et al.	Apr 2009	A1
20090119330	Sampath et al.	May 2009	A1
20090119843	Rodgers et al.	May 2009	A1
20090124867	Hirsch et al.	May 2009	A1
20090131759	Sims et al.	May 2009	A1
20090143832	Saba	Jun 2009	A1
20090146822	Soliman	Jun 2009	A1
20090157058	Ferren et al.	Jun 2009	A1
20090164236	Gounares	Jun 2009	A1
20090171170	Li et al.	Jul 2009	A1
20090171225	Gadodia et al.	Jul 2009	A1
20090177090	Grunwald et al.	Jul 2009	A1
20090182287	Kassab	Jul 2009	A1
20090204977	Tavares et al.	Aug 2009	A1
20090221880	Soderberg et al.	Sep 2009	A1
20090226372	Ruoslahti et al.	Sep 2009	A1
20090247984	Lamego et al.	Oct 2009	A1
20090264778	Markowitz et al.	Oct 2009	A1
20090275813	Davis	Nov 2009	A1
20090275844	Al-Ali	Nov 2009	A1
20090281462	Heliot et al.	Nov 2009	A1
20090299157	Telfort et al.	Dec 2009	A1
20090309755	Williamson	Dec 2009	A1
20090322540	Richardson et al.	Dec 2009	A1
20100004518	Vo et al.	Jan 2010	A1
20100030040	Poeze et al.	Feb 2010	A1
20100030094	Lundback	Feb 2010	A1
20100036209	Ferren et al.	Feb 2010	A1
20100069725	Al-Ali	Mar 2010	A1
20100088120	Gonzalvo	Apr 2010	A1
20100088121	Shih et al.	Apr 2010	A1
20100099964	O'Reilly et al.	Apr 2010	A1
20100125217	Kuo et al.	May 2010	A1
20100144627	Vitek et al.	Jun 2010	A1
20100185101	Sakai et al.	Jul 2010	A1
20100188230	Lindsay	Jul 2010	A1
20100198622	Gajic et al.	Aug 2010	A1
20100210958	Manwaring et al.	Aug 2010	A1
20100234718	Sampath et al.	Sep 2010	A1
20100270257	Wachman et al.	Oct 2010	A1
20100298650	Moon et al.	Nov 2010	A1
20100298659	McCombie et al.	Nov 2010	A1
20100298661	McCombie et al.	Nov 2010	A1
20100298742	Perlman et al.	Nov 2010	A1
20100305412	Darrah et al.	Dec 2010	A1
20100312103	Gorek et al.	Dec 2010	A1
20100317936	Al-Ali et al.	Dec 2010	A1
20100317951	Rutkowski et al.	Dec 2010	A1
20110001605	Kiani et al.	Jan 2011	A1
20110021930	Mazzeo et al.	Jan 2011	A1
20110023130	Gudgel et al.	Jan 2011	A1
20110028806	Merritt et al.	Feb 2011	A1
20110028809	Goodman	Feb 2011	A1
20110040197	Welch et al.	Feb 2011	A1
20110046495	Osypka	Feb 2011	A1
20110066051	Moon et al.	Mar 2011	A1
20110077473	Lisogurski	Mar 2011	A1
20110077488	Buxton et al.	Mar 2011	A1
20110078596	Rawlins et al.	Mar 2011	A1
20110080294	Tanishima et al.	Apr 2011	A1
20110082711	Poeze et al.	Apr 2011	A1
20110087081	Kiani et al.	Apr 2011	A1
20110087083	Poeze et al.	Apr 2011	A1
20110087084	Jeong et al.	Apr 2011	A1
20110087117	Tremper et al.	Apr 2011	A1
20110087756	Biondi	Apr 2011	A1
20110098583	Pandia et al.	Apr 2011	A1
20110105854	Kiani et al.	May 2011	A1
20110105956	Hirth	May 2011	A1
20110106561	Eaton, Jr. et al.	May 2011	A1
20110106565	Compton et al.	May 2011	A1
20110117878	Barash et al.	May 2011	A1
20110118561	Tari et al.	May 2011	A1
20110118573	Mckenna	May 2011	A1
20110125060	Telfort et al.	May 2011	A1
20110130636	Daniel et al.	Jun 2011	A1
20110137297	Kiani et al.	Jun 2011	A1
20110140896	Menzel	Jun 2011	A1
20110152629	Eaton et al.	Jun 2011	A1
20110166465	Clements et al.	Jul 2011	A1
20110167133	Jain	Jul 2011	A1
20110172498	Olsen et al.	Jul 2011	A1
20110172967	Al-Ali et al.	Jul 2011	A1
20110178373	Pacey et al.	Jul 2011	A1
20110184252	Archer et al.	Jul 2011	A1
20110184253	Archer et al.	Jul 2011	A1
20110208015	Welch et al.	Aug 2011	A1
20110208018	Kiani	Aug 2011	A1
20110208073	Matsukawa et al.	Aug 2011	A1
20110209915	Telfort et al.	Sep 2011	A1
20110212090	Pedersen et al.	Sep 2011	A1
20110213210	Temby et al.	Sep 2011	A1
20110213212	Al-Ali	Sep 2011	A1
20110227739	Gilham et al.	Sep 2011	A1
20110230733	Al-Ali	Sep 2011	A1
20110237911	Lamego et al.	Sep 2011	A1
20110237969	Eckerbom et al.	Sep 2011	A1
20110245707	Castle	Oct 2011	A1
20110257544	Kaasinen et al.	Oct 2011	A1
20110263950	Larson et al.	Oct 2011	A1
20110288383	Diab	Nov 2011	A1
20110295094	Doyle et al.	Dec 2011	A1
20110301444	Al-Ali	Dec 2011	A1
20120002791	Kraus et al.	Jan 2012	A1
20120004579	Luo et al.	Jan 2012	A1
20120025992	Tallent et al.	Feb 2012	A1
20120029300	Paquet	Feb 2012	A1
20120029304	Medina et al.	Feb 2012	A1
20120029879	Sing et al.	Feb 2012	A1
20120041316	Al-Ali et al.	Feb 2012	A1
20120041783	McKee	Feb 2012	A1
20120046557	Kiani	Feb 2012	A1
20120059230	Teller et al.	Mar 2012	A1
20120059267	Lamego et al.	Mar 2012	A1
20120071771	Behar	Mar 2012	A1
20120075464	Derenne et al.	Mar 2012	A1
20120088984	Al-Ali et al.	Apr 2012	A1
20120095778	Gross et al.	Apr 2012	A1
20120101353	Reggiardo et al.	Apr 2012	A1
20120112903	Kaib et al.	May 2012	A1
20120116175	Al-Ali et al.	May 2012	A1
20120123231	O'Reilly	May 2012	A1
20120123799	Nolen et al.	May 2012	A1
20120134257	Knox	May 2012	A1
20120136221	Killen et al.	May 2012	A1
20120165629	Merritt et al.	Jun 2012	A1
20120179006	Jansen et al.	Jul 2012	A1
20120184120	Basta et al.	Jul 2012	A1
20120197619	Namer Yelin et al.	Aug 2012	A1
20120203078	Sze et al.	Aug 2012	A1
20120209082	Al-Ali	Aug 2012	A1
20120209084	Olsen et al.	Aug 2012	A1
20120226117	Lamego et al.	Sep 2012	A1
20120226160	Kudoh	Sep 2012	A1
20120227739	Kiani	Sep 2012	A1
20120239434	Breslow et al.	Sep 2012	A1
20120242501	Tran et al.	Sep 2012	A1
20120259233	Chan	Oct 2012	A1
20120265039	Kiani	Oct 2012	A1
20120278104	Traughber et al.	Nov 2012	A1
20120282583	Thaler et al.	Nov 2012	A1
20120283524	Kiani et al.	Nov 2012	A1
20120284053	Rosenfeld	Nov 2012	A1
20120286955	Welch et al.	Nov 2012	A1
20120293323	Kaib et al.	Nov 2012	A1
20120294801	Scherz et al.	Nov 2012	A1
20120296178	Lamego et al.	Nov 2012	A1
20120302894	Diab et al.	Nov 2012	A1
20120303476	Krzyzanowski et al.	Nov 2012	A1
20120306881	Nemoto	Dec 2012	A1
20120315867	Davis	Dec 2012	A1
20120319816	Al-Ali	Dec 2012	A1
20120330112	Lamego et al.	Dec 2012	A1
20130006131	Narayan et al.	Jan 2013	A1
20130006151	Main et al.	Jan 2013	A1
20130012830	Leininger	Jan 2013	A1
20130023775	Lamego et al.	Jan 2013	A1
20130035603	Jarausch et al.	Feb 2013	A1
20130041591	Lamego	Feb 2013	A1
20130046197	Dlugos, Jr. et al.	Feb 2013	A1
20130046204	Lamego et al.	Feb 2013	A1
20130060108	Schurman et al.	Mar 2013	A1
20130060147	Welch et al.	Mar 2013	A1
20130069802	Foghel et al.	Mar 2013	A1
20130079610	Al-Ali	Mar 2013	A1
20130092805	Funk et al.	Apr 2013	A1
20130096405	Garfio	Apr 2013	A1
20130096936	Sampath et al.	Apr 2013	A1
20130109929	Menzel	May 2013	A1
20130109935	Al-Ali et al.	May 2013	A1
20130123616	Merritt et al.	May 2013	A1
20130162433	Muhsin et al.	Jun 2013	A1
20130178749	Lamego	Jul 2013	A1
20130190581	Al-Ali et al.	Jul 2013	A1
20130197328	Diab et al.	Aug 2013	A1
20130197364	Han	Aug 2013	A1
20130211214	Olsen	Aug 2013	A1
20130243021	Siskavich	Sep 2013	A1
20130253334	Al-Ali et al.	Sep 2013	A1
20130261494	Bloom et al.	Oct 2013	A1
20130267804	Al-Ali	Oct 2013	A1
20130274571	Diab et al.	Oct 2013	A1
20130274572	Al-Ali et al.	Oct 2013	A1
20130279109	Lindblad et al.	Oct 2013	A1
20130296672	O'Neil et al.	Nov 2013	A1
20130296713	Al-Ali et al.	Nov 2013	A1
20130304559	Stone et al.	Nov 2013	A1
20130317327	Al-Ali et al.	Nov 2013	A1
20130317370	Dalvi et al.	Nov 2013	A1
20130317393	Weiss et al.	Nov 2013	A1
20130324804	McKeown et al.	Dec 2013	A1
20130324808	Al-Ali et al.	Dec 2013	A1
20130324817	Diab	Dec 2013	A1
20130331660	Al-Ali et al.	Dec 2013	A1
20130331670	Kiani	Dec 2013	A1
20130338461	Lamego et al.	Dec 2013	A1
20130340176	Stevens et al.	Dec 2013	A1
20130345921	Al-Ali et al.	Dec 2013	A1
20140012100	Al-Ali et al.	Jan 2014	A1
20140022081	Ribble et al.	Jan 2014	A1
20140025306	Weber et al.	Jan 2014	A1
20140031650	Weber et al.	Jan 2014	A1
20140034353	Al-Ali et al.	Feb 2014	A1
20140046674	Rosenfeld	Feb 2014	A1
20140051952	Reichgott et al.	Feb 2014	A1
20140051953	Lamego et al.	Feb 2014	A1
20140051954	Al-Ali et al.	Feb 2014	A1
20140058230	Abdul-Hafiz et al.	Feb 2014	A1
20140066783	Kiani et al.	Mar 2014	A1
20140073167	Al-Ali et al.	Mar 2014	A1
20140081090	Picard et al.	Mar 2014	A1
20140081097	Al-Ali et al.	Mar 2014	A1
20140081100	Muhsin et al.	Mar 2014	A1
20140081175	Telfort	Mar 2014	A1
20140094667	Schurman et al.	Apr 2014	A1
20140097961	Vaglio et al.	Apr 2014	A1
20140100434	Diab et al.	Apr 2014	A1
20140114199	Lamego et al.	Apr 2014	A1
20140120564	Workman et al.	May 2014	A1
20140121482	Merritt et al.	May 2014	A1
20140121483	Kiani	May 2014	A1
20140127137	Bellott et al.	May 2014	A1
20140128696	Al-Ali	May 2014	A1
20140128699	Al-Ali et al.	May 2014	A1
20140129702	Lamego et al.	May 2014	A1
20140135588	Al-Ali et al.	May 2014	A1
20140142399	Al-Ali et al.	May 2014	A1
20140142401	Al-Ali et al.	May 2014	A1
20140142402	Al-Ali et al.	May 2014	A1
20140152673	Lynn et al.	Jun 2014	A1
20140155712	Lamego et al.	Jun 2014	A1
20140162598	Villa-Real	Jun 2014	A1
20140163344	Al-Ali	Jun 2014	A1
20140163402	Lamego et al.	Jun 2014	A1
20140166076	Kiani et al.	Jun 2014	A1
20140171763	Diab	Jun 2014	A1
20140180038	Kiani	Jun 2014	A1
20140180154	Sierra et al.	Jun 2014	A1
20140180160	Brown et al.	Jun 2014	A1
20140187973	Brown et al.	Jul 2014	A1
20140188516	Kamen	Jul 2014	A1
20140194709	Al-Ali et al.	Jul 2014	A1
20140194711	Al-Ali	Jul 2014	A1
20140194766	Al-Ali et al.	Jul 2014	A1
20140200422	Weber et al.	Jul 2014	A1
20140206963	Al-Ali	Jul 2014	A1
20140213864	Abdul-Hafiz et al.	Jul 2014	A1
20140243627	Diab et al.	Aug 2014	A1
20140257057	Reis Cunha et al.	Sep 2014	A1
20140266787	Tran	Sep 2014	A1
20140266790	Al-Ali et al.	Sep 2014	A1
20140275808	Poeze et al.	Sep 2014	A1
20140275835	Lamego et al.	Sep 2014	A1
20140275871	Lamego et al.	Sep 2014	A1
20140275872	Merritt et al.	Sep 2014	A1
20140275881	Lamego et al.	Sep 2014	A1
20140276115	Dalvi et al.	Sep 2014	A1
20140288400	Diab et al.	Sep 2014	A1
20140288947	Simpson	Sep 2014	A1
20140296664	Bruinsma et al.	Oct 2014	A1
20140303520	Telfort et al.	Oct 2014	A1
20140309506	Lamego et al.	Oct 2014	A1
20140309559	Telfort et al.	Oct 2014	A1
20140316217	Purdon et al.	Oct 2014	A1
20140316218	Purdon et al.	Oct 2014	A1
20140316228	Blank et al.	Oct 2014	A1
20140316804	Tran	Oct 2014	A1
20140323825	Al-Ali et al.	Oct 2014	A1
20140323897	Brown et al.	Oct 2014	A1
20140323898	Purdon et al.	Oct 2014	A1
20140330092	Al-Ali et al.	Nov 2014	A1
20140330098	Merritt et al.	Nov 2014	A1
20140330099	Al-Ali et al.	Nov 2014	A1
20140333440	Kiani	Nov 2014	A1
20140336481	Shakespeare et al.	Nov 2014	A1
20140343436	Kiani	Nov 2014	A1
20140343889	Ben Shalom et al.	Nov 2014	A1
20140357966	Al-Ali et al.	Dec 2014	A1
20140358574	Tara et al.	Dec 2014	A1
20140371548	Al-Ali et al.	Dec 2014	A1
20140371632	Al-Ali et al.	Dec 2014	A1
20140378784	Kiani et al.	Dec 2014	A1
20150001302	Gelay et al.	Jan 2015	A1
20150005600	Blank et al.	Jan 2015	A1
20150011907	Purdon et al.	Jan 2015	A1
20150012231	Poeze et al.	Jan 2015	A1
20150018650	Al-Ali et al.	Jan 2015	A1
20150019231	Sadler et al.	Jan 2015	A1
20150025406	Al-Ali	Jan 2015	A1
20150032029	Al-Ali et al.	Jan 2015	A1
20150038859	Dalvi et al.	Feb 2015	A1
20150045637	Dalvi	Feb 2015	A1
20150051462	Olsen	Feb 2015	A1
20150073241	Lamego	Mar 2015	A1
20150080754	Purdon et al.	Mar 2015	A1
20150087936	Al-Ali et al.	Mar 2015	A1
20150094546	Al-Ali	Apr 2015	A1
20150094618	Russell et al.	Apr 2015	A1
20150097701	Al-Ali et al.	Apr 2015	A1
20150099950	Al-Ali et al.	Apr 2015	A1
20150099951	Al-Ali et al.	Apr 2015	A1
20150099955	Al-Ali et al.	Apr 2015	A1
20150101844	Al-Ali et al.	Apr 2015	A1
20150106121	Muhsin et al.	Apr 2015	A1
20150112151	Muhsin et al.	Apr 2015	A1
20150116076	Al-Ali et al.	Apr 2015	A1
20150126830	Schurman et al.	May 2015	A1
20150133755	Smith et al.	May 2015	A1
20150140863	Al-Ali et al.	May 2015	A1
20150141781	Weber et al.	May 2015	A1
20150165312	Kiani	Jun 2015	A1
20150196237	Lamego	Jul 2015	A1
20150196249	Brown et al.	Jul 2015	A1
20150201874	Diab	Jul 2015	A1
20150208966	Al-Ali	Jul 2015	A1
20150213217	Amarasingham	Jul 2015	A1
20150216459	Al-Ali et al.	Aug 2015	A1
20150220696	Lekutai et al.	Aug 2015	A1
20150223705	Sadhu	Aug 2015	A1
20150230755	Al-Ali et al.	Aug 2015	A1
20150238722	Al-Ali	Aug 2015	A1
20150245773	Lamego et al.	Sep 2015	A1
20150245794	Al-Ali	Sep 2015	A1
20150257689	Al-Ali et al.	Sep 2015	A1
20150272514	Kiani et al.	Oct 2015	A1
20150351697	Weber et al.	Dec 2015	A1
20150359429	Al-Ali et al.	Dec 2015	A1
20150366472	Kiani	Dec 2015	A1
20150366507	Blank et al.	Dec 2015	A1
20150374298	Al-Ali et al.	Dec 2015	A1
20150380875	Coverston et al.	Dec 2015	A1
20160000362	Diab et al.	Jan 2016	A1
20160007930	Weber et al.	Jan 2016	A1
20160029932	Al-Ali	Feb 2016	A1
20160029933	Al-Ali et al.	Feb 2016	A1
20160045118	Kiani	Feb 2016	A1
20160051205	Al-Ali et al.	Feb 2016	A1
20160058338	Schurman et al.	Mar 2016	A1
20160058347	Reichgott et al.	Mar 2016	A1
20160066823	Al-Ali et al.	Mar 2016	A1
20160066824	Al-Ali et al.	Mar 2016	A1
20160066879	Telfort et al.	Mar 2016	A1
20160072429	Kiani et al.	Mar 2016	A1
20160073967	Lamego et al.	Mar 2016	A1
20160078747	King et al.	Mar 2016	A1
20160081552	Wojtczuk et al.	Mar 2016	A1
20160095543	Telfort et al.	Apr 2016	A1
20160095548	Al-Ali et al.	Apr 2016	A1
20160103598	Al-Ali et al.	Apr 2016	A1
20160113527	Al-Ali	Apr 2016	A1
20160143548	Al-Ali	May 2016	A1
20160166182	Al-Ali et al.	Jun 2016	A1
20160166183	Poeze et al.	Jun 2016	A1
20160166188	Bruinsma et al.	Jun 2016	A1
20160166210	Al-Ali	Jun 2016	A1
20160192869	Kiani et al.	Jul 2016	A1
20160196388	Lamego	Jul 2016	A1
20160197436	Barker et al.	Jul 2016	A1
20160213281	Eckerbom et al.	Jul 2016	A1
20160228043	O'Neil et al.	Aug 2016	A1
20160233632	Scruggs et al.	Aug 2016	A1
20160234944	Triman et al.	Aug 2016	A1
20160270735	Diab et al.	Sep 2016	A1
20160283665	Sampath et al.	Sep 2016	A1
20160285717	Kim et al.	Sep 2016	A1
20160287090	Al-Ali et al.	Oct 2016	A1
20160287786	Kiani	Oct 2016	A1
20160296169	McHale et al.	Oct 2016	A1
20160310052	Al-Ali et al.	Oct 2016	A1
20160314260	Kiani	Oct 2016	A1
20160321904	Johnson et al.	Nov 2016	A1
20160324486	Al-Ali et al.	Nov 2016	A1
20160324488	Olsen	Nov 2016	A1
20160327984	Al-Ali et al.	Nov 2016	A1
20160328528	Al-Ali et al.	Nov 2016	A1
20160331332	Al-Ali	Nov 2016	A1
20160361026	Sarkar	Dec 2016	A1
20160367173	Dalvi et al.	Dec 2016	A1
20170007134	Al-Ali et al.	Jan 2017	A1
20170007198	Al-Ali et al.	Jan 2017	A1
20170014083	Diab et al.	Jan 2017	A1
20170014084	Al-Ali et al.	Jan 2017	A1
20170024748	Haider	Jan 2017	A1
20170027456	Kinast et al.	Feb 2017	A1
20170042488	Muhsin	Feb 2017	A1
20170055851	Al-Ali et al.	Mar 2017	A1
20170055882	Al-Ali et al.	Mar 2017	A1
20170055887	Al-Ali	Mar 2017	A1
20170055896	Al-Ali et al.	Mar 2017	A1
20170079594	Telfort et al.	Mar 2017	A1
20170086723	Al-Ali et al.	Mar 2017	A1
20170102901	Burke	Apr 2017	A1
20170143281	Olsen	May 2017	A1
20170147774	Kiani	May 2017	A1
20170156620	Al-Ali et al.	Jun 2017	A1
20170173632	Al-Ali	Jun 2017	A1
20170187146	Kiani et al.	Jun 2017	A1
20170188919	Al-Ali et al.	Jul 2017	A1
20170196464	Jansen et al.	Jul 2017	A1
20170196470	Lamego et al.	Jul 2017	A1
20170202490	Al-Ali et al.	Jul 2017	A1
20170224262	Al-Ali	Aug 2017	A1
20170235910	Cantillon et al.	Aug 2017	A1
20170245790	Al-Ali et al.	Aug 2017	A1
20170251974	Shreim et al.	Sep 2017	A1
20170251975	Shreim et al.	Sep 2017	A1
20170258403	Abdul-Hafiz et al.	Sep 2017	A1
20170311891	Kiani et al.	Nov 2017	A1
20170325728	Al-Ali et al.	Nov 2017	A1
20170332976	Al-Ali et al.	Nov 2017	A1
20170340293	Al-Ali et al.	Nov 2017	A1
20170360310	Kiani et al.	Dec 2017	A1
20170367632	Al-Ali et al.	Dec 2017	A1
20180008146	Al-Ali et al.	Jan 2018	A1
20180014752	Al-Ali et al.	Jan 2018	A1
20180028124	Al-Ali et al.	Feb 2018	A1
20180055385	Al-Ali	Mar 2018	A1
20180055390	Kiani et al.	Mar 2018	A1
20180055430	Diab et al.	Mar 2018	A1
20180064381	Shakespeare et al.	Mar 2018	A1
20180069776	Lamego et al.	Mar 2018	A1
20180103874	Lee et al.	Apr 2018	A1
20180199871	Pauley et al.	Jul 2018	A1
20180213583	Al-Ali	Jul 2018	A1
20180216370	Ishiguro et al.	Aug 2018	A1
20180242926	Muhsin et al.	Aug 2018	A1
20180247353	Al-Ali et al.	Aug 2018	A1
20180247712	Muhsin et al.	Aug 2018	A1
20180256087	Al-Ali et al.	Sep 2018	A1
20180296161	Shreim et al.	Oct 2018	A1
20180300919	Muhsin et al.	Oct 2018	A1
20180310822	Indorf et al.	Nov 2018	A1
20180310823	Al-Ali et al.	Nov 2018	A1
20180317826	Muhsin	Nov 2018	A1
20190015023	Monfre	Jan 2019	A1
20190090760	Kinast et al.	Mar 2019	A1
20190117070	Muhsin et al.	Apr 2019	A1
20190130730	Boyer	May 2019	A1
20190200941	Chandran et al.	Jul 2019	A1
20190239787	Pauley et al.	Aug 2019	A1
20190320906	Olsen	Oct 2019	A1
20190374139	Kiani et al.	Dec 2019	A1
20190374173	Kiani et al.	Dec 2019	A1
20190374713	Kiani et al.	Dec 2019	A1
20200060869	Telfort et al.	Feb 2020	A1
20200111552	Ahmed	Apr 2020	A1
20200113435	Muhsin	Apr 2020	A1
20200113488	Al-Ali et al.	Apr 2020	A1
20200113496	Scruggs et al.	Apr 2020	A1
20200113497	Triman et al.	Apr 2020	A1
20200113520	Abdul-Hafiz et al.	Apr 2020	A1
20200138288	Al-Ali et al.	May 2020	A1
20200138368	Kiani et al.	May 2020	A1
20200163597	Dalvi et al.	May 2020	A1
20200196877	Vo et al.	Jun 2020	A1
20200219335	Gintz et al.	Jul 2020	A1
20200253474	Muhsin et al.	Aug 2020	A1
20200253544	Belur Nagaraj et al.	Aug 2020	A1
20200275841	Telfort et al.	Sep 2020	A1
20200288983	Telfort et al.	Sep 2020	A1
20200321793	Al-Ali et al.	Oct 2020	A1
20200329983	Al-Ali et al.	Oct 2020	A1
20200329984	Al-Ali et al.	Oct 2020	A1
20200329993	Al-Ali et al.	Oct 2020	A1
20200330037	Al-Ali et al.	Oct 2020	A1
20210022628	Telfort et al.	Jan 2021	A1
20210104173	Pauley et al.	Apr 2021	A1
20210113121	Diab et al.	Apr 2021	A1
20210117525	Kiani et al.	Apr 2021	A1
20210118581	Kiani et al.	Apr 2021	A1
20210121582	Krishnamani et al.	Apr 2021	A1
20210161465	Barker et al.	Jun 2021	A1
20210236729	Kiani et al.	Aug 2021	A1
20210256267	Ranasinghe et al.	Aug 2021	A1
20210256835	Ranasinghe et al.	Aug 2021	A1
20210275101	Vo et al.	Sep 2021	A1
20210290060	Ahmed	Sep 2021	A1
20210290072	Forrest	Sep 2021	A1
20210290080	Ahmed	Sep 2021	A1
20210290120	Al-Ali	Sep 2021	A1
20210290177	Novak, Jr.	Sep 2021	A1
20210290184	Ahmed	Sep 2021	A1
20210296008	Novak, Jr.	Sep 2021	A1
20210330228	Olsen et al.	Oct 2021	A1
20210386382	Olsen et al.	Dec 2021	A1
20210402110	Pauley et al.	Dec 2021	A1
20220026355	Normand et al.	Jan 2022	A1
20220039707	Sharma et al.	Feb 2022	A1
20220053892	Al-Ali et al.	Feb 2022	A1
20220071562	Kiani	Mar 2022	A1
20220096603	Kiani et al.	Mar 2022	A1
20220151521	Krishnamani et al.	May 2022	A1
20220218244	Kiani et al.	Jul 2022	A1
20220287574	Telfort et al.	Sep 2022	A1
20220296161	Al-Ali et al.	Sep 2022	A1
20220361819	Al-Ali et al.	Nov 2022	A1
20220379059	Yu et al.	Dec 2022	A1
20220392610	Kiani et al.	Dec 2022	A1
20230028745	Al-Ali	Jan 2023	A1
20230038389	Vo	Feb 2023	A1
20230045647	Vo	Feb 2023	A1
20230058052	Al-Ali	Feb 2023	A1
20230058342	Kiani	Feb 2023	A1
20230069789	Koo et al.	Mar 2023	A1
20230087671	Telfort et al.	Mar 2023	A1
20230110152	Forrest et al.	Apr 2023	A1
20230111198	Yu et al.	Apr 2023	A1
20230115397	Vo et al.	Apr 2023	A1
20230116371	Mills et al.	Apr 2023	A1
20230135297	Kiani et al.	May 2023	A1
20230138098	Telfort et al.	May 2023	A1
20230145155	Krishnamani et al.	May 2023	A1
20230147750	Barker et al.	May 2023	A1
20230210417	Al-Ali et al.	Jul 2023	A1

Foreign Referenced Citations (41)

Number	Date	Country
202889636	Apr 2013	CN
0 735 499	Oct 1996	EP
1 075 831	Feb 2001	EP
1 226 783	Jul 2002	EP
2 335 569	Jun 2011	EP
2 766 834	Aug 2014	EP
2 811 894	Dec 2014	EP
10-336064	Dec 1998	JP
2002-513602	May 2002	JP
2002-165764	Jun 2002	JP
2002-172096	Jun 2002	JP
2002-542493	Dec 2002	JP
2005-218036	Aug 2005	JP
2005-295375	Oct 2005	JP
2007-021213	Feb 2007	JP
2007-095365	Apr 2007	JP
2007-174051	Jul 2007	JP
2008-519635	Jun 2008	JP
2008-541045	Nov 2008	JP
2009-017959	Jan 2009	JP
2009-207836	Sep 2009	JP
2010-503134	Jan 2010	JP
2010-524510	Jul 2010	JP
2011-519607	Jul 2011	JP
2011-519684	Jul 2011	JP
2011-152261	Aug 2011	JP
2014-533997	Dec 2014	JP
WO 98029790	Jul 1998	WO
WO 99013766	Mar 1999	WO
WO 99056613	Nov 1999	WO
WO 00063713	Oct 2000	WO
WO 2004056266	Jul 2004	WO
WO 2004059551	Jul 2004	WO
WO 2006051461	May 2006	WO
WO 2011001302	Jan 2011	WO
WO 2011002904	Jan 2011	WO
WO 2011025549	Mar 2011	WO
WO 2013056160	Apr 2013	WO
WO 2013119982	Aug 2013	WO
WO 2015054665	Apr 2015	WO
WO 2019204368	Oct 2019	WO

Non-Patent Literature Citations (14)

Entry
US 8,845,543 B2, 09/2014, Diab et al. (withdrawn)
US 2022/0192529 A1, 06/2022, Al-Ali et al. (withdrawn)
Invitation to Pay Additional Fees in PCT Application No. PCT/US2019/027772, dated Jul. 5, 2019.
International Search Report & Written Opinion in PCT Application No. PCT/US2019/027772, dated Aug. 29, 2019.
International Preliminary Report on Patentability & Written Opinion in PCT Application No. PCT/US2019/027772, dated Oct. 29, 2020.
Cahalin et al., “The Six-Minute Walk Test Predicts Peak Oxygen Uptake and Survival in Patients with Advanced Heart Failure”, Chest, 110(2):325-332, (Aug. 1996), Downloaded from http://journal.publications.chestnet.org/ on Oct. 16, 2013.
Capuano et al., “Remote Telemetry—New Twists for Old Technology”, Nursing Management, Jul. 1995, vol. 26, No. 7, pp. 26-32.
Elmer-Dewitt, Philip, “Apple's iWatch: The killer apps may be in hospitals, not health clubs”, Fortune.com, Feb. 3, 2014, http://fortune.com/2014/02/03/apples-iwatch-the-killer-apps-may-be-in-hospitals-not-health-clubs/, 4 pages.
Grundy et al., “Telemedicine in Critical Care: An Experiment in Health Care Delivery”, JACEP, Oct. 1977, vol. 6, No. 10, pp. 439-444.
Grundy et al., “Telemedicine in Critical Care: Problems in Design, Implementation and Assessment”, Jul. 1982, vol. 10, No. 7, pp. 471-475.
“Multihoming”—Wikipedia, the free encyclopedia, Retrieved from http://en.wikipedia.org/w/index.php?title=Multihoming&oldid=511630157 on Sep. 25, 2012.
Ruppen et al., “A Wot Approach to eHealth: Case Study of a Hospital Laboratory Alert Escalation System”, Proceedings of the Third International Workshop on the Web of Things; 2012, vol. 1. No. 6, pp. 6.
Rysavy, Peter, “Making the Call with Two-Way Paging”, Network Computing, Published Jan. 15, 1997, www.rysavy.com/Articles/twoway.htm, pp. 5.
Wachter et al., “The Employment of an Iterative Design Process to Develop a Pulmonary Graphical Display”, Journal of the American Medical Informatics Association, vol. 10, No. 4, Jul./Aug. 2003, pp. 363-372.

Related Publications (1)

	Number	Date	Country
	20210027887 A1	Jan 2021	US

Provisional Applications (3)

Number	Date	Country
61738362	Dec 2012	US
61713418	Oct 2012	US
61703643	Sep 2012	US

Continuations (2)

	Number	Date	Country
Parent	15498194	Apr 2017	US
Child	17061495		US
Parent	14030360	Sep 2013	US
Child	15498194		US

Intelligent medical escalation process

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications

Disclaimer

Abstract