Medication order processing and reconciliation

US11901057B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11901057-B2
Application numberUS-202117346149-A
CountryUS
Kind codeB2
Filing dateJun 11, 2021
Priority dateDec 30, 2005
Publication dateFeb 13, 2024
Grant dateFeb 13, 2024

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A system and method for managing medication orders, including changes to those orders, is described. A server receives medication orders from a pharmacy and communicates those orders to an infusion pump. The infusion pump communicates status messages to the server and the server compares the status messages to the medication orders to determine if the there were any changes to the order, or if a medication was administered absent a medication order. The server assigns a new order identification number to the status message if needed. The system may also reconcile original medication orders with information associated with a new order identification number and stores the information in the eMAR of a patient.

First claim

Opening claim text (preview).

The invention claimed is: 1. A system comprising: one or more processors; and a memory including executable instructions that, when executed by the one or more processors, cause the one or more processors to: receive a first medication identification entered into a user interface of an infusion device associated with a patient; verify that a first medication associated with the first medication identification is associated with the patient; automatically program, responsive to the verifying, operation of the infusion device to administer the first medication to the patient by way of automatic download of configuration parameters associated with the first medication; receive, after the programming via the user interface, a second medication identification associated with a second medication provided by the infusion device; determine that the second medication is not associated with the patient; responsive to determining that the second medication is not associated with the patient: generate a new order identifier for the second medication; and update an electronic record associated with the patient to reflect the new order identifier for the second medication identification; receive, while the infusion device is administering the second medication to the patient, delivery status messages associated with the administering of the second medication; and update the electronic record with information from the delivery status messages. 2. The system of claim 1 , wherein the one or more processors are further caused to: receive, via the infusion device, an indication that a delivery of the first medication has started, the second medication comprising the second medication identification; assign, responsive to the first medication being started, an order identifier to the delivery of the first medication, wherein the order identifier is provided in the delivery status messages as the second medication identification. 3. The system of claim 1 , wherein the second medication identification comprises an operational parameter associated with a delivery of the second medication by the infusion device, wherein determining that the second medication is not associated with the patient comprises: determining that the operational parameter does not satisfy a rule or guideline for the first medication. 4. The system of claim 1 , wherein the one or more processors are further caused to: receive a first order identifier for the first medication from the infusion device, wherein verifying that the first medication is associated with the patient comprises correlating the first order identifier with a pharmacy order identifier in the electronic record; and responsive to determining that the second medication is not associated with the patient: provide the new order identifier to the infusion device for use in status messages, wherein the new order identifier is received in the delivery status messages after the new order identifier is provided to the infusion device. 5. The system of claim 4 , wherein the new order identifier is assigned based on determining that data fields of updated infusion information received in a delivery status message match data fields for a different order than a current order for the patient based on a pattern matching algorithm. 6. The system of claim 1 , wherein determining that the second medication is not associated with the patient comprises: determining that a order identifier received in a status message from the infusion device is not associated with a pharmacy order identifier stored in the electronic record. 7. The system of claim 1 , wherein the one or more processors are further caused to: receiving one or more operational parameters associated with the first medication from the infusion device; verifying that the operational parameters are appropriate for the first medication; when the one or more operational parameters are verified, providing instructions to the infusion device to proceed with an infusion of the first medication, wherein the infusion device is otherwise electronically prevented from performing the infusion until the instructions are received by the infusion device. 8. The system of claim 7 , wherein verifying that the operational parameters are appropriate for the first medication comprise verifying that the operational parameters are appropriate for the patient. 9. The system of claim 1 , wherein the delivery status messages are received periodically at predetermined intervals. 10. A machine-implemented method comprising: receiving a first medication identification entered into a user interface of an infusion device associated with a patient; verifying that a first medication associated with the first medication identification is associated with the patient; automatically program, responsive to the verifying, operation of the infusion device to administer the first medication to the patient by way of automatic download of configuration parameters associated with the first medication; receiving, after the programming via the user interface, a second medication identification associated with a second medication provided by the infusion device; determining that the second medication is not associated with the patient; responsive to determining that the second medication is not associated with the patient: generate a new order identifier for the second medication; and updating an electronic record associated with the patient to reflect the new order identifier for the second medication identification; receiving, while the infusion device is administering the second medication to the patient, delivery status messages associated with the administering of the second medication; and updating the electronic record with information from the delivery status messages. 11. The machine-implemented method of claim 10 , further comprising: receive, via the infusion device, an indication that a delivery of the first medication has started, the second medication comprising the second medication identification; assign, responsive to the first medication being started, a first order identifier to the delivery of the first medication, wherein the first order identifier is provided in the delivery status messages as the second medication identification. 12. The machine-implemented method of claim 10 , wherein the second medication identification comprises an operational parameter associated with a delivery of the second medication by the infusion device, wherein determining that the second medication is not associated with the patient comprises: determining that the operational parameter does not satisfy a rule or guideline for the first medication. 13. The machine-implemented method of claim 10 , further comprising: receiving a first order identifier for the first medication from the infusion device, wherein verifying that the first medication is associated with the patient comprises correlating the first order identifier with a pharmacy order identifier in the electronic record; and responsive to determining that the second medication is not associated with the patient: wherein the new order identifier is received in the delivery status messages after the new order identifier is provided to the infusion device. 14. The machine-implemented method of claim 10 , wherein determining that the second medication is not associated with the patient comprises: determining that a first order identifier received in a status message from the infusion device is not associated with a pharmacy order identifier stored in the electronic record. 15. The machi

Assignees

Inventors

Classifications

  • G16H20/10Primary

    relating to drugs or medications, e.g. for ensuring correct administration to patients · CPC title

  • for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms · CPC title

  • G16H40/67Primary

    for remote operation · CPC title

  • relating to drugs, e.g. their side effects or intended usage · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11901057B2 cover?
A system and method for managing medication orders, including changes to those orders, is described. A server receives medication orders from a pharmacy and communicates those orders to an infusion pump. The infusion pump communicates status messages to the server and the server compares the status messages to the medication orders to determine if the there were any changes to the order, or if …
Who is the assignee on this patent?
Carefusion 303 Inc
What technology area does this patent fall under?
Primary CPC classification G16H20/10. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Feb 13 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).