JP5553045B2 - Nursing support method and system, nurse support server device and program - Google Patents

Description

  The present invention relates to a nursing support method and system, a nursing support server device, and a program for preventing an injection or drip administration error in advance.

  Checking at the bedside (immediately before administration) is the most effective way to prevent injection and infusion errors. For this purpose, it is possible to check at the bedside using a database of an electronic medical record server that manages the order of injections and infusions and a PDA (Personal Digital Assistant) that is a personal digital assistant used by multiple nurses. There is a need.

  In such a system, generally, using the patient ID transmitted from the PDA, the PDA server obtains patient information from the electronic medical record server and transmits it to the PDA. Further, the PDA server obtains order information from the electronic medical record server using the order ID (order number) such as the instillation ID read by the PDA. Using this acquired order information, an administration error or the like is checked.

  Specifically, in order to prevent errors in administration of injection and infusion, nurses use PDAs to perform the following three procedures: “Nurse Barcode & Patient Barcode & Order Barcode (attached to infusion packs, etc.)” read. Then, the PDA server matches the user ID, the patient ID, and the order ID, which are nurse IDs determined based on each barcode read by the PDA, with the order information received from the electronic medical record server. Check for missed doses. On the other hand, since data records such as the number of excretion registrations need not be as robust as the administration error check, the PDA displays a list of patients in charge of the nurse by barcode authentication of the nurse. Then, the nurse selects a patient from the list and registers the data. That is, in the case of data registration such as the number of excretion, it is not necessary to read the barcode of the patient.

  The following are known as conventional techniques for preventing medication errors (for example, Patent Document 1). First, the nurse identification code, patient identification code, and medication identification code read by the identification code reading means are sent to the collation execution means of the nursing support server by the identification code sending means. The nurse identification code, patient identification code, and medication identification code are collated with information registered in the nurse master file, patient master file, and medication detail data file, and if they match, the process proceeds to the next operation. At the same time, when the medication identification code matches the predetermined condition, the medication administration information sending means sends the nurse information and the medication time to the medication administration information recording means and records them in the medication detail data file. If any one of the medication identification code and the patient / prescription injection / medication date does not match, the warning means issues a warning.

JP 2003-16182 A

The above-described conventional technique notifies a nurse about an order for which an injection has not been administered, and informs the nurse that the order has not been administered.
However, when checking incomplete orders for infusions, you should check within the same route. Because, even if it is an unexecuted order for a patient, it should not be warned if it is infused by a different route. Here, a tube is usually connected to a pack in which a medicine is placed, and a needle for injecting the medicine into the patient's body is further connected to the tip of the tube. And when a drug is administered from each of a plurality of parts of a patient's body, a route refers to each tube for injecting the drug to each part or a tube connected to each of a plurality of packs physically outside the patient's body. In the case of administration to a patient from one tube after the combination, each tube before the connection, and the like. In particular, in the latter case, the doctor designates a main route and a sub route for each tube before joining.

  In the above prior art, when instilling into a patient's body from multiple routes at the same time, there is a problem that a useless warning is generated in addition to a warning that is really necessary, and the nurse who receives the warning is confused. It was.

  SUMMARY OF THE INVENTION An object of the present invention is to make it possible to check an unimplemented order of drug administration for a patient within the same route.

  In one example, a computer receives a patient ID for identifying a patient and an order ID for identifying a medication order, and a patient ID is designated for each of a plurality of order IDs including the order ID issued for the patient ID. The storage unit stores a plurality of pieces of order information in which the administration date and time information, the administration route for specifying the administration form of the administration, and the administration status of the administration correspond to each other, the received patient ID and the received order ID corresponding to the received order ID. Obtained execution order information, tied to the received patient ID, the medication date information is younger than the medication date information included in the unimplemented order information, and the medication route and medication route included in the unimplemented order information are the same The presence / absence of unexecuted order information is determined, and the presence of an unexecuted order is notified within the same medication route based on the determination result.

  It is possible to check an unperformed order of drug administration for a patient within the same administration route. For this reason, it becomes possible to avoid that a nurse is confused by many warnings.

1 is an overall system configuration diagram of an embodiment. It is explanatory drawing of the nursing assistance service implemented using the system of embodiment. It is a functional block diagram of the system of an embodiment. It is a figure which shows the data structural example of an order information table. It is a figure which shows the data structural example of an order content table. It is a figure which shows the data structural example of a patient information table. It is a figure which shows the example of a data structure of a user information table. It is a flowchart (the 1) which shows a medication order check process. It is a flowchart (the 2) which shows a medication order check process. It is a flowchart (the 3) which shows a medication order check process. It is a flowchart (the 4) which shows a medication order check process. It is a flowchart (the 5) which shows a medication order check process. It is a figure which shows the example of a screen transition (the 1). It is a figure which shows the example of a screen transition (the 2). It is a figure which shows the example of a screen transition (the 3). It is explanatory drawing of the effect of embodiment. It is a block diagram of the hardware which can implement | achieve the PDA server 102 of embodiment.

Hereinafter, embodiments for carrying out the present invention will be described in detail with reference to the drawings.
FIG. 1 is an overall system configuration diagram of the embodiment.
A PDA (Personal Digital Assistants) 101 functions as a portable terminal device that is shared and used by a plurality of nurses. The nurse uses the PDA 101 in the hospital room. The PDA 101 accesses the PDA server 102 by WEB cooperation of HTTP (Hyper Text Transfer Protocol) using a wireless LAN (Local Area Network) 104 in the hospital. As a result, the nurse uses various functions provided by the PDA server 102. The PDA server 102 is connected to the electronic medical record server 103 by a wired LAN (local area network) 105, for example, and accesses tables of various databases in the electronic medical record server 103 as necessary. The registered contents of the various tables on the electronic medical record server 103 are updated by the doctor using the electronic medical record terminal 106 connected via the LAN 105.

  The system of the embodiment of FIG. 1 is performed after a medical worker (doctor / nurse) authenticates the patient and the instruction content at the bedside with the PDA 101 which is a portable terminal when performing injection or infusion. It is a system that can. In addition, regarding the recording of vital values and observation items, it is possible to perform real-time updates to the electronic medical record server 103 by inputting from the PDA 101, not by posting after returning to the staff station. To improve efficiency.

FIG. 2 is an explanatory diagram of nursing support work carried out using the system of the embodiment of FIG.
In FIG. 2, in the ward or nurse station 201, a doctor issues an injection (infusion) order from the electronic medical record terminal 106. This injection order is registered in the order information table and the order content table of the electronic medical record server 103. If the injection order is, for example, a regular order (S1 in FIG. 2) before the deadline for receiving the injection order, the drug department system (not shown) issues a barcode label in the drug department 202. The person in charge of the medicine department pays out the ward together with the medicine. On the other hand, if the injection order is, for example, a temporary order after the deadline (S2 in FIG. 2), the doctor issues a temporary injection instruction with a barcode printed on the printer at hand and uses the placement medicine. May be prepared.

  In the hospital room 203, the nurse logs in by entering his / her user ID and password when starting to use the shared PDA 101 (FIG. 1). Furthermore, the nurse performs the following three-point authentication “who”, “who”, and “what to do” with the PDA 101 in order to prevent administration errors during injection and infusion. First, the nurse reads the user ID stored in the barcode of the nurse's own ID card or the like by operating the PDA. The user ID is identification information of the nurse, and a double check of the user ID is performed when logging in and when performing injection and the like. Next, the nurse reads the patient ID from the patient bar code of the wristband worn by the patient. The patient ID is information for identifying each individual patient. The PDA 101 receives patient ID and displays patient information and nurses. By confirming the patient information and the nurse, the nurse prevents the patient from being mixed up. Further, the nurse reads the order ID from the infusion label of the medicine or the barcode of the temporary injection instruction. The order ID is an order of injection or infusion prescribed by a doctor and is identification information attached to one enforcement unit. The nurse can confirm the specific contents of the injection and infusion to be performed in the PDA 101 by inputting the order ID. In addition to the injection and infusion to be performed from now on, the nurse can also check the PDA 101 for any untreated treatment. The PDA server 102 (FIG. 1) is a display frame for order contents on the display screen of the PDA 101 based on the user ID, patient ID, and order ID determined based on each barcode read by the PDA 101. Check the instruction frame. First, the PDA server 102 acquires patient information corresponding to the patient ID from the electronic medical record server 103 (FIG. 1) and transmits it to the PDA 101. Further, the PDA server 102 acquires order information from the electronic medical record server 103 by using an order ID (order number) such as a drip medicine ID read by the PDA 101. Then, the PDA server 102 checks the medication error by combining the patient ID and the order ID read by the PDA 101 with the order information received from the electronic medical record server 103.

  Here, in the case of drug administration, it may be necessary to administer drugs in the order instructed by the doctor even if the time is somewhat different (for example, changing the connecting pack from A to B with the drip needle held down) To do). In addition, in the case of infusion, two types of A1 (main route) and A2 (subroute) may be mixed and administered by connecting tubes before entering the patient's body. When a doctor instructs administration in the order of A1 → B in the main route, it is necessary to check whether A1 is administered before B. In this case, the nurse does not need to check whether A2 is administered before B.

  In the case of an anticancer drug, there are restrictions on the order of administration and the time of administration, so instructions such as order can be set and registered on the electronic medical record server 103. However, there are many cases in which the order of drug administration must be observed in addition to anticancer agents, and the conventional system has not been able to manage the order of drug administration. For example, when there is a drug set that needs to be administered every 3 hours, the drug administration may be missed once, such as when the test is delayed for 3 hours due to a delay in the examination, etc., which may lead to a medication accident. It was.

  FIG. 3 is a functional block diagram of the system of the present embodiment based on the system configuration of FIG. 1, which can check the order of medication in drug administration that requires an order check for each route as described above.

  In the present embodiment, when the PDA 101 receives an order ID such as a patient ID and a drip medicine ID, order information associated with the patient ID (information including an unexecuted order ID, medication date information, and a medication route) is acquired. . The order of execution is younger than the order ID, and it is possible to notify the presence of unexecuted orders in the same medication route by determining the presence / absence of order information for the same medication route, which is useless other than the really necessary warning. No warnings can occur and nurses can be prevented from being confused.

  3, PDA 101 functions as a personal information terminal device, PDA server 102 functions as a first server device, and electronic medical record server 103 functions as a second server device, which are the same as those shown in FIG. As shown in FIG. 1, the PDA 101 and the PDA server 102 are connected by, for example, a wireless LAN 104, and the PDA server 102 and the electronic medical record server 103 are connected by, for example, a wired LAN 105.

  In FIG. 3, the PDA 101 has a patient ID receiving unit 301. The patient ID receiving unit 301 receives a patient ID for identifying a patient. The patient ID receiving unit 301 is, for example, a barcode reader that reads a barcode printed on a wristband worn by a patient and receives a patient ID included in the barcode.

  The PDA 101 also has an order ID receiving unit 302. The order ID receiving unit 302 receives an order ID for identifying a medication order. The order ID receiving unit 302 is, for example, a barcode reading device that reads a barcode printed on an infusion label for infusion or a label on a syringe and receives an order ID included in the barcode.

  The PDA 101 also has an order error warning unit 306. The order error warning unit 306 warns information about a medicine to be administered earlier than a medicine of the order indicated by the read order ID based on a notification from an order error notification part 305 in the PDA server 102 described later. Notice.

  The PDA 101 also has a patient information display unit 311. The patient information display unit 311 displays patient information received from a patient information acquisition unit 310 in the PDA server 102 described later. The patient information is, for example, the patient name corresponding to the patient ID received by the patient ID receiving unit 301 in the PDA 102.

  Further, the PDA 101 has a user ID receiving unit 312. The user ID receiving unit 312 acquires a user ID and password for identifying a nurse who cares for a patient. The user ID accepting unit 312 is, for example, a keyboard or touch panel that accepts a user ID and password at login, and a bar that accepts a user ID by reading a barcode printed on a nurse's ID card at the time of injection or infusion. It is a code reader.

  In FIG. 3, the PDA server 102 includes an order information acquisition unit 303. The order information acquisition unit 303 acquires the patient ID received by the PDA 101 and the incomplete order information corresponding to the order ID received by the PDA 101 from the electronic medical record server. More specifically, the order information acquisition unit 303 accesses the order information table storage unit 308 in the electronic medical record server 103 connected to the PDA server 102, for example, via the LAN 105, and acquires order information. The order information table storage unit 308 designates a patient ID, designated medication date and time information, and a dosage form for medication for each of a plurality of order IDs including individual order IDs issued to individual patient IDs. A plurality of order information in which a medication route to be associated with a medication implementation status is stored as an order information table.

  In addition, the PDA server 102 includes a medication route-based medication date determination unit 304 that performs the next determination using the order information acquired by the order information acquisition unit 303. The medication date and time determination unit 304 for each medication route is associated with the patient ID received by the PDA 101, and the medication date and time information is younger than the medication date and time information included in the unimplemented order information acquired by the order information acquisition unit. The presence / absence of other incomplete order information having the same medication route and medication route is determined. Thereby, the medication date and time determination unit 304 for each medication route checks the order of medication for each medication route.

  The PDA server 102 also includes an order error notification unit 305. The order error notification unit 305 notifies the PDA 101 of the presence of an unimplemented order based on the determination result in the dosing date and time determination unit 304 for each dosing route. As a result, the sequence error warning unit 306 in the PDA 101 receives the above notification from the PDA server 102 and notifies the presence of an unexecuted order in the same medication route.

  As described above, in the present embodiment, first, order information including the medication date and time information and the medication route corresponding to the patient ID accepted by the PDA 101 and the order ID accepted by the PDA 101 is acquired. And in matching with this order information and the other unimplemented order information memorize | stored in the order information table memory | storage part 308 of the electronic medical record server 103, in addition to an implementation order, the identity of a medication route is also checked. Consider a case where two types of infusions A1 (main route) and A2 (subroute) are mixed and administered as in the above example. In this case, based on the doctor's instruction, information that A1 and B are the same medication route (main route) is registered in the order information table storage unit 308 of the electronic medical record server 103. The medication date and time of A1 and the medication date and time of B are also registered in the order information table storage unit 308 by the doctor. On the other hand, information that A2 is a different medication route (sub route) is registered in the order information table storage unit 308 of the electronic medical record server 103 by the doctor. Further, the medication date and time of A2 is also registered by the doctor. That is, it is assumed that an order having a medication date and time before B's medication date and time exists for A1 and A2. However, according to this embodiment, the dosing date and time determination unit 304 for each dosing route checks whether A1 and B are administered in the correct order. On the other hand, since the order check of A2 and B is unnecessary, the operation is performed so that the check by the medication date and time determination unit 304 for each medication route is not performed.

  The above-described example is an example in the case where the administration route is route information for distinguishing a mixing route when a plurality of drugs are mixed and administered. In addition, the same can be considered when the medication route is route information for distinguishing a site on the human body to which the drug is administered, such as the left hand and the right hand or the back.

  In this embodiment, the actual order information stored in the order information table storage unit 308 in the electronic medical record server 103 stores information called a procedure code, not information on the medication route itself. This procedure code is information for distinguishing procedures such as injection and infusion as an application originally used in the electronic medical chart system. However, in this embodiment, in addition to the procedure, the procedure code is a medication route such as a mixed route when a plurality of drugs are mixed and administered and a route indicating a site on the human body to which the drug is administered as described above. It is coded to include route information. That is, in the present embodiment, the procedure code included in the order information is used as medication mode information indicating a medication mode including a medication route. In addition to the procedure code, it may be provided as a table item indicating a medication route. In this case, the procedure code and the medication route can be combined and taken as medication mode information.

  As described above, in the present embodiment, it is possible to check an unimplemented order of drug administration for a certain patient within the same dosing route. Conventionally, when instilling into a patient's body from multiple routes, there has been a problem that a nurse who has received a warning is confused by generating a useless warning in addition to a warning that is really necessary. It was. On the other hand, in the present embodiment, since order information to be warned can be limited to the same medication route, there is an effect that the nurse is not confused.

  The PDA server 102 also includes an order execution setting unit 307. The order execution completion setting unit 307 receives the order execution input from the PDA 101 and updates the execution status of the corresponding order information to information indicating that it has been executed among the order information stored in the order information table storage unit 308. . More specifically, the order execution completed setting unit 307 updates the execution presence / absence information of the record corresponding to the order information in the order information table storage unit 308 of the electronic medical record server 103 to information indicating that it has been executed.

  The PDA server 102 also includes a patient information acquisition unit 310. The patient information acquisition unit 308 accesses the patient information table storage unit 309 in the electronic medical record server 103 based on the patient ID received by the patient ID reception unit 301 in the PDA 101. The patient information table storage unit 309 stores patient information including a patient name corresponding to each patient ID as a patient information table. The patient information acquisition unit 310 accesses the patient information table storage unit 309 to acquire patient information corresponding to the received patient ID from the electronic medical record server 103 and transmits it to the PDA 101. As a result, the patient information display unit 309 in the PDA 101 displays the patient information received from the PDA server 102 on the display.

  Further, the PDA server 102 has a user authentication unit 314. The user authentication unit 314 accesses the user information table storage unit 313 in the electronic medical record server 103 based on the user ID and password received by the user ID reception unit 312 in the PDA 101. The user information table storage unit 313 stores user information including a user name and a password corresponding to each user ID as a user information table. The user authentication unit 314 obtains user information corresponding to the received user ID and password from the electronic medical record server 103 by accessing the user information table. Then, the user authentication unit 314 authenticates the nurse who operates the PDA 101 based on the acquired user information.

  FIG. 4 is a diagram showing a data configuration example of an order information table stored in the order information table storage unit 308 in the electronic medical record server 103 of FIG. In the order information table, a record having information items of order number (order ID), patient ID, medication date / time information, implementation flag (implementation presence / absence information), and procedure code (medication route) is registered in plural records for each order information. It is a table that was made. In each record, the order number (order ID) is used to identify the medication order specified by the barcode label attached to the medicine or the barcode printed on the temporary injection instruction in the medicine department of FIG. Information. The patient ID is information for identifying the patient specified by the barcode printed on the patient wristband in the hospital room 203 of FIG. The medication date / time information is date / time information input by a doctor, and is information indicating the date and time when the medicine should be administered. The execution flag (execution presence / absence information) is information indicating whether or not the medicine corresponding to the order information of the record including the execution flag has been executed or not. “1” is registered if it has been implemented, and “0” if it has not been implemented. As described above, the procedure code is not only information for specifying the procedure such as injection or infusion, but also the route indicating the administration site on the human body such as the left hand and right hand, and the main or sub (side tube) dosing tube. It is coded to include information on a medication route such as a mixing route that specifies That is, in the present embodiment, the procedure code included in the order information is used as medication mode information indicating a medication mode including a medication route.

  In the example of FIG. 4, “00011315” is registered as the order number (order ID) in the first record. “1111111111” is registered as the patient ID. As the medication date / time information, “20111011900000” is registered. This specifies that it should be administered at 8:00:00 on January 19, 2011. As the execution flag (execution presence / absence information), “1” (performed) is registered. “Abcde1111” is registered as the procedure code. This procedure code is coded according to a predetermined rule, and indicates medication mode information including a medication route such as “main drip of the right hand”. In the second record, “00032430” is registered as the order number (order ID). The same “1111111111” as the first is registered as the patient ID. “20111011190000” is registered as the medication date information. This specifies that it should be administered at 12:00:00 on January 19, 2011. As an execution flag (execution presence / absence information), “0” (not executed) is registered. The same “abcde1111” as the first is registered as the procedure code. In the third record, “00054545” is registered as the order number (order ID). The same “1111111111” as the first and second is registered as the patient ID. “20111101190000” is registered as the medication date information. This specifies that it should be administered at 18:00:00 on January 19, 2011. As an execution flag (execution presence / absence information), “0” (not executed) is registered. The same “abcde1111” as the first and second is registered as the procedure code.

  In the example of FIG. 4, for example, when an order number (order ID) “00054545” is checked in order of medication, the order information acquisition unit 303 of FIG. 3 acquires the order information of the third record. Next, the dosing date and time determination unit 304 for each dosing route in FIG. 3 is the same day before the third dosing date and time for the third patient ID and the dosing date and time indicated by the third dosing date and time information. Order information including the medication date and time information indicating the medication date and time and the same procedure code as the third procedure code is retrieved. As a result, in the example of FIG. 4, each order information of the first and second records is retrieved. Further, the order error notification unit 305 in FIG. 3 notifies the PDA 101 of the presence of the second order as unexecuted order information out of the first and second order information.

  The doctor simply designates the medication time and places an order, and does not enter the order of administration. In other words, the electronic medical record server 103 does not accurately grasp the administration order, and considers the ascending order of the medication date and time information in which the medication times input by the doctor are recorded as the administration order.

  FIG. 5 is a diagram showing a data configuration example of an order content table stored in the electronic medical record server 103, which is not explicitly shown in FIG. The order content table is a table in which a plurality of records having information items of order number (order ID), patient ID, order content, quantity, and unit are registered for each order content information. In each record, the order number (order ID) and patient ID are the same as the order number (order ID) and patient ID on the order information table of FIG. With these combinations, one record on the order content table of FIG. 5 is linked to a record having the same order number (order ID) and patient ID set on the order information table of FIG. The order content is information indicating the detailed content of the drug actually administered. The quantity is information indicating the quantity of the medicine. The unit is information indicating a physical unit for counting the number of drugs.

  In the example of the first record in FIG. 5, “00054545” is registered as the order number (order ID), “1111111111” is registered as the patient ID, and “continuous infusion peripheral main” is registered as the order content. The quantity and unit are entered by the doctor when necessary. If not entered, the quantity and unit will be blank. In the example of the second record, “00054545” is registered as the order number (order ID), “1111111111” as the patient ID, “Solita T3” as the order content, “1” as the unit, and “cylinder” as the unit. Furthermore, in the example of the third record, “00054545” is registered as the order number (order ID), “1111111111” as the patient ID, and “1st floor East Ward” as the order contents.

  When the PDA server 102 in FIG. 3 is instructed to perform injection or infusion, the PDA server 102 determines the order of the third record in FIG. 4 based on the patient ID and the order ID received by the PDA 101. A record having the same set as the set of number (order ID) and patient ID is searched on the order content table of FIG. As a result, the order contents of the first, second, and third records in FIG. 5 are displayed on the display of the PDA 101 via the PDA server 102. Thereby, the nurse can display the details of the order contents corresponding to the injection or infusion to be performed on the PDA 101.

  FIG. 6 is a diagram illustrating a data configuration example of a patient information table stored in the patient information table storage unit 309 in the electronic medical record server 103. The patient information table is a table in which a plurality of records having information items of patient ID and patient name are registered for each patient information. In each record, the patient ID is information for identifying the patient specified by the barcode printed on the patient wristband in the hospital room 203 of FIG. The patient name is information indicating the name of the patient corresponding to the patient ID.

  In the example of FIG. 6, “1111111111” is registered as the patient ID and “Taro Fujitsu” is registered as the patient name in the first record. In the second record, “222222222” is registered as the patient ID and “Jiro Fujitsu” is registered as the patient name. In the third record, “33333333333” is registered as the patient ID, and “Fujitsu Ichiro” is registered as the patient name.

  The patient information acquisition unit 310 of the PDA server 102 in FIG. 3 accesses the patient information table storage unit 309 of the electronic medical record server 103 using the patient ID received by the PDA 101 at the patient ID reception unit 301. As a result, for example, if the patient ID is “1111111111”, the first record in FIG. 6 is searched and the patient name “Taro Fujitsu” is acquired. The patient name is notified from the patient information acquisition unit 310 in the PDA server 102 to the patient information display unit 311 in the PDA 101 and displayed on the display of the PDA 101. Thereby, the nurse can prevent a patient's mistake by checking whether the patient who is going to treat and the patient information displayed on the PDA 101 are the same.

  FIG. 7 is a diagram illustrating a data configuration example of a user information table stored in the user information table storage unit 313 in the electronic medical record server 103. The user information table is a table in which a plurality of records having information items of user ID, user name, and password are registered for each user information. In each record, the user ID, which is the nurse ID, is information for identifying the nurse designated by the barcode printed on the nurse's ID card in the hospital room 203 of FIG. The nurse name is information indicating the name of the nurse corresponding to the user ID. The password is information for identifying the password received by the user ID receiving unit 312 of the PDA 101 when the nurse starts using the PDA 101.

  In the example of FIG. 7, “aabbcc” is registered as the user ID, “Fujitsu Hanako” as the user name, and “pw111111” as the password in the first record. In the second record, “ddeeff” as the user ID, “Fujitsu Haruko” as the user name, and “pw222222” as the password are registered. In the third record, “gghhi” is registered as the user ID, “Akiko Fujitsu” as the user name, and “pw333333” as the password.

  The user authentication unit 314 of the PDA server 102 in FIG. 3 accesses the user information table storage unit 313 of the electronic medical record server 103 using the user ID and password received by the PDA 101 at the user ID reception unit 312. As a result, for example, if the user ID is “aabbcc”, the first record in FIG. 6 is searched, and the user name “Fujitsu Hanako” is acquired. Further, the user authentication unit 314 authenticates whether or not the accepted password is the same as the password “pw111111” registered in the first record. If the password is the same, the user authentication unit 314 permits the nurse who operates the PDA 101 to use the PDA 101. Although not explicitly shown in FIG. 3, the user authentication unit 314 displays the authenticated user name on the display of the PDA 101.

  8, FIG. 9, FIG. 10, FIG. 11, and FIG. 12 show the medication order check process for checking the medication order displayed in the instruction frame for realizing the function of the system of the embodiment of FIG. It is a flowchart. This flowchart is a process in which each CPU (central processing unit) executes a control program stored in each memory in each of the computers of the PDA 101, the PDA server 102, and the electronic medical record server 103 shown in FIGS. Realized.

  First, based on the operation of the nurse, the PDA 101 inputs a user ID and password (steps S801 and S802 in FIG. 8). These processes correspond to some functions of the user ID receiving unit 312 in FIG.

  Next, the PDA server 102 accesses the user information table storage unit 313 in the electronic medical record server 103 based on the user ID and password. As a result, the user information corresponding to the user ID is retrieved from the user information table having the data configuration example of FIG. Further, authentication is performed by determining whether or not the password (see FIG. 7) included in the user information matches the password input in step S802 (step S803 in FIG. 8). This processing corresponds to some functions of the user authentication unit 314 in FIG.

  If the authentication is successful, the user name is displayed on the PDA 101 as the user information retrieved by the PDA server 102 (step S804 in FIG. 8). Subsequently, the user ID is stored in an internal variable in the memory of the PDA server 102 (step S805 in FIG. 8). Thereafter, login is executed (step S806 in FIG. 8), and a menu screen is displayed on the display of the PDA 101 (step S807 in FIG. 8). The processes from step S804 to S807 described above correspond to some functions of the user authentication unit 314 and the user ID reception unit 312 in FIG.

  Next, based on the operation of the nurse, the PDA 101 selects an injection execution input function button on the menu screen (step S808 in FIG. 8). As a result, this information is notified to the PDA server 102, and the function of the order information acquisition unit 303 in FIG. 3 is activated.

  First, the PDA 101 reads the barcode of the user ID from the nurse's own ID card by the operation of the nurse (step S809 in FIG. 9). This processing corresponds to the function of the user ID receiving unit 312 in FIG.

  Next, the user ID read in step S809 is compared with the user ID stored in the internal variable in step S805 in FIG. 8 at the time of login (step S810 in FIG. 9), and it is determined whether or not they match. (Step S811 in FIG. 9). If the two user IDs do not match and the determination in step S811 is NO, an error is displayed on the PDA 101, and the process returns to the user ID input process in step S809.

  If both user IDs match and the determination in step S811 is YES, the user name (nurse name) as user information is displayed again on the PDA 101 (step S813 in FIG. 9).

  Each process from the above steps S809 to S811 corresponds to a part of the function of the order information acquisition unit 303 in FIG.

  Next, in the PDA 101, the barcode of the patient ID is read from the wristband of the patient by the operation of the nurse (step S814 in FIG. 9). This process corresponds to the function of the patient ID receiving unit 301 in FIG.

  Next, the PDA server 102 accesses the patient information table storage unit 309 in the electronic medical record server 103 based on the patient ID. As a result, patient information corresponding to the patient ID is retrieved from the patient information table having the data configuration example of FIG. 6 (step S815 in FIG. 9). This process corresponds to the function of the patient information acquisition unit 310 in FIG.

  Next, the patient name which is the retrieved patient information is displayed on the display of the PDA 101 (step S816 in FIG. 9). This process corresponds to the function of the patient information display unit 311 in FIG.

  Next, in the PDA 101, the barcode of the order number (order ID) is read from the infusion label attached to the medicine or the temporary injection instruction (see FIG. 2) by the operation of the nurse (step S817 in FIG. 10). ). This processing corresponds to the function of the order ID receiving unit 302 in FIG.

  Next, the PDA server 102 accesses the order information table storage unit 308 in the electronic medical record server 103 of FIG. 3 based on the order number (order ID) read in step S817. As a result, a record of order information having the order number (order ID) is retrieved from the order information table having the data configuration example of FIG. 4 (step S818 in FIG. 10).

  Further, a record having the same patient ID as the patient ID read in step S814 in FIG. 9 is further searched from the records searched in step S818. Here, when the record can be searched, the order content information corresponding to the combination of the order number (order ID) and the patient ID is acquired from the order content table in the electronic medical record server 103 (see FIG. 5). (Thus, step S819 of FIG. 10).

  Next, it is determined in step S819 whether or not a record having the same patient ID as the patient ID read in step S814 in FIG. 9 has been searched (step S820 in FIG. 10). If this determination is NO, the process proceeds to an error or warning display process in step S823 of FIG.

  If the determination in step S820 is YES, it is determined whether or not the execution flag (execution presence / absence information) (see FIG. 4) of the record searched in step S819 is a value “0” indicating non-execution (FIG. 4). 10 step S821). If the determination has already been made and this determination is NO, the process proceeds to the error or warning display process in step S823 of FIG.

  If the determination in step S821 is YES, it is determined whether or not the medication date / time information (see FIG. 4) of the record searched in step S819 is within a certain range compared to the current time (FIG. 10). Step S822). If it is more than a certain range away from the current time and the determination in step S822 is NO, the process proceeds to the error or warning display process in step S823 of FIG.

If the determination in step S822 is yes, the process proceeds to step S824 in FIG.
In step S823, which is executed when any of the determinations in steps S820, S821, and S822 is NO, an error or warning display indicating that the order to be executed is incorrect is displayed on the display of the PDA 101. Thereafter, the process returns to the process of step S817, and barcodes of other order numbers are read.

  The processing from step S818 to S822 in FIG. 10 corresponds to a part of the function of the order information acquisition unit 303 in FIG.

  When the determination in step S822 in FIG. 10 is YES, the order information table in the order information table storage unit 308 in the electronic medical record server 103 is accessed. The same patient ID as the order information acquired in step S819, the medication date / time information indicating the earlier medication time on the same day as the medication date / time indicated by the medication date / time information, and the order information including the same procedure code are also included. Search is performed (step S824 in FIG. 11). This processing corresponds to the function of the administration date determination unit 304 for each administration route in FIG. As described above, the procedure code includes, in addition to information on procedures originally used, a mixing route when a plurality of drugs are mixed and administered, a route indicating a site on the human body to which the drug is administered, and the like. It is coded as dosage mode information indicating the dosage mode including information on the dosage route.

  Next, by determining the execution flag (see FIG. 4) of each order information searched in step S824, it is determined whether or not all the order information has been executed (step in FIG. 11). S825).

  If all the order information has not been executed and the determination in step S825 is NO, it is determined whether warning information or error display should be displayed for the unexecuted order information (step S826 in FIG. 11). This criterion is set in advance.

  If an error is to be displayed, an error is displayed on the PDA 101 (step S829 in FIG. 11), and then the process returns to the process in step S817 in FIG. 10 to read barcodes of other order numbers.

  When warning display is to be made, the PDA 101 is notified of the presence of an unexecuted order. As a result, the PDA 101 receives the notification from the PDA server 102, and displays a warning on the display that there is an order not yet executed in the same medication route having the same procedure code.

  The processes in steps S825 to S827 in FIG. 11 correspond to the functions of the order error notification unit 305 and the order error warning unit 306 in FIG.

  After the determination in step S825 becomes YES or after the processing in step S827, the order information and the order content read in step S819 in FIG. 10 are displayed on the PDA 101 (step S828 in FIG. 11).

Thereafter, in the PDA 101, the execution of the order is input by the operation of the nurse (step S830 in FIG. 12).
Further, the PDA server 102 updates the execution presence / absence information of the record corresponding to the order information acquired in step S819 in the order information table storage unit 308 of the electronic medical record server 103 to information indicating that the execution has been performed (FIG. 12 step S831). This processing corresponds to the function of the order execution setting unit 307 in FIG.

FIGS. 13, 14, and 15 are diagrams showing screen transition examples of the display of the PDA 101 corresponding to the medication order check process shown in the flowcharts of FIGS.
The login screen S1 of FIG. 13 is an example of the screen when executing steps S801 and S802 of FIG. 8, and the nurse can input the user ID and password using the software keyboard on the screen of the PDA 101. .

  The menu screen S2 in FIG. 13 is an example of the screen at the time of execution of step S807 in FIG. 8, and the nurse executes the process in step S808 in FIG. 8 by selecting the “injection input” button on the screen. Is done.

The user authentication screen S3 in FIG. 13 is an example of a screen when step S809 in FIG. 9 is executed, and the nurse reads the barcode on the nurse's own ID card according to this screen instruction.
The patient authentication screen S4 in FIG. 13 is a screen example when step S814 in FIG. 9 is executed, and the nurse reads the barcode of the patient wristband according to the screen instruction.

  The order authentication screen S5 of FIG. 14 is a screen example when step S817 of FIG. 10 is executed, and the nurse reads the order number bar code of the infusion label or the temporary injection instruction according to this screen instruction.

  Here, for example, in the same administration route (medication route) having the same procedure code, when the order at time 12:00 (second order in FIG. 4) is not executed, the order at time 18:00 (FIG. If the third order (4) is authenticated first, an order error is warned. The warning notification screen S6 in FIG. 14 is a screen example when executing step S827 in FIG. 11 in such a case. For example, notification is made by blinking a lamp, sound, and vibration of the PDA 101 main body so that the nurse can recognize it immediately.

  The slip detail screen S7 of FIG. 14 is a screen displayed when the nurse selects OK on the warning notification screen S6. On this screen, detailed information regarding the order of injection or infusion to be performed at present is displayed based on the registered content of the order content table of FIG. 5 when step S828 of FIG. 11 is executed. Along with this detailed display, the warning notification screen S6 is taken over, and a warning message such as “There is an unexecuted order within the same administration route” is also displayed on the screen.

  The slip detail screen S8 in FIG. 15 is a screen showing a state when the nurse selects the “execution input” button in the slip detail screen S7. As a result, the process of step S830 in FIG. 12 is executed, and as a result, the execution screen S9 including the notification sentence “execution registered” in FIG. 15, for example, is displayed, indicating that the execution of the order has been completed. .

  The implementation status of injection and infusion by the operation of the PDA 101 by the nurse can also be confirmed from the electronic medical chart terminal 106 (FIG. 1) managed by the doctor or administrator. The electronic medical record terminal 106 accesses the order information table storage unit 308 (FIG. 3) or the like on the electronic medical record server 103 (FIG. 1), and performs injection or infusion, for example, using the roll browser screen S10 of FIG. You can view the records.

  In the above embodiment, when each medicine is instilled from the tube of the main route and the sub route, even if both the main route and the sub route start at the same time, they do not necessarily end at the same time. When A is finished first from medicine A (main) + medicine B (sub), it can be changed to medicine C to be infused at the main next to A, and then instilled at C (main) + B (sub). It can be. For example, A and C are drugs, and B is a physiological saline solution. In the case of C + B, in addition to the processing according to the present embodiment, it may be checked whether or not C and B are drugs that should not be infused simultaneously. A known technique can be used for checking the contraindications of the drug to be administered.

  In the present embodiment, the procedure code stored in the order information table in FIG. 4 includes, as described above, a medication mode including medication route information in addition to information for specifying a procedure such as injection or infusion. It is coded as medication mode information for identification. This dosing route includes route information for specifying a dosing site on the human body such as the left hand and the right hand, and mixed route information for specifying a main or sub (side tube) dosing tube.

  The procedure code in the above-described embodiment can be set in three layers such as “procedure” + “administration site route such as left hand and right hand” + “main and side tube mixed route”, and the range of unexecuted orders to be warned Can be further narrowed down. On the other hand, with the information up to the second layer of “procedure” + “medicine site route such as left hand and right hand”, the check is expanded and the same “procedure” and “medicine site route” are checked. Embodiments are possible. Even in this case, the number of unexecuted warnings can be set to an appropriate number as compared with the case of searching only in the execution order. For example, in the case of injection order procedure information such as “infusion”, “deletion”, and “main”, an injection order having information of only “infusion” and “deletion” is searched, and a medication time earlier than the read injection order is searched. By checking an unperformed injection order, it is possible to check for non-medication injection regardless of the main or side tube. That is, by changing the level of the procedure code as the medication mode information stored in the order information table having the data configuration example of FIG. 4, various medication order check processes can be performed.

FIG. 16 is an explanatory diagram of the effect of this embodiment by changing the level of the procedure code as the medication mode information in this way.
Now, for example, both drug A1 and drug A2 are instilled into the left hand, the A1 infusion pack is set in the main, and the A2 infusion pack is set in the sub (side tube) at the same time. Assume that after the tube is connected, a drug is administered by inserting a drip needle into the patient's left hand. Thereafter, it may be necessary to administer the medicines in the order instructed by the doctor even if the time is slightly changed, such as changing the infusion pack connected to the main from A1 to B with the infusion needle held down.

  When a doctor instructs administration in the order of A1 → B in the main route, it is necessary to check whether A1 is administered before B. In this case, it is not necessary to check whether A2 is administered before B.

  According to the present embodiment, as shown in FIG. 16, the procedure code of each order information of the medicines A1, A2, and B includes the procedure (injection, infusion, etc.), the administration site route (the administration route such as the left hand, the right hand). , And the mixing route (main, sub-medication route, etc.) are coded so that they can be identified. Thereby, it is possible to check whether or not the medicine A1 administered prior to the medicine B is not performed only in the medication route that is the same as the medication route of the medicine B "main infusion of left hand". .

  Conventionally, when checking the execution order of drug administration, only the level of identification by a technique was possible. For this reason, if there is an unimplemented medicine that is administered prior to the medicine B, a warning is issued as a corresponding unimplemented medicine administration. That is, in FIG. 16, the nurse who is the user is notified that the orders belonging to all nodes of the branch tree other than the procedure code are not executed. For this reason, in the past, many warnings occurred in addition to the warnings that were really necessary, and the nurses who received the warnings could be confused. In addition, nurses may not pay sufficient attention to such a large number of warning notices.

  According to the present embodiment, it is possible to avoid such confusion of the nurse, and the nurse can pay sufficient attention to the warning that is really necessary.

  FIG. 17 is a diagram illustrating an example of a hardware configuration of a computer that can realize the function of the PDA server 102 of the system illustrated in FIG. 3 as software processing.

  The computer shown in FIG. 17 includes a CPU 1701, a memory 1702, an input device 1703, an output device 1704, an external storage device 1705, a portable recording medium driving device 1706 into which a portable recording medium 1709 is inserted, and a communication interface 1707. These are connected to each other by a bus 1708. The configuration shown in the figure is an example of a computer that can implement the PDA server 102, and such a computer is not limited to this configuration.

  The CPU 1701 controls the entire computer. The memory 1702 is a memory such as a RAM that temporarily stores a program or data stored in the external storage device 1705 (or the portable recording medium 1709) when executing a program, updating data, or the like. The CUP 1701 performs overall control by reading the program into the memory 1702 and executing it.

  The input device 1703 detects an input operation by a user using a keyboard, a mouse, or the like, and notifies the CPU 1701 of the detection result. The output device 1704 outputs data sent under the control of the CPU 1701 to a display device or a printing device.

The external storage device 1705 is, for example, a hard disk storage device. Mainly used for storing various data and programs.
The portable recording medium driving device 1706 accommodates a portable recording medium 1709 such as an optical disc, SDRAM, or CompactFlash (registered trademark), and has an auxiliary role for the external storage device 1705.

The communication interface 1707 is a device for connecting the wireless LAN 104 or the LAN 105 of FIG.
The system according to the present embodiment is realized by the CPU 1701 executing a program that has the functions realized by the configuration of FIG. 3 or the functions executed by the PDA server 102 in the flowcharts of FIGS. 8 to 12. . The program may be distributed by being recorded in, for example, the external storage device 1705 or the portable recording medium 1709, or may be acquired from the network by the network connection device 1707.

Regarding the above embodiment, the following additional notes are disclosed.
(Appendix 1)
Computer
Accepting a patient ID for identifying a patient and an order ID for identifying a medication order;
For each of a plurality of order IDs including the order ID issued for the patient ID, the patient ID, designated medication date and time information, a medication route for designating a medication dosage form, and a medication implementation status, From the storage unit that stores a plurality of order information that corresponds to the received patient ID and the incomplete order information corresponding to the received order ID,
Other incomplete order information associated with the received patient ID, the medication date information is younger than the medication date information included in the incomplete order information, and the medication route and medication route included in the incomplete order information are the same The presence or absence of
Based on the result of the determination, notify the presence of an unexecuted order within the same medication route.
A nursing support method characterized by that.
(Appendix 2)
The administration route is route information for distinguishing a site on a human body to which a drug is administered.
The nursing support method according to Supplementary Note 1, wherein
(Appendix 3)
The dosing route is route information for distinguishing a mixing route when a plurality of drugs are mixed and administered.
The nursing support method according to Supplementary Note 1, wherein
(Appendix 4)
The storage unit is an order information table storage unit included in another device, and acquires the unexecuted order information by accessing the order information table storage unit (304).
The nursing support method according to any one of appendices 1 to 3, characterized in that:
(Appendix 5)
In response to the order execution input, the execution status of the corresponding order information is updated to information indicating that it has been executed among the order information stored in the storage unit.
The nursing support method according to any one of appendices 1 to 4, characterized in that:
(Appendix 6)
The patient information corresponding to the received patient ID is searched and displayed by accessing a patient information table storage unit that stores patient information including the patient name corresponding to each patient ID.
The nursing support method according to any one of appendices 1 to 5, characterized in that:
(Appendix 7)
Further accepts a user ID and password that identifies the nurse who cares for the patient;
By accessing a user information table storage unit that stores user information including a user name and a password corresponding to each nurse code, user information corresponding to the received user ID and password is obtained. Acquiring and authenticating a nurse corresponding to the received user ID based on the acquired user information;
The nursing support method according to any one of appendices 1 to 6, characterized in that:
(Appendix 8)
A patient ID receiving unit for receiving a patient ID for identifying the patient;
A terminal device having an order ID receiving unit for receiving an order ID for identifying a medication order;
For each of a plurality of order IDs including the order ID issued for the patient ID, the patient ID, designated medication date and time information, a medication route for designating a medication dosage form, and a medication implementation status, An order information acquisition unit that acquires the received patient ID and incomplete order information corresponding to the received order ID from a storage unit that stores a plurality of order information associated with
Other terminal devices associated with the patient ID received by the terminal device, the medication date information is younger than the medication date information included in the unimplemented order information, and the medication route included in the unimplemented order information is the same as the medication route. A dosing date and time determination unit for each dosing route that determines the presence or absence of execution order information;
An order error notification unit for notifying the terminal device of the presence of an unimplemented order in the same medication route based on the determination result;
A server device connected to the terminal device via a network;
A nursing support system characterized by comprising
(Appendix 9)
The administration route is route information for distinguishing a site on a human body to which a drug is administered.
The nursing support system according to appendix 8, characterized in that.
(Appendix 10)
The dosing route is route information for distinguishing a mixing route when a plurality of drugs are mixed and administered.
The nursing support system according to appendix 8, characterized in that.
(Appendix 11)
The server device is connected to the first server device having the order information acquisition unit, the medication date and time determination unit for each medication route, and the order error notification unit via the network, A second server device having an order information table storage unit as a storage unit;
The order information acquisition unit in the first server device receives the patient ID and the order ID received by the terminal device, and accesses the order information table storage unit in the second server device. , Obtain the incomplete order information,
The terminal device further includes a sequence error warning unit that receives a notification from the sequence error notification unit in the first server device and issues a warning notification of information on a drug to be administered before a drug to be administered from now on. Have
The nursing support system according to any one of appendices 8 to 10, characterized in that.
(Appendix 12)
An order execution completion setting unit that receives an order execution input from the terminal device and updates the execution status of the corresponding order information to information indicating that it has been executed among the order information stored in the storage unit,
The nursing support system according to any one of appendices 8 to 11, wherein
(Appendix 13)
The second server device further includes a patient information table storage unit that stores patient information including a patient name corresponding to each patient ID,
The first server device corresponds to the patient ID received by the terminal device by accessing the patient information table storage unit in the second server device based on the patient ID received by the terminal device. Patient information is acquired from the second server device, and further includes a patient information acquisition unit for transmitting to the terminal device,
The terminal device further includes a patient information display unit that displays patient information received from the first server device.
The nursing support system according to any one of appendices 8 to 12, characterized in that:
(Appendix 14)
The second server device further includes a user information table storage unit that stores user information including a user name and a password corresponding to each user ID,
The terminal device further includes a user ID receiving unit for receiving a user ID and password for identifying a nurse who cares for a patient,
Based on the user ID and password received by the terminal device, the first server device accesses the user information table storage unit in the second server device, thereby accepting the use received by the terminal device. A user authentication unit that acquires user information corresponding to a person ID and password from the second server device, and performs authentication of a nurse who operates the terminal device based on the acquired user information;
The nursing support system according to any one of appendices 8 to 13, characterized in that:
(Appendix 15)
For each of a plurality of order IDs including an order ID received by the terminal device issued to a patient ID received by a terminal device connected by a network, the patient ID, designated medication date and time information, and medication The received patient ID and the incomplete order information corresponding to the received order ID are stored from a storage unit that stores a plurality of order information in which a medication route designating a dosage form and an implementation status of the medication correspond to each other. An order information acquisition unit to acquire;
Other terminal devices associated with the patient ID received by the terminal device, the medication date information is younger than the medication date information included in the unimplemented order information, and the medication route included in the unimplemented order information is the same A dosing date and time determination unit for each dosing route that determines the presence or absence of execution order information;
An order error notification unit for notifying the terminal device of the presence of an unimplemented order in the same medication route based on the determination result;
A nursing support server device characterized by that.
(Appendix 16)
The administration route is route information for distinguishing a site on a human body to which a drug is administered.
The nursing support server device according to supplementary note 15, characterized by:
(Appendix 17)
The dosing route is route information for distinguishing a mixing route when a plurality of drugs are mixed and administered.
The nursing support server device according to supplementary note 15, characterized by:
(Appendix 18)
The order information acquisition unit receives a patient ID and an order ID received by the terminal device, and accesses an order information table storage unit that is the storage unit of a second server device connected via a network. To obtain the incomplete order information.
The nursing support server device according to any one of appendices 15 to 17, characterized in that:
(Appendix 19)
To a computer that provides nursing support,
For each of a plurality of order IDs including an order ID received by the terminal device issued to a patient ID received by a terminal device connected by a network, the patient ID, designated medication date and time information, and medication From the storage unit that stores a plurality of order information in which a medication route for designating a dosage form and a medication implementation status correspond to each other, the received patient ID and the incomplete order information corresponding to the accepted order ID Get
Other terminal devices associated with the patient ID received by the terminal device, the medication date information is younger than the medication date information included in the unimplemented order information, and the medication route included in the unimplemented order information is the same as the medication route. Determine whether there is execution order information,
Based on the result of the determination, the terminal device is notified of the presence of an unexecuted order within the same medication route.
Program for executing processing.
(Appendix 20)
The administration route is route information for distinguishing a site on a human body to which a drug is administered.
The program according to appendix 19, characterized by:
(Appendix 21)
The dosing route is route information for distinguishing a mixing route when a plurality of drugs are mixed and administered.
The program according to appendix 19, characterized by:
(Appendix 22)
By receiving the patient ID and the order ID received by each of the terminal devices and accessing the order information table storage unit which is the storage unit of the second server device connected via the network, the unexecuted order Get information,
The program according to any one of supplementary notes 19 to 21, characterized in that:

101 PDA
102 PDA server 103 Electronic medical record server 103
104 wireless LAN
105 LAN
106 Electronic Medical Record Terminal 201 Ward / Nurse Station 202 Drug Department 203 Hospital Room 301 Patient ID Accepting Unit 302 Order ID Accepting Unit 303 Order Information Obtaining Unit 304 Medication Date / Time Determination Unit 305 Order Error Notifying Unit 306 Order Error Notifying Unit 307 Order Implementation Completed setting unit 308 Order information table storage unit 309 Patient information table storage unit 310 Patient information acquisition unit 311 Patient information display unit 312 Patient ID reception unit 313 User information table storage unit 314 User authentication unit

Claims (10)

Computer
Accepting a patient ID for identifying a patient and an order ID for identifying a medication order;
For each of a plurality of order IDs including the order ID issued for the patient ID, the patient ID, designated medication date and time information, a medication route for designating a medication dosage form, and a medication implementation status, From the storage unit that stores a plurality of order information that corresponds to the received patient ID and the incomplete order information corresponding to the received order ID,
Other incomplete order information associated with the received patient ID, the medication date information is younger than the medication date information included in the incomplete order information, and the medication route and medication route included in the incomplete order information are the same The presence or absence of
Based on the result of the determination, notify the presence of an unexecuted order within the same medication route.
A nursing support method characterized by that. The administration route is route information for distinguishing a site on a human body to which a drug is administered.
The nursing support method according to claim 1, wherein: The dosing route is route information for distinguishing a mixing route when a plurality of drugs are mixed and administered.
The nursing support method according to claim 1, wherein: The storage unit is an order information table storage unit (308) included in another device, and acquires the unexecuted order information by accessing the order information table storage unit.
The nursing support method according to any one of claims 1 to 3. A patient ID receiving unit for receiving a patient ID for identifying the patient;
A terminal device having an order ID receiving unit for receiving an order ID for identifying a medication order;
For each of a plurality of order IDs including the order ID issued for the patient ID, the patient ID, designated medication date and time information, a medication route for designating a medication dosage form, and a medication implementation status, Order information acquisition that acquires the patient ID received by the terminal device and the incomplete order information corresponding to the order ID received by the terminal device from the storage unit (308) that stores a plurality of order information corresponding to And
Other terminal devices associated with the patient ID received by the terminal device, the medication date information is younger than the medication date information included in the unimplemented order information, and the medication route included in the unimplemented order information is the same as the medication route. A dosing date and time determination unit for each dosing route that determines the presence or absence of execution order information;
An order error notification unit for notifying the terminal device of the presence of an unimplemented order in the same medication route based on the determination result;
A server device connected to the terminal device via a network;
A nursing support system characterized by comprising The administration route is route information for distinguishing a site on a human body to which a drug is administered.
The nursing support system according to claim 5. The dosing route is route information for distinguishing a mixing route when a plurality of drugs are mixed and administered.
The nursing support system according to claim 5. The server device is connected to the first server device having the order information acquisition unit, the medication date and time determination unit for each medication route, and the order error notification unit via the network, A second server device having an order information table storage unit as a storage unit;
The order information acquisition unit in the first server device receives the patient ID and the order ID received by the terminal device, and accesses the order information table storage unit in the second server device. , Obtain the incomplete order information,
The terminal device further includes a sequence error warning unit that receives a notification from the sequence error notification unit in the first server device and issues a warning notification of information on a drug to be administered before a drug to be administered from now on. Have
A nursing support system according to any one of claims 5 to 7. For each of a plurality of order IDs including an order ID received by the terminal device issued to a patient ID received by a terminal device connected by a network, the patient ID, designated medication date and time information, and medication Acquired unaccompanied order information corresponding to the received patient ID and the received order ID from a storage unit storing a plurality of order information in which a medication route for specifying a dosage form and an implementation status of the medication correspond to each other. An order information acquisition unit;
Other terminal devices associated with the patient ID received by the terminal device, the medication date information is younger than the medication date information included in the unimplemented order information, and the medication route included in the unimplemented order information is the same as the medication route. A dosing date and time determination unit for each dosing route that determines the presence or absence of execution order information;
An order error notification unit for notifying the terminal device of the presence of an unimplemented order in the same medication route based on the determination result;
A nursing support server device characterized by that. To a computer that provides nursing support,
For each of a plurality of order IDs including an order ID received by the terminal device issued to a patient ID received by a terminal device connected by a network, the patient ID, designated medication date and time information, and medication Acquire the received patient ID and incomplete order information corresponding to the received order ID from a storage unit that stores a plurality of order information in which a medication route for specifying the dosage form and the implementation status of the medication correspond to each other. And
Other terminal devices associated with the patient ID received by the terminal device, the medication date information is younger than the medication date information included in the unimplemented order information, and the medication route included in the unimplemented order information is the same as the medication route. Determine whether there is execution order information,
Based on the result of the determination, the terminal device is notified of the presence of an unexecuted order within the same medication route.
Program for executing processing.