JP2007229308A - Prescription order device and prescription order method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce a burden of a doctor inflicted by order input, and prevent discontinuation of drugs which should be continuously given. <P>SOLUTION: In a prescription order, the order should be continuously implemented and recorded in a control DB 120. An issuing means 110 refers to an order DB 130 controlling the status of implementation of the prescription order, the order recorded in the control DB 120 calculates the prescription finish date from the last status of implementation. When the finish date does not reach the next order date, a necessary continuous order is automatically formed and transmitted to a pharmaceutical terminal 400. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a prescription instruction apparatus and a prescription instruction method for receiving a prescription order from an instruction terminal for instructing a prescription order and instructing the prescription order to a preparation terminal for preparing an ordered prescription object based on the prescription order.

As a conventional technique, based on the total amount of infusion to be administered and the flow rate per unit time input by the nurse, a technique for predicting the end of infusion from the infusion administration start time and warning the nurse before the end is already available. Published (Patent Document 1).
JP-A-2005-237666

  The prior art only considers the convenience for nurses. However, it is a doctor who orders the prescription of such an infusion, and the problem of the doctor who instructs such a prescription order cannot be solved.

  That is, even for a prescription order that should be continuously administered for a certain period of time, such as an infusion or a tablet, if the prescription subject that is being administered has expired, it is necessary for the doctor to reinstruct the order.

  In addition, there is an input deadline for order input, and if this is missed, there is a risk that a drip or tablet to be prescribed will be interrupted.

  However, if that is the case, if the order is re-instructed mechanically in anticipation of the end time of the subject of prescription, for example, if some sudden abnormal situation occurs in the patient, the mechanical instruction is given. Orders placed may become unnecessary or dangerous that may exacerbate the abnormal situation.

  An object of the present invention is to identify a prescription order to be continuously executed while considering the above-described problems, and to automatically generate a prescription order.

  The present invention is a prescription instruction apparatus or prescription instruction method for instructing a prescription order to a preparation terminal connected to an instruction terminal for instructing a prescription order and a preparation terminal for preparing an ordered prescription object. Using a continuation table in which information on prescription orders to be executed is managed, a prescription table in which various performance information on prescription orders to be transmitted to the preparation terminal, and a schedule table in which order entry deadlines are managed, The prescription order received from the instruction terminal is registered in the continuation table, the prescription order to be continuously executed is searched from the prescription table, the result information is identified, and the prescription execution end date and time of the prescribed prescription target is calculated. If the next instruction date and time to instruct the preparation terminal next time is specified from the schedule table, and the execution end date and time does not reach the next instruction date and time And automatically generates the necessary prescription orders, and transmits to the preparation terminal.

  Furthermore, the present invention further manages a confirmation flag indicating whether or not the prescription order has been confirmed before the prescription order is transmitted to the preparatory terminal in the prescription table, and the prescription searched from the prescription table. When the confirmation flag corresponding to the identification information indicates that it has not been confirmed, the execution end date / time is not calculated.

  ADVANTAGE OF THE INVENTION According to this invention, while being able to reduce a doctor's order input burden significantly, it becomes possible to prevent that a doctor forgets an order input time limit and to interrupt the prescription subject which should be continued continuously.

  In addition, if the prescription order is not confirmed by the nurse before the prescription order is finally given to the pharmacist, it is determined that some abnormality has occurred in the patient, and the prescription order is automatically generated. Necessary or dangerous prescription orders can be avoided.

  The system configuration in the present invention is shown in FIG. The present invention includes an issuing device 100, a doctor terminal 200 in which a doctor instructs a prescription order, a nurse terminal 300 in which a nurse inputs confirmation and execution of a prescription order, and a pharmacist terminal 400 that displays a prescription order to the pharmacist, Consists of. Note that there may be a system configuration in which a plurality of doctor terminals 200, nurse terminals 300, and pharmacist terminals 400 are connected to the issuing device 100.

  The issuing device 100 and the doctor terminal 200, the nurse terminal 300, and the pharmacist terminal 400 are connected via a wired cable such as a LAN or a network such as wireless communication, and exchange data with each other.

  The issuing device 100 further manages the issuing means 110, a management DB (database) 120 for managing prescription orders to be continuously executed, and confirmation and prescription results for prescription orders to be transmitted to the pharmacist terminal 400. The order DB 130, the schedule DB 140 for managing the input deadline of the instructed prescription order, and the target DB 150 for defining prescription orders to be continuously executed.

  The issuing means 110 accepts prescription orders input from the doctor terminal 200 and the nurse terminal 300, or generates continuous prescription orders to be continuously executed by the issuing means 110, and outputs these prescription orders to the nurse terminal 300. To the pharmacist terminal 400. The prescription order confirmed from the nurse terminal 300 is transmitted to the pharmacist terminal 400.

  The management DB 120 manages prescription order information to be continuously executed. Specifically, as shown in the management table 600 of FIG. 6, an order ID for identifying a prescription order, a patient ID for identifying a patient to be prescribed, an instruction content to be prescribed, an amount to be administered, and Each data item includes an end date indicating the end point of continuous execution.

  In the order DB 130, confirmation and prescription results of prescription orders to be transmitted to the pharmacist terminal 400 are managed. Specifically, as shown in the order table 700 of FIG. 7, an order ID for identifying an order, a type indicating an order type, a registration date indicating date and time information registered in the order DB, and a patient identifying a patient to be prescribed ID, instruction content to be prescribed, amount to be administered, instruction reception indicating confirmation status from the nurse terminal 300, execution indicating date and time information on which the nurse has performed the prescription, and prescription target administration pace It consists of data items such as remarks.

  The type item includes “normal” indicating a normal order and “continue” indicating a prescription order to be executed continuously. Furthermore, there are cases where the nurse urgently instructs an order from the nurse terminal 300, such as when the patient's sudden condition worsens or the subject of prescription is insufficient, and the postdoctoral approval is given later to the doctor in charge. There is a type “Temporary” indicating an urgent order.

  The administration pace recorded in the remarks item indicates when the prescription subject currently prescribed, such as the flow rate per hour if the subject is an infusion, or the amount taken per day if the subject is a tablet. Information that can be used to determine whether or not to complete.

  In the schedule DB 140, the input deadline of the prescription order input from the doctor terminal 200 or the nurse terminal 300 is managed. Specifically, as shown in the schedule table 800 of FIG. 8, the instruction deadline date and time that will be the input deadline is recorded. In the example of FIG. 8, only the time is set, but in this case, this set time becomes the deadline for each day.

  The target DB 150 manages definition information that defines what prescription order should be continuously executed, that is, what kind of order is “continue”. Specifically, as shown in the definition table 900 of FIG. 9, it is composed of data items such as a target type indicating the type of the corresponding prescription target and a target name that is specifically designated for each target type.

  For example, in the case where the definition as shown in FIG. 9 is made, all infusion prescription orders are recognized as “continuation” orders. In the tablet prescription order, only the tablet “C” is recognized as the “continuation” order, and if the tablet has another name, it is determined as the “normal” order. However, in the case of the “temporary” type order urgently input from the nurse terminal 300, even the medicine corresponding to the definition table 900 does not become the “continuous” type order.

  The doctor terminal 200 includes a display input unit 210 for displaying a prescription order instruction screen transmitted from the issuing device 100, receiving a prescription order input by the doctor, and transmitting the prescription order to the issuing device 100.

  The nurse terminal 300 receives the prescription order before being transmitted to the pharmacist terminal 400 from the issuing device 100, displays it on the screen, receives the confirmation information (instruction received information) input by the nurse, and transmits it to the issuing device 100. . In addition, the nurse terminal 300 receives the prescription execution date and time and the prescription target pace input by the nurse and transmits them to the issuing device 100. In addition, the nurse terminal 300 receives an order corresponding to the “temporary” type input by the nurse and transmits it to the issuing device 100.

  The nurse terminal 300 includes a display input unit 310 for performing various information displays and information input acceptance as described above.

  The pharmacist terminal 400 displays the prescription order transmitted from the issuing device 100, receives various input information input by the pharmacist such as prescription order preparation completion information, and transmits it to the issuing device 100. In order to perform such information display and information input reception, the pharmacist terminal 400 includes a display input unit 410.

  The doctor terminal 200, the nurse terminal 300, and the pharmacist terminal 400 are assumed to be, for example, a WS (workstation), a PC (personal computer), a mobile phone, a PDA (Personal Data Assistant) terminal, and the like. If it can perform, it will not be limited to these products.

  Next, using FIG. 2 and FIG. 3, it is performed between the issuing means 110 of the issuing apparatus 100 and each display input means 210, 310, 410 of the doctor terminal 200, the nurse terminal 300, and the pharmacist terminal 400. The overall processing flow of the present invention will be described.

  The processing shown in FIG. 2 is particularly performed for “normal” type orders and “temporary” type orders.

  In S1_1, an order is input to the doctor terminal 200. Alternatively, the order of the “temporary” type is input to the nurse terminal 300 in S1_2. In either case, each of the terminals 200 and 300 transmits the input order to the issuing device 100.

  In S <b> 2, the issuing device 100 receives the order transmitted from the doctor terminal 200 or the nurse terminal 300.

  In S3, the issuing device 100 determines whether or not the received order is an order of “continuation” type. If applicable, after issuing a new order ID and registering the order in the management DB 120, the pharmacist The order to be transmitted to the terminal 400 is registered in the order DB 130. On the other hand, when it does not correspond to the “continuation” type order, it is registered only in the order DB 130.

  Details of the issuing process in S3 will be described later with reference to FIG.

  In S <b> 4, the issuing device 100 transmits an instruction reception request screen generated based on the order information to the nurse terminal 300 in order to make the nurse confirm the order registered in the order DB 130 before sending it to the pharmacist terminal 400. The prior confirmation of the nurse is called “reception of instructions” and is a work performed in conventional hospital operations.

  In S5, the nurse terminal 300 receives the instruction reception request screen from the issuing device 100, and displays the instruction reception request screen on the screen. In S6, when the nurse browses the contents of the order and presses a confirmation button on the screen corresponding to each order, the nurse terminal 300 indicates that the displayed order has been received. The received information is transmitted to the issuing device 100. This instruction received information includes an order ID.

  In S7, the issuing device 100 receives the instruction received information and updates the instruction receiving item of the corresponding order ID in the order DB 130 from “not yet” to “completed”.

  Note that even if an abnormality occurs, such as when the patient's condition suddenly changes, the nurse can send information about canceling the instruction from the nurse terminal 300 even for the record that has been subjected to the instruction reception processing.

  In S8, the issuing device 100 generates a fixed prescription instruction screen for requesting a medicine preparation instruction based on the order whose instruction receiving item is “completed” among the orders registered in the order DB 130, and the pharmacist terminal 400. For orders for which the order receiving item is left as “not yet”, it is judged that the result is that the nurse does not accept the order because the patient's condition is different from the time when the order was ordered. , It is not transmitted to the pharmacist terminal 400.

  In S9, the pharmacist terminal 400 receives the fixed prescription instruction screen from the issuing device 100 and displays the screen. By browsing this fixed prescription instruction screen, the nurse prepares various drugs corresponding to the instructed order.

  The issuing device 100 prepares a preparation completion button to be pressed for an order for which preparation has been completed on the fixed prescription instruction screen, and when the button is pressed, the pharmacist terminal 400 transmits the preparation completion information to the issuing device 100, and the issuing device 100 May record information indicating preparation completion in association with the corresponding order ID in the order DB 130.

  Although not shown, a printing apparatus is connected to the pharmacist terminal 400, and the pharmacist terminal 400 corresponds to the order ID, patient ID (or patient ID) based on the order information displayed on the final prescription instruction screen. The patient name), the subject of the prescription, and the amount of the prescription subject are printed on the prescription bag containing the prescription subject or the prescription receipt attached to the prescription bag.

  In S <b> 10, when the nurse terminal 300 actually administers the prescription target to the patient, the nurse terminal 300 transmits information indicating the implementation status to the issuing device 100. Specifically, the nurse confirms the prescription receipt and inputs the order ID, the implementation date and time, and the administration pace to the nurse terminal 300. The nurse terminal 300 transmits the input information to the issuing device 100 as implementation information.

  In S <b> 11, when the issuing device 100 receives the execution information from the nurse terminal 300, the issuing apparatus 100 records the execution information in association with the corresponding order ID in the order DB 130.

  For orders of the “normal” type, for example, the processing of the instruction reception request in S4 and the preparation instruction in S8 may be performed collectively at a predetermined date and time after the data entry deadline. Since an order is urgent, if there is an order input of S1_2, the processes of S4 and S8 are performed without waiting for the predetermined batch processing date and time.

  Next, a flow of processing related to an order that is determined as the “continuation” type in S3 and registered in the management DB 120 will be described with reference to FIG. 3 is performed between the issuing unit 110 of the issuing device 100 and the display input units 310 and 410 of the nurse terminal 300 and the pharmacist terminal 400, and is characterized in that the doctor terminal 200 is not involved.

  In S21, the issuing device 100 determines whether to start processing. Specifically, the process starts depending on whether or not the prescription order input deadline from the doctor terminal 200 or the nurse terminal 300 managed in the schedule table 800 of the schedule DB 140 matches the current date and time information held by the system. Detect when to do. If it is determined that the timing for starting the process has been reached, the issuing device 100 performs the processes after S22.

  In S22, the issuing device 100 determines whether or not the “continuation” type order, that is, the order registered in the management DB 120 should be generated again and registered in the order DB 130 without an instruction from the doctor terminal 200. For the order to be registered, an order is generated and registered in the order DB 130. Details of the continuous issue process in S22 will be described later with reference to FIG.

  The processing in S23 to S30 for the order newly registered in the order DB 130 in S22 is the same as the processing in S4 to S11 in FIG.

  Next, details of the issuing process executed by the issuing unit 110 of the issuing device 100 in S3 of FIG. 2 will be described with reference to FIG.

  In S31, the issuing unit 110 identifies whether the received order information is transmitted from the doctor terminal 200 or the nurse terminal 330, and what kind of prescription target drug is included in the order information.

  Although not shown, the issuing device 100 manages the address information of the doctor terminal 200, the nurse terminal 300, and the pharmacist terminal 400, and from which terminal the address information is transmitted from the address of the order information transmission source. It is possible to identify.

  In S32, the issuing unit 110 determines whether or not the received order is an order of the “temporary” type. Specifically, if the transmission source of the order information is the nurse terminal 300, the order is determined to be a “temporary” type order.

  If it is determined that the order is a “temporary” type, the issuing unit 110 identifies the patient ID included in the received order, proceeds to S36, and deletes the order with the matching patient ID from the management table 600 of the management DB 120. The “temporary” type order can be predicted that the condition of the target patient has changed suddenly, and the nurse has instructed an urgently required drug prescription without waiting for the doctor's instruction. Therefore, it is necessary to cancel the order that has been instructed before and determined to be the “continuation” type, wait for the doctor's instruction again. For this reason, the issuing unit 110 executes the process of S36.

  Then, the issuing unit 110 proceeds to S37, generates a new record in the order table 700 of the order DB 130, registers the order information determined to be the “temporary” type, and completes the issuing process. When registering, the issuing means 110 newly generates an order ID, associates it with the order ID, sets “temporary” as the type item, and sets each item of patient ID, instruction content, and quantity based on the received order information. Register information in. Also, the date and time when the information was registered is recorded in the registration date item.

  On the other hand, if it is determined in S32 that the order is not the “temporary” type, the issuing unit 110 determines whether or not the received order information is the “continuous” type order in S33. Specifically, the issuing unit 110 refers to the target table 900 of the target DB 150 and determines whether or not a prescription target drug included in the received order information is included in the target table 900. Alternatively, in the case of the “continuation” type order, the expiration date of how long this order is valid is included in the order information, so that it may be determined as the “continuation” type order.

  If it is determined that the order is the “continuation” type, the issuing unit 110 proceeds to S34. In S <b> 34, the issuing unit 110 generates a new record in the management table 600 of the management DB 120 and registers the order determined as the “continuation” type. At this time, the issuing means 110 generates a new order ID, associates it with the order ID, and registers information in each item of patient ID, instruction content, amount, and end date (expiration date) based on the received order information. Further, the issuing unit 110 proceeds to S35, generates a new record in the order table 700 of the order DB 130, registers the received order information determined as the “continuation” type, and completes the issuing process. When registering in the order table 700, the issuing unit 110 sets “continuation” in the type item in association with the order ID generated in S34, and each item of patient ID, instruction content, and quantity based on the received order information. Register information in. Also, the date and time when the information was registered is recorded in the registration date item.

  On the other hand, if it is determined in S33 that the order is not the “continuation” type, this order is an order of the “normal” type. Therefore, the issuing unit 110 proceeds to S38 and receives the received order information determined as the “normal” type. Is registered in the order table 700 of the order DB 130, and the issuing process is completed. When registering, the issuing means 110 generates a new order ID, associates it with the order ID, sets “normal” in the type item, and sets each item of patient ID, instruction content, and quantity based on the received order information. Register information in. Also, the date and time when the information was registered is recorded in the registration date item.

  The above is the details of the issuing process in S3 of FIG. 2 executed by the issuing unit 110 of the issuing device 100.

  Next, details of the continuous issue processing executed by the issuing unit 110 of the issuing device 100 in S22 of FIG. 3 will be described with reference to FIG.

  In S41, the issuing unit 110 identifies the next order entry deadline based on the schedule table 800 and the current date and time of the system, and stores it in the work memory.

  For example, it is assumed that the current date and time is March 3 at 10:00 am. Referring now to the schedule table 800 of FIG. 8, the order entry deadline is 10:00 am every day, so 10 am on March 3 is the current entry deadline, and the next entry deadline is 10 am on March 4th the next day. It will be time.

  In S <b> 42, the issuing unit 110 reads the first record of the management table 600 of the management DB 130.

  In S43, the issuing unit 110 confirms the end date item of the read record. If the current date and time has passed the set end date, it is determined that the order should not be continued, and the issuing unit 110 proceeds to S44 and deletes the record from the management table 600 of the management DB 120. , Go to S50.

  On the other hand, if the current date does not exceed the end date in S43, the issuing unit 110 proceeds to S45, and reads the “continuation” type managed in the order table 700 of the order DB 130 by referring to the order. The most recent record is specified in the same record as the record order ID.

  In S46, it is determined whether or not the instruction receiving item of the latest record with the specified order ID is set to “Done”, and whether or not the execution date / time information is recorded in the execution item. As a result of the determination, if the instruction receiving item is not “completed” or if the execution item is not recorded, the issuing unit 110 proceeds to S44 and deletes the corresponding order ID record from the management table 600 of the management DB 120. Then, the process proceeds to S50. In this process, some abnormality occurred, such as a sudden change in the condition of the patient in the corresponding order, so the nurse did not perform the instruction reception confirmation process for this `` continue '' type order, or the prescription target drug was actually administered It is executed because there is a risk that it has not been done and it is not recognized as an order to continue any further.

  On the other hand, in S46, when the record specified in the order table 700 has received the instruction and has been executed (recording of the execution date / time information), the issuing unit 110 proceeds to S47 and completes the prescription target that was previously executed. Predict the date and time. Specifically, the total amount of the prescription subject recorded in the prescription amount item of the specified record is divided by the administration pace of the remarks item to obtain the completion time, and the completion time is added starting from the execution date and time information. Calculate the end date and time.

  In step S48, the issuing unit 110 determines whether or not the calculated end date / time reaches the next order input deadline obtained in step S41. When the end date / time reaches the next input deadline, that is, at the next input deadline, when it is determined that the previous administration of the medicine has not yet been completed, an order to be transmitted to the pharmacist terminal 400 is generated at the current input deadline. Since there is no need to do this, the issuing means 110 proceeds to S50.

  On the other hand, if the calculated end date / time does not reach the next input deadline in S48, that is, if the previous drug administration is completed by the next input deadline, the order to be transmitted to the pharmacist terminal 400 at the current input deadline. Therefore, the issuing unit 110 proceeds to S49, generates a new record in the order table 700 of the order DB 130, and based on the order information of the read record, new “continuation” type order information is added to the new record. Record. Also, the date and time when the information was registered is recorded in the registration date item. At this time, the order ID is not newly generated, and the order ID of the read record is used as it is.

  In addition, when the remaining period until the end date reaches a predetermined period amount, there is a risk of overdose if it is set according to the prescription amount of the management table 600. In this case, the prescription amount is a prescription amount item of a new record. When a request for receiving an instruction is transmitted to the nurse terminal 300 without recording the request, a request screen having an input area for allowing the nurse to set a necessary amount is generated and transmitted, and the instruction from the nurse terminal 300 is transmitted. The prescription amount included in the received information shall be recorded.

  In S50, the issuing unit 110 determines whether or not there is an unprocessed next record in the management table 600, and if it exists, the process proceeds to S51, and after reading the next record, the process proceeds to S43. Return. On the other hand, when the next record does not exist, a series of continuous issue processing is completed.

  Finally, how data of the “continuation” type that is a feature of the present invention is processed when data as shown in FIG. 7 is recorded in the order table 700 will be described with reference to FIG.

  The order table 700 of FIG. 7 shows data contents at the time of March 3 at 10 am, that is, when the order entry deadline is reached. FIG. 10 shows only the order of the patient corresponding to the “continuation” type order in the order table 700. It is assumed that the orders transmitted to the pharmacist terminal 400 at the previous order entry deadline (= 10 am on March 2) are the most recent orders for all these “continuation” type orders.

  Now, assuming that the order entry deadline at 10 am on March 3 has been reached, the contents of these “continuation” type orders will be examined.

  First, it can be seen from the record content of the order table 700 in FIG. 7 that the order ID “0002” starts infusion administration at 1 pm on March 2 and is infused at a dosage rate of 10 units per hour. Since the total amount of infusion is 600 units, the required administration time is 60 hours. When the administration end date and time is calculated based on the administration start date and time, 1 am on March 5 is the end date and time. On the other hand, the next order entry deadline is March 4 at 10:00 am, and therefore the order ID “0002” does not have to be the order to be transmitted to the pharmacist terminal 400 with the current entry deadline. Therefore, the continuous issuance process for the order ID “0002” is a determination process of “YES” in S48 of FIG. 5, and the continuous issuance process is completed without generating a new order.

  Next, considering the order ID “0004”, it can be seen from the order table 700 in FIG. 7 that the infusion is started at 1 pm on March 2, and is infused at an administration pace of 10 units per hour. Since the total amount of infusion is 300 units, the administration time is 30 hours, and from this, the administration is predicted to be completed at 9 pm on March 3. On the other hand, the next order entry deadline is 10 am on March 4, and therefore, the infusion of the order ID “0004” will be interrupted by the next order entry deadline. It is necessary to generate an order as an order to be transmitted. Therefore, the continuous issuance process for the order ID “0004” is a determination process of “NO” in S48 of FIG. 5, and the order registration process of S49 is performed.

  Next, considering the order ID “0005”, tablets for two days (March 2 and March 3) at 1:00 pm on March 2 were given to the patient. Therefore, it will be necessary to deliver tablets after March 4th at 10 am on the next order entry deadline on March 4th. However, it should be noted here that an order of “temporary” type (order ID “0008”) is instructed to the same patient “150” corresponding to this order at 1 am on March 3rd. It is. According to the issuance process of FIG. 4, since “YES” determination is made in the determination process of S32, the order ID “0005” is deleted from the management table 600 of the management DB 120 in S36. Therefore, the order ID “0005” does not exist in the management table 600 at 10:00 am on March 3 of the current order entry deadline, and thus is not a target of the continuous issue process of FIG.

  Next, considering the order ID “0006”, in the order table 700 of FIG. 7, the instruction received item remains “not yet”. Therefore, in the last order entry deadline at 10 am on March 2, the order was not transmitted to the pharmacist terminal 400 after all. Therefore, according to the continuous issuance process of FIG. 5, the determination process of S46 is “No”, and the process proceeds to S44, where the order is deleted from the management table 600, and the target order of the continuous issuance process after the next order entry deadline. Not.

  As described above, the embodiment in which the present invention is applied to the medical field has been described. However, when the prescription order is received, the identification information of the doctor is also received, and the “continuation” type deleted from the management DB 120 before the expiration date of the expiration date. The data may be notified to the contact associated with the identification information of the doctor who has instructed the “continuation” type order when the data is deleted.

  Further, in this embodiment, when an order of the “Temporary” type is accepted, all orders of the “Continuous” type for the corresponding patient are deleted, but the contents of the order of the “Temporary” type (for example, what prescription target drugs are available) )), The “continuation” type order to be deleted may be limited.

Further, the application field of the present invention is not limited to the medical field. For example, in fields where fuel such as chemicals, coal, gas, and water must be continuously replenished, or consumables and wear parts such as gears, metals, rubber products must be replaced after a certain period of time. The present invention is also applicable in such fields.
(Supplementary note 1) A prescription instruction device connected to an instruction terminal for instructing a prescription order and a preparation terminal for preparing an ordered prescription target, and instructing the prescription order to the preparation terminal,
A continuation table in which prescription targets to be ordered and prescription amounts indicating the amounts of the prescription targets are managed in association with prescription identification information;
In correspondence with the prescription identification information, a prescription table in which the start date and time when the prescription target for which prescription is instructed and the execution status of the prescription target are managed,
A schedule table in which an instruction date and time for instructing the prescription order to the preparation terminal is managed,
Receiving means for receiving a prescription order including a prescription amount from an instruction terminal;
Issuing prescription identification information to the received prescription order, the registration means for registering the prescription order in the continuation table;
The prescription identification information registered in the continuation table is searched with reference to the prescription table, the start date and time and the implementation status corresponding to the searched prescription identification information are identified, and the prescription identification information in the continuation table is supported. A calculating means for calculating the execution end date and time of the prescription object based on the prescription amount to be
The next instruction date and time to be instructed to the preparation terminal next time is specified from the schedule table, the next instruction date and time is compared with the calculated execution end date and time, and the execution end date and time does not reach the next instruction date and time, the continuation Generating means for identifying a prescription object related to the prescription identification information from the table and generating a prescription order for the prescription object;
An instruction unit that transmits the generated prescription order to the preparation terminal. (1)
(Appendix 2) A prescription instruction method for instructing a prescription order to a prescription order connected to an instruction terminal for instructing a prescription order and a preparatory terminal for preparing an ordered prescription object,
Computer
A reception step for receiving a prescription order including a prescription amount from an instruction terminal;
After issuing the prescription identification information to the received prescription order, the prescription order is associated with the prescription identification information in the continuation table in which the prescription target to be ordered and the prescription amount indicating the amount of the prescription target are managed. A registration step to register
The prescription registered in the continuation table with reference to the prescription table in which the start date and time of execution of the prescription target and the implementation status of the prescription target are managed in association with the prescription identification information A calculation step of searching for identification information, identifying a start date and time and an execution status corresponding to the searched prescription identification information, and calculating an execution end date and time of a prescription object based on a prescription amount corresponding to the prescription identification information in the continuation table When,
From the schedule table in which the instruction date and time for instructing the prescription order to the preparation terminal are managed, the next instruction date and time to instruct the preparation terminal next time is specified, and the next instruction date and time is compared with the calculated execution end date and time. When the end date / time does not reach the next instruction date / time, from the continuation table, a prescription target related to the prescription identification information is identified, and a generation step for generating a prescription order for the prescription target;
An instruction step of transmitting the generated prescription order to the preparation terminal. (2)
(Supplementary note 3) Prescription instruction method according to supplementary note 2,
The prescription table further includes a confirmation flag indicating whether or not the prescription order has been confirmed before the computer transmits the prescription order to the preparation terminal in an instruction step in association with prescription identification information. And
In the prescription instruction method, when the computer indicates that the confirmation flag corresponding to the prescription identification information retrieved from the prescription table is not confirmed, the execution end date and time is not calculated. (3)
(Appendix 4) The prescription instruction method according to Appendix 2,
In the calculation instruction method, the computer does not calculate the execution end date and time when the execution status corresponding to the searched prescription identification information is not recorded.
(Additional remark 5) It is the prescription instruction | indication method of Additional remark 2,
In the continuation table and the prescription table, in addition to prescription identification information, a prescription subject that is a subject to which the prescription subject is to be administered is managed,
Furthermore, in the prescription table, further, emergency information indicating an urgently instructed prescription is managed in association with the urgently instructed prescription identification information,
In the calculation step, the computer does not calculate the execution end date and time when the emergency information is recorded in association with the searched prescription identification information.
(Supplementary note 6) The prescription instruction method according to supplementary note 2,
In the registration step, the computer refers to a definition table in which prescription targets to be registered in the continuation table are managed, and whether the prescription targets included in the prescription order received in the reception step are included in the definition table. The prescription ordering method is characterized in that the prescription order is registered in the continuation table only when it is determined whether or not it is included.

It is a figure which shows the system configuration example of this invention. It is a whole processing flow figure with respect to the "normal" and "temporary" classification order of this invention. It is a whole processing flow figure with respect to the "continuation" classification order of this invention. It is a detailed process flowchart of the issuing process of this invention. It is a detailed process flowchart of the continuous issue process of this invention. It is a figure which shows the management table 600 of this invention. It is a figure which shows the order table 700 of this invention. It is a figure which shows the schedule table 800 of this invention. It is a figure which shows the object table 900 of this invention. It is a prescription time series conceptual diagram based on the order table 700 of FIG. 7 of the present invention.

Explanation of symbols

100 Issuing device 110 Issuing means 120 Management DB (database)
130 Order DB (database)
140 Schedule DB (database)
150 Target DB (database)
200 Doctor terminal 210, 310, 410 Display input means 300 Nurse terminal 400 Pharmacist terminal 600 Management table 700 Order table 800 Schedule table 900 Target table

Claims (3)

An instruction terminal for instructing a prescription order, and a prescription instruction apparatus connected to a preparation terminal for preparing an ordered prescription target, instructing the prescription order to the preparation terminal,
A continuation table in which prescription targets to be ordered and prescription amounts indicating the amounts of the prescription targets are managed in association with prescription identification information;
In correspondence with the prescription identification information, a prescription table in which the start date and time when the prescription target for which prescription is instructed and the execution status of the prescription target are managed,
A schedule table in which an instruction date and time for instructing the prescription order to the preparation terminal is managed,
Receiving means for receiving a prescription order including a prescription amount from an instruction terminal;
Issuing prescription identification information to the received prescription order, the registration means for registering the prescription order in the continuation table;
The prescription identification information registered in the continuation table is searched with reference to the prescription table, the start date and time and the implementation status corresponding to the searched prescription identification information are identified, and the prescription identification information in the continuation table is supported. A calculating means for calculating the execution end date and time of the prescription object based on the prescription amount to be
The next instruction date and time to be instructed to the preparation terminal next time is specified from the schedule table, the next instruction date and time is compared with the calculated execution end date and time, and the execution end date and time does not reach the next instruction date and time, the continuation Generating means for identifying a prescription object related to the prescription identification information from the table and generating a prescription order for the prescription object;
An instruction unit that transmits the generated prescription order to the preparation terminal. An instruction terminal for instructing a prescription order, and a prescription instruction method for instructing the prescription order to the preparatory terminal connected to a preparation terminal for preparing the ordered prescription object,
Computer
A reception step for receiving a prescription order including a prescription amount from an instruction terminal;
After issuing the prescription identification information to the received prescription order, the prescription order is associated with the prescription identification information in the continuation table in which the prescription target to be ordered and the prescription amount indicating the amount of the prescription target are managed. A registration step to register
The prescription registered in the continuation table with reference to the prescription table in which the start date and time of execution of the prescription target and the implementation status of the prescription target are managed in association with the prescription identification information A calculation step of searching for identification information, identifying a start date and time and an execution status corresponding to the searched prescription identification information, and calculating an execution end date and time of a prescription object based on a prescription amount corresponding to the prescription identification information in the continuation table When,
From the schedule table in which the instruction date and time for instructing the prescription order to the preparation terminal are managed, the next instruction date and time to instruct the preparation terminal next time is specified, and the next instruction date and time is compared with the calculated execution end date and time. When the end date / time does not reach the next instruction date / time, from the continuation table, a prescription target related to the prescription identification information is identified, and a generation step for generating a prescription order for the prescription target;
An instruction step of transmitting the generated prescription order to the preparation terminal. A prescription instruction method according to claim 2,
The prescription table further includes a confirmation flag indicating whether or not the prescription order has been confirmed before the computer transmits the prescription order to the preparation terminal in an instruction step in association with prescription identification information. And
The calculation instruction method does not calculate the execution end date when the computer indicates that the confirmation flag corresponding to the prescription identification information retrieved from the prescription table is not confirmed.

Images