JP2021018666A - Medication management system, medication support device, medication support method, and medication support program - Google Patents

Abstract

To provide a medication support device that manages prescribed medicine so that it can be administered to a target patient without fail.SOLUTION: A medicine support device reads patient information on a patient from a tag of the patient to whom medicine is administered, reads mixed notice information including information indicating medicine housed in a medicine container and identification information identifying medication instruction information based on medication instruction information for the patient, refers to a medication instruction storage unit that has stored the medication instruction information for each patient in association with the identification information and the patient information, reads the medication instruction information and the patient information corresponding to the identification information read from a tag attached to the medicine container, detects setting information of an apparatus from the apparatus to be used for medication, and collates and outputs whether the medication instruction information read from the medication instruction storage unit matches the mixed notice information, whether the setting information matches the medication instruction information, and whether the patient information read from the medication instruction storage unit matches the patient information read from the tag allocated for each patient.SELECTED DRAWING: Figure 13

Description

The present invention relates to a medication management system, a medication support device, a medication support method, and a medication support program.

In a large-scale medical institution, when a doctor instructs a medication, the medication instruction is input to a hospital information system (HIS), and the instructed drug is discharged from the pharmacy department and transported to a ward. .. The medicine transported to the ward is administered to the patient by a medical worker such as a nurse. Here, when the drug is administered by intravenous drip infusion, the medical staff consists of a stand (infusion stand) for suspending the bag of the drug, an injection needle, an injection route (tube) for connecting the injection needle and the bag of the drug, and the like. Prepare a drip device. In addition, when a plurality of drugs are administered by intravenous drip infusion, a mixed injection operation of mixing the plurality of drugs with a base infusion preparation such as Ringer's solution is performed in advance.

In mixed injection work, for example, documents such as slips and copies of medication instructions output from HIS are compared with drugs to be mixed, multiple checks by multiple staff, etc., resulting in mistakes in drugs and errors in usage. A great deal of effort has been put into it.

Therefore, in order to improve the efficiency of mixed injection work, read the barcode attached to each medicine delivered to the ward, and check the contents of the injections registered in HIS and the actual mixed injection work by the nurse. A mixed injection work support system that collates with the contents has been proposed (for example, Patent Document 1). By using such a mixed injection work support system, not only is it possible to check the excess or deficiency of the medicine used for mixed injection, but even if there is a change in the prescription instructions after the medicine is delivered from the pharmacy department to the ward, Mixed injection work can be performed based on the latest prescription.

Further, the healthcare professional who administers the drug to the patient needs to finally confirm at the time of administration whether or not the patient is the person himself / herself and the drug to be administered is prescribed to the patient. In order to support such confirmation at the time of administration, patient information and drug information are acquired via the drug solution in the drip line, and if the consistency between the patient and the drug is confirmed and correct, the infusion pump is operated. A communication system has also been proposed (Patent Document 2).

Japanese Unexamined Patent Publication No. 2012-108901 Special Table 2006-521191 Japanese Unexamined Patent Publication No. 2011-70429

However, in the mixed injection work support system of Patent Document 1, since the content of the mixed injection work and the prescribed content are collated at the time of mixed injection, the content of the medication instruction is changed after the mixed injection and before the administration to the patient. Even so, there was a problem that the change could not be reflected in the injection after mixed injection. Therefore, if the prescription is changed after the mixed injection, it is necessary for a person to discontinue the administration of the injectable drug based on the prescription before the change and to judge whether or not the injection is based on the changed prescription. , The confirmation work at the time of administration was complicated.

Further, also in the drip data communication system of Patent Document 2, since the drug information is set at the time of the mixed injection work, the information changed after the mixed injection work cannot be reflected.

Further, in order to realize the system of Patent Document 2, it is necessary to use a communication device for acquiring drug information and the like, and a special infusion pump provided with a control unit for determining consistency and controlling the operation of the pump. When the pump is controlled by the control device in this way, if the control device malfunctions, it may have a serious effect on the patient. Therefore, it is necessary to have a fail-safe function, a self-check function, etc., and the device configuration is very large. Complicate. Further, in the system of Patent Document 2, since the communication medium is a chemical solution in the drip line, the communication path is interrupted even if a slight bubble is generated in the drip line, and data cannot be acquired. Therefore, the system of Patent Document 2 has a problem of poor feasibility.

Further, the system of Patent Document 3 collates the prescription of the drug with the patient information and the instruction information, but in the check at the time of medication, not only the prescription of the drug and the patient information but also the devices such as the infusion pump and the syringe pump are confirmed. In the system of Patent Document 3, this device could not be confirmed, and it was insufficient as a check at the time of medication.
Therefore, an object of the present invention is to provide a technique for managing a prescribed drug so that it can be definitely administered to a target patient.

In order to solve the above problems, the medication support device of the present invention
A patient information reader that reads patient information about the patient from the tags assigned to the patient to whom the drug is administered,
The mixed injection information including the information indicating the drug contained in the drug container and the identification information identifying the medication instruction information based on the medication instruction information for the patient is read from the tag attached to the drug container, or the mixed injection information. A mixed injection information acquisition unit that acquires mixed injection information including the identification information read from the drug container by referring to the mixed injection information storage unit that stores the information.
The medication instruction storage unit that stores the medication instruction information for each patient in association with the identification information and the patient information is referred to, and the identification information read from the tag attached to the drug container and the corresponding medication instruction information and patient information. The medication information acquisition unit that reads out
A device setting detection unit that detects device setting information from the device used based on the medication instruction information,
The patient information read from the medication instruction storage unit matches the mixed injection information, the setting information detected by the device setting detection unit matches the medication instruction information, and the patient information is read from the medication instruction storage unit. And a collation unit that collates whether or not the information matches the patient information read from the tag assigned to each patient.
It includes an output control unit that outputs the result of the collation.

Further, in order to solve the above problems, the medication management system of the present invention is used.
It has a drug information server and a medication support device that are connected via a network.
The drug information server includes a medication instruction storage unit that stores medication instruction information for each patient in association with identification information and patient information.
The medication support device
A patient information reader that reads patient information about the patient from the tags assigned to the patient to whom the drug is administered,
The mixed injection information including the information indicating the drug contained in the drug container and the identification information identifying the medication instruction information based on the medication instruction information for the patient is read from the tag attached to the drug container, or the mixed injection information. A mixed injection information acquisition unit that acquires mixed injection information including the identification information read from the drug container by referring to the mixed injection information storage unit that stores the information.
A medication information acquisition unit that refers to the medication instruction storage unit and reads out medication instruction information and patient information corresponding to the identification information read from the tag attached to the drug container.
A device setting detection unit that detects device setting information from the device used based on the medication instruction information,
The patient information read from the medication instruction storage unit matches the mixed injection information, the setting information detected by the device setting detection unit matches the medication instruction information, and the patient information is read from the medication instruction storage unit. And a collation unit that collates whether or not the information matches the patient information read from the tag assigned to each patient.
It includes an output control unit that outputs the result of the collation.

The medication support device includes a photographing device that photographs a display field on which setting information of the device is displayed.
The device setting detection unit may recognize the setting information of the device from the captured image of the device captured by the photographing device.

The medication support device includes a reading unit that reads display position information indicating the position of a display field on which setting information of the device is displayed from a tag attached to the device.
The device setting detection unit may specify an area corresponding to the display column in the captured image based on the display position information, and recognize the setting information of the device from the area corresponding to the display column.

The medication support device includes a drug information reading unit that reads identification information added to each drug when mixing a plurality of drugs based on the medication instruction information for the patient.
The identification information of each drug is stored as the mixed injection information in the storage unit of the tag attached to the drug container, or the identification information indicated by the tag attached to the drug container and the identification information of each drug are mixed injection. A mixed injection information writing unit that stores information in the mixed injection information storage unit,
May be provided.

The collation unit reads out the medical history corresponding to the patient information from the medical history storage unit that stores the medical history of each patient, and determines whether or not a contraindicated drug for the medical history of the patient is included in the mixed injection information. You may.

The collation unit obtains the interval or order between the medication based on the medication instruction information and the previous medication based on the medication history of the patient, and the interval or order obtained from the medication history is specified in the medication instruction information. It may be determined whether or not it conforms to the interval or order.
The medication support device further includes a vital detection unit for detecting the vital signs of the patient.
The collation unit may collate whether or not the vital signs satisfy the conditions of the vital signs specified in the medication instruction information.
Further, in order to solve the above problems, the medication support method of the present invention is used.
The step of reading patient information about a patient from the tags assigned to the patient receiving the drug, and
The mixed injection information including the information indicating the drug contained in the drug container and the identification information identifying the medication instruction information based on the medication instruction information for the patient is read from the tag attached to the drug container, or the mixed injection information. The step of acquiring the mixed injection information including the identification information read from the drug container by referring to the mixed injection information storage unit that stores the above.
The medication instruction storage unit that stores the medication instruction information for each patient in association with the identification information and the patient information is referred to, and the identification information read from the tag attached to the drug container and the corresponding medication instruction information and patient information. And the step to read
A step of detecting device setting information from a device to be used based on the medication instruction information, and
The medication instruction information read from the medication instruction storage unit matches the mixed injection information, the setting information matches the medication instruction information, and the patient information read from the medication instruction storage unit is assigned to each patient. The step of collating whether or not it matches the patient information read from the tag,
The step of outputting the collation result and
Is executed by the computer.

Further, the present invention may be a medication support program for causing a computer to execute the above medication support method. Further, the present invention may record this medication support program on a computer-readable recording medium. The function can be provided by causing a computer to read and execute a program of this recording medium.

Here, a recording medium that can be read by a computer or the like is a recording medium that can store information such as data and programs by electrical, magnetic, optical, mechanical, or chemical action and can be read from the computer or the like. To say. Among such recording media, those that can be removed from a computer or the like include, for example, flexible discs, optical magnetic discs, CDs (Compact Discs), CD-R / Ws, DVDs (Digital Versatile Disks), and Blu-ray (registered trademark) discs. There are memory cards such as (Blu-ray Disc), DAT, 8 mm tape, and flash memory. In addition, there are hard disks, ROMs (read-only memories), and the like as recording media fixed to computers and the like.

According to the present invention, it is possible to provide a technique for managing a prescribed drug so that it can be surely administered to a target patient.

FIG. 1 is a schematic view of the entire hospital information system (HIS). FIG. 2 is a schematic configuration diagram of a drug information server. FIG. 3 is a schematic configuration diagram of a medication support terminal. FIG. 4 is a diagram showing an example of a drug container. FIG. 5 is a schematic configuration diagram of the drug information tag. FIG. 6 is a diagram showing an example of an infusion pump. FIG. 7 is a diagram showing an example of a patient information tag. FIG. 8 is a diagram showing a data configuration example of patient information stored in the patient information tag. FIG. 9 is a diagram showing a data structure of medication instruction information stored in the drug information server. FIG. 10 is a diagram showing an example of device information stored in the device information storage unit of the drug information server 1. FIG. 11 is a diagram showing an example of an injection slip in which medication instruction information is printed out. FIG. 12 is a diagram showing a flow of the medication support method of the first embodiment executed by the medication support terminal at the time of mixed injection. FIG. 13 is a diagram showing a flow of a medication support method executed by the medication support terminal at the time of medication. FIG. 14 is a diagram showing a detailed flow of processing in which the medication support terminal detects device setting information. FIG. 15 is a diagram showing an example of a template used for a process of detecting device setting information. FIG. 16 is a diagram showing an example of a template used for a process of detecting device setting information. FIG. 17 is an explanatory diagram of a process of detecting device setting information from a captured image based on a template. FIG. 18 is a diagram showing a flow of a medication support method executed by the medication support terminal according to the medication support program after medication. FIG. 19 is a diagram showing a flow of a medication support method during mixed injection work. FIG. 20 is a diagram showing a flow of a medication support method at the time of medication in the first modification. FIG. 21 is a diagram showing an example of data of a contraindicated drug storage unit. FIG. 22 is a diagram showing an example of a device information tag attached to a device and display position information included in the device information tag. FIG. 23 is a diagram showing an example of a device information tag attached to a device and display position information included in the device information tag. FIG. 24 is a diagram showing a configuration of a medication support terminal according to the second embodiment. FIG. 25 is a diagram showing a flow of a medication support method executed by the medication support terminal according to the second embodiment at the time of medication. FIG. 26 is a diagram showing an example in which the name tag of a medical worker is used as an RF tag. FIG. 27 is an explanatory diagram of an authentication process when acquiring an ID of a medical worker. FIG. 28 is a schematic configuration diagram of the device. FIG. 29 is a diagram showing a flow of a medication support method executed by the medication support terminal at the time of medication.

Hereinafter, the medication management system according to the embodiment will be described with reference to the drawings. The configurations of the following embodiments are exemplary, and the medication management system is not limited to the configurations of the embodiments.
<Embodiment 1>
Hereinafter, the medication management system according to the first embodiment will be described with reference to the drawings of FIGS. 1 to 23.

"System configuration"
FIG. 1 is a schematic view of the entire hospital information system (HIS). As shown in FIG. 1, the HIS of the first embodiment has a medication management system 10, an electronic medical record system 20, and an inventory management system 30.

The electronic medical record system 20 is a system in which a doctor inputs medical examination findings, test results, prescriptions, and the like as medical records and electronically records them. The electronic medical record system 20 also functions as an ordering system for giving medication instructions and examination instructions. The electronic medical record system 20 includes an electronic medical record server 201 and an electronic medical record terminal 202, and when a doctor operates the electronic medical record terminal 202 to input a medication instruction, the electronic medical record terminal 202 transmits the medication instruction information via a network such as a LAN. It is transmitted to the electronic medical record server 201. The electronic medical record server 201 records the medication instruction information received from the electronic medical record terminal 202 in the electronic medical record, and transmits the medication instruction information to the medication management system 10 to order the medication. The medication instruction information includes at least information for identifying a patient to be dosed and information indicating a drug to be administered.

The inventory management system 30 manages the inventory of drugs and medical devices. For example, the inventory management system 30 subtracts the inventory quantity of the drug when the drug is consumed based on the medication instruction information, and orders the drug when the inventory quantity becomes less than a predetermined number. Then, the inventory management system 30 adds the number of stocks of the medicines when the medicines are delivered, and manages the medicines so that a predetermined number of stocks is secured for each medicine.

The medication management system 10 manages information on the drug prescribed to the patient, and information for confirmation at the time of mixed injection work and confirmation at the time of drug administration so that the prescribed drug is definitely administered to the target patient. I will provide a. The medication management system 10 includes a drug information server 1 that manages medication information, and a medication support terminal (also referred to as a medication support device) 2 that acquires medication information from the drug information server 1 via a wireless line. The medication support terminal 2 is carried by a medical worker such as a doctor or a nurse, connects to a network via a wireless access point 3 during mixed injection work or medication, and accesses the drug information server 1 to provide medication instruction information. Get and collate. For example, when a medical worker inputs information indicating a plurality of drugs mixedly injected into an infusion bag (hereinafter, also referred to as mixed injection information) into the medication support terminal 2, the medication support terminal 2 identifies the mixed injection information as a medication instruction. Write the information on the tag attached to the drug container (hereinafter, also referred to as the drug information tag).

Then, when the drug after the mixed injection is administered to the patient, the medication support terminal 2 acquires the medication instruction information corresponding to the identification information patient information of the medication instruction read from the drug information tag from the drug information server 1, and obtains the drug information. Collate with the mixed injection information read from the tag. Further, the medication support terminal 2 collates the patient information acquired from the drug information tag or the drug information server 1 with the patient information read from the patient information tag assigned to the patient. In this way, this medication management system supports to easily collate drug and patient information at the time of medication and reduce the confirmation work of medical staff.

FIG. 2 is a schematic configuration diagram of the drug information server 1. As shown in FIG. 2, the drug information server 1 includes an arithmetic processing unit 11 including a CPU (central processing unit), a main memory, and the like, a storage unit 12 that stores data and software for arithmetic processing, and an input / output interface 13. It is a computer equipped with a communication unit (CCU: Communication Control Unit) 14 and the like.

An input device such as a keyboard, a mouse, a reader of a storage medium (memory card or the like), a writing device of a display or a storage medium, and an output device such as a speaker are appropriately connected to the input / output interface 13.

The CCU 14 communicates with other computers via a network. The storage unit 12 is an auxiliary storage device such as a hard disk, and an operating system (OS) and application software (medication support program, etc.) are installed. The storage unit 12 stores medication instruction information for each patient and also functions as a medication instruction storage unit. In addition, the storage unit 12 stores information (device information) of the device used for medication, and also functions as a device information storage unit.

The arithmetic processing unit 11 appropriately reads the OS or application from the storage unit 12 and executes it, and arithmetically processes the information input from the input / output interface 13 and the CCU 14 and the information read from the storage unit 12, thereby performing medication information. It also functions as a receiving unit 112, a medication instruction notification unit 113, and a medication information response unit 114.

The medication information receiving unit 112 receives the medication instruction information from the electronic medical record system 20 and stores it in the medication instruction storage unit of the storage unit 12. Further, the medication information receiving unit 112 receives information indicating that the medication has been performed from the medication support terminal 2, stores the corresponding medication instruction in the medication instruction storage unit, and updates the medication instruction information. ..

When the medication instruction notification unit 113 receives the medication instruction information from the electronic medical record system 20, the medication instruction notification unit 113 transmits the medication instruction information to a terminal (not shown) of the pharmacy department. The pharmacy department prints out the received medication instruction information as an instruction sheet (injection sheet) as described later, and delivers the instructed drug to the ward with the injection sheet attached.

When the medication information response unit 114 receives an inquiry about medication instruction information from the medication support terminal 2, the medication information response unit 114 reads the medication instruction information from the medication instruction storage unit and returns it to the medication support terminal 2.

FIG. 3 is a schematic configuration diagram of the medication support terminal 2. As shown in FIG. 3, the medication support terminal 2 includes an arithmetic processing unit 21 including a CPU (central processing unit), a main memory, and the like, a storage unit 22 that stores data and software for arithmetic processing, and an input / output interface 23. It is a computer equipped with a communication unit (CCU: Communication Control Unit) 24 and the like.

The input / output interface 23 includes operation buttons, a reader for a storage medium (memory card, etc.), a touch panel, a barcode reader 231, an RF tag reader 232, an input device such as a camera (photographing device) 233, and a display. An output device such as a storage medium writing device, an RF tag writing device 234, a speaker, a vibrator, and an indicator light is connected. In the medication support terminal 2 of the first embodiment, the camera 233 and the barcode reader 231 are provided so that the shooting direction in which the subject is photographed by the camera 233 and the direction in which the barcode is read by the barcode reader 231 are substantially the same. ing. For example, the camera 233 and the barcode reader 231 are provided so that the optical axis of the photographing lens of the camera 233 and the axis that is the center of the light that the barcode reader 231 irradiates to the barcode to read the barcode are parallel to each other. As a result, when the shooting button of the camera 233 is pressed, shooting and reading of the barcode by the barcode reader 231 can be performed at the same time. When a two-dimensional barcode is used as the barcode, the camera 233 may capture the two-dimensional barcode and read the barcode information.

The CCU 24 communicates with other computers via a network. An operating system (OS) and application software (medication support program, etc.) are installed in the storage unit 22. In addition, the storage unit 22 stores data necessary for executing the medication support program.

The arithmetic processing unit 21 appropriately reads the OS or application from the storage unit 22 and executes it, and arithmetically processes the information input from the input / output interface 23 and the CCU 24 and the information read from the storage unit 22 to perform patient information. It also functions as a reading unit 211, a mixed injection information acquisition unit 212, a medication information acquisition unit 213, a drug information reading unit 214, a mixed injection information writing unit 215, a collation unit 216, a device setting detection unit 218, and an output control unit 217.

The patient information reading unit 211 controls the RF tag reading device 232 to read patient information about the patient from the tags assigned to each patient and stores the patient information in the storage unit 22.

The mixed injection information acquisition unit 212 reads information (mixed injection information) indicating the drug contained in the drug container from the tag attached to the drug container based on the medication instruction information for the patient.

The medication information acquisition unit 213 reads the medication instruction information from the medication instruction storage unit of the drug information server 1. For example, the identification information of the medication instruction and the corresponding medication instruction information are read out at the time of mixed injection or medication.

The drug information reading unit 214 acquires identification information (drug ID) of the drug from the barcode or RF tag attached to each drug. For example, at the time of mixed injection work, the drug information reading unit 214 obtains information on the drugs mixed in the drug container by sequentially reading the barcode printed on the exterior of each drug to be mixed. As for the drug ID, it is sufficient if the drug name and ingredient can be specified. For example, the Japanese standard product classification number, drug efficacy classification number, drug price standard listed drug code, unified product code, JAN code, approval number, JAPIC code, HOT number, ATC classification are used. Be done. The medication management system of the present embodiment uses a JAN code, and the sales packaging unit of the drug is specified by reading the JAN code attached to the exterior of the drug. The information on the sales packaging unit includes the drug name and ingredients as well as the content per sales packaging unit.

The mixed injection information writing unit 215 controls the RF tag writing device 234 to store the identification information of each drug read by the drug information reading unit 214 in the tag storage unit attached to the drug container as the mixed injection information. Let me.

The device setting detection unit 218 detects device setting information such as the flow rate and the planned amount of the infusion pump from the image taken by the camera (photographing device) 233.

The collation unit 216 collates whether or not the medication instruction information read from the medication instruction storage unit of the drug information server 1 and the mixed injection information read from the drug information tag match at the time of medication. Further, the collating unit collates the patient information acquired from the drug information tag or the medication instruction storage unit of the drug information server 1 with the patient information read from the patient information tag assigned to the patient. Further, the collation unit collates whether or not the device setting information detected by the device setting detection unit 218 matches the medication instruction information.

The output control unit 217 outputs the collation result by the collation unit 216 from the display, the speaker, the vibrator, the indicator lamp and the like. For example, if the medication instruction information and the mixed injection information do not match as a result of the collation by the collation unit 216, the output control unit 217 displays a warning message on the display and outputs a warning sound from the speaker. The output by the output control unit 217 is not limited to the display output and the sound output, and may be vibration by a vibrator, light emission by an indicator lamp, print output, writing to a recording medium, transmission to another computer, or the like.
Also works as.

FIG. 4 is a diagram showing an example of a drug container. The drug container 5 is an infusion container in which the peripheral edge of the overlapped sheet material is sealed to form a bag shape, and the drug is stored inside the container surrounded by the peripheral edge and the sheet material. As shown in FIG. 4, the drug container 5 has a through hole 52 formed in a sealed portion on the upper part of the bag-shaped main body 51 for suspending the drug container 5 on a pedestal, and is housed in the lowermost part of the bag-shaped main body 51. An outlet 53, which is an outlet for the drug, is formed. Further, a drug information tag 54 is attached to the drug container 5.

The drug container 5 of the present embodiment may be any container in which the drug information tag 54 is attached to the container for accommodating the drug, and is not limited to the configuration shown in FIG. For example, it may be a hollow molded plastic bottle. Further, the drug container 5 may be a syringe used for a syringe pump to which a drug information tag 54 is attached.

The drug information tag 54 may be attached in a state where it can be handled integrally with the main body 51 which is a drug accommodating portion, and the attachment method thereof is not particularly limited. For example, the drug information tag 54 may be attached to the main body 51 with a band, a clip, or the like, or may be attached to the surface of the main body. The sheet material may be sealed with the drug information tag 54 sandwiched between the sheet materials, and the drug information tag 54 may be included in the sealed portion as shown in FIG. Here, it is desirable that the drug information tag 54 is attached to the seal portion of the main body 51, that is, the portion where the drug is not contained. As a result, mixed injection information can be transmitted and received without being affected by drugs such as infusions.

FIG. 5 is a schematic configuration diagram of the drug information tag 54. The drug information tag 54 uses the antenna 541, the receiving unit 542 that receives the mixed injection information via the antenna 541, the storage unit 543 that stores the received mixed injection information, and the mixed injection information read from the storage unit 543 as radio waves from the antenna 541. It is a so-called RF tag provided with a control unit 545 that controls reading and writing of mixed injection information to the transmission unit 544 and the storage unit 543 to be transmitted. The receiving unit 542, the storage unit 543, the transmitting unit 544, and the control unit 545 are configured as one IC chip 540.

The drug information tag 54 of the present embodiment transmits / receives mixed injection information in a passive manner using a radio wave of 2.4 GHz. By adopting the radio wave of such a high frequency (2.4 GHz), the antenna 541 can be shortened, and by adopting the passive method, the built-in battery is not required, so that the drug information tag 54 can be miniaturized. In addition, by adopting high frequency radio waves, the communication speed is high and high responsiveness can be obtained. Further, by adopting a high frequency radio wave, the straightness of the radio wave is high and the wraparound of the radio wave is small, so that the tag other than the tag to be read is not erroneously communicated, and high safety can be obtained. Not limited to this, the communication method of the drug information tag 54 and the frequency band used for communication may be any as long as they can transmit and receive mixed injection information. For example, the communication method may be a passive method or an active method. Further, the frequency band may be arbitrarily adopted from 130 to 135 Hz, 13.56 MHz, 433 MHz, 900 MHz band and the like.

FIG. 6 is a diagram showing an example of the infusion pump 6. As shown in FIG. 6, the infusion pump 6 includes an operating state indicator 61, a planned amount or integrated amount display field 62, a flow rate display field 63, an operation button (operation unit) 64, and a device information tag 65. There is.

The medical staff sets the infusion line 7 connected to the drug container 5 on the infusion pump 6, operates the operation button 64 to set the flow rate and the planned amount based on the medication instruction, and sets the planned amount and the planned amount in the display columns 62 and 63. After confirming that the flow rate is as instructed to administer and selecting start, the infusion pump 6 delivers the drug (medicine solution) in the infusion line at the set flow rate. The infusion pump 6 of the present embodiment is different from the conventional infusion pump in that it is provided with the device information tag 65. That is, by attaching the device information tag 65 to the conventional infusion pump, it can be used as the infusion pump 6 of this system. Therefore, since the configurations of the infusion pump 6 other than the drug information tag 54 are known, detailed description of the configuration for sending the drug at a predetermined flow rate and the like will be omitted. Further, by attaching the device information tag 65 to the conventional syringe pump, it can be used as a syringe pump of this system.

The device information tag 65 is a tag on which device information is recorded, and is a barcode in the present embodiment. The bar code as the device information tag 65 is recorded by coding (bar-coding) device identification information (device ID) as device information, for example. When the medical worker points the medication support terminal 2 toward the device 6 such as the infusion pump when checking the device information, the bar code reader 231 or the camera 233 reads the bar code, and the device setting detection unit 218 reads the read data. Decoding is performed to acquire the identification information of the device, and device information such as the device status, usage history, and model name corresponding to the identification information is read from the device information storage unit of the drug information server 1. Further, the device setting detection unit 218 identifies a display area of the flow rate and the planned amount from the image of the device taken by the camera based on the read model name, and acquires the device setting information from the display area. The details of the process of acquiring the device setting information will be described later.

FIG. 7 is a diagram showing an example of the patient information tag 4. The example of FIG. 7 shows an example in which the patient information tag 4 is attached to a patient's wrist or anklet like a bracelet or anklet. The patient information tag 4 is not limited to the shape shown in FIG. 7, and may be a necklace or the like that is hung on the neck, or a name tag or the like that is fastened to the chest or the like. The patient information tag 4 is preferably attached to the patient's body so that it will not be replaced carelessly, but the present invention is not limited to this, and the patient information tag 4 may be attached to an object around the patient such as a bed or a wall of a hospital room. Further, a mobile phone having a function of an RF tag or a medical examination ticket may be used as a patient information tag.
As shown in FIG. 6A, the patient information tag 4 has a belt-shaped belt 41 and a transmission / reception unit 42 for transmitting / receiving patient information.

The material of the belt 41 is not particularly limited, but it is desirable that the belt 41 has a strength that does not easily break and a flexibility that does not hurt the wearing body. For example, the material of the belt 41 may be a flexible synthetic resin. In particular, the material of the belt 41 is preferably silicone rubber, which is less likely to cause allergies to the skin in contact with it.

The patient name 43 and the barcode 44 are written on the surface of the belt 41 by sticking a sticker or printing with a label printer. The bar code 44 is a bar code of the patient identification information (hereinafter, also referred to as a patient ID) corresponding to the patient name 43. Further, the transmission / reception unit 42 is attached to the belt 41 so as to be fixed or detachable.

The transmission / reception unit 42 includes an antenna, a reception unit that receives patient information via the antenna, a storage unit that stores the received patient information, a transmission unit that transmits patient information read from the storage unit as radio waves, and a storage unit. It is a so-called RF tag provided with a control unit that controls reading and writing of patient information with respect to the patient, and the hardware configuration is the same as that of the drug information tag 54 of FIG.

The transmission / reception unit 42 of the present embodiment transmits / receives patient information in a passive manner using a radio wave of 2.4 GHz. Not limited to this, the communication method of the transmission / reception unit 42 and the frequency band used for communication may be any as long as they can transmit / receive patient information. For example, the communication method may be a passive method or an active method. Further, the frequency band may be arbitrarily adopted from 130 to 135 Hz, 13.56 MHz, 433 MHz, 900 MHz band and the like.

The patient information tag 4 is prepared as a tag for the patient, in which the patient name 43 and the barcode 44 are described using the information of the electronic medical record system 20 at the time of admission of the patient. The information medical worker confirms that the patient name 43 of the belt 41 belongs to the patient himself, wraps the belt 41 of the patient information tag 4 around the patient's wrist or ankle, and adheres both ends of the belt 41. , The patient information tag 4 is attached to the patient as a ring as shown in FIG. 4 (B). Then, by the operation of the medical staff, the medication support terminal 2 reads the barcode 44 with the barcode reader 231 and decodes the read data with the patient information reading unit 211 to acquire the patient ID, and obtains the patient ID. It is transmitted to the information tag 4 and stored in the storage unit of the transmission / reception unit 42.

<< Data structure >>
FIG. 8 is a diagram showing a data configuration example of patient information stored in the patient information tag 4. As shown in FIG. 8, the patient information has data such as patient ID, medication history, medical history, and medical condition.

The patient ID is identification information for uniquely identifying the patient, and is issued for each patient by the electronic medical record system 20 in the present embodiment.

The medication history is a history of the drug administered to the patient specified by the patient ID, and has a medication instruction ID, a drug ID, a dosage, a medication execution date and time, and a medication completion date and time. Here, the medication instruction ID is identification information for uniquely identifying the medication instruction. The drug ID is information for uniquely identifying a drug included in a medication instruction, and is, for example, a unified product code or a JAN (Japanese Article Number) code. The dosage is the dose of the drug included in the medication instruction. In the present embodiment, the sales packaging unit of the drug is specified by the drug ID, and the dose is indicated by how many of these are used. For example, when "drug A 20 mg" is specified by the drug ID, the dose specifies how many sales packaging units of this drug are used, such as "1 bottle" and "2 bottles". The medication administration date and time is the date and time when the medication was administered to the patient based on the medication instruction.

The medical history is a history of the patient's disease specified by the patient ID, and has a disease name, treatment content, and treatment date. Here, the disease name is the name of the disease suffered by the patient, the treatment content is information indicating the content of treatment for the disease, and the treatment date is information indicating the date of the treatment.

FIG. 9 is a diagram showing a data structure of medication instruction information stored in the drug information server 1. As shown in FIG. 9, the medication instruction information includes the medication instruction ID, the patient ID, the administration method, the drug ID, the dosage, the flow rate, the medication order, the medication date and time, the medication execution date and time, the enforcer ID, and the mixed injection worker ID. It has data such as status.

The medication instruction ID, patient ID, drug ID, dosage, and medication execution date and time are the same as those described in the medication history of FIG. The administration method is information indicating the administration method of the drug, such as intramuscular injection, intravenous injection, intravenous drip infusion, and continuous intravenous injection. The administration method may include information indicating the device to be used, such as intravenous drip infusion (using an infusion pump) when the infusion pump 6 or a syringe pump is used. The flow rate is information indicating the dose per unit time when the drug is administered by intravenous drip infusion, and is indicated by, for example, mL / h. The dosing date and time is the scheduled dosing date and time specified by the dosing instruction. The practitioner ID is identification information indicating the medical worker who performed the medication, and the mixed injection worker ID is identification information indicating the medical worker who performed the mixed injection work. The status is information indicating the status related to the medication instruction, and indicates the status such as change, discontinuation, mixed injection, and administration. For example, when a change in the content of a medication instruction such as a drug ID or dosage is input from the electronic medical record terminal 202, this change is notified from the electronic medical record server 201 to the drug information server 1, and the drug ID in the medication instruction storage unit or The content of the medication instruction such as the dosage is updated and "change" is recorded as the status. Further, when the discontinuation of the medication instruction is input from the electronic medical record terminal 202, the discontinuation information is notified from the electronic medical record server 201 to the drug information server 1, the drug ID and the dosage in the medication instruction storage unit are deleted, and the status is changed. "Cancellation" is recorded as. The dosing order is information indicating this order when the dosing order is specified when chemotherapy such as an anticancer drug is performed. For example, the medication instruction IDs are recorded in the order of administration as in [2002, 2004, 2005], the drug with the medication instruction ID = 2002 is first administered, then the drug with the medication instruction ID = 2004 is administered, and then the medication instruction ID is administered. = Indicates that 2005 drug is administered.

FIG. 10 is a diagram showing an example of device information stored in the device information storage unit of the drug information server 1. As shown in FIG. 10, the device information includes, for example, information such as a device ID, a device status, a usage history, and a model name.

The device status is information indicating the status of the device such as normal, during failure, and inspection required. The usage history is information such as identification information of a medical worker who has used the device and the date and time of use. The model name is information that identifies the type of the device, and in this example, is information such as a manufacturer name and a model name.

The device ID and model name are registered in the device information storage unit in advance, and the usage history and device status are registered from the medication support terminal 2 to the drug information server 1 when the device is used. For example, when a medical worker discovers that the infusion pump 6 or the syringe pump is out of order or needs to be inspected, he / she selects input of device information from the menu (not shown) of the medication support terminal 2, and then selects the input of device information as an input item. When failure or inspection is selected and writing is selected, the medication support terminal 2 transmits the device status indicating the failure or inspection as device information to the drug information server 1 by the CCU 24 and stores it in the device information storage unit. Further, the drug information server 1 may integrate the usage time of each device based on the usage history, and when the usage time reaches a predetermined value, rewrite the device state as an inspection requirement to prompt the inspection. When the input indicating that the inspection has been completed is performed, the drug information server 1 normally rewrites the device state and resets the usage time.

《Medication support method》
FIG. 11 is a diagram showing an example of an injection slip in which medication instruction information is printed out, and FIG. 12 is a view showing medication executed by the medication support terminal 2 according to a medication support program when a medical worker performs mixed injection work based on the injection slip. It is a figure which shows the flow of the support method.

As shown in FIG. 11, the injection slip 8 has a medication instruction ID 81, a barcode 80, a patient name 82, an administration method 83, a drug name 84, a dosage 85, a dosing date 86, a dosing time 87, a flow rate 88, and a dosing order. 89 is described. The electronic medical record terminal 202 has a drug table in which the drug name of each drug and the drug ID are stored in association with each other, and when the injection slip 8 is output, the drug ID corresponding to the drug ID in the medication instruction information is used as the drug. Read from the table and print. Similarly, when the electronic medical record terminal 202 outputs the injection slip 8, the patient ID corresponding to the medication instruction information and the patient name corresponding to the patient name are acquired from the electronic medical record server 201 and printed.

The medical worker (mixed injection worker) who performs the mixed injection work receives the medicine to be mixed injection together with the injection slip 8 from the pharmacy department. When the mixed injection worker operates the medication support terminal 2 and selects mixed injection support from the menu screen (not shown), the medication support terminal 2 starts the process of FIG.

The medication support terminal 2 first displays a message such as "Please read the barcode of the mixed injection worker" to prompt the reading of the identification information indicating the mixed injection worker, and the mixed injection worker is attached to the name tag or the like. When the barcode reader 231 of the medication support terminal 2 is pointed at the barcode (not shown), the medication support terminal 2 reads and decodes the barcode to acquire the identification information (mixed injection worker ID) of the mixed injection worker (mixed injection worker ID). Step S10).

Next, the medication support terminal 2 displays a message such as "Please read the barcode of the medication instruction" to prompt the reader to read the barcode 80 written on the injection slip 8, and the mixed injection operator responds to this message. Directs the barcode reader 231 of the medication support terminal 2 toward the barcode 80, and the medication support terminal 2 reads and decodes the barcode 80 to acquire the medication instruction ID (step S20).

The medication support terminal 2 that has acquired the medication instruction ID refers to the medication instruction storage unit of the drug information server 1, confirms the status corresponding to the medication instruction ID, and determines whether the medication instruction is valid, that is, changes or discontinues. It is confirmed whether or not it is (step S25), and if it is not valid, the process is terminated (step S25, No). For example, if the patient's condition changes after the injection slip 8 and the drug are dispensed from the pharmacy department, and the status such as change or discontinuation is recorded in the medication instruction information, the mixed injection is stopped, and the mixed injection worker uses the injection slip. 8 and the drug are returned to the pharmacy department.

On the other hand, if the medication instruction is valid, the medication instruction information corresponding to the medication instruction ID is read from the medication instruction storage unit of the drug information server 1, the drug ID and the dosage are extracted from the medication instruction information, and the mixed injection schedule list is created. Generate (step S30).

Then, when the mixed injection worker holds the barcode of the drug to be mixedly injected over the barcode reader 231 of the medication support terminal 2, the medication support terminal 2 reads the barcode of the drug to obtain the drug ID (step S40) and performs the mixed injection. It is determined whether or not it matches the drug ID in the schedule list (step S50).

When the drug ID read from the drug and the drug ID in the mixed injection list do not match (step S50, No), the medication support terminal 2 outputs a sound or message indicating an error and returns to step S40 (step S60). ). On the other hand, when the drug ID read from the drug and the drug ID in the mixed injection list match (step S50, Yes), the medication support terminal 2 outputs a sound, a message, or the like indicating that the drug is appropriate. The drug ID is removed from the mixed injection schedule list (step S70), and it is determined whether or not the drug ID has disappeared from the mixed injection schedule list, that is, whether or not the mixed injection of all the drugs has been completed (step S80).

When the mixed injection is not completed (step S80, No), the medication support terminal 2 is set to step S.
Returning to 40, when the mixed injection is completed (step S80, Yes), the drug ID, patient name, medication instruction ID, mixed injection worker ID, etc. of the mixed drug are written in the drug information tag 54 as mixed injection information (step S90). Further, the medication support terminal 2 writes the mixed injection worker ID and the status indicating that the mixed injection has been completed in the medication instruction storage unit of the drug information server 1, and notifies the inventory management system 30 of the drug ID of each drug mixedly injected. (Step S100), the process of FIG. 12 is completed.

As described above, in the present embodiment, since the information on the mixed-injected drug is recorded in the drug information tag 54, it is easy to confirm the drug in the drug container at the time of performing the infusion intravenous injection. In addition, since the effectiveness of the medication instruction is confirmed during the mixed injection work, the mixed injection work will not be accidentally proceeded when there is a change or the like. Further, since the inventory management system 30 is notified of the mixed injection of the chemicals at the time of the mixed injection work, the inventory management of the chemicals can be performed accurately. For example, when the inventory management system records that a drug has been consumed by administering the drug to a patient, if there is a change after the mixed injection and the drug is not administered to the patient, the consumption is not recorded and the inventory is recorded. May cause an error. Therefore, in the present embodiment, the inventory management system 30 records that the drug has been consumed due to the mixed injection, so that the inventory can be managed accurately.

When the mixed injection work is completed and the status indicating that the mixed injection has been completed is written in the drug information server 1, the drug information server 1 identifies the patient to whom the drug is administered based on the medication instruction information. Then, the person in charge registered in advance as a medical worker who administers the drug to the patient, for example, the ID of the nurse in charge is read from the storage unit, and finally instructed to the medication support terminal 2 to which the person in charge is logged in. Send information to instruct medication. FIG. 13 is a diagram showing a flow of a medication support method executed by the medication support terminal 2 according to the medication support program at the time of medication.

When the medical worker (executor) performing the medication operates the medication support terminal 2 and selects drug administration from the menu screen (not shown), the medication support terminal 2 starts the process of FIG.

The medication support terminal 2 first displays a message such as "Please read the information to be checked", and prompts the reader to read the identification information indicating the person who performed the intravenous drip injection, the mixed injection information, the patient information, and the device information ( Step S110). In response to this, when the enforcer points the medication support terminal 2 so as to read each information from information sources such as a name tag, a drug information tag 54, and a patient information tag 4, the medication support terminal 2 reads a barcode reader or a tag. Information is read by the device and the camera 233 (step S115), and the type of the information is determined (step S120). The information to be checked, such as the practitioner's identification information, mixed injection information, patient information, and device information, includes information (type code) indicating the type of these information. For example, each identification information includes a specific code such as IN for mixed injection information and MA for device information. In addition, the format of each information is identified, such as 10 digits for patient information, 8 digits for identification information of medical staff (executor), and hyphens between the first 4 digits and the second 6 digits for device information. It may be a code. As a result, when the medication support terminal 2 reads the information to be checked, it determines whether the type of the information is, for example, the identification information of the enforcer, the mixed injection information, the patient information, or the device information, based on the type code. judge.

For example, when the enforcer points the barcode reader 231 of the medication support terminal 2 at the barcode (not shown) attached to the name tag, the medication support terminal 2 reads the barcode (step S115), and the information of this barcode is read. When it is determined to be the identification information of the medical worker (step S120), this identification information is stored in the memory as the performer ID (step S130).

Further, when the enforcer points the reading device 232 of the medication support terminal 2 at the drug information tag 54 attached to the drug container, the medication support terminal 2 reads the drug information tag 54 (step S115), and this information is combined with the mixed injection information. When the determination is made (step S120), the medication instruction ID, the patient ID, the administration method, and the drug ID as mixed injection information are stored in the memory (step S140).

Similarly, when the practitioner points the reading device 232 of the medication support terminal 2 at the patient information tag 4, the medication support terminal 2 reads the patient information tag 4 and determines that this information is patient information (step S120). The patient ID is stored in the memory as patient information (step S150).

Further, when the enforcer points the medication support terminal 2 at the device such as the infusion pump 6 and presses the image of the camera 233, the camera 233 captures the image of the infusion pump 6 and the barcode reader 231 captures the device information tag 65. (Step S115), when it is determined that this information is the device ID (step S120), the drug information server 1 is accessed and information on the device status and model corresponding to the device ID is acquired from the device information storage unit. Then, the device ID, the device status, and the model name are stored in the memory as device information (step S160).

Then, the medication support terminal 2 reads information such as a flow rate, a planned amount, and an operating state of the device from the captured image of the infusion pump 6 and stores it in the memory as device setting information (step S165).

When the medication support terminal 2 reads the information in steps S130 to S165, it determines whether or not the information to be checked is satisfied (step S170). When the medication support terminal 2 of the present embodiment reads, for example, the enforcer ID, mixed injection information, and patient information, it is determined that the information to be checked is satisfied. Then, when the use of a device such as the use of an infusion pump or the use of a syringe pump is specified as the administration method of the medication instruction information, the device information and the device setting information are provided in addition to the enforcer ID, mixed injection information, and patient information. It is determined that the information to be checked is satisfied when it is read.

If the information to be checked is not satisfied (step S170, No), the medication support terminal 2 returns to step S110 and repeats reading, and if the information to be checked is satisfied (step S170, Yes), the drug. The medication instruction information corresponding to the medication instruction ID read from the information tag 54 is acquired from the drug information server 1 (step S180). The medication support terminal 2 receives the medication instruction information when receiving the medication instruction from the drug information server 1, but obtains the latest medication instruction information again in step S180.

Next, the medication support terminal 2 determines whether or not each of the acquired information conforms to the medication conditions (step S190). Here, the medication condition is a condition for determining whether or not medication is possible. For example, the patient ID read from the drug information tag 54 or the patient ID of the medication instruction information acquired from the drug information server 1 and the patient information tag are read. It is the same as the patient ID.

In addition, the medication conditions are that the drug ID read from the drug information tag 54 and the drug ID acquired from the drug information server 1 match, the device state is normal, and the device setting state matches the medication instruction. Is. In the present embodiment, the medication support terminal 2 determines that the medication conditions are met when all of these conditions are satisfied (step S190).

It should be noted that the condition of whether the device state is normal and the condition of whether the device setting information matches the medication instruction need to be determined only when the use of the device is specified. Further, regarding the device setting information, in addition to the flow rate and the planned amount, the medication condition may be that there is no error in the operating state. For example, if there is no error display such as forgetting to close the lid of the infusion pump or the battery is low, it is considered to be compatible, and if there is an error display, it is considered to be non-conforming.

Then, when it is determined that the medication conditions are not met (steps S190, No), the medication support terminal 2 outputs a sound or a message indicating an error, ends the process of FIG. 13, and determines that the medication conditions are met. If so (step S190, Yes), the medication support terminal 2 outputs a sound or a message indicating that the medication conditions are met (step S210).

Further, the medication support terminal 2 transmits and stores information (start information) related to the start of medication to the drug information server 1 (step S220). For example, the medication support terminal 2 transmits the medication instruction ID, the enforcer ID, the medication execution date and time, and the device ID as start information to the drug information server 1, and the drug information server 1 matches the medication instruction ID in the medication instruction storage unit. The performer ID of the start information, the medication execution date and time, and the device ID are stored in the record. Further, the drug information server 1 stores the enforcer ID of the start information, the medication execution date and time, and the medication instruction ID in the record in which the device ID of the device information storage unit matches. Then, the medication support terminal 2 writes the enforcer ID, the medication instruction ID, the medication ID of the medication, and the medication execution date and time in the patient information tag 4 (step S230), and ends the process of FIG.

FIG. 14 is a diagram showing a detailed flow of a process in which the medication support terminal 2 detects device setting information in step S165.

First, the medication support terminal 2 reads out the template corresponding to the model information acquired in step S160 of FIG. 13 from the storage unit 22 (step S510). The template has shape information for specifying the shape of the device. For example, an infusion pump that may be used at the time of medication is photographed in advance for each model, and this photographed image is stored in the storage unit 22 as a template. .. When photographing the device, the display surface on which the setting information such as the flow rate, the planned amount, and the operating state is displayed is photographed. 15 and 16 are diagrams showing an example of a template. In FIGS. 15 and 16, 71 is an operating state display column, 72 is a planned amount display column, 73 is a flow rate display column 73, and the positions of display columns 71-73 in the captured image are shown by coordinates or the like. The information is display position information. The templates of FIGS. 15 and 16 are shown as images of the appearance of the infusion pump 6 for convenience, but any format may be used as long as the images can be compared. For example, the templates are extracted from the images shown in FIGS. 15 and 16, respectively. Data indicating feature points or vector data used in CAD or the like may be used.

Next, the medication support terminal 2 compares the template 70 with the captured image 60, extracts an image area similar to the template, that is, an image area of a portion showing the display surface of the device (step S520), and extracts the extracted image. The region is normalized (step S530). FIG. 17A shows an example of a captured image, and FIG. 17B shows an extracted image area. The image area of FIG. 17 (C) is normalized so that the position of the image area of FIG. 17 (B) and the display fields 71-73 in the template can be correlated. Here, normalization is processing such as rotation, enlargement, reduction, complementation, projective transformation, distortion correction, brightness correction, and contrast correction.

Based on the display position information, the medication support terminal 2 specifies the display area (display column) 71 of the operating state, the display area 72 of the planned amount, and the display area 73 of the flow rate on the normalized image (step S540). ..

Then, the medication support terminal 2 recognizes characters in each display area (display column) 71-73, and reads the flow rate, the planned amount, and the error code (operating state) displayed in each display area as device setting information ( Step S550).

The reading of the operating state is not limited to character recognition, and may be one that recognizes an indicator light, a symbol indicating an error, or the like. For example, when an error occurs as shown in the display field 71 of FIG. 15, when a specific indicator lamp 71A is lit to indicate an error status, the type of error is recognized according to the position of the lit indicator lamp. You may. If it is displayed in the operation status display column only in the case of an error, it does not specify the code or the type of error, but if there is a display, it is an error, and if there is no display, it is normal. May be recognized. Further, when the presence or absence of an error is specified by the display color of the display column, such as red in the case of an error and green in the case of normal, the information on the operating state such as error or normal may be recognized by this display color. ..

FIG. 18 is a diagram showing a flow of a medication support method (post-administration processing) executed by the medication support terminal 2 according to the medication support program after medication.

When a medical worker (confirmer) who confirms after administration operates the medication support terminal 2 and selects post-administration processing from the menu screen (not shown), the medication support terminal 2 starts the processing of FIG.

The medication support terminal 2 first displays a message such as "Please enter the identification information of the confirmer" and prompts the reader to read the identification information indicating the confirmer after the intravenous drip injection (step S310). In response to this, when the confirmer points the medication support terminal 2 at the barcode on the name tag, the medication support terminal 2 reads the confirmer ID with the barcode reader (step S320).

Next, the medication support terminal 2 displays a message such as "Have the medication been completed normally?" To prompt the input of whether or not the medication has been completed normally (step S330). It is determined whether or not the input by the confirmer is normal (step S340).

When it is input that the drug has been completed normally (step S340, Yes), a message such as "Write the end information" is displayed to prompt the user to write the information (end information) regarding the completion of the medication (step). S350). In response to this, when the confirmer points the medication support terminal 2 at the patient information tag 4 or the drug information tag 54, the medication support terminal 2 writes the end information in the patient information tag 4 by the tag writing device. Further, the medication support terminal 2 transmits the end information to the drug information server 1 and stores it (step S360). For example, the medication support terminal 2 uses the confirmer ID (identification information of the medical staff), the medication end time, the device ID of the device used for the medication, and the information indicating that the medication was completed as the end information in the patient information tag 4. Add to the medication history of. Similarly, the medication support terminal 2 adds the confirmer ID, the medication end time, the device ID, and the information indicating that the drug has been completed normally to the drug information tag 54 as the end information. Further, when the medication support terminal 2 transmits the medication instruction ID, the confirmer ID, the medication end date and time, the device ID, and the information indicating that the medication was completed normally to the drug information server 1, the drug information server 1 administers the medication. In the record in which the medication instruction ID of the instruction storage unit matches, the confirmer ID of the end information, the date and time of the end of medication, and the information indicating that the medication was completed normally are stored. Further, the drug information server 1 stores the confirmer ID of the end information, the medication end date and time, the medication instruction ID, and the information indicating that the end was normal in the record in which the device ID of the device information storage unit matches. In the first embodiment, the medication support terminal 2 writes the end information in the drug information tag 54, but the present invention is not limited to this, and when the end is normally completed, the drug information is prepared for disposal of the drug container. All information may be deleted from the tag 54. Here, the medication support terminal 2 may delete only specific information such as the patient ID and the drug ID from the drug information tag 54.

On the other hand, when there is an input indicating that it is not normal in step S340 (step S340, No), the input of information indicating a more detailed situation is urged and the input by the confirmer is accepted (step S370). For example, the confirmer inputs information (device status) indicating an abnormality of the device, such as a failure, inspection, error display, drug remaining even at the scheduled end time, abnormal fever, etc., and the medication support terminal 2 accepts as device information. In addition, the confirmer inputs information on the condition after medication such as changes in vital signs, deterioration of physical condition, edema around the puncture site, and vasculitis, and the medication support terminal 2 accepts it as patient information.

Then, the medication support terminal 2 displays a message such as "Please write the end information" and prompts the writing of the information regarding the abnormality of the patient or the device and the information (end information) regarding the completion of the medication (step S380). .. In response to this, when the confirmer points the medication support terminal 2 at the patient information tag 4 or the drug information tag 54, the medication support terminal 2 sends the end information to the patient information tag 4 or the drug information tag 54 by the tag writing device. Write. Further, the medication support terminal 2 transmits the end information to the drug information server 1 and stores it (step S390). For example, the medication support terminal 2 adds the confirmer ID (identification information of the medical staff) and the medication end time to the medication history of the patient information tag 4 as the end information, and the post-medication condition input in step S370. The patient information indicating the above is recorded in the patient information tag 4. Similarly, the medication support terminal 2 adds the confirmer ID and the medication end time to the drug information tag 54 as end information. Further, when the medication support terminal 2 transmits the medication instruction ID, the confirmer ID, the medication end date and time, the device ID and the device status as end information to the drug information server 1, the drug information server 1 sends the medication instruction ID of the medication instruction storage unit. The confirmer ID of the end information and the medication end date and time are stored in the record that matches. Further, the drug information server 1 stores the confirmer ID of the end information, the medication end date and time, the medication instruction ID, and the device status in the record in which the device ID of the device information storage unit matches. In the present embodiment, the end information is written in the drug information tag 54, but the end information may not be written in the drug information tag 54. Further, the medication support terminal 2 may delete unnecessary information such as a patient ID and a drug ID from the drug information tag 54.

<< Management of device information >>
As described above, by attaching the drug information tag 54 to each drug and storing the device information at the time of administration, it is possible to individually record the device used for the administration. By storing the information of the device used in the drug information tag attached to the container of each drug in this way, it is possible to verify which device was used for the medication (for example, infusion). Further, by storing the information of the device used for the medication in the patient information of the patient information tag 4, it is possible to verify which device was used for the medication (for example, infusion) for each patient.
By making it possible to verify the device used for medication at a later date and ensuring traceability in this way, it becomes easy to recover the drug or device when it is recalled and to investigate the cause when a problem occurs.
Further, by storing the device information of the device used for the medication in the medication instruction storage unit or the device information storage unit of the drug information server 1, the device information can be collectively managed. For example, the frequency of use and maintenance time for each device, the operating rate of the entire device, the failure rate, and the like can be obtained.
Furthermore, by storing the location of each device in the device information storage unit, it is possible to know where each device is, where the device needs repair, and whether there is a place where there is a shortage of usable devices. It can be confirmed from the device information.

<< Effect of the embodiment >>
As described above, according to the present embodiment, since the medication support terminal 2 collects the information to be checked at the time of medication and determines whether or not it conforms to the medication conditions, the check at the time of medication can be reliably performed and the prescription. It can be managed so that the prescribed drug can be definitely administered to the target patient. That is, the medication support terminal of the present embodiment supports the medication work by making it possible to reduce the check by the enforcer by performing the check at the time of medication.

Further, according to the present embodiment, since the information of the drug to be administered can be collated with the latest medication instruction information at the time of administration, it is possible to prevent accidental administration based on the changed or discontinued medication instruction.

Furthermore, by performing a check at the time of medication using the medication support terminal 2, information such as who, when, who, and what was administered can be recorded, and the check and recording can be performed at the same time. Efficiency is improved.

In the first embodiment, the identification information of the medical staff such as the mixed injection person, the person who administers the medication, and the confirmer is used as a barcode, and the medication support terminal 2 is read by the barcode reader, but the present invention is not limited to this. The identification information of the worker may be recorded in the RF tag and read by the reading device of the RF tag.

Further, in the first embodiment, the device information such as the device ID is used as a bar code, and the medication support terminal 2 is configured to read by the bar code reader. However, the present invention is not limited to this, and the device information is recorded in the RF tag and the FR tag is read. It may be configured to be read by a device. In this case, the device information tag 65 is an antenna, a receiving unit that receives device information via the antenna, a storage unit that stores the received device information, and a transmission that transmits the device information read from the storage unit as radio waves from the antenna. It is provided with a control unit that controls reading and writing of device information to the unit and storage unit. Since the hardware configuration of the device information tag 65 is the same as that of the drug information tag 54 of FIG. 5, the illustration is omitted. When the device information tag 65 is an RF tag, the device information tag 65 may store the device status as device information in addition to the device identification information (device ID). For example, when a medical worker discovers that the infusion pump 6 or the syringe pump is out of order or needs to be inspected, select the input of device information from the menu (not shown) of the medication support terminal 2, and then select the input of device information as an input item. When failure or inspection is selected and writing is selected, the medication support terminal 2 writes the device status indicating the failure or inspection as device information in the device information tag 65 of the infusion pump 6 by the RF tag writing device 234. As a result, the medication support terminal 2 can acquire the device status from the device information tag 65 without acquiring the device status from the drug information server 1 when performing a check at the time of medication.

<Modification example 1>
In the above-described first embodiment, the mixed injection information is recorded in the drug information tag added to the drug container, but the present modification 1 is not limited to this, and the present modification 1 has a configuration in which the mixed injection information is recorded in another device. In the present modification 1, since the other configurations are the same as those in the above-described first embodiment, the same elements are designated by the same reference numerals, and the description thereof is omitted again.

The device for storing the mixed injection information may be any device as long as the medication support terminal 2 can be connected via a network and can read and write the mixed injection information. In the present modification 1, the drug information server 1 is used as a device for storing mixed injection information, and the storage unit 12 functions as a drug information storage unit.

Further, in the present modification 1, it is sufficient that the medication instruction ID can be read from the drug container, and it is not necessary to write the drug ID or the like. Therefore, an RF tag that does not correspond to data writing or an RF tag having a slow data communication speed is used. This also increases the degree of freedom in configuring the system. Further, the tag attached to the drug container is not limited to the RF tag, and may be a barcode in which the medication instruction ID is coded. In the first modification, the electronic medical record terminal 202 of the drug department prints the bar-coded dosing instruction ID on the sticker paper with a printer, outputs the bar code sticker, and attaches the bar code sticker to the drug container.

FIG. 19 is a diagram showing a flow of a medication support method at the time of mixed injection work in the modified example 1, and FIG. 20 is a diagram showing a flow of a medication support method at the time of medication. As shown in FIG. 19, the process in which the medication support terminal 2 collects the mixed injection information in steps S10 to S80 is the same as the description of the first embodiment shown in FIG. 12, and the medication support terminal 2 uses the mixed injection information for the drug information. The process (step S90A) of storing in the mixed injection information storage unit of the drug information server 1 instead of writing in the tag is different.

Then, when the enforcer operates the medication support terminal 2 at the time of medication and selects drug administration from the menu screen (not shown), the medication support terminal 2 starts the process of FIG. 20.

The medication support terminal 2 first displays a message such as "Please read the information to be checked", and identifies the identification information indicating the person who performed the intravenous drip injection, the medication instruction ID attached to the drug container, the patient information, and the like. Prompt to read the device information (step S110). In response to this, when the enforcer points the medication support terminal 2 so as to read each information from information sources such as a name tag, a barcode of a drug container, and a patient information tag 4, the medication support terminal 2 becomes a barcode reader or a tag. Information is read by the reading device (step S115), and the type of the information is determined (step S120). The information to be checked, such as the practitioner's identification information, the medication instruction ID, the patient information, and the device information, includes a code (type code) indicating the type of the information. In addition, the format of each information is identified, such as 10 digits for patient information, 8 digits for identification information of medical staff (executor), and hyphens between the first 4 digits and the second 6 digits for device information. It may be a code. As a result, when the medication support terminal 2 reads the information to be checked, whether it is the type of the information based on the type code, for example, the identification information of the enforcer, the medication instruction ID, the patient information, or the device information. To judge.

For example, when the enforcer points the barcode reader 231 of the medication support terminal 2 at the barcode (not shown) attached to the name tag, the medication support terminal 2 reads the barcode, and the information of this barcode is used by the medical staff. When it is determined to be the identification information (step S120), the identification information is stored in the memory as the enforcer ID (step S130).

Further, when the enforcer points the barcode reader 231 of the medication support terminal 2 at the barcode attached to the drug container, the medication support terminal 2 reads the barcode. When the bar code information is determined to be the medication instruction ID (step S120), the medication support terminal 2 reads the mixed injection information including the medication instruction ID from the mixed injection information storage unit of the drug information server 1 and stores it in the memory (step S120). Step S140A). The subsequent processes for collating the information to be checked (steps S150 to S230) are the same as those in the above-described first embodiment shown in FIG.

As described above, according to this modification, the information on the drug mixed in the drug container can be recorded as the mixed injection information, while the tag attached to the drug container can be simplified.

<Modification 2>
In the above-described first embodiment, the patient ID of the medication instruction information and the patient ID read from the patient information tag match, and the drug ID read from the drug information tag 54 and the drug ID acquired from the drug information server 1 are matched. The medication conditions are the same and the device condition is normal, but the medication conditions are not limited to this and may be other conditions. For example, the medication condition may be that, in addition to the above conditions, the mixed injection information does not include a drug contraindicated for the patient's medical history.

FIG. 21 is a diagram showing an example of data of a contraindicated drug storage unit that stores contraindicated drugs for each disease. As shown in FIG. 21, the contraindicated drug storage unit stores the disease and the contraindicated drug in association with each other. For example, in the case of glaucoma, the drug ID of a drug having an anticholinergic effect, and in the case of aspirin asthma, the drug ID of a drug having a PG synthesis inhibitory effect, etc. In the second modification, these data are stored in the storage unit 12 of the drug information server 1, and the storage unit 12 functions as a contraindicated drug storage unit. Not limited to this, the storage unit 22 of the medication support terminal 2 may be stored, and the storage unit 22 may function as a contraindicated drug storage unit.

As for the medical history of the patient, the medical history corresponding to the patient ID read from the patient information tag 4 by the medication support terminal 2 may be acquired from the electronic medical record server 201, or the medical history of the patient is recorded in the patient information tag 4 in advance. , The medication support terminal 2 may be read from the patient information tag 4. That is, in this example, the electronic medical record server 201 and the patient information tag 4 function as a medical history storage unit that stores the medical history of the patient.

At the time of dosing, steps S110 to S180 of FIG. 13 are performed as described above to acquire information to be checked and dosing instruction information, and it is determined whether or not the information conforms to the dosing conditions (step S190). Here, the medication support terminal 2 of the present modification 2 reads the patient's medical history information from the patient information tag 4, reads the drug ID of the contraindicated drug corresponding to the disease name recorded in the medical history from the contraindicated drug storage unit, and reads the information. It is determined whether or not the drug ID of the contraindicated drug is included in the mixed injection information. When the drug ID of the contraindicated drug is included in the mixed injection information, it is determined that the medication condition is not met (step S190, No), an error is displayed, and the process of FIG. 21 is terminated (step S200). On the other hand, when the drug ID of the contraindicated drug is not included in the mixed injection information and other medication conditions are satisfied, it is determined that the medication conditions are met (steps S190, No), and the medication support terminal 2 conforms to the medication conditions. A sound or message indicating that the operation has been performed is output (step S210).

In addition, the medication support terminal 2 stores the enforcer ID and the medication execution date and time in the medication instruction storage unit of the drug information server 1 (step S220), and the patient information tag 4 stores the enforcer ID, the medication instruction ID, and the medication. The drug ID of the drug and the date and time of administration of the drug are written (step S230), and the process of FIG. 21 is completed.
As described above, according to the present modification 2, it is possible to determine whether or not to administer the medication according to the pre-existing condition of each patient.

Further, the medication condition may be one that determines whether or not the medication timing is predetermined. For example, when the dosing interval or order is specified in the dosing instruction, the dosing support terminal 2 has an interval from the previous dosing based on the dosing end time, the dosing instruction ID, and the dosing ID read from the patient information tag 4. Or may be determined whether or not the medication is administered in the specified order. The dosing condition of whether or not the predetermined dosing timing may be used instead of the presence or absence of a contraindicated drug according to the pre-existing condition, or may be used in combination.

<Modification example 3>
In the above-described first embodiment, the template has the display position information, but the present invention is not limited to this, and the device information tag 65 has the display position information, and the display fields 71-73 are based on the display position information of the device information tag 65. It may be configured to specify the position of. The other configurations are the same as those in the above-described embodiment. The device information tag 65 of the third modification has a relative positional relationship between the attachment position of the device information tag 65 and the position of the display columns 71-73 as display position information.

FIG. 22 is a diagram showing an example in which a device information tag 65 having display position information is attached to a device. FIG. 22A is an example in which the device information tag 65 is attached to each of the positions indicating the display columns 71-73, and FIG. 22B is an explanatory diagram of the device information included in the device information tag 65. In the example of FIG. 22 (A), the device information tag 65 is designated by the reference numerals 65A to 65F according to the attachment position. For example, the device information tag 65A is attached to the left side of the display field 71, the device information tag 65B is attached to the right side of the display field 71, the device information tag 65C is attached to the upper left of the display field 72, and the device information tag 65D is attached to the lower right of the display field 72. Was attached, and device information tags 65E and 65F were attached above and below the display field 73. Display position information indicating the positional relationship between the sticking position and the display column is recorded in each device information tag 65A to 65F as shown in the field 66 of FIG. 22 (B). For example, the display position information of the device information tag 65A indicates that the device information tag 65A is located on the left side of the display field 73, and the display position information of the device information tag 65B is such that the device information tag 65B is displayed in the display field 71. Indicates that it is located on the right side of. As a result, it can be seen that the area sandwiched between the device information tag 65A and the device information tag 65B is the display field 71.

When the device information tag 65 having the display position information is attached to the device and the medication support terminal 2 photographs the device with the camera 233 in step S115 of FIG. 13, FIG. 22 (A) is included in the captured image. ), Since the device information tags 65A to 65F are photographed, the medication support terminal 2 decodes the two-dimensional barcode (device information tags 65A to 65F) in the photographed image in step S165, and each device. The device setting information is acquired by recognizing the characters in the display fields 71-73 indicated by the display position information of the information tags 65A to 65F. For example, the medication support terminal 2 obtains the flow rate as the device setting information by recognizing the area (display column 73) sandwiched between the device information tag 65E and the device information tag 65F as characters. Similarly, the medication support terminal 2 obtains a planned amount as device setting information by character-recognizing the area (display field 72) sandwiched between the device information tag 65C and the device information tag 65D. Further, the medication support terminal 2 recognizes the error code, the state of the indicator light, the display color, and the like for the area (display column 71) sandwiched between the device information tag 65A and the device information tag 65B in the same manner as described above. Obtain the operating status as device setting information.

In the example of FIG. 22, the device information tag 65 is attached to two places sandwiching each display column 71-73, but the device information tag 65 may be attached to one place adjacent to each display column 71-73. .. For example, the device information tags 65B, 65D, 65F in FIG. 22A are omitted, and the device information tags 65A, 65C, 65E are attached. In this case, when the medication support terminal 2 decodes the device information tag 65A in step S165 and recognizes that the tag is located on the left side of the display field 71 from the display position information, the area on the right side of the device information tag 65A is recognized. Recognize the error code, indicator light status, display color, etc. and use it as device setting information. Similarly, when the device information tag 65C is decoded and the tag located at the upper left of the display field 72 is recognized from the display position information, characters are recognized for the lower right area of the device information tag 65C and the device setting information is planned. Get the amount. Even if the device information tag 65 attached in this way is one for each display field 71-73, the device setting information can be obtained by recognizing the adjacent area in the direction indicated by the display position information of the device information tag 65. .. In this case, when the camera 233 shoots the device, the acceleration sensor (not shown) detects the tilt of the camera at the time of shooting, corrects the tilt of the shot image based on this tilt, and specifies the top, bottom, left, and right. It may be configured to determine the direction indicated by the position information.

FIG. 23 (A) is an example in which the device information tag 65 is attached to the diagonal of the rectangular area surrounding each display field 71-73, and FIG. 23 (B) is an explanatory diagram of the device information included in the device information tag 65. Is. In the example of FIG. 23A, the device information tag 65 is designated by the reference numerals 65G and 65H according to the attachment position. FIG. 23A shows an example in which the device information tags 65G and 65H are attached diagonally to the rectangular area 67 surrounding each display field 71-73. As shown in FIG. 23B, the device information tags 65G and 65H have their respective identification information, coordinates, diagonal tag identification information (diagonal identification information), and the device ID of the attached device. The display position information is recorded. The display position information field 66 has an object name indicating each display field 71-73 and coordinates of each display field 71-73. Further, in the example of FIG. 23B, the coordinates of the device information tag 65G are (0,0), which is the origin, and the device information tag 65H indicated by the diagonal identification information is a diagonal tag.

When the device information tag 65 having the display position information is attached to the device in this way and the medication support terminal 2 photographs the device with the camera 233 in step S115 of FIG. 13, FIG. 23 (A) is included in the captured image. ), Since the device information tags 65G, 65H are photographed, the medication support terminal 2 decodes the two-dimensional barcode (device information tags 65G, 65H) in the photographed image in step S165, and FIG. 23 The area for recognizing the device setting information is specified based on the information shown in (B). For example, in the rectangular area 67 in the captured image with the device information tags 65G and 65H as diagonal points, the attachment position of the device information tag 65G is set as the origin (0,0), and the coordinates of the device information tag 65H are set as (100,100). ), And the display information in the display field 73 is recognized from the area of the coordinates (10,65) to (90,90). The medication support terminal 2 stores the type of information displayed in each display column 71-73 in association with the device ID and the object name (display column 71-73), as described above. Based on this correspondence, the medication support terminal 2 recognizes characters in the display field 73 whose device ID is MA0011, and acquires the flow rate as device setting information. Similarly, the medication support terminal 2 obtains a planned amount as device setting information by character-recognizing the areas indicated by the coordinates (10, 40) to (90, 65) of the display field 72. Further, the medication support terminal 2 recognizes the error code, the state of the indicator light, the display color, and the like for the area indicated by the coordinates (10, 10) to (90, 40) of the display column 71 in the same manner as described above. , Obtain the operating status as device setting information.

When shooting the device, if the device is shot according to the rectangle of the specified size displayed on the display unit, the size of the rectangular area 67 in the shot image becomes almost constant. In this case, the device information The attachment of the tag 65H may be omitted. Further, the size of the rectangular area 67 in the captured image is recognized from the size of the display fields 71-73, the size of the characters displayed in the display fields 71-73, etc., and is indicated by the coordinates of each display field 71-73. If the area to be specified can be specified, the attachment of the device information tag 65H may be omitted.

As described above, in the present modification 3, the position of the display field 71-73 is specified based on the attachment position of the device information tag 65 and the display position information, so that the display field 71-73 is not matched with the template. Can be specified and the processing speed can be improved.

In FIGS. 22 and 23, an example in which a barcode is used as the device information tag 65 is shown, but this modification is not limited to this, and an RF tag may be used as the device information tag 65. In this case, each display field 71-73 is specified based on the display position information read from each device information tag 65 by the RF tag reading device 232 and the attachment position of each device information tag 65 photographed by the camera 233. The correspondence between the attachment position of each device information tag 65 in the captured image and the display position information is the position of each device information tag 65 in the captured image and the position (coordinates, etc.) indicated by each display position information. It may be judged by collation. Markers such as symbols and figures that identify each device information tag 65 are described in each device information tag 65, and each device information tag 65 is identified according to the type of marker shown in the captured image, and the identified device information. The tag 65 and the display position information may be associated with each other.

<Embodiment 2>
In the above-described first embodiment, an example of reading the patient ID and medical history from the RF tag of the patient information is shown, but in the second embodiment, in addition to this, the vital sign of the patient is detected. In the first embodiment, since the other configurations are the same as those in the first embodiment, the same elements are designated by the same reference numerals, and the description thereof is omitted again.

FIG. 24 is a diagram showing the configuration of the medication support terminal 2 according to the second embodiment. As shown in FIG. 24, the medication support terminal 2 of the third embodiment includes a vital detection unit in addition to the configuration of the medication support terminal 2 of the first embodiment shown in FIG.

The vital detection unit detects the patient's pulse, heart rate, respiratory rate, blood pressure, body temperature, etc. as vital signs (vital information). For example, the vital detector can use networks such as LAN and Bluetooth (registered trademark) to provide information indicating pulse, heart rate, respiratory rate, blood pressure, and body temperature measured by an electrocardiogram monitor, saturation monitor (pulse oximeter), sphygmomanometer, and thermometer. ) Etc. via short-range wireless communication. Further, the vital detection unit may have a configuration in which a measuring device such as a sphygmomanometer or a thermometer is photographed by a camera and vital information such as blood pressure or body temperature is detected from the photographed image, similarly to the device setting detection unit of the second embodiment.

FIG. 25 is a diagram showing a flow of a medication support method executed by the medication support terminal 2 according to the third embodiment according to the medication support program at the time of medication.

When the medical worker (executor) performing the medication operates the medication support terminal 2 and selects drug administration from the menu screen (not shown), the medication support terminal 2 starts the process of FIG. 25.

The medication support terminal 2 first displays a message such as "Please read the information to be checked", and prompts the reader to read the identification information indicating the person who performed the intravenous drip injection, the mixed injection information, the patient information, and the device information ( Step S110). In response to this, when the enforcer points the medication support terminal 2 so as to read each information from information sources such as a name tag, a drug information tag 54, a patient information tag 4, and a vital sign measuring device, the medication support terminal 2 becomes a bar. Information is read by a code reader, a tag reader, or a camera (step S115), and the type of the information is determined (step S120).

Here, in order to acquire vital signs such as the patient's blood pressure and body temperature, the practitioner points the camera of the medication support terminal 2 toward the vital sign measuring device and presses the photographing button, and the medication support terminal 2 moves to the measuring device. An image is taken, and vital signs such as the patient's pulse, heart rate, respiratory rate, blood pressure, and body temperature are read from the image in the same manner as in the device information detection unit described above (step S115). When the vital sign measuring device can communicate via LAN, Bluetooth (registered trademark), or the like, the medication support terminal 2 communicates with the measuring device and receives the patient's vital sign (step S115). When the acquired information is pulse, heart rate, respiratory rate, blood pressure, and body temperature, the medication support terminal 2 determines that it is vital information (step S120) and stores it in the memory as vital information (step S167). The process of reading the performer ID, mixed injection information, patient information, and device information from the barcode or RF tag is the same as described above (steps S115 to S160).

When the medication support terminal 2 acquires the information in steps S115 to S165, it determines whether or not the information to be checked is satisfied (step S170).

If the information to be checked is not satisfied (step S170, No), the medication support terminal 2 returns to step S110 and repeats reading, and if the information to be checked is satisfied (step S170, Yes), the drug. The medication instruction information corresponding to the medication instruction ID read from the information tag 54 is acquired from the drug information server 1 (step S180). The medication support terminal 2 receives the medication instruction information when receiving the medication instruction from the drug information server 1, but obtains the latest medication instruction information again in step S180.

Next, the medication support terminal 2 determines whether or not each of the acquired information conforms to the medication conditions (step S190). In the third embodiment, in addition to the above-described processing of the first embodiment, whether or not the vital information is compatible with the medication instruction information is set as a medication condition. For example, it is administered when the body temperature is 38 ° C or higher, it cannot be administered when the body temperature is outside 36 ° C to 38 ° C, it is administered when the systolic blood pressure is less than 70 mmHg, and it is administered when the pulse is below a predetermined value. When there is an instruction regarding pulse, heart rate, respiratory rate, blood pressure, and body temperature in the medication instruction such as administration when there is abstinence within a predetermined time, it is determined whether or not the instruction is met.

Then, when it is determined that the medication conditions are not met (steps S190, No), the medication support terminal 2 outputs a sound or a message indicating an error, ends the process of FIG. 13, and determines that the medication conditions are met. If so (step S190, Yes), the medication support terminal 2 outputs a sound or a message indicating that the medication conditions are met (step S210).

In addition, the medication support terminal 2 stores the enforcer ID and the medication execution date and time in the medication instruction storage unit of the drug information server 1 (step S220), and the patient information tag 4 stores the enforcer ID, the medication instruction ID, and the medication. The drug ID of the drug, the date and time of administration, and vital information are written (step S230), and the process of FIG. 25 is completed.

As described above, according to the second embodiment, the vital information can also be read by the medication support terminal 2 to confirm whether or not the medication conditions are met, so that the medication work can be further reduced by the practitioner. Support.

In the second embodiment, an example in which a configuration for detecting the vital signs of a patient is added to the configuration of the first embodiment has been described, but this can be similarly applied to the modified example.

<Embodiment 3>
In the above-described first embodiment, an example in which the device information tag 65 is used as a barcode is shown, but the device information tag 65 is not limited to the barcode, and is an RFID tag provided with an IC chip capable of reading and writing device information, so-called. It may be an RF tag. In the third embodiment, since the other configurations are the same as those in the first embodiment, the same elements are designated by the same reference numerals, and the description thereof will be omitted again.

In the third embodiment, by adopting the RF tag for the device information tag 65, it is possible to write not only the device ID but also information such as the device status, usage history, and model name as the device information. Therefore, in the first embodiment, the medication support terminal 2 is configured to read the device ID from the device information tag 65 and acquire information such as the corresponding device status, usage history, and model name from the drug information server 1. However, in the third embodiment, the medication support terminal 2 reads the device information such as the device ID, the device status, the usage history, and the model name directly from the device information tag 65, and directly sends these to the device information tag 65. It is configured to write device information. In the third embodiment, the medication support terminal 2 reads the device information recorded on the device information tag 65 by the RF tag reading device 232, and the RF tag writing device 234 reads the device information on the device information tag 65. Write.

Next, the medication support method of the third embodiment will be described. In the third embodiment, since the basic flow of the process of performing the medication is the same as that of FIG. 13, the process at the time of administration will be described with reference to FIG.
When the medical worker (executor) performing the medication operates the medication support terminal 2 and selects drug administration from the menu screen (not shown), the medication support terminal 2 starts the process of FIG.

The medication support terminal 2 first displays a message such as "Please read the information to be checked", and prompts the reader to read the identification information indicating the person who performed the intravenous drip injection, the mixed injection information, the patient information, and the device information ( Step S110). In response to this, when the enforcer points the medication support terminal 2 so as to read each information from information sources such as a name tag, a drug information tag 54, and a patient information tag 4, the medication support terminal 2 reads a barcode reader or a tag. Information is read by the device and the camera 233 (step S115), and the type of the information is determined (step S120). The information to be checked, such as the practitioner's identification information, mixed injection information, patient information, and device information, includes information (type code) indicating the type of these information. For example, each information includes a specific code such as IN for mixed injection information and MA for device information. In addition, the format of each information is identified, such as 10 digits for patient information, 8 digits for identification information of medical staff (executor), and hyphens between the first 4 digits and the second 6 digits for device information. It may be a code. In this way, when the medication support terminal 2 reads the information to be checked, it determines whether the type of the information is, for example, the identification information of the enforcer, the mixed injection information, the patient information, or the device information, based on the type code. judge.

For example, when the enforcer points the barcode reader 231 of the medication support terminal 2 at the barcode (not shown) attached to the name tag, the medication support terminal 2 reads the barcode (step S115), and the information of this barcode is read. When it is determined to be the identification information of the medical worker (step S120), this identification information is stored in the memory as the performer ID (step S130).

Further, when the enforcer points the reading device 232 of the medication support terminal 2 at the drug information tag 54 attached to the drug container, the medication support terminal 2 reads the drug information tag 54 (step S115), and this information is combined with the mixed injection information. When it is determined (step S120), the medication instruction ID as mixed injection information
, Patient ID, administration method and drug ID are stored in the memory (step S140).

Similarly, when the practitioner points the reading device 232 of the medication support terminal 2 at the patient information tag 4, the medication support terminal 2 reads the patient information tag 4 and determines that this information is patient information (step S120). The patient ID is stored in the memory as patient information (step S150).

Further, when the practitioner points the medication support terminal 2 at a device such as the infusion pump 6 and presses the shooting button of the camera 233, the camera 233 captures an image of the infusion pump 6 and the reading device 232 starts from the device information tag 65. When the device information is read (step S115) and it is determined that this information is the device information (step S120), the device ID, the device status, the model name, etc. as the device information are stored in the memory (step S160).

Then, the medication support terminal 2 reads information such as a flow rate, a planned amount, and an operating state of the device from the captured image of the infusion pump 6 and stores it in the memory as device setting information (step S165).

When the medication support terminal 2 reads the information in steps S130 to S165, it determines whether or not the information to be checked is satisfied (step S170). When the medication support terminal 2 of the present embodiment reads, for example, the enforcer ID, mixed injection information, and patient information, it is determined that the information to be checked is satisfied. Then, when the use of a device such as the use of an infusion pump or the use of a syringe pump is specified as the administration method of the medication instruction information, the device information and the device setting information are provided in addition to the enforcer ID, mixed injection information, and patient information. It is determined that the information to be checked is satisfied when it is read.

If the information to be checked is not satisfied (step S170, No), the medication support terminal 2 returns to step S110 and repeats reading, and if the information to be checked is satisfied (step S170, Yes), the drug. The medication instruction information corresponding to the medication instruction ID read from the information tag 54 is acquired from the drug information server 1 (step S180). The medication support terminal 2 receives the medication instruction information when receiving the medication instruction from the drug information server 1, but obtains the latest medication instruction information again in step S180.

Next, the medication support terminal 2 determines whether or not each of the acquired information conforms to the medication conditions (step S190). Here, the medication condition is a condition for determining whether or not medication is possible. For example, the patient ID read from the drug information tag 54 or the patient ID of the medication instruction information acquired from the drug information server 1 and the patient information tag are read. It is the same as the patient ID.

In addition, the medication conditions are that the drug ID read from the drug information tag 54 and the drug ID acquired from the drug information server 1 match, the device state is normal, and the device setting state matches the medication instruction. Is. In the present embodiment, the medication support terminal 2 determines that the medication conditions are met when all of these conditions are satisfied (step S190).

It should be noted that the condition of whether the device state is normal and the condition of whether the device setting information matches the medication instruction need to be determined only when the use of the device is specified. Further, regarding the device setting information, in addition to the flow rate and the planned amount, the medication condition may be that there is no error in the operating state. For example, if there is no error display such as forgetting to close the lid of the infusion pump or the battery is low, it is considered to be compatible, and if there is an error display, it is considered to be non-conforming.

Then, when it is determined that the medication conditions are not met (steps S190, No), the medication support terminal 2 outputs a sound or a message indicating an error, ends the process of FIG. 13, and determines that the medication conditions are met. If so (step S190, Yes), the medication support terminal 2 outputs a sound or a message indicating that the medication conditions are met (step S210).

Further, the medication support terminal 2 transmits and stores information (start information) related to the start of medication to the drug information server 1 (step S220). For example, the medication support terminal 2 transmits the medication instruction ID, the enforcer ID, the medication execution date and time, and the device ID as start information to the drug information server 1, and the drug information server 1 matches the medication instruction ID in the medication instruction storage unit. The performer ID of the start information, the medication execution date and time, and the device ID are stored in the record. Further, the medication support terminal 2 writes the enforcer ID of the start information, the medication execution date and time, and the medication instruction ID in the device information tag 65. Then, the medication support terminal 2 writes the enforcer ID, the medication instruction ID, the medication ID of the medication, and the medication execution date and time in the patient information tag 4 (step S230), and ends the process of FIG.

Further, the medication support method (post-administration processing) executed by the medication support terminal 2 according to the medication support program after medication has the same basic flow as that of FIG. 18 described above, and thus will be described with reference to FIG.

When a medical worker (confirmer) who confirms after administration operates the medication support terminal 2 and selects post-administration processing from the menu screen (not shown), the medication support terminal 2 starts the processing of FIG.

The medication support terminal 2 first displays a message such as "Please enter the identification information of the confirmer" and prompts the reader to read the identification information indicating the confirmer after the intravenous drip injection (step S310). In response to this, when the confirmer points the medication support terminal 2 at the barcode on the name tag, the medication support terminal 2 reads the confirmer ID with the barcode reader (step S320).

Next, the medication support terminal 2 displays a message such as "Have the medication been completed normally?" To prompt the input of whether or not the medication has been completed normally (step S330). It is determined whether or not the input by the confirmer is normal (step S340).

When it is input that the drug has been completed normally (step S340, Yes), a message such as "Write the end information" is displayed to prompt the user to write the information (end information) regarding the completion of the medication (step). S350). In response to this, when the confirmer points the medication support terminal 2 at the patient information tag 4, the drug information tag 54, and the device information tag 65, the medication support terminal 2 sends the end information to the patient information tag 4 or the patient information tag 4 by the tag writing device. Write in the drug information tag 54 and the device information tag 65. Further, the medication support terminal 2 transmits the end information to the drug information server 1 and stores it (step S360). For example, the medication support terminal 2 uses the confirmer ID (identification information of the medical staff), the medication end time, the device ID of the device used for the medication, and the information indicating that the medication was completed as the end information in the patient information tag 4. Add to the medication history of. Similarly, the medication support terminal 2 adds the confirmer ID, the medication end time, the device ID, and the information indicating that the drug has been completed normally to the drug information tag 54 as the end information. Further, the medication support terminal 2 writes the confirmer ID, the medication end date and time, and the information indicating that the medication was completed normally in the device information tag 65 as the termination information. Further, when the medication support terminal 2 transmits the medication instruction ID, the confirmer ID, the medication end date and time, the device ID, and the information indicating that the medication was completed normally to the drug information server 1, the drug information server 1 administers the medication. In the record that matches the medication instruction ID of the instruction storage unit, the confirmer ID of the end information, the date and time of the end of the medication, the device ID of the device used for the medication, and the information indicating that the end was normal are stored. In the third embodiment, the medication support terminal 2 writes the end information in the drug information tag 54, but the present invention is not limited to this, and when the end is normally completed, the drug information is prepared for disposal of the drug container. All information may be deleted from the tag 54. Here, the medication support terminal 2 may delete only specific information such as the patient ID and the drug ID from the drug information tag 54.

On the other hand, when there is an input indicating that it is not normal in step S340 (step S340, No.
), Prompts the input of information indicating a more detailed situation, and accepts the input by the confirmer (step S370). For example, the confirmer inputs information (device status) indicating an abnormality of the device, such as a failure, inspection, error display, drug remaining even at the scheduled end time, abnormal fever, etc., and the medication support terminal 2 accepts as device information. In addition, the confirmer inputs information on the condition after medication such as changes in vital signs, deterioration of physical condition, edema around the puncture site, and vasculitis, and the medication support terminal 2 accepts it as patient information.

Then, the medication support terminal 2 displays a message such as "Please write the end information" and prompts the writing of the information regarding the abnormality of the patient or the device and the information (end information) regarding the completion of the medication (step S380). .. In response to this, when the confirmer points the medication support terminal 2 toward the patient information tag 4, the drug information tag 54, and the device information tag 65, the medication support terminal 2 sends the end information to the patient information tag 4 by the tag writing device 234. And drug information tag 54 and device information tag 65. Further, the medication support terminal 2 transmits the end information to the drug information server 1 and stores it (step S390). For example, the medication support terminal 2 adds the confirmer ID (identification information of the medical worker), the medication end time, and information on the abnormality to the medication history of the patient information tag 4 as the end information, and is input in step S370. Patient information indicating the condition after administration is recorded in the patient information tag 4. Similarly, the medication support terminal 2 adds the confirmer ID and the medication end time to the drug information tag 54 as end information. Further, the medication support terminal 2 writes the confirmer ID, the medication end date and time, and information on the abnormality in the device information tag 65 as the end information. Further, when the medication support terminal 2 transmits information on the medication instruction ID, the confirmer ID, the medication end date and time, the device ID, the device status, and the abnormality as the end information to the drug information server 1, the drug information server 1 sends the medication instruction storage unit. In the record that matches the medication instruction ID of the above, the confirmer ID of the end information, the medication end date and time, and the information regarding the abnormality are stored. In the third embodiment, the medication support terminal 2 writes the end information in the drug information tag 54, but the present invention is not limited to this, and all the information is sent from the drug information tag 54 in preparation for disposal of the drug container. You may delete it. Here, the medication support terminal 2 deletes only specific information such as the patient ID and the drug ID from the drug information tag 54, in other words, is necessary for processing the abnormality such as information on the abnormality and device information used for the medication. You may delete information other than the specified information.

<< Management of device information >>
As described above, by attaching the drug information tag 54 to each drug and storing the device information at the time of administration, it is possible to individually record the device used for the administration. By storing the information of the device used in the drug information tag attached to the container of each drug in this way, it is possible to verify which device was used for the medication (for example, infusion). Further, by storing the information of the device used for the medication in the patient information of the patient information tag 4, it is possible to verify which device was used for the medication (for example, infusion) for each patient.

By making it possible to verify the device used for medication at a later date and ensuring traceability in this way, it becomes easy to recover the drug or device when it is recalled and to investigate the cause when a problem occurs.

Further, by storing the device information of the device used for the medication in the device information tag 65, the device information can be managed. For example, the frequency of use, maintenance time, device status, etc. for each device can be obtained.

Further, by storing the device information of the device used for the medication in the device information storage unit of the drug information server 1, the device information can be collectively managed. For example, the operating rate, failure rate, etc. of the entire management device can be obtained. In addition, by storing the location of each device in the device information storage unit, it is possible to know where each device is, where the device needs repair, and whether there is a place where there is a shortage of usable devices. It can be confirmed from the device information.

Although the third embodiment shows an example of the configuration of the first embodiment in which the device information tag 65 is used as an RF tag and the device information is read / written to / from the device information tag 65, other configurations are shown. Can be similarly applied to the modification and the second embodiment.

<Embodiment 4>
In the above-described first embodiment, the identification information of the medical staff such as the mixed injection person, the medication performer, and the confirmer is described as a barcode on the name tag or the like, and the medication support terminal 2 is read by the barcode reader. However, the configuration may be such that the identification information of the medical staff is stored in a readable and writable RF tag (IC tag) and read by the medication support terminal 2 by an RFID reader. In the fourth embodiment, since the other configurations are the same as those in the first embodiment, the same elements are designated by the same reference numerals, and the description thereof will be omitted again.

FIG. 26 is a diagram showing an example in which the name tag of a medical worker is used as an RF tag. As shown in FIG. 26 (A), the RF tag (name tag) 90 has a photograph 901, a name 902, a hospital name 903, etc. of a medical worker written on the front. Further, as shown in FIG. 26B, the RF tag 90 includes an antenna 941, a receiving unit 942 that receives information via the antenna 941, a storage unit 943 that stores the received mixed injection information, and a storage unit. It includes a transmission unit 944 that transmits information read from 943 as radio waves from the antenna 941, and a control unit 945 that controls reading and writing of information to and from the storage unit 943. The receiving unit 942, the storage unit 943, the transmitting unit 944, and the control unit 945 are configured as one IC chip 940.

FIG. 27 is an explanatory diagram of an authentication process when the medication support terminal 2 acquires an ID of a medical worker. When the acquisition of the ID of the medical worker is instructed, the medication support terminal 2 transmits a radio wave for reading or generates a magnetic field by the RFID reading device (step S410). The RF tag 90 acquires electric power from the antenna 941 affected by the radio wave or magnetic field, operates the IC chip 940 by this electric power, and the control unit 945 reads the ID of the medical worker from the storage unit 943 and transmits it. The unit 944 transmits the ID as a change in radio waves or magnetic fields from the antenna 941.

The reader of the medication support terminal 2 acquires the ID of the medical worker by the change of the radio wave or the magnetic field from the RF tag 90 (step S420), and uses, for example, a random sequence as the encryption key (challenge) as the change of the radio wave or the magnetic field. Transmit (step S430). In the RF tag 90, which receives the change in the radio wave or the magnetic field by the antenna 941 and receives the challenge by the receiving unit 942, the control unit 945 reads the password from the storage unit 943, and the password and the challenge are combined to determine a predetermined RF tag 90. Create a response with an algorithm. For example, the control unit 945 processes a sequence of passwords and challenges in a one-way function, obtains a hash value, and uses it as a response.

Similarly, the medication support terminal 2 reads the password stored in the storage unit 22 as the authentication information of the medical worker, combines it with the challenge transmitted in step S430, calculates it with a predetermined algorithm, and calculates the calculation result for authentication ( Hash value) is obtained (step S440).

Then, the medication support terminal 2 receives a response from the RF tag 90 by the reading device (step S450), compares the received response with the calculation result of step S440, and determines whether or not they match (step S460). .. If these do not match (step S460, No), the medication support terminal 2 determines that the ID could not be acquired correctly, discards the ID acquired in step S420, and outputs an error (step S470), FIG. 27. Ends the processing of.

On the other hand, if the received response and the calculation result of step S440 match (step S460, Yes), the medication support terminal 2 determines that the ID has been acquired correctly and passes the ID acquired in step S420 to the subsequent processing. Is stored in a memory or the like (step S480), and the process of FIG. 27 is completed.

As described above, in the fourth embodiment, by adopting the RF tag 90 for the name tag of the medical worker, the duplication becomes more difficult than the bar code, and the security can be enhanced. In particular, when the RF tag 90 transmits the ID of the medical worker to the medication support terminal 2, the RF tag 90 is provided because the password and the like can be encrypted and transmitted instead of simply transmitting the ID. It is possible to prevent an unauthorized person from operating the terminal illegally.

For example, the medication support terminal 2 reads the RF tag 90 at the time of login and performs the authentication process of FIG. 27, and if the authentication is successful (step S460, Yes), the medication support terminal 2 can be logged in to operate the medication support terminal 2. If the authentication is not successful (step S460, No), the operation of the medication support terminal 2 is disabled without logging in. In this way, the ID of the medical worker is read from the RF tag 90 at the time of login and stored in the memory, and in the subsequent processing such as step S10 in FIG. 12 and step S115 in FIG. 13, the medical worker's ID is read from the memory of the medication support terminal 2. It may be configured to read the ID. Further, the medication support terminal 2 can read the medical worker's ID from the RF tag 90 not only at the time of login but also when reading the medical worker's ID in the subsequent processing such as step S10 in FIG. 12 and step S115 in FIG. May be configured to read and perform the authentication process of FIG. 27.

In the fourth embodiment, an example in which the name tag of the medical worker is the RF tag 90 is shown, but the present invention is not limited to this, and other forms such as an identification card, an ID card, and a bracelet may be used.

Although the fourth embodiment shows an example in which the ID of the medical worker is read from the RF tag 90 instead of the barcode in the configuration of the first embodiment, the present embodiment is not limited to the first embodiment. Also in the above-described second and third embodiments, the ID of the medical worker may be read from the RF tag 90 in the same manner.

<Embodiment 5>
In the above-described third embodiment, the device ID, device status, usage history, model name, etc. are read as device information from the device information tag as the RF tag, but in the fifth embodiment, the device setting is performed from the device information tag. The configuration is such that the information is read and the device setting information is written in the device information tag from the medication support terminal 2 and the device is set based on the device setting information. In the fifth embodiment, since the other configurations are the same as those in the first embodiment, the same elements are designated by the same reference numerals, and the description thereof will be omitted again.

FIG. 28 is a schematic configuration diagram of the device. As shown in FIG. 28, the device 6 used in the fifth embodiment includes a display unit 610, a function unit 620, a control circuit 630, an operation unit 64, and a device information tag 650.
The display unit 610 is a display element such as an LED or a liquid crystal display element, and displays setting information and the like. For example, in the case of the infusion pump of FIG. 6, the operating state indicator 61, the planned amount or integrated amount display column 62, and the flow rate display column 63 correspond to the display unit 610.

The function unit 620 performs an operation based on the setting information in order to exert the function of the device 6. The functional unit 620 is, for example, a drive mechanism for delivering the infusion solution at the flow rate specified in the setting information in the infusion pump, or a drive mechanism for driving the pusher (plunger) so as to have the flow rate specified in the setting information in the syringe pump. , A mechanism for atomizing and spraying a chemical solution in a nebulizer.

The control circuit 630 receives an input from the operation unit 64 and stores it in a memory, a control for displaying setting information or the like on the display unit 610, a control for operating the function unit 620 based on the setting information, and a device information tag 650. Controls such as reading information such as setting information from the device and writing information such as setting information to the device information tag 650 are performed.

The operation unit 64 is an operation button or switch operated by an operator such as a medication performer (medical worker), and is instructed to input setting information, start an operation, end an operation, or the like.
The device information tag 650 is an RF tag capable of reading and writing device information. The device information tag 650 uses the antenna 651, the receiving unit 652 that receives the mixed injection information via the antenna 651, the storage unit 653 that stores the received mixed injection information, and the mixed injection information read from the storage unit 653 as radio waves from the antenna 651. It is a so-called RF tag provided with a control unit 655 that controls reading and writing of mixed injection information to the transmission unit 654 and the storage unit 653 to be transmitted. The receiving unit 652, the storage unit 653, the transmitting unit 654, and the control unit 655 are configured as one IC chip 660. If the device information tag 650 of the present embodiment has a function as an RF tag capable of reading and writing device information and setting information, the antenna 651 and the IC chip 660 are housed in the housing of the device 6 and the tag is used. It does not have to have the appearance as.

The control circuit 630 of the device 6 and the device information tag 650 can communicate with each other, and the control circuit 630 can read the setting information from the device information tag 650 and can write the setting information from the control circuit 630 to the device information tag 650.

FIG. 29 is a diagram showing a flow of a medication support method executed by the medication support terminal 2 according to the medication support program at the time of medication.

When the medical worker (executor) performing the medication operates the medication support terminal 2 and selects drug administration from the menu screen (not shown), the medication support terminal 2 starts the process of FIG. 29.

The medication support terminal 2 first displays a message such as "Please read the information to be checked", and prompts the reader to read the identification information indicating the person who performed the intravenous drip injection, the mixed injection information, the patient information, and the device information ( Step S110). In response to this, when the enforcer points the medication support terminal 2 so as to read each information from information sources such as a name tag, a drug information tag 54, and a patient information tag 4, the medication support terminal 2 reads a barcode reader or a tag. Information is read by the device and the camera 233 (step S115), and the type of the information is determined (step S120). The information to be checked, such as the practitioner's identification information, mixed injection information, patient information, and device information, includes information (type code) indicating the type of these information. For example, each information includes a specific code such as IN for mixed injection information and MA for device information. In addition, the format of each information is identified, such as 10 digits for patient information, 8 digits for identification information of medical staff (executor), and hyphens between the first 4 digits and the second 6 digits for device information. It may be a code. In this way, when the medication support terminal 2 reads the information to be checked, it determines whether the type of the information is, for example, the identification information of the enforcer, the mixed injection information, the patient information, or the device information, based on the type code. judge.

For example, when the enforcer points the barcode reader 231 of the medication support terminal 2 at the barcode (not shown) attached to the name tag, the medication support terminal 2 reads the barcode (step S115), and the information of this barcode is read. When it is determined to be the identification information of the medical worker (step S120), this identification information is stored in the memory as the performer ID (step S130).

In addition, the enforcer attaches the drug information tag 54 to the drug container to the reader 23 of the medication support terminal 2.
When 2 is turned, when the medication support terminal 2 reads the drug information tag 54 (step S115) and determines that this information is mixed injection information (step S120), the medication instruction ID, patient ID, administration method and drug as mixed injection information. The ID is stored in the memory (step S140).

Similarly, when the practitioner points the reading device 232 of the medication support terminal 2 at the patient information tag 4, the medication support terminal 2 reads the patient information tag 4 and determines that this information is patient information (step S120). The patient ID is stored in the memory as patient information (step S150).

Further, when the enforcer brings the medication support terminal 2 close to the device such as the infusion pump 6, the reading device 232 reads the device information from the device information tag 65 (step S115), and determines that this information is the device information (step S115). Step S120), the device ID, the device status, the model name, and the like as the device information are stored in the memory (step S160).

When the medication support terminal 2 reads the information in steps S130 to S160, it determines whether or not the information to be checked is satisfied (step S170). When the medication support terminal 2 of the present embodiment reads, for example, the enforcer ID, mixed injection information, and patient information, it is determined that the information to be checked is satisfied. Then, when the use of a device such as the use of an infusion pump or the use of a syringe pump is specified as the administration method of the medication instruction information, the device information and the device setting information are provided in addition to the enforcer ID, mixed injection information, and patient information. It is determined that the information to be checked is satisfied when it is read.

If the information to be checked is not satisfied (step S170, No), the medication support terminal 2 returns to step S110 and repeats reading, and if the information to be checked is satisfied (step S170, Yes), the drug. The medication instruction information corresponding to the medication instruction ID read from the information tag 54 is acquired from the drug information server 1 (step S180). The medication support terminal 2 receives the medication instruction information when receiving the medication instruction from the drug information server 1, but obtains the latest medication instruction information again in step S180.

Next, the medication support terminal 2 writes the device setting information such as the flow rate and the planned amount of the infusion pump 6 in the device information tag 650 of the device 6 by the RFID writing device 234 among the medication instruction information acquired in step S180 ( Step S185). The device 6 in which the setting information is written reads the setting information from the device information tag 650, and sets the setting information such as the flow rate and the planned amount in the function unit 620. Further, the device 6 reads the setting information actually set in the function unit 620 and writes it in the device information tag 650. Further, the medication support terminal 2 reads the actually set setting information written in the device information tag 650 by the device 6 from the device information tag 650 (step S187).

Then, the medication support terminal 2 determines whether or not each of the acquired information conforms to the medication conditions (step S190). Here, the medication condition is a condition for determining whether or not medication is possible. For example, the patient ID read from the drug information tag 54 or the patient ID of the medication instruction information acquired from the drug information server 1 and the patient information tag are read. It is the same as the patient ID.

In addition, the medication conditions are that the drug ID read from the drug information tag 54 and the drug ID acquired from the drug information server 1 match, the device state is normal, and the device setting state matches the medication instruction. Is. In the present embodiment, the medication support terminal 2 determines that the medication conditions are met when all of these conditions are satisfied (step S190).

It should be noted that the condition of whether the device state is normal and the condition of whether the device setting information matches the medication instruction need to be determined only when the use of the device is specified. Further, regarding the device setting information, in addition to the flow rate and the planned amount, the medication condition may be that there is no error in the operating state. For example, if there is no error display such as forgetting to close the lid of the infusion pump or the battery is low, it is considered to be compatible, and if there is an error display, it is considered to be non-conforming.

Then, when it is determined that the medication conditions are not met (steps S190, No), the medication support terminal 2 outputs a sound or a message indicating an error, ends the process of FIG. 13, and determines that the medication conditions are met. If so (step S190, Yes), the medication support terminal 2 outputs a sound or a message indicating that the medication conditions are met (step S210).

Further, the medication support terminal 2 transmits and stores information (start information) related to the start of medication to the drug information server 1 (step S220). For example, the medication support terminal 2 transmits the medication instruction ID, the enforcer ID, the medication execution date and time, and the device ID as start information to the drug information server 1, and the drug information server 1 matches the medication instruction ID in the medication instruction storage unit. The performer ID of the start information, the medication execution date and time, and the device ID are stored in the record. Further, the medication support terminal 2 writes the enforcer ID of the start information, the medication execution date and time, and the medication instruction ID in the device information tag 65. Then, the medication support terminal 2 writes the enforcer ID, the medication instruction ID, the medication ID of the medication, and the medication execution date and time in the patient information tag 4 (step S230), and ends the process of FIG. 29.

As described above, according to the fifth embodiment, the medication support terminal 2 writes the setting information input as the medication instruction information to the device information tag 650 of the device 6, and the device 6 writes the setting information written to the device information tag 650. Since it can be set using the above, it is possible to prevent human error such as the person performing the medication making a mistake in setting the device 6.

Further, since the device 6 writes the setting state to the device information tag 650 and the medication support terminal 2 reads the setting information from the device information tag 650 and determines whether or not the setting state is met, the setting of the device 6 is set. You can definitely check it.

The device 6 is not limited to an infusion pump or a syringe pump, and may be a device used for medication, treatment, or examination, and may be a device whose settings can be electronically controlled. For example, the device 6 may be a nebulizer, an anesthesia machine, a respiratory system, a dialysis machine, or the like.

1 Drug information server 2 Medication support terminal 3 Wireless access point 4 Patient information tag 5 Drug container 6 Infusion pump 7 Infusion line 8 Injection slip 10 Medication management system 11 Calculation processing unit 12 Storage unit 13 Input / output interface 20 Electronic chart system 21 Calculation processing Unit 22 Storage unit 23 Input / output interface 30 Inventory management system 41 Belt 42 Transmission / reception unit 43 Patient name 44 Bar code 51 Main body 52 Through hole 53 Outlet 54 Drug information tag 61 Indicator 62 Scheduled amount display field 63 Flow rate display field 64 Operation Button 65 Device information tag 90 RF tag 112 Dosing information receiving unit 113 Dosing instruction notification unit 114 Dosing information response unit 201 Electronic chart server 202 Electronic chart terminal 211 Patient information reading unit 212 Mixed injection information acquisition unit 213 Dosing information acquisition unit 214 Drug information reading Unit 215 Mixed injection information writing unit 216 Matching unit 217 Output control unit 231 Bar code reader 232 Reading device 234 Writing device

Claims (10)

A patient information reader that reads patient information about the patient from the tags assigned to the patient to whom the drug is administered,
The mixed injection information including the information indicating the drug contained in the drug container and the identification information identifying the medication instruction information based on the medication instruction information for the patient is read from the tag attached to the drug container, or the mixed injection information. A mixed injection information acquisition unit that acquires mixed injection information including the identification information read from the drug container by referring to the mixed injection information storage unit that stores the information.
The medication instruction storage unit that stores the medication instruction information for each patient in association with the identification information and the patient information is referred to, and the identification information read from the tag attached to the drug container and the corresponding medication instruction information and patient information. The medication information acquisition unit that reads out
A device setting detection unit that detects device setting information from the device used based on the medication instruction information,
The patient information read from the medication instruction storage unit matches the mixed injection information, the setting information detected by the device setting detection unit matches the medication instruction information, and the patient information is read from the medication instruction storage unit. And a collation unit that collates whether or not the information matches the patient information read from the tag assigned to each patient.
An output control unit that outputs the result of the collation and
Medication support device equipped with. It is equipped with a photographing device that captures a display field in which setting information of the device is displayed.
The medication support device according to claim 1, wherein the device setting detection unit recognizes setting information of the device from a photographed image of the device photographed by the photographing device. It is provided with a reading unit that reads display position information indicating the position of a display field in which setting information of the device is displayed from a tag attached to the device.
The second aspect of claim 2, wherein the device setting detection unit identifies an area corresponding to a display column in the captured image based on the display position information, and recognizes the setting information of the device from the area corresponding to the display column. Medication support device. A drug information reading unit that reads identification information added to each drug when a plurality of drugs are mixed based on the medication instruction information for the patient.
The identification information of each drug is stored as the mixed injection information in the storage unit of the tag attached to the drug container, or the identification information indicated by the tag attached to the drug container and the identification information of each drug are mixed injection. A mixed injection information writing unit that stores information in the mixed injection information storage unit,
The medication support device according to any one of claims 1 to 3. The collating unit reads out the medical history corresponding to the patient information from the medical history storage unit that stores the medical history of each patient, and determines whether or not a contraindicated drug for the medical history of the patient is included in the mixed injection information. The medication support device according to any one of claims 1 to 4. The collation unit obtains the interval or order between the medication based on the medication instruction information and the previous medication based on the medication history of the patient, and the interval or order obtained from the medication history is specified in the medication instruction information. The medication support device according to any one of claims 1 to 5, which determines whether or not the interval or order is compatible. Further provided with a vital detection unit for detecting the vital signs of the patient,
The medication support device according to any one of claims 1 to 6, wherein the collation unit collates whether or not the vital signs satisfy the conditions of the vital signs specified in the medication instruction information. It has a drug information server and a medication support device that are connected via a network.
The drug information server includes a medication instruction storage unit that stores medication instruction information for each patient in association with identification information and patient information.
The medication support device
A patient information reader that reads patient information about the patient from the tags assigned to the patient to whom the drug is administered,
The mixed injection information including the information indicating the drug contained in the drug container and the identification information identifying the medication instruction information based on the medication instruction information for the patient is read from the tag attached to the drug container, or the mixed injection information. A mixed injection information acquisition unit that acquires mixed injection information including the identification information read from the drug container by referring to the mixed injection information storage unit that stores the information.
A medication information acquisition unit that refers to the medication instruction storage unit and reads out medication instruction information and patient information corresponding to the identification information read from the tag attached to the drug container.
A device setting detection unit that detects device setting information from the device used based on the medication instruction information,
The patient information read from the medication instruction storage unit matches the mixed injection information, the setting information detected by the device setting detection unit matches the medication instruction information, and the patient information is read from the medication instruction storage unit. And a collation unit that collates whether or not the information matches the patient information read from the tag assigned to each patient.
An output control unit that outputs the result of the collation and
Medication management system with. The step of reading patient information about a patient from the tags assigned to the patient receiving the drug, and
The mixed injection information including the information indicating the drug contained in the drug container and the identification information identifying the medication instruction information based on the medication instruction information for the patient is read from the tag attached to the drug container, or the mixed injection information. The step of acquiring the mixed injection information including the identification information read from the drug container by referring to the mixed injection information storage unit that stores the above.
The medication instruction storage unit that stores the medication instruction information for each patient in association with the identification information and the patient information is referred to, and the identification information read from the tag attached to the drug container and the corresponding medication instruction information and patient information. And the step to read
A step of detecting device setting information from a device to be used based on the medication instruction information, and
The medication instruction information read from the medication instruction storage unit matches the mixed injection information, the setting information matches the medication instruction information, and the patient information read from the medication instruction storage unit is assigned to each patient. The step of collating whether or not it matches the patient information read from the tag,
The step of outputting the collation result and
A medication support method performed by a computer. The step of reading patient information about a patient from the tags assigned to the patient receiving the drug, and
The mixed injection information including the information indicating the drug contained in the drug container and the identification information identifying the medication instruction information based on the medication instruction information for the patient is read from the tag attached to the drug container, or the mixed injection information. The step of acquiring the mixed injection information including the identification information read from the drug container by referring to the mixed injection information storage unit that stores the above.
The medication instruction storage unit that stores the medication instruction information for each patient in association with the identification information and the patient information is referred to, and the identification information read from the tag attached to the drug container and the corresponding medication instruction information and patient information. And the step to read
A step of detecting device setting information from a device to be used based on the medication instruction information, and
The medication instruction information read from the medication instruction storage unit matches the mixed injection information, the setting information matches the medication instruction information, and the patient information read from the medication instruction storage unit is assigned to each patient. The step of collating whether or not it matches the patient information read from the tag,
The step of outputting the collation result and
A medication support program that allows a computer to run.

Images