Information processing device, information provision method and program

Abstract

To provide a mechanism for generating a document that supports a systematic medical treatment plan using data recorded through a terminal operated by a user who modifies behavior.SOLUTION: An information processing device has one or more processors. The one or more processors accept output of a document supporting a medical treatment plan, generate a goal and information on the progress of goal achievement from data recorded through a terminal operated by a user who modifies behavior, and output a document including the generated goal and information on the progress of goal achievement.SELECTED DRAWING: Figure 16

Description

[Technical Field]

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

[0002] As of May 2024, the payment of lifestyle-related disease management fees requires the attachment of a treatment plan. For this reason, there are services available that create treatment plans required for the payment of lifestyle-related disease management fees based on medical interview and test results. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] "Recabal", [online], [searched April 17, 2024], Internet<URL:https: / / recoval.jp / > Summary of the Invention [Problem to be solved by the invention]

[0004] Currently, the main medical fees for hypertension, dyslipidemia, and diabetes are calculated as specific disease treatment management fees, and no treatment plan is required to be attached. However, with the revision of medical fees to take effect on June 1, 2024, hypertension, dyslipidemia, and diabetes will be excluded from the scope of calculation of the specified disease medical care management fee. As a result, it is expected that medical fees for hypertension, dyslipidemia, and diabetes will mainly be calculated as lifestyle-related disease management fee (I) or (II). In other words, medical fees for hypertension, dyslipidemia, and diabetes will also require the attachment of a medical care plan. Treatment plans are not just a way to share information between medical institutions and patients, but are also expected to serve as a tool to encourage patients to actively participate in their own treatment.However, creating a treatment plan can be quite a burden.

[0005] One aspect of the present disclosure provides a mechanism for generating a document that supports a treatment plan using data recorded through a terminal operated by a user who modifies behavior. [Means for solving the problem]

[0006] The invention described in claim 1 is an information processing device having one or more processors, which accepts the output of a document that supports a treatment plan, generates goals and information regarding the status of goal achievement from data recorded through a terminal operated by a user who is changing their behavior, and outputs the document including the generated goals and information regarding the status of goal achievement. The invention described in claim 2 is the information processing device described in claim 1, wherein the one or more processors generate a graph of measurement values ​​extracted from the data as information regarding the progress of the goal. The invention described in claim 3 is an information processing device described in claim 1, wherein the one or more processors extract records of measurement values ​​from the data and generate information indicating changes in the measurement values ​​over a predetermined period as information regarding the progress of the goal. The invention described in claim 4 is an information processing device described in claim 1, wherein the one or more processors extract actions that result in goal achievement from the data and output the extracted actions as information regarding the status of goal achievement. The invention described in claim 5 is an information processing device described in claim 1, wherein the one or more processors extract behaviors currently being performed by the user from the data and output the extracted behaviors as information regarding the progress of achieving the goal. The invention described in claim 6 is an information processing device described in claim 5, wherein the one or more processors generate a summary of the user's behavior contained in the data and output the generated summary as the behavior currently being performed. The invention described in claim 7 is an information processing device described in claim 1, wherein the one or more processors evaluate actions related to the goals of the data based on predetermined criteria and output the results of the evaluation as information regarding the status of achievement of the goals. The invention described in claim 8 is an information processing device described in claim 1, wherein the one or more processors extract progress status for each management item of the application program executed on the terminal from the data, and output the extracted progress status for each management item as information regarding the achievement status of the goal. The invention described in claim 9 is the information processing device described in claim 1, wherein the one or more processors extract behavioral goals that the user has set or is currently practicing from the data, and output the extracted behavioral goals to a behavioral goal column of the document. The invention recited in claim 10 is the information processing device recited in claim 9, wherein the one or more processors accept an editing operation on the content output in a behavioral goal column of the document. The invention described in claim 11 is an information processing device described in claim 1, wherein the one or more processors extract quantitatively identified goals from the data and output the extracted goals to a column for achievement goals in the document. The invention described in claim 12 is the information processing device described in claim 11, wherein the one or more processors accept an editing operation on the content output in a column of the goal to be achieved of the document. The invention described in claim 13 is an information processing device described in claim 1, wherein the one or more processors extract progress status for each management item of the application program executed on the terminal from the data, generate guidance information according to the progress status for each management item, and output the generated guidance information to an item column related to guidance of the document. The invention described in claim 14 is an information processing device described in claim 1, wherein the one or more processors accept output of the document through operations on a viewing screen of the data input through the terminal operated by the user. The invention described in claim 15 is an information processing device described in claim 1, wherein the one or more processors accept output of the document through operations on a management screen that displays a list of the usage status of application programs prescribed to the user. The invention described in claim 16 is the information processing device described in claim 1, wherein the one or more processors accept output of the document through an operation of opening a browser tab. The invention described in claim 17 is an information provision method in which a computer executes the following processes: a process of accepting output of a document that supports a treatment plan; a process of generating information about goals and the status of goal achievement from data recorded through a terminal operated by a user who changes their behavior; and a process of outputting the document that includes the generated information about the goals and the status of goal achievement. The invention described in claim 18 is a program for enabling a computer to perform the following functions: accepting the output of a document that supports a treatment plan; generating information regarding goals and the status of goal achievement from data recorded through a terminal operated by a user who changes their behavior; and acquiring the document that includes the generated goals and information regarding the status of goal achievement. [Effects of the Invention]

[0007] According to one embodiment of the present disclosure, a mechanism can be provided for generating a document that supports a medical treatment plan using data recorded through a terminal operated by a user who changes his or her behavior. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an overall configuration of an information processing system. [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 executed in the information processing system. [Figure 8] FIG. 10 is a diagram illustrating an example of an operation screen in a patient application. [Figure 9] FIG. 1 is a diagram illustrating a treatment program. [Figure 10] 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 11] FIG. 10 is a diagram illustrating an example of a patient data viewing screen. [Figure 12] FIG. 10 is a diagram illustrating a display example of a consultation date registration screen. [Figure 13] 10 is a diagram illustrating an example of the layout of a reception screen for information to be entered in a medical treatment plan. FIG. [Figure 14] FIG. 10 is a diagram illustrating some of the items displayed in the input field for the report content. [Figure 15] FIG. 10 is a diagram illustrating the remaining items displayed in the report content setting field. [Figure 16] FIG. 10 is a diagram illustrating an example of an output of a medical treatment plan. [Figure 17] FIG. 10 is a diagram illustrating another example of output of a medical treatment plan. [Figure 18] FIG. 10 is a diagram illustrating another example of the management screen for the usage status of patient applications displayed on the output device of the doctor terminal. [Figure 19] 10 is a diagram illustrating an example of a browser screen displayed on an output device of a doctor terminal. FIG. 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] "App purpose" refers to the effect that should be achieved by using an app that promotes behavioral change. The purpose of the app varies depending on the disease that the app is designed to promote behavioral change for. For example, app purposes include improving lifestyle habits, maintaining improved lifestyle habits, and maintaining improved values. "App goal" refers to the goal to be achieved by using an app that encourages behavioral change. Goals are defined from the perspective of achieving a purpose. 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. App goals can also be further defined by one or more sub-goals. Sub-goals are smaller-granular 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 (hereinafter also referred to as "patient app data") outside of medical institutions.

[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 the information, or may include other information.

[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 specified for each disease. For example, if the disease is hypertension, blood pressure values ​​are recorded as measurement values. Blood pressure values ​​are specified, for example, as systolic blood pressure (i.e., maximum blood pressure value) and diastolic blood pressure (i.e., minimum blood pressure value). 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] The "activity record" is, for example, a patient app operation history, a medication record, a meal record, a smoking record, a drinking record, and an exercise record. The activity record is an example of information about activity. The "mood record" is, for example, a subjective mood. The mood record is an example of information about mood. The "record of physical condition" is, for example, a subjective physical condition or symptom. The record of physical condition is an example of information related to 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.

[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's 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.

[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, medical institutions also include facilities and organizations that employ these medical professionals. 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] <Overall system> Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. 1 is a diagram illustrating the overall configuration of an information processing system 1. The information processing system 1 shown in FIG. 1 is composed of 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 services as a PDT platform. 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).

[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, stores patient application data input through the patient application, and provides patient data to a doctor terminal (not shown). 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 the 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 every 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 auxiliary storage device 23 stores an operating system and other programs. 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] The other programs also include an application program for generating a recuperation plan document. The recuperation plan document is an example of a document for supporting a recuperation plan. In addition, the auxiliary storage device 23 also records the patient data 230 recorded through the patient app. The communication interface 24 is an interface for communicating with an external terminal 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 the 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. The patient data 230 shown in FIG. 5 stores measured values and other information recorded through the patient app.

[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 the management data of the patient app and the 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 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 of the medical institution that prescribed the patient app. The patient ID and patient name are acquired from the PDT platform 10 (see FIG. 1), for example, when authenticating 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 value and a diastolic blood pressure value.

[0051] The review / input date and time 230C2 records a review of the day's activities 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 activities performed are recorded. The details of the activities consist of the category of the activities performed and text input. In the case of this embodiment, the category of the activities performed is recorded by checking buttons labeled "reduce salt," "loss of weight," "exercise," etc. Other possible labels include, for example, "sleep," "stress," "moderate drinking," and "other." 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," 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 records a target value set by the patient. For example, the target value 230C6 records a blood pressure reduction target set by the patient as a target value in step 3 of the treatment program. The target value here is an example of an achievement goal. A quantitative target is assumed for the target value. The outpatient record 230C7 records appointments with the doctor, the next appointment date, medication timing, etc. The doctor's appointment records appointments that the patient should make or be careful about before the next appointment. In this embodiment, doctor's appointments can only be recorded through the patient app. 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). 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] <Treatment plan output processing> The following describes the process of outputting a treatment plan in the information processing system 1 (see FIG. 1) with reference to FIGS. 7 is a diagram illustrating an example of a processing sequence executed by the information processing system 1 (see FIG. 1). The symbol S in FIG. 7 represents a step.

[0060] <Step 101> Patients record measurements and other information from the patient app's operation screen. For example, patients can record measurements, reflections, behavioral goals, target values, outpatient records, and medication records. 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 the user to record the level of physical condition, stress level, length of sleep, weight, and details of the activity. As mentioned above, the details of the activity include a record of button operations corresponding to the category of the activity that was successfully performed. The details of the activity also include text input. The start program screen 404 is the screen used in "Step 1" of the treatment program.

[0062] Fig. 9 is a diagram for explaining the treatment program. The treatment program shown in Fig. 9 is composed of "Step 1," "Step 2," and "Step 3." "Step 1" is the learning stage. In the learning stage, knowledge is acquired. "Step 1" is made up of multiple chapters. There is an order to the multiple chapters, and you cannot move on to the next chapter until you have finished studying one chapter. Once you have finished studying all the chapters, you can move on to "Step 2." In "Step 1," the patient is first asked to enter information about their employment status, preferences, etc. Next, the patient's characteristics are analyzed from the entered information.

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

[0064] "Step 2" is the stage where behavioral goals are put into practice. First, in "Step 2," appropriate behavioral goals are presented to the patient from among "reducing salt," "reducing weight," "exercise," "sleep," "stress," and "alcohol." 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.

[0065] In "Step 2," specific behavioral goals are presented for multiple behavioral categories that represent lifestyle habits that will improve the disease. Behavioral categories include, for example, "reducing salt intake," "weight loss," "exercise," "sleep," "stress," and "alcohol." For example, behavioral goals in the "reducing salt intake" category include "avoiding salty snacks such as snacks and rice crackers," "avoiding drinking the broth of udon or ramen noodles," "avoiding 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." Once behavioral goals for all behavioral categories have been achieved, the patient can move on to "Step 3." The target duration for "Step 2" is one month.

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

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

[0068] The My Data screen 407 is a screen used to check the progress of steps, measurement values, 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 screen 411 is a screen on which medication records and record contents can be viewed.

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

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

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

[0072] The management screen 300 shown in FIG. 10 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.

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

[0074] The management screen 300 shown in FIG. 10 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. 10, the information field 301 is displayed in a table format. Incidentally, information for each patient is displayed in the rows, and management items of the patient app are displayed in the columns. FIG. 10 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.

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

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

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

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

[0079] <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. 10) described above. Specifically, the doctor terminal 30 accepts the operation of the "Details" button 303. For example, the doctor terminal 30 accepts the operation of the "Details" button 303 corresponding to Mr. E, for whom more than three months have passed since the prescription date. 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.

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

[0081] <Step 106> The PDT server 20, which has been accessed by the doctor terminal 30, generates a patient data viewing screen 310 (see FIG. 11) for the selected patient. FIG. 11 is a diagram illustrating an example of a patient data viewing screen 310. The viewing screen 310 shown in FIG. 11 is composed of a “patient information field” 311, a “measurement result display field” 312, a “blood pressure target value field” 313, a “review information display field” 314, an “activity record display field” 315, a “Go to examination date registration screen” button 316, a “treatment plan” button 317, and an “exit” button 318.

[0082] The "patient information column" 311 shown in FIG. 11 indicates that the medical record number is "12754," the patient name is "Mr. E," 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 11. Daily measurement values ​​can be entered on the measurement value input screen 402 (see Figure 8). In the case of FIG. 11, the average values ​​for two intervals, "8 weeks to 4 weeks ago" and "4 weeks ago to the day before," are shown. Here, the day before means 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.

[0083] The "blood pressure reduction target value field" 313 shown in Figure 11 indicates that the target value for systolic blood pressure is less than 125 mmHg and the target value for diastolic blood pressure is less than 75 mmHg. In Figure 11, the "blood pressure reduction target value field" 313 has a "change" button for the target value. Only a doctor or the like can change the target time. Records of mood and physical condition are displayed in the "retrospective information display field" 314 shown in Fig. 11. The retrospective information can be input from the above-mentioned retrospective input screen 403 (see Fig. 8).

[0084] The activity record display field 315 shown in Figure 11 displays activity records 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. The "Go to consultation date registration screen" button 316 shown in FIG. 11 is a button for opening the consultation date registration screen 320 (see FIG. 12). The "Treatment plan" button 317 shown in FIG. 11 is a button for receiving an instruction to output a treatment plan. The "Exit" button 318 shown in FIG. 11 is a button for closing the patient data viewing screen 310.

[0085] Fig. 12 is a diagram illustrating a display example of the examination date registration screen 320. In Fig. 12, parts corresponding to those in Fig. 11 are assigned the same reference numerals. The appointment date registration screen 320 shown in Figure 12 is composed of a patient information column 311, a column 321 for displaying appointments with the patient, an insurance calculation information column 322, an appointment history column 323, a "Return to previous screen" button 324, and an "End appointment" button 325. 12, the appointment display field 321 displays advice and explanations from a doctor or the like, as well as the history of appointment details and the degree of achievement during previous consultations. As described above, in this embodiment, the appointment details and the degree of achievement are registered by the patient via the patient app.

[0086] The insurance calculation information field 322 shown in Figure 12 displays the date of the current consultation and a selection button for whether or not you wish to use insurance calculation for this consultation. In the case of Figure 12, the consultation date can be entered from a calendar. In the case of Figure 12, the doctor or other person can select whether or not to use insurance calculation for this consultation. "Yes" is selected in the insurance calculation information field 322 in Figure 12. However, even if the doctor or other medical professional wants to make the treatment eligible for insurance calculation, if the patient's recording of patient data does not meet the calculation requirements, the calculation of medical fees will not be approved. If it is clear that medical fees cannot be calculated, it is also possible to select "No." For example, if medical fees are limited to once a month, and this medical treatment occurs in the same month as the previous medical treatment for which medical fees were calculated, "No" would be selected.

[0087] The medical examination history column 323 shown in FIG. 12 displays a number of medical examination dates, including the most recent medical examination date, and the results of insurance calculation. The "return to previous screen" button 324 is a button for returning to the patient data viewing screen 310 (see FIG. 11). The "End Consultation" button 325 is a button for ending the consultation by closing the consultation date registration screen 320. Closing the consultation date registration screen 320 also means closing the patient data viewing screen 310 (see FIG. 11).

[0088] <Step 107> Returning to the explanation of Figure 7. After the doctor or other medical professional performs medical treatment based on the presented patient data viewing screen 310 (see FIG. 11), etc., the doctor or other medical professional instructs the output of the medical treatment plan. In other words, the doctor terminal 30 accepts the output of the medical treatment plan. Specifically, the doctor terminal 30 accepts the operation of the "medical treatment plan" button 317 (see FIG. 11). The doctor terminal 30 notifies the PDT server 20 of the receipt of the output of the treatment plan.

[0089] <Step 108> The PDT server 20 presents to the doctor terminal 30 a reception screen 330 (see FIG. 13) for items to be entered in the treatment plan. FIG. 13 is a diagram illustrating an example of the layout of a reception screen 330 for items to be entered in a medical treatment plan. The reception screen 330 shown in FIG. 13 is composed of a title field 331 , a “Create new” button 332 , an output history field 333 , a report content setting field 334 , and an output image field 335 .

[0090] The title field 331 shown in Fig. 13 states "Lifestyle-related disease treatment plan report." In the explanation of Fig. 13, it is simply referred to as "report." The "Lifestyle-related disease treatment plan report" in FIG. 13 means that it is a treatment plan or a document that meets the conditions of a treatment plan. The "Create new" button 332 is a button for instructing the creation of a new report. When the "Create new" button 332 is operated, information in which all or some of the input items are blank is displayed in the report content setting field 334. Note that the output image field 335 displays an output image that reflects the content entered in the input items. Therefore, the output image immediately after the "Create new" button 332 is operated will have many blank items.

[0091] The output history field 333 is a field for displaying the output history of reports. The output history field 333 displays a list of the creation dates of reports created in the past. When a specific creation date is specified, the report content setting field 334 displays the details of the corresponding report. Furthermore, the output image field 335 displays the output image of the corresponding report. An input field is displayed for each item field that constitutes the report in the report content setting field 334. When the "Create new" button 332 is operated, input into the input field is possible. The output image field 335 displays an output image of a report that is to be newly created or that was created in the past.

[0092] FIG. 14 is a diagram for explaining some of the items displayed in the report content setting field 334. In the case of Figure 14, the "Setting creation date, etc." field 334A is composed of an input field for the creation date, an input field for the entry date, a check box used to indicate whether or not the entered entry date should be displayed on the report, an input field for the number of times the report is output, and a check box used to indicate whether or not the entered number of times the report is output should be displayed on the report.

[0093] In the case of Fig. 14, the "Format Designation" field 334B is composed of a selection field used to indicate whether or not to use the "Ministry of Health, Labour and Welfare format," and a pull-down menu used to indicate whether or not to use the format for continuation. In the case of Fig. 14, the "Ministry of Health, Labour and Welfare format" is not being used. Also, in the case of Fig. 14, "continuation" has been selected. In the case of Fig. 14, the "basic patient information" column 334C is made up of the patient's name, sex, and date of birth. In the case of Fig. 14, the sex column is blank.

[0094] In the case of FIG. 14, the "main disease" field 334D displays the main disease for which the report is to be created. Since the main disease is related to the patient app, the PDT server 20 (see FIG. 1) displays the main disease corresponding to the patient app. In the case of FIG. 14, the "main disease" field 334D displays "hypertension." Needless to say, the name of the disease displayed in the main disease field 334D differs depending on the patient app. For example, it may be "diabetes," "dyslipidemia," or "NASH."

[0095] In the case of Fig. 14, the target blood pressure values ​​are displayed in the "target" column 334E. In the case of Fig. 14, the target value for systolic blood pressure is 125 mmHg, and the target value for diastolic blood pressure is 75 mmHg. The initial value in the "target" column 334E may be the blood pressure value set by a doctor or the like in the "blood pressure reduction target value column" 313 (see FIG. 11). Needless to say, the content and values ​​displayed in the target column differ depending on the disease. For example, for "diabetes," target values ​​such as blood glucose level and Hba1c level are displayed. For example, for "dyslipidemia," target values ​​for cholesterol and triglycerides are displayed. For example, for "NASH," target weight is displayed.

[0096] In the case of Figure 14, the "Goal Achievement Status" column 334F displays blood pressure measurement values ​​recorded through the patient app. The "Goal Achievement Status" column 334F shown in Figure 14 displays the measurement values ​​of "average home blood pressure one week from start" and "average home blood pressure from the previous day to one week ago." Note that "start" refers to the day when recording of blood pressure measurement values ​​through the recording app began. Additionally, "previous day" refers to the day before the creation date. Needless to say, measurement values ​​according to the disease are displayed. "One week" in Figure 14 is an example of a predetermined period. Needless to say, "one week" is just an example, and a period longer than one week, such as "two weeks" or "10 days," may also be used. A period shorter than one week, such as "three days," may also be used. In the case of Figure 14, by displaying the measured values ​​for two periods, it can be seen that the average home blood pressure from the previous day to one week ago is closer to the blood pressure reduction target than the average home blood pressure from the start to one week ago.

[0097] In the case of FIG. 14, two options, "Set in app" and "Other," are displayed in the "Goal" field 334G in the form of radio buttons. When "Set in app" is selected, for example, the blood pressure reduction target recorded in target value 230C6 (see FIG. 5) in patient app data 230C (see FIG. 5) is extracted. The blood pressure reduction target is an example of a quantitatively specified target. The target entered in the "achievement target" field 334G here is an example of information regarding the achievement status of the target.

[0098] However, for patients whose treatment program step is "Step 2," behavioral goal 230C5 (see FIG. 5) is blank. In this case, when "Set in app" is selected, the behavioral goal recorded in behavioral goal 230C5 (see FIG. 5) set in step 2 is extracted. If the patient app allows the setting of a target goal separate from the blood pressure control goal, the target goal set through the patient app will be extracted. In this case, the final blood pressure control goal can also be set as a target in Step 2 of the treatment program. However, if "Set with app" is selected, a standard phrase such as "Improve your lifestyle habits using the patient app" may be output. On the other hand, if "Other" is selected, the doctor or other person can input any text.

[0099] FIG. 15 is a diagram illustrating the remaining items displayed in the report content setting field 334. In the case of FIG. 15, the "Behavioral Goal" field 334H displays two options in the form of radio buttons: "Set in app" and "Other." When "Set in app" is selected, for example, the behavioral goal recorded in behavioral goal 230C5 (see FIG. 5) of patient application data 230C (see FIG. 5) is extracted. The behavioral goal here is the behavioral goal set by the patient himself / herself in step 2 or step 3 of the treatment program. In addition, when "Set in app" is selected, the behavioral goal recorded as "Appointment with doctor" in outpatient record 230C7 (see FIG. 5) may be extracted.

[0100] Furthermore, if "Set in App" is selected, the behavioral goal being practiced in the treatment program may be extracted. The behavioral goal being practiced may be extracted, for example, from "Treatment Program Practice History" 230C4 (see FIG. 5). The behavioral goal may be a quantitatively specified goal or a qualitatively specified goal. However, when "Set in app" is selected, a fixed phrase such as "Set in patient app" may be output. On the other hand, if "Other" is selected, the doctor or other person can input any text.

[0101] In the case of Figure 15, the "Areas to focus on and items for guidance" column 334I allows doctors and other medical professionals to set areas to focus on and items requiring guidance from the perspective of the treatment plan. In the case of Figure 15, "diet," "exercise," "tobacco," and "other" are shown in the form of check boxes as potential areas to focus on. Items entered in areas with checked check boxes will be included in the report. On the other hand, items entered in areas with unchecked check boxes will not be included in the report. In the case of Figure 15, the checkboxes corresponding to all four areas are checked.

[0102] Incidentally, for "Diet" and "Exercise," two checkboxes are displayed: "Set in app" and "Other." Because they are checkboxes, it is possible to check both "Set in app" and "Other." It is also possible to leave neither "Set in app" nor "Other" checked. If "Other" is checked, doctors and others can freely enter comments.

[0103] For example, if the "Set in app" checkbox for "Diet" is checked, behavioral goals managed in the patient app for "Reduce salt intake," "Reduce weight," and "Alcohol intake" are extracted. However, behavioral goals related to behaviors that have been confirmed to have been achieved in the "Treatment program practice history" 230C4 (see Figure 5) are excluded.

[0104] Similarly, if the "Set in app" checkbox for "exercise" is checked, behavioral goals managed in the patient app for "exercise," "sleep," and "stress" are extracted. However, behavioral goals related to behaviors confirmed to have been achieved in the "treatment program practice history" 230C4 (see Figure 5) are excluded. For "Tobacco," two items are displayed in checkbox format: "Effectiveness of Smoking Cessation / Smoking Reduction" and "Implementation Methods of Smoking Cessation." Because it is in checkbox format, it is possible to check both the "Effectiveness of Smoking Cessation / Smoking Reduction" and "Implementation Methods of Smoking Cessation." It is also possible to check neither the "Effectiveness of Smoking Cessation / Smoking Reduction" nor the "Implementation Methods of Smoking Cessation."

[0105] For "Other," two checkboxes are displayed: "Practice the behaviors suggested by the app" and "Other." Because they are checkboxes, it is possible to check both "Practice the behaviors suggested by the app" and "Other." It is also possible to check neither "Practice the behaviors suggested by the app" nor "Other." If "Other" is checked, doctors and other medical professionals can freely enter comments.

[0106] In the case of FIG. 15, a doctor or the like can freely enter comments in the "comments" field 334J. 15, the name of the doctor, etc. is entered in the "Doctor's Name" column 334K. Entering the name of the doctor, etc. is mandatory, just like the "Patient Basic Information" column 334C, etc. In the case of Figure 15, the "Explanation to patient: The patient has received an explanation about the contents of the treatment plan and fully understood it" column 334L is displayed in the form of a check box. If the check box is not checked, the "Save" button 334N and the "Save and print" button 334O cannot be operated. 15, the "I have confirmed the contents of the plan" field 334M is displayed in the form of a check box. If the check box is not checked, the "Save" button 334N and the "Save and print" button 334O cannot be operated.

[0107] Incidentally, when the "Save" button 334N is operated, document data reflecting the contents set in the report content setting field 334 (see FIG. 13) is saved. The document data is saved in the auxiliary storage device 23 (see FIG. 4) of the PDT server 20 (see FIG. 1). However, the document data may also be saved in the auxiliary storage device 33 (see FIG. 6) of the doctor terminal 30 (see FIG. 1). The document data here may be in PDF (Portable Document Format) format, or in the format of a document, spreadsheet, presentation, or other office application. When the "Save and Print" button 334O is operated, the document data reflecting the settings made in the report content setting field 334 (see FIG. 13) is saved and output as a printout. A printout is a piece of paper with letters and figures fixed on its surface.

[0108] <Step 109> Returning to the explanation of Figure 7. The doctor terminal 30 accepts settings for the contents to be written in the report. Specifically, the doctor terminal 30 accepts input and settings for the information to be written in the treatment plan on a reception screen 330 (see FIG. 13). <Step 110> For items for which "Set in app" is selected, the PDT server 20 generates a treatment plan from the patient data. The generated treatment plan (i.e., report) is reflected in the output image field 335 of the reception screen 330 (see FIG. 13) for information to be entered into the treatment plan.

[0109] <Step 111> The doctor terminal 30 accepts editing of the output contents. However, this step is executed only when editing is instructed by a doctor or the like. The doctor terminal 30 notifies the PDT server 20 of the editing contents. <Step 112> The PDT server 20 reflects the edited content in the treatment plan. This step is also executed only when an instruction to edit the treatment plan is given. The edited treatment plan is notified from the PDT server 20 to the doctor terminal 30.

[0110] <Step 113> The doctor terminal 30 saves or prints the medical treatment plan according to the instruction. Fig. 16 is a diagram illustrating an example of an output of a medical treatment plan 336. The medical treatment plan 336 shown in Fig. 16 is an example of an output when "Ministry of Health, Labour and Welfare format" is not selected in the "Format specification" field 334B (see Fig. 14). The treatment plan 336 shown in FIG. 16 is made up of a plurality of sections 336A to 336G. Section 336A contains the items written in the "Setting creation date, etc." column 334A (see Figure 14), the "Patient basic information" column 334C (see Figure 14), the "Main illness" column 334D (see Figure 14), and the "Goal" column 334E (see Figure 14).

[0111] Section 336B is given the title "1. Goal achievement status." In the case of FIG. 16, it is made up of a plurality of sub-sections 336B1 to 336B6. Subsection 336B1 outputs information indicating changes in mean blood pressure values ​​within a predetermined period. In the example of FIG. 16, the predetermined periods are one week from the start date of blood pressure recording and one week immediately preceding the date the treatment plan was created. By displaying the values ​​for the two periods side by side, it is easy to confirm changes in mean blood pressure values ​​within the two periods. Furthermore, by comparing the values ​​with the target value (i.e., 125 / 75 mmHg) included in section 336A, it is easy to understand the progress toward the goal. The output of subsection 336B1 is an example of information regarding the goal and the progress toward the goal.

[0112] Subsection 336B2 outputs information indicating changes in weight over a predetermined period. In the case of FIG. 16, the predetermined period is from the start date of weight recording to the date on which the treatment plan is created. In the example of FIG. 16, a weight loss of 5.2 kg has been achieved. The output of subsection 336B2 is also an example of information regarding goals and the progress of the goals. The information output to the subsections 336B1 and 336B2 is also an example of information indicating changes in measurement values ​​recorded through the patient app.

[0113] Subsection 336B3 displays a graph of changes in measured values ​​over the past few weeks. In the case of FIG. 16, subsection 336B3 displays a time series graph of changes in blood pressure values ​​recorded through the patient app. In the case of FIG. 16, changes in diastolic and systolic blood pressure values ​​over the past three weeks are shown. The graph also displays target values ​​for the diastolic and systolic blood pressures. The target values ​​here are the target values ​​set in the "target" field 334E (see FIG. 14). The output of subsection 336B3 is also an example of information regarding the goal and the progress of the goal. Note that the information output to subsection 336B3 is also an example of information indicating changes in the measurement values ​​recorded through the patient app.

[0114] Subsection 336B4 contains a "Contents learned and practiced most recently in the app" column. For example, if the current step in the treatment program is "Step 1," the content being learned is extracted from the patient app and output. Also, for example, if the current step in the treatment program is "Step 2" or "Step 3," the behavioral goals that have been confirmed to be practiced among the behaviors set through the patient app are output. The output of subsection 336B4 is also an example of information regarding goals and goal achievement status.

[0115] Subsection 336B5 contains an "App Progress" column. In the case of Figure 16, the current step in the treatment program and the actions for which the goal has been achieved are displayed. In Figure 16, achieved items are represented by solid lines, and unachieved items are displayed in grayed-out form. Therefore, in the case of subsection 336B5 in Figure 16, it can be seen that "Step 1" has been achieved. Furthermore, it can be seen that of the six actions managed in "Step 2," "reducing salt intake" has been achieved, but the remaining five actions have not been achieved.

[0116] The output of sub-section 336B5 is generated from the patient data, such as the current step of the treatment program 230C3 (see FIG. 5) and the treatment program performance history 230C4 (see FIG. 5). The six actions managed in "Step 2" are examples of management items. The progress of each management item can be checked by checking subsection 336B5. In other words, the output of subsection 336B5 can be used to help understand the status of efforts to improve the disease. The output of subsection 336B5 is also an example of information about goals and the status of goal achievement.

[0117] Subsection 336B6 displays statistical information about the usage status of the patient app and the patient's behavior. In the case of Fig. 16, subsection 336B6 includes "Number of days of application," "App usage rate," "Number of blood pressure measurements," and "Number of days for reflection entries." However, the content shown in Fig. 16 is just an example, and various information that can be generated from the patient app data 230C (see Fig. 5) can be displayed. The output of subsection 336B6 is an example of information regarding goals and goal achievement.

[0118] Section 336C is titled "2. Goal to be achieved." In the case of FIG. 16, section 336C contains the items written in the "Goal to be achieved" column 334G (see FIG. 14). In the case of FIG. 16, section 336C outputs "Improve lifestyle habits using the patient app." The goal output in section 336C differs depending on whether the patient is currently at "Step 2" or "Step 3" of the treatment program. In the case of "Step 2," the behavioral goal being practiced, for example, through the patient app, is output. In the case of "Step 3," the blood pressure reduction goal set, for example, through the patient app, is output. The goal output in section 336C may be a quantitative goal or a qualitative goal. The target output in section 336C is an example of information about a target.

[0119] Section 336D is titled "3. Behavioral Goal." In the case of FIG. 16, section 336D contains the items written in the "Behavioral Goal" field 334H (see FIG. 15). In the case of FIG. 16, section 336D outputs "Set in patient app." The goals output in section 336D are behavioral goals set through the patient app, regardless of whether the patient's current step is "Step 2" or "Step 3" of the treatment program.

[0120] The goal displayed in section 336D is an example of information related to a goal. An action goal currently being implemented or set is displayed in section 336D. For example, an action goal related to an action that is grayed out in subsection 336B5 is displayed. Note that not all grayed-out behaviors are set as behavioral goals. Therefore, in the case of "Step 2" of the treatment program, only the behavioral goals that the patient has set as behavioral goals among the grayed-out behaviors in sub-section 336B5 are selectively output to section 336D. In the case of "Step 3" of the treatment program, the behavioral goals set by the patient are output to section 336D.

[0121] Section 336E contains the items written in the "Areas of focus and instruction items" column 334I (see Figure 15). In the case of Figure 16, for "diet" it says "Implement weight loss behavioral goals using the patient app." For "exercise" it says "Implement exercise behavioral goals using the patient app." For "tobacco" it says "Methods for quitting smoking, etc." For "other" it says "Measurements at home (blood pressure, weight, salt content)." The items written in "other" are output as they are written by the doctor or other doctor. Guidance information according to the progress of each behavior, which is a management item of the treatment program, may be generated by AI (=Artificial Intelligence) and output to block 336E. For the AI ​​here, for example, AI that has been trained by machine learning is used, with the practice status for each behavioral goal as input and guidance information as output.

[0122] In section 336F, the items entered in the "Comments" column 334J (see FIG. 15) and the items entered in the "Doctor's Name" column 334K (see FIG. 15) are arranged. In section 336G, the following text is printed: "We confirm that the patient has received an explanation of the contents of the treatment plan and fully understands it," followed by a section for the patient's signature.

[0123] Fig. 17 is a diagram for explaining another output example of the treatment plan 336. In Fig. 17, parts corresponding to those in Fig. 16 are assigned the same reference numerals. The difference between the treatment plan 336 shown in FIG. 17 and the treatment plan 336 shown in FIG. 16 is the output contents of subsection 336B4 and the output contents of subsection 336B5. In the case of Figure 17, subsection 336B4 contains a "Most frequently achieved behavioral goals in the app" column. In the case of Figure 17, subsection 336B4 outputs the behavioral goals that are ranked highest in terms of the number of times they have been achieved among the behavioral goals practiced in "Step 2" of the treatment program. Furthermore, in the case of Figure 17, the number of times each behavioral goal has been achieved is also displayed.

[0124] In the output format shown in Figure 17, it is possible to specifically confirm whether the behavioral goal has been achieved and the number of times it has been achieved. Note that the behavioral goal in Figure 17 is a specific behavioral goal such as "don't drink the soup in udon or ramen." In other words, sub-behavioral goals and the number of times they have been achieved are output. However, the behavioral goal displayed in subsection 336B4 may be in units of granularity defined in subsection 336B5, such as "reduce salt intake," "reduce weight," etc. In this case, the number of achievements may display the total number of achievements of the sub-behavioral goals belonging to "reduce salt intake."

[0125] In addition, the sub-section 336B4 may output the behavioral goals currently being practiced that are set through the patient app. In this output example, information on the behavior currently being practiced can be shared between the doctor and the patient. In addition, a summary of the description of the reflections recorded through the patient app may be output to subsection 336B4. For example, the reflections are a record of daily activities. However, since the reflections are recorded daily, it is difficult to display all of the written content in subsection 336B4.

[0126] Therefore, for example, the generation AI can be instructed to input the reflections recorded within a specified period (for example, the period from the previous output of the treatment plan to the current one) and output a summary of them. The summary will include the action goals that were successfully implemented. However, if the reflections include a description of actions that could not be implemented, the action goals that could not be implemented may also be included in the summary. In this output example, the action goals that were successfully implemented and the action goals that could not be implemented can be shared between the doctor and the patient.

[0127] The subsection 336B4 may also output the results of an evaluation of the progress of the behavioral goal based on predetermined criteria. The evaluation may be, for example, whether the achievement rate calculated from the patient data exceeds a reference value (e.g., 80%). The evaluation result may also be, for example, that the progress of the behavioral goal is "on track" or "requires improvement." The evaluation result may also be advice based on the progress. The evaluation of the progress of the behavioral goal may use AI that has learned the relationship between patient data as input and evaluation as output through machine learning.

[0128] Subsection 336B5 shown in Figure 17 is output for a patient currently practicing "Step 3" of the treatment program. Therefore, all actions in "Step 2" are displayed as having been achieved. Since the goal of "Step 3" is to make effective behavior a habit, the number of times the patient has achieved the behavioral goal set by the patient is displayed. In the case of Figure 17, the number of times achieved is 12.

[0129] <Summary> In this embodiment, a doctor or the like can open a reception screen 330 (see FIG. 13) for information to be entered into a medical treatment plan from a patient data viewing screen 310 (see FIG. 11). Furthermore, the contents to be entered in the treatment plan can be set by operating check boxes and radio buttons on the reception screen 330. This reduces the effort required for doctors and others to create a treatment plan.

[0130] Furthermore, in the case of this embodiment, a doctor or the like can generate a rich treatment plan 336 (see FIGS. 16 and 17) that utilizes patient data recorded through the patient app. In addition, in this embodiment, a treatment plan 336 can be generated that makes it easy to visually grasp behavioral goals and the progress of goal achievement, using measurements, reflections, and other information recorded by the patient through the patient app. Furthermore, the achievement goals and behavioral goals of the treatment plan 336 can be written according to the steps in the learning program of the user who uses the patient app and the behavioral goals set by the patient. This makes it less likely that discrepancies will occur between the treatment plan 336 and the goals managed by the patient app. As a result, seamless collaboration between the treatment plan and the patient app can be achieved.

[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 operations of the processors are performed is not limited to the above-described order, and may be changed individually.

[0133] (3) In the above-described embodiment, a patient app is given as an example of an application program executed on a patient terminal, but the app here may include a patient app whose validity period has expired. For example, it may be a patient app designated as a target of elective medical treatment. For prescribed medical treatment that references patient data entered through a patient app designated as a target of selected medical treatment, medical fees are permitted under the medical insurance system. Therefore, the description of the above-mentioned embodiment can also be applied to medical treatment that references patient data entered through a patient app designated as a target of selected medical treatment.

[0134] (4) In the above-described embodiment, the requirements for calculating medical fees under the public medical insurance system are assumed, but information regarding whether or not medical fees under the private medical insurance system can be calculated may also be displayed on the work screen of the doctor terminal 30. 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.

[0135] (5) In the above-described embodiment, the case where the reception screen 330 (see Figures 14 and 15) for information to be entered into the treatment plan is opened from the patient data viewing screen 310 (see Figure 11) was described. However, the reception screen 330 may also be opened from the patient app usage status management screen 300 (see Figure 10). Fig. 18 is a diagram illustrating another example of the management screen 300 for the usage status of patient apps, which is displayed on the output device 37 (see Fig. 6) of the doctor terminal 30 (see Fig. 6). In Fig. 18, parts corresponding to those in Fig. 10 are assigned the same reference numerals.

[0136] In the management screen 300 shown in FIG. 18, a "treatment plan" button 306 is arranged for each row corresponding to a patient. The doctor terminal 30 may provide the prescription code of the patient for which a treatment plan is to be generated to the PDT server 20 (see Figure 1) of the corresponding patient app, for example, via the PDT platform 10 (see Figure 1), and open the reception screen 330 for the patient linked to the prescription code.

[0137] The doctor terminal 30 may request the PDT platform 10 to issue a one-time token required to access the PDT server 20 corresponding to the prescription code of the patient for whom the medical treatment plan is to be generated. In this case, the doctor terminal 30 accesses the PDT server 20 using the one-time token received from the PDT platform 10.

[0138] (6) In the above-described embodiment, the generation of the treatment plan is performed on the condition that the items to be included in the treatment plan are set on the reception screen 330 (see Figures 14 and 15). However, the treatment plan may be generated automatically when the "treatment plan" button 317 (see Figure 11) is operated. In this case, editing of the contents of the created treatment plan may be accepted on the confirmation screen. For example, it may be possible to edit the achievement goals and behavioral goals set based on the information recorded through the patient app. Of course, it may also be possible to edit other items. This function can reduce the burden on doctors and others in creating treatment plans.

[0139] (7) In the above-described embodiment, it is assumed that the patient app usage status management screen 300 (see FIG. 10), the patient data viewing screen 310 (see FIG. 11), and the patient data viewing screen 310 are each displayed in a window format, but they may also be displayed in a browser tab format. Fig. 19 is a diagram illustrating an example of a browser screen displayed on the output device 37 of the doctor terminal 30. In the case of Fig. 19, three tabs are displayed on the browser screen.

[0140] One of the tabs corresponds to a patient application usage status management screen 300. In Fig. 19, the corresponding tab is denoted by the number "300." One of the other tabs corresponds to the View Patient Data screen 310. In Figure 19, the corresponding tab is labeled "310." In Figure 19, the page of the View Patient Data screen 310 is open. The last tab corresponds to the reception screen 330 for information to be entered in the treatment plan. In Fig. 19, the corresponding tab is labeled "330."

[0141] In the case of Figure 19, when the "330" tab is selected while the patient data viewing screen 310 is open, the prescription code of the patient data displayed on the patient data viewing screen 310 is carried over to the page that provides the treatment plan reception screen 330. As a result, the PDT server 20 generates a reception screen 330 for the treatment plan based on the patient data corresponding to the prescription code and updates the display content of the tab "330." The displayed reception screen 330 and the like are the same as those in the above-mentioned embodiment. When the user clicks the "Treatment Plan" button 317 (see FIG. 11) or the like, a tab screen dedicated to the corresponding patient may be opened. In this case, the prescription code of the corresponding patient is notified to the PDT server 20, and the generated treatment plan is displayed on the newly opened tab screen.

[0142] (8) In the above-described embodiment, the generation of a treatment plan for hypertension was described. However, treatment plans for dyslipidemia and diabetes can also be generated using a similar method. While the current medical fee system requires the attachment of a treatment plan only for hypertension, dyslipidemia, and diabetes, the above-described technology can be applied to all diseases for which a treatment plan is required. For example, it can also be applied to nicotine addiction, insomnia, NASH, kidney disease, alcoholism, cancer, chronic heart failure, attention deficit hyperactivity disorder, depression, tinnitus, delayed grief disorder, opioid-induced constipation, post-mastectomy pain syndrome, bronchial asthma, obesity, and nephrotic syndrome.

[0143] (9) In the above embodiment, the generation of a medical treatment plan was described, but the above technology can be applied to the generation of documents that support a user's medical treatment plan. For example, although not essential in relation to medical fees, it can also be applied to documents generated for the purpose of improving the effectiveness of treatment.

[0144] (10) In the above-described embodiment, the PDT server 20 generates a treatment plan and presents it to the doctor terminal 30. However, an app that generates a treatment plan may be executed on another server independent of the PDT server 20 (for example, the PDT platform 10 or a dedicated server not shown), or on the doctor terminal 30.

[0145] (11) In the above-described embodiment, the patient app is assumed to be a program located in a medical device, but it may also be a program located in a non-medical device. In that case, the above-described technology is used to generate documents that support treatment plans.

[0146] <Summary> The disclosed examples described in the above-mentioned embodiments are shown below. (((1))) An information processing device having one or more processors, which accepts the output of a document that supports a medical treatment plan, generates goals and information regarding the status of goal achievement from data recorded through a terminal operated by a user receiving medical treatment, and generates the document including the generated goals and information regarding the status of goal achievement. This information processing device can provide a mechanism for generating a document that supports a medical treatment plan using data recorded via a terminal operated by a user who changes his or her behavior.

[0147] (((2))) The information processing device according to ((1)), wherein the one or more processors output a graph of measurement values ​​extracted from the data as information relating to the progress of the goal. This information processing device can assist in understanding changes in daily measurement values.

[0148] (((3))) The information processing device described in (((1))), wherein one or more processors extract records of measurement values ​​from the data and generate information indicating changes in the measurement values ​​over a predetermined period as information regarding the progress of the goal. This information processing device can assist in understanding the progress of a task.

[0149] (((4))) The information processing device according to (((1))), wherein the one or more processors extract, from the data, actions that result in the achievement of the goal, and output the extracted actions as information relating to the achievement status of the goal. This information processing device can assist in understanding the actions that have been achieved.

[0150] (((5))) The information processing device according to (((1))), wherein the one or more processors extract a behavior currently being performed by the user from the data, and output the extracted behavior as information regarding a progress status of the goal. This information processing device can assist in understanding the behavior that is currently being practiced.

[0151] (((6))) The information processing device according to (((5))), wherein the one or more processors generate a summary of the user's behavior included in the data, and output the generated summary as the behavior being performed. This information processing device can efficiently assist in understanding the behavior that is currently being performed.

[0152] (((7))) The information processing device according to (((1))), wherein the one or more processors evaluate actions related to the goal of the data based on predetermined criteria, and output the results of the evaluation as information regarding the achievement status of the goal. This information processing device can provide information that supports the user's medical treatment.

[0153] (((8))) The information processing device described in (((1)))), wherein one or more processors extract the progress status for each management item of an application program executed on a terminal from the data, and output the extracted progress status for each management item as information regarding the achievement status of a goal. This information processing device can assist in understanding the status of efforts to improve a disease.

[0154] (((9))) The information processing device described in (((1))), wherein the one or more processors extract behavioral goals that have been set by the user or that the user is currently practicing from the data, and output the extracted behavioral goals to a behavioral goal column of the document. According to this information processing device, it is possible to effectively utilize the record of the behavioral goals set by the user who changes his / her behavior through the application.

[0155] (((10))) The information processing device according to (((9))), wherein the one or more processors accept an editing operation on the content output in the action goal field of the document. According to this information processing device, the content of the behavioral goal set by the user who changes his / her behavior can be changed after the fact.

[0156] (((11))) The information processing device according to (((1))), wherein the one or more processors extract quantitatively specified goals from the data and output the extracted goals to a column for goals to be achieved in the document. According to this information processing device, it is possible to effectively utilize the records of quantitatively specified goals managed by the application.

[0157] (((12))) The information processing device according to (((11))), wherein the one or more processors accept an editing operation for the content output in the goal column of the document. According to this information processing device, the content of the goal set by the user who is changing his / her behavior can be changed after the fact.

[0158] (((13))) The information processing device described in (((1)))) in which one or more processors extract the progress status for each management item of the application program executed on the terminal from the data, generate guidance information according to the progress status for each management item, and output the generated guidance information to the area of ​​focus and guidance item column of the document. According to this information processing device, information on management items that a user who is changing his / her behavior is currently practicing can be effectively utilized.

[0159] (((14))) The information processing device according to (((1))), wherein the one or more processors accept document output through an operation on a viewing screen for data input via a terminal operated by a user. According to this information processing device, it is possible to accept the output of a document that supports a medical treatment plan from a viewing screen for data recorded by a user who is changing his or her behavior.

[0160] (((15))) The information processing device according to (((1))), wherein the one or more processors accept document output through an operation on a management screen that displays a list of usage statuses of application programs prescribed to a user. According to this information processing device, it is possible to receive output of a document that supports a treatment plan from a management screen that displays a list of usage statuses of apps prescribed for a user who is changing their behavior.

[0161] (((16))) The information processing device according to (((1))), wherein the one or more processors accept document output through an operation of opening a browser tab. According to this information processing device, it is possible to receive output of a document that supports a medical treatment plan by opening a browser tab.

[0162] (((17))) An information provision method in which a computer performs the following processes: accepting the output of a document that supports a medical treatment plan; generating information about goals and the status of goal achievement from data recorded through a terminal operated by a user who is changing their behavior; and outputting a document containing the generated information about goals and the status of goal achievement. This information provision method can provide a mechanism for generating a document that supports a medical treatment plan using data recorded via a terminal operated by a user who changes his or her behavior.

[0163] (((18))) A program for enabling a computer to perform the following functions: accept output of documents that support treatment plans; generate information regarding goals and the status of goal achievement from data recorded through a terminal operated by a user who is changing their behavior; and output the document containing the generated information regarding goals and the status of goal achievement. This program can provide a mechanism for generating documents that support treatment plans using data recorded through a terminal operated by a user who is changing their behavior. [Explanation of symbols]

[0164] 10...PDT platform, 20, 20A, 20B, 20C, 20D, 20E, 20F...PDT server, 30...doctor's terminal, 40...patient terminal

Claims

1. having one or more processors; the one or more processors: Accepts output of documents that support treatment plans, generating a goal and information regarding the achievement of the goal from data recorded through a terminal operated by the user undergoing medical examination; outputting the document including the generated goal and information regarding the achievement status of the goal; Information processing device.

2. the one or more processors: generating a graph of measurements extracted from the data as information regarding progress toward the goal; The information processing device according to claim 1 .

3. the one or more processors: extracting a record of measurements from said data; generating information indicating a change in the measurement value over a predetermined period as information regarding the achievement status of the goal; The information processing device according to claim 1 .

4. the one or more processors: extracting from the data actions that have achieved the goal; outputting the extracted behavior as information regarding the achievement status of the goal; The information processing device according to claim 1 .

5. the one or more processors: extracting from the data the behavior currently being practiced by the user; outputting the extracted behavior as information regarding the achievement status of the goal; The information processing device according to claim 1 .

6. the one or more processors: generating a summary of the user's actions contained in the data; outputting the generated summary as the action being performed; The information processing device according to claim 5 .

7. the one or more processors: Evaluating the data's goal-related actions based on predetermined criteria; outputting the results of the evaluation as information regarding the achievement status of the goal; The information processing device according to claim 1 .

8. the one or more processors: extracting progress status for each management item of the application program executed on the terminal from the data; outputting the extracted progress status for each management item as information regarding the achievement status of the goal; The information processing device according to claim 1 .

9. the one or more processors: extracting a behavioral goal set by the user or being practiced by the user from the data; The extracted behavioral goal is output to the behavioral goal column of the document. The information processing device according to claim 1 .

10. the one or more processors: Accepting an editing operation for the content output in the action goal field of the document; The information processing device according to claim 9 .

11. the one or more processors: extracting quantitatively specified targets from the data; The extracted goals are output to the goal column of the document. The information processing device according to claim 1 .

12. the one or more processors: Accepting an editing operation for the content output in the achievement goal column of the document; The information processing device according to claim 11.

13. the one or more processors: extracting progress status for each management item of the application program executed on the terminal from the data; generating guidance information according to the progress status for each management item; The generated instruction information is output to an item column related to the instruction in the document. The information processing device according to claim 1 .

14. the one or more processors: receiving an output of the document through an operation on a viewing screen of the data input through the terminal operated by the user; The information processing device according to claim 1 .

15. the one or more processors: receiving an output of the document through an operation on a management screen that displays a list of usage statuses of application programs prescribed to the user; The information processing device according to claim 1 .

16. the one or more processors: Accepting output of the document through the opening of a browser tab; The information processing device according to claim 1 .

17. The computer A process for receiving output of documents supporting the treatment plan; A process of generating information about a goal and a progress of the goal from data recorded through a terminal operated by a user who changes his / her behavior; outputting the document including the generated goal and information regarding the achievement status of the goal; Information provision method to carry out.

18. On the computer, A function to accept output of documents that support the treatment plan; A function of generating information about a goal and the progress of the goal from data recorded through a terminal operated by a user who changes his / her behavior; a function of obtaining the document containing the generated goals and information regarding the achievement of the goals; A program to achieve this.

Images