Information processing device, information provision method, and program

Abstract

We provide a system that supports the improvement of lifestyle habits from a psychological perspective. [Solution] An information processing device having a processor, the processor obtains a reference date for the target user regarding a program used by a user who is changing their behavior to record health-related data, and presents the target user with a reference diary associated with the number of days that have passed from the reference date to the present.

Description

Technical Field

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

Background Art

[0002] As a means for supporting the improvement of lifestyle habits, the use of application programs executed on user terminals has attracted attention. Currently, various application programs for supporting the improvement of lifestyle habits are publicly available in the app store.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Application programs for supporting the improvement of lifestyle habits can record health-related data in the form of a diary. On the other hand, current application programs specialized for recording have limitations in improving lifestyle habits.

[0005] This disclosure provides a mechanism to support the improvement of lifestyle habits from a psychological perspective. [Means for solving the problem]

[0006] The invention described in claim 1 is an information processing device having a processor, the processor obtaining a reference date for a target user relating to a program used by a behavior-changing user to record health data, and presenting the target user with a reference diary associated with the number of days elapsed from the reference date to the present. The invention described in claim 2 is the information processing device according to claim 1, wherein the reference diary includes at least one first diary in which the indicators managed by the program are good and a second diary in which the indicators managed by the program are not good. The invention described in claim 3 is an information processing device according to claim 2, wherein the index relates to behavior or results recorded as data relating to health. The invention described in claim 4 is the information processing device according to claim 1, wherein the reference diary is a pre-prepared virtual diary. The invention described in claim 5 is the information processing device described in claim 1, wherein the reference diary includes advice according to its contents. The invention described in claim 6 is an information processing device according to claim 1, wherein the processor presents the reference diary after detecting the recording of health data by the target user. The invention described in claim 7 is an information processing device according to claim 1, wherein the processor stops presenting the reference diary when the number of days exceeds a threshold. The invention described in claim 8 is an information processing device according to claim 1, wherein if the health data includes data inherited from another program different from the program, the processor obtains the second reference date of the target user relating to the other program as the reference date. The invention described in claim 9 is an information provision method in which a computer performs the following processes: obtaining a reference date for a target user with respect to a program used by a user who changes their behavior to record health data; and presenting the target user with a reference diary associated with the number of days that have elapsed from the reference date to the present. The invention described in claim 10 is a program for a computer to implement the following functions: a function to cause a user to obtain a reference date for a program used by a user who changes their behavior to record health data; and a function to cause the user to be presented with a reference diary associated with the number of days that have passed from the reference date to the present. [Effects of the Invention]

[0007] According to one form of this disclosure, it is possible to provide a mechanism that supports the improvement of lifestyle habits from a psychological perspective. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram illustrates an example of the overall configuration of an information processing system according to an embodiment. [Figure 2] This diagram illustrates an example hardware configuration for a PDT platform. [Figure 3] This diagram illustrates an example of status management data stored in the auxiliary storage device of the PDT platform. [Figure 4] This diagram illustrates an example hardware configuration for a PDT server. [Figure 5] This diagram illustrates an example of patient data stored in the auxiliary storage device of a PDT server. [Figure 6] This diagram illustrates an example of the hardware configuration for a physician's terminal and a patient's terminal. [Figure 7] This diagram illustrates an example of a diary table stored in auxiliary storage as part of a patient application. [Figure 8] This diagram illustrates the first half of the sub-diary table for a character whose metrics managed in the patient app are favorable. [Figure 9]This is a diagram explaining the latter half of the sub-diary table of a character with good indicators managed by the patient app. [Figure 10] This is a diagram explaining the first half of the sub-diary table of a character with poor indicators managed by the patient app. [Figure 11] This is a diagram explaining the latter half of the sub-diary table of a character with poor indicators managed by the patient app. [Figure 12] This is a diagram explaining an example of the processing sequence in the embodiment. [Figure 13] This is a diagram explaining the "Home" screen of the patient app. [Figure 14] This is a diagram explaining the "Pi Diary" screen. [Figure 15] This is a diagram explaining the "Pi Diary" screen. [Figure 16] This is a diagram explaining the presentation process of the "Pi Diary" by the PDT server.

Embodiments for Carrying Out the Invention

[0009] <Terms> First, the terms used in the embodiments described below will be explained. The "program for promoting behavior 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 depends on the user who uses the program. Therefore, the program for promoting behavior change can also be said to be a program for supporting behavior change.

[0010] This type of program includes a program positioned as a medical device and a program positioned as a non-medical device. The program positioned as a medical device is an example of a program that requires a prescription, and the program positioned as a non-medical device is an example of a program that does not require a prescription. Note that the program positioned as a non-medical device is not limited to a program for promoting behavior change, and may also be a program having a function of recording health-related data. Programs that promote behavior change or record health-related data include, in addition to programs that can be downloaded from the app store, programs used by private businesses, public organizations, etc. for the health management of employees, etc. Among the programs classified as non-medical devices, there are also programs used in medical institutions.

[0011] The "purpose of the app" refers to the effects to be achieved by using a program that promotes behavior change. The purpose of the app varies depending on the disease corresponding to the program that promotes behavior change. For example, the purposes of the app include improvement of lifestyle habits, continuation of improved lifestyle habits, and continuation of improved numerical values.

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

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

[0014] A "user" refers to a person who uses a program that has the function of recording health-related data. A person who changes their behavior through the aforementioned behavioral change-promoting program is an example of a user. Users include both users before visiting a medical institution and users who have visited a medical institution. Users who have visited a medical institution include both users who are eligible for medical fee calculation and users 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 app" refers to a program that can be used through a terminal operated by a doctor or other healthcare professional (hereinafter also referred to as a "doctor terminal"). In the embodiment described later, the doctor app runs on a cloud server that can be operated from the doctor terminal. The doctor app is used to view patient data (including patient app data). Healthcare professionals are also referred to as medical personnel.

[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, and goal achievement status. However, the information recorded as patient data varies depending on the disease, and it does not need to include all of the information exemplified; it may include only some of it, or other information. Furthermore, all the information recorded as patient data is also an example of health-related data.

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

[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 also serve as examples of reference diaries. Furthermore, quantitative information from these records is an example of an indicator managed within a patient app.

[0021] "Medical history" includes, for example, the date treatment began, the date of the consultation, the content of the treatment, and advice given. Medical history is just one example of information related to a medical consultation. "Patient app operation history" refers to, for example, the history of operations related to launching the patient app, inputting measurement values ​​and reflections, etc. "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. "Goal achievement status" refers to information indicating the progress toward goals set by a doctor for each patient. It could also refer to the progress toward goals set by the patient themselves. Furthermore, it could refer to the progress toward goals presented by a patient app for each patient. Furthermore, the information mentioned above can be classified into subjective information and objective information.

[0024] 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 may include personal information. Health-related data may include data recorded through programs that encourage behavioral change, as well as data obtained by processing such data.

[0025] The processed data includes, for example, processed data, data obtained through statistical processing, and summaries of patient data generated by artificial intelligence (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 the baseline. Health-related data may include data related to programs other than those that have the functionality to record health data or programs that encourage behavioral change. For example, it may include user accounts used to access various services and privacy-related information.

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

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

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

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

[0030] "Before use begins" refers to a state where the prescription for the patient app has been issued, but the patient has not yet started using it on their device. For example, it refers to a state where the patient has not yet entered the prescription code into their device. "Expired start date" refers to a situation where the prescription code was not entered within the period during which the prescription code is valid (for example, within 4 days including the prescription date).

[0031] "In Use" refers to the state where the patient app installed on the patient's device has been activated and is available for use. Note that activating the patient app requires entering an activation code, such as the prescription code mentioned above. "Scheduled to end" refers to a state in which a medical institution has designated a patient as no longer subject to management within the validity period. For example, this state is set for patients who do not receive follow-up appointments.

[0032] "Termination" refers to a state where the patient app becomes unusable, for example, due to the expiration of its validity period. "Expiration of the period" indicates that a specified period has elapsed since the prescription date. The specified period is set to be longer than the validity period. For example, if the validity period is 6 months, the specified period is set to 8 months. "Selective Medical Treatment" is displayed when the validity period has expired but the treatment is still eligible for selective medical treatment. Selective medical treatment refers to a medical service that allows patients enrolled in social insurance to receive treatment not covered by insurance in conjunction with treatment covered by insurance, by bearing the additional cost.

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

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

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

[0036] <Embodiment> <Overall System> Figure 1 is a diagram illustrating an example of the overall configuration of an information processing system 1 according to an embodiment. The information processing system 1 shown in Figure 1 consists of a PDT platform 10, PDT servers 20 (20A, 20B, 20C...20F), a physician terminal 30, and a patient terminal 40.

[0037] Figure 1 shows only one PDT platform 10. However, multiple PDT platforms 10 may exist. The PDT platform 10 may consist of multiple servers connected via a network. In this case, the multiple servers cooperate to provide the services of the PDT platform 10. The PDT platform 10 and the PDT server 20 are connected via a network (not shown) that enables communication. For reference, the network could include, for example, a LAN (Local Area Network), the Internet, or a mobile communication system (4G, 5G, etc.).

[0038] In Figure 1, six PDT servers 20 are connected to one PDT platform 10. However, the number of PDT servers 20 connected to one PDT platform 10 is arbitrary. The PDT server 20 is a server that performs tasks such as patient authentication, management of patient application data entered through the patient application, and provision of patient data to physician terminals (not shown). The PDT server 20 is an example of an information processing device. In Figure 1, the PDT server 20A is a server that manages patient data for a patient application (hereinafter referred to as "Patient Application A") provided by Company A for patients with alcohol dependence. PDT Server 20B is a server that manages patient data for a patient application (hereinafter referred to as "Patient Application B") provided by Company B for patients with hypertension.

[0039] PDT Server 20C is a server that manages patient data for a patient application (hereinafter referred to as "Patient Application C") provided by Company A for patients with diabetes. PDT Server 20D is a server that manages patient data for a patient application (hereinafter referred to as "Patient Application D") provided by Company B for patients with diabetes. PDT Server 20E is a server that manages patient data for a patient application (hereinafter referred to as "Patient Application E") provided by Company C for patients with dyslipidemia. PDT Server 20F is a server that manages patient data for the patient application (hereinafter referred to as "Patient Application F") provided by Company D for patients with NASH.

[0040] As shown in Figure 1, a PDT server 20 is prepared for each combination of the disease targeted by the patient application and the service provider that provides the patient application. Therefore, even if the service provider that provides the patient application is the same, different PDT servers 20 will be prepared if the targeted diseases are different. Furthermore, even if the target disease is the same, different PDT servers 20 will be provided if the service provider offering the patient app is different.

[0041] However, it is also possible to provide a single PDT server 20 for multiple patient applications with different combinations. The PDT platform 10 and the PDT servers 20 are not limited to being operated by the same operator; they may be operated by different operators. For example, some of the operators of the multiple PDT servers 20 may be the same operator as the operator of the PDT platform 10.

[0042] The physician terminal 30 is a terminal operated by physicians and other medical professionals who use the services provided by the PDT platform 10 and the PDT server 20. Figure 1 shows only one physician terminal 30 as a representative example. For example, physicians can view the usage status of patient applications by logging into the PDT platform 10. They can also view patient data by logging into the PDT server 20. The physician's terminal 30 can be, for example, a desktop computer, a laptop computer, a tablet computer, a smartphone, smart glasses, or a server.

[0043] The patient terminal 40 is a terminal operated by the patient. The patient terminal 40 uploads patient application data recorded through the patient application to the corresponding PDT server 20. Figure 1 shows only one patient terminal 40 as a representative example. The patient terminal 40 is an example of a user terminal. The patient terminal 40 is also an example of an information processing device. The patient terminal 40 may be, for example, a smartphone, smart glasses, a desktop computer, a laptop computer, or a tablet computer.

[0044] <Terminal Hardware Configuration> <PDTプラットフォーム> Figure 2 illustrates an example of the hardware configuration of the PDT platform 10. The PDT platform 10 is a so-called server. The PDT platform 10 shown in Figure 2 includes a processor 11, semiconductor memory 12, auxiliary storage device 13, and communication interface 14. Each device is connected via a bus or other signal lines.

[0045] Processor 11 is a device that realizes various functions through program execution. Processor 11 may be composed of a plurality of CPU (Central Processing Unit) cores. In that case, Processor 11 executes a program through the cooperation of a plurality of CPU cores. UEFI (Unified Extensible Firmware Interface) etc. are stored in semiconductor memory 12. Semiconductor memory 12 is also used as an execution area for programs. Processor 11 and semiconductor memory 12 function as a computer.

[0046] Auxiliary storage device 13 is composed of, for example, a hard disk device or a semiconductor storage. Operating systems and other programs are stored in auxiliary storage device 13. Other programs include, for example, a program that displays a list of usage statuses of patient apps. In addition, data for managing status management data 130 by prescription code prescribed by a medical institution is also stored in auxiliary storage device 13. Communication interface 14 is an interface for communicating with external terminals such as PDT server 20 (see FIG. 1) through a network. Communication interface 14 is compatible with communication standards such as Ethernet (registered trademark), Wi-Fi (registered trademark), and mobile communication systems.

[0047] <Management data of the PDT platform> FIG. 3 is a diagram for explaining an example of status management data 130 stored in auxiliary storage device 13 (see FIG. 2) of PDT platform 10 (see FIG. 1). Prescription code 130A, patient ID / patient name 130B, prescription date / consultation date 130C, medical institution ID / prescriber ID 130D, patient app name 130E, and usage status 130F are stored in status management data 130 shown in FIG. 3. However, these are just examples, and for example, a patient's medical record number, patient's gender, patient's date of birth, age, type of insurance card, insurance number, and version of the patient app may be stored.

[0048] Prescription code 130A is issued from the physician's terminal 30 (see Figure 1) for each prescription notification. Patient ID / Patient Name 130B is the patient ID and patient name registered when the prescription was issued in the patient app. In Figure 3, the patient name for patient ID "12543" is "Mr. A", the patient name for patient ID "12544" is "Mr. B", and the patient name for patient ID "12545" is "Mr. C".

[0049] The prescription date / consultation date 130C is the date the doctor examined the patient. In this embodiment, the consultation date on which the doctor prescribed the patient app is indicated as the "prescription date" to distinguish it from other consultation dates. In Figure 3, only the prescription date is stored. In Figure 3, the prescription date for the patient app for "Person A" and "Person B" is "2024 / 5 / 28", and the prescription date for the patient app for "Person C" is "2024 / 2 / 24". The Medical Institution ID / Prescriber ID 130D is an ID that identifies the medical institution and prescriber that prescribed the patient app. In Figure 3, prescription codes "12345" and "23456" were prescribed by the same doctor or other medical institution at the same medical institution.

[0050] Patient app name 130E is the name of the patient app prescribed by the doctor or other medical professional. However, it is sufficient to remember the patient app's identification code, as long as the patient app can be identified. In Figure 3, "Patient A" and "Patient B" are prescribed patient app A. Patient C is prescribed patient app D. Usage status 130F indicates the usage status of the patient's application. The usage status can store one of the following: not yet started, start date expired, in use, scheduled to end, ended, or period expired. In Figure 3, all patient applications are in the "in use" status.

[0051] <PDTサーバ> Figure 4 illustrates an example of the hardware configuration of the PDT server 20. The PDT server 20 shown in FIG. 4 has a processor 21, a semiconductor memory 22, an auxiliary storage device 23, and a communication interface 24. Each device is connected through a bus or other signal lines.

[0052] The processor 21 is a device that realizes various functions through program execution. The processor 21 may be composed of a plurality of CPU cores. In that case, the processor 21 executes a program through the cooperation of the plurality of CPU cores. UEFI etc. is stored in the semiconductor memory 22. The semiconductor memory 22 is also used as a program execution area. The processor 21 and the semiconductor memory 22 function as a computer.

[0053] The auxiliary storage device 23 is composed of, for example, a hard disk device or a semiconductor storage. The operating system and other programs are stored in the auxiliary storage device 23. Other programs include, for example, a doctor app. The doctor app is a program that generates a browsing screen of patient data corresponding to patients examined by doctors etc.

[0054] In addition, patient data 230 recorded through the patient app is also recorded in the auxiliary storage device 23. The communication interface 24 is an interface for communicating with external terminals such as the PDT platform 10 through a network. The communication interface 24 corresponds to communication standards such as Ethernet (registered trademark), Wi-Fi (registered trademark), and mobile communication systems.

[0055] <Management data of the PDT server> FIG. 5 is a diagram for explaining an example of patient data 230 stored in the auxiliary storage device 23 (see FIG. 4) of the PDT server 20. The patient data 230 shown in FIG. 5 stores measurement values and other information recorded through the patient app. The content of the information recorded as patient data 230 also differs depending on the disease corresponding to the patient app. In Figure 5, patient data 230 stores prescription code 230A, patient ID / patient name 230B, and patient application data 230C.

[0056] In this embodiment, patient application data 230C means patient application management data and data recorded by the user through the patient application. Prescription code 230A records prescription code 130A (see Figure 3) issued by the PDT platform 10 (see Figure 1). Prescription code 130A is registered by the patient when they start using the patient app (i.e., when they register for the first time). The patient ID / patient name 230B is, for example, the patient ID and patient name at the medical institution that prescribed the patient app. The patient ID and patient name are obtained from the PDT platform 10, for example, when the prescription code is authenticated.

[0057] The patient app data 230C shown in Figure 5 includes measurement values / measurement date and time 230C1, reflection / input date and time 230C2, current step of the treatment program 230C3, treatment program implementation history 230C4, behavioral goals 230C5, target values ​​230C6, outpatient records 230C7, and medication records 230C8. Note that the items exemplified do not need to be all of the patient app data 230C; they may be only a part of it, or other items may be included.

[0058] The measurement / measurement date and time field 230C1 records the health-related values ​​and date and time measured by the patient. For example, in a patient app for hypertension, the measured blood pressure value and the date and time the blood pressure was measured are recorded. The blood pressure value is given as systolic blood pressure and diastolic blood pressure. The "Reflection / Input Date & Time 230C2" field records a reflection on the day's activities along with the input date and time. The review process records things like physical condition level, stress level, sleep duration, weight, alcohol consumption, activities undertaken, and a diary (user's thoughts on the day's activities, etc.). For example, sleep duration, weight, and alcohol consumption are examples of results recorded as health-related data.

[0059] The content of the actions consists of the genre of the action that was performed and text input. Incidentally, other possible labels include, for example, "sleep," "stress," "moderate alcohol consumption," and "other." In this embodiment, the genre of the action that was performed is recorded by checking buttons labeled with "salt reduction," "weight loss," "exercise," etc. Text input allows users to freely enter content, emotions, etc., that cannot be recorded by checking buttons.

[0060] The current step 230C3 of the treatment program records the steps indicating the progress of the treatment program provided by the patient app. In this embodiment, the treatment program consists of three steps. These three steps consist of, for example, "acquiring knowledge," "implementing behavioral goals," and "habituating behavior." The treatment program implementation history 230C4 records the history of learning and behavior practiced in accordance with the treatment program. For example, in the case of a patient app for hypertension, "Step 1" records the learning history, including whether or not each learning item has been completed. "Step 2" records the behavior history, including the progress towards goals such as "salt reduction," "weight loss," "exercise," "sleep," "stress," "alcohol consumption," and "smoking cessation." "Step 3" records the progress towards behaviors set as goals by the patient.

[0061] Behavioral objective 230C5 records the behaviors that the patient has set as goals. These goals include one or more behavioral objectives selected by the patient from those presented by the patient app as the treatment program progresses. For example, behavioral objective 230C5 records the behavioral objectives set by the patient in step 2 or 3 of the treatment program. A behavioral objective refers to the action that must be taken to achieve the target goal. Furthermore, behavioral goals are not limited to those selected from the behaviors presented by the patient app; they may also include behaviors set individually by the patient.

[0062] The target value 230C6 is where the value set by the doctor or other medical professional during the examination is recorded. The "Target Blood Pressure Value" column is an example of a quantitative target, as it is given as a numerical value. Outpatient record 230C7 records appointments with the doctor, the date of the next appointment, medication timing, etc. The appointments with the doctor record what the patient should do or be careful about before the next consultation. In this embodiment, appointments with the doctor can only be recorded through the patient app. Alternatively, appointments with the doctor may only be recorded from the doctor's terminal 30 (see Figure 1). Medication record 230C8 contains information about the taking of prescribed medications.

[0063] <Physician terminal / Patient terminal> Figure 6 illustrates an example of the hardware configuration of a physician terminal 30 and a patient terminal 40. The hardware configuration of the physician terminal 30 and the patient terminal 40 are basically the same. Therefore, in Figure 6, they are expressed in the format of "code of the elements constituting the physician terminal 30 / code of the elements constituting the patient terminal 40". The physician terminal 30 / patient terminal 40 shown in Figure 6 includes a processor 31 / 41, semiconductor memory 32 / 42, auxiliary storage device 33 / 43, input interface 34 / 44, input device 35 / 45, output interface 36 / 46, output device 37 / 47, and communication interface 38 / 48. Each device is connected via a bus or other signal lines.

[0064] The processors 31 / 41 are devices that perform various functions through program execution. The processors 31 / 41 may consist 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 32 / 42 stores UEFI and other information. The semiconductor memory 32 / 42 is also used as an execution area for programs. The processor 31 / 41 and the semiconductor memory 32 / 42 function as a computer. The auxiliary storage devices 33 / 43 consist of, for example, hard disk drives or semiconductor storage devices. The operating system and other programs are stored in the auxiliary storage devices 33 / 43.

[0065] In the case of the physician terminal 30, the auxiliary storage device 33 stores a client certificate for accessing the PDT platform 10 (see Figure 1) and a client certificate for accessing the PDT server 20 (see Figure 1). In the case of the patient terminal 40, the auxiliary storage device 43 stores a client certificate for accessing the PDT server 20 (see Figure 1). The auxiliary storage device 43 also stores the patient application and patient application data 230C (see Figure 5) recorded through the program. The patient application in this embodiment includes a diary table. The diary table stores a virtual diary that supports the user in improving their lifestyle habits from a psychological perspective.

[0066] Input interfaces 34 / 44 can use, for example, USB (Universal Serial Bus) or Bluetooth (registered trademark) to connect to input devices 35 / 45. Input devices 35 / 45 can include, for example, keyboards, mice, or touch panels. Output interfaces 36 / 46 can be connected to output devices 37 / 47, for example, using HDMI (High-Definition Multimedia Interface) (registered trademark) or a LAN interface. Output devices 37 / 47 can be, for example, monitors or printers. Communication interfaces 38 / 48 are interfaces for communicating with external terminals over a network. Communication interfaces 38 / 48 are compatible with Ethernet®, Wi-Fi®, mobile communication systems, and other communication standards.

[0067] <Diary Table> Figure 7 illustrates an example of a diary table 430 stored in auxiliary storage device 43 (see Figure 6) as part of the patient application. In this embodiment, the diary table 430 is composed of two sub-diary tables 431 and 432. In Figure 7, subdiary table 431 is the diary table for characters whose indicators managed by the patient app are favorable, and subdiary table 432 is the diary table for characters whose indicators managed by the patient app are not favorable. Therefore, subdiary table 431 and subdiary table 432 record the daily lives and psychological states of characters whose lifestyle improvements after starting to use the patient app differ.

[0068] The diary entries recorded in subdiary table 431 are examples of the first diary, and the diary entries recorded in subdiary table 432 are examples of the second diary. The diaries recorded in sub-diary tables 431 and 432 are examples of diaries for reference. In this embodiment, the diaries for reference are provided for reference by users of the patient application.

[0069] An indicator is one or more behaviors or outcomes (or results) managed in the patient app, and is defined, for example, according to the purpose and goals of the patient app. For example, in a patient app for alcohol dependence, the amount of alcohol consumed per day is used as an indicator. In the case of alcohol dependence, behavior and outcome are aligned. For example, a patient app for hypertension might use "salt reduction" or "blood pressure" as indicators. Incidentally, salt reduction is a behavior, while blood pressure is an outcome. In the case of hypertension, behavior and outcome do not coincide.

[0070] "Good indicators" means that the indicators managed by the patient app are in a favorable state. Therefore, a character with "good indicators" is a character who is likely to succeed in improving their lifestyle. In other words, a character with "good indicators" is a high-achieving character. On the other hand, "the indicators are not good" means that the indicators managed by the patient app are in an unfavorable state. Therefore, characters with poor indicators are likely to fail to improve their lifestyle habits. In other words, characters with poor indicators are failing students.

[0071] In this embodiment, sub-diary tables 431 and 432 each contain diary entries for 91 days (i.e., 13 weeks). Needless to say, 91 days is just an example; the diary entries could be for a shorter or longer period. Basically, it depends on the treatment period assumed by the treatment app. However, this does not prevent recording diary entries for a period exceeding the treatment period. The 91-day diary is a fictional record of events and thoughts experienced in daily life by a character who is using a patient app to improve their lifestyle.

[0072] In this embodiment, the 91-day diary entries begin from the prescription date in the patient app (hereinafter referred to as the "reference date"). In other words, in this embodiment, the prescription date in the patient app is considered day 1. In this embodiment, the content of the diary, according to the number of days elapsed, is determined from the perspective of supporting the improvement of lifestyle habits by the user of the patient app. One perspective is to encourage the habit of recording daily activities through the patient app. Another perspective is to provide psychological support through the character's diary.

[0073] The characters here are virtual users who started improving their lifestyle habits using the same patient app on the same day as the user. In other words, the two characters are virtual companions who are using the patient app. The virtual companion's diary is made public to users of the patient app. In this embodiment, diaries with the same number of days elapsed since the prescription date in the patient app are presented for viewing. The prescription date in the patient app is an example of a reference date for the target user.

[0074] As mentioned earlier, the two characters show different levels of improvement in their lifestyle habits after starting to use the patient app. Therefore, by presenting both of their diaries, users can more easily find a diary that is similar to their own situation compared to when only one person's diary is presented. Finding a character whose situation is similar to your own means that another character's situation is far removed from your own. Even in that case, the diary of a character far removed from your own situation is not necessarily useless. Even if it's a fictional character, the presence of a companion in a similar situation can have the same effect as group therapy. For example, sharing the psychological state recorded in the diary provided can be expected to strengthen intrinsic motivation for treatment.

[0075] <Example of a sub-diary table> The following describes specific examples of subdiary tables 431 and 432 used in a patient app for alcohol dependence.

[0076] Figure 8 illustrates the first half of sub-diary table 431 for characters with good indicators managed by the patient app. Figure 9 illustrates the latter half of sub-diary table 431 for characters with good indicators managed by the patient app. The sub-diary table 431 shown in Figures 8 and 9 consists of "number of days elapsed," the "week" corresponding to the number of days elapsed, the "target value" per day, the "amount of alcohol" actually consumed, the "satisfaction level" at the time of drinking, the "impressions" which are the main body of the diary, and "advice" regarding the impressions. The sub-diary table 431 may also include information such as the day of the week corresponding to the number of days elapsed and the character's name.

[0077] Figures 8 and 9 show only excerpts of the sub-diary table 431 due to space limitations. Even in diaries of characters with good performance indicators, the data includes not only days without alcohol consumption but also days with heavy consumption. In this embodiment, a character with good indicators to manage is defined as female. For females, the target value for pure alcohol content is 20g or less. Therefore, the "target value" in subdiary table 431 is set to 20g. However, 20g is just one example. Below, I will describe the diary entries for 13 of the 91 days.

[0078] • Days elapsed: Day 1 The amount of alcohol consumed that day was 18g, and the level of satisfaction was "neutral." The "Thoughts" section records, "Starting to cut back on alcohol today. Thanks to talking with the doctor and feeling motivated, I was able to limit myself to just one glass of shochu and water as usual." In response to the thoughts, the advice recorded is, "Nice start! I'm happy for you." It appears to be the day the patient started using the app, as it contains positive feedback and advice that affirms that feedback.

[0079] • Days elapsed: Day 2 The amount of alcohol consumed on this day was 0g. The satisfaction level is left blank. Under "Thoughts," the entry reads, "Today is a night shift, so it's a day off from drinking. It's probably a good thing to have days when I can't drink due to circumstances." Additionally, the advice given in response to the thoughts reads, "Whatever the reason, a day off from drinking is wonderful!" This is a diary entry about days when the user did not consume alcohol due to work-related reasons. Regardless of the reason, the entry aims to demonstrate the usefulness of having alcohol-free days. Furthermore, the blank space for recording satisfaction is expected to reduce the user's psychological burden.

[0080] • Days elapsed: Day 3 The amount of alcohol consumed that day was 24g, and the satisfaction level was "good." The "Thoughts" section recorded was, "Today was my first time trying real-time recording. The one-word advice was fun." In response to the thoughts, the advice recorded was, "This is your first real-time recording!" This is a diary entry from a day when the user consumed more alcohol than their target limit. It illustrates that this occurred on the third day of using the patient app.

[0081] Even characters with good performance metrics may have days where they exceed their target values. This can help alleviate the psychological burden on users who are struggling because they have exceeded their target values. This day's diary also includes advice praising the real-time recording of drinking. Recording drinking in real time is an action that is expected to help prevent excessive alcohol consumption. It is hoped that this will be helpful to users.

[0082] • Days elapsed: Day 8 The amount of alcohol consumed that day was 36g, and the level of satisfaction was "good." The "Thoughts" section records, "I drank the wine I bought as a souvenir from the Italian restaurant I went to yesterday, and it was so delicious that I drank three glasses." The advice given in response to the thoughts is, "It was delicious, but there was too much of it." On this particular day, the user consumed significantly more alcohol than their target amount. Therefore, the advice, while empathizing with the user's feelings, also points out the objective fact that "the quantity was excessive." This makes it easier for the user to calmly accept the advice while still empathizing with the feelings of a character whose managed metrics are performing well.

[0083] • Days elapsed: Day 9 The amount of alcohol consumed that day was 24g, and the level of satisfaction was "good." The "Thoughts" section recorded was, "With one glass of wine, I'm still well within my goal, but with two glasses, I'd be slightly over. It's a dilemma." In response to the thoughts, the advice recorded was, "You're being mindful of your target number of drinks!" On this day too, the user consumed more alcohol than their target amount. This is an example of exceeding the target amount for two consecutive days. The comments describe the worries that any user trying to reduce their alcohol intake would likely experience, and are expected to resonate with other users. Furthermore, the content conveys to the reader the importance of being mindful of the number of drinks consumed while drinking.

[0084] • Days elapsed: 30 days The amount of alcohol consumed that day was 20g, and the level of satisfaction was "good." The "Feedback" section records, "Second consultation. I was praised for various efforts after they looked at my diary. I want to increase my achievements a little more before the next consultation." In addition, the advice given in response to the feedback is, "Your motivation has increased!" This is the day the user is scheduled to have their second medical checkup. Although the amount of alcohol consumed on this day is within the target range, the drinking habit itself continues. This content is likely to resonate with users who are working to reduce or abstain from alcohol. Also, although omitted in Figure 8, it is possible to inform the user that they will be praised for carrying out the efforts recorded in their diary up to the previous day.

[0085] • Days elapsed: 40 days On this day, the amount of alcohol consumed was 40g, and the level of satisfaction was "good." The "Thoughts" section recorded, "Perhaps because I told my colleagues about cutting back on alcohol, they now occasionally encourage me not to drink too much." In addition, the advice given in response to the thoughts was, "Good things happen when you talk about your challenge with those around you!" On this day, the amount of alcohol consumed was twice the target amount. On the other hand, it is noted that the person is working to reduce their alcohol consumption, and the advice given to colleagues is positively described. In this diary entry, it is recommended to inform drinking buddies about efforts to reduce alcohol consumption.

[0086] • Days elapsed: 60 days The amount of alcohol consumed that day was 20g, and the level of satisfaction was "good." The "Feedback" section records, "I achieved more and was praised. Also, when I talked about my own discoveries, the doctor was impressed." In addition, the advice given in response to the feedback was, "I'm glad it was a good consultation!" This is the day the user is scheduled to have a doctor's appointment. Two months have already passed. Reading this day's diary entry, the user will be reminded that they will be praised by their doctor if they continue to achieve their target values.

[0087] • Days elapsed: 79 days The amount of alcohol consumed that day was 20g, and the level of satisfaction was "good." The "Thoughts" section recorded, "Lately, I feel like I've only been pressing the right side of the face when checking in and checking out. It makes me feel motivated and I'm in good shape." In addition, the advice given in response to the thoughts was, "Keeping a record of changes in my condition makes it easier to look back on!" Here, "check-in" refers to recording information such as your physical condition upon waking up in the patient app, and "check-out" refers to recording information such as your physical condition before going to sleep in the patient app. Also, "the right side of the face" indicates a state of good physical condition. Incidentally, if you are feeling unwell, you will operate the left side of the face. Therefore, this diary entry indicates that physical condition, stress levels, and sleep were all good. It also suggests that good alcohol management leads to improved physical condition.

[0088] • Days elapsed: 80 days The amount of alcohol consumed on this day was 0g, and the satisfaction level is left blank. Under "Thoughts," the user recorded, "I haven't had a day off from drinking recently, so today is a day off. I just now realized that there's a liver character on my home screen when I take a day off from drinking." In addition, the user recorded the advice, "Keeping a record of changes in your condition makes it easier to look back on!" This diary reveals that even individuals with good performance indicators don't necessarily have alcohol-free days every day.

[0089] • Days elapsed: 89th day The amount of alcohol consumed that day was 20g, and the level of satisfaction was "good." The "Thoughts" section recorded: "Tomorrow is finally the last appointment. I've done all my homework. I achieved my goals and learned a lot!" In addition, the advice given in response to the thoughts was: "It seems like you've had a wonderful three months!" The content is exemplary because it focuses on characters with good performance metrics.

[0090] • Number of days elapsed: 90 days On this day, the amount of alcohol consumed was 20g, and the satisfaction level was "good." The "Thoughts" section reads, "My teacher praised me a lot! Not only has my drinking habits changed in three months, but my lifestyle has changed too! I'll keep recording with the app without letting my guard down." In response to the thoughts, the advice recorded is, "The important thing is to keep going! You're absolutely right!" This content reaffirms the importance of continuously managing the amount of alcohol consumed.

[0091] • Days elapsed: 91 days This is the final day the diary entries are presented. The amount of alcohol consumed on this day is 0g, and the satisfaction level is blank. Under "Thoughts," it is recorded: "It's the last Sunday of the week. I have work tomorrow, so when I woke up this morning I decided to make it an alcohol-free day, and I was able to do just that!" Also, as advice for the thoughts, it is recorded: "It's a good idea to decide on your plans in the morning!" The diary entries are befitting of an exemplary character.

[0092] <Specific example of a sub-diary table for a character whose managed metrics are not performing well> Figure 10 illustrates the first half of subdiary table 432 for characters whose indicators managed by the patient app are not favorable. Figure 11 illustrates the latter half of subdiary table 432 for characters whose indicators managed by the patient app are not favorable.

[0093] The sub-diary table 432 shown in Figures 10 and 11 also consists of "number of days elapsed," the "week" corresponding to the number of days elapsed, the "target value" per day, the "amount of alcohol" actually consumed, the "satisfaction level" at the time of drinking, the "impressions" which are the main body of the diary, and "advice" regarding the impressions. In the case of the sub-diary table 432, information such as the day of the week corresponding to the number of days elapsed and the character name may also be included.

[0094] Figures 10 and 11 also show excerpts of the sub-diary table 432 due to space limitations. Even for diaries of characters whose managed indicators are not favorable, the entries include not only days when alcohol is consumed, but also periods of consecutive alcohol-free days. In this embodiment, a character whose indicators are not favorable is defined as male. For males, the target value for pure alcohol intake is 40g or less. However, the "target value" in subdiary table 432 is set to 60g in relation to the amount of alcohol the character has consumed at the time of treatment. In the following sections, as with Figures 8 and 9, we will describe the diary entries for 13 days out of the 91 days.

[0095] • Days elapsed: Day 1 The amount of alcohol consumed that day was 88g, and the level of satisfaction was "good." The "Thoughts" section recorded: "I drank as usual to motivate myself to work hard from tomorrow. My doctor also said we should gradually reduce it, so it's okay." In addition, the advice given in response to the thoughts was: "First of all, thank you for recording your first record!" The character's performance indicators are apparently not good, as evidenced by the fact that alcohol consumption exceeding the target amount has been recorded since the start of using the patient app. However, this content is likely to resonate with users who regularly consume large amounts of alcohol. On the other hand, the app also includes advice that supports recording alcohol consumption.

[0096] • Days elapsed: Day 2 The amount of alcohol consumed that day was 62g, and the level of satisfaction was "neutral." The "Thoughts" section recorded was, "I tried having one less drink than usual. I think I wanted one more at the end after all." In response to the thoughts, the advice recorded was, "You tried cutting back by one drink. Good attempt!" The amount of alcohol consumed that day was almost exactly in line with the target value. In addition, the user recorded in their comments that they "drank one less than usual." Therefore, the advice given also praised their efforts.

[0097] • Days elapsed: Day 3 The amount of alcohol consumed that day was 55g, and the level of satisfaction was "neutral." The "Thoughts" section records, "I managed to achieve my goal today by replacing one drink with a non-alcoholic one. But I still feel somewhat unsatisfied." In response to the thoughts, the advice recorded is, "Non-alcoholic drinks are great!" This day's diary entry shows an example where even characters with poor performance metrics can achieve their target values. It also illustrates an effective technique for reducing alcohol consumption: switching to non-alcoholic beverages. This is a useful action for users who have begun efforts to reduce their alcohol intake.

[0098] • Days elapsed: Day 8 The amount of alcohol consumed that day was 62g, and the level of satisfaction was "bad." The "Thoughts" section records, "I was feeling terrible this morning from drinking every day, so I intended to take a break from drinking today, but... I ended up drinking anyway." The advice given in response to the thoughts is, "Regret only happens when you want to change!" The diary entry for that day contains a confession of regret for drinking despite intending to have a day off from drinking. This is a situation that every user prescribed the patient app will experience. Therefore, it is a story that many users will relate to, and at the same time, it is expected to encourage other users to try to have a day off from drinking by using the companion's experience as a cautionary tale. Accordingly, the advice given is also affirming the regret and empathizing with the character's feelings.

[0099] • Days elapsed: Day 9 The amount of alcohol consumed that day was 81g, and the level of satisfaction was "good." The "Thoughts" section states, "I wanted to take a break from drinking today, but my boss invited me to a drinking party, so I had no choice." The advice given in response to the thoughts is, "Is an invitation from your boss an unavoidable trigger?" This day is the day after the confession. It's a situation that any user who has started treatment using the patient app might experience. Also, the amount of alcohol consumed has far exceeded the target amount. For this reason, the advice is also geared towards encouraging introspection.

[0100] • Days elapsed: 30 days The amount of alcohol consumed on this day was 0g, and the satisfaction level is blank. The "Thoughts" section records, "Second consultation. I was told that I'm the type of person who can't stop drinking once I start, so I should try to find something to enjoy other than alcohol." In addition, the advice given in response to the thoughts is, "Instead of trying to reduce alcohol, try to increase other things to enjoy!" In this character's case, alcohol consumption is recorded, and there are also records of alcohol-free days, but the amount of alcohol consumed when drinking tends to be high. Therefore, the content suggests finding "enjoyment other than alcohol" by using the characters' opinions. The advice given is along the same lines. The feedback from that day serves as advice for users who have a low success rate in reducing their alcohol consumption.

[0101] • Days elapsed: 40 days The amount of alcohol consumed that day was 106g, and the level of satisfaction was "good." The "Thoughts" section recorded: "It was a team drinking party. My subordinates kept pouring, so I ended up drinking a lot. I couldn't really bring myself to say that I was trying to cut back on drinking." In response to the thoughts, the advice recorded was: "At what point do you think you could confide that you're cutting back on drinking?"

[0102] On this day, the amount of alcohol consumed was about twice the target amount, similar to the other characters. However, while the other characters told Etano that they were working to reduce their alcohol consumption, this character was unable to confide in him about their own efforts to cut back. Furthermore, the advice given that day doesn't simply encourage telling colleagues about your efforts to reduce alcohol consumption, but rather prompts you to consider the conditions under which you should confide in them. This diary entry provides users with an opportunity to reaffirm the importance of telling those they drink with about their alcohol consumption.

[0103] • Days elapsed: 60 days On this day, the amount of alcohol consumed was 60g, and the level of satisfaction was "neutral." The "Thoughts" section records, "The doctor suggested that it might be better to abstain from alcohol altogether, and that reducing it can sometimes be more difficult. I replied that I would continue to reduce my alcohol intake for another month." In response to the thoughts, the advice recorded is, "The doctor seems to be reading Taro's diary very carefully." This character's name is "Taro." As mentioned in the previous diary entry, Taro does have alcohol-free days, but he tends to consume large amounts of alcohol at once. Therefore, as indicated by the doctor's comments in the review, abstinence would be better for this type of user.

[0104] • Days elapsed: 79 days The amount of alcohol consumed on this day was 0g, and "good" was recorded for satisfaction. The "Thoughts" section states, "I made it a day off from drinking, remembering how bad I felt yesterday." In addition, the advice given in response to the thoughts is, "The unpleasant feeling caused by alcohol acted as a stopper for drinking." Although not shown in Figure 11, the previous day was a day off from drinking. However, he had been drinking for four consecutive days leading up to that, and his diary entry for the previous day reads, "I went to work in the worst mood because I had been drinking every day. I got irritated by a subordinate's mistake and now I hate myself."

[0105] In short, the report states that his health did not recover after just one day of abstinence from alcohol due to the effects of consuming large amounts of alcohol on consecutive days. Taro is aware that his failure to reduce his alcohol intake has negatively impacted his health. Therefore, the advice given doesn't praise taking alcohol-free days, but rather indirectly points out the negative effects of drinking. This diary may be uncomfortable for users who recognize similarities with Taro, but it is hoped that it will motivate them to improve their lifestyle habits.

[0106] • Days elapsed: 80 days The amount of alcohol consumed that day was 0g, and the satisfaction level is blank. Under "Thoughts," it is recorded that "I distract myself from the urge to drink by jogging. Surprisingly, I've been able to keep it up, and I've gotten much stronger." Also, as advice in response to the thoughts, it is recorded that "Three consecutive days without alcohol! Taro is amazing after all!" This diary entry exemplifies jogging as an enjoyable pastime other than drinking. The diary highlights the importance of having other forms of enjoyment besides alcohol.

[0107] • Days elapsed: 89th day The amount of alcohol consumed that day was 0g, and the satisfaction level was recorded as "good." The "Thoughts" section reads, "A drinking party on the weekend. I decided not to drink because I wasn't feeling very well. I realized that it might be surprisingly manageable if I don't drink a single drop." In addition, the advice given in response to the thoughts reads, "So you used the 'not feeling well' method!" Taro is a character whose performance indicators are not good, but there is a record of his success in that he managed to avoid drinking a single drop of alcohol at a drinking party due to his health. Unlike other characters, not all users are successful in controlling their alcohol consumption, so this diary entry can serve as a hint for users who find themselves drinking alcohol against their will.

[0108] • Number of days elapsed: 90 days The amount of alcohol consumed that day was 0g, and the satisfaction level was recorded as "good." The "Thoughts" section reads, "After talking with the doctor, I decided to quit drinking for the sake of my health and my family. I've decided that I feel better when I don't drink." In response to the thoughts, the advice recorded is, "You've realized that not drinking isn't painful, and that you can feel better when you don't drink!" This day's diary entry includes advice for users who are struggling to control their alcohol intake even with treatment using the patient app. For users whose treatment goal has already been shifted to "abstinence," this diary entry also serves as an opportunity to reaffirm the meaning of aiming for abstinence.

[0109] • Days elapsed: 91 days This is the final day the diary entries are presented. The alcohol intake for this day is 0g, and the satisfaction level is blank. Under "Thoughts," it is recorded: "I managed to get through today without drinking. I realized that deciding not to drink at all on days like this suits me better than trying to drink less." In addition, the advice given in response to the thoughts is: "You have chosen a method that suits you. Excellent!" This day's diary entry recommends abstinence for users who struggle to control their alcohol intake. The advice praises the choice to abstain and encourages continued abstinence.

[0110] <Processing Sequence> Figure 12 is a diagram illustrating an example of a processing sequence in an embodiment. The processing sequence shown in Figure 12 is executed through a patient application installed on the patient terminal 40. In Figure 12, the symbol S represents a step. The processing sequence shown in Figure 12 assumes a patient application for alcohol dependence. Therefore, the patient application screen described later is also customized for alcohol dependence. The processing operations shown in Figure 12 are realized through the execution of a patient application by the processor 41 (see Figure 6) of the patient terminal 40. In the following explanation, the patient application will be described as the implementing entity.

[0111] <Step 101> First, the patient app determines whether or not the required items have been entered. In this embodiment, the designated item is a record of alcohol consumption. The record of alcohol consumption includes records of drinking times and records of alcohol-free days. In records of drinking, for example, "information before drinking" and "information during or after drinking" are recorded.

[0112] Prior to drinking, information such as the level of desire to drink, the location where drinking will take place, the people drinking with, and the emotions before drinking will be recorded. Information recorded during or after drinking includes, for example, the location of drinking, who you are drinking with, the type of alcohol, the amount of alcohol consumed, the duration of your stay, your level of satisfaction, and your thoughts after drinking. These thoughts correspond to the main text of the diary mentioned earlier.

[0113] In addition, records of alcohol-free days include, for example, the level of craving for alcohol, the triggers for the craving (person, place, object, situation), and feelings about the alcohol-free day. If the input does not meet the specified criteria, a negative result is obtained in step 101. In this case, the patient app either repeats the determination in step 101 or performs an unillustrated processing action. On the other hand, if the input is for a predetermined item, a positive result is obtained in step 101. In this case, the patient app proceeds to step 102. The input of a predetermined item here is an example of detecting the recording of health-related data.

[0114] <Step 102> The patient application records the input content as patient application data 230C (see Figure 5). Incidentally, the patient application data 230C is stored in the semiconductor memory 42 (see Figure 6) and the auxiliary storage device 43 (see Figure 6).

[0115] <Step 103> The patient app uploads patient app data 230C to the PDT server 20 (see Figure 1). However, the upload of patient app data 230C is performed only if the patient app remains logged into the PDT server 20. Therefore, if the patient app is not logged into the PDT server 20 at the time of step 103 (i.e., logged out), step 103 is skipped. Incidentally, if the patient app is not logged into the PDT server 20 at step 103, the upload of patient app data 230C will be performed when the patient app logs into the PDT server 20 again.

[0116] <Step 104> The patient app adds a button to view the diary to the home screen. In this embodiment, the diary viewing button is not displayed on the home screen while the predetermined items are not entered. Please note that the display of the diary viewing button is reset daily. Therefore, even if the viewing button appears on the home screen after the input of the required items is detected, it will disappear from the home screen after, for example, 27 hours have passed.

[0117] <Step 105> The patient app determines whether or not the user has pressed the button to view their diary. For example, if no operation of the view button is detected after a predetermined time has elapsed, or if an operation other than the view button is detected, a negative result is obtained in step 105. In this case, the patient app returns to step 101. On the other hand, if the view button is detected to have been pressed, a positive result is obtained in step 105. In this case, the patient app proceeds to step 106.

[0118] <Step 106> The patient app retrieves the user's reference date. In this embodiment, this is the prescription date in the patient app. <Step 107> The patient app retrieves the number of days that have passed from the reference date to the present (i.e., elapsed days). In this embodiment, the reference date is set as day 1.

[0119] <Step 108> The patient app determines whether the number of days elapsed is within a threshold. The threshold is, for example, the number of days recorded in the diary table 430 (see Figure 7). In this embodiment, the threshold is "91". If the number of days elapsed is greater than the threshold (e.g., 91 days), a negative result is obtained in step 108. In this case, the patient app returns to step 101.

[0120] On the other hand, if the number of days elapsed is within a threshold (e.g., 91 days), a positive result is obtained in step 109. In this case, the patient app proceeds to step 109. In other words, the patient app proceeds to step 109 and presents the diary as long as the number of days elapsed is within the threshold, but stops presenting the diary when the number of days elapsed exceeds the threshold.

[0121] <Step 109> The patient app reads and displays reference diary entries corresponding to the number of days elapsed. These reference diary entries are those recorded in diary table 430. For example, if 5 days have passed, the diary entries for day 5 from subdiary table 431 (see Figure 7) and day 5 from subdiary table 432 (see Figure 7) will be displayed.

[0122] <Example of diary display on the patient app screen> The following describes an example of how to display a diary on the patient app screen. Figure 13 illustrates the "Home" screens 500 and 510 of the patient app. The "Home" screen 500 is the screen before entering the drinking record, and the "Home" screen 510 is the screen after entering the drinking record. The "Home" screen 500 has a message field 501 and selection buttons 502 and 503. In Figure 13, the message field 501 reads "Mr. A, let's decide what to do today," prompting user A to take action.

[0123] Incidentally, selection button 502 is for selecting "Decide what to do today," and selection button 503 is for selecting "Record yesterday's drinking / alcohol-free days." The "drinking / alcohol-free days record" here corresponds to the aforementioned drinking record. In this embodiment, it is assumed that the selection button 503 is selected. If there is a record of drinking or a day off from drinking, the "Home" screen 510 is displayed.

[0124] The "Home" screen 510 has a message field 511 and selection buttons 512 and 513. In Figure 13, the message field 511 reads, "Thank you for entering your drinking record. Let's review yesterday's drinking as well." Incidentally, selection button 512 is for selecting "Reflect on yesterday," and selection button 513 is for selecting "View Pia's Diary." Here, "Pia" means "friends," and "Pia's Diary" refers to the diaries in sub-diary tables 431 and 432. The selection button 513 is displayed only if a positive result is obtained in step 101 (see Figure 12). In this embodiment, it is assumed that the selection button 513 is selected.

[0125] Figure 14 is a diagram illustrating screens 520 and 530 of the "Pia Diary" app. The "Pia Diary" screen 520 has a message field 521, a "back" button 522, and a "forward" button 523. In Figure 14, message box 521 reads, "Taro, let's see what kind of records Hanako has made." "Taro" is the name of a character whose managed indicators are not good, and "Hanako" is the name of a character whose managed indicators are good. In other words, both "Taro" and "Hanako" are fictional characters.

[0126] The "Back" button 522 is used to return to the "Home" screen 510. On the other hand, the "Forward" button 523 is used to proceed to viewing the diary. When the "Next" button 523 is pressed, the "Pia Diary" screen 530 is displayed. The "Pia Diary" screen 530 is an image that displays "Taro-san's" virtual diary. The "Pia Diary" screen 530 has a diary field 531, a "back" button 532, and a "forward" button 533. The "Back" button 532 is used to return to the "Pia Diary" screen 520. On the other hand, the "Forward" button 533 is used to advance to the "Pia Diary" screen 540.

[0127] On the "Pia Diary" screen 530, the diary section 531 displays the icon for "Taro-san" 531A and the advisor icon 531B. The diary entry 531 reads the diary of "Taro" corresponding to the number of days elapsed for the user using the patient app (for example, person A). For example, if 15 days have passed since person A received the prescription for the patient app, the diary entry for day 15 from subdiary table 431 (see Figure 8) will be read. The diary section 531 consists of an alcohol content display section 531C, a satisfaction level display section 531D, a comments display section 531E, and an advice display section 531F.

[0128] The alcohol quantity display section 531C shows the amount of alcohol consumed by "Taro" on the corresponding number of days elapsed, with the numerator being the amount of alcohol consumed and the denominator being the target value. In Figure 14, the amount of alcohol is 60g in all cases. The satisfaction level display unit 531D shows the satisfaction level information from the sub-diary table 431 (see Figure 8). In Figure 14, the satisfaction level when drinking is "average".

[0129] The feedback display unit 531E shows the feedback of "Taro-san," who is not managing his alcohol intake well. In Figure 14, it displays, "I couldn't cut down on my alcohol and my wife hid my beer. I had to resist the urge to have one more drink at the end, so it left a bad taste in my mouth." This feedback expresses the struggles of "Taro-san" who is having difficulty reducing his alcohol intake. The advice display unit 531F shows advice from the advisor to "Taro-san". In Figure 14, it displays, "Your wife is worried about you, but you feel something is lacking."

[0130] The advice given here is not meant to scold "Taro-san," but rather to accept his struggles. Therefore, even users who feel a personal connection to "Taro-san" will find reading "Pia Diary" less painful. On the other hand, the advice does not endorse Taro's drinking habits. Therefore, it is hoped that users who feel a personal connection to Taro will feel a sense of camaraderie with him and be motivated to reduce their alcohol consumption together.

[0131] When the "Next" button 533 is pressed, the screen proceeds to the "Pia Diary" screen 540. Figure 15 is a diagram illustrating screens 540 and 550 of the "Pia Diary" app. The "Pia Diary" screen 540 is a screen that displays Hanako's virtual diary. The "Pia Diary" screen 540 has a diary field 541, a "back" button 542, and a "forward" button 543. The "Back" button 542 is used to return to the "Pia Diary" screen 530. On the other hand, the "Forward" button 543 is used to advance to the "Pia Diary" screen 550.

[0132] On the "Pia Diary" screen 540, the diary section 541 displays the "Hanako-san" icon 541A and the advisor icon 541B. In diary entry 541, just like with "Taro-san," the diary entries of "Hanako-san" corresponding to the number of days elapsed for the user using the patient app (in this case, person A) are read. The diary section 541 consists of an alcohol content display section 541C, a satisfaction level display section 541D, a comments display section 541E, and an advice display section 541F.

[0133] The alcohol content display section 541C shows the amount of alcohol consumed by "Hanako-san" on the corresponding number of days elapsed, with the numerator being the amount of alcohol consumed and the denominator being the target value. In the case of Figure 15, the target value is 20g, and the amount of alcohol consumed by "Hanako-san" is 12g. The satisfaction level display unit 541D shows the satisfaction level information from the sub-diary table 432 (see Figure 10). In Figure 15, the satisfaction level when drinking is "average".

[0134] The feedback display unit 541E shows the feedback of "Hanako-san," who has good control over her alcohol intake. In Figure 15, it displays, "Just one drink with a friend at lunch. I felt like having a little drink because work was depressing, but I should probably finish my app homework soon." The comments here mention that while she was in a psychological state where she was likely to consume more alcohol, Hanako realized her own feelings and limited herself to just one drink.

[0135] The advice display unit 541F shows advice from the advisor to "Hanako-san." In Figure 15, it displays, "She became aware of her craving and decided not to drink." The advice here explains what enabled Hanako to reduce her alcohol consumption. This advice is also designed to provide hints for users who relate to Taro to help them reduce their alcohol intake.

[0136] When the "Next" button 543 is pressed, the screen proceeds to the "Pia Diary" screen 550. Screen 550 of the "Pia Diary" displays a message to users who have finished reading the diaries of "Taro-san" and "Hanako-san". The "Pia Diary" screen 550 has a message field 551, a "back" button 552, and a "forward" button 553. The "Back" button 552 is used to return to the "Pia Diary" screen 540. On the other hand, the "Forward" button 553 is used to proceed to the "Home" screen (not shown).

[0137] In Figure 15, message field 551 reads, "Thank you. It's wonderful that the record is continuing." The "Pia Diary" screen 550 will appear after you have finished viewing the diaries of "Taro-san" and "Hanako-san." Furthermore, even if you have recorded drinking or a day off from drinking, you can choose not to read the "Pia Diary."

[0138] However, "Pia Diary" is expected to have the effect of supporting users from a psychological perspective by providing them with a record of their daily lives and psychological states, as documented in the diaries of companions who, like the users, are working to improve their alcohol-related illnesses. For this reason, message field 551 includes an expression of gratitude for reading the diaries of "Taro-san" and "Hanako-san," a measure taken to encourage continued reading of "Pia Diary." Furthermore, access to the "Pia Diary" is only possible after recording drinking and alcohol-free days. Therefore, it includes text praising the continued recording of drinking and alcohol-free days.

[0139] <Summary> In this embodiment, when the patient app detects that the user has recorded drinking or a day of abstinence from alcohol, the patient app presents the user with a "Pia Diary" corresponding to the number of days elapsed. The content of the presented "Pia Diary" matches the number of days elapsed since the user was prescribed the patient app. Therefore, the content of the "Pia Diary" is perceived as that of a companion in the same situation as the current user. Furthermore, the content of the "Pia Diary," which expresses the actions and psychological state of the companion, is set to have a high degree of commonality with the worries and other issues the user is experiencing. Therefore, the user can vicariously experience the actions and psychological state of the companion through the content of the "Pia Diary."

[0140] As a result, users can be made to feel as if they are participating in group therapy. In other words, it becomes possible to support users in improving their lifestyle habits from a psychological perspective. Furthermore, the characters in "Pia Diary" include not only those who are successfully reducing their alcohol consumption, but also those who are not. Therefore, even users whose progress in reducing alcohol consumption is not going smoothly can easily empathize with the diaries of characters who are not succeeding, making them more likely to continue reading "Pia Diary."

[0141] Furthermore, since viewing "Pia Diary" requires recording drinking or alcohol-free days, it becomes possible to encourage patients to make recording drinking or alcohol-free days a habit through the patient app. Incidentally, continuing to record alcohol consumption or alcohol-free days through a patient app is expected to have the effect of making patients more conscious of their daily alcohol intake. As a result, compared to cases where patients do not record alcohol consumption or alcohol-free days using a patient app, they are more likely to continue their efforts to reduce their alcohol intake.

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

[0143] (2) The processor in the embodiments described above refers to a processor in a broad sense, and includes not only general-purpose processors (e.g., CPUs) but also specialized processors (e.g., GPUs (=Graphical Processing Units), ASICs (=Application Specific Integrated Circuits), FPGAs (=Field Programmable Gate Arrays), programmable logic devices, etc.). Furthermore, the processor operations in each of the embodiments described above are not limited to a single processor, but may be performed collaboratively by multiple processors or multiple CPU cores. Also, the order in which each operation is executed in the processor is not limited to the order described above, but may be changed individually.

[0144] (3) In the embodiments described above, the prescription date in the patient app was used as an example of the reference date, but the invention is not limited to this. For example, the reference date could be the day the patient app was downloaded. This is because users can activate the patient app within three days of the prescription date, and do not necessarily start using the patient app on the prescription date. On the other hand, many users install and activate the patient app on the same day they download it. Therefore, by using the day the patient app was downloaded as the reference date, it is possible to eliminate or minimize the discrepancy between the content of the "Pia Diary" presented to the user and the number of days the user has actually used the patient app.

[0145] For example, the reference date could be the date the patient app was installed on the user's device 40 (see Figure 1). As mentioned above, there may be a discrepancy between the prescription date and the date the patient app was installed. However, by using the date the user installed the patient app on the user's device 40 as the reference date, the discrepancy between the content of the "Pia Diary" presented to the user and the number of days the user has used the patient app can be eliminated or reduced.

[0146] For example, the reference date could be the date the patient started using the patient app. As mentioned earlier, there may be a discrepancy between the prescription date and the date the patient started using the patient app. However, by using the date the user started using the patient app as the reference date, the discrepancy between the content of the "Pia Diary" presented to the user and the number of days the user has used the patient app can be eliminated or reduced. The date the user started using the patient app is defined as the date on which a record for an indicator managed by the patient app (e.g., alcohol amount) is detected. Incidentally, records of alcohol-free days are treated as records with an alcohol amount of 0.

[0147] For example, the reference date could be the date the user began their efforts to improve their lifestyle habits. This reference date allows for situations where the start date of using the patient app and the start date of lifestyle improvement efforts do not necessarily coincide. For example, it may be preferable to consider the first day of lifestyle improvement as the day after the patient has completed acquiring knowledge about their disease through the learning program in the prescribed patient app. In cases of nicotine addiction, for instance, behavioral therapy cannot begin until the learning program is completed.

[0148] However, in this embodiment, the content of the diary presented is determined according to the number of days since lifestyle improvements were started. Therefore, depending on the disease the patient app supports, the reference date will be the actual date on which lifestyle improvements were started. The actual date on which lifestyle improvements were started will be, for example, the date of the first operation of the "Practice" button used to record the practice.

[0149] (4) In the embodiments described above, the "Pia Diary" screen consists of text (impressions, advice), numbers, and icons, but the way in which the "Pia Diary" is presented is not limited to these. For example, the "Pia Diary" may be presented as a video or as audio.

[0150] (5) In the above-described embodiment, the user is presented with diaries of characters whose indicators managed by the patient app (e.g., alcohol consumption) are good and diaries of characters whose indicators managed by the patient app are not good, as "Pia Diaries". However, it is also acceptable to only show the diaries of characters whose metrics managed by the patient app are good, or to only show the diaries of characters whose metrics managed by the patient app are not good. Additionally, depending on the user's progress in improving their lifestyle, the character's diary may be displayed. Additionally, the presentation of diaries from characters with good performance indicators managed by the patient app may be randomly switched between those from characters with poor performance indicators managed by the patient app.

[0151] (6) In the above-described embodiment, the user is presented with diaries of characters whose indicators managed by the patient app (e.g., alcohol consumption) are good and diaries of characters whose indicators managed by the patient app are not good, as "Pia Diaries". However, the diaries of the characters that make up "Pia Diary" are not limited to just two types. For example, it is acceptable to present three or more types of diaries, including one for a character that is neither particularly good nor bad.

[0152] (7) In the above-described embodiment, the diaries of the fictional characters "Taro-san" and "Hanako-san" were presented as "Pia Diary". However, other users may present their diaries and other information recorded through the patient app. However, when using other users' diaries and other information as "reference diaries," personal information must be removed to ensure it is not identifiable.

[0153] (8) The above-described embodiment explained the case in which the diary to be presented is prepared in advance. However, it is also possible to provide the user's input information from the reference date to the present to a generating AI (=Artificial Intelligence) and have it generate a diary to present to the user.

[0154] (9) In the above-described embodiment, the "Pia Diary" is presented as a trigger when the operation of the selection button 513 (see Figure 13) as a viewing button is detected. However, the "Pia Diary" may also be presented as a trigger when the input of a drinking record (including a record of alcohol-free days) is made. In this case, operation of the viewing button is unnecessary, and the "Pia Diary" is presented to the user immediately after the drinking record.

[0155] (10) The diary table 430 in the above embodiment consists of sub-diary tables 431 and 432 in which 91 days' worth of diaries are recorded, and reads and presents the diary for the day corresponding to the number of days that have passed from the reference date to the present. However, the diary entries presented may be prepared in increments of several days, for example. For instance, the diary content may be changed every two days, or every three days. In this case, the number of diary entries recorded in sub-diary tables 431 and 432 will be half, one-third, etc., compared to the embodiment. Additionally, a dedicated diary may be prepared for days when medical appointments or other appointments are scheduled. In this case, the patient app simply needs to select the corresponding diary entry based on the number of days elapsed to date.

[0156] (11) In the above embodiment, the presentation of "Pia Diary" is stopped when the number of elapsed days exceeds a threshold (for example, 91 days). However, a system that does not set an upper limit on the period during which "Pia Diary" is presented would also be acceptable.

[0157] (12) In the above-described embodiment, the reference date is determined based on the premise of a patient app prescribed by a doctor or the like for the treatment of alcohol dependence. However, it is possible that a patient app may inherit data from another patient app or from a non-patient app. For example, due to moving or other reasons, a user may change the patient app they use for treatment, and the patient app data recorded in the previous patient app may be inherited by the next patient app. Also, the restrictions of the non-patient app mode, which limit functionality, may be lifted, and the app mode may switch to patient app mode.

[0158] In these cases, the content of the diary presented may be determined by inheriting the reference date from other patient apps or non-patient apps (hereinafter referred to as "other reference date" or "previous reference date"). The other reference date or previous reference date is an example of a second reference date. For example, if the current date is July 20th, the prescription date in the current patient app is July 10th, and the previous reference date is July 1st, then July 1st will be used as the reference date for the current patient app.

[0159] (13) In the above embodiment, "Pia Diary" is presented as a function of the patient app prescribed to the user. However, the presentation of "Pia Diary" may also be presented to the patient terminal 40 as a function of the PDT server 20 (see Figure 1). In other words, the PDT server 20 may present "Pia Diary" as one of its cloud services. Figure 16 is a diagram illustrating the presentation process of "Pia Diary" by the PDT server 20. In Figure 16, parts corresponding to those in Figure 12 are indicated with corresponding numerals.

[0160] <Step 201> Patients input information such as their daily alcohol intake by following the instructions on the patient app's interface. For example, patients input daily reflections, behavioral goals, target values, outpatient records, and medication records. The patient terminal 40 records the entered information as patient application data. The patient application data may also include data processed from this data. Incidentally, the processing of the patient application data is performed by the patient application.

[0161] <Step 202> At predetermined times, the patient terminal 40 uploads patient application data. One predetermined time is when new data is recorded or updated. This upload is performed when the patient application remains logged into the PDT server 20. Another predetermined time is when the patient logs into the PDT server 20. This upload is performed when the patient application is logged out of the PDT server 20 and then logs back into the PDT server 20.

[0162] <Step 203> The PDT server 20 stores the uploaded patient application data. This patient application data constitutes a part of the patient data 230 (see Figure 5). <Step 204> In the case of Figure 16, the PDT server 20 determines whether the uploaded patient application data contains predetermined items. Similar to the embodiment described above, if the patient application is an application for alcohol dependence, the predetermined items are drinking records.

[0163] <Step 205> The PDT server 20 retrieves the user's reference date. <Step 107> Next, the PDT server 20 retrieves the number of days that have elapsed from the reference date to the present (i.e., the number of days elapsed).

[0164] <Step 108> Next, the PDT server 20 determines whether the elapsed days are within a threshold. The threshold is, for example, the number of days in the diary stored in the diary table 430 (see Figure 7). If the number of elapsed days exceeds the threshold, a negative result is obtained in step 108. In this case, the PDT server 20 skips step 206. On the other hand, if the number of elapsed days is within the threshold, a positive result is obtained in step 108. In this case, the PDT server 20 proceeds to step 206. <Step 206> The PDT server 20 reads a reference diary corresponding to the number of days elapsed and displays it on the patient terminal 40.

[0165] (14) In the above-described embodiment, a patient application for alcohol dependence was explained. However, an app that provides a diary display function based on the number of days elapsed can be a patient app for other diseases, or a non-patient app. Incidentally, the other diseases can be lifestyle-related diseases or non-lifestyle-related diseases. Lifestyle-related diseases include, for example, hypertension, dyslipidemia, chronic heart failure, hyperuricemia, diabetes, NASH, 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.

[0166] (15) In the embodiments described above, patient apps and healthcare apps are assumed to be used as apps for recording health-related data. However, the type of app used to record health-related data is not restricted. For example, it could be a diary app, a photo app, or an audio app.

[0167] <Summary> An example of the disclosure described in the above-mentioned embodiment is shown below. (((1))) An information processing device having a processor, the processor obtains a reference date for a target user regarding a program used by a user who is changing their behavior to record health data, and presents the target user with a reference diary associated with the number of days that have passed from the reference date to the present. This information processing device can support the improvement of lifestyle habits from a psychological perspective.

[0168] (((2))) The information processing device described in (((1))) includes at least one reference diary, which is a first diary with good programmatic indicators and a second diary with poor programmatic indicators. This information processing device can provide a shared experience of psychological states.

[0169] (((3))) The indicator is an information processing device as described in (((2))) relating to behavior or outcome recorded as health data. This information processing device can provide a shared experience of psychological states.

[0170] (((4))) The reference diary is a pre-prepared virtual diary, an information processing device described in one of the (((1))) to (((3))) entries. This information processing device makes it possible to manage the content that is presented.

[0171] (((5))) The reference diary is an information processing device described in one of the following (((1))) to (((4))) that includes advice relevant to its content. This information processing device makes it possible to provide indirect advice.

[0172] (((6))) The processor is an information processing device described in any one of (((1))) to (((5))) that presents a reference diary after detecting the recording of health data by the target user. This information processing device can enhance the effectiveness of support.

[0173] (((7))) The processor is an information processing device described in any one of (((1))) to (((6))) that stops presenting a reference diary when the number of days exceeds a threshold. This information processing device allows for limiting the presentation of reference diaries to periods when improvement effects are most likely to occur.

[0174] (((8))) If the health data includes data inherited from another program different from the program, the processor obtains the second reference date for the target user related to the other program as the reference date, as described in any one of (((1))) to (((7))). According to this information processing device, the period during which other programs were used can be reflected in the displayed content.

[0175] (((9))) An information provision method in which a computer performs the following processes: obtaining a reference date for a target user regarding a program used by users who change their behavior to record health data; and presenting the target user with a reference diary associated with the number of days that have passed from the reference date to the present. This method of providing information allows for the provision of a system that supports the improvement of lifestyle habits from a psychological perspective.

[0176] (((10))) A program that enables a computer to obtain a reference date for a target user related to a program used by users who are changing their behavior to record health data, and to present the target user with a reference diary associated with the number of days that have passed from that reference date to the present. This program provides a mechanism to support lifestyle improvements from a psychological perspective. [Explanation of Symbols]

[0177] 1…Information processing system, 10…PDT platform, 20, 20A, 20B, 20C, 20D, 20E, 20F…PDT server, 30…Physician terminal, 40…Patient terminal

Claims

1. It has a processor, The aforementioned processor, Obtain the reference date for the target user regarding the program that users who change their behavior use to record health data. The user is presented with a reference diary associated with the number of days that have elapsed from the aforementioned reference date to the present. Information processing device.

2. The aforementioned reference diary includes at least one of a first diary in which the indicators managed by the program are good, and a second diary in which the indicators managed by the program are not good. The information processing apparatus according to claim 1.

3. The aforementioned indicator relates to the behavior or outcome recorded as health-related data. The information processing apparatus according to claim 2.

4. The aforementioned reference diary is a pre-prepared, fictional diary. The information processing apparatus according to claim 1.

5. The aforementioned reference diary includes advice relevant to the content. The information processing apparatus according to claim 1.

6. The processor presents the reference diary after detecting that the target user has recorded the health-related data. The information processing apparatus according to claim 1.

7. The processor stops presenting the reference diary when the number of days exceeds a threshold. The information processing apparatus according to claim 1.

8. If the health data includes data inherited from another program different from the program, the processor obtains the second reference date of the target user for the other program as the reference date. The information processing apparatus according to claim 1.

9. Computers The process of obtaining the reference date for the target user regarding the program that users who change their behavior use to record health data, The process of presenting the target user with a reference diary associated with the number of days that have elapsed from the aforementioned reference date to the present, A method for providing information to carry out the task.

10. On the computer, A feature that allows users to obtain a reference date for the target user regarding the program they use to record health data as they change their behavior, A function that presents the target user with a reference diary associated with the number of days that have elapsed from the aforementioned reference date to the present, A program to achieve this.

Images