Program, information processing device, and information provision method

Abstract

We provide a system that can offer personalized support to each user based on their progress towards achieving their goals. [Solution] A program is used in the computer to implement a function that controls the support provided in management mode according to the progress of the user working towards achieving their goals in changing their behavior.

Description

Technical Field

[0005] , , , , ,

[0004] , , , , , , , , , ,

[0003] , , , ,

[0006] ,

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

Background Art

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

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Some user apps support the improvement of a user's lifestyle habits by dividing it into multiple stages. The multiple stages include, for example, a stage of acquiring knowledge about diseases and a stage of supporting the habituation of actions through practice. Each stage is designed on the premise of an average user who uses the user app. However, the improvement of lifestyle habits does not always progress as expected. For this reason, it may happen that a support service for users whose improvement of lifestyle habits is progressing is provided to users whose progress of improving lifestyle habits is slow.

[0005] The present disclosure provides a mechanism capable of providing support according to the progress of goal achievement for each user.

Means for Solving the Problems

[0006] One of the disclosures is a program that enables a computer to control the level of support provided in management mode based on the user's progress in achieving their goals as they work towards behavioral change. The function that controls the support provided in management mode may also control the switching between a first mode that supports the achievement of goals and a second mode that supports the continuation of a state where goals have been achieved. In this case, it is desirable to use Mode 1 for users who have not achieved their goals and Mode 2 for users who have achieved their goals. Furthermore, a decision may be made at a predetermined timing after the switch whether to continue in the currently used mode or switch to another mode. Preferably, this predetermined timing is one or more of the following: the timing when the user's attributes change, the timing when a medical professional instructs a switch, and the timing when a predetermined period has elapsed since the start of the first or second mode. Furthermore, while support is being provided in Mode 1, the user may be informed that at least Mode 1 support is being provided. Furthermore, when providing support using Mode 1, one or more behavioral goals may be presented, while when providing support using Mode 2, it is not necessary to present one or more behavioral goals. The behavioral goals here may be indicators among several indicators whose scores are lower than the standard, or indicators whose scores are lower than other indicators. Furthermore, support in management mode may be initiated after the mode that supports the habituation of behavior has ended. One of the disclosures is an information provision method in which a computer performs processing to control the support provided in management mode according to the progress of a user working towards achieving their goals in changing their behavior. One of the disclosures is an information processing device having a processor, which controls the support provided in management mode according to the progress of the user in achieving their goals while working on behavioral change. [Effects of the Invention]

[0007] According to one form of this disclosure, support can be provided to each user according to their progress in achieving their goals. [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 the internal processing performed in step 110. [Figure 10] This diagram illustrates an example of the home screen in "Normal Mode". [Figure 11] This diagram illustrates an example of the learning screen displayed on the first day of the unit practice period. [Figure 12] This diagram illustrates an example of the home screen in "Overcoming Weaknesses Mode." [Figure 13] This diagram illustrates an example of the display of the behavioral goal setting screen in "Step 3: Overcoming Weaknesses Mode". [Figure 14] This diagram illustrates an example of how the relearning screen is displayed. [Figure 15] This diagram illustrates an example of the home screen that appears after setting behavioral goals in "Overcoming Weaknesses Mode." [Figure 16] This diagram illustrates an example of a change notification screen used to prompt users to switch from "Overcoming Weaknesses Mode" to "Normal Mode." [Figure 17] This diagram illustrates an example of the display screen for the results of the second type analysis. [Figure 18] This is a diagram for explaining an information processing system composed of a management server for managing patient data and a patient terminal. [Figure 19] This is a flowchart for explaining an example of the processing operation of a mode management application.

Embodiments for Carrying Out the Invention

[0009] <Terms> First, terms used in the embodiments described below will be explained. The "program for promoting behavioral change" refers to a program provided with the intention of promoting a change in human behavior. However, this program does not guarantee a change in human behavior. Whether a person's behavior actually changes or not depends on the user who uses the program. Therefore, the program for promoting behavioral change can also be said to be a program for supporting behavioral change.

[0010] This type of program includes a program positioned for medical devices and a program positioned for non-medical devices. The program positioned for medical devices is an example of a program that requires a prescription, and the program positioned for non-medical devices is an example of a program that does not require a prescription. Note that the program positioned for non-medical devices is not limited to the program for promoting behavioral change, and may also be a program having a function of recording health-related data. The program for promoting behavioral change or the program having a function of recording health-related data (hereinafter also referred to as "program for promoting behavioral change, etc.") includes, in addition to the program downloadable from the app store, programs used by private businesses, public organizations, etc. for the health management of employees, etc.

[0011] The program positioned for non-medical devices also includes programs used in medical institutions. When distinguishing the program executed on the terminal operated by the user (i.e., the user terminal) among the above-described programs from the programs used in medical institutions, the program targeted may be referred to as a user app.

[0012] The "purpose of the app" refers to the effect that should be achieved by using programs that encourage behavioral change. The purpose of the app varies depending on the disease to which the program that encourages behavioral change corresponds. For example, the purpose of the app may include improving lifestyle habits, maintaining improved lifestyle habits, and maintaining improved numerical values. "App goals" refer to the objectives that are aimed to be achieved through the use of programs and other means that promote behavioral change. Goals are defined from the perspective of achieving the objective. Goals are classified into qualitative and quantitative indicators. Furthermore, goals are classified into indicators defined by measured values ​​or other numerical values ​​and indicators defined by the content of actions. For example, goals include improvement or maintenance of habits, behaviors, and numerical values. App goals can also be defined by one or more sub-goals. Sub-goals are smaller-grained goals set to achieve the corresponding goal.

[0013] A "therapeutic app" refers to a program that has received approval under the Pharmaceuticals and Medical Devices Act. A therapeutic app is classified as a medical device. Therapeutic apps are approved on a disease-by-disease basis. Diseases for which approval has already been obtained include, for example, hypertension, nicotine addiction, and insomnia. Diseases for which therapeutic apps are currently under development include, for example, NASH (non-alcoholic steatohepatitis), diabetes, dyslipidemia, kidney disease, and alcoholism.

[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 NASH, body weight is recorded as a measurement. For example, if the disease is hypertension, blood pressure values ​​are recorded as measurements. Blood pressure values ​​are defined, for example, by 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 ​​would be carbon monoxide (CO) in exhaled breath and nicotine concentration in saliva. Other measurements include, for example, pulse rate, respiratory rate, 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 that shows the progress toward goals set by a doctor for each patient. It could also be information that shows the progress toward goals set by the patient themselves. Furthermore, it could be information that shows the progress toward goals presented by a patient app for each patient. Goal achievement status is an example of putting behavioral goals into practice and habituating those actions. It is also an example of progress toward achieving goals. 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 performed 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 may also include, for example, the mean, the maximum and minimum values ​​within a given period, the data distribution for each given period, and the difference from a 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 user apps (including patient apps). In other words, management indicators are examples of multiple indicators used to manage habit formation. 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 patterns." Each of these indicators is just one example of a management indicator. "Substitute eating" refers to the behavior of eating to relieve stress.

[0028] 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.

[0029] 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 may 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 may use "meal content," "substitute feeding," "eating motivation," and "regularity of eating habits" as management indicators. Management indicators are also called "behavioral goals."

[0030] In the embodiment described later, a score corresponding to each indicator is calculated based on health data recorded by the user who is working to change their behavior. The score here is an example of data obtained by processing the health data recorded by the user who is working to change their behavior. 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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."

[0035] 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.

[0036] 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.

[0037] 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.

[0038] <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 who is working to treat or prevent a disease through behavioral change. 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 user app that supports lifestyle improvement, and it has a function to control the support content in management mode according to the progress of the user in achieving their goals as they work to change their behavior.

[0039] 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.

[0040] 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.

[0041] 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 "daily review" and 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.

[0042] 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.

[0043] <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.

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

[0045] The "Reflection / Input Date & Time 131B" field records a reflection on the day's activities and the date and time of input. In the case of the NASH app, the reflection may include, for example, physical condition level, 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.

[0046] 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.

[0047] 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 performed in the order they are listed. For this reason, the "acquiring knowledge" step is also called "Step 1," the "implementing behavioral goals" step is called "Step 2," and the "habitualizing behavior" step is called "Step 3."

[0048] The "habit formation" step is also an example of a management mode for managing the habit formation of behavioral goals that were practiced in the "implementation of behavioral goals" step. The behavioral goals here may also be examples of sub-goals practiced to achieve the main goal. Behavioral goals are set for each individual behavior. In this embodiment, the "habituation of behavior" step includes both a "normal mode" and a "difficulty overcoming mode." Therefore, the current step 131C of the treatment plan also records information about the "current mode" that is currently being applied.

[0049] Treatment plan implementation history 131D records the history of learning and behaviors implemented in accordance with the treatment plan. For example, in the patient app 130 for NASH, "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.

[0050] In the case of the NASH patient app 130, "Step 3" records, for example, the practice of behaviors. "Step 3" is also called habit management. The recording of behavioral practice in "Step 3" is an example of recording behaviors related to habit formation. Behavioral objective 131E records the actions that the patient has set as goals for each unit of practice period. The goals here 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.

[0051] 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.

[0052] <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.

[0053] <Initial settings> <Step 101> Patients who have successfully installed the patient app 130 (see Figure 1) 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, successful authentication of the prescription code by a PDT platform (not shown) is required. 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.

[0054] 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.

[0055] 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 patient app 130 is logged into the PDT server and new data is recorded or data is updated. In addition, patient app data is uploaded from the patient app to the PDT server when the patient logs into the PDT server.

[0056] <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.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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. For example, in the case of the patient app 130 for NASH, a patient whose lifestyle has not been sufficiently improved is a patient who has not succeeded in losing weight to reach their target weight. Target weight is an example of a numerical target managed by the app. In this embodiment, the target weight is set by the doctor. When the doctor sets the target weight through the doctor app, it is reflected in the patient app via the PDT server on which the doctor app operates. The target weight is set to a value that is, for example, 7% less than the weight at the start of treatment. Therefore, if the weight at the start of treatment is 100 kg, the target weight is 93 kg.

[0061] In this embodiment, the relationship between the target weight and the patient's weight is referred to as the progress status. For example, if the patient's weight at the start of treatment, as measured by the patient app, is set as progress status "0," and the target weight is set as progress status "100," then the current weight is expressed as progress status "20," "50," "80," etc. In this case, weight increases from the start of treatment may be expressed as progress status "-10," etc. Also, weight decreases from the target weight may be expressed as progress status "110," etc. In this embodiment, the state in which weight loss to the target weight has been successfully achieved is referred to as "target achieved" or "achieved," and the state in which weight loss to the target weight has not been successfully achieved is referred to as "target not reached" or "not reached."

[0062] Managing progress based on whether or not the goal has been achieved (i.e., a dichotomy) is one example of how progress can be measured. In this embodiment, the "habit formation" step controls the support provided within the step according to the progress towards achieving the goal. For example, patients who have successfully lost weight to their target weight are provided with "normal mode" support, while patients who have not yet achieved their target weight are provided with "weakness overcoming mode" support.

[0063] In this embodiment, changing the screens presented to the patient or the services provided is referred to as "controlling the support content in patient mode." "Normal mode" is an example of a second mode that supports maintaining the state after achieving the goal (target weight). The "Overcoming Weaknesses Mode" is an example of the first mode, which supports the achievement of a goal (target weight). In other words, the "Overcoming Weaknesses Mode" is a mode that supports the habituation of one or more predetermined behaviors. Here, the "predetermined behaviors" are indicators (behaviors) that have not been sufficiently habitualized or indicators (behaviors) with low scores.

[0064] 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 who have achieved their goal (target weight), setting behavioral goals in the "habituation of behavior" step is optional. In other words, behavioral goals may or may not be set. Therefore, the "habituation of behavior" step for patients who have achieved their goal (target weight) also serves as a period for recording behaviors.

[0065] <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.

[0066] <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.

[0067] 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.

[0068] 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". The target weight is set by the doctor during the examination. In this embodiment, the target weight is set to a value that is 7% less than the weight at the start of treatment. Since it is the first day, the graph section is blank. The vertical axis of the graph represents weight, and the horizontal axis represents the month. In Figure 4, October, November, and December are displayed along the horizontal axis.

[0069] 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.

[0070] 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.

[0071] 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.

[0072] 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."

[0073] 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 after the completion of learning on the 7th day from the start date of using the patient app 130. The "Quiz" task displays content that tests the acquisition of knowledge about the disease. In this embodiment, the patient's answer is accepted in the form of selecting one from, for example, three options.

[0074] <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.

[0075] 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.

[0076] 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.

[0077] 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.

[0078] 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."

[0079] 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.

[0080] 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".

[0081] 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.

[0082] 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.

[0083] 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.

[0084] 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.

[0085] 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).

[0086] 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.

[0087] 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.

[0088] In the analysis results section 221 shown in Figure 6, the advice section 221B displays advice corresponding to the type analysis results. In Figure 6, following the message "Great 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.

[0089] 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.

[0090] <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).

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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."

[0096] 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.

[0097] Related content 232A and related content 232B include three face icons. These face icons represent supporters corresponding to the related content. Here, supporters represent 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 the goal. Tapping each face icon will display the advice of the person who was tapped.

[0098] 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".

[0099] <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.

[0100] 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 of the answers to questions given during the unit practice period, as well as the accuracy rate of those answers.

[0101] 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.

[0102] 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."

[0103] 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.

[0104] 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.

[0105] 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.

[0106] <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. Therefore, the support provided by "Step 3," which begins after the completion of "Step 2," starts after the completion of the mode that supports the habituation of the behavior (i.e., "Step 2").

[0107] <Step 110> The patient terminal 10 (i.e., the patient application 130) determines the management mode to either "normal mode" or "difficulty overcoming mode," and then performs management according to the determined mode. As mentioned earlier, the patient app 130 helps patients achieve their target weight through lifestyle improvements, as weight loss is effective in treating NASH.

[0108] However, even with the use of the patient app 130, the rate at which weight decreases varies from person to person. Therefore, at the end of "Step 2," some patients will have a weight below their target weight (i.e., they have achieved their target weight), while others will have a weight above their target weight (i.e., they have not achieved their target weight). Of course, it is desirable that the target weight be achieved by the end of "Step 2," but for patients who have not reached their target weight, the same support as in "Step 2" should be continued.

[0109] Therefore, in this embodiment, the patient terminal 10 (i.e., the patient application 130) determines the management mode to either a "normal mode" that supports the maintenance or continuation of improved lifestyle habits, or a "difficulty overcoming mode" that continues the processing operation of "Step 2". In other words, the patient terminal 10 (i.e., the patient application 130) determines the support content in management mode according to the progress made in achieving the goal.

[0110] Figure 9 is a diagram illustrating the internal processing performed in step 110. Figure 9 is denoted with corresponding reference numerals for parts that correspond to those in Figure 3. First, the patient terminal 10 (i.e., the patient app 130) determines whether or not the target weight has been achieved (step 110A). If the target weight has been achieved, a positive result is obtained in step 110A. In this case, the patient terminal 10 (i.e., the patient app 130) presents the home screen corresponding to "normal mode" to support the continuation of current behavioral habits (step 110B). That is, the patient terminal 10 (i.e., the patient app 130) applies "normal mode" (i.e., second mode) to patients who have achieved their goal (target weight).

[0111] In this embodiment, the scores of the control indicators at the start of "Step 3" (or at the end of "Step 2") do not affect the selection of the control mode. This is because the control indicators are means to reduce the patient's weight to the target weight. Therefore, even if all the control indicator scores are "0", if the current weight has reached the target weight, the application of "Normal Mode" is decided. Figure 10 illustrates an example of the home screen 200A in "normal mode". Figure 10 is denoted with corresponding reference numerals for parts that correspond to those in Figure 4. There are three differences between the home screen 200A shown in Figure 10 and the home screen 200 shown in Figure 4.

[0112] The first difference is the content displayed in information section 201. In Figure 10, the date in weight section 201A is "Day 193, April 1st (Fri)," and the current weight is displayed as "66.0 kg." The graph section also displays the weight change over the past three months. In addition, five buttons, including the "Quiz" button, are displayed as active in function section 201B.

[0113] The second difference is the content displayed in task column 202. In Figure 10, the following tasks are displayed: "Measure your weight" task 202A, "Keep a record of your activities" task 202C, "Recently seen trivia" task 202D, "How to interpret weight changes" task 202E, and "Step 2 process" task 202F. The goal of "Normal Mode" is to maintain weight through self-management. Therefore, "Normal Mode" primarily focuses on recording daily activities and weight, and relearning, and does not provide proactive support through setting behavioral goals.

[0114] The third difference is the content displayed in advice section 203. In Figure 10, advice section 203 reads, "Tap here if you would like to review 'Step 3: Habit Management'." The display in the advice section 203 indicates that the current step is "Step 3," meaning it is habit formation management. In this embodiment, the home screen 200 does not include any indication that the current management mode is "Normal Mode." However, the current management mode may be displayed to the patient user, as in the "Overcoming Weaknesses Mode" described later. After this, the patient terminal 10 (i.e., the patient application 130) proceeds to step 111 (see Figure 3).

[0115] Return to the explanation of step 110A in Figure 9. If the current weight does not meet the target weight (i.e., the current weight is heavier than the target weight), a negative result is obtained in step 110A. In this case, the patient terminal 10 (i.e., the patient app 130) presents a home screen corresponding to the "Overcoming Weaknesses Mode" to support the habituation of changing the behavior that the patient dislikes (step 110C). In other words, the patient terminal 10 (i.e., the patient app 130) applies the "Overcoming Weaknesses Mode" (i.e., the first mode) to patients who have not achieved their goal (target weight). Here, "difficulty" refers to behaviors that have not been sufficiently habitualized. In "difficulty overcoming mode," the same support as in habit formation support (i.e., the same support as in "Step 2") is repeated.

[0116] Figure 11 illustrates an example of the learning screen 240 displayed on the first day of the unit practice period. The learning screen 240 shown in Figure 11 displays a description of the learning content 241, a "back" button 242, and a "next" button 243. In Figure 11, the explanation of the learning content 241 states, "Ms. Suzuki, who was close to her target weight, will continue with 'Learning and practicing behavioral goals.'" This learning screen 240 is specific to the "Overcoming Weaknesses Mode" and is provided to inform the patient that their weight has not yet reached their target weight.

[0117] In this context, "overcoming weaknesses" means making the behaviors that the patient finds difficult a habit. In this embodiment, indicators with low scores are considered "weaknesses." In this embodiment, "low score" is used in a relative sense. For example, a score of "50" is lower than "60" but higher than "40". Therefore, if the scores of all other indicators are "100", an indicator with a score of "90" is a relatively weak indicator.

[0118] However, a score lower than a predetermined score value (baseline value 1) may be considered "low," and a score higher than a predetermined score value (baseline value 1) may be considered "high." For example, if the predetermined score value is "50," then not only a score of "90" but also a score of "60" would be considered high. However, the base value may differ for each indicator. In this embodiment, "overcoming" means raising the score of a weak indicator from its initial value.

[0119] For example, "overcoming" could mean that the score of a difficult indicator exceeds a predetermined score value (benchmark 2). Here, "benchmark 2" is independent of "benchmark 1". However, "benchmark 2" may be the same as "benchmark 1". As described above, the "Overcoming Weaknesses Mode" aims to help you achieve your target weight by supporting the habituation of indicators (or behaviors) that you find difficult. When the "Back" button 242 is pressed, the user returns to the previous page. Incidentally, when the "<" button located in the upper left corner of the screen is pressed, the user returns to the home screen. On the other hand, when the "Next" button 243 is pressed, a home screen 250 (see Figure 12) specific to patients to whom the "Overcoming Weaknesses Mode" is applied is displayed.

[0120] Figure 12 illustrates an example of the home screen 250 in "Overcoming Weaknesses Mode". The home screen 250 shown in Figure 12 is a dedicated screen that is displayed when the "Overcoming Weaknesses Mode" is started. In this embodiment, the home screen 250 consists of a title field 251A, a mode information field 251B, a support details field 251C, a message field 251D, and a "Set Goal" button 251E.

[0121] The title field 251A in Figure 12 displays "Just a little more to reach your target weight." In this embodiment, the same title is used regardless of the size of the difference between the current weight and the target weight. However, the title may be switched depending on the size of the difference. For example, if the difference is less than 1 kg, "Just a little more to reach your target weight" is displayed, but if the difference is more than 1 kg, a specific numerical target such as "5 kg to reach your target weight!" may be displayed.

[0122] In Figure 12, the mode information section 251B displays "You have entered 'Overcoming Weaknesses Mode'." This display allows the patient to recognize that they have entered "Overcoming Weaknesses Mode," that is, that they need to overcome their weaknesses. In the support content section 251C shown in Figure 12, it states, "In this mode, you will be asked to work on behavioral goals again." This indication lets the patient know that in "Overcoming Difficulties Mode," setting and practicing behavioral goals is necessary. As mentioned above, setting and practicing behavioral goals is the same as the support in "Step 2."

[0123] In the message box 251D shown in Figure 12, the message reads, "Let's work hard to achieve your target weight!" This message is meant to encourage the patient. When the "Set Goal" button 251E is pressed, the action goal setting screen 230A (see Figure 13) is displayed. Figure 13 illustrates an example of the display of the behavioral goal setting screen 230A in the "Overcoming Weaknesses Mode" of "Step 3". In Figure 13, corresponding parts with reference numerals are shown.

[0124] In the case of the behavioral goal setting screen 230A shown in Figure 13, the explanation field 231C displays "Choose the learning you want to focus on." This display is intended to encourage relearning of indicators (i.e., behaviors) that the student struggles with. However, as in the case of Figure 8, a message encouraging the selection of behavioral goals would also be acceptable. In the radar chart section 231B shown in Figure 13, the score for "Surrogate Eating" in the "Current" radar chart is low compared to other indicators. Therefore, "Surrogate Eating" is recommended as a behavioral goal in the recommended indicator 231D.

[0125] Additionally, the related content section 232 displays content related to surrogate eating. In Figure 13, related content 232A is "Avoid triggers that make you want to eat," and related content 232B is "Avoid binge eating." Both have been learned in "Step 2." Therefore, the word "Achieved" is displayed for related content 232A and 232B in Figure 13. Here, "Achieved" indicates that the content has been learned in "Step 2" or has been implemented in "Step 2."

[0126] Figure 14 illustrates an example of the display of the retraining screen 260. The relearning screen 260 shown in Figure 14 is displayed when any of the content in the related content section 232 (see Figure 13) is tapped. The relearning screen 260 shown in Figure 14 consists of an indicator information section 261, a content information section 262, a learning content section 263, a progress display section 264, a supporter episode section 265, a "Work on this goal" button 266, and a "View learning" button 267.

[0127] In the indicator information section 261 shown in Figure 14, "Surrogate Feeding" is displayed, corresponding to the manipulated related content 232A (see Figure 13). In other words, the indicators displayed in the indicator information section 261 are linked to the related content displayed in the related content section 232 (see Figure 13). The content information section 262 displays information about the relevant content selected as the learning target. In Figure 14, the content information section 262 displays "Avoiding triggers that make you want to eat." The learning content section 263 shown in Figure 14 states, "There are reasons for eating other than 'being hungry.' By avoiding the causes, you may be able to reduce the frequency of 'wanting to eat.'" The content of the learning content section 263 is determined according to the content information section 262.

[0128] The progress display area 264 shows information on whether the learning has been achieved or not. In Figure 14, the progress display area 264 shows "Achieved". The supporter episode section 265 displays episodes from supporters that correspond to the related content. In Figure 14, episodes from two of the three supporters are displayed. Operating the controls corresponding to each supporter or episode will display the full text of the episode. In Figure 14, only the episode title is displayed.

[0129] When the "Work towards this goal" button 266 is pressed, the learned related content is set as the behavioral goal for the newly started unit practice period. In the case of the relearning screen 260 shown in Figure 14, the sub-behavior related to "surrogate eating," "avoid triggers that make you want to eat," is set as the behavioral goal. When the "View Learning" button 267 is pressed, the behavioral goal setting screen 230A (see Figure 13) is displayed, allowing the user to select the indicators to be studied.

[0130] Figure 15 illustrates an example of the home screen 200B that appears after the behavioral goals for "Overcoming Weaknesses Mode" have been set. In Figure 15, corresponding parts with reference numerals are shown to correspond to those in Figure 10. The difference between the home screen 200B shown in Figure 15 and the home screen 200A shown in Figure 10 is that a mode display 201C is added to the information section 201. In the "Overcoming Weaknesses Mode," if the home screen is 200B, "Overcoming Weaknesses" is displayed as mode display 201C.

[0131] The layout of home screen 200B is the same as the home screen for "Step 2" and home screen 200A for "Normal Mode" (see Figure 10). In other words, it is a screen that the patient has been looking at for at least six months. However, by displaying "Overcoming Weaknesses" as the mode display 201C, the patient can be made aware that a mode for overcoming weaknesses is in progress. After this, the patient terminal 10 (i.e., the patient application 130) proceeds to step 111 (see Figure 3). Let's return to the explanation of Figure 3.

[0132] <Step 111> The patient terminal 10 (i.e., the patient application 130) determines whether it is time to review the mode. In other words, the patient terminal 10 (i.e., the patient application 130) reviews the use of the current mode at a predetermined timing after switching to "normal mode" or "difficulty overcoming mode". In this embodiment, the current mode is reviewed every two weeks. However, two weeks is just one example of "the timing when a predetermined period has elapsed since the start of the current mode," and it could be one week or three weeks or more. Furthermore, the timing of the current mode review may be managed on a daily basis, such as every 5 days or every 10 days, rather than on a weekly basis. Furthermore, the current mode review cycle may be individually set by the doctor through the doctor app. For example, the review timing could be set to every two weeks for "Patient A" and every three weeks for "Patient B".

[0133] If it is time to review the current mode, a positive result is obtained in step 111. In this case, the patient terminal 10 (i.e., the patient app 130) returns to step 110. The patient terminal 10 (i.e., the patient app 130) returns to step 110 and decides again which mode to execute in management mode.

[0134] The management mode is reviewed not only when the current mode is "Weakness Overcoming Mode," but also when it is "Normal Mode." This is because even in "Normal Mode," there is a possibility that the weight may exceed the target weight again. Also, as mentioned above, if the target weight has been achieved, "Normal Mode" will be selected even if there are indicators with low scores. When switching from "Normal Mode" to "Weakness Overcoming Mode," for example, the learning screen 240 (see Figure 11) or the home screen 250 (see Figure 12) will be displayed.

[0135] On the other hand, if the target weight has been achieved at the end of the "overcoming weaknesses mode," the patient terminal 10 (i.e., the patient app 130) changes the management mode for the newly starting unit practice period to "normal mode." Figure 16 illustrates an example of a change notification screen 270 used to indicate a change from "Overcoming Weaknesses Mode" to "Normal Mode." In Figure 16, the change notification screen 270 is displayed as a pop-up in front of the home screen 200B for "Overcoming Weaknesses Mode."

[0136] The change notification screen 270 shown in Figure 16 consists of multiple messages 271, 272, 273, and 274. The message 271 shown in Figure 16 displays "Congratulations!" and "You have completed the difficulty-overcoming mode." This display allows the patient to indirectly know that they have transitioned to "normal mode." The message 272 shown in Figure 16 displays "You have fallen below your target weight!". The display of message 272 is used to notify the patient of the reason or cause for the mode change. This display allows the patient to clearly understand the reason or cause for the change in support.

[0137] Message 273, shown in Figure 16, displays the message, "The next goal is for you to be able to manage your weight on your own." This message 273 allows the patient to understand the goal for the next unit practice period in which the modified mode will be applied. The message 274 shown in Figure 16 reads, "Let's live our daily lives remembering what we have learned so far." This message 274 is encouragement and advice for the patient. Let's return to the explanation of Figure 3. If it is not time to review the mode, a negative result is obtained in step 111. In this case, the patient terminal 10 (i.e., the patient app 130) proceeds to step 112.

[0138] <Step 112> The patient terminal 10 (i.e., the patient app 130) determines whether a predetermined number of days (e.g., 340 days) has elapsed since the start of using the patient app 130. This determination is used to detect the timing for performing the second type analysis. The predetermined number of days may be set for each disease. Also, even for the same disease, different numbers of days may be used if the patient app 130 is different.

[0139] If no predetermined number of days have elapsed since the patient began using the patient app 130, a negative result is obtained in step 112. In this case, the patient terminal 10 (i.e., the patient app 130) returns to step 110. On the other hand, if a predetermined number of days have passed since the patient started using the patient app 130, a positive result is obtained in step 112. In this case, the patient terminal 10 (i.e., the patient app 130) proceeds to step 113.

[0140] <Step 113> The patient terminal 10 (i.e., the patient application 130) performs a second type analysis and displays the analysis results in a radar chart. In this embodiment, the second type analysis is performed whether the current mode is "normal mode" or "weakness overcoming mode." This is because even if the target weight has been achieved, there is a possibility that the patient has not yet developed healthy lifestyle habits. 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".

[0141] Figure 17 illustrates an example of the display screen for the results of the second type analysis. In Figure 17, corresponding parts with those in Figure 6 are indicated with corresponding numerals. There are two differences between the "Type Analysis" screen 220 shown in Figure 17 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.

[0142] 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 17, 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 "exercise," "eating habits," "dietary content," "substitute feeding," "eating motivation," and "regularity of eating habits" are at their highest, but the scores for the other two management indicators are not. This indicates that behavioral improvements are still needed for these two management indicators.

[0143] 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."

[0144] The second difference is that the "Type Analysis" screen 220 shown in Figure 17 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 "Normal Mode" or "Overcoming Weaknesses Mode" is in operation, so it depends on the current management mode. However, if the second type analysis is performed on the final day of "Step 3," setting new behavioral goals is not planned. In this embodiment, the second type analysis is assumed to be performed on the final day of "Step 3," but the process may return to Step 110 after the second type analysis is performed.

[0145] <Summary> The patient app 130 envisioned in this embodiment controls the mode in the "habituation of behavior" step (i.e., "step 3") to either "normal mode" or "weakness overcoming mode" depending on the patient's progress toward achieving their target weight. Specifically, patients who have achieved their target weight are given the "normal mode," which is based on self-care, while patients who have not achieved their target weight are given the "weakness overcoming mode," which is based on continuing the "practice of behavior" step (i.e., "step 2"). This control allows the patient app 130 to provide support to the patient according to their progress in achieving their goals.

[0146] In this embodiment, the patient app 130 switches between "normal mode" and "weakness overcoming mode," and the patient is not allowed to freely switch or change modes. This function prevents situations where "normal mode" is applied instead of "weakness overcoming mode" even though the target weight has not been achieved. In other words, it prevents situations where "normal mode" is used for purposes other than its intended use, resulting in the inability to obtain therapeutic effects using the patient app 130.

[0147] Furthermore, in this embodiment, the patient app 130 presents one or more behavioral goals only to patients who have not achieved their target weight, thereby supporting them in achieving their target weight. In other words, the patient app 130 operating in "normal mode" does not present behavioral goals to the patient, while the patient app 130 operating in "weakness overcoming mode" presents one or more behavioral goals to the patient. In other words, in this embodiment, for patients who have achieved their target weight, support can be shifted from active support through the presentation of behavioral goals to passive support, enabling them to maintain their target weight through self-management. On the other hand, for patients who have not yet reached their target weight, active support can be provided through the presentation of behavioral goals to help them achieve their target weight.

[0148] <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.

[0149] (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.

[0150] 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.

[0151] 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).

[0152] 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.

[0153] 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.

[0154] 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.

[0155] 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.

[0156] (3) In the above-described embodiment, the timing for reviewing the "normal mode" and the "weakness overcoming mode" was explained as the timing when two cycles of the unit practice period have ended from the start of the current mode. However, the timing for reviewing "normal mode" and "overcoming weaknesses mode" is not limited to the examples mentioned above.

[0157] For example, the "Normal Mode" and "Overcoming Weaknesses Mode" could be reviewed at the time when a doctor or other medical professional instructs a switch to the current mode (for example, when instructing a mode switch via a doctor app). Additionally, the "normal mode" and "weakness-overcoming mode" may be reviewed when the patient's attributes change (for example, when switching from the insurance coverage period to the selective treatment period).

[0158] Furthermore, patient attributes may include the achievement status of goals (e.g., target weight). For example, the patient may switch from "overcoming weaknesses mode" to "normal mode" the day after achieving their goal, or switch from "normal mode" to "overcoming weaknesses mode" the day after their goal reverts from being achieved to not being achieved. Furthermore, the timing of the review is not limited to adopting just one of the example timings; multiple timings may be adopted simultaneously.

[0159] (4) In the above-described embodiment, the fact that the current mode is "Overcoming Weaknesses Mode" is displayed on the home screen 250 (see Figure 12) and home screen 200B (see Figure 15), but the fact that the current mode is "Normal Mode" is not displayed on the home screen or elsewhere. However, it is also acceptable to display on the home screen or elsewhere that the current mode is "normal mode." Even in the case of "normal mode," displaying this on the home screen or elsewhere would allow patients to easily confirm the mode they are currently using.

[0160] (5) In the above-described embodiment, the case in which the support provided in "Step 3" consists of two types, "Normal Mode" and "Overcoming Weakness Mode," was explained. However, you may provide three or more modes and use any of them as the current mode. For example, you could divide the "Overcoming Weaknesses Mode" into multiple sub-modes and switch between the sub-modes applied depending on the relationship between, for example, your goal (e.g., target weight) and your current value.

[0161] (6) In the embodiments described above, whether a goal (e.g., target weight) has been achieved or not has been achieved was explained as an example of "progress towards achieving the goal." In other words, the progress is determined in two ways: achieving the goal and not achieving it. However, progress can be managed using three or more different methods, and the support provided can be changed accordingly. For example, the support provided can be changed based on the magnitude of the difference between the current value and the target.

[0162] (7) In the embodiments described above, the focus is on achieving a goal (for example, target weight), and the support content in step 3 is controlled accordingly, but the embodiments are not limited to this. For example, the support provided in Step 3 may be controlled according to the "achievement status of the behavioral goals." Here, the "achievement status of the behavioral goals" may be managed, for example, by the sum of the scores for each indicator.

[0163] (8) In the above-described embodiment, "Step 3" provides "Normal Mode" and "Weakness Overcoming Mode," and the mode used as the current mode is switched according to the progress made in achieving the goal. However, in other steps (for example, "Step 2"), the support provided may also be controlled according to the progress made in achieving the goal. For example, in "Step 2," once the target weight is achieved, the support provided to the patient may be switched to "the following day" or "at the end of the unit practice period."

[0164] (9) In the above-described embodiment, the case in which the mode in the "habit formation of behavior" step is controlled to "normal mode" or "overcoming weakness mode" as a function of the patient app 130 (see Figure 1) was explained. However, the function to control the support provided in management mode may be provided on the server side that manages patient data.

[0165] Figure 18 illustrates an information processing system 100 consisting of a management server 20 for managing patient data 236 and a patient terminal 10. Figure 18 is denoted with reference numerals corresponding to the parts that correspond to those in Figure 1. The patient application 130A on the patient terminal 10 in Figure 18 differs from the embodiment in that it does not have a function to switch between "normal mode" and "weakness overcoming mode" according to the progress of goal achievement. However, the patient application 130A has a function to switch the mode applied in "step 3" in response to instructions from the management server 20.

[0166] 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 switching modes applied in "Step 3" for each patient.

[0167] 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.

[0168] 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. Among the other programs is the mode management application 235. The mode management application 235 is a program that manages the progress of the treatment plan of the patient application running on the patient terminal 10. Mode management app 235 is an example of a program that enables the management of progress toward goals and controls the support provided in management modes based on health app data recorded by patients working on behavioral change.

[0169] 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.

[0170] Figure 19 is a flowchart illustrating an example of the processing operation of the mode management application 235 (see Figure 18). In Figure 19, corresponding parts with reference numerals are shown. In the case of Figure 19, only the determination and review of the management mode in "Step 3" (Steps 110A, 111A) and the management of the timing of the second type analysis (Step 112A) are performed on the management server 20, while other processing operations are performed on the patient terminal 10.

[0171] 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.

[0172] In the explanation in Figure 19, the management server 20 controls whether the current mode applied in "Step 3" is "Normal Mode" or "Overcoming Difficulties Mode," but it may also perform all the functions of the patient application 130. In this case, the patient uses a patient terminal 10 such as a smartphone as an input / output device and utilizes the services of the patient application 130 described as an embodiment as a cloud service.

[0173] (10) 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.

[0174] (11) In the embodiment described above, 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).

[0175] (12) 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.

[0176] (13) In the embodiments described above, a patient application for NASH was described. 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.

[0177] (14) 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 the health data recorded by the user working to change their behavior was installed. However, the app that users working to change their behavior use to record health-related data can be any user app, including so-called healthcare apps.

[0178] In this case, a function is provided to control the level of support in management mode for any user application, based on its progress towards achieving its goals. Any user application could be a diary application, a photo application, or an audio application. Furthermore, if user data (including patient data) for any user application is managed on the server, a function may be provided on the server side to control the support content of the management mode according to the progress of goal achievement, as explained using Figure 19.

[0179] <Summary> An example of the disclosure described in the above-mentioned embodiment is shown below. (((1))) A program that enables a computer to control the level of support provided in management mode based on the user's progress in achieving their goals as they work towards behavioral change. This program allows for personalized support tailored to each user's progress toward achieving their goals.

[0180] (((2))) The function that controls the support provided in management mode is the program described in (((1))) which controls the switching between the first mode, which supports the achievement of the goal, and the second mode, which supports the continuation of the state in which the goal has been achieved. According to this program, switching between two modes can help users achieve their goals.

[0181] (((3))) The function that controls the support provided in management mode is the program described in (((2))) which uses the first mode for users who have not achieved their goals and the second mode for users who have achieved their goals. According to this program, the type of support can be adjusted according to the progress made in achieving the goals.

[0182] ((((4))) The function that controls the support provided in management mode is the program described in (((2))) which determines whether to continue in the currently used mode or switch to another mode at a predetermined timing after the switch. According to this program, the support provided can be reviewed in accordance with changes in the progress towards achieving the goals.

[0183] (((5))) The program described in (((4)))) where the predetermined timing is one or more of the following: the timing when the user's attributes change, the timing when a medical professional instructs a switch, and the timing when a predetermined period has elapsed since the start of the first mode or the second mode. This program helps to avoid mismatches in the level of support provided.

[0184] (((6))) The function that controls the support provided in management mode is the program described in (((2))) which, while support is being provided in mode 1, informs the user that support is being provided in mode 1. This program can help users become aware of the need to make certain behaviors a habit.

[0185] (((7))) The function that controls the support content in management mode is the program described in (((2))) which presents one or more behavioral goals when providing support in the first mode, and does not present one or more behavioral goals when providing support in the second mode. According to this program, users who have not achieved their goals can be presented with behavioral targets to help them achieve them.

[0186] (((8))) The behavioral goal is the program described in (((7))) which is one of several indicators in which the score is lower than the standard or in which the score is lower than that of other indicators. According to this program, it is possible to set indicators with low scores as behavioral goals.

[0187] (((9))) Management mode support is a program described in any one of (((1))) to (((8))) that is started after the mode for supporting goal achievement has ended. This program allows for the provision of support tailored to the user's situation after the completion of a mode that assists in achieving goals.

[0188] (((10))) A method for providing information in which a computer performs a process to control the support provided in management mode according to the progress of a user working to change their behavior in achieving their goals. This information delivery method allows for personalized support tailored to each user's progress toward achieving their goals.

[0189] (((11))) An information processing device having a processor, the processor controls the level of support provided in management mode according to the progress of the user in achieving their goals as they work towards behavioral change. This information processing device allows for personalized support tailored to each user's progress toward achieving their goals. [Explanation of symbols]

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

Claims

1. On the computer, A function that controls the level of support provided in management mode based on the progress of users working towards achieving their goals in behavioral change. A program to achieve this.

2. The function that controls the support content of the aforementioned management mode controls the switching between a first mode that supports the achievement of the goal and a second mode that supports the continuation of the state in which the goal has been achieved. The program according to claim 1.

3. The function that controls the support provided in the management mode uses the first mode for users who have not achieved the goal, and uses the second mode for users who have achieved the goal. The program according to claim 2.

4. The function that controls the support provided in the aforementioned management mode determines, at a predetermined timing after the switch, whether to continue the currently used mode or switch to another mode. The program according to claim 2.

5. The predetermined timing is one or more of the following: the timing when the user's attributes change, the timing when a medical professional instructs a switch, and the timing when a predetermined period has elapsed since the start of the first mode or the second mode. The program according to claim 4.

6. The function that controls the support content of the management mode shall, while support is being provided in the first mode, indicate to the user that support is being provided in the first mode. The program according to claim 2.

7. The function that controls the support content of the management mode presents one or more behavioral goals when providing support in the first mode, and does not present one or more behavioral goals when providing support in the second mode. The program according to claim 2.

8. The aforementioned behavioral target is an indicator whose score is lower than the standard among several indicators, or an indicator whose score is lower than other indicators. The program according to claim 7.

9. The support provided by the aforementioned management mode is initiated after the mode for supporting the achievement of the goal has ended. The program according to any one of claims 1 to 8.

10. Computers A process that controls the level of support provided in management mode based on the progress of users working towards achieving their goals in behavioral change. A method for providing information to carry out the task.

11. It has a processor, The aforementioned processor, The support provided in management mode is controlled according to the progress of users working towards achieving their goals in behavioral change. Information processing device.

Images