Virtual assistant for interconnecting medical devices

Abstract

A method may include receiving a selection of a doctor's advice associated with a patient. A scannable token, such as a barcode, may be generated for interacting with one or more medical devices involved in the patient interaction to fulfill a doctor's advice. In some cases, the same scannable token may be further associated with one or more additional patient interactions made by the same or different clinician, and associated with the same or different patient. The scannable token may be sent to a client device. In response to the scannable token scanning on one or more medical devices, at least a portion of information related to a doctor's advice may be sent to the one or more medical devices. Related methods and articles are also disclosed.

Description

Technical Field

[0001] The subject matter described herein relates generally to device integration and, more particularly, to a virtual assistant for providing software-based interconnectivity between various medical devices. Background Art

[0002] Clinicians can interact with various medical devices when caring for various patients. For example, a clinician can dispense one or more medications to a patient from a medication cabinet. In the case of an intravenous infusion of one or more medications, a clinician can configure an infusion pump to deliver the one or more medications. In the case of one or more medications including controlled substances and / or hazardous substances, a clinician can interact with a discard station to discard any unused portions of the one or more medications.

[0003] Clinicians often have limited time. Clinicians’ time is often spent on device interaction, interacting with patients, discussing with clinical colleagues, and other tasks. As the complexity of devices increases, the time spent on device interaction and configuration also increases. Time spent on any one device is time that cannot be spent with patients. Summary of the invention

[0004] Systems, methods, and articles of manufacture, including computer program products, are provided for a virtual assistant that interconnects different medical devices to speed up interactions with the medical devices, thereby enabling more time for encounters with patients. In some exemplary embodiments, upon receiving information for interaction with a patient, an assistant server may generate a token for interacting with one or more medical devices involved in the interaction. Scanning the token on a medical device involved in the interaction may trigger one or more operations related to the interaction, including, for example, configuring the medical device, generating one or more records of the operation, and the like. In the case where the token is associated with a limited lifetime, scanning the token on a medical device after the token expires may not trigger any operations.

[0005] In one aspect, a system for performing scannable token-based patient interactions is provided. The system may include at least one data processor and at least one memory. The at least one memory may store instructions that, when executed by the at least one data processor, produce a plurality of operations. The plurality of operations may include: receiving a selection of a first medical order associated with a first patient; generating a scannable token for interacting with one or more medical devices involved in the first patient interaction to fulfill the first medical order; sending the scannable token to a client device; and in response to the scannable token being scanned on the one or more medical devices, sending at least a portion of information associated with the first medical order to the one or more medical devices.

[0006] In another aspect, a method for conducting a patient interaction based on a scannable token is provided. The method may include: receiving a selection of a first medical order associated with a first patient; generating a scannable token for interacting with one or more medical devices involved in the first patient interaction to fulfill the first medical order; sending the scannable token to a client device; and in response to the scannable token being scanned on the one or more medical devices, sending at least a portion of information associated with the first medical order to the one or more medical devices.

[0007] In another aspect, a non-transitory computer-readable medium is provided that stores instructions that, when executed by at least one data processor, result in a plurality of operations. The plurality of operations may include: receiving a selection of a first medical order associated with a first patient; generating a scannable token for interacting with one or more medical devices involved in an interaction with the first patient to fulfill the first medical order; sending the scannable token to a client device; and in response to the scannable token being scanned on the one or more medical devices, sending at least a portion of information associated with the first medical order to the one or more medical devices.

[0008] In some variations of the method, system, and non-transitory computer-readable medium, one or more of the following features can be optionally included in any feasible combination. The scannable token can be associated with a limited use period. The scannable token can expire when the scannable token reaches the end of the limited use period without being scanned on the one or more medical devices.

[0009] In some embodiments, the limited use period of the scannable token may be extended in response to the scannable token being scanned a threshold number of times and / or on a threshold number of medical devices among one or more medical devices before the scannable token expires.

[0010] In some variations, in response to determining that the first patient interaction is completed without the scannable token being scanned on any of the one or more medical devices, the scannable token may expire prior to the end of a limited use period of the scannable token.

[0011] In some variations, the operations may further include validating a scannable token scanned on the one or more medical devices prior to sending at least a portion of the information related to the first order to the one or more medical devices.

[0012] In some variations, the operations may further include authenticating an identity of a clinician interacting with the one or more medical devices based at least on a scannable token scanned on the one or more medical devices.

[0013] In some variations, the scannable token may be an additional authentication factor used to authenticate the identity of a clinician interacting with the one or more medical devices.

[0014] In some variations, at least a portion of the information sent to the one or more medical devices may include one or more parameters for configuring the one or more medical devices for the first medical order.

[0015] In some variations, the one or more medical devices may include an infusion pump.At least a portion of the information sent to the one or more medical devices may include one or more infusion parameters related to the first patient and / or a drug delivered to the first patient.

[0016] In some variations, the one or more data medical devices may include a dispensing cabinet. At least a portion of the information sent to the one or more medical devices may unlock a first container for removing the medication included in the first medical order and / or a second container for returning an unused portion of the medication after administering the medication to the first patient.

[0017] In some variations, at least a portion of the information sent to the one or more medical devices may trigger the generation of one or more electronic records documenting the interaction with the one or more medical devices to fulfill the first medical order.

[0018] In some embodiments, the operations may further include: receiving a patient interaction command specifying a first patient; retrieving one or more medical orders related to the first patient from an electronic medical record (EMR) repository in response to the patient interaction command; sending the one or more medical orders to a client device for output on the client device; and receiving a selection of a first medical order from the client device based at least on the one or more medical orders output on the client device.

[0019] In some variations, the patient interaction command and selection of the first order may include one or more of voice input, text input, and / or tactile input received on the client device.

[0020] In some variations, the scannable token may be generated to include a uniform resource locator (URL) of a server from which the one or more medical devices retrieve at least a portion of the information related to the first medical order.

[0021] In some variations, the scannable token may be generated to include at least a portion of the information related to the first medical order.

[0022] In some variations, the information associated with the first medical order may be encrypted. The scannable token may be further generated to include a uniform resource locator (URL) of a server from which a key for decrypting the information is retrieved.

[0023] In some variations, the patient interaction may include a first interaction with a first medical device followed by a second interaction with a second medical device. The error message may be triggered in response to the scannable token being scanned on the second medical device before the first medical device.

[0024] In some variations, the scannable token may be further generated for a second patient interaction to fulfill a second medical order associated with the first patient or the second patient. The first patient interaction may be prioritized over the second patient interaction based on a predetermined time for each interaction, a first location of the clinician relative to a second location of the first patient and a third location of the second patient, a shift and break schedule of the clinician, and / or a criticality of each patient.

[0025] In some variations, the first patient interaction and the second patient interaction may be conducted by the same clinician or different clinicians.

[0026] In some variations, the operations may further include sending one or more instructions, reminders, and / or feedback related to the interaction to the client device in response to the scannable token being scanned on the one or more medical devices.

[0027] The embodiments of the current theme may include methods consistent with the description provided herein and articles of machine-readable media including tangible implementations, the machine-readable media being operable to cause one or more machines (e.g., computers, etc.) to generate operations that implement one or more of the described features. Similarly, a computer system is also described, the computer system including one or more processors and a memory connected to the one or more processors. The memory (which may include a non-transitory computer-readable or machine-readable storage medium) may include one or more programs, encoding, storing, etc., one or more programs causing one or more processors to perform one or more of the operations described herein. The computer-implemented methods consistent with one or more embodiments of the current theme may be implemented by one or more data processors residing in a single computing system or multiple computing systems. Such multiple computing systems may be connected, for example, by one or more connections including connections through a network (e.g., the Internet, a wireless wide area network, a local area network, a wide area network, a wired network, etc.), by direct connections between one or more of the multiple computing systems, etc., and may exchange data and / or commands or other instructions, etc.

[0028] Details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the following description. Other features and advantages of the subject matter described herein will be apparent from the description and drawings, as well as from the claims. Although certain features of the subject matter disclosed herein are described for purposes of illustrating medical devices involved in interconnected clinical workflows, it should be readily understood that these features are not meant to be limiting. The claims appended to this disclosure are intended to define the scope of the protected subject matter. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate certain aspects of the subject matter disclosed herein and, together with the description, help explain some principles associated with the disclosed embodiments. In these drawings:

[0030] Figure 1 shows a system diagram of a virtual assistant system according to some exemplary embodiments;

[0031] Figure 2A A schematic diagram illustrating an example of a clinical workflow according to some exemplary embodiments;

[0032] Figure 2B A schematic diagram illustrating another example of a clinical workflow according to some exemplary embodiments;

[0033] Figure 2C A schematic diagram illustrating an example of a clinical workflow according to some exemplary embodiments;

[0034] Figure 3 A timing diagram illustrating an example of a process for conducting a scannable token-based patient interaction according to some exemplary embodiments;

[0035] Figure 4A A flow chart illustrating an example of a process for conducting a scannable token-based patient interaction according to some exemplary embodiments;

[0036] Figure 4B A flowchart illustrating another example of a process for conducting a scannable token-based patient interaction according to some exemplary embodiments; and

[0037] Figure 5 A block diagram of a computing system is depicted, according to some exemplary embodiments.

[0038] Whenever practicable, similar reference numerals refer to similar structures, features, or elements. DETAILED DESCRIPTION

[0039] In order to provide care for various patients, clinicians can interact with various medical devices (e.g., including dispensing cabinets, infusion pumps, waste stations, etc.). However, existing medical devices have limited interconnectivity. That is, although most clinical workflows require interaction with a series of medical devices, key data (e.g., patient, prescription or treatment information) used to perform each clinical workflow cannot be shared between different medical devices. Therefore, in order to administer medicines to patients, clinicians may need to enter patient information when dispensing medicines from dispensing cabinets, and then enter the same patient information again to configure infusion pumps to deliver medicines and / or discard any unused medicines at waste stations. The resulting workflow may lack efficiency, hinder patient participation, and distract clinicians from actual patient care.

[0040] In some exemplary embodiments, the virtual assistant can interconnect different medical devices involved in the interaction with the patient. The virtual assistant utilizes the existing functionality of various medical devices and can therefore be implemented with minimal additions and modifications to the hardware infrastructure of the medical facility. For example, upon receiving information related to an interaction with a patient, the assistant server can generate a token for interacting with one or more medical devices involved in the interaction. The token can be scanned at a first medical device involved in the interaction (e.g., a medicine cabinet) to dispense one or more drugs for administration to the patient, and then scanned at a second medical device involved in the interaction (e.g., an infusion pump) to configure the second medical device for delivery of the one or more drugs to the patient. In some cases, discarding any unused portion of one or more drugs at a third medical device involved in the interaction (e.g., a disposal station) can include scanning a token on the third medical device.

[0041] In some exemplary embodiments, the token generated at the assistant server can be displayed on the assistant client of the clinician with whom the patient interacts (e.g., a mobile device running an assistant application). In this case, the token can be scanned on each medical device involved in the interaction. Alternatively or additionally, the token generated at the assistant server can be displayed on the medical device involved in the interaction, in which case the scanning of the token can be performed by the assistant client of the clinician who is interacting (encountering) the patient. Scanning the token on the medical device can trigger one or more operations related to the interaction on the medical device. In the case where the token is associated with a limited period of use, scanning the token on the medical device after the token expires can trigger an error message, but will not trigger any operations related to the interaction.

[0042] Figure 1 A system diagram of a virtual assistant system 100 is shown according to some exemplary embodiments. Figure 1 , the virtual assistant system 100 may include an assistant server 110, an assistant client 120 deployed on a client device 125, a device controller 130 associated with one or more medical devices 135, and an electronic medical record (EMR) repository 140. Figure 1 As shown, the assistant server 110 , the client device 125 , the medical device controller 130 , and the electronic medical record repository 140 may be communicatively connected via a network 150 .

[0043] exist Figure 1In the example shown, the client device 125 can be specifically configured as a processor-based device, such as a smartphone, a tablet computer, a wearable device, a desktop computer, a laptop computer, a workstation, etc. The assistant client 120 can be an application, such as a mobile application or a web application, running on the client device 125 to perform one or more of the features described. In some cases, the client device 125 including the assistant client 120 can be a wireless handheld terminal specially configured to manage medical care in a clinical environment such as a hospital. The client device 125 can be (or include) a bar code module (BCM) that can display and scan codes corresponding to, for example, patient identification, item identification, document characters and phrases, commands and instructions. The code is preferably a machine-readable code, including one-dimensional and two-dimensional optically readable codes such as bar codes, but can include radio frequency identification (RFID) and near field communication (NFC) devices or tags. The code can be applied to objects, cards or signs throughout the hospital environment. Alternatively or additionally, as will be described in more detail below, the code can be a token generated by the assistant server 110 and propagated for display on the client device 125 and / or one or more medical devices 135.

[0044] One or more medical devices 135 associated with the device controller 130 may include medical devices configured to perform various clinical tasks (e.g., medication dispensing, infusion, waste, vascular access management, urine output monitoring, supply logistics, pharmacy compounding, transfer detection, etc.). Examples of the electronic medical record library 140 include a hospital information system (HIS) and a patient information database (PID). Meanwhile, the network 150 may be a wired and / or wireless network, including, for example, a public land mobile network (PLMN), a local area network (LAN), a virtual local area network (VLAN), a wide area network (WAN), the Internet, etc.

[0045] In some exemplary embodiments, the virtual assistant 120 on the client device 125 can be configured to interconnect one or more medical devices 135 involved in an interaction with a patient. Upon receiving information related to the patient interaction, the assistant server 110 can generate a token 115 for interacting with the one or more medical devices 135 involved in the interaction. For example, scanning the token 115 on each of the one or more medical devices 135 can trigger one or more corresponding operations related to the interaction. In the case where the token 115 is associated with a limited period of use, scanning the token 115 at one or more medical devices 135 after the token 115 has expired can trigger an error message, but will not trigger any operations related to the interaction. In this case, the clinician can still interact with the device according to the standard workflow, but, as discussed, this may take more time or operations than when the token 115 is valid.

[0046] In some exemplary embodiments, the token 115 may be associated with a limited lifespan corresponding to an estimated or projected amount of time required to complete a patient interaction. Thus, in some cases, the lifespan of a token 115 may be determined based on one or more factors, such as the location of the clinician relative to the location of the patient associated with each interaction, the nature of the task associated with each interaction, etc. Thus, if a token 115 is associated with a more complex task or a patient at a more remote location, a longer lifespan may be assigned to the token 115.

[0047] In some exemplary embodiments, the state of the token 115 can be changed based on whether the token 115 is scanned before expiration. For example, the token 115 may expire without having been scanned. In some cases, once the assistant server 110 determines that the corresponding interaction is completed, the token 115 may expire even if the token 115 is not scanned on any medical device 135 involved in the interaction. Determining that the interaction is completed can be based on information received from a client device, an electronic medical record system, a patient data management system, or other devices accessible by the assistant server 110. Alternatively, in other cases, the token 115 may be scanned at least once, but may expire before the interaction is completed. In some cases, in response to, for example, the token 115 being scanned a threshold number of times and / or being scanned on a threshold number of medical devices before the token 115 expires, the assistant server 110 may determine to extend the life of the token 115. For example, the assistant server 110 can dynamically determine the amount of time extension to be applied to the life of the token 115 based at least on the following equation (1). According to equation (1), the amount of time extension applied to the life of the token 115 can correspond to the proximity between the current medical device (e.g., the first medical device 135a) and the next medical device (e.g., the second medical device 135b) in the interaction. In addition, in some cases, the frequency with which tokens generated for a particular clinician expire before being scanned or before the corresponding interaction is completed can be used as a data point to assess the likelihood that the clinician will engage in risky behaviors such as diversion.

[0048] TimeExtension=dist(current to next)×avg_pace+buffer (1)

[0049] Among them, dist (current to next) represents the distance between the current medical device and the next medical device in the interaction, avg_pace represents the average travel speed (for example, the actual speed of the clinician associated with token 115, the speed derived from historical activities (for example, scanning), etc.), and buffer represents a time buffer generated by the system, user, or dynamically to account for randomness or variability in the clinical environment.

[0050] To further illustrate, Figure 2A An example of a clinical workflow 200 performed by the assistant client 120 on the client device 125 is depicted. In some exemplary embodiments, the clinician can interact with the assistant client 120 on the client device 125 through, for example, voice input, text input, tactile input, etc. To process the voice input, the assistant server 110 and / or the assistant client 120 can apply one or more natural language processing (NLP) techniques. Figure 2A, the clinical workflow 200 may include the assistant client 120 responding to a first user input from a clinician specifying a patient (e.g., Pat Jones) by displaying one or more interactions associated with the patient (e.g., administer medication N at 9:30 a.m., test at 11:00 a.m., etc.) on at least the client device 125. In some exemplary embodiments, the assistant client 120 may provide a recommended sequence for performing one or more interactions, for example, by displaying the one or more interactions in an order corresponding to the priority of each interaction. The respective priority of each interaction may in turn be determined based on various factors, including, for example, the scheduled time of each interaction, the location of the clinician relative to the location of the patient associated with each interaction, the shift and rest schedule of the clinician, the criticality of each patient, and the like.

[0051] like Figure 2A As shown, the assistant client 120 may receive a second user input selecting one of the patient-related interactions (e.g., administer medication N at 9:30 AM). In response to the second user input selecting one of the patient-related interactions, the assistant client 120 may prepare the selected interaction, which may include interacting with the assistant server 110 to generate a token 115 associated with the interaction. Figure 2A As shown, the token 115 received by the assistant client 120 from the assistant server 110 can be displayed on the client device 125 so that the token 115 can be used to interact. In some cases, selecting a particular interaction can include entering the client device 125 in a remote queue to access one or more medical devices 135 associated with the interaction. For example, in some exemplary embodiments, a client device 125 including the assistant client 120 can automatically connect to the first medical device 135a to enter a medical order for a drug (e.g., drug N). This connection can be established regardless of where the drug is actually stored, and there is no need to queue up at a terminal with other clinicians. In some cases, the pairing between the client device 125 and the first medical device 135a can prevent or lock other clinicians from pairing with or accessing the first medical device 135 for the duration of the pairing, while in other cases, the first medical device 135a can support multiple pairings, but limit access to the drug to a single device (e.g., the currently paired client device 125) based on the software queue.

[0052] Figure 2B Another example of a clinical workflow in which a token 115 is used to conduct an interaction with a patient is depicted. For example, in some cases, the token 115 that the assistant client 120 may receive from the assistant server 110 may be displayed on the client device 125 such that the token 115 may be presented on a first medical device 135a involved in the interaction with the patient. Figure 2BIn the example shown, the first medical device 135a is a medicine cabinet, and by scanning the token 115 displayed on the client device 125, a medicine (e.g., drug N) for administration to a patient (e.g., Pat Jones) during the interaction can be dispensed. However, it should be understood that in some cases, medicines can be removed from the first medical device 135a as part of the patient discharge procedure. In some cases, the token 115 can be scanned as part of authenticating a clinician associated with the client device 125. For example, the token 115 can encode an authentication token associated with the clinician and / or be used as an additional authentication factor for verifying the identity of the clinician. In this case, the authentication process can be adjusted based on whether a valid token 115 is presented at the first medical device 135a.

[0053] Additionally, in some exemplary embodiments, scanning the token 115 at the first medical device 135a may trigger one or more operations associated with dispensing the medication for the patient, including, for example, unlocking a container (e.g., a drawer, a pocket, etc.) containing the medication, generating one or more electronic records recording the transaction, etc. The one or more records of the transaction may include one or more transaction values ​​corresponding to, for example, a timestamp, a patient identifier, a device identifier, a clinician identifier, a medication identifier, a prescription order identifier, inventory information, a patient status, a shift identifier, a location tracking identifier, infusion information, dispensing information, administration information, an off-duty time indicator, an electronic health record (EHR) identifier, etc.

[0054] Reference again Figure 2B When a drug (e.g., drug N) is removed from the first medical device 135a, the assistant client 120 may provide one or more instructions, reminders, and / or feedback related to the interaction through the client device 125. Figure 2B In the example shown, the assistant client 120 can display one or more locations on the client device 125 where a patient (e.g., Pat Jones) who needs to take out the medicine from the first medical device 135a may be located. The assistant client 120 can also display procedural instructions related to the first medical device 135a or the medicine being administered to the patient on the client device 125. In some cases, the assistant client 120 can display encouraging messages and patient-specific instructions on the client device 125, such as the patient's birthday, previous complications, allergies, etc. It should be understood that the assistant client 120 can use a variety of different modalities (including text messages, voice prompts, tactile feedback, push notifications, etc.) to provide one or more instructions, reminders and / or feedback. In addition, in some cases, the assistant client 120 can actively provide one or more instructions, reminders and / or feedback related to the interaction, such as through push notifications, text messages, etc., without any triggering by the clinician.

[0055] In some exemplary embodiments, once the medicine removed from the first medical device 135a is administered to the patient, the assistant client 120 can provide various mechanisms to confirm and record the administration of the medicine. For example, the assistant client 120 on the client device 125 can provide one or more user interface elements, which are configured to receive one or more user inputs confirming the administration of the medicine. Therefore, in some cases, the administration of the medicine can be confirmed based on the user input received by the assistant client 120 through the client device 125 (e.g., one or more corresponding user interface elements displayed on the client device 125). Alternatively or additionally, the administration of one or more medicines can be confirmed by scanning a token 115 displayed by the assistant client 120 on the client device 125 on an electronic medical record (EMR) terminal.

[0056] Reference again Figure 2B In some cases, after the medication is administered and the administration of the medication is confirmed by the assistant client 120, the interaction with the patient may continue with the return of any unused portion of the medication. Figure 2B In the example shown, the unused portion of the drug removed from the first medical device 135a can be returned to the first medical device 135a (or a different medical device) for disposal and / or treatment. Figure 2BAs shown, the return of unused drugs can be performed by scanning a token 115 on a first medical device 135a to trigger one or more operations related to the return, disposal and / or disposal of unused drugs. Examples of such operations may include unlocking a container (e.g., a drawer, a pocket, etc.) designated to receive unused drugs, generating one or more electronic records of a record transaction, etc. One or more records of a transaction may include one or more transaction values ​​corresponding to, for example, a timestamp, a patient identifier, a device identifier, a clinician identifier, a drug identifier, a prescription order identifier, inventory information, a patient status, a shift identifier, a location tracking identifier, an infusion information, a dispensing information, a giving information, an off-duty time indicator, an electronic health record (EHR) identifier, etc. Once the unused drugs are returned to the first medical device 135a, the interaction with the patient can be terminated. The trigger may be based on a comparison between a token 115 or the data encoded thereby and one or more records. For example, a token 115 may include an identifier of the drug to be returned. In the absence of a token, the first medical device 135a may require a user to log in to the device and authenticate. Thereafter, the first medical device 135a may need to be configured to execute a disposal workflow, which may also include additional steps of identifying the medication, the amount to be disposed of, etc. However, in the case of using a token, when the token is presented to the first medical device 135a, the device 135a may skip one or more workflow steps based on information associated with the token 115. In addition to saving time, the token 115 may also reduce errors when configuring the first medical device 135a (e.g., avoiding manual data entry errors, correct workflow selection, etc.).

[0057] Figure 2C Another example of a clinical workflow conducted through the assistant client 120 on the client device 125 is depicted. In this example, an interaction with a patient (e.g., Pat Jones) may include administering a medication (e.g., drug N) intravenously, rather than orally to the patient. Thus, when a token 115 is scanned to remove medication from a first medical device 135a (e.g., a dispensing cabinet, a supply room, etc.), the token 115 may then be scanned on a second medical device 135b, which in this example is an infusion pump configured to deliver the medication removed from the first medical device 135a. Figure 2CAs shown, the second medical device 135b can be used as a bar code module (BCM) so that the token 115 is displayed on the client device 125 and scanned by the second medical device 135b. Alternatively, in some exemplary embodiments, the client device 125 can also be used as a bar code module (BCM), which means that the token 115 is instead displayed on the second medical device 135b and scanned by the client device 125. In either case, scanning the token 115 can trigger one or more operations on the second medical device 135b related to the delivery of the drug removed from the first medical device 135a. For example, Figure 2C It is shown that scanning the token 115 can configure the infusion parameters for the second medical device 135b to deliver the drug (e.g., drug N) to the patient (e.g., Pat Jones). Once the drug removed from the first medical device 135a is delivered to the patient using the second medical device 135b, the patient interaction can be terminated. Alternatively, although Figure 2C Not shown, but the patient interaction may be terminated after the unused portion of the medication is returned to the first medical device 135a (or a different medical device) (by, for example, scanning the token 115 on the first medical device 135a).

[0058] Although FIG. 2A to FIG. 2C The example of clinical workflow that token 115 is associated with single patient interaction (for example, single doctor's order of single patient) is shown, but it should be understood that in some cases, token 115 can be generated for multiple interactions related to the same patient or different patients and performed by the same clinician or different clinicians. For example, token 115 can be associated with the interaction performed by the same clinician with multiple patients. Token 115 can also be associated with multiple interactions related to the same patient. Alternatively or additionally, token 115 can be associated with multiple patient interactions occurring at a specific time (for example, 9 am). As previously mentioned, when token 115 is associated with multiple patient interactions, the interaction can be prioritized based on factors such as the scheduled time of each interaction, the position of the clinician relative to the patient position related to each interaction, the shift and rest time arrangement of the clinician, the criticality of each patient.

[0059] As described above, the assistant client 120 on the client device 125 may interact with the assistant server 110 to generate a token 115 for interacting with one or more medical devices 135. In some exemplary embodiments, the assistant server 110 may further interact with the device controller 130 and the electronic medical record repository 140 to integrate key data that is usually isolated in the device controller 130 and the electronic medical record repository 140. In this process, the assistant server 110 may generate the token 115 to include patient data from the electronic medical record repository 140 and device information from the device controller 130 when the token 115 is generated. For example, for each patient interaction, the generated token 115 may include information of the corresponding doctor's order, patient, clinician, etc.

[0060] In some cases, a token 115 may be generated to encode a unique identifier (e.g., a uniform resource locator (URL) of the assistant server 110) including information for locating the assistant server 110, so that corresponding information can be retrieved from the assistant server 110, the assistant client 120 on the client device 125, and / or the medical device 135 based on the unique identifier. For example, the first part of the identifier may include the network address of the assistant server 110, and the second part may include a string associated with the interaction. When the string is presented to the assistant server 110, the assistant server 110 may be caused to send a response message including information for the interaction. Alternatively, the token 115 may be generated to include information required for each medical device 135 involved in the interaction for each patient interaction (e.g., medical orders, patient and clinician information). In this case, the token 115 may include separated data elements that can be parsed by each device. When presented to a specific device, the device may extract data from the fields required for its interaction. In some cases, the information included in the token 115 may include a specific task sequence and a corresponding medical device. For example, the token 115 may encode information indicating that the interaction includes a first interaction with the first medical device 135a, followed by a second interaction with the second medical device 135b, in which case scanning the token 115 on the third medical device 135c after scanning the token 115 on the first medical device 135a may trigger a corresponding error message. It should be understood that the information included in the token 115 may be encrypted. In addition, in some cases, the token 115 may still include a unique identifier of the assistant server 110 (e.g., a uniform resource locator (URL) of the assistant server 110), but instead of retrieving information from the assistant server 110, the assistant client 120 may retrieve a key for decrypting the encrypted information included in the token 115.

[0061] To further illustrate, Figure 3FIG. 1 is a timing diagram illustrating an example of a process 300 for conducting a scannable token-based patient interaction according to some exemplary embodiments. Figure 3 , at 310, the assistant client 120 on the client device 125 can send a patient interaction command to the assistant server 110. In some cases, the patient interaction command can specify a specific patient (e.g., Pat Jones) by specifying one or more patient identifiers (e.g., patient name, patient identification number, etc.). In response to the patient interaction command, the assistant server 110 can identify the patient at 312. Identifying the patient can include performing natural language processing on audio of speech associated with the interaction command. Identifying the patient can include decoding or looking up the patient identifier based on the interaction command. At 314, the assistant server 110 can retrieve one or more patient orders from the electronic medical record (EMR) repository 140 based at least on the information identifying the patient. Referring again to Figure 2A Examples of patient orders may include administration of medication (e.g., medication N), laboratory tests, physical therapy, etc. In addition, each patient order (e.g., administration of multiple medication orders, collection of samples for laboratory tests, and physical therapy exercise exercises) may be associated with a patient's interaction.

[0062] For example, one or more patient orders retrieved from the electronic medical record repository 140 may be displayed by the assistant client 120 on the client device 125. The assistant client 120 may receive a user input selecting one of the orders displayed on the client device 125. At 316, the selected order may be sent to the assistant server 110, thereby initiating a clinical workflow for interacting with a patient corresponding to the selected order. For example, at 318, the assistant server 110 may identify one or more medical devices 135 required to perform the order. The identification may be based on an order type (e.g., drug administration). The order type may be associated with a dispensing device, an administration device, and a discarded or returned device. The association relationship may be stored in a data storage device accessible by the assistant server 110 and indexed using, for example, an order type. In addition, at 319, the assistant server 110 may generate a token (e.g., a token with a limited lifespan) for interacting with one or more medical devices 135 required to perform the order. The token may be generated to encode information and / or enable retrieval of information required to interact on each of the one or more medical devices for interaction (e.g., those identified at 318). It should be understood that operation 318 may be optional in the event that one or more medical devices 135 are configured to contact the assistant server 110 in response to scanning the token 115.

[0063] As described above, the assistant client 120 can display the token 115 on the client device 125 so that the token 115 can be scanned on one or more medical devices 135. Figure 3 In the example shown, the token may be presented to the device controller 130 at 320, and then the device controller 130 may verify the token 115 at 322. Verification of the token 115 may include determining whether the token 115 is not expired, is associated with an authorized user of the medical device, etc. At 324, the device controller 130 may verify an order identifier associated with the token 115, and then retrieve corresponding order details from the electronic medical record (EMR) repository 140 at 326. For example, the order may change between the time the token 115 is generated and the token 115 is presented to the medical device. Similarly, the verification at 324 may be used as a security check to authorize activities conducted by the device controller 130. Once confirmed, the device controller 130 may use at least a portion of the order information to retrieve the details needed to manage the order. At 328, the device controller 130 may configure one or more medical devices 135 based on the details of the order retrieved from the electronic medical record repository 140. For example, as Figure 2C As shown, the device controller 130 may configure the second medical device 135b according to infusion parameters associated with the patient (eg, Pat Jones) and the medication being delivered (eg, Drug N).

[0064] As used herein, the terms "adjust" or "adjusted", "control" or "controlled" may include various operations. For example, "adjusting" a medical device may include sending one or more messages to change the operating state or functional element of the device. The message may include specific instructions to be executed by the processor of the device to indicate the change. "Adjusting" may include storing a value at a certain location of a storage device for subsequent retrieval by the device to be controlled, transmitting a value directly to the device to be controlled through at least one wired or wireless communication medium, transmitting or storing a reference to a value, etc. For example, a control message may include a value for adjusting the power level of a power supply from the controlled device. As another example, a control message may activate or deactivate a structural element of the controlled device, such as a light, audio playback, motor, lock, pump, dispensing cabinet, dispensing drawer, dispensing box, display, or other components of the device described herein. "Controlling" or "adjusting" may include selecting one of a set of workflows on the device. For example, a drug return device may be configured to allow the return of fluid drugs in one way and the return of solid drugs in a second way. Adjustments in this case may activate different workflows and hardware to facilitate the safe and verifiable collection of material types. "Controlling" or "regulating" may include indirectly controlling a device by adjusting a configuration value used by the controlled device. For example, a control message may include a threshold value for a device characteristic (e.g., temperature, rate, frequency, etc.). The threshold value may be stored in a memory location and referenced by the controlled device during operation.

[0065] Figure 4A A flow chart illustrating an example of a process 400 for conducting a scannable token-based patient interaction according to some exemplary embodiments is shown. Figure 1 , Figure 3 and Figure 4A , process 400 can be performed by the assistant server 110 to conduct patient interactions involving one or more medical devices 135.

[0066] At 402, the assistant server 110 may receive a patient interaction command from the assistant client 120. For example, the assistant server 110 may receive a patient interaction command from the assistant client 120 on a client device to initiate an interaction with a particular patient (e.g., Pat Jones). The patient interaction command may specify a patient by specifying one or more patient identifiers (such as a patient name, a patient identification number, etc.).

[0067] At 404, the assistant server 110 may identify a patient associated with the patient interaction command. For example, the assistant server 110 may identify a corresponding patient based at least on one or more patient identifiers included in the patient interaction command.

[0068] At 406, the assistant server 110 may retrieve one or more medical orders associated with the patient for output by the assistant client 120 on the client device 125. In some exemplary embodiments, such as Figure 2A As shown, the assistant server 110 can retrieve one or more uncompleted medical orders related to the patient from the electronic medical record (ERM) repository 140 (e.g., administer medication N at 9:30 a.m., order a test at 11:00 a.m., etc.). Figure 2A In the example shown, these medical orders can be displayed by the assistant client 120 on the client device 125.

[0069] At 408, the assistant server 110 may receive a selection of a medical order associated with the patient from the assistant client 120. Figure 2A In the example shown, the assistant server 110 may receive a selection of an order to administer medication N to a patient from the assistant client 120 on the client device 125. The selection may include multiple orders for the same or different patients.

[0070] At 410, the assistant server 110 may generate a scannable token for interacting with one or more medical devices involved in the interaction to fulfill the selected medical order. In some exemplary embodiments, the assistant server 110 may generate a token 115 for interacting with one or more medical devices 135 involved in the interaction to fulfill the medical order to administer drug N to the patient. For example, Figure 2B An exemplary workflow is shown in which an interaction to fulfill an order to administer a medication N to a patient includes interacting with a first medical device 135a (e.g., a dispensing cabinet) to remove medication N and return an unused portion of medication N. Alternatively, Figure 2CAnother exemplary workflow is shown, in which the interaction of administering the drug N further includes interacting with a second medical device 135b (e.g., an infusion pump) to deliver the drug N to the patient. In either case, a token 115 can be generated to encode information and / or be able to retrieve information required for interaction at each of the one or more medical devices 135. For example, the token 115 can be generated to encode a unique identifier for locating the assistant server 110 (e.g., a uniform resource locator (URL) of the assistant server 110) so that the corresponding information can be retrieved from the assistant server 110, the assistant client 120 on the client device 125, and / or the medical device 135 based on the unique identifier. Alternatively, the token 115 can be generated to include information in an encrypted form required for each medical device 135 involved in the interaction for each patient interaction (e.g., medical orders, patient and clinician information). In some cases, the assistant server 110 can identify one or more medical devices 135 involved in the interaction before generating the token 115. However, this operation may be omitted where one or more medical devices 135 are configured to contact the assistant server 110 in response to scanning the token 115 .

[0071] At 412, the assistant server 110 may respond to the scannable token scanned on the one or more medical devices involved in the interaction by sending at least a portion of the information related to the selected order to the one or more medical devices. For example, when the token 115 is scanned at the one or more medical devices 135, the assistant server 110 may verify the token 115 before sending the corresponding order identifier to the device controller 130, so that the device controller 130 can retrieve the corresponding order details from the electronic medical record (EMR) repository 140 and send the order details to the one or more medical devices 135 for interaction on each of the one or more medical devices 135. In some cases, the order details sent to each of the one or more medical devices 135 may trigger operations such as configuring the one or more medical devices 135, generating one or more records recording the corresponding transaction, and the like.

[0072] Figure 4B FIG. 4 is a flow chart illustrating another example of a process 450 for conducting a scannable token-based patient interaction according to some exemplary embodiments. Figure 1 and Figure 4B , process 450 can be performed by the assistant client 120 on the client device 125 to conduct patient interactions involving one or more medical devices 135.

[0073] At 452, the assistant client 120 may respond to the first user input by sending at least a patient interaction command to the assistant server 110. For example, Figure 2A As shown, the assistant client 120 on the client device 125 may receive a first user input to initiate an interaction with a particular patient (e.g., Pat Jones). The assistant client 120 may respond to the first user input by at least sending a corresponding patient interaction command to the assistant server 110, which may specify the patient by specifying one or more patient identifiers (such as a patient name, a patient identification number, etc.).

[0074] At 454, the assistant client 120 may receive one or more orders of the patient associated with the patient interaction command from the assistant server 110. For example, the assistant client 120 may receive one or more uncompleted orders associated with the patient from the assistant server 110 (e.g., administer medication N at 9:30 a.m., order a test at 11:00 a.m., etc.), and the assistant server 110 may retrieve the orders from the electronic medical record (ERM) repository 140. As described above, the assistant server 110 may retrieve the one or more uncompleted orders from the electronic medical record (EMR) repository 140 based on one or more patient identifiers (e.g., patient name, patient identification number, etc.).

[0075] At 456, the assistant client 120 may output one or more medical instructions for the patient. In some exemplary embodiments, the assistant client 120 may output the one or more medical instructions by displaying the one or more medical instructions in at least a graphical user interface (GUI) on the client device 125. Alternatively or additionally, the one or more medical instructions may be provided as voice output on the client device 125.

[0076] At 458, the assistant client 120 may respond to the second user input selecting an order associated with the patient by sending at least an indication of the selected order to the assistant server 110. For example, upon receiving the second user input selecting an order to administer drug N to the patient, the assistant client 120 may send a corresponding indication of the selected order to the assistant server 110. As described above, the assistant server 110 may respond to receiving an indication of the selected order by at least identifying one or more medical devices 135 involved in the interaction to fulfill the selected order. In addition, the assistant server 110 may respond to receiving an indication of the selected order by generating a token 115 that can be used to interact with one or more medical devices 135 involved in the interaction.

[0077] At 460, the assistant client 120 may receive from the assistant server 110 a scannable token for interacting with one or more medical devices involved in the interaction to fulfill the selected medical order. In some exemplary embodiments, the assistant client 120 may receive from the assistant server 110 a token 115 for interacting with one or more medical devices 135 involved in the interaction to deliver the drug N to the patient.

[0078] At 462, the assistant client 120 may present a token for scanning on one or more medical devices. In some exemplary embodiments, the token 115 may be generated to encode information and / or be able to retrieve information required for interaction at each of the one or more medical devices 135. For example, the token 115 may be generated to encode a unique identifier for locating the assistant server 110 (e.g., a uniform resource locator (URL) of the assistant server 110) so that corresponding information may be retrieved from the assistant server 110, the assistant client 120 on the client device 125, and / or the medical device 135 based on the unique identifier. Alternatively, the token 115 may be generated to include information (e.g., medical orders, patient, and clinician information) in an encrypted form required for each medical device 135 involved in the interaction for each patient interaction. Thus, for example, when the token 115 is scanned in the first medical device 135a, the first medical device 135a may determine the corresponding portion of information for interaction at the first client device 135a based at least on the token 115. If the medical device is not configured to read the token 115 or the token 115 has expired or is otherwise invalid, the medical device is still operable to perform the patient interaction. However, at least one step of using the medical device will need to be performed manually, which would be bypassed if the token 115 is valid.

[0079] In view of the above embodiments of the subject matter of the present invention, the present application discloses the following list of examples, wherein one feature of an example alone or more than one feature combination of the examples and optionally in combination with one or more features of one or more further examples are further examples that also fall within the disclosure scope of the present application:

[0080] Item 1: A method comprising: receiving a selection of a first medical order associated with a first patient; generating a scannable token for interacting with one or more medical devices involved in an interaction with the first patient to fulfill the first medical order; sending the scannable token to a client device; and in response to the scannable token being scanned on the one or more medical devices, sending at least a portion of information associated with the first medical order to the one or more medical devices.

[0081] Item 2: A method according to Item 1, wherein the scannable token is associated with a limited usage period, and wherein the scannable token expires when the scannable token reaches the end of the limited usage period without being scanned on the one or more medical devices.

[0082] Item 3: A method according to Item 2, wherein the limited use period of the scannable token is extended in response to the scannable token being scanned a threshold number of times and / or being scanned on a threshold number of medical devices among one or more medical devices before the scannable token expires.

[0083] Item 4: A method according to any one of Items 1 to 3, wherein, in response to determining that a first patient interaction is completed without the scannable token being scanned on any one of the one or more medical devices, the scannable token expires before the end of a limited usage period of the scannable token.

[0084] Item 5: The method according to any one of Items 1 to 4 further includes: verifying the scannable token scanned on the one or more medical devices before sending at least a portion of the information related to the first medical order to the one or more medical devices.

[0085] Item 6: The method according to any one of Items 1 to 5 further includes: authenticating the identity of a clinician interacting with the one or more medical devices based at least on a scannable token scanned on the one or more medical devices.

[0086] Item 7: The method of Item 6, wherein the scannable token includes an additional authentication factor for authenticating the identity of a clinician interacting with the one or more medical devices.

[0087] Item 8: A method according to any one of Items 1 to 7, wherein at least a portion of the information sent to the one or more medical devices includes one or more parameters for configuring the one or more medical devices for the first medical order.

[0088] Item 9: A method according to any one of Items 1 to 8, wherein the one or more medical devices include an infusion pump, and wherein at least a portion of the information sent to the one or more medical devices includes one or more infusion parameters related to the first patient and / or the drug delivered to the first patient.

[0089] Item 10: A method according to any one of Items 1 to 9, wherein the one or more data medical devices include a medicine dispensing cabinet, and wherein at least a portion of the information sent to the one or more medical devices unlocks a first container for removing the medicine included in the first medical order and / or a second container for returning an unused portion of the medicine after administering the medicine to the first patient.

[0090] Item 11: A method according to any one of Items 1 to 10, wherein at least a portion of the information sent to the one or more medical devices triggers the generation of one or more electronic records recording the interaction with the one or more medical devices to fulfill the first medical order.

[0091] Item 12: The method according to any one of Items 1 to 11 further includes: receiving a patient interaction command specifying a first patient; retrieving one or more medical orders related to the first patient from an electronic medical record (EMR) repository in response to the patient interaction command; sending the one or more medical orders to a client device for output on the client device; and receiving a selection of a first medical order from the client device based at least on the one or more medical orders output on the client device.

[0092] Item 13: A method according to any one of Items 1 to 12, wherein the patient interaction command and the selection of the first medical order include one or more voice inputs, text inputs, and / or tactile inputs received on the client device.

[0093] Item 14: A method according to any one of Items 1 to 13, wherein the scannable token is generated to include a uniform resource locator (URL) of a server, and the one or more medical devices retrieve at least a portion of the information related to the first medical order from the server.

[0094] Item 15: A method according to any one of Items 1 to 14, wherein the scannable token is generated to include at least a portion of the information related to the first medical order.

[0095] Item 16: A method according to Item 15, wherein the information related to the first medical order is encrypted, and wherein the scannable token is further generated to include a uniform resource locator (URL) of a server, and a key for decrypting the information is retrieved from the server.

[0096] Item 17: A method according to any one of Items 1 to 16, wherein the patient interaction includes a first interaction with a first medical device followed by a second interaction with a second medical device, and wherein an error message is triggered in response to the scannable token being scanned on the second medical device before the first medical device.

[0097] Item 18: A method according to any one of Items 1 to 17, wherein the scannable token is further generated for a second patient interaction to fulfill a second medical order associated with the first patient or the second patient, and wherein the first patient interaction is prioritized over the second patient interaction based on a scheduled time for each interaction, a first location of the clinician relative to a second location of the first patient and a third location of the second patient, the clinician's shift and break schedule, and / or the criticality of each patient.

[0098] Item 19: A method according to Item 18, wherein the first patient interaction and the second patient interaction are performed by the same clinician or different clinicians.

[0099] Item 20: The method according to any one of claims 1 to 19 further includes: in response to the scannable token being scanned on the one or more medical devices, sending one or more instructions, reminders and / or feedback related to the interaction to the client device.

[0100] Item 21: A system comprising: at least one data processor; and at least one memory, wherein the at least one memory stores instructions that, when executed by the at least one data processor, produce operations including the method described in any one of Items 1 to 20.

[0101] Item 22: A non-transitory computer-readable storage medium storing instructions that, when executed by at least one data processor, produce operations including the method of any one of Items 1 to 20.

[0102] Figure 5 A block diagram of a computing system 500 consistent with an embodiment of the current subject matter is shown. Figure 1 and Figure 5 , the computing system 500 can be specifically configured to implement the assistant server 110, the client device 120, the device controller 130 and / or components therein.

[0103] like Figure 5As shown, the computing system 500 may include a processor 510, a memory 520, a storage device 530, and an input / output device 540. The processor 510, the memory 520, the storage device 530, and the input / output device 540 may be interconnected via a system bus 550. The processor 510 is capable of processing instructions for execution within the computing system 500. Such execution instructions may implement one or more components such as the assistant server 110, the client device 120, the device controller 130, etc. In some exemplary embodiments, the processor 510 may be a single-threaded processor. Alternatively, the processor 510 may be a multi-threaded processor. The processor 510 is capable of processing instructions stored in the memory 520 and / or the storage device 530 to display graphical information of a user interface provided by the input / output device 540.

[0104] Memory 520 is a computer-readable medium such as a volatile or non-volatile medium that stores information within computing system 500. For example, memory 520 may store a data structure representing a configuration object database. Storage device 530 can provide persistent storage for computing system 500. Storage device 530 may be a floppy disk device, a hard disk device, an optical disk device, a magnetic tape device, a solid-state device, and / or other suitable persistent storage device. Input / output device 540 provides input / output operations for computing system 500. In some exemplary embodiments, input / output device 540 includes a keyboard and / or a pointing device. In various embodiments, input / output device 540 includes a display unit for displaying a graphical user interface.

[0105] According to some exemplary embodiments, the input / output device 540 can provide input / output operations for the network device. For example, the input / output device 540 can include an Ethernet port or other network port for communicating with one or more wired and / or wireless networks (e.g., a local area network (LAN), a wide area network (WAN), the Internet).

[0106] In some exemplary embodiments, the computing system 500 can be specifically configured to execute various interactive computer software applications that can be used to organize, analyze and / or store data in various formats. These applications can be used to perform various functions, such as planning functions (e.g., generating, managing, editing electronic spreadsheet documents, word processing documents and / or any other objects, etc.), computing functions, communication functions, etc., to support the described interactive and medical device configuration functions. Once activated within the application, the functions can be used to generate a user interface provided by the input / output device 540. The user interface can be generated by the computing system 500 and presented to the user (e.g., on a computer screen monitor, etc.).

[0107] One or more aspects or features of the subject matter described herein can be implemented in a digital electronic circuit, an integrated circuit, a specially designed ASIC, a field programmable gate array (FPGA) computer hardware, firmware, software and / or a combination thereof of a specific configuration. These various aspects or features can include embodiments in one or more computer programs that can be executed and / or interpreted on a programmable system, the programmable system including at least one programmable processor, a storage system, at least one input device and at least one output device, the at least one programmable processor being connected to the storage system, at least one input device and at least one output device, to receive data and instructions from the storage system, at least one input device and at least one output device and to send data and instructions to them. A programmable system or computing system can include a client and a server. The client and the server are usually far away from each other and usually interact through a communication network. The relationship between the client and the server is generated by a computer program running on a respective computer and having a client-server relationship between each other.

[0108] These computer programs, which may also be referred to as programs, software, software applications, applications, components or codes, include machine instructions for programmable processors and may be implemented in high-level programs and / or object-oriented programming languages ​​and / or in assembly / machine languages. As used herein, the term "machine-readable medium" refers to a computer program product, device and / or equipment, such as a disk, an optical disk, a memory and a programmable logic device (PLD), for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as machine-readable signals. The term "machine-readable signal" refers to a signal for providing machine instructions and / or data to a programmable processor. A machine-readable medium may, for example, store such machine instructions non-temporarily, such as a non-transient solid-state memory or a magnetic hard drive or an equivalent storage medium. A machine-readable medium may alternatively or additionally, for example, store such machine instructions in a transient manner, such as a processor cache or other random access memory associated with one or more physical processor cores.

[0109] To provide interaction with a user, one or more aspects or features of the subject matter described herein may be implemented on a computer having a display device, such as a cathode ray tube (CRT) or liquid crystal display (LCD) or light emitting diode (LED) monitor for displaying information to a user, and a keyboard and pointing device, such as a mouse or trackball, through which a user can provide input to the computer. Other types of devices may also be used to provide interaction with a user. For example, feedback provided to a user may be sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from a user may be received, including acoustic, voice, or tactile input. Other possible input devices include touch screens or other touch-sensitive devices such as single-point or multi-point resistive or capacitive tracking pads, voice recognition hardware and software, optical scanners, optical pointers, digital image capture devices, and associated interpretation software, and the like.

[0110] In the above description and in the claims, phrases such as "at least one" or "one or more" may appear before a list of combinations of elements or features. The term "and / or" may also appear in a list of two or more elements or features. Unless otherwise implicitly or explicitly contradictory to the context used, this phrase is intended to mean any one of the elements or features listed individually, or any combination of any one of the elements or features recorded with any other elements or features recorded. For example, the phrases "at least one of A and B", "one or more of A and B", and "A and / or B" are used to mean "single A, single B, or A and B together", respectively. Similar explanations can also be used for lists including three or more items. For example, the phrases "at least one of A, B, and C"; "one or more of A, B, and C"; and "A, B, and / or C" are used to mean "single A, single B, single C, A and B together, A and C together, B and C together, or A, B and C together", respectively. The term "based on" as used above and in the claims is used to mean "based, at least in part, on" such that non-recited features or elements are also permitted.

[0111] Depending on the desired configuration, the subject matter of the present invention described herein can be implemented in systems, devices, methods and / or objects. The embodiments set forth in the above description do not represent all embodiments consistent with the subject matter described herein. On the contrary, the embodiments are only some examples consistent with the aspects related to the described subject matter. Although some variations have been described in detail above, other modifications or additions may also be made. In particular, in addition to those features and / or variations set forth herein, other features and / or variations may also be provided. For example, the above embodiments may be directed to various combinations and sub-combinations of the disclosed features, and / or combinations and sub-combinations of several further features disclosed above. In addition, the logical flows depicted in the accompanying drawings and / or described herein do not necessarily require the specific order or sequence shown to obtain the desired results. Other embodiments may fall within the scope of the appended claims.

Claims

1. A system comprising: at least one data processor; as well as At least one memory storing instructions that, when executed by at least one data processor, produce the following operations: receiving a selection of a first physician order associated with a first patient; generating a scannable token for interacting with one or more medical devices involved in a first patient interaction to fulfill a first medical order; sending the scannable token to a client device; as well as In response to the scannable token being scanned on the one or more medical devices, at least a portion of the information related to the first medical order is sent to the one or more medical devices.

2. The system according to claim 1, wherein: The scannable token is associated with a limited use period, and wherein the scannable token expires when the scannable token reaches an end of the limited use period without being scanned on the one or more medical devices.

3. The system according to claim 2, wherein: In response to the scannable token being scanned a threshold number of times and / or being scanned on a threshold number of medical devices among the one or more medical devices before the scannable token expires, the limited use period of the scannable token is extended.

4. The system according to any one of claims 1 to 3, wherein: In response to determining that the first patient interaction is completed without the scannable token being scanned on any of the one or more medical devices, the scannable token expires prior to an end of a limited usage period of the scannable token.

5. The system according to any one of claims 1 to 4, wherein: The operations further include: Prior to sending at least a portion of the information related to the first medical order to the one or more medical devices, a scannable token scanned on the one or more medical devices is authenticated.

6. The system according to any one of claims 1 to 5, wherein: The operations further include: An identity of a clinician interacting with the one or more medical devices is authenticated based at least on a scannable token scanned on the one or more medical devices.

7. The system according to claim 6, wherein: The scannable token includes an additional authentication factor for authenticating the identity of a clinician interacting with the one or more medical devices.

8. The system according to any one of claims 1 to 7, wherein: At least a portion of the information sent to the one or more medical devices includes one or more parameters for configuring the one or more medical devices for a first medical order.

9. The system according to any one of claims 1 to 8, wherein: The one or more medical devices include an infusion pump, and wherein at least a portion of the information sent to the one or more medical devices includes one or more infusion parameters related to the first patient and / or a drug delivered to the first patient.

10. The system according to any one of claims 1 to 9, wherein: The one or more digital medical devices include a dispensing cabinet, and wherein at least a portion of the information sent to the one or more medical devices unlocks a first container for removing a drug included in a first medical order and / or a second container for returning an unused portion of the drug after administering the drug to a first patient.

11. The system according to any one of claims 1 to 10, wherein: At least a portion of the information sent to the one or more medical devices triggers generation of one or more electronic records documenting interactions with the one or more medical devices to fulfill a first medical order.

12. The system according to any one of claims 1 to 11, wherein: The operations further include: receiving a patient interaction command designating a first patient; In response to the patient interaction command, retrieving one or more medical orders associated with a first patient from an electronic medical record (EMR) repository; sending the one or more medical orders to a client device for output on the client device; and A selection of a first medical order is received from a client device based at least on one or more medical orders output on the client device.

13. The system according to any one of claims 1 to 12, wherein: The patient interaction command and selection of a first order include one or more voice input, text input, and / or tactile input received on a client device.

14. The system according to any one of claims 1 to 13, wherein: The scannable token is generated to include a uniform resource locator (URL) of a server, and the one or more medical devices retrieve at least a portion of the information related to the first medical order from the server.

15. The system according to any one of claims 1 to 14, wherein: The scannable token is generated to include at least a portion of information related to the first medical order.

16. The system of claim 15, wherein: Information associated with the first medical order is encrypted, and wherein the scannable token is further generated to include a uniform resource locator (URL) of a server from which a key for decrypting the information is retrieved.

17. A system according to any one of claims 1 to 16, wherein: The patient interaction includes a first interaction with a first medical device followed by a second interaction with a second medical device, and wherein an error message is triggered in response to the scannable token being scanned on the second medical device before the first medical device.

18. A system according to any one of claims 1 to 17, wherein: The scannable token is further generated for a second patient interaction to fulfill a second medical order associated with the first patient or the second patient, and wherein the first patient interaction is prioritized over the second patient interaction based on a scheduled time for each interaction, a first location of the clinician relative to a second location of the first patient and a third location of the second patient, the clinician's shift and break schedule, and / or the criticality of each patient.

19. The system of claim 18, wherein: The first patient interaction and the second patient interaction are performed by the same clinician or different clinicians.

20. The system according to any one of claims 1 to 19, wherein: The operations further include: In response to the scannable token being scanned on the one or more medical devices, one or more instructions, reminders, and / or feedback related to the interaction are sent to the client device.

21. A method comprising: receiving a selection of a first physician order associated with a first patient; generating a scannable token for interacting with one or more medical devices involved in a first patient interaction to fulfill a first medical order; sending the scannable token to a client device; as well as In response to the scannable token being scanned on the one or more medical devices, at least a portion of the information related to the first medical order is sent to the one or more medical devices.

22. The method according to claim 21, wherein: The scannable token is associated with a limited use period, and wherein the scannable token expires when the scannable token reaches an end of the limited use period without being scanned on the one or more medical devices.

23. The method according to claim 22, wherein: In response to the scannable token being scanned a threshold number of times and / or being scanned on a threshold number of medical devices among the one or more medical devices before the scannable token expires, the limited use period of the scannable token is extended.

24. The method according to any one of claims 21 to 23, wherein: In response to determining that the first patient interaction is completed without the scannable token being scanned on any of the one or more medical devices, the scannable token expires prior to an end of a limited usage period of the scannable token.

25. The method according to any one of claims 21 to 24, further comprising: Prior to sending at least a portion of the information related to the first medical order to the one or more medical devices, a scannable token scanned on the one or more medical devices is authenticated.

26. The method according to any one of claims 21 to 25, further comprising: An identity of a clinician interacting with the one or more medical devices is authenticated based at least on a scannable token scanned on the one or more medical devices.

27. The method according to claim 26, wherein: The scannable token includes an additional authentication factor for authenticating the identity of a clinician interacting with the one or more medical devices.

28. The method according to any one of claims 21 to 27, wherein: At least a portion of the information sent to the one or more medical devices includes one or more parameters for configuring the one or more medical devices for a first medical order.

29. The method according to any one of claims 21 to 28, wherein: The one or more medical devices include an infusion pump, and wherein at least a portion of the information sent to the one or more medical devices includes one or more infusion parameters related to the first patient and / or a drug delivered to the first patient.

30. The method according to any one of claims 21 to 29, wherein: The one or more digital medical devices include a dispensing cabinet, and wherein at least a portion of the information sent to the one or more medical devices unlocks a first container for removing a drug included in a first medical order and / or a second container for returning an unused portion of the drug after administering the drug to a first patient.

31. The method according to any one of claims 21 to 30, wherein: At least a portion of the information sent to the one or more medical devices triggers generation of one or more electronic records documenting interactions with the one or more medical devices to fulfill a first medical order.

32. The method according to any one of claims 21 to 31, further comprising: receiving a patient interaction command designating a first patient; In response to the patient interaction command, retrieving one or more medical orders associated with a first patient from an electronic medical record (EMR) repository; sending the one or more medical orders to a client device for output on the client device; as well as A selection of a first medical order is received from a client device based at least on one or more medical orders output on the client device.

33. The method according to any one of claims 21 to 32, wherein: The patient interaction command and selection of a first order include one or more voice input, text input, and / or tactile input received on a client device.

34. The method according to any one of claims 21 to 33, wherein: The scannable token is generated to include a uniform resource locator (URL) of a server, and the one or more medical devices retrieve at least a portion of the information related to the first medical order from the server.

35. The method according to any one of claims 21 to 34, wherein: The scannable token is generated to include at least a portion of information related to the first medical order.

36. The method of claim 35, wherein: Information associated with the first medical order is encrypted, and wherein the scannable token is further generated to include a uniform resource locator (URL) of a server from which a key for decrypting the information is retrieved.

37. The method according to any one of claims 21 to 36, wherein: The patient interaction includes a first interaction with a first medical device followed by a second interaction with a second medical device, and wherein an error message is triggered in response to the scannable token being scanned on the second medical device before the first medical device.

38. The method according to any one of claims 21 to 37, wherein: The scannable token is further generated for a second patient interaction to fulfill a second medical order associated with the first patient or the second patient, and wherein the first patient interaction is prioritized over the second patient interaction based on a scheduled time for each interaction, a first location of the clinician relative to a second location of the first patient and a third location of the second patient, the clinician's shift and break schedule, and / or the criticality of each patient.

39. The method of claim 38, wherein: The first patient interaction and the second patient interaction are performed by the same clinician or different clinicians.

40. The method according to any one of claims 21 to 39, further comprising: In response to the scannable token being scanned on the one or more medical devices, one or more instructions, reminders, and / or feedback related to the interaction are sent to the client device.

41. A non-transitory computer-readable storage medium storing instructions which, when executed by at least one data processor, produce operations comprising the method of any one of claims 21 to 40.

Images