Program, method, and information processing device

Abstract

To provide a program, a method, and an information processing device for presenting medical care support information that supports medical care to medical staff.SOLUTION: A method in a medical care support system includes: a step S601 in which a user side terminal device receives an input of first patient state information based on a chief complaint from a patient; a step S631 in which a server extracts a first tag group related to cases associated with the information; a step 602 in which the user side terminal device receives an input of second patient state information based on information excluding the chief complaint from the patient; a step S632 in which the server extracts a second tag group related to cases associated with the information; a step S633 for evaluating the compatibility of both pieces of tag information contained in either the first tag group or the second tag group; a step S634 for generating estimated disease information based on relating tag information, if the compatibility is equal to a prescribed level or higher; and a step S635 in which the estimated disease information generated is presented to a user being a medical staff member.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] The present disclosure relates to a program, a method, and an information processing device. [Background technology]

[0002] As medical care has become more sophisticated and specialized due to recent advances in medical technology, higher levels of expertise are required in the medical treatment of patients provided by doctors and other medical professionals. As a result, medical professionals are required to provide treatment that matches their own specialty, but in environments with a limited number of medical professionals, such as rural and depopulated areas, a limited number of medical professionals must be able to provide all types of medical treatment.

[0003] In such an environment, medical professionals need medical knowledge to treat patients outside their own specialty, but acquiring this knowledge in between their busy schedules places a heavy burden on them. At the same time, patients also feel anxious about not receiving appropriate medical care when they are treated by medical professionals outside their specialty.

[0004] For this reason, there is a demand for technology to support medical care provided by medical professionals when examining patients. As a means of supporting medical care provided by such medical professionals, technology is known that provides medical-related information about patients that can be viewed by medical professionals during medical care.

[0005] Patent Document 1 describes a medical support system for supporting medical treatment by medical professionals. This medical support system extracts tags related to input information entered by a medical professional, and identifies medical treatment-related information about a patient based on the extracted tags. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-201093 Summary of the Invention [Problem to be solved by the invention]

[0007] However, in the technology of Patent Document 1, tags are extracted based on information input by a medical professional, but it is not determined whether the extracted tags are appropriate tags, so if there is an error in the input information, for example, an incorrect tag may be extracted, which may lead to an incorrect diagnosis. In particular, when a medical professional who is not a specialist in the field is providing medical care, there is a risk that he or she will not notice the error in the tag and will not be able to provide accurate medical care.

[0008] Therefore, the present disclosure provides a technology that can present medical support information that supports medical treatment to medical professionals, regardless of the expertise of the medical professionals providing the treatment. [Means for solving the problem]

[0009] According to one embodiment, a program for processing information about a patient to be treated is executed by a computer having a processor and a storage unit, the program including the steps of: receiving input of first patient condition information about the condition of the patient, the first patient condition information being acquired based on information about a chief complaint from the patient during treatment of the patient; extracting a first tag group including at least one tag information about a case associated with the first patient condition information based on the received first patient condition information; and extracting a second patient condition information about the condition of the patient, the second patient condition information being acquired based on information other than the chief complaint from the patient during treatment of the patient. extracting a second tag group including at least one tag information related to a case associated with the second patient condition information based on the received second patient condition information; evaluating the consistency between the tag information included in at least one of the extracted first tag group and the second tag group; generating inferred disease information related to a suspected disease of the patient based on the tag information related to the evaluation if the consistency is evaluated to be at least a predetermined level; and presenting the generated inferred disease information to a user who is a medical professional. [Effects of the Invention]

[0010] According to the present disclosure, tag information is extracted based on information regarding the patient's condition obtained during medical treatment, and after evaluating the suitability of the tag information, disease prediction is performed based on the tag information, thereby providing accurate medical support information to medical professionals. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram showing the overall configuration of a medical care support system 1 according to an embodiment. [Figure 2] 2 is a block diagram showing the functional configuration of a user terminal device 10. FIG. [Figure 3] FIG. 2 is a block diagram showing the functional configuration of a server 20. [Figure 4]FIG. 2 is a diagram showing the data structure of a reference tag information management database 2021. [Figure 5] FIG. 10 is a diagram showing the data structure of a reference suspected disease information management database 2022. [Figure 6] FIG. 2 is a diagram showing the data structure of a patient information management database 2023. [Figure 7] FIG. 10 is a diagram showing the data structure of a reference question information management database 2027. [Figure 8] 4 is a flowchart showing a processing operation (operation example 1) in the medical support system 1. [Figure 9] 10 is a flowchart showing a processing operation (operation example 2) in the medical assistance system 1. [Figure 10] 10 is a flowchart showing a processing operation (operation example 3) in the medical assistance system 1. [Figure 11] 10 is a flowchart showing a processing operation (operation example 4) in the medical assistance system 1. [Figure 12] FIG. 10 is a diagram showing an example of a screen displaying suspected disease information presented to a user. [Figure 13] FIG. 10 is a diagram showing an example of a screen showing an evaluation result regarding the consistency of tag information presented to a user. [Figure 14] FIG. 10 is a diagram showing another example of a screen showing the evaluation result regarding the consistency of tag information presented to the user. [Figure 15] FIG. 10 is a diagram showing an example of a screen for a user to modify tag information. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. The names and functions of the components are also the same. Therefore, detailed description thereof will not be repeated.

[0013] First Embodiment In this embodiment, during a patient's medical examination, tag information is extracted based on patient condition information obtained from the patient's condition, the eligibility of the tag information is determined, and then suspected disease information for the patient is generated based on the tag information, and the generated suspected disease information is presented to a medical professional. In this embodiment, patient medical examination includes a series of medical procedures, such as a patient interview and a patient examination, for diagnosing the patient's symptoms based on information about the patient's condition obtained from the patient's chief complaint, observation of the patient's appearance, etc. Furthermore, patient medical examination includes not only face-to-face medical examination but also remote medical examination, such as so-called online medical examination.

[0014] <1.1 Overall configuration of the medical support system> Fig. 1 is a block diagram showing an example of the overall configuration of a medical assistance system 1 according to an embodiment. As shown in Fig. 1, the medical assistance system 1 includes a user terminal device 10, a server 20, an external input device 30, and a medical institution terminal device 40, which are connected to each other via a network 80 so as to be able to communicate with each other.

[0015] The user terminal device 10 is a device operated by a user who is a medical professional such as a doctor, etc. The user terminal device 10 is, for example, a mobile terminal such as a smartphone or a tablet, or a PC (Personal Computer).

[0016] The user terminal device 10 executes a program to provide the user with an environment for operating the medical assistance system 1 according to the program. By reading and executing the program, the user terminal device 10 communicates with the server 20, the external input device 30, and the medical institution terminal device 40. The user terminal device 10 also accepts input of patient condition information relating to the patient's condition acquired during medical treatment, transmits the accepted patient condition information to the server 20, and receives estimated disease information of the patient from the server 20.

[0017] The user-side terminal device 10 accepts inputs such as patient condition information obtained by a user, who is a medical professional providing medical care, when performing medical care such as interviewing and examining the patient, patient condition information obtained by an external input device 30, and patient condition information obtained by a medical institution-side terminal device 40.

[0018] As shown in FIG. 1, the user terminal device 10 includes a communication IF (Interface) 12, an input device 13, an output device 14, a memory 17, a storage unit 18, and a processor 19.

[0019] The communication IF 12 is an interface for inputting and outputting signals so that the user terminal device 10 can communicate with external devices.

[0020] The input device 13 is a device for receiving input operations from a user (for example, a touch panel, a touch pad, a pointing device such as a mouse, a keyboard, etc.).

[0021] The output device 14 is a device (such as a display or speaker) for presenting information to the user.

[0022] The memory 17 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0023] The storage unit 18 is for storing data, and is, for example, a flash memory or a hard disk drive (HDD).

[0024] The processor 19 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, a register, a peripheral circuit, and the like.

[0025] The server 20 is a device that manages a series of processes related to the medical support system 1. The server 20 receives input of first patient condition information obtained based on information about the patient's chief complaint and second patient condition information obtained based on information other than the patient's chief complaint, extracts tag information (first tag group, second tag group) based on the received patient condition information, evaluates the consistency between the tag information included in the extracted first tag group and the tag information included in the second tag group, and, if tag information with a consistency level equal to or higher than a predetermined level is included between the first tag group and the second tag group, generates estimated disease information based on the tag information and presents the generated estimated disease information to a user who is a medical professional. The server 20 manages various data such as patient information, tag information, and estimated disease information.

[0026] The server 20 includes a communication IF 22 , an input / output IF 23 , a memory 25 , a storage 26 , and a processor 29 .

[0027] The communication IF 22 is an interface for inputting and outputting signals so that the server 20 can communicate with external devices.

[0028] The input / output IF 23 functions as an input device for receiving input operations from the user and as an interface with an output device for presenting information to the user.

[0029] The memory 25 is for temporarily storing programs and data to be processed by the programs, and is a volatile memory such as a DRAM (Dynamic Random Access Memory).

[0030] The storage 26 is for storing data, and is, for example, a flash memory or a hard disk drive (HDD).

[0031] The processor 29 is hardware for executing an instruction set written in a program, and is composed of an arithmetic unit, registers, peripheral circuits, and the like.

[0032] The external input device 30 is, for example, a device installed in a consultation room where a medical professional examines a patient, and is a device of various types for acquiring patient condition information (first patient condition information) relating to the patient's condition at the time of examination. The patient condition information acquired by the external input device 30 is transmitted to the user terminal device 10 or the server 20 via the network 80.

[0033] Examples of the external input device 30 include a device that acquires information about the patient's speech and voice, a device that acquires information about the patient's appearance such as the patient's facial expression, complexion, appearance, and posture, and a device that acquires the patient's biological information such as the patient's body temperature, pulse, blood pressure, and respiration. These devices not only acquire information but also convert the acquired information into patient condition information that can be processed by the server 20. The external input device 30 is not limited to the above, and any type of device that acquires information that can be processed as patient condition information by the server 20 can be applied.

[0034] The medical institution terminal device 40 is a device set up in the medical institution where the patient receives medical treatment, and is a device for acquiring patient condition information (first patient condition information) regarding the patient's condition in a preliminary interview before the patient is examined. The medical institution terminal device 40 is, for example, a mobile terminal such as a smartphone or tablet, or a PC (Personal Computer). The patient condition information acquired by the external input device 30 is transmitted to the user terminal device 10 or server 20 via the network 80. Note that the medical institution terminal device 40 is distinguished from the user terminal device 10 operated by a user who is a medical professional during medical treatment.

[0035] <1.2 Functional configuration of the user terminal device 10> 2 is a diagram showing the functional configuration of the user terminal device 10. The user terminal device 10 includes multiple antennas (antenna 111, antenna 112), wireless communication units (first wireless communication unit 121, second wireless communication unit 122) corresponding to the respective antennas, an operation reception unit 130, an audio processing unit 140, a microphone 141, a speaker 142, a camera 150, a storage unit 160, and a control unit 170. The user terminal device 10 also has functions and configurations not specifically shown in FIG. 2 (e.g., a battery for storing power, a power supply circuit for controlling the supply of power from the battery to each circuit, etc.). As shown in FIG. 2, the blocks included in the user terminal device 10 are electrically connected by a bus or the like.

[0036] The antenna 111 radiates the signal emitted by the user terminal device 10 into space as a radio wave. The antenna 111 also receives the radio wave from space and provides the received signal to the first radio communication unit 121.

[0037] The antenna 112 radiates the signal emitted by the user terminal device 10 into space as a radio wave. The antenna 112 also receives the radio wave from space and provides the received signal to the second radio communication unit 122.

[0038] The first wireless communication unit 121 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 111 so that the user terminal device 10 can communicate with other wireless devices. The second wireless communication unit 122 performs modulation / demodulation processing and the like for transmitting and receiving signals via the antenna 112 so that the user terminal device 10 can communicate with other wireless devices. The first wireless communication unit 121 and the second wireless communication unit 122 are communication modules including a tuner, an RSSI (Received Signal Strength Indicator) calculation circuit, a CRC (Cyclic Redundancy Check) calculation circuit, a high-frequency circuit, etc. The first wireless communication unit 121 and the second wireless communication unit 122 perform modulation / demodulation and frequency conversion of wireless signals transmitted and received by the user terminal device 10, and provide the received signals to the control unit 180.

[0039] The operation reception unit 130 has a mechanism for receiving input operations from the user. Specifically, the operation reception unit 130 is configured as a touch screen and includes a touch-sensitive device 131 and a display 132. The touch-sensitive device 131 receives input operations from the user of the user-side terminal device 10. The touch-sensitive device 131 detects the user's touch position on the touch panel, for example, by using a capacitive touch panel. The touch-sensitive device 131 outputs a signal indicating the user's touch position detected by the touch panel to the control unit 180 as an input operation.

[0040] Display 132 displays data such as images, videos, and text under the control of control unit 180. Display 132 is realized by, for example, an LCD (Liquid Crystal Display), an organic EL (Electro-Luminescence) display, or the like.

[0041] The audio processing unit 140 modulates and demodulates audio signals. The audio processing unit 140 modulates a signal provided from the microphone 141 and provides the modulated signal to the control unit 180. The audio processing unit 140 also provides the audio signal to the speaker 142. The audio processing unit 140 is realized, for example, by a processor for audio processing. The microphone 141 accepts audio input and provides an audio signal corresponding to the audio input to the audio processing unit 140. The speaker 142 converts the audio signal provided from the audio processing unit 140 into audio and outputs the audio to the outside of the user side terminal device 10.

[0042] The camera 150 is a device that receives light with a light receiving element and outputs the received light as a captured image. The camera 150 is, for example, a depth camera that can detect the distance from the camera 150 to a subject being photographed.

[0043] The storage unit 160 is configured with, for example, a flash memory or the like, and stores data and programs used by the user terminal device 10. In one aspect, the storage unit 160 stores user information 161, patient information 162, patient condition information 163, and medical interview information 164.

[0044] User information 161 is information about a user who is a medical professional such as a doctor who treats a patient. The user information includes information about a user ID, information about the user's name, information about users to which the user belongs, and the like.

[0045] Patient information 162 is information about a patient treated by the user. Patient information includes information about the patient ID, information about the patient's name, information about the patient's age, information about the patient's sex, the patient's medical history, information about the patient's chief complaint, etc. Here, information about the patient's chief complaint is information about the symptoms that led the patient to seek medical treatment, and information about the symptoms reported by the patient.

[0046] Patient condition information 163 is information about the patient's condition during medical treatment. This patient condition information includes first patient condition information acquired based on information about the patient's chief complaint and second patient condition information acquired based on information other than the patient's chief complaint. The first patient condition information is information about the patient's chief complaint, i.e., information about the symptoms that led the patient to seek medical treatment, and is acquired based on information about the symptoms reported by the patient. The second patient condition information is information acquired based on information other than the patient's chief complaint. Information other than the patient's chief complaint includes information about the patient's speech and voice, information about the patient's appearance such as the patient's facial expression, complexion, appearance, and posture, and information about the patient's biological information such as the patient's body temperature, pulse, blood pressure, and respiration, and includes any information about the patient that can be acquired without a diagnosis by a medical professional such as a doctor. Note that the patient's speech includes, for example, the speaking style, the accuracy of what is spoken (e.g., whether the patient is speaking at a level that is understandable to the other person), the tone of speech, etc., but is distinguished from the patient's chief complaint, which is related to the patient's symptoms.

[0047] The control unit 170 reads a program stored in the storage unit 160 and executes instructions included in the program to control the operation of the user terminal device 10. The control unit 170 is, for example, an application that is pre-installed in the user terminal device 10. The control unit 170 operates in accordance with the program to fulfill the functions of an input operation reception unit 171, a transmission / reception unit 172, a notification control unit 173, and a data processing unit 174.

[0048] The input operation receiving unit 171 performs processing to receive a user's input operation on an input device such as the touch-sensitive device 131. Based on information on the coordinates where the user has touched the touch-sensitive device 131 with a finger or the like, the input operation receiving unit 171 determines the type of operation, such as whether the user's operation is a flick operation, a tap operation, or a drag (swipe) operation.

[0049] The transmitting / receiving unit 172 performs processing for the user terminal device 10 to transmit and receive data to and from external devices such as the server 20 in accordance with a communication protocol.

[0050] The notification control unit 173 performs processing to present information to the doctor who is the user. The notification control unit 183 performs processing to display a display image on the display 132, processing to output sound to the speaker 142, and the like.

[0051] The data processing unit 174 performs calculations on the data that the user terminal device 10 has received as input in accordance with a program, and outputs the calculation results to a memory or the like.

[0052] <1.3 Functional configuration of server 20> 3 is a diagram showing the functional configuration of the server 20. As shown in FIG. 3, the server 20 functions as a communication unit 201, a storage unit 202, and a control unit 203.

[0053] The communication unit 201 performs processing for the server 20 to communicate with external devices.

[0054] The storage unit 202 stores a reference tag information management database 2021, a reference suspected disease information management database 2022, a patient information management database 2023, patient condition information 2024, tag information 2025, suspected disease information 2026, and a reference question information management database 2027.

[0055] The reference tag information management database 2021 is a database for managing reference tag information that is associated with patient condition information (first patient condition information, second patient condition information) received during medical treatment and that is referenced by the server 20 to extract tag information related to cases of a specific disease. The reference tag information management database 2021 stores reference patient condition information related to unspecified patients and reference tag information associated with the reference patient condition information. The reference tag information is information related to cases associated with the reference patient condition information. The information related to cases includes, for example, information representing the characteristics of symptoms that occur when a specific disease develops. The reference patient condition information and the reference tag information stored in the reference tag information management database 2021 are not limited to being associated with one each. For example, multiple reference tag information may be associated and stored with one reference patient condition information, or multiple reference patient condition information may be stored with one reference tag information. The reference tag information management database 2021 will be described in detail below.

[0056] The reference estimated disease information management database 2022 is a database for managing reference estimated disease information that is referenced by the server 20 to generate estimated disease information for patients based on the extracted tag information. The reference estimated disease information management database 2022 stores reference tag information and reference estimated disease information associated with the reference tag information. The reference estimated disease information is information about diseases that may be causes of the cases included in the reference tag information. The disease information includes information that represents the characteristics of the disease, such as information about a specific disease and information about the general name of the disease. The reference tag information and reference estimated disease information stored in the reference estimated disease information management database 2022 are not limited to being associated with one each. For example, multiple reference estimated disease information may be associated and stored with one reference tag information, or multiple reference tag information may be stored with one reference estimated disease information. The reference estimated disease information management database 2022 will be described in detail below.

[0057] The patient information management database 2023 is a database for managing various types of information relating to patients treated by the user. Details of the patient information management database 2023 will be described later.

[0058] The patient condition information 2024 is information that indicates the patient's condition, such as the patient's symptoms, received during medical treatment. The patient condition information includes first patient condition information and second patient condition information. The first patient condition information is information about the patient's chief complaint, i.e., information about the symptoms that led the patient to seek medical treatment, and is information obtained based on information about the symptoms reported by the patient. The second patient condition information is information obtained based on information other than the patient's chief complaint. Information other than the patient's chief complaint includes information about the patient's speech and voice, information about the patient's appearance, such as the patient's facial expression, complexion, appearance, and posture, and information about the patient's biological information, such as the patient's temperature, pulse, blood pressure, and respiration, and includes any information about the patient that can be obtained without a diagnosis by a medical professional such as a doctor.

[0059] The tag information 2025 is information about a case associated with the patient condition information (first patient condition information, second patient condition information). The information about a case includes, for example, information that describes the characteristics of symptoms that occur when a specific disease develops. The tag information 2025 is extracted by the server 20 based on the patient condition information (first patient condition information, second patient condition information) received at the time of medical treatment, by referring to the information stored in the reference tag information management database 2021. This tag information also includes modified tag information that is modified by an operation by a medical professional.

[0060] The suspected disease information 2026 is information about diseases that may be the cause of the cases included in the extracted tag information. The information about diseases includes information that expresses the characteristics of the disease, such as information about specific diseases and information about generic names of diseases. The suspected disease information 2026 is generated by the server 20 based on the extracted tag information and by referring to the information stored in the reference suspected disease information management database 2022.

[0061] The reference question information management database 2027 is a database for managing reference question information that is referenced to generate information regarding questions for patients to be presented to medical professionals based on the generated suspected disease information. The reference question information management database 2027 stores reference suspected disease information and reference question information associated with the reference suspected disease information. The reference question information is information regarding questions asked of an unspecified patient (anticipated patient) to more accurately determine whether the disease corresponding to the reference suspected disease information associated with the reference question information is a disease that the patient has. This reference information corresponds to question information presented to medical professionals providing medical care, and, for example, when the suspected disease information is depression, it includes multiple reference question information associated with the suspected disease information. Details of the reference question information management database 2027 will be described later.

[0062] The control unit 203 is realized by the processor 29 reading a program stored in the storage unit 202 and executing instructions included in the program. By operating in accordance with the program, the control unit 203 exhibits functions shown as a reception control module 2031, a transmission control module 2032, a patient information acquisition module 2033, a patient condition information acquisition module 2034, a tag information extraction module 2035, a consistency evaluation module 2036, a tag information correction module 2037, an estimated disease information generation module 2038, a reliability evaluation module 2039, and a question information generation module 2040.

[0063] The reception control module 2031 controls the process by which the server 20 receives signals from external devices in accordance with a communication protocol.

[0064] The transmission control module 2032 controls the process in which the server 20 transmits signals to external devices in accordance with a communication protocol.

[0065] The patient information acquisition module 2033 performs a series of processes for managing information about patients receiving medical treatment. The patient information includes information about the patient's ID, name, age, sex, contact information, and medical history. The patient information acquisition module 2033 stores the acquired patient information in the patient information management database 2023.

[0066] The patient condition information acquisition module 2034 performs a series of processes to acquire patient condition information regarding the patient's condition acquired during medical treatment. The patient condition information includes first patient condition information acquired based on information regarding the patient's chief complaint and second patient condition information acquired based on information other than the patient's chief complaint. The first patient condition information includes patient condition information acquired by a user who is a medical professional providing medical care through medical treatment such as interviewing and examining the patient, and patient condition information acquired by the medical institution terminal device 40. The second patient condition information includes patient condition information acquired by a user who is a medical professional providing medical care through medical treatment such as interviewing and examining the patient, and patient condition information acquired by the medical institution terminal device 40. The patient condition information acquisition module 2034 stores the acquired patient condition information in the storage unit 202.

[0067] The tag information extraction module 2035 performs a series of processes to extract tag information associated with the received patient condition information. Specifically, the tag information extraction module 2035 references the information (reference patient condition information and reference tag information) stored in the reference tag information management database 2021, and extracts a first tag group including at least one tag information related to a case associated with first patient condition information derived from information related to the patient's chief complaint. The tag information extraction module 2035 also references the information (reference patient condition information and reference tag information) stored in the reference tag information management database 2021, and extracts a second tag group including at least one tag information related to a case associated with second patient condition information derived from information other than the patient's chief complaint. The first tag group and the second tag group extracted by the tag information extraction module 2035 each include at least one tag information.

[0068] Tag information is information about a case associated with patient condition information (first patient condition information, second patient condition information). Information about a case includes, for example, information that describes the characteristics of symptoms that occur when a specific disease develops. For example, in the case of a mental illness, tag information includes information such as "decreased interest," "depressed mood," "decreased appetite," and "weight loss." The tag information extraction module 2035 stores the extracted tag information in the storage unit 202.

[0069] The consistency evaluation module 2036 performs a series of processes to evaluate the consistency between tag information included in at least one of the extracted first tag group and the extracted second tag group. Specifically, the consistency evaluation module 2036 evaluates whether the consistency between tag information included in at least one of the extracted first tag group and the extracted second tag group is at or above a predetermined level. For example, when the extracted first tag group includes multiple pieces of tag information, the consistency evaluation module 2036 evaluates whether the consistency between tag information selected from the multiple pieces of tag information included in the first tag group is at or above a predetermined level. For another example, when the extracted second tag group includes multiple pieces of tag information, the consistency evaluation module 2036 evaluates whether the consistency between tag information selected from the multiple pieces of tag information included in the second tag group is at or above a predetermined level. For another example, the consistency evaluation module 2036 evaluates whether the consistency between tag information selected from the multiple pieces of tag information included in the first tag group and the second tag group is at or above a predetermined level. For example, the consistency evaluation module 2036 evaluates whether the consistency between the tag information included in the first tag group (if multiple tag information is included, tag information selected from the multiple tag information) and the tag information included in the second tag group (if multiple tag information is included, tag information selected from the multiple tag information) is at or above a predetermined level.

[0070] The consistency between tag information is information related to an index for evaluating the degree to which the tag information to be compared is consistent as information for generating specific estimated disease information. Consistency at or above a predetermined level represents an index for determining whether the consistency meets a predetermined standard, and indicates that the consistency between the tag information included in at least one of the extracted first tag group and second tag group is at a level that allows estimated disease information to be generated with sufficient accuracy.

[0071] For example, the consistency evaluation module 2036 evaluates the consistency between the tag information to be at least a predetermined level when at least one of the extracted first tag group and second tag group contains a predetermined number of tag information items that are consistent with each other. Consistency means, for example, that the compared tag information items match, or that the degree of association between the compared tag information items is at least a predetermined level, thereby indicating that the compared tag information items are tag information items that are associated with the same estimated disease information. The degree of association between the tag information items is a measure indicating whether the compared tag information items are associated with each other, and is determined, for example, based on classification information previously assigned to each tag information item. Classification information is, for example, symbolized or quantified information associated with information related to a specific disease, and by referring to the classification information, it is possible to determine the degree of association between the compared tag information items. Note that the degree of association is not limited to this, and various indicators can be used to determine the degree of association between the compared tag information items. As a specific example, when a condition is set that three or more pieces of tag information associated with presumed disease information are required to generate presumed disease information about a specific disease, if either the extracted first tag group or the extracted second tag group contains three or more pieces of tag information that are consistent with each other, the consistency between the tag information is evaluated to be at a predetermined level or above. In this case, the extracted three or more pieces of tag information may be identical to each other or may be different (different within the scope of maintaining consistency).

[0072] Furthermore, for example, if the degree of association between tag information included in at least one of the extracted first tag group and the extracted second tag group is equal to or greater than a predetermined level, the consistency evaluation module 2036 evaluates that the consistency between the tag information is equal to or greater than a predetermined level. The degree of association between tag information is a measure indicating whether the compared tag information is associated with each other, and is determined, for example, based on classification information previously assigned to each tag information. The classification information is, for example, symbolized or quantified information associated with information related to a specific disease, and by referring to the classification information, it is possible to determine the degree to which the compared tag information is associated with each other. As a specific example, each piece of extracted tag information is assigned quantified classification information, and if the numerical difference between the compared tag information is within a predetermined range (e.g., 0 to 5), the consistency between the tag information is evaluated to be equal to or greater than a predetermined level. On the other hand, if the tag information being compared is associated with common suspected disease information but the numerical values ​​of the tag information being compared are not within a predetermined range, for example, if the two tag information being compared are associated with the suspected disease information of "depression," but there is a large difference in the numerical information between the two tag information, such as "depressed mood (e.g., numerical value: 30)" and "medication overdose (e.g., numerical value: 70)," (in this case, the numerical difference: 40), and there is no correlation between the tag information that may be a factor in the suspected disease information, the consistency between the tag information is evaluated to be below a predetermined level. Note that the degree of correlation is not limited to this and can be determined using various indices.

[0073] On the other hand, if the above requirements are not met, the consistency evaluation module 2036 can evaluate that the consistency is not at a predetermined level or above. Specifically, the consistency evaluation module 2036 evaluates that the consistency is not at a predetermined level or above when at least one of the extracted first tag group and second tag group does not contain a predetermined number of mutually consistent tag information. Furthermore, the consistency evaluation module 2036 evaluates that the consistency is not at a predetermined level or above when the degree of association between tag information included in at least one of the extracted first tag group and second tag group is not at a predetermined level or above.

[0074] Furthermore, the consistency evaluation module 2036 can evaluate that the consistency is not at a predetermined level or above when tag information of at least one of the extracted first tag group and second tag group contains tag information that is incompatible with each other. Examples of tag information that is incompatible with each other include tag information where one tag information is associated with certain suspected disease information and the other tag information is not associated with this suspected disease information, or tag information that denies the possibility of this suspected disease information. For example, when information about a patient's chief complaint is obtained, there may be cases where the information about the chief complaint that the patient wrote on the medical questionnaire and the information about the chief complaint obtained during a face-to-face interview with a medical professional contain contradictory information (for example, the medical questionnaire contains information about the chief complaint indicating that there is no change in the patient's physical condition, but the face-to-face interview reveals information about the chief complaint indicating that the patient has had a fever for several days), or there may be cases where information about the chief complaint from the patient through the interview, etc. contains contradictory information about information other than the chief complaint that is obtained during an examination by a medical professional (for example, the medical interview reveals information about the chief complaint indicating that the patient has no fever, but the examination reveals information about the patient's body temperature indicating a fever as information other than the chief complaint), and in these cases, tag information with mutually incompatible combinations may occur.

[0075] The tag information correction module 2037 performs a series of processes to correct the extracted tag information. The extracted tag information may not always be appropriate. In such cases, the tag information can be corrected by, for example, a medical professional. The tag information is corrected by at least one of replacing tag information included in either the first tag group or the second tag group extracted before the correction with new tag information, deleting tag information included in either the first tag group or the second tag group extracted before the correction, or adding tag information not included in either the first tag group or the second tag group extracted before the correction. When an operation to correct tag information is received from the user-side terminal device 10 by, for example, a medical professional user, the tag information correction module 2037 corrects the extracted tag information. The tag information correction module 2037 stores the corrected tag information in the storage unit 202.

[0076] The estimated disease information generation module 2038 performs a series of processes for generating estimated disease information based on the extracted tag information. Specifically, the estimated disease information generation module 2038 references the information (reference tag information and reference estimated disease information) stored in the reference estimated disease information management database 2022, and generates at least one piece of estimated disease information based on tag information related to the evaluation that the consistency is evaluated to be at least a predetermined level. The estimated disease information generation module 2038 can not only generate one piece of estimated disease information based on one piece of tag information, but also generate multiple pieces of estimated disease information based on one piece of tag information. Furthermore, the estimated disease information generation module 2038 can generate one piece of estimated disease information based on multiple pieces of tag information. The estimated disease information is information about a disease that is estimated to have developed in a patient at the time of medical treatment, and includes information about a specific disease, information about a specific disease name, etc. Information about a specific disease includes information about chronic respiratory diseases, neurological diseases, psychiatric diseases, etc. Information about a specific disease name includes information about bronchial asthma, Parkinson's disease, schizophrenia, dementia, etc. The estimated disease information generating module 2038 stores the generated estimated disease information in the storage unit 202.

[0077] The reliability evaluation module 2039 performs a series of processes to evaluate the reliability of the generated estimated disease information. Specifically, the reliability evaluation module 2039 evaluates the reliability of the generated estimated disease information by referring to extracted tag information associated with the generated estimated disease information. Reliability is information related to a measure indicating the degree to which the generated estimated disease information is reliable as estimated information. For example, the reliability evaluation module 2039 can evaluate the generated estimated disease information as having a higher reliability the more extracted tag information associated with the generated estimated disease information. Furthermore, for example, the reliability evaluation module 2039 can evaluate the generated estimated disease information as having a high reliability if the extracted tag information associated with the generated estimated disease information includes tag information associated with a major cause of the estimated disease information. This reliability evaluation is an example, and the reliability evaluation module 2039 can evaluate the reliability of the generated estimated disease information based on various criteria. The evaluation results evaluated by the reliability evaluation module 2039 can be expressed as information related to various indicators, such as symbolic information (rating: A, B, C, etc.), numerical information (rating: 10, 50, 100, etc.), and textual information (rating: high reliability, medium reliability, low reliability, etc.).

[0078] The question information generation module 2040 performs a series of processes to generate information regarding questions to be presented to a medical professional based on the generated suspected disease information. Specifically, the question information generation module 2040 references information (reference suspected disease information and reference question information) stored in the reference question information management database 2027 and generates question information regarding questions to be asked to a patient during medical treatment based on the generated suspected disease information. The question information is information presented to a patient to improve the accuracy of the suspected disease information and more accurately diagnose the patient's symptoms and disease. The question information generation module 2040 can generate question information based not only on the generated suspected disease information but also on other information. For example, if the evaluation of the consistency of tag information indicates that the consistency is not at a predetermined level or higher and no suspected disease information is generated, the question information generation module 2040 can generate question information for extracting tag information necessary to generate suspected disease information. The question information generation module 2040 generates information regarding questions to be asked to a patient by reference to information stored in the reference question information management database 2027.

[0079] <2 Data Structure> 4 to 9 are diagrams showing the data structures of databases stored in the server 20. Note that Figs. 4 to 9 are merely examples and do not exclude data not shown.

[0080] 4 is a diagram showing the data structure of the reference tag information management database 2021. Each record in the reference tag information management database 2021 includes an item "information ID," an item "reference patient condition information," and an item "reference tag information." In the illustrated example, five data examples are shown, but the present invention is not limited to this.

[0081] The item "information ID" is information for identifying the reference tag information to be managed.

[0082] The item "reference patient condition information" is information about the condition of an unspecified patient, and is reference information that can be compared with information about the condition of the patient being treated that is obtained during medical treatment. Examples of this reference information include "stopped watching TV," "constantly sad," "no appetite," "has paranoia," and "disorganized speech."

[0083] The item "Reference tag information" is information associated with the reference patient condition information, and is reference information that includes information that describes the characteristics of symptoms that occur when an unspecified patient develops a specific disease. Examples of this reference information include "decreased interest," "depressed mood," "decreased appetite and weight loss," "delusions," and "disorganized conversation."

[0084] 5 is a diagram showing the data structure of the reference suspected disease information management database 2022. Each record in the reference tag information management database 2021 includes an item "information ID," an item "reference tag information," and an item "reference suspected disease information." In the illustrated example, five data examples are shown, but the number is not limited to this.

[0085] The item "information ID" is information for identifying the reference suspected disease information to be managed.

[0086] The item "Reference tag information" is information associated with the reference patient condition information, and is reference information that includes information that describes the characteristics of symptoms that may occur when an unspecified patient develops a specific disease. Examples of this reference information include "decreased interest," "depressed mood," "decreased appetite and weight loss," "delusions," and "disorganized conversation."

[0087] The item "Reference suspected disease information" is information associated with the reference tag information, and is reference information including information indicating diseases that may be factors in the onset of specific symptom characteristics in unspecified patients. This reference information includes, for example, information on specific cases such as "depression," "dementia," and "schizophrenia."

[0088] 6 is a diagram showing the data structure of the patient information management database 2023. Each record in the patient information management database 2023 includes an item "Patient ID," an item "Patient Name," an item "Patient Age," an item "Patient Gender," an item "Patient Contact Information," and an item "Medical History Information." In the illustrated example, three data examples are shown, but the present invention is not limited to these.

[0089] The item "patient ID" is information that identifies each patient who is the subject of medical treatment.

[0090] The item "patient name" is information indicating the name of the patient.

[0091] The item "patient age" is information indicating the age of the patient.

[0092] The item "patient gender" is information indicating the gender of the patient.

[0093] The item "Patient Contact Information" is information indicating the patient's contact information. Examples of the information indicating the patient's contact information include an email address and a telephone number.

[0094] The item "Medical History Information" is information about the history of medical treatments that the patient has received at the medical institution in question. Information about the medical treatment history includes, for example, the date of the treatment, the details of the diagnosis made at the time of the treatment, the details of the prescribed medication, etc.

[0095] 7 is a diagram showing the data structure of the reference question information management database 2027. Each record in the reference question information management database 2027 includes an item "information ID," an item "reference suspected disease information," and an item "reference question information." In the illustrated example, six data examples are shown, but the number is not limited to this.

[0096] The item "information ID" is information for identifying the reference suspected disease information to be managed.

[0097] The item "Reference suspected disease information" is information associated with the reference tag information, and is reference information including information indicating diseases that may be factors in the onset of specific symptom characteristics in unspecified patients. This reference information includes, for example, information on specific cases such as "depression," "dementia," and "schizophrenia."

[0098] The item "reference question information" is information associated with the presumed disease information, and is information regarding questions to be asked to the patient to more accurately determine whether the generated presumed disease information is a disease that the patient is being treated for. This reference information corresponds to question information presented to medical professionals who are providing medical treatment, and for example, if the presumed disease information is depression, it includes multiple pieces of reference question information associated with the presumed disease information.

[0099] <3 operations> Next, the operation of each device constituting the medical assistance system 1 will be described.

[0100] <3.1 Operation example 1> 8 is a diagram showing the flow of processing related to medical support for a patient via the server 20. In the following example, a user who is a medical professional providing medical care provides medical care to a patient, extracts tag information based on first patient condition information acquired by a preliminary interview with the patient and second patient condition information acquired during the medical care, generates estimated disease information for the patient based on the extracted tag information, and presents the information to the user.

[0101] In step S671, the medical institution terminal device 40 acquires first patient condition information regarding the patient's condition based on information regarding the patient's chief complaint from the patient, and transmits the acquired first patient condition information to the user terminal device 10. The first patient condition information is acquired, for example, based on information regarding the patient's chief complaint regarding symptoms that the patient has filled out in a questionnaire during a pre-examination before the patient's consultation. The first patient condition information is transmitted to the user terminal device 10 by an operator of the medical institution operating the medical institution terminal device 40.

[0102] In step S601, the user terminal device 10 accepts input of first patient condition information transmitted from the medical institution terminal device 40. The user terminal device 10 can also accept input of first patient condition information acquired by a medical interview conducted by a user who is a medical professional providing medical care to the patient. The accepted first patient condition information is transmitted to the server 20 by the user operating the user terminal device 10.

[0103] In step S631, the server 20 extracts a first tag group, which is information associated with the first patient condition information and includes tag information related to cases of a specific disease, based on the first patient condition information transmitted from the user terminal device 10. The first tag group includes multiple pieces of tag information associated with the acquired first patient condition information.

[0104] In step S651, the external input device 30 acquires second patient condition information by acquiring and analyzing information about the patient's appearance, etc., and transmits the acquired second patient condition information to the server 20. The second patient condition information is acquired by acquiring and analyzing information about the patient's appearance, such as the patient's facial expression, complexion, appearance, and posture. The second patient condition information is not limited to information about the patient's appearance, but can also be acquired by acquiring and analyzing information about the patient's speech and voice, or by acquiring and analyzing the patient's biological information, such as the patient's body temperature, pulse, blood pressure, and respiration. The second patient condition information is transmitted to the user terminal device 10 by automatic processing from the external input device 30 or by operation by the operator of the external input device 30.

[0105] In step S602, the user terminal device 10 accepts input of second patient condition information transmitted from the external input device 30. The user terminal device 10 can also accept input of second patient condition information acquired through an examination of the patient by a user who is a medical professional providing medical care. The accepted second patient condition information is transmitted to the server 20 by the user operating the user terminal device 10.

[0106] In step S632, the server 20 extracts a second tag group, which is information associated with the second patient condition information and includes tag information related to cases of a specific disease, based on the second patient condition information transmitted from the user terminal device 10. The second tag group includes multiple pieces of tag information associated with the acquired second patient condition information.

[0107] In step S633, the server 20 evaluates the consistency between the tag information included in at least one of the extracted first tag group and second tag group. Here, the server 20 evaluates whether the consistency between the tag information included in at least one of the extracted first tag group and second tag group is at or above a predetermined level. Specifically, the server 20 evaluates that the consistency is at or above a predetermined level when at least one of the extracted first tag group and second tag group contains at least a predetermined number of pieces of tag information that are consistent with each other.

[0108] In step S634, if the server 20 evaluates that the consistency between the tag information contained in at least one of the extracted first tag group and second tag group is at a predetermined level or above, i.e., if the server 20 evaluates that at least one of the extracted first tag group and second tag group contains a predetermined number or more of tag information that is consistent with each other, it generates estimated disease information regarding the estimated disease of the patient based on the tag information related to the evaluation.

[0109] In step S635, the server 20 presents the generated inferred disease information to the user, who is a medical professional. In this case, the generated inferred disease information is transmitted from the server 20 to the user terminal device 10 and displayed on the display screen of the user terminal device 10.

[0110] <3.2 Operation example 2> 9 is a diagram showing another example of the flow of processing related to medical care support for patients via the server 20. In the following example, an example of processing will be described in which the consistency between tag information included in at least one of the extracted first tag group and second tag group is not at a predetermined level or higher. Note that the processing up to the extraction of the first tag group and the second tag group is the same as in Operation Example 1, so a description thereof will be omitted.

[0111] In step S731, the server 20 evaluates the consistency between the tag information included in at least one of the extracted first tag group and second tag group.

[0112] In step S732, if the server 20 determines that the consistency between the tag information included in at least one of the extracted first tag group and the second tag group is not at a predetermined level or above, it presents the result of the evaluation (evaluation result) to the user. Specifically, if either the first tag group or the second tag group does not contain a predetermined number of mutually consistent tag information or if at least one of the first tag group and the second tag group contains tag information that is inappropriate for combination with each other, the consistency is determined to be not at a predetermined level or above, and the evaluation result is presented to the user. In this case, information related to the evaluation result is transmitted from the server 20 to the user terminal device 10 and displayed on the display screen of the user terminal device 10. The information related to the evaluation result may include, for example, information on the reason why the consistency was determined to be not at a predetermined level or above, information listing the tag information whose consistency was determined to be not at a predetermined level or above, information prompting the user to correct the tag information, etc.

[0113] <3.3 Operation example 3> 10 is a diagram showing another example of the flow of processing related to medical care support for patients via the server 20. In the following example, an example of processing is described in which corrections to extracted tag information are accepted from a user, and the consistency of the tag information is evaluated based on the corrected tag information. Note that the processing up to the extraction of the first tag group and the second tag group is the same as in Operation Example 1, and therefore a description thereof is omitted.

[0114] In step S831, the server 20 presents the tag information included in at least one of the extracted first tag group and second tag group to the user. In this case, the tag information is transmitted from the server 20 to the user terminal device 10 and displayed on the display screen of the user terminal device 10.

[0115] In step S801, the user terminal device 10 accepts an operation from the user to modify the presented tag information. The user modifies the tag information by at least one of replacing tag information included in either the first tag group or the second tag group extracted before the modification with new tag information, deleting tag information included in either the first tag group or the second tag group extracted before the modification, or adding tag information not included in either the first tag group or the second tag group extracted before the modification. The user uses the user terminal device 10 to transmit the modified tag information to the server 20.

[0116] In step S832, the server 20 evaluates the consistency between the tag information included in at least one of the first tag group and the second tag group based on the received corrected tag information. The processing from this step onwards is the same as in Operation Example 1, so a description thereof will be omitted.

[0117] <3.4 Operation example 4> 11 is a diagram showing another example of the flow of processing related to medical care support for patients via the server 20. In the following example, an example of processing is described in which question information to be asked of the patient is generated based on the generated estimated disease information and presented to the user. Note that the processing up to the generation of the estimated disease information is the same as in Operation Example 1, so a description thereof is omitted.

[0118] In step S931, the server 20 generates question information to be posed to the patient based on the generated suspected disease information. The number of question information generated may be one or more.

[0119] In step S932, the server 20 presents the generated question information to the user. If there are multiple pieces of generated question information, the display order can be set based on information such as a priority assigned in advance.

[0120] <4 Screen example> Next, examples of screens showing various types of information extracted and generated in the processing of the medical support system 1 will be described.

[0121] <4.1 Screen example 1> FIG. 12 is a diagram showing an example of a screen of suspected disease information presented to the user.

[0122] 12 is an example of a screen in which the suspected disease information of a patient generated by the server 20 is displayed on the display screen of the user terminal device 10 of a user who is a medical professional. This corresponds to the processing of step S637 in FIG.

[0123] As shown in Figure 12, this screen example 1000 displays, on the user side terminal device 10, an area 1010 for displaying information regarding the patient's consultation date, an area 1020 for displaying information regarding the patient's name, an area 1030 for displaying information regarding patient condition information obtained during consultation, an area 1040 for displaying tag information associated with the patient condition information, an area 1050 for displaying estimated disease information generated based on the tag information, and an area 1060 for displaying information regarding the reliability of each estimated disease information.

[0124] Area 1010 may display information regarding the date the patient was seen.

[0125] Information relating to the name of the patient who is the subject of medical treatment can be displayed in area 1020. Information other than the patient's name, such as the patient ID, age, and sex, can also be displayed in this area 1020.

[0126] First patient condition information acquired based on information related to the patient's chief complaint and second patient condition information acquired based on information other than the patient's chief complaint can be displayed in area 1030. In this case, the first patient condition information and the second patient condition information can be displayed so that they can be distinguished from each other.

[0127] Tag information included in a first tag group extracted based on the acquired first patient condition information and tag information included in a second tag group extracted based on the acquired second patient condition information can be displayed in area 1040. In this case, it is also possible to display each piece of tag information in such a way that it can be distinguished whether it belongs to the first tag group or the second tag group.

[0128] The consistency between the tag information included in the first tag group and the tag information included in the second tag group is evaluated, and suspected disease information generated when the consistency between the tag information included in the first tag group and the tag information included in the second tag group is evaluated to be at a predetermined level or higher can be displayed in area 1050. One or more pieces of suspected disease information can be displayed in area 1050.

[0129] Information about the reliability of each piece of generated estimated disease information can be displayed in area 1060. The information about the reliability displayed in area 1060 can be displayed in various forms, such as not only symbolized information such as A, B, and C, but also numerical information.

[0130] <4.2 Screen example 2> 13 is a diagram showing an example of a screen showing the evaluation result of the consistency of tag information presented to the user. This screen example shows the determination result when the estimated disease information is not generated as a result of the evaluation of the consistency of tag information.

[0131] As shown in Figure 13, this screen example 1100 displays, on the user side terminal device 10, an area 1110 for displaying information regarding the patient's consultation date, an area 1120 for displaying information regarding the patient's name, an area 1130 for displaying information regarding patient condition information obtained during consultation, an area 1140 for displaying tag information associated with the patient condition information, an area 1150 for displaying estimated disease information generated based on the tag information, an area 1160 for displaying information regarding the reliability of the estimated disease information, an area 1170 for displaying information regarding the consistency evaluation results, and an area 1180 for displaying information regarding the reasons for the evaluation results.

[0132] Area 1110 may display information regarding the date the patient was seen.

[0133] Information relating to the name of the patient who is the subject of medical treatment can be displayed in area 1120. Information other than the patient's name, such as the patient ID, age, and sex, can also be displayed in this area 1120.

[0134] First patient condition information obtained based on information about the patient's chief complaint and second patient condition information obtained based on information other than the patient's chief complaint can be displayed in area 1130. In this case, the first patient condition information and the second patient condition information can be displayed so that they can be distinguished from each other.

[0135] Tag information included in a first tag group extracted based on the acquired first patient condition information and tag information included in a second tag group extracted based on the acquired second patient condition information can be displayed in area 1140. In this case, it is also possible to display each piece of tag information in such a way that it can be distinguished whether it belongs to the first tag group or the second tag group.

[0136] The consistency between the tag information included in the first tag group and the tag information included in the second tag group is evaluated, and estimated disease information generated when the consistency between the tag information included in the first tag group and the tag information included in the second tag group is evaluated to be at or above a predetermined level can be displayed in area 1150. In this example screen, the consistency is evaluated to be below the predetermined level, so the estimated disease information is not displayed.

[0137] Information about the reliability of each piece of generated estimated disease information can be displayed in the area 1160. In this example screen, no estimated disease information has been generated, so information about the reliability is not displayed.

[0138] Information indicating that no estimated disease information has been generated and information prompting an operation to add new patient condition information can be displayed in the area 1170. The information displayed in the area 1170 is not limited to this.

[0139] Information indicating the reason why estimated disease information was not generated can be displayed in area 1180. In this example screen, information indicating that the amount of extracted tag information is small is displayed as the reason why the consistency is not at a predetermined level or higher. The information displayed in area 1180 is not limited to this.

[0140] <4.3 Screen example 3> FIG. 14 is a diagram showing another example of a screen showing the evaluation result regarding the consistency of tag information presented to the user.

[0141] 14 is a diagram showing an example of a screen showing the evaluation result of the consistency of tag information presented to the user. This screen example shows the determination result when the estimated disease information is not generated as a result of the evaluation of the consistency of tag information.

[0142] As shown in Figure 14, this screen example 1200 displays, on the user side terminal device 10, an area 1210 for displaying information regarding the patient's consultation date, an area 1220 for displaying information regarding the patient's name, an area 1230 for displaying information regarding patient condition information obtained during consultation, an area 1240 for displaying tag information associated with the patient condition information, an area 1250 for displaying estimated disease information generated based on the tag information, an area 1260 for displaying information regarding the reliability of the estimated disease information, an area 1270 for displaying information regarding the consistency evaluation results, and an area 1280 for displaying information regarding the reasons for the evaluation results.

[0143] Area 1210 may display information regarding the date the patient was seen.

[0144] Information relating to the name of the patient who is the subject of medical treatment can be displayed in area 1220. Information other than the patient's name, such as the patient ID, age, and gender, can also be displayed in this area 1220.

[0145] First patient condition information acquired based on information related to the patient's chief complaint and second patient condition information acquired based on information other than the patient's chief complaint can be displayed in area 1230. In this case, the first patient condition information and the second patient condition information can be displayed so that they can be distinguished from each other.

[0146] Tag information included in a first tag group extracted based on the acquired first patient condition information and tag information included in a second tag group extracted based on the acquired second patient condition information can be displayed in area 1240. In this case, it is also possible to display each piece of tag information in a manner that allows the user to distinguish whether it belongs to the first tag group or the second tag group.

[0147] The consistency between the tag information included in the first tag group and the tag information included in the second tag group is evaluated, and the estimated disease information generated when the consistency between the tag information included in the first tag group and the tag information included in the second tag group is evaluated to be at or above a predetermined level can be displayed in area 1250. In this example screen, this corresponds to the case where tag information that is an inappropriate combination is included between the first tag group and the second tag group, and the consistency is evaluated to be below a predetermined level, so the estimated disease information is not displayed.

[0148] Information about the reliability of each piece of generated estimated disease information can be displayed in the area 1260. In this example screen, no estimated disease information has been generated, so information about the reliability is not displayed.

[0149] Information indicating that estimated disease information has not been generated and information prompting the user to review the patient condition information can be displayed in the area 1270. The information displayed in the area 1270 is not limited to this.

[0150] Information indicating the reason why estimated disease information was not generated can be displayed in area 1280. In this example screen, the reason why the consistency is not at a predetermined level or higher is that tag information that is not a suitable combination is included between the first tag group and the second tag group, specifically, information indicating that there is a contradiction between the two pieces of extracted tag information is displayed. The information displayed in area 1080 is not limited to this.

[0151] <4.4 Screen example 4> FIG. 15 is a diagram showing an example of a screen for a user to modify tag information.

[0152] As shown in FIG. 15, this example screen 1300 displays, on the user side terminal device 10, an area 1310 for displaying information prompting the user to modify tag information, an area 1320 for displaying check boxes corresponding to each tag information, an area 1330 for displaying tag information, an area 1340 for displaying patient condition information associated with the tag information, an area 1350 for displaying information guiding the user to modify the tag information, and an area 1360 for displaying information guiding the user to add tag information.

[0153] Information that prompts the user to check a checkbox to correct the tag information can be displayed in area 1310. The information displayed in area 1310 is not limited to this.

[0154] Area 1320 can display check boxes corresponding to each piece of tag information displayed on the screen. The tag information to be corrected is designated by clicking the check box corresponding to the tag information to be corrected (in the example screen, the tag information "declining interest" is designated). The display manner of the check boxes displayed in area 1310 is not limited to this.

[0155] Tag information included in a first tag group extracted based on the acquired first patient condition information and tag information included in a second tag group extracted based on the acquired second patient condition information can be displayed in area 1330. In this case, it is also possible to display each piece of tag information in a manner that allows the user to distinguish whether it belongs to the first tag group or the second tag group.

[0156] Patient condition information associated with tag information, i.e., first patient condition information acquired based on information about the patient's chief complaint, and second patient condition information acquired based on information other than the patient's chief complaint, can be displayed in area 1340. In this case, the first patient condition information and the second patient condition information can be displayed so that they can be distinguished from each other.

[0157] Area 1350 can display information 1351 guiding an operation to change checked tag information and information 1352 guiding an operation to delete checked tag information, as information guiding an operation for tag information to be corrected. Information 1351 displayed as "Change" includes link information for performing a process to change the tag information. Information 1352 displayed as "Delete" includes link information for performing a process to delete the tag information. After checking the information displayed on the screen, the user specifies a check box corresponding to the tag information they want to correct, and clicks either information 1351 displayed as "Change" or information 1352 displayed as "Delete," thereby performing a process to change or delete the tag information.

[0158] Area 1360 can display information 1361 guiding the operation of adding new tag information as information guiding the operation of tag information to be corrected. Information 1361 displaying "Add" includes link information for performing the process of adding tag information. After checking the information displayed on the screen, the user performs the process of adding tag information by clicking on information 1361 displaying "Add." In this case, there is no need to perform the operation of selecting a check box to specify the tag information to be displayed.

[0159] <5 Variations> A modification of this embodiment will now be described.

[0160] (1) Regarding the first patient condition information obtained from information regarding the patient's chief complaint, in addition to being obtained in a preliminary interview before the consultation, processing may be performed to obtain the information from the medical professional's answers regarding the patient's chief complaint to questions from the medical professional when the medical professional providing the medical treatment is face-to-face with the patient.

[0161] (2) The consistency between tag information included in at least one of the extracted first tag group and the second tag group may be evaluated, and if the consistency is evaluated to be at least a predetermined level, a process may be executed to generate estimated disease information based on the tag information related to the evaluation, and to generate information on the evaluation result indicating that at least one of the first tag group and the second tag group contains tag information that is not related to the consistency evaluation. In this case, the generated estimated disease information and information on the evaluation result indicating that tag information that is not related to the consistency evaluation may be presented to the user. The information on the evaluation result may include, for example, information on why specific tag information was not related to the consistency evaluation, information listing tag information that was not related to the consistency evaluation, information prompting correction of the tag information, etc.

[0162] (3) The first patient condition information acquired by the medical institution terminal device 40 may be transmitted directly to the server 20 without going through the user terminal device 10. In this case, the server 20 receives the input of the first patient condition information, and extracts a first tag group based on the received first patient condition information.

[0163] (4) The second patient condition information acquired by the external input device 30 may be transmitted directly to the server 20 without going through the user terminal device 10. In this case, the server 20 receives the input of the second patient condition information, and extracts a second tag group based on the received first patient condition information.

[0164] As described above, the medical support system 1 of the present disclosure acquires first patient condition information based on information related to the patient's chief complaint, extracts a first tag group based on the acquired first patient condition information, acquires second patient condition information based on information other than the patient's chief complaint, extracts a second tag group based on the acquired second patient condition information, evaluates the consistency between the tag information included in at least one of the extracted first tag group and the second tag group, and if the consistency between the tag information included in at least one of the first tag group and the second tag group is evaluated to be at a predetermined level or higher, generates estimated disease information for the patient based on the tag information related to the evaluation, and presents the generated estimated disease information to a user who is a medical professional. In this way, tag information is extracted based on information related to the patient's condition acquired during medical treatment, and disease estimation is performed based on the tag information after evaluating the eligibility (consistency) of the tag information, thereby making it possible to provide accurate medical support information to a user who is a medical professional.

[0165] Furthermore, according to the medical assistance system 1 of the present disclosure, when at least one of the first tag group and the second tag group contains a predetermined number or more of tag information that is consistent with each other, a process is performed to evaluate the consistency as being at a predetermined level or higher. This improves the accuracy of the tag information used to generate estimated disease information, making it possible to provide more accurate medical assistance information to users who are medical professionals.

[0166] Furthermore, according to the medical assistance system 1 of the present disclosure, when the degree of association between tag information included in at least one of the first tag group and the second tag group is at or above a predetermined level, a process is performed to evaluate the consistency as being at or above a predetermined level. This improves the accuracy of the tag information for generating estimated disease information, making it possible to provide more accurate medical assistance information to users who are medical professionals.

[0167] Furthermore, according to the medical assistance system 1 of the present disclosure, when the consistency is evaluated to be below a predetermined level, processing is performed to present information on the evaluation to the user. This prevents the generation of estimated disease information based on tag information that does not reach sufficient accuracy, thereby preventing users who are not specialized medical professionals from making incorrect diagnoses and making it possible to provide more accurate medical assistance information to users who are medical professionals.

[0168] Furthermore, according to the medical assistance system 1 of the present disclosure, when tag information in at least one of the first tag group and the second tag group contains tag information that is inappropriate for the combination with each other, a process is performed to evaluate the consistency as being below a predetermined level. This prevents the generation of estimated disease information based on tag information that is not an appropriate combination, thereby preventing users, particularly non-specialist medical professionals, from making incorrect diagnoses and making it possible to provide more accurate medical assistance information to users.

[0169] Furthermore, according to the medical assistance system 1 of the present disclosure, tag information included in at least one of the first tag group and the second tag group is presented to the user, an operation to correct the presented tag information is accepted from the user, and a process of evaluating consistency is performed based on the accepted corrected tag information. This provides an opportunity to correct tag information that does not reach a level sufficient for generating estimated disease information, such as when the tag information extracted by the server contains an error or is not accurate enough, thereby improving the accuracy of the tag information and making it possible to provide more accurate medical assistance information to users who are medical professionals.

[0170] Furthermore, according to the medical assistance system 1 of the present disclosure, a process is performed to acquire at least one of information related to the patient's speech, information related to the patient's appearance, information related to the patient's movements, and information related to the patient's body as the second patient condition information. This allows estimated disease information to be generated ultimately based on more accurate patient condition information, making it possible to provide more accurate medical assistance information to the user.

[0171] Furthermore, the medical support system 1 of the present disclosure performs a process of evaluating the reliability of the generated estimated disease information based on the consistency evaluation result, allowing the user, who is a medical professional, to understand the accuracy of the information regarding the generated estimated disease information, thereby making it possible to provide the user with more accurate medical support information.

[0172] Furthermore, according to the medical care support system 1 of the present disclosure, in the step of presenting the estimated disease information, a process of presenting the estimated disease information including information on reliability to the user is performed. This allows the accuracy of the information on the generated estimated disease information to be grasped, and more accurate medical care support information can be provided to the user.

[0173] Furthermore, according to the medical support system 1 of the present disclosure, question information related to questions to be asked to the patient during medical treatment is generated based on the generated estimated disease information, and the generated question information is presented to the user, thereby enabling even medical professionals who are not specialized in medical treatment to make more accurate diagnoses.

[0174] Although several embodiments of the present disclosure have been described above, these embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and modifications are intended to be included in the scope of the inventions and their equivalents as defined in the claims, as well as in the scope and spirit of the inventions.

[0175] <Additional Notes> The matters described in the above embodiments will be supplemented below. (Appendix 1) A program for processing information about a patient who is a medical target, executed by a computer having a processor (29) and a storage unit (25), the program including: a step (S601) of receiving input of first patient condition information about the patient's condition, which is obtained based on information about the patient's chief complaint from the patient during medical treatment of the patient; a step (S631) of extracting a first tag group including at least one tag information about a case associated with the first patient condition information based on the received first patient condition information; and a step (S632) of receiving input of second patient condition information about the patient's condition, which is obtained based on information other than the chief complaint from the patient during medical treatment of the patient. 02), a step of extracting a second tag group including at least one tag information related to a case associated with the second patient condition information based on the received second patient condition information (S632), a step of evaluating the consistency between the tag information included in at least one of the extracted first tag group and the second tag group (S633), a step of generating inferred disease information related to a suspected disease of the patient based on the tag information related to the evaluation if the consistency is evaluated to be at least a predetermined level (S634), and a step of presenting the generated inferred disease information to a user who is a medical professional (S635).

[0176] (Appendix 2) A program described in Appendix 1, in which, in the step of evaluating consistency, if at least one of the first tag group and the second tag group contains a predetermined number or more of tag information that is consistent with each other, the consistency is evaluated to be at a predetermined level or above.

[0177] (Appendix 3) A program described in Appendix 1, in which, in the step of evaluating consistency, if the degree of association between tag information included in at least one of the first tag group and the second tag group is at or above a predetermined level, the consistency is evaluated to be at or above a predetermined level.

[0178] (Appendix 4) 3. The program according to claim 1, wherein the program executes a step (S732) of presenting information about the evaluation result to the user when the consistency is evaluated to be less than a predetermined level.

[0179] (Appendix 5) A program described in Appendix 4, in which, in the step of evaluating consistency, if tag information in at least one of the first tag group and the second tag group contains tag information that is incompatible with each other, the program evaluates that the consistency is not at a predetermined level or above.

[0180] (Appendix 6) A program described in Appendix 1 or 2, which executes a step (S831) of presenting tag information included in at least one of a first tag group and a second tag group to a user, and a step (S801) of accepting an operation from the user to modify the presented tag information, and in an evaluation step (S832), evaluates consistency based on the accepted modified tag information.

[0181] (Appendix 7) 3. The program according to claim 1, wherein the second patient condition information is at least one of information relating to the patient's speech, information relating to the patient's appearance, information relating to the patient's movements, and information relating to the patient's biological body.

[0182] (Appendix 8) A program described in Appendix 1 or 2, which executes a step of evaluating the reliability of the generated estimated disease information based on the consistency evaluation result.

[0183] (Appendix 9) 8. The program according to claim 7, wherein in the step of presenting the suspected disease information, the suspected disease information including information on reliability is presented to the user.

[0184] (Appendix 10) A program described in Appendix 1 or 2, which executes a step (S931) of generating question information regarding questions to be asked to the patient during medical treatment based on the generated estimated disease information, and a step (S932) of presenting the generated question information to the user.

[0185] (Appendix 11) A method executed by a computer including a processor (29) and a storage unit (25), the method for processing information about a patient who is a medical target, the method including the steps of: receiving (S601) input of first patient condition information about the patient's condition, which is obtained based on information about the patient's chief complaint from the patient during medical treatment of the patient; extracting (S631) a first tag group including at least one tag information about a case associated with the first patient condition information based on the received first patient condition information; and receiving (S632) input of second patient condition information about the patient's condition, which is obtained based on information other than the chief complaint from the patient during medical treatment of the patient. a step (S602) of extracting a second tag group including at least one tag information related to a case associated with the second patient condition information based on the received second patient condition information; a step (S632) of evaluating consistency between tag information included in at least one of the extracted first tag group and the second tag group; a step (S634) of generating inferred disease information related to a suspected disease of the patient based on the tag information related to the evaluation if the consistency is evaluated to be at least a predetermined level; and a step (S635) of presenting the generated inferred disease information to a user who is a medical professional.

[0186] (Appendix 12) The information processing device includes a control unit (29) and a storage unit (25), and the information processing device processes information about a patient who is a medical treatment target, and includes a step (S601) of accepting input of first patient condition information about the patient's condition, which is acquired based on information about the patient's chief complaint from the patient during medical treatment of the patient; a step (S631) of extracting a first tag group including at least one tag information about a case associated with the first patient condition information based on the accepted first patient condition information; and a step (S602) of accepting input of second patient condition information about the patient's condition, which is acquired based on information other than the chief complaint from the patient during medical treatment of the patient. ), based on the received second patient condition information, extracting a second tag group including at least one tag information related to a case associated with the second patient condition information (S632); evaluating the consistency between the tag information included in at least one of the extracted first tag group and the second tag group (S633); if the consistency is evaluated to be at least a predetermined level, generating inferred disease information related to a suspected disease of the patient based on the tag information related to the evaluation (S634); and presenting the generated inferred disease information to a user who is a medical professional (S635). [Explanation of symbols]

[0187] 1: medical care support system, 10: user-side terminal device, 12: communication IF, 13: input device, 14: output device, 17: memory, 18: storage unit, 19: processor, 20: server, 22: communication IF, 23: input / output IF, 25: memory, 26: storage, 29: processor, 30: external input device, 40: medical institution-side terminal device, 80: network, 111: antenna, 112: antenna, 121: first wireless communication unit, 122: second wireless communication unit, 130: operation reception unit, 131: touch-sensitive device, 132: display, 140: audio processing unit, 141: microphone, 142: speaker, 150: camera, 160: storage unit, 161: user information, 162: patient information, 163: patient condition information, 164: chief complaint information, 170: control unit, 171: input operation reception unit , 172: Transmitter / receiver unit, 173: Notification control unit, 174: Data processing unit, 201: Communication unit, 202: Memory unit, 203: Control unit, 2021: Reference tag information management database, 2022: Reference estimated disease information management database, 2023: Patient information management database, 2024: Patient condition information, 2025: Tag information, 2026: Estimated disease information, 2027: Reference question information management database, 2031: Reception control module, 2032: Transmission control module, 2033: Patient information acquisition module, 2034: Patient condition information acquisition module, 2035: Tag information extraction module, 2036: Consistency evaluation module, 2037: Tag information correction module, 2038: Estimated disease information generation module, 2039: Reliability evaluation module, 2040: Question information generation module

Claims

1. A program for processing information about a patient who is a medical treatment target, the program being executed by a computer having a processor and a storage unit, the program comprising: receiving input of first patient condition information regarding the condition of the patient, the first patient condition information being acquired based on information regarding a chief complaint from the patient during medical treatment of the patient; extracting a first tag group including at least one tag information item related to a case associated with the first patient condition information based on the received first patient condition information; receiving input of second patient condition information regarding the condition of the patient, the second patient condition information being acquired based on information other than the patient's chief complaint during medical treatment of the patient; extracting a second tag group including at least one tag information item related to a case associated with the second patient condition information based on the received second patient condition information; a step of evaluating consistency between tag information included in at least one of the extracted first tag group and the extracted second tag group; generating at least one piece of suspected disease information related to a suspected disease of the patient based on tag information related to the evaluation when the consistency is evaluated to be equal to or greater than a predetermined level; presenting the generated estimated disease information to a user who is a medical professional; A program that executes the following.

2. The program of claim 1, wherein in the step of evaluating the consistency, if at least one of the first tag group and the second tag group contains a predetermined number or more of tag information that is consistent with each other, the consistency is evaluated to be at a predetermined level or above.

3. The program according to claim 1, wherein in the step of evaluating the consistency, if the degree of association between tag information included in at least one of the first tag group and the second tag group is at or above a predetermined level, the consistency is evaluated to be at or above a predetermined level.

4. 3. The program according to claim 1, further comprising the step of: presenting information relating to the evaluation to the user when the consistency is evaluated to be less than a predetermined level.

5. The program of claim 4, wherein in the step of evaluating the consistency, if tag information in at least one of the first tag group and the second tag group contains tag information that is inappropriate for combination with each other, the consistency is evaluated to be below a predetermined level.

6. presenting tag information included in at least one of the first tag group and the second tag group to the user; receiving an operation from the user to modify the presented tag information; 3. The program according to claim 1, wherein in the evaluating step, the consistency is evaluated based on the received corrected tag information.

7. 3. The program according to claim 1, wherein the second patient condition information is at least one of information about the patient's speech, information about the patient's appearance, information about the patient's movements, and information about the patient's biological body.

8. The program according to claim 1 or 2, further comprising: a step of evaluating the reliability of the generated estimated disease information based on the evaluation result of the consistency.

9. The program according to claim 8 , wherein the step of presenting the suspected disease information includes presenting the suspected disease information to the user, the suspected disease information including information on the reliability.

10. generating question information regarding questions to be asked to the patient during medical treatment based on the generated suspected disease information; 3. The program according to claim 1, further comprising: a step of presenting the generated question information to the user.

11. 1. A computer-implemented method comprising a processor and a memory unit for processing information relating to a patient in a medical care setting, the method comprising: the processor: receiving input of first patient condition information regarding the condition of the patient, the first patient condition information being acquired based on information regarding a chief complaint from the patient during medical treatment of the patient; extracting a first tag group including at least one tag information item related to a case associated with the first patient condition information based on the received first patient condition information; receiving input of second patient condition information regarding the condition of the patient, the second patient condition information being acquired based on information other than the patient's chief complaint during medical treatment of the patient; extracting a second tag group including at least one tag information item related to a case associated with the second patient condition information based on the received second patient condition information; a step of evaluating consistency between tag information included in at least one of the extracted first tag group and the extracted second tag group; generating at least one piece of suspected disease information related to a suspected disease of the patient based on tag information related to the evaluation when the consistency is evaluated to be equal to or greater than a predetermined level; presenting the generated estimated disease information to a user who is a medical professional; How to perform.

12. An information processing device including a control unit and a storage unit, the information processing device for processing information relating to a patient who is a medical treatment target, the control unit: receiving input of first patient condition information regarding the condition of the patient, the first patient condition information being acquired based on information regarding a chief complaint from the patient during medical treatment of the patient; extracting a first tag group including at least one tag information item related to a case associated with the first patient condition information based on the received first patient condition information; receiving input of second patient condition information regarding the condition of the patient, the second patient condition information being acquired based on information other than the patient's chief complaint during medical treatment of the patient; extracting a second tag group including at least one tag information item related to a case associated with the second patient condition information based on the received second patient condition information; a step of evaluating consistency between tag information included in at least one of the extracted first tag group and the extracted second tag group; generating at least one piece of suspected disease information related to a suspected disease of the patient based on tag information related to the evaluation when the consistency is evaluated to be equal to or greater than a predetermined level; presenting the generated estimated disease information to a user who is a medical professional; An information processing device that executes the above.

Images