Account creation program, account creation method, and information processing device

Abstract

To generate an account for accessing a system that assists a user to use a medical institution, in association with a user who has a predetermined relation with the above user.SOLUTION: A program causes a first computer to execute the processes of: reading, when a first user creates an account, a code output from a second computer accessing a system; acquiring, from the code, first information based on whether the second computer is a predetermined terminal used by a person concerned of a medical institution, and second information for identifying a second user who has a predetermined relation with the first user; displaying, when the first information indicates that the second computer is the predetermined terminal, one or more first screens for generating an account in association with the second user indicated by the second information; displaying, when the first information indicates that the second computer is not the predetermined terminal, a second screen for authentication processing regarding the second user; displaying one or more first screens when the authentication is successful; and generating an account associated with the second user in accordance with an operation input on the first screens.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present invention relates to an account creation program, an account creation method, and an information processing device. [Background technology]

[0002] There are known systems that support users in using medical institutions. These systems provide users with accounts to access the system with functions for making appointments at medical institutions, checking appointment status, checking in, accounting, referring to electronic medical records, and communicating with doctors, etc.

[0003] This system can manage a user's account by linking (associating) it with users who have a predetermined relationship with the user, for example, a family relationship.

[0004] This allows a user (e.g., a mother) to receive the above-mentioned functions for other users (e.g., children) associated with the mother's account. For example, if a child is linked to the mother's account, the mother can access the system using her account and view the child's electronic medical record. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2020-86590 [Patent Document 2] Japanese Patent Application Laid-Open No. 2010-55196 Summary of the Invention [Problem to be solved by the invention]

[0006] In the above-mentioned system, there are cases where the timing at which a user account can be created is limited. For example, when a user visits a medical institution (for example, for the first time), an account is created by associating the user with the medical institution.

[0007] Here, it is assumed that a certain user (for example, a father) does not have an account and has no medical history at a certain medical institution, but accompanies his child to the medical institution.

[0008] Because the father does not have an account to access the system, he may not be able to use the system's functions related to the medical institution for his child, such as making appointments for the child, checking appointment status, checking in, accounting, accessing electronic medical records, and communicating with doctors. Also, because there is no history of the father's visits to the medical institution, the medical institution may not be able to create an account linked to the child.

[0009] In this way, medical institutions and users may not be able to fully enjoy the functions provided by the system. Furthermore, medical institutions may incur costs for personnel, computer resources, etc. to deal with the above-mentioned situations.

[0010] The system is not limited to a system that supports users in using medical institutions, and may be various other systems.

[0011] In one aspect, an object of the present invention is to create an account for accessing a system that supports a user's use of a medical institution, in association with a user who has a predetermined relationship with the user. [Means for solving the problem]

[0012] In one aspect, the account creation program may cause a first computer used by a first user to execute the following processes. The processes may include, when the first user creates an account for accessing a system that supports users' use of a medical institution, reading a code output from a second computer accessing the system. The processes may include, from the read code, acquiring first information indicating whether the second computer is a predetermined terminal used by a person associated with the medical institution and second information identifying a second user who has a predetermined relationship with the first user. The processes may include, when the first information indicates that the second computer is the predetermined terminal, displaying one or more first screens for creating a first account for the first user in association with the second user indicated by the second information. When the first information indicates that the second computer is not the predetermined terminal, displaying a second screen for performing authentication processing for the second user indicated by the second information, and displaying the one or more first screens if the authentication processing on the second screen is successful. The process may include a process of creating the first account associated with the second user in response to an operation input on the one or more first screens. [Effects of the Invention]

[0013] In one aspect, the present invention can create an account for accessing a system that supports a user's use of a medical institution, in association with a user who has a predetermined relationship with the user. [Brief explanation of the drawings]

[0014] [Figure 1] 1 is a block diagram illustrating an example of the configuration of an account creation system according to an embodiment. [Figure 2] FIG. 1 is a diagram illustrating an example of an application scene of an account creation system according to an embodiment. [Figure 3] FIG. 2 is a diagram illustrating a first operation example of the account creation system according to an embodiment. [Figure 4] FIG. 2 is a diagram illustrating a first operation example of the account creation system according to an embodiment. [Figure 5] FIG. 2 is a diagram showing a first example of information included in a two-dimensional code. [Figure 6] FIG. 10 is a diagram illustrating a second operation example of the account creation system according to an embodiment. [Figure 7] FIG. 10 is a diagram illustrating a second operation example of the account creation system according to an embodiment. [Figure 8] FIG. 10 is a diagram showing a second example of information included in a two-dimensional code. [Figure 9] FIG. 2 is a block diagram showing an example of the hardware (HW) configuration of a computer that realizes the functions of a terminal according to an embodiment. [Figure 10] FIG. 2 is a block diagram illustrating an example of the software configuration of an account creation system according to an embodiment. [Figure 11] FIG. 2 is a diagram illustrating an example of user information stored in a database (DB). [Figure 12] 10 is a flowchart illustrating an example of the operation of a terminal of an account creation system according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the embodiments described below are merely examples, and are not intended to exclude various modifications or application of techniques not explicitly described below. For example, the present embodiment can be implemented with various modifications within the scope of the spirit thereof. In the drawings used in the following description, parts with the same reference numerals represent the same or similar parts unless otherwise specified.

[0016] [A] Configuration example of one embodiment 1 is a block diagram showing an example of the configuration of an account creation system 1 according to one embodiment. The account creation system 1 creates an account for accessing the system in association with a user who has a predetermined relationship with the user. In one embodiment, the system is a support system 6 that supports users in using medical institutions.

[0017] The account creation system 1 may illustratively include a plurality of terminals 2 to 4 and a server 5, as shown in FIG.

[0018] The terminals 2 to 4 and the server 5 may be connected to each other so as to be able to communicate with each other via a network 7. The network 7 may be formed by at least one of a LAN (Local Area Network), a mobile network, and the Internet.

[0019] Terminals 2 and 3 are computers used by users of the support system 6. Below, a father 11, a mother 13, and a child 14 who are in a family relationship with each other will be taken as examples of users. The father 11 is an example of a first user, and the child 14 is an example of a second user. The mother 13 is an example of a third user who has a predetermined relationship with both the father 11 and the child 14.

[0020] For example, the user of terminal 2 is a father 11 who does not have an account with the support system 6. The user of terminal 3 is a mother 13 who has an account (second account) with the support system 6. A child 14 is linked to the account of the mother 13. Hereinafter, linking another user who is in a family relationship with a user's account may be referred to as "family registration."

[0021] Family relationships are an example of predetermined relationships. The predetermined relationships are not limited to family relationships, and may include, for example, various relationships established by the support system 6 or medical institutions.

[0022] Fig. 2 is a diagram showing an example of an application scene of the account creation system 1 according to an embodiment. As shown in Fig. 2, in one embodiment, an example will be described in which a father 11 creates an account (first account) for the support system 6 and registers a child 14 as a family member in the account created by the father 11. In the following description, it is assumed that the child 14 has a medical history at Hospital A, which is an example of a medical institution, and the mother 13 has an account that is associated with Hospital A and in which the child 14 has been registered as a family member.

[0023] Returning to the explanation of Fig. 1, the terminal 4 is a computer used by medical institution staff 12. Examples of medical institutions include various medical institutions or facilities such as hospitals, clinics, nursing / recuperation institutions, health checkup institutions, pharmacies, and vaccination facilities.

[0024] The staff member 12 is an example of a person related to a medical institution. Examples of the staff member 12 (user of the terminal 4) include people who work at a medical institution, such as doctors, nurses, medical staff, and front desk staff. For example, if the medical institution is a hospital, examples of the terminal 4 include a terminal used by a doctor in an examination room and a terminal used by a front desk staff at a reception desk.

[0025] The terminal 2 used by the father 11 is an example of a first computer or a first information processing device, and the terminal 3 used by the mother 13 and the terminal 4 used by the staff member 12 are each an example of a second computer or a second information processing device that accesses the support system 6. Furthermore, the terminal 4 is an example of a predetermined terminal or a medical institution terminal.

[0026] The staff 12 may be referred to as a "medical institution user" who has authority over the functions of the medical institution among the users of the support system 6. In contrast to the staff 12, users (patients) of the medical institution, such as the father 11, mother 13, and child 14, who do not have authority over the functions of the medical institution, may be referred to as a "general user."

[0027] The server 5 is a server provided in the support system 6. The server 5 may be, for example, a server that stores and manages user information including user accounts in the support system 6. The server 5 may be, for example, provided with a DB (database) that stores user information.

[0028] The support system 6 is an example of a system that supports a user's use of medical institutions. The support system 6, for example, cooperates with a plurality of medical institutions, and manages a user who has an account for the support system 6 in association with one or more of the medical institutions that the user uses. The support system 6 then provides a terminal used by the user with various functions related to the medical institution associated with the user, such as functions for referencing electronic medical records, making appointments, and checking appointment status.

[0029] Hereinafter, the provision of functions to a user by the assistance system 6 will be described as being realized, for example, by an application installed on a terminal used by the user communicating with multiple servers (including server 5) of the assistance system 6 via the network 7. The application may be a dedicated application for the purpose of accessing and using the assistance system 6.

[0030] An application (hereinafter referred to as "APP") 8, which is an example of the above-mentioned application, is installed on each of terminals 2 and 3. Furthermore, an application APP9, which is an example of the above-mentioned application, is installed on terminal 4. For example, APP8 may provide functions of the support system 6 that are used by general users, and APP9 may provide functions of the support system 6 that are used by medical institution users. Note that APP9 may be an application for displaying two-dimensional codes. At least some of the functions of APP8 and APP9 may be common to each other.

[0031] The APP 8 may control user login. For example, the APP 8 may display a login screen, transmit information such as the user's account and password accepted on the login screen to the server 5, and, when the server 5 permits login, provide the user with the functions of the support system 6 associated with the account.

[0032] In the following explanation, it is assumed that APP8 on the terminal 3 of the mother 13 has been logged in using the account of the mother 13, who is a general user. Also, it is assumed that APP8 has been installed on the terminal 2 of the father 11, but the father 11 has not yet created an account, and therefore is not yet logged in. Furthermore, it is assumed that APP9 on the terminal 4 of the staff member 12 has been logged in using the account of the staff member 12, who is a medical institution user.

[0033] [B] First operation example of one embodiment Next, a first operation example of the account creation system 1 according to an embodiment will be described with reference to Fig. 3 and Fig. 4. Fig. 3 and Fig. 4 are diagrams for explaining the first operation example of the account creation system 1 according to an embodiment. Fig. 3 and Fig. 4 show an example in which a father 11 creates an account for the father 11 linked to the child 14 when the father 11 visits Hospital A together with the child 14 to accompany the child 14 to a medical examination at Hospital A.

[0034] 3 and 4, the processing (steps) proceed in the order of symbols A1 to A15. In addition, in Fig. 3 and 4, the screen displayed on terminal 2 by APP8 is expressed as "2A" by combining the symbol "2" of terminal 2 with an alphabet to distinguish the screen. Similarly, the screen displayed on terminal 4 by APP9 is expressed as "4A".

[0035] At reference symbol A1 in FIG. 3, father 11 presents information about child 14, such as the child's health insurance card and medical examination number, to staff member 12 at Hospital A. Staff member 12 checks whether information about child 14 exists in, for example, a server (or server 5) that manages patient information at Hospital A. Staff member 12 may further check a predetermined relationship (family relationship) between father 11 and child 14.

[0036] In reference symbol A2, if information about a child 14 is present in the patient information, the staff member 12 operates the APP 9 of the terminal 4 to output a two-dimensional code 41 for registering the information about the child 14 as a family member. For example, the APP 9 of the terminal 4 is operated by the staff member 12 to display a two-dimensional code display screen 4A on a display device such as a monitor of the terminal 4.

[0037] As shown in FIG. 3, the two-dimensional code display screen 4A may include a display area 4A1 for the name and patient information (date of birth, sex, etc.) of the patient (child 14), and a two-dimensional code 41 for registering the child 14 as a family member.

[0038] Fig. 5 is a diagram showing a first example of information included in the two-dimensional code 41. As shown in Fig. 5, the two-dimensional code 41 may include, for example, a medical institution ID, a medical institution name, a patient ID, a patient name, patient information, etc., as well as authentication necessity information indicating whether or not an authentication screen is to be displayed.

[0039] The medical institution ID is an example of identification information of a medical institution in the support system 6, for example, "GPR0000111." The medical institution name is the name of the medical institution set in the support system 6, for example, "Hospital A."

[0040] The patient ID is an example of identification information for a patient (user) for each medical institution, for example, "000001000." A patient associated with multiple medical institutions may have a different patient ID for each medical institution. The patient ID is an example of second information for identifying a second user who has a predetermined relationship with the first user.

[0041] The patient name and patient information are an example of user information of the patient, such as name, sex, date of birth, and name in kana.

[0042] The authentication necessity information indicates whether or not to perform authentication processing for the user to be registered when performing family registration. For example, in the first operation example, when the terminal 4 outputs the two-dimensional code 41, it is assumed that authentication for family registration has been completed by the staff member 12, and the authentication necessity information may be set to information indicating "not required."

[0043] In other words, the authentication necessity information is an example of first information corresponding to whether the second computer is a predetermined terminal. Note that the two-dimensional code 41 may include other first information instead of or in addition to the authentication necessity information. Examples of other first information include, for example, information indicating whether the medical institution terminal (terminal 4) has displayed the two-dimensional code 41, and / or identification information of a screen to which APP 8 is transitioned (the authentication screen or the screen after skipping the authentication screen).

[0044] The two-dimensional code 41 may be information obtained by encoding at least a portion of the above-mentioned information, and is an example of a code output by the second computer. Examples of the two-dimensional code 41 include codes using various methods, such as a matrix type such as QR Code (registered trademark) or a stack type. Note that the code is not limited to the two-dimensional code 41, and various methods capable of transferring (notifying) information from the terminal 4 to the terminal 2, such as a one-dimensional code such as a barcode or wireless communication, may also be used. Examples of wireless communication include contactless integrated circuit (IC) technology such as near field communication (NFC).

[0045] 3, at reference symbol A3, the father 11 starts up the APP 8 of the terminal 2, and the login screen 2A is displayed on the display device of the terminal 2. Note that either reference symbol A2 or reference symbol A3 may be performed first.

[0046] The login screen 2A may include a link 2A1 for "first-time users, click here" in addition to an input field 2A2 for the login ID and password. The father 11 selects the link 2A1 for "first-time users, click here." Note that, from reference symbol A3 onwards, the father 11 is not shown on each screen because the processing is in response to the operation of the terminal 2 by the father 11.

[0047] In reference symbol A4, APP8 of terminal 2 displays a two-dimensional code reading screen 2B on the display device. The two-dimensional code reading screen 2B may include a two-dimensional code reading frame 2B1 and a back button (denoted as "<") 2B2. The back button 2B2 is a button for returning to the screen immediately before the current screen. This is also true for other screens described later. Father 11 uses a code reading device provided in terminal 2, for example a camera (imaging device) that captures an image of two-dimensional code 41, to capture an image of two-dimensional code 41 displayed on the display device of terminal 4.

[0048] The APP 8 of the terminal 2 acquires the medical institution ID, medical institution name, patient ID, patient name, patient information, and authentication necessity information contained in the read two-dimensional code 41.

[0049] APP8 of terminal 2 acquires the patient ID of the second user by reading the two-dimensional code 41, and determines to associate the first user with the second user when creating an account for the first user to access the support system 6.

[0050] At symbol A5, APP8 of terminal 2 displays the registered two-dimensional code information confirmation screen 2C on the display device because the acquired authentication necessity information indicates "not required" (because two-dimensional code 41 was output by terminal 4).

[0051] The registration two-dimensional code information confirmation screen 2C is an example of a confirmation screen for creating an account by associating the child 14 indicated by the patient ID with the father 11, and may include a display area 2C1 for the acquired patient name, patient information, etc., and a "Next" button 2C2. The father 11 agrees with the contents of the display area 2C1 and presses the "Next" button 2C2.

[0052] At reference symbol A6, the APP 8 of the terminal 2 displays an application terms agreement screen 2D on the display device. The application terms agreement screen 2D is a screen for requesting consent to the terms of use of the APP 8 of the support system 6, and may include an input field 2D1 for checking consent and a "Next" button 2D2. The father 11 checks the input field 2D1 and presses the "Next" button 2D2.

[0053] At symbol A7, the APP 8 of the terminal 2 displays a Hospital A terms and conditions consent screen 2E on the display device. The Hospital A terms and conditions consent screen 2E is a screen that requests consent to the terms and conditions of the APP 8 for each medical institution, and may include a check input field 2E1 indicating consent, and a "Next" button 2E2. The father 11 checks the input field 2E1 and presses the "Next" button 2E2.

[0054] At symbol A8 in FIG. 4, APP8 of terminal 2 displays a guest account creation screen 2F on the display device. The guest account creation screen 2F may include an input field 2F1 for the father's 11's user information, such as his name, kana name, gender, date of birth, login ID, password, etc., and a "Register" button 2F2. The father 11 inputs his user information into the input field 2F1 and presses the "Register" button 2F2. The user information of the father 11 input into the input field 2F1 is an example of first input information related to the father 11.

[0055] Here, we will explain the "guest account." By registering as a user in the support system 6 and registering each medical institution to be used, a user can receive the functions of the support system 6 for the registered medical institution. However, as mentioned above, registering each medical institution to be used requires that the user visits the medical institution.

[0056] 3 and 4 is an account for which user registration of the father 11 in the support system 6 has been completed, but registration with each medical institution to be used has not been completed. In one embodiment, such an account is referred to as a "guest account" to distinguish it from a (normal) account for which user registration in the support system 6 and registration with each medical institution to be used have been completed.

[0057] Even with a guest account, the child 14 who is registered as a family member can receive the functions of the support system 6. After creating a guest account, when the father 11 visits a medical institution that is affiliated with the support system 6, he can convert the guest account into a (normal) account by completing registration for each medical institution he visits.

[0058] At symbol A9, the APP8 of the terminal 2 displays a registration confirmation screen 2G on the display device. The registration confirmation screen 2G may include a display area 2G1 for the user information entered on the guest account creation screen 2F, a "No" button 2G2, and a "Yes" button 2G3. If the content of the display area 2G1 is incorrect, the father 11 presses the "No" button 2G2, and if the content is correct, the father 11 presses the "Yes" button 2G3. When the "No" button 2G2 is pressed, the APP8 displays the guest account creation screen 2F on the display device to allow the father 11 to correct the input content.

[0059] At reference symbol A10, when the "Yes" button 2G3 is pressed, the APP 8 of the terminal 2 transmits to the server 5 the input user information of the father 11 and the patient ID (identification information) of the child 14 acquired at reference symbol A4.

[0060] The server 5 stores the user information of the father 11 associated with the child 14 in the DB, and responds to the APP 8 of the terminal 2 that the registration is complete. By storing the user information of the father 11 in the DB of the server 5, the creation of the guest account for the father 11 is completed.

[0061] In this way, the terminal 2 completes the creation of a guest account for the father 11 associated with the child 14 by sending an account creation request to the server 5. This makes it possible to reduce consumption of processing resources and network resources of the terminal 2 and the server 5 compared to creating an account and registering the family separately.

[0062] As described above, the screens 2C to 2G shown in FIGS. 3 and 4 are examples of one or more first screens for creating an account (guest account) for the father 11 in association with the child 14 indicated by the patient ID.

[0063] At symbol A11, the APP 8 of the terminal 2 displays a registration completion screen 2H on the display device in response to notification of the completion of registration from the server 5. The registration completion screen 2H is a screen notifying the father 11 that the creation of a guest account has been completed, and may include an "OK" button 2H1.

[0064] At symbol A12, when the "OK" button 2H1 is pressed, the APP 8 of the terminal 2 displays a login screen 2I on the display device. The login screen 2I is the same screen as the login screen 2A of FIG. 3, and may include an input field 2I1 for a login ID and password, and a "Login" button 2I2. The father 11 enters the login ID and password of the guest account registered at symbols A8 and A9 in the input field 2I1, and presses the "Login" button 2I2.

[0065] At reference symbol A13, the APP 8 of the terminal 2 displays a main screen 2J on the display device. The main screen 2J is a screen that displays information about the user (child 14) associated with the guest account when logging in to the APP 8 with a guest account.

[0066] The main screen 2J may include a display area 2J1 for information about the child 14 and Hospital A, and a user switching icon 2J2. The display area 2J1 may display patient information about the child 14 at Hospital A, such as the user information of the child 14 and information such as the patient card number. The father 11 can use the functions provided by the support system 6 for the child 14 by pressing the display area 2J1 (for example, by pressing the ">" button).

[0067] At symbol A14, when the user switching icon 2J2 is pressed, the APP 8 of the terminal 2 displays a user switching screen 2K on the display device. The user switching screen 2K is a screen for switching the user displayed on the main screen 2J, and may include links 2K1 to 2K3 for selecting the user to be displayed.

[0068] Link 2K1 is a link for selecting the father 11 who is a user of the guest account, and link 2K2 is a link for selecting the child 14 who is a user who has already been registered as a family member for the guest account. Link 2K3 is a link for registering other family members.

[0069] At symbol A15, when link 2K1 is selected, APP8 of terminal 2 displays main screen 2L on the display device. Main screen 2L is a screen that displays information about father 11, who is the user of the guest account, and is the first screen that is displayed after logging in if the account is a (normal) account.

[0070] As described above, since no medical institution is associated with the guest account, the main screen 2L may display a message that no medical institution is registered and a camera icon 2L1 for registering a medical institution.

[0071] For example, when the camera icon 2L1 is pressed, the APP 8 of the terminal 2 may display on the display device a screen (not shown) for reading a two-dimensional code for registering a medical institution in a guest account. The method of registering a medical institution in a guest account can be realized by a known method in the support system 6.

[0072] As described above, according to the account creation system 1 of one embodiment, the terminal 2 can create an account for the father 11 by reading the two-dimensional code 41 displayed on the terminal 4, and associate the account with the child 14 who has a predetermined relationship with the father 11.

[0073] This allows a father 11 who does not have an account for the support system 6 to create an account on the spot and use the functions of the support system 6 relating to the child 14, even if the father 11 visits a medical institution with his child 14.

[0074] Furthermore, for a user in the same situation as father 11, medical institutions can simply display two-dimensional code 41 on terminal 4, and the processing burden will be the same as when, for example, mother 13 with an account brings her child 14. In other words, medical institutions can reduce costs for personnel, computer resources (for example, information storage resources, processing resources for information search and information registration, and network resources) and the like required to deal with users in the same situation as father 11.

[0075] [C] Second operation example of one embodiment Next, a second operation example of the account creation system 1 according to an embodiment will be described with reference to Fig. 6 and Fig. 7. Fig. 6 and Fig. 7 are diagrams for describing the second operation example of the account creation system 1 according to an embodiment. Fig. 6 and Fig. 7 illustrate an example in which a father 11 creates an account for the father 11 linked to the child 14 before visiting Hospital A with the child 14 to accompany the child 14 to a medical examination at Hospital A (or before meeting with the staff 12 at Hospital A). As an example, a case will be illustrated in which the father 11 uses the terminal 2 at home to read the two-dimensional code 31 displayed on the terminal 3 of the mother 13.

[0076] At B1 in FIG. 6, the mother 13 logs in to the APP 8 of the terminal 3 using her account and performs an operation to display the setting screen 3A.

[0077] In reference symbol B2, APP8 of terminal 3 displays setting screen 3A on the display device of terminal 3. Setting screen 3A is a screen for making various settings related to APP8, and may include link 3A1 for "Display registered two-dimensional code." Mother 13 presses link 3A1.

[0078] When link 3A1 is pressed, APP8 of terminal 3 displays registration two-dimensional code selection screen 3B on the display device. Registration two-dimensional code selection screen 3B is a screen for selecting users (users whose identification information is to be included in the two-dimensional code) for registering a two-dimensional code for family registration from all users associated with the account, including the account holder (mother 13). Mother 13 presses link 3B1 for "Taro XXXX," her child 14.

[0079] At reference symbol B4, the APP 8 of the terminal 3 outputs a two-dimensional code 31 for family registration of information on the child 14. For example, the APP 8 of the terminal 3 displays a two-dimensional code display screen 3C on the display device in response to an operation by the mother 13.

[0080] As shown in FIG. 6, the two-dimensional code display screen 3C may include the name of the child 14 and a two-dimensional code 31 for registering the child 14 as a family member.

[0081] 8 is a diagram showing a second example of information included in the two-dimensional code 31. As shown in FIG. 8, the two-dimensional code 31 may include the same items as the two-dimensional code 41 exemplified in FIG.

[0082] Here, in the second operation example, authentication regarding family registration has not been performed by the staff member 12. In other words, at the time of symbol B4, the support system 6 is in a state where it cannot guarantee that the father 11 will register the child 14 as a family member. Therefore, in the second operation example, when the two-dimensional code 31 is output by a terminal other than the medical institution terminal, for example, the terminal 3, the authentication necessity information may be set to information indicating "required."

[0083] When the APP8 of the terminal 3 outputs the two-dimensional code 31, if there are multiple medical institutions associated with the child 14, the APP8 may output the two-dimensional code 31 including, for example, the patient ID of the child 14 associated with the medical institution with the smaller medical institution ID. In this case, after creating a guest account for the father 11, the child 14 can be associated with the guest account for the medical institutions that were not selected using a known method in the support system 6.

[0084] Returning to the explanation of Figure 6, at reference symbol B5, the father 11 starts up APP8 on the terminal 2, and a login screen 2A similar to that of Figure 3 is displayed on the display device of the terminal 2. Note that it does not matter whether reference symbols B1 to B4 or reference symbol B5 are performed first. Note that, since the processing from reference symbol B5 onwards is in response to the operation of the terminal 2 by the father 11, illustrations of the father 11 on each screen are omitted.

[0085] In reference symbol B6, APP8 of terminal 2 displays a two-dimensional code reading screen 2B' on the display device. The two-dimensional code reading screen 2B' may include a two-dimensional code reading frame 2B1. Father 11 uses a code reading device provided in terminal 2, such as a camera that captures an image of two-dimensional code 31, to capture the image of two-dimensional code 31 displayed on the display device of terminal 3.

[0086] As in the first operation example, the APP8 of the terminal 2 converts the read two-dimensional code 31 into a string of characters using image analysis processing, decodes the string of characters, and obtains the medical institution ID, medical institution name, patient ID, patient name, patient information, etc., and authentication requirement information contained in the two-dimensional code 31.

[0087] At symbol B7 in Figure 7, APP8 of terminal 2 displays the registered two-dimensional code authentication screen 2M on the display device because the acquired authentication necessity information indicates "required" (because two-dimensional code 41 was output by terminal 3).

[0088] The registration two-dimensional code authentication screen 2M is an example of a second screen for performing authentication processing for the patient (child 14) identified by the patient ID, and may include an input field 2M1 for inputting user information of the child 14 used in the authentication processing, such as the child's name in kana and date of birth, and a "Next" button 2M2. The father 11 inputs the user information of the child 14 in the input field 2M1 and presses the "Next" button 2M2. Note that the user information requested to be input in the input field 2M1 is not limited to the above-described information, and may be various information that can be used to authenticate that the father 11 has a predetermined relationship with the child 14. The user information of the child 14 input in the input field 2M1 is an example of second input information for the child 14.

[0089] At symbol B8, when the "Next" button 2M2 is pressed, the APP8 of the terminal 2 transmits to the server 5 the user information of the child 14 entered in the input area 2M1 and the patient ID (identification information) of the child 14 acquired at symbol B6.

[0090] The server 5 determines whether user information matching the user information and patient ID received from the terminal 2 is stored in the DB, and if matching user information is stored in the DB, it sends an authentication result indicating "success (OK)" to the APP8 of the terminal 2.

[0091] At symbol B9, when the APP 8 of the terminal 2 receives an authentication result indicating "success (OK)" from the server 5 (when the authentication process is successful), it displays on the display device a registered two-dimensional code information confirmation screen 2C similar to symbol A5 in Fig. 3. After the father 11 presses the "Next" button 2C2, the processes from symbol A6 in Fig. 3 onwards are executed.

[0092] As described above, the second operation example can also achieve the same effect as the first operation example. Furthermore, according to the second operation example, even when the two-dimensional code 31 is displayed on a terminal 3 different from the terminal 4 used by the medical institution, the security level related to family registration can be maintained at the same level as when the two-dimensional code 41 is displayed on the terminal 4.

[0093] Furthermore, when the authentication necessity information indicates "required" (in the case of the second operation example), authentication processing is performed, and when the authentication necessity information indicates "not required" (in the case of the first operation example), authentication processing is omitted. This makes it possible to prevent unnecessary authentication processing from being performed, which is highly convenient. Furthermore, when authentication processing can be omitted, consumption of processing resources and network resources of the terminal 2 and server 5 can be reduced.

[0094] [D] Hardware configuration example FIG. 9 is a block diagram showing an example of the hardware (HW) configuration of a computer 10 that realizes the functions of the terminal 2 according to an embodiment.

[0095] As shown in FIG. 9, the computer 10 may, as a HW configuration, illustratively include a processor 10a, a graphics processing unit 10b, a memory 10c, a storage unit 10d, an IF (Interface) unit 10e, an IO (Input / Output) unit 10f, and a reading unit 10g.

[0096] The processor 10a is an example of a processing unit that performs various controls and calculations. The processor 10a may be connected to each block in the computer 10 via a bus 10j so that they can communicate with each other. The processor 10a may be a multiprocessor including multiple processors, a multi-core processor having multiple processor cores, or a configuration having multiple multi-core processors.

[0097] The processor 10a may be, for example, an integrated circuit (IC) such as a CPU, MPU, APU, DSP, ASIC, or FPGA. Note that the processor 10a may be a combination of two or more of these integrated circuits. CPU is an abbreviation for Central Processing Unit, MPU is an abbreviation for Micro Processing Unit, APU is an abbreviation for Accelerated Processing Unit, DSP is an abbreviation for Digital Signal Processor, ASIC is an abbreviation for Application Specific IC, and FPGA is an abbreviation for Field-Programmable Gate Array.

[0098] The graphics processing device 10b controls screen display for an output device such as a monitor in the IO unit 10f. Examples of the graphics processing device 10b include various arithmetic processing devices, such as a GPU (Graphics Processing Unit), an APU, a DSP, an ASIC, an FPGA, or other integrated circuits (ICs).

[0099] The memory 10c is an example of HW that stores various types of data, programs, and other information. Examples of the memory 10c include one or both of a volatile memory such as a dynamic random access memory (DRAM) and a non-volatile memory such as a persistent memory (PM).

[0100] The storage unit 10d is an example of HW that stores various types of data, programs, and other information. Examples of the storage unit 10d include various storage devices such as a magnetic disk device such as a hard disk drive (HDD), a semiconductor drive device such as a solid state drive (SSD), and a nonvolatile memory. Examples of nonvolatile memory include a flash memory, a storage class memory (SCM), and a read-only memory (ROM).

[0101] The storage unit 10d may store a program 10h (account creation program) that realizes all or part of the various functions of the computer 10.

[0102] For example, the processor 10a of the terminal 2 can implement the function of the terminal 2 (for example, the control unit 20 shown in FIG. 10) described later by loading the program 10h stored in the storage unit 10d into the memory 10c and executing it.

[0103] The IF unit 10e is an example of a communication IF that controls connection and communication between the terminal 2 and other computers, such as the terminal 3, the terminal 4, the server 5, or the support system 6. For example, the IF unit 10e may include an adapter that complies with a LAN such as Ethernet (registered trademark) or optical communication such as FC (Fibre Channel). The adapter may be compatible with either or both of wireless and wired communication methods. The IF unit 10e may also include an adapter that complies with wireless communication technology such as a contactless IC.

[0104] For example, the terminal 2 may be connected to the support system 6 (server 5) illustrated in Fig. 1 so as to be able to communicate with each other via the IF unit 10e and the network 7. The program 10h may be downloaded to the computer 10 from the network via the communication IF and stored in the storage unit 10d.

[0105] The IO unit 10f may include one or both of an input device and an output device. Examples of input devices include a keyboard, a mouse, a touch panel, and a camera. Examples of output devices include a display device such as a monitor, a projector, and a printer. The IO unit 10f may also include a touch panel or the like that integrates an input device and a display device. The display device may be connected to the graphics processing device 10b. Screens 2A to 2M shown in FIGS. 3, 4, 6, and 7 may be displayed on the display device of the IO unit 10f. The terminal 2 may read the two-dimensional code 31 or 41 using a camera, which is an input device of the IO unit 10f.

[0106] The reading unit 10g is an example of a reader that reads data and program information recorded on the recording medium 10i. The reading unit 10g may include a connection terminal or device to which the recording medium 10i can be connected or inserted. Examples of the reading unit 10g include an adapter that complies with USB (Universal Serial Bus) or the like, a drive device that accesses a recording disk, and a card reader that accesses a flash memory such as an SD card. Note that the recording medium 10i may store the program 10h, and the reading unit 10g may read the program 10h from the recording medium 10i and store it in the memory unit 10d.

[0107] Examples of the recording medium 10i include non-transitory computer-readable recording media such as magnetic / optical disks and flash memories. Examples of magnetic / optical disks include flexible disks, CDs (Compact Discs), DVDs (Digital Versatile Discs), Blu-ray Discs, and HVDs (Holographic Versatile Discs). Examples of flash memories include semiconductor memories such as USB memories and SD cards.

[0108] The above-described HW configuration of the computer 10 is an example. Therefore, the HW in the computer 10 may be increased or decreased (for example, adding or deleting any block), divided, integrated in any combination, or the HW may be added or deleted as needed.

[0109] Each of the computers that realize the functions of the terminal 3, the terminal 4, and the server 5 may have the same hardware configuration as the computer 10 illustrated in Fig. 9. For example, the display devices of the terminals 3 and 4 may be an example of the IO unit 10f of the computer 10 that realizes the functions of the terminals 3 and 4.

[0110] [E] Software configuration example 10 is a block diagram showing an example of the software configuration of the account creation system 1 according to an embodiment. Hereinafter, an example of the software configuration of the account creation system 1 will be described with reference to FIG.

[0111] 10, the terminal 2 may illustratively include a display control unit 201, a two-dimensional code acquisition unit 202, an authentication processing unit 203, and a user registration unit 204. These blocks 201 to 204 are an example of the control unit 20, and may be, for example, part of an APP 8 installed in the terminal 2, and may be realized by the hardware of a computer 10 (see FIG. 9) serving as the terminal 2.

[0112] The display control unit 201 controls the display of screens 2A to 2M (see FIGS. 3, 4, 6, and 7) on the display device of the terminal 2.

[0113] The two-dimensional code acquisition unit 202 reads the two-dimensional code 31 output by the terminal 3 or the two-dimensional code 41 output by the terminal 4 using an input device such as a camera or a wireless communication adapter.

[0114] In addition, the two-dimensional code acquisition unit 202 converts the read two-dimensional code 31 or 41 into a string of characters using image analysis processing, and by decoding the string of characters, acquires the medical institution ID, medical institution name, patient ID, patient name, patient information, etc., and authentication requirement information contained in the two-dimensional code 31 or 41.

[0115] The authentication processing unit 203 performs authentication processing in accordance with the information acquired by the two-dimensional code acquisition unit 202 .

[0116] For example, if the authentication necessity information acquired by the two-dimensional code acquisition unit 202 indicates "not required," the authentication processing unit 203 determines that authentication processing will not be performed and causes the display control unit 201 to display a registered two-dimensional code information confirmation screen 2C, which is an example of one or more first screens.

[0117] On the other hand, if the authentication necessity information acquired by the two-dimensional code acquisition unit 202 indicates "required," the authentication processing unit 203 determines to perform authentication processing and causes the display control unit 201 to display the registered two-dimensional code authentication screen 2M, which is an example of the second screen.

[0118] The authentication processing unit 203 performs authentication processing by sending an authentication request including the input information (second input information) entered on the registered two-dimensional code authentication screen 2M and the patient ID acquired by the two-dimensional code acquisition unit 202 to the server 5. Upon receiving a response indicating successful authentication (an authentication result indicating "success (OK)") from the server 5, the authentication processing unit 203 causes the display control unit 201 to display a registered two-dimensional code information confirmation screen 2C, which is an example of one or more first screens.

[0119] On the other hand, when a response indicating authentication failure (an authentication result indicating "failed (NG)") is received from the server 5, the authentication processing unit 203 may cause the display control unit 201 to re-display the registered two-dimensional code authentication screen 2M and retry the authentication process. Furthermore, when the authentication processing unit 203 receives a response indicating authentication failure a predetermined number of times or more, it may instruct the display control unit 201 to display a screen indicating that the account creation has failed.

[0120] The user registration unit 204 creates a guest account for the first user associated with the second user in accordance with an operation input on one or more first screens. For example, the user registration unit 204 performs the guest account creation process by sending to the server 5 a creation request including the user information of the father 11 input on a guest account creation screen 2F, which is an example of one or more first screens, and the patient ID of the child 14 acquired by the two-dimensional code acquisition unit 202.

[0121] When the user registration unit 204 is notified by the server 5 that the creation (registration) of the guest account has been completed, the user registration unit 204 causes the display control unit 201 to display a registration completion screen 2H.

[0122] 10, the terminal 3 includes a two-dimensional code display control unit 301. The two-dimensional code display control unit 301 may be, for example, a part of the APP8 installed in the terminal 3, and may be realized by the hardware of the computer 10 (see FIG. 9) serving as the terminal 3.

[0123] Since the same APP8 is installed in each of terminal 2 and terminal 3, terminal 2 and terminal 3 may each include blocks 201 to 204 of terminal 2 and block 301 of terminal 3 shown in FIG.

[0124] In response to the operation of the terminal 3 by the mother 13, the two-dimensional code display control unit 301 queries the server 5 for registered family users associated with the account currently logged in to the APP8, and obtains user information of the registered family users from the server 5.

[0125] Furthermore, the two-dimensional code display control unit 301 displays on the display device of the terminal 3 a registration two-dimensional code selection screen 3B for selecting the user of the currently logged-in account and a registered family user acquired from the server 5.

[0126] The two-dimensional code display control unit 301 displays on the display device a two-dimensional code display screen 3C that displays the two-dimensional code 31 related to the user selected on the registration two-dimensional code selection screen 3B.

[0127] 10, the terminal 4 includes a two-dimensional code display control unit 401. The two-dimensional code display control unit 401 may be, for example, a part of the APP 9 installed in the terminal 4, or may be realized by the hardware of the computer 10 (see FIG. 9) serving as the terminal 4.

[0128] In response to the operation of the terminal 4 by the staff member 12, the two-dimensional code display control unit 401 displays a two-dimensional code display screen 2B on the display device of the terminal 4, which displays a two-dimensional code 41 based on the user information of the selected user (e.g., user information obtained from the server 5).

[0129] 10, the server 5 includes a DB 501, an authentication unit 502, and a user information registration unit 503. The DB 501, the authentication unit 502, and the user information registration unit 503 may be, for example, part of the functions of the support system 6, and may be realized by the hardware of the computer 10 (see FIG. 9) serving as the server 5.

[0130] The DB 501 stores user information used in the support system 6. Fig. 11 is a diagram showing an example of user information stored in the DB 501.

[0131] As shown in FIG. 11, the DB 501 may store, as user information, information such as account information for the support system, registered medical institution information, and registered family information, for example.

[0132] The account information of the support system is information about the user's account (including a guest account) for using the support system 6, and may include information such as the user ID, user name, name in kana, gender, date of birth, and password.

[0133] The registered medical institution information is information about a medical institution associated with the account information, and may include, for example, information such as a medical institution ID, a medical institution name, a patient ID (of the user at the medical institution), a patient name, a kana name, a gender, a date of birth, etc. When multiple medical institutions are associated with the account information, the registered medical institution information may have an item for each medical institution, or an entry may be prepared for each medical institution.

[0134] The registered family information is information about users such as family members associated with the account information, and may include, for example, information such as a patient ID, patient name, medical institution ID, name in kana, gender, date of birth, etc. When multiple users are associated with the account information, the registered family information may have an item for each associated user (family member), or an entry may be prepared for each associated user (family member).

[0135] 11, for convenience, DB501 is shown in a table format, but is not limited to this. DB501 may store user information in various formats, such as DB format or array format. Also, in FIG. 11, for convenience, DB501 is shown as information in one table (DB), but is not limited to this, and DB501 may be information combining multiple tables (DBs). In other words, the record and column configuration of DB501 is not limited to the configuration shown in FIG. 11.

[0136] When the authentication unit 502 receives an authentication request from the authentication processing unit 203 of the terminal 2, it determines whether or not a user matching the input information (e.g., name in kana, date of birth) and patient ID included in the authentication request exists in the DB 501. For example, the authentication unit 502 may search for an entry that matches the input information and patient ID included in the authentication request from the patient ID, name in kana, and date of birth included in the registered medical institution information or registered family information.

[0137] If the search finds a matching user, the authentication unit 502 transmits an authentication result indicating "success (OK)" to the terminal 2 in response to the authentication request. On the other hand, if a matching user does not exist, the authentication unit 502 transmits an authentication result indicating "failure (NG)" to the terminal 2 in response to the authentication request.

[0138] When the user information registration unit 503 receives a creation request from the user registration unit 204 of the terminal 2, it creates an entry in the DB 501, using the user information included in the creation request as account information for the support system 6 and the patient ID included in the creation request as registered family information.

[0139] When the user information registration unit 503 creates an entry in the DB 501, it notifies the completion of the creation (registration) of the guest account as a response to the creation request.

[0140] [F] Example of terminal operation of account creation system Next, an example of the operation of the terminal 2 of the account creation system 1 according to an embodiment will be described. Fig. 12 is a flowchart for explaining an example of the operation of the terminal 2 of the account creation system 1 according to an embodiment.

[0141] In the following explanation, it is assumed that the two-dimensional code 31 is displayed on the display device of terminal 3 by the two-dimensional code display control unit 301 of terminal 3, or that the two-dimensional code 41 is displayed on the display device of terminal 4 by the two-dimensional code display control unit 401 of terminal 4.

[0142] As shown in FIG. 12, the two-dimensional code acquisition unit 202 of the terminal 2 acquires the two-dimensional code 31 or 41 from the terminal 3 or 4 (step S1).

[0143] The two-dimensional code acquisition unit 202 acquires at least the patient ID and authentication necessity information from the decoded result of the acquired two-dimensional code 31 or 41 (step S2).

[0144] The authentication processing unit 203 of the terminal 2 determines whether the authentication necessity information indicates that authentication is "necessary" (step S3).

[0145] If the authentication necessity information indicates that authentication is "unnecessary" (NO in step S3), the process proceeds to step S5.

[0146] If the authentication necessity information indicates that authentication is "required" (YES in step S3), the authentication processing unit 203 causes the display control unit 201 to display the registered two-dimensional code authentication screen 2M and executes authentication processing (step S4). For example, the authentication processing unit 203 may determine that authentication has been successful when it transmits an authentication request to the server 5 and receives an authentication result indicating "success (OK)" from the server 5 (authentication unit 502). After authentication is successful, the process proceeds to step S5.

[0147] In step S5, the display control unit 201 displays screens 2C to 2E (see FIG. 3) such as a family registration confirmation screen and a terms and conditions agreement screen.

[0148] The user registration unit 204 of the terminal 2 causes the display control unit 201 to display the guest account creation screen 2F (see FIG. 4) (step S6).

[0149] The user registration unit 204 transmits the user information and patient ID entered in the input field 2F1 to the server 5 in response to pressing of the "Yes" button 2G3 on the registration confirmation screen 2G (see FIG. 4) (step S7).

[0150] When the user registration unit 204 receives a response indicating the completion of registration from the server 5 (user information registration unit 503), it causes the display control unit 201 to display the registration completion screen 2H (step S8), and the process ends.

[0151] [G] Other The technology according to the embodiment described above can be implemented with the following modifications and variations.

[0152] For example, at least one of the screens 2A to 2M shown in FIGS. 3, 4, 6, and 7 may be a dialog or a pop-up, and may be displayed on the display device of the terminal 2 in various other modes.

[0153] 3, 4, 6, and 7 show screen transitions within APP 8 as examples, but the present invention is not limited to this. At least one of screens 2A to 2M may be a screen displayed on a display device when an application such as a web browser installed on terminal 2 executes content provided by a web server of support system 6.

[0154] Furthermore, in one embodiment, an example is given in which terminal 2 creates an account in support system 6, but this is not limited to this, and the method of one embodiment can also be applied in cases in which terminal 2 creates accounts in various other systems.

[0155] Furthermore, the software configurations provided in the respective devices of terminals 2 to 4 and server 5 shown in FIG. 10 may be combined in any combination in each device, or may be divided into separate parts.

[0156] [H] Note The following additional notes are provided regarding the above-described embodiments.

[0157] (Appendix 1) On the first computer used by the first user, reading a code output from a second computer accessing a system that supports users' use of a medical institution when the first user creates an account for accessing the system; From the read code, first information indicating whether the second computer is a predetermined terminal used by a person related to the medical institution and second information identifying a second user who has a predetermined relationship with the first user are obtained; When the first information is information corresponding to the second computer being the predetermined terminal, displaying one or more first screens for creating a first account of the first user in association with the second user indicated by the second information; If the first information is information corresponding to the second computer not being the predetermined terminal, displaying a second screen for performing authentication processing for the second user indicated by the second information, and if the authentication processing on the second screen is successful, displaying the one or more first screens; creating the first account associated with the second user in response to an operation input on the one or more first screens; The account creation program that runs the process.

[0158] (Appendix 2) the creating process includes a process of creating the first account associated with the second user by sending first input information about the first user acquired by the operation input on the first screen and the second information to the system. The account creation program described in Appendix 1.

[0159] (Appendix 3) The authentication process includes: transmitting second input information about the second user and the second information acquired by operation input on the second screen to the system; receiving, from the system, an authentication result regarding the second user based on the second input information and the second information; 2. An account creation program as set forth in Appendix 1 or Appendix 2.

[0160] (Appendix 4) the second computer is a computer used by a third user who has the predetermined relationship with both the first user and the second user and who has a second account associated with the second user; An account creation program according to any one of Supplementary Note 1 to Supplementary Note 3.

[0161] (Appendix 5) the code is a two-dimensional code, The process of acquiring the code includes a process of capturing an image of the two-dimensional code displayed on a display device of the second computer with an imaging device of the first computer. An account creation program according to any one of Supplementary Note 1 to Supplementary Note 4.

[0162] (Appendix 6) A first computer used by a first user is reading a code output from a second computer accessing a system that supports users' use of a medical institution when the first user creates an account for accessing the system; From the read code, first information indicating whether the second computer is a predetermined terminal used by a person related to the medical institution and second information identifying a second user who has a predetermined relationship with the first user are obtained; When the first information is information corresponding to the second computer being the predetermined terminal, displaying one or more first screens for creating a first account of the first user in association with the second user indicated by the second information; If the first information is information corresponding to the second computer not being the predetermined terminal, displaying a second screen for performing authentication processing for the second user indicated by the second information, and if the authentication processing on the second screen is successful, displaying the one or more first screens; creating the first account associated with the second user in response to an operation input on the one or more first screens; How to create an account to process your transactions.

[0163] (Appendix 7) the creating process includes a process of creating the first account associated with the second user by sending first input information about the first user acquired by the operation input on the first screen and the second information to the system. How to create an account as described in Appendix 6.

[0164] (Appendix 8) The authentication process includes: transmitting second input information about the second user and the second information acquired by operation input on the second screen to the system; receiving, from the system, an authentication result regarding the second user based on the second input information and the second information; How to create an account as described in Appendix 6 or Appendix 7.

[0165] (Appendix 9) the second computer is a computer used by a third user who has the predetermined relationship with both the first user and the second user and who has a second account associated with the second user; An account creation method according to any one of Supplementary Notes 6 to 8.

[0166] (Appendix 10) the code is a two-dimensional code, The process of acquiring the code includes a process of capturing an image of the two-dimensional code displayed on a display device of the second computer with an imaging device of the first computer. An account creation method according to any one of Supplementary Notes 6 to 9.

[0167] (Appendix 11) A first information processing device used by a first user, When the first user creates an account for accessing a system that supports users in using medical institutions, a code output from a second information processing device that accesses the system is read; obtain, from the read code, first information according to whether the second information processing device is a predetermined terminal used by a person related to the medical institution, and second information identifying a second user who has a predetermined relationship with the first user; When the first information is information corresponding to the fact that the second information processing device is the predetermined terminal, displaying one or more first screens for creating a first account of the first user in association with the second user indicated by the second information; When the first information is information corresponding to the fact that the second information processing device is not the predetermined terminal, displaying a second screen for performing authentication processing for the second user indicated by the second information, and when the authentication processing on the second screen is successful, displaying the one or more first screens; creating the first account associated with the second user in response to an operation input on the one or more first screens; An information processing device comprising a control unit.

[0168] (Appendix 12) In the creation process, the control unit creates the first account associated with the second user by sending first input information about the first user acquired by the operation input on the first screen and the second information to the system. 12. The information processing device according to claim 11.

[0169] (Appendix 13) The control unit, in the authentication process, transmitting second input information about the second user and the second information acquired by operation input on the second screen to the system; receiving, from the system, an authentication result regarding the second user based on the second input information and the second information; 13. The information processing device according to claim 11 or 12.

[0170] (Appendix 14) the second information processing device is an information processing device used by a third user who has the predetermined relationship with both the first user and the second user and who has a second account associated with the second user; An information processing device according to any one of Supplementary notes 11 to 13.

[0171] (Appendix 15) the code is a two-dimensional code, In the process of acquiring the code, the control unit captures an image of the two-dimensional code displayed on a display device of the second information processing device with an imaging device of the first information processing device. An information processing device according to any one of Supplementary Note 11 to Supplementary Note 14. [Explanation of symbols]

[0172] 1. Account Creation System 10a processor 10b Graphics Processing Unit 10c memory 10d storage section 10e IF section 10f IO section 10g reading unit 10-hour program 10i recording media 10j bus 11 Father 12 staff 13 Mother 14. Children 2,3,4 terminals 2A~2M,3A~3C,4A screen 201 Display control unit 202 Two-dimensional code acquisition unit 203 Authentication processing section 204 User Registration Section 31,41 2D code 301,401 Two-dimensional code display control unit 5 Server 501 DB 502 Authentication Department 503 User Information Registration Department 6. Support System 7 Network

Claims

1. A first computer used by a first user reading a code output from a second computer accessing a system that supports users' use of a medical institution when the first user creates an account for accessing the system; From the read code, first information indicating whether the second computer is a predetermined terminal used by a person associated with the medical institution and second information identifying a second user who has a predetermined relationship with the first user are obtained; When the first information is information corresponding to the second computer being the predetermined terminal, displaying one or more first screens for creating a first account of the first user in association with the second user indicated by the second information; If the first information is information corresponding to the second computer not being the predetermined terminal, displaying a second screen for performing authentication processing for the second user indicated by the second information, and if the authentication processing on the second screen is successful, displaying the one or more first screens; creating the first account associated with the second user in response to an operation input on the one or more first screens; The account creation program that runs the process.

2. the creating process includes a process of creating the first account associated with the second user by sending first input information about the first user acquired by the operation input on the first screen and the second information to the system. The account creation program according to claim 1 .

3. The authentication process includes: transmitting second input information related to the second user and the second information acquired by operation input on the second screen to the system; receiving, from the system, an authentication result regarding the second user based on the second input information and the second information; 3. The account creation program according to claim 1.

4. the second computer is a computer used by a third user who has the predetermined relationship with both the first user and the second user and who has a second account associated with the second user; 3. The account creation program according to claim 1.

5. the code is a two-dimensional code, the process of acquiring the code includes a process of capturing an image of the two-dimensional code displayed on a display device of the second computer with an imaging device of the first computer.

3. The account creation program according to claim 1.

6. A first computer used by a first user, reading a code output from a second computer accessing a system that supports users' use of a medical institution when the first user creates an account for accessing the system; From the read code, first information indicating whether the second computer is a predetermined terminal used by a person associated with the medical institution and second information identifying a second user who has a predetermined relationship with the first user are obtained; When the first information is information corresponding to the second computer being the predetermined terminal, displaying one or more first screens for creating a first account of the first user in association with the second user indicated by the second information; If the first information is information corresponding to the second computer not being the predetermined terminal, displaying a second screen for performing authentication processing for the second user indicated by the second information, and if the authentication processing on the second screen is successful, displaying the one or more first screens; creating the first account associated with the second user in response to an operation input on the one or more first screens; How to create an account to process your transactions.

7. A first information processing device used by a first user, When the first user creates an account for accessing a system that supports users in using medical institutions, a code output from a second information processing device that accesses the system is read; From the read code, first information according to whether the second information processing device is a predetermined terminal used by a person related to the medical institution and second information identifying a second user who has a predetermined relationship with the first user are obtained; When the first information is information corresponding to the second information processing device being the predetermined terminal, displaying one or more first screens for creating a first account of the first user in association with the second user indicated by the second information; When the first information is information corresponding to the fact that the second information processing device is not the predetermined terminal, a second screen for performing authentication processing for the second user indicated by the second information is displayed, and when the authentication processing on the second screen is successful, the one or more first screens are displayed; creating the first account associated with the second user in response to an operation input on the one or more first screens; An information processing device comprising a control unit.

Images