Treatment System

Abstract

To provide a treatment system capable of managing behavior of a patient in cooperation with a doctor and a pharmacist.SOLUTION: A treatment system used for treating a patient includes: a patient terminal of the patient; a doctor terminal used when a doctor issues a prescription of an application for managing behavioral information regarding behavior of the patient; a pharmacist terminal used when a pharmacist sets the application executed at the patient terminal based on the prescription; and a management server for receiving behavioral information periodically from the patient terminal to store the received behavioral information. The doctor terminal and the pharmacist terminal acquire the behavioral information stored in the management server.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a treatment system. [Background technology]

[0002] Regarding smoking cessation treatment for patients, a system in which a doctor performs smoking cessation treatment based on smoking information obtained from an application installed on the patient's smartphone is disclosed in Non-Patent Document 1. Regarding obesity treatment for patients, Patent Document 1 discloses a technology that allows obesity treatment to be performed over a long period of time using an electronic device carried by the patient. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2021-101367 A [Non-patent literature]

[0004] [Non-Patent Document 1] “Japan’s first doctor-prescribed smoking cessation treatment app”, [online], Internet, [searched July 22, 2021],<URL:https: / / kenko.sawai.co.jp / theme / 202012.html> Summary of the Invention [Problem to be solved by the invention]

[0005] When a doctor manages a patient's behavior and provides treatment, the doctor can provide the patient with an application that has the function of managing the patient's behavior to the patient's device (such as a smartphone). In this case, the application is provided to the patient's device based on the doctor's prescription, and the doctor can provide treatment based on information about the patient's behavior obtained from the application. However, if the doctor manages the patient's behavior alone, the doctor's burden becomes heavy.

[0006] Here, not only doctors but also pharmacists (including dietitians and medical professionals) can provide applications to patients' terminals based on prescriptions issued by doctors. For this reason, it is desirable for doctors and pharmacists to work together to manage patients' behavior. The technology disclosed in Patent Document 1 and Non-Patent Document 1 does not perform such work.

[0007] As one aspect, an object of the present disclosure is to provide a treatment system that enables doctors, pharmacists, and the like to cooperate with each other to manage the behavior of patients. [Means for solving the problem]

[0008] A treatment system according to one embodiment of the present invention is a treatment system used to treat a patient, and comprises a patient terminal for the patient, a doctor terminal used when a doctor issues a prescription for an application that manages behavioral information related to the patient's behavior, a pharmacist terminal used when a pharmacist sets up the application to be executed on the patient terminal based on the prescription, and a management server that periodically receives the behavioral information from the patient terminal and stores the received behavioral information, and the doctor terminal and the pharmacist terminal acquire the behavioral information stored in the management server. Effect of the Invention

[0009] It is possible to provide a treatment system that allows doctors, pharmacists, etc. to cooperate with each other to manage the behavior of patients. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 illustrates an example of a treatment system. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of a doctor terminal. [Diagram 3] FIG. 2 is a block diagram showing an example of the configuration of a pharmacist terminal. [Figure 4] FIG. 2 is a block diagram showing an example of the configuration of a patient terminal. [Diagram 5]FIG. 2 is a block diagram showing an example of a configuration of a management server. [Figure 6] FIG. 13 is a sequence diagram showing an example of a flow of prescription of an application to a patient terminal. [Figure 7] FIG. 13 illustrates an example of a barrier list and multiple challenge lists. [Figure 8] FIG. 13 is a diagram illustrating an example of a screen of an application executed on a patient terminal. [Figure 9] FIG. 13 is a diagram showing an example of a transition of a daily review screen. [Figure 10] 13 is a flowchart showing an example of the flow of a review process. [Figure 11] FIG. 11 is a diagram showing an example of a transition of a target step count determination screen. [Figure 12] FIG. 13 is a diagram showing an example of a transition of a challenge setting screen. [Figure 13] 13 is a flowchart showing an example of the flow of a challenge setting process. [Figure 14] A flowchart showing an example of the processing flow performed by a patient terminal during an online consultation. [Figure 15] FIG. 13 is a diagram showing an example of an online interview. [Figure 16] FIG. 13 is a diagram showing an example of a screen for additional functions. [Figure 17] 13 is a flowchart showing an example of a processing flow executed by a pharmacist terminal during an online consultation. [Figure 18] 13 is a flowchart showing an example of a flow of a process executed by a doctor terminal during a medical examination. [Figure 19] 13 is a flowchart illustrating an example of a process flow according to another embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Each embodiment will be described below. Each of the following embodiments can be modified as appropriate. The configuration of each embodiment can be replaced with a substantially similar configuration, a configuration that provides similar effects, or a configuration that can achieve similar purposes. Furthermore, the order of the processes in the flowcharts described in each embodiment can be changed as much as possible.

[0012] The present embodiment will be described below. In the following, a pharmacist or a registered dietitian belonging to an outpatient pharmacy (hereinafter, simply referred to as a pharmacy) will be described as providing patient self-management support and specific health guidance. However, medical professionals other than pharmacists can also be substituted. Also, a pharmacist who is qualified as a diabetes medical instructor can provide medical guidance and other support according to his / her qualification. FIG. 1 is a diagram showing an example of a treatment system 10. The treatment system 10 includes a doctor terminal 11, a pharmacist terminal 12, a patient terminal 13, a management server 14, a prescription issuing device 11A, and a pedometer 13A. Elements of the treatment system 10 in FIG. 1 other than the doctor terminal 11, the pharmacist terminal 12, the patient terminal 13, and the management server 14 may not be included in the treatment system 10.

[0013] The doctor terminal 11, the pharmacist terminal 12, the patient terminal 13, and the management server 14 are connected to each other via a network NW so that they can communicate with each other. The doctor terminal 11, the pharmacist terminal 12, the patient terminal 13, and the management server 14 may be connected to the same network NW, or some or all of them may be connected via a network separate from the network NW.

[0014] The doctor terminal 11 is a terminal operated by a doctor. The doctor terminal 11 has a function of receiving operations by the doctor and issuing a prescription when examining a patient. The doctor terminal 11 has a function of issuing an application for managing the patient's behavior as a prescription. Details of the application will be described later. The doctor terminal 11 also has a function of issuing a prescription for medicine to be prescribed to the patient.

[0015] The doctor terminal 11 is connected to the prescription issuing device 11A via a network within the hospital. The prescription issuing device 11A is, for example, a device installed at the accounting counter of the hospital. The prescription issuing device 11A receives prescription information related to a prescription issued by the doctor terminal 11 from the doctor terminal 11, and prints a paper prescription based on the prescription information. The printed prescription is handed over to the patient.

[0016] The prescription includes information for a pharmacist to configure the application. The prescription may also include information for a pharmacist to dispense the drug. The application prescription and the drug prescription may be printed as separate prescriptions that are associated with each other, or may be printed as a single prescription. The prescription may include only information for a pharmacist to configure the application.

[0017] Although an example will be described in which the information for the pharmacist to set up the application is written on a paper prescription, the information for the pharmacist to prescribe the application may be electronic data, as will be described later.

[0018] The pharmacist terminal 12 is a terminal operated by a pharmacist, a registered dietitian, or a medical professional. The pharmacist terminal 12 has a function of setting up an application based on information written on a prescription. A prescription issued at a hospital where the doctor terminal 11 is installed is obtained by a pharmacist. The pharmacist has the authority to set up an application based on a prescription within the pharmacy where the pharmacist terminal 12 is installed. Setting up an application based on a prescription is permitted only by a pharmacist, similar to dispensing medicine.

[0019] The patient terminal 13 is a terminal carried by the patient. In this embodiment, the patient terminal 13 is described as being a smartphone, but the patient terminal 13 may be another device. The pedometer 13A is a wearable device that is attached to the patient's body (such as the arm). The pedometer 13A and the patient terminal 13 have a function of performing short-range wireless communication. As a result, the patient terminal 13 obtains the number of steps counted by the pedometer 13A. The pedometer 13A is also referred to as an exercise therapy monitoring device that monitors the patient's exercise therapy, a wearable gait measuring device, or the like.

[0020] The management server 14 is a server that manages the entire treatment system 10. In this embodiment, the management server 14 holds information to be displayed on the screen of each of the doctor terminal 11, the pharmacist terminal 12, and the patient terminal 13. For example, the screen displayed on each terminal is a Web browser. Each terminal transmits a request to the management server 14 to obtain information to be displayed on the Web browser, obtains information to be displayed on the Web browser from the management server 14, and displays the obtained information on the Web browser.

[0021] 1 shows an example in which there is one doctor terminal 11, one pharmacist terminal 12, and one patient terminal 13, but there may be multiple of each terminal. There may also be multiple management servers 14. A hospital network to which one or more doctor terminals 11 belong and a pharmacy network to which one or more pharmacist terminals 12 belong may be connected to the network NW. This allows multiple hospitals and multiple pharmacies to participate in the treatment system 10.

[0022] In the following description, the ID identifying the prescribing doctor who prescribed the prescription is referred to as the prescribing doctor ID, the ID identifying the patient is referred to as the patient ID, and the ID identifying the pharmacy is referred to as the pharmacy ID. When multiple pharmacist terminals 12 are installed in one pharmacy, the same pharmacy ID is assigned to each pharmacist terminal 12. Also, different pharmacy IDs are assigned to pharmacist terminals 12 installed in different pharmacies.

[0023] 2 is a block diagram showing an example of the configuration of the doctor terminal 11. The doctor terminal 11 is, for example, a computer such as a personal computer. The doctor terminal 11 includes a doctor terminal control unit 21, a doctor terminal storage unit 22, a doctor terminal communication unit 23, a doctor terminal display unit 24, and a doctor terminal operation unit 25.

[0024] The doctor terminal control unit 21 controls the entire doctor terminal 11. The doctor terminal control unit 21 includes one or more processors, such as a CPU (Central Processing Unit). The processor executes a program stored in the doctor terminal storage unit 22, thereby realizing the control of the doctor terminal 11 in this embodiment.

[0025] The doctor terminal storage unit 22 is, for example, a memory or a hard disk drive. The doctor terminal storage unit 22 stores various information in addition to the above-mentioned programs. The doctor terminal communication unit 23 communicates with other terminals and servers via the network NW.

[0026] The doctor terminal display unit 24 is a display that displays various information. For example, the information displayed on the doctor terminal display unit 24 is information that the doctor refers to or views when examining a patient. The information includes information about the patient's behavior (behavior information).

[0027] The doctor terminal operation unit 25 is an operation unit using devices such as a mouse and a keyboard. The configuration of the doctor terminal 11 is not limited to the example of FIG. 2, and may include other configurations, or some configurations may be omitted.

[0028] 3 is a block diagram showing an example of the configuration of pharmacist terminal 12. Pharmacist terminal 12 is, for example, a computer such as a personal computer. Pharmacist terminal 12 includes a pharmacist terminal control unit 31, a pharmacist terminal storage unit 32, a pharmacist terminal communication unit 33, a pharmacist terminal display unit 34, a pharmacist terminal operation unit 35, and a reading device 36.

[0029] The pharmacist terminal control unit 31 performs overall control of the pharmacist terminal 12. The pharmacist terminal control unit 31 includes, for example, one or more processors such as a CPU. The processor executes a program stored in the pharmacist terminal storage unit 32, thereby realizing control of the pharmacist terminal 12 in this embodiment.

[0030] The pharmacist terminal storage unit 32 is, for example, a memory or a hard disk drive. The pharmacist terminal storage unit 32 stores various information in addition to the above-mentioned programs. The pharmacist terminal communication unit 33 communicates with other terminals and servers via the network NW.

[0031] The pharmacist terminal display unit 34 is a display that displays various information. For example, the information displayed on the pharmacist terminal display unit 34 includes information for setting an application on the patient terminal 13 based on a doctor's prescription. In addition, the pharmacist terminal display unit 34 displays a screen for an online consultation using an application executed on the patient terminal 13.

[0032] The online interview is a video call between a patient and a pharmacist regarding the patient's treatment. The online interview will be described as a video call using video and audio, but it may be an interview using either video or audio. The online interview is conducted between the pharmacist terminal 12 and the patient terminal 13.

[0033] The pharmacist terminal operation unit 35 is, for example, an operation unit using devices such as a mouse and a keyboard. The reading device 36 is, for example, a barcode reader and a scanner. The reading device 36 reads information written on a prescription. If the prescription is electronic data, the reading device 36 does not need to be provided in the pharmacist terminal 12. The configuration of the pharmacist terminal 12 is not limited to the example in FIG. 3, and may include other configurations, or some configurations may be omitted.

[0034] 4 is a block diagram showing an example of the configuration of the patient terminal 13. As described above, the patient terminal 13 is a smartphone. However, the patient terminal 13 may be a device such as a tablet terminal or a mobile phone. The patient terminal 13 corresponds to a computer. The patient terminal 13 includes a patient terminal control unit 41, a patient terminal storage unit 42, a patient terminal communication unit 43, and a touch panel display 44.

[0035] The patient terminal control unit 41 performs overall control of the patient terminal 13. The patient terminal control unit 41 includes, for example, one or more processors such as a CPU. The processor executes a program stored in the patient terminal storage unit 42, thereby realizing control of the patient terminal 13 in this embodiment. The patient terminal control unit 41 also executes an application of this embodiment. The application is realized by a program in which processing contents are described.

[0036] The patient terminal storage unit 42 is, for example, a memory or a portable recording medium. The patient terminal storage unit 42 stores various information in addition to the above-mentioned programs. The patient terminal communication unit 43 communicates with other terminals and servers via the network NW. The patient terminal storage unit 42 also stores the above-mentioned applications.

[0037] The touch panel display 44 displays information and accepts operations from the patient. For example, assume that an icon for executing an application is displayed on the touch panel display 44. In this case, when the touch panel display 44 accepts an instruction to start the icon, it outputs an instruction to start the icon to the patient terminal control unit 41. As a result, the patient terminal control unit 41 starts executing the application. The configuration of the patient terminal 13 is not limited to the example in FIG. 3, and may include other configurations, or some configurations may be omitted.

[0038] 5 is a block diagram showing an example of the configuration of the management server 14. The management server 14 includes a management server control unit 51, a management server storage unit 52, a management server communication unit 53, a management server display unit 54, and a management server operation unit 55.

[0039] The management server control unit 51 is a computer that performs overall control of the management server 14. The management server control unit 51 includes, for example, one or more processors such as a CPU. The processor executes a program stored in the management server storage unit 52, thereby realizing control of the management server 14 in this embodiment.

[0040] The management server storage unit 52 is, for example, a memory or a hard disk drive. The management server storage unit 52 stores various information in addition to the above-mentioned programs. As described above, the management server 14 manages the entire treatment system 10. The management server storage unit 52 stores information received from each terminal. The management server communication unit 53 communicates with each device via the network NW.

[0041] The management server display unit 54 is a display and displays various information. For example, the management server display unit 54 may display information to be provided to each terminal. The management server operation unit 55 is an operation unit using devices such as a mouse and a keyboard. The configuration of the management server 14 is not limited to the example of FIG. 5, and may include other configurations, or some configurations may be omitted.

[0042] Next, the setting of the application in the patient terminal 13 will be described. The application in this embodiment will be described. The application executed in the patient terminal 13 is an application used for the treatment of the patient. In this embodiment, the daily behavior management of the patient is a part of the treatment of the patient.

[0043] For example, the treatment of a type 2 diabetes patient requires continued appropriate exercise. The application of this embodiment manages, for example, whether the type 2 diabetes patient continues appropriate exercise on a daily basis. As described above, the patient terminal 13 operates in cooperation with the pedometer 13A, and can obtain the number of steps counted by the pedometer 13A through short-range wireless communication.

[0044] The application executed on the patient terminal 13 acquires the number of steps taken in one day by the patient wearing the pedometer 13A. This allows the application executed on the patient terminal 13 to recognize the number of steps taken in one day by the patient as behavior information of the patient.

[0045] The application executed on the patient terminal 13 transmits the patient's behavior information to the management server 14. The management server 14 performs a predetermined process on the received patient's behavior information and stores it in the management server storage unit 52. The doctor terminal 11 and the pharmacist terminal 12 can acquire the patient's behavior information stored in the management server storage unit 52 of the management server 14. This allows the doctor operating the doctor terminal 11 to examine the patient while checking the patient's behavior information.

[0046] In this embodiment, not only the doctor who operates the doctor terminal 11 but also the pharmacist who operates the pharmacist terminal 12 can obtain the patient behavior information. The pharmacist terminal 12 is the pharmacist terminal used when setting an application in the patient terminal 13 based on a prescription, or a different pharmacist terminal located in the same pharmacy.

[0047] The pharmacist terminal 12 can conduct an online interview with an application executed on the patient terminal 13. In the online interview, the pharmacist can provide self-management support and specific health guidance to the patient while referring to the behavioral information of the patient displayed on the pharmacist terminal display unit 34 of the pharmacist terminal 12. This allows doctors, pharmacists, and registered dietitians to cooperate in managing the behavior of patients.

[0048] The target patient of this embodiment does not have to be a type 2 diabetes patient, and may be, for example, an obese patient, etc. Furthermore, the above-mentioned behavior information for managing the patient's behavior is not limited to the information on the number of steps, and may be any information such as the pulse rate when the patient exercises.

[0049] The treatment system 10 of this embodiment can set behavioral goals for the treatment of a patient using an application executed on the patient terminal 13. The goals are set based on the patient's consent. The application executed on the patient terminal 13 periodically transmits behavioral information on the patient's behavior to the management server 14, and receives feedback information based on the behavioral information from the management server 14. The feedback information includes information on whether or not the goal has been achieved, or information on barriers and challenges, which will be described later. This allows for interaction between the user and the treatment system 10.

[0050] The feedback information includes information for achieving the goal (for example, a message encouraging the patient to achieve the goal and information on the result of the behavior). An application executed on the patient terminal 13 displays the feedback information on the touch panel display 44. The operation of such an application is part of an intervention or treatment for the patient's behavior.

[0051] The application executed on the patient terminal 13 autonomously manages the progress of the set target number of steps on a daily basis, and performs processing according to the progress (for example, displaying a message), etc. Also, support is provided for the pharmacist who operates the pharmacist terminal 12 and the doctor who operates the doctor terminal 11 in managing the patient's behavior. The processing executed on each terminal will be described below.

[0052] 6 is a sequence diagram showing an example of the flow of setting an application to the patient terminal 13. When a doctor examines a patient, the doctor terminal 11 is used. The doctor performs an operation using the doctor terminal operation unit 25, and the doctor terminal 11 accepts the doctor's operation.

[0053] The doctor terminal 11 has a function of issuing a prescription. The prescription contains information on the medicine to be prescribed to the patient, and also contains information for setting an application. For example, the doctor who operates the doctor terminal 11 may determine the prescription depending on which stage of the behavioral change stage model the target patient belongs to.

[0054] Also, depending on the patient, setting an application in the patient terminal 13 may be contraindicated. For example, depending on the patient, exercise restrictions may be required. In such a case, it is necessary to prevent an application that encourages the patient's behavior from being set in the patient terminal 13. In this case, the doctor terminal 11 issues a prescription stating that the application will not be set because it falls under the contraindication. The doctor terminal 11 may issue an instruction sheet stating that the application will not be prescribed because it falls under the contraindication, separately from the prescription.

[0055] In the following, it is assumed that an application is set in the patient terminal 13 of a patient to whom this embodiment is applied. The doctor terminal 11 accepts an operation from the doctor and inputs the prescription contents of the application (step S11). The prescription contents that define the contents of the prescription include information on at least the acceptable range of behavior that is acceptable for the patient's behavior. The acceptable range of behavior indicates, for example, an acceptable range for at least one of the type and amount of the patient's behavior. The type of behavior is, for example, the type of exercise that the patient is allowed to perform. The amount of behavior is, for example, the amount of exercise that the patient is allowed to perform. In this embodiment, it is assumed that the doctor terminal 11 sets, as the prescription contents, the upper and lower limits of the number of steps presented as a daily goal for the patient.

[0056] When the doctor terminal 11 receives an operation to issue a prescription from the doctor, it issues the prescription (step S12). After executing the process of step S12, the doctor terminal 11 transmits information indicating the contents of the issued prescription (prescription information) to the management server 14 via the network NW (step S13). In this embodiment, the prescription information includes information for setting the above-mentioned application. The prescription information in this embodiment includes at least information indicating the upper and lower limits of the number of steps presented as a daily goal for the patient.

[0057] Here, the prescription information may be associated with patient data. In this case, the prescription information and the patient data are transmitted from the doctor terminal 11 to the management server 14 via the network NW.

[0058] The prescription issuing device 11A prints the prescription issued in step S12 on paper. When the doctor terminal 11 issues the above patient data, the prescription issuing device 11A prints a code obtained by encrypting the patient data together with the prescription. The code is a code that can uniquely identify the patient ID, and can be read by the reading device 36 of the pharmacist terminal 12. The above code may also be a one-time code that cannot be reused after being used once.

[0059] The printed prescription is given to the patient. If a paper sheet containing the patient data code (hereinafter referred to as the patient data sheet) is also printed, the patient data sheet is also given to the patient. The prescription and patient data may be electronic data instead of paper. In this case, since there is no need to print a paper prescription, the process of step S12 may be omitted.

[0060] Next, at the pharmacy, the reading device 36 of the pharmacist terminal 12 acquires the prescription information written on the prescription (step S14). For example, in the pharmacy, the pharmacist receives the prescription from the patient and operates the pharmacist terminal 12 to start reading the prescription information by the reading device 36. As a result, the reading device 36 reads the prescription information, and the pharmacist terminal 12 recognizes the contents of the prescription information. The same applies when a patient data sheet is issued.

[0061] The prescription information written on the prescription may be a two-dimensional code or the like, or may be characters describing the contents of the prescription. When the prescription information written on the prescription is a two-dimensional code or the like, the reading device 36 reads the prescription information written on the prescription, and the pharmacist terminal 12 recognizes the contents of the prescription information. When the prescription contents are written characters, the pharmacist terminal 12 accepts an input operation of the prescription contents by the pharmacist using the pharmacist terminal operation unit 35. As a result, the pharmacist terminal 12 recognizes the contents of the prescription information. The above two-dimensional code is not a code that cannot be reused after being used once, like a code printed on a patient data sheet.

[0062] The pharmacist terminal 12 may recognize the contents of the prescription information and obtain the patient data corresponding to the patient ID indicated by the prescription information from the management server 14 via the network NW. In this way, the pharmacist terminal 12 recognizes the patient data as well as the contents of the prescription information. In this case, the patient data paper becomes unnecessary.

[0063] Next, an application executed on the patient terminal 13 is started based on an operation by the patient (step S15). The application executed on the patient terminal 13 may be installed in the patient terminal 13 in advance.

[0064] Next, the application executed on the patient terminal 13 undergoes an activation process (step S16). The application executed on the patient terminal 13 is activated, thereby enabling the use of the application. The application activation process is performed in cooperation between the patient terminal 13 and the pharmacist terminal 12.

[0065] The prescription information includes a prescribing doctor ID. Furthermore, the pharmacist terminal 12 holds a pharmacy ID that identifies the pharmacy. Furthermore, the pharmacist terminal 12 generates a patient ID of the patient corresponding to the prescription. When the patient terminal 13 and the pharmacist terminal 12 work together to perform an application activation process, the patient ID, the prescribing doctor ID, and the pharmacy ID are linked. In other words, the application is set in the patient terminal 13 by linking the patient ID, the prescribing doctor ID, and the pharmacy ID. This allows the patient, the doctor, and the pharmacist to work together, allowing both the doctor and the pharmacist to manage the patient's behavior.

[0066] The pharmacist terminal 12 sets a barrier based on the operation by the pharmacist (step S18). The pharmacist terminal 12 also sets the first target number of steps and a challenge based on the operation by the pharmacist (step S19). The target number of steps and challenges from the second time onwards are set based on the operation on an application executed on the patient terminal 13. Details will be described later.

[0067] As described above, the patient's daily behavior is managed as part of the patient's treatment. In this embodiment, the management of the patient's daily behavior involves setting the patient's target number of steps each day, checking the actual number of steps, and comparing the target and the actual number. When the patient walks, there are some physical, environmental, and psychological barriers. For example, the patient's condition, weather, and the like, which change daily, become barriers to the patient's walking. Information indicating the barriers (barrier information) is the barrier.

[0068] The challenge is information (goal information) indicating the goal of the patient's daily activities, and indicates how to walk, etc., that is set according to the patient's condition. If the patient is unable to walk, information indicating activities that can be performed at home (e.g., light exercise, housework, etc.) is included in the goal information. The challenge can be set, for example, according to the patient's walking environment (places that can be walked, things that can be done while walking, places that can be reached by walking, etc.).

[0069] The details of the above barriers and challenges are heard from the patient operating the patient terminal 13 by the pharmacist operating the pharmacist terminal 12 and input into the pharmacist terminal 12.

[0070] The above-mentioned patient data is issued by the doctor terminal 11, but may be generated by, for example, the pharmacist terminal 12. In this case, the pharmacist terminal 12 generates the test result data acquired from the management server 14 as patient data together with the set barrier and challenge. At this time, the pharmacist terminal 12 may associate the patient data with the prescribing doctor ID and transmit it to the management server 14. In addition, when the pharmacist terminal 12 acquires the test result data, the pharmacist can refer to the test result data. The test result data may be referable by an application executed on the patient terminal 13.

[0071] In this embodiment, an example in which a challenge is set for each barrier will be described, but the barrier and the challenge may be set separately. In the following description, it is assumed that the initial target number of steps is set when the first challenge is set in step S19.

[0072] After the process of step S17 is executed, a barrier and an initial target number of steps and a challenge are set in the pharmacist terminal 12 based on what the pharmacist has heard from the patient. The pharmacist terminal 12 recognizes the received settings of the barrier, the initial target number of steps and the challenge. The pharmacist terminal 12 transmits information (setting information) relating to the recognized settings of the barrier, the initial target number of steps and the challenge to the management server 14 in association with the patient ID (step S20).

[0073] Based on the activation information received in step S17 and the setting information received in step S20, the management server 14 links the patient ID, the prescribing doctor ID, and the pharmacy ID, and registers various pieces of information (step S21). At this time, the various pieces of information are stored in the management server storage unit 52.

[0074] The pharmacist may operate the pharmacist terminal operation unit 35 to set the timing of the online interview, which will be described later, when setting the barrier and the initial target number of steps or challenge in the pharmacist terminal 12. When the pharmacist terminal 12 accepts the setting of the timing of the online interview, the pharmacist terminal 12 may transmit information indicating the timing of the online interview to the management server 14.

[0075] The barrier and the initial target number of steps or challenge may be set based on an operation performed on the patient terminal 13. For example, the barrier and the initial target number of steps or challenge may be set on the patient terminal 13 by the patient together with the pharmacist who operates the pharmacist terminal 12. Also, the barrier and the initial target number of steps or challenge may be set based on an operation performed on the doctor terminal 11.

[0076] 7 is a diagram showing an example of a barrier list and multiple challenge lists. The barrier list includes multiple items, and one or more items can be selected. In addition, each item in the barrier list corresponds to a challenge list. The challenge list includes multiple items, and one or more items can be selected.

[0077] Information on the barrier list and each challenge list is held by management server 14. Pharmacist terminal 12 acquires information on the barrier list and each challenge list from management server 14 and displays it on pharmacist terminal display unit 34. Then, when pharmacist terminal 12 accepts the selection of the barrier and challenge by the pharmacist, pharmacist terminal 12 recognizes the selected barrier and challenge (initial challenge). This causes the processes of steps S18 and S19 described above to be performed.

[0078] For example, assume that, based on the results of a pharmacist's interview with a patient, the pharmacist sets a barrier of "I don't want to walk because I seem tired" and a first challenge of "I'll walk when I feel good" using the pharmacist terminal operation unit 35. In this case, the pharmacist terminal 12 recognizes the above settings received using the pharmacist terminal operation unit 35. It is possible to select multiple barriers and first challenges, rather than just one.

[0079] Fig. 8 is a diagram showing an example screen of an application executed on the patient terminal 13. The example screen of Fig. 8 shows the status of the patient's daily actions after the application activation process has been performed. The example screen of the application executed on the patient terminal 13 is not limited to the example of Fig. 8.

[0080] The patient terminal 13 includes a screen 60. The screen 60 is a screen displayed on the touch panel display 44. Predetermined operations can be performed on each screen displayed on the touch panel display 44. The screen 60 includes a step count item 61, a measurement result item 62, and a challenge item 63.

[0081] The step count item 61 includes information on the step count goal and the actual step count for each day. In the example of Fig. 8, the actual step count with respect to the step count goal is not only displayed as a numerical value, but also displayed in the form of an indicator showing the degree of achievement (=actual step count / step count goal).

[0082] Here, the step count target will be explained. The step count target is set by an application executed on the patient terminal 13. However, as described above, when a prescription is issued by the doctor terminal 11, the upper and lower limit values ​​of the number of steps presented as the patient's daily goal are set as prescription information. The application executed on the patient terminal 13 sets the target number of steps within a range that is equal to or less than the upper limit value and equal to or more than the lower limit value of the number of steps indicated by the prescription information. In other words, the step count target set by the application executed on the patient terminal 13 is not allowed to exceed the upper and lower limit values ​​of the number of steps indicated by the prescription information.

[0083] The measurement result items 62 include weight measurement results and blood pressure measurement results. For weight measurement results, the weight value measured by the patient may be input through the touch panel display 44, or the weight value may be acquired from a weight scale that can be linked through communication. For blood pressure measurement results, the blood pressure value measured by the patient may be input through the touch panel display 44, or the blood pressure value may be acquired from a blood pressure monitor that can be linked through communication. For items for which measurement results have been acquired, a check mark is placed in the check box.

[0084] Challenge item 63 is an item that indicates the content of today's challenge. Challenge item 63 includes multiple items 63A, 63B. Challenge item 63 may include three or more items. Each item 63A, 63B represents the content of one challenge. The content of each challenge is set based on the content set in step S19 for the first challenge. Furthermore, the content of the second and subsequent challenges is set based on the content set in patient terminal 13.

[0085] Each of items 63A, 63B includes challenge information indicating the content of the challenge and barrier information indicating the content of the barrier corresponding to the challenge. When the patient checks a check box using the touch panel display 44, the fact that the corresponding challenge has been performed is input to the patient terminal 13. In the example of Fig. 8, the challenge of item 63A indicates that it has been performed, but the challenge of item 63B indicates that it has not been performed.

[0086] The management server 14 acquires information set using the patient terminal 13. For example, the patient terminal 13 transmits to the management server 14 the actual number of steps per day obtained based on the number of steps counted by the pedometer 13A. The patient terminal 13 also transmits to the management server 14 information on whether a check box corresponding to each challenge item 63 has been checked. The patient terminal 13 may transmit to the management server 14 information indicating the actual number of steps per day and information indicating whether each challenge item 63 has been checked in association with the patient ID. The management server 14 stores each piece of information described above for each patient ID.

[0087] Fig. 9 is a diagram showing an example of the transition of the daily review screen. The display of the review screen in Fig. 9 is also an intervention by an application executed on the patient terminal 13. For example, the daily review screen may be automatically displayed on the touch panel display 44 by the application executed on the patient terminal 13 at a predetermined time of day (for example, a predetermined time in the evening). Alternatively, the daily review screen may be displayed on the touch panel display 44 in response to a predetermined function being selected while the application executed on the patient terminal 13 is running.

[0088] Screens 60A to 60D are screens displayed on the touch panel display 44 of the patient terminal 13. Screen 60A is an example of a screen for selecting the implementation status of the set challenge. Each piece of information on screens 60A to 60D is displayed by an application executed on the patient terminal 13 acquiring it from the management server 14.

[0089] Screen 60A includes buttons for Performed, Not Performed, and Not Applicable. The Performed button is a button for selecting that the challenge has been performed. The Not Performed button is a button for selecting that the challenge has not been performed. The Not Applicable button is a button indicating that the challenge was not applicable on a particular day. The patient selects and presses one of the three buttons displayed on touch panel display 44.

[0090] The non-applicable button is a button that is selected when the situation does not correspond to the situation in which the challenge should be performed. For example, assume that the challenge is "Be conscious of walking during work" and today is not a work day. In this case, the situation does not correspond to the situation in which the challenge should be performed. In such a case, the non-applicable button can be selected.

[0091] Screen 60B shows an evaluation of the progress of the challenge. The application executed on the patient terminal 13 transmits information on the number of steps taken each day to the management server 14 as behavior information.

[0092] For example, suppose that the management server 14 stores information indicating an evaluation for each ratio value of the information on the step value per day to the target number of steps in the management server storage unit 52. The information indicating the evaluation stored in the management server storage unit 52 may indicate that the higher the ratio value, the higher the evaluation, and that the lower the ratio value, the more the behavior is encouraged.

[0093] The management server 14 transmits information indicating the evaluation according to the value of the ratio to the patient terminal 13. The application executed on the patient terminal 13 causes the touch panel display 44 to display the received information indicating the evaluation, such as screen 60B.

[0094] The screen 60C shows an evaluation of the progress toward the goal. The screen 60C includes the same information as the step count item 61 in FIG. 8. The screen 60C also includes information indicating whether the target number of steps has been achieved, and information indicating advice for each of the cases where the target number of steps has been achieved and where the target has not been achieved. The information indicating the advice is acquired from the management server 14.

[0095] Screen 60D is an example of a screen for inputting reason information. Reason information includes reasons why the step count target was achieved and reasons why it was not achieved. The example in FIG. 9 is an example of a screen for inputting reasons why the step count target was achieved. An example of a screen for inputting reasons why the step count target was not achieved is displayed as a screen different from screen 60D in FIG. 9. The screen for inputting reasons why the step count target was achieved may be displayed when the actual number of steps is significantly high. The screen for inputting reasons why the step count target was not achieved may be displayed when the actual number of steps is significantly low compared to the target number of steps.

[0096] Screen 60D includes selection items and a free entry field. The selection items allow the patient to select an item for the reason why the step count target was achieved. Information for the item for the reason why the step count target was achieved is acquired from management server 14. The free entry field is a field for the patient to input any information into touch panel display 44. By inputting information into screen 60D, the application executed on patient terminal 13 can recognize the reason why the step count target was achieved.

[0097] The application executed on the patient terminal 13 transmits information indicating the reason why the step count target was achieved to the management server 14 in association with the patient ID. The management server 14 stores the information indicating the reason why the step count target was achieved for each patient ID. The doctor terminal 11 and the pharmacist terminal 12 can refer to the information indicating the reason why the step count target was achieved. This allows the doctor operating the doctor terminal 11 to refer to the reason why the step count target was achieved or the reason why the step count target was not achieved when examining a patient. In addition, the pharmacist operating the pharmacist terminal 12 can refer to the reason why the step count target was achieved or the reason why the step count target was not achieved when conducting an online consultation, which will be described later.

[0098] Next, a description will be given of a daily review process executed by an application executed on the patient terminal 13. Fig. 10 is a flowchart showing an example of the flow of the review process. The flowchart in Fig. 10 is executed, for example, at a predetermined time in the evening of one day. Also, the flowchart in Fig. 10 is executed every time the application is started, regardless of the timing for reviewing one day.

[0099] The application executed on the patient terminal 13 acquires setting information including barrier information and challenge information from the management server 14 via the network NW (step S31). Then, the application executed on the patient terminal 13 acquires measurement information (step S32). The measurement information includes information on the number of steps counted by the pedometer 13A, the measurement results of body weight, and the measurement results of blood pressure.

[0100] The application executed on the patient terminal 13 transitions between screens as shown in Fig. 9 and displays them. On each screen, the patient inputs information to the touch panel display 44. The patient terminal 13 accepts the input operation (step S33). The information on the input operation accepted by the patient terminal 13 includes information on the implementation status of the challenge selected based on the screen 60A and reason information on the screen 60D.

[0101] The application executed on the patient terminal 13 transmits the measurement information acquired in step S32 and the information on the input operation accepted in step S33 as behavior information to the management server 14 (step S34).

[0102] The above process is one of the functions in which an application executed on the patient terminal 13 intervenes, and is used when the patient looks back on his or her actions for the day. The patient who operates the patient terminal 13 can use each screen example in FIG. 9 as a reference when carrying out actions on the following day and thereafter.

[0103] Next, the target step count setting process and the challenge setting process will be described. The target step count setting process and the challenge setting process described below are also one of the functions in which the application executed on the patient terminal 13 intervenes. As described above, the second and subsequent step count setting and challenge are set based on the operation on the patient terminal 13. The step count setting and challenge setting by the application executed on the patient terminal 13 (the second and subsequent step count setting and challenge setting) are performed once a week.

[0104] For example, the function for setting the number of steps and performing the challenge setting process may be automatically started when an application executed on the patient terminal 13 detects that a predetermined day of the week has arrived. Also, the function for setting the number of steps and performing the challenge setting process may be started based on an operation on the patient terminal 13.

[0105] 11 is a diagram showing an example of the transition of the screen for deciding the target number of steps from the second time onwards. The screen 60E is a screen for setting the degree of confidence that the target can be achieved. In the screen 60E, the number of days can be selected from 1 to 7 days. In the screen 60E, 5900 steps is displayed as the target number of steps according to the patient ID acquired from the management server 14.

[0106] For example, the application executed on the patient terminal 13 may set the target number of steps depending on whether the input number of days is a predetermined number of days (e.g., 5 days) or more. For example, when the input number of days is 5 days, the application executed on the patient terminal 13 sets 5900 steps shown on the screen 60E as the target number of steps.

[0107] On the other hand, if the input number of days is less than five days, the application executed on the patient terminal 13 resets the target number of steps. For example, the application executed on the patient terminal 13 sets the target number of steps to 5800 steps, which is a predetermined number of steps (e.g., 100 steps) less than 5900 steps, and redisplays the screen 60E. The application executed on the patient terminal 13 redisplays the screen 60E while decreasing the target number of steps until the input number of days is five days or more.

[0108] Then, when the number of days inputted reaches 5 or more, the application executed on the patient terminal 13 displays a screen for deciding the target number of steps, such as screen 60F. This sets the target number of steps. Since the set target number of steps is the number of steps agreed upon by the patient, the target number of steps is set based on two-way communication with the patient. Note that the target number of steps will not fall below the lower limit indicated in the prescription information, and will not fall below the value obtained by subtracting a predetermined number of steps from the target number of steps one week ago.

[0109] 12 is a diagram showing an example of the transition of the challenge setting screen. Screens 60G to 60J are screens displayed on the touch panel display 44. Screen 60G is a screen showing the progress of the weekly step count. The information of screen 60G is acquired from management server 14. As described above, management server 14 acquires information on the step count for each day corresponding to the patient ID. Management server 14 also acquires information on the target step count corresponding to the patient ID.

[0110] The management server 14 stores information associated with the patient ID, indicating whether the step count for one day in one week has reached the target number of steps for that day. The management server 14 transmits information on the number of days on which the target number of steps has been achieved to the patient terminal 13. This allows the application executed on the patient terminal 13 to display the screen 60G.

[0111] The management server 14 stores information on advice according to the number of days to achieve the goal. The management server 14 transmits the information on advice according to the number of days to achieve the goal to the patient terminal 13. This enables the application executed on the patient terminal 13 to display advice such as that shown on a screen 60H.

[0112] Screen 60I is a challenge selection screen. Selectable challenge information is displayed on screen 60I. The selectable challenge information is acquired from management server 14. In the example of screen 60I in FIG. 12, multiple challenges can be selected. Also, multiple challenges may be selectable for each reason for not being able to walk. In this case, screen 60I is displayed repeatedly.

[0113] Fig. 13 is a flow chart showing an example of the flow of setting information processing for each week. The application executed on the patient terminal 13 sets the target number of steps input based on the screens 60E and 60F in Fig. 11 (step S41). If the number of days input by the patient is small, the application executed on the patient terminal 13 reduces the target number of steps and resets it.

[0114] 12, when a challenge is selected on screen 60I, the application executed on the patient terminal 13 accepts the selected challenge (step S42). Then, the application executed on the patient terminal 13 transmits weekly setting information including the target number of steps set in step S41 and the challenge accepted in step S42 to the management server 14 (step S43).

[0115] As described above, the application executed on the patient terminal 13 performs review processing every day, and resets the target number of steps and the challenge every week. The application executed on the patient terminal 13 also performs review processing every week. As described above, the target number of steps and the challenge are reset every week based on the patient's agreement. Also, advice such as that on screen 60H in FIG. 12 is displayed as feedback information. The above is an intervention by the application. Then, an intervention by a pharmacist is performed at intervals longer than the intervention by the application (for example, once a month). Hereinafter, the intervention by the pharmacist is described as an online consultation, but the intervention by the pharmacist may be performed by a method other than an online consultation.

[0116] Fig. 14 is a flowchart showing an example of the flow of processing executed by the patient terminal 13 during an online consultation. For example, assume that an application executed on the patient terminal 13 has a function for reserving an online consultation. In this case, the application executed on the patient terminal 13 starts up the online consultation function at or before the reservation date and time (step S51). The online consultation function may be a part of the function of the above application, or may be a video call function that the patient terminal 13 has.

[0117] The patient terminal 13 starts communication with the pharmacist terminal 12 via the network NW (step S52). When the preparation for the online interview of the pharmacist terminal 12 operated by the pharmacist is completed, the online interview is performed (step S53).

[0118] In the online interview, video and audio communication can be carried out between the patient who operates the patient terminal 13 and the pharmacist who operates the pharmacist terminal 12. This allows the patient to set goals for future actions based on specific advice from the pharmacist, and to recognize areas for improvement in daily actions, etc.

[0119] When the patient terminal 13 is operated by the patient to terminate the online consultation function, the patient terminal 13 accepts the operation. As a result, the application executed on the patient terminal 13 terminates the online consultation function (step S54). The online consultation function may be terminated based on an operation performed on the pharmacist terminal 12.

[0120] FIG. 15 is a diagram showing an example of an online consultation. Screen 60J is a screen displayed on touch panel display 44 of patient terminal 13. Screen 60J includes a pharmacist screen and a patient screen. The pharmacist screen is a video obtained by shooting a pharmacist operating pharmacist terminal 12. The patient screen is a video obtained by shooting a patient operating patient terminal 13. Voice spoken by the pharmacist operating pharmacist terminal 12 is output from the speaker of patient terminal 13.

[0121] 16 is a diagram showing an example of a screen of an additional function of an application executed on the patient terminal 13. The additional function allows reference to past data for a patient with a patient ID linked to the patient terminal 13. Screen 60K is a screen displayed on the touch panel display 44 by the additional function of the application executed on the patient terminal 13. Screen 60K includes information on the number of steps taken for each day up to the present in a week. Each piece of step count information displayed on screen 60K is obtained from the management server 14.

[0122] Screen 60L includes a graph showing the change in the correlation between the number of steps and body weight. The bar graph represents the change in the number of steps per day, and the line graph represents the change in body weight per predetermined period (e.g., per day, per week, or per three months). Information on the change in the number of steps and the change in body weight are stored in management server storage unit 52 of management server 14. An application executed on patient terminal 13 acquires information on the change in the number of steps and the change in body weight from management server 14 and displays screen 60L.

[0123] Screen 60M includes a graph showing the change in the correlation between the number of steps and blood pressure. The bar graph shows the change in the number of steps per day, and the line graph shows the change in blood pressure for each predetermined period. Information on the change in the number of steps and the change in blood pressure are stored in management server storage unit 52 of management server 14. An application executed on patient terminal 13 acquires information on the change in the number of steps and the change in blood pressure from management server 14 and displays screen 60L.

[0124] Next, a description will be given of the process executed by the pharmacist terminal 12 during an online consultation. Fig. 17 is a flow chart showing an example of the flow of the process executed by the pharmacist terminal 12 during an online consultation.

[0125] When the pharmacist performs an operation to start an online consultation using the pharmacist terminal operation unit 35, the pharmacist terminal 12 accepts the operation and starts the online consultation function (step S61). The online consultation function of the pharmacist terminal 12 is different from the online consultation function of the application executed on the patient terminal 13.

[0126] As described above, the management server storage unit 52 of the management server 14 stores behavioral information for each patient ID. The pharmacist terminal 12 acquires behavioral information corresponding to the patient ID of the patient with whom the online interview is to be conducted from the management server 14. As described above, the online interview is conducted at a predetermined interval (for example, once a month). The management server 14 provides the pharmacist terminal 12 with behavioral information including information (summary information) summarizing the behavioral information at the predetermined interval.

[0127] In addition, the management server 14 stores various information such as information indicating the progress of the challenge, barrier information, weight transition information, blood pressure transition information, etc. The management server 14 provides the pharmacist terminal 12 with various information corresponding to the patient ID of the patient who is the subject of the online interview together with behavioral information.

[0128] The pharmacist terminal 12 acquires various pieces of information provided by the management server 14 (step S62). The pharmacist terminal 12 displays a pharmacist screen including the acquired various pieces of information on the pharmacist terminal display unit 34 (step S63). This allows the pharmacist operating the pharmacist terminal 12 to grasp information on the behavior of the patient who is the subject of the online interview from the previous online interview to the current online interview.

[0129] The pharmacist terminal 12 starts communication with the patient terminal 13 via the network NW (step S64). When the preparation for the online interview of the patient terminal 13 operated by the patient is completed, the online interview is executed (step S65). In step S63, the pharmacist terminal display unit 34 displays various information including behavioral information from the previous online interview to the current online interview for the patient who is the subject of the online interview. This allows the pharmacist to provide self-management support and specific health guidance to the patient while referring to various information during the online interview using the pharmacist terminal 12. In addition, the pharmacist operating the pharmacist terminal 12 can ask the patient whether any side effects (e.g., knee pain, etc.) have occurred due to the use of the application executed on the patient terminal 13 during the above-mentioned online interview.

[0130] When the pharmacist performs an operation to end the online consultation function on the pharmacist terminal 12, the pharmacist terminal 12 accepts the operation. As a result, the pharmacist terminal 12 ends the online consultation function (step S66). The online consultation function may be ended based on an operation performed on the patient terminal 13.

[0131] After the online interview is completed, the pharmacist may use the pharmacist terminal operation unit 35 to transmit information regarding the results of the online interview (online interview information). The pharmacist terminal 12 may transmit the online interview information to the management server 14 in association with the patient ID. The management server 14 may store the patient ID and the online interview information in association with each other in the management server storage unit 52. This allows, for example, a doctor operating the doctor terminal 11 to conduct a medical examination while referring to the online interview information.

[0132] Next, an example of the flow of processing of the doctor terminal 11 when a doctor performs a medical examination will be described. Fig. 18 is a flow chart showing an example of the flow of processing executed by the doctor terminal 11 during a medical examination. The interval between patient examinations performed by a doctor operating the doctor terminal 11 is longer than the interval between interventions by a pharmacist using the pharmacist terminal 12. For example, the interval between patient examinations is three months.

[0133] The doctor terminal 11 acquires various information provided by the management server 14 (step S71). The various information acquired by the doctor terminal 11 in step S71 may be the same as or different from the information acquired by the pharmacist terminal 12 in step S62. For example, the doctor terminal 11 may acquire the above-mentioned online interview information from the management server 14 in addition to various information including the patient's behavior information.

[0134] The doctor terminal 11 displays the consultation screen including the above-mentioned various information on the doctor terminal display unit 24 (step S72). The doctor operating the doctor terminal 11 can refer to various information including the patient's behavior information from the previous consultation to the current consultation based on the information displayed on the doctor terminal display unit 24. The doctor operating the doctor terminal 11 can check the safety of whether any trouble has occurred due to the use of the application executed on the patient terminal 13. For example, when the above-mentioned online interview information is displayed on the consultation screen, the doctor operating the doctor terminal 11 can also refer to information on intervention by a pharmacist. This allows the doctor terminal 11 to present information that contributes to the consultation of the patient. The doctor may operate the doctor terminal 11 to register the results of a blood test performed in the hospital. This allows the doctor operating the doctor terminal 11 to refer to the change in the result of the current blood test compared to the result of the previous blood test.

[0135] As described above, in this embodiment, based on the prescription issued by the doctor terminal 11, the pharmacist terminal 12 installed in the pharmacy sets an application for managing the patient's behavior in the patient terminal 13. The patient terminal 13 in which the application is set periodically transmits behavior information to the management server 14. Then, both the doctor terminal 11 and the pharmacist terminal 12 acquire the behavior information. This allows the doctor operating the doctor terminal 11 and the pharmacist operating the pharmacist terminal 12 to work together to manage the patient's behavior. Furthermore, the application executed on the patient terminal 13 allows various settings (such as setting a target number of steps) to be made based on the patient's agreement. This allows two-way communication between the patient and the treatment system 10.

[0136] <Other embodiments> Next, another embodiment will be described. As described using the example of Fig. 11, the second and subsequent target number of steps is set, for example, once a week, by an application executed on the patient terminal 13. The management server 14 may control the application executed on the patient terminal 13 as follows to set the second and subsequent target number of steps (new target number of steps) based on the past walking record of the patient associated with the patient ID.

[0137] As described above, the behavioral information includes information on the step count counted by the pedometer 13A. The management server 14 acquires the behavioral information including the step count information for each day. The management server 14 stores and manages the information on the step count information for each day for each patient ID in the management server storage unit 52 as a step count record.

[0138] For example, the management server 14 may refer to the number of days in which the target was achieved for a predetermined number of past days stored in the management server storage unit 52, and if the number of days in which the target was achieved is large, control may be performed so that a larger number of steps is presented as the target number of steps from the second time onwards. The management server 14 controls an application executed on the patient terminal 13 to perform each of the following processes.

[0139] 19 is a flowchart showing an example of a process flow of another embodiment. The management server 14 judges whether the number of days during a predetermined number of days in the past is equal to or greater than a first number of days (step S81). The predetermined number of days is, for example, the past one week. The number of days during which the goal is achieved is the number of days during which the set target number of steps is achieved. The first number of days is, for example, six days in one week.

[0140] For example, assume that the currently set target number of steps corresponding to the patient ID is 6000 steps, and the number of days in the most recent past week when the actual number of steps exceeded 6000 steps was 6 or more. In this case, the management server 14 judges Yes in step S81 and proceeds to the process of step S82. If the judgment in step S81 is Yes, the number of days until the target is achieved for the patient corresponding to the patient ID is large, so a new target number of steps that is greater than the current target number of steps is presented to the patient in order to encourage him or her to walk more.

[0141] When the management server 14 determines that the number of days during which the goal was achieved during the past predetermined number of days is not equal to or greater than the first number of days, the management server 14 determines No in step S81 and advances the process to step S82. The management server 14 determines whether there are consecutive weeks with a large number of days during which the goal was achieved (step S82).

[0142] For example, if there are less than six days in the most recent week in which the daily step count exceeds the number of days for which the goal was achieved, but there are consecutive weeks in the most recent two weeks in which the number of days for which the goal was achieved per week is equal to or exceeds a predetermined threshold (a number of days less than the first number of days: for example, five days), then step S82 is determined to be Yes. In this case, there are consecutive weeks in which the number of days for which the goal was achieved is large.

[0143] If the management server 14 determines "Yes" in step S81 and if the management server 14 determines "Yes" in step S82, the processing proceeds to step S83. In this case, since the patient's actual number of steps is large, a target number of steps that is larger than the current target number of steps is presented as a new target number of steps.

[0144] The management server 14 determines whether a target number of steps higher than the current target number of steps has been set in the past for the patient corresponding to the patient ID (step S83). Information related to the setting of the target number of steps corresponding to the patient ID is stored in the management server storage unit 52 of the management server 14. The management server 14 refers to the information and determines whether a target number of steps higher than the current target number of steps has been set in the past.

[0145] If a target number of steps higher than the current target number of steps has not been set in the past, the management server 14 determines No in step S83 and proceeds to step S84. The management server 14 adds the first number of steps to the current target number of steps and presents the target number of steps as a new target number of steps (step S84).

[0146] On the other hand, if a target number of steps higher than the current target number of steps has been set in the past, the management server 14 determines Yes in step S83 and proceeds to step S85. The management server 14 adds a second number of steps (second number of steps<first number of steps) to the current target number of steps and presents the target number of steps as a new target number of steps (step S85).

[0147] For example, assume that the current target number of steps is 6000. If step S83 returns No, then, for example, 6500 steps, which is the current target number of steps (6000) plus 500 steps as a first step number, is presented. On the other hand, if step S83 returns Yes, then, for example, 6300 steps, which is the current target number of steps (6000) plus 300 steps as a second step number, is presented.

[0148] As described above, when setting the second or subsequent target number of steps, the management server 14 sets the new target number of steps to be presented if a number of steps greater than the current target number has never been set in the past to be greater than the new target number of steps to be presented if a number of steps has been set in the past. In this way, by presenting a new target number of steps that is greater than the current target number of steps, the patient can be encouraged to walk more.

[0149] If the management server 14 determines that the weeks with a large number of days to achieve the goal are not consecutive, it determines No in step S82 and proceeds to step S86. If the determination in step S82 is No, the determination in step S81 is also No, so that the number of days to achieve the goal in this case is not large.

[0150] The management server 14 determines whether the number of days during which the goal was achieved during a predetermined number of past days (one week) is equal to or less than a second number of days (step S86). The second number of days is, for example, one day in a week.

[0151] If the management server 14 determines that the number of days for which the goal was achieved in the past week is not equal to or less than the second number of days, the result in step S86 is No, and the process proceeds to step S87. The management server 14 determines whether there are consecutive weeks with a small number of days for which the goal was achieved (step S87).

[0152] For example, if there is one day in the most recent week in which the daily step count is equal to or greater than the number of days for which the goal was achieved (one day), but there are consecutive weeks in the most recent two weeks in which the number of days for which the goal was achieved is equal to or less than a predetermined number of days (a number of days greater than the second number of days: for example, two days), then step S87 is determined to be Yes. In this case, there are consecutive weeks in which the number of days for which the goal was achieved is small.

[0153] If the management server 14 determines Yes in step S86 and if the management server 14 determines Yes in step S87, the process proceeds to step S88. In this case, since the patient's actual number of steps is small, the management server 14 presents a new target number of steps obtained by subtracting the current target number of steps.

[0154] The management server 14 compares the step value obtained by subtracting a predetermined number of steps from the current target number of steps with the maximum target number of steps (less than the current target number of steps) previously achieved by the patient corresponding to the patient ID stored in the management server storage unit 52 (step S88). The management server 14 presents the larger value of the comparison results as a new target number of steps (step S89).

[0155] For example, suppose the current target number of steps is 6000. Also suppose the above-mentioned predetermined number of steps is 300, and the maximum target number of steps the patient has ever achieved is 5800. In this case, the step value obtained by subtracting the predetermined number of steps from the current target number of steps is 5700, and the maximum target number of steps the patient has ever achieved is 5800, so 5800 steps is presented.

[0156] If step S86 is judged as Yes, or if step S87 is judged as Yes, the patient's step count record corresponding to the patient ID is small, so the patient may have a situation that makes walking difficult. Therefore, if step S86 is judged as Yes, or if step S87 is judged as Yes, the management server 14 presents a new target number of steps that is the number of steps that is the current target number of steps subtracted from the new target number of steps. However, the management server 14 presents as many target steps as possible among them. This makes it possible to encourage the patient to walk more while taking into consideration the patient's circumstances.

[0157] If the management server 14 determines No in step S87, the number of days to achieve the goal is neither too many nor too few. In this case, the current goal number of steps is maintained.

[0158] When the patient operates the patient terminal 13 to determine the presented second or subsequent target number of steps for the new target number of steps presented as described above, the management server 14 sets the target number of steps as the new target number of steps. In this way, the set target number of steps for the second or subsequent times is the number of steps agreed upon by the patient, and therefore the target number of steps is set based on two-way communication with the patient.

[0159] As described above, the management server 14 stores the upper and lower limits of the number of steps per day for the patient indicated in the prescription information in the management server storage unit 52 for each patient ID. As described above, the management server 14 performs control to increase or decrease the target number of steps via an application executed on the patient terminal 13. At this time, the management server 14 presents and sets the target number of steps for the second and subsequent times within the range between the upper and lower limits of the number of steps per day for the patient indicated in the prescription information. This ensures that the contents of the prescription information are observed.

[0160] The management server 14 may repeat the process of presenting the new target number of steps. For example, assume that the patient performs an operation using the patient terminal 13 to not accept a new target number of steps presented by an application executed on the patient terminal 13 by the management server 14.

[0161] In this case, the management server 14 may control an application executed on the patient terminal 13 to re-present as a new target number of steps a number of steps obtained by subtracting a predetermined number of steps (e.g., 200 steps) from the presented new target number of steps. In response to this, when an operation to accept the re-presented new target number of steps is performed on the patient terminal 13, the management server 14 sets the re-presented new target number of steps. The new target number of steps is also a target number of steps based on two-way communication with the patient.

[0162] The management server 14 may set a predetermined limit on the number of times the process of re-presenting the new target number of steps is repeated. For example, the management server 14 may allow the process of re-presenting the new target number of steps to be repeated up to two times. This prevents the new target number of steps from being reduced excessively.

[0163] <Modification> In the above embodiment, the application executed on the patient terminal 13 may display a warning on the touch panel display 44 when it detects that the step value acquired from the pedometer 13A exceeds the upper limit of the number of steps per day of the patient indicated in the prescription information, or falls below the lower limit. By displaying the warning, it is possible to notify the patient operating the patient terminal 13 that the allowable range indicated in the prescription information is not being observed. In addition, the application executed on the patient terminal 13 may display a warning when the step value acquired from the pedometer 13A exceeds the target number of steps set per day.

[0164] For example, an application executed on the patient terminal 13 may present a step count target that exceeds the upper limit of the patient's daily step count indicated in the prescription information. In such a case, the above-mentioned warning is displayed on the touch panel display 44 of the patient terminal 13, thereby notifying the patient that the limit of the allowable range of the target step count indicated in the prescription information has been reached.

[0165] Furthermore, the patient terminal 13 may transmit information indicating the above-mentioned warning to the management server 14 in association with the patient ID.

[0166] The patient terminal 13 may transmit information indicating the running status of the application (running status information) for each day in association with the patient ID to the management server 14. The running status information includes, for example, the number of times the application is started on the patient terminal 13 per day or the time for which the application is executed.

[0167] The pharmacist terminal 12 acquires activation status information corresponding to the patient ID from the management server 14. This allows the pharmacist operating the pharmacist terminal 12 to recognize whether the above-mentioned application for managing the patient's behavior is used every day. For example, the pharmacist terminal 12 may be set to automatically acquire activation status information from the management server 14 when executing the online consultation function. This allows the pharmacist operating the pharmacist terminal 12 to provide self-management support, specific health guidance, etc. to the patient operating the patient terminal 13 in accordance with the activation status information when the pharmacist intervenes in the online consultation.

[0168] As described above, the pharmacist terminal 12 sets an application for the patient terminal 13 based on the prescription, and the barrier, the first challenge, and the first target number of steps are set in the application of the patient terminal 13. The first target number of steps may be set after a certain trial period (e.g., two weeks) has elapsed.

[0169] For example, in step S16 of Fig. 6, an activation process of the application of the patient terminal 13 is performed. As a result, the application is set in the patient terminal 13. The patient terminal 13 in which the application is set is used by the patient for a certain trial period. During the certain trial period, the patient goes about his or her daily life. Then, the application executed on the patient terminal 13 obtains the number of steps taken in the daily life from the pedometer 13A. The information on the number of steps taken is associated with the patient ID and transmitted from the patient terminal 13 to the management server 14.

[0170] After a certain trial period has elapsed, the pharmacist terminal 12 may obtain information on the number of steps taken each day in daily life from the management server 14, and set the average of the number of steps taken each day (for example, 14 days) as a baseline number of steps that serves as a reference for the initial target number of steps. This allows the initial target number of steps to be set in accordance with the patient who uses the application executed on the patient terminal 13. As described above, the application executed on the patient terminal 13 can change the target number of steps every week based on input from the patient.

[0171] The application executed on the patient terminal 13 may display a notification message according to the set target number of steps and the actual number of steps per day on the touch panel display 44. For example, if the actual number of steps per day is below a predetermined range of steps based on the set target number of steps, a notification message encouraging walking may be displayed on the touch panel display 44. Also, if the actual number of steps per day exceeds a predetermined range of steps based on the set target number of steps, a notification message suppressing walking may be displayed on the touch panel display 44 to avoid placing an excessive burden on the patient using the patient terminal 13.

[0172] As described above, the management server 14 stores reason information indicating the reason why the patient was able to walk and reason information indicating the reason why the patient was unable to walk, corresponding to the patient ID. When the application executed on the patient terminal 13 detects that the number of days in which the step count per day reaches the target number of steps continues, the application executed on the patient terminal 13 may acquire the reason information indicating the reason why the patient was able to walk, corresponding to the patient ID, from the management server 14. The application executed on the patient terminal 13 displays the reason information indicating the reason why the patient was able to walk on the touch panel display 44. This can provide the patient using the patient terminal 13 with an opportunity to encourage him or her to walk more.

[0173] On the other hand, when the application executed on the patient terminal 13 detects that the days on which the step count per day reaches the target step count are not consecutive, the application may transmit information indicating this to the management server 14 in association with the patient ID. In this case, the management server 14 may transmit information indicating that the days on which the step count per day of the patient identified by the patient ID reaches the target step count are not consecutive to the doctor terminal 11 and the pharmacist terminal 12. This allows information that can be used as a reference when the doctor operating the doctor terminal 11 performs a medical examination and when the pharmacist operating the pharmacist terminal 12 performs an intervention.

[0174] Furthermore, the application executed on the patient terminal 13 may display a support message according to the progress of the step count goal on the touch panel display 44 at one or more predetermined times each day. For example, the application executed on the patient terminal 13 may cause a support message according to the progress of the step count goal to be displayed on the touch panel display 44 at predetermined times each day, such as 11:00, 13:00, and 16:00.

[0175] Furthermore, the prescription information of the prescription issued in step S12 in Fig. 6 may also include information regarding the medicine taken by the patient. The information regarding the medicine is managed as information in a medicine notebook or the like. The management server 14 may manage the application executed on the patient terminal 13 in association with the data in the medicine notebook. This allows the application executed on the patient terminal 13 to be linked with the data in the medicine notebook. The data in the medicine notebook is linked by the management server 14 to each of the doctor terminal 11, the pharmacist terminal 12, and the patient terminal 13, and it is possible to refer to the data in the medicine notebook from each terminal.

[0176] In the above, an example has been described in which a pharmacist or a registered dietitian provides self-management support or specific health guidance to a patient. This allows for seamless cooperation between doctors and outpatient pharmacies. On the other hand, instead of a pharmacist, a medical professional or a registered dietitian belonging to a hospital or clinic may provide self-management support or lifestyle guidance to a patient using the above-mentioned application. This allows for seamless cooperation between doctors, hospitals, clinics, and patients. In the above cases, the pharmacist terminal can be read as a medical professional terminal operated by a medical professional or a registered dietitian terminal operated by a registered dietitian. Also, the pharmacist can be read as a medical professional or a registered dietitian. Also, the related party terminal is a terminal operated by a related party related to medical care (pharmacist, medical professional, registered dietitian, etc.) and is a terminal corresponding to the above-mentioned pharmacist terminal, medical professional terminal, registered dietitian terminal, etc.

[0177] The order of the processes in the flowcharts described in the above embodiments can be changed as much as possible. Also, the embodiments of the present invention are not limited to the above-mentioned forms and can be modified as appropriate. Furthermore, the configurations of the embodiments can be replaced with substantially similar configurations, configurations that provide similar effects, or configurations that can achieve similar purposes. [Explanation of symbols]

[0178] 10 Treatment System 11 Doctor's terminal 11A Prescription issuing device 12 Pharmacist terminal 13 Patient terminal 13A Pedometer 14 Management Server

Claims

1. 1. A therapeutic system for use in treating a patient, comprising: A patient terminal of the patient; A doctor terminal used when a doctor issues a prescription for an application that manages behavioral information related to the patient's behavior; a pharmacist terminal used when a pharmacist sets the application to be executed on the patient terminal based on the prescription; A management server that periodically receives the behavioral information from the patient terminal, stores the received behavioral information, and stores first prescription information indicating information on the patient's prescription obtained from the doctor terminal; Equipped with The doctor terminal and the pharmacist terminal acquire the behavior information stored in the management server, The pharmacist terminal acquires from the management server the first prescription information corresponding to identification information for identifying a patient indicated by the second prescription information read from the paper on which the prescription information is printed, and activates the application in cooperation with the patient terminal using the acquired first prescription information. Treatment system.

2. The treatment system of claim 1 , wherein the prescription includes information indicating a behavioral tolerance range for the patient's behavior.

3. The treatment system according to claim 2 , wherein the acceptable range of behavior is a range between an upper limit and a lower limit of the patient's daily step count.

4. The treatment system according to claim 3 , wherein the application executed on the patient terminal displays a warning when it detects that the patient's behavior exceeds the upper limit or falls below the lower limit.

5. The treatment system according to claim 4 , wherein the application executed on the patient terminal transmits information indicating the warning to the management server.

6. The treatment system according to claim 1 , wherein the application is prescribed to the patient terminal by linking identification information identifying the patient, identification information identifying the doctor, and identification information identifying the pharmacy.

7. The treatment system according to claim 6 , wherein the pharmacist terminal acquires information on the prescription on which identification information for identifying the patient and identification information for identifying the doctor are written, and the linking is performed.

8. The treatment system according to claim 1 , wherein the pharmacist terminal performs an intervention regarding the patient's behavior on the application executed on the patient terminal at a predetermined timing.

9. The treatment system of claim 8 , wherein the intervention is an online interview between the patient terminal and the pharmacist terminal.

10. A screen for setting a goal for the patient's behavior is displayed on the patient terminal at an interval shorter than the interval at which the intervention is performed; The treatment system according to claim 9 , wherein information indicating the goal set on the screen is transmitted to the management server.

11. The management server stores a target number of steps set for the patient for each day, and acquires the behavior information including information on the number of steps per day from the patient terminal, The treatment system of claim 3, wherein the management server presents to the patient terminal a new target number of steps that is increased or decreased within a range between the upper limit and the lower limit depending on the number of days during a specified number of days that the daily step value is equal to or greater than the target number of steps.

12. The treatment system of claim 11, wherein the management server presents to the patient terminal a new target number of steps that is an increase from the target number of steps when the number of days during the specified number of days during which the daily step value is equal to or greater than the target number of steps is a first number or more.

13. The treatment system of claim 12, wherein the management server sets a new target number of steps to be presented when a number of steps greater than the set target number of steps has not been set in the past to be greater than a new target number of steps to be presented when a number of steps greater than the set target number of steps has been set in the past.

14. The treatment system of claim 12, wherein the management server presents to the patient terminal a new target number of steps that is a reduction of the target number of steps when the number of days during the specified number of days during which the daily step value is equal to or greater than the target number of steps is equal to or less than a second number of days that is less than the first number of days.

15. The treatment system according to claim 14, wherein the management server presents to the patient terminal as the new target number of steps the greater of the number of steps obtained by subtracting a predetermined number of steps from the set target number of steps or the maximum number of steps achieved in the past.

16. The patient terminal transmits information indicating a running status of the application to the management server, The treatment system according to claim 1 , wherein the management server transmits information indicating a running status of the application to one or both of the doctor terminal and the pharmacist terminal.

17. 1. A therapeutic system for use in treating a patient, comprising: A patient terminal of the patient; A doctor terminal used when a doctor issues a prescription for an application that manages behavioral information related to the patient's behavior; a related party terminal used when a related party in medical care sets the application to be executed on the patient terminal based on the prescription; A management server that periodically receives the behavioral information from the patient terminal, stores the received behavioral information, and stores first prescription information indicating information on the patient's prescription obtained from the doctor terminal; Equipped with The doctor terminal and the related party terminal acquire the behavior information stored in the management server, The related party terminal acquires from the management server the first prescription information corresponding to a patient ID indicated by the second prescription information read from the paper on which the prescription information is printed, and activates the application in cooperation with the patient terminal using the acquired first prescription information. Treatment system.

Images