JP7777928B2 - Message systems and mobile programs - Google Patents

Description

The present invention relates to a messaging system that enables users to send messages between their mobile devices at various facilities, as well as a messaging program that can be executed on the mobile devices.

Traditionally, medical treatment at medical facilities such as hospitals and clinics typically follows a flow of initial consultation, appointment, and follow-up visit. After the initial consultation or follow-up visit, patients can make a follow-up appointment to ensure smooth medical treatment.

However, some patients may forget to go to a medical facility when they return to Japan. In such cases, the medical facility or the patient will need to make another appointment. Furthermore, there may be empty seats when the patient returns to Japan, which could hinder smooth medical treatment.

In addition, large medical facilities such as general hospitals tend to be crowded due to the large number of outpatients, and outpatients are often forced to wait between reception and consultation. Taking this situation into consideration, Patent Document 1 discloses a consultation guidance system that includes a return-examination reception terminal that accepts return-examination requests from outpatients, a department reception terminal that accepts return-examination requests from outpatients to a department after the return-examination is accepted, a mobile device carried by the outpatient, and a patient information management server that, if the return-examination request is not accepted at the department reception terminal within a specified time after being accepted at the return-examination reception terminal, causes the mobile device to send a push notification informing the department of the return-examination request.

JP 2017-120470 A

In medical facilities, it is essential to keep information about patients as customers confidential, and careless leaking of such information could jeopardize the medical facility's credibility. Patent Document 1 discloses sending reception information via push notification, and also discloses sending an email if the patient does not show up at the reception desk after receiving the reception information. Sending an email requires the message content to be stored on an external email server, which is not necessarily desirable from an information security perspective.

For these reasons, it is difficult for medical facilities to send messages to their customers (patients, etc.). Furthermore, when using email, email addresses must be registered, but email addresses at medical facilities are typically registered by the patient or other user writing them down on paper. If the email address is entered incorrectly or misread, messages may not be sent or may be sent to the wrong person.

The present invention was developed in light of these circumstances, and aims to enable safe and reliable messaging to patients and other customers in medical facilities and other settings. The present invention can be used not only in medical facilities, but also in various other facilities where confidentiality of customer information is required, such as financial institutions such as banks and securities companies.

The message system according to the first-1 configuration is
A message system including a mobile terminal, a message management device installed in a facility, and a reception device installed in the facility,
The mobile terminal executes a function addition process, a setting process, and a message process,
The function addition process involves a user using the reception device to register facility user-related information, including identification information of the mobile terminal, in the mobile terminal;
The setting process executes settings necessary for message processing between the facility user and the message management device corresponding to the registered facility user related information, based on the registered facility user related information;
The message processing allows the device to receive messages sent from the message manager or to send messages to the message manager after the setting process is completed.
The setting process sets, in the message management device , identification information of the mobile terminal, identification information of the facility user, and the relationship of the facility user as information regarding the destination of a message to be sent by a message program executed in the message management device ;
When a facility user is selected, the message processing selects the relationship to the facility user set in the setting processing, and sets the mobile device of the relationship to the facility user as the message destination.

Furthermore, in the message system according to the first-second configuration,
The function addition process registers facility user-related information in the mobile terminal by having the reception device read the facility's usage ticket.

Furthermore, in the message system according to the first to third configurations,
The portable program is capable of executing function addition processing, setting processing, and message processing for each facility.

Furthermore, in the message system according to the first to fourth configurations,
The portable program enables function addition processing, setting processing, and message processing to be executed for each facility user.

Furthermore, in the message system according to the first to sixth configurations,
The message program is
A confirmation process for confirming the running status of a mobile program on the mobile terminal that is the destination of the transmission;
When the portable program is in an activated state, a transmission process is executed to transmit a message that can be notified by the portable program of the portable terminal to the portable terminal.

In addition, the portable program according to the first to seventh configuration is
A portable program executable on a portable terminal,
The mobile program causes the mobile terminal to execute a function addition process, a setting process, and a message process,
The function addition process uses a reception device installed in the facility to register facility user related information, including identification information of the mobile terminal, in the mobile terminal;
The setting process executes settings necessary for message processing between the facility user and the message management device corresponding to the registered facility user related information, based on the registered facility user related information;
The message processing allows the device to receive messages sent from the message manager or to send messages to the message manager after the setting process is completed.
The setting process sets the identification information of the mobile terminal, the identification information of the facility user, and the relationship to the facility user in the message management device as information regarding the destination of the message to be sent by the message program executed in the message management device .
Furthermore, a message management device according to configuration 1-8 includes:
A message management device used in a message system including a mobile terminal and a message management device installed in a facility,
The mobile device is
executes a setting process for setting, in the message management device , identification information of the mobile terminal, identification information of the facility user, and the relationship of the facility user as information regarding the destination of a message sent by a message program executed in the message management device;
The message management device
After the setting process is completed, the message manager is enabled to send messages.
When a facility user is selected, by selecting the relationship to the facility user set in the setting process, a message process is executed to set the mobile terminal of the relationship to the facility user as the destination of the message to be sent.
Furthermore, a message management device according to configuration 1-9 includes:
A message program executed on a message management device used in a message system including a mobile terminal and a message management device installed in a facility,
The mobile device is
executes a setting process for setting, in the message management device , identification information of the mobile terminal, identification information of the facility user, and the relationship of the facility user as information regarding the destination of a message sent by a message program executed in the message management device;
The message program is
After the setting process is completed, the message manager is enabled to send messages.
When a facility user is selected, by selecting the relationship to the facility user set in the setting process, a message process is executed to set the mobile terminal of the relationship to the facility user as the destination of the message to be sent.

The message system disclosed in this specification also has the following configurations 2-1 to 2-8.

The message system according to the second-first configuration is
A message system including a portable program executable on a portable terminal and a message program executable on a message management device installed in a facility,
The message program is
A confirmation process for confirming the running status of a mobile program on the mobile terminal that is the destination of the transmission;
When the portable program is in an activated state, a transmission process is executed to transmit a message that can be notified by the portable program of the portable terminal to the portable terminal.

Furthermore, in the message system according to the second-2 configuration,
If the portable program is not running, a notification process is performed to send a notification to the portable terminal to prompt the portable program to start up.

Furthermore, in the message system according to the second-third configuration,
The message program executes a public key acquisition process to acquire the public key of the portable program;
In the sending process, when a message is sent, encryption is performed based on the acquired public key.

Furthermore, in the message system according to the second-fourth configuration,
In the public key acquisition process, a public key is acquired from a message server that manages public keys for portable programs.

Furthermore, in the message system according to the second-fifth configuration,
The public key acquisition process is executed when message acquisition settings are made in the portable program.

Furthermore, in the message system according to the second-sixth configuration,
The recipient of the message can be set by a combination of name and relationship.

Furthermore, in the message system according to the second-sixth configuration,
It is possible to set whether or not a message can be sent for each recipient.

In addition, the message program according to the second-seventh configuration is
A message program executed on a message management device installed in a facility,
A confirmation process for confirming the running status of a mobile program on the mobile terminal that is the destination of the transmission;
When the portable program is in an activated state, a transmission process can be executed to transmit a message that can be notified by the portable program of the portable terminal to the portable terminal.

Furthermore, the message system disclosed in this specification has the following configurations 3-1 to 3-3.

The message system according to the third-1 configuration is
A message system including a portable program executable on a portable terminal and a message program executable on a message management device,
The portable program is assigned subscriber information including user identification information and a relationship to the user;
The message program allows a user to select a user's identification information and a relationship to the user, thereby sending a message to a portable program to which the corresponding subscriber information has been assigned.

Furthermore, in the message system according to the third-2 configuration,
The message program registers the subscriber information sent from the portable program, and allows the user to select user identification information and the relationship to the user from the registered subscriber information.

Furthermore, in the message system according to the third-third configuration,
The portable program stores information on a plurality of subscribers.

The message system and mobile program according to the first configuration (configurations 1-1 to 1-6) allows for easy message transmission between a mobile device and a message management device by performing function addition processing and configuration processing, without the need to transmit email addresses by hand or other means. Furthermore, since a reception device installed within the facility is used, messages can be configured safely.

Furthermore, the message system, message management device, and message program according to the second configuration (configurations 2-1 to 2-8) check the running status of the portable program, and if the portable program is running, send a message that can be notified by the portable program on the portable device to the portable device. This makes it possible to send (or receive) messages directly between the portable device and the message management device, thereby improving the confidentiality of personal information handled within the facility.

Furthermore, with the message system according to the third configuration (configurations 3-1 to 3-3), by registering the user's identification information (user ID or at least one of the user's name) and the user's relationship to the user (self, spouse, parent, child, etc.) as subscriber information on the mobile device, the message program can send messages specifying the user's identification information and relationship to the user. In particular, in medical facilities, it is possible to send messages specifying the user (patient) and their relationship to the user. Therefore, it is possible to send messages for the same patient based on their relationship to the patient, such as messages to be conveyed to the patient and their relatives, messages to be conveyed only to the patient, or messages to be conveyed only to their relatives.

FIG. 1 is a diagram showing the configuration of a reception system according to an embodiment of the present invention; FIG. 10 is a front view of the reception device according to the present embodiment. FIG. 1 is a block diagram showing the configuration of a reception device according to the present embodiment. FIG. 1 is a block diagram showing the configuration of a mobile terminal according to an embodiment of the present invention; FIG. 10 is a diagram showing an initial screen of the reception device according to the embodiment; FIG. 10 is a diagram showing an outpatient screen of the reception device according to the present embodiment. FIG. 10 is a flowchart showing check-in processing according to the present embodiment. FIG. 10 is a diagram showing a check-in confirmation screen according to the embodiment; FIG. 10 is a diagram showing various data configurations used in the reception system according to the present embodiment. FIG. 10 is a flowchart showing a function acceptance process according to the present embodiment; 10A to 10C are diagrams showing various screens of a mobile terminal according to the present embodiment; 10A to 10C are diagrams showing various screens of a mobile terminal according to the present embodiment; FIG. 1 is a block diagram showing the configuration of a message system according to an embodiment of the present invention. 10A to 10C are diagrams showing various screens of a mobile terminal according to the present embodiment; FIG. 10 is a flowchart showing initial registration processing of a mobile terminal according to the present embodiment; FIG. 10 is a flowchart showing a handshake process according to the present embodiment. FIG. 10 is a diagram showing various data configurations used in the message system according to the present embodiment. FIG. 10 is a flowchart showing a transmission process (when a program for a mobile terminal is started) according to the present embodiment. FIG. 10 is a flowchart showing a transmission process according to the present embodiment (when the mobile terminal program is not running). FIG. 10 is a diagram showing a message client screen according to the present embodiment; FIG. 10 is a diagram showing a message client screen according to the present embodiment; 10A to 10C are diagrams showing various screens of a mobile terminal according to the present embodiment;

Figure 1 shows the configuration of the reception system according to this embodiment. The reception system according to this embodiment is installed in a lobby located near the entrance/exit 72 of a medical facility. The reception system is composed of reception devices 1a and 1b located in the lobby and operated by users, and a management computer 3 located in the hospital reception 71 or elsewhere and operated by employees. Note that multiple reception devices 1a and 1b (two in this embodiment) are installed so that services can be provided to multiple users simultaneously.

Reception devices 1a and 1b and management computer 3 are connected to each other via LAN 51 so that they can communicate with each other. Connected to management computer 3 are a monitor 42 for displaying various information, and input devices 41 such as a keyboard and mouse for accepting input from employees. Also connected are a receipt printer 44 for printing on receipt-type paper, and a card reader 43 for reading (or potentially writing to) information stored on patient registration cards.

Figure 2 is a front view of the reception device 1 according to this embodiment. The reception device 1 is a device that can provide various services to the user who sits face-to-face and operates it, such as new patient reception and returning patient reception (also known as check-in). The reception device 1 of this embodiment is configured with a touch panel monitor 12, card reader 14, scanner 15a, two-dimensional barcode reader 15b, receipt printer 16a, printer 16b, camera 13a, and infrared camera 13b. These components function as a user interface for the user who operates the reception device 1.

The touch panel monitor 12 displays visual information to the user who is operating the device face-to-face, and is capable of accepting touch operations from the user. Above the touch panel monitor 12 are a camera 13a that can capture an image of an area including the face of the user who is operating the device face-to-face, and an infrared camera 13b. Camera 13a is used to capture an image of the face of the user who uses the device, and infrared camera 13b is used to capture an image of the face of the user who uses the device and perform a temperature measurement process to detect the user's body temperature.

The card reader 14 reads various information, such as the patient ID, stored on a magnetic card or IC card (equivalent to a facility card) held by the user. The card reader may also be equipped with a function to read credit cards used for paying medical expenses. The scanner 15a is a flatbed type designed to read health insurance cards, and is used to read the health insurance card held by the user when it is required to present the card, such as when accepting a return visit or for the patient's first consultation of the month.

The 2D barcode reader 15b is capable of reading various types of 2D barcodes, such as 2D barcodes printed on printed materials or 2D barcodes displayed on the mobile terminal 2. Note that instead of 2D barcodes, the object to be read may be a 1D barcode or other form of code information, in which case a code reader (code reading device) appropriate for the object to be read is used instead of the 2D barcode reader 15b. Furthermore, instead of providing both the scanner 15a and the 2D barcode reader 15b, a common reading unit, such as a camera, may be used.

The reception device 1 of this embodiment is equipped with a receipt printer 16a and a printer 16b to provide paper media to the user. The receipt printer 16a is a simple printer that prints on thermal paper used as receipts, and is used to print reception completion forms issued when receiving return visits, appointment forms issued when receiving appointments, etc. The printer 16b is a laser printer, inkjet printer, or other printer that prints using toner or ink on regular paper, and is used to print medical statements, receipts, etc. issued when paying medical expenses.

Figure 3 is a block diagram showing the configuration of the reception device 1 according to this embodiment. Similar to a typical computer, the reception device 1 is configured with a CPU 11a as a control unit, ROM 11b, RAM 11c, image processing unit 11d, and audio processing unit 11e. It also has a storage unit such as a hard disk 18 for storing various types of information. Furthermore, a card reader 14, scanner 15a, two-dimensional barcode reader 15b, receipt printer 16a, printer 16b, camera 13a, infrared camera 13b, and LAN communication unit 17 are connected via an interface 19, enabling control by the control unit.

A touch panel monitor 12 is connected to the image processing unit 11d. The touch panel monitor 12 is configured with a display unit 122 that displays various information to the user, and a touch panel 121 that accepts touch operations by the user. The touch panel 121 is connected to the interface 19, and is capable of transmitting touch operations by the user to the control unit. A speaker that transmits auditory information to the user is connected to the audio processing unit 11e.

The interface 19 is connected to the camera 13a, infrared camera 13b, card reader 14, receipt printer 16a, printer 16b, scanner 15a, two-dimensional barcode reader 15b, and touch panel 121 described in Figure 2, and performs various processes under the control of the control unit. In addition, the interface 19 is connected to a LAN communication unit 17 as a means for performing various communications. The LAN communication unit 17 is connected to a LAN 51, and is capable of communicating with various information processing devices on the LAN, such as the management computer 3 described in Figure 1, or with the Internet via a router 52.

As described above, the reception system described using Figures 1 and 2 can be used to provide various services to users. Here, we will explain the configuration of the mobile device 2 possessed by the user. The mobile device 2 is a smartphone, tablet device, or the like, and is a device that is owned, carried, and used by the user.

Figure 4 is a block diagram showing the configuration of the mobile device 2 according to this embodiment. The mobile device 2 is configured with a CPU 21a as a control unit, ROM 21b, RAM 21c, image processing unit 21d, and audio processing unit 21e. It also has a non-volatile storage unit 22 such as flash memory. Furthermore, 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), as well as an input switch 27, are connected via an interface 23, enabling control by the control unit.

A touch panel monitor 25 and a camera 24 are connected to the image processing unit 21d. The touch panel monitor 25 is configured with a display unit 252 that displays various information to the user, and a touch panel 251 that accepts touch operations by the user. The camera 24 is located on the back of the mobile terminal 2, etc., and is capable of taking still images and videos. Note that multiple cameras 24 may be located not only on the back but also on the front, for example. A speaker 28a that conveys auditory information to the user and a microphone 28b that acquires acoustic information are connected to the audio processing unit 21e. Note that the touch panel monitor 25 and input switches function as a mobile terminal-side user interface for the user operating the mobile terminal 2.

Figure 5 is a diagram showing the initial screen displayed on the touch panel monitor 12 of the reception device 1 according to this embodiment. The initial screen displays buttons 121a-121c, which ask the user whether they are an outpatient, inpatient, or visitor; button 121d for adding functions to the smartphone (mobile terminal 2); and button 121e for switching to a language other than Japanese. When the user selects one of buttons 121a-121e, the corresponding process is executed. Note that these various services may be unavailable during certain hours. For example, it is preferable to enable only button 121a, which handles various outpatient receptions, immediately after the medical facility opens. The reception device 1 executes processes other than repeat patient reception, making it possible to prevent the queue of users waiting at the reception device 1 from being filled up.

The following describes the functions used for outpatients on the initial screen in Figure 5, i.e., the functions that occur when button 121a displayed in Figure 5 is selected. When button 121a, which selects outpatient status, is pressed on the initial screen, the screen transitions to the outpatient screen shown in Figure 6. This outpatient screen displays buttons 122a-122d labeled "New Patient Reception," "Returning Patient Reception," "Medical Fee Payment," and "Appointment Request," as well as button 122e for returning to the initial screen.

Here, we will explain the various services displayed on each button 122a-122d. Touching and selecting button 122a (new patient reception) starts the new patient reception process for a new patient, i.e., a patient visiting this medical facility for the first time. The new patient reception process uses the scanner 15a of the reception device 1 to read identification documents such as a My Number card or driver's license, as well as health insurance cards. A message is displayed on the touch panel monitor 12 informing the user to wait until registration is complete, and the new patient reception process on the reception device 1 side is completed. The read information is sent to the management computer 3, and after processing by a clerical staff member or other personnel, is registered as basic patient information in the medical facility's database.

The process initiated by touching and selecting button 122c (revisit reception) is the process (check-in process) for accepting a patient for a second or subsequent visit to a medical facility. In this embodiment, the revisit reception process targets users who have made a prior appointment, such as at a previous visit, but it may also be possible to accept users who have not made an appointment. For this reason, the revisit reception process will be referred to as the check-in process.

The process started by touching and selecting button 122b (Pay medical fees) is a process for paying medical fees for users whose medical treatment has ended. The reception device 1 of this embodiment allows payment by credit card using the card reader 14, but may also be equipped with a cash handling function to allow payment by cash. The process started by selecting button 122d (Request appointment) is a process for reserving the next medical appointment date and time.

The process initiated by selecting button 121d (adding functions to smartphone) on the initial screen described in Figure 5 is a process for adding functions to a portable program (also called an "app") running on the user's mobile device 2. The user downloads the portable program to be used at medical institutions to the mobile device 2 via an internet connection. The basic functions of this portable program include the acquisition of basic information such as the locations of various medical institutions, or the use of waiting numbers to notify the user of the current progress of treatment at each medical institution.

Furthermore, various additional functions that can be executed by the mobile device 2 can be added, such as repeat visit reception (check-in processing), medical fee payment, and appointment requests, which are executed by the reception device 1 as described in Figure 5. These additional functions require the user (patient, etc.) using the mobile device 2 to be identified, and important information such as the patient ID must be handled on the mobile device 2 side. Therefore, incorporating such additional functions as basic program functions is not desirable from a security perspective. Furthermore, adding functions solely to the mobile device 2 is also not desirable from a security perspective. There is also the possibility of unauthorized use by exploiting security flaws. Therefore, in this embodiment, when adding functions to a portable program executed on the mobile device 2, the reception device 1 is used.

Figure 7 is a flow diagram showing the check-in process according to this embodiment. The check-in process is executed by the reception device 1, and is performed by the user facing the reception device 1 and operating the touch panel monitor 12, etc. The check-in process is started by operating button 122c (return visit reception) on the outpatient screen in Figure 6. Note that the normal check-in process at the reception device 1 is started when the reception start time set by the medical facility arrives, or by an instruction given by a medical facility employee, etc.

When the check-in process begins, a guide screen is displayed on the touch panel monitor 12 prompting the user to insert their patient registration card or to hold the two-dimensional barcode displayed by the patient registration card function of the mobile terminal 2 over the two-dimensional barcode reader 15b (S100). The patient registration card function of the mobile terminal 2 will be described in detail later. When the user inserts the patient registration card into the card reader 14 (S101: Yes), the card reader 14 reads the patient ID stored on the patient registration card (S102). Also, when the two-dimensional barcode displayed on the mobile terminal 2 is read by the two-dimensional barcode reader 15b (S101: Yes), the reception device 1 reads the patient ID from the two-dimensional barcode. The reception device 1 sends a check-in request including the read patient ID to the management computer 3 (S103).

Figure 9 shows the various data configurations used in the reception system of this embodiment. Basic patient information registered in advance at the time of the first consultation, etc., is recorded in the management computer 3. As shown in Figure 9 (A), the basic patient information includes information about the patient as a user, such as the patient ID, facility ID, name, address, gender, date of birth, personal identification information, and health insurance card information.

In this embodiment, a patient ID and a medical facility ID are combined and used as a system ID. The reception system of this embodiment is designed to be usable at multiple medical facilities. Therefore, by referencing the system ID, which is a combination of a patient ID and a medical facility ID, it is possible to identify the medical facility and the patient.

Personal identification information is various information that can identify an individual, such as the number written on a driver's license or My Number card presented by the patient at the time of initial consultation, or a copy of such information. Health insurance card information includes the health insurance card type, health insurance card number, expiration date, etc. If a My Number card can be used as an health insurance card, personal identification information and health insurance card information can also be integrated with information related to the My Number card.

The management computer 3 also stores appointment information related to medical appointments. As shown in Figure 9 (B), the appointment information includes the patient ID, appointment date, appointment time slot, department ID, and doctor ID. In this embodiment, the appointment format specifies the appointment date and appointment time slot, but the appointment format is not limited to this. Various formats are possible, such as specifying only the appointment date, or specifying the appointment date and appointment time. The information in the appointment information will be changed as appropriate depending on the appointment format of the medical facility.

When the management computer 3 receives a check-in request, it references the patient ID included in the check-in request and searches for the corresponding appointment information. If there is no appointment information corresponding to the patient ID, or if the appointment date of the appointment information corresponding to the patient ID is not for the current day, it sends error information to the reception device 1. If error information is received (S104: Yes), the reception device 1 displays a check-in error screen on the touch panel monitor 12 notifying that there is no appointment and the request could not be accepted (S114).

On the other hand, if the management computer 3 finds appointment information that corresponds to the patient ID and has an appointment date of the current day, the management computer 3 sends appointment confirmation information to the reception device 1. The appointment confirmation information includes various information based on the appointment information, such as the patient name, appointment date, appointment time slot, department name, doctor name, etc. When the reception device 1 receives the appointment confirmation information (S105: Yes), it displays a check-in confirmation screen based on the received appointment confirmation information (S108). In this embodiment, the infrared camera 13b is used to take the user's temperature before displaying the check-in confirmation screen.

As explained in FIG. 2, the reception device 1 is equipped with an infrared camera 13b capable of capturing an image of an area including the user. Temperature is measured using this infrared camera 13b (S106). In this embodiment, the body temperature near the temples of a person, where accurate temperature measurement is possible, is used. Furthermore, to improve the accuracy of the temperature measurement results, the body temperature near the temples is corrected based on the temperature distribution over a wide area of the face and used as the temperature measurement result. Camera 13a may also be used to accurately detect the temple position. If the temperature measurement result is abnormal (S107: No), that is, if the person is thought to have a high fever due to influenza or other infections, a fever warning screen is displayed on the touch panel monitor 12 (S112), and fever warning information is sent to the management computer 3 (S113).

The fever warning screen displays a message informing the user that they have a fever and are being asked to move to an isolation space or similar location. Furthermore, upon receiving the fever warning information, the management computer 3 notifies employees that a patient has developed an abnormal fever, along with the identification information of the reception device 1. By taking measures at check-in, such as isolating users with influenza when accepting returning patients, it is possible to prevent hospital infections. In addition to the fever warning screen, the reception device 1 may also be equipped with a notification means for sending notifications around the reception device 1. For example, a notification light could be installed on the top of the reception device 1, and turned on to notify employees waiting around the reception device 1, or a notification could be provided by audio. Furthermore, temperature measurement using the infrared camera 13b is not limited to the timing described in this embodiment, and may be performed at an appropriate timing during the regular check-in process.

If the temperature measurement result is abnormal (S107: No), the use of the reception device 1 may be temporarily suspended. The suspension of use of the reception device 1 continues until the medical facility administrator has completed disinfection. A message such as "Please wait until cleaning is complete" is displayed on the touch panel monitor 12, preventing the next user from using the device. If the medical facility administrator determines that cleaning of the reception device 1 is necessary based on a notification to the management computer 3 or the status of the notification light, the administrator thoroughly cleans the touch panel monitor 12 of the reception device 1 and then resumes suspension of the reception device 1. The reception device 1 can be resumed by performing a specified operation on the reception device 1 or by remotely canceling the suspension from the management computer 3. In this way, even if a user suspected of infection is using the device, the spread of infection can be curbed by temporarily suspending use.

On the other hand, if the temperature measurement result is normal (S107: Yes), the reception device 1 displays a check-in confirmation screen on the touch panel monitor 12 based on the received appointment confirmation information (S108). Figure 8 is a diagram showing the check-in confirmation screen according to this embodiment. The check-in confirmation screen displays a consultation content display field 123a, including the medical department, doctor's name, and appointment time slot, a cancel button 123b, and a confirm button 123c. As can be seen from the check-in confirmation screen displayed in Figure 7, in this embodiment, it is possible to visit multiple departments during a single visit. In this case, the check-in confirmation screen is displayed based on the corresponding multiple appointment information (S108). If there are no problems with the consultation content, the user operates the confirm button 123c to confirm the consultation content for that day (S109: Yes). On the other hand, if the user wants to cancel the consultation content, they can select the item (such as the department) they want to cancel and operate the cancel button 123b to cancel the appointment corresponding to that item.

If the confirmation button 123c is touched (S109: Yes), the reception device 1 sends confirmation instruction information to the management computer 3 (S110). Based on receiving the confirmation instruction information, the management computer 3 adds the corresponding appointment information to the consultation queue as consultation information. A consultation queue is set up for each doctor in the corresponding department, and consultations are generally carried out in the order of the consultation queue. The reception device 1 also prints out a reception completion slip for the user using the receipt printer 15 (S111).

The reception completion slip is printed with the department, doctor's name, and reservation time slot included in the appointment information, as well as a waiting number corresponding to the order of reception and a two-dimensional barcode. Note that, if the patient visits multiple departments, as in this embodiment, a waiting number may be issued for each department. The two-dimensional barcode printed on the reception completion slip is information for verification by an information processing device (not shown) located in the department at the time of the visit. The information processing device located in the department is connected to management computer 3 via LAN 51, and the two-dimensional barcode read by the information processing device can be used to verify the patient's identity.

The check-in process executed by the reception device 1 has been explained above. Next, we will explain the function addition process using the reception device 1. The function addition process is a process for adding various functions, such as a patient registration card function and a message function, to the mobile device 2 carried by the user. In this embodiment, these additional functions are not performed by operating the mobile device 2 alone, but are performed in cooperation with the reception device 1 installed within the medical facility, thereby improving the security of various information.

Figure 10 is a flow diagram showing the function addition process according to this embodiment. This process is initiated by selecting the button 121d labeled "Add function to smartphone" in Figure 5 on the reception device 1. When the process begins, a screen prompting the user to insert their patient card is displayed on the touch panel monitor 12. When the user inserts the patient card into the card reader 14 (S201: Yes), the card reader 14 reads the patient ID stored on the card (S202). The reception device 1 also begins capturing images using the camera 13a (S203). Note that the camera 13a continues to capture images (video or multiple still images), and later selects the best shot from the captured images that is suitable for identifying the patient.

The reception device 1 transmits the read patient ID to the management computer 3 and acquires the patient basic information corresponding to the patient ID from the management computer 3 (S204). Note that the acquired patient basic information does not necessarily have to be all of the information contained therein, but may be only a necessary portion of the information. After that, a function addition confirmation screen including a two-dimensional barcode to be read by the mobile terminal 2 is displayed on the touch panel monitor 12 (S205). This two-dimensional barcode contains information for identifying the patient (corresponding to the "facility user related information" according to the present invention). Note that the patient ID is preferably encrypted in the two-dimensional barcode.

The user uses the launched mobile program (app) to have the camera 24 of the mobile device 2 read the 2D barcode displayed on the touch panel monitor 12 (this corresponds to a function addition process on the mobile device 2 side). Figure 9 (C1) shows one form of the data structure contained in the 2D barcode, which includes the patient ID, medical facility ID (system ID), name, date of birth, and device ID for identifying the reception device 1 being used. The 2D barcode read by the camera 24 is decrypted and converted into information on the mobile device 2. Of the read information, the patient ID, medical facility ID, name, and date of birth, which are necessary for using the mobile device 2 as a patient registration card, are stored (registered) on the mobile device 2 as patient registration card information.

Figures 11 and 12 are diagrams showing various screens of the mobile device 2 according to this embodiment. Figure 11 (A) is the initial screen displayed on the touch panel monitor 25 of the mobile device 2. The initial screen displays the currently selected medical facility name 251a as well as various buttons 251b to 251j. Button 251b is a button for using the mobile device 2 as a patient registration card (patient registration card function), and by completing the function addition process described in Figure 10, the mobile device 2 can be used as a patient registration card that can be accepted by the reception device 1. The mobile device 2 can display a two-dimensional barcode as a patient registration card on its touch panel monitor 25 for check-in.

Button 251c is used to pay medical expenses. After receiving medical treatment, the user can operate this button 251c to select payment by credit card, payment at a convenience store, etc. Therefore, by using this function, it is possible to pay medical expenses without having to visit reception device 1 or the reception desk.

Button 251d is a button that allows a hospitalized user to send information for issuing a visiting pass to relatives, friends, acquaintances, etc. by email. Using this function, a hospitalized user can send emails to relatives, friends, acquaintances, and other people who are permitted to visit. The email contains information for issuing a visiting pass, such as a two-dimensional barcode or a web address for obtaining the two-dimensional barcode, and a visiting permission number. The visitor can receive a visiting pass that allows them to visit by having the reception device 1 read or inputting this information.

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

Button 251f is a function that can be executed after the function addition process has been performed, and is a messaging function that allows you to receive messages from medical facilities and send messages to medical facilities. This messaging function allows you to safely send and receive messages to and from medical facilities, and will be explained in detail later.

Button 251g is a function that can be executed after the function addition process has been performed, and allows you to make an appointment for the next consultation date and time at the selected medical facility. Note that on the initial screen in Figure 11 (A), buttons indicated by dashed lines are functions that are not used at the selected medical facility. This takes into account the different specifications of each medical facility. In this embodiment, reservation requests using button 251g cannot be used.

Button 251h is a button for referring to instructions on how to use the mobile program (app). Button 251j is a button for switching to a language other than Japanese.

Next, we will explain the screen transitions that occur when button 251b, which is used for the function addition process, is operated. When using the mobile terminal 2 in place of a patient registration card, it is necessary to execute the function addition process with the reception device 1 and register information such as a patient ID on the mobile terminal 2. When button 251b is operated, if no information has yet been registered on the mobile terminal 2, the terms of use in Figure 11 (B) will be displayed first. Although Figure 11 (B) only displays "Terms of Use," in reality, details of the terms of use will be displayed here. Also displayed are button 252a, which reads "Agree," and button 252b, which reads "Do not agree." A user who agrees to the displayed terms of use operates button 252a to proceed to the screen in Figure 11 (C).

Figure 11 (C) shows the screen when the patient card has not yet been registered. The user can proceed to the screen shown in Figure 12 (D) by operating button 253 labeled "Register Patient Card." Figure 12 (D) is a screen that prompts operation on the reception device 1 side. This screen also displays button 254 labeled "Read 2D Barcode." Operating this button 254 transitions to the reading screen shown in Figure 12 (E). The reading screen displays a monitor field 256a that displays the image being captured by camera 24, and a cancel button 256. While checking the image in monitor field 256a, the user can capture the function addition confirmation screen displayed in S205 during the function addition process executed by reception device 1.

After reading the two-dimensional barcode displayed on the reception device 1, the mobile device 2 uses the mobile line communication unit 26a to send registration request information to a management server (not shown) on the Internet. Figure 9 (D) is a diagram showing the data structure of the registration request information. The registration request information includes the patient ID, medical facility ID, and terminal ID associated with the mobile device 2. The terminal ID may be an ID unique to the mobile device 2 or an ID unique to the mobile program (app). The management server receives the registration request information from the mobile device 2 via the mobile line network and the Internet, and sends it to the management computer 3 of the reception system that uses the reception device 1 with the device ID. The management computer notifies the reception device 1 with the device ID included in the registration request information that it has received the registration request information.

When the reception device 1 confirms that the management computer 3 has received the registration request information (S206: Yes), the reception device 1 selects the best shot that best captures the user's face from the video or multiple still images continuously captured by the camera 13a, records this as shooting information (S207), and sends it to the management computer 3 (S208), thereby completing the function addition process.

Upon receiving the imaging information, the management computer 3 registers the mobile device registration information based on the previously received registration request information and imaging information. Figure 9 (E) shows the data structure of the mobile device registration information. The mobile device registration information includes the patient ID, medical facility ID, terminal ID of the mobile device 2, device ID of the reception device 1, registration date and time indicating the date and time of registration, and imaging information taken by camera 13a. The mobile device registration information is used to identify whether the mobile device 2 is valid, using the terminal ID included therein. If a problem occurs after adding a function, this mobile device registration information can be referenced and used as a history of when and who registered the function.

On the other hand, if the reception device 1 cannot receive the terminal ID of the mobile device 2 (S206: No), the function addition process ends after a certain timeout period has elapsed (S209: Yes). In this case, the photographic information captured by the camera 13a is discarded (S210).

As described above, in this embodiment, when adding a function such as a patient registration card function to the mobile terminal 2, the user is required to perform the function addition process by interacting with the reception device 1. This makes it possible to prevent various problems, such as security and fraudulent 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 system ID. However, by providing this information from the reception system to the mobile terminal 2, as in this embodiment, it is possible to ensure accuracy and confidentiality.

Figure 12(F) shows the screen of the mobile device 2 when the function addition process is complete. This screen is transitioned to by operating button 251b shown in Figure 11(A). In this embodiment, it is possible to register patient card information for multiple people, and it is possible to register patient card information for not only the user himself/herself, but also the user's relatives or the user's (nursing provider's) care recipients. In the example of Figure 12(F), two patient card display areas 255a and 255b are displayed, and patient cards for two people have been registered. The user can move either patient card display area 255a or patient card display area 255b to the foreground and use it by touching the patient card display area 255a or 255b they wish to use. In the example of Figure 12(F), patient card display area 255a is displayed in the foreground and is ready for use.

The patient appointment card display area 255a displays a button 255c labeled "Message Settings," a button 255d labeled "Delete," and a two-dimensional barcode 255e. Operating button 255c configures the message function, which will be explained later. Operating button 255d makes it possible to delete the selected patient appointment card display area 255a and the corresponding information. The two-dimensional barcode 255e is a two-dimensional barcode version of the patient appointment card information registered on the mobile device 2. In this embodiment, the two-dimensional barcode 255e can also be used as a patient appointment card by having the reception device 1 read it.

In this embodiment, various information is sent and received by displaying a two-dimensional barcode on the reception device 1 and reading it with the mobile terminal 2. However, instead of this, a two-dimensional barcode including a terminal ID may be displayed on the mobile terminal 2 and read by the two-dimensional barcode reader 15b on the reception device 1. In this case, the reception system will use the mobile network to send various information required for adding functions (at least the patient ID, medical facility ID, etc. required to identify the user) to the mobile terminal 2 identified by the terminal ID.

Alternatively, the two-dimensional barcode may not include the information shown in FIG. 9 (C1), but may instead include the device ID of the reception device 1, as shown in FIG. 9 (C2), as authentication information. The mobile device 2 that receives the two-dimensional barcode transmits the mobile device authentication information to the reception system via the mobile network or the Internet, and receives from the reception system the information necessary for adding functions (at least the patient ID, medical facility ID, etc. required to identify the user). In this manner, there is no need to display confidential information in a two-dimensional barcode, making it possible to prevent information leaks caused by photographing or copying the two-dimensional barcode.

Next, the message function of this embodiment will be described. Figure 13 is a block diagram showing the configuration of the message system of this embodiment. The message system of this embodiment is configured with management computers 3a and 3b (corresponding to the "message management device" of the present invention) installed in each medical facility, and a message server 62. In addition, the external configuration of the message system includes a mobile terminal 2a (first OS), a mobile terminal 2b (second OS), a first notification server 61a (for the first OS), and a second notification server 61b (for the second OS).

Management computers 3a and 3b (corresponding to the "message management device" according to the present invention) are installed within each medical facility and perform various processes, such as creating, sending, and receiving messages. In addition to management computers 3a and 3b, information processing devices capable of performing various message-related processes may also be installed within the medical facility. These information processing devices are connected to the network within the medical facility and, like management computers 3a and 3b, are able to check messages received from mobile terminals 2a and 2b or send messages to mobile terminals 2a and 2b.

Management computers 3a and 3b are connected to the Internet via routers 52a and 52b. Management computers 3a and 3b are also connected to a message server 62 via a VPN (Virtual Private Network).

As mentioned above, users such as patients own mobile devices 2a and 2b and can use various functions using the mobile programs on the mobile devices 2a and 2b. In this embodiment, it is assumed that the mobile devices 2a and 2b have two types of operating systems (OS). A first notification server 61a (for the first OS) and a second notification server 61b (for the second OS) corresponding to the OS on each mobile device 2a and 2b are provided. These first notification server 61a (for the first OS) and second notification server 61b (for the second OS) are managed by the management company of the corresponding OS, and can check various statuses of the mobile devices 2a and 2b on which the corresponding OS is installed, or send notifications to the mobile devices 2a and 2b.

The message server 62 is a server set up on the Internet to implement the messaging function of this embodiment. In this embodiment, it enables secure message transmission and reception between the management computers 3a, 3b and the mobile terminals 2a, 2b. The message server 62 of this embodiment has the function of connecting the mobile terminal 2 (or management computer 3) that is the message sender with the management computer 3 (or mobile terminal 2) that is the message destination, but does not store or preserve the messages to be sent. In other words, it functions as a tunnel between the mobile terminal 2 and the management computer 3.

Conventionally, when sending email using a mobile device 2, the recipient's address is provided and the email is sent to that address. If a medical facility wants to send an email message to mobile devices 2a and 2b, it could ask for the email address of a user, such as a patient, in advance and then send the email to that address.

Here, the following problems can be expected with conventional email sending. Patients and other users' email addresses are collected by having them write them down on paper, but it is possible that the email address written down may be incorrect or may be misread, making it impossible to collect the email accurately. This can lead to the problem of not being able to send important messages even after collecting the email address.

In addition, traditional email transmissions are carried out via mail servers installed on the Internet. The mail server temporarily stores the email to be sent before sending it, and the email is sent via multiple mail servers. This means that information handled by medical facilities is exposed on the Internet, raising security concerns.

Although medical facilities desire an easy way to convey messages to patients and others, the above-mentioned circumstances have made it difficult to send messages via email. This embodiment takes these circumstances into consideration and aims to realize a highly secure messaging function by reliably identifying the recipients of messages, such as patients.

The message function of this embodiment allows messages to be sent and received between the management computers 3a and 3b within the medical facility and the mobile device 2 carried by the user. This message function requires that a function addition process has been performed between the mobile device 2 carried by the user and the reception device 1, and that the medical facility's patient card has been registered on the mobile device 2.

As explained in Figure 12 (F), a patient registration card is registered on a mobile terminal 2 that has completed the function addition process using a reception device 1 installed in a medical facility. The patient registration card display area 255a has a button 255c labeled "Message Settings," and operating this button 255c sets a message for the patient registration card.

Figure 14 (G) shows the screen that appears when button 255c displayed in the patient card display area 255a in Figure 12 (F) is operated, displaying a message setting field 256c. This message setting field 256c displays the name of the medical facility (hospital name), patient name, and patient ID for the selected patient card. The user checks this message setting field 256c, and if they wish to use the message function, they operate button 256e labeled "Receive." If they do not wish to use the message function, they can return to the previous screen by operating button 256d.

When button 256e is operated, the relationship setting field 257a in Figure 14 (H) is displayed. Here, it is conceivable that the user of the mobile terminal 2 is not the patient himself/herself. For example, the user of the mobile terminal 2 may be the patient's relative, guardian, caregiver, etc. In this embodiment, as mentioned above, even a user other than the patient corresponding to the patient's medical card can register the medical card in place of the patient, or in addition to the patient.

For this reason, when setting up the message function, it is possible to register the relationship of the person to the patient. The registered relationship can be referenced by the management computers 3a and 3b within the medical facility that send and receive messages, making it possible to confirm who the message is about. Also, since a patient may have multiple guardians and caregivers, it is possible to set up the message function on multiple mobile devices 2 for a given patient.

In this embodiment, the relationship setting field 257a allows the user to set the patient, spouse, parent, child, relative, friend, or provider (such as a care provider), and a corresponding relationship selection button 257b is provided. Operating button 257c returns the user to the previous screen. When a relationship is selected with the relationship selection button 257b, a confirmation field 258a shown in FIG. 14(I) is displayed. This confirmation field 258a displays the medical facility name (hospital name), patient name, patient ID, and the relationship selected with the relationship selection button 257b ("Person" in the case of FIG. 14(I)).

After confirming the settings for the message function in the confirmation field 258a, the user operates the button 258c labeled "OK" to complete the settings for the message function. Note that if button 258b is operated, the user will return to the previous screen.

In this way, in this embodiment, it is possible to set messages for each patient card registered on the mobile device 2 during the function addition process. When the message function is set on the mobile device 2, various processes for setting the message function are executed between the mobile device 2, message server 62, and management computer 3. Figures 15 and 16 are flow diagrams showing the processes for setting these message functions (corresponding to the "setting process" according to the present invention), and Figure 17 is a diagram showing the various data structures used in the message system according to this embodiment. Here, we will explain the processes between the mobile device 2a and the management computer 3a installed in medical facility A.

Figure 15 is a flow diagram showing the initial registration process for a mobile device according to this embodiment. Here, we will explain the process using a mobile device 2a that uses a first OS as an example. For a mobile device 2a, the corresponding first notification server 61a is used. For a mobile device 2b that uses a second OS, the corresponding second notification server 61b is used.

When a portable program (app) is installed on the mobile device 2a and launched for the first time (S301), the mobile device 2a notifies the first notification server 61a that the app is being launched for the first time. The first notification server 61a assigns an app ID to the mobile device 2a, stores it, and notifies the mobile device 2a (S302). The mobile device 2a stores the received app ID in its mobile-side setting information.

Next, the mobile device 2a sends an initial registration request to the message server 62. At that time, the application ID assigned by the first notification server 61a is sent to the message server 62. The message server 62 generates information necessary for setting up the mobile device 2a (S303). The information necessary for setting up includes the M_JID, M password, M public key, and M private key. Of these, the M_JID, M password, M public key, and the received application ID are registered as server-side mobile information (S303). The M_JID is identification information for the mobile device 2a and is also used as the destination. The M password is a password required when logging in to the message server 62. The M public key is key information used when encrypting on the mobile device 2a.

The message server 62 sends the M_JID, M password, and M public key, which are part of the information required for the generated settings, to the mobile device 2a that made the initial registration request. The mobile device 2a registers the received information in the mobile device setting information (S305). The mobile device setting information includes the M_JID, M password, M private key, and app ID.

Next, mobile device 2a logs in to message server 62 using M_JID and M password. After confirming the login, message server 62 officially registers the server-side mobile device information of mobile device 2a (S306). It then notifies mobile device 2a that the login was successful. Upon receiving the notification of successful login, mobile device 2a officially registers the mobile device-side setting information (S307).

By completing the initial registration process described above, the mobile device 2a will be able to use the messaging function using the message server 62. Next, we will explain the handshake process used to set up the messaging function with individual medical facilities.

Figure 16 is a flow diagram showing the handshake process performed between the mobile device 2a and the management computer 3a installed at the medical facility selected when the message function was added. By performing this handshake process, information about the mobile device 2a is registered in the management computer 3a, public keys are exchanged between the two, and message transmission and reception becomes possible. Here, the management computer 3a performs a setting process with the message server 62 and stores facility-side setting information. The facility-side setting information includes the medical facility ID, H_JID, H password, and H private key. The H_JID is identification information for the management computer 3a installed at the medical facility and is also used as the destination. The H private key is the private key of the management computer 3a and is used to decrypt information encrypted with the H public key.

The handshake process is executed when button 258c is operated in the confirmation field 258a described in Figure 14 (I). In the handshake process, mobile terminal 2a logs in to message server 62 (S351), and based on the selected patient card, mobile terminal 2a sends a patient card setting request to message server 62 (S352). The setting request includes the medical facility ID indicating the medical facility for the selected patient card. The message server 62 pre-stores server-side setting information for the medical facility.

The server-side setting information includes a medical facility ID, H_JID, and H public key. The medical facility ID is identification information that can identify the medical facility. The H_JID is identification information for the management computer 3a installed in the medical facility, and is also used as the destination. The H public key is the public key of the management computer 3a.

Upon receiving a setting request from the mobile terminal 2a, the message server 62 sends the H_JID and H public key (S353) to the mobile terminal 2a. The mobile terminal 2a registers the H_JID and H public key as patient card-related information. The patient card-related information includes the medical facility ID, H_JID, H public key, and subscriber information. The subscriber information is information related to the patient card, and includes the patient ID, patient name, and relationship selected in Figure 14 (H).

The mobile device 2a sends a setting request to the management computer 3a. The setting request is sent via the message server 62. The message server 62 connects the M_JID of the mobile device 2a, which is the sender, with the H_JID of the management computer 3a, which is the destination, enabling direct communication between the two. The setting request includes the M_JID of the mobile device 2a, and upon receiving the setting request, the management computer 3a requests the M public key from the message server 62 (S355). The message server 62 references the server-side mobile device information and sends the M public key corresponding to the M_JID to the management computer 3a (S356).

The management computer 3a registers the received M_JID in the facility's mobile information (S357). The facility's mobile information includes the M_JID and M public key. The management computer 3a sends a subscription notification to the mobile terminal 2a. Upon receiving the subscription notification, the mobile terminal 2a sends subscriber information to the management computer 3a. By registering the received subscriber information in the facility's mobile information (S358), the management computer 3a becomes able to create and send messages by referencing the recipient's patient ID, patient name, and relationship, or to reference the patient ID, patient name, and relationship in received messages.

Once the handshake process between the mobile terminal 2a and the management computer 3a is completed, messages can be sent between them. The handshake process is carried out without specifying the destination M_JID and H_JID, which prevents messages from being interrupted or sent incorrectly due to incorrect email addresses, as is the case with conventional email. Furthermore, there is no need to exchange email addresses by hand, making setup easy.

The message server 62 also manages the public keys of the mobile terminal 2 and the management computer 3. The mobile terminal 2a and the management computer 3a also receive each other's public keys (H public key, M public key) from the message server 62. In other words, the message server 62 functions as a key bank. The mobile terminal 2 and the management computer 3 communicate directly, but this direct communication is all encrypted, ensuring sufficient security.

Figures 18 and 19 are flow diagrams showing the transmission process according to this embodiment. In this embodiment, messages can be sent between the mobile terminal 2a and the management computer 3a, just like conventional email. In this case, the message server 62 simply functions as a tunnel connecting the sender and destination, essentially providing direct communication between the mobile terminal 2a and the management computer 3a, thereby improving security. Note that the mobile terminal 2a and the management computer 3a are both logged in to the message server 62.

Here, the transmission process for sending a message from the management computer 3a to the mobile device 2a checks the running status of the mobile program (app) on the mobile device 2a before sending the message. Figure 18 is a flow diagram showing the transmission process (when the mobile device program is running) according to this embodiment, and Figure 19 is a flow diagram showing the transmission process (when the mobile device program is not running) according to this embodiment.

First, the management computer 3a creates a message (S401). Figure 20 shows a message client screen according to this embodiment. The message client (corresponding to the "message program" according to the present invention) is a program executed by the management computer 3a for sending and receiving messages.

The message client screen has a search field 421a, a search result display button 421b, a new message creation button 421c, a send message selection button 421d, a recipient list 421e, a text view field 421f, and a data view field 421g.

The search field 421a allows the user to enter the patient ID and patient name to which a message will be sent. Search results are displayed using the search result display button 421b. The operator of the management computer 3 selects the patient to whom the message will be sent from the search results. In the example of Figure 20, the selected patient ID and patient name fields are shaded ("Patent Taro" is selected). A message for the selected patient can be created by operating the new message creation button 421c.

When the new message creation button 421c is operated, a new message creation field 421h is displayed, as shown in FIG. 21. The new message creation field 421h includes a title input field 421i, patient ID, patient name, recipient relationship selection button 421j, text input field 421k, attachment data input field 421m, and send button 421n.

The recipient relationship selection button 421j displays the relationship of the mobile device 2 registered in the handshake process to the selected patient. In the example of Figure 21, three mobile devices 2 are registered for the patient "Patent Taro": "Patent Taro," "Spouse," and "Child." The user uses this recipient relationship selection button 421j to set one or more relationships. Then, the user enters the desired message in the title input field 421i and text input field 421k, and, if necessary, registers a file as attached data. Sending begins by operating the send button 421n.

In this way, in this embodiment, three mobile devices 2 are registered for each patient: the patient's "self," "spouse," and "child." Messages about the same patient can be sent by selecting the relationship to the patient, such as addressing all of the patient, "spouse," and "child," or by addressing only the patient, "spouse," or only the "spouse" and "child," making it easier to manage message sending at medical facilities.

As shown in FIG. 20, on the message client screen, messages that have already been sent are displayed as a sent message selection button 421d. This sent message selection button 421d displays the creation date and time of the message and its title. Furthermore, selecting the sent message selection button 421d displays a list of recipients 421e for that message and a text view field 421f showing the content of that message. The example in FIG. 20 shows that a message with the title "Next medical examination notice" has been sent to the relationships "Self" and "Spouse." Of these, the status for "Self" is "Delivered," indicating that delivery has been made to the active mobile device 2. Furthermore, the status for "Spouse" is "Not delivered (5 attempts)," indicating that the mobile device 2 is not active and that the notification described in FIG. 19 has been made five times.

If a message has been sent with attached data, the file name, data content, etc. are displayed in the data view field 421g. Attached data sent from a medical facility may include a referral letter, medical certificate, medical examination results, health check results, etc., but the message function of this embodiment has improved security, so it is also possible to send such confidential documents.

When message creation is complete (S401) and the send button is pressed, the management computer 3a does not immediately send the message, but first sends a confirmation request to the message server 62 (S402). The confirmation request is a request to confirm whether a portable program (app) is running on the destination portable terminal 2a. Note that the launch of a portable program (app) on portable terminal 2a (and similarly for 2b) can take the following two forms. The form differs depending on the OS used. In the first form, the portable program (app) is considered to be running not only when its screen is displayed on portable terminal 2a, but also when it is running in the background. In the second form, the portable program (app) is considered to be running only when its screen is displayed on portable terminal 2a. These launch states can be confirmed by the first notification server 61a and second notification server 61b of the corresponding OS.

In this embodiment, it is assumed that two types of OS are used on the mobile device 2. Therefore, the message server 62 determines the OS of the mobile devices 2a and 2b to be the transmission target based on a confirmation request from the management computer 3a (S404). This determination can be made based on the app ID in the mobile device setting information of the management computer 3a. In the example of Figures 18 and 19, the message server 62 determines that the mobile device 2a to be the transmission target is running the first OS, and therefore sends a confirmation request to the first notification server 61a for the first OS (S404).

The first notification server 61a, which has received the confirmation request, checks whether the portable program (app) on the portable device 2a is running (S405). In the example of Figure 18, the portable program (app) is running (S406), so the first notification server 61a confirms that the portable program (app) is running (S407) and notifies the message server 62 of the running status (S408). The message server 62, which has received the running status, sends the running status to the management computer 3a that made the confirmation request (S409).

After confirming the startup status of the destination mobile terminal 2a (S410), the management computer 3a sends a message to the mobile terminal 2a (S411). By encrypting the message using the M public key of the mobile terminal 2a, it is possible to send the message securely. The message is sent via the message server 62, but the message server 62 simply connects the H_JID of the management computer 3a as the sender and the M_JID of the mobile terminal 2a as the destination; it does not store or preserve the message; it functions as a tunnel, so to speak. This essentially enables direct communication between the management computer 3a and the mobile terminal 2a.

The mobile device 2a that receives the message decrypts the message using the M private key and displays it (S413). Figure 22 (J) shows the message display screen on which the message received by the mobile device 2a is displayed. The message display screen displays a message display field 259b. The message display field 259b displays the name of the medical facility (hospital name) to which the message was sent, the patient's name, the patient ID, the relationship to the patient, the message body, a reply button 259c, and a close button 259d.

The user can check messages from the medical facility based on the message display field 259b. Additionally, by operating the reply button 259c, the user can reply to the management computer 3a installed at the sending medical facility. In this embodiment, when sending a message from the management computer 3a to the mobile device 2a, it was necessary to check the application startup status on the mobile device 2a. However, since the message client on the management computer 3a is basically always running, the startup status is not checked.

The above is the transmission process when the portable program (app) is active on the portable device 2a. Next, we will explain the case when the portable program (app) is not active on the portable device 2a. Figure 19 shows the case when the portable program (app) is not active on the portable device 2a (S451). The process is the same as Figure 18 up to the app activation check (S405) on the first notification server 61a.

In the case of Figure 19, the portable program (app) is in a non-active state (S451), so the first notification server 61a confirms that the portable program (app) is in a non-active state (S452) and notifies the message server 62 of the non-active state (S453). The message server 62, which receives the non-active state, transmits the non-active state to the management computer 3a (S454). When the management computer 3a confirms that the portable program (app) is in a non-active state on the destination mobile device 2a (S455), it does not send the message, but waits for a predetermined time to elapse (S456: Yes), and then executes the confirmation request again (S403).

Meanwhile, the message server 62 sends a notification (S457) to the mobile device 2a. This notification (S457) is a process performed at the OS level of the mobile device 2a, and is executed via the first notification server 61a. In this embodiment, based on the reception of the message, a notification is sent prompting the user to launch a mobile program (app). The mobile device 2a displays the received message (S457). In this embodiment, the message server 62 can determine the management computer 3a (facility) by referencing the logged-in H_JID, and can therefore notify the user which facility the message is from.

Figure 22 (K) is a diagram showing the home screen of the mobile device 2a, showing a situation in which a notification is being made. The home screen displays icons for various apps. The mobile program (app) used in this embodiment is also displayed as the patient card app 259a. A notification display field 259e is displayed above this home screen (or another app screen). The notification display field 259e displays a notification message stating, "A new message has been received from Almex Hospital. Please launch the 'patient card app'." The user refers to this notification message and launches the patient card app 259a.

When the patient registration card app 259a is launched on the mobile device 2a, it becomes possible to receive and display messages from medical facilities, as shown in Figure 22 (J), in accordance with the transmission process described in Figure 18.

The above describes various embodiments of the invention pertaining to the present invention, but the present invention is not limited to these embodiments, and forms formed by appropriately combining the configurations of each of the various embodiments also fall within the scope of the present invention.

The present invention can be used not only in medical facilities, but also in financial institutions such as banks, golf courses, and other facilities where confidentiality of customer information is required. At financial institutions such as banks, cash cards are used as facility tickets, and ATMs are used as reception devices. At golf courses, membership cards are used as facility tickets, and function addition processing is performed using reception devices installed on the golf course.

1 (1a, 1b): Reception device 61a: First notification server 2 (2a, 2b): Mobile terminal 61b: Second notification server 3 (3a, 3b): Management computer 62: Message server 11a: CPU 71: Hospital reception 11b: ROM 72: Entrance/exit 11c: RAM 121: Touch panel 11d: Image processing unit 122: Display unit 11e: Voice processing unit 123a: Consultation details display field 12: Touch panel monitor 123b: Cancel button 13a: Camera 123c: Confirm button 13b: Infrared camera 251: Touch panel 14: Card reader 251a: Medical facility name 15: Receipt printer 252: Display unit 15a: Scanner 255a, 255b: Patient card display area 15b: Two-dimensional barcode reader 255e: Two-dimensional barcode 16a: Receipt printer 256: Cancel button 16b: Printer 256a: Monitor field 17: LAN communication unit 256c: Message setting field 18: Hard disk 257a: Relationship setting field 19: Interface 257b: Relationship selection button 21a: CPU 258a: Confirmation field 21b: ROM 259a: Patient registration card application 21c: RAM 259b: Message display field 21d: Image processing unit 259c: Reply button 21e: Audio processing unit 259d: Button 22: Storage unit 259e: Notification display field 23: Interface 352: Message server 24: Camera 421a: Search field 25: Touch panel monitor 421b: Search result display button 26a: Mobile line communication unit 421c: New message creation button 26b: Wireless LAN communication unit 421d: Send message selection button 26c: Communication unit 421e: Destination list 27: Input switch 421f: Text view field 28a: Speaker 421g: Data view field 28b: Microphone 421h: New message creation field 41: Input device 421i: Title input field 42: Monitor 421j: Recipient relationship selection button 43: Card reader 421k: Text input field 44: Receipt printer 421m: Attachment data input field 52 (52a, 52b): Router 421n: Send button

Claims (4)

A message system including a mobile terminal, a message management device installed in a facility, and a reception device installed in the facility,
The mobile terminal executes a function addition process, a setting process, and a message process,
The function addition process involves a user using the reception device to register facility user-related information, including identification information of the mobile terminal, in the mobile terminal;
The setting process executes settings necessary for message processing between the facility user and the message management device corresponding to the registered facility user related information, based on the registered facility user related information;
The message processing allows the device to receive messages sent from the message manager or to send messages to the message manager after the setting process is completed.
The setting process sets, in the message management device , identification information of the mobile terminal, identification information of the facility user, and the relationship of the facility user as information regarding the destination of a message to be sent by a message program executed in the message management device ;
In the message processing, when a facility user is selected, the relationship to the facility user set in the setting processing is selected, and the mobile device of the relationship to the facility user is set as the message destination.
Message system. A portable program executable on a portable terminal,
The mobile program causes the mobile terminal to execute a function addition process, a setting process, and a message process,
The function addition process uses a reception device installed in the facility to register facility user related information, including identification information of the mobile terminal, in the mobile terminal;
The setting process executes settings necessary for message processing between the facility user and the message management device corresponding to the registered facility user related information, based on the registered facility user related information;
The message processing allows the device to receive messages sent from the message manager or to send messages to the message manager after the setting process is completed.
The setting process is a portable program that sets the identification information of the mobile terminal, the identification information of the facility user, and the relationship to the facility user in the message management device as information regarding the destination of the message to be sent by the message program executed in the message management device . A message management device used in a message system including a mobile terminal and a message management device installed in a facility,
The mobile device is
executes a setting process for setting, in the message management device , identification information of the mobile terminal, identification information of the facility user, and the relationship of the facility user as information regarding the destination of a message sent by a message program executed in the message management device;
The message management device
After the setting process is completed, the message manager is enabled to send messages.
When a facility user is selected, the message management device executes message processing to set a mobile device related to the facility user as the destination of a message to be sent by selecting the relationship to the facility user set in the setting processing. A message program executed on a message management device used in a message system including a mobile terminal and a message management device installed in a facility,
The mobile device is
executes a setting process for setting, in the message management device , identification information of the mobile terminal, identification information of the facility user, and the relationship of the facility user as information regarding the destination of a message sent by a message program executed in the message management device;
The message program is
After the setting process is completed, the message manager is enabled to send messages.
A message program that, when a facility user is selected, executes message processing to set a mobile device of the facility user's relationship as the destination of a message to be sent by selecting the relationship of the facility user that was set in the setting processing.