Medical Support Device, Operating Method Thereof, and Program for Medical Support Device

Abstract

A medical support device that prevents overlooking of revised medical processes, a method for operating the same, and a program for the medical support device are provided. [Solution] In a medical care support system in which a client terminal, a medical care support device, and a group of servers are connected to each other so that they can communicate with each other using a network such as a LAN installed within a medical facility, the medical care support device 12 generates a display screen that displays the contents of multiple items related to the medical care processes of multiple patients, obtains change information indicating that the contents of each of the multiple items related to the patient's medical care process have been changed to at least either unread or revised, and notifies the user of the change information when the display screen is not displayed.

Description

Technical Field

[0001] The present invention relates to a medical support device, an operating method thereof, and a program for a medical support device.

Background Art

[0002] In the medical field, an integrated medical support device that shares the process and results of medical treatment, etc. among medical staff or between medical departments is used in order for medical staff such as doctors and medical technicians to smoothly proceed with examinations and tests. The medical support device supports medical treatment, for example, by providing a list of the processes and results of medical treatment, etc. for a plurality of patients to medical staff (Patent Document 1). Further, the medical support device may support medical treatment by, for example, displaying a so-called timeline in which the processes and results of medical treatment for each patient are arranged in chronological order for each patient, so as to clearly display the medical treatment process and results of that patient (Patent Document 2).

[0003] In addition, in fields other than the medical field, when a plurality of people share and view a document, etc., it is known to set importance or urgency, etc. for the group, and to treat it as read when one person in the group views it (Patent Document 3).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Patent Document 3

Summary of the Invention

Problems to be Solved by the Invention

[0005] The medical support device displays lists and timeline screens related to patients and medical treatment processes as described above. However, in the list related to patients and medical treatment processes, when the number of patients is large or the number of items such as medical treatments is large, even if there are new images and reports, medical staff may overlook them. Also, in the timeline, when multiple examinations are conducted during the same period or when the number of examination items is large, medical staff may overlook new images and reports. Such oversights, or delays in treatment due to overlooking (temporary oversight), may ultimately affect the patient's condition, etc. Therefore, support to prevent oversights is necessary as much as possible.

[0006] For this reason, the medical support device in Patent Document 1 attempts to reduce oversights by, for example, attaching a mark indicating "unread" to new items in the list related to patients and medical treatment processes that have not yet been viewed. Also, the medical support device in Patent Document 2 attempts to reduce oversights by attaching a mark of "un" to unread images, etc. in the timeline.

[0007] On the other hand, after viewing an image, report, etc., its content may be revised. In the medical field, revisions to images or reports, etc. are, for example, the addition or replacement of images taken under different conditions than when the original image was acquired, or the addition or change of findings by a doctor, etc., and affect the treatment policy. Therefore, compared to revisions for the purpose of correcting errors or adding content in general documents, etc., revisions to images or reports, etc. in the medical field have particularly important significance. Therefore, although revised images or reports, etc. can be treated as "unread" again, in the medical field, it is desirable to display, etc. the fact that they have been revised separately from "unread".

[0008] Therefore, an object of the present invention is to provide a medical support device, an operating method thereof, and a program for a medical support device that prevent oversights by calling attention to revisions in the medical treatment process of images or reports, etc.

Means for Solving the Problem

[0009] The medical support device of the present invention includes a processor, which generates a display screen for displaying the contents of a plurality of items related to the medical processes of a plurality of patients, obtains change information indicating that the contents of the plurality of items related to the medical processes of the patients have been changed to at least one of unread or having few revisions, and notifies the change information when the display screen is not being displayed.

[0010] It is preferable that the case where the display screen is not being displayed includes the case where the display screen is minimized.

[0011] The display screen preferably is a display screen that displays a patient column in which patient identification information for identifying a plurality of patients is arranged, at least a part of a plurality of medical process columns in which the contents for a plurality of items related to the medical processes of the plurality of patients are arranged, and a scroll bar.

[0012] The change information indicating a change to unread preferably includes information indicating that an item of a medical process whose status has not been assigned by obtaining an examination image or a report is registered as unread.

[0013] When change information is obtained for an item of a specific medical process among a plurality of medical processes, it is preferable to notify the change information regarding the item of the specific medical process.

[0014] The item of the specific medical process is preferably an item of the medical process associated with the user of the medical support device.

[0015] The item of the specific medical process is preferably an item of the medical process associated with the group to which the user of the medical support device belongs.

[0016] It is preferable to display the change information as a pop-up message.

[0017] It is preferable to notify change information that does not include the personal information of the patient.

[0018] The operation method of the medical support device of the present invention includes a step of generating a display screen for displaying the contents of a plurality of items related to the medical treatment processes of a plurality of patients, a step of obtaining change information indicating that the contents of a plurality of items related to the medical treatment process of the patient have been changed to at least one of unread or having few revisions, and a step of notifying the change information when the display screen is not being displayed.

[0019] The program for the medical support device of the present invention causes a computer to execute a function of generating a display screen for displaying the contents of a plurality of items related to the medical treatment processes of a plurality of patients, a function of obtaining change information indicating that the contents of a plurality of items related to the medical treatment process of the patient have been changed to at least one of unread or having few revisions, and a function of notifying the change information when the display screen is not being displayed.

Advantages of the Invention

[0020] The medical support device, its operation method, and the program for the medical support device of the present invention can reduce the oversight of the medical treatment process with revisions by calling attention to the fact that there are revisions in the medical treatment process.

Brief Description of the Drawings

[0021]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Mode for Carrying Out the Invention

[0022] [First Embodiment] As shown in FIG. 1, the medical support system 10 is a computer system that provides medical support in a medical facility such as a hospital, and includes a client terminal 11, a medical support device 12, and a server group 13. Each element constituting these medical support systems 10 is communicably connected to each other using a network 14 such as a LAN (Local Area Network) installed in the medical facility.

[0023] The client terminal 11 is a terminal for receiving service provision (provision of functions of the medical support device 12) from the medical support device 12, and is a computer (including the case of a tablet terminal, etc.) directly operated by medical staff such as doctors, medical technologists, or nurses. The client terminal 11 is installed in various medical departments such as internal medicine or surgery, various examination departments such as radiology or clinical laboratory, the nursing center, or other necessary locations. Also, the client terminal 11 can be provided for each medical staff, and can also be shared by a plurality of medical staff. Therefore, as shown in FIG. 2, the medical support system 10 includes a plurality of client terminals 11. For example, the group G1 is "internal medicine" to which doctors A1 and A2 belong, and doctors A1 and A2 each have a client terminal 11. Similarly, for example, the group G2 is "surgery" to which doctor B1 belongs, and there is at least one client terminal 11 in the group G2. Also, for example, the group G19 is "radiology" to which technologist N1 belongs, and there is at least one client terminal 11 in the group G19.

[0024] The medical support device 12 provides a display screen including medical data (such as images themselves) and / or information indicating the location of the medical data (such as a link to an image, etc.) to the client terminal 11 in response to a request from the client terminal 11, for example. The medical data is data obtained or created in examinations, inspections, surgeries, etc., such as images, reports, inspection results, other data obtained during or as a result of medical treatment, or information indicating their locations (so-called links (aliases), etc.). The medical support device 12 obtains the medical data used on the display screen from the server group 13.

[0025] The display screen provided by the medical support device 12 to the client terminal 11 refers to the data used by the client terminal 11 to form the screen of the display unit 36 (see FIG. 3) of the client terminal 11. Further, the display screen provided by the medical support device 12 to the client terminal 11 includes not only the data for full-screen display that the client terminal 11 uses to configure the display of the entire screen, but also the data for configuring the display related to a part of the screen. For example, in the present embodiment, the medical support device 12 provides the client terminal 11 with a display screen that can be displayed in a general window format on a part of the screen of the display unit 36.

[0026] The display screens provided by the medical support device 12 to the client terminal 11 are specifically the clinical flow screen 81 (see FIG. 8), the timeline screen 201 (see FIG. 15), the layout screen 301 (see FIG. 16), the unread data list screen 401 (see FIG. 18), and the like. The clinical flow screen 81 is a display screen that displays, for a plurality of patients, for each patient, the identification information of the patient and a part or all of the medical treatment process in association with each other. The identification information of the patient is, for example, the name, date of birth, age, or gender of the patient, or an ID (Identification Data) such as a unique number and / or symbol assigned to the patient (hereinafter referred to as the patient ID). The medical treatment process refers to the process or result of the medical treatment that has already been performed and the medical treatment that is planned to be performed in the future. Therefore, the medical treatment process may include not only the medical treatment data that has already been acquired, etc., but also the medical treatment data that is planned to be acquired, etc. The medical treatment data that is planned to be acquired, etc. is, for example, information regarding the presence or absence of an order for a specific examination, the scheduled date and time thereof, or the type of medical treatment data that is planned to be acquired, etc. In the present embodiment, when one medical treatment process includes a plurality of items (items such as examination results), when referring to the medical treatment process, it refers to any one of the items that make up the medical treatment process, rather than the entire medical treatment process (an aggregate of a plurality of items). The timeline screen 201 is a display screen that displays, for a specific patient, a part or all of the medical treatment process of that patient in chronological order on one screen. The layout screen 301 is a display screen that displays, for a specific patient, a part or all of the medical treatment process of that patient arranged vertically and horizontally (for example, arranged in a tile-like manner). The unread data list screen 401 is a display screen that displays a list of medical treatment data that the medical staff has not confirmed the content of and / or medical treatment data that is planned to be acquired in the future.

[0027] The medical support device 12 provides a display screen to the client terminal 11 in a description format using a markup language such as XML (Extensible Markup Language) data. The client terminal 11 displays the XML-formatted display screen using a web browser. Note that the medical support device 12 can provide the display screen to the client terminal 11 in other formats such as JSON (JavaScript (registered trademark) Object Notation) instead of XML.

[0028] The server group 13 searches for medical data corresponding to a request from the medical support device 12 and provides the medical data corresponding to the request to the medical support device 12. The server group 13 includes an electronic medical record server 21, an image server 22, a report server 23, etc.

[0029] The electronic medical record server 21 has a medical record database 21A for storing electronic medical records. An electronic medical record is an aggregate of one or more pieces of medical data. Specifically, an electronic medical record includes, for example, medical data such as examination records, results of specimen tests, patients' vital signs, orders for examinations, treatment records, or accounting data. Electronic medical records can be input and viewed using the client terminal 11.

[0030] Note that an examination record is a record of the content and results of an interview or palpation, or a disease name, etc. A specimen is blood or tissue collected from a patient, and a specimen test is a blood test or a biochemical test, etc. Vital signs are data indicating the state of a patient such as the patient's pulse, blood pressure, or body temperature. An order for an examination, etc. is a request for an examination such as a specimen test, imaging using various modalities, creation of a report, treatment or surgery, or administration of medicine. A treatment record is a record of treatment, surgery, administration of medicine, or a prescription, etc. Accounting data is data related to medical fees, medicine fees, or hospitalization fees, etc.

[0031] The image server 22 is a so-called PACS (Picture Archiving and Communication System) server and has an image database 22A in which inspection images are stored. The inspection images are images obtained by various image inspections such as CT (Computed tomography) inspection, MRI (Magnetic Resonance Imaging) inspection, X-ray inspection, ultrasonic inspection, or endoscopic inspection. These inspection images are recorded in a format compliant with, for example, the DICOM (Digital Imaging and Communications in Medicine) standard. The inspection images can be viewed using the client terminal 11.

[0032] The report server 23 has a report database 23A in which reading reports are stored. A reading report (hereinafter simply referred to as a report) is a report summarizing the reading results of inspection images obtained by image inspection. The reading of inspection images is performed by a radiologist. The report can be created and / or viewed using the client terminal 11.

[0033] The above-mentioned electronic medical records, inspection images, and reports are each accompanied by a patient ID. In addition to the patient ID, the electronic medical record is accompanied by information for identifying the medical staff who input the medical data for each piece of medical data. The inspection image is accompanied by information for identifying the medical staff (specifically, the medical technician) who performed the inspection in addition to the patient ID. The report is accompanied by information for identifying the medical staff who created it (specifically, the radiologist). The information for identifying the medical staff is the name of the medical staff, etc., or an ID such as a unique number and / or symbol assigned to each medical staff (hereinafter referred to as the medical staff ID).

[0034] The client terminal 11, the medical support device 12, and each of the servers 21 to 23 that make up the server group 13 are configured by installing an operating system program and an application program such as a server program or a client program on a computer such as a server computer, a personal computer, or a workstation. That is, the basic configurations of the client terminal 11, the medical support device 12, and each of the servers 21 to 23 that make up the server group 13 are the same, and include a CPU (Central Processing Unit), a memory, a storage, a communication unit, etc., and a connection circuit that connects these. The communication unit is a communication interface (such as a LAN board) for connecting to the network 14. The connection circuit is, for example, a motherboard that provides a system bus and / or a data bus, etc.

[0035] As shown in FIG. 3, in addition to a CPU 31, a memory 32, a storage 33, a communication unit 34, and a connection circuit 35, the client terminal 11 includes a display unit 36 and an operation unit 37. The display unit 36 is, for example, a display using liquid crystal or the like, and has a screen for displaying at least the display screen provided by the medical support device 12. The operation unit 37 is, for example, a pointing device such as a mouse and / or an input device such as a keyboard. The display unit 36 and the operation unit 37 can constitute a so-called touch panel.

[0036] The client terminal 11 stores, in the storage 33, in addition to an operating system program and the like, an operation program 39. The operation program 39 is an application program for receiving the provision of the functions of the medical support device 12 using the client terminal 11. In the present embodiment, the operation program 39 is a web browser program. However, the operation program 39 can be a dedicated application program for receiving the provision of the functions of the medical support device 12. Note that the operation program 39 may include one or a plurality of widget engines for controlling part or all of the display screen provided by the medical support device 12. A widget engine is a subprogram that exhibits various functions by operating in association with a web browser or the like.

[0037] When the operation program 39 is started on the client terminal 11, as shown in FIG. 4, the CPU 31 of the client terminal 11 functions as a GUI (Graphical User Interface) control unit 41 and a request issuing unit 42 in cooperation with the memory 32.

[0038] The GUI control unit 41 displays the display screen provided by the medical support device 12 on the web browser on the display unit 36. The GUI control unit 41 controls the client terminal 11 in response to an operation instruction input using the operation unit 37, such as a click operation of a button with a pointer.

[0039] The request issuing unit 42 issues various processing requests (hereinafter referred to as processing requests) to the medical support device 12 in response to the operation instruction of the operation unit 37. The processing requests issued by the request issuing unit 42 are, for example, a distribution request for the display screen, or an editing request for the display screen, etc. The request issuing unit 42 transmits the processing request to the medical support device 12 via the communication unit 34 and the network 14.

[0040] The display screen delivery request requests the medical support device 12 to deliver a display screen having a specific configuration. For example, according to the display screen delivery request, any one of the clinical flow screen 81, the timeline screen 201, the layout screen 301, the unread data list screen 401, etc. can be specified to receive the delivery.

[0041] The display screen editing request requests the medical support device 12 to edit the content such as medical data to be displayed on the display screen after receiving the delivery of the display screen having a specific configuration from the medical support device 12. For example, when receiving the delivery of the clinical flow screen 81, requests such as specifying or changing the list of patients to be displayed, specifying or changing the display target period of the medical process, specifying or changing the medical process to be the display target, or sorting the display content are display screen editing requests.

[0042] Note that the display screen delivery request and / or editing request, etc. include information such as the medical staff ID and the address on the network of the client terminal 11. The medical staff ID is input on the login screen (not shown) to the medical support system 10 (or the medical support device 12).

[0043] As shown in FIG. 5, the medical support device 12 includes a CPU 51, a memory 52, a storage 53, a communication unit 54, and a connection circuit 55. The medical support device 12 can be provided with a display unit and / or an operation unit as needed in the same manner as the client terminal 11, and can also be attached with a display unit and / or an operation unit as needed. However, in this embodiment, the medical support device 12 does not have a display unit and an operation unit.

[0044] The medical support device 12 stores, in the storage 53, in addition to an operating system and the like, an operation program 59. The operation program 59 is an application program for causing the computer constituting the medical support device 12 to function as the medical support device 12. When the operation program 59 is started, as shown in FIG. 6, the CPU 51 of the medical support device 12 cooperates with the memory 52 and functions as a request reception unit 61, a display screen generation unit 62, an unread management unit 63, and the like.

[0045] The request reception unit 61 receives various processing requests such as a display screen distribution request and an edit request from the client terminal 11. When the request reception unit 61 receives various processing requests, the request reception unit 61 inputs a processing instruction to each unit that executes the corresponding processing according to the content of the requested processing. For example, when there is a display screen distribution request from the client terminal 11, the request reception unit 61 inputs a generation instruction for the corresponding display screen to the display screen generation unit 62. Similarly, when there is an edit request for a display screen from the client terminal 11, the request reception unit 61 inputs an edit instruction for the corresponding display screen to the display screen generation unit 62. Note that the request reception unit 61 also receives a login request to the medical support device 12, and a login processing unit (not shown) executes login processing such as confirmation of the medical staff ID and password.

[0046] The display screen generation unit 62 generates or edits various display screens such as the clinical flow screen 81. In the present embodiment, when there is a delivery request for a new display screen, the display control unit 66 generates XML data representing the display screen, and when there is an editing request for the display screen, it edits the previously created XML data according to the request content. The display screen generation unit 62 accesses the server group 13 as needed and obtains information related to the medical treatment process and the like used for generating or editing the display screen. Note that the display screen generation unit 62 can hold part or all of the information related to the medical treatment process and the like obtained from the server group 13 in order to reduce the access frequency to the server group 13. When the login processing unit completes the login process normally, the display screen generation unit 62 generates the initial screen 71 (see FIG. 7) to be displayed first after login. Also, when creating or editing the initial screen 71, the display screen generation unit 62 obtains the information necessary for generating or editing the initial screen 71 from the server group 13, the client terminal 11, or a device or system that cooperates with other medical treatment support systems 10.

[0047] The unread management unit 63 manages the status of the medical treatment process included in the display screen generated or edited by the display screen generation unit 62. The status of the medical treatment process is management information including that the medical treatment process is unread, read, or both of these. Unread (management information including being unread) means a state where medical staff has not yet performed a predetermined process such as browsing, editing, inserting comments, approval processing, etc. (hereinafter referred to as browsing, etc.) on the medical treatment process. Read (management information including being read) means a state where medical staff has already performed a predetermined process such as browsing, etc. on the medical treatment process. Management information including both unread and read information is substantially unread or read management information. This is because unread and read represent mutually exclusive states, so being unread means not being read at the same time, and being read means not being unread at the same time.

[0048] In addition, the unread management unit 63 manages the status of "revision" as one of the statuses of the medical process, in addition to unread, read, or both of these. "Revision" is a status indicating that there has been a change in the content of the medical process that was previously unread or read. For example, the revision of examination images refers to adding newly acquired examination images to the already acquired examination images, or replacing some or all of the already acquired examination images with newly acquired examination images, and so on. The revision of a report refers to adding information such as findings to an existing report, or changing the content of an existing report, and so on.

[0049] Furthermore, the unread management unit 63 manages the status of "important" as one of the statuses of the medical process, in addition to the above. "Important" is a status indicating a medical process for which a medical staff has set a setting (for example, setting an important flag) to call attention to the medical process for themselves or other medical staff. The unread management unit 63 can manage the "important" status as a status that is mutually exclusive to unread, read, and revision, or as a status that can coexist with the statuses of unread, read, and revision. Mutually exclusive to unread, etc. means that for one medical process, any one of unread, read, revision, or important is set and managed. Coexisting with unread, etc. means that a certain medical process is managed as unread and important, etc., and unread, read, or revision and important are set and managed in duplicate.

[0050] The unread management unit 63 displays the above status on the display screen generated or edited by the display screen generation unit 62. Thereby, the unread management unit 63 can reduce the oversight of the medical staff in the medical process. For example, the unread management unit 63 attaches a predetermined mark (e.g., a "badge" in a predetermined form) representing the status such as unread or read to the display part of the target medical process on the display screen generated or edited by the display screen generation unit 62. That is, the unread management unit 63 displays the status such as unread on the display screen according to the presence or form of a specific mark attached to the medical process. The display by the mark is visually easy to understand and is particularly easy to achieve the purpose of reducing oversight. The form of the mark is the shape of the mark (including differences in size), color, pattern, etc., or a combination thereof.

[0051] In this embodiment, since the display screen generation unit 62 generates or edits XML data representing the display screen, the unread management unit 63 edits the XML data generated or edited by the display screen generation unit 62, or causes the display screen generation unit 62 to edit it (including the case of editing simultaneously with the generation of the display screen), thereby specifying the medical process to which the mark is attached, the color and form of the mark to be attached, or specifying the medical process from which the already attached mark is removed (or the medical process to which no mark is attached). Thereby, the unread management unit 63 displays the status such as unread on the display screen generated etc. by the display screen generation unit 62.

[0052] In particular, when there is a revision to a medical process whose status is unread or read, the unread management unit 63 displays the status of the revised medical process in a display mode different from the display modes representing unread and read. Thereby, the unread management unit 63 provides information to the user of the client terminal 11 indicating that there has been a revision to the medical process, distinguishable from unread and read.

[0053] In addition, in the present embodiment, the unread management unit 63, for example, attaches a mark indicating unread or the like for unread or the like, and additionally attaches a mark indicating importance for a medical process with a setting indicating importance, so as to display in a state where the status of unread or the like and the status of importance can coexist. As a result, the unread management unit 63 distinguishes the status of a specific medical process with a setting indicating importance from the status of a medical process without a setting indicating importance, and displays them in different display modes on the display screen. As a result, the unread management unit 63 can reduce the oversight of a medical process with a setting indicating importance.

[0054] The unread management unit 63 acquires each status of unread, read, revised, and / or important, for example, from a device or system that cooperates with the medical support device 12, such as the server group 13. In addition, the unread management unit 63 can directly acquire each status of unread, read, revised, and / or important from the client terminal 11 by acquiring the operation information of the client terminal 11.

[0055] The display screen generation unit 62 distributes the display screen generated or edited as described above to the client terminal 11 via the communication unit 54. As a result, the client terminal 11 displays the display screen provided by the display screen generation unit 62 on the display unit 36. In addition, when the unread management unit 63 further edits the display screen generated or edited by the display screen generation unit 62 in order to display a mark such as unread on the display screen, the unread management unit 63 can provide the display screen to the client terminal 11.

[0056] In addition, the unread management unit 63 manages the number of items of each status of unread, read, revised, and / or important displayed on the display screen, and displays the number of items of each status on the display screen as needed. In the present embodiment, the total number of unread items and the number of revised items is managed as the number of unread items and displayed on the display screen.

[0057] In addition, the unread management unit 63 can manage each status of unread, read, revised, and / or important separately for each requester of the medical process, and can display them on the display screen in a display mode that can be distinguished for each requester. The distinction for each requester of the medical process includes, in addition to distinguishing each medical staff member, distinguishing for each group (such as a medical department) to which the medical staff belongs. In the present embodiment, each status of unread, read, revised, and / or important is managed by distinguishing requesters, and is displayed on the display screen in a display mode that can be distinguished for each requester. Further, in the present embodiment, the requesters of the medical process are distinguished into three types: "oneself", "own department", and "other department". "Oneself" represents the case where the requester of the medical process is the user himself / herself of the client terminal 11. The user of the client terminal 11 is a person who uses the client terminal 11 and browses the display screen on the client terminal 11. "Own department" represents the case where the requester of the medical process belongs to the group to which the user of the client terminal 11 belongs and is a medical staff other than the user of the client terminal 11. "Other department" represents the case where the requester of the medical process is a medical staff belonging to a group to which the user of the client terminal 11 does not belong.

[0058] That is, the unread management unit 63 manages the status such as unread by distinguishing "oneself" from "own department" and "other department". In this regard, the unread management unit 63 distinguishes the status of the medical process requested by the person (oneself) who browses the display screen from the status of the medical process requested by a person other than the person who browses the display screen (medical staff of own department and / or other department), and displays these in different display modes on the display screen. Thereby, the medical staff can clearly recognize the medical process that oneself should browse, etc., separately from others. As a result, the medical staff can reduce the oversight of the medical process that oneself should browse, etc.

[0059] Similarly, the unread management unit 63 manages the status of unread and the like by distinguishing between "oneself" and "one's own department" and "other departments". In this regard, the unread management unit 63 differentiates between the status of unread and the like regarding the medical treatment processes requested by the staff members belonging to the group to which the person (oneself) viewing the display screen belongs (medical staff belonging to one's own department (including oneself)), and the status of unread and the like regarding the medical treatment processes requested by the staff members belonging to the group to which the person viewing the display screen does not belong (medical staff belonging to other departments), and displays these in different display modes on the display screen. As a result, medical staff can clearly recognize, separately from others, the medical treatment processes that medical staff in their own department, including themselves, should view and the like. Consequently, medical staff can efficiently support or manage the tasks of medical staff in the same group, and can reduce oversight of medical treatment processes at the group level. Also, if necessary, by communicating with other departments and the like, it is possible to support the reduction of oversight by medical staff in other departments. When the user of the client terminal is an administrator (responsible person) of a medical facility such as a hospital, management can be carried out so that there is no oversight of medical treatment processes for the entire facility.

[0060] And the unread management unit 63 manages the status of unread and the like by distinguishing between "oneself", "one's own department", and "other departments". In this regard, the unread management unit 63 differentiates between the status of unread and the like regarding the medical treatment processes requested by the person (oneself) viewing the display screen, the status of unread and the like regarding the medical treatment processes requested by the staff members belonging to the group to which the person viewing the display screen belongs and who are other than the person viewing the display screen (medical staff in one's own department (excluding oneself)), and the status of unread and the like regarding the medical treatment processes requested by the staff members belonging to the group to which the person viewing the display screen does not belong (medical staff in other departments), and displays these in different display modes on the display screen. As a result, since the status of unread and the like is clear in a state where "oneself", "one's own department", and "other departments" are distinguished, it is possible to reduce oversight of the medical treatment processes that oneself should view and the like, reduce oversight of medical treatment processes at the group level, and also support the reduction of oversight by medical staff in other departments.

[0061] The medical support system 10 configured as described above operates as follows. First, when a medical staff member logs in to the medical support system 10 using the client terminal 11, the screen generation unit 62 generates an initial screen 71 shown in FIG. 7 based on settings etc. for each medical staff member, and provides it to the client terminal 11. As a result, the client terminal 11 displays the initial screen 71 on the screen of the display unit 36.

[0062] The initial screen 71 has, for example, three display columns: a schedule display column 72, a mail display column 73, and a list display column 74. The display contents of the schedule display column 72 and the mail display column 73 are generated by a gadget engine, which is part of the operating program 39 of the client terminal 11, obtaining information from the client terminal 11 and other devices or systems. Also, in this embodiment, the list display column 74 displays at least a part of the clinical flow screen 81. For this reason, the display screen generation unit 62 generates an initial screen 71 including the schedule display column 72 and the mail display column 73 without content, and the list display column 74 including the content of the clinical flow screen 81. The client terminal 11 uses the gadget engine to display on the screen of the display unit 36 an initial screen 71 with the contents of the schedule display column 72 and the mail display column 73 replenished.

[0063] If all of the content to be displayed does not fit within the list display column 74, a scroll bar 78 and a scroll bar 79 for transitioning (so-called scrolling) the display content of the list display column 74 are displayed in the list display column 74 or in the vicinity of the list display column 74. The scroll bar 78 is a GUI that is operated when transitioning the display content of the list display column 74 in the horizontal direction to display the non-displayed part. The scroll bar 79 is a GUI that is operated when transitioning the display content of the list display column 74 in the vertical direction to display the non-displayed part. The display and control of such GUIs are performed by the GUI control unit 41.

[0064] In the initial screen 71 described above, when an operation such as a predetermined menu is performed using a GUI such as a pointer (not shown), the request issuing unit 42 issues a distribution request for the display screen. The operation in which the request issuing unit 42 issues a distribution request for the display screen based on such an operation of the GUI or the like constitutes a display screen distribution request step. In the present embodiment, in order to display the entire clinical flow screen 81 in which a part is displayed in the list display column 74, an operation for displaying the clinical flow screen 81 is executed. As a result, the request issuing unit 42 issues a distribution request for the clinical flow screen 81.

[0065] When the request issuing unit 42 issues a distribution request for the display screen, in the medical support device 12, the request receiving unit 61 receives the distribution request for the display screen, and the display screen generation unit 62 generates a display screen related to the distribution request for the display screen. The operation in which the display screen generation unit 62 generates a display screen related to the distribution request for the display screen constitutes a display screen generation step. In the present embodiment, the display screen generation unit 62 generates the clinical flow screen 81 using information related to the medical process or the like appropriately acquired from the server group 13 or the like.

[0066] As described above, when the display screen generation unit 62 generates a display screen related to a distribution request, before generating the display screen, simultaneously with (in parallel with) the generation of the display screen, or after generating the display screen, the unread management unit 63 appropriately acquires, from the server group 13 or the like, the status regarding the unread or the like of the medical process to be displayed on the display screen. Then, the unread management unit 63 edits the display screen generated by the display screen generation unit 62, or causes the display screen generation unit 62 to further edit it. Thereby, the unread management unit 63 displays the status regarding the unread or the like on the display screen. In the present embodiment, since the display screen generation unit 62 generates the clinical flow screen 81, the unread management unit 63 acquires, etc., the status regarding the unread or the like of the medical process to be displayed on the clinical flow screen 81, and displays the status regarding the unread or the like on the clinical flow screen 81. The operation in which the unread management unit 63 acquires, etc., the status regarding the unread or the like of the medical process constitutes a status acquisition step. Also, the operation of the unread management unit 63 for displaying the status regarding the unread or the like of the medical process on the display screen generated by the display screen generation unit 62 constitutes a status display step.

[0067] Thereafter, the GUI control unit 41 of the client terminal 11 receives the distribution of the display screen generated as described above, and displays this on the screen of the display unit 36 instead of the initial screen 71, or displays it in another window or the like while leaving the initial screen 71 and superimposing it.

[0068] As shown in FIG. 8, the clinical flow screen 81 generated or the like in the present embodiment includes, for example, a clinical flow display column 82 having a patient column C01, an unread count management column C02, a biophysical examination column C03, a radiation column C04, an endoscope column C05, a pathology column C06, an echocardiogram column C07, and the like. The patient column C01 constitutes a list related to a plurality of patients satisfying a predetermined condition. The predetermined condition is, for example, that the person in charge is a medical staff who is the logged-in user, or that the person in charge is a group (such as a department) to which the medical staff who is the logged-in user belongs, and the like. The unread count management column C02 is an aggregate of columns for displaying the unread count of the medical process. The biophysical examination column C03, the radiation column C04, the endoscope column C05, the pathology column C06, the echocardiogram column C07, and the like (columns other than the patient column C01 and the unread count management column C02) are each an aggregate of columns for displaying the process or result of each examination or the like with its display name. Each column of the biophysical examination column C03, the radiation column C04, the endoscope column C05, the pathology column C06, the echocardiogram column C07, and the like (columns other than the patient column C01 and the unread count management column C02) constitutes a medical process column for displaying the medical process. Note that, similar to the list display column 74 on the initial screen 71, the clinical flow display column 82 can display a non-displayed portion by a scroll operation or the like.

[0069] Also, as shown in FIGS. 9 and 10, the clinical flow display column 82 has an item display row L01 indicating the display items of each column in the top row. By clicking on the item name or the like in each column of the item display row L01 with a pointer or the like, the display content can be sorted in row units according to descending order, ascending order, or other specified conditions. Sorting in row units means changing the display order while maintaining the correspondence in the row direction. For example, when "patient" is clicked in the patient column C01 and the item display row L01, the request issuing unit 42 issues an edit request for the display screen. Then, the display screen generation unit 62 edits the clinical flow screen 81 according to a predetermined condition such as the order of patient IDs and provides it to the client terminal 11. As a result, the display content of the clinical flow display column 82 is sorted in the order of patient IDs or the like. In addition, a mark (for example, "▲" mark) indicating that sorting has been performed is displayed for each item in the item display row L01 used as the sorting criterion.

[0070] Among the rows from the second row onwards in the clinical flow display column 82, each row constitutes a so-called clinical flow that associates the identification information of each patient with the medical treatment process of that patient. In FIGS. 9 and 10, the clinical flows of two patients, "Taro Yamaguchi" shown in row L02 and "Jiro Yamaguchi" shown in row L03, are exemplified respectively. Also, the medical treatment processes included in the clinical flow of each patient are managed and displayed for each item included in each medical treatment process (for example, for each medical treatment data). For example, for the radiographic image examination (radiation column C04), which is one of the medical treatment processes, the status such as unread for the "image" of CT, the "report" of CT, the "image" of MRI, and the "report" of MRI are managed and displayed separately. In the medical treatment process column of each patient (for example, the column in row L02 and column C04), for those with the display of "image" or "report", it indicates that the medical treatment data has already been acquired, etc. And not displaying "image" or "report" represents that the "image" or "report" has not yet been acquired, etc., or there is no plan to acquire, etc. (for example, refer to the column in row L03 and column C04). The same applies to other medical treatment process columns.

[0071] Statuses such as unread are displayed with a "badge", which is a mark indicating the content of the status, attached to each item in the medical treatment process. As shown in FIG. 11, the unread management unit 63 uses badges with different shapes and patterns to display statuses such as unread, including an essentially new "unread" due to newly acquiring medical data, etc., a "revision" indicating that it has become unread again due to a revision, "read", and "important". In this specification, when simply referring to unread, it means the above-mentioned new unread. In this embodiment, a round-shaped ("○") badge is attached to the "unread" item. Also, a square-shaped ("□") badge including a pattern imitating a pen is attached to an item with a "revision". A triangular-shaped ("△") badge including an exclamation mark ("!") pattern is attached to the "important" item. And for the "read" item, it is indicated as read by not attaching any of these or by depriving these badges.

[0072] Also, statuses such as unread have different colors for the "badge", which is a mark indicating the content of the status, according to the requester in the medical treatment process. Thereby, the difference between requesters of "oneself", "own department", and "other department" is indicated by the color of the badge. For example, the color representing "oneself" is orange, the color representing "own department" is blue, and the color representing "other department" is green.

[0073] For example, in the column at row L02 and column C04 (see FIG. 10), an orange and round-shaped badge is attached to the item of the CT report. Therefore, it is clear that the CT report of the patient ("Yamatarou the Goat") is requested by oneself who is the user of the client terminal 11, and it is a newly added unread report. Also, in the same column, an orange and square-shaped badge is attached to the item of the MRI report. Therefore, it is clear that the MRI report of the patient has a revision mark because it has become unread due to a revision and is requested by oneself who is the user of the client terminal 11. Note that in the same column, since neither the CT examination image ("image") nor the MRI examination image has any marks, it can be seen that they have been read and there has been no subsequent revision. The same applies to other columns.

[0074] As shown in FIG. 12, for example, when the MRI report is a report requested by oneself who is the user of the client terminal 11, it has become unread due to a revision, and the medical staff who is the creator of the report has set that the revision content is "important", both a green square badge indicating that there has been a revision and a green triangle badge indicating that it is important are attached. Thereby, it is clear that there has been a revision and that the content is important.

[0075] As described above, the medical support device 12 manages the status such as unread for the medical process by the unread management unit 63. And it displays the status such as unread on a display screen such as the clinical flow screen 81. Therefore, since the status such as unread of each medical process is clear on the display screen such as the clinical flow screen 81, it is possible to reduce the oversight of unread medical processes.

[0076] Then, the medical support device 12 clearly distinguishes and manages and displays "unread" due to newly acquired information, etc. and "revision". Compared with revisions for the purpose of correcting errors or adding content in general documents in other fields, etc., revisions to the medical process are highly likely to be directly related to subsequent treatment policies, etc., and have particularly important significance. Therefore, when there is a revision to the medical process, by managing and displaying this fact separately from other statuses, it is possible to reduce the oversight of the above-mentioned particularly important revised information.

[0077] The management and display of statuses such as unread in the first embodiment are particularly useful at least when a display screen that is commonly browsed, etc. by oneself, who is the user of the client terminal 11, and others (medical staff other than oneself belonging to the same department or medical staff from other departments) is displayed on the screen. This is because, on a display screen such as the clinical flow screen 81, in addition to the medical process requested by oneself, the medical processes requested by others are also displayed.

[0078] In the first embodiment, the clinical flow screen 81, which is one of the display screens, has a column in the unread count management column C02 for each patient (see FIG. 9), such as the column at row L02 and column C02 (hereinafter referred to as the unread count display column). When providing an unread count display column, even without scrolling to check the entire clinical flow, it is possible to immediately recognize the presence or absence of a medical process in an unread or revised state, so it is easier to further reduce the oversight of a medical process in an unread or revised state. The unread count display column displays, for example, the number (number of cases) of medical processes whose status is unread or revised for each patient. In this embodiment, the unread count display column is divided into three rows. For example, as shown in FIG. 13, the number of unread or revised cases of "oneself" is displayed in the first row S1, the number of unread or revised cases of "own department" is displayed in the second row S2, and the number of unread or revised cases of "other departments" is displayed in the third row S3. Also, when the number of displayed cases in each of these rows S1 to S3 is one or more, the same color as that of a badge is applied. For example, when the number of cases displayed in the first row S1 is one or more, the first row S1 is colored orange, similar to the badge indicating unread or revised cases of "oneself". As a result, even without scrolling to check the entire clinical flow, it is possible to distinguish between "oneself", "own department", and "other departments", and immediately recognize the presence or absence of a medical process in an unread or revised state in each category, so it is particularly easy to reduce the oversight of a medical process in an unread or revised state. When the number of displayed cases is 0, as shown in FIG. 14, the rows S1 to S3 are not colored. This is to make the colored rows relatively more prominent.

[0079] In the above first embodiment, the shape of the badge is changed based on the status such as unread, and the color of the badge is changed based on the category of the requester (see FIG. 11). However, the color of the badge may be changed based on the status such as unread, and the shape of the badge may be changed based on the category of the requester. Also, the form of the badge may be changed for each combination of the status such as unread and the category of the requester. Of course, a badge indicating the status of read may be provided. In addition, as long as each section can be distinguished, the form of the badge is arbitrary. The same applies to the setting of the display color of the unread count display column.

[0080] In the above first embodiment, the status such as unread is displayed on the display screen using a badge (see FIG. 11). Instead of attaching a badge to the medical treatment process, or in addition to attaching a badge, the display mode of the medical treatment process itself may be changed to display the status such as unread. For example, the status such as unread may be displayed by changing the font type, font size, font color, and background color of the character "Image" according to the status such as unread.

[0081] [Second Embodiment] In the above first embodiment, the status such as unread of the medical treatment process is displayed on the clinical flow screen 81. However, as shown in FIG. 15, when the display screen generation unit 62 generates or edits the timeline screen 201, similar to the clinical flow screen 81 of the first embodiment, the unread management unit 63 can display the status such as unread regarding the medical treatment process on the timeline screen 201.

[0082] The timeline screen 201 displays by associating time elements such as date and time with the medical treatment process. For example, in FIG. 15, it is displayed that there was an examination by CT in the column of "18 / 06 / 12" (June 12, 2018). In this case, the unread management unit 63 attaches a badge similar to the badge (see FIG. 11) on the clinical flow screen 81 of the first embodiment, for example, to the display of "Image" indicating the examination image of CT or "Repo" indicating the report, so as to display the status such as unread on the timeline screen 201. In FIG. 15, a green square badge indicating "Revised" is attached to the CT report ("Repo").

[0083] As described above, when displaying the status such as unread of the medical treatment process on the timeline screen 201, it is possible to associate and grasp the date and time when the medical treatment process was performed or the date and time scheduled to be performed in the future with the status such as unread. For example, when performing the same type of medical treatment process multiple times, it is beneficial to be able to distinguish each medical treatment process and grasp the status such as unread. Also, when there is a revision after a certain amount of time has passed since the medical treatment process was first implemented, even if notified by email or the like, it is not easy to visually recognize that there has been a revision to the past medical treatment process on other display screens. However, if the revision status is displayed on the timeline screen 201, the revision to the past medical treatment process can be grasped easily and surely.

[0084] [Third Embodiment] As shown in FIG. 16, when the display screen generation unit 62 generates or edits the layout screen 301, similar to the clinical flow screen 81 of the first embodiment, the unread management unit 63 can display the status such as unread of the medical treatment process on the layout screen 301. In FIG. 16, the unread management unit 63 displays the status of "revision" on the endoscopic image column 302 that constitutes a part of the layout screen 301 for the inspection image of the endoscope. More specifically, as shown in FIG. 17, a status display column 303 for displaying the status regarding revision and other unread etc. is provided in the endoscopic image column 302. Then, the status regarding revision and other unread etc. is displayed in the status display column 303 by means of characters such as "revision", badges indicating "revision" etc., and / or coloring of the status display column 303. The form of the badge and the color to be colored etc. are the same as those in the first embodiment.

[0085] As described above, when displaying the status such as unread on the layout screen 301, it is possible to list the outline of the patient's medical treatment process and grasp the status such as unread. In particular, when displaying the status of "revision" on the layout screen 301, it is possible to easily compare the process or result of other medical treatment processes with the content of the medical treatment process with "revision". Therefore, it is possible to accurately grasp the content of "revision" and particularly quickly proceed with operations such as diagnosis.

[0086] [Fourth Embodiment] As shown in FIG. 18, when the display screen generation unit 62 generates or edits the unread data list screen 401, the unread management unit 63 can display the status such as unread regarding the medical treatment process on the unread data list screen 401, similar to the clinical flow screen 81 of the first embodiment. In FIG. 18, a status bar 402 for displaying the status such as unread is provided, and by displaying the characters "unread" or "revision" in the status bar 402, the status of "unread" or "revision" is displayed for the corresponding data. Also, for example, by coloring each row with the same color as the legend (see FIG. 11) of the first embodiment, the requesters can be distinguished. In FIG. 18, the data type is an item of the medical treatment process.

[0087] As described above, by generating and displaying the unread data list screen 401, the medical support system 10 can manage the status such as unread in the entire facility such as a hospital and reduce the oversight of the medical treatment process with the status such as unread. This is because the unread or revised medical treatment processes can be listed. Also, the unread data list screen 401 that distinguishes and displays unread and revised allows for considerations such as preferentially processing the medical treatment processes in the particularly important "revised" state. Therefore, compared with the case of making a list display without distinguishing between unread and revised, significant oversights can be more reliably reduced.

[0088] Note that the display screen generation unit 62 and the unread management unit 63 can generate and edit an unread list display screen that lists only the medical processes in the new "unread" state. Similarly, the display screen generation unit 62 and the unread management unit 63 can list only the medical processes in the "revision" state. The same applies to other statuses.

[0089] In the first embodiment and the like, the display screens such as the clinical flow screen 81 are generated and displayed via the initial screen 71. However, the display screens such as the clinical flow screen 81 can be indirectly generated from other devices or systems that cooperate with the medical support device 12. For example, since the electronic medical record server 21 can be directly operated from the client terminal 11, the clinical flow screen 81 can be called during the operation of the electronic medical record server 21.

[0090] In the display screens such as the clinical flow screen 81, the timeline screen 201, the layout screen 301, or the unread data list screen 401 of the first embodiment and the like, patients, medical processes, or items included in the medical processes can be arbitrarily searched, sorted, or selected for inclusion or exclusion.

[0091] <Conditions for marking as read> In principle, the status of unread, etc. in the above-described first embodiment, etc. can be changed by anyone who is a medical staff member who can log in to the medical support system 10. That is, when either the requester or a person other than the requester of a medical process whose status is unread or revised views the medical process whose status is unread or revised, the unread management unit 63 changes the status to read. For example, when a medical process in the "unread" or "revised" state is viewed, etc. by the requester of that medical process, the unread management unit 63 changes the status of that medical process to "read". Also, even when a medical process in the "unread" or "revised" state is viewed, etc. by a person other than the requester of that medical process, the unread management unit 63 changes the status of that medical process to "read". In this way, allowing any medical staff member to change an unread or revised medical process to read can reduce the oversight of medical processes in the unread or revised state for the entire medical facility such as a hospital.

[0092] However, the unread management unit 63 can change the status to read when a specific person (person eligible for read) views a medical process whose status of unread, etc. is unread or revised. For example, it may be limited to the case where the requester himself / herself of the medical process views the medical process that can be changed to the read status from the unread or revised status. Also, the person who can change the unread or revised medical process to the read status may be limited to the requester himself / herself of that medical process ("oneself") or a person belonging to the group to which the requester himself / herself of that medical process belongs ("one's own department"). In this way, when limiting the person who can mark as read to a specific person, it will not be marked as read unless the person who should view the unread or revised medical process views it, etc. Therefore, the person who should view the unread or revised medical process can surely view that medical process. Also, it is possible to prevent mistakes such as a person other than the person who should view the unread or revised medical process viewing it and thus marking it as read and the person who should view it overlooking this.

[0093] In addition, the unread management unit 63 may be configured to change the status of an unread or revised medical process to read when a plurality of medical staff members view it or the like. In particular, when a specific plurality of medical staff members view it or the like, the unread or revised medical process may be changed to read. This is useful when a plurality of medical staff members should view an unread or revised medical process. For example, it is useful when it is necessary to request viewing (approval) or the like from the attending physician in addition to a temporary attending physician (e.g., an intern).

[0094] In the first embodiment and the like, when a medical staff member views or the like an medical process whose status is unread or revised, the unread management unit 63 automatically changes the status of the viewed medical process to read without performing an explicit read operation. If overlooking can be prevented, there is no need to execute an explicit read operation, so the operation burden is small and the convenience is high. However, when the unread management unit 63 receives an operation input to change the status of an medical process whose status is unread or revised to read, it can change the status to read. If it is set to be read only by an explicit operation, even if a person who does not need to view or the like accidentally views an unread or revised medical process, it will not be marked as read, so that the person who should view or the like can surely view the unread or revised medical process without overlooking it. The explicit operation for marking as read is a menu selection on the client terminal 11, a click on a button or the like, or other operations.

[0095] Note that the unread management unit 63 can accept an operation to change (restore) the status of a read medical process to unread or revised. The operation to change the read status to an unread or revised status is a menu selection on the client terminal 11, a click on a button or the like, or other operations. In this way, when the status once marked as read can be changed to unread or revised, even if a person who does not need to view or the like accidentally marks a medical process as read, it can be restored, so that the person who should view or the like can surely view the unread or revised medical process without overlooking it.

[0096] As shown in FIG. 19, it is preferable that the medical support device 12 of the first embodiment or the like includes a notification unit 501 that notifies of a change to an unread or revised status when the client terminal 11 does not display the display screen generated by the display screen generation unit 62 on the display unit 36. The change to the unread status means that a medical process to which a status has not been assigned due to acquisition of an examination image, a report, or the like is registered with an unread status. The notification unit 501 acquires information indicating that the status of the medical process has changed to unread or revised from the unread management unit 63. The notification unit 501 is one function of the operation program 59, and the CPU 51 and the memory 52 cooperate to function as the notification unit 501.

[0097] For example, as shown in FIG. 20, it is assumed that a display screen such as the clinical flow screen 81 is minimized and the client terminal 11 is displaying a so-called desktop screen 503 on the display unit 36. In this case, when the notification unit 501 acquires information indicating that the status has changed to unread or revised for a specific medical process, the notification unit 501 displays a pop-up message 504 or the like on the desktop screen 503 (the screen displayed by the client terminal 11) to notify the user of the client terminal 11 that the status of the specific medical process has changed to unread or revised. The specific medical process is, for example, a medical process in which the requester is the user of the client terminal 11, or a medical process in which a medical staff member of the same department is the requester.

[0098] As described above, when a notification is made when the status of a specific medical process becomes unread or revised, even when the display screen provided by the medical support device 12 such as the clinical flow screen 81 is not being displayed, it is possible to know the existence of a specific medical process that has newly become unread or revised. As a result, overlooking of that medical process can be reduced.

[0099] Note that the notification unit 501 can change the content of the notification in the pop-up message 504 or the like according to the setting. For example, a part of the notification content can be omitted or made into a hidden text. When notifying with the pop-up message 504, the notification unit 501 is useful when omitting a part related to the patient's personal information or when examining another patient at the location where the client terminal 11 is located.

[0100] As shown in FIG. 21, the medical support device 12 of the first embodiment or the like preferably includes a medical record writing unit 601 that automatically writes the content of the medical process whose status has become read into the electronic medical record when the status of the medical process becomes read. The medical record writing unit 601 acquires information indicating that the status of the medical process has become read from the unread management unit 63. The medical record writing unit 601 is one function of the operation program 59, and the CPU 51 and the memory 52 cooperate to function as the medical record writing unit 601. In this way, when the content of the medical process whose status has become read is automatically written into the electronic medical record, it becomes easier to create the electronic medical record. Further, when the medical record writing unit 601 automatically writes the content of the medical process that has become read into the electronic medical record, the medical record writing unit 601 can receive an input of a comment from the medical staff. In this case, it becomes even easier to create the electronic medical record.

[0101] The medical support system 10 of the first embodiment or the like includes a display screen generation unit 62 that generates a display screen for displaying, for each of a plurality of patients, the patient's identification information and the medical process in association with each other, and an unread management unit 63 that displays, on the display screen, a status including information that the medical process is unread, read, or both. When there is a revision to the medical process whose status is unread or read, the unread management unit 63 displays the status of the revised medical process in a display mode different from the display mode indicating unread and read.

[0102] In addition, the operation program 59 of the medical support device 12 in the first embodiment and the like causes the CPU 51, or the CPU 51 and the memory 52, to function as a display screen generation unit 62 that generates a display screen for displaying, for each of a plurality of patients, the identification information of the patient and the medical process in association with each other, and an unread management unit 63 that displays, on the display screen, a status including information indicating that the medical process is unread, read, or both. When there is a revision to a medical process whose status is unread or read, the unread management unit 63 displays the status of the revised medical process in a display mode different from the display modes indicating unread and read.

[0103] The operation method of the medical support device 12 in the first embodiment includes a display screen generation unit 62 that generates a display screen for displaying, for each of a plurality of patients, the identification information of the patient and the medical process in association with each other, and an unread management unit 63 that displays, on the display screen, a status including information indicating that the medical process is unread, read, or both. The operation method of the medical support device 12 includes a step in which, when there is a revision to a medical process whose status is unread or read, the unread management unit 63 displays the status of the revised medical process in a display mode different from the display modes indicating unread and read.

[0104] The operation method of the medical support system 10 in the first embodiment and the like includes a display screen generation unit 62 that generates a display screen for displaying, for each of a plurality of patients, the identification information of the patient and the medical process in association with each other, and an unread management unit 63 that displays, on the display screen, a status including information indicating that the medical process is unread, read, or both. The operation method of the medical support system 10 includes a step in which, when there is a revision to a medical process whose status is unread or read, the unread management unit 63 displays the status of the revised medical process in a display mode different from the display modes indicating unread and read.

[0105] In the above-described first embodiment and the like, the hardware structure of the processing unit that executes various processes such as the GUI control unit 41, the request issuing unit 42, the request receiving unit 61, the display screen generation unit 62, the unread management unit 63, the notification unit 501, and the medical record writing unit 601 is various processors as shown below. The various processors include a CPU (Central Processing Unit), which is a general-purpose processor that executes software (program) and functions as various processing units, and a programmable logic device (PLD) such as an FPGA (Field Programmable Gate Array), which is a processor whose circuit configuration can be changed after manufacturing, and an application-specific electric circuit, which is a processor having a circuit configuration specifically designed to execute various processes.

[0106] One processing unit may be constituted by one of these various processors, or may be constituted by a combination of two or more processors of the same type or different types (for example, a plurality of FPGAs, or a combination of a CPU and an FPGA). Also, a plurality of processing units may be constituted by one processor. As an example of constituting a plurality of processing units by one processor, first, as represented by a computer such as a client or a server, one processor is constituted by a combination of one or more CPUs and software, and this processor functions as a plurality of processing units. Second, as represented by a System On Chip (SoC), there is a form in which a processor that realizes the functions of the entire system including a plurality of processing units with one IC (Integrated Circuit) chip is used. Thus, the various processing units are constituted by using one or more of the above-described various processors as the hardware structure.

[0107] Furthermore, the hardware structure of these various processors is more specifically an electric circuit in the form of a combination of circuit elements such as semiconductor elements.

Explanation of Signs

[0108] 10 Medical Support System 11 Client Terminal 12 Medical Support Device 13 Server Group 14 Network 21 Electronic Medical Record Server 21A Medical Record Database 22 Image Server 22A Image Database 23 Report Server 23A Report Database 32 Memory 33 Storage 34 Communication Unit 35 Connection Circuit 36 Display Unit 37 Operation Unit 39 Operating Program 41 GUI Control Unit 42 Request Issuing Unit 52 Memory 53 Storage 54 Communication Unit 55 Connection Circuit 59 Operating Program 61 Request Reception Unit 62 Display Screen Generation Unit 62 Screen Generation Unit 63 Unread Management Unit 66 Display Control Unit 71 Initial Screen 72 Schedule Display Column 73 Mail Display Column 74 List Display Column 78 Scroll Bar 79 Scroll Bar 81 Clinical Flow Screen 82 Clinical Flow Display Column 201 Timeline Screen 301 Layout Screen 302 Endoscope Image Column 303 Status Display Column 401 Unread Data List Screen 402 Status bar 501 Notification section 503 Desktop screen 504 Pop-up message 601 Medical record writing section A1 Doctor A2 Doctor B1 Doctor C01 Patient column C02 Unread count management column C03 Biopsy column C04 Radiology column C04 Radiology section C05 Endoscopy column C06 Pathology column C07 Echocardiogram column G1 Group G19 Group G2 Group L01 Item display row N1 Technician S1 First row S2 Second row S3 Third row

Claims

1. comprising a processor, wherein the processor, generates a display screen for displaying the content for a plurality of items related to the medical treatment processes of a plurality of patients, obtains change information indicating that at least any one of the content of a plurality of items related to the medical treatment process of the patient has been changed to a revision, and when the display screen is not being displayed and the desktop screen is being displayed, as the change information, notifies the items of the revised medical treatment process and does not notify the items of the medical treatment process that has not been revised, a medical treatment support device.

2. The case where the display screen is not being displayed includes the case where the display screen is minimized, The medical treatment support device according to claim 1.

3. The display screen is a display screen that displays at least a part of a patient column in which patient identification information for identifying a plurality of patients is arranged, a plurality of medical treatment process columns in which the content for a plurality of items related to the medical treatment processes of the plurality of patients is arranged, and a scroll bar, the medical treatment support device according to claim 1.

4. wherein the processor, when obtaining change information for items of a specific medical treatment process among the medical treatment processes of the plurality of patients, notifies the change information related to the items of the specific medical treatment process, the medical treatment support device according to claim 1.

5. The items of the specific medical treatment process are the items of the medical treatment process associated with the user of the medical treatment support device, the medical treatment support device according to claim 4.

6. The items of the specific medical treatment process are the items of the medical treatment process associated with the group to which the user of the medical treatment support device belongs, the medical treatment support device according to claim 4.

7. wherein the processor, displays the change information as a pop-up message, the medical treatment support device according to claim 1.

8. The processor is configured to: The medical support device according to claim 1, which notifies the changed information that does not include the personal information of the patient.

9. Generating a display screen for displaying the contents of a plurality of items related to the medical treatment processes of a plurality of patients; Obtaining change information indicating that at least any one of the contents of a plurality of items related to the medical treatment process of the patient has been changed to a revision; When the display screen is not being displayed and the desktop screen is being displayed, notifying, as the change information, the items of the revised medical treatment process and not notifying the items of the medical treatment process that have not been revised. A method of operating a medical support device having the steps.

10. A function of generating a display screen for displaying the contents of a plurality of items related to the medical treatment processes of a plurality of patients; A function of obtaining change information indicating that at least any one of the contents of a plurality of items related to the medical treatment process of the patient has been changed to a revision; A program for a medical support device that causes a computer to execute a function of notifying, as the change information, the items of the revised medical treatment process and not notifying the items of the medical treatment process that have not been revised when the display screen is not being displayed and the desktop screen is being displayed.

Images