System, Method and Apparatus for Electronic Patient Care
US-2015154364-A1 · Jun 4, 2015 · US
US12465684B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12465684-B2 |
| Application number | US-202318483579-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 10, 2023 |
| Priority date | Dec 21, 2011 |
| Publication date | Nov 11, 2025 |
| Grant date | Nov 11, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A pump for pumping fluid includes a tube platen, a plunger, a bias member, inlet and outlet valves, an actuator mechanism, a position sensor, and a processor. The plunger is configured for actuation toward and away from the infusion-tube when the tube platen is disposed opposite to the plunger. The tube platen can hold an intravenous infusion tube. The bias member is configured to urge the plunger toward the tube platen.
Opening claim text (preview).
What is claimed is: 1 . A system for pumping comprising: a plunger configured to move toward and away from a tube; a biasing member configured to provide a dynamically adjustable force urging the plunger toward the tube, the dynamically adjustable force varying based on operational conditions; an actuator configured to cause the plunger to move relative to the tube, the actuator being configured to mechanically disengage from the plunger; an inlet valve; an outlet valve; and a processor configured for: receiving a sensed position of a plunger relative to a tube; estimating a fluid flow within the tube based on the sensed position; and detecting an anomaly based on the sensed position of the plunger when at least one of the inlet valve and the outlet valve are in an occluding position and the actuator is mechanically disengaged from the tube while the biasing member urges the plunger toward the tube, wherein the anomaly is detected when a force applied to the plunger does not produce an expected displacement. 2 . The system of claim 1 further comprising a position sensor configured to sense a position of the plunger. 3 . The system of claim 1 wherein the detected anomaly is based in part on the sensed position when at least one of the inlet valve and the outlet valve is in an occluding position, and further configured to: close the inlet valve; close the outlet valve; disengage the actuator from the plunger; determine a first position of the plunger; open the outlet valve; engage the actuator with the plunger; determine a second position of the plunger. 4 . The system of claim 1 wherein said processor is configured for logging an infusion of fluid to generate an infusion log. 5 . The system of claim 4 further comprising a user-interface processor configured for receiving the infusion log. 6 . The system of claim 5 wherein said user-interface processor is configured for executing an infusion manager process to control an infusion of fluid. 7 . The system of claim 6 wherein said user-interface processor is configured to select a Drug Administration Library entry to: validate the infusion of fluid; and/or pass a dose mode, a dose limit, and/or a default value to a user interface display. 8 . The system of claim 7 wherein said processor is configured to provide error detection of flawed messages. 9 . The system of claim 5 wherein said processor is configured for: storing the infusion log in a database; communicating the infusion log; and/or interacting within said processor to communicate the infusion log. 10 . The system of claim 9 wherein the database is configured as a buffer to a plurality of logs including an infusion log prior to uploading into a device gateway server. 11 . The system of claim 9 wherein a communication between an intercommunication task and an intercommunication process is asynchronous. 12 . The system of claim 9 wherein said communicating is performed by a device gateway communication manager configured to: communicate over a wireless connection; manage communications with a device gateway server; poll a device gateway server for updates; upload the infusion log; and/or flag the infusion log within the database after uploading the infusion log. 13 . The system of claim 12 wherein the infusion log is an event. 14 . The system of claim 13 wherein the event is a status, a measurement, and/or a therapy history event. 15 . A method of pumping comprising: receiving a sensed position of a plunger relative to a tube, the plunger being biased toward the tube by a biasing member that provides a dynamically adjustable force based on operational conditions; disengaging an actuator from the plunger; estimating a fluid flow within the tube based on the sensed position; and detecting an anomaly based on the sensed position when at least one of an inlet valve and an outlet valve is in an occluding position and the actuator is mechanically disengaged from the tube while the biasing member urges the plunger toward the tube, wherein the anomaly is detected when a force applied to the plunger does not produce an expected displacement. 16 . The method of claim 15 further comprising controlling an infusion of fluid. 17 . The method of claim 15 further comprising: closing the inlet valve; closing the outlet valve; disengaging an actuator from the plunger; determining a first position of the plunger; opening the outlet valve; engaging the actuator with the plunger; determining a second position of the plunger; and estimating a volume of fluid flow based on the first position and the second position. 18 . The method of claim 15 further comprising logging an infusion of fluid to generate an infusion log. 19 . The method of claim 18 wherein the infusion log is an event. 20 . The method claim 19 wherein the event is a status, a measurement, and/or a therapy history event. 21 . The method of claim 18 further comprising receiving the infusion log. 22 . The method of claim 21 further comprising: storing the infusion log in a database; communicating the infusion log; and/or interacting with an intercommunication task to communicate the infusion log. 23 . The method of claim 22 wherein said interacting comprises an intercommunication process and is asynchronous. 24 . The method of claim 22 wherein said communicating comprises: communicating over a wireless connection; managing communications with a device gateway server; polling a device gateway server for updates; uploading the infusion log; and/or flagging the infusion log within the database after uploading the infusion log. 25 . The method of claim 22 wherein the database is configured as a buffer to a plurality of infusion logs including an infusion log prior to uploading into a device gateway server. 26 . The method of claim 15 further comprising: validating an infusion of fluid; and/or passing a dose mode, a dose limit, and/or a default value to a user interface display. 27 . The method of claim 26 further comprising providing error detection of flawed messages.
for remote operation · CPC title
delivered via infusion or injection · CPC title
Diaphragm type · CPC title
Docking stations · CPC title
Mounting brackets, arm supports for equipment · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.