Information processing system, information processing method, and program

Abstract

To provide a function for prompting transfer of patient data entered through a prescribed first application to a second application.SOLUTION: An information processing system comprising one or more processors is provided, the one or more processors being configured to output a notification prompting transfer of first patient data entered through a first application prescribed for the purpose of treating disease and installed on a terminal of a patient to a second application used for entering second patient data.SELECTED DRAWING: Figure 15

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. A patient who has received a prescription for a therapeutic app installs the therapeutic app on their own electronic device and inputs the patient's information (hereinafter also referred to as "patient data") until the next consultation with a doctor. The patient data is stored, for example, in a cloud server managed by the developer of the therapeutic app, and is also used for insurance treatment at insurance medical institutions. [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 are regulated by a set period during which they are covered by the medical insurance system (hereinafter referred to as the "insured medical treatment period"). In other words, the use of the therapeutic app is limited to the insured medical treatment period, and after the insured medical treatment period ends, it will no longer be possible to input patient data, etc. However, treatment for chronic diseases caused by lifestyle habits continues even after the insurance medical treatment period ends. For this reason, support for inputting patient data is desired even after the insurance medical treatment period ends. For example, the use of an application program (hereinafter referred to as a "recording application") separate from the treatment application can be considered. On the other hand, even if it is possible to input patient data using a record app even after the end of the insured medical treatment period, it is inconvenient if the patient data input during the insured medical treatment period cannot be viewed using the record app. Also, even if it is possible to view patient data input during the insured medical treatment period by launching a treatment app even after the insured medical treatment period, if the treatment app must be launched in order to view it, the visibility of patient data during the insured medical treatment period and patient data after the insured medical treatment period has ended is impaired. These circumstances are also the same for treatment apps with expiration dates that are prescribed for private medical treatment or mixed medical treatment.

[0005] One embodiment of the present disclosure provides a technique for prompting transfer of patient data entered through a prescribed first app to a second app. [Means for solving the problem]

[0006] As another aspect of the present disclosure, there is provided an information processing system having one or more processors, the one or more processors outputting a notification prompting a patient to transfer first patient data, which has been prescribed for the purpose of treating a disease and which has been input through a first app installed on a patient's terminal, to a second app different from the first app.

[0007] As another aspect of the present disclosure, there is provided an information processing method in which a computer executes a process to output a notification prompting a patient to transfer first patient data, which is prescribed for the purpose of treating a disease and input through a first app installed on a patient's terminal, to a second app used to input second patient data.

[0008] As one embodiment of the present disclosure, a program is provided for causing a computer to implement a function of outputting a notification prompting a patient to transfer first patient data, which has been prescribed for the purpose of treating a disease and entered through a first app installed on a patient's terminal, to a second app used to enter second patient data. Effect of the Invention

[0009] According to one embodiment of the present disclosure, it is possible to provide a technique for prompting transfer of patient data inputted through a prescribed first application to a second application. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of an information processing system according to an embodiment. [Diagram 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a 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] 11 is a diagram illustrating an example of patient data stored in an auxiliary storage device of a record application operation server. FIG. [Diagram 5] FIG. 2 is a diagram illustrating an example of a hardware configuration of an information terminal. [Figure 6] 13 is an example of a processing sequence illustrating a processing operation from prescribing a therapeutic application to registering patient data in a therapeutic application operation server. [Figure 7] 13 is a diagram illustrating an example of a printed matter on which a prescription code is printed. FIG. [Figure 8] FIG. 13 is a diagram illustrating an example of an operation screen of a treatment application. [Figure 9] 13 is a diagram illustrating an example of a consultation screen displayed on the display of a doctor's terminal. FIG. [Figure 10] 13 is an example of a processing sequence illustrating a pre-handover process of patient data in the embodiment. [Figure 11] 13 is a diagram illustrating an example of a screen notifying the end of the insured medical treatment period displayed on the display of a patient terminal. FIG. [Figure 12] FIG. 13 is a diagram illustrating an example of a screen displayed on a display of a patient terminal. [Figure 13] 13A and 13B are diagrams illustrating an example of a usage confirmation screen and an installation recommendation screen for a recording application. [Figure 14] 13 is an example of a processing sequence illustrating a patient data handover process in the embodiment. [Figure 15] FIG. 13 is a diagram illustrating an example of a takeover consent confirmation screen. [Figure 16] 13 is a diagram illustrating an example of an operation screen of a recording application displayed on a patient terminal. FIG. [Figure 17] 13 is a diagram illustrating another example of authentication data stored in the auxiliary storage device of the treatment application operation server. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. <Embodiment> 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 embodiment. The information processing system 1 shown in Figure 1 is composed of a treatment application operation server 10, a record application operation server 20, a doctor terminal 30 operated by a doctor who prescribes the treatment application, a patient terminal 40 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 30 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 health insurance medical institution (specifically, the doctor terminal 30), 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 and the record application operation server 20. As mentioned above, therapeutic apps are apps 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. In this case, insured medical treatment includes not only face-to-face consultations but also online consultations. The treatment application in the present embodiment is an example of a first application, and the patient data input through the treatment application is an example of first patient data.

[0014] 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 insured medical treatment period. That is, the patient is allowed to input and record blood pressure values ​​and the like through the treatment app. The insured medical treatment period here is an example of a validity period.

[0015] 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 40, 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.

[0016] The patient data includes the patient's attributes (gender, date of birth, height, weight), blood pressure, activity records, mood records, physical condition records, medical examination history, treatment app operation history, record app operation history, biological characteristics, psychological characteristics, social characteristics, habits, goal achievement status, etc. However, the patient data does not need to be all of this information, and may be only a part of it. The blood pressure value is, for example, a systolic blood pressure (i.e., a maximum blood pressure value) and a diastolic blood pressure (i.e., a minimum blood pressure value). The blood pressure value is an example of information related to blood pressure. 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.

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

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

[0019] The operation history of the treatment application or the recording application is, for example, a history of operations related to start-up operations, input operations of blood pressure values, and reviews. 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.

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

[0021] The record application operation server 20 is a server that distributes the record application, authenticates patients, stores patient data input after the period of insured medical treatment has expired, and provides patient data to insured medical institutions. The recording application in the present embodiment is different from the treatment application in that it is an application that does not require approval under the Pharmaceutical and Medical Device Act. The recording application is an example of a second application. The patient data input through the recording application is an example of second patient data.

[0022] In FIG. 1, one treatment application operation server 10 and one record application operation server 20 are depicted, but multiple treatment application operation servers 10 may exist on the network N, and multiple record application operation servers 20 may exist on the network N. Furthermore, the services provided by one treatment application operation server 10 may be realized by the cooperative operation of multiple servers, and the services provided by one record application operation server 20 may be realized by the cooperative operation of multiple servers. In the present embodiment, the business entity that operates the treatment application operation server 10 is the same as the business entity that operates the record application operation server 20. However, the business entity that operates the treatment application operation server 10 and the business entity that operates the record application operation server 20 may be different.

[0023] The doctor terminal 30 refers to a terminal operated by a doctor in an insurance medical institution, etc. A plurality of doctor terminals 30 are depicted in FIG. The patient terminal 40 refers to a terminal operated by a patient who is examined or treated for hypertension. A plurality of patient terminals 40 are illustrated in FIG. For example, a desktop computer, a notebook computer, a tablet computer, or a smartphone is used as the doctor terminal 30 and the patient terminal 40. However, wearable computers such as smart glasses and a headset may also be used as the doctor terminal 30 and the patient terminal 40. The doctor terminal 30 and the patient terminal 40 are examples of information terminals connected to the network N.

[0024] 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 treatment application operation server 10, the record application operation server 20, the doctor terminal 30, and the patient terminal 40 are connected to one network N, but they may be connected via multiple networks N that are connected to each other.

[0025] <Server hardware configuration> 2 is a diagram illustrating an example of a hardware configuration of a server. The hardware configuration shown in FIG. Therefore, in the following, the medical application operation server 10 will be described as a representative example of the server.

[0026] 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, the recording 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 is composed of, for example, a patient ID, a user ID, a patient name, a prescription date, a medical institution ID, a doctor ID, a prescription code, and an insured medical treatment period (last month) of the medical treatment application.

[0030] The patient ID is an ID that identifies the patient and is notified by the health insurance medical institution when a medical treatment app is prescribed. The user ID is an ID used for managing the medical application operation server 10 and is used for authenticating the patient. The patient name is recorded when the patient name is notified by the health insurance medical institution. In the case of Figure 3, the patient name is "Tokyo Taro." The prescription date is the date on which the treatment app was prescribed. In the case of Figure 3, it is July 31, 2023.

[0031] The medical institution ID is an ID that identifies the health insurance medical institution that prescribed the therapeutic app. The doctor ID is an ID for identifying the doctor who prescribed the treatment app. The prescription code is a code that is notified to the patient to activate the treatment app. A prescription code is generated for each prescription. A prescription code has a usage period, and prescription codes that have passed the usage period will be invalidated. The usage period of a prescription code is, for example, three days after the prescription date. The insured medical treatment period (last month) of the treatment app is information that gives the 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.

[0032] 3 includes, for example, a patient ID, a user ID, a patient name, an input date and time, and a blood pressure value. As described above, the patient data 142 also includes information other than the blood pressure value, but this information is omitted in FIG. 3 due to space limitations. The patient ID 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 blood pressure values, etc., into the activated treatment app. In the case of Figure 3, the beginning of the input date and time is recorded as 6:35 a.m. 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.

[0033] Fig. 4 is a diagram for explaining an example of patient data 241 stored in the auxiliary storage device 24 (see Fig. 2) of the record application operation server 20. The patient data 241 is data input using the record application. In the case of Fig. 4, only the information of "Tokyo Taro" is illustrated, but the auxiliary storage device 24 also records data of other patients. 4 includes, for example, a patient ID, a user ID, a patient name, an input date and time, and a blood pressure value. As described above, the patient data 241 may include information other than the blood pressure value, but this information is omitted in FIG. 4 due to space limitations.

[0034] The patient ID is inherited from the treatment app, for example, when registering to start using the record app. The user ID is an ID used for managing the record application operation server 20, and is used for authenticating the patient. In the present embodiment, the user ID in FIG. 4 is the same as the user ID in FIG. 3. However, the user ID in FIG. 4 may be different from the user ID in FIG. 3. In that case, by recording two types of user IDs, it is possible to link the patient data 142 inputted through the treatment application with the patient data 241 inputted through the record application.

[0035] The patient name is registered by the patient when the patient starts using the record app, or is inherited from the treatment app. In the case of Figure 4, the patient name is "Tokyo Taro." In the case of Figure 4, the input date and time is 7:05 on February 1, 2024, which is the date after the end of the insured medical treatment period. In addition, the patient data 241 shown in FIG. 4 also records input values ​​on the night of February 1, 2024 and input values ​​on the following morning.

[0036] <Hardware configuration of information terminal> 5 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 30 will be described as a representative example of an information terminal. The doctor terminal 30 shown in Fig. 5 has a processor 31, a ROM 32 storing a BIOS and the like, a RAM 33 used as a work area for the processor 31, an auxiliary storage device 34, a communication interface 35, a display 36, and an input reception device 37. Each device is connected via a bus or other signal lines 38. The patient terminal 40 is also provided with a camera.

[0037] The communication interface 35 is an interface for communicating with other servers or terminals or with peripheral devices through the network N. The communication interface 35 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 36 is, for example, a liquid crystal display or an organic EL (Electro Luminescence) display. The input reception device 37 is, for example, a mouse or a keyboard. In addition, when the doctor terminal 30 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 36 is used as the input reception device 37. 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. 6 is an example of a processing sequence illustrating a process from prescription of a therapeutic application to registration of patient data in the therapeutic application operation server 10. Note that the symbol S in the figure indicates a step, and the symbol t indicates time. The processing sequence shown in FIG. 6 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 40 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 30 to input details of a medical examination for 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 patient ID 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 patient ID, 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 30 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 30 may notify the patient terminal 40 by email.

[0043] Fig. 7 is a diagram illustrating an example of a printed matter 50 on which a prescription code is printed. On the printed matter 50 shown in Fig. 7, a title 51, a medical record number 52, an issue date 53, a patient's name 54, a patient's gender 55, information on the health insurance medical institution 56, a prescription code 57, a QR code (registered trademark) 58, and a note 59 are printed. The expiration date is also printed on the prescription code 57. In the case of FIG. 7, the expiration date is 10:31 on August 3, 2023, three days after the date of issue. The QR code 58 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. 6). 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 40 (S112). In addition, if the therapeutic application has already been downloaded to the patient terminal 40, the processing operations of S111 and S112 are omitted.

[0045] The patient terminal 40 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 40 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 40 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. In addition, even if the two prescription codes match, if the prescription code usage 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 40 (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 40 (S117). As a result, the therapeutic app becomes available in the patient terminal 40. When the therapeutic app is in an activated state, the prescription code entered in S113 is recorded in association with the therapeutic app. The prescription code is used, for example, when transferring patient data 142 (see FIG. 3) to the record app operation server 20 (see FIG. 1). 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 46 of the patient terminal 40 (see FIG. 5).

[0048] When the therapeutic application is activated, registration of patient information in the therapeutic application operation server 10 becomes possible. Specifically, the account ID and password used for logging in are transmitted from the patient terminal 40 to the therapeutic application operation server 10 (S118), and are registered in association with the prescription code, etc. (S119). For example, the account ID and 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 40 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 40 (S121). When the input is confirmed, the input patient information is transmitted from the patient terminal 40 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 40 of the completion of the registration (S124). The completion of the registration is displayed on the display 46 of the patient terminal 40 (see FIG. 5).

[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 40 to start the therapeutic application (S131). When the therapeutic application is started, the patient terminal 40 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, 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 40 (S134). If the authentication is successful, it becomes possible to input data such as blood pressure values ​​into the patient terminal 40. If the authentication is unsuccessful, the patient terminal 40 displays an error on the display 46.

[0052] Fig. 8 is a diagram for explaining an example of an operation screen of a treatment application. In the case of Fig. 8, the patient terminal 40 is a smartphone. Moreover, the operation screen displayed on the display 46 is a screen for manual input. In the case of FIG. 8, 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 6. When the patient inputs data such as blood pressure values ​​(S135), the patient terminal 40 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. The patient data 142 registered in the therapeutic application operation server 10 can be downloaded and viewed from a doctor terminal 30 (see FIG. 1) operated by the doctor who prescribed the therapeutic application. For example, patient data that matches the patient ID and other information entered by the doctor is transmitted to the doctor terminal 30. As a result, the doctor can use information such as blood pressure values ​​at home for examinations.

[0054] FIG. 9 is a diagram for explaining an example of a medical examination screen displayed on the display 36 of the doctor terminal 30. As shown in FIG. The medical examination screen shown in FIG. 9 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 column on the examination screen shown in FIG. 9 is made up of a display column 361 for displaying changes in average blood pressure, a display column 362 for review information, a display column 363 for displaying activity records, and an end button 364.

[0055] In the case of FIG. 9, the date displayed on the consultation screen is January 21, 2024. Therefore, display field 361 displays the average blood pressure, average pulse rate, and blood pressure measurement rate calculated from patient data from 8 weeks to 4 weeks prior to the display 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 prior to the display date to the day before (from December 24th, 2023 to January 20th, 2024).

[0056] A record of mood and physical condition is displayed in a display field 362 shown in Fig. 9. A record of mood and physical condition is also called a diary. 9, 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 364 is operated, the examination screen is closed.

[0057] <Processing operations after the insurance medical treatment period of the treatment app> Here, a series of processing operations executed after the end of the insured medical treatment period of the treatment app will be described. Specifically, a notification process for prompting the transfer of patient data input through the treatment app to the record app will be described.

[0058] <Up to installing the recording app> 10 is an example of a processing sequence for explaining pre-handover processing of patient data in the embodiment. Note that the symbol S in the figure represents a step, and the symbol t represents time. The processing operation shown in FIG. 10 is an example of an information processing method.

[0059] The processing sequence shown in FIG. 10 consists of two stages. The first stage is the processing operations S151 to S155 (t51 to t54) that are executed when the medical treatment application is started just before the end of the insured medical treatment period. The second stage is the processing operations S151 to S170 (t51 to t60) that are executed when the medical treatment application is started after the end of the insured medical treatment period.

[0060] <First stage> First, the first stage will be described. The patient operates the patient terminal 40 to start the therapeutic application (S151). When the therapeutic application is started, the patient terminal 40 transmits an account ID and a password used for logging in to the therapeutic application operation server 10 (S152). The therapeutic application operation server 10 executes an authentication process using the received account ID and password (S153).

[0061] If the received account ID and password exist in the authentication data 141, the medical application operation server 10 determines that the authentication has been successful, regardless of whether the current time is within the period covered by insurance. Note that whether the current time is within the period covered by insurance is determined separately from the authentication process. The result of the authentication is transmitted from the medical treatment application operation server 10 to the patient terminal 40 (S154). As described above, in the first stage, it is assumed that the insured medical treatment period has not ended. However, it is assumed that the insured medical treatment period will end soon. In the case of this embodiment, it is assumed that the date of launching the medical treatment application is within one week (i.e., seven days) from the end date of the insured medical treatment period. In this case, the patient terminal 40 displays a notice of the end of the insured medical treatment period on the display 46 (see FIG. 5).

[0062] FIG. 11 is a diagram illustrating an example of an insured medical treatment period expiration notice screen 460 displayed on the display 46 of the patient terminal 40. As shown in FIG. The termination notice screen 460 is composed of a termination notice field 461 for the insured medical treatment period, a field 462 for recommending the use of a record application, a "Close" button 463, and a button 464 for calling up an explanation of the treatment period (i.e., the insured medical treatment period).

[0063] In the case of FIG. 11, the end notice field 461 states "The treatment period using the treatment app will end on January 31st." In addition, the end notice field 461 may display the number of days remaining until the end of the treatment period, such as "The treatment period using the treatment app will end in 3 days" or "The treatment period using the treatment app will end today."

[0064] In the case of FIG. 11, the usage recommendation field 462 states, "After you finish, you can continue recording and reviewing your blood pressure by installing a recording app (free).", and contains text encouraging the installation (implicitly downloading) of the recording app. In addition, the usage recommendation field 462 may display information such as "When the treatment period ends, this treatment app will no longer be available" or "To view blood pressure records and reviews during the treatment period after the treatment period ends, a record app (free) is required" to inform the user that the treatment app will no longer be available or to encourage the user to use the record app. The notification by the termination notice field 461 is an example of a notice of the end of the treatment period (that is, the health care period), and is also an example of a notice that prompts the transfer of patient data inputted through the treatment application to the record application. The notification by the use recommendation field 462 is a notification that recommends the use of the recording app, and is also an example of a notification that prompts the transfer of patient data inputted through the treatment app to the recording app.

[0065] <Second stage> Next, the second stage will be described. In the second stage, the processing operations from S151 to S154 are the same as those in the first stage. That is, the therapeutic application operation server 10 notifies the authentication result of the patient terminal 40. 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 has failed. As described above, the second stage assumes that the current time is after the end of the insured medical treatment period. Therefore, the medical treatment application operation server 10 determines that the period has expired and notifies the user of the expiration of the insured medical treatment period together with the authentication result.

[0066] The patient terminal 40 that receives the authentication result notifies the patient of the end of the insured medical treatment period (S156). At that time, the patient terminal 40 displays a message recommending the use of an app (i.e., a record app) different from the treatment app. FIG. 12 is a diagram for explaining an example of screens 470, 480 displayed on the display 46 of the patient terminal 40. As shown in FIG. Screen 470 is composed of a section 471 notifying the end of the insured medical treatment period, a section 472 recommending the use of a record app, a question 473 asking whether the patient wishes to use the service, a "Use" button 474, a "Do not use" button 475, and a button 476 for calling up an explanation of the treatment period (i.e., the insured medical treatment period).

[0067] In the case of FIG. 12, the end notification field 471 states "The treatment period using the treatment app has ended." In addition, the end notification field 471 may display the date on which the treatment period ended or the number of days that have passed, such as "The treatment period using the treatment app ended on January 31st" or "The treatment period using the treatment app ended three days ago." In the case of FIG. 12, the usage recommendation field 472 states, "After you finish, you can continue recording and reviewing your blood pressure by installing a recording app (free).", and contains text encouraging the installation (implicitly downloading) of the recording app.

[0068] In addition, the usage recommendation field 462 may display information such as "This app will no longer be available when the treatment period ends" or "A record app (free) is required to view blood pressure records and reviews from the treatment period after the treatment period ends," to inform the user that the treatment app will become unavailable or to encourage the user to use the record app. The end notification field 471 is an example of a notification that the treatment period (that is, the medical treatment period) has ended, and is also an example of a notification that prompts the transfer of patient data inputted through the treatment application to the record application. On the other hand, the usage recommendation field 472 is an example of a notification that encourages the use of the record application, and is also an example of a notification that encourages the transfer of patient data inputted through the treatment application to the record application.

[0069] The inquiry 473 about whether to use the application states “Do you want to use the recording application?” and prompts the user to select either a “Use” button 474 or a “Do not use” button 475 . The “Do not use” button 475 is a button for switching the display from the screen 470 to the screen 480 .

[0070] The screen 480 is composed of a screen 481 for future handling of the treatment application, an introduction 482 of the application required for viewing patient data, and a “Close” button 483. Future handling of the therapeutic app 481 states, "The therapeutic app will no longer be available, so you may uninstall it," indicating that the therapeutic app will no longer be available and that it may be uninstalled even if the user does not use the recording app. This display is an example of a notification encouraging the user to uninstall the therapeutic app.

[0071] The introduction 482 of the app required for viewing patient data states, "If you would like to view your blood pressure and review data, please use the record app," and indicates that you will not be able to view your blood pressure and review data if you do not use the record app. This display is an example of a notification encouraging the use of the record app, and is also an example of a notification encouraging the transfer of patient data entered through the treatment app to the record app. It should be noted that the “close” button 483 is a button for switching the display from the screen 480 to the screen 470 .

[0072] When the "Use" button 474 on the screen 470 is operated, the display on the patient terminal 40 switches from the screen 470 to a record application use confirmation screen 490 (see FIG. 13). Specifically, the use confirmation S157 in FIG. 10 is executed. FIG. 13 is a diagram illustrating an example of a usage confirmation screen 490 and an installation recommendation screen 500 for a recording application. The record application usage confirmation screen 490 is composed of a dedicated account registration request 491, a data transfer notice 492, an inquiry about whether to register 493, a “Register” button 494, and a “Do not register” button 495.

[0073] In the case of Fig. 13, the dedicated account registration request 491 states "A dedicated account must be registered to use the recording app," indicating that a dedicated account for the recording app must be registered. This display is an example of a notification that prompts registration of patient information that uses the recording app, and is also an example of a notification that prompts transfer of patient data entered through the treatment app to the recording app. In the case of Fig. 13, the data transfer notice 492 states "The data of the treatment app will be transferred to the registered account information," indicating that the patient data will be transferred to a dedicated account. This display is an example of a notification of the transfer destination of the patient data, and is also an example of a notification that prompts the transfer of the patient data entered through the treatment app to the record app.

[0074] The registration intention inquiry 493 states “Do you want to register a dedicated account?” and prompts the user to select either a “Register” button 494 or a “Don't Register” button 495 . Incidentally, when the "Do not register" button 495 is operated, the display of the patient terminal 40 returns to the screen 470 (see FIG. 12). When the "Register" button 494 is operated, the patient terminal 40 requests the therapeutic application operation server 10 to register a dedicated account (S158 in FIG. 10).

[0075] When the therapeutic application operation server 10 registers a new dedicated account based on the received patient information (S159), it notifies the patient terminal 40 of the completion (S160). This notification includes the user ID of the authentication data 141 of the therapeutic application (see FIG. 3). Next, the patient terminal 40 requests the therapeutic application operation server 10 to add (link) the received user ID to its own patient data 142 (see FIG. 3) (S161). The therapeutic application operation server 10 executes a process of adding the user ID (S162), and notifies the patient terminal 40 of the completion of the addition (S163).

[0076] Upon receiving this notification, the patient terminal 40 issues a notification that the record application is available (S164) and a notification that the treatment application is unavailable (S165). In the case of this embodiment, these notifications are executed as the display of an installation recommendation screen 500 (see FIG. 13). The installation recommendation screen 500 is composed of a dedicated account registration completion notification 501, a treatment app unavailability notification 502, an "Install App" button 503, and a button 504 for calling up an explanation of the treatment period (i.e., the insured medical treatment period).

[0077] In the case of Fig. 13, the registration completion notice 501 states "You can now use the recording app", indicating that registration of a dedicated account required to use the recording app has been completed. The registration completion notice 501 may display content encouraging installation (implicitly downloading) of the recording app, such as "Registration of a dedicated account has been completed. Please install the recording app" or "The recording app is ready to be installed". The registration completion notice 501 is an example of a notice encouraging installation or download of the recording app, and is also an example of a notice encouraging transfer of patient data inputted through a treatment app to the recording app.

[0078] In the case of Fig. 13, the treatment app unavailability notification 502 states "You cannot use the treatment app because the treatment period has ended", indicating that the treatment app has become unavailable. The unavailability notification 502 may display information indicating that the treatment app will become unavailable or encouraging the use of a record app, such as "Since the treatment app is unavailable, you may uninstall the treatment app" or "Since the treatment app is no longer available, you cannot view blood pressure or reviews." The unavailability notification 502 is an example of a notification encouraging the installation (or download) of a record app or a notification encouraging the use of a record app, and is also an example of a notification encouraging the transfer of patient data input through the treatment app to the record app.

[0079] When the "Install App" button 503 is operated, the patient terminal 40 accesses the URL (=Uniform Resource Locator) of the record app operation server 20 or other app store embedded in the button, and requests the record app (S166 in FIG. 10). In this embodiment, the patient terminal 40 requests a recording application from the record application operation server 20. Upon receiving the request, the record application operation server 20 performs authentication (S167) and then transmits the recording application to the patient terminal 40 that made the request (S168). The patient terminal 40 that has downloaded the recording application installs the recording application (S169), and then uninstalls the treatment application (S170). Uninstallation of the treatment app is optional.

[0080] <Patient data transfer> 14 is an example of a process sequence for explaining a patient data handover process in an embodiment. Note that the symbol S in the figure represents a step, and the symbol t represents time. The processing operation shown in FIG. 14 is an example of an information processing method. First, the patient starts up the recording application installed on the patient terminal 40 (S171). This is the first start-up after installation. When the recording application is started, a sign-in screen is displayed on the patient terminal 40 (S172).

[0081] In this embodiment, when the patient instructs to sign in (that is, requests to sign in) (S173), the patient terminal 40 transmits an account ID and password to be used for logging in to the therapeutic application operation server 10 (S174). The medical application operation server 10 performs authentication processing using the received account ID and password (S175).

[0082] 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. The result of the authentication is transmitted from the therapeutic application operation server 10 to the patient terminal 40 (S176).

[0083] If the authentication is successful, the patient terminal 40 displays a screen requesting consent to the transfer of patient data (S177). If the authentication is unsuccessful, the patient terminal 40 displays a message indicating that the authentication has failed. FIG. 15 is a diagram illustrating an example of the takeover consent confirmation screen 510. As shown in FIG. The transfer consent confirmation screen 510 shown in FIG. 15 is composed of a title "Confirm data transfer of medical application", a question 511 about whether or not to transfer, operating instructions 512, a check box 513, and a "Continue using" button 514.

[0084] In the case of Fig. 15, the handover intention inquiry 511 states "Do you want to hand over the data from the treatment application?" This display is an example of a notification that prompts the handover of patient data to the record application. In the case of Fig. 15, the operation instructions 512 state "If you wish to transfer, check 'Agree' and then click 'Continue using'", indicating the operations required for the transfer. This display is also an example of a notification that prompts the transfer of patient data to the recording app.

[0085] When the patient operates the “Continue Use” button 514 with the check box checked, the patient terminal 40 requests the therapeutic application operation server 10 to take over the patient data (S178 in FIG. 14). In this embodiment, the request includes the prescription code and the user ID. The prescription code and the user ID may be read out from the patient terminal 40 by the recording application and transmitted, or may be requested to be input by the patient.

[0086] The medical application operation server 10 identifies the handover data based on the prescription code and the user ID included in the received request (S179). The risk of making a mistake in the patient data to be handed over is significantly reduced by combining the prescription code printed when the treatment application is prescribed with the user ID included in the authentication data 141 (see FIG. 3) used to authenticate the patient. The user ID is linked to the patient data 142 (see FIG. 3).

[0087] When the handover data is specified, the medical application operation server 10 transmits the handover data (that is, the patient's own patient data during the period of insured medical treatment) to the patient terminal 40 that has requested the handover (S180). The transfer data is transmitted as a copy. Therefore, at this point, the original transfer data is stored in the treatment application operation server 10. Therefore, even if an error occurs during the transfer data transmission, the original transfer data can be retransmitted.

[0088] The patient terminal 40, which has completed receiving the handover data, transmits the handover data received from the treatment application operation server 10 to the record application operation server 20 (S181). The record application operation server 20 writes the received handover data into a dedicated storage area (that is, the second area) associated with the patient terminal 40 that is the sender of the handover data (S182).

[0089] The record application operation server 20 transmits the result of writing to the patient terminal 40 (S183). If the writing of the handover data is successful, the patient terminal 40 notifies the therapeutic application operation server 10 of the completion of the transfer (S184). If the writing of the handover data fails, the patient terminal 40 resends the handover data to the record application operation server 20. If the writing of the handover data to the record application operation server 20 fails a predetermined number of times in succession, the patient terminal 40 notifies the treatment application operation server 10 of the failure of the data transfer.

[0090] The treatment application operation server 10 that has received the transfer completion notice executes a transfer completion process (S185) and transmits the result of the process to the patient terminal 40 (S186). In the transfer completion process, for example, the patient data for which the transfer has been completed may be deleted from the treatment application operation server 10, or the patient data for which the transfer has been completed may be transferred to an area dedicated to backup. In addition, the execution of the transfer to the record application operation server 20 may be recorded as auxiliary information of the patient data, and the storage of the patient data may continue as it is. Note that the processes from S178 to S186 are executed in the background on the patient terminal 40.

[0091] The patient terminal 40, which has received the notification that the transfer process of the handover data has been completed, displays the home screen of the recording application (S187). After this, it becomes possible to input blood pressure values ​​and the like into the recording application. When the patient inputs data such as blood pressure values ​​(S188), the patient terminal 40 transmits the input patient data to the record application operation server 20 (S189). The data input in S188 is an example of the first recording of patient data using the recording application.

[0092] The record application operation server 20 writes the newly received data such as blood pressure values ​​into a dedicated storage area (i.e., a second area) linked to the patient terminal 40 that is the sender (S190). In the present embodiment, the record application operation server 20 records, for one patient, a data file of patient data taken over from the treatment application operation server 10 and a data file of patient data input via the record application separately.

[0093] It is also possible to add the patient data input through the recording application to the patient data taken over from the treatment application operation server 10. In this case, one data file is recorded in the recording application operation server 20 for one patient. In addition, in the case of the second or subsequent sign-in, S177 to S186 are not executed, and S187 to S190 are executed. In the case of this embodiment, the newly input patient data is added to the patient data previously input through the recording application.

[0094] Fig. 16 is a diagram for explaining an example of an operation screen of a recording application displayed on the patient terminal 40. In Fig. 16, parts corresponding to those in Fig. 8 are denoted by the same reference numerals. FIG. 16 shows two operation screens 520 and 530. An operation screen 520 is an example of a home screen of a recording application, and on the display 46, a field 521 for inputting blood pressure values ​​and displaying the inputted blood pressure values, and a field 522 for inputting review information are displayed. The upper row of the blood pressure value display column 521 shows the morning blood pressure value, and the lower row shows the evening blood pressure value. In the case of Fig. 16, the morning blood pressure value shows an input value, but the evening blood pressure value is left blank. Incidentally, the review information input field 522 is used to record mood and physical condition.

[0095] The operation screen 530 is an example of an input screen of the recording application, and is displayed, for example, by tapping the blood pressure value display field 521 on the home screen. The measurement date on the input screen shown in Fig. 16 is Thursday, February 1, 2024, and the blood pressure input time is 20:12. The blood pressure values ​​and the like shown on the operation screen 530 are the values ​​measured the first time, with the systolic blood pressure being 135 mmHg, the diastolic blood pressure being 85 mmHg, and the pulse rate being 70 bpm. When the operation of button 531 is accepted on operation screen 530, the recording application moves to a screen for inputting the second measurement value. On the other hand, when the operation of button 532 is accepted, the recording application closes the input screen and transmits the input blood pressure value, etc. as patient data to the recording application operation server 20 (see FIG. 14).

[0096] <Summary> After the end of the insured medical treatment period, patients will be guided to input their blood pressure values ​​through the recording app, allowing them to continue the experience of inputting their blood pressure values, which has become a habit through the prescribed treatment app. In addition, after the end of the insured medical treatment period, the patient data entered through the treatment app will be transferred to the record app, so the blood pressure values ​​entered during the insured medical treatment period and reviews can also be viewed in the record app. Of course, blood pressure values ​​entered through the record app and reviews can also be viewed. In addition, blood pressure values ​​during the insured medical treatment period and blood pressure values ​​after the end of the insured medical treatment period can be viewed not only from the patient terminal 40 but also from the doctor terminal 30 (see FIG. 1). Therefore, doctors can consider treatment plans based on the trends in blood pressure values ​​measured at home.

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

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

[0099] (3) In the above-described embodiment, an example was given of a case in which all authentication processing when the patient terminal 40 accesses the therapeutic app operation server 10 or when the patient terminal 40 accesses the record app operation server 20 is completed within the server. However, the results may be used in combination with authentication by a third party, including the business entity or telecommunications company from which the patient obtained the therapeutic app or record app.

[0100] (4) The treatment app and record app described in the above embodiment are intended to be prescribed to patients with hypertension, but may also be apps prescribed to patients suffering from other diseases. That is, the above-mentioned treatment application and record application may be applications prescribed for, for example, nicotine addiction, insomnia disorder, depression, diabetes, alcoholism, obesity, etc. Note that the information inputted into the treatment application and record application differs depending on the type of disease.

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

[0102] 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 and the record application may be capable of inputting information on a plurality of diseases.

[0103] (5) In the above-described embodiment, a notification prompting the transfer of patient data is output based on the end date of the insured medical treatment period. However, in cases where the expiration date of the treatment app is determined based on the date of hospital visits, a notification prompting the transfer of patient data may be output based on the end date of the expiration date. For example, if the usage period for a treatment app is set to the last day of the month following the hospital visit or within 30 days from the hospital visit, and use of the treatment app is restricted once the usage period has expired even before the end of the insured medical treatment period, the processing of the embodiment described above may be executed on the condition that no extension of the usage period by the doctor is recorded within a specified period from the end of the usage period. Fig. 17 is a diagram illustrating another example of the authentication data 141 stored in the auxiliary storage device 14 (see Fig. 2) of the treatment application operation server 10. In Fig. 17, parts corresponding to those in Fig. 3 are denoted by the same reference numerals.

[0104] FIG. 17 differs from the authentication data 141 shown in FIG. 3 in that the "Prescription Date" column has been changed to "Prescription Date / Consultation Date" and a column for "Expiration Month of Treatment App" has been added. In the case of Figure 17, the date on which the treatment app was prescribed to "Tokyo Taro" is July 31, 2023. Therefore, the insured medical treatment period is set to January 2024. On the other hand, the expiration month of the treatment app is recorded as August 2023. If "Tokyo Taro" does not receive his next medical examination by August 2023, he will no longer be able to use the treatment app. However, in the case of Figure 17, "Tokyo Taro" received his second medical examination on August 29, 2023. Therefore, the expiration month of the treatment app has been updated to September 2023. In this way, when the expiration date of the medical treatment app is set separately from the medical treatment period covered by insurance, a notification prompting the transfer of patient data may be output on the condition that the expiration date has expired. The expiration date here is also an example of a validity period.

[0105] (6) In the above explanation, a notification prompting the transfer of patient data is output after the end of the insured medical treatment period or the expiration date of the treatment app, which is set based on the consultation date. However, if use of the record app is started before the end of the insured medical treatment period or the expiration date, a notification prompting the transfer of patient data to the record app may be output before the end of the insured medical treatment period or the expiration date. This notification may be a notification to prompt the transfer of patient data, or a notification to prompt the use of a recording application or a notification to prompt the input of patient data into an installed recording application.

[0106] (7) In the above explanation, notifications from the server or app output around the last day of the treatment app's validity period, which is set based on the insured medical treatment period and consultation date, are used as notifications to encourage the transfer of patient data. However, notifications to encourage the transfer of patient data may also be output to the patient terminal 40 based on the doctor's instructions to the doctor terminal 30.

[0107] (8) In the above explanation, the notification from the server or app output around the last day of the treatment app’s validity period, which is set based on the insured medical treatment period and consultation date, is used as a notification to encourage the transfer of patient data. However, a viewing instruction from the doctor terminal 30 or the patient terminal 40 may be used as a trigger to output a notification to encourage the transfer of patient data. The viewing instruction here is not limited to an instruction to view pre-transfer patient data, and may be triggered by an instruction to view patient data input via the recording application, so long as the patient data is before it is transferred.

[0108] (9) In the above embodiment, the notification prompting the handover of patient data is output to the patient terminal 40, but it may be output to the doctor terminal 30. In this case, the patient can be prompted to hand over the patient data through the doctor currently examining the patient. Also, the notification prompting the handover of patient data can be output to the patient terminal 40 through the doctor's operation.

[0109] (10) In the above-described embodiment, the treatment application operation server 10 and the record application operation server 20 include both an authentication function and a patient data storage function, but the authentication function may be performed by an authentication server and the patient data storage function may be performed by a storage server. When servers are provided for each function, the above-described patient data migration process is realized by cooperation between multiple servers.

[0110] (11) In the above explanation, the processing operations executed by the server and the information terminal are explained using FIG. 6, FIG. 10, and FIG. 14, but the execution entity of each processing operation is not limited to the contents exemplified. For example, a processing operation that is executed by a server may be executed by an information terminal, and a processing operation that is executed by an information terminal may be executed by a server. Furthermore, a processing operation whose execution subject is the treatment application operation server 10 may be executed by the record application operation server 20. A processing operation whose execution subject is the doctor terminal 30 may be executed by the patient terminal 40, and a processing operation whose execution subject is the patient terminal 40 may be executed by the doctor terminal 30.

[0111] (12) In the above explanation, the insurance medical institution is assumed to be a hospital or other facility where a doctor terminal 30 that prescribes the treatment app is installed, but when a pharmacist, public health nurse, nurse, nutritionist, hospital staff, or other medical professional issues a prescription code, the insurance medical institution also includes a facility or institution where an information terminal operated by a pharmacist, public health nurse, nurse, nutritionist, hospital staff, or other medical professional is installed. In addition, the issuance of a prescription code is not limited to issuance for medical treatment, and may be issuance for uninsured treatment or mixed treatment.

[0112] (13) In the above description, the second app is a record app that does not require a prescription. However, the second app may be a treatment app that is installed on the patient terminal 40 by a prescription different from that of the first app. In addition, the second app may be a completely different app from the first app, or may be the same app as the first app. In this case, the patient data input through the previously prescribed treatment application can be prompted to be transferred to the separately prescribed treatment application.

[0113] <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 outputting a notification prompting the transfer of first patient data, which is prescribed for the purpose of treating a disease and which is input through a first app installed on a patient's terminal, to a second app used to input second patient data. This information processing system can provide a technology that prompts the transfer of patient data entered through a prescribed first app to a second app.

[0114] (((2))) The information processing system described in (((1))), wherein the processor executes the notification as a notification prompting downloading the second app to the patient's device, a notification prompting installation of the second app on the patient's device, a notification prompting registration of patient information that uses the second app, a notification prompting use of the second app, a notification prompting input of second patient data, or a notification prompting uninstallation of the first app. According to this information processing system, it is possible to realize the handover of patient data in association with the operation required of the patient.

[0115] (((3))) The information processing system according to (((1))) or (((2))), wherein the processor executes the notification as a notice of an end of a validity period of the first application or a notice that the validity period of the first application has ended. According to this information processing system, the handover of patient data can be realized in association with the validity period of the first application.

[0116] (((4))) The information processing system according to any one of (((1))) to (((3))), wherein the notification is displayed on a doctor's terminal or a patient's terminal. According to this information processing system, it is possible to prompt the doctor or the patient to take over the patient data.

[0117] (((5))) The information processing system according to any one of (((1))) to (((4))), wherein, when a predetermined operation is detected, the processor outputs a notification. According to this information processing system, it is possible to prompt the handover of patient data in association with a specific operation of the doctor or patient.

[0118] (((6))) The information processing system according to (((5))), wherein the predetermined operation is an instruction to output a notification from a doctor's terminal. This information processing system makes it possible to support the handover of patient data at the doctor's discretion.

[0119] (((7))) The information processing system according to (((5))), wherein the predetermined operation is an instruction to view the first patient data or the second patient data from the doctor's terminal or the patient's terminal. According to this information processing system, it is possible to increase the possibility that the handover of patient data will be carried out.

[0120] (((8))) The information processing system according to any one of (((1))) to (((7))), wherein the second application is an application that is not covered by the medical insurance system. With this information processing system, the second app is not subject to the restrictions of the Pharmaceuticals and Medical Devices Act, making it easier to respond to patient requests.

[0121] (((9))) An information processing method in which a computer executes a process to output a notification prompting a patient to transfer first patient data, which has been prescribed for the purpose of treating a disease and entered through a first app installed on a patient's terminal, to a second app used to enter second patient data. This information processing method can provide a technique for encouraging transfer of patient data entered through a prescribed first application to a second application. It should be noted that in this information processing method as well, it is possible to combine techniques corresponding to (((2))) to (((8))).

[0122] (((10))) A program for enabling a computer to achieve the function of outputting a notification that prompts a patient to transfer first patient data, which has been prescribed for the purpose of treating an illness and entered through a first app installed on the patient's device, to a second app used to enter second patient data. The program provides technology that facilitates the transfer of patient data entered through a first prescribed app to a second app. In this program, it is also possible to combine technologies corresponding to (((2))) to (((8)). [Explanation of symbols]

[0123] 1...information processing system, 10...treatment application operation server, 20...recording application operation server, 11, 21, 31, 41...processor, 12, 22, 32, 42...ROM, 13, 23, 33, 43...RAM, 14, 24, 34, 44...auxiliary storage device, 15, 25, 35, 45...communication interface, 16, 26, 38, 48...signal line, 30...doctor terminal, 36, 46...display, 37, 47...input reception device, 40...patient terminal

Claims

1. One or more processors; The one or more processors: An information processing system that outputs a notification prompting the transfer of first patient data, which has been prescribed for the purpose of treating a disease and entered through a first app installed on a patient's terminal, to a second app used to enter second patient data.

2. The processor executes the notification as a notification to prompt downloading the second app to the patient's terminal, a notification to prompt installation of the second app to the patient's terminal, a notification to prompt registration of patient information that uses the second app, a notification to prompt use of the second app, a notification to prompt input of the second patient data, or a notification to prompt uninstallation of the first app. The information processing system according to claim 1 .

3. The processor executes the notification as a notice of an expiration of a validity period of the first application or a notification that a validity period of the first application has expired. The information processing system according to claim 1 .

4. The notification is displayed on the doctor's terminal or the patient's terminal. The information processing system according to claim 1 .

5. When a predetermined operation is detected, the processor outputs the notification. The information processing system according to claim 1 .

6. The predetermined operation is an instruction to output the notification from a doctor's terminal.

6. The information processing system according to claim 5.

7. The predetermined operation is an instruction to view the first patient data or the second patient data from a doctor's terminal or a patient's terminal.

6. The information processing system according to claim 5.

8. The second app is an app that is not covered by the medical insurance system. The information processing system according to any one of claims 1 to 7.

9. An information processing method in which a computer executes a process to output a notification prompting the transfer of first patient data, which has been prescribed for the purpose of treating a disease and entered through a first app installed on a patient's terminal, to a second app used to enter second patient data.

10. A program for enabling a computer to realize a function of outputting a notification prompting a transfer of first patient data, which has been prescribed for the purpose of treating a disease and entered through a first app installed on a patient's terminal, to a second app used to enter second patient data.

Images