JP2020086551A - Reception system for medical treatment facility - Google Patents

Abstract

To improve security in interview to an inpatient and manage properly interview in a medical treatment facility.SOLUTION: There is provided a reception system for a medical treatment facility comprising: a reception device; and a program which is executed on a portable terminal possessed by a user. The reception device comprises a user interface which a user faces for operation, and the reception device can allow function addition processing which is executed between the device and the portable terminal when a user operates the user interface, and interview reception processing for determining whether or not to permit interview on the basis of interview permission information input by a visitor, and the program can send interview permission information for permitting interview to a visitor on a condition in which the function addition processing has been executed.SELECTED DRAWING: Figure 1

Description

The present invention relates to a medical facility reception system that receives an in-patient visit in a medical facility such as a hospital.

BACKGROUND ART In medical facilities such as hospitals, visits are held to visit patients (inpatients) who are hospitalized by relatives, acquaintances, etc., or to take care of them. Conventionally, visits at medical facilities have been made by recording the name of the visitor, the name of the inpatient who is the visitee, the hospital room number of the inpatient, the time of visit, the time of exit, etc. in a paper visit record installed at the counter. It was usually managed.

However, such visit management has security problems such as inaccurate records of visits and passing through if the name and hospital room number of the inpatient are known. In order to solve such a problem, in Patent Document 1, an interview application is made from the PC of the interview applicant, and if the answer of the application is a witness, the visit reservation is sent to the PC of the applicant and the visit is made. It is disclosed that the opening and closing of the gate device is controlled on the condition that the permission is granted and that the voiceprint information registered in advance is matched at the time of the visit.

Further, in Patent Document 2, when an inpatient designates a visit permitting person and a desired visit date, an inquiry is made about the medical treatment schedule of the inpatient, the visitable date and time is sought, and then a visit visitor is visited by email. Disclosing the authorization code is disclosed. Further, in Patent Document 3, the number of visitors who can be accommodated at the same time (the number of people who can accommodate at the same time) is assigned to each patient room, and when the number of patients that can be accommodated at the same time is less than or equal to the patient room, the patient's room can be selected as the meeting place. It is disclosed.

JP, 2008-305315, A JP, 2013-222269, A JP, 2008-225834, A

As disclosed in Patent Documents 1 to 3, various visit managements using an information processing device have been proposed. By the way, nowadays, mobile terminals owned and owned by users, such as smartphones, have become popular. It is conceivable to manage visits using such a mobile terminal. However, if the personal-owned mobile terminal is allowed to freely manage visitation, a security problem will occur. An object of the present invention is to make it possible to execute various kinds of processing relating to visits using a mobile terminal possessed by a user, and to secure security at that time.

The medical facility reception system according to the 1-1 configuration,
A reception system for a medical facility, which includes a reception device and a program executed by a mobile terminal owned by a user,
The reception device has a user interface with which a user faces and operates,
By operating using the user interface, function addition processing executed with the mobile terminal,
It is possible to execute visitation acceptance processing for judging permission or disapproval of visitation based on the visitation permission information input by the visitor,
The program enables transmission of the visit permission information for permitting the visit to the visitor on condition that the function addition process is executed.

Further, the medical facility reception system according to the 1-2 configuration is the medical facility reception system according to the 1-1 configuration,
The function addition process is performed by reading the code information displayed on the reception device with the mobile terminal, or by reading the code information displayed on the mobile terminal with the reception device.

Further, the medical facility reception system according to the 1-3rd configuration is the medical facility reception system according to the 1-1 or 1-2 configuration,
The reception device includes a camera,
In the function addition processing, a user who operates in front of the reception device is photographed by the camera, and the function addition time information including image pickup information is stored.

Further, the medical facility reception system disclosed in the present specification has the following 2-1 to 2-5 configurations.

The medical facility reception system according to the 2-1st configuration,
A reception system for a medical facility including a reception device and a storage unit,
The storage unit stores identification information of a patient and attribute information indicating a relationship between the user and the patient in association with the biometric authentication information of the user,
The reception device is capable of executing a visit reception process,
The visit reception process executes a biometric authentication process for the user who has applied for the visit,
In the biometric authentication process, if there is biometric authentication information for the user, the patient identification information corresponding to the biometric authentication information, and the attribute information is read,
A medical facility reception system that determines whether a visit is possible based on the read attribute information when the patient corresponding to the read patient identification information is in the hospital.

The medical facility reception system according to the 2-2 configuration is the medical facility reception system according to the 2-1 configuration,
The visit acceptance process determines whether or not the visit is possible based on the available visit time corresponding to the read attribute information.

The medical facility reception system according to the 2-3rd configuration is the medical facility reception system according to the 2-1 or 2-2 configuration,
When a plurality of patients associated with biometric authentication information are hospitalized in the visit reception process, the user is allowed to select a patient to visit.

A medical facility reception system according to a 2-4th configuration is the medical facility reception system according to any one of the 2-1 to 2-3 configurations,
The storage unit is capable of setting special attribute information indicating the relationship between the user and the patient in association with the biometric information of the user,
In the emergency reception process, when an emergency reception application is made in an emergency, only the user for whom the special attribute information is set is allowed to receive the visit.

The medical facility reception system according to the 2-5th configuration is the medical facility reception system according to the 2-4th configuration,
The special attribute information is limited in the number of users that can be set for one patient.

A medical facility reception system according to a 2-6th configuration is the medical facility reception system according to any one of the 2-1 to 2-5 configurations,
Makes it possible to perform check-in processing for receiving patient medical treatment,
In the check-in process, a biometric authentication process is executed for the user who has applied for medical treatment,
In the biometric authentication process, if there is biometric authentication information for the user, the medical treatment of the patient corresponding to the biometric authentication information is accepted.

Further, the medical facility reception system disclosed in the present specification has the following third configuration.
The medical facility reception system according to the third configuration,
A reception system for a medical facility including a reception device and a storage unit,
The storage unit stores the identification information of the patient associated with the biometric authentication information of the user, and can set the special attribute information indicating the relationship between the user and the patient,
The reception device is capable of executing a visit reception process,
The visit reception process executes a biometric authentication process for the user who has applied for the visit,
In the biometric authentication process, if there is biometric authentication information for the user, read the patient identification information corresponding to the biometric authentication information,
When an application for an interview is made in an emergency, only the user who has the hospital corresponding to the read identification information of the patient and has the special attribute information set is allowed to visit.

Further, the medical facility reception device disclosed in the present specification has the following fourth configuration.

The medical facility reception system according to the fourth configuration,
A reception system for a medical facility including a reception device and a storage unit,
The storage unit stores the identification information of the patient associated with the biometric authentication information of the user, and can set the special attribute information indicating the relationship between the user and the patient,
The reception device is capable of executing a visit reception process,
The visit reception process executes a biometric authentication process for the user who has applied for the visit,
In the biometric authentication process, if there is biometric authentication information for the user, read the patient identification information corresponding to the biometric authentication information,
When an application for an interview is made in an emergency, only the user who has the hospital corresponding to the read identification information of the patient and has the special attribute information set is allowed to visit.

Further, the medical facility reception device disclosed in the present specification has the following 5-1 to 5-2 configurations.

The medical facility reception system according to the 5-1st configuration,
A reception system for a medical facility including a reception device and a storage unit,
The storage unit stores the identification information of the patient associated with the biometric authentication information of the user,
The reception device is capable of executing a first visit reception process and second visit information,
In the first visit reception processing, the biometric authentication processing is executed for the user who has applied for the visit,
In the biometric authentication process, if there is biometric authentication information for the user, the identification information of the patient corresponding to the biometric authentication information is read, and if the patient corresponding to the read identification information of the patient is in the hospital, the visit is permitted. ,
The second visit acceptance process permits the visit when the visit permission information input by the user is appropriate.

The medical facility reception system according to the 5-2nd configuration is the medical facility reception system according to the 5-1th configuration,
The storage unit stores attribute information indicating the relationship between the user and the patient in association with the biometric information of the user,
In the first visit reception process, when the patient corresponding to the read identification information of the patient is hospitalized, it is determined whether or not the visit is possible based on the read attribute information.

Further, the medical facility reception device disclosed in the present specification has the following 6-1 to 6-2 configurations.

The medical facility reception apparatus according to the 6-1th configuration,
Check-in processing for receiving medical treatment of patients and visit reception processing for receiving visits for inpatients can be executed.
In the check-in process and the visit reception process, a body temperature of the user facing the reception device is measured, and a temperature measurement process for determining whether the body temperature is normal is executed.
The temperature measurement process performed in the check-in process and the temperature measurement process performed in the visit reception process have different thresholds for determining whether or not the body temperature is normal.

In the medical facility reception device according to the sixth configuration,
The threshold value of the body temperature used in the temperature measurement process of the check-in process is set higher than the threshold value of the body temperature used in the temperature measurement process of the visit reception process.

According to the medical facility reception system according to the first configuration (1-1 to 1-3 configurations), the program executed on the mobile terminal performs the function addition process executed with the reception device. By executing it, it becomes possible to transmit the visit permission information for permitting the visit to the visitor. Therefore, it is possible to enhance the safety of the function of transmitting the visit permission information in which security is important.

According to the medical facility reception system according to the second configuration (the configurations 2-1 to 2-5), the biometric authentication process is used in the visit application, and the attribute information indicating the relationship between the user and the patient is displayed. It is decided to use it to judge whether or not to meet. With such a configuration, it is possible to judge whether or not a visit can be made using attribute information, such as allowing visits for relatives within the first degree of relatives and disallowing visits for relatives more than one degree apart. Is possible. In addition, if the user has pre-registered the biometric authentication information, it is not necessary to present any documents when applying for the visit.

According to the medical facility reception system according to the third configuration, as in the second configuration, it is possible to determine whether or not a visit can be made using the attribute information privately, and at the time of emergency, the special attribute information is used. It is possible to limit the scope of visits. For example, when a viral illness such as influenza is prevalent, only users with special attribute information are allowed to visit, limiting the number of visitors to the medical facility and controlling nosocomial infections. It becomes possible.

According to the medical facility reception system according to the fourth configuration, as in the third configuration, it is possible to limit the range of the visit using the special attribute information in an emergency.

According to the medical facility reception system according to the fifth configuration (the configurations 5-1 to 5-2), the first visit reception process for performing the biometric authentication process, and the second visit using the visit permission information. By enabling the reception process to be performed, the user who has registered the biometric authentication information can easily perform the visit, and the user who receives the visit permission information by e-mail or the like inputs the visit permission information. This makes it possible to meet.

According to the medical facility reception system according to the sixth configuration (the 6-1 to 6-2 configurations), the temperature measurement process performed in the check-in process and the temperature measurement process performed in the visit reception process. The processing is different in the threshold value for determining whether or not the body temperature is normal. With such a configuration, for example, in a visit reception process, by setting a strict threshold for determining whether the body temperature is normal or not, when a viral illness such as influenza is prevalent, nosocomial infection due to the visit can be prevented. It becomes possible to suppress.

The figure which shows the structure of the reception system which concerns on this embodiment. Front view of the reception device according to the present embodiment Block diagram showing the configuration of a reception device according to the present embodiment Block diagram showing the configuration of a mobile terminal according to the present embodiment The figure which shows the initial screen of the reception device which concerns on this embodiment. Flow chart showing face registration processing (on the reception device side) according to the present embodiment Flow chart showing face registration processing (management computer side) according to the present embodiment Flow chart showing face registration processing (management computer side) according to the present embodiment Diagram showing various data configurations used in the reception system according to the present embodiment The figure for demonstrating the relationship of the face registration authentication information and patient basic information which concern on this embodiment. The figure which shows the consultation ticket reading screen which concerns on this embodiment The figure which shows the attribute selection screen which concerns on this embodiment The figure which shows the auxiliary authentication information registration screen which concerns on this embodiment. The figure which shows the user addition confirmation screen which concerns on this embodiment A diagram showing an outpatient screen according to the present embodiment Flow chart showing the check-in process according to the present embodiment Flow chart showing the first face authentication processing according to the present embodiment The figure which shows the auxiliary authentication information input screen which concerns on this embodiment. The figure which shows the target patient selection screen which concerns on this embodiment A diagram showing a check-in confirmation screen according to the present embodiment Flowchart showing wireless check-in function addition processing according to the present embodiment The figure which shows the various screens of the portable terminal which concerns on this embodiment. The figure which shows the various screens of the portable terminal which concerns on this embodiment. Flowchart showing visit invitation processing according to the present embodiment The figure which shows the visit invitation confirmation screen of the mobile terminal which concerns on this embodiment. Flow chart showing the visit reception process according to the present embodiment The figure which shows the selection screen which concerns on this embodiment Flow chart showing the first meeting determination process according to the present embodiment Flowchart showing the second face authentication processing according to the present embodiment Flow chart showing the second meeting determination process according to the present embodiment The figure which shows the visit certificate which concerns on this embodiment

FIG. 1 is a diagram showing a configuration of a reception system according to the present embodiment. The reception system of the present embodiment is a system that enables easy reception (check-in) of a medical examination at the time of the second medical examination and subsequent medical examinations at various medical facilities such as hospitals. The reception system of this embodiment is installed in the lobby located near the entrance 72 of the medical facility. The reception system includes reception devices 1a and 1b arranged in the lobby and operated by the user, a management computer 3 arranged in the hospital reception 71 and the like and operated by an employee. It should be noted that a plurality of reception devices 1a and 1b (two in this embodiment) are arranged so that a plurality of users can be simultaneously provided with services.

The reception devices 1a and 1b and the management computer 3 are communicably connected to each other via a LAN 51. The management computer 3 is connected to a monitor 42 for displaying various information, a keyboard, a mouse, and the like, and an input device 41 for accepting input by an employee. Further, a receipt printer 44 for printing on receipt-type paper and a card reader 43 for reading (writing may be possible) the information stored in the medical examination ticket are also connected.

FIG. 2 is a front view of the reception device 1 according to the present embodiment. The reception device 1 is a device that can provide various services such as new patient reception and re-receipt reception (also referred to as check-in) to a user who faces the operation. The accepting device 1 of the present embodiment includes a touch panel monitor 12, a card reader 14, a scanner 15a, a two-dimensional barcode reader 15b, a receipt printer 16a, a printer 16b, a camera 13a, and an infrared camera 13b. These configurations function as a user interface for a user who operates the reception apparatus 1.

The touch panel monitor 12 displays visual information to a user who is face-to-face and is capable of accepting a touch operation by the user. Above the touch panel monitor 12, a camera 13a capable of picking up an image of a range including the face of a user who faces and operates, and an infrared camera 13b are provided. The camera 13a is for taking a picture of the user's face to be used, and the infrared camera 13b is provided for taking a picture of the user's face to be used and performing a temperature detecting process to detect the body temperature of the user.

The card reader 14 reads various kinds of information such as a patient ID stored in a medical examination card constituted by a magnetic card or an IC card carried by the user. Further, the card reader may have a reading function of a credit card used for payment of medical expenses. The scanner 15a is a flat bed type provided for reading a health insurance card, and when it is necessary to present the health insurance card at the time of re-acceptance, the first medical examination of the month, etc., the scanner 15a is used. Read the insurance card etc. that the user has.

The two-dimensional barcode reader 15b can read various two-dimensional barcodes such as a two-dimensional barcode printed on a printed matter or a two-dimensional barcode displayed on the mobile terminal 2. The object to be read may be in the form of reading various code information such as a one-dimensional bar code instead of the two-dimensional bar code. In that case, a code suitable for the object to be read instead of the two-dimensional bar code reader 15b. A reader is used. Further, the scanner 15a and the two-dimensional bar code reader 15b may be a common reading unit such as using a camera instead of providing both.

The reception device 1 of the present embodiment is provided with a receipt printer 16a and a printer 16b in order to provide a paper medium to the user. The receipt printer 16a is a simple printer that prints on thermal paper used as a receipt, and is used for printing a reception completion table issued at the time of re-receipt, or a reservation table issued at the time of reservation reception. The printer 16b is a printer such as a laser printer or an inkjet printer that prints on normal paper using toner or ink, and is used for printing medical bills, receipts, etc. issued when clothing costs are paid. To be done.

FIG. 3 is a block diagram showing the configuration of the reception device 1 according to the present embodiment. The reception apparatus 1 is configured to include a CPU 11a as a control unit, a ROM 11b, a RAM 11c, an image processing unit 11d, and a sound processing unit 11e, as in a normal computer. Further, it has a storage unit for storing various information such as the hard disk 18. Further, the card reader 14, the scanner 15a, the two-dimensional barcode reader 15b, the receipt printer 16a, the printer 16b, the camera 13a, the infrared camera 13b, the LAN communication unit 17a, and the Bluetooth communication unit 17b are connected via the interface 17. Control by the control unit is possible.

The touch panel monitor 12 is connected to the image processing unit 11d. The touch panel monitor 12 includes a display unit 122 that displays various kinds of information to the user, and a touch panel 121 that receives a touch operation by the user. The touch panel 121 is connected to the interface 17 and can transmit a touch operation by the user to the control unit. A speaker that transmits auditory information to the user is connected to the voice processing unit 11e.

The interface 13 is connected to the camera 13a, the infrared camera 13b, the card reader 14, the receipt printer 16a, the printer 16b, the scanner 15a, the two-dimensional barcode reader 15b, and the touch panel 121 described in FIG. Various processes are executed based on the. In addition, a LAN communication unit 17a and a Bluetooth communication unit 17b (Bluetooth is a registered trademark) as a short-range wireless communication unit are connected to the interface 17 as means for performing various communications. The LAN communication unit 17a is connected to the LAN 51, and can communicate with the Internet via the router 52 and various information processing devices on the LAN such as the management computer 3 described in FIG.

In the present embodiment, in order to communicate with the mobile terminal 2, the Bluetooth communication unit 17b as a short-range wireless communication unit is installed in each reception device 1, but the short-range wireless communication unit includes one reception device. Alternatively, it may be mounted on the No. 1 unit. Alternatively, it may be installed outside the reception device 1. For example, it may be installed in the management computer 3 installed on the same floor as the reception device 1, or may be installed separately in an information processing device that is communicatively connected to the LAN 51 to perform wireless communication with the mobile terminal 2. Can be considered.

As described above, it is possible to execute various services for the user by using the reception system described with reference to FIGS. 1 and 2. Here, the configuration of the mobile terminal 2 owned by the user will be described. The mobile terminal 2 is a smart phone, a tablet terminal, or the like, and is a terminal owned and owned by the user and used by the user.

FIG. 4 is a block diagram showing the configuration of the mobile terminal 2 according to this embodiment. The mobile terminal 2 includes a CPU 21a as a control unit, a ROM 21b, a RAM 21c, an image processing unit 21d, and a sound processing unit 21e. It also has a non-volatile storage unit 22 such as a flash memory. In addition to the various communication means such as the mobile communication unit 26a, the wireless LAN communication unit 26b, and the Bluetooth communication unit 26c (short-range wireless communication unit) via the interface 23, an input switch 27 is connected, and the control unit is connected. It is possible to control by.

A touch panel monitor 25 and a camera 24 are connected to the image processing unit 21d. The touch panel monitor 25 includes a display unit 252 that displays various kinds of information to the user, and a touch panel 251 that receives a touch operation by the user. The camera 24 is arranged on the back surface or the like of the mobile terminal 2 and can take a still image and a moving image. It should be noted that the cameras 24 may be arranged in plural not only on the back surface but also on the front surface. A speaker 28a that transmits auditory information to the user and a microphone 28b that acquires acoustic information are connected to the voice processing unit 21e. The touch panel monitor 25 and the input switch function as a mobile terminal side user interface for the user who operates the mobile terminal 2.

FIG. 5 is a diagram showing an initial screen displayed on the touch panel monitor 12 of the reception device 1 according to the present embodiment. On the initial screen, buttons 121a and 121b for asking the user whether the user is an outpatient or a visitor, patient-related persons (patients themselves and relatives of patients, or nursing services for patients) (For any of the users), a button 121c for performing face registration, a button 121d for adding a function to the smartphone (mobile terminal 2), and a button 121e for switching to a language other than Japanese are displayed. There is. When the user selects one of the buttons 121a to 121e, the corresponding process is executed.

In a conventional medical facility, it is necessary to insert a medical examination ticket into the reception device 1 when performing return visit reception, and the patient who receives the return visit must carry the medical examination ticket. Normally, a medical examination ticket is issued for each medical facility, so a user who needs to be examined at a plurality of medical facilities must carry a plurality of medical examination tickets, which is troublesome to handle. Therefore, in this embodiment, face authentication is used instead of using the medical examination ticket. Face authentication can be performed by registering a face and performing face registration processing that is associated with the patient ID in advance. By using the face authentication, the patient can perform reception at the reception device 1 without having a medical examination ticket. In the present embodiment, face authentication is used as a biometric authentication method, but it is not limited to face authentication, and various biometric authentication such as fingerprint authentication, iris authentication, vein authentication, voice authentication, etc. may be used. Is possible.

By the way, some patients to be examined may be accompanied by a caregiver because they are children, are in wheelchairs, cannot walk on their own, or have dementia. .. In such a case, it is considered difficult for the patient to operate the reception apparatus 1, and the caregiver may perform the operation. The caregiver may be a patient's relatives (parent, child, relative), a friend, a business worker who cares for the patient, or the like. In the conventional reception device 1 using a medical examination ticket, for example, when the parent of the caregiver is a patient, the medical examination ticket is taken from the parent who is the patient and the reception device 1 is operated to perform reception. The same applies to the case of a business worker, in which the patient receives a medical examination ticket from the patient for reception.

In biometric authentication including face authentication, it is usual to authenticate the person. However, there are situations in which the patient himself cannot face the reception apparatus 1 and perform an operation based on the above-mentioned circumstances peculiar to the medical facility. Therefore, the reception system of the present embodiment is characterized by having at least one of the following three configurations.
-Associating a certain patient with another user other than the face-recognizable patient.
-Associating a plurality of users (may include patients) capable of face authentication with a certain one patient.
-In the case of the above-mentioned worker, there are cases where a plurality of patients are assisted in one medical facility. Therefore, a certain user (for example, a worker) may be associated with a plurality of patients so that face recognition is possible.

First, the face registration processing according to this embodiment will be described with reference to FIGS. 6 and 7. FIG. 6 is a flowchart showing the face registration processing (on the reception device side) according to this embodiment, and FIG. 7 is a flowchart showing the face registration processing (on the management computer side) according to this embodiment.

Here, the data structure of various information used in the reception system of this embodiment will be described. FIG. 8 shows various data configurations used in the reception system according to the present embodiment. In the management computer 3, basic patient information registered in advance is recorded at the timing of the first medical examination or the like. As shown in FIG. 8(A), as the patient basic information, information about the patient as a user such as patient ID, facility ID, name, address, sex, date of birth, personal identification information, insurance card information, etc. is registered. ing. Here, in the present embodiment, the patient ID and the medical facility ID are combined and used as the system ID. The reception system of this embodiment is premised on being usable in a plurality of medical facilities. Therefore, it is possible to specify the medical facility and the patient by referring to the system ID that is a combination of the patient ID and the medical facility ID. The system ID is not limited to the combination of the patient ID and the medical facility ID, and may be appropriately set so that the medical facility and the patient can be specified.

The personal identification information is various information that can identify an individual, such as a driver's license presented by a patient at the time of first reception of a medical examination, a number written on a my number card, or a copy image thereof. The insurance card information includes an insurance card type, an insurance card number, an expiration date, and the like.

Reservation information regarding medical treatment reservations is also registered in the management computer 3. As shown in FIG. 8B, the reservation information includes a patient ID, a reservation date, a reservation time zone, a medical department ID, and a doctor ID. In the present embodiment, the reservation form is such that the reservation date and the reservation time zone are designated, but the reservation form is not limited to such a form, and only the reservation date or the reservation date and the reservation time It is possible to adopt various forms such as, and the information in the reservation information will be appropriately changed according to the reservation form of the medical facility.

The face registration processing is started by operating the button 121c described as the patient-related person face registration described in FIG. When the face registration process is started, the touch panel monitor 12 displays a consultation ticket reading guide screen for prompting the insertion of the consultation ticket (S101).

In addition, in this embodiment, in addition to the card-type medical examination ticket, the mobile terminal 2 such as a smartphone can be used instead of the medical examination ticket. In that case, the user downloads the program (app) to the mobile terminal 2 and registers information regarding the medical examination ticket in the program (function addition processing described later). The program is executed on the mobile terminal on which the registration of the medical examination ticket is completed, and information about the medical examination ticket (patient ID, etc.) is displayed as a two-dimensional barcode (code information) on the screen of the mobile terminal, and the two-dimensional barcode of the reception device 1 is displayed. The reader 15b makes it possible to accept the information by reading it.

FIG. 10 is a diagram showing a consultation ticket reading screen according to the present embodiment. On the consultation ticket reading guide screen, reading of a card-type consultation ticket or reading of a two-dimensional barcode displayed on the mobile terminal 2 (smartphone) is guided. Further, a button 122a described as face registration and a button 122b described as cancel are displayed. When the card type or the reading of the medical examination ticket by the mobile terminal 2 is completed (S102: Yes) and the face registration start operation is performed by operating the button 122a (S103: Yes), the image capturing by the camera 13a is started. (S104). When the button 122b is operated on the consultation ticket reading guidance screen (not shown), the face registration process is terminated and the initial screen is displayed again.

The camera 13a is oriented in a direction to photograph the face of the user who faces the reception device 1 and operates. The reception apparatus 1 acquires face authentication information from the video information captured by the camera 13a. As the face authentication information, various forms such as video information, a feature amount of a face extracted from the video information, or video information and a feature amount can be adopted. If face recognition is not possible, such as when wearing a mask or wearing sunglasses, it is determined that face recognition information cannot be acquired (S106: No). When acquisition of the face authentication information sufficient for face authentication is completed from the video information captured by the camera 13a (S106: Yes), an attribute selection screen is displayed (S107).

On the other hand, when the face authentication information necessary for performing the face authentication cannot be acquired and the predetermined timeout time has elapsed (S105: Yes), an error screen is displayed on the touch panel monitor 12 (S114), and the user is added. A confirmation screen is displayed (S112). Alternatively, the items necessary for acquiring the face authentication information may be displayed on the touch panel monitor 12, and the acquisition of the face authentication information may be continued.

In the present embodiment, as described above, even a user (caregiver) other than the patient corresponding to the medical examination ticket can perform face registration instead of the patient or in addition to the patient. Therefore, in the face registration processing of the present embodiment, the user who has performed the face registration can register the attribute information indicating who is the patient. The registered attribute information can be referred to by an employee of the medical facility in the reception system in addition to the check-in processing described later. Therefore, in a medical facility, it is possible to use the information processing device that is communicatively connected to the reception system and refer to the attributes of the caregiver accompanying the patient who received it on the day.

FIG. 10 is a diagram showing an attribute selection screen according to the present embodiment. On the attribute selection screen, a photographed image display field 123a for displaying video information photographed by the camera 13a, an attribute selection button 123b, a button 123d described next, a button 123c described as cancel, for the user to confirm. Is displayed. The user uses the attribute selection button 123b to select his attribute for the patient. It should be noted that in the present embodiment, the mode is selected from among predetermined attributes, but it is possible to allow the user to input the attribute in a free mode by using an input means such as a soft keyboard or a numeric keypad. Good. For example, when a plurality of patients are in charge of one medical facility like a trader (worker), by using a management number assigned to the patient by the trader, check-in processing and the like described later can be performed. It becomes possible to easily select a target patient. Further, the number of attributes is not limited to one, and a plurality of attributes may be selected.

After the attribute is selected and the button 123d is operated, that is, when the attribute selection is completed (S108: Yes), the auxiliary authentication information registration screen is displayed. FIG. 13 is a diagram showing an auxiliary authentication information registration screen according to the present embodiment. In this embodiment, a contact telephone number is used as auxiliary authentication information in addition to face authentication as biometric authentication. As the auxiliary authentication information, not only the contact telephone number but also various information such as the date of birth and the password determined by the user can be used. By using the auxiliary authentication information, it is possible to improve the accuracy of authentication and reduce the burden of face authentication. That is, by using the face authentication and the authentication based on the auxiliary authentication information together, it is possible to improve the authentication accuracy without using the highly accurate face authentication. Further, it is possible to reduce the processing load of the management computer 3 or the like that executes face authentication by performing face authentication or the like on the patient on the database for which the auxiliary authentication information matches.

An input display field 124a, a ten-key pad 124b, and buttons 124c and 124d are displayed on the auxiliary authentication information registration screen. The user operating the reception apparatus 1 uses the ten-key pad 124b to input his/her contact telephone number. The input contact telephone number is displayed in the input display field 124a. The user who has completed the input completes the registration of the supplementary authentication information by operating the button 124c described as registration (S110: Yes). By operating the button 123d described as “cancel” on the auxiliary authentication information registration screen, it is possible to return to the previous screen or exit the face registration process.

After the registration of the auxiliary authentication information is completed, the accepting device 1 transmits the registration authentication information to the management computer 3 (S111). 10A and 10B, the data structure of registration authentication information is described. The registration authentication information is registered as a database in the storage unit or the like of the management computer 3. In the registration authentication information, the face authentication information, auxiliary authentication information, and attribute information acquired in this registration process are associated with the patient ID. The face registration information of this embodiment uses a face ID and is associated with basic information and bridge information. FIG. 10A is an example in which a user who has registered one face is associated with a plurality of patients. Further, FIG. 10B is an example in which a plurality of users who have registered faces are associated with one patient.

As described above, in this embodiment, it is possible to register a plurality of users with respect to one patient or to register a plurality of patients with respect to one user. Therefore, in the face registration process executed by the accepting apparatus 1, it is possible to perform face registration for a plurality of users in one process. After transmitting the registration authentication information (S111), the user addition confirmation screen is displayed. By displaying (S112), other users can also perform face registration. That is, it is possible to perform face registration of a plurality of users such as the person himself, his relatives, a trader (business worker), etc. by one face registration process.

FIG. 14 is a diagram showing a user addition confirmation screen according to the present embodiment. On the user addition confirmation screen of this embodiment, a photographed image display field 125a and buttons 125b and 125c are displayed. The image captured by the camera 13a is displayed in the captured image display field 125a. The user can confirm that the face can be registered by visually checking the photographed image display field 125a. When the face registration of another user is continuously performed, the button 125b described as YES is operated (S113: Yes). In that case, the process returns to S104 to start the face registration of another user. On the other hand, if the button 124c labeled No is operated (S113: No), the series of face registration processing ends.

FIG. 7 is a flowchart showing a face registration process on the management computer 3 side, which is executed corresponding to the face registration process on the reception device 1 side described in FIGS. 7 and 6. When the management computer 3 receives the registration authentication information transmitted from the accepting device 1 to the management computer 3 (S112) (S151: Yes), first, the basic information portion described with reference to FIGS. 10A and 10B. Is searched (S152). If the registration authentication information (face authentication information, auxiliary authentication information) acquired by the reception device 1 is not registered this time (S153: No), since the face registration of the user is not performed, FIG. Registration authentication information is registered in the form as shown in FIG.

On the other hand, when the registration authentication information (face authentication information, auxiliary authentication information) acquired by the reception device 1 has already been registered this time (S153: Yes), whether the matched user is associated with the patient or not. That is, it is confirmed whether the bridge information matches (S155). If there is no matching bridge information (S155: No), only the bridge information part is additionally registered as registration authentication information (S157). For the basic information part, the already registered information is used, or the information acquired this time is updated. On the other hand, if there is no matching bridge information (S155: Yes). The error information is transmitted to the reception device 1 that has transmitted the registration authentication information (S156). Receiving the error information, the accepting device 1 displays that the user who tried to register a face for a certain patient this time has already registered for the patient (not shown in FIG. 6).

As described above, in the present embodiment, when registering in the management computer 3, since the registration authentication information is separately registered into the basic information and the bridge information, duplication in the basic information portion including the face authentication information is avoided, and the data amount is reduced. It is possible to reduce the number of problems, suppress the occurrence of troubles caused by registering a plurality of face authentication information, and realize efficiency in face authentication.

Next, the check-in process using the face authentication process in this embodiment will be described. Here, the check-in process corresponds to the process performed by the return visit reception performed when the patient who once visited the hospital returns. When the button 121a described as an outpatient on the initial screen of FIG. 5 is selected, the screen transitions to the outpatient screen shown in FIG. On the outpatient screen, buttons 126a to 126d described as new patient reception, return reception, medical fee payment, reservation request, and button 126e for returning to the initial screen are displayed.

Here, various services displayed on the buttons 126a to 126d will be described. When the button 126a (new patient reception) is touch-selected, the new patient reception process is started for a new patient, that is, a patient who first comes to this medical facility. In the new patient reception process, the scanner 15a of the reception device 1 is used to read a personal identification card such as a my number card, a driver's license, and an insurance card. On the touch panel monitor 12, a display for notifying the user to wait until the registration is completed is displayed, and the new patient reception processing on the reception device 1 side is completed. The read information is transmitted to the management computer 3 and is registered as basic patient information in the database of the medical facility through the work of an clerk or the like.

The process started by touch-selecting the button 126c (receipt reception) is a process (check-in process) of accepting medical treatment at the second and subsequent medical examinations at the medical facility. The return-accepting process of the present embodiment is intended for users who have made medical appointments in advance, such as at the time of previous medical examination, but may accept users who have not made appointments. Therefore, the recurrence acceptance process will be referred to as a check-in process.

The process started by touch-selecting the button 165b (payment of medical expenses) is a process for paying the medical expenses to the user who has completed the medical treatment. Although the accepting device 1 of the present embodiment is capable of making payment by credit card using the card reader 14, it may be possible to provide a cash handling function and make payment by cash. The process started by selecting the button 126d (reservation request) is a process for reserving the next medical treatment date and time.

The face authentication processing according to the present embodiment can be used not only for the check-in processing but also for various kinds of processing conventionally used for patient authentication using an examination ticket. As such a process, for example, a medical fee payment process executed when the button 126b is operated, a reservation request acceptance process executed when the button 125d is operated, or the button 121b of FIG. 5 is operated. The process at the time of accepting an interview is performed by doing so.

FIG. 16 is a flowchart showing the check-in process according to this embodiment. The check-in process is a process executed by the reception device 1 and is performed by the user facing the reception device 1 and operating the touch panel monitor 12 or the like. The check-in process is started by operating the button 126c (return reception) on the outpatient screen in FIG.

When the check-in process is started, a guide screen is displayed on the touch panel monitor 12 (S201). The guide screen prompts the user to select one of two check-in methods. Here, the two types of check-in methods are check-in by inserting a medical examination ticket as in the past, or check-in by face authentication information registered in advance in face registration processing without using the medical examination ticket. Is. When the medical examination ticket is inserted (S202: medical examination ticket), the card reader 14 identifies the patient by reading the patient ID stored in the medical examination ticket (S203), and accepts the patient. To execute.

On the other hand, when face authentication is selected on the guidance screen (S202: face authentication), the first face authentication process of identifying the patient using the face of the user facing the reception device 1 without using the examination ticket (S300). ) Is executed.

FIG. 17 is a flowchart showing the first face authentication processing according to this embodiment. When the first face authentication processing (S300) is started, the reception apparatus 1 starts shooting with the camera 13a (S301). Then, the auxiliary authentication information input screen is displayed (S302). FIG. 18 shows an auxiliary authentication information input screen according to this embodiment. The auxiliary authentication information input screen includes a captured image display field 127a, an input display field 127b, a ten-key pad 127c, and buttons 127d and 127e. The captured image display field 127a displays the image captured by the camera 13a and guides the user to an appropriate position. In the input display field 127b, the number (contact telephone number in this example) entered with the ten keys 127c is displayed.

The user who has finished inputting the contact telephone number as the input auxiliary information operates the button 127d labeled “confirm” to confirm the auxiliary input information. When the auxiliary input information is input (S303: Yes), the management computer 3 is inquired based on the input auxiliary authentication information and the image captured by the camera 13a (S304). The management computer 3 executes authentication based on the received auxiliary authentication information and the video image captured by the camera 13a. Specifically, in the registration authentication information described with reference to FIGS. 10A and 10B, the first authentication whether the face authentication information corresponding to the image captured by the camera 13a this time is registered. Then, the second authentication is executed based on the auxiliary authentication information indicating whether the auxiliary authentication information matching the input auxiliary authentication information is registered this time. In the authentication in the management computer 3, the processing load on the management computer 3 is reduced by first executing the second authentication.

The authentication result in the management computer 3 is transmitted to the acceptance device 1. The reception device 1 that has acquired the authentication result (S305: Yes) confirms the content of the authentication result (S306). When the authentication is successful (S306: Yes), it is determined in the authentication result whether the target patient is singular (S307: No) or plural (S307: Yes). As described with reference to FIG. 10A, in this embodiment, it is possible to associate a plurality of patients with one user who can perform face authentication. Therefore, when the authenticated user has a plurality of patients (S307: Yes), the associated plurality of patients are presented as candidates to be selected by the user.

FIG. 19 is a diagram showing a target patient selection screen according to the present embodiment. Patient selection buttons 128a to 128d are displayed on the target patient selection screen. On each of the patient selection buttons 128a to 128d, the name of the patient and the relationship with the authenticated user (the user operating the reception apparatus 1) are displayed. This relationship is based on the attribute information selected or input on the attribute selection screen of the registration process. The user confirms the names and relationships displayed on the patient selection buttons 128a to 128d and selects the patient to be examined this time (S309: Yes). The selected patient is determined as the target patient to receive the medical examination this time (S310).

Returning to FIG. 16, the check-in process after the target patient is determined will be described. The process after the target patient to be examined is specified by reading the examination ticket (S203) or the first face recognition process (S300) will be described. The reception device 1 transmits a check-in request including the patient ID of the target patient identified in the reading of the examination ticket (S203) or the first face authentication processing (S300) (S204).

Upon receiving the check-in request, the management computer 3 refers to the patient ID included in the check-in request and searches for the corresponding reservation information. If there is no reservation information corresponding to the patient ID, or if the reservation date of the reservation information corresponding to the patient ID is not the current day, error information is transmitted to the reception device 1. When the error information is received (S205: Yes), the acceptance device 1 displays a check-in error screen notifying that the reservation cannot be accepted because there is no reservation on the touch panel monitor 12 (S215).

On the other hand, in the management computer 3, when there is reservation information corresponding to the patient ID and the reservation date is the current day, the management computer 3 transmits the reservation confirmation information to the reception device 1. The reservation confirmation information includes various information based on the reservation information, that is, a patient name, a reservation date, a reservation time zone, a department name, a doctor name, and the like. When receiving the reservation confirmation information (S206: Yes), the reception apparatus 1 displays a check-in confirmation screen based on the received reservation confirmation information (S209). In this embodiment, before displaying the check-in confirmation screen, the infrared camera 13b is used to perform a temperature measurement process for measuring the body temperature of the user.

As described with reference to FIG. 2, the reception device 1 is provided with the infrared camera 13b capable of capturing an image of the range including the user. Temperature measurement is performed using this infrared camera 13b (S207). In the present embodiment, the body temperature in the vicinity of the temple of a human being who can accurately perform temperature measurement is used. Further, in order to improve the accuracy of the temperature measurement result, the body temperature in the vicinity of the temple is corrected based on a wide range of body temperature distribution of the face and used as the temperature measurement result. Further, in order to accurately detect the temple position, the camera 13a may be used together. When the temperature measurement result is not normal (S208: No), that is, when it is considered to be high fever due to the onset of influenza or the like, a fever caution screen is displayed on the touch panel monitor 12 (S213), and fever caution information is sent to the management computer 3. It is transmitted (S214).

The heat generation caution screen displays that the user requests the user to move to an isolated space or the like due to heat generation. Further, the management computer 3 that has received the fever caution information notifies the employee that the patient with the fever abnormality has occurred, including the identification information of the reception device 1. In this way, it is possible to suppress nosocomial infections by taking measures at the time of check-in, such as isolating the user who has developed influenza at the time of the return visit. It should be noted that the reception device 1 may be provided with notifying means for notifying not only the heat generation caution screen but also the periphery of the reception device 1. For example, it is conceivable to provide a notification light on the upper part of the reception device 1 and to provide a notification means for turning on the notification light to notify an employee standing by around the reception device 1 or a voice notification. .. Further, the temperature measurement by the infrared camera 13b is not limited to being performed at the timing of this embodiment, and may be performed at an appropriate timing within the check-in processing.

On the other hand, when the temperature measurement result is normal (S208: Yes), the reception device 1 displays a check-in confirmation screen on the touch panel monitor 12 based on the received reservation confirmation information (S209). FIG. 20 is a diagram showing a check-in confirmation screen according to the present embodiment. On the check-in confirmation screen, a consultation content display field 129a including a medical department, a doctor name, and a reserved time zone, a cancel button 129b, and a confirmation button 129c are displayed. As can be seen from the check-in confirmation screen shown in FIG. 20, in this embodiment, it is possible to visit a plurality of departments at one visit. In that case, a check-in confirmation screen is displayed based on the corresponding plurality of reservation information (S209). If there is no problem with the examination content, the user operates the confirmation button 129c to confirm the examination content on the day (S210: Yes). On the other hand, in the case of wanting to cancel the contents of the medical examination, it is possible to cancel the reservation corresponding to the item by selecting the item to be canceled (medical department etc.) and operating the cancel button 129b.

When the confirmation button 129c is touch-operated (S210: Yes), the reception apparatus 1 transmits the confirmation instruction information to the management computer 3 (S211). Based on the reception of the confirmation instruction information, the management computer 3 adds the corresponding reservation information as consultation information to the medical treatment queue. The medical treatment queue is provided for each doctor in the corresponding medical department, and the medical treatment is basically performed based on this medical treatment queue in order. Further, the acceptance device 1 prints out the acceptance completion vote for the user using the receipt printer 15 (S212).

On the reception completion vote, the medical examination department, the doctor's name, the reservation time zone, and the waiting number corresponding to the reception order and the two-dimensional bar code (code information) included in the reservation information are printed. In addition, as in the present embodiment, when a plurality of consultation departments are used for consultation, a waiting number may be issued for each consultation department. Here, the two-dimensional bar code printed on the acceptance completion form is information for confirmation by an information processing device (not shown) arranged in the medical department at the time of consultation. The information processing apparatus arranged in the medical department is communicatively connected to the management computer 3 via the LAN 51, and it is possible to confirm the identity of the person using the two-dimensional bar code read by the information processing apparatus.

In addition, in the present embodiment, when the first face authentication process (S300) is performed, the attribute information of the user who performed the first face authentication process (S300) is added to the confirmation instruction information. By referring to the attribute information, it is possible to easily confirm who the person accompanying the patient is on the day. For example, when referring to information (name, etc.) about a patient in an information processing device installed in a medical department to be examined, a notification for notifying (displaying) the relationship between the patient and the user who is assisting based on this attribute information By executing the process, the medical facility side can easily confirm the relationship between the patient and the caregiver. For example, in the situation where you want to explain the medical condition only to the patient's relatives (parent, child, spouse), the medical facility side can easily understand the relationship between the patient notified by the attribute information and the user who is assisting. However, it becomes possible to judge whether the medical condition can be explained. The attribute information may be included in the two-dimensional barcode (code information) of the acceptance completion vote instead of being added to the confirmation instruction information to perform the notification process.

For example, when the target patient is a child and the user who has authenticated with the reception apparatus 1 is the parent, the information processing apparatus installed in the medical department is notified that the target patient is the parent. In this case, at the time of registration processing, the relationship of the patient as seen from the user who performs authentication (child in this case), but when notifying at the medical facility side, the relationship of the user who performs authentication as seen from the patient (parent in this case). ) Is different. In this way, by making the relationship selected in the registration process different from the form notified in the notification process, it becomes easy to select attribute information in the registration process, and the target process grasps the relationship to the patient on the medical facility side. Can be made easy.

Next, a function adding process for adding a function to the mobile terminal 2 in the present embodiment will be described. The process started by selecting the button 121d (addition of function to smartphone) in the initial screen described with reference to FIG. 5 is executed by selecting the function for the program (app) executed by the mobile terminal 2 owned by the user. This is a process to be added. The user downloads the program used in the medical institution to the mobile terminal 2 through the Internet line and uses it. As a basic function of this program, it is possible to acquire basic information such as the location of various medical institutions, or use a waiting number to notify the current progress of medical treatment at each medical institution.

In addition, as additional functions that can be executed by the mobile terminal 2, various functions described in FIG. 16, such as re-receipt reception (check-in processing) executed by the reception device 1, medical fee payment, reservation request, visit invitation, etc. are added. It is possible to do. Such an additional function needs to specify a user (patient etc.) who uses the mobile terminal 2, and needs to handle important information such as a patient ID on the mobile terminal 2 side. Therefore, incorporating such an additional function as the basic function of the program is not preferable for ensuring security. Alternatively, it is not preferable in terms of security to add a function only with the mobile terminal 2. There is a possibility that it may be used illegally by exploiting security problems. Therefore, in the present embodiment, the reception device 1 is used when adding a function to a program (application) executed by the mobile terminal 2.

FIG. 21 is a flowchart showing the function addition processing according to this embodiment. This process is started by selecting the button 121d described as adding a function to a smartphone in FIG. 5 in the reception device 1. When the processing is started, a screen prompting the insertion of the medical examination ticket is displayed on the touch panel monitor 12. When the user inserts the examination ticket into the card reader 14 (S401: Yes), the card reader 14 reads the patient ID stored in the examination ticket (S402). In addition, the reception device 1 starts shooting using the camera 13a (S403). Note that shooting (moving images or still images over a plurality of times) by the camera 13a is continuously performed, and shooting information that is the best shot suitable for confirming the person in the shooting is selected later.

The reception apparatus 1 transmits the read patient ID to the management computer 3, and acquires the patient basic information corresponding to the patient ID from the management computer 3 (S404). The basic patient information to be acquired may not be all the information included therein but may be necessary partial information. Then, the touch panel monitor 12 displays a function addition confirmation screen including a two-dimensional bar code to be read by the mobile terminal 2 (S405). This two-dimensional bar code contains information for identifying the patient. The patient ID in the two-dimensional barcode is preferably encrypted. The user causes the camera 24 of the mobile terminal 2 to read the two-dimensional bar code displayed on the touch panel monitor 12 using the activated program (app). FIG. 8C1 is one form of the data configuration included in the two-dimensional barcode, and identifies the patient ID, the medical facility ID (system ID), the name, the date of birth, and the reception device 1 being used. The device ID for this is included. The two-dimensional barcode read by the camera 24 is decrypted by the mobile terminal 2 and converted into information. In the read information, information necessary for using the mobile terminal 2 as a medical examination ticket, such as a patient ID, a medical facility ID, a name, and a date of birth, is stored (registered) in the mobile terminal 2 as medical examination ticket information. It

22 and 23 are diagrams showing various screens of the mobile terminal 2 according to the present embodiment. 22A is an initial screen displayed on the touch panel monitor 25 immediately after the program is started up in the mobile terminal 2. Various buttons 251b to 251j are displayed on the initial screen in addition to the currently selected medical facility name 251a. The button 251b is a button for using the mobile terminal 2 as a medical examination ticket, and by using the mobile terminal 2 as a medical examination ticket that can be received by the reception device 1 by completing the function addition processing described in FIG. It becomes possible to do. In the mobile terminal 2, there are two modes, that is, a mode in which a two-dimensional bar code as a medical examination ticket is displayed on the touch panel monitor 25 for check-in and a mode in which the wireless function of the mobile terminal 2 is used for check-in.

The button 251c is a button for paying medical expenses, and the user can select payment by credit card, payment at a convenience store, or the like by operating the button 251c after medical treatment. Therefore, using this function, it is possible to pay the medical expenses without having to stop at the reception device 1 or the reception.

The button 251d is a button for the user who is hospitalized to send mail to the relatives, friends, acquaintances, etc., for issuing the visit certificate. Using this function, a user who is hospitalized can send an email to a relative, friend, acquaintance, or other person who is permitted to visit. Information for issuing the visit certificate such as a two-dimensional bar code, a WEB address for obtaining the two-dimensional bar code, and a visit permit number (visit permit information) is attached to the mail. The visitor can receive the visit certificate permitting the visit by reading or inputting this information at the reception device 1.

The button 251e is a button for switching target medical facilities. The program of this embodiment can be used in a plurality of medical facilities. By operating the button 251e, available medical facilities are displayed, and a target medical facility can be selected. After the selection, the medical facility name 251a is changed to the selected one.

The button 251f is a basic function of the program and is used to notify the progress of medical treatment in the selected medical facility. By operating the button 251f, the progress status of each medical department regarding the currently selected medical facility is displayed. In this embodiment, a waiting number is used, and a waiting number queue is displayed for each medical department as a progress status.

The button 251g is a function that can be executed after the function addition process is performed, and can reserve the next medical treatment date and time for the selected medical facility. Note that, in the initial screen of FIG. 22A, the button indicated by the broken line has a function which is not used in the selected medical facility. This takes into account different specifications for each medical facility. In this embodiment, the reservation request by the button 251g cannot be used.

The button 251h is a button for referring to various information provided from the medical facility or the reception system. For example, when referring to the progress status of the button 251f, by registering his/her waiting number, a pop-up notification is displayed on the mobile terminal 2 each time the progress status is updated. The user can confirm the details by operating the button 251h. The button 251i is a button for referring to how to use this program (application). The button 251j is a button for switching to a multi-language other than Japanese.

Here, the screen transition when the button 251b used for the function addition process is operated will be described. When the mobile terminal 2 is used instead of the medical examination ticket, it is necessary to execute function addition processing with the reception device 1 and register information such as a patient ID in the mobile terminal 2. When information is not yet registered in the mobile terminal 2 when the button 251b is operated, first, the terms of use of FIG. 22B are displayed. In FIG. 22B, only "Terms of Use" is displayed, but in practice, details of the terms of use will be displayed here. Further, a button 252a described as "agree" and a button 252b described as "not agree" are displayed. The user who agrees with the displayed terms of use operates the button 252a and proceeds to the screen of FIG.

FIG. 22C is a screen in a state where the medical examination ticket is not yet registered. The user operates the button 253 described as registration of medical examination ticket to proceed to the screen of FIG. 23(D). FIG. 23D is a screen that prompts an operation on the reception device 1 side. Further, on this screen, a button 254 described as "read two-dimensional barcode" is displayed. By operating this button 254, the screen transitions to the reading screen of FIG. On the reading screen, a monitor field 256a for displaying the image being taken by the camera 24 and a cancel button 256 are displayed. While confirming the video on the monitor field 256a, the user shoots the function addition confirmation screen displayed in the processing of S405 during the function addition processing executed by the reception apparatus 1.

The mobile terminal 2 that has read the two-dimensional barcode uses the mobile line communication unit 26a to transmit the registration request information to a management server (not shown) on the Internet. FIG. 8D is a diagram showing a data structure of registration request information. The patient ID, the medical facility ID, and the terminal ID associated with the mobile terminal 2 are transmitted to the registration request information. The terminal ID may be an ID unique to the mobile terminal 2 or an ID unique to a program (app). The management server receives the registration request information from the mobile terminal 2 via the mobile network or the Internet, and transmits the registration request information to the management computer 3 of the reception system that uses the reception device 1 having the device ID. The management computer notifies the acceptance device 1 having the device ID included in the registration request information that the registration request information has been received.

When the reception device 1 confirms that the management computer 3 has received the registration request information (S406: Yes), the reception device 1 displays a moving image continuously captured by the camera 13a or a plurality of still images. The best shot in which the user's face can be appropriately photographed is selected from the inside, recorded as photographing information (S407), and transmitted to the management computer 3 (S408).

The management computer 3, which has received the shooting information, registers the mobile terminal registration information based on the registration request information and the shooting information received earlier. FIG. 8(E) shows the data structure of the mobile terminal registration information. The mobile terminal registration information includes a patient ID, a medical facility ID, a terminal ID of the mobile terminal 2, a device ID of the accepting device 1, a registration date and time indicating registration date and time, and imaging information captured by the camera 13a. The mobile terminal registration information is used to identify whether the mobile terminal 2 is a proper one by using the terminal ID included in the mobile terminal registration information. Then, if a trouble or the like occurs after the addition of the function, by referring to the mobile terminal registration information, it becomes possible to use it as a history of who registered the function and when.

On the other hand, when the reception apparatus 1 cannot receive the terminal ID (or application ID) of the mobile terminal 2 (S406: No), the process ends after a fixed time-out period (S409: Yes). In that case, the shooting information taken by the camera 13a is discarded (S410).

As described above, in the present embodiment, when adding various functions to the mobile terminal 2, the user needs to face the reception apparatus 1 and perform an operation. Therefore, various problems such as security and unauthorized use when using the mobile terminal 2 can be suppressed. In particular, the mobile terminal 2 stores information such as a patient ID and a system ID that requires accuracy and confidentiality. However, as in the present embodiment, the reception system provides these information to the mobile terminal 2. By doing so, it becomes possible to ensure accuracy and confidentiality.

In the present embodiment, it is described that the reception device 1 displays the two-dimensional barcode and the mobile terminal 2 reads and transmits various information, but instead of such a form, the mobile terminal 2 side is replaced. , A two-dimensional barcode including the terminal ID (or application ID) may be displayed and read by the two-dimensional barcode reader 15b on the reception device 1 side. In that case, from the reception system side to the mobile terminal 2 specified by the terminal ID, various information necessary for adding the function (at least the patient required to specify the user by using the mobile network) ID, medical facility ID, etc.) will be transmitted.

Alternatively, the two-dimensional barcode does not include the information as shown in FIG. 8(C1), but the device ID of the accepting device 1 as shown in FIG. 8(C2) is used as the authentication information. May be included. The mobile terminal 2 receiving the two-dimensional bar code transmits the mobile terminal authentication information to the reception system through the mobile network or the Internet, and the reception system receives information necessary for adding a function (at least identifies the user). The patient ID, the medical facility ID, etc., which are required for the above will be received. According to such a form, it is not necessary to display confidential information in a two-dimensional barcode, and it is possible to suppress information leakage due to photographing and copying of the two-dimensional barcode.

In addition, in the present embodiment, the basic patient information includes biometric authentication information. When the information necessary for face recognition is adopted as the biometric information, the registered biometric information is compared with the imaging information included in the mobile terminal registration information, and the matching rate is low. In the case of a user different from the biometric information of the information, it is possible to take no measures such as not adding the function or notifying the management computer 3 of an alert. In addition, when the user who operates does not face the proper direction, or when the best shot in S407 cannot be selected because the user wears a mask or sunglasses, the proper direction for the user is selected. The best shot may be obtained by instructing to turn to, or instructing to remove the mask or sunglasses. Further, when the best shot cannot be acquired, it is also possible to take measures such as not adding a function or notifying the management computer 3 of an alert.

Next, the meeting invitation process that can be executed by the mobile terminal 2 that has completed registration by the function addition process will be described. The visit invitation process is a process for a patient who is in the hospital or is scheduled to be hospitalized to use the mobile terminal 2 of his/herself to invite the visit. FIG. 9 shows the data structure of various information regarding visits. FIG. 9F shows hospitalization-related information indicating the hospitalization status of the patient. The hospitalization related information includes a patient ID for identifying a patient, a medical facility ID, a hospitalization start date, and a hospitalization end date. The hospitalization start date and hospitalization end date may be scheduled. When the hospitalization end date is undecided, no information is recorded on the hospitalization end date, or information indicating that it is undecided is recorded. The sickroom number is information (a sickroom identification information) for identifying a sickroom in which a patient stays during hospitalization.

In addition, the hospitalization-related information of this embodiment includes access restriction information and necessity of identification. The visit restriction information is information for specifying a range that can be visited, and is information that defines the attributes of the visitor, such as being limited to the patient's relatives or being within the first-degree relative of the patient. In addition, whether or not the identification is required is information that defines whether or not an identification such as a driver's license or a health insurance card is required at the time of visit. For example, when a politician or entertainer is hospitalized, a person unrelated to the patient may try to enter the hospital room. In this embodiment, the visit permission number is used, but if the visit permission number is leaked, it is possible to easily enter the hospital room. Whether or not the identification is required corresponds to a flag for increasing security at the time of visit, and when the flag is set, the reception device 1 needs to present the identification certificate.

FIG. 24 is a flowchart showing the meeting invitation process according to this embodiment. The visit invitation process is started by operating the button 251d in the initial screen of the mobile terminal 2 described with reference to FIG. When the visit invitation process is started, the patient ID and the medical facility ID stored in the mobile terminal 2 are transmitted to the medical facility reception system (for example, the management computer 3), and the hospitalization determined based on the hospitalization related information is performed. Information indicating whether or not there is a hospitalization plan is received (S501). When a plurality of medical examination tickets are registered in the mobile terminal 2, an inquiry is made by designating the medical examination ticket to be an inpatient.

If the patient who made the inquiry is in the hospital or is scheduled to be hospitalized (S502: Yes), the destination information (e-mail address, telephone number of the mobile terminal 2, etc.) of the visitor can be designated (S503). On the other hand, if the patient is hospitalized or is not scheduled to be hospitalized (S502: No), the visit invitation process is terminated. When designating the destination information of the visitor, the user selects the destination information by referring to the contact information or the like stored in the mobile terminal 2, or directly inputs the destination information and determines the destination information. When the designation of the destination information is confirmed, the meeting invitation confirmation screen is displayed on the touch panel monitor 25 of the mobile terminal 2 (S504).

FIG. 25 is a diagram showing a meeting invitation confirmation screen of the mobile terminal 2 according to the present embodiment. On the visit invitation confirmation screen, a subject name 257a, a destination display field 257b in which an email address as destination information is displayed, a medical facility name 257c who has been hospitalized (or will be hospitalized), an interview permission number 257d, a two-dimensional barcode 257e, Buttons 257f and 257g are displayed. The visit permission number is a number assigned by the mobile terminal 2 or the medical facility reception system side, and the visit certificate can be issued by inputting the visit permission number into the reception device 1. The two-dimensional bar code 257e is information in which the visit permission number is coded, and by causing the two-dimensional bar code reader 257 of the reception apparatus 1 to read the two-dimensional bar code 257e, it is possible to issue the face cancellation. As for the visit permission number as the visit permission information, various types of information can be used privately instead of the number.

The user who confirms the contents of the visit invitation confirmation screen operates the button 257g to send the information of the displayed contents to the destination information when the displayed contents are satisfactory (S506). On the other hand, it is possible to cancel the transmission by operating the button 257f. After confirming the transmission, the mobile terminal 2 transmits the meeting invitation information to the medical facility system (S507). FIG. 9G shows the data structure of the visit invitation information. The visit invitation information includes the patient ID of the patient to be hospitalized, the medical facility ID, the destination information (email address in this case), the issued meeting permit number, the transmission date and time, and the like. On the side of the received medical facility system, the meeting invitation information is stored in, for example, a database managed by the storage unit of the management computer 3.

On the side of the invited visitor, a message having substantially the same content as the visit invitation confirmation screen of FIG. 25 is received. In addition, in the present embodiment, the hospitalization period, the visitable time, and the like are not included, but the information may be included in the content of the invitation to visit. The person who has been invited to the visit (visitor) receives the visit certificate by inputting the visit permit number in the acceptance device 1 or by causing the acceptance device 1 to read the two-dimensional barcode 257e received by the mobile terminal 2 or the like. It becomes possible to do.

FIG. 26 is a flowchart showing the meeting reception process according to this embodiment. The visit reception process is a reception process for a visitor who is invited to visit or a user who has registered a face in advance to visit an inpatient. Conventionally, in various medical facilities, it is often done by simply recording the name of the visitor, the name of the inpatient, the room number, etc. on a piece of paper, which is not reliable in terms of security. In the present embodiment, by performing the visit reception processing by the reception device 1, various visit-related records are issued by issuing an interview certificate to an invited visitor or a user who has already registered a face. It is possible to improve security at the visit.

When the visit reception process is started, the reception device 1 displays a selection screen on the touch panel monitor 12. FIG. 27 is a diagram showing a selection screen according to the present embodiment. In the reception processing of the present embodiment, it is possible to issue the visit certificate in three forms of the visit permission number, the two-dimensional barcode, and the face authentication, and the selection buttons 130a to 130c corresponding to each are displayed. There is. In the visit reception process of the present embodiment, the operating user is photographed by the camera 13a regardless of the result of the visit (S602), and the shooting information as a history is left. Note that the timing of shooting can be appropriately set within the meeting reception process.

When the selection button 130a is operated, that is, when the input of the visit permit number is selected (S603: Yes), the visit permit number authentication process (S604) is executed. In the visit permission number authentication process (S604), the visitor inputs the visit permission number received in advance using the visit permission number input screen (not shown). The reception apparatus 1 transmits the input visit authorization number to the management computer 3. The management computer 3 refers to the visit invitation information, authenticates based on whether or not the input visit permission number is registered, and transmits the result to the reception apparatus 1. Receiving the authentication result, the accepting device 1 executes the first meeting determination process (S630) when the authentication is successful (S605: Yes). On the other hand, if the authentication is not successful (S605: No), an interview error screen (not shown) is displayed on the touch panel monitor 12 (S619).

FIG. 28 is a flowchart showing the first meeting determination process (S630) according to this embodiment. Even if the visit authorization number is successfully authenticated, the inpatient may not be able to visit due to various reasons such as the inpatient being discharged from the hospital or the condition of the inpatient. The first visit determination process (S630) determines whether the visit is possible based on such circumstances. When the process is started, first, the hospitalization start date and the hospitalization end date in the hospitalization-related information stored in the management computer 3 or the like are referred to, and it is determined whether the target patient is hospitalized (S631). ). If the patient is not in the hospital (S631: Yes), it is set that the visit is not possible (S638).

On the other hand, when the target patient is hospitalized (S631: Yes), it is determined whether it is within the visitable time (S632). The visitable time is set by the medical facility side and is set in the reception device 1 or in the management computer 3. If it is not within the visitable time (S632: No), the availability of visitation is set to “not visitable” (S638). On the other hand, when it is within the visitable time (S632: Yes), it is determined whether or not the visitee is restricted. This is determined by referring to the visit restriction information in the hospitalization related information. If the visitor is restricted with reference to the visitation restriction information (S633: Yes), whether or not the visitation is possible is set to "not visitable" (S638).

If the visitor is not restricted (S633: No), it is determined whether or not the identification certificate is necessary by referring to the presence/absence of identification in the hospitalization-related information (S634). If it is determined that the identification card is required (S634: Yes), a message for placing the identification card is displayed on the scanner 15a of the reception apparatus 1, and the process of reading the identification card is executed (S635). If the information described in the identification card is suitable (S636: Yes), the availability of visit is set to allow visit (S637). On the other hand, if the identification certificate does not match (S636: No), it is set that the visit is not possible (S638). Further, when the identification certificate is not required (S634: No), the availability of visit is set to allow visit (S637).

Here, the conformity of the ID card is determined by various kinds of information regarding the ID card (name, address, various numbers of the ID card (for example, driver's license number, license number, insurance card (In case of health insurance number), it can be done by registering it in advance and checking it against it. It may be presented to the patient for the judgment, or it may be possible not to judge the suitability and to only store the read identification card.

Returning to the interview reception process of FIG. 26, when it is determined that the visit is possible as a result of the first visit determination process (S630) (S606: Yes), the temperature measurement process for the visitor (S614) is executed. On the other hand, when it is determined that the visit is impossible (S606: No), the visit error screen (not shown) is displayed on the touch panel monitor 12 (S619).

Although the temperature measurement processing during the check-in processing has been described above, in the present embodiment, not only the patient but also the visitor can be subjected to the temperature measurement processing to prevent the introduction of viruses and the like from outside. It is possible to suppress. In the temperature measurement process (S614), the body temperature of the visitor is measured using the infrared camera 13b, as in the check-in process. In addition, the determination threshold during the visit reception process is set lower than the determination threshold during the check-in process. This is because the patient accepted during the check-in process is a sick person and is accompanied by some fever. In this way, different check thresholds isolate patients with high fever such as influenza during the check-in process, while stricter fever determination during the visit reception process will more reliably suppress nosocomial infections. It is possible to do.

When the temperature measurement result is not normal (S615: No), that is, when the body temperature exceeds the determination threshold value, the fever caution screen is displayed on the touch panel monitor 12 (S618), and the visit error screen is displayed (S619). On the other hand, when the temperature measurement result is normal (S615: Yes), the visitor is inquired about the number of accompanying persons (S616). The inquiry about the number of accompanying persons is made on the touch panel monitor 12, and the visitor touch-inputs the number of accompanying persons. In the present embodiment, only the visitor operates the reception device 1 as a representative, but when accompanied by a companion, the companion is faced to the reception device 1 to perform the temperature measurement process and the camera. The image capturing may be performed by 13a. When the temperature measurement process of the companion is not normal, only the companion, or all of the companion and the companion may be prohibited from meeting on the meeting error screen.

When the inquiry about the number of accompanying persons is completed, the receipt printer 16a prints out the meeting certificate (S617). When accompanied by a companion, the visit certificate may be printed out for the total number of visitors and accompanying persons.

FIG. 31 is a diagram showing an interview certificate 45 according to the present embodiment. On the visit certificate, the medical facility name 45a, the issue date and time 45b, the inpatient name 45c, the room number 45d, and the two-dimensional barcode 45e are displayed. Here, the two-dimensional bar code 45e is information for passing through a gate provided in the medical facility or going to a predetermined floor by an elevator, and the visitor can use the scanner provided at the gate, the elevator, or the like. By reading the two-dimensional bar code 45e, it is possible to open the gate or move the elevator to a predetermined floor. Note that the gate and elevator may be permitted only in the path of the hospital room of the inpatient to be visited. In addition to the above information, the visit certificate may include various information such as a route to a hospital room. Further, in the present embodiment, the visit certificate printed with the two-dimensional bar code is used, but instead of the two-dimensional barcode, a pass-through password is described, or an IC card is used instead of the print type visit certificate. It is possible to adopt various forms such as.

Whether the visit certificate is printed out (S617), that is, whether the visit is permitted or not (S619), the visit history information is recorded in the database or the like of the management computer 3. (S620). FIG. 9H shows the data structure of the visit history information. The visit history information includes the patient ID, the medical facility ID, the visit type, the visit availability, the date and time of the visit, the imaging information, the temperature measurement information, and the number of accompanying persons of the patient to be visited. The visit type is information indicating whether the visit permit number was used, the visit permit two-dimensional barcode was used, or face recognition was used, and the information indicating the contents. When the visit permit number is used In the field, as shown in (a), information indicating the type (permit number) and the visit permit number are recorded. When the visit permission two-dimensional bar code is used, as shown in (b), information indicating the type (two-dimensional barcode) and the visit permission number included in the two-dimensional barcode are recorded. On the other hand, when face recognition is used, information indicating the type (face recognition) and face ID are recorded as shown in (c).

The visit approval/disapproval is information indicating whether the visit is permitted (that is, the visit certificate is issued) or not. The reception date and time is information indicating the date and time when the visit reception process is executed. The shooting information is the appearance of the visitor recorded in the shooting (S602) by the camera 13a. The temperature measurement information is information indicating the body temperature of the visitor measured in the temperature measurement process (S614). When the image capturing and temperature measuring process by the camera 13a is performed on the companion, the photographing information and the temperature measuring information of the visitor and the companion are recorded. The number of accompanying persons is information indicating the input result of the number of accompanying persons inquired in S616.

As described above, in the visit reception process of the present embodiment, by recording the visit history information, it is possible to appropriately leave the information of the visitor at the time of the visit, and it is possible to compare it with the record conventionally performed on paper. Therefore, it is possible to improve security.

Next, a case where the selection button 130b is selected on the selection screen of FIG. 27, that is, the use of the visit permission two-dimensional barcode is selected (S607: Yes) will be described. In the present embodiment, the visit permission two-dimensional bar code includes the visit permission number. Therefore, the use of the visit permission two-dimensional bar code is only to read the visit permission number using the two-dimensional barcode reader 15b, and is basically the same as the process when inputting the visit permission number (S603: Yes). It is the same. When the use of the visit permission two-dimensional bar code is selected (S607), the visit permission two-dimensional barcode is read using the two-dimensional barcode reader 15b, and the visit permission number included in the visit permission two-dimensional barcode is read. Based on this, the visit authorization number authentication process (S608) is executed. The visit authorization number authentication process (S608) is the same as the visit authorization number authentication process (S604) when the visit authorization number is input.

As a result of the visit permission number authentication processing (S608), if the authentication is successful (S609), the first visit determination processing (S630) is executed. The first visit determination process (S630) is similar to the first visit determination process (S630) when the visit permission number is input. As a result of the first visit determination process (S630), if the visit is possible (S610: Yes), the process proceeds to the next process. On the other hand, if the authentication is not possible (S609: No) and it is determined that the visit is not possible (S610: No), the visit error screen is displayed (S619), and the visit is not permitted.

Next, the case where the selection button 130c is selected on the selection screen of FIG. 27, that is, the case where face authentication is selected (S611: Yes) will be described. In the visit reception process of this embodiment, if the user has performed the face registration process described in FIGS. 6 and 7 in advance, it is not the visitor invited by the visit permission number and the visit permission two-dimensional barcode. It is also possible to receive an interview certificate. This is because the user who has performed the face registration process is likely to be a user who accompanied a patient and visited a medical facility and who is assisting the patient. Further, in the present embodiment, since attribute information indicating the relationship between the patient and the user is registered in the face registration process, it is possible to use the attribute information to determine whether or not the visit is possible.

When the selection button 130c is selected (S611: Yes), the second face authentication process (S650) is executed. FIG. 29 is a flowchart showing the second face authentication processing (S650) according to this embodiment. The second face authentication process (S650) has substantially the same content of authentication as the first face authentication process (S300) executed in the check-in process described in FIG.

When the second face authentication process (S650) is started, the accepting device 1 starts shooting with the camera 13a (S651). Then, the auxiliary authentication information input screen is displayed (S652). Various screens used in the second face authentication process (S650), such as the auxiliary authentication information input screen, are the same as the various screens with the same name described in the first face authentication process (S300), and are not shown here.

When the auxiliary input information is input (S653: Yes), an inquiry is made to the management computer 3 based on the input auxiliary authentication information and the image captured by the camera 13a (S654). The reception device 1 that has acquired the authentication result (S655: Yes) confirms the content of the authentication result (S656). If the authentication is not successful, the authentication result is set to be invalid (S661).

On the other hand, when the authentication is successful (S656: Yes), it is determined whether the number of hospitalized patients corresponding to the face ID is single (S657: No) or plural (S657: Yes) in the authentication result. Usually, it is a rare case that multiple patients associated with oneself are hospitalized. However, for example, when a company (worker) is assisting, there are multiple patients at one medical facility. It is conceivable that a person is admitted to the hospital (assistance). In this way, when the number of patients (hospitalized patients) who are hospitalized (S657: Yes) is associated with the face ID, the names of candidate hospitalized patients are displayed on the hospitalized patient selection screen ( S658), and the target inpatient is selected. When the target inpatient is selected on the inpatient selection screen (S659: Yes), the target inpatient is determined (S660).

As a result of the second face authentication process (S650), if the authentication is successful, that is, if the target inpatient can be determined, the process proceeds to the next second visit determination process (S670). On the other hand, if the authentication is not successful, the touch panel monitor 12 displays an interview error screen (not shown) (S619).

FIG. 30 is a flowchart showing the second meeting determination process (S630) according to this embodiment. Similar to the first visit determination process (S630), even if the authentication is successful, the visit cannot be made if the inpatient is discharged from the hospital. In the second meeting determination process (S670), first, it is determined whether or not the target patient is in the hospital by referring to the hospitalization start date and the hospitalization end date in the hospitalization related information stored in the management computer 3 or the like. (S671). If the patient is not hospitalized (S671: No), it is set that the visit is not possible (S678).

In addition, in the present embodiment, it is possible to manage visit permission/non-permission and visit permission time based on the attribute information registered in the face registration process. For example, when the patient is in a critical condition, it is conceivable that the visit is permitted if the attribute information is a relative within the first degree, and the visit is not permitted otherwise. Alternatively, if it is a relative, it is possible to permit visits by 22:00, and if not a relative (for example, in the case of a trader), it is possible to permit visits until 18:00.

If the attribute information is within the first visit permission range (S672: Yes), for example, if the relative is within the first degree of relatives, the current time is the first visit possible set for the first visit permission range. It is determined whether it is within time. When the current time is within the first visitable time (for example, from 9:00 to 22:00) (S673: Yes), the availability of the visit is set to allow the visit (S674). On the other hand, if the current time is not within the first meeting available time (S673: No), the meeting availability is set to not meeting possible (S678).

If the attribute information is not within the first meeting permission range (S672: No), it is determined whether the attribute information belongs to the second meeting permission range (S675). For example, the second visit permission range may be a relative or a trader. If it belongs to the second meeting permission range (S675: Yes), it is determined whether or not it is within the second meeting possible time set for the second meeting permission range. If the current time is within the second visitable time (for example, 13:00 to 18:00) (S676: Yes), the availability of the visit is set to allow the visit (S674). On the other hand, when the current time is not within the second meeting possible time (S676: No), the meeting availability is set to not meeting possible (S677).

In this way, when the face authentication process is selected in the visit reception process, the visitor can perform the visit without receiving an invitation from the inpatient in advance. Further, it is possible to easily receive the visit certificate without having to bring the visit permit number or the visit permit two-dimensional barcode. And even for inpatients who need identification cards for visits, it is possible to issue them to users who have registered their faces in advance without presenting them. ing. In addition, in the present embodiment, attribute information indicating a relationship with the patient is registered during the face registration process, so that it is possible to appropriately manage the availability of the visit using the attribute information or the available visit time. Has become.

Returning to the visit reception processing of FIG. 26, when it is determined that the visit is possible as a result of the second visit determination processing (S670) (S613: Yes), the temperature measurement processing for the visitor (S614) and the subsequent processing are executed. On the other hand, when it is determined that the visit is not possible (S613: No), the visit error screen (not shown) is displayed on the touch panel monitor 12 (S619).

Although the visit reception process has been described above, in the medical facility reception system of the present embodiment, it is possible to invite a visitor to the visitor using the mobile terminal 2 possessed by an inpatient or a person concerned. Becomes At that time, the mobile terminal 2 capable of executing the visit invitation process needs to execute the function addition process to be performed in face-to-face with the reception device 1 in advance, so that it is possible to improve security at the visit. Become.

In addition, in the medical facility reception system of the present embodiment, it is also possible to adopt a modified example described below.

In a medical facility such as a hospital, a nosocomial infection may occur due to an inflowing person. In particular, it is necessary to avoid the occurrence of nosocomial infection as much as possible when influenza, rubella, etc. are prevalent. In such a situation, allowing a visit from the outside, as usual, may allow the visitor to bring the virus into the medical facility. On the other hand, if all visits are blocked, it may be impossible for the inpatient to carry out personal activities. In this way, the absence of the visitor will burden not only the inpatient but also the staff on the medical facility side.

In the above-described embodiment, the attribute information indicating the relationship between the user who has submitted the visit application (the user who is the authentication target of the face authentication process) and the patient (inpatient) is used in the second face authentication process in the interview reception process. Although it has been described that the determination of whether or not the visitation is possible and the limitation of the visitation time are performed, a user who is a key person may be set among the users registered in advance. The key person can be set on the attribute selection screen described with reference to FIG. 12, for example. Alternatively, the setting may be made after the fact.

When set as a key person, special attribute information is set for the user. Further, it is preferable to limit the number of sets of special setting information such that only one person can be set for a patient. For example, in the diagram showing the registration authentication information and the patient basic information in FIG. 10B, one user in the bridge information, that is, special attribute information is set for any one of the bridge information, and the user is It will be designated as a key person.

In a medical facility, in normal times, the visit reception process described with reference to FIG. 26 is executed to determine whether the visit is possible. On the other hand, in an emergency such as when a viral illness is prevalent, in the second visit determination process (S670), among the users who applied for the visit, the user designated as the key person, that is, the special attribute information is set. Only users who are present are allowed to visit and issue an interview certificate. In this way, in the modified example that uses the special attribute information, in an emergency, the number of visitors who visit the hospital room can be suppressed to an appropriate number by limiting the number of users who can visit to the key person set to the inpatient. Therefore, it becomes possible to suppress nosocomial infection. In addition, it is possible to secure a visitor who takes care of the inpatient's personal belongings and the like, so that the burden on the medical facility side can be suppressed.

Although various embodiments of the invention according to the present invention have been described above, the present invention is not limited to these various embodiments, and a configuration in which the configurations of the respective various embodiments are appropriately combined is also present. It is a category of the invention.

1 (1a, 1b): Reception device 21e: Voice processing unit 2: Mobile terminal 22: Storage unit 3: Management computer 23: Interface 11a: CPU 24: Camera 11b: ROM 25: Touch panel monitor 11c: RAM 26a: Mobile line communication Part 11d: Image processing unit 26b: Wireless LAN communication unit 11e: Audio processing unit 26c: Communication unit 12: Touch panel monitor 27: Input switch 13a: Camera 28a: Speaker 13b: Infrared camera 28b: Microphone 14: Card reader 41: Input device 15: Receipt Printer 42: Monitor 15a: Scanner 43: Card Reader 15b: Two-dimensional Bar Code Reader 44: Receipt Printer 16a: Receipt Printer 45: Visit Certificate 16b: Printer 45a: Medical Facility Name 17: Interface 45b: Issue Date/Time 17a: LAN communication unit 45c: Name 17b: Communication unit 45d: Hospital room number 18: Hard disk 45e: Two-dimensional barcode 21a: CPU 52: Router 21b: ROM 71: Hospital reception 21c: RAM 72: Doorway 21d: Image processing unit 121: Touch panel

Claims (3)

A reception system for a medical facility, which includes a reception device and a program executed by a mobile terminal owned by a user,
The reception device has a user interface with which a user faces and operates.
By operating using the user interface, function addition processing executed with the mobile terminal,
It is possible to execute visitation acceptance processing for judging permission/non-permission of visitation based on the visitor permission information input by the visitor,
The program is a medical facility reception system capable of transmitting, to a visitor, visit permission information permitting an visit on condition that the function addition process is executed. The function addition process is performed by reading the code information displayed on the reception device with the mobile terminal, or by reading the code information displayed on the mobile terminal with the reception device.
The medical facility reception system according to claim 1. The reception device includes a camera,
The medical facility reception system according to claim 1 or 2, wherein the function addition process captures an image of a user who is operating in front of the reception device by the camera, and stores information when the function is added, including imaging information.