Information processing method

Abstract

Provided is an information processing method capable of effectively utilizing health information including results of various tests conducted at medical institutions.　The health information is stored in a database in association with user identification information for each user. A computer, upon acquiring user identification information read by a dispersedly located management system, reads the health information associated with the acquired user identification information from the database. Then, the computer outputs the read health information to the management system.

Description

Technical Field

[0001] The present disclosure relates to an information processing method.

Background Art

[0002] In recent years, at the entrances of various facilities, the body temperature of users has been measured using a thermal camera or the like, and the entry of users into the facility has been restricted according to the measurement results. Further, in Patent Document 1, a system has been proposed in which a user acquires authentication information indicating that he / she does not carry a pathogen using a pathogen sensor, and the entry gate is opened based on the authentication information, thereby permitting entry into the facility.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the system disclosed in Patent Document 1, a user can detect the presence or absence of a pathogen in his / her breath using a pathogen sensor installed in a home or a public facility or the like. On the other hand, although a user may undergo various tests as necessary at a medical institution or the like, the test results are not used except when a doctor diagnoses a medical condition. Since the tests performed at a medical institution or the like are highly reliable, it is desirable that they be effectively utilized.

[0005] The present disclosure has been made in view of such circumstances, and an object thereof is to provide an information processing method capable of effectively using health information of a user including various test results obtained at a medical institution or the like.

Means for Solving the Problems

[0006] An information processing method according to an aspect of the present disclosure stores health information in a database in association with user identification information for each user, acquires the user identification information read by a distributed management system, reads out the health information corresponding to the acquired user identification information from the database, and outputs the read health information to the management system.

Effect of the Invention

[0007] In the present disclosure, it is possible to effectively utilize the health information of a user including various test results performed at a medical institution or the like.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4A

Figure 4B

Figure 4C

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9A

Figure 9B

Figure 9C

Figure 10

Figure 11

Figure 12A

Figure 12B

Figure 13

Figure 14A

Figure 14B

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23

Figure 24

Figure 25

Figure 26

Figure 27

Figure 28

Figure 29

Figure 30

Figure 31

Figure 32

Figure 33

Figure 34

Figure 35

Figure 36A

Figure 36B

Figure 37

Modes for Carrying Out the Invention

[0009] Hereinafter, the information processing method of the present disclosure will be described in detail based on the drawings showing its embodiments.

[0010] (Embodiment 1) An information processing system that restricts the passage of users at various checkpoints (pass gates) using the health information of users including various test results obtained at medical institutions and the like will be described. The passage restriction at a checkpoint includes, for example, restricting the participation of users in various events or restricting the entry of users into various facilities. The events for which participation restrictions are imposed in the present disclosure can be various events such as concerts and exhibitions. In addition, the facilities for which entry restrictions are imposed in the present disclosure include schools, medical institutions, welfare facilities, public facilities, facilities of public transportation, theme parks, amusement facilities, companies, stores, etc., and immigration control facilities (including drive-through checks) at the borders at airports and ports, as well as facilities that manage entry and exit to specific areas, and can be various facilities. The participation restriction or entry restriction may be one that restricts entry into a building or a site, may be one that restricts entry into each room within a building, or may be one that restricts passage through a predetermined checkpoint (pass gate).

[0011] FIG. 1 is a schematic diagram showing a configuration example of the information processing system. The information processing system 100 of the present embodiment includes a server 10, a user terminal 20, an admission management server 30, a registration terminal 40, etc., and the server 10, the user terminal 20, the admission management server 30, and the registration terminal 40 are configured to be communicable via a network N such as the Internet.

[0012] Server 10 is a computer that manages the personal health information (PHR: Personal Health Record) of users who have been registered in advance. Personal health information includes, for example, the test results of various clinical examinations, health check-ups, and various tests received during a comprehensive medical check-up that the user has undergone at a medical institution or the like. Clinical examinations include tests for the presence or absence of infections caused by pathogens of infectious diseases such as the coronavirus (SARS-Cov, MERS-Cov, SARS-Cov-2 (hereinafter referred to as the "novel coronavirus")), influenza virus, hepatitis B virus (HBV), hepatitis C virus (HCV), norovirus, Streptococcus pneumoniae, adenovirus, etc., and tests for the presence or absence of allergic diseases to allergens such as milk (dairy products), wheat, eggs, almonds, peanuts, shrimp, crab, etc. Various test items are included. In addition, each test item includes various tests for determining the presence or absence of antigens or antibodies, etc., derived from the virus or bacteria, etc. to be tested. For example, antigen tests, PCR (Polymerase Chain Reaction) tests, antibody tests, etc. are included. Note that antibody tests include, for example, tests for the presence or absence of IgM antibodies or IgG antibodies against a specific virus or bacteria, or tests for the presence or absence of both IgM antibodies and IgG antibodies, and tests for measuring the antibody levels of each antibody. Personal health information may also include medical examination data regarding treatment history, surgical history, rehabilitation history, medication history, etc. received at a medical institution or the like, the types and amounts of medications being taken, the frequency and amounts of smoking and drinking, information (genetic information) such as the personal and family medical history (medical history, allergy history, etc.). Furthermore, personal health information may include the vaccination history for preventing the infection of various infectious diseases. The vaccination history may include, in addition to the presence or absence of vaccination, information such as the type of vaccine (drug name, manufacturer name, lot number, etc.), the number of vaccinations, the vaccination time (vaccination date), the elapsed period since vaccination, and the information of the medical institution where the vaccination was received. Note that health information does not include simple physical information such as an individual's height, age, weight, etc., but these physical information may be registered incidentally.

[0013] Server 10 is an information processing device capable of various information processing and information transmission and reception, and is configured using, for example, a server computer or a personal computer. Server 10 may be configured with multiple units for distributed processing, may be realized by multiple virtual machines provided in one server, or may be realized using a cloud server. User terminal 20 is a terminal used by a user whose personal health information is managed by server 10. User terminal 20 is configured using an information processing device such as a smartphone, a tablet terminal, or a personal computer, and may be configured by a dedicated terminal. Admission management server 30 is configured using, for example, a server computer or a personal computer. Admission management server 30 may be configured with multiple units for distributed processing, may be realized by multiple virtual machines provided in one server, or may be realized using a cloud server. Admission management server 30 is communicably configured with gate device 30a distributed at locations where user participation restrictions or admission restrictions (passage restrictions) are imposed. Gate device 30a is installed at the entrance of a building of a facility or the entrance to the site, the entrance to each room in the building, etc. Admission management server 30 and gate device 30a constitute a management system (admission management system) for managing a user's participation in an event or entry into a facility (passage through a passage point). In this embodiment, admission management server 30 controls the operations of multiple gate devices 30a, but each gate device 30a may have the functions of admission management server 30. Registration terminal 40 is a terminal used by the organizer of an event where participation restrictions are imposed or the person in charge of a facility where admission restrictions are imposed, using the admission management system. Registration terminal 40 is configured using an information processing device such as a personal computer, a tablet terminal, or a smartphone.

[0014] In the information processing system 100 of the present embodiment, a user who wants to participate in various events or enter various facilities uses the user terminal 20 to receive a code including the user's identification information from the server 10. Note that the server 10 generates a code including the user's identification information in response to a request from the user terminal 20 and transmits it to the user terminal 20. Then, when the user participates in an event or enters a facility, the user causes the user terminal 20 to display the code and have it read by the code reader 36 of the gate device 30a. When the entry management server 30 reads the code by the code reader 36 and acquires the user's identification information, the entry management server 30 requests the server 10 to determine whether the user is allowed to participate in the event or enter the facility based on the user's identification information. The server 10 determines whether the user is allowed to participate in the event or enter the facility based on the user's personal health information in response to a request from the entry management server 30, and transmits the determination result to the entry management server 30. Thereby, when the user participates in an event or enters a facility, the server 10 determines whether the user is allowed to participate or enter based on the user's identification information read by the entry management server 30 from the user terminal 20, and the entry management server 30 can acquire the determination result. Note that the organizer of an event that imposes participation restrictions registers in advance with the server 10 the participation conditions for imposing participation restrictions on the event using the registration terminal 40, and the person in charge of a facility that imposes entry restrictions registers in advance with the server 10 the entry conditions for imposing entry restrictions on entry into the facility using the registration terminal 40.

[0015] In this embodiment, the case where a user participates in an event means the case where a user who participates in various events such as a concert or an exhibition enters the event venue or the concert venue. Also, the case where a user enters a facility means the case where children, students, etc. go to school, the case where patients, etc. enter a building such as a medical institution or a welfare facility, the case where users using public transportation such as airplanes and bullet trains pass through the boarding gate of an airport or the ticket gate of a station, the case where employees of a company, etc. enter the building or the interior of the company, the case where customers of a restaurant, etc. enter the store, etc. can be considered. In addition, regarding the case where a user enters various facilities such as public facilities, theme parks, or play facilities, the case where a user enters and exits a country at the border, the case where a user enters and exits a specific area, etc., they can also be targeted for entry restrictions.

[0016] Figure 2 is a block diagram showing a configuration example of the server 10 and the user terminal 20. The server 10 includes a control unit 11, a storage unit 12, a communication unit 13, an input unit 14, a display unit 15, a reading unit 16, etc., and each of these units is interconnected via a bus. The control unit 11 includes one or more processors such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), or a GPU (Graphics Processing Unit). The control unit 11 performs various information processes, control processes, etc. that the server 10 should perform by appropriately executing the control program 12P stored in the storage unit 12.

[0017] The storage unit 12 includes a RAM (Random Access Memory), a flash memory, a hard disk, an SSD (Solid State Drive), etc. The storage unit 12 stores in advance a control program 12P executed by the control unit 11 and various types of data necessary for the execution of the control program 12P. Also, the storage unit 12 temporarily stores data and the like generated when the control unit 11 executes the control program 12P. Further, the storage unit 12 stores a user DB (database) 12a, an event DB 12b, a facility DB 12c, and a determination result DB 12d, which will be described later. The user DB 12a, the event DB 12b, the facility DB 12c, and the determination result DB 12d may be stored in another storage device connected to the server 10, may be stored in another storage device to which the server 10 can communicate via the network N, or may be stored in a plurality of other servers to which the server 10 can be connected in a distributed ledger format such as a blockchain with consistency.

[0018] The communication unit 13 is an interface for connecting to the network N by wired communication or wireless communication, and transmits and receives information to and from other devices via the network N. The input unit 14 receives an operation input by a user who uses the server 10 and sends a control signal corresponding to the operation content to the control unit 11. The display unit 15 is a liquid crystal display, an organic EL display, or the like, and displays various types of information according to an instruction from the control unit 11. The input unit 14 and the display unit 15 may be a touch panel configured integrally.

[0019] The reading unit 16 reads information stored in a portable storage medium 1a including a CD (Compact Disc)-ROM, a DVD (Digital Versatile Disc)-ROM, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, etc. The control program 12P and various data stored in the storage unit 12 may be read by the control unit 11 from the portable storage medium 1a via the reading unit 16 and stored in the storage unit 12. Also, the control program 12P and various data stored in the storage unit 12 may be downloaded by the control unit 11 from another device via the communication unit 13 and stored in the storage unit 12.

[0020] The user terminal 20 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, a display unit 25, etc., and these units are interconnected via a bus. Since each of the control unit 21, the storage unit 22, the communication unit 23, the input unit 24, and the display unit 25 of the user terminal 20 has the same configuration as the control unit 11, the storage unit 12, the communication unit 13, the input unit 14, and the display unit 15 of the server 10, a detailed description thereof is omitted. Note that the storage unit 22 of the user terminal 20 stores, in addition to the control program 22P executed by the control unit 21, a PHR application program 22AP (hereinafter referred to as the PHR app 22AP) for browsing personal health information managed by the server 10.

[0021] FIG. 3 is a schematic diagram showing a configuration example of the user DB 12a, FIG. 4A is a schematic diagram showing a configuration example of the event DB 12b, FIG. 4B is a schematic diagram showing a configuration example of the facility DB 12c, and FIG. 4C is a schematic diagram showing a configuration example of the determination result DB 12d. The user DB 12a stores various types of information including personal health information for each registered user. The user DB 12a shown in FIG. 3 includes a user ID column, a name column, an infectious disease test column, an allergy test column, and the like. The user ID column stores user identification information (user ID) assigned to each registered user, and the name column stores the name of the user specified at the time of user registration in association with the user ID. The infectious disease test column stores the results of tests for determining the presence or absence of infection with infectious diseases received by the user in association with the user ID. Examples of pathogens of infectious diseases include coronavirus, influenza virus, hepatitis B virus, hepatitis C virus, norovirus, pneumococcus, adenovirus, etc. For each infectious disease, the test results of antigen test, antibody test, PCR test and the test date are stored. Note that the result of the antibody test may include, for example, the presence or absence of IgM antibody and / or IgG antibody against the virus or bacterium to be tested, and further, the measurement result of the antibody amount of each antibody. The allergy test column stores the results of tests for determining the presence or absence of allergic diseases received by the user in association with the user ID. Examples of allergens include milk, wheat, eggs, almonds, peanuts, shrimps, crabs, etc. For each allergen, the test result and the test date are stored. The user ID stored in the user DB 12a is issued and stored by the control unit 11 when a new user is registered. The name stored in the user DB 12a is stored by the control unit 11 when the control unit 11 acquires the name of a new user via the communication unit 13 or the input unit 14. The results of the infectious disease test and the allergy test stored in the user DB 12a are stored by the control unit 11 when the control unit 11 acquires each test result via the communication unit 13 or the input unit 14. Also, the results of the infectious disease test and the allergy test may be deleted by the control unit 11 when, for example, a predetermined expiration date has passed since the test date.In addition, an expiration flag may be provided in the user DB 12a in association with the results of each of the infectious disease test and the allergy test, and when a predetermined expiration period has elapsed since the test date, the control unit 11 may change the expiration flag corresponding to each test result from 0 to 1. The expiration period is set in advance for each test item and stored in the storage unit 12. The stored content of the user DB 12a is not limited to the example shown in FIG. 3, and various types of information about the user may be stored. For example, biometric information such as the user's height, weight, and body fat percentage, examination data such as treatment, surgery, and rehabilitation at a medical institution, etc., the type and amount of medicine being taken, the frequency and amount of smoking and drinking, the medical history of the user himself and his family, the vaccination history, etc. may be stored in the user DB 12a. When the vaccination history is stored, information regarding the user's vaccination history is stored in the vaccination column in association with the user ID. Examples of the types of vaccines include vaccines against coronavirus, influenza virus, hepatitis B virus, poliovirus, pneumococcus, etc. For each type of vaccine (drug name), the vaccination date (vaccination time), vaccine information regarding the vaccinated vaccine, information such as the medical institution where the vaccination was received, etc. are stored. The vaccine information includes, for example, the manufacturer name, lot number, and number of vaccinations (which vaccination). The information of the vaccination institution includes the name of the medical institution, etc., and the location (e.g., country name, prefecture name). Also, the information regarding vaccination may be deleted by the control unit 11 when a predetermined expiration period has elapsed since the vaccination date. In addition, an expiration flag may be provided in the user DB 12a in association with each vaccine, and when a predetermined expiration period has elapsed since the vaccination date, the control unit 11 may change the expiration flag corresponding to each vaccine from 0 to 1.

[0022] The event DB 12b stores information about events registered by the event organizers for each event. The event DB 12b shown in FIG. 4A includes an event ID column, an event name column, a host ID column, a participation condition column, etc. The event ID column stores event identification information (event ID, passing point identification information) assigned to each registered event. The event name column, the host ID column, and the participation condition column store, in association with the event ID, the name of the event specified at the time of event registration, the identification information (host ID) assigned to the event organizer, and the conditions for permitting participation in the event, respectively. As the participation conditions, conditions using inspection results for various inspection items are used. For example, in the example shown in FIG. 4A, for the event with the event ID I001, conditions using a plurality of inspection items, such as a negative antigen test for the novel coronavirus and a negative PCR test for the novel coronavirus, are set. Although not shown, the presence or absence of vaccination and the number of vaccination times (within a predetermined period) may be set as conditions. The event ID stored in the event DB 12b is issued and stored by the control unit 11 when a new event is registered. Other information stored in the event DB 12b is stored by the control unit 11 when the control unit 11 acquires each information of a new event via the communication unit 13 or the input unit 14, and is changed by the control unit 11 when a change instruction is acquired. The stored content of the event DB 12b is not limited to the example shown in FIG. 4A, and various information about the event may be stored. For example, the date and time when the event is held, the start date and time of entry to the event venue, etc. may be stored. Also, the expiration date of the inspection uniquely determined by the organizer as the event participation condition may be stored and used in the process of determining whether to permit entry, which will be described later.

[0023] The facility DB 12c stores information about facilities registered by the person in charge of each facility. The facility DB 12c shown in FIG. 4B includes a facility ID column, a facility name column, an address column, an admission condition column, etc. The facility ID column stores facility identification information (facility ID, passing point identification information) assigned to each registered facility. The facility name column, the address column, and the admission condition column respectively store, in association with the facility ID, the name of the facility, the address of the facility, and the conditions for permitting entry into the facility specified at the time of facility registration. As the admission conditions, conditions using the test results for various test items are used. For example, in the example shown in FIG. 4B, for the facility with the facility ID S003, conditions using a plurality of test items, that is, the antigen test for influenza virus is negative and the antigen test for novel coronavirus is negative, are set. Also, although not shown, the presence or absence of vaccination and the number of vaccinations (within a predetermined period) may be set as conditions. The facility ID stored in the facility DB 12c is issued and stored by the control unit 11 when a new facility is registered. Other information stored in the facility DB 12c is stored by the control unit 11 when the control unit 11 acquires each information of a new facility via the communication unit 13 or the input unit 14, and is changed by the control unit 11 when a change instruction is acquired. The stored content of the facility DB 12c is not limited to the example shown in FIG. 4B, and various information about the facility may be stored. For example, the date and time, day of the week, time zone, etc. when entry into the facility is possible may be stored.

[0024] The determination result DB12d stores the user IDs of users who are permitted to participate in an event or enter a facility and users who are denied. The determination result DB12d shown in FIG. 4C includes an event ID / facility ID column, a permitted user column, a denied user column, and the like. The event ID / facility ID column stores the event ID of each event or the facility ID (passing point identification information) of each facility. The permitted user column stores the user IDs of users who are permitted to participate in an event or enter a facility, in association with the event ID / facility ID. The denied user column stores the user IDs of users who are denied to participate in an event or enter a facility, in association with the event ID / facility ID. Note that the denied user column may be configured to store the number of denied users instead of storing the user IDs. The event ID / facility ID stored in the determination result DB12d is the event ID registered in the event DB12b or the facility ID registered in the facility DB12c when new event information is registered in the event DB12b or new facility information is registered in the facility DB12c, and is stored by the control unit 11. The permitted users stored in the determination result DB12d are such that when each user is permitted to participate in an event or enter a facility, the user ID of the permitted user is stored by the control unit 11, and the denied users are such that when each user is denied to participate in an event or enter a facility, the user ID of the denied user is stored by the control unit 11. The stored content of the determination result DB12d is not limited to the example shown in FIG. 4C.

[0025] FIG. 5 is a block diagram showing a configuration example of the entrance management server 30 and the registration terminal 40. The entrance management server 30 includes a control unit 31, a storage unit 32, a communication unit 33, a gate device communication unit 34, etc., and these units are interconnected via a bus. Since each of the control unit 31, the storage unit 32, and the communication unit 33 of the entrance management server 30 has the same configuration as the control unit 11, the storage unit 12, and the communication unit 13 of the server 10, detailed descriptions thereof are omitted. A gate device 30a is connected to the gate device communication unit 34, and the control unit 31 controls the operations of the respective units of the gate device 30a via the gate device communication unit 34. The gate device 30a includes a display unit 35, a code reader 36, a notification unit 37, a gate opening / closing unit 38, etc. Since the display unit 35 has the same configuration as the display unit 15 of the server 10, detailed descriptions thereof are omitted.

[0026] The code reader 36 is a device that reads a one-dimensional code such as a barcode and a two-dimensional code such as a QR code (registered trademark), or an RF tag that acquires information by radio waves (wireless communication) such as RFID, and decodes the read code to acquire code information. The code reader 36 sequentially sends the code information read from the code to the control unit 31.

[0027] The notification unit 37 is, for example, a light output unit such as an LED (Light Emitting Diode) light or a rotating light, or a sound output unit such as a buzzer or a speaker. The notification unit 37 may notify by lighting or flashing the light output unit, or may notify by voice through the buzzing of the buzzer or the sound output from the speaker. The notification unit 37 executes a predetermined notification process according to an instruction from the control unit 31 to notify a user passing through the gate device 30a that entry into the facility (participation in an event) has been permitted or rejected. Note that the notification unit 37 may be configured to perform a notification process by displaying various information on the display unit 35.

[0028] The gate opening / closing unit 38 controls the opening and closing of the gate 38a for blocking the progress of a user passing through the gate device 30a according to an instruction from the control unit 31. The gate opening / closing unit 38 promotes the progress of the user by opening the gate 38a according to an instruction from the control unit 31, and blocks the progress of the user by closing the gate 38a. As shown in FIG. 1, the gate device 30a of the present embodiment has an entrance passage formed by progressing in the direction indicated by the white arrow for entering the facility, and the gate 38a is provided at the exit of the entrance passage. Further, in the gate device 30a shown in FIG. 1, a code reader 36 is provided on the entrance side of the entrance passage on the right side in the progress direction of the user, and a display unit 35 and a notification unit 37 are provided on the exit side. The gate device 30a is not limited to the configuration shown in FIG. 1.

[0029] The registration terminal 40 includes a control unit 41, a storage unit 42, a communication unit 43, an input unit 44, a display unit 45, etc., and these units are interconnected via a bus. Since each of the control unit 41, the storage unit 42, the communication unit 43, the input unit 44, and the display unit 45 of the registration terminal 40 has the same configuration as the control unit 11, the storage unit 12, the communication unit 13, the input unit 14, and the display unit 15 of the server 10, detailed description thereof is omitted.

[0030] Hereinafter, in the information processing system 100 of the present embodiment, the processing performed by each device will be described using a flowchart. When a user receives various examinations at a medical institution, for example, the user transmits his / her user ID registered in the server 10 to the medical institution. Then, for example, a doctor or a medical technician uses a terminal (not shown) of the medical institution to register the examination results of various examinations in association with the user ID in the server 10. Thereby, the results of various examinations performed at a medical institution or the like can be registered in the server 10. That is, it is assumed that various examination results performed on each user are already registered in the user DB 12a of the server 10. Note that the user himself / herself may be configured to register his / her own examination results in the server 10 using the user terminal 20.

[0031] The process in which the organizer of an event or the person in charge of a facility registers information related to the event or information related to the facility using the registration terminal 40 will be described. FIG. 6 is a flowchart showing an example of the registration process procedure, and FIG. 7 is a schematic diagram showing an example of a screen. In FIG. 6, the processes performed by the registration terminal 40 are shown on the left side, and the processes performed by the server 10 are shown on the right side. The following processes are realized by the control unit 41 according to the control program 42P stored in the storage unit 42 of the registration terminal 40, and are realized by the control unit 11 according to the control program 12P stored in the storage unit 12 of the server 10. A part of the following processes may be realized by a dedicated hardware circuit.

[0032] In the information processing system 100 of the present embodiment, the organizer of an event registers information related to an event that restricts participation based on the health information of users in the server 10 using the registration terminal 40. Also, the person in charge of the facility registers information related to the facility that restricts entry based on the health information of users in the server 10 using the registration terminal 40. Note that the registration of information related to an event or information related to a facility can be performed, for example, from a website publicly available by the server 10 via the network N, or by executing a predetermined application program (for example, the PHR application 22AP stored in the user terminal 20). The control unit 41 of the registration terminal 40 acquires a registration screen for registering event information or facility information from the server 10 according to an operation by the user via the input unit 44 and displays it on the display unit 45 (S11).

[0033] FIG. 7 shows an example of a registration screen. The registration screen includes a checkbox for selecting either event registration or facility registration, an input field for the event name and an input field for the organizer ID that become available when event registration is selected, and an input field for the facility name and an input field for the address that become available when facility registration is selected. The input field for the event name is configured to allow any text data to be entered. The input field for the organizer ID has a pull-down menu for selecting any of the organizer IDs already registered in server 10. A new registration button for instructing the registration of a new organizer is provided near the input field for the organizer ID. The input fields for the facility name and the address are configured to allow any text data to be entered. The registration screen also has an input field for the conditions at the time of entry (participation conditions or entry conditions) when imposing participation restrictions or entry restrictions. The input field for the conditions has checkboxes for selecting either the test results (positive or negative) for various infectious diseases and the results of allergy tests for various allergens (presence or absence of allergies). Specifically, infectious diseases include the novel coronavirus, influenza virus, hepatitis B virus, hepatitis C virus, etc., and test items for infectious diseases include PCR tests, antigen tests, antibody tests, etc. Checkboxes are provided for selecting either positive or negative for each test item. Allergens include milk, wheat, eggs, almonds, peanuts, shrimp, crab, etc., and checkboxes are provided for selecting either presence or absence for each allergen (test item). Note that the conditions at the time of entry are not limited to the test results (positive or negative) for each test item of infectious diseases or the test results (presence or absence of allergies) for each allergen of allergy tests, and may be configured to allow various test items to be input (selected). Also, a checkbox for the presence or number of vaccinations (vaccinated once, vaccinated twice, etc.) and / or for being within a predetermined period from vaccination may be entered in the input field for the conditions. The above-mentioned conditions may be based on satisfying any one of them or on satisfying a plurality of them. The registration screen has a registration button for instructing the registration of the entered content.The registration screen is not limited to the configuration shown in FIG. 7.

[0034] On the registration screen shown in FIG. 7, when the event organizer or the person in charge of the facility inputs the content to be registered in each input field via the input unit 44 and instructs the registration of the input content, the registration button is operated. The control unit 41 receives the registration content (event information or facility information) for each input field on the registration screen (S12), and displays the received event information or facility information in each input field. Then, the control unit 41 determines whether the registration button on the registration screen has been operated (S13). If it is determined that it has not been operated (S13: NO), the process of step S12 is repeated. If it is determined that the registration button has been operated (S13: YES), the control unit 41 transmits the event information or facility information received via the registration screen to the server 10 and requests the server 10 to register the event information or facility information (S14).

[0035] When the control unit 11 of the server 10 receives a registration request for new event information or facility information from the registration terminal 40, it issues an event ID or a facility ID (S15), and stores the received event information or facility information (registration information) in the event DB 12b or the facility DB 12c in association with the issued event ID or facility ID (S16). Then, the control unit 11 transmits the issued event ID or facility ID to the registration terminal 40 (S17). When the control unit 41 of the registration terminal 40 receives the event ID or the facility ID from the server 10, it displays the received event ID or facility ID on the display unit 45 (S18) and notifies the event organizer or the person in charge of the facility of the event ID or the facility ID. Note that the control unit 41 may store the received event ID or facility ID in the storage unit 42. By the above-described process, each piece of information regarding the event or each piece of information regarding the facility can be registered in the server 10. As a result, the event information registered by the organizer for each event is registered in the event DB 12b of the server 10, and the facility information registered by the person in charge of the facility for each facility is registered in the facility DB 12c.

[0036] Next, a process will be described in which a user (a user who wants to participate in an event) who wants to enter the facility receives a code including the user's identification information from the server 10 using the user terminal 20. FIG. 8 is a flowchart showing an example of a code issuance process procedure, and FIGS. 9A to 9C are schematic diagrams showing screen examples. In FIG. 8, the processes performed by the user terminal 20 are shown on the left side, and the processes performed by the server 10 are shown on the right side. The following processes are realized by the control unit 21 according to the control program 22P stored in the storage unit 22 of the user terminal 20, and are realized by the control unit 11 according to the control program 12P stored in the storage unit 12 of the server 10. A part of the following processes may be realized by a dedicated hardware circuit.

[0037] In the information processing system 100 of the present embodiment, before participating in an event or entering the facility, the user starts the PHR app 22AP on the user terminal 20 and receives a code including the user's identification information from the server 10. When the control unit 21 of the user terminal 20 receives an execution instruction for the PHR app 22AP via the input unit 24, it starts the PHR app 22AP and displays an initial screen on the display unit 25 (S21). FIG. 9A shows an example of the initial screen. The initial screen has a test result confirmation button for instructing the confirmation of the test results registered in the server 10 and a code issuance button for requesting the issuance of a code to the server 10. Note that the PHR app 22AP can execute not only the process of receiving a code from the server 10 but also the process of receiving the test results registered in the server 10. On the initial screen, when the user operates the test result confirmation button, the control unit 21 displays a test item selection screen as shown in FIG. 9B on the display unit 25. Then, when a test item is selected via the selection screen, the control unit 21 requests the test results of the selected test item from the server 10 and, when it receives the test results from the server 10, displays them on the display unit 25. Thereby, the user can confirm their own test results registered in the server 10 using the user terminal 20. Note that in the process shown in FIG. 8, the test result confirmation process is omitted.

[0038] When the user wants to receive the code from Server 10, the user operates the code issuance button on the initial screen. The control unit 21 of the user terminal 20 determines whether the code issuance button has been operated (S22). If it determines that it has not been operated (S22: NO), it waits until it is operated. When it determines that the code issuance button has been operated (S22: YES), the control unit 21 requests Server 10 to issue the code (S23). At this time, the control unit 21 transmits the user ID of the user to Server 10 to request the issuance of the code.

[0039] When the control unit 11 of Server 10 receives a code issuance request from the user terminal 20, it performs user authentication based on the user ID received from the user terminal 20 (S24). Here, the control unit 11 determines whether the received user ID is registered in the user DB 12a. If it is registered, it authenticates that this user is a legitimate user. The control unit 11 determines whether it can authenticate that the user is a legitimate user (S25). If it determines that it can authenticate (S25: YES), it generates a code including the user ID received from the user terminal 20 (S26). In this embodiment, the control unit 11 generates a QR code, but it is not limited to the QR code.

[0040] The control unit 11 transmits the generated code to the user terminal 20 (S27). When the control unit 21 of the user terminal 20 receives the code from Server 10, it displays the received code on the display unit 25 as shown in FIG. 9C (S28) and notifies the user. The notification screen shown in FIG. 9C has a save button for instructing to store the displayed code in the PHR app 22AP and a close button for instructing to end the PHR app 22AP without storing the code. Therefore, when the save button on the notification screen is operated, the control unit 21 stores the displayed code in the PHR app 22AP, and when the close button is operated, it ends the display of the notification screen.

[0041] When it is determined that the user cannot be authenticated (S25: NO), the control unit 11 transmits error information indicating that the user ID is inappropriate to the user terminal 20 (S29). When the control unit 21 of the user terminal 20 receives the error information from the server 10, the received error information is displayed on the display unit 25 (S30) and notified to the user. Through the above-described processing, a legitimate user can receive a code including the user's identification information (user ID) from the server 10.

[0042] Next, a process of determining whether to permit participation or entry based on the health information registered in the server 10 when the user participates in an event or enters a facility will be described. FIGS. 10 and 11 are flowcharts showing an example of the determination processing procedure. In FIG. 10, the processing performed by the user terminal 20 is shown on the left side, the processing performed by the entrance management server 30 is shown in the center, and the processing performed by the server 10 is shown on the right side. In FIG. 11, the processing performed by the entrance management server 30 is shown on the left side, and the processing performed by the server 10 is shown on the right side. The following processing is realized by the control unit 21 according to the control program 22P stored in the storage unit 22 of the user terminal 20, realized by the control unit 31 according to the control program 32P stored in the storage unit 32 of the entrance management server 30, and realized by the control unit 11 according to the control program 12P stored in the storage unit 12 of the server 10. A part of the following processing may be realized by a dedicated hardware circuit.

[0043] In the information processing system 100 of the present embodiment, when the user participates in an event or enters a facility, the user activates the PHR application 22AP, causes the code received from the server 10 as described above to be displayed on the user terminal 20, and causes the gate device 30a to read it. Note that the code received by the user terminal 20 from the server 10 may be printed on, for example, a recording sheet or a card and used. In this case, even a user such as an elementary school student who does not carry the user terminal 20 can use the information processing system 100 of the present embodiment.

[0044] When the control unit 21 of the user terminal 20 receives an execution instruction for the PHR app 22AP and a code display instruction via the input unit 24, it activates the PHR app 22AP and displays the code stored in the PHR app 22AP on the display unit 25 (S31). At this time, the control unit 21 may display a screen as shown in FIG. 9C. The user holds the user terminal 20 on which the code is displayed in front of the code reader 36 of the gate device 30a to cause the code reader 36 to read the code. The control unit 31 of the entrance management server 30 reads the code with the code reader 36 (S32) and acquires the user ID included in the code (S33). Thereby, the control unit 31 (user information acquisition unit) acquires the identification information (user ID) of the user. The control unit 31 transmits the acquired user ID and the event ID of the event for which the entrance management server 30 manages the user's participation, or the facility ID of the facility for which the entrance management server 30 manages the user's entrance, to the server 10 (S34), and requests the server 10 to determine whether the user is permitted to participate in the event or enter the facility. The event ID or the facility ID is received from the server 10 when the registration terminal 40 registers the event information or the facility information in the server 10 in the process shown in FIG. 6, and is stored, for example, in the storage unit 32 of the entrance management server 30.

[0045] When the control unit 11 (acquisition unit) of the server 10 is requested by the admission management server 30 to determine whether to permit event participation or facility entry, it receives the user ID read by the admission management server 30 from the code and performs authentication processing based on the received user ID (S35). Here, the control unit 11 determines whether the received user ID is registered in the user DB 12a. If it is registered, the control unit 11 determines that this user is a legitimate user. The control unit 11 determines whether it can authenticate that the user is a legitimate user (S36). If it determines that authentication is successful (S36: YES), it determines whether the authenticated user has already been permitted to participate in the event or enter the facility (S37). Here, the control unit 11 determines whether the user ID of the authenticated user is registered in the determination result DB 12d as an authorized user, associated with the event ID or facility ID received from the admission management server 30. Then, if the user ID of the authenticated user is registered as an authorized user, the control unit 11 determines that the user has already been permitted.

[0046] When it is determined that the user is not an authorized user (S37: NO), the control unit 11 acquires the participation conditions for this event or the admission conditions for the facility (S38). Specifically, when the control unit 11 has received an event ID from the admission management server 30, the control unit 11 reads out the participation conditions corresponding to the event ID from the event DB 12b, and when it has received a facility ID, the control unit 11 reads out the admission conditions corresponding to the facility ID from the facility DB 12c. Then, the control unit 11 (reading unit) reads out the inspection results of the authenticated user from the user DB 12a for the inspection items corresponding to the read participation conditions or admission conditions (S39). For example, when the control unit 11 reads out the condition "Antigen test for novel coronavirus: negative", the control unit 11 reads out the result of the antigen test for the novel coronavirus of the authenticated user from the results of the infectious disease test stored in the user DB 12a. Then, the control unit 11 determines whether the read inspection results of the user satisfy the conditions acquired in step S38 (S40). For example, when the condition is "Antigen test for novel coronavirus: negative", the control unit 11 determines that the condition is satisfied if the read inspection result is negative, and determines that the condition is not satisfied if the result is positive. When the condition includes a plurality of inspection items such as "Antigen test for novel coronavirus: negative, PCR test for novel coronavirus: negative", the control unit 11 determines whether the inspection results satisfy the conditions for all the inspection items. In addition, the control unit 11 may determine whether the inspection date of the read inspection results is within the expiration date, and if the expiration date has passed, determine that the conditions are not satisfied.

[0047] When it is determined that the inspection result of the user does not satisfy the conditions acquired in step S38 (S40: NO), the control unit 11 (output unit) transmits rejection information (information regarding the inspection result) indicating rejection of participation or entry of this user and the reason for rejection to the entry management server 30 (S41). The reason for rejection includes information indicating the inspection items that did not satisfy the participation conditions or entry conditions among the inspection results of the user. For example, it may be included in the reason for rejection that the inspection result of the user is not the inspection result set for the participation conditions or entry conditions, that the user has not undergone the inspection of the inspection items set for the participation conditions or entry conditions, that the expiration date for the inspection result of the user has passed, etc. Also, when a plurality of inspection items are included in the conditions, the inspection items that satisfy the conditions and the inspection items that do not satisfy the conditions may be included in the reason for rejection. The control unit 31 (health information acquisition unit) of the entry management server 30 receives the rejection information determined by the server 10. When the control unit 31 receives the rejection information from the server 10, it closes the gate 38a by the gate opening / closing unit 38 (S43) and notifies the reason for rejection by the notification process of the notification unit 37 (S44). For example, when the notification unit 37 has an optical output unit, the control unit 31 notifies the reason for rejection by turning on or flashing the optical output unit, and when the notification unit 37 has an audio output unit, by performing audio output by the audio output unit. Also, the control unit 31 may notify by displaying a notification message on the display unit 35. Thereby, the entry management server 30 can notify the user passing through the entry passage and the organizer of the nearby event or the person in charge of the facility that participation in the event or entry into the facility has been rejected. Note that the control unit 31 may perform different notification processes according to the content of the reason for rejection.

[0048] After the process of step S41, the control unit 11 of server 10 associates the user ID of the user who has been refused participation or entry with the event ID or facility ID, and registers it in the rejected user column of the determination result DB 12d (S42). Note that the number of rejected users may be stored in the rejected user column of the determination result DB 12d. In this case, the control unit 11 adds 1 to the number of rejected users stored in the determination result DB 12d and updates it. When it is determined that the inspection result of the user satisfies the conditions acquired in step S38 (S40: YES), the control unit 11 (output unit) transmits permission information (information regarding the inspection result) indicating permission for this user to participate or enter to the entrance management server 30 (S45). Then, the control unit 11 associates the user ID of the user who has been permitted to participate or enter with the event ID or facility ID, and registers it in the permitted user column of the determination result DB 12d (S46).

[0049] On the other hand, when it is determined that authentication cannot be performed in step S36 (S36: NO), or when it is determined that permission has already been granted in step S37 (S37: YES), the control unit 11 transmits rejection information indicating rejection of participation or entry of this user to the entrance management server 30 (S47). Note that the control unit 11 may transmit the reason for rejection for which participation or entry has been rejected to the entrance management server 30. By not performing the determination process of whether the participation conditions or entry conditions are satisfied when the user cannot be authenticated, the execution target of the determination process can be limited to legitimate users. Also, by rejecting the participation or entry of a user who has already been permitted, it is possible to prevent duplicate issuance of participation permission or entry permission based on the same user ID.

[0050] The control unit 31 (health information acquisition unit, determination unit) of the admission management server 30 determines whether or not permission information has been received from the server 10 (S48). If it is determined that permission information has been received (S48: YES), the gate opening / closing unit 38 opens the gate 38a (S49). At this time, the control unit 31 may perform a notification process of notifying, by the notification unit 37, that participation in the event or entry into the facility has been permitted. If it is determined that permission information has not been received (S48: NO), that is, if rejection information has been received, the control unit 31 closes the gate 38a by the gate opening / closing unit 38 (S50), and notifies, by the notification process by the notification unit 37, that participation in the event or entry into the facility has been rejected (S51). At this time, if the control unit 31 has acquired the reason for rejection from the server 10, the reason for rejection may be notified.

[0051] By the above-described processing, in the information processing system 100 of the present embodiment, when a user participates in an event or enters a facility, based on the information on the test results of the user registered in the server 10, it is determined whether or not the participation conditions or entry conditions set for each event or facility are satisfied. Then, depending on whether or not the test results of the user satisfy the conditions, the user's participation in the event or entry into the facility is permitted or rejected. Therefore, since the personal health information of each user registered in the server 10 can be used for restricting the participation or entry of the user by the admission management system, it becomes possible to effectively use the highly reliable test results obtained at a medical institution or the like. By performing the participation restriction or entry restriction using the test results registered in the server 10 in this way, the sense of security for the event or facility can be enhanced, the safe implementation of the event and the safe use of the facility can be achieved, and the reliability for the event and the facility can be enhanced.

[0052] In this embodiment, since the code issued by the server 10 contains only the user ID, the code can be reused when participating in different events or entering different facilities. Therefore, by storing the code issued by the server 10 in the PHR app 22AP of the user terminal 20, it is possible to determine whether to allow participation or entry using the stored code when participating in different events or entering different facilities. Also, in this embodiment, since the user ID of the user whose participation or entry is permitted is registered in the determination result DB 12d, it is possible to grasp the users who are permitted to participate or enter for each event or facility. As a result, it is possible to grasp the users who participated in each event and the users who entered each facility, and it is possible to use the number of participants, for example, when charging for the execution of the determination process of whether participation or entry is permitted or not.

[0053] In this embodiment, when the server 10 issues a code in response to a request from the user terminal 20, the server 10 may issue a random temporary ID and issue a code including the temporary ID and the user ID to provide it to the user terminal 20. In this case, the admission management server 30 obtains the temporary ID and the user ID by reading the code displayed on the user terminal 20, and transmits the obtained temporary ID and user ID and the event ID or facility ID to the server 10 to request a determination of whether the user is permitted to participate or enter. Then, when the temporary ID received from the admission management server 30 matches the temporary ID stored in association with the user ID, the server 10 performs a determination process of whether participation or entry is permitted or not. With such a configuration, it is possible to prevent the code from being misused. Also, it may be configured to discard the temporary ID when the authentication process based on the temporary ID has been performed once. In this case, misuse of the code can be further prevented. Furthermore, an expiration date may be set for the code issued by the server 10. In this case as well, misuse of the code can be further prevented.

[0054] In this embodiment, when a user participates in an event or enters a facility, the server 10 determines whether to permit the user to participate or enter, and the determination result is notified to the admission management server 30. That is, since only the determination result is transmitted from the server 10 to the admission management server 30, leakage of the inspection results (personal health information) of each user registered in the server 10 can be avoided. Note that a configuration in which the admission management server 30 determines whether to permit the user to participate or enter may also be adopted. In this case, the admission management server 30 acquires the inspection results used for the determination of whether to permit participation or entry from the server 10, and determines whether the acquired inspection results satisfy the participation conditions or the entry conditions. Also in this case, the participation or entry of the user can be restricted using the personal health information of each user registered in the server 10. Note that in such a configuration, it is preferable that the server 10 encrypts the inspection results and then transmits them to the admission management server 30.

[0055] In this embodiment, the organizer of the event or the person in charge of the facility registers in advance in the server 10 the inspection items and inspection results used for the determination process of whether to permit participation or entry as the participation conditions or the entry conditions. However, the present invention is not limited to such a configuration. For example, a configuration may be adopted in which the organizer of the event or the person in charge of the facility notifies the user of the participation conditions or the entry conditions, and the user notifies the server 10 of the participation conditions or the entry conditions when requesting the issuance of a code from the server 10. Also, a configuration may be adopted in which the participation conditions or the entry conditions are registered in the admission management server 30, and the admission management server 30 transmits the participation conditions or the entry conditions to the server 10 when requesting the server 10 to determine whether to permit the user to participate or enter. Even in such a configuration, the server 10 can determine whether to permit the user to participate or enter based on the participation conditions or the entry conditions set for each event or facility.

[0056] In this embodiment, in addition to the inspection items and inspection results, a period (valid period) during which the inspection result is valid may be registered in the participation conditions or admission conditions set for each event or facility. The valid period can be, for example, a period within three months from the event date. In this case, when determining whether the user's inspection result meets the participation conditions or admission conditions, the server 10 determines whether the inspection date is within the valid period set in the participation conditions or admission conditions. Thereby, it becomes possible to determine whether to permit the user to participate or enter using the inspection result inspected within the valid period. Note that the server 10 periodically determines whether the valid period of each inspection result has elapsed based on the inspection date of each inspection result stored in the user DB 12a, and may sequentially delete the inspection results whose expiration date has passed from the user DB 12a or perform a process of changing the expiration flag from 0 to 1.

[0057] (Embodiment 2) A modification example of the admission management system will be described. FIG. 12A is a schematic diagram showing the admission management system of Embodiment 2, and FIG. 12B is a block diagram showing a configuration example of the admission management system of Embodiment 2. In the information processing system 100 of this embodiment, the admission management system is composed of an admission management terminal 50 composed of an information processing device such as a personal computer or a tablet terminal and a code reader 50a instead of the admission management server 30 and the gate device 30a. Since the other configurations are the same as those in Embodiment 1, detailed description thereof is omitted.

[0058] The access management terminal 50 and the code reader 50a may be wired-connected via a cable or may be configured to perform wireless communication. The access management terminal 50 of the present embodiment includes a control unit 51, a storage unit 52, a communication unit 53, an input unit 54, a display unit 55, a code reader connection unit 56, a notification unit 57, and the like. Each of the control unit 51, the storage unit 52, the communication unit 53, the input unit 54, and the display unit 55 of the access management terminal 50 has the same configuration as the control unit 11, the storage unit 12, the communication unit 13, the input unit 14, and the display unit 15 of the server 10 shown in FIG. 2. Since the notification unit 57 is the same as the notification unit 37 of the gate device 30a shown in FIG. 5, a detailed description thereof is omitted. The code reader connection unit 56 is an interface for connecting the code reader 50a and acquires the information read by the externally attached code reader 36 of the access management terminal 50.

[0059] In the access management system having such a configuration, the code reader 50a is installed at a location where participation restriction or access restriction is performed, such as an entrance of a facility, and the access management terminal 50 is installed and used at an arbitrary location within the facility. Note that the display unit 55 or the notification unit 57 may be configured to be externally attached to the access management terminal 50. In this case, the display unit 55 or the notification unit 57 may be installed at the entrance of the facility together with the code reader 50a. The access management system having such a configuration is installed and used in a facility that does not have a gate at the entrance, such as a store or a small-scale facility. Note that the access management system of the present embodiment may have a gate for restricting the entry of a user into the facility. In this case, the access management terminal 50 includes a gate opening / closing unit, and the gate opening / closing unit is configured to transmit an opening / closing instruction to the gate by wire communication or wireless communication.

[0060] In the information processing system 100 including the admission management system having the above-described configuration, each device also executes the same processing as the processing shown in FIG. 6 and executes the same processing as the processing shown in FIG. 8. As a result, also in the present embodiment, the event information or facility information input via the registration terminal 40 is registered in the server 10, and the code requested via the user terminal 20 is issued by the server 10 and provided to the user terminal 20. Also in the present embodiment, each device executes the same processing as the processing shown in FIGS. 10 and 11. In the present embodiment, in steps S32 and S33 in FIG. 10, the control unit 51 of the admission management terminal 50 acquires the user ID acquired by the code reader 50a reading the code via the code reader connection unit 56. Other processing is the same as in the first embodiment. When the information processing system 100 of the present embodiment does not have the gate opening / closing unit 38 and the gate 38a, the control unit 31 of the admission management server 30 does not execute the processing of steps S43, S49, and S50 in FIGS. 10 and 11.

[0061] By the above-described processing, also in the present embodiment, the same effects as those in the first embodiment can be obtained. Also in the present embodiment, since an admission management system configured by connecting a code reader 50a to an admission management terminal 50 configured by a personal computer, a tablet terminal, or the like is used, even in a facility where no gate is provided at the entrance, the use of the information processing system 100 (personal health information managed by the server 10) can be easily started.

[0062] (Embodiment 3) An information processing system in which, when the server 10 determines whether to permit a user to participate or enter, user authentication based on authentication data in addition to the user ID will be described. Since the information processing system 100 of the present embodiment can be realized by the same devices as the information processing system 100 of the first embodiment, detailed description of the configuration will be omitted. In the present embodiment, the user DB 12a, the event DB 12b, and the facility DB 12c stored in the storage unit 12 of the server 10 are slightly different from the configuration of the first embodiment shown in FIGS. 3 to 4B. Also, the admission management server 30 is slightly different from the configuration of the first embodiment shown in FIG. 5. Therefore, only the different parts will be described.

[0063] FIG. 13 is a schematic diagram showing a configuration example of the user DB 12a according to Embodiment 3. The user DB 12a of the present embodiment further has an IC (Integrated Circuit) card ID column and a face image information column in the configuration of Embodiment 1 shown in FIG. 3. The IC card ID column and the face image information column store the IC card ID and the face image information specified at the time of user registration in association with the user ID, respectively. The IC card ID is card information stored in an IC card assigned to the user, and the face image information is image data obtained by photographing the user's face. The IC card ID and the face image information are data used when authenticating the user, and may not be registered in the user DB 12a. In addition to being stored in the user DB 12a, the face image information may be stored in a predetermined area of the storage unit 12 or another storage device. In this case, the face image information column stores information (for example, a file name indicating the storage location) for reading the face image information. The IC card ID and the face image information stored in the user DB 12a are stored by the control unit 11 when the control unit 11 acquires each piece of information via the communication unit 13 or the input unit 14, and are changed by the control unit 11 when a change instruction is acquired.

[0064] FIG. 14A is a schematic diagram showing a configuration example of the event DB 12b according to Embodiment 3, and FIG. 14B is a schematic diagram showing a configuration example of the facility DB 12c according to Embodiment 3. Each of the event DB 12b and the facility DB 12c of the present embodiment further has an authentication method column in the configuration of Embodiment 1 shown in FIGS. 4A and 4B. The authentication method column stores the type of data used when authenticating (recognizing) the user in association with the event ID or the facility ID. The authentication method is set for each event or facility together with the event information or the facility information via a registration screen as shown in FIG. 7, for example, and a user ID, an IC card ID, a face image, etc. are used. The authentication method stored in the event DB 12b and the facility DB 12c is stored by the control unit 11 when the control unit 11 acquires it via the communication unit 13 or the input unit 14, and is changed by the control unit 11 when a change instruction is acquired.

[0065] FIG. 15 is a block diagram showing a configuration example of the entrance management system according to Embodiment 3. In addition to the configuration of Embodiment 1 shown in FIG. 5, the entrance management system of this embodiment has an IC card reader 36b and a camera 36c in the gate device 30a. The IC card reader 36b is a card reader that reads card information stored in an IC card. The camera 36c is an imaging device that performs imaging processing according to an instruction from the control unit 11 and sends the acquired image data (captured image) to the storage unit 12 for storage. The IC card reader 36b and the camera 36c may be configured to be externally attached to the gate device 30a in addition to being built into the gate device 30a. In this case, the gate device 30a includes a connection part capable of connecting an external IC card reader or camera, or a wireless communication part capable of wireless communication with an external IC card reader or camera.

[0066] In the information processing system 100 of this embodiment, each device executes the same processing as the processing shown in FIG. 6 and the processing shown in FIG. 8. As a result, also in this embodiment, the event information or facility information input via the registration terminal 40 is registered in the server 10, and the code requested via the user terminal 20 is issued by the server 10 and provided to the user terminal 20.

[0067] FIG. 16 is a flowchart showing an example of the determination processing procedure according to Embodiment 3. The processing shown in FIG. 16 is obtained by adding steps S61 to S62 instead of step S34 in the processing shown in FIG. 10, and adding steps S63 to S64 instead of step S35. Explanation of the same steps as in FIGS. 10 and 11 is omitted. Note that in FIG. 16, illustration of steps S37 to S51 in FIGS. 10 and 11 is omitted. The control unit 21 of the user terminal 20 and the control unit 31 of the entrance management server 30 according to the present embodiment perform the same processing as steps S31 to S33 shown in FIG. 10. Next, the control unit 31 of the entrance management server 30 acquires authentication data (authentication information) of the user using the IC card reader 36b or the camera 36c (S61). Note that authentication data used for user authentication is set for each event or facility, and when the user causes the code to be read by the gate device 30a, the gate device 30a reads the authentication data set for the event in which the user participates or the facility to be entered. Specifically, the control unit 31 reads the card ID stored in the IC card by the IC card reader 36b, or acquires the face image of the user by the camera 36c.

[0068] The control unit 31 transmits the event ID or facility ID, the acquired user ID, and the acquired authentication data to the server 10 (S62), and requests the server 10 to determine whether the user is permitted to participate in the event or enter the facility. When the control unit 11 of the server 10 is requested by the admission management server 30 to determine whether to permit event participation or entry into the facility, it identifies the authentication method set for the event of the received event ID or the facility of the facility ID (S63). Here, when the control unit 11 receives an event ID, it reads out the authentication method corresponding to the event ID from the event DB 12b, and when it receives a facility ID, it reads out the authentication method corresponding to the facility ID from the facility DB 12c. Then, the control unit 11 performs an authentication process based on the authentication data received from the admission management server 30 according to the read authentication method (S64). For example, when the control unit 11 reads out an authentication method using the user ID, it authenticates the user according to whether the received user ID is registered in the user DB 12a. Also, when the control unit 11 reads out an authentication method using the IC card ID, it performs an authentication process based on the received IC card ID (authentication data). Here, the control unit 11 determines whether the received IC card ID matches the IC card ID registered in the user DB 12a in association with the received user ID, and if they match, it determines that this user is a legitimate user. Further, when the control unit 11 reads out an authentication method using the face image, it determines whether the received face image information matches the face image information registered in the user DB 12a in association with the received user ID, and if they match, it determines that this user is a legitimate user.

[0069] Thereafter, the control unit 11 determines whether it has been able to authenticate that the user is a legitimate user (S36). If it determines that authentication has been successful (S36: YES), it proceeds to the process of step S37. If it determines that authentication has not been successful (S36: NO), it proceeds to the process of step S47. Through the above-described processing, in the information processing system 100 of the present embodiment, when the admission management server 30 requests the server 10 to determine whether to permit a user to participate or enter, the authentication data used for the authentication method corresponding to each event or facility is transmitted to the server 10. Therefore, when determining whether to permit a user to participate or enter, the server 10 can perform user authentication based not only on the user ID but also on the authentication data, making it possible to enhance security. Note that the authentication data is not limited to the IC card ID or face image information, and may be various biometric authentication data such as fingerprint, palm vein, finger vein, iris of the eye, voiceprint, etc., or may be configured to perform authentication by combining a plurality of biometric information.

[0070] In the present embodiment, the same effects as those of the above-described embodiments can be obtained. Also, in the present embodiment, when the server 10 determines whether to permit a user to participate or enter, since user authentication is performed using not only the user ID but also the IC card ID or face image, etc., security can be enhanced. Also in the present embodiment, the application of the modification examples appropriately described in the above-described embodiments is possible. Further, the configuration of the present embodiment can also be applied to the information processing system 100 of Embodiment 2, and the same effects can be obtained even when applied to the information processing system 100 of Embodiment 2. Specifically, in the configuration of the present embodiment, the admission management system of Embodiment 2 may be used.

[0071] (Embodiment 4) When a user participates in an event or enters a facility, in addition to the inspection results (health information) of the user registered in the server 10, the biometric information of the user is acquired, and an information processing system that determines whether the user is allowed to participate or enter using the inspection results and biometric information will be described. Since the information processing system 100 of the present embodiment can be realized by the same devices as the information processing system 100 of Embodiment 1, detailed description of the configuration will be omitted. Note that since the gate device 30a of the present embodiment is slightly different from the configuration of Embodiment 1 shown in FIG. 5, only the different parts will be described.

[0072] FIG. 17 is a block diagram showing a configuration example of the entrance management system according to Embodiment 4. The entrance management system of the present embodiment has a biometric information acquisition unit 39 in addition to the configuration of Embodiment 1 shown in FIG. 5. The biometric information acquisition unit 39 acquires biometric information such as the body temperature, respiratory rate, and heart rate of a user passing through the entrance passage. The biometric information acquisition unit 39 has a sensor that detects the biometric information of the user, and acquires the biometric information detected by the sensor. Note that the sensor may be a sensor that detects biometric information in a state of being in contact with the user, or a sensor that detects biometric information in a non-contact state. Further, the biometric information acquisition unit 39 may be configured to acquire biometric information detected by a wearable device from the wearable device worn by the user.

[0073] In the information processing system 100 of the present embodiment, each device executes the same processes as the processes shown in FIG. 6 and FIG. 8. As a result, also in the present embodiment, the event information or facility information input via the registration terminal 40 is registered in the server 10, and the code requested via the user terminal 20 is issued by the server 10 and provided to the user terminal 20.

[0074] FIG. 18 is a flowchart showing an example of the determination processing procedure according to Embodiment 4. The processing shown in FIG. 18 is obtained by adding steps S71 to S74 between steps S33 and S34 in the processing shown in FIG. 10. Explanation of the same steps as those in FIGS. 10 and 11 is omitted. Note that in FIG. 18, the illustration of steps S36 to S51 in FIGS. 10 and 11 is omitted. The control unit 21 of the user terminal 20 and the control unit 31 of the entrance management server 30 in the present embodiment perform the same processing as steps S31 to S33 shown in FIG. 10. Next, the control unit 31 of the entrance management server 30 acquires biometric information of a user carrying the user terminal 20 (a user who is proceeding through the entrance passage) by the biometric information acquisition unit 39 (S71).

[0075] Based on the acquired biometric information of the user, the control unit 31 determines whether or not the participation conditions or entrance conditions regarding the biometric information are satisfied (S72). The conditions here are that the body temperature, respiratory rate, heart rate, etc. are within a predetermined range, and are stored in the storage unit 32 in advance. For example, the participation conditions or entrance conditions are used such as the body temperature being less than 37.5 degrees, the respiratory rate being 10 to 20 times per minute, and the heart rate being 50 to 100 times per minute. Also, for example, conditions regarding various test items that can be inspected from exhalation, such as wearing a mask and the alcohol concentration in exhaled breath, may be used. Furthermore, if the biometric information acquisition unit 39 can also acquire the age or gender of the user, the participation conditions or entrance conditions may be registered for each age group or gender.

[0076] When it is determined that the user's biometric information satisfies the conditions (S72: YES), the control unit 31 proceeds to the process of step S34, and the admission management server 30 and the server 10 perform the processes after step S34. When it is determined that the user's biometric information does not satisfy the conditions (S72: NO), the control unit 31 closes the gate 38a by the gate opening / closing unit 38 (S73) and performs a notification process by the notification unit 37 (S74). As a result, when the biometric information at the time of passing through the access passage acquired from the user does not satisfy the participation conditions or the admission conditions, the admission management server 30 can reject the participation in the event or the entry into the facility, and can notify the user that the participation or entry has been rejected. At this time, when notifying that the participation or entry has been rejected based on the biometric information of the user at the time of passing through the access passage, the poor physical condition of the user can be notified to the user and the staff of the event, etc.

[0077] By the above-described process, in the information processing system 100 of the present embodiment, when a user participates in an event or enters a facility, in addition to the inspection result of the user registered in the server 10, based on the biometric information of the user at the time of passing through the access passage, it is determined whether participation or entry is permitted. Since there is a time lag between the inspection implementation date and the time of passing through the access passage for each inspection result registered in the server 10, there is a possibility that the state of the user at the time of passing through the access passage is not accurately indicated. Therefore, it is possible to perform a more accurate determination by combining the result of the previously performed inspection and the biometric information acquired at the time of participating in the event or entering the facility. As a result, it is possible to perform a participation restriction or an entry restriction that more accurately determines the state of the user.

[0078] In this embodiment, the same effects as those of the above-described embodiments can be obtained. Also, in this embodiment, based on the result of an inspection conducted before participating in an event or entering a facility and the biometric information at the time of participating in the event or entering the facility, it is determined whether the user is allowed to participate or enter, so that participation restrictions or entry restrictions can be performed more accurately. Also in this embodiment, the application of the modification examples appropriately described in the above-described embodiments is possible. Further, the configuration of this embodiment can also be applied to the information processing system 100 of Embodiment 2-3, and the same effects can be obtained even when applied to the information processing system 100 of Embodiment 2-3.

[0079] (Embodiment 5) An information processing system including a gate device 30a provided at the boarding gate of an airline will be described. Since the information processing system 100 of this embodiment can be realized by the same devices as the information processing system 100 of Embodiment 1, a detailed description of the configuration will be omitted. Note that the admission management server 30 of this embodiment stores a ticket DB 32a in the storage unit 32 in addition to the configuration of Embodiment 1 shown in FIG. 5. FIG. 19 is a schematic diagram showing a configuration example of the ticket DB 32a. The ticket DB 32a is a conversion table that stores the ticket information of an airplane boarding ticket issued by an airline in association with the user ID of the user who purchased this boarding ticket. As the ticket information, for example, data (e.g., boarding ID) included in a code described on an airplane boarding ticket (boarding pass) can be used. Note that each piece of information regarding the boarding ticket and each piece of information regarding the user who purchased the boarding ticket may be stored in the ticket DB 32a. The ticket DB 32a may be stored in another storage device connected to the admission management server 30, or may be stored in another storage device that can communicate with the admission management server 30 via the network N.

[0080] In the information processing system 100 of the present embodiment, each device executes the same processing as the processing shown in FIG. 6. In the present embodiment, facility information regarding the airport facility is input via the registration terminal 40 and registered in the server 10. Further, in the present embodiment, the gate device 30a installed at the boarding gate of the airline company is made to read the code (for example, QR code) of the boarding ticket of the airplane issued by the airline company. The code of the boarding ticket may be printed on the ticket paper or may be displayed on the user terminal 20. The admission management server 30 of the present embodiment stores, in the ticket DB 32a, the ticket information of the boarding ticket purchased by each user in association with the user ID registered in the server 10. Therefore, the admission management server 30 can convert the ticket information acquired by reading the code of the boarding ticket into the corresponding user ID. Therefore, in the present embodiment, the user does not need to acquire the code issued by the server 10 using the user terminal 20. That is, in the present embodiment, instead of the code issued by the server 10, the code of the boarding ticket of the airplane issued by the airline company is used, so each device does not need to execute the processing of FIG. 8.

[0081] FIG. 20 is a flowchart showing an example of the determination processing procedure of Embodiment 5. The processing shown in FIG. 20 is obtained by adding steps S81 to S86 instead of steps S31 to S33 in the processing shown in FIG. 10. Explanation of the same steps as in FIGS. 10 and 11 is omitted. In FIG. 20, the illustration of steps S36 to S51 in FIGS. 10 and 11 is omitted. The control unit 31 of the admission management server 30 of the present embodiment reads the code of the boarding ticket issued by the airline company by the code reader 36 (S81) and acquires the ticket information included in the code (S82).

[0082] Based on the acquired ticket information, the control unit 31 determines whether boarding the airplane is possible (whether the ticket is valid) (S83). For example, the ticket information of valid tickets is stored in the storage unit 32 of the admission management server 30, and the control unit 31 determines whether the ticket is valid according to whether the ticket information read from the code is stored in the storage unit 32. If it is determined that the ticket is valid (S83: YES), the control unit 31 converts this ticket information into a user ID corresponding to the ticket information (S86). Specifically, the control unit 31 reads out the user ID registered in the ticket DB 32a in association with this ticket information. Then, the control unit 31 transmits the converted user ID and the event ID or facility ID (here, the facility ID corresponding to the airline or boarding gate of the airport) to the server 10 (S34), and requests the server 10 to determine whether to allow this user to enter (whether to allow boarding the airplane). The control unit 11 of the server 10 performs the processing after step S35. Thereby, the control unit 11 of the server 10 determines whether to allow this user to board the airplane based on the user ID received from the admission management server 30, and outputs the determination result (permission information or rejection information) to the admission management server 30 that read the ticket information before conversion.

[0083] If it is determined that the ticket is not valid (S83: NO), the control unit 31 closes the gate 38a by the gate opening / closing unit 38 (S84), and notifies that boarding the airplane has been rejected by the notification process of the notification unit 37 (S85). Note that the control unit 31 may notify that boarding cannot be done because the boarding ticket is not valid. By the above-described processing, the admission management server 30 of the present embodiment can identify the user ID registered in the server 10 from the boarding ticket code of the airplane carried by the user by reading the code of the boarding ticket. Therefore, since the user only needs to present the boarding ticket code when boarding the airplane, the management of the code becomes easy.

[0084] In this embodiment, the process of converting ticket information into a user ID corresponding to the ticket information is not limited to the configuration performed by the admission management server 30. For example, the ticket DB 32a may be stored in another device, and the control unit 31 of the admission management server 30 may transmit the ticket information read by the code reader 36 to another device and obtain the user ID converted by the other device. Also, the server 10 may store the ticket DB 32a and perform the process of converting the ticket information into a user ID. In this case, the admission management server 30 transmits the ticket information read by the code reader 36 to the server 10, and the server 10 converts the received ticket information into a user ID based on the ticket DB 32a, and may perform the determination process of whether the user is allowed to participate or enter based on the converted user ID.

[0085] In this embodiment, the same effects as those of the above-described embodiments can be obtained. Also, in this embodiment, since the server 10 can be made to determine whether boarding is permitted based only on the code of the airplane boarding ticket, the convenience for the user is improved. Also in this embodiment, the application of the modification examples appropriately described in the above-described embodiments is possible. Further, the configuration of this embodiment can also be applied to the information processing system 100 of Embodiments 2-4, and the same effects can be obtained even when applied to the information processing system 100 of Embodiments 2-4.

[0086] (Embodiment 6) An information processing system will be described in which, when the server 10 issues a code in response to a request from the user terminal 20, in addition to the identification information of the user, a code including information on the ticket necessary for participating in the event or entering the facility is generated. Since the information processing system 100 of this embodiment can be realized by the same devices as the information processing system 100 of Embodiment 1, a detailed description of the configuration will be omitted. In the information processing system 100 of this embodiment, each device executes the same processing as the processing shown in FIG. 6. As a result, also in this embodiment, the event information or facility information input via the registration terminal 40 is registered in the server 10.

[0087] FIG. 21 is a flowchart showing an example of the code issuance processing procedure according to Embodiment 6, and FIG. 22 is a schematic diagram showing an example of a screen. The processing shown in FIG. 21 adds steps S91 to S93 between steps S22 and S23 in the processing shown in FIG. 8, and adds steps S94 to S95 instead of step S26. Explanation of the same steps as in FIG. 8 is omitted. The control unit 21 of the user terminal 20 in the present embodiment performs the same processing as steps S21 to S22 shown in FIG. 8. In the present embodiment, when the control unit 21 determines that the code issuance button has been operated on the initial screen (S22: YES), it displays on the display unit 25 an input screen for inputting the event ID of the event in which the user participates or the facility ID of the facility where the user enters (S91). FIG. 22 shows an example of an input screen. The input screen has an input field for the event ID or facility ID, an OK button for instructing code issuance based on the input event ID or facility ID, and a return button for returning to the display of the initial screen. The user inputs the event ID of the event they want to participate in or the facility ID of the facility they entered in the input field and operates the OK button. Note that the event ID or facility ID is an ID issued by the server 10 when event information or facility information is registered in the server 10, and the user obtains it from, for example, the event organizer or the person in charge of the facility.

[0088] The control unit 21 receives the input of the event ID or facility ID for the input field in the input screen via the input unit 24 (S92), and displays the received event ID or facility ID in the input field. Then, the control unit 21 determines whether the OK button on the input screen has been operated (S93). If it determines that the button has been operated (S93: YES), it proceeds to the processing of step S23 and requests the server 10 to issue a code (S23). Note that in the present embodiment, the control unit 21 transmits the user ID of the user and the event ID or facility ID obtained in step S92 to the server 10 to request code issuance. If it determines that the OK button has not been operated (S93: NO), that is, if the return button on the input screen has been operated, the control unit 21 returns to the processing of step S21. Specifically, the control unit 21 ends the display of the input screen and redisplay the initial screen.

[0089] When the control unit 11 of the server 10 determines in step S25 that the user has been authenticated (S25: YES), it acquires ticket information of a ticket necessary to participate in this event or a ticket necessary to enter the facility based on the event ID or facility ID received from the user terminal 20 (S94). The ticket information is, for example, received by the server 10 from the registration terminal 40 when event information or facility information is registered, and registered in the event DB 12b or the facility DB 12c. Then, the control unit 11 generates a code including the user ID received from the user terminal 20 and the ticket information acquired in step S94 (S95), and transmits the generated code to the user terminal 20 (S27). By the above-described processing, also in the present embodiment, the code requested via the user terminal 20 is issued by the server 10 and provided to the user terminal 20. Note that, in the present embodiment, the code provided from the server 10 includes not only the identification information (user ID) of the user, but also the ticket information necessary when the user participates in the event or the ticket information necessary when the user enters the facility. Therefore, the user can present the user ID and the ticket information with one code, which facilitates the handling of the code.

[0090] FIG. 23 is a flowchart showing an example of the determination processing procedure of Embodiment 6. The processing shown in FIG. 23 is obtained by adding steps S101 to S104 instead of step S33 in the processing shown in FIG. 10. Description of the same steps as those in FIGS. 10 and 11 is omitted. Note that, in FIG. 23, illustration of steps S36 to S51 in FIGS. 10 and 11 is omitted. The control unit 21 of the user terminal 20 and the control unit 31 of the entrance management server 30 in the present embodiment perform the same processing as steps S31 to S32 shown in FIG. 10. When the control unit 31 of the entrance management server 30 in the present embodiment reads the code, it acquires the user ID and the ticket information included in the code (S101).

[0091] Based on the acquired ticket information, the control unit 31 determines whether it is possible to participate in the event or enter the facility (whether the ticket is valid) (S102). If it is determined that the ticket is valid (S102: YES), the control unit 31 proceeds to the process of step S34, transmits the user ID read from the code and the event ID or facility ID to the server 10 (S34), and requests the server 10 to determine whether to permit the user to participate or enter.

[0092] If it is determined that the ticket is not valid (S102: NO), the control unit 31 closes the gate 38a by the gate opening / closing unit 38 (S103) and performs a notification process by the notification unit 37 (S104). Through the above-described process, in this embodiment, the admission management server 30 can acquire the user ID used when requesting the server 10 to determine whether to permit the user to participate or enter, and the ticket information, by reading the code displayed on the user terminal 20. Therefore, when the user participates in the event or enters the facility, the user only needs to present one code, which facilitates the management of the code.

[0093] In this embodiment, the code including the user ID and ticket information may be issued not only by the server 10 but also by a terminal on the side of the event organizer or a terminal on the side of the ticket issuer, etc. In this case, the terminal that issues the code may acquire the user ID of each user from the server 10, generate a code including the acquired user ID and the ticket information of each user, and provide it to the user terminal 20 of each user.

[0094] In this embodiment, the same effects as those of the above-described embodiments are obtained. Also, in this embodiment, since the user ID and ticket information can be presented with one code, the convenience of the user is improved. In this embodiment as well, the application of the modification examples appropriately described in the above-described embodiments is possible. Further, the configuration of this embodiment can also be applied to the information processing system 100 of Embodiments 2-5, and the same effects can be obtained even when applied to the information processing system 100 of Embodiments 2-5.

[0095] (Embodiment 7) When the server 10 issues a code in response to a request from the user terminal 20, an information processing system that generates a code including information on the user's inspection results in addition to the user's identification information (user ID) will be described. Since the information processing system 100 of this embodiment can be realized by the same devices as the information processing system 100 of Embodiment 1, detailed description of the configuration will be omitted. In the information processing system 100 of this embodiment, each device executes the same processing as the processing shown in FIG. 6. As a result, also in this embodiment, the event information or facility information input via the registration terminal 40 is registered in the server 10.

[0096] FIG. 24 is a flowchart showing an example of the code issuance processing procedure of Embodiment 7. The processing shown in FIG. 24 is obtained by adding steps S111 to S113 between steps S22 and S23 in the processing shown in FIG. 8, and adding steps S114 to S116 instead of step S26. Explanation of the same steps as in FIG. 8 will be omitted. The control unit 21 of the user terminal 20 in this embodiment performs the same processing as steps S21 to S22 and S91 to S93 shown in FIG. 21 (S21 to S22, S111 to S113), similar to Embodiment 6. Therefore, also in this embodiment, the user terminal 20 transmits the user ID of the user and the event ID or facility ID acquired via the input screen to the server 10 to request the issuance of a code.

[0097] When the control unit 11 of the server 10 determines that the user can be authenticated in step S25 (S25: YES), based on the event ID or facility ID received from the user terminal 20, it acquires the participation conditions set for this event from the event DB 12b, or acquires the admission conditions set for this facility from the facility DB 12c (S114). Next, the control unit 11 reads out the inspection results of the user with the received user ID for the inspection items corresponding to the read participation conditions or admission conditions from the user DB 12a (S115). Then, the control unit 11 generates a code including the user ID and the inspection results of the user read in step S115 (S116), and transmits the generated code to the user terminal 20 (S27).

[0098] Through the above-described processing, also in the present embodiment, the code requested via the user terminal 20 is issued by the server 10 and provided to the user terminal 20. In the present embodiment, the code provided from the server 10 includes not only the user ID but also information on the inspection results used when determining whether the user is permitted to participate in an event or enter a facility. Therefore, the user can obtain from the server 10 a code including the inspection results of the inspection items according to the participation conditions set for the event the user wishes to participate in or the entry conditions set for the facility the user wishes to enter.

[0099] FIG. 25 is a flowchart showing an example of the determination processing procedure of Embodiment 7. In FIG. 25, the processing performed by the user terminal 20 is shown on the left side, and the processing performed by the entry management server 30 is shown on the right side. The following processing is realized by the control unit 21 according to the control program 22P stored in the storage unit 22 of the user terminal 20, and is realized by the control unit 31 according to the control program 32P stored in the storage unit 32 of the entry management server 30. A part of the following processing may be realized by a dedicated hardware circuit.

[0100] Also in the information processing system 100 of the present embodiment, when the control unit 21 of the user terminal 20 receives an execution instruction of the PHR application 22AP and a display instruction of a code, the control unit 21 starts the PHR application 22AP and displays the code on the display unit 25 (S121). Then, the user causes the code displayed on the user terminal 20 to be read by the code reader 36 of the gate device 30a. The control unit 31 of the entry management server 30 reads the code with the code reader 36 (S122) and acquires the user ID and the inspection results included in the code (S123). At this time, the control unit 31 may be configured to acquire the user ID included in the code, request the server 10 for user authentication based on the user ID, and perform the processing after step S124 when the user is authenticated.

[0101] Next, the control unit 31 determines whether the user ID read from the code has already been registered (stored) in the storage unit 32 as the user ID of an authorized user (S124). In the present embodiment, since the control unit 31 has already registered the user IDs of the users whose participation or entry has been permitted in the storage unit 32 (a database not shown), it is possible to determine whether the user is an already permitted user according to whether the user ID is registered in the storage unit 32. In addition, the control unit 31 may transmit the event ID or facility ID and the user ID to the server 10, and determine whether the server 10 has already registered them as the user IDs of authorized users in the determination result DB12d stored in the server 10.

[0102] If it is determined that the user is not an authorized user (S124: NO), the control unit 31 determines whether the inspection result read from the code satisfies the participation conditions or entry conditions set for the event or facility that the entry management server 30 manages for participation or entry (S125). The participation conditions or entry conditions are stored in advance in the storage unit 32 of the entry management server 30. If it is determined that the inspection result read from the code satisfies the participation conditions or entry conditions (S125: YES), the control unit 31 opens the gate 38a by the gate opening / closing unit 38 (S126). Then, the control unit 31 registers the user ID of the user whose participation or entry has been permitted in the storage unit 32 as the user ID of an authorized user (S127).

[0103] When it is determined that the user is an authorized user (S124: YES), or when it is determined that the inspection result does not meet the conditions (S125: NO), the control unit 31 closes the gate 38a by the gate opening / closing unit 38 (S128), and notifies the reason for rejecting participation or entry through the notification process by the notification unit 37 (S129). Note that when the control unit 31 determines that the user is an authorized user, it notifies that the user has already entered, and when it determines that the inspection result does not meet the conditions, it notifies the reason for not meeting the participation conditions or entry conditions. For example, it notifies that the inspection result of the user is not the inspection result set in the conditions, that the user has not undergone the inspection of the inspection items set in the conditions, that the expiration date for the inspection result of the user has passed, and the like. By the above-described processing, in the present embodiment, the entrance management server 30 can acquire the inspection result of the user by reading the code displayed on the user terminal 20, and can determine whether to permit the user to participate or enter based on the acquired inspection result. Also in this case, based on the information on the inspection result of the user registered in the server 10, it is possible to determine whether to permit participation in the event or entry into the facility.

[0104] In the present embodiment, the configuration is not limited to the case where the participation conditions for the event or the entry conditions for the facility are registered in advance in the server 10 (event DB 12b or facility DB 12c). For example, a configuration may be adopted in which the organizer of the event or the person in charge of the facility notifies the participation conditions or the entry conditions to the user, and the user notifies the participation conditions or the entry conditions to the server 10 when requesting the server 10 to issue a code. Even in such a configuration, the server 10 can generate a code including the inspection result of the user corresponding to the participation conditions or the entry conditions set for each event or facility and provide it to the user terminal 20.

[0105] In this embodiment, the same effects as those of the above-described embodiments can be obtained. Also, in this embodiment, since the determination of whether to permit participation in an event or entry into a facility is executed by the admission management server 30 alone, there is no need for the admission management server 30 to communicate with the server 10, and the processing time can be shortened. Also in this embodiment, the application of the modification examples appropriately described in the above-described embodiments is possible. Further, the configuration of this embodiment can also be applied to the information processing system 100 of Embodiments 2-6, and the same effects can be obtained even when applied to the information processing system 100 of Embodiments 2-6. Note that when the configuration of this embodiment is applied to the information processing system 100 of Embodiment 6, the server 10 generates a code including information on the inspection result of the user, the user ID, and ticket information and provides it to the user terminal 20. Also, when the configuration of this embodiment is applied to the information processing system 100 of Embodiment 4, the participation restriction or entry restriction of the user can be performed based not only on the inspection result included in the code but also on the biometric information at the time of participating in the event or entering the facility.

[0106] In addition, in this embodiment, an information processing system that generates a code including information on the test results of a user in addition to the identification information (user ID) of the user has been described. However, the present invention is not limited to this. Instead of or in addition to the information on the test results of the user, a mode of generating a code including vaccination history information may be adopted. The code issuance procedure can be issued by a process similar to the procedure described with reference to FIGS. 8 and 9A to 9C. In this case, on the screen of FIG. 9A, a configuration may be adopted in which a vaccination history confirmation button is displayed, and on a selection screen such as FIG. 9B, a configuration may be adopted in which a specific vaccine type can be selected from a list of a plurality of vaccines to issue a code. Further, on the screen of FIG. 9C, in addition to the code, a vaccination history in character information and various information on an infectious disease test result, a user name, and a date of birth may be displayed side by side. At that time, the code includes not only the user ID but also information on the vaccination history specified by the user and, optionally, an infectious disease test result. By having this code read by the entrance management server 30 in which the passing conditions are stored in advance, smooth passage at the passing point becomes possible. In addition, since the vaccination history information in characters is displayed on the display screen, it becomes possible for the supervisor to visually confirm the passing conditions at the passing point.

[0107] (Embodiment 8) When a user enters a store facility such as a restaurant, the entrance management server 30 performs an entrance restriction based on the inspection results of the user registered in the server 10 and collects information on the user's allergic diseases. An information processing system will be described. Note that in the information processing system of this embodiment, a configuration may be adopted in which only the process of collecting information on the user's allergic diseases is performed when the user enters the store. Since the information processing system 100 of this embodiment can be realized by the same devices as the information processing system 100 of Embodiment 1, detailed description of the configuration will be omitted. Note that the entrance management server 30 of this embodiment may use the entrance management system of Embodiment 2 shown in FIGS. 12A and 12B. For example, a code reader 36 is installed at the entrance of the store. Also, the facility DB 12c stored in the storage unit 12 of the server 10 of this embodiment is slightly different from the configuration of Embodiment 1 shown in FIG. 4B.

[0108] FIG. 26 is a schematic diagram showing a configuration example of the facility DB 12c of Embodiment 8. The facility DB 12c of this embodiment further has a collection target column in the configuration of Embodiment 1 shown in FIG. 4B. The collection target column stores the items (allergens) of the allergy test to be collected when each user enters (enters the store) the facility. The items to be collected are stored by the control unit 11 when the control unit 11 acquires each piece of information via the communication unit 13 or the input unit 14, and are changed by the control unit 11 when a change instruction is acquired. Note that the event DB 12b of this embodiment may also have a configuration having a collection target column.

[0109] In the information processing system 100 of the present embodiment, each device executes the same processing as the processing shown in FIG. 6. As a result, also in the present embodiment, the event information or facility information input via the registration terminal 40 is registered in the server 10. In the present embodiment, the registration terminal 40 receives event information or facility information via the registration screen shown in FIG. 27, transmits the received event information or facility information to the server 10, and registers it in the server 10. FIG. 27 is a schematic diagram showing an example of a registration screen. The registration screen shown in FIG. 27 has the same configuration as the registration screen shown in FIG. 7, and further has an input field for inspection items for which inspection results should be collected at the time of entry (at the time of store entry). In the screen shown in FIG. 27, as a condition for imposing an entry restriction, a check box for selecting inspection results for inspection items for infectious diseases is provided, and as an inspection item for which inspection results should be collected at the time of entry, a check box for selecting allergens (inspection items) for allergy inspection is provided. However, it is not limited to such a configuration.

[0110] Also, in the information processing system 100 of the present embodiment, each device executes the same processing as the processing shown in FIG. 8. As a result, also in the present embodiment, the code requested via the user terminal 20 is issued by the server 10 and provided to the user terminal 20.

[0111] FIG. 28 is a flowchart showing an example of the determination processing procedure of Embodiment 8. The processing shown in FIG. 28 is obtained by adding steps S131 to S133 instead of step S45 in the processing shown in FIG. 11, adding step S134 instead of step S49, and adding step S135 instead of steps S50 to S51. Explanation of the same steps as in FIGS. 10 and 11 is omitted. In FIG. 28, the illustration of steps S31 to S44 in FIG. 10 is omitted.

[0112] The control unit 21 of the user terminal 20, the control unit 31 of the admission management server 30, and the control unit 11 of the server 10 perform the same processing as steps S31 to S44 shown in FIG. 10. When the control unit 11 of the server 10 determines in step S40 that the inspection result of the user satisfies the conditions obtained in step S38 (S40: YES), it acquires the inspection items (collection targets) to be collected at the time of admission for this event or facility (S131). Specifically, when the control unit 11 has received the facility ID, it reads out the collection target corresponding to the facility ID from the facility DB 12c. In addition, when the collection target is also registered in the event DB 12b for the event ID, the control unit 11 may read out the collection target corresponding to the event ID from the event DB 12b.

[0113] Then, the control unit 11 reads out the inspection result of the authenticated user from the user DB 12a for the inspection items corresponding to the read collection target (S132). For example, when the control unit 11 has read out "milk allergy test" as the collection target, it reads out the milk allergy test result of the authenticated user from the allergy test results stored in the user DB 12a. Then, the control unit 11 transmits the permission information indicating the admission permission of this user and the read allergy test result of the user to the admission management server 30 (S133).

[0114] When the control unit 31 of the admission management server 30 determines that it has received the permission information from the server 10 (S48: YES), it notifies the notification unit 37 or the display unit 35 that the admission (entry into the store) is permitted and the allergy test result for this user (S134). On the other hand, when it determines that it has not received the permission information from the server 10 (S48: NO), the control unit 31 notifies the notification unit 37 or the display unit 35 that the admission (entry into the store) has been rejected (S135). Thereby, the admission management server 30 can determine whether to permit the user to enter based on the inspection results registered in the server 10 when the user enters, and can acquire the allergy test results of the user from the server 10.

[0115] The configuration of this embodiment is used not only in the information processing system 100 that uses the gate device 30a installed at the entrance of a store facility such as a restaurant, but also in, for example, the information processing system 100 that uses the gate device 30a installed at the boarding gate of an airport. In this case, when a user passes through the boarding gate of the airport and boards an airplane, it is possible to determine whether the user is allowed to board based on the inspection results registered in the server 10, and it is also possible to obtain the results of the user's allergy test. Therefore, when providing food containing allergens in in-flight meals, by using the results of the allergy tests of each user, it is possible to provide safe in-flight meals.

[0116] In this embodiment, the same effects as those of the above-described embodiments can be obtained. Also, in this embodiment, when entering a facility (entering a store), not only is it determined whether entry is permitted, but the results of the user's allergy test can also be collected. Therefore, in a store that provides products containing allergens of food allergies, such as a restaurant, by collecting the results of the user's allergy test at the time of entry, it is possible to provide products that take allergies into consideration. In this embodiment as well, the application of the modification examples appropriately described in the above-described embodiments is possible. Also, the configuration of this embodiment can be applied to the information processing system 100 of Embodiments 2-7, and the same effects can be obtained even when applied to the information processing system 100 of Embodiments 2-7.

[0117] (Embodiment 9) An information processing system that charges based on the number of inspection items used to determine whether to allow participation or entry for each event or facility, or based on the number of users for whom it has been determined whether to allow participation or entry will be described. Since the information processing system 100 of this embodiment can be realized by the same devices as the information processing system 100 of Embodiment 1, a detailed description of the configuration will be omitted.

[0118] In the information processing system 100 of the present embodiment, each device executes the same processes as those shown in the processes of FIG. 6 and FIG. 8. As a result, also in the present embodiment, the event information input via the registration terminal 40 is registered in the server 10, and the code requested via the user terminal 20 is issued by the server 10 and provided to the user terminal 20. Further, each device executes the same processes as those shown in the processes of FIGS. 10 and 11. As a result, when the user passes through the entrance passage of the gate device 30a, it is determined whether to participate in the event or enter the facility based on the inspection result of the user registered in the server 10.

[0119] The server 10 of the present embodiment executes the calculation process of the usage fee for each event or facility while executing each process described in Embodiment 1. FIG. 29 is a flowchart showing an example of the procedure for calculating the usage fee, and FIG. 30 is a schematic diagram showing an example of a screen. The following processes are realized by the control unit 11 according to the control program 12P stored in the storage unit 12 of the server 10. A part of the following processes may be realized by a dedicated hardware circuit.

[0120] In the information processing system 100 of the present embodiment, when the execution timing of the usage fee calculation process arrives, the control unit 11 of the server 10 reads out the participation conditions or admission conditions for one event or facility from the event DB 12b or the facility DB 12c (S141). The calculation timing of the usage fee can be, for example, after the end of the event, after the elapse of a predetermined period, etc. The control unit 11 counts the number of inspection items included in the read participation conditions or admission conditions (S142). Note that the number of inspection items included in the participation conditions or admission conditions is the number of inspection items (desired inspection items) used when performing participation restrictions or admission restrictions. The control unit 11 of the server 10 receives event information or facility information from the registration terminal 40 and registers it in the event DB 12b or the facility DB 12c. Therefore, the control unit 11 acquires the desired inspection items that the admission management system hopes to use when performing participation restrictions or admission restrictions, in association with each event or facility. Note that the number of inspection items included in each participation condition or admission condition may be registered in the event DB 12b or the facility DB 12c in association with the event ID or the facility ID. In this case, the control unit 11 may read out the number of inspection items from the event DB 12b or the facility DB 12c.

[0121] Next, the control unit 11 counts the total number of users (the number of users using the inspection results) who have been permitted and the number of users who have been rejected and registered in the determination result DB 12d for this event or facility (S143). Note that the determination result DB 12d may store the number of users who have been permitted, the number of users who have been rejected, or the total number of users using the inspection results, in association with the event ID or the facility ID. When the number of users who have been permitted and the number of users who have been rejected are stored, the control unit 11 reads out the number of each user from the determination result DB 12d and calculates the total number of users. Also, when the total number of users is stored, the control unit 11 may read out the total number of users from the determination result DB 12d.

[0122] Then, the control unit 11 calculates the usage fee for this event or facility based on the number of inspection items or the number of users who use the inspection results (S144). For example, a fee for one inspection item may be set, a fee for one user may be set, or a fee for one user for each inspection item may be set. The control unit 11 stores the calculated usage fee in the storage unit 12 in association with the event ID or facility ID. Next, the control unit 11 generates a notification screen for the calculated usage fee (S145), and transmits the generated notification screen to the terminal of the event organizer or the person in charge of the facility (S146).

[0123] FIG. 30 shows an example of a notification screen. The notification screen displays the event name or facility name, the usage period, the inspection items used for determining whether to allow participation in the event or entry into the facility, the unit price per user set for each inspection item, the number of users who used the inspection results of each inspection item, the usage fee for each inspection item, and the total amount of the usage fee (the amount to be billed), etc. By transmitting such a notification screen to the event organizer or the person in charge of the facility, it is possible to notify the usage amount due to the use of the server 10 for restricting participation in the event or restricting entry into the facility.

[0124] The control unit 11 determines whether the calculation process has been completed for all events and facilities for which the usage fee should be calculated (S147). If it is determined that the process has not been completed (S147: NO), the process returns to the process of step S141, and the processes of steps S141 to S146 are performed for the unprocessed events and facilities. If it is determined that the calculation process has been completed for all events and facilities (S147: YES), the control unit 11 ends the process. By the above-described process, in the information processing system 100 of the present embodiment, when a user participates in an event or enters a facility, it is possible to determine whether to allow participation or entry and perform participation restriction or entry restriction, and it is possible to calculate the amount (usage fee) to be charged for the participation or entry permission determination process.

[0125] In this embodiment, the same effects as those of the above-described embodiments can be obtained. Further, in this embodiment, when restricting participation in an event or entry into a facility, it is possible to calculate and notify a usage fee for the permission / denial determination process for participation or entry based on the inspection results of the users registered in the server 10. Also in this embodiment, the application of the modification examples appropriately described in the above-described embodiments is possible. Further, the configuration of this embodiment can also be applied to the information processing system 100 of Embodiments 2-8, and the same effects can be obtained even when applied to the information processing system 100 of Embodiments 2-8.

[0126] (Embodiment 10) An information processing system that guides a user to different guiding destinations according to the result of permission / denial determination of the user's participation or entry, which is performed based on the inspection results of the users registered in the server 10 when the user participates in an event or enters a facility, will be described. Since the information processing system 100 of this embodiment can be realized by the same devices as the information processing system 100 of Embodiment 1, a detailed description of the configuration will be omitted. In this embodiment, in addition to the configuration of Embodiment 1 shown in FIG. 5, the entrance management server 30 stores a guidance content DB 32b in the storage unit 32.

[0127] FIG. 31 is a schematic diagram showing a configuration example of the guidance content DB 32b. The guidance content DB 32b stores information regarding a guidance destination according to the result of a permission / denial determination of participation or entry based on the inspection results of users participating in an event or users entering a facility. The guidance content DB 32b shown in FIG. 31 includes a guidance destination ID column, a guidance destination column, a guidance condition column, an additional item column, and the like. The guidance destination ID column stores identification information (guidance destination ID) assigned to each guidance destination. The guidance destination column, the guidance condition column, and the additional item column respectively store information indicating the guidance destination, such as a gate number, in association with the guidance destination ID, conditions for guiding a user to each guidance destination, and information regarding additional inspections to be performed for each guidance destination. Examples of the guidance conditions include cases where the result of the permission / denial determination of participation or entry for a user does not satisfy the conditions for all inspection items, does not satisfy the conditions for some inspection items, or the expiration date of the inspection items has passed. Note that, as the guidance conditions, for example, cases where the result of a PCR test for the novel coronavirus is positive, the result of an antibody test for the novel coronavirus is negative, the novel coronavirus vaccine (first or second dose) has not been administered, or a predetermined period has passed since the novel coronavirus vaccination may be used. Examples of the additional items include measurement of biological information such as body temperature, respiratory rate, and heart rate, inspection of various inspection items detectable from exhalation, confirmation of mask wearing, and finger alcohol disinfection. The guidance destination ID stored in the guidance content DB 32b is issued and stored by the control unit 31 when each guidance destination is registered. Other information stored in the guidance content DB 32b is stored by the control unit 31 when the control unit 31 acquires each piece of information of the guidance destination via an input unit (not shown), and is changed by the control unit 31 when a change instruction is acquired. The stored content of the guidance content DB 32b is not limited to the example shown in FIG. 31, and various types of information regarding the guidance destination may be stored. Further, the guidance content DB 32b may be created by another terminal such as a terminal of an event organizer or a terminal of a facility staff member. In this case, the entrance management server 30 may acquire the guidance content DB 32b from another terminal via the network N and store it in the storage unit 32.

[0128] In the information processing system 100 of the present embodiment, each device executes the same processing as that shown in the processing of FIG. 6 and the processing of FIG. 8. Thus, also in the present embodiment, the event information input via the registration terminal 40 is registered in the server 10, and the code requested via the user terminal 20 is issued by the server 10 and provided to the user terminal 20.

[0129] FIGS. 32 and 33 are flowcharts showing an example of the determination processing procedure of Embodiment 10. The processing shown in FIGS. 32 and 33 is a modification of a part of steps S41 to S51 in the processing shown in FIGS. 10 and 11. The description of the same steps as those in FIGS. 10 and 11 is omitted. The control unit 21 of the user terminal 20, the control unit 31 of the entrance management server 30, and the control unit 11 of the server 10 in the present embodiment perform the same processing as steps S31 to S40 shown in FIG. 10.

[0130] When the control unit 11 determines in step S40 that the inspection result of the user satisfies the participation condition or the entrance condition (S40: YES), the control unit 11 transmits permission information indicating the participation permission or the entrance permission of this user to the entrance management server 30 (S45), and associates the user ID of this user with the event ID or the facility ID and registers it in the permitted user column of the determination result DB12d (S46). When the control unit 31 of the entrance management server 30 receives the permission information from the server 10, the control unit 31 opens the gate 38a by the gate opening / closing unit 38 (S151). At this time, the control unit 31 may perform a notification process of notifying by the notification unit 37 that participation in the event or entry into the facility is permitted.

[0131] On the other hand, when it is determined that the inspection result of the user does not satisfy the participation condition or the entrance condition (S40: NO), the control unit 11 transmits rejection information indicating the rejection of participation or entry of this user, the reason for rejection, and the inspection results of the inspection items that are the reasons for rejection to the entrance management server 30 (S152). Then, the control unit 11 associates the user ID of the user who has been rejected from participation or entry with the event ID or the facility ID and registers it in the rejected user column of the determination result DB12d (S42).

[0132] When the control unit 31 of the entrance management server 30 receives the rejection information from the server 10, it determines whether the reason for rejection is that there are inspection items that do not meet the participation conditions or the entrance conditions (S153). If it is determined that there are inspection items that do not meet the participation conditions or the entrance conditions (S153: YES), the control unit 31 identifies a guiding destination corresponding to the inspection items that do not meet the participation conditions or the entrance conditions (S154). For example, the control unit 31 identifies the gate of the guiding destination corresponding to the reason for rejection and the inspection result of the user based on the registration content of the guidance content DB 32b. For example, when all the inspection items included in the participation conditions or the entrance conditions are not met, the control unit 31 identifies the first gate as the guiding destination for this user. Further, the control unit 31 may, for example, identify a guiding destination according to the inspection result of a predetermined inspection item, or may, for example, identify a predetermined gate as the guiding destination for a user whose antigen test result for the novel coronavirus is negative.

[0133] If it is determined that there is no inspection item for which the rejection reason fails to meet the participation conditions or entry conditions (S153: NO), for example, if the rejection reason is that the user has not undergone the inspection of the inspection item set for the participation conditions or entry conditions, or if the rejection reason is that the expiration date for the user's inspection result has passed, the control unit 31 identifies a guidance destination according to the rejection reason (S156). For example, the control unit 31 identifies the gate of the guidance destination corresponding to the rejection reason based on the registered content of the guidance content DB 32b. For example, when the expiration date of the user's inspection result has passed, the control unit 31 identifies the third gate as the guidance destination for this user. Then, the control unit 31 notifies the rejection reason through the notification process by the notification unit 37 and guides the user to the identified guidance destination (S155). For example, the control unit 31 displays a message such as "Please go to the first gate" on the display unit 35 to guide the user to move to the first gate. At this time, the control unit 31 may open the gate 38a by the gate opening / closing unit 38 to guide the user to the guidance destination. Thereby, when the user participates in the event or enters the facility, the entry management server 30 can not only impose participation restrictions or entry restrictions, but also guide the user to different guidance destinations according to the user's inspection result or the result of the approval / denial determination. Therefore, according to the inspection result, it becomes possible to additionally perform inspections such as temperature checks as necessary when participating in the event or entering the facility, and it becomes possible to impose participation restrictions or entry restrictions by more accurately judging the user's status.

[0134] If it is determined in step S36 that authentication cannot be performed (S36: NO), or if it is determined in step S37 that permission has already been granted (S37: YES), the control unit 11 transmits rejection information indicating rejection of participation or entry of this user and the reason for rejection to the entrance management server 30 (S157). The reason for rejection here is that authentication was not performed, that permission has already been issued, etc. When the control unit 31 of the entrance management server 30 receives the rejection information from the server 10, it closes the gate 38a by the gate opening / closing unit 38 (S158), and notifies that participation in the event or entry into the facility has been rejected by the notification process of the notification unit 37 (S159). Note that the control unit 31 may notify the reason for rejection received from the server 10.

[0135] In the present embodiment, the same effects as those of the above-described embodiments can be obtained. Also, in the present embodiment, it is possible to guide to different guiding destinations and perform different responses according to the result (reason for rejection) of the approval determination based on the inspection result of the user. Note that a response (guiding destination) according to the inspection result may be registered for each inspection item, and in this case, even for inspections for the same infectious disease, different responses can be performed for each inspection using different types of inspection methods. Also in the present embodiment, the application of the modified examples appropriately described in the above-described embodiments is possible. Further, the configuration of the present embodiment can also be applied to the information processing system 100 of Embodiments 2-9, and the same effects can be obtained even when applied to the information processing system 100 of Embodiments 2-9.

[0136] In each of the above-described embodiments, when a user participates in an event or enters a facility, approval determination of participation or entry is made based on the inspection result of the user registered in the server 10. In addition, the user may be configured to make an approval determination of participation or entry based on his / her own inspection result in advance. In this case, since the user can grasp in advance whether participation or entry is approved, it is possible to take measures such as receiving additional inspections so that participation or entry is permitted, and for example, it is possible to prepare to surely participate in the event on the event date.

[0137] (Embodiment 11) An information processing system that uses vaccination history to restrict the passage of users at various checkpoints (gates) will be described. Since the information processing system of this embodiment can be realized by an apparatus similar to the information processing system 100 of Embodiment 1, a detailed description of the configuration will be omitted. In this embodiment, the user DB 12a stored in the storage unit 12 of the server 10 is slightly different from the configuration of Embodiment 1 shown in FIG. 3. Also, in this embodiment, since the passage of users is restricted based on vaccination history, it is not necessary to set passage conditions for each event or facility, and it is not necessary to provide the registration terminal 40, nor is it necessary for the event DB 12b and the facility DB 12c to be stored in the storage unit 12 of the server 10. As the passage condition for each event or facility, the number of vaccinations may be set. In this case, the passage condition for each event or facility is set using the registration terminal 40 and stored in the event DB 12b and the facility DB 12c of the server 10.

[0138] FIG. 34 is a schematic diagram showing a configuration example of the user DB 12a of Embodiment 11. The user DB 12a of this embodiment includes a user ID column, a name column, a code information column, a vaccination column, etc. The code information column stores information (code information) used when generating a code issued to each user in association with the user ID. Note that the user ID may be included in the code information. The vaccination column stores information regarding the vaccination history of the user in association with the user ID. The vaccination history information includes, for each vaccination number (which vaccination it is), the vaccination date, the name of the vaccine manufacturer, the type, the lot number, the expiration date, information such as the medical institution where the vaccination was received, etc. The information of the vaccination institution includes the name of the medical institution, etc., and the location (for example, country name, prefecture name), etc. Note that the vaccination history information may be deleted by the control unit 11 when a predetermined expiration date has passed since the vaccination date. Also, an expiration flag may be provided in the user DB 12a, and the control unit 11 may change the expiration flag from 0 to 1 when a predetermined expiration date has passed since the vaccination date.

[0139] In the information processing system 100 of the present embodiment, each device executes the same processing as that shown in FIG. 8. In the present embodiment, in step S26 in FIG. 8, the control unit 11 of the server 10 reads out the code information corresponding to the user ID received from the user terminal 20 from the user DB 12a, and generates a code based on the read code information. Thus, also in the present embodiment, the control unit 11 (first output unit) of the server 10 can issue the code requested via the user terminal 20, output it to the user terminal 20, and provide it to the user. In the present embodiment, the code issued using the code information associated with the user is provided to the user terminal 20.

[0140] FIG. 35 is a flowchart showing an example of the determination processing procedure of Embodiment 11. In FIG. 35, the processing performed by the user terminal 20 is shown on the left side, the processing performed by the admission management server 30 is shown in the center, and the processing performed by the server 10 is shown on the right side. In the following processing, it is assumed that the passing condition is set to having been vaccinated twice with the vaccine within six months. The vaccine can be, for example, a vaccine against the novel coronavirus. Also in the present embodiment, when the control unit 21 of the user terminal 20 receives an execution instruction for the PHR app 22AP and a display instruction for the code via the input unit 24, the control unit 21 starts the PHR app 22AP and displays the code received from the server 10 on the display unit 25 (S201). Then, the user holds the user terminal 20 on which the code is displayed over the code reader 36 of the gate device 30a to cause the code reader 36 to read the code.

[0141] The control unit 31 of the entrance management server 30 reads the code with the code reader 36 (S202) and acquires the code information (S203). The control unit 31 transmits the acquired code information to the server 10 (S204) and requests the server 10 for the vaccination history of this user. When the control unit 11 (acquisition unit) of the server 10 is requested for the vaccination history from the entrance management server 30, it acquires the code information read by the entrance management server 30 and performs an authentication process based on the code information acquired from the entrance management server 30 (S205). Here, the control unit 11 determines whether the code information acquired from the entrance management server 30 is registered in the user DB 12a. If it is registered, this user is determined to be a legitimate user. The control unit 11 (reading unit, second output unit) determines whether it can authenticate that the user is a legitimate user (S206). If it determines that authentication is successful (S206: YES), it reads the vaccination history information of the authenticated user from the user DB 12a (S207) and transmits the read vaccination history information to the entrance management server 30 (S208).

[0142] When the control unit 31 of the entrance management server 30 acquires the vaccination history information from the server 10, it determines whether the passing condition is satisfied based on the acquired vaccination history information (S209). Here, the control unit 31 determines whether the user has been vaccinated twice within 6 months based on the vaccination history information. When the control unit 31 determines that the passing condition is satisfied (S209: YES), that is, when the user has been vaccinated twice within 6 months, the gate opening / closing unit 38 opens the gate 38a (S210). At this time, the control unit 31 may perform a notification process of notifying that passage is permitted by the notification unit 37.

[0143] On the other hand, when it is determined that the passing condition is not satisfied (S209: NO), that is, when the user has not been vaccinated twice, or when the user has been vaccinated twice but the expiration date of the vaccine (for example, six months) has passed, the control unit 31 closes the gate 38a by the gate opening / closing unit 38 (S211), and notifies that the passage has been rejected by the notification process of the notification unit 37 (S212). The notification process here notifies the reason for the rejection of passage. For example, it notifies "The vaccine has not been administered twice" or "The expiration date of the vaccine has passed". As a result, the user can recognize that the passing condition regarding vaccination is not satisfied, and the entrance management server 30 can notify the user, the organizer of the nearby event, or the person in charge of the facility that the passage of the user has been rejected.

[0144] When it is determined in step S206 that the user cannot be authenticated as a legitimate user (S206: NO), the control unit 11 of the server 10 transmits rejection information indicating the rejection of passage of this user to the entrance management server 30 (S213). Also in this case, the control unit 31 of the entrance management server 30 closes the gate 38a by the gate opening / closing unit 38 (S211), and notifies that the passage has been rejected by the notification process of the notification unit 37 (S212). The notification process here notifies that the authentication has failed. For example, it notifies "Please read the correct code". As a result, the user can recognize that an incorrect code has been read to the entrance management server 30.

[0145] Through the above-described processing, in the information processing system 100 of the present embodiment, when a user passes through a passage gate, it is determined whether or not the passage conditions are satisfied based on the vaccination history of the user registered in the server 10. Then, depending on whether or not the user's vaccination history satisfies the passage conditions, passage through the passage gate is permitted or rejected. Therefore, the vaccination history of each user registered in the server 10 can be used for restricting the passage of users by the entrance management system. For example, when vaccination is mandatory when entering or leaving a country or entering or leaving a specific area, the passage examination can be cleared by using the vaccination history of each user registered in the server 10.

[0146] In the present embodiment, the determination as to whether or not the user's vaccination history satisfies the passage conditions may be made not only by the entrance management server 30 but also by the server 10. In this case, after reading the user's vaccination history from the user DB 12a, the server 10 determines whether or not the read vaccination history satisfies the passage conditions, and transmits the determination result to the entrance management server 30. Note that the passage conditions may be registered in the server 10 in advance, or the server 10 may acquire them from the entrance management server 30. Further, the server 10 may determine whether or not to permit the passage of the user according to whether or not the vaccination history satisfies the passage conditions, and transmit the determination result to the entrance management server 30. Furthermore, in addition to various information on vaccination, the user DB 12 may include information regarding the results of infectious disease tests (test date, test result, test location, etc.). In this case, the results of the infectious disease tests are read at the same timing as S207 in FIG. 35 and transmitted to the entrance management server 30 together with the vaccination history. The passage conditions may include, in addition to the above-described passage conditions for vaccination, that the results of the infectious disease tests (for example, the results of the infectious disease tests received within a predetermined period before passage) are negative.

[0147] In this embodiment, the same effects as those of the above-described embodiments can be obtained. Also, in this embodiment, it is possible to determine whether to permit a user to pass (participate in an event or enter a facility) according to the user's vaccination history. For example, when vaccination against the novel coronavirus is mandatory when entering or leaving the country at the border or entering or leaving a predetermined area, the user can pass the screening based on the novel coronavirus vaccination history registered in the server 10. Also in this embodiment, the application of the modification examples appropriately described in the above-described embodiments is possible. Further, the configuration of this embodiment can also be applied to the information processing system 100 of Embodiments 2-10, and the same effects can be obtained even when applied to the information processing system 100 of Embodiments 2-10.

[0148] Note that in this embodiment, as described above, in step S26 in FIG. 8, the control unit 11 of the server 10 reads out the code information corresponding to the user ID received from the user terminal 20 from the user DB 12a and generates a code based on the read code information. However, the present invention is not limited to this, and the generated code may include vaccination history information and / or infectious disease test result information in addition to the code information. In this case, the control unit 11 transmits a screen including a code such as a QR code and vaccination history information and / or infectious disease test results in character information to the user terminal 20. Then, when the entrance management server 30 in which the passage conditions are stored reads the code of the screen, it acquires the code information included in the code, and the vaccination history information and / or infectious disease test result information, and determines whether the passage conditions are satisfied. Thereby, it is possible to execute a rejection determination of the user's passage by the entrance management server 30 alone without passing through the server 10.

[0149] (Embodiment 12) In the passage restriction when a user passes through various passing points (passing gates), an information processing system configured to perform processing according to the contents of the vaccination history and the infectious disease test results will be described. Since the information processing system 100 of this embodiment can be realized by the same devices as the information processing system 100 of Embodiment 1, detailed description of the configuration will be omitted. In this embodiment, in addition to the configuration of Embodiment 1 shown in FIG. 5, the entrance management server 30 stores a correspondence processing DB 32c and a passage management DB 32d in the storage unit 32. The correspondence processing DB 32c and the passage management DB 32d may be stored in another storage device connected to the entrance management server 30, or may be stored in another storage device that the entrance management server 30 can communicate with via the network N. Also in this embodiment, the registration terminal 40 may not be provided, and the event DB 12b and the facility DB 12c may not be stored in the storage unit 12 of the server 10. Note that, as the passage conditions for each event or each facility, conditions based on the number of vaccination times and / or the infectious disease test results may be set.

[0150] FIG. 36A is a schematic diagram showing a configuration example of the correspondence processing DB 32c. The correspondence processing DB 32c stores information on processes to be executed according to the vaccination history and the results of infectious disease tests. Specifically, the correspondence processing DB 32c includes a process ID column, a vaccination history column, an infectious disease test result column, a process content column, and the like. The process ID column stores identification information (process ID) for identifying each process. The vaccination history column stores condition information regarding the vaccination history of, for example, the novel coronavirus, and specifically includes those who have been vaccinated twice, those who have been vaccinated once, and those who have not been vaccinated. The infectious disease test result column stores condition information regarding the PCR test result of, for example, the novel coronavirus, and includes, for example, negative, positive, and untested. The process content column stores information on processes to be executed according to each condition of the vaccination history and each condition of the infectious disease test result. The process content includes, for example, opening or closing of the gate by the gate device 30a, notification of a predetermined message by the notification unit 37, display of a predetermined message by the display unit 35, and the like. With such a configuration, the correspondence processing DB 32c registers the processes to be executed at the passage gate according to the vaccination history and the results of infectious disease tests. The content of the correspondence processing DB 32c is set and stored in advance and can be changed as appropriate.

[0151] FIG. 36B is a schematic diagram showing a configuration example of the passage management DB 32d. The passage management DB 32d stores information regarding the result of restricting the passage of users by the entrance management server 30. Specifically, the passage management DB 32d includes an entrance management server ID column, a user ID column, a passage restriction result column, an execution process column, and the like. The entrance management server ID column is an ID assigned to the entrance management server 30 that restricts the passage of users. Note that the entrance management server ID column may be configured to store the gate ID assigned to the gate device 30a in addition to the ID of the entrance management server 30. The user ID column stores the user ID of the user whose passage is permitted or denied by the entrance management server 30. The passage restriction result column stores information indicating the result of the passage restriction performed by the entrance management server 30, and stores, for example, passage permission or passage rejection. The execution process column stores the content of the process executed during the passage restriction, and stores, for example, the process ID of each process registered in the corresponding process DB 32c. According to the passage management DB 32d having such a configuration, as a result of the passage restriction by the entrance management server 30, it is possible to accumulate whether each user is permitted or denied passage, and the content of the process executed by the gate device 30a at that time. The passage management DB 32d may be configured to also store the vaccination history and infectious disease test results of each user.

[0152] In the information processing system 100 of the present embodiment, each device executes the same processing as the processing shown in FIG. 8. Also in the present embodiment, in step S26 in FIG. 8, the control unit 11 of the server 10 generates a code based on the code information corresponding to the user ID received from the user terminal 20. Thus, also in the present embodiment, in response to a request from the user terminal 20, a code based on the code information associated with the user is issued by the server 10 and provided to the user terminal 20. Note that the control unit 11 of the server 10 operates as a first output unit that outputs the code generated from the code information associated with the vaccination history of the user who has requested the code to the user terminal of the requesting user.

[0153] FIG. 37 is a flowchart showing an example of the determination processing procedure according to Embodiment 12. The processing shown in FIG. 37 adds steps S221 to S222 instead of step S208 in the processing shown in FIG. 35, adds steps S251 to S253 instead of steps S209 to S210, and adds step S254 after step S212. Explanation of the same steps as in FIG. 35 is omitted. The control unit 21 of the user terminal 20, the control unit 31 of the entrance management server 30, and the control unit 11 of the server 10 in the present embodiment perform the same processing as steps S201 to S207 shown in FIG. 35. The control unit 11 of the server 10 reads out the vaccination history information of the authenticated user from the user DB 12a (S207), reads out the result information of the infectious disease test from the user DB 12a (S221), and transmits the read vaccination history information and the result information of the infectious disease test to the entrance management server 30 (S222). Therefore, the control unit 11 of the server 10 operates as a second output unit that outputs the vaccination history and the infectious disease test result of the user whose code has been read by the entrance management server 30 to the entrance management server 30.

[0154] In the present embodiment, when the control unit 31 of the entrance management server 30 acquires the vaccination history information and the result information of the infectious disease test from the server 10, based on the acquired vaccination history information and the result information of the infectious disease test, the control unit 31 specifies the processing to be executed by the gate device 30a (S251). Here, the control unit 31 specifies the vaccination history and the infectious disease test result that match the vaccination history information and the result information of the infectious disease test acquired from the server 10 based on the stored content of the correspondence processing DB 32c, and specifies the processing content corresponding to the specified vaccination history and the infectious disease test result.

[0155] The control unit 31 (execution unit) instructs the gate device 30a to execute the specified process, and the gate device 30a executes the specified process (S252). For example, when the control unit 31 specifies the opening of the gate as the process to be executed, it instructs the gate device 30a to open the gate, and the gate device 30a opens the gate 38a by the gate opening / closing unit 38 to permit the user to pass through. Also, when the control unit 31 specifies the closing of the gate and the notification of the implementation of the infectious disease inspection as the processes to be executed, it instructs the gate device 30a to close the gate and also instructs the notification of the implementation of the infectious disease inspection. In this case, the gate device 30a closes the gate 38a by the gate opening / closing unit 38 to reject the passage of the user, and notifies that it is necessary to perform the infectious disease inspection by the notification process of the notification unit 37.

[0156] The control unit 31 stores the result of the executed passage restriction in the passage management DB 32d (S253). Specifically, the control unit 31 associates the user ID of the user who was the target of the passage restriction, the passage restriction result indicating whether passage was permitted or rejected, and the process performed during the passage restriction with the ID of the admission management server 30, and stores them in the passage management DB 32d. The process ID of each process registered in the correspondence processing DB 32c may be stored as the process performed during the passage restriction. Note that the control unit 31 may store the code information of the user acquired in step S203, the vaccination history received from the server 10, the infectious disease inspection result, etc. in the passage management DB 32d. By the above-described process, the admission management server 30 can not only perform passage restriction of the passage gate, but also perform notification of various messages by processes according to the vaccination history and infectious disease inspection result of the user. Also, as a result of performing passage restriction, the admission management server 30 can accumulate whether passage of each user is permitted or not, the processes performed on the gate device 30a for each user, etc., and can store information regarding passage restriction for each user. Note that the admission management server 30 may transmit information regarding such a passage restriction result to the server 10, and the server 10 may be configured to store information regarding passage restriction for each user in, for example, the user DB 12a.

[0157] On the other hand, when it is determined in step S206 that the user cannot be authenticated (S206: NO), the control unit 11 of the server 10 transmits rejection information to the entrance management server 30 (S213). In this case, the control unit 31 of the entrance management server 30 closes the gate 38a by the gate opening / closing unit 38 (S211), and notifies that the passage has been rejected by the notification process of the notification unit 37 (S212). Then, the control unit 31 stores the result of the executed passage restriction in the passage management DB 32d (S254). Here, the control unit 31 associates the user ID of the user who was the target of the passage restriction, the passage restriction result indicating that the passage was rejected, and the process performed during the passage restriction (specifically, the closing of the gate) with the ID of the entrance management server 30 and stores them in the passage management DB 32d. Also here, the control unit 31 may store the code information etc. of the user acquired in step S203 in the passage management DB 32d. Thereby, the entrance management server 30 can accumulate information regarding the result of passage rejection due to the inability to authenticate the user.

[0158] In the present embodiment, the same effects as those of the above-described embodiments can be obtained. Also in the present embodiment, since processing according to the user's vaccination history and the results of infectious disease tests can be performed, different responses can be made for each user. Also in the present embodiment, the application of the modification examples appropriately described in the above-described embodiments is possible. Further, the configuration of the present embodiment can also be applied to the information processing system 100 of Embodiments 2-10, and the same effects can be obtained even when applied to the information processing system 100 of Embodiments 2-10.

[0159] The embodiments disclosed this time should be considered to be illustrative in all respects and not restrictive. The scope of the present disclosure is shown not by the above meaning but by the claims, and it is intended that all modifications within the meaning and scope equivalent to the claims are included.

Description of Reference Numerals

[0160] 10 Server 11 Control Unit 12 Storage Unit 13 Communication unit 20 User terminal 30 Entrance management server 31 Control unit 32 Memory unit 33 Communication unit 34 Gate device communication unit 36 Code reader 37 Notification unit 38 Gate opening / closing unit 39 Biometric information acquisition unit 40 Registration terminal 12a User DB 12b Event DB 12c Facility DB 30a Gate device 32a Ticket DB 32b Guidance content DB 36b IC card reader 36c Camera 38a Gate

Claims

1. Store health information in a database for each user in association with user identification information, For each passing point where a distributed management system manages the passing of the user, store in a condition database the passing conditions of the passing point based on the health information, in association with passing point identification information, Obtain the user identification information and the passing point identification information read by the management system, Read from the database the health information corresponding to the obtained passing point identification information among the health information corresponding to the obtained user identification information, Based on the read health information, determine whether the passing conditions of the passing point are satisfied, Output the determination result to the management system An information processing method executed by a computer for the above process.

2. Store in a database the user identification information of the user determined to satisfy the passing conditions of the passing point, in association with the passing point identification information, If the obtained user identification information is stored in the database in association with the obtained passing point identification information, output to the management system a determination result indicating that the passing conditions of the passing point are not satisfied The information processing method according to claim 1, executed by the computer for the above process.

3. Output the health information to a management system that manages the opening and closing of a gate The information processing method according to claim 1 or 2, executed by the computer for the above process.

4. The health information is selected from the test results regarding the presence or absence of infection with an infectious disease, the presence or absence of antibodies, the presence or absence of vaccination, the presence or absence of allergic diseases to allergens, medical history, and medication history The information processing method according to any one of claims 1 to 3.

5. Cause the management system to read the authentication information of the user, Cause the management system to execute the authentication of the user based on the authentication information The information processing method according to any one of claims 1 to 4, executed by the computer for the above process.

6. Generate a code including the user identification information and the ticket information required for passing through the passing points managed by the management system, Output the generated code to the user terminal of the user The information processing method according to any one of claims 1 to 5, executed by the computer for the above process.

7. The ticket information required for passing through the passing points managed by the management system and the user identification information are associated with a conversion table, Obtain the converted user identification information converted by the conversion table corresponding to the ticket information read by the management system, Read the health information corresponding to the obtained converted user identification information from the database, Output information regarding the read health information to the management system that read the ticket information before conversion. The computer executes the process according to any one of claims 1 to 6. The information processing method described.

8. Obtain the user identification information of the user and the passing point identification information of the passing point through which the user passes, Among the health information corresponding to the obtained user identification information, obtain from a server having a database that stores health information associated with the user identification information for each user according to the passing conditions of the passing point corresponding to the obtained passing point identification information, Based on the obtained health information, determine whether the user is allowed to pass through the passing point. The information processing method executed by the computer.

9. Store health information in the database in association with the user identification information for each user, Among the health information corresponding to the user identification information, read the health information according to the passing conditions of the passing point through which the user passes from the database, Generate a code including the read health information and the user identification information, Output the generated code to the user terminal of the user. The information processing method executed by the computer.

10. Store in the database the passing conditions of the passing point based on the health information of the user, Obtain the health information read from the code including the user identification information and health information of the user, Read the passing conditions of the passing point through which the user passes from the database, Based on the obtained health information, determine whether the passing conditions are satisfied, Based on the determination result, determine whether the user is allowed to pass through the passing point. The information processing method executed by the computer.

11. Store the user identification information of the user who is permitted to pass through the passing point in the database, Obtain the user identification information read from the code, If the obtained user identification information is stored in the database, reject the user's passing through the passing point. The computer executes the process according to the information processing method described in claim 10.

12. An information processing method by an information processing system including a server having a database for storing health information in association with user identification information for each user, and a distributed management system, comprising: The management system: Obtains the user identification information and the passing point identification information of the passing point through which the user passes; Outputs the obtained user identification information and the passing point identification information to the server; The server: Reads out from the database the health information corresponding to the obtained passing point identification information among the health information corresponding to the user identification information obtained from the management system, according to the passing condition corresponding to the obtained passing point identification information; Outputs the read health information to the management system; The management system: Determines whether the user is allowed to pass through the passing point based on the health information corresponding to the user identification information obtained from the server. An information processing method including the above processing.

13. Store health information in a database for each user, Output the code associated with the health information to the user terminal of the user, The distributed management system obtains the code information obtained by reading the code and the passing point identification information of the passing point through which the user passes, Reads out from the database the health information corresponding to the passing point corresponding to the obtained passing point identification information among the health information corresponding to the obtained code information, according to the passing condition of the passing point corresponding to the obtained passing point identification information, Outputs the read health information to the management system. An information processing method in which a computer executes the above processing.

Images