Information processing system, information processing method, and program

Abstract

To provide a technique for preliminarily notifying a patient of the end of a use period of a prescribed treatment application.SOLUTION: An information processing system has one or more processors. The one or more processors gives, to a terminal operated by a patient, an advance notice of the end of a use period of an application which is prescribed to the patient for treatment of a disease, before the end of the use period.SELECTED DRAWING: Figure 9

Description

[Technical field]

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

[0002] Medical institutions that provide health insurance have begun prescribing application programs aimed at treating nicotine addiction and high blood pressure (hereinafter referred to as "therapeutic apps"). In addition, there are other therapeutic apps approved under the Pharmaceuticals and Medical Devices Act that aim to treat insomnia. [Prior art documents] [Patent documents]

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

[0004] Therapeutic apps approved under the Pharmaceuticals and Medical Devices Act have a set period during which the medical insurance system applies (hereinafter referred to as the "insured medical treatment period"). In other words, the insured medical treatment period corresponds to the maximum period during which the therapeutic app can be used. On the other hand, for patients who do not visit the doctor as instructed, it is possible to consider a practice in which the use of the therapeutic app is terminated before the expiration of the insured medical treatment period. This practice also applies to therapeutic apps with an expiration date that are prescribed in private medical care or mixed medical care.

[0005] One embodiment of the present disclosure provides a technique for notifying a patient in advance of the expiration of a usage period for a prescribed therapeutic app. [Means for solving the problem]

[0006] As another aspect of the present disclosure, there is provided an information processing system having one or more processors, the one or more processors notifying a terminal operated by a patient of the expiration of a usage period of an app prescribed to the patient for the purpose of treating a disease, before the expiration of the usage period.

[0007] As another aspect of the present disclosure, there is provided an information processing method in which a computer executes a process for notifying a terminal operated by a patient of the expiration of a usage period of an app prescribed to the patient for the purpose of treating a disease, before the usage period expires.

[0008] As one embodiment of the present disclosure, a program is provided for enabling a computer to realize a function of notifying a terminal operated by a patient of the expiration of a usage period of an app prescribed to the patient for the purpose of treating a disease, before the expiration of the usage period. Effect of the Invention

[0009] According to one embodiment of the present disclosure, a technique can be provided that notifies a patient in advance of the expiration of the usage period of a prescribed therapeutic app. [Brief description of the drawings]

[0010] [Figure 1] FIG. 2 is a diagram illustrating an example of the configuration of an information processing system assumed in the first embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a treatment application operation server. [Diagram 3] 11 is a diagram illustrating an example of authentication data and patient data stored in an auxiliary storage device of the medical application operation server. FIG. [Figure 4] FIG. 2 is a diagram illustrating an example of a hardware configuration of an information terminal. [Diagram 5] 13 is a processing sequence illustrating an example of a processing operation from prescribing a therapeutic application to registering patient data in a therapeutic application operation server. [Figure 6] 13 is a diagram illustrating an example of a printed matter on which a prescription code is printed. FIG. [Figure 7]FIG. 13 is a diagram illustrating an example of an operation screen of a treatment application. [Figure 8] 13 is a diagram illustrating an example of a consultation screen displayed on the display of a doctor's terminal. FIG. [Figure 9] 13 is a flowchart illustrating an example of a process used for notifying the end of a treatment application. [Figure 10] FIG. 2 is a diagram illustrating a processing sequence in the first embodiment. [Figure 11] 13 is a diagram illustrating an example of an end notice screen displayed on a patient terminal. FIG. [Figure 12] 13 is a diagram illustrating another example of the termination notice screen displayed on the patient terminal. FIG. [Figure 13] 13 is a diagram illustrating another example of the termination notice screen displayed on the patient terminal. FIG. [Figure 14] 13 is a diagram illustrating another example of the termination notice screen displayed on the patient terminal. FIG. [Figure 15] 13 is a flowchart illustrating another example of a process used for notifying the end of a treatment application. [Figure 16] FIG. 11 is a diagram illustrating a processing sequence in the second embodiment. [Figure 17] 13 is a diagram illustrating an example of an end notice screen displayed on a patient terminal. FIG. [Figure 18] 13 is a diagram illustrating an example of authentication data in which the end of the month following the month of medical examination is set as the end date of the usage period. [Figure 19] FIG. 13 is a diagram illustrating an example of authentication data in which the end date of the usage period is 40 days after the consultation date. [Figure 20] 13 is a diagram illustrating an example of authentication data for managing a planned stop date designated by a doctor or the like as the end date of a usage period. FIG. [Figure 21] 13 is a diagram illustrating an example of a management screen of a treatment application displayed on a display of a doctor terminal. FIG. [Figure 22] 13 is a diagram illustrating a processing sequence when a doctor terminal issues an instruction to stop a therapeutic application executed on a patient terminal. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. <Embodiment 1> In this embodiment, an application for assisting in the treatment of hypertension will be described as an example of a treatment application prescribed by a doctor.

[0012] <System configuration> FIG. 1 is a diagram illustrating an example of the configuration of an information processing system 1 assumed in the first embodiment. The information processing system 1 shown in Figure 1 is composed of a therapeutic application operation server 10, a doctor terminal 20 operated by a doctor who prescribes the therapeutic application, a patient terminal 30 operated by a patient receiving treatment for hypertension, and a network N connecting these terminals. It is also assumed that, to the extent permitted, the doctor terminal 20 will be operated by nurses, pharmacists, public health nurses, nutritionists, hospital staff, and other medical personnel.

[0013] The therapeutic application operation server 10 in this embodiment is a server that realizes distribution of the therapeutic application, authentication of the patient, storage of the patient data input through the therapeutic application, provision of the patient data to the medical institution (specifically, the doctor terminal 20), etc. However, the distribution of the therapeutic application may be performed by an entity different from the entity that operates the therapeutic application operation server 10.

[0014] As mentioned above, therapeutic apps are apps that have been approved under the Pharmaceuticals and Medical Devices Act, and patients who use therapeutic apps can receive insured medical treatment from a doctor during the insured medical treatment period. By using this treatment app, the patient can store blood pressure values ​​measured between the time of the next consultation with the doctor and other patient data in the treatment app operation server 10. Meanwhile, the doctor can use the patient data stored through the treatment app between the previous consultation and the current consultation to understand the patient's physical condition and decide on a treatment plan. The treatment app in this embodiment is an example of an app. In addition, insured medical treatment includes not only face-to-face medical treatment but also online medical treatment.

[0015] In this embodiment, the insured medical treatment period is set to six months. However, six months is just an example, and it may be nine months or twelve months. It may also be set in days, such as 60 days or 180 days, or it may be set in weeks, such as 8 weeks or 24 weeks. Needless to say, these values ​​are just examples. In this embodiment, the patient is permitted to use the treatment app only during the period of medical treatment covered by insurance, that is, the patient is allowed to input and record blood pressure values ​​and the like through the treatment app.

[0016] The starting date of the insured medical treatment period may be determined based on the consultation date when the treatment app was prescribed, or based on the date when the treatment app was installed on the patient terminal 30, or based on the date when use of the treatment app began, or based on the month when the treatment app was prescribed (hereinafter referred to as the "consultation month"). When the month of the medical examination is used as the starting month, the month following the month of the medical examination is considered to be month 1. This is because if the month of the medical examination is used as the 1st month, the insured medical treatment period for patients who receive medical treatment at the end of the month will be shortened by approximately one month.

[0017] Patient data includes patient attributes (gender, date of birth, height, weight), blood pressure, activity records, mood records, physical condition records, medical examination history, treatment app operation history, biological characteristics, psychological characteristics, social characteristics, habits, goal achievement status, etc. However, patient data does not need to be all of this information and may be only a part of it. The blood pressure values ​​are, for example, systolic blood pressure (i.e., the highest blood pressure value) and diastolic blood pressure (i.e., the lowest blood pressure value). The activity record is, for example, a usage history of a medical application, a medication record, a food record, a smoking record, a drinking record, and an exercise record. The activity record is an example of information about an activity.

[0018] The record of taking medicine is, for example, the type and number of medicines taken, and the time when the medicine was taken. The record of taking medicine is an example of information related to taking medicine. The food record is, for example, the contents of the food eaten and the amount of salt ingested. The food record is an example of information related to food. The smoking record is, for example, whether or not a person smoked, the date and time of smoking, and the number of cigarettes smoked. The smoking record is an example of information related to smoking. The drinking record is, for example, the date and time of drinking, the amount of alcohol consumed, and the type of alcohol. The drinking record is an example of information related to drinking.

[0019] The exercise record includes, for example, records related to sports, as well as records of daily activities such as walking, shopping, cleaning, etc. The exercise record is an example of information related to exercise. The mood record is, for example, a subjective mood. The mood record is an example of information related to mood. The record of physical condition is, for example, a subjective physical condition or symptoms. The record of physical condition is an example of information related to physical condition. The medical examination history is, for example, the treatment start date, the examination date, the details of the treatment, and advice. The medical examination history is an example of information related to medical examinations.

[0020] The operation history of the treatment application is, for example, a history of operations related to the start-up operation, the input operation of blood pressure values, and the input operation of reviewing the treatment application. Biological characteristics include, for example, the presence or absence of other diseases, the presence or absence of injuries undergoing treatment, the presence or absence of knee or foot pain, the presence or absence of experience of treatment for hypertension, the number of years since hypertension was diagnosed, the strength of seasonings used in home cooking, and the amount of food eaten. Psychological characteristics include, for example, expectations regarding app treatment, willingness to acquire knowledge about hypertension treatment, whether reducing salt intake is difficult or whether one cannot change one's sense of taste, and psychological resistance to leaving food on one's plate.

[0021] Social characteristics include, for example, wake-up time, bedtime, type of work (e.g., shift work, day shift, night shift), days of the week worked, start time of work, time home from work, regular days off, and whether or not there is heating in the changing room. Habits include, for example, exercise habits, the habit of weighing oneself, the habit of checking calorie counts on food labels, the habit of choosing low-fat foods, the habit of not consuming caffeine after 4 p.m., the habit of eating and drinking after 10 p.m., the habit of skipping breakfast, the habit of snacking, the habit of taking a bath one hour before going to bed, the habit of stretching or massaging before going to bed, and the habit of sleeping six hours or more. The goal achievement status is, for example, the relationship between the patient's status and the goal set for each patient by a doctor or the like. The above-mentioned information can be classified into subjective information and objective information.

[0022] Although only one therapeutic application operation server 10 is illustrated in FIG. 1, a plurality of therapeutic application operation servers 10 may exist on the network N. Furthermore, the services provided by one therapeutic application operation server 10 may be realized by the cooperative operation of a plurality of servers.

[0023] The doctor terminal 20 refers to a terminal operated by a doctor in an insurance medical institution, etc. A plurality of doctor terminals 20 are depicted in FIG. The patient terminal 30 refers to a terminal operated by a patient who is examined or treated for hypertension. A plurality of patient terminals 30 are illustrated in FIG.

[0024] For example, a desktop computer, a notebook computer, a tablet computer, or a smartphone is used as the doctor terminal 20 and the patient terminal 30. However, wearable computers such as smart glasses and a headset may also be used as the doctor terminal 20 and the patient terminal 30. The doctor terminal 20 and the patient terminal 30 are examples of information terminals connected to the network N.

[0025] The network N is, for example, a LAN (Local area network), the Internet, or a mobile communication system (4G, 5G). FIG. 1 illustrates an example in which the therapeutic application operation server 10, the doctor terminal 20, and the patient terminal 30 are connected to one network N, but they may be connected via a plurality of networks N that are connected to each other.

[0026] <Server hardware configuration> FIG. 2 is a diagram illustrating an example of a hardware configuration of the medical application operation server 10. As shown in FIG. 2 includes a processor 11, a ROM (=Read Only Memory) 12 in which a BIOS (=Basic Input Output System) and the like are stored, a RAM (=Random Access Memory) 13 used as a work area for the processor 11, an auxiliary storage device 14, and a communication interface 15. Each device is connected via a bus and other signal lines 16.

[0027] The processor 11 is a device that realizes various functions through the execution of programs. The processor 11, the ROM 12, and the RAM 13 function as a computer. The auxiliary storage device 14 is configured by, for example, a hard disk device or a semiconductor storage device. In addition to the therapeutic app, the auxiliary storage device 14 stores data related to authentication of patients to whom the therapeutic app is prescribed and patient data registered through the therapeutic app.

[0028] In this embodiment, the treatment application and the OS (=Operating System) are collectively referred to as a program. The communication interface 15 is an interface for communicating with other servers and terminals via the network N. The communication interface 15 supports Ethernet (registered trademark), Wi-Fi (registered trademark), mobile communication systems, and other communication standards.

[0029] <Data managed by the server> 3 is a diagram for explaining an example of the authentication data 141 and the patient data 142 stored in the auxiliary storage device 14 (see FIG. 2) of the medical application operation server 10. In the case of FIG. 3, only the information of Tokyo Taro is illustrated, but data of other patients is also recorded. The authentication data 141 shown in FIG. 3 includes, for example, a medical record number, a user ID, a patient name, a prescription date, a medical institution ID, a doctor ID, a prescription code, an insured medical treatment period (last month) of the medical treatment application, and an end date of use of the medical treatment application.

[0030] The medical record number is a number for identifying a patient who has been prescribed a medical treatment application, and is notified from the doctor's terminal 20 (see FIG. 1) of the health insurance medical institution. The user ID is an ID used for managing the medical application operation server 10 and is used for authenticating the patient. The patient name is recorded when the patient name is notified by the health insurance medical institution. In the case of Figure 3, the patient name is "Tokyo Taro." The prescription date is the date on which the patient was examined at the health insurance medical institution. In this embodiment, the examination date on which the medical treatment app was prescribed is called the "prescription date." In the case of FIG. 3, the prescription date is July 31, 2023.

[0031] The medical institution ID is an ID that identifies the health insurance medical institution that prescribed the therapeutic app. The doctor ID is an ID for identifying the doctor who prescribed the treatment app. The prescription code is a code that is notified to the patient to activate the treatment app. A prescription code is generated for each prescription. A deadline for starting use of the app (hereinafter referred to as the "usage start deadline") is set for the prescription code, and the prescription code becomes invalid after the usage start deadline. The usage start deadline for the prescription code is, for example, three days after the prescription date.

[0032] The insured medical treatment period (last month) of the treatment app is information that gives the longest period during which the treatment app can be used. In the present embodiment, the insured medical treatment period is managed on a monthly basis. Therefore, the last month of the insured medical treatment period is recorded. In the case of FIG. 3, it is January 2024. The insured medical treatment period is recorded when the treatment app is activated.

[0033] 3 includes, for example, a chart number, a user ID, a patient name, an input date and time, and a blood pressure value. As described above, the patient data 142 includes information other than the blood pressure value, but this information is omitted in FIG. 3 due to space limitations. The medical record number and user ID here are used to link with the authentication data 141. The input date and time is the date and time when the patient inputs the blood pressure value, etc., into the activated treatment application.

[0034] In the case of Figure 3, the top of the input date and time is recorded as 6:35 on August 1, 2023, the day after the prescription date. In the case of Figure 3, the systolic blood pressure value of "145" and the diastolic blood pressure value of "97" are recorded for the same day and time. In addition, the patient data 142 shown in FIG. 3 also records input values ​​on the evening of August 1, 2023 and input values ​​on the following morning.

[0035] <Hardware configuration of information terminal> 4 is a diagram illustrating an example of a hardware configuration of an information terminal. The hardware configuration shown in FIG. Therefore, in the following, the doctor terminal 20 will be described as a representative example of an information terminal. 4 includes a processor 21, a ROM 22 storing a BIOS and the like, a RAM 23 used as a work area for the processor 21, an auxiliary storage device 24, a communication interface 25, a display 26, and an input reception device 27. Each device is connected via a bus or other signal lines 28. The patient terminal 30 is also provided with a camera.

[0036] The communication interface 25 is an interface for communicating with other servers or terminals or with peripheral devices through the network N. The communication interface 25 supports Ethernet (registered trademark), Wi-Fi (registered trademark), Bluetooth (registered trademark), USB (=Universal Serial Bus), mobile communication systems, and other communication standards.

[0037] The display 26 is, for example, a liquid crystal display or an organic EL (Electro Luminescence) display. The input reception device 27 is, for example, a mouse or a keyboard. In addition, when the doctor terminal 20 is a notebook computer, a tablet computer, or a smartphone, a capacitive touch sensor having transparency that does not interfere with the visibility of the image displayed on the display 26 is used as the input reception device 27. A device that combines this type of touch sensor with a display is called a touch panel.

[0038] <Processing operations during the insured medical treatment period of the treatment app> Here, a series of processing operations that begins with the prescription of a treatment application will be described. 5 is a process sequence illustrating an example of a process from prescription of a therapeutic application to registration of patient data in the therapeutic application operation server 10. Note that the symbol S in the figure represents a step, and the symbol t represents time. The processing sequence shown in FIG. 5 consists of three stages.

[0039] The first stage is processing operations S101 to S105 (t11 to t14) related to notification of a prescription code of a medical treatment application. The second stage is processing operations S111 to S124 (t21 to t28) related to installing the therapeutic application in the patient terminal 30 and linking the therapeutic application with information identifying the patient. The third stage is processing operations S131 to S137 (t31 to t35) related to the registration of patient data in the medical application operation server 10 via the medical application.

[0040] <First stage> First, a doctor operates doctor terminal 20 to input details of a medical examination of a patient with hypertension (S101). The details of the examination are registered in the management system of the health insurance medical institution to which the doctor belongs. In this embodiment, the doctor determines that a therapeutic application needs to be prescribed for the patient. In this case, the doctor accesses a website for medical institutions published by the therapeutic application operation server 10 and requests a prescription code (S102). Incidentally, a doctor ID and a login password, for example, are used to log in to the website. At this time, the patient identification information (for example, the patient's name, date of birth, etc.) may be attached, or the medical record number used in the hospital system may be attached.

[0041] The medical application operation server 10 that has received the prescription code requests issues the prescription code (S103). In the present embodiment, a prescription code is issued for each request. The issued prescription code is associated with information (e.g., a medical record number, a user ID) that identifies the patient to whom the prescription code is to be issued, and is registered in the authentication data 141 (see FIG. 3). Thereafter, the medical application operation server 10 transmits the issued prescription code to the doctor terminal 20 which is the request source (S104). The notified prescription code is printed on a sheet of paper and handed to the patient (S105). The doctor terminal 20 may notify the patient terminal 30 by email.

[0042] Fig. 6 is a diagram illustrating an example of a printed matter 40 on which a prescription code is printed. On the printed matter 40 shown in Fig. 6, a title 41, a medical record number 42, an issue date 43, a patient's name 44, a patient's gender 45, information on the health insurance medical institution 46, a prescription code 47, a QR code (registered trademark) 48, and a note 49 are printed. The expiration date (i.e., the date by which the prescription can be used) is also printed on the prescription code 47. In the case of FIG. 6, the expiration date is 10:31 on August 3, 2023, three days after the date of issue. The QR code 48 has prescription code information embedded therein.

[0043] <Second stage> For example, the patient accesses a website provided by a doctor and requests a therapeutic application (S111 in FIG. 5). In the present embodiment, the therapeutic application is distributed by the therapeutic application operation server 10. Therefore, in S111, the therapeutic application is requested from the therapeutic application operation server 10. The therapeutic application operation server 10 that has received the request for the therapeutic application transmits the requested therapeutic application to the patient terminal 30 (S112). If the therapeutic application has already been downloaded to the patient terminal 30, the processing operations of S111 and S112 are omitted.

[0044] The patient terminal 30 that has received the therapeutic application installs the therapeutic application, starts the installed prescription application, and receives the prescription code in this order in response to the patient's operation (S113). The therapeutic application cannot be used simply by being installed, and activation by inputting the prescription code is required. The patient terminal 30 transmits the input prescription code to the medical application operation server 10 (S114). The medical application operation server 10 authenticates the patient by comparing the prescription code received from the patient terminal 30 with the prescription code in the authentication data 141 (see FIG. 3) (S115).

[0045] If these two prescription codes match, the therapeutic application operation server 10 determines that the authentication is successful. On the other hand, if these two prescription codes do not match, the therapeutic application operation server 10 determines that the authentication is unsuccessful. Even if the two prescription codes match, if the prescription code usage period (i.e., usage start period) has expired, the therapeutic application operation server 10 regards the authentication as a failure. As described above, in this embodiment, the usage period is three days after the prescription date. In either case, the therapeutic application operation server 10 transmits the result of the authentication to the patient terminal 30 (S116).

[0046] If the authentication is successful, the authentication result includes a code that allows activation of the therapeutic app. In this case, activation of the therapeutic app is executed in the patient terminal 30 (S117). As a result, the therapeutic app becomes available in the patient terminal 30. When the therapeutic app is in an activated state, the prescription code entered in S113 is recorded in association with the therapeutic app. On the other hand, if the authentication fails, the authentication result does not include a code that allows activation of the therapeutic application. In this case, an error screen is displayed on the display 36 of the patient terminal 30 (see FIG. 4).

[0047] When the therapeutic application is activated, registration of patient information in the therapeutic application operation server 10 becomes possible. Specifically, the patient terminal 30 transmits an account ID and a password used for logging in to the therapeutic application operation server 10 (S118), and the account ID and the password are registered in association with the prescription code, etc. (S119). For example, the account ID and the password are added to the authentication data 141 (see FIG. 3). When the registration of the account ID and password used for logging in is completed, the therapeutic application operation server 10 notifies the patient terminal 30 of the completion of the registration (S120).

[0048] After completing the registration of the account ID and password used for logging in, the patient inputs the patient name and other patient information into the patient terminal 30 (S121). When the input is confirmed, the input patient information is transmitted from the patient terminal 30 to the therapeutic application operation server 10 (S122). The therapeutic application operation server 10 registers the received patient information in association with the prescription code and the like (S123), and notifies the patient terminal 30 of the completion of the registration (S124). The completion of the registration is displayed on the display 36 of the patient terminal 30 (see FIG. 4).

[0049] <Third stage> Here, the process of inputting patient data using the treatment app after activation will be described. First, the patient operates the patient terminal 30 to start the therapeutic application (S131). When the therapeutic application is started, the patient terminal 30 transmits an account ID and a password used for logging in to the therapeutic application operation server 10 (S132). The therapeutic application operation server 10 executes an authentication process using the received account ID and password (S133). If the received account ID and password exist in the authentication data 141 (see FIG. 3), the therapeutic application operation server 10 determines that the authentication is successful. On the other hand, if the received account ID and password do not exist in the authentication data 141, the therapeutic application operation server 10 determines that the authentication is unsuccessful.

[0050] The result of the authentication is transmitted from the therapeutic application operation server 10 to the patient terminal 30 (S134). If the authentication is successful, it becomes possible to input data such as blood pressure values ​​into the patient terminal 30. If the authentication is unsuccessful, the patient terminal 30 displays an error on the display .

[0051] Fig. 7 is a diagram for explaining an example of an operation screen of a treatment application. In the case of Fig. 7, the patient terminal 30 is a smartphone. Moreover, the operation screen displayed on the display 36 is a screen for manual input. In the case of FIG. 7, the measurement date is August 1, 2023 (Tuesday), and the blood pressure was entered at 8 p.m. The systolic blood pressure is 135mmHg, the diastolic blood pressure is 85mmHg, and the pulse rate is 70bpm.

[0052] Returning to the explanation of Figure 5. When the patient inputs data such as blood pressure values ​​(S135), the patient terminal 30 transmits the input patient data to the medical application operation server 10 (S136). The medical application operation server 10 registers the received data as the patient data 142 (see FIG. 3) (S137). The input of data such as blood pressure values ​​may be done manually by the patient, or may be done automatically by inputting blood pressure values ​​measured by a peripheral device connected via Bluetooth, etc. The peripheral device here is a blood pressure monitor.

[0053] The patient data 142 registered in the therapeutic application operation server 10 can be downloaded and viewed from a doctor terminal 20 (see FIG. 1) operated by the doctor who prescribed the therapeutic application. For example, patient data that matches the chart number and other information entered by the doctor is sent to the doctor terminal 20. As a result, the doctor can use information such as blood pressure values ​​at home for examinations.

[0054] FIG. 8 is a diagram for explaining an example of a medical examination screen displayed on the display 26 of the doctor terminal 20. As shown in FIG. The examination screen shown in FIG. 8 is displayed based on the patient data 142 of Tokyo Taro read from the medical application operation server 10 (see FIG. 3). The patient data field on the examination screen shown in FIG. 8 is made up of a display field 261 for displaying changes in average blood pressure, a display field 262 for review information, a display field 263 for displaying activity records, and an end button 264.

[0055] In the case of FIG. 8, the date displayed on the consultation screen is January 21, 2024. Therefore, display field 261 displays the average blood pressure, average pulse rate, and blood pressure measurement rate calculated from patient data from 8 weeks to 4 weeks before the displayed date (from December 3rd to December 23rd, 2023), and the average blood pressure, average pulse rate, and blood pressure measurement rate calculated from patient data from 4 weeks before the displayed date to the day before (from December 24th, 2023 to January 20th, 2024).

[0056] A record of mood and physical condition is displayed in a display field 262 shown in Fig. 8. A record of mood and physical condition is also called a diary. 8, the number of days the treatment app was used, the number of days a salt reduction in meals was recorded, the number of days a weight loss was recorded, etc. are displayed as activity records. Of course, these are just examples. When the end button 264 is operated, the examination screen is closed.

[0057] <Notice of expiration of usage period> 9 is a flowchart for explaining an example of a process used for notifying the end of a therapeutic application The process shown in FIG. First, the processor 11 determines whether or not access from the treatment application of the patient terminal 30 has been detected (S201). If no access from the patient terminal 30 is detected, a negative result is obtained in S201. In this case, the processor 11 repeats the determination in S201 until a positive result is obtained in S201.

[0058] When an access from the patient terminal 30 is detected, a positive result is obtained in S201. In this case, the processor 11 acquires the end date of the usage period of the treatment app that is the access source (S202). In the case of this embodiment, the end date of the usage period is the last day of the insured medical treatment period, and is acquired from the authentication data 141. For example, when a user ID associated with the medical treatment app can be obtained from the patient terminal 30, the processor 11 obtains the insured medical treatment period of the medical treatment app by identifying the accessing patient. Also, when a prescription code of the accessing medical treatment app can be obtained, the processor 11 obtains the insured medical treatment period through the prescription code.

[0059] Next, the processor 11 determines whether the current time is within the usage period (S203). If the current time has passed the usage period, a negative result is obtained in S203. In this case, the processor 11 instructs the patient terminal 30, which is the access source, to stop the execution of the treatment app (S204). In other words, the processor 11 instructs the invalidation of the treatment app. After this instruction, the processor 11 ends a series of processes. Note that the treatment app whose execution has been stopped cannot be started.

[0060] On the other hand, if the current time is within the usage period, a positive result is obtained in S203. In this case, the processor 11 calculates the number of remaining days until the end date (S205). Next, the processor 11 determines whether the remaining number of days is equal to or less than a threshold (S206). In the case of this embodiment, the threshold here is, for example, 3 days. Of course, 3 days is just an example, and it may be 7 days or 2 days.

[0061] If the remaining number of days is equal to or less than the threshold, a positive result is obtained in S206. In this case, the processor 11 notifies the patient terminal 30 of the expiration of the usage period of the treatment application (S207). The expiration notice here is notified as an authentication result. After execution of S207, or if a negative result is obtained in S206 (i.e., if the remaining days are greater than the threshold value), the processor 11 registers the patient data received from the patient terminal 30 (S208). After that, the processor 11 ends the series of processes.

[0062] <Processing sequence> FIG. 10 is a diagram illustrating a processing sequence according to the first embodiment. The processing sequence shown in FIG. 10 consists of two stages. The first stage is the processing operations S301 to S309 immediately before the expiration of the usage period of the treatment application. The second stage is the processing operations S311 to S316 that are performed after the usage period of the treatment application has ended.

[0063] <First stage> First, the patient operates the patient terminal 30 to start up the treatment application (S301). When the therapeutic application is started, the patient terminal 30 transmits an account ID and a password used for logging in to the therapeutic application operation server 10 (S302). Upon receiving the account ID and password, the therapeutic application operation server 10 executes authentication processing using the received account ID and password (S303). If the received account ID and password exist in the authentication data 141 (see FIG. 3) (i.e., if the authentication is successful), the therapeutic application operation server 10 determines the end date of the usage period of the therapeutic application that is the sender of the account ID, etc. (S304).

[0064] Specifically, the determination processes of S203 (see FIG. 9) and S206 (see FIG. 9) described above are executed. Thereafter, the therapeutic application operation server 10 transmits the result of the authentication and the like to the patient terminal 30 (S305). For example, if the authentication is successful and there is still time until the end of the usage period (i.e., the number of remaining days of the usage period exceeds a threshold), a message indicating that the authentication is successful is transmitted to the patient terminal 30. In this case, a notice of the end of the usage period is not included.

[0065] For example, if the authentication is successful and the expiration date of the usage period is approaching (i.e., the number of remaining days of the usage period is equal to or less than a threshold), a message indicating that the authentication was successful and a notice of the expiration of the usage period are transmitted to the patient terminal 30. If the account ID and password do not exist in the authentication data 141 (see FIG. 3) (that is, if the authentication fails), the therapeutic application operation server 10 transmits a message to the patient terminal indicating that the authentication has failed.

[0066] If the received result includes an end notice, the patient terminal 30 displays the end notice on the display 36 (see FIG. 4) (S306). If the received result indicates that the authentication has been successful, input of data such as blood pressure values ​​becomes possible (S307). After that, the input patient data is transmitted from the patient terminal 30 to the therapeutic application operation server 10 (S308). The medical application operation server 10 registers the received data as the patient data 142 (see FIG. 3) (S309).

[0067] <Second stage> The second stage envisages the first launch of the treatment app after the end date of the treatment app's usage period has passed. In this case as well, the patient operates the patient terminal 30 to start up the treatment application (S311). When the therapeutic application is started, the patient terminal 30 transmits an account ID and a password used for logging in to the therapeutic application operation server 10 (S312).

[0068] The therapeutic application operation server 10 receives the account ID and password and performs authentication processing using the received account ID and password (S313). If the authentication is successful, the therapeutic application operation server 10 further determines the end date of the usage period of the therapeutic application (S314). Since the expiration date of the therapeutic application's usage period has already passed this time, the therapeutic application operation server 10 notifies the patient terminal 30 of the expiration of the therapeutic application's usage period (step 315). The patient terminal 30 that has received this notification disables the treatment application (S316). By disabling the treatment application, the treatment application cannot be started.

[0069] <Example of notification screen> An example of a screen used for notifying the end of a program will be described below. <Example 1> Fig. 11 is a diagram for explaining an example of a termination notice screen 360 displayed on the patient terminal 30 (see Fig. 1). In Fig. 11, parts corresponding to those in Fig. 7 are denoted by the same reference numerals. An expiration notice screen 360 shown in FIG. 11 is made up of a usage period expiration notice field 361, a “Close” button 362, and a “What is the usage period?” button 363.

[0070] 11, the expiration notice field 361 states, "The usage period of the treatment app will end soon." This expiration notice screen 360 is displayed any number of times each time the treatment app is started, as long as the usage period has not ended. By adopting a mechanism to notify patients in advance that the treatment app will soon become unavailable, it is possible to reduce the risk of patients being surprised that the treatment app will not start after the usage period has expired, or mistaking it for a malfunction. It can also reduce the number of inquiries to medical institutions regarding treatment apps that will not start.

[0071] In addition, the termination notice field 361 may display a message such as "The treatment application will soon become unavailable due to the expiration of the usage period." When the "Close" button 362 is operated, the end notice screen 360 is closed and the input screen for blood pressure values ​​and the like, exemplified in FIG. 7, is displayed. When the "What is the usage period?" button 363 is operated, a screen explaining the usage period is displayed. In the case of this embodiment, an explanation of the insured medical treatment period is displayed.

[0072] <Example 2> In the case of the display example shown in FIG. 11, the patient can know in advance that the therapeutic application will no longer be usable, but cannot know specifically how many days remain until the therapeutic application's usage period ends. In Example 2, a case where the remaining number of days of the usage period is notified will be described. Fig. 12 is a diagram for explaining another example of the termination notice screen 360 displayed on the patient terminal 30 (see Fig. 1). In Fig. 12, parts corresponding to those in Fig. 11 are denoted by the same reference numerals.

[0073] In the expiration notice screen 360 shown in FIG. 12, an expiration notice field 361 states "The usage period of the treatment app will end in 3 days," and displays the number of remaining days. 12, the patient can know not only that the therapeutic app will soon become unusable, but also the number of days remaining until the end of the therapeutic app's usage period. As a result, it is possible to improve the predictability of the date on which the therapeutic app will become unusable.

[0074] <Example 3> In Example 3, an example of notifying the end date of the usage period will be described. Fig. 13 is a diagram for explaining another example of the termination notice screen 360 displayed on the patient terminal 30 (see Fig. 1). In Fig. 13, parts corresponding to those in Fig. 11 are denoted by the same reference numerals.

[0075] 13, the end notice screen 360 indicates "The usage period of the treatment app will end on January 31" in the end notice field 361, and the end date is specifically specified. Note that the end notice field 361 may also indicate "The usage period of the treatment app will end today" or "The usage period of the treatment app will end next Friday." In either case, the expression is not a date display, but allows the date to be specified. 13, the patient can know not only that the therapeutic app will soon become unusable, but also the specific end date of the therapeutic app's usage period. As a result, the predictability of the date on which the therapeutic app will become unusable can be improved.

[0076] <Example 4> Example 4 describes an example of notifying the end of a usage period. Fig. 14 is a diagram for explaining another example of the termination notice screen 360 displayed on the patient terminal 30 (see Fig. 1). In Fig. 14, parts corresponding to those in Fig. 11 are denoted by the same reference numerals.

[0077] In the termination notice screen 360 shown in FIG. 14, a termination notice field 361 states, "The usage period of the treatment application has ended." The first message literally notifies the patient that the usage period has ended, which is effective in helping the patient understand the current situation. The second message notifies the patient of the behavior of the treatment app when the treatment period ends, and is used as a notice that the treatment app will no longer be able to be launched after this message is displayed.

[0078] Furthermore, even if the therapeutic app is forcibly terminated after this termination notice screen 360 is displayed, the notice is displayed immediately before the termination, which reduces the patient's confusion compared to when a patient who is unaware that the usage period has ended attempts to launch the therapeutic app. In addition, by clearly indicating the reason why the treatment app cannot be used, it is expected that the patient's suspicion regarding a malfunction of the treatment app or the patient terminal 30 will be reduced.

[0079] <Summary> According to the information processing system 1 (see FIG. 1) of this embodiment, before the usage period of the prescribed therapeutic app expires, the patient who operates the patient terminal 30 can be notified of the expiration of the usage period. This can improve the patient's predictability regarding events such as the therapeutic app not starting up.

[0080] In this embodiment, when the patient terminal 30 accesses the therapeutic application operation server 10, if the number of remaining days until the end date of the usage period is less than a threshold, the end of the usage period is notified in advance. That is, by notifying the end of the usage period in association with the patient's use of the therapeutic application, the patient's predictability regarding the end of the usage period can be improved. In addition, when the expiration of the usage period is announced, the number of days remaining until the expiration of the usage period and the expiration date are specifically indicated, so that the patient who uses the therapeutic app can know in advance the date on which the usage period of the therapeutic app will expire. As a result, it is possible to improve the predictability of the date on which the therapeutic app will no longer be available.

[0081] In addition, if a therapeutic app that has not been disabled is launched after the expiration of the usage period of the therapeutic app, the therapeutic app is disabled after notifying the patient terminal 30 that the usage period has expired, thereby making it possible to increase the predictability of the therapeutic app becoming unusable.

[0082] <Embodiment 2> This embodiment is also premised on the system configuration and processing operations of the information processing system 1 (see FIG. 1) described in the first embodiment. The therapeutic application operation server 10 in the second embodiment differs from the information processing system 1 in the first embodiment in that it has a function of notifying the patient terminal 30 of the expiration of the usage period regardless of access from the patient terminal 30. The function described in this embodiment may be added to the advance notice function of the treatment application operation server 10 described in the first embodiment.

[0083] Fig. 15 is a flowchart for explaining another example of processing used for notifying the end of a therapeutic application. In Fig. 15, parts corresponding to those in Fig. 9 are assigned with the same reference numerals. The processing shown in Fig. 15 is also executed by the processor 11 (see Fig. 2) of the therapeutic application operation server 10. First, the processor 11 acquires data of one of the patients currently being treated from the authentication data 141 (see FIG. 3) (S401).

[0084] Next, the processor 11 acquires the end date of the usage period of the therapeutic app used by the patient (S402). If the patient uses a plurality of therapeutic apps, the end date of the usage period is acquired for each therapeutic app. In the present embodiment, the end date of the usage period is also assumed to be the last day of the insured medical treatment period. Next, the processor 11 determines whether the current time is within the usage period (S403).

[0085] If the current time has passed the usage period, a negative result is obtained in S203. In this case, the processor 11 instructs the patient terminal 30 associated with the patient (e.g., user ID) to stop executing the treatment app (S404). The instruction here is realized as a so-called push notification. The patient terminal 30 that has received the push notification displays, for example, a termination notice screen 360 as illustrated in Fig. 14 on the display 36, and then changes the status of the treatment app to disabled. The notification of the contents of the termination notice screen 360 may be by email or a short message.

[0086] On the other hand, if the current time is within the usage period, a positive result is obtained in S403. In this case, the processor 11 calculates the remaining number of days of the usage period of the treatment app (S405). The remaining number of days here is also calculated for each treatment app linked to the patient. Next, the processor 11 determines whether the calculated remaining number of days is equal to or less than a threshold value (S406). In the present embodiment, the threshold value here is also set to, for example, three days.

[0087] If the remaining number of days is equal to or less than the threshold, a positive result is obtained in S406. In this case, the processor 11 notifies the patient terminal 30 associated with the patient of the advance notice of the end of the usage period of the therapeutic app (S407). This notification is also realized as a push notification. Note that the notification may be by email or a short message. The patient terminal 30 that has received the push notification displays on the display 36, for example, the termination notice screen 360 exemplified in FIG. After execution of S404 or S407, or if a negative result is obtained in S406 (if the remaining number of days is greater than the threshold value), the processor 11 determines whether or not processing of all patients currently being treated has been completed (S408).

[0088] If there are patients left for which processing has not been completed, a negative result is obtained in S408. In this case, the processor 11 returns to S401 and obtains data of one of the patients for which processing has not been completed. On the other hand, if the processing has been completed for all patients, a positive result is obtained in S408, in which case the processor 11 ends the series of processing.

[0089] FIG. 16 is a diagram illustrating a processing sequence according to the second embodiment. 16 is initiated from the therapeutic application operation server 10. That is, unlike the first embodiment, the patient terminal 30 is not the starting point. For example, when a predetermined time arrives, the therapeutic application operation server 10 judges whether or not a termination notice is given for a therapeutic application prescribed for a patient under treatment (ie, whether or not a condition for termination notice is satisfied) (S501).

[0090] The predetermined times are, for example, 9 am, 12 noon, and 3 pm The determination in S501 may be performed every predetermined period (for example, 12 hours, 24 hours). As described above, the medical application operation server 10 pushes the termination notice to the patient terminals 30 of the patients who satisfy the notice conditions (S502). The patient terminal 30 that has received the push notification from the medical application operation server 10 displays a termination notice on the display 36 (see FIG. 4) (S503).

[0091] <Example of notification screen> Fig. 17 is a diagram for explaining an example of a termination notice screen 370 displayed on the patient terminal 30 (see Fig. 1). In Fig. 17, parts corresponding to those in Fig. 7 are denoted by the same reference numerals. 17, the termination notice screen 370 displays messages such as "The usage period of the treatment app will end on September 30th," and "Please see a doctor at a hospital." This termination notice screen 370 is displayed every time a push notification is received.

[0092] Incidentally, the first text is the same as the expiration notice screen 360 shown in Fig. 13 in that it specifically notifies the end date of the usage period of the therapeutic app. Note that the first text may contain content notifying only the end of the usage period of the therapeutic app or content notifying the number of days remaining until the usage period of the therapeutic app ends. The second message encourages patients who use the therapeutic app to visit a doctor. If the patient follows the notification and visits a doctor, the patient can, for example, receive a prescription for a new therapeutic app.

[0093] <Summary> For example, for a patient who inputs blood pressure values ​​and the like into a treatment app every day, by adopting the mechanism described in embodiment 1, it is possible to notify the patient that the end of the usage period for the treatment app is approaching before the usage period for the treatment app ends. However, in the case of patients who use therapeutic apps infrequently or who have stopped using therapeutic apps, notification using the mechanism described in embodiment 1 may not be able to warn of the end of the therapeutic app's usage period before the end of the therapeutic app's usage period.

[0094] On the other hand, in the case of the mechanism described for the information processing system 1 (see FIG. 1) according to the present embodiment, even in the case of a patient who uses a therapeutic app infrequently or a patient who has stopped using the therapeutic app, it is possible to notify the patient in advance that the expiration of the therapeutic app's usage period is approaching. As a result, it is possible to improve the patient's predictability regarding the expiration of the therapeutic app's usage period.

[0095] <Embodiment 3> In the above embodiment, the end date of the usage period of the therapeutic app was the last day of the insured medical treatment period, but in this embodiment, a case will be described in which an end date determined based on the operation rule is added as the end date of the usage period of the therapeutic app. Note that the operation rule to be applied may be registered, selected, switched, etc. by a doctor, etc. The end date determined based on the operational rules is also an example of the end date of the usage period of the therapeutic app.

[0096] In the following, as examples of the end date determined based on the operational rules, a case where the end date is the end of the month following the month of the medical examination and a case where the end date is the 40th day after the medical examination are described. The 40 days includes a buffer period of 10 days, assuming that patients receiving treatment using a treatment app are required to see a doctor once every 30 days. Therefore, for a treatment app that requires consultation once every two months, 70 days (60 days + 10 days) may be used as the threshold. However, the buffer period is merely an example, and may be 5 days or 14 days. The buffer period may be a specification that is given as an initial setting for each treatment app, or may be a specification that can be freely specified by the doctor.

[0097] In either case, the end date based on the operation rules is determined mechanically based on the rules. Note that the end date based on the operation rules cannot be set after the end of the insured medical treatment period. As mentioned above, the insured medical treatment period is set to provide the maximum period during which the medical treatment app can be used.

[0098] <Example 1> Fig. 18 is a diagram for explaining an example of authentication data 141 that manages the end of the usage period as the end date of the month following the month of medical examination. In Fig. 18, parts corresponding to those in Fig. 3 are denoted by the same reference numerals. The authentication data 141 shown in FIG. 18 differs from the authentication data 141 shown in FIG. 3 in that a column for "expiration month of treatment application" is added. In the case of Figure 18, only Tokyo Taro's information is shown as an example, but data on other patients is also recorded.

[0099] In the case of FIG. 18, the consultation date (i.e., the prescription date) on which the therapeutic app was prescribed to Tokyo Taro is July 31, 2023. Therefore, the expiration month of the therapeutic app is managed as August 2023, which is the month following the consultation month. In this case, the last day of the usage period of the therapeutic app will be August 31, 2023. Therefore, if the threshold value of S206 (see FIG. 9) is three days, the advance notice in the above-described first and second embodiments will be notified to the patient terminal 30 on or after August 29, 2023.

[0100] Incidentally, Tokyo Taro received his second medical examination on August 29, 2023. Therefore, the last day of the period for using the treatment app has been updated to September 2023, the month following the month of the examination. In this case, the last day of the period for using the treatment app will be September 30, 2023. Therefore, the advance notice in the above-mentioned first and second embodiments will be notified to the patient terminal 30 after September 28, 2023.

[0101] <Example 2> Fig. 19 is a diagram for explaining an example of authentication data 141 in which the end date of the usage period is set to 40 days after the consultation date. In Fig. 19, the parts corresponding to those in Fig. 3 are denoted by the same reference numerals. The authentication data 141 shown in FIG. 19 differs from the authentication data 141 shown in FIG. 3 in that a column for "end date of use period of treatment application" is added. In the case of Figure 19, only Tokyo Taro's information is shown as an example, but data for other patients is also recorded.

[0102] In the case of FIG. 19, the consultation date (i.e., the prescription date) on which the therapeutic app was prescribed to Tokyo Taro is July 31, 2023. Therefore, the end date of the usage period of the therapeutic app is managed as September 9, 2023. Therefore, if the threshold value in S206 (see FIG. 9) is three days, the advance notice in the above-described first and second embodiments will be notified to the patient terminal 30 on or after September 7, 2023.

[0103] Incidentally, Tokyo Taro received his second medical examination on August 29, 2023. For this reason, the final date of the treatment app's usage period has been updated to October 8, 2023. Therefore, the advance notice in the above-mentioned first and second embodiments will be notified to the patient terminal 30 after October 6, 2023.

[0104] <Summary> As described above, in the information processing system 1 (see FIG. 1) according to this embodiment, the end date of the usage period of the treatment app is managed by an end date that is mechanically determined based on the operation rules in addition to the end date of the insured medical treatment period. Note that the operation rules to be applied may be registered, selected, switched, etc. by a doctor, etc. In the present embodiment, it is possible to manage the usage period of the treatment app in units of a period shorter than the insured medical treatment period. As a result, at least two end dates can be set within at least the insured medical treatment period, and an end notice for each end date can be notified to the patient terminal 30.

[0105] <Fourth embodiment> In the above embodiment, the case where the end date of the therapeutic app usage period is mechanically determined based on the prescription date, the consultation date, etc. is described, but in the present embodiment, the case where the doctor, etc. can specify the end date of the therapeutic app usage period (i.e., the planned termination date) is described. In other words, the case where the doctor, etc. can specify whether or not the therapeutic app is to be executed on the patient terminal 30 is described.

[0106] <Example of authentication data> Fig. 20 is a diagram for explaining an example of authentication data 141 that manages a planned stop date designated by a doctor or the like as the end date of a usage period. In Fig. 20, the parts corresponding to those in Fig. 3 are denoted by the same reference numerals. The authentication data 141 shown in FIG. 20 differs from the authentication data 141 shown in FIG. 3 in that a column for "Planned date of stopping treatment application" is added. In the "planned termination date of the treatment application" field, the end date of the usage period designated by the doctor or the like (i.e., the planned termination date) is recorded.

[0107] In the case of Figure 20, only Tokyo Taro's information is shown as an example, but data for other patients is also recorded. In the case of Figure 20, the consultation date (i.e., the prescription date) when the treatment app was prescribed to Tokyo Taro is July 31, 2023. For this reason, the final month of the insured medical treatment period is managed as January 2024. In the case of Figure 20, Tokyo Taro will have his second medical examination on August 29, 2023.

[0108] In the authentication data 141 shown in Fig. 20, a doctor or the like who noticed that the third consultation had not been performed set the planned date for stopping the treatment app. Therefore, October 20, 2023 is recorded in the "Planned date for stopping treatment app" column in the row for the second consultation date. Therefore, if the threshold value of S206 (see FIG. 9) is three days, the advance notice in the above-described first and second embodiments will be notified to the patient terminal 30 on or after October 18, 2023.

[0109] <Example of management screen> 21 is a diagram for explaining an example of a management screen of the treatment app displayed on the display 26 of the doctor terminal 20. The management screen here is used to specify the end date of the usage period of the treatment app described above. The management screen of the therapeutic application shown in Fig. 21 is generated based on authentication data 141 (see Fig. 20) related to a patient who is treated by a doctor who operates the doctor terminal 20. To extract the corresponding authentication data 141, for example, a doctor ID or a medical institution ID inputted at the time of logging in to the therapeutic application operation server 10 is used.

[0110] The management screen of the therapeutic application shown in FIG. 21 is an example of an operation screen used to switch whether or not the therapeutic application is executed on the patient terminal 30. The management screen of the therapeutic app may be configured only with information on patients for whom the doctor or the like operating the doctor terminal 20 has prescribed a therapeutic app, or may be configured only with information on patients for whom the medical institution to which the doctor or the like operating the doctor terminal 20 belongs has prescribed a therapeutic app. In other words, the management screen of the therapeutic app may include information on patients for whom another doctor or the like belonging to the same medical institution has prescribed a therapeutic app.

[0111] In addition, the management screen of the therapeutic app may include information on a patient being treated by a doctor or the like other than the medical institution or doctor who prescribed the therapeutic app. This display is necessary, for example, when a second opinion is sought from another doctor or the like. This display can be realized, for example, by the doctor or the like operating the doctor terminal 20 providing information identifying the patient being treated (for example, a medical record number or a patient name) to the therapeutic app operation server 10.

[0112] Also, technically, it is possible to include information on all patients managed by the medical application operation server 10 on the management screen of the medical application. In that case, however, it is desirable to enable narrowing down or sorting of patients displayed on the management screen by the ID of the doctor operating the doctor terminal 20, etc.

[0113] The management screen shown in FIG. 21 is composed of an information column 265, a current date and time 266, a “details” button 267, and a “close” button 268. The information field 265 displays management information of therapeutic applications prescribed to each patient. In the case of Fig. 9, the information field 265 is displayed in a table format. Incidentally, information for each patient is displayed in the rows, and management items of the therapeutic applications are displayed in the columns. In FIG. 21, examples of management items include chart number / patient name 265A, application name 265B, status 265C, planned stop date 265D, prescription date 265E, and application usage start date 265F.

[0114] The medical record number / patient name 265A is used to display the medical record number and the patient name, which are examples of information for identifying a patient to whom the application is prescribed. The information for identifying a patient may include a user ID, an address, and the like. The application name 265B is used to display the name of the application prescribed to the patient. In this embodiment, the therapeutic application is assumed to be an application that assists in the treatment of hypertension, but the number of therapeutic applications prescribed by a doctor or the like is not limited to one.

[0115] For example, if multiple therapeutic apps are approved for treating hypertension (including different versions), it is necessary to confirm the differences in the prescribed apps by their names. In addition to therapeutic apps for hypertension, there are also therapeutic apps for nicotine addiction and insomnia disorders, and these must be recognized by their names. In Figure 21, the differences in app names are distinguished between "therapeutic app 1" and "therapeutic app 2." In addition to the application name 265B, the name and type of the disease that the treatment application is intended to treat may be displayed.

[0116] The status 265C is used to display the usage status of the treatment application. In the present embodiment, four statuses are used: not yet started, in use, scheduled to be stopped, and completed. "Before use has started" is an example of information indicating a state before use of the therapeutic app has started. In addition, a state in which the therapeutic app has been prescribed but not yet installed may be displayed as "Prescribed," and a state in which the therapeutic app has been installed but not yet activated or in which registration of patient information has not yet been completed may be displayed as "Installed," allowing the user to grasp the current state of the therapeutic app in detail. "In use" is an example of information indicating that a therapeutic application is being used. In this embodiment, "in use" is displayed when the registration of patient information in the therapeutic application operation server 10 is completed or when patient data is being registered from the patient terminal 30.

[0117] "Planned stop" is an example of information indicating the presence of a reservation for the date on which the use of the treatment app is to be stopped. Here, "scheduled to end" is used when a doctor or other person specifies a date to end the usage period, but the specified end date has not yet arrived. The end date of the usage period is specified by a doctor or other medical professional, which differs from the end date of an insured medical treatment period, which is mechanically determined, or an end date based on operational rules (for example, the end of the month following the consultation or the 40th day after the consultation). In the case of this embodiment, the reservation for the date on which the use is to be stopped can be made by a doctor who prescribes the therapeutic application or a doctor who is treating a patient who is using the therapeutic application.

[0118] The scheduled stop date can be changed by the doctor, etc. Also, the doctor, etc. can cancel the scheduled stop date. An operation for reserving a date for stopping use of the therapeutic app or an operation for canceling the reservation are examples of operations for switching whether or not the therapeutic app can be executed on the patient terminal 30. In the present embodiment, the reservation of the date on which the use of the treatment app is to be stopped is used to mean the same as the reservation of the date on which the treatment app is to be disabled.

[0119] "End" is an example of information indicating the end of the usage period of the therapeutic app. Here, "end" includes a state where the end date of the insured medical treatment period that provides the maximum usage period of the therapeutic app has passed, a state where the scheduled end date of usage has passed, and a state where a doctor or the like has instructed immediate suspension of usage. When the "end" is reached, the execution of the treatment application on the patient terminal 30 is stopped.

[0120] In this embodiment, it is possible to switch whether or not to execute the therapeutic app prescribed for the patient by tapping or clicking with the pointer on the status 265C. For example, by tapping or clicking with the pointer on the display field of the status 265C, it is possible to switch from "In use" to "Scheduled to stop" or "Ended."

[0121] When the state of status 265C is changed to "scheduled to stop", input of the stop date is prompted. For example, the frame or cell corresponding to the scheduled stop date 265D flashes. Also, for example, a screen for inputting the stop date pops up. For the stop date, it is possible to input a date from the day after the operation date to the day before the last day of the insured medical treatment period. When the state of status 265C is switched to "Ended", the use of the treatment app by the corresponding patient is immediately stopped.

[0122] Conversely, the state of the status 265C can be switched from “scheduled to stop” or “ended” to “in use.” These switching operations are also examples of operations by medical personnel to switch whether or not a treatment app can be executed. For example, if a medical examination cannot be received within the specified period due to reasons attributable to the medical institution (e.g., closure due to equipment problems) or due to reasons attributable to the patient (e.g., oversight, restrictions on going out), it may be possible to change "scheduled to be suspended" or "ended" to "in use" even after the suspension date specified by the doctor or the mechanically determined end date. However, changing the status from "terminated" to "in use" due to the passage of the insured medical treatment period is prohibited.

[0123] Planned stop date 265D is used to display the date (i.e., the stop date) that is set when status 265C is "Planned stop". In the case of this embodiment, a doctor or the like can directly input a date into the corresponding box or cell that corresponds to planned stop date 265D. It is also possible to change the displayed date to another date. The prescription date 265E is used to display the date on which the medical treatment application was prescribed by a doctor or the like. The application usage start deadline 265F is used to display the last date on which the prescription code issued when prescribing the treatment application is valid. In the present embodiment, the application usage start deadline 265F displays a date that is three days after the prescription date 265E.

[0124] The current date and time 266 is the date and time when the management screen of the medical application shown in FIG. 21 is viewed. The "details" button 267 is a button used to display an information screen for each patient. The "details" button 267 is arranged on each line corresponding to a patient. The "close" button 268 is a button for closing the management screen of the treatment application shown in FIG.

[0125] <Processing sequence> Here, a series of processing operations that begins with the prescription of a treatment application will be described. FIG. 22 is a diagram for explaining a processing sequence in the case where the doctor terminal 20 instructs the patient terminal 30 to stop the treatment application being executed. The processing sequence shown in FIG. 22 consists of three stages.

[0126] The first stage is processing operations S601 to S603 related to registration of the stop date or planned stop date of the treatment app by the doctor. The second stage is processing operations S611 to S618 related to the registration of patient data in the medical application operation server 10 via the medical application. The third stage is the therapeutic application operation server 10 performing the therapeutic application stop process (S621 to S626).

[0127] <First stage> First, the doctor operates the doctor terminal 20 to transmit the stop date or planned stop date of the therapeutic app for a specific patient to the therapeutic app operation server 10 through the operation of the therapeutic app management screen (see FIG. 21) etc. (S601). The "stop date" here is the date when the execution of the therapeutic app is stopped on the same day as the operation date, and the "planned stop date" is the date when the execution of the therapeutic app is stopped on or after the day after the operation date. The medical application operation server 10 registers the stop date or the planned stop date received from the doctor terminal 20 (S602), and notifies the doctor terminal 20 of the completion of the registration (S603). The completion of the notification is displayed on the display 26 of the doctor terminal 20 (see FIG. 4).

[0128] <Second stage> Here, the process of inputting patient data using the treatment app after activation will be described. First, the patient operates the patient terminal 30 to start the therapeutic application (S611). When the therapeutic application is started, the patient terminal 30 transmits an account ID and password used for logging in to the therapeutic application operation server 10 (S612). The therapeutic application operation server 10 executes authentication processing using the received account ID and password (S613). Next, the therapeutic application operation server 10 checks the scheduled stop date and the like of the therapeutic application that is the access source (S614).

[0129] After that, the therapeutic application operation server 10 transmits the authentication result to the patient terminal 30 (S615). If the patient terminal 30 logs in within three days of the scheduled termination date managed in the authentication data 141, the authentication result includes a termination notice. When the patient inputs data such as blood pressure values ​​(S616), the patient terminal 30 transmits the input patient data to the medical application operation server 10 (S617). The medical application operation server 10 registers the received data as the patient data 142 (see FIG. 3) (S618).

[0130] <Third stage> The third stage begins with the launch of the therapeutic application in the patient terminal 30 (S621). When the therapeutic application is launched, the patient terminal 30 transmits an account ID and a password used for logging in to the therapeutic application operation server 10 (S622). The therapeutic application operation server 10 executes an authentication process using the received account ID and password (S623). The therapeutic application operation server 10 also checks the planned stop date and the like of the therapeutic application that is the access source (S624).

[0131] However, in this stage, it is assumed that the timing of login from the patient terminal 30 is after the scheduled stop date managed in the authentication data 141. Therefore, the therapeutic application operation server 10 notifies the patient terminal 30 of the suspension of the execution of the therapeutic application (S625). The patient terminal 30 stops the execution of the therapeutic application in accordance with the received notification (S626), that is, disables the therapeutic application in question.

[0132] The patient is notified of the stop of the execution of the therapeutic application through a display such as a dialogue on the display 36 of the patient terminal 30 (see FIG. 4). Even if a plurality of therapeutic applications are installed in the patient terminal 30, the execution of only the therapeutic application started in S621 is stopped.

[0133] <Summary> As described above, in the information processing system 1 (see FIG. 1) according to this embodiment, the end date of the usage period of the treatment app is managed by the end date of the insured medical treatment period as well as the scheduled stop date (i.e., the end date of the usage period) specified by a doctor, etc. Therefore, in this embodiment, a notice of the end of the usage period can be notified to the patient terminal 30 before the scheduled stop date specified by a doctor, etc. arrives.

[0134] The notice of the end of the usage period may be sent to the patient terminal 30 by push notification at the timing when the doctor or the like specifies the planned stop date, etc. (i.e., at the timing when the change to the usage period is accepted), as in the third embodiment. That is, the patient can be notified of the end of the usage period at the timing when the change to the usage period is accepted from the doctor or the like. In this case, there will be more opportunities for push notifications of termination notices to be sent earlier than the usual notification timing, which will result in patients being treated at the hospital for longer than usual. Incidentally, the end notice may be executed at any timing when a doctor or the like instructs a push notification through the doctor terminal 20.

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

[0136] (2) The processor in the above-described embodiments refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPU (=Central Processing Unit)) as well as dedicated processors (e.g., GPU (=Graphical Processing Unit), ASIC (=Application Specific Integrated Circuit), FPGA (=Field Programmable Gate Array), programmable logic devices, etc.). In addition, the operations of the processor in each of the above-mentioned embodiments may be executed by multiple processors in cooperation with each other, and the order of execution of each operation in the processor is not limited to the order described in each of the above-mentioned embodiments, and may be changed individually.

[0137] (3) In the above-described embodiment, an example was given of a case in which all authentication processing when accessing between the patient terminal 30 and the therapeutic application operation server 10 was completed within the server. However, the results may also be used in combination with authentication by a third party, including the business entity from which the patient obtained the therapeutic application or a telecommunications carrier.

[0138] (4) The therapeutic application described in the above embodiment is assumed to be prescribed to a patient with hypertension, but may be an application prescribed to a patient suffering from another disease. That is, the above-mentioned therapeutic application may be an application prescribed for, for example, nicotine addiction, insomnia, depression, diabetes, alcoholism, obesity, etc. The information to be inputted into the therapeutic application differs depending on the type of disease.

[0139] In the case of an app prescribed to patients with nicotine addiction, for example, carbon monoxide (CO) in the breath, nicotine concentration in saliva, smoking date and time, number of cigarettes smoked or number of times smoked, patient's cognitive information (way of thinking, values), exercise (number of steps, length of time exercised, distance traveled), other illnesses (diabetes), medication, blood pressure, heart rate, pulse, current physical condition (headache, irritability, feeling good, nausea, etc.), and all or part of the answers to the assumed causes are input. These pieces of information are examples of information related to smoking. In the case of an app prescribed to a patient with insomnia, for example, all or part of the following information is input: bedtime, wake-up time, sleep duration, sleep efficiency, number and type of meals, exercise record, and medication record. Bedtime, wake-up time, sleep duration, and sleep efficiency are examples of information related to sleep. In the case of an app prescribed to a patient with depression, for example, all or part of the following records may be entered: mood records, behavior records, medication records, sleep records, and appetite records.

[0140] In the case of an app prescribed for a diabetic patient, for example, all or part of the number and contents of meals, exercise records, medication records, weight, blood pressure value, and blood glucose level are input. Blood glucose level is an example of information related to blood glucose level. In the case of an app prescribed to patients with alcoholism, for example, medication records, whether or not they have drunk alcohol, and all or part of the details of their drinking are entered. In the case of an app prescribed to an obese patient, for example, all or part of the target weight, treatment start date, number of days of treatment, appropriate calorie intake, health history (mood), weight history, calorie intake history, date and time of calorie intake, medication history (dosage taken, date and time of taking medication), treatment history (treatment, content of advice, whether or not the patient performed it), medical history, blood data (AST (aspartate aminotransferase) / ALT (alanine aminotransferase)) and CT value are entered. The treatment application may allow input of information on a plurality of diseases.

[0141] (5) In the above-described embodiment, the processing operations executed by the server and the information terminal are explained using Figures 5, 9, 10, 15, 16 and 22, but the entity executing each processing operation is not limited to the exemplified contents. For example, a part or all of the processing operations performed by the therapeutic application operation server 10 may be executed by the patient terminal 30. Also, a part or all of the processing operations performed by the patient terminal 30 may be executed by the therapeutic application operation server 10.

[0142] (6) In the above explanation, the insurance medical institution is assumed to be a hospital or other facility where a doctor terminal 20 that prescribes a treatment app is installed, but when a pharmacist, public health nurse, nurse, nutritionist, hospital staff, or other medical personnel issues a prescription code, the insurance medical institution includes a facility or institution where an information terminal operated by a pharmacist, public health nurse, nurse, nutritionist, hospital staff, or other medical personnel is installed. In addition, the issuance of a prescription code is not limited to issuance for medical treatment, but may be issuance for uninsured medical treatment (i.e., non-insured medical treatment) or issuance for mixed medical treatment.

[0143] <Summary> The disclosed examples described in the above-mentioned embodiments are shown below. (((1))) An information processing system having one or more processors, the one or more processors notifying a terminal operated by a patient of the expiration of a usage period of an app prescribed to the patient for the purpose of treating a disease before the expiration of the usage period. This information processing system can provide a technique for notifying a patient in advance of the expiration of the usage period of a prescribed therapeutic app.

[0144] (((2))) The information processing system according to (((1))), wherein the processor outputs the notice when the number of days remaining until the end of the usage period is less than a threshold value when accessed from the terminal. According to this information processing system, it is possible to notify the patient of the end of the usage period in association with the patient's use of the treatment app.

[0145] (((3))) The information processing system according to (((1))), wherein the processor outputs the notice when the number of remaining days until the end of the usage period falls below a threshold value. This information processing system can notify the patient in advance of the end of the usage period even if the patient is not using the treatment app.

[0146] (((4))) The information processing system according to (((1))), wherein the processor outputs the notice at a timing when a change to the usage period is accepted from a terminal operated by a medical professional. According to this information processing system, it is possible to notify the end of the usage period at the time when a change to the usage period is received from a medical professional.

[0147] (((5))) The information processing system according to (((1)), wherein the processor causes the terminal to display an end date of the usage period as the advance notice. According to this information processing system, the end date of the usage period can be specifically notified.

[0148] (((6))) The information processing system according to (((1))), wherein the notice is displayed on the terminal as the number of days remaining until the end of the usage period. According to this information processing system, it is possible to notify the user of the number of days remaining until the expiration of the usage period.

[0149] (((7))) An information processing method in which a computer executes a process for notifying a terminal operated by a patient of the expiration of a usage period of an app prescribed to the patient for the purpose of treating a disease, before the expiration of the usage period. This information processing method can provide a technique for notifying a patient in advance of the expiration of the usage period of a prescribed therapeutic app. It should be noted that in this information processing method as well, it is possible to combine techniques corresponding to (((2))) to (((6))).

[0150] (((8))) A program for enabling a computer to have the function of notifying a device operated by a patient of the expiration of the usage period of an app prescribed to the patient for the purpose of treating an illness, before the expiration of the usage period. The program provides technology that notifies patients in advance when the usage period for prescribed therapeutic apps is about to expire. In this program, it is also possible to combine technologies corresponding to (((2))) to (((6))). [Explanation of symbols]

[0151] 1...information processing system, 10...treatment application operation server, 11, 21, 31...processor, 12, 22, 32...ROM, 13, 23, 33...RAM, 14, 24, 34...auxiliary storage device, 15, 25, 35...communication interface, 16, 28...signal line, 20...doctor terminal, 26, 36...display, 27, 37...input reception device, 30...patient terminal

Claims

1. One or more processors; The one or more processors: An information processing system that notifies a device operated by a patient of the expiration of the usage period of an app prescribed to the patient for the purpose of treating a disease, before the usage period expires.

2. the processor outputs the notice when the number of remaining days until the end date of the usage period is less than a threshold value at the time of access from the terminal. The information processing system according to claim 1 .

3. The processor outputs the notice when the number of remaining days until the end date of the usage period falls below a threshold. The information processing system according to claim 1 .

4. The processor outputs the notice at a timing when a change to the usage period is accepted from a terminal operated by a medical professional. The information processing system according to claim 1 .

5. The processor causes the terminal to display, as the notice, an end date of the usage period. The information processing system according to claim 1 .

6. displaying, as the advance notice, the number of days remaining until the end of the usage period on the terminal; The information processing system according to claim 1 .

7. The computer A process for notifying a device operated by a patient of the expiration of a usage period of an app prescribed to the patient for the purpose of treating a disease before the expiration of the usage period; An information processing method for performing the above.

8. On the computer, A program that enables a function to notify the patient of the expiration of the usage period of an app prescribed to the patient for the purpose of treating an illness on the device operated by the patient before the expiration of the usage period.

Images