JP7131164B2 - Hospital reservation system and server device - Google Patents

Description

The present invention relates to a hospital reservation system and server device.

For example, Patent Literature 1 proposes a technology that enables a patient to select an appropriate doctor for treatment of his or her disease based on evaluations of each of a plurality of doctors.

JP 2017-21641 A

In Patent Literature 1, a doctor's evaluation involves presenting information about the doctor to a plurality of other doctors, and the other doctors evaluate based on this information, which tends to be a subjective evaluation. It is not possible to present to the user candidates of doctors suitable for the user or hospitals to which the doctors belong based on objective indices, and the user to select and make a reservation from among them.

The present invention has been made in view of the above circumstances, and its object is to be able to present suitable hospital or doctor candidates to the user based on objective indicators, and to make a hospital reservation according to the user's selection. To provide a hospital reservation system and a server device that can

The present invention adopts the following configurations in order to solve the above-described problems.

In one aspect of the present disclosure, the hospital reservation system includes at least patient information about patients, reception date and time, medical treatment start date and time, medical treatment end date and time, medical doctor, and accounting end date and time for each medical treatment at each of a plurality of hospitals. an electronic medical record network for sharing an electronic medical record for each patient among the plurality of hospitals, and an electronic medical record collection unit for collecting the contents of the electronic medical records from the electronic medical record network; a biometric data collection unit that collects biometric data of each of a plurality of users via a communication network; a reception unit that receives a request from a user terminal via the communication network; and an evaluation from the user terminal by the reception unit When the request and the biometric data of the user of the user terminal are received, the biometric data of the user of the user terminal that requested the evaluation request received by the receiving unit and the biometric data collected by the biometric data collection unit a limiting unit for limiting evaluation targets from among the plurality of hospitals or a plurality of doctors belonging to the plurality of hospitals based on the biometric data; and description contents of the electronic medical chart collected by the electronic medical chart collection unit an evaluation unit that evaluates the plurality of hospitals or doctors limited as the evaluation targets by the limiting unit by evaluation items including at least consultation time and waiting time per patient, and an evaluation result by the evaluation unit a presenting unit that presents at least one of the plurality of hospitals or doctors evaluated as a reservation candidate, via the communication network, to the user terminal that is the source of the request, and to each of the plurality of hospitals a hospital control unit that manages reservations for patients; When received from the user terminal, a request is made, via the communication network, to the hospital control unit of the hospital corresponding to the hospital or doctor accepted by the reception unit to make an appointment for the user of the user terminal that is the request source. and a reservation unit for
A hospital is a hospital group that includes a small hospital with a single room in a building, a large hospital with multiple wards on one site, and affiliated hospitals distributed in multiple regions. can be In the case of a hospital group, electronic medical records may be distributed among hospitals within the group. Also, the electronic medical record may be located in a data center provided within the electronic medical record network instead of in the hospital. Here, arrangement includes being stored in a storage unit provided with a storage medium. The data format of electronic medical charts may be different for each hospital, and the electronic medical charts of each hospital can be converted into a unified format within the electronic medical chart network and stored in the storage unit of the data center. Confidentiality is ensured by data encryption or the like in the transmission and reception of electronic medical records between each hospital and the data center. Within the electronic medical record network, restricted access rights are given to each medical staff, and it is possible to view and update information in electronic medical records located at the hospital or data center from a medical terminal operated by each medical staff. It has become. In addition, within the electronic medical record network, restricted access rights are given to each user who is a patient, and it is now possible for each user to view information in his/her own electronic medical record located in the data center from a user terminal operated by the user. in some cases. In this case as well, it is desirable to ensure confidentiality by means of data encryption or the like in data transmission/reception between the user terminal and the data center.
According to the hospital reservation system configured as described above, in response to an evaluation request from an arbitrary user terminal, a limited hospital or doctor is selected based on the biological data of the user of the user terminal and the collected biological data of a plurality of users. Evaluation is performed using an objective index of time, and based on the evaluation results, appointment candidates are presented to the user, and a hospital reservation is made according to the selection of the user of the user terminal that requested the evaluation. By presenting candidate hospitals or doctors suitable for the user, the user can easily select a hospital and can easily make a reservation for the hospital according to the selection.

In the above aspect, the evaluation unit calculates an evaluation value representing evaluation results of the plurality of hospitals or doctors, and the presentation unit selects a plurality of hospitals or doctors in descending order of evaluation values calculated by the evaluation unit. A doctor may be extracted as the appointment candidate, and the extracted appointment candidate may be presented to the requesting user terminal together with its evaluation value.
According to this configuration, by using numerical values called evaluation values, it is possible to sort in the order of evaluation values, and it is possible to easily present reservation candidates suitable for the user.

In the aspect described above, the hospital reservation system further includes a correspondence database in which hospitals or doctors are databased according to attributes of the biometric data collected by the biometric data collection unit, and the limiting unit receives the request The plurality of hospitals or doctors to be evaluated may be limited by referring to the correspondence database according to the attributes of the biometric data of the user of the original user terminal.
According to this configuration, by using the database, it is possible to easily and quickly limit hospitals or doctors to be evaluated.

In the aspect described above, the biometric data collection unit can receive, via the communication network, the biometric data of the user transmitted from each of a plurality of user terminals each collecting the biometric data of the user.
According to this configuration, biometric data can be easily collected by collecting biometric data from each user terminal of a user who subscribes to the hospital reservation service.

In the aspect described above, the biometric data collection unit collects biometric data histories of each of the plurality of users, and the evaluation items evaluated by the evaluation unit include the biometric data collected by the biometric data collection unit. It can include the degree of improvement in symptoms based on historical data over time.
According to this configuration, it is possible to provide more suitable candidates for the user by adding an evaluation based on the degree of symptom improvement, that is, the degree of symptom improvement.

In the above aspect, the evaluation unit converts the evaluation results for each evaluation item into points, sets the total points as the evaluation value for doctors, and sets the average value of the evaluation values of doctors belonging to the hospital as the evaluation value for hospitals. The presenting unit extracts a plurality of hospitals or doctors from the highest evaluation value calculated by the evaluation unit as the appointment candidate, and sends the extracted appointment candidate together with the evaluation value to the user terminal of the request source. can be presented.
According to this configuration, by using scored evaluation values and presenting appointment candidates along with their numerical values, it is possible to provide an index for the user to select a hospital to make an appointment with, thereby facilitating the user's selection. becomes possible.

In the above aspect, the hospital reservation system further includes a doctor attribute acquisition unit that acquires releasable doctor attribute information including at least gender and age for each doctor belonging to each hospital, and the reception unit is Furthermore, the evaluation items to be evaluated by the evaluation unit are the attribute information of the doctor acquired by the doctor attribute acquisition unit and the reception unit. may include a relationship with the attribute information of the user of the user terminal of the request source received by.
According to this configuration, the evaluation is performed based on the gender or age of the user whose evaluation value is to be presented and the gender or age of the doctor. can be made a candidate.

In the above aspect, the reception unit further receives location information from the requesting user terminal, and the limiting unit receives the location information from the requesting user terminal received by the reception unit. based on, the plurality of hospitals or doctors to be evaluated are limited, and the evaluation items evaluated by the evaluation unit are further the position information received by the reception unit from the user terminal of the request source and , with the location of the hospital being evaluated.
According to this configuration, by limiting the hospitals that the user can visit according to the current position of the user who requested the evaluation or the specified position specified by the user, the possibility of presenting the user with inappropriate hospitals as candidates is reduced. can be made smaller.

In the above aspect, the hospital control unit further performs time management of the patient during his/her stay at the hospital, and the evaluation unit accesses the hospital control unit to obtain at least current information of each hospital. The number of patients waiting for medical treatment and the number of patients with future appointments are acquired, and the evaluation items evaluated by the evaluation unit can further include the acquired number of patients waiting for medical treatment and the number of patients with appointments.
According to this configuration, it is possible to present candidates for hospitals or doctors in consideration of the current waiting time of each hospital.

In another aspect of the present disclosure, the server device stores at least patient information about the patient, reception date and time, medical treatment start date and time, medical treatment end date and time, medical doctor, and accounting end date and time for each medical treatment at each of the plurality of hospitals. an electronic medical record collection unit for collecting the contents of the electronic medical records from the electronic medical record network for sharing the electronic medical records for each patient among the plurality of hospitals, and a communication network; a biometric data collection unit that collects biometric data of each of a plurality of users via the communication network; a reception unit that receives a request from a user terminal via the communication network; When the biometric data of the user is accepted, the biometric data of the user of the user terminal that requested the evaluation request accepted by the accepting unit and the biometric data collected by the biometric data collecting unit Based on the description contents of the electronic medical charts collected by the limiting unit for limiting evaluation targets from the plurality of hospitals or the plurality of doctors belonging to the plurality of hospitals, and the electronic medical chart collection unit, at least An evaluation unit that evaluates the plurality of hospitals or doctors limited as the evaluation targets by the limiting unit by evaluation items including consultation time and waiting time per patient; a presenting unit configured to present at least one of the evaluated hospitals or doctors as an appointment candidate to the requesting user terminal via the communication network; a hospital control provided in each of the plurality of hospitals for managing patient appointments when an appointment request for a hospital or a doctor selected by the user is received from the requesting user terminal via the communication network; a reservation unit for requesting, through the communication network, the hospital control unit of the hospital corresponding to the hospital or doctor accepted by the reception unit to make a reservation for the user of the user terminal of the request source; ,
According to this configuration, in response to an evaluation request from an arbitrary user terminal, the server device selects a limited hospital or doctor based on the biological data of the user of the user terminal and the collected biological data of a plurality of users. Then, an appointment candidate based on the evaluation result is sent to the user terminal that requested the evaluation and presented to the user. , to present candidates of hospitals or doctors suitable for the user based on objective indicators, so that the user can easily select a hospital and easily make a reservation for the hospital according to the selection. become.

ADVANTAGE OF THE INVENTION According to this invention, the technique which can present the candidate of a hospital or a doctor suitable for a user based on an objective index, and can make a hospital reservation according to a user's selection can be provided.

FIG. 1 is a block diagram that schematically illustrates an example of the configuration of a hospital reservation system according to an embodiment. FIG. 2 is a block diagram showing an example of the overall configuration of the hospital reservation system according to the first embodiment. FIG. 3 is a diagram showing an example of contents stored in a hospital database. FIG. 4 is a diagram showing an example of contents stored in a user database. FIG. 5 is a diagram showing an example of contents stored in a correspondence database. FIG. 6 is a diagram showing an example of the contents of the collection database. FIG. 7 is a diagram showing an example of contents stored in an evaluation database. FIG. 8 is a flowchart illustrating an example of a processing procedure of a service server; FIG. 9 is a flowchart illustrating an example of a processing procedure of a user terminal; FIG. 10 is a flowchart illustrating an example of evaluation processing in FIG. FIG. 11 is a flowchart illustrating an example of electronic medical record collection processing in FIG. FIG. 12 is a flowchart illustrating an example of evaluation calculation processing in FIG. FIG. 13 is a diagram for explaining an example of biometric data history. FIG. 14 is a diagram for explaining another example of biometric data history. FIG. 15 is a flowchart illustrating an example of a processing procedure of a service server in the hospital reservation system according to the second embodiment; FIG. 16 is a flowchart illustrating an example of electronic medical record collection processing in FIG. FIG. 17 is a flowchart illustrating an example of the number-of-persons collection process in FIG. FIG. 18 is a flowchart illustrating an example of a processing procedure of a service server in the hospital reservation system according to the third embodiment; 19 is a flowchart illustrating an example of the first evaluation calculation process in FIG. 18. FIG. 20 is a flowchart illustrating an example of the second evaluation calculation process in FIG. 18. FIG.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described based on the drawings.

[Application example]
First, with reference to FIG. 1, an example of a scene to which the present invention is applied will be described. FIG. 1 schematically illustrates an example of the configuration of a hospital reservation system according to an embodiment.

[Configuration of application example]
In the example of FIG. 1, the hospital reservation system includes an electronic medical record network (EHR: Electronic Health Records) 1 and a service server 10, each connected to a communication network NET such as the Internet. The service server 10 can be connected to multiple user terminals 20 via the communication network NET.

The electronic medical record network 1 stores at least patient information about each patient, and medical information regarding each medical treatment, including the reception date and time, the medical treatment start date and time, the medical treatment end date and time, the treating doctor, and the accounting end date and time. It is a network for sharing the described electronic medical records (EMR: Electronic Medical Records) for each patient among a plurality of hospitals. The electronic medical chart network 1 is configured by connecting, for example, a hospital server 30 provided in each of a plurality of hospitals and a data server 40 provided in a data center via a communication network NET. The electronic medical chart network 1 may use a dedicated communication line instead of the Internet as the communication network NET. However, the data server 40 must have a configuration that allows the service server 10 to access the data server 40 via the communication network NET.

The hospital server 30 of each hospital can have, for example, a control unit 31, a storage unit 32 connected to the control unit 31, and a communication interface (not shown). In addition, the hospital server 30 includes, for example, personal computers (PCs) operated by medical personnel such as doctors, nurses, laboratory technicians, and clerks in the hospital, automatic reception machines and automatic accounting machines operated by patients visiting the hospital. , are connected via a hospital LAN (Local Area Network) or the like. The intra-hospital LAN may be a wired LAN, a wireless LAN, or a mixed wired and wireless LAN. Although not shown, the hospital server 30 includes a biological data measuring device for measuring biological data such as a patient's blood pressure value, a CT (computerized tomography) device for capturing an internal image of the patient, and the like. Various examination equipment including equipment, etc. can also be connected via the hospital LAN or the like.

A hospital is a group of hospitals that includes small-scale hospitals with a single room in a building, large-scale hospitals with multiple wards on one site, and affiliated hospitals distributed in multiple regions. good. In the case of a hospital group, a hospital server 30 may be arranged for each hospital in the group, or one hospital server 30 may be arranged in one main hospital, and medical terminals 33 of each affiliated hospital may be connected via a dedicated communication line or the like. may be connected to the hospital server 30 via Alternatively, only the control unit 31 of the hospital server 30 may be provided for each hospital in the group, and the storage unit 32 may be arranged only in the hospital server 30 of one main hospital.

Although not shown, the control unit 31 in the hospital server 30 includes, for example, a processor such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit) and a memory such as a RAM (Random Access Memory) or a ROM (Read Only Memory). and can include The ROM stores, for example, programs executed by the processor. A RAM is, for example, a memory used as a work memory by a processor. The controller 31 can perform various operations by causing the processor to execute necessary programs.

The storage unit 32 can store, for example, programs executed by the processor of the control unit 31, setting data necessary for executing the programs, and various databases. The programs executed by the processor of the control unit 31 include, for example, an electronic medical chart management program for viewing and updating electronic medical charts, a reservation management program for managing patient reservations, reception hours for each patient staying at the hospital, and the like. A time management program to manage, etc. can be included. The setting data necessary for executing the program can include, for example, the access address of the data server 40 of the data center. The database includes, for example, a medical staff database that stores each medical staff information including the authority and password of the medical staff who operates the medical terminal 33, an electronic medical record database that stores each patient's electronic medical record (EMR), a reservation can include a reservation database that stores status, and the like. Note that the storage unit 32 of each hospital does not necessarily store all of the programs, setting data, and databases as described above, and stores programs, setting data, and databases other than those described above. Also good. The storage medium included in the storage unit 32 stores information such as programs by electrical, magnetic, optical, mechanical or chemical action so that information such as programs recorded by computers, machines, etc. can be read. Any medium can be used as long as it is stored by For example, the storage medium included in the storage unit 32 can be EEPROM (registered trademark) (Electrically Erasable, Programmable Read-Only Memory) or the like. The storage unit 32 may also be used by the processor of the control unit 31 as a work memory.

The processor of the control unit 31 executes, for example, an electronic medical record management program stored in the storage unit 32 to update the contents of the electronic medical records stored in the storage unit 32 according to the operation of each medical terminal 33. It can be displayed on the medical terminal 33 and can update the contents of the electronic chart. In addition, the processor of the control unit 31 can add, for example, examination data from an examination device (not shown) to the electronic medical record. Furthermore, the processor of the control unit 31 can communicate with the data server 40 via a communication network NET or a dedicated communication line, for example, using a communication interface (not shown). Communication through the communication interface is not limited to a specific communication method. However, in communication with the data server 40, it is necessary to secure confidentiality by data encryption or the like. The processor of the control unit 31 can, for example, transmit the electronic medical record stored in the storage unit 32 to the data server 40 of the data center. In this case, the processor of the control unit 31 can convert the electronic medical chart into a data format common to the electronic medical chart network 1, encrypt it, for example, and then transmit it. Conversely, the processor of the control unit 31 receives from the data server 40 an electronic medical chart created in another hospital and stored in the data server 40 in a common format, for example, decrypts it, After changing to the medical chart format, it can be registered in the electronic medical chart database of the storage unit 32 .

In addition, the processor of the control unit 31 executes, for example, a reservation management program stored in the storage unit 32 to receive a reservation from the medical terminal 33 or a request from the service server 10 or the user terminal 20 via the communication network NET. Reservations can be accepted and the reservation database can be updated with current affairs.

Further, the processor of the control unit 31 executes the time management program stored in the storage unit 32, for example, to acquire the reception date and time, the start date and time of the medical care, the end date and time of the medical care, the treating doctor, and the accounting end date and time of each patient. By doing so, it is also possible to manage the time of each patient during his/her stay in the current affairs of the hospital. The processor of the control unit 31 executes the electronic medical record management program, for example, to obtain medical information including the reception date and time of each patient, the medical treatment start date and time, the medical treatment end date and time, the medical doctor, and the accounting end date and time. can be entered in each patient's electronic medical record.

The data server 40 of the data center can have, for example, a control unit 41, a storage unit 42 connected to the control unit 41, and a communication interface (not shown). Although not shown, the control unit 41 can include, for example, processors such as a CPU and MPU, and memories such as a RAM and a ROM. The ROM stores, for example, programs executed by the processor. A RAM is, for example, a memory used as a work memory by a processor. The controller 41 can perform various operations by causing the processor to execute necessary programs.

The storage unit 42 can store, for example, programs executed by the processor of the control unit 41, setting data necessary for executing the programs, and various databases. Programs executed by the processor of the control unit 41 include, for example, an electronic medical chart processing program for processing electronic medical charts transmitted from each hospital server 30 via the communication network NET or a dedicated communication line, the service server 10, and user terminals. 20 and communication programs for transmission, and the like. The database includes, for example, an access authority database that stores the authority and password of the medical staff who operates the medical terminal 33 and the user who operates the user terminal 20, the authority of the service server 10, and the electronic data of each patient received from the hospital server 30. An electronic medical record database that stores medical records (EMRs) can be included, and the like. Note that the storage unit 42 may store programs and databases other than those described above. The storage medium provided in the storage unit 42 stores information such as programs by electrical, magnetic, optical, mechanical or chemical action so that the information such as programs recorded can be read by a computer, machine, or the like. Any medium can be used as long as it is stored by For example, an EEPROM or the like can be used as the storage medium included in the storage unit 42 . The storage unit 42 may also be used by the processor of the control unit 41 as a work memory.

The processor of the control unit 41 communicates with each hospital server 30 via a communication network NET or a dedicated communication line by executing an electronic medical record processing program stored in the storage unit 42, for example, and executes each hospital server. For example, the encrypted electronic medical chart transmitted from 30 can be decrypted and registered in the electronic medical chart database of the storage unit 42 . Conversely, in response to a request from the hospital server 30 of each hospital, the processor of the control unit 41 encrypts, for example, electronic medical records stored in the electronic medical record database of the storage unit 42 in a common format, It can be sent to the hospital server 30 .

In addition, in the example of FIG. 1, in hospital C, the storage unit 32 of the hospital server 30 does not have an electronic medical record database. In the hospital server 30 having such a configuration, the electronic medical charts stored in the storage unit 42 of the data server 40 can be virtually used as the electronic medical charts that the hospital server 30 of the hospital C has. Therefore, the processor of the control unit 41, for example, by executing the electronic medical chart processing program stored in the storage unit 42, through the communication network NET or a dedicated communication line and the hospital server 30 of the hospital C, medical By acquiring operation information from the terminal 33, it is possible to process electronic medical charts. Also, the processor of the control unit 41 can communicate with the service server 10 or the user terminal 20 via the communication network NET by executing a communication program stored in the storage unit 42, for example.

As described above, it is not possible for the control unit 31 of the hospital server 30 to convert the electronic medical chart in the unique data format stored in the storage unit 32 into the common data format of the electronic medical chart network 1 and then transmit it. Not required. From the hospital server 30 of each hospital, an electronic medical record in a unique data format may be encrypted, for example, and transmitted to the data center. In this case, in the control unit 41 of the data server 40 that has received it, the received electronic medical chart is decrypted, for example, converted into a data format common to the electronic medical chart network 1, and stored in the storage unit 42. It should be stored in the database. Conversely, when transmitting an electronic medical chart to the hospital server 30 of each hospital, the control unit 41 of the data server 40 converts the electronic medical chart in a common data format into a data format unique to each hospital, for example, It should be encrypted and sent.

Within the electronic medical record network 1, each medical staff is given restricted access authority, and each medical staff can access the storage section 32 of the hospital server 30 of their own hospital to which access is permitted or the data from the medical terminal 33. The information of the electronic medical records stored in the storage unit 42 of the data server 40 of the center can be browsed. Moreover, each medical staff can update electronic medical charts from the medical terminal 33 if authorized.

The user terminal 20 may be a smart device such as a general smart phone (smartphone) or a tablet-type terminal having a connection function to the communication network NET. The user terminal 20 has, for example, a control unit 21, a measurement unit 22 and a storage unit 23 connected to the control unit 21, a communication interface for connecting to a communication network NET (not shown), and a user interface. can be done. Also, the user terminal 20 can be connected to a biometric data measuring device 24 . The communication interface can include, for example, a Wi-Fi® module. For example, the communication interface is connected to a communication network NET such as the Internet via a Wi-Fi base station (not shown), and communicates with the service server 10 and the data server 40 of the electronic medical record network 1 via the communication network NET. be able to. The user interface includes a liquid crystal display, a touch panel arranged on the display screen, and operation buttons provided on the housing of the smart device.

Although not shown, the control unit 21 in the user terminal 20 can include, for example, processors such as CPU and MPU, and memories such as RAM and ROM. The ROM stores, for example, programs executed by the processor. A RAM is, for example, a memory used as a work memory by a processor.

The measurement unit 22 measures various biological data of the user. For example, the measurement unit 22 can measure the pulse rate using a camera and an LED flashlight that are generally provided in smart devices as a PPG (Photo Plethysmography) sensor. Smart devices are also known that can measure blood pressure by adding a pressure sensor.

The biological data measuring device 24 is a device capable of measuring one or a plurality of various biological data such as electrocardiogram, pulse, blood pressure, weight, and body fat percentage. The biological data measuring device 24 performs short-range wireless communication with the control unit 21 of the user terminal 20, for example. For example, the user terminal 20 and the biometric data measuring device 24 can each have a BLE communication module that employs a short-range wireless data communication standard such as Bluetooth (registered trademark), but is not limited to this. Also, the biological data measuring device 24 and the control unit 21 of the user terminal 20 may be connected by wire.

The storage unit 23 stores a web browser and various application programs (smartphone apps). By the processor executing programs stored in the ROM or the storage unit 23, the control unit 21 can perform various operations. For example, the control unit 21 can access the service server 10 using a smartphone application, a web browser, or the like. In addition, within the electronic medical record network 1, restricted access rights are given to each user who is a patient. In some cases, it is possible to view information in electronic medical records that are authorized by The user terminal 20 may have a GPS (Global Positioning System) receiver. The user terminal 20 can use the position information of the user terminal acquired by the GPS receiver or the Wi-Fi module in the smartphone application, and can transmit it to the service server 10 or the like via the communication network NET as necessary. It's becoming

In addition, the storage unit 23 can accumulate the user's biological data acquired by the measuring unit 22 and the biological data measuring device 24 as PHR (Personal Health Records). In other words, the user of the user terminal 20 can save medical/health records managed by himself/herself in the storage unit 23 for a certain period of time or more.

The service server 10 operating as a server device, although not particularly illustrated, can have, for example, a control unit, a storage unit connected to the control unit, and a communication interface for connecting to the communication network NET. . The communication interface can communicate with the user terminal 20, the data server 40 of the electronic medical record network 1, and the hospital server 30 via the communication network NET. Communication through the communication interface is not limited to a specific communication method. The control unit can include, for example, a processor such as CPU and MPU, and memory such as RAM and ROM. The ROM stores, for example, programs executed by the processor. A RAM is, for example, a memory used as a work memory by a processor. By executing the program required by the processor, the control unit is configured to operate the electronic medical chart collection unit 11, the biometric data collection unit 12, the reception unit 13, the limitation unit 14, the evaluation unit 15, the presentation unit 16, the reservation unit 17, the correspondence database 18, and the operation of the doctor attribute acquisition unit 19 can be performed.

The electronic medical record collection unit 11, for example, accesses the data server 40 of the data center in the electronic medical record network 1 via the communication network NET, and collects the description contents of the electronic medical records of each hospital stored in the storage unit 42. can be done. For example, the electronic medical record collection unit 11 requests the control unit 41 of the data server 40 to transmit the electronic medical record descriptions, and receives the electronic medical charts transmitted from the data server 40 to obtain the electronic medical chart descriptions. collect.

The biometric data collection unit 12 can collect biometric data accumulated in the storage unit 23 of each user terminal 20 via the communication network NET, for example. For example, every time biometric data is acquired by the measurement unit 22 or the biometric data measurement device 24 in the user terminal 20, the biodata collection unit 12 transmits the acquired biodata from the user terminal 20 to the service server 10. , the biometric data stored in the storage unit 23 of each user terminal 20 can be collected. Alternatively, the biological data collection unit 12 requests the control unit 21 of each user terminal 20 to transmit the biological data for at least a certain period of time stored in the storage unit 23, and the biological data transmitted from each user terminal 20 for at least a certain period of time. It is also possible to collect the biometric data by receiving the biometric data from the device.

The reception unit 13 receives a request from the user terminal 20 via the communication network NET, for example. Requests received by the receiving unit 13 can include an evaluation request requesting the presentation of hospital candidates and a hospital appointment request requesting an appointment with a hospital. When transmitting the evaluation request to the service server 10, the control unit 21 of the user terminal 20 can also transmit information necessary for the evaluation operation in the service server 10, such as position information. At this time, the latest biometric data stored as PHR in the storage unit 23 may also be transmitted. However, this is not always necessary because the biometric data is transmitted from the user terminal 20 to the service server 10 each time the user terminal 20 acquires biometric data. The hospital appointment request also includes information indicating the hospital or doctor requesting the appointment.

For example, when the receiving unit 13 receives an evaluation request from the user terminal 20 and the biometric data of the user of the user terminal 20 via the communication network NET, the limiting unit 14 limits evaluation targets to be evaluated. For example, based on the biometric data of the user of the user terminal 20 that requested the evaluation request, and the biometric data collected from a plurality of users by the biometric data collection unit 12, the limiting unit 14 may select a plurality of hospitals or a plurality of Evaluation targets to be evaluated can be limited from among a plurality of doctors belonging to the hospital.

The evaluation unit 15 determines, for example, a plurality of hospitals or doctors limited as evaluation targets by the limiting unit 14 based on the contents of the electronic medical records collected by the electronic medical record collecting unit 11, and at least the treatment time and waiting time per patient. Evaluate by evaluation items including time. For example, the treatment time is the time from the start of the patient's treatment to the end of the treatment, and the waiting time is the total of the time from the reception of the patient to the start of the treatment and the time from the end of the treatment to the end of accounting.

For example, based on the evaluation result by the evaluation unit 15, the presentation unit 16 selects at least one of a plurality of evaluated hospitals or doctors as a reservation candidate, and sends it to the user terminal 20 that requested the evaluation via the communication network NET. By transmitting, it is possible to cause the user terminal 20 to present reservation candidates.

For example, the reservation unit 17 receives a hospital reservation request for a hospital or a doctor selected by the user from among the presented reservation candidates from the user terminal 20 that requested the evaluation via the communication network NET by the reception unit 13. When the user is requested to make an appointment, the hospital is requested to make the reservation. For example, the reservation unit 17 sends the hospital server 30 of the hospital indicated by the hospital reservation request or the hospital server 30 via the communication network NET to the control unit 31 that operates as a hospital control unit that manages patient reservations. It is possible to request the reservation of the user of the user terminal 20 who is the reservation requester, that is, the evaluation requester.

The correspondence database 18 is, for example, a database of hospitals or doctors according to attributes of biometric data collected by the biometric data collection unit 12 . The limiting unit 14 can refer to the correspondence database 18 according to the attributes of the biometric data of the user of the user terminal 20 who requested the evaluation, and limit the plurality of hospitals or doctors to be evaluated.

The doctor attribute acquisition unit 19 can acquire, for example, publicly available doctor attribute information including at least gender and age for each doctor belonging to each hospital. Although not shown, the data server 40 has a database in which doctor attribute information of doctors belonging to each hospital is registered. , is updated every time there is a change in the doctor to which he belongs. Therefore, the doctor attribute acquisition unit 19 can acquire doctor attribute information from the control unit 41 of the data server 40 via the communication network NET, for example. In addition, many hospitals provide web pages for introducing hospitals through the hospital server 30 or other web servers, and publish available doctor attribute information of affiliated doctors there. Therefore, the doctor attribute acquisition unit 19 can also acquire doctor attribute information from a web page via the communication network NET, for example.

The reception unit 13 can further receive the attribute information of the user of the user terminal 20 that requested the evaluation via the communication network NET. and the attribute information of the user of the user terminal 20 who is the source of the evaluation request and received by the reception unit 13 can be included. The user attribute information may be transmitted together with the evaluation request from the user terminal 20, or may be received by the reception unit 13 when the user subscribes to the service provided by the service server 10, and may be used as information of the user who is the subscriber. may be registered in a user database (not shown).

[Operation of application example]
Next, an example of the operation of the hospital reservation system will be explained.

In each hospital, a patient first receives at an automatic reception machine or a reception counter. Then, for example, patient information including a patient ID for identifying a patient is input to the control unit 31 from a medical terminal 33 such as an automatic reception machine or a PC operated by a medical staff. For example, based on this patient information, the control unit 31 describes or stores the reception date and time in the electronic medical record of the patient in the electronic medical record database stored in the storage unit 32 . In addition, when a medical treatment such as medical treatment, diagnosis, and treatment of a patient by a doctor, or an examination of a patient by a nurse or a laboratory technician is performed, for example, from the medical terminal 33 operated by a medical staff, the start date and time of medical treatment, medical treatment, etc. Information such as the end date and time, the doctor who treats the patient, the content of the medical care, the prescription, the test results, etc. is input to the control unit 31 . The control unit 31 , for example, describes or stores the input information in the corresponding patient's electronic medical chart in the electronic medical chart database stored in the storage unit 32 . In addition, the control unit 31 calculates the amount to be paid for each patient based on the contents of the electronic medical record stored in the storage unit 32, for example, using an accounting program stored in the storage unit 32, or the like. When the patient pays the payment amount at an automatic accounting machine or accounting counter, payment information is input to the control unit 31 from, for example, an automatic accounting machine or a medical terminal 33 such as a PC operated by a medical worker. The control unit 31 , for example, stores this payment information in the storage unit 32 and describes or stores the accounting end date and time in the corresponding patient's electronic medical chart in the electronic medical chart database stored in the storage unit 32 . In hospitals that store electronic medical charts in the data server 40 of the data center without storing the electronic medical chart database in the storage unit 32, the control unit 31, for example, communicates information to be described in the electronic medical charts. It transmits to the data server 40 via the network NET or a dedicated line. The control unit 41 of the data server 40 , for example, updates the description contents of the corresponding patient's electronic medical record in the electronic medical record database stored in the storage unit 42 based on the received information.

In addition, the control unit 31, for example, every time the description contents of each patient's electronic medical chart is updated or at regular time intervals, for electronic medical charts that have been updated, the entire electronic medical chart or the updated contents are sent to the communication network NET or It transmits to the data server 40 via a dedicated line. The control unit 41 of the data server 40 , for example, updates the description contents of the corresponding patient's electronic medical record in the electronic medical record database stored in the storage unit 42 based on the received information.

The electronic medical record collection unit 11 of the service server 10, for example, at regular intervals, sends electronic medical record description contents to the control unit 41 of the data server 40 of the data center in the electronic medical record network 1 via the communication network NET by a communication interface (not shown). Send request can be sent. Then, in response to this, the description contents of the electronic medical record transmitted from the data server 40 are received and stored in a storage unit (not shown). In each electronic medical record in the electronic medical record database provided in the storage unit 42 of the data server 40, patient information including personal information identifying the individual patient such as name and address, and examination information related to the patient is described. . Further, each electronic medical chart contains medical information regarding each medical treatment of the patient, including reception date/time, medical treatment start date/time, medical treatment end date/time, treating doctor, accounting end date/time, and the like. The electronic medical record description content transmission request to be transmitted to the data server 40 includes collection target information specifying information to be collected, and the electronic medical chart collection unit 11 includes at least medical information in this collection target information. In addition, since transmission and reception of already collected description contents of electronic medical charts is a waste of communication resources, the electronic chart description contents transmission request can include collection period information indicating the period during which information should be collected. The electronic medical record collection unit 11 updates the contents stored in the storage unit (not shown) according to the description contents of the received electronic medical records.

When the user's biological data is acquired by the measuring unit 22 or the biological data measuring device 24 in each user terminal 20, the control unit 21 stores the acquired biological data in the storage unit 23 as PHR. Further, the control unit 21 can transmit the acquired biometric data to the service server 10 via the communication network NET using a communication interface (not shown).

The biometric data collection unit 12 of the service server 10 receives, for example, biometric data transmitted from each user terminal 20 via the communication network NET by a communication interface (not shown), and stores the biometric data in a storage unit (not shown). The received biometric data is additionally stored in the history of biometric data for each user of the user terminal 20 . Alternatively, the biological data collection unit 12 requests the control unit 21 of each user terminal 20 to transmit the biological data for at least a certain period of time stored in the storage unit 23, and the biological data transmitted from each user terminal 20 for at least a certain period of time. The biometric data is collected by receiving the biometric data from the

When one of the user terminals 20 accesses the service server 10 using a smartphone application, a web browser, or the like and transmits an evaluation request, the receiving unit 13 receives this evaluation request via a communication interface (not shown). When the accepting unit 13 accepts this evaluation request, in response to it, the limiting unit 14 stores the biometric data of the user of the user terminal 20 that is the source of the evaluation request, which is accepted together with the evaluation request, in a storage unit (not shown). Evaluation targets to be evaluated are limited from among multiple hospitals or multiple doctors belonging to multiple hospitals based on biometric data collected from multiple users. For example, the limiting unit 14 can refer to the correspondence database 18 according to the attributes of the biometric data of the user of the user terminal 20 who requested the evaluation, and limit a plurality of hospitals or doctors to be evaluated.

In addition, the evaluation request from the user terminal 20 includes the current position of the user terminal 20 acquired by a GPS receiver or a Wi-Fi module, or a position such as a user-designated position input via a user interface (not shown). Can contain information. The specified location can include address information such as the user's home or place of work, for example. Also, the designated position can be registered in advance for each user and stored in a storage unit (not shown) of the service server 10 . The limiting unit 14 can limit a plurality of hospitals or doctors to be evaluated based on this position information.

The evaluation unit 15 selects the electronic medical charts corresponding to the hospitals or doctors limited as evaluation targets by the limiting unit 14 from the contents of the electronic medical charts collected by the electronic medical chart collection unit 11 and stored in the storage unit (not shown). Based on the description of , the limited number of hospitals or doctors are evaluated by evaluating at least the evaluation items including the consultation time and waiting time per patient, and the evaluation results are stored in a storage unit not shown. do. The evaluation items evaluated by the evaluation unit 15 can include the degree of symptom improvement based on the history of the biological data collected by the biological data collecting unit 12 and stored in a storage unit (not shown) for a certain period of time. Furthermore, the evaluation items evaluated by the evaluation unit 15 may include the relationship between the location information from the user terminal 20 that requested the evaluation and the location of the hospital limited as the evaluation target.

It should be noted that, when an examination is performed for medical treatment, the length of stay in the hospital is long, so it is not desirable to use the waiting time as it is for the evaluation of the hospital or the doctor. Therefore, if there is a record of the execution of examinations in the electronic medical charts collected by the electronic medical chart collection unit 11 and stored in the storage unit (not shown), the time information of the medical examination is not used for evaluation by the hospital or doctor. , or the time is multiplied by some coefficient. In addition, when the electronic medical record collecting unit 11 collects the contents of the electronic medical records, it is possible not to collect the information of the medical examinations for which there is a record of the execution of the examination.

Also, the evaluation request from the user terminal 20 can include user attribute information including at least gender and age about the user of the user terminal 20 . Alternatively, the user attribute information can be registered in advance for each user and stored in a storage unit (not shown) of the service server 10 . Further, the doctor attribute acquisition unit 19 acquires publicly available doctor attribute information including at least gender and age for each doctor belonging to each hospital, and stores the information in a storage unit (not shown). The evaluation items evaluated by the evaluation unit 15 can also include the relationship between the user attribute information and the doctor attribute information stored in the storage unit (not shown).

In addition, the control unit 31 of the hospital server 30 manages the patient's time during his stay at the hospital. The evaluation unit 15 sends, via a communication network NET, the control unit 31 of the hospital server 30 of the hospital server 30 of the limited hospital or the hospital to which the limited doctor belongs, to the control unit 31 of each hospital, at least current patients waiting for treatment The number of patients and the number of future reserved patients can be acquired by inquiring. The evaluation items evaluated by the evaluation unit 15 can include the acquired number of patients waiting for treatment and the number of reserved patients.

For example, based on the evaluation result by the evaluation unit 15, the presentation unit 16 sets at least one of a plurality of evaluated hospitals or doctors as a reservation candidate, and makes an evaluation request via a communication network NET using a communication interface (not shown). Send to the original user terminal 20 . The smartphone application, web browser, or the like of the user terminal 20 that has received this reservation candidate presents it to the user.

The evaluation unit 15 calculates an evaluation value representing evaluation results of a plurality of hospitals or doctors limited as evaluation targets, and the presentation unit 16 selects a plurality of hospitals or doctors from the highest evaluation value as reservation candidates. The extracted reservation candidates may be transmitted to the user terminal 20 that requested the evaluation together with the evaluation value.

Alternatively, the evaluation unit 15 converts the evaluation results for each evaluation item into points, sets the total points as the evaluation value for doctors, and sets the average value of the evaluation values of doctors belonging to the hospital as the evaluation value for hospitals. good. In this case, the presentation unit 16 extracts a plurality of hospitals or doctors from the highest evaluation value calculated by the evaluation unit 15 as the appointment candidates, and sends the extracted appointment candidates together with the evaluation values to the user terminal 20 that requested the evaluation. can be sent.

When the patient, who is the user of the user terminal 20 who is the source of the evaluation request, sees the appointment candidates presented on the user terminal 20, and makes an appointment for a desired hospital using a user interface (not shown) such as a smartphone application or a web browser, the user terminal 20 A control unit 21 of 20 transmits a hospital reservation request to the service server 10 via a communication network NET using a communication interface (not shown).

When the reception unit 13 of the service server 10 receives this hospital reservation request through a communication interface (not shown), in response, the reservation unit 17 selects the hospital selected by the user included in the hospital reservation request or the hospital to which the doctor belongs. Then, the hospital is requested to make an appointment for the user. For example, the reservation unit 17 sends the control unit 31 of the hospital server 30 of the identified hospital via the communication network NET through a communication interface (not shown) a reservation for the user of the user terminal 20 who is the requester of the hospital reservation, i.e. who is the evaluation requester. ask for The control unit 31 of the hospital server 30, which operates as a hospital control unit that manages reservations for patients, determines whether or not the reservation is possible, and registers the reservation for the patient if the reservation is possible. Then, the reservation result is returned to the service server 10 via the communication network NET. The reservation unit 17 of the service server 10 receives the reservation result through a communication interface (not shown) and returns the result to the user terminal 20 that requested the reservation. By including the e-mail address of the user of the user terminal 20 who requested the reservation in the reservation request sent from the reservation unit 17 to the hospital server 30, the hospital server 30 can directly notify the user of the reservation result. Also good.

[Effect of application example]
As described above, according to the hospital reservation system according to the application example, in response to an evaluation request from an arbitrary user terminal 20, the evaluation unit 15 of the service server 10 collects biometric data of the user of the user terminal 20 and The hospitals or doctors limited based on the biological data of a plurality of users are evaluated by an objective index of time, and the presentation unit 16 presents appointment candidates to the user based on the evaluation results. Then, the reservation unit 17 makes a reservation for a hospital according to the selection of the hospital or the doctor by the user of the user terminal 20 who requested the evaluation. Therefore, candidates for a hospital or doctor suitable for the user are presented based on an objective index, and the user can easily select a hospital, and can easily make a reservation for the hospital according to the selection. .

<1> First embodiment
A first embodiment will be described below.

<1-1> Configuration A configuration example of the hospital reservation system according to the first embodiment will be described with reference to FIG. The hospital reservation system according to the first embodiment operates as an electronic medical record network 1, a plurality of user terminals 20, and a server device, which are respectively connected to a communication network NET such as the Internet, as described in the application example above. and a service server 100 . FIG. 2 is a block diagram showing an example of the overall configuration of the hospital reservation system according to the first embodiment.

The electronic medical record network 1 includes the hospital server 30 of each hospital and the data server 40 of the data center, as described in the application example above. The hospital server 30 includes the control unit 31, the storage unit 32, and a communication interface (not shown), and is connected to the medical terminal 33, as described in the application example above. The data server 40 includes a control unit 41, a storage unit 42, and a communication interface (not shown), as described in the application example above.

The user terminal 20 includes a control unit 21, a measurement unit 22, a storage unit 23, a communication interface (not shown), and a user interface (not shown), as described in the application examples above. Connectable.

The service server 100 includes a control unit 110, a storage unit 120, and a communication interface 130 in the example of FIG. In addition, in FIG. 2, the communication interface is described as "communication I/F."

The control unit 110 includes, for example, a CPU 111, a RAM 112, and a ROM 113, and controls each component of the service server 100 according to information processing. Other processors such as an MPU may be used instead of the CPU 111 . The ROM 113 stores, for example, an operating system and other programs (eg, hospital reservation program) executed by the CPU 111 . The RAM 112 is, for example, a memory used by the CPU 111 as a work memory.

By executing necessary programs, the CPU 111 performs the electronic medical chart collection unit 11, the biological data collection unit 12, the reception unit 13, the limitation unit 14, the evaluation unit 15, the presentation unit 16, and the reservation unit 17 as described in the application examples. , and the processing of the doctor attribute acquisition unit 19 may be executed. The program may be stored in the storage unit 120 instead of the ROM 113, for example. When the CPU 111 executes a necessary program, for example, the target program stored in the ROM 113 and/or the storage unit 120 is developed in the RAM 112 . Then, the CPU 111 interprets and executes the program developed in the RAM 112, for example, and controls each component.

The storage unit 120 stores, for example, programs executed by the control unit 110 (for example, a hospital reservation program), setting data necessary for executing the programs (for example, address information of the data server 40), various databases, and the like. can be memorized. A storage medium included in the storage unit 120 stores information such as a program by an electrical, magnetic, optical, mechanical, or chemical action so that a computer, machine, or the like can read the information such as the program. Any medium can be used as long as it is stored by For example, an EEPROM or the like can be used as a storage medium included in the storage unit 120 . Note that the storage unit 120 may also be used by the CPU 111 as a work memory. The databases stored by the storage unit 120 can include a hospital database 121, a user database 122, a correspondence database 123, a collection database 124, an evaluation database 125, and the like. In FIG. 2, the hospital database, user database, correspondence database, collection database and evaluation database are described as "hospital DB", "user DB", "medical DB", "collection DB" and "evaluation DB". there is

Under the control of the control unit 110, the communication interface 130 performs data communication with the user terminal 20, the hospital server 30 and the data server 40 via the communication network NET. The communication protocol uses the protocol defined by the communication network NET. Specifically, TCP/IP (Transmission Control Protocol/Internet protocol), UDP/IP (User Datagram Protocol/Internet protocol), or the like can be used.

FIG. 3 is a diagram showing an example of the contents stored in the hospital database 121. As shown in FIG. In the example shown in FIG. 3, the hospital database 121 includes item names such as hospital ID, access information, hospital information, hospital reputation, clinical department, doctor ID, name, gender, age, number of guests, appointment status, doctor reputation, and the like. The information of each corresponding hospital is stored. In FIG. 3, the doctor's reputation is described as "reputation", and the number of visitors is described as "waiting".

“Hospital ID” is a management number uniquely assigned to each hospital in the hospital reservation service provided by the service server 100 . "Access information" is address information for accessing the hospital server 30 and the hospital's web page. "Hospital information" is general information about each hospital, such as hospital name, address, telephone number, business hours, holidays (business days), and parking lot information. “Hospital reputation” is subjective hospital evaluation information arbitrarily input at each user terminal 20 and/or obtained from various hospital evaluation web pages on the Internet. "Clinical department" is information on the clinical departments of the hospital, such as internal medicine and dermatology.

"Doctor ID" is a management number uniquely assigned to each doctor belonging to the hospital. This doctor ID is associated with the hospital ID so that each doctor can be distinguished, but since the doctor may move to another hospital, it is uniquely set in the hospital reservation service provided by the service server 100 . If each hospital uses a unique doctor ID, a separate doctor database is prepared in the storage unit 120 so that the hospital's unique doctor ID can be converted into a doctor ID for this hospital reservation service. good. "Name" is the name of each doctor. "Gender" is the gender of each doctor. "Age" is the age of each doctor. "Waiting" is the current number of patients waiting for treatment for each doctor. "Appointment status" is the number of future appointment patients for each doctor. For this reservation status, for example, one day is divided into arbitrary periods such as morning and afternoon, and the number of reserved patients for each is stored. “Doctor reputation” is subjective doctor evaluation information arbitrarily input at each user terminal 20 and/or obtained from various hospital evaluation web pages on the Internet.

FIG. 4 is a diagram showing an example of the contents of the user database 122. As shown in FIG. In the example shown in FIG. 4, the user database 122 includes items such as user ID, password, name, user information, hospital ID, location, priority condition, date, hospital visit flag, biometric data (eg, blood pressure, pulse, etc.). , symptom patterns, etc. In FIG. 4, the password is described as "PW", the hospital visit flag is described as "hospital visit F", and the symptom pattern is described as "symptom P".

“User ID” is a user management number uniquely assigned when the user subscribes to the hospital reservation service provided by the service server 100 . "Password" is a value arbitrarily set by the user for authentication. “Name” is the name of the user. "User information" is information about the user, including email address, phone number, gender and age. The “hospital ID” is information indicating the management number of the user at each hospital, and is a combination of the hospital ID and the user management number at the hospital. This hospital-by-hospital ID makes it possible to associate each user with the electronic medical record of each hospital. A "point" is the user's location information and can include current location, home address, work address, and registered location. As for the current position, for example, the current position transmitted from the user terminal 20 is registered as necessary. The home address, workplace address, and registered position are designated positions arbitrarily designated by the user. “Priority condition” is information selected from predetermined options or arbitrarily specified by the user as a priority condition.

“Date” is the date when the user terminal 20 acquired the biometric data. The "hospital visit flag" indicates whether or not the user has visited any hospital, and "1" is set when the user has visited a hospital. The biometric data (“blood pressure”, “pulse”, etc.) is biometric data acquired by the user terminal 20 . "Symptom pattern" indicates a symptom set based on the attributes of biometric data including various measured values or relationships between measured values included in biometric data, that is, the pattern of biometric data. "Date", "Visit flag", biometric data ("Blood pressure", "Pulse rate", etc.), and "Symptom pattern" are allotted to each user in a predetermined amount of data. are stored, and when adding more information, the oldest information is deleted. A predetermined number may be used instead of the period. In any case, this period or number should be determined so that biometric data is stored for at least a certain period of time, which will be described later. The user database 122 may also store a record of doctor IDs with whom the user has received treatment in the past.

FIG. 5 is a diagram showing an example of the contents stored in the correspondence database 123. As shown in FIG. The correspondence database 123 corresponds to the correspondence database 18 described in the application example above. In the example shown in FIG. 5, the correspondence database 123 has symptom patterns, hospital IDs, and doctor IDs as items. In FIG. 5, the symptom pattern is described as "symptom P". This correspondence database 123 is a database of hospitals and doctors corresponding to symptom patterns.

“Symptom pattern” corresponds to the symptom pattern of the user database 122 . "Hospital ID" is a management number for identifying a hospital. "Doctor ID" is a management number for identifying a doctor. These hospital IDs and doctor IDs correspond to those in the hospital database 121 .

FIG. 6 is a diagram showing an example of the contents of the collection database 124. As shown in FIG. In the example shown in FIG. 6, the collection database 124 has items such as hospital ID, patient ID, appointment date and time, reception, start of medical care, doctor ID, end of medical care, end of accounting, first visit flag, symptoms, and the like. In FIG. 6, the first visit flag is described as "first visit F".

"Hospital ID" is a management number for specifying a hospital, and the information in the hospital database 121 and the collection database 124 can be linked by this hospital ID. "Patient ID" is a patient management number uniquely assigned by each hospital. "Appointment date and time" is the date and time when the patient made an appointment. The "reception" is the time when the patient came to the hospital and received the reception. For example, at each hospital, reception is performed by the medical terminal 33, for example, a PC operated by a receptionist or an automatic reception machine operated by a patient, and the reception time is entered in the electronic medical record corresponding to the patient. "Clinical service start" is the time when the doctor's medical care for the patient was started. "Doctor ID" is information for identifying a doctor who provides medical treatment. Information in the hospital database 121 and the collection database 124 can be linked by this doctor ID. "End of medical care" is the time when the doctor's medical care for the patient ended. For example, at each hospital, by inputting the medical treatment start time, doctor ID, and medical treatment end time from the medical terminal 33, for example, a PC operated by a doctor or a nurse, such information is recorded in the electronic medical record corresponding to the patient. be done. "Accounting end" is the time when the patient has completed accounting. For example, in each hospital, by inputting the end of payment on the medical terminal 33, for example, a PC operated by an accounting clerk, or by making payment with an automatic accounting machine operated by the patient, the patient can described in the corresponding electronic medical record. The "first visit flag" indicates whether or not the medical care is the first visit, and "1" is set in the case of the first visit. "Symptom" is the disease name of the patient.

Note that the example of FIG. 6 shows a case in which, when collecting the contents described in the electronic medical record, the information of the medical examination session for which there is a record of the examination execution is not collected. In the case of collecting information on medical examination times when examinations are performed, for example, the collection database 124 further provides, as items, flags indicating whether or not examinations have been performed. In many cases, an examination is also performed at the time of the first visit, so the "initial examination flag" may also be used as a flag indicating whether or not this examination is to be performed.

FIG. 7 is a diagram showing an example of contents stored in the evaluation database 125. As shown in FIG. In the example shown in FIG. 7, the evaluation database 125 includes items such as user ID, hospital ID, hospital score, clinical department, clinical department score, doctor ID, total score, time score, improvement score by symptom (for example, hypertension improvement severity score, diabetes improvement score, urticaria improvement score, etc.), etc. In FIG. 7, only the hypertension improvement score among the improvement scores for each symptom is shown and described as "hypertension".

"User ID" is a management number for specifying a user, and information in the user database 122 and the evaluation database 125 can be linked with this user ID. "Hospital ID" is a management number for specifying a hospital, and the information of the hospital database 121, the collection database 124, and the evaluation database 125 can be linked by this hospital ID. The "hospital score" is an evaluation value obtained by digitizing the evaluation result of the hospital. Here, numerical values are shown with the maximum score being 100 points, but this numerical expression is an example. For example, it may be expressed in terms of the number of stars with five stars as the highest score, or in terms of deviation values. This "hospital score" can be the average value of evaluation values of all departments of the hospital. "Department" is information on the departments owned by the hospital, and information on the hospital database 121 and the evaluation database 125 can be linked by this department. The “medical department score” is an evaluation value for each medical department. This "clinical department score" can be an average value of evaluation values of all doctors belonging to the relevant clinical department, for example, a total score described later.

"Doctor ID" is information for identifying a doctor who provides medical treatment. Information in the hospital database 121, the collection database 124, and the evaluation database 125 can be linked with this doctor ID. "Total score" is an evaluation value for each doctor. This "total score" can be the sum of the time evaluation value for the doctor and the average or weighted average of all improvement evaluation values.

The "time score" is a time evaluation value evaluated from the consultation time and waiting time per patient for each doctor. The time evaluation value is evaluated based on, for example, the average consultation time per patient and the average waiting time per patient. For example, regarding the average value of consultation time per patient, the longer the average value, the higher the evaluation value according to a predetermined time range. For example, if the average consultation time per patient is 10 minutes or more, the full score is 10 points, and each time the time is reduced by 1 minute, 1 point can be reduced. In addition, regarding the average value of the waiting time per patient, for example, the shorter the average value, the higher the evaluation value according to a predetermined time range. For example, if the average waiting time per patient is within 30 minutes, the full score is 50 points, and every time the waiting time increases by 2 minutes, the score is reduced by 1 point. The "time score" can be the sum of the points obtained in this manner for the average consultation time per patient and the average waiting time per patient.

The "symptom improvement score" is an improvement evaluation value evaluated from the improvement of each symptom. For example, among the patients who received medical care by the doctor, for patients registered in the user database 122 and whose biometric data history for a certain period can be obtained, the improvement evaluation value is obtained from the biometric data history for a certain period. Based on how much the symptoms have improved, an evaluation value of the degree of improvement of the symptoms can be obtained, and the evaluation values of all users can be averaged. For example, if the symptom is hypertension, if the systolic blood pressure decreases by 20 mmHg over a certain period of time, for example, one month, the full score is 10 points, and 1 point is given for each decrease of 1 mmHg. can be reduced, etc.

The "total score" can be calculated from the "time score" and the total "improvement score by symptom". By adding priority conditions, user attribute information, etc. to the evaluation items, the calculated "time score" can be corrected.

<1-2> Operation Next, an operation example of the hospital reservation system according to the first embodiment will be described with reference to FIGS. 8 and 9. FIG.

FIG. 8 is a flowchart illustrating an example of the processing procedure of the service server, and FIG. 9 is a flowchart illustrating an example of the processing procedure of the user terminal.

<1-2-1> Biological Data Collection Operation [Step S101]
The CPU 111 of the service server 100 first determines whether or not it is time to collect biometric data. In this embodiment, biometric data is collected at a predetermined timing, such as once a day. When determining that it is time to collect biological data (step S101, YES), the CPU 111 advances the process to step S102. When determining that it is not the time to collect biometric data (step S101, NO), the CPU 111 advances the process to step S103.

[Step S102]
When determining that it is time to collect biometric data in step S101 (step S101, YES), the CPU 111 executes biometric data collection processing. In this biometric data collection process, the CPU 111 requests the user terminal 20 of each user registered in the user database 122 to transmit the PHR stored in the storage unit 23 of the user terminal 20 through the communication interface 130. In response to this, the PHR transmitted from each user terminal 20 is registered in the corresponding user's biometric data (“blood pressure”, “pulse”, etc.) item of the user database 122 . In addition, the CPU 111 determines the attributes of the biometric data including the measured values of each item of the biometric data registered in the user database 122 or the relationship between the measured values, that is, the symptom corresponding to the pattern of the biometric data, and stores it in the user database 122. Register in the symptom pattern item. Any method may be used to determine this symptom. For example, symptoms are selected in advance for a large number of patterns of biometric data, stored in a database, and by pattern matching between the databased patterns and the biometric data patterns registered in the user database 122, the most similar pattern is determined. Symptoms can be taken. Alternatively, by machine-learning a large amount of biometric data patterns, symptoms corresponding to biometric data patterns registered in the user database 122 may be determined. After completing the biometric data collection process, the CPU 111 advances the process to step S103.

[Step S201]
That is, the processor (not shown) of the control unit 21 of the user terminal 20 executes a hospital reservation program as one of the application programs executed in the background in the same way as an e-mail program, etc. It can be determined whether it has received a PHR request from. When determining that the PHR request has not been received (step S201, NO), the processor advances the process to step S202. Also, when determining that the PHR request has been received (step S201, YES), the processor advances the process to step S203.

[Step S202]
When the processor (not shown) of the control unit 21 of the user terminal 20 determines in step S201 that the PHR request has not been received from the service server 100 (step S201, NO), the user operation through the user interface (not shown) is valid. determine whether or not When determining that there is no operation (step S202, NO), the processor returns the process to step S201. If it is determined that some kind of operation has been performed (step S202, YES), the processor advances the process to step S204.

[Step S203]
When the processor (not shown) of the control unit 21 of the user terminal 20 determines in step S201 that the PHR request has been received from the service server 100 (step S201, YES), it executes PHR transmission processing. In this PHR transmission process, the processor notifies the user of the user terminal 20 of the reception of the PHR request by pop-up or the like. If the user confirms this and performs an operation to permit transmission, the processor transmits the PHR stored in the storage unit 23 to the service server 100 via a communication interface (not shown). In this case, in order to respond to the request from the service server 100, user authentication processing does not have to be performed. Also, if the operation to permit transmission is not performed, the PHR request is ignored, or a rejection response is returned to the service server 100 after waiting for a predetermined time from the reception. Therefore, in step S102 of the operation of the service server 100, there are user terminals that cannot collect biometric data. After completing the PHR transmission process, the processor returns the process to step S201.

<1-2-2> Registration Information Update Operation [Step S103]
When the CPU 111 of the service server 100 determines in step S101 that it is not the time to collect the biological data (step S101, NO), or after the biological data collection process in step S102 ends, the hospital database 121 is updated. Execute the process. For example, the CPU 111 sends an update inquiry to the hospital server 30 or the data server 40 via the communication interface 130, or confirms a request to update the hospital information from the hospital server 30 or the data server 40. Update the hospital database 121 for the hospital. Also, the CPU 111 can add a new hospital to the hospital database 121 . For this new registration, for example, the administrator of the service server 100 can operate an administrator terminal (not shown) connected to the service server 100 directly or via a communication network NET. It should be noted that in the updating process in step S103, among the items of the hospital database 121, the hospital ID, access information, hospital information, clinical department, doctor ID, gender, and age are updated or newly registered. Don't update the status. In addition, the CPU 111 can search for subjective hospital evaluation information and doctor evaluation information from arbitrary web pages and the like, and register the results in the hospital database 121 in the items of hospital reputation and doctor reputation. It should be noted that, in the updating process of step S103, there may be cases where there is no particular information to be changed and the contents of the hospital database 121 are not updated at all.

[Step S104]
The CPU 111 of the service server 100 executes update processing of the user database 122 . For example, the CPU 111 updates the user database 122 for users who need to be updated by operating the user terminal 20 or an administrator terminal (not shown) through the communication interface 130 . User authentication is required to perform an update according to an operation from the user terminal 20, and the update processing in step S104 includes user authentication processing. Also, the CPU 111 can add a new user to the user database 122 . It should be noted that in the updating process of step S104, among the items of the user database 122, the user ID, password, name, user information, hospital ID, location, and priority conditions are updated or newly registered. Some information may not. The ID for each hospital may be input by operation from the user terminal 20, or an inquiry may be made to each hospital server 30 for the management number of the user using user information, location (home address), etc. as keys. may be collected at It should be noted that, in the updating process of step S104, there may be cases where there is no particular information to be changed and the contents of the user database 122 are not updated at all.

[Step S105]
The CPU 111 of the service server 100 determines by the communication interface 130 whether or not the PHR has been received from any user terminal 20 via the communication network NET. When determining that the PHR has not been received (step S105, NO), the CPU 111 advances the process to step S106. When determining that the PHR has been received (step S105, YES), the CPU 111 advances the process to step S107.

[Step S106]
When the CPU 111 of the service server 100 determines that the PHR has not been received from any of the user terminals 20 in step S105 (step S105, NO), the communication interface 130 allows any user to It is determined whether or not an evaluation request has been received from the terminal 20 . Note that this determination includes user authentication processing. When determining that the evaluation request has not been received (step S106, NO), the CPU 111 returns the process to step S101. When determining that the user has been authenticated and the evaluation request has been received (step S106, YES), the CPU 111 advances the process to step S108.

[Step S204]
If the processor (not shown) of the control unit 21 of the user terminal 20 determines that there has been some kind of operation in step S202 (step S202, YES), whether or not the operation is an instruction to acquire biometric data by the measurement unit 22. to judge whether This biometric data acquisition instruction can include an instruction to measure biometric data by the measurement unit 22 provided in the user terminal 20 . The biometric data acquisition instruction may be an instruction to acquire biometric data measured by the biometric data measuring device 24 that can communicate with the user terminal 20 . If it is determined that there is an instruction to acquire biometric data (step S204, YES), the processor advances the process to step S205. When determining that the performed operation is not an instruction to acquire biometric data (step S204, NO), the processor advances the process to step S208.

[Step S205]
If the processor (not shown) of the control unit 21 of the user terminal 20 determines that the biometric data acquisition instruction has been given in step S204 (step S204, YES), it executes biometric data acquisition processing. In this biometric data acquisition process, the biometric data is acquired by measuring the biometric data with the measuring unit 22 provided in the user terminal 20 . Alternatively, biometric data is measured by a biometric data measuring device 24 that can communicate with the user terminal 20, and the measured biometric data is obtained through communication.

[Step S206]
A processor (not shown) of the control unit 21 of the user terminal 20 additionally records the acquired biometric data in the PHR accumulated in the storage unit 23 .

[Step S207]
Then, the processor (not shown) of the control unit 21 of the user terminal 20 transmits the PHR stored in the storage unit 23 to the service server 100 via the communication network NET using a communication interface (not shown). In this case, the PHR is transmitted with a user ID attached so that it is possible to identify whose biometric data the PHR belongs to. Moreover, it is not necessary to transmit all the data of the PHR stored in the storage unit 23 . For example, only the latest biometric data may be transmitted, or the latest biometric data may be transmitted for a certain period of time or in a certain number. After that, the processor returns the process to step S201.

[Step S107]
When the CPU 111 of the service server 100 determines that a PHR has been received from any user terminal 20 in step S105 (step S105, YES), the CPU 111 of the corresponding user in the user database 122 based on the received PHR. Update date, biometric data ("blood pressure", "pulse", etc.) and symptom pattern items. In this case, the received PHR can be compared with the biometric data registered in the user database 122, and only the difference can be additionally updated. If a predetermined period of time or a predetermined number of biometric data have already been stored for the corresponding user in the user database 122, the oldest information is deleted and added. Also, when the received PHR contains biometric data for several times per day, only the biometric data for the first time may be added, or only the biometric data for the last time may be added. You can do it. For blood pressure, for example, since the data measured after waking up is particularly effective information, it is desirable to use the biological data for the first time. Therefore, which of the multiple times to use may be determined depending on the type of biometric data. After updating the user database 122, the CPU 111 advances the process to step S106.

<1-2-3> Electronic chart collection and evaluation operation [Step S208]
When the processor (not shown) of the control unit 21 of the user terminal 20 determines that the operation performed in step S204 is not an instruction to acquire biological data (step S204, NO), the operation performed is an instruction to acquire medical evaluation. Determine whether or not When determining that there is an instruction to obtain a medical evaluation (step S208, YES), the processor advances the process to step S209. When determining that the performed operation is not an instruction to obtain a medical evaluation (step S208, NO), the processor advances the process to step S210.

[Step S209]
If the processor (not shown) of the control unit 21 of the user terminal 20 determines that there is an instruction to obtain the medical evaluation in step S208 (step S208, YES), it executes evaluation processing. FIG. 10 is a flowchart illustrating an example of this evaluation processing.

[Step S2091]
A processor (not shown) of the user terminal 20 receives an input of evaluation conditions by a user's operation through a user interface (not shown). Evaluation conditions can include priority conditions. Also, the evaluation conditions can include an evaluation target condition indicating whether the target for presenting the evaluation result is a hospital or a doctor. Since a hospital may have a plurality of clinical departments, the evaluation target condition may be the clinical department instead of the hospital.

[Step S2092]
Then, the processor of the user terminal 20 attaches the input evaluation conditions and transmits an evaluation request to the service server 100 via the communication network NET. At this time, the evaluation request may include a user ID and password for user authentication and location information indicating the current location of the user terminal 20 . Also, the latest biometric data stored as PHR in the storage unit 23 may be transmitted together.

[Step S2093]
Thereafter, the processor of the user terminal 20 waits to receive reservation candidates from the service server 100 via the communication network NET. That is, the processor determines whether or not a reservation candidate has been received, and if not (step S2093, NO), repeats the process of step S2093.

[Step S108]
If the CPU 111 of the service server 100 determines in step S106 that an evaluation request has been received (step S106, YES), the CPU 111 authenticates the user using the user ID and password included in the received evaluation request. update the user database 122 with the location information contained in the request and the priority conditions contained in the evaluation conditions sent with the evaluation request. In other words, the CPU 111 updates the current position and priority conditions for the user in the user database 122 with the received information. The CPU 111 also stores the evaluation target conditions included in the received evaluation conditions in the RAM 112 or the storage unit 120 . When the latest biometric data is also transmitted, it is compared with the biometric data registered in the user database 122 and additionally registered if necessary.

[Step S109]
Here, the CPU 111 limits hospitals or doctors to be evaluated. For example, the CPU 111 first reads a symptom from the symptom pattern item corresponding to the latest biometric data of the corresponding user in the user database 122, searches the correspondence database 123 using the read symptom as a search key, limit. Furthermore, the CPU 111 stores hospitals or doctors to be evaluated among the hospitals or doctors limited by the biometric data attribute, that is, the biometric data pattern, in the user database 122 in the priority condition item of the corresponding user. The information is limited by the information that defines the position. That is, for example, if the priority condition is "current location", the CPU 111 determines the distance from the address stored in the hospital information in the hospital database 121 based on the current location stored in the location item of the corresponding user in the user database 122. is limited to hospitals or doctors within a predetermined range as evaluation targets. Similarly, the hospital or doctor to be evaluated can be limited by the home address if the priority condition is "home", the workplace address if the priority condition is "workplace", and the registered location if the priority condition is "registered location". .

As for the method of narrowing down the hospitals or doctors to be evaluated, it is also possible to first limit them according to the position information and then limit them according to the pattern of the biometric data. Whether the hospital or the doctor is to be evaluated depends on the evaluation target conditions from the user terminal 20 that requested the evaluation stored in the RAM 112 or the storage unit 120 .

The CPU 111 stores in the RAM 112 or the storage unit 120 the list of hospital IDs of the limited evaluation target hospitals or the list of the doctor IDs of the evaluation target doctors and the hospital IDs of the hospitals to which the corresponding doctors belong. Even if the subject of evaluation is a doctor, the hospital may not be able to make an appointment with a designated doctor.

[Step S110]
The CPU 111 executes an electronic medical chart collection process for collecting the contents of the electronic medical charts of the limited hospitals. FIG. 11 is a flowchart illustrating an example of this electronic medical chart collection process.

[Step S1101]
In the electronic medical record collection process, the CPU 111 first selects one hospital ID from the list of hospital IDs stored in the RAM 112 or the storage unit 120 to determine the acquisition destination hospital.

[Step S1102]
Next, the CPU 111 acquires the contents of the electronic medical record of the acquisition destination hospital from the data server 40 via the communication network NET by the communication interface 130 . For example, the CPU 111 refers to the hospital database 121 using the hospital ID, and reads specific information that identifies the hospital, such as the hospital ID, access information, hospital name, address, or telephone number. Then, the CPU 111 requests the control unit 41 of the data server 40 to transmit the description contents of the electronic medical record together with the specific information through the communication network NET by the communication interface 130 . The CPU 111 receives the contents of the electronic medical record transmitted from the data server 40 in response to this through the communication interface 130 .

In addition, if the number of electronic medical records at the receiving hospital is large, it is expected that processing will take some time. can be

[Step S1103]
Next, the CPU 111 registers information in the hospital database 121 and the collection database 124 based on the contents of the received electronic medical record. For example, for each patient ID, the CPU 111 collects information about each medical treatment described in the electronic medical record, that is, appointment date and time, reception, start of medical treatment, doctor ID, end of medical treatment, end of accounting, first visit flag, and symptoms in the collection database 124. Remember. Note that, in this embodiment, when the received electronic medical record records the execution of an examination, the CPU 111 does not store information regarding the medical treatment of that medical treatment session in the collection database 124 . In addition, the CPU 111 counts the current number of patients waiting for medical treatment for each doctor ID based on the content of the electronic medical record, and stores the counted number of patients in the "Waiting" item corresponding to each doctor ID in the hospital database 121. do.

[Step S1104]
Next, the CPU 111 acquires the number of reserved patients from the acquisition destination hospital using the communication interface 130 via the communication network NET. For example, the CPU 111 refers to the hospital database 121 using the hospital ID to read the access information of the hospital, and sends the current information about each doctor to the control unit 31 of the hospital server 30 of the hospital via the communication network NET by the communication interface 130 . Queries the number of patients booked at the time point. The current number of patients waiting for treatment can be determined by aggregating the contents of the electronic medical records. unable to comprehend. Therefore, it is necessary to inquire about the number of reserved patients to the receiving hospital. The CPU 111 receives, through the communication interface 130, information on the number of reserved patients transmitted from the hospital server 30 in response to this inquiry.

[Step S1105]
Next, the CPU 111 stores the number of reserved patients in the "reservation status" item of the hospital database 121 in correspondence with each doctor's ID according to the received information on the number of reserved patients at the present time for each doctor.

[Step S1106]
Next, the CPU 111 determines whether or not the contents of the electronic medical records have been collected for all the hospitals indicated by the list of hospital IDs stored in the RAM 112 or the storage unit 120 . If it is determined that there is a hospital that has not yet been collected (step S1106, NO), the CPU 111 returns the process to step S1101 to perform the process for the next hospital. If the CPU 111 determines that the collection of electronic medical record contents from all the listed hospitals has been completed (step S1106, YES), the CPU 111 advances the process to step S111.

[Step S111]
The CPU 111 executes an evaluation calculation process for calculating an evaluation value based on the contents of the electronic medical charts of the limited hospitals stored in the collection database 124 . FIG. 12 is a flowchart illustrating an example of this evaluation calculation process.

[Step S1111]
In the evaluation calculation process, the CPU 111 first selects one hospital ID from the list of hospital IDs stored in the RAM 112 or the storage unit 120 to determine a hospital to be processed.

[Step S1112]
Next, the CPU 111 evaluates the doctor by evaluation items including at least consultation time and waiting time per patient. For example, the CPU 111 refers to the collection database 124 using the hospital ID to calculate the time score for each doctor of the processing target hospital. The time score can be calculated, for example, based on the sum of the average score for consultation time and the average score for waiting time per patient. The consultation time is the time from the start of medical care to the end of medical care stored in the collection database 124, and the waiting time is the time from reception to the start of medical care stored in the collection database 124 and the time from the end of medical care to the end of accounting. is the sum of CPU 111 stores the calculated time score for each doctor in RAM 112 or storage unit 120 . In many cases, the initial consultation takes a long time, so whether or not it is the first consultation is determined by the "initial consultation flag" in the collection database 124, and the time used to calculate the time score is predetermined if it is the first consultation. may be used after being multiplied by the given coefficient.

[Step S1113]
Next, the CPU 111 evaluates the doctor using evaluation items including the relationship between the doctor's attribute information and the user's attribute information. For example, the CPU 111 corrects the time score for each doctor stored in the RAM 112 or storage unit 120 based on the attribute information. Attribute information includes, for example, gender and age. The CPU 111 compares the attribute information of each doctor stored in the hospital database 121 with the attribute information stored in the user database 122 and corresponding to the user ID of the user who requested the evaluation. Then, the score value is corrected according to a predetermined rule, such as, for example, increasing the score if the person is of the same sex or increasing the score if the age is close. CPU 111 stores the corrected time score for each doctor in RAM 112 or storage unit 120 .

[Step S1114]
Next, the CPU 111 evaluates the doctor by evaluation items including the relationship between the location information specified as the priority condition from the user terminal 20 and the location of the hospital. For example, the CPU 111 corrects the time score for each doctor, which is corrected based on the attribute information and stored in the RAM 112 or the storage unit 120, based on the priority condition. The CPU 111 refers to the priority condition corresponding to the user ID of the user who requested the evaluation, stored in the user database 122, and the location information specified as the priority condition matches the address of the hospital stored in the hospital database 121. If it is within a certain distance, the score value is increased. CPU 111 stores the corrected time score for each doctor in RAM 112 or storage unit 120 .

[Step S1115]
After that, the CPU 111 evaluates the doctor by evaluation items including the current number of patients waiting for treatment and the number of reserved patients. For example, the CPU 111 corrects the time score for each doctor, which has been corrected based on the priority conditions and stored in the RAM 112 or the storage unit 120, based on the number of waiting patients and the number of reserved patients. The CPU 111 counts the number of patients waiting for medical treatment and the number of reserved patients for each doctor stored in the hospital database 121, and increases the score value as the counted number decreases. CPU 111 stores the corrected time score for each doctor in RAM 112 or storage unit 120 .

[Step S1116]
Next, the CPU 111 refers to the user database 122 and the collection database 124 to calculate the symptom improvement score for each doctor. For example, based on the hospital-by-hospital ID of each user in the user database 122, the symptoms of the user are obtained from the collection database 124, and users with the same symptoms as the acquired symptoms are identified. Also, biometric data to be referred to is determined according to the symptom. Then, if the specified user is registered in the user database 122, the CPU 111 reads from the user database 122 and evaluates the biometric data determined based on the user's symptoms over a certain period of time. For example, if the symptom is high blood pressure, the CPU 111 reads and evaluates blood pressure values for a certain period of time.

FIG. 13 is a diagram showing an example of the history of this read biometric data. In the example of this figure, the systolic blood pressure drops by D during a certain period of time P. For example, if the systolic blood pressure decreases by 20 mmHg or more for a certain period of time P, for example, one month, the score is set to 10 points, which is a full score, and the score is reduced by 1 point for each decrease of 1 mmHg.

FIG. 14 is a diagram showing another example of biometric data history. Also in the example of this figure, it is assumed that the amount of decrease D in systolic blood pressure during a certain period of time P is within the same score range as in the example of FIG. 13 . However, in this example, the temporarily degraded history is included. In such a case, the same score as in the example of FIG. 13 may be set as it is, but it may be calculated to be lower than in the example of FIG. In particular, if the timing of a change from a temporarily worsened condition to an improvement coincides with the timing of switching to another hospital or doctor, there is a high possibility that the temporarily worsened condition is due to a misdiagnosis. . The CPU 111, for example, determines the possibility of this misdiagnosis based on the date recorded in the appointment date and time item of the collection database 124, the date recorded in the date item of the user database 122, and the record of the outpatient visit recorded in the outpatient flag item. sex can be determined and the score can be modified accordingly.

The CPU 111 stores in the RAM 112 or the storage unit 120 the symptom improvement score calculated for each doctor.

[Step S1117]
Next, the CPU 111 calculates a total score from the improvement score by symptom and the corrected time score for each doctor stored in the RAM 112 or the storage unit 120 . Furthermore, the CPU 111 calculates a clinical department score and a hospital score from the total score for each doctor. The CPU 111 stores in the RAM 112 or the storage unit 120 the total score, department score, and hospital score thus calculated for each doctor.

[Step S1118]
Then, CPU 111 registers each score thus calculated and stored in RAM 112 or storage unit 120 in evaluation database 125 in association with the user ID. By correcting the time score based on attribute information and priority conditions in this way, as shown in FIG. will be registered with

[Step S1119]
Next, the CPU 111 determines whether calculation of the evaluation values for all the hospitals indicated by the list of hospital IDs stored in the RAM 112 or the storage unit 120 has been completed. If it is determined that there is a hospital for which evaluation values have not yet been calculated (step S1119, NO), the CPU 111 returns the process to step S1111 and performs the process for the next hospital. When determining that evaluation values have been calculated for all listed hospitals (step S1119, YES), the CPU 111 advances the process to step S112.

[Step S112]
The CPU 111 reads and sorts the evaluation results corresponding to the user ID of the user requesting the evaluation stored in the evaluation database 125 according to the evaluation target conditions stored in the RAM 112 or the storage unit 120 . For example, if the evaluation target condition is a hospital, a set of hospital ID and hospital score is read and sorted in descending order of hospital score. Further, for example, if the evaluation target condition is a doctor, the combination of the doctor ID and the total score is read and sorted in descending order of the total score. CPU 111 stores the sorted result in RAM 112 or storage unit 120 .

[Step S113]
Then, the CPU 111 determines reservation candidates based on the sorted results stored in the RAM 112 or the storage unit 120, and transmits them to the user terminal 20 that requested the evaluation by the communication interface 130 via the communication network NET. The number of reservation candidates should be at least one, but it is desirable to determine and transmit a plurality of candidates in order to give the user a choice. Of course, the next candidate may be sequentially determined and transmitted in response to a return instruction from the user terminal 20 . Reservation candidates are determined according to evaluation target conditions stored in RAM 112 or storage unit 120 . For example, if the evaluation target condition is a hospital, hospital information including at least the name and address of the hospital and the score value of the hospital can be included. Hospital information can be obtained from the hospital database 121 . Also, for example, if the evaluation target condition is a doctor, doctor information including at least the doctor's name, gender, and age, the score value of the doctor, hospital information of the hospital to which the doctor belongs, and the score value of the hospital, can include Doctor information and hospital information can be acquired from the hospital database 121 .

[Step S2094]
If it is determined in step S2093 that a reservation candidate has been received (step S2093, YES), the processor of the user terminal 20 advances the process to step S2094 and presents the received reservation candidate to the user through a user interface (not shown).

<1-2-4> Reservation Operation [Step S114]
After transmitting the reservation candidate in step S113, the CPU 111 of the service server 100 determines whether or not the communication interface 130 has received a reservation request from the user terminal 20 via the communication network NET. When determining that the reservation request has not been received (step S114, NO), the CPU 111 advances the process to step S115.

[Step S2095]
After presenting the reservation candidate received in step S2094 to the user, the processor (not shown) of the user terminal 20 accepts input of end or reservation by user operation through a user interface (not shown). Appointment entry includes selection of a hospital or doctor for which the appointment is desired and entry of the desired date and time.

[Step S2096]
Then, the processor of the user terminal 20 determines whether or not the received input is an end input. If the received input is not an end input, that is, if it is determined that it is a reservation input (step S2096, NO), the processor advances the process to step S2097.

[Step S2097]
If it is determined in step S2096 that the reservation input has been received (step S2096, NO), the processor of the user terminal 20 transmits a reservation request to the service server 100 via the communication network NET.

[Step S2098]
After that, the processor of the user terminal 20 waits to receive the reservation result from the service server 100 via the communication network NET. That is, the processor determines whether or not the reservation result has been received, and if not (step S2098, NO), repeats the process of step S2098.

[Step S116]
If the CPU 111 of the service server 100 determines in step S114 that the reservation request has been received (step S114, YES), the process proceeds to step S116, and the communication interface 130 sends the request to the hospital server of the hospital via the communication network NET. 30 with the user's PHR stored in the user database 122 . Instead of the PHR including all biometric data, only the latest biometric data may be included. At this time, the CPU 111 refers to the hospital ID in the user database 122, and if it can be confirmed that the user has a management number in the hospital, the management number is added to the reservation request. can be included.

[Step S117]
After that, the CPU 111 waits for reception of the reservation result from the hospital server 30 of the hospital by the communication interface 130 via the communication network NET. That is, the CPU 111 determines whether or not the reservation result has been received, and if it determines that the reservation result has not been received (step S117, NO), repeats this step S117.

The hospital server 30, which manages reservations for patients, performs reservation processing according to this reservation request. Then, the result is returned to the service server 100 via the communication network NET.

[Step S118]
When determining in step S117 that the reservation result has been received (step S117, YES), the CPU 111 transmits the reservation result to the user terminal 20 that requested the reservation via the communication network NET through the communication interface 130 . After that, the CPU 111 returns the process to step S114.

[Step S2099]
If it is determined in step S2098 that the reservation result has been received (step S2098, YES), the processor of the user terminal 20 advances the process to step S2099 and presents the received reservation result to the user through a user interface (not shown). After that, the processor returns the process to step S2095.

If the reservation result indicates that the desired appointment cannot be made, in step S2095 the user can reset another desired appointment date and time, or select another hospital, another doctor, or the like. is. Also, when the desired appointment is made, the user inputs an end to end the medical evaluation process.

<1-2-5> End Operation [Step S20910]
If the processor (not shown) of the user terminal 20 determines that the input received in step S2096 is an end input (step S2096, YES), the process proceeds to step S20910, and an end request is sent via the communication network NET. Send to service server 100 . Then, the processor returns the process to step S201.

[Step S115]
When the CPU 111 of the service server 100 determines in step S114 that the reservation request has not been received (step S114, NO), the communication interface 130 further receives a termination request from the user terminal 20 via the communication network NET. is received. When determining that the end request has not been received (step S115, NO), the CPU 111 returns the process to step S114. When determining that the end request has been received (step S115, YES), the CPU 111 returns the process to step S101.

<1-2-6> Other processing [Step S210]
If the processor (not shown) of the control unit 21 of the user terminal 20 determines that the operation performed in step S208 is not an instruction to obtain a medical evaluation (step S208, NO), it executes other processing according to the operation. do. The other processing includes, for example, processing corresponding to the user's new registration operation and information update operation for updating the user database 122 in step S104 of the service server 100 . After executing the process, the processor returns the process to step S201.

<1-3> Effect According to the first embodiment described above, the CPU 111 of the service server 100 collects the contents of each electronic medical record from the electronic medical record network 1 for sharing the electronic medical records among a plurality of hospitals. At the same time, the biometric data history of each of a plurality of users is collected from the user terminal 20 of each user for a certain period of time, and based on the collected information, at least each hospital, further each department of each hospital, or each doctor of each hospital Each time, at least a time score based on the consultation time and waiting time per patient and an improvement score for each symptom based on the improvement of each user's symptoms are calculated and stored in the evaluation database 125 . Therefore, it is possible to evaluate at least a hospital, and furthermore, a clinical department or a doctor of a hospital, based on the objective index of time and the degree of symptom improvement of the user. Then, the CPU 111 transmits this evaluation score to the user terminal 20 and presents it to the user, so that the user can refer to the presented score to select a hospital, department, or doctor to undergo medical treatment. can be selected.

In addition, according to the first embodiment, evaluation results are obtained by evaluation values, that is, numerical values called scores, so that the evaluation results can be ranked according to the numerical values, and as a result, reservation candidates suitable for the user can be easily determined. be able to.

Further, according to the first embodiment, by using the correspondence database 123, it is possible to easily and quickly limit hospitals or doctors to be evaluated.

Further, according to the first embodiment, by collecting the PHR from each user terminal 20 of the user subscribing to the hospital reservation service, it is possible to easily collect the biometric data of the user.

Further, according to the first embodiment, not only the temporal evaluation but also the evaluation based on the degree of symptom improvement, which is the degree of symptom improvement, can be added to provide more suitable candidates for the user.

Further, according to the first embodiment, by using a score value, which is a scored evaluation value, and transmitting and presenting appointment candidates to the user terminal 20 together with the numerical values, the user can select a hospital to make an appointment as an index. can be provided, making it possible to facilitate user selection.

Further, according to the first embodiment, evaluation is performed based on the gender or age of the user who requested the evaluation and the gender or age of the doctor. It will be possible to make a candidate for a doctor who has

Further, according to the first embodiment, by limiting the hospitals that the user can visit according to the current location of the user who requested the evaluation or the specified location specified by the user, inappropriate hospitals are presented to the user as candidates. can reduce the chances of

In addition, according to the first embodiment, when calculating the evaluation value of a hospital or a doctor, the number of patients waiting for treatment at the present time and the future reservation status are referred to, and the hospital or doctor who can provide treatment immediately with less waiting time has a higher evaluation value. By using the score, it is possible to provide an effective means when the user unexpectedly has free time or when he or she suddenly becomes unwell and searches for a hospital that can immediately treat the patient.

In addition, when searching for a hospital that can provide medical care immediately, the number of patients waiting for medical care and the number of reserved patients The number-based correction weight may be increased, that is, the score value may be increased. Alternatively, the weight of the correction based on the attribute information in step S1113 and the correction based on the priority condition in step S1114 may be lightened, or these corrections may be skipped.

In addition, when a user makes a hospital reservation using the hospital reservation system as described above, the service server 100 may have a billing process procedure for collecting a referral fee from the hospital where the reservation is made.

Also, the hospital may provide a service that does not require a letter of introduction or reduces the fee for users who have made a reservation through the processing procedure of the service server 100 as described above.

<2> Second Embodiment Next, a second embodiment will be described.

<2-1> Configuration and <2-2> Operation The basic configuration and basic operation of the hospital reservation system according to the second embodiment are the same as those of the hospital reservation system according to the first embodiment described above. . Therefore, the description of the matters described in the first embodiment described above and the matters that can be easily inferred from the first embodiment described above will be omitted.

FIG. 15 is a flowchart illustrating an example of a processing procedure of the service server 100 in the second embodiment. The same reference numerals are given to the same processes as in FIG.

<2-2-1> Collection Operation [Step S119]
The CPU 111 of the service server 100 first determines whether or not it is time to collect the biometric data and the electronic medical record. In this embodiment, biometric data and electronic medical charts are collected at predetermined timings, such as once a day. If the CPU 111 determines that it is not the time to collect the biological data and the electronic medical record (step S119, NO), the CPU 111 advances the process to step S103. When determining that it is time to collect biological data and electronic medical records (step S119, YES), the CPU 111 advances the process to step S102.

[Step S102]
If it is determined in step S101 that it is time to collect biological data and electronic medical records (step S101, YES), the CPU 111 first executes biological data collection processing similar to that of the first embodiment.

[Step S120]
Next, the CPU 111 executes electronic medical record collection processing. In this case, unlike the electronic medical record collection process in step S110 in the first embodiment, the target hospitals are not limited, so the CPU 111 collects electronic medical record contents of all hospitals. . FIG. 16 is a flowchart illustrating an example of this electronic medical record collection process.

[Step S1201]
In the electronic medical record collection process, the CPU 111 first selects one hospital ID from the hospital IDs registered in the hospital database 121 to determine the acquisition destination hospital.

[Step S1202]
Next, the CPU 111 acquires the contents of the electronic medical record of the acquisition destination hospital from the data server 40 via the communication network NET by the communication interface 130 . The process of step S1202 is the same as the process of step S1102 in the first embodiment. That is, the CPU 111 refers to the hospital database 121 using the hospital ID, and reads specific information for specifying the hospital, such as the hospital ID, access information, hospital name, address, or telephone number. Then, the CPU 111 requests the control unit 41 of the data server 40 to transmit the description contents of the electronic medical record together with the specific information through the communication network NET by the communication interface 130 . The CPU 111 receives the contents of the electronic medical record transmitted from the data server 40 in response to this through the communication interface 130 .

In addition, if the number of electronic medical records at the receiving hospital is large, it is expected that processing will take some time. can be

[Step S1203]
Next, the CPU 111 registers information in the hospital database 121 and the collection database 124 based on the contents of the received electronic medical record. For example, for each patient ID, the CPU 111 collects information about each medical treatment described in the electronic medical record, that is, appointment date and time, reception, start of medical treatment, doctor ID, end of medical treatment, end of accounting, first visit flag, and symptoms in the collection database 124. Remember.

[Step S1204]
Next, the CPU 111 determines whether or not the collection of the contents of the electronic medical records for all hospitals indicated by the hospital IDs registered in the hospital database 121 has been completed. If it is determined that there is a hospital that has not yet collected data (step S1204, NO), the CPU 111 returns the process to step S1201 and performs the process for the next hospital. If the CPU 111 determines that the collection of electronic medical record contents from all registered hospitals has been completed (step S1204, YES), the CPU 111 advances the process to step S103.

<2-2-2> Registration Information Update Operation [Step S103] to [Step S108]
When the CPU 111 determines in step S119 that it is not the timing to collect the biological data and the electronic medical chart (step S119, NO), or after the electronic medical chart collection process in step S110 ends, the first embodiment and the Similar processing from [step S101] to [step S106] is performed. However, when it is determined in step S106 that the evaluation request has not been received (step S106, NO), the process returns to step S119. That is, the CPU 111 performs update processing of the hospital database 121 and update processing of the user database 122 . Then, the CPU 111 determines whether or not a PHR or an evaluation request has been received from any user terminal 20 . When determining that neither has been received, the CPU 111 returns the process to step S119. When determining that the PHR has been received, the CPU 111 updates the corresponding user date and biological data (“blood pressure”, “pulse”, etc.) in the user database 122 based on the received PHR. . Further, when determining that an evaluation request has been received, the CPU 111 authenticates the user using the user ID and password included in the received evaluation request, and then uses the location information and the location information included in the evaluation request. The user database 122 is updated according to the priority conditions set.

<2-2-3> Evaluation Operation [Step S109]
After receiving the evaluation request and updating the user database 122, the CPU 111 limits hospitals to be evaluated, as in the first embodiment.

[Step S121]
After that, the CPU 111 performs a number collection process for totalizing the current number of patients waiting for treatment and the number of reserved patients in each of the hospitals limited in step S109. That is, in step S120, the contents of electronic medical charts are collected at a predetermined timing, such as once a day, so the number of patients waiting for medical treatment and the number of reserved patients are not counted. Therefore, the CPU 111 collects the number of people. FIG. 17 is a flowchart illustrating an example of this number-of-persons collection process.

[Step S1211]
In the number-of-persons collection process, the CPU 111 first selects one hospital ID from the limited list of hospital IDs stored in the RAM 112 or the storage unit 120, thereby determining the acquisition destination hospital.

[Step S1212]
Next, the CPU 111 acquires the number of patients waiting for treatment and the number of reserved patients from the acquisition destination hospital through the communication network NET by the communication interface 130 . For example, the CPU 111 refers to the hospital database 121 using the hospital ID to read the access information of the hospital, and sends the current information about each doctor to the control unit 31 of the hospital server 30 of the hospital via the communication network NET by the communication interface 130 . Inquires about the number of patients waiting for treatment and the number of reserved patients at the time. Then, the CPU 111 receives, through the communication interface 130, information on the number of patients waiting for treatment and the number of reserved patients transmitted from the hospital server 30 in response to this inquiry.

[Step S1213]
Next, according to the received information on the number of patients waiting for medical treatment and the number of patients with reservations at the present time for each doctor, the CPU 111 stores items of "waiting" and "reservation status" in correspondence with each doctor's ID in the hospital database 121. Remember the number of each.

[Step S1214]
Next, the CPU 111 determines whether or not the number of people has been collected for all the hospitals indicated by the list of hospital IDs stored in the RAM 112 or the storage unit 120 . If it is determined that there is a hospital that has not yet collected data (step S1214, NO), the CPU 111 returns the process to step S1211 to perform the process for the next hospital. When determining that the number of people has been collected from all the listed hospitals (step S1214, YES), the CPU 111 advances the process to step S111.

[Step S111] to [Step S113]
After that, the CPU 111 performs the same processes as [step S111] to [step S113] as in the first embodiment. That is, the CPU 111 calculates the evaluation value only based on the contents of the limited hospital among the contents of the electronic medical records of each hospital stored in the collection database 124 . After that, the CPU 111 reads and sorts the evaluation results corresponding to the user ID of the user who requested the evaluation stored in the evaluation database 125 according to the evaluation target conditions included in the evaluation conditions, and sorts the sorted results and the evaluation target conditions. Determine reservation candidates according to The CPU 111 then transmits the determined reservation candidate to the user terminal 20 that requested the evaluation via the communication network NET through the communication interface 130 .

<2-2-4> Reservation operation, <2-2-5> End operation [Step S114] to [Step S118]
The subsequent processing from [step S114] to [step S118] is the same as in the first embodiment. However, when it is determined in step S115 that the end request has been received (step S115, YES), the process returns to step S119.

<2-3> Effects According to the above-described second embodiment, the same effects as those of the above-described first embodiment can be obtained. In addition, in the second embodiment, since the contents of electronic medical charts are collected in advance for all hospitals, the evaluation value calculation process can be executed immediately in response to an evaluation request from the user, and the evaluation result can be sent to the user with good response. can be presented.

<3> Third Embodiment Next, a third embodiment will be described.

<3-1> Configuration and <3-2> Operation The basic configuration and basic operation of the hospital reservation system according to the third embodiment are the same as those of the hospital reservation system according to the second embodiment described above. . Therefore, the description of the matters described in the above-described second embodiment and the matters that can be easily inferred from the above-described second embodiment will be omitted.

FIG. 18 is a flowchart illustrating an example of a processing procedure of the service server 100 according to the third embodiment. The same reference numerals are given to the same processes as in FIG.

<3-2-1> Collection operation and first evaluation operation [Step S119], [Step S102], [Step S120]
The CPU 111 of the service server 100 first determines whether or not it is time to collect the biometric data and the electronic medical record, as in the second embodiment. If it is determined that it is time to collect the biological data and the electronic medical record (step S119, YES), the CPU 111 performs [step S102] and [step S120] similar to those of the second embodiment. That is, the CPU 111 executes biological data collection processing similar to that of the first embodiment and electronic medical record collection processing similar to that of the second embodiment.

[Step S122]
After that, the CPU 111 executes a first evaluation calculation process for calculating an evaluation value based on the contents of the electronic medical records of each hospital stored in the collection database 124 . In this first evaluation calculation process, a time score for each doctor is calculated as an evaluation value. FIG. 19 is a flowchart illustrating an example of this first evaluation calculation process.

[Step S1221]
In the first evaluation calculation process, the CPU 111 first selects one hospital ID from among the hospital IDs registered in the hospital database 121 to determine the processing target hospital.

[Step S1112]
Next, the CPU 111 refers to the collection database 124 using the hospital ID to calculate the time score for each doctor of the processing target hospital, as in the first embodiment. CPU 111 stores the calculated time score for each doctor in RAM 112 or storage unit 120 .

[Step S1222]
Next, the CPU 111 registers the time score of each doctor belonging to the hospital, which has been calculated and stored in the RAM 112 or the storage unit 120, in the item of the total score corresponding to the corresponding doctor ID in the evaluation database 125. FIG.

[Step S1223]
Then, the CPU 111 determines whether or not calculation of the evaluation values for all the hospitals indicated by the hospital IDs stored in the hospital database 121 has been completed. When determining that there is a hospital for which evaluation values have not yet been calculated (step S1223, NO), the CPU 111 returns the process to step S1211 to perform the process for the next hospital. When determining that evaluation values have been calculated for all hospitals (step S1223, YES), the CPU 111 advances the process to step S103.

<3-2-2> Registration Information Update Operation [Step S103] to [Step S108]
[Step S103] to [Step S108] are the same as those in the first embodiment.

<3-2-3> Second Evaluation Operation [Step S109]
After receiving the evaluation request and updating the user database 122, the CPU 111 of the service server 100 selects the location from among the information stored in the priority condition items of the corresponding user in the user database 122, as in the first embodiment. The specified information limits the hospitals to be evaluated.

[Step S121]
Next, as in the second embodiment, the CPU 111 inquires the current number of patients waiting for treatment and the number of reserved patients in each of the hospitals limited in step S109, and registers the results in the hospital database 121. Perform collection processing.

[Step S123]
After that, the CPU 111 executes a second evaluation calculation process for calculating an evaluation value based on the contents of the electronic medical records of each hospital stored in the collection database 124 . FIG. 20 is a flowchart illustrating an example of this second evaluation calculation process.

[Step S1111]
In the second evaluation calculation process, the CPU 111 first selects one hospital ID from the list of hospital IDs stored in the RAM 112 or the storage unit 120, as in the first embodiment. to decide.

[Step S1231]
Then, the doctor ID of each doctor belonging to the processing target hospital is acquired from the hospital database 121, the time score corresponding to the doctor ID is read from the total score item corresponding to the doctor ID in the evaluation database 125, and the RAM 112 Alternatively, it is stored in the storage unit 120 .

[Step S1113] to [Step S1119]
The subsequent processing from [step S1113] to [step S1119] is the same as in the first embodiment. That is, the CPU 111 corrects the time score for each doctor stored in the RAM 112 or the storage unit 120 based on the attribute information and priority conditions, and further corrects it based on the number of waiting patients and the number of reserved patients. In addition, the CPU 111 refers to the user database 122 and the collection database 124 to calculate the symptom improvement score for each doctor. Then, the CPU 111 calculates a total score from the improvement score by symptom and the corrected time score for each doctor, and further calculates the department score and the hospital score from the total score for each doctor. Each score obtained is registered in the evaluation database 125 in association with the user ID. After that, the CPU 111 determines whether or not evaluation values have been calculated for all the hospitals shown in the list of hospital IDs stored in the RAM 112 or the storage unit 120. If there are hospitals for which evaluation values have not yet been calculated, , the process returns to step S1111 to perform the process for the next hospital. When determining that evaluation values have been calculated for all listed hospitals, the CPU 111 advances the process to step S112.

[Step S112], [Step S113]
The subsequent processes of [step S112] and [step S113] are the same as those of the first embodiment. That is, the CPU 111 reads and sorts the evaluation results corresponding to the user ID of the user requesting the evaluation stored in the evaluation database 125 according to the evaluation target conditions included in the evaluation conditions, and sorts the sorted results and the evaluation target conditions. Determine reservation candidates according to The CPU 111 then transmits the determined reservation candidate to the user terminal 20 that requested the evaluation via the communication network NET through the communication interface 130 .

<3-2-4> Reservation operation, <3-2-5> End operation [Step S114] to [Step S118]
The subsequent processing from [step S114] to [step S118] is the same as in the first embodiment. However, when it is determined in step S115 that the end request has been received (step S115, YES), the process returns to step S119.

<3-3> Effects According to the above-described third embodiment, the same effects as those of the above-described second embodiment can be obtained. In addition, in the third embodiment, since the user-independent evaluation value is calculated in advance, the user-dependent evaluation value calculation process can be immediately executed in response to an evaluation request from the user, and the user can evaluate the user with good response. It is possible to present the results.

The present invention is not limited to the above-described embodiments as they are, and can be embodied by modifying constituent elements without departing from the scope of the present invention at the implementation stage. Also, various inventions can be formed by appropriate combinations of the plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiments. Furthermore, constituent elements of different embodiments may be combined as appropriate.

For example, the processing procedure described with reference to the flowchart is merely an example, and each processing may be changed as much as possible. In addition, steps can be appropriately omitted, replaced, or added to the described processing procedure according to the embodiment.

Some or all of the above embodiments may also be described in the following additional remarks, but are not limited to the following.

(Appendix 1)
For each patient, in each of a plurality of hospitals, at least patient information about the patient and medical information related to each medical treatment, including the reception date and time, the medical treatment start date and time, the medical treatment end date and time, the treating doctor, and the accounting end date and time. an electronic medical record network (1) for sharing electronic medical records among the plurality of hospitals;
an electronic medical record collection unit (11) that collects the contents of the electronic medical records from the electronic medical record network;
a biometric data collection unit (12) that collects biometric data of each of a plurality of users via a communication network (NET);
a reception unit (13) that receives a request from a user terminal (20) via the communication network;
When an evaluation request and the biometric data of the user of the user terminal are received from the user terminal by the receiving unit, the biometric data of the user of the user terminal that requested the evaluation request received by the receiving unit , a limiting unit (14) for limiting an evaluation target from among the plurality of hospitals or a plurality of doctors belonging to the plurality of hospitals based on the biological data collected by the biological data collecting unit;
The plurality of hospitals limited as the evaluation target by the limiting unit by evaluation items including at least consultation time and waiting time per patient based on the description contents of the electronic medical record collected by the electronic medical record collecting unit, or an evaluation unit (15) for evaluating a doctor;
A presenting unit (16) for presenting at least one of the evaluated plurality of hospitals or doctors as a reservation candidate to the requesting user terminal via the communication network based on the evaluation result by the evaluation unit. )When,
a hospital control unit (31) provided in each of the plurality of hospitals for managing patient reservations;
When an appointment request for a hospital or a doctor selected by the user from among the appointment candidates is accepted by the accepting unit from the user terminal of the request source via the communication network, the accepting unit accepts the request. a reservation unit (17) for requesting, via the communication network, the hospital control unit of the hospital or the hospital corresponding to the doctor to make a reservation for the user of the user terminal of the request source;
A hospital reservation system comprising:

(Appendix 2)
A hospital reservation method executed by a server device having a processor (111) and a memory (112, 120),
By the processor, at least patient information about the patient in each of the plurality of hospitals, and medical information regarding each medical treatment, including the reception date and time, the medical treatment start date and time, the medical treatment end date and time, the treating doctor, and the accounting end date and time. a step of collecting the contents of electronic medical charts for each patient from an electronic medical chart network for sharing among the plurality of hospitals and storing them in the memory (S110);
a step of collecting biometric data of each of a plurality of users and storing them in the memory by the processor via a communication network (S102);
a step of receiving, by the processor, an evaluation request from a user terminal together with biometric data of a user of the user terminal via the communication network (S106);
In response to the evaluation request from the user terminal, the processor causes the biometric data of the user of the user terminal requesting the evaluation request and the biometric data of each of the plurality of users stored in the memory. a process of limiting evaluation targets from among the plurality of hospitals or a plurality of doctors belonging to the plurality of hospitals based on the above (S109);
By the processor, the plurality of hospitals or doctors limited as the evaluation targets by evaluation items including at least consultation time and waiting time per patient based on the contents of the electronic medical chart stored in the memory. a step of evaluating and storing the evaluation result in the memory (S111);
By the processor, based on the evaluation results of the plurality of hospitals or doctors stored in the memory, at least one of the evaluated plurality of hospitals or doctors is set as a reservation candidate, and the A process (S113) of causing the requesting user terminal to present the
a step of receiving, by the processor, an appointment request for a hospital or doctor selected by the user from among the appointment candidates from the user terminal of the request source via the communication network (S114);
In response to an appointment request for the hospital or doctor from the requesting user terminal, the processor manages patient appointments provided by the requested hospital or hospital corresponding to the doctor via the communication network. a process of requesting the hospital control unit to make a reservation for the user of the requesting user terminal (S116);
How to book a hospital appointment.

(Appendix 3)
The electronic medical chart collection unit (11), the biological data collection unit (12), the reception unit (13), the limitation unit (14), the evaluation unit (15), which the server device according to claim 10 comprises, A hospital reservation program that causes a processor to function as the presentation unit (16) and the reservation unit (17).

DESCRIPTION OF SYMBOLS 1... Electronic medical record network 10... Service server 11... Electronic medical record collection part 12... Biological data collection part 13... Reception part 14... Limitation part 15... Evaluation part 16... Presentation part 17... Reservation part 18... Correspondence database 19... Physician attribute Acquisition unit 20 User terminal 21, 31, 41, 110 Control unit 22 Measuring unit 23, 32, 42, 120 Storage unit 24 Biological data measuring device 30 Hospital server 33 Medical terminal 40 Data server 100 Service server 111 ... CPU
112 RAM
113 ROM
121... Hospital database 122... User database 123... Correspondence database 124... Collection database 125... Evaluation database 130... Communication interface

Claims (10)

For each patient, in each of a plurality of hospitals, at least patient information about the patient and medical information related to each medical treatment, including the reception date and time, the medical treatment start date and time, the medical treatment end date and time, the treating doctor, and the accounting end date and time. an electronic medical record network for sharing electronic medical records among the plurality of hospitals;
an electronic medical record collection unit that collects the contents of the electronic medical records from the electronic medical record network;
a biometric data collection unit that collects biometric data of each of a plurality of users via a communication network;
a reception unit that receives a request from a user terminal via the communication network;
When an evaluation request and the biometric data of the user of the user terminal are received from the user terminal by the receiving unit, the biometric data of the user of the user terminal that requested the evaluation request received by the receiving unit a limiting unit that limits evaluation targets from among the plurality of hospitals or a plurality of doctors belonging to the plurality of hospitals based on the biological data collected by the biological data collecting unit;
The plurality of hospitals limited as the evaluation target by the limiting unit by evaluation items including at least consultation time and waiting time per patient based on the description contents of the electronic medical record collected by the electronic medical record collecting unit, or an evaluation unit that evaluates a doctor;
a presenting unit that presents at least one of the evaluated plurality of hospitals or doctors as a reservation candidate to the requesting user terminal via the communication network based on the evaluation result by the evaluating unit;
a hospital control unit provided in each of the plurality of hospitals for managing patient reservations;
When an appointment request for a hospital or a doctor selected by the user from among the appointment candidates is accepted by the accepting unit from the user terminal of the request source via the communication network, the accepting unit accepts the request. a reservation unit that requests, via the communication network, the hospital control unit of the hospital or the hospital corresponding to the doctor to make a reservation for the user of the user terminal that is the request source;
A hospital reservation system comprising: The evaluation unit calculates an evaluation value representing evaluation results of the plurality of hospitals or doctors,
The presentation unit extracts, as the appointment candidates, a plurality of hospitals or doctors with the highest evaluation values calculated by the evaluation unit, and presents the extracted appointment candidates together with the evaluation values to the requesting user terminal. The hospital reservation system according to claim 1, wherein further comprising a correspondence database in which hospitals or doctors are databased according to attributes of the biometric data collected by the biometric data collection unit;
2. The restricting unit refers to the correspondence database according to the attributes of the biometric data of the user of the user terminal that is the request source, and restricts the plurality of hospitals or doctors to be evaluated. The hospital reservation system described in . 2. The hospital reservation system according to claim 1, wherein said biometric data collection unit receives, via said communication network, user's biometric data transmitted from each of a plurality of user terminals each collecting user's biometric data. The biometric data collection unit collects biometric data histories of each of the plurality of users,
The evaluation items evaluated by the evaluation unit further include the degree of symptom improvement based on the history of the biological data collected by the biological data collection unit for a certain period of time.
The hospital reservation system according to claim 1. The evaluation unit converts the evaluation results for each evaluation item into points, sets the total score as an evaluation value for doctors, and sets an average value of the evaluation values of doctors belonging to the hospital as an evaluation value for hospitals,
The presentation unit extracts, as the appointment candidates, a plurality of hospitals or doctors with the highest evaluation values calculated by the evaluation unit, and presents the extracted appointment candidates together with the evaluation values to the requesting user terminal. The hospital reservation system according to claim 1, wherein further comprising a doctor attribute acquisition unit that acquires releasable doctor attribute information including at least gender and age for each doctor belonging to each hospital;
The receiving unit further receives attribute information of the user of the user terminal of the request source,
The evaluation items evaluated by the evaluation unit further include the relationship between the attribute information of the doctor acquired by the doctor attribute acquisition unit and the attribute information of the user of the requesting user terminal received by the reception unit. 2. The hospital appointment system of claim 1, comprising: The reception unit further receives location information from the user terminal that is the request source,
The limiting unit limits the plurality of hospitals or doctors to be evaluated based on the location information from the requesting user terminal received by the receiving unit,
2. The evaluation item according to claim 1, wherein the evaluation item evaluated by the evaluation unit further includes a relationship between the location information received by the reception unit from the user terminal of the request source and the location of the hospital to be evaluated. The hospital reservation system mentioned. The hospital control unit further manages the patient's time during a current affairs stay at the hospital,
The evaluation unit accesses the hospital control unit and acquires at least the number of patients waiting for treatment at the current time and the number of patients scheduled in the future at each hospital,
2. The hospital reservation system according to claim 1, wherein the evaluation items evaluated by said evaluation unit further include said acquired number of patients waiting for treatment and number of reserved patients. For each patient, in each of a plurality of hospitals, at least patient information about the patient and medical information related to each medical treatment, including the reception date and time, the medical treatment start date and time, the medical treatment end date and time, the treating doctor, and the accounting end date and time. an electronic medical record collection unit that collects the contents of the electronic medical records from an electronic medical record network for sharing the electronic medical records among the plurality of hospitals;
a biometric data collection unit that collects biometric data of each of a plurality of users via a communication network;
a reception unit that receives a request from a user terminal via the communication network;
When an evaluation request and the biometric data of the user of the user terminal are received from the user terminal by the receiving unit, the biometric data of the user of the user terminal that requested the evaluation request received by the receiving unit a limiting unit that limits evaluation targets from among the plurality of hospitals or a plurality of doctors belonging to the plurality of hospitals based on the biological data collected by the biological data collecting unit;
The plurality of hospitals limited as the evaluation target by the limiting unit by evaluation items including at least consultation time and waiting time per patient based on the description contents of the electronic medical record collected by the electronic medical record collecting unit, or an evaluation unit that evaluates a doctor;
a presenting unit that presents at least one of the evaluated plurality of hospitals or doctors as a reservation candidate to the requesting user terminal via the communication network based on the evaluation result by the evaluating unit;
When an appointment request for a hospital or a doctor selected by the user from among the appointment candidates is accepted by the accepting unit from the requesting user terminal via the communication network, each of the plurality of hospitals provided, among the hospital control units that manage patient reservations, to the hospital control unit of the hospital that corresponds to the hospital or the doctor accepted by the reception unit, via the communication network, the user terminal of the request source a reservation unit for requesting a reservation for the user of
A server device comprising:

Images