Therapeutic application management system and therapeutic application program

Abstract

To enable a treatment application to be made usable without applying a large burden on medical workers.SOLUTION: A treatment application management system comprises: a treatment application 1 installed on a patient terminal 10, and a management server 30 that issues an ID. The management server 30 comprises a medical institution ID issuing unit 31 that issues a medical institution ID that identifies a medical institution that prescribes the treatment application 1. The treatment application 1 comprises an application setting unit 12 that sets a medical institution ID as information for making the treatment application 1 usable. By using a medical institution ID that does not include patient information as an ID required to start using the treatment application 1, a medical worker of a medical institution who has diagnosed a patient and prescribed the treatment application 1 can issue a medical institution ID by the management server 30, without performing any input work for issuing the ID.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a treatment application management system and a treatment application program, and is particularly suitable for use in a system that performs processing related to the start of use of a treatment application installed and used on a patient terminal.

Background Art

[0002] In recent years, the development of application programs for the purpose of treating diseases (hereinafter referred to as treatment applications) has been underway. For example, a treatment application for treating diseases such as sleep disorders through the improvement of a patient's lifestyle is known (see, for example, Non-Patent Document 1). In addition, a treatment application for treating nicotine dependence by quitting smoking is also known. Many treatment applications are installed and used on smartphones.

[0003] A general smartphone application can be freely downloaded from a predetermined download site (so-called app store), installed on a smartphone, and used. On the other hand, since a treatment application is a medical device (medical software), it cannot be freely used by anyone. In order to use a treatment application, a patient needs to receive a medical examination and diagnosis by a doctor, and an ID and password provided when the doctor determines that it is necessary and prescribes it.

[0004] Conventionally, the issuance of this ID and password has been performed at a medical institution. At the medical institution, patient information is input from a terminal to issue a patient ID and password, the patient information and patient ID are recorded in a two-dimensional code, and the two-dimensional code and password are handed to the patient separately in the form of data or paper media. However, in a situation where a medical institution has to prescribe a patient ID and password for a treatment application for each patient, the burden on medical staff becomes significant.

[0005] On the other hand, there is known a system that automatically issues the ID and password of a treatment application in response to a request from the treatment application installed on a user terminal, without the computer operation for a doctor who diagnosed a patient to issue a user ID and a password. (For example, see Patent Document 1).

[0006] In the system described in Patent Document 1, when a patient who has installed the treatment application on a user terminal makes a code display request from a management screen displayed on a medical institution terminal installed in a lobby or a consultation room of a medical institution after receiving a doctor's diagnosis, the management server that has received the request from the medical institution terminal issues a user ID and a password, generates a two-dimensional code image recording these pieces of 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 on the medical institution terminal by the function of the treatment application, a system registration request is sent from the treatment application to the management server, and the treatment application that made the request is registered as a legitimate application, and the function restriction of the treatment application is released. Thereafter, it becomes possible to use the treatment application without being subject to function restrictions by logging in using the user ID and the password.

[0007] However, in the system described in this Patent Document 1, a special mechanism for restricting some functions of the treatment application is required until the user ID and the password are registered, and a treatment application without such a function restriction mechanism cannot be applied.

[0008] There is also known a system that enables the treatment application to be used by reading a predetermined activation code (two-dimensional code) with a smartphone. (For example, see Patent Documents 2 and 3).

[0009] In the system described in Patent Document 2, when a decision to use a medical application is made as a result of a medical examination, a doctor or a person receiving instructions from a doctor issues a prescription (including an activation code generated by forming a barcode or a two-dimensional code) via a system such as an electronic medical record. After receiving the prescription, the patient downloads and installs the medical application on the patient-side terminal, then activates the medical application and causes the activation code to be read using the code reader function of the terminal, enabling the medical application to be used.

[0010] In the system described in Patent Document 3, the server receives a request for an activation code for executing a treatment application from the information processing terminal of a patient who is the subject of treatment by the treatment application, generates an activation code based on initial information regarding the disease to be treated by the patient that has been previously input by a medical worker, and transmits it to the patient's information processing terminal. The patient's information processing terminal executes the treatment application with the initial information applied using the activation code received from the server.

[0011] However, in the system described in Patent Document 2, a doctor or a person receiving instructions from a doctor needs to issue an activation code recording various information via a system such as an electronic medical record. Also, in the system described in Patent Document 3, as a prerequisite for issuing an activation code for executing a treatment application, it is necessary for a medical worker to input in advance initial information regarding the disease to be treated by the patient and register it with the server. Therefore, in either system of Patent Documents 2 and 3, the burden on medical workers is significant.

Prior Art Documents

Patent Documents

[0012]

Patent Document 1

Patent Document 2

Patent Document 3

Non-Patent Literature

[0013]

Non-Patent Literature 1

Summary of the Invention

Problems to be Solved by the Invention

[0014] The present invention has been made to solve such problems, and an object thereof is to enable a treatment application to be used without imposing a large burden on medical staff.

Means for Solving the Problems

[0015] In order to solve the above-described problems, in the present invention, a management server issues a medical institution ID that identifies a medical institution that prescribes a treatment application as an ID necessary for starting the use of the treatment application installed on a patient terminal, and the treatment application acquires the medical institution ID issued by the management server and sets the medical institution ID as information for enabling the treatment application to be used in the treatment application.

Effects of the Invention

[0016] According to the present invention configured as described above, the ID required for starting the use of the treatment application is the medical institution ID determined in advance for each medical institution and does not include information regarding patients. Therefore, medical staff of the medical institution that diagnosed the patient and prescribed the treatment application do not need to perform any input work to enable the use of the treatment application, and by setting the medical institution ID issued by the management server in the treatment application by the patient, settings for enabling the use of the treatment application can be performed. Thus, according to the present invention, it is possible to enable the use of the treatment application without imposing a great burden on medical staff of the medical institution.

Brief Description of the Drawings

[0017]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Modes for Carrying Out the Invention

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

[0019] A plurality of patient terminals 10 -1 , 10 -2 , ··· are terminals used by individual patients who install a treatment application to perform disease treatment, 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 individual medical institutions that diagnose patients and prescribe treatment applications, and are composed of, for example, a smartphone, a tablet, a personal computer, or a dedicated medical terminal.

[0020] The management server 30 and the code issuing server 40 perform processing related to the start of use of the treatment application installed on the patient terminal 10. Here, the management server 30 is, for example, a server operated by an entity that provides the treatment application, and issues a medical institution ID required for the start of use of the treatment application. After the use of the treatment application is started, the management server 30 also executes processing related to treatment by the treatment application in cooperation with the treatment application and the medical institution terminal 20.

[0021] 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. This code issuing server 40 may be, for example, a server operated by an entity that provides the treatment application, or may be a server operated by another entity. Note that the management server 30 and the code issuing server 40 may not be separated, and the management server 30 may be configured to include a medical institution ID issuing unit 31 and a code information generating unit 41.

[0022] FIG. 2 and FIG. 3 are block diagrams showing functional configuration examples of the treatment application management system according to the present embodiment. FIG. 2 shows a functional configuration related to the process until a medical institution ID is set in the treatment application, and FIG. 3 shows a functional configuration related to the process after the medical institution ID is set in the treatment application.

[0023] As shown in FIG. 2, as a functional configuration related to the process until a 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 generation unit 41. In addition to the treatment application 1, a code reading application 2 (corresponding to the code reading means in the claims) is also stored in the patient terminal 10. Note that the treatment application 1 may be provided with the code reading means.

[0024] Also, as shown in FIG. 3, as a functional configuration related to the process 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 transmission unit 14, and the management server 30 includes a login information registration unit 32 and a patient information management unit 33.

[0025] The functional blocks shown in FIGS. 2 and 3 can be configured by any of hardware, DSP (Digital Signal Processor), and software. For example, when configured by software, the above functional blocks are actually configured with a CPU, RAM, ROM, etc. of a computer built in each of 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, hard disk, or semiconductor memory. In particular, the functional configuration of the treatment application 1 is realized by the operation of the treatment application program installed in the patient terminal 10.

[0026] In FIG. 2, 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, regardless of whether or not the medical institution prescribes the treatment application 1 to the patient, the medical institution ID issuing unit 31 issues a plurality of medical institution IDs corresponding to a plurality of medical institutions, and provides the plurality of medical institution IDs to the code issuing server 40.

[0027] Here, "regardless of whether or not the medical institution prescribes the treatment application 1 to the patient" means in advance before the medical institution prescribes the treatment application 1 to the patient. For example, when the information of the medical institution that has decided to introduce the treatment 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. The medical institution ID issuing unit 31 issues a medical institution ID every time the information of the medical institution is registered in the management server 30.

[0028] The code information generation 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. This 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.

[0029] In the present embodiment, regardless of whether or not the medical institution prescribes the treatment application 1 to the patient, the code information generation unit 41 generates a plurality of code information recording the corresponding medical institution ID for each of the plurality of medical institutions, and provides the plurality of code information to the plurality of medical institution terminals 20. For example, as described above, every time the information of the 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 generation unit 41 generates code information including the provided medical institution ID, and provides the generated code information to the corresponding medical institution terminal 20.

[0030] The method of providing the code information is arbitrary. For example, the code information generation unit 41 can transmit the code information to the medical institution terminal 20 via the communication network 50. Further, the code information generation unit 41 may record the code information on a removable storage medium, and the administrator may deliver this 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 web site for data transfer managed by the management server 30 or the code issuing server 40.

[0031] 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 in which the medical institution ID of the medical institution is recorded regardless of whether the medical institution prescribes the treatment application 1 to the patient (even before the medical institution prescribes the treatment application 1 to the patient).

[0032] 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 treatment application 1 to the patient. For example, when a medical staff operates the medical institution terminal 20 to instruct the provision of the code information, the code providing unit 22 receives this instruction, reads out the code information from the code storage unit 21, and provides it to the patient terminal 10.

[0033] The method of providing the code information is arbitrary. For example, the code providing unit 22 can cause the display device of the medical institution terminal 20 to display the code information, and the code information can be provided by reading it with the code reading app 2 of the patient terminal 10. Instead of causing the display device of the medical institution terminal 20 to display the code information, the code providing unit 22 may 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 recorded on the paper medium is read by the code reading app 2 of the patient terminal 10 to provide the code information. Further, the code providing unit 22 may record the code information on a removable storage medium, and the patient terminal 10 may provide the code information by reading the code information from this removable storage medium. Alternatively, the code providing unit 22 may provide the code information to the patient terminal 10 via a web site for data transfer managed by the management server 30.

[0034] The medical institution ID acquisition unit 11 of the treatment app 1 acquires the medical institution ID issued by the medical institution ID issuing unit 31 of the management server 30. For example, when configured such that the code information is provided from the medical institution terminal 20 to the patient terminal 10 by reading the code information with the code reading app 2, the medical institution ID acquisition unit 11 acquires the medical institution ID that the code reading app 2 has read and decoded the code information from the code reading app 2. When configured such that the code information is provided from the medical institution terminal 20 to the patient terminal 10 via a removable storage medium or a web site for data transfer, the medical institution ID acquisition unit 11 acquires the medical institution ID by decoding the provided code information.

[0035] The app setting unit 12 sets the medical institution ID acquired by the medical institution ID acquisition unit 11 in the treatment app 1 as information for enabling the use of the treatment app 1. Enabling the use of the treatment app 1 means a state in which the treatment app 1 can cooperate with the medical institution terminal 20 via the management server 30 to perform processing related to treatment.

[0036] That is, after the patient starts using the treatment application 1, various pieces of information related to the treatment (such as the current symptoms and information indicating the implementation status of the treatment application 1) are registered from the treatment application 1 to the management server 30, and it becomes viewable from the medical institution terminal 20. However, it is necessary to ensure that it can only be viewed from the medical institution terminal 20 linked to the treatment application 1. The medical institution ID is used for linking the treatment application 1 and the medical institution terminal 20. Therefore, before the medical institution ID is set in the treatment application 1, the treatment application 1 cannot be used, and the medical institution ID is information that needs to be set in the treatment application 1 when starting the use of the treatment application 1.

[0037] In FIG. 3, the login information registration request unit 13 of the treatment application 1 makes a login information registration request executable to the management server 30 due to the setting of the medical institution ID 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 triggered by, for example, the completion of setting the medical institution ID, and prompts the patient to register the login information. Note that the registration request for the login information may be made such that the patient can manually display the registration screen at an arbitrary timing after the setting of the medical institution ID is completed.

[0038] In this embodiment, when the patient actually uses the treatment application 1, it is designed such that it is necessary to log in to the treatment application 1. For this login, the patient's user ID and password are used. For the user ID, for example, the email address of the patient terminal 10 is used. When the patient inputs the user ID and password by operating on the registration screen, the login information registration request unit 13 transmits 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 make a registration request for the login information.

[0039] The login information registration unit 32 of the management server 30 registers the login information used by the patient to log in to the treatment application 1 in the management server 30 in response to the login information registration request transmitted from the treatment application 1. At the time of this registration, the login information registration unit 32 associates the user ID with the medical institution ID transmitted from the treatment application 1 together with the login information and registers it. As described above, in this embodiment, if the medical institution ID is not set in the treatment application 1, the login information cannot be registered in the management server 30.

[0040] After the login information registration unit 13 of the treatment application 1 issues a login information registration request and the login information is registered in the management server 30 in response thereto, the patient information transmission unit 14 of the treatment application 1 accepts the input of the initial patient information to be set at the start of treatment using the treatment application 1, and transmits the input initial patient information to the management server 30.

[0041] For example, the patient information transmission unit 14 displays an input screen for initial patient information on the display device of the patient terminal 10 triggered by, for example, receiving a registration completion notification of the login information from the management server 30, and prompts the patient to input the initial patient information. The initial patient information includes, for example, the examination ticket number, name, gender, date of birth, other diseases during treatment (comorbid diseases), and information related to the disease to be treated by the treatment application 1 (current symptoms, etc.). When the patient inputs the initial patient information by operating the input screen, the patient information transmission unit 14 transmits the input initial patient information to the management server 30. Note that the input of the initial patient information may be performed by the patient manually displaying the input screen at an arbitrary timing after the registration of the login information is completed.

[0042] The patient information management unit 33 stores the initial patient information transmitted from the treatment app 1 in a storage medium and manages it in a state where it can be viewed from the medical institution terminal 20 linked to the treatment app 1 by 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 linked to the medical institution ID in a state where it can be viewed by the medical institution terminal 20.

[0043] The patient information management unit 33 provides not only the initial patient information but also various pieces of information related to the treatment sequentially registered from the treatment app 1 to the management server 30 after the start of use of the treatment app 1 to the medical institution terminal 20. By viewing this information related to the treatment, medical staff can grasp the patient's disease and treatment status (how the numerical values are changing, whether the use of the treatment app 1 is being continued, etc.) and can contact the patient as needed. Note that the patient information management unit 33 does not provide the user ID (email address) and password to the medical institution terminal 20.

[0044] The patient information management unit 33 may manage the initial patient information transmitted from the treatment app 1 in a state where it can be edited from the medical institution terminal 20 linked to the treatment app 1 by the medical institution ID. For example, when a medical staff member who has viewed the initial patient information registered in the management server 30 recognizes that the input is incorrect when compared with the memory at the time of diagnosis or the medical record information for which the treatment app 1 was prescribed, the medical staff member may be allowed to correct it to the correct information. Also, when it is recognized that there is an input omission when compared with the memory at the time of diagnosis or the medical record information, or the input information of other patients, the medical staff member may be allowed to add input the information.

[0045] The patient information management unit 33 may manage not only the initial patient information but also various pieces of information related to treatment that are sequentially registered from the treatment application 1 to the management server 30 after the start of use of the treatment application 1 in an editable state from the medical institution terminal 20 linked with the medical institution ID for the treatment application 1. For example, when it is recognized that there are input errors or omissions in the information transmitted from the treatment application 1 to the management server 30 and registered, in comparison with the medical record information that medical staff routinely use in medical treatment, it may be possible for the medical staff to edit the information.

[0046] FIG. 4 and FIG. 5 are flowcharts showing operation examples of the treatment application management system according to the present embodiment configured as described above. FIG. 4 shows the processing until the code information is stored in the medical institution terminal 20, and FIG. 5 shows the processing after the medical institution prescribes the treatment application 1 to the patient.

[0047] In FIG. 4, 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 treatment application 1 is registered in the management server 30 (step S1). Here, until the information of the medical institution is registered in the management server 30, the determination in step S1 is repeated at predetermined time intervals. 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).

[0048] The code information generating unit 41 of the code issuing server 40 generates code information recording the medical institution ID provided from 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 from the code issuing server 40 (step S4). Thus, the processing of the flowchart shown in FIG. 4 is terminated.

[0049] In FIG. 5, first, the code providing unit 22 of the medical institution terminal 20 determines whether an operation for instructing the provision of code information has been performed on the medical institution terminal 20 by a medical staff who has prescribed the treatment application 1 (step S11). If this instruction is given, 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 treatment application 1 (step S12).

[0050] At the patient terminal 10, the medical institution ID acquisition unit 11 of the treatment application 1 acquires, from the code reading application 2, the medical institution ID that the code reading application 2 has read and decoded the code information (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 enabling the use of the treatment application 1 (step S14).

[0051] Next, the login information registration request unit 13 displays a login information registration screen on the patient terminal 10, and transmits 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 make a login information registration request (step S15). The login information registration unit 32 of the management server 30 registers the login information in association with the medical institution ID in the management server 30 in response to the login information registration request transmitted from the treatment application 1 (step S16).

[0052] Thereafter, the patient information transmission unit 14 of the treatment application 1 displays a patient initial information input screen on the patient terminal 10 triggered by receiving a notification of the completion of the registration of the login information from the management server 30, and transmits the patient initial information input through this input screen to the management server 30 (step S17). The patient information management unit 33 of the management server 30 stores the patient initial information transmitted from the treatment application 1 in a storage medium, and manages it in a state where it can be browsed and edited by the medical institution terminal 20 associated with the treatment application 1 by the medical institution ID. Thus, the processing of the flowchart shown in FIG. 5 is completed.

[0053] As described in detail above, in this embodiment, the management server 30 issues a medical institution ID (an ID for identifying the medical institution that prescribed the treatment application) necessary for starting the use of the treatment application 1 installed on the patient terminal 10, and the treatment application 1 acquires and sets this medical institution ID, thereby enabling the treatment application 1 to be used.

[0054] Also, in this embodiment, after the medical institution ID is set in the treatment application 1, the treatment application 1 makes a login information registration request to the management server 30 to perform the registration of the login information. Further, in this embodiment, after the login information is registered, the treatment application 1 transmits and registers the initial patient information to the management server 30.

[0055] In this embodiment configured as described above, the information used to enable the treatment application 1 to be used is a medical institution ID determined in advance for each medical institution, and does not include login information or patient-related information. For this reason, it is not necessary for the medical staff of the medical institution to perform any input work for ID issuance, and the management server 30 can issue the medical institution ID. Also, it is possible to provide the medical institution ID to the medical institution terminal 20 in advance before the medical staff diagnoses the patient and prescribes the treatment application 1. Then, after the treatment application 1 is prescribed, the patient can set the medical institution ID provided by the medical institution in the treatment application 1 to perform the settings for enabling the treatment application 1 to be used. Furthermore, the login information and the initial patient information are configured such that the patient inputs them from the treatment application 1 and registers them with the management server 30 after setting the medical institution ID in the treatment application 1. For this reason, it is not necessary for the medical staff of the medical institution to perform the registration work for the login information and the initial patient information to actually enable the treatment application 1 to be used. Thus, according to this embodiment, the patient can be enabled to use the treatment application 1 without imposing a large burden on the medical staff of the medical institution.

[0056] In the above-described embodiment, the management server 30 is a server operated by the entity that provides the treatment application 1, and the configuration in which the management server 30 includes the functional components 31 to 33 has been described. However, the present invention is not limited to this. For example, a first management server including a medical institution ID issuing unit 31 that issues a medical institution ID, and a second management server including a login information registration unit 32 and a patient information management unit 33 that executes processing related to treatment using the treatment application 1 may be provided. The entity that provides the treatment application 1 may operate the second management server, while the first management server may be operated by another entity. Further, the first management server may be configured to include a code information generation unit 41 in addition to the medical institution ID issuing unit 31. In this case, the first management server may be a plurality of servers operated by individual medical institutions. Even in a configuration where a medical institution ID is issued by a management server operated by a medical institution, it is not necessary for a medical staff member of the medical institution to perform any input operation for ID issuance.

[0057] Also, in the above-described embodiment, an example in which a code issuing server 40 is provided and a medical institution ID is encoded and provided to the medical institution terminal 20 has been described. However, 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.

[0058] In addition, in the above-described embodiment, the configuration of logging in to the treatment application 1 using the login information registered in the management server 30 has been described. However, it is also possible to eliminate the need to log in to the treatment application 1. In this case, for example, instead of the login information registration request unit 13, an application ID transmission unit is provided, and instead of associating the user ID and the medical institution ID and registering them in the management server 30, it is conceivable to associate the application ID for identifying the prescribed treatment application 1 and the medical institution ID and register them in the management server 30. Also in this case, after the treatment application 1 becomes usable due to the setting of the medical institution ID by the application setting unit 12, the patient information transmission unit 14 accepts the input of the initial patient information to be set at the start of the treatment using the treatment application 1, and transmits the input initial patient information to the management server 30.

[0059] In addition, in the above-described embodiment, an example has been described in which the medical institution issues a medical institution ID and stores the code information in the medical institution terminal 20 regardless of whether the medical institution prescribes the treatment application 1 to the patient (even before the medical institution prescribes the treatment application 1 to the patient). However, the present invention is not limited to this. For example, when the medical institution prescribes the treatment application 1 to the patient, an ID issuance request may be transmitted from the medical institution terminal 20 to the management server 30 to issue the medical institution ID.

[0060] Furthermore, each of the above-described embodiments merely shows an example of implementation when carrying out the present invention, and the technical scope of the present invention should not be construed in a limited manner thereby. That is, the present invention can be implemented in various forms without departing from the gist or the main features thereof.

Explanation of Reference Numerals

[0061] 1 Treatment application 10 Patient terminal 11 Medical institution ID acquisition unit 12 Application setting unit 13 Login information registration request unit 14 Patient information transmission unit 20 Medical institution terminal 21 Code Memory Unit 22 Code Provision Unit 30 Management Server 31 Medical Institution ID Issuing Unit 32 Login Information Registration Unit 33 Patient Information Management Unit 40 Code Issuing Server 41 Code Information Generation Unit

Claims

1. A system for performing processing related to the start of use of a treatment application installed and used on a patient terminal, the treatment application installed on the patient terminal, and a management server that issues an ID necessary for starting the use of 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 treatment application, the treatment application includes a medical institution ID acquisition unit that acquires the medical institution ID issued by the medical institution ID issuing unit, and an application setting unit that sets the medical institution ID acquired by the medical institution ID acquisition unit as information for enabling the treatment application to be used, A treatment application management system characterized by the above.

2. The treatment application further includes a login information registration request unit that sends a login information registration request to the management server, which becomes executable due to the setting of the medical institution ID by the application setting unit, the management server further includes a login information registration unit that registers login information used when a patient using the treatment application logs in to the treatment application in response to the login information registration request sent from the treatment application, The treatment application management system according to claim 1, characterized by the above.

3. The management server includes a first management server having the medical institution ID issuing unit, and a second management server having the login information registration unit, The treatment application management system according to claim 2, characterized by the above.

4. After the medical institution ID is set by the above app setting unit, the treatment app further includes a patient information transmission unit that accepts input of initial patient information to be set at the start of treatment using the treatment app, and transmits the input initial patient information to the management server. The management server further includes a patient information management unit that manages the initial patient information transmitted from the treatment app in a state where it can be viewed from a medical institution terminal used in the medical institution. The treatment app management system according to claim 1, characterized in that.

5. After the login information is registered by the above login information registration unit, the treatment app further includes a patient information transmission unit that accepts input of initial patient information to be set at the start of treatment using the treatment app, and transmits the input initial patient information to the management server. The management server further includes a patient information management unit that manages the initial patient information transmitted from the treatment app in a state where it can be viewed from a medical institution terminal used in the medical institution. The treatment app management system according to claim 2, characterized in that.

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

7. After the login information is registered by the above login information registration unit, the treatment app further includes a patient information transmission unit that accepts input of initial patient information to be set at the start of treatment using the treatment app, and transmits the input initial patient information to the management server. The management server further includes a patient information management unit that manages the initial patient information transmitted from the treatment app in a state where it can be viewed from a medical institution terminal used in the medical institution. The management server or the code issuing server that receives the provision of the medical institution ID from the management server includes a code information generation unit that generates code information including the medical institution ID and not including both the login information and the initial patient information. The medical institution ID acquisition unit of the patient terminal acquires the medical institution ID obtained by reading and decrypting the code information by the code reading means of the patient terminal. The therapeutic application management system according to claim 2, characterized in that.

8. The management server or the code issuing server that receives the provision of the medical institution ID from the management server includes a code information generation unit that 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 obtained by decrypting the code information displayed on the display device of the medical institution terminal by reading it with the code reading means of the patient terminal. The therapeutic application management system according to any one of claims 1 to 5, characterized in that.

9. 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, according to any one of claims 1 to 5. The therapeutic application management system described.

10. 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 generation unit generates a plurality of code information records with the corresponding medical institution ID for each of a plurality of medical institutions regardless of whether the medical institution prescribes the therapeutic application. The therapeutic application management system according to claim 8, characterized in that.

11. A program for a therapeutic application installed and used on a patient terminal, An ID issued by a management server as an ID required for starting the use of the above therapeutic application, a medical institution ID acquisition means for acquiring a medical institution ID that identifies the medical institution prescribing the above therapeutic application, and An app setting means for setting the medical institution ID acquired by the medical institution ID acquisition means as information for enabling the use of the above therapeutic application A therapeutic application program for causing a computer to function as such.

12. A login information registration request means for making a login information registration request to the above management server, which becomes executable due to the setting of the above medical institution ID by the above app setting means The therapeutic application program according to claim 11, characterized in that the computer is further caused to function as such.

13. After the login information is registered with the above management server in response to the above login information registration request by the above login information registration request means, an input of initial information of a patient to be set at the start of treatment using the above therapeutic application is accepted, and a patient information transmission means for transmitting the input patient initial information to the above management server The therapeutic application program according to claim 12, characterized in that the computer is further caused to function as such.

Images