Information processing device, information provision method, and program

Abstract

To provide a mechanism that supports the review of a record input by a user who changes his / her action.SOLUTION: An information processing device includes one or a plurality of processors in which the one or the plurality of processors acquire data related to health input by a user who changes his / her action, and present information portion in which a predetermined change appears as compared to a comparison target among the data related to health in a form different from that of other information portions.SELECTED DRAWING: Figure 13

Description

[Technical Field]

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

[0002] Today, there are application programs (hereinafter referred to as "programs") that can be used for health promotion and medical treatment. Programs that do not require approval under the Pharmaceutical and Medical Device Act are called, for example, healthcare apps. On the other hand, programs that require approval under the Pharmaceutical and Medical Device Act are called treatment apps. These programs have a function for recording daily activities, feelings, etc. in a diary-like manner. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 5299965 Summary of the Invention [Problem to be solved by the invention]

[0004] There are times when you want to review past records. However, the more records you have, the greater the burden of reviewing them becomes. For this reason, a sampling-based review method is used. However, with a sampling-based review method, there is a risk that information needed for health promotion or medical treatment will be overlooked. This defeats the purpose of reviewing daily life records.

[0005] As one aspect of the present disclosure, a mechanism is provided to support review of records entered by users who change their behavior. [Means for solving the problem]

[0006] The invention described in claim 1 is an information processing device having one or more processors, which acquire health-related data input by a user who is changing their behavior, and presents information portions of the health-related data that show a predetermined change compared to a comparison subject in a manner different from other information portions. The invention described in claim 2 is the information processing device described in claim 1, wherein the one or more processors use a second information portion corresponding to the information portion in the immediately previous target period as the comparison target. The invention of claim 3 is the information processing device of claim 1, wherein the one or more processors use an initial value corresponding to the information portion as the comparison target. The invention described in claim 4 is the information processing device described in claim 1, wherein the one or more processors use the user's therapeutic goal as the comparison object. The invention described in claim 5 is the information processing device described in claim 1, wherein the one or more processors use a goal managed by a program used to record the health-related data as the comparison object. The invention described in claim 6 is an information processing device described in claim 1, in which the one or more processors use a response from the user to a query from a program used to record the health-related data as the information part that changes the presentation manner. The invention described in claim 7 is an information processing device described in claim 1, in which the one or more processors use at least one of the health-related data, including a record of the user's behavior, a record of the user's mood, a record of an image by the user, and a record of the user's voice, as the information part that changes the presentation manner. The invention described in claim 8 is the information processing device described in claim 1, wherein the one or more processors present the information portion that shows a predetermined improvement over the comparison target in a manner different from other information portions. The invention described in claim 9 is an information processing device described in claim 1, in which the one or more processors present the third information portion in which a first change appears and the fourth information portion in which a second change appears in relation to the comparison object in different manners. The invention described in claim 10 is an information provision method in which a computer executes a process of acquiring health-related data input by a user who is changing their behavior, and a process of presenting, in a manner different from other information portions, information portions of the health-related data that show a predetermined change relative to a comparison subject. The invention described in claim 11 is a program for enabling a computer to acquire health-related data input by a user who is changing their behavior, and to present information from the health-related data that shows a predetermined change relative to a comparison subject in a manner different from other information portions. [Effects of the Invention]

[0007] According to one embodiment of the present disclosure, it is possible to support the review of records entered by a user who is changing their behavior. [Brief explanation of the drawings]

[0008] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of an information processing system according to a first embodiment. [Figure 2] FIG. 1 is a diagram illustrating an example of the hardware configuration of a PDT platform. [Figure 3] FIG. 2 is a diagram illustrating an example of status management data stored in an auxiliary storage device of the PDT platform. [Figure 4] FIG. 2 is a diagram illustrating an example of the hardware configuration of a PDT server. [Figure 5] FIG. 10 is a diagram illustrating an example of patient data stored in an auxiliary storage device of the PDT server. [Figure 6] FIG. 2 is a diagram illustrating an example of the hardware configuration of a doctor terminal and a patient terminal. [Figure 7] FIG. 2 is a diagram illustrating an example of a processing sequence according to the first embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of an operation screen in a patient application. [Figure 9] FIG. 10 is a diagram illustrating screen transitions related to a review input screen. [Figure 10] FIG. 10 is a diagram illustrating an example of an inquiry screen displayed on the start program screen. [Figure 11] FIG. 10 is a diagram illustrating an example of a management screen for the usage status of a patient application displayed on the output device of the doctor terminal. [Figure 12] FIG. 10 is a diagram illustrating a display example of a patient data viewing screen. [Figure 13] FIG. 10 is a diagram illustrating another display example of the patient data viewing screen. [Figure 14] FIG. 10 is a diagram illustrating another display example of the patient data viewing screen. [Figure 15] FIG. 10 is a diagram illustrating another display example of the patient data viewing screen. [Figure 16] FIG. 10 is a diagram illustrating another display example of the patient data viewing screen. [Figure 17] FIG. 10 is a diagram illustrating an example of a processing sequence according to the second embodiment. [Figure 18] FIG. 11 is a diagram illustrating an example of a processing sequence according to the third embodiment. [Figure 19] FIG. 10 is a diagram illustrating a method for reading out my data from the menu screen. [Figure 20] 10A and 10B are diagrams illustrating a display example in which two types of changes relative to a comparison target are highlighted in different modes. [Figure 21] FIG. 10 is a diagram illustrating an embodiment in which "health-related data" recorded through a non-patient app and "health-related data" recorded through a patient app are used in combination. [Figure 22] FIG. 10 is a diagram illustrating another embodiment in which "health-related data" recorded through a non-patient app and "health-related data" recorded through a patient app are used in combination. DETAILED DESCRIPTION OF THE INVENTION

[0009] <Terminology> First, terms used in the embodiments described below will be explained. A "program that encourages behavioral change" is a program that is provided with the intention of encouraging a change in a person's behavior. However, this program does not guarantee that a person's behavior will change. Whether or not a person's behavior actually changes depends on the user who uses the program. Therefore, a program that encourages behavioral change can also be said to be a program that supports behavioral change. This type of program can be classified as a medical device or a non-medical device. A medical device program is an example of a program that requires a prescription, while a non-medical device program is an example of a program that does not require a prescription.

[0010] "Program objectives" refer to the effects to be achieved by using a program to promote behavioral change. Program objectives vary depending on the disease for which the program promotes behavioral change is targeted. For example, program objectives may include improving lifestyle habits, maintaining improved lifestyle habits, and maintaining improved numerical values. "Program goal" refers to the goal to be achieved through the use of a program to promote behavioral change. Goals are defined from the perspective of achieving the objective. Goals are classified into qualitative indicators and quantitative indicators. Goals are also classified into indicators defined by measurements or other numerical values ​​and indicators defined by the content of actions. For example, goals can include improving or maintaining habits, behaviors, or numerical values. Program goals can also be further defined by one or more subgoals. Subgoals are smaller-scale targets set to achieve the corresponding goal.

[0011] "Therapeutic App" refers to an application program that has been approved under the Pharmaceuticals and Medical Devices Act. Therapeutic Apps are programs that are classified as medical devices. Therapeutic apps are approved for each disease. Diseases for which approval has already been obtained include hypertension, nicotine addiction, and insomnia. Diseases for which therapeutic apps are currently in development include NASH (non-alcoholic steatohepatitis), diabetes, dyslipidemia, kidney disease, and alcoholism.

[0012] "User" refers to a person who changes their behavior through a program that encourages behavioral change. Users include users who have not yet visited a medical institution and users who have visited a medical institution. Users who have visited a medical institution include users who are subject to medical fee calculations and users who are not subject to medical fee calculations. A "patient" refers to a user who is currently receiving treatment at a medical institution. In other words, a patient refers to a user who has started or is currently undergoing treatment at a medical institution.

[0013] Treatment apps include patient apps and doctor apps. A "Patient App" is an application program that runs on a device operated by a patient (hereinafter also referred to as a "Patient Terminal") and is prescribed to the patient by a doctor. In this sense, the Patient App is also called a PDT (Prescription Digital Therapeutic). The patient app can be downloaded from, for example, an app store. In the embodiment described below, a code required for activation (hereinafter referred to as a "prescription code") is issued by a doctor's prescription. The patient app is used to record patient data outside of medical institutions (hereinafter also referred to as "patient app data").

[0014] A validity period is set for a patient app at the time of approval. This validity period is determined based on, for example, the period during which the public medical insurance system applies. The validity period is determined depending on the type of disease that the patient app covers. For example, the validity period for a patient app for hypertension is six months, counting from the month following the month in which the patient app was prescribed. However, six months is just an example, and it could be, for example, nine months or 12 months. The validity period may also be determined in days, such as 60 days or 180 days, or in weeks, such as eight weeks or 24 weeks. Needless to say, these values ​​are just examples.

[0015] A "doctor app" refers to an application program that can be used through a terminal operated by a doctor or other medical professional (hereinafter also referred to as a "doctor terminal"). In the embodiment described below, 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). Note that medical professionals are also referred to as medical workers.

[0016] "Patient data" includes, for example, patient attributes, measurement values, activity records, mood records, physical condition records, medical examination history, patient app operation history, biological characteristics, psychological characteristics, social characteristics, habits, and goal achievement status. However, the items recorded as patient data vary depending on the disease, and do not necessarily have to be all of the exemplified information, but may be some of it or may include other information. Note that the items recorded as patient data are all examples of health-related data.

[0017] The "patient attributes" include, for example, the patient's name, gender, and date of birth. These pieces of information are examples of basic patient information. "Measurement value" refers to a numerical value measured using a measuring device. The measurement value items recorded as patient app data are defined for each disease. For example, if the disease is hypertension, blood pressure values ​​are recorded as measurement 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 measurements recorded would be carbon monoxide (CO) in the breath and nicotine concentration in the saliva.

[0018] "Activity records" include, for example, operation history of the patient app, medication records, meal records, smoking records, drinking records, and exercise records. These records are also records of the user's behavior. Activity records are an example of information related to activities. The "mood record" is, for example, a record of the mood perceived by the user. The mood record is an example of information related to mood. The "physical condition record" is, for example, a record of the physical condition or symptoms that the user feels. The physical condition record is an example of information related to the physical condition.

[0019] The "medical examination history" includes, for example, the treatment start date, the consultation date, the content of the treatment, and advice. The medical examination history is an example of information related to medical examinations. The "patient application operation history" is, for example, a history of operations related to the patient application startup operation, and the input operation of measurement values ​​and reviews. "Biological characteristics" include, for example, whether or not the patient has other illnesses, whether or not they have had injuries undergoing treatment, whether or not they have pain in their knees or feet, whether or not they have had treatment for an illness, the number of years since the illness was diagnosed, how strongly seasoned their food is at home, and the amount of food they eat.

[0020] "Psychological characteristics" include, for example, expectations regarding app treatment, willingness to acquire knowledge about disease treatment, whether reducing salt intake is difficult, whether one believes one's sense of taste cannot be changed, and psychological resistance to leaving food on one's plate. "Social characteristics" include, for example, wake-up time, bedtime, type of work (e.g., shift work, day shift, night shift), days of the week worked, start time of work, time home from work, regular days off, and whether or not there is a heater in the changing room.

[0021] "Habits" include, for example, exercise habits, weighing oneself, checking the calorie count on food labels, choosing low-fat foods, not consuming caffeine after 4 p.m., eating and drinking after 10 p.m., skipping breakfast, snacking, taking a bath one hour before bedtime, stretching or massaging before bedtime, and sleeping for six hours or more. The "goal achievement status" is, for example, information indicating the progress status toward a goal set by a doctor for each patient. The "goal achievement status" may be, for example, information indicating the progress status toward a goal set by the patient himself / herself. The "goal achievement status" may be, for example, information indicating the progress status toward a goal presented by a patient app for each patient. The above-mentioned information can be classified into subjective information and objective information. The patient application data is recorded, for example, as text, images (moving images, still images), audio, numerical values, and codes.

[0022] The "PDT server" is a server that manages patient data entered through a patient app, etc. The PDT server is also an example of a cloud server. A PDT server is basically provided for each patient app. Therefore, in order for a doctor to view patient data, he / she must log in to the PDT server running the doctor app that is paired with the patient app used by the patient.

[0023] For example, if a patient uses a patient app for hypertension provided by service provider A, the doctor needs to log in to the PDT server operated by service provider A for hypertension. Also, if a patient uses a patient app for hypertension provided by service provider B, the doctor needs to log in to the PDT server operated by service provider B for hypertension.

[0024] In addition, if a patient uses 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. It should be noted that multiple patient apps targeting different diseases may share one PDT server. Furthermore, multiple patient apps provided by different service providers may share one PDT server.

[0025] The PDT platform is a server that manages patient app prescriptions and the usage status of patient 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, meaning that it is a server that provides prescription services for patient apps. The usage status may be, for example, "before use begins," "expired," "in use," "scheduled to end," "ended," or "expired."

[0026] "Before use begins" refers to the state in which the prescription for the patient app has been completed but use on the patient's device has not yet begun. For example, this refers to the state in which the patient has not yet entered the prescription code into the device. "Start expired" refers to a state in which the prescription code has not been confirmed as entered within the period in which the prescription code is valid (for example, within four days including the prescription date).

[0027] "In use" refers to the state in which the patient app installed on the patient device has been activated and is ready for use. Activating the patient app requires the entry of an activation code, such as the prescription code mentioned above. "Scheduled to end" refers to a state in which a medical institution has set the patient to be outside the scope of management within the validity period. For example, this state is set for a patient who will not receive a follow-up examination.

[0028] "Terminated" refers to a state in which the patient app cannot be used due to, for example, the expiration of the validity period. "Expired" is a state that indicates that a predetermined period has passed since the prescription date. The predetermined period is set to be longer than the validity period. For example, if the validity period is 6 months, the predetermined period is set to 8 months. "Selected medical treatment" is displayed when the validity period has expired but the patient is still eligible for selected medical treatment. Selected medical treatment refers to medical services that patients enrolled in social insurance can receive in addition to insured treatment, treatment not covered by insurance, by paying an additional fee.

[0029] The PDT platform can support 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 acts as a platform for multiple patient apps. The app, which runs on the PDT platform, manages the usage status of multiple patient apps for different diseases and service providers on a patient-by-patient basis.

[0030] In the embodiments described below, the "medical institution" is assumed to be a medical institution that is covered by health insurance. More specifically, the medical institution refers to a medical institution that is covered by health insurance and to which a doctor who issues a prescription code required to activate a patient app belongs. However, if deregulation allows pharmacists, public health nurses, nurses, nutritionists, hospital staff, and other medical professionals to issue prescription codes, the term "medical institution" also includes facilities and organizations that employ these medical professionals. In the following, these medical professionals will be collectively referred to as "doctors, etc." The issuance of prescription codes is not limited to medical treatment, but may also be for non-insurance treatment (i.e., private treatment) or mixed treatment. Incidentally, medical treatment is not limited to face-to-face treatment, but also includes online treatment.

[0031] <First Embodiment> <Overall system> 1 is a diagram illustrating an example of the overall configuration of an information processing system 1 according to Embodiment 1. The information processing system 1 illustrated in FIG. 1 includes a PDT platform 10, PDT servers 20 (20A, 20B, 20C, . . . 20F), a doctor terminal 30, and a patient terminal 40.

[0032] 1 depicts only one PDT platform 10, although multiple PDT platforms 10 may exist. The PDT platform 10 may be configured with 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 communicatively connected via a network (not shown). The network may be, for example, a LAN (Local Area Network), the Internet, or a mobile communication system (4G, 5G, etc.).

[0033] 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 patient authentication, manages patient application data input through the patient application, and provides patient data to the doctor terminal 30. The PDT server 20 is an example of an information processing device. In the case of FIG. 1, the PDT server 20A is a server that manages patient data of a patient application (hereinafter referred to as "patient application A") provided by company A for patients with hypertension. The PDT server 20B is a server that manages patient data of a patient application (hereinafter referred to as "patient application B") provided by Company B for patients with hypertension.

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

[0035] 1, a PDT server 20 is prepared for each combination of a disease targeted by a patient app and a service provider that provides the patient app. Therefore, even if the service provider that provides the patient app is the same, if the targeted diseases are different, a different PDT server 20 is prepared. Furthermore, even if the target disease is the same, if the service provider that provides the patient app is different, a different PDT server 20 will be prepared.

[0036] However, it is also possible to provide one PDT server 20 for a plurality of patient applications with different combinations. The PDT platform 10 and the PDT server 20 may be operated by different operators, not necessarily by the same operator. For example, some of the PDT servers 20 may be operated by the same operator as the PDT platform 10.

[0037] The doctor terminal 30 is a terminal operated by a doctor or the like who uses the services provided by the PDT platform 10 and the PDT server 20. In Figure 1, only one representative doctor terminal 30 is depicted. For example, a doctor can view the usage status of the patient app by logging in to the PDT platform 10. Also, a doctor can view patient data by logging in to the PDT server 20. The patient terminal 40 is a terminal operated by a patient. The patient terminal 40 uploads patient application data recorded through the patient application to the corresponding PDT server 20. In Fig. 1, only one patient terminal 40 is depicted as a representative example.

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

[0039] The processor 11 is a device that realizes various functions through the execution of programs. The semiconductor memory 12 stores UEFI (Unified Extensible Firmware Interface) and the like. The semiconductor memory 12 is also used as an execution area for programs. The processor 11 and the semiconductor memory 12 function as a computer.

[0040] The auxiliary storage device 13 is composed of, for example, a hard disk device or a semiconductor storage. The auxiliary storage device 13 stores an operating system and other programs. The other programs include, for example, an application program that displays a list of the usage status of the patient app. In addition, the auxiliary storage device 13 also stores data for managing the status management data 130 by prescription code prescribed by a medical institution. The communication interface 14 is an interface for communicating with an external terminal such as a PDT server 20 (see FIG. 1) through a network. The communication interface 14 is compatible with communication standards such as Ethernet (registered trademark), Wi-Fi (registered trademark), and mobile communication systems.

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

[0042] The prescription code 130A is issued each time a prescription is notified from the doctor terminal 30. The patient ID / patient name 130B is the patient ID and patient name registered at the time of prescribing the patient app. In the case of FIG. 3, the patient name of patient ID "12543" is "Mr. A", the patient name of patient ID "12544" is "Mr. B", and the patient name of patient ID "12545" is "Mr. C".

[0043] The prescription date / treatment date 130C is the date on which the doctor examined the patient. In this embodiment, the treatment date on which the doctor prescribed the patient app is referred to as the "prescription date" to distinguish it from other treatment dates. In the case of FIG. 3, only the prescription date is stored. In the case of FIG. 3, the prescription date of the patient app for "Mr. A" and "Mr. B" is "2024 / 5 / 28", and the prescription date of the patient app for "Mr. 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 the case of Figure 3, the prescription codes "12345" and "23456" were prescribed by the same doctor at the same medical institution.

[0044] The patient app name 130E is the name of the patient app prescribed by a doctor or the like. However, as long as it is possible to identify the patient app, an identification code of the patient app may be stored. In the case of FIG. 3, patient app A has been prescribed to "Mr. A" and "Mr. B." Patient app D has been prescribed to "Mr. C." The usage status 130F is information indicating the usage status of the patient app. The usage status stores one of the following: before use, start deadline expired, in use, scheduled to end, finished, and expired. In the case of FIG. 3, all patient apps are "in use."

[0045] <PDTサーバ> FIG. 4 is a diagram illustrating an example of the hardware configuration of the PDT server 20. As shown in FIG. 4 includes a processor 21, a semiconductor memory 22, an auxiliary storage device 23, and a communication interface 24. Each device is connected via a bus or other signal lines. The processor 21 is a device that realizes various functions through the execution of programs. The semiconductor memory 22 stores UEFI and the like. The semiconductor memory 22 is also used as an execution area for programs. The processor 21 and the semiconductor memory 22 function as a computer.

[0046] 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. Among the other programs, there is, for example, a doctor app. The doctor app is an application program that generates a browsing screen for patient data corresponding to patients treated by doctors and the like.

[0047] 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 is compatible with communication standards such as Ethernet (registered trademark), Wi-Fi (registered trademark), and mobile communication systems.

[0048] <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. Note that the patient data 230 shown in FIG. 5 assumes data of a hypertension patient. In the patient data 230 shown in FIG. 5, measured values and other information recorded through the patient app for hypertension are stored.

[0049] In the case of FIG. 5, the patient data 230 stores a prescription code 230A, a patient ID / patient name 230B, and patient app data 230C. In the case of the present embodiment, the patient app data 230C means management data of the patient app and data recorded by the patient through the patient app. The prescription code 230A records the prescription code 130A (see FIG. 3) issued by the PDT platform 10 (see FIG. 1). The prescription code 130A is registered by the patient at the start of using the patient app (i.e., at the time of new registration). The patient ID / patient name 230B is, for example, the patient ID and patient name in the medical institution that prescribed the patient app. The patient ID and patient name are obtained from the PDT platform 10, for example, at the time of authentication of the prescription code.

[0050] 5 includes a measurement value / measurement date and time 230C1, a review / input date and time 230C2, a current step of a treatment program 230C3, a treatment program practice history 230C4, a behavioral goal 230C5, a target value 230C6, an outpatient record 230C7, and a medication record 230C8. Note that the illustrated items do not need to be all of the patient application data 230C, and may be only a part of the patient application data 230C, or may include other items. The measured blood pressure value and the date and time when the blood pressure was measured are recorded in the measurement value / measurement date and time 230C1. The blood pressure value is given as a systolic blood pressure and a diastolic blood pressure.

[0051] The review / input date and time 230C2 records a review of the day's actions and the input date and time. In the review, for example, the level of physical condition, stress level, length of sleep, weight, and details of the actions taken are recorded. The details of the actions are composed of the category of the actions taken and text input. Other label candidates include, for example, "sleep," "stress," "moderate drinking," and "other." In this embodiment, the category of the actions taken is recorded by checking buttons labeled "reduce salt," "weight loss," "exercise," etc. In the text input, it is possible to freely input details and emotions that cannot be recorded by checking buttons.

[0052] The current step 230C3 of the treatment program records a step indicating the progress of the treatment program provided by the patient app. In this embodiment, the treatment program is composed of three steps. The three steps are, for example, "acquiring knowledge," "practicing behavioral goals," and "making behavior a habit." The treatment program practice history 230C4 records the history of learning and behavior practiced in accordance with the treatment program. For example, in the case of "Step 1," the learning history records whether or not each learning item has been taken. For example, in the case of "Step 2," the behavior history records the practice status of each goal, such as "reducing salt intake," "reducing weight," "exercise," "sleep," "stress," "alcohol consumption," and "quitting smoking." For example, in the case of "Step 3," the practice status of the behavior set by the patient as a goal is recorded.

[0053] The behavioral goal 230C5 records behaviors that the patient has set as goals. The goals here include one or more behavioral goals that the patient has selected from among the goals presented by the patient app according to the progress of the treatment program. For example, the behavioral goal 230C5 records a behavioral goal that the patient has set in step 2 or 3 of the treatment program. A behavioral goal refers to a behavioral goal that should be achieved in order to achieve a target. The behavioral goal is not limited to a behavioral goal selected from the behaviors presented by the patient app, and may include behaviors individually set by the patient.

[0054] The target value 230C6 is recorded with a value set by a doctor or the like in the "blood pressure reduction target value field" 313 (see FIG. 129) on the patient data viewing screen 310 (see FIG. 12). The "blood pressure reduction target value field" 313 is an example of a quantitative target in that it is given as a numerical value. The outpatient record 230C7 records appointments with the doctor, the next appointment date, medication timing, etc. The appointments with the doctor record appointments that the patient should make or be aware of before the next medical examination. In this embodiment, appointments with the doctor can only be recorded through the patient app. Note that appointments with the doctor may also be recorded only from the doctor terminal 30 (see FIG. 1). The medication record 230C8 records information about taking prescribed medication.

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

[0056] The processor 31 / 41 is a device that realizes various functions through the execution of a program. The semiconductor memory 32 / 42 stores UEFI and the like. 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 device 33 / 43 is configured by, for example, a hard disk drive or semiconductor storage, and stores an operating system and other programs.

[0057] In the case of the doctor terminal 30, the auxiliary storage device 33 stores a client certificate for accessing the PDT platform 10 (see FIG. 1) and a client certificate for accessing the PDT server 20 (see FIG. 1). In the case of the patient terminal 40, a client certificate for accessing the PDT server 20 (see FIG. 1) is recorded in the auxiliary storage device 43. In addition, the auxiliary storage device 43 also records patient application data 230C (see FIG. 5). The input interface 34 / 44 uses, for example, USB (=Universal Serial Bus) or Bluetooth (registered trademark) for connection to the input device 35 / 45. The input device 35 / 45 may be, for example, a keyboard, a mouse, or a touch panel.

[0058] The output interfaces 36 / 46 may be, for example, HDMI (=High-Definition Multimedia Interface) (registered trademark) or a LAN interface for connection to the output devices 37 / 47. The output devices 37 / 47 may be, for example, a monitor or a printer. The communication interface 38 / 48 is an interface for communicating with an external terminal via a network, and is compatible with Ethernet (registered trademark), Wi-Fi (registered trademark), mobile communication systems, and other communication standards.

[0059] <Patient data viewing screen output> The output process of the patient data viewing screen in the information processing system 1 (see FIG. 1) will be described below with reference to FIGS. Fig. 7 is a diagram illustrating an example of a processing sequence according to embodiment 1. The symbol S in Fig. 7 represents a step.

[0060] <Step 101> Patients record measurements and other data from the patient app's operation screen. Patients are an example of users who change their behavior. Patients record, for example, measurements, reflections, responses to inquiries, behavioral goals, target values, outpatient records, and medication records. These records are examples of health-related data. 8 is a diagram illustrating an example of an operation screen in the patient application. The operation screen shown in FIG. 8 can be transitioned from the home screen 401. The measurement value input screen 402 is, for example, a screen for inputting blood pressure values. Measurement values ​​can be input manually or through data linkage with a blood pressure monitor. However, data linkage with a blood pressure monitor is limited to cases where the blood pressure monitor can be linked with a patient app.

[0061] The review input screen 403 allows users to record their physical condition level, stress level, sleep duration, weight, activity details, mood, and physical condition. As mentioned above, the activity details include records of button operations corresponding to the category of activity that was successfully performed. The activity details also include text input. 9 is a diagram illustrating screen transitions related to the review input screen 403. The review input screen 403 is displayed by operating the input button 401A for "Today's review" provided on the home screen 401. Since it is "Today's review," it is assumed that input is made for each day. Note that the input button 401A shown in FIG. 9 is labeled "Enter."

[0062] 9 is composed of two screens. The first screen has fields for inputting the level of physical condition, the level of stress, the amount of sleep, and the weight. The second screen, which is displayed when the input on the first screen is completed, has a recording field 403A for actions related to lifestyle habits and a recording field 403B in which the user can freely record. Recording field 403A shown in Fig. 9 contains the question "Please tell us about the habits you were aware of or were able to act on today (multiple answers allowed)" and four buttons labeled "Lose weight," "Reduce salt intake," "Exercise," and "Other." In Fig. 9, the buttons corresponding to "Reduce salt intake" and "Other" are selected.

[0063] Recording field 403B shown in FIG. 9 includes an explanatory note saying "Please write freely," an example entry, and a text entry field. The text entered in recording field 403B is an example of health-related data entered by the user. In the case of FIG. 9, the text entered in the text entry field is "I tried cooking low-salt food. I'm glad it turned out delicious." Record field 403B, which allows free entry, can also be used as a kind of diary or memo, so the content entered in record field 403B is not necessarily limited to matters related to health. The contents entered in the record field 403B can be viewed on the doctor terminal 30 (see FIG. 1).

[0064] Returning to the explanation of Figure 8. The start program screen 404 is a screen used in "Step 1" of the treatment program, etc. "Step 1" is a learning stage aimed at acquiring knowledge about the disease. In "Step 1," the patient is first asked to input information about their employment status, preferences, etc. Next, the patient's characteristics are analyzed from the input information. Once the analysis results are obtained, knowledge regarding "reducing salt intake," "weight loss," "exercise," "sleep," "stress," "alcohol," "tobacco," "understanding the disease," and "blood pressure measurement" is presented according to the patient's characteristics. In addition, some of the information presented to patients will be adjusted depending on whether or not kidney dysfunction is indicated, their usual exercise habits, alcohol consumption, etc. The recommended duration for "Step 1" is two weeks.

[0065] "Step 2" is the stage where behavioral goals are put into practice. First, in "Step 2," behavioral goals appropriate for the patient are presented from among "reducing salt," "reducing weight," "exercise," "sleep," "stress," "alcohol," and "tobacco." The patient confirms the presented actions and records the results of the actions. Regarding the behavioral goals in this step, the displayed content of each item is partially adjusted based on the information entered by the patient themselves. In "Step 2," specific behavioral goals are presented for multiple behavioral categories that represent lifestyle habits that will improve the disease. Examples of behavioral categories include "reducing salt intake," "weight loss," "exercise," "sleep," "stress," and "alcohol." For example, behavioral goals in the "reducing salt intake" category include "avoiding salt intake through snacks and rice crackers," "avoiding drinking the broth of udon or ramen noodles," "avoiding eating at convenience stores or eating out for lunch," "avoiding eating within two hours before bed," "walking for 20 minutes," and "getting at least six hours of sleep."

[0066] "Step 3" is the stage where behavior becomes a habit. The patient sets the blood pressure target themselves. The blood pressure target is an example of an achievement goal. The patient records the progress of achieving the blood pressure target. In "Step 3," behaviors that the patient himself evaluated as being highly effective in "Step 2" are presented as behavioral goals with priority. The patient sets the presented behavior as a behavioral goal and aims to make the behavior a habit. Fig. 10 is a diagram illustrating an example of an inquiry screen 404A displayed on the start program screen 404 (see Fig. 8). The inquiry screen 404A shown in Fig. 10 is for inputting lifestyle habits based on the patient's awareness. The patient app uses the input information, for example, to identify the patient's characteristics and select behavioral goals to present to the patient.

[0067] Inquiry screen 404A shown in Fig. 10 displays nine items and options, followed by the explanation "Please check the items that apply to you." In the case of Fig. 10, four options are provided for each item. For example, for "Miso soup, soup, etc.", there are four options: "More than two bowls a day," "About one bowl a day," "2-3 times a week," and "Not often." These four options are accompanied by radio buttons, so you can only select one.

[0068] Other items include "Udon, ramen, and other noodles," "Rice crackers, rice crackers, potato chips, etc.", "How often do you put soy sauce or other sauces on your food?", "Do you drink the soup with udon, ramen, etc.", "Do you eat out or use convenience store bento for lunch?", "Do you drink sugary drinks?", "Do you use butter, mayonnaise, or dressing?", and "Do you usually eat until you're full." Each item has options depending on the content of the inquiry. In the case of Figure 10, the options correspond to the frequency or amount of intake.

[0069] Returning to the explanation of Figure 8. The behavioral goal list screen 405 is a screen that can be displayed after "Step 2." A list of behavioral categories is displayed on the behavioral goal list screen 405. The degree of adherence is also displayed for each category. The social support screen 406 is a screen that can be displayed after "Step 2". A list of social supports is displayed on the social support screen 406. The social support screen 406 displays treatment know-how that is useful in real life.

[0070] The My Data screen 407 is a screen used to check the progress of steps, measurement values, review, salt intake status, knowledge, and behavior. The measurement value screen 408 is a screen on which the measurement values ​​recorded up to now are displayed as a trend graph or numerical values. The salt intake screen 409 is a screen that can be displayed after "Step 2". On the salt intake screen 409, it is possible to record salt intake, record dietary details, and view the recorded details. The recorded details can be displayed as a trend graph or numerical values. The outpatient record screen 410 is a screen on which the patient can record appointments made with the doctor at the time of the visit, record the next visit date, record the time of day when prescribed medicines will be taken, and view the recorded contents. The medication record input screen 411 is a screen on which medication records can be recorded and the recorded contents can be viewed.

[0071] <Step 102> Returning to the explanation of Figure 7. The patient terminal 40 uploads patient app data at predetermined times. One of the predetermined times is when new data is recorded or updated. This upload is performed when the patient app remains logged in to the PDT server 20. Another predetermined time is when the patient signs in to the PDT server 20. This upload is performed when the patient app logs out of the PDT server 20 and then logs in to the PDT server 20 again.

[0072] <Step 103> The PDT server 20 stores the uploaded patient application data, which constitutes part of the patient data 230 (see FIG. 5). Steps 101 to 103 shown in FIG. 7 are executed in response to a recording operation by a patient to the patient application.

[0073] <Step 104> When a doctor or the like logs in to the PDT platform 10 via the doctor terminal 30, the PDT platform 10 presents a confirmation screen for the usage status of the patient app to the doctor terminal 30. FIG. 11 is a diagram illustrating an example of a management screen 300 for the use status of patient applications displayed on the output device 37 (see FIG. 6) of the doctor terminal 30 (see FIG. 6).

[0074] The management screen 300 shown in FIG. 11 is an example of a management screen that displays, in a list, the usage status of patient apps prescribed to patients by a doctor or the like who operates the doctor terminal 30. The management screen 300 may display only the usage status of patient apps prescribed by the doctor or the like operating the doctor terminal 30, or may display the usage status of patient apps prescribed by the medical institution to which the doctor or the like operating the doctor terminal 30 belongs. In other words, the management screen 300 may include the usage status of patient apps prescribed by other doctors or the like who belong to the same medical institution.

[0075] In addition, the management screen 300 may be configured to display the usage status of patient apps prescribed by other doctors or other medical institutions. This display function is useful, for example, when a patient requests a second opinion. This display can be realized, for example, by a doctor operating the doctor terminal 30 providing information identifying the patient under treatment (for example, a medical record number or a patient name) to the PDT platform 10. Furthermore, technically, it is also possible to include information on all patients managed by the PDT platform 10 on the management screen 300. In that case, however, it is desirable to be able to narrow down or rearrange the patients displayed on the management screen using the ID of the doctor operating the doctor terminal 30, etc.

[0076] The management screen 300 shown in FIG. 11 is composed of an information field 301 , a current date and time 302 , a “Details” button 303 , a “New prescription” button 304 , and a “Close” button 305 . Management information of the patient app prescribed to each patient is displayed in the information field 301. In the case of Fig. 11, the information field 301 is displayed in a table format. Information for each patient is displayed in the rows, and management items of the patient app are displayed in the columns. FIG. 11 shows, as management items, examples of medical record number / patient name 301A, application name 301B, usage status 301C, prescription date 301D, and prescription code expiration date 301E.

[0077] The medical record number / patient name 301A displays the medical record number and the patient name, which are examples of information for identifying a patient to whom the patient application has prescribed a medication. The information for identifying a patient may include a user ID, an address, etc. The application name 301B displays the name of the patient application prescribed to the patient. In this embodiment, four applications are displayed: patient application A, patient application B, patient application C, and patient application D. The application name 301B may include version information.

[0078] Note that if multiple patient apps are approved for a patient, the information will be displayed in different rows. In addition to or in addition to the application name 301B, the name of the disease targeted by the patient application may be displayed. The usage status 301C is used to display the usage status of the patient app. In the case of Fig. 11, the usage status 301C displays three options: "Before starting usage," "In use," and "Ended." However, as mentioned above, the usage status 301C also displays "Start deadline expired," "Scheduled to end," "Expired," etc.

[0079] The prescription date 301D displays the date on which the patient app was prescribed by a doctor or the like. The last date on which the prescription code is valid is displayed in prescription code expiration date 301E. In this embodiment, the date three days after prescription date 301D is displayed in prescription code expiration date 301E. The current date and time 302 is the date and time when the patient application usage status management screen 300 is viewed.

[0080] The "Details" button 303 is a button used to display a patient data viewing screen. The "Details" button 303 is arranged on each row corresponding to a patient. When the "Details" button 303 is operated, the patient data viewing screen for the patient corresponding to the "Details" button 303 is displayed. The "New Prescription" button 304 is used when prescribing a patient app to a patient. When the "New Prescription" button 304 is operated, a screen for inputting the app name, patient name, gender, date of birth, etc. is displayed. The name of the prescribing doctor is also registered at the same time. The "close" button 305 is a button for closing the management screen 300 shown in FIG.

[0081] <Step 105> Returning to the explanation of Figure 7. The doctor terminal 30 accepts the selection of a patient on the management screen 300 (see FIG. 11) described above. Specifically, the doctor terminal 30 accepts the operation of the "Details" button 303 (see FIG. 11). For example, the doctor terminal 30 accepts the operation of the "Details" button 303 corresponding to Mr. H, for whom more than five months have passed since the prescription date. "Mr. H" here is an example of a specific user. The doctor terminal 30 that has accepted the operation of the "Details" button 303 accesses the PDT server 20 of the patient app prescribed to the patient corresponding to the operated "Details" button 303.

[0082] It is assumed that the doctor or the like has already logged in to the PDT server 20 to be accessed via the doctor terminal 30. In this access, the prescription code of the patient app prescribed to the patient corresponding to the operated “Details” button 303 is notified. The doctor terminal 30 may request the PDT platform 10 to issue a one-time token required to access the corresponding PDT server 20. In this case, the doctor terminal 30 accesses the PDT server 20 using the one-time token returned from the PDT platform 10. When this method is adopted, doctors and other personnel can access patient app data of PDT servers 20 to which they are not logged in.

[0083] <Step 106> The PDT server 20, which has been accessed by the doctor terminal 30, generates a viewing screen for patient data relating to the selected patient. In the present embodiment, a viewing screen for Mr. H is generated.

[0084] <Step 107> The PDT server 20 extracts information portions that exhibit predetermined changes relative to the comparison target. The comparison targets are set in advance. For example, when displaying health data in units of a predetermined period, the information portion of the previous period is used as the comparison target for each period. The information portion is the unit of display on the viewing screen. The information portion includes behavior, mood, images, sounds, measurements, and averages, representative values, summaries, etc. recorded through the patient app. The period can be, for example, one day, one week, one month, two months, three months, or other periods. The period is an example of the target period corresponding to the information portion.

[0085] Alternatively, the comparison may be made with an initial value corresponding to the information portion, such as a value from the first period of the viewing screen or a value initially recorded through the patient app. Furthermore, the comparison may be made with therapeutic goals determined for each user. The goals may be set by, for example, a doctor. Of course, the goals set differ depending on the disease. For example, in the case of hypertension, the comparison target is blood pressure values. In the case of diabetes, the comparison target is blood sugar levels and Hba1c values. In the case of nicotine addiction, the comparison target is the CO concentration in the breath. In the case of alcohol addiction, the comparison target is the amount of alcohol. Furthermore, the comparison may be made with goals managed by the patient app, such as goals managed in "Step 2" or "Step 3" of the treatment program. The comparison target is also an example of a reference value.

[0086] A "predetermined change" refers to a change that has been determined in advance. Information that does not correspond to a predetermined change relative to the comparison target is not extracted as a "predetermined change." For example, if the amount of change is small relative to the threshold, it does not correspond to a "predetermined change." Also, if the content of the change does not meet the standard, it does not correspond to a "predetermined change." For example, if the standard is an improvement in health status, deterioration or maintenance of health status does not correspond to a "predetermined change." Also, if the standard exceeds the comparison target, even if the health status improves, the information does not correspond to a "predetermined change" as long as it does not reach the comparison target.

[0087] Note that, for example, a method using a predetermined extraction algorithm can be used to extract an information portion in which a "predetermined change" appears. The extraction algorithm includes an algorithm that compares a comparison object with an information portion and determines whether or not to extract the information portion based on the comparison result. Note that the comparison can be performed, for example, by directly comparing the comparison object with the information portion, or by comparing the corresponding scores. Another extraction algorithm includes an algorithm that scores the change from the comparison object to the information portion and determines whether or not to extract the information portion by comparing the score with a threshold value. In addition, to extract information portions in which "predetermined changes" appear, one method is to use a trained model that has learned "predetermined changes" through machine learning.

[0088] <Step 108> The PDT server 20 presents the viewing screen 310 (see FIG. 13, etc.) in which the extracted information portion has been changed to a form different from other records to the doctor terminal 30. If the information portion extracted in step 107 does not exist, the viewing screen presented to the doctor terminal 30 is the same as the viewing screen generated in step 106. FIG. 12 is a diagram illustrating a display example of the patient data viewing screen 310.

[0089] 12 shows the upper portion of the viewing screen 310. The viewing screen 310 shown in Fig. 12 is composed of a "patient information field" 311, a "measurement result display field" 312, a "blood pressure reduction target value field" 313, a "review information display field" 314, an "activity record display field" 315, a "inquiry response result list display field" 316, and a scroll bar 317. The viewing screen 310 may include operation buttons (not shown), etc. The operation buttons (not shown) include, for example, a button for opening a registration screen for the examination date and a button for closing the viewing screen 310.

[0090] 12, a "patient information column" 311 is arranged at the top of the viewing screen 310. A "measurement result display column" 312, a "review information display column" 314, and an "activity record display column" 315 are arranged at the second row from the top of the viewing screen 310. A "blood pressure reduction target value column" 313 is arranged at the third row from the top of the viewing screen 310, and a "display column for a list of response results to inquiries" 316 is arranged at the bottom. However, the display serving as output device 37 (see FIG. 6) cannot display the entire viewing screen 310 at once. For this reason, only a part of the "display column for a list of response results to an inquiry" 316 is displayed on viewing screen 310 shown in FIG.

[0091] The "Patient Information" column 311 shown in FIG. 12 indicates that the medical record number is "13002," the patient name is "Mr. H," the age is "60 years old," and the sex is "male." The average blood pressure measured at home is displayed numerically and graphically in the "measurement result display column" 312 shown in Figure 12. Daily measurement values ​​can be entered on the measurement value input screen 402 (see Figure 8).

[0092] In the case of FIG. 12, the average values ​​are shown for two intervals: "8 weeks to 4 weeks ago" and "4 weeks ago to the day before." Here, the "day before" refers to the day before the current date and time when the viewing screen 310 is opened. Doctors and other medical professionals can check the progress of treatment by viewing the numerical values ​​and other information displayed in the "measurement result display column" 312. 12 indicates that the target value for home diastolic blood pressure (maximum blood pressure) is less than 125 mmHg, and the target value for home systolic blood pressure (minimum blood pressure) is less than 75 mmHg. Note that the target blood pressure may differ depending on gender, the presence of other diseases, age, and other factors. 12, a "change" button for the target value is provided in the "blood pressure reduction target value field" 313. Only a doctor or the like can change the target value.

[0093] The "retrospective information display field" 314 shown in FIG. 12 displays records of mood and physical condition. The retrospective information is the content entered in the record field 403B (see FIG. 9). In the case of FIG. 12, four days' worth of retrospective information is displayed. For example, it is displayed that the physical condition on 5 / 27 was good, the physical condition on 5 / 26 was normal, the physical condition on 5 / 25 was extremely poor, and the physical condition on 5 / 24 was poor. In addition, the beginning of the text entered in the record field 403B corresponding to each date is displayed. To read the entire text of the "review information display column" 314, simply operate the "list" button 314A.

[0094] The "activity record display column" 315 shown in Figure 12 displays activity records for the last 28 days, such as the number of days the patient app was used, the number of days a reduction in salt intake was recorded, and the number of days a weight loss was recorded. In the "display column for a list of response results to inquiries" 316, the patient's response to the inquiry entered through the inquiry screen 404A (see FIG. 10) is displayed in a list format.

[0095] In this embodiment, among the information portions displayed in the "display column for the list of response results to inquiries" 316, information portions from which predetermined changes have been extracted are displayed in a format different from the other information portions. Incidentally, there are various types of comparison targets and predetermined changes, so below we will explain display examples of the "display column for a list of response results to an inquiry" 316 for each combination of comparison target and predetermined change. Note that a vertical scroll bar 317 is arranged on the right edge of viewing screen 310 shown in Fig. 12. In the case of Fig. 12, this indicates that the upper part of viewing screen 310 is displayed, and the lower part is not displayed.

[0096] <Display example 1: Example of a specified change being an improvement over the answer from the previous period> Fig. 13 is a diagram for explaining another display example of the patient data viewing screen 310. In Fig. 13, parts corresponding to those in Fig. 12 are assigned the same reference numerals. 13 shows the lower portion of the viewing screen 310. Note that the "patient information column" 311 is a screen area that is different from the area that is scrolled by the scroll bar 317. Therefore, the "patient information column" 311 is also displayed at the top of the viewing screen 310 shown in FIG. In FIG. 13, the entire "display column for the list of response results to inquiries" 316 is displayed.

[0097] In the "display column for the list of response results to inquiries" 316 shown in FIG. 13, "category," "content," and three "periods" are arranged horizontally. The "categories" on the viewing screen 310 shown in FIG. 13 are three: salt reduction, weight loss, and blood pressure. However, the configuration of the "categories" is not limited to the example in FIG. 13. For example, salt reduction, weight loss, exercise, etc. may be presented as "categories." The configuration of the "categories" may be determined according to the type of disease that the patient app supports.

[0098] Furthermore, the "category" may be determined according to the behavioral goal being managed through the patient app. For example, the behavioral goal being worked on in "Step 2" or "Step 3" of a treatment program may be presented as a "category." Furthermore, the "category" may be determined according to the purpose of treatment determined for each user. For example, for a patient with hypertension, blood pressure may be presented as a "category."

[0099] Each "category" is associated with a plurality of corresponding "contents." For example, the "contents" that correspond to reducing salt include "miso soup, soup, etc.", "noodles such as udon and ramen," "rice crackers, rice crackers, potato chips, etc.", "how often do you put soy sauce or other sauces on your food?", "do you drink the broth from udon, ramen, etc.", and "do you eat out or use convenience store bento for lunch?"

[0100] For example, the "content" items corresponding to weight loss include "Do you drink sugary drinks?", "Do you use butter, mayonnaise, or dressing?", and "You often eat until you are full." For example, the "contents" corresponding to blood pressure include "average blood pressure" and "amount of blood pressure reduction from the initial stage." Incidentally, the "contents" corresponding to reduced salt and reduced weight match those on the inquiry screen 404A (see FIG. 10).

[0101] However, the content displayed in the "display column for the list of answer results to the inquiry" 316 is not necessarily a match with the question on the inquiry screen 404A. For example, the "content" may be information that can be calculated quantitatively or qualitatively based on health-related data recorded through the patient app. For example, the "content" may be the number of days the patient app has been used, the rate at which the patient app has been used, the number of times or rate at which salt reduction has been recorded, the level of physical condition, the level of mood, or the level of stress.

[0102] The three periods shown in Figure 13 are "2023.12.8", one month after the prescription date in the patient app, "2024.4.8", four months after the prescription date in the patient app, and "2024.6.8", six months after the prescription date in the patient app. The information displayed for the first period is the response to inquiries made within one month of the prescription date. The information displayed for the second period is the response to inquiries made within three months, from two months to four months after the prescription date. The information displayed for the third period is the response to inquiries made within two months, from four months to six months after the prescription date.

[0103] In addition, if there are multiple inquiries within each period, the representative value may be displayed as, for example, the average value, the best response, the worst response, or the most recent response within each period. The viewing screen 310 shown in FIG. 13 shows an example of a display in which an improvement over the answer from the immediately previous period is considered to be a predetermined change.

[0104] For this reason, for "miso soup, soup, etc.", "about one cup per day" for "April 8, 2024," where a decrease in the number of intakes was confirmed, is highlighted compared to "two or more cups per day" for "December 8, 2023." Here, "two or more cups per day" and "about one cup per day" are the information parts. Also, "two or more cups per day" is an example of the second information part. Highlighting can be achieved by, for example, changing the display color, brightness, font, or a combination thereof. Highlighting is an example of a display mode that is different from other information portions. Incidentally, for "miso soup, soup, etc.", only answers from one of the three periods are highlighted.

[0105] For the questions "Udon, ramen, and other noodles," "Rice crackers, okaki, potato chips, etc.", "How often do you put soy sauce or other sauces on your food?", "Do you drink sugary drinks?", "Using butter, mayonnaise, or dressing," and "I often eat until I'm full," only answers from one of the three periods are highlighted. On the other hand, for the questions "Do you drink the broth of udon, ramen, etc.?" and "Do you eat out or buy convenience store bento for lunch?", the answers for two of the three periods are highlighted. This is because the two periods, "April 8, 2024" and "June 8, 2024," respectively, show improvements over the answers for the previous period. 13, the number of answers (i.e., information portions) is not necessarily large, but answers in which a predetermined change has been observed are highlighted, allowing the user to efficiently review answers that need to be confirmed. Also, highlighting reduces the risk of overlooking answers that need to be confirmed.

[0106] <Display example 2: Example of improvement over the initial value as the specified change> Fig. 14 is a diagram for explaining another display example of the patient data viewing screen 310. In Fig. 14, parts corresponding to those in Fig. 13 are assigned the same reference numerals. In the case of Fig. 14, an initial value is assumed as a comparison target. In Fig. 14, the answer (i.e., the information part) corresponding to the first period, "2023.12.8", is used as the initial value. In the case of FIG. 14, the answers that are highlighted are those that show a predetermined change compared to the answers in the first period, so the number of highlighted answers is increased compared to the display example shown in FIG. In FIG. 14, both the answers for the second and third periods for "average blood pressure" corresponding to the blood pressure category are highlighted. In the case of the viewing screen 310 shown in FIG. 14, it is easy to check the answers for each period in which a predetermined change has occurred relative to the initial value.

[0107] <Display example 3: Example of behavioral change that achieves the treatment goal for the first time as the specified change> Fig. 15 is a diagram for explaining another display example of the patient data viewing screen 310. In Fig. 15, parts corresponding to those in Fig. 13 are assigned the same reference numerals. In the case of Fig. 15, therapeutic goals (i.e., treatment objectives) are assumed as the comparison target. In the present embodiment, treatment objectives are set for each item in each category. For example, the options located at the right end of the inquiry screen 404A shown in Fig. 10 are set as treatment objectives or indicators corresponding to each item. In the case of Figure 15, a predetermined change refers to achieving a treatment goal or indicator for the first time.

[0108] As a result, in Figure 15, for the category "reduced salt," the answer for the third period corresponding to the question "Do you drink the broth of udon, ramen, etc.?" and the answer for the third period corresponding to the question "Do you eat out or buy convenience store bento for lunch?" are highlighted. In other words, the answer for which the treatment goal set for each item was first achieved is highlighted. In this way, doctors and other medical professionals can easily confirm when and for which item the treatment goal was first achieved.

[0109] The predetermined change is not limited to the achievement of the treatment goal, but may be defined as a predetermined change approaching the treatment goal. For example, the first achievement of the indicator immediately preceding the treatment goal (the second option from the right in FIG. 10) may be defined as the predetermined change. In this way, even before the treatment goal is reached, by highlighting the predetermined answer that indicates approaching the treatment goal, it is easy to confirm the items for which treatment is progressing smoothly. It is also possible to prevent overlooking the items for which treatment is progressing smoothly. In the case of the viewing screen 310 shown in Fig. 15, it is not clear what comparison target corresponds to each item. Therefore, a treatment goal or index may be displayed as a comparison target in association with each item. For example, when the mouse pointer is moved over an item, the corresponding treatment goal or index may be displayed as a pop-up on the screen.

[0110] <Display example 4: Example of a behavioral change that achieves a periodic goal for the first time as a specified change> Fig. 16 is a diagram for explaining another display example of the patient data viewing screen 310. In Fig. 16, parts corresponding to those in Fig. 13 are assigned the same reference numerals. In the case of Figure 16, the targets for comparison are assumed to be the goals for each period managed by the patient app (i.e., period goals). For example, the goal for "miso soup, soup, etc." corresponding to the first and second periods is "about one bowl per day," and the goal for the third period is "2-3 times per week."

[0111] In this case, only the answer "about one cup per day" for the second period, which is recorded as reaching the period goal for the question "miso soup, soup, etc.", is highlighted. The answer for the third period is also "about one cup per day." However, because the corresponding period goal is "2-3 times per week," the answer "about one cup per day" for the third period is not highlighted. On the other hand, for the question "rice crackers, okaki, potato chips, etc.", two answers, one for the first period and one for the third period, are highlighted because both achieved their period targets.

[0112] 16, doctors and other medical professionals can easily check the period in which the period goal was achieved for each item corresponding to each category. In addition, doctors and other medical professionals can prevent themselves from overlooking the items and periods in which the period goal was achieved. 16, the comparison target corresponding to each item is unclear. Therefore, a period target or indicator may be displayed in association with each item. For example, when the mouse pointer is moved over an item, the corresponding period target or indicator may be displayed as a pop-up on the screen.

[0113] <Summary> In this embodiment, doctors and other medical professionals can efficiently check answers that show a predetermined change compared to the comparison target among the answers of the patient displayed as patient data. In addition, the risk of doctors and other medical professionals overlooking answers that should be checked can be reduced. Furthermore, by changing the comparison target and the combination of predetermined changes, doctors and other medical professionals can read various information from the same viewing screen 310. As a result, doctors and other medical professionals can review the patient data recorded through the patient app from various perspectives.

[0114] In this embodiment, the "comparison object" and the "predetermined change" are set in advance, but the doctor or other person may be able to specify both or either of the "comparison object" and the "predetermined change." For example, if the "comparison object" or the like can be changed, it can help to understand the answer results displayed on the viewing screen 310 from multiple angles. Note that even if the "comparison object" or the like is changed, the number and position of the highlighted information portions may not change. However, the lack of change can also be used to understand the answer results from multiple angles.

[0115] <Embodiment 2> A second embodiment will be described. The information processing system according to this embodiment is the same as the information processing system 1 (see FIG. 1) described in the first embodiment. However, in this embodiment, it is assumed that a patient checks a summary of the review information that the patient inputs on a patient terminal 40 (see FIG. 1). Therefore, the information processing system does not necessarily require the PDT platform 10 (see FIG. 1) or the doctor terminal 30.

[0116] <Patient data viewing screen output> Hereinafter, the output process of the patient data viewing screen in the information processing system 1 (see FIG. 1) will be described with reference to FIG. Fig. 17 is a diagram illustrating an example of a processing sequence according to the second embodiment. In Fig. 17, parts corresponding to those in Fig. 7 are assigned the same reference numerals.

[0117] <Steps 101-106> Steps 101 to 106 are the same as those in the first embodiment. That is, the patient records measurement values, review information, and the like through a patient app running on the patient terminal 40. The patient terminal 40 then uploads the patient app data to the PDT server 20. The PDT server 20 also stores the patient app data. On the other hand, when a doctor or the like selects a specific patient through operation of the doctor terminal 30, the PDT server 20 generates a viewing screen for the corresponding patient data.

[0118] <Step 111> In this embodiment, the PDT server 20 instructs the generation AI server 50 to extract information portions that exhibit a predetermined change relative to the comparison target. The PDT server 20 provides the generation AI server 50 with the viewing screen generated in step 106, for example. However, the PDT server 20 may provide the generation AI server 50 with only the "display column for a list of response results to an inquiry" 316. The PDT server 20 also provides a prompt to the generation AI server 50 along with the viewing screen 310 or the "display field for the list of response results to the inquiry" 316 to be processed. The prompt includes, for example, an instruction and a restriction. The instruction may include a specification of the object of comparison and a definition of the specified change. The restriction may include a specification of the information portion that is prohibited from being extracted as the specified change.

[0119] <Step 112> The generation AI server 50 extracts information parts that show a predetermined change in comparison with the comparison target in accordance with the prompt. The generation AI server 50 has a trained model that has learned the input-output relationship by machine learning, taking documents, images, sounds, and other content as input and outputting information parts that satisfy the conditions specified in the prompt. 17, the generation AI server 50 is a server different from the PDT server 20. However, the PDT server 20 may also serve as the generation AI server 50.

[0120] <Step 108> Step 108 is the same as in embodiment 1. That is, the PDT server 20 presents to the doctor terminal 30 a viewing screen 310 (see FIG. 13, etc.) in which the information portion extracted by the generation AI server 50 has been changed to a form different from other records.

[0121] <Summary> In this embodiment, the generation AI server 50 is instructed to extract information portions that exhibit a predetermined change relative to the comparison target. That is, the PDT server 20 in this embodiment can concentrate its computational resources on managing patient data by utilizing the generation AI server 50, which is an external terminal. Note that, from the perspective of ensuring the confidentiality of patient data, patient data that has been processed so that individuals cannot be identified is provided to the generation AI server 50.

[0122] <Third Embodiment> A third embodiment will now be described. The information processing system according to this embodiment is the same as the information processing system 1 (see FIG. 1) described in the first embodiment. However, in this embodiment, it is assumed that a patient instructs a patient terminal 40 (see FIG. 1) to display a My Data screen 407 (see FIG. 8). Therefore, the information processing system does not necessarily require the PDT platform 10 (see FIG. 1) or the doctor terminal 30. As described above, the My Data screen 407 displays information input by the patient.

[0123] <My Data screen output> The following describes the output process of review information in the patient terminal 40 (see FIG. 1) with reference to FIGS. The patient terminal 40 here is an example of an information processing device. Fig. 18 is a diagram illustrating an example of a processing sequence according to the third embodiment. Note that in Fig. 18, parts corresponding to those in Fig. 17 are assigned the same reference numerals.

[0124] <Step 101> Step 101 is the same as in embodiment 1. That is, the patient records the measured values, reflections, and the like through the patient application running on the patient terminal 40.

[0125] <Step 121> The patient terminal 40 accepts a display operation for the personal data through the patient application. FIG. 19 is a diagram for explaining a method for reading out my data from the menu screen 421. In FIG. The menu screen 421 can be read from the home screen 401 (see FIG. 8). The menu screen 421 shown in FIG. 19 has a "Blood Pressure Measurement" button, a "Review" button, a "Start Program" button, a "Behavioral Goal List" button, a "Social Support" button, a "Quiz" button, a "Consultation Room" button, a "My Data" button, and the like. In step 121, the "My Data" button is operated.

[0126] <Step 122> The patient terminal 40 generates a My Data screen 407 (see FIG. 8). However, at this stage, the My Data screen 407 is not displayed on the patient terminal 40.

[0127] <Step 107> The patient terminal 40 extracts information portions where predetermined changes appear relative to the comparison target. In the present embodiment, the extraction of information portions where predetermined changes appear relative to the comparison target is assumed to be the display portion of retrospective information. For example, the comparison target is set to a periodic goal being managed by the patient app. Furthermore, for example, the predetermined change is assumed to be a change in behavior to achieve the periodic goal.

[0128] <Step 123> The patient terminal 40 presents a My Data screen 407 (see FIG. 19) in which the extracted information portion has been changed to a different form from the other information portions. As shown in FIG. 8, the My Data screen 407 displays a list of various recorded data. The My Data screen 407 shown in FIG. 19 displays blood pressure data and retrospective data.

[0129] In the case of the retrospective data shown in Figure 19, a portion 407A of the retrospective information for "2024 / 5 / 25," when the periodic goal for "exercise," one of the behaviors managed by the patient app, was achieved, is highlighted. Specifically, the portion "I was able to walk my dog ​​1 km further than usual early in the morning" is highlighted. Therefore, even when reviewing information reflecting on a month, for example, it is easy to find the part where the periodic goal was achieved.

[0130] <Summary> In this embodiment, when the patient displays the My Data screen 407, the part of the retrospective information in which a predetermined change appears compared to the comparison subject can be highlighted. Therefore, when reviewing the retrospective information that the patient has recorded, the patient can easily find the portion of the record where the period goal was achieved. In particular, the retrospective information is recorded for many days and contains a large amount of text. However, with the function described in this embodiment, the patient can efficiently review their own records.

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

[0132] (2) The processor in the above-described embodiments refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPUs (=Central Processing Units)) as well as dedicated processors (e.g., GPUs (=Graphical Processing Units), ASICs (=Application Specific Integrated Circuits), FPGAs (=Field Programmable Gate Arrays), programmable logic devices, etc.). Furthermore, the operations of the processors in each of the above-described embodiments may be performed by multiple processors working together, rather than by a single processor. The order in which the processors perform the operations is not limited to the order described above, and may be changed individually.

[0133] (3) In the above-described embodiment, the calculation requirements for medical fees under the public medical insurance system are assumed, but information regarding the applicability of medical fees under the private medical insurance system may also be displayed on the work screen of the doctor terminal 30 (see FIG. 1). For example, if the requirements for approval of calculation of medical fees under the private medical insurance system require the use of a specific app or medical treatment that refers to patient data entered through a specific app, the explanation of the above-described embodiment can be applied.

[0134] (4) In the above-mentioned first and second embodiments, the function of highlighting information parts that show a predetermined change compared to the comparison target using the “display column for the list of response results to inquiries” 316 (see FIG. 15) was described. However, the above-mentioned function does not have to be limited to the "display column for a list of response results to inquiries" 316 (see FIG. 15) as long as it is a patient data viewing screen provided to a doctor, etc. For example, in the "display column for review information" 314 (see FIG. 12) on the patient data viewing screen 310 (see FIG. 12), information parts in which a predetermined change appears compared to the comparison target may also be highlighted. Incidentally, in the above-mentioned first and second embodiments, the answers are given by selecting from options, but the answers may also be given by inputting text (including inputting numerical values), by registering an image (for example, a photograph or video), or by voice.

[0135] (5) In the third embodiment described above, a function for highlighting the portion of the review information recorded through the patient app in which the periodic goal has been achieved has been described. However, the above-described functions may be applied to display portions of other information displayed on My Data screen 407. Also, the above-described functions may be applied to screens other than My Data screen 407. Incidentally, the above-mentioned third embodiment is based on the assumption of text input, but it is also possible to record by selecting an option, input a number, register an image (e.g., a photograph or video), or register audio.

[0136] (6) In the first embodiment, an example of a predetermined change is described as an improvement over the previous period or an initial value, but deterioration may also be included, or differences in the degree of improvement may be distinguished. 20 is a diagram illustrating a display example in which two types of changes relative to a comparison subject are highlighted in different ways. In FIG. 20, parts corresponding to those in FIG. 14 are assigned the same reference numerals. The viewing screen 310 shown in FIG. 20 is composed of a "patient information column" 311, a "behavioral goal implementation status display column" 318, and a scroll bar 317.

[0137] In the case of Figure 20, among the answers corresponding to "2023.12.8", all answers except for the answer about "sleep" show improvements in content compared to the answers from the previous period. For this reason, the six answers other than "sleep" are highlighted in Figure 20. The improvement in content here is an example of the first change. Furthermore, the six answers other than "sleep" are an example of the third information portion.

[0138] Let's look at the next period, June 8, 2024. The answers regarding "weight loss," "exercise," "stress," and "alcohol consumption" for this period have improved compared to the answers for the previous period. On the other hand, the answers regarding "reducing salt intake" have deteriorated compared to the answers for the previous period. The answers regarding "sleep" and "smoking" are the same as the answers for the previous period. For this reason, the answer "reducing salt intake," which has deteriorated compared to the previous period, and the four answers "weight loss," "exercise," "stress," and "drinking alcohol," which have improved compared to the previous period, are highlighted.

[0139] However, the style of highlighting used for the response "reducing salt," which has deteriorated, is different from the style of highlighting used for the responses "weight loss," "exercise," "stress," and "drinking alcohol," which have improved. The four answers, "weight loss," "exercise," "stress," and "drinking," are examples of the third information section. The deterioration of content is an example of the second change, and the corresponding answer, "reducing salt intake," is the fourth information section. In addition, different degrees of improvement and different degrees of deterioration may be distinguished, and the corresponding answers may be highlighted so that the viewer (e.g., a doctor or a patient) can distinguish them on the screen. For example, the display color or saturation may be changed between the third information part and the fourth information part.

[0140] (7) In the above-described embodiment, information that has been improved over the comparison target is highlighted, but it is also possible to select not to highlight the information depending on the degree of improvement. The degree of improvement here is an example of a predetermined improvement. For example, if the information portion is a numerical value, an operation may be adopted in which if the difference in the numerical value from the comparison target exceeds a threshold, it is considered to be an improvement, and if it does not exceed the threshold, it is not considered to be an improvement. For example, if the information portion is an image, the condition of the affected area, etc. may be scored using image recognition or AI evaluation, and the change in score may be compared with a threshold to determine whether or not the condition is considered to have improved. For example, if the information portion is an audio file or text that has been recognized by voice recognition, the content of the speech may be scored using voice recognition or AI evaluation, and the change in score may be compared with a threshold to determine whether or not it is considered an improvement. The same emphasis on improvements over comparison targets can also be applied to deterioration.

[0141] (8) In the second embodiment described above, the generation AI server 50 is instructed to extract information portions that exhibit predetermined changes relative to the comparison target. However, the doctor terminal 30 or the patient terminal 40 may instruct the generation AI server 50 to extract information portions where a predetermined change appears. The doctor terminal 30 and the patient terminal 40 here are examples of information processing devices.

[0142] (9) In the above-described embodiment, a viewing screen for blood pressure values ​​recorded through a patient app prescribed for the treatment of hypertension is assumed, but for other diseases, viewing screens for different measurement values ​​are prepared. For example, in the case of nicotine addiction, a viewing screen is prepared that displays, for example, the amount of nicotine intake, the number of times a medium containing nicotine has been taken, the number of times a medium containing nicotine has been taken, and the measured value of the CO concentration in the breath.

[0143] In addition, if the person is an alcoholic, a screen for viewing the measured amount of alcohol intake is prepared. In addition, for NASH or obesity, a screen for viewing weight measurements, for example, is provided. In addition, for insomnia, a viewing screen is provided for recording, for example, the amount of sleeping pills taken and the total score of the Pittsburgh Sleep Quality Index (PSQI), which is defined by 24 items. Other diseases contemplated include, for example, kidney disease, cancer, chronic heart failure, attention deficit hyperactivity disorder, depression, tinnitus, delayed grief disorder, opioid-induced constipation, post-mastectomy pain syndrome, bronchial asthma, and nephrotic syndrome.

[0144] (10) In the above-described embodiment, the data recorded through the patient app is treated as “health-related data.” That is, information portions showing predetermined changes are extracted from the data recorded by the program located in the medical device. However, the information portion in which a predetermined change occurs relative to the comparison target is not limited to data recorded through a program located in a medical device, but may also include data recorded through a program located in a non-medical device.

[0145] Programs that are positioned as non-medical devices are also programs that behavior change users use to record health-related data. In the following, programs that are classified as non-medical devices will be referred to as "non-patient apps." FIG. 21 is a diagram illustrating an embodiment in which "health-related data" recorded via a non-patient app and "health-related data" recorded via a patient app are used in combination.

[0146] The horizontal axis in Figure 21 is the time axis. The right end of the time axis is the consultation date, and the left end is the past tense. Figure 21 shows up to 7 months ago. In the case of FIG. 21, the prescription date of the patient app is between three months and four months ago. Before being prescribed the patient app, the patient (i.e., the user) records "health-related data" through the non-patient app. The "health-related data" may be recorded only on the patient terminal 40, only on the management server 60, or on both the patient terminal 40 and the management server 60. The management server 60 is, for example, a server operated by a business operator that provides the non-patient app.

[0147] Non-patient apps in this context are sometimes called healthcare apps. Healthcare apps are programs whose primary purpose is to record health information and are not medical devices. In the case of Fig. 21, the "health-related data" recorded through the non-patient app before the patient app is prescribed is imported from the patient terminal 40 or the management server 60 to the PDT server 20. Of course, when importing, the identity of the user is confirmed using a user account or the like.

[0148] Therefore, on the day of the consultation, the PDT server 20 stores not only about four months of "reviews" after the patient app is prescribed, but also about three months of "health data" before the patient app is prescribed. In other words, the PDT server 20 stores about seven months of "health data" of the patient. In the case of the embodiment described above, the information portion in which the predetermined change appears is highlighted for a maximum of four months after the prescription date. However, in the embodiment described using Figure 21, the "health data" before treatment using the patient app is started is also included, and it is possible to highlight information parts where specified changes appear.

[0149] (11) In the above-described embodiment, it is assumed that the consultation date falls within the insured medical treatment period. However, it may also be possible to highlight information portions in which predetermined changes appear in “health data” recorded through a program that is positioned as a non-medical device even after the insured medical treatment period. FIG. 22 is a diagram illustrating another embodiment in which "health-related data" recorded through a non-patient app and "health-related data" recorded through a patient app are used in combination.

[0150] The horizontal axis in Figure 22 is the time axis. The right end of the time axis is the consultation date, and the left end is the past tense. Figure 22 shows up to 7 months ago. In the case of Figure 22, the prescription date in the patient app is 7 months ago, and the insured medical treatment period expired within the period 2 months before the consultation date. In the case of Figure 22, after the expiration of the insured medical treatment period, a medical treatment period not covered by insurance (i.e., outside the insured medical treatment period) begins.

[0151] 22 assumes that a patient app continues to be used after the validity period has expired to record "health-related data" outside of the insured medical treatment period. In other words, it assumes that a patient app continues to be used as a non-patient app after the validity period has expired. For this reason, not only "health-related data" during the insured medical treatment period but also "health-related data" outside of the insured medical treatment period is recorded in the PDT server 20.

[0152] However, the "health-related data" may be recorded on the patient terminal 40 or the management server 60 using a non-patient app that is different from the patient app used during the insured medical treatment period. If the "health-related data" recorded through the non-patient app is not stored in the PDT server 20, the "health-related data" is imported from the patient terminal 40 or the management server 60 to the PDT server 20.

[0153] (12) In the above-described embodiment, the generation AI server 50 (see FIG. 17) extracts information portions of the "health-related data" that show predetermined changes compared to the comparison target. However, if the PDT platform 10 (see Figure 1), PDT server 20 (see Figure 1), doctor terminal 30 (see Figure 1), and patient terminal 40 (see Figure 1) have a trained model, any of these terminals may extract information from the "health-related data" that shows a specified change compared to the comparison subject.

[0154] (13) In the above-described embodiment, the patient app is assumed to be a program located in a medical device, but it may be a program located in a non-medical device. In other words, it may be assumed that all "health-related data" is recorded through a program located in a non-medical device. In this case, as in the above-described embodiment, the generation AI server 50 (see FIG. 17) or the like may extract information portions that exhibit predetermined changes relative to the comparison target.

[0155] (14) In the above embodiment, the case where the app used to record health-related data is a patient app or a healthcare app has been described. However, the type of app used to record health-related data is not limited, and the type of app may be, for example, a diary app, an image app, or an audio app.

[0156] <Summary> The disclosed examples described in the above-mentioned embodiments are shown below. (((1))) An information processing device having one or more processors, which acquire health-related data input by a user who is changing their behavior, and presents information portions of the health-related data in which a predetermined change occurs relative to a comparison subject in a manner different from other information portions. This information processing device can assist users who change their behavior in reviewing records entered by them.

[0157] (((2))) The information processing device according to (((1))), wherein the one or more processors use a second information portion corresponding to the information portion in the immediately previous target period as a comparison target. This information processing device can assist in reviewing information parts that have undergone a predetermined change over a period of time.

[0158] (((3))) The information processing device according to (((1))), wherein the one or more processors compare an initial value corresponding to the information portion. This information processing device can assist in reviewing information parts that have undergone predetermined changes relative to their initial values.

[0159] (((4))) The information processing device according to (((1))), wherein the one or more processors use the user's therapeutic goals as a comparison target. This information processing device can assist in reviewing information that has undergone a predetermined change from the initial therapeutic value.

[0160] (((5))) The information processing device according to (((1))), wherein the one or more processors use a target managed by a program used to record health-related data as a comparison target. This information processing device can assist in reviewing information that has undergone a predetermined change with respect to a target being managed by a program.

[0161] (((6))) The information processing device according to (((1))), wherein the one or more processors use a response from a user to a query from a program used to record health-related data as the information portion that changes the presentation manner. This information processing device can assist in reviewing answers that have undergone predetermined changes.

[0162] (((7))) The information processing device described in (((1)))) in which the one or more processors use at least one of the following health-related data: a record of the user's behavior, a record of the user's mood, a record of an image by the user, and a record of the user's voice as the information part that changes the presentation manner. This information processing device can assist in reviewing records in which a predetermined change has occurred.

[0163] (((8))) The information processing device according to (((1))), wherein the one or more processors present information portions that show a predetermined improvement over a comparison target in a manner different from other information portions. This information processing device can assist in reviewing records that show a predetermined improvement over a comparison target.

[0164] (((9))) The information processing device described in (((1))), wherein the one or more processors present the third information portion in which the first change appears and the fourth information portion in which the second change appears in relation to the comparison subject in different manners. This information processing device can assist in reviewing by distinguishing between differences in changes.

[0165] (((10))) An information provision method in which a computer acquires health-related data entered by a user whose behavior is changing, and presents information portions of the health-related data that show a predetermined change relative to a comparison subject in a manner different from other information portions. This information providing method can assist users who are changing their behavior in reviewing records entered by them.

[0166] (((11))) A program for enabling a computer to acquire health-related data entered by a user who is changing their behavior, and to present information in the health-related data that shows a predetermined change relative to a comparison subject in a manner different from other information. This program can assist users in reviewing records entered by users who are changing their behavior. [Explanation of symbols]

[0167] 10...PDT platform, 20, 20A, 20B, 20C, 20D, 20E, 20F...PDT server, 30...doctor's terminal, 40...patient's terminal, 50...generation AI server, 60...management server

Claims

1. having one or more processors, the one or more processors: Obtain health data entered by users who want to change their behavior; presenting, in a different manner from the rest of the health-related data, information portions showing a predetermined change relative to a comparison subject; Information processing device.

2. the one or more processors: a second information portion corresponding to the information portion in the immediately preceding target period is used as the comparison target; The information processing device according to claim 1 .

3. the one or more processors: an initial value corresponding to the information portion is used as the comparison target; The information processing device according to claim 1 .

4. the one or more processors: The comparison is made with the user's therapeutic goal. The information processing device according to claim 1 .

5. the one or more processors: The comparison object is a goal managed by a program used to record the health-related data. The information processing device according to claim 1 .

6. the one or more processors: a response from the user to a query from a program used to record the health-related data being used as the information portion whose presentation is changed; The information processing device according to claim 1 .

7. the one or more processors: At least one of a record of the user's behavior, a record of the user's mood, a record of an image by the user, and a record of a voice by the user is set as the information portion whose presentation manner is changed among the health-related data. The information processing device according to claim 1 .

8. the one or more processors: presenting the portion of the information that exhibits a predetermined improvement over a comparison subject in a different manner; The information processing device according to claim 1 .

9. the one or more processors: presenting a third information portion in which the first change appears and a fourth information portion in which the second change appears in a manner different from that of the comparison object; The information processing device according to claim 1 .

10. The computer Obtaining health-related data entered by a behavior-changing user; a process of presenting, in a different manner from the rest of the health-related data, information portions showing a predetermined change relative to a comparison subject; Information provision method to carry out.

11. On the computer, A function to capture health data entered by a user who modifies their behavior; a function of presenting, in a different manner from the rest of the health-related data, information portions showing a predetermined change relative to a comparison subject; A program to achieve this.

Images