Patent ID: 12257419

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG.1is a block diagram100illustrating a medical device110used in connection with the treatment of a patient. Example medical devices110include, but are not limited to, infusion systems (i.e., systems configured to administer fluid such as medication and food to a patient, etc.) and ventilators (i.e., systems configured to assist a patient with his or her breathing function). The medical device100can include at least one hardware data processor111(which can be a multi-core processor) and memory112storing instructions for execution by the at least one data processor. In addition, the medical device110can include a communications interface113which, depending on the desired implementation, can communicate with external devices/computer networks that are physically connected to the medical device110and/or which are in direct or indirect communication with the medical device110via a wired and/or wireless communications network.

The medical device110can additionally and optionally include at least one mechanically actuatable element114that can have variable operating modes (e.g., variable speeds, active/non-active, etc.). Examples of mechanically actuatable elements114include, for example, a pump used for infusion of fluids to a patient and a pump to deliver gas to a patient for breathing purposes.

The medical device110can also include a display115that renders a graphical user interface that characterizes various aspects regarding the operation of the medical device110. In some implementations, the graphical user interface displayed in the display115includes a plurality of graphical user interface elements which, when activated via user-generated input, causes either a mode of operation of the medical device110to change and/or a view presented in the graphical user interface of the display115to change. The user-generated input can be via various modalities including, for example, the display115if it includes a capacitive or other touch screen interface, mechanical buttons/knobs/sliders external to the display115, and the like.

The medical device110can be coupled to one or more accessories120that form part of the functionality offered by the medical device110(e.g., change the manner in which the at least one mechanically actuatable elements114operate, etc.) and/or which cause the graphical user interface (GUI) rendered within the display115to change (e.g., a different view can be displayed in the GUI, etc.). The accessories120can take a wide variety of forms including components required for the operation of the medical device110, sensors for use by the medical device110, and/or other medical devices involved with the treatment/care of a patient.

The accessories120can be coupled to the medical device110in a variety of manners. For example, the accessory120Acan be connected by a wire/socket providing either unidirectional communication from the accessory120Ato the medical device110or providing bi-directional communication. For example, the accessory120Acan be a vital signs monitor such as a pulse oximeter, a set of electrocardiogram electrodes (collectively ECG), heart rate monitor, blood pressure monitor, as well as other types of physiological/vital sign monitors. In some cases, such as with pulse oximeters, signals are transmitted from the accessory120Ato the medical device110and not vice versa. With other cases, the accessory120Acan receive signals from the medical device110such as the activation of a blood pressure cuff.

Similar to the hard-wired accessory120A, other accessories120Band120Dcan be coupled to the medical device110either directly via peer-to-peer unidirectional or bi-directional communication (as with accessory120D) or indirectly via unidirectional or bi-directional communication over a network130(as with accessory120B) which may be wired and/or wireless. These accessories120Eand120D, while not directly connected to the medical device110can have similar functionality to the accessory120Awhich is hard-wired to the medical device110(as described above). The network130can be, for example, a local area Intranet, a hospital information system, the Internet, and the like.

In other cases, the accessory120Ccan be physically connected to the medical device110either directly or via an adapter or other mechanism. For example, in the case of the medical device110, the accessory120Ccan be an infusion module such as a syringe pump module, a patient controlled analgesia (PCA) module, an enteral pump, an elastomeric pump, a peristaltic pump, a multi-channel pump, or a large volume pump. The accessory120ccan also be a disposable element for use by the medical device110such as a tubing set or other adapter. For example, different tubing sets can, for example, implicate different caregiving modalities. Opaque tubing sets can be used in some applications and/or some tubing sets can act as chemical barriers. Tubing sets can be coded, for example, by an RFID chip, a bar code, a QR code, an optical code, or other, and identified by the medical device110and the medical device110can automatically switch to the appropriate configuration for providing care to the patient. For example, a tubing set that is coded for use with a neonate, would automatically switch the controls, alarms, settings, and other functions appropriate for a neonate rather than an adult.

The accessory120, need not be a tubing set but, rather, can take the form of disposables. For example, the accessory can be a disposable element used for chemotherapy, a syringe for manual administration of medication, epidural disposable, enteral disposable, per-enteral disposable as well as other types of equipment used to deliver fluid to a patient (in the case the case of infusion systems) or gas to a patient (in the case of ventilators).

The medical device110can detect the coupling of an accessory120to it. Coupling, in this regard (unless otherwise specifically specified), can include one or more of: the wired connection of an accessory120Ato the medical device110, the initiation of communication by the medical device110with an accessory120Bvia a network, a direct mechanical/physical coupling of an accessory120cto the medical device110, or peer-to-peer communication between the medical device110and an accessory120D. Upon this detection of the coupling of an accessory120, the medical device110can, in some cases, change a mode of operation of the medical device110. This changing can be based, for example, by accessing a local or remote (via the network130) rules engine/lookup table/server to determine whether or not any changes to the mode of operation medical device110should occur in response to the detection of the accessory120coupling.

The detection of the coupling can occur when the communications interface113initiates communication by receiving data/signals from an accessory120B, D or by initiating bi-directional communication with an accessory120B, D. With the latter, there may be initial handshaking/discovery which is used to initiate the communication and the detection can be considered to occur once such discovery has been completed. Similar handshaking/discovering can occur in connection with a wired accessory120Aas part of establishing unidirectional or bidirectional communication (via the communications interface113).

In some variations, the detection of the coupling of an accessory120can cause an alarm to be triggered and/or to cause the medical device110to cease operation. Such an arrangement is advantageous to avoid misconnections or reconnections in which an accessory120is inadvertently connected to the wrong medical device110(either because of compatibility issues or particular patient care). For example, the current subject matter can be used to detect the misconnection of an air cuff to an IV line. The alarms can be visual indicators (changes in colors to the GUI), audio indicators, and/or vibratory indicators.

In other variations, the detection of the coupling can occur when the accessory120Cis being physically connected to the medical device110or in physical proximity thereof. The physical connection can be detected, for example, using a switch which is mechanically tripped when the accessory120Cis mechanically connected to the medical device110. In the addition or in the alternative, proximity sensors can form part of the medical device110that can be used to detect when the accessory120Cis coupled to the medical device110. Other type of proximity technologies can be used including integrated bar code scanners and other optical technologies, magnetic elements/switches, electromechanical element/switches and the like. In some variations, the medical device110can include a proximity sensor that detect a corresponding signal from the accessory via electromagnetic fields/electromagnetic induction such as, Radio-Frequency Identification (RFID), Near Field Communication (NFC), and the like. In other variations, the medical device110can include an optical sensor that includes an optical sensor to scan or otherwise capture a visual identifier (e.g., bar code, optical pattern, etc.) on the accessory120C(or in some cases on an identifier worn by the patient).

After the detection, the medical device110can associate the coupled accessory120with a different mode of operation and cause the medical device110to commence operation according to such different mode operation. The different mode of operation can include automatically changing one or more operating parameters of the medical device110and/or changing elements within the GUI rendered in the display115(i.e., a different GUI view can be displayed). This changing can, for example, be automatic in that it is implemented by the medical device110without any clinician intervention. In some variations, the GUI rendered in the display115can provide a prompt to a caregiver to approve the change of the mode of operation of the medical device110(upon the detection of coupling of the accessory120).

In some cases, changing the mode of operation can include changing one or more operating parameters associated with the mechanically actuatable element(s)114. For example, the mechanically actuatable element114can be a pump that is used by the accessory120for various purposes such as fluid infusion or gas delivery to a patient. The changes in mode of operation can accommodate different flow rates, operating time periods, periodicity of operation, and the like.

In other variations, changing of the mode of operation can include updating software/firmware that is executed by the medical device110. In such implementations, the medical device110, in response to the detection of the coupling of the accessory120, can poll a remote computing system/device to indicate such coupling, and such remote computing system/device can reply with data encapsulating information required for such an update of the software/firmware. For example, a software update can include a new/expanded drug library associated with the accessory120. This drug library can be obtained, for example, by polling a hospital pharmacy system with an identification associated with the medical device110and/or the patient to ensure that the proper drugs/medication/treatment is administered to the patient. The software update can additionally/alternatively include data including a prescription for the patient obtained, for example, from the hospital pharmacy system. The remote computing system/device can also provide information about permitted medications to be administered to the patient as well as related concentrations, doses, and the like. Relatedly, information about allergies and/or medications which cannot be mixed with prescribed medications can be provided. In addition or in the alternative, the polling of the remote computing system can be implemented to ensure, for example, that the medical device110is licensed to implement the corresponding operations/actions.

FIG.2is a system diagram illustrating a computing landscape200within a healthcare environment such as a hospital that includes one or medical devices110as described above. Various devices and systems, both local to the healthcare environment and remote from the healthcare environment, can interact via the network130(which can be one of a plurality of networks). The computing network130can provide any form or medium of digital communication connectivity (i.e., wired or wireless) amongst the various devices and systems. Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), and the Internet. In some cases, one or more of the various devices and systems can interact directly via peer-to-peer coupling (either via a hardwired connection or via a wireless protocol such as BLUETOOTH, ZIGBEE, short range radio, WiFi, etc.). In addition, in some variations, one or more of the devices and systems communicate via a cellular data network.

The medical devices110can each include at least one communications interface113that can access the computing network130either via a fixed wired connection or via a wireless connection (via, for example, one or more access points). In addition, the medical devices110can also couple to other components within the computing landscape200via direct wired or wireless peer-to-peer coupling (not shown). Furthermore, in some cases, the medical devices110can be self-contained and are not connected to any other devices or networks. The medical devices110can transmit data via the computing network130to any of the other components within the landscape200that can, for example, characterize the medical device110. In addition, the medical devices110can receive data from the computing network130relating to monitoring and in some cases controlling one or more attributes of the medical devices110(e.g., software updates, configuration updates, historical data, status information, assets location, patient information, etc.).

In particular, aspects of the computing landscape200can be implemented in a computing system that includes a back-end component (e.g., as a data server210), or that includes a middleware component (e.g., an application server215), or that includes a front-end component (e.g., a client computer220having a graphical user interface or a Web browser through which a user may interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, or front-end components. A client220and server210,215are generally remote from each other and typically interact through the communications network130. The relationship of the clients220and servers210,215arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. Clients220can be any of a variety of computing platforms that include local applications for providing various functionality within the healthcare environment. Example clients220include, but are not limited to, desktop computers, laptop computers, tablets, and other computers with touch-screen interfaces. The local applications can be self-contained in that they do not require network connectivity and/or they can interact with one or more of the servers210,215(e.g., a web browser).

A variety of applications can be executed on the various devices and systems within the computing landscape including the medical devices110such as electronic health record applications, medical device monitoring, operation, and maintenance applications, scheduling applications, billing applications and the like. As another example, the applications can comprise a collection of enterprise-based applications that provide dose error reduction software (DERS) for the medical devices110incorporates a role-based view of infusion data, provides a comprehensive platform for connectivity to external hospital applications, and enables directed maintenance and calibration activities for devices, storage of clinical and device history, etc. As a further example, the applications can provide for remote alarms management and/or asset tracking for the medical devices110.

The network130can be coupled to one or more data storage systems225. The data storage systems225can include databases providing physical data storage within the healthcare environment or within a dedicated facility. In addition, or in the alternative, the data storage systems225can include cloud-based systems providing remote storage of data in, for example, a multi-tenant computing environment. The data storage systems225can also comprise non-transitory computer readable media.

Mobile communications devices (MCDs)230can also form part of the computing landscape200. The MCDs230can communicate directly via the network130and/or they can communicate with the network130via an intermediate network such as a cellular data network. Various types of communication protocols can be used by the MCDs230including, for example, messaging protocols such as SMS and MIMS. In some cases, the MCDs230can receive alerts generated from the operation of the medical devices110and/or they can otherwise be used to monitor the operation of such medical devices110.

Various types of medical devices110can be used as part of the computing landscape200. These medical devices110can comprise, unless otherwise specified, any type of device or system with a communications interface that characterizes one or more physiological measurements of a patient and/or that characterize or are used for the treatment of a patient. In some cases, the accessories120communicate via peer to peer wired or wireless communications with a medical device110(as opposed to communicating with the network130). For example, the accessory120can comprise a bedside vital signs monitor that is connected to a medical device110. One or more attributes of the medical devices110can be locally controlled by a clinician, controlled via a clinician via the network130, and/or they can be controlled by one or more of a server210,215, a client220, or a MCD230.

The computing landscape200can provide various types of functionality as may be required within a healthcare environment such as a hospital. For example, a pharmacy can initiate a prescription via one of the client computers220. This prescription can be stored in the data storage225and/or pushed out to other clients220, an MCD230, and/or one or more of the medical devices110. In addition, the medical devices110can provide data characterizing one or more physiological measurements of a patient and/or treatment of a patient (e.g., medical device110can be an infusion management system, etc.). The data generated by the medical devices110can be communicated to other medical devices110, the servers210,215, the clients220, the MCDs230, and/or stored in the data storage systems225.

Various methods can be implemented in accordance with the current subject matter.FIG.3is a process flow diagram300in which, at310, a medical device, such as an infusion system or a ventilator, detects that an accessory has been coupled to it. The medical device includes at least one data processor, memory, and a display for rendering a graphical user interface and initially operates in a first mode of operation. Thereafter, at320, the medical device associates, in response to the detecting, the accessory with a different mode of operation for the infusion system. The different mode of operation can changes at least one of: operating parameters for the infusion system or elements within the graphical user interface. Subsequently, at330, the mode of operation of the medical device is automatically changed from the first mode of operation to the associated different mode of operation to reflect the coupling of the accessory to the medical device.

In the descriptions above and in the claims, phrases such as “at least one of” or “one or more of” may occur followed by a conjunctive list of elements or features. The term “and/or” may also occur in a list of two or more elements or features. Unless otherwise implicitly or explicitly contradicted by the context in which it is used, such a phrase is intended to mean any of the listed elements or features individually or any of the recited elements or features in combination with any of the other recited elements or features. For example, the phrases “at least one of A and B;” “one or more of A and B;” and “A and/or B” are each intended to mean “A alone, B alone, or A and B together.” A similar interpretation is also intended for lists including three or more items. For example, the phrases “at least one of A, B, and C;” “one or more of A, B, and C;” and “A, B, and/or C” are each intended to mean “A alone, B alone, C alone, A and B together, A and C together, B and C together, or A and B and C together.” In addition, use of the term “based on,” above and in the claims is intended to mean, “based at least in part on,” such that an unrecited feature or element is also permissible.

One or more aspects or features of the subject matter described herein may be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations may include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device (e.g., mouse, touch screen, etc.), and at least one output device.

These computer programs, which can also be referred to programs, software, software applications, applications, components, or code, include machine instructions for a programmable processor, and can be implemented in a high-level procedural language, an object-oriented programming language, a functional programming language, a logical programming language, and/or in assembly/machine language. As used herein, the term “machine-readable medium” refers to any computer program product, apparatus and/or device, such as for example magnetic discs, optical disks, memory, and Programmable Logic Devices (PLDs), used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor. The machine-readable medium can store such machine instructions non-transitorily, such as for example as would a non-transient solid state memory or a magnetic hard drive or any equivalent storage medium. The machine-readable medium can alternatively or additionally store such machine instructions in a transient manner, such as for example as would a processor cache or other random access memory associated with one or more physical processor cores.

With certain aspects, to provide for interaction with a user, the subject matter described herein can be implemented on a computer having a display device, such as for example a cathode ray tube (CRT) or a liquid crystal display (LCD) monitor for displaying information to the user and a keyboard and a pointing device, such as for example a mouse or a trackball, by which the user may provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well. For example, feedback provided to the user can be any form of sensory feedback, such as for example visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including, but not limited to, acoustic, speech, or tactile input. Other possible input devices include, but are not limited to, touch screens or other touch-sensitive devices such as single or multi-point resistive or capacitive trackpads, voice recognition hardware and software, optical scanners, optical pointers, digital image capture devices and associated interpretation software, and the like.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

The subject matter described herein can be embodied in systems, apparatus, methods, and/or articles depending on the desired configuration. The implementations set forth in the foregoing description do not represent all implementations consistent with the subject matter described herein. Instead, they are merely some examples consistent with aspects related to the described subject matter. Although a few variations have been described in detail above, other modifications or additions are possible. In particular, further features and/or variations can be provided in addition to those set forth herein. For example, the implementations described above can be directed to various combinations and subcombinations of the disclosed features and/or combinations and subcombinations of several further features disclosed above. In addition, the logic flow(s) depicted in the accompanying figures and/or described herein do not necessarily require the particular order shown, or sequential order, to achieve desirable results. Other implementations may be within the scope of the following claims.