Infusion device configured to make non-infusion electronic medical record (EMR) entries

Abstract

Certain aspects of the disclosure provide electronic medical record documentation systems and methods, in particular, systems and methods for adding notes to a patient's electronic medical record via an infusion system. Methods include receiving user input corresponding to a patient note and sending to the electronic medical record information for adding an entry to the electronic medical record, including the patient note.

Description

INFUSION DEVICE CONFIGURED TO MAKE NON-INFUSION ELECTRONIC MEDICAL RECORD (EMR) ENTRIES BACKGROUNDField

[0001] Aspects of the present disclosure relate to electronic medical record documentation systems and methods, in particular, systems and methods for adding notes to a patient’s electronic medical record via an infusion system.Description of Related Art

[0002] Clinicians document a variety of patient medical information, events, and other information in a patient’s electronic medical record (“EMR”). An EMR (also called an electronic health record “EHR”) may include documentation of a patient’s medical history, diagnosis, treatments, laboratory data, etc.

[0003] Generally, when a clinician wishes to document in an EMR, for example, record information, events, etc., the clinician must log into an EMR terminal, identify the patient, and create an entry. An EMR terminal may be a computer or mobile device connected to an EMR system.

[0004] Often, however, a clinician wishes to document an event (or other information) when the clinician is not connected to an EMR terminal or in close proximity to the EMR terminal. For example, the EMR terminal may be a computer located outside of a patient’s room and the clinician must leave the room to connect to the EMR terminal and record an event. Either the clinician stops working in the patient’s room to contemporaneously record, or the clinician waits until finished working in the patient’s room and to subsequently record.

[0005] If the clinician stops working in the patient’s room to contemporaneously record, the recorded information may be beneficially accurate, but the clinician pauses care. In some cases, the clinician would need to pause care many times to record. Not only does this disrupt patient care, but also leads to time-loss and other inefficiencies. Further, the clinician must re-log into the terminal and identify the patient before making the entry, to ensure authorization to record, which may introduce additional potential error where the clinician misidentifies a patient.

[0006] If the clinician waits until they are finished working in the patient’s room to subsequently record, patient care is not disrupted and the clinician completes patient care tasks before recordation. Further, the clinician does not need to log in as many times, and reduces chances of misidentifying the patient. However, by waiting to record, a clinician may be lessaccurate in the record, for example, omitting an event or information, misidentifying an event or information, conflating an event, etc.

[0007] Even when the EMR terminal is a mobile device, the clinician needs to pause interaction with the patient and / or other devices in the patient’s room to record.

[0008] Accordingly, there is a need for additional and improved systems and methods for entering patient notes into a patient’s EMR.SUMMARY

[0009] Certain aspects provide a method of adding entries to an electronic medical record using an infusion pump controller configured to control an infusion pump configured to deliver fluid to a patient, comprising: associating the infusion pump controller with the patient; receiving, on the infusion pump controller, user input corresponding to a patient note; and sending, from the infusion pump controller, to the electronic medical record, information for adding an entry to the electronic medical record, the information comprising the patient note.

[0010] Other aspects provide processing systems configured to perform the aforementioned methods as well as those described herein; non-transitory, computer-readable media comprising instructions that, when executed by a processors of a processing system, cause the processing system to perform the aforementioned methods as well as those described herein; a computer program product embodied on a computer readable storage medium comprising code for performing the aforementioned methods as well as those further described herein; and a processing system comprising means for performing the aforementioned methods as well as those further described herein.

[0011] The following description and the related drawings set forth in detail certain illustrative features of one or more aspects.DESCRIPTION OF THE DRAWINGS

[0012] The appended figures depict certain aspects and are therefore not to be considered limiting of the scope of this disclosure.

[0013] FIG. 1 depicts an example electronic medical recordation system.

[0014] FIG. 2 depicts an example workflow for activating a patient note mode on an infusion system.

[0015] FIG. 3 depicts an example workflow for entering a patient note on an infusion system.

[0016] FIGS. 4A, 4B, and 5 depict various example infusion system user interfaces configured to facilitate a patient note mode and patient note entry.

[0017] FIG. 6 depicts an example method for entering a patient note on an infusion system.

[0018] FIG. 7 depicts an example processing system with which aspects of the present disclosure can be performed.

[0019] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the drawings. It is contemplated that elements and features of one embodiment may be beneficially incorporated in other embodiments without further recitation.DETAILED DESCRIPTION

[0020] Aspects of the present disclosure provide apparatuses, methods, processing systems, and computer-readable mediums for adding patient notes to patient EMR via an infusion system. In particular, systems and methods described herein provide for recordation of non-infusion patient notes to the patient EMR through the infusion system and infusion system-EMR system connectivity. Non-infusion patient notes may refer to notes other than notes generated by the infusion system related to operation of the infusion system to perform infusion. For example, non-infusion patient notes may refer to user generated or user selected notes, as opposed to auto generated notes generated by the infusion system based on operation of the infusion system.

[0021] EMRs are used to generate a comprehensive record of a patient’s medical information, including, history, complaints, laboratory and radiographic tests, medications, procedures, diagnoses, treatments, and / or the like. Clinicians enter such information during the course of patient care. In some cases, an EMR may further include information related to medical devices, for example, an infusion system used to administer one or more treatments to a patient. A clinician, for example, a clinician entering an infusion medication order, may enter such information. The infusion system may automatically generate notes based on operation of the infusion system.

[0022] As described herein, improved and efficient entry into the EMR improves patient care, for example, by reducing medical errors. EMR terminals, such as computers and / or mobile devices, allow clinicians to enter information into a patient’s EMR, including patient notes regarding the clinician’s interactions, observations, and activities with the patient.

[0023] However, as described above, such terminals are not always convenient for contemporaneous recordation because the terminals may be located outside of a patient’s room or care area, shared between multiple clinicians, require repetitive login, and / or the like. Thus, a clinician may need to pause care to add an entry. Other times, a clinician delays entry, such as to finish patient care, access an available terminal, and / or the like. This may result in data loss, especially where a clinician desires to make multiple entries. For example, after one patient interaction, a clinician may desire to make entries: “Heart rate 85 BMP;” “BP 113 / 76;” and“Patient complained of cold feed. Put socks on both feet.” However, the clinician may miss inputting one entry, or otherwise mix up an entry when the clinician waits to enter into the EMR.

[0024] Further, a clinician may make a note, such as a physical note, for later entry into the EMR. Such notes may improve retention and recordation of data; however, there may be privacy and security concerns with physical notes. In addition, a clinician may lose a physical note, forget to which patient a note applies, or neglect to enter the contents of the note into the EMR.

[0025] Thus, aspects described herein overcome such technical limitations and provide improved systems and methods for patient note entry into an EMR by utilizing an infusion system as an EMR terminal. Beneficially, infusion systems often are already conveniently located close to patients, and within patient care areas, such that a clinician caring for a patient may also be close to the infusion system. In some cases, the clinician may already be working with an infusion system as part of caring for the patient. Thus, by utilizing the infusion system as an EMR terminal, even for non-infusion related entries, entries may be added in a convenient and efficient manner, allowing clinicians to remain with a patient while contemporaneously adding EMR entries. Thereby, efficiency is increased by reducing time-loss between activity and entry, as well as reducing data loss due to delayed entry. Patient care is improved through improve recordation methods.

[0026] Furthermore, aspects described herein provide technical benefits by utilizing preexisting network connections, providing secure transmission methods. Specifically, many infusion systems may be integrated with an EMR and / or hospital system to facilitate transmission of infusion data, such as infusion parameters, through secure networks. Thus, EMR entries through the infusion pump may advantageously utilize these secure networks to transmit the entries, maintaining security of the EMR.

[0027] Additionally, an infusion system may be associated with a patient, for example, during set-up of the infusion system, such that entries at an infusion pump are already associated with the patient, thereby reducing errors in recording entries on an incorrect patient’s EMR.Example Electronic Medical Recordation System

[0028] FIG. 1 depicts an example electronic medical recordation system 100 to facilitate creation and maintenance of patient electronic medical records.

[0029] EMR system 114, e.g., including one or more of a database, one or more computing devices, etc., may store one or more EMRs, including EMR 106. Accordingly, EMR system 114 is configured to create and / or maintain patients’ EMRs, including EMR 106. EMR 106 may include documentation of a patient’s medical history, diagnosis, treatments, laboratory data,and / or the like. EMR system 114 may communicate (e.g., send and / or receive), directly or indirectly via one or more other devices, with infusion system 102, such as using network 104 (e.g., a local area network (LAN), internet, etc.). Further, EMR system 114 may communicate with one or more EMR terminals 108. An EMR terminal 108 may be a computer or mobile device, for example. Accordingly, EMR system 114 can communicate EMR related data, such as patient data, with infusion system 102, and in some cases, EMR terminals 108. EMR system 114 may create and / or update EMR 106 based on data communicated by infusion system 102 and / or EMR terminals 108. Further, in certain aspects, EMR system 114 may send data related to EMR 106 to infusion system 102 and / or EMR terminals 108, such as based on receiving a request for such data from infusion system 102 and / or EMR terminals 108.

[0030] In certain aspects, EMR system 114 may further communicate, directly or indirectly, such as via network 104, with hospital system 110, e.g., including one or more of one or more computing devices, a database, etc. For example, hospital system 110 may transmit laboratory testing data, prescriptions, and / or the like to EMR system 114 for updating EMR 106.

[0031] Infusion system 102 is an electromechanical device for infusing therapeutic fluids into a patient in a controlled and precise manner. Exemplary infusion systems may include a syringe pump or a large volume pump. Infusion system 102 comprises an infusion system controller (not depicted) configured to control operations of infusion system 102. In general operation, therapeutic fluid is loaded into an infusion pump, for example, in a syringe, bottle, bag, or other storage container, and the infusion system is configured to pump, or infuse, the therapeutic fluid according to operational parameters of the pump, including, for example, flow rate, volume, and / or time to administer a specific dose of treatment.

[0032] Infusion system 102 is further configured to transmit data related to the infusion, for example, infusion parameters, infusion data, operational data, and / or the like. As described herein, infusion system 102 is configured to send data to EMR system 114, for entry into a patient’s EMR, such as EMR 106. According to aspects described herein, infusion system 102 is further configured to send EMR entries to EMR system 114, for entry into a patient’s EMR, such as EMR 106, for example, entries unrelated to infusion system 102.Example Workflow for Entering Patient Notes

[0033] FIGS. 2-3 depict example workflows for entering patient notes on an infusion system, such as infusion system 102 in FIG. 1. In particular, FIG. 2 depicts an example workflow 200 for activating a patient note mode on the infusion system.

[0034] Workflow 200 begins at 202. At step 204, the infusion system is associated with a patient. The infusion system may receive data associated with a patient, for example, a patient’s name, hospital identification number, etc. or other identifiers of the patient. In some examples, a clinician may enter, such as through a user interface of the infusion system, the patient’s identifier. In other examples, the patient identifier may entered by scanning an identification number, such as a barcode on a hospital bracelet, an electronic data tag, such as a radio frequency identification device ("RFID") tag, and / or the like.

[0035] At step 206, the infusion system is associated with a clinician. The infusion system may receive data associated with a clinician, for example, a clinician’s name, hospital identification number, etc. or other identifiers of the clinician. In some examples, a clinician may enter, such as through a user interface of the infusion system, the clinician’s identifier. In other examples, the clinician identifier may entered by scanning an identification number, such as a barcode on an identification badge, an electronic data tag, such as an RFID tag, or the like. In some embodiments, the infusion system is not associated with any clinician, for example, when a clinician identifier is not entered, entered incorrectly, clinician not found, and the like, and the patient note mode is disabled until the infusion system is associated with a clinician.

[0036] At step 208, the infusion system displays a patient note control element. The patient note control element may be displayed on a graphical user interface associated with the infusion system. The patient note control element controls activation of a patient note mode allowing for adding entries to the patient’s EMR. Activation of the patient note control element may include interacting with a portion of the graphical user interface (e.g., graphical control element) or pressing a physical button (e.g., a softkey) associated with the patient note mode.

[0037] At step 210, the infusion system determines whether the patient note control element is activated. The patient note control element is activated when selected, for example, by a clinician using a button on the infusion system, selecting on the user interface of the infusion system, issuing a voice command (e.g., “Infusion Helper, please take a patient note”), or the like.

[0038] If the patient note control element is not activated, then workflow 200 proceeds to step 212 with determining whether the infusion device association with the patient and clinician are active. The patient note control element may be associated with a time-out, whereby the patient note control element becomes inactivated after expiration of a timer, thereby increasing security and privacy of the EMR entries. In some cases, the patient note control element is not activated when the clinician is not authorized to access the patient note mode, for example, where the clinician is not on a list of authorized clinicians.

[0039] If the association with the patient and the clinician is active, then workflow 200 returns to step 208 with displaying the patient note control element.

[0040] If the association with the patient and the clinician is not active, then the infusion device, at step 214 of workflow 200, terminates display of the patient note control element. The termination ensures that, because the infusion system is not associated with a patient or a clinician, a note will not be submitting missing either an identifier for the patient or the clinician. Workflow 200 then terminates at step 218.

[0041] If the patient note control element is activated at step 210 of workflow 200, then workflow proceeds to step 216 with activating the patient note mode.

[0042] Where a patient note mode is activated on the infusion system, for example through workflow 200, or another suitable workflow, the infusion system may utilize workflow 300 to facilitate entry of the patient note. In particular, FIG. 3 depicts an example workflow 300 for entering a patient note through a patient note mode.

[0043] Workflow 300 begins at step 302, for example, following activation of a patient note mode at step 216 in FIG. 2. Though certain aspects are discussed with respect to an infusion system allowing both preset notes and “free-form” text notes that are not preset, other workflows may similarly be used that support only preset notes, or only text notes that are not preset.

[0044] At step 304, such as if preset notes are supported, workflow 300 proceeds with determining whether one or more preset clinician notes (also called quick notes) are defined. Exemplary preset notes may include: “Patient awake;” “Patient denies needs;” or “Responsive and alert.” Preset notes may be defined by a manufacturer of the infusion system, for example, pre-programed on the infusion system. Preset notes may be defined by the hospital system and transmitted, for example, through the network, to the infusion system. Preset notes may be based on one or more of: a location of the infusion pump, a clinician type, a patient type, one or more infusion parameters, or the like. For example, the one or more preset notes for a physician may be different from the one or more preset notes for a nurse. As another example, the one or more preset notes for an infusion system in a neonatal intensive care unit may be different from the one or more preset notes for an infusion system in an adult intensive care unit. The preset notes may then be beneficially relevant to the patient, clinician, or location of the infusion system.

[0045] If one or more preset notes are defined, workflow 300 proceeds to step 306 with displaying a control element for at least one preset note of the one or more preset notes. An exemplary user interface displaying control elements for preset notes is depicted as user interface 456 in FIG. 4B. Workflow 300 may then proceed to step 308, such as if text notes are supported.

[0046] If one or more preset notes are not defined, workflow 300 may proceed directly to step 308. At step 308, workflow 300 proceeds with displaying a control element for a text note. An exemplary user interface displaying a control element for a text note, but not for preset notes, is depicted as user interface 406 in FIG. 4A.

[0047] At step 310, workflow 300 proceeds with displaying a control element for exiting the patient note mode, which was activated at step 216 of workflow 200.

[0048] At step 312, such as if preset notes are supported, workflow 300 proceeds with determining whether one control element of the one or more preset notes control elements is selected by a user. A user may make a selection of a control element by, for example, pressing a button on the infusion system controller or selecting a preset note on the user interface of the infusion system controller.

[0049] If, at step 312, one of the one or more preset notes control elements is selected, then workflow 300 proceeds to step 314 with generating a message based on the preset note. Workflow 300 then proceeds to step 320.

[0050] If, at step 312, one of the one or more preset notes control elements is not selected, then workflow 300 may proceed to step 316 with determining whether the text note control element is selected.

[0051] If, at step 316, the text note control element is selected, then workflow 300 proceeds to step 318 with receiving a free-form text entry message. In some embodiments, free-form text entry message is generated by a user inputting text using a keyboard, for example, a keyboard on a user interface, or one or more buttons on the infusion system. In some embodiments, a free-form text entry message is generated based on receiving speech-to-text. Workflow 300 proceeds to step 320.

[0052] If, at step 316, the text note control element is not selected, then workflow 300 proceeds to step 324.

[0053] At step 320, workflow 300 proceeds with displaying a control element for submitting the patient note, whether the patient note is generated based on a preset note or a free-form text entry.

[0054] Workflow 300 proceeds to step 322 with determining whether the control element for submitting the patient note is selected. If, at step 322, the control element for submitting the patient note is selected, then workflow 300 proceeds to step 326 with generating the patient note.

[0055] Information is then sent to the EMR based on selecting the submit control element to add an entry to the EMR. The information includes the patient note. In some embodiments, forexample, where text entry was received at step 318, the patient note includes the free-form text entry. In some embodiments, for example, where one of the preset note control elements was selected at step 312, the patient note includes the preset note.

[0056] In some embodiments, the information further comprises an identifier of the clinician currently associated with the infusion system. In some embodiments, the information additionally or alternatively comprises an identifier of the patient currently associated with the infusion system. The inclusion of the clinician identifier or patient identifier is performed automatically (e.g., without user input during the note taking), relying on the current association between the infusion system, patient, and clinician (e.g., an association established during prior initialization of the infusion system). In some embodiments, the information additionally or alternatively comprises at least one of: a time stamp of when the user input was received (e.g., selection of a preset note control element or free-form text entry received), an identifier associated with the infusion pump controller, or a location of the infusion pump controller. The patient note may be formatted to conform with a standardized electronic medical messaging format such as HT7 Clinical Note or similar. The patient note may be formatted according to a proprietary standard such as a well- defined XML or JSON format.

[0057] If, at step 322, the control element for submitting the patient note is not selected, then workflow 300 proceeds to step 324 with determining whether the control element for exiting the patient note mode is selected.

[0058] If, at step 324, the control element for exiting the patient note model is not selected, then workflow 300 returns to step 312.

[0059] If, step 324, the control element for exiting the patient note model is selected, then workflow 300 proceeds to step 328 with exiting the patient note mode. Exiting patient note mode may include adjusting a graphical user interface of the infusion system to remove control elements associated with inputting a patient note. Exiting patient note mode may include adjusting a function associated with a softkey from patient note taking function to a more general infusion system function (e.g., view status, adjust infusion, channel select, pause infusion, etc.). Workflow 300 terminates at step 330.

[0060] Note that workflows 200 and 300 are just examples, and other flows including fewer, additional, or alternative steps, consistent with this disclosure, are possible. As discussed, a control element described in FIG. 3 may include a physical button or an element shown on a graphical user interface that can be activated or mapped to a physical button (e.g., a softkey). Activation of the control element may include interacting with a portion of the graphical user interface (e.g.,buton) or pressing a physical buton (e.g., a softkey) to cause the transmission of a message indicating the interaction with the control element.Example Infusion System User Interfaces

[0061] FIGS. 4A-4B and 5 depict example user interfaces of an infusion system performing aspects of workflows 200 and 300, described with respect to FIGS. 2 and 3. In particular, FIG. 4 A depicts an example flow 400 of an infusion system user interface for adding entries to an EMR via a free-form text message.

[0062] Initially, the infusion system user interface 402 displays a patient association control element 412, such as to associate a patient with the infusion system, as described with respect to step 202 of FIG. 2. A clinician may interact with the infusion system user interface, for example through one or more buttons, on-screen selections, and the like, to enter patient details. Note that prior to associating with a patient, the infusion system user interface 402 does not include a patient note control element.

[0063] Once associated with a patient, the infusion system user interface 404 displays a patient note control element 414, such as to activate a patient note mode, as described with respect to step 216 of FIG. 2.

[0064] In the patient note mode, the infusion system user interface 406 displays an element 416 for free-form text entry, such as to facilitate reception of the free-form text entry message, as described with respect to step 318 of FIG. 3. In the depicted example, the free-form text entry includes “Complaining of cold feet. Put socks on both feet.” As described herein, the entry need not be related to the infusion system, but rather the infusion system beneficially is configured as an EMR data entry terminal, allowing for convenient entry of notes to a patient’s electronic medical record.

[0065] Although depicted here as a QWERTY keyboard 426, other keyboards may be used to facilitate efficient text entry such as a telephone keypad. Further, a speech-to-text control element may be configured to receive speech, such as through a microphone, and convert the speech to a free-form text entry. Other suitable methods of entering free-form text may also be used.

[0066] The patient note may be submited, for example, by selection of submit note element 436. Submitting the note may transmit a formatted message including the note, patient identifier, and clinician identifier, from the infusion system to the EMR system or server. The transmission may be direct or via an intermediate system such as via an infusion system communication gateway. After submission of the patient note, the infusion system user interface 408 has exitedpatient note mode, such as when a control element for exiting the patient note mode (not depicted) is selected, as described with respect to step 324 of FIG. 3.

[0067] FIG. 4B depicts an example flow 450 of the infusion system user interface for adding entries to the EMR via one or more preset notes.

[0068] User interface 452 and user interface 454 may operate as described with respect to user interfaces 402 and 404 described in FIG. 4A.

[0069] However, in flow 450, in the patient note mode, the infusion system user interface 456 displays a preset element 466 comprising one or more preset notes, depicted here as Quick Notes 1-5. As described with respect to steps 304-306 of FIG. 3, the preset element 466 may be displayed where one or more preset notes are defined and then may be displayed. Beneficially, these one or more preset notes may be commonly used notes, such that a clinician may presently document commonly used notes without needing to take time to type out such a note.

[0070] The infusion system user interface 458 displays a selection of Quick Note 3 for submission of the patient note. Quick notes may be defined per user, per user role (e.g., nurse, head nurse, doctor), per care area, per facility, or combinations thereof.

[0071] FIG. 5 depicts another exemplary flow 500 of the infusion system user interface for adding entries to the EMR, beneficially; flow 500 depicts aspects of both free-form text and preset entry.

[0072] User interface 502 displays multiple control elements, including an EMR note control element 512. After selection of the EMR note control element 512, patient note mode is activated, for example as described at step 216 of FIG. 2.

[0073] User interface 504 displays a text note control element 514, as well as control elements associated with Quick Notes 01-04. In the depicted example, a timestamp 524 is also depicted and may be associated with the entry.

[0074] User interface 506 displays a free-form text entry 516, as well as a QWERTY keyboard 526 to facilitate entry.

[0075] In some embodiments, a preset note control element may control entry of a text entry template, for example, “Heart rate at > BPM.” Selection of the preset note 510 may allow for subsequent addendum, in this example, to enter the patient’s heart rate. This allows for improved usability of the user interface, while also allowing for additional text entry.

[0076] User interface 508 depicts the patient note 518, the optional associated timestamp 524, and control elements for exiting the patient note mode 528 or submitting the patient note 538. When the patient submission control element 538 is selected, the patient note is generated andsent to the EMR, such as described with respect to step 322 in FIG. 3. When the exit control element 528 is selected, the user interface exits the patient note mode, such as described with respect to step 328 in FIG. 3.Example Method of Adding Entries to an Electronic Medical Record

[0077] FIG. 6 depicts an example method 600 of adding entries to an electronic medical record using an infusion pump controller configured to control an infusion pump configured to deliver fluid to a patient.

[0078] Initially method 600 begins at step 602 with associating the infusion pump controller with the patient. In some embodiments, associating the infusion pump controller with the patient comprises receiving a patient identifier of the patient; and associating the patient identifier of the patient with the infusion pump controller.

[0079] Method 600 proceeds to step 604 with receiving, on the infusion pump controller, user input corresponding to a patient note. In some embodiments, the user input comprises free-form text input.

[0080] Method 600 then proceeds to step 606 with sending, to the electronic medical record, information for adding an entry to the electronic medical record, the information comprising the patient note. In some embodiments, sending the information from the infusion pump controller to the electronic medical record comprises sending the information from the infusion pump controller to the electronic medical record via one or more additional devices. In some embodiments, sending the information from the infusion pump controller to the electronic medical record comprises sending the information directly from the infusion pump controller to the electronic medical record.

[0081] In some embodiments, the information further comprises a patient identifier of the patient. In some embodiments, the information further comprises at least one of: a time stamp of receipt of the user input, an identifier associated with the infusion pump controller, or a location of the infusion pump controller.

[0082] In some embodiments, method 600 further comprises receiving, on the infusion pump controller, a second user input indicating to initiate a patient note mode of the infusion pump controller; and displaying, in the patient note mode, on the infusion pump controller, one or more user interface elements, wherein: the one or more user interface elements are configured to receive the user input; or the one or more user interface elements are associated with one or more buttons configured to receive the user input.

[0083] In some embodiments, method 600 further comprises receiving, on the infusion pump controller, a third user input indicating to initiate a patient note mode of the infusion pump controller; identifying, based on at least one of: a location of the infusion pump, a patient identifier of the patient; or a clinician identifier of a clinician, a preset patient note user interface element; and displaying, in the patient note mode, on the infusion pump controller, one or more user interface elements including the preset patient note user interface element.

[0084] In some embodiments, method 600 further comprises determining the infusion pump controller is not associated with any clinician; disabling receipt of the user input corresponding to the patient note; receiving a clinician identifier of a clinician to associate with the infusion pump controller; and enabling receipt of the user input corresponding to the patient note. In some embodiments, the clinician identifier of the clinician is received via a badge scanner.

[0085] In some embodiments, method 600 further comprises displaying, on the infusion pump controller, one or more preset notes, wherein the user input comprises selection of at least one of the one or more preset notes.

[0086] In some embodiments, method 600 further comprises receiving, on the infusion pump controller, a fourth user input indicating to exit the patient note mode of the infusion pump controller; and in response to the fourth user input, stop displaying the one or more user interface elements associated with the user input.

[0087] In some embodiments, method 600 further comprises determining the infusion pump controller is not associated with the patient; disabling receipt of the user input corresponding to the patient note; receiving a patient identifier of the patient to associate with the infusion pump controller; and enabling receipt of the user input corresponding to the patient note.

[0088] In some embodiments, method 600 further comprises presenting, on a touchscreen display associated with the infusion pump controller, graphical control elements; and receiving, via the touchscreen display associated with the infusion pump controller, user inputs including the user input.

[0089] Note that method 600 is just one example, and other methods including fewer, additional, or alternative steps, consistent with this disclosure, are possible.Example Computing Device

[0090] FIG. 7 depicts an example computing device 700, such as a medical device, that implements various features and processes described herein, such as infusion system 102 in FIG. 1. For example, the computing device 700 may perform one or more steps of any of flows 200-300 or method 600. The computing device 700 may include one or more processors 704, oneor more memories 706, one or more input components 710, one or more output components 712, and one or more communication interfaces 708. Each of these components may be coupled by a bus 702.

[0091] Computing device 700 may perform these processes based on one or more processors 704 executing software instructions stored by a computer-readable medium, such as one or more memories 706. In certain embodiments, one or more processors 704 may be programmed / designed / configured to perform these processes. A computer-readable medium (e.g., a non-transitory computer-readable medium) is defined herein as a non-transitory memory device. A memory device includes memory space located inside of a single physical storage device or memory space spread across multiple physical storage devices. Software instructions may be read into one or more memories from another computer-readable medium or from another device via communication interface 708. When executed, software instructions stored in one or more memories may cause one or more processors 704 to perform one or more processes described herein.

[0092] A memory 706 may include data storage or one or more data structures (e.g., a database, etc.). Computing device 700 may be capable of receiving information from, storing information in, communicating information to, or searching information stored in the data storage or one or more data structures in one or more memories 706.

[0093] A memory 706 may include random access memory (RAM), read only memory (ROM), and / or other types of dynamic or static storage devices (e.g., flash memory, magnetic memory, optical memory, etc.), that stores information and / or instructions for use by one or more processors 704. For example, a memory 706 may include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magnetooptical disks; and CD-ROM and DVD-ROM disks.

[0094] One or more memories 706 may include a message component 714 configured to send and receive information from an EMR, for example, for adding entries to the EMR. Message component may be configured to perform operations, for example, step 326 in FIG. 3 or step 606 in FIG. 6.

[0095] One or more memories 706 may include a patient note component 716 configured to receive user input corresponding to a patient note, for example, step 604 in FIG. 6. Patient note component 716 may be further configured to perform operations for activating a patient note mode, facilitating user input, managing preset note data 720, and / or the like.

[0096] One or more memories 706 may include an association component 718 configured to associate the infusion system with the EMR, for example, by associating the infusion pump with the patient. Association component 718 is further configured to associate the infusion pump with the clinician.

[0097] One or more processors 704 may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), etc.), a microprocessor, a digital signal processor (DSP), and / or any processing component (e.g., a field- programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.), that may be programmed to perform a function, such as described herein.

[0098] One or more input components 710 may include a component that permits computing device 700 to receive information, such as via user input (e.g., a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, a microphone, etc.). Further, one or more input components 710 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.).

[0099] One or more output components 712 may include a component that provides output information from computing device 700 (e.g., a display, a speaker, one or more light-emitting diodes (LEDs), etc.).

[0100] Communication interface 708 may include a transceiver-like component (e.g., a transceiver, a separate receiver and transmitter, etc.) that enables computing device 700 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface 708 may permit computing device 700 to receive information from another device and / or provide information to another device. For example, communication interface 708 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, and / or the like.Example Clauses

[0101] Implementation examples are described in the following numbered clauses:

[0102] Clause 1 : A method of adding entries to an electronic medical record using an infusion pump controller configured to control an infusion pump configured to deliver fluid to a patient, comprising: associating the infusion pump controller with the patient; receiving, on the infusion pump controller, user input corresponding to a patient note; and sending, to the electronic medicalrecord, information for adding an entry to the electronic medical record, the information comprising the patient note.

[0103] Clause 2: The method of clause 1, further comprising: determining the infusion pump controller is not associated with any clinician; disabling receipt of the user input corresponding to the patient note; receiving a clinician identifier of a clinician to associate with the infusion pump controller; and enabling receipt of the user input corresponding to the patient note.

[0104] Clause 3 : The method of clause 2, wherein the clinician identifier of the clinician is received via a badge scanner.

[0105] Clause 4: The method of any one of clauses 1-4, wherein the information further comprises a patient identifier of the patient.

[0106] Clause 5 : The method of any one of clauses 1 -4, wherein the user input comprises freeform text input.

[0107] Clause 6: The method of any one of clauses 1-5, further comprising: displaying, on the infusion pump controller, one or more preset notes, wherein the user input comprises selection of at least one of the one or more preset notes.

[0108] Clause 7: The method of any one of clauses 1-6, wherein the information further comprises at least one of: a time stamp of receipt of the user input, an identifier associated with the infusion pump controller, or a location of the infusion pump controller.

[0109] Clause 8: The method of any one of clauses 1-7, further comprising, prior to receipt of the user input: receiving, on the infusion pump controller, a second user input indicating to initiate a patient note mode of the infusion pump controller; and displaying, in the patient note mode, on the infusion pump controller, one or more user interface elements, wherein: the one or more user interface elements are configured to receive the user input; or the one or more user interface elements are associated with one or more buttons configured to receive the user input.

[0110] Clause 9: The method of clause 8, further comprising: receiving, on the infusion pump controller, a third user input indicating to initiate a patient note mode of the infusion pump controller; identifying, based on at least one of: a location of the infusion pump, a patient identifier of the patient; or a clinician identifier of a clinician, a preset patient note user interface element; and displaying, in the patient note mode, on the infusion pump controller, one or more user interface elements including the preset patient note user interface element.

[0111] Clause 10: The method of any one of clauses 1-9, wherein associating the infusion pump controller with the patient comprises: receiving a patient identifier of the patient; and associating the patient identifier of the patient with the infusion pump controller.

[0112] Clause 11 : The method of any one of clauses 1-10, further comprising: determining the infusion pump controller is not associated with the patient; disabling receipt of the user input corresponding to the patient note; receiving a patient identifier of the patient to associate with the infusion pump controller; and enabling receipt of the user input corresponding to the patient note.

[0113] Clause 12: The method of any one of clauses 1-11, further comprising: presenting, on a touchscreen display associated with the infusion pump controller, graphical control elements; and receiving, via the touchscreen display associated with the infusion pump controller, user inputs including the user input.

[0114] Clause 13: A processing system, comprising a memory (e.g., comprising computerexecutable instructions); and a processor configured to (e.g., execute the computer-executable instructions and) cause the processing system to perform a method in accordance with any one of clauses 1-12.

[0115] Clause 14: A processing system, comprising means for performing a method in accordance with any one of clauses 1-12.

[0116] Clause 15: A non-transitory computer-readable medium storing program code for causing an infusion system to perform the steps of any one of clauses 1-12.

[0117] Clause 16: A computer program product embodied on a computer-readable storage medium comprising code for performing a method in accordance with any one of clauses 1-12.

[0118] Clause 17: An infusion system, comprising: an infusion pump and an infusion pump controller, comprising: a memory (e.g., comprising computer-executable instructions); and a processor configured to (e.g., execute the computer-executable instructions and) cause the infusion system to perform a method in accordance with any one of clauses 1-12.Additional Considerations

[0119] The preceding description is provided to enable any person skilled in the art to practice the various embodiments described herein. The examples discussed herein are not limiting of the scope, applicability, or embodiments set forth in the claims. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments. For example, changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For instance, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may beimplemented or a method may be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover such an apparatus or method that is practiced using other structure, functionality, or structure and functionality in addition to, or other than, the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0120] As used herein, the word “exemplary” means “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0121] As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c). Reference to an element in the singular is not intended to mean only one unless specifically so stated, but rather “one or more.” For example, reference to an element (e.g., “a processor,” “a memory,” etc.), unless otherwise specifically stated, should be understood to refer to one or more elements (e.g., “one or more processors,” “one or more memories,” etc.). The terms “set” and “group” are intended to include one or more elements, and may be used interchangeably with “one or more.” Where reference is made to one or more elements performing functions (e.g., steps of a method), one element may perform all functions, or more than one element may collectively perform the functions. When more than one element collectively performs the functions, each function need not be performed by each of those elements (e.g., different functions may be performed by different elements) and / or each function need not be performed in whole by only one element (e.g., different elements may perform different sub-functions of a function). Similarly, where reference is made to one or more elements configured to cause another element (e.g., an apparatus) to perform functions, one element may be configured to cause the other element to perform all functions, or more than one element may collectively be configured to cause the other element to perform the functions. Unless specifically stated otherwise, the term “some” refers to one or more.

[0122] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure), ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information), accessing (e.g.,accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.

[0123] The methods disclosed herein comprise one or more steps or actions for achieving the methods. The method steps and / or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims. Further, the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and / or software component(s) and / or module(s), including, but not limited to a circuit, an application specific integrated circuit (ASIC), or processor. Generally, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components with similar numbering.

[0124] The following claims are not intended to be limited to the embodiments shown herein, but are to be accorded the full scope consistent with the language of the claims. Within a claim, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. No claim element is to be construed under the provisions of 35 U.S.C. §112(f) unless the element is expressly recited using the phrase “means for” or, in the case of a method claim, the element is recited using the phrase “step for.” All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Claims

CLAIMS1. An infusion system, comprising: an infusion pump configured to deliver fluid to a patient; and an infusion pump controller configured to: control the infusion pump; associate the infusion pump controller with the patient; receive, on the infusion pump controller, user input corresponding to a patient note; and send, to an electronic medical record, information for adding an entry to the electronic medical record, the information comprising the patient note.

2. The infusion system of claim 1, wherein the infusion pump controller is further configured to: determine that the infusion pump controller is not associated with a clinician; disable receipt of the user input corresponding to the patient note; receive identifying clinician identifier of a clinician to associate with the infusion pump controller; and enable receipt of the user input corresponding to the patient note.

3. The infusion system of claim 2, wherein the infusion pump controller includes a badge scanner, and wherein the infusion pump controller is configured to receive the clinician identifier of the clinician via the badge scanner.

4. The infusion system of any one of claims 1-3, wherein the information further comprises a patient identifier of the patient.

5. The infusion system of any one of claims 1-4, wherein the user input comprises free-form text input.

6. The infusion system of any one of claims 1 -4, wherein the infusion pump controller is further configured to: display, on the infusion pump controller, one or more preset notes, wherein the user input comprises selection of at least one of the one or more preset notes.

7. The infusion system of any one of claims 1-6, wherein the information further comprises at least one of: a time stamp of receipt of the user input, an identifier associated with the infusion pump controller, or a location of the infusion pump controller.

8. The infusion system of any one of claims 1 -7, wherein the infusion pump controller is further configured to, prior to receipt of the user input:receive, on the infusion pump controller, a second user input indicating to initiate a patient note mode of the infusion pump controller; and display, in the patient note mode, on the infusion pump controller, one or more user interface elements, wherein: the one or more user interface elements are configured to receive the user input; or the one or more user interface elements are associated with one or more buttons configured to receive the user input.

9. The infusion system of any one of claims 1 -8, wherein the infusion pump controller is further configured to, prior to receipt of the user input: receive, on the infusion pump controller, a third user input indicating to initiate a patient note mode of the infusion pump controller; identify, based on at least one of: a location of the infusion system, a patient identifier of the patient, or a clinician identifier of a clinician, a preset patient note user interface element; and display, in the patient note mode, on the infusion pump controller, one or more user interface elements including the preset patient note user interface element.

10. The infusion system of any one of claims 1-9, wherein to associate the infusion pump controller with the patient, the infusion pump controller is configured to: receive a patient identifier of the patient; and associate the patient identifier of the patient with the infusion pump controller.

11. The infusion system of any one of claims 1-10, wherein the infusion pump controller is further configured to: determine that the infusion pump controller is not associated with the patient; disable receipt of the user input corresponding to the patient note; receive a patient identifier of the patient to associate with the infusion pump controller; and enable receipt of the user input corresponding to the patient note.

12. The infusion system of any one of claims 1-11, further comprising: a touchscreen display associated with the infusion pump controller, the touchscreen display configured to present graphical control elements and receive user inputs including the user input.

13. A method of adding entries to an electronic medical record using an infusion pump controller configured to control an infusion pump configured to deliver fluid to a patient, comprising: associating the infusion pump controller with the patient; receiving, on the infusion pump controller, user input corresponding to a patient note; and sending, to the electronic medical record, information for adding an entry to the electronic medical record, the information comprising the patient note.

14. The method of claim 13, further comprising: determining the infusion pump controller is not associated with any clinician; disabling receipt of the user input corresponding to the patient note; receiving a clinician identifier of a clinician to associate with the infusion pump controller; and enabling receipt of the user input corresponding to the patient note.

15. The method of claim 14, wherein the clinician identifier of the clinician is received via a badge scanner.

16. The method of any one of claims 13-15, wherein the information further comprises a patient identifier of the patient.

17. The method of any one of claims 13-16, wherein the user input comprises freeform text input.

18. The method of any one of claims 13-16, further comprising: displaying, on the infusion pump controller, one or more preset notes, wherein the user input comprises selection of at least one of the one or more preset notes.

19. The method of any one of claims 13-18, wherein the information further comprises at least one of: a time stamp of receipt of the user input , an identifier associated with the infusion pump controller, or a location of the infusion pump controller.

20. The method of any one of claims 13-19, further comprising, prior to receipt of the user input: receiving, on the infusion pump controller, a second user input indicating to initiate a patient note mode of the infusion pump controller; and displaying, in the patient note mode, on the infusion pump controller, one or more user interface elements, wherein:the one or more user interface elements are configured to receive the user input; or the one or more user interface elements are associated with one or more buttons configured to receive the user input.

21. The method of any one of claims 13-20, further comprising: receiving, on the infusion pump controller, a third user input indicating to initiate a patient note mode of the infusion pump controller; identifying, based on at least one of: a location of the infusion pump, a patient identifier of the patient; or a clinician identifier of a clinician, a preset patient note user interface element; and displaying, in the patient note mode, on the infusion pump controller, one or more user interface elements including the preset patient note user interface element.

22. The method of any one of claims 13-21, wherein associating the infusion pump controller with the patient comprises: receiving a patient identifier of the patient; and associating the patient identifier of the patient with the infusion pump controller.

23. The method of any one of claims 13-22, further comprising: determining the infusion pump controller is not associated with the patient; disabling receipt of the user input corresponding to the patient note; receiving a patient identifier of the patient to associate with the infusion pump controller; and enabling receipt of the user input corresponding to the patient note.

24. The method of any one of claims 13-23, further comprising: presenting, on a touchscreen display associated with the infusion pump controller, graphical control elements; and receiving, via the touchscreen display associated with the infusion pump controller, user inputs including the user input.

25. A non-transitory computer-readable medium storing program code for causing an infusion system to add entries to an electronic medical record using an infusion pump controller configured to control an infusion pump configured to deliver fluid to a patient, by performing operations comprising: associating the infusion pump controller with the patient;receiving, on the infusion pump controller, user input corresponding to a patient note; and sending, to the electronic medical record, information for adding an entry to the electronic medical record, the information comprising the patient note.

26. The non-transitory computer-readable medium of claim 25, wherein the operations further comprise: determining the infusion pump controller is not associated with any clinician; disabling receipt of the user input corresponding to the patient note; receiving a clinician identifier of a clinician to associate with the infusion pump controller; and enabling receipt of the user input corresponding to the patient note.

27. The non-transitory computer-readable medium of claim 26, wherein the clinician identifier of the clinician is received via a badge scanner.

28. The non-transitory computer-readable medium of any one of claims 25-27, wherein the information further comprises a patient identifier of the patient.

29. The non-transitory computer-readable medium of any one of claims 25-28, wherein the user input comprises free-form text input.

30. The non-transitory computer-readable medium of any one of claims 25-29, wherein the operations further comprise: displaying, on the infusion pump controller, one or more preset notes, wherein the user input comprises selection of at least one of the one or more preset notes.

31. The non-transitory computer-readable medium of any one of claims 25-30 wherein the information further comprises at least one of: a time stamp of receipt of the user input, an identifier associated with the infusion pump controller, or a location of the infusion pump controller.

32. The non-transitory computer-readable medium of any one of claims 25-31, wherein, prior to receipt of the user input, the operations further comprise: receiving, on the infusion pump controller, a second user input indicating to initiate a patient note mode of the infusion pump controller; and displaying, in the patient note mode, on the infusion pump controller, one or more user interface elements, wherein: the one or more user interface elements are configured to receive the user input; orthe one or more user interface elements are associated with one or more buttons configured to receive the user input.

33. The non-transitory computer-readable medium of any one of claims 25-32, wherein the operations further comprise: receiving, on the infusion pump controller, a third user input indicating to initiate a patient note mode of the infusion pump controller; identifying, based on at least one of: a location of the infusion pump, a patient identifier of the patient; or a clinician identifier of a clinician, a preset patient note user interface element; and displaying, in the patient note mode, on the infusion pump controller, one or more user interface elements including the preset note user interface element.

34. The non-transitory computer-readable medium of any one of claims 25-33, wherein associating the infusion pump controller with the patient comprises: receiving a patient identifier of the patient; and associating the patient identifier of the patient with the infusion pump controller.

35. The non-transitory computer-readable medium of any one of claims 25-34, wherein the operations further comprise: determining the infusion pump controller is not associated with the patient; disabling receipt of the user input corresponding to the patient note; receiving a patient identifier of the patient to associate with the infusion pump controller; and enabling receipt of the user input corresponding to the patient note.

36. The non-transitory computer-readable medium of any one of claims 25-35, wherein the operations further comprise: presenting, on a touchscreen display associated with the infusion pump controller, graphical control elements; and receiving, via the touchscreen display associated with the infusion pump controller, user inputs including the user input.

Images