JP2022139407A - Program, method, and system for personal authentication - Google Patents

Abstract

To provide a reliable personal authentication.SOLUTION: The present invention relates to a person authentication program executed by a computer of a terminal used by a doctor, the computer executing the processing of: generating information that allows an application to register the use of an application used by a terminal of a target patient from the terminal of the target patient when an input that shows the personal identification of the target patient was made, and outputting the generated information in a state in which the terminal of the target patient can read the information.SELECTED DRAWING: Figure 8

Description

This case relates to a personal authentication program, a personal authentication method, and a personal authentication system.

A technology has been proposed that provides a patient with electronic medical record information via an application installed on a patient's terminal such as a smart phone (for example, Patent Document 1).

Japanese Patent Application Laid-Open No. 2020-149670

Since the information contained in the electronic medical record is sensitive information, reliable personal authentication is required when starting to use the application so that the information is not provided to anyone other than the patient.

An object of one aspect is to provide a personal authentication program, a personal authentication method, and a personal authentication system capable of performing reliable personal authentication.

In one aspect, the personal authentication program is a personal authentication program that is executed by a computer of a terminal used by a doctor, and when an input indicating that the personal identification of the target patient has been performed is performed, the terminal of the target patient Generate information that enables application for use registration of the application used in the terminal of the target patient from, and output the generated information in a state readable by the terminal of the target patient. This is the program to run.

Reliable personal authentication can be implemented.

FIG. 1 is a diagram schematically showing the configuration of a personal authentication system according to one embodiment. FIG. 2 is a functional block diagram of an electronic medical chart server, a doctor terminal, a patient terminal, and an application server. 3A shows the hardware configuration of the doctor terminal, FIG. 3B shows the hardware configuration of the patient terminal, and FIG. 3C shows the hardware configuration of the application server. It is a figure which shows a structure. FIG. 4A is a diagram showing an example of an electronic chart screen, and FIG. 4B is a diagram showing an example of a two-dimensional code displayed on a doctor terminal. FIG. 5 is a diagram showing an example of information stored in a user information DB. FIG. 6 is a flow chart showing the processing of the doctor terminal when generating information enabling application for use registration of the outpatient support application installed in the patient terminal. FIG. 7 is a flowchart showing a process of applying for registration of use of the outpatient support application by the patient terminal. FIGS. 8A to 8H are diagrams showing an example of screen transitions of the hospital visit support application. FIG. 9 is a flowchart showing user registration processing executed by the application server. FIGS. 10A and 10B are diagrams illustrating another example of a method of generating information that enables application for registration of outpatient support app usage.

An embodiment of the personal authentication system will be described in detail below with reference to FIGS. 1 to 9. FIG.

FIG. 1 shows the configuration of a personal authentication system 100 according to one embodiment. The personal authentication system 100 includes an electronic chart server 70, a doctor terminal 30, a patient terminal 10, and an application server 50, as shown in FIG. The patient terminal 10 and the application server 50 are connected to a network NW1 such as the Internet. The application server 50 and the electronic medical record server 70 are interconnected by a network NW3 such as a VPN (Virtual Private Network). The electronic chart server 70 and the doctor terminal 30 are interconnected by a network NW2 such as a LAN (Local Area Network).

As shown in FIG. 2 , the electronic medical chart server 70 includes an electronic medical chart DB 71 that holds electronic medical chart information, provides information to the doctor terminal 30 , and manages information input from the doctor terminal 30 . The electronic medical record server 70 also has various functions other than the functions of the units shown in FIG. 2, but illustration and description thereof are omitted.

A doctor terminal 30 is a terminal that can be used by a doctor. When a doctor examines a patient, the doctor inputs various information about the patient to the doctor terminal 30, and inputs order information such as prescription instructions. Also, the doctor can make an appointment for a re-examination by operating the doctor terminal 30 after finishing the examination of the patient. Furthermore, by operating the doctor terminal 30, the doctor can also generate information necessary for applying for use registration of an outpatient support application (hereinafter referred to as an outpatient support application), which will be described later.

FIG. 3A shows the hardware configuration of the doctor terminal 30. As shown in FIG. As shown in FIG. 3A , the doctor terminal 30 includes a CPU (Central Processing Unit) 301 , a ROM (Read Only Memory) 302 , a RAM (Random Access Memory) 304 and a storage section 306 . The doctor terminal 30 also includes a network interface 307, a display unit 303, an input unit 305, a portable storage medium drive 308, and the like. A display unit 303 includes a liquid crystal display and the like, and an input unit 305 includes a keyboard, mouse, touch panel, and the like. Each component of the doctor terminal 30 is connected to the bus 310 . In the doctor's terminal 30, the CPU 301 executes a program (including an identity authentication program) stored in the ROM 302 or the storage unit 306, thereby realizing the functions of each unit shown in FIG. Note that the functions of the units shown in FIG. 2 may be realized by the CPU 301 executing a program (including a personal authentication program) read from the portable storage medium 309 by the portable storage medium drive 308 .

Specifically, in the doctor terminal 30, the CPU 301 executes the personal authentication program, thereby realizing the functions of the generation unit 31 and the output unit 32. FIG. Although the doctor's terminal 30 has various functions other than the functions of the units shown in FIG. 2, illustration and description thereof are omitted.

When an input indicating that the identity of the patient has been confirmed is received, the generation unit 31 generates information from the patient terminal 10 that enables application for registration of use of an outpatient support application used in the patient terminal 10 . FIG. 4A is a diagram showing an example of an electronic medical record screen. For example, on the electronic medical chart screen of the patient (patient under examination) whom the doctor is currently facing, when the dotted line "use registration" is clicked, the generation unit 31 generates information that enables a use registration application. do.

The output unit 32 outputs the information enabling use registration application generated by the generation unit 31 in a state readable by the terminal of the patient. For example, as shown in FIG. 4B, the output unit 32 displays a two-dimensional code (for example, QR code (registered trademark)) containing information necessary for application for use registration on the display unit 303 of the doctor terminal 30. Let

The patient terminal 10 is a terminal used by a patient, such as a smart phone. An outpatient support application is installed in the patient terminal 10 .

FIG. 3B shows the hardware configuration of the patient terminal 10. As shown in FIG. As shown in FIG. 3B, the patient terminal 10 includes a CPU 101, a ROM 102, a RAM 104, a storage unit 106, a network interface 107, a display unit 103, an input unit 105, a portable storage medium drive 108, and the like. . The display unit 103 includes a liquid crystal display and the like, and the input unit 105 includes a touch panel, a camera and the like. Each component of the patient terminal 10 is connected to the bus 110 . In the patient terminal 10, the CPU 101 executes programs stored in the ROM 102 or the storage unit 106, thereby realizing the functions of the units shown in FIG. The functions of the units shown in FIG. 2 may be implemented by the CPU 101 executing a program read from the portable storage medium 109 by the portable storage medium drive 108 .

Specifically, in the patient terminal 10, the CPU 101 executes programs to realize the functions of the display control unit 13, the reading unit 11, and the application unit 12 as a transmitting unit. The patient terminal 10 also has various functions other than the functions of the units shown in FIG. 2, but illustrations and descriptions thereof are omitted.

The display control unit 13 controls the screen displayed on the display unit 103 of the patient terminal 10 according to the operation of the patient terminal 10 by the patient.

The reading unit 11 reads the information required for the use registration application output by the output unit 32 of the doctor terminal 30 . For example, when the output unit 32 displays a two-dimensional code on the display unit 303 of the doctor terminal 30 as shown in FIG. read the two-dimensional code containing the information required for

The application unit 12 transmits a usage registration application for the application to the application server 50 in response to the reading unit 11 reading the information necessary for the usage registration application.

The application server 50 executes various processes in response to requests from the outpatient support application. Specifically, when the application server 50 receives a usage registration application for the outpatient support application from the patient terminal 10 for which usage registration has not been completed, the application server 50 performs usage registration. In addition, in response to a request from the patient terminal 10 for which the application for use registration has been completed, various information (medical appointment information, medication history information, etc.) is read from the electronic chart DB 71 and transmitted to the patient terminal 10 .

FIG. 3C shows the hardware configuration of the application server 50. As shown in FIG. As shown in FIG. 3C, the application server 50 includes a CPU 501, a ROM 502, a RAM 504, a storage unit 506, a network interface 507, a portable storage medium drive 508, and the like. Each component of the application server 50 is connected to the bus 510 . In the application server 50, the CPU 501 executes programs stored in the ROM 502 or the storage unit 506, thereby implementing the functions of the units shown in FIG. The functions of the units shown in FIG. 2 may be implemented by the CPU 501 executing a program read from the portable storage medium 509 by the portable storage medium drive 508 . The function of each part of the application server 50 may be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array).

Specifically, in the application server 50, the CPU 501 executes programs to realize the functions of the registration unit 51 and the information providing unit 53. FIG. A user information DB 52 is implemented by the storage unit 506 . Note that the application server 50 also has various functions other than the functions of the units shown in FIG. 2, but illustration and description thereof are omitted.

Upon receiving the use registration application from the patient terminal 10, the registration unit 51 stores the user (patient) of the patient terminal 10 as the user of the outpatient support application in the user information DB 52 based on the information included in the use registration application. do.

FIG. 5 is a diagram showing an example of information stored in the user information DB 52. As shown in FIG. The user information DB 52 has fields for login ID, password, hospital identification ID, patient ID, patient name, kana, date of birth, and gender.

The login ID and password fields store the ID and password used when logging into the outpatient support application installed in the patient terminal 10 . The field of hospital identification ID stores an identifier for uniquely identifying a hospital that provides a service of providing electronic medical record information using an outpatient support application. The patient ID field stores an identifier for uniquely identifying a patient, which is used in the hospital identified by the hospital identification ID. The patient name field stores the name of the patient identified by the hospital identification ID and the patient ID. The kana field stores the kana of the name of the patient identified by the hospital identification ID and the patient ID. The date of birth field stores the date of birth of the patient identified by the hospital identification ID and the patient ID. The sex field stores the sex of the patient identified by the hospital identification ID and the patient ID.

Returning to FIG. 2, the information providing unit 53 acquires various types of information from the electronic medical record DB 71 of the electronic medical record server 70 in response to a request from the outpatient support application of the patient terminal 10 for which use registration has been completed, and the patient terminal 10 Send to For example, when the outpatient support application of the patient terminal 10 requests the provision of medical appointment information, the information providing unit 53 acquires the patient's medical appointment information from the electronic medical record DB 71 and transmits it to the patient terminal 10 .

(Generation process of information that enables user registration application)
Next, regarding the processing of the doctor terminal 30 when generating information enabling use registration application of the outpatient support application installed in the patient terminal 10, along the flowchart of FIG. 6, while referring to other drawings as appropriate explain.

In the process of FIG. 6, first, in step S11, the generation unit 31 waits until receiving an input indicating that the identity of the target patient has been verified. Here, the doctor knows that the patient under examination is the person described in the electronic medical record. Therefore, in the present embodiment, when a predetermined display or button (in FIG. 4A, the display of "use registration") is clicked on the patient's electronic medical record screen, the generating unit 31 confirms the identity of the target patient. It is determined that an input indicating that the operation has been performed has been received. That is, in the present embodiment, personal identification is not performed by providing a code or the like by e-mail or short message service (SMS), but the personal identification is performed by the doctor in charge of the patient. can.

After proceeding to step S13, the generation unit 31 acquires patient information (patient name, kana, date of birth, gender) from the electronic medical chart DB 71 using the patient ID of the electronic medical chart as a key, and proceeds to step S15.

When the process proceeds to step S15, information is generated that enables application for use registration of the outpatient support application. Information that enables use registration application includes, for example, a hospital identification ID, a patient ID, patient information acquired by the generation unit 31, and a code indicating that personal identification has been performed. The code indicating that the identity has been verified is processed according to a predetermined algorithm on the outpatient support application side, and is used to determine whether or not the outpatient support application usage registration application can be permitted.

Next, in step S17, the output unit 32 displays the two-dimensional code including the information generated by the generation unit 31 on the display unit 303 (see FIG. 4B), and the processing in FIG. 6 ends.

(Use registration application process)
Using the two-dimensional code displayed on the display unit 303 of the doctor terminal 30, the process in which the patient terminal 10 applies for use registration of the outpatient support application is shown in FIGS. 8(H) as appropriate. FIGS. 8A to 8H are diagrams showing an example of screen transitions of the hospital visit support application.

In the process of FIG. 7, when the patient starts the hospital visit support application on the patient terminal 10, in step S31, the display control unit 13 displays a login screen as shown in FIG. 8(A).

On the displayed login screen, when the patient performs an operation for applying for registration of use of the outpatient support application, the process proceeds to step S33, and the display control unit 13 displays a user registration screen. For example, in the login screen shown in FIG. 8(A), when the character "Click here for first-time users" indicated by the dotted line is tapped, the display control unit 13 performs user registration as shown in FIG. 8(B). display the screen.

Next, when the user decides to continue the registration process using the two-dimensional code on the user registration screen, the process proceeds to step S35, and the display control unit 13 displays the two-dimensional code registration screen. For example, on the user registration screen shown in FIG. 8(B), when the "next" button indicated by the dotted line is tapped, the display control unit 13 causes the two-dimensional code registration screen to be displayed as shown in FIG. 8(C). display the screen.

When the two-dimensional code registration screen is displayed, in step S37, the reading unit 11 uses the camera to read the two-dimensional code displayed on the display unit 303 of the doctor terminal 30 by the processing in step S17 of FIG.

Next, in step S39, the application unit 12 checks the read two-dimensional code. For example, the application unit 12 checks whether the read two-dimensional code is a two-dimensional code for an outpatient support application, and whether the two-dimensional code contains predetermined information in a predetermined data format.

If the read two-dimensional code is not the two-dimensional code for the outpatient support application, or if the two-dimensional code does not contain the predetermined information in the predetermined data format, the determination in step S39 is denied. , the process of FIG. 6 ends. At this time, the display control unit 13 may display a message such as “personal authentication failed” on the display unit 103 of the patient terminal 10 .

On the other hand, if there is no problem with the read two-dimensional code (if the check result is OK), the determination in step S39 is affirmative, and the process proceeds to step S41. When the process proceeds to step S41, the display control unit 13, for example, as shown in FIG. date of birth, gender) are displayed on the display unit 103 .

Then, when the patient taps the "next" button on the screen of FIG. 8(D), the process proceeds to step S43, and the display control unit 13 displays the terms of use screen as shown in FIG. 8(E). indicate.

When the patient agrees to the terms of use and taps the "register" button on the screen of FIG. 8(E), the process proceeds to step S45. After proceeding to step S45, the display control unit 13 displays a screen requesting the user to input information (login ID and password) necessary for logging in to the hospital visit support application as shown in FIG. 8(F).

Then, on the screen shown in FIG. 8(F), when the login ID and password are entered and the "registration" button is tapped, the process proceeds to step S47, and the display control unit 13 displays the information included in the usage registration application. do. For example, the display control unit 13 displays a confirmation screen on which information registered in the application server 50 is displayed, as shown in FIG. 8(G).

When the "Yes" button is tapped on the confirmation screen shown in FIG. When the process of step S49 ends, the process of FIG. 7 ends.

(User registration process)
Next, user registration processing executed by the application server 50 will be described with reference to the flowchart of FIG.

In the process of FIG. 9, in step S61, the registration unit 51 waits until receiving a usage registration application. Then, upon receiving the use registration application, the registration unit 51 proceeds to step S63.

Receipt of the use registration application means that personal authentication has been successful in the outpatient support application of the patient terminal 10 . Therefore, when the process proceeds to step S63, the registration unit 51 registers the patient in the user information DB 52 (see FIG. 5) as a user of the hospital visit support application based on the information included in the usage registration application. For example, if the use registration application includes a login ID, password, hospital identification ID, patient ID, patient name, kana, date of birth, and gender, the registration unit 51 stores the information in the user information DB 52. sign up. In addition, when the login ID, password, hospital identification ID, and patient ID are included in the use registration application, the registration unit 51 registers the login ID, password, hospital identification ID, and patient ID in the user information DB 52. do. Furthermore, the registration unit 51 acquires the patient's name, kana, date of birth, and gender from the electronic medical record DB 71 using the patient ID as a key, and registers them in the user information DB 52 .

As a result, the patient is registered as a user of the outpatient support app, and can use the outpatient support app thereafter. Specifically, by entering the login ID and password on the login screen of the outpatient support application (see FIG. 8A), the outpatient support application can be used.

As described in detail above, the personal authentication system 100 according to this embodiment includes the doctor terminal 30, the patient terminal 10, and the application server 50. FIG. When an input indicating that the identity of the patient has been confirmed is received, the generation unit 31 of the doctor terminal 30 generates information from the patient terminal 10 that enables application for registration of use of the outpatient support application used in the patient terminal 10. to generate The output unit 32 of the doctor terminal 30 outputs (displays) the two-dimensional code including the generated information to the display unit 303 . The reading unit 11 of the patient terminal 10 reads the two-dimensional code displayed on the display unit 303, and the application unit 12, in response to the reading of the two-dimensional code by the reading unit 11, applies for usage registration of the outpatient support application. Send. Upon receiving the usage registration application, the registration unit 51 of the application server 50 registers the patient as a user of the hospital visit support application based on the information included in the usage registration application. Since the identification of the patient is performed by the doctor in charge of the patient, it is possible to confirm the identity of the patient more reliably than in the case of entering a code notified by e-mail, SMS, or the like. In other words, it is possible to prevent a third party impersonating a patient from applying for registration of use of the outpatient support application. Further, since the person can be authenticated by reading the two-dimensional code displayed on the display unit 303 of the doctor terminal 30, the person can be authenticated easily.

In addition, according to this embodiment, the generated information includes information specifying the patient (patient ID, patient name, kana, date of birth, sex). As a result, the patient does not need to input information identifying the patient when applying for registration of use of the outpatient support app, so the burden on the patient can be reduced when applying for registration of use of the outpatient support app.

In the above embodiment, the generated information includes information specifying the patient (patient ID, patient name, kana, date of birth, sex), but is not limited to this. For example, the generation unit 31 may generate information that includes a hospital identification ID and a code indicating that personal identification has been performed, but does not include information that identifies a patient. In this case, the patient may enter information for identifying the patient, such as a patient ID, in addition to the login ID and password after the patient is successfully authenticated by the outpatient support application.

In the above embodiment, the output unit 32 displays the two-dimensional code including the information generated by the generation unit 31 on the display unit 303, but the present invention is not limited to this. It is sufficient if the information generated by the generator 31 can be provided to the patient terminal 10 in a situation where the doctor and the patient face each other. For example, if the patient terminal 10 can read the information in the IC chip, the output unit 32 may record the data including the generated information in the IC chip. In this case, the patient terminal 10 reads the IC chip, and personal authentication processing is performed by the outpatient support application. In addition, the output unit 32 may transmit data including the generated information to the patient terminal 10 by proximity communication. In this case, when the patient terminal 10 receives data including information generated by close proximity communication, personal authentication processing is performed by the outpatient support application.

Further, in the above embodiment, an input indicating that the identity of the patient has been confirmed is performed on the electronic medical record screen, but the present invention is not limited to this. For example, as shown in FIG. 10A, the doctor double-clicks the icon 40 displayed on the display unit 303 of the doctor terminal 30 to start the personal authentication program. Then, the doctor inputs the patient ID of the patient currently facing him on the screen as shown in FIG. A two-dimensional code may be displayed.

Further, in the above embodiment, the information stored in the user information DB 52 is not limited to the information described above, and may store other patient information (for example, address). Also, the user information DB 52 may store at least a login ID, a password, a hospital identification ID, and a patient ID.

Further, in the above-described embodiment, the outpatient support application is a native application installed in the patient terminal 10, but the outpatient support application may be a web application.

Also, in the above-described embodiment, a case has been described in which a doctor confirms the identity of a patient, but the present invention is not limited to this. The relationship between the first person and the second person is such that the first person can authenticate the identity of the second person, and the second person applies for registration of use of the app that requires identity verification by the first person. When doing so, the above-described personal authentication system 100 can be used. For example, assume that a school provides an application that allows students to view their grades and the like. Since grades and other information are sensitive information, secure personal authentication is required when starting to use the app. In this case, for example, the student's homeroom teacher verifies the student's identity, and in response to receiving an input indicating that the student's identity has been verified, the teacher's terminal generates the information necessary to apply for application usage registration. can be made

Note that the processing functions described above can be realized by a computer. In that case, a program is provided that describes the processing contents of the functions that the processing device should have. By executing the program on a computer, the above processing functions are realized on the computer. A program describing the processing content can be recorded in a computer-readable storage medium (excluding carrier waves).

When a program is distributed, it is sold in the form of a portable storage medium such as a DVD (Digital Versatile Disc) or a CD-ROM (Compact Disc Read Only Memory) on which the program is recorded. It is also possible to store the program in the storage device of the server computer and transfer the program from the server computer to another computer via the network.

A computer that executes a program stores, for example, a program recorded on a portable storage medium or a program transferred from a server computer in its own storage device. The computer then reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable storage medium and execute processing according to the program. In addition, the computer can also execute processing in accordance with the received program each time the program is transferred from the server computer.

The embodiments described above are examples of preferred implementations of the present invention. However, the present invention is not limited to this, and various modifications can be made without departing from the spirit of the present invention.

In addition, the following additional remarks will be disclosed with respect to the above description of the embodiment.
(Appendix 1) A personal authentication program executed by a computer of a terminal used by a doctor,
When an input indicating that the identity of the target patient has been confirmed is made, information is generated from the target patient's terminal to enable application for registration of use of the application used in the target patient's terminal,
outputting the generated information in a state readable by the terminal of the target patient;
A personal identification program characterized by causing the computer to execute processing.
(Appendix 2) The generated information includes information identifying the target patient,
The personal authentication program described in Appendix 1.
(Additional remark 3) The output process includes a process of displaying the generated two-dimensional code containing the information on the terminal used by the doctor, and a process of displaying the generated data containing the information on the terminal of the target patient. At least one of a process of recording on a storage medium and a process of transmitting data containing the generated information to the terminal of the target patient by proximity communication,
The personal authentication program according to Supplementary Note 1 or Supplementary Note 2.
(Appendix 4) A personal authentication method executed by a computer of a terminal used by a doctor,
When an input indicating that the identity of the target patient has been verified is made, information is generated from the target patient's terminal to enable application for registration of use of the application used in the target patient's terminal,
outputting the generated information in a state readable by the terminal of the target patient;
A personal authentication method characterized by including processing.
(Additional remark 5) When an input indicating that the subject patient's identity has been verified is performed, information is generated that enables application for use registration of the application used in the subject patient's terminal from the subject patient's terminal. a generator that
an output unit that outputs the generated information in a state readable by the terminal of the target patient;
a doctor terminal including
a reading unit that reads the generated information;
a transmitting unit that transmits a usage registration application for the application in response to the reading of the information by the reading unit;
a patient terminal comprising
an application server including a registration unit that registers the target patient as a user of the application based on the information included in the use registration application when the use registration application is received;
Personal authentication system with
(Appendix 6) The generated information includes information identifying the target patient,
The personal authentication system described in Supplementary Note 5.
(Appendix 7) The output unit performs processing for displaying the generated two-dimensional code including the information on the doctor terminal, and records data including the generated information on a storage medium readable by the terminal of the target patient. and at least one of a process of transmitting data including the generated information to the terminal of the target patient by proximity communication,
The personal authentication system according to Supplementary Note 5 or Supplementary Note 6.

10 patient terminal 11 reading unit 12 application unit (transmitting unit)
30 doctor terminal 31 generation unit 32 output unit 50 application server 51 registration unit

Claims (5)

A personal authentication program executed by a computer of a terminal used by a doctor,
When an input indicating that the identity of the target patient has been confirmed is made, information is generated from the target patient's terminal to enable application for registration of use of the application used in the target patient's terminal,
outputting the generated information in a state readable by the terminal of the target patient;
A personal identification program characterized by causing the computer to execute processing. The generated information includes information identifying the target patient,
The personal authentication program according to claim 1. The output process includes displaying the generated two-dimensional code containing the information on the terminal used by the doctor, and recording the generated data containing the information on a storage medium readable by the terminal of the target patient. and at least one of a process of transmitting data including the generated information to the terminal of the target patient by proximity communication,
The personal authentication program according to claim 1 or 2. A personal authentication method executed by a computer of a terminal used by a doctor,
When an input indicating that the identity of the target patient has been confirmed is made, information is generated from the target patient's terminal to enable application for registration of use of the application used in the target patient's terminal,
outputting the generated information in a state readable by the terminal of the target patient;
A personal authentication method characterized by including processing. a generation unit that generates information that enables application for use registration of an application used in the terminal of the target patient from the terminal of the target patient when an input indicating that the identity of the target patient has been confirmed is performed; ,
an output unit that outputs the generated information in a state readable by the terminal of the target patient;
a doctor terminal including
a reading unit that reads the generated information;
a transmitting unit that transmits a usage registration application for the application in response to the reading of the information by the reading unit;
a patient terminal comprising
an application server including a registration unit that, upon receiving the application for registration of use, registers the target patient as a user of the application based on information included in the application for registration of use;
Personal authentication system with

Images