JP7287613B2 - Support server, patient computer program and service support method - Google Patents

Description

Applied to Article 30, Paragraph 2 of the Patent Law Released from the website on May 28, 2019 Distributed flyers at Tottori University Hospital on May 28, 2019 Tottori University Hospital on September 24, 2019 Published on the website Pamphlet distribution at Tottori University Hospital on September 24, 2019 Public press conference at Tottori University Hospital on October 7, 2019 Tottori University School of Medicine on October 8, 2019 Published in the Ehime Shimbun morning edition on October 17, 2019 Published in the Kyoto Shimbun evening edition on October 17, 2019 Published in the Tou Nippo on October 17, 2019 Tottori on November 28, 2019 Public relations magazine placed in the university hospital Announced at the 2019 university hospital information management department liaison conference (Akita Castle Hotel) on January 30, 2020 The 9th Sanin on February 1, 2020 Presented at the Cultural Area Medical Information Technology Study Group (Yonago Medical Center, Kuzumo Hall)

TECHNICAL FIELD The present invention relates to technology for assisting reception and calling for a patient to receive a medical examination at a medical institution .

In recent years, as consumer needs have changed from "things" to "things", it is becoming increasingly important for service providers to create a system for providing services such as reception and calling, in addition to the quality of the service itself. ing. For example, Patent Literatures 1 to 4 below propose various techniques for calling service users.

In Patent Document 1 below, the notification time is calculated based on the travel time required to move from the user's current location to the service provision location and the scheduled time when the user's turn will come, and when the notification time comes, the turn will approach. A turn notification system is disclosed that notifies a user's mobile terminal that the order has been placed.
Patent Document 2 below discloses statistical data obtained by statistically processing service information and user information, requests from users regarding waiting information, and travel time from the location of the user to the service provider. An apparatus is disclosed for setting queue information delivery conditions to and.
Patent Document 3 below describes a notice to display notification information that urges a customer to move to a service providing location based on the required time from the customer's current location to the service providing location and the service start time for the customer. A terminal device is disclosed that calculates the time and displays the notification information at the notification time.
Patent Document 4 below discloses a call system that acquires the position of a relay device that communicates with a mobile terminal as patient position information and notifies the mobile terminal of call information according to the distance between the patient's position and the position of the examination room. An outpatient call notification system is disclosed that calculates timing and notifies call information to a mobile terminal according to the result of comparison between the order of medical examination and the call timing or the designated timing set from the mobile terminal.

Japanese Patent Application Laid-Open No. 2003-143648 JP-A-11-308344 JP 2010-286958 A JP 2015-49620 A

However, the proposed method described above hardly mentions a mechanism related to reception for receiving the target service. It is troublesome for the service user to go to the counter once for reception.
SUMMARY OF THE INVENTION The present invention has been made in view of such circumstances, and provides a technique for assisting reception or calling for a medical examination at a medical institution so as not to make the patient feel stressed.

A support server according to one aspect of the present invention supports reception and calling for a patient to receive a medical examination at a target medical institution . A support server according to this aspect includes a terminal information table that stores a unique ID that can identify a patient and a terminal token of the patient's portable terminal in association with each other, and a unique ID, reception information, and call confirmation history for each patient. a patient management table stored respectively; a position obtaining means for obtaining position information of the portable terminal of the patient ; determining whether or not the position information satisfies a predetermined condition; A terminal control means for controlling the terminal to switch to a reception operable state or a reception operable state , and a call including the unique ID of the accepted patient in response to a call operation specifying a patient accepted to the terminal of the electronic medical record system Designating an instruction acquisition means for acquiring an instruction and a terminal token stored in the terminal information table in association with the unique ID included in the acquired call instruction, push notification of call information including the unique ID. and the user's confirmation operation on the call information display including the patient name, reception information and notification message displayed on the mobile terminal of the accepted patient who received the push notification of the call information, confirmation receiving means for receiving, from the portable terminal, confirmation information indicating that a call information confirmation operation has been performed and including the unique ID of the patient who has received a call; and receiving a push notification of the call information and the confirmation information. a holding means for adding a call history and a confirmation history to a call confirmation history stored in the patient management table associated with the unique ID of the accepted patient; and a portable terminal of the accepted patient. means for transmitting confirmation information including the unique ID of the accepted patient to the electronic medical record system upon receipt of the confirmation information from.
In addition, a computer program for patients according to another aspect of the present invention can be executed by a mobile terminal capable of communicating with the above-described support server , and the mobile terminal receives operation based on information sent from the support server. When the reception operation is detected, the reception application information including the unique ID of the patient to be accepted is transmitted to the support server , and the reception application information is transmitted from the support server . receiving the corresponding reception reply information; if the received reception reply information indicates a reception error , displaying information indicating the content of the error ; and if the received reception reply information indicates reception completion, Display information indicating reception completion, receive a push notification of the call information from the support server, display the call information including the name of the accepted patient, reception information and a notification message so that confirmation operation is possible, and display the call information is detected, confirmation information indicating that the call information confirmation operation has been performed and including the unique ID of the accepted patient is transmitted to the support server.
Also, a service support method according to another aspect of the present invention is executed by a server device and a mobile terminal, and supports reception and calling for a patient to receive treatment at a target medical institution . In this service support method, the server device includes a terminal information table that stores a unique ID that can identify a patient and a terminal token of the patient's portable terminal in association with each other, and a unique ID, reception information, and call confirmation history for each patient. A server device or a mobile terminal obtains location information of the mobile terminal, determines whether the location information satisfies a predetermined condition, and determines whether the mobile terminal satisfies a predetermined condition. , according to the result of the determination, it switches to the reception operation possible state or the reception operation impossible state, and the server device responds to the call operation specifying the accepted patient to the terminal of the electronic medical record system, the accepted patient acquires a call instruction including the unique ID of the call instruction, designates a terminal token stored in the terminal information table in association with the unique ID included in the acquired call instruction, and creates call information including the unique ID Push notification is performed, and the mobile terminal receives the push notification of the call information from the server device, displays the call information including the name of the accepted patient, the reception information, and the notification message so that the call can be operated. When the user's confirmation operation for displaying the information is detected, confirmation information indicating that the confirmation operation of the call information has been performed and including the unique ID of the accepted patient is transmitted to the server device, and the server device , receiving the confirmation information, and in response to the push notification of the call information and the reception of the confirmation information, call history and confirmation history, and sending confirmation information including the unique ID of the accepted patient to the electronic chart system .

ADVANTAGE OF THE INVENTION According to this invention, the technique which assists the reception desk for a medical examination at a medical institution, or a call can be provided so that a patient may not feel stress.

1 is a schematic diagram showing a system configuration of a service support system according to this embodiment; FIG. FIG. 2 is a schematic diagram showing a hardware configuration example of a service support server and a mobile terminal; 2 is a block diagram conceptually showing the software configuration of a service support server and a mobile terminal; FIG. 4A and 4B are diagrams showing examples of information stored in the terminal information storage unit, FIG. 4A exemplifying a terminal information table storing terminal information related to the mobile terminal, and FIG. illustrates a patient management table that stores management information regarding patient calls and receptions. It is a figure which illustrates the patient information table stored in a patient information storage part. FIG. 4 is a diagram showing an example of a main screen of an application for service users displayed on a mobile terminal; 10 is a flowchart showing an operation example of a mobile terminal when registering a patient; 4 is a flow chart showing an operation example of the service support server and the portable terminal when a patient performs reception; 4 is a flow chart showing an operation example of the service support server and the portable terminal when calling a patient; 10A and 10B are diagrams showing display examples of the portable terminal, FIG. 10A showing an example of a display for selecting patients to be accepted, and FIG. FIG. 10(c) shows an example of the display of call information.

An embodiment of the present invention will be described below with reference to the drawings. The embodiments listed below are examples, and the present invention is not limited to the configurations of the following embodiments.

FIG. 1 is a schematic diagram showing the system configuration of a service support system according to this embodiment.
The service support system according to this embodiment includes a service support server (hereinafter abbreviated as a support server) 1, an electronic chart system 5, and the like, and supports the provision of medical services by medical institutions. Specifically, the service support system communicates with the mobile terminals 8 of individual patients to support reception and calling for patients to receive medical services.

The electronic medical chart system 5 is a system consisting of one or more computers that perform general processing related to electronic medical charts.
In this embodiment, the electronic medical record system 5 performs reception processing in response to a reception application from the support server 1, and sends back a reception response to the support server 1 as a result of the reception processing, as will be described later. In addition, the electronic medical record system 5 manages the reception status of each patient according to the reception application from the support server 1 and reception at the reception counter, etc. It has an interface. In this call interface, a screen for receiving a call operation by a doctor or the like is displayed on the medical institution side terminal, and a call instruction for the target patient is sent to the support server 1 according to the call operation. In addition, the call interface can display location information for each accepted patient and confirmation information (read or unread) for the call.
However, the electronic medical record system 5 can transmit a patient call instruction to the support server 1, perform reception processing according to the reception application sent from the support server 1, and support the reception reply as a result of the reception processing. As long as it can be sent back to the server 1, other specific functions and processes are not limited at all.

The support server 1 intervenes between each mobile terminal 8 and the electronic medical record system 5 and executes various processes for service support while communicating with each mobile terminal 8 and the electronic medical chart system 5 .
The mobile terminal 8 is a mobile computer owned by each patient, such as a smart phone, a tablet terminal, or a mobile notebook PC (Personal Computer). The portable terminal 8 communicates with the support server 1 by operating an application for receiving service support by the service support system according to the present embodiment, and performs the operation on the patient side, that is, the service user side of the service support system. to realize a user interface of

[Hardware configuration]
FIG. 2 is a schematic diagram showing a hardware configuration example of the service support server 1 and the mobile terminal 8. As shown in FIG.
The support server 1 is a so-called computer, and as shown in FIG. 2, a CPU (Central Processing Unit) 11, a memory 12, an input/output interface (I/F) 13, and a communication unit 14, which are interconnected by a bus. etc.
The CPU 11 may be one or more general CPUs or MPUs (Micro Processing Units), alternatively or together therewith, application specific integrated circuits (ASICs), DSPs (Digital Signal Processors), GPUs (Graphics Processing Unit), FPGA (Field Programmable Gate Array), or the like.
The memory 12 is RAM (Random Access Memory) and ROM (Read Only Memory), and includes an auxiliary storage device (hard disk, etc.).

The input/output I/F unit 13 is a device that controls input or output of signals to be processed or processed by the CPU 11, and can be connected to a display device 15, an input device 16, a user interface device such as a microphone, and the like. The input/output I/F unit 13 can also be connected to a portable recording medium or the like.
The display device 15 is a device such as an LCD (Liquid Crystal Display) or a CRT (Cathode Ray Tube) display that displays a screen corresponding to drawing data processed by the CPU 11 or the like. The input device 16 is a device such as a keyboard, a mouse, etc., that receives user-operated input. The display device 15 and the input device 16 may be integrated and implemented as a touch panel. Moreover, both or one of the display device 15 and the input device 16 may be omitted.
The communication unit 14 communicates with the electronic chart system 5 and the mobile terminal 8 . Communication between the support server 1 and the mobile terminal 8 is performed via a communication network including the Internet, and may be performed via an external relay server connected to the communication network, or may be performed directly. good too.

As described above, the mobile terminal 8 is a mobile computer such as a smartphone, a tablet terminal, a mobile notebook PC, etc., and includes a CPU 81, a memory 82, a display unit 83, a touch sensor 84, a communication unit 85, an imaging unit 86, and a microphone. It has a unit 87, a speaker unit 88, and the like.
CPU 81 and Memory 82 As described for the CPU 11 and memory 12 above.
The display unit 83 is similar to the display device 15 and forms a touch panel together with the touch sensor 84 . The touch sensor 84 receives an operation input from the user by sensing contact from the outside. The touch sensor 5 may be a sensor capable of detecting a proximity state from the outside even in a non-contact state. However, together with the touch sensor 5 or instead of the touch sensor 5, the mobile terminal 8 may have an input/output interface (not shown) connected to an input device such as a mouse or a keyboard.

A microphone unit 87 is a sound collecting device.
The speaker unit 88 is an audio output device.
The imaging unit 86 acquires a captured image.
The communication unit 85 performs wireless communication or wired communication, and communicates with the support server 1 via a communication network. Further, the communication unit 85 may obtain information from the support server 1 via an external server connected to the communication network. The communication system realized by the communication unit 85 is various, such as a mobile communication system, a Wi-Fi system, and a Bluetooth system, and is not limited at all. In this embodiment, the communication unit 8 includes a GPS (Global Positioning System) receiver.

The hardware configurations of the support server 1 and the mobile terminal 8 are not limited to the configurations shown in FIG. The number of each hardware element is not limited to the example shown in FIG. 2, and the support server 1 and the mobile terminal 8 may include hardware elements not shown in FIG. For example, the mobile terminal 8 may have a vibration sensor, an acceleration sensor, and a geomagnetic sensor that can detect other types of user operations not shown in FIG.

[Software configuration]
Next, software configurations of the support server 1 and the mobile terminal 8 will be described with reference to FIG.
FIG. 3 is a block diagram conceptually showing the software configuration of the support server 1 and the mobile terminal 8. As shown in FIG.
The support server 1 implements a software configuration as shown in FIG. 3 by executing a computer program stored in the memory 12 by the CPU 11 . Specifically, the support server 1 has, as software elements, a terminal information storage unit 20, a terminal communication module 21, a relay processing module 22, a terminal control module 23, and the like.
The mobile terminal 8 implements a software configuration as shown in FIG. 3 by executing a computer program (sometimes referred to as an application for service users) stored in the memory 82 by the CPU 81 . Specifically, the mobile terminal 8 has a patient information storage unit 90, a registration processing module 91, a reception processing module 92, a call processing module 93, a display processing module 94, and the like.
However, each software element shown in FIG. 3 is conceptually shown separately for convenience of explanation. It may not be clearly separated into each element as shown.

The terminal information storage unit 20 of the support server 1 stores information on the mobile terminal 8 and information on reception and calling of patients registered in the mobile terminal 8 .
4A and 4B are diagrams showing examples of information stored in the terminal information storage unit 20. FIG. 4A shows an example of a terminal information table storing terminal information about the mobile terminal 8, and FIG. b) illustrates a patient management table that stores management information regarding patient calls and receptions;

The terminal information table contains, for each patient, an identifier (expressed as a unique ID) that can identify the patient, a terminal token of the mobile terminal 8 in which the patient's information is registered, and location information of the mobile terminal 8. Store in association.
A unique ID for each patient is generated at the time of patient registration in the mobile terminal 8 and stored in the terminal information table. Here, the unique ID can also be called a user identifier that can identify individual service users.
A terminal token is information used when the support server 1 sends a push notification to each mobile terminal 8 , and is information uniquely given to each mobile terminal 8 or to each application of the mobile terminal 8 . The terminal token may be assigned by the support server 1 or may be assigned by an external server interposed between the support server 1 and the mobile terminal 8 . In the latter case, for example, a terminal token (registration token) is issued by an FCM (Firebase Cloud Messaging) connection server, which is an external server, and provided to the mobile terminal 8 . However, the terminal token only needs to be capable of realizing push notification to each mobile terminal 8, and the granting method and specific contents are not limited.
The location information is information indicating the location of each mobile terminal 8 . The position information is periodically sent from the mobile terminal 8 to the support server 1 and reflected in the terminal information table by the support server 1 .

Although details will be described later, in this embodiment, a plurality of patients can be registered in the mobile terminal 8 . As a result, the mother can not only register herself as a patient in her portable terminal 8, but also her child as a patient, and can also register the elderly person (parents, etc.) accompanying her as a patient. can.
As a result, in the terminal information table described above, one terminal token may be associated with a plurality of unique IDs and stored.

The patient management table stores the unique ID, reception information, reception status, and calling/confirmation history for each patient in association with each other.
The reception information is information reflected in the patient management table by the support server 1 based on the reception reply information sent from the electronic chart system 5 to the support server 1 . The reception information indicates information such as the reception number, department name, appointment time, etc., when the electronic medical record system 5 has completed the reception processing. show.
The reception status indicates the reception status of each patient, such as reception completed, no reception, reception error, and the like. When the reception reply information received from the electronic medical record system 5 indicates reception completion, the reception status is set to "accepted", and when the reception reply information indicates reception error, the reception status is set to reception error. be. Further, when the reception completion information is received from the electronic medical record system 5, the reception information is initialized, and the reception state is set to the initial state (no reception).
The call/confirmation history shows a history of a combination of call status and confirmation status for the call for each patient. For example, for each call, the call time and the presence or absence of confirmation operation for that call are associated and stored as a call/confirmation history. When the push notification of call information is performed from the support server 1, one history information including the time at that time is added, and after that, when the confirmation information is received from the mobile terminal 8, the one history information is confirmed. Confirmation is set in the status.

The patient information storage unit 90 of the mobile terminal 8 stores information on patients registered in the mobile terminal 8 and information on reception of the patient.
FIG. 5 illustrates a patient information table as an example of information stored in the patient information storage unit 90. As shown in FIG.
The patient information table stores unique IDs, patient IDs, patient names, reception information, and reception statuses for each of one or more patients registered in the mobile terminal 8 in association with each other. Such patient-by-patient information is generated at the time of patient registration in the mobile terminal 8 and added to the patient information table. Details of patient registration in the mobile terminal 8 will be described later.

The unique ID is as described above, and is the same as the unique ID stored in the terminal information storage unit 20 of the support server 1. FIG.
A patient ID is an identifier that can identify each patient in the electronic medical record system 5 . In this embodiment, a patient ID managed within the electronic medical record system 5 and a unique ID assigned separately from the patient ID are provided as individual patient identifiers. The patient ID is held in the electronic chart system 5 and the portable terminal 8, but not held in the support server 1. FIG. As a result, the patient ID, which has the property of being personal information, is used only by the mobile terminal 8 owned by the individual patient or the electronic medical record system 5 of the medical institution, which leads to the protection of personal information.
The patient name is a name for identifying each patient on the display of the mobile terminal 8 and can be edited by operating the mobile terminal 8 .
The reception information is information reflected in the patient information table by the mobile terminal 8 based on reception response information sent from the support server 1 to the mobile terminal 8 . The reception information indicates information such as the reception number, department name, appointment time, etc., when the electronic medical record system 5 has completed the reception processing. show.
The reception status indicates the reception status of each patient registered in the mobile terminal 8, such as reception completed, no reception, reception error, and the like. When the reception reply information received from the support server 1 indicates reception completion, the reception status is set to "accepted", and when the reception reply information indicates reception error, the reception status is set to reception error. . Further, when the reception completion information is received from the support server 1, the reception information is initialized and the reception state is set to the initial state (no reception).

However, the information shown in FIGS. 4 and 5 are examples, respectively, and the support server 1 or the mobile terminal 8 stores other information not shown in FIGS. 90, and the table structures of the terminal information storage unit 20 and the patient information storage unit 90 are not limited to the examples shown in FIGS.
For example, the terminal information storage unit 20 of the support server 1 may store the history of the location information of each mobile terminal 8 . In this case, time information and location information may be associated and stored for each mobile terminal 8 . Further, the patient information storage unit 90 of the portable terminal 8 may store call/confirmation history for each patient as shown in FIG. 4(b).

FIG. 6 is a diagram showing an example of the main screen of the application for service users displayed on the mobile terminal 8. As shown in FIG.
While the service user application is running, the display processing module 94 causes the display unit 83 to display the main screen illustrated in FIG.
A menu section DM is provided at the upper end of the main screen, and a reception operation section DU, a registration operation section DT, and an information presentation section DS are provided below the menu section DM.
In the menu part DM, an application name "service use application" is displayed, and an icon DC1 of a registrant edit menu and an icon DC2 of a call history menu are displayed.
The reception operation unit DU is operated when accepting a patient, and the registration operation unit DT is operated when a patient is registered in the mobile terminal 8 .
Various types of information are presented to the information presentation unit DS. For example, before reception, a message such as ``Accept today's reservation by pressing the reception button'' is displayed. Please come to window No. 1.”, and error messages such as “You need to confirm your health insurance card. Please come to window No. 3.”

Here, when an operation of the icon DC1 is detected, the display processing module 94 displays a list of patient IDs and patient names stored in the patient information storage unit 90, and displays a list of patient IDs and patient names stored in the patient information storage unit 90. , the changed patient name is reflected in the patient information table of the patient information storage unit 90 .
Further, the display processing module 94 can display the call/confirmation history stored in the patient information storage unit 90 when the operation of the icon DC2 is detected.
Details of operations performed on the reception operation unit DU and the registration operation unit DT will be described later.

The support server 1 and the portable terminal 8 operate as shown in FIGS. 7, 8 and 9 by the respective software elements executing processes using the various information stored as described above. . Therefore, in describing an operation example of the support server 1 and the mobile terminal 8, the processing contents of each software element of the support server 1 and the mobile terminal 8 will also be described in detail below.
In the following description, the subject of each operation is indicated by the name of the software element. Each operation is realized by executing a computer program (application for service users) stored in the memory 82 by the CPU 81 .

[Example of operation]
[Operation at the time of registration]
First, an operation example of the mobile terminal 8 when registering a patient in the mobile terminal 8 will be described with reference to FIG.
FIG. 7 is a flow chart showing an operation example of the portable terminal 8 at the time of patient registration.
When registering a patient in the portable terminal 8, the user causes the registration terminal (not shown) to read the patient's patient identification card to be registered. The patient ID card contains at least the patient ID so that it can be read by the registration terminal. The patient registration card may be a magnetic card, an IC card, or a card on which a two-dimensional code is printed.
The registration terminal can communicate with the support server 1. When the patient ID is successfully read, the registration terminal generates a unique ID corresponding to the patient ID. registered trademark)).
After that, when the user of the mobile terminal 8 presses the registration operation section DT on the main screen (see FIG. 6), the mobile terminal 8 operates as shown in FIG.

When an operation on the registration operation section DT on the main screen (see FIG. 6) is detected, the registration processing module 91 activates the imaging unit 86 (S71). Imaging is thereby started, and the registration processing module 91 scans the two-dimensional code displayed on the registration terminal (S72).
If the two-dimensional code is successfully scanned (S73; YES), the registration processing module 91 can acquire the patient ID and unique ID (S74). If scanning fails (S73; NO), scanning of the two-dimensional code is repeated (S72).
When the patient ID and unique ID are acquired, the display processing module 94 displays an input screen for the patient name corresponding to the patient ID (S75). The user inputs the patient name on the input screen.
When the patient name is entered, the display processing module 94 displays a display asking whether the registration is permitted and a display that enables a registration OK operation.

When the registration OK operation is detected (S76; YES), the registration processing module 91 generates patient information including the unique ID and patient ID obtained in (S74) and the patient name input in (S75). , the patient information is added to the patient information table (patient information storage unit 90) (S77). In the patient information to be added, there is no reception information (in the initial state), and the reception status is "no reception".
Thereafter, the display processing module 94 outputs a display asking whether a test call is made or the registration procedure is completed for the patient whose patient information has been added in (S77).
When the test call operation is detected (S78; YES), the call processing module 93 transmits a test call request including the unique ID obtained in (S74) to the support server 1 (S79).

In the support server 1, when the test call request is received, the terminal control module 23 stores the terminal token associated with the unique ID in the terminal information table (terminal information storage table) based on the unique ID included in the test call request. 20), specify the terminal token, and push notification of the test call information. This test call information push notification is performed in the same manner as the call information push notification described later.
As a result, the user of the mobile terminal 8 can confirm whether the test call is properly executed.

If the operation to complete the registration procedure is not detected (S80; NO), the display asking whether to make a test call or complete the registration procedure is continuously output.
When the completion operation of the registration procedure is detected (S80; YES), the registration processing module 91 transmits a registration request including the unique ID acquired in (S74) and its own terminal token to the support server 1 (S81). . As a result, the support server 1 associates the unique ID included in the registration request with the terminal token of the portable terminal 8 that sent the registration request, and additionally stores them in the terminal information table (terminal information storage unit 20). In addition, the support server 1 also adds the patient information including the unique ID included in the registration request to the patient management table (terminal information storage unit 20). In this patient information, there is no reception information (initial state), the reception status is no reception, and there is no call/confirmation history.

Here, the terminal token may be obtained from the support server 1 or an external server when the service user application is activated for the first time, or obtained when the first patient is registered on the mobile terminal 8. may be The mobile terminal 8 holds the obtained terminal token.
Further, when the unique ID and the patient ID are acquired in (S74), the registration processing module 91 determines whether the patient ID has already been registered in the patient information table (patient information storage unit 90), You can also display an error if it is already registered.

As described above, multiple patients can be registered in one mobile terminal 8 in this embodiment. Therefore, the processing flow shown in FIG. 7 should be executed for each patient to be registered.
Moreover, the user of the portable terminal 8 may be a patient who will receive a medical examination from now on, or may not be the patient.

[Operation at reception]
Next, an operation example of the support server 1 and the portable terminal 8 when accepting is described with reference to FIG.
FIG. 8 is a flow chart showing an operation example of the support server 1 and the portable terminal 8 when a patient performs reception. Here, as a premise for performing the operation of FIG.

The mobile terminal 8 transmits the position information to the support server 1 at periodic or arbitrarily repeated timings (S90). The position information transmitted here may be position information acquired by the mobile terminal 8, for example, position information obtained based on a GPS signal received by a GPS receiver mounted on the mobile terminal 8. location information obtained using a beacon signal, or location information obtained using a wireless LAN (Wi-Fi).
When the support server 1 (terminal communication module 21) acquires the location information from each mobile terminal 8, the new location information is associated with the terminal token of the mobile terminal 8 and stored in the terminal information table (terminal information storage unit 20). The stored location information is updated (S91). Therefore, the terminal communication module 21 can be described as position acquisition means for acquiring position information of the mobile terminal. At this time, in the support server 1, the relay processing module 22 extracts the unique ID associated with the updated location information from the terminal information table, and extracts the extracted unique ID and the updated location information of the patient. The location information may be transmitted to the electronic medical chart system 5 . In this way, the electronic medical record system 5 can manage current position information for each patient.

When the position information is updated in the support server 1, the terminal control module 23 determines whether or not the mobile terminal 8 corresponding to the position information is positioned within a predetermined area (S92).
This predetermined area may be an area that includes at least part of the building of the target medical institution. It may be set within a range of a predetermined distance (for example, 500 meters), or may be set over the entire area within the premises or building of the target medical institution.
Also, this predetermined area may be set, for example, to a range within which the elderly can walk to the front of the examination room within a predetermined time (for example, 15 minutes) after being called.

The terminal control module 23, according to the determination result of (S92), transmits reception-ready information to the mobile terminal 8 determined to be located within the predetermined area (S92; YES) (S93), If it is determined that the mobile terminal 8 is not located within the predetermined area (S92; NO), the mobile terminal 8 is transmitted with reception-impossible information (S94).
The mobile terminal 8 puts the reception operation unit DU into an operable state (sometimes referred to as an active state) when receiving the reception-possible information, and puts the reception operation unit DU into an operable state (sometimes referred to as an active state) when receiving the reception-impossible information. is in an inoperable state (sometimes referred to as an inactive state) (S95).
For this reason, the terminal control module 23 determines whether or not the position information satisfies a predetermined condition, and controls the mobile terminal 8 to switch between the reception operation enabled state and the reception operation disabled state according to the result of the judgment. In other words, it is a control means.

The content of the acceptable information to be transmitted is not limited in any way, and the acceptable information may be information indicating that acceptance is possible, or information instructing to activate the acceptance operation unit DU. It may be information indicating that the mobile terminal 8 is located within a predetermined area. Similarly, the content itself of the non-acceptance information is not limited at all. The reception-impossible information may be information indicating that reception is not possible, information instructing to put the reception operation unit DU in an inactive state, or information indicating that the mobile terminal 8 is within a predetermined area. may be information indicating that it is not located at

In addition, the "receiving operation disabled state" of the mobile terminal 8 means a state in which the receiving operation cannot be performed. For this reason, in this specification, the inactive state of the reception operation unit DU means a state in which the mobile terminal 8 cannot accept operations on the reception operation unit DU, and the reception operation unit DU is displayed in this state. It also includes states that are not (erased).

In this way, by switching the mobile terminal 8 between the reception operation enabled state and the reception operation disabled state depending on whether the position information of the mobile terminal 8 satisfies a predetermined condition, the service user can be brought to the service providing location when calling after the reception. It can prevent situations such as being in a place where you can not come. Furthermore, since the service user can accept the application by operating the portable terminal 8, it is possible to eliminate the troublesomeness of going to the counter for the application.

When the reception operation unit DU is set to the active state, the portable terminal 8 displays the reception operation unit DU in a display mode corresponding to the active state. can be made inactive (S95). For example, on the reception operation unit DU in the active state, the characters "accept" are displayed in a form (size or color) that is easy to see, and the outline of the reception operation unit DU is also displayed in a form that is easy to see. In the reception operation unit DU in the state, the characters "accept" are displayed in a form (size or color) that is difficult to see, and the outline display of the reception operation unit DU is also displayed in a form that is difficult to see. However, the display mode of the reception operation unit DU in the active state and inactive state is not limited to such an example. For example, in the non-active state, the characters displayed on the reception operation unit DU may be "out of acceptance range", and the display may not be in a form that is difficult to see. Further, the contour display of the reception operation unit DU in the inactive state may not be made difficult to see, and the display color of the reception operation unit DU as a whole may be changed. Furthermore, the reception operation unit DU may not be displayed in the inactive state.
This makes it possible for the user to easily grasp whether the reception operation unit DU is in the active state or the inactive state.

After that, when an operation to the reception operation unit DU in the active state is detected (S96; YES), the reception processing module 92 transmits reception application information including the unique ID of the patient who receives the operation to the support server 1. (S97). Here, when only one patient is registered in the mobile terminal 8, the unique ID to be included in the reception application information can be easily extracted from the patient information table (patient information storage unit 90).
When two or more patients are registered in the mobile terminal 8, the display processing module 94 accepts from among the registered patients based on the information stored in the patient information table. Outputs a selection display that allows one or more patients to be selected. Then, the reception processing module 92 extracts the unique IDs of one or more patients selected in this selection display from the patient information table, and transmits reception application information including the extracted one or more unique IDs to the support server 1. (S97).

As described above, according to the present embodiment, it is possible to register a plurality of patients (service users) in the mobile terminal 8, and to select a patient (service user) from among the registered patients for reception. You can specify and apply for acceptance. In addition, it is also possible to apply for reception of multiple patients at once.

FIG. 10(a) is a diagram showing an example of a reception patient selection display. In the example of FIG. 10A, a selection display DP1 is popped up. Two patients ("Patient S" and "Patient T") can be selected in the selection display DP1, and a state in which both patients are selected is illustrated. The operation of pressing the reception button in the selection display DP1 is the reception operation.

In the support server 1, when the reception application information is received, the relay processing module 22 designates the unique ID included in the received reception application information and applies for reception to the electronic medical record system 5 (S98). At this time, the relay processing module 22 may transfer the reception application information received from the mobile terminal 8 to the electronic medical record system 5 as a reception application, or may transfer the information of another format including the unique ID included in the reception application information. may be transmitted to the electronic medical record system 5 as a reception application.
In response to this reception application, the electronic medical record system 5 identifies the patient ID corresponding to the specified unique ID, and executes reception processing based on that patient ID. In this reception process, it is determined whether or not the patient's examination may be accepted. For example, in the reception process, it is determined whether or not the patient has a consultation appointment for that day, whether or not the appointment time has passed, and whether or not confirmation of the patient's health insurance card is required. However, the reception processing by the electronic medical chart system 5 only needs to include a determination as to whether or not the patient's consultation is acceptable, and the specific contents of the reception processing are not limited at all.

When the electronic medical record system 5 completes such reception processing, the electronic medical record system 5 returns reception response information for the reception application information to the support server 1 . This reception response information may include at least the unique ID included in the reception application information and the determination result as to whether or not the patient corresponding to the unique ID may be accepted for consultation. , acceptance status information indicating acceptance completion or acceptance error is included as the determination result. In this embodiment, the reception reply information indicates information such as the reception number, department name, and appointment time when the reception is completed, and when the reception error occurs, the reception response information indicating the error details. Further information is included.
Thereby, the support server 1 receives the reception reply information (S99).

In the support server 1, when the reception reply information is received, the terminal communication module 21 converts the reception reply information including the unique ID included in the received reception reply information and the judgment result (reception status information) into the unique ID. is transmitted to the portable terminal 8 which is the transmission source of the acceptance application information including (S100). At this time, the terminal communication module 21 can also specify the terminal token stored in correspondence with the unique ID in the terminal information table and transmit the reception reply information. The terminal communication module 21 may transfer the reception/response information received from the electronic medical record system 5 to the mobile terminal 8, or carry information in a different format including the unique ID included in the reception/response information as reception/response information. You may transmit to the terminal 8.

In addition, the support server 1 is stored in the patient management table (terminal information storage unit 20) in association with the unique ID based on the unique ID included in the reception reply information received from the electronic chart system 5. The reception information and reception status are updated with the information contained in the reception reply information. The reception information contained in the reception reply information is set in the reception information stored in the patient management table, and the reception state information (judgment result) contained in the reception reply information is set in the reception state.

When the reception reply information is received by the mobile terminal 8, the reception processing module 92, based on the determination result (reception status information) included in the reception reply information, along with the transmission of the reception application information in (S97). It is determined whether or not the reception has been completed (S101).
If it is determined that the reception has not been completed (S101; NO), the display processing module 94 displays an error message indicating the content of the reception error on the information presentation unit DS based on the reception information included in the reception reply information. (S102). For example, if it is determined that the patient does not have an appointment for that day, an error message such as "Unable to confirm appointment information." has passed." is displayed, and if it is determined that confirmation of the health insurance card is necessary, an error message such as "Confirmation of the health insurance card is required." is displayed. However, the specific contents of such an error message, the acceptance error determination conditions, and the like are not limited at all.

On the other hand, if it is determined that the reception has been completed (S101; YES), the display processing module 94 displays the reception information indicating the completion of reception on the information presentation unit DS based on the reception information included in the reception reply information. (S103). In this case, for example, together with reception information such as reception number, clinical department name, appointment time, patient name, etc., a message indicating reception completion such as "Reception is completed. We will call you with a call message." Is displayed.
As described above, according to the present embodiment, the reception can be automatically performed by the reception operation of the mobile terminal 8 without going to the counter, and the patient (service user) can be relieved of the troublesomeness of the reception. In addition, even when the reception is not possible, the reason can be easily grasped from the displayed error content, which is highly convenient for the patient.

Subsequently, the reception processing module 92 updates the reception information and reception status stored in the patient information table (patient information storage unit 90) based on the received reception reply information (S104). Specifically, the reception processing module 92 identifies the patient information corresponding to the unique ID included in the reception reply information from the patient information table, and determines the reception state of the identified patient information as the determination result included in the reception reply information. (accepted or received error), and updates the reception information to the reception information included in the reception reply information.
As a result, when a plurality of patients (service users) are registered in the mobile terminal 8, whether or not each of the plurality of patients (service users) has been accepted is managed.
When the icon DC1 on the main screen is operated, the patient name and reception status for each of the plurality of patients registered in the mobile terminal 8 may be displayed as a list as a registrant edit menu. In addition, the information of the patient whose reception status is "accepted" may be displayed as a list in the information presentation unit DS. In this way, it becomes possible to easily grasp the patients who have already received the information.

When the reception status of the patient information table (patient information storage unit 90) is updated, the display processing module 94 checks whether the reception status of all the patient information stored in the patient information table has been accepted. Determine (S105). If there is patient information that has not been accepted (S105; NO), the display processing module 94 maintains the acceptance operation unit DU in the active state (END). At this time, the display processing module 94 maintains the display mode of the reception operation unit DU in the display mode corresponding to the active state. color).
On the other hand, when it is determined that all patient information has been accepted (S105; YES), the display processing module 94 deactivates the acceptance operation unit DU. At this time, the display processing module 94 changes the display of the reception operation unit DU to a display mode corresponding to the inactive state, for example, as shown in FIG. is changed from "accepted" to "accepted", and the display color of the acceptance operation unit DU is changed.
FIG. 10B is a diagram showing a display example of the acceptance operation unit DU when all registered patients have been accepted.

However, the display of the reception operation unit DU when all registered patients have been accepted is not limited to the example shown in FIG. 10(b). In this case, the reception operation unit DU may be deleted, the characters "reception" displayed on the reception operation unit DU may be changed to a form that is difficult to see (light gray color), and the outline of the reception operation unit DU may be displayed. may be changed to display in a form that is difficult to see. The display form of the reception operation unit DU changed in (S106) is not limited at all as long as it is a form that allows the user to easily recognize that the reception operation cannot be performed.

Therefore, when all service users corresponding to a plurality of stored user identifiers have entered the accepted state, the portable terminal 8 is changed from the accepting operation enabled state to the accepting operation disabled state. , can be expressed by changing the display mode of the reception operation section.
As a result, a user-friendly user interface can be realized, such as preventing the user of the mobile terminal 8 from performing useless reception operations.

[Action when calling]
Next, an operation example of the support server 1 and the portable terminal 8 when calling a patient will be described with reference to FIG. FIG. 9 is a flow chart showing an operation example of the support server 1 and the portable terminal 8 when calling a patient. As a premise for performing the operation of FIG. 9, it is necessary that the reception of the patient to be called has been completed by the operation of FIG.

At the time of calling, a doctor or the like uses the terminal of the electronic medical record system 5 to designate a patient who has already received a call and performs a calling operation. Along with this, in the support server 1, the relay processing module 22 receives the call instruction from the electronic medical record system 5 (S111). The received call instruction includes the unique ID of the target patient, reception information, a notification message, the identifier of the terminal operated for calling, and the like. As a result, the relay processing module 22 can be rephrased as instruction acquisition means for acquiring a call instruction including a user identifier (unique ID) that can identify a service user (patient).

Based on the unique ID included in the call instruction, the terminal communication module 21 extracts the terminal token associated with the unique ID from the terminal information table (terminal information storage unit 20), and specifies the terminal token. Push notification of call information is performed (S112). As a result, the call information is sent from the support server 1 or via an external server to the mobile terminal 8 corresponding to the designated terminal token. Therefore, based on the user identifier (unique ID) included in the acquired call instruction, the terminal communication module 21 transmits call information including the user identifier to the mobile terminal corresponding to the user identifier. It can be rephrased as transmission means.
The call information to be notified by push preferably includes a part or all of the unique ID and reception information included in the call instruction. In this embodiment, the call information includes a unique ID, reception information and notification message. The call information to be notified by push may be the information itself of the call instruction received from the electronic medical record system 5, or may be information in another format including the unique ID included in the call instruction. .
In addition, the terminal communication module 21 adds the call history (call time, etc.) to the management information of the target patient stored in the patient management table (terminal information storage unit 20) based on the unique ID included in the call instruction. to add.

Upon receiving the push notification of the call information, the mobile terminal 8 outputs the call notification on the home screen or lock screen (S113).
When the call notification is selected by the user along with this output, the display processing module 94 displays the main screen of the application for service users and the call information (S114). The display processing module 94 extracts the patient name associated with the unique ID from the patient information table (patient information storage unit 90) based on the unique ID included in the received call information, and performs a call including the patient name. Information is displayed (S114).
As described above, in this embodiment, the patient ID and patient name, which correspond to personal information, are not exchanged between the electronic medical chart system 5 and the mobile terminal 8, so it is possible to prevent leakage of personal information.

FIG. 10(c) is a diagram showing an example of call information display. In the example of FIG. 10(c), a call information display DP2 is popped up on the main screen. In the call information display DP2, in addition to the notification message "Examination will start soon" and reception information (medical department name, reception number, etc.) included in the call instruction from the electronic medical record system 5, The managed patient name "Patient S" is displayed. However, the call information display may include contents that allow the user of the mobile terminal 8 to identify at least the patient and caller (medical department, etc.) being called, and to recognize that the call is being made. , the specific contents thereof are not limited to the above examples.
Furthermore, in the call information display DP2, confirmation operation indicating that the user of the portable terminal 8 has confirmed the display is possible. In the example of FIG. 10(c), an "OK" button DP3 is displayed. In this way, it is more preferable that the call information display allows a confirmation operation.

When the confirmation operation for the call information display is detected (S115; YES), in the mobile terminal 8, the call processing module 93 transmits confirmation information indicating that the confirmation operation for the call information has been performed to the support server 1 ( S116). This confirmation information includes at least a unique ID corresponding to the patient for whom the call information is intended.

In the support server 1, the terminal communication module 21 receives the confirmation information from the portable terminal 8, and the relay processing module 22 transmits confirmation information including at least the unique ID included in the confirmation information to the electronic medical record system 5 (S117). . At this time, the relay processing module 22 may relay the confirmation information received from the mobile terminal 8 to the electronic medical record system 5, or may electronically transmit the confirmation information in another format including the unique ID included in the received confirmation information. You may transmit to the chart system 5.
Thereby, the electronic medical record system 5 can manage that the called patient has confirmed the call based on the confirmation information.

At this time, the terminal communication module 21 further updates the management information of the target patient stored in the patient management table (terminal information storage unit 20) based on the unique ID included in the confirmation information received from the mobile terminal 8. Add confirmation history (confirmation status, etc.).
As a result, the terminal communication module 21 indicates that the call information confirmation operation has been performed from the portable terminal to which the call information was sent, and the user identifier (unique ID) included in the call information. When the confirmation information is received, the terminal information storage unit 20 stores the user identifier (unique ID) included in the confirmation information and the confirmation operation performed. It can be rephrased as holding means for holding the information in association with the information indicating that.
As described above, according to this embodiment, it is possible to call a patient who has already received a call by a push notification to the mobile terminal 8, and to confirm that the call has been confirmed by the mobile terminal 8. side). As a result, it is possible for the caller to grasp whether the called patient is aware that the call has been made.

[Modification]
The above-described embodiment is an example of a service support system as an embodiment of the present invention. The service support system is not limited to the configuration described above, and may be partially modified as appropriate as long as it has at least a part of the configuration described above.

For example, in the above-described embodiment, the electronic medical record system 5 and the support server 1 are provided separately, but the configuration of the support server 1 may be integrated into the electronic medical record system 5 . When integrated, a patient ID may be exchanged between the electronic medical record system 5 and the mobile terminal 8, or a unique ID converted from the patient ID may be exchanged as in the above-described embodiment. . In the former case, the unique ID is unnecessary.

In the above-described embodiments, the service support system supports the provision of medical services by medical institutions. , amusement parks, theme parks, and other attraction facilities. In this case, the above-mentioned "patient" should be read as the service user, the above-mentioned "electronic medical record system" should be read as the service provider system, and the "doctor, etc." should be read as the service provider's person in charge.
Also, when registering the service user in the portable terminal 8, the registration processing module 91 registers the service user ID by another method instead of (S71), (S72) and (S73) shown in FIG. And you may acquire only a unique ID or a service user ID. For example, the service user ID may be given by the service provider system when the user registers with the service provider system by a general method.

Further, in the above-described embodiment, the support server 1 determines whether or not the mobile terminal 8 is located within the predetermined area based on the location information of the mobile terminal 8 (S92 in FIG. 8). , may be executed by the mobile terminal 8 . In this case, the mobile terminal 8 pre-stores or obtains from the support server 1 information (area information, base position information, etc.) that can determine whether it is within a predetermined area, and uses that information to perform the determination (S92 ).

The contents of the embodiments and modifications described above can also be specified as follows.
(Appendix 1)
A service support method for supporting reception and calling for a service user to receive a target service, which is executed by a server device and a mobile terminal,
the server device or the mobile terminal,
Acquiring location information of the mobile terminal,
determining whether the position information satisfies a predetermined condition;
The mobile terminal
Switching to a reception operation enabled state or a reception operation disabled state according to the result of the determination;
Service support methods, including:
(Appendix 2)
The server device
obtain a call instruction containing a user identifier that can identify a service user;
based on the user identifier included in the acquired call instruction, sending call information including the user identifier to a mobile terminal corresponding to the user identifier;
receiving confirmation information indicating that the confirmation operation of the call information has been performed and including the user identifier included in the call information from the portable terminal to which the call information was sent;
When the confirmation information is received, the user identifier included in the confirmation information and the information indicating that the confirmation operation has been performed are stored in association with each other.
The service support method according to (Appendix 1), further comprising:
(Appendix 3)
The mobile terminal
When an acceptance operation is detected, send acceptance application information including a user identifier that can identify the service user to be accepted,
receiving reception reply information corresponding to the reception application information;
displaying information indicating a reception error or reception completion based on the received reception reply information;
The service support method according to (Appendix 1) or (Appendix 2), further comprising:
(Appendix 4)
The mobile terminal
Holding multiple user identifiers that can identify multiple service users,
outputting a selection display that enables selection of a service user to be accepted from among the plurality of service users;
when the reception operation is detected, transmitting reception application information including the user identifier of the service user selected in the selection display;
managing whether or not each of the plurality of service users is in an accepted state;
The service support method according to (Appendix 3), further comprising:
(Appendix 5)
The mobile terminal
holding the plurality of user identifiers and the plurality of user names in association with each other;
when call information is received, displaying call information including a user name associated with a user identifier included in the received call information;
The service support method according to (Appendix 4), further comprising:
(Appendix 6)
The mobile terminal
Display a reception operation part that enables reception operation by the user,
Triggered by all the service users corresponding to the plurality of held user identifiers being in the accepted state, the state of accepting operation is changed from the state of accepting operation to the state of being unable to accept operation, and the operation is accepted. Change the display mode of the part,
The service support method according to (Appendix 4) or (Appendix 5), further comprising:

1 service support server (support server), 5 electronic medical record system, 8 mobile terminal, 11 CPU, 12 memory, 13 input/output I/F, 14 communication unit, 15 display device, 16 input device, 20 terminal information storage unit, 21 terminal communication module, 22 relay processing module, 23 terminal control module, 81 CPU, 82 memory, 83 display unit, 84 touch sensor, 85 communication unit, 86 imaging unit, 87 microphone unit, 88 speaker unit, 90 patient information storage unit, 91 registration processing module 92 reception processing module 93 call processing module 94 display processing module

Claims (8)

A support server that supports reception and calling for a patient to receive a medical examination at a target medical institution ,
a terminal information table that associates and stores a unique ID that can identify a patient and a terminal token of the patient's portable terminal;
a patient management table that stores a unique ID, reception information, and call confirmation history for each patient;
a position acquisition means for acquiring position information of the patient's mobile terminal;
terminal control means for determining whether or not the position information satisfies a predetermined condition, and controlling the portable terminal of the patient to switch between a reception operable state and a reception operable state according to the result of the determination;
an instruction acquiring means for acquiring a calling instruction including a unique ID of a patient who has been accepted in response to a call operation specifying a patient who has been accepted to a terminal of the electronic medical record system;
call transmission means for designating a terminal token stored in the terminal information table in association with the unique ID included in the acquired call instruction, and performing push notification of call information including the unique ID;
In accordance with the user's confirmation operation on the call information display including the patient name, reception information and notification message displayed on the mobile terminal of the accepted patient who has received the push notification of the call information, the call information is sent from the mobile terminal confirmation receiving means for receiving confirmation information indicating that the confirmation operation of has been performed and including the unique ID of the accepted patient;
In response to the push notification of the call information and the reception of the confirmation information, the call history and the confirmation history are added to the call confirmation history stored in the patient management table in association with the unique ID of the accepted patient. additional retention means;
means for transmitting confirmation information including a unique ID of the accepted patient to the electronic medical record system upon receipt of the confirmation information from the mobile terminal of the accepted patient;
A support server comprising: Means for receiving a registration request including the unique ID and the terminal token of the mobile terminal from the mobile terminal that has acquired the patient ID acquired from the patient registration card of the patient to be registered and the unique ID generated corresponding to the patient ID. and,
means for associating a unique ID and a terminal token included in the received registration request and additionally storing them in the terminal information table;
means for additionally storing patient information including a unique ID included in the received registration request in the patient management table;
means for receiving a test call request including the unique ID from the mobile terminal;
means for, based on the unique ID included in the received test call request, designating a terminal token stored in the terminal information table in association with the unique ID and performing push notification of test call information;
further comprising
The electronic medical record system and the mobile terminal of each patient hold the patient ID of each patient and the unique ID of each patient in association with each other, while the support server does not hold the patient ID.
A support server according to claim 1 . A computer program for patients that can be executed on the mobile terminal that can communicate with the support server according to claim 1 or 2,
on the mobile terminal,
switching to the reception operation enabled state or the reception operation disabled state based on information sent from the support server ;
When the reception operation is detected, transmitting reception application information including the unique ID of the patient to be received to the support server ;
receive reception reply information corresponding to the reception application information from the support server ;
when the received reception reply information indicates a reception error , displaying information indicating error details ; when the received reception reply information indicates reception completion, displaying information indicating reception completion;
In response to a push notification of the call information from the support server, display the call information including the name of the accepted patient, reception information and a notification message so that confirmation operation is possible,
When a user's confirmation operation on the display of the call information is detected, confirmation information indicating that the confirmation operation of the call information has been performed and including the unique ID of the accepted patient is transmitted to the support server.
A computer program for patients . The mobile terminal further
A unique ID and a patient name for each of a plurality of patients are associated with each other and held;
outputting a selection display that enables selection of a patient to be accepted from among the plurality of patients ;
When the reception operation is detected, transmitting reception application information including the unique ID of the patient selected in the selection display to the support server ;
managing whether or not each of the plurality of patients is in an accepted state ;
When a push notification of the call information is received from the support server, the patient name held in association with the unique ID included in the call information is included in the display of the call information as the name of the accepted patient,
Displaying one reception operation unit that enables reception operation by the user,
When all of the plurality of patients whose unique IDs are held are in the reception completed state, the reception operation enabled state is changed to the reception operation disabled state, and the one reception operation unit is displayed. change the mode,
4. A patient computer program according to claim 3 . A patient computer program executable on the mobile terminal communicable with the support server of claim 2,
on the mobile terminal,
Hold the patient information table,
Acquiring a patient ID from a patient registration card and generating a unique ID corresponding to the patient ID by scanning a two-dimensional code displayed by a registration terminal to acquire the patient ID and the unique ID,
displaying an input screen for the name of the patient to be registered corresponding to the acquired patient ID;
adding patient information including the name of the patient to be registered input to the input screen, the acquired patient ID and unique ID to the patient information table;
causing a registration request not including the obtained patient ID and including the obtained unique ID and a terminal token of the mobile terminal itself to be transmitted to the support server;
When a test call operation is detected, causing a test call request not including the obtained patient ID and including the obtained unique ID to be sent to the support server;
A computer program for patients. A service support method for supporting reception and calling for a patient to receive a medical examination at a target medical institution , which is executed by a server device and a mobile terminal,
The server device includes a terminal information table that stores a unique ID that can identify a patient and a terminal token of the patient's portable terminal in association with each other, and a patient information table that stores a unique ID, reception information, and call confirmation history for each patient. It has a management table and
the server device or the mobile terminal,
Acquiring location information of the mobile terminal,
determining whether the position information satisfies a predetermined condition;
The mobile terminal
Switching to a reception operation possible state or a reception operation impossible state according to the result of the determination,
The server device
Acquiring a call instruction including a unique ID of the accepted patient in response to a calling operation specifying the accepted patient to the terminal of the electronic medical record system,
Designating a terminal token stored in the terminal information table in association with the unique ID included in the acquired call instruction, and performing a push notification of call information including the unique ID;
The mobile terminal
receiving a push notification of the call information from the server device, displaying the call information including the name of the accepted patient, the reception information and the notification message so that confirmation operation is possible;
when a user's confirmation operation on the display of the call information is detected, confirmation information indicating that the confirmation operation of the call information has been performed and including the unique ID of the accepted patient is transmitted to the server device;
The server device
receiving said confirmation information;
In response to the push notification of the call information and the reception of the confirmation information, the call history and the confirmation history are added to the call confirmation history stored in the patient management table in association with the unique ID of the accepted patient. adding and sending confirmation information including the unique ID of the accepted patient to the electronic medical record system;
Service support methods, including : The mobile terminal
A patient ID and a unique ID are acquired by scanning a two-dimensional code displayed by a registration terminal that acquires a patient ID from a patient ID card of a patient to be registered and generates a unique ID corresponding to the patient ID,
displaying an input screen for the name of the patient to be registered corresponding to the acquired patient ID;
adding patient information including the name of the patient to be registered input to the input screen, the acquired patient ID and unique ID to a patient information table;
transmitting to the server device a registration request that does not include the obtained patient ID and includes the obtained unique ID and a terminal token of the mobile terminal itself;
The server device
receiving from the mobile terminal the registration request that does not include the patient ID of the patient to be registered but includes the unique ID of the patient to be registered and a terminal token of the mobile terminal itself;
associate a unique ID and a terminal token included in the received registration request and additionally store them in the terminal information table;
additionally storing patient information including the unique ID included in the received registration request in the patient management table;
The mobile terminal
when a test call operation is detected, sending a test call request that does not include the patient ID and includes the unique ID to the server device;
The server device
receiving a test call request including the unique ID from the mobile terminal;
Based on the unique ID included in the received test call request, specifying a terminal token stored in the terminal information table in association with the unique ID to perform push notification of test call information;
7. The service support method according to claim 6, comprising: The mobile terminal holds a unique ID and a patient name associated with each of a plurality of patients, and
The mobile terminal
Displaying one reception operation part that enables reception operation by the user,
outputting a selection display that enables selection of a patient to be accepted from among the plurality of patients;
when an acceptance operation for the one acceptance operation unit is detected, sending acceptance application information including a unique ID of the patient selected in the selection display to the server device ;
The server device
transmitting reception response information corresponding to the reception application information to the mobile terminal;
The mobile terminal
receiving the reception reply information from the server device ;
managing whether or not each of the plurality of patients is in an accepted state based on the received acceptance reply information;
when the received reception reply information indicates a reception error, displaying information indicating error details; when the received reception reply information indicates reception completion, displaying information indicating reception completion;
Triggered by all of the plurality of patients holding unique IDs entering the reception completed state, the reception operation enabled state transitions to the reception operation disabled state, and the one reception operation unit is displayed. change the mode,
8. The service support method according to claim 6 or 7, further comprising:

Images