JP6867585B2 - Work management program, work management device and work management method - Google Patents

Description

The present invention relates to a work management program, a work management device, and a work management method.

There is known a management system that accepts registration of information indicating a work (ToDo) to be performed by a user and enables the user to confirm the registered information. For example, a list listing the registered information is generally called a "ToDo list".

In addition, the following techniques related to ToDo have been proposed. For example, a library management system has been proposed that generates ToDo list data composed of each tray identifier, business name, and number of business management records based on tray conditions. Further, for example, in the mail sending / receiving system, a mail sending / receiving system has been proposed in which a new item is added to the recipient's ToDo list when the mail recipient accepts the item specified in the mail.

Japanese Unexamined Patent Publication No. 2008-27079 JP-A-2002-297512

By the way, in some management systems that manage the work to be performed by the user, when the work based on the registered information is completed, it is possible to record the completion of the work. When such a management system is used, the user, for example, performs an operation of calling up the registered information, confirms the content, and performs work based on the confirmed content. Then, when the work is completed, the user performs an operation of calling the registered information and registers that the work is completed. However, in such a procedure, after the work is completed, information indicating a work different from the work may be erroneously called, and the completion of the work may be registered. In this case, there is a problem that the management accuracy of the work by the management system is lowered.

In one aspect, it is an object of the present invention to provide a work management program, a work management device, and a work management method that can improve the work management accuracy.

In one aspect, a work management program is provided. This work management program receives a request for registration of work information indicating the work to be performed in the computer, registers the work information in the storage unit, and receives a request for registration of work information indicating the work of creating a document as the work. , The user who performs the creation work and the type of the document to be created are registered in the storage unit in association with the work information, and when a confirmation instruction for confirming the document being created is received, the work information registered in the storage unit is received. The first work information associated with the user who performed the confirmation instruction operation and the type of the document being created is searched for, and when the first work information is searched, the first work information is searched. Displays a confirmation screen to confirm whether to change to the completed state indicating the completion of the work, and when the permission operation to allow the change to the completed state is accepted, the first work information is changed to the completed state. Let the process be executed.

Also, in one aspect, a work management device is provided. This work management device has a storage unit and a control unit. The control unit receives a work information registration request indicating the work to be performed, registers the work information in the storage unit, and when it receives a work information registration request indicating the document creation work as the work, the control unit performs the creation work. When the user to perform and the type of the document to be created are registered in the storage unit in association with the work information and a confirmation instruction for confirming the document being created is received, the work information registered in the storage unit is confirmed. The first work information associated with the user who performed the instruction operation and the type of the document being created is searched, and when the first work information is searched, the first work information is used to complete the work. When a confirmation screen for confirming whether to change to the completed state is displayed and a permission operation for permitting the change to the completed state is accepted, the first work information is changed to the completed state.

Also, in one aspect, a work management method is provided. In this work management method, when the computer receives a work information registration request indicating the work to be performed, the work information is registered in the storage unit, and the work information registration request indicating the document creation work is received as the work. , The user who performs the creation work and the type of the document to be created are registered in the storage unit in association with the work information, and when a confirmation instruction for confirming the document being created is received, the work information registered in the storage unit is received. The first work information associated with the user who performed the confirmation instruction operation and the type of the document being created is searched for, and when the first work information is searched, the first work information is searched. Displays a confirmation screen for confirming whether to change to the completed state indicating the completion of the work, and when the permission operation for permitting the change to the completed state is accepted, the first work information is changed to the completed state.

On one side, work management accuracy can be improved.

It is a figure which shows the work management apparatus of 1st Embodiment. It is a figure which shows the information processing system of the 2nd Embodiment. It is a figure which shows the hardware example of the management server. It is a figure which shows the functional example of the management server. It is a figure which shows the example of the user table. It is a figure which shows the example of the ToDo information table. It is a figure which shows the example of the ToDo state table. It is a figure which shows the example of the patient table. It is a figure which shows the example of the medical record display table. It is a figure which shows the example of the template table. It is a figure which shows the example of the ToDo creation screen. It is a figure which shows the example of the ToDo creation list screen. It is a figure which shows the example of the ToDo list screen. It is a figure which shows the example of the ToDo detail screen. It is a figure which shows the example of the medical record screen. It is a figure which shows the example of the ToDo creation screen in which the input field of a patient can be input. It is a figure which shows the example of the ToDo creation screen in which the information based on a template is set. It is a flowchart which shows the example of the display process of the medical record screen. It is a flowchart (the 1) which shows the example of the display process of the ToDo creation screen. It is a flowchart (the 2) which shows the example of the display process of the ToDo creation screen. It is a flowchart which shows the example of the notification processing of ToDo information. It is a flowchart which shows the example of the display processing of the ToDo detail screen. It is a figure which shows the example in the case of modifying the content of ToDo information from the ToDo creation list screen. It is a flowchart which shows the example of the correction processing of ToDo information. It is a figure which shows the example in the case of deleting ToDo information. It is a flowchart which shows the example of the deletion process of ToDo information. It is a figure which shows the example of the discharge summary creation screen. It is a figure which shows the example of the ToDo creation screen of the discharge summary approval request. It is a flowchart which shows an example of a series of processing starting from discharge summary preparation.

Hereinafter, the present embodiment will be described with reference to the drawings.
[First Embodiment]
FIG. 1 is a diagram showing a work management device according to the first embodiment. The work management device 1 is connected to the display 2, and can display a screen on the display 2 and receive information input to the displayed screen. For example, the work management device 1 may be connected to a terminal device having the display 2 instead of being directly connected to the display 2.

The work management device 1 has a storage unit 1a and a control unit 1b. The storage unit 1a may be a volatile storage device such as a RAM (Random Access Memory) or a non-volatile storage device such as an HDD (Hard Disk Drive) or a flash memory. The control unit 1b is, for example, a processor. The processor may include a CPU (Central Processing Unit), a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), and the like. Further, the control unit 1b may be a multiprocessor.

The control unit 1b accepts the registration of the work information 3a, 3b, 3c, ... Indicates the work to be performed by the user, and registers the received work information 3a, 3b, 3c, ... In the storage unit 1a. For example, the user inputs the content of the work on the registration screen 2a displayed on the display 2 and performs the registration operation of the input information. The control unit 1b registers the input information in the storage unit 1a in response to the registration operation.

Further, the user can call the registered work information 3a, 3b, 3c, ... By a predetermined operation for instructing the control unit 1b, and can confirm their contents. For example, when the user displays work information indicating the work to be performed on the display 2 and performs a selection operation on one of them, the content of the selected work information is displayed on the display 2. As a result, the user can confirm the content of the work to be performed and perform the work.

Here, when the control unit 1b receives the registration request of the work information 3x indicating the document creation work as the work to be performed, the control unit 1b determines the user who performs the creation work 3x and the type of the document to be created. It is registered in the storage unit 1a in association with 3x.

Further, the control unit 1b can receive a confirmation instruction for confirming the document 4 being created. For example, the user creates a document 4 by an input operation on the creation screen 2b displayed on the display 2, and performs an operation for a confirmation instruction when the creation is completed. The control unit 1b receives a confirmation instruction in response to this operation.

When the control unit 1b receives the confirmation instruction, the user who has performed the confirmation instruction operation is associated with the type of the document 4 from the work information 3a, 3b, 3c, ... Registered in the storage unit 1a. Search the work information 3y. For example, when the type of the user who performed the confirmation instruction operation and the type of the created document 4 are the same as the type of the user and the document associated with the work information 3x, respectively, the work information 3y that meets the above conditions. The work information 3x is searched as.

When the work information 3y that matches the above conditions is searched, the control unit 1b displays a confirmation screen 2c for confirming whether to change the work information 3y to the completion state indicating the completion of the work. Then, when the control unit 1b receives the permission operation for permitting the change to the completed state, the control unit 1b changes the work information 3y to the completed state.

According to the above processing, when the user who has performed the document 4 creation work performs the confirmation instruction operation and completes the creation work, the document 4 creation work is performed through the confirmation screen 2c that is automatically displayed thereafter. The work information 3y shown can be changed to the completed state. Therefore, after completing the creation work of the document 4, the user can change the work information 3y to the completed state without performing an operation for calling the work information 3y and changing the work information 3y to the completed state.

By such a procedure, it is possible to reduce the possibility that the user who has completed the work of creating the document 4 mistakenly calls the work information indicating the work different from this work and changes the work information to the completed state. Therefore, the work management accuracy of the work management device 1 can be improved. Further, since the user who has completed the creation work of the document 4 does not have to perform the operation of calling the work information 3y corresponding to this work again, the operability of the user can be improved.

In the example of FIG. 1, the registration screen 2a, the creation screen 2b, and the confirmation screen 2c are displayed on the same display 2, but this point is not essential, and they are different displays (for example, different terminals). It may be displayed on the display of the device).

[Second Embodiment]
FIG. 2 is a diagram showing an information processing system according to the second embodiment. The information processing system includes a management server 100 and terminal devices 200, 200a, 200b. The management server 100 and the terminal devices 200, 200a, 200b are connected to each other via the network 300. For example, the network 300 may be a wide area network such as a LAN (Local Area Network), a WAN (Wide Area Network), or the Internet.

The management server 100 is a computer that manages medical information. For example, the management server 100 is installed in a hospital, a data center, or the like. The terminal devices 200, 200a, 200b are computers used by medical professionals such as doctors and laboratory technicians. For example, the terminal devices 200, 200a, 200b are installed in a hospital. In the following description, medical personnel who can use the terminal devices 200, 200a, 200b are referred to as "users" and are distinguished from "patients". The user can use the service provided by the management server 100 by logging in to the management server 100 through any of the terminal devices 200, 200a, and 200b, for example. The number of terminal devices is not limited to three as shown in FIG.

The management server 100 provides the user with an electronic medical record service that manages the patient's medical record and a service that manages a so-called "ToDo list". In the electronic medical record service, the user can browse the patient's medical record and register information in the medical record. The ToDo list management service is implemented as an additional function of the electronic medical record service, for example.

In this ToDo list management service, ToDo information including information indicating the work to be performed by the user is registered in the management server 100. Here, the user can register not only the ToDo information indicating the work to be performed by the user himself but also the ToDo information indicating the work to be performed by another user in the management server 100. The registered ToDo information includes a destination indicating the user to be notified (that is, the user who performs the work). At the time of registration of ToDo information, the user can set the user himself / herself, another user, or both as a destination. Then, the user can confirm the content of the work to be performed by displaying the ToDo information addressed to him / her in a list and selecting the ToDo information from the list.

Furthermore, the electronic medical record service and the ToDo list management service are linked to each other. For example, the notification date and time is specified for the ToDo information, and when the notification date and time comes while the user is browsing the screen of the electronic medical record service, a notification image prompting the user to browse the ToDo information is displayed on the screen. .. The user can browse the ToDo information by operating on the notification image. The user can also display the ToDo information creation screen and register the ToDo information by operating the screen on which the electronic medical record is displayed.

Next, the hardware of the management server 100 will be described.
FIG. 3 is a diagram showing a hardware example of the management server. The management server 100 includes a processor 101, a RAM 102, an HDD 103, an image signal processing unit 104, an input signal processing unit 105, a reading device 106, and a communication interface 107. Each unit is connected to the bus of the management server 100.

The processor 101 controls the entire management server 100. The processor 101 may be a multiprocessor including a plurality of processing elements. The processor 101 is, for example, a CPU, DSP, ASIC, FPGA, or the like. Further, the processor 101 may be a combination of two or more elements such as a CPU, a DSP, an ASIC, and an FPGA.

The RAM 102 is the main storage device of the management server 100. The RAM 102 temporarily stores at least a part of an OS (Operating System) program or an application program to be executed by the processor 101. Further, the RAM 102 stores various data used for processing by the processor 101.

HDD 103 is an auxiliary storage device of the management server 100. The HDD 103 magnetically writes and reads data from the built-in magnetic disk. The OS program, application program, and various data are stored in the HDD 103. The management server 100 may include other types of auxiliary storage devices such as a flash memory and an SSD (Solid State Drive), or may include a plurality of auxiliary storage devices.

The image signal processing unit 104 outputs an image to the display 11 connected to the management server 100 in accordance with an instruction from the processor 101. As the display 11, various displays such as a CRT (Cathode Ray Tube) display, a liquid crystal display (LCD: Liquid Crystal Display), and an organic EL (Electro-Luminescence) display can be used.

The input signal processing unit 105 acquires an input signal from the input device 12 connected to the management server 100 and outputs the input signal to the processor 101. As the input device 12, various input devices such as a pointing device such as a mouse and a touch panel and a keyboard can be used. A plurality of types of input devices may be connected to the management server 100.

The reading device 106 is a device that reads programs and data recorded on the recording medium 13. As the recording medium 13, for example, a magnetic disk such as a flexible disk (FD) or HDD, an optical disk such as a CD (Compact Disc) or a DVD (Digital Versatile Disc), or an optical magnetic disk (MO: Magneto-Optical disk) can be used. Can be used. Further, as the recording medium 13, for example, a non-volatile semiconductor memory such as a flash memory card can be used. The reading device 106 stores, for example, a program or data read from the recording medium 13 in the RAM 102 or the HDD 103 in accordance with an instruction from the processor 101.

The communication interface 107 communicates with the terminal devices 200, 200a, 200b via the network 300.
The terminal devices 200, 200a, 200b can also be realized by the same hardware as the management server 100.

Next, the functions of the management server 100 will be described.
FIG. 4 is a diagram showing a functional example of the management server. The management server 100 has a storage unit 110, an electronic medical record processing unit 120, and a ToDo information processing unit 130.

The storage unit 110 is implemented as, for example, a storage area secured in the RAM 102 or the HDD 103. The storage unit 110 stores a user table, a ToDo information table, a ToDo status table, a patient table, a medical record display table, and a template table.

The user table holds information about the user. The ToDo information table holds the registered ToDo information. The ToDo status table manages the status of each registered ToDo information. The patient table holds information about the patient. The medical record display table holds information indicating whether or not the patient's medical record is displayed. The stationery table holds stationery information that can be used when creating ToDo information.

The electronic medical record processing unit 120 and the ToDo information processing unit 130 are implemented as, for example, modules of a program executed by the processor 101. The electronic medical record processing unit 120 provides the user with an electronic medical record viewing service. The ToDo information processing unit 130 accepts registration of ToDo information and provides the user with a service for allowing the user to view the registered ToDo information.

The electronic medical record processing unit 120 and the ToDo information processing unit 130 provide a GUI (Graphical User Interface) to the terminal devices 200, 200a, 200b. Specifically, the electronic medical record processing unit 120 and the ToDo information processing unit 130 create an HTML (HyperText Markup Language) file for displaying a GUI screen. The electronic medical record processing unit 120 and the ToDo information processing unit 130 transmit the created HTML file to the terminal devices 200, 200a, 200b, and cause the Web browsers of the terminal devices 200, 200a, 200b to display the GUI screen based on the HTML file. The electronic medical record processing unit 120 and the ToDo information processing unit 130 receive a processing request through the GUI screen and execute the requested processing.

Next, the information stored in the storage unit 110 will be described.
FIG. 5 is a diagram showing an example of a user table. The user table 111 is stored in the storage unit 110. The user table 111 includes items such as a user ID, a user name, a job type, and an instructor.

The item of the user ID indicates the identification information of the user. The user name item indicates the user's name. The job type item indicates the job type of the user. The instructor item indicates the user ID of the instructor who instructes the user.

FIG. 6 is a diagram showing an example of a ToDo information table. The ToDo information table 112 is stored in the storage unit 110. The ToDo information table 112 holds the registered contents of all the registered ToDo information. One record in the ToDo information table 112 corresponds to one ToDo information. Each record includes items such as ToDo ID, address, title, content, notification date and time, deadline date, notifier ID, comment, patient ID, and discharge summary flag.

The ToDo ID item indicates identification information of ToDo information. The destination item indicates the user ID of the user who is the destination of the ToDo information, that is, the user who should perform the work described in the ToDo information. The title item indicates the title of the ToDo information. The content item indicates the content of the work to be performed. The information of the content item is described, for example, in text.

The notification date / time item indicates the date and time when the ToDo information is notified to the destination user. The deadline item indicates the date and time of the deadline for the user to perform the work described in the ToDo information. The item of the notifier ID indicates the user ID of the notifier of ToDo information, that is, the registrant of ToDo information.

The comment indicates the content of the comment described in the ToDo information. In the ToDo information, a text comment can be described by the user who created the information or the user who browsed the information, and the content of the comment described in this way is recorded in the comment item. The patient ID item indicates a patient ID that identifies a particular patient when the ToDo information indicates work related to that particular patient. Patient-related work includes, for example, medical practice for the patient, work of preparing documents about the patient, and the like. The discharge summary flag item indicates a flag indicating whether or not the work described in the ToDo information is a request for creating a discharge summary. The discharge summary is a document created at the time of discharge of an inpatient, and describes, for example, the course of medical conditions and treatment actions during hospitalization.

FIG. 7 is a diagram showing an example of a ToDo state table. The ToDo state table 113 is stored in the storage unit 110. The ToDo state table 113 has a record for each ToDo information registered in the ToDo information table 112, and holds information indicating various states related to ToDo. Each record includes items of ToDo ID, notification status, browsing status, protection status, and completion status.

The ToDo ID item indicates identification information of ToDo information. The item of the notification state indicates whether or not the ToDo information has been notified to the destination user. The item in the browsing state indicates whether or not the content of the ToDo information has been browsed by the destination user. If it has not been viewed, it is set as "unread", and if it has been viewed, it is set as "read".

The protected state item indicates whether or not the ToDo information is protected from being deleted. The ToDo information is automatically deleted after a certain period of time when it is set by the user's operation that the work is completed. However, if the ToDo information is protected, the ToDo information will not be automatically deleted. The completed item indicates whether or not the user has completed the work.

FIG. 8 is a diagram showing an example of a patient table. The patient table 114 is stored in the storage unit 110. The patient table 114 includes items such as patient ID, patient name, and medical record contents. The patient ID item indicates patient identification information. The patient name item indicates the patient's name. The item of the medical record contents shows the information of the medical record. The medical record content "BB1" shown in FIG. 8 is a simple representation of the medical record content, and the actual medical record describes, for example, the age, disease name, medical condition, etc. of the patient with the patient name "PN1". Will be done.

FIG. 9 is a diagram showing an example of a medical record display table. The medical record display table 115 is stored in the storage unit 110. The medical record display table 115 includes items of patient ID and user ID. In the medical record display table 115, when a certain user is browsing the medical record of a certain patient, the patient ID of the patient and the user ID of the browsing user are registered in association with each other. The patient ID item indicates patient identification information corresponding to the chart being viewed. The user ID indicates the identification information of the user who is browsing the medical record.

FIG. 10 is a diagram showing an example of a template table. The template table 116 is stored in the storage unit 110. The stationery table 116 includes items such as a name and a stationery content. The name item indicates the name of the template. The item of the stationery contents indicates the contents of the stationery. The template contents "CC1" and "CC2" shown in FIG. 10 are vague expressions of the contents of the template, and the actual template is, for example, a sentence of a specific format.

Next, a specific example of the GUI displayed on the displays of the terminal devices 200, 200a, 200b will be shown. First, an example of the GUI displayed by the processing of the ToDo information processing unit 130 will be shown.

FIG. 11 is a diagram showing an example of a ToDo creation screen. The ToDo creation screen 400 is a GUI for the user to register ToDo information in the management server 100.
The ToDo creation screen 400 includes a destination, a notification date and time, a template, a deadline date, a title, contents, and a patient input field. The patient input field includes a check box 401, a patient ID input field 402, and a patient name input field 403.

The user inputs the user name of the user who is the destination of the ToDo information in the destination input field. You can enter the user names of multiple users in the destination input field. In addition, the user name of the registrant can be entered, or the user name of another user can be entered. Further, the user sets the date and time for notifying the ToDo information to the destination user in the notification date and time input field, and sets the deadline date and time for the destination user to view the ToDo information in the deadline date input field. It is not mandatory to enter the deadline in the entry field. Further, the user inputs the title of the ToDo information in the title input field, and inputs the content of the work to be performed by the destination user in the content input field.

Further, the ToDo creation screen 400 includes a confirmation button 404. The user instructs the management server 100 to register the ToDo information by performing an operation of pressing the confirmation button 404 (for example, a click operation). Then, the ToDo information processing unit 130 registers a new record in the ToDo information table 112, and registers the content set in the ToDo creation screen 400 for the record. Further, the ToDo information processing unit 130 also registers a new record corresponding to the record registered in the ToDo information table 112 in the ToDo status table 113. At this time, in the created record, "not notified" is set for the item in the notification state, "unread" is set for the item in the browsing state, and "none" is set for the item in the protected state to indicate that it is not protected. , "Incomplete" is set in the completed item. When the ToDo information is registered, the ToDo creation list screen for displaying the ToDo information registered by the user is displayed.

In the ToDo creation screen 400, a template of ToDo information is selected in the template input field. In the patient input field, information about the patient related to ToDo information is input. In the example of FIG. 11, both the template input field and the patient input field are in a state where input is impossible. As will be described later, the patient input field can be input only when the ToDo creation screen 400 is displayed while the medical record screen is displayed. In addition, the template input field is in a state where the template can be selected only when the patient information is input in the patient input field.

FIG. 12 is a diagram showing an example of a ToDo creation list screen. On the ToDo creation list screen 410, when a user browses, the ToDo information registered in the management server 100 by that user is displayed in a list. The ToDo information processing unit 130 generates information for displaying the ToDo creation list screen 410 by extracting information corresponding to the user to browse from the ToDo information table 112 and the ToDo status table 113. The ToDo creation list screen 410 has display fields for notification status, notification date / time, title, deadline date, completion, patient ID, patient name, medical record, and comment as display fields indicating ToDo information.

In the notification date / time, title, deadline date, and patient ID display fields, the information registered in the notification date / time, title, deadline date, and patient ID items of the ToDo information table 112 is displayed. In the comment display column, the number of comments recorded in the comment item of the ToDo information table 112 is displayed. In the notification status and completion display fields, the information registered in the notification status and completion status items of the ToDo status table 113 is displayed.

In the patient name display field, the name of the patient corresponding to the patient ID is displayed. When the patient ID and patient name are registered, it indicates that the ToDo information is related to the registered patient. In the medical record display field, a display button for instructing the display of the patient's medical record is displayed. This display button is displayed only if the ToDo information is relevant to the patient. In the example of FIG. 12, display buttons 413a and 413b are displayed in the display columns of the medical records on the second and fourth lines from the top in which the patient ID and the patient name are registered, respectively.

Further, the ToDo creation list screen 410 includes a new creation button 411 and a ToDo list button 412. The user can display the ToDo creation screen for registering new ToDo information by pressing the new creation button 411. In addition, the user can display the ToDo list screen that displays a list of ToDo information destined for the user by pressing the ToDo list button 412.

FIG. 13 is a diagram showing an example of a ToDo list screen. On the ToDo list screen 420, ToDo information destined for one user is displayed in a list. That is, the ToDo list screen 420 is a so-called "ToDo list". The ToDo information processing unit 130 generates information for displaying the ToDo list screen 420 by extracting information corresponding to the user to browse from the ToDo information table 112 and the ToDo status table 113.

The ToDo list screen 420 has read, protected, title, deadline, completion, notification date and time, notifier, patient ID, patient name, medical record, and comment display fields as display fields for displaying ToDo information. Further, the ToDo list screen 420 includes a new creation button 421, a ToDo creation list button 422, and a state change button 423.

In the title, deadline date, notification date / time, and patient ID display fields, the information registered in the title, deadline date, notification date / time, and patient ID items of the ToDo information table 112 is displayed. In the notifier display field, the name of the notifier indicated by the ID registered in the notifier ID item of the ToDo information table 112 is displayed.

In the patient name display field, the name of the patient corresponding to the patient ID is displayed. When the patient ID and patient name are registered, it indicates that the ToDo information is related to the registered patient. In the medical record display field, a display button for instructing the display of the patient's medical record is displayed. In the example of FIG. 13, display buttons 424a and 424b are displayed in the display columns of the charts on the second and fourth rows from the top, respectively.

In the comment display column, the number of comments recorded in the comment item of the ToDo information table 112 is displayed. In each of the read, protected, and completed display columns, the information registered in the browsing status, protected status, and completed status items of the ToDo status table 113 is displayed.

Here, for example, the user can display the menu screen 426 by performing a right-click operation with the mouse cursor 425 on the line where the ToDo information is displayed. At least "detailed display" is displayed on the menu screen 426, and the user can display the ToDo detailed screen for viewing the detailed contents of the ToDo information by performing a click operation on the "detailed display". The user may also display the ToDo detail screen in the same manner when he / she wants to describe a comment in the ToDo information.

Further, the user can display the ToDo creation screen for registering new ToDo information by performing the operation of pressing the new creation button 421. In addition, the user can display the ToDo creation list screen that displays a list of ToDo information registered by the user by pressing the ToDo creation list button 422.

Further, the user can update any of the read, protected, and completed information by pressing the state change button 423 while selecting the line in which the ToDo information is displayed. For example, when the status change button 423 is pressed, a menu screen (not shown) is displayed in which either "read", "protection", or "completed" can be selected.

For example, when the content of ToDo information has been confirmed, the user performs an operation of selecting "read" on the menu screen. As a result, the read display field changes from "unread" to "read", and the information of the item in the browsing state in the ToDo state table 113 is also updated from "unread" to "read".

Further, for example, when the user has already performed the work indicated by the ToDo information, the user performs an operation of selecting "Done" on the menu screen. As a result, "completed" is displayed in the completion display column, and the information of the completed state item in the ToDo status table 113 is updated from "incomplete" to "completed".

Further, the ToDo information registered in the management server 100 is automatically deleted after a predetermined time has elapsed when the completion state is updated to "completed". When the user wants to prevent the ToDo information from being automatically deleted in this way, the user performs an operation of selecting "protection" on the menu screen. As a result, "protection" is displayed in the protection display column, and the information of the protection status item in the ToDo status table 113 is updated from "none" to "protection".

FIG. 14 is a diagram showing an example of a ToDo detailed screen. The ToDo detail screen 430 is a screen for the user to browse the detailed contents of the ToDo information.
The ToDo detail screen 430 includes display fields for the title, content, notifier, and comment. In the title, content, notifier, and comment display fields, the information registered in the title, content, notifier ID, and comment items of the ToDo information table 112 is displayed. Further, the ToDo detail screen 430 includes a new comment input field 431. The user can newly write and register a comment in the new comment input field 431.

Further, the ToDo detail screen 430 includes a confirmation button 432 and an end button 433 for closing the screen. When the user writes a comment in the new comment input field 431, the user performs an operation of pressing the confirmation button 432. In this case, the information added to the new comment input field 431 is registered in the comment item of the ToDo information table 112. As for the content of the comment, the content written in the input field 431 of the new comment is registered as a set of information for one case. Comments can only be added, and comments written in the past cannot be deleted. On the other hand, when the operation of pressing the end button 433 is performed, the display of the ToDo detail screen 430 is terminated without updating the ToDo information table 112.

As described with reference to FIG. 13, the ToDo detail screen 430 is displayed by selecting ToDo information from the ToDo list screen 420. In this case, when the confirmation button 432 or the end button 433 of the ToDo detail screen 430 is pressed, the display is switched to the original ToDo list screen 420. In addition to this, the ToDo detail screen 430 may be displayed by selecting ToDo information from the ToDo creation list screen 410. In this case, when the confirmation button 432 or the end button 433 of the ToDo detail screen 430 is pressed, the display is switched to the original ToDo creation list screen 410.

Next, an example of the GUI displayed by the processing of the electronic medical record processing unit 120 is shown. The GUI of the electronic medical record viewing service is roughly divided into a patient list screen and a medical record screen. Patients are listed on the patient list screen. Then, when the user performs an operation of selecting a patient from the patient list screen, a medical record screen showing the contents of the medical record for the patient is displayed.

FIG. 15 is a diagram showing an example of a medical record screen. The medical record screen 440 is a GUI displayed based on the corresponding patient information registered in the patient table 114. As described above, the medical record screen 440 is displayed by selecting a patient from the patient list screen. The medical record screen 440 is also displayed when the operation of pressing the display button displayed in the medical record display field of the ToDo creation list screen 410 or the ToDo list screen 420 is performed. For example, when the operation of pressing the display button 424a in FIG. 13 is performed, a medical record screen 440 showing the contents of the medical record of the patient corresponding to the patient ID “P1” and the patient name “PN1” is displayed.

When the medical record screen 440 is displayed, the electronic medical record processing unit 120 registers a record including the patient ID of the patient corresponding to the medical record and the user ID of the user who is browsing in the medical record display table 115. Then, when the medical record screen 440 is closed, the electronic medical record processing unit 120 deletes the registered record from the medical record display table 115.

The medical record screen 440 also includes a ToDo creation button 441 and a discharge summary button 442. The user can display the ToDo creation screen by pressing the ToDo creation button 441. In addition, the user can display the discharge summary creation screen described later by performing an operation of pressing the discharge summary button 442.

Further, the medical record screen 440 has a user information area 443. In the user information area 443, for example, the user name of the user who is browsing is displayed. Further, when the notification date and time of the ToDo information addressed to the user who is browsing comes, the notification image 444 for notifying the user of the ToDo information is displayed in the user information area 443. When the notification image 444 is displayed, the corresponding ToDo information is in the "notified" state.

In addition, the user can confirm the corresponding ToDo information by performing an operation of selecting the displayed notification image 444 (for example, a click operation). For example, when the notification image 444 is selected, the ToDo detail screen 430 for displaying the contents of the corresponding ToDo information is displayed. Further, for example, when the selection operation of the notification image 444 is performed, if there are a plurality of ToDo information having the notification date and time, a selection screen for selecting the ToDo information is displayed. In this case, by performing the selection operation of any ToDo information on the selection screen, the ToDo detail screen 430 for displaying the contents of the selected ToDo information is displayed.

The user information area 443 is displayed not only on the medical record screen 440 but also on the patient list screen. Then, the notification image 444 is displayed in the user information area 443 on the screen even when the patient list screen is displayed. As a result, the user can recognize that the ToDo information has been generated at the notification date and time regardless of whether the medical record screen 440 or the patient list screen is being viewed.

Further, the display of the notification image 444 is an example of a notification method of ToDo information, and other notification methods may be used. For example, the ToDo information processing unit 130 may send an e-mail to the user indicating that the ToDo information has been generated at the notification date and time. Further, the notification image 444 may be displayed on the ToDo creation screen 400 or the ToDo list screen 420. Further, on the ToDo creation screen 400 and the ToDo list screen 420, the line of ToDo information may be highlighted at the notification date and time due to a change in color or the like.

By the way, on the ToDo creation screen 400 shown in FIG. 11, the patient input field cannot be input. As described above, the patient input field can be input only when the ToDo creation screen 400 is displayed while the medical record screen 440 is displayed.

FIG. 16 is a diagram showing an example of a ToDo creation screen in which a patient input field can be input. In FIG. 16, the ToDo creation screen 400a is displayed with the medical record screen 440 displayed. For example, when the operation of pressing the ToDo creation button 441 of the chart screen 440 shown in FIG. 15 is performed, the ToDo creation screen 400a is displayed as shown in FIG.

When the ToDo creation screen 400a is displayed together with the medical record screen 440 in this way, the check box 401a, the patient ID input field 402a, and the patient name input field 403a included in the patient input field of the ToDo creation screen 400a are input. It will be possible. When the check box 401a is checked, the patient ID and patient name corresponding to the displayed chart screen 440 are automatically entered in the patient ID input field 402a and the patient name input field 403a, respectively. Set. By setting the patient ID and the patient name, ToDo information related to the patient is created.

In this way, the user cannot create ToDo information about the patient unless the patient's chart screen 440 is displayed. This reduces the possibility of erroneously specifying the patient when creating ToDo information about the patient.

For example, the user cannot set patient information on the ToDo creation screen unless the patient's chart screen 440 is displayed (the state of the ToDo creation screen 400 in FIG. 11). By this mechanism, the user can set the patient ID and the patient name while visually recognizing the medical record, so that the possibility of erroneously setting the patient ID and the patient name can be reduced. Further, by automatically setting the patient ID and the patient name corresponding to the displayed medical record on the ToDo creation screen 400a, the possibility of erroneous setting can be further reduced. Further, by automatically setting only the patient ID and the patient name corresponding to the displayed medical record on the ToDo creation screen 400a, the possibility of erroneous setting can be further reduced.

Further, on the ToDo creation screen 400a of FIG. 16, the template input field 404a is also in a state in which input is possible. The stationery input field 404a is ready for input when the check box 401a is checked. In this state, when the selection button 405a in the template input field 404a is selected, the names of the selectable templates are displayed in a list. Then, when one of the names displayed in the list is selected, the information preset in the selected template is set in the predetermined input field of the ToDo creation screen 400a.

FIG. 17 is a diagram showing an example of a ToDo creation screen in which information based on a template is set. In the ToDo creation screen 400b shown in FIG. 17, a template called "discharge summary creation request" for requesting the creation of a discharge summary was selected in the input field 404b of the template of the ToDo creation screen 400a shown in FIG. Show the case. At this time, for example, the text preset in the selected template is automatically set in the title input field 405b and the content input field 406b. In this way, the information is automatically set in the predetermined input field on the ToDo creation screen 400b by the template selection operation, so that the burden of the user's setting operation can be reduced.

Next, the display process executed between the management server 100 and the terminal device will be described with reference to a flowchart. In the following description, as an example, it is assumed that the user is using the terminal device 200 among the terminal devices 200, 200a, 200b.

FIG. 18 is a flowchart showing an example of display processing of the chart screen. Hereinafter, the process shown in FIG. 18 will be described along with the step numbers.
(S11) The electronic medical record processing unit 120 receives a display request for the medical record screen 440. For example, the electronic medical record processing unit 120 receives a display request from the terminal device 200 when a patient selection operation is performed from the patient list screen displayed on the terminal device 200. Further, for example, when an operation of pressing the open button displayed in the medical record display field of the ToDo creation list screen 410 or the ToDo list screen 420 is performed, the electronic medical record processing unit 120 requests the display from the terminal device 200 to ToDo. It is received via the information processing unit 130. The display request includes the patient ID.

(S12) The electronic medical record processing unit 120 searches the patient table 114 and identifies a record corresponding to the patient ID included in the display request.
(S13) The electronic medical record processing unit 120 creates an HTML file for displaying the medical record screen 440 on the terminal device 200 based on the specified record. The electronic medical record processing unit 120 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the medical record screen 440.

(S14) A new record is created in the electronic medical record processing unit 120 and the medical record display table 115, and the patient ID and the user ID corresponding to the user who is browsing are registered in the record. Although not shown, the electronic medical record processing unit 120 deletes the record created in the medical record display table 115 in step S14 when the display of the medical record screen 440 is completed.

FIG. 19 is a flowchart (No. 1) showing an example of display processing of the ToDo creation screen. FIG. 20 is a flowchart (No. 2) showing an example of display processing of the ToDo creation screen. Hereinafter, the processes shown in FIGS. 19 and 20 will be described along with the step numbers.

(S21) The ToDo information processing unit 130 receives a display request for the ToDo creation screen. For example, when the new creation button 411 of the ToDo creation list screen 410 displayed on the terminal device 200 or the new creation button 421 of the ToDo list screen 420 is pressed, the ToDo information processing unit 130 displays from the terminal device 200. Receive the request. Further, when the ToDo creation button 441 of the medical record screen 440 displayed on the terminal device 200 is pressed, the ToDo information processing unit 130 receives the display request from the terminal device 200 via the electronic medical record processing unit 120. ..

(S22) The ToDo information processing unit 130 refers to the medical record display table 115 and determines whether or not the medical record screen 440 is displayed for the user who is browsing. When there is a record in which the user ID of the user is registered in the medical record display table 115, it is determined that the medical record screen 440 is displayed. When the chart screen 440 is displayed, the ToDo information processing unit 130 advances the process to step S31 in FIG. When the medical record screen 440 is not displayed, the ToDo information processing unit 130 advances the process to step S23.

(S23) The ToDo information processing unit 130 displays an HTML file for displaying the ToDo creation screen 400 in a state in which the patient information input field is invalidated (that is, a state in which input is not possible) on the terminal device 200. create. The ToDo information processing unit 130 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the ToDo creation screen 400.

(S24) When the confirmation button 404 of the ToDo creation screen 400 is pressed, the terminal device 200 transmits a registration instruction together with the information set on the ToDo creation screen 400. The ToDo information processing unit 130 receives the registration instruction together with the setting information.

(S25) The ToDo information processing unit 130 creates a new record in the ToDo information table 112, and sets the received setting information in the record. Further, the ToDo information processing unit 130 also creates a new record in the ToDo status table 113, and sets initial values for each item of the created record. That is, "not notified" is set for the notification status item, "unread" is set for the browsing status item, "none" is set for the protected status item, and "incomplete" is set for the completed status item. Will be done. By the process of step S25 described above, ToDo information is registered in the management server 100.

(S31) The ToDo information processing unit 130 creates an HTML file for displaying the ToDo creation screen 400a in a state in which the patient information input field is enabled (that is, a state in which input is possible) on the terminal device 200. To do. The ToDo information processing unit 130 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the ToDo creation screen 400a.

(S32) When the check box 401a of the ToDo creation screen 400a is set, the terminal device 200 transmits a patient information display request. If the ToDo information processing unit 130 receives the patient information display request before receiving the registration instruction in step S37, the process proceeds to step S33. On the other hand, when the request for displaying the patient information is not received, the ToDo information processing unit 130 proceeds to the process in step S37.

(S33) The ToDo information processing unit 130 refers to the patient table 114 and searches for a record corresponding to the patient ID registered in the record specified from the medical record display table 115 in step S22. The ToDo information processing unit 130 identifies the patient name corresponding to the patient ID from the searched record.

(S34) The ToDo information processing unit 130 transmits the patient ID and the patient name, the display instruction thereof, and the instruction for activating the input field 404a of the template to the terminal device 200. As a result, the transmitted patient ID and patient name are set in the patient ID input field 402a and the patient name input field 403a of the ToDo creation screen 400a, respectively. Further, the input field 404a of the template changes to a state in which input is possible.

(S35) When the operation of selecting a template is performed in the template input field 404a, the terminal device 200 transmits a template application instruction together with information indicating the name of the selected template. When the ToDo information processing unit 130 receives the template application instruction before receiving the registration instruction in step S37, the process proceeds to step S36. On the other hand, if the template application instruction is not received, the ToDo information processing unit 130 advances the process to step S37.

(S36) The ToDo information processing unit 130 acquires the contents of the selected template from the template table 116. The ToDo information processing unit 130 instructs the terminal device 200 to set the information set in the template in the predetermined input field of the ToDo creation screen 400a based on the contents of the acquired template. As a result, the information set in the template is set in the predetermined input field of the ToDo creation screen 400a.

(S37) When the confirmation button on the ToDo creation screen 400a is pressed, the terminal device 200 transmits the ToDo information registration instruction together with the information set on the ToDo creation screen 400a. The ToDo information processing unit 130 receives the setting information and the registration instruction.

(S38) The ToDo information processing unit 130 creates a new record in the ToDo information table 112, and sets the received setting information in the record. Further, the ToDo information processing unit 130 also creates a new record in the ToDo status table 113, and sets initial values for each item of the created record. As a result, ToDo information related to the patient is registered in the management server 100.

Further, when the template "Request for creating discharge summary" for requesting the creation of discharge summary is selected in step S35, the ToDo information processing unit 130 displays the discharge summary flag of the record created in the ToDo information table 112. Is set to "1". From this, it is possible to identify that this ToDo information requests the preparation of a discharge summary.

According to the above processes of FIGS. 19 and 20, the user can set the patient information on the ToDo creation screen 400a only when the patient's chart screen 440 is displayed. This reduces the possibility of erroneously specifying the patient when creating ToDo information about the patient.

In steps S31 to S34 described above, the ToDo information processing unit 130 first displays the ToDo creation screen 400a in which the patient information input field is enabled. Then, when the ToDo information processing unit 130 subsequently receives the patient information display request, the patient ID and the patient name are set in the patient ID input field 402a and the patient name input field 403a, respectively. However, as another example, the ToDo information processing unit 130 displays the ToDo creation screen 400a in which the patient ID and the patient name are set in the patient ID input field 402a and the patient name input field 403a, respectively, at the time of step S31. It may be displayed. As a result, the work of inputting the patient ID and the patient name by the user can be further made more efficient.

FIG. 21 is a flowchart showing an example of notification processing of ToDo information. The ToDo information processing unit 130 executes the following processing at regular intervals for each user logged in to the electronic medical record viewing service. Hereinafter, the process shown in FIG. 21 will be described along with the step numbers.

(S41) The ToDo information processing unit 130 determines whether or not there is ToDo information whose notification date and time has come in the ToDo information destined for the user to be processed. Specifically, the ToDo information processing unit 130 identifies records destined for the user to be processed from the ToDo information table 112, and further identifies records whose notification date and time match the current time. .. When the corresponding record is identified, the ToDo information processing unit 130 advances the process to step S42. If there is no corresponding record, the ToDo information processing unit 130 ends the process.

(S42) The ToDo information processing unit 130 requests the electronic medical record processing unit 120 to display the notification image of the ToDo information on the user to be processed. The electronic medical record processing unit 120 causes the notification image to be displayed in the patient list screen of the corresponding user or the user information area of the medical record screen (for example, the user information area 443 in FIG. 15).

(S43) The ToDo information processing unit 130 identifies a record corresponding to the ToDo information specified in step S41 from the ToDo status table 113, and updates the notification status item of the specified record to "notified".

(S44) When the user performs the notification image selection operation, the electronic medical record processing unit 120 requests the ToDo information processing unit 130 to display the ToDo information. When the ToDo information processing unit 130 receives the ToDo information display request, the process proceeds to step S45. On the other hand, for example, assuming that the notification image is displayed for a certain period of time, the ToDo information processing unit 130 ends the process of FIG. 21 if the display request is not received within the time when the notification image is displayed.

(S45) The ToDo information processing unit 130 creates an HTML file for displaying the ToDo detail screen 430 that displays the contents of the ToDo information specified in step S41. The ToDo information processing unit 130 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the ToDo detail screen 430.

For example, when a plurality of ToDo information is specified in step S41, the ToDo information processing unit 130 first displays a selection screen for selecting the specified ToDo information. Then, the ToDo information processing unit 130 displays the ToDo detail screen 430 showing the ToDo information selected through the selection screen. As another example, the ToDo information processing unit 130 may only display a screen for displaying an outline (for example, a title) of ToDo information at the time of step S45.

FIG. 22 is a flowchart showing an example of display processing of the ToDo detail screen. For example, in FIG. 22, the process is started when the user name “US2” selects “detailed display” from the menu screen 426. Hereinafter, the process shown in FIG. 22 will be described along with the step numbers.

(S51) The ToDo information processing unit 130 receives a display request for the ToDo detail screen 430 from the terminal device 200a. For example, the user can right-click on the ToDo information area on the ToDo creation list screen 410 or ToDo list screen 420 displayed on the terminal device 200 to perform a menu screen (for example, the menu screen 426 in FIG. 13). Is displayed. When the user performs an operation of selecting "detailed display" on the menu screen, the terminal device 200 transmits a display request for the ToDo detailed screen 430 together with the ToDo ID of the ToDo information, and the ToDo information processing unit 130 receives this. ..

(S52) The ToDo information processing unit 130 identifies a record corresponding to the received ToDo ID from the ToDo information table 112 and the ToDo status table 113. The ToDo information processing unit 130 creates an HTML file for displaying the ToDo detail screen 430 on the terminal device 200 based on the information acquired from the specified record. The ToDo information processing unit 130 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the ToDo detail screen 430.

(S53) When the pressing operation on the confirmation button 432 of the ToDo detail screen 430 is performed, the terminal device 200 transmits a new comment registration instruction together with the comment written in the new comment input field 431. On the other hand, when the end button 433 of the ToDo detail screen 430 is pressed, the terminal device 200 transmits a display end instruction of the ToDo detail screen 430. When the ToDo information processing unit 130 receives the instruction to register a new comment, the process proceeds to step S54. On the other hand, when the ToDo information processing unit 130 receives the display end instruction, the process proceeds to step S55.

(S54) The ToDo information processing unit 130 additionally registers the received comment in the comment item in the corresponding record of the ToDo information table 112.
(S55) The ToDo information processing unit 130 ends the display of the ToDo detail screen 430. For example, the ToDo information processing unit 130 displays a screen displayed immediately before the ToDo detail screen 430. Further, when the item of the browsing state is set to "unread" in the corresponding record of the ToDo state table 113, the ToDo information processing unit 130 updates this to "read".

Next, a case where the content of the ToDo information is modified will be described.
FIG. 23 is a diagram showing an example in which the content of the ToDo information is modified from the ToDo creation list screen. For example, the user displays the menu screen 412a by performing a right-click operation with the mouse cursor 411a placed on one ToDo information area on the ToDo creation list screen 410a. The menu screen 412a includes "detailed display", "correction", and the like, and when the user performs a "correction" selection operation, the ToDo creation screen 400c is displayed.

However, the ToDo information related to the patient can be modified only when the patient's chart screen is displayed. In the example of FIG. 23, the ToDo information to which the mouse cursor 411a is aligned is the ToDo information related to the patient with the patient ID “P1”. In this case, it is assumed that the menu screen 412a is displayed and "correction" is selected. At this time, when the medical record screen 440 for the patient with the patient ID “P1” is displayed as shown in FIG. 23, the ToDo creation screen 400c is displayed, and the ToDo information can be corrected. On the other hand, when the medical record screen 440 for the patient with the patient ID "P1" is not displayed, a warning message 450 for notifying that the ToDo information cannot be corrected is displayed. The warning message 450 may contain, for example, information for displaying the patient's chart screen 440 and then instructing the patient to correct the ToDo information.

In this way, the user can modify the ToDo information related to the patient only when the patient's chart screen 440 is displayed. This prevents the user from modifying the ToDo information associated with the patient without checking the contents of the patient's chart. Therefore, it is possible to reduce the possibility that the user erroneously corrects the ToDo information.

FIG. 24 is a flowchart showing an example of correction processing of ToDo information. Hereinafter, the process shown in FIG. 24 will be described along with the step numbers.
(S61) The ToDo information processing unit 130 receives a request for correction of ToDo information from the terminal device 200 together with the ToDo ID of the ToDo information.

(S62) The ToDo information processing unit 130 refers to the ToDo information table 112 and determines whether or not the patient ID is set in the record corresponding to the received ToDo ID. Here, when the patient ID is not set, that is, when the ToDo information is not related to the patient, the ToDo information processing unit 130 proceeds to the process in step S64.

On the other hand, when the patient ID is set, the ToDo information processing unit 130 refers to the medical record display table 115, and records including the patient ID set in the ToDo information table 112 and the user ID of the user who is browsing. Is registered or not. When the corresponding record is registered, the patient's chart screen 440 is displayed on the terminal device 200 viewed by the user. In this case, the ToDo information processing unit 130 advances the process to step S64. On the other hand, if the corresponding record is not registered, the ToDo information processing unit 130 advances the process to step S63.

(S63) The ToDo information processing unit 130 creates an HTML file for displaying the warning message 450 on the terminal device 200. The ToDo information processing unit 130 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the warning message 450. Then, the ToDo information processing unit 130 ends the process. This makes it impossible to correct the ToDo information related to the patient without displaying the patient's chart.

(S64) The ToDo information processing unit 130 refers to the ToDo information table 112 and identifies a record corresponding to the received ToDo ID. The ToDo information processing unit 130 creates an HTML file for displaying the ToDo creation screen 400c in which the information included in the specified record is set on the terminal device 200. The ToDo information processing unit 130 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the ToDo creation screen 400c.

(S65) The ToDo information processing unit 130 receives a correction confirmation instruction from the terminal device 200 in response to a pressing operation on the confirmation button on the ToDo creation screen 400c. At this time, the ToDo information processing unit 130 also receives the information set on the ToDo creation screen 400c.

(S66) The ToDo information processing unit 130 corrects the record specified in step S64 based on the received information. The comment registered in the ToDo information is maintained as it is without being deleted.

(S67) The ToDo information processing unit 130 refers to the ToDo status table 113 and identifies a record corresponding to the ToDo ID received in step S61. The ToDo information processing unit 130 determines whether or not "notified" is set in the notification status item of the specified record. If "notified" is set, the ToDo information processing unit 130 advances the process to step S68. If "not notified" is set, the ToDo information processing unit 130 ends the process.

(S68) The ToDo information processing unit 130 updates the notification date and time to the current time in the record of the ToDo information table 112 specified in step S64. In this case, the ToDo information is immediately notified to the destination user by the notification process shown in FIG. In this way, when the ToDo information that has already been notified to the destination user is modified, the ToDo information is notified to the destination user again. As a result, even if the ToDo information has been notified, the destination user can be surely recognized that the content of the ToDo information has been modified.

Further, the ToDo information processing unit 130 updates the record of the ToDo state table 113 specified in step S67 to "unread" when the browsing state is "read". By this process, the read display field of the modified ToDo information is updated from "read" to "unread" on the ToDo list screen 420 for the destination user. As a result, the destination user can recognize that the modified ToDo information has not been read even if the contents of the ToDo information have been viewed. Therefore, it is possible to reduce the possibility that the destination user forgets to confirm the content of the modified ToDo information.

Next, a case where the ToDo information is deleted will be described.
FIG. 25 is a diagram showing an example in the case of deleting ToDo information. For example, the user displays the menu screen 412b by performing a right-click operation with the mouse cursor 411b placed on one ToDo information area on the ToDo creation list screen 410b. The menu screen 412b includes "delete" in addition to the above-mentioned "correction", and when the user performs a "delete" selection operation, the ToDo information can be deleted.

Here, when the ToDo information is not notified, it is highly possible that the destination user has not confirmed the ToDo information. Therefore, when the ToDo information is not notified, even if the destination user is a user other than the notifier, even if the ToDo information is deleted, there is no particular significant effect. On the other hand, when the ToDo information has been notified, the destination user may confirm the ToDo information and recognize it as a work to be performed. Further, for example, a user who thinks that the work is important may set the protection state of the ToDo information to "protected" so that the ToDo information is not automatically deleted. Therefore, deleting the notified ToDo information may affect the action schedule and psychological state of the destination user.

Therefore, when the ToDo information processing unit 130 is instructed to delete the notified ToDo information, the confirmation screen 460 including a confirmation message for confirming whether or not the deletion is really allowed is displayed without immediately executing the deletion. Display it. The confirmation screen 460 includes a permission button 461 that permits deletion and a disallow button 462 that does not permit deletion. When the user executes the deletion after confirmation, the user presses the permission button 461 to execute the deletion of the ToDo information. On the other hand, the user can cancel the deletion of the ToDo information by pressing the disallow button 462. By such a procedure, it is possible to execute the deletion of the ToDo information after making the user aware of the influence of deleting the notified ToDo information.

Further, the ToDo information processing unit 130 forcibly deletes the ToDo information when the permission button 461 is pressed, even if the destination user protects the ToDo information. According to this process, since the user performing the deletion operation is still trying to delete the ToDo information even if he / she recognizes the influence on the destination user, the intention of the user is prioritized over the destination user and the ToDo information is given. Can be deleted.

FIG. 26 is a flowchart showing an example of the ToDo information deletion process. Hereinafter, the process shown in FIG. 26 will be described along with the step numbers.
(S71) The ToDo information processing unit 130 receives a deletion request from the terminal device 200 together with the ToDo ID.

(S72) The ToDo information processing unit 130 refers to the ToDo status table 113 and determines whether or not the notification status item in the record corresponding to the received ToDo ID has been notified. If notified, the ToDo information processing unit 130 advances the process to step S73. If not notified, the ToDo information processing unit 130 advances the process to step S76.

(S73) The ToDo information processing unit 130 creates an HTML file for displaying the confirmation screen 460 for confirming whether to delete the terminal device 200. The ToDo information processing unit 130 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the confirmation screen 460.

The user presses the permit button 461 or the disallow button 462 on the confirmation screen 460. When the user presses the permission button 461, the terminal device 200 transmits a deletion execution request to the management server 100. Further, when the user presses the disallow button 462, the terminal device 200 transmits an instruction to cancel the deletion request to the management server 100.

(S74) The ToDo information processing unit 130 determines whether or not to execute the deletion of the ToDo information. When the deletion execution request is received, the ToDo information processing unit 130 determines that the deletion is to be executed, and proceeds to the process in step S75. When the cancellation instruction of the deletion request is received, the ToDo information processing unit 130 ends the process without executing the deletion.

(S75) The ToDo information processing unit 130 deletes the ToDo information by deleting the record corresponding to the ToDo ID received in step S71 from the ToDo information table 112 and the ToDo status table 113. At this time, the ToDo information processing unit 130 deletes the ToDo information even if the ToDo status table is registered to protect the ToDo information.

(S76) The ToDo information processing unit 130 refers to the ToDo status table 113, and determines whether or not protection is registered in the protected status item in the record corresponding to the ToDo ID received in step S71. When the protection is registered, the ToDo information processing unit 130 ends the process without executing the deletion. On the other hand, if the protection is not registered, the ToDo information processing unit 130 advances the process to step S77.

(S77) The ToDo information processing unit 130 deletes the ToDo information by deleting the record corresponding to the ToDo ID received in step S71 from the ToDo information table 112 and the ToDo status table 113.

Next, the preparation of the discharge summary will be described.
The discharge summary is a document prepared by a doctor at the time of discharge of an inpatient, and describes, for example, the course of medical conditions and treatment actions during hospitalization. As shown in FIG. 15, the user can display the discharge summary creation screen for creating the discharge summary by pressing the discharge summary button 442 displayed on the patient's chart screen 440.

FIG. 27 is a diagram showing an example of a discharge summary creation screen. The discharge summary creation screen 470 has input fields such as a diagnosis name, a course up to admission, a present condition at admission, a clinical course after admission, and a discharge prescription. The user writes necessary items in the above input field while referring to, for example, the patient's chart screen 440. In addition, the discharge summary creation screen 470 includes a confirmation button 471. When confirming and registering the content written on the discharge summary creation screen 470, the user performs an operation of pressing the confirmation button 471.

By the way, as shown in FIG. 17, the user can register ToDo information for requesting the creation of the discharge summary. The ToDo information is recorded in association with the ToDo information of the discharge summary creation request by using the template of the “discharge summary creation request” at the time of creation. Specifically, in step S38 of FIG. 20, the discharge summary flag of the record registered in the ToDo information table 112 is set to “1”.

Here, when the user presses the confirmation button 471 on the discharge summary creation screen 470 for a certain patient to register the discharge summary, the discharge summary for the same patient is created in the ToDo information addressed to this user. There may be ToDo information to request. Hereinafter, this ToDo information will be referred to as "related ToDo information".

In this case, as shown in FIG. 27, a completion confirmation screen 480 for confirming whether to complete the related ToDo information is displayed. The completion confirmation screen 480 includes a completion instruction button 481 for completing the related ToDo information and an end button 482 for closing the screen without completing the related ToDo information. By performing the operation of pressing the completion instruction button 481, the user can complete the related ToDo information without displaying the ToDo list screen 420 again to instruct the completion. As a result, the operation load of the user is reduced.

Also, when a doctor prepares a discharge summary, the prepared discharge summary may be forwarded to another pre-determined doctor for approval. Therefore, when the ToDo information processing unit 130 completes the related ToDo information by the above procedure, the ToDo information processing unit 130 automatically displays the ToDo creation screen for requesting the approval of the discharge summary.

FIG. 28 is a diagram showing an example of a ToDo creation screen for a discharge summary approval request. For example, when the completion is instructed by pressing the completion instruction button 481 of FIG. 27 for the ToDo information of the discharge summary creation request addressed to the user with the user name “US2”, the ToDo creation screen 400d shown in FIG. 28 is displayed. .. Further, it is assumed that the prepared discharge summary is for a patient with a patient ID "P1" and a patient name "PN1". Further, it is assumed that the user with the user name "US11" is registered as the instructor of the user with the user name "US2" in the user table 111.

In this case, the template for the discharge summary approval request is automatically selected from the template table 116, and the text based on the selected template is set in the title and content input fields of the ToDo creation screen 400d. As in the example of FIG. 28, the patient name and the patient ID may be automatically set in the text of the content input field. Further, in the address field, the user name "US11" corresponding to the instructor of the user with the user name "US2" is automatically set. Further, in the patient input field, as in the example of FIG. 28, a check may be automatically set in the check box, and the patient ID and the patient name may be automatically set.

In this way, when the completion operation of the ToDo information indicating a specific work is performed, the ToDo creation screen 400d for creating the ToDo information indicating another work associated with the work is automatically displayed. Is displayed. As a result, the workload of the user can be reduced. In addition, the user can accurately recognize the work to be executed next and create ToDo information for performing the work. Furthermore, on the displayed ToDo creation screen 400d, a predetermined template is automatically selected, and the destination and patient information are automatically set, so that the workload of the user can be reduced and the work can be performed. Can improve the accuracy of.

FIG. 29 is a flowchart showing an example of a series of processes starting from the preparation of the discharge summary. For example, in FIG. 29, the process starts when the user name “US2” presses the discharge summary button 442 on the medical record screen 440. Hereinafter, the process shown in FIG. 29 will be described along with the step numbers.

(S81) When the discharge summary button 442 displayed on the chart screen 440 displaying the patient's chart is pressed, the electronic medical record processing unit 120 receives a display request for the discharge summary creation screen 470 from the terminal device 200. ..

(S82) The electronic medical record processing unit 120 creates an HTML file for displaying the discharge summary creation screen 470 on the terminal device 200. The electronic medical record processing unit 120 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the discharge summary creation screen 470.

(S83) The user presses the confirmation button 471 after writing the necessary items on the discharge summary creation screen 470. The terminal device 200 transmits a confirmation notification indicating that the contents of the discharge summary have been confirmed to the management server 100 together with the written contents of the discharge summary. When the electronic medical record processing unit 120 receives the confirmation notification, the electronic medical record processing unit 120 stores the contents of the received discharge summary in the storage unit 110.

(S84) The electronic medical record processing unit 120 determines whether or not there is related ToDo information. Specifically, the electronic medical record processing unit 120 refers to the ToDo information table 112 and identifies a record whose discharge summary flag is “1” from the records set as the destination by the user who created the discharge summary. .. Further, the electronic medical record processing unit 120 identifies a record in which the patient ID of the patient corresponding to the created discharge summary is set from the specified records. The specified record becomes a record of related ToDo information. The patient ID of the patient corresponding to the discharge summary is specified as the patient ID corresponding to the medical record screen 440 displayed immediately before the discharge summary creation screen 470.

When the record corresponding to the above condition is specified, the electronic medical record processing unit 120 proceeds to the process in step S85. On the other hand, the electronic medical record processing unit 120 ends the process when the record satisfying the above conditions does not exist.

(S85) The electronic medical record processing unit 120 creates an HTML file for displaying the completion confirmation screen 480 on the terminal device 200. The electronic medical record processing unit 120 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the completion confirmation screen 480.

(S86) When the completion instruction button 481 on the completion confirmation screen 480 is pressed by the user, the terminal device 200 transmits the completion instruction to the management server 100. When the electronic medical record processing unit 120 receives the completion instruction, the electronic medical record processing unit 120 proceeds to the process in step S87. On the other hand, when the end button 482 of the completion confirmation screen 480 is pressed by the user, the terminal device 200 transmits the end instruction to the management server 100. When the electronic medical record processing unit 120 receives the end instruction, the electronic medical record processing unit 120 ends the process.

(S87) The electronic medical record processing unit 120 notifies the ToDo information processing unit 130 of the ToDo ID of the related ToDo information specified in step S84, and requests the completion of the related ToDo information. The ToDo information processing unit 130 refers to the ToDo status table 113, updates the completion status of the record corresponding to the notified ToDo ID to "completed", and completes the related ToDo information.

(S88) The ToDo information processing unit 130 displays the ToDo creation screen 400d on the terminal device 200 based on the record of the ToDo information table 112 corresponding to the notified ToDo ID and the template of the discharge summary approval request. Create an HTML file for. The ToDo information processing unit 130 transmits the created HTML file to the terminal device 200, and causes the Web browser of the terminal device 200 to display the ToDo creation screen 400d.

(S89) When the confirmation button on the ToDo creation screen 400d is pressed, the terminal device 200 transmits the ToDo information registration instruction together with the information set on the ToDo creation screen 400d. The ToDo information processing unit 130 receives the setting information and the registration instruction.

(S90) The ToDo information processing unit 130 creates a new record in the ToDo information table 112, and sets the received setting information in the record. Further, the ToDo information processing unit 130 also creates a new record in the ToDo status table 113, and sets initial values for each item of the created record. As a result, the ToDo information of the discharge summary approval request is registered in the management server 100.

The information processing of the first embodiment can be realized by causing the processor used in the work management device 1 to execute the program. The information processing of the second embodiment can be realized by causing the processor 101 to execute the program. The program can be recorded on a computer-readable recording medium. For example, the recording medium on which the program is recorded can be distributed by distributing the program. Further, the programs that realize the electronic medical record processing unit 120 and the ToDo information processing unit 130 can be distributed separately as separate programs. The electronic medical record processing unit 120 and the ToDo information processing unit 130 may be realized by separate computers.

1 Work management device 1a Storage unit 1b Control unit 2 Display 2a Registration screen 2b Creation screen 2c Confirmation screen 3a, 3b, 3c, 3x, 3y Work information 4 Documents

Claims (6)

On the computer
When a request for registration of work information indicating the work to be performed is received and the work information is registered in the storage unit, and a request for registration of work information indicating the work of creating a document is received as the work, the user who performs the creation work And the type of document to be created are associated with the work information and registered in the storage unit.
When the confirmation instruction for confirming the document being created is received, the first user who has performed the confirmation instruction operation and the type of the document being created are associated with each other from the work information registered in the storage unit. Search for work information and
When the first work information is searched, a confirmation screen for confirming whether to change the first work information to a completed state indicating the completion of the work is displayed.
When the permission operation for permitting the change to the completed state is accepted, the first work information is changed to the completed state.
A work management program that executes processing. The storage unit stores a plurality of templates for setting the contents of the work information.
Wherein in the registration of the work information, determines the contents of the previous SL work information when it is set by using a specific model of the plurality of stationery, registration of the job information is requested,
The work management program according to claim 1. On the computer
When the first work information is changed to the completed state, a setting screen for setting the content of the second work information indicating other work associated in advance with respect to the type of the document being created is displayed. Let me
When the registration request for the second work information is received, the second work information is registered in the storage unit based on the setting contents for the setting screen.
The work management program according to claim 1 or 2, wherein the process is further executed. When displaying the setting screen, the setting screen is displayed in a state where another user associated with the user who has performed the confirmation instruction operation is set as a user who performs the other work.
The work management program according to claim 3. It has a storage unit and a control unit,
The control unit
When the work information registration request indicating the work to be performed is received and the work information is registered in the storage unit, and the work information registration request indicating the document creation work is received as the work, the creation work is performed. The user and the type of the created document are associated with the work information and registered in the storage unit.
When the confirmation instruction for confirming the document being created is received, the first user who has performed the confirmation instruction operation and the type of the document being created are associated with each other from the work information registered in the storage unit. Search for work information and
When the first work information is searched, a confirmation screen for confirming whether to change the first work information to a completed state indicating the completion of the work is displayed.
When the permission operation for permitting the change to the completed state is accepted, the first work information is changed to the completed state.
Work management device. The computer
When a request for registration of work information indicating the work to be performed is received and the work information is registered in the storage unit, and a request for registration of work information indicating the work of creating a document is received as the work, the user who performs the creation work And the type of document to be created are associated with the work information and registered in the storage unit.
When the confirmation instruction for confirming the document being created is received, the first user who has performed the confirmation instruction operation and the type of the document being created are associated with each other from the work information registered in the storage unit. Search for work information and
When the first work information is searched, a confirmation screen for confirming whether to change the first work information to a completed state indicating the completion of the work is displayed.
When the permission operation for permitting the change to the completed state is accepted, the first work information is changed to the completed state.
Work management method.

Images