Information processing system, method for processing information, and program

Abstract

To provide a mechanism for providing a diagnosis based on a treatment guideline.SOLUTION: The information processing system has at least one processor. The at least one processor acquires information regarding at least one of the age and the disease state of a patient and proposes information for assisting diagnosis of a patient stipulated by a treatment guideline regarding a disease being treated.SELECTED DRAWING: Figure 8

Description

[Technical field]

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

[0002] Medical institutions that provide health insurance have begun prescribing application programs aimed at treating nicotine addiction and high blood pressure (hereinafter referred to as "therapeutic apps"). In addition, there are other therapeutic apps approved under the Pharmaceuticals and Medical Devices Act that aim to treat insomnia. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-149190 A Summary of the Invention [Problem to be solved by the invention]

[0004] For example, the 2019 Hypertension Treatment Guidelines set out diagnostic criteria for hypertension and blood pressure target values. It also indicates that blood pressure target values ​​should be changed depending on age and disease condition. However, hypertension treatment is not always performed by specialists. As a result, depending on the patient, it may be difficult to provide appropriate treatment goals according to the guidelines and the patient's condition. In addition, in clinical settings, a system that supports high-precision treatment within limited consultation time is required.

[0005] One aspect of the present disclosure provides a mechanism for providing medical care that complies with treatment guidelines. [Means for solving the problem]

[0006] As another aspect of the present disclosure, there is provided an information processing system having one or more processors that acquire information relating to at least one of a patient's age and pathological condition, and presents to medical personnel information to assist in the medical care of the patient as defined in treatment guidelines for the disease being treated.

[0007] As another aspect of the present disclosure, there is provided an information processing method in which a computer executes a process of acquiring information regarding at least one of a patient's age and pathological condition, and a process of presenting to a medical professional information that assists in the medical treatment of the patient as defined in a treatment guideline for the disease being treated.

[0008] As one form of the present disclosure, a program is provided to enable a computer to perform the following functions: acquiring information regarding at least one of a patient's age and pathological condition; and presenting to medical personnel information that assists in the medical treatment of the patient as defined in treatment guidelines for the disease being treated. Effect of the Invention

[0009] According to one aspect of the present disclosure, a mechanism for providing medical care in accordance with treatment guidelines can be provided. [Brief description of the drawings]

[0010] [Figure 1] FIG. 2 is a diagram illustrating an example of the configuration of an information processing system assumed in the first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a treatment application operation server. [Diagram 3] 11 is a diagram illustrating an example of authentication data and patient data stored in an auxiliary storage device of the medical application operation server. FIG. [Figure 4] FIG. 2 is a diagram illustrating an example of a hardware configuration of an information terminal. [Diagram 5] 13 is a process sequence illustrating an example of a process operation from prescribing a therapeutic application to registering patient data in a therapeutic application operation server. [Figure 6]13 is a diagram illustrating an example of a printed matter on which a prescription code is printed. FIG. [Figure 7] FIG. 13 is a diagram illustrating an example of an operation screen of a treatment application. [Figure 8] 4 is an example of a flowchart illustrating a display process executed in the first embodiment. [Figure 9] This is a chart explaining the blood pressure reduction targets set out in the 2019 Hypertension Treatment Guidelines. [Figure 10] 13 is a diagram illustrating an example of an initial screen displayed on a doctor's terminal prior to medical treatment of a patient receiving hypertension treatment. FIG. [Figure 11] FIG. 13 is a diagram illustrating an example of a display of an initial screen in which a blood pressure reduction target is changed from an initial value. [Figure 12] 13 is a diagram illustrating an example of a patient data viewing screen displayed on a doctor terminal. FIG. [Figure 13] This is a chart explaining the treatment goals set out in the 2019 Diabetes Care Guidelines. [Figure 14] This is a chart explaining the treatment goals for elderly people as set out in the 2019 Diabetes Care Guidelines. [Figure 15] 13 is a diagram illustrating an example of an initial screen displayed on a doctor's terminal prior to medical treatment of a patient receiving diabetes treatment. FIG. [Figure 16] 13 is a diagram illustrating an example of an initial screen displayed on a doctor's terminal prior to medical treatment of an elderly patient receiving diabetes treatment. FIG. [Figure 17] 4 is an example of a flowchart illustrating a display process executed in the first embodiment. [Figure 18] This is a diagram explaining the drug therapy plan prescribed in the minimum essentials for the treatment of adult bronchial asthma. [Figure 19] FIG. 13 is a diagram illustrating an example of an initial screen display assuming an untreated patient. [Figure 20] FIG. 13 is a diagram illustrating an example of an initial screen display assuming a patient under treatment. [Figure 21] FIG. 13 is a diagram showing an example of a display of a treatment method screen presenting treatment methods according to treatment steps. [Figure 22]This is a chart explaining the severity assessment classification stipulated in the 2018 Evidence-Based CKD Treatment Guidelines. [Figure 23] FIG. 13 is a diagram illustrating an example of an initial screen display assuming a patient with chronic kidney disease. [Figure 24] FIG. 13 is a diagram showing an example of a display of a treatment method screen presenting treatment methods for chronic kidney disease according to treatment stages. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. <Embodiment 1> In this embodiment, an application for assisting in the treatment of hypertension will be described as an example of a treatment application prescribed by a doctor.

[0012] <System configuration> FIG. 1 is a diagram illustrating an example of the configuration of an information processing system 1 assumed in the first embodiment. The information processing system 1 shown in Figure 1 is composed of a therapeutic application operation server 10, a doctor terminal 20 operated by a doctor who prescribes the therapeutic application, a patient terminal 30 operated by a patient receiving treatment for hypertension, and a network N connecting these terminals. It is also assumed that, to the extent permitted, the doctor terminal 20 will be operated by nurses, pharmacists, public health nurses, nutritionists, hospital staff, and other medical personnel.

[0013] The therapeutic application operation server 10 in this embodiment is a server that realizes distribution of the therapeutic application, authentication of the patient, storage of the patient data input through the therapeutic application, provision of the patient data to the medical institution (specifically, the doctor terminal 20), etc. However, the distribution of the therapeutic application may be performed by an entity different from the entity that operates the therapeutic application operation server 10.

[0014] As mentioned above, therapeutic apps are apps that have been approved under the Pharmaceuticals and Medical Devices Act, and patients who use therapeutic apps can receive insured medical treatment from a doctor during the insured medical treatment period. By using this treatment app, the patient can store blood pressure values ​​measured between the time of the next consultation with the doctor and other patient data in the treatment app operation server 10. Meanwhile, the doctor can use the patient data stored through the treatment app between the previous consultation and the current consultation to understand the patient's physical condition and decide on a treatment plan. The treatment app in this embodiment is an example of an app. In addition, insured medical treatment includes not only face-to-face medical treatment but also online medical treatment.

[0015] In this embodiment, the insured medical treatment period is set to six months. However, six months is just an example, and it may be nine months or twelve months. It may also be set in days, such as 60 days or 180 days, or it may be set in weeks, such as 8 weeks or 24 weeks. Needless to say, these values ​​are just examples. In this embodiment, the patient is permitted to use the treatment app only during the period of medical treatment covered by insurance, that is, the patient is allowed to input and record blood pressure values ​​and the like through the treatment app.

[0016] The starting date of the insured medical treatment period may be determined based on the consultation date when the treatment app was prescribed, or based on the date when the treatment app was installed on the patient terminal 30, or based on the date when use of the treatment app began, or based on the month when the treatment app was prescribed (hereinafter referred to as the "consultation month"). When the month of the medical examination is used as the starting month, the month following the month of the medical examination is considered to be month 1. This is because if the month of the medical examination is used as the 1st month, the insured medical treatment period for patients who receive medical treatment at the end of the month will be shortened by approximately one month.

[0017] Patient data includes patient attributes (gender, date of birth, height, weight), blood pressure, activity records, mood records, physical condition records, medical examination history, treatment app operation history, biological characteristics, psychological characteristics, social characteristics, habits, goal achievement status, etc. However, patient data does not need to be all of this information and may be only a part of it. The blood pressure values ​​are, for example, systolic blood pressure (i.e., the highest blood pressure value) and diastolic blood pressure (i.e., the lowest blood pressure value). The activity record is, for example, a usage history of a medical application, a medication record, a food record, a smoking record, a drinking record, and an exercise record. The activity record is an example of information about an activity.

[0018] The record of taking medicine is, for example, the type and number of medicines taken, and the time when the medicine was taken. The record of taking medicine is an example of information related to taking medicine. The food record is, for example, the contents of the food eaten and the amount of salt ingested. The food record is an example of information related to food. The smoking record is, for example, whether or not a person smoked, the date and time of smoking, and the number of cigarettes smoked. The smoking record is an example of information related to smoking. The drinking record is, for example, the date and time of drinking, the amount of alcohol consumed, and the type of alcohol. The drinking record is an example of information related to drinking.

[0019] The exercise record includes, for example, records related to sports, as well as records of daily activities such as walking, shopping, cleaning, etc. The exercise record is an example of information related to exercise. The mood record is, for example, a subjective mood. The mood record is an example of information related to mood. The record of physical condition is, for example, a subjective physical condition or symptoms. The record of physical condition is an example of information related to physical condition. The medical examination history is, for example, the treatment start date, the examination date, the details of the treatment, and advice. The medical examination history is an example of information related to medical examinations.

[0020] The operation history of the treatment application is, for example, a history of operations related to the start-up operation, the input operation of blood pressure values, and the input operation of reviewing the treatment application. Biological characteristics include, for example, the presence or absence of other diseases, the presence or absence of injuries undergoing treatment, the presence or absence of knee or foot pain, the presence or absence of experience of treatment for hypertension, the number of years since hypertension was diagnosed, the strength of seasonings used in home cooking, and the amount of food eaten. Psychological characteristics include, for example, expectations regarding app treatment, willingness to acquire knowledge about hypertension treatment, whether reducing salt intake is difficult or whether one cannot change one's sense of taste, and psychological resistance to leaving food on one's plate.

[0021] Social characteristics include, for example, wake-up time, bedtime, type of work (e.g., shift work, day shift, night shift), days of the week worked, start time of work, time home from work, regular days off, and whether or not there is heating in the changing room. Habits include, for example, exercise habits, the habit of weighing oneself, the habit of checking calorie counts on food labels, the habit of choosing low-fat foods, the habit of not consuming caffeine after 4 p.m., the habit of eating and drinking after 10 p.m., the habit of skipping breakfast, the habit of snacking, the habit of taking a bath one hour before going to bed, the habit of stretching or massaging before going to bed, and the habit of sleeping six hours or more. The goal achievement status is, for example, the relationship between the patient's status and the goal set for each patient by a doctor or the like. The above-mentioned information can be classified into subjective information and objective information.

[0022] Although only one therapeutic application operation server 10 is illustrated in FIG. 1, a plurality of therapeutic application operation servers 10 may exist on the network N. Furthermore, the services provided by one therapeutic application operation server 10 may be realized by the cooperative operation of a plurality of servers.

[0023] The doctor terminal 20 refers to a terminal operated by a doctor in an insurance medical institution, etc. A plurality of doctor terminals 20 are depicted in FIG. The patient terminal 30 refers to a terminal operated by a patient who is examined or treated for hypertension. A plurality of patient terminals 30 are illustrated in FIG.

[0024] For example, a desktop computer, a notebook computer, a tablet computer, or a smartphone is used as the doctor terminal 20 and the patient terminal 30. However, wearable computers such as smart glasses and a headset may also be used as the doctor terminal 20 and the patient terminal 30. The doctor terminal 20 and the patient terminal 30 are examples of information terminals connected to the network N.

[0025] The network N is, for example, a LAN (Local area network), the Internet, or a mobile communication system (4G, 5G). FIG. 1 illustrates an example in which the therapeutic application operation server 10, the doctor terminal 20, and the patient terminal 30 are connected to one network N, but they may be connected via a plurality of networks N that are connected to each other.

[0026] <Server hardware configuration> FIG. 2 is a diagram illustrating an example of a hardware configuration of the medical application operation server 10. As shown in FIG. 2 includes a processor 11, a ROM (=Read Only Memory) 12 in which a BIOS (=Basic Input Output System) and the like are stored, a RAM (=Random Access Memory) 13 used as a work area for the processor 11, an auxiliary storage device 14, and a communication interface 15. Each device is connected via a bus and other signal lines 16.

[0027] The processor 11 is a device that realizes various functions through the execution of programs. The processor 11, the ROM 12, and the RAM 13 function as a computer. The auxiliary storage device 14 is configured by, for example, a hard disk device or a semiconductor storage device. In addition to the therapeutic app, the auxiliary storage device 14 stores data related to authentication of patients to whom the therapeutic app is prescribed and patient data registered through the therapeutic app.

[0028] In this embodiment, the treatment application and the OS (=Operating System) are collectively referred to as a program. The communication interface 15 is an interface for communicating with other servers and terminals via the network N. The communication interface 15 supports Ethernet (registered trademark), Wi-Fi (registered trademark), mobile communication systems, and other communication standards.

[0029] <Data managed by the server> 3 is a diagram for explaining an example of the authentication data 141 and the patient data 142 stored in the auxiliary storage device 14 (see FIG. 2) of the medical application operation server 10. In the case of FIG. 3, only the information of "Tokyo Taro" is illustrated, but data of other patients is also recorded. The authentication data 141 shown in FIG. 3 includes, for example, a medical record number, a user ID, a patient name, a prescription date / examination date, a medical institution ID, a doctor ID, a prescription code, an insured medical treatment period (last month) of the medical treatment application, and a prescription code usage start date.

[0030] The medical record number is a number for identifying a patient who has been prescribed a medical treatment application, and is notified from the doctor's terminal 20 (see FIG. 1) of the health insurance medical institution. The user ID is an ID used for managing the medical application operation server 10 and is used for authenticating the patient. The patient name is recorded when the patient name is notified by the health insurance medical institution. In the case of Figure 3, the patient name is "Tokyo Taro."

[0031] The prescription date / examination date is the date on which the patient was examined at the health insurance medical institution. In this embodiment, the examination date on which the treatment app was prescribed is called the "prescription date" and is distinguished from other examination dates. In the case of FIG. 3, the prescription date is July 31, 2023, and the second examination date is August 29, 2023.

[0032] The medical institution ID is an ID that identifies the health insurance medical institution that prescribed the therapeutic app. The doctor ID is an ID for identifying the doctor who prescribed the treatment app. A prescription code is a code that is notified to a patient to activate a treatment app. A prescription code is generated for each prescription. A deadline for starting use of the app (hereinafter referred to as the "start-use deadline") is set for the prescription code, and a prescription code that has passed the start-use deadline is invalidated. The start-use deadline for a prescription code is, for example, three days after the prescription date.

[0033] The insured medical treatment period (last month) of the treatment app is information that gives the longest period during which the treatment app can be used. In the present embodiment, the insured medical treatment period is managed on a monthly basis. Therefore, the last month of the insured medical treatment period is recorded. In the case of FIG. 3, it is January 2024. The insured medical treatment period is recorded when the treatment app is activated. The prescription code usage start date indicates the date until which the prescription code is valid.

[0034] The patient data 142 shown in Fig. 3 is composed of, for example, a chart number, a user ID, a patient name, an input date and time, and a blood pressure value. As mentioned above, the patient data 142 also records information other than the blood pressure value, but this is omitted in Fig. 3 due to space limitations. The medical record number and user ID here are used to link with the authentication data 141. The patient data 142 is also an example of data used by a doctor or the like for medical treatment (hereinafter referred to as "medical treatment data"). The input date and time is the date and time when the patient inputs the blood pressure value, etc., into the activated treatment application.

[0035] In the case of Figure 3, the top of the input date and time is recorded as 6:35 on August 1, 2023, the day after the prescription date. In the case of Figure 3, the systolic blood pressure value of "145" and the diastolic blood pressure value of "97" are recorded for the same day and time. In addition, the patient data 142 shown in FIG. 3 also records input values ​​on the evening of August 1, 2023 and input values ​​on the following morning.

[0036] <Hardware configuration of information terminal> 4 is a diagram illustrating an example of a hardware configuration of an information terminal. The hardware configuration shown in FIG. Therefore, in the following, the doctor terminal 20 will be described as a representative example of an information terminal. 4 includes a processor 21, a ROM 22 storing a BIOS and the like, a RAM 23 used as a work area for the processor 21, an auxiliary storage device 24, a communication interface 25, a display 26, and an input reception device 27. Each device is connected via a bus or other signal lines 28. The patient terminal 30 is also provided with a camera.

[0037] The communication interface 25 is an interface for communicating with other servers or terminals or with peripheral devices through the network N. The communication interface 25 supports Ethernet (registered trademark), Wi-Fi (registered trademark), Bluetooth (registered trademark), USB (=Universal Serial Bus), mobile communication systems, and other communication standards.

[0038] The display 26 is, for example, a liquid crystal display or an organic EL (Electro Luminescence) display. The input reception device 27 is, for example, a mouse or a keyboard. In addition, when the doctor terminal 20 is a notebook computer, a tablet computer, or a smartphone, a capacitive touch sensor having transparency that does not interfere with the visibility of the image displayed on the display 26 is used as the input reception device 27. A device that combines this type of touch sensor with a display is called a touch panel.

[0039] <Processing operations during the insured medical treatment period of the treatment app> Here, a series of processing operations that begins with the prescription of a treatment application will be described. 5 is a process sequence illustrating an example of a process operation from prescription of a therapeutic application to registration of patient data in the therapeutic application operation server 10. Note that the symbol S in the figure represents a step, and the symbol t represents time. The processing sequence shown in FIG. 5 consists of three stages.

[0040] The first stage is processing operations S101 to S105 (t11 to t14) related to notification of a prescription code of a medical treatment application. The second stage is processing operations S111 to S124 (t21 to t28) related to installing the therapeutic application in the patient terminal 30 and linking the therapeutic application with information identifying the patient. The third stage is processing operations S131 to S137 (t31 to t35) related to the registration of patient data in the medical application operation server 10 via the medical application.

[0041] <First stage> First, a doctor operates doctor terminal 20 to input details of a medical examination of a patient with hypertension (S101). The details of the examination are registered in the management system of the health insurance medical institution to which the doctor belongs. In this embodiment, the doctor determines that a therapeutic application needs to be prescribed for the patient. In this case, the doctor accesses a website for medical institutions published by the therapeutic application operation server 10 and requests a prescription code (S102). Incidentally, a doctor ID and a login password, for example, are used to log in to the website. At this time, the patient identification information (for example, the patient's name, date of birth, etc.) may be attached, or the medical record number used in the hospital system may be attached.

[0042] The medical application operation server 10 that has received the prescription code requests issues the prescription code (S103). In the present embodiment, a prescription code is issued for each request. The issued prescription code is associated with information (e.g., a medical record number, a user ID) that identifies the patient to whom the prescription code is to be issued, and is registered in the authentication data 141 (see FIG. 3). Thereafter, the medical application operation server 10 transmits the issued prescription code to the doctor terminal 20 which is the request source (S104). The notified prescription code is printed on a sheet of paper and handed to the patient (S105). The doctor terminal 20 may notify the patient terminal 30 by email.

[0043] Fig. 6 is a diagram illustrating an example of a printed matter 40 on which a prescription code is printed. On the printed matter 40 shown in Fig. 6, a title 41, a medical record number 42, an issue date 43, a patient's name 44, a patient's gender 45, information on the health insurance medical institution 46, a prescription code 47, a QR code (registered trademark) 48, and a note 49 are printed. The expiration date (i.e., the date by which the prescription can be used) is also printed on the prescription code 47. In the case of FIG. 6, the expiration date is 10:31 on August 3, 2023, three days after the date of issue. The QR code 48 has prescription code information embedded therein.

[0044] <Second stage> For example, the patient accesses a website provided by a doctor and requests a therapeutic application (S111 in FIG. 5). In the present embodiment, the therapeutic application is distributed by the therapeutic application operation server 10. Therefore, in S111, the therapeutic application is requested from the therapeutic application operation server 10. The therapeutic application operation server 10 that has received the request for the therapeutic application transmits the requested therapeutic application to the patient terminal 30 (S112). If the therapeutic application has already been downloaded to the patient terminal 30, the processing operations of S111 and S112 are omitted.

[0045] The patient terminal 30 that has received the therapeutic app installs the therapeutic app, starts the installed prescription app, and receives the prescription code in that order in response to the patient's operation (S113). The therapeutic app cannot be used simply by being installed, and activation by inputting the prescription code is required. The patient terminal 30 transmits the input prescription code to the medical application operation server 10 (S114). The medical application operation server 10 authenticates the patient by comparing the prescription code received from the patient terminal 30 with the prescription code in the authentication data 141 (see FIG. 3) (S115).

[0046] If these two prescription codes match, the therapeutic application operation server 10 determines that the authentication is successful. On the other hand, if these two prescription codes do not match, the therapeutic application operation server 10 determines that the authentication is unsuccessful. Even if the two prescription codes match, if the prescription code usage period (i.e., usage start period) has expired, the therapeutic application operation server 10 regards the authentication as a failure. As described above, in this embodiment, the usage period is three days after the prescription date. In either case, the therapeutic application operation server 10 transmits the result of the authentication to the patient terminal 30 (S116).

[0047] If the authentication is successful, the authentication result includes a code that allows activation of the therapeutic app. In this case, activation of the therapeutic app is executed in the patient terminal 30 (S117). As a result, the therapeutic app becomes available in the patient terminal 30. When the therapeutic app is in an activated state, the prescription code entered in S113 is recorded in association with the therapeutic app. On the other hand, if the authentication fails, the authentication result does not include a code that allows activation of the therapeutic application. In this case, an error screen is displayed on the display 36 of the patient terminal 30 (see FIG. 4).

[0048] When the therapeutic application is activated, registration of patient information in the therapeutic application operation server 10 becomes possible. Specifically, the patient terminal 30 transmits an account ID and a password used for logging in to the therapeutic application operation server 10 (S118), and the account ID and the password are registered in association with the prescription code, etc. (S119). For example, the account ID and the password are added to the authentication data 141 (see FIG. 3). When the registration of the account ID and password used for logging in is completed, the therapeutic application operation server 10 notifies the patient terminal 30 of the completion of the registration (S120).

[0049] After completing the registration of the account ID and password used for logging in, the patient inputs the patient name and other patient information into the patient terminal 30 (S121). When the input is confirmed, the input patient information is transmitted from the patient terminal 30 to the therapeutic application operation server 10 (S122). The therapeutic application operation server 10 registers the received patient information in association with the prescription code and the like (S123), and notifies the patient terminal 30 of the completion of the registration (S124). The completion of the registration is displayed on the display 36 of the patient terminal 30 (see FIG. 4).

[0050] <Third stage> Here, the process of inputting patient data using the treatment app after activation will be described. First, the patient operates the patient terminal 30 to start the therapeutic application (S131). When the therapeutic application is started, the patient terminal 30 transmits an account ID and a password used for logging in to the therapeutic application operation server 10 (S132). The therapeutic application operation server 10 executes an authentication process using the received account ID and password (S133). If the received account ID and password exist in the authentication data 141 (see FIG. 3), the therapeutic application operation server 10 determines that the authentication is successful. On the other hand, if the received account ID and password do not exist in the authentication data 141, the therapeutic application operation server 10 determines that the authentication is unsuccessful.

[0051] The result of the authentication is transmitted from the therapeutic application operation server 10 to the patient terminal 30 (S134). If the authentication is successful, it becomes possible to input data such as blood pressure values ​​into the patient terminal 30. If the authentication is unsuccessful, the patient terminal 30 displays an error on the display .

[0052] Fig. 7 is a diagram for explaining an example of an operation screen of a treatment application. In the case of Fig. 7, the patient terminal 30 is a smartphone. Moreover, the operation screen displayed on the display 36 is a screen for manual input. In the case of FIG. 7, the measurement date is August 1, 2023 (Tuesday), and the blood pressure was entered at 8 p.m. The systolic blood pressure is 135mmHg, the diastolic blood pressure is 85mmHg, and the pulse rate is 70bpm.

[0053] Returning to the explanation of Figure 5. When the patient inputs data such as blood pressure values ​​(S135), the patient terminal 30 transmits the input patient data to the medical application operation server 10 (S136). The medical application operation server 10 registers the received data as the patient data 142 (see FIG. 3) (S137). The input of data such as blood pressure values ​​may be done manually by the patient, or may be done automatically by inputting blood pressure values ​​measured by a peripheral device connected via Bluetooth, etc. The peripheral device here is a blood pressure monitor.

[0054] The patient data 142 registered in the therapeutic application operation server 10 can be downloaded and viewed from a doctor terminal 20 (see FIG. 1) operated by the doctor who prescribed the therapeutic application. For example, patient data that matches the chart number and other information entered by the doctor is sent to the doctor terminal 20. As a result, the doctor can use information such as blood pressure values ​​at home for examinations.

[0055] <Display processing of information to assist doctors in their medical treatment> FIG. 8 is an example of a flowchart illustrating the display process executed in the first embodiment. The processing operation shown in FIG. 8 is executed by the processor 11 (see FIG. 2) of the medical application operation server 10 (see FIG. 1).

[0056] In this embodiment, the processing operation shown in Fig. 8 is started when a doctor or the like requests to view patient data through the operation of the doctor terminal 20 (see Fig. 1). However, a request by a doctor or the like to view an electronic medical record may be used as a trigger for the processing operation shown in Fig. 8. In the present embodiment, a request for viewing is made to the medical application operation server 10, for example, at the time of a medical interview or before or after the medical interview. When requesting viewing, for example, a medical record number, a user ID, a prescription code, etc. are transmitted from the doctor terminal 20 to the medical application operation server 10. This information is read from, for example, an electronic medical record, etc. However, this information may also be input by a doctor, etc.

[0057] The processor 11, which has received a request to view patient data, acquires the patient data of the target patient (S201). Incidentally, the disease information of the patient is specified, for example, through information that specifies the prescribed therapeutic application. Note that the therapeutic application operation server 10 may read the disease information from the electronic medical record, or a doctor or the like may input the disease information. Figure 9 is a chart explaining the blood pressure control targets stipulated in the Hypertension Treatment Guidelines 2019. In the chart shown in Figure 9, blood pressure control targets are stipulated in two categories.

[0058] The blood pressure reduction targets in one category are systolic / diastolic blood pressure of 130 / 80 in the doctor's office and systolic / diastolic blood pressure of 125 / 75 at home. This blood pressure reduction target applies to patients who fall into any of the following categories: (1) adults under 75 years of age, (2) cerebrovascular disease patients without bilateral carotid artery stenosis or major cerebral artery occlusion, (3) coronary artery disease patients, (4) CKD patients (with positive proteinuria), (5) diabetic patients, and (6) patients taking antithrombotic drugs.

[0059] The blood pressure reduction targets in the other category are systolic / diastolic blood pressure of 140 / 90 in the doctor's office and systolic / diastolic blood pressure of 135 / 85 at home. This blood pressure target applies to patients who fall into any of the following categories: (1) elderly patients aged 75 years or older, (2) patients with cerebrovascular disease who have bilateral carotid artery stenosis or major cerebral artery occlusion or who have not yet been evaluated, and (3) patients with CKD (negative proteinuria).

[0060] Returning to the explanation of Figure 8. Next, the processor 11 displays, on the doctor terminal 20, an initial screen including the initial value of the target value and confirmation items of the patient's age and pathological condition accompanied by a change in the category of the target value based on the treatment guideline (S202). The initial value here is, for example, the lower of the two divisions. FIG. 10 is a diagram for explaining an example of an initial screen 260 displayed on the doctor terminal 20 (see FIG. 1) prior to the examination of a patient undergoing hypertension treatment.

[0061] 10, the initial screen 260 is displayed in front of a viewing screen 270 for the patient data that the doctor has requested to view. Therefore, the doctor or the like is required to confirm the blood pressure reduction target based on the treatment guidelines before starting medical treatment based on the patient data. 10, the viewing screen 270 is displayed in a grayed-out state in order to improve the visibility of the initial screen 260. However, the display 26 may be designed to display only the initial screen 260.

[0062] An initial screen 260 shown in FIG. 10 is composed of an initial value 261 of the target value, an explanation 262 regarding the display contents, a selection field 263 listing factors for changing the target value, and a button 264 for starting examination. The initial target value 261 displays "125 / 75 mmHg", which is the lower home blood pressure target specified in the hypertension treatment guidelines. The blood pressure value shown in the initial value 261 is an example of an observation target according to a treatment goal (ie, a blood pressure reduction goal).

[0063] The explanation 262 displays that the target value is the recommended value in the hypertension treatment guidelines, that the target value may be changed depending on the patient's age and pathology, etc. In the case of FIG. 10, the first line displays "This is the blood pressure reduction target recommended in the hypertension treatment guidelines," and the second line displays "Checking the following item will change the target value to 135 / 85 mmHg."

[0064] In the case of Figure 10, three check boxes are displayed corresponding to the three factors that correspond to the higher of the two categories stipulated in the hypertension treatment guidelines. These check boxes are examples of options. The first factor is "age." In Figure 10, this is "75 years old or older." The second factor is the patient's condition. In Figure 10, this is "chronic kidney disease (negative for proteinuria)." The third factor is also the pathology of the patient. In Figure 10, it is "cerebrovascular disorder (bilateral carotid artery stenosis, occlusion of major cerebral arteries, or not evaluated)." These factors are examples of information that are defined as diagnostic criteria for the target value. These factors also correspond to the check items in S202.

[0065] Returning to the explanation of Figure 8. Next, processor 11 determines whether or not a confirmation item has been selected (S203). If a confirmation item is selected, a positive result is obtained in S203. In this case, the processor 11 changes the display of the target value (S204). 11 is a diagram for explaining a display example of an initial screen 260 in which the blood pressure reduction target has been changed from the initial value. In FIG 11, parts corresponding to those in FIG 10 are denoted by the same reference numerals. In Figure 11, the check box corresponding to "75 years or older" is selected, and as a result, the displayed blood pressure target is changed to "135 / 85 mmHg."

[0066] In this embodiment, the blood pressure target display is changed to "135 / 85 mmHg" whether any one of the other two check boxes is selected, or whether two or all three of the three check boxes are selected. The display of the blood pressure reduction target here is an example of information that assists in the medical treatment of the patient. In the hypertension treatment guidelines assumed in this embodiment, the target values ​​are classified into two categories, but if they are classified into three or more categories, the display content is changed to the target value of the category corresponding to the selected check box. Also, if the category is specified according to a combination of multiple factors, the display content of the target value is changed according to the combination of factors corresponding to the selected check box.

[0067] Returning to the explanation of Figure 8. After execution of S204, or if a negative result is obtained in S203 (no confirmation item is selected), the processor 11 determines whether or not a confirmation operation has been accepted (S205). The confirmation operation here is the operation of the Start Examination button 264 (see Figs. 10 and 11). The Start Examination button 264 is labeled "Start Examination." If no operation of the examination start button 264 is detected, a negative result is obtained in S205. In this case, the processor 11 returns to the determination process of S203.

[0068] On the other hand, if an operation of the examination start button 264 is detected, a positive result is obtained in S205. In this case, the processor 11 displays the screen of the medical care data (S206). This ends the processing up to the display of the screen of the medical care data. In this embodiment, the medical data is patient data input by the patient through a treatment application in the patient terminal 30 (see FIG. 1). As described above, the medical data may include the patient's electronic medical record.

[0069] FIG. 12 is a diagram for explaining an example of a patient data viewing screen 270 displayed on the doctor terminal 20 (see FIG. 1). The viewing screen 270 shown in FIG. 12 is displayed based on the patient data 142 of “Tokyo Taro” read out from the medical application operation server 10 (see FIG. 3). The patient data column on the viewing screen 270 shown in FIG. 12 is composed of a display column 271 for the average blood pressure values ​​measured at home over the past few weeks, a display column 272 for the change in the average blood pressure value over the same period, a display column 273 for the blood pressure reduction target, a display column 274 for notes, a display column 275 for review information, a display column 276 for activity records, a column 277 for appointments with the patient, and a button 278 for moving to other screens.

[0070] In the case of Fig. 12, two broken lines corresponding to the two target values ​​of the diastolic blood pressure and the systolic blood pressure are displayed as indicators in the display field 272. The target values ​​here are linked to the blood pressure reduction target of the patient displayed on the initial screen 260 (see Figs. 10 and 11). The initial values ​​displayed on the initial screen 260 (see Fig. 10) are displayed in the display field 272 shown in Fig. 12.

[0071] Of course, if any of the check boxes in the selection fields 263 (see FIG. 10) are checked, the heights of the two target values ​​will change to 135 / 85 mmHg. The target value presented based on the hypertension treatment guidelines is also displayed in a display field 273 . This allows doctors and other medical professionals to check the relationship between changes in blood pressure values ​​measured at home and the correct target values ​​on the same screen.

[0072] A record of mood and physical condition is displayed in a display field 275 shown in Fig. 12. A record of mood and physical condition is also called a diary. 12, the number of days the treatment app was used, the number of days a salt reduction in meals was recorded, the number of days a weight loss was recorded, etc. are displayed as activity records. Of course, these are just examples. The patient promise column 277 displays the promises made by the doctor etc. with the patient and the degree of fulfillment of the promises. In the case of this embodiment, when the other screen move button 278 labeled "To examination date registration screen" is operated, the patient data viewing screen is switched to an electronic medical record or the like.

[0073] <Summary> According to the information processing system 1 (see FIG. 1) of this embodiment, medical personnel can check not only the initial value of the blood pressure reduction target but also the patient's age and pathological condition, which are factors that may change the initial value, on the initial screen 260 (see FIG. 10). Furthermore, by checking the patient's age and pathological condition on the initial screen 260, medical personnel can check the blood pressure reduction target appropriate for the patient based on the hypertension treatment guidelines before the patient data viewing screen 270 (see FIG. 12) is displayed or before medical treatment.

[0074] Furthermore, the blood pressure reduction target suitable for the patient is also displayed as a numerical value or index on the viewing screen 270, making it possible to view medical data such as patient data while checking the blood pressure reduction target suitable for the patient. As a result, medical procedures such as diagnosis based on hypertension treatment guidelines can be provided within a short consultation time not only by specialists but also by non-specialists.

[0075] <Embodiment 2> This embodiment is also premised on the system configuration and processing operations of the information processing system 1 (see FIG. 1) described in the first embodiment. In this embodiment, however, it is assumed that the patient has diabetes as the disease. Therefore, a treatment app for diabetes is prescribed to the patient. For this reason, blood glucose levels and the like measured at home are recorded as patient data. The patient data input through the treatment app is transmitted from the patient terminal 30 to the treatment app operation server 10 (see FIG. 1) and made available for viewing by doctors and the like.

[0076] <Diabetes Treatment Guidelines> Figure 13 is a chart explaining the treatment goals set out in the 2019 Diabetes Care Guidelines. In the case of Figure 13, the treatment goals are divided into three categories: "goals for aiming at blood glucose normalization," "goals for preventing complications," and "goals when intensifying treatment is difficult." It is also stipulated that treatment goals should be set individually, taking into account the patient's age, duration of illness, organ damage, risk of hypoglycemia, and support system. The duration of the disease, organ damage, and risk of hypoglycemia are examples of information regarding the pathological condition of a patient.

[0077] By the way, the 2019 Diabetes Treatment Guidelines stipulate additional treatment goals for elderly people. Figure 14 is a chart explaining the treatment goals for elderly people as stipulated in the 2019 Diabetes Care Guidelines. Regarding treatment goals for the elderly, it is stipulated that "in addition to age, duration of illness, risk of hypoglycemia, and support system, for the elderly, cognitive function, basic ADLs, instrumental ADLs, and comorbid diseases are taken into consideration and set individually. However, it is important to be aware that the risk of severe hypoglycemia increases with age." In addition, the 2019 Diabetes Care Guidelines classify elderly people into three categories based on their characteristics and health condition, and set more specific target values ​​for each category.

[0078] <Initial screen for target values> FIG. 15 is a diagram for explaining an example of an initial screen 280 displayed on the doctor terminal 20 (see FIG. 1) prior to medical examination of a patient undergoing diabetes treatment. In the case of Fig. 15 as well, the initial screen 280 is displayed in front of the viewing screen for the patient data that the doctor has requested to view. Note that in Fig. 15, the viewing screen is represented by shading. By displaying the initial screen 280 on the front side of the viewing screen, the doctor or the like can confirm the control target suitable for the patient based on the treatment guidelines before viewing the patient data.

[0079] In the case of Fig. 15, the initial screen 280 is displayed near the center of the display 26 of the doctor terminal 20 (see Fig. 1). As in the case of Fig. 10, a patient data viewing screen or the like may be displayed in a grayed-out state behind the initial screen 280. An initial screen 280 shown in FIG. 15 is composed of an initial value 281 of the target value, an explanation 282 regarding the display contents, a selection field 283 listing factors for changing the target value, and a button 284 for starting examination.

[0080] The initial target value 281 displays "HbA1c less than 6.0 (%)," which is the minimum blood glucose control target specified in the Diabetes Care Guidelines 2019. The HbA1c shown in the initial value 281 is an example of an observation target according to a treatment target (ie, a control target).

[0081] Explanation 282 displays that the target value is the recommended value in the Diabetes Care Guidelines 2019, and that the target value may change depending on the patient's age and condition. In the case of Figure 15, the first and second lines display "These are the target values ​​recommended in the Diabetes Care Guidelines 2019 for 'aiming to normalize blood glucose levels.'" and the third line displays "Checking the following items will change the target value." In the case of Figure 15, three check boxes are displayed corresponding to the three factors stipulated in the Diabetes Care Guidelines 2019. These check boxes are examples of options.

[0082] The first factor is "prevention of complications." If this factor applies, the target value will be changed to "less than 7.0 (%)." The second factor is "when it is difficult to intensify treatment." If this factor applies, the target value will be changed to "less than 8.0 (%)." The third factor is also the age category of the patient. In Figure 15, it is displayed as "elderly." For elderly people, it is required to set a target value according to the condition of the patient, so in the example of Figure 15, "Next question" is displayed as the process to be taken when the checkbox is checked.

[0083] Fig. 16 is a diagram for explaining an example of an initial screen 290 displayed on the doctor terminal 20 (see Fig. 1) prior to the examination of an elderly patient undergoing diabetes treatment. In Fig. 16, the parts corresponding to those in Fig. 15 are denoted by the same reference numerals. The initial screen 290 shown in FIG. 16 is composed of an initial target value 291, a selection field 292 for patients "not using medications (insulin preparations, SU agents, glinides, etc.) that are at risk of causing severe hypoglycemia," a selection field 293 for patients "using medications (insulin preparations, SU agents, glinides, etc.) that are at risk of causing severe hypoglycemia," and a start examination button 284. The initial screen 290 may include display fields for the definitions of categories I, II, and III, and buttons for calling up each definition.

[0084] In addition, when an elderly patient is selected, the initial target value 291 is changed to "HbA1c less than 7.0 (%)," which is the minimum blood glucose control target specified in the Diabetes Care Guidelines 2019. However, since the target values ​​differ depending on the pathological condition of the elderly patient, the initial screen 290 further displays a number of check boxes for the two categories.

[0085] For example, in the case of selection field 292, the target values ​​for categories I and II are "HbA1c less than 7.0(%)", while the target value for category III is "HbA1c less than 8.0(%)". In addition, in the case of selection field 293, two target values ​​for category I are displayed by age. One is "HbA1c less than 7.5(%)" for those aged 65 to 75 years old, and the other is "HbA1c less than 8.0(%)" for those aged 75 years old or older. The factors displayed on the initial screen 280 (see FIG. 15) and the initial screen 290 (see FIG. 16) are also an example of information that defines the diagnostic criteria for the target value.

[0086] <Summary> According to the information processing system 1 (see FIG. 1) of this embodiment, medical personnel can check not only the blood glucose control target value but also the patient's age and pathological condition, which are factors that may change the target value, on the initial screen 280 (see FIG. 15) or the initial screen 290 (see FIG. 16). In addition, medical professionals can check the patient's age and condition on the initial screen 280 or 290 to confirm the blood glucose control target values ​​appropriate for the patient, as stipulated in the Diabetes Care Guidelines 2019, before the patient data viewing screen is displayed or before treatment begins.

[0087] Also, in this embodiment, by displaying target values ​​appropriate for each patient as numerical values ​​or indices on the patient data viewing screen, it becomes possible to view medical data such as patient data while checking target values ​​appropriate for the patient. As a result, not only specialists but also non-specialists will be able to provide medical procedures such as diagnoses based on the 2019 Diabetes Care Guidelines within a short consultation time.

[0088] <Embodiment 3> In this embodiment, the patient's disease is assumed to be adult bronchial asthma, and a case will be described in which a treatment method is presented as information to assist the patient's medical care. In the present embodiment, it is assumed that no therapeutic application is prescribed for the patient. For this reason, the information processing system in the third embodiment is composed of only the doctor terminal 20, or the doctor terminal 20 and a management system of a medical institution. Alternatively, a medical support server different from the medical application operation server 10 may be provided on the network N, and the services described below may be provided through the medical support server.

[0089] <Display processing of information to assist doctors in their medical treatment> FIG. 17 is an example of a flowchart illustrating a display process executed in the third embodiment. The processing operation shown in FIG. 17 is executed by the processor 21 (see FIG. 4) of the doctor terminal 20 (see FIG. 1). First, the processor 21 acquires medical data of a patient (step 301). The medical data is, for example, an electronic medical record of the patient.

[0090] In the case of this embodiment, the minimum essence published for the treatment of adult bronchial asthma is used as the treatment guideline. Figure 18 is a chart explaining the drug therapy plan prescribed in the minimum essentials of adult asthma treatment. FIG. 18 shows a chart 300 defining the diagnostic criteria for "assessment of control state," a chart 310 defining drug treatment methods for each "asthma treatment step," and a chart 320 defining the classification of "symptoms of untreated patients and treatment steps as a guide."

[0091] For untreated patients, they are classified into one of treatment steps 1 to 4 based on chart 320, and the treatment method of the corresponding treatment step in chart 310 is applied. For patients undergoing treatment, if the patient is classified as "well controlled" or "inadequately controlled" in Chart 300, treatment should be continued at the current treatment step, and for patients classified as "poorly controlled," the treatment step shown in Chart 310 should be stepped up.

[0092] Returning to the explanation of Figure 17. Next, the processor 21 displays an initial screen 340 including confirmation items for the patient's age and pathological condition based on the treatment guidelines (S302). In this embodiment, since adult bronchial asthma is assumed, confirmation items relating to the pathological condition are displayed.

[0093] Fig. 19 is a diagram for explaining a display example of an initial screen 340 assuming an untreated patient. The initial screen 340 shown in Fig. 19 is an example of information that assists medical treatment. The initial screen 340 shown in FIG. 19 is composed of an initial value 341 for the treatment step, an explanation 342 regarding the display content, a selection field 343 listing factors for changing the treatment step, and a button 344 used to display the treatment method corresponding to the treatment step.

[0094] In the case of FIG. 19, the initial value 341 of the treatment step displays the lowest step, "treatment step 1." It is indicated in the explanation 342 that the treatment step will be changed by checking the checkbox. In the case of FIG. 19, it is indicated that "The treatment step will be changed if the following items are checked." In the selection column 343, factors corresponding to the treatment steps 2 to 4 of the chart 320 are displayed by item.

[0095] For example, asthma symptoms are labeled as “at least once a week but not daily” corresponding to treatment step 2, “daily” corresponding to treatment step 3, and “daily (frequent asthma even under treatment)” corresponding to treatment step 4. For example, for nighttime symptoms, treatment step 2 corresponds to "more than twice a month," treatment step 3 corresponds to "more than once a week," and treatment step 4 corresponds to "often." For example, the interference with daily life is displayed as "once a month or more," which corresponds to treatment step 2, "once a week or more," which corresponds to treatment step 3, and "persistent," which corresponds to treatment step 4.

[0096] When any of these items is checked, the treatment step is changed to the corresponding step. For example, when "once a week or more" for nighttime symptoms is checked, the treatment step displayed on the initial screen 340 is changed from "treatment step 1" to "treatment step 3." The options displayed in the selection field 343 are examples of diagnostic criteria for treatment steps. When the button 344 labeled "Treatment Method" is operated, a treatment method corresponding to the treatment step of the patient is displayed.

[0097] Fig. 20 is a diagram for explaining a display example of an initial screen 350 assuming a patient under treatment. In Fig. 20, the parts corresponding to those in Fig. 19 are given the same reference numerals. The initial screen 350 shown in Fig. 20 is an example of information that assists medical treatment. The initial screen 350 shown in FIG. 20 is composed of an initial value 351 for the treatment step, an explanation 352 regarding the display content, a selection field 353 listing factors for changing the treatment step, and a button 344 used to display the treatment method corresponding to the treatment step. In the case of FIG. 20 as well, the initial value 351 of the treatment step is written as "treatment step 1."

[0098] However, only a check box corresponding to "poorly controlled" is displayed in the selection field 353. This is because, according to the treatment guidelines, stepping up the treatment step is limited to "poorly controlled." Therefore, when "Poor Control" is checked, the treatment step displayed on the initial screen 350 is changed from "Treatment Step 1" to "Treatment Step 2." When the button 344 labeled "Treatment Method" is operated, the patient's treatment steps and treatment method are displayed.

[0099] Returning to the explanation of Figure 17. During display of the initial screen 340 (see FIG. 19) or the initial screen 350 (see FIG. 20), the processor 21 determines whether or not a confirmation item has been selected (S303). The confirmation items here correspond to the check boxes in FIG. 19 and FIG. 20. If a confirmation item is selected, a positive result is obtained in S303. In this case, the processor 21 displays a treatment step according to the selection of the confirmation item (S304). As mentioned above, there are multiple check items for untreated patients and only one check item for treated patients.

[0100] After execution of S304, or if a negative result is obtained in S303 (no confirmation item is selected), the processor 21 determines whether or not a confirmation operation has been accepted (S305). The confirmation operation here is the operation of the button 344 (see Figs. 19 and 20) used to display the treatment method. The button 344 is labeled "Treatment Method."

[0101] If no operation of the button 344 is detected, a negative result is obtained in S305. In this case, the processor 21 returns to the determination process of S303. On the other hand, if an operation of the button 344 is detected, a positive result is obtained in S305. In this case, the processor 21 presents a treatment method corresponding to the treatment step (S306).

[0102] 21 is a diagram showing a display example of a treatment method screen 360 presenting a treatment method according to a treatment step. The treatment method here is an example of a treatment policy. The treatment method screen 360 is also an example of information that assists medical care. The treatment method screen 360 shown in FIG. 21 is composed of a treatment method explanation field 361 and a consultation start button 362. The start consultation button 362 is labeled "Start Consultation."

[0103] Returning to the explanation of Figure 17. When the treatment method screen 360 (see FIG. 21) is displayed, the processor 21 determines whether or not an operation of the examination start button 362 (see FIG. 21) has been accepted (S307). If the operation of the examination start button 362 is not detected, a negative result is obtained in S307. In this case, the processor 21 repeats the determination in S307.

[0104] On the other hand, if an operation of the examination start button 362 is detected, a positive result is obtained in S307. In this case, the processor 21 displays the screen of the medical care data (S308). This ends the processing up to the display of the screen of the medical care data. In this embodiment, the medical data is an electronic medical record of the patient. If a treatment application is prescribed for the patient, the medical data may be patient data input by the patient through the treatment application. In the case of this embodiment as well, a doctor or the like can confirm the treatment steps of a patient and the corresponding treatment method before starting treatment based on the medical data.

[0105] <Summary> According to the doctor terminal 20 (see FIG. 1) assumed in this embodiment, medical personnel can check not only the treatment steps of an asthma patient but also the pathological condition that is the diagnostic criterion on the initial screen 340 (see FIG. 19) or the initial screen 350 (see FIG. 20). In addition, medical personnel can confirm the patient's condition on the initial screen 340 or 350 to check the treatment steps and treatment methods appropriate for the patient based on the minimum essence of adult bronchial asthma before the medical data viewing screen is displayed or before treatment begins. As a result, medical treatment based on the minimum essence of bronchial asthma can be provided within a short consultation time not only by specialists but also by non-specialists.

[0106] <Fourth embodiment> In this embodiment, a case will be described in which the patient's illness is assumed to be chronic kidney disease, and a treatment method is presented as information to assist the patient's medical care. In the present embodiment, it is assumed that no treatment application is prescribed for the patient. Therefore, in the fourth embodiment, the information processing system is composed of only the doctor terminal 20, or the doctor terminal 20 and the management system of the health insurance medical institution. Alternatively, a medical support server different from the medical application operation server 10 may be provided on the network N, and the services described below may be provided through the medical support server.

[0107] Incidentally, the processing operation shown in FIG. 17 is also used in this embodiment. In this embodiment, the Evidence-Based CKD Clinical Practice Guidelines 2018 are used as the treatment guidelines. Figure 22 is a chart explaining the severity assessment classification stipulated in the Evidence-Based CKD Clinical Practice Guidelines 2018. In Figure 22, the difference in density of each cell corresponding to the combination of GFR categories G1 to G5 and A1 to A3 represents the severity. In Figure 22, the density is expressed in four stages, with the darker the cell, the higher the severity. The lightest density is green, followed by yellow, orange, and red in that order.

[0108] Fig. 23 is a diagram for explaining a display example of an initial screen 370 assuming a patient with chronic kidney disease. The initial screen 370 shown in Fig. 23 is also an example of information that assists medical treatment. The initial screen 370 shown in FIG. 23 is composed of an initial value 371 for the treatment stage, an explanation 372 regarding the display content, a selection field 373 listing factors determining the treatment stage, and a button 374 for instructing the display of a treatment method corresponding to the treatment stage. 23, "Treatment stage 1" is written in the initial treatment stage value 371. "Treatment stage 1" here corresponds to the stage with the least severe condition in FIG.

[0109] Explanation 372 indicates that the treatment stage is determined by a combination of checks in the check boxes. In the case of Fig. 23, it indicates "The treatment stage is determined by a combination of the following check items." In the selection column 373, factors required for determining the treatment stages 1 to 4 in FIG. 22 are displayed by item.

[0110] In the case of FIG. 23, the doctor or the like checks the primary disease, GFR category, and protein amount category, but these items may be automatically read from an electronic medical record or the like and input. When the automatic input specification is used, the initial value 371 may display the treatment stage determined according to the combination of input factors. When the button 374 labeled "Treatment Method" is operated, a treatment method according to the treatment stage of the patient is displayed.

[0111] 24 is a diagram showing a display example of a treatment method screen 380 presenting treatment methods for chronic kidney disease according to treatment stages. The treatment method screen 380 is an example of information that assists medical care. The treatment method screen 380 shown in FIG. 24 is composed of a treatment method explanation field 381 and a consultation start button 382. The start visit button 382 is labeled "Start Visit."

[0112] <Summary> According to the doctor terminal 20 (see FIG. 1) assumed in this embodiment, medical personnel can check not only the treatment stage of the patient but also the pathological condition that is the diagnostic criterion on the initial screen 370 (see FIG. 23). In addition, medical professionals can check the patient's condition on the initial screen 370 and confirm the treatment stage and treatment method appropriate for the patient based on the 2018 Evidence-Based CKD Treatment Guidelines before the medical data viewing screen is displayed or before treatment. As a result, not only specialists but also non-specialists can provide medical care based on the evidence-based CKD Treatment Guidelines 2018 within a short consultation time.

[0113] <Other embodiments> (1) Although the embodiments of the present disclosure have been described above, the technical scope of the present disclosure is not limited to the scope of the above-described embodiments. It is clear from the claims that the technical scope of the present disclosure also includes various modifications or improvements to the above-described embodiments.

[0114] (2) The processor in the above-described embodiments refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPU (=Central Processing Unit)) as well as dedicated processors (e.g., GPU (=Graphical Processing Unit), ASIC (=Application Specific Integrated Circuit), FPGA (=Field Programmable Gate Array), programmable logic devices, etc.). In addition, the operations of the processor in each of the above-mentioned embodiments may be executed by multiple processors in cooperation with each other, and the order of execution of each operation in the processor is not limited to the order described in each of the above-mentioned embodiments, and may be changed individually.

[0115] (3) In the above-described embodiment, an example was given of a case in which all authentication processing when accessing between the patient terminal 30 and the therapeutic application operation server 10 was completed within the server. However, the results may also be used in combination with authentication by a third party, including the business entity from which the patient obtained the therapeutic application or a telecommunications carrier.

[0116] (4) The therapeutic application described in the above embodiment is assumed to be prescribed to a patient with hypertension, but may be an application prescribed to a patient suffering from another disease. That is, the above-mentioned therapeutic application may be an application prescribed for, for example, nicotine addiction, insomnia, depression, diabetes, alcoholism, obesity, etc. The information to be inputted into the therapeutic application differs depending on the type of disease.

[0117] In the case of an app prescribed to patients with nicotine addiction, for example, carbon monoxide (CO) in the breath, nicotine concentration in saliva, smoking date and time, number of cigarettes smoked or number of times smoked, patient's cognitive information (way of thinking, values), exercise (number of steps, length of time exercised, distance traveled), other illnesses (diabetes), medication, blood pressure, heart rate, pulse, current physical condition (headache, irritability, feeling good, nausea, etc.), and all or part of the answers to the assumed causes are input. These pieces of information are examples of information related to smoking. In the case of an app prescribed to a patient with insomnia, for example, all or part of the following information is input: bedtime, wake-up time, sleep duration, sleep efficiency, number and type of meals, exercise record, and medication record. Bedtime, wake-up time, sleep duration, and sleep efficiency are examples of information related to sleep. In the case of an app prescribed to a patient with depression, for example, all or part of the following records may be entered: mood records, behavior records, medication records, sleep records, and appetite records.

[0118] In the case of an app prescribed for a diabetic patient, for example, all or part of the number and contents of meals, exercise records, medication records, weight, blood pressure value, and blood glucose level are input. Blood glucose level is an example of information related to blood glucose level. In the case of an app prescribed to patients with alcoholism, for example, medication records, whether or not they have drunk alcohol, and all or part of the details of their drinking are entered. In the case of an app prescribed to an obese patient, for example, all or part of the target weight, treatment start date, number of days of treatment, appropriate calorie intake, health history (mood), weight history, calorie intake history, date and time of calorie intake, medication history (dosage taken, date and time of taking medication), treatment history (treatment, content of advice, whether or not the patient performed it), medical history, blood data (AST (aspartate aminotransferase) / ALT (alanine aminotransferase)) and CT value are entered. The treatment application may allow input of information on a plurality of diseases.

[0119] (5) In the above-described embodiment, the processing operations executed by the treatment application operation server 10 and the doctor terminal 20 are described using Figures 5, 8 and 17, but the entity executing each processing operation is not limited to the exemplified contents. For example, the processing operation performed by the medical treatment application operation server 10 may be executed by the doctor terminal 20 or the management system of the medical institution to which the doctor belongs. Also, the processing operation performed by the doctor terminal 20 may be executed by the management system of the medical institution to which the doctor belongs, the medical treatment application operation server 10, or another server.

[0120] (6) In the above-mentioned first and second embodiments, hypertension and diabetes are exemplified as the patient's disease, and in the above-mentioned third and fourth embodiments, adult bronchial asthma and chronic kidney disease are exemplified as the patient's disease, but the present invention can be applied to other diseases. For example, the present invention can be applied to nicotine addiction, insomnia, depression, diabetes, alcoholism, obesity, and nephrotic syndrome.

[0121] (7) In the above explanation, the insurance medical institution is assumed to be a hospital or other facility where a doctor terminal 20 that prescribes a treatment app is installed, but when a pharmacist, public health nurse, nurse, nutritionist, hospital staff, or other medical personnel issues a prescription code, the insurance medical institution includes a facility or institution where an information terminal operated by a pharmacist, public health nurse, nurse, nutritionist, hospital staff, or other medical personnel is installed. In addition, the issuance of a prescription code is not limited to issuance for medical treatment, but may be issuance for uninsured medical treatment (i.e., non-insured medical treatment) or issuance for mixed medical treatment.

[0122] <Summary> The disclosed examples described in the above-mentioned embodiments are shown below. (((1))) An information processing system having one or more processors, which acquire information regarding at least one of a patient's age and pathological condition, and present to medical personnel information that assists in the medical treatment of the patient as specified in treatment guidelines for the disease being treated. This information processing system can provide a mechanism for providing medical care that complies with treatment guidelines.

[0123] (((2))) The information processing system according to (((1))), wherein the processor presents target values ​​for the observation subject according to the treatment goal as information to assist medical treatment. According to this information processing system, target values ​​according to treatment guidelines can be presented to medical personnel.

[0124] (((3))) The information processing system according to (((2))), wherein the processor displays, as a prerequisite for presentation, information regarding at least one of age and disease state for which the treatment guidelines stipulate diagnostic criteria for target values ​​as an option. According to this information processing system, target values ​​according to the age and pathological condition of the patient can be presented in accordance with the treatment goal.

[0125] (((4))) The information processing system according to (((3))), wherein the processor displays a numerical value corresponding to one or a combination of multiple options selected by a medical professional as a target value. According to this information processing system, target values ​​according to the age and pathological condition of the patient can be presented in accordance with the treatment goal.

[0126] (((5))) The information processing system according to (((2))), wherein the processor displays a viewing screen for medical data relating to the patient after accepting a confirmation operation of the target value. According to this information processing system, treatment can be started after confirming the blood pressure reduction target suitable for the patient.

[0127] (((6))) The information processing system according to (((5))), wherein the processor displays the target value in a portion of the viewing screen. According to this information processing system, it is possible to check target values ​​suitable for a patient on the medical data viewing screen.

[0128] (((7))) The information processing system according to (((5))), wherein the viewing screen is a screen used to view data entered by the patient through an app prescribed for the purpose of treating a disease. According to this information processing system, it is possible to check the pathological condition of the patient between the previous medical treatment and the current medical treatment, on the condition that the target value according to the treatment guideline is confirmed.

[0129] (((8))) The information processing system according to (((1))) or (((2))), wherein the processor presents a treatment plan according to a treatment step or treatment stage of the patient as information to assist medical treatment. According to this information processing system, a treatment plan according to the treatment guidelines can be presented to medical personnel.

[0130] (((9))) The information processing system according to (((8))), wherein the processor displays, as a prerequisite for presentation, information regarding at least one of age and pathological condition for which the treatment guideline specifies the diagnostic criteria for the treatment step or treatment stage as an option. According to this information processing system, a treatment plan according to the treatment guidelines can be presented to medical personnel.

[0131] (((10))) The information processing system according to (((8))), wherein the processor presents diagnostic criteria for a patient's treatment step or treatment stage as information to assist medical treatment. This information processing system can assist medical personnel in diagnosing a treatment step or stage.

[0132] (((11))) An information processing method in which a computer executes a process of comparing information regarding at least one of a patient's age and pathological condition with treatment guidelines for the disease being treated, and a process of presenting a treatment plan for the patient to medical personnel based on the comparison results. This information processing method can provide a mechanism for providing medical care that complies with treatment guidelines. It should be noted that in this information processing method as well, it is possible to combine techniques corresponding to (((2))) to (((10))).

[0133] (((12))) A program for enabling a computer to perform the following functions: comparing information regarding at least one of a patient's age and pathological condition with treatment guidelines for the disease being treated; and presenting medical professionals with information to assist in the patient's medical treatment based on the results of the comparison. The program provides a mechanism for providing care that is compliant with treatment guidelines. In addition, in this program, it is possible to combine technologies corresponding to (((2))) to (((10)). [Explanation of symbols]

[0134] 1...information processing system, 10...treatment application operation server, 11, 21, 31...processor, 12, 22, 32...ROM, 13, 23, 33...RAM, 14, 24, 34...auxiliary storage device, 15, 25, 35...communication interface, 16, 28, 38...signal line, 20...doctor terminal, 26, 36...display, 27, 37...input reception device, 30...patient terminal

Claims

1. One or more processors; The one or more processors: obtaining information on at least one of the patient's age and pathological condition, and presenting to medical personnel information to assist in the medical treatment of said patient as defined in treatment guidelines for the disease being treated; Information processing system.

2. The processor, Present a target value of an observation subject according to a treatment goal as information to assist the medical treatment; The information processing system according to claim 1 .

3. The processor, As a prerequisite for the presentation, information on at least one of age and pathological condition for which the treatment guideline specifies the diagnostic criteria for the target value is displayed as an option. The information processing system according to claim 2 .

4. The processor, displaying a numerical value corresponding to one or more combinations of the options selected by a medical professional as the target value; The information processing system according to claim 3 .

5. The processor, After receiving a confirmation operation of the target value, a viewing screen of the medical data related to the patient is displayed. The information processing system according to claim 2 .

6. The processor, displaying the target value on a part of the viewing screen; 6. The information processing system according to claim 5.

7. The viewing screen is a screen used to view data entered by a patient through an application prescribed for the purpose of treating a disease, 6. The information processing system according to claim 5.

8. The processor, Present a treatment plan according to a treatment step or treatment stage of the patient as information to assist the medical treatment; 3. The information processing system according to claim 1 or 2.

9. The processor, As a prerequisite for the presentation, the treatment guideline displays, as an option, information on at least one of age and pathological condition that specifies the diagnostic criteria for the treatment step or the treatment stage. The information processing system according to claim 8.

10. The processor, Present diagnostic criteria for a patient's treatment step or treatment stage as information to assist in the medical treatment; 8. An information processing system according to claim 1.

11. The computer obtaining information regarding at least one of the patient's age and condition; presenting to medical personnel information that aids in the medical treatment of said patient, as defined in a treatment guideline for the disease being treated; An information processing method for performing the above.

12. On the computer, A function for acquiring information regarding at least one of the patient's age and pathology; a function of presenting to medical personnel information that assists in the medical treatment of the patient as defined in a treatment guideline for the disease being treated; A program to achieve this.

Images