JP2019179508A - Information providing program, information providing method, and information providing device - Google Patents

Abstract

To provide an information providing program, an information providing method, and an information providing device for preventing unauthorized use of an insurance card at a medical institution or the like.SOLUTION: An information providing program is executed by a computer. The computer obtains, from a server device that holds insurance card information, a first token used for inquiring information on an insurance card identified by identification information notified from a terminal. The computer obtains, from a server device that holds information used by a medical institution, a second token used for inquiring information on a consultation ticket associated with the information notified from the terminal. The computer transmits, to the terminal, the information on the insurance card acquired using the first token and the information on the consultation ticket acquired using the second token, when receiving information indicating successful user authentication at the terminal and information specifying the medical institution from the terminal.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an information providing program, an information providing method, and an information providing apparatus.

  When a patient visits a medical institution such as a hospital, the patient presents a health insurance card together with an examination ticket issued by the medical institution. The medical institution confirms the patient's past history using the presented examination ticket, and determines the amount of the patient's share of the medical expenses using the health insurance card.

  As a related technology, a system has been proposed in which insurance card information of an insurance card using an IC (integrated circuit) card is stored in a storage device of a mobile phone owned by the insured and the mobile phone has an insurance card function. (For example, Patent Document 1).

JP 2002-351997 A

  Even if a patient submits a health insurance card or medical examination card to a medical institution, it is difficult for the medical institution to confirm whether the patient is using a health insurance card or medical examination card issued to the patient himself. For this reason, when a patient submits another person's health insurance card to a medical institution and tries to impersonate another person for medical treatment, it is extremely difficult for the medical institution to confirm that the impersonation is being performed. . Such a situation is not limited to the case where a health insurance card printed on paper is used, but as described in the background art, the insurance card is stored in the storage device of the mobile phone to have the insurance card function. It can also happen when the mobile phone is presented to a medical institution.

  An object of the present invention is to prevent unauthorized use of an insurance card in a medical institution or the like as one aspect.

  An information providing program according to one aspect is executed by a computer. The computer obtains a first token used for inquiring information on the insurance card identified by the identification information notified from the terminal from a server device that holds the insurance card information. The computer obtains a second token used for inquiry of information on the examination ticket associated with the information notified from the terminal from a server device that holds information used by the medical institution. When the computer receives information indicating that the user of the terminal has been successfully authenticated and information designating the medical institution from the terminal, the computer receives the information on the insurance card obtained using the first token, and the second token. The information of the examination ticket acquired by using is transmitted to the terminal.

  Unauthorized use of insurance cards at medical institutions can be prevented.

It is a figure explaining the example of the information provision method concerning embodiment. It is a figure explaining the example of the system in which the information provision method is used. It is a figure explaining the example of a correspondence table and an insured person database. It is a figure explaining the example of the hardware constitutions of an information processing apparatus and a server apparatus. It is a figure explaining the example of the hardware constitutions of a terminal and a reception device. It is a flowchart explaining the example of a registration process of insurance card information. It is a figure explaining the example of an insurance card database and a corresponding | compatible table. It is a flowchart explaining the example of registration processing of a medical examination ticket. It is a figure explaining the example of a hospital database and a corresponding table. It is a flowchart explaining the example of the registration process of a credit card. It is a figure explaining the example of a financial database and a corresponding table. It is a figure explaining the example of a display of the terminal before medical examination reception. It is a flowchart explaining the example of the reception process of a medical examination. It is a figure explaining the example of the update of the data performed in the case of the reception process of a medical examination. It is a figure explaining the example of a display of the terminal in the case of medical examination reception. It is a flowchart explaining the example of the payment process of a consultation fee. It is a figure explaining the example of the update of the data performed in the case of the payment process of a consultation fee. It is a figure explaining the example of a display of a terminal when the payment process of a consultation fee is performed. It is a flowchart explaining the example of the designation | designated process of a pharmacy. It is a figure explaining the example of the update of the data performed in the case of the designation | designated process of a pharmacy. It is a figure explaining the example of a display of the terminal in the case of a pharmacy designation | designated process. It is a figure explaining the example of the update of data when the designation | designated process of a pharmacy is performed. It is a flowchart explaining the example of the process performed at the time of reception of a medicine. It is a figure explaining the example of the update of the data performed at the time of reception of a medicine. It is a figure explaining the example of the display screen for medicine reception.

  FIG. 1 is a diagram illustrating an example of an information providing method according to the embodiment. The system in which the information providing method according to the embodiment is performed includes a receiving device 10, a terminal 20, an information processing device 30, a health insurance server 2, and a hospital server 4. The terminal 20 is a mobile phone terminal such as a smartphone carried by a user who is going to the hospital or a tablet, and whether or not an operator who operates the terminal 20 is a regular user of the terminal 20 in advance. Assume that information for authentication is held. The health insurance server 2 is a server managed by a health insurance association that issues health insurance cards (insurance cards), and holds information on insurance cards. The hospital server 4 is a server that manages patient information of a certain hospital (Y hospital). The reception device 10 is a device used for the reception process of Y hospital, and can communicate with the terminal 20. The information processing device 30 is a device that can provide the terminal 20 with information that the terminal 20 presents to the receiving device 10 in order to accept a user's examination.

  Hereinafter, an example of processing performed by the information providing method will be described in time series with reference to the sequence diagram of FIG. First, the user of the terminal 20 inputs identification information (A) included in the user's own health insurance card into the terminal 20 as pre-registration. The terminal 20 transmits the insurance card identification information (A) to the information processing apparatus 30 (step S1). The information processing device 30 requests the health insurance server 2 to issue an access token that can be used when inquiring about the insurance card identified by the identification information (A) (step S2). In response to a request from the information processing device 30, the health insurance server 2 generates an access token (α) for inquiring information on the insurance card identified by the identification information (A), and uses the access token (α) as the information processing device. 30 (steps S3 and S4). The information processing apparatus 30 stores the access token (α) (step S5).

  Further, as pre-registration, the user of the terminal 20 inputs information (B) on the examination ticket of the Y hospital to which the user is going to the terminal 20. The terminal 20 transmits the examination ticket information (B) to the information processing device 30 (step S6). The information processing apparatus 30 requests the hospital server 4 that holds the information of the Y hospital to issue an access token that can be used when inquiring about information related to the medical examination ticket identified by the medical examination ticket information (B) ( Step S7). In response to a request from the information processing apparatus 30, the hospital server 4 generates an access token (β) for referring to information on the examination ticket identified by the examination ticket information (B), and processes the access token (β). It transmits to the apparatus 30 (step S8, S9). The information processing apparatus 30 stores the access token (β) (step S10).

  Thereafter, it is assumed that the user of the terminal 20 tries to receive a medical examination at Y hospital. In order to start the examination reception process, the user inputs information specifying Y hospital to the terminal 20. Then, the terminal 20 performs an authentication process for determining whether the operator who performed the input process is an authorized user of the terminal 20. The authentication process performed at the terminal 20 may be an arbitrary authentication process. Note that the authentication process may be an authentication process including a verification process in the information processing apparatus 30 in addition to the authentication in the terminal 20, such as FIDO (Fast Identity Online) authentication. Here, it is assumed that the terminal 20 determines that the operator of the terminal 20 is an authorized user of the terminal 20 by the authentication process. Then, the terminal 20 notifies the information processing apparatus 30 of information indicating that the authentication process has been successful and information indicating that the hospital that receives the medical treatment is Y hospital (step S11). ).

  When the information processing apparatus 30 recognizes that the authentication success at the terminal 20 and the target of the medical treatment acceptance process are the Y hospital, the information processing apparatus 30 requests the health insurance server 2 for information on the user's insurance card using the access token α ( Step S12). Furthermore, the information processing apparatus 30 requests the hospital server 4 for information on the user's examination ticket using the access token β (step S13). It is assumed that the information processing apparatus 30 acquires the user's insurance card information from the health insurance server 2 and further acquires the user's examination ticket information from the hospital server 4 (steps S14 and S15). Then, the information processing apparatus 30 transmits the obtained information on the health insurance card and information on the examination ticket to the terminal 20 as information for reception processing (step S16). At this time, the information processing apparatus 30 can transmit, for example, an information code such as a QR (Quick Response) code including information on the health insurance card and information on the examination ticket to the terminal 20 as information for reception processing.

  The terminal 20 performs reception processing by providing the information on the insurance card and the information on the examination ticket received from the information processing device 30 to the reception device 10 (step S17). At this time, for example, the user of the terminal 20 displays the QR code (registered trademark) received as information for reception processing on the screen of the terminal 20, and images the QR code with the camera provided in the reception device 10, thereby making the insurance Information on the certificate and information on the examination ticket may be provided to the reception device 10.

  As described above, according to the information providing method according to the embodiment, when it is determined that the operator of the terminal 20 is an authorized user of the terminal 20 by the authentication process in the terminal 20, the insurance of the authorized user of the terminal 20 is obtained. Information on the certificate and the examination ticket is transmitted from the information processing apparatus 30 to the terminal 20. Accordingly, the authorized user of the terminal 20 can present the information acquired by the terminal 20 from the information processing apparatus 30 to the reception apparatus 10, thereby presenting the information on the insurance card pre-registered by the user to the reception apparatus 10 in the hospital. Furthermore, provision of insurance card information from the information processing apparatus 30 is not performed unless the authentication process at the terminal 20 is successful, so that if the authorized user of the terminal 20 is not the operator of the terminal 20, the terminal 20 Information on the health insurance card of the authorized user is not provided to the terminal 20. For this reason, according to the information providing method according to the embodiment, unauthorized use of the insurance card can be prevented.

  Note that the sequence diagram of FIG. 1 is merely an example of processing. For example, the processes of steps S1 to S5 may be performed in parallel with the processes of steps S6 to S10, and the processes of steps S1 to S5 may be performed after the processes of steps S6 to S10. Further, after the process of step S11, the information processing apparatus 30 acquires the insurance card information acquired from the health insurance server 2 before the notification in step S11 or the hospital server 4 before the notification in step S11. The information on the examination ticket that has been obtained may be transmitted in step S16. Furthermore, the information providing method according to the embodiment may be modified so that the information processing apparatus 30 can provide insurance card information to a pharmacy or the like.

<Example of system configuration and device configuration>
FIG. 2 is a diagram illustrating an example of a system in which the information providing method is used. FIG. 2 shows an example of a system in which the information processing apparatus 30 can provide insurance card information to a pharmacy. Furthermore, in the following example, the case where the authentication process performed to determine whether the operator of the terminal 20 is a regular user of the terminal 20 is FIDO authentication will be described as an example.

  The system includes a reception device 10a used for reception at a hospital, a reception device 10b used for reception at a pharmacy, a terminal 20, an information processing device 30, a health insurance server 2, a hospital server 4, a pharmacy server 6, and a financial institution server. 8 is included. The health insurance server 2 includes an insurance card database 3 in which insurance card information is recorded. The hospital server 4 includes a hospital database 5 in which information on hospital examination tickets is recorded. The pharmacy server 6 includes a pharmacy database 7 in which information related to pharmacy dispensing is recorded. The financial institution server 8 includes a financial database 9 that stores information related to payment processing using a credit card.

  The terminal 20 includes a communication unit 21, a camera 22, an application processing unit 23, an authentication processing unit 24, a display unit 25, and a storage unit 26. The communication unit 21 performs communication processing with the receiving device 10 and the information processing device 30. Accordingly, the application processing unit 23, the authentication processing unit 24, and the like can communicate with the information processing apparatus 30 and the like via the communication unit 21. The camera 22 performs an imaging process. The application processing unit 23 performs processing of an application used for processing for providing information. For example, the application processing unit 23 performs a drawing process of display screen data displayed on a screen included in the display unit 25, a process of an image captured by the camera 22, and the like. The authentication processing unit 24 performs FIDO authentication in order to determine whether the operator who operates the terminal 20 is an authorized user of the terminal 20. In the FIDO authentication, the authentication processing unit 24 operates as a FIDO client. The storage unit 26 stores data obtained by the processing of the camera 22, the application processing unit 23, and the authentication processing unit 24.

  The information processing apparatus 30 includes a communication unit 31, a healthcare information processing unit 32, and an authentication information processing unit 40. The communication unit 31 performs communication processing with the health insurance server 2, the hospital server 4, the pharmacy server 6, the financial institution server 8, and the terminal 20. Therefore, the authentication information processing unit 40 and the healthcare information processing unit 32 can communicate with the health insurance server 2 and the terminal 20 via the communication unit 31.

  The authentication information processing unit 40 includes an authentication processing unit 41, an acquisition unit 42, and a storage unit 50. The storage unit 50 includes PIN (personal identification number) information 51 and a correspondence table 52. The authentication processing unit 41 operates as a FIDO server. The authentication processing unit 41 performs the user's FIDO registration and FIDO authentication using the acquired information transmitted to and received from the terminal 20 operating as the FIDO client. The acquisition unit 42 acquires an access token for acquiring information on the insurance card issued to the user from the health insurance server 2. The PIN information 51 is information on a personal identification number used when registering insurance card information. The correspondence table 52 stores information regarding users who have succeeded in the FIDO authentication. An example of the correspondence table 52 will be described later.

  The healthcare information processing unit 32 includes a control unit 60 and a storage unit 70. The storage unit 70 includes hospital information 71, pharmacy information 72, and an insured person database 80. The hospital information 71 is information on a hospital that can receive medical treatment using the information providing method according to the embodiment. The hospital information 71 includes the address of the hospital server 4 of each hospital included in the hospital information 71. The pharmacy information 72 is information of a pharmacy that can accept a prescription and receive a medicine using the information providing method according to the embodiment. The pharmacy information 72 includes the address of the pharmacy server 6 of each pharmacy included in the pharmacy information 72, position information of each pharmacy, and the like. The insured person database 80 is a database that stores information on the insured person. Details of the insured person database 80 will be described later.

  The control unit 60 includes an acquisition unit 61, a QR code generation unit 62, a service processing unit 63, and an application control unit 64. The acquisition unit 61 acquires an access token for acquiring information on a medical examination ticket issued to a user who has succeeded in the FIDO authentication. The QR code generation unit 62 generates a QR code including information to be transmitted to the terminal 20. The service processing unit 63 performs update processing of the insured person database 80 by transmitting and receiving data to and from the hospital server 4, the pharmacy server 6, and the financial institution server 8 via the communication unit 31. The application control unit 64 transmits / receives data to / from the terminal 20 via the communication unit 31 to request an update of the screen display of the terminal 20.

  FIG. 3 is a diagram for explaining an example of the correspondence table 52 and the insured person database 80. The correspondence table 52 stores a health insurance access token, a Kureka access token identifier, a hospital access token identifier, and a pharmacy access token identifier for each FIDO-ID. Here, the FIDO-ID is an identifier that can uniquely identify each user who has succeeded in FIDO registration. The health insurance access token is an access token that can be used for inquiring information on the insurance card issued to the user identified by the FIDO-ID in the entry. The Creca access token identifier is an identifier for identifying an access token (creca access token) used for payment processing using a user's credit card identified by the FIDO-ID in the entry. The hospital access token identifier is an identifier for identifying an access token (hospital access token) that is used when acquiring the examination ticket information of the user identified by the FIDO-ID in the entry. The pharmacy access token identifier is an identifier for identifying an access token (pharmacy access token) used for notification of the dispensing result of the user's medicine identified by the FIDO-ID in the entry.

  The insured person database 80 includes an insured person information table 81, a hospital access token table 82, a Kureka access token table 83, and a pharmacy access token table 84. The insured person information table 81 stores information associated with a user who has successfully obtained the health insurance access token. The insured person information table 81 includes FIDO-ID, status information, position information, prescription information, dispensing result information, and payment information. The status information represents the current state of the user identified by the FIDO-ID in the entry. The status information is set to, for example, “waiting for medical care”, “waiting for prescription”, and the like. The position information is information representing the current position of the terminal 20 held by the user identified by the FIDO-ID in the entry. The prescription information is information on a prescription issued to the user of the terminal 20. The dispensing result information is a dispensing result of the user's medicine identified by the FIDO-ID in the entry. The payment information is information representing the payment status to the hospital or pharmacy for the user identified by the FIDO-ID in the entry.

  The hospital access token table 82 records the correspondence relationship between the hospital access token identifier, the hospital access token, and the information of the hospital that issued the access token. The credit card access token table 83 records the correspondence relationship between the credit card access token identifier, the credit card access token, and the information of the financial institution that issued the access token. The pharmacy access token table 84 records the correspondence relationship between the pharmacy access token identifier, the pharmacy access token, and information on the pharmacy that issued the access token.

  In the example of FIG. 3, the insured database 80 holds a hospital access token table 82, a cleka access token table 83, and a pharmacy access token table 84, but the correspondence table 52 does not include any access token other than the health insurance access token. As described above, when a plurality of access tokens are not directly associated with the FIDO-ID and recorded, the access tokens are held as compared with the case where all the access tokens are directly associated with the FIDO-ID. Security has been enhanced. However, FIG. 3 is an example, and the information elements in the table and the information elements in the insured person information table 81 can be changed according to the implementation.

  FIG. 4 is a diagram illustrating an example of the hardware configuration of the information processing apparatus 30 and the server apparatus. Each of the information processing device 30, health insurance server 2, hospital server 4, pharmacy server 6, and financial institution server 8 includes a processor 101, a memory 102, a bus 103, and a network connection device 104. The processor 101 is an arbitrary processing circuit, and can be a CPU (Central Processing Unit), for example. The processor 101 executes various processes by executing programs using the memory 102 as a working memory. The memory 102 includes a RAM (Random Access Memory), and further includes a nonvolatile memory such as a ROM (Read Only Memory). The memory 102 is used for storing data used for processing by the program and the processor 101. The network connection device 104 is used for communication with other devices via the network. The bus 103 connects the processor 101, the memory 102, and the network connection device 104 so that data can be input and output among them.

  In the information processing apparatus 30, the processor 101 operates as the authentication processing unit 41, the acquisition unit 42, and the control unit 60, and the memory 102 operates as the storage unit 50 and the storage unit 70. Further, the network connection device 104 operates as the communication unit 31. In the health insurance server 2, the insurance card database 3 is stored in the memory 102. In the hospital server 4, the hospital database 5 is stored in the memory 102, and in the pharmacy server 6, the pharmacy database 7 is stored in the memory 102. Further, in the financial institution server 8, the financial database 9 is stored in the memory 102. Any of the information processing device 30, the health insurance server 2, the hospital server 4, the pharmacy server 6, and the financial institution server 8 can be realized as a computer, a server device, or the like.

  FIG. 5 is a diagram illustrating an example of the hardware configuration of the terminal 20 and the receiving device 10. Each of the receiving device 10 and the terminal 20 includes a processor 111, a memory 112, an input device 113, a display device 114, a camera 22, a wireless processing circuit 116, and a bus 117. The terminal 20 further includes a biological information reader 118. The bus 117 connects the processor 111, the memory 112, the input device 113, the display device 114, the camera 22, and the wireless processing circuit 116 so that data can be input and output. The processor 111 is an arbitrary processing circuit, and may be a CPU, for example. The memory 112 includes a ROM and a RAM.

  In the terminal 20, the memory 112 operates as the storage unit 26. In the terminal 20, the processor 111 reads the program recorded in the ROM and realizes the application processing unit 23. The input device 113 is an arbitrary device used for inputting information, such as a touch panel and buttons, and the display device 114 is a display device including a display. The display unit 25 is realized by the processor 111 and the display device 114. The wireless processing circuit 116 performs wireless communication processing when the accepting device 10 and the terminal 20 communicate. The communication unit 21 of the terminal 20 is realized by the processor 111 and the wireless processing circuit 116. The biometric information reader 118 reads biometric information used for FIDO authentication and the like. Therefore, the authentication processing unit 24 is realized by the processor 111 and the biometric information reader 118. The terminal 20 is realized as a mobile phone terminal including a smartphone, a tablet, a computer, or the like.

<Embodiment>
Hereinafter, the embodiment is divided into insurance card registration processing, examination ticket registration processing, credit card registration processing, examination reception, examination fee payment processing, pharmacy designation processing for receiving medicine, and medicine reception processing. explain. It is assumed that an application for using the information providing method according to the embodiment is installed in the terminal 20 in advance.

(1) Insurance Card Registration Processing FIG. 6 is a flowchart for explaining an example of insurance card information registration processing. FIG. 7 is a diagram for explaining an example of the insurance card database 3 and the correspondence table 52. Hereinafter, an example of processing performed when registering a health insurance card will be described with reference to FIGS. 6 and 7. In the following description, it is assumed that the mail address used by the user is registered in advance in the health insurance server 2.

  It is assumed that the application processing unit 23 displays the insurance card registration screen on the display unit 25 in accordance with the processing of the user of the terminal 20. In this state, it is assumed that the user took a picture of the insurance card issued to the user using the camera 22 of the terminal 20 (step S21). The application processing unit 23 performs OCR (Optical character recognition) processing on the captured image to identify information such as the insurance card number and the insured person name printed on the insurance card. When the OCR process is performed on the image, the application processing unit 23 may use a formatless OCR technique using AI (artificial intelligence) as appropriate, or based on a pre-stored insurance card format. Individual information may be read. The application processing unit 23 transmits the obtained insurance card number and insured person's name to the information processing apparatus 30 via the communication unit 21 (step S22).

  The acquisition unit 42 of the information processing apparatus 30 acquires the insurance card number and the insured person name via the communication unit 31. The acquisition unit 42 issues a PIN used to register insurance card information. The acquiring unit 42 stores the issued PIN in the storage unit 50 as PIN information 51 in association with the information of the terminal 20. The acquisition unit 42 transmits the issued PIN to the health insurance server 2 together with the combination of the insurance card number and the insured person's name (step S23).

  When the health insurance server 2 receives the combination of the insurance card number and the insured person's name and the PIN, a valid insurance card including the received combination of the insurance card number and the insured person's name is registered in the insurance card database 3. (Step S24). When a valid insurance card including the combination of the insurance card number and the insured person name is not registered, the health insurance server 2 ends the process (No in step S24). When a valid insurance card including a combination of the insurance card number and the insured person's name is registered, the health insurance server 2 sends an email address registered in advance in association with the information of the insurance card whose registration is confirmed. The PIN is transmitted (Yes in step S24, step S25). It is assumed that the health insurance server 2 associates the PIN with the information on the health insurance card that triggered the issue of the PIN.

  When the user of the terminal 20 obtains the PIN by checking the mail, the user inputs the PIN to the terminal 20. For example, the user can display the PIN input screen by operating the terminal 20 and input the PIN on the PIN input screen. The application processing unit 23 transmits the input PIN to the information processing apparatus 30 (step S26).

  The acquisition unit 42 of the information processing device 30 collates the PIN received from the terminal 20 and the information of the terminal 20 with the PIN information 51 (step S27). If the PIN code verification fails, the acquisition unit 42 ends the process (No in step S27). If the verification of the PIN code is successful, the acquisition unit 42 transmits the verified PIN to the health insurance server 2 in order to request access to the member information of the insurance association and use authorization of the member information. (Step S28). In the following description, the process of requesting access to the member information of the insurance association and use authorization of the member information is performed by requesting the issuance of a health insurance access token. In other words, the request for the health insurance access token is a request for permission to use personal information related to the health insurance card such as the health insurance card number based on the result of identity verification at the terminal 20.

  When the health insurance server 2 receives the PIN from the information processing device 30, the health insurance server 2 generates a health insurance access token that can be used for inquiring information on the insurance card that triggered the issuance of the received PIN (step S29). The health insurance server 2 associates the health insurance access token with the information to be queried with the access token.

  The insurance card database 3 in FIG. 7 is an example of correspondence between health insurance access tokens and insurance card registration information. In the insurance card database 3 of FIG. 7, the name of the insured with the insurance card number = 1234567 is “Fujitsu Taro”. Is recorded. The health insurance server 2 transmits a health insurance access token to the information processing device 30.

  In step S <b> 30 of FIG. 6, the acquisition unit 42 in the information processing apparatus 30 registers the acquired health insurance access token in the correspondence table 52. The authentication processing unit 41 requests the terminal 20 for the user's FIDO authentication (step S31).

  In the terminal 20, the application processing unit 23 displays a screen for requesting the user to read biometric information on the display unit 25. The user causes the biometric information reader 118 to read biometric information such as the user's own fingerprint corresponding to the biometric information already registered. Then, the authentication processing unit 24 performs biometric authentication processing by comparing the biometric information of the user read from the biometric information reader 118 with biometric information registered in advance (step S32). If the biometric authentication fails, the authentication processing unit 24 ends the process (No in step S32). On the other hand, when the biometric authentication is successful, the authentication processing unit 24 generates a secret key and a public key for use in the authentication phase as an authenticator of the FIDO client. The authentication processing unit 24 notifies the information processing apparatus 30 of a public key as information indicating that biometric authentication has been successful (Yes in step S32).

  The authentication processing unit 41 of the information processing device 30 stores the public key received from the terminal 20 and generates a FIDO-ID for identifying the user of the terminal 20. Further, the authentication processing unit 41 registers the health access token acquired for the user of the terminal 20 in association with the FIDO-ID (step S33). The correspondence table 52a in FIG. 7 is an example when the health insurance access token and the FIDO-ID are registered. In the correspondence table 52a, the FIDO-ID “ID_A” is generated for the user of the health insurance access token “KNPT1”.

  FIG. 6 is an example of processing. For example, the processing order can be changed according to the implementation, such as the processing of steps S31 to S33 being performed in parallel with the processing of steps S28 to S30.

(2) Examination Ticket Registration Process FIG. 8 is a flowchart for explaining an example of the examination ticket registration process. FIG. 9 is a diagram illustrating an example of the hospital database 5 and the correspondence table 52. Hereinafter, an example of registration of an examination ticket will be described with reference to FIGS.

  It is assumed that the application processing unit 23 displays the registration screen for the examination ticket on the display unit 25 by the processing of the user of the terminal 20. In this state, the user of the terminal 20 takes a picture of the examination ticket using the camera 22 of the terminal 20 (step S42). The application processing unit 23 performs OCR processing on the photographed image, thereby specifying information such as the examination ticket number and name printed on the examination ticket (step S43). The application processing unit 23 transmits the obtained examination ticket number and name to the information processing apparatus 30. At this time, the application processing unit 23 may transmit information notifying that the registration information of the examination ticket is being transmitted to the information processing apparatus 30 together with the examination ticket number and the name.

  The authentication processing unit 41 of the information processing apparatus 30 requests the terminal 20 for FIDO authentication (step S44). At this time, the authentication processing unit 41 transmits information such as a random number to the terminal 20 as a challenge. The application processing unit 23 of the terminal 20 displays a screen for requesting the user to input biometric information on the display unit 25. The authentication processing unit 24 performs biometric authentication processing by comparing the biometric information read by the biometric information reader 118 by the user with biometric information registered in advance (step S45). If the biometric authentication fails, the authentication processing unit 24 ends the process (No in step S45). On the other hand, when the biometric authentication is successful, the authentication processing unit 24 notifies the information processing apparatus 30 of information that has signed the challenge using the secret key generated at the time of FIDO registration as information indicating that biometric authentication is successful. (Yes in step S45). The authentication processing unit 41 of the information processing apparatus 30 verifies the signature received from the terminal 20 using the public key. When the information processing apparatus 30 succeeds in the verification, the information processing apparatus 30 completes the FIDO authentication for the user. Furthermore, the FIDO-ID associated with the public key used when the signature verification is successful is specified as the user's FIDO-ID.

  Since the user's FIDO-ID is specified when the FIDO authentication is completed, the acquisition unit 42 uses the health insurance access token associated with the user's FIDO-ID to store the user's insurance card number. An inquiry is requested (step S46). For example, it is assumed that the user's FIDO-ID is identified as ID_A by FIDO authentication. Then, the acquisition unit 42 specifies KNPT1 as the health insurance access token associated with ID_A from the correspondence table 52a of FIG. Then, the acquiring unit 42 requests the health insurance server 2 to make an inquiry using the identified health care access token (KNPT1). In response to the inquiry request, the health insurance server 2 notifies the information processing apparatus 30 of the insurance card number (step S47). In the example of the insurance card database 3 in FIG. 7, the health insurance server 2 notifies the information processing apparatus 30 of the insurance card number = 1234567. The acquisition unit 42 of the information processing device 30 acquires the insurance card number and notifies the terminal 20 of the insurance card number (step S48).

  When the terminal 20 acquires the insurance card number, the application processing unit 23 waits for input of information specifying a hospital to be associated with the information on the examination ticket photographed in step S42 (No in step S49). If the hospital name is read during the OCR process in step S43, the application processing unit 23 may use the hospital name read by the OCR process as information for identifying the hospital. When the information specifying the hospital is input, the application processing unit 23 transmits a registration request including the insurance card number, the examination ticket number, and the user name to the information processing apparatus 30 together with the information of the registered hospital. (Step S50).

  When receiving the registration request, the acquisition unit 61 of the information processing device 30 uses the hospital information 71 to identify the hospital server 4 that manages information used by the registration destination hospital. The acquisition unit 61 transmits the insurance card number, the examination ticket number, and the user name to the identified hospital server 4 and requests a hospital access token (step S51). The hospital server 4 verifies the information received from the information processing device 30 by comparing it with the information registered in the hospital database 5 (step S52). When the combination of the examination ticket number and the user's name is not registered in the hospital database 5, the hospital server 4 ends the process (No in step S52). On the other hand, when the combination of the examination ticket number and the user's name is registered in the hospital database 5, the hospital server 4 generates a hospital access token and transmits it to the information processing apparatus 30 (Yes in step S52, step S53). . Further, the hospital server 4 records the hospital access token in the hospital database 5. For example, it is assumed that a hospital access token called HPT1 is generated for a patient whose examination ticket number is 123 and whose name is “Taro Fujitsu”. In this case, as shown in the hospital database 5 in FIG. 9, an access token called HPT1 is stored in association with the corresponding patient information.

  Next, processing of the information processing apparatus 30 when receiving a hospital access token will be described. The acquisition unit 61 of the information processing apparatus 30 registers the hospital access token in the hospital access token table 82 and generates a hospital access token identifier (step S54 in FIG. 8). For example, the acquisition unit 61 determines that the identifier of the hospital access token called HPT1 is ID_hpt1. Then, as shown in the hospital access token table 82a of FIG. 9, the hospital access token and the hospital access token identifier are associated with each other. In the example of the hospital access token table 82a, the acquisition unit 61 also registers Y hospital information as information on the hospital that issued the hospital access token HPT1. Further, the acquisition unit 42 of the authentication information processing unit 40 records the hospital access token identifier in the correspondence table 52 in association with the FIDO-ID for identifying the user (step S55 in FIG. 8). In this example, a hospital access token called HPT1 is generated for information inquiry of the user of FIDO-ID = ID_A. Therefore, the acquisition unit 42 records the identifier ID_hpt1 for identifying the hospital access token called HPT1 in the correspondence table 52 in association with FIDO-ID = ID_A. Therefore, the correspondence table 52a in FIG. 7 is updated as shown in the correspondence table 52b in FIG.

(3) Credit Card Registration Processing FIG. 10 is a flowchart for explaining an example of credit card registration processing. It is assumed that the application processing unit 23 displays the credit card registration screen on the screen of the display unit 25 by the processing of the user of the terminal 20. In this state, the user of the terminal 20 photographs the credit card face using the camera 22 of the terminal 20 (step S61). The application processing unit 23 performs OCR processing on the captured image to specify information such as a card number, a name of a right holder, an expiration date, and the like printed on the credit card, and uses the obtained information as the information processing device 30. (Step S62). At this time, the application processing unit 23 may also transmit information notifying that the registration information of the credit card is transmitted to the information processing apparatus 30 together with the examination ticket number and the name.

  The acquisition unit 61 of the information processing apparatus 30 notifies the financial institution server 8 of information such as a card number, a name of a right holder, an expiration date, etc., and is used for settlement using a credit card specified by the notified information. A possible Creca access token is requested (step S63). When the financial institution server 8 generates a PIN in association with the notified credit card information, the financial institution server 8 requests the PIN of the user terminal 20 registered in advance (step S64). It is assumed that the PIN generated by the financial institution server 8 is notified to the user using an e-mail address registered in the financial institution server 8 in advance. When the user inputs a PIN, the terminal 20 transmits the input PIN to the financial institution server 8 (step S65). The financial institution server 8 verifies the PIN notified from the terminal 20 by comparing it with the PIN generated in Step S64 (Step S66). If it is determined that the PIN is not correct, the financial institution server 8 ends the process (NG in step S66). If it is determined that the PIN is correct, the financial institution server 8 generates a credit card access token that can be used for payment using the user's credit card (OK in step S66, step S67).

  FIG. 11 shows a storage example of the Creca access token. For example, as a result of verifying a PIN issued to a credit card with a card number = 123456, the holder “Fujitsu Taro”, and an expiration date of October 2020, it is determined that the correct PIN is transmitted from the terminal 20. To do. Further, it is assumed that the financial institution server 8 uses CCT1 as the credit card access token that can be used for the payment of the credit card specified by these pieces of information. Then, information is stored in the financial database 9 as shown in FIG. The financial institution server 8 transmits the Kureka access token to the information processing apparatus 30.

  The acquiring unit 61 registers the cleka access token together with the identifier for identifying the cleka access token in the cleka access token table 83 (step S68 in FIG. 10). FIG. 11 shows an example of registration in the Creca access token table 83 when the Creca access token is CCT1 and the Creca access token identifier is ID_cct1. In the example of FIG. 11, it is assumed that the financial institution server 8 that has issued the credit card access token CCT1 is a server that manages information on cards issued by the card company B.

  The authentication processing unit 41 requests the terminal 20 to perform the FIDO authentication in order to confirm which FIDO-ID is associated with and recorded the Creca access token identifier (step S69 in FIG. 10). The FIDO authentication process performed in steps S69 to S70 is the same as the process of steps S44 to S45 described with reference to FIG. When the FIDO authentication for the user is completed, the authentication processing unit 41 specifies the user's FIDO-ID. Then, the acquisition unit 42 registers the Kureka access token identifier in the correspondence table 52 in association with the specified FIDO-ID (Step S71). For example, when it is specified that the user's FIDO-ID is ID_A, the acquisition unit 42 records the Creca access token identifier ID_cct1 in association table 52 in association with FIDO-ID = ID_A. Therefore, the correspondence table 52b (FIG. 9) is updated as shown in the correspondence table 52c in FIG.

(4) Consultation Reception FIG. 12 is a diagram for explaining a display example of the terminal 20 before the diagnosis reception. When the registration of the health insurance card and the registration of the examination ticket are completed, the application processing unit 23 can display on the screen of the display unit 25 a screen that can be selected as a hospital to which the registration process of the information on the examination ticket has been completed. In the example of FIG. 12, it is assumed that the registration of the examination ticket issued from the Y hospital and the examination ticket issued from the X internal medicine has been completed. It is assumed that the user can select an icon associated with each hospital on a screen that can select a hospital as a hospital destination.

  FIG. 13 is a flowchart for explaining an example of a medical reception process. FIG. 14 is a diagram for explaining an example of data update performed during the examination acceptance process. Hereinafter, an example of processing that is performed at the time of medical examination reception processing will be described with reference to FIGS. 12 to 14.

  When the user selects a hospital icon while the screen shown in FIG. 12 is displayed on the terminal 20, the application processing unit 23 recognizes that a medical examination reception is performed for the hospital associated with the icon. To do. Therefore, the application processing unit 23 transmits information (hospital designation information) for designating a hospital associated with the selected icon to the information processing apparatus 30 (step S81 in FIG. 13). In the following example, it is assumed that an icon associated with Y hospital is designated.

  Upon receipt of the hospital designation information, the authentication processing unit 41 of the information processing apparatus 30 requests the terminal 20 for FIDO authentication in order to specify an access token used for obtaining information on the examination ticket and insurance card (step S82). . The FIDO authentication process performed in steps S82 to S83 is the same as the process of steps S44 to S45 described with reference to FIG. When the FIDO authentication for the user is completed, the authentication processing unit 41 specifies the user's FIDO-ID.

  Using the user's FIDO-ID, the acquisition unit 42 determines a hospital access token used for inquiry of information on the examination ticket (step S84). At this time, the acquisition unit 42 uses the hospital access token identifier associated with the notified hospital designation information among the hospital access token identifiers associated with the identified FIDO-ID as the information on the examination ticket. This is the identifier of the access token used for the inquiry. For example, it is assumed that the information processing apparatus 30 holds the correspondence table 52d and the hospital access token table 82 illustrated in FIG. 14 when a hospital icon is selected on the terminal 20. Further, it is assumed that the user's FIDO-ID is identified as ID_A by the FIDO authentication. Then, the acquisition unit 42 identifies the identifier of the access token issued from the hospital Y designated by the hospital designation information among the hospital access token identifiers associated with FIDO-ID = ID_A. At this time, the acquisition unit 42 refers to the hospital access token table 82 as appropriate. As a result, in the example of FIG. 14, the acquiring unit 42 selects ID_hpt1 as the identifier of the access token to be used. Further, the acquisition unit 42 searches the hospital access token table 82 (FIG. 14) using the obtained identifier as a key, thereby determining the hospital access token used for inquiry of the information on the examination ticket in the HPT 1.

  The acquisition unit 42 notifies the acquired hospital access token to the acquisition unit 61 and the service processing unit 63. Using the confirmed hospital access token, the acquiring unit 61 requests the hospital server 4 holding the information on the Y hospital to inquire about the examination ticket number (step S85 in FIG. 13). Further, the service processing unit 63 stores the confirmed hospital access token and the user's FIDO-ID as information of the user who is performing the reception process. The hospital server 4 verifies the validity of the hospital access token (step S86). If the hospital access token is not valid, the hospital server 4 ends the process (NG in step S86). When the hospital access token is valid, the hospital server 4 transmits the examination ticket number associated with the hospital access token to the information processing apparatus 30 (OK in step S86, step S87). For example, it is assumed that the information in the hospital database 5 held by the hospital server 4 is as shown in the hospital database 5a in FIG. Further, assume that the hospital access token used for the inquiry is HPT1. In this case, the hospital server 4 notifies the information processing apparatus 30 of the examination ticket number = 123.

  In parallel with the inquiry ticket information, the insurance card information is also inquired. At this time, the acquisition unit 42 specifies the health insurance access token associated with the specified FIDO-ID from the correspondence table 52. For example, when the information processing apparatus 30 holds the correspondence table 52d illustrated in FIG. 14 and the user's FIDO-ID is ID_A, the acquisition unit 42 determines the health access token to be used for the inquiry as KNPT1. Using the determined health insurance access token, the acquisition unit 42 requests the health insurance server 2 to refer to insurance card information (step S88 in FIG. 13). The health insurance server 2 verifies the validity of the health insurance access token (step S89). If the health insurance access token is not valid, the health insurance server 2 ends the process (NG in step S89). When the health insurance access token is valid, the health insurance server 2 transmits the insurance card number associated with the health insurance access token and the name of the insured person to the information processing apparatus 30 (OK in step S89, step S90). For example, it is assumed that the information in the insurance card database 3 held by the health insurance server 2 is as shown in FIG. 14, and the health insurance access token used for the inquiry is KNPT1. In this case, the health insurance server 2 notifies the information processing apparatus 30 of the insurance card number = 1234567 and the insured person name = Fujitsu Taro.

  The QR code generating unit 62 of the information processing apparatus 30 acquires the examination ticket number transmitted from the hospital server 4, the insurance card number and the insured person name transmitted from the health insurance server 2, and information obtained by combining these information Generate (merge). The QR code generation unit 62 generates a QR code for notifying the merged information (step S91 in FIG. 13). The service processing unit 63 transmits the generated QR code to the terminal 20. At this time, the service processing unit 63 specifies the information of the destination terminal 20 using the user's FIDO-ID stored as the information of the user during the reception process. Although not shown in the figure, it is assumed that the information of the destination terminal 20 is also included in the insured person database 80 in association with the FIDO-ID. As information on the terminal 20, for example, an application code or the like can be recorded in the insured person database 80. The application processing unit 23 of the terminal 20 displays the QR code received from the information processing device 30 on the display unit 25 (step S92). The user holds the screen of the terminal 20 on which the QR code is displayed over the reception device 10. Then, the accepting device 10 reads the QR code displayed on the screen of the terminal 20 (step S93). The reception device 10 transmits a combination of the examination ticket number, the insurance card number, and the insured person name included in the QR code to the hospital server 4, and the hospital server 4 receives information using the information received from the reception device 10. Processing is performed (step S94).

  When the reception process is completed, the hospital server 4 transmits to the information processing apparatus 30 the hospital access token of the patient who has performed the reception process and information notifying the completion of the reception. The service processing unit 63 of the information processing apparatus 30 updates the status registered in the insured person information table 81 to “waiting for medical examination” for the user of the FIDO-ID associated with the received hospital access token (step S95). ). Furthermore, the application control unit 64 notifies the terminal 20 that it has been received, and requests that the reception has been received on the screen of the terminal 20. In response to a request from the information processing device 30, the application processing unit 23 of the terminal 20 changes the display on the screen and displays that the examination has been received (step S96).

  The insured person information table 81a in FIG. 14 is an example of status change by the process in step S95 in FIG. For example, it is assumed that the information processing apparatus 30 is notified from the hospital server 4 of hospital Y that the acceptance of the patient associated with the hospital access token of HPT 1 has ended. Further, it is assumed that the service processing unit 63 stores that the user's FIDO-ID during the reception process is ID_A and that the user's hospital access token is HPT1. Then, as shown in the insured person information table 81a in FIG. 14, the service processing unit 63 updates the status status of the user whose FIDO-ID is ID_A to “waiting for medical examination (Y hospital)”.

  Note that FIG. 13 is an example of processing, and the processing procedure can be changed according to the implementation. For example, the process of steps S84 to S87 and the process of steps S88 to S90 may be performed in parallel, or one of them may be performed before the other.

  FIG. 15 is a diagram illustrating a display example of the terminal 20 at the time of receiving a medical examination. A screen G1 in FIG. 15 is a display example of a QR code used for the reception process. The QR code is displayed on the screen of the terminal 20 as shown in the screen G1 by the process of step S92 in FIG. Note that information other than the QR code may also be displayed on the screen. In the example of the screen G1, in addition to the QR code, information such as the user's name, insurance card number, date of birth, and the like is displayed so that the user or the operator who performs the reception process of the hospital can easily understand. The date of birth can be notified from the health insurance server 2 to the terminal 20 via the information processing device 30 together with the insurance card number and the like. Furthermore, in the example of the screen G1, since the user has already registered the credit card, it is also displayed that the payment processing using the system according to the embodiment is approved in advance.

  The screen G2 is a display example of the user status. On the screen G2, icons associated with each of the hospitals in which the user registers the examination ticket are displayed. A display A indicating that the user is waiting for a medical examination is included on the icon of Y hospital. Note that such an icon drawing change is performed by the application processing unit 23 of the terminal 20 in response to a request from the application control unit 64 of the information processing device 30.

  When the user authentication is successful, the information processing apparatus 30 autonomously generates data to be used for medical examination reception and provides the data to the terminal 20. In other words, if the user authentication is not successful, the data for accepting the diagnosis is not sent from the information processing apparatus 30 to the terminal 20. Therefore, in the system according to the embodiment, it is possible to prevent the insurance card and the examination ticket from being used illegally by a person other than the authorized user of the terminal 20.

  By the way, in the system according to the embodiment, the reception of the diagnosis is completed by causing the reception device 10 to photograph the QR code provided to the terminal 20. For this reason, in the system according to the embodiment, the reception process of the diagnosis is much more convenient than the conventional reception process that requires the presentation of the medical examination ticket and the insurance card.

  Furthermore, the information processing apparatus 30 does not hold the information on the user's health insurance card or the information on the examination ticket, and inquires the health insurance server 2 or the hospital server 4 about the information according to the success of the user authentication. Yes. That is, the user's personal information such as insurance card registration contents and examination ticket information is not constantly stored in the information processing apparatus 30. Therefore, in the system according to the embodiment, the information processing apparatus 30 can provide the user's personal information to the terminal 20, but the risk of the user's personal information leaking from the information processing apparatus 30 is small.

(5) Examination Fee Payment Processing FIG. 16 is a flowchart illustrating an example of a consultation fee payment process. FIG. 17 is a diagram for explaining an example of data update performed during the examination fee payment process. Hereinafter, an example of processing performed when the examination fee is paid will be described with reference to FIGS. 16 and 17.

  When the examination at the hospital is completed, the hospital server 4 generates payment request information and the like (step S101 in FIG. 16). The hospital database 5b in FIG. 17 is an example of the hospital database 5 when billing information is generated. In the hospital database 5b, billing information of 980 yen is recorded for the patient with the examination ticket number = 123 and the name = Fujitsu Taro. In this example, prescription information is also recorded, but the prescription information may be generated after the payment of the examination fee is confirmed. Thereafter, the hospital server 4 transmits the billing information for the examination fee and the hospital access token to the information processing apparatus 30 (step S102 in FIG. 16).

  The acquisition unit 42 of the information processing device 30 specifies the FIDO-ID of the user who is requested to pay the examination fee using the hospital access token (step S103). In the example of FIG. 17, since the information processing apparatus 30 receives the hospital access token = HPT1 together with the billing information, the acquiring unit 42 refers to the hospital access token table 82, thereby identifying an identifier for identifying the received hospital access token. It is recognized as ID_hpt1. Therefore, the acquisition unit 42 searches the correspondence table 52d using the hospital access token identifier = ID_hpt1 as a key, thereby recognizing that the FIDO-ID of the user charged for the examination fee is ID_A.

  The acquisition unit 42 outputs the FIDO-ID and billing information of the user who has been charged for the examination fee to the service processing unit 63. The service processing unit 63 updates the status state and payment information in the insured person information table 81 for the user for whom the examination fee is charged. The insured person information table 81b in FIG. 17 is an example of the insured person information table 81 when the service processing unit 63 updates the status status of the user with FIDO-ID = ID_A to “waiting for payment (Y hospital)”. It is. In the example of FIG. 17, it is also recorded in the insured person information table 81b that the charged amount is 980 yen and the payee is Y hospital. The service processing unit 63 transmits the billing information to the terminal 20 associated with the user's FIDO-ID for which the consultation fee has been charged (step S104 in FIG. 16).

  The application processing unit 23 of the terminal 20 requests the user to confirm payment by displaying the received billing information on a screen provided in the display unit 25 (step S105 in FIG. 16). For example, in this example, information that the examination fee is 980 yen, the payee is Y hospital, and an approval button can be displayed. When the user of the terminal 20 confirms the billing information and determines that there is no problem, the user presses the approval button displayed on the screen. Then, the application processing unit 23 transmits a payment processing request to the information processing apparatus 30.

  When receiving the payment processing request, the acquisition unit 42 of the information processing device 30 requests the terminal 20 for FIDO authentication (step S106). The FIDO authentication process performed in steps S106 to S107 is the same as the process of steps S44 to S45 described with reference to FIG. When the FIDO authentication for the user is completed, the authentication processing unit 41 specifies the user's FIDO-ID.

  The acquisition unit 42 determines the credit card access token used for the payment process (step S108). At this time, the acquisition unit 42 sets the credit card access token identified by the credit card access token identifier associated with the specified FIDO-ID as an access token used for the payment process. For example, it is assumed that the correspondence table 52d shown in FIG. Further, it is assumed that the user's FIDO-ID is identified as ID_A. Then, the acquisition unit 42 determines to use the access token identified by the Creca access token identifier = ID_cct1 for payment processing. Furthermore, in the cleka access token table 83, it is assumed that cleka access token identifier = ID_cct1 is associated with cleka access token = CCT1. Then, the acquisition unit 42 uses the credit card access token = CCT1 as an access token used for the payment process. The service processing unit 63 generates payment information including information about the hospital of the payee and the amount billed, and transmits a payment request including the credit card access token = CCT1 and the payment information to the financial institution server 8 (step S109 in FIG. 16). ). At this time, the service processing unit 63 stores the FIDO-ID and the credit card access token of the user who is requesting payment.

  The financial institution server 8 performs a verification process of the Kureka access token (step S110). If the credit card access token is not valid, the financial institution server 8 ends the process (No in step S110). If the credit card access token is valid, the financial institution server 8 performs a settlement process using the credit card information associated with the credit card access token (Yes in step S110). The financial institution server 8 notifies the information processing apparatus 30 of the completion of payment together with the Kureka access token (step S111).

  The service processing unit 63 of the information processing device 30 receives a payment completion notification. The application control unit 64 specifies the FIDO-ID of the user who is requesting payment stored in association with the credit card access token notified from the financial institution server 8. The application control unit 64 sends a payment completion notification to the terminal 20 associated with the user's FIDO-ID requesting payment, and requests the terminal 20 to display a screen informing the payment completion. To do. (Step S112). The application processing unit 23 of the terminal 20 displays a screen notifying completion of payment on the screen of the display unit 25 in accordance with a request from the information processing apparatus 30 (step S113). The application processing unit 23 of the terminal 20 notifies the information processing apparatus 30 of the display change. Then, the service processing unit 63 updates the status information and payment information associated with the FIDO-ID stored as the user who is requesting payment (step S114). For example, when the payment process for the user of FIDO-ID = ID_A is completed, the service processing unit 63 updates the insured person information table 81b shown in FIG. 17 as shown in the insured person information table 81c.

  Note that the processing described with reference to FIGS. 16 and 17 is an example, and changes may be made according to the implementation. For example, the process of step S114 may be performed before step S113. In addition, when the billing information is transmitted in step S102, the hospital server 4 may notify the information processing apparatus 30 of the presence or absence of a prescription. In this case, the service processing unit 63 can appropriately record in the insured person information table 81 information indicating whether a prescription has been issued for the user who is charged for the examination fee. Furthermore, the application control unit 64 can notify the terminal 20 that the payment end screen includes a display for notifying the user that a prescription has been issued.

  FIG. 18 is a diagram illustrating a display example of the terminal 20 when the examination fee payment process is performed. FIG. 18 is a display example of the terminal 20 when a display notifying that a prescription has been issued is included in the payment end screen. In the example of FIG. 18, the user of the terminal 20 is notified that payment of 980 yen to Y hospital has been completed and that a prescription has been issued.

  As described above, the information processing apparatus 30 acquires billing information from the hospital server 4, and when the user authentication is successful, performs the payment process using the Creca access token and provides the payment result to the terminal 20. ing. Therefore, in the system according to the embodiment, the user can perform the payment process even if he / she is not in the hospital where he / she has been examined. That is, if the system according to the embodiment is used, the user does not have to spend the time between the end of the examination and the calculation of the billing amount in the hospital or the vicinity of the hospital. For this reason, the user's convenience improves with the system concerning an embodiment.

  Furthermore, the information processing apparatus 30 does not hold credit card information, and requests payment processing from the financial institution server 8 using a credit card access token in response to successful user authentication. That is, since the user's credit card information is not constantly stored in the information processing apparatus 30, the risk of the user's credit card information leaking from the information processing apparatus 30 is small.

(6) Pharmacy Designation Processing for Receiving Medicine FIG. 19 is a flowchart for explaining an example of pharmacy designation processing. FIG. 20 is a diagram illustrating an example of data update performed in the pharmacy designation process. Hereinafter, an example of processing performed when designating a pharmacy to receive a drug will be described with reference to FIGS. 19 and 20.

  When the payment process ends, the hospital server 4 transmits prescription information that can be presented to the pharmacy and a hospital access token to the information processing apparatus 30 (steps S121 and S122).

  The acquisition unit 42 of the information processing device 30 specifies the user's FIDO-ID for which prescription information has been generated using the hospital access token (step S123). The processing performed in step S123 is the same as the processing described with reference to step S103 in FIG. 16 and FIG. Here, it is assumed that the correspondence table 52d and the hospital access token table 82 are used when the FIDO-ID is specified. Next, the service processing unit 63 records the notified prescription information in the insured person information table 81 in association with the user's FIDO-ID. For example, it is assumed that the user's FIDO-ID notified of the prescription information is identified as ID_A. In this case, as shown in the insured person information table 81d in FIG. 20, the prescription information is recorded in the prescription information in the entry of FIDO-ID = ID_A. Thereafter, the application control unit 64 notifies the terminal 20 that the prescription has been issued, and requests the terminal 20 to display a request for confirmation of the content of the prescription (step S124 in FIG. 19).

  In response to the notification from the information processing device 30, the application processing unit 23 of the terminal 20 displays a display requesting confirmation of the content of the prescription on the screen of the display unit 25. The display requesting confirmation of the contents of the prescription may be a dialog box for inquiring whether to display prescription information, or may be a button written as “prescription confirmation” as shown in FIG. . When the user selects a button or the like associated with confirmation of prescription information, the application processing unit 23 displays prescription information on the screen of the display unit 25 (step S125). The prescription information displayed on the screen is, for example, a display including the name of the medical institution that issued the prescription, the name of each prescription medicine, and the prescription amount for each medicine. When displaying the prescription information confirmation screen, the application processing unit 23 acquires the position information of the terminal 20 and transmits the acquired position information to the information processing apparatus 30 (step S126). Here, for example, GPS (Global Positioning System) information or the like is used as the position information. When receiving the position information, the service processing unit 63 of the information processing apparatus 30 records the position information in an entry including the FIDO-ID of the user who transmitted the prescription issuance notification in the insured person information table 81. The insured person information table 81e in FIG. 20 is an update example of the insured person information table 81 when the terminal 20 of the user with FIDO-ID = ID_A is located in the north latitude XX east longitude XX.

  When the service processing unit 63 of the information processing device 30 acquires the position information from the terminal 20, the service processing unit 63 searches for a dispensing pharmacy that is close to the position of the terminal 20 using the pharmacy information 72 (step S127 in FIG. 19). The pharmacy recorded in the pharmacy information 72 is a pharmacy that holds the pharmacy server 6 to which the information processing apparatus 30 can transmit prescription information and insurance card information. The service processing unit 63 transmits pharmacy information obtained by the search to the terminal 20. The service processing unit 63 may transmit, to the terminal 20, information such as an estimated reception time at each pharmacy together with the searched list of dispensing pharmacies. For example, when the average waiting time at each pharmacy is recorded in the pharmacy information 72, the standard of the reception time is set to the time when the average waiting time has elapsed from the current time. The application processing unit 23 of the terminal 20 displays the pharmacy information received from the information processing device 30 on the screen of the display unit 25. At this time, the pharmacy information may be text information or information including a map. Moreover, prescription information may be displayed with the information of a pharmacy.

  FIG. 21 is a diagram illustrating a display example of the terminal during the pharmacy designation process. A screen G11 in FIG. 21 is an example in which the names of candidate pharmacies and prescription information are displayed together. In the example of the screen G11, a part of the pharmacies included in the list of dispensing pharmacies notified to the terminal 20 as candidates for pharmacies that receive the prescribed drug and information notified about the pharmacy are displayed in text. . In this example, the application processing unit 23 selects “A pharmacy” as a display target from the list of dispensing pharmacies, and indicates that the drug can be received after 15:00 in the A pharmacy. Furthermore, in the example of the screen G11, the date when the prescription was issued, the name of the medical institution that issued the prescription, the name of each prescription medicine, and the prescription amount for each medicine are displayed as prescription information. Has been. The screen G11 also displays a button for applying for dispensing at the selected pharmacy. When the user presses the “Receive Application” button in the screen G11, the designation of the pharmacy A as the dispensing pharmacy is confirmed.

  Screen G12 in FIG. 21 is also an example of a pharmacy designation screen. In the example of the screen G12, the terminal 20 receives a list of pharmacies from the information processing apparatus 30 in the form of a map on which pharmacies are displayed. The application processing unit 23 of the terminal 20 displays the map received from the information processing device 30 on the screen. At this time, the application processing unit 23 displays an icon or the like in association with the display position of each pharmacy so that each pharmacy can be selected. In the example of the screen G12, information on the selected pharmacy is also displayed below the map. In the example of the screen G12, A pharmacy is selected. In addition, the screen G12 includes an indication of the time that can be received at the A pharmacy. When the user presses the “apply at this place” button in the screen G12, the designation of the pharmacy A as the dispensing pharmacy is confirmed.

  When the designation of the dispensing pharmacy is confirmed by the user input on the pharmacy selection screen, the application processing unit 23 of the terminal 20 requests the information processing apparatus 30 to apply for the dispensing to the designated pharmacy (FIG. 19). Steps S128 and S129).

  Upon receiving the dispensing application, the authentication processing unit 41 of the information processing apparatus 30 starts the insurance card information acquisition process in order to generate information to be presented to the designated dispensing pharmacy. First, the authentication processing unit 41 requests the terminal 20 for FIDO authentication (step S130). The FIDO authentication process performed in steps S130 to S131 is the same as the process of steps S44 to S45 described with reference to FIG. When the FIDO authentication for the user is completed, the authentication processing unit 41 specifies the user's FIDO-ID. Then, the acquisition unit 42 stores the identified FIDO-ID as the user's FIDO-ID during the pharmacy designation process. Furthermore, the acquisition unit 42 requests the health insurance server 2 to query the health insurance card information using the health insurance access token associated with the identified FIDO-ID (step S132). The health insurance server 2 verifies the validity of the health insurance access token (step S133). If the health insurance access token is not valid, the health insurance server 2 ends the process (No in step S133). If the health insurance access token is valid, the health insurance server 2 transmits the insurance card number associated with the health insurance access token and the name of the insured person to the information processing apparatus 30 (Yes in step S133, step S134). The service processing unit 63 of the information processing device 30 uses the prescription information associated with the insurance card number, the insured person's name, and the user's FIDO-ID during the pharmacy designation process by the designated dispensing pharmacy. It transmits to the pharmacy server 6 to perform (step S135). The pharmacy server 6 registers the prescription information in the pharmacy database 7 (step S136).

  FIG. 22 is a diagram illustrating an example of data when a pharmacy designation process is performed. An update example of the insured person information table 81 and details of the registration process in the pharmacy server 6 will be described with reference to FIG.

  When the service processing unit 63 of the information processing apparatus 30 transmits the prescription information to the pharmacy server 6 (step S135 in FIG. 19), the status information of the processing target user is updated in the insured person information table 81. For example, when the prescription information is transmitted to the pharmacy server 6 of the A pharmacy, the service processing unit 63 updates the insured person information table 81e (FIG. 20) as shown in the insured person information table 81f of FIG.

  On the other hand, when receiving the prescription information from the information processing apparatus 30, the pharmacy server 6 searches the pharmacy database 7 using the insured person's name as a key, and records the prescription information in the hit entry. For example, it is assumed that an insurance card number and prescription information xxxx are transmitted from the information processing apparatus 30 together with information on the insured person name = Fujitsu Taro. Then, as shown in the pharmacy database 7 of FIG. 22, prescription information is recorded in an entry including name = Fujitsu Taro. The pharmacy server 6 issues an access token (pharmacy access token) used when notifying the dispensing result in association with the prescription information. In the example of FIG. 22, as shown in the pharmacy database 7, YKT <b> 1 is issued as a pharmacy access token used for notifying the dispensing result for the prescription information xxxx of name = Fujitsu Taro. The pharmacy server 6 notifies the information processing apparatus 30 of the issued pharmacy access token.

  The service processing unit 63 of the information processing device 30 generates a pharmacy access token identifier that identifies the notified pharmacy access token, and records the pharmacy access token and the pharmacy access token identifier in the pharmacy access token table 84. Furthermore, the service processing unit 63 also records pharmacy information associated with the pharmacy server 6 that issued the pharmacy access token as pharmacy information. In the example of FIG. 22, pharmacy access token = YKT1, pharmacy access token identifier = ID_yk1, and pharmacy information = A pharmacy are recorded in the pharmacy access token table 84. The service processing unit 63 records the pharmacy access token identifier in the correspondence table 52 in association with the FIDO-ID of the user to be processed. In the example of FIG. 22, the identifier of the pharmacy access token issued to the user with FIDO-ID = ID_A is ID_yk1. Therefore, the correspondence table 52d (FIG. 20) is updated as shown in the correspondence table 52e in FIG.

  As described above, in the system to which the method according to the embodiment is applied, instead of the prescription being issued as a paper medium, electronic data is transmitted and received between the hospital server 4, the information processing device 30, the terminal 20, and the pharmacy server 6. Is done. Therefore, the user can apply for drug dispensing to the pharmacy selected by the user without receiving a prescription issued in paper form at the hospital. Therefore, in the system to which the method according to the embodiment is applied, the user does not have to stop at the hospital after payment of the examination fee in order to receive the paper medium prescription, which is compared with the case where the paper medium prescription is issued. , User convenience is improved.

(7) Medicine Receiving Process FIG. 23 is a flowchart illustrating an example of a process performed when a medicine is received. FIG. 24 is a diagram illustrating an example of data update performed when a medicine is received. Hereinafter, an example of processing performed when a user receives a medicine at a pharmacy will be described with reference to FIGS. 23 and 24.

  When dispensing at the pharmacy is completed, the pharmacy server 6 generates a dispensing result and billing information for the price of the drug (step S141). The pharmacy server 6 transmits the dispensing result and the billing information to the information processing device 30 together with the pharmacy access token issued to the prescription target user.

  The acquisition unit 42 of the information processing device 30 specifies the FIDO-ID that identifies the prescription target user using the pharmacy access token (step S142). For example, it is assumed that the information received from the pharmacy server 6 includes a pharmacy access token = YKT1. Then, the acquisition unit 42 specifies the pharmacy access token identifier by searching the pharmacy access token table 84 using the received pharmacy access token as a key. In the example of FIG. 24, the identifier for identifying the pharmacy access token = YKT1 is ID_yk1. The acquisition unit 42 sets the FIDO-ID associated with the obtained pharmacy access token identifier as the FIDO-ID that identifies the prescription target user. In the example of the correspondence table 52e shown in FIG. 24, since FIDO-ID = ID_A is associated with the pharmacy access token identifier = ID_yk1, the acquisition unit 42 recognizes ID_A as the FIDO-ID of the prescription target user.

  The acquiring unit 42 outputs the prescription target user's FIDO-ID, the dispensing result, and the billing information to the service processing unit 63. The service processing unit 63 updates the status state, dispensing result information, and payment information in the insured person information table 81 for the prescription target user. In the insured person information table 81g of FIG. 24, the service processing unit 63 sets the status status to “prescription payment waiting (A pharmacy)” and the payment information to “560 yen (A pharmacy)” for the user with FIDO-ID = ID_A. It is an example of the insured person information table 81 at the time of updating. In the insured person information table 81g of FIG. 24, the dispensing result information is also updated. The service processing unit 63 transmits the dispensing result and the billing information to the terminal 20 associated with the prescription target user's FIDO-ID (step S143 in FIG. 23).

  The application processing unit 23 of the terminal 20 requests the user of the terminal 20 to confirm the dispensing contents and payment by displaying the received dispensing result and billing information on a screen provided in the display unit 25 (step S144). For example, in this example, along with the contents of dispensing, information that the price of the medicine = 560 yen, the payee = A pharmacy, and the approval button may be displayed. The user of the terminal 20 confirms the dispensing contents and the billing information, and when determining that there is no problem, pushes down the approval button displayed on the screen. Then, the application processing unit 23 transmits a payment processing request to the information processing apparatus 30 (Yes in step S144).

  Upon receiving the payment processing request, the acquisition unit 42 of the information processing device 30 requests the terminal 20 for FIDO authentication (step S145). The processing in steps S145 to S151 is the same as the processing in steps S106 to S112 described with reference to FIG. That is, payment processing using the credit card after completion of FIDO authentication or FIDO authentication is performed in the same manner as the processing for paying the examination fee.

  When the application processing unit 23 of the terminal 20 is requested to display a screen informing the completion of payment from the information processing device 30, the application processing unit 23 displays a screen informing the completion of payment on the screen of the display unit 25 (step S152). When there is an input from the user after the display is changed, the application processing unit 23 of the terminal 20 notifies the information processing apparatus 30 that the user has confirmed the completion of the payment for the medicine. For example, a confirmation button or the like may be included in the notification screen for the completion of payment for the medicine. In this case, when the user presses down the confirmation button, the application processing unit 23 can notify the information processing apparatus 30 that the user has confirmed the completion of the payment of the price of the medicine.

  When the terminal 20 is notified that the user has confirmed the completion of the payment for the medicine, the service processing unit 63 of the information processing device 30 receives the status information and payment associated with the FIDO-ID of the prescription target user. Information is updated (step S153). For example, when the payment processing of the medicine price for the user of FIDO-ID = ID_A is completed, the service processing unit 63 updates the insured person information table 81g shown in FIG. 24 as shown in the insured person information table 81h. .

  Further, the QR code generating unit 62 of the information processing device 30 generates a QR code to be presented to the pharmacy accepting device 10 when receiving the medicine (step S154 in FIG. 23). The QR code to be presented when the medicine is received includes prescription information for the medicine to be received and status information indicating that payment for the price of the medicine to be received has been completed. The service processing unit 63 transmits the generated QR code to the terminal 20. At this time, the service processing unit 63 specifies the information of the terminal 20 of the transmission destination using the user's FIDO-ID stored as the information of the user who has completed the payment processing for the medicine. The application processing unit 23 of the terminal 20 displays the QR code received from the information processing device 30 on the screen of the display unit 25 (Step S155).

  FIG. 25 is a diagram for explaining an example of a display screen for receiving medicine. In the example shown in FIG. 25, the display screen for receiving medicine contains the QR code and the name of the hospital that issued the prescription. Also included is a display that prompts the user to present the display screen to the pharmacist.

  The user goes to the pharmacy that applied for dispensing and informs the pharmacist that he / she has received the medicine. Then, the pharmacist or the like prepares the receiving apparatus 10 for reading the QR code for receiving medicine displayed on the user terminal 20. When the user holds the screen of the terminal 20 over the prepared reception device 10, the reception device 10 reads the QR code displayed on the terminal 20 (step S156 in FIG. 23). Then, the reception device 10 decodes the QR code, and the prescription content of the medicine to be received and whether the payment has been completed are displayed on the screen of the reception device 10. Therefore, the pharmacist hands the medicine to the user and explains the medicine based on the information displayed on the screen of the reception device 10.

  In parallel with the delivery of the medicine from the pharmacist to the user, the reception device 10 uses the combination of the prescription information included in the QR code and the status information indicating that the payment of the medicine has been completed to the pharmacy server 6. Send to. Then, the pharmacy server 6 uses the information received from the reception device 10 to transmit a notification indicating that the medicine has been received to the information processing device 30 together with the pharmacy access token associated with the user who has received the medicine. (Step S157).

  The service processing unit 63 of the information processing apparatus 30 updates the status registered in the insured person information table 81 to “completion of drug reception” for the user of the FIDO-ID associated with the received pharmacy access token. Furthermore, the application control unit 64 requests the terminal 20 to display a display indicating that the medicine has been received on the screen of the terminal 20. In response to a request from the information processing device 30, the application processing unit 23 of the terminal 20 displays a display indicating that the medicine has been received on the screen of the terminal 20 (step S159).

  Thus, in the system to which the method according to the embodiment is applied, the user can perform payment processing via the terminal 20 when the end of the dispensing is displayed on the screen of the terminal 20. For this reason, in the pharmacy, the reception device 10 can receive the medicine by reading the QR code. Therefore, in the system to which the method according to the embodiment is applied, it is difficult for the waiting time at the pharmacy to occur, and the convenience for the user is improved.

  As described above, the information processing apparatus 30 performs the FDO authentication before acquiring the health insurance card information and completes the FIDO authentication, as described in the description of the reception process of the examination and the designation of the pharmacy that receives the medicine. 2. Obtain insurance card information using an access token from 2. Further, a health insurance access token used for obtaining insurance card information is issued for each insurance card. Therefore, when the method according to the embodiment is used, when the user's identity verification is successful, the user's identity card information is notified to the terminal 20 or the pharmacy server 6, but if the identity verification fails, the insurance card information Is not presented on the terminal 20 or the like. In other words, when the identity verification is successful, the insurance card information can be notified to the pharmacy server 6, and the insurance card information can also be notified to the hospital reception device 10 through reading the QR code. On the other hand, if the identity verification fails, the insurance card information is not notified to the pharmacy server 6. Further, if the identity verification fails, the QR code including the insurance card information is not displayed on the terminal 20, so that the insurance card information is not notified to the hospital reception apparatus 10. For this reason, in the system in which the method according to the embodiment is used, unauthorized use of the insurance card can be prevented.

  Furthermore, as described in the explanation of each of the examination reception, the examination fee payment process, the pharmacy designation process for receiving the medicine, and the medicine reception process, the information processing apparatus 30 receives the information received from the terminal 20 or the like. Accordingly, the type of personal information to be acquired is determined. The information processing apparatus 30 acquires personal information to be acquired from a server of an external organization such as the health insurance server 2 and provides the terminal 20 with a combination of the acquired information. As a result, a combination of information on health insurance card and examination ticket is provided at the reception of the hospital, and a combination of payment result of medicine fee and information on the prescription of the medicine to be received is provided when receiving the medicine at the pharmacy For example, information tailored to the usage scene of the user is provided to the terminal 20. Therefore, the procedure performed by the user is simplified.

<Others>
The embodiment is not limited to the above, and can be variously modified. Some examples are described below.

  In the above description, an example in which a plurality of pieces of information are merged when a plurality of pieces of information are notified to the terminal 20 has been described, but this is only an example of an embodiment. Depending on the implementation, a plurality of pieces of information may be displayed on the screen of the terminal 20 with different QR codes without being merged.

  Furthermore, although the embodiment has been described by way of example in which a QR code is used as information to be transmitted to the terminal 20, this is also merely an example. An information presentation method is also arbitrary depending on the implementation, and an information code other than the QR code may be used. In addition, information may be presented to the terminal 20 or the reception device 10 in a form different from the information code.

  The information transmitted to the terminal 20 may be an access destination to information used for processing in the reception device 10 in a hospital or pharmacy. For example, the information processing apparatus 30 holds information that combines the insurance card information of the user of the terminal 20 and the examination ticket information, and the QR code generation unit 62 is used to acquire information that combines the insurance card information and the examination ticket information. Possible URL (Uniform Resource Locator) can be included in the QR code. In this case, the hospital reception apparatus 10 accesses the URL acquired by reading the QR code, acquires the insurance card information and the examination ticket information of the user of the terminal 20, and performs reception processing. In addition, the target of notifying the access destination of information by the URL is not limited to the combination of the insurance card information of the user of the terminal 20 and the examination ticket information. For example, the access destination may be specified by URL for either one of the insurance card information and the examination ticket information. In this case, for the information whose access destination is not specified by the URL, the information itself is transmitted from the information processing apparatus 30 to the terminal 20. In addition, for both the insurance card information and the examination ticket information, the access destination may be individually designated by a URL. Furthermore, the URL is an example of an access destination designation method, and the access destination designation method may be arbitrarily changed. Here, taking the information used for the reception process at the hospital as an example, the case where information specifying the access destination is transmitted to the terminal 20 has been described. However, the information transmitted to the terminal 20 at the time of reception at the pharmacy Alternatively, the access destination may be transmitted to the terminal 20 instead of the information itself.

  In the above description, the case where FIDO authentication is used for identity verification has been described as an example. However, authentication processing other than FIDO authentication may be used.

  The position information used when selecting a dispensing pharmacy can be any information that can be acquired by the terminal 20 and can be used for specifying the position, and is not limited to GPS information. For example, base station information with which the terminal 20 has established a connection may be used.

  The position information used when selecting a dispensing pharmacy is not limited to the current location of the terminal 20, and may be, for example, information on a position input by the user to the terminal 20. With this modification, for example, when the user is away from home or office on the way home from a hospital or the like, the position used for searching for a pharmacy that receives the medicine can be set near the home or office. . Then, the user can apply for dispensing at a position away from home or office, and can move toward the home or office while being dispensed. Furthermore, the user can receive medicine from a nearby pharmacy such as home or office when dispensing is finished.

  The QR code may have an expiration date. When an expiration date is provided for the QR code, the service processing unit 63 manages the expiration date. The hospital server 4 and the pharmacy server 6 that have acquired the QR code information via the reception apparatus 10 inquire the information processing apparatus 30 about the validity of the QR code information. When the inquiry is received within the expiration date, the service processing unit 63 notifies the inquiry source that the QR code is valid, and the processing at the inquiry source is continued. On the other hand, when the inquiry is received after the expiration date has passed, the service processing unit 63 notifies the inquiry source that the QR code is invalid, and requests the inquiry source to end the process. The hospital server 4 and the pharmacy server 6 end the processing in response to a request from the information processing device 30. By deforming in this way, it is possible to further prevent unauthorized use of the insurance card.

  Even if the information processing apparatus 30 acquires personal information such as insurance card information, examination ticket information, and credit card information from the health insurance server 2, the hospital server 4, the financial institution server 8, and the like, the information processing apparatus 30 holds the information for a predetermined period. good. When the information is acquired in this manner, when the information is requested from the terminal 20 within a predetermined period after the acquisition of the information, the information processing device 30 may include the health insurance server 2, the hospital server 4, the financial institution server 8, and the like. The requested information can be transmitted to the terminal 20 without making an inquiry to. For this reason, the response time to the request of the terminal 20 is shortened and the processing load of the information processing device 30 is reduced as compared with the case where an inquiry is made from the information processing device 30 to the health insurance server 2 each time.

  When holding personal information such as insurance card information, examination ticket information, and credit card information over a predetermined period, the information processing apparatus 30 may hold these personal information in association with the terminal 20. For example, when it is confirmed that the insurance card information related to the processing target user is registered in the health insurance server 2 by acquiring the health insurance access token, the information processing apparatus 30 displays the insurance card of the terminal 20 and the user of the terminal 20. Information may be stored in association with each other. Similarly, regarding the medical examination ticket information, if it is possible to confirm that the medical examination ticket information is registered in the hospital server 4 by acquiring the hospital access token, the information processing apparatus 30 will obtain the medical examination ticket of the terminal 20 and the user of the terminal 20. Information may be stored in association with each other. With this modification, the response time for the inquiry from the terminal 20 can be further shortened. Further, after such processing, the information processing apparatus 30 transmits, to the terminal 20, a list of medical institutions storing medical examination ticket information associated with the terminal 20 in response to access from the terminal 20. Also good. In this case, based on the list received from the information processing apparatus 30, the terminal 20 can display a list of candidates for medical examination on the screen. At this time, the terminal 20 can display a list of medical institutions so that each medical institution can be selected, for example, as in the display example of the screen shown in FIG. If it deform | transforms in this way, even if the registration state of a medical examination ticket is changed by the deletion of registration of a medical examination ticket, etc., the user of the terminal 20 can grasp | ascertain the registration situation of the medical examination ticket to the information processing apparatus 30 easily.

  In the above description, the process management of the application is performed on the terminal 20 side, but the process management may be performed by the application control unit 64 in the information processing apparatus 30. In this case, for example, OCR processing can also be performed by the information processing apparatus 30. When the OCR process is performed by the information processing device 30, the information processing device 30 receives a captured image of a health insurance card or a captured image of a medical examination ticket from the terminal 20. Furthermore, the acquisition unit 42 and the acquisition unit 61 of the information processing device 30 access the health insurance server 2 and the hospital server 4 based on information obtained by the OCR processing in the information processing device 30. One of the insurance card and the examination ticket may be OCR processed by the information processing apparatus 30 and the other may be OCR processed by the terminal 20.

2 Health insurance server 4 Hospital server 6 Pharmacy server 8 Financial institution server 10 Accepting device 20 Terminal 21, 31 Communication unit 22 Camera 23 Application processing unit 24, 41 Authentication processing unit 25 Display unit 26, 50, 70 Storage unit 30 Information processing device 32 Health care information processing unit 40 Authentication information processing unit 42, 61 Acquisition unit 51 PIN information 52 Correspondence table 60 Control unit 62 QR code generation unit 63 Service processing unit 64 Application control unit 71 Hospital information 72 Pharmacy information 80 Insured person database 101, 111 Processor 102, 112 Memory 103, 117 Bus 104 Network Connection Device 113 Input Device 114 Display Device 115 Camera 116 Wireless Processing Device 118 Biological Information Reader

Claims (10)

Obtaining a first token to be used for inquiry of information on the insurance card identified by the identification information notified from the terminal from a server device holding the insurance card information;
Obtaining a second token used for inquiry of information on a medical examination ticket associated with information notified from the terminal from a server device holding information used by a medical institution;
When receiving from the terminal information indicating successful authentication of the user of the terminal and information designating the medical institution, the information on the insurance card obtained using the first token, and the second An information providing program for causing a computer to execute a process of transmitting the information on the examination ticket acquired using the token to the terminal. Receiving prescription information issued by the medical institution for the user of the terminal,
A list of pharmacies holding devices capable of transmitting the prescription information is transmitted to the terminal,
When receiving pharmacy information designating a pharmacy included in the list from the terminal, and information indicating that the user of the terminal has been successfully authenticated, information on the insurance card obtained using the first token, and The information providing program according to claim 1, wherein the computer is caused to execute a process of transmitting the prescription information to a server device of a pharmacy identified by the pharmacy information. From a financial institution server device associated with the credit card information notified from the terminal, obtain a third token to be used for payment processing of the user of the terminal,
When receiving the dispensing result of the medicine specified by the prescription information from the server device used by the pharmacy specified by the pharmacy information, the dispensing result is transmitted to the terminal,
When receiving information indicating approval of the dispensing result and authentication of the user from the terminal, the medicine specified by the dispensing result in the server device of the financial institution using the third token. The information providing program according to claim 2, wherein the computer is caused to execute a process of requesting a payment process of the price. When the end of the payment processing for the medicine is notified from the server device of the financial institution, it includes information indicating that the payment of the price has ended and the prescription information, and is designated by the pharmacy information The information providing program according to claim 3, wherein the computer is caused to execute a process of transmitting an information code readable by a pharmacy accepting device to the terminal. When receiving the billing information of the examination fee for the user of the terminal from the server device used by the medical institution, the billing information is transmitted to the terminal,
Upon receiving from the terminal information indicating that the billing information has been approved and that the user has been successfully authenticated, the diagnosis specified by the billing information is made to the financial institution server device using the third token. 5. The information providing program according to claim 3, wherein the computer is caused to execute processing for requesting fee payment processing. 6. Information indicating that the user of the terminal has been successfully authenticated and information to be transmitted to the terminal when information specifying the medical institution is received are information on the insurance card obtained using the first token, The information code includes information on the examination ticket acquired by using the second token and is readable by a reception device installed in the medical institution. The information providing program according to any one of the above. Obtaining a first token to be used for inquiry of information on the insurance card identified by the identification information notified from the terminal from a server device holding the insurance card information;
Obtaining a second token used for inquiry of information on a medical examination ticket associated with information notified from the terminal from a server device holding information used by a medical institution;
When receiving from the terminal information indicating successful authentication of the user of the terminal and information designating the medical institution, the information on the insurance card obtained using the first token, and the second An information providing method, wherein the computer executes a process of transmitting the information on the examination ticket acquired by using the token to the terminal. The first token used for the inquiry of the insurance card information identified by the identification information notified from the terminal is acquired from the server device holding the insurance card information, and is associated with the information notified from the terminal An acquisition unit that acquires a second token used for inquiry of information on a medical examination ticket from a server device that holds information used by a medical institution;
When receiving from the terminal information indicating successful authentication of the user of the terminal and information designating the medical institution, the information on the insurance card obtained using the first token, and the second An information providing apparatus comprising: a communication unit that transmits information on the examination ticket acquired using the token of the terminal to the terminal. In an information processing apparatus accessible to a system comprising a database for storing insurance card information including identification information of an insured person,
After confirming the existence of the information of the insured person by accessing the system based on the identification information of the insured person extracted from the captured image of the insurance card received from the terminal or the identification information of the insured person received from the terminal, Storing association information between the terminal and the identification information in the storage unit;
Information on the medical institution corresponding to the examination ticket extracted from the captured image of the examination ticket received from the terminal and information on the subject of the examination ticket, or information on the medical institution corresponding to the examination ticket received from the terminal Based on the information of the subject of the medical examination ticket, access to the corresponding system of the medical institution, confirm the existence of the information of the subject of the medical examination ticket, and then associate each terminal with the subject information for each medical institution Store the information in the storage,
In response to designation of a medical institution from the terminal, subject information associated with the terminal for the designated medical institution or access destination information to the subject information, and an insured person associated with the terminal Transmitting the identification information of or the access destination information to the identification information of the insured person to the terminal,
An information providing program for causing a computer to execute processing. In an information processing apparatus accessible to a system comprising a database for storing insurance card information including identification information of an insured person,
Information of the medical institution corresponding to the medical examination ticket extracted from the captured image of the medical examination ticket received from the terminal and the information of the subject of the medical examination ticket or the information of the medical institution corresponding to the medical examination ticket received from the terminal and the examination ticket After accessing the corresponding medical institution system based on the information of the target person and confirming the existence of the information of the target person of the examination ticket, each association information of the terminal and the target person information is stored in the storage unit for each medical institution Remember,
In response to access from the terminal, a list of medical institutions stored in association with the terminal in the storage unit is transmitted to the terminal.
An information providing program for causing a computer to execute processing.