JP7471610B2 - Medical Pump Management System - Google Patents

Description

This invention relates to a medical pump management system, and more specifically, to a computer system for the operation and management of medical pump devices in a medical institution that operates multiple medical pump devices.

In hospitals and other medical institutions, when injecting (supplying) a set amount of medicinal liquid to a patient over a period of time, medical pump devices such as infusion pumps and syringe pumps that have a mechanism for mechanically assisting the supply of medicinal liquid are used.

As is well known, various types of medical pump devices have been proposed, including a type that uses a mechanical mechanism to squeeze a tube containing a medicinal liquid (a so-called finger-type infusion pump), a type that controls the number of drops of medicinal liquid in a drip tube (a drop-number-control type infusion pump), a type that controls the flow rate of the delivered liquid (a flow-rate-control type infusion pump), and a type that controls the movement of the inner tube of a syringe to which an outer tube is fixed (a syringe pump). In recent years, all types of devices have been equipped with various sensors, and based on the information obtained by these sensors, the control unit of the medical pump device detects abnormalities such as running out of liquid (insufficient remaining amount), liquid clogging (blockage of the liquid delivery tube), and liquid leakage (abnormal flow rate). When an abnormality is detected, a specified warning operation is performed, such as sounding an alarm, to notify staff such as nurses that an abnormality has occurred in the medical pump device (see, for example, Patent Document 1).

JP 2011-200326 A

However, such a conventional method has the following problems.
(1) Conventional medical pump devices use an alarm generator provided on the device body to notify the outside of the device of an abnormality. For example, when a liquid runs out, an alarm sounds in the patient's room (more specifically, near the patient's bed), and a nurse must either hear the alarm leaking from the patient's room and head to the patient's room, or the patient must call the nurse after hearing the alarm, and head to the patient's room to confirm that the liquid in the medical pump device has run out and take action (for example, by replacing the medicinal liquid). As a result, there has been a tendency for the response to device abnormalities to be delayed.

(2) In recent years, medical pump devices have been provided that are configured to issue a preliminary warning (forecast) before the liquid runs out by, for example, monitoring the flow rate of the liquid using a sensor installed in the device. However, the timing at which a forecast is necessary varies depending on the circumstances under which the medical pump device is operated (for example, the ratio of patients to nurses, the size of the ward or room, the type of liquid (importance/urgency), time of day, etc.), making it difficult to respond in a detailed manner according to the operating circumstances of the medical pump device using only the uniform forecast function installed in the medical pump device.

The present invention was made in consideration of these problems, and its purpose is to provide a medical pump management system that can efficiently and accurately identify medical pump devices that require action depending on the operating situation.

In order to achieve the above object, the medical pump management system according to the present invention comprises:
a plurality of medical pump devices for supplying fluid to a patient;
A pump management server communicatively connected to the medical pump device;
In a medical pump management system including a medical support system communicatively connected to the pump management server,
The medical pump device is configured to output pump status information indicating a status of the medical pump device periodically and when an event occurs,
The pump management server includes a database and a control device,
The database includes a patient-pump correspondence table that stores, for a patient receiving liquid from the medical pump device, a patient and the medical pump device in association with each other using patient ID information that identifies the patient and pump ID information that identifies the medical pump device;
a pump status record table for storing pump status information transmitted periodically and when an event occurs from the medical pump device for each medical pump device;
a prediction condition recording table that stores a prediction issuance condition set for each of the medical pump devices,
the control device is provided with a control configuration for determining, for each of the medical pump devices, whether or not each of the medical pump devices satisfies a preset forecast issuance condition based on the pump status information and the forecast issuance condition stored in the database, and when it is determined that the forecast issuance condition is satisfied, transmitting a forecast issuance command to the medical support system, the forecast issuance command including forecast type information indicating the content of the forecast issuance condition, and pump ID information of the medical pump device and/or patient ID information associated with the pump ID information ;
The condition for issuing the forecast is a grace period until the liquid in the medical pump device runs out,
The control device is configured to calculate a grace period until the liquid runs out based on a planned amount of liquid to be administered and a set flow rate included in the pump status information, and to determine whether or not a warning condition is satisfied.
It is characterized by:

The present invention has the following configuration as a preferred embodiment.
(1) The medical support system is characterized in that, when it receives the forecast issuance command transmitted from the control device, it is provided with an alarm means for alarming the forecast type information contained in the received forecast issuance command, the pump ID information of the medical pump device, and/or the patient ID information corresponding to the pump ID information of the medical pump device.

(2) The control device is characterized in that it has a destination setting means for setting a destination of the forecast issuance command, and when transmitting the forecast issuance command, it has a control configuration for converting the forecast issuance command into a data format readable by the medical support system set by the destination setting means and transmitting the converted data.

(3) The patient-pump correspondence table of the database stores the patient ID information in association with patient location information that identifies the location of the patient, and the control device is characterized in that it has a control configuration that, when transmitting the patient ID information to the medical support system, also transmits the patient location information associated with the patient ID information.

According to the present invention, the pump management server is configured to determine whether or not a pre-set forecast issuance condition is met for each medical pump device based on the pump status information and forecast issuance conditions stored in the database for each medical pump device, and when it determines that the conditions are met, to transmit a forecast issuance command including forecast type information indicating the content of the forecast issuance condition, and pump ID information of the medical pump device and/or patient ID information associated with the pump ID information of the medical pump device to a medical support system such as a nurse call system or an electronic medical record system. Therefore, the medical support system that receives the forecast issuance command can know which medical pump device (or which patient) has met which forecast issuance condition based on the information included in the forecast issuance command. Therefore, staff such as nurses who come into contact with this information can quickly take appropriate action according to the notified forecast type.

In addition, because the conditions for issuing a forecast are set for each medical pump device, for example, by changing the timing of issuing a forecast of fluid shortage depending on the distance from the nursing center, it is possible to give ample time between the issuance of the forecast of fluid shortage and responding to the situation (for example, by replacing the medicinal fluid), thereby reliably avoiding delays in response.

1 is a system configuration diagram showing an example of a schematic configuration of a medical pump management system according to the present invention. 2A and 2B show examples of events that cause pump status information to be output in a syringe pump. FIG. 2A shows an event during normal operation, and FIG. 2B shows an alarm event associated with the detection of an abnormality. 1 is a block diagram functionally illustrating an example of a schematic configuration of a pump management server in a medical pump management system according to the present invention. FIG. 11 is an explanatory diagram showing an example of a procedure for registering patient information using a nursing support system in the medical pump management system. FIG.

Embodiments of the present invention will now be described in detail with reference to the drawings. Note that the same reference numerals throughout the drawings denote the same components or elements.

FIG. 1 shows a schematic configuration of a medical pump management system 1 to which the present invention is applied.
The medical pump management system 1 is a system that supports the operation of medical pump devices 2 used in medical institutions such as hospitals, and comprises as its main components a plurality of medical pump devices 2 (in the illustrated example, 2a, 2b, 2c, ... 2x), a pump management server 3, and medical support systems (medical support systems) such as an electronic medical record system 4, a nursing support system 5, and a nurse call system 6, which are communicatively connected via a wired or wireless network N.

The medical pump device 2 is a device that supplies liquid such as a medicinal liquid to a patient, and examples of the device include an infusion pump and a syringe pump. A device that uses a mechanical mechanism to assist in the supply of liquid is preferably used as the medical pump device 2. The medical pump device 2 is also equipped with a control unit (not shown) that monitors the state of the device, and is configured to output pump status information (for example, various information indicating the state of the medical pump device 2, such as the presence or absence of fluid delivery, the planned administration amount, the set flow rate, the detected flow rate, etc., and information notifying the occurrence of a specified event) indicating the status (state) of the medical pump device 2 to the outside periodically (at regular intervals) and when a specified event occurs. The medical pump device 2 is connected to a network N for communication, and the pump status information can be received by the pump management server 3 via the network N.

Figure 2 shows an example of an output event of pump status information in a syringe pump, which is an example of a medical pump device 2. As shown in this figure, events that output pump status information are broadly divided into status notification events during normal operation (see Figure 2(a)) and alarm events when an alarm occurs (alarm is issued) (see Figure 2(b)).

In FIG. 2(a), examples of status notification events include "start of infusion", "start of fast forward", "start of bolus (HOB, HFB)", "start of KOR", "change in flow rate during infusion", "end of fast forward", "end of bolus (HOB, HFB)", "stop of infusion from infusion state", "clear accumulation", "power OFF", and "when drug library selection is confirmed". When these status notification events occur, pump status information notifying the occurrence of the event is output from the syringe pump to the network N.

In FIG. 2(b), examples of alarm events include "shutdown warning alarm", "linkage interruption alarm", "completion alarm", "occlusion alarm infusion pump downstream", "occlusion alarm up", "syringe disconnection alarm", "push disconnection alarm", "clutch disconnection alarm", "syringe detection alarm", "clip disconnection alarm", "infusion probe disconnection alarm", "free flow alarm", "empty liquid alarm", "abnormal flow rate alarm", "air bubble alarm", "door alarm", "remaining amount alarm", "notification before remaining amount setting time", "power supply abnormality alarm", "AC cable disconnection alarm", "flow rate not set alarm", "flow rate/scheduled amount large/small judgment alarm", "scheduled amount not set alarm", "low battery alarm", "start forgotten alarm", "occlusion precaution", "maintenance timer", and "battery replacement time/failure alarm". When the control unit detects any of these abnormalities, it generates an alarm event to notify the detected abnormality, and pump status information to notify the occurrence of the alarm is output from the syringe pump to the network N.

The pump status information includes the state of the medical pump device 2 and the type of event that occurred (the event types illustrated in FIG. 2), as well as information that identifies the medical pump device 2 (for example, the serial number of the medical pump device 2).

The pump management server 3 is a server computer whose main purpose is to support the operation of multiple medical pump devices 2, and as shown in FIG. 3, its main components include a database 31 and a control device 32.

The database 31 is a storage device that stores information necessary for operational support of the medical pump device 2. The database 31 has a patient-pump correspondence table 101 that uses patient ID information that identifies the patient and pump ID information that identifies the medical pump device 2, and stores at least a patient who receives liquid from the medical pump device 2 in association with the medical pump device 2, a pump status record table 102 that stores pump status information transmitted from the medical pump device 2 periodically and when an event occurs for each medical pump device 2, and a forecast condition record table 103 that stores forecast issuance conditions set for each medical pump device 2. In this embodiment, the patient-pump correspondence table 101 employs a configuration in which, when storing patient ID information, the patient ID information is associated with patient location information that identifies the location of the patient.

The patient ID information that identifies the patient is an individual ID that is set for each patient. For example, a character string that combines symbols and numbers is preferably used as the patient ID, but the patient's name, etc., can also be used as the patient ID. In this embodiment, the patient ID information is converted into a barcode and printed on a wristband worn by the patient, etc.

On the other hand, the pump ID information identifying the medical pump device 2 is an individual ID set for each medical pump device 2. For example, the manufacturing number (serial number) of the medical pump device 2 is preferably used as the pump ID information. The reason why the manufacturing number is preferably used is because the manufacturing number is often used as information identifying the device included in the pump status information output from the medical pump device 2. Therefore, when the medical pump device 2 is identified using information other than the manufacturing number in the pump status information, it is preferable to use the other information as the pump ID information.

Patient location information is information about the location where the patient is. For example, patient location information is information that allows nurses and other staff to easily identify the patient's location, such as which ward, which hospital room, and which hospital bed the patient is in.

The patient-pump correspondence table 101 is a data table that stores patient ID information and pump ID information received via the network N in a corresponding relationship. In this embodiment, as described below, patient ID information, patient location information, and pump ID information are transmitted from the nursing support system 5 in a corresponding relationship (details will be described later), and this corresponding information is stored in the patient-pump correspondence table 101.

The pump status record table 102 is a data table that stores, for each medical pump device 2, pump status information transmitted from the medical pump device 2 periodically and when an event occurs. The pump status record table 102 is configured to store pump status information so that at least the previous and current pump status information can be compared.

For example, when pump status information is transmitted from the syringe pump 2a in response to a status notification event "start of fluid delivery," the pump status record table 102 stores the information "start of fluid delivery" as the pump status information of the syringe pump 2a. Then, when the next pump status information is transmitted from the syringe pump 2a (for example, periodic pump status information is transmitted before the next status notification event occurs), the pump status information is stored in a different memory area from the previous one. In this way, the pump status record table 102 is configured to store pump status information transmitted one after another via the network N for each medical pump device 2 so that it can be compared with at least the previous information. Therefore, the control device 32 can detect a change in the status of the medical pump device 2 by comparing and referring to the pump status information stored in the pump status record table 102.

The forecast condition storage table 103 is a data table that stores forecast issuance conditions that are set for each medical pump device 2. The forecast issuance conditions are conditions for the occurrence of forecast events that are arbitrarily set by the user on the pump management server 3 side, separate from events that are set on the medical pump device 2 side (see, for example, the status notification event and alarm event shown in FIG. 2), and the control device 32 is configured to determine whether or not the forecast issuance conditions set for each medical pump device 2 are met (whether or not the conditions are met).

The control device 32 is a device that uses the data stored in the database 31 to support the operation of the medical pump device 2, and is configured as a computer that is either integrated with the database 31 or separate from it. As shown in FIG. 3, the control device 32 has, in terms of its functional configuration, a control means 201, a forecast condition setting means 202, a destination setting means 203, and a communication means 204.

The control means 201 includes a processor that executes software for supporting the operation of the medical pump device 2, and the execution of this software realizes the operation support of the medical pump device 2, which will be described later. The control means 201 also functions as a control means for input devices (such as a keyboard and a mouse) and display devices (such as a liquid crystal display device) that are provided in the control device 32 and are not shown.

The forecast condition setting means 202 is a means for setting (setting, canceling, changing, etc.) forecast issuance conditions that are set for each medical pump device 2. An input device provided in the control device 32 is preferably used as the forecast condition setting means 202, but for example, another terminal device (for example, a PC, tablet terminal, smartphone, etc. that constitutes a client terminal of the nursing support system 5) that is communicatively connected to the control device 32 via the network N may also be used as the forecast condition setting means 202.

The forecast issuance conditions set by the forecast condition setting means 202 can be set arbitrarily as long as the control means 201 can determine whether the conditions that are the premise for forecast issuance are met or not based on the information included in the pump status information stored in the pump status record table 102 (pump status information transmitted from the medical pump device 2). For example, if the pump status information includes the planned administration amount of the medicinal liquid and the set flow rate, the control means 201 can calculate the grace period until the liquid runs out based on this information, and the grace period until the liquid runs out can be set as the forecast issuance condition (for example, 5 minutes before the liquid runs out, 10 minutes before the liquid runs out, etc.).

The destination setting means 203 is a means for setting the destination of a forecast issuance command, which will be described later, in relation to operational support for the medical pump device 2. As the destination setting means 203, an input device provided in the control device 32 is preferably used, but similar to the forecast condition setting means 202, it is also possible to use another terminal device connected to the control device 32 via the network N as the destination setting means 203.

In this embodiment, as described below, the occurrence of an event related to the medical pump device 2 is notified to staff such as nurses via the nurse call system 6, so the nurse call system server 61 is set as the destination of the forecast report command. As a result, when the control means 201 of the control device 32 outputs a forecast report command, it converts the generated forecast report command into a data format readable by the destination, the nurse call system server 61, and transmits it.

In this embodiment, the destination setting means 203 also functions as a means for setting the destination of an alarm event issuance command, which will be described later, and the medical support system set as the destination of the forecast issuance command becomes the destination of the alarm event issuance command. Therefore, when the control means 201 of the control device 32 outputs an alarm event issuance command, the generated alarm event issuance command is converted into a data format readable by the nurse call system server 61 and transmitted.

The communication means 204 is a communication device that enables the control device 32 to communicate with the medical support system via the network N. Specifically, when the network N is configured as a local area network, the communication means 204 includes a network interface for communicatively connecting to the local area network.

A medical support system is a computer system that supports medical and nursing care procedures for patients (for example, medical examinations, medical treatments, tests, health checks, etc.), and in the example shown in Figure 1, an electronic medical record system 4, a nursing support system 5, and a nurse call system 6 are exemplified as this medical support system. Note that the medical support system is not limited to these exemplified systems, and may include systems other than the exemplified systems, such as an ordering system used to transmit order information for tests, drug prescriptions, etc., or conversely, the medical support system may be configured excluding some systems.

The electronic medical record system 4 is a computer system that provides computerized patient medical records (medical records) to client terminals, and FIG. 1 illustrates a server computer 41 that provides this electronic medical record system. The configuration of the electronic medical record system 4 is well known, so a detailed explanation will be omitted, but this electronic medical record system 4 makes it possible to view and edit medical records using client terminals located in examination rooms, nurse stations, etc.

The nursing support system 5 is a computer system that supports the work of staff such as nurses (for example, registering basic patient information, managing hospital beds, creating progress records, etc.), and FIG. 1 shows a server computer 51 that provides the nursing support system. The configuration of the nursing support system 5 is also well known, so a detailed explanation will be omitted, but in the nursing support system 5, a terminal that can be carried by a nurse or the like (for example, a tablet terminal or a smartphone) is preferably used as a client terminal. The reference numeral 300 indicates a smartphone that also functions as a client terminal for the nursing support system 5.

In this embodiment, the above-mentioned patient ID information, patient location information, and pump ID information are registered in the server 51 of the nursing support system 5 using this nursing support system 5.

Figure 4 shows an example of the registration procedure for patient ID information, patient location information, and pump ID information. In the illustrated example, the patient ID information and patient location information are printed in advance as barcodes on a wristband worn by the patient (barcode BC1). Also, the pump ID information is printed in advance as a barcode on a label to be affixed to the medical pump device 2 (barcode BC2).

In the nursing support system 5, the barcode BC1 on the patient's wristband is read using a client terminal (e.g., smartphone 300) (see step S1 in FIG. 4), and the patient ID information of the patient wearing the wristband is associated (linked) with the patient location information and registered in the server 51 (see step S2 in FIG. 4). Similarly, the nursing support system 5 uses a client terminal to read the barcode BC2 on the label attached to the medical pump device 2 (see step S3 in FIG. 4), and registers the pump ID information of the medical pump device 2. At this time, by reading the barcode BC2 with the patient identified in advance, the patient ID information of the identified patient can be associated with the read pump ID information and registered in the server 51 (see step 4 in FIG. 4).

The patient ID information, patient location information, and pump ID information registered in the server 51 in this manner are sent to the database 31 of the pump management server 3 (see step S5 in Figure 4) and stored in the patient-pump correspondence table 101 of the database 31. In other words, for patients who receive liquid from the medical pump device 2, the patient, the patient location, and the medical pump device 2 are associated and stored in the database 31. When a patient is admitted or discharged from the hospital, changes hospital room or bed, or the medical pump device 2 is replaced, the barcodes BC1 and BC2 are read each time, so that the information associated with the patient, patient location, and medical pump device 2 stored in the database 31 can always be kept up to date.

The nurse call system 6 is primarily a system for patients to call staff such as nurses, and FIG. 1 shows a server computer 61 that provides the nurse call system 6. As with other medical support systems, the configuration of the nurse call system 6 is well known, so a detailed explanation will be omitted, but the main components of the nurse call system 6 shown in this embodiment are a server 61 equipped with software that provides the service, controllers 62 that are placed in predetermined units such as each ward, and a terminal device 63 that serves as a means for notifying nurse calls.

The server 61 is a server computer that is connected to multiple controllers 62 via wired or wireless communication, and is configured to provide various services using the nurse call system 6, such as storing nurse call history sent from each controller 62 so that it can be viewed, and working with the pump management server 3 to notify the terminal device 63 of information related to the medical pump device 2.

The controller 62 is a device that forms an interface between the server 61 and the terminal device 63. In the illustrated example, the controller 62 is connected to a display device 400 such as an LCD panel, a terminal computer 500, a parent unit 600 for nurse call with a display function, and a wireless LAN access point 64 for using the smartphone 300 as the terminal device 63.

The nurse call master unit 600 is connected to multiple nurse call handsets (e.g. wall-embedded handsets with a call grip button) by wired or wireless communication, and by operating the call grip button of the nurse call handset, a nurse call is made via the nurse call master unit 600 to the display device 400, the terminal computer 500, the nurse call master unit 600, and further to the smartphone 300 via the access point 64. The display device 400, the terminal computer 500, and the nurse call master unit 600 shown in FIG. 1 are usually placed in a nurse's station where staff such as nurses are stationed. The smartphone 300 is carried by staff such as nurses working in the ward.

The terminal device 63 is a device that notifies the user of a call to the nurse call system 6. In this embodiment, the terminal device 63 is a device equipped with a screen capable of displaying characters and symbols so that the contents of the forecast issuance command, which will be described later, can be displayed. In the illustrated example, the display device 400, terminal computer 500, nurse call master unit 600, and smartphone 300 are shown as examples of the terminal device 63, but it goes without saying that the combination of these can be freely changed as appropriate.

The network N is a computer network that performs data communication. In this embodiment, the network N is configured as a local area network established within a medical institution such as a hospital in which the medical pump management system 1 is installed. In FIG. 1, the medical pump device 2, the pump management server 3, the electronic medical record system server 41, the nursing support system server 51, and the nurse call system server 61 are connected by a single network N, but these may also be configured to be connected by multiple networks.

Next, we will explain an example of operational support for the medical pump device 2 by the pump management server 3.

A: Issuance of an alarm event In the medical pump management system 1 of the present invention, when an alarm event occurs in the medical pump device 2 and pump status information notifying the occurrence of the alarm event is output from the medical pump device 2, the pump management server 3 which receives this pump status information notifies staff such as nurses of the occurrence of the alarm event via the nurse call system 6.

(1) For example, when an "empty liquid alarm" (alarm event) occurs in a syringe pump 2a supplying medicinal liquid to a patient, the syringe pump 2a in which the alarm event occurred outputs pump status information notifying the occurrence of the alarm event.

(2) The pump status information output to the network N is received and analyzed by the pump management server 3. The pump management server 3 uses the serial number (pump ID information) of the syringe pump 2a included in the received pump status information to identify the patient ID information associated with the syringe pump 2a in which the alarm event occurred and the location information of the patient, using the information stored in the patient-pump correspondence table 101 of the database 31.

(3) Once the syringe pump 2a in which the alarm event occurred and the patient ID information and patient location information associated with that syringe pump 2a have been identified in this manner, the control device 32 then generates an alarm event issuance command that includes information on the type of alarm event that occurred (information indicating that it is an "empty liquid alarm") and the patient ID information and patient location information associated with the syringe pump 2a in which the alarm event occurred, converts the generated alarm event issuance command into a data format that can be read by the nurse call system 6, and transmits it to the nurse call system server 61.

(4) When the nurse call system server 61 receives an alarm event issuance command from the pump management server 3 via the network N, it analyzes the received alarm event issuance command. By analyzing the received alarm event issuance command, the nurse call system server 61 identifies the type of alarm event that has occurred, as well as the patient ID information and patient location information associated with the syringe pump 2a in which the alarm event has occurred, and notifies staff such as nurses of this identified information using the functions of the nurse call system 6.

(5) That is, the nurse call system server 61 notifies staff such as nurses of the type of alarm event that has occurred (information indicating that it is an "empty liquid alarm"), the patient ID information, and the location information of the patient through the terminal device 63 of the nurse call system 6 (for example, by displaying the above information on the screen of the terminal device 63 or by having the terminal device 63 sound an alarm). This allows staff such as nurses to grasp, through the terminal device 63 (for example, the smartphone 300), almost simultaneously (instantly) with the occurrence of the alarm event, what type of alarm has occurred in which medical pump device 2 for which person in which bed in which room. This enables the alarm to be dealt with promptly.

When making this notification, for example, a table that associates patient ID information with patient names or patient information including the patient names (e.g., gender, age, etc.) may be provided in the pump management server 3 or the nurse call system server 61, etc., and the patient names, etc. may be notified along with or instead of the patient ID information. Also, a table that associates pump ID information with the type of medical pump device 2 (information that identifies the type of medical pump device 2, such as model name) may be provided in the pump management server 3 or the nurse call system server 61, etc., and information such as the model name may be identified from the pump ID information, and the type of medical pump device 2 may also be notified when the occurrence of the above alarm event is notified.

B: Issuance of a forecast event In the medical pump management system 1 of the present invention, in addition to the issuance of the alarm event described above, when the forecast issuance conditions that have been individually set in advance in the pump management server 3 for the medical pump device 2 are satisfied, the pump management server 3 generates a forecast issuance event and notifies staff such as nurses of the occurrence of the event via the nurse call system 6.

(1) For example, assume that the warning condition for a syringe pump 2a that is supplying liquid to a patient is set to "10 minutes before the liquid runs out."

(2) When the forecast issuance conditions are set in this manner, the control device 32 of the pump management server 3 monitors the pump status information of the syringe pump 2a for which the forecast issuance conditions are set, and determines whether the forecast issuance conditions are met.

Specifically, the pump status information of the syringe pump 2a is stored in the pump status record table 102 of the database 31, and the control device 32 monitors the pump status information of the syringe pump 2a stored in the pump status record table 102 to determine whether the forecast issuance conditions are met (conditions met/not met).

In this case, the forecast alert condition is set to "10 minutes before the liquid runs out," so the control device 32 reads pump status information (e.g., "planned administration amount" and "set flow rate") required to calculate the grace period until the liquid runs out from the pump status record table 102, and calculates the grace period until the liquid runs out. This calculation is repeated periodically until the forecast alert condition is met. Then, when the forecast alert condition is met as a result of this calculation, the control device 32 generates a forecast alert event for the syringe pump 2a.

(3) When generating a forecast alert event, the control device 32 uses the information stored in the patient-pump correspondence table 101 of the database 31 to identify the patient ID information associated with the syringe pump 2a for which a forecast alert event has occurred and the location information of the patient, based on the serial number (pump ID information) of the syringe pump 2a contained in the pump status information of the syringe pump 2a.

(4) Then, when the syringe pump 2a in which the forecast alert event occurred and the patient ID information and patient location information associated with that syringe pump 2a are identified, the control device 32 then generates a forecast alert command that includes forecast type information indicating the content of the forecast alert event that occurred (information indicating that "10 minutes until liquid runs out") and the patient ID information and patient location information associated with the syringe pump 2a in which the forecast alert event occurred, and converts the generated forecast alert command into a data format that can be read by the nurse call system 6 and transmits it to the nurse call system server 61.

(5) When the nurse call system server 61 receives a forecast issuance command from the pump management server 3 via the network N, it analyzes the received forecast issuance command. By analyzing the received alarm event issuance command, the nurse call system server 61 identifies the content of the forecast issuance event that has occurred (the forecast issuance condition that has been fulfilled) and the patient ID information and patient location information associated with the syringe pump 2a in which the forecast issuance event has occurred, and notifies staff such as nurses of this identified information using the functions of the nurse call system 6.

(6) That is, the nurse call system server 61 notifies staff such as nurses of the details of the forecast event that has occurred (information indicating that "10 minutes left until fluid runs out"), the patient ID information, and the location information of the patient via the terminal device 63 of the nurse call system 6. This allows staff such as nurses to know, via the terminal device 63 (e.g., smartphone 300), almost simultaneously (instantaneously) with the occurrence of the forecast event, which forecast condition has been met for which medical pump device 2 in which bed in which room, and therefore allows for rapid response to the forecast (e.g., changing the medicinal fluid, etc.).

As with the alarm event notification, for example, a table may be provided that matches patient ID information with the patient's name or patient information including the patient's name (e.g., gender, age, etc.), and the patient's name, etc. may be notified along with or instead of the patient ID information. Also, a table may be provided that matches pump ID information with the type of medical pump device 2, and information such as the model name may be identified from the pump ID information, and the type of medical pump device 2 may also be notified when the occurrence of the above-mentioned forecast event is notified.

In this way, according to the medical pump management system 1 of the present invention, the pump management server 3 is configured to determine whether or not the forecast issuance conditions set for each medical pump device 2 have been met, and when it determines that the forecast issuance conditions have been met, to transmit a forecast issuance command to the nurse call system 6, which includes forecast type information indicating the content of the forecast issuance condition that has been met, the pump ID information of the medical pump device, and the patient ID information associated with the pump ID information of the medical pump device 2. Therefore, the nurse call system 6 can quickly know which medical pump device (or which patient) has met which forecast issuance condition. Therefore, nurses and other staff who come into contact with this information can quickly take appropriate action according to the notified forecast type information.

In addition, because the conditions for issuing a forecast are set for each medical pump device, for example, by changing the timing for issuing a forecast of fluid shortage depending on the distance from the nursing center, it becomes possible to take action against the forecast (for example, by replacing the medicinal fluid) in good time after the forecast of fluid shortage is issued.

The above-mentioned embodiments are merely preferred embodiments of the present invention, and the present invention is not limited to these, and various design changes are possible within the scope of the present invention.

For example, in the above-described embodiment, the medical pump device itself is provided with a control unit, but the pump status information may be output by a later-installed device as long as the pump status information can be output periodically and when an event occurs.

In the above embodiment, when an alarm event or a forecast issuance event is notified, the control device 32 generates an alarm event issuance command (or forecast issuance command) including the alarm event type information (or forecast type information), the patient ID information associated with the pump ID information of the medical pump device, and the patient location information, and transmits it to the nurse call system 6. However, the alarm event issuance command and the forecast issuance command are only required to notify, at a minimum, the type of the event that has occurred and which medical pump device 2 or patient the event occurred in, so the alarm event issuance command or the forecast issuance command may include the alarm event type information (or forecast type information) and the pump ID information of the medical pump device 2 and/or the patient ID information associated with the pump ID information. Therefore, the alarm event issuance command or the forecast issuance command may be composed of the event type information and the pump ID information of the medical pump device 2 in which the event has occurred, or may be composed of the event type information and the patient ID information, or may be composed of a combination of these with the patient location information.

In the above embodiment, the forecast issuance condition is set to "10 minutes before the liquid runs out." However, the time until the liquid runs out can be freely changed, and the forecast issuance condition can be changed as desired, for example, by using the remaining amount of liquid before the liquid runs out instead of the grace period until the liquid runs out. In short, the forecast issuance condition can be freely set as long as it is a condition that can be determined based on the pump status information transmitted from the medical pump device 2 periodically and when an event occurs.

Reference Signs List 1 Medical pump management system 2 Medical pump device 3 Pump management server 4 Electronic medical record system 5 Nursing support system 6 Nurse call system 31 Database 32 Control device 63 Terminal device (notification means)
101 Patient-pump correspondence table 102 Pump status record table 103 Forecast condition record table 201 Control means 202 Forecast condition setting means 203 Transmission destination setting means 204 Communication means 300 Smartphone 400 Display device 500 Terminal computer 600 Nurse call base unit N Network

Claims (4)

a plurality of medical pump devices for supplying fluid to a patient;
A pump management server communicatively connected to the medical pump device;
In a medical pump management system including a medical support system communicatively connected to the pump management server,
The medical pump device is configured to output pump status information indicating a status of the medical pump device periodically and when an event occurs,
The pump management server includes a database and a control device.
The database includes a patient-pump correspondence table that stores, for a patient receiving a supply of liquid from the medical pump device, a patient and the medical pump device in association with each other using patient ID information that identifies the patient and pump ID information that identifies the medical pump device;
a pump status record table for storing pump status information transmitted periodically and when an event occurs from the medical pump device for each medical pump device;
a prediction condition recording table that stores a prediction issuance condition set for each of the medical pump devices,
the control device is configured to determine, for each of the medical pump devices, whether or not a preset forecast issuance condition is satisfied based on pump status information and forecast issuance conditions stored in the database, and when it is determined that the forecast issuance condition is satisfied, to transmit a forecast issuance command to the medical support system, the forecast issuance command including forecast type information indicating the content of the forecast issuance condition, and pump ID information of the medical pump device and/or patient ID information associated with the pump ID information ;
the condition for issuing the forecast is a grace period until the medical pump device runs out of fluid,
The control device is configured to calculate a grace period until the liquid runs out based on a planned amount of liquid to be administered and a set flow rate included in the pump status information, and to determine whether or not a warning condition is satisfied.
A medical pump management system comprising: The medical pump management system of claim 1, characterized in that the medical support system is equipped with an alarm means for, when receiving the forecast issuance command transmitted from the control device, notifying the forecast type information contained in the received forecast issuance command, the pump ID information of the medical pump device and/or the patient ID information corresponding to the pump ID information of the medical pump device. The medical pump management system according to claim 1 or 2, characterized in that the control device is provided with a destination setting means for setting a destination of the forecast issuance command, and is configured to convert the forecast issuance command into a data format readable by the medical support system set by the destination setting means and transmit the converted data when the forecast issuance command is transmitted. The patient-pump correspondence table of the database stores the patient ID information in association with patient location information that identifies the location of the patient;
The medical pump management system according to claim 1 or 2, characterized in that the control device has a control configuration that, when transmitting the patient ID information to the medical support system, also transmits patient location information corresponding to the patient ID information.

Images