Information processing system, method for processing information, and program

Abstract

To provide a technique of switching execution or non-execution of an application installed to a terminal of a patient by prescription, from a terminal operated by a medical service worker.SOLUTION: An information processing system has at least one processor. The at least one processor displays information for identifying a patient to which an application was prescribed, in an operation screen of a first terminal operated by a medical service worker, and receives an operation by a medical service worker of switching execution or non-execution of an application installed to a second terminal operated by a patient through an operation screen.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. For this reason, even if you do not visit a doctor as instructed, you can continue to use the therapeutic app as long as it is within the insured medical treatment period. The same applies to therapeutic apps with an expiration date that are prescribed under private medical care or mixed medical care.

[0005] One embodiment of the present disclosure provides a technology that enables a medical professional to switch whether or not an app installed on a patient's device by prescription can be executed from the device operated by the medical professional. [Means for solving the problem]

[0006] As another aspect of the present disclosure, an information processing system is provided that has one or more processors, which display information identifying a patient to whom the app has been prescribed on an operation screen of a first terminal operated by a medical professional, and accepts, via the operation screen, an operation by the medical professional to switch whether or not the app installed on a second terminal operated by a patient can be executed.

[0007] As another aspect of the present disclosure, there is provided an information processing method in which a computer executes a process of displaying information identifying a patient to whom the app has been prescribed on an operation screen of a first terminal operated by a medical professional, and a process of accepting, via the operation screen, an operation by the medical professional to switch whether or not the app installed on a second terminal operated by a patient can be executed.

[0008] As one form of the present disclosure, a program is provided to enable a computer to perform the following functions: displaying information identifying a patient to whom the app has been prescribed on an operation screen of a first terminal operated by a medical professional; and accepting, via the operation screen, an operation by the medical professional to switch whether or not the app installed on a second terminal operated by a patient can be executed. Effect of the Invention

[0009] According to one embodiment of the present disclosure, a technology can be provided that enables a medical professional to switch whether or not an app installed on a patient's device by prescription can be executed from the device operated by the medical professional. [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 process sequence illustrating an example of a process 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 diagram illustrating an example of a management screen of a treatment application displayed on a display of a doctor terminal. FIG. [Figure 10] FIG. 13 is a diagram illustrating an example of a display of a details screen of person A before he starts using a treatment application. [Figure 11] 13 is a diagram illustrating a display example of a setting screen used to switch whether or not a therapeutic application can be executed. FIG. [Figure 12] 13 is a diagram illustrating a display example of a details screen of Mr. H who is using a treatment application. FIG. [Figure 13] 13A and 13B are diagrams illustrating another example of a display of a setting screen used for switching whether or not a therapeutic application can be executed. [Figure 14] 13 is a diagram illustrating an example of a display of a setting screen on which an enlarged calendar used to specify a stop date is displayed. FIG. [Figure 15] FIG. 13 is a diagram illustrating an example of a display of a details screen after a stop date is specified. [Figure 16] FIG. 13 is a diagram illustrating an example of the management screen of the medical treatment app after the end date of Mr. H's medical treatment app has been specified by the doctor. [Figure 17] 13 is a flowchart illustrating an example of control for stopping a therapeutic application by a therapeutic application operation server. [Figure 18] 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. [Figure 19] FIG. 13 is a diagram illustrating an example of a message displayed on a display of a patient terminal. [Figure 20] 13 is a flowchart illustrating an example of an alert notification by a doctor terminal. [Figure 21] 13 is a diagram illustrating an example of an alert screen displayed on the display of the doctor terminal. FIG. [Figure 22] FIG. 13 is a diagram illustrating an example of an alert screen that is displayed when a "Confirm" button is operated. [Diagram 23] FIG. 13 is a diagram showing another display example of the management screen of the treatment application. [Figure 24] FIG. 13 is a diagram illustrating an example of an alert notification using a detailed screen for each patient. [Diagram 25] 13 is a diagram illustrating an example of an alert screen suggesting stopping the execution of a therapeutic application. 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 leg 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. 1. The doctor terminal 20 is an example of a first terminal. 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 depicted in Fig. 1. The patient terminal 30 is an example of a second terminal.

[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 / examination 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 / examination 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 treatment app was prescribed is called the "prescription date" and is distinguished from other examination dates. In the case of FIG. 3, the prescription date is July 31, 2023, and the second examination date is August 29, 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] The end date of use of the therapeutic app is information that gives the date on which the use of the therapeutic app will end. The end date of use is a date that precedes the end date of the insured medical treatment period. In the present embodiment, the end date of use can only be specified by a doctor. This is because shortening the available period may be detrimental to the patient. On the other hand, shortening the available period by specifying the end date of use also has the aspect of encouraging patients who have not been examined for a long time to visit the hospital. Incidentally, the execution of the therapeutic application in the patient terminal 30 (see FIG. 1) is stopped (ie, disabled) at the first communication between the patient terminal 30 and the therapeutic application operation server 10 after the usage end date.

[0034] The patient data 142 shown in Fig. 3 is composed of, for example, a chart number, a user ID, a patient name, an input date and time, and a blood pressure value. As mentioned above, the patient data 142 also records information other than the blood pressure value, but this 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.

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

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

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

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

[0039] <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 operation 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0055] 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 out 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.

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

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

[0058] <Change in the usage period of the treatment app by the doctor's device> <Example of management screen> FIG. 9 is a diagram for explaining an example of a management screen of a treatment application displayed on the display 26 of the doctor terminal 20. As shown in FIG. 9 is generated based on authentication data 141 (see FIG. 3) related to a patient who is managed 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 medical application operation server 10 is used. The management screen of the therapeutic application shown in FIG. 9 is an example of an operation screen used to switch whether or not the therapeutic application is executed on the patient terminal 30.

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

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

[0061] The management screen shown in FIG. 9 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. FIG. 9 illustrates, as management items, a chart number / patient name 265A, an application name 265B, a status 265C, a planned stop date 265D, a prescription date 265E, and an application usage start date 265F.

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

[0063] 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 9, the differences in app names are distinguished as "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.

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

[0065] "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 the doctor, etc., and is different from the end date of the insured medical treatment period that is mechanically determined or the end date based on the operation rules (for example, the end of the month following the month of the consultation or the date 40 days after the consultation). The operation rules to be applied may be registered, selected, switched, etc. by the doctor, etc. 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.

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

[0067] Basically, a disabled treatment app will not be able to be launched. However, it is also possible to permit the start of the treatment application and to allow viewing of previously entered patient data, while prohibiting new input of patient data. In other words, in this embodiment, stopping the execution of functional units such as the patient data input function and the patient data viewing function is also considered as a form of the disabled state.

[0068] "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 usage period that is mechanically set by the insurance medical treatment period that gives the maximum usage period of the therapeutic app or the operation rules of the information processing system 1 (see FIG. 1) has passed, as well as a state where the reserved end date of usage has passed or a state where a doctor or the like has instructed immediate suspension of usage. When the information indicates "end", the execution of the therapeutic application is stopped in the patient terminal 30. Therefore, "end" is also an example of information indicating the stop of the execution of the therapeutic application. However, the therapeutic application in the patient terminal 30 is actually stopped when communication between the therapeutic application operation server 10 and the patient terminal 30 is established.

[0069] 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". This switching operation is an example of an operation by a medical professional to switch whether or not to execute the therapeutic app.

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

[0071] Conversely, an operation to switch the state of the status 265C from “scheduled to be stopped” or “ended” to “in use” is also possible. These switching operations are also examples of operations by medical personnel to switch whether or not a treatment app can be executed. For example, when a medical examination cannot be received within the specified period due to reasons attributable to a medical institution (e.g., cancellation of a medical examination due to trouble with equipment, etc.) or due to reasons attributable to the patient (e.g., forgetfulness, restricted going out), it may be possible to change "Scheduled Stop" or "End" to "In Use" even after the specified stop date designated by a doctor, etc. or after the mechanically determined end date. However, it is prohibited to change "End" to "In Use" on the grounds of the expiration of the insurance-covered medical treatment period.

[0072] The scheduled stop date 265D is used for displaying the date (i.e., the stop date) set when the status 265C is "Scheduled Stop". In the case of this embodiment, a doctor, etc. can directly input the date into the corresponding frame or cell corresponding to the scheduled stop date 265D. It is also possible to change the displayed date to another date. The prescription date 265E is used for displaying the date when a treatment application was prescribed by a doctor, etc. The application start deadline 265F is used for displaying the last day when the prescription code issued at the time of prescribing the treatment application is valid. In the case of this embodiment, the date three days after the prescription date 265E is displayed for the application start deadline 265F.

[0073] The current date and time 266 is the date and time when the management screen of the treatment application shown in FIG. 9 is viewed. The "Details" button 267 is a button used for displaying the information screen for each patient. The "Details" button 267 is arranged for each row corresponding to a patient. The "Close" button 268 is a button for closing the management screen of the treatment application shown in FIG. 9.

[0074] <Example of Details Screen> <Screen of Mr. A> FIG. 10 is a diagram for explaining an example of the display of the details screen 270 of Mr. A before starting the use of the treatment application. The details screen 270 is also generated by the treatment application operation server 10 (see FIG. 1). However, for information that is not managed by the medical application operation server 10 (see FIG. 1), information collected through a browser plug-in or the like executed on the doctor terminal 20 (see FIG. 1) is displayed. The browser realizes linkage with electronic medical records of medical institutions through the plug-in or the like.

[0075] In the present embodiment, the details screen 270 is displayed by operating the "details" button 267 (see FIG. 9). For example, it is displayed as a pop-up on the management screen of the treatment application shown in FIG. A part of the display contents of the details screen 270 is the same as the display contents of the management screen of the therapeutic application. On the other hand, the details screen 270 also displays personal information that was not displayed on the management screen of the therapeutic application.

[0076] In the case of FIG. 10, the details screen 270 is composed of a patient icon 270A, an application icon 270B, a medical record number 270C, gender 270D, date of birth 270E, prescription code 270F, status 270G, planned stop date 270H, prescription date 270I, application usage start deadline 270J, and prescriber 270K. The patient icon 270A displays a photograph of the patient's face or a face image linked to the patient's account and published. If there is no corresponding photograph or image, an icon such as that shown in FIG. 10 is displayed.

[0077] The application icon 270B displays the icon and application name registered for the treatment application. The medical record number registered in the authentication data 141 is displayed in the medical record number 270C. Gender 270D displays information recorded in an electronic medical record, etc. In this embodiment, gender is not specified. Date of birth 270E displays the patient's date of birth as recorded in the electronic medical record or the like.

[0078] The prescription code read out from the authentication data 141 is displayed in the prescription code 270F. The status 270G, the planned stop date 270H, the prescription date 270I, and the application usage start date 270J display the same information as in the management screen of the medical application shown in FIG. The doctor ID of the authentication data 141 and the name of the doctor linked to the doctor ID are displayed to the prescriber 270K.

[0079] In the case of the details screen 270, when a doctor or the like taps the status 270G or clicks the status 270G with a pointer, a screen for switching whether or not the treatment app can be executed is displayed. Fig. 11 is a diagram for explaining a display example of a setting screen 280 used for switching whether or not a therapeutic application can be executed. The setting screen 280 shown in Fig. 11 can be transitioned from not only the details screen 270 (see Fig. 10) but also the management screen of the therapeutic application shown in Fig. 9. This setting screen 280 is also an example of an operation screen used by doctors and other medical personnel to switch the execution of a therapeutic application.

[0080] The setting screen 280 shown in FIG. 11 is composed of a title 280A, a stop use button 280B, a stop date designation field 280C, and a "close" button 280D. 11, the title 280A displays "Change prescription information." The title "Change prescription information" indicates that this is a screen for accepting changes to prescription information. The use stop button 280B is a radio button for switching whether or not to stop the use of the treatment application (that is, whether or not to execute the treatment application). That is, the use stop button 280B is an example of an operator used to specify whether or not to execute the treatment application. However, since Mr. A has not yet started using the treatment application, the stop use button 280B is displayed in a non-selected state.

[0081] The stop date designation field 280C is an input field used to designate a stop date. In Fig. 11, the use suspension button 280B is in an unselected state, so the stop date designation field 280C is also displayed in an unselected state. That is, the stop date designation field 280C in Fig. 11 is displayed in a state in which it cannot be operated by a doctor or the like. The "Close" button 280D is a button for closing the setting screen 280 and returning to the previous screen.

[0082] <Mr. H's screen> FIG. 12 is a diagram for explaining an example display of the detailed screen 270 of Mr. H while using the treatment application. In FIG. 12, reference numerals corresponding to the corresponding parts in FIG. 10 are shown. Among the information other than the status 270G in the detailed screen 270 shown in FIG. 12, personal information of Mr. H and unique information based on prescriptions from doctors, etc. are displayed. Note that the status 270G of Mr. H is "In use". FIG. 13 is a diagram for explaining another example display of the setting screen 280 used for switching the execution availability of the treatment application. In FIG. 13, reference numerals corresponding to the corresponding parts in FIG. 11 are shown. The setting screen 280 shown in FIG. 13 is also displayed when a doctor, etc. taps on the status 270G (see FIG. 12) or clicks on the status 270G with a pointer.

[0083] In the case of the setting screen 280 shown in FIG. 13, since Mr. H is using the treatment application, the suspension button 280B is displayed in a selectable state. In FIG. 13, the suspension button 280B has been selected by a doctor, etc. Therefore, the stop date specification field 280C is also displayed in a selectable manner. However, it is also possible to close the setting screen 280 without operating the stop date specification field 280C, that is, without specifying a stop date. When the setting screen 280 is closed without specifying a stop date and the selection state of the suspension button 280B is confirmed, the use of Mr. H's treatment application is immediately stopped.

[0084] Hereinafter, the case where Mr. H reserves a stop date for the treatment application he uses will be described. The stop date specification field 280C in FIG. 13 is composed of a checkbox field 280C1, an explanatory text 280C2 regarding the operation, a calendar 280C3, and an explanatory text 280C4 regarding the stop date. The check box field 280C1 shown in Fig. 13 is composed of a check box and a remark. In the case of Fig. 13, the remark reads "Specify the date to stop", and a doctor or the like is informed that the check box must be operated when the stop date is to be specified. The check box field 280C1 here is an example of an operator used to specify whether or not a therapeutic app can be executed.

[0085] The explanatory text 280C2 may say, for example, "If you want to specify the date on which you want to stop using the service, please specify and change the date," indicating that it is necessary to specify a stop date. The explanatory text 280C4 may state, for example, "You can specify a stop date up to December 26, 2023," indicating the last date that can be specified. This is because there is no point in specifying a date after the mechanically determined end date as the stop date. When a doctor or the like taps or clicks the check box field 280C1 with the pointer, a calendar 280C3 is displayed in an enlarged scale.

[0086] Fig. 14 is a diagram illustrating an example of a display of the setting screen 280 in which the calendar 280C3 used to specify the stop date is displayed in an enlarged manner. In Fig. 14, the parts corresponding to those in Fig. 13 are denoted by the same reference numerals. In the setting screen 280 shown in FIG. 14, a check box field 280C1 is checked, and a calendar 280C3 is displayed in an enlarged manner. The doctor or other such person completes the designation of the stop date by designating a specific date on the calendar 280C3. When the check box field 280C1 is unchecked, the designation of the stop date is cancelled and the display size of the calendar 280C3 returns to the size before it was enlarged.

[0087] When the "Close" button 280D is operated with the stop date specified, the stop date specification is finalized. Thereafter, the setting screen 280 closes, and the screen returns to the screen before the transition to the setting screen 280. Fig. 15 is a diagram for explaining a display example of the details screen 270 after the stop date has been specified. In Fig. 15, parts corresponding to those in Fig. 12 are denoted by the same reference numerals. In the details screen 270 shown in FIG. 15, the display of the status 270G is changed from "in use" to "scheduled to be stopped," and the date designated by the doctor or the like is displayed in the planned stop date 270H.

[0088] Fig. 16 is a diagram for explaining an example of a management screen of a medical treatment app after a doctor has specified an end date of the medical treatment app for Mr. H. In Fig. 16, the parts corresponding to those in Fig. 9 are denoted by the same reference numerals. The difference between the management screen shown in Figure 16 and the management screen shown in Figure 9 is that the status 265C, which was previously displayed as "In use," has been changed to "Planned to be stopped," and the planned stop date 265D, which was previously blank, has been changed to "2023 / 08 / 15." A doctor or the like can check the change in the status of the therapeutic app prescribed for each patient by checking the change in the display content of the therapeutic app management screen.

[0089] <Controlling the termination of treatment apps> 17 is a flowchart illustrating an example of the therapeutic application stop control by the therapeutic application operation server 10. The process illustrated in FIG. 17 is executed by the processor 11 (see FIG. 2) of the therapeutic application operation server 10. 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.

[0090] When an access from the patient terminal 30 is detected, a positive result is obtained in S201. In this case, the processor 11 judges whether the current time is within the insured medical treatment period of the treatment app that is the access source (S202). For example, when a user ID linked to the treatment app can be acquired from the patient terminal 30, the processor 11 identifies the insured medical treatment period of the treatment app by identifying the patient that is the access source. Also, for example, when a prescription code of the treatment app that is the access source can be acquired, the processor 11 identifies the insured medical treatment period through the prescription code.

[0091] If the current time is within the insured medical treatment period, a positive result is obtained in S202. In this case, the processor 11 determines whether or not a scheduled stop date or end date is set in the treatment application (S203). The scheduled stop date here is the stop date specified by a doctor or the like. The end date is the end date based on the operation rules. If no scheduled stop date or end date is set, a negative result is obtained in S203. In this case, the processor 11 records the received patient data (S204). In the case of this embodiment, the patient data is blood pressure values, review information, activity records, etc. After this, the processor 11 temporarily ends the processing for the access to be processed, and resumes the judgment in S201.

[0092] If the scheduled stop date or end date is set, a positive result is obtained in S203. In this case, the processor 11 determines whether the current time is on or after the scheduled stop date or end date of the treatment app (S205). If the current time is before the scheduled stop date or end date of the treatment application, a negative result is obtained in S205. In this case, the processor 11 records the received patient data (S204). On the other hand, if the current time is after the scheduled stop date or end date of the treatment app, a positive result is obtained in S205. In this case, or if the result in S202 is negative (if the current time is after the insured medical treatment period), the processor 11 instructs the patient terminal 30 that is the access source to stop the execution of the treatment app (S206). After this, the processor 11 temporarily ends the process for the access to be processed, and resumes the judgment in S201.

[0093] FIG. 18 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. 18 consists of two stages. The first stage is processing operations S301 to S303 related to registration of the stop date or planned stop date of the treatment app by the doctor. The second stage is the therapeutic application operation server 10 performing a therapeutic application stop process (S311 to S315).

[0094] <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. 9) etc. (S301). 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 (S302), and notifies the doctor terminal 20 of the completion of the registration (S303). The completion of the notification is displayed on the display 26 of the doctor terminal 20 (see FIG. 4).

[0095] <Second stage> The second stage begins with the launch of the therapeutic application in the patient terminal 30 (S311). When the therapeutic application is launched, the patient terminal 30 transmits an account ID and password used for logging in to the therapeutic application operation server 10 (S312). The therapeutic application operation server 10 executes authentication processing using the received account ID and password (S313). 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 has been successful.

[0096] Next, the therapeutic application operation server 10 checks the planned stop date, etc. of the therapeutic application that is the access source (S314). The planned stop date, etc. here include the stop date, the planned termination date, and the end date. In the case of FIG. 18, the planned stop date, etc. are set in S302. Therefore, the therapeutic application operation server 10 notifies the patient terminal 30 that the execution of the therapeutic application will be stopped (S315). The patient terminal 30 stops the execution of the target therapeutic application in accordance with the received notification (S316), in other words, invalidates the target therapeutic application. 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 S311 is stopped.

[0097] Fig. 19 is a diagram for explaining an example of a message 361 displayed on the display 36 of the patient terminal 30. In Fig. 19, parts corresponding to those in Fig. 7 and Fig. 10 are denoted by the same reference numerals. A message 361 shown in FIG. 19 is displayed immediately after the tap operation on the icon 270B of the "Treatment application 1" or as an initial screen of the started "Treatment application 1".

[0098] A message 361 shown in Fig. 19 states, "The usage period of the treatment app has ended," and "To resume use of the treatment app, please visit the prescribed hospital for a consultation." This message assumes that the treatment app will be resumed after a follow-up visit. However, if the execution suspension is not lifted and a new therapeutic app is prescribed at the time of a follow-up visit, the message may simply read, for example, "The therapeutic app usage period has ended." Message 361 may be designed to automatically close after a certain period of time (for example, five seconds) has elapsed since it was displayed. A "Close" button 362 is provided in the message 361 shown in FIG. 19, allowing the patient to close the display of the message 361 by himself.

[0099] <Summary> According to the information processing system 1 (see FIG. 1) of this embodiment, it is possible to switch whether or not to execute a therapeutic app installed in the patient terminal 30 by prescription from the doctor terminal 20 operated by a doctor or the like. Specifically, by specifying a stop date or planned stop date on the treatment app management screen (see Figure 9) displayed on the display 26 (see Figure 4) of the doctor terminal 20 (see Figure 1), or by canceling a specified stop date or planned stop date, it becomes possible for a doctor or the like to switch whether or not a treatment app installed on a specific patient terminal 30 can be executed.

[0100] In addition, the management screen of the treatment app (see FIG. 9) and the detail screen 270 (see FIG. 10) display the planned stop date (scheduled stop date) in association with information for identifying the patient (e.g., medical record number, patient name), so that it is easy to check the patients who have reserved a stop date or a planned stop date for the treatment app they are using. At the same time, it is easy to check the stop date of the treatment app they are using. In addition, by displaying status 265C (see Figure 9) on the management screen of the treatment app and status 270G (see Figure 10) on the details screen 270 (see Figure 10), a doctor operating the doctor terminal 20 (see Figure 1) can easily check the current status regarding whether or not the treatment app can be executed for each patient.

[0101] Furthermore, the doctor or the like can schedule the suspension of execution of the therapeutic app through operators such as the status 265C (see FIG. 9) on the management screen of the therapeutic app, the status 270G (see FIG. 10) on the detail screen 270 (see FIG. 10), a radio button (e.g., the stop use button 280B) provided on the setting screen 280, and a check box (e.g., the check box field 280C1). This makes it easy for the doctor or the like to schedule the date on which execution of the therapeutic app will be suspended. In other words, the burden on the doctor or the like of switching whether or not to execute the therapeutic app can be reduced.

[0102] <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 doctor terminal 20 in the second embodiment differs from the information processing system 1 in the first embodiment in that a function for presenting information on patients who have not been treated for a long period of time to a doctor or the like is added.

[0103] 20 is a flowchart illustrating an example of an alert notification by the doctor terminal 20. The process shown in FIG. 20 is executed by the processor 21 of the doctor terminal 20 (see FIG. 4). First, the processor 21 acquires one of the medical data of the patient under treatment (S401). The medical data of the patient under treatment is acquired, for example, from the auxiliary storage device 24 (see FIG. 2) of the doctor terminal 20 or an electronic medical record stored in the management system of the health insurance medical institution. In addition, patients who do not have a record of completion of treatment in their electronic medical records, etc., will be considered as patients still undergoing treatment.

[0104] Next, the processor 21 calculates the number of days that have passed since the acquired medical data up to the present time (S402). Next, the processor 21 determines whether the number of elapsed days exceeds a threshold value (S403). If the number of days elapsed exceeds the threshold, a positive result is obtained in S403. In this case, the processor 21 records the patient's chart number (S404).

[0105] After execution of S404, or if a negative result is obtained in S403 (the number of elapsed days does not exceed the threshold), the processor 21 determines whether or not processing of all patients currently being treated has been completed (S405). If there are any untreated patients remaining among the patients under treatment, a negative result is obtained in S405. In this case, the processor 21 returns to S401. On the other hand, if the processing of all patients under treatment is completed, a positive result is obtained in S405. In this case, the processor 21 determines whether or not there is a recorded medical record number (S406). The medical record number here means the medical record number recorded in S404.

[0106] If the recorded chart number exists, a positive result is obtained in S406. In this case, the processor 21 outputs an alert to the screen of the doctor terminal 20 (S407). The output of the alert here includes, for example, a pop-up display on the display 26. After executing this S407, the processor 21 ends the series of processes. If the recorded medical record number does not exist, a negative result is obtained in S406. In this case, the processor 21 ends the series of processes without outputting an alert. The processing operation shown in Fig. 20 is periodically and repeatedly executed. For example, it is executed at a fixed time every day. For example, it is executed at 9 am and 5 pm. It may also be executed at a timing instructed by a doctor or the like.

[0107] FIG. 21 is a diagram for explaining an example of an alert screen 290 displayed on the display 26 of the doctor terminal 20. As shown in FIG. The title of the alert screen 290 displays "Alert" and "Regarding a patient undergoing treatment with a treatment application." In other words, it indicates that the alert is about a patient undergoing treatment with a treatment application.

[0108] Furthermore, on the alert screen 290, "There are patients for whom it has been more than 40 days since their last examination" is displayed as the content 291 of the alert. Note that the text above is just an example; other possible text could be something like "There is a patient who has not been seen for a while," which notifies the presence of the patient who is the subject of the alarm, or "Mr. A has not been seen for a while," which notifies the name of the patient who is the subject of the alarm. This alert screen 290 is an example of a screen that notifies the presence of a patient whose number of days since the last consultation date exceeds a threshold value.

[0109] Incidentally, "40 days" corresponds to the threshold value of S403 (see FIG. 20). Note that 40 days is the number of days obtained by adding a buffer period of 10 days, assuming that a patient undergoing treatment using a treatment app is required to have a medical examination (or medical treatment) once every 30 days. Therefore, for a treatment app that requires consultation (or medical treatment) once every two months, a threshold of 70 days (60 days + 10 days) may be used. The value of the buffer period is 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 application, or may be a specification that can be freely specified by a doctor.

[0110] In addition, the alert screen 290 has a “Confirm” button 292 and a “Close” button 293 arranged thereon. In the case of this embodiment, when the "Confirm" button 292 is operated, a list of patient information that is the subject of the alert is displayed. Incidentally, when the "close" button 293 is operated, the alert screen 290 is closed.

[0111] Fig. 22 is a diagram for explaining a display example of an alert screen 290 that is displayed when the "Confirm" button 292 is operated. In Fig. 22, reference numerals corresponding to those in Fig. 21 are used. An alert screen 290 shown in FIG. 22 displays a chart number 292A, a patient name 292B, an application name 292C, the number of days elapsed 292D, and a "details" button 292E.

[0112] Incidentally, medical record number 292A and patient name 292B correspond to medical record number / patient name 265A (see FIG. 9). Also, application name 292C corresponds to application name 265B (see FIG. 9). Also, "details" button 292E corresponds to "details" button 267 (see FIG. 9). An item specific to the alert screen 290 is the number of days since the alert was issued 292D. This item makes it possible to check the number of days since the alert was issued by linking it to the name of the patient who was the subject of the alert. For example, it can be seen that the number of days since the alert was issued for Mr. X is 46 days, and the number of days since the alert was issued for Mr. P is 45 days.

[0113] <Another example of the alert screen> An example of the alert screen output in S407 (see FIG. 20) will be described below.

[0114] <Example 1> Fig. 23 is a diagram showing another display example of the management screen of a treatment application, in which the same reference numerals are used to denote parts corresponding to those in Fig. 9. On the management screen of the medical treatment application shown in FIG. 23, a label 269 reading "Caution" is displayed in the field of the planned stop date 265D.

[0115] By displaying label 269 in the item field where date and time are normally displayed, it becomes easier to notice that the number of days that have passed since the last consultation date until the present time has exceeded the threshold value. It is also possible to notify by other displays. For example, if the display color of "In Use" in status 265C is normally "black," it may be displayed in "red," or the entire line may be displayed in high brightness, or the entire line may be displayed in a blinking manner. In other words, the presence of the target patient can be easily noticed by changing the display mode.

[0116] <Example 2> Fig. 24 is a diagram for explaining an example of an alert notification using a detailed screen for each patient. In Fig. 24, parts corresponding to those in Fig. 10 are denoted by the same reference numerals. In Fig. 24, label 270L reading "Caution" is displayed in the item for planned stop date 270H, as in Fig. 23. However, in the case of Fig. 24, label 270L is displayed at the beginning of the line for planned stop date 270H. By displaying label 270L in a position different from the display position of so-called attribute values, the presence of label 270L can be easily noticed. Label 270L may be displayed at the display position of the attribute value corresponding to planned stop date 270H, or, similar to label 269 (see FIG. 23), may notify the presence of an alert by changing the display color, changing the display brightness, blinking, etc. That is, by changing the display mode, it is possible to make the target patient more easily aware of the change.

[0117] <Example 3> Fig. 25 is a diagram illustrating an example of an alert screen 300 that suggests stopping the execution of a therapeutic application. In Fig. 25, parts corresponding to those in Fig. 22 are denoted by the same reference numerals. The alert screen 300 is also displayed as a pop-up on the management screen of the medical application shown in FIG.

[0118] An alert screen 300 displays two messages 301 and 302 . In the case of FIG. 25, the message 301 states "Mr. H has not been seen for more than 40 days since his last visit," and the message 302 states "Do you want to stop using the medical treatment application 1?". The message 302 here suggests stopping the execution of the treatment application as one of the countermeasures, based on the message 301 notifying the fact.

[0119] The message 302 also includes information for identifying the therapeutic application that is a candidate for stopping. Incidentally, when the "Details" button 292E is operated, for example, a patient-specific details screen 270 (see FIG. 12) pops up, making it possible to check Mr. H's status and specify a scheduled stop date.

[0120] <Summary> According to the information processing system 1 (see FIG. 1) of this embodiment, it is possible to notify a doctor or the like of the presence of a patient who has been seen for a long time since his or her last consultation. At that time, the system can notify the specific names of patients who have been seen for a long time since their last appointment. Furthermore, when the alert screen 300 is output, it is possible to suggest to the doctor or the like to stop the execution of the treatment app, which is one of the measures for a patient who has been examined a long time ago.

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

[0122] (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.

[0123] (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.

[0124] (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.

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

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

[0127] (5) In the above-described embodiment, the processing operations executed by the server and the information terminal are explained using Figures 5, 17, 18 and 20, but the entity executing each processing operation is not limited to the exemplified contents. For example, the processing operation performed by the medical device terminal 20 may be executed by the medical device management system of the medical institution to which the doctor belongs. Also, the processing operation performed by the medical device terminal 20 may be executed by the medical device management system of the medical institution to which the doctor belongs or by the medical device management system of the medical institution to which the doctor belongs.

[0128] (6) In the case of the above-mentioned embodiment 2, notifications such as the presence of a patient whose number of days since the last consultation date exceeds a threshold value are displayed on the operation screen of the doctor terminal 20 (see FIG. 1) via alert screens 290 (see FIG. 21 and FIG. 22), 300 (see FIG. 25) or labels 269 (see FIG. 23), 270L (see FIG. 24). However, notifications may also be sent via e-mail, etc.

[0129] (7) 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.

[0130] <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 display information identifying a patient to whom the app has been prescribed on an operation screen of a first terminal operated by a medical professional, and accept, via the operation screen, an operation by the medical professional to switch whether or not the app installed on a second terminal operated by a patient can be executed. This information processing system can provide technology that enables medical professionals to switch whether or not an app installed on a patient's device via a prescription can be executed from the device they operate.

[0131] (((2))) The information processing system according to (((1))), wherein the processor accepts a command to stop execution of the application as an operation on an operator on the operation screen. This information processing system can reduce the burden on medical personnel of switching between enabling and disabling the execution of an app.

[0132] (((3))) The information processing system according to (((1))) or (((2))), wherein the processor accepts a reservation for a date for stopping the app via an operation screen. According to this information processing system, a reservation for a date on which an application is to be stopped can be easily specified.

[0133] (((4))) The information processing system according to (((3))), wherein the processor displays the existence of a reservation for the stop date in association with the information. This information processing system makes it easy to check patients who have scheduled dates for when the app will be stopped.

[0134] (((5))) The information processing system according to (((3))) or (((4))), wherein the processor displays the reserved stop date in association with the information. This information processing system makes it easy to check the scheduled app stop date for a patient.

[0135] (((6))) The information processing system according to any one of (((1))) to (((5))), wherein the processor displays, on the operation screen, a current status regarding whether or not the application can be executed. This information processing system can assist in determining whether or not to run an application.

[0136] (((7))) The information processing system described in (((6))), wherein the current status includes at least one of information indicating before use of the app has started, information indicating that the app is being used, information indicating that there is a reservation for a date on which use of the app will be stopped, information indicating that execution of the app has stopped, and information indicating the end of the usage period of the app. This information processing system can assist in determining whether or not to run an application.

[0137] (((8))) The information processing system according to any one of (((1))) to (((7))), wherein the processor notifies the presence of a patient whose number of days elapsed since the last consultation date until the present exceeds a threshold value. This information processing system makes it easier to notice the presence of patients who have been examined for a long time.

[0138] (((9))) The information processing system described in (((8))), wherein the processor further notifies the number of days elapsed and information identifying the relevant patient. According to this information processing system, it is possible to specifically notify patients who have been examined a long time ago.

[0139] (((10))) The information processing system according to (((8))), wherein the processor further notifies information suggesting stopping execution of an app linked to the information identifying the patient in question. According to this information processing system, it is possible to suggest stopping the execution of a therapeutic app, which is one of the measures for a patient for whom a long time has passed since their last consultation.

[0140] (((11))) An information processing method in which a computer executes a process of displaying information identifying a patient to whom the app has been prescribed on an operation screen of a first terminal operated by a medical professional, and a process of accepting, via the operation screen, an operation by the medical professional to switch whether or not the app installed on a second terminal operated by a patient is to be executed. This information processing method provides a technology that enables a medical professional to switch whether or not an app installed on a patient's device by prescription can be executed from the device operated by the medical professional. It should be noted that in this information processing method as well, it is possible to combine techniques corresponding to (((2))) to (((10))).

[0141] (((12))) A program for enabling a computer to perform the following functions: displaying information identifying a patient to whom the app has been prescribed on the operation screen of a first device operated by a medical professional; and accepting, via the operation screen, an operation by the medical professional to switch whether or not the app installed on a second device operated by a patient should be executed. This program provides technology that allows medical professionals to control whether or not an app installed on a patient's device via prescription can be executed from the device they operate. In addition, in this program, it is possible to combine technologies corresponding to (((2))) to (((10)). [Explanation of symbols]

[0142] 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, 38...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: The app displays information identifying the patient to whom the prescription is given on the operation screen of the first terminal operated by the medical professional; accepting, via the operation screen, an operation by a medical professional to switch whether or not the app installed in the second terminal operated by the patient is executed; Information processing system.

2. The processor accepts a command to stop the execution of the application as an operation performed on an operator on the operation screen. The information processing system according to claim 1 .

3. The processor accepts, via the operation screen, a reservation for a date for stopping the application. The information processing system according to claim 1 .

4. The processor displays the existence of a reservation for the stop date in association with the information. The information processing system according to claim 3 .

5. The processor displays the reserved stop date in association with the information.

5. The information processing system according to claim 3 or 4.

6. The processor displays a current status regarding whether the application can be executed on the operation screen. The information processing system according to claim 1 .

7. the current status includes at least one of information indicating a state before use of the app has started, information indicating that the app is being used, information indicating that a reservation exists for a date on which use of the app will be stopped, information indicating that execution of the app has been stopped, and information indicating that a period during which the app is in use has ended; 7. The information processing system according to claim 6.

8. The processor, Notify the presence of patients whose number of days since their last visit exceeds a threshold; The information processing system according to claim 1 .

9. The processor, Further notifying the number of days elapsed and information identifying the corresponding patient. The information processing system according to claim 8.

10. The processor, Further notifying the patient of information suggesting stopping the execution of the app linked to the information identifying the patient. The information processing system according to claim 8.

11. The computer A process of displaying information identifying a patient to whom the app is prescribed on an operation screen of a first terminal operated by a medical professional; A process of accepting, via the operation screen, an operation by a medical professional to switch whether or not the app installed in the second terminal operated by the patient is executed; An information processing method for performing the above.

12. On the computer, A function of displaying information identifying a patient to whom the app is prescribed on an operation screen of a first terminal operated by a medical professional; A function of accepting, via the operation screen, an operation by a medical professional to switch whether or not the app installed in the second device operated by the patient is executed; A program to achieve this.

Images