WO2004077324A1 - Reservation reception method, method for calling in advance, and program thereof - Google Patents

Reservation reception method, method for calling in advance, and program thereof Download PDF

Info

Publication number
WO2004077324A1
WO2004077324A1 PCT/JP2004/001676 JP2004001676W WO2004077324A1 WO 2004077324 A1 WO2004077324 A1 WO 2004077324A1 JP 2004001676 W JP2004001676 W JP 2004001676W WO 2004077324 A1 WO2004077324 A1 WO 2004077324A1
Authority
WO
WIPO (PCT)
Prior art keywords
reservation
remote server
processing device
reception processing
reception
Prior art date
Application number
PCT/JP2004/001676
Other languages
French (fr)
Japanese (ja)
Inventor
Koichi Yoshii
Kinji Asada
Masahiro Satonishi
Junji Minotani
Original Assignee
Koichi Yoshii
Kinji Asada
Masahiro Satonishi
Junji Minotani
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Koichi Yoshii, Kinji Asada, Masahiro Satonishi, Junji Minotani filed Critical Koichi Yoshii
Publication of WO2004077324A1 publication Critical patent/WO2004077324A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02Banking, e.g. interest calculation or account maintenance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/02Reservations, e.g. for tickets, services or events

Definitions

  • the present invention relates to a reservation receiving method and a program therefor, and more specifically, a user terminal, a remote server connectable to the user terminal via a telecommunication line, and a remote server connectable to the remote server via the telecommunication line.
  • the present invention relates to a reservation reception method for receiving service provision using a simple reception processing device and a program therefor. Background art
  • An object of the present invention is to provide a reservation receiving system that can effectively utilize the time from receiving a reservation until receiving service.
  • Another object of the present invention is to provide a reservation receiving system that can ensure high security and can continue business even if an abnormality occurs in a telecommunication line.
  • the reservation receiving method is a reservation receiving method using a user terminal, a remote server connectable to the user terminal, and a reception processing device connectable to the remote server, wherein the user terminal transmits a reservation request to the remote server. And transmitting the reservation request transmitted to the remote server to the reception processing device, and receiving the reservation based on the reservation request transmitted to the reception processing device.
  • the user terminal When a user makes a reservation, the user inputs a reservation request to the user terminal.
  • the user terminal sends the input reservation request to the remote server.
  • the remote server Upon receiving the reservation request, the remote server transmits the reservation request to the reception processing device.
  • the reservation request is always transmitted from the user terminal to the reception processing device via the remote server.
  • the reception processing device does not directly receive information such as a reservation request from the user terminal. Therefore, the reception processing device can prevent unauthorized access from the user terminal, and the security of the reception processing device is improved. As a result, it is possible to prevent the operation of the reception processing device from being stopped due to unauthorized access or the like, and the reception processing device can continue to operate.
  • the reservation receiving method further includes an inquiry step from the reception processing device to the remote server, and the step of transmitting the reservation request to the reception processing device transmits the reservation request in response to the inquiry.
  • the remote server does not transmit the reservation request to the reception processing device unless there is an inquiry from the reception processing device. That is, the reception processing device receives only the reservation request transmitted from the remote server in response to the inquiry transmitted by itself. Thus, the security of the reception processing device is further improved.
  • the reservation receiving method further includes a step of determining whether or not the reception processing device has received a response from the remote server to the inquiry within a predetermined period, and a step of determining that the response has not been received within the predetermined period. Notifying an operator of the reception processing device of a warning.
  • the reception processing device determines whether a response from the remote server has been received within a predetermined period. If there is no response from the remote server, it is likely that some trouble has occurred in the telecommunications line ⁇ remote server. Therefore, if there is no response, the reception processing device notifies the operator of a warning by voice or screen display. As a result, the operator can easily recognize that a failure has occurred in the telecommunication line or the remote server, and can take prompt action.
  • the reservation receiving method further comprises: transmitting reservation status data indicating the reservation status from the reception processing device to the remote server at predetermined intervals; and transmitting the reservation status from the remote server to the user terminal in response to a request from the user terminal. And a step for transmitting data.
  • the reception processing device transmits the reservation status data to the remote server every predetermined period. Therefore, the reservation status data in the remote server can be synchronized with the reservation status data in the reception processing device. In addition, the remote server returns reservation status data in response to a request from the user terminal. This allows the user to refer to the most recent reservation status before making a reservation request.
  • the reservation receiving method further includes: transmitting a reservation receiving number from the user terminal to the remote server; and receiving service provision based on the reservation receiving number and the reservation status data transmitted to the remote server. Calculating the number of people waiting and / or the waiting time as call status data; and transmitting the call status data from the remote server to the user terminal.
  • the user of the user terminal transmits the reservation reception number from the user terminal to the remote server after the reservation is completed. Based on the reservation reception number and reservation status data, the remote server waits for the user to receive the service and / or The time is calculated as call status data. The calculated call status data is transmitted to the user terminal. Therefore, the user can grasp how many people are waiting or how long the waiting time is before receiving the service. As a result, the time until the user receives the service can be effectively used.
  • a pre-call method is a pre-call method by a user terminal connectable to a remote server having call status data until a service is provided, comprising: a step of storing a call condition input from outside; Transmitting the reservation receipt number input from the remote server to the remote server based on the reservation receipt number, and determining whether the call status data satisfies the calling condition based on the reservation receipt number.
  • the method includes a judging step and a step of notifying the user of the user terminal that the calling condition is satisfied when the calling condition is satisfied.
  • the user inputs calling conditions to the user terminal, for example, to notify when the number of people waiting for receiving the service becomes less than 10 people. Thereafter, the user inputs the reservation reception number to the user terminal, and the user terminal transmits the input reservation reception number to the remote server.
  • the remote server transmits the call status data until the user of the reservation reception number receives service provision to the user terminal based on the reservation reception number.
  • the user terminal determines whether the received call status data satisfies the call conditions, and if so, notifies the user by voice, vibration, screen display, or the like. As a result, the user can be informed to the user terminal that the turn to receive the service is approaching. As a result, the user can effectively utilize the time until the service is provided.
  • the advance calling method includes: a step of transmitting a reservation reception number to a remote server when it is determined in the determining step that the calling condition is not satisfied; a step of receiving the calling status data; And the step of determining whether or not the condition is satisfied is repeated.
  • the user terminal transmits the reservation reception number to the remote server until the call status data satisfies the call condition, receives the call status data, and determines whether the received call status satisfies the call condition. Is repeated.
  • the user can enter the calling condition and the reservation reception number once and enter the reservation reception number repeatedly. The user can be notified of the fact that the turn to receive the service is approaching without repetition.
  • FIG. 1 is a functional block diagram showing an overall configuration of a reservation receiving system according to an embodiment of the present invention.
  • FIG. 2 is a flowchart showing an operation of a reservation request process of the reservation reception system shown in FIG.
  • FIG. 3 is a diagram of a reservation request information input screen in step S101 in FIG.
  • FIG. 4 is a flowchart showing the operation of the reservation receiving process of the reservation receiving system shown in FIG.
  • FIG. 5 is a display screen view of the bulletin board at step S215 in FIG.
  • FIG. 6 is a flowchart showing the operation of the completion notification process of the reservation receiving system shown in FIG.
  • FIG. 7 is an input screen diagram in step S301 in FIG.
  • FIG. 8 is a diagram of a completion notification screen in step S305 in FIG.
  • FIG. 9 is a flowchart showing the operation of the regular communication process of the reservation receiving system shown in FIG.
  • FIG. 10 is a flowchart showing an operation of a call status notification process of the reservation receiving system shown in FIG.
  • FIG. 11 is an input screen diagram in step S501 in FIG.
  • FIG. 12 is a diagram of a call status notification screen in step S506 in FIG.
  • FIG. 13 is a flowchart showing the operation of another example of the call status notification process of the reservation receiving system shown in FIG.
  • FIG. 14 is a flowchart showing the operation of the congestion status notification process of the reservation receiving system shown in FIG. .
  • FIG. 15 is a congestion status notification screen view in step S706 in FIG.
  • FIG. 16 is a flowchart showing the operation of the gun gauge information notification process of the reservation receiving system shown in FIG.
  • FIG. 17 is a flowchart showing the operation of the ticket issuing process of the reservation receiving system shown in FIG.
  • FIG. 18 is a flowchart showing an operation of a call process of the reservation receiving system shown in FIG.
  • FIG. 19 is a flowchart showing the operation of the skip processing of the reservation receiving system shown in FIG.
  • FIG. 20 is a notice display screen view in step S103 in FIG.
  • FIG. 21 is a flowchart showing the operation of another example of the call skipping process of the reservation receiving system shown in FIG. BEST MODE FOR CARRYING OUT THE INVENTION
  • a reservation reception system 10 includes a reception processing device 1 and a remote server 2.
  • the reception processing device 1 and the remote server 2 are connected via an electric communication line 3 such as the Internet.
  • the reception processing device 1 includes a CPU (Central Processing Unit.) 11, a memory 12, a hard disk 13, a signboard display 15, an input unit 16 such as a mouse and a keyboard, and a ticketing unit 17.
  • the hard disk 13 includes a main-side status data file 13 1 and a main-side reception data file 13 2.
  • the main status data file 1 3 1 contains the latest reservation reception number among the issued reservation reception numbers, the number of people waiting, the waiting time, the reservation reception number currently being called, and the reservation reception number of the person who was absent at the time of the call (Hereinafter referred to as status data).
  • the main reception data file 1 32 stores the reservation request.
  • the signage display 15 is preferably installed at a place in the hospital where visitors can view.
  • the input unit 16 may be provided for each reception place and each examination room.
  • the ticketing section 17 issues a reservation receipt number ticket to visitors.
  • Reception processing device 1 is remote Based on the reservation request sent from the central server 2, it performs the consultation reservation service. Further, the reception processing device 1 can also accept a reservation independently of the remote server 2.
  • the remote server 2 includes a CPU 21, a memory 22, and a hard disk 23.
  • the hard disk 23 includes a remote-side status data file 2 31, a remote-side reception data file 2 32, and a statistical data file 2 33.
  • the remote-side status data file 2 31 stores the status data transmitted from the reception processing device 1.
  • the remote reception data file 2 3 2 is transmitted from a portable terminal 4 or a fixed terminal 5 such as a PDA (Personal Digital Assistant) or a mobile phone used by the user (hereinafter, the portable terminal 4 and the fixed terminal 5 are also referred to as a user terminal 6). Save the requested reservation.
  • the statistical data file 233 stores the statistical results of the status data every predetermined period (for example, every hour).
  • the remote server 2 receives a reservation request from the user terminal 6 via the telecommunication line 3.
  • the remote server 2 receives the reservation request, the user can reserve an examination from home or outside before going to the hospital.
  • the reservation accepting program may be stored in advance in the memories 12 and 22 as a microprogram.
  • the mobile terminal 4 includes a CPU 41 and a memory 42, and can perform a pre-call process by installing a pre-call program.
  • the mobile terminal 4 may be sold after a prior call program is installed in advance.
  • the pre-call program may be stored in the hard disk 23 of the remote server 2 in advance, and the user may purchase the mobile terminal 4 and then download the pre-call program from the remote server 2 to the mobile terminal 4.
  • the remote reservation receiving process is a process in which the remote server 2 receives a reservation request from the user terminal 6 (temporary reservation receiving process), and the remote server 2 transmits a reservation request to the reception processing device 1 at predetermined intervals, and the reception processing device 1 is divided into a process for accepting the user's reservation (final reservation acceptance process) and a process for the user to inquire whether the reservation acceptance has been completed (reservation completion inquiry process).
  • each process will be described.
  • FIG. 3 shows a reservation request information input screen when the user uses the mobile terminal 4.
  • the reservation request information enter the user's name, date of birth, mobile phone number, and if not the first consultation, the consultation ticket number. If the user's name, consultation ticket number, and date of birth are linked to the user ID and stored in the hard disk 23 of the remote server 2 in advance, the user uses the user ID as the reservation request information. It may be input to terminal 6.
  • the user terminal 6 transmits the inputted reservation request information to the remote server 2 (S102).
  • the remote server 2 After receiving the reservation request information (S103), the remote server 2 determines whether or not the periodic communication processing has been performed within a predetermined period before the reception (S104).
  • the periodic communication process refers to a process of periodically transmitting and receiving information between the reception processing device 1 and the remote server 2. The regular communication processing will be described later. Whether or not the periodic communication processing has been performed is determined based on whether or not the status data in the remote-side status data file 231 has been updated within a predetermined period before the reception of step S103.
  • step S104 determines that an abnormality has occurred in the reservation receiving system 10. This is because the fact that the periodic communication processing is not performed is because it is considered that an abnormality has occurred in the reception processing device 1 or an abnormality has occurred in the telecommunication line 3. Therefore, in this case, the remote server 2 transmits to the user terminal 6 a notification that the reservation reception system is currently stopped (hereinafter, referred to as an error notification) (S105). The user terminal 6 receives the information indicating that it is stopped, and displays it on a display (not shown) (S108).
  • the periodic communication process is performed within a predetermined period. If it is determined that the reservation has been made, the remote server 2 performs a tentative reservation acceptance process (S106). Specifically, the remote server 2 stores the reservation request information transmitted from the user terminal 6 in the remote-side reception data file 232.
  • the remote server 2 transmits a provisional reservation reception completion notification to the user terminal 6 (S107).
  • the user terminal 6 receives the tentative reservation acceptance completion notice and displays it on the display (S108).
  • the user's reservation is not completed just by completing the provisional reservation reception process.
  • the user reservation is completed only after the reception processing device 1 receives the user reservation. Therefore, the reception processing device 1 performs the main reservation reception process of acquiring the reservation request information from the remote server 2.
  • Fig. 4 shows the operation of this reservation acceptance process. As shown in FIG. 4, the entire operation of the reservation accepting process is defined as step S20.
  • this reservation reception processing is performed after a periodic communication processing in which the reception processing device 1 and the remote server 2 periodically transmit and receive information.
  • the periodical communication processing will be described later.
  • the reception processing device 1 determines whether or not new reservation request information is recorded in the remote-side reception data file 2 32. (S202 to S206).
  • the new reservation request information refers to the reservation request information stored in the remote-side reception data file 232 since the previous main reservation reception processing.
  • the reception processing device 1 transmits an inquiry message as to whether or not there is new reservation request information to the remote server 2 (S202). After receiving the inquiry message (S203), the remote server 2 determines whether or not new reservation request information is stored in the remote-side reception data file 232, and transmits the determination result.
  • the reception processing device 1 After receiving the determination result from the remote server 2 (S205), the reception processing device 1 determines whether there is new reservation request information based on the determination result (S206). As a result of the determination, when there is no new reservation request information, the reception processing device 1 ends the reservation reception processing. On the other hand, if there is new reservation request information, the reception processing device 1 performs a process of acquiring the reservation request information stored in the remote-side reception data file 23 (S207 to S215). Specifically, the reception processing device 1 transmits a request message for reservation request information to the remote server 2 (S207). Remote server 2 sends request message After receiving the message (S208), the reservation request information stored in the remote-side reception data file 232 is transmitted to the reception processing device 1 (S209). After receiving the reservation request information, the reception processing device 1 stores it in the main-side reception data file 132 in the hard disk 13 (S210).
  • the reception processing device 1 calculates a reservation reception number based on the latest status data stored in the main-side status data file 131 and the stored reservation request information (S21 1), The calculation processing (S212) and the waiting time calculation processing (S213) are performed.
  • the reservation reception numbers are assigned in the order of the reservation request information for which the reservation request was earlier (S211). Specifically, by referring to the latest issued reservation reception number in the situation data, the reservation reception number is sequentially assigned and assigned to each reservation request information for which the reservation request has been made earlier.
  • the reception processing device 1 sends the reservation request information , A reservation reception number of “30051”, “30052”, or “30053” is given to the user.
  • the reservation reception number may be incremented by 10 and may be "30060", "30070", or "30080".
  • the waiting person is calculated by the following equation (1) (S212).
  • the calling number is the number that has been called from the consultation room (that is, the number for which the waiting for consultation has been completed).
  • the waiting time is calculated by the following equation (2) (S213).
  • the expected time can be determined for each time slot or field.
  • the reception processing device 1 issues a reservation reception number ticket from the ticket issuing unit 17 based on the reservation reception number calculated in step S212 (S214). Further, information on the number of waiting persons calculated in step S 211 and the waiting time calculated in step S 213 is displayed on the bulletin board display 15 in the hospital (S 215).
  • FIG. 5 shows the screen of the bulletin display in step S215. The call number is displayed on the call number display section 201, the number of persons waiting on the waiting number display section 202, and the waiting time on the waiting time display section 203.
  • the reception processing device 1 repeats the operations of S211-S215 for the number of reservation information received in S210.
  • the reception processing device 1 transmits the reservation reception number for each reservation information calculated in S211 to the remote server 2 (S216). It should be noted that the status data stored in the main-side status data file 131 is also transmitted when the reservation reception number is transmitted.
  • the remote server 2 After receiving the reservation reception number for each reservation request information (S217), the remote server 2 links the reservation reception number with the corresponding reservation request information and stores it in the remote-side reception data file 232 (S218). The number of people waiting, the waiting time, and the call number are stored in the remote H-law situation data file 231.
  • the user can use the user terminal 6 to inquire whether or not the reservation reception by the reception processing device 1 has been completed.
  • the user sends an inquiry message to remote server 2 using user terminal 6 (S301).
  • FIG. 7 shows the mobile terminal screen in step S301 when the user uses the mobile terminal 4.
  • the remote server 2 determines whether or not the reservation reception has been completed by the reception processing device 1 (S303).
  • the remote server 2 refers to the user's reservation request information in the remote-side reception data file 232 from information (for example, a telephone number or an identification number previously assigned from the remote server 2) that specifies the user terminal 6. Then, it is determined whether or not the reservation request information has the reservation reception number assigned from the reception processing device 1. If it is determined that the reservation server does not have a reservation reception number, the remote server 2 reserves A notification that the reception has not been completed (incomplete notification) is transmitted to the user terminal 6 (S30)
  • the user terminal 6 After receiving the incomplete notification, the user terminal 6 displays it on the display (S30)
  • step S303 if the remote server 2 has the reservation reception number, the remote server 2 sends the reservation reception number and the remote-side status data file 2 3 1 to the user terminal 6.
  • the status data and the status data are transmitted (S304).
  • the user terminal 6 After receiving the reservation reception number and the status data, the user terminal 6 displays the reservation reception number and the status data on the display (S305).
  • FIG. 8 shows the screen of the portable terminal 4 at this time.
  • the reception processing device 1 and the remote server 2 perform a periodic communication process for exchanging information at predetermined intervals.
  • the information in the main-side status data file 13 1 ⁇ is synchronized with the status data in the remote-side status data file 2 3 1.
  • Figure 9 shows the operation of the periodic communication process.
  • the periodical communication processing operation on the reception processing device 1 side is periodical communication processing S41
  • the periodical communication processing operation on the remote server 2 side is periodic communication processing S42.
  • the reception processing device 1 first determines whether or not the online flag is ON as a periodic communication process (S4.01).
  • the online flag is “ON” when the reservation reception system 10 is operating normally, and is “OFF” when the reservation reception system 10 is not operating normally due to some abnormality.
  • the online flag is stored in the hard disk 13.
  • the periodic communication processing is temporarily terminated, and after a predetermined period has elapsed (S415), the process returns to step S401 again.
  • the reception processing device 1 prepares for periodic communication (S402). Specifically, status data updated after the previous periodic communication process (hereinafter referred to as update data) is retrieved from the main-side status data file 13 1.
  • the searched update data is converted into a transmittable data format.
  • the reception processing device 1 After completing the preparation for the periodic communication, the reception processing device 1 transmits the periodic communication message including the update data. The message is sent to the remote server 2 (S403). After receiving the periodic communication message (S404), the remote server 2 determines whether the received message is valid (S405). One reason for judging the validity of a message is to check for missing data in the updated data and for garbled characters in the updated data. Another reason is to prevent unauthorized access by checking whether the transmitted message is transmitted from the reception processing device 1 or not.
  • the remote server 2 sets the status to "OK” (S406), and stores the received update data in the remote-side status data file 231 (S407). At this time, the update date and time are also saved.
  • the remote server 2 sets the status to "NG” (S408). The status is recorded in the hard disk 23. After determining the status, the remote server 2 sends a response message to the reception processing device 1 (S409). The response message contains status information.
  • the reception processing device 1 After transmitting the message in step S403, the reception processing device 1 waits for a response message from the remote server 2 for a predetermined period (S410). If there is no response message even after the lapse of a predetermined period (S411), the reception processing device 1 determines that some abnormality has occurred in the telecommunication line 3 or the remote server 2 and displays an error notification on the display. It is displayed on 15 (S413). The error notification may be made by sound or voice. Thereafter, the reception processing device 1 sets the online flag to “off” (S414). The work of setting the online flag to “off” may be performed manually. By setting the online flag to “OFF”, the reception processing device 1 is completely independent of the telecommunication line 3, and can independently perform the reservation reception processing in the hospital as described later.
  • the periodic communication processing is performed using the two servers, the reception processing device 1 and the remote server 2. Therefore, even if any trouble occurs in the telecommunication line 3 or the remote server 2, the reception processing device 1 can perform the reservation reception processing independently. Therefore, even when a trouble occurs, the reservation receiving system 10 can be kept operating, and the entire system does not stop.
  • the regular communication message is always transmitted from the reception processing device 1 to the remote server 2, and not vice versa. That is, the reception processing device 1 itself transmits a periodic communication message, and does not transmit / receive information to / from other than the remote server 2 which has responded. Therefore, the security of the reception processing device 1 can be extremely increased.
  • the user who has completed the reservation reception by the reception processing device 1 by the remote reservation reception processing and has been given the reservation reception number can receive information (call status data) such as the number of people waiting and the waiting time until his / her reservation reception number is called. Notification (call status notification processing).
  • the user inputs a reservation reception number to user terminal 6, and user terminal 6 transmits an inquiry message including the input reservation reception number to remote server 2 (S501). .
  • FIG. 11 shows a reservation reception number input screen when the mobile terminal 4 is used in step S501.
  • the remote server 2 After receiving the inquiry message (S502), the remote server 2 determines whether or not the regular communication processing has been performed within a predetermined period before the reception (S503). The determination as to whether or not the regular communication process has been performed is made by referring to the update date and time record in the remote-side status data file 23 1.
  • the remote server 2 sends an error notification to the user terminal 6 (S504).
  • the remote server 2 determines that the reservation receiving system 10 is operating normally.
  • the remote server 2 calculates call status data using the status data in the remote-side status data file 231. Specifically, The number of people waiting until the reservation reception number received in step S502 is called and the waiting time are calculated using the reservation reception number and the formulas (1) and (2).
  • the calculation result is transmitted to the user terminal 6 as call status data (S505).
  • the user terminal 6 displays it on the display (S506).
  • FIG. 12 shows the screen of step S506 when the mobile terminal 4 is used.
  • the user can grasp information such as the number of people waiting and the waiting time until his / her reservation reception number is called. Therefore, the user does not need to be in the hospital immediately before being called at the hospital, and can use the time until the call is effectively used.
  • the user may be notified by sound, vibration or display that the calling time is approaching before a predetermined time before being called.
  • the user of portable terminal 4 first inputs a reservation reception number and a calling condition to portable terminal 4 (S601).
  • the calling condition refers to a condition that, for example, a notification is made when the waiting time is less than 30 minutes, or a notification is made when the number of waiting people is less than 10 people.
  • the mobile terminal 4 determines whether or not the mobile terminal 4 is currently within the service area (S602). When the mobile terminal 4 is out of the service area, the portable terminal 4 calls the user's attention by a warning sound or vibration, or by displaying a warning on a display (S603). Thereafter, after a lapse of a predetermined period (S604), the operation returns to the operation of the re-start step S602.
  • the mobile terminal 4 transmits an inquiry message including the input reservation reception number to the remote server 2 (S620). Subsequently, the remote server performs the operation of steps S502 to S505 during the call status notification processing in FIG. 10 and transmits an error notification or the calculated call status data to the portable terminal 4. The mobile terminal 4 receives the error notification or the call status data (S605).
  • the mobile terminal 4 determines whether or not the reservation receiving system 10 is operating normally based on the received information (S606).
  • the reservation reception system is stopped (that is, when an error notification is received in step S605)
  • the mobile terminal 4 displays an error notification on the display or emits a warning sound to alert the user.
  • the reservation accepting system is operating normally
  • the mobile terminal 4 inputs the call status data and the input in step S601. It is determined whether or not to notify the user based on the called calling condition (S608).
  • the mobile terminal 4 determines whether the waiting time in the call status data is less than 30 minutes. Alternatively, the mobile terminal 4 determines whether the number of waiting persons in the call status data is less than 10 persons.
  • the operation returns to step S602 again after a predetermined time (S604).
  • the portable terminal 4 notifies that the call time is approaching (S609). Notification is made by sound or vibration or by screen display on the display.
  • the mobile terminal 4 determines whether or not the key operation has been performed (S611).
  • the key operation is a key operation for stopping the notification in step S609, and the key operation is performed by pressing any of a plurality of buttons (not shown) in the mobile terminal 4, for example. It has been done.
  • the key operation is performed (S611), the user recognizes the notification, and the portable terminal 4 ends the operation.
  • the portable terminal 4 returns to the playback step S602 after a predetermined time has elapsed (S640). This is because the user has not recognized the notification and needs to perform the re-notification.
  • the predetermined time in step S604 may be shorter as the calling time of the user's reservation reception number approaches. For example, if the waiting time is 10 minutes or more, the predetermined time in step S604 may be 3 minutes, and if the waiting time is less than 10 minutes, the predetermined time may be 1 minute.
  • the user can use the user terminal 6 to grasp the reservation status of the hospital.
  • the user uses user terminal 6 to send a reservation status inquiry message.
  • the message is transmitted (S701).
  • the remote server 2 determines whether or not the regular communication processing has been performed within a predetermined period before the reception (S703). If the periodic communication processing is not being performed, the remote server 2 notifies the user terminal 6 of an error (S704). At this time, the user terminal 6 receives the error notification and displays it on the display (S706). On the other hand, if the regular communication processing has been performed, the remote server 2 transmits the status data in the remote-side status data file 231 to the user terminal 6 (S705).
  • the status data includes the number of people waiting, the waiting time, the reservation reception number currently being called, and the like.
  • the user terminal 6 displays it on the display (S706).
  • FIG. 15 shows the display screen of the user terminal 6 in step S706.
  • the user can grasp the reservation status of the hospital at home or out of the office without going to the hospital, and can obtain effective information for determining whether or not to make a reservation.
  • the remote server 2 saves status data for each predetermined period (for example, every hour) from the remote-side status data file 2 3 1 to the statistical data file 2 3 3 (S 1 201) .
  • the status data for each specified time is saved as statistical data. Data is acquired every predetermined period because it is easiest to understand the congestion status by statistically analyzing the congestion status on an hourly basis.
  • conditions other than time may be set as the storage conditions for the statistical data file 233.
  • the user sends a request message for statistical data to the remote server using the user terminal 6.
  • the remote server 2 After receiving the request message (S1203), the remote server 2 sends the statistical data stored in the statistical data file 233 to the user terminal 6 (S1204). At this time, the statistical data may be sent as a graph so that the contents of the statistical data can be easily understood.
  • the user terminal 6 sends the transmitted statistical data After receiving, it is displayed on the display (S125).
  • the user can grasp the congestion state for each predetermined period. Therefore, by referring to the statistical data, it can be used as a reference when accepting reservations for hospitals.
  • reservation reception is performed by transmitting and receiving information between the reception processing device 1 and the remote server 2.
  • the reception processing device 1 can independently perform the reservation reception processing.
  • the reservation reception processing and the call processing (individual reservation reception processing) by the reception processing device 1 alone will be described.
  • the single reservation accepting process includes a ticket issuing process, a calling process, and a call skipping process.
  • the receptionist of the hospital performs a ticketing operation using the input unit 16 of the reception processing device 1 (S801). For example, the receptionist receives a consultation ticket or the like from a patient who has come to the hospital for consultation, and then inputs a ticketing request to the reception processing device 1. After the input is completed, the reception processing device 1 calculates a reservation reception number to be given to the user (S802).
  • the reservation reception numbers are counted in the order of reception, but may be counted one by one or ten. However, for example, the higher-order digits of the reservation receipt number can be used as a division of business (medical, surgical, etc.), and the upper-order digits can be assigned to dates.
  • the reception processing device 1 After calculating the reservation reception number, the reception processing device 1 performs a waiting person calculation process (S803). The number of waiting persons is calculated by equation (1). Subsequently, the reception processing device 1 performs a waiting time calculation process (S804). The waiting time is calculated by equation (2). After completing the above calculation, the reception processing device 1 issues a reservation reception number ticket from the ticket issuing unit 17 (S805). Subsequently, the reception processing device 1 displays the number of people waiting and the waiting time on the notice display 15 (S806). Note that the calculation results in steps S802 to S804 are stored in the main-side status data file 131, and the periodic communication processing (S41, S42) performed after step S806 is performed. ) Is sent to the remote server 2 as status data. The periodic communication process is the same as the operation in FIG.
  • the waiting time is calculated from equation (2) based on the number of waiting people updated in step S903.
  • the calculation results of steps S902 to S904 are stored in the main-side situation data file 131.
  • the reception processing device 1 emits a ringing sound or a calling voice (S905), and displays the call number calculated in step S902 on the bulletin board display (S906). Thereafter, periodic communication processing (S41, S42) is performed between the reception processing device 1 and the remote server 2.
  • the patient can be regarded as absent and the reservation number of the patient can be skipped.
  • the doctor or nurse in charge in the examination room instructs to skip using the input unit 16 of the reception processing device 1 (S1001).
  • the skipped reservation reception number (skip data) is recorded in the absentee table in the main-side status data file 131 (S1002), and the skip data is displayed on the notice display 15 of the reception processing device 1.
  • FIG. 20 shows the screen of the bulletin display in step S1003. By displaying the skipped reservation number, it is easy to determine whether the patient was skipped.
  • the reception processing device 1 counts the number of skipped reservation reception numbers (the number of skips) (S1004). After calculating the number of skips, the reception processing device 1 performs the operation (call processing) of steps S902 to S906 in FIG. After the end of the calling process, the reception processing device 1 performs a periodic communication process.
  • the status data transmitted in the periodic communication process may include the skip number. If the patient with the skipped reservation number does not appear within the predetermined period, or if the patient with the skipped reservation number appears within the predetermined period, the reception worker erases the corresponding reservation number. it can. Referring to FIG.
  • the reception worker uses the input unit 16 of the reception processing device 1 to delete the reservation reception number of the patient who has not appeared within a predetermined time (S1101).
  • the appointment receipt number of the patient who has appeared within the predetermined time period and has undergone a medical examination is deleted (S111).
  • the corresponding reservation reception number in the absentee table in the reception processing device 1 is deleted, and as a result, the skip data is updated (S1103).
  • the updated skip data is displayed on the bulletin board display 15 (S1104).
  • the reception processing device 1 also updates the skip number (S111). After that, the reception processing device 1 performs a periodic communication process (S41, S42).
  • the reservation reception processing can be performed by the reception processing device 1 alone. Therefore, the reservation accepting process can be performed for a patient who does not use the user terminal 6. Also, even if an abnormality occurs in the telecommunications line 3, the reception processing device 1 alone can receive and call a reservation.
  • the status data in the reception processing device 1 and the remote server 2 are synchronized by the periodic communication process, even if the reception processing device 1 performs the single reservation reception process, the call status data and the call status data in the call status notification process are processed. However, the accuracy of the status data in the congestion status notification processing does not decrease.
  • the reception processing device 1 and the remote server 2 may be managed by the same company or may be managed by different companies.
  • the notice display 15 of the reception processing device 1 may be installed in a facility such as a hospital, a bank, a restaurant, or a plurality of displays may be installed in a hospital, a bank, or a coffee shop or a shopping street near a restaurant facility. You may. By installing the signage display 15 outside the facility, users who do not use the user terminal 6 such as the mobile terminal 4 do not need to stay in the facility and wait for their turn.
  • the “predetermined period” in the description of the embodiment of the present invention is appropriately determined, and may be all set as the same period, or may be set as individual periods.
  • the embodiment of the present invention has been described above, but the above-described embodiment is merely an example for implementing the present invention. Therefore, the present invention is not limited to the above-described embodiment, and can be implemented by appropriately modifying the above-described embodiment without departing from the spirit thereof.

Abstract

When a user wants to make a reservation, the user inputs a reservation request to a user terminal (6). The user terminal (6) transmits the reservation request to a remote server (2). The remote server (2) stores the reservation request. When a reception processing device (1) transmits an enquiry message to the remote server (2), the remote server (2) responds to the enquiry message and transmits the stored reservation request to the reception processing device (1). The reception processing device (1) performs a reservation reception according to the reservation request received. By the aforementioned operation, the reception processing device (1) receives information from the server which has responded to the enquiry message and accordingly, it is possible to prevent unauthorized access.

Description

明細書 予約受付方法、 事前呼出方法及びそのプログラム 技術分野  Description Reservation accepting method, advance calling method and its program
本発明は、 予約受付方法及びそのプログラムに関し、 さらに詳しくは、 ユーザ 端末と、 前記ユーザ端末と電気通信回線を介して接続可能なリモートサーバと、 前記リモートサーバと前記電気通信回線を介して接続可能な受付処理装置とを用 いた、 サービスの提供を受けるための予約受付方法及ぴそのプログラムに関する。 背景技術  The present invention relates to a reservation receiving method and a program therefor, and more specifically, a user terminal, a remote server connectable to the user terminal via a telecommunication line, and a remote server connectable to the remote server via the telecommunication line. The present invention relates to a reservation reception method for receiving service provision using a simple reception processing device and a program therefor. Background art
現在、 銀行では受付窓口への先着順に利用者に予約受付番号を発行し、 予約受 付番号順に利用者に対してサービスを提供している。 また、 病院では先着順に予 約受付番号を発行し、 予約受付番号順に診察を行っている。  Currently, banks issue reservation reception numbers to users on a first-come, first-served basis, and provide services to users in the order of reservation reception numbers. Hospitals also issue reservation numbers on a first-come, first-served basis, and perform consultations in the order of reservation numbers.
以上に示したように、 銀行や病院のようなユーザに来所してもらいサービスを 提供する業種では、 先着順にサービスを提供するために予約受付番号を発券する システムが導入されている場合がある。  As described above, in industries such as banks and hospitals that provide users with services to visit, systems for issuing reservation receipt numbers to provide services on a first-come, first-served basis may be introduced. .
し力 しながら、 発券システムの場合はサービス窓口や診察室といつたサービス 提供所に列をなして並ぶ必要はないものの、 サービス提供所付近にはとどまって おく必要があった。 なぜなら呼出を受ける時期は不明であり、 電光掲示板の見え る範囲又は呼出音声が聞こえる範囲内にいなければ、 自己の予約受付番号が呼び 出されたか否かがわからないからである。 よって、 受付後サービスを受けるまで の時間帯は銀行内や病院内といった所定の場所に拘束されなければならず、 時間 の無駄が生じていた。  However, in the case of the ticketing system, it was not necessary to line up with the service counters, such as the service counter and consultation room, but it was necessary to stay near the service provider. This is because it is unknown when the call will be received, and if it is not within the range where the electronic bulletin board can be seen or the calling voice can be heard, it is not known whether or not the reservation reception number has been called. Therefore, the time period from reception to reception of the service must be restricted to a predetermined place such as in a bank or a hospital, which wastes time.
このような時間の無駄の解消を目的として、 近年携帯電話によるィンターネッ ト接続機能を使った診察申し込みシステムが注目を浴びている。 しかしながら、 セキュリティの確保の問題ゃィンターネットで障害が発生した場合にシステムが 停止する等の問題がある。 発明の開示 In order to eliminate such waste of time, a medical examination application system using the Internet connection function using a mobile phone has recently attracted attention. However, there is a problem of security assurance. If a failure occurs on the Internet, the system stops. Disclosure of the invention
本発明の目的は、 予約受付後サービスの提供を受けるまでの時間を有効に利用 できる予約受付システムを提供することである。  SUMMARY OF THE INVENTION An object of the present invention is to provide a reservation receiving system that can effectively utilize the time from receiving a reservation until receiving service.
本発明の他の目的は、 高いセキュリティを確保でき、 電気通信回線に異常が発 生しても業務を継続できる予約受付システムを提供することである。  Another object of the present invention is to provide a reservation receiving system that can ensure high security and can continue business even if an abnormality occurs in a telecommunication line.
本発明による予約受付方法は、 ユーザ端末と、 ユーザ端末に接続可能なリモー トサーバと、 リモートサーバに接続可能な受付処理装置とによる予約受付方法で あって、 ユーザ端末からリモートサーバに予約依頼を送信するステップと、 リモ 一トサーバに送信された予約依頼を受付処理装置に送信するステップと、 受付処 理装置に送信された予約依頼に基づいて予約受付を行うステップとを備える。 ユーザが予約を行うとき、 ユーザはユーザ端末に予約依頼を入力する。 ユーザ 端末は入力された予約依頼をリモートサーバに送信する。 予約依頼を受信したリ モートサーバは、 その予約依頼を受付処理装置に送信する。 このように、 予約依 頼はユーザ端末から必ずリモートサーパを経由して受付処理装置へ送信される。 よって、 受付処理装置はユーザ端末から予約依頼等の情報を直接受信することは ない。 そのため、 受付処理装置はユーザ端末からの不正アクセスを防止でき、 受 付処理装置のセキュリティは向上する。 その結果、 不正アクセス等による受付処 理装置の動作停止を防止でき、 受付処理装置は継続して動作することができる。 好ましくは、 予約受付方法はさらに、 受付処理装置からリモートサーバに問い 合わせを行ぅステツプを備え、 予約依頼を受付処理装置に送信するステツプでは、 問い合わせに応じて、 予約依頼を送信する。  The reservation receiving method according to the present invention is a reservation receiving method using a user terminal, a remote server connectable to the user terminal, and a reception processing device connectable to the remote server, wherein the user terminal transmits a reservation request to the remote server. And transmitting the reservation request transmitted to the remote server to the reception processing device, and receiving the reservation based on the reservation request transmitted to the reception processing device. When a user makes a reservation, the user inputs a reservation request to the user terminal. The user terminal sends the input reservation request to the remote server. Upon receiving the reservation request, the remote server transmits the reservation request to the reception processing device. Thus, the reservation request is always transmitted from the user terminal to the reception processing device via the remote server. Therefore, the reception processing device does not directly receive information such as a reservation request from the user terminal. Therefore, the reception processing device can prevent unauthorized access from the user terminal, and the security of the reception processing device is improved. As a result, it is possible to prevent the operation of the reception processing device from being stopped due to unauthorized access or the like, and the reception processing device can continue to operate. Preferably, the reservation receiving method further includes an inquiry step from the reception processing device to the remote server, and the step of transmitting the reservation request to the reception processing device transmits the reservation request in response to the inquiry.
この場合、 リモートサーバは受付処理装置からの問い合わせがない限り、 予約 依頼を受付処理装置に送信しない。 すなわち、 受付処理装置は自身が発信した問 い合わせに応じてリモートサーバから送信される予約依頼しか受信しない。 よつ て、 受付処理装置のセキュリティはさらに向上する。  In this case, the remote server does not transmit the reservation request to the reception processing device unless there is an inquiry from the reception processing device. That is, the reception processing device receives only the reservation request transmitted from the remote server in response to the inquiry transmitted by itself. Thus, the security of the reception processing device is further improved.
なお、 この場合、 受付処理装置のアドレスを固定する必要がなくなる。 なぜな ら、 リモートサーバから受付処理装置に予約依頼が送信される場合、 必ずその前 に受付処理装置からリモートサーパへ問い合わせが行われ、 その問い合わせによ りリモートサーバが受付処理装置のアドレスを特定するからである。 よって、 受 付処理装置は専用線を利用しなくてよく、 設備費用を抑えることができる。 好ましくは、 予約受付方法はさらに、 問い合わせに対するリモートサーバから の応答を所定期間内に受付処理装置が受信した力否かを判断するステップと、 応 答を所定期間内に受信しなかったと判断した場合、 受付処理装置のオペレータに 警告を通知するステップとを備える。 In this case, it is not necessary to fix the address of the reception processing device. The reason is that before the reservation request is sent from the remote server to the reception processing device, the reception processing device always makes an inquiry to the remote server before the request is sent. It is because it specifies. Therefore, The processing equipment does not need to use a dedicated line, and equipment costs can be reduced. Preferably, the reservation receiving method further includes a step of determining whether or not the reception processing device has received a response from the remote server to the inquiry within a predetermined period, and a step of determining that the response has not been received within the predetermined period. Notifying an operator of the reception processing device of a warning.
この場合、 受付処理装置はリモートサーバに問い合わせをした後、 所定期間内 にリモートサーバからの応答を受信したか否かを判断する。 リモートサーバから の応答がない場合は、 電気通信回線ゃリモートサーバに何らかの障害が発生して いると考えられる。 そこで、 応答がない場合、 受付処理装置はオペレータに対し て音声や画面表示等により警告を通知する。 その結果、 オペレータは電気通信回 線やリモートサーバに障害が発生していることを容易に認識でき、 迅速な対応を 行うことができる。  In this case, after making an inquiry to the remote server, the reception processing device determines whether a response from the remote server has been received within a predetermined period. If there is no response from the remote server, it is likely that some trouble has occurred in the telecommunications line ゃ remote server. Therefore, if there is no response, the reception processing device notifies the operator of a warning by voice or screen display. As a result, the operator can easily recognize that a failure has occurred in the telecommunication line or the remote server, and can take prompt action.
好ましくは、 予約受付方法はさらに、 受付処理装置からリモートサーバに予約 状況を示す予約状況データを所定期間ごとに送信するステップと、 ユーザ端末か らの要求に応じてリモートサーバからユーザ端末に予約状況データを送信するス テツプとを備える。  Preferably, the reservation receiving method further comprises: transmitting reservation status data indicating the reservation status from the reception processing device to the remote server at predetermined intervals; and transmitting the reservation status from the remote server to the user terminal in response to a request from the user terminal. And a step for transmitting data.
この場合、 受付処理装置は予約状況データを所定期間ごとにリモートサーバに 送信する。 そのため、 リモートサーバ内の予約状況データを受付処理装置内の予 約状況データに同期させることができる。 さらに、 リモートサーバはユーザ端末 からの要求に応じて予約状況データを返信する。 これにより、 ユーザは予約依頼 を行う前にほぼ最新の予約状況を参照できる。  In this case, the reception processing device transmits the reservation status data to the remote server every predetermined period. Therefore, the reservation status data in the remote server can be synchronized with the reservation status data in the reception processing device. In addition, the remote server returns reservation status data in response to a request from the user terminal. This allows the user to refer to the most recent reservation status before making a reservation request.
好ましくは、 予約受付方法はさらに、 ユーザ端末からリモートサーバに予約受 付番号を送信するステップと、 リモートサーパに送信された予約受付番号及ぴ予 約状況データに基づいて、 サービスの提供を受けるまでの待ち人数及び/又は待 ち時間を呼出状況データとして算出するステップと、 リモートサーバからユーザ 端末に呼出状況データを送信するステップとを備える。  Preferably, the reservation receiving method further includes: transmitting a reservation receiving number from the user terminal to the remote server; and receiving service provision based on the reservation receiving number and the reservation status data transmitted to the remote server. Calculating the number of people waiting and / or the waiting time as call status data; and transmitting the call status data from the remote server to the user terminal.
この場合、 ユーザ端末のユーザは予約完了後に、 予約受付番号をユーザ端末か らリモートサーバに送信する。 リモートサーパは予約受付番号及び予約状況デー タに基づいて、 ユーザがサービスの提供を受けるまでの待ち人数及び/又は待ち 時間を呼出状況データとして算出する。 算出された呼出状況データはユーザ端末 に送信される。 よって、 ユーザは自分がサービスの提供を受けるまでにあとどの 位の待ち人数がいるか、 又はどの位の待ち時間があるかを把握できる。 その結果、 ユーザがサービスの提供を受けるまでの時間を有効に活用できる。 In this case, the user of the user terminal transmits the reservation reception number from the user terminal to the remote server after the reservation is completed. Based on the reservation reception number and reservation status data, the remote server waits for the user to receive the service and / or The time is calculated as call status data. The calculated call status data is transmitted to the user terminal. Therefore, the user can grasp how many people are waiting or how long the waiting time is before receiving the service. As a result, the time until the user receives the service can be effectively used.
本発明による事前呼出方法は、 サービスの提供を受けるまでの呼出状況データ を有するリモートサーバに接続可能なユーザ端末による事前呼出方法であって、 外部から入力された呼出条件を保存するステップと、 外部から入力された予約受 付番号をリモートサーバに送信するステップと、 予約受付番号に基づいてリモー トサーパから送信された呼出状況データを受信するステップと、 呼出状況データ が呼出条件を満たすか否かを判断するステップと、 呼出条件を満たしたとき、 ュ 一ザ端末のユーザに呼出条件を満たした旨を通知するステップとを備える。  A pre-call method according to the present invention is a pre-call method by a user terminal connectable to a remote server having call status data until a service is provided, comprising: a step of storing a call condition input from outside; Transmitting the reservation receipt number input from the remote server to the remote server based on the reservation receipt number, and determining whether the call status data satisfies the calling condition based on the reservation receipt number. The method includes a judging step and a step of notifying the user of the user terminal that the calling condition is satisfied when the calling condition is satisfied.
本発明による事前呼出方法では、 ユーザはたとえばサービスを受けるまでの待 ち人数が 1 0人未満になった場合に通知する等の呼出条件をユーザ端末に入力す る。 その後、 ユーザはユーザ端末に予約受付番号を入力し、 ユーザ端末は入力さ れた予約受付番号をリモートサーバに送信する。 リモートサーパは予約受付番号 に基づいて予約受付番号のユーザがサービスの提供を受けるまでの呼出状況デー タをユーザ端末に送信する。 ユーザ端末は受信した呼出状況データが呼出条件を 満たすか否かを判断し、 満たした場合はその旨の通知を音声や振動、 又は画面表 示等により行う。 その結果、 ユーザは自分がサービスの提供を受ける番が近づい ている旨をユーザ端末に知らせてもらうことができる。 その結果、 ユーザは自分 がサービスの提供を受けるまでの時間を有効に活用できる。  In the advance calling method according to the present invention, the user inputs calling conditions to the user terminal, for example, to notify when the number of people waiting for receiving the service becomes less than 10 people. Thereafter, the user inputs the reservation reception number to the user terminal, and the user terminal transmits the input reservation reception number to the remote server. The remote server transmits the call status data until the user of the reservation reception number receives service provision to the user terminal based on the reservation reception number. The user terminal determines whether the received call status data satisfies the call conditions, and if so, notifies the user by voice, vibration, screen display, or the like. As a result, the user can be informed to the user terminal that the turn to receive the service is approaching. As a result, the user can effectively utilize the time until the service is provided.
好ましくは、 事前呼出方法は、 判断するステップで呼び出し条件を満たさない と判断したとき、 予約受付番号をリモートサーバに送信するステップと、 呼出状 況データを受信するステップと、 呼出状況データが呼出条件を満たすか否かを判 断するステップとを繰り返す。  Preferably, the advance calling method includes: a step of transmitting a reservation reception number to a remote server when it is determined in the determining step that the calling condition is not satisfied; a step of receiving the calling status data; And the step of determining whether or not the condition is satisfied is repeated.
この場合、 ユーザ端末は呼出状況データが呼出条件を満たすまで、 予約受付番 号をリモートサーバに送信し、 呼出状況データを受信し、 受信した呼出状況が呼 出条件を満足するか否かを判断するという一連の動作を繰り返す。 その結果、 ュ 一ザは 1回呼出条件及び予約受付番号を入力すれば、 繰り返し予約受付番号の入 力を繰り返すことなく自分がサービスの提供を受ける番が近づいている旨をユー ザ端末に知らせてもらうことができる。 図面の簡単な説明 In this case, the user terminal transmits the reservation reception number to the remote server until the call status data satisfies the call condition, receives the call status data, and determines whether the received call status satisfies the call condition. Is repeated. As a result, the user can enter the calling condition and the reservation reception number once and enter the reservation reception number repeatedly. The user can be notified of the fact that the turn to receive the service is approaching without repetition. BRIEF DESCRIPTION OF THE FIGURES
図 1は、 本発明の実施の形態による予約受付システムの全体構成を示す機能ブ ロック図である。  FIG. 1 is a functional block diagram showing an overall configuration of a reservation receiving system according to an embodiment of the present invention.
図 2は、 図 1に示した予約受付システムの予約依頼処理の動作を示すフロー図 である。  FIG. 2 is a flowchart showing an operation of a reservation request process of the reservation reception system shown in FIG.
図 3は、 図 2中のステップ S 1 0 1における予約依頼情報入力画面図である。 図 4は、 図 1に示した予約受付システムの予約受付処理の動作を示すフロー図 である。  FIG. 3 is a diagram of a reservation request information input screen in step S101 in FIG. FIG. 4 is a flowchart showing the operation of the reservation receiving process of the reservation receiving system shown in FIG.
図 5は、 図 4中のステップ S 2 1 5における掲示ディスプレイ画面図である。 図 6は、 図 1に示した予約受付システムの完了通知処理の動作を示すフロー図 である。  FIG. 5 is a display screen view of the bulletin board at step S215 in FIG. FIG. 6 is a flowchart showing the operation of the completion notification process of the reservation receiving system shown in FIG.
図 7は、 図 6中のステップ S 3 0 1における入力画面図である。  FIG. 7 is an input screen diagram in step S301 in FIG.
図 8は、 図 6中のステップ S 3 0 5における完了通知画面図である。  FIG. 8 is a diagram of a completion notification screen in step S305 in FIG.
図 9は、 図 1に示した予約受付システムの定期通信処理の動作を示すフロー図 である。  FIG. 9 is a flowchart showing the operation of the regular communication process of the reservation receiving system shown in FIG.
図 1 0は、 図 1に示した予約受付システムの呼出状況通知処理の動作を示すフ ロー図である。  FIG. 10 is a flowchart showing an operation of a call status notification process of the reservation receiving system shown in FIG.
図 1 1は、 図 1 0中のステップ S 5 0 1における入力画面図である。  FIG. 11 is an input screen diagram in step S501 in FIG.
図 1 2は、 図 1 0中のステップ S 5 0 6における呼出状況通知画面図である。 図 1 3は、 図 1に示した予約受付システムの呼出状況通知処理の他の例の動作 を示すフロー図である。  FIG. 12 is a diagram of a call status notification screen in step S506 in FIG. FIG. 13 is a flowchart showing the operation of another example of the call status notification process of the reservation receiving system shown in FIG.
図 1 4は、 図 1に示した予約受付システムの混雑状況通知処理の動作を示すフ ロー図である。 ,  FIG. 14 is a flowchart showing the operation of the congestion status notification process of the reservation receiving system shown in FIG. ,
図 1 5は、 図 1 4中のステップ S 7 0 6における混雑状況通知画面図である。 図 1 6は、 図 1に示した予約受付システムの銃計情報通知処理の動作を示すフ ロー図である。 図 1 7は、 図 1に示した予約受付システムの発券処理の動作を示すフロー図で ある。 FIG. 15 is a congestion status notification screen view in step S706 in FIG. FIG. 16 is a flowchart showing the operation of the gun gauge information notification process of the reservation receiving system shown in FIG. FIG. 17 is a flowchart showing the operation of the ticket issuing process of the reservation receiving system shown in FIG.
図 1 8は、 図 1に示した予約受付システムの呼出処理の動作を示すフロー図で ある。  FIG. 18 is a flowchart showing an operation of a call process of the reservation receiving system shown in FIG.
図 1 9は、 図 1に示した予約受付システムのスキップ処理の動作を示すフロー 図である。  FIG. 19 is a flowchart showing the operation of the skip processing of the reservation receiving system shown in FIG.
図 2 0は、 図 1 9中のステップ S 1 0 0 3における掲示ディスプレイ画面図で ある。  FIG. 20 is a notice display screen view in step S103 in FIG.
図 2 1は、 図 1に示した予約受付システムの呼出スキップ処理の他の例の動作 を示すフロー図である。 発明を実施するための最良の形態  FIG. 21 is a flowchart showing the operation of another example of the call skipping process of the reservation receiving system shown in FIG. BEST MODE FOR CARRYING OUT THE INVENTION
以下、 本発明の実施の形態を図面を参照して詳しく説明する。 図中同一又は相 当部分には同一符号を付してその説明を援用する。  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts have the same reference characters allotted, and description thereof will be used.
1 . 予約受付システムの全体構成  1. Overall configuration of reservation reception system
図 1を参照して、 予約受付システム 1 0は、 受付処理装置 1とリモートサーバ 2とを備える。 受付処理装置 1とリモートサーパ 2とはインターネット等の電気 通信回線 3を介して接続される。  Referring to FIG. 1, a reservation reception system 10 includes a reception processing device 1 and a remote server 2. The reception processing device 1 and the remote server 2 are connected via an electric communication line 3 such as the Internet.
受付処理装置 1は、 C P U (Central Processing Unit.) 1 1 と、 メモリ 1 2と、 ハードディスク 1 3と、 掲示ディスプレイ 1 5と、 マウスやキーボード等の入力 部 1 6と、 発券部 1 7とを含む。 ハードディスク 1 3はメイン側状況データファ ィノレ 1 3 1とメイン側受付データファイル 1 3 2とを含む。 メィン側状況データ ファイル 1 3 1は、 発行済みの予約受付番号のうちの最新の予約受付番号、 待ち 人数、 待ち時間、 現在呼び出し中の予約受付番号や呼び出し時に不在であった者 の予約受付番号等の情報 (以下、 状況データと称する) を記憶する。 メイン側受 付データファイル 1 3 2は予約依頼を記憶する。 掲示ディスプレイ 1 5は病院内 で来訪者が閲覧可能な場所に設置されるのが好ましい。 また、 病院内に複数の診 察室がある場合は、 入力部 1 6は受付場所及び診察室ごとに設置されてもよい。 発券部 1 7は来訪者に対して予約受付番号券を発行する。 受付処理装置 1はリモ 一トサーバ 2から送信される予約依頼に基づいて、 診察の予約受付業務を行う。 また、 受付処理装置 1はリモートサーバ 2とは独立して、 予約の受付を行うこと もできる。 The reception processing device 1 includes a CPU (Central Processing Unit.) 11, a memory 12, a hard disk 13, a signboard display 15, an input unit 16 such as a mouse and a keyboard, and a ticketing unit 17. Including. The hard disk 13 includes a main-side status data file 13 1 and a main-side reception data file 13 2. The main status data file 1 3 1 contains the latest reservation reception number among the issued reservation reception numbers, the number of people waiting, the waiting time, the reservation reception number currently being called, and the reservation reception number of the person who was absent at the time of the call (Hereinafter referred to as status data). The main reception data file 1 32 stores the reservation request. The signage display 15 is preferably installed at a place in the hospital where visitors can view. When a hospital has a plurality of examination rooms, the input unit 16 may be provided for each reception place and each examination room. The ticketing section 17 issues a reservation receipt number ticket to visitors. Reception processing device 1 is remote Based on the reservation request sent from the central server 2, it performs the consultation reservation service. Further, the reception processing device 1 can also accept a reservation independently of the remote server 2.
一方、 リモートサーバ 2は、 C P U 2 1と、 メモリ 2 2と、 ハードディスク 2 3とを含む。 ハードディスク 2 3は、 リモート側状況データフアイル 2 3 1と、 リモート側受付データファイル 2 3 2と、 統計データファイル 2 3 3とを含む。 リモート側状況データファイル 2 3 1は受付処理装置 1から送信された状況デー タが保存される。 リモート側受付データファイル 2 3 2はユーザが利用する P D A ( Personal Digital Assistant ) や携帯電話機等の携帯端末 4又は固定端末 5 (以下、 携帯端末 4及び固定端末 5をユーザ端末 6とも称する) から送信され た予約依頼を保存する。 統計データファイル 2 3 3は所定期間ごと (たとえば、 1時間ごと) の状況データの統計結果が保存される。 リモートサーバ 2はユーザ 端末 6から電気通信回線 3を介して予約依頼を受ける。 リモートサーパ 2が予約 依頼を受けることで、 ユーザは病院へ行く前に自宅又は外から診察を予約できる。 受付処理装置 1及ぴリモートサーバ 2に予約受付プログラムをインストールす ることで、 受付処理装置 1及びリモートサーバ 2は以下に示す予約受付処理を実 行できる。 なお、 予約受付プログラムはメモリ 1 2及ぴメモリ 2 2にマイクロプ ログラムとして予め記憶されていてもよい。  On the other hand, the remote server 2 includes a CPU 21, a memory 22, and a hard disk 23. The hard disk 23 includes a remote-side status data file 2 31, a remote-side reception data file 2 32, and a statistical data file 2 33. The remote-side status data file 2 31 stores the status data transmitted from the reception processing device 1. The remote reception data file 2 3 2 is transmitted from a portable terminal 4 or a fixed terminal 5 such as a PDA (Personal Digital Assistant) or a mobile phone used by the user (hereinafter, the portable terminal 4 and the fixed terminal 5 are also referred to as a user terminal 6). Save the requested reservation. The statistical data file 233 stores the statistical results of the status data every predetermined period (for example, every hour). The remote server 2 receives a reservation request from the user terminal 6 via the telecommunication line 3. When the remote server 2 receives the reservation request, the user can reserve an examination from home or outside before going to the hospital. By installing the reservation reception program on the reception processing device 1 and the remote server 2, the reception processing device 1 and the remote server 2 can execute the following reservation reception processing. The reservation accepting program may be stored in advance in the memories 12 and 22 as a microprogram.
また、 携帯端末 4は C P U 4 1及ぴメモリ 4 2を含み、 事前呼出プログラムを インストールすることで、 事前呼出処理を行うことができる。 携帯端末 4は予め 事前呼出プログラムをインストールされたうえで販売されてもよい。 また、 リモ 一トサーバ 2のハードディスク 2 3に事前呼出プログラムが予め保存されてぉり、 ユーザが携帯端末 4を購入後、 リモートサーパ 2から事前呼出プログラムを携帯 端末 4にダウンロードしてもよい。  Also, the mobile terminal 4 includes a CPU 41 and a memory 42, and can perform a pre-call process by installing a pre-call program. The mobile terminal 4 may be sold after a prior call program is installed in advance. Further, the pre-call program may be stored in the hard disk 23 of the remote server 2 in advance, and the user may purchase the mobile terminal 4 and then download the pre-call program from the remote server 2 to the mobile terminal 4.
2 . 遠隔予約受付処理  2. Remote reservation acceptance processing
予約受付システム 1 0による予約受付処理のうち、 病院外にいるユーザから予 約受付を行う動作 (以下、 遠隔予約受付処理と称する) について説明する。 ユー ザが在宅のまま診察の予約を行う場合や、 外出しているユーザが診察の予約を行 う場合に遠隔予約受付処理が行われる。 W 遠隔予約受付処理はリモートサーバ 2がユーザ端末 6から予約依頼を受ける処 理 (仮予約受付処理) と、 所定期間ごとにリモートサーバ 2が受付処理装置 1へ 予約依頼を送信し、 受付処理装置 1がユーザの予約を受け付ける処理 (本予約受 付処理) と、 予約受付が完了したか否かをユーザが問い合わせる処理 (予約完了 問い合わせ処理) とに分かれる。 以下、 それぞれの処理について説明する。 The operation of receiving a reservation from a user outside the hospital in the reservation reception processing by the reservation reception system 10 (hereinafter, referred to as a remote reservation reception processing) will be described. When the user makes an appointment for an examination while staying at home, or when an out-of-home user makes an appointment for an examination, the remote appointment reception process is performed. W The remote reservation receiving process is a process in which the remote server 2 receives a reservation request from the user terminal 6 (temporary reservation receiving process), and the remote server 2 transmits a reservation request to the reception processing device 1 at predetermined intervals, and the reception processing device 1 is divided into a process for accepting the user's reservation (final reservation acceptance process) and a process for the user to inquire whether the reservation acceptance has been completed (reservation completion inquiry process). Hereinafter, each process will be described.
2 - 1 . 仮予約受付処理  2-1. Temporary reservation acceptance process
図 2を参照して、 ユーザが病院の予約を行いたい場合、 ユーザはユーザ端末 6 の予約依頼情報入力画面に予約依頼情報を入力する (S 1 0 1 ) 。 図 3にユーザ が携帯端末 4を用いた場合の予約依頼情報入力画面を示す。 予約依頼情報にはュ 一ザの氏名、 生年月日、 携帯電話番号、 初診でない場合は診察券番号をそれぞれ 入力する。 なお、 ユーザの氏名と診察券番号と生年月日とがユーザ I Dと連結し てリモートサーパ 2のハードディスク 2 3内に予め保存されている場合は、 ユー ザは予約依頼情報としてユーザ I Dをユーザ端末 6に入力してもよい。 ユーザ端 末 6は入力された予約依頼情報をリモートサーバ 2に送信する ( S 1 0 2 ) 。 リ モートサーバ 2は予約依頼情報を受信後 (S 1 0 3 ) 、 受信前の所定期間内に定 期通信処理が行われた力否かを判断する (S 1 0 4 ) 。 ここで、 定期通信処理と は、 受付処理装置 1とリモートサーパ 2との間で情報を定期的に送受信する処理 をいう。 定期通信処理については後述する。 定期通信処理が行われたか否かは、 リモート側状況データファイル 2 3 1内の状況データがステップ S 1 0 3の受信 前の所定期間内に更新されているか否かで判断される。  Referring to FIG. 2, when the user wants to make a hospital reservation, the user inputs the reservation request information on the reservation request information input screen of the user terminal 6 (S101). FIG. 3 shows a reservation request information input screen when the user uses the mobile terminal 4. In the reservation request information, enter the user's name, date of birth, mobile phone number, and if not the first consultation, the consultation ticket number. If the user's name, consultation ticket number, and date of birth are linked to the user ID and stored in the hard disk 23 of the remote server 2 in advance, the user uses the user ID as the reservation request information. It may be input to terminal 6. The user terminal 6 transmits the inputted reservation request information to the remote server 2 (S102). After receiving the reservation request information (S103), the remote server 2 determines whether or not the periodic communication processing has been performed within a predetermined period before the reception (S104). Here, the periodic communication process refers to a process of periodically transmitting and receiving information between the reception processing device 1 and the remote server 2. The regular communication processing will be described later. Whether or not the periodic communication processing has been performed is determined based on whether or not the status data in the remote-side status data file 231 has been updated within a predetermined period before the reception of step S103.
ステップ S 1 0 4で定期通信処理が行われていないと判断した場合、 リモート サーバ 2は予約受付システム 1 0内で異常が発生していると判断する。 なぜなら、 定期通信処理が行われていないということは、 受付処理装置 1に異常が発生して いるか、 又は電気通信回線 3に異常が発生していると考えられるからである。 よ つてこの場合、 リモートサーバ 2は予約受付システムが現在停止している旨の通 知 (以下、 エラー通知と称する) をユーザ端末 6に送信する (S 1 0 5 ) 。 ユー ザ端末 6は停止している旨の情報を受信し、 ディスプレイ (図示せず) に表示す る (S 1 0 8 ) 。  If it is determined in step S104 that the periodic communication process has not been performed, the remote server 2 determines that an abnormality has occurred in the reservation receiving system 10. This is because the fact that the periodic communication processing is not performed is because it is considered that an abnormality has occurred in the reception processing device 1 or an abnormality has occurred in the telecommunication line 3. Therefore, in this case, the remote server 2 transmits to the user terminal 6 a notification that the reservation reception system is currently stopped (hereinafter, referred to as an error notification) (S105). The user terminal 6 receives the information indicating that it is stopped, and displays it on a display (not shown) (S108).
—方、 ステップ S 1 0 4での判断の結果、 所定期間内に定期通信処理が行われ ていたと判断した場合、 リモートサーバ 2は仮予約受付処理を行う (S 1 0 6 ) 。 具体的には、 リモートサーパ 2はユーザ端末 6から送信された予約依頼情報をリ モート側受付データフアイル 2 3 2に記憶する。 —As a result of the determination in step S104, the periodic communication process is performed within a predetermined period. If it is determined that the reservation has been made, the remote server 2 performs a tentative reservation acceptance process (S106). Specifically, the remote server 2 stores the reservation request information transmitted from the user terminal 6 in the remote-side reception data file 232.
仮予約受付処理が終了した後、 リモートサーバ 2は仮予約受付完了通知をユー ザ端末 6に送信する (S 1 0 7 ) 。 ユーザ端末 6は仮予約受付完了通知を受信し、 ディスプレイに表示する (S 1 0 8 ) 。  After the provisional reservation reception processing is completed, the remote server 2 transmits a provisional reservation reception completion notification to the user terminal 6 (S107). The user terminal 6 receives the tentative reservation acceptance completion notice and displays it on the display (S108).
2 - 2 . 本予約受付処理  2-2. Book Reception Processing
仮予約受付処理が完了しただけでは、 ユーザの予約は完了しない。 受付処理装 置 1がユーザの予約受付を行って初めてユーザの予約が完了する。 そのため、 受 付処理装置 1がリモートサーバ 2から予約依頼情報を取得する本予約受付処理が 行われる。 図 4に本予約受付処理の動作を示す。 なお、 図 4に示すように、 本予 約受付処理の全体動作をステップ S 2 0とする。  The user's reservation is not completed just by completing the provisional reservation reception process. The user reservation is completed only after the reception processing device 1 receives the user reservation. Therefore, the reception processing device 1 performs the main reservation reception process of acquiring the reservation request information from the remote server 2. Fig. 4 shows the operation of this reservation acceptance process. As shown in FIG. 4, the entire operation of the reservation accepting process is defined as step S20.
図 4を参照して、 本予約受付処理 ( S 2 0 ) は受付処理装置 1とリモートサー バ 2とが定期的に情報を送受信する定期通信処理の後で行われる。 なお、 定期通 信処理については後述する。 受付処理装置 1はリモート側受付データファイル 2 3 2に新たな予約依頼情報が記録されているか否かを判断する。 (S 2 0 2〜S 2 0 6 ) 。 ここで、 新たな予約依頼情報とは、 前回の本予約受付処理以降にリモ ート側受付データファイル 2 3 2に保存された予約依頼情報をいう。 受付処理装 置 1は新たな予約依頼情報の有無についての問い合わせメッセージをリモートサ ーバ 2に送信する ( S 2 0 2 ) 。 リモートサーバ 2は問い合わせメッセージを受 信後 ( S 2 0 3 ) 、 リモート側受付データファイル 2 3 2内に新たな予約依頼情 報が保存されているか否かを判断し、 その判断結果を送信する ( S 2 0 4 ) 。 受 付処理装置 1はリモートサーバ 2からの判断結果を受信後 ( S 2 0 5 ) 、 判断結 果に基づいて新たな予約依頼情報の有無を判断する (S 2 0 6 ) 。 判断の結果、 新たな予約依頼情報がない場合、 受付処理装置 1は予約受付処理を終了する。 一方、 新たな予約依頼情報がある場合、 受付処理装置 1はリモート側受付デー タファイル 2 3 2に保存されている予約依頼情報を取得する処理を行う (S 2 0 7〜S 2 1 5 ) 。 具体的には、 受付処理装置 1は予約依頼情報の要求メッセージ をリモートサーバ 2に送信する (S 2 0 7 ) 。 リモートサーバ 2は要求メッセ一 ジを受信後 (S 208) 、 リモート側受付データファイル 232に保存された予 約依頼情報を受付処理装置 1に送信する (S 209) 。 受付処理装置 1は予約依 頼情報を受信後、 ハードディスク 13内のメイン側受付データファイル 132に 保存する (S 210) 。 Referring to FIG. 4, this reservation reception processing (S20) is performed after a periodic communication processing in which the reception processing device 1 and the remote server 2 periodically transmit and receive information. The periodical communication processing will be described later. The reception processing device 1 determines whether or not new reservation request information is recorded in the remote-side reception data file 2 32. (S202 to S206). Here, the new reservation request information refers to the reservation request information stored in the remote-side reception data file 232 since the previous main reservation reception processing. The reception processing device 1 transmits an inquiry message as to whether or not there is new reservation request information to the remote server 2 (S202). After receiving the inquiry message (S203), the remote server 2 determines whether or not new reservation request information is stored in the remote-side reception data file 232, and transmits the determination result. (S204). After receiving the determination result from the remote server 2 (S205), the reception processing device 1 determines whether there is new reservation request information based on the determination result (S206). As a result of the determination, when there is no new reservation request information, the reception processing device 1 ends the reservation reception processing. On the other hand, if there is new reservation request information, the reception processing device 1 performs a process of acquiring the reservation request information stored in the remote-side reception data file 23 (S207 to S215). Specifically, the reception processing device 1 transmits a request message for reservation request information to the remote server 2 (S207). Remote server 2 sends request message After receiving the message (S208), the reservation request information stored in the remote-side reception data file 232 is transmitted to the reception processing device 1 (S209). After receiving the reservation request information, the reception processing device 1 stores it in the main-side reception data file 132 in the hard disk 13 (S210).
予約依頼情報を保存後、 受付処理装置 1はメイン側状況データファイル 131 に保存された最新の状況データと保存した予約依頼情報とに基づいて、 予約受付 番号計算処理 (S 21 1) 、 待ち人数計算処理 (S 212) 及び待ち時間計算処 理 (S 213) を行う。 予約受付番号計算処理では、 予約依頼の早かった予約依 頼情報順に予約受付番号を付与する (S 21 1) 。 具体的には、 状況データ内の 最新の発行済み予約受付番号を参照して、 予約依頼の早かった予約依頼情報ごと に予約受付番号を順次力ゥントァップさせて付与する。 たとえば、 ステップ S 2 10で受信した予約依頼が 3件あり、 状況データ内の最新の発行済み予約受付番 号が 「30050」 である場合、 受付処理装置 1は予約依頼の早かった予約依頼 情報ごとに 「30051」 、 「30052」 、 「30053」 の予約受付番号を 付与する。 なお、 予約受付番号は 10ずつカウントアップさせ、 「30060」 、 「30070」 、 「30080」 としてもよい。 また、 待ち人数計算処理では、 次の式 (1) により待ち人数を算出する (S 212) 。  After storing the reservation request information, the reception processing device 1 calculates a reservation reception number based on the latest status data stored in the main-side status data file 131 and the stored reservation request information (S21 1), The calculation processing (S212) and the waiting time calculation processing (S213) are performed. In the reservation reception number calculation process, the reservation reception numbers are assigned in the order of the reservation request information for which the reservation request was earlier (S211). Specifically, by referring to the latest issued reservation reception number in the situation data, the reservation reception number is sequentially assigned and assigned to each reservation request information for which the reservation request has been made earlier. For example, if there are three reservation requests received in step S210 and the latest issued reservation reception number in the status data is "30050", the reception processing device 1 sends the reservation request information , A reservation reception number of “30051”, “30052”, or “30053” is given to the user. The reservation reception number may be incremented by 10 and may be "30060", "30070", or "30080". In the waiting person calculation process, the waiting person is calculated by the following equation (1) (S212).
待ち人数 =予約受付番号一呼出番号 ( 1 )  Waiting person = reservation reception number-calling number (1)
ここで、 呼出番号とは、 診察室から呼び出しを受けた番号 (すなわち、 診察待 ちが終了した番号) である。 待ち時間計算処理では、 次の式 (2) により待ち時 間を算出する (S 213) 。  Here, the calling number is the number that has been called from the consultation room (that is, the number for which the waiting for consultation has been completed). In the waiting time calculation process, the waiting time is calculated by the following equation (2) (S213).
待ち時間 =待ち人数 X予想時間 (2)  Waiting time = number of people waiting X estimated time (2)
ここで、 予想時間は任意に決定できる時間である。 たとえば病院での診察が 1 人当たり平均 5分かかるのであれば、 予想時間 =5分とすることができる。 さら に、 時間帯によって 1人当たりの診察時間が異なる場合や、 内科や外科といった ように分野により診察時間が異なる場合は、 時間帯や分野ごとに予想時間を決定 できる。 さらに、 待ち人数が 1人〜 10人までの間は予想時間 =3分とし、 待ち 人数 11人以降については予想時間 =5分というように、 待ち人数に応じて予想 時間を変えることもできる。 なお、 ステップ S 21 1〜S 213の算出結果はメ イン側状況データファイル 131に保存される。 Here, the expected time is a time that can be determined arbitrarily. For example, if a consultation in a hospital takes an average of 5 minutes per person, the expected time = 5 minutes. In addition, when consultation time per person varies depending on the time zone, or when consultation time varies depending on the field such as internal medicine or surgery, the expected time can be determined for each time slot or field. Furthermore, the expected time can be changed according to the number of people waiting, such as setting the estimated time = 3 minutes for people waiting for 1 to 10 people, and the estimated time = 5 minutes for 11 or more people waiting. Note that the calculation results of steps S 211 to S 213 are It is stored in the in-side situation data file 131.
以上の計算処理を終了後、 受付処理装置 1はステップ S 212で算出した予約 受付番号に基づいて予約受付番号券を発券部 17から発行する (S 214) 。 ま た、 ステップ S 21 1で算出した待ち人数及びステップ S 213で算出した待ち 時間の情報を病院内の掲示ディスプレイ 15に表示する (S 215) 。 ステップ S 215における掲示ディスプレイの画面を図 5に示す。 呼出番号表示部 201 に呼出番号が、 待ち人数表示部 202に待ち人数が、 待ち時間表示部 203に待 ち時間がそれぞれ表示される。 受付処理装置 1は S 21 1〜S 215の動作を S 210で受診した予約情報数分繰り返す。  After completing the above calculation process, the reception processing device 1 issues a reservation reception number ticket from the ticket issuing unit 17 based on the reservation reception number calculated in step S212 (S214). Further, information on the number of waiting persons calculated in step S 211 and the waiting time calculated in step S 213 is displayed on the bulletin board display 15 in the hospital (S 215). FIG. 5 shows the screen of the bulletin display in step S215. The call number is displayed on the call number display section 201, the number of persons waiting on the waiting number display section 202, and the waiting time on the waiting time display section 203. The reception processing device 1 repeats the operations of S211-S215 for the number of reservation information received in S210.
以上の動作を終了後、 受付処理装置 1は S 211で算出した予約情報ごとの予 約受付番号をリモートサーバ 2に送信する (S 216) 。 なお、 予約受付番号の 送信時にメィン側状況データファイル 131に保存された状況データも送信され る。 リモートサーバ 2は予約依頼情報ごとの予約受付番号を受信後 (S 217) 、 予約受付番号を対応する予約依頼情報とリンクしてリモート側受付データフアイ ル 232に保存する (S 218) 。 なお、 待ち人数、 待ち時間及ぴ呼出番号はリ モー H則状況データファイル 231に保存される。  After finishing the above operation, the reception processing device 1 transmits the reservation reception number for each reservation information calculated in S211 to the remote server 2 (S216). It should be noted that the status data stored in the main-side status data file 131 is also transmitted when the reservation reception number is transmitted. After receiving the reservation reception number for each reservation request information (S217), the remote server 2 links the reservation reception number with the corresponding reservation request information and stores it in the remote-side reception data file 232 (S218). The number of people waiting, the waiting time, and the call number are stored in the remote H-law situation data file 231.
2-3. 予約完了問い合わせ処理  2-3. Booking completion inquiry processing
ユーザはユーザ端末 6を用いて受付処理装置 1での予約受付が完了したか否か を問い合わせできる。 図 6を参照して、 ユーザはユーザ端末 6を用いて問い合わ せメッセージをリモートサーバ 2へ送信する (S 301) 。 図 7にユーザが携帯 端末 4を用いた場合のステツプ S 301での携帯端末画面を示す。 このとき、 ュ 一ザが画面中の 「確認画面を見る」 を選択すれば、 携帯端末 4からリモートサー パ 2へ問い合わせメッセージが送信される。 リモートサーバ 2は問い合わせメッ セージを受信後 (S 302) 、 予約受付が受付処理装置 1で完了したか否かを判 断する (S 303) 。 具体的には、 リモートサーバ 2はユーザ端末 6を特定する 情報 (たとえば電話番号や予めリモートサーバ 2から付与される識別番号等) か らリモート側受付データファイル 232内のユーザの予約依頼情報を参照し、 そ の予約依頼情報が受付処理装置 1から付与された予約受付番号を有する力否かを 判断する。 判断の結果、 予約受付番号を有しない場合、 リモートサーバ 2は予約 受付が未完了である旨の通知 (未完了通知) をユーザ端末 6に送信する (S 3 0The user can use the user terminal 6 to inquire whether or not the reservation reception by the reception processing device 1 has been completed. Referring to FIG. 6, the user sends an inquiry message to remote server 2 using user terminal 6 (S301). FIG. 7 shows the mobile terminal screen in step S301 when the user uses the mobile terminal 4. At this time, if the user selects “see the confirmation screen” on the screen, an inquiry message is transmitted from the mobile terminal 4 to the remote server 2. After receiving the inquiry message (S302), the remote server 2 determines whether or not the reservation reception has been completed by the reception processing device 1 (S303). Specifically, the remote server 2 refers to the user's reservation request information in the remote-side reception data file 232 from information (for example, a telephone number or an identification number previously assigned from the remote server 2) that specifies the user terminal 6. Then, it is determined whether or not the reservation request information has the reservation reception number assigned from the reception processing device 1. If it is determined that the reservation server does not have a reservation reception number, the remote server 2 reserves A notification that the reception has not been completed (incomplete notification) is transmitted to the user terminal 6 (S30)
4 ) 。 ユーザ端末 6は未完了通知を受信後、 ディスプレイに表示する (S 3 0Four ) . After receiving the incomplete notification, the user terminal 6 displays it on the display (S30)
5 ) 。 Five ) .
一方、 ステップ S 3 0 3での判断の結果、 予約受付番号を有している場合、 リ モートサーバ 2はユーザ端末 6に対して、 付与された予約受付番号とリモート側 状況データファイル 2 3 1内の状況データとを送信する (S 3 0 4 ) 。 ユーザ端 末 6は予約受付番号と状況データとを受信後、 予約受付番号と状況データとをデ イスプレイに表示する (S 3 0 5 ) 。 このときの携帯端末 4の画面を図 8に示す。 以上の動作により、 ユーザは病院に行くことなく、 病院外から診察の予約を行 うことができる。  On the other hand, as a result of the judgment in step S303, if the remote server 2 has the reservation reception number, the remote server 2 sends the reservation reception number and the remote-side status data file 2 3 1 to the user terminal 6. The status data and the status data are transmitted (S304). After receiving the reservation reception number and the status data, the user terminal 6 displays the reservation reception number and the status data on the display (S305). FIG. 8 shows the screen of the portable terminal 4 at this time. With the above operation, the user can make an appointment for a medical examination from outside the hospital without going to the hospital.
3 . 定期通信処理  3. Periodic communication processing
受付処理装置 1とリモートサーバ 2とは所定期間ごとに情報を授受する定期通 信処理を行う。 定期通信処理を行うことで、 メイン側状況データファイル 1 3 1 內の情報とリモート側状況データファイル 2 3 1内の状況データとを同期させる。 図 9に定期通信処理の動作を示す。 なお、 図 9中の受付処理装置 1側での定期通 信処理動作を定期通信処理 S 4 1、 リモートサーバ 2側での定期通信処理動作を 定期通信処理 S 4 2とする。  The reception processing device 1 and the remote server 2 perform a periodic communication process for exchanging information at predetermined intervals. By performing the periodic communication process, the information in the main-side status data file 13 1 內 is synchronized with the status data in the remote-side status data file 2 3 1. Figure 9 shows the operation of the periodic communication process. In FIG. 9, the periodical communication processing operation on the reception processing device 1 side is periodical communication processing S41, and the periodical communication processing operation on the remote server 2 side is periodic communication processing S42.
図 9を参照して、 受付処理装置 1は定期通信処理として初めにオンラインフラ グがオンか否かを判断する (S 4 .0 1 ) 。 オンラインフラグは、 予約受付システ ム 1 0が正常に動作している場合は 「オン」 となり、 何らかの異常により予約受 付システム 1 0が正常に動作していない場合は 「オフ」 となる。 オンラインフラ グはハードディスク 1 3内に記憶されている。 オンラインフラグが 「オフ」 の場 合 (S 4 0 1 ) 、 定期通信処理は一端終了し、 所定期間経過後に (S 4 1 5 ) 再 びステップ S 4 0 1に戻る。 一方、 オンラインフラグが 「オン」 の場合、 受付処 理装置 1は定期通信の準備を行う (S 4 0 2 ) 。 具体的には前回の定期通信処理 後に更新された状況データ (以下、 更新データと称する) をメイン側状況データ ファイル 1 3 1から検索する。 検索された更新データは送信可能なデータフォー マツトに変換される。  Referring to FIG. 9, the reception processing device 1 first determines whether or not the online flag is ON as a periodic communication process (S4.01). The online flag is “ON” when the reservation reception system 10 is operating normally, and is “OFF” when the reservation reception system 10 is not operating normally due to some abnormality. The online flag is stored in the hard disk 13. When the online flag is “OFF” (S401), the periodic communication processing is temporarily terminated, and after a predetermined period has elapsed (S415), the process returns to step S401 again. On the other hand, when the online flag is “ON”, the reception processing device 1 prepares for periodic communication (S402). Specifically, status data updated after the previous periodic communication process (hereinafter referred to as update data) is retrieved from the main-side status data file 13 1. The searched update data is converted into a transmittable data format.
定期通信準備を終了後、 受付処理装置 1は更新データを含む定期通信メッセー ジをリモートサーバ 2に送信する (S 403) 。 リモートサーバ 2は定期通信メ ッセージを受信後 (S 404) 、 受信したメッセージが有効か否かを判断する (S 405) 。 メッセージの有効性を判断する 1つの理由は、 更新データのデー タ落ちゃ更新データの文字化け等がないかチェックするためである。 また、 他の 理由は、 送信されたメッセージが受付処理装置 1から送信されたものか否かをチ エックすることで、 不正アクセスを防止するためである。 After completing the preparation for the periodic communication, the reception processing device 1 transmits the periodic communication message including the update data. The message is sent to the remote server 2 (S403). After receiving the periodic communication message (S404), the remote server 2 determines whether the received message is valid (S405). One reason for judging the validity of a message is to check for missing data in the updated data and for garbled characters in the updated data. Another reason is to prevent unauthorized access by checking whether the transmitted message is transmitted from the reception processing device 1 or not.
判断の結果、 メッセージが有効である場合 (S405) 、 リモートサーバ 2は ステータスを 「OK」 とし (S 406) 、 受信した更新データをリモート側状況 データファイル 231に保存する (S 407) 。 このとき、 更新日時も保存され る。 一方、 判断の結果、 メッセージが無効である場合 (S 405) 、 リモートサ ーバ 2はステータスを 「NG」 とする (S 408) 。 なお、 ステータスはハード ディスク 23内に記録される。 ステータスを決定後、 リモートサーバ 2は応答メ ッセージを受付処理装置 1に送信する (S 409) 。 なお、 応答メッセージには ステータス情報が含まれる。  If the result of the determination is that the message is valid (S405), the remote server 2 sets the status to "OK" (S406), and stores the received update data in the remote-side status data file 231 (S407). At this time, the update date and time are also saved. On the other hand, if the result of the determination is that the message is invalid (S405), the remote server 2 sets the status to "NG" (S408). The status is recorded in the hard disk 23. After determining the status, the remote server 2 sends a response message to the reception processing device 1 (S409). The response message contains status information.
受付処理装置 1はステップ S 403でメッセージを送信後、 リモートサーバ 2 からの応答メッセージを所定期間待つ (S 410) 。 所定期間を経過しても応答 メッセージがない場合 (S 41 1) 、 受付処理装置 1は、 電気通信回線 3又はリ モートサーパ 2になんらかの異常が発生していると判断し、 エラー通知を掲示デ イスプレイ 15に表示する (S413) 。 なお、 エラー通知は音又は音声により 行われてもよい。 その後、 受付処理装置 1はオンラインフラグを 「オフ」 とする (S 414) 。 なお、 オンラインフラグを 「オフ」 とする作業は手動で行つても 良い。 オンラインフラグを 「オフ」 とすることで、 受付処理装置 1は電気通信回 線 3から完全に独立し、 後述するように病院内にて予約受付処理を単独で行うこ とができる。  After transmitting the message in step S403, the reception processing device 1 waits for a response message from the remote server 2 for a predetermined period (S410). If there is no response message even after the lapse of a predetermined period (S411), the reception processing device 1 determines that some abnormality has occurred in the telecommunication line 3 or the remote server 2 and displays an error notification on the display. It is displayed on 15 (S413). The error notification may be made by sound or voice. Thereafter, the reception processing device 1 sets the online flag to “off” (S414). The work of setting the online flag to “off” may be performed manually. By setting the online flag to “OFF”, the reception processing device 1 is completely independent of the telecommunication line 3, and can independently perform the reservation reception processing in the hospital as described later.
—方、 所定期間内に応答メッセージを受けた場合 (S 411) 、 受信した応答 メッセージに含まれるステータスが OKか否かを判断する (S 412) 。 判断の 結果、 ステータスが OKの場合、 図 4に示した本予約受付処理 S 20を行う。 ス テツプ S 412での判断の結果、 ステータスが NGの場合、 電気通信回線 3又は リモートサーバ 2でトラブルが発生していると判断し、 エラー通知を掲示ディス プレイ 1 5に表示する (S 4 1 3 ) 。 このとき、 オンラインフラグは自動又は手 動により 「オフ」 とする (S 4 1 4 ) 。 On the other hand, if a response message is received within a predetermined period (S411), it is determined whether the status included in the received response message is OK (S412). If the result of the determination is that the status is OK, the real reservation reception processing S20 shown in FIG. 4 is performed. If the result of the determination in step S412 is NG, it is determined that a trouble has occurred in the telecommunication line 3 or the remote server 2, and an error notification is displayed. Display on play 15 (S4 13). At this time, the online flag is automatically or manually turned off (S414).
以上の動作により、 本発明の実施の形態による予約受付システムでは、 受付処 理装置 1及ぴリモートサーパ 2の 2つのサーバを用いて定期通信処理を行う。 そ のため、 電気通信回線 3又はリモートサーバ 2になんらかのトラブルが発生して も、 受付処理装置 1は単独で予約受付処理を行うことができる。 よって、 トラブ ル発生時も予約受付システム 1 0を稼働させ続けることができ、 システム全体は 停止しない。 また、 定期通信処理では、 定期通信メッセージは必ず受付処理装置 1からリモートサーバ 2へ送信され、 その逆はない。 すなわち、 受付処理装置 1 は自分が定期通信メッセージを送信し、 応答してきたリモートサーバ 2以外とは 情報の送受信を行わない。 よって、 受付処理装置 1のセキュリティを極めて高く することができる。  With the above operation, in the reservation reception system according to the embodiment of the present invention, the periodic communication processing is performed using the two servers, the reception processing device 1 and the remote server 2. Therefore, even if any trouble occurs in the telecommunication line 3 or the remote server 2, the reception processing device 1 can perform the reservation reception processing independently. Therefore, even when a trouble occurs, the reservation receiving system 10 can be kept operating, and the entire system does not stop. In the regular communication process, the regular communication message is always transmitted from the reception processing device 1 to the remote server 2, and not vice versa. That is, the reception processing device 1 itself transmits a periodic communication message, and does not transmit / receive information to / from other than the remote server 2 which has responded. Therefore, the security of the reception processing device 1 can be extremely increased.
4 . 呼出状況通知処理  4. Call status notification processing
遠隔予約受付処理により受付処理装置 1で予約受付を完了し、 予約受付番号を 付与されたユーザは、 自分の予約受付番号が呼ばれるまでの待ち人数及ぴ待ち時 間等の情報 (呼出状況データ) の通知を受けることができる (呼出状況通知処 理) 。 図 1 0を参照して、 ユーザはユーザ端末 6に予約受付番号を入力し、 ユー ザ端末 6は入力された予約受付番号を含む問い合わせメッセージをリモートサー バ 2に送信する (S 5 0 1 ) 。 ステップ S 5 0 1で携帯端末 4を用いた場合の予 約受付番号入力画面を図 1 1に示す。 リモートサーバ 2は問い合わせメッセージ を受信後 ( S 5 0 2 ) 、 受信前の所定期間内に定期通信処理がなされたか否かを 判断する (S 5 0 3 ) 。 定期通信処理がなされたか否かの判断は、 リモート側状 況データファイル 2 3 1内の更新日時記録を参照して行う。  The user who has completed the reservation reception by the reception processing device 1 by the remote reservation reception processing and has been given the reservation reception number can receive information (call status data) such as the number of people waiting and the waiting time until his / her reservation reception number is called. Notification (call status notification processing). Referring to FIG. 10, the user inputs a reservation reception number to user terminal 6, and user terminal 6 transmits an inquiry message including the input reservation reception number to remote server 2 (S501). . FIG. 11 shows a reservation reception number input screen when the mobile terminal 4 is used in step S501. After receiving the inquiry message (S502), the remote server 2 determines whether or not the regular communication processing has been performed within a predetermined period before the reception (S503). The determination as to whether or not the regular communication process has been performed is made by referring to the update date and time record in the remote-side status data file 23 1.
判断の結果、 定期通信処理がなされていない場合 (S 5 0 3 ) 、 電気通信回線 3又は受付処理装置 1に異常が発生していると判断する。 このときリモートサー バ 2はエラー通知をユーザ端末 6に送信する (S 5 0 4 ) 。 一方、 定期通信処理 がなされている場合、 リモートサーバ 2は予約受付システム 1 0が正常に動作し ていると判断する。 このとき、 リモートサーバ 2はリモート側状況データフアイ ル 2 3 1内の状況データを用いて呼出状況データの算出を行う。 具体的には、 ス テツプ S 5 0 2で受信した予約受付番号が呼出されるまでの待ち人数と、 待ち時 間とを予約受付番号及び式 (1 ) , (2 ) を用いて算出する。 算出結果は呼出状 況データとしてユーザ端末 6に送信される (S 5 0 5 ) 。 ユーザ端末 6は呼出状 況データを受信後、 ディスプレイに表示する (S 5 0 6 ) 。 携帯端末 4を用いた 場合のステップ S 5 0 6の画面を図 1 2に示す。 If the result of the determination is that the periodic communication processing has not been performed (S503), it is determined that an abnormality has occurred in the telecommunication line 3 or the reception processing device 1. At this time, the remote server 2 sends an error notification to the user terminal 6 (S504). On the other hand, when the regular communication process is performed, the remote server 2 determines that the reservation receiving system 10 is operating normally. At this time, the remote server 2 calculates call status data using the status data in the remote-side status data file 231. Specifically, The number of people waiting until the reservation reception number received in step S502 is called and the waiting time are calculated using the reservation reception number and the formulas (1) and (2). The calculation result is transmitted to the user terminal 6 as call status data (S505). After receiving the call status data, the user terminal 6 displays it on the display (S506). FIG. 12 shows the screen of step S506 when the mobile terminal 4 is used.
以上の動作により、 ユーザは病院外にいる場合でも、 自分の予約受付番号が呼 ぴ出されるまでの待ち人数や待ち時間等の情報を把握できる。 そのため、 ユーザ は病院で呼び出される直前まで病院内にいる必要はなく、 呼び出されるまでの時 間を有効に利用できる。  By the above operation, even when the user is outside the hospital, the user can grasp information such as the number of people waiting and the waiting time until his / her reservation reception number is called. Therefore, the user does not need to be in the hospital immediately before being called at the hospital, and can use the time until the call is effectively used.
なお、 ユーザが携帯端末 4を利用している場合、 呼び出される所定時間前に音 振動、 又は表示により呼出時間が近い旨の通知をユーザが受けるようにすること もできる。  When the user uses the mobile terminal 4, the user may be notified by sound, vibration or display that the calling time is approaching before a predetermined time before being called.
図 1 3を参照して、 携帯端末 4のユーザは初めに予約受付番号と呼出条件とを 携帯端末 4に入力する (S 6 0 1 ) 。 ここで、 呼出条件とは、 たとえば待ち時間 が 3 0分未満となつた場合に通知を行う、 又は待ち人数が 1 0人よりも少なくな つた場合に通知を行う、 といった条件をいう。 予約受付番号及び呼出条件が入力 された後、 携帯端末 4は現在サービス圏内か否かを判断する (S 6 0 2 ) 。 サー ビス圏外の場合、 携帯端末 4は警告音や振動により、 又は、 ディスプレイに警告 表示を行うことにより、 ユーザに注意を促す (S 6 0 3 ) 。 その後、 所定期間経 過後に (S 6 0 4 ) 再ぴステップ S 6 0 2の動作に戻る。  Referring to FIG. 13, the user of portable terminal 4 first inputs a reservation reception number and a calling condition to portable terminal 4 (S601). Here, the calling condition refers to a condition that, for example, a notification is made when the waiting time is less than 30 minutes, or a notification is made when the number of waiting people is less than 10 people. After the reservation reception number and the calling conditions are input, the mobile terminal 4 determines whether or not the mobile terminal 4 is currently within the service area (S602). When the mobile terminal 4 is out of the service area, the portable terminal 4 calls the user's attention by a warning sound or vibration, or by displaying a warning on a display (S603). Thereafter, after a lapse of a predetermined period (S604), the operation returns to the operation of the re-start step S602.
一方、 サービス圏内の場合、 携帯端末 4は入力された予約受付番号を含む問い 合わせメッセージをリモートサーバ 2に送信する ( S 6 2 0 ) 。 続いて、 リモー トサーバは図 1 0における呼出状況通知処理中のステップ S 5 0 2〜S 5 0 5の 動作を行い、 エラー通知又は算出した呼出状況データを携帯端末 4に送信する。 携帯端末 4はエラー通知又は呼出状況データを受信する (S 6 0 5 ) 。  On the other hand, in the service area, the mobile terminal 4 transmits an inquiry message including the input reservation reception number to the remote server 2 (S620). Subsequently, the remote server performs the operation of steps S502 to S505 during the call status notification processing in FIG. 10 and transmits an error notification or the calculated call status data to the portable terminal 4. The mobile terminal 4 receives the error notification or the call status data (S605).
受信後、 携帯端末 4は受信した情報に基づいて予約受付システム 1 0が正常に 動作している力否かを判断する (S 6 0 6 ) 。 予約受付システムが停止している 場合 (すなわち、 ステップ S 6 0 5でエラー通知を受信した場合) 、 携帯端末 4 はエラー通知をディスプレイに表示したり、 警告音を発したりしてユーザの注意 を促す (S 6 0 7 ) 。 一方、 予約受付システムが正常に動作している場合 (すな わち、 ステップ S 6 0 5で呼出状況データを受信した場合) 、 携帯端末 4は呼出 状況データ及ぴステップ S 6 0 1で入力した呼出条件に基づいて、 ユーザに通知 を行うか否かを判断する (S 6 0 8 ) 。 具体的には、 携帯端末 4は呼出状況デー タ中の待ち時間が 3 0分未満か否かを判断する。 又は、 携帯端末 4は呼出状況デ ータ中の待ち人数が 1 0人未満か否かを判断する。 After the reception, the mobile terminal 4 determines whether or not the reservation receiving system 10 is operating normally based on the received information (S606). When the reservation reception system is stopped (that is, when an error notification is received in step S605), the mobile terminal 4 displays an error notification on the display or emits a warning sound to alert the user. (S607). On the other hand, when the reservation accepting system is operating normally (that is, when the call status data is received in step S605), the mobile terminal 4 inputs the call status data and the input in step S601. It is determined whether or not to notify the user based on the called calling condition (S608). Specifically, the mobile terminal 4 determines whether the waiting time in the call status data is less than 30 minutes. Alternatively, the mobile terminal 4 determines whether the number of waiting persons in the call status data is less than 10 persons.
判断の結果、 呼出状況データが呼出条件を満足していない場合、 所定時間経過 後 (S 6 0 4 ) に再びステップ S 6 0 2の動作に戻る。 一方、 呼出状況データが 呼出条件を満足している場合、 携帯端末 4は呼出時間が近づいた旨の通知を行う ( S 6 0 9 ) 。 通知は音や振動により、 又はディスプレイへの画面表示により行 われる。  If the call status data does not satisfy the call conditions as a result of the determination, the operation returns to step S602 again after a predetermined time (S604). On the other hand, if the call status data satisfies the call conditions, the portable terminal 4 notifies that the call time is approaching (S609). Notification is made by sound or vibration or by screen display on the display.
続いて、 携帯端末 4は所定期間経過後 (S 6 1 0 ) 、 キー操作が行われた力否 かを判断する ( S 6 1 1 ) 。 ここで、 キー操作とは、 ステップ S 6 0 9の通知を 停止させるためのキー操作であり、 たとえば携帯端末 4内の複数のポタン (図示 せず) 内のいずれかを押せばキー操作が行われたことになる。 キー操作が行われ た場合 ( S 6 1 1 ) 、 ユーザが通知を認識したため、 携帯端末 4は動作を終了す る。 一方、 キー操作が行われなかった場合 (S 6 1 1 ) 、 携帯端末 4は所定時間 経過後 (S 6 0 4 ) 、 再ぴステップ S 6 0 2に戻る。 ユーザが通知を認識してい ないため、 再ぴ通知を行う必要があるためである。 なお、 ステップ S 6 0 4の所 定時間は、 ユーザの予約受付番号の呼出時間が近づくにつれて、 短くなつてもよ い。 たとえば、 待ち時間が 1 0分以上の場合、 ステップ S 6 0 4の所定時間が 3 分であり、 待ち時間が 1 0分未満の場合、 所定時間が 1分となってもよい。 以上の動作により、 ユーザは携帯端末 4に一度呼出条件を入力しておけば、 自 己の予約受付番号の呼出が近づいたときに自動的に音声又は画面表示により通知 を受ける。 そのため、 病院外にいたため呼出時に間に合わなかったといった事態 を未然に防ぐことができる。  Subsequently, after a lapse of a predetermined period (S610), the mobile terminal 4 determines whether or not the key operation has been performed (S611). Here, the key operation is a key operation for stopping the notification in step S609, and the key operation is performed by pressing any of a plurality of buttons (not shown) in the mobile terminal 4, for example. It has been done. When the key operation is performed (S611), the user recognizes the notification, and the portable terminal 4 ends the operation. On the other hand, if no key operation has been performed (S611), the portable terminal 4 returns to the playback step S602 after a predetermined time has elapsed (S640). This is because the user has not recognized the notification and needs to perform the re-notification. The predetermined time in step S604 may be shorter as the calling time of the user's reservation reception number approaches. For example, if the waiting time is 10 minutes or more, the predetermined time in step S604 may be 3 minutes, and if the waiting time is less than 10 minutes, the predetermined time may be 1 minute. By the above operation, once the user inputs the calling conditions into the portable terminal 4, the user is automatically notified by voice or screen display when the calling of his / her reservation reception number approaches. Therefore, it is possible to prevent a situation in which the patient was outside the hospital and was unable to make the call in time.
5 . 予約状況通知処理  5. Reservation status notification processing
ユーザはユーザ端末 6を用いて病院の予約状況を把握することもできる。 図 1 4を参照して、 ユーザはユーザ端末 6を用いて、 予約状況の問い合わせメッセ一 ジを送信する (S 7 0 1 ) 。 リモートサーバ 2は問い合わせメッセージを受信後 ( S 7 0 2 ) 、 受信前の所定期間内に定期通信処理を行ったか否かを判断する ( S 7 0 3 ) 。 定期通信処理が行われていない場合、 リモートサーバ 2はユーザ 端末 6へエラー通知を行う (S 7 0 4 ) 。 このとき、 ユーザ端末 6はエラー通知 を受け、 ディスプレイに表示する (S 7 0 6 ) 。 一方、 定期通信処理が行われて いた場合、 リモートサーバ 2はリモート側状況データファイル 2 3 1内の状況デ ータをユーザ端末 6に送信する (S 7 0 5 ) 。 ここで、 状況データは待ち人数、 待ち時間、 現在呼出されている予約受付番号等を含む。 ユーザ端末 6は状況デー タを受信後、 ディスプレイに表示する (S 7 0 6 ) 。 ステップ S 7 0 6でのユー ザ端末 6のディスプレイ画面を図 1 5に示す。 The user can use the user terminal 6 to grasp the reservation status of the hospital. Referring to FIG. 14, the user uses user terminal 6 to send a reservation status inquiry message. The message is transmitted (S701). After receiving the inquiry message (S702), the remote server 2 determines whether or not the regular communication processing has been performed within a predetermined period before the reception (S703). If the periodic communication processing is not being performed, the remote server 2 notifies the user terminal 6 of an error (S704). At this time, the user terminal 6 receives the error notification and displays it on the display (S706). On the other hand, if the regular communication processing has been performed, the remote server 2 transmits the status data in the remote-side status data file 231 to the user terminal 6 (S705). Here, the status data includes the number of people waiting, the waiting time, the reservation reception number currently being called, and the like. After receiving the status data, the user terminal 6 displays it on the display (S706). FIG. 15 shows the display screen of the user terminal 6 in step S706.
以上の動作により、 ユーザは病院に行くことなく在宅又は外出時に病院の予約 状況を把握することができ、 予約を行うか否かを判断するときの有効な情報を取 得できる。  By the above operation, the user can grasp the reservation status of the hospital at home or out of the office without going to the hospital, and can obtain effective information for determining whether or not to make a reservation.
6 . 統計情報通知処理  6. Statistical information notification processing
予約状況通知処理では、 ユーザが問い合わせをした時点での病院の状況データ を見ることができたが、 病院の混雑具合をもっと大局的に見たい場合もある。 こ のような場合、 ユーザは統計情報を参照することで、 病院の 1週間単位又は 1ケ 月単位での混雑具合を把握できる。 図 1 6を参照して、 リモートサーバ 2は所定 期間ごと (たとえば 1時間ごと ) の状況データをリモート側状況データファイル 2 3 1から統計データファイル 2 3 3に保存する ( S 1 2 0 1 ) 。 このとき、 所 定時間ごとの状況データは統計データとして保存される。 所定期間ごとにデータ を取得するのは混雑状況を時間単位で統計することが最も混雑状況を理解しやす いからである。 ただし、 統計データファイル 2 3 3への保存条件は時間以外の条 件を設定してもよい。  In the reservation status notification process, we could see the status data of the hospital at the time of the user's inquiry, but sometimes we want to see the congestion of the hospital more broadly. In such a case, the user can grasp the degree of congestion in the hospital on a weekly or monthly basis by referring to the statistical information. Referring to FIG. 16, the remote server 2 saves status data for each predetermined period (for example, every hour) from the remote-side status data file 2 3 1 to the statistical data file 2 3 3 (S 1 201) . At this time, the status data for each specified time is saved as statistical data. Data is acquired every predetermined period because it is easiest to understand the congestion status by statistically analyzing the congestion status on an hourly basis. However, conditions other than time may be set as the storage conditions for the statistical data file 233.
ユーザはユーザ端末 6を用いて統計データの要求メッセージをリモートサーバ The user sends a request message for statistical data to the remote server using the user terminal 6.
2に送信する (S 1 2 0 2 ) 。 リモートサーバ 2は要求メッセージの受信後 (S 1 2 0 3 ) 、 統計データファイル 2 3 3に保存してある統計データをユーザ端末 6に送信する (S 1 2 0 4 ) 。 このとき、 統計内容を理解しやすいように、 統計 データをグラフ化して送信してもよい。 ユーザ端末 6は送信された統計データを 受信後、 ディスプレイに表示する (S 1 2 0 5 ) 。 2 is transmitted to (S122). After receiving the request message (S1203), the remote server 2 sends the statistical data stored in the statistical data file 233 to the user terminal 6 (S1204). At this time, the statistical data may be sent as a graph so that the contents of the statistical data can be easily understood. The user terminal 6 sends the transmitted statistical data After receiving, it is displayed on the display (S125).
以上の動作により、 ユーザは所定期間ごとの混雑状況を把握できる。 よって、 統計データを参照することで、 病院の予約受付を行うときの参考にすることがで 含る。  With the above operation, the user can grasp the congestion state for each predetermined period. Therefore, by referring to the statistical data, it can be used as a reference when accepting reservations for hospitals.
7 . 単独予約受付処理  7. Single reservation reception processing
以上に示した処理は受付処理装置 1とリモートサーパ 2との間で情報を送受信 することにより予約受付を行っていた。 しかしながら、 先述したとおり、 受付処 理装置 1が独立して予約受付処理を行うこともできる。 以下、 受付処理装置 1単 独での予約受付処理及ぴ呼出処理 (単独予約受付処理) について説明する。 単独 予約受付処理は発券処理と呼出処理と呼出スキップ処理とを含む。  In the processing described above, reservation reception is performed by transmitting and receiving information between the reception processing device 1 and the remote server 2. However, as described above, the reception processing device 1 can independently perform the reservation reception processing. Hereinafter, the reservation reception processing and the call processing (individual reservation reception processing) by the reception processing device 1 alone will be described. The single reservation accepting process includes a ticket issuing process, a calling process, and a call skipping process.
7 - 1 . 発券処理  7-1. Ticketing process
図 1 7を参照して、 ユーザからの求めに応じて、 病院の受付担当者は受付処理 装置 1の入力部 1 6を用いて発券操作を行う (S 8 0 1 ) 。 たとえば、 受付担当 者は病院に診察を受けに来た患者から診察券等を受け取った後、 受付処理装置 1 に発券依頼を入力する。 入力が終了後、 受付処理装置 1はユーザに付与すべき予 約受付番号を算出する (S 8 0 2 ) 。 予約受付番号は受付順に番号をカウントさ れるが、 1ずつカウントされてもよいし、 1 0ずつカウントされてもよい。 ただ し、 たとえば予約受付番号の上位複数桁は業務 (内科や外科等) の区分として使 用することもでき、 また上位数桁を日付に割り当てることもできる。  Referring to FIG. 17, in response to a request from the user, the receptionist of the hospital performs a ticketing operation using the input unit 16 of the reception processing device 1 (S801). For example, the receptionist receives a consultation ticket or the like from a patient who has come to the hospital for consultation, and then inputs a ticketing request to the reception processing device 1. After the input is completed, the reception processing device 1 calculates a reservation reception number to be given to the user (S802). The reservation reception numbers are counted in the order of reception, but may be counted one by one or ten. However, for example, the higher-order digits of the reservation receipt number can be used as a division of business (medical, surgical, etc.), and the upper-order digits can be assigned to dates.
予約受付番号の算出後、 受付処理装置 1は待ち人数算出処理を行う (S 8 0 3 ) 。 待ち人数は式ひ)により算出される。 続いて、 受付処理装置 1は待ち時間 算出処理を行う (S 8 0 4 ) 。 待ち時間は、 式 (2 ) で算出される。 以上の計算 を終了後、 受付処理装置 1は予約受付番号券を発券部 1 7より発券する ( S 8 0 5 ) 。 続いて、 受付処理装置 1は待ち人数及ぴ待ち時間を掲示ディスプレイ 1 5 に表示する (S 8 0 6 ) 。 なお、 ステップ S 8 0 2〜S 8 0 4での算出結果はメ イン側状況データファイル 1 3 1に保存され、 ステップ S 8 0 6以降に行われる 定期通信処理 (S 4 1, S 4 2 ) にて状況データとしてリモートサーバ 2に送信 される。 定期通信処理は図 9の動作と同じである。  After calculating the reservation reception number, the reception processing device 1 performs a waiting person calculation process (S803). The number of waiting persons is calculated by equation (1). Subsequently, the reception processing device 1 performs a waiting time calculation process (S804). The waiting time is calculated by equation (2). After completing the above calculation, the reception processing device 1 issues a reservation reception number ticket from the ticket issuing unit 17 (S805). Subsequently, the reception processing device 1 displays the number of people waiting and the waiting time on the notice display 15 (S806). Note that the calculation results in steps S802 to S804 are stored in the main-side status data file 131, and the periodic communication processing (S41, S42) performed after step S806 is performed. ) Is sent to the remote server 2 as status data. The periodic communication process is the same as the operation in FIG.
7 - 2 . 呼出処理 図 18を参照して、 病院内の各診察室での診断が終了した場合、 その診察室の 担当医又は担当看護士等は診察が終了した旨を受付処理装置 1の入力部 16を用 いて入力する (S 901) 。 このとき、 受付処理装置 1は呼出番号算出処理を行 う (S 902) 。 具体的には、 呼び出しの対象となった予約受付番号を 1カウン ト増加する (S 902) 。 続いて、 受付処理装置 1は待ち人数算出処理 (S 90 3) 及び待ち時間算出処理 (S 904) を行う。 待ち人数算出処理では、 受付処 理装置 1は式 ( 1 ) を用いてメイン側状況データファイル 131に保存された待 ち人数から 1人分差し引く。 また、 待ち時間算出処理ではステップ S 903で更 新した待ち人数に基づいて式 (2) より待ち時間を算出する。 なお、 ステップ S 902〜S 904の算出結果はメイン側状況データファイル 131に保存される。 以上の動作を終了後、 受付処理装置 1は呼出音又は呼出音声を発し (S 90 5) 、 掲示ディスプレイにステップ S 902で算出した呼出番号を表示する (S 906) 。 以降、 受付処理装置 1とリモートサーバ 2との間で定期通信処理 (S 41, S 42) が行われる。 7-2. Call processing Referring to FIG. 18, when the diagnosis in each consultation room in the hospital is completed, the doctor or nurse in charge of the consultation room informs that the consultation has been completed using the input unit 16 of the reception processing device 1. Enter it (S901). At this time, the reception processing device 1 performs a call number calculation process (S902). Specifically, the reservation reception number for which the call was made is increased by one (S902). Subsequently, the reception processing device 1 performs a waiting person calculation process (S903) and a waiting time calculation process (S904). In the waiting person calculation process, the reception processing device 1 subtracts one waiting person from the waiting person stored in the main-side situation data file 131 using the equation (1). In the waiting time calculation process, the waiting time is calculated from equation (2) based on the number of waiting people updated in step S903. The calculation results of steps S902 to S904 are stored in the main-side situation data file 131. After the above operation is completed, the reception processing device 1 emits a ringing sound or a calling voice (S905), and displays the call number calculated in step S902 on the bulletin board display (S906). Thereafter, periodic communication processing (S41, S42) is performed between the reception processing device 1 and the remote server 2.
7-3. 呼出スキップ処理  7-3. Call skip processing
呼出を行っても診察室に患者が現れない場合、 その患者が不在とみなして患者 の予約受付番号をスキップ処理できる。 図 19を参照して、 診察室の担当医又は 担当看護士が受付処理装置 1の入力部 16を用いてスキップを指示する (S 10 01) 。 このとき、 メイン側状況データファイル 131内の不在者テーブルにス キップされた予約受付番号 (スキップデータ) が記録され (S 1002) 、 受付 処理装置 1の掲示ディスプレイ 15にはスキップデータが表示される。 図 20に ステップ S 1003における掲示ディスプレイの画面を示す。 スキップされた予 約受付番号を表示することで、 患者がスキップされたか否かが容易にわかるため である。  If the patient does not appear in the consultation room after the call, the patient can be regarded as absent and the reservation number of the patient can be skipped. Referring to FIG. 19, the doctor or nurse in charge in the examination room instructs to skip using the input unit 16 of the reception processing device 1 (S1001). At this time, the skipped reservation reception number (skip data) is recorded in the absentee table in the main-side status data file 131 (S1002), and the skip data is displayed on the notice display 15 of the reception processing device 1. . FIG. 20 shows the screen of the bulletin display in step S1003. By displaying the skipped reservation number, it is easy to determine whether the patient was skipped.
続いて、 受付処理装置 1はスキップした予約受付番号の数 (スキップ数) を力 ゥントする (S 1004) 。 スキップ数を算出後、 受付処理装置 1は図 18にお けるステップ S 902〜S 906の動作 (呼出処理) を行う。 呼出処理終了後、 受付処理装置 1は定期通信処理を行う。 定期通信処理で送信する状況データには、 スキップ数を含んでもよい。 なお、 スキップされた予約受付番号の患者が所定期間内に現れなかつた場合、 や、 スキップされた予約受付番号の患者が所定期間内に現れた場合、 受付作業者 は該当する予約受付番号を消去できる。 図 2 1を参照して、 受付作業者が受付処 理装置 1の入力部 1 6を用いて所定時間内に現れなかった患者の予約受付番号を 削除する (S 1 1 0 1 ) 。 又は、 所定時間内に現れて診察を行った患者の予約受 付番号を削除する (S 1 1 0 2 ) 。 このとき、 受付処理装置 1内の不在者テープ ル内の該当する予約受付番号が削除され、 その結果、 スキップデータは更新され る (S 1 1 0 3 ) 。 更新されたスキップデータは掲示ディスプレイ 1 5に表示さ れる (S 1 1 0 4 ) 。 このとき受付処理装置 1はスキップ数についても更新する ( S 1 1 0 5 ) 。 その後、 受付処理装置 1は定期通信処理 (S 4 1, S 4 2 ) を 行う。 Subsequently, the reception processing device 1 counts the number of skipped reservation reception numbers (the number of skips) (S1004). After calculating the number of skips, the reception processing device 1 performs the operation (call processing) of steps S902 to S906 in FIG. After the end of the calling process, the reception processing device 1 performs a periodic communication process. The status data transmitted in the periodic communication process may include the skip number. If the patient with the skipped reservation number does not appear within the predetermined period, or if the patient with the skipped reservation number appears within the predetermined period, the reception worker erases the corresponding reservation number. it can. Referring to FIG. 21, the reception worker uses the input unit 16 of the reception processing device 1 to delete the reservation reception number of the patient who has not appeared within a predetermined time (S1101). Alternatively, the appointment receipt number of the patient who has appeared within the predetermined time period and has undergone a medical examination is deleted (S111). At this time, the corresponding reservation reception number in the absentee table in the reception processing device 1 is deleted, and as a result, the skip data is updated (S1103). The updated skip data is displayed on the bulletin board display 15 (S1104). At this time, the reception processing device 1 also updates the skip number (S111). After that, the reception processing device 1 performs a periodic communication process (S41, S42).
以上の動作により、 受付処理装置 1単独でも予約受付処理ができる。 よって、 ユーザ端末 6を利用しない患者に対しても、 予約受付処理ができる。 また、 電気 通信回線 3に異常が発生した場合でも、 受付処理装置 1だけで、 予約の受付及び 呼び出しができる。  With the above operation, the reservation reception processing can be performed by the reception processing device 1 alone. Therefore, the reservation accepting process can be performed for a patient who does not use the user terminal 6. Also, even if an abnormality occurs in the telecommunications line 3, the reception processing device 1 alone can receive and call a reservation.
さらに、 受付処理装置 1とリモートサーバ 2内の状況データは定期通信処理に より同期されるため、 受付処理装置 1が単独予約受付処理を行った場合でも、 呼 出状況通知処理における呼出状況データや、 混雑状況通知処理における状況デー タの精度が低くなることはない。  Further, since the status data in the reception processing device 1 and the remote server 2 are synchronized by the periodic communication process, even if the reception processing device 1 performs the single reservation reception process, the call status data and the call status data in the call status notification process are processed. However, the accuracy of the status data in the congestion status notification processing does not decrease.
なお、 本実施の形態では病院での予約受付システムについて説明したが、 本発 明は銀行やレストランといった所定の場所でサービスを提供する業種に対しても 同様に利用できる。 受付処理装置 1とリモートサーバ 2とは、 同一業者が管理し てもよいし、 異なる業者が管理してもよい。 また、 受付処理装置 1の掲示ディス プレイ 1 5は病院や銀行、 レストランといった施設内に設置されてもよいし、 病 院ゃ銀行、 又はレストランの施設付近の喫茶店や商店街等に複数台設置されても よい。 掲示ディスプレイ 1 5を施設外に設置することで、 携帯端末 4等のユーザ 端末 6を利用しないユーザも施設内に留まって順番を待つ必要がなくなる。 本発明の実施の形態での説明中の 「所定期間」 は適切に定められ、 全て同じ期 間として設定されても良いし、 個々の期間として設定されてもよい。 以上、 本発明の実施の形態を説明したが、 上述した実施の形態は本発明を実施 するための例示に過ぎない。 よって、 本発明は上述した実施の形態に限定される ことなく、 その趣旨を逸脱しない範囲内で上述した実施の形態を適宜変形して実 施することが可能である。 Although the present embodiment has been described with reference to a reservation reception system at a hospital, the present invention can be similarly applied to industries that provide services at predetermined locations such as banks and restaurants. The reception processing device 1 and the remote server 2 may be managed by the same company or may be managed by different companies. In addition, the notice display 15 of the reception processing device 1 may be installed in a facility such as a hospital, a bank, a restaurant, or a plurality of displays may be installed in a hospital, a bank, or a coffee shop or a shopping street near a restaurant facility. You may. By installing the signage display 15 outside the facility, users who do not use the user terminal 6 such as the mobile terminal 4 do not need to stay in the facility and wait for their turn. The “predetermined period” in the description of the embodiment of the present invention is appropriately determined, and may be all set as the same period, or may be set as individual periods. The embodiment of the present invention has been described above, but the above-described embodiment is merely an example for implementing the present invention. Therefore, the present invention is not limited to the above-described embodiment, and can be implemented by appropriately modifying the above-described embodiment without departing from the spirit thereof.

Claims

請求の範囲 The scope of the claims
1 . ユーザ端末と、 前記ユーザ端末に接続可能なリモートサーバと、 前記リモ 一トサーバに接続可能な受付処理装置とによる予約受付方法であって、 1. A reservation receiving method using a user terminal, a remote server connectable to the user terminal, and a reception processing device connectable to the remote server,
前記ユーザ端末から前記リモートサーバに予約依頼を送信するステツプと、 前記リモートサーバに送信された予約依頼を前記受付処理装置に送信するステ ップと、  Transmitting a reservation request from the user terminal to the remote server; transmitting a reservation request transmitted to the remote server to the reception processing device;
前記受付処理装置に送信された予約依頼に基づいて予約受付を行うステップと を備えることを特徴とする予約受付方法。  Performing a reservation reception based on the reservation request transmitted to the reception processing device.
2 . 請求項 1に記載の予約受付方法であってさらに、 2. The reservation receiving method according to claim 1, further comprising:
前記受付処理装置から前記リモートサーバに問い合わせを行うステップを備え、 前記予約依頼を前記受付処理装置に送信するステップでは、 前記問い合わせに 応じて、 前記予約依頼を送信することを特徴とする予約受付方法。  A step of sending an inquiry to the remote server from the reception processing device; and a step of sending the reservation request to the reception processing device, wherein the booking request is transmitted in response to the inquiry. .
3 . 請求項 2に記載の予約受付方法であってさらに、  3. The reservation receiving method according to claim 2, further comprising:
前記問い合わせに対する前記リモートサーバからの応答を所定期間内に前記受 付処理装置が受信したか否かを判断するステップと、  Determining whether the reception processing device has received a response from the remote server to the inquiry within a predetermined period;
前記応答を所定期間内に受信しなかつたと判断した場合、 前記受付処理装置の オペレータに警告を通知するステップとを備えることを特徴とする予約受付方法。 Notifying the operator of the reception processing device of a warning when it is determined that the response has not been received within a predetermined period.
4 . 請求項 1〜請求項 3のいずれか 1項に記載の予約受付方法であってさらに、 前記受付処理装置から前記リモートサーバに予約状況を示す予約状況データを 所定期間ごとに送信するステップと、 4. The reservation receiving method according to any one of claims 1 to 3, further comprising: transmitting reservation status data indicating a reservation status from the reception processing device to the remote server at predetermined intervals. ,
前記ユーザ端末からの要求に応じて前記リモートサーバから前記ユーザ端末に 前記予約状況データを送信するステップとを備えることを特徴とする予約受付方 法。  Transmitting the reservation status data from the remote server to the user terminal in response to a request from the user terminal.
5 . 請求項 4に記載の予約受付方法であってさらに、 5. The reservation receiving method according to claim 4, further comprising:
前記ユーザ端末から前記リモートサーバに予約受付番号を送信するステツプと、 前記リモートサーバに送信された予約受付番号及び前記予約状況データに基づ いて、 サービスの提供を受けるまでの待ち人数及び/又は待ち時間を呼出状況デ ータとして算出するステップと、 前記リモートサーバから前記ユーザ端末に前記呼出状況データを送信するステ ップとを備えることを特徴とする予約受付方法。 A step of transmitting a reservation reception number from the user terminal to the remote server; and, based on the reservation reception number and the reservation status data transmitted to the remote server, the number of persons waiting and / or the number of waiting until service is provided. Calculating time as call status data; Transmitting the call status data from the remote server to the user terminal.
6 . ユーザ端末から予約依頼を受信するリモートサーバに接続可能な受付処理 装置による予約受付方法であって、  6. A reservation receiving method by a reception processing device connectable to a remote server that receives a reservation request from a user terminal,
前記リモートサーバに問い合わせを行うステップと、  Querying the remote server;
前記問い合わせに応じて前記リモートサーバから送信される予約依頼を受信す るステップと、  Receiving a reservation request transmitted from the remote server in response to the inquiry;
前記予約依頼に基づいて予約受付を行うステップとを備えることを特徴とする 予約受付方法。  Performing a reservation reception based on the reservation request.
7 . 請求項 6に記載の予約受付方法であってさらに、 7. The reservation receiving method according to claim 6, further comprising:
前記問い合わせに対する前記リモートサーバからの応答を所定期間内に受信し たか否かを判断するステップと、  Judging whether a response from the remote server to the inquiry has been received within a predetermined period,
前記応答を所定期間内に受信しなかつたと判断した場合、 前記受付処理装置の オペレータに警告を通知するステツプとを備えることを特徴とする予約受付方法。  A step of notifying an operator of the reception processing device of a warning when it is determined that the response has not been received within a predetermined period.
8 . 予約受付を行う受付処理装置及びユーザ端末に接続可能なリモートサーバ による予約受付方法であって、 8. A reservation receiving method using a reception processing device for receiving a reservation and a remote server connectable to a user terminal,
前記ユーザ端末から送信された予約依頼を保存するステツプと、  Saving the reservation request transmitted from the user terminal;
前記受付処理装置からの問い合わせに応じて前記保存された予約依頼を前記受 付処理装置に送信するステップとを備えることを特徴とする予約受付方法。  Transmitting the stored reservation request to the reception processing device in response to an inquiry from the reception processing device.
9 . 請求項 8に記載の予約受付方法であってさらに、  9. The reservation receiving method according to claim 8, further comprising:
所定期間ごとに前記受付処理装置から送信される予約状況を示す予約状況デー タを受信するステップと、  Receiving reservation status data indicating a reservation status transmitted from the reception processing device every predetermined period;
前記ユーザ端末からの要求に応じて、 前記予約状況データを前記ユーザ端末に 送信するステップとを備えることを特徴とする予約受付方法。  Transmitting the reservation status data to the user terminal in response to a request from the user terminal.
1 0 . 請求項 9に記載の予約受付方法であってさらに、  10. The method for accepting a reservation according to claim 9, further comprising:
前記ユーザ端末から予約受付番号を受信するステップと、  Receiving a reservation receipt number from the user terminal;
前記予約受付番号及び前記予約状況データに基づいて、 サービスの提供を受け るまでの待ち人数及び 又は待ち時間を呼出状況データとして算出するステップ と、 前記呼出状況データを前記ユーザ端末に送信するステツプとを備えることを特 徴とする予約受付方法。 Calculating, as call status data, the number of people waiting and / or the waiting time until the service is provided, based on the reservation reception number and the reservation status data; A step of transmitting the call status data to the user terminal.
1 1 . 請求項 1〜請求項 1 0のいずれかに 1項に記載のステップをコンビユー タに実行させるための予約受付プログラム。  11. A reservation acceptance program for causing a computer to execute the steps described in any one of claims 1 to 10.
1 2 . サービスの提供を受けるまでの呼出状況データを有するリモートサーバ に接続可能なユーザ端末による事前呼出方法であって、 1 2. A pre-call method by a user terminal that can be connected to a remote server having call status data until the service is provided,
外部から入力された呼出条件を保存するステツプと、  A step of storing the calling conditions input from the outside,
外部から入力された予約受付番号を前記リモートサーバに送信するステップと、 前記予約受付番号に基づいて前記リモートサーパから送信された前記呼出状況 データを受信するステップと、  Transmitting a reservation reception number input from the outside to the remote server; andreceiving the call status data transmitted from the remote server based on the reservation reception number;
前記呼出状況データが前記呼出条件を満たす力否かを判断するステップと、 前記呼出条件を満たしたとき、 前記ユーザ端末のユーザに呼出条件を満たした 旨を通知するステツプとを備えることを特徴とする事前呼出方法。  Determining whether the call status data satisfies the call condition; and, when the call condition is satisfied, notifying the user of the user terminal that the call condition has been satisfied. Pre-call method to do.
1 3 . 請求項 1 2に記載の事前呼出方法であって、  1 3. The pre-call method according to claim 1, wherein
前記判断するステップで前記呼び出し条件を満たさないと判断したとき、 前記 予約受付番号を前記リモートサーパに送信するステップと、 前記呼出状況データ を受信するステップと、 前記呼出状況データが前記呼出条件を満たすか否かを判 断するステップとを繰り返すことを特徴とする事前呼出方法。  When it is determined that the call condition is not satisfied in the determining step, a step of transmitting the reservation reception number to the remote server; a step of receiving the call status data; And a step of determining whether the condition is satisfied.
1 4 . 請求項 1 2又は請求項 1 3に記載のステップをコンピュータに実行させ るための事前呼出プログラム。  14. A pre-call program for causing a computer to execute the steps according to claim 12 or claim 13.
PCT/JP2004/001676 2003-02-28 2004-02-16 Reservation reception method, method for calling in advance, and program thereof WO2004077324A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2003054050A JP3913182B2 (en) 2003-02-28 2003-02-28 Reservation acceptance method, advance call method and program thereof
JP2003-054050 2003-02-28

Publications (1)

Publication Number Publication Date
WO2004077324A1 true WO2004077324A1 (en) 2004-09-10

Family

ID=32923451

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2004/001676 WO2004077324A1 (en) 2003-02-28 2004-02-16 Reservation reception method, method for calling in advance, and program thereof

Country Status (4)

Country Link
JP (1) JP3913182B2 (en)
KR (1) KR20050095790A (en)
CN (1) CN1754182A (en)
WO (1) WO2004077324A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011152740A1 (en) * 2010-06-03 2011-12-08 Callao Mansueto B A dynamic queuing management system
CN102968839B (en) * 2012-11-07 2016-03-23 刘海滢 A kind of with no paper self-service queuing system
KR101781704B1 (en) * 2012-11-07 2017-09-25 가부시키가이샤 코나미 데지타루 엔타테인멘토 Service delivery system and method for controlling same
CN104182501B (en) * 2014-08-18 2018-01-02 曾蔚峰 Remote reserved clinic system

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11308344A (en) * 1998-04-20 1999-11-05 Mitsubishi Electric Corp Queueing information delibery condition setting device and queueing information deribery system
JP2002140239A (en) * 2000-08-17 2002-05-17 Masahiro Mizuno Information management system, information management method and system controller

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11308344A (en) * 1998-04-20 1999-11-05 Mitsubishi Electric Corp Queueing information delibery condition setting device and queueing information deribery system
JP2002140239A (en) * 2000-08-17 2002-05-17 Masahiro Mizuno Information management system, information management method and system controller

Also Published As

Publication number Publication date
CN1754182A (en) 2006-03-29
KR20050095790A (en) 2005-09-30
JP2004265074A (en) 2004-09-24
JP3913182B2 (en) 2007-05-09

Similar Documents

Publication Publication Date Title
CN100595721C (en) Method and system for managing access to presence attribute information
US20060147005A1 (en) Queuing system
JP2003044684A (en) Order management system and method
JP5667993B2 (en) Standby order management system, management apparatus, standby order management method, and standby order management program
JP5843305B2 (en) Emergency transport support system and terminal
JP2012068838A (en) Common patient id card management system
JP2000057226A (en) Network system and maintenance method for technical service
WO2004077324A1 (en) Reservation reception method, method for calling in advance, and program thereof
KR20010047881A (en) Order-stand by service system and method by use of a radio communication terminal
JP2004348765A (en) Reservation reception method, preliminary call method, and its program
JP5398298B2 (en) Alert information creation system and alert information creation program
JP4666522B2 (en) Home care device and home care support system
TWI761732B (en) Clinic visit reminder system
WO2001090978A1 (en) Medical information providing system, medical information providing method, hospital reception method, medical information database, and patient terminal for reception of hospital
JP2004341741A (en) System and method for waiting time management, and waiting time management program
JP2003186983A (en) Notice system
JP2002351979A (en) Reservation system
JP2001325343A (en) Method for providing communication procedure agent service, reservation procedure method, communication procedure agent system, and reservation procedure system
WO2021054171A1 (en) Order management system, order management device, and program
KR100588091B1 (en) System for transmitting the information of waiting list by using SMS and the Method
JP2013017098A (en) Care call system and 24-hour operating care support system using the same
JP6581689B1 (en) Order management system, order management apparatus, and program
EP2003866B1 (en) Connection device, connection method, and connection program
JP6814609B2 (en) Nurse call system
JP2003173373A (en) Wait information report system for dispensing pharmacy

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 1020057015759

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 20048054627

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 1020057015759

Country of ref document: KR

122 Ep: pct application non-entry in european phase