Classifications

• • G—PHYSICS
  • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
  • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
  • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
  • G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
  • G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders
• • G—PHYSICS
  • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
  • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
  • G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
  • G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
  • G16H20/13—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered from dispensers

Definitions

• the present disclosure relates to systems and methods for managing the storage and distribution of pharmaceuticals and medical supplies in a healthcare facility.
• medication management systems may be classified as centralized medication management systems or decentralized medication management systems.
• a healthcare professional e.g., a nurse
• medications may be provided from the central pharmacy directly to a healthcare professional (e.g., a nurse) that will be administering the medications to respective patients.
• multiple medication dispensing sites are located remotely from a centralized distribution location, such as a facility's pharmacy.
• the remote dispensing sites such as a nurses' station in a hospital ward, serve as base stations from which healthcare professionals can readily access medications or other medical supplies to be administered to the patients under their care.
• a decentralized medication management system may implement a decentralized medication dispensing system (MDS).
• An MDS can comprise a cabinet having a plurality of storage compartments, such as drawers, shelves, or bins, for example.
• the storage compartments are stocked with individual medications and/or medication doses or other medical supplies by the pharmacy.
• the contents of the base stations are thoroughly inventoried and the distribution of medications and medical supplies is carefully controlled.
• Access to the MDS (and to the individual storage compartments in the MDS) is limited and can be gained only by healthcare professionals with the appropriate credentials.
• a user interface controls access to and records the inventory, and distribution of the medications and medical supplies from the MDS can be computer controlled.
• the MDS may correspond to an automated dispensing machine (ADM) that stores medications in secure transportable compartments.
• ADM automated dispensing machine
• the compartments may be loaded (i.e., stocked with medications) in the pharmacy and then transported to the ADM.
• a nurse removes medications from the compartment at the ADM and transports the medications (e.g., in a pocket) to the patient and administers the medication.
• Systems and methods according to the principles of the present disclosure relate to tracking medications in a healthcare facility from the central pharmacy to the patient. For example, after medications are removed from a medication base station (e.g., an ADM) and transferred to and/or stored in a transport apparatus (e.g., a patient specific drawer, portable container, bin, compartment and/or mobile point-of-care (POC) workstation) and/or are otherwise under the control of a healthcare professional, and prior to the medications being administered to the patient, inventory data, including the in- stock quantities and locations of the medications can be tracked and/or monitored and recorded by a medication system.
• a medication base station e.g., an ADM
• a transport apparatus e.g., a patient specific drawer, portable container, bin, compartment and/or mobile point-of-care (POC) workstation
• POC mobile point-of-care
• a central inventory database storing comprehensive inventory data, for the stock of medications throughout the healthcare facility, is not updated to reflect any changes to the in-stock quantities of medications in inventory until the medication system communicates to the central inventory database that the medication has been administered to the patient or otherwise disposed of by the healthcare professional.
• the medication system includes a control module that determines when a medication is removed from a central pharmacy and/or a medication base station for administration to a patient, such as by a healthcare professional according to a healthcare facility's medication management system protocols.
• a control module determines when a medication is removed from a central pharmacy and/or a medication base station for administration to a patient, such as by a healthcare professional according to a healthcare facility's medication management system protocols.
• the medication is transferred to and/or stored in a transport apparatus under the control of the healthcare professional for securely transporting medications to a patient care area (e.g., the patient's bedside) and administering the medications to the patient as prescribed.
• the transport apparatus can include, for example, a patient specific drawer, portable container, or mobile POC workstation, and/or are otherwise under the control of a healthcare professional.
• a remote, patient-specific medication database separate from the central inventory database associated with the healthcare facility, stores or has access to inventory data for the medications in the healthcare facility, including, for example, the quantities of the medications located in the central pharmacy and/or in the medication base station.
• the local medication inventory database records and/or stores inventory data including the quantities and locations of the medications in the transport apparatus and not yet administered to a patient.
• the control module can track and/or monitor when medications are removed from the central pharmacy and/or the medication base station and placed in the transport apparatus and update the inventory data in the remote medication database accordingly, including the in-stock quantities of the medications in the transport apparatus.
• the control module can also track and/or monitor when medications are administered by the healthcare professional to the patient and update the inventory data in the remote medication database accordingly.
• the control module can then update the inventory data in the central inventory database based on the updated inventory data of the remote medication database of the medication system.
• FIG. 1 is an example ADM
• FIG. 2 is an example mobile POC workstation
• FIG. 3 is an example medication management system including a medication system according to the principles of the present disclosure
• FIG. 4 is an example medication system according to the principles of the present disclosure
• FIG. 5 illustrates example information stored by a remote medication database according to the principles of the present disclosure.
• FIG. 6 illustrates and example medication method according to the principles of the present disclosure.
• inventory data for the medications maintained within a healthcare facility may be stored in a medication inventory database.
• Inventory data can include information about the in-stock quantities and storage locations of the stock of medications on-hand in the healthcare facility.
• the inventory data corresponds to medications stored in a central pharmacy and, in a decentralized medication management system, medications stored in medication base stations (e.g., ADMs) distributed throughout the healthcare facility.
• the central inventory database may store inventory data including information about, inter alia, the stock on- hand of unit dose packages of medications and their locations in the facility.
• the inventory data can be indexed and/or tallied by medication type and/or location (e.g., whether the medication is in the central pharmacy or in a particular medication base station).
• the medication management system generally updates the inventory data for the medications when a healthcare professional (e.g., a nurse) removes a unit (e.g., a dose) of the medication from any of the medication base stations for administering the medication to a patient according to facility protocols. For example, the total stock for the medication may be reduced by the number of units of the medication that are removed from the medication base station. In other words, the medication management system may consider that the medication is removed from inventory even before the medication has been administered to a patient, or otherwise disposed of by the healthcare professional (e.g., "wasted").
• the central inventory database generally may not track and/or monitor the inventory data for medications that are in transit between a medication base station and a patient care area.
• Systems and methods according to the principles of the present disclosure relate to tracking and/or monitoring the medications in a healthcare facility from the central pharmacy all the way to the patient (e.g., the patient bedside or other patient care area). For example, when a medication is removed from a medication base station and placed in a transport apparatus, the in-stock quantity and location of the medication can be tracked and/or monitored (e.g., at predefined intervals or in real-time) through the administering of the medication to the patient.
• the systems and methods are described herein with respect to decentralized medication management systems, the principles of the present disclosure may be implemented in centralized medication management systems and/or hybrid medication management systems, as well.
• an update to the inventory data of the central inventory database may not be made in response to the healthcare professional removing a medication from the pharmacy or medication base station. Instead, the corresponding inventory data reflected in the central inventory database, including the stock on-hand, may not be updated until the medication is actually administered to the patient. For example, a separate medication system may continue to monitor the quantities and locations of the medication and generate and/or store that inventory data in a remote, patient-specific medication database.
• the inventory data may include, but is not limited to, information about the identity of the healthcare professional that removed the medication from the medication base station, the identity of the transport mechanism (e.g., a POC workstation) to which the medication was transferred, a location within the healthcare facility of the medication (e.g., where it is and/or where it is being transported), etc.
• the medication system may be in continuous, conditional, and/or periodic communication with the medication inventory database.
• the medication system may record inventory data reflecting that the medication was removed from the medication base station and transferred to and/or stored in a transport apparatus for subsequent administration to a patient without also updating the total quantity inventory data in the central inventory database.
• the inventory data in the central inventory database may reflect the medication withdrawn from the medication base station that is in transit for administration to a patient as still included within the stock on-hand in the medical base station.
• the inventory data of central inventory database may still include the withdrawn medication as part of the stock on-hand in the healthcare facility, while also indicating that the medication was removed from the medication base station.
• the medication system may subsequently inform the central inventory database (and/or the medication base station) when the medication is administered or otherwise disposed of (i.e., "wasted") by the healthcare professional.
• the central inventory database may then update its inventory data, including the stock quantities of the medication throughout the facility and/or the status of the medication (e.g., administered to a patient or wasted).
• the medication systems and methods track and/or monitor, separately from and supplemental to a central inventory database, the stock quantities, locations, and statuses of medications, and particularly medications removed from medication base stations and transferred to transport apparatus for subsequent administering to patients. Accordingly, current information is maintained about medications removed from medication base stations but not yet administered to respective patients.
• FIGS. 1 -3 show an example medication base station 100 and mobile POC workstation 200, respectively.
• FIG. 3 shows an example medication system 300 according to the principles of the present disclosure operating within a medication management system 304. While the medication management system 304 is described as a decentralized medication management system, the medication system 300 may also be implemented in a centralized medication management system or hybrid medication management system. Accordingly, as described, the example medication management system 304 includes the medication base station 100 and the mobile workstation 200.
• medications are provided from a central pharmacy 308 to one or more medication base stations 100.
• a central inventory database 312 stores inventory data about the medications, such as stock quantities of each medication available in the healthcare facility, locations of the medications (e.g., stock quantities of each medication in the central pharmacy 308 and/or in respective medication base stations 100, etc.).
• the healthcare professional accesses either the mobile workstation 200 or the medication base station 100 according to facility protocols (e.g., by utilizing a user access control module 316 on one of the workstation 200 or base station 100).
• the healthcare professional obtains information related to one or more medications prescribed for a particular patient.
• the information about patient specific medication is placed in a queue that can be accessed by the control module 316, as appropriate.
• the base station 100 and the workstation 200 may negotiate a communication link. After the communication link is secured, the base station 100 receives or reads the information in the queue containing the information about patient-specific medication and prescription information for a given patient. The base station 100 then enables access by the healthcare professional to respective storage locations (e.g., drawers 320) containing the particular medications for that patient. At the same time the mobile workstation 200 enables access by the healthcare professional to the patient specific drawer 324 for that patient on the mobile workstation 200.
• respective storage locations e.g., drawers 320
• the healthcare professional then retrieves the medications from the drawers 320 of the base station 100 and may record the retrieval activity according to facility protocols.
• the healthcare professional then places those medications in the patient-specific drawer 324 on the mobile workstation 200 and may record that activity according to facility protocols. These steps are repeated for each of the medications for the patient that are retrieved from the base station 100 and placed in the patient specific drawer 324 on the mobile workstation 200. Then the steps may also be repeated for any number of patients under the care of the healthcare professional.
• the healthcare professional can thereafter administer the medications to the patient at the patient's bedside 328.
• the healthcare professional transports the mobile workstation 200 to the patient.
• the healthcare professional can access the mobile workstation 200 according to facility protocols utilizing the control module 316 on the workstation 200.
• the healthcare professional selects the patient for administration of medications.
• the control module 316 then enables access by the healthcare professional to the patient-specific drawer 324 containing the medications for that patient.
• the healthcare professional then removes the medications from the patient-specific drawer 324 and administers the medications to the patient according to facility protocols (e.g., according to the well-known "five rights" protocol). This may include using the control module 316 to record that the medications have been administered.
• the healthcare professional can then proceed to successive patients whose medications are contained in the mobile workstation 200, if any.
• Either or both of the medication base station 100 and the mobile workstation 200 may be configured to communicate with peripheral devices, such as bar code readers, PDAs, biometric security devices (e.g., a fingerprint scanner), scanners, card readers, keyboards, RFID systems, and the like.
• peripheral devices such as bar code readers, PDAs, biometric security devices (e.g., a fingerprint scanner), scanners, card readers, keyboards, RFID systems, and the like.
• the medication base station 100 and/or the mobile workstation 200 (e.g., via respective control modules 316) may implement the operating protocols of the healthcare facility for managing the distribution of medications from a pharmacy to a patient.
• the central inventory database 312 stores, for example, the inventory data including stock quantities for medications in the central pharmacy 308 and/or in the respective medication base stations 100
• the medication system 300 separately monitors, tracks, generates and/or stores inventory data about medications removed from the medication base station 100 and transferred to and/or stored in the mobile workstation 200 (or another transport apparatus under the control of a healthcare professional).
• the stock quantities of the medications in the healthcare facility that are maintained by the central inventory database 312 may typically be updated (e.g., diminished to reflect spent inventory) when the healthcare provider removes the medications from the medication base station 100.
• the stock quantities of the medications are also maintained in the inventory data of a remote, patient-specific medication database 408 (shown in FIG. 4).
• the inventory data of the remote medication database 408 are not diminished merely in response to the medication being removed from the medication base station 100. Instead, the remote medication database 408 continues to reflect thatstock associated with the corresponding medication base station 100 still remains, and therefore is included within a total stock quantity of the facility, even while the central inventory database 312 may reflect a different (diminished) stock quantity.
• the inventory data for the medications located in the mobile workstation 200 may also associate the medications with a particular healthcare provider (e.g., the healthcare provider that removed the medication from the medication base station 100), a particular patient, and/or a location of the mobile workstation 200.
• a particular healthcare provider e.g., the healthcare provider that removed the medication from the medication base station 100
• a particular patient e.g., a particular patient
• a location of the mobile workstation 200 e.g., the location of the mobile workstation 200 may be determined based on a predetermined portion of the healthcare facility assigned to the mobile workstation 200, by RFID or another real time location system (RTLS), WLAN communication, etc.
• RTLS real time location system
• the medication system 300 is in communication with one or more of the central inventory database 312, the medication base station 100, and/or the mobile workstation 200 to maintain and selectively update the stock quantities of the medications in the healthcare facility recorded in the central inventory database 312.
• the medication system 300 may inform the central inventory database 312 to update the inventory data, including the stock quantities of a medication, only after receiving confirmation from a healthcare professional that the medication was administered to the patient or otherwise disposed (i.e., "wasted").
• the central inventory database 312 may then update the stock quantities and/or status of the medication.
• the medication system 300 may be a separate device or module (e.g., implemented within a handheld device), or may be implemented within the medication base station 100 and/or the mobile workstation 200 (e.g., within respective control modules 216).
• a schematic representation of an example medication system 400 includes a control module 404, a remote, patient-specific medication database 408, communication interfaces 412 and 416, a user interface 420 (e.g., a graphical user interface), and an optional tracking module 424.
• the control module 404 controls and coordinates communication and processing of information between the remote medication database 408, the communication interfaces 412 and 416, the user interface 420, and the tracking module 424.
• control module 404 receives information about various medications removed from medication base stations 100 and transferred and/or stored in mobile workstations 200 via the communication interface 416 and/or the user interface 420, receives information about locations of a mobile workstation 200, medications removed from medication base stations 100, healthcare professionals, and/or various devices implemented the medication system 400 from the tracking module 424, and stores the information to and retrieves the information from the remote medication database 408.
• the control module 404 also provides information to be communicated via the communication interfaces 412 and 416 and the user interface 420.
• the user interface 420 allows a user (e.g., a healthcare professional) to interact with the medication system 400 and may include, for example only, a display(e.g., for a graphical user interface), user input controls, etc.
• a user e.g., a healthcare professional
• the user interface 420 may correspond to a user interface of the control modules 316.
• the healthcare professional may input information according to facility protocols, such as, for example, identity authentication and/or security credentials, medication removed from the medication base station 100, medication administered to respective patients, etc.
• the communication interface 412 exchanges information with the central inventory database 412, and the communication interface 416 exchanges information with the medication base station 100 and/or the mobile workstation 200.
• the communication interfaces 412 and 416 may communicate using WiFi or other WLAN signals, Bluetooth, various wired communication protocols, or any other suitable long or short range communication protocols.
• the tracking module 424 may implement RFID or another RTLS to determine a location of a device implementing the medication system 400.
• the location of the device (which may be associated with a particular medication removed from the medication base station 100) may be recorded in the inventory data generated and/or stored in the remote medication database, communicated to the central inventory database 312 via the communication interface 412, and/or communicated to the medication base station 100 and/or the mobile workstation 200 via the communication interface 416.
• the device implementing the medication system 400 corresponds to the mobile workstation 200.
• the control module 404 may receive information related to removal of a medication from the medication base station 100 (and, in some implementations, therefore stored in the mobile workstation 200). For example, the control module 404 may learn that the medication is removed from the medication base station 100 via automatic communication transmitted from the medication base station 100 (via the communication interface 416) that can be selectively triggered by the a drawer 320 being opened, a medication being removed from the drawer 320, a healthcare professional inputting information (via user interface 420, one of the control modules 316, etc.) indicating that the medication was removed from the medication base station 100 or that the medication was placed in a patient specific drawer 324, the patient specific drawer being opened and/or the medication being placed therein, etc. It can be appreciated that the above are only several examples describing how the control module 404 may determine when a medication is removed from the medication base station 100 and that other implementations are anticipated.
• the control module 404 records information about the medication in the remote medication database 408.
• the remote medication database 408 may be implemented using memory located on a handheld device including the medication system 400.
• the remote medication database 408 may store information about stock quantities of medications in the healthcare facility consistent with the stock quantities stored in the central inventory database 312, and/or stock quantities of the medications in respective medication base stations 100.
• the remote medication database 408 may store further information about medication removed from the pharmacy and/or the base station 100 and placed in the mobile workstation 200. This further information may indicate various stock quantities (and locations) of medications that still reside in the healthcare facility, but not in the pharmacy 308 or a base station 100.
• the remote medication database 408 records further information indicating an amount of a medication that has been removed from respective base stations 100 and has not yet been administered to a patient or otherwise disposed. Accordingly, the further information indicates an amount (and a location) of the medication that is located in various mobile workstations 200, that is being carried by a healthcare professional, etc.
• the central inventory database 312 may store information about the stock quantities of the medication, but may not reflect the amount of the medication still in the healthcare facility but not yet administered to a patient. For example, in a typical medication management system the central inventory database may reduce the stock quantities of the medication when the medication is removed from the base station 100 even though the medication has not been administered or otherwise disposed (e.g., is in a mobile workstation 200). Conversely, according to the principles of the present disclosure, the central inventory database 312 maintains (i.e., does not reduce) the stock quantities of the medication upon removal of the medication from the base station 100.
• the medication system 400 stores, in the remote medication database 408, information indicating that the stock quantities of the medication in the healthcare facility is the same, but some portion of the medication is now in transport between a respective base station 100 and a patient's bedside 328. Accordingly, the remote medication database 408, and consequently the central inventory database 312, has more robust and accurate information about the total inventories of various medications within the healthcare facility.
• the remote medication database 408 can be updated, accordingly, to reflect the actual reduction in the stock quantities of the medication in the healthcare facility (i.e., to reflect an actual inventory changing event). For example, the stock quantities of the medication, as recorded in the inventory data of the remote medication database 408, is reduced by an amount of the medication administered. A corresponding stock quantity of the medication in the mobile workstation 200 is also reduced.
• the remote medication database 408 may be updated according to user input at the user interface 420, automatically in response to a predetermined protocol being followed (e.g., bar codes associated with the patient, medication, healthcare professional, etc. being scanned as part of a medication administration protocol), and/or another suitable condition.
• the medication system 400 may then update the central inventory database 312 (via the communication interface 412) to adjust the stock quantities of the medication in the healthcare facility.
• the medication system 400 may update the central inventory database 312 automatically upon confirmation that the medication was administered or disposed of, on a periodic (e.g., real time) basis, and/or in response to some other condition (e.g., in response to a prompt from a healthcare professional at the base station 100 and/or the mobile workstation 200).
• the medication base station 100, the mobile workstation 200, and/or another storage or transport item may include a compartment (e.g., the drawer 324, a removable module or cassette, etc.) movable between an open configuration and a closed configuration. Contents (e.g., medication and/or other items) may be transferred to and from the compartment in the open configuration. Conversely, the contents of the compartment are not accessible in the closed configuration.
• a compartment e.g., the drawer 324, a removable module or cassette, etc.
• Contents e.g., medication and/or other items
• the contents of the compartment are not accessible in the closed configuration.
• the control module 404 may communicate with the compartment (e.g., electronically, wirelessly, etc.).
• the control module may receive an association signal that identifies the patient and store (e.g., a patient-specific database within the remote medication database 408 and/or the medication inventory database 312), based on the association signal, an association between the patient and the compartment.
• the association signal may be generated upon access to the medication base station 100, the medication system 300, etc. by a healthcare professional.
• the control module 404 may then receive a load signal identifying the medication prescribed to the patient and, upon verification that the medication is indeed prescribed to the patient associated with the compartment, (e.g., via the patient-specific database), cause the compartment to move to the open configuration to allow the healthcare professional to load the medication.
• the control module 404 stores (e.g., in the patient-specific database) information indicating that the prescribed medication is now stored in the compartment.
• the control module 404 may also inform the medication inventory database 312 that the medication is stored within the compartment in the medication management system 304.
• the compartment may then be transitioned to the closed configuration after the medication is placed therein.
• the control module 404 may receive a dispense signal (prompted by the healthcare professional attempting to access the compartment to administer the medication to the patient).
• the control module 404 changes the compartment to the open configuration in response to the dispense signal.
• the healthcare professional can then access the compartment to remove the medication and administer the medication to the patient.
• the healthcare professional may provide some indication that the medication was administered to the patient (e.g., via the user interface 420), causing an administration signal to be provided to the control module 404.
• the control module 404 can then update the patient-specific database (and/or the medication inventory database) accordingly.
• example information 500 stored by the remote medication database 408 includes a medication type 504, a total stock quantity 508 of the medication in the healthcare facility, an amount 512 of the of the medication in the pharmacy, amounts 516 and 520 of the medication in respective base stations (1 and 2), and respective amounts 524, 528, and 532 of the medication in respective mobile workstations (WS 1 , 2, and 3).
• the total stock quantity 508 corresponds to a tally or sum of the stock quantities 512, 516, 520, 524, 528, and 532.
• the central inventory database 312 may only store information about the total stock quantity 508, the amount 512 of the medication in the pharmacy, and the amounts 516 and 520 of the medication in the respective base stations 100.
• the remote medication database 408 is updated accordingly. For example, as medication is administered, the amount of the medication in a particular one of the mobile workstations 200 is updated, and the total stock quantity 508 is reduced accordingly.
• the medication system 400 then updates the central inventory database 312 with the updated total stock quantity 508 stored in the remote medication database 408.
• an example medication method 600 begins at 604.
• a healthcare professional removes a medication from a central pharmacy or a medication base station 100 and transfers the medication to a transport apparatus, e.g., according to a facility-approved protocol.
• the method 600 updates a remote medication database 408 (separate from a central inventory database 312 associated with the medication management system of the healthcare facility) according to the medication removed from the pharmacy/base station.
• the method 600 determines whether the medication has been administered to a patient or otherwise disposed. If true, the method 600 continues to 620. If false, the method 600 continues to 616.
• the method 600 updates the remote medication database 408 to reflect that the medication was administered.
• the method 600 may optionally generate and transmit a medication restock request, e.g., to the central pharmacy, and/or a medication reorder request, e.g., to the central pharmacy and/or a third party pharmaceuticals supplier, based on the updated remote medication database 408.
• the method 600 determines whether to generate a restock request to the central pharmacy to restock the medication base station 100.
• the method 600 may generate the restock request if the administration of the medication, as confirmed at 616, results in the stock quantity of the medication located in the medication base station 100 to decrease below a predetermined threshold.
• the method 600 transmits the restock request to the central pharmacy 308 to cause the central pharmacy 308 to have the medication base station 100 restocked. If false, the method 600 continues to 632.
• the method 600 determines whether to generate a reorder request to obtain new stock of the medication for the healthcare facility. For example only, the method 600 may generate the reorder request if the administration of the medication, as confirmed at 616, results in the total stock of the medication in the healthcare facility to decrease below a predetermined threshold. If the result of 632 is true, the method 600 transmits the reorder request to a third party pharmaceuticals supplier outside of the healthcare facility and/or to the central pharmacy. If false, the method 600 continues to 640. [0054] At 640, the method 600 updates the central inventory database 312 according to the information stored in the remote medication database 408. The method 600 ends at 644.
• Example embodiments are provided so that this disclosure will be thorough, and will fully convey the scope to those who are skilled in the art. Numerous specific details are set forth such as examples of specific components, devices, and methods, to provide a thorough understanding of embodiments of the present disclosure. It will be apparent to those skilled in the art that specific details need not be employed, that example embodiments may be embodied in many different forms and that neither should be construed to limit the scope of the disclosure. In some example embodiments, well-known processes, well-known device structures, and well-known technologies are not described in detail.

Landscapes

• Engineering & Computer Science (AREA)
• Business, Economics & Management (AREA)
• Health & Medical Sciences (AREA)
• General Business, Economics & Management (AREA)
• Medical Informatics (AREA)
• Public Health (AREA)
• Primary Health Care (AREA)
• General Health & Medical Sciences (AREA)
• Epidemiology (AREA)
• Biomedical Technology (AREA)
• Medicinal Chemistry (AREA)
• Bioinformatics & Cheminformatics (AREA)
• Chemical & Material Sciences (AREA)
• Economics (AREA)
• Quality & Reliability (AREA)
• Accounting & Taxation (AREA)
• Theoretical Computer Science (AREA)
• Finance (AREA)
• Development Economics (AREA)
• Physics & Mathematics (AREA)
• Tourism & Hospitality (AREA)
• General Physics & Mathematics (AREA)
• Strategic Management (AREA)
• Operations Research (AREA)
• Marketing (AREA)
• Human Resources & Organizations (AREA)
• Entrepreneurship & Innovation (AREA)
• Medical Treatment And Welfare Office Work (AREA)

Applications Claiming Priority (2)

Publications (2)

Family

ID=55019861

Family Applications (1)

Country Status (3)

Families Citing this family (2)

Family Cites Families (11)

• 2015
  • 2015-06-29 CA CA2954045A patent/CA2954045A1/en active Pending
  • 2015-06-29 WO PCT/US2015/038229 patent/WO2016003855A1/en active Application Filing
  • 2015-06-29 EP EP15814560.7A patent/EP3160418A4/de not_active Ceased

Also Published As

Similar Documents

Legal Events