WO2018022355A1

WO2018022355A1 - Cloning medical device configurations

Info

Publication number: WO2018022355A1
Application number: PCT/US2017/042633
Authority: WO
Inventors: Donald Eugene DIEZ; Glen James LARSON; Jennifer Lynn Pavlovic; James B. Drost; Grant A. Adams
Original assignee: Smiths Medical Asd, Inc.
Priority date: 2016-07-25
Filing date: 2017-07-18
Publication date: 2018-02-01

Abstract

Embodiments include a system of localized cloning of a plurality of child medical devices with common operating parameters of a parent medical device. The system includes a rack including a plurality of mounting structures configured to physically and removably couple a plurality of child medical devices and a parent medical device. The system also includes a digital communication bus provided on the rack that enables communication between the parent medical device and the plurality of child medical devices that are coupled to the rack. Additionally, the parent medical device adjusts one or more operating parameters of the plurality of child medical devices with communications sent via the digital communication bus.

Description

CLONING MEDICAL DEVICE CONFIGURATIONS

CROSS REFERENCE TO RELATED APPLICATION

The present application claims the benefit of US Provisional Patent Application No. 62/366,440, filed on July 25, 2016, which is hereby fully incorporated herein by reference.

TECHNICAL FIELD

Embodiments relate generally to communication and control components and systems for medical devices and, more particularly, to informational, advisory, and control devices and systems for infusion pumps and other coordinated medical devices. Embodiments specifically include systems, methods and apparatus for locally transferring operating parameters between medical devices.

BACKGROUND

In the medical arts, medical devices such as infusion pumps have been useful for managing the delivery and dispensation of a prescribed amount or dose of a drug, fluid, fluid- like substance, or medicament (hereinafter, collectively, an "infusate") to patients. Infusion pumps can provide some significant advantages over manual infusion techniques, by accurately delivering and dispensing infusates over an extended period of time. Infusion pumps are particularly useful for treating diseases and disorders that require regular pharmacological intervention, including cancer, diabetes, and vascular, neurological, and metabolic disorders. They also enhance the ability of healthcare providers to deliver anesthesia and manage pain. Infusion pumps are used in various settings, including hospitals, nursing homes, and other short-term and long-term medical facilities, as well as in residential care settings. Infusion pumps can include various constructions, modes of operation, and types. Generally, infusion pumps include portable or ambulatory pumps, large volume pumps (LVPs), patient-controlled analgesia (PCA) pumps, peristaltic pumps, elastomeric pumps, syringe pumps, enteral pumps, and insulin pumps. Depending upon their specific designs and intended uses, infusion pumps can be used to administer infusates through various delivery methods, including intravenously, intraperitoneally, intra-arterially, subcutaneously, neuraxially, and specifically into an intraoperative site, epidural space, and subarachnoid space.

In hospitals, clinics, and other medical environments, including in-home care, patient safety continues to be a paramount concern along with improved workflow efficiencies. This has been especially true when dealing with vulnerable patients and situations in which potent infusates capable of causing significant physiological or chemical effects are being administered. Accordingly, medical practitioners strive to ensure that patients receive safe and appropriate medical care including appropriate infusions of infusates. The "five rights of medication administration", commonly referenced in connection with ensuring safe infusions, are: the right medication (determining if a particular infusate has been prescribed correctly); the right patient (determining if the infusate was prescribed for the correct patient); the right dose (determining what volume or how many milliliters, tablets, or doses of the infusate are to be given to the patient); the right route (determining if the infusate should be given to the patient intravenously or by mouth, feeding tube, or other injection, etc.); and the right time (determining what time of day the infusate should be delivered to the patient). Accordingly, most infusion pump manufacturers and users have been keenly interested in ensuring that these "five rights" are implemented, observed, and verified.

Infusion pumps may be controlled locally via the programming of each individual pump. For example, a medical practitioner can configure an infusion pump to execute a delivery profile that corresponds to a patient's treatment needs, or a patient can configure an infusion pump according to their individual requirements within pre-defined limits without the involvement of a physician. Alternatively, infusion pumps may be controlled via other techniques such as by, for example, a network server that communicates with the pumps. Hospital information systems (HIS) and electronic medical record (EMR) systems may, in some circumstances, provide such network functionality.

Generally, an infusion pump is specifically programmed or configured according to certain physiological, pharmacokinetic, and operational parameters or limits that are often predefined and with the safety provisions of the "five rights" in mind. In recent years, infusion pumps have become increasingly sophisticated and may include such features as close error reduction software, which enable infusion pumps to perform functions that assist in proper programming and calculating of dosing and delivery rates in an effort to reduce medication errors and potentially consequential patient harm. Infusion pumps can also be programmed or configured to access databases (often referred to as "drug libraries") containing information relating to medications that can be used with a specific pump, as well as information corresponding to dosing guidelines, drug concentrations, dose limits, and clinical advisories. Such features can include medication safety software and "guard toolboxes" and servers. These features may generally enable healthcare providers to select medications from pre-loaded lists, which can be tailored to each healthcare facility and patient care area. Additionally, healthcare facilities can integrate infusion pumps with electronic medical records, computerized order entry systems, and medication recognition systems, such as, e.g., barcode scanning systems, to further enhance safety and efficacy. Healthcare facilities can also choose to generally or specifically implement dosing and delivery limitations, commonly called hard and soft limits, on preselected drugs.

In traditional infusion systems, infusion pumps are individually programmed, meaning that concentration limits, volume limits, and other limits or boundaries, as well as other medicament or drug programming parameters are set individually for each such infusate and the pump is programmed within those boundaries. Moreover, it is not uncommon for several infusion pumps to be employed to deliver various infusates to a single patient. A medical practitioner or doctor must spend time programming each of the infusion pumps separately, and respectively program each of the infusion pumps. It can take substantial effort and time to program all of the infusion pumps needed for a particular patient or procedure. Over the course of a week, this can easily mean hours of infusion pump programming. This sort of repetitive, individual programming of pumps can be laborious, time-consuming, and subject to human error.

Accordingly, there is a need for devices, systems, and methods for procedure-based programming for infusion pumps that can minimize repetitive, laborious, time-consuming, and/or potentially erroneous interactions of certain infusion pump programming tasks. Medical devices used in systems as described, for example, are increasingly complex and can require significant programming and attention, particularly when multiple medical devices are required for a given patient or procedure. Consequently, a system providing a more efficient and effective infusion pump and medical device programming is desired. This is true whether in total, or individually, or in various sub-combinations. Various new pumps, systems, methods and other arrangements could be decidedly advantageous in provision or improvement of patient safety, workflow efficiency, programming, control, and operational parameters or limits, etc., for infusion pumps and other coordinated medical devices.

SUMMARY

Embodiments described or otherwise contemplated herein substantially provide the aforementioned advantages of providing or improving patient safety, workflow efficiency, programming, control, and operational parameters or limits, among possible other advantages.

One embodiment relates to a system of localized cloning of a plurality of child medical devices with common operating parameters of a parent medical device. The system includes a rack including a plurality of mounting structures configured to physically and removably couple a plurality of child medical devices and a parent medical device. The system also includes a digital communication bus provided on the rack that enables communication between the parent medical device and the plurality of child medical devices that are coupled to the rack. In the system, the parent medical device can adjust one or more operating parameters of the plurality of child medical devices with communications sent via the digital communication bus.

Another embodiment relates to a system for configuring a selected operating parameter for a plurality of medical devices. The system includes a rack, configured to physically and removably couple the plurality of medical devices as well as a router, configured to enable digital communications between the plurality of medical devices that are physically and removably coupled to the rack with a local area network. Further, a selected one of the plurality of medical devices communicates the selected operating parameter to others of the plurality of medical devices depending upon whether the plurality of medical devices are physically coupled to the rack and communicatively coupled to the local area network through the router.

An embodiment relates to a mounting rack for localized cloning of a plurality of child medical devices with operating parameters of a parent medical device. The mounting rack includes a mounting structure including a plurality of coupleable receptacles that are each structured to receive one of a plurality of medical devices as well as a digital communication bus including a set of communication hardware integrated between the plurality of coupleable receptacles. The plurality of medical devices are releaseably coupled to the rack and readily transfer a set of operating parameters from a parent medical device to one or more child medical devices.

Another embodiment relates to an infusion pump providing localized cloning of operating parameters. The infusion pump includes a pump housing, a pumping mechanism, a pump control system and a control module. The pumping mechanism is coupled to the pump housing that selectively delivers an infusate to a patient. The pump control system includes a processor and a memory programmable to control operation of the pumping mechanism. The control module relays commands to the pump control system including a user interface. The user interface provides selection of multiple operation modes including a parent clone mode, enabling transfer of operating parameters and a child clone mode, enabling receipt of operating parameters. In some embodiments, the parent clone mode includes searching to locate one or more child infusion pumps connected to a common local access point for medical devices, displaying one or more child clone pumps on a pump screen/display, establishing a connection with each of the one or more child clone pumps, transferring desired operating parameters and information to each of the child clone pumps, verifying transferred operating parameters and information is correct, and collecting information regarding the transfer. In some embodiments, the child clone mode includes: searching to locate a parent clone infusion pump connected to a common local access point for medical devices, displaying the parent pump on a pump screen, establishing a connection with the parent clone infusion pump, receiving desired operating parameters and information from the parent clone infusion pump, verifying transferred operating parameters and information is correct, and collecting information regarding the transfer.

Another embodiment includes a method of localized cloning of a medical device. The method includes: connecting a parent medical device to a mounting rack, connecting one or more child medical devices to the mounting rack, establishing a set of operating parameters for the parent medical device, initiating a search enabling the parent medical device and the one or more child medical devices to recognize one another to establish a connection, and approving transfer of the set of operating parameters from the parent medical device to the one or more child medical devices. Some embodiments further including verifying that the set of operating parameters was transferred.

A further embodiment relates to a method of localized cloning of a medical device. The method includes: searching for one or more child medical devices to the medical device that are connected to a common a digital communication bus and coupled to a common mounting structure, displaying the one or more child medical devices on a display of the medical device, establishing a connection with each of the one or more child medical devices, transferring operating parameters to each of the one or more child medical devices, verifying that the operating parameters transferred are correct, and collecting information regarding transfer of the operating parameters.

The foregoing summary is not necessarily intended to describe each illustrated embodiment or every implementation of the subject matter hereof. The figures and the detailed description that follow more particularly exemplify the embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

Subject matter hereof may be more completely understood in consideration of the following detailed description of various embodiments of the subject matter in connection with the accompanying drawings, in which:

FIGS. 1 A-C are various infusion pumps that are examples of medical devices that can be part of localized cloning systems, applications or methods, according to various embodiments.

FIG. 2 is a block diagram of various elements of an infusion pump system that can be part of localized cloning systems, applications or methods, according to various embodiments.

FIG. 3 is an example of a mounting rack including a plurality of infusion pumps coupled to the mounting rack, according to an embodiment.

FIG. 4 is a diagram of a localized cloning system for medical devices, according to an embodiment.

FIG. 5 is a diagram showing a localized cloning of medical devices arrangement, according to an embodiment. FIG. 6 is a diagram showing a localized cloning of medical devices arrangement, according to an embodiment.

FIG. 7 is a diagram showing a localized cloning arrangement, according to an embodiment.

FIG. 8 is a flow chart of a method of localized cloning of a medical device, according to an embodiment.

FIG. 9 is a flow chart of a method of localized cloning of a medical device, according to an embodiment.

While embodiments are amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit subject matter hereof to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of subject matter hereof in accordance with the appended claims.

DETAILED DESCRIPTION

Medical device systems including multiple programmed infusion pumps and/or other medical devices are increasingly complex. The need for and advantages of a simplified setup and control for these types of systems has been recognized by applicants. The following disclosure relates to specifically to technology and methods aimed at this.

First, for organization and simplicity, aspects of patient safety, workflow efficiency, programming, control, and operational parameters or limits, among potentially other important considerations, can be understood at times throughout this disclosure as belonging to integrated informational, advisory, and control ("Inform / Advise / Control") systems, whether in total, or individually, or in various sub-combinations:

"Inform" pertains to a linking and transfer of patient and medical device data for both use and view by means of a portal or user interface; "Advise" pertains to use of the "Inform" data to derive clinical suggestions or recommendations for a particular patient's therapy; and "Control" pertains to use of, for example, algorithms and/or real-time patient data to change a therapy, with or without direct involvement of a medical practitioner.

In an embodiment of a medical device or system incorporating an Inform / Advise / Control system, "Inform" (if included in a particular embodiment) could assist in meeting a practitioner's need or desire for easily and efficiently obtaining data from a medical device or coordinated group of devices in treatment of a particular patient. Such data could include, for example, information on the status and operating parameters of the device or group of devices and/or so-called Continuous Quality Improvement or "CQI" data. The data could also be used, for example, to populate the EMR. Beyond "Inform", "Advise" (if included in a particular embodiment) could assist in meeting a practitioner's need or desire for easily and efficiently obtaining more information on how to improve clinical outcomes and/or provide recommended therapies. This could be provided by, for example, an "Advise" system utilizing "Inform" data that then links patient outcomes to therapies provided by the medical devices. The medical devices themselves could accordingly be linked in so-called machine- to-machine (M2M) fashion. "Advise" could also introduce new algorithms that link therapies to desired effects; and through "Advise", practitioners could be provided with means for creating their own algorithms and decision support rules. Beyond "Advise", "Control" (if included in a particular embodiment) could assist in meeting a practitioner's need or desire for easily and efficiently acknowledging a changed therapy within medication safety software limits. M2M interfaces could link patient states to therapeutic actions, and the algorithms could titrate infusates to desired therapeutic effects.

Embodiments of an Inform / Advise / Control system, whether in total, or individually, or in various sub-combinations, could be decidedly advantageous in provision or improvement of patient safety, workflow efficiency, programming, control, and operational parameters or limits, etc., for infusion pumps and other coordinated medical devices.

One specific area involving an Inform / Advise / Control type system which applicants have identified for improvement relates to efficiently programming multiple medical devices such as infusion pumps. Users often would prefer not to set up multiple related medical devices manually. In general, setting up multiple medical devices manually can be time-consuming, repetitive, or otherwise undesirable as a task for users, such as medical staff or professionals. Accordingly, the described cloning system or device, where one medical device readily reconfigures other medical devices to be generally identical copies or at least contain a set of common operating parameters, is highly desirable.

In various embodiments, only the origin of the set up for a "parent" medical device are locally, manually configured. In other embodiments, a parent medical device set-up can locally originate from another source. Once the parent medical device is configured, it can then be used to transfer information to other "child" medical devices by localized transfer and subsequent local transfers throughout the facility or healthcare system.

The type of localized cloning systems contemplated by this disclosure can be advantageous in many ways. For example, many facilities currently do not have server systems for sharing operational configurations in a large system-wide fashion. This method provides cloning of medical devices without requiring a server system or computer to be present. This system can also be adapted to provide a level of security to the medical device configurations themselves.

FIGS. 1A-C show various pumps 100 as examples of medical devices that can be used in Inform / Advise / Control systems. Namely, the pumps 100 (also referred to and distinguished more specifically as pumps 100A, 100B and lOOC, respectively, in FIGS 1A, IB, and 1C) shown are examples of various infusion pumps that can be used in a localized cloning system or method.

Infusion pumps 100A and 100B, shown respectively in FIGS. 1A and IB, are a syringe-type pumps that can be used to deliver a wide range of drug therapies and treatments. Infusion pumps 100A and 100B include a pharmaceutical container or syringe 110, which is supported on and secured to housing 120 by clamp 130, respectively. In embodiments, syringe 110 can be separately supplied from the respective pump 100. In other embodiments, syringe 110 is an integrated component of pump 100. Syringe 110 includes a plunger 140 that forces fluid outwardly from syringe 110 via infusion line 160 that is connected to a patient. A motor and lead screw arrangement internal to housing 120 of pump 100 cooperatively actuates a pusher or plunger driver mechanism 170, to move plunger 140. In embodiments, a sensor can monitor force and/or position of the plunger 140 in the syringe 110 according to system specifications. Also, depicted on the pumps 100A and 100B is at least one user interface 172 for operator input and/or display 174. In various embodiments, the display 174 can also be combined with or serve as part of a user interface 172 as a touch screen or touchless interface, for example. Infusion pump lOOC shown in FIG. 1C is an example of an ambulatory infusion pump that can be used to deliver a wide range of drug therapies and treatments. Such ambulatory pumps can be comfortably worn by or otherwise removably coupled to a user for in-home ambulatory care by way of belts, straps, clips or other simple fastening means, and can also be alternatively provided in ambulatory pole-mounted arrangements within hospitals and other medical care facilities.

Infusion pump lOOC generally includes a peristaltic type infusion pump mechanism that controls the flow of medication from a reservoir (not shown in FIG. 1C) of fluid coupled to pump lOOC through a conduit from the reservoir which matingly passes along bottom surface 180 of pump lOOC. The reservoir can comprise a cassette that is attached to the bottom of pump lOOC at surface 180, or an IV bag or other fluid source that is similarly connected to pump lOOC via an adapter plate (not shown) at surface 180. Specifically, pump lOOC uses valves and an expulsor located on bottom surface 180 to selectively squeeze a tube of fluid (not shown) connected to the reservoir to effect the movement of the fluid supplied by the reservoir through the tube and to a patient in peristaltic pumping fashion. Pump lOOC also has at least one user interface 182 for operator input and/or display 184. In various embodiments, the display 184 can also be combined with or serve as part of a user interface 182 as a touch screen or touchless interface, for example.

Infusion pumps 100A, 100B, and lOOC are each examples of infusion pumps that can be suitable for use with embodiments discussed herein, though other pumps and devices can be used in various other embodiments of infusion systems utilizing subject matter hereof.

FIG. 2 is a block diagram of an infusion pump system 200. System 200 includes infusion pump 100 having pump control system 202 with processor 204 and memory 206 programmable with selected protocols, profiles, segments of profiles, and other settings for controlling operation of pumping mechanism 208 such as, for example, the aforementioned syringe and ambulatory or peristaltic type mechanisms that can draw infusate from a reservoir or other fluid or infusate source 210. In embodiments, reservoir 210 can comprise any suitable infusate supply, such as an IV bag, syringe, continuous supply, or other infusate storage.

Processor 204 can be any programmable device that accepts digital data as input, is configured to process the input according to instructions or algorithms, and provides results as outputs. In an embodiment, processor 204 can be a central processing unit (CPU) configured to carry out the instructions of a computer program. Alternatively, processor 204 can be an application specific integrated circuit (ASIC) or a field-programmable gate array (FPGA). Processor 204 is therefore configured to perform arithmetical, logical, and input/output operations.

In an embodiment, memory 206 can comprise volatile or non-volatile memory as required by the coupled processor 204 to not only provide space to execute the instructions or algorithms, but to provide the space to store the instructions themselves. In embodiments, volatile memory can include random access memory (RAM), dynamic random access memory (DRAM), or static random access memory (SRAM), for example. In embodiments, non-volatile memory can include read-only memory, flash memory, ferroelectric RAM, hard disk, floppy disk, magnetic tape, or optical disc storage, for example.

The infusion pump 100 also includes a control module 220 for relaying commands to the pump control system 245. Control module 220 includes at least one user interface 230 utilizing an operator input including input mechanism(s) 235, that works cohesively with a display screen 225. In some cases, the display 225 will be considered part of the user interface(s) 230. In some embodiments, operation modes including a parent clone mode and a child clone mode may be selectable by this user interface 230. User interface 230 generally allows a user to enter various operating parameters, including but not limited to names, drug information, limits, delivery shapes, information relating to hospital facilities, as well as various user-specific operating parameters (e.g., patient age and/or weight).

In some embodiments, the infusion pump 100 includes a USB port or other appropriate input/output (I/O) interface port 240 for connecting the infusion pump 100 to a network or computer 250 having software designed to interface with the infusion pump 100. In some cases, the input/output port 240 may also be useful for connecting to a rack or other hardware for localized wired or wireless networking or connectivity. Embodiments relating to rack and other subnet or hardware arrangements will be discussed later in greater detail. Power to the infusion pump 100 is accomplished via an AC power cord or internally provided battery.

User inputs 260 to the system are provided by programming of a user such as a nurse, physician, or other medical practitioner. These inputs 260 can include a variety of forms. The inputs 260 are generally received by the operator input mechanisms 235.

In FIG. 3, a plurality of infusion pumps 100 are depicted as each being installed in a generally vertical stacked relationship along pole 310 as part of a localized cloning system 300. Although illustrated fragmentally, it will be appreciated by those of skill in the art that pole 310 may be any suitable and generally vertical support structure such as is commonly used for suspending elevated intravenous (IV) fluid reservoirs, bags, and the like. A rack 302 is coupled to pole 310 by way of pole clamp and pumps 100 are each removably couplable to rack 302. In other embodiments, rack 302 may be freestanding or coupled to other structures or support features. Accordingly, mounting rack 302 includes a plurality of infusion pumps 100 coupled to the mounting rack 302 that are vertically aligned, stacked, and coupled to the mounting rack 302. Other arrangements are possible in embodiments as well. Infusion pumps 100 merely represent one type of medical device that could be mounted on a rack 302. Other medical devices of various shapes sizes and functions could be coupled to a rack as well. Examples of other medical devices include various types of monitors, sensors and status/ alerting devices (e.g. pulse oximeters, blood pressure monitors, blood gas sensors, breathing assistance devices, and core temperature sensors, among others) that are routinely used in hospital settings for patient care. The system is "localized" as cloned parameters are configured and transmitted in close physical proximity and/or to a limited group of interconnected devices. Cloning is not performed in a system-wide, centralized manner but through local device to device interactions, via rack 302, local router, or other intermediary structures in certain embodiments, in which local transmission of information or operating parameters from one physical device to another is made possible.

FIG. 4 depicts a diagram of a localized cloning system 400, similar to the specific localized cloning system 300 shown in FIG. 3. The system 400 includes a rack 402, digital communication bus 404, router 406, and a plurality of medical devices 410, 420, 430, 440 and 450.

System 400 can be understood in certain embodiments as providing localized cloning of operating parameters of one medical device to a plurality of other medical devices, all coupled to a common local component or interface. For purposes here, the one medical device will be identified as a parent medical device 410 and the plurality of other medical devices will be referred to as child medical devices 420, 430, 440 and 450. In some systems, any of the medical devices could be deemed the parent device as this function is not necessarily dictated by pump physical location or position. Further, while four child medical devices are shown, this number of child medical devices should not be viewed as limiting. Fewer or additional medical devices may be present in certain embodiments. In general, rack 402 can take on various shapes and sizes. In some cases, rack 402 may be similar to the rack 302 shown in FIG. 3. However, the shape and size of rack 402 is not limited to such an arrangement and can be a structure suitably adapted to effectively mount and connect the various medical devices desired. Rack 402 generally includes at least a plurality of mounting structures 460 configured to physically and removably couple the plurality of child medical devices 420, 430, 440 and 450 to a parent medical device 410. Mounting structures 460 can include any attachment structure or mechanism used to physically couple the medical devices to the rack 402. Digital communication bus 404 is shown as integrated with or on rack 402. Digital communication bus 404 enables communication between the parent medical device 410 and the plurality of child medical devices 420, 430, 440 and 450 that are coupled to the rack 402. Medical devices 410, 420, 430, 440 and 450 may be infusion pumps 100, as shown in FIGS. 1 A-C and/or FIG. 2 in some embodiments.

In the system 400 in FIG. 4, it is possible for parent medical device 410 to adjust one or more operating parameters of the plurality of child medical devices 420, 430, 440 and 450 by sending communications across the digital communication bus 404 with instructions to make these changes. Accordingly, the operating parameters of the parent medical device will be transferred to the child medical devices. Digital communication bus 404 generally refers to a communication system that transfers data between components inside a computing device, or between computing devices. In some embodiments, bus 404 can cover all related hardware components (wire, optical fiber, etc.) and software, including communication protocols. Bus 404 could utilize an Ethernet, SPI, CAN, RS232, wireless or other communication architecture or method. Bus 404 can include a wireless digital communications bus or other wireless communications architecture. In some embodiments, digital communication bus 404 may include a router 406. Router 406 can be configured to enable digital communications between the medical devices 410, 420, 430, 440 and 450 that are physically and removably coupled to the rack 402 and into a local area network (LAN) 408, in certain embodiments. In some embodiments, medical devices may not be physically coupled to a common rack, but rather, be part of a group of devices associated with one another by way of a connection to a common local access point. In some cases, this local access point can be a wired or wireless router that manages devices in close proximity.

Accordingly, a rack 402 of medical devices 410, 420, 430, 440 and 450 can be an isolated subnet in a larger communication network. The medical devices on rack 402 can identify that only the medical devices also mounted to the rack are viable partners for the operation. This obviates the possibility that random medical devices in a facility will mistakenly be re-configured. For example, such identification can be implemented by any suitable "five rights" scheme or procedure. In other embodiments, the medical devices mounted to the rack can be identified by a hardware ID such as a media access control (MAC) address, a software ID such as a message header or unique packet identifier, or a network ID such as a subnet mask. One skilled in the art will readily appreciate that combinations of the aforementioned identifiers can be utilized in combination to identify viable partners for configuration. A data structure can be configured to store the subset of medical devices that are identified as viable configuration partners.

Using this system, it is possible to quickly and easily pass on the operating parameters and internal set-up of a medical device. Specifically, the complete internal set-up of a single medical device 410 can be passed to other medical devices 420, 430, 440 and 450 using a digital communication pathway through mounting rack 402. The "complete" set-up includes any downloaded information and modifications to the medical device set-up done on the parent medical device 410. The locally-made configuration may include how alarms are handled (i.e. alarm settings), display intensity and mode, drug library used and any other operating characteristic that can be modified at the medical device 410. In some embodiments, medical device set-up may include cloning firmware or various pieces of software. In some embodiments, cloning a configuration can include sharing alarms or patient data, for example. In some embodiments, operating parameters can relate to firmware updates or medical device set-up. In some cases, medical device set-up includes networking of infusion pumps (including syringe pumps and LVPs) for a particular facility. In some cases, medical device set-up includes establishing Ethernet connections or credentials. Medical device set-up can include setting up authentication protocols, permission levels, or passwords. In some embodiments, medical device set-up includes a merger of event histories. For example, the event history of a parent infusion pump can merge with the event history of a cloned child infusion pump, so as to create a single data file of event history information for both devices. The parent medical devices 410 can be configured from a server, PC-based configuration tool, or in manufacturing, to be the "source" and have its information passed to other child medical devices 420, 430, 440 and 450.

Shown in FIG. 5 is a diagram of a system 500 providing localized cloning of medical devices. See medical devices 502, 504, 506, 508 and 510. As generally depicted in FIG. 5, a child medical device 504a, after cloning by a parent clone 502a, can become a parent clone 504b to another medical device 506 in a "train the trainers" relationship. Likewise, in turn, child clone 506a could become parent clone 506b to clone medical device 508. Child clone 508a would become parent clone 508b to clone medical device 510. This parent and child cloning arrangement can, accordingly, continue as extensively as desired.

To help accomplish this type of system 500, in addition to regular operating modes, medical devices 502, 504, 506, 508 and 510 can have two additional operating modes: a "clone parent" mode; and "clone child" mode. When placed into their respective parent or child cloning mode, the medical devices 502, 504, 506, 508 and 510 will search for appropriate partners on the digital communication bus 404. As partners are found, they are displayed on the display screen of the medical device, such as, for example, display 174 or 184 in Figs. 1A-C. Two "clone parents" would be an error as one, and only one, parent would be allowed. However, there can be one or more "clone children". Once a successful configuration has been made consisting of one parent and one or more children, the cloning operation may be started.

Cloning will include transferring the configuration and verifying that the transfer was correct. In some embodiments, cloning will not be permitted while a medical device is in operation for safety reasons. For example, while an infusion pump is performing an infusion it will typically not be involved in cloning parameters in other medical devices in any way. In some embodiments, cloning parameters can be downloaded and installed after an infusion is complete. In some embodiments, a user may be prompted to complete cloning or initiate downloading of parameters. In other embodiments, robust communications, software, and safety measures will enable simultaneous updates at any time regardless of whether an infusion delivery to a patient is ongoing.

Some embodiments can require that an infusion pump or medical device be placed in a particular operating mode for cloning operations to take place. In some embodiments, no particular operating mode is necessary for cloning operations. In some cases, the system can be arranged to so that a parent medical device and a rack can operate as a type of production fixture in which a many child pumps can be attached to the rack at once for rapid cloning. See FIGS. 6 and 7 also. In one embodiment, eleven child infusion pumps can be attached to a rack and cloned simultaneously. This type of cloning could be made persistent and accordingly, provide a semi-automatic arrangement in which a parent is left in a rack and child pumps are added and removed under the assumption that newly added pumps to the rack are child pumps. In some cases, default relationships of parent and child pumps can be established for cloning operations. Using such default parameters and relationships enables safety measures to be built and put in place.

Information will be collected during the cloning operation to identify who did the cloning and when the cloning occurred. This feature can require a password to engage in cloning activities or can include other configurable access and safety features controlled by authorized users or administrators. In some embodiments, cloning changes to certain portions of an infusion pump drug library can be restricted or entirely prevented. This type of restriction can segregate out parts of a drug library which present a high level of safety risk if incorrectly altered or compromised. For example, an pump administering anesthesia or a pump administering infusions in a NICU may include restrictions. Restrictions on cloning may be put in place to prevent syringe pump programming from being cloned to LVP pumps and vise versa. In general, restrictions can be implemented to prevent cloning operating parameters that are vastly different from one another.

Authorization restrictions can also be implemented in medical device cloning based on event history data. When cloning operations take place, the who, when, and where of these data transfers is recorded. For example, the location of infusion pumps being cloned can be recorded (whether wired on a rack or wireless) as well as a time and date stamp. This can be done with the aid of information such as IP location, GPS, or other location-based identifiers. The serial number of the parent cloning pump and the child receiving pump can, likewise, be recorded for tracking and approval purposes. Tracking this information lends itself to numerous safety and ease-of-use advantages. In terms of creating a record, embodiments that create a merged event history record each time a cloning operation takes place, enables a consolidated data file for both pumps. Consolidated data files of this type can be of assistance in the review of medical device information.

Cloning medical devices, like infusion pumps, can also provide benefits in difficult operating environments, such as the battlefield. Simplifying programming and reducing the possibility of user errors can be extremely important in these locations where efficiency is at a premium and the margin for errors is reduced.

FIG. 6 is another diagram of a system 600 providing localized cloning of medical devices In this embodiment, the system uniformly uses medical device 602 as a parent clone 602a to concurrently program a plurality of medical devices 604, 614 and 624. As shown, these medical devices can, in turn, be used to accept operating parameters or other programming as a child clone 604a, 614a and 624a. Further, the medical devices then can subsequently be configured to operate as a parent clone 604b and 624b in some cases to further pass on operating parameters to other devices such as medical devices 606, 608, 610, and 626 using parent and child cloning relationships as discussed above. Systems 600 can be configured in various ways and are not limited to one particular configuration, number of devices, or structure.

FIG. 7 is a diagram showing a system 700 representing a localized cloning arrangement. In this system 700, cloning between pumps 710, 720 and 730 is local, however, cloning does not necessarily require transfer of operating parameters over a structure, such as a piece of physical hardware with a digital communication bus. Accordingly, parent infusion pump 710 transfers operating parameters wirelessly to infusion pumps 720 and 730, such that each pump need not be individually programmed by the user. Even pumps commonly mounted to a rack or other structure may communicate wirelessly, rather than via a physical wired connection of a bus at times.

Wireless communication technologies that can be used to interconnect medical devices with one another include: infrared communication; ultrasonic communication; Bluetooth®; peer-to-peer or network-based WiFi; short range communication (i.e. ZigBee, ANT, etc.); near-field communication (NFC); and radio-frequency identification (RFID) communication. These wireless technologies can enable the rapid expansion of protocols from one medical device to many medical devices. Accordingly, use of a series of medical devices connected to a common access point, such as a wireless router, can make up a wireless local cloning system. For example, a single access point in a hospital ICU could be responsible for managing cloning infusion pumps in that ICU. Bluetooth®, for example can be effectively used as the communications vehicle in various cloning arrangements. Due to the localized nature of Bluetooth® communications, the inherent proximity limitations of such an arrangement can serve as a control safety measure.

A further cloning arrangement, not specifically discussed thus far, relates to use of a USB stick to provide the localized cloning arrangement. For example, a rack or router can include a USB port that can supply information to a local group of medical devices. The device containing the USB stick accordingly, acts as the parent device and connected devices serve as child devices. In this arrangement, the USB stick would include a configuration file in a format that can be readily accessed and the medical device is permitted to write to that same media. This arrangement can simplify merger of history files onto a single file on the USB stick. The USB stick can then provide automatic uploads and creates a convenient reporting mechanism for reports.

FIG. 8 sets forth a flow chart of a method 800 of localized cloning of a medical device. At 802, the operator connects a parent medical device (i.e. medical device 410 from FIG. 4), to a mounting rack (i.e. rack 402). At 804, the operator connects one or more child medical devices (i.e. medical devices 420, 430, 440, and 450) to the mounting rack. At 806, a set of operating parameters is established for the parent medical device. Once operating parameters are established, as at 808, the operator can initiate a search enabling the parent medical device and the one or more child medical devices to recognize one another to establish a connection. At 810, transfer of the operating parameters is approved from the parent medical device to the one or more child medical devices. Finally, in certain embodiments, at 812, verification of the desired set of operating parameters transferred can take place.

Shown in FIG. 9 is another flow chart of a method 900 of localized cloning of a medical device. The method 900 includes searching, at 902, for one or more child medical devices (i.e. medical devices 420, 430, 440, and 450 from FIG. 4) to a medical device (i.e. medical device 410) that are connected to a common a digital communication bus (i.e. bus 404) and coupled to a common mounting structure (i.e. mounting structure 460). At 904, the one or more child medical devices are displayed on a display (such as displays 174, 184 and/or 225) of the medical device. At 906, a connection is established with each of the one or more child medical devices and at 908 operating parameters are transferred to each of the one or more child medical devices. At 910, the correctness of the operating parameters transferred is verified and, at 912, information regarding transfer of the operating parameters is collected.

Accordingly, numerous advantages can be realized from the cloning systems, applications, and methods described. In some embodiments, the one medical device controller could "clone" a pump 100 in a rack 302 of pumps 100 (referred to as a smart pump stack). See FIG. 3, for example. Accordingly, if one of the pumps 100 in the rack a pump 100 faults or needs to be taken out of service, another pump 100, that is in a rack 302 but not being used, could receive the full programming and current status of pump 100. All programming and status parameters could be transferred to pump 100. A syringe or other reservoir could be quickly moved from pump to pump with very little delay in therapy and no loss of data. A location in the rack 302 could be designated as the spare pump spot. A fault in any other pump 100 in the rack 302 could cause the medical device controller to program the spare pump 100 so that it can be quickly swapped with the pump 100 that has faulted.

It is to be appreciated and understood that methods, systems, and software for downloading, editing, and/or integrating drug delivery profiles or segments of profiles for infusion pumps may allow for complex delivery patterns. It is further to be appreciated and understood that any of the aforementioned delivery profiles or segments of delivery profiles can be stored and/or performed in the infusion pump itself or a computer server, in the pump internally or separately or otherwise remotely from the pump. Further, it is to be appreciated that the aforementioned delivery profiles or segments of delivery profiles can be created by or with outside software or systems and subsequently downloaded to or integrated with the systems and software described herein.

It should also be appreciated that the exemplary embodiment or exemplary embodiments are only examples, and are not intended to limit the scope, applicability, or configuration of the invention in any way. Rather, the foregoing detailed description will provide those skilled in the art with an enabling disclosure for implementing the exemplary embodiment or exemplary embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the scope of the subject matter hereof as set forth in the appended claims and the legal equivalents thereof.

The embodiments above are intended to be illustrative and not limiting. Additional embodiments are within the claims. Although subject matter hereof has been described with reference to particular embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the subject matter. Various modifications to subject matter hereof may be apparent to one of skill in the art upon reading this disclosure. For example, persons of ordinary skill in the relevant art will recognize that the various features described for the different embodiments of the invention can be suitably combined, un-combined, and re-combined with other features, alone, or in different combinations, within the spirit of the subject matter. Likewise, the various features described above should all be regarded as example embodiments, rather than limitations to the scope or spirit of the subject matter. Therefore, the above is not contemplated to limit the scope of the subject matter.

For purposes of interpreting the claims for subject matter hereof, it is expressly intended that the provisions of Section 112(f) of 35 U.S.C. are not to be invoked unless the specific terms "means for" or "step for" are recited in a claim.

Claims

1. A system of localized cloning of a plurality of child medical devices with common operating parameters of a parent medical device, comprising:

a rack including a plurality of mounting structures configured to physically and removably couple a plurality of child medical devices and a parent medical device; and

a digital communication bus provided on the rack that enables communication between the parent medical device and the plurality of child medical devices that are coupled to the rack;

wherein the parent medical device adjusts one or more operating parameters of the plurality of child medical devices with communications sent via the digital communication bus.

2. The system of claim 1, wherein the one or more operating parameters include one or more of: a drug library, an alarm setting, a display intensity setting, a display mode setting, a firmware update, and an event history.

3. The system of claim 1, wherein the digital communication bus uses an Ethernet, SPI, CAN, RS232, or wireless communication architecture.

4. The system of claim 1, wherein the parent medical device is an infusion pump.

5. The system of claim 1, wherein the plurality of mounting structures of the rack are configured for vertically stacking the child medical devices and the parent medical devices.

6. The system of claim 1, wherein adjustments to one or more operating parameters of the child medical devices includes transfer of event history information collected related to the adjustments.

7. The system of claim 6, wherein parent event history information and child event history information is merged.

8. The system of claim 1, wherein cloning adjustments to one or more operating parameters is permitted to occur simultaneously with an infusion delivery to a patient.

9. The system of claim 1, wherein each medical device is assigned default cloning relationship parameters.

10. A system for configuring a selected operating parameter for a plurality of medical devices, comprising:

a rack, configured to physically and removably couple the plurality of medical devices thereto; and

a router, configured to enable digital communications between the plurality of medical devices, that are physically and removably coupled to the rack, with a local area network, wherein a selected one of the plurality of medical devices communicates a selected operating parameter to others of the plurality of medical devices depending upon whether the plurality of medical devices are physically coupled to the rack and communicatively coupled to the local area network through the router.

11. The system of claim 10, wherein the operating parameter is selected from a group consisting of a drug library, an alarm setting, a display intensity setting, a display mode setting, a firmware update and an event history.

12. The system of claim 10, wherein the selected operating parameter comprises a modification to a setting performed by an authorized user on the selected one of the plurality of medical devices.

13. The system of claim 10, wherein one of the others of the plurality of medical devices is designated as a trainer device which enables that trainer device to communicate the selected operating parameter to another medical device that is, subsequently, physically coupled to the rack and communicatively coupled to the local area network through the router.

14. The system of claim 10, wherein the router uses Bluetooth® for digital communication between the plurality of medical devices.

15. An infusion pump providing localized cloning of operating parameters, comprising: a pump housing;

a pumping mechanism coupled to the pump housing that selectively delivers an infusate to a patient;

a pump control system including a processor and a memory programmable to control operation of the pumping mechanism; and

a control module that relays commands to the pump control system including a user interface providing selection of multiple operation modes including:

a parent clone mode, enabling transfer of operating parameters; and a child clone mode, enabling receipt of operating parameters.

16. The infusion pump of claim 15, wherein the parent clone mode includes:

searching to locate one or more child clone infusion pumps connected to a common local access point for medical devices;

displaying one or more child clone pumps on a pump screen;

establishing a connection with each of the one or more child clone pumps;

transferring desired operating parameters and information to each of the child clone pumps;

verifying transferred operating parameters and information is correct; and

collecting information regarding the transfer.

17. The infusion pump of claim 16, wherein the common local access point is located on a common rack structure.

18. The infusion pump of claim 16, wherein the common local access point is a wireless router.

19. The infusion pump of claim 15, wherein the child clone mode includes:

searching to locate a parent clone infusion pump connected to a common local access point for medical devices;

displaying the parent clone infusion pump on the pump screen;

establishing a connection with the parent clone infusion pump;

receiving desired operating parameters and information from the parent clone infusion pump;

verifying transferred operating parameters and information is correct; and

collecting information regarding the transfer.

20. The infusion pump of claim 19, wherein establishing a connection with the parent clone infusion pump is accomplished via a wireless digital communication bus.

21. A method of localized cloning of a medical device, comprising:

searching for one or more child medical devices to the medical device that are connected to a common a digital communication bus and coupled to a common mounting structure;

displaying the one or more child medical devices on a display of the medical device; establishing a connection with each of the one or more child medical devices; transferring operating parameters to each of the one or more child medical devices; verifying that the operating parameters transferred are correct; and

collecting information regarding transfer of the operating parameters.

22. The method of localized cloning of claim 21, wherein information regarding transfer of operating parameters includes one or more of: a drug library, an alarm setting, a display intensity setting, and a display mode setting.