JP2021119449A - Method for managing medical apparatus, information processing device, and management system for medical apparatus - Google Patents

Abstract

To provide a technique for an information processing device that manages information output from a medical apparatus to appropriately handle the information output from the medical apparatus.SOLUTION: When receiving patient ID, medicine ID, and pump ID from a terminal 3 operated by a medical staff in step S204, a management server 2 requests state information from an infusion pump 1 identified by the pump ID. In response to the request, in step S100, the infusion pump 1 transmits the state information in the infusion pump 1 to the management server 2. In response to reception of the state information, in step S206, the management server 2 calculates difference between time information of the state information and time measured by a timer in the management server 2, and corrects the time information of the state information transmitted from the infusion pump 1 based on the difference.SELECTED DRAWING: Figure 7

Description

The present disclosure relates to the management of information generated in medical devices.

Conventionally, various techniques have been proposed for managing information generated in medical devices. For example, Japanese Patent Application Laid-Open No. 2018-504952 (Patent Document 1) discloses a technique for outputting an evaluation of infusion reactivity of a medical device (infusion device) connected to an evaluation system. Japanese Patent Application Laid-Open No. 2018-532473 (Patent Document 2) warns that a system for supplying a drug to a patient via a syringe is based on the relationship between the amount of the drug supplied via the syringe and the vital sign signal of the patient. Disclose the technology to output. Japanese Unexamined Patent Publication No. 2019-177131 (Patent Document 3) discloses a technique for changing a threshold value for outputting an error code depending on whether a medical device (infusion device) is moving or stationary.

JP-A-2018-504952 Japanese Unexamined Patent Publication No. 2018-532473 JP-A-2019-177131

As described above, in the conventional system, what kind of information is output based on the information acquired from the medical device (infusion device, etc.) by the information processing device such as the server is examined. On the other hand, since the medical device is originally intended to be used alone, there is an inconvenience when the information processing device handles the data output from the medical device and the data is used as it is. It can occur. However, conventionally, sufficient studies have not been made on the handling of data by information processing devices.

The present disclosure has been devised in view of such circumstances, and the purpose of the present disclosure is to provide a technique for an information processing device that manages information output from a medical device to appropriately handle the information output from the medical device. To provide.

According to certain aspects of the disclosure, a method of managing a medical device, performed by a computer, in response to the steps in which the computer obtains a notification associating the medical device with the patient and the acquisition of the notification. However, the state information includes the time information in the medical device, and the computer includes the time in the state information transmitted from the medical device. The step of identifying the difference between the information and the time information in the computer, and the computer stores the state information transmitted from the medical device in the storage device after modifying the time information so that the specified difference is eliminated. A method is provided that comprises steps.

The method is a step in which the computer requests the medical device to output a history of the state information in the medical device when the state information transmitted from the medical device indicates that the medical device is already in operation. The computer may further include a step of modifying the history of state information transmitted from the medical device, modifying the time information so that the identified difference is eliminated, and storing it in the storage device.

The history of the state information may include the state information from the start of operation of the medical device most recent to the time when the output of the state information is requested to the time when the output of the state information is requested.

The method further comprises a step in which the computer stores the state information transmitted from the medical device without being related to the acquisition of the notification, modifying the time information so that the identified difference is eliminated and storing it in the storage device. You may.

The method may further comprise a step in which the computer receives patient data associated with the medical device and stores the patient data in storage along with the received time information.

The method may further comprise a step in which the computer transmits the status information transmitted from the medical device to the terminal from which the notification is sent.

According to other aspects of the disclosure, it comprises a processor, a timer, a storage device, and the processor, in response to receiving a notification associating the medical device with the patient, tells the medical device the state in the medical device. Requesting the output of information, the state information includes time information in the medical device, the processor identifies the difference between the time information in the state information transmitted from the medical device and the time information measured by the timer, and the medical device. An information processing device is provided that modifies the time information so that the specified difference is eliminated and stores the state information transmitted from the device in the storage device.

According to yet another aspect of the present disclosure, the information processing device comprises the medical device, the information processing device includes a processor, a timer, and a storage device, and the processor provides a notification associating the medical device with the patient. In response to the acquisition, the medical device is requested to output the state information of the medical device, the state information includes the time information of the medical device, and the medical device is requested by the information processing device. On the other hand, the state information of the medical device is transmitted, the processor identifies the difference between the time information in the state information transmitted from the medical device and the time information measured by the timer, and the state information transmitted from the medical device. A medical device management system is provided that modifies the time information so that the identified difference is eliminated and stores it in the storage device.

According to the present disclosure, when there is a difference between the time information in the state information transmitted from the medical device to the computer (information processing device) and the time information in the computer (information processing device), the difference is specified. The state information is stored in the storage device after the time information is modified so that the difference is eliminated. That is, in a computer (information processing device), the state information output from the medical device is stored in a state having time information according to the same standard as other information, whereby the information output from the medical device is appropriately stored. Be treated.

It is a figure which shows the whole structure of the management system of a medical device. It is a figure which shows the hardware composition of the infusion pump 1. It is a figure which shows an example of the hardware configuration of management server 2. It is a figure which shows an example of the hardware composition of the terminal 3. It is a figure which shows an example of the hardware composition of the electronic medical record server 4. It is a figure which shows an example of the data structure of the patient information stored in management server 2. It is a flowchart of an example of the process executed for the management of the information generated in the infusion pump 1 in the management system 1000. It is a flowchart of an example of the process executed for the management of the information generated in the infusion pump 1 in the management system 1000. It is a flowchart of an example of the process executed for the management of the information generated in the infusion pump 1 in the management system 1000. It is a figure which shows an example of the display of order information on a touch panel 313. It is a figure which shows an example of the patient information generated in step S210. It is a figure which shows another example of the patient information generated in step S210. It is a figure which shows an example of the patient information which added the history of the state information with respect to FIG. It is a figure which shows an example of the display of an error in a terminal 3. It is a figure which shows another example of the display of an error in a terminal 3. It is a figure which shows an example of the display of the completion of an infusion solution in a terminal 3.

An embodiment of a medical device management system will be described below with reference to the drawings. In the following description, the same parts and components are designated by the same reference numerals. Their names and functions are the same. Therefore, these explanations will not be repeated.

[1. Management system configuration]
FIG. 1 is a diagram showing an overall configuration of a medical device management system. The management system 1000 includes an infusion pump 1, a management server 2, a terminal 3, and an electronic medical record server 4, which are examples of medical devices. The infusion pump 1, the management server 2, the terminal 3, and the electronic medical record server 4 are configured to be able to communicate with each other via the network 9. The network 9 is, for example, a LAN (Local Area Network).

The infusion pump 1 is used, for example, in a hospital for infusion treatment of a patient. The management system 1000 may include a plurality of infusion pumps 1.

The management server 2 is an example of an information processing device that manages data generated by each infusion pump 1 in the management system 1000.

The terminal 3 is operated by medical staff (doctors, nurses, etc., hereinafter simply referred to as "staff") in the hospital. The terminal 3 may be a mobile terminal such as a smartphone, or a stationary information processing terminal such as a desktop computer.

The electronic medical record server 4 manages information on each patient. In one embodiment, the doctor registers in the management system 1000 information on infusion therapy for each patient (such as infusion flow rate). The staff sets the information registered for the infusion treatment of each patient in the infusion pump 1 by referring to the information registered in the electronic medical record server 4 using the terminal 3. As a result, each patient is provided with treatment using the infusion pump 1.

[2. Hardware configuration of infusion pump 1]
FIG. 2 is a diagram showing a hardware configuration of the infusion pump 1. The infusion pump 1 includes a control unit 100 that controls the infusion pump 1. The control unit 100 includes a processor 101, a non-volatile RAM (Random Access Memory) 102, a timer 103, and a bus line connecting these elements to each other.

The processor 101 generates a log of the operation of the infusion pump 1 and stores it in the non-volatile RAM 102. The timer 103 clocks and outputs the current year, month, day, and time. The control unit 100 can recognize the current year, month, day, and time based on the output of the timer 103. The timer 103 is supplied with power by a backup power source such as a battery, and maintains the above timing even when the infusion pump 1 is turned off (power is turned off).

The infusion pump 1 includes a start button 10, an operation unit 11, a power button 12, a bubble sensor 71, a blockage sensor 72, a door sensor 73, a drip sensor 74, and an impact sensor 75. These are connected to the control unit 100, and signals from switches (buttons) and sensors are input to the control unit 100.

The start button 10 receives an infusion start instruction. The operation unit 11 includes a hardware button and receives inputs of various instructions (for example, setting of flow velocity, setting of total flow rate in infusion, etc.) to the infusion pump 1. The power button 12 receives an instruction to switch the power of the infusion pump 1 ON / OFF.

The bubble sensor 71 detects bubbles mixed in the infusion tube and is realized by, for example, an ultrasonic sensor. The obstruction sensor 72 detects the closure of the infusion tube on the downstream side. The main body of the infusion pump 1 accommodates a chemical solution pack and the like, and is configured to be opened and closed by a door. The door sensor 73 detects the opening and closing of the door. The drop sensor 74 detects drops dropped in the infusion solution and is realized by, for example, an optical sensor. The impact sensor 75 detects the magnitude (and direction) of the impact applied to the infusion pump 1 and is realized by, for example, an acceleration sensor.

The infusion pump 1 includes a display 13, an indicator 14, a speaker 15, and an electric motor 16. These are connected to the control unit 100, and their operation is controlled by the control unit 100.

The display 13 displays various information such as the state of the infusion pump 1, and is realized by, for example, a liquid crystal display device. The indicator 14 is realized by one or more lamps, and includes a power lamp that indicates that the power is turned on by lighting. The speaker 15 outputs sound. In one implementation example, the control unit 100 outputs a given voice from the speaker 15 when an abnormality (battery abnormality, bubble abnormality, etc.) occurs in the infusion pump 1 and when the infusion solution is completed. The electric motor 16 is driven by the infusion pump 1 to deliver the infusion solution in the chemical solution pack to the infusion solution tube.

The infusion pump 1 further includes a communication interface 110. The communication interface 110 is realized by, for example, a network card. The control unit 100 connects to the network 9 using the communication interface 110, and communicates with the management server 2 via the network 9. The control unit 100 may directly communicate with the management server 2 without going through the network.

The infusion pump 1 further includes a battery 76 and a power supply circuit 77. The battery 76 supplies electric power to each part of the infusion pump 1. In one embodiment, the infusion pump 1 is connected to a commercial power source by an AC (Alternative Current) power cord, and the battery 76 is charged by the commercial power source. The power supply circuit 77 supplies electric power of a commercial power source to each part in the infusion pump 1 via an AC power cord.

[3. Management server 2 hardware configuration]
FIG. 3 is a diagram showing an example of the hardware configuration of the management server 2. The management server 2 includes a CPU (Central Processing Unit) 211. The CPU 211 realizes a given function by executing a program. The program may include not only a program that can be directly executed by the CPU 211, but also a source program format program, a compressed program, an encrypted program, and the like.

The management server 2 further includes a timer 212, an input interface 213, a RAM 214, a hard disk 215, a media drive 216, a communication interface 217, and an output interface 218. Each component in the management server 2 is connected to each other by a bus.

The timer 212 has a clock function. The CPU 211 synchronizes the time measured by the timer 212 with the time measured by the clock server by communicating with an external clock server via the communication interface 217 at a given timing (for example, when the management server 2 is started). Can be done.

The input interface 213 is connected to the keyboard 221 and the mouse 222. The CPU 211 receives inputs from the keyboard 221 and the mouse 222 via the input interface 213. The media drive 216 is equipped with a recording medium. The CPU 211 reads data from a recording medium (CD-ROM, USB memory, memory card, etc.) 219 via the media drive 216, and writes the data to the recording medium.

The hard disk 215 stores the program and various data necessary for executing the program.

The output interface 218 is connected to the display 223. The CPU 211 controls the display of the display 223 via the output interface 218. The display 223, the keyboard 221 and the mouse 222 may be realized by a touch panel. In this case, the input interface 213 and the output interface 218 function as interfaces for communicating with the touch panel.

[4. Hardware configuration of terminal 3]
FIG. 4 is a diagram showing an example of the hardware configuration of the terminal 3. The terminal 3 includes a CPU 311. The CPU 311 realizes a given function by executing a program. An application program (hereinafter referred to as "staff application") for transmitting and receiving information on infusion treatment of a patient is installed in the terminal 3. The staff carrying the terminal 3 can acquire various information related to the infusion treatment by causing the CPU 311 to execute the staff application. The program may include not only a program that can be directly executed by the CPU 311 but also a source program format program, a compressed program, an encrypted program, and the like.

The terminal 3 further includes a touch panel 313, a RAM 314, a storage 315, a media drive 316, a communication interface 317, and a camera 318. Each component in the terminal 3 is connected to each other by a bus.

The touch panel 313 includes a display and a touch sensor. The CPU 311 receives an operation via the touch sensor and displays information on the display. The storage 315 is realized by, for example, a flash ROM, and stores a program and various data necessary for executing the program. The media drive 316 is equipped with a recording medium. The CPU 311 reads data from a recording medium (CD-ROM, USB memory, memory card, etc.) 319 via the media drive 316, and writes the data to the recording medium. The camera 318 outputs image information to the CPU 311.

[5. Hardware configuration of electronic medical record server 4]
FIG. 5 is a diagram showing an example of the hardware configuration of the electronic medical record server 4. The electronic medical record server 4 includes a CPU 411. The CPU 411 realizes a given function by executing a program. The program may include not only a program that can be directly executed by the CPU 411, but also a source program format program, a compressed program, an encrypted program, and the like.

The electronic medical record server 4 further includes a timer 412, an input interface 413, a RAM 414, a hard disk 415, a media drive 416, a communication interface 417, and an output interface 418. Each component in the electronic medical record server 4 is connected to each other by a bus.

The timer 412 has a clock function. The CPU 411 synchronizes the clocked time of the timer 412 with the clocked time of the clock server by communicating with an external clock server via the communication interface 417 at a given timing (for example, when the electronic medical record server 4 is started). be able to.

The input interface 413 is connected to the keyboard 241 and the mouse 222. The CPU 411 receives inputs from the keyboard 241 and the mouse 222 via the input interface 413. The media drive 416 is equipped with a recording medium. The CPU 411 reads data from a recording medium (CD-ROM, USB memory, memory card, etc.) 419 via the media drive 416, and writes the data to the recording medium.

The hard disk 415 stores the program and various data necessary for executing the program.

[6. Order information]
In the management system 1000, the order information database is stored in the hard disk 415. The order information database stores order information that defines infusion therapy for each patient. In one implementation example, the doctor generates a plan for infusion treatment of each patient, generates order information according to the plan, and registers the order information in the electronic medical record server 4. In the electronic medical record server 4, the registered order information is stored in the hard disk 415.

In one implementation example, the order information includes the following five types of information.
・ Order ID
・ Patient ID
・ Drug ID
-Scheduled flow velocity-Scheduled total flow rate The order ID specifies order information. The patient ID identifies the target patient in the order information. The drug ID may specify the drug to be used according to the order information, specify the name of the drug, specify the drug solution pack filled with the drug, or specify both of them. .. In one embodiment, the doctor identifies the name of the drug as the drug ID, the staff prepares the drug solution pack based on the drug ID (and the planned total flow rate), and the drug ID is further added to the drug solution pack. May also be modified to associate. That is, the drug ID may specify both the name of the drug and the drug solution pack. The planned flow velocity specifies the flow velocity in the infusion solution according to the order information. The planned total flow rate specifies the total amount of drug dropped in the infusion according to the order information.

[7. Status information output from the infusion pump 1]
In the management system 1000, the infusion pump 1 transmits state information to the management server 2 in response to a request from the management server 2 or at a given timing. In one implementation example, the state information includes the following six types of information.

-Time information-Operating state-Flow velocity-Integrated amount-Alarm state-Power supply information The time information represents the time measured by the timer 103.

The operating state represents the operating state of the infusion pump 1. In one embodiment, the infusion pump 1 transmits 8-bit data as an operating state. Of the 8-bit data, the upper 4 bits represent the operating state of the pump, and the lower 4 bits represent the key lock state of the pump. The operating state of the pump represents, for example, one of the following six types of states.

-Stop-Standby-Normal infusion-Fast-forward-Porus-Complete Stop indicates a state in which the electric motor 16 is stopped in the infusion pump 1. The standby represents a state in which the infusion pump 1 is stopped in a state where infusion is possible. The normal infusion represents a state in which the infusion pump 1 is executing the infusion in a normal manner. The fast-forward represents a state in which the infusion pump 1 is delivering the drug solution at a speed faster than the set flow velocity. Porous represents a state in which the infusion pump 1 is executing infusion at high pressure. Completion represents a state (KOR (Keep Open Rate) state) in which the infusion is continued at the minimum flow rate after the infusion according to the most recently set order is completed.

Returning to the state information, the flow velocity represents a value set as the speed at which the electric motor 16 sends the chemical solution. The integrated amount represents the set value of the total amount of the drug solution to be sent.

The alarm state indicates whether or not an error has occurred in the infusion pump 1 and the type of error when an error has occurred. The error includes an impact abnormality, a system abnormality, a battery abnormality, a bubble abnormality, an upstream blockage abnormality, a downstream blockage abnormality, a door open abnormality, a flow velocity abnormality, an empty liquid abnormality, a drip sensor mounting failure, an abnormality after infusion completion, and the like. The alarm state is represented by, for example, a code. An example of the code when no error occurs is "0x00000000000".

The shock abnormality indicates that a shock exceeding a given threshold value has been applied to the infusion pump 1. The system abnormality indicates that an abnormality has occurred in the computer system including the control unit 100. The battery abnormality means that the commercial power supply cannot be supplied through the power supply circuit 77, and the remaining amount of the battery 76 falls below a given threshold value. Bubble anomaly indicates that bubbles of a given size or larger have been generated in the infusion tube. Each of the upstream obstruction abnormality and the downstream obstruction abnormality indicates that the infusion tube is obstructed on the upstream side and the downstream side of the pump portion to which the driving force of the electric motor 16 is transmitted.

The door open abnormality indicates that the door that opens and closes the main body of the infusion pump 1 is continuously opened for a given time or longer. The flow velocity abnormality indicates that the flow velocity of the chemical solution in the infusion pump 1 differs from the flow velocity (planned flow velocity) specified in the order information by a given value or more. An empty liquid abnormality indicates that the chemical solution in the chemical solution pack has run out before the infusion of the total flow rate (total flow rate) specified in the order information is completed. A drip sensor mounting failure represents a state in which the drip sensor is not properly mounted. Abnormality after the completion of infusion indicates that the above KOR state has continued for a given time or longer.

Returning to the state information, the power supply information represents the information of the drive power source of the infusion pump 1. In one implementation example, the power supply information is 8-bit data, the upper 4 bits represent the power supply source (battery 76 or power supply circuit 77), and the lower 4 bits represent the remaining battery level of the battery 76.

[8. Patient information on management server 2]
FIG. 6 is a diagram showing an example of a data structure of patient information stored in the management server 2. As shown in FIG. 6, the patient information associates management information, status information, and vital information. In one embodiment, the patient information is stored on the hard disk 215.

The management information in the patient information includes the pump ID and the staff ID in addition to the data (order ID, patient ID, drug ID, planned flow velocity, planned total flow rate) included in the order information registered in advance in the electronic medical record server 4. include. The pump ID identifies each infusion pump 1. The staff ID identifies each staff member. The state information represents the state information transmitted from the infusion pump 1. The vital information represents the vital information acquired for the patient ID included in the order information.

In one implementation example, the management server 2 receives the vital information associated with the patient ID via the network 9 and stores it in the patient information. In the example of FIG. 6, the vital information includes blood pressure (maximum blood pressure H and diastolic blood pressure L) and body temperature. For example, a patient provided with infusion therapy with an infusion pump 1 wears a sphygmomanometer and a thermometer. The sphygmomanometer and the thermometer transmit the measurement result to the management server 2 via the network 9. The management server 2 may receive the measurement result directly from the sphygmomanometer and / or the thermometer (without going through the network). Further, the staff may input the vital information of the patient into the terminal 3, and the terminal 3 may transmit the vital information to the management server 2.

[9. Process flow]
7 to 9 are flowcharts of an example of processing executed for management of information generated in the infusion pump 1 in the management system 1000. In the examples of FIGS. 7-9, a process for providing an infusion therapy to a patient using the infusion pump 1 is shown.

7 to 9 show the processes executed by the infusion pump 1, the terminal 3, the management server 2, and the electronic medical record server 4, respectively. The infusion pump 1 executes the processes of FIGS. 7 to 9, for example, when the processor 101 executes a given program. The terminal 3 executes the processes shown in FIGS. 7 to 9 by, for example, the CPU 311 executing a given program (for example, a staff application). The management server 2, for example, the CPU 211, executes the given program to execute the processes of FIGS. 7 to 9. The electronic medical record server 4 executes the processes of FIGS. 7 to 9 by, for example, the CPU 411 executing a given program.

Prior to the description of the processes of FIGS. 7 to 9, an example of the operation of the staff when starting the infusion therapy will be described.

The staff activates the staff application on the terminal 3 and inputs the staff ID. In response to this, the staff application of the terminal 3 requests the management server 2 for the order information database. The management server 2 authenticates the staff by the staff ID, and if the authentication is successful, requests the electronic medical record server 4 for the order information database. The order information database in the electronic medical record server 4 is transferred to the terminal 3 via the management server 2. After that, the staff inputs the patient ID of the patient in front of the staff to the terminal 3, the drug ID of the drug solution pack prepared for the patient, and the pump ID of the infusion pump 1. The staff application of the terminal 3 extracts the order information corresponding to the input patient ID and displays it on the touch panel 313. The staff sets the flow rate and the like in the infusion pump 1 according to the display of the order information, confirms that the chemical solution pack prepared for the patient is the correct chemical solution pack, and then operates the start button 10 of the infusion pump 1. do. As a result, the infusion therapy using the infusion pump 1 is started. When the terminal 3 transmits the patient ID to the electronic medical record server 4 via the management server 2 instead of transferring the order information database to the terminal 3, the electronic medical record server 4 is associated with the patient ID. The management system 1000 may be configured to transmit order information to the terminal 3.

The input of each ID may be realized by a character input operation on the touch panel by the staff, or may be realized by taking a bar code or a QR code (registered trademark) with the camera 318. In the case of shooting, for example, the code printed on the staff name tag is shot when inputting the staff ID. For input of the patient ID, for example, a code printed on a tape wrapped around the patient's wrist is photographed. To enter the drug ID, a code printed on a sticker attached to the drug solution pack attached to the infusion pump 1 or to be attached by the staff is photographed. For input of the pump ID, for example, a code printed on a sticker attached to the main body of the infusion pump 1 is photographed. The staff application acquires each ID by specifying the ID represented by the barcode or QR code from the image taken by the camera 318.

Hereinafter, the processes of FIGS. 7 to 9 will be described.
First, referring to FIG. 7, in step S300, the terminal 3 acquires the staff ID and transmits the staff ID to the management server 2.

In step S200, the management server 2 transfers the staff ID to the electronic medical record server 4. The management server 2 may authenticate the staff ID and transfer the staff ID to the electronic medical record server 4 on condition that the authentication is successful.

In step S400, the electronic medical record server 4 transmits the order information database to the management server 2 in response to receiving the staff ID.

Upon receiving the order information database, in step S202, the management server 2 transfers the order information database to the terminal 3 (which is the source of the staff ID in step S200).

In step S302, the terminal 3 acquires the patient ID, the drug ID, and the pump ID.

In step S304, the terminal 3 transmits the patient ID, the drug ID, and the pump ID acquired in step S302 to the management server 2 in association with each other.

Upon receiving the patient ID, the drug ID, and the pump ID from the terminal 3, in step S204, the management server 2 requests the state information from the infusion pump 1 specified by the received pump ID. In one implementation example, the management server 2 stores information relating the pump ID and the IP address of the infusion pump 1, and the management server 2 sends the status information to the IP address associated with the received pump ID as a destination. Send the requested message.

In step S204, the management server 2 receives the patient ID, the drug ID, and the pump ID. In this sense, step S204 is an example of a step of obtaining a notification associating a patient with a medical device (infusion pump 1).

In response to the transmission of the status information from the management server 2, the infusion pump 1 transmits the status information to the management server 2 in step S100.

In response to the transmission of the state information from the infusion pump 1, the management server 2 calculates the difference between the time information of the state information and the timed time of the timer 212 in step S206. The management server 2 stores the difference in the hard disk 215 or RAM 214, and corrects the state information transmitted from the infusion pump 1 based on the difference. More specifically, the management server 2 modifies the time information of the state information so as to eliminate the above difference, that is, to align the time information with the timer 212. For example, the time of the timer 212 when the management server 2 receives the status information is 10:00 on February 18, 2019, and the time information of the status information is 9:50 on February 18, 2019. When pointing to minutes, "10 minutes" is calculated as the difference. Then, the management server 2 modifies the state information so as to add the difference to the time information of the state information. As a result, the time information of the corrected state information will point to 10:00 on February 18, 2019.

In step S208, the management server 2 transmits the modified state information in step S206 to the terminal 3. After that, the management server 2 advances the control to step S210 (FIG. 8).

In step S306, the terminal 3 displays the order information corresponding to the patient ID acquired in step S302 on the touch panel 313.

FIG. 10 is a diagram showing an example of displaying order information on the touch panel 313. As shown in FIG. 10, the screen 600 includes columns 601, 602, 603, 604, 605.

Column 601 displays the staff ID (13023022) acquired in step S300. Column 602 displays the patient ID (17011089) acquired in step S302. Column 603 represents the pump ID (1234567899) acquired in step S302.

The staff name associated with each staff ID may be registered in the staff application, or the patient name associated with each patient ID may be registered. In the example of FIG. 10, in column 601 the staff name (Nipro Hanako) is displayed in addition to the staff ID, and in column 602, the patient name (Takao Ikechi) is displayed in addition to the patient ID. It is displayed. Further, the name of the pump associated with each pump ID may be registered in the staff application. In the example of FIG. 10, in column 603, the name of the pump (pump 1) is displayed in addition to the pump ID.

Column 603 further displays the status information of the infusion pump 1 transmitted from the management server 2 in step S208. In the example of FIG. 10, the integrated amount (planned amount_XXXXXXXXX), the flow velocity (flow velocity_XXXXXX), and the operating state (stopped) are displayed in the state information.

Column 604 displays the order ID (20190218_17011089_001) of the order information extracted for the patient ID acquired in step S302. Column 604 further displays the drug ID (drug (1)) of the order information, the planned total flow rate (flow rate_XXXXXX) of the order information, and the planned flow velocity (velocity_XXXXXXXXX).

Column 605 is a message prompting the staff to confirm the information displayed on the screen 600 when inputting the setting related to the infusion treatment to the infusion pump 1 and the operation start instruction to the infusion pump 1 (as ordered). After setting, press the "Start" button of the pump).

By looking at column 604 of the screen 600, the staff can set the value to be set as the "integrated amount" in the infusion pump 1 (planned total flow rate of the order information) and the value to be set as the "flow velocity" in the infusion pump 1 (order information). (Scheduled flow velocity) can be confirmed. Further, the staff can confirm the patient to be treated by the infusion treatment by looking at the screen 600, and can confirm the infusion pump 1 and the drug solution pack used for the infusion treatment of the patient.

Further, if the staff has input the "integrated amount" and the "flow velocity" in the infusion pump 1 before inputting the patient ID, the drug ID, and the pump ID in step S302, the fields 603 are set. "Integrated amount" and "flow velocity" are displayed. Therefore, the staff can judge whether or not the input of the "integrated amount" and the "flow velocity" is correct by comparing the column 603 and the column 604.

After that, when the staff operates the start button 10 of the infusion pump 1, the infusion pump 1 starts the infusion of the drug in the drug solution pack, and the infusion treatment of the patient is started.

With reference to FIG. 8, in step S210, the management server 2 has the staff ID received in step S200, the order information database received in step S202, and the patient ID and drug ID received in step S204. Then, the patient information is generated by using the pump ID and the state information received in step S206.

FIG. 11 is a diagram showing an example of patient information generated in step S210. In the example of FIG. 11, among the management information, the patient ID is the patient ID acquired in step S204. The order ID, the drug ID, the planned flow velocity, and the planned total flow rate constitute the order information associated with the patient ID acquired in step S204 among the order information included in the order information database acquired in step S202. To do. The pump ID in the management information is the pump ID acquired in step S204. The staff ID in the management information is the staff ID acquired in step S200.

The patient information in FIG. 11 includes only the status information associated with the time "2019.02.18_10:00" (10:00 on February 18, 2019). The state information is the state information received in step S step S206. However, the "time" of the state information is the time corrected in step S206.

When the management server 2 receives the state information in step S206, the management server 2 may further acquire the vital information associated with the patient ID received in step S204. In one implementation example, the management server 2 requests a response from the device associated with the patient ID on the network 9, and acquires vital information from the device that transmitted the response. The vital information shown in FIG. 11 is acquired in such an embodiment and stored in the patient information, for example.

Returning to FIG. 8, in step S212, the management server 2 determines whether or not the operating state indicated by the state information received in step S206 indicates that the operation is in progress. If the operating state indicated by the state information indicates that it is operating (YES in step S212), the management server 2 advances control to step S214, and if not (NO in step S212), the management server 2 proceeds to step S218. Advance control.

The example of FIG. 11 is based on the values of the operating states corresponding to the respective states as follows.
0: Stop 1: Standby 2: Normal infusion 3: Fast forward 4: Porous 5: Completion In step S214, the management server 2 requests the infusion pump 1 to have a history of status information since the latest operation start.

Upon receiving the history request, in step S102, the infusion pump 1 transmits the history of the state information including the state information since the latest operation start at the present time to the management server 2. The history may further include state information at the time of the previous stop.

Upon receiving the history of the state information, in step S216, the management server 2 modifies the time information of the state information included in the history in the same manner as in step S206 and stores it in the patient information. After that, the management server 2 advances the control to step S218.

Here, the control of steps S212 to S216 will be described with specific examples.
For example, it is assumed that the staff sets the information corresponding to the order information in the infusion pump 1, operates the start button 10, and then inputs the patient ID, the drug ID, and the pump ID to the terminal 3. In such a case, since the infusion pump 1 starts the infusion by operating the start button 10, the terminal 3 executes the control of step S302 after the start of the infusion, and the state acquired in step S208. The information becomes state information after the start of infusion (when the infusion pump 1 is already in operation). FIG. 12 is a diagram showing another example of patient information generated in step S210. In the above case, as shown in FIG. 12, only the state information indicating that the operating state is in operation (the value of the operating state is "2") is registered as the state information. In this case, the management server 2 advances control from step S212 to step S214.

After that, when the history of the state information is received in step S216, the management server 2 adds the history to the patient information. FIG. 13 is a diagram showing an example of patient information in which a history of state information is added to FIG. 12. With the addition of the state information history, the patient information will be in the last stopped state (10:00, February 18, 2019) with respect to the time point shown in FIG. 12, as shown in FIG. ) Subsequent status information has been added.

Returning to FIG. 8, in step S218, the management server 2 determines whether or not the status information received from the infusion pump 1 is for notifying the occurrence of an error. In one implementation example, the management server 2 determines whether or not the status information notifies the occurrence of an error based on whether or not the value of the "alarm status" in the status information indicates the occurrence of an error. To judge. If the management server 2 determines that the status information is for notifying the occurrence of an error (YES in step S218), it proceeds to control to step S220, otherwise (NO in step S218), step S222 (NO). Proceed with control to Fig. 9).

In step S220, the management server 2 notifies the terminal 3 of the error. The notification may include the type of error occurring (the type of error indicated by the alarm state).

Upon receiving the error notification, in step S308, the terminal 3 displays the error on the touch panel 313.

FIG. 14 is a diagram showing an example of error display in the terminal 3. The screen 700 of FIG. 14 includes areas 710 and 720. The character string "pump 1" displayed in the area 710 represents the name of the infusion pump 1 in which the error has occurred. This display is based on the name of the infusion pump 1 associated with the pump ID at the terminal 3 if the error notification includes the pump ID.

The character string "bubble alarm" displayed in the area 710 means that an error of bubble abnormality has occurred. The area 710 further includes a button 711 for displaying a coping method for an error that has occurred, and a button 712 for returning the display of the touch panel 313 to the previous screen.

Region 720 includes time information (11:26) timed at terminal 3. The CPU 311 can synchronize the time information timed by the terminal 3 with the time measured by the external clock server at a given timing.

FIG. 15 is a diagram showing another example of displaying an error in the terminal 3. In the screen 700A of FIG. 15, the area 710 further includes the error occurrence time (11:25) as compared to the screen 700 of FIG. When the error notification from the management server 2 includes the time information of the status information, the display of the error occurrence time is based on the time information.

The time information of the state information transmitted from the management server 2 is the time information of the state information transmitted from the infusion pump 1 modified by the management server 2. In one implementation example, in the management system 1000, the time of the timer 103 in the infusion pump 1 is not synchronized with the clock server, but the time of the management server 2 and the time of the terminal 3 are synchronized with the clock server. .. As a result, the time information transmitted from the management server 2 to the terminal 3 becomes the time information according to the same standard as that of the terminal 3. Therefore, the staff who sees the display on the screen 700A can recognize the time according to the same reference as that of the terminal 3 as the error occurrence time.

With reference to FIG. 9, in step S222, the management server 2 determines whether or not the operating state of the state information received from the infusion pump 1 indicates “completion”. If the management server 2 determines that the operating state indicates "completion" (YES in step S222), it proceeds to control to step S224, otherwise (NO in step S222), it goes to step S228. Advance control.

In step S224, the management server 2 notifies the terminal 3 of the completion of the infusion solution. The notification may include the pump ID of the infusion pump 1 for which the infusion has been completed (the pump ID of the infusion pump 1 from which the status information targeted in step S222 is transmitted). After that, the management server 2 advances the control to step S226.

In response to receiving the notification of the completion of the infusion, the terminal 3 displays the completion of the infusion on the touch panel 313 in step S310. FIG. 16 is a diagram showing an example of a display of completion of infusion at the terminal 3.

The screen 800 of FIG. 16 includes an area 810. Region 810 includes the name of the infusion pump 1 (pump 1). The display of the name is the name associated with the pump ID included in the notification. Region 810 further includes the string "infusion completed". The staff who sees the screen 800 can recognize in which infusion pump 1 the infusion is completed.

Returning to FIG. 9, in step S226, the management server 2 transmits patient information to the electronic medical record server 4 for the infusion pump 1 (patient) for which the infusion has been completed.

In response to receiving the patient information, in step S402, the electronic medical record server 4 updates the electronic medical record so as to add the patient information. As a result, the patient information accumulated in the management server 2 during the infusion treatment is accumulated in the electronic medical record server 4. In the patient information transmitted from the management server 2, the time information of the state information transmitted from the infusion pump 1 is corrected by the management server 2 according to the time measured in the management server 2. The time clock on both the management server 2 and the electronic medical record server 4 is synchronized with the time clock on the external clock server. Therefore, patient information including time information according to the same criteria as that of the electronic medical record server 4 is transmitted to the electronic medical record server 4.

In step S228, the management server 2 determines whether or not the vital data of the patient undergoing the infusion therapy has been received. When the management server 2 determines that the vital data has been received (YES in step S228), the management server 2 stores the vital data as vital information in the patient information in step S230. After that, when the infusion pump 1 transmits the state information to the management server 2 in step S104, the control is returned to step S216 (FIG. 8). On the other hand, when the management server 2 determines that the vital data has not been received (NO in step S228), the management server 2 responds to the transmission of the state information from the infusion pump 1 without executing the control of step S230 (NO in step S228). Return control to FIG. 8).

After that, until the infusion treatment (infusion) is completed, the infusion pump 1 sends the status information to the management server 2 in step S104 at a given timing (for example, every given time, when an error occurs, etc.). To send. The management server 2 stores the received state information in step S216, and then executes the control of steps S218 to S222.

In step S216, the management server 2 corrects the time information of the state information received from the infusion pump 1 by using the difference calculated and stored in step S206.

[10. Modification example of medical equipment]
The infusion pump 1 is an example of a medical device. The medical device may be another type of device, such as a blood glucose meter. At the start of the infusion therapy, the staff transmits the patient ID and the information for identifying the blood glucose meter (blood glucose meter ID) to the management server 2. As a result, the management server 2 stores the measurement result received from the device specified by the blood glucose meter ID in the patient information in addition to the state information or instead of the state information. Time information according to the time measured by the timer in the blood glucose meter is attached to the measurement result. The management server 2 identifies the difference between the time information attached to the measurement result and the time information of the timer 212, corrects the time information attached to the measurement result from the glucose meter using the difference, and then sets the time. Store information and measurement results in patient information.

It should be considered that each embodiment disclosed this time is exemplary in all respects and is not restrictive. The scope of the present invention is shown by the scope of claims rather than the above description, and it is intended to include all modifications within the meaning and scope equivalent to the scope of claims. In addition, the inventions described in the embodiments and the modifications are intended to be implemented, either alone or in combination, wherever possible.

1 infusion pump, 2 management server, 3 terminals, 4 electronic medical record server, 9 networks, 10 start buttons, 600, 700, 700A, 800 screens, 1000 management systems.

Claims (8)

A way of managing medical devices by being run by a computer,
When the computer gets a notification that associates the medical device with the patient,
In response to the acquisition of the notification, the computer comprises a step of requesting the medical device to output state information in the medical device.
The state information includes time information in the medical device.
A step in which the computer identifies a difference between the time information in the state information transmitted from the medical device and the time information in the computer.
A method comprising a step in which the computer corrects the time information of the state information transmitted from the medical device so that the specified difference is eliminated and stores the state information in a storage device. When the state information transmitted from the medical device indicates that the medical device is already in operation, the computer requests the medical device to output a history of the state information in the medical device. Steps to do and
1. The computer further comprises a step of modifying the history of state information transmitted from the medical device, modifying the time information so that the specified difference is eliminated, and storing the history in the storage device. The method described in. 2. The history of the state information includes the state information from the start of operation of the medical device most recent to the time when the output of the state information is requested to the time when the output of the state information is requested. The method described in. A step in which the computer corrects the time information so that the specified difference is eliminated and stores the state information transmitted from the medical device without being related to the acquisition of the notification in the storage device. The method according to any one of claims 1 to 3, further comprising. Any of claims 1 to 4, wherein the computer further comprises a step of receiving patient data associated with the medical device and storing the patient data in the storage device together with the received time information. The method according to item 1. The method according to any one of claims 1 to 5, further comprising a step in which the computer transmits the state information transmitted from the medical device to the terminal from which the notification is transmitted. With the processor
With a timer
Equipped with a storage device
The processor
In response to the acquisition of the notification for the start of operation of the medical device, the medical device is requested to output the state information of the medical device.
The state information is
Including time information in the medical device
The processor
The difference between the time information in the state information transmitted from the medical device and the time information measured by the timer is specified.
An information processing device that corrects time information and stores the state information transmitted from the medical device in a storage device so that the specified difference is eliminated. Equipped with information processing equipment and medical equipment,
The information processing device
With the processor
With a timer
Including storage device
The processor
In response to the acquisition of the notification for the start of operation of the medical device, the medical device is requested to output the state information in the medical device.
The state information is
Including time information in the medical device
The medical device is
In response to the request, the state information of the medical device is transmitted to the information processing device.
The processor
The difference between the time information in the state information transmitted from the medical device and the time information measured by the timer is specified.
A medical device management system that modifies time information so that the specified difference is eliminated and stores the state information transmitted from the medical device in a storage device.

Images