JP2009110363A - Medical information management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a medical information management system for efficiently managing orders. <P>SOLUTION: In a medical information management server 100, an order execution information management part 180 determines, upon receipt of execution information from a portable terminal device 70, whether the date thereof belongs to an order issuing period, and whether the order is to be repeatedly issued. When the date belongs to the order issuing period and the order is to be repeatedly issued, the management part 180 determines whether the an upper limit or a lower issuing limit is reached. When the upper issuing limit is not reached, the management part 180 determines to reissue the order, and reports an original order ID to an order reissuing part 120. When the lower issuing limit is reached, the management part 180 further reports that effect to a display screen data generation part 150, and the generation part 150 generates display information showing that the lower issuing limit is reached. The order reissuing part 120 forms a duplicate of the order to reissue the order. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to business support technology in medical facilities and the like, and more particularly, to a medical information management system that manages an order for specifying the contents of medical practice in a hospital.

In medical facilities such as hospitals, information management systems such as electronic medical record systems and order systems have been introduced in order to efficiently carry out the work of medical staff such as doctors and nurses and prevent medical errors. Yes. In such a system, when a medical worker who has performed a medical practice performs a completed input, the fact that it has been performed is recorded and displayed. For example, the medical plan and recording support system proposed in Document 1 displays a status display mark in the medical plan table according to the situation such as whether or not an order related to each medical practice has already been issued. The ordered order is displayed in the “order record” column. Document 2 discloses that in a medical item confirmation system, a symbol mark assigned to a state of medical data such as an order being issued or executed is displayed.
JP 2001-52073 A JP 2005-353086 A

  In the order system, the server issues an order for identifying the content of the medical practice, the mobile terminal for the nurse receives it, and the user such as a nurse carries out the content of the medical practice performed by the nurse according to the order information. Input to the terminal. Since a medical error can lead to a serious problem, such an order system is required to make a strict plan according to instructions on medical practice and to manage the implementation status reliably. On the other hand, since medical practice is intended for humans, it is often difficult to operate strictly, and such an order system is required to have flexibility to allow ambiguity.

  For example, for a certain type of medical practice, the implementation time and the number of implementations are not determined in advance, and must be implemented as needed. As an example, suction of sputum or the like is performed as needed while watching the state of the patient each time. However, in the order system, it is not easy to efficiently issue an order of medical practice whose execution time and number of executions are not determined. For example, a method may be considered in which a plurality of orders are issued in advance and the nurse sequentially executes the orders. In this case, the same order is always displayed on the nurse's mobile terminal. Therefore, there is a problem that it is troublesome. There is also a problem that nurses cannot receive orders from the order system because there are no orders issued when the number of medical actions performed on patients reaches the number of orders issued due to deterioration of the patient's condition. .

  This invention is made | formed in view of such a subject, The objective is to provide the medical information management system which can issue an order efficiently.

  In order to solve the above problems, a medical information management system according to an aspect of the present invention includes an order issuing unit that issues an order, an implementation information receiving unit that receives implementation information that is an implementation result for the order, and an implementation information receiving unit. When the execution information is received, an order reissuing unit that creates a copy of the order and reissues the order is provided.

  According to this aspect, it is possible to reissue an order related to a medical practice to be repeatedly performed without giving instructions from a doctor or a nurse each time.

  It should be noted that any combination of the above-described constituent elements and a conversion of the expression of the present invention between a method, an apparatus, a system, a recording medium, a computer program, etc. are also effective as an aspect of the present invention.

  According to the present invention, it is possible to efficiently manage an order for which the execution time and the number of executions are not specified.

  Hereinafter, embodiments of the present invention (hereinafter referred to as “embodiments”) will be described in detail with reference to the drawings.

  FIG. 1 shows a configuration example of a hospital information system 10 including a medical information management system 30 according to an embodiment of the present invention. The hospital information system 10 is installed in a medical facility such as a hospital and includes a hospital information management server 20, doctor personal computers 40 a and 40 b (hereinafter collectively referred to as “doctor PC 40”), and a medical information management system 30. These are set so as to be able to transmit and receive each other on a network 90 such as an intranet. The hospital information management server 20 controls and manages the operation of subsystems such as the medical information management system 30. For example, a plurality of medical information management systems 30 may be installed for each department.

  The hospital information management server 20 includes an order issuing unit 22 that issues an order created by a doctor and input from the doctor PC 40. The order is information for specifying the contents of medical practice issued by medical personnel such as doctors and nurses. In addition to the content of the medical practice, the order may include information such as the implementation time of the medical practice, the number of times the order is issued, and the issue period. The number of times of issuance may be set so that an upper limit, a lower limit, or both can be designated. A specific time may be designated as the implementation time, and it is set so that it can be selected to designate as appropriate without designating the time. Furthermore, it may be set so that a wide time zone can be specified, and for an order that is repeatedly issued, a time interval from the previous execution time to the next order issuing time may be specified.

  The medical information management system 30 includes a medical information management server 100, access points 50a and 50b (hereinafter collectively referred to as “access point 50” or “AP 50”), departmental personal computers 60a and 60b ( Hereinafter, it is collectively referred to as a departmental PC 60), and mobile terminal devices 70a, 70b, and 70c (hereinafter collectively referred to as “mobile terminal device 70”). The medical information management server 100 and the access point 50 or departmental PC 60 are set to be able to transmit and receive each other via a network such as a LAN (Local Area Network). The medical information management server 100 and the mobile terminal device 70 transmit and receive data via the access point 50. In a department where the medical information management system 30 is installed, an order created by a nurse or other medical staff is input from the department PC 60. The medical information management system 30 may be configured without including a part of the access point 50, the departmental PC 60, and the mobile terminal device 70.

  The medical information management server 100 includes an order issuing unit 110, an order reissuing unit 120, an order receiving unit 130, an execution information receiving unit 140, a display screen data generating unit 150, a communication unit 160, an order execution information storage unit 170, and order execution information. A management unit 180 is provided. The order issuing unit 110 issues orders input from the departmental PC 60, the mobile terminal device 70, and the like. The order receiving unit 130 receives orders issued by the order issuing unit 22, the order issuing unit 110, etc., and supplies them to the order execution information management unit 180. The order execution information management unit 180 includes information on the supplied order, an order execution information table stored in the order execution information storage unit 170, and an order issue record stored in the order execution information storage unit 170 as necessary. Record on the table. The order issuing unit 110 and the order reissuing unit 120 may be configured as one module having the functions of both the order issuing unit 110 and the order reissuing unit 120.

  FIG. 2 shows an example of the structure of the order execution information table 300 stored in the order execution information storage unit 170. The order execution information table 300 includes an order ID column 302, an order content column 304, a time column 306, an issue interval column 307, an upper limit count column 308, a lower limit count column 310, a period column 312, and an implementation status column 314. In the order ID column 302, an order ID uniquely given to each order is described. The order ID is also given to each order individually for orders that are expected to be issued repeatedly (hereinafter referred to as “repeated orders”). For example, in FIG. 2, “gauze replacement” of order IDs 1002, 1006, and 1009 and “temperature detection” of order IDs 1003 and 1008 are orders that are repeatedly issued, but different order IDs are given to the orders. In the order content column 304, the content of the medical practice is described. In the time column 306, when the execution time is specified, the execution time is not specified, and an order to be appropriately executed is described as “appropriate”.

  For repeated orders, an upper limit and a lower limit of the number of times to be performed per day may be instructed. For example, the maximum number of times is specified for the administration of a dose medicine, and the minimum number of times may be instructed as a reference for the minimum number of times for calling the patient, watching the situation, and the like. In addition to this, for example, in the measurement of vital signs such as body temperature, there may be an instruction that the execution time is not specified but the measurement may be performed a predetermined number of times per day. The upper limit count column 308 and the lower limit count column 310 describe the upper limit count and the lower limit count, respectively, when the upper limit or lower limit of the count is specified for the repetitive order. In the upper limit count column 308 and the lower limit count column 310, both the upper limit and the lower limit may be specified, or by setting the same value for the upper limit count and the lower limit count, the number of times may be specified. In FIG. 2, the number of executions is specified by describing the same number of times in the upper limit number column 308 and the lower limit number column 310 for the “sample collection” of the order ID 1001 and the “temperature detection” order of the order ID 1003/1008.

  In addition to the number of times to be performed per day, a period for performing the order may be indicated. For example, vital signs are measured daily during hospitalization, and gauze replacement is instructed to be performed for three days after surgery. The period column 312 describes a period in which the order should be executed. The execution status column 314 describes the order execution status indicating whether the order has been executed or not. Furthermore, it may be possible to describe the time interval from the order execution time input to the mobile terminal device 70 in the issue interval field 307 to the next order issue time. In FIG. 2, “2 hours” is specified in the issue interval field 307 for the “temperature detection” order with the order ID 1003/1008, and it is indicated that the next order should be issued after 2 hours have passed since the previous temperature detection. .

  FIG. 3 shows an example of the structure of the order issue record table 330 stored in the order execution information storage unit 170. The order issue record table 330 includes an order ID column 332, a previous execution time column 334, an issue count column 336, and a copy destination order ID column 338. In the order ID column 332, an order ID at the time of initial issuance is described for repeated orders. Hereinafter, this ID is referred to as “original order ID”. The last execution time column 334 describes the latest order execution time for the order executed at least once and the execution information is transmitted from the mobile terminal device 70. In the issue number column 336, the number of times the order has been issued is described. In the copy destination order ID column 338, the order IDs of orders issued for the second and subsequent times are described. For example, in FIG. 3, the order of the original order ID 1002 has already been issued three times as the order ID 1002 for the first time, the order ID 1006 for the second time, and the order ID 1009 for the third time. It was shown to be 15 minutes.

  The order execution information management unit 180 refers to the information regarding the upper limit number of times for the newly issued order, and if it is determined to be a repetitive order, it adds the issue record of the order to the order issue record table 330. Then, “1” is set as an initial value in the issuance count column 336, and no initial value is set in the previous execution time column 334 and the duplication destination order ID column 338.

  Returning to FIG. The display screen data generation unit 150 acquires information related to the order from the order execution information table 300 stored in the order execution information management unit 180 or the order execution information storage unit 170, and displays display screen data to be displayed on the mobile terminal device 70. Created and supplied to the communication unit 160. The communication unit 160 transmits the supplied display screen data to the mobile terminal device 70 via the access point 50. The display screen data generation unit may be provided in the mobile terminal device 70. In this case, the communication unit 160 may acquire information related to the order from the order execution information management unit 180 or the order execution information table 300 and transmit the information to the mobile terminal device 70 via the access point 50.

  When the nurse or other medical worker executes the transmitted order, the nurse or other medical worker inputs an execution record of the order (hereinafter referred to as “execution information”) to the mobile terminal device 70. The execution information transmitted from the mobile terminal device 70 is received by the execution information reception unit 140 and supplied to the order execution information management unit 180. The order execution information management unit 180 searches the order ID column 302 of the order execution information table 300 for the order ID related to the execution information, and updates the corresponding execution status column 314 to “Done”. Further, the order execution information management unit 180 refers to the order issue upper limit count described in the corresponding upper limit count column 308, the order issue lower limit count described in the lower limit count column 310, and the order issue period described in the period column 312. . Note that these values may be referred to collectively, or may be individually referred to as needed. Then, it is determined whether the order issuance upper limit number is not “1”, that is, whether the order is a repetitive order. If the order is a repetitive order, it is determined whether the day belongs to the order issuance period.

  When belonging to the order issue period, the order execution information management unit 180 searches the order ID column 332 or the copy destination order ID column 338 of the order issue record table 330 for the order ID related to the execution information, and the corresponding previous execution time. The column 334 is updated with the time described in the implementation information. Furthermore, the order execution information management unit 180 refers to the corresponding issuance count column 336 and determines whether the issuance count has reached the upper limit count or the lower limit count. When the upper limit number has not been reached, it is determined to reissue the order, and the original reissue unit 120 is notified of the original order ID. Further, when the lower limit number has been reached, the order execution information management unit 180 notifies the display screen data generation unit 150, and the display screen data generation unit 150 generates display information indicating that the lower limit number has been reached. To do.

  The order reissue unit 120 searches the order ID column 302 of the order execution information table 300 for the acquired original order ID. Then, a copy of the order is created, a new order ID is given, and it is reissued. The reissued order is received by the order receiving unit 130 and supplied to the order execution information management unit 180. The order execution information management unit 180 adds the issued order information to the order execution information table 300, describes the new order ID assigned in the duplication destination order ID column 338 of the order issue record table 330, and issues the number of times issued. The number of issues described in the column 336 is incremented. Note that these processes may be executed by the order reissue unit 120. Then, the display screen data generation unit 150 creates display screen data to be displayed on the mobile terminal device 70, and the communication unit 160 transmits the display screen data to the mobile terminal device 70 via the access point 50.

  FIG. 4 shows a configuration example of the mobile terminal device 70 according to the embodiment of the present invention. The mobile terminal device 70 includes a communication unit 72, an input / output processing unit 74, an input receiving unit 76, and a display unit 78. As described above, the mobile terminal device 70 may include the display screen data generation unit 80. The communication unit 72 transmits and receives data wirelessly to and from the medical information management server 100 via the access point 50. The display unit 78 is a display such as a liquid crystal panel, and displays a screen based on display information generated by the display screen data generation unit 150 or the display screen data generation unit 80. The display screen is configured by a GUI (Graphical User Interface), and a user such as a nurse performs desired input using an input / output interface such as a touch pen or a touch panel. The input receiving unit 76 receives input from the user. The input / output processing unit 74 supplies the display screen data received from the medical information management server 100 to the display unit 78, processes the user input received by the input receiving unit 76, and the medical information management server from the communication unit 72. 100 has a function of transmitting.

  Each block shown in FIGS. 1 and 4 can be realized in hardware by a computer CPU, memory, and other LSI, and in software by a computer program or the like. It depicts the functional blocks that are realized. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by hardware only, software only, or a combination thereof.

  Next, a procedure for reissuing an order will be described with reference to FIG. First, an unexecuted order is displayed on the display unit 78 of the mobile terminal device 70 (S10). When the user executes an order (S12) and inputs an execution record to the mobile terminal device 70 (S14), the input receiving unit 76 of the mobile terminal device 70 receives the input, and the input / output processing unit 74 communicates the execution information. The information is transmitted from the unit 72 to the medical information management server 100 via the access point 50 (S16). The transmitted execution information is received by the execution information receiving unit 140 via the communication unit 160 of the medical information management server 100 and supplied to the order execution information management unit 180.

  The order execution information management unit 180 records that the order related to the acquired execution information has been executed (S18). Specifically, the execution status column 314 of the order execution information table 300 is updated to “Done”. When the updated execution record is transmitted to the mobile terminal device 70 (S20), the display unit 78 of the mobile terminal device 70 deletes the executed order from the unexecuted order list and displays it on the executed order list. (S22).

  The display unit 78 of the portable terminal device 70 does not wait for transmission of the completed record from the medical information management server 100 (S20) after the execution record is input (S14), and the order is added from the list of unexecuted orders. Then, it may be moved to the completed order list and displayed (S22). In that case, the step (S20) of transmitting the updated execution record to the mobile terminal device 70 may be omitted.

  Subsequently, the order execution information management unit 180 refers to the period column 312 of the order execution information table 300 and determines whether or not the date belongs to the order issue period (S24). If it does not belong to the order issue period (N in S24), the reissue procedure is terminated. When belonging to the order issue period (Y in S24), the order execution information management unit 180 further refers to the upper limit number column 308 of the order execution information table 300 and the issue number column 336 of the order issue record table 330 to issue It is determined whether the number of times has reached the upper limit of the number of order issuances (S26). If the upper limit has been reached (Y in S26), the reissue procedure is terminated.

  If the number of times of issue has not reached the upper limit of the number of times of order issuance (N in S26), the order execution information management unit 180 determines to reissue the order and notifies the order reissue unit 120 of the original order ID. Subsequently, the order execution information management unit 180 refers to the lower limit number column 310 of the order execution information table 300 and determines whether or not the number of issues has reached the order issue lower limit number (S28). When the lower limit has been reached (Y in S28), the order execution information management unit 180 notifies the display screen data generation unit 150, and the display screen data generation unit 150 displays the display information indicating that the lower limit number of issues has been achieved. Is generated (S30). For example, the character color and the background color may be changed for display, or a mark may be added for display. In addition, the display priority order of the repeated orders at the time of display may be lowered so that it is not displayed on the upper part of the display unit 78, or may be set not to be displayed except when specified. If the lower limit number of issuances has not been reached (N in S28), such display information is not generated.

  The order reissue unit 120 retrieves the original order ID from the order execution information table 300, creates a copy of the order, assigns a new order ID, and reissues it (S32). The order execution information management unit 180 adds the newly issued order to the order execution information table 300, describes the new order ID in the duplication destination order ID column 338 of the order issue record table 330, and issues the number of times issued column The issuance count described in 336 is incremented (S34). Note that the order reissuing unit 120 may execute these processes instead of the order execution information management unit 180.

  The reissued order is transmitted by the communication unit 160 to the mobile terminal device 70 via the access point 50 (S36). When the mobile terminal device 70 receives the reissued order (Y in S38), the reissued order is displayed again on the display unit 78 as an unexecuted order (S10). Therefore, orders that should be repeatedly executed continue to be displayed in the unexecuted order list until the number of order issuance reaches the maximum number of issuances, and it seems that only the previous execution time and the number of order issuance are updated.

  If the time interval from the previous execution time to the next reissuance of the order is designated, the order is issued after the designated time has elapsed without immediately reissuing the order in S32. You may do it. As a result, it is possible to grasp the order to be executed at an appropriate time without immediately redisplaying the repetitive order that has just been executed in the business list for today.

  FIG. 6 shows an example of a screen in which today's business list screen is displayed on the display unit 78 of the mobile terminal device 70. However, in FIG. 6, for the sake of explanation, a display example of repeated orders by a plurality of display methods is shown in a mixed format. On the today's task list screen, the unexecuted task list and the performed task list may be switched and displayed by selecting a tab or the like. For example, the user may be able to display the completed work list tab by instructing “done” with a touch pen or the like on the screen on which the unexecuted work list tab of FIG. 6 is displayed. When the user performs an order displayed in the unexecuted business list and inputs completed information, the order is deleted from the unexecuted business list and displayed in the performed business list.

  An order display 350 in FIG. 6 shows a display example of an order for which time is specified. Order displays 352, 354, 356, 358, and 360 indicate display examples of repeated orders. As for the repetitive order, as shown in the order display 352, the scheduled execution time may be displayed as “-:-” to indicate that it is a repetitive order. As shown in the order display 354, the time In order to distinguish from the order in which is specified, the character color or background color may be changed for display. Further, as shown in the order display 354, the previous execution time may be displayed, the elapsed time from the previous execution time, or the next execution scheduled time calculated from the previous execution time may be displayed. The next execution scheduled time may be calculated by the order execution information management unit 180 referring to the previous execution time column 334 of the order issuance record table 330 and information related to the execution interval. Information relating to the execution interval may be prepared in advance by referring to a table describing the standard execution interval for each work, and may be specified when inputting an order.

  In addition, as shown in the order display 356, the current number of order issuances may be displayed, or the order issuance upper limit number and lower limit number may be displayed. The order display 358 is an example in which the current number of times of order issuance and the designated number of issuances are both displayed, and indicates that the order is to be executed three times and is the second issue. The order display 360 is a display example indicating that the number of order issuance has reached the order issuance lower limit number, and indicates that it is the order issued for the fourth time for an order that should be executed at least three times. When the order issuance count reaches the issuance lower limit count, the order display priority may be lowered and displayed after other orders.

  Since repeated orders continue to exist in the unexecuted list even if they are executed, if a large number of repeated orders are displayed in a format that is mixed with orders for which time is specified, the order you want to see cannot be displayed at the top of the list. There can also be a risk of overlooking important orders. In order to prevent this, the order may be repeatedly displayed after the order for which the time is specified, or may be displayed by switching tabs on another screen, for example. Further, when displaying a large number of orders, such as when all orders of today's ward are acquired and displayed at a time, repeated orders need not be displayed. And it is good also as a setting which displays an order repeatedly only when narrowing down conditions, such as an order for every patient, and an order for every treatment, and displaying a list of unexecuted orders.

  In FIG. 7, when all orders of today's ward are acquired at once, and when orders are acquired by narrowing down conditions such as orders for patients and orders for items, the display unit 78 of the mobile terminal device 70 is displayed. A transition example of the displayed screen is shown. When acquiring all of today's orders at a time, when the user selects “Today's Work List” on the work list selection screen 410, the mobile terminal device 70 sends to the medical information management server 100 all the orders of the current ward. Send a send request. When the medical information management server 100 receives the transmission request, the medical information management server 100 transmits all the orders of today's ward to the mobile terminal device 70. When the mobile terminal device 70 receives the data, the display unit 78 displays today's business list screen 420. When the user selects one of the lists on this screen, a patient and an item are selected, and a patient authentication screen 480 is displayed. Thereafter, an order execution input process is advanced. In patient authentication, for example, an identification mark attached to a wristband or a medical examination ticket may be optically read, or an identification number may be input.

  In the ward, since a plurality of orders are generally issued for each patient and a person in charge is often determined for each patient, there is a request for obtaining a business list for each patient. When the user selects “operation list for each patient” on the operation list selection screen 410, a patient selection screen 430 is displayed on the display unit 78. When a patient is selected and input on this screen, the operation item selection screen 440 is displayed. Is displayed. In addition, it is good also as a setting which displays the work item selection screen 440 or work list screen about a patient in charge immediately after logging in by setting beforehand.

  On the business item selection screen 440, the user can select all the items for the patient, or can select only one item. For example, when the user selects the item “Vital” on the work item selection screen 440, the mobile terminal device 70 requests the medical information management server 100 to transmit an order related to “Vital” of the designated patient. When the medical information management server 100 transmits the designated data to the portable terminal device 70, the work list screen 450 is displayed on the display unit 78, and only the order related to “vital” that is the designated item of the designated patient is displayed. ,Is displayed. Here, when the user selects one order, the screen transits to the patient authentication screen 480, and thereafter, the order execution input process proceeds in the same manner.

  On the other hand, in the case of outpatients, since the number of patients is very large, it is difficult to find a target order if a business list is obtained for each patient or an entire business list is obtained. In addition, since there is a case where an instruction for each patient is not given in advance, it is more convenient to narrow down orders from items. When the user selects “business list for each item” on the business list selection screen 410, a business item selection screen 460 is displayed. Here, when one item, for example, a treatment is selected, a task list screen 470 for each item is displayed, and by selecting a patient, the screen transits to the patient authentication screen 480. Is advanced. In addition, when logging in from the startup screen, it is possible to change the subsequent transition screen by selecting “Ward Mode” and “Outpatient Mode”. That is, the setting may be such that the patient selection screen 430 is displayed first when logging in in the “ward mode”, and the work item selection screen 460 is displayed first when logging in in the “outpatient mode”.

  In the business item selection screens 440, 460, etc., the button settings may be configured in a customizable form. That is, the name of the button that transitions to each function, the number of buttons corresponding to the number of items, the transition destination screen when the button is pressed, the arrangement of buttons, and the like may be changed by setting. Thereby, button setting can be changed easily and it can respond flexibly to a different request for each medical facility and each department.

  In the above, this invention was demonstrated based on the Example. It will be understood by those skilled in the art that this embodiment is an exemplification, and that various modifications can be made to combinations of the respective components and processing processes, and such modifications are also within the scope of the present invention. By the way.

It is a figure which shows the structural example of the hospital information system containing the medical information management system concerning this embodiment. It is a figure which shows the structural example of the order execution information table in this embodiment. It is a figure which shows the structural example of the order issue recording table in this embodiment. It is a figure which shows the structural example of the portable terminal device concerning this embodiment. It is a figure explaining the procedure in which an order is reissued in this embodiment. It is a figure which shows the example of a screen which displayed today's work list screen on the display part of the portable terminal device concerning this embodiment. It is a figure which shows the example of a transition of the screen displayed on the display part of the portable terminal device concerning this embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 Hospital information system, 20 Hospital information management server, 22 Order issuing part, 30 Medical information management system, 70 Portable terminal device, 72 Communication part, 74 Input / output processing part, 76 Input reception part, 78 Display part, 80 Display screen data Generating unit, 100 medical information management server, 110 order issuing unit, 120 order reissuing unit, 130 order receiving unit, 140 execution information receiving unit, 150 display screen data generating unit, 170 order execution information storage unit, 180 order execution information management Department.

Claims (6)

An order issuing department that issues orders;
An implementation information receiving unit that receives implementation information that is an implementation result for the order;
When the execution information receiving unit receives the execution information, an order reissue unit that creates a copy of the order and reissues the order;
A medical information management system comprising: An order execution information storage unit for storing the number of times the execution information has been received;
The order issuing unit sets an upper limit number of times an order is issued,
The medical information management system according to claim 1, wherein the order reissuing unit reissues the order until the number of times the implementation information is received reaches the issuance upper limit number. An order execution information storage unit for storing the number of times the execution information has been received;
A display information generating unit for generating display information;
The order issuing unit sets the order issue lower limit number of times,
2. The medical information according to claim 1, wherein the display information generation unit creates display information indicating that the issue lower limit number has been reached when the number of times the implementation information is received reaches the issue lower limit number. Management system. An order execution information storage unit for storing execution information;
The order issuing unit sets information on the execution date of the order,
The medical information management system according to claim 1, wherein the order reissuing unit reissues the order only on a date that coincides with the implementation date. A display unit for displaying the order;
The medical information management system according to any one of claims 1 to 4, wherein the display unit displays an order scheduled to be reissued for an order scheduled to be reissued. A display unit for displaying the order;
The order reissuing unit re-issues the order by adding information on the time at which the order is included in the received execution information.
The medical information management system according to any one of claims 1 to 4, wherein the display unit displays information related to a time when the previous order was performed together with the reissued order.