WO2004077324A1 - Procede de reception de reservation, procede d'appel anticipe, et programme correspondant - Google Patents

Procede de reception de reservation, procede d'appel anticipe, et programme correspondant 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
English (en)
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/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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/00—Administration; Management
    • G06Q10/02—Reservations, 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.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Theoretical Computer Science (AREA)
  • Marketing (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Human Resources & Organizations (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Technology Law (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Medical Treatment And Welfare Office Work (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

Lorsqu'un utilisateur désire faire une réservation, l'utilisateur introduit une demande de réservation dans un terminal utilisateur (6). Le terminal utilisateur (6) transmet la demande de réservation à un serveur distant (2). Le serveur distant (2) mémorise la demande de réservation. Lorsqu'un dispositif de traitement de réception (1) transmet un message de recherche au serveur distant (2), ce dernier répond au message de recherche et transmet la demande de réservation mémorisée au dispositif de traitement de réception (1). Le dispositif de traitement de réception (1) effectue une réception de réservation, conformément à la demande de réservation reçue. Grâce à l'opération précitée, le dispositif de traitement de réception (1) reçoit une information du serveur qui a répondu au message de recherche, de sorte qu'il est possible d'empêcher un accès non autorisé.
PCT/JP2004/001676 2003-02-28 2004-02-16 Procede de reception de reservation, procede d'appel anticipe, et programme correspondant WO2004077324A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2003054050A JP3913182B2 (ja) 2003-02-28 2003-02-28 予約受付方法、事前呼出方法及びそのプログラム
JP2003-054050 2003-02-28

Publications (1)

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

Family

ID=32923451

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2004/001676 WO2004077324A1 (fr) 2003-02-28 2004-02-16 Procede de reception de reservation, procede d'appel anticipe, et programme correspondant

Country Status (4)

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

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011152740A1 (fr) * 2010-06-03 2011-12-08 Callao Mansueto B Système de gestion dynamique de la mise en file d'attente
CN104769633B (zh) * 2012-11-07 2018-04-10 科乐美数码娱乐株式会社 服务提供系统以及该服务提供系统的控制方法
CN102968839B (zh) * 2012-11-07 2016-03-23 刘海滢 一种无纸化自助排号系统
CN104182501B (zh) * 2014-08-18 2018-01-02 曾蔚峰 远程预约门诊系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11308344A (ja) * 1998-04-20 1999-11-05 Mitsubishi Electric Corp 順番待ち情報配信条件設定装置および順番待ち情報配信方式
JP2002140239A (ja) * 2000-08-17 2002-05-17 Masahiro Mizuno 情報管理システム及び情報管理方法及びシステム制御装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH11308344A (ja) * 1998-04-20 1999-11-05 Mitsubishi Electric Corp 順番待ち情報配信条件設定装置および順番待ち情報配信方式
JP2002140239A (ja) * 2000-08-17 2002-05-17 Masahiro Mizuno 情報管理システム及び情報管理方法及びシステム制御装置

Also Published As

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

Similar Documents

Publication Publication Date Title
CN100595721C (zh) 用于管理存取现状属性信息的方法和系统
US20060147005A1 (en) Queuing system
JP2003044684A (ja) 順番管理システム及び方法
JP5667993B2 (ja) 待順管理システム、管理装置、待順管理方法及び待順管理プログラム
JP5843305B2 (ja) 救急搬送支援システム及び端末
JP2012068838A (ja) 共通診察券管理システム
JP2000057226A (ja) 技術サービス用ネットワークシステム及び保守方法
WO2004077324A1 (fr) Procede de reception de reservation, procede d'appel anticipe, et programme correspondant
KR20010047881A (ko) 무선단말기를 이용한 순번대기 서비스 시스템 및 방법
JP2004348765A (ja) 予約受付方法、事前呼出方法及びそのプログラム
JP5398298B2 (ja) アラート情報作成システムおよびアラート情報作成プログラム
WO2001090978A1 (fr) Systeme d'information medicale, procede correspondant, procede de reception d'information d'hopital, base de donnees d'information medicale, et terminal de patient pour la reception d'information d'hopital
JP4666522B2 (ja) 訪問介護装置及び訪問介護支援システム
TWI761732B (zh) 診所看診提醒系統
JP2004341741A (ja) 待ち時間管理システムおよび管理方法並びに待ち時間管理プログラム
JP2003186983A (ja) 通知システム
JP2002351979A (ja) 予約システム
JP2001325343A (ja) 連絡手続代行サービスの提供方法、予約手続方法、連絡手続代行システム及び予約手続システム
WO2021054171A1 (fr) Système de gestion de commande, dispositif de gestion de commande et programme
KR100588091B1 (ko) 단문 메시지 서비스를 이용한 대기현황 정보 발송 시스템및 그 방법
JP2013017098A (ja) ケアコールシステム及びこれを用いた２４時間対応型介護支援システム
JP6581689B1 (ja) 順番管理システム、順番管理装置、およびプログラム
EP2003866B1 (fr) Dispositif, procede et programme de connexion
JP6814609B2 (ja) ナースコールシステム
JP2003173373A (ja) 調剤薬局向け待ち情報通知システム

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