Information processing system, information processing method, and program

Abstract

To provide a system that can present a recommended hydrogen inhalation amount and inhalation results to a hydrogen inhaler user.SOLUTION: An information processing system provided herein comprises a processor configured to acquire information on at least either of the age and clinical condition of a patient, and present a medical professional with information for assisting in treatment of the patient as described in a treatment guideline regarding the disease being treated.SELECTED DRAWING: Figure 8

Description

[Technical Field]

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

[0002] Inhaling a mixture of hydrogen and oxygen gas is said to have the effects of relieving fatigue, providing relaxation, improving health, and enhancing athletic performance. In particular, it has been reported that hydrogen absorbed into the body reduces active oxygen (hydroxyl radicals), and is expected to have the effects of improving health and athletic performance. Patent Document 1 describes a hydrogen-oxygen mixed gas inhalation device. This hydrogen-oxygen mixed gas inhalation device compresses hydrogen-oxygen mixed gas with a compressor and supplies it into a pressure vessel. The user can inhale the compressed hydrogen-oxygen mixed gas, which increases the efficiency of absorption into the body. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2023-153714 Summary of the Invention [Problem to be solved by the invention]

[0004] However, users of hydrogen-oxygen mixed gas inhalation devices such as those described in Patent Document 1 have had difficulty understanding the appropriate amount of hydrogen to inhale and their own actual hydrogen inhalation amount. Because the appropriate amount of hydrogen to inhale varies depending on the purpose of inhalation and physical condition, it is necessary to provide information on the amount of hydrogen to inhale that corresponds to the purpose, physical condition, and mood.

[0005] One aspect of the present disclosure provides a system that can present the appropriate amount of hydrogen inhaled and inhalation results to a user of a hydrogen inhaler. [Means for solving the problem]

[0006] In another aspect of the present disclosure, an information processing system is provided that has a processor that acquires age, sex, and condition information of a user of a hydrogen inhalation device, and presents to the user or a person who treats or instructs the user a recommended amount of hydrogen to inhale based on the intended use of the hydrogen inhalation device.

[0007] Another aspect of the present disclosure provides an information processing method in which a computer executes a process of acquiring age, sex, purpose, and condition information of a user of a hydrogen inhalation device, and a process of presenting a recommended amount of hydrogen to be inhaled to the user or a person who treats or instructs the user.

[0008] As one aspect of the present disclosure, a program is provided for enabling a computer to acquire information on the age, sex, purpose, and condition of a user of a hydrogen inhalation device, and to present a recommended amount of hydrogen to be inhaled to the user or a person who treats or instructs the user. [Effects of the Invention]

[0009] According to one aspect of the present disclosure, a system can be provided that can present the appropriate amount of hydrogen inhaled and inhalation results to a user of a hydrogen inhaler. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of an information processing system assumed in a first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a support application operation server. [Figure 3] 10 is a diagram illustrating an example of authentication data and patient data stored in an auxiliary storage device of the assistance application operation server. FIG. [Figure 4] FIG. 2 is a diagram illustrating an example of a hardware configuration of an information terminal. [Figure 5] 10 is a processing sequence illustrating an example of processing operations from the start of use of the assistance application to the recording of patient data in the assistance application operation server. [Figure 6] FIG. 10 is a diagram illustrating an example of a printed matter on which a usage code is printed. [Figure 7] FIG. 10 is a diagram illustrating an example of an input screen of a support application. [Figure 8] 4 is an example of a flowchart illustrating a process for calculating a recommended hydrogen intake amount executed in the first embodiment. [Figure 9] 10 is a diagram illustrating an example of a screen display of a recommended amount of hydrogen inhalation in a support app. [Figure 10] FIG. 10 is a diagram illustrating an example of a screen display of the actual amount of hydrogen inhalation and the recommended amount of hydrogen inhalation in the support app. [Figure 11] FIG. 10 is a diagram illustrating an example of the configuration of an information processing system assumed in a second embodiment. [Figure 12] FIG. 11 is a diagram illustrating a display example of an input screen for user registration information in the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. <First Embodiment> In this embodiment, an application that assists in cancer treatment will be described as an example of an application that supports a hydrogen inhaler (hereinafter also referred to as a "support application"). Since the purpose of this embodiment is treatment, the hydrogen inhaler may be referred to as a patient as appropriate.

[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 support app operation server 10, a doctor terminal 20 operated by a doctor who prescribes the support app, a patient terminal 30 operated by a patient receiving cancer treatment, and a network N connecting these terminals. It is also assumed that, within an acceptable range, the doctor terminal 20 may be operated by nurses, pharmacists, public health nurses, nutritionists, hospital staff, and other medical personnel.

[0013] The assistance application operation server 10 in this embodiment is a server that distributes the assistance application, authenticates patients, stores patient data input through the assistance application, and provides patient data to medical institutions (specifically, doctor terminals 20). However, the assistance application may be distributed by an entity different from the entity that operates the assistance application operation server 10.

[0014] By using this assistance app, the patient can save data on the amount of hydrogen inhaled until the next consultation with the doctor in the assistance app operation server 10. Meanwhile, the doctor can use the patient data saved through the assistance app between the previous consultation and the current consultation to understand the patient's physical condition and decide on a treatment plan. The assistance app in this embodiment is an example of an app. Medical treatment includes not only face-to-face medical treatment but also online medical treatment.

[0015] Patient data includes patient attributes (gender, date of birth, height, weight), amount of hydrogen inhaled, activity record, mood record, physical condition record, medical examination history, operation history of the support app, biological characteristics, psychological characteristics, social characteristics, habits, goal achievement status, etc. However, patient data does not need to be all of this information; only some of it is acceptable. The amount of hydrogen inhaled is, for example, the actual value inhaled by the patient using a hydrogen inhalation device. The activity record is, for example, a usage history of the support app, a medication record, a meal record, a smoking record, a drinking record, and an exercise record. The activity record is an example of information about the activity.

[0016] The medication record includes, for example, the type and number of medications taken, and the time at which the medication was taken. The medication record is an example of information related to medication. The food record includes, for example, the contents of the food eaten and the amount of salt ingested. The food record is an example of information about food. The smoking record includes, 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 includes, for example, the date and time of drinking, the amount of alcohol consumed, and the type of alcohol consumed. The drinking record is an example of information related to drinking.

[0017] The exercise record includes, for example, records of 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 about mood. The record of physical condition is, for example, a subjective physical condition or symptom. The record of physical condition is an example of information related to physical condition. The medical history includes, for example, the treatment start date, the medical examination date, the details of the treatment, and advice. The medical history is an example of information related to medical examinations.

[0018] The operation history of the support application is, for example, a history of start-up operations, input operations for the amount of hydrogen inhaled, and review operations. Biological characteristics include, for example, whether or not the patient has other diseases, whether or not they have had any injuries during treatment, whether or not they have knee or foot pain, whether or not they have had treatment for high blood pressure, the number of years since they were diagnosed with high blood pressure, how strongly they season their food at home, and the amount of food they eat. Psychological characteristics include expectations for app support, willingness to acquire knowledge about cancer treatment, and psychological resistance such as finding restrictions imposed by treatment difficult.

[0019] 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 a heater in the changing room. Habits include, for example, exercise habits, weighing oneself, checking the calorie count on food labels, choosing low-fat foods, not consuming caffeine after 4 p.m., eating and drinking after 10 p.m., skipping breakfast, snacking, taking a bath one hour before bedtime, stretching or massaging before bedtime, and sleeping for 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.

[0020] Although only one support application operation server 10 is depicted in FIG. 1, multiple support application operation servers 10 may exist on the network N. Furthermore, the services provided by one support application operation server 10 may be realized by the cooperative operation of multiple servers.

[0021] The doctor terminal 20 refers to a terminal operated by a doctor at an insurance medical institution, etc. A plurality of doctor terminals 20 are depicted in FIG. The patient terminal 30 is a terminal operated by a patient receiving treatment. A plurality of patient terminals 30 are depicted in FIG.

[0022] The doctor terminal 20 and the patient terminal 30 may be, for example, a desktop computer, a notebook computer, a tablet computer, or a smartphone. However, wearable computers such as smart glasses or 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.

[0023] 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 support 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 multiple networks N that are interconnected.

[0024] <Server hardware configuration> FIG. 2 is a diagram illustrating an example of the hardware configuration of the support application operation server 10. As shown in FIG. 2 includes a processor 11, a ROM (Read Only Memory) 12 storing a BIOS (Basic Input Output System) and the like, 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. The devices are connected via a bus and other signal lines 16.

[0025] 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 drive or semiconductor storage. In addition to the assistance app, the auxiliary storage device 14 stores data related to authentication of patients to whom the assistance app is prescribed and patient data registered through the assistance app.

[0026] In this embodiment, the support 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 is compatible with Ethernet (registered trademark), Wi-Fi (registered trademark), mobile communication systems, and other communication standards.

[0027] <Data managed by the server> 3 is a diagram illustrating an example of authentication data 141 and patient data 142 stored in the auxiliary storage device 14 (see FIG. 2) of the assistance application operation server 10. In the case of FIG. 3, information on "Suzuki Taro" and "Yamada Hanako" is illustrated, but data on 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, an age, a sex, a purpose of using the support application, a consultation start date, a medical institution ID, a doctor ID, a usage code, and the like.

[0028] The medical record number is a number that identifies a patient who has been prescribed the support app, and is notified from the doctor terminal 20 (see FIG. 1) of the health insurance medical institution. The user ID is an ID used for managing the assistance application operation server 10 and is used for authenticating the patient. The patient name is recorded when it is notified by the health insurance medical institution. In the case of Figure 3, the patient name is "Taro Suzuki."

[0029] Age is recorded as the age of the patient. Sex is recorded as the sex of the patient. The purpose of use of the support app for the hydrogen inhaler is recorded, including cancer treatment, diabetes, health promotion, improving physical function, sleep, etc.

[0030] The consultation start date is the date on which the patient started receiving treatment at the health insurance medical institution. In this embodiment, the date and time when the information on the day on which the support app was used is referred to as the "input date and time." In the case of Figure 3, Taro Suzuki's consultation start date is February 1, 2024.

[0031] The medical institution ID is an ID that identifies the health insurance medical institution that prescribed the support app. The doctor ID is an ID that identifies the doctor who prescribed the support app. The usage code is an identification code for using the assistance app. The usage code is a code unique to each patient and is used to identify the patient using the assistance app when they start using the downloaded assistance app.

[0032] 3 includes, for example, a medical record number, a user ID, a patient name, an input date and time, a weight, a mood before inhalation, a physical condition, a mood after inhalation, an amount of hydrogen inhaled, a recommended amount of hydrogen inhaled, etc. In addition to the weight, a mood, a physical condition, and an amount of hydrogen inhaled, the patient data 142 also includes information on the patient's daily health condition, but this information is omitted from FIG. 3 due to space limitations. The medical record number and user ID here are used to associate with the authentication data 141. The patient data 142 is also an example of data used by a doctor or the like for medical treatment (hereinafter referred to as "medical treatment data"). The input date and time is the date and time when the patient inputs information about his / her physical condition, mood, etc. into the activated support app.

[0033] In the case of Figure 3, the beginning of the input date and time is recorded as 9:30 on February 1, 2024, which is the prescription start date. In the case of Figure 3, the patient's mood and physical condition are recorded as level values ​​on a five-point scale. The patient data 142 shown in FIG. 3 also records the amount of hydrogen to be inhaled and the recommended amount to be inhaled.

[0034] <Hardware configuration of information terminal> Fig. 4 is a diagram illustrating an example of the hardware configuration of an information terminal. The hardware configuration shown in Fig. 4 is common to the doctor terminal 20 and the patient terminal 30. The reference numerals in parentheses in the figure are the reference numerals of the hardware configuration of the patient terminal. 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 BIOS and other data, 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.

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

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

[0037] <Support app processing during the insured medical treatment period> Here, a series of processing operations that start with the prescription of the support application will be described. 5 is a processing sequence illustrating an example of processing operations from the start of use of the assistance application to the recording of patient data in the assistance application operation server 10. Note that the symbol S shown in the figure represents a step, and the symbol t represents time. The processing sequence shown in Figure 5 consists of three stages.

[0038] The first usage code issuing stage is the processing operations S101 to S105 (t11 to t14) related to the notification of the usage code of the support application. The second stage of application installation is processing operations S111 to S124 (t21 to t28) related to installing the assistance application in the patient terminal 30 and associating the assistance application with information identifying the patient. The third patient data recording stage is processing operations S131 to S137 (t31 to t35) related to recording of patient data in the support application operation server 10 via the support application.

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

[0040] The assistance application operation server 10, which has received the request for the usage code, issues the usage code (S103). In this embodiment, a usage code is issued for each request. The issued usage code is registered in the authentication data 141 (see FIG. 3) in association with information (e.g., a medical record number, a user ID) that identifies the patient to whom the usage code is issued. Then, the assistance application operation server 10 transmits the issued usage code to the requesting doctor terminal 20 (S104). The notified usage 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.

[0041] Fig. 6 is a diagram illustrating an example of a printed matter 40 on which a usage code is printed. The printed matter 40 shown in Fig. 6 has printed thereon a title 41, a medical record number 42, an issue date 43, a patient's name 44, a patient's gender 45, information about the medical institution 46, a usage code 47, and a QR code 48 (registered trademark). The QR code 48 (registered trademark) has usage code information embedded therein. The purpose of using the support app is displayed in purpose 49. In the example in Figure 6, "cancer treatment" is checked in purpose 49.

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

[0043] The patient terminal 30 that has received the assistance app installs the assistance app, launches the installed prescription app, and receives the usage code in that order, according to the patient's operations (S113). The assistance app cannot be used just by being installed; activation by entering the usage code is required. The patient terminal 30 transmits the input usage code to the assistance application operation server 10 (S114). The assistance application operation server 10 authenticates the patient by comparing the usage code received from the patient terminal 30 with the usage code in the authentication data 141 (see FIG. 3) (S115).

[0044] If these two usage codes match, the assistance application operation server 10 determines that the authentication is successful. On the other hand, if these two usage codes do not match, the assistance application operation server 10 determines that the authentication is unsuccessful. Even if the two usage codes match, if the usage period (that is, the period until the start of use) of the usage code has expired, the support application operation server 10 regards the authentication as a failure. The assistance application operation server 10 transmits the result of the authentication to the patient terminal 30 (S116).

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

[0046] When the assistance application is activated, patient information can be registered in the assistance application operation server 10. Specifically, the account ID and password used for logging in are transmitted from the patient terminal 30 to the assistance application operation server 10 (S118), and are registered in association with the usage 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 login is completed, the assistance application operation server 10 notifies the patient terminal 30 of the completion of the registration (S120).

[0047] 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). Once the input is confirmed, the input patient information is sent from the patient terminal 30 to the assistance application operation server 10 (S122). The assistance application operation server 10 registers the received patient information in association with the usage code etc. (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).

[0048] <Patient data recording stage> Here, the process of inputting patient data using the support app after activation will be described. First, the patient operates the patient terminal 30 to start the assistance application (S131). When the assistance application is started, the patient terminal 30 transmits an account ID and a password used for logging in to the assistance application operation server 10 (S132). The assistance application operation server 10 executes authentication processing 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 assistance 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 assistance application operation server 10 determines that the authentication is unsuccessful.

[0049] The result of the authentication is transmitted from the assistance application operation server 10 to the patient terminal 30 (S134). If the authentication is successful, it becomes possible to input data such as weight, mood, physical condition, amount of hydrogen inhaled, etc. into the patient terminal 30. If the authentication is unsuccessful, the patient terminal 30 displays an error on the display 36 (see FIG. 4).

[0050] 7 is a diagram illustrating an example of an input screen of the assistance application. In the case of FIG. 7, the patient terminal 30 is a smartphone. The operation screen displayed on the display 36 is a screen for manual input. In the case of FIG. 7, the measurement date is February 11, 2024, and the weight, mood, and physical condition were input at 8:00 p.m. The subject's weight was 65 kg, his mood before inhalation was 3 (normal), and his physical condition was 3 (normal).

[0051] Returning to the explanation of Figure 5. When the patient inputs data such as weight, mood, and physical condition (S135), the patient terminal 30 transmits the input patient data to the assistance application operation server 10 (S136). The assistance application operation server 10 registers the received data as the patient data 142 (see FIG. 3) (S137). Data such as the amount of hydrogen inhaled can be input manually by the patient, or the amount of hydrogen inhaled can be automatically input as measured by a peripheral device connected via Bluetooth, etc. The peripheral device in this case is a hydrogen inhalation device.

[0052] The patient data 142 registered in the assistance application operation server 10 can be downloaded and viewed from a doctor terminal 20 (see FIG. 1) operated by the doctor who prescribed the assistance application. For example, patient data that matches the medical record 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 the amount of hydrogen inhaled at home in his or her examination.

[0053] <Display processing of information to assist doctors in their medical treatment> FIG. 8 is an example of a flowchart illustrating the process for calculating the recommended hydrogen intake amount executed in the first embodiment. The processing operation shown in FIG. 8 is executed by the processor 11 (see FIG. 2) of the assistance application operation server 10 (see FIG. 1).

[0054] In this embodiment, the processing operation shown in Fig. 8 is started when a doctor or the like requests to view patient data through the operation of doctor terminal 20 (see Fig. 1). However, a request by a doctor or the like to view the electronic medical record may also be used as a trigger for the processing operation shown in Fig. 8. In this embodiment, a request for viewing to the assistance application operation server 10 is made, for example, at the time of a medical interview or before or after the medical interview. When requesting viewing, for example, a medical record number, a user ID, a usage code, etc. are transmitted from the doctor terminal 20 to the support application operation server 10. This information is read from, for example, an electronic medical record, etc. However, this information may also be input by a doctor, etc.

[0055] The processor 11 receives a request to view patient data and acquires the authentication data and patient data of the target patient (S201). The information on the patient's disease is identified, for example, through information that identifies the prescribed support application. Note that the support application operation server 10 may read the information from the electronic medical record, or a doctor or the like may input the disease information.

[0056] Next, the processor 11 calculates the recommended amount of hydrogen to be inhaled (S202). The calculation model or formula for the recommended amount of hydrogen to be inhaled may be set for each purpose, and may take the patient's condition parameters as input information and output the recommended amount of hydrogen to be inhaled. For example, the calculation model for the recommended amount of hydrogen to be inhaled may be a multivariate linear regression formula or a machine learning model. In the case of a multivariate linear regression equation, it may be an equation that estimates the recommended amount of hydrogen inhalation using variables such as weight, sex, mood before inhalation, physical condition, etc. Also, a trained model that estimates the amount of hydrogen inhalation can be used, in which a machine learning model is trained with a set of training data of input variables such as weight, sex, mood before inhalation, physical condition, etc. and output recommended hydrogen inhalation amounts. The recommended amount of hydrogen to be inhaled may be calculated as the total amount to be inhaled over a week, or as the amount to be inhaled per day.

[0057] Next, the processor 11 transmits data on the recommended amount of hydrogen inhalation to the patient terminal 30 (S203). The patient checks the recommended amount of hydrogen inhalation on a display screen for the recommended amount of hydrogen inhalation, as shown in Figure 9. In the example of Figure 9, the recommended amount of hydrogen inhalation for one week, the recommended amount of hydrogen inhalation per day, and the amount of inhalation recorded so far in one week are displayed.

[0058] Returning to FIG. 8, after checking the recommended hydrogen inhalation amount displayed in FIG. 9, the patient inhales the recommended daily amount of hydrogen (S204). The hydrogen inhalation device measures the amount of hydrogen inhaled, and when the recommended amount is reached, stops supplying hydrogen (S205). In this case, if the hydrogen inhalation device is not linked to the support app, the patient can manually inhale the recommended amount of hydrogen and inhale only the recommended amount. Furthermore, the hydrogen inhalation device linked to the support app records the automatic measurement result of the amount of hydrogen inhaled as the actual amount of inhalation in the auxiliary storage device 34 (see FIG. 4) or the auxiliary storage device 14 (see FIG. 1) (S206). If the hydrogen inhalation device is not linked to the support app, the patient may manually input and record the actual amount of hydrogen inhaled.

[0059] Figure 10 shows a graph of the progress of daily hydrogen inhalation over the past week and the recommended amount of hydrogen inhalation for the next week. By viewing this graph, patients can check their inhalation results to date and their future plans.

[0060] <Embodiment 2> This embodiment is a usage form of a support app that supports a user of a hydrogen inhalation device without the intervention of a doctor. Fig. 11 is a diagram illustrating an example of the configuration of an information processing system 1 assumed in embodiment 2. 11 includes a support application operation server 10, a user terminal 300 operated by a user, and a network N connecting these terminals. The second embodiment is significantly different from the system configuration of the information processing system 1 (see FIG. 1) described in the first embodiment in that the doctor terminal 20 is not included. The second embodiment is intended for purposes other than the treatment of diseases that do not require medical intervention, such as sports (improvement of motor function) and health promotion.

[0061] In the first embodiment, the use of the support app begins after a usage code is sent via a doctor, but in the second embodiment, the user can download the support app from a predetermined website and enter the registration information by themselves from the beginning.

[0062] Fig. 12 is a diagram illustrating an example of an input screen for user registration information. On the registration screen 400 of the user terminal shown in Fig. 12, a title 41, an identification number 42b, a date of use 43b, the user's name 44, the user's gender 45, information about the operating institution 46, and a purpose 49 are displayed on the user terminal 30b. In the example of FIG. 12, purpose 49 is checked as sports.

[0063] In the second embodiment, the procedure is the same as in the first embodiment in that after the support app is downloaded, the recommended hydrogen inhalation amount is displayed, and the actual inhalation amount is recorded and displayed.

[0064] <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 various modifications or improvements to the above-described embodiments are also included in the technical scope of the present disclosure.

[0065] (2) The processor in the above-described embodiments refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPUs (=Central Processing Units)) as well as dedicated processors (e.g., GPUs (=Graphical Processing Units), ASICs (=Application Specific Integrated Circuits), FPGAs (=Field Programmable Gate Arrays), programmable logic devices, etc.). Furthermore, the operations of the processors in the above-described embodiments may be performed by multiple processors working together, rather than by a single processor. The order in which the operations of the processors are performed is not limited to the order described in the above-described embodiments, and may be changed individually.

[0066] (3) In the above-described embodiment, the case where all authentication processing when the patient terminal 30 accesses the support application operation server 10 is completed within the server has been exemplified. However, the results may be used in combination with authentication by a third party, including the business entity from which the patient obtained the support application or a telecommunications carrier.

[0067] (4) The support app described in the above embodiment is intended to be prescribed to patients undergoing cancer treatment or to improve motor function, but it may also be an app used for other purposes. The information to be input into the support app varies depending on the purpose of use of the support app. The support app may allow input of information about multiple diseases.

[0068] (5) In the first embodiment, the processing operations executed by the support application operation server 10 and the doctor terminal 20 are described using FIG. 5, but the execution entities of the individual processing operations are not limited to the exemplified contents. For example, the processing operation executed by the support application operation server 10 may be executed by the doctor terminal 20 or the management system of the medical institution to which the doctor belongs. Also, the processing operation executed by the doctor terminal 20 may be executed by the management system of the medical institution to which the doctor belongs, the support application operation server 10, or another server.

[0069] (6) In the description of the first embodiment, the health insurance medical institution is assumed to be a hospital or other facility where a doctor terminal 20 that prescribes the support app is installed, but when a pharmacist, public health nurse, nurse, nutritionist, hospital staff, or other medical professional issues a usage code, the health 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. Furthermore, the issuance of a usage code is not limited to issuance for medical treatment, but may also be issuance for uninsured treatment (i.e., private treatment) or mixed treatment.

[0070] The "processor" in the claims is interpreted as a concept that includes the processor 11 of the operation server 10 and the processor 21 of the user terminal 20. The "program" in the claims may be composed of a combination of multiple program modules or multiple code segments, etc. The program may also be recorded in a distributed manner on recording media located in physically separate locations. The "processing" in the claims is executed by any computer using a processor or program. The computer may be a general-purpose computer, a dedicated computer, or a system computer. [Explanation of symbols]

[0071] 1...information processing system, 10...support 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 acceptance device, 30...patient terminal, 300...user terminal, 400...registration screen of user terminal

Claims

1. a processor; The processor: Acquire the age, sex, and condition information of the user of the hydrogen inhalation device, and present the recommended amount of hydrogen to be inhaled according to the purpose of use of the hydrogen inhalation device to the user or a person who treats or instructs the user. Information processing system.

2. The processor: As the status information, at least data on the weight, mood, and physical condition of the user is acquired. The information processing system according to claim 1 .

3. The processor: Displaying the recommended amount of hydrogen to inhale according to the purpose of treating a disease, promoting health, improving sleep, or improving physical function. The information processing system according to claim 2 .

4. The processor: Display the actual amount of hydrogen inhaled and the recommended amount of hydrogen inhaled as a time series graph. The information processing system according to claim 3 .

5. The computer A process of acquiring age, sex, purpose, and status information of a user of the hydrogen inhalation device; A process of presenting a recommended amount of hydrogen to the user or a person who treats or instructs the user; An information processing method that performs the above.

6. On the computer, A function to acquire the age, sex, purpose, and status information of the user of the hydrogen inhalation device; A function of presenting a recommended amount of hydrogen to the user or a person who treats or instructs the user; A program to achieve this.

Images