Medical device system including information technology infrastructure having secure cluster domain supporting external domain

Description

PRIORITY CLAIM

The present application is a National Phase filing of International Application No. PCT/EP2017/081763, filed Dec. 7, 2017, which claims priority to Swedish Application No. 1651699-9, filed Dec. 21, 2016, the entire contents of each of which are incorporated herein by reference and relied upon.

BACKGROUND

The present disclosure relates generally medical device systems and more particularly to the managing and running of an information technology (“IT”) infrastructure with connection to external systems like clinic information systems (“CIS”), billing systems, laboratories, and the like.

IT connectivity for medical systems was introduced originally to only a selected set of medical providers and was strictly proprietary. Eventually, medical IT systems gradually started to rely on standardized solutions, which were considered advantageous from cost and development perspectives. On the downside, where responsibility resided before with the proprietary system providers, standardized solutions split the responsibility for the reliability of the IT systems onto several parties, the major responsibilities being delegated to the associated equipment manufacturer, the CIS manufacturer, and IT professionals.

The complexity involved in managing the infrastructure of a medical device IT system is considerable and, in general, only larger clinics may afford the cost and competence to setup and maintain such a system running with the reliability and availability required in a health care environment. The result is that progress in using IT-based support to increase the efficiency in medical device settings, such as dialysis clinics, has been slow. Indeed, many would say that little progress has been seen over the last thirty years in the health care environment when compared to the explosive development of today's personal computing and smart mobile communication devices.

The burden on the clinic is further increased by the fact that the clinic is ultimately responsible from a quality management and risk analysis perspective when combining all subsystems and equipment into a unit. The responsibility imposes expectations on the clinic to have access to qualified personnel for performing such quality and risk management evaluations, since most equipment and software manufacturers will refrain from assuming such responsibilities when their products are combined with other products, or integrated in a system in which the software manufacturers have no prior or upfront knowledge.

To summarize, most medical treatment settings (e.g., dialysis clinics) today recognize the potential of IT systems in reducing errors, documentation workload and other administration workload. The clinics also recognize the cost and complexity of managing different IT solutions and that off-the-shelf support for integrating such systems is very limited. That is, the clinics realize that they will shoulder the burden of implementing and maintaining an IT solution. Most clinics however do not have and cannot afford dedicated IT personnel.

While there is a widespread desire to use IT for therapy management, many electronic medical record systems in place do not meet the needs from either a data structure or a reporting perspective. Existing systems are accordingly perceived as lacking understanding for the medical user's needs in the context of clinic workflow management.

An improved IT solution for medical treatment settings, e.g., dialysis clinics, in which there is a large data management need but a relatively small IT budget, is needed accordingly.

SUMMARY

The medical device information technology (“IT”) system and methodology of the present disclosure is applicable, for example, to medical devices such as those for: plasmapherisis, hemodialysis (“HD”), hemofiltration (“HF”) hemodiafiltration (“HDF”), and continuous renal replacement therapy (“CRRT”) treatments. The medical device IT system described herein is also applicable to peritoneal dialysis (“PD”), intravenous drug delivery, and nutritional fluid delivery. These modalities may be referred to herein collectively or generally individually as medical fluid delivery, however, the IT system is not limited to medical fluid delivery and instead may involve medical devices generally. The medical devices may house components needed to deliver medical fluid, such as one or more pump, plural valves, a heater if needed, online medical fluid generation equipment if needed, plural sensors, such as any one, or more, or all of pressure sensors, conductivity sensors, temperature sensors, air detectors, blood leak detectors, and the like, a user interface, and a control unit, which may employ one or more processor and memory to control the above-described equipment. The medical fluid delivery device may also include one or more filter, such as a dialyzer or hemofilter for cleansing blood and/or an ultrafilter for purifying water, dialysis fluid, or other fluid.

The medical device IT system and methodology of the present disclosure may be used with medical devices located in a clinic/hospital or with home-based medical devices. One suitable hemodialysis machine for a clinical setting is described in U.S. Pat. No. 8,647,290, issued Feb. 11, 2014, entitled “Hemodialysis or Hemo(dia)filtration Apparatus and a Method for Controlling a Hemodialysis or Hemo(dia)filtration Apparatus”, filed May 26, 2008. One suitable CRRT machine for a hospital or clinical setting is described in U.S. Pat. No. 8,911,390, issued Dec. 16, 2014, entitled “Multipart Fluid System And A System For Regional Citrate Anticoagulation In An Extracorporeal Blood Circuit”, filed Mar. 31, 2010. One suitable home system is described in U.S. Pat. No. 8,029,454, issued Oct. 4, 2011, entitled “High Convection Home Hemodialysis/Hemofiltration and Sorbent System”, filed Nov. 4, 2004, assigned to the assignee of the present application. Another such home system is described in U.S. Pat. No. 8,393,690, issued Mar. 12, 2013, entitled “Enclosure for a Portable Hemodialysis System”, filed Aug. 27, 2008. One suitable peritoneal dialysis system that may be used at home or in a clinic is described in U.S. Pat. No. 9,248,225, issued Feb. 2, 2016, entitled “Medical Treatment System and Methods Using a Plurality of Fluid Lines”, filed Jan. 23, 2009. The entire contents of each of the above references are incorporated herein by reference and relied upon.

Each of the above types of medical devices may be considered to be a node in a cluster of multiple nodes, which share a common distributed database. Each node of the cluster shares its data (e.g., (i) data concerning its programmed operating parameters, (ii) data gathered from a treatment such as medical device output data, event data, and patient data, and (iii) any other relevant data) with each other node of the cluster. To share its data, the cluster may be configured such that the nodes (i) push their data to each other, (ii) pull their data from each other, or (iii) push and pull data from each other. Further, to share its data, the cluster may be configured such that (a) the nodes each send their data to each other node using (i), (ii) or (iii) or (b) one or more hub node may be provided that collects data from a subset of nodes, shares the data along with its own data within the subset, passes the collected data along with its own data to any other existing hub node for distribution within the other node's subset, and receives collected data from any other hub node for distribution within its own subset, using (i), (ii) or (iii).

Regardless of how information is shared within the cluster or distributed database, the information and information sharing is secure and complete. The information is secure for multiple reasons. First, only cluster compatible and certified nodes are connected to the cluster, and only these nodes may share data. Managed exceptions to this rule are described below. Second, software for the cluster is in one embodiment proprietary, so that outside devices not having the proprietary software cannot communicate with the nodes even if somehow connected to the same network as the nodes of the cluster. The proprietary software may have standardized components, e.g., may use open source software, but the overall software is proprietary.

The cluster is in one embodiment provided by the medical device manufacturers. The secure distributed database is deployed as part of each medical device participating as nodes in the cluster. The cluster compatible medical devices connect in a network and automatically form the shared or distributed database of the present disclosure, which may be formed around a physical database (e.g., hard disk-based) residing in each physical medical device. Discussed below are many functions that the cluster of nodes may control. The cluster of devices (nodes) designed for running as cluster member nodes assumes the majority of the responsibility for handling the complexities associated with an open IT infrastructure and is accordingly an attractive option for clinics and any other medical device setting in which there is a large data management need but a relatively small IT budget. Some responsibility may still reside with the clinic, such as providing cabling and other hardware.

The cluster and its nodes may be said to form a cluster domain. It is expected that most if not all clinics or other medical device settings will have some sort of computer network upon which nurses, clinicians and technicians may use to run pertinent software, such as third party clinical software, billing software, accounting software, etc. Any of this software outside of the cluster domain may be said to form an external domain.

Some of the external domain software may have a need for at least some of the data shared within the distributed database. Additionally, depending upon what functions are handled within the cluster domain, there may be a need for the distributed database to receive data from and deliver data to the external domain. To do so, it is contemplated to create or designate one or more nodes of the distributed data base as an access node. Each access node in an embodiment has an internal part and an external part, which may only communicate with each other through one or more controlled interface, such as a memory manager. The external part of the access node interfaces with the external domain, while internal part of the access node interfaces with the cluster domain. The cluster access nodes may be said to form an interface domain between the open external domain and the internal cluster domain.

It is contemplated to provide three different types of access options. A first type of access option is an access node, which is a distributed database access node. This access node maintains the shared database formed between all the other nodes. The distributed database access node may or may not add data to the shared database but in either case receives all data from all other nodes generating data and permanently storing the data. The distributed database access node enables a client device to receive data from the shared database and to add data to the shared database. While the access nodes are generally described as being different from the medical devices of the cluster, it is contemplated that a medical device may also provide access capabilities and therefore also form an access node.

A second type of access option is also an access node, but which is a conversion only node or non-distributed database access node. A non-distributed database access node does not contain the shared database and is instead limited to allowing a client device to interact functionally with a cluster node. For example, it may be desired to send from a weight scale a patient's weight data wired or wirelessly to the cluster via the non-distributed database access node. In an embodiment, the non-distributed database node connects to a distributed database node and transfers its information to that node. The transferred information is shared with the rest of the distributed database at the next distributed database update. The weight data along with a patient identifier may then be recalled by whichever node or medical device has need for the weight data, e.g., the node or medical device treating the patient that day. The conversion only access node enables a secure transfer of the weight data to the cluster of nodes but does not itself contain the distributed database.

Besides the two types of physical access nodes, it is contemplated to provide a third type of interface between the distributed database domain and the external domain, which may be referred to as a virtual access node. The access node is considered virtual because there is no additional hardware involved. The virtual node may for example be software in a doctor's or clinician's computer that runs in its own open network separated from the distributed database. The doctor or clinician's computer and the lab technician's computer may run software that needs to or benefits from sharing information with the distributed database. Such software might for example require data from the lab technician's computer, e.g., patient test results. While it is contemplated that the doctor or clinician's computer be able to send service requests via an access node to invoke operational routines running in the distributed database, it may alternatively be possible and perhaps desirable to enable the doctor's computer to access the distributed database virtually with the assurance that the doctor's computer is protected enough to do so. For example, the security may be provided via a virtual private network (“VPN”) between the doctor's computer and the part of a virtual access node that resides inside a medical device.

The medical device IT system and methodology of the present disclosure reduces the overall complexity of managing and running an IT infrastructure, while offering full flexibility to connect to external systems (a CIS, billing systems, laboratories, etc.) deployed within or outside a medical device clinic. The IT system and methodology is hidden and controlled at a single responsible part (the cluster configuration and its associated distributed database) for critical areas like reliability, availability, security, safety and integrity, while at the same time providing access to services needed in the clinic from a process, staff and patient perspective. The IT system and methodology is able to integrate patient related medical information stored in the distributed database with the clinic's overall medical record system and with information used and produced by equipment at the patient's bedside, before, during and/or after treatment.

The medical device IT system and methodology of the present disclosure enables data to flow both ways, in real time, e.g., between outside medical equipment and the medical devices of the cluster, enabling, for example, correct dialysis equipment setup prior to treatment based on physician's prescriptions and on information generated at the bedside, e.g., under the guidance of nurses and other dialysis caregiver staff, before, during and/or after treatment. Conversely, it may be desired that actual treatment result information from medical equipment, e.g., events (e.g., alarms, alerts) generated and documented on the equipment, and nurse's notes or inputs associated with a treatment be transmitted back to the CIS for short and/or long term medical evaluation.

The complexity of running current “open” IT structures in the clinics originates from maintaining an infrastructure of application servers with server software, database servers, backup servers (physically separated from the servers), IT network (wired or wireless, cabling and routers) and client computers with client software. Integrating such infrastructure within medical device equipment to collectively form a distributed database, in combination with supporting proprietary connectivity equipment (access nodes), in a “closed” cluster configuration with access to/from external systems (e.g. a CIS or any other information management system) causes the main responsibility for the overall reliability of such an infrastructure to be limited and confined within the well-controlled realm of the medical equipment and its integrated distributed database.

The advantages of the medical device IT system and methodology of the present disclosure are applicable to home treatment and other external scenarios as well. There may for example be a separate cluster of nodes forming a virtual network of, e.g., home dialysis machines, or a mixture of in-center and home dialysis machines. The clinic responsible for the home-based medical devices may still benefit from the synchronization mechanisms and other services offered by the cluster. The main exception is the control of the transport infrastructure, which in case of home patients cannot be claimed to be under the control of the cluster configuration. This may affect availability and performance since disturbances in such infrastructure is beyond control from the cluster. However, most other benefits of the cluster configuration in addition to synchronization will still be available, e.g. safety, security, integrity and information exchange will still be available, albeit subject to data rates offered by the transport chain between clinic and the patient home environment.

Cluster inclusion of medical devices external to a clinic or hospital may be valuable in a situation in which a patient normally treated in a clinic is instead treated temporarily outside the clinic (e.g., home, work trip or vacation). The system of the present disclosure may ensure that all medical devices belonging to a clinic are configured in the same way (e.g., technically), regardless if they are used inside or outside of the clinic. In an embodiment, medical devices or nodes used at the patient's home location are given restricted access to the shared database, so that the patient may only see his or her own data and the information needed to setup and run a treatment. The data generated by the external treatment is added to the shared database. The device is therefore not necessarily operating “offline” from the database when operating outside of the hospital or clinic.

In light of the disclosure herein and without limiting the disclosure in any way, in a first aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, a medical device system includes: a cluster including a plurality of nodes and running proprietary software; a plurality of medical devices implementing at least some of the nodes; at least one of the nodes being an access node; a distributed database shared along the cluster and hosted by at least some of the nodes; and at least one external equipment outside the cluster, the at least one external equipment running software different than the proprietary software and able to at least one of (i) write to, or (ii) read from, at least some of the distributed database via the access node.

In a second aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, the at least one access node is provided separately from the medical devices.

In a third aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, the at least one access node is provided with one the medical devices.

In a fourth aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, the at least one access node does not host the distributed database.

In a fifth aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, the at least one external equipment is a first external equipment, and which further includes a virtual access node of the cluster formed via a second external equipment, the virtual access node providing a secure data exchange environment so as to ensure security of the cluster operating with the second external equipment.

In a sixth aspect of the present disclosure, which may be combined with the fifth aspect in combination with any other aspect listed herein unless specified otherwise, the secure data exchange environment includes a secure channel such as a virtual private network.

In a seventh aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, the at least one external equipment is configured to deliver data to the distributed database, the data used by one of the medical devices implementing one of the nodes for treatment.

In an eighth aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, the plurality of medical devices are of a same treatment type.

In a ninth aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, the plurality of medical devices are treating a same patient.

In a tenth aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, the distributed database is populated by (i) each of the nodes that produces data pushing its data to other nodes, (ii) each of the nodes having distributed database pulling data from other nodes, or (iii) a combination of (i) and (ii).

In an eleventh aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, a medical device system includes: a cluster including a plurality of nodes; each of a set of the nodes implemented by a medical device; a distributed database hosted by each of the medical devices; at least one first access node that hosts the distributed database; at least one second access node provided separately from the distributed database; and at least one external equipment outside of the cluster, the at least one external equipment able to at least one of (i) write to, or (ii) read from, the distributed database via the at least one first access node or the at least one second access node.

In a twelfth aspect of the present disclosure, which may be combined with the eleventh aspect in combination with any other aspect listed herein unless specified otherwise, the at least one first access node and the at least one second access node are separate from the medical devices.

In a thirteenth aspect of the present disclosure, which may be combined with the eleventh aspect in combination with any other aspect listed herein unless specified otherwise, the at least one first access node and the at least one second access node are provided with or operate with a user interface.

In a fourteenth aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, a medical device system includes: a cluster including a plurality of nodes; a plurality of medical devices implementing at least some of the nodes; at least one of the nodes being an access node including an external part and an internal part; a distributed database provided along the cluster and hosted by at least some of the nodes, the distributed database, if stored by the at least one access node, associated with the internal part of the access node; and at least one external equipment outside the cluster, the at least one external equipment able to at least one of (i) write to, or (ii) read from, at least some of the distributed database via the external part of access node.

In a fifteenth aspect of the present disclosure, which may be combined with the fourteenth aspect in combination with any other aspect listed herein unless specified otherwise, the external part and the internal part are separated by a processing and memory manager that knows how to (i) place data into the external part coming from the internal part and (ii) place data into the internal part coming from the external part.

In a sixteenth aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, a medical device system includes: a cluster including a plurality of nodes; a plurality of medical devices implementing at least some of the nodes, each medical device including processing and memory configured to perform a medical procedure; and a distributed database shared along the cluster by at least some of the nodes, the distributed database deployed on the plurality of medical devices, the distributed database separated from the processing and memory configured to perform the medical procedure by a processing and memory manager that knows how to (i) place data into the processing and memory configured to perform the medical procedure coming from the distributed database and (ii) place data into the distributed database coming from the processing and memory configured to perform the medical procedure.

In a seventeenth aspect of the present disclosure, which may be combined with the sixteenth aspect in combination with any other aspect listed herein unless specified otherwise, the processing and memory configured to perform the medical procedure are configured to initiate communication with the distributed database via the processing and memory manager.

In an eighteenth aspect of the present disclosure, which may be combined with the sixteenth aspect in combination with any other aspect listed herein unless specified otherwise, the distributed database is located in a cluster control part of the medical device that is separate from the processing and memory configured to perform the medical procedure located in a therapy control part of the medical device, the cluster control part separated from the therapy control part by the processing and memory manager.

In a nineteenth aspect of the present disclosure, which may be combined with any other aspect listed herein unless specified otherwise, a medical device system includes a medical device system (110) including: a cluster (10) including a plurality of nodes (12); a plurality of medical devices implementing at least some of the nodes (12); a distributed database (14) shared along the cluster (10) and hosted by the plurality of medical devices; an external equipment (50) outside the cluster (10); and a virtual access node (100) of the cluster (10) formed with the external equipment (50) and one of the medical devices, the virtual access node (100) providing a secure data exchange environment so as to ensure the security of the distributed database (14) when the external equipment (50) writes to, or (ii) reads from, the medical device.

In a twentieth aspect of the present disclosure, which may be combined with the nineteenth aspect in combination with any other aspect listed herein unless specified otherwise, the medical device includes a first virtual access node interface and the external equipment includes a second virtual access node interface, and wherein the secure data exchange environment includes a secure channel such as a virtual private network interfacing with the virtual access node interfaces.

In a twenty-first aspect of the present disclosure, any of the structure and functionality disclosed in connection with FIGS. 1 to 15 may be combined with any of the other structure and functionality disclosed in connection with FIGS. 1 to 15.

In light of the present disclosure and the above aspects, it is therefore an advantage of the present disclosure to provide an improved medical information technology (“IT”) system in which connectivity is integrated into the associated medical devices.

It is another advantage of the present disclosure to reduce the clinic's cost of ownership for an IT connectivity solution in a health care environment, and wherein responsibility for operation is centralized around a cluster of nodes having a well defined scope.

It is a further advantage of the present disclosure to improve reliability, availability and correctness of an IT connectivity solution in a health care environment.

It is still another advantage of the present disclosure to provide an IT connectivity solution in a health care environment that is easy for caregiver staff, e.g., nurses and technicians, to use, and which reduces overhead work.

It is still a further advantage of the present disclosure to provide an IT connectivity solution in a health care environment that promotes and supports the needs of at least one of a care giver (remote alarms, instant access, bidirectional information flow), a physician, whose primary concerns are the welfare of and benefits for the patient (prescription updates, access to information even if the medical devices belonging to the cluster are not available, real time retrieval of patient data), an IT technician (reduced IT complexity, responsibility held at least in part by the medical device maker), a service technician (software installs and updates may be cluster wide, historical data readily available, early warning diagnostics), and/or an administrator (easy to set and implement clinical preferences, run reports and obtain statistics, easy to schedule medical devices for treatments, easy to track patient data).

Further still, it is an advantage of the present disclosure to provide an IT connectivity solution that provides all updates, instantly, to all nodes, with low risk of distorted information.

It is yet another advantage of the present disclosure to provide an IT connectivity solution that is two-way between a secured, real time distributed medical device domain and an outside, open external domain, and which has malware immunity.

It is yet a further advantage of the present disclosure to provide scalability to a clinic or other medical device setting in which a cluster of medical devices may operate alone, with a lesser set of external devices upon installation, and with an expanded set of external databases in the future if desired.

Still a further advantage of the present disclosure is to provide an IT connectivity solution that enables a medical device node or access node that is temporarily disconnected (by choice or by accident) from the cluster of nodes to still have access to the distributed database as it existed at the time of disconnection and to be updated upon reconnection to the cluster of nodes.

Moreover, it is an advantage of the present disclosure to provide a medical device IT connectivity solution that provides good overall reliability regarding at least one of data availability, correctness, security, safety, integrity and/or usability.

The advantages discussed herein may be found in one, or some, and perhaps not all of the embodiments disclosed herein. Additional features and advantages are described herein, and will be apparent from, the following Detailed Description and the figures.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic view illustrating one embodiment of a cluster of nodes sharing a distributed database of the present disclosure.

FIG. 2 is a schematic illustration of one embodiment of an overall medical device information technology (“IT”) system including a cluster of nodes forming a cluster domain that communicates with an open external domain via an interface domain.

FIG. 3 is a schematic view of one embodiment of an overall medical device IT system that includes a cluster of nodes sharing a distributed database interfacing with plural external entities via multiple access nodes of the cluster.

FIG. 4 is a schematic view further illustrating examples of external information system equipment.

FIG. 5 is a schematic view further illustrating an example of presentation type external equipment.

FIG. 6 is a schematic view further illustrating an example of tablet and computer type external equipment.

FIG. 7 is a schematic view further illustrating an example of shared medical type external equipment.

FIG. 8 is a schematic view further illustrating an example of bedside medical type external equipment.

FIG. 9 is a schematic view illustrating one embodiment of a distributed database access node and an enlarged view of a medical device node of the cluster system of the present disclosure.

FIG. 10 is a schematic view further illustrating the isolation aspects of a medical device node of the cluster system of the present disclosure.

FIGS. 11 and 12 are schematic views illustrating one embodiment of an enlarged view of a distributed database access node of the cluster system of the present disclosure.

FIG. 13 is schematic view illustrating one embodiment of an enlarged view of a non-distributed database access node of the cluster system of the present disclosure.

FIG. 14 is a schematic view illustrating one embodiment of how the cluster domain includes the cluster having the distributed database and a therapy control part of each medical device node.

FIG. 15 is a schematic view illustrating one embodiment of a virtual access node of the cluster system of the present disclosure.

DETAILED DESCRIPTION

The examples described herein are applicable to any type of medical device, for example, medical devices that deliver a medical fluid, such as blood, dialysis fluid, substitution fluid or an intravenous drug (“IV”). The examples are particularly well suited for kidney failure therapies, such as all forms of hemodialysis (“HD”), hemofiltration (“HF”), hemodiafiltration (“HDF”), continuous renal replacement therapies (“CRRT”) and peritoneal dialysis (“PD”), referred to herein collectively or generally individually as renal failure therapy. The medical devices may alternatively be drug delivery or nutritional fluid delivery medical devices, such as large volume peristaltic type pumps or syringe pumps. The medical devices may have any one or more of: one or more pump, plural valves, a heater if needed, online medical fluid generation equipment if needed, plural sensors, such as any one, or more, or all of pressure sensors, conductivity sensors, temperature sensors, air detectors, blood leak detectors, and the like, a user interface, and a control unit, which may employ one or more processor and memory to control the above-described equipment. The medical device may also include one or more filter, such as a dialyzer or hemofilter for cleansing blood and/or an ultrafilter for purifying water, dialysis fluid, or other fluid.

The medical devices in many instances include a reusable part operating with a disposable part. The reusable part may (e.g., online blood treatment dialysis machines) or may not (e.g., peritoneal dialysis machines, CRRT machines, drug and nutritional fluid delivery machines) carry treatment fluid. The disposable part may carry blood (blood treatment including CRRT machines) or treatment fluid (peritoneal dialysis machines, CRRT machines, drug and nutritional fluid delivery machines).

Referring now to the drawings and in particular to FIG. 1, a cluster of nodes 10 is illustrated. Cluster 10 includes a plurality of nodes 12a to 12h (referred to herein collectively as nodes 12 or generally individually as node 12). Nodes 12 may be represented by any of the medical devices described above. Any of nodes 12 may alternatively be a computer. Most of the nodes of cluster 10 share a common set of data or distributed database 14. As discussed in detail below, access node 12h does not possess or share distributed database 14.

Distributed database 14 is the combination of all data inputted to and generated at each of nodes 12, including data generated by non-distributed database node 12h. That is, even though node 12h does not share distributed database 14, data may still come in through non-distributed database node 12h or be generated by node 12h, which becomes part of distributed database 14 shared by nodes 12a to 12g.

Many embodiments for how nodes 12a to 12g may share their data are set forth in copending Patent Cooperation Treaty Application PCT/EP2016/064392, having an international filing date of 22 Jun. 2016, and a common applicant with the present disclosure, the entire contents of which are incorporated herein by reference and relied upon. In general each node 12 of cluster 10 shares its data (e.g., (i) data concerning its programmed operating parameters, (ii) data gathered from a treatment such as medical device output data, event data, and patient data, and (iii) any other relevant data) with each other node 12 of cluster 10, except certain access nodes, such as node 12h. To share its data, cluster 10 may be configured such that nodes 12 (i) push their data to each other, (ii) pull their data from each other, or (iii) push and pull data from each other. Further, to share its data, cluster 10 may be configured such that (a) nodes 12 each send their data to each other node using (i), (ii) or (iii) or (b) one or more hub node may be provided that collects data from a subset of nodes, shares the data along with its own data within the subset, passes the collected data along with its own data to any other existing hub node for distribution within the other node's subset, and receives collected data from any other hub node for distribution within its subset, using (i), (ii) or (iii).

The nodes of cluster 10 run on proprietary software and access to distributed database 14 is limited to that described below. The software may be built using off the shelf components, such as open source software, but the overall product is proprietary. Thus, even if cluster 10 is somehow improperly accessed or hacked, access to distributed database data 14 is difficult without the proprietary software (e.g., software developed in-house by the medical device manufacturer, which may use publically available software, such as open source software, but which itself is not publically available). Cluster 10 may therefore, within a closed environment, be trusted handle all aspects regarding the complexities associated with existing clinics running open IT infrastructures. Such complexities may include assuming: (i) required server (service) and synchronization roles, (ii) database deployment, (iii) network solutions on all levels (except perhaps on a physical and link layer level, where there is an option of either running on an existing/shared hardware infrastructure or running a virtual private network on existing clinic IT hardware solutions), and (iv) backup server roles as each node 12 having common set of data 14 acts as a backup device (except a requirement that a back-up server has to be physically separated from any other device).

By integrating information technology (“IT”) infrastructure support within a medical device, in combination with supporting proprietary connectivity equipment, in a “closed” cluster configuration with limited access to/from cluster-external systems (e.g., a client information system (“CIS”) or any other information system), the responsibility for the overall reliability of such IT infrastructure is restricted and confined within the well-controlled realm of the medical equipment, e.g., medical fluid delivery device nodes 12.

Referring now to FIGS. 2 and 3, cluster 10 of FIG. 1 is illustrated as being part of an overall medical device information technology (“IT”) system 110. FIG. 2 illustrates that system 110 includes an external domain 110a, a cluster domain 110b, and an interface domain 110c, which links external domain 110a to cluster domain 110b. In FIG. 2, cluster 10 of FIG. 1 is illustrated as being part of cluster domain 110b. There may be multiple clusters 10 forming cluster domain 110b. For example, there may be different clusters 10 for the different types of medical devices described above at nodes 12.

Cluster domain 110b represents core functionality of the cluster database services and infrastructure. Cluster domain 110b handles the transfer and conversion of information flow in both cluster 10 inbound and outbound directions between it and external domain 110a. As discussed above, each node 12 (except node 12h) of cluster 10 holds shared data 14. Each node 12 of each cluster 10 (there may be more than one cluster 10 in domain 110b) of cluster domain 110b is mutually synchronized, which allows for arbitrary member nodes 12 to be shut down while still maintaining external access to the services and information of cluster 10.

Each cluster 10 of cluster domain 110b forms a protected space both in terms of network traffic and information access, incorporating a significant amount of redundancy, with a purpose to guarantee that cluster 10 is available at all times. Cluster 10 maintains a high degree of information integrity; implements secure ways of accessing information from clients external to the cluster, while meeting established security requirements associated with the connection of the medical devices of nodes 12 to outside equipment.

In one embodiment, if a medical device associated with a node 12 is for whatever reason accessed without using the node (e.g., via a virtual access discussed below), the medical device is subject to certain security requirements. For instance, if the medical device is to be connected, e.g., via a wired local area network (“LAN”), both to cluster 10 and to a piece of outside client equipment, then two separated LAN connectors are required in one embodiment, one connector reserved for cluster 10 connectivity and a second connector for open environment connectivity. In another embodiment, the LAN connectors may be shared for both the cluster and open environments but software isolation is employed. Separation within cluster 10 may therefore employ different combinations of hardware and software isolation between a cluster 10 LAN connection and the connection to the open environment. Providing such isolation and maintaining responsibility for quality, IT connectivity, and associated services inside a well confined cluster 10, where equipment is developed under a strict rigor associated with medical products, results in a redundant and highly stable system of operation.

One important application of cluster 10 is to support technical maintenance of the equipment occupying nodes 12. In the same way that nodes 12 replicate medical information, they may also replicate downloaded code (e.g., medical device software updates). By connecting, e.g., via a laptop or tablet device via an access node 12a or 12h (discussed below), a service technician may diagnose, configure and update software on the medical device, including the gathering of technical statistical information to promote preventive maintenance.

From a medical perspective, cluster 10 will assist in a multitude of areas, e.g., operational prescription management, treatment result assembly and storage, treatment session reporting, and medical record management and support. From an alarm perspective, cluster 10 constantly updates and distributes alarms and other real time events between nodes 12 of cluster 10, including medical equipment and access nodes 12.

Still another area in which cluster 10 may play an important role is for synchronization between different types of connected equipment. In one example, multiple online dialysis fluid generation dialysis machines may be connected fluidically to a central water supply loop that supplies purified water to the machines, which use the purified water to prepare dialysis fluid. The water supply loop needs to be cleaned periodically, e.g., via hot water disinfection. In an embodiment, the custom software of cluster 10 is able to ascertain when each of the dialysis machine nodes 12 is available for having its portion of the water supply loop disinfected, so that a disinfection sequence may be commenced that efficiently and optimally cleans the entire water supply loop, including portions of the loop connecting the machines to the remainder of the water supply loop. Cluster 10 may report out that all relevant medical device nodes 12 (non-medical device access nodes being excluded) are available for a cleaning session, upon which a central water plant initiates a hot water loop disinfection. Note that initiation of a request for disinfection of the central water supply loop may come from (i) within cluster 10, e.g., the proprietary software is programmed to prompt when all medical device nodes 12 are at rest and at least a certain amount of time or total service hours have passed since the last disinfection or (ii) the central water plant, e.g., after at least a certain amount of time or total service hours have passed since the last disinfection. Other examples of where the medical devices of nodes 12 may synchronize with outside equipment includes software updates, where an update may be scheduled for the next time each of the medical device nodes 12 is at rest, at which time cluster 10 reports out that it is ready for the new software.

It is also contemplated that the collaboration between nodes 12 of cluster 10 not be limited to medical applications. For example, cluster 10 may store and synchronize information to support patient in-center entertainment preferences, such as, favorite websites, television and radio channels, movies, food and beverages. This information is available no matter which medical device of cluster 10 is used to treat a patient.

The clusters 10 of cluster domain 110b offer a powerful platform having high integrity for a multitude of application areas listed below. The below list is not exhaustive, but serves to exemplify the variety of services that benefit from the closed cluster domain 110b. Each of the entries of the following list in one way another benefits from the safety, security and quality aspects that cluster domain 110b provides, including: (i) clinic administration services, (ii) staff and patient administration services, (iii) attention services including information presentation services, staff assistance call services, medical device alarm distribution services, and staff reminder services, (iv) connectivity services including cluster node connectivity services, connectivity level services, and dialysis monitor connectivity services, (v) equipment services including dialysis monitoring services, and water purification system services, (vi) financial services including dialysis billing services, (vii) identification services including dialysis session identification services, medication identification services, dialysis station identification services, disposable identification services, equipment identification services, patient identification services, and staff identification services, (viii) information management services including clinic information services, and patient information services, (ix) inventory services including inventory consumption tracking services, product traceability services, and reuse traceability services, (x) scheduling services including equipment scheduling services, patient scheduling services, and staff scheduling services, (xi) security services including access control services, availability protection services, confidentiality protection services, encryption services, and integrity protection services, (xii) therapy services including assessment services, consultation services, dialysis session services, dialysis session record services, medical tests services, prescription services, and vascular access services, and (xiii) water purification services including distribution loops services, and water quality services.

In FIG. 2, external domain 110a is in one embodiment an open IT environment domain using standard off-the-shelf hardware and software. The only exception to the off-the-shelf architecture being software applications deployed on external domain 110a equipment for the purpose of interacting with cluster domain 110b via interface domain 110c. In many instances, external domain 110a equipment is not readily programmable and therefore will not receive custom software for interfacing with cluster 10. Instead, access nodes 12a and 12h contain the interfacing software to read the data entering from the external equipment. In the case of a doctor's or clinician's computer, however, there may be application software that is installed on the computer that has counterpart application software stored at nodes 12 or software for interfacing with the application software stored at nodes 12. External domain 110a equipment may include non-proprietary devices that are not designed for inclusion cluster domain 110b and therefore need additional equipment (interface domain 110c) to exchange information with the cluster domain 110b.

FIG. 3 illustrates external domain 110a in more detail and operating with cluster domain 110b having access nodes 12a and 12h forming at least part of interface domain 110c. In the illustrated embodiment, external domain 110a is represented by the following classes or types of equipment: (i) external information systems 50a, which may be any information system external to cluster 10 that benefits from exchanging information with member nodes 12 of cluster 10, (ii) presentation equipment 50b, which may be any equipment primarily used for presenting information retrieved from cluster 10, e.g., display screens of all sizes and technologies (optionally of touch type), (iii) tablet and personal computer equipment 50c, which may be any keyboard- or touch-based user interface equipment used for exchanging information between external domain 110a and cluster domain 110c equipment, e.g., smartphones, smart pads, laptops, stationary personal computers (“PCs”), hybrids, and similar computer-based equipment, (iv) shared (e.g., medical) equipment 50d, which may be any equipment (medical or non-medical) used to support a medical device clinical process that is shared between patients as part of their pre- and/or post-registration activities during the presence at the clinic, e.g., patient pre/post treatment weight scale and registration stations, blood pressure stations, clinic arrival/departure registration and equipment deployed in the clinic for similar purposes (such shared equipment is normally equipped with, connected to and/or used with some kind of personal identification equipment), and (v) bedside (e.g., medical) equipment 50e, which may be any equipment (medical or non-medical) deployed at the patient's bedside and associated with (serving) a specific patient during part or full duration of treatment, e.g., water reverse osmosis units for dialysis fluid preparation, blood pressure meters, entertainment consoles and other equipment deployed at bedside for similar purposes.

While FIGS. 1 and 3 illustrate cluster 10 having both distributed database access node 12a and non-distributed database access node 12h, it should be appreciated that any cluster containing one or more nodes 12b-12g may have (i) one or more distributed database access node 12a only, (ii) one or more non-distributed database access node 12h only, (iii) one or more distributed database access node 12a and one or more non-distributed database access node 12h, (iv) a virtual access node 100 (described below) only, and (v) a virtual access node 100 in combination with any one or more of either or both distributed database access node 12a and non-distributed database access node 12h.

FIG. 4 illustrates non-limiting examples of external information systems 50a. External information systems 50a may take many different forms from purely administrative ones, e.g., billing and reimbursement, to dedicated and specialized medically related systems, such as, laboratory analysis systems and clinic information systems. Examples listed in FIG. 4 include, but are not limited to, local clinic information systems, cloud based clinic information systems, electronic medical record systems, health information systems, medical quality monitoring systems, laboratory analysis systems, national registry systems, billing and reimbursement systems, and inventory systems.

External information systems 50a in an embodiment connect to cluster 10 via wired or wireless connection to one or more distributed database access node 12a of interface domain 110c.

FIG. 5 illustrates non-limiting examples of presentation equipment 50b. Presentation equipment 50b includes equipment, handheld or stationary (e.g. mounted on a wall), with a primary (but not exclusive) purpose of presenting information to staff and/or patients within a treatment clinic. Presentation equipment 50b in general does not generate data for input into the medical devices of cluster 10, however, they may optionally be used for input if, for example, they have touch support capability. Presentation equipment 50b may for example present patient information for guiding arriving patients through various steps during treatment. For example, the patient arriving at the clinic may have access to scheduling information including pre-post weight registration location/status and treatment station location for receiving treatment. Staff information screens may present patient preparation status, dialysis station occupancy and treatment progress, and alarm information for various treatment locations in the clinic.

Presentation equipment 50b in an embodiment connects to cluster 10 via wired or wireless connection to one or more distributed database access node 12a of interface domain 110c.

FIG. 6 illustrates non-limiting examples of tablet and personal computer (“PC”) equipment 50c. Tablet and PC equipment 50c may require more input intensive and advanced information exchange that what is at presently practical using handheld, e.g., smartphone or tablet, devices. However, the advancement of tablets and of hybrid tablet/PC technology brings both types of devices under equipment 50c. Software deployed on equipment 50c may range from very simple applications to highly advanced applications including a complete CIS interface and environment towards accessing the information stored within cluster 10. Such applications may present a user interface for clinic staff (physicians, nurses, technical service staff, and administrative staff, etc.) to access and update information or feature in service areas, such as, administration services, staff and patient attention services, connectivity services, equipment technical service and maintenance services, billing and reimbursement services, identification services, information management services, inventory services, scheduling services, security services, patient medication services, therapy services and water purification services.

Tablet and PC equipment 50c in an embodiment connects to cluster 10 via (i) wired or wireless connection to one or more distributed database access node 12a of interface domain 110c or (ii) virtual access connection without access node hardware. Mobile connections enable a physician to make bedside changes to the original operating parameter prescriptions, changes that are then immediately distributed into shared data 14 and that take effect at the appropriate medical device of a node 12. A laptop or stationary PC may be used alternatively where mobility is not a top priority, e.g., for longer sessions interacting with cluster 10.

FIG. 7 illustrates non-limiting examples of shared, e.g., medical, equipment 50d. Shared, e.g., medical, equipment 50d includes equipment shared between patients present at the same time in a clinic. Shared equipment 50d may have medical or non-medical purposes. Although equipment for shared medical or medically related purposes is prevalent, a variety of other equipment, such as equipment that serves administrative purposes and/or supports the clinical therapy process, also falls under this category.

One example is patient weight pre-treatment and post-treatment registration. A weight scale may be shared by multiple patients in a clinic or other treatment setting. Each patient is identified at the time of weighing, e.g., by entering the patient's name or patient identification (“ID”) into the weighing equipment or via, e.g., a patient ID card presented to equipment present at the weighing station. The registered and identified weight is then transferred to distributed database 14 of cluster 10 and stored for example in a weight file for that patient. The medical device of whichever node 12 that the patient is assigned to retrieves the patient's pre-treatment weight for that day and for example enters the weight into the machine for use with the patient's prescription. Pre-treatment weight may be used in combination with a known dry weight to determine how much excess blood water or ultrafiltration to remove from the patient undergoing a dialysis treatment. Other examples of shared equipment include blood pressure measurement equipment, glucose measuring equipment, and patient log-in and log-out equipment for registration when the patient enters and leaves the clinic.

Shared equipment 50d in various embodiments connects to cluster 10 via wired or wireless connection to one or more distributed database access node 12a or non-distributed database node 12h of interface domain 110c. Non-distributed database access node 12h may be used if the shared equipment 50d has no need for any data from distributed database 14.

FIG. 8 illustrates non-limiting examples of bedside, e.g., medical, equipment 50e. Bedside equipment may, just like shared equipment 50d, have a medical or non-medical reason or purpose. Non-medical bedside or patient-dedicated equipment 50e may include, for example, personal communication, entertainment (e.g., HDMI connected televisions), patient work-related equipment, and patient identification equipment. Non-medical bedside or patient-dedicated equipment 50e may not need access to data from distributed database 14 and if so may connect to cluster 10 via wired or wireless connection to one or more non-distributed database node 12h of interface domain 110c. Shared data 14 may however benefit from interacting with non-medical bedside equipment 50e. In an example, distributed database 14 of cluster 10 may form a personal preferences file for each patient storing individual preferences with respect to favorite websites, television channels, radio stations, etc.

Bedside or patient-dedicated equipment 50e may of course be medical related. Certain clinics may provide blood pressure cuffs for each medical device of a node 12, so that blood pressure may be tracked during treatment. Another example is water purification equipment used to make dialysis fluid for dialysis. In either case, medical bedside or patient-dedicated equipment 50e may or may not need access to shared data 14 and therefore connect to cluster 10 via (i) wired or wireless connection to one or more distributed database access node 12a or one or more non-distributed database node 12h of interface domain 110c or (ii) a virtual access node as described herein.

Another example involves the delivery of drugs to the patient during a hemodialysis or other blood cleansing treatment, e.g., Epogen™ for red blood cells or Venofer™ for iron/sucrose. These drugs may be delivered by a dialysis machine pump of a node 12 or via an external pump. If provided by a dialysis machine pump, then drug delivery is already part of cluster 10. If by a separate pump, however, which for example is a floating pump used in the clinic as needed, the separate pump may access distributed database 14 via distributed database access node 12a or non-distributed database node 12h of interface domain 110c for two-way communication between the drug delivery pump and the dialysis machine of node 12. Dialysis machine of node 12 adds any desired drug delivery data to distributed database 14 of cluster 10, while the external drug delivery pump may record any desired data, such as patient response after delivery in the form of a blood pressure reading, a bioimpedance reading, hydration level reading, or a subjective response from the patient entered into the user interface of the dialysis machine. The drug delivery pump in an embodiment is part of its own cluster 10 of floating pumps and feeds data to its own distributed database 14.

A further example involves a hospital room or drug delivery setting in which a patient is receiving multiple drugs. Here, it is contemplated to implement one or more cluster 10. A first cluster 10 may be formed around the patient, where nodes 12 are formed by the different pumps or different channels of one or more pump along with any equipment analyzing the patient during drug delivery. The resulting distributed database 14 may be used for electronic medical records (“EMR”), billing and other purposes, and proprietary software may be written to achieve any goal for the shared data 14. For example, it may be desirable to (i) record any reactions to a delivered drug, e.g., blood pressure reading, a bioimpedance reading, hydration level reading, or a subjective response from the patient entered by a nurse or (ii) record any reactions to a combination of delivered drugs, e.g., blood pressure reading, a bioimpedance reading, hydration level reading, or a subjective response from the patient entered by a nurse. Time of drug delivery, dose, dose rate, etc., may also bee recorded for each drug.

A second cluster 10 may be formed around a particular drug where, for example, a drug manufacturer may find collective data concerning its drug to be very valuable. Here, nodes 12 reside at multiple bedsides, each delivering the drug to be analyzed. Proprietary software may be written to strip or simply not record any patient identification data but to record, for multiple patients, any reactions to the delivered drug, e.g., blood pressure reading, a bioimpedance reading, hydration level reading, or a subjective response from the patient entered by a nurse into distributed database 14. The proprietary software may be written to record patient type data, e.g., sex, age, race, ethnicity at distributed database 14. The software may also record data gleaned from the delivery of other drugs, e.g., any of the above reactions while the patient is receiving the manufacturer's drug in combination with one or more other drugs in distributed database 14. Here, such other drug information may come in through one or more access node 12a or 12h.

As noted above, both drug delivery clusters 10 just described may be run concurrently and simultaneously.

Referring now to FIGS. 2, 3 and 9, interface domain 110c is described in more detail. Cluster interface domain 110c acts as a façade to access the services of the cluster configuration without exposure of the internals of the actual cluster implementation, infrastructure and setup. As discussed above, access nodes 12a and 12h form part of interface domain 110c. Also discussed above, most of equipment 50a to 50e (referred to herein collectively as equipment 50 or generally individually as equipment 50) may be connected to distributed database via a distributed database access node 12a, a non-distributed database node 12h, or a virtual access node if the primary purpose of the access is information access only.

In an embodiment, distributed database access node 12a is a full-fledged member of cluster 10 and holds a replicated set of data 14 identical, in terms of content as well as service capabilities, to distributed database 14 hosted by medical equipment nodes 12b to 12g in FIGS. 1, 2, and 9. Cluster 10 via access nodes 12a and 12h will therefore still be available for external access even if all other medical device nodes 12b to 12g of cluster 10 are switched off. In an embodiment, non-distributed database node 12h provides an interface conversion between equipment 50 of external domain 110a (e.g., arbitrary equipment not meeting cluster 10 infrastructure requirements) and internal (protected) infrastructure of cluster domain 110b. Non-distributed database node 12h for example allows data from arbitrary shared equipment 50d and bedside equipment 50e along with patient identify data from a patient identity device to be sent to distributed database 14 for patient medical record storage.

In terms of connectivity capabilities, distributed database access node 12a and non-distributed database node 12h are identical in one embodiment. Each may connect to any of the above-described types of equipment 50a to 50e.

FIG. 2 illustrates that interface domain 110c includes a third type of access into distributed database 14 of domain 110b, namely, a virtual access node 100. Virtual access node 100 is virtual because there is no additional equipment representing a node, as is the case for access nodes 12a and 12h. Virtual access node 100 in an embodiment requires that responsibility for maintaining isolation between external domain 110a and cluster domain 110b be shared between the connected client equipment 50 and medical device nodes 12 of cluster 10. Client equipment 50 is in one embodiment connected to cluster domain 110b in such a way to guarantee the integrity of the information transferred to cluster 10. Secure connectivity may be provided via a virtual private network (“VPN”) connection made directly to the cluster 10 environment. Virtual access node 100 may for example allow a doctor, clinician, or technician computer that is connected within the clinic or medical device setting via a VPN to access distributed database 14. Such computers may run device prescription software that develops operational routines for the medical devices of nodes 12. The computers via virtual access node 100 may operate to send and receive lab results, for example, to be entered into the prescription software. Once the prescription operation routine is completed, it may be deposited via virtual access node 100 onto distributed database 14 under a folder for the patient or patients for which the operational routine has been developed. Client computers may also use the protected virtual access node 100 to pull data from distributed database 14 of cluster 10, e.g., to review treatment results from one or more operational routine to see if it needs to be modified or replaced.

Referring now to FIGS. 9 and 10, cluster compatible medical device nodes 12b to 12g . . . 12n are illustrated in more detail. FIG. 9 illustrates medical device nodes 12b to 12g . . . 12n operating within cluster 10 and highlights medical device node 12f, while FIG. 10 provides more detail on the distributed database 14 side of medical device node 12f. FIGS. 9 and 10 both illustrate that medical device node 12f includes two separate (separated by hardware and/or software) parts, namely, a therapy control part 28a and a cluster control part 28b. Therapy control part 28a in the illustrated embodiment includes a server interface hosted on middleware 16. Server interface and middleware 16 operates with medical device operating software 20, which may include any one or more of a main medical device control processor and memory, one or more safety processor and memory, a user interface processor and memory and one or more lower level controllers, such as, sensor boards, pump control boards, etc., for sensors and actuators 22 (FIG. 10). Any and all of the above functions may be combined alternatively on a single processor and memory.

Server interface and middleware 16 in the illustrated embodiment drives user interface 18 of medical device nodes 12. User interface 18 may, for example, display set-up screens, treatment screens, technical data, etc. If the patient wishes to view web pages from websites desired by the patient, e.g., via an internet connection provided by the hospital or clinic, the patient may do so at a user interface 18 of an access node, such as distributed database access node 12a, provided as part of cluster 14 in FIG. 9. Such websites may be stored in a preferences file for the patient in distributed database 14, so that the preferred website is known regardless of which access node of cluster 10 the patient uses next. An access node 12a, 12h may be placed at each medical device node 12b to 12g . . . 12n to provide internet access for use by the patient and/or caregiver.

Cluster control part 28b houses replicated database 14, which in FIG. 9 is shared by medical devices at nodes 12a to 12g and 12n-2 to 12n of cluster 10. Cluster control part 28b is structured carefully to meet requirements for security, safety, availability, integrity and others for the protected internal cluster infrastructure. Additionally, because therapy control part 28a runs treatments, it is responsible for the patient's safety and therefore should not face competition over resources (clock cycles, memory consumption, etc.) with distributed database 14. In an embodiment a processing and memory manager 120 may therefore be applied between therapy control part 28a and cluster control part 28b of medical device node 12f. Processing and memory manager 120 may for example be supported by a Linux™ operating system or other operating system capable of handling hardware-supported processing and memory protection and virtualization. Processing and memory manager 120 in an embodiment copies (i) data originating from the therapy control part 28a into cluster control part 28b and (ii) data that originates from cluster control part 28b into therapy control part 28a, in a way that preserves isolation between parts 28a and 28b (e.g., parts 28a and 28b never share or see each other's memory areas).

In one embodiment, server interface and middleware 16 of therapy control part 28a knows when it is free to share data with distributed database 14 and is therefore given the responsibility of initiating a data transfer with internal part 112b. Server interface and middleware 16 of therapy control part 28a sends data to cluster control part 28b via memory processing and memory manager 120 when it has data to send and opens itself to receiving data from distributed database 14 when it is ready.

FIG. 10 illustrates cluster control part 28b in more detail. Besides distributed database 14, cluster control part 28b includes a cluster database manager 24 and a cluster communication interface 26. Cluster database manager 24 and cluster communication interface 26 may be separate pieces of software, in which cluster database manager 24 is responsible for receiving data from middleware software 16 via processing and memory manager 120 and securely converting the data into a storage format suitable for distributed database 14. Cluster database manager 24 is also responsible for securely converting data retrieved from distributed database 14 into a form suitable for middleware software 16 and medical device operating software 20 of therapy control part 28a.

Cluster communication interface 26 in an embodiment is a messaging supervisor for controlling how data is to be sent to and received from other nodes 12 of cluster 10. Discussed above are many different ways that data may be distributed between the different nodes 12 of cluster 10. Cluster communication interface 26 knows the selected data transport configuration and causes its node 12f to send and/or receive data, securely and completely, at the appropriate time and/or in the appropriate order with other nodes 12.

Referring now to FIGS. 11 and 12, distributed database access node 12a is illustrated in more detail. Distributed database node 12a includes and is part of distributed database 14 and interacts with external equipment 50 as has been discussed herein. Distributed database node 12a includes its own server interface and middleware 116 hosted operating with cluster access node logic 118 (operating software for the access node). Distributed database access node 12a, similar to medical device nodes 12b to 12g and 12n-2 to 12n, includes an external part 112a and an internal part 112b separated by processing and memory manager 120 as described above, so that a clear and distinct separation between distributed database 14 and server interface and middleware 116 is established. Distributed database access node 12a is able to retrieve and send information from distributed database 14 to external equipment 50. Distributed database access node 12a may receive and store in shared distributed database 14 data from external equipment 50, such as the CIS, and server clients such as a computer, a display device, a handheld smart device, such as a smartphone or smart tablet, and/or medical equipment, such as a weight scale.

Connectivity between external part 112a and external equipment 50 may for example be via wired local area network (“LAN”), wireless local area network (“WLAN”), or Bluetooth technology, etc. If connection is made via a physical LAN cable between external equipment 50 and distributed database access node 12a, the cable may be a separate cable from any other external equipment cable and be connected to a dedicated port of the access node 12a.

FIGS. 11 and 12 illustrate that distributed database access node 12a may include its own user interface 18, which operates with server interface and middleware 116. As discussed above, user interface 18 of distributed database access node 12a may display internet sites to a patient undergoing treatment or to a caregiver, e.g., needing assistance. User interface 18 may also display set-up screens, treatment screens, technical data, etc., to the patient or caregiver. Again, the selection of any external content by the patient or caregiver may be stored in a preferences file in shared database 14.

Data transfer between external equipment 50 and distributed database 14 may occur without application interference directly via cluster access node logic 118. Access node interface and middleware 116 and access node logic 118 may host access node configuration software and applications, e.g., web clients (internet explorer, google chrome, etc.), for user interaction via a user interface 18 integrated or externally connected to access node 12a. Cluster access node logic 118 may error check the data and if needed combine data into a form useable with distributed database 14. For example, there may be a first external equipment 50 that provides a treatment operating prescription to distributed database access node 12a and a second external equipment 50 that provides patient weight data. Cluster access node logic 118 may assist in sorting and assembling related data, e.g., data associated with a same patient ID, and route the to a particular entry in distributed database 14.

FIGS. 11 and 12 further illustrate that distributed database access node 12a may however store different external device/system interface software, e.g., software 150a and 150e (referred to herein collectively as external device/system interface software 150 or generally individually as external device/system interface software 150) for different external equipment, e.g., 50a and 50e, respectively. External device/system interface software 150 is provided for certain external equipment 50 to send and receive information to and from distributed database 14. The interplay between external device/system interface software 150 and cluster access node logic 118 provides a first layer of isolation (as indicated by upper dotted line in external part 112a in FIG. 12). The purpose of this first isolation is to prevent erroneous or malicious external devices from affecting access node logic 118.

Internal part 112b, separated by processing and memory manager 120 from external part 112a, of distributed database access node 12a operates in the same manner as cluster control part 28b described above for medical device node 12f. In particular, database manager 24 may be responsible for receiving data from cluster access node logic 118 via processing and memory manager 120 and securely converting the data into a form suitable for distributed database 14. Cluster communication interface 26 is again a messaging supervisor for knowing how data is to be sent to and received from different nodes 12 of cluster 10. Processing and memory manager 120 provides a second layer of isolation to distributed database access node 12a.

Referring now to FIG. 13, non-distributed database access node 12h is illustrated in more detail. Non-distributed database node 12h does not have its own memory storage for distributed database 14 but does interact with external equipment 50 as has been discussed herein. Non-distributed database node 12h may send and receive data to and from distributed database 14, respectively, and data from distributed database 14 may be displayed on its user interface 18. But distributed database 14 is not resident at non-distributed database node 12h and therefore may not be accessed without access to other nodes. With distributed database access node 12a, on the other hand, database 14 is accessible even if access node 12a is the only available node 12 of cluster 10.

External device/system interface software 150, server interface and middleware 116, cluster access node logic 118, processing and memory manager 120, database manager 24 and cluster communication interface 26 of non-distributed database access node 12h operate the same in one embodiment as described or referenced above for distributed database access node 12a.

In the above embodiments, therapy control part 28a/external part 112a may be provided on its own one or more processor and memory separate from one or more processor and memory used for cluster control part 28b/internal part 112b. In an alternative embodiment therapy control part 28a/external part 112a may be provided on the same processor and memory as cluster control part 28b/internal part 112b, but be maintained on different parts of the memory and still be separated by processing and memory manager 120.

Moreover, while access nodes 12a and 12h have been described as being physically separate from medical device nodes 12b to 12g and 12n-2 to 12n of cluster 10, the additional structure and functionality of access nodes 12a and 12h may be provided alternatively as a separate node housed in a common housing with one of the medical device nodes 12b to 12g and 12n-2 to 12n. In particular, server interface and middleware 116, cluster access node logic 118, and external device/system interface 150 may be added as an external part 112a, as described above, that operates alongside the therapy control part 28a of medical device node 12b to 12g and 12n-2 to 12n. In an embodiment, both control part 28a and external part 112a are separated from cluster database 14, cluster database manager 24 and cluster communications interface 26 via processing and memory manager 120 in the manner described herein. The access node 12a within the medical device is a separate node from the medical device node 12b to 12g and 12n-2 to 12n in one embodiment. It operates independent of the medical device node even though the two nodes share the same housing and may share cluster database manager 24 and cluster communications interface 26. Information received by the access node 12a is not necessarily intended for its host medical device and may be information needed by another medical device of cluster 10. The information is stored on distributed database 14. Likewise, access node 12a located within the medical device may pull data from distributed database 14 and send it to outside equipment 50 regardless of whether the information has been generated by the host medical device or another medical device of cluster 10.

Referring now to FIG. 14, the therapy control part 28a and cluster control part 28b of medical device nodes 12b to 12e and the external part 112a and internal part 112b of distributed database access node 12a of FIGS. 9 to 13 are illustrated together with the external domain 110a, cluster domain 110b, and interface domain 110c of FIG. 2. FIG. 14 represents cluster 10 via a circle and shows that cluster domain 110b includes cluster 10. Additionally, cluster domain 110b includes therapy control parts 28a of medical device nodes 12b to 12e. FIG. 14 reiterates that external domain 110a includes external equipment 50.

FIG. 14 also illustrates that cluster 10 includes cluster control parts 28b of medical device nodes 12b to 12e and internal part 112b (including distributed database 14) of distributed database access node 12a (would also include internal part 112b of non-distributed database access node 12h). External part of distributed database access node 12a in the illustrated embodiment is not part of cluster domain 110b and instead forms interface domain 110c along with the external parts 112a of any other access nodes of cluster 10. FIGS. 2 and 3 illustrate distributed database access node 12a having distributed database 14 within interface domain 110c. Distributed database 14 is shown this way in FIGS. 2 and 3 to differentiate distributed database access node 12a from non-distributed database access node 12h. It should be appreciated from FIG. 14, however, that distributed database 14 of full access node 12a belongs within cluster 10 of cluster domain 110b.

Referring now to FIG. 15, one embodiment for virtual access node 100 is illustrated. Virtual access node 100 in the illustrated embodiment includes an interface between a medical device node, such as medical device node 12f and a piece of external (open side) equipment 50, such as an external computer (doctor, nurse or technician computer). Medical device node 12f is provided with each of the structures and associated functionality described above in connection with FIG. 10 for middleware 16, user interface 18, server interface 20, actuators 22, distributed database 14, cluster database manager 24, and cluster communications interface.

Computer 50 in the illustrated embodiment has installed thereon third party application software 114, such as software for developing treatment operating prescriptions. Third party application software 114 may for example receive data from distributed database 14 and use it to analyze or form new treatment operating prescriptions. If the desired third party application software 114 does not exist or the hospital or clinic does not own such software, it is contemplated to provide virtual access node 100 with proprietary data handling software 102 that performs the same and/or additional functions as third party application software 114 using the data retrieved from distributed database 14. In either case, proprietary data handling software 102 and third party application software 114 may in turn create data that is stored at distributed database 14.

A third party system interface 104 converts data from third party application software 114 into a form required by a secure communication channel, e.g., a virtual private network (“VPN”) 106, present between medical device virtual access node interface 108a and an external equipment virtual access node interface 108b. VPN 106 is in essence an encrypted bridge between medical device node 12f and external equipment 50. VPN 106 may be provided and installed by the installer of cluster 10. Proprietary data handling software 102 in the illustrated embodiment, after conversions performed by third party system interface 104, is structured to communicate directly over VPN 106 between medical device virtual access node interface 108a and an external equipment virtual access node interface 108b.

Once inside medical device node 12f, data from external equipment virtual access node interface 108b is sent securely from therapy control part 28a to cluster control part 28b via processing and memory manager 120, is made available to distributed database 14 via cluster database manager 24, and is sent to other nodes via cluster communications interface 26 in a manner described above. Data from distributed database 14 may be converted via cluster database manager 24 and be sent securely from cluster control part 28b to therapy control part 28a via processing and memory manager 120, sent from interface 108a to interface 108b over VPN 106 and from there to one or both proprietary data handling software 102 and/or third party application software 114 via conversion at third party system interface 104.

It should be understood that various changes and modifications to the presently preferred embodiments described herein will be apparent to those skilled in the art. Such changes and modifications may be made without departing from the spirit and scope of the present subject matter and without diminishing its intended advantages. It is therefore intended that such changes and modifications be covered by the appended claims.

Claims

1. A medical device system comprising: a cluster including a plurality of nodes, wherein the cluster is configured to run proprietary software that creates a closed configuration for the cluster;a plurality of medical devices implementing at least some of the nodes, at least one of the nodes being an access node;a distributed database shared along the cluster and hosted by at least some of the nodes; andat least one external equipment separate from the cluster, the at least one external equipment running software different than the proprietary software, wherein the different software is unable to directly communicate with the cluster having the closed configuration, and wherein the different software is configured to perform at least one of (i) writing to at least some of the distributed database via the access node or (ii) reading from at least some of the distributed database via the access node.
2. The medical device system of claim 1, wherein the at least one access node is provided separately from the medical devices.
3. The medical device system of claim 1, wherein the at least one access node is provided with one of the medical devices.
4. The medical device system of claim 1, wherein the at least one access node does not host the distributed database.
5. The medical device system of claim 1, wherein the at least one external equipment is a first external equipment, wherein the medical device system further includes a virtual access node of the cluster formed via a second external equipment, and wherein the virtual access node provides a secure data exchange environment so as to ensure security of the cluster while operating with the second external equipment.
6. The medical device system of claim 5, wherein the secure data exchange environment includes a secure channel, such as a virtual private network.
7. The medical device system of claim 1, wherein the at least one external equipment is configured to deliver data to the distributed database, and wherein the data is used by one of the medical devices implementing one of the nodes for treatment.
8. The medical device system of claim 1, wherein the plurality of medical devices are of a same treatment type.
9. The medical device system of claim 1, wherein the plurality of medical devices are configured to treat a common patient.
10. The medical device system of claim 1, wherein the distributed database is populated by (i) at least a first subset of the nodes that produce data and push data to other nodes, (ii) a second subset of the nodes hosting the distributed database pulling data from other nodes, or (iii) a combination of (i) and (ii).
11. A medical device system comprising: a cluster including a plurality of nodes, wherein the cluster is configured to run proprietary software that creates a closed configuration for the cluster;each of at least a set of the plurality of nodes implemented by at least one of a plurality of medical devices;a distributed database hosted by each of the plurality of medical devices, at least one first access node configured to also host the distributed database;at least one second access node provided separately from the distributed database; andat least one external equipment separate from the cluster, the at least one external equipment running software different than the proprietary software, wherein the different software is unable to directly communicate with the cluster having the closed configuration, and wherein the different software is configured to perform at least one of (i) writing to the distributed database via the at least one first access node or the at least one second access node, or (ii) reading from the distributed database via the at least one first access node or the at least one second access node.
12. The medical device system of claim 11, wherein the at least one first access node and the at least one second access node are located separately from the medical devices.
13. The medical device system of claim 11, wherein the at least one first access node and the at least one second access node are provided with or operate with a user interface.
14. A medical device system comprising: a cluster including a plurality of nodes, wherein the cluster is configured to run proprietary software that creates a closed configuration for the cluster;a plurality of medical devices implementing at least at least some of the nodes, at least one of the nodes being an access node including an external part and an internal part;a distributed database provided along the cluster and hosted by at least some of the nodes, the distributed database, when stored by the at least one access node, associated with the internal part of the access node; andat least one external equipment separate from the cluster, the at least one external equipment running software different than the proprietary software, wherein the different software is unable to directly communicate with the cluster having the closed configuration, and wherein the different software is configured to perform at least one of (i) writing to at least some of the distributed database via the external part of the access node or (ii) reading from at least some of the distributed database via the external part of the access node.
15. The medical device system of claim 14, wherein the external part and the internal part are separated by a processing and memory manager configured to (i) provide data to the external part coming from the internal part and (ii) provide data to the internal part coming from the external part.
16. A medical device system comprising: a cluster including a plurality of nodes, wherein the cluster is configured to run first software that creates a closed configuration for the cluster;a plurality of medical devices implementing at least some of the nodes, each medical device including a first processor and a memory configured to perform a medical procedure; anda distributed database shared along the cluster by at least some of the nodes, the distributed database deployed on the plurality of medical devices, the distributed database separated from the first processor and memory configured to perform the medical procedure by a second processor and a memory manager running second software different than the first software, wherein the second software is unable to directly communicate with the cluster having the closed configuration, and wherein the second software is configured to (i) provide, to the first processor and memory, data coming from the distributed database and (ii) provide, to the distributed database, data coming from the first processor and memory.
17. The medical device system of claim 16, wherein the first processor and memory are configured to initiate communication with the distributed database via the second processor and the memory manager.
18. The medical device system of claim 16, wherein the distributed database is located in a cluster control part of the medical device that is separate from the first processor and memory located in a therapy control part of the medical device, the cluster control part separated from the therapy control part by the second processor and the memory manager.
19. A medical device system comprising: a cluster including a plurality of nodes, wherein the cluster is configured to run first software that creates a closed configuration for the cluster;a plurality of medical devices implementing at least some of the nodes;a distributed data base shared along the cluster and hosted by the plurality of medical devices;an external equipment separate from the cluster; anda virtual access node of the cluster formed with the external equipment and one of the medical devices, the virtual access node providing a secure data exchange environment so as to ensure security of the distributed database, the virtual access node running second software different than the first software, wherein the second software is unable to directly communicate with the cluster having the closed configuration, and wherein the second software (i) writes to the medical device or (ii) reads from the medical device.
20. The medical device system of claim 19, wherein the medical device includes a first virtual access node interface and the external equipment includes a second virtual access node interface, and wherein the secure data exchange environment includes a secure channel such as a virtual private network interfacing with the virtual access node interfaces.

Priority Claims (1)

Number	Date	Country	Kind
16516999	Dec 2016	SE	national

PCT Information

Filing Document	Filing Date	Country	Kind
PCT/EP2017/081763	12/7/2017	WO

Publishing Document	Publishing Date	Country	Kind
WO2018/114346	6/28/2018	WO	A

US Referenced Citations (1695)

Number	Name	Date	Kind
250868	Abbott	Dec 1881	A
927476	Barker	Jul 1909	A
1505050	Lauritsen	Aug 1924	A
2292007	Morgan	Aug 1942	A
2529028	Landon	Jul 1947	A
2122509	Beliaeff	Jul 1948	A
2736332	Simmons	Feb 1956	A
3044236	Bearden et al.	Jul 1962	A
3074645	Main	Jan 1963	A
3095062	Neely	Jun 1963	A
3229445	Kraft	Jan 1966	A
3287885	Sommer	Nov 1966	A
3295297	Collins	Jan 1967	A
3332737	Krause	Jul 1967	A
3342019	Smythe	Sep 1967	A
3388803	Scott	Jun 1968	A
3412760	Franck	Nov 1968	A
3426150	Tygart	Feb 1969	A
3463728	Kolobow et al.	Aug 1969	A
3485245	Lahr et al.	Dec 1969	A
3490479	Mott et al.	Jan 1970	A
3527572	Urkiewicz	Sep 1970	A
3528550	Cappelen Jr.	Sep 1970	A
3540477	Hogel	Nov 1970	A
3545438	De Vries	Dec 1970	A
3563381	Edelson et al.	Feb 1971	A
3581464	Bhuta et al.	Jun 1971	A
3598727	Wilock	Aug 1971	A
3608729	Haselden	Sep 1971	A
3617545	Dabois et al.	Nov 1971	A
3619423	Galletti et al.	Nov 1971	A
3667612	Leonard	Jun 1972	A
3669878	Marantz et al.	Jun 1972	A
3669880	Marantz et al.	Jun 1972	A
3677710	Hirsch	Jul 1972	A
3682817	Marx	Aug 1972	A
3685680	Tenckhoff et al.	Aug 1972	A
3697418	Johnson	Oct 1972	A
3703959	Raymond	Nov 1972	A
3707967	Kitrilakis et al.	Jan 1973	A
3727612	Sayers et al.	Apr 1973	A
3730183	Goldsmith et al.	May 1973	A
3739943	Williamsen et al.	Jun 1973	A
3742938	Stern	Jul 1973	A
3744492	Leibinsohn	Jul 1973	A
3744636	Commarmot	Jul 1973	A
3756234	Kopp	Sep 1973	A
3756752	Stenner	Sep 1973	A
3769207	Baer	Oct 1973	A
3771288	Wisman et al.	Nov 1973	A
3774762	Lichtenstein	Nov 1973	A
3786190	Pori	Jan 1974	A
3795088	Esmond	Mar 1974	A
3799873	Brown	Mar 1974	A
3809241	Alvine	May 1974	A
3809871	Howard et al.	May 1974	A
3810102	Parks, III et al.	May 1974	A
3814249	Eaton	Jun 1974	A
3825493	Brown et al.	Jul 1974	A
3827561	Serfass et al.	Aug 1974	A
3827975	Bizot et al.	Aug 1974	A
3830234	Kopp	Aug 1974	A
3834386	Sisley	Sep 1974	A
3848112	Weichselbaum et al.	Nov 1974	A
3849071	Kayser	Nov 1974	A
3850835	Marantz et al.	Nov 1974	A
3858574	Page	Jan 1975	A
3878095	Frasier et al.	Apr 1975	A
3878564	Yao et al.	Apr 1975	A
3884808	Scott	May 1975	A
3908653	Kettering	Sep 1975	A
3910257	Fletcher et al.	Oct 1975	A
3911915	Seifter et al.	Oct 1975	A
3915802	Kominek	Oct 1975	A
3910260	Sarnoff et al.	Nov 1975	A
3921196	Patterson	Nov 1975	A
3926797	Gigou et al.	Dec 1975	A
3939069	Granger et al.	Feb 1976	A
3946731	Lichtenstein	Mar 1976	A
3964479	Boag et al.	Jun 1976	A
3971000	Cromwell	Jul 1976	A
3976311	Spendlove	Aug 1976	A
3979284	Granger et al.	Sep 1976	A
3985134	Lissot et al.	Oct 1976	A
3989622	Marantz et al.	Nov 1976	A
3996027	Schnell et al.	Dec 1976	A
3998103	Bjorklund et al.	Dec 1976	A
4000072	Sato et al.	Dec 1976	A
4031010	Nose	Jun 1977	A
4031891	Jess	Jun 1977	A
4032908	Rice et al.	Jun 1977	A
4036747	Hori et al.	Jul 1977	A
4038190	Baudet et al.	Jul 1977	A
4047563	Kurata	Sep 1977	A
4048995	Mittleman	Sep 1977	A
4054522	Pinkerton	Oct 1977	A
4060485	Eaton	Nov 1977	A
4061031	Grimsrud	Dec 1977	A
4067803	Quentin	Jan 1978	A
4078562	Friedman	Mar 1978	A
4081372	Atkin et al.	Mar 1978	A
4102655	Jeffrey et al.	Jul 1978	A
4115259	Bigi	Sep 1978	A
4118314	Yoshida	Oct 1978	A
4137160	Ebing et al.	Jan 1979	A
4144496	Cunningham et al.	Mar 1979	A
4149860	Kulik	Apr 1979	A
4151088	Wolf, Jr. et al.	Apr 1979	A
4151407	McBride et al.	Apr 1979	A
4156867	Bench et al.	May 1979	A
4164320	Irazoqui et al.	Aug 1979	A
4173537	Newhart et al.	Nov 1979	A
4173971	Karz	Nov 1979	A
4180460	Calari	Dec 1979	A
4181245	Garrett et al.	Jan 1980	A
4190047	Jacobsen et al.	Feb 1980	A
4191182	Popovich et al.	Mar 1980	A
4191646	Larsson et al.	Mar 1980	A
4192748	Hyden	Mar 1980	A
4194536	Stine et al.	Mar 1980	A
4199307	Jassawalla	Apr 1980	A
4200095	Reti	Apr 1980	A
4209402	Gentles	Jun 1980	A
4212738	Henne	Jul 1980	A
4213859	Smakman et al.	Jul 1980	A
4229299	Savitz et al.	Oct 1980	A
4240408	Schael	Dec 1980	A
4244816	Vogler et al.	Jan 1981	A
4247393	Wallace	Jan 1981	A
4256718	McArthur et al.	Mar 1981	A
4267040	Schal	May 1981	A
4267047	Henne et al.	May 1981	A
4269708	Bounomini et al.	May 1981	A
4270532	Franetzki et al.	Jun 1981	A
4273121	Jassawalla	Jun 1981	A
4276175	Bower	Jun 1981	A
4282872	Franetzki et al.	Aug 1981	A
4293413	Schnell	Oct 1981	A
4293762	Ogawa	Oct 1981	A
4303376	Siekmann	Dec 1981	A
4303521	Lehmann	Dec 1981	A
4304670	Watanabe et al.	Dec 1981	A
4308866	Jelliffe et al.	Jan 1982	A
4311137	Gerard	Jan 1982	A
4313831	Lehmann et al.	Feb 1982	A
4319338	Grudowski et al.	Mar 1982	A
4320757	Whitney et al.	Mar 1982	A
4325715	Bowman et al.	Apr 1982	A
4332264	Gortz	Jun 1982	A
4338190	Kraus et al.	Jul 1982	A
4344777	Siposs	Aug 1982	A
4345919	Wilkinson et al.	Aug 1982	A
4345999	Sigdell et al.	Aug 1982	A
4348280	George et al.	Sep 1982	A
4353368	Slovak et al.	Oct 1982	A
4354252	Lamb et al.	Oct 1982	A
4360323	Anderson	Nov 1982	A
4360507	McArthur et al.	Nov 1982	A
4363641	Finn, III	Dec 1982	A
4364747	Blackshear et al.	Dec 1982	A
4368118	Siposs	Jan 1983	A
4369780	Sakai	Jan 1983	A
4370983	Lichtenstein	Feb 1983	A
4373527	Fischell	Feb 1983	A
4381003	Buoncristiani	Apr 1983	A
4381776	Latham, Jr.	May 1983	A
4385630	Gilcher et al.	May 1983	A
4386634	Stasz et al.	Jun 1983	A
4398289	Schoate	Aug 1983	A
4398908	Siposs	Aug 1983	A
4416654	Schoendorfer et al.	Nov 1983	A
4425114	Schoendorfer et al.	Jan 1984	A
4427009	Wells et al.	Jan 1984	A
4428381	Hepp	Jan 1984	A
4433971	Lindsay et al.	Feb 1984	A
4443216	Chappell	Apr 1984	A
4447224	DeCant, Jr. et al.	May 1984	A
4449538	Corbitt et al.	May 1984	A
4451255	Bujan et al.	May 1984	A
4457750	Hill	Jul 1984	A
4458693	Badzinski et al.	Jul 1984	A
4460358	Somerville et al.	Jul 1984	A
4460555	Thompson	Jul 1984	A
4464172	Lichtenstein	Aug 1984	A
4464563	Jewett	Aug 1984	A
4469481	Kobayashi	Sep 1984	A
4473449	Michaels et al.	Sep 1984	A
4475901	Kraegen et al.	Oct 1984	A
4476381	Rubin	Oct 1984	A
4477342	Allan et al.	Oct 1984	A
4480751	Lueptow	Nov 1984	A
4481670	Freeburg	Nov 1984	A
4487604	Iwatschenko et al.	Dec 1984	A
4490798	Franks et al.	Dec 1984	A
4493705	Gordon et al.	Jan 1985	A
4496351	Hillel et al.	Jan 1985	A
4498900	Bouncristiani	Feb 1985	A
4511352	Theeuwes et al.	Apr 1985	A
4512163	Wells et al.	Apr 1985	A
4525861	Freeburg	Jun 1985	A
4529401	Leslie et al.	Jul 1985	A
4531527	Reinhold, Jr. et al.	Jul 1985	A
4531937	Yates	Jul 1985	A
4532414	Shah et al.	Jul 1985	A
4538138	Harvey et al.	Aug 1985	A
4542015	Smakman et al.	Sep 1985	A
4545071	Freeburg	Oct 1985	A
4551133	Zegers de Beyl et al.	Nov 1985	A
4559038	Berg et al.	Dec 1985	A
4560979	Rosskopf	Dec 1985	A
4561443	Hogrefe et al.	Dec 1985	A
4562751	Nason	Jan 1986	A
4568333	Sawyer et al.	Feb 1986	A
4581141	Ash	Apr 1986	A
4583981	Urquhart et al.	Apr 1986	A
4586920	Peabody	May 1986	A
4586925	Carlsson et al.	May 1986	A
4590473	Burke et al.	May 1986	A
4602249	Abbott	Jul 1986	A
4618343	Polaschegg	Oct 1986	A
4619653	Fischell	Oct 1986	A
4622032	Katsura et al.	Nov 1986	A
4622979	Katchis et al.	Nov 1986	A
4624661	Arimond	Nov 1986	A
RE32303	Lasker et al.	Dec 1986	E
4636950	Caswell et al.	Jan 1987	A
4637817	Archibald et al.	Jan 1987	A
4643713	Viitala	Feb 1987	A
4643715	Isono et al.	Feb 1987	A
4650458	Dahlberg et al.	Mar 1987	A
4650464	Ruiz et al.	Mar 1987	A
4650469	Berg et al.	Mar 1987	A
4650857	May	Mar 1987	A
4652262	Veracchi	Mar 1987	A
4655941	Suzuki	Apr 1987	A
4657490	Abbott	Apr 1987	A
4661246	Ash	Apr 1987	A
4664891	Cosentino et al.	May 1987	A
4666598	Heath et al.	May 1987	A
4670007	Wheeldon et al.	Jun 1987	A
4676776	Howson	Jun 1987	A
4678460	Rosner	Jul 1987	A
4680445	Ogawa	Jul 1987	A
4681563	Deckert et al.	Jul 1987	A
4681606	Swan, Jr. et al.	Jul 1987	A
4684460	Issautier	Aug 1987	A
4688167	Agarwal	Aug 1987	A
4691580	Fosslien	Sep 1987	A
4695954	Rose et al.	Sep 1987	A
4696671	Epstein et al.	Sep 1987	A
4697928	Csongor	Oct 1987	A
4702595	Mutschler et al.	Oct 1987	A
4702829	Polaschegg et al.	Oct 1987	A
4703913	Hunkapiller	Nov 1987	A
4705506	Archibald	Nov 1987	A
4708802	Rath et al.	Nov 1987	A
4714462	DiComenico	Dec 1987	A
4717042	McLaughlin	Jan 1988	A
4718576	Tamura et al.	Jan 1988	A
4718890	Peabody	Jan 1988	A
4722224	Scheller et al.	Feb 1988	A
4722349	Baumberg	Feb 1988	A
4722725	Sawyer et al.	Feb 1988	A
4722731	Vailancourt	Feb 1988	A
4722734	Kolln	Feb 1988	A
4730849	Siegel	Mar 1988	A
4731058	Doan	Mar 1988	A
4732411	Siegel	Mar 1988	A
4734198	Harm et al.	Mar 1988	A
4734269	Clarke et al.	Mar 1988	A
4735609	Comeau et al.	Apr 1988	A
4741732	Crankshaw et al.	May 1988	A
4741736	Brown	May 1988	A
4747822	Peabody	May 1988	A
4756706	Kerns et al.	Jul 1988	A
4759756	Forman	Jul 1988	A
4765907	Scott	Aug 1988	A
4767399	Bollish	Aug 1988	A
4769151	Shouldice	Sep 1988	A
4778449	Weber et al.	Oct 1988	A
4778451	Kamen	Oct 1988	A
4779626	Peel et al.	Oct 1988	A
4784645	Fischell	Nov 1988	A
4785799	Schoon et al.	Nov 1988	A
4785969	McLaughlin	Nov 1988	A
4796644	Polaschegg	Jan 1989	A
4797840	Fraden	Jan 1989	A
4803625	Fu et al.	Feb 1989	A
4804474	Blum	Feb 1989	A
4806135	Siposs	Feb 1989	A
4810090	Boucher	Mar 1989	A
4810243	Howson	Mar 1989	A
4811844	Moulding, Jr. et al.	Mar 1989	A
4816208	Woods et al.	Mar 1989	A
4817044	Ogren	Mar 1989	A
4828543	Weiss et al.	May 1989	A
4828545	Epstein et al.	May 1989	A
4830018	Treach	May 1989	A
4831562	McIntosh et al.	May 1989	A
4832033	Maher et al.	May 1989	A
4835372	Beard et al.	May 1989	A
4835521	Andrejasich et al.	May 1989	A
4838275	Lee	Jun 1989	A
4838865	Flank et al.	Jun 1989	A
4839806	Goldfischer et al.	Jun 1989	A
4844074	Kurucz	Jul 1989	A
4845644	Anthias et al.	Jul 1989	A
4847470	Bakke	Jul 1989	A
4847764	Halvorson	Jul 1989	A
4850009	Zook et al.	Jul 1989	A
4850972	Schulman et al.	Jul 1989	A
4853521	Claeys et al.	Aug 1989	A
4854324	Hirschman et al.	Aug 1989	A
4857713	Brown	Aug 1989	A
4857716	Gombrich et al.	Aug 1989	A
4865584	Epstein et al.	Sep 1989	A
4871351	Feingold	Oct 1989	A
4878175	Norden-Paul et al.	Oct 1989	A
4889132	Hutcheson et al.	Dec 1989	A
4889134	Greenwold et al.	Dec 1989	A
4893270	Beck et al.	Jan 1990	A
4897777	Janke et al.	Jan 1990	A
4898576	Philip	Feb 1990	A
4898578	Rubalcaba, Jr.	Feb 1990	A
4901728	Hutchison	Feb 1990	A
4906816	van Leerdam	Mar 1990	A
4908017	Howson et al.	Mar 1990	A
4912623	Rantala et al.	Mar 1990	A
4916441	Gombrich et al.	Apr 1990	A
4922922	Pollock et al.	May 1990	A
4923612	Trivett et al.	May 1990	A
4925444	Orkin et al.	May 1990	A
4932987	Molina	Jun 1990	A
4933843	Scheller et al.	Jun 1990	A
4937777	Flood et al.	Jun 1990	A
4941808	Qureshi et al.	Jul 1990	A
4941875	Brennan	Jul 1990	A
4943279	Samiotes et al.	Jul 1990	A
4946439	Eggers	Aug 1990	A
4949274	Hollander et al.	Aug 1990	A
4950259	Geary et al.	Aug 1990	A
4952928	Carroll et al.	Aug 1990	A
4953074	Kametani et al.	Aug 1990	A
4955508	Capanna et al.	Sep 1990	A
D311061	Vrana et al.	Oct 1990	S
4960230	Marelli	Oct 1990	A
4966579	Polaschegg	Oct 1990	A
4967928	Carter	Nov 1990	A
4968295	Neumann	Nov 1990	A
4976683	Gauthier et al.	Dec 1990	A
4976685	Block, Jr.	Dec 1990	A
4977590	Milovancevic	Dec 1990	A
4978335	Arthur	Dec 1990	A
4991091	Allen	Feb 1991	A
4992926	Janke et al.	Feb 1991	A
4993068	Piosenka et al.	Feb 1991	A
4997464	Kopf	Mar 1991	A
4998249	Bennett et al.	Mar 1991	A
5002055	Merki et al.	Mar 1991	A
5002471	Perlov	Mar 1991	A
5003296	Lee	Mar 1991	A
5004459	Peabody et al.	Apr 1991	A
5006699	Felkner et al.	Apr 1991	A
5007429	Treatch et al.	Apr 1991	A
5011607	Shinzato	Apr 1991	A
5012402	Akiyama	Apr 1991	A
5012411	Policastro et al.	Apr 1991	A
5014875	McLaughlin et al.	May 1991	A
5016172	Dessertine	May 1991	A
5023770	Siverling	Jun 1991	A
5025374	Roizen et al.	Jun 1991	A
5032265	Jha et al.	Jul 1991	A
5036852	Leishman	Aug 1991	A
5038800	Oba	Aug 1991	A
5041086	Koenig et al.	Aug 1991	A
5045048	Kaleskas et al.	Sep 1991	A
5047147	Chevallet et al.	Sep 1991	A
5047959	Phillips et al.	Sep 1991	A
5049492	Sauer et al.	Sep 1991	A
5053031	Borsanyi	Oct 1991	A
5053990	Kreifels et al.	Oct 1991	A
5055001	Natwick et al.	Oct 1991	A
5057076	Polaschegg	Oct 1991	A
5059173	Sacco	Oct 1991	A
5061236	Sutherland et al.	Oct 1991	A
5061243	Winchell et al.	Oct 1991	A
5061365	Utterberg	Oct 1991	A
5062774	Kramer et al.	Nov 1991	A
5072356	Watt et al.	Dec 1991	A
5072383	Brimm et al.	Dec 1991	A
5072412	Henderson, Jr. et al.	Dec 1991	A
5073167	Carr et al.	Dec 1991	A
5078683	Sancoff et al.	Jan 1992	A
5084828	Kaufman et al.	Jan 1992	A
5087245	Doan	Feb 1992	A
5088515	Kamen	Feb 1992	A
5088904	Okada	Feb 1992	A
5088981	Howson et al.	Feb 1992	A
5088990	Hivale et al.	Feb 1992	A
5091094	Veech	Feb 1992	A
5096385	Georgi et al.	Mar 1992	A
5098377	Borsanyi et al.	Mar 1992	A
5100380	Adaniya et al.	Mar 1992	A
5104374	Bishko et al.	Apr 1992	A
5108363	Tuttle et al.	Apr 1992	A
5108367	Epstein et al.	Apr 1992	A
5108372	Swenson	Apr 1992	A
5109487	Ohgomori et al.	Apr 1992	A
5109849	Goodman et al.	May 1992	A
5112319	Lai	May 1992	A
5112480	Hukasawa	May 1992	A
5114580	Ahmad et al.	May 1992	A
5116203	Natwick et al.	May 1992	A
5116312	Blankenship et al.	May 1992	A
5120303	Hombrouckx	Jun 1992	A
5122516	Watanabe et al.	Jun 1992	A
5125069	O'Boyle	Jun 1992	A
5131092	Sackmann et al.	Jul 1992	A
5134574	Beaverstock et al.	Jul 1992	A
5135500	Zdeb	Aug 1992	A
5137023	Mendelson et al.	Aug 1992	A
5141492	Dadson et al.	Aug 1992	A
5141493	Jacobson et al.	Aug 1992	A
5151978	Bronikowski et al.	Sep 1992	A
5152296	Simons	Oct 1992	A
5153416	Neeley	Oct 1992	A
5153827	Coutre et al.	Oct 1992	A
5155693	Altmayer et al.	Oct 1992	A
5157595	Lovrenich	Oct 1992	A
5158091	Butterfield et al.	Oct 1992	A
5159673	Sackmann et al.	Oct 1992	A
5160320	Yum et al.	Nov 1992	A
5161211	Taguchi et al.	Nov 1992	A
5167235	Seacord et al.	Dec 1992	A
5167921	Gordon	Dec 1992	A
5172698	Stanko	Dec 1992	A
5173125	Felding	Dec 1992	A
5176004	Gaudet	Jan 1993	A
5178763	Delaunay	Jan 1993	A
5179569	Sawyer	Jan 1993	A
5179700	Aihara et al.	Jan 1993	A
5180896	Gibby et al.	Jan 1993	A
5181910	Scanlon	Jan 1993	A
5190185	Blechl	Mar 1993	A
5190522	Wojcicki et al.	Mar 1993	A
5191891	Righter	Mar 1993	A
5204000	Steadman et al.	Apr 1993	A
5208907	Shelton et al.	May 1993	A
5211849	Benzing et al.	May 1993	A
5213099	Tripp, Jr.	May 1993	A
5213232	Kraft et al.	May 1993	A
5213568	Lattin et al.	May 1993	A
5219330	Bollish et al.	Jun 1993	A
5219331	Vanderveen	Jun 1993	A
5221267	Folden	Jun 1993	A
5225974	Mathews et al.	Jul 1993	A
5226425	Righter	Jul 1993	A
5228450	Sellers	Jul 1993	A
5228889	Cortial et al.	Jul 1993	A
5231990	Gauglitz	Aug 1993	A
5234404	Tuttle et al.	Aug 1993	A
5235510	Yamada et al.	Aug 1993	A
5236416	McDaniel et al.	Aug 1993	A
5236476	Klick	Aug 1993	A
5238001	Gallant et al.	Aug 1993	A
5240007	Pytel et al.	Aug 1993	A
5244463	Cordner, Jr. et al.	Sep 1993	A
5245693	Ford et al.	Sep 1993	A
5245704	Weber et al.	Sep 1993	A
5246560	Nekoksa et al.	Sep 1993	A
5254096	Rondelet et al.	Oct 1993	A
5256156	Kern et al.	Oct 1993	A
5256157	Samiotes et al.	Oct 1993	A
5256371	Pippert	Oct 1993	A
5259954	Taylor	Nov 1993	A
5259961	Eigendorf	Nov 1993	A
5265010	Evans-Paganelli et al.	Nov 1993	A
5265431	Gaudet et al.	Nov 1993	A
5267174	Kaufman et al.	Nov 1993	A
5268077	Bubik et al.	Dec 1993	A
5271405	Boyer et al.	Dec 1993	A
5272318	Gorman	Dec 1993	A
5272321	Otsuka et al.	Dec 1993	A
5273517	Barone et al.	Dec 1993	A
5274434	Morioka et al.	Dec 1993	A
5277188	Selker	Jan 1994	A
5277820	Ash	Jan 1994	A
5283861	Dangler et al.	Feb 1994	A
5284150	Butterfield et al.	Feb 1994	A
5284470	Beltz	Feb 1994	A
5286252	Tuttle et al.	Feb 1994	A
5292029	Pearson	Mar 1994	A
5295505	Polaschegg et al.	Mar 1994	A
5297257	Struger et al.	Mar 1994	A
5298021	Sherer	Mar 1994	A
5304126	Epstein et al.	Apr 1994	A
5307263	Brown	Apr 1994	A
5307372	Sawyer et al.	Apr 1994	A
5307463	Hyatt et al.	Apr 1994	A
5311908	Barone et al.	May 1994	A
5314243	McDonald et al.	May 1994	A
5315505	Pratt et al.	May 1994	A
5317506	Coutre et al.	May 1994	A
5318750	Lascombes	Jun 1994	A
5319543	Wilhelm	Jun 1994	A
5321618	Gessman	Jun 1994	A
5321829	Zifferer	Jun 1994	A
5325478	Shelton et al.	Jun 1994	A
5326473	Lascombes et al.	Jul 1994	A
5327341	Whalen et al.	Jul 1994	A
5330420	Lee	Jul 1994	A
5331549	Crawford, Jr.	Jul 1994	A
5336165	Twardowski	Aug 1994	A
5336173	Folden	Aug 1994	A
5336245	Adams et al.	Aug 1994	A
5337230	Baumgartner et al.	Aug 1994	A
5338157	Blomquist	Aug 1994	A
5338293	Jeppsson et al.	Aug 1994	A
5339821	Fujimoto	Aug 1994	A
5341291	Roizen et al.	Aug 1994	A
5341412	Ramot et al.	Aug 1994	A
D350822	Lanigan	Sep 1994	S
D350823	Lanigan	Sep 1994	S
5348008	Bornn et al.	Sep 1994	A
5348539	Herskowitz	Sep 1994	A
5349675	Fitzgerald et al.	Sep 1994	A
5350357	Kamen et al.	Sep 1994	A
5356376	Milijasevic et al.	Oct 1994	A
5356378	Doan	Oct 1994	A
5358481	Todd et al.	Oct 1994	A
5361202	Doue	Nov 1994	A
5361758	Hall et al.	Nov 1994	A
5366630	Chevallet	Nov 1994	A
5366896	Margrey et al.	Nov 1994	A
5366904	Qureshi et al.	Nov 1994	A
5367555	Isoyama	Nov 1994	A
5368555	Sussman et al.	Nov 1994	A
5368562	Blomquist et al.	Nov 1994	A
5370612	Maeda et al.	Dec 1994	A
5370674	Farrell	Dec 1994	A
5371687	Holmes, II et al.	Dec 1994	A
5374251	Smith	Dec 1994	A
5374813	Shipp	Dec 1994	A
5374965	Kanno	Dec 1994	A
5375604	Kelly et al.	Dec 1994	A
5376070	Colman et al.	Dec 1994	A
5376263	Fischel	Dec 1994	A
5377864	Blechl et al.	Jan 1995	A
5378231	Johnson et al.	Jan 1995	A
5379214	Arbuckle et al.	Jan 1995	A
5381510	Ford et al.	Jan 1995	A
5385564	Slater et al.	Jan 1995	A
5389078	Zalesky et al.	Feb 1995	A
5390238	Kirk et al.	Feb 1995	A
5392951	Gardner et al.	Feb 1995	A
5394732	Johnson et al.	Mar 1995	A
5395320	Padda et al.	Mar 1995	A
5395321	Kawahara et al.	Mar 1995	A
5398336	Tantry et al.	Mar 1995	A
5401059	Ferrario	Mar 1995	A
5401342	Vincent et al.	Mar 1995	A
D357312	Riquier et al.	Apr 1995	S
5404292	Hendrickson	Apr 1995	A
5404384	Colburn et al.	Apr 1995	A
5406473	Yoshikura et al.	Apr 1995	A
5408576	Bishop	Apr 1995	A
5411472	Steg, Jr. et al.	May 1995	A
5411705	Thor et al.	May 1995	A
5412715	Volpe	May 1995	A
5415167	Wilk	May 1995	A
5416695	Miller et al.	May 1995	A
5417222	Dempsey et al.	May 1995	A
5420962	Bakke	May 1995	A
5420977	Sztipanovits et al.	May 1995	A
5421343	Feng	Jun 1995	A
5421815	Noguchi et al.	Jun 1995	A
5423746	Burkett et al.	Jun 1995	A
5429595	Wright, Jr. et al.	Jul 1995	A
5429602	Hauser	Jul 1995	A
5431299	Brewer et al.	Jul 1995	A
5431627	Pastrone et al.	Jul 1995	A
5433736	Nilsson	Jul 1995	A
5438510	Bryant et al.	Aug 1995	A
5438607	Przygoda, Jr. et al.	Aug 1995	A
5440699	Farrand et al.	Aug 1995	A
5441047	David et al.	Aug 1995	A
5441636	Chevallet et al.	Aug 1995	A
5445294	Gardner et al.	Aug 1995	A
5445621	Poli et al.	Aug 1995	A
5446868	Gardea, II et al.	Aug 1995	A
5453098	Botts et al.	Sep 1995	A
5455851	Chaco et al.	Oct 1995	A
5458123	Unger	Oct 1995	A
5460294	Williams	Oct 1995	A
5460605	Tuttle et al.	Oct 1995	A
5461665	Shur et al.	Oct 1995	A
5462051	Oka et al.	Oct 1995	A
5464392	Epstein et al.	Nov 1995	A
5465286	Clare et al.	Nov 1995	A
5467773	Bergelson et al.	Nov 1995	A
5468110	McDonald et al.	Nov 1995	A
5468388	Goddard et al.	Nov 1995	A
5469855	Pompei et al.	Nov 1995	A
5470483	Bene et al.	Nov 1995	A
5471382	Tallman et al.	Nov 1995	A
5474552	Palti	Dec 1995	A
5474683	Bryant et al.	Dec 1995	A
5482043	Zulauf	Jan 1996	A
5482446	Williamson et al.	Jan 1996	A
5484397	Twardowski	Jan 1996	A
5485408	Blomquist	Jan 1996	A
5489385	Raabe et al.	Feb 1996	A
5490610	Pearson	Feb 1996	A
5490925	Eigendorf	Feb 1996	A
5494592	Latham, Jr. et al.	Feb 1996	A
5496265	Langley et al.	Mar 1996	A
5496273	Pastrone et al.	Mar 1996	A
5498338	Kruger et al.	Mar 1996	A
5502944	Kraft et al.	Apr 1996	A
5503801	Brugger	Apr 1996	A
5507412	Ebert et al.	Apr 1996	A
5508912	Schneiderman	Apr 1996	A
5509422	Fukami	Apr 1996	A
5509895	Noguchi et al.	Apr 1996	A
5513957	O'Leary	May 1996	A
5514088	Zakko	May 1996	A
5514095	Brightbill et al.	May 1996	A
5515426	Yacenda et al.	May 1996	A
5520450	Colson, Jr. et al.	May 1996	A
5520637	Pager et al.	May 1996	A
5520640	Utterberg	May 1996	A
5522396	Langer et al.	Jun 1996	A
5522798	Johnson et al.	Jun 1996	A
5522998	Polaschegg	Jun 1996	A
5526428	Arnold	Jun 1996	A
5528503	Moore et al.	Jun 1996	A
5529063	Hill	Jun 1996	A
5531680	Dumas et al.	Jul 1996	A
5531697	Olsen et al.	Jul 1996	A
5531698	Olsen	Jul 1996	A
5533079	Colburn et al.	Jul 1996	A
5533981	Mandro et al.	Jul 1996	A
5534691	Holdaway et al.	Jul 1996	A
5536084	Curtis et al.	Jul 1996	A
5537313	Pirelli	Jul 1996	A
5537853	Finburgh et al.	Jul 1996	A
5540808	Vincent et al.	Jul 1996	A
5540842	Aoyama et al.	Jul 1996	A
5542420	Goldman et al.	Aug 1996	A
5542919	Simon et al.	Aug 1996	A
5544649	David et al.	Aug 1996	A
5544651	Wilk	Aug 1996	A
5544661	Davis et al.	Aug 1996	A
5545131	Davankov	Aug 1996	A
5545140	Conero et al.	Aug 1996	A
5546580	Seliger et al.	Aug 1996	A
5547470	Johnson et al.	Aug 1996	A
5549117	Tacklind et al.	Aug 1996	A
5549460	O'Leary	Aug 1996	A
5553609	Chen et al.	Sep 1996	A
5558638	Evers et al.	Sep 1996	A
5558640	Pfeiler et al.	Sep 1996	A
5560352	Heim et al.	Oct 1996	A
5562232	Pearson	Oct 1996	A
5562621	Claude et al.	Oct 1996	A
5563347	Martin et al.	Oct 1996	A
5564803	McDonald et al.	Oct 1996	A
5568912	Minami et al.	Oct 1996	A
5569186	Lord et al.	Oct 1996	A
5569187	Kaiser	Oct 1996	A
5570026	Buffaloe, IV et al.	Oct 1996	A
5571258	Pearson	Nov 1996	A
5573502	LeCocq et al.	Nov 1996	A
5573506	Vasko	Nov 1996	A
5575632	Morris et al.	Nov 1996	A
5576952	Stutman et al.	Nov 1996	A
5578070	Utterberg	Nov 1996	A
5579001	Dempsey et al.	Nov 1996	A
5579378	Arlinghaus, Jr.	Nov 1996	A
5581369	Righter et al.	Dec 1996	A
5581687	Lyle et al.	Dec 1996	A
5582593	Hultman	Dec 1996	A
5583758	McIlroy et al.	Dec 1996	A
5588815	Zaleski, II	Dec 1996	A
5588816	Abbott et al.	Dec 1996	A
5589932	Garcia-Rubio et al.	Dec 1996	A
5590648	Mitchell et al.	Jan 1997	A
5591251	Brugger	Jan 1997	A
5591344	Kenley et al.	Jan 1997	A
5593267	McDonald et al.	Jan 1997	A
5594637	Eisenberg et al.	Jan 1997	A
5594786	Chaco et al.	Jan 1997	A
5597995	Williams et al.	Jan 1997	A
5598536	Slaughter, III et al.	Jan 1997	A
5601445	Schipper et al.	Feb 1997	A
5605540	Utterberg	Feb 1997	A
5609572	Lang	Mar 1997	A
5609575	Larson et al.	Mar 1997	A
5609576	Voss et al.	Mar 1997	A
5613115	Gihl et al.	Mar 1997	A
5614677	Wansiedler et al.	Mar 1997	A
5616248	Schal	Apr 1997	A
5619428	Lee et al.	Apr 1997	A
5619991	Sloane	Apr 1997	A
5623652	Vora et al.	Apr 1997	A
5623925	Swenson et al.	Apr 1997	A
5626144	Tacklind et al.	May 1997	A
5628619	Wilson	May 1997	A
5628908	Kamen	May 1997	A
5630710	Tune et al.	May 1997	A
5631844	Margrey et al.	May 1997	A
5633910	Cohen	May 1997	A
D380260	Hyman	Jun 1997	S
5634893	Rishton	Jun 1997	A
5637081	Noguchi et al.	Jun 1997	A
5637082	Pages et al.	Jun 1997	A
5637093	Hyman et al.	Jun 1997	A
5640301	Roecher et al.	Jun 1997	A
5640953	Bishop et al.	Jun 1997	A
5640995	Packard et al.	Jun 1997	A
5641405	Keshaviah et al.	Jun 1997	A
5641628	Bianchi	Jun 1997	A
5643193	Papillon et al.	Jul 1997	A
5643201	Peabody et al.	Jul 1997	A
5643212	Coutre et al.	Jul 1997	A
5643250	Utterberg	Jul 1997	A
5645734	Kenley et al.	Jul 1997	A
5647853	Feldmann et al.	Jul 1997	A
5647854	Olsen et al.	Jul 1997	A
5650071	Brugger et al.	Jul 1997	A
5651775	Walker et al.	Jul 1997	A
5652566	Lambert	Jul 1997	A
5658240	Urdahl et al.	Aug 1997	A
5658250	Blomquist et al.	Aug 1997	A
5658456	Kenley et al.	Aug 1997	A
5661978	Holmes et al.	Sep 1997	A
5664270	Bell et al.	Sep 1997	A
5666404	Ciccotelli et al.	Sep 1997	A
5674199	Brugger	Oct 1997	A
5678562	Sellers	Oct 1997	A
5678568	Uchikubo et al.	Oct 1997	A
5681285	Ford et al.	Oct 1997	A
5681294	Osborne et al.	Oct 1997	A
5682526	Smokoff et al.	Oct 1997	A
5683355	Fini et al.	Nov 1997	A
5683367	Jordan et al.	Nov 1997	A
5683381	Carr et al.	Nov 1997	A
5685844	Marttila	Nov 1997	A
5685988	Malchesky	Nov 1997	A
5685989	Krivitski et al.	Nov 1997	A
5687717	Halpern	Nov 1997	A
5687734	Dempsey et al.	Nov 1997	A
5690614	Carr et al.	Nov 1997	A
5690831	Kenley et al.	Nov 1997	A
5695473	Olsen	Dec 1997	A
5697951	Harpstead	Dec 1997	A
5700998	Palti	Dec 1997	A
5701894	Cherry et al.	Dec 1997	A
5702597	Chevallet et al.	Dec 1997	A
5702606	Peter, Jr. et al.	Dec 1997	A
5704351	Mortara et al.	Jan 1998	A
5704364	Saltzstein et al.	Jan 1998	A
5704366	Tacklind et al.	Jan 1998	A
5712798	Langley et al.	Jan 1998	A
5712912	Tomko et al.	Jan 1998	A
5713485	Liff et al.	Feb 1998	A
5713856	Eggers et al.	Feb 1998	A
5715823	Wood et al.	Feb 1998	A
5716114	Holmes et al.	Feb 1998	A
5716194	Butterfield et al.	Feb 1998	A
5718562	Lawless et al.	Feb 1998	A
5719761	Gatti et al.	Feb 1998	A
RE35743	Pearson	Mar 1998	E
5722947	Jeppsson et al.	Mar 1998	A
5724025	Tavori	Mar 1998	A
5724478	Thweatt	Mar 1998	A
5724580	Levin et al.	Mar 1998	A
5725776	Kenley et al.	Mar 1998	A
5729653	Magliochetti et al.	Mar 1998	A
5730712	Falkvall et al.	Mar 1998	A
5730730	Darling, Jr.	Mar 1998	A
5732709	Tacklind et al.	Mar 1998	A
5733259	Valcke et al.	Mar 1998	A
5735887	Barreras, Sr. et al.	Apr 1998	A
5737539	Edelson et al.	Apr 1998	A
5740185	Bosse	Apr 1998	A
5740800	Hendrickson et al.	Apr 1998	A
5744042	Stange et al.	Apr 1998	A
5745366	Higham et al.	Apr 1998	A
5745378	Barker et al.	Apr 1998	A
5752917	Fuchs	May 1998	A
5752976	Duffin et al.	May 1998	A
5755563	Clegg et al.	May 1998	A
5762782	Kenley et al.	Jun 1998	A
5763266	Palsson et al.	Jun 1998	A
5764923	Tallman et al.	Jun 1998	A
5766155	Hyman et al.	Jun 1998	A
5769811	Stacey et al.	Jun 1998	A
5771657	Lasher et al.	Jun 1998	A
5772585	Lavin et al.	Jun 1998	A
5772586	Heinonen et al.	Jun 1998	A
5772635	Dastur	Jun 1998	A
5772637	Heinzmann et al.	Jun 1998	A
5776057	Swenson et al.	Jul 1998	A
5776091	Brugger et al.	Jul 1998	A
5776345	Truitt et al.	Jul 1998	A
5778345	McCartney	Jul 1998	A
5778882	Raymond et al.	Jul 1998	A
5781442	Chamberlain et al.	Jul 1998	A
5782575	Vincent et al.	Jul 1998	A
5782805	Meinzer et al.	Jul 1998	A
5782878	Morgan et al.	Jul 1998	A
5785650	Akasaka et al.	Jul 1998	A
5788669	Peterson	Aug 1998	A
5790409	Fedor et al.	Aug 1998	A
5790752	Anglin et al.	Aug 1998	A
5791342	Woodard	Aug 1998	A
5791880	Wilson	Aug 1998	A
5793861	Haigh	Aug 1998	A
5793969	Kamentsky et al.	Aug 1998	A
5795317	Brierton et al.	Aug 1998	A
5795327	Wilson et al.	Aug 1998	A
5797515	Liff et al.	Aug 1998	A
5800387	Duffy et al.	Sep 1998	A
5803906	Pratt et al.	Sep 1998	A
5805442	Crater et al.	Sep 1998	A
5805456	Higham et al.	Sep 1998	A
5805505	Zheng et al.	Sep 1998	A
5807321	Stoker et al.	Sep 1998	A
5807322	Lindsey et al.	Sep 1998	A
5807336	Chen et al.	Sep 1998	A
5810747	Brudny et al.	Sep 1998	A
5814015	Cowen et al.	Sep 1998	A
5815566	Ramot et al.	Sep 1998	A
5816779	Lawless et al.	Oct 1998	A
5822418	Yacenda et al.	Oct 1998	A
5822544	Chaco et al.	Oct 1998	A
5823949	Goltra	Oct 1998	A
5826237	Macrae et al.	Oct 1998	A
5829438	Gibbs et al.	Nov 1998	A
5830185	Block, Jr.	Nov 1998	A
5832448	Brown	Nov 1998	A
5832450	Myers et al.	Nov 1998	A
5833599	Schrier et al.	Nov 1998	A
5836908	Beden et al.	Nov 1998	A
5841975	Layne et al.	Nov 1998	A
5842841	Danby et al.	Dec 1998	A
5842976	Williamson	Dec 1998	A
5845253	Rensimer et al.	Dec 1998	A
5846419	Nederlof	Dec 1998	A
5848593	McGrady et al.	Dec 1998	A
5849065	Wojke	Dec 1998	A
5851186	Wood et al.	Dec 1998	A
5851202	Carlsson	Dec 1998	A
5852590	De La Huerga	Dec 1998	A
5853387	Clegg et al.	Dec 1998	A
5855550	Buyan et al.	Jan 1999	A
5857967	Frid et al.	Jan 1999	A
5858238	McRea et al.	Jan 1999	A
5858239	Kenley et al.	Jan 1999	A
5859972	Subramaniam et al.	Jan 1999	A
5863421	Peter, Jr. et al.	Jan 1999	A
5865745	Schmitt et al.	Feb 1999	A
5865786	Sibalis et al.	Feb 1999	A
5866880	Seitz et al.	Feb 1999	A
5867821	Ballantyne et al.	Feb 1999	A
5871465	Vasko	Feb 1999	A
5871694	Beden et al.	Feb 1999	A
5873853	Keilman et al.	Feb 1999	A
5875282	Jordan et al.	Feb 1999	A
5876611	Shettigar	Mar 1999	A
5876926	Beecham	Mar 1999	A
5880443	McDonald et al.	Mar 1999	A
5882338	Gray	Mar 1999	A
5883370	Walker et al.	Mar 1999	A
5883576	De La Huerga	Mar 1999	A
5885245	Lynch et al.	Mar 1999	A
5891035	Wood et al.	Apr 1999	A
5891734	Gill et al.	Apr 1999	A
5893697	Zimi et al.	Apr 1999	A
5894273	Meador et al.	Apr 1999	A
5895368	Utterberg	Apr 1999	A
5895371	Jordan et al.	Apr 1999	A
5895578	Simard et al.	Apr 1999	A
5897493	Brown	Apr 1999	A
5897530	Jackson	Apr 1999	A
5897989	Beecham	Apr 1999	A
5899665	Makino et al.	May 1999	A
5899855	Brown	May 1999	A
5901150	Dupouy et al.	May 1999	A
5902336	Mishkin	May 1999	A
5902476	Twardowski	May 1999	A
5904668	Hyman et al.	May 1999	A
5905653	Higham et al.	May 1999	A
5907291	Chen et al.	May 1999	A
5908027	Butterfield et al.	Jun 1999	A
5910107	Iliff	Jun 1999	A
5910252	Corbin, III et al.	Jun 1999	A
5911132	Sloane	Jun 1999	A
5911687	Sano et al.	Jun 1999	A
5912818	McGrady et al.	Jun 1999	A
5913197	Kameda	Jun 1999	A
5913310	Brown	Jun 1999	A
5915240	Karpf	Jun 1999	A
5919154	Toavs et al.	Jul 1999	A
5919369	Ash	Jul 1999	A
5921938	Aoyama et al.	Jul 1999	A
5921951	Morris	Jul 1999	A
5923018	Kameda et al.	Jul 1999	A
5924074	Evans	Jul 1999	A
5924103	Ahmed et al.	Jul 1999	A
5925011	Faict et al.	Jul 1999	A
5927540	Godlewski	Jul 1999	A
5928744	Heilmann et al.	Jul 1999	A
5928889	Bakich et al.	Jul 1999	A
5931791	Saltzstein et al.	Aug 1999	A
5931990	Andrews	Aug 1999	A
5932103	Kenley et al.	Aug 1999	A
5932110	Shah	Aug 1999	A
5935060	Iliff	Aug 1999	A
5935099	Peterson et al.	Aug 1999	A
5935106	Olsen	Aug 1999	A
5938413	Makino et al.	Aug 1999	A
5938634	Packard	Aug 1999	A
5939326	Chupp et al.	Aug 1999	A
5939699	Perttunen et al.	Aug 1999	A
5940306	Gardner et al.	Aug 1999	A
5940802	Hildebrand et al.	Aug 1999	A
5941829	Saltzstein et al.	Aug 1999	A
5942986	Shabot et al.	Aug 1999	A
5943423	Muftic	Aug 1999	A
5943633	Wilson et al.	Aug 1999	A
5944659	Flach et al.	Aug 1999	A
5944684	Roberts et al.	Aug 1999	A
5945651	Chorosinski et al.	Aug 1999	A
5946083	Melendez et al.	Aug 1999	A
5946659	Lancelot et al.	Aug 1999	A
5948251	Brugger	Sep 1999	A
5950006	Crater et al.	Sep 1999	A
5951300	Brown	Sep 1999	A
5951510	Barak	Sep 1999	A
5951870	Utterberg	Sep 1999	A
5954640	Szabo	Sep 1999	A
5954885	Bollish et al.	Sep 1999	A
5954958	Folden	Sep 1999	A
5954971	Pages et al.	Sep 1999	A
5956023	Lyle et al.	Sep 1999	A
5957153	Frey et al.	Sep 1999	A
5957885	Bollish et al.	Sep 1999	A
5959529	Kail, IV	Sep 1999	A
5960085	De La Huerga	Sep 1999	A
5960160	Clark et al.	Sep 1999	A
5960403	Brown	Sep 1999	A
5960991	Ophardt	Oct 1999	A
5961446	Beller et al.	Oct 1999	A
5961448	Swenson et al.	Oct 1999	A
5961487	Davis	Oct 1999	A
5964700	Tallman et al.	Oct 1999	A
5966304	Cook et al.	Oct 1999	A
5967975	Ridgeway	Oct 1999	A
5970423	Langley et al.	Oct 1999	A
5971593	McGrady	Oct 1999	A
5971921	Timbel	Oct 1999	A
5971948	Pages et al.	Oct 1999	A
5974124	Schlueter, Jr. et al.	Oct 1999	A
5975737	Crater et al.	Nov 1999	A
5980481	Gorsuch	Nov 1999	A
5980490	Tsoukalis	Nov 1999	A
5980741	Schnell et al.	Nov 1999	A
5983193	Heinonen et al.	Nov 1999	A
5983947	Utterberg	Nov 1999	A
5984891	Keilman et al.	Nov 1999	A
5987519	Peifer et al.	Nov 1999	A
5989238	Ginsburg	Nov 1999	A
5989318	Schroll	Nov 1999	A
5989423	Kamen et al.	Nov 1999	A
5991731	Colon et al.	Nov 1999	A
5993046	McGrady et al.	Nov 1999	A
5993420	Hyman et al.	Nov 1999	A
5995077	Wilcox et al.	Nov 1999	A
5995965	Experton	Nov 1999	A
5997167	Crater et al.	Dec 1999	A
5997476	Brown	Dec 1999	A
6001201	Vincent et al.	Dec 1999	A
6003006	Colella et al.	Dec 1999	A
6004020	Bartur	Dec 1999	A
6004276	Wright et al.	Dec 1999	A
6004311	Heilmann et al.	Dec 1999	A
6006191	DeRienzo	Dec 1999	A
6009333	Chaco	Dec 1999	A
6010454	Arieff et al.	Jan 2000	A
6010623	Schnell et al.	Jan 2000	A
6011858	Stock et al.	Jan 2000	A
6011999	Holmes	Jan 2000	A
6012034	Hamparian et al.	Jan 2000	A
6013057	Danby et al.	Jan 2000	A
6014631	Teagarden et al.	Jan 2000	A
6016444	John	Jan 2000	A
6017318	Gauthier et al.	Jan 2000	A
6018713	Coli et al.	Jan 2000	A
6019745	Gray	Feb 2000	A
6019824	Schnell	Feb 2000	A
6021392	Lester et al.	Feb 2000	A
6022315	Iliff	Feb 2000	A
6023522	Draganoff et al.	Feb 2000	A
6024539	Blomquist	Feb 2000	A
6024699	Allen et al.	Feb 2000	A
6024720	Chandler et al.	Feb 2000	A
6027217	McClure et al.	Feb 2000	A
6029138	Khorasani et al.	Feb 2000	A
6032119	Brown et al.	Feb 2000	A
6032155	de la Huerga	Feb 2000	A
6033076	Braeuning et al.	Mar 2000	A
6039251	Crone et al.	Mar 2000	A
6039467	Holmes	Mar 2000	A
6042784	Wamsiedler et al.	Mar 2000	A
6046806	Thompson	Apr 2000	A
6047259	Campbell et al.	Apr 2000	A
6050940	Braun et al.	Apr 2000	A
6051134	Schnell et al.	Apr 2000	A
6053967	Heilmann et al.	Apr 2000	A
6055487	Margery et al.	Apr 2000	A
6057758	Dempsey et al.	May 2000	A
6059736	Tapper	May 2000	A
6061603	Papadopoulos et al.	May 2000	A
6065819	Holmes et al.	May 2000	A
6066111	Brockhoff	May 2000	A
6068153	Young et al.	May 2000	A
6069343	Kolowich	May 2000	A
6071269	Schnell et al.	Jun 2000	A
6073046	Patel et al.	Jun 2000	A
6074345	van Oostrom et al.	Jun 2000	A
6074359	Keshaviah et al.	Jun 2000	A
6079621	Vardanyan et al.	Jun 2000	A
6080106	Lloyd et al.	Jun 2000	A
6081048	Bergmann et al.	Jun 2000	A
6082776	Feinberg	Jul 2000	A
6083206	Molko	Jul 2000	A
6093146	Filangeri	Jul 2000	A
6095985	Raymond et al.	Aug 2000	A
6101407	Groezinger	Aug 2000	A
6101478	Brown	Aug 2000	A
6102856	Groff et al.	Aug 2000	A
6108399	Hernandez-Guerra et al.	Aug 2000	A
6108588	McGrady	Aug 2000	A
6109774	Holmes et al.	Aug 2000	A
6112224	Peifer et al.	Aug 2000	A
RE36871	Epstein et al.	Sep 2000	E
6113554	Gilcher et al.	Sep 2000	A
6116461	Broadfield et al.	Sep 2000	A
6117342	Schnell et al.	Sep 2000	A
6117940	Mjalli	Sep 2000	A
6123524	Danby et al.	Sep 2000	A
6125350	Dirbas	Sep 2000	A
6129517	Danby et al.	Oct 2000	A
6129699	Haight et al.	Oct 2000	A
6132371	Dempsey et al.	Oct 2000	A
6132616	Twardowski et al.	Oct 2000	A
6134504	Douglas et al.	Oct 2000	A
6135949	Russo et al.	Oct 2000	A
6139495	De La Huerga	Oct 2000	A
6139528	Kistner et al.	Oct 2000	A
6139748	Ericson et al.	Oct 2000	A
6139754	Hartranft	Oct 2000	A
6139757	Ohmura	Oct 2000	A
6142974	Kistner et al.	Nov 2000	A
6142975	Kistner et al.	Nov 2000	A
6144922	Douglas et al.	Nov 2000	A
6145695	Garrigues	Nov 2000	A
6146359	Carr et al.	Nov 2000	A
6146523	Barrett et al.	Nov 2000	A
6146536	Twardowski	Nov 2000	A
6148297	Swor et al.	Nov 2000	A
6149063	Reynolds et al.	Nov 2000	A
6151536	Arnold et al.	Nov 2000	A
6152364	Schoonen et al.	Nov 2000	A
6154668	Pedersen et al.	Nov 2000	A
6154726	Rensimer et al.	Nov 2000	A
6157914	Seto et al.	Dec 2000	A
6158965	Butterfield et al.	Dec 2000	A
6160478	Jacobsen et al.	Dec 2000	A
6161095	Brown	Dec 2000	A
6163737	Fedor et al.	Dec 2000	A
6165154	Gray et al.	Dec 2000	A
6168563	Brown	Jan 2001	B1
6168578	Diamond	Jan 2001	B1
6170007	Venkatraman et al.	Jan 2001	B1
6170746	Brook et al.	Jan 2001	B1
6171112	Clark et al.	Jan 2001	B1
6171237	Boaz et al.	Jan 2001	B1
6171264	Bader	Jan 2001	B1
6171484	Schnell et al.	Jan 2001	B1
6173198	Schulze et al.	Jan 2001	B1
6175688	Cassidy et al.	Jan 2001	B1
6175779	Barrett	Jan 2001	B1
6175977	Schumacher et al.	Jan 2001	B1
6176903	Wamsiedler	Jan 2001	B1
6182047	Dirbas	Jan 2001	B1
6183417	Geheb et al.	Feb 2001	B1
6186145	Brown	Feb 2001	B1
6187198	Utterberg	Feb 2001	B1
6188988	Barry et al.	Feb 2001	B1
6192320	Margrey et al.	Feb 2001	B1
6193480	Butterfield	Feb 2001	B1
6193684	Burbank et al.	Feb 2001	B1
6195887	Danby et al.	Mar 2001	B1
6196992	Keilman et al.	Mar 2001	B1
6198394	Jacobsen et al.	Mar 2001	B1
6200264	Satherley et al.	Mar 2001	B1
6200289	Hochman et al.	Mar 2001	B1
6203495	Bardy	Mar 2001	B1
6203528	Deckert et al.	Mar 2001	B1
6206238	Ophardt	Mar 2001	B1
6206829	Iliff	Mar 2001	B1
6206954	Schnell et al.	Mar 2001	B1
6210361	Kamen et al.	Apr 2001	B1
6213391	Lewis	Apr 2001	B1
6213738	Danby et al.	Apr 2001	B1
6219439	Burger	Apr 2001	B1
6219587	Ahlin et al.	Apr 2001	B1
6220299	Arvidsson et al.	Apr 2001	B1
6221011	Bardy	Apr 2001	B1
6221012	Maschke et al.	Apr 2001	B1
6222619	Herron et al.	Apr 2001	B1
6224549	Van Drongelen	May 2001	B1
6225901	Kail, IV	May 2001	B1
6226564	Stuart	May 2001	B1
6228047	Dadson	May 2001	B1
6229957	Baker	May 2001	B1
6230927	Schoonen et al.	May 2001	B1
6234991	Gorsuch	May 2001	B1
6234992	Haight et al.	May 2001	B1
6234997	Kamen et al.	May 2001	B1
6236809	Cassidy et al.	May 2001	B1
6245013	Minoz et al.	Jun 2001	B1
6245039	Brugger et al.	Jun 2001	B1
6246473	Smith, Jr. et al.	Jun 2001	B1
6248063	Barnhill et al.	Jun 2001	B1
6248065	Brown	Jun 2001	B1
6251167	Berson	Jun 2001	B1
6251279	Peterson et al.	Jun 2001	B1
6254567	Treu et al.	Jul 2001	B1
6255951	De La Huerga	Jul 2001	B1
6256643	Cork et al.	Jul 2001	B1
6256967	Hebron et al.	Jul 2001	B1
6259355	Chaco et al.	Jul 2001	B1
6259654	De La Huerga	Jul 2001	B1
6260715	Simard et al.	Jul 2001	B1
6261261	Gordon	Jul 2001	B1
6261809	Bertling et al.	Jul 2001	B1
6266645	Simpson	Jul 2001	B1
6269340	Ford et al.	Jul 2001	B1
D446854	Cheney, II et al.	Aug 2001	S
6270455	Brown	Aug 2001	B1
6270457	Bardy	Aug 2001	B1
6272394	Lipps	Aug 2001	B1
6272505	De La Huerga	Aug 2001	B1
6274034	Nikaido et al.	Aug 2001	B1
6274103	Taylor	Aug 2001	B1
6277072	Bardy	Aug 2001	B1
6280632	Polaschegg	Aug 2001	B1
6280634	Shah et al.	Aug 2001	B1
6283322	Liff et al.	Sep 2001	B1
6283944	McMullen et al.	Sep 2001	B1
6287516	Matson et al.	Sep 2001	B1
6290646	Cosentino	Sep 2001	B1
6290650	Butterfield et al.	Sep 2001	B1
6290669	Zicherman	Sep 2001	B1
6293921	Shinmoto et al.	Sep 2001	B1
6294999	Yarin et al.	Sep 2001	B1
6295506	Heinonen	Sep 2001	B1
6302653	Bryant et al.	Oct 2001	B1
6304788	Eady et al.	Oct 2001	B1
6306088	Krausman et al.	Oct 2001	B1
6307956	Black	Oct 2001	B1
6308171	De La Huerga	Oct 2001	B1
6309673	Duponchelle	Oct 2001	B1
6311163	Sheehan et al.	Oct 2001	B1
6312227	Davis	Nov 2001	B1
6312378	Bardy	Nov 2001	B1
6312414	Brockhoff et al.	Nov 2001	B1
6314384	Goetz	Nov 2001	B1
6315895	Summerton et al.	Nov 2001	B1
6317719	Schrier et al.	Nov 2001	B1
6319200	Lai	Nov 2001	B1
6319221	Savage et al.	Nov 2001	B1
6321203	Kameda	Nov 2001	B1
6322504	Kirshner	Nov 2001	B1
6322515	Goor et al.	Nov 2001	B1
6322551	Brugger	Nov 2001	B1
6331252	El Sayyid et al.	Dec 2001	B1
RE37531	Chaco et al.	Jan 2002	E
6337631	Pai	Jan 2002	B1
6338007	Broadfield et al.	Jan 2002	B1
6339732	Phoon et al.	Jan 2002	B1
6344139	Utterberg	Feb 2002	B1
6345260	Cummings, Jr. et al.	Feb 2002	B1
6346886	De La Huerga	Feb 2002	B1
6348162	Ash	Feb 2002	B1
6352200	Schoonen et al.	Mar 2002	B1
6353817	Jacobs et al.	Mar 2002	B1
6357600	Scagliarini	Mar 2002	B1
6358225	Butterfield	Mar 2002	B1
6358237	Paukovits	Mar 2002	B1
6361201	Russell et al.	Mar 2002	B1
6361263	Dewey et al.	Mar 2002	B1
6362591	Moberg	Mar 2002	B1
6363282	Nichols et al.	Mar 2002	B1
6363290	Lyle et al.	Mar 2002	B1
6366282	Nichols et al.	Mar 2002	B1
6364143	Knierbein	Apr 2002	B1
6364834	Reuss et al.	Apr 2002	B1
6364857	Gray et al.	Apr 2002	B1
6368273	Brown	Apr 2002	B1
6370841	Chudy et al.	Apr 2002	B1
6381577	Brown	Apr 2002	B1
6382923	Gray	May 2002	B1
6385505	Lipps	May 2002	B1
6391541	Petersen et al.	May 2002	B1
6391638	Shaaltiel	May 2002	B1
6393369	Carr	May 2002	B1
6397190	Goetz	May 2002	B1
6402702	Gilcher et al.	Jun 2002	B1
6406426	Reuss et al.	Jun 2002	B1
6406631	Collins et al.	Jun 2002	B1
6407335	Franklin-Lees et al.	Jun 2002	B1
6408330	De La Huerga	Jun 2002	B1
6416293	Bouchard et al.	Jul 2002	B1
6416471	Kumar et al.	Jul 2002	B1
6421650	Goetz et al.	Jul 2002	B1
6426056	Taylor	Jul 2002	B2
6427088	Bowman, IV et al.	Jul 2002	B1
6434531	Lancelot et al.	Aug 2002	B1
6434569	Tomlinson et al.	Aug 2002	B1
6449927	Hebron et al.	Sep 2002	B2
6450956	Rappaport et al.	Sep 2002	B1
6458102	Mann et al.	Oct 2002	B1
6464977	Kai et al.	Oct 2002	B2
6468242	Wilson et al.	Oct 2002	B1
6470234	McGrady	Oct 2002	B1
6471089	Liff et al.	Oct 2002	B2
6471645	Warkentin et al.	Oct 2002	B1
6475146	Frelburger et al.	Nov 2002	B1
6475148	Jackson et al.	Nov 2002	B1
6475180	Peterson et al.	Nov 2002	B2
6478737	Bardy	Nov 2002	B2
6485465	Moberg et al.	Nov 2002	B2
6489301	Kobira et al.	Dec 2002	B1
6511138	Gardner et al.	Jan 2003	B1
6519569	White et al.	Feb 2003	B1
6537244	Paukovits	Mar 2003	B2
6542902	Dulong et al.	Apr 2003	B2
6542910	Cork et al.	Apr 2003	B2
6544174	West et al.	Apr 2003	B2
6544228	Heitmeier	Apr 2003	B1
6551243	Bocionek et al.	Apr 2003	B2
6551276	Mann et al.	Apr 2003	B1
6554791	Cartledge et al.	Apr 2003	B1
6554798	Mann et al.	Apr 2003	B1
6555986	Moberg	Apr 2003	B2
6558321	Burd et al.	May 2003	B1
6561975	Pool et al.	May 2003	B1
6562001	Lebel et al.	May 2003	B2
6564104	Nelson et al.	May 2003	B2
6564105	Starkweather et al.	May 2003	B2
6571128	Lebel et al.	May 2003	B2
6575900	Zweig et al.	Jun 2003	B1
6577899	Lebel et al.	Jun 2003	B2
6579232	Sakamaki et al.	Jun 2003	B2
6579253	Burbank et al.	Jun 2003	B1
6581069	Robinson et al.	Jun 2003	B1
6582385	Burbank et al.	Jun 2003	B2
6584336	Ali et al.	Jun 2003	B1
6585157	Brandt et al.	Jul 2003	B2
6585644	Lebel et al.	Jul 2003	B2
6585675	O'Mahony et al.	Jul 2003	B1
6592551	Cobb	Jul 2003	B1
6593528	Franklin-Lees et al.	Jul 2003	B2
6595944	Balschat et al.	Jul 2003	B2
6602502	Strahilevitz	Aug 2003	B1
6607485	Bardy	Aug 2003	B2
6613009	Bainbridge et al.	Sep 2003	B1
6623709	Taylor	Sep 2003	B2
6635014	Starkweather et al.	Oct 2003	B2
6648821	Lebel et al.	Nov 2003	B2
6656355	Sano	Dec 2003	B2
6659948	Lebel et al.	Dec 2003	B2
6664893	Eveland et al.	Dec 2003	B1
6668196	Villegas et al.	Dec 2003	B1
6673314	Burbank et al.	Jan 2004	B1
6673376	Knerr et al.	Jan 2004	B1
6685831	Donig et al.	Feb 2004	B2
6687546	Lebel et al.	Feb 2004	B2
6689091	Bui et al.	Feb 2004	B2
6694191	Starkweather et al.	Feb 2004	B2
6694334	Dulong et al.	Feb 2004	B2
6733446	Lebel et al.	May 2004	B2
6733447	Lai et al.	May 2004	B2
6740075	Lebel et al.	May 2004	B2
6745903	Grandics	Jun 2004	B2
6746398	Hervy et al.	Jun 2004	B2
6746607	Vijayalakshmi et al.	Jun 2004	B1
6749818	Sano et al.	Jun 2004	B2
6752928	Pfeil et al.	Jun 2004	B2
6758810	Lebel et al.	Jul 2004	B2
6758975	Peabody et al.	Jul 2004	B2
6768425	Flaherty et al.	Jul 2004	B2
6787032	Kurome et al.	Sep 2004	B2
6790198	White et al.	Sep 2004	B1
6804656	Rosenfeld et al.	Oct 2004	B1
6810290	Lebel et al.	Oct 2004	B2
6811533	Lebel et al.	Nov 2004	B2
6811534	Bowman, IV et al.	Nov 2004	B2
6811707	Rovatti et al.	Nov 2004	B2
6813519	Lebel et al.	Nov 2004	B2
6820093	De La Huerga	Nov 2004	B2
6854088	Massengale et al.	Feb 2005	B2
6861033	Mullins et al.	Mar 2005	B2
6871211	Labounty et al.	Mar 2005	B2
6873268	Lebel et al.	Mar 2005	B2
6880034	Manke et al.	Apr 2005	B2
6885288	Pincus	Apr 2005	B2
6902670	Ho	Jun 2005	B2
6908546	Smith	Jun 2005	B2
6912549	Rotter et al.	Jun 2005	B2
6913590	Sorenson et al.	Jul 2005	B2
6923987	Kai et al.	Aug 2005	B2
6928452	De La Huerga	Aug 2005	B2
6950708	Bowman, IV et al.	Sep 2005	B2
6958705	Lebel et al.	Oct 2005	B2
6960179	Gura	Nov 2005	B2
6974437	Lebel et al.	Dec 2005	B2
6976628	Krupa	Dec 2005	B2
6979306	Moll	Dec 2005	B2
6980958	Surwit et al.	Dec 2005	B1
6986872	Taylor	Jan 2006	B2
7024245	Lebel et al.	Apr 2006	B2
7039878	Auer et al.	May 2006	B2
7044927	Mueller et al.	May 2006	B2
7045061	Nishimura et al.	May 2006	B2
7051002	Keresman, III et al.	May 2006	B2
7061831	De La Huerga	Jun 2006	B2
7072769	Fletcher-Haynes et al.	Jul 2006	B2
7076520	Nelson et al.	Jul 2006	B2
7077956	Rovatti	Jul 2006	B2
7089780	Sunshine et al.	Aug 2006	B2
7092796	Vanderveen	Aug 2006	B2
7096072	Engleson et al.	Aug 2006	B2
7108790	Collins et al.	Sep 2006	B2
7117239	Hansen	Oct 2006	B1
7122210	Paola	Oct 2006	B2
7156808	Quy	Jan 2007	B2
7161484	Tsoukalis	Jan 2007	B2
7165221	Monteleone et al.	Jan 2007	B2
7171274	Starkweather et al.	Jan 2007	B2
7188151	Kumar et al.	Mar 2007	B2
7194336	DeGianfilippo et al.	Mar 2007	B2
7208092	Micheli	Apr 2007	B2
7216802	De La Huerga	May 2007	B1
7231263	Choi	Jun 2007	B2
7238156	Adamczyk	Jul 2007	B1
7241272	Karoor et al.	Jul 2007	B2
7250619	Taylor et al.	Jul 2007	B2
7251610	Alban et al.	Jul 2007	B2
7264148	Tachibana	Sep 2007	B2
7274799	Cohen et al.	Sep 2007	B2
7275220	Brummel et al.	Sep 2007	B2
7290680	Henry et al.	Nov 2007	B2
7292141	Staats et al.	Nov 2007	B2
7300418	Zaleski	Nov 2007	B2
7304582	Robert et al.	Dec 2007	B2
7306736	Collins et al.	Dec 2007	B2
7308894	Hickle	Dec 2007	B2
7309323	Gura et al.	Dec 2007	B2
7315825	Rosenfeld et al.	Jan 2008	B2
7316648	Kelly et al.	Jan 2008	B2
7316662	Delnevo et al.	Jan 2008	B2
7317967	DiGianfilippo et al.	Jan 2008	B2
7319386	Collins, Jr. et al.	Jan 2008	B2
7321862	Rosenfeld et al.	Jan 2008	B2
7343224	DiGianfilippo et al.	Mar 2008	B2
7347819	Lebel et al.	Mar 2008	B2
7356382	Vanderveen	Apr 2008	B2
7369913	Heminway et al.	May 2008	B2
7383196	Tang et al.	Jun 2008	B1
7384410	Eggers et al.	Jun 2008	B2
7419587	Valbjoern et al.	Sep 2008	B2
7419597	Brugger et al.	Sep 2008	B2
7544300	Brugger et al.	Jun 2009	B2
7749393	Brugger et al.	Jul 2010	B2
7892423	Rohde et al.	Feb 2011	B2
7976711	Brugger et al.	Jul 2011	B2
8029454	Kelly et al.	Oct 2011	B2
8071055	Newcombe	Dec 2011	B2
8177977	Gaignet	May 2012	B2
8192387	Brugger et al.	Jun 2012	B2
8216452	Rohde et al.	Jul 2012	B2
8354029	Hank	Jan 2013	B2
8393690	Grant et al.	Mar 2013	B2
8425767	Fava et al.	Apr 2013	B2
8647290	Masala et al.	Feb 2014	B2
8911390	Sternby	Dec 2014	B2
9037616	Bessette	May 2015	B2
9248225	Demers et al.	Feb 2016	B2
9860302	Wittner et al.	Jan 2018	B2
20010001237	Stroda et al.	May 2001	A1
20010003177	Schena et al.	Jun 2001	A1
20010007053	Bardy	Jul 2001	A1
20010007932	Kamen et al.	Jul 2001	A1
20010011153	Bardy	Aug 2001	A1
20010016699	Burbank et al.	Aug 2001	A1
20010017817	De La Huerga	Aug 2001	A1
20010021801	Bardy	Sep 2001	A1
20010021817	Brugger et al.	Sep 2001	A1
20010025138	Bardy	Sep 2001	A1
20010025156	Bui et al.	Sep 2001	A1
20010027289	Treu et al.	Oct 2001	A1
20010027634	Hebron et al.	Oct 2001	A1
20010028308	De La Huerga	Oct 2001	A1
20010030234	Wiklof	Oct 2001	A1
20010031944	Peterson et al.	Oct 2001	A1
20010032101	Statius Muller	Oct 2001	A1
20010034502	Moberg et al.	Oct 2001	A1
20010034616	Giannini	Oct 2001	A1
20010037057	Bardy	Nov 2001	A1
20010037079	Burbank et al.	Nov 2001	A1
20010037083	Hartlaub et al.	Nov 2001	A1
20010037217	Abensour et al.	Nov 2001	A1
20010037220	Merry et al.	Nov 2001	A1
20010041892	Burbank et al.	Nov 2001	A1
20010041920	Starkweather et al.	Nov 2001	A1
20010042441	Purdom et al.	Nov 2001	A1
20010044588	Mault	Nov 2001	A1
20010044731	Coffman et al.	Nov 2001	A1
20010051764	Bardy	Dec 2001	A1
20010053885	Gielen et al.	Dec 2001	A1
20020002326	Causey, III et al.	Jan 2002	A1
20020002473	Schrier et al.	Jan 2002	A1
20020004645	Carlisle et al.	Jan 2002	A1
20020010568	Rubbert et al.	Jan 2002	A1
20020013612	Whitehurst	Jan 2002	A1
20020016567	Hochman et al.	Feb 2002	A1
20020016568	Lebel et al.	Feb 2002	A1
20020016719	Nemeth et al.	Feb 2002	A1
20020016722	Kameda	Feb 2002	A1
20020019606	Lebel et al.	Feb 2002	A1
20020019748	Brown	Feb 2002	A1
20020022776	Bardy	Feb 2002	A1
20020025796	Taylor et al.	Feb 2002	A1
20020026104	Bardy	Feb 2002	A1
20020029157	Marchosky	Mar 2002	A1
20020029776	Blomquist	Mar 2002	A1
20020032602	Lanzillo, Jr. et al.	Mar 2002	A1
20020038392	De La Huerga	Mar 2002	A1
20020040208	Flaherty et al.	Apr 2002	A1
20020044043	Chaco et al.	Apr 2002	A1
20020046062	Kameda	Apr 2002	A1
20020046185	Villart et al.	Apr 2002	A1
20020046346	Evans	Apr 2002	A1
20020052539	Haller et al.	May 2002	A1
20020052542	Bardy	May 2002	A1
20020052574	Hochman et al.	May 2002	A1
20020065540	Lebel et al.	May 2002	A1
20020067273	Jaques et al.	Jun 2002	A1
20020068015	Polaschegg et al.	Jun 2002	A1
20020072718	Brugger et al.	Jun 2002	A1
20020072733	Flaherty	Jun 2002	A1
20020077852	Ford et al.	Jun 2002	A1
20020077865	Sullivan	Jun 2002	A1
20020082480	Riff et al.	Jun 2002	A1
20020082865	Bianco et al.	Jun 2002	A1
20020082868	Pories et al.	Jun 2002	A1
20020084904	De La Huerga	Jul 2002	A1
20020087120	Rogers et al.	Jul 2002	A1
20020099283	Christ et al.	Jul 2002	A1
20020099301	Bardy	Jul 2002	A1
20020100762	Liff et al.	Aug 2002	A1
20020107476	Mann et al.	Aug 2002	A1
20020107707	Naparstek et al.	Aug 2002	A1
20020116509	De La Huerga	Aug 2002	A1
20020128606	Cowan et al.	Sep 2002	A1
20020128871	Adamson et al.	Sep 2002	A1
20020128880	Kunikiyo	Sep 2002	A1
20020131332	Kaelin	Sep 2002	A1
20020133377	Brown	Sep 2002	A1
20020140675	Ali et al.	Oct 2002	A1
20020143254	Maruyama	Oct 2002	A1
20020156462	Stultz	Oct 2002	A1
20020158128	Ashiuro	Oct 2002	A1
20020162778	Peabody et al.	Nov 2002	A1
20020165491	Reilly	Nov 2002	A1
20020169636	Eggers et al.	Nov 2002	A1
20020187940	Masuda et al.	Dec 2002	A1
20020198513	Lebel et al.	Dec 2002	A1
20030000876	Kawaguchi	Jan 2003	A1
20030023177	Bardy	Jan 2003	A1
20030036783	Bauhahn et al.	Feb 2003	A1
20030050621	Lebel et al.	Mar 2003	A1
20030052787	Zerhusen	Mar 2003	A1
20030060753	Starkweather et al.	Mar 2003	A1
20030060754	Reilly	Mar 2003	A1
20030060765	Campbell et al.	Mar 2003	A1
20030060768	Kiyatake	Mar 2003	A1
20030065287	Spohn et al.	Apr 2003	A1
20030078534	Hochman et al.	Apr 2003	A1
20030083901	Bosch et al.	May 2003	A1
20030088238	Poulsen et al.	May 2003	A1
20030097092	Flaherty	May 2003	A1
20030105424	Karoor et al.	Jun 2003	A1
20030114836	Estes et al.	Jun 2003	A1
20030125611	Bardy	Jul 2003	A1
20030135250	Lauman et al.	Jul 2003	A1
20030139701	White et al.	Jul 2003	A1
20030140929	Wilkes et al.	Jul 2003	A1
20030141368	Pascual et al.	Jul 2003	A1
20030144878	Wilkes et al.	Jul 2003	A1
20030144880	Talachian et al.	Jul 2003	A1
20030144881	Talachian et al.	Jul 2003	A1
20030144882	Talachian et al.	Jul 2003	A1
20030154108	Fletcher-Haynes et al.	Aug 2003	A1
20030160683	Blomquist	Aug 2003	A1
20030163088	Blomquist	Aug 2003	A1
20030163223	Blomquist	Aug 2003	A1
20030163789	Blomquist	Aug 2003	A1
20030167035	Flaherty et al.	Sep 2003	A1
20030176933	Lebel et al.	Sep 2003	A1
20030181851	Mann et al.	Sep 2003	A1
20030182164	Shabot et al.	Sep 2003	A1
20030195397	Bardy	Oct 2003	A1
20030201697	Richardson	Oct 2003	A1
20030204414	Wilkes et al.	Oct 2003	A1
20030204416	Radpay et al.	Oct 2003	A1
20030204419	Wilkes et al.	Oct 2003	A1
20030204420	Wilkes et al.	Oct 2003	A1
20030212379	Bylund et al.	Nov 2003	A1
20030220605	Bowman et al.	Nov 2003	A1
20030225596	Richardson et al.	Dec 2003	A1
20030225728	Moura	Dec 2003	A1
20040010425	Wilkes et al.	Jan 2004	A1
20040039260	Bardy	Feb 2004	A1
20040039264	Bardy	Feb 2004	A1
20040051368	Caputo et al.	Mar 2004	A1
20040088374	Webb et al.	May 2004	A1
20040111293	Firanek et al.	Jun 2004	A1
20040116862	Ray	Jun 2004	A1
20040117215	Marchosky	Jun 2004	A1
20040121767	Simpson et al.	Jun 2004	A1
20040167465	Mihai et al.	Aug 2004	A1
20040172283	Vanderveen et al.	Sep 2004	A1
20040172300	Mihai et al.	Sep 2004	A1
20040172301	Mihai et al.	Sep 2004	A1
20040172302	Martucci et al.	Sep 2004	A1
20040176667	Mihai et al.	Sep 2004	A1
20040193328	Zaitsu et al.	Sep 2004	A1
20040204673	Flaherty	Oct 2004	A1
20040215490	Duchon et al.	Oct 2004	A1
20040220829	Baharav et al.	Nov 2004	A1
20040235446	Flaherty et al.	Nov 2004	A1
20040260233	Garibotto et al.	Dec 2004	A1
20050038680	McMahon	Feb 2005	A1
20050054923	Pan	Mar 2005	A1
20050060202	Taylor et al.	Mar 2005	A1
20050065817	Mihai et al.	Mar 2005	A1
20050070767	Maschke	Mar 2005	A1
20050071194	Bormann et al.	Mar 2005	A1
20050080651	Morrison et al.	Apr 2005	A1
20050177096	Bollish et al.	Apr 2005	A1
20050101901	Gura	May 2005	A1
20050102028	Arnin et al.	May 2005	A1
20050102167	Kapoor	May 2005	A1
20050131340	Sorenson et al.	Jun 2005	A1
20050131741	Tang et al.	Jun 2005	A1
20050133449	Sternby	Jun 2005	A1
20050135306	McAllen et al.	Jun 2005	A1
20050137573	McLaughlin	Jun 2005	A1
20050139651	Lim et al.	Jun 2005	A1
20050143671	Hastings et al.	Jun 2005	A1
20050148890	Hastings	Jul 2005	A1
20050171815	Vanderveen	Aug 2005	A1
20050177395	Blomquist	Aug 2005	A1
20050201345	Williamson	Sep 2005	A1
20050228693	Webb et al.	Oct 2005	A1
20050231374	Diem et al.	Oct 2005	A1
20050234381	Niemetz et al.	Oct 2005	A1
20050246416	Blomquist	Nov 2005	A1
20050267780	Ray et al.	Dec 2005	A1
20050278194	Holland et al.	Dec 2005	A1
20050283385	Hunkeler et al.	Dec 2005	A1
20060015015	Kawamoto et al.	Jan 2006	A1
20060167722	Struys et al.	Jan 2006	A1
20060064020	Burnes et al.	Mar 2006	A1
20060064053	Bollish et al.	Mar 2006	A1
20060065713	Kingery	Mar 2006	A1
20060089539	Miodownik et al.	Apr 2006	A1
20060089854	Holland et al.	Apr 2006	A1
20060089855	Holland et al.	Apr 2006	A1
20060100907	Holland et al.	May 2006	A1
20060106647	Brummel et al.	May 2006	A1
20060106649	Eggers et al.	May 2006	A1
20060116639	Russell	Jun 2006	A1
20060143051	Eggers et al.	Jun 2006	A1
20060149591	Hanf et al.	Jul 2006	A1
20060173713	Petro et al.	Aug 2006	A1
20060184455	Meyer et al.	Aug 2006	A1
20060190302	Eggers et al.	Aug 2006	A1
20060200369	Batch et al.	Sep 2006	A1
20060206356	Vanderveen	Sep 2006	A1
20060211994	Roman et al.	Sep 2006	A1
20060229551	Martinez et al.	Oct 2006	A1
20060247606	Batch	Nov 2006	A1
20060253301	Simms et al.	Nov 2006	A1
20060258985	Russell	Nov 2006	A1
20060259327	Hoag	Nov 2006	A1
20060277070	Hungerford et al.	Dec 2006	A1
20070033073	Tajaliawal	Feb 2007	A1
20070073266	Chmiel et al.	Mar 2007	A1
20070083386	Chuang et al.	Apr 2007	A1
20070083390	Gorup et al.	Apr 2007	A1
20070088578	Hoffman et al.	Apr 2007	A1
20070124002	Estes et al.	May 2007	A1
20070129983	Scherpbier et al.	Jun 2007	A1
20070135866	Baker et al.	Jun 2007	A1
20070156452	Batch	Jul 2007	A1
20070158268	DeComo	Jul 2007	A1
20070163965	Wolfe	Jul 2007	A1
20070179807	Nessinger et al.	Aug 2007	A1
20070185738	Anuszewski et al.	Aug 2007	A1
20070197878	Shklarski	Aug 2007	A1
20070198293	Ash et al.	Aug 2007	A1
20070203753	Hasan et al.	Aug 2007	A1
20070214003	Holland et al.	Sep 2007	A1
20070233035	Wehba et al.	Oct 2007	A1
20070233049	Wehba et al.	Oct 2007	A1
20070233050	Wehba et al.	Oct 2007	A1
20070233281	Wehba et al.	Oct 2007	A1
20070233520	Wehba et al.	Oct 2007	A1
20070233521	Wehba et al.	Oct 2007	A1
20070255126	Moberg et al.	Nov 2007	A1
20070265879	Charlson et al.	Nov 2007	A1
20070276869	Charlson et al.	Nov 2007	A1
20070278155	Lo et al.	Dec 2007	A1
20070293817	Feng et al.	Dec 2007	A1
20080015895	Charlson et al.	Jan 2008	A1
20080021741	Holla et al.	Jan 2008	A1
20080033360	Evans et al.	Feb 2008	A1
20080033749	Blomquist	Feb 2008	A1
20080034323	Blomquist	Feb 2008	A1
20080045877	Levin et al.	Feb 2008	A1
20080045932	Beau et al.	Feb 2008	A1
20080052317	Francis et al.	Feb 2008	A1
20080059239	Gerst et al.	Mar 2008	A1
20080076969	Kraft et al.	Mar 2008	A1
20080077436	Muradia	Mar 2008	A1
20080086441	Wolff et al.	Apr 2008	A1
20080091466	Butler et al.	Apr 2008	A1
20080097912	Dicks et al.	Apr 2008	A1
20080097913	Dicks et al.	Apr 2008	A1
20080097914	Dicks et al.	Apr 2008	A1
20080103554	Dicks et al.	May 2008	A1
20080114292	Rasch-Menges et al.	May 2008	A1
20080126969	Blomquist	May 2008	A1
20080133265	Silkaitis et al.	Jun 2008	A1
20080143515	Wood et al.	Jun 2008	A1
20080161754	Marano-Ford	Jul 2008	A1
20080203023	Burbank et al.	Aug 2008	A1
20080208111	Kamen	Aug 2008	A1
20080210606	Burbank	Sep 2008	A1
20080230450	Burbank et al.	Sep 2008	A1
20090008318	Anes et al.	Jan 2009	A1
20090008331	Wilt et al.	Jan 2009	A1
20090012655	Kienman et al.	Jan 2009	A1
20090045121	Kabayama et al.	Feb 2009	A1
20090218285	Hank	Sep 2009	A1
20100018923	Rohde et al.	Jan 2010	A1
20100051546	Vuong et al.	Mar 2010	A1
20100078092	Weilhoefer et al.	Apr 2010	A1
20100137693	Porras et al.	Jun 2010	A1
20100326916	Wrazel et al.	Dec 2010	A1
20100332149	Scholpp	Dec 2010	A1
20110072422	Brauer	Mar 2011	A1
20110100913	Minami et al.	May 2011	A1
20110180480	Kloeffel et al.	Jul 2011	A1
20110186521	Burbank et al.	Aug 2011	A1
20110192796	Smejtek et al.	Aug 2011	A1
20110225008	Elkouh et al.	Sep 2011	A1
20110315611	Fulkerson et al.	Dec 2011	A1
20120158882	Oehme	Jun 2012	A1
20130008854	Wallace et al.	Jan 2013	A1
20130062265	Balschat et al.	Mar 2013	A1
20140238912	Vincent	Aug 2014	A1
20150070187	Wiesner	Mar 2015	A1
20150082542	Hayes et al.	Mar 2015	A1
20160105402	Soon-Shiong	Apr 2016	A1
20170203022	Burbank et al.	Jul 2017	A1
20210027869	Sayani	Jan 2021	A1

Foreign Referenced Citations (140)

Number	Date	Country
296007	Jan 1954	CH
1806654	May 1970	DE
20 02 033	Aug 1970	DE
29 01 628	Jul 1980	DE
31 22 756	Jun 1982	DE
33 07 830	Jun 1984	DE
34 42 744	Jun 1986	DE
40 03 452	Aug 1991	DE
42 08 054	Oct 1992	DE
41 22 754	Jan 1993	DE
198 14 695	Oct 1999	DE
19828923	Jan 2000	DE
198 54 338	Jun 2000	DE
19814695	Sep 2001	DE
0 058 325	Aug 1982	EP
0 064 393	Oct 1982	EP
64393	Nov 1982	EP
0 106 026	Apr 1984	EP
0 143 340	Jun 1985	EP
0 143 341	Jun 1985	EP
152717	Aug 1985	EP
0 171 550	Feb 1986	EP
0 233 848	Aug 1987	EP
0 318 993	Jun 1989	EP
0 350 675	Jan 1990	EP
0 373 455	Jun 1990	EP
0 222 709	May 1991	EP
0243547	Jul 1991	EP
0 490 212	Jun 1992	EP
0 501 144	Sep 1992	EP
0 560 368	Sep 1993	EP
0402505	Dec 1993	EP
0 587 251	Mar 1994	EP
0 720 856	Jul 1996	EP
0 722 744	Jul 1996	EP
0498382	Nov 1996	EP
0778033	Nov 1996	EP
0 749 328	Dec 1996	EP
0 776 222	Jun 1997	EP
0 826 383	Mar 1998	EP
0 826 384	Mar 1998	EP
0575512	May 1998	EP
0928615	Jul 1999	EP
0956876	Nov 1999	EP
980685	Feb 2000	EP
0659092	Oct 2000	EP
0 659 091	Dec 2000	EP
1 097 724	May 2001	EP
0847769	Aug 2001	EP
1 277 485	Jan 2003	EP
1614437	Jan 2006	EP
2080134	May 2008	EP
2180908	May 2010	EP
2 397 197	Feb 1979	FR
2 585 251	Jan 1987	FR
1 408 319	Oct 1975	GB
2 014 060	Aug 1979	GB
1 554 810	Oct 1979	GB
2 061 755	May 1981	GB
2122509	Jan 1984	GB
2124511	Feb 1984	GB
2 212 739	Aug 1989	GB
3 026 703	Jul 1998	GR
55-32384	Mar 1980	JP
55-45437	Mar 1980	JP
55-122559	Sep 1980	JP
57161511	Oct 1982	JP
61-25564	Feb 1986	JP
6-143074	Jun 1986	JP
S61143074	Jun 1986	JP
4-2060	Jan 1992	JP
92002060	Jan 1992	JP
4348757	Mar 1992	JP
4-384757	Dec 1992	JP
59-029264	Feb 1994	JP
07-299455	Nov 1995	JP
7-299455	Nov 1995	JP
8-29224	Feb 1996	JP
8029224	Feb 1996	JP
96029224	Feb 1996	JP
9-327511	Dec 1997	JP
9327511	Dec 1997	JP
10085324	Apr 1998	JP
H1085324	Apr 1998	JP
11-137672	May 1999	JP
11137672	May 1999	JP
2000-217908	Aug 2000	JP
2000-296318	Oct 2000	JP
200120483	Dec 2000	JP
2001-270856	Oct 2001	JP
2003047657	Feb 2003	JP
2003-513714	Apr 2003	JP
2011-172961	Aug 2011	JP
2014520593	Aug 2014	JP
1012918	Mar 1981	SE
1344362	Jun 1984	SE
1001945	Mar 1983	SU
1992 018048	Oct 1992	WO
9415099	Jul 1994	WO
9420158	Sep 1994	WO
9502559	Jan 1995	WO
9517597	Jun 1995	WO
9535124	Dec 1995	WO
9625214	Aug 1996	WO
9640318	Dec 1996	WO
9709074	Mar 1997	WO
9747337	Jun 1997	WO
9817333	Apr 1998	WO
9822165	May 1998	WO
9823353	Jun 1998	WO
9832477	Jul 1998	WO
9903519	Jan 1999	WO
9906082	Feb 1999	WO
9942150	Aug 1999	WO
0009182	Feb 2000	WO
0020050	Apr 2000	WO
0020052	Apr 2000	WO
0031967	Jun 2000	WO
0050143	Aug 2000	WO
0057925	Oct 2000	WO
0057926	Oct 2000	WO
0057927	Oct 2000	WO
0057928	Oct 2000	WO
0064510	Nov 2000	WO
0137786	May 2001	WO
0137894	May 2001	WO
0137895	May 2001	WO
0137900	May 2001	WO
0141831	Jun 2001	WO
0141832	Jun 2001	WO
0141833	Jun 2001	WO
0142758	Jun 2001	WO
0145769	Jun 2001	WO
0147576	Jul 2001	WO
0243859	Jun 2002	WO
2007118235	Oct 2007	WO
2008138311	Nov 2008	WO
2011069110	Jun 2011	WO
2012120078	Sep 2012	WO
2012129501	Sep 2012	WO

Non-Patent Literature Citations (18)

Entry
International Search Report for corresponding International Application PCT/US2009/031809 dated Oct. 19, 2009.
Written Opinion for corresponding International Application PCT/US2009/031809 dated Oct. 19, 2009.
Japanese Office Action dated Dec. 14, 2012 for related Application No. 2011-100145—corresponding communication indicates no references cited in JP Office Action (1 page).
Fresenius 90/2 Peritoneal Therapy Cycler, Articile, written by Fresenius SA, dated Jul. 1993—6 pages.
Notice of Reasons for Rejection dated Dec. 5, 2017 in corresponding JP Application No. 2013-257132.
European Search Report—EP Application No. 16176496 dated Mar. 21, 2017—13 pages.
European Communication—EP Application No. 09710209.9 dated Mar. 20, 2015—6 pages.
Search and Examination Report dated Jul. 29, 2014 for related GB Appl. No. 1322331.8.
Office Action for Mexican Patent Application No. MX/a/2010/008961 received Apr. 22, 2013.
International Search Report for PCT/US2017/031405 dated Sep. 26, 2017—7 pages.
Written Opinion of the International Searching Authority for PCT/US2017/031405 dated Sep. 26, 2017—13 pages.
International Search Report for PCT/US2017/031400 dated Sep. 26, 2017—7 pages.
Written Opinion of the International Search Authority for PCT/US2017/031400 dated Sep. 26, 2017—14 pages.
International Search Report for PCT/US2017/031396 dated Jul. 27, 2017—6 pages.
Written Opinion of the International Search Authority for PCT/US2017/031396 dated Jul. 27, 2017—7 pages.
U.S. Appl. No. 15/195,801, filed Jun. 28, 2016.
Japanese Office Action received Jun. 13, 2013 for Japanese Application No. 2011-100145.
Japanese Office Action dated Feb. 18, 2014 for related Japanese Appln. No. 2013-051434.

Related Publications (1)

	Number	Date	Country
	20200092259 A1	Mar 2020	US

Medical device system including information technology infrastructure having secure cluster domain supporting external domain

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

International Classifications

Term Extension

Abstract