Information processing device, information provision method, and program

Abstract

We provide a system to support the provision of medical services tailored to specific diseases. [Solution] An information processing device having a processor, the processor reads multiple screens prepared according to the flow of examination according to the disease, and outputs the screen corresponding to the operation input from among the multiple screens according to the progress of the examination.

Description

Technical Field

[0004] ,

[0006] , , , , , ,

[0005] , , , , ,

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

Background Art

[0002] Today, in addition to medical records and test results, examinations may be performed using health-related data recorded by the patients themselves.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Clinicians are required to be involved in the diagnosis of various diseases. For this reason, clinicians are required to provide appropriate medical services to patients with diseases other than their own specialties. <000,027> The present disclosure provides a mechanism for assisting in the provision of medical services according to diseases.

Means for Solving the Problems

[0006] The invention according to claim 1 is an information processing apparatus having a processor, the processor reads out a plurality of screens prepared along the flow of diagnosis according to a disease, and outputs a screen corresponding to an operation input among the plurality of screens according to the progress of the diagnosis. The invention described in claim 2 is the information processing device described in claim 1, wherein the disease is a lifestyle-related disease. The invention described in claim 3 is the information processing device according to claim 1, wherein at least one of the plurality of screens is a screen that explains the flow of a medical examination. The invention described in claim 4 is the information processing apparatus according to claim 1, wherein at least one of the plurality of screens is a screen that explains the effects brought about by the improvement of the disease. The invention described in claim 5 is the information processing device according to claim 1, wherein at least one of the plurality of screens is a screen that describes the current condition of a patient receiving medical treatment. The invention described in claim 6 is the information processing apparatus according to claim 1, wherein at least one of the plurality of screens is a screen that supports the goals that the patient undergoing medical examination is working towards. The invention described in claim 7 is the information processing device according to claim 1, wherein at least one of the plurality of screens is a screen that explains tasks that the patient should work on before the next consultation. The invention described in claim 8 is the information processing device according to claim 1, wherein at least one of the plurality of screens is a screen for confirming changes in the patient's state of mind from the previous consultation to the current consultation. The invention described in claim 9 is the information processing device according to claim 1, wherein at least one of the plurality of screens is a screen for confirming the patient's behavior between the previous consultation and the current consultation. The invention described in claim 10 is an information processing device according to claim 9, wherein the screen for confirming the patient's behavior is generated based on health data, including data recorded through a user terminal. The invention described in claim 11 is an information processing device according to claim 1, wherein the processor receives a disease to be used for medical examination through an operation on a screen for selecting a disease. The invention described in claim 12 is an information provision method in which a computer performs the following processes: reading a plurality of screens prepared in accordance with the flow of examination according to a disease; and outputting a screen from the plurality of screens that corresponds to an operation input according to the progress of the examination. The invention described in claim 13 is a program for realizing a function that causes a computer to read out a plurality of screens prepared in accordance with the flow of examination according to a disease, and a function that causes the computer to output a screen corresponding to an operation input from among the plurality of screens according to the progress of the examination. [Effects of the Invention]

[0007] According to one form of this disclosure, a mechanism can be provided to support the provision of medical services tailored to specific diseases. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram illustrates an example of the overall configuration of an information processing system according to an embodiment. [Figure 2] This diagram illustrates an example hardware configuration for a PDT platform. [Figure 3] This diagram illustrates an example of status management data stored in the auxiliary storage device of the PDT platform. [Figure 4] This diagram illustrates an example hardware configuration for a PDT server. [Figure 5] This diagram illustrates an example of patient data stored in the auxiliary storage device of a PDT server. [Figure 6] This diagram illustrates an example of the hardware configuration for a physician's terminal and a patient's terminal. [Figure 7] This figure illustrates an example of a processing sequence in the embodiment. [Figure 8] This diagram illustrates an example of a management screen for managing the usage status of patient applications, which is displayed on the output device of a physician's terminal. [Figure 9] This is a diagram illustrating an example of a medical consultation support screen. [Figure 10] This is a diagram illustrating an example of a slide used in the "Consultation Flow" section of the consultation process. [Figure 11] This diagram illustrates an example of a slide used in the "Understanding the Current Situation" step of the medical examination process. [Figure 12]This is a diagram for explaining an example of a slide used in "grasping the current situation" in the examination process. [Figure 13] This is a diagram for explaining an example of a slide used in "goal setting" in the examination process. [Figure 14] This is a diagram for explaining an example of a proposal screen and a cooperation screen for a reduced alcohol plan. [Figure 15] It represents a slide when the "want to quit drinking" button is selected as the set goal. [Figure 16] This is a diagram for explaining an example of a slide used in "towards the next examination" in the examination process. [Figure 17] This is a diagram for explaining an example of a slide used in "examination process" and a slide used in "review" in the examination process. [Figure 18] This is a diagram for explaining an example of a slide used in "review" and a slide used in "goal setting" in the examination process. [Figure 19] This is a diagram for explaining an example of a slide used in "towards the next examination" in the examination process. [Figure 20] This is a diagram for explaining an example of a slide used in "towards the next examination" in the examination process. [Figure 21] This is a diagram for explaining an example of a selection screen for a plurality of examination support screens. [Figure 22] This is a diagram for explaining an example of a processing operation when the doctor terminal displays the examination support screen alone.

Embodiments for Carrying Out the Invention

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

[0010] This type of program includes programs classified as medical devices and programs classified as non-medical devices. Programs classified as medical devices are examples of programs that require a prescription, while programs classified as non-medical devices are examples of programs that do not require a prescription. Furthermore, programs classified as non-medical devices are not limited to programs that encourage behavioral change; they may also include programs that have a function to record health-related data. Programs that encourage behavioral change or have a function to record health data include programs that can be downloaded from app stores. These types of programs may also be used by private companies, public organizations, etc., for the health management of their employees. Some programs classified as non-medical devices are used in medical institutions.

[0011] The "purpose of the app" refers to the effect that should be achieved by using a program that promotes behavioral change. The purpose of the app varies depending on the disease to which the program that promotes behavioral change corresponds. For example, the purpose of the app may include improving lifestyle habits, maintaining improved lifestyle habits, and maintaining improved numerical values.

[0012] "App goals" refer to the objectives that are aimed for by using a program that encourages behavioral change. Goals are defined from the perspective of achieving the objective. Goals are classified into qualitative and quantitative indicators. Furthermore, goals are classified into indicators defined by measurements or other numerical values ​​and indicators defined by the content of actions. For example, goals include improving or maintaining habits, behaviors, and numerical values. App goals can also be defined by one or more sub-goals. Sub-goals are smaller-grained goals set to achieve the corresponding goal.

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

[0014] A "user" refers to a person who uses a program that has the function of recording health-related data. A person who changes their behavior through the aforementioned behavioral change-promoting program is an example of a user. Users include both users before visiting a medical institution and users who have visited a medical institution. Users who have visited a medical institution include both users who are eligible for medical fee calculation and users who are not eligible for medical fee calculation. "Patient" refers to a user who is receiving treatment at a medical institution. In other words, a patient is a user who has started or is currently receiving treatment at a medical institution.

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

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

[0017] A "doctor app" refers to a program that can be used through a terminal operated by a doctor or other healthcare professional (hereinafter also referred to as a "doctor terminal"). In the embodiment described later, the doctor app runs on a cloud server that can be operated from the doctor terminal. The doctor app is used to view patient data (including patient app data). Healthcare professionals are also referred to as medical personnel.

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

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

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

[0021] "Medical history" includes, for example, the date treatment began, the date of the consultation, the content of the treatment, and advice given. Medical history is just one example of information related to a medical consultation. "Patient app operation history" refers to, for example, the history of operations related to launching the patient app, inputting measurement values ​​and reflections, etc. "Biological characteristics" include, for example, the presence or absence of other diseases, injuries currently being treated, the presence or absence of knee or foot pain, experience with disease treatment, and the number of years since the disease was diagnosed.

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

[0023] "Habits" include, for example, exercise habits, weight measurement habits, habits of checking calorie information on food labels, habits of choosing low-fat foods, habits of not consuming caffeine after 4 PM, eating habits after 10 PM, skipping breakfast habits, snacking habits, bathing habits one hour before bedtime, habits of stretching or massaging before bedtime, habits of getting more than 6 hours of sleep, wake-up and bedtime, the intensity of seasoning at home, and the amount of food consumed. "Goal achievement status" refers to information showing the progress toward goals set by a doctor for each patient, for example. "Goal achievement status" may also refer to information showing the progress toward goals set by the patient themselves, for example. "Goal achievement status" may also refer to information showing the progress toward goals presented by a patient app for each patient, for example. Furthermore, the information mentioned above can be classified into subjective information and objective information.

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

[0025] The processed data includes, for example, processed data, data obtained through statistical processing, and summaries of patient data generated by artificial intelligence (AI). The processed data may also include, for example, the mean, the maximum and minimum values ​​within a given period, the data distribution for each given period, and the difference from the baseline. Health-related data may include data related to programs other than those that have the functionality to record health data or programs that encourage behavioral change. For example, it may include user accounts used to access various services and privacy-related information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0045] The processor 11 is a device that realizes various functions through the execution of a program. The processor 11 may be composed of multiple CPU (=Central Processing Unit) cores. In that case, the processor 11 executes the program through the cooperation of the multiple CPU cores. The semiconductor memory 12 stores information such as UEFI (Unified Extensible Firmware Interface). 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.

[0046] 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, a program for listing 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.

[0047] <PDT Platform Management Data> [[ID=URL:8]]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 / consultation 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.

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

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

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

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

[0052] The processor 21 is a device that realizes various functions through the execution of a program. The processor 21 may be composed of multiple CPU cores. In that case, the processor 11 executes the program through the cooperation of the multiple CPU cores. 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.

[0053] 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. Other programs include, for example, a doctor app. The doctor app is a program that generates a browsing screen for patient data corresponding to patients examined by doctors and the like.

[0054] In addition, the auxiliary storage device 23 also records 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 supports communication standards such as Ethernet (registered trademark), Wi-Fi (registered trademark), and mobile communication systems.

[0055] <Management data of the PDT server> FIG. 5 is a diagram for explaining an example of patient data 230 stored in the auxiliary storage device 23 (see FIG. 4) of the PDT server 20. The patient data 230 shown in FIG. 5 stores measured values and other information recorded through the patient app. The content of the information recorded as the patient data 230 also varies depending on the disease corresponding to the patient app. 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.

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

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

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

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

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

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

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

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

[0064] The processors 31 / 41 are devices that perform various functions through program execution. The processors 31 / 41 may consist of multiple CPU cores. In that case, the processor 11 executes the program through the cooperation of the multiple CPU cores. The semiconductor memory 32 / 42 stores UEFI and other information. The semiconductor memory 32 / 42 is also used as an execution area for programs. The processor 31 / 41 and the semiconductor memory 32 / 42 function as a computer. The auxiliary storage devices 33 / 43 consist of, for example, hard disk drives or semiconductor storage devices. The operating system and other programs are stored in the auxiliary storage devices 33 / 43.

[0065] In the case of the physician terminal 30, the auxiliary storage device 33 stores a client certificate for accessing the PDT platform 10 (see Figure 1) and a client certificate for accessing the PDT server 20 (see Figure 1). In the case of the patient terminal 40, the auxiliary storage device 43 stores a client certificate for accessing the PDT server 20 (see Figure 1). The auxiliary storage device 43 also stores the patient application and the patient application data 230C (see Figure 5) recorded through the program.

[0066] Input interfaces 34 / 44 can use, for example, USB (Universal Serial Bus) or Bluetooth (registered trademark) to connect to input devices 35 / 45. Input devices 35 / 45 can include, for example, keyboards, mice, or touch panels.

[0067] Output interfaces 36 / 46 can be connected to output devices 37 / 47, for example, using HDMI (High-Definition Multimedia Interface) (registered trademark) or a LAN interface. Output devices 37 / 47 can be, for example, monitors or printers. Communication interfaces 38 / 48 are interfaces for communicating with external terminals over a network. Communication interfaces 38 / 48 are compatible with Ethernet®, Wi-Fi®, mobile communication systems, and other communication standards.

[0068] <Processing Sequence> Figure 7 illustrates an example of a processing sequence in an embodiment. The processing sequence shown in Figure 7 corresponds to the period between one medical examination and the next. In Figure 7, the symbol S stands for step. The processing sequence shown in Figure 7 assumes a case where a patient with alcohol dependence is being examined. Therefore, the examination support screen described later is also customized for the examination of a patient with alcohol dependence.

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

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

[0071] <Step 103> The PDT server 20 stores the uploaded patient application data. This patient application data constitutes a part of the patient data 230 (see Figure 5). Steps 101 to 103, shown in Figure 7, are executed as a result of the patient's input operations into the patient application. On the other hand, steps 104 to 110 shown in Figure 7 are performed as a result of the patient visiting a medical institution.

[0072] <Step 104> When a doctor or other medical professional logs into the PDT platform 10 via the doctor's terminal 30, the PDT platform 10 displays a screen on the doctor's terminal 30 showing the status of the patient's application usage. Figure 8 illustrates an example of a patient application usage status management screen 300 displayed on the output device 37 (see Figure 6) of the physician terminal 30 (see Figure 1).

[0073] The management screen 300 shown in Figure 8 is an example of a management screen that displays a list of usage statuses of patient applications prescribed to patients by a physician or other person operating the physician terminal 30. Furthermore, the management screen 300 may display only the usage status of patient apps prescribed by the physician operating the physician terminal 30, or it may display the usage status of patient apps prescribed by the medical institution to which the physician operating the physician terminal 30 belongs. In other words, the management screen 300 may also include the usage status of patient apps prescribed by other physicians belonging to the same medical institution.

[0074] In addition, the management screen 300 may also 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 implemented, for example, by a doctor operating the doctor terminal 30 providing the PDT platform 10 with information that identifies the patient being treated (e.g., medical record number or patient name). Furthermore, technically, it is possible to include all patient information managed by the PDT platform 10 in the management screen 300. However, in that case, it is desirable to enable filtering and sorting of patients displayed on the management screen based on the ID of the physician operating the physician terminal 30.

[0075] The management screen 300 shown in Figure 8 consists of an information field 301, the current date and time 302, a "Details" button 303, a "New Prescription" button 304, and a "Close" button 305. Information field 301 displays management information for the patient app prescribed to each patient. In Figure 8, information field 301 is displayed in a table format. Specifically, the rows display information for each patient, and the columns display management items for the patient app. Figure 8 shows examples of management items, including medical record number / patient name 301A, application name 301B, usage status 301C, prescription date 301D, and prescription code expiration date 301E.

[0076] The field "Medical Record Number / Patient Name 301A" displays the medical record number and patient name, which are examples of information used to identify a patient prescribed by the patient app. Note that the patient identification information may also include user ID, address, etc. The app name 301B displays the name of the patient app prescribed to the patient. In this embodiment, four apps are displayed: patient app A, patient app B, patient app C, and patient app D. The app name 301B may also include version information.

[0077] If multiple patient apps are approved for the same patient, the information will be displayed on different rows. In addition to the app name 301B, or separately, the name of the disease targeted by the patient app may be displayed. Usage status 301C is used to display the usage status of the patient's application. In Figure 10, usage status 301C displays three options: "Before use," "In use," and "Finished." However, as mentioned above, usage status 301C can also display "Start deadline expired," "Scheduled end," "Period expired," etc.

[0078] The prescription date 301D displays the date the patient app was prescribed by a doctor or other healthcare professional. The prescription code expiration date 301E displays the last day the prescription code is valid. In this embodiment, the prescription code expiration date 301E displays a date three days after the prescription date 301D. The current date and time 302 is the date and time when the patient app usage status management screen 300 was viewed.

[0079] The "Details" button 303 is used to view patient data. A "Details" button 303 is placed for each row corresponding to a patient. When the "Details" button 303 is pressed, 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 pressed, a screen appears for entering the app name, patient name, gender, date of birth, etc. The name of the prescribing physician is also registered at the same time. The "Close" button 305 is used to close the administration screen 300 shown in Figure 10.

[0080] <Step 105> Let's return to the explanation of Figure 7. The physician terminal 30 accepts patient selection on the aforementioned management screen 300 (see Figure 8). Specifically, the physician terminal 30 accepts operation of the "Details" button 303 (see Figure 8). Upon receiving the operation of the "Details" button 303, the physician terminal 30 accesses the PDT server 20 of the patient app prescribed to the patient corresponding to the operated "Details" button 303.

[0081] Furthermore, the physician or other medical professional is assumed to be logged in to the PDT server 20 via the physician's terminal 30. During this access, the prescription code of the patient app prescribed to the patient corresponding to the operated "Details" button 303 is notified. Incidentally, the physician terminal 30 may request the PDT platform 10 to issue a one-time token necessary to access the corresponding PDT server 20. In this case, the physician terminal 30 uses the one-time token received in return from the PDT platform 10 to access the PDT server 20. When this method is adopted, physicians and others can access patient application data on the PDT server 20 even if they are not logged in.

[0082] <Step 106> Upon receiving access from the physician's terminal 30, the PDT server 20 outputs a consultation support screen corresponding to the consultation session. In other words, the PDT server 20 displays a consultation support screen on the physician's terminal 30. The medical examination support screen in this embodiment consists of multiple slides with content that follows the flow of the medical examination. In this embodiment, the medical consultation support screen is intended to be viewed by both doctors and patients. Therefore, the amount of information on each slide is kept to a minimum, prioritizing ease of information transmission. For example, the slides use bullet points, illustrations, graphs, etc.

[0083] Of course, how medical institutions and doctors use the consultation support screen is entirely up to them. However, by allowing doctors and other medical professionals to view the consultation support screen together with the patient, patients can receive explanations from the doctor or other medical professional while anticipating the flow of the consultation. As a result, patients are more likely to concentrate on the doctor's or other medical professional's explanation compared to when they are unaware of the flow of the consultation. Furthermore, by viewing the consultation support screen together with the patient, doctors and other medical professionals can more easily explain the patient's symptoms and the necessary treatment measures. As a result, doctors and other medical professionals can provide appropriate medical services according to the disease, regardless of their own specialization.

[0084] In step 106, the PDT server 20 identifies the number of consultations based on the records of consultation dates (including prescription dates) associated with the patient. In this embodiment, the prescription date in the patient app is set as the 0th consultation. This is because, in this embodiment, patient data recorded through the patient app between the prescription date and the next consultation is used to customize the content of the slides displayed on the consultation support screen. If the prescription date in the patient app is considered the 0th consultation, then, for example, a consultation four weeks after the prescription date will be the 1st consultation, and a consultation four weeks after that will be the 2nd consultation.

[0085] Figure 9 illustrates an example of a medical consultation support screen. In this embodiment, a consultation support screen corresponding to the first consultation and a consultation support screen corresponding to the second and subsequent consultations are provided. Both the consultation support screen for the first consultation and the consultation support screen for subsequent consultations consist of multiple slides (i.e., screens) prepared in accordance with the flow of the consultation. In this embodiment, the content of the multiple slides is divided into four sections: "Consultation Flow," "Review," "Goal Setting," and "Looking Ahead to the Next Consultation."

[0086] The consultation support screens for each consultation session appear in the following order: "Consultation Flow," "Review," "Goal Setting," and "Preparing for the Next Consultation." The number of slides that make up each section is arbitrary. Therefore, one section may consist of one slide, while another may consist of multiple slides. In the case of Figure 9, each section consists of multiple slides.

[0087] Figure 9 shows the process progressing in the order of "Consultation Flow," "Review," "Goal Setting," and "Preparing for the Next Consultation," but it is also possible to go back in time depending on the input of the doctor or other staff member. In other words, doctors and other medical professionals can freely display slides that reflect the progress of the examination. In Figure 9, there are two selectable goals in the "Goal Setting" section. Therefore, Figure 9 represents the existence of the two scenarios in two separate rows, one above the other.

[0088] Needless to say, if it's possible to set more than three goals, then more than three scenarios will be available. The "Consultation Flow" section explains the treatment system using the patient app and the flow of each consultation session. The "Consultation Flow" is used for sharing information about treatment and the consultation process between the doctor and the patient. Reviewing the consultation flow in advance helps prepare for a smooth consultation.

[0089] In the "reflection," for example, the effects of disease improvement, the impact of the disease (reasons why treatment is necessary), and the patient's current condition (including symptoms) are explained, and changes in the patient's feelings from the previous consultation to the current consultation and the patient's behavior during that period are confirmed. In this embodiment, the explanation of the effects of disease improvement and the impact of the disease (reasons why treatment is necessary) is explained only at the first consultation, but it may be explained at every consultation. The "reflection" is used to support the patient's sustained motivation for treatment and to improve their motivation for treatment by helping them understand their disease and their own condition. Furthermore, some of the slides used in the "review" session will be generated based on patient app data.

[0090] The "Goal Setting" section assists patients in setting goals they will work towards during their consultation. Goal setting varies depending on the disease. If the patient app allows patients to set their own goals, "Goal Confirmation" may be provided instead of "Goal Setting." If "Goal Confirmation" is provided, doctors and other medical professionals can confirm the goals set by the patient. Patients can also have their goals confirmed by doctors and other medical professionals and receive advice. "Goal Setting" is used to support the maintenance and improvement of patients' motivation for treatment by sharing goals between doctors and patients. Furthermore, setting goals according to the slides can support doctors and other medical professionals in setting goals.

[0091] The "Preparing for Your Next Appointment" section explains the tasks the patient should address before their next appointment. These tasks are specific actions to achieve their goals. In other words, the tasks the patient should address are the agreement between the doctor and the patient regarding the next appointment. The "Preparing for Your Next Appointment" section is used to support the patient's motivation for treatment by confirming the tasks between the doctor and the patient and, if necessary, making a commitment to implement those tasks. Furthermore, explaining the tasks the patient should address using slides can support the explanation of these tasks to the patient.

[0092] <Step 107> Let's return to the explanation of Figure 7. The physician terminal 30 accepts slide advance or slide rewind operations on the examination support screen. The entity performing these operations is the physician or other medical professional. These advance or rewind operations are performed, for example, by using the forward button, the reverse button, or the scroll bar slider. <Step 108> Upon receiving an operation from the physician's terminal 30, the PDT server 20 outputs the corresponding slide to the physician's terminal 30. As a result, the display on the physician's terminal 30 changes to reflect the slide that was operated on. Steps 107 and 108 are repeated.

[0093] <Step 109> The physician's terminal 30 accepts the operation to end the consultation. This operation is performed, for example, by pressing the "End" button or "Consultation Complete" button located on the final slide of the consultation support screen. <Step 110> Upon receiving notification from the physician's terminal 30 that the consultation has ended, the PDT server 20 closes the patient consultation support screen. In this embodiment, the screen on the physician's terminal 30 returns to the management screen 300 (see Figure 8).

[0094] <Specific examples of consultation support screens> Let me explain a specific example of the consultation support screen mentioned earlier. As previously stated, the consultation support screen consists of "Consultation Flow," "Review," "Goal Setting," and "Preparing for the Next Consultation." The following describes the consultation support screen used in the examination of a patient diagnosed with alcohol dependence. Alcohol dependence is an example of a lifestyle-related disease. As explained using Figure 9, the consultation support screen in this embodiment consists of a consultation support screen corresponding to the first consultation and consultation support screens corresponding to the second and subsequent consultations. Therefore, the consultation support screens will be described separately for each consultation.

[0095] <Consultation support screen for the first consultation> <Consultation Procedure> Figure 10 illustrates an example of slides 400 and 410 used in the "Consultation Flow" section of the consultation flow. Slide 400 is page 1, and slide 410 is page 2. Slide 400 includes a patient information section 401, a consultation session section 402, a main information section 403, and a "Next" button 404. The patient information section 401 displays information about the patient being examined.

[0096] The consultation number column 402 displays the consultation number for the current consultation. On slide 400, the section labeled "1st consultation" is highlighted. Note that on slide 400, "2nd consultation" is displayed normally, but "3rd consultation" through "7th consultation" are grayed out. The main information section, page 403, displays the title "We support your efforts to reduce / quit drinking with the help of an app and your doctor," along with an illustration explaining the relationship between the patient (you), the doctor, and the app. Here, "app" refers to a "patient app."

[0097] The arrow from the patient to the doctor is labeled "Consultation." Here, "Consultation" refers to a consultation during the medical examination. The arrows from doctor to patient are labeled "Suggestions and Support During Consultation." This indicates that doctors and other medical professionals support patients as advisors. The arrow from the patient to the app is labeled "Record Learning." Here, "Record Learning" refers to the recording of the patient's daily activities and learning about alcohol dependence through the patient app.

[0098] The arrow from the app to the patient is labeled "Daily Support." This label indicates that the patient can receive various forms of support by using the patient app daily. It also shows that the app acts as the patient's personal trainer. A two-way arrow is drawn between the doctor and the app. This arrow is labeled "Information Sharing." This label indicates that doctors and other healthcare professionals will share the health data (i.e., patient app data) that patients record through their patient app.

[0099] The "Next" button 404 is a forward button used to switch the screen display to the next slide 410. Since slide 400 is the first page, the backward button is not displayed. By using slide 400, doctors and other medical professionals can more easily explain to patients the details of the examination or treatment they are about to begin. Furthermore, patients can more easily grasp the overall picture of their treatment or examination using the patient app compared to receiving explanations verbally.

[0100] Slide 410 includes a patient information section 401, a consultation session section 402, a main information section 411, a "next" button 404, and a "back" button 405. In the main information section 411, under the title "Today's Consultation," the comments "I'm happy to be able to join you in this wonderful challenge" and "Let's work together to achieve our goals" are displayed.

[0101] Furthermore, the main information section 411 indicates that this consultation will proceed in the following order: "1. Understanding the current situation," "2. Setting goals," and "3. Preparing for the next consultation." This display is an example of the "consultation flow." By reviewing the "Today's Consultation" section and numbered illustrations at the top of the slide, doctors and patients can easily share information about the upcoming consultation process.

[0102] The main information section 411 shown in Figure 10 also indicates that the medical questionnaire has been completed. The "Back" button 405 is a reverse button used to switch to the previous page, slide 400. Since slide 410 is the second page, both the "Forward" button 404 and the "Back" button 405 are provided. Because the "Back" button 405 is available, doctors and other medical professionals can switch the display to slide 400 as needed.

[0103] <Reflection> Figure 11 illustrates an example of slides 420 and 430 used in the "Assessing the Current Situation" step of the examination process. Figure 11 is labeled with corresponding symbols for parts that correspond to those in Figure 10. Slide 420 is the page following slide 410 (see Figure 10), and slide 430 is the page following slide 420. In the case of slides 420 and 430 shown in Figure 11, a table of contents section 406, which represents the flow of the examination, is displayed in the lower left part of the slide.

[0104] Slides 420 and 430 have the following headings in the table of contents section 406: "1. Review," "2. Goal Setting," and "3. Towards the Next Appointment." In slides 420 and 430, a marker is displayed next to "1. Review" to allow you to check the current step. Slide 420's main information section 421 displays the title, "What are the benefits of reducing alcohol consumption?" This slide 420 is used to explain the effects of improving a disease. Below the title, there are three sections: "What can you expect?", "Who will be happy?", and "What kind of reward would you like to give yourself?".

[0105] The section "What can be expected?" already displays the benefits that can be gained if alcohol dependence improves. The question "Who will be happy?" records responses from patients, for example. In Figure 11, it shows "Colleagues." Other responses to "Who will be happy?" include "Family," "Wife," "Children," "Parents," etc., depending on the patient's circumstances. For example, the patient's response to the question, "What reward would you like to give yourself?" is recorded. In Figure 11, this field is left blank.

[0106] Slide 430's main information section 431 is titled "Your Information Regarding Alcohol Consumption." This slide 430 is used to explain the effects of the disease (why treatment is necessary). Below the title, there are two sections: "Pre-existing medical conditions whose risk increases with alcohol consumption" and "Difficulties in current daily life." Under "Pre-existing conditions whose risk is increased by drinking," the pre-existing conditions of patients affected by alcohol dependence are displayed. This display may be entered by a doctor or other professional, or it may be implemented as a function of the PDT server 20. Under "What difficulties are you currently facing in your life?", for example, responses from patients are recorded.

[0107] Figure 12 illustrates an example of slide 440 used in the "Understanding the Current Situation" step of the examination process. Figure 12 is labeled with corresponding symbols to those in Figure 11. Slide 440 is the page following slide 430 (see Figure 11). Slide 440's main information section 441 is titled "Current Alcohol Consumption and Frequency." This slide 440 is used to describe the patient's current condition (including symptoms).

[0108] Slide 440's main information section 441 shows that the patient has one "alcohol-free day" per week, consumes one large bottle of beer per week, one medium bottle of beer per week, and consumes one glass of wine per week. This information is displayed, for example, through the analysis of patient data. Alternatively, patients may be asked questions according to the information displayed on slide 440, and their responses may be entered. On the right side of slide 440, it is shown that the average daily alcohol intake is 56.8g, and the average daily alcohol intake over a week is 48.7g.

[0109] Additionally, slide 440, shown in Figure 12, also contains buttons for "Data Comparison," "Changes in Disease Risk," and "Type of Disease." Operating each button will display the corresponding slide. In this embodiment, the explanation of the slide examples is omitted. By displaying the slide corresponding to each button, the patient can receive an explanation of their condition using graphs, illustrations, bullet points, etc. Understanding your current condition and sharing information with doctors and other healthcare professionals is beneficial for maintaining and improving the effectiveness of treatment.

[0110] <Goal Setting> Figure 13 illustrates an example of slides 450 and 460 used in the "goal setting" section of the consultation flow. Figure 13 is denoted with corresponding symbols for parts that correspond to those in Figure 11. Slide 450 is the page following slide 440 (see Figure 12). Slide 450's main information section, 451, is titled "How to Approach Alcohol in the Future." This slide 450 is used to explain how patients undergoing treatment can set goals.

[0111] In the main information section 451 shown in Figure 13, two buttons are displayed as setting goals: "I want to reduce my alcohol intake" and "I want to abstain from alcohol." In the main information section 451, the "I want to reduce my alcohol consumption" button is selected. The goal is set through consultation between the patient and, for example, a doctor. Below the goal selection button, comments corresponding to the selected goal are displayed. In Figure 13, three comments are displayed: "1. Set an achievable goal for reducing alcohol consumption," "2. Goals can be changed along the way," and "3. Don't blame yourself for not being able to do something, praise yourself for what you can do." The comments are in bullet points, making them easy for patients to understand. Furthermore, doctors and other medical professionals can reduce the chances of missing important information by simply reading the slides aloud.

[0112] Slide 460's main information section, 461, is titled "Setting Goals." On this slide, you can set specific goals corresponding to the set objective (in this case, "reducing alcohol consumption"). Incidentally, the screen layout of the main information section 461 is similar to that of slide 440 in the "Review" section (see Figure 12). In Figure 13, the value on slide 440 is displayed as the value before the change. Based on this value, fields for setting target values ​​such as "Alcohol-free days ( / week)" are provided. The initial value is the value on slide 440. In Figure 13, the value can be increased or decreased using the "plus" and "minus" buttons.

[0113] Additionally, a button labeled "Add Drink" is provided to allow users to add alcoholic beverages not displayed on the screen. For example, users can add "Shochu," "Whiskey / Brandy," "Sake," and "Highball." In addition, slide 460's main information section 461 includes an area with the subtitle "Suggestion for a reduced alcohol consumption plan." Figure 13 shows buttons for "Reduce heavy drinking to 40g or less" and "Reduce to the recommended standard of 20g or less."

[0114] Figure 14 illustrates an example of the alcohol reduction plan proposal screen 470 and the linking screen 480. The upper part of Figure 14 shows an example of the display of the alcohol reduction plan suggestion screen 470. In this example, the alcohol reduction plan suggestion screen 470 is displayed as a pop-up in front of the grayed-out slide 460. The suggested alcohol reduction plan screen 470 shown in Figure 14 displays suggestions for achieving the goal of "reducing heavy drinking to 40g or less."

[0115] One suggestion is to "increase the number of alcohol-free days." Studies have shown that increasing alcohol-free days from one to three per week reduces the average weekly alcohol intake from 48.7g to 32.5g. Another suggestion is to "reduce the number of bottles or glasses consumed." Studies have shown that changing the consumption of large bottles of beer from one glass to zero can reduce the average weekly alcohol intake from 48.7g to 27.0g. In addition, Figure 14 shows a portion of the third proposal.

[0116] A "Submit" button is provided for each suggestion. When the "Apply" button is pressed, or when the goal setting is accepted on slide 460 (see the lower part of Figure 13), the display switches to the linkage screen 480. The linking screen 480 is displayed in the lower section of Figure 14. The collaboration screen 480 shown in Figure 14 is displayed as a pop-up in front of the grayed-out slide 460. In Figure 14, the linking screen 480 displays the message: "The following goal settings will be linked to the application the patient is using. Is this OK?"

[0117] On the linked screen 480, it is displayed that the goal to be set is "reduced alcohol consumption," the daily alcohol intake is 56.8g, the number of alcohol-free days per week is 1, the average alcohol intake per week is 48.7g per day, and there is an "Apply" button to reflect these settings in the patient app. The above shows the slide transitions after the "I want to reduce my alcohol consumption" button is pressed on slide 450 (see Figure 13).

[0118] Figure 15 shows slide 450 when the "I want to quit drinking" button is selected as the target. Figure 15 is labeled with corresponding symbols for parts that correspond to Figure 13. In Figure 15, the comments displayed below the goal selection button include three options: "1. Don't be too fixated on abstaining from alcohol," "2. It's okay to drink today, you can try harder tomorrow," and "3. Don't push yourself too hard if it's having too much of an impact on your body or mind." The content displayed in this main information section 451 changes depending on the selected objective.

[0119] <Regarding the next appointment> Figure 16 illustrates an example of slides 490 and 500 used in the "Preparing for the next consultation" section of the consultation flow. Figure 16 is indicated with corresponding reference numerals for parts that correspond to those in Figure 13. Slide 490 is, for example, the page following slide 460 (see the lower part of Figure 14), and slide 500 is the page following slide 490.

[0120] The main information section 491 is titled "Preparing for your next appointment." This section is used to explain the tasks the patient should complete before their next appointment. As shown in Figure 16, the left side of slide 490 displays the target column 407, which indicates the set goal. In Figure 16, the target column 407 displays "abstinence from alcohol."

[0121] The main information section (491) displays, "Please record your drinking in the app every day!" In other words, recording your drinking using the patient app is a task required of the patient. Furthermore, the app explains that "the support you receive will change based on your daily records" and "we will discuss your next appointment based on your records," along with an illustration illustrating the recorded data. Sharing the contents of slide 490 between doctors and patients makes it easier to share the tasks that patients need to address before their next appointment. When the "Next" button 404 is pressed on slide 490, slide 500 is displayed.

[0122] The main information section 501 displays the title, "Let's get started today." It also displays questions such as, "Do you have any questions about today's consultation?" and "Please feel free to discuss any future concerns or anxieties you may have." This display helps doctors and other medical professionals remember to speak to patients. It also makes it easier for patients to ask questions of doctors and other medical professionals. In other words, opportunities for communication between doctors and other medical professionals and patients are provided.

[0123] Furthermore, the main information section 501 includes an optional field for "Advice for the next visit." Although it's labeled as advice, its use is left to the discretion of the doctor or other healthcare professional. For example, considering that the information entered in the field is sent to the patient's app, it can be used to confirm tasks the patient needs to address or to record appointments. In slide 500, shown in Figure 16, a speech bubble featuring a personified character representing the patient app displays the message, "I'll support you until your next appointment." This comment in the speech bubble encourages patients to use the patient app.

[0124] When the "Consultation Complete" button is pressed, this consultation support screen will be closed. In this way, the end of the consultation support screen includes a slide to review the tasks the patient should address before the next consultation, which is expected to help maintain and improve the effectiveness of treatment. Next, we will explain an excerpt of the consultation support screen used in the second and subsequent consultation sessions.

[0125] <Consultation support screen for the second and subsequent consultations> <Opening screen and review> Figure 17 illustrates an example of slide 510 used in the "Consultation Flow" section and slide 520 used in the "Review" section of the consultation flow. Figure 17 is indicated with corresponding reference numerals for parts that correspond to Figures 10 and 11. Slide 510, shown in Figure 17, corresponds to the second consultation. Therefore, the title in the main information section 511 displays "This is the second consultation." If it were the third consultation, the title would display "This is the third consultation."

[0126] The main information section 511 also indicates that the process should proceed in the following order: "1. Understanding the current situation," "2. Setting goals," and "3. Preparing for the next consultation." This allows patients to review the flow of the current consultation and creates an environment where they can concentrate on the explanations from the doctor or other medical staff. When the "Next" button 404 is pressed, the display switches to slide 520. Slide 520 is a slide for "understanding the current situation." Since this is the second consultation, slides reviewing the current situation since the last consultation will be displayed instead of slides 420 (see Figure 11) and 430 (see Figure 11) mentioned earlier.

[0127] The main information field 521 displays the title "How have things been since your last consultation?". This main information field 521 displays information recorded by the patient through the patient app since the last consultation. The displayed content is generated by the PDT server 20 (see Figure 1) and customized for the patient's consultation support screen. In the case of Figure 17, the study period is 12 weeks (i.e., 84 days).

[0128] In addition, the main information section 521 shows that the "drinking record" is for 42 days, that 2 out of 5 "homework" items have been completed, that there are 36 records of "practice," that there are 10 records of "self-care," that there are 20 days' worth of "check-in" records, and that there are 7 days' worth of "check-out" records. By reviewing this information, doctors and patients can confirm the patient's drinking habits over the past 12 weeks. Furthermore, slide 520 displays information for each item using icons, making it easy to review the content of each item.

[0129] <Continuing the review and resetting goals> Figure 18 illustrates an example of slides 530, used for the "review" section of the consultation flow, and slide 540, used for the "goal setting" section. Accordingly, the table of contents section 406 displayed in the lower left of slides 530 and 540 has markers indicating the "review" and "goal reset" sections. Figure 18 also includes corresponding symbols for sections in Figures 11 and 13.

[0130] Slide 530 is the page following slide 520 (see the lower part of Figure 17), and slide 540 is the page following slide 530. Slides 520 and 530 are used in subsequent consultations. Therefore, the section corresponding to "2. Goal Setting" in the table of contents (section 406) has been changed to "2. Goal Reset." This is because the goal has already been set during the first consultation.

[0131] The main information section 531 displays the title, "Have there been any changes in your life or state of mind?". The main information section 531 also has a section for "Thoughts on the current situation," where comments from the patient, entered through the patient app, are displayed. However, in the case of Figure 18, the "Thoughts on the current situation" section displays "Not filled in". The main information section 531 also displays "Benefits of reducing alcohol consumption" and "Information about drinking." The content of this section basically corresponds to slide 420 (see upper section of Figure 11) and slide 430 (see lower section of Figure 11). In this way, each consultation provides an opportunity to repeatedly confirm the patient's current condition.

[0132] The main information section 541 displays the title "Confirmation and Suggestions for Practice." Here, "practice" refers to actions taken to achieve the goal (in this case, reducing alcohol consumption). In addition, the main information section 541 displays "Practices in Progress," such as "Recording alcohol consumption using an app each time you order a refill," "Drinking alcohol and soft drinks alternately," "Drinking low-alcohol beverages," and "Not drinking for more than two hours a day." Note that these are just examples. Furthermore, each practice is displayed with information on whether it was effective and the number of times it was recorded. After confirmation using slide 540, slides 450 (see upper section of Figure 13, or see Figure 15) and 460 (see lower section of Figure 13), which were displayed during the first consultation, will be shown.

[0133] <Regarding the next appointment> Figure 19 illustrates an example of slides 550 and 560 used in the "Preparing for the next consultation" section of the consultation flow. Figure 19 is indicated with corresponding reference numerals for parts that correspond to Figure 16. Slide 550 is used, for example, in the second and third consultations, and slide 560 is used, for example, in the fourth consultation. Slide 550 or slide 560 may also be used in the fifth through seventh consultations.

[0134] Slides 550 and 560 are both used to explain the tasks the patient should work on before their next appointment. Slides 550 and 560 are, for example, the pages following slide 540 (see the lower part of Figure 18).

[0135] The main information section 551 displays the title "Preparing for your next appointment." It also displays "Continue to record your daily activities in the app!" The explanation includes, "Maintaining the habit of accurate record-keeping will lead to more reliable reduction or abstinence from alcohol," and "Continue completing the app's homework to deepen your understanding of alcohol." This display content may be one of the template sentences prepared for each consultation session, or it may be content generated or selected for each patient based on the patient data recording status.

[0136] The tasks displayed on slide 550, which serve as a consultation support screen, can be independent of the homework managed by the patient app. However, this does not eliminate the overlap between the tasks displayed on slide 550 and the homework managed by the patient app. In addition, item 551 in the main information section displays "Things you are currently struggling with in your life." The explanation for this includes "Each small step you take will surely lead to results" and "Even if you fail, it is important to keep going."

[0137] This display contains additional information compared to slide 490 (see upper section of Figure 16) from the first consultation. Slide 550 is displayed in subsequent consultations, meaning the patient has already started treatment using the patient app. Therefore, slide 550 explains the importance of continuing treatment as one of the tasks until the next consultation.

[0138] The main information section 561 is titled "Regarding Future Treatment." Unlike slide 550 mentioned earlier, this main information section 561 focuses on confirming the future treatment plan. The main information section 561 displays several confirmation items. Figure 19 shows four examples of confirmation items: "Your feelings about reducing or abstaining from alcohol," "Your thoughts on drug therapy," "Types of medications you are interested in," and "Your thoughts on specialized treatment."

[0139] By facilitating two-way communication with patients according to the presented items, a shared understanding of treatment plans will be achieved between doctors and patients. In the case of Figure 19, it was confirmed that patients perceived themselves as being able to "barely reduce" their alcohol consumption, regarding their "perceived progress in reducing or abstaining from alcohol." Furthermore, regarding their "views on drug therapy," the patient responded that they "would definitely like to try it." Regarding "types of medication they are interested in," the patient indicated interest in "nalmefene," a drug that works in the brain to help reduce alcohol consumption. Finally, regarding their "views on specialized treatment," the patient indicated that they "are not considering it at the moment."

[0140] This information is crucial for considering treatment tailored to each individual patient. Furthermore, treating alcohol dependence, a lifestyle-related disease, requires a long-term approach. Therefore, the content of the slides is changed according to the patient's consultation sessions. Consequently, even doctors who do not specialize in alcohol dependence can provide medical services tailored to the patient's treatment stage.

[0141] Figure 20 illustrates an example of slide 570 used in the "Preparing for the next consultation" section of the consultation flow. Figure 20 is indicated with corresponding symbols for parts that correspond to Figure 16. Slide 570 is the page following slide 560 or 560 (see Figure 19). Slide 570, shown in Figure 20, is the final page of the consultation support screen.

[0142] Since this is the second or subsequent consultation, the title displayed in the main information section 571 is "A new four-week period begins." The title of the main information section 501 corresponding to slide 500 (see the lower part of Figure 16) for the first consultation was "Let's get started today." In this way, the wording of the title is prepared according to the consultation session. The rest of the information displayed on slide 570 is the same as on slide 500.

[0143] <Summary> In this embodiment, the physician's terminal 30 (see Figure 1) displays a consultation support screen prepared according to the flow of an alcohol dependence consultation. This consultation support screen consists of multiple slides that follow the flow of the consultation. Specifically, it consists of "Consultation Flow," "Review," "Goal Setting," and "Towards the Next Consultation." The content and layout of these slides are designed with efficiency and therapeutic effectiveness in mind. Therefore, physicians and other medical professionals can provide high-quality medical services by following the consultation support screen.

[0144] Specifically, it will become easier to share information with patients regarding the treatment mechanism and the flow of examinations. Furthermore, by sharing with the patient their current condition and their progress in daily life, including homework assignments, at the beginning of the consultation, it becomes possible to set goals that are appropriate to the patient's condition. Furthermore, by confirming actions to be taken before the next consultation at the end of the examination, it becomes possible to maintain or improve the patient's motivation for treatment. Thus, the PDT server 20 in this embodiment (see Figure 1) can support the provision of medical services by doctors and other medical professionals through a medical consultation support screen.

[0145] Furthermore, in this embodiment, by linking with the patient app, information recorded through the patient app is reflected in each slide. This increases objectivity compared to gathering information about the patient's current condition and daily activities through conversation during the examination. As a result, doctors' judgments become more accurate, and it becomes possible to provide treatment content and advice that is more appropriate for the patient. Furthermore, since the switching of slides on the consultation support screen is done by the doctor or other medical staff, flexible consultations become possible.

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

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

[0148] (3) In the embodiment described above, multiple scenarios were prepared only for "goal setting" (see Figure 9). However, multiple scenarios may be prepared for one or more (including all) of the following: "procedure of the examination," "reflection," and "preparation for the next examination."

[0149] (4) In the above-described embodiment, the scenario is switched according to the target selection operation by a doctor or the like. However, scenario switching may be performed in response to other operations by a doctor or other personnel. For example, scenario switching may be performed by operating a specific key assigned to scenario switching. For example, scenario switching may be performed by selecting a tab. For example, scenario switching may be performed depending on the presence or absence of checked items or the combination of checked items.

[0150] Furthermore, scenario switching may be performed based on the content of comments entered by doctors or other personnel. For example, if a comment entered by a doctor or other user contains a specific word, the corresponding scenario may be displayed. Alternatively, the comments entered by the doctor or other user may be fed to a pre-trained model that has been trained using machine learning to analyze the relationship between the content of the comments and the scenarios, and the scenario corresponding to the output of the trained model may be displayed. In other words, the comments from the doctor or other user may be analyzed by AI, and the displayed scenario may be switched accordingly.

[0151] (5) In the above-described embodiment, the scenario is switched according to the goal selection operation by the doctor or other person. However, the PDT server 20 may also perform the scenario switching according to the content of the patient app data recorded from the previous consultation to the current consultation. For example, the scenario presented may be changed depending on whether the patient's usage rate of the patient app from the previous consultation to the current consultation is below a threshold or above a threshold.

[0152] In addition, the PDT server 20 may switch scenarios based on the content of patient app data recorded up to the current consultation (including records prior to the prescription date if available). For example, the scenario presented may be different for patients whose patient app usage rate from the prescription date to the current consultation date is below a threshold compared to patients whose patient app usage rate from the prescription date to the current consultation date is above a threshold. Alternatively, the patient's app data may be provided to a trained model, which has been trained using machine learning or similar methods to determine the relationship between the content of the patient's app data and the corresponding scenario, and the scenario corresponding to the output of the trained model may be displayed. In other words, the content of the patient's app data may be analyzed by AI, and the displayed scenario may be switched accordingly.

[0153] (6) In the embodiment described above, the consultation support screen consists of four steps: "Consultation Flow," "Review," "Goal Setting," and "Towards the Next Consultation." However, other screen configurations for consultation support screens may be presented. For example, screens for reviewing past consultation results, past and recent test results, treatment effectiveness, and past treatment plans may be included. On the other hand, a screen configuration that does not include one or more of the four screens described in the embodiment may be adopted. For example, a screen configuration that does not include the "consultation flow" in the consultation support screen may be adopted.

[0154] (7) In the embodiment described above, the same consultation support screen is displayed regardless of the consultation session. That is, it consists of four steps: "Consultation Flow," "Review," "Goal Setting," and "Towards the Next Consultation." However, the number of steps in the consultation support screen may be changed depending on the consultation session. For example, the first consultation session may have a 4-step structure, while subsequent consultation sessions may have a 2-step, 3-step, or even 5-step structure.

[0155] (8) In the above-described embodiment, the titles and layouts of some slides related to the consultation support screen presented in the second and subsequent consultation sessions are different. However, while maintaining the four-step structure, the content of the consultation support screen may differ for each consultation.

[0156] (9) The PDT server 20 in the above-described embodiment (see Figure 1) is intended for the examination of patients with alcohol dependence. However, when examining patients with other diseases, a consultation support screen for those diseases will be displayed. These other diseases can be lifestyle-related diseases or non-lifestyle-related diseases. Lifestyle-related diseases include, for example, hypertension, dyslipidemia, chronic heart failure, hyperuricemia, diabetes, NASH, kidney disease, nicotine addiction, chronic bronchitis, cancer, periodontal disease, attention deficit hyperactivity disorder, depression, tinnitus, delayed grief disorder, opioid-induced constipation, post-mastectomy pain syndrome, nephrotic syndrome, and insomnia.

[0157] (10) In the above-described embodiment, the provision of a medical examination support screen service was described as a function of the PDT server 20 (see Figure 1). However, the provision of the medical consultation support screen may be provided as a service by a server other than the PDT server 20. For example, the medical consultation support screen may be provided as a service of the PDT platform 10 (see Figure 1), or it may be provided as a so-called cloud-based medical service.

[0158] (11) In the above embodiment, a PDT server 20 dedicated to a specific disease is assumed. Therefore, the physician terminal 30 (see Figure 1) displays a consultation support screen for alcohol dependence. However, if the PDT server 20 supports multiple diseases, a screen for selecting the examination support screen to display may be displayed on the physician's terminal 30. Figure 21 illustrates an example of a selection screen 600 for multiple consultation support screens.

[0159] The selection screen 600 shown in Figure 21 displays the title "Selection of Examination Support Screen." It also displays the explanatory text "Please select a disease." Furthermore, the selection screen 600 displays six selection buttons. In Figure 21, the selection buttons are labeled "Disease 1" through "Disease 6".

[0160] Incidentally, "Disease 1" to "Disease 6" are, for example, one of the following: alcohol dependence, hypertension, dyslipidemia, chronic heart failure, hyperuricemia, diabetes, NASH, kidney disease, nicotine dependence, chronic bronchitis, cancer, periodontal disease, attention deficit hyperactivity disorder, depression, tinnitus, delayed grief disorder, opioid-induced constipation, post-mastectomy pain syndrome, nephrotic syndrome, or insomnia. In Figure 21, there are six selection buttons, but there can be two to five. There can also be seven or more selection buttons.

[0161] (12) In the above-described embodiment, an information processing system 1 (see Figure 1) that prescribes a patient application was described. However, the output control of the medical examination support screen may be performed solely by the physician terminal 30 (see Figure 1). In other words, it may be implemented as a function of a program installed on the physician terminal 30 (including a server within the medical institution). Figure 22 illustrates an example of processing operation when the physician terminal 30 displays the examination support screen independently. Figure 22 is denoted with reference numerals corresponding to the parts that correspond to those in Figure 7.

[0162] As a prerequisite, the physician's terminal 30 has a program running that controls the output of, for example, a consultation support screen for alcohol dependence. First, the physician terminal 30 obtains information about the patient's number of consultations (step 111). For example, the physician terminal 30 obtains information about the number of consultations by accepting input or selection of the number of consultations by a physician or other medical professional. However, the physician terminal 30 may also obtain the number of consultations by linking with an electronic medical record system or other system within the medical institution.

[0163] Next, the physician's terminal 30 outputs a consultation support screen corresponding to the consultation session (step 106). Subsequently, the physician's terminal 30 accepts page forward / backward operations on the examination support screen (step 107) and outputs the corresponding slide (step 108). This processing operation is repeated until the examination is completed. Note that the physician's terminal 30 in Figure 22 is operating in standalone mode. Therefore, the consultation support screen assumed in Figure 22 does not include information about patient application data or its processing data recorded through the patient application.

[0164] Therefore, the examination support screen with the processing operation shown in Figure 22 can also be used for examinations of lifestyle-related diseases that do not involve prescriptions from the patient's app. However, if patient app data recorded via the patient app has been acquired from the PDT server 20 (see Figure 1) prior to the examination, it is possible to present an examination support screen that reflects the patient app data, similar to the embodiment described above. Subsequently, the physician's terminal 30 accepts the operation to end the consultation (step 109) and closes the patient's consultation support screen (step 110).

[0165] (13) In the above embodiment, it is assumed that all data reflected on the medical examination support screen is recorded through the patient application. However, all or part of the data reflected on the consultation support screen may be recorded through a program classified as a non-medical device. A program classified as a non-medical device is, like a patient app, a program used to record health-related data.

[0166] (14) In the above-described embodiment, the case where the direction of progress (direction of movement) is to the right was described for the examination support screen. That is, the case where the left side of the display screen is the beginning of the slide was described. However, the direction of progression (the direction of movement) of the examination support screen may be leftward. In other words, the right side of the display screen may be the beginning of the slide.

[0167] Furthermore, the direction of progression (the direction of movement) of the examination support screen may be downwards. In other words, the top of the display screen may be the beginning of the slide. Furthermore, the direction of progression (the direction of movement) of the examination support screen may be upward. In other words, the bottom of the display screen may be the beginning of the slide.

[0168] In the embodiment described above, the slides displayed on the screen are switched using the "forward" button 404 (see Figure 10) and the "back" button 405 (see Figure 10). However, the slides displayed on the screen may also be switched using the scrollbar slider, the mouse wheel, the side buttons of the mouse, etc.

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

[0170] (16) The consultation support screen described in the above embodiment is intended to be viewed by both the doctor and the patient during the consultation in the examination room. However, the above consultation support screen may also be shared between the doctor's terminal 30 (see Figure 1) and the patient's terminal 40 (see Figure 1) in online consultation. In this case, doctors and other medical professionals can conduct online consultations by sharing a consultation support screen with patients who are not in the examination room. Sharing the consultation support screen makes it easier to share information with patients even during online consultations.

[0171] <Summary> An example of the disclosure described in the above-mentioned embodiment is shown below. (((1))) An information processing device having a processor, the processor reads multiple screens prepared according to the flow of examination for each disease, and outputs the screen corresponding to the operation input from among the multiple screens according to the progress of the examination. This information processing device can provide a system that supports the provision of medical services tailored to specific diseases.

[0172] (((2))) The disease is a lifestyle-related disease, and the information processing device is as described in (((1))). This information processing device can support the provision of medical services tailored to lifestyle-related diseases.

[0173] (((3))) The information processing device described in (((1))) has at least one screen that explains the flow of the medical examination. This information processing device makes it easier to share information regarding the flow of medical examinations.

[0174] (((4))) The information processing device described in (((1))) has at least one of its multiple screens which is a screen that explains the effects of disease improvement. This information processing device can help maintain and improve patients' motivation for treatment.

[0175] (((5))) The information processing device described in (((1))) has at least one screen that describes the current condition of the patient being examined. This information processing device can help maintain and improve patients' motivation for treatment.

[0176] (((6))) The information processing device described in (((1))) has at least one of several screens that supports the goals that the patient undergoing treatment is working towards. This information processing device can help sustain and improve the effectiveness of treatment.

[0177] (((7))) The information processing device described in (((1))) has at least one screen that explains the tasks the patient should work on before the next appointment. This information processing device can help sustain and improve the effectiveness of treatment.

[0178] (((8))) The information processing device described in (((1))) has at least one screen that confirms changes in the patient's state of mind from the previous consultation to the current consultation. This information processing device can help sustain and improve the effectiveness of treatment.

[0179] (((9))) The information processing device described in (((1))) has at least one of its multiple screens that confirms the patient's behavior between the previous and current consultations. This information processing device can help sustain and improve the effectiveness of treatment.

[0180] (((10))) The screen for checking the patient's behavior is the information processing device described in (((9))), which is generated based on health-related data including the data recorded through the user terminal. According to this information processing device, it is possible to support the continuation and improvement of the treatment effect.

[0181] (((11))) The processor is the information processing device described in (((1))), which accepts operations on the disease selection screen for supporting diagnosis. According to this information processing device, it is possible to support the provision of medical services according to the disease.

[0182] (((12))) An information providing method in which a computer executes a process of reading a plurality of screens prepared along the flow of diagnosis according to the disease, and a process of outputting, according to the progress of diagnosis, a screen corresponding to an operation input among the plurality of screens. According to this information providing method, it is possible to provide a mechanism for supporting the provision of medical services according to the disease.

[0183] (((13))) A program for causing a computer to realize a function of reading a plurality of screens prepared along the flow of diagnosis according to the disease, and a function of outputting, according to the progress of diagnosis, a screen corresponding to an operation input among the plurality of screens. According to this program, it is possible to provide a mechanism for supporting the provision of medical services according to the disease.

Explanation of Signs

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

Claims

1. It has a processor, The aforementioned processor, The system reads multiple screens prepared according to the examination procedure for each disease, and outputs the screen corresponding to the user input from among these multiple screens according to the progress of the examination. Information processing device.

2. The aforementioned disease is a lifestyle-related disease. The information processing apparatus according to claim 1.

3. The information processing apparatus according to claim 1, wherein at least one of the plurality of screens is a screen that explains the flow of a medical examination.

4. The information processing apparatus according to claim 1, wherein at least one of the plurality of screens is a screen that explains the effects brought about by the improvement of the disease.

5. The information processing apparatus according to claim 1, wherein at least one of the plurality of screens is a screen that explains the current condition of a patient receiving medical treatment.

6. The information processing apparatus according to claim 1, wherein at least one of the plurality of screens is a screen that supports the goals that a patient undergoing medical examination is working towards.

7. The information processing apparatus according to claim 1, wherein at least one of the plurality of screens is a screen that explains the tasks the patient should work on before the next consultation.

8. The information processing apparatus according to claim 1, wherein at least one of the plurality of screens is a screen for confirming changes in the patient's state of mind from the previous consultation to the current consultation.

9. The information processing apparatus according to claim 1, wherein at least one of the plurality of screens is a screen for confirming the patient's actions between the previous consultation and the current consultation.

10. The information processing apparatus according to claim 9, wherein the screen for confirming the patient's behavior is generated based on health data, including data recorded through the user terminal.

11. The aforementioned processor, The system accepts patients through an operation on a screen to select diseases that support the examination. The information processing apparatus according to claim 1.

12. Computers The process involves reading multiple screens prepared according to the examination procedure for each disease, A process that outputs the screen corresponding to the operation input from among the multiple screens mentioned above, according to the progress of the examination, A method for providing information to carry out the task.

13. On the computer, A function that displays multiple screens prepared according to the flow of examination for each disease, A function to output the screen corresponding to the operation input from among the aforementioned multiple screens according to the progress of the examination, A program to achieve this.

Images