Medical information display device, program, and display method

Abstract

To shorten a time to access diagnosis information on patients to be diagnosed preferentially.SOLUTION: A medical information display device according to an embodiment comprises: an acquisition unit; a mapping unit; and a display control unit. The acquisition unit is configured to acquire patient identification information identifying a patient having occurrence of an event serving as an index of a determination in a diagnosis, and time information representing a time associated with the event from diagnosis information on a plurality of patients. The mapping unit is configured to generate mapping data having an icon about the event mapped to a common time axis identifiably for each patient on the basis of a plurality of pieces of patient identification information and a plurality of pieces of time information. The display control unit is configured to display the mapping data on a display.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] An embodiment of the present invention relates to a medical information display device, a program, and a display method. [Background technology]

[0002] In recent years, there are medical information display devices that implement a medical information integrated viewer that can comprehensively observe the medical information of a patient. With such a medical information display device, a user such as a doctor can comprehensively observe the medical information of a patient displayed on the display of the medical information display device and diagnose and treat the patient. The medical information of a patient includes various types of information such as medical image data representing medical images and electronic medical record data. Specifically, the medical information includes items such as test results of imaging tests, specimen tests, and bacteriological tests, vital signs, information on drug administration, image interpretation reports, and medical record contents. The medical information of a patient is accumulated in a predetermined database every day.

[0003] In a medical information display device that is equipped with such an integrated viewer, a user can, for example, arbitrarily select each item of medical information on a screen displayed on the display, and arrange and display it in a specified area.

[0004] In order to improve the efficiency of medical care performed by each doctor, it is important to be able to quickly access the medical information of patients who should be treated with priority. In the conventional technology, for example, information showing the progress of medical care for each patient is displayed for each patient. At this time, the user checks the information showing the progress for each patient and determines, for example, the priority of checking the medical information of the patients. For this reason, it takes a long time to access the medical information of patients who should be treated with priority. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2016-130984 A Summary of the Invention [Problem to be solved by the invention]

[0006] The problem to be solved by the present invention is to shorten the time required to access medical information of a patient who should be given priority in medical treatment. [Means for solving the problem]

[0007] A medical information display device according to an embodiment includes an acquisition unit, a mapping unit, and a display control unit. The acquisition unit acquires, from medical information of multiple patients, patient identification information for identifying a patient in whom an event that serves as an indicator for judgment in medical treatment has occurred, and time information indicating a time associated with the event. The mapping unit generates mapping data in which icons relating to the events are mapped on a common time axis so as to be identifiable for each patient, based on the multiple pieces of patient identification information and the multiple pieces of time information. The display control unit displays the mapping data on a display. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram showing a medical information system including a medical information display device according to an embodiment. [Diagram 2] FIG. 2 is a block diagram showing a functional configuration of the medical information display device shown in FIG. [Diagram 3] FIG. 3 is a flowchart illustrating an example of the operation of the processing circuit of the medical information display device according to the embodiment. [Figure 4] FIG. 4 is a diagram showing an example of a medical examination screen relating to a heart failure symptom event displayed on the display shown in FIG. [Diagram 5] FIG. 5 is a diagram showing an example of a medical examination screen relating to a surgery schedule event displayed on the display shown in FIG. [Figure 6]FIG. 6 is a diagram showing an example of a medical examination screen relating to an imaging examination event displayed on the display shown in FIG. [Figure 7] FIG. 7 is a diagram showing a display example of mapping data according to the first modification. [Figure 8] FIG. 8 is a diagram showing another display example of the mapping data according to the first modification. [Figure 9] FIG. 9 is a diagram showing another display example of the mapping data according to the first modification. [Figure 10] FIG. 10 is a diagram showing a display example of mapping data according to the second modification. [Figure 11] FIG. 11 is a diagram showing another display example of mapping data according to the second modification. [Figure 12] FIG. 12 is a diagram showing another display example of mapping data according to the second modification. [Figure 13] FIG. 13 is a diagram showing another display example of mapping data according to the second modification. [Figure 14] FIG. 14 is a diagram showing a display example of mapping data according to the third modification. [Figure 15] FIG. 15 is a diagram showing another display example of mapping data according to the third modification. [Figure 16] FIG. 16 is a diagram showing another display example of mapping data according to the third modification. [Figure 17] FIG. 17 is a diagram showing a display example of mapping data according to the fourth modification. [Figure 18] FIG. 18 is a diagram showing another display example of mapping data according to the fourth modification. [Figure 19] FIG. 19 is a diagram showing another display example of mapping data according to the fourth modification. [Figure 20] FIG. 20 is a diagram showing an example of a medical examination screen according to another embodiment. [Figure 21] FIG. 21 is a diagram illustrating an example of a patient details screen showing details of medical information of a patient according to another embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, embodiments will be described with reference to the drawings.

[0010] FIG. 1 is a block diagram showing an example of an environment in which a medical information display device 1 according to the present embodiment is used. The medical information display device 1 shown in FIG. 1 is, for example, a device capable of observing medical information in an integrated manner. For example, an integrated viewer is implemented in the medical information display device 1. The integrated viewer is an application that presents medical information to a user in an integrated manner. The integrated viewer may adopt any implementation form, such as a Web application, a fat client application, or a thin client application. The medical information display device 1 is connected to a hospital information system (HIS: Hospital Information Systems) 2, a radiology information system (RIS: Radiology Information Systems) 3, a medical image diagnostic device 4, a medical image management system (PACS: Picture Archiving and Communication Systems) 5, and a data warehouse (DWH: Data WareHouse) 6 so as to be able to communicate with each other via an intra-hospital network such as a LAN (Local Area Network).

[0011] 1, the HIS2 includes, for example, an electronic medical record system that manages information related to electronic medical records. Information related to electronic medical records includes, for example, patient information and medical treatment information. Patient information is information specific to a patient, and includes, for example, a patient ID, a patient name, a sex, and an age.

[0012] The medical information is information that a medical professional has come to know about the patient's physical condition, medical condition, treatment, etc., during the course of medical treatment. The medical information includes, for example, image information, examination history information, electrocardiogram information, vital sign information, medication history information, report information, chart information, and nursing record information. The image information is, for example, information indicating the location of a medical image acquired by photographing a patient. The image information includes, for example, information indicating the location of a medical image file (described later) generated by the medical image diagnostic device 4 as a result of an examination being performed. The examination history information is, for example, information indicating the history of examination results acquired as a result of specimen examination, bacterial examination, etc. being performed on the patient. The electrocardiogram information is, for example, information regarding an electrocardiogram waveform measured from the patient. The vital sign information is, for example, basic information related to the life of the patient. The vital sign information includes, for example, pulse rate, respiratory rate, oxygen concentration, body temperature, blood pressure, and consciousness level. The medication history information is, for example, information indicating the history of the amount of medicine administered to the patient. The report information is, for example, information compiled by a radiologist in the radiology department who interprets medical images such as X-ray images, CT images, MRI images, and ultrasound images in response to an examination request from a medical doctor in a clinical department, and summarizes the patient's condition and disease. The report information includes, for example, image interpretation report information that represents an image interpretation report created by the image interpretation doctor with reference to a medical image file stored in the PACS 5. Since the report information is generally stored in the PACS 5, the electronic medical record system can display the report information by reading the report information from the PACS 5.

[0013] The medical record information is, for example, information input into an electronic medical record by a doctor, etc. The medical record information includes, for example, a medical record at the time of hospitalization, a patient's medical history, a drug prescription history, and the like.

[0014] The nursing record information is, for example, information input into an electronic medical record by a nurse, etc. The nursing record information includes nursing records at the time of hospitalization, etc.

[0015] The information on the electronic medical record includes, for example, examination implementation information. The examination implementation information is generated by the medical image diagnostic device 4 that performed the examination according to the examination order information. The examination implementation information is information representing the examination performed in the medical image diagnostic device 4. The examination implementation information includes an order number, an examination UID (Unique ID), a patient ID, a modality type, an imaging region, and imaging conditions. The examination UID is an identifier that can uniquely identify an examination. The modality type indicates the modality used for imaging. The modality types include, for example, "X-ray computed tomography device," "X-ray diagnostic device," "magnetic resonance imaging device," and "ultrasound diagnostic device." The imaging region corresponds to the examination region included in the examination order information. The imaging region includes, for example, the abdomen, the brain, and the chest. The imaging conditions include the body position, the imaging direction, and the presence or absence of use of a contrast agent.

[0016] The HIS 2 also includes, for example, an order system that manages reservation information, order information, etc. The HIS 2 may be configured such that an electronic medical record system includes an ordering system.

[0017] The reservation information includes, for example, information about consultation appointments and examination appointments. The information about consultation appointments includes, for example, consultation date, consultation time, reception number, requesting doctor, and requesting department. The information about examination appointments includes, for example, examination date, examination time, and reception number. The order information is, for example, information about an order requested by a medical practitioner, and includes order information about an imaging test, a specimen test, a physiological test, a prescription, and medication. When the order information is examination order information requesting an imaging test, the examination order information includes, for example, an order number that can identify the examination, a patient ID, an examination type, an examination site, and requester information. The order number is a number issued when the examination order information is input, and is, for example, an identifier for uniquely identifying the examination order information within one hospital. The examination type includes X-ray examination, CT (Computed Tomography) examination, MR (Magnetic Resonance) examination, and RI (Radio Isotope) examination. The examination site includes, for example, the abdomen, the brain, and the chest. The requester information includes the name of the medical department, the name of the doctor in charge, etc. Information regarding the examination reservation is linked to the order information.

[0018] The RIS3 is a system that manages examination reservation information related to radiological examination work. The RIS3 adds various setting information to examination order information input by a medical practitioner in an order system included in the HIS2, for example, and accumulates the information, and manages the accumulated information as examination reservation information. The RIS3 may add various setting information to the examination order information using an irradiation record that records various setting information set in the medical image diagnostic device 4 during past examinations. The RIS3 transmits an examination order to the medical image diagnostic device 4 according to the examination reservation information. The RIS3 also transmits examination implementation information generated by the medical image diagnostic device 4 as a result of the examination being performed to an electronic medical record system included in the HIS2.

[0019] The medical image diagnostic apparatus 4 is an apparatus that performs an examination by photographing a patient, etc. The medical image diagnostic apparatus 4 includes, for example, an X-ray computed tomography apparatus, an X-ray diagnostic apparatus, a magnetic resonance imaging apparatus, a nuclear medicine diagnostic apparatus, and an ultrasonic diagnostic apparatus. The medical image diagnostic apparatus 4 performs an examination based on examination reservation information transmitted from, for example, the RIS 3. The medical image diagnostic apparatus 4 generates examination implementation information and transmits it to the RIS 3.

[0020] Furthermore, the medical image diagnostic device 4 generates medical image data by carrying out an examination. The medical image data is, for example, X-ray CT image data, X-ray image data, MRI image data, nuclear medicine image data, and ultrasound image data. The medical image diagnostic device 4 generates a medical image file by converting the generated medical image data into a format that complies with, for example, the DICOM (Digital Imaging and Communication in Medicine) standard. The medical image file is, for example, a file in a format that complies with the DICOM standard. The medical image diagnostic device 4 transmits the generated medical image file to the PACS 5.

[0021] The PACS 5 is a system that manages various medical image files. The PACS 5 stores, for example, medical image files transmitted from the medical image diagnostic apparatus 4. The PACS 5 may store report information attached to the medical image files, or report information for examinations related to multiple medical image files.

[0022] The DWH6 is a database system that collectively accumulates, for example, information generated in medical and nursing care institutions, so-called medical big data. The DWH6 is realized, for example, by a general server device. As shown in Fig. 1, the DWH6 has, for example, a processing circuit 61, a memory 62, and a communication interface 63. The processing circuit 61, the memory 62, and the communication interface 63 are connected to each other so as to be able to communicate with each other, for example, via a bus.

[0023] The processing circuitry 61 is a processor that functions as the core of the DWH 6. The processing circuitry 61 executes a program stored in the memory 62 or the like, thereby realizing, for example, a collection function 611 and a registration function 612 corresponding to the program.

[0024] The collection function 611 is a function for collecting desired information from the HIS2, the RIS3, the medical image diagnostic apparatus 4, and the PACS5. Specifically, in the collection function 611, the processing circuitry 61 collects, for example, preset information from the HIS2, the RIS3, the medical image diagnostic apparatus 4, and the PACS5 at a preset cycle. The processing circuitry 61 may collect desired information from the HIS2, the RIS3, the medical image diagnostic apparatus 4, and the PACS5 using a machine learning model stored in advance. As a result, for example, information on the electronic medical record is collected from the HIS2, examination reservation information is collected from the RIS3, and medical image files are collected from the medical image diagnostic apparatus 4 or the medical image management system 5.

[0025] The processing circuitry 61 may collect various pieces of information from the HIS 2, the RIS 3, the medical image diagnostic apparatus 4, and the PACS 5, and then obtain desired information from the collected information.

[0026] The registration function 612 is a function for storing information collected by the collection function 611 in the memory 62. Specifically, in the registration function 612, the processing circuit 61 stores the medical information collected from the HIS2 in the memory 62 in accordance with, for example, a preset rule. The preset rule is, for example, an order using event dates and times associated with medical events such as outpatient visits for each patient, surgery, imaging tests, specimen tests, bacterial tests, electrocardiogram measurements, vital sign measurements, drug administration, report creation, and chart entry. The event dates and times are, for example, the dates and times when a medical event occurs, or the dates and times when a medical event is scheduled. The event dates and times include, for example, the dates and times when an imaging test is performed, the dates and times when a specimen test is performed, the dates and times when an electrocardiogram waveform is measured, the dates and times when a vital sign is measured, the dates and times when a drug is administered, the dates and times when a report is created, and the dates and times when a chart is entered. As a result, the collected medical information is stored in the memory 62 as log information 621 in, for example, the order of event dates and times.

[0027] The memory 62 is a storage device such as a hard disk drive (HDD), a solid state drive (SSD), or an integrated circuit storage device that stores various information. The memory 62 may also be a drive device that reads and writes various information to and from a portable storage medium such as a CD-ROM drive, a DVD drive, or a flash memory. The memory 62 stores, for example, a control program for implementing a collection function 611 and a registration function 612. The program may be distributed by being stored in a non-transient storage medium, and may be read from the non-transient storage medium and installed in the memory 62. The memory 62 stores, for example, log information 621.

[0028] The communication interface 63 performs data communication with the medical information display device 1, the HIS 2, the RIS 3, the medical image diagnostic device 4, and the PACS 5, which are connected via the hospital network. Any standard may be used for communication with the medical information display device 1, the HIS 2, the RIS 3, the medical image diagnostic device 4, and the PACS 5, and examples of such standards include HL7 (Health Level 7), DICOM, or both.

[0029] Next, details of the medical information display device 1 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing the functional configuration of the medical information display device 1 shown in Fig. 1.

[0030] 2 includes a processing circuit 11, an input interface 12, a display 13, a memory 14, and a communication interface 15. The processing circuit 11, the input interface 12, the display 13, the memory 14, and the communication interface 15 are communicatively connected to each other via a bus, for example.

[0031] The processing circuitry 11 is a processor that functions as the core of the medical information display device 1. The medical information display device 1 executes a control program stored in, for example, the memory 14, to realize a function corresponding to the program.

[0032] The input interface 12 is realized by, for example, a mouse, a keyboard, and a touch panel where instructions are input by touching an operation surface. The input interface 12 receives, for example, a display instruction from an operator. The input interface 12 converts the display instruction from the operator into an electrical signal and outputs the electrical signal to a processing circuit. A display instruction is, for example, specifying a button displayed on the screen, specifying a character string from a pull-down menu, and the like.

[0033] The display 13 displays various information for the user to perform various tasks. As the display 13, for example, a CRT display, a liquid crystal display, an organic EL display, an LED display, a plasma display, or any other display known in the art can be appropriately used.

[0034] The memory 14 is a storage device such as a hard disk drive (HDD), a solid state drive (SSD), or an integrated circuit storage device that stores various information. The memory 14 may also be a drive device that reads and writes various information from and to a portable storage medium such as a CD-ROM drive, a DVD drive, or a flash memory.

[0035] The memory 14 stores acquisition conditions for acquiring event information related to events that serve as indicators for judgment in medical treatment. The event information is, for example, information that represents any record related to a patient's medical treatment. The event information includes at least one of each item of the medical treatment information. Note that the event information includes, for example, a fact that has been determined as a result of analysis of a specific character string or numerical value contained in the medical treatment information that a notification (warning) should be given to the user. The events also include events in a medical treatment workflow that is predefined for medical treatment work, and events detected from the patient's medical treatment information based on empirical rules regarding medical treatment.

[0036] The acquisition conditions are based on, for example, predetermined rules. The predetermined rules include, for example, rules defined by medical events occurring in a hospital. The predetermined rules include, for example, rules defined in official guidelines. Furthermore, the predetermined rules include, for example, rules set by a medical facility or an individual doctor. Furthermore, the acquisition conditions include, for example, an event type that indicates the type of event.

[0037] The acquisition conditions may be defined based on artificial intelligence (AI) technology or the like.

[0038] The communication interface 15 performs data communication with the HIS 2, RIS 3, medical image diagnostic device 4, PACS 5, and DWH 6, which are connected via the hospital network. Any standard may be used for communication with the HIS 2, RIS 3, medical image diagnostic device 4, PACS 5, and DWH 6, and examples of such standards include HL7, DICOM, or both.

[0039] The processing circuitry 11 according to this embodiment includes an acquisition function 111 , a mapping function 113 , a display control function 115 , and a system control function 117 .

[0040] The acquisition function 111 is a function for acquiring, from the medical information of a plurality of patients, patient identification information for identifying a patient in whom an event that serves as an index for judgment in medical treatment has occurred, and time information representing the time associated with the event. The time information is expressed, for example, by a year, a month, a date, or a time and date. By executing the acquisition function 111, the processing circuit 11 reads out acquisition conditions stored in the memory 14 based on, for example, an input via the input interface 12, and acquires a plurality of event information related to events for each patient from the log information 621 stored in the memory 62 of the DWH 6 based on the read acquisition conditions. Each record included in each of the acquired plurality of event information has, as items, for example, an event type, a patient ID (patient identification information), an event date and time (time information) associated with the event represented by the event information, and event-related information related to the event. The patient identification information may include a patient name.

[0041] The mapping function 113 is a function for mapping event information. By executing the mapping function 113, the processing circuit 11 generates mapping data in which one or more icons related to events are mapped on a common time axis so as to be identifiable for each patient, based on the multiple pieces of patient identification information and multiple pieces of time information acquired by the acquisition function 111. For example, a patient ID or a patient name for identifying a patient corresponding to the event may be displayed on the icon related to the event. Also, an event name for identifying the event may be displayed on the icon related to the event. Note that the symbols mapped to the mapping data are not limited to icons, and may be symbols capable of identifying an event by its shape.

[0042] The display control function 115 is a function for displaying mapping data on a display. By executing the display control function 115, the processing circuitry 11 displays, for example, the mapping data generated by the mapping function 113 on the display 13. At this time, the processing circuitry 11 may display event-related information related to events for each patient together with the mapping data.

[0043] The system control function 117 is a function that controls basic operations such as input / output and communication of the medical information display device 1. When the system control function 117 is executed, the processing circuitry 11 receives various requests via the input interface 12. The processing circuitry 11 executes various functions in response to the received various requests.

[0044] The acquisition function 111, mapping function 113, display control function 115, and system control function 117 may be incorporated as a control program, or the processing circuitry 11 itself may incorporate dedicated hardware circuits capable of executing each function.

[0045] Next, various operations of the medical information display device 1 according to this embodiment will be described with reference to the drawings.

[0046] FIG. 3 is a flowchart showing an example of the operation of the processing circuit 11 of the medical information display device 1 according to this embodiment. In the following description, the processing circuit 11 accepts the designation of the event type via the input interface 12. At this time, the processing circuit 11 accepts the designation of the event type by, for example, displaying a character string representing candidates of the event type in a pull-down manner on the display 13. Then, the processing circuit 11 accepts the designation of the event type "heart failure symptom event". In addition, the acquisition condition for acquiring the event information (heart failure symptom event information) representing this heart failure symptom event includes, for example, "elements related to biological information acquired from the patient". The elements related to biological information acquired from the patient include, for example, a condition related to the urine volume "urine volume collected per day is 400 ml or less". In addition, the acquisition condition includes a time element (for example, a period, etc.) and an element representing the attributes of the patient (for example, a doctor in charge, a medical department, and a ward, etc.). An example of a time element is "the period from April 10, 2017, when the event occurred, to April 27, 2017." An example of an element representing a patient attribute is "patients under the care of Doctor A." In this case, the patients under the care of Doctor A are those with patient IDs "00000001," "00000002," "00000003," "00000004," and "00000005."

[0047] For a patient with patient ID "00000001", the date and time that meets the acquisition condition "urine volume collected per day is 400 ml or less" is "April 24, 2017", "April 25, 2017", and "April 26, 2017", and the urine volume collected at each date and time is "400 ml", "300 ml", and "400 ml". For a patient with patient ID "00000002", the date and time that meets the acquisition condition "urine volume collected per day is 400 ml or less" is "April 15, 2017", and the urine volume collected at that date and time is "400 ml". For a patient with patient ID "00000003", the date and time that meets the acquisition condition "urine volume collected per day is 400 ml or less" is "April 10, 2017", and the urine volume collected at that date and time is "400 ml". For the patient with patient ID "00000004", the date and time that satisfies the acquisition condition "urine volume collected per day is 400 ml or less" is "April 14, 2017", and the volume of urine collected at that date and time is "400 ml". For the patient with patient ID "00000005", the date and time that satisfies the acquisition condition "urine volume collected per day is 400 ml or less" is "April 18, 2017", and the volume of urine collected at that date and time is "400 ml".

[0048] In addition, the elements related to the biological information acquired from the patient, which are included in the acquisition conditions related to the heart failure symptom event, may include, in addition to the condition related to the urine volume "urine volume collected per day is 400 ml or less", a condition related to weight gain or loss "weight gain of 3 kg or more in 2 days" or a condition related to blood components "BNP (Brain Natriuretic peptide) is 200 pg / ml or more". Furthermore, the acquisition conditions related to the heart failure symptom event may include a condition related to the contents of the nursing record, etc.

[0049] The event type is not limited to a "heart failure symptom event". An example of the event type is a "renal function deterioration event". In this case, the elements related to the biological information acquired from the patient included in the acquisition conditions related to the renal function deterioration event include, for example, a condition related to blood components, "serum creatinine increases by 0.3 mg / dl or more within 48 hours".

[0050] When the processing circuitry 11 receives the designation of the acquisition condition, it reads out the designated acquisition condition from the memory 14 (step SA1). The processing circuitry 11 reads out, for example, the acquisition condition for acquiring a heart failure symptom event from the memory 14.

[0051] The processing circuitry 11 acquires multiple pieces of event information based on the read acquisition conditions (step SA2). For example, the processing circuitry 11 acquires heart failure symptom event information for each patient from information representing a record of a daily urine volume included in the log information 621 stored in the memory 62 of the DWH 6 based on the read acquisition conditions for acquiring a heart failure symptom event. In other words, the processing circuitry 11 acquires patient identification information for identifying a patient in which a heart failure symptom event has occurred, and time information representing a time associated with the heart failure symptom event.

[0052] Specifically, the processing circuit 11 determines that a heart failure symptom event has occurred for a patient with patient ID "00000001" because the urine volumes collected on date and time "April 24, 2017", "April 25, 2017", and "April 26, 2017" are "400 ml", "300 ml", and "400 ml", respectively, and acquires necessary information from the log information 621. Also, the processing circuit 11 determines that a heart failure symptom event has occurred for a patient with patient ID "00000002" because the urine volume collected on date and time "April 15, 2017" is "400 ml", and acquires necessary information from the log information 621. The processing circuit 11 also determines that a heart failure symptom event has occurred in a patient with patient ID "00000003" because the amount of urine collected on date and time "April 10, 2017" is "400 ml", and acquires necessary information from the log information 621. The processing circuit 11 also determines that a heart failure symptom event has occurred in a patient with patient ID "00000004" because the amount of urine collected on date and time "April 14, 2017" is "400 ml", and acquires necessary information from the log information 621. The processing circuit 11 also determines that a heart failure symptom event has occurred in a patient with patient ID "00000005" because the amount of urine collected on date and time "April 18, 2017" is "400 ml", and acquires necessary information from the log information 621.

[0053] At this time, the acquired heart failure symptom event information includes a record having an event type "heart failure symptom event", a patient ID "00000001", an event date and time "April 24, 2017", and event related information related to the heart failure symptom event (heart failure symptom event related information). The heart failure symptom event related information is, for example, information indicating a change in daily urinary volume during a predetermined period acquired for a patient with a patient ID "00000001". The heart failure symptom event information also includes a record having an event type "heart failure symptom event", a patient ID "00000001", an event date and time "April 25, 2017", and heart failure symptom event related information. The heart failure symptom event information also includes a record having an event type "heart failure symptom event", a patient ID "00000001", an event date and time "April 26, 2017", and heart failure symptom event related information. The heart failure symptom event related information for the three records with the patient ID "00000001" is identical.

[0054] The heart failure symptom event information also includes a record having an event type "heart failure symptom event", a patient ID "00000002", an event date and time "April 15, 2017", and heart failure symptom event related information. The heart failure symptom event related information is, for example, information indicating a change in daily urine volume during a predetermined period acquired for a patient with patient ID "00000002". The heart failure symptom event information also includes a record having an event type "heart failure symptom event", a patient ID "00000003", an event date and time "April 10, 2017", and heart failure symptom event related information. The heart failure symptom event related information includes, for example, a record having information indicating a change in daily urine volume during a predetermined period acquired for a patient with patient ID "00000003".

[0055] The heart failure symptom event information also includes a record having an event type "heart failure symptom event", a patient ID "00000004", an event date and time "April 14, 2017", and heart failure symptom event related information. The heart failure symptom event related information is, for example, information indicating a change in daily urine volume during a predetermined period acquired for a patient with patient ID "00000004". The heart failure symptom event information also includes a record having an event type "heart failure symptom event", a patient ID "00000005", an event date and time "April 18, 2017", and heart failure symptom event related information. The heart failure symptom event related information is, for example, information indicating a change in daily urine volume during a predetermined period acquired for a patient with patient ID "00000005".

[0056] The processing circuitry 11 maps the acquired event information across the acquired patients (step SA3). Specifically, the processing circuitry 11 generates mapping data in which one or more icons related to heart failure symptom events are mapped on a common time axis so as to be identifiable for each patient, based on the acquired patient identification information and time information.

[0057] The processing circuit 11 displays the event-related information for each patient's event together with the mapping data (step SA4). Fig. 4 is a diagram showing an example of a medical examination screen for a heart failure symptom event displayed on the display 13 shown in Fig. 2. The medical examination screen shown in Fig. 4 includes a mapping area R41 having mapping data and an event-related information area R42 having at least one event-related information.

[0058] The mapping area R41 includes icons I41a, I41b, I41c, I42, I43, I44, and I45 representing each patient. As shown in Fig. 4, each icon included in the mapping area R41 is displayed with a different color for each patient. Each icon may be displayed with the patient's name.

[0059] Icon I41a indicates that a heart failure symptom event occurred at the event date and time "April 24, 2017" for a patient with patient ID "00000001". Icon I41b indicates that a heart failure symptom event occurred at the event date and time "April 25, 2017" for a patient with patient ID "00000001". Icon I41c indicates that a heart failure symptom event occurred at the event date and time "April 26, 2017" for a patient with patient ID "00000001". Icon I42 indicates that a heart failure symptom event occurred at the event date and time "April 15, 2017" for a patient with patient ID "00000002". Icon I43 indicates that a heart failure symptom event occurred at the event date and time "April 10, 2017" for a patient with patient ID "00000003". Icon I44 represents the fact that a heart failure symptom event occurred for a patient with patient ID "00000004" on the event date and time "April 14, 2017."

[0060] In addition, a linear indicator L1 is displayed in the mapping area R41. The indicator L1 indicates an arbitrary date and time on the time axis included in the mapping area R41. The position where the indicator L1 is displayed can be arbitrarily changed by a user's instruction via the input interface 12, such as a click operation or cursor movement. The same applies to the indicators displayed in the subsequent mapping areas.

[0061] The event-related information region R42 includes regions R421, R422, R423, R424, and R425 that represent event-related information related to the event information for each patient. A scroll bar SC1 is provided at the right end of the event-related information region R42. The display range of the event-related information region R42 can be changed by a user's instruction to the scroll bar (scrolling operation). In the event-related information region R42 shown in FIG. 4, parts of the regions R423 and R425 are not displayed on the display 13.

[0062] In the region R421, information related to heart failure symptom events is displayed for a patient with a patient ID of "00000001". In the region R421, for example, it is displayed that the name of the patient with the patient ID of "00000001" is "Shinju Taro" and the gender is "Male". In addition, in the region R421, the transition of the amount of urine collected from April 10, 2017 to April 27, 2017 for the patient with the patient ID of "00000001" is displayed in a graph format. In addition, the region R421 includes a button B41. When the user designates the button B41 via the input interface 12, the processing circuit 11 displays details of the medical information of the patient with the patient ID of "00000001". Therefore, the user can access details of the medical information of the patient with the patient ID of "00000001" by designating the button B41. When the user designates an icon mapped in the mapping area, the processing circuitry 11 may display a detailed screen of the medical information of the patient associated with the icon. This also applies to the following cases.

[0063] Region R421 includes marks M41a, M41b, and M41c that highlight the time when a heart failure indication event occurred for a patient with patient ID "00000001." Mark M41a indicates that a heart failure indication event occurred on date and time "April 24, 2017," and corresponds to icon I41a. Mark M41b indicates that a heart failure indication event occurred on date and time "April 25, 2017," and corresponds to icon I41b. Mark M41c indicates that a heart failure indication event occurred on date and time "April 26, 2017," and corresponds to icon I41c.

[0064] Note that, although the region R421 displays a summary of multiple events for a patient with the patient ID "00000001", this is not limiting. For example, the event-related information region R42 may include three regions each including a mark M41a, a mark M41b, and a mark M41c.

[0065] In the area R422, information related to heart failure symptom events is displayed for the patient with the patient ID "00000002". For example, in the area R422, it is displayed that the name of the patient with the patient ID "00000002" is "Shinju Hanako" and the gender is "Female". In addition, in the area R422, the transition of the amount of urine collected from April 10, 2017 to April 27, 2017 for the patient with the patient ID "00000002" is displayed in a graph format. In addition, the area R422 includes a button B42. By designating the button B42, the user can access detailed medical information of the patient with the patient ID "00000002".

[0066] Region R422 includes mark M42 that highlights the time when a heart failure indication event occurred for a patient with patient ID "00000002." Mark M42 indicates that a heart failure indication event occurred on the date and time "April 15, 2017," and corresponds to icon I42.

[0067] In the area R424, information related to heart failure symptom events is displayed for the patient with the patient ID "00000004". For example, in the area R424, it is displayed that the name of the patient with the patient ID "00000004" is "Shinju Ichiro" and the gender is "Male". In addition, in the area R424, the transition of the amount of urine collected from April 10, 2017 to April 27, 2017 for the patient with the patient ID "00000004" is displayed in a graph format. In addition, the area R424 includes a button B44. By designating the button B44, the user can access detailed medical information of the patient with the patient ID "00000004".

[0068] Region R424 includes a mark M44 that highlights the time when a heart failure indication event occurred for a patient with patient ID "00000004." Mark M44 indicates that a heart failure indication event occurred on the date and time "April 14, 2017," and corresponds to icon I44.

[0069] In the region R423, information related to heart failure symptom events is displayed for a patient with a patient ID of "00000003". For example, in the region R423, it is displayed that the name of the patient with the patient ID of "00000003" is "Shinju Jiro" and the gender is "Male". In addition, in the region R423, the transition of the amount of urine collected from April 10, 2017 to April 27, 2017 for the patient with the patient ID of "00000003" is displayed in a graph format. In addition, the region R423 includes a button B43. By designating the button B43, the user can access detailed medical information of the patient with the patient ID of "00000003".

[0070] Region R423 includes a mark M43 that highlights the time when a heart failure indication event occurred for a patient with patient ID "00000003." Mark M43 indicates that a heart failure indication event occurred on the date and time "April 10, 2017," and corresponds to icon I43.

[0071] In the region R425, information related to heart failure symptom events is displayed for the patient with the patient ID "00000005". For example, in the region R425, it is displayed that the name of the patient with the patient ID "00000005" is "Shinju Saburo" and the gender is "Male". In addition, in the region R425, the transition of the amount of urine collected from April 10, 2017 to April 27, 2017 for the patient with the patient ID "00000005" is displayed in a graph format. In addition, the region R425 includes a button B45. By designating the button B45, the user can access detailed medical information of the patient with the patient ID "00000005".

[0072] Region R425 includes mark M45 that highlights the time when a heart failure symptom event occurred for a patient with patient ID "00000005." Mark M45 indicates that a heart failure symptom event occurred on the date and time "April 18, 2017," and corresponds to icon I45.

[0073] According to the medical examination screen shown in Fig. 4 described above, for example, a user visually checking the mapping data displayed in the mapping area R41 can see at a glance which patient has a concentration of events and when the events are concentrated. Specifically, for example, in Fig. 4, a user visually checking the mapping area R41 can see at a glance that heart failure symptom events occurred for three consecutive days on the event dates and times "April 24, 2017", "April 25, 2017", and "April 26, 2017" for a patient with patient ID "00000001".

[0074] Then, a user who visually recognizes the mapping region R41 can determine that a patient with a patient ID of "00000001" needs to be treated with priority, and can access detailed medical information about the patient. At this time, the user does not need to check detailed medical information about patients other than the patient who should be treated with priority, and unnecessary screen transitions for checking detailed medical information about patients can be reduced. In other words, the trial and error time required to access detailed medical information about a patient who should be treated with priority can be shortened.

[0075] According to the first embodiment, the processing circuitry 11 included in the medical information display device 1 acquires event information for each patient based on a predetermined acquisition condition. Based on the acquired event information, the processing circuitry 11 generates mapping data in which events represented by the event information are mapped on a common time axis so as to be identifiable for each patient. Specifically, the processing circuitry 11 generates mapping data in which one or more icons related to events are mapped on a common time axis so as to be identifiable for each patient based on a plurality of pieces of patient identification information and a plurality of pieces of time information.

[0076] This allows a user who sees the mapping data display to see at a glance, for example, which patients have a high concentration of events and when the events are concentrated. In addition, the user does not need to check detailed medical information on patients other than the patient who should be given priority treatment, for example, and can reduce the trial and error time required to access detailed medical information on the patient who should be given priority treatment.

[0077] In addition, the processing circuitry 11 displays event-related information related to the event together with the mapping data, which allows a user who visually views the event-related information to recognize the content of the event without checking the details of the patient's medical information.

[0078] The mapping data of events displayed by the processing circuitry 11 included in the medical information display device 1 is not limited to those notifying the patient's medical condition, such as a heart failure symptom event. The mapping data of events displayed by the processing circuitry 11 may be, for example, related to events in a medical workflow. Events in a medical workflow include, for example, a surgery schedule event indicating a surgery schedule, an examination result event indicating an examination result, and an outpatient visit event indicating a scheduled outpatient visit. Below, the display modes when the processing circuitry 11 displays a surgery schedule event and an imaging examination event indicating the results of an imaging examination included in an examination result event will be described.

[0079] First, a display mode in which the processing circuit 11 displays mapping data on the display 13 for a scheduled surgery event will be described. At this time, the processing circuit 11 performs the process shown in the flowchart of FIG. 3. In the following description, the processing circuit 11 accepts the designation of the event type "scheduled surgery event" via the input interface 12. In addition, the acquisition condition for acquiring the event information (scheduled surgery event information) representing this scheduled surgery event includes, for example, "medical information recorded as scheduled surgery." In addition, the acquisition condition includes a time element (for example, a period, etc.) and an element representing the attributes of the patient (for example, the doctor in charge, the medical department, and the ward, etc.). The time element is, for example, "the period from April 10, 2017 to April 27, 2017 when the event date and time occurs." In addition, the element representing the attributes of the patient is, for example, a patient in charge of Doctor A. In this case, the patients under the care of Doctor A are assumed to include patients with patient IDs "00000001," "00000002," "00000003," "00000004," and "00000005."

[0080] When the processing circuitry 11 receives the designation of the acquisition condition, it reads out the designated acquisition condition from the memory 14 (step SA1). The processing circuitry 11 reads out, for example, the acquisition condition for acquiring a surgery scheduled event from the memory 14.

[0081] The processing circuit 11 acquires multiple pieces of event information based on the read acquisition conditions (step SA2). For example, the processing circuit 11 acquires surgery schedule event information for each patient from medical care information recorded as surgery schedule included in the log information 621 stored in the memory 62 of the DWH 6 based on the read acquisition conditions for acquiring the surgery schedule event. In other words, the processing circuit 11 acquires patient identification information that identifies the patient in which the surgery schedule event occurred and time information that indicates the time associated with the surgery schedule event.

[0082] At this time, the acquired scheduled surgery event information includes a record having an event type "scheduled surgery event", a patient ID "00000001", an event date and time "April 14, 2017", and event related information related to the scheduled surgery event (scheduled surgery event related information), etc. The scheduled surgery event related information is, for example, disease name "ventricular septal defect", age (months) "3 months", date of admission "April 1, 2017", scheduled surgery date "April 14, 2017", surgical procedure "BT shunt surgery", and surgeon "test physician". The scheduled surgery event information also includes a record having an event type "scheduled surgery event", a patient ID "00000002", an event date and time "April 14, 2017", and scheduled surgery event related information, etc. The planned surgery event related information is, for example, the disease name "Tetraminal Fallot's disease", age (months) "3 years old", date of admission "4 / 8 / 2017", planned surgery date "4 / 14 / 2017", surgical procedure "BT shunt procedure", and surgeon "test physician". The planned surgery event information also includes a record having an event type "scheduled surgery event", a patient ID "00000003", event date and time "April 21, 2017", and planned surgery event related information. The planned surgery event related information is, for example, the disease name "Ventricular septal defect", age (months) "4 years old", date of admission "4 / 5 / 2017", planned surgery date "4 / 21 / 2017", surgical procedure "BT shunt procedure", and surgeon "test physician". The scheduled surgery event information also includes a record having an event type "scheduled surgery event", a patient ID "00000004", an event date and time "April 21, 2017", and other information related to the scheduled surgery event. The scheduled surgery event related information is, for example, disease name "Hypoplastic Left Heart Syndrome", age (months) "5 years old", date of admission "April 4, 2017", scheduled surgery date "April 21, 2017", surgical procedure "Fontan surgery", and surgeon "Test physician". The scheduled surgery event information also includes a record having an event type "scheduled surgery event", a patient ID "00000005", an event date and time "April 26, 2017", and other information related to the scheduled surgery event. Examples of information related to the scheduled surgery event include the disease name "Ventricular Septal Defect", age (in months) "2 years old", date of admission "4 / 6 / 2017", scheduled surgery date "4 / 26 / 2017", surgical procedure "BT shunt surgery", and surgeon "Test Physician".

[0083] The processing circuitry 11 maps the acquired event information across the acquired patients (step SA3). Specifically, the processing circuitry 11 generates mapping data in which one or more icons related to surgery schedule events are mapped on a common time axis so as to be identifiable for each patient, based on the acquired patient identification information and time information.

[0084] The processing circuit 11 displays the event-related information for each patient's event together with the mapping data (step SA4). Figure 5 is a diagram showing an example of a medical examination screen for a scheduled surgery event displayed on the display 13 shown in Figure 2. The medical examination screen shown in Figure 5 includes a mapping area R51 having mapping data and an event-related information area R52 having at least one event-related information.

[0085] The mapping area R51 includes icons I51, I52, I53, I54, and I55 representing each patient. As shown in Fig. 5, each icon included in the mapping area R51 is displayed with a different color for each patient. Each icon may be displayed with the patient's name.

[0086] Icon I51 represents the fact that surgery is scheduled for the event date and time "April 14, 2017" for a patient with patient ID "00000001". Icon I52 represents the fact that surgery is scheduled for the event date and time "April 14, 2017" for a patient with patient ID "00000002". Icon I53 represents the fact that surgery is scheduled for the event date and time "April 21, 2017" for a patient with patient ID "00000003". Icon I54 represents the fact that surgery is scheduled for the event date and time "April 21, 2017" for a patient with patient ID "00000004". Icon I55 represents the fact that surgery is scheduled for the event date and time "April 26, 2017" for a patient with patient ID "00000005".

[0087] The event-related information region R52 includes regions R521, R522, R523, R524, and R525 that represent event-related information related to the event information for each patient. A scroll bar SC2 is provided at the right end of the event-related information region R52. The display range of the event-related information region R52 can be changed by a user's instruction to scroll bar SC2. In the event-related information region R52 shown in FIG. 5, parts of the regions R523 and R525 are not displayed on the display 13.

[0088] In the region R521, surgery schedule event related information is displayed for the patient with the patient ID "00000001". In the region R521, for example, it is displayed that the name of the patient with the patient ID "00000001" is "Shinju Taro" and the gender is "Male". In addition, in the region R521, for the patient with the patient ID "00000001", the disease name "Ventricular Septal Defect", the age (months) "3 months", the date of admission "2017 / 4 / 1", the scheduled surgery date "2017 / 4 / 14", the surgical procedure "BT Shunt Surgery", and the surgeon "Test Doctor" are displayed. In addition, the region R521 includes a button B51. When the user designates the button B51 via the input interface 12, the processing circuit 11 displays the details of the medical information of the patient with the patient ID "00000001". Therefore, by selecting button B51, the user can access detailed medical information of the patient with patient ID "00000001."

[0089] In the region R522, surgery scheduled event related information is displayed for the patient with the patient ID "00000002". For example, in the region R522, for the patient with the patient ID "00000002", the name "Heartbeat Hanako" and the gender "Female" are displayed. In addition, in the region R522, the disease name "Tetraminal Fallot's syndrome", the age (months) "3 years old", the date of admission "2017 / 4 / 8", the scheduled surgery date "2017 / 4 / 14", the surgical procedure "BT shunt surgery", and the surgeon "Test Doctor" are displayed. In addition, the region R522 includes a button B52. By designating the button B52, the user can access the detailed medical information of the patient with the patient ID "00000002".

[0090] In the region R524, surgery schedule event related information is displayed for the patient with the patient ID "00000004". For example, in the region R524, it is displayed that the name of the patient with the patient ID "00000004" is "Shinju Ichiro" and the gender is "Male". In addition, in the region R524, for the patient with the patient ID "00000004", the disease name "Hypoplastic Left Heart Syndrome", age (months) "5 years old", admission date "4 / 4 / 2017", scheduled surgery date "4 / 21 / 2017", surgical procedure "Fontan surgery", and surgeon "Test Doctor" are displayed. In addition, the region R524 includes a button B54. By designating the button B54, the user can access the details of the medical information of the patient with the patient ID "00000004".

[0091] In the region R523, surgery schedule event related information is displayed for the patient with the patient ID "00000003". In the region R523, for example, it is displayed that the name of the patient with the patient ID "00000003" is "Shinju Jiro" and the gender is "Male". In the region R523, the name of the disease "Ventricular Septal Defect" is displayed for the patient with the patient ID "00000003". Note that some event related information is not displayed in the region R523. In addition, the region R523 includes a button B53. The user can access detailed medical information of the patient with the patient ID "00000003" by specifying the button B53.

[0092] In the area R525, surgery schedule event related information is displayed for the patient with the patient ID "00000005". For example, in the area R525, it is displayed that the name of the patient with the patient ID "00000005" is "Shinju Saburo" and the gender is "Male". In the area R525, the name of the disease of the patient with the patient ID "00000005" is "Ventricular Septal Defect". Note that some event related information is not displayed in the area R525. In addition, the area R525 includes a button B55. By designating the button B55, the user can access detailed medical information of the patient with the patient ID "00000005".

[0093] Next, a display mode in which the processing circuit 11 displays mapping data on the display 13 for an imaging examination event will be described. At this time, the processing circuit 11 performs the process shown in the flowchart shown in FIG. 3. In the following description, the processing circuit 11 accepts the designation of the event type "imaging examination event" via the input interface 12. In addition, the acquisition condition for acquiring event information (imaging examination event information) representing this imaging examination event includes, for example, "medical information representing the results of the imaging examination." In addition, the acquisition condition includes a time element (for example, a period, etc.) and an element representing the attributes of the patient (for example, the doctor in charge, the medical department, and the ward, etc.). The time element is, for example, "the period from April 10, 2017 to April 27, 2017 when the event date and time occurs." In addition, the element representing the attributes of the patient is, for example, a patient in charge of Doctor A. In this case, the patients under the care of Doctor A are assumed to include patients with patient IDs "00000001," "00000002," "00000003," "00000004," and "00000005."

[0094] When the processing circuitry 11 receives the designation of the acquisition condition, the processing circuitry 11 reads the designated acquisition condition from the memory 14 (step SA1). The processing circuitry 11 reads, for example, the acquisition condition for acquiring an image inspection event from the memory 14.

[0095] The processing circuitry 11 acquires a plurality of event information items based on the read acquisition conditions (step SA2). For example, the processing circuitry 11 acquires event information representing an imaging examination event for each patient from medical information representing the results of imaging examination included in the log information 621 stored in the memory 62 of the DWH 6 based on the read acquisition conditions for acquiring imaging examination events. In other words, the processing circuitry 11 acquires patient identification information for identifying a patient in which an imaging examination event has occurred and time information representing a time associated with the imaging examination event.

[0096] At this time, the acquired imaging examination event information includes a record having an event type "imaging examination event", a patient ID "00000001", an event date and time "April 23, 2017", and event related information related to the imaging examination event (imaging examination event related information). The imaging examination event related information is, for example, medical image data acquired for a patient with a patient ID "00000001". The imaging examination event information also includes a record having an event type "imaging examination event", a patient ID "00000001", an event date and time "April 22, 2017", and imaging examination event related information. The imaging examination event related information is, for example, medical image data acquired for a patient with a patient ID "00000002". The imaging examination event information also includes a record having an event type "imaging examination event", a patient ID "00000003", an event date and time "April 18, 2017", and imaging examination event related information. The imaging examination event related information is, for example, medical image data acquired for a patient with a patient ID of "00000003". The imaging examination event information includes a record having an event type "imaging examination event", a patient ID of "00000004", an event date and time "April 19, 2017", and imaging examination event related information. The imaging examination event related information is, for example, medical image data acquired for a patient with a patient ID of "00000004". The imaging examination event information includes a record having an event type "imaging examination event", a patient ID of "00000005", an event date and time "April 13, 2017", and imaging examination event related information. The imaging examination event related information is, for example, medical image data acquired for a patient with a patient ID of "00000005".

[0097] The processing circuitry 11 maps the acquired event information across the acquired patients (step SA3). Specifically, the processing circuitry 11 generates mapping data in which one or more icons related to imaging examination events are mapped on a common time axis so as to be identifiable for each patient, based on the acquired patient identification information and time information.

[0098] The processing circuitry 11 displays the event-related information for each patient's event together with the mapping data (step SA4). Figure 6 is a diagram showing an example of a medical examination screen for an image examination event displayed on the display shown in Figure 2. The medical examination screen shown in Figure 6 includes a mapping area R61 having mapping data and an event-related information area R62 having at least one event-related information.

[0099] The mapping area R61 includes icons I61, I62, I63, I64, and I65 representing each patient. As shown in Fig. 6, each icon included in the mapping area R61 is displayed with a different color for each patient. Each icon may be displayed with the patient's name.

[0100] Icon I61 indicates that an imaging test, i.e., acquisition of medical images, was performed on the event date and time "April 23, 2017" for a patient with patient ID "00000001". Icon I62 indicates that an imaging test was performed on the event date and time "April 22, 2017" for a patient with patient ID "00000002". Icon I63 indicates that an imaging test was performed on the event date and time "April 18, 2017" for a patient with patient ID "00000003". Icon I64 indicates that an imaging test was performed on the event date and time "April 19, 2017" for a patient with patient ID "00000004". Icon I65 indicates that an imaging test was performed on the event date and time "April 13, 2017" for a patient with patient ID "00000005".

[0101] The event-related information region R62 includes regions R621, R622, R623, R624, and R625 that represent event-related information related to the event information for each patient. A scroll bar SC3 is provided at the right end of the event-related information region R62. The display range of the event-related information region R62 can be changed by a user's instruction to scroll bar SC3. In the event-related information region R62 shown in FIG. 6, parts of the regions R623 and R625 are not displayed on the display 13.

[0102] In the region R621, image examination event related information is displayed for the patient with the patient ID "00000001". In the region R621, for example, it is displayed that the name of the patient with the patient ID "00000001" is "Shinju Taro" and the gender is "Male". In addition, in the region R621, medical images based on medical image data acquired on the event date and time "April 23, 2017" for the patient with the patient ID "00000001" are displayed. In addition, the region R621 includes a button B61. When the user designates the button B61 via the input interface 12, the processing circuit 11 displays details of the medical information of the patient with the patient ID "00000001". Therefore, the user can access details of the medical information of the patient with the patient ID "00000001" by designating the button B61.

[0103] In the area R622, information related to the imaging examination event is displayed for the patient with the patient ID "00000002". For example, in the area R622, it is displayed that the name of the patient with the patient ID "00000002" is "Heartbeat Hanako" and the gender is "Female". In addition, in the area R622, medical images based on medical image data acquired on the event date and time "April 22, 2017" are displayed for the patient with the patient ID "00000002". In addition, the area R622 includes a button B62. By designating the button B62, the user can access detailed medical information of the patient with the patient ID "00000002".

[0104] In the region R624, information related to the imaging examination event is displayed for the patient with the patient ID "00000004". For example, in the region R624, it is displayed that the name of the patient with the patient ID "00000004" is "Shinju Ichiro" and the gender is "Male". In addition, in the region R624, medical images based on medical image data acquired on the event date and time "April 19, 2017" for the patient with the patient ID "00000004" are displayed. In addition, the region R624 includes a button B64. By designating the button B64, the user can access detailed medical information of the patient with the patient ID "00000004".

[0105] In the region R623, image examination event related information is displayed for the patient with the patient ID "00000003". For example, in the region R623, it is displayed that the name of the patient with the patient ID "00000003" is "Shinju Jiro" and the gender is "Male". In addition, in the region R623, medical images based on medical image data acquired on the event date and time "April 18, 2017" for the patient with the patient ID "00000003" are displayed. Note that some of the medical images are not displayed in the region R623. In addition, the region R623 includes a button B63. The user can access detailed medical information of the patient with the patient ID "00000003" by designating the button B63.

[0106] In the region R625, information related to the imaging examination event is displayed for the patient with the patient ID "00000005". For example, in the region R625, it is displayed that the name of the patient with the patient ID "00000005" is "Shinju Saburo" and the gender is "Male". In addition, in the region R625, medical images based on medical image data acquired on the event date and time "April 13, 2017" for the patient with the patient ID "00000005" are displayed. Note that some of the medical images are not displayed in the region R625. In addition, the region R625 includes a button B65. The user can access detailed medical information of the patient with the patient ID "00000005" by specifying the button B65.

[0107] (Variation 1) In the above embodiment, the processing circuit 11 generates summary screen data for one type of event, but this is not limited thereto. The processing circuit 11 may summarize event information covering multiple patients and multiple types of events to generate summary screen data. In the first modification, the processing circuit 11 accepts the designation of acquisition conditions for multiple types of events via the input interface 12. At this time, the processing circuit 11 accepts the designation of acquisition conditions for multiple types of events by, for example, displaying multiple areas in a pull-down manner on the display 13 in which character strings representing candidates for the acquisition conditions can be selected.

[0108] Fig. 7 is a diagram showing a display example of mapping data according to Modification 1. In the explanation of Fig. 7, it is assumed that the processing circuitry 11 accepts, for example, designation of the event types "heart failure symptom event", "renal function deterioration event", and "drug evaluation event". The mapping data shown in Fig. 7 is displayed, for example, on the display 13 shown in Fig. 2.

[0109] In Fig. 7, icons including character strings representing event types are mapped in chronological order for each patient. Specifically, in a mapping area R71 shown in Fig. 7, icons I71, I72a, I72b, I73, and I74 representing each event type are mapped in chronological order with the vertical axis representing patient ID and the horizontal axis representing time (date). The display period of the events shown in Fig. 7 is from April 10, 2017 to April 27, 2017.

[0110] More specifically, an icon I71 including "Drug Evaluation" representing a drug evaluation event is mapped to a position representing a patient ID "00000001" and a date "April 26, 2017". An icon I72a including "Heart Failure Sign" representing a heart failure sign event is mapped to a position representing a patient ID "00000002" and a date "April 15, 2017". An icon I72b including "Heart Failure Sign" representing a heart failure sign event is mapped to a position representing a patient ID "00000002" and a date "April 24, 2017". An icon I73 including "Renal Function Worsening" representing a renal function worsening event is mapped to a position representing a patient ID "00000003" and a date "April 17, 2017". Additionally, an icon I74 including "heart failure symptom" indicating a heart failure symptom event is mapped to a position indicating the patient ID "00000004" and the date "April 17, 2017".

[0111] 7 indicate the number of events displayed in the mapping area R71 for each patient ID. Note that the number displayed next to each patient ID may indicate, for example, when the acquired event information exists outside the display period, the number displayed next to each patient ID, the number of events not displayed in the mapping area R71, or the number of displayed events plus the number of undisplayed events.

[0112] Furthermore, as shown in FIG. 7, the icons included in the mapping area R71 are displayed in different colors for each event type, for example.

[0113] According to the display mode of Figure 7 described above, a user viewing the mapping data shown in Figure 7 can obtain more information without reducing visibility, for example, because multiple types of events are displayed in chronological order for each patient.

[0114] Fig. 8 is a diagram showing another display example of mapping data according to Modification 1. In the explanation of Fig. 8, it is assumed that the processing circuitry 11 accepts, for example, designation of event types "heart failure symptom event", "renal function deterioration event", "drug evaluation event", and "imaging test event". The mapping data shown in Fig. 8 is displayed, for example, on the display 13 shown in Fig. 2.

[0115] In Fig. 8, icons including patient IDs representing patients are mapped in chronological order for each event type. Specifically, in a mapping area R81 shown in Fig. 8, icons I81, I82a, I82b, I83, and I84 representing patient IDs identifying each patient are mapped in chronological order with the vertical axis representing character strings representing each event type and the horizontal axis representing time (date). The display period for the events shown in Fig. 8 is from April 10, 2017 to April 27, 2017. Each icon may be displayed with the patient's name attached.

[0116] More specifically, an icon I81 including a patient ID "00000001" is mapped to a position representing a character string "Drug Evaluation" representing a drug evaluation event and a date "April 26, 2017". An icon I82a including a patient ID "00000002" is mapped to a position representing a character string "Heart Failure Symptoms" representing a heart failure symptom event and a date "April 15, 2017". An icon I82b including a patient ID "00000002" is mapped to a position representing a character string "Heart Failure Symptoms" representing a heart failure symptom event and a date "April 24, 2017". An icon I83 including a patient ID "00000003" is mapped to a position representing a character string "Renal Function Worsening" representing a renal function deterioration event and a date "April 17, 2017". An icon I84 including a patient ID "00000004" is mapped to a position representing the character string "heart failure symptom", which indicates a heart failure symptom event, and the date "April 21, 2017".

[0117] 8 represent the total number of patients displayed in the mapping area R81 for each event type. Note that the numbers displayed next to the character strings representing each event type may represent, for example, the total number of patients not displayed in the mapping area R81 for each event type when the acquired event information exists outside the display period, or the total number of patients displayed plus the total number of patients not displayed.

[0118] Furthermore, as shown in FIG. 8, the icons included in the mapping region R81 are displayed in different colors for each event type, for example.

[0119] According to the display mode of Figure 8 described above, a user who views the mapping data shown in Figure 8 can obtain more information without reducing visibility, for example, because multiple patients in the user's care are displayed in chronological order by event type.

[0120] In the above description of Fig. 8, the events are displayed together in an area including one time axis, but this is not limited to this. Below, a description will be given of a case where the mapping data is displayed by allocating an area including one time axis to each event related to each event type.

[0121] Fig. 9 is a diagram showing another display example of mapping data according to Modification 1. In the explanation of Fig. 9, it is assumed that the processing circuitry 11 accepts designation of character strings "heart failure symptom event", "renal function deterioration event", "drug evaluation event", and "imaging test event", for example.

[0122] In FIG. 9, the mapping region R91 includes regions R911, R912, R913, and R914 including one time axis for each event type. The region R911 displays mapping data in which heart failure symptom events are mapped on a common time axis so as to be identifiable for each patient. The region R912 displays mapping data in which renal function deterioration events are mapped on a common time axis so as to be identifiable for each patient. The region R913 displays mapping data in which drug evaluation events are mapped on a common time axis so as to be identifiable for each patient. The region R914 displays mapping data in which imaging examination events are mapped on a common time axis so as to be identifiable for each patient.

[0123] According to the display mode of FIG. 9 described above, for example, the display area per event type is large, and therefore visibility is improved compared to the mapping data shown in FIG.

[0124] (Variation 2) In the above embodiment, the processing circuit 11 may display each event included in the mapping data shown in Fig. 4 in consideration of the user's browsing history. For example, the processing circuit 11 displays events that the user has viewed and events that the user has not viewed in a distinguishable manner. Here, "the user views an event" means, for example, that the user accesses details of medical information of a patient linked to one event included in the mapping data and opens a medical care screen showing the details.

[0125] Fig. 10 is a diagram showing a display example of mapping data according to Modification 2. A mapping area R101 shown in Fig. 10 represents mapping data in which heart failure symptom events across multiple patients are mapped on a common time axis so as to be identifiable for each patient.

[0126] The mapping area R101 includes icons I101, I102, I103, I104, and I105 representing each patient. At this time, among the icons I101, I102, I103, I104, and I105 shown in FIG. 10, for example, the details of the medical information of the patient linked to each event represented by the icons I102, I104, and I105 have already been viewed by the user. In response to this, the processing circuit 11 changes the display mode of the icons I102, I104, and I105 and displays them. Specifically, the processing circuit 11 changes the frame lines surrounding the icons I102, I104, and I105 and the patient IDs included in the icons from solid lines to dotted lines and displays them.

[0127] According to the display mode of FIG. 10 described above, a user who visually views an icon included in the mapping data shown in FIG. 10 can easily understand whether or not the event represented by the icon he or she has viewed has been viewed by the user.

[0128] In the above description of FIG. 10, the display mode of the icon representing the event viewed by the user is changed, but the present invention is not limited to this. For example, the processing circuit 11 may display the display period shown in the mapping data in such a way that the period viewed by the user and the period not viewed by the user can be distinguished. The "period viewed by the user" is, for example, a period including the event viewed by the user. In addition, the "period viewed by the user" may be specified by having the user directly specify the period during which the user is thought to have viewed the displayed mapping data via the input interface 12.

[0129] Fig. 11 is a diagram showing another display example of mapping data according to Modification 2. A mapping region R111 shown in Fig. 11 represents mapping data in which heart failure symptom events across multiple patients are mapped on a common time axis so as to be identifiable for each patient.

[0130] The mapping region R111 includes icons I111, I112, I113, I114, and I115 representing each patient. At this time, of the "period from April 10, 2017 to April 20, 2017" represented by the region R115 shown in FIG. 11, the "period from April 10, 2017 to April 20, 2017" represented by the region R116 has already been viewed by the user. In response to this, the processing circuit 11 changes the display mode of the region R116 and displays it. Specifically, the processing circuit 11 superimposes, for example, a shaded image on the region R116. At this time, the shaded image is also superimposed on the icons I123, I124, and I125 included in the region R116.

[0131] The notification area R117 included in the mapping area R111 shown in Fig. 11 has a function of notifying a user that details of medical information of a patient that has been viewed once have been updated by designating the area in question. The notification area R117 shown in Fig. 11 shows the state before designation by using a low-brightness color.

[0132] Next, a case where the notification area R117 shown in Fig. 11 is specified will be described. Fig. 12 is a diagram showing another display example of mapping data displayed according to Modification Example 2. The mapping area R121 shown in Fig. 12 represents the mapping data after the notification area R117 shown in Fig. 11 is specified. At this time, the notification area R127 shown in Fig. 12 represents the state after the specification by, for example, a bright color.

[0133] The mapping area R121 includes icons I121, I122, I123, I124, and I125 representing each patient. At this time, among the icons I121, I122, I123, I124, and I125 shown in FIG. 12, details of the medical information of the patient corresponding to the event represented by the icon I125 are updated. In response to this, the processing circuit 11 releases the overlap of the shaded image only on the area occupied by the icon I125. This makes it possible to notify that details of the medical information of the patient for the event represented by the icon I125 have been updated. Note that the processing circuit 11 may newly display events that have newly occurred during the period viewed by the user.

[0134] Furthermore, when the mapping data is displayed, the processing circuit 11 may highlight an icon representing an event included in the mapping data, for example, when the number of times that the detailed medical information of the corresponding patient has not been viewed exceeds a predetermined threshold. Fig. 13 is a diagram showing another display example of mapping data according to Modification Example 2. The mapping area R131 shown in Fig. 13 represents mapping data in which heart failure symptom events across multiple patients are mapped on a common time axis so as to be identifiable for each patient.

[0135] The mapping area R131 includes icons I131, I132, I133, I134, and I135 representing each patient. At this time, among the icons I131, I132, I133, I134, and I135 shown in FIG. 13, for example, the detailed medical information of the patient associated with each event represented by the icons I133 and I135 has not been viewed more than a predetermined threshold number of times. In response to this, the processing circuit 11 highlights the patient IDs included in the icons I133 and I135 by making them bold or blinking, for example. This makes it possible to notify the user of events that have been frequently overlooked, for example.

[0136] (Variation 3) In the above embodiment, the processing circuit 11 can further improve visibility by devising a display mode. For example, the processing circuit 11 summarizes and displays the event information in the form of a histogram or a line graph. A case where the event information is summarized and displayed in the form of a histogram will be described below. FIG. 14 is a diagram showing a display example of mapping data according to Modification Example 3. The mapping area R141 shown in FIG. 14 represents mapping data in which heart failure symptom events across multiple patients are mapped on a common time axis so as to be identifiable for each patient. In the mapping area R141 shown in FIG. 14, the number of events for each date is displayed in a recognizable manner.

[0137] Specifically, in the mapping area R141 shown in Fig. 14, icons I141, I142, I143, I144, I145, and I146 representing each patient are mapped in chronological order, with the vertical axis representing the number of events and the horizontal axis representing time (date). The display period of the events shown in Fig. 14 is from April 10, 2017 to April 27, 2017. Note that in Fig. 14, each icon included in the mapping area R141 is given a different color for each patient, and is displayed so that the patients can be identified. The numbers shown on the left side of the mapping area R141 correspond to the number of icons piled up in the area corresponding to each date, i.e., the number of events.

[0138] According to the display mode of FIG. 14 described above, a user who visually checks the mapping data can easily grasp, for example, the occurrence frequency of events on each date.

[0139] Moreover, the processing circuit 11 may directly map and display the event-related information on the time axis included in the mapping data. FIG. 15 is a diagram showing another display example of the mapping data according to the third modification. The mapping area R150 shown in FIG. 15 represents mapping data in which heart failure symptom events across a plurality of patients are mapped on a common time axis so as to be identifiable for each patient. The mapping area R150 includes a time axis display area R151 representing the time axis, and areas R152, R153, R154, and R155 representing event-related information related to the event information for each patient. As shown in FIG. 15, the areas R152, R153, R154, and R155 are directly mapped to the time axis display area R151. Specifically, the time axis display area R151 and the areas R152, R153, R154, and R155 are connected by line segments, respectively.

[0140] According to the display mode of FIG. 15 described above, the event occurrence timing and the event-related information are displayed in a visually linked state, improving visibility.

[0141] Furthermore, the processing circuitry 11 may further display the priority order of events included in the mapping data. Fig. 16 is a diagram showing another display example of mapping data according to Modification Example 3. A mapping region R161 shown in Fig. 16 represents mapping data in which heart failure symptom events across multiple patients are mapped on a common time axis so as to be identifiable for each patient.

[0142] The mapping area R161 includes icons I161, I162, I163, I164, and I165 representing each patient. As shown in Fig. 16, each icon included in the mapping area R161 is displayed with a different color for each patient. Note that each icon may be displayed with the patient's name.

[0143] The mapping area R161 includes an area R162 that represents an event queue, and a mark M161 that represents the priority of processing. The area R162 represents an event queue in which icons representing patients are stacked. The mark M161 indicates that the thicker the mark is in the vertical direction, the higher the priority. In other words, the higher the icon located at the top of the event queue shown in the area R162, the higher the priority of the patient's medical information.

[0144] According to the display mode of FIG. 16 described above, a user who visually checks the mapping data can easily understand, for example, the priority of confirmation of patient medical information among patients.

[0145] (Variation 4) In the above embodiment, the processing circuitry 11 may change the display mode of the mapping data to be displayed according to the occurrence pattern of events related to the same patient. In the following description, it is assumed that the mapping data displayed on the display 13 includes an area where the summary method can be selected in a pull-down manner.

[0146] First, a case will be described where the processing circuit 11 displays a period including a group of events that occurred during a specific period. Fig. 17 is a diagram showing an example of display of mapping data according to Modification 4. A mapping area R171 shown in Fig. 17 represents mapping data in which heart failure symptom events across multiple patients are mapped onto a common time axis so as to be identifiable for each patient. In Fig. 17, "period" is selected as a mapping method for the mapping data.

[0147] In FIG. 17, the mapping area R171 includes icons I171, I173, and I174 representing each patient. The icon I171 represents, in a band shape, the fact that a plurality of heart failure symptom events occurred for a patient with a patient ID of "00000001", for example, over a period of "April 21, 2017 to April 23, 2017". The icon I173 represents, in a band shape, the fact that a plurality of heart failure symptom events occurred for a patient with a patient ID of "00000003", for example, over a period of "April 10, 2017 to April 16, 2017". The icon I174 represents, in a band shape, the fact that a plurality of heart failure symptom events occurred for a patient with a patient ID of "00000004", for example, over a period of "April 15, 2017 to April 19, 2017".

[0148] Next, a case will be described where the display mode of the mapping data is changed in consideration of the frequency of occurrence of events when the processing circuit 11 displays a period including a group of events that occurred in a specific period. Fig. 18 is a diagram showing another display example of mapping data according to Modification 4. The mapping area R181 shown in Fig. 18 represents mapping data in which heart failure symptom events across multiple patients are mapped on a common time axis so as to be identifiable for each patient. In Fig. 18, "distribution" is selected as the mapping method for the mapping data.

[0149] In FIG. 18, the mapping region R181 includes icons I181, I183, and I184 representing each patient. The icon I181 represents, in a band shape, the fact that a plurality of heart failure symptom events occurred for a patient with a patient ID of "00000001", for example, over a period "from December 2017 to February 2018". The icon I181 also displays the distribution of the heart failure symptom events in a shading pattern according to the frequency of the heart failure symptom events. The icon I183 represents, in a band shape, the fact that a plurality of heart failure symptom events occurred for a patient with a patient ID of "00000003", for example, over a period "from January 2017 to July 2017". The icon I183 also displays the distribution of the heart failure symptom events in a shading pattern according to the frequency of the heart failure symptom events. Icon I184 indicates, in the form of a band, the fact that multiple heart failure symptom events occurred for a patient with patient ID "00000004" over a period from, for example, "June 2017 to October 2017." Icon I184 also indicates the distribution of heart failure symptom events in shading according to the frequency of their occurrence.

[0150] The processing circuit 11 may display only the last or latest event in the specific period in which the events occurred. Also, the processing circuit 11 may display only a portion where the events are most concentrated in the specific period in which the events occurred.

[0151] Finally, a case will be described in which the processing circuitry 11 displays events that have occurred for each patient based on a combination of events that have occurred across multiple event types. In this case, the processing circuitry 11 can display events at an appropriate granularity and the similarity of the events that have been displayed by classifying the occurrence patterns of the events using a method such as clustering. Fig. 19 is a diagram showing another display example of mapping data according to the fourth modification. According to Fig. 19, the processing circuitry 11 displays events that have occurred for each patient based on the order in which the events occurred.

[0152] In FIG. 19, the mapping area R191 includes icons I191, I192, I193, and I194 representing each patient. Each icon included in the mapping area R191 shown in FIG. 19 is displayed with a different color for each patient. The icon I191 represents, for example, in a band shape, the fact that events have occurred over a predetermined period of time for a patient with a patient ID of "00000001" in the order of event types "SpO2 decrease event" and "hypoxemia symptom event". The icon I192 represents, for example, in a band shape, the fact that events have occurred over a predetermined period of time for a patient with a patient ID of "00000002" in the order of event types "urine volume decrease event", "respiratory rate increase event", and "heart failure symptom event". Icon I193 represents, for example, in a band shape, the fact that events have occurred over a predetermined period of time for a patient with patient ID "00000003" in the order of event types "BNP increase event," "respiratory rate increase event," and "heart failure symptom event." Icon I194 represents, for example, in a band shape, the fact that events have occurred over a predetermined period of time for a patient with patient ID "00000004" in the order of event types "SpO2 decrease event," and "hypoxemia symptom event."

[0153] In addition, the mapping data shown in FIG. 19 displays combinations of similar event types in the same row (at the same height).

[0154] [Other embodiments] In the above embodiment, the processing circuit 11 may change the display content related to the event-related information displayed in the event-related information area R42 in synchronization with a change in the time axis included in the mapping data represented by the mapping area R41 shown in Fig. 4. Hereinafter, a case will be described in which the period represented by the time axis included in the mapping data represented by the mapping area R41 shown in Fig. 4 is changed from "the period from April 10, 2017 to April 27, 2017" to "the period from April 5, 2017 to April 22, 2017."

[0155] FIG. 20 is a diagram showing an example of a medical examination screen according to another embodiment. FIG. 20 shows a medical examination screen after the range of the time axis included in the mapping data represented by the mapping area R41 shown in FIG. 4 is changed. According to FIG. 20, the "period from April 23, 2017 to April 27, 2017" represented by the time axis displayed in the mapping area R41 shown in FIG. 4 is hidden after the range of the time axis is changed. At this time, icons I41a, I41b, and I41c are also hidden after the range of the time axis is changed. Furthermore, according to FIG. 20, the area R421 corresponding to icons I41a, I41b, and I41c representing patient ID "00000001" included in the event-related information area R42 shown in FIG. 4 is also hidden after the range of the time axis is changed. In this way, the processing circuit 11 can change the content of the event-related information displayed in the event-related information area R42 in synchronization with the change in the range of the time axis. Note that the time axis represented by each piece of event-related information included in the event-related information region R42 may be changed in conjunction with a change in the time axis included in the mapping data represented by the mapping region R41. Furthermore, the processing circuitry 11 may optimize the content of the event-related information displayed in the event-related information region R42 according to the patient.

[0156] In the above embodiment, the processing circuit 11 displays, for example, information acquired about one patient in one graph area in the event-related information area R42 shown in Fig. 4, but is not limited to this. For example, the processing circuit 11 may display information acquired about multiple patients in one graph area.

[0157] In the above embodiment, the processing circuit 11 displays details of the medical information of a patient when, for example, each "View" button shown in FIG. 4 is designated. Hereinafter, a case where the button B42 included in the area R422 included in the event-related information area R42 shown in FIG. 4 is designated will be described. When the button B42 shown in FIG. 4 is designated, the processing circuit 11 displays details of the medical information of a patient with a patient ID of "00000002". FIG. 21 is a diagram showing an example of a patient details screen showing details of the medical information of a patient according to another embodiment. The patient details screen shown in FIG. 21 shows that the patient with the patient ID "00000002" has the patient name "Heartbeat Hanako", date of birth "January 1, 2013", and gender "female".

[0158] The patient details screen shown in FIG. 21 includes a timeline area R211, and a medical information area divided into an image information area R212a that displays images from an imaging test, a vital sign information area R212b that displays vital sign information, and a medical record information area R212c that displays information from the medical record.

[0159] The timeline area R211 displays a plurality of icons corresponding to a plurality of pieces of medical information etc. in chronological order over the period from "04:00" to "21:00" on "April 15, 2017." The timeline area R211 includes an indicator L211 that indicates the position of the date and time specified by the operator (specified date and time "April 15, 2017 12:00").

[0160] The image information area R212a includes an information display area R212d that displays thumbnails of examination images for a specific patient in chronological order (e.g., images located at the top of the screen have newer images) over a certain period of time. The information display area R212d includes an indicator L212a that indicates a position corresponding to a specified date and time. Hereinafter, the "thumbnail of the examination image" will be simply referred to as a "thumbnail." The position corresponding to the specified date and time in the information display area R212d corresponds to, for example, the top or bottom of a thumbnail associated with a date and time closest to the specified date and time. This position may also be on the thumbnail.

[0161] The vital sign information region R212b displays vital sign information about a specific patient over the period "from April 11, 2017 to April 21, 2017." The vital sign information region R212b includes an indicator L212b that indicates a position corresponding to the specified date and time.

[0162] The medical record information area R212c displays comments by doctors and nurses about a specific patient over a certain period of time, for example, in chronological order (for example, comments located at the top of the screen have more recent dates and times). The medical record information area R212c includes an indicator L212c that indicates a position corresponding to a specified date and time. Note that the position corresponding to the specified date and time in the medical record information area corresponds to, for example, the top or bottom of a comment associated with a date and time closest to the specified date and time. This position may also be on the comment.

[0163] In summary, when the indicator L211 is set first on the medical treatment screen shown in FIG. 21, the indicators L212a, L212b, and L212c are automatically set (or displayed).

[0164] 21, the processing circuit 11 changes the display content of the patient details screen shown in FIG. 21 according to, for example, the event type of an event that occurs. For example, the processing circuit 11 changes the initial layout of the patient details screen shown in FIG. 21 according to the content of the event that occurs. Furthermore, the processing circuit 11 changes the display content to be displayed in the medical information area shown in FIG. 21 according to the content of the event that occurs. Note that, in FIG. 21, the processing circuit 11 may display the time axis median value included in the timeline area R211, the image information area R212a, the vital sign information area R212b, and the medical record information area R212c that are displayed immediately after the button B42 shown in FIG. 4 is specified, so as to be the event date and time.

[0165] The term "processor" used in the above description means, for example, a circuit such as a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a programmable logic device (for example, a simple programmable logic device (SPLD), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)). The processor realizes its function by reading and executing a program stored in a memory circuit. Note that each processor in this embodiment is not limited to being configured as a single circuit for each processor, and may be configured as one processor by combining multiple independent circuits to realize its function. Furthermore, multiple components in FIGS. 1 and 2 may be integrated into one processor to realize its function.

[0166] According to at least one of the embodiments described above, it is possible to reduce the time required to access medical information of a patient who should be given priority in medical treatment.

[0167] Although some embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope and spirit of the invention, and are included in the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0168] 1...Medical information display device 2. Hospital information systems 3…Radiology department information management system 4. Medical imaging diagnostic equipment 5. Medical image management system 6. Data warehouse 11, 61...Processing circuit 12...Input interface 13…Display 14, 62…Memory 15, 63…Communication interface 111…Acquisition function 113…Mapping function 115...Display control function 117...System control function 611…Collection function 612…Registration function 621...Log information R41, R51, R61, R71, R81, R91, R101, R111, R121, R131, R141, R150, R161, R171, R181, R191…Mapping area R42, R52, R62...Event related information area R211…Timeline area R212a…Image information area R212b: Vital signs information area R212c…Medical record information area R212d…Information display area

Claims

1. an acquisition unit that receives a designation of an event type serving as an index for judgment in medical treatment, reads out acquisition conditions for acquiring event information including at least patient identification information for identifying a patient in whom an event has occurred and time information indicating a time associated with the event based on the received event type, and acquires event information that satisfies the acquisition conditions from medical treatment information of a plurality of patients; a mapping unit that generates mapping data in which an icon that can identify the occurrence of the event for each patient is mapped onto a common time axis based on the patient identification information and the time information included in the acquired event information; a display control unit that displays the mapping data on a display; Equipped with the display control unit displays event-related information related to the event information together with the mapping data; A medical information display device, wherein the event-related information includes medical data corresponding to the event identified by the icon mapped to the mapping data, and is displayed on the display with a display area divided for each patient.

2. The event type specifies an event that indicates a symptom of a disease. The medical information display device according to claim 1 .

3. The event type includes an event related to a heart failure symptom. The medical information display device according to claim 1 or 2.

4. The event type includes an event related to deterioration of renal function. The medical information display device according to claim 1 .

5. The acquisition condition is a relationship between the event type and the event information to be acquired that is defined by artificial intelligence. The medical information display device according to claim 1 .

6. The acquisition condition includes a numerical evaluation of the biological information of the patients included in the medical information of the plurality of patients. The medical information display device according to claim 1 .

7. The mapping unit identifies and displays a location where the events are concentrated during a period in which the events occurred. The medical information display device according to claim 1 .

8. the display control unit changes the content of the event-related information to be displayed in synchronization with the change in the range of the time axis. The medical information display device according to claim 1 .

9. the display control unit displays the events that have been viewed by a user in a distinguishable manner from the events that have not been viewed by the user. The medical information display device according to claim 1 .

10. On the computer, A first function of accepting a designation of an event type that serves as an index for judgment in medical treatment; a second function of reading out an acquisition condition for acquiring event information including at least patient identification information for identifying a patient in whom an event has occurred and time information indicating a time associated with the event, based on the received event type; a third function of acquiring event information that satisfies the acquisition condition from medical information of a plurality of patients; a fourth function of generating mapping data in which an icon capable of identifying the occurrence of the event for each patient is mapped on a common time axis based on the patient identification information and the time information included in the acquired event information; A fifth function of displaying the mapping data on a display. Realize this, The fifth function displays event-related information related to the event information together with the mapping data; The event-related information includes medical data corresponding to the event identified by the icon mapped to the mapping data, and is displayed on the display with a display area divided for each patient.

11. Accepting designation of an event type that serves as an indicator for judgment in medical treatment; reading out an acquisition condition for acquiring event information including at least patient identification information for identifying a patient in which an event has occurred and time information indicating a time associated with the event, based on the received event type; acquiring event information that satisfies the acquisition condition from medical information of a plurality of patients; generating mapping data in which an icon capable of identifying the occurrence of the event for each patient is mapped onto a common time axis based on the patient identification information and the time information included in the acquired event information; displaying the mapping data on a display; Equipped with displaying on the display includes displaying event-related information related to the event information together with the mapping data; A method for displaying medical information, wherein the event-related information includes medical data corresponding to the event identified by the icon mapped to the mapping data, and is displayed on the display with a display area divided for each patient.

Images