This application relates generally to determining when an occluder valve operating on an intravenous (IV) administration line is failing or faulty.
As a result of the ongoing need for improved health care, there is a continuous effort with regard to administering intravenous fluid to patients. As is well known, medication dispensers and infusion devices are used for infusion of predetermined amounts of medication into the body of a patient. Various types of medication dispensers employing different techniques for a variety of applications are known to exist. Some existing infusion devices employ a finger type pump unit having fingers, often referred to in the industry as pumping fingers and occluder fingers (occluder valves), which are moved in predetermined sequence to fill and squeeze a tube to infuse predetermined amounts of medication continuously and cyclically into a patient. In many cases it is of critical importance to provide precisely controlled and consistent flow rates of intravenous fluid to patients. This need for more controlled IV flow rates is only partially fulfilled by the above-mentioned displacement pumps.
Infusion devices may monitor for some conditions that can negatively affect the accuracy and consistency of flow rates, such as by monitoring pressure sensors that indicate the occurrence of overpressures due to, for example, occlusions in the infusion line, which may cause interruptions in the infusion flow. Other conditions, such as a failing or faulty occluder valve, can also negatively affect flow rate accuracy and consistency. The delay between the detection of a condition negatively affecting flow accuracy and consistency and any subsequent alarm is relevant to patient safety.
The subject technology modifies occlusion valves with various sensors to detect occlusion conditions in an intravenous (IV) administration line. The subject technology provides a medication infusion device having a finger-type pump unit which is small in size and light in weight and durable in construction.
According to various implementations, an occluder detection system comprises at least one occluder element configured to move according to a cam motion to apply a periodic compression to a flexible infusion line when the flexible infusion line is placed between the occluder element and a plate assembly, wherein a section of the occluder element is configured to emit or modify an energy or magnetic field; a sensor configured to measure the energy or magnetic field being emitted or modified by the section of the occluder element; one or more processors configured to: cause the at least one occluder element to move according to the cam motion to move a fluid within the flexible infusion line by periodically compressing the flexible infusion line; measure the energy or magnetic field via the sensor; obtain a current cam state associated with the cam motion at a time corresponding to the measured energy or magnetic field; determine, based on the measured energy or magnetic field, and the current cam state, a state of the occluder element; and cause, responsive to determining the state of the occluder element, an adjustment to a hardware element of a device associated with the flexible infusion line. Other aspects include corresponding methods, apparatuses, and computer program products for implementation of the foregoing features.
According to various implementations, an infusion pump comprises a first occluder element and a second occluder element each configured to move according to a cam motion to apply a periodic compression to a flexible infusion line when the flexible infusion line is placed between the occluder element and a plate assembly, wherein a portion of the occluder element is configured to emit or modify an energy or magnetic field; a first sensor and a second sensor each configured to measure the energy or magnetic field being emitted or modified by a respective first or second occluder element; and one or more processors configured to: cause the first and second occluder elements to move in a predetermined sequence according to the cam motion to squeeze the flexible infusion line to infuse predetermined amounts of medication continuously and cyclically into a patient; measure, using the first and second sensors, the energy or magnetic field emitted or modified by each occluder element; obtain a current cam state associated with the cam motion at a time corresponding to the measured energy; determine, based on the current cam state and determining a position of the respective occluder element based on the measured energy or magnetic field corresponding to the respective occluder element, a current linear displacement of each of the first and second occluder elements with respect to a predetermined expected position of the occluder element corresponding to the current cam state; determining that the current linear displacement of at least one of the first and second occluder elements did not correspond to a threshold compression of the flexible infusion line; and activate an alarm indicating that a respective occluder valve is defective responsive to determining that the current linear displacement did not correspond to the threshold compression of the flexible infusion line. Other aspects include corresponding systems, methods, apparatuses, and computer program products for implementation of the foregoing features.
It is understood that other configurations of the subject technology will become readily apparent to those skilled in the art from the following detailed description, wherein various configurations of the subject technology are shown and described by way of illustration. As will be realized, the subject technology is capable of other and different configurations and its several details are capable of modification in various other respects, all without departing from the scope of the subject technology. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.
For a better understanding of the various described implementations, reference should be made to the Description of Implementations below, in conjunction with the following drawings. Like reference numerals refer to corresponding parts throughout the figures and description.
Reference will now be made to implementations, examples of which are illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide an understanding of the various described implementations. However, it will be apparent to one of ordinary skill in the art that the various described implementations may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the implementations.
Infusion devices, such as those that include large volume infusion pumps (LVPs), may use a linear peristaltic or similar type of mechanism that creates the pumping action by way of squeezing the IV tubing to generate the pressure that causes the IV medication to flow through the IV tubing and ultimately into the patient. The squeezing action can also be used as a mechanism to close off the flow. This is used in pumping mechanisms that operate in a cyclical fashion by operating in a cycle that includes a filling portion and a delivery portion. In such instances, the pumping mechanism uses valving that includes an intake (or fill) valve 112, and an outflow (or delivery) valve 114. These valves can be referred to as “occluder valves”. Proper operation of the pumping mechanism requires complete closure of these valves when they are not expected to be open. Incomplete closure will produce leakage, which can produce uncontrolled flow resulting in either, not enough medication, or too much medication being delivered to the patient. For this reason, it is desirable to verify that the occluder mechanism is operating as expected. Accordingly, the subject technology provides detection mechanisms for determining whether an upstream or downstream valve is faulty.
In order to verify that the valving mechanism is properly closing in an LVP pump, the degree of movement of the occluder has to extend past a certain point to ensure that the tubing is completely pinched (closed). If it is not, then there is a possibility of leaking and uncontrolled flow. The amount of occluder displacement is generally in the range of 15% to 20% of the tubing wall thickness. This ensures that the occluder will not lift under fluid pressure causing leakage. The force that is needed to be applied to the tubing to ensure that it is pinched, and closed, completely is therefore, important. In a system that generates the force using compression springs, the amount of force is dependent on the spring compression distance. By ensuring that the spring is compressed the correct amount, the occluder valve provides the required pinch force to the tubing.
With brief reference to
The pumping mechanism 110 comprises a cam assembly that acts upon the occluder elements 122, 124, and which is driven by an axle shaft (not shown). The axle shaft is driven by a motor and provides rotation to the cam assembly. The cam assembly may be formed and machined from a single piece of metal. The occluder elements 122, 124 may slidably move up and down and are subsequently displaced in a predetermined sequence, thereby squeezing a delivery tube placed between the occluder elements 122, 124 and dispensing a specified volume of fluid. According to various implementations each occluder valve may include a guide 126, 128 which at least partially constrains the occluder element therein. As shown in the depicted example, guides 126, 128 may include a slot in an upper portion of a housing, with a portion of the occluder element extending therethrough. As will be described further, guides 126, 128 may facilitate placement of an energy source or detection mechanism for determining a position and/or displacement of the respective occluder elements.
Each cam 132 may be elliptical in shape and may rotate on an axis off center of the ellipse.
If the occluder is obstructed such as by fluid leaking into the mechanism and jamming the occluder, then it will not be able to achieve the full range of motion from top dead center position (TDC) to bottom dead center (BDC). The detection of the displacement of the occluder can be accomplished in many ways. By using electronic sensors that measure displacement by optical means, electromagnetic, or ultrasonic are some examples.
According to various implementations the magnet 140 (or other similarly situated mechanism) may be placed on or embedded within an extension tab 142 extending from a top of the occluder element 130. As depicted in both
According to various implementations, a displacement sensing element 150 is connected to electronics that provide the necessary modulation and signal conditioning to provide an intelligible signal that can be used by the pump's software to determine the operating state of the occluder valve, and then make a decision as to whether or not to stop the pump and alarm notifying the user of an abnormal condition. In this regard, a sensor 150 is configured to measure an energy of the energy source being emitted or modified by an energy element of the occluder element 130.
In the depicted implementation, a section of the occluder element (e.g., an extension tab) is configured with a magnet to emit a magnetic field. The sensor 150 is externally fixed to an upper portion of a housing (e.g., a metal frame), as shown in both
The sensor 150 provides signals to one or more processors of a monitoring circuit, for example, associated with or within the infusion pump. The processor(s) causes the occluder element 130 to move according to the cam motion to move a fluid within the flexible infusion line by periodically compressing the flexible infusion line. The processor(s) measure an energy or magnetic field modified or emitted by the occluder element 130, here a magnetic field.
Concurrently with measuring the energy field, the processor(s) obtains a current cam state associated with the cam motion at a time corresponding to the measured energy. For example, one or more sensors (not shown) may be configured to monitor a rotational positioning of cam 132. In this manner, the processor(s) is configured to determine when the cam 132 is at a top dead center (TDC) position or a bottom dead center (BDC) position. The processor(s) may then determine, based on the measured energy and the current cam state, a state of the occluder element 130. The state of the occluder element 130 may be a linear displacement from an expected position or, more generally, whether the occluder element is misaligned or displaced more than a threshold displacement.
The movement of the magnet creates a variable magnetic field which is proportional to the distance of the magnet to the sensor 150. In this way, the sensor outputs a value that is calibrated to be a certain position. In some implementations, the sensor 150 includes a Hall effect sensor. In some implementation, a linear inductive encoder may be used. In operation, two positions which represent the extended and retracted locations of the occluder element 130. Values received or derived from sensor measurements are used by a software algorithm that compares the values at these positions to acceptable values. If the values are outside the acceptable value, then the system has the capability of alarming the user of a fault, stopping the pump, or not allowing the pump to begin an infusion. This prevents the infusion pump from being used, thus preventing a serious over-infusion.
Using an AI (artificial intelligence or machine learning) algorithm, the occluder position data can also be compared against previous measurements from the instrument or compared to the population of pumps in the field, to identify abnormal conditions such as wear on the occluder mechanism. This can allow it to be used as a predictive measure to identify instruments that should be serviced, or taken out of use, prior to a failure occurring.
According to various implementations, the pumping mechanism 110 may be calibrated, such that the state of the occluder element (e.g., its position and/or fault condition) is determined based on the measured energy (e.g., magnetic field or light pattern) and the current cam state and a calibration parameter. The calibration parameter may be, for example, an offset value used in a calculation of the occluder element displacement, or a value used in the machine learning algorithm.
Accordingly, the infusion pump may be calibrated by performing an operation on the line set when the line set is first installed. The line set may be loaded and the calibration process started by way of the user inputting the necessary start procedure using the pump's interface, as discussed with regard to
Additionally or in the alternative, the state of the calibration parameter may result from user input at an input device. For example, the user may input the type of line set used, and the processor(s) may perform a lookup in memory (local or at a server) to determine a calibration parameter corresponding to the line set. In some implementations, the infusion device or other monitoring system may detect the line set automatically when installed (e.g., by way of an RFID embedded in the line set). In such implementations, user input may involve confirming the line set type once detected.
The occluder position detection system has the capability to identify various conditions, including obstructed movement of the occluder element 130, the detection of non-conforming IV pump tubing, mechanical component failure that affects positioning of the occluder stroke relative to the platen, and whether an object is lodged in the area of the occluder element.
For example, if the occluder element 130 is obstructed by fluid leaking into the mechanism and jamming the occluder, then it will not be able to achieve the full range of motion from TDC to BDC. Additionally, a software algorithm may be incorporated to measure the time interval between the TDC and BDC positions. This may be compared to the expected time interval calculated from the programmed flow rate. If this is outside the expected range, then it can indicate that the occluder is obstructed from movement. If a non-conforming IV set with tubing wall thickness that is over or under the required tolerances is used, the occluder position sensor will be able to identify be if the occluder does not reach the expected BDC position. If any object other than the tubing is placed in the area of the occluder such as another segment of the IV tubing, a piece of surgical tape etc. it would prevent the occluder to reach the BDC position and also limiting its range of motion which would be detected by the sensor.
If the occluder element 130 is too high, for example with respect to the sensor 150, the occluder element may exhibit significant overtravel with respect to the cam 132, as depicted in
The foregoing detection mechanism provides the numerous advantages. For example, a means to detect the correct functioning of the occluder elements is provided in real-time. Fault conditions may be detected that could lead to uncontrolled flow causing inadvertent over or under infusion of medication to patient. The system can further potentially detect wear of the occlusion mechanism and identify instruments that may need repair.
When the light path is obstructed, the detector will output a binary “on” signal, when unobstructed the sensor will not detect light and output an “off” signal. These values are then used by the software to determine the state of the occluder during operation. The software will only check the sensor status at the positions when the occluder is either fully extended (closed), and fully retracted (open). The software will determine if the correct logic signal is provided by the sensor. If the logic signal is off, then this indicates that the occluder is not in the correct position, or that the sensor is malfunctioning. In both of these cases, the software can then alarm the user of the fault, stopping the pump or not allowing the pump to begin an infusion.
Various other photoelectric configurations may be used. For example,
In the depicted example, a processor (or processors) associated with an infusion device causes at least one occluder element (e.g., occluder element 130) associated with an infusion pump to move according to a cam motion to apply a periodic compression to a flexible infusion line when the flexible infusion line is placed between the occluder element and a plate assembly and to move a fluid within the flexible infusion line (62). As described previously, the occluder element may be configured to emit or modify an energy. For example, the occluder element may be a magnetic element embedded in a portion of the occluder element such as an extension tab 142.
The processor measures, using a sensor, an energy or magnetic field being emitted or modified by the section of the occluder element (63). For example, the sensor may be a magnetic sensor to detect a magnetic field. As examples, sensor may be a Hall effect sensor or a linear inductive encoder configured to measure a position of the magnetic object with respect to the sensor. The sensor may be configured to measure a magnetic flux emitted by the magnetic object. Additionally, or in the alternative, the sensor may be a photoelectric sensor configured to measure a position at least one occluder element based on detecting a diffusion characteristic of a light transmitted through a portion of the occluder element.
The processor obtains a current cam state associated with the cam motion at a time corresponding to the measured energy (64), and determines, based on the measured energy or magnetic field and the current cam state, a state of the occluder element (65). The state of the occluder element may be determined, for example, based on a magnitude and/or direction of a measured magnetic flux. Determining the state of the occluder element may include, for example, determining a linear displacement of the occluder element from a predetermined expected position of the occluder element corresponding to the current cam state.
The processor then (optionally) provides, for display on a display device (e.g., display device 54 or display screen of device 16 or 32 of
According to various implementations, the processor(s) may cause first and second occluder elements, such as shown in
Many of the above-described devices, systems and methods, may also be implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium), and may be executed automatically (e.g., without user intervention). When these instructions are executed by one or more processing unit(s) (e.g., one or more processors, cores of processors, or other processing units), they cause the processing unit(s) to perform the actions indicated in the instructions. Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard drives, EPROMs, etc. The computer readable media does not include carrier waves and electronic signals passing wirelessly or over wired connections.
The term “software” is meant to include, where appropriate, firmware residing in read-only memory or applications stored in magnetic storage, which can be read into memory for processing by a processor. Also, in some implementations, multiple software aspects of the subject disclosure can be implemented as sub-parts of a larger program while remaining distinct software aspects of the subject disclosure. In some implementations, multiple software aspects can also be implemented as separate programs. Finally, any combination of separate programs that together implement a software aspect described here is within the scope of the subject disclosure. In some implementations, the software programs, when installed to operate on one or more electronic systems, define one or more specific machine implementations that execute and perform the operations of the software programs.
A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
Each device 12 may be connected to an internal healthcare network 10 by a transmission channel 31. Transmission channel 31 is any wired or wireless transmission channel, for example an 802.11 wireless local area network (LAN). In some implementations, network 10 also includes computer systems located in various departments throughout a hospital. For example, network 10 of
Additionally, institutional patient care system 70 may incorporate a separate information system server 30. According to various implementations, server 30 and/or database 37 may incorporate, function as, or include a remote records system configured to store electronic medication administration records (eMAR) for patients admitted or cared for within the hospital organization. Although the information system server 30 is shown as a separate server, the functions and programming of the information system server 30 may be incorporated into another computer, if such is desired by engineers designing the institution's information system. Institutional patient care system 100 may further include one or multiple device terminals 32 for connecting and communicating with information system server 30. Device terminals 32 may include personal computers, personal data assistances, mobile devices such as laptops, tablet computers, augmented reality devices, or smartphones, configured with software for communications with information system server 30 via network 10.
Patient care device 12 comprises a system for providing patient care, such as for providing an infusion of medication to a patient. Patient care device 12 may include or incorporate an infusion pump, a physiological monitor (e.g., heart rate, blood pressure, ECG, EEG, pulse oximeter, and other patient monitors), therapy device, and other drug delivery device. In the depicted example, patient care device 12 comprises a control unit 14, also referred to as interface unit 14 or docking station, connected to one or more functional modules 16, 18, 20, 22. Interface unit 14 includes a central processing unit (CPU) 50 connected to a memory, for example, random access memory (RAM) 58, and one or more interface devices such as user interface device 54, a coded data input device 60, a network connection 52, and an auxiliary interface 62 for communicating with additional modules or devices. Interface unit 14 also, although not necessarily, includes a main non-volatile storage unit 56, such as a hard disk drive or non-volatile flash memory, for storing software and data and one or more internal buses 64 for interconnecting the aforementioned elements.
In various implementations, user interface device 54 is a touch screen for displaying information to a user and allowing a user to input information by touching defined areas of the screen. Additionally, or in the alternative, user interface device 54 could include any means for displaying and inputting information, such as a monitor, a printer, a keyboard, softkeys, a mouse, a track ball and/or a light pen. Data input device 60 may be a bar code reader capable of scanning and interpreting data printed in bar coded format. Additionally or in the alternative, data input device 60 can be any device for entering coded data into a computer, such as a device(s) for reading a magnetic strips, radio-frequency identification (RFID) devices whereby digital data encoded in RFID tags or smart labels (defined below) are captured by the reader 60 via radio waves, PCMCIA smart cards, radio frequency cards, memory sticks, CDs, DVDs, or any other analog or digital storage media. Other examples of data input device 60 include a voice activation or recognition device or a portable personal data assistant (PDA). Depending upon the types of interface devices used, user interface device 54 and data input device 60 may be the same device. Although data input device 60 is shown in
Network connection 52 may be a wired or wireless connection, such as by Ethernet, WiFi, BLUETOOTH, an integrated service digital network (ISDN) connection, a digital subscriber line (DSL) modem or a cable modem. Any direct or indirect network connection may be used, including, but not limited to a telephone modem, an MIB system, an RS232 interface, an auxiliary interface, an optical link, an infrared link, a radio frequency link, a microwave link or a WLANS connection or other wireless connection.
Functional modules 16, 18, 20, 22 are any devices for providing care to a patient or for monitoring patient condition. As shown in
Each functional module 16, 18, 20, 22 may communicate directly or indirectly with interface unit 14, with interface unit 14 providing overall monitoring and control of device 12. Functional modules 16, 18, 20, 22 may be connected physically and electronically in serial fashion to one or both ends of interface unit 14 as shown in
Each functional module 16, 18, 20, 22 may include module-specific components 76, a microprocessor 70, a volatile memory 72 and a nonvolatile memory 74 for storing information and performing the functions and/or operations described herein. It should be noted that while four functional modules are shown in
While each functional module may be capable of a least some level of independent operation, interface unit 14 monitors and controls overall operation of device 12. For example, as will be described in more detail below, interface unit 14 provides programming instructions to the functional modules 16, 18, 20, 22 and monitors the status of each module.
Patient care device 12 is capable of operating in several different modes, or personalities, with each personality defined by a configuration database. The configuration database may be a database 56 internal to patient care device, or an external database 37. A particular configuration database is selected based, at least in part, by patient-specific information such as patient location, age, physical characteristics, or medical characteristics. Medical characteristics include, but are not limited to, patient diagnosis, treatment prescription, medical history, medical records, patient care provider identification, physiological characteristics or psychological characteristics. As used herein, patient-specific information also includes care provider information (e.g., physician identification) or a patient care device's 10 location in the hospital or hospital computer network. Patient care information may be entered through interface device 52, 54, 60 or 62, and may originate from anywhere in network 10, such as, for example, from a pharmacy server, admissions server, laboratory server, and the like.
Medical devices incorporating aspects of the subject technology may be equipped with a Network Interface Module (NIM), allowing the medical device to participate as a node in a network. While for purposes of clarity the subject technology will be described as operating in an Ethernet network environment using the Internet Protocol (IP), it is understood that concepts of the subject technology are equally applicable in other network environments, and such environments are intended to be within the scope of the subject technology.
Data to and from the various data sources can be converted into network-compatible data with existing technology, and movement of the information between the medical device and network can be accomplished by a variety of means. For example, patient care device 12 and network 10 may communicate via automated interaction, manual interaction or a combination of both automated and manual interaction. Automated interaction may be continuous or intermittent and may occur through direct network connection 54 (as shown in
All direct communications with medical devices operating on a network in accordance with the subject technology may be performed through information system server 30, known as the remote data server (RDS). In accordance with aspects of the subject technology, network interface modules incorporated into medical devices such as, for example, infusion pumps or vital signs measurement devices, ignore all network traffic that does not originate from an authenticated RDS. The primary responsibilities of the RDS of the subject technology are to track the location and status of all networked medical devices, and maintain open communication.
With further reference to
Electronic system 600 may include various types of computer readable media and interfaces for various other types of computer readable media. In the depicted example, electronic system 600 includes a bus 608, processing unit(s) 612, a system memory 604, a read-only memory (ROM) 610, a permanent storage device 602, an input device interface 614, an output device interface 606, and one or more network interfaces 616. In some implementations, electronic system 600 may include or be integrated with other computing devices or circuitry for operation of the various components and processes previously described.
Bus 608 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of electronic system 600. For instance, bus 608 communicatively connects processing unit(s) 612 with ROM 610, system memory 604, and permanent storage device 602.
From these various memory units, processing unit(s) 612 retrieves instructions to execute and data to process in order to execute the processes of the subject disclosure. The processing unit(s) can be a single processor or a multi-core processor in different implementations.
ROM 610 stores static data and instructions that are needed by processing unit(s) 612 and other modules of the electronic system. Permanent storage device 602, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when electronic system 600 is off. Some implementations of the subject disclosure use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive) as permanent storage device 602.
Other implementations use a removable storage device (such as a floppy disk, flash drive, and its corresponding disk drive) as permanent storage device 602. Like permanent storage device 602, system memory 604 is a read-and-write memory device. However, unlike storage device 602, system memory 604 is a volatile read-and-write memory, such a random access memory. System memory 604 stores some of the instructions and data that the processor needs at runtime. In some implementations, the processes of the subject disclosure are stored in system memory 604, permanent storage device 602, and/or ROM 610. From these various memory units, processing unit(s) 612 retrieves instructions to execute and data to process in order to execute the processes of some implementations.
Bus 608 also connects to input and output device interfaces 614 and 606. Input device interface 614 enables the user to communicate information and select commands to the electronic system. Input devices used with input device interface 614 include, e.g., alphanumeric keyboards and pointing devices (also called “cursor control devices”). Output device interfaces 606 enables, e.g., the display of images generated by the electronic system 600. Output devices used with output device interface 606 include, e.g., printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD). Some implementations include devices such as a touchscreen that functions as both input and output devices.
Also, as shown in
These functions described above can be implemented in computer software, firmware or hardware. The techniques can be implemented using one or more computer program products. Programmable processors and computers can be included in or packaged as mobile devices. The processes and logic flows can be performed by one or more programmable processors and by one or more programmable logic circuitry. General and special purpose computing devices and storage devices can be interconnected through communication networks.
Some implementations include electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer-readable medium (also referred to as computer-readable storage media, machine-readable media, or machine-readable storage media). Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and/or solid state hard drives, read-only and recordable Blu-Ray® discs, ultra density optical discs, any other optical or magnetic media, and floppy disks. The computer-readable media can store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.
While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some implementations are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some implementations, such integrated circuits execute instructions that are stored on the circuit itself.
As used in this specification and any claims of this application, the terms “computer”, “server”, “processor”, and “memory” all refer to electronic or other technological devices. These terms exclude people or groups of people. For the purposes of the specification, the terms display or displaying means displaying on an electronic device. As used in this specification and any claims of this application, the terms “computer readable medium” and “computer readable media” are entirely restricted to tangible, physical objects that store information in a form that is readable by a computer. These terms exclude any wireless signals, wired download signals, and any other ephemeral signals.
To provide for interaction with a user, implementations of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; e.g., feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; e.g., by sending web pages to a web browser on a user's client device in response to requests received from the web browser.
Implementations of the subject matter described in this specification can be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
The computing system can include clients and servers. A client and server are generally remote from each other and may 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. In some implementations, a server transmits data (e.g., an HTML, page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server.
Those of skill in the art would appreciate that the various illustrative blocks, modules, elements, components, methods, and algorithms described herein may be implemented as electronic hardware, computer software, or combinations of both. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality may be implemented in varying ways for each particular application. Various components and blocks may be arranged differently (e.g., arranged in a different order, or partitioned in a different way) all without departing from the scope of the subject technology.
It is understood that the specific order or hierarchy of steps in the processes disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Some of the steps may be performed simultaneously. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. The previous description provides various examples of the subject technology, and the subject technology is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. Pronouns in the masculine (e.g., his) include the feminine and neuter gender (e.g., her and its) and vice versa. Headings and subheadings, if any, are used for convenience only and do not limit the invention described herein.
The term website, as used herein, may include any aspect of a website, including one or more web pages, one or more servers used to host or store web related content, etc. Accordingly, the term website may be used interchangeably with the terms web page and server. The predicate words “configured to”, “operable to”, and “programmed to” do not imply any particular tangible or intangible modification of a subject, but, rather, are intended to be used interchangeably. For example, a processor configured to monitor and control an operation or a component may also mean the processor being programmed to monitor and control the operation or the processor being operable to monitor and control the operation. Likewise, a processor configured to execute code can be construed as a processor programmed to execute code or operable to execute code.
The term automatic, as used herein, may include performance by a computer or machine without user intervention; for example, by instructions responsive to a predicate action by the computer or machine or other initiation mechanism. The word “example” is used herein to mean “serving as an example or illustration.” Any aspect or design described herein as “example” is not necessarily to be construed as preferred or advantageous over other aspects or designs.
A phrase such as an “aspect” does not imply that such aspect is essential to the subject technology or that such aspect applies to all configurations of the subject technology. A disclosure relating to an aspect may apply to all configurations, or one or more configurations. An aspect may provide one or more examples. A phrase such as an aspect may refer to one or more aspects and vice versa. A phrase such as an “embodiment” does not imply that such embodiment is essential to the subject technology or that such embodiment applies to all configurations of the subject technology. A disclosure relating to an embodiment may apply to all implementations, or one or more implementations. An embodiment may provide one or more examples. A phrase such as an “embodiment” may refer to one or more embodiments and vice versa. A phrase such as a “configuration” does not imply that such configuration is essential to the subject technology or that such configuration applies to all configurations of the subject technology. A disclosure relating to a configuration may apply to all configurations, or one or more configurations. A configuration may provide one or more examples. A phrase such as a “configuration” may refer to one or more configurations and vice versa.
This application claims the benefit of U.S. Provisional Application No. 63/212,441, entitled “SYSTEM AND METHOD FOR DETECTING A FAULTY OCCLUDER VALVE,” filed Jun. 18, 2021, the entirety of which is incorporated herein by reference.
Number | Date | Country | |
---|---|---|---|
63212441 | Jun 2021 | US |