Program, information provision method, and information processing device.

Abstract

This system provides psychological support for users' efforts to treat or prevent diseases. [Solution] A program is used to enable a computer to display the user's status regarding management indicators based on health data recorded by the user who is working to treat or prevent a disease.

Description

Technical Field

[0001] The present disclosure relates to a program, an information providing method, and an information processing apparatus.

Background Art

[0002] As a means for supporting the improvement of lifestyle habits, the utilization of application programs (hereinafter referred to as "user apps") executed on user terminals has attracted attention. Currently, various user apps for supporting the improvement of lifestyle habits are publicly available in app stores.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] A user app can record health-related data by the user in the form of a diary. The use of the user app is expected to have the effect of supporting the effort to improve lifestyle habits. However, there are individual differences in the progress of improving lifestyle habits with the support of the user app, and there is a concern that the delay in improvement may lead to a decrease in the user's motivation.

[0005] The present disclosure provides a mechanism for supporting a user's effort for the treatment or prevention of diseases.

Means for Solving the Problems

[0006] One aspect of the disclosure is a program for causing a computer to realize a function of presenting a user's state regarding a management index from health-related data recorded by a user who is working on the treatment or prevention of a disease. The function may present the user's status regarding management indicators using graphs. Furthermore, the function may present the user's status using radar charts with multiple management indicators as vertices of a polygon. The proposed functionality may generate the user's initial state regarding management metrics based on their answers to questions about those metrics. The function presented may also display the user's status regarding management indicators in a format that does not decrease from the previous value. The function may also display the patient's status related to management indicators on the terminal operated by the user. The program used by users to record data may include a function to display the user's status regarding management indicators. One disclosure is an information provision method in which a computer performs processing to present the user's status regarding management indicators from health data recorded by the user who is working to treat or prevent a disease. One of the disclosures is an information processing device having a processor, which presents the user's status regarding management indicators from health data recorded by the user who is working to treat or prevent a disease. [Effects of the Invention]

[0007] One form of this disclosure can provide psychological support to users' efforts toward treating or preventing diseases. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram illustrates an example of a patient terminal's hardware configuration. [Figure 2] This is a diagram illustrating an example of patient app data. [Figure 3] This is a flowchart illustrating an example of how the patient application processes. [Figure 4] This is a diagram illustrating an example of the home screen in "Step 1". [Figure 5] This diagram illustrates the processing flow of type analysis. [Figure 6]This diagram illustrates an example of a display screen for the results of type analysis. [Figure 7] This diagram illustrates an example of the display screen for setting action goals in "Step 1". [Figure 8] This diagram illustrates an example of the display screen for setting action goals in "Step 2". [Figure 9] This diagram illustrates an example of the display screen for the results of the second type analysis. [Figure 10] This diagram illustrates other display examples of the action goal setting screen in "Step 2". [Figure 11] This diagram illustrates an information processing system consisting of a management server for managing patient data and patient terminals. [Figure 12] This is a flowchart illustrating an example of the processing operation of an information presentation application. [Modes for carrying out the invention]

[0009] <Terminology> First, we will explain the terminology used in the embodiments described later. A "program designed to encourage behavioral change" refers to a program intended to encourage a change in a person's behavior. However, this program does not guarantee a change in a person's behavior. Whether or not a person's behavior actually changes depends on the user of the program. Therefore, a program designed to encourage behavioral change can also be described as a program that supports behavioral change.

[0010] This type of program includes programs classified as medical devices and programs classified as non-medical devices (hereinafter also referred to as "programs that promote behavioral change, etc."). Programs classified as medical devices are examples of programs that require a prescription, while programs classified as non-medical devices are examples of programs that do not require a prescription. Furthermore, programs classified as non-medical devices are not limited to programs that encourage behavioral change; they may also include programs that have the function of recording health-related data. Programs that promote behavior change or have a function to record health-related data include, in addition to programs that can be downloaded from the app store, programs used by private businesses, public organizations, etc. for the health management of employees, etc.

[0011] Among the programs classified as non-medical devices, there are also programs used in medical institutions. When distinguishing a program executed on a terminal operated by a user (i.e., a user terminal) from the programs used in medical institutions among the above-mentioned programs, the program in question may be referred to as a user app.

[0012] The "purpose of the app" refers to the effect to be achieved by using a program that promotes behavior change or the like. The purpose of the app varies depending on the disease corresponding to the program that promotes behavior change or the like. For example, the purposes of the app include improvement of lifestyle, continuation of the improved lifestyle, and continuation of the improved numerical values. The "goal of the app" refers to the goal aimed at by using a program that promotes behavior change or the like. The goal is determined from the perspective of achieving the purpose. The goal is classified into qualitative indicators and quantitative indicators. Also, the goal is classified into indicators defined by measured values or other numerical values and indicators defined by the content of actions. For example, the goals include improvement and maintenance of habits, actions, and numerical values. Note that the goal of the app can also be defined by one or more sub-goals. A sub-goal is a goal with a small granularity set to achieve the corresponding goal.

[0013] A "treatment app" refers to a program that has obtained approval under the Pharmaceutical Affairs Law. A treatment app is a program classified as a medical device. Treatment apps are approved for each disease. Diseases for which approval has already been obtained include, for example, hypertension, nicotine dependence, and insomnia. Also, diseases for which treatment apps are under development include, for example, NASH (non-alcoholic steatohepatitis), diabetes, dyslipidemia, kidney disease, and alcohol dependence.

[0014] A "user" refers to a person who uses a program that has the function of recording health-related data. A person who works to treat or prevent a disease through the aforementioned programs that encourage behavioral change is an example of a user. A person who works to treat or prevent a disease is also called a person who changes their behavior or a person who works to change their behavior. Users include those who have not yet visited a medical institution and those who have visited a medical institution. Users who have visited a medical institution include those who are eligible for medical fee calculation and those who are not eligible for medical fee calculation. "Patient" refers to a user who is receiving treatment at a medical institution. In other words, a patient is a user who has started or is currently receiving treatment at a medical institution.

[0015] Treatment apps include patient apps and doctor apps. A "patient app" is a program that runs on a device operated by the patient (hereinafter also referred to as the "patient device") and is prescribed to the patient by a doctor. In this sense, patient apps are also called PDT (=Prescription Digital Therapeutic). The patient app can be downloaded, for example, from an app store. In the embodiment described later, the code required for activation (hereinafter referred to as the "prescription code") is issued by a doctor upon prescription. The patient app is used to record patient health data outside of medical facilities (hereinafter also referred to as "patient app data").

[0016] Patient apps have an expiration date set upon approval. This expiration date is determined based on, for example, the period during which the public health insurance system applies. The expiration date is also determined by the type of disease the patient app addresses. For example, the expiration date for a hypertension patient app is six months, starting from the month following the month in which the app was prescribed. However, six months is just an example; it could be nine months or twelve months, for example. The expiration date can also be set in days, such as 60 days or 180 days, or in weeks, such as eight weeks or 24 weeks. Needless to say, these numbers are just examples. Programs classified as non-medical devices generally do not have a set expiration date. However, it is permissible to set an expiration date even for programs classified as non-medical devices.

[0017] A "doctor's app" refers to a program that can be used through a terminal operated by a doctor (hereinafter also referred to as a "doctor's terminal"). A doctor's app runs, for example, on a cloud server that can be operated from a doctor's terminal. Alternatively, a doctor's app may run on the doctor's terminal itself. Doctor's apps are used to view patient data (including patient app data). Medical professionals are also referred to as healthcare workers.

[0018] "Patient data" includes, for example, patient attributes, measurements, activity records, mood records, physical condition records, medical history, patient app usage history, biological characteristics, psychological characteristics, social characteristics, habits, goal achievement status, and answers to various questions. Patient data is an example of health data recorded by users working on behavioral change, and an example of health data recorded by users working on the treatment or prevention of disease. However, the information recorded as patient data varies depending on the disease, and it does not need to include all of the example information; it may include only some of it, or other information. Furthermore, all the information recorded as patient data is also an example of health-related data.

[0019] "Patient attributes" include, for example, the patient's name, gender, and date of birth. This information is just one example of basic patient information. "Measured values" refer to numerical values ​​measured using measuring instruments. The items of measured values ​​recorded as patient app data are defined for each disease. For example, if the disease is hypertension, blood pressure values ​​will be recorded as measured values. Blood pressure values ​​are defined, for example, as systolic blood pressure (i.e., maximum blood pressure) and diastolic blood pressure (i.e., minimum blood pressure). For example, if the disease is nicotine addiction, the measured values ​​recorded include carbon monoxide (CO) in exhaled breath and nicotine concentration in saliva. Other measured values ​​include pulse rate, respiratory rate, weight, body temperature, blood glucose level, Na / K ratio, oxygen saturation, and electroencephalogram (EEG).

[0020] "Activity records" include, for example, patient app operation history, medication records, meal records, smoking records, alcohol consumption records, and exercise records. These records also represent the user's behavior. Activity records are just one example of information related to activities. A "mood record" is, for example, a record of the user's perceived mood. A mood record is just one example of information related to mood. "Health record" refers to a record of physical condition or symptoms as perceived by the user. A health record is just one example of information related to health. Records of activities, mood, and physical condition are examples of records related to the practice of behavioral goals and the habituation of behaviors. This information is recorded, for example, as a "daily reflection."

[0021] "Medical history" includes, for example, the date treatment began, the date of the consultation, the content of the treatment, the agreement between the doctor and the patient, and the doctor's advice to the patient. Medical history is just one example of information related to a medical consultation. The "patient app operation history" includes, for example, the history of operations such as launching the patient app and inputting measurements and reflections. The patient app operation history is an example of putting behavioral goals into practice and habituating those actions. The "patient app operation history" is also the usage history of the user app. "Biological characteristics" include, for example, the presence or absence of other diseases, injuries currently being treated, the presence or absence of knee or foot pain, experience with disease treatment, and the number of years since the disease was diagnosed.

[0022] "Psychological characteristics" include, for example, expectations for app-based treatment, willingness to acquire knowledge about disease treatment, whether one finds reducing salt intake difficult, whether one believes one cannot change their taste preferences, and psychological resistance to leaving food on one's plate. "Social characteristics" include, for example, the type of work (e.g., shift work, day shift, night shift), the days of the week worked, the start time of work, the time of return home, regular days off, and the presence or absence of heating equipment in the changing room.

[0023] "Habits" include, for example, exercise habits, weight measurement habits, habits of checking calorie information on food labels, habits of choosing low-fat foods, habits of not consuming caffeine after 4 PM, eating habits after 10 PM, skipping breakfast habits, snacking habits, bathing habits one hour before bedtime, habits of stretching or massaging before bedtime, habits of getting more than 6 hours of sleep, wake-up and bedtime, the intensity of seasoning at home, and the amount of food consumed.

[0024] "Goal achievement status" refers to information showing the progress toward goals set by a doctor for each patient. It could also be information showing the progress toward goals set by the patient themselves. Furthermore, it could be information showing the progress toward goals presented by a patient app for each patient. Goal achievement status is an example of the practice of behavioral goals and the habituation of those behaviors. Furthermore, the information mentioned above can be classified into subjective information and objective information.

[0025] Patient data is recorded using various formats, such as text, images (video and still images), audio, numerical data, and codes. Images include pictures of the affected area (e.g., inflamed areas) taken by the patient. Video and audio recordings are useful, for example, in the examination of mental illnesses. "Health-related data" refers to data owned by or related to a user, and includes personal information. Health-related data may include data recorded through programs that encourage behavioral change, as well as data obtained by processing such data. Furthermore, health-related data may include data measured at medical institutions, data recorded by doctors during consultations, and data obtained by processing these.

[0026] The processing here also includes processing by AI (Artificial Intelligence). The processed data includes, for example, processed data, data obtained through statistical processing, and summaries of patient data generated by AI. The processed data includes, for example, the mean, the maximum and minimum values ​​within a given period, the data distribution for each given period, and the difference from the baseline value. Health-related data may include data related to programs other than those that have the function of recording health-related data or programs that encourage behavioral change. For example, it may include user accounts used to access various services and privacy-related information. Health-related data can be qualitatively identifiable or quantitatively identifiable. Hereinafter, qualitatively identifiable information will be referred to as "qualitative information," and quantitatively identifiable information will be referred to as "quantitative information."

[0027] "Management indicators" refer to indicators related to diet and exercise that characterize lifestyle habits and are managed by the user app (including the patient app). In the case of NASH, management indicators include, for example, "food content," "substitute eating," "eating motivation," "regularity of eating habits," "snacks," "nutritional balance," "exercise," and "eating habits." Each of these indicators is an example of a management indicator. You may use some of the eight indicators exemplified as your management indicators. These may include not only multiple indicators, but also a single indicator. In addition, the management indicators may be a combination of the eight indicators exemplified and other indicators different from these. Furthermore, the management indicators may be a combination of some of the eight indicators exemplified and other indicators different from those exemplified. Also, the management indicators may be a combination of other indicators different from any of the eight indicators exemplified.

[0028] Furthermore, the indicators or combinations of indicators used as management indicators may be set for each disease. Furthermore, the indicators or combinations of indicators used as management indicators may differ depending on the patient app, for example. For instance, patient app A might use "meal content," "substitute feeding," "eating motivation," "regularity of eating habits," "snacks," "nutritional balance," "exercise," and "eating style" as management indicators, while patient app B might use "meal content," "substitute feeding," "eating motivation," and "regularity of eating habits" as management indicators.

[0029] In the embodiment described later, a score corresponding to each indicator is calculated based on health data recorded by a user who is working to treat or prevent a disease. The score here is an example of data obtained by processing health data recorded by a user who is working to treat or prevent a disease. The process of calculating a score can involve several methods: calculating the score through calculations; determining the score using pre-defined branching rules (e.g., programs, judgment tables); or inputting health data into a pre-trained model (such as one created using machine learning) that has been trained to understand the relationship between health data and the score, and then outputting the score.

[0030] A "PDT server" is a server that manages patient data entered through patient applications, etc. A PDT server is also an example of a cloud server. A PDT server is typically set up for each patient application. Therefore, in order for a doctor to view patient data, they must log in to the PDT server running the doctor's application that is paired with the patient's application.

[0031] For example, if a patient is using a hypertension patient app provided by service provider A, the doctor needs to log in to the PDT server operated by service provider A for hypertension. Furthermore, if a patient is using a hypertension patient app provided by service provider B, the doctor needs to log in to the PDT server operated by service provider B for hypertension.

[0032] Furthermore, if a patient is using a patient app for nicotine addiction provided by service provider A, the doctor needs to log in to the PDT server operated by service provider A for nicotine addiction. Furthermore, a single PDT server may be shared among multiple patient applications targeting different diseases. Furthermore, multiple patient apps provided by different service providers may share a single PDT server.

[0033] The "PDT platform" is a server that manages the prescription of patient apps and the usage status of those apps after prescription. The PDT platform is also an example of a cloud server. The PDT platform is also called an APS (Application Prescription Service) server, as it is a server that provides prescription services for patient apps. Usage statuses include, for example, "Not yet started," "Start date expired," "In use," "Scheduled to end," "Ended," and "Period expired."

[0034] The PDT platform supports multiple patient apps that target the same disease but are provided by different service providers, as well as multiple patient apps that are provided by the same service provider but target different diseases. In this sense, the PDT platform functions as a platform for multiple patient applications. Apps running on the PDT platform manage the usage status of multiple patient apps, each with different diseases and service providers, on a patient-by-patient basis.

[0035] In the embodiment described later, "medical institution" refers to a health insurance medical institution. More specifically, a medical institution refers to a health insurance medical institution to which the doctor who issues the prescription code necessary to activate the patient app belongs. However, if deregulation allows pharmacists, public health nurses, nurses, dietitians, hospital staff, and other healthcare professionals (hereinafter also referred to as "physicians, etc.") to issue prescription codes, then the term "healthcare institution" will also include facilities and organizations where these healthcare professionals are located.

[0036] Furthermore, prescription codes may be issued not only through medical consultations, but also through uninsured medical services (i.e., private medical services) or mixed medical services. Incidentally, medical consultations include not only in-person consultations but also online consultations. "Consultation" refers to receiving a medical examination at a medical institution. In the embodiments described below, the examination may include not only consultations by doctors but also interviews by other medical professionals. For example, it may include interviews by nurses or pharmacists.

[0037] <Embodiment> <Device Configuration> Figure 1 illustrates an example of the hardware configuration of the patient terminal 10. The patient terminal 10 is a terminal operated by a patient undergoing treatment or prevention of a disease. The patient terminal 10 is an example of a user terminal. Furthermore, the patient terminal 10 is also an example of an information processing device. In this embodiment, a patient application 130 is assumed to be the program used for inputting health-related data. Patient app 130 is an example of a program that enables the presentation of a user's status regarding management indicators based on health data recorded by users working to treat or prevent a disease.

[0038] The patient terminal 10 may be, for example, a smartphone, smart glasses, a desktop computer, a laptop computer, or a tablet computer. The patient terminal 10 shown in Figure 1 includes a processor 11, semiconductor memory 12, auxiliary storage device 13, input interface 14, input device 15, output interface 16, output device 17, and communication interface 18. Each device is connected via a bus or other signal lines.

[0039] The processor 11 is a device that realizes various functions through the execution of a program. The processor 11 may be composed of multiple CPU (=Central Processing Unit) cores. In that case, the processor 11 executes the program through the cooperation of the multiple CPU cores. The semiconductor memory 12 stores UEFI (Unified Extensible Firmware Interface), etc. The semiconductor memory 12 is also used as an execution area for programs. The processor 11 and the semiconductor memory 12 function as a computer.

[0040] The auxiliary storage device 13 is composed of, for example, a hard disk drive or semiconductor storage. The auxiliary storage device 13 stores the operating system and other programs. In this embodiment, the patient application 130 is stored as one of the other programs. The patient application 130 in this embodiment is assumed to be an application prescribed to patients with NASH. Hereinafter, the patient application 130 prescribed to NASH patients will also be referred to as the "NASH application". The NASH application is used for recording weight, etc. The weight and other information recorded in the NASH application can be viewed by a physician operating a terminal at a medical institution via a PDT server (not shown), etc. This viewing allows the physician to utilize changes in weight at home in examinations. In addition, patient application data 131 is also recorded in the auxiliary storage device 13.

[0041] The input interface 14 uses, for example, USB (Universal Serial Bus) or Bluetooth (registered trademark) to connect to the input device 15. The input device 15 can be, for example, a keyboard, mouse, or touch panel. The output interface 16 can use interfaces such as HDMI (High-Definition Multimedia Interface) (registered trademark) or LAN (Local Area Network) for connection to the output device 17. The output device 17 can be, for example, a monitor or a printer. The communication interface 18 is an interface for communicating with external terminals via a network. The communication interface 18 supports Ethernet®, Wi-Fi®, mobile communication systems, and other communication standards.

[0042] <Patient App Data> Figure 2 illustrates an example of patient app data 131. As mentioned above, patient app data 131 is an example of health data recorded by the patient through the patient app 130 (see Figure 1). The patient app data 131 shown in Figure 2 includes the measured value / measurement date and time 131A, the reflection / input date and time 131B, the current step of the treatment plan 131C, the treatment plan implementation history 131D, the behavioral goal 131E, and the target value 131F. Note that the items exemplified do not need to be all of the patient app data 131; they may be only a part of it, or other items may be included.

[0043] The measurement / measurement date and time 131A records the health-related values ​​and dates measured by the patient. In the case of the NASH app, the measured weight and the date and time of measurement are recorded. In the case of the hypertension patient app 130, the measured blood pressure value and the date and time of measurement are recorded. The blood pressure value is given as systolic blood pressure and diastolic blood pressure. In the case of the nicotine addiction patient app 130, the measured carbon monoxide concentration and the date and time of measurement are recorded.

[0044] The "Reflection / Input Date & Time 131B" field records a reflection on the day's activities and the date and time of entry. In the case of a patient app for NASH patients, the reflection may include, for example, the level of physical condition, stress level, length of sleep, weight, amount of alcohol consumed, time when meals started, time when meals ended, content of meals, whether snacks were eaten, what snacks were eaten, number of cigarettes smoked, details of activities performed, and a diary (user's thoughts on the day's activities, etc.). The reflection is essentially a record of daily life.

[0045] The details of the actions taken are recorded, for example, by the category of the action taken and by text input. Recording the category of the action taken is done by checking buttons labeled with "salt reduction," "weight loss," "exercise," etc. Other labels include, for example, "sleep," "stress," "moderate alcohol consumption," and "other." Needless to say, the content of the behaviors to be recorded varies depending on the disease. Text input allows for the free entry of information and emotions that cannot be recorded by checking buttons.

[0046] The current step 131C of the treatment plan records the steps indicating the progress of the treatment plan provided by the patient app 130. In this embodiment, the treatment plan consists of three steps. These three steps are, for example, the "Knowledge Acquisition" step, the "Implementation of Behavioral Goals" step, and the "Habituation of Behavior" step. These three steps are executed in the order they are written. For this reason, the "Knowledge Acquisition" step is also called "Step 1," the "Implementation of Behavioral Goals" step is also called "Step 2," and the "Habituation of Behavior" step is also called "Step 3." The behavioral goals here are examples of sub-goals to be implemented in order to achieve the main goal. Behavioral goals are set for each behavior. Treatment plan implementation history 131D records the history of learning and behaviors implemented in accordance with the treatment plan.

[0047] For example, in the case of the hypertension patient app 130, "Step 1" records whether or not each learning item has been completed as part of the learning history. "Step 1" is also called the basic learning step. The learning record in "Step 1" is an example of a record related to the acquisition of knowledge about the disease. In the case of the NASH patient app 130, "Step 2" records behavioral history, such as "don't overeat," "limit fried foods," "reduce snacks," and "exercise." "Step 2" is also called habit formation support. In "Step 2," these behaviors are practiced as goals for a unit practice period. A unit practice period is, for example, 8 days. The record of the progress of the goals in "Step 2" is an example of a record regarding the practice of behavioral goals.

[0048] In the case of the NASH patient app 130, "Step 3" records the progress of the patient in implementing the behaviors they have set as goals. "Step 3" is also called habit management. The record of behavioral implementation in "Step 3" is an example of recording the habit formation of a behavior. Behavioral objective 131E records the actions the patient has set as goals for each period. These goals include, for example, one or more actions selected by the patient from among the goals presented by the patient app 130 as the treatment plan progresses. Specifically, these are the actions set or selected by the patient in "Step 2" or "Step 3" of the treatment plan.

[0049] The behavioral goals are not limited to those set or selected from the behaviors presented by the patient app 130; they may also be behaviors set individually by the patient. Furthermore, individual patient behavioral goals may be set by the physician through their screen. An example of this type is a treatment app for alcohol dependence. The target value 131F will record, for example, the value set by the doctor during the examination. However, if the patient can set the target value themselves, the value set by the patient will be recorded in target value 131F. Examples of target values ​​include blood pressure, daily alcohol intake, number of alcohol-free days, and body weight. In these cases, the target values ​​are all given numerically. In that they are given numerically, target values ​​are an example of quantitative targets.

[0050] <Patient App Processing Actions> Figure 3 is a flowchart illustrating an example of the processing operation of the patient application 130 (see Figure 1). In Figure 3, the symbol S represents a step. Needless to say, the patient application 130 is executed on the patient terminal 10.

[0051] <Initial settings> <Step 101> Patients who have successfully installed the patient app 130 will begin the initial setup. That is, the patient terminal 10 will accept the initial registration for the patient app 130. In order to make the patient app 130 usable, the prescription code must be successfully authenticated by a PDT platform (not shown). During initial registration, for example, initial values ​​for patient attributes and physical information are recorded. Patient attributes include, for example, name, gender, date of birth, patient's biological characteristics, patient's psychological characteristics, patient's social characteristics, and patient's habits.

[0052] In this embodiment, the patient's biological characteristics, psychological characteristics, social characteristics, and habits each consist of multiple items. Each item has multiple choices, and one or more choices selected by the patient are recorded as the answer to the item. Initial physical information recorded during initial registration includes, for example, height, weight, and blood pressure.

[0053] Data collected through the patient app 130, including information recorded during initial registration (i.e., patient app data), is uploaded to a PDT server (not shown) at a predetermined time. Patient app data is uploaded, for example, when new data is recorded or data is updated while patient app 130 is logged into the PDT server. In addition, patient app data is also uploaded from the patient app to the PDT server when the patient logs into the PDT server.

[0054] <Step 102> Once the patient completes initial registration, the patient terminal 10 (i.e., the patient app 130) begins management based on the treatment plan in the patient app 130. The treatment plan in this embodiment consists of three steps: the "Knowledge Acquisition" step, the "Implementation of Behavioral Goals" step, and the "Habituation of Behavior" step. However, this classification is just an example, and the number of steps is not limited to three. For example, there may be two steps, or four or more steps. Also, the names and contents of each step are not limited to those exemplified.

[0055] The "knowledge acquisition" step is also called the learning step. In this embodiment, the "knowledge acquisition" step lasts 12 days. Of course, 12 days is just an example and will be determined according to the disease. Also, even for the same disease, different periods may be set by the patient app 130. In the "Knowledge Acquisition" step, the patient app 130 supports the acquisition of basic knowledge about the disease. The progress of knowledge acquisition is checked, for example, through answers to quizzes. If the answer to a question consists of multiple choices, one or more choices selected by the patient are recorded as the answer. Furthermore, in the "knowledge acquisition" step, the patient app 130 assists in recording daily life measurements (e.g., weight and blood pressure) and recording reflections.

[0056] The "implementation of behavioral goals" step is a step aimed at improving the patient's lifestyle through the implementation of behavioral goals. In this embodiment, the "implementation of behavioral goals" step is approximately 6 months. Of course, 6 months is just an example and will be determined according to the disease. Furthermore, even for the same disease, different periods may be set for each patient app 130. In this embodiment, the "implementation of behavioral goals" step involves "setting behavioral goals," "learning behavioral goals," "implementation of behavioral goals," and "reflection," all of which are managed with the support of the patient app 130.

[0057] In this embodiment, the implementation period for the "implementation of behavioral goals" step consists of multiple unit implementation periods. In this embodiment, each unit implementation period is 8 days long. In this embodiment, "setting behavioral goals" and "learning behavioral goals" are allocated to the first day of the unit implementation period, while "implementation of behavioral goals" and "reflection" are allocated to the 7 days from the second to the eighth day of the unit implementation period. Therefore, in the "Implementing Action Goals" step, the following cycle is repeated every eight days: "Setting Action Goals," "Learning about Action Goals," "Implementing Action Goals," and "7-Day Review." In this embodiment, the patient application 130 has a function that suggests behaviors that the patient finds difficult as candidate behavioral goals. However, it is the patient themselves who decides which behavioral goals to actually pursue.

[0058] The "habit formation" step aims to solidify the improved lifestyle habits achieved through the implementation of behavioral goals. However, for patients whose lifestyle habits have not improved sufficiently, the "implementation of behavioral goals" step is essentially repeated. The "habituation of behavior" step in this embodiment also takes approximately 6 months. Of course, 6 months is just one example, and the duration will be determined according to the disease. Furthermore, even for the same disease, different periods may be set for each patient app 130. When targeting patients aiming to solidify improved lifestyle habits, setting behavioral goals is optional in the "habituation of behavior" step. That is, patients may or may not set behavioral goals. The "habituation of behavior" step for patients aiming to solidify improved lifestyle habits becomes a period of behavioral recording.

[0059] <Step 103> The patient terminal 10 (i.e., the patient app 130) sets the current step of the treatment plan to "Step 1". "Step 1" corresponds to the "Knowledge Acquisition" step mentioned earlier. <Step 104> The patient terminal 10 (i.e., the patient app 130) displays information related to "Step 1" on its home screen to support the recording of daily learning and activities. Figure 4 is a diagram illustrating an example of the home screen 200 in "Step 1". The home screen 200 shown in Figure 4 consists of an information section 201, a task section 202, and an advice section 203.

[0060] The information section 201 shown in Figure 4 has a weight section 201A related to the weight being measured, and a function section 201B representing the functions available in the patient application 130. The weight column 201A shown in Figure 4 is an example of the display on the first day of using the patient app 130 (i.e., day 1). Therefore, "Day 1" is displayed in the weight column 201A. The weight column 201A also includes fields for "Current Date," "Current Weight," "Target Weight," and a graph field to display the weight change over a three-month period. Incidentally, the current date is "October 1st (Tuesday)". Also, the current weight is blank because it has not been entered. The target weight is "66.2 kg". Since it is the first day, the graph column is also blank. Note that the vertical axis of the graph column is weight, and the horizontal axis is month. In Figure 4, October, November, and December are displayed along the horizontal axis.

[0061] The function panel 201B shown in Figure 4 consists of the "Data" button, the "Implementation Record" button, the "Behavioral Goal" button, the "Consultation Management" button, and the "Quiz" button. In Figure 4, the "Quiz" button is inactive. Therefore, the "Quiz" button is grayed out. The other four buttons are active. Therefore, these four buttons are displayed as active. The task column 202 shown in Figure 4 is titled "Things to do today." Task column 202 displays the tasks managed in "Step 1" of the treatment plan. In Figure 4, there are three tasks that the patient performs on the day of operation on the home screen 200.

[0062] In Figure 4, the tasks "Let's weigh ourselves" (Task 202A), "Basic Learning 1: Let's start NASH treatment" (Task 202B), and "Let's keep a record of our activities" (Task 202C) are displayed. The "Basic Learning 1: Let's start NASH treatment" (Task 202B) also displays a "Start Learning" button. For example, when the "Measure Your Weight" task 202A is performed, the weight recording process is executed. If the patient terminal 10 and a scale (not shown) are connected via Bluetooth, the patient's weight is imported from the scale to the patient app 130. If there is no Bluetooth-connected scale, a screen for manual weight entry is displayed.

[0063] For example, when the "Start Learning" button is pressed in task 202B, "Basic Learning 1: Let's Start NASH Treatment," pre-prepared content will be displayed in order. In this embodiment, "Step 1" has 12 items of content. For example, the fourth item can be displayed after the third item is completed. In this embodiment, one item of content is assigned per day. It is also possible to learn multiple items of content in a single day. Furthermore, it is possible to relearn previously learned content.

[0064] For example, if you perform the "Keep a Record of Your Activities" task 202C, the "Daily Review" screen will appear. On the "Daily Review" screen, actions you consciously performed and diary entries are recorded. Actions you consciously performed include, for example, "controlling overeating," "reducing snacking," "reducing fried foods," and "exercise." Advice section 203 displays advice relevant to the current operation. In Figure 4, advice section 203 reads, "Start basic learning by clicking the 'Start Learning' button."

[0065] When the "Quiz" button is activated, the "Quiz" task is displayed in the task column 202. In this embodiment, the "Quiz" button is activated after the completion of learning on the start date of the latter half of "Step 1". In this embodiment, since the period of "Step 1" is 12 days, it becomes available every 7 days after the start date of using the patient app 130. The "Quiz" task displays questions that test the patient's knowledge of the disease. In this embodiment, the patient's answer is accepted in the form of selecting one option from, for example, three choices.

[0066] <Step 105> Patient app 130 performs a type analysis as one of the initiatives in "Step 1" and displays the analysis results in a radar chart. The radar chart here is one example of how the user's status regarding management indicators can be presented. The type analysis is performed as part of "Basic Learning 1". The type analysis examines the patient's eating habits and way of thinking. In this embodiment, step 105 is executed as the 11th item associated with the "Start Learning" button. In this embodiment, the 11th item is the second to last item.

[0067] Figure 5 is a diagram illustrating the processing flow of type analysis. The learning screen 210 shown in Figure 5 is displayed when the "Start Learning" button in the "Basic Learning 1: Let's Start NASH Treatment" task 202B (see Figure 4) on the home screen 200 (see Figure 4) is pressed.

[0068] The learning screen 210 shown in Figure 5 displays a description of the learning content 211, a "back" button 212, and a "next" button 213. When the "back" button 212 is pressed, the user returns to the home screen 200. When the "next" button 213 is pressed, questions related to psychology and health begin. In the case of Figure 5, the explanation of the learning content 211 states, "Today we will conduct a 'question about Ms. Suzuki's state of mind and environment' and a 'type analysis'." Questions about "state of mind" are, for example, questions about "psychological characteristics." Questions about "environment" are, for example, questions about "social characteristics." In this embodiment, there are 12 questions. Needless to say, the number of questions is just an example.

[0069] After answering questions about psychology and health, the questions for type analysis begin. The type analysis includes questions about eating habits and ways of thinking. These questions are, for example, about "habits." In this embodiment, there are 40 questions. Needless to say, the number of questions is just an example. Once all questions have been answered, the patient app 130 begins analyzing the patient's type.

[0070] Type analysis analyzes the patient's eating habits and thought patterns. In this embodiment, only the answers to questions related to type analysis are used for the type analysis. In type analysis, a score is calculated for each management indicator related to diet and exercise. In this embodiment, the management indicators used are "meal content," "substitute eating," "eating motivation," "regularity of eating habits," "snacks," "nutritional balance," "exercise," and "eating habits."

[0071] Therefore, the user's initial state regarding management metrics (initial score value) is generated solely from the results of their answers to questions about management metrics. Furthermore, type analysis can also utilize records such as "daily reflections." Behaviors recorded in "daily reflections" include, for example, "self-control overeating," "reducing snacking," "reducing fried foods," and "exercise." It is also possible to include the contents of a diary recorded in "daily reflections." When using records of "daily reflections" for type analysis, the score may be calculated using only the "daily reflections" records, or it may be calculated using both the "daily reflections" records and the answers to questions related to management indicators.

[0072] For example, pre-defined calculation formulas or evaluation formulas are used to calculate the score for each management indicator. For example, a scoring method is employed in which points such as "0" to "4" are assigned to each answer, and the total score of the target answers is used as the score. However, the points for answers may differ depending on the question. For example, five answers to one question may be assigned "0", "1", "2", "3", and "4", but five answers to another question may be assigned "0", "2", "4", "6", and "8".

[0073] In addition, to equalize the total scores across different management indicators, the total scores for each indicator may be normalized. For example, if the total score for a certain management indicator is 150 points and the maximum score for that indicator is 200 points, a score of 75 points may be used, with 100 points being the maximum. Alternatively, the numerical value assigned to the interval to which the calculated total score for the management indicator belongs may be output as the score. For example, if the maximum score is 100 points, and the score intervals are divided into 10-point increments and each interval is assigned a numerical value from "0" to "10", then a score of "0" may be assigned to 0-9 points, a score of "1" to 10-19 points, and so on, with a score of "9" to 90-99 points and a score of "10" to 100 points.

[0074] Furthermore, AI technology may be used to calculate scores for each management indicator. For example, a pre-trained model using machine learning or deep learning could be used to input patient responses or "daily reflection" records and output corresponding scores. Note that a pre-trained model may be prepared for each management metric, or a pre-trained model may be prepared that outputs scores for multiple management metrics at once. In any case, when patient responses and records of "daily reflections" are fed into a trained model, a score corresponding to the management indicator is output.

[0075] Once the score for each management indicator is determined, the patient app 130 displays each score in a radar chart. The radar chart in this embodiment is an example of a graph, where multiple management indicators are represented as vertices of a polygon. Figure 6 illustrates an example of a display screen showing the results of type analysis. The "Type Analysis" screen 220 shown in Figure 6 displays the analysis results field 221, the "Proceed to Next Learning" button 222, and the "Return to Home" button 223.

[0076] When the "Proceed to next lesson" button 222 is pressed, the user proceeds to the next lesson. Specifically, they proceed to the final day screen of "Step 1". When the "Return to Home" button 223 is pressed, the user returns to the home screen 200 (see Figure 4). However, the contents of the weight field 201A (see Figure 4), such as "Current Date" and "Current Weight," will be the values ​​at the time of display.

[0077] The display (or presentation) of the analysis results column 221 shown in Figure 6 is achieved through a function that presents the user's status regarding management indicators. The analysis results section 221 shown in Figure 6 consists of a radar chart section 221A and an advice section 221B. In the radar chart section 221A shown in Figure 6, an octagonal figure (i.e., a radar chart) representing the score associated with each management indicator is drawn against the backdrop of a regular octagon with the eight aforementioned management indicators as its vertices (or superimposed on the regular octagon).

[0078] In Figure 6, the center of the regular octagon corresponds to a score of "0," and the outermost perimeter corresponds to the maximum score. On the other hand, the octagonal shape represented by color represents the user's state during type analysis (in this case, the initial state). The radar chart representing the analysis results is drawn by connecting the scores of adjacent management indicators with line segments. In this embodiment, the arrangement of the eight control indicators corresponding to each vertex of the regular octagon is predetermined.

[0079] The eight control indicators corresponding to each vertex of the regular octagon may be arranged in order of the magnitude of their corresponding scores, clockwise from the reference position (for example, the position of "Meal Content" in Figure 6). Arranging the control indicators in order of the magnitude of their scores reduces the unevenness of the figure representing the analysis results, making it easier to compare the magnitudes of the scores. Displaying messages in radar chart section 221A is optional. In Figure 6, the message "Thank you for your hard work on the diagnosis!" is displayed. The radar chart displayed in step 105 represents the results of the initial type analysis of the user. In this sense, the radar chart displayed in step 105 represents the user's initial state in relation to the management metrics.

[0080] In the analysis results section 221B shown in Figure 6, advice is displayed according to the results of the type analysis. In Figure 6, after the message "Good job!", it says, "Items with low values ​​in the graph are items that should be improved in particular. In 'Step 2', let's prioritize improving those lifestyle habits!" In the advice, "low number" means a small score. In other words, "low number" means being close to the center of the regular octagon. On the other hand, "high number" means a large score. In other words, "high number" means being close to the perimeter of the regular octagon.

[0081] Advice section 221B is displayed to help patients understand the results of their type analysis. In Figure 6, the values ​​for "Dietary Content" and "Nutritional Balance" are lower compared to other management indicators. Conversely, the values ​​for "Eating Habits" and "Regularity of Eating Habits" are higher compared to other management indicators. The shape and area of ​​the radar chart visualize the user's lifestyle habits. Therefore, compared to verbal explanations, it becomes easier for users to understand their own lifestyle habits. Furthermore, as will be discussed later, changes in the shape and area of ​​the radar chart make it easier for users to track changes in their lifestyle habits.

[0082] <Step 106> Once the radar chart showing the results of the type analysis is finished, the patient app 130 accepts the setting of behavioral goals to be addressed in "Step 2". In this embodiment, step 106 is executed when the "Proceed to next lesson" button 222 (see Figure 6) is pressed. In this embodiment, step 106 is the final day of "step 1," that is, the 12th day since the patient started using the patient app 130. Figure 7 illustrates an example of the display of the action goal setting screen 230 in "Step 1". The action goal setting screen 230 shown in Figure 7 is displayed after the "Set Goal" button is pressed on the final day screen (not shown).

[0083] The action goal setting screen 230 shown in Figure 7 displays the analysis results section 231 and the related content section 232. The analysis results section 231 shown in Figure 7 consists of a screen switching button 231A, a radar chart section 231B, an explanation section 231C, and recommended indicators 231D. The screen switching button 231A consists of two tabs: "Not Implemented" and "Implemented." The "Not Implemented" tab is used to set new action goals, while the "Implemented" tab is used to view the setting screen for action goals that have been implemented in the past. In Figure 7, the "Not Implemented" tab is selected.

[0084] Radar chart section 231B displays the same radar chart and legend as radar chart section 221A (see Figure 6). The legend explains the display colors (or line types) that represent the radar chart at the start of treatment and the display colors (or line types) that represent the radar chart at the present time. In the case of Figure 7, since no type analysis was performed before the present time, only the radar chart corresponding to the present time is displayed. The explanation field 231C displays instructions for the user. In the explanation field 231C shown in Figure 7, the message "Choose one goal to work towards starting tomorrow" is displayed.

[0085] The recommended indicator 231D displays the indicator recommended for the behavioral goal. In this embodiment, the recommended indicator 231D displays one management indicator that the user finds difficult. In Figure 7, "nutritional balance," which has the lowest score among the eight management indicators, is recommended. In addition, one recommended indicator may be determined according to predetermined criteria. These predetermined criteria include priority relationships among multiple indicators. For example, if "nutritional balance" and "dietary content" are two recommended indicators based on scores, "nutritional balance" will be prioritized according to the predetermined priority relationships.

[0086] It is also possible to display multiple indicators in Recommendation Indicator 231D. In the example in Figure 7, two indicators, "nutritional balance" and "dietary content," could be recommended. In this case, the related content displayed in the related content section 232 may be switched depending on the selection of the two indicators. Alternatively, the related content corresponding to each of the two indicators may be displayed side by side.

[0087] The related content section 232 displays content related to the recommended indicator 231D. In Figure 7, the related content section 232 displays two related content items, 232A and 232B. In Figure 7, related content 232A is "Be mindful of PFC balance," and related content 232B is "Increase your fiber intake." "PFC" is an acronym for Protein, Fat, and Carbohydrate. The related content displayed in the related content section 232 can be one item or three or more. Incidentally, the third related content item related to "nutritional balance" is "Don't consume too many carbohydrates."

[0088] The related content displayed in the related content section 232 has a sequence of execution requirements. In the case of Figure 7, this means that you cannot select related content 232B until related content 232A is completed. Therefore, in Figure 7, related content 232A is displayed in an active state, while related content 232B is grayed out. This is because the learning and actions related to "being mindful of PFC balance" have not been completed. The completion of related learning and actions can be confirmed by the record of their implementation.

[0089] Related content 232A and related content 232B include three face icons. These face icons represent supporters who assist with the related content. Here, supporters are people who offer advice on episodes related to the related content (for example, cooking methods or points to keep in mind) and tips for achieving success. Tapping each face icon will display the advice of the person who tapped it.

[0090] In Figure 7, the combination of face icons displayed in related content 232A is different from the combination of face icons displayed in related content 232B. This is because the combination of supporters is different. In this embodiment, "being mindful of the PFC balance" under "nutritional balance" is set as the behavioral goal to be addressed in "Step 2".

[0091] <Step 107> The patient terminal 10 (i.e., the patient app 130) sets the current step of the treatment plan to "Step 2". "Step 2" corresponds to the "Implementation of Behavioral Goals" step mentioned above. <Step 108> The patient terminal 10 (i.e., the patient app 130) displays the behavioral goals set in "Step 2" on its home screen to support daily practice. As mentioned above, the unit practice period for "Step 2" is 8 days. Day 1 of the unit practice period is a day for learning the behavioral objectives, and days 2 through 8 are days for putting the behavioral objectives into practice.

[0092] In this embodiment, on the first day of the unit practice period, learning content for the behavioral goal (for example, "Be mindful of the PFC balance") is displayed. From the second day onward, a screen for practicing and recording the behavioral goal is displayed. The record made here is recorded as a "daily reflection." In this embodiment, if the patient reports "Done" or "Mostly done" in the "Daily Review" for five or more days out of seven, the patient app 130 considers the behavioral goal to be completed (or achieved). On the other hand, if the patient reports "completed" or "mostly completed" in the "daily review" for fewer than 5 out of 7 days, the patient app 130 considers the behavioral goal to be incomplete (or not achieved). Furthermore, the information used to determine whether the behavioral objectives have been completed (or achieved) may include the content and accuracy rate of answers to questions given during the unit practice period.

[0093] On the final day of a single practice period (after entering the "daily reflection" information), a screen for reviewing behavioral goals is displayed. In other words, the behavioral goal review screen is displayed every 8 days. To put it another way, the patient app 130 periodically displays the progress using a radar chart. On the behavioral goal review screen, the behavioral goals for the next practice period are also set. Figure 8 illustrates an example of the display of the action goal setting screen 230 in "Step 2". In Figure 8, corresponding parts with reference numerals are shown.

[0094] In the case of Figure 8, a new action goal is being set. Therefore, the "Not Implemented" tab of the screen switching button 231A is selected. There are two differences between the behavior goal setting screen 230 shown in Figure 8 and the behavior goal setting screen 230 shown in Figure 7. The first difference is that two radar charts are shown in the radar chart section 231B. In this embodiment, one is the radar chart for "the start of treatment," and the other is the radar chart for "the present."

[0095] In Figure 8, the shape of the "current" radar chart is larger than the "initial treatment" radar chart for the management indicator "nutritional balance." This is because the score for "nutritional balance" during the current unit of practice is higher than the score for "nutritional balance" at the "initial treatment." In other words, the user has completed (or achieved) the behavioral goals for the current unit of practice. Note that in Figure 8, the scores for the other management indicators are the same as the scores at the "initial treatment." However, the actions taken during each unit of practice are not limited to behavioral goals. Therefore, if the score corresponding to another management indicator is higher than the score at the "initial treatment," the radar chart will be larger in the corresponding management indicator section.

[0096] In this embodiment, the patient app 130 displays the "current" radar chart in a way that it is larger than the radar chart at the "start of treatment" or the radar charts for previous treatment periods. For example, even if the current management indicator score based on the overall evaluation is lower than the score at the "start of treatment," the management indicator score for the current treatment period is represented with the same value as the score at the "start of treatment." In other words, the patient app 130 presents the user's status regarding management indicators in a format that does not decrease from the previous value. By adopting this presentation method, the patient app 130 can prevent a decline in the motivation of users working to improve their management indicators.

[0097] The second difference lies in the content of the two related content items displayed in related content section 232. In Figure 8, related content 232A is "Increase your fiber intake," and related content 232B is "Don't consume too many carbohydrates." Since the related content "Be mindful of PFC balance" has been completed, the related content displayed in related content section 232 has moved up one position. In Figure 8, the actionable item "Increase your fiber intake" is displayed as active, while "Don't consume too many carbohydrates" is grayed out.

[0098] <Step 109> Once the "Step 2" implementation period (approximately 6 months) is complete, the patient terminal 10 (i.e., the patient app 130) sets the current step of the treatment plan to "Step 3". "Step 3" corresponds to the "habit formation of behavior" step mentioned earlier. <Step 110> The patient terminal 10 (i.e., the patient application 130) determines the execution mode to either normal mode or difficulty-overcoming mode. Patient App 130 is a program designed to support users in improving their lifestyle habits. However, in reality, at the end of "Step 2," some users will have shown sufficient behavioral change (their lifestyle habits can be considered to have improved), while others will have shown insufficient behavioral change (their lifestyle habits have not improved).

[0099] In this embodiment, whether or not "behavioral change is sufficient" is determined by the relationship between the current weight and the target weight, and the mode to be applied is determined. Specifically, the normal mode is applied to users whose current weight is less than the target weight, and the weakness-overcoming mode is applied to users whose current weight is above the target weight. The normal mode is designed to support the maintenance or continuation of improved lifestyle habits. Therefore, the patient app 130's homepage displays information to support the recording of daily measurements and activities. In the "Overcoming Weaknesses" mode, the processing steps from "Step 2" continue. Specifically, progress is displayed in a radar chart for each practice period, and the user is presented with recommended actions for the management indicators they struggle with.

[0100] In this embodiment, a change in mode is determined every two weeks. For example, if the measured value exceeds the target value even in normal mode, the patient app 130 will change the next unit practice period to the difficulty-overcoming mode. For example, if the measurement reaches the target value even in the "overcoming weaknesses" mode, the patient app 130 will change the next unit practice period to normal mode. The change from "overcoming weaknesses" mode to normal mode prioritizes achieving the target value over the achievement status of the behavior.

[0101] <Step 111> The patient terminal 10 (i.e., the patient app 130) performs a type analysis after a predetermined number of days have elapsed (for example, on day 340) and displays the analysis results in a radar chart. Needless to say, 340 days is just one example. The predetermined number of days is set for each disease. Also, even for the same disease, different patient apps 130 may use different numbers of days. As mentioned above, the type analysis involves questions about eating habits and ways of thinking. In this embodiment, the content of the questions is the same as in "Step 1".

[0102] Figure 9 illustrates an example of the display screen for the results of the second type analysis. In Figure 9, corresponding parts with those in Figure 6 are indicated with corresponding labels. There are two differences between the "Type Analysis" screen 220 shown in Figure 9 and the "Type Analysis" screen 220 shown in Figure 6. The first difference is that in radar chart section 221A, in addition to the radar chart for "at the start of treatment," a radar chart for "the present" is displayed.

[0103] Therefore, the legend, as in Figure 8, explains the display colors (or line types) that represent the radar chart at the start of treatment and the display colors (or line types) that represent the radar chart at the present time. In Figure 9, the "current" radar chart is larger than the "at the start of treatment" radar chart, but many management indicators remain unmet. For example, the scores for "eating habits" and "exercise" are at their highest, but the scores for the other six management indicators are not. This indicates that behavioral improvements are still needed for these six management indicators.

[0104] In the advice section 221B, following the message "Great job!", it says, "How were the results this time? For the items that have improved compared to last time, please continue to improve them!", and "If there are any items that have declined, please reconfirm the action goals for those items and try to live your life with those goals in mind." Here, "items" refers to management indicators. In this embodiment, the type analysis in "Step 1" and "Step 3" is based on the same questions. Therefore, the wording allows for the possibility that the scores for each management indicator may be lower than those at the "start of treatment."

[0105] The second difference is that the "Type Analysis" screen 220 shown in Figure 9 does not display the "Proceed to Next Learning" button 222 (see Figure 6). Incidentally, the "Proceed to Next Learning" button 222 is used to set the action goal for "Step 2". In "Step 3," either the normal mode or the mode for overcoming weaknesses is in operation, so it depends on the current mode of operation. However, if the second type analysis is performed on the final day of "Step 3," setting new behavioral goals is not planned.

[0106] <Summary> The patient application 130 envisioned in this embodiment presents the patient with the results of type analysis and the scores of management indicators at each point in time as a radar chart. A radar chart is a polygonal figure with the scores of management indicators as its vertices. Therefore, patients can easily see their own eating habits and ways of thinking through the shape of the radar chart. Furthermore, because radar charts make it easy to identify management indicators with high and low scores, patients can easily determine which management indicators they should prioritize addressing.

[0107] Furthermore, the patient app 130 uses scores for each management indicator, obtained through analysis of eating habits and ways of thinking, as initial values ​​for the radar chart. Therefore, the radar chart can be displayed even at an early stage of patient app 130 usage. As a result, it becomes easier for patients to confirm the behavioral goals they should pursue. Furthermore, in this embodiment, the patient app 130 displays the radar chart at the start of treatment and the radar chart at the present time overlaid on the same coordinates, making it easy to check the changes in the score for each management indicator.

[0108] In this case, the patient app 130 displays a radar chart of the "current" score in a format where the "current" score does not decrease compared to the previous score of the corresponding management indicator. By ensuring that the "current" score does not decrease compared to the "initial treatment" score, it is possible to help maintain or improve the user's motivation to use the patient app 130. Through these functions, the patient app 130 can support users' efforts to treat or prevent diseases.

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

[0110] (2) The processing in the embodiments described above is performed on any computer. Any computer may be implemented as a processor as hardware, a program as software, or a combination thereof. Any computer may be a general-purpose computer, a computer for a specific purpose, a workstation, or any other system capable of performing each processing.

[0111] The processor is configured to perform various processes in cooperation with the program. The processor can function as each unit or each means in this embodiment. The execution order of the processes performed by the processor is not limited to the order described in this embodiment and can be changed as needed.

[0112] A processor can be configured with one or more hardware components. The types of hardware that make up a processor are not limited to any particular type. For example, a processor may be a CPU (=Central Processing Unit), an MPU (=Micro Processing Unit), a programmable logic device such as an FPGA (=Field Programmable Gate Array), a dedicated circuit for performing specific processing such as an ASIC (=Application Specific Integrated Circuit), a GPU (=Graphic Processing Unit), or hardware such as an NPU (=Neural Processing Unit).

[0113] A processor can be configured not only with a combination of multiple hardware components of the same type, but also with a combination of multiple hardware components of different types. When multiple hardware components are configured to perform one or more processes of a given processor, these components may reside in physically separate devices or in the same device. Hardware is composed of electrical circuits and other components, such as semiconductor elements.

[0114] In any of the embodiments, the execution order of each process by the processor is not limited to the order described in each embodiment, and can be changed as necessary. The program can be firmware, or it can be software such as microcode. The program may be, for example, a group of program modules. Each function constituting the group of program modules may be implemented by a processor configured to execute each function.

[0115] The program in each embodiment may be program code or multiple code segments stored in one or more non-temporary computer-readable media (e.g., semiconductor memory, magnetic or optical storage media, or other storage). The program may be divided and stored on multiple non-temporary computer-readable media located on devices that are physically separated from each other.

[0116] Program code and multiple code segments can be represented by any combination of procedures, functions, subprograms, routines, subroutines, modules, software packages, classes, instructions, data structures, and program statements. Program code or multiple code segments may be connected to other code segments or hardware circuits by sending and receiving information, data, arguments, parameters, or memory contents.

[0117] (3) In the above-described embodiment, a radar chart was presented using a score that indicates the user's status with respect to management indicators, but other presentation methods may be adopted. For example, one could employ a method that presents scores in correspondence with management indicators. This type of presentation could use, for instance, a table. Alternatively, methods may be employed to present the scores using graphs other than radar charts.

[0118] Figure 10 illustrates another example of the display of the action goal setting screen 230 in "Step 2". Figure 10 is denoted with corresponding reference numerals for parts that correspond to those in Figure 8. The difference between the behavioral goal setting screen 230 shown in Figure 10 and the behavioral goal setting screen 230 shown in Figure 8 lies in the method of displaying the score in the analysis results section 231. In the behavioral goal setting screen 230 shown in Figure 10, the bar graph section 231E is displayed in the position of the radar chart section 231B.

[0119] In the bar graph section 231E shown in Figure 10, eight management indicators are arranged vertically, and corresponding to each, a bar graph showing the score at the start of treatment and a bar graph showing the current score are displayed in two rows. In Figure 10, the bar graph showing the current score is in the upper row, and the bar graph showing the score at the start of treatment is in the lower row. In the bar graph shown in Figure 10, the minimum score is "0" and the maximum score is "100". The length of the bar represents the magnitude of the score. In Figure 10, it can be seen that the "current" score for all management indicators is higher than the "initial treatment" score.

[0120] Furthermore, when displaying scores using bar graphs, the initial score will use the results of the type analysis in "Step 1," and when displaying scores for each unit of practice period in "Step 2," etc., the current score will be presented in a format that does not decrease from the "start of treatment" score. In addition, other graphs used to present the patient's condition in relation to management indicators may include, for example, line graphs that show the change in score over time, and pictograms (graphs that show differences in score by the size of the images). This display method, using bar graphs and the like, can also be used to display scores in other embodiments described later.

[0121] (4) In the embodiments described above, the radar chart at the start of treatment and the radar chart at the present time are presented in a comparable manner. However, in place of the radar chart at the start of treatment, or in addition to the radar chart at the start of treatment, other radar charts from the previous time point may be presented. For example, a radar chart for the "previous unit practice period" and a radar chart for the "present" period may be presented in a comparable manner. Alternatively, a radar chart for the "start of treatment," a radar chart for the "previous unit practice period," and a radar chart for the "present" period may be presented in a comparable manner.

[0122] By the way, the change in scores between the radar chart for the "previous unit practice period" and the radar chart for the "present" is small, so it's possible that you won't really notice the change in your scores. Therefore, a radar chart showing the score at an approximate midpoint between "the start of treatment" and "the present" may be presented.

[0123] Additionally, one or more radar charts showing the score for the corresponding unit practice period may be added to the display of the "at the start of treatment" radar chart and the "current" radar chart at a predetermined rate of once every four times. Additionally, radar charts may be displayed for a unit of practice period in which a predetermined change in the score of any of the management indicators is observed between the radar charts displayed on the screen (at least the radar chart at the start of treatment and the radar chart for the present).

[0124] (5) In the above-described embodiment, the patient app 130 (see Figure 1), which is used to record measurements and "daily reflections," displays the scores of the patient's management indicators using the patient app 130 in a radar chart. In other words, the description describes a case in which the recording of measurements and other data and the display of radar charts based on that data are completed within the patient app 130. However, a function to display the patient's condition in relation to management indicators using a radar chart may be provided on the server that manages the patient data.

[0125] Figure 11 is a diagram illustrating an information processing system 100 consisting of a management server 20 that manages patient data 236 and a patient terminal 10. Figure 11 is denoted by reference numerals corresponding to the parts that correspond to those in Figure 1. The patient application 130A on the patient terminal 10 in Figure 11 differs from the embodiment in that it does not have functions for type analysis or analysis of the achievement status of behavioral goals for each unit practice period. However, the patient application 130A has a function to obtain analysis results from the management server 20 and display the "type analysis" screen 220 (see Figures 6 and 9) and the behavioral goal setting screen 230 (see Figures 7 and 8).

[0126] The patient terminal 10 and the management server 20 are connected via a network to enable communication. For example, the network could include a LAN, the internet, or a mobile communication system (4G, 5G, etc.). The management server 20 is a PDT server that manages patient data 236. The management server 20 is an example of an information processing device. If the management server 20 is a PDT server, it is assumed that the PDT server runs the physician application that corresponds to the patient application 130A. However, the management server 20 may also be a PDT platform that manages prescriptions for the patient app 130A, or it may be a server that provides services such as type analysis and analysis of the achievement status of behavioral goals for each unit practice period.

[0127] The management server 20 includes a processor 21, semiconductor memory 22, auxiliary storage device 23, and a communication interface 24. Each device is connected via a bus or other signal lines. The processor 21 is a device that realizes various functions through the execution of a program. The processor 21 may be composed of multiple CPU cores. In that case, the processor 21 executes the program through the cooperation of the multiple CPU cores. The semiconductor memory 22 stores UEFI and other information. The semiconductor memory 22 is also used as an execution area for programs. The processor 21 and the semiconductor memory 22 function as a computer.

[0128] The auxiliary storage device 23 consists of, for example, a hard disk drive or semiconductor storage. The auxiliary storage device 23 stores the operating system and other programs. Other programs include the information presentation application 235. The information presentation application 235 is a program that provides the patient terminal 10 with the results of type analysis and analysis of the achievement status of behavioral goals for each unit practice period, as well as radar charts corresponding to these results. Information presentation app 235 is an example of a program that implements a function to present the user's status regarding management indicators based on health data recorded by users who are working to treat or prevent diseases.

[0129] In addition, the auxiliary storage device 23 also stores patient data 236 recorded through the patient application 130A. The communication interface 24 is an interface for communicating with external terminals such as PDT platforms via a network. The communication interface 24 supports Ethernet®, Wi-Fi®, mobile communication systems, and other communication standards.

[0130] Figure 12 is a flowchart illustrating an example of the processing operation of the information presentation application 235 (see Figure 11). In Figure 12, corresponding parts with reference numerals are shown. In the case of Figure 12, only steps 105A, 108A, and 111A related to the presentation of the radar chart are executed on the management server 20, while other processing operations are executed on the patient terminal 10. The patient terminal 10 uploads patient application data 131 to the management server 20 at predetermined intervals. This upload occurs, for example, when new data is recorded or data is updated while the patient application 130 is logged into the management server 20. In addition, patient application data is also uploaded when the patient logs into the management server 20.

[0131] Incidentally, in step 105A, the management server 20 performs type analysis after a predetermined number of days have elapsed and provides the patient terminal 10 with the analysis results in the form of a radar chart. Furthermore, in step 108A, the management server 20 periodically provides the patient terminal 10 with a progress chart. Furthermore, in step 111A, the management server 20 performs a type analysis after a predetermined number of days have elapsed and provides the patient terminal 10 with the analysis results in the form of a radar chart.

[0132] In the case of the explanation in Figure 12, the management server 20 provides the patient terminal 10 with the results of the analysis of the patient's eating habits and way of thinking, etc. However, it may also be provided to a terminal operated by a doctor or other medical professional who is examining a user of the patient application. In other words, the management server 20 may present the patient's terminal as medical support information, such as a list of scores or radar charts related to management indicators for each unit implementation period, as well as the results of the analysis of the patient's eating habits and way of thinking. Doctors and other healthcare professionals can use on-screen scores, radar charts, and other visual aids to provide medical services to patients.

[0133] In the explanation in Figure 12, the management server 20 provides the patient terminal 10 with the analysis results in a radar chart, but it may also perform all the functions of the patient application 130. In this case, the patient uses the patient terminal 10, such as a smartphone, as an input / output device and utilizes the patient application 130 service described as an embodiment as a cloud service.

[0134] (6) As mentioned above, the content of the data recorded in the patient app data 131 (see Figure 2) will vary depending on the disease to which the patient app 130 (see Figure 1) corresponds. However, if the treatment of the disease involves taking medication, the patient app 130 may record information regarding the taking of prescribed medications. The medication record may also include records of taking over-the-counter medications, etc.

[0135] (7) In the above-described embodiment, the "normal mode" and the "weakness overcoming mode" in "Step 3" are switched depending on the relationship between the current weight and the target weight. However, mode switching may also be performed based on whether the scores for one or more management indicators managed by type analysis, etc., meet the criteria (for example, whether they exceed the threshold used to determine mode switching).

[0136] (8) In the above-described embodiment, the decision to switch between "normal mode" and "weakness overcoming mode" in "Step 3" is made every two weeks, but it may also be done when a predetermined number of unit practice periods (for example, 2 times) have been completed.

[0137] (9) In the embodiments described above, a patient application for NASH was explained. However, the patient app can be a patient app for other diseases. Incidentally, these other diseases can be lifestyle-related diseases or non-lifestyle-related diseases. Lifestyle-related diseases include, for example, hypertension, alcoholism, dyslipidemia, chronic heart failure, hyperuricemia, diabetes, kidney disease, nicotine addiction, chronic bronchitis, cancer, periodontal disease, attention deficit hyperactivity disorder, depression, tinnitus, delayed grief disorder, opioid-induced constipation, post-mastectomy pain syndrome, nephrotic syndrome, and insomnia. Examples of non-lifestyle-related diseases include headaches and irritable bowel syndrome.

[0138] (10) In the embodiments described above, the case in which the user using the application for recording health data is a patient was described. That is, a patient terminal was assumed to be a terminal on which a program that presents the user's status regarding management indicators from health data recorded by a user who is working to treat or prevent a disease is installed. However, the app that users who are working to treat or prevent diseases use to record health-related data can be any user app, including so-called healthcare apps.

[0139] In this case, any user application will have a function to display the user's status regarding management metrics. Any user application could be a diary application, an image application, or an audio application. Furthermore, when managing user data for any user application on a server, a function may be provided on the server side to display the user's status related to management indicators, as explained using Figures 11 and 12.

[0140] <Summary> An example of the disclosure described in the above-mentioned embodiment is shown below. (((1))) A program that enables a computer to display the user's status regarding management indicators based on health data recorded by the user who is working to treat or prevent a disease. This program can provide psychological support to users in their efforts to treat or prevent diseases.

[0141] (((2))) The function to be presented is the program described in (((1))) which presents the user's status regarding management indicators in a graph. This program makes it easier to check the user's status regarding management metrics.

[0142] (((3))) The function to be presented is the program described in (((2))) which presents the user's status using a radar chart with multiple management indicators as the vertices of a polygon. This program makes it easy to monitor changes in user status related to management metrics.

[0143] ((((4))) The function to be presented is a program described in one of (((1))) to (((3))) that generates the user's initial state regarding management metrics based on the results of answers to questions about management metrics. This program allows for the presentation of the user's status regarding management metrics, even at an early stage when the user has recorded limited data.

[0144] (((5))) The function to be presented is a program described in one of the following (((1))) to (((4))) that presents the user's status regarding management indicators in a format that does not decrease from the previous value. This program can help maintain or improve user motivation.

[0145] (((6))) The function to be presented is a program described in any one of (((1))) to (((5))) that displays the patient's status related to management indicators on the terminal operated by the user. This program allows us to provide a service that displays the user's status regarding management metrics.

[0146] (((7))) A program described in any one of (((1))) to (((6))) that, as a function of the program used by the user to record data, presents the user's status regarding management indicators. This program makes it possible to check the user's status regarding management indicators regardless of their internet connection.

[0147] (((8))) An information provision method in which a computer performs a process to present the user's status regarding management indicators based on health data recorded by a user who is working to treat or prevent a disease. This method of providing information can psychologically support users' efforts toward treating or preventing diseases.

[0148] (((9))) An information processing device having a processor, the processor presents the user's status regarding management indicators from health data recorded by the user who is working to treat or prevent a disease. This information processing device can provide psychological support to users' efforts toward treating or preventing diseases. [Explanation of symbols]

[0149] 10…Patient terminal, 11, 21…Processor, 12, 22…Semiconductor memory, 13, 23…Auxiliary storage device, 14…Input interface, 15…Input device, 16…Output interface F, 17…Output device, 18, 24…Communication interface, 20…Management server F, 100…Information processing system, 130, 130A…Patient application, 131…Patient application data, 235…Information presentation application, 236…Patient data

Claims

1. On the computer, A function that presents the user's status regarding management indicators based on health data recorded by users who are working to treat or prevent diseases. A program to achieve this.

2. The aforementioned function presents the user's status regarding management indicators using graphs. The program according to claim 1.

3. The aforementioned function presents the user's status using a radar chart with multiple management indicators as the vertices of a polygon. The program according to claim 2.

4. The aforementioned function generates the user's initial state regarding management metrics based on the results of answers to questions related to management metrics. The program according to claim 1.

5. The aforementioned function presents the user's status regarding management indicators in a format that does not decrease from the previous value. The program according to claim 1.

6. The aforementioned function displays the patient's status related to management indicators on the terminal operated by the user. The program according to claim 1.

7. As a function of the program that the user uses to record the data, it presents the user's status regarding management indicators. The program according to claim 1.

8. Computers A process that presents the user's status regarding management indicators based on health data recorded by users who are working to treat or prevent a disease. A method for providing information to carry out the task.

9. It has a processor, The aforementioned processor, This system presents the user's status regarding management indicators based on health data recorded by users who are working to treat or prevent a disease. Information processing device.

Images