JP7066595B2 - Reception system for medical facilities - Google Patents

Description

The present invention relates to a reception system for medical facilities that accepts visits to inpatients in medical facilities such as hospitals.

At medical facilities such as hospitals, visits are held to visit patients (inpatients) who are hospitalized by relatives, acquaintances, etc., or to take care of their surroundings. Conventionally, visits at medical facilities are made by recording the name of the visitor, the name of the inpatient to be visited, the hospital room number of the inpatient, the visit time, the exit time, etc. in the paper visit record installed at the counter. It was usually managed.

However, in the management of such visits, there are security problems such as the record of the visit is uncertain, and if the name and room number of the inpatient are known, the patient can pass through. In order to solve such a problem, in Patent Document 1, a visit application is made from the visitor's PC, and if the answer to the visit request is a witness, the visit reservation is sent to the visit applicant's PC and the visit is held. It is disclosed that the opening and closing of the gate device is controlled on condition that it is permitted and that it matches the voiceprint information registered in advance at the time of the visit.

Further, in Patent Document 2, when the inpatient has specified a visit permitter or a desired visit date, the inpatient's medical treatment schedule is inquired, the date and time when the visit is possible is requested, and then the visit permitter is sent an e-mail. It is disclosed to notify the permit code. Further, in Patent Document 3, the number of visitors that can be accommodated at the same time (the number of people that can be accommodated at the same time) is assigned to each hospital room, and when the number of visitors that can be accommodated at the same time is less than or equal to the number of people that can be accommodated at the same time, the patient's hospital room can be selected as the meeting place. It has been disclosed.

Japanese Unexamined Patent Publication No. 2008-305315 Japanese Unexamined Patent Publication No. 2013-222269 Japanese Unexamined Patent Publication No. 2008-225834

As disclosed in Patent Documents 1 to 3, various visitation management using an information processing device has been proposed. By the way, at present, mobile terminals owned and owned by users such as smartphones are widespread. It is conceivable to use such a mobile terminal to manage visits. However, if the mobile terminal owned by an individual is allowed to freely manage visits, a security problem will occur. One object of the present invention is to enable various processes related to a visit to be executed by using a mobile terminal owned by a user, and to ensure security at that time.

The reception system for medical facilities related to the first configuration is
It is a reception system for medical facilities that includes a reception device and a program executed by a mobile terminal owned by the user.
The reception device has a user interface in which users perform face-to-face operations.
Addition of a function performed by performing an operation using the user interface and reading the code information displayed on the reception device with the mobile terminal, or reading the code information displayed on the mobile terminal with the reception device. Processing and
It is possible to execute the visit reception process to determine whether the visit is permitted or not based on the visit permission information entered by the visitor.
The program enables the visitor permission information for permitting the visitor to be transmitted to the designated destination information, provided that the function addition process is executed.

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

Further, the reception system for medical facilities disclosed in the present specification includes the following configurations of 2-1 to 2-5.

The reception system for medical facilities related to the configuration of 2-1 is
A reception system for medical facilities that includes a reception device and a storage unit.
The storage unit stores patient identification information and attribute information indicating the relationship between the user and the patient in association with the biometric authentication information of the user.
The reception device enables the visit reception process to be executed.
In the visit reception process, the biometric authentication process is executed for the user who applied for the visit.
In the biometric authentication process, if there is biometric authentication information for the user, the patient identification information and attribute information corresponding to the biometric authentication information are read out.
A reception system for medical facilities that determines whether or not 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 reception system for medical facilities according to the configuration of 2-2 is the reception system for medical facilities according to the configuration of 2-1.
The visit reception process determines whether or not a visit is possible based on the available visit time corresponding to the read attribute information.

The reception system for medical facilities according to the configuration of 2-3 is the reception system for medical facilities according to the configuration of 2-1 or 2-2.
In the visit reception process, when a plurality of patients associated with the biometric authentication information are hospitalized, the user is made to select the patient to be visited.

The reception system for medical facilities according to the configuration of 2-4 is the reception system for medical facilities according to any one of 2-1 to 2-3.
The storage unit can set special attribute information indicating the relationship between the user and the patient in association with the biometric authentication information of the user.
In the visit reception process, when an application for visit acceptance is made in an emergency, only the user for which the special attribute information is set is allowed to accept the visit.

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

The medical facility reception system according to the second 2-6 configuration is the medical facility reception system according to any one of the 2-1 to 2-5 configurations.
It is possible to execute the check-in process that accepts medical treatment of patients.
In the check-in process, the biometric authentication process is executed for the user who applied for medical treatment, and the check-in process is performed.
In the biometric authentication process, if there is biometric authentication information for the user, medical treatment of the patient corresponding to the biometric authentication information is accepted.

In addition, the reception system for medical facilities disclosed in the present specification includes the third configuration shown below.
The reception system for medical facilities related to the third configuration is
A reception system for medical facilities that includes a reception device and a storage unit.
The storage unit stores patient identification information associated with the user's biometric authentication information, and can set special attribute information indicating the relationship between the user and the patient.
The reception device enables the visit reception process to be executed.
In the visit reception process, the biometric authentication process is executed for the user who 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 is read out.
When a visit application is made in an emergency, only the user who is in the hospital corresponding to the read patient identification information and the special attribute information is set is allowed to visit.

Further, the reception device for medical facilities disclosed in the present specification has the fourth configuration shown below.

The reception system for medical facilities related to the fourth configuration is
A reception system for medical facilities that includes a reception device and a storage unit.
The storage unit stores patient identification information associated with the user's biometric authentication information, and can set special attribute information indicating the relationship between the user and the patient.
The reception device enables the visit reception process to be executed.
In the visit reception process, the biometric authentication process is executed for the user who 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 is read out.
When a visit application is made in an emergency, only the user who is in the hospital corresponding to the read patient identification information and the special attribute information is set is allowed to visit.

In addition, the reception device for medical facilities disclosed in the present specification includes the following configurations of 5-1 to 5-2.

The reception system for medical facilities related to the configuration of No. 5-1 is
A reception system for medical facilities that includes a reception device and a storage unit.
The storage unit stores patient identification information associated with the user's biometric authentication information, and stores the patient's identification information.
The reception device enables execution of the first visit reception process and the second visit information.
In the first visit reception process, the biometric authentication process is executed for the user who 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 is read out, and if the patient corresponding to the read patient identification information is in the hospital, the visit is permitted. ,
The second visit reception process permits the visit if the visit permission information input by the user is appropriate.

The reception system for medical facilities according to the configuration of No. 5-2 is the reception system for medical facilities according to the configuration of No. 5-1.
The storage unit stores attribute information indicating the relationship between the user and the patient in association with the biometric authentication information of the user.
The first visit reception process determines whether or not a visit is possible based on the read attribute information when the patient corresponding to the read patient identification information is in the hospital.

In addition, the reception device for medical facilities disclosed in the present specification includes the configurations of Nos. 6-1 to 6-2 shown below.

The reception device for medical facilities according to the configuration of No. 6-1 is
It is possible to execute the check-in process for accepting medical treatment of patients and the visit reception process for accepting visits to inpatients.
In the check-in process and the visit reception process, the body temperature of the user facing the reception device is measured, and a temperature measurement process for determining whether or not the body temperature is normal is executed.
The temperature measurement process executed in the check-in process and the temperature measurement process executed in the visit reception process have different threshold values for determining whether or not the body temperature is normal.

In the reception device for medical facilities related to the configuration of No. 6-2
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 (configurations 1-1 to 1-3), the program executed on the mobile terminal performs the function addition process executed with the reception device. By executing this, it becomes possible to send visit permission information that permits 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 reception system for medical facilities according to the second configuration (configurations 2-1 to 2-5), biometric authentication processing is used in the visit application, and attribute information indicating the relationship between the user and the patient is provided. It will be used to determine whether or not a visit is possible. With such a configuration, for example, if the relatives are within the first degree of kinship, the visit is permitted, and if the relatives are separated by the second degree or more, the visit is not permitted. Is possible. In addition, if the user has pre-registered biometric authentication information, there is no need to present any documents when applying for a visit.

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

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

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

According to the medical facility reception system according to the sixth configuration (configurations 6-1 to 6-2), the temperature measurement process executed in the check-in process and the temperature measurement process executed in the visit reception process. The treatments differ in the thresholds for determining whether the body temperature is normal. With such a configuration, for example, in the visit reception process, by setting a strict threshold for determining whether or not the body temperature is normal, if a viral disease such as influenza is prevalent, nosocomial infection due to the visit can be caused. It becomes possible to suppress it.

The figure which shows the structure of the reception system which concerns on this embodiment Front view of the reception device according to this embodiment Block diagram showing the configuration of the reception device according to this embodiment Block diagram showing the configuration of the mobile terminal according to this embodiment The figure which shows the initial screen of the reception device which concerns on this embodiment. A flow chart showing the face registration process (reception device side) according to this embodiment. A flow chart showing the face registration process (management computer side) according to this embodiment. A flow chart showing the face registration process (management computer side) according to this embodiment. The figure which shows various data structures used in the reception system which concerns on this embodiment. The figure for demonstrating the relationship between the face registration authentication information and the patient basic information which concerns on this embodiment. The figure which shows the examination 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 The figure which shows the screen for an outpatient which concerns on this embodiment Flow chart showing check-in process according to this embodiment A flow chart showing a first face recognition process according to this 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 The figure which shows the check-in confirmation screen which concerns on this Embodiment Flow diagram showing wireless check-in function addition processing according to this embodiment The figure which shows various screens of the mobile terminal which concerns on this embodiment. The figure which shows various screens of the mobile terminal which concerns on this embodiment. Flow chart showing visit invitation processing according to this embodiment The figure which shows the visit invitation confirmation screen of the mobile terminal which concerns on this embodiment. Flow chart showing visit reception processing according to this embodiment The figure which shows the selection screen which concerns on this embodiment The flow chart which shows the 1st visit determination process which concerns on this Embodiment A flow chart showing a second face recognition process according to this embodiment. The flow chart which shows the 2nd visit determination process which concerns on this Embodiment The figure which shows the visitation 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 medical examinations at the time of the second and subsequent medical examinations at various medical facilities such as hospitals. The reception system of the present embodiment is installed in a lobby located near the entrance / exit 72 of the medical facility. The reception system includes reception devices 1a and 1b arranged in a lobby and operated by a user, a management computer 3 arranged in a hospital reception 71 and the like and operated by an employee. A plurality of reception devices 1a and 1b (two in this embodiment) are arranged so that the service can be provided to a plurality of users at the same time.

The reception devices 1a and 1b and the management computer 3 are connected to each other so as to be able to communicate with each other via the LAN 51. The management computer 3 is connected to an input device 41 for receiving input by employees, such as a monitor 42 for displaying various information, a keyboard, and a mouse. Further, a receipt printer 44 for printing on the receipt form paper and a card reader 43 for reading (or writing) 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 capable of providing various services such as new patient reception and return reception (also referred to as check-in) to a user who operates face-to-face with the reception device 1. The reception 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 the user who operates the reception device 1.

The touch panel monitor 12 displays visual information to a user who performs a face-to-face operation, and can accept the user's touch operation. Above the touch panel monitor 12, a camera 13a capable of capturing a range including the face of a user who performs a face-to-face operation and an infrared camera 13b are provided. The camera 13a is for photographing the face of the user to be used, and the infrared camera 13b is provided for photographing the face of the user to be used and performing a temperature measuring process for detecting the body temperature of the user.

The card reader 14 reads various information such as a patient ID stored in a magnetic card possessed by the user or a medical examination ticket composed of an IC card. Further, the card reader may be provided with a function of reading a credit card used for payment of medical expenses. The scanner 15a is a flatbed type provided for reading the health insurance card, and when it is necessary to show the health insurance card, such as at the time of returning reception or at the first medical examination of the month, the scanner 15a can be used. Read the insurance card etc. possessed by the user.

The two-dimensional bar code reader 15b can read various two-dimensional bar codes such as a two-dimensional bar code printed on a printed matter or a two-dimensional bar code displayed on the mobile terminal 2. The object to be read may be a 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 read target may be used 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-arrival reception, a reservation table issued at the time of reservation reception, and the like. Further, the printer 16b prints on ordinary paper such as a laser printer or an inkjet printer by using toner or ink, and is used for printing medical statements, receipts, etc. issued at the time of payment of clothing expenses. Will be done.

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

A 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 information to the user and a touch panel 121 that accepts 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 camera 13a, the infrared camera 13b, the card reader 14, the receipt printer 16a, the printer 16b, the scanner 15a, the two-dimensional bar code reader 15b, and the touch panel 121 described with reference to FIG. 2 are connected to the interface 17, and the control unit is controlled. Various processes are executed based on. 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 various information processing devices on the LAN such as the management computer 3 described with reference to FIG. 1 or a router 52.

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 mounted on each reception device 1, but the short-range wireless communication unit is one reception device. It may be mounted on 1. Alternatively, it may be installed outside the reception device 1. For example, it may be mounted on a management computer 3 installed on the same floor as the reception device 1, or separately mounted on an information processing device connected to a LAN 51 to perform wireless communication with a 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 possessed by the user will be described. The mobile terminal 2 is a smartphone, a tablet terminal, or the like, and is a terminal owned and possessed by the user and used by the user.

FIG. 4 is a block diagram showing the configuration of the mobile terminal 2 according to the present embodiment. The mobile terminal 2 includes a CPU 21a, a ROM 21b, a RAM 21c, an image processing unit 21d, and a voice processing unit 21e as control units. It also has a non-volatile storage unit 22 such as a flash memory. Further, an input switch 27 is connected to the control unit via the interface 23, in addition to various communication means such as a mobile line communication unit 26a, a wireless LAN communication unit 26b, and a Bluetooth communication unit 26c (short-range wireless communication unit). 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 information to the user, and a touch panel 251 that accepts a touch operation by the user. The camera 24 is arranged on the back surface of the mobile terminal 2 or the like, and can shoot still images and moving images. It should be noted that a plurality of cameras 24 may be arranged not only on the back surface but also on the front surface. A speaker 28a for transmitting auditory information to the user and a microphone 28b for acquiring acoustic information are connected to the voice processing unit 21e. The touch panel monitor 25 and the input switch function as a user interface on the mobile terminal side 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 asking the user whether the user is an outpatient or a visitor, a patient-related person (the patient himself / herself, a relative of the patient, or a business engaged in nursing the patient) A button 121c for registering a face, a button 121d for adding a function to a smartphone (mobile terminal 2), and a button 121e for switching to another language other than Japanese are displayed. There is. When the user selects the buttons 121a to 121e, the corresponding processing is executed.

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

By the way, some patients undergoing medical examination may be accompanied by a caregiver because they are children, are in a wheelchair, cannot walk on their own, or have dementia. .. In such a case, it is difficult for the patient to operate the reception device 1, and it is conceivable that the operation is performed by the caregiver. The caregiver may be relatives (parents, children, relatives) of the patient, friends, business workers who care for the patient, and the like. In the reception device 1 using the conventional medical examination ticket, for example, when the caregiver's parent is a patient, the medical examination ticket is received from the parent who is the patient, and the reception device 1 is operated to perform reception. The same applies to business workers, who will receive a medical examination ticket from the patient.

In biometric authentication including face authentication, it is usual to authenticate the person. However, due to the above-mentioned circumstances peculiar to the medical facility, there is a situation in which the patient himself / herself cannot perform the operation facing the reception device 1. Therefore, the reception system of the present embodiment is characterized by having at least one of the three configurations shown below.
-Associating one patient with another user other than the patient who can perform face recognition.
-Associating a plurality of users (which may include patients) capable of face recognition with one patient.
-In the case of the above-mentioned workers, there are cases where a plurality of patients are assisted in one medical facility. Therefore, a certain user (for example, a worker or the like) may be associated with a plurality of patients so that face recognition can be performed.

First, the face registration process according to the present embodiment will be described with reference to FIGS. 6 and 7. FIG. 6 is a flow chart showing a face registration process (reception device side) according to the present embodiment, and FIG. 7 is a flow chart showing a face registration process (management computer side) according to the present embodiment.

Here, the data structure of various information used in the reception system of the present embodiment will be described. FIG. 8 shows various data configurations used in the reception system according to the present embodiment. The management computer 3 records pre-registered basic patient information at the timing of the first medical examination or the like. As shown in FIG. 8A, the patient basic information includes information about the patient as a user, such as patient ID, facility ID, name, address, gender, date of birth, personal identification information, and health insurance card information. 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 identify 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 may be appropriately determined so that the medical facility and the patient can be identified as well as the combination of the patient ID and the medical facility ID.

The personal identification information is various information that makes it possible to identify an individual, such as a driver's license presented by the patient at the time of receiving the first medical examination, a number written on the My Number card, or a copy image thereof. The health insurance card information includes the health insurance card type, health insurance card number, 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 clinical 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 specified, but the reservation form is not limited to such a form, and is limited to 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 changed as appropriate according to the reservation form of the medical facility.

The face registration process 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 medical examination ticket reading guidance screen prompting the insertion of the medical examination ticket (S101).

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

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

The camera 13a is directed in the direction of photographing the face of the user who operates the reception device 1 in front of the reception device 1. The reception device 1 acquires face recognition information from the video information taken by the camera 13a. As the face recognition information, various forms such as video information, facial features extracted from the video information, video information, and features can be adopted. Further, if face authentication cannot be performed, such as wearing a mask or sunglasses, it is determined that face authentication information cannot be acquired (S106: No). When the acquisition of sufficient face authentication information for performing face authentication is completed from the video information captured by the camera 13a (S106: Yes), the attribute selection screen is displayed (S107).

On the other hand, if the face authentication information required for face authentication cannot be acquired and the predetermined time-out time has elapsed (S105: Yes), an error screen is displayed on the touch panel monitor 12 (S114), and a user is added. A confirmation screen is displayed (S112). Alternatively, the touch panel monitor 12 may display the items necessary for acquiring the face authentication information, 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 in place of the patient or in addition to the patient. Therefore, in the face registration process of the present embodiment, it is possible to register attribute information indicating who the user who has performed face registration is for the patient. The registered attribute information can be referred to by the employee of the medical facility in the reception system in addition to the check-in process described later. Therefore, in the medical facility, it is possible to use the information processing device communication-connected to the reception system and refer to the attributes of the caregiver who is accompanying the patient who received the reception 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 captured by the camera 13a, an attribute selection button 123b, a button 123d labeled as Next, and a button 123c labeled as Cancel are displayed on the attribute selection screen so that the user can confirm them. Is displayed. The user uses the attribute selection button 123b to select his or her attributes for the patient. In this embodiment, the attributes are selected from predetermined attributes, but the user can freely input the attributes by using an input means such as a soft keyboard or a numeric keypad. May be good. For example, when a single medical facility is in charge of multiple patients, such as a contractor (business worker), the management number assigned by the contractor to the patient can be used in the check-in process described later. , It becomes possible to easily select the target patient. Moreover, not only one attribute but also 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, in addition to face authentication as biometric authentication, a contact telephone number is used as auxiliary authentication information. 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 face authentication and authentication using auxiliary authentication information together, it is possible to improve the accuracy of authentication without using 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 for patients on the database in which the auxiliary authentication information matches.

On the auxiliary authentication information registration screen, input display fields 124a, numeric keypad 124b, buttons 124c, and 124d are displayed. The user who operates the reception device 1 inputs his / her contact telephone number using the numeric keypad 124b. The entered contact telephone number is displayed in the input display field 124a. The user who has completed the input completes the registration of the auxiliary authentication information by operating the button 124c described as registration (S110: Yes). By operating the button 123d marked 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 reception device 1 transmits the registration authentication information to the management computer 3 (S111). 10 (A) and 10 (B) show the data structure of the registered authentication information. 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, the auxiliary authentication information, and the attribute information acquired in the registration process this time 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 one user who has performed face registration is associated with a plurality of patients. Further, FIG. 10B is an example in which a plurality of users who have performed face registration are associated with one patient.

As described above, in the present embodiment, it is possible to register a plurality of users for one patient, or to register a plurality of patients for one user. Therefore, in the face registration process executed by the reception device 1, it is possible to register the faces of a plurality of users in one process, and after transmitting the registration authentication information (S111), the user addition confirmation screen is displayed. By displaying (S112), other users can also register their faces. That is, it is possible to register the faces of a plurality of users such as the person, relatives, traders (business workers), 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 the present embodiment, the captured image display fields 125a, buttons 125b, and 125c are displayed. In the captured image display field 125a, the image captured by the camera 13a is displayed. The user can confirm that the face registration is possible by visually recognizing the photographed image display field 125a. When continuously registering the face of another user, the button 125b marked as "Yes" is operated (S113: Yes). In that case, the process returns to S104 and the face registration of another user is started. On the other hand, when the button 124c marked with No is operated (S113: No), a series of face registration processes is terminated.

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

On the other hand, when the registration authentication information (face authentication information, auxiliary authentication information) acquired by the reception device 1 is already registered this time (S153: Yes), is the matching user associated with the patient? That is, it is confirmed whether the bridge information matches (S155). When there is no matching bridge information (S155: No), only the bridge information portion is additionally registered as the registration authentication information (S157). For the basic information part, the one already registered will be used, or the information acquired this time will be updated. On the other hand, when 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). The reception device 1 that has received the error information displays that the user who tried to register the face for a certain patient has already registered for the patient (not shown in FIG. 6).

As described above, in the present embodiment, when the registration authentication information is registered in the management computer 3, the registration authentication information is separately registered as the basic information and the bridge information. Therefore, duplication of the basic information portion including the face authentication information is avoided and the amount of data is increased. It is possible to reduce the number of problems, suppress the occurrence of problems due to the registration of multiple face recognition information, and improve the efficiency of face recognition.

Next, the check-in process using the face recognition process in the present embodiment will be described. Here, the check-in process corresponds to the process performed at the return reception, which is performed when the patient who has visited the hospital again visits the hospital again. When the button 121a labeled as an outpatient is selected on the initial screen of FIG. 5, 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 buttons 126e for returning to the initial screen are displayed.

Here, various services displayed on the buttons 126a to 126d will be described. When it is started by touch-selecting the button 126a (new patient reception), the new patient reception process for a new patient, that is, a patient who visits this medical facility for the first time is started. In the new patient reception process, the scanner 15a of the reception device 1 is used to read the identification card such as the My Number card and the driver's license, and the health insurance card. The touch panel monitor 12 is displayed to notify the user to wait until the registration is completed, and the new patient reception process 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 the clerk and the like.

The process started by touch-selecting the button 126c (return reception) is a process (check-in process) for receiving medical treatment when the second and subsequent consultations are performed at the medical facility. The return reception process of the present embodiment is intended for users who have made a medical appointment in advance, such as at the time of the previous consultation, but it may be possible to accept users who have not made a reservation. Therefore, the return reception process is called the 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 reception device 1 of the present embodiment makes it possible to make payments by credit card using the card reader 14, it is also possible to provide a cash handling function and make payments 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 recognition process in the present embodiment can be used not only for the check-in process but also for various processes conventionally used for patient authentication using a medical 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 a button 121b in FIG. 5 is operated. The processing at the time of accepting the visit, which is executed by doing so, can be mentioned.

FIG. 16 is a flow chart showing a check-in process according to the present embodiment. The check-in process is a process executed by the reception device 1, and is a process 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 of FIG.

When the check-in process is started, the guidance screen is displayed on the touch panel monitor 12 (S201). The guidance screen allows the user to select two types of 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 the face registration process 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 processes after S204 in order to accept the patient. To execute.

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

FIG. 17 is a flow chart showing the first face recognition process according to the present embodiment. When the first face recognition process (S300) is started, the reception device 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 the present embodiment. The auxiliary authentication information input screen includes a captured image display field 127a, an input display field 127b, a numeric keypad 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 input by the numeric keypad 127c (in this example, the contact telephone number) is displayed.

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

The authentication result in the management computer 3 is transmitted to the reception device 1. The receiving device 1 that has acquired the authentication result (S305: Yes) confirms the content of the authentication result (S306). If authentication is possible (S306: Yes), it is determined in the authentication result whether the target patient is singular (S307: No) or plural (S307: Yes). As described as shown in FIG. 10A, in the present embodiment, it is possible to associate a plurality of patients with one user capable of face recognition. Therefore, when the authenticated user has a plurality of patients (S307: Yes), the associated plurality of patients are presented as candidates and the user is allowed to select the patient.

FIG. 19 is a diagram showing a target patient selection screen according to the present embodiment. The patient selection buttons 128a to 128d are displayed on the target patient selection screen. The patient selection buttons 128a to 128d display the patient's name and the relationship with the authenticated user (user operating the reception device 1). 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 be examined this time (S310).

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

The management computer 3 that has received the check-in request 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 same as that day, error information is transmitted to the reception device 1. When the error information is received (S205: Yes), the reception device 1 displays a check-in error screen on the touch panel monitor 12 notifying that the reception has not been made (S215).

On the other hand, when the management computer 3 has the reservation information corresponding to the patient ID and the reservation date is the same 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 clinical department name, a doctor name, and the like. When the reception device 1 receives the reservation confirmation information (S206: Yes), the reception device 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 an infrared camera 13b capable of capturing an image of a range including the user. The temperature is measured using this infrared camera 13b (S207). In this embodiment, the body temperature in the vicinity of the human temple, which can accurately measure the temperature, is used. Furthermore, in order to improve the accuracy of the temperature measurement result, the body temperature near the temple is corrected based on the body temperature distribution of the face over a wide range 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 that the patient has a 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 the fever caution information is transmitted to the management computer 3. Transmit (S214).

On the heat generation caution screen, it is displayed that the user is requested to move to an isolated space or the like due to heat generation. In addition, the management computer 3 that has received the fever caution information notifies the employee that a patient with 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 check-in, such as isolating users who have influenza at the time of re-arrival reception. The reception device 1 may be provided with not only a heat generation caution screen but also a notification means for notifying the surroundings 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 turn it on to provide a notification means such as notifying the employees waiting around the reception device 1 or notifying by voice. .. Further, the temperature measurement by the infrared camera 13b is not limited to the timing of the present embodiment, and may be performed at an appropriate timing in the check-in process.

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 clinical department, a doctor name, and a reservation time zone, a cancellation 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 in one visit. In that case, the check-in confirmation screen is displayed based on the corresponding plurality of reservation information (S209). If there is no problem with the consultation content, the user operates the confirmation button 129c to confirm the consultation content on the day (S210: Yes). On the other hand, when it is desired to cancel the consultation contents, it is possible to cancel the reservation corresponding to the item by selecting the item to be canceled (medical examination department, etc.) and operating the cancel button 129b.

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

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

In the present embodiment, when the first face authentication process (S300) is performed, the attribute information of the user who has 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 is attending the patient on the day. For example, when referring to information about a patient (name, etc.) in an information processing device installed in a clinical department to be examined, a notification that notifies (displays) the relationship between the patient and the assisting user based on this attribute information. By executing the treatment, the medical facility can easily confirm the relationship between the patient and the caregiver. For example, in a situation where the patient's relatives (parent, child, spouse) want to explain the medical condition, the medical facility can easily grasp the relationship between the patient notified based on the attribute information and the user who is assisting. However, it becomes possible to judge whether or not the explanation of the medical condition is possible. Instead of adding this attribute information to the confirmation instruction information, the notification processing may be performed by including it in the two-dimensional bar code (code information) of the reception completion slip.

For example, when the target patient is a child and the user who has authenticated by the reception device 1 is the parent, the information processing device installed in the clinical department notifies that the target patient is the parent. In this case, at the time of registration processing, it is the relationship of the patient from the viewpoint of the user who authenticates (in this case, the child), whereas when the medical facility notifies, the relationship of the user who authenticates from the viewpoint of the patient (in this case, the parent). ). By making the relationship to be selected in the registration process different from the form of notification in the notification process in this way, it is easy to select the attribute information in the registration process, and in the target process, the relationship with the patient on the medical facility side is grasped. It is possible to make it easy.

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

In addition, as additional functions that can be executed on the mobile terminal 2, various functions such as return reception (check-in processing), medical fee payment, reservation request, and visit invitation, which are executed by the reception device 1, are added as described in FIG. It is possible to do. Such an additional function needs to specify a user (patient or the like) 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 a basic function of the program is not preferable for ensuring security. Alternatively, it is not preferable from the viewpoint of security to add the function only with the mobile terminal 2. There is also the possibility of unauthorized use due to security problems. Therefore, in the present embodiment, the reception device 1 is used when adding a function to the program (application) executed by the mobile terminal 2.

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

The reception device 1 transmits the read patient ID to the management computer 3 and acquires the basic patient 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 contained therein, but may be some necessary information. After that, the touch panel monitor 12 displays a function addition confirmation screen including a two-dimensional bar code for the mobile terminal 2 to read (S405). This two-dimensional bar code contains information for identifying the patient. It is preferable that the patient ID is encrypted in the two-dimensional bar code. 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 by using the activated program (application). FIG. 8 (C1) is a form of a data structure included in a two-dimensional bar code, and identifies a patient ID, a medical facility ID (system ID), a name, a date of birth, and a reception device 1 used. The device ID for the device is included. The two-dimensional bar code read by the camera 24 is decrypted by the mobile terminal 2 and converted into information. Among 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 a medical examination ticket information. To.

22 and 23 are views showing various screens of the mobile terminal 2 according to the present embodiment. FIG. 22A is an initial screen displayed on the touch panel monitor 25 immediately after the program is started in the mobile terminal 2. On the initial screen, in addition to the currently selected medical facility name 251a, various buttons 251b to 251j are displayed. The button 251b is a button for using the mobile terminal 2 as a medical examination ticket, and by completing the function addition process described with reference to FIG. 21, the mobile terminal 2 can be used as a medical examination ticket that can be accepted by the reception device 1. It becomes possible to do. The mobile terminal 2 can be checked in by displaying a two-dimensional bar code as a medical examination ticket on the touch panel monitor 25, or by using the wireless function of the mobile terminal 2 to 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 medical expenses without having to stop by the reception device 1 or the reception.

The button 251d is a button for a hospitalized user to send information for issuing a visitation certificate to relatives, friends, acquaintances, etc. by e-mail. Using this function, hospitalized users can send e-mails to relatives, friends, acquaintances, and other persons who are permitted to visit. The e-mail is accompanied by information for issuing a visitation certificate, such as a two-dimensional bar code, a WEB address for obtaining the two-dimensional bar code, and a visitation permission number (visiting permission information). The visitor can receive a visitation certificate permitting the visit by having the reception device 1 read this information or input it.

The button 251e is a button for switching the target medical facility. 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 it is possible to select a target medical facility. After selection, the medical facility name 251a is changed to the selected one.

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

The button 251g is a function that can be executed after the function addition process is performed, and it is possible to reserve the next medical treatment date and time for the selected medical facility. In the initial screen of FIG. 22A, the button shown by the broken line is a function that is not used in the selected medical facility. This takes into account the specifications that differ from medical facility to medical facility. In this embodiment, the reservation request by the button 251 g 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 one's own waiting number, a pop-up notification is displayed on the mobile terminal 2 every 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). Button 251j is a button for switching to a multilingual language other than Japanese.

Here, the screen transition at the time of operating the button 251b used for the function addition process will be described. When the mobile terminal 2 is used instead of the medical examination ticket, it is necessary to execute a function addition process with the reception device 1 and register information such as a patient ID in the mobile terminal 2. If the information has not yet been registered in the mobile terminal 2 when the button 251b is operated, the terms of use shown in FIG. 22B are displayed first. Although only "Terms of Service" is displayed in FIG. 22B, the details of the Terms of Use are actually displayed here. In addition, a button 252a indicating that the user agrees and a button 252b indicating that the user disagrees are displayed. The user who agrees to the displayed terms of use operates the button 252a to proceed to the screen of FIG. 22 (C).

FIG. 22C is a screen in which the medical examination ticket has not been registered yet. The user advances to the screen of FIG. 23 (D) by operating the button 253 labeled as the medical examination ticket registration. FIG. 23D is a screen that prompts the operation on the reception device 1 side. Further, on this screen, a button 254 labeled as two-dimensional bar code reading is displayed. By operating this button 254, the screen transitions to the reading screen of FIG. 23 (E). On the reading screen, a monitor field 256a for displaying an image being photographed by the camera 24 and a cancel button 256 are displayed. While checking the image in the monitor column 256a, the user captures the function addition confirmation screen displayed in the process of S405 during the function addition process executed by the reception device 1.

The mobile terminal 2 that has read the two-dimensional bar code uses the mobile line communication unit 26a to transmit 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 the program (application). The management server receives registration request information from the mobile terminal 2 via the mobile line network and the Internet, and transmits the registration request information to the management computer 3 of the reception system using the reception device 1 having the device ID. The management computer notifies the receiving device 1 of the device ID included in the registration request information that the registration request information has been received.

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

The management computer 3 that has received the shooting information registers the mobile terminal registration information based on the previously received registration request information and the shooting information. FIG. 8E 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 reception device 1, a registration date and time indicating the registration date and time, and shooting information taken by the camera 13a. The mobile terminal registration information is used to identify whether the mobile terminal 2 is appropriate by using the terminal ID included in the mobile terminal registration information. Then, when a trouble or the like occurs after the function is added, it is possible to use it as a history of when and who registered the function by referring to the mobile terminal registration information.

On the other hand, when the reception device 1 cannot receive the terminal ID (or application ID) of the mobile terminal 2 (S406: No), the process ends after a time-out period of a certain 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 is required to perform the operation facing the reception device 1. Therefore, it is possible to suppress various problems such as security and unauthorized use when using the mobile terminal 2. In particular, the mobile terminal 2 stores information that requires accuracy and confidentiality, such as a patient ID and a system ID, and the reception system provides these information to the mobile terminal 2 as in the present embodiment. By doing so, it is possible to ensure accuracy and confidentiality.

In the present embodiment, it has been described that various information is transmitted / received by displaying the two-dimensional bar code on the reception device 1 and reading it on the mobile terminal 2, but instead of such a form, the mobile terminal 2 side. , A two-dimensional bar code including the terminal ID (or application ID) may be displayed and read by the two-dimensional bar code reader 15b on the reception device 1 side. In that case, from the reception system side, for the mobile terminal 2 specified by the terminal ID, various information necessary for adding a function (at least a patient required to identify the user) is used by using the mobile line network. ID, medical facility ID, etc.) will be transmitted.

Alternatively, the two-dimensional bar code does not include the information as shown in FIG. 8 (C1), and the device ID or the like of the receiving device 1 as shown in FIG. 8 (C2) is used as the authentication information. May be included. The mobile terminal 2 that has received the two-dimensional bar code transmits the information for mobile terminal authentication to the reception system through the mobile network and the Internet, and the reception system identifies the information necessary for adding the function (at least the user is specified). (Patient ID, medical facility ID, etc. required for) will be received. According to such a form, it is not necessary to display information requiring confidentiality with a two-dimensional bar code, and it is possible to suppress information leakage due to shooting and copying of the two-dimensional bar code.

Further, in the present embodiment, the biometric authentication information is included in the basic patient information. When the information required for face authentication is adopted for this biometric authentication information, the registered biometric authentication information is compared with the imaging information included in the mobile terminal registration information, and the matching rate is low. If the user is different from the biometric authentication information of the information, the function may not be added, or measures such as notifying the management computer 3 of an alert may be taken. In addition, if the operating user does not face the appropriate direction, or the user cannot select the best shot in S407 because the user wears a mask or sunglasses, the appropriate direction for the user. You may get the best shot by instructing them to look at you or by instructing them to remove their mask or sunglasses. If the best shot cannot be obtained, the function may not be added, or measures such as notifying the management computer 3 of an alert may be taken.

Next, the visit invitation process that can be executed on the mobile terminal 2 that has been registered 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 planning to be hospitalized to invite a visit using his / her mobile terminal 2. FIG. 9 shows the data structure of various information related to the visit. FIG. 9F shows hospitalization-related information indicating the hospitalization status of the patient. The hospitalization-related information includes the patient ID for identifying the patient, the medical facility ID, and the hospitalization start date and hospitalization end date. The hospitalization start date and hospitalization end date may be scheduled. If the hospitalization end date is undecided, information indicating that the information is not recorded or is undecided will be recorded on the hospitalization end date. The hospital room number is information for identifying the hospital room in which the patient stays in the hospital (hospital room identification information).

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

FIG. 24 is a flow chart showing a visit invitation process according to the present embodiment. By operating the button 251d in the initial screen of the mobile terminal 2 described with reference to FIG. 22 (A), the visit invitation process is started. When the visit invitation process is started, the patient ID and 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 is determined based on the hospitalization-related information. Receive information indicating whether you are in the middle or will be hospitalized (S501). When a plurality of medical examination tickets are registered in the mobile terminal 2, an inquiry is made by designating the medical examination tickets to be inpatients.

For the patient who made an inquiry, if he / she is in the hospital or is scheduled to be hospitalized (S502: Yes), the destination information (email address, telephone number of the mobile terminal 2, etc.) of the visitor can be specified (S503). On the other hand, if the patient is in the hospital or has no plans to be hospitalized (S502: No), the visit invitation process is terminated. In the designation of the destination information of the visitor, the user selects the destination information by referring to the contact information stored in the mobile terminal 2, or directly inputs the destination information and confirms the destination information. When the designation of the destination information is confirmed, the visit invitation confirmation screen is displayed on the touch panel monitor 25 of the mobile terminal 2 (S504).

FIG. 25 is a diagram showing a visit invitation confirmation screen of the mobile terminal 2 according to the present embodiment. On the visit invitation confirmation screen, the subject 257a, the address display field 257b displaying the e-mail address as the address information, the name of the medical facility that has been hospitalized (or will be hospitalized) 257c, the visit permission number 257d, the two-dimensional bar code 257e, Buttons 257f and 257g are displayed. The visit permission number is a number assigned by the mobile terminal 2 or the reception system for medical facilities, and by inputting this visit permission number into the reception device 1, it is possible to issue a visit certificate. The two-dimensional bar code 257e is information in which a visit permission number is coded, and by having the two-dimensional bar code 257e read by the two-dimensional bar code reader 15b of the reception device 1, it is possible to issue a surface elimination. As the visit permission number as the visit permission information, various forms of information can be used privately instead of the number.

If the user who has confirmed the contents of the visit invitation confirmation screen has no problem with the displayed contents, he / she operates the button 257g to send the information of the displayed contents to the destination information (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 visit invitation information to the medical facility system (S507). FIG. 9 (G) shows the data structure of the visit invitation information. The visit invitation information includes the patient ID of the hospitalized patient, the medical facility ID, the destination information (in this case, the e-mail address), the issued visit permission number, the transmission date and time, and the like. On the medical facility system side that has received the information, for example, the visit invitation information is stored in the database managed by the storage unit of the management computer 3.

The side invited to visit will receive a text with substantially the same content as the visit invitation confirmation screen shown in FIG. 25. In this embodiment, the hospitalization period, the available visit time, etc. are not included, but such information may be included in the content of the visit invitation. The person invited to visit (visitor) receives the visit certificate by inputting the visit permission number in the reception device 1 or having the reception device 1 read the two-dimensional bar code 257e received by the mobile terminal 2 or the like. It becomes possible to do.

FIG. 26 is a flow chart showing a visit reception process according to the present embodiment. The visit reception process is a reception process for a visitor invited to visit or a user who has registered a face in advance to meet with an inpatient. Conventionally, in various medical facilities, the name of the visitor, the name of the inpatient, the hospital room number, etc. are often recorded only on paper, which is not reliable in terms of security. In the present embodiment, by performing the visit reception process by the reception device 1, various records related to the visit are issued to the visitor invited to the visit or the user who has registered the face in advance. Has become possible, and the security of visits has been improved.

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 process of this embodiment, it is possible to issue a visitation certificate in three forms of a visitation permission number, a two-dimensional bar code, and face recognition, and selection buttons 130a to 130c corresponding to each are displayed. There is. In the visit reception process of the present embodiment, the user to be operated is photographed by the camera 13a (S602) regardless of the result of the visit, and the shooting information as a history is left. It should be noted that the timing of shooting can be appropriately set within the visit reception process.

When the selection button 130a is operated, that is, when the input of the visit permission number is selected (S603: Yes), the visit permission number authentication process (S604) is executed. In the visit permission number authentication process (S604), the visitor inputs the visit permission number received in advance by using the visit permission number input screen (not shown). The reception device 1 transmits the entered visit permission number to the management computer 3. The management computer 3 refers to the visit invitation information, authenticates based on whether or not the entered visit permission number is registered, and transmits the result to the reception device 1. When the receiving device 1 that has received the authentication result can be authenticated (S605: Yes), the first visit determination process (S630) is executed. On the other hand, when authentication cannot be performed (S605: No), a visit error screen (not shown) is displayed on the touch panel monitor 12 (S619).

FIG. 28 is a flow chart showing the first visit determination process (S630) according to the present embodiment. Even if the visit permission number is successfully authenticated, the inpatient may be discharged or may not be able to visit due to various reasons such as the condition of the inpatient. The first visit determination process (S630) decides whether or not to allow a visit 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 or not the target patient is in the hospital (S631). ). If you are not in the hospital (S631: Yes), the availability of visits is set to not possible (S638).

On the other hand, when the target patient is in the hospital (S631: Yes), it is determined whether or not it is within the visitable time (S632). The visitable time is set on 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), whether or not the visit is possible is set to be non-visitable (S638). On the other hand, if 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 visitation restriction information in the hospitalization-related information. When the visitor is restricted by referring to the visit restriction information (S633: Yes), whether or not the visit is possible is set to be non-visitable (S638).

When the visitor is not restricted (S633: No), it is determined whether or not the identification card is necessary by referring to the possibility of identification in the hospitalization-related information (S634). When it is determined that the ID card is necessary (S634: Yes), a message for placing the ID card is displayed on the scanner 15a of the reception device 1, and the ID card reading process is executed (S635). If the information on the ID card matches (S636: Yes), the availability of visits is set to allow visits (S637). On the other hand, if the ID card does not match (S636: No), whether or not to visit is set to not be possible (S638). If the ID card is not required (S634: No), the possibility of visitation is set to allow visitation (S637).

Here, the conformity judgment of the ID card is made by the visit invitation process, etc., and various information related to the ID card (name, address, various numbers of the ID card (for example, in the case of a driver's license, the license number, the insurance card) In this case, it is possible to register the insurance card number) in advance and check it against it. Alternatively, the employee of the medical facility can judge various information about the read ID card or be hospitalized. It may be presented to the patient for judgment, or the suitability may not be judged and only the read identification card may be saved.

Returning to the visit 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 (S614) for the visitor is executed. On the other hand, when it is determined that the visit is not possible (S606: No), the visit error screen (not shown) is displayed on the touch panel monitor 12 (S619).

The temperature measurement process at the time of check-in process was explained earlier, but in this embodiment, by performing the temperature measurement process not only for the patient but also for the visitor, it is possible that a virus or the like is brought in from the outside. It is possible to suppress it. 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. The determination threshold value at the time of the visit reception process is set lower than the determination threshold value at the time of the check-in process. This is because the patient accepted during the check-in process is sick and has some fever. In this way, by making the judgment threshold different, in the check-in process, patients with high fever such as influenza are isolated, and in the visit reception process, the judgment regarding fever is stricter, so that nosocomial infection is suppressed more reliably. 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 heat generation 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 companions is made on the touch panel monitor 12, and the visitor will touch-input the number of companions. In this embodiment, only the visitor inputs the operation of the reception device 1 as a representative, but when accompanied by a companion, the companion is also faced with the reception device 1 for temperature measurement processing and a camera. It may be possible to take a picture with 13a. If the temperature measurement process of the companion is not normal, only the companion, or all of the visitor and the companion may not be able to visit on the visit error screen.

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

FIG. 31 is a diagram showing a visitor certificate 45 according to the present embodiment. The visit certificate displays the name of the medical facility 45a, the date and time of issuance 45b, the name of the inpatient 45c, the hospital room number 45d, and the two-dimensional bar code 45e. 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 in 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. The gates and elevators may be permitted only on the route of the hospital room of the inpatient to be visited. In addition to these information, various information such as the route to the hospital room may be described in the visitation certificate. Further, in the present embodiment, the visit certificate is printed with a two-dimensional bar code, but instead of the two-dimensional bar code, a passing 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.

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

Whether or not the visit is possible is information indicating whether the visit was permitted (that is, the visit certificate was issued) or the visit was not permitted. The reception date and time is information indicating the date and time when the visit reception process was executed. The shooting information is the appearance of the visitor recorded by shooting with the camera 13a (S602). The temperature measurement information is information indicating the body temperature of the visitor measured by the temperature measurement process (S614). When the image taken by the camera 13a and the temperature measurement process are performed on the companion, the photographed information and the temperature measurement information of the visitor and the companion are recorded. The number of companions is information indicating the input result of the number of companions 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, which is compared with the record previously 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, a case where the use of the visit permission two-dimensional bar code 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 abbreviated as the process when the visit permission number is input (S603: Yes), because the visit permission number is only read by using the two-dimensional bar code reader 15b. The same is true. When the use of the visit permission 2D barcode is selected (S607), the visit permission 2D barcode is read by using the 2D barcode reader 15b, and the visit permission number included in the visit permission 2D barcode is used. Based on this, the visit permission number authentication process (S608) is executed. The visit permission number authentication process (S608) is the same as the visit permission number authentication process (S604) when the visit permission number is input.

If authentication is possible as a result of the visit permission number authentication process (S608) (S609), the first visit determination process (S630) is executed. This first visit determination process (S630) is the same as 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 cannot be performed (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, a case where the selection button 130c is selected on the selection screen of FIG. 27, that is, a case where performing face authentication is selected (S611: Yes) will be described. In the visit reception process of the present embodiment, if the user has performed the face registration process described in FIGS. 6 and 7 in advance, he / she is not the visitor invited by the visit permission number and the visit permission two-dimensional bar code. It is also possible to receive a visitation certificate. This is because the user who has performed the face registration process is a user who has visited the medical facility with the patient and is likely to be a user who is assisting the patient. Further, in the present embodiment, since the attribute information indicating the relationship between the patient and the user is registered in the face registration process, it is possible to determine whether or not the visit is possible by using the attribute information.

When the selection button 130c is selected (S611: Yes), the second face recognition process (S650) is executed. FIG. 29 shows a flow chart showing the second face recognition process (S650) according to the present embodiment. The second face authentication process (S650) is substantially the same as the first face authentication process (S300) executed in the check-in process described with reference to FIG. 16 in terms of authentication content.

When the second face recognition process (S650) is started, the reception device 1 starts shooting with the camera 13a (S651). Then, the auxiliary authentication information input screen is displayed (S652). The 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 having 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 taken by the camera 13a (S654). The receiving device 1 that has acquired the authentication result (S655: Yes) confirms the content of the authentication result (S656). If the authentication cannot be performed, the authentication result is set to disabled (S661).

On the other hand, when authentication is possible (S656: Yes), it is determined in the authentication result whether the number of inpatients corresponding to the face ID is singular (S657: No) or plural (S657: Yes). Normally, it is a rare case that multiple patients associated with oneself are hospitalized, but for example, when assistance is provided by a contractor (worker), there are multiple patients in one medical facility. It is conceivable that the inpatients are visited (assisted). In this way, in addition to corresponding to the face ID, when there are multiple inpatients (inpatients) (S657: Yes), the names of candidate inpatients are displayed on the inpatient selection screen ( S658) to select the target inpatient. When the target inpatient is selected on the inpatient selection screen (S659: Yes), the target inpatient is determined (S660).

If the authentication is successful as a result of the second face recognition process (S650), that is, if the target inpatient is determined, the process proceeds to the next second visit determination process (S670). On the other hand, if authentication cannot be performed, a visit error screen (not shown) is displayed on the touch panel monitor 12 (S619).

FIG. 30 is a flow chart showing a second visit determination process (S630) according to the present embodiment. Similar to the first visit determination process (S630), even if the authentication is successful, the inpatient cannot be visited if he / she is discharged. In the second visit determination process (S670), 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 or not the target patient is in the hospital. (S671). If you are not in the hospital (S671: No), whether or not you can visit is set to not be possible (S678).

Further, in the present embodiment, it is possible to manage the permission, disapproval, and permission time of the visit 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 they are relatives, they can be allowed to visit by 22:00, and if they are not relatives (for example, in the case of a trader), they can be allowed to visit by 18:00.

When the attribute information is within the first visit permission range (S672: Yes), for example, when the relatives are within the first degree, the current time is set for the first visit permission range. It is determined whether or not it is within the time. When the current time is within the first visitable time (for example, 9:00 to 22:00) (S673: Yes), whether or not the visit is possible is set so that the visit is possible (S674). On the other hand, when the current time is not within the first visitable time (S673: No), the visitability is set to no visit (S678).

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

In this way, when face recognition processing is selected in the visit reception process, the visitor can perform the visit without receiving an invitation from the inpatient in advance. In addition, it is not necessary to bring a visit permit number or a visit permit two-dimensional bar code, and it is possible to easily receive a visit certificate. Even if the patient is an inpatient who requires an ID card for the visit, it is possible to issue the visit certificate to the user whose face is registered in advance without presenting the ID card. ing. Further, in the present embodiment, since the attribute information indicating the relationship with the patient is registered at the time of the face registration process, it is possible to appropriately manage whether or not the visit is possible using the attribute information or the visitable time. It has become.

Returning to the visit reception process of FIG. 26, when it is determined that the visit is possible as a result of the second visit determination process (S670) (S613: Yes), the process after the temperature measurement process (S614) for the visitor is 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 explanation of the visit reception process has been explained above, in the reception system for medical facilities of the present embodiment, it is possible to invite the visitor to the visit using the mobile terminal 2 possessed by the inpatient or a related person. Will be. At that time, since the mobile terminal 2 capable of executing the visit invitation process is required to execute the function addition process face-to-face with the reception device 1 in advance, it is possible to improve the security in the visit. Become.

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

In medical facilities such as hospitals, nosocomial infections may occur due to influx of people from the outside. In particular, it is necessary to avoid hospital-acquired infections as much as possible when influenza, rubella, etc. are prevalent or during the period. Under these circumstances, allowing external visits as usual may allow the virus to be brought into the medical facility by the visitor. On the other hand, if all visits are blocked, it is possible that some inpatients will not be able to do personal belongings. In this way, the absence of visitors causes a burden not only on inpatients but also on staff on the medical facility side.

In the above-described embodiment, in the second face recognition process in the visit reception process, attribute information indicating the relationship between the user who applied for the visit (user to be authenticated in the face recognition process) and the patient (hospitalized patient) is used. Although it has been explained that the possibility of visitation and the limitation of visitation time are performed, it is also possible to set a user who will be a key person among the users registered in advance. The key person can be set, for example, on the attribute selection screen described with reference to FIG. 12. Alternatively, it may be possible to set it after the fact.

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

In the medical facility, in normal times, the visit reception process described with reference to FIG. 26 is executed to determine whether or not the visit is possible. On the other hand, in an emergency such as when a viral disease 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 a visit certificate is issued. In this way, in the modified example using special attribute information, the number of visitors to the hospital room is suppressed to an appropriate number by limiting the users who can visit to the hospital room to only the key person set as the inpatient in an emergency. However, it becomes possible to suppress nosocomial infections. In addition, it is possible to secure visitors who take care of the surroundings of inpatients and suppress the burden on the medical facility side.

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 the present invention also includes a configuration in which the configurations of the various embodiments are appropriately combined. It is a category of 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 Unit 11d: Image processing unit 26b: Wireless LAN communication unit 11e: Voice 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 17a: LAN communication unit 45c: Name 17b: Communication unit 45d: Hospital room number 18: Hard disk 45e: Two-dimensional bar code 21a: CPU 52: Router 21b: ROM 71: Hospital reception 21c: RAM 72: Doorway 21d: Image processing unit 121: Touch panel

Claims (2)

It is a reception system for medical facilities that includes a reception device and a program executed by a mobile terminal owned by the user.
The reception device has a user interface in which users perform face-to-face operations.
Addition of a function performed by performing an operation using the user interface and reading the code information displayed on the reception device with the mobile terminal, or reading the code information displayed on the mobile terminal with the reception device. Processing and
It is possible to execute the visit reception process to determine whether the visit is permitted or not based on the visit permission information entered by the visitor.
The program is a reception system for medical facilities that can send visit permission information that permits a visit to a visitor to a designated destination information, provided that the function addition process is executed. The reception device includes a camera and
The medical facility reception system according to claim 1 , wherein the function addition process captures a user who operates in front of the reception device by the camera and stores information at the time of function addition including image pickup information.

Images