Therapeutic application management system and therapeutic application program

Abstract

This therapeutic application management system is provided with a therapeutic application (1) installed in a patient terminal (10) and a management server (30) that issues an ID, and the management server (30) is provided with a medical institution ID issuing unit (31) that issues a medical institution ID that identifies a medical institution that has issued a prescription for the therapeutic application (1). A therapeutic application (1) is provided with an application setting unit (12) that sets a medical institution ID as information for bringing the therapeutic application (1) into a usable state. By using a medical institution ID, which does not include information relating to a patient, as the ID required to start the use of the therapeutic application (1), the medical institution ID can be issued by the management server (30), and a medical practitioner of a medical institution that diagnoses a patient and issues a prescription for the therapeutic application (1) does not need to perform any input work for issuing the ID.

Description

Technical Field

[0001] The present invention relates to a therapeutic application management system and a therapeutic application program, and is particularly suitable for a system that performs processing related to starting to use a therapeutic application installed in a patient terminal. Background Art

[0002] In recent years, the development of applications for the purpose of treating diseases (hereinafter referred to as "therapeutic applications") has been promoted. For example, there are known therapeutic applications for the purpose of treating diseases such as sleep disorders by improving the patient's lifestyle (for example, refer to non-patent document 1). In addition, there are also known therapeutic applications for the purpose of treating nicotine dependence by quitting smoking. Most therapeutic applications are installed on smartphones for use.

[0003] General smartphone applications can be freely downloaded from a specified download website (so-called app store) and installed on a smartphone for use. In contrast, therapeutic applications are medical devices (medical software), so not everyone can use them freely. In order to use therapeutic applications, the patient needs to provide an ID and password when the doctor determines that the application is necessary and prescribes it.

[0004] In the past, medical institutions issued such IDs and passwords. In medical institutions, patient information is input from a terminal to issue a patient ID and password, the patient information and patient ID are recorded in a QR code, and the QR code and password are handed over to the patient in the form of data or paper media. However, when medical institutions have to issue a patient ID and password for treatment applications to each patient, it is a heavy burden on medical practitioners.

[0005] In this regard, there is known a system that automatically issues a treatment application ID and password in response to a request from a treatment application installed in a user terminal, without requiring a doctor who diagnoses a patient to perform computer operations for issuing a user ID and password (see, for example, Patent Document 1).

[0006] In the system described in Patent Document 1, when a patient who has installed a therapeutic application in a user terminal makes a code display request from a management screen displayed in a medical institution terminal located in a lobby or consulting room of a medical institution after receiving a diagnosis from a doctor, the management server that receives the request from the medical institution terminal issues a user ID and password, generates a two-dimensional code image recording this information, and displays it on the medical institution terminal. When the user who made the code display request reads the two-dimensional code image displayed in the medical institution terminal through the function of the therapeutic application, a system registration request is sent from the therapeutic application to the management server, the therapeutic application that sent the request is registered as a regular application, and the functional restrictions of the therapeutic application are lifted. Thereafter, the therapeutic application can be used without functional restrictions by logging in using the user ID and password.

[0007] However, the system described in Patent Document 1 requires a special mechanism for limiting some functions of the therapeutic application until the user ID and password are registered, and a therapeutic application without such a function limiting mechanism cannot be used.

[0008] In addition, there is also known a system in which a treatment application is made available by reading a predetermined activation code (two-dimensional code) using a smartphone (see, for example, Patent Documents 2 and 3).

[0009] In the system described in Patent Document 2, when the result of the medical examination is to decide to use a medical application, the doctor or a person who has received the doctor's instruction issues a prescription (including an activation code generated by forming a barcode or a QR code) via a system such as an electronic medical record. The patient who has received the prescription downloads and installs the medical application on the patient's terminal, starts the medical application, and uses the terminal's barcode reader function to read the activation code, thereby making the medical application usable.

[0010] In the system described in Patent Document 3, a server receives a request for an activation code for executing a therapeutic application from an information processing terminal of a patient who is a treatment target of the therapeutic application, generates an activation code based on initial information related to the patient's treatment disease input in advance by a medical practitioner, and transmits the activation code to the patient's information processing terminal. The patient's information processing terminal uses the activation code received from the server to execute the therapeutic application in a state where the initial information is applied.

[0011] However, in the system described in Patent Document 2, a doctor or a person who has received a doctor's instruction needs to issue an activation code recording various information via an electronic medical record system. In addition, in the system described in Patent Document 3, as a prerequisite for issuing an activation code for executing a therapeutic application, a medical practitioner needs to input initial information related to the patient's treatment disease in advance and register it in a server. Therefore, in either of the systems of Patent Documents 2 and 3, the burden on medical practitioners is very large.

[0012] Prior art literature

[0013] Patent Literature

[0014] Patent Document 1: Japanese Patent No. 6611112

[0015] Patent Document 2: Japanese Patent Application Publication No. 2022-80050

[0016] Patent Document 3: Japanese Patent Application Publication No. 2022-70086

[0017] Non-patent literature

[0018] Non-patent document 1: Website “Yawn improves insomnia and recovers 15 trillion yen in economic losses”, retrieved on September 12, 2022, URL 〈https: / / alldtx.com / product-best / mentalhealth-best-product-pickup-best / yawn-susmed / 〉 Summary of the invention

[0019] The present invention has been made to solve such a problem, and an object of the present invention is to enable therapeutic applications to be usable without placing a large burden on medical practitioners.

[0020] In order to solve the above-mentioned problem, in the present invention, the management server issues a medical institution ID for identifying the medical institution that prescribes the therapeutic application as the ID required to start using the therapeutic application installed on the patient terminal. The therapeutic application obtains the medical institution ID issued by the management server and sets the medical institution ID in the therapeutic application as information for making the therapeutic application usable.

[0021] (Effects of the Invention)

[0022] According to the present invention constructed as described above, the ID required to start using the therapeutic application is a medical institution ID predetermined for each medical institution, and does not include information related to the patient. Therefore, the medical practitioner of the medical institution who diagnoses the patient and prescribes the therapeutic application does not need to perform any input operation to make the therapeutic application available for use, and can make settings for making the therapeutic application available for use by setting the medical institution ID issued by the management server to the therapeutic application. In this way, according to the present invention, the therapeutic application can be made available for use without placing a large burden on the medical practitioners of the medical institution. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 It is a schematic diagram of an overall configuration example of the therapeutic application management system involved in this embodiment.

[0024] Figure 2 This is a block diagram showing an example of the functional configuration of the treatment application management system according to the present embodiment.

[0025] Figure 3 This is a block diagram showing an example of the functional configuration of the treatment application management system according to the present embodiment.

[0026] Figure 4 This is a flowchart showing an example of the operation of the therapeutic application management system according to the present embodiment.

[0027] Figure 5 This is a flowchart showing an example of the operation of the therapeutic application management system according to the present embodiment.

[0028] (Explanation of symbols)

[0029] 1: Therapeutic applications

[0030] 10: Patient terminal

[0031] 11: Medical institution ID acquisition department

[0032] 12: Application settings

[0033] 13: Login information registration request section

[0034] 14: Patient information sending department

[0035] 20: Medical institution terminal

[0036] 21: Code storage unit

[0037] 22: Code provision department

[0038] 30: Management Server

[0039] 31: Medical institution ID issuance department

[0040] 32: Login information registration department

[0041] 33: Patient Information Management Department

[0042] 40: Code distribution server

[0043] 41: Code information generation unit DETAILED DESCRIPTION

[0044] Hereinafter, one embodiment of the present invention will be described with reference to the drawings. Figure 1 FIG. 2 is a schematic diagram of an overall configuration example of the therapeutic application management system according to the present embodiment. Figure 1 As shown, the medical application management system of this embodiment is configured to include a plurality of patient terminals 10 -1 , 10 -2 , ... (hereinafter referred to as "patient terminal 10" when not particularly distinguished), a plurality of medical institution terminals 20 -1 , 20 -2 , ... (hereinafter referred to as "medical institution terminal 20" when not particularly distinguished), management server 30 and code issuing server 40. The patient terminal 10, medical institution terminal 20, management server 30 and code issuing server 40 are configured to be connectable via a communication network 50 such as the Internet or a mobile phone network.

[0045] Multiple patient terminals 10 -1 , 10 -2 , ... are terminals used by each patient to install a treatment application to treat a disease, and are composed of, for example, a smartphone, a tablet, or a personal computer. A plurality of medical institution terminals 20 -1 , 20 -2 , ... are terminals used in various medical institutions to diagnose patients and prescribe therapeutic applications, and are composed of, for example, smartphones, tablet computers, personal computers, or dedicated medical terminals.

[0046] The management server 30 and the code issuing server 40 perform processing related to starting to use the therapeutic application installed in the patient terminal 10. Here, the management server 30 is, for example, a server operated by a business operator that provides the therapeutic application, and issues a medical institution ID required to start using the therapeutic application. After the therapeutic application starts to be used, the management server 30 cooperates with the therapeutic application and the medical institution terminal 20 to perform processing related to treatment using the therapeutic application.

[0047] In addition, the code issuing server 40 generates code information including the medical institution ID issued by the management server 30, and provides it to the medical institution terminal 20. The code issuing server 40 may be, for example, a server operated by a business operator that provides a therapeutic application, or a server operated by another business operator. In addition, it is also possible to configure the management server 30 and the code issuing server 40 to be independent of each other, and to have the medical institution ID issuing unit 31 and the code information generating unit 41 in the management server 30.

[0048] Figure 2 and Figure 3 This is a block diagram showing an example of the functional configuration of the treatment application management system according to the present embodiment. Figure 2 The functional configuration related to the process up to setting the medical institution ID in the treatment application is shown. Figure 3 This section shows the functional configuration related to the processing after the medical institution ID is set in the treatment application.

[0049] like Figure 2 As shown, as a functional configuration associated with the process until the medical institution ID is set in the treatment application 1, the treatment application 1 of the patient terminal 10 includes a medical institution ID acquisition unit 11 and an application setting unit 12, the medical institution terminal 20 includes a code storage unit 21 and a code providing unit 22, the management server 30 includes a medical institution ID issuing unit 31, and the code issuing server 40 includes a code information generating unit 41. In addition to the treatment application 1, a code reading application 2 (equivalent to the code reading unit in the claims) is also stored in the patient terminal 10. In addition, the treatment application 1 may also include a code reading unit.

[0050] In addition, if Figure 3 As shown, as functional configurations related to processing after the medical institution ID is set in the treatment application 1, the treatment application 1 includes a login information registration request unit 13 and a patient information sending unit 14, and the management server 30 includes a login information registration unit 32 and a patient information management unit 33.

[0051] Figure 2 and Figure 3The functional blocks shown can also be constituted by any one of hardware, DSP (Digital Signal Processor), and software. For example, in the case of being constituted by software, the functional blocks are actually constituted by a CPU, RAM, ROM, etc. of a computer respectively built into the patient terminal 10, the medical institution terminal 20, the management server 30, and the code issuing server 40, and are realized by the operation of a program stored in a storage medium such as RAM, ROM, a hard disk or a semiconductor memory. In particular, the functional configuration of the therapeutic application 1 is realized by the operation of the therapeutic application program installed in the patient terminal 10.

[0052] exist Figure 2 In the embodiment, the medical institution ID issuing unit 31 of the management server 30 issues a medical institution ID for identifying each medical institution, and provides the issued medical institution ID to the code issuing server 40. In the present embodiment, the medical institution ID issuing unit 31 issues a plurality of medical institution IDs corresponding to a plurality of medical institutions, regardless of whether the medical institution prescribes the therapeutic application 1 to the patient, and provides the plurality of medical institution IDs to the code issuing server 40.

[0053] Here, “issuing regardless of whether the medical institution prescribes the therapeutic application 1 to the patient” means issuing in advance before the medical institution prescribes the therapeutic application 1 to the patient. For example, when the information of the medical institution that has decided to introduce the therapeutic application 1 is first registered in the management server 30, the medical institution ID issuing unit 31 issues a medical institution ID for identifying the registered medical institution and provides it to the code issuing server 40. Every time the information of a medical institution is registered in the management server 30, the medical institution ID issuing unit 31 issues a medical institution ID.

[0054] The code information generating unit 41 of the code issuing server 40 generates code information recording the medical institution ID, and provides the generated code information to the medical institution terminal 20 of the medical institution corresponding to the medical institution ID. The code information does not include both the login information and the patient initial information described later. The code information is, for example, a two-dimensional code such as a QR code (registered trademark). Alternatively, the code information may be a barcode or other computer-readable code.

[0055] In the present embodiment, the code information generating unit 41 generates a plurality of code information recording the corresponding medical institution ID for each of a plurality of medical institutions, regardless of whether the medical institution prescribes the therapeutic application 1 to the patient, and provides the plurality of medical institution terminals 20. For example, as described above, whenever the information of a medical institution is registered in the management server 30 and the medical institution ID of the medical institution is provided from the management server 30 to the code issuing server 40, the code information generating unit 41 generates code information including the provided medical institution ID, and provides the generated code information to the corresponding medical institution terminal 20.

[0056] The method of providing the code information is arbitrary. For example, the code information generation unit 41 can send the code information to the medical institution terminal 20 via the communication network 50. In addition, the code information generation unit 41 may record the code information in a removable storage medium, and the administrator may distribute the removable storage medium to the medical institution terminal 20. Alternatively, the code information generation unit 41 may provide the code information to the medical institution terminal 20 via a website for data transfer managed by the management server 30 or the code issuing server 40.

[0057] The code storage unit 21 of the medical institution terminal 20 acquires and stores the code information provided from the code issuing server 40. The code storage unit 21 stores the code information recording the medical institution ID of the medical institution (in advance before the medical institution prescribes the therapeutic application 1 to the patient), regardless of whether the medical institution prescribes the therapeutic application 1 to the patient.

[0058] The code providing unit 22 provides the code information stored in the code storage unit 21 to the patient terminal 10. The code information is provided to the patient terminal 10 after the medical institution prescribes the therapeutic application 1 to the patient. For example, when a medical practitioner operates the medical institution terminal 20 to instruct to provide the code information, the code providing unit 22 receives the instruction, reads the code information from the code storage unit 21, and provides it to the patient terminal 10.

[0059] The method of providing the code information is arbitrary. For example, the code information can be provided by displaying the code information on the display device of the medical institution terminal 20 by the code providing unit 22, and reading the code information using the code reading application 2 of the patient terminal 10. The code providing unit 22 can also replace the display device that displays the code information on the medical institution terminal 20, and print the code information on a paper medium by a printing device connected to the medical institution terminal 20. In this case, the code information is provided by reading the code information recorded on the paper medium using the code reading application 2 of the patient terminal 10. In addition, the code information can also be provided by recording the code information in a removable storage medium by the code providing unit 22, and reading the code information from the removable storage medium by the patient terminal 10. Alternatively, the code providing unit 22 can also provide the code information to the patient terminal 10 via a website for data transfer managed by the management server 30.

[0060] The medical institution ID acquisition unit 11 of the treatment application 1 acquires the medical institution ID issued by the medical institution ID issuance unit 31 of the management server 30. For example, in a case where the code information is provided from the medical institution terminal 20 to the patient terminal 10 by reading the code information using the code reading application 2, the medical institution ID acquisition unit 11 acquires the medical institution ID obtained by reading the code information and deciphering it from the code reading application 2. In a case where the code information is provided from the medical institution terminal 20 to the patient terminal 10 via a removable storage medium or a website for data transfer, the medical institution ID acquisition unit 11 acquires the medical institution ID by deciphering the provided code information.

[0061] The application setting unit 12 sets the medical institution ID acquired by the medical institution ID acquisition unit 11 in the treatment application 1 as information for making the treatment application 1 usable. Making the treatment application 1 usable means that the treatment application 1 can perform treatment-related processing in cooperation with the medical institution terminal 20 via the management server 30.

[0062] That is, after the patient starts using the therapeutic application 1, it is necessary to register various information related to the treatment (information indicating the current symptoms and the implementation status of the therapeutic application 1, etc.) from the therapeutic application 1 to the management server 30, and make such information viewable from the medical institution terminal 20, and only from the medical institution terminal 20 associated with the therapeutic application 1. The medical institution ID is used in the association between the therapeutic application 1 and the medical institution terminal 20. Therefore, the therapeutic application 1 is in a state where it cannot be used before the medical institution ID is set in the therapeutic application 1. The medical institution ID is information that needs to be set in the therapeutic application 1 when the therapeutic application 1 starts to be used.

[0063] exist Figure 3 In the example, the login information registration request unit 13 of the treatment application 1 makes a login information registration request to the management server 30, which becomes executable because the medical institution ID is set by the application setting unit 12. For example, the login information registration request unit 13 displays a login information registration screen on the display device of the patient terminal 10, for example, with the completion of setting of the medical institution ID as a trigger, and urges the patient to register the login information. In addition, it can also be configured so that the patient can manually display the registration screen and request to register the login information at any time after the setting of the medical institution ID is completed.

[0064] In the present embodiment, it is designed that when the patient actually uses the therapeutic application 1, it is necessary to log in to the therapeutic application 1. The patient's user ID and password are used for this login. The user ID is, for example, the email address of the patient terminal 10. When the patient inputs the user ID and password by operating the registration screen, the login information registration request unit 13 sends the input user ID and password and the medical institution ID acquired by the medical institution ID acquisition unit 11 to the management server 30 to request registration of the login information.

[0065] The login information registration unit 32 of the management server 30 registers the login information used by the patient when logging into the treatment application 1 in the management server 30 according to the login information registration request sent from the treatment application 1. During the registration, the login information registration unit 32 registers the user ID and the medical institution ID sent from the treatment application 1 together with the login information in association with each other. As described above, in the present embodiment, the mechanism is such that if the medical institution ID is not set in the treatment application 1, the login information cannot be registered in the management server 30.

[0066] After registering the login information to the management server 30 according to the login information registration request of the login information registration request unit 13, the patient information sending unit 14 of the therapeutic application 1 accepts the input of the patient's initial information to be set when starting to use the therapeutic application 1 for treatment, and sends the input patient initial information to the management server 30.

[0067] For example, the patient information sending unit 14 displays the input screen of the patient initial information on the display device of the patient terminal 10, for example, triggered by the registration completion notification of the login information received from the management server 30, and urges the patient to enter the patient initial information. The patient initial information includes, for example, the registration number, name, gender, date of birth, other diseases under treatment (concurrent diseases), and information related to the disease treated by the therapeutic application 1 (current symptoms, etc.). When the patient enters the patient initial information by operating the input screen, the patient information sending unit 14 sends the input patient initial information to the management server 30. In addition, the patient can manually display the input screen and enter the patient initial information at any time after the registration of the login information is completed.

[0068] The patient information management unit 33 stores the initial patient information sent from the treatment application 1 in a storage medium, and manages the information in a state that the information can be viewed from the medical institution terminal 20 associated with the treatment application 1 through the medical institution ID. That is, when the medical institution terminal 20 accesses the management server 30 using the medical institution ID, the patient information management unit 33 provides the initial patient information registered in association with the user ID associated with the medical institution ID to the medical institution terminal 20 in a state that the information can be viewed.

[0069] The patient information management unit 33 not only provides the medical institution terminal 20 with the patient's initial information, but also provides the medical institution terminal 20 with various information related to treatment that is successively registered from the treatment application 1 to the management server 30 after the treatment application 1 is started. By viewing the information related to treatment, medical practitioners can understand the patient's disease and treatment status (how the values ​​change, whether the treatment application 1 is continued, etc.), and can contact the patient as needed. In addition, the patient information management unit 33 does not provide the user ID (email address) and password to the medical institution terminal 20.

[0070] The patient information management unit 33 may manage the patient initial information sent from the therapeutic application 1 in a state that can be edited from the medical institution terminal 20 associated with the therapeutic application 1 through the medical institution ID. For example, when a medical practitioner who has viewed the patient initial information registered in the management server 30 compares it with the storage or medical record information at the time of diagnosis or prescribing the therapeutic application 1 and recognizes an input error, the medical practitioner can correct it to the correct information. In addition, when a medical practitioner compares it with the storage or medical record information at the time of diagnosis or the input information of other patients and recognizes that there is an input omission, the medical practitioner can add the input information.

[0071] The patient information management unit 33 may manage not only the initial patient information but also various information related to treatment that is successively registered from the treatment application 1 to the management server 30 after the treatment application 1 is started to be used, in a state that the information can be edited from the medical institution terminal 20 associated with the treatment application 1 by the medical institution ID. For example, when the information sent from the treatment application 1 and registered to the management server 30 is compared with the medical record information used by the medical practitioner in daily diagnosis and treatment and an input error or input omission is recognized, the medical practitioner can edit the information.

[0072] Figure 4 and Figure 5 1 is a flowchart showing an operation example of the therapeutic application management system according to the present embodiment configured as described above. Figure 4 represents the processing until the code information is stored in the medical institution terminal 20, Figure 5 This shows the process after the medical institution prescribes the therapeutic application 1 to the patient.

[0073] exist Figure 4 In the present invention, first, the medical institution ID issuing unit 31 of the management server 30 determines whether the information of the medical institution that has decided to introduce the therapeutic application 1 has been registered in the management server 30 (step S1). Here, the determination of step S1 is repeated at a predetermined time interval until the information of the medical institution is registered in the management server 30. When the information of the medical institution is registered in the management server 30, the medical institution ID issuing unit 31 issues a medical institution ID for identifying the medical institution, and provides the issued medical institution ID to the code issuing server 40 (step S2).

[0074] The code information generating unit 41 of the code issuing server 40 generates code information recording the medical institution ID provided by the management server 30, and provides the generated code information to the medical institution terminal 20 of the medical institution corresponding to the medical institution ID (step S3). The code storage unit 21 of the medical institution terminal 20 acquires and stores the code information provided by the code issuing server 40 (step S4). Figure 4 The process of the flowchart shown.

[0075] exist Figure 5 In the present invention, first, the code providing unit 22 of the medical institution terminal 20 determines whether the medical practitioner who has prescribed the therapeutic application 1 has performed an operation of instructing the medical institution terminal 20 to provide code information (step S11). If the instruction is performed, the code providing unit 22 provides the code information stored in the code storage unit 21 to the patient terminal 10 of the patient who has been prescribed the therapeutic application 1 (step S12).

[0076] In the patient terminal 10, the medical institution ID acquisition unit 11 of the treatment application 1 acquires the medical institution ID obtained by reading the code information and deciphering it from the code reading application 2 (step S13). Then, the application setting unit 12 sets the medical institution ID acquired by the medical institution ID acquisition unit 11 in the treatment application 1 as information for making the treatment application 1 usable (step S14).

[0077] Next, the login information registration request unit 13 displays the login information registration screen on the patient terminal 10, and sends the user ID and password input through the registration screen and the medical institution ID acquired by the medical institution ID acquisition unit 11 to the management server 30 to request registration of the login information (step S15). The login information registration unit 32 of the management server 30 associates the login information with the medical institution ID and registers it in the management server 30 in accordance with the login information registration request sent from the treatment application 1 (step S16).

[0078] Then, the patient information sending unit 14 of the therapeutic application 1 displays the input screen of the patient's initial information on the patient terminal 10, triggered by the registration completion notification of the login information received from the management server 30, and sends the initial patient information input through the input screen to the management server 30 (step S17). The patient information management unit 33 of the management server 30 stores the initial patient information sent from the therapeutic application 1 in a storage medium, and manages it in a state that it can be viewed and edited from the medical institution terminal 20 associated with the therapeutic application 1 through the medical institution ID (step S18). The above is completed. Figure 5 The process of the flowchart shown.

[0079] As described in detail above, in this embodiment, the management server 30 issues the medical institution ID (the ID that identifies the medical institution that has prescribed the therapeutic application) required to start using the therapeutic application 1 installed on the patient terminal 10, and obtains and sets the medical institution ID in the therapeutic application 1, thereby making the therapeutic application 1 usable.

[0080] In addition, in the present embodiment, after the medical institution ID is set in the treatment application 1, the login information registration request is made from the treatment application 1 to the management server 30, thereby registering the login information. In addition, in the present embodiment, after the login information is registered, the patient initial information is sent from the treatment application 1 to the management server 30 and registered.

[0081] In the present embodiment constructed as described above, the information for making the therapeutic application 1 usable is a medical institution ID predetermined for each medical institution, and does not include login information or information related to the patient. Therefore, the following mechanism is provided: the medical practitioner of the medical institution does not need to perform any input operation for issuing the ID, and the medical institution ID can be issued by the management server 30. In addition, it is also possible to provide the medical institution ID to the medical institution terminal 20 in advance before the medical practitioner diagnoses the patient and prescribes the therapeutic application 1. Then, after prescribing the therapeutic application 1, the patient sets the medical institution ID provided by the medical institution to the therapeutic application 1, thereby making it possible to make settings for making the therapeutic application 1 usable. Furthermore, the login information and the patient's initial information are input by the patient from the therapeutic application 1 after the medical institution ID is set to the therapeutic application 1 and registered in the management server 30. Therefore, it is also unnecessary for the medical practitioner of the medical institution to perform the registration operation of the login information and the patient's initial information in order to actually make the therapeutic application 1 usable. As described above, according to the present embodiment, the patient can make the therapeutic application 1 available for use without placing a large burden on medical practitioners in a medical institution.

[0082] In addition, in the above-mentioned embodiment, the management server 30 is a server operated by a business operator providing the therapeutic application 1, and the management server 30 has a configuration of functional components 31 to 33, but the present invention is not limited to this. For example, it can also be configured to have a first management server and a second management server, the business operator providing the therapeutic application 1 operates the second management server, and the first management server is operated by another business operator, wherein the first management server has a medical institution ID issuing unit 31 and issues a medical institution ID, and the second management server has a login information registration unit 32 and a patient information management unit 33 and performs processing related to the treatment using the therapeutic application 1. Furthermore, it can also be configured that the first management server has a code information generating unit 41 in addition to the medical institution ID issuing unit 31. In this case, the first management server can also be a plurality of servers operated by each medical institution. Even if it is configured to issue a medical institution ID using a management server operated by a medical institution, medical practitioners of the medical institution do not need to perform any input operations in order to issue the ID.

[0083] In addition, in the above embodiment, an example is described in which a code issuing server 40 is provided to encode a medical institution ID and provide it to the medical institution terminal 20, but the present invention is not limited to this. That is, the medical institution ID issued by the medical institution ID issuing unit 31 may be provided to the medical institution terminal 20, and the medical institution ID may be provided from the medical institution terminal 20 to the treatment application 1 of the patient terminal 10.

[0084] In addition, in the above-mentioned embodiment, the configuration of logging in the treatment application 1 using the login information registered in the management server 30 is described, but it is not necessary to log in the treatment application 1. In this case, for example, it is conceivable to provide an application ID sending unit instead of the login information registration request unit 13, and instead of registering the user ID and the medical institution ID in association with each other in the management server 30, the application ID identifying the prescription for the treatment application 1 is registered in association with the medical institution ID in the management server 30. In addition, in this case, after the treatment application 1 becomes available due to the setting of the medical institution ID by the application setting unit 12, the patient information sending unit 14 receives the input of the patient initial information to be set when starting treatment using the treatment application 1, and sends the input patient initial information to the management server 30.

[0085] In addition, in the above embodiment, an example is described in which a medical institution ID is issued and code information is stored in the medical institution terminal 20 regardless of whether the medical institution prescribes the therapeutic application 1 to the patient (before the medical institution prescribes the therapeutic application 1 to the patient), but the present invention is not limited to this. For example, when the medical institution prescribes the therapeutic application 1 to the patient, an ID issuance request may be sent from the medical institution terminal 20 to the management server 30 to issue the medical institution ID.

[0086] In addition, the above-mentioned embodiments are merely examples of specific implementations of the present invention, and should not be interpreted as limiting the technical scope of the present invention. That is, the present invention can be implemented in various forms without departing from the gist or main features thereof.

Claims

1. A therapeutic application management system that performs processing related to starting to use a therapeutic application installed on a patient terminal for use, the therapeutic application management system being characterized by comprising: The therapeutic application is installed on the patient terminal; and The management server issues an ID required to start using the treatment application. The management server includes a medical institution ID issuing unit that issues a medical institution ID for identifying a medical institution that prescribes the therapeutic application. The therapeutic application comprises: a medical institution ID acquisition unit that acquires the medical institution ID issued by the medical institution ID issuance unit; and The application setting unit sets the medical institution ID acquired by the medical institution ID acquisition unit as information for making the treatment application available.

2. The therapeutic application management system according to claim 1, characterized in that: The treatment application further includes a login information registration request unit that makes a login information registration request executable by setting the medical institution ID in the application setting unit to the management server. The management server further includes a login information registration unit configured to register login information used when a patient using the therapeutic application logs into the therapeutic application in response to the login information registration request transmitted from the therapeutic application.

3. The therapeutic application management system according to claim 2, characterized in that: The management server has: A first management server including the medical institution ID issuing unit; and The second management server includes the login information registration unit.

4. The therapeutic application management system according to claim 1, characterized in that: The treatment application further includes a patient information sending unit, which, after the medical institution ID is set by the application setting unit, receives input of initial patient information to be set when starting treatment using the treatment application, and sends the input initial patient information to the management server. The management server further includes a patient information management unit that manages the patient original information transmitted from the treatment application in a state where the patient original information can be viewed from a medical institution terminal used in the medical institution.

5. The therapeutic application management system according to claim 2, characterized in that: The therapeutic application further includes a patient information sending unit, which receives input of initial patient information to be set when starting treatment using the therapeutic application after the login information is registered by the login information registration unit, and sends the input initial patient information to the management server. The management server further includes a patient information management unit that manages the patient original information transmitted from the treatment application in a state where the patient original information can be viewed from a medical institution terminal used in the medical institution.

6. The therapeutic application management system according to claim 4 or 5, characterized in that: The patient information management unit manages the patient initial information transmitted from the treatment application in a state where the information can be edited from the medical institution terminal.

7. The therapeutic application management system according to claim 2, characterized in that: The therapeutic application further includes a patient information sending unit, which receives input of initial patient information to be set when starting treatment using the therapeutic application after the login information is registered by the login information registration unit, and sends the input initial patient information to the management server. The management server further includes a patient information management unit that manages the patient initial information transmitted from the treatment application in a state where the patient initial information can be viewed from a medical institution terminal used in the medical institution. The management server or the code issuing server receiving the medical institution ID from the management server includes a code information generating unit, which generates code information that does not include both the login information and the patient initial information but includes the medical institution ID. The medical institution ID acquisition unit of the patient terminal acquires the medical institution ID obtained by reading and deciphering the code information through a code reading unit of the patient terminal.

8. The therapeutic application management system according to any one of claims 1 to 5, characterized in that: The management server or the code issuing server receiving the medical institution ID from the management server has a code information generating unit, which generates code information including the medical institution ID and provides the generated code information to a medical institution terminal used in the medical institution. The medical institution ID acquisition unit of the patient terminal acquires the medical institution ID decoded by reading the code information displayed on the display device of the medical institution terminal using the code reading unit of the patient terminal.

9. The therapeutic application management system according to any one of claims 1 to 5, characterized in that: The medical institution ID issuing unit issues a plurality of medical institution IDs corresponding to a plurality of medical institutions regardless of whether the medical institution prescribes the therapeutic application.

10. The therapeutic application management system according to claim 8, characterized in that: The medical institution ID issuing unit issues a plurality of medical institution IDs corresponding to a plurality of medical institutions regardless of whether the medical institution prescribes the therapeutic application. The code information generating unit generates a plurality of code information in which corresponding medical institution IDs are recorded for a plurality of medical institutions, regardless of whether the medical institutions prescribe the therapeutic application.

11. A therapeutic application program installed on a patient terminal for use, wherein the therapeutic application program is characterized in that: Make the computer function as a medical institution ID acquisition unit and application setting unit, The medical institution ID acquisition unit acquires a medical institution ID, which is an ID issued from a management server as an ID required to start using the therapeutic application and is used to identify a medical institution that prescribes the therapeutic application. The application setting unit sets the medical institution ID acquired by the medical institution ID acquisition unit as information for making the treatment application available.

12. The therapeutic application according to claim 11, wherein: The treatment application further causes the computer to function as a login information registration request unit that makes a login information registration request executable by setting the medical institution ID by the application setting unit to the management server.

13. The therapeutic application according to claim 12, wherein: The therapeutic application also enables the computer to function as a patient information sending unit, which accepts input of initial patient information to be set when starting treatment using the therapeutic application after the login information registration request unit registers the login information with the management server according to the login information registration request, and sends the input patient initial information to the management server.

Images