WO2020021973A1 - Système de réservation pour hôpital et dispositif serveur - Google Patents

Système de réservation pour hôpital et dispositif serveur Download PDF

Info

Publication number
WO2020021973A1
WO2020021973A1 PCT/JP2019/026079 JP2019026079W WO2020021973A1 WO 2020021973 A1 WO2020021973 A1 WO 2020021973A1 JP 2019026079 W JP2019026079 W JP 2019026079W WO 2020021973 A1 WO2020021973 A1 WO 2020021973A1
Authority
WO
WIPO (PCT)
Prior art keywords
hospital
evaluation
unit
user
reservation
Prior art date
Application number
PCT/JP2019/026079
Other languages
English (en)
Japanese (ja)
Inventor
出野　徹
直樹 土屋
貴広 濱口
洋貴 和田
佐藤　博則
湯本　将彦
山内　隆伸
和 松岡
Original Assignee
オムロンヘルスケア株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by オムロンヘルスケア株式会社 filed Critical オムロンヘルスケア株式会社
Publication of WO2020021973A1 publication Critical patent/WO2020021973A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms

Definitions

  • the present invention relates to a hospital reservation system and a server device.
  • Patent Literature 1 proposes a technology that allows a patient to select an appropriate doctor based on evaluations of a plurality of doctors, for receiving treatment for his or her own disease.
  • the evaluation of a doctor is to present information about the doctor to a plurality of other doctors, and the other doctor evaluates the information based on the information, which is likely to be a subjective evaluation.
  • a doctor suitable for the user or a candidate for a hospital to which the doctor belongs is presented to the user based on the objective index, and the user cannot select and make a reservation from the candidates.
  • the present invention has been made in view of the above circumstances, and an object of the present invention is to present a candidate of a hospital or a doctor suitable for a user based on an objective index, and to reserve a hospital according to the selection of the user. It is to provide a hospital reservation system and a server device which can perform the above.
  • the present invention employs the following configuration in order to solve the above-described problems.
  • the hospital reservation system at each of the plurality of hospitals, at least patient information on the patient and, for each medical treatment, the reception date and time, medical treatment start date and time, medical treatment end date and time, medical doctor, and accounting end date and time.
  • An electronic medical record network for sharing an electronic medical record for each patient among the plurality of hospitals, the electronic medical record network describing the electronic medical record, and an electronic medical record collection unit that collects the contents of the electronic medical record from the electronic medical record network.
  • a biometric data collection unit for collecting biometric data of each of a plurality of users
  • a reception unit for receiving a request from a user terminal via the communication network, and an evaluation from the user terminal by the reception unit
  • the receiving unit receives the request.
  • An evaluation unit that evaluates the plurality of hospitals or doctors limited as the evaluation target, and based on an evaluation result by the evaluation unit, at least one of the evaluated plurality of hospitals or doctors is a reservation candidate.
  • a hospital is a small group of hospitals in one building, a large-scale hospital with multiple wards on one site, and a hospital group including affiliated hospitals distributed in multiple regions. May be.
  • the electronic medical records may be distributed for each hospital in the group. Further, the electronic medical record may be arranged in a data center provided in the electronic medical record network instead of in the hospital.
  • the arrangement includes being stored in a storage unit having a storage medium.
  • the data format of the electronic medical record may be different for each hospital, and the electronic medical record of each hospital can be converted into a unified format in the electronic medical record network and stored in the storage unit of the data center.
  • confidentiality is ensured by data encryption or the like.
  • access permissions are limited for each medical worker, and medical terminals operated by each medical worker can view and update information on electronic medical records located at the hospital or data center. It has become.
  • a limited access right is given to each user who is a patient, and the user terminal operated by each user can browse information of the electronic medical record arranged in the data center.
  • the hospital reservation system in response to an evaluation request from an arbitrary user terminal, a hospital or a doctor limited based on the biometric data of the user of the user terminal and the collected biometric data of a plurality of users.
  • the evaluation is made by an objective index of time, and a reservation candidate is presented to the user based on the evaluation result, and a hospital reservation is made according to the selection of the user of the user terminal of the evaluation request source.
  • presenting a hospital or doctor candidate suitable for the user the user can easily select a hospital, and can easily reserve a hospital according to the selection.
  • the evaluation unit calculates an evaluation value representing an evaluation result of the plurality of hospitals or doctors
  • the presentation unit calculates a plurality of hospitals or doctors in descending order of the evaluation value calculated by the evaluation unit.
  • a doctor can be extracted as the reservation candidate, and the extracted reservation candidate can be presented to the requesting user terminal together with the evaluation value. According to this configuration, it is possible to rearrange in the order of the evaluation values by using the numerical value called the evaluation value, and it is possible to easily present the reservation candidates suitable for the user.
  • 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 includes The plurality of hospitals or doctors to be evaluated may be limited by referring to the correspondence database based on 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 the hospitals or doctors to be evaluated.
  • the biometric data collection unit may receive, via the communication network, the biometric data of the user transmitted from each of the plurality of user terminals that collect the biometric data of the user. According to this configuration, the biometric data can be easily collected by collecting the biometric data from each user terminal of a user who subscribes to the hospital reservation service.
  • the biometric data collection unit may collect the history of the biometric data of each of the plurality of users, and the evaluation items evaluated by the evaluation unit may further include the biometric data collected by the biometric data collection unit.
  • the degree of symptom improvement based on a certain period of history of the data may be included. According to this configuration, it is possible to provide a candidate more suitable for the user by adding an evaluation based on the symptom improvement degree, ie, the symptom improvement degree.
  • the evaluation unit scores the evaluation result for each evaluation item, sets a total score for a doctor as an evaluation value, and sets a mean value of evaluation values of doctors belonging to the hospital as an evaluation value for a hospital.
  • the presentation unit extracts a plurality of hospitals or doctors from the higher evaluation value calculated by the evaluation unit as the reservation candidate, and extracts the extracted reservation candidate together with the evaluation value to the user terminal of the request source. Can be presented. According to this configuration, by using the scored evaluation value and presenting the reservation candidate together with the numerical value, it is possible to provide an index for selecting a hospital to be reserved by the user, thereby facilitating the selection of the user. It becomes possible.
  • the hospital reservation system further includes a doctor attribute acquisition unit that acquires doctor attribute information that can be disclosed including at least gender and age for each doctor belonging to each hospital
  • the reception unit includes: Further, the attribute information of the user of the user terminal of the request source that receives the attribute information and is evaluated by the evaluation unit further includes attribute information of the doctor acquired by the doctor attribute acquisition unit and the reception unit. And the attribute of the user terminal of the request source accepted by the user with the attribute information of the user.
  • the evaluation is performed based on the gender or age of the user to whom the evaluation value should be presented and the gender or age of the doctor, so that a doctor suitable for the user can be highly evaluated, and a doctor more suitable for the user. Becomes a candidate.
  • the receiving unit may further receive position information from the requesting user terminal, and the limiting unit may receive the position information from the requesting user terminal received by the receiving unit.
  • the plurality of hospitals or doctors to be evaluated is limited, and the evaluation items evaluated by the evaluation unit further include the position information from the user terminal of the request source received by the reception unit. , The relationship with the position of the hospital to be evaluated. According to this configuration, the possibility of presenting an inappropriate hospital to the user as a candidate is limited by limiting the hospitals that the user can visit according to the current position of the user requesting the evaluation and the designated position specified by the user. Can be smaller.
  • the hospital control unit further performs time management of a patient during stay at the current affairs of the hospital, and the evaluation unit accesses the hospital control unit, and at least a current time of each hospital.
  • the evaluation item obtained by acquiring the number of patients waiting for medical treatment and the number of patients reserved in the future and evaluating by the evaluation unit can further include the acquired number of patients waiting for medical treatment and the number of reserved patients. According to this configuration, it is possible to present hospital or doctor candidates in consideration of the current waiting time of each hospital.
  • the server device at each of the plurality of hospitals, at least the patient information on the patient and, for each medical treatment, reception date and time, medical treatment start date and time, medical treatment end date and time, medical doctor, and accounting end date and time.
  • An electronic medical record collection unit that collects the contents of the electronic medical record, from the electronic medical record network for sharing the electronic medical record for each patient, which includes the medical information,
  • a biometric data collection unit that collects biometric data of each of a plurality of users, a reception unit that receives a request from a user terminal via the communication network, an evaluation request from the user terminal by the reception unit, and the user terminal
  • the user of the request source of the evaluation request received by the reception unit is received.
  • the evaluation target is limited from among the plurality of doctors belonging to the plurality of hospitals or the plurality of hospitals.
  • the limiting unit based on the contents of the electronic medical record collected by the electronic medical record collecting unit, by an evaluation item including at least a medical treatment time and a waiting time per patient, the limited unit is limited by the limiting unit as the evaluation target
  • An evaluation unit that evaluates a plurality of hospitals or physicians, and, based on an evaluation result by the evaluation unit, at least one of the plurality of evaluated hospitals or physicians as a reservation candidate, the request via the communication network.
  • the server apparatus determines a time limit for a hospital or a doctor limited based on the biometric data of the user of the user terminal and the collected biometric data of the plurality of users.
  • a reservation candidate based on the evaluation result is transmitted to the user terminal requesting the evaluation and presented to the user, and a hospital reservation is performed according to the selection of the user of the user terminal.
  • the present invention it is possible to provide a technology capable of presenting a candidate for a hospital or a doctor suitable for a user based on an objective index, and making a reservation for a hospital according to the selection of the user.
  • FIG. 1 is a block diagram schematically illustrating an example of the configuration of the hospital reservation system according to the embodiment.
  • FIG. 2 is a block diagram illustrating an example of the overall configuration of the hospital reservation system according to the first embodiment.
  • FIG. 3 is a diagram illustrating an example of storage contents of a hospital database.
  • FIG. 4 is a diagram illustrating an example of the contents stored in the user database.
  • FIG. 5 is a diagram illustrating an example of the storage content of the correspondence database.
  • FIG. 6 is a diagram illustrating an example of the storage contents of the collection database.
  • FIG. 7 is a diagram illustrating an example of the storage contents of the evaluation database.
  • FIG. 8 is a flowchart illustrating an example of a processing procedure of the service server.
  • FIG. 1 is a block diagram schematically illustrating an example of the configuration of the hospital reservation system according to the embodiment.
  • FIG. 2 is a block diagram illustrating an example of the overall configuration of the hospital reservation system according to the first embodiment.
  • FIG. 3
  • FIG. 9 is a flowchart illustrating an example of a processing procedure of the user terminal.
  • FIG. 10 is a flowchart illustrating an example of the evaluation process in FIG.
  • FIG. 11 is a flowchart illustrating an example of the electronic medical record collection process in FIG.
  • FIG. 12 is a flowchart illustrating an example of the evaluation calculation process in FIG.
  • FIG. 13 is a diagram for describing an example of a history of biometric data.
  • FIG. 14 is a diagram for explaining another example of the history of the biometric data.
  • FIG. 15 is a flowchart illustrating an example of a processing procedure of the service server in the hospital reservation system according to the second embodiment.
  • FIG. 16 is a flowchart illustrating an example of the electronic medical record collection process in FIG. FIG.
  • FIG. 17 is a flowchart illustrating an example of the headcount collection process in FIG.
  • FIG. 18 is a flowchart illustrating an example of a processing procedure of the service server in the hospital reservation system according to the third embodiment.
  • FIG. 19 is a flowchart illustrating an example of the first evaluation calculation process in FIG.
  • FIG. 20 is a flowchart illustrating an example of the second evaluation calculation process in FIG.
  • FIG. 1 schematically illustrates an example of a configuration of a hospital reservation system according to the embodiment.
  • the hospital reservation system includes an electronic medical record network (EHR: Electronic Health Records) 1 and a service server 10 connected to a communication network NET such as the Internet.
  • the service server 10 can be connected to a plurality of user terminals 20 via the communication network NET.
  • the electronic medical record network 1 includes, at least in each of a plurality of hospitals, patient information relating to a patient and medical treatment information including a reception date / time, a medical treatment start date / time, a medical treatment end date / time, a medical doctor, and a transaction end date / time regarding each medical treatment.
  • This is a network for sharing the described electronic medical records (EMR: Electronic Medical Records) for each patient among a plurality of hospitals.
  • EMR Electronic Medical Records
  • the electronic medical record network 1 is configured, for example, by connecting 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. It should be noted that the electronic medical record network 1 may use a dedicated communication line instead of the Internet as the communication network NET.
  • the data server 40 needs to 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).
  • the hospital server 30 includes, for example, a personal computer (PC) operated by a medical staff such as a doctor, a nurse, a laboratory technician, and a clerk in the hospital, an automatic reception machine and an automatic accounting machine operated by a visiting patient. , Etc., are connected via a hospital LAN (Local Area Network) or the like.
  • the hospital LAN may be a wired LAN, a wireless LAN, or a LAN in which wired and wireless are mixed.
  • the hospital server 30 includes an internal image capturing device such as a biological data measuring device that measures biological data such as a patient's blood pressure value and a CT (Computerized @ Tomography) device that captures an internal image of the patient.
  • an internal image capturing device such as a biological data measuring device that measures biological data such as a patient's blood pressure value and a CT (Computerized @ Tomography) device that captures an internal image of the patient.
  • Various types of inspection equipment including devices can be connected via a hospital LAN or the like.
  • Hospitals can be small hospitals, one room in a building, large hospitals with multiple wards located on one site, and hospital groups that include affiliated hospitals distributed in multiple regions. good.
  • the hospital server 30 may be provided for each hospital in the group, or one hospital server 30 may be arranged in one main hospital, and the 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.
  • 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.
  • control unit 31 in the hospital server 30 includes, for example, a processor such as a CPU (Central Processing Unit) and an MPU (Micro Processing Unit) and a memory such as a RAM (Random Access Memory) and a ROM (Read Only Memory). And can be included.
  • the ROM stores, for example, a program executed by the processor.
  • the RAM is, for example, a memory used by the processor as a work memory.
  • the storage unit 32 can store, for example, a program executed by a processor of the control unit 31, setting data necessary for executing the program, and various databases.
  • Programs executed by the processor of the control unit 31 include, for example, an electronic medical record management program for browsing and updating the electronic medical record, a reservation management program for managing patient reservations, a reception time for each patient staying at the hospital, and the like. Management time management program, and the like.
  • the setting data required to execute the program can include, for example, an access address of the data server 40 of the data center.
  • the database includes, for example, a medical worker database that stores information on each medical worker including the authority and password of the medical worker operating the medical terminal 33, an electronic medical record database that stores an electronic medical record (EMR) of each patient, a reservation.
  • EMR electronic medical record
  • the storage unit 32 may include a reservation database that stores the status, and the like. It is not essential for the storage unit 32 of each hospital to store all of the programs, setting data, and databases as described above, and also stores programs, setting data, and databases other than those described above. Is also good.
  • the storage medium included in the storage unit 32 stores information such as a program stored in an electronic, magnetic, optical, mechanical, or chemical operation so that a computer or a machine can read information such as a recorded program. Any medium may be used as long as the medium accumulates the data.
  • an EEPROM registered trademark
  • the storage unit 32 may be used as a work memory by the processor of the control unit 31.
  • the processor of the control unit 31 executes, for example, an electronic medical record management program stored in the storage unit 32, and stores the contents of the electronic medical record stored in the storage unit 32 according to the operation of each medical terminal 33. The information can be displayed on the medical terminal 33 or the content of the electronic medical record can be updated.
  • the processor of the control unit 31 can also add, for example, inspection data from an inspection device (not shown) to the electronic medical record.
  • the processor of the control unit 31 can communicate with the data server 40 via a communication network NET or a dedicated communication line by a communication interface (not shown), for example. Communication by 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 transmit, for example, the electronic medical records stored in the storage unit 32 to the data server 40 of the data center.
  • the processor of the control unit 31 can convert the electronic medical record into a common data format of the electronic medical record network 1 and transmit it after, for example, encrypting it.
  • the processor of the control unit 31 receives, from the data server 40, an electronic medical record created in another hospital and stored in the data server 40 in a common format, for example, decrypts the received electronic medical record, and After changing to the chart format, the chart can be registered in the electronic chart database of the storage unit 32.
  • the processor of the control unit 31 executes, for example, a reservation management program stored in the storage unit 32 to make 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.
  • the reservation database can be updated by receiving the reservation.
  • the processor of the control unit 31 acquires, for example, the reception date and time, the medical treatment start date and time, the medical treatment end date and time, the medical doctor, and the accounting end date and time by executing the time management program stored in the storage unit 32, for example. Then, it is also possible to manage the time of each patient during the current stay at the hospital.
  • the processor of the control unit 31 executes, for example, the electronic medical record management program, and obtains the medical information including the reception date and time, the medical treatment start date and time, the medical treatment end date and time, the medical doctor, and the accounting end date and time of each of the acquired patients. Can be described 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).
  • the control unit 41 can include, for example, a processor such as a CPU and an MPU, and a memory such as a RAM and a ROM.
  • the ROM stores, for example, a program executed by the processor.
  • the RAM is, for example, a memory used by the processor as a work memory. When the processor executes a necessary program, the control unit 41 can perform various operations.
  • the storage unit 42 can store, for example, a program executed by the processor of the control unit 41, setting data required for executing the program, and various databases.
  • the program executed by the processor of the control unit 41 includes, for example, an electronic medical record processing program for processing an electronic medical record transmitted from each hospital server 30 via the communication network NET or a dedicated communication line, the service server 10 and the user terminal. 20 and a communication program for transmission.
  • the database includes, for example, an access authority database storing the authority and password of a medical worker operating the medical terminal 33 and the user operating the user terminal 20, the authority of the service server 10, and the electronic information of each patient received from the hospital server 30.
  • An electronic medical record database that stores medical records (EMR) may be included.
  • the storage unit 42 may store programs and databases other than those described above.
  • the storage medium included in the storage unit 42 stores information such as a program stored in an electronic, magnetic, optical, mechanical, or chemical operation so that a computer or a machine can read information such as a recorded program. Any medium may be used as long as the medium accumulates the data.
  • a storage medium included in the storage unit 42 an EEPROM or the like can be used.
  • the storage unit 42 may be used as a work memory by the processor of the control unit 41.
  • the processor of the control unit 41 communicates with each hospital server 30 via the communication network NET or a dedicated communication line, for example, by executing an electronic medical record processing program stored in the storage unit 42.
  • the encrypted electronic medical record transmitted from the electronic medical record 30 can be decrypted and registered in the electronic medical record database of the storage unit 42, for example.
  • the processor of the control unit 41 encrypts the electronic medical record stored in the electronic medical record database of the storage unit 42 in a common format, for example, and encrypts the electronic medical record. It can be transmitted to the hospital server 30.
  • the storage unit 32 of the hospital server 30 does not have an electronic medical record database.
  • the electronic medical record stored in the storage unit 42 of the data server 40 can be virtually used as the electronic medical record included in the hospital server 30 of the hospital C. Therefore, the processor of the control unit 41 executes, for example, the electronic medical record processing program stored in the storage unit 42, and performs the medical treatment via the communication network NET or the dedicated communication line and the hospital server 30 of the hospital C. By acquiring operation information from the terminal 33, processing on the electronic medical record can be performed. Further, the processor of the control unit 41 can communicate with the service server 10 or the user terminal 20 via the communication network NET, for example, by executing a communication program stored in the storage unit 42.
  • control unit 31 of the hospital server 30 may convert the electronic medical record of the original data format stored in the storage unit 32 into the common data format of the electronic medical record network 1 and then transmit the converted data. Not required. From the hospital server 30 of each hospital, an electronic medical record in a unique data format may be transmitted to the data center after being encrypted, for example.
  • the control unit 41 of the data server 40 that has received the data, for example, decodes the received electronic medical record, converts the data format into a common data format of the electronic medical record network 1, and stores the electronic medical record in the storage unit 42. What is necessary is just to store it in a database.
  • control unit 41 of the data server 40 converts the electronic medical record of the common data format into a data format unique to each hospital, and then, for example, What is necessary is just to encrypt and transmit.
  • each medical worker can access from the medical terminal 33 the storage unit 32 or the data of the hospital server 30 of the own hospital to which access is permitted.
  • Information on the electronic medical record stored in the storage unit 42 of the data server 40 at the center can be viewed. If the authority is given, each medical worker can also update the electronic medical record from the medical terminal 33.
  • the user terminal 20 may be a general smart phone (smartphone) or a smart device such as a tablet terminal having a function of connecting to the communication network NET.
  • the user terminal 20 includes, 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. Further, the user terminal 20 can be connected to the biological data measurement device 24.
  • the communication interface can include, for example, a Wi-Fi® module.
  • 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 a display screen thereof, and operation buttons provided on a housing of the smart device.
  • control unit 21 of the user terminal 20 can include, for example, a processor such as a CPU and an MPU and a memory such as a RAM and a ROM.
  • the ROM stores, for example, a program executed by the processor.
  • the RAM is, for example, a memory used by the processor as a work memory.
  • the measuring unit 22 measures various types of biological data of the user.
  • the measurement unit 22 can measure a pulse rate by using a camera and an LED flashlight generally provided in a smart device as a photoplethysmograph (PPG (Photo @ Plethysmography) sensor).
  • PPG Photo @ Plethysmography
  • a smart device capable of measuring a blood pressure by adding a pressure sensor.
  • the biometric data measurement device 24 is a device that can measure one or a plurality of various biometric data such as electrocardiogram, pulse, blood pressure, weight, body fat percentage, and the like.
  • the biometric data measurement device 24 performs short-range wireless communication with the control unit 21 of the user terminal 20, for example.
  • each of the user terminal 20 and the biometric data measurement device 24 can have a BLE communication module that employs a short-range wireless data communication standard such as Bluetooth (registered trademark), but is not limited thereto.
  • the biological data measurement 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 applications).
  • the control unit 21 can perform various operations.
  • the control unit 21 can access the service server 10 using a smartphone application, a Web browser, or the like.
  • a limited access right is given to each user who is a patient, and each user accesses the data server 40 from the user terminal 20 and accesses the data server 40 stored in the storage unit 42.
  • the user may be able to view the information on the electronic medical records for which the permission has been granted.
  • the user terminal 20 may have a GPS (Global Positioning System) receiver.
  • the user terminal 20 can use the location information of the user terminal acquired by the GPS receiver or the Wi-Fi module with the smartphone application, and can transmit the location information to the service server 10 or the like via the communication network NET as necessary. Has become.
  • the storage unit 23 can store the user's biological data acquired by the measurement unit 22 and the biological data measurement device 24 as PHR (Personal Health Records). That is, the user of the user terminal 20 can store the medical / health record managed by the user for a certain period or more in the storage unit 23.
  • PHR Personal Health Records
  • the service server 10 operating as a server device can include, 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 and the data server 40 or the hospital server 30 of the electronic medical record network 1 via the communication network NET. Communication by the communication interface is not limited to a specific communication method.
  • the control unit can include, for example, a processor such as a CPU and an MPU, and a memory such as a RAM and a ROM.
  • the ROM stores, for example, a program executed by the processor.
  • the RAM is, for example, a memory used by the processor as a work memory.
  • control unit When the processor executes the necessary programs, the control unit performs the following operations: the electronic medical record 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, 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 accesses, for example, the data server 40 of the data center in the electronic medical record network 1 via the communication network NET, and collects the contents of the electronic medical record of each hospital stored in the storage unit 42. Can be.
  • the electronic medical record collection unit 11 requests the control unit 41 of the data server 40 to transmit the description contents of the electronic medical record, and receives the electronic medical record transmitted from the data server 40, thereby transmitting the description contents of the electronic medical record. collect.
  • the biometric data collection unit 12 can, for example, collect biometric data stored in the storage unit 23 of each user terminal 20 via the communication network NET. For example, every time the biometric data is acquired by the measurement unit 22 or the biometric data measurement device 24 in the user terminal 20, the biometric data collection unit 12 transmits the acquired biometric data from the user terminal 20 to the service server 10, The biological data stored in the storage unit 23 of each user terminal 20 can be collected. Alternatively, the biometric data collection unit 12 requests the control unit 21 of each user terminal 20 to transmit the biometric data stored in the storage unit 23 for at least a certain period, and transmits the biometric data transmitted from each user terminal 20 for at least a certain period. It is also possible to collect biometric data by receiving the biometric data.
  • the receiving unit 13 receives a request from the user terminal 20 via the communication network NET, for example.
  • the request received by the reception unit 13 can include an evaluation request for requesting the presentation of a hospital candidate and a hospital reservation request for requesting a reservation to a hospital.
  • 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.
  • the latest biometric data stored as PHR in the storage unit 23 may be transmitted together.
  • the hospital reservation request includes information indicating the hospital or doctor requesting the reservation.
  • the limiting unit 14 limits the evaluation target to be evaluated when, for example, the receiving unit 13 receives the evaluation request and the biometric data of the user of the user terminal 20 from the user terminal 20 via the communication network NET.
  • the limiting unit 14 may be configured to store a plurality of hospitals or a plurality of hospitals based on the biometric data of the user of the user terminal 20 that has requested the evaluation
  • An evaluation target to be evaluated can be limited from among a plurality of doctors belonging to a hospital.
  • the evaluation unit 15 may, for example, identify a plurality of hospitals or doctors limited as evaluation targets by the limitation unit 14 based on the contents of the electronic medical record collected by the electronic medical record collection unit 11 and at least consultation time and waiting time per patient. Evaluate by evaluation items including time.
  • the medical treatment time is the time from the start of the medical treatment of the patient to the end of the medical treatment
  • the waiting time is the total of the time from the reception of the patient to the start of the medical treatment and the time from the end of the medical treatment to the end of the accounting.
  • the presentation unit 16 sets at least one of the plurality of evaluated hospitals or doctors as a reservation candidate to the user terminal 20 of the evaluation request source via the communication network NET. By transmitting, the reservation candidate can be presented to the user terminal 20.
  • the reservation unit 17 receives a hospital reservation request for the hospital or doctor selected by the user from the presented reservation candidates from the evaluation request source user terminal 20 via the communication network NET by the reception unit 13, for example.
  • the user requests the corresponding hospital to make a reservation.
  • the reservation unit 17 sends a request to the control unit 31 of the hospital server 30 corresponding to the hospital or the doctor indicated by the hospital reservation request, which operates as a hospital control unit that performs patient reservation management, via the communication network NET. It is possible to request the reservation of the user of the user terminal 20 of the reservation request source, that is, the evaluation request source.
  • the correspondence database 18 is, for example, a database of hospitals or doctors according to the attributes of the biometric data collected by the biometric data collection unit 12.
  • the limiting unit 14 can limit the plurality of hospitals or doctors to be evaluated with reference to the correspondence database 18 based on the attribute of the biometric data of the user of the user terminal 20 that has requested the evaluation.
  • the doctor attribute acquisition unit 19 can acquire doctor attribute information that can be disclosed, including at least gender and age, for each doctor belonging to each hospital.
  • the data server 40 has a database in which doctor attribute information of doctors belonging to each hospital is registered, and this database is, for example, controlled by the control unit 31 of the hospital server 30 in each hospital. It is updated every time there is a change in the doctor to which it belongs. Therefore, the doctor attribute acquisition unit 19 can acquire doctor attribute information from the control unit 41 of the data server 40 via, for example, the communication network NET.
  • many hospitals provide a web page or the like for hospital introduction by the hospital server 30 or another web server, and publish doctor attribute information which can be disclosed by a doctor belonging thereto. 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 receiving unit 13 can further receive the attribute information of the user of the user terminal 20 that is the requester of the evaluation via the communication network NET, and the evaluation items to be evaluated by the evaluating unit 15 further include the doctor attribute obtaining unit 19 And the attribute information of the user of the user terminal 20 of the evaluation request source received by the receiving unit 13 can be included.
  • the attribute information of the user may be transmitted together with the evaluation request from the user terminal 20, or may be received by the receiving unit 13 when the user subscribes to the service provided by the service server 10, and the information of the user who is the subscriber May be registered in a user database (not shown).
  • the patient first receives the patient at the automatic reception machine or 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 worker.
  • 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 based on the patient information.
  • control unit 31 when a medical practice such as medical treatment, diagnosis, treatment, or the like of a patient by a doctor, or a medical examination operation of a patient by a nurse or a laboratory technician is performed, for example, the medical treatment start date and time, Information such as the end date and time, medical doctor, medical treatment content, prescription, test results, and the like are input to the control unit 31.
  • the control unit 31 writes, for example, the input information in the electronic medical record database of the patient in the electronic medical record database stored in the storage unit 32, that is, stores the input information.
  • the control unit 31 calculates the payment amount of 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.
  • the settlement information is input to the control unit 31 from a medical terminal 33 such as an automatic teller machine or a PC operated by a medical worker.
  • the control unit 31 stores, for example, the settlement information in the storage unit 32, and also describes or stores the accounting end date and time in the electronic medical record of the patient in the electronic medical record database stored in the storage unit 32.
  • the control unit 31 transmits, for example, information to be described in the electronic medical record.
  • the data is transmitted to the data server 40 via the network NET or the dedicated line.
  • the control unit 41 of the data server 40 updates, for example, the content of the electronic medical record of the corresponding patient in the electronic medical record database stored in the storage unit 42 based on the received information.
  • control unit 31 transmits the entire electronic medical record or the updated content to the communication network NET or The data is transmitted to the data server 40 via the dedicated line.
  • the control unit 41 of the data server 40 updates, for example, the content of the electronic medical record of the corresponding patient 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 transmits the electronic medical record 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 via a communication interface (not shown) at regular intervals.
  • a transmission request can be transmitted.
  • the contents of the electronic medical record transmitted from the data server 40 are received and stored in a storage unit (not shown).
  • patient information including personal information such as a name and an address identifying a patient and examination information on the patient is described. .
  • each electronic medical record medical treatment information, such as a reception date and time, a medical treatment start date and time, a medical treatment end date and time, a medical doctor, and a transaction end date and time, for each medical treatment of the patient is described.
  • the electronic chart description transmission request transmitted to the data server 40 includes collection target information that specifies information to be collected, and the electronic medical record collection unit 11 includes at least medical care information in the collection target information.
  • the request for transmitting the contents of the electronic medical record can include collection period information indicating a period during which information should be collected.
  • the electronic medical record collection unit 11 updates the storage contents of the storage unit (not shown) with the contents of the received electronic medical record.
  • the control unit 21 stores the acquired biometric data in the storage unit 23 as a PHR. Further, the control unit 21 can transmit the obtained biometric data to the service server 10 via a communication network NET via 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 stored in a storage unit (not shown). The received biometric data is additionally stored in the biometric data history of each user of the user terminal 20. Alternatively, the biometric data collection unit 12 requests the control unit 21 of each user terminal 20 to transmit the biometric data stored in the storage unit 23 for at least a certain period, and transmits the biometric data transmitted from each user terminal 20 for at least a certain period. By receiving the biometric data, the biometric data is collected.
  • the receiving unit 13 receives the evaluation request via a communication interface (not shown).
  • the limiting unit 14 stores the biometric data of the user of the user terminal 20 that has received the evaluation request together with the evaluation request in a storage unit (not shown). Based on biometric data collected from a plurality of users, an evaluation target to be evaluated is limited from among a plurality of hospitals or a plurality of doctors belonging to a plurality of hospitals. For example, the limiting unit 14 can limit the plurality of hospitals or doctors to be evaluated with reference to the correspondence database 18 based on the attributes of the biometric data of the user of the user terminal 20 that has made the evaluation request.
  • the evaluation request from the user terminal 20 includes a current position of the user terminal 20 acquired by the GPS receiver or the Wi-Fi module, and a position such as a designated position designated by a user input via a user interface (not shown). Information can be included.
  • the designated position can include, for example, address information such as the user's home and work location. Further, 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 the position information.
  • the evaluation unit 15 includes, among the contents of the electronic medical record collected by the electronic medical record collection unit 11 and stored in the storage unit (not shown), the electronic medical record corresponding to the hospital or the doctor limited as the evaluation target by the limiting unit 14 in this way. Is evaluated based on the evaluation items including at least the consultation time and the waiting time per patient based on the description contents, thereby evaluating the limited plurality of hospitals or doctors, and storing the evaluation results in a storage unit (not shown). I do.
  • the evaluation items evaluated by the evaluation unit 15 can include a degree of improvement of a symptom based on a history of biometric data collected by the biometric data collection unit 12 and stored in a storage unit (not shown) for a certain period. Further, the evaluation item evaluated by the evaluation unit 15 may include a relationship between the position information from the user terminal 20 that is the evaluation request source and the position of the hospital limited as the evaluation target.
  • the time spent in a hospital will be long, and it is not desirable to use the waiting time as it is when evaluating the hospital or doctor. Therefore, if there is a record of the examination performed in the contents of the electronic medical record collected by the electronic medical record collection unit 11 and stored in the storage unit (not shown), the time information of the medical treatment is not used for the evaluation of the hospital or the doctor. Alternatively, time is used by multiplying it by some coefficient. In addition, when collecting the contents of the electronic medical record in the electronic medical record collection unit 11, the information on the number of medical examinations in which the record of the examination is present may not be collected.
  • the evaluation request from the user terminal 20 can include user attribute information including at least gender and age for the user of the user terminal 20.
  • 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.
  • the doctor attribute acquisition unit 19 acquires openable doctor attribute information including at least gender and age for each doctor belonging to each hospital, and stores it in a storage unit (not shown).
  • the evaluation items evaluated by the evaluation unit 15 can include the relationship between the user attribute information and the doctor attribute information stored in the storage unit (not shown).
  • the control unit 31 of the hospital server 30 manages the time of the patient during the current affairs of the hospital.
  • the evaluation unit 15 transmits, via a communication interface (not shown), the control unit 31 of the hospital server 30 of the limited hospital or the hospital to which the limited physician belongs via the communication network NET, and at least the patient waiting for medical treatment at each hospital at the present time.
  • the number of patients and the number of reserved patients in the future can be obtained by inquiring.
  • the evaluation items evaluated by the evaluation unit 15 can include the acquired number of patients waiting for medical treatment and the number of reserved patients.
  • the presentation unit 16 sets at least one of the plurality of evaluated hospitals or doctors as a reservation candidate, and requests an evaluation request via a communication network NET by a communication interface (not shown).
  • the message is transmitted to the original user terminal 20.
  • the smartphone application or Web browser of the user terminal 20 that has received the reservation candidate presents it to the user.
  • the evaluation unit 15 calculates an evaluation value representing an evaluation result of a plurality of hospitals or doctors limited as evaluation targets, and the presentation unit 16 selects a plurality of hospitals or doctors as reservation candidates from the higher evaluation value.
  • the extracted reservation candidate may be transmitted to the user terminal 20 of the evaluation request source together with the evaluation value.
  • the evaluation unit 15 converts the evaluation result for each evaluation item into a score, sets a total score for a doctor as an evaluation value, and sets a mean value of evaluation values of doctors belonging to the hospital as a evaluation value for a hospital. good.
  • the presentation unit 16 extracts a plurality of hospitals or doctors from the one with the highest evaluation value calculated by the evaluation unit 15 as the reservation candidate, and sends the extracted reservation candidate together with the evaluation value to the user terminal 20 that is the evaluation request source. Can be sent.
  • the user terminal 20 When a patient who is the user of the user terminal 20 that has requested the evaluation and sees the reservation candidate presented on the user terminal 20 performs a reservation operation for a desired hospital using a user interface (not shown) on a smartphone application or a Web browser, the user terminal The control unit 21 of 20 transmits a hospital reservation request to the service server 10 through a communication interface (not shown) via the communication network NET.
  • the reservation unit 17 When the reception unit 13 of the service server 10 receives the hospital reservation request via a communication interface (not shown), the reservation unit 17 responds to the request by selecting the hospital selected by the user included in the hospital reservation request or the hospital to which the doctor belongs. Identify and request the hospital to make a reservation for the user. For example, the reservation unit 17 requests the control unit 31 of the hospital server 30 of the specified hospital to reserve the user of the user terminal 20 of the hospital reservation request source, that is, the evaluation request source via the communication network NET by a communication interface (not shown). Ask for.
  • the control unit 31 of the hospital server 30 that operates as a hospital control unit that manages a patient's reservation determines whether or not the reservation can be made, and if the reservation can be made, registers the patient's reservation.
  • 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 via a communication interface (not shown) and returns the result to the user terminal 20 that has issued the reservation request.
  • the reservation request transmitted from the reservation unit 17 to the hospital server 30 includes the e-mail address of the user of the reservation requesting user terminal 20 so that the reservation result can be notified directly from the hospital server 30 to the user. Is also good.
  • the evaluation unit 15 of the service server 10 collects the biometric data of the user of the user terminal 20.
  • the hospital or doctor limited based on the biometric data of a plurality of users is evaluated by an objective index of time, and the presentation unit 16 presents a reservation candidate to the user based on the evaluation result.
  • the reservation unit 17 makes a reservation for the hospital according to the selection of the hospital or the doctor of the user of the user terminal 20 that is the evaluation request source. Therefore, presenting a candidate of a hospital or a doctor suitable for the user based on the objective index, the user can easily select a hospital, and can easily reserve a hospital according to the selection. .
  • FIG. 2 is a block diagram illustrating 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.
  • 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.
  • the data server 40 includes the control unit 41, the storage unit 42, and a communication interface (not illustrated).
  • the user terminal 20 includes the control unit 21, the measurement unit 22, the storage unit 23, a communication interface (not shown), and a user interface (not shown). Connectable.
  • the service server 100 includes a control unit 110, a storage unit 120, and a communication interface 130.
  • the communication interface is described as “communication I / F”.
  • the control unit 110 includes, for example, a CPU 111, a RAM 112, a ROM 113, and the like, and controls each component of the service server 100 according to information processing.
  • a CPU 111 instead of the CPU 111, another processor such as an MPU may be used.
  • the ROM 113 stores, for example, an operating system executed by the CPU 111 and other programs (for example, a hospital reservation program).
  • the RAM 112 is, for example, a memory used by the CPU 111 as a work memory.
  • the CPU 111 executes a necessary program
  • the program may be stored in the storage unit 120 instead of the ROM 113, for example.
  • the CPU 111 executes a necessary program, for example, the target program stored in the ROM 113 and / or the storage unit 120 is expanded in the RAM 112. Then, the CPU 111 controls each component by interpreting and executing the program developed in the RAM 112, for example.
  • the storage unit 120 stores, for example, a program (for example, a hospital reservation program) executed by the control unit 110, setting data (for example, address information of the data server 40) necessary for executing the program, various databases, and the like. Can be memorized.
  • the storage medium included in the storage unit 120 stores information such as a program in a computer or a machine so that the information such as the program can be read by using an electrical, magnetic, optical, mechanical, or chemical action. Any medium may be used as long as the medium accumulates the data.
  • an EEPROM or the like can be used as the storage medium included in the storage unit 120.
  • the storage unit 120 may also be used by the CPU 111 as a work memory.
  • the databases stored in 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.
  • 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”. I have.
  • 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 under the control of the control unit 110.
  • the communication protocol uses a 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 storage contents of the hospital database 121.
  • the hospital database 121 includes items such as hospital ID, access information, hospital information, hospital reputation, medical department, doctor ID, name, gender, age, number of guests, reservation status, and doctor reputation.
  • the information of the corresponding hospital is stored.
  • the reputation of the doctor is described as “reputation”, and the number of residents 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.
  • the “access information” is address information for accessing the hospital server 30 or a hospital Web page.
  • “Hospital information” is general information on each hospital, such as the name, address, telephone number, business hours, holidays (business days), and parking lot information of the hospital.
  • “Hospital reputation” is subjective hospital evaluation information that has been arbitrarily input at each user terminal 20 and / or obtained from various hospital evaluation Web pages on the Internet.
  • “Clinical department” is information of a medical department that a hospital has, such as a medical department or a dermatology department.
  • doctor ID is a management number uniquely assigned to each doctor belonging to the hospital. This doctor ID can be distinguished from each other by associating it with the hospital ID, 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 unique doctor ID can be converted to 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. “Wait” is the current number of patients waiting for medical treatment for each doctor. “Reservation status” is the number of future reserved patients for each doctor.
  • the number of reserved patients is stored for an arbitrary period, such as dividing the day into morning and afternoon.
  • the “doctor reputation” is subjective doctor evaluation information that is arbitrarily input at each user terminal 20 and / or acquired from various hospital evaluation web pages on the Internet.
  • FIG. 4 is a diagram showing an example of the contents stored in the user database 122.
  • the user database 122 includes, as items, a user ID, a password, a name, user information, an ID for each hospital, a point, a priority condition, a date, a visit flag, and biometric data (for example, blood pressure, pulse, and the like). , Symptom patterns, etc.
  • the password is described as “PW”
  • the visit flag is described as “visit F”
  • the symptom pattern is described as “symptom P”.
  • the “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, and includes a mail address, a telephone 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. With this hospital ID, it is possible to link each user with the electronic medical record of each hospital.
  • the “point” is position information of the user, and can include a current position, a home address, a work address, and a registered position.
  • the current position for example, the current position transmitted from the user terminal 20 is registered as necessary.
  • the home address, the work address, and the registered position are designated positions arbitrarily designated by the user.
  • the “priority condition” is information selected or arbitrarily specified by the user as a priority condition from predetermined options.
  • “Date” is the date when the biometric data was acquired at the user terminal 20.
  • the “visit flag” indicates whether or not the user has visited any hospital, and “1” is set when the user has visited the hospital.
  • the biological data (“blood pressure”, “pulse”, etc.) is the biological data acquired by the user terminal 20.
  • “Symptom pattern” indicates an attribute of biometric data including various measured values or a relationship between the measured values included in the biometric data, that is, a symptom set based on a pattern of the biometric data.
  • “Date”, “visit to hospital”, biometric data (“blood pressure”, “pulse”, etc.) and “symptom pattern” have a predetermined data capacity that can be assigned to each user. Is stored, and when more information is added, the oldest information is deleted.
  • a predetermined number may be used. In any case, the period or the number may be determined so as to store at least the biometric data for a certain period described later.
  • the user database 122 may store a record of a doctor ID with which the user has been treated in the past.
  • FIG. 5 is a diagram showing an example of the storage contents of the correspondence database 123.
  • the correspondence database 123 corresponds to the correspondence database 18 described in the application example.
  • the correspondence database 123 has, as items, a symptom pattern, a hospital ID, and a doctor ID.
  • the symptom pattern is described as “symptom P”.
  • the correspondence database 123 is a database of hospitals and doctors corresponding to symptom patterns.
  • Symptom pattern corresponds to the symptom pattern in the user database 122.
  • Hospital ID is a management number for specifying a hospital.
  • doctor ID is a management number for specifying a doctor. These hospital ID and doctor ID correspond to those in the hospital database 121.
  • FIG. 6 is a diagram showing an example of the storage contents of the collection database 124.
  • the collection database 124 has items such as a hospital ID, a patient ID, an appointment date and time, a reception, a medical treatment start, a doctor ID, a medical treatment end, a transaction end, a first medical examination flag, and a symptom.
  • the first consultation flag is described as “first consultation F”.
  • the “hospital ID” is a management number for specifying a hospital, and the hospital ID enables information of the hospital database 121 and the collection database 124 to be linked.
  • Patient ID is a patient management number uniquely assigned by each hospital.
  • “Reservation date and time” is the date and time when the patient made a reservation.
  • “Reception” is the time when the patient visited the hospital and performed reception. For example, in each hospital, reception is performed by a medical terminal 33, for example, a PC operated by a reception clerk or an automatic reception machine operated by a patient, and the reception time is described in an electronic medical record corresponding to the patient.
  • “Start of medical treatment” is the time when medical treatment of the doctor for the patient has started.
  • doctor ID is information for specifying a doctor who performs medical treatment.
  • the information of the hospital database 121 and the information of the collection database 124 can be linked by this doctor ID.
  • the “end of medical treatment” is the time at which the medical treatment of the doctor for the patient has ended.
  • a medical terminal 33 for example, a PC operated by a doctor or a nurse inputs a medical treatment start time, a doctor ID, and a medical treatment end time, and the information is described in an electronic medical record corresponding to the patient. Is done.
  • “Accounting end” is the time at which the patient has completed accounting.
  • the accounting end time is calculated for the patient. Is described in the electronic medical record corresponding to.
  • the “first consultation flag” indicates whether the medical treatment is the first consultation, and is set to “1” when the medical examination is the first consultation.
  • “Symptoms” is the name of the patient's disease.
  • FIG. 6 shows a case in which, when collecting the contents of the electronic medical record, the information on the number of medical examinations in which the record of the examination is present is not collected.
  • the collection database 124 further includes, for example, a flag indicating whether or not the examination has been performed as an item. In many cases, an examination is also performed at the time of the first consultation, so that a "first consultation flag" may be used as a flag indicating whether or not the examination is performed.
  • FIG. 7 is a diagram showing an example of the storage contents of the evaluation database 125.
  • the evaluation database 125 includes, as items, a user ID, a hospital ID, a hospital score, a medical department, a medical department score, a doctor ID, an overall score, a time score, and a symptom improvement degree score (for example, improvement of hypertension). Degree score, diabetes improvement degree score, urticaria improvement degree score, etc.).
  • FIG. 7 shows only the hypertension improvement degree score among the symptom-based improvement degree scores, and is described as “hypertension”.
  • the “User ID” is a management number for specifying a user, and the user ID enables information in the user database 122 and the evaluation database 125 to be linked.
  • the “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 the hospital ID.
  • the “hospital score” is an evaluation value obtained by quantifying the evaluation result of the hospital. Here, the numerical value is shown with the highest point being 100 points, but this numerical expression is an example. For example, any value may be used, such as indicating the number of stars with five stars as the highest point, or expressing the number as a deviation value. This “hospital score” can be an average value of the evaluation values of all medical departments of the hospital.
  • “Clinical department” is information of a clinical department provided by the hospital, and the information of the hospital database 121 and the information of the evaluation database 125 can be linked by this medical department.
  • “Clinical department score” is an evaluation value for each medical department.
  • the “medical department score” can be an average value of evaluation values of all doctors belonging to the medical department, for example, a comprehensive score described later.
  • doctor ID is information for specifying a doctor who performs medical treatment. With this doctor ID, information of the hospital database 121, the collection database 124, and the evaluation database 125 can be linked.
  • the “overall score” is an evaluation value for each doctor. This “overall score” can be an added value of the time evaluation value of the doctor and the average value or weighted average value of all the improvement degree evaluation values.
  • Time score is a time evaluation value evaluated from the medical treatment time per patient and the waiting time for each doctor.
  • the time evaluation value is evaluated based on, for example, the average value of the medical treatment time per patient and the average value of the waiting time per patient.
  • the average value of the medical hours per patient is set to a higher evaluation value as the average value is longer according to a predetermined time range.
  • the average value of the medical treatment time per patient is 10 minutes or more, it is possible to set a perfect score of 10 points, and reduce the score by 1 point every 1 minute.
  • the average value of the waiting time per patient is set to a higher evaluation value as the average value is shorter, for example, according to a predetermined time range.
  • the “time score” may be a total score of the score obtained by the average value of the medical hours per patient and the score obtained by the average value of the waiting time per patient.
  • Symptom improvement score is an improvement evaluation value evaluated from the improvement of each symptom.
  • the improvement degree evaluation value is, for example, for a patient who has been registered in the user database 122 and is able to obtain a history of biometric data for a certain period of time among patients who received medical treatment by the doctor, Based on how much the symptom is improved based on the symptom, an evaluation value of the degree of improvement of the symptom can be obtained, and the average value of the evaluation values of all users can be obtained.
  • the score is set to 10 points, which is a perfect score, and one point is set every time the decrease is reduced by 1 mmHg. Can be reduced.
  • the “overall score” can be calculated from the “time score” and the total “improvement score by symptom”. In the present embodiment, as described later, a user who requests a hospital reservation is further specified.
  • the calculated “time score” can be corrected by adding a priority condition, user attribute information, and the like to the evaluation item.
  • FIG. 8 is a flowchart illustrating an example of a processing procedure of the service server
  • FIG. 9 is a flowchart illustrating an example of a processing procedure of the user terminal.
  • Step S101 the CPU 111 of the service server 100 determines whether it is time to collect biometric data.
  • biological data is collected at a predetermined timing, for example, once a day. If it is determined that it is time to collect biological data (step S101, YES), the CPU 111 proceeds with the process to step S102. If it is determined that it is not time to collect biometric data (step S101, NO), the CPU 111 proceeds with the process to step S103.
  • step S102 If it is determined in step S101 that it is time to collect biometric data (step S101, YES), the CPU 111 executes a 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 via the communication interface 130.
  • the PHR request transmitted from the user terminal 20 is registered in the corresponding user's biometric data (“blood pressure”, “pulse”, etc.) in the user database 122 in response to the request.
  • the CPU 111 determines the attribute of the biometric data including the measured value or the relationship of the measured value of each item of the biometric data registered in the user database 122, that is, the symptom corresponding to the pattern of the biometric data. Register in the symptom pattern item. Note that any method may be used to determine this symptom. For example, a symptom is selected in advance for a large number of patterns of the biometric data, and the symptom is made into a database, and the pattern of the database and the pattern of the biometric data registered in the user database 122 are subjected to pattern matching, so that the most similar Symptoms can be adopted.
  • a symptom corresponding to the pattern of the biometric data registered in the user database 122 may be determined by machine learning a large amount of patterns of the biometric data.
  • Step S201 That is, the processor (not shown) of the control unit 21 of the user terminal 20 executes the hospital reservation program as one of the application programs to be executed in the background in the same manner as the e-mail program and the like. It is possible to determine whether or not a PHR request has been received. When determining that the PHR request has not been received (step S201, NO), the processor advances the process to step S202. 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), there is a user operation through a user interface (not shown). It is determined whether or not. If it is determined that there is no operation (step S202, NO), the processor returns the process to step S201. If it is determined that an operation has been performed (step S202, YES), the processor advances the process to step S204.
  • Step S203 When determining in step S201 that the PHR request has been received from the service server 100 (step S201, YES), the processor (not shown) of the control unit 21 of the user terminal 20 executes a PHR transmission process.
  • the processor In the PHR transmission processing, the processor notifies the user of the user terminal 20 of the reception of the PHR request by a pop-up or the like. If the user confirming this performs an operation of permitting 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, the user authentication process need not be performed in order to respond to the request from the service server 100.
  • step S102 of the operation of the service server 100 there are user terminals that cannot collect biometric data.
  • the processor After the completion of the PHR transmission process, the processor returns the process to step S201.
  • the CPU 111 of the service server 100 updates the hospital database 121 when it is determined in step S101 that it is not time to collect biometric data (step S101, NO), or after the biometric data collection process in step S102 ends. Execute the process. For example, the CPU 111 needs to make an update by inquiring the hospital server 30 or the data server 40 of the update via the communication interface 130, or confirming a request for updating the hospital information from the hospital server 30 or the data server 40.
  • the hospital database 121 is updated for the hospital. Further, the CPU 111 can add a new hospital to the hospital database 121.
  • This new registration can be performed, for example, by the administrator of the service server 100 operating the administrator terminal (not shown) connected to the service server 100 directly or via the communication network NET.
  • the hospital ID, access information, hospital information, medical department, doctor ID, gender, and age are updated or newly registered among the items of the hospital database 121. I will not update on the situation.
  • the CPU 111 can search for subjective hospital evaluation information and doctor evaluation information from an arbitrary Web page or the like, and register the result in the hospital reputation and doctor reputation items of the hospital database 121.
  • there is no information to be changed and the contents of the hospital database 121 may not be updated at all.
  • Step S104 The CPU 111 of the service server 100 executes a process of updating the user database 122.
  • the CPU 111 updates the user database 122 for a user who needs updating by operating the user terminal 20 or an administrator terminal (not shown) via the communication interface 130. Updating according to an operation from the user terminal 20 requires user authentication, and the updating process in step S104 includes a user authentication process.
  • the CPU 111 can add a new user to the user database 122.
  • the user ID, password, name, user information, hospital-specific ID, point, and priority condition are updated or newly registered in the items of the user database 122. Some information may not be available.
  • an input by an operation from the user terminal 20 may be accepted, or the management number of the user may be inquired to each hospital server 30 by using user information, a point (home address), or the like as a key. May be collected at In the updating process in step S104, there is a case where there is no information to be changed and the content of the user database 122 is not updated at all.
  • Step S105 The CPU 111 of the service server 100 determines whether the PHR has been received from any of the user terminals 20 via the communication network NET by the communication interface 130. When determining that the PHR has not been received (step S105, NO), the CPU 111 proceeds with the process to step S106. If it is determined that a PHR has been received (step S105, YES), CPU 111 proceeds with the process to step S107.
  • Step S106 If the CPU 111 of the service server 100 determines in step S105 that the PHR has not been received from any of the user terminals 20 (step S105, NO), the communication interface 130 causes any one of the users via the communication network NET. It is determined whether an evaluation request has been received from the terminal 20. This determination includes a user authentication process. If it is determined that the evaluation request has not been received (step S106, NO), the CPU 111 returns the process to step S101. If it is determined that the user authentication has been performed and the evaluation request has been received (step S106, YES), CPU 111 proceeds to step S108.
  • Step S204 If the processor (not shown) of the control unit 21 of the user terminal 20 determines that any operation has been performed in step S202 (step S202, YES), whether the operation is an instruction to acquire biometric data by the measurement unit 22 or not Judge.
  • the instruction to acquire the biometric data can include an instruction to measure the biometric data by the measurement unit 22 provided in the user terminal 20. Further, the instruction to acquire biometric data may be an instruction to acquire biometric data measured by the biometric data measurement 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. If it is determined that the performed operation is not a biometric data acquisition instruction (step S204, NO), the processor advances the processing to step S208.
  • Step S205 The processor (not shown) of the control unit 21 of the user terminal 20 executes the biometric data acquisition process when determining in step S204 that there is an instruction to acquire biometric data (step S204, YES).
  • the biometric data is acquired by measuring the biometric data by the measurement unit 22 provided in the user terminal 20.
  • biometric data is measured by the biometric data measurement device 24 that can communicate with the user terminal 20, and the measured biometric data is acquired by communication.
  • Step S206 The processor (not shown) of the control unit 21 of the user terminal 20 additionally records the acquired biometric data in the PHR stored in the storage unit 23.
  • a 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 by a communication interface (not shown).
  • the PHR is transmitted with the user ID attached so that the biometric data of the PHR can be specified.
  • the processor returns the process to step S201.
  • Step S107 If the CPU 111 of the service server 100 determines in step S105 that a PHR has been received from any of the user terminals 20 (step S105, YES), the CPU 111 of the user database 122 in the user database 122 based on the received PHR. Update the date, biometric data ("blood pressure", "pulse”, etc.) and symptom pattern items. In this case, the received PHR is compared with the biometric data registered in the user database 122, and only the difference can be additionally updated. If the biometric data for a predetermined period or a predetermined number of biometric data has already been stored for the corresponding user in the user database 122, the oldest information is deleted and added.
  • the received PHR includes many times of biometric data per day, only the first biometric data may be added, or only the last biometric data may be added. You may do it. For example, for blood pressure, measurement data after waking up is particularly effective information, and therefore it is desirable to use the first one time of biological data. Therefore, which of a plurality of times is adopted may be determined according to the type of biometric data.
  • the CPU 111 advances the processing to step S106.
  • Step S208 If the processor (not shown) of the control unit 21 of the user terminal 20 determines that the operation performed in step S204 is not a biometric data acquisition instruction (step S204, NO), the performed operation is a medical evaluation acquisition instruction. Is determined. If it is determined that there is a medical evaluation acquisition instruction (step S208, YES), the processor advances the process to step S209. If it is determined that the performed operation is not a medical evaluation acquisition instruction (step S208, NO), the processor advances the process to step S210.
  • Step S209 The processor (not shown) of the control unit 21 of the user terminal 20 executes an evaluation process when determining in step S208 that a medical evaluation acquisition instruction has been issued (step S208, YES).
  • FIG. 10 is a flowchart illustrating an example of the evaluation process.
  • a processor (not shown) of the user terminal 20 receives an input of an evaluation condition by a user operation through a user interface (not shown).
  • the evaluation condition can include a priority condition.
  • the evaluation condition can include an evaluation target condition indicating whether the target for which the evaluation result is presented is a hospital or a doctor. Since a hospital may have a plurality of departments, the condition to be evaluated may be a department instead of a hospital.
  • the processor of the user terminal 20 sends the evaluation request to the service server 100 via the communication network NET with the input evaluation condition.
  • the evaluation request may include a user ID and a password for user authentication and position information indicating the current position of the user terminal 20.
  • 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 a reservation candidate 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 processing of step S2093.
  • Step S108 If the CPU 111 of the service server 100 determines that the evaluation request has been received in step S106 (step S106, YES), the CPU 111 performs user authentication using the user ID and the password included in the received evaluation request, and then performs the same evaluation request.
  • the user database 122 is updated with the position information included in the evaluation condition and the priority condition included in the evaluation condition sent together with the evaluation request. That is, the CPU 111 updates the current position and the priority condition of the user database 122 at a point related to the user with the received information. Further, the CPU 111 stores the evaluation target condition included in the received evaluation condition in the RAM 112 or the storage unit 120. When the latest biometric data is also transmitted, the biometric data is compared with the biometric data registered in the user database 122, and additionally registered if necessary.
  • the CPU 111 limits the hospital or doctor to be evaluated. For example, the CPU 111 first reads a symptom from an item of a symptom pattern corresponding to the latest biometric data of the user in the user database 122, searches the correspondence database 123 using the read symptom as a search key, and searches for a hospital or doctor. Restrict. Further, the CPU 111 stores the attribute of the biometric data, that is, the hospital or physician to be evaluated from among the hospitals or physicians limited by the pattern of the biometric data in the priority condition item of the corresponding user in the user database 122. The information is limited by the information defining the position.
  • the CPU 111 calculates the distance from the address stored in the hospital information of the hospital database 121 by the current position stored in the point item of the corresponding user in the user database 122. Restricts 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 work address if “workplace”, or the registered position if “registered position”. .
  • the method of narrowing down the hospitals or doctors to be evaluated may be limited by the position information first, and then limited by the biometric data pattern. Which of the hospital and the physician is to be evaluated depends on the evaluation target condition from the user terminal 20 that is the evaluation request source stored in the RAM 112 or the storage unit 120.
  • the CPU 111 stores the list of hospital IDs of the limited hospitals to be evaluated or the doctor IDs of the doctors to be evaluated and the hospital IDs of the hospitals to which the doctors belong in the RAM 112 or the storage unit 120. Even if the evaluation target is a physician, the hospital side may not be able to make a reservation specifying the physician, so the hospital to which the physician to be evaluated belongs is also evaluated.
  • Step S110 The CPU 111 executes an electronic medical record collection process of collecting the contents of the limited electronic medical record of the hospital.
  • FIG. 11 is a flowchart illustrating an example of the electronic medical record collection process.
  • Step S1101 In the electronic medical record collection process, the CPU 111 first determines one hospital ID by selecting one hospital ID from a list of hospital IDs stored in the RAM 112 or the storage unit 120.
  • 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 CPU 111 refers to the hospital database 121 based on the hospital ID and reads out specific information for specifying the hospital, for example, the hospital ID, access information, hospital name, address, or telephone number.
  • the CPU 111 requests the control unit 41 of the data server 40 via the communication network NET via the communication interface 130 to transmit the contents described in the electronic medical record together with the specific information.
  • the CPU 111 receives the contents of the electronic medical chart transmitted from the data server 40 in response to the request via the communication interface 130.
  • 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, the CPU 111 stores, in the collection database 124, information on each medical treatment described in the electronic medical record for each patient ID, that is, the appointment date and time, the reception, the medical treatment start, the doctor ID, the medical treatment end, the accounting end, the first medical examination flag, and the symptoms.
  • the CPU 111 when the examination is recorded in the received electronic medical record, the CPU 111 does not store the information on the medical care of the medical care in the collection database 124. Further, the CPU 111 totalizes the current number of patients waiting for medical treatment for each doctor ID based on the contents of the electronic medical record, and stores the total number in the “waiting” item corresponding to each doctor ID in the hospital database 121. I do.
  • the CPU 111 acquires the number of reserved patients from the acquisition destination hospital via the communication network NET by the communication interface 130.
  • the CPU 111 reads the access information of the hospital by referring to the hospital database 121 based on the hospital ID, 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.
  • the number of patients waiting for medical treatment at the present time can be determined by tabulating the contents of the electronic medical record.However, there is no electronic medical record for patients who have requested an appointment for the first consultation. I can't figure out. For this reason, it is necessary to inquire of the acquisition hospital about the number of reserved patients.
  • the CPU 111 receives, via the communication interface 130, information on the number of reserved patients transmitted from the hospital server 30 in response to the inquiry.
  • Step S1105 the CPU 111 stores the number of reserved patients in the item of “reservation status” in association with each doctor ID in the hospital database 121 in accordance with the received information on the number of reserved patients at the current time for each doctor.
  • Step S1106 the CPU 111 determines whether or not the collection of the contents of the electronic medical record has been completed for all the hospitals indicated by the hospital ID list stored in the RAM 112 or the storage unit 120. If it is determined that there is a hospital that has not been collected yet (step S1106, NO), the CPU 111 returns the process to step S1101, and performs the process for the next hospital. If it is determined that the collection of the contents of the electronic medical record has been completed from all listed hospitals (step S1106, YES), the CPU 111 advances the processing to step S111.
  • Step S111 The CPU 111 executes an evaluation calculation process of calculating an evaluation value based on the contents of the electronic medical records of each limited hospital stored in the collection database 124.
  • FIG. 12 is a flowchart illustrating an example of the 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.
  • the CPU 111 evaluates the doctor based on the evaluation items including at least the medical treatment time and the waiting time per patient.
  • the CPU 111 refers to the collection database 124 based on the hospital ID and calculates a time score for each doctor at the hospital to be processed.
  • the time score can be calculated, for example, based on the sum of the score based on the average value of the medical hours per patient and the score based on the average value of the waiting time.
  • the medical treatment time is the time from the start of medical treatment to the end of medical treatment stored in the collection database 124
  • the waiting time is the time from the reception to the start of medical treatment stored in the collection database 124, and the time from the end of medical treatment to the end of accounting.
  • the CPU 111 stores the calculated time score for each doctor in the RAM 112 or the storage unit 120.
  • the consultation time is long at the first consultation. Therefore, it is determined whether or not the first consultation is performed based on the “first consultation flag” in the collection database 124, and the time used for calculating the time score is predetermined for the first consultation. It may be used after being multiplied by the given coefficient.
  • the CPU 111 evaluates the doctor by an evaluation item including a relationship between the attribute information of the doctor and the attribute information of the user. For example, 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.
  • the 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 evaluation requesting user. Then, the score value is corrected in accordance with a predetermined rule, such as increasing the score for the same sex or increasing the score as the age decreases.
  • the CPU 111 stores the corrected time score for each doctor in the RAM 112 or the storage unit 120.
  • the CPU 111 evaluates the doctor based on an evaluation item including a relationship between the position information designated as the priority condition from the user terminal 20 and the position of the hospital. For example, the CPU 111 corrects based on the attribute information and corrects the time score for each doctor 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 requesting the evaluation stored in the user database 122, and the position information designated as the priority condition is added to the address of the hospital stored in the hospital database 121. On the other hand, if the distance is within a certain distance, the score value is increased.
  • the CPU 111 stores the corrected time score for each doctor in the RAM 112 or the storage unit 120.
  • the CPU 111 evaluates the doctor based on the evaluation items including the current number of patients waiting for medical treatment and the number of reserved patients. For example, the CPU 111 corrects the time score for each doctor stored in the RAM 112 or the storage unit 120 based on the priority condition and corrects the time score based on the number of patients waiting for medical treatment and the number of reserved patients. The CPU 111 totalizes 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 total number is smaller. The CPU 111 stores the corrected time score for each doctor in the RAM 112 or the storage unit 120.
  • the CPU 111 refers to the user database 122 and the collection database 124 to calculate a symptom improvement degree score for each doctor. For example, based on each user's hospital ID in the user database 122, the user's symptom is acquired from the collection database 124, and a user having the same symptom as the symptom is specified. Further, 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 out the history of the biometric data determined by the symptom of the user for a certain period from the user database 122 and evaluates it. For example, if the symptom is hypertension, the CPU 111 reads and evaluates the blood pressure value for a certain period.
  • FIG. 13 is a diagram showing an example of the history of the read biometric data.
  • the systolic blood pressure decreases by D.
  • the score is determined to be 10 points, which is a perfect score if the reduction amount D during a certain period P of the systolic blood pressure, for example, one month is 20 mmHg or more, and to be reduced by one point each time the reduction amount decreases by 1 mmHg.
  • FIG. 14 is a diagram showing another example of the history of the biometric data. Also in the example of this figure, it is assumed that the reduction amount D of the systolic blood pressure during the certain period P is in the range where the score is the same as that of the example of FIG. However, in this example, a temporarily deteriorated history is included. In such a case, the same score as in the example of FIG. 13 may be used as it is, or a lower score than in the example of FIG. 13 may be calculated. In particular, when the timing at which the temporarily deteriorated state turned to improvement was the timing at which there was a switch to another hospital or doctor, there is a high possibility that the temporarily deteriorated state is due to a misdiagnosis. .
  • the CPU 111 can perform this misdiagnosis based on, for example, the date recorded in the reservation date and time item of the collection database 124 and the date recorded in the date item of the user database 122 and the visit record recorded in the visit flag item. Sex can be determined and the score can be modified accordingly.
  • the CPU 111 stores the symptom improvement degree score for each physician thus calculated in the RAM 112 or the storage unit 120.
  • Step S1117 the CPU 111 calculates an overall score from the symptom-based improvement degree score and the corrected time score for each doctor stored in the RAM 112 or the storage unit 120. Further, the CPU 111 calculates a clinical department score and a hospital score from the total score for each doctor. The CPU 111 stores the total score, medical department score, and hospital score calculated for each doctor in the RAM 112 or the storage unit 120.
  • Step S1118 the CPU 111 registers the scores thus calculated and stored in the RAM 112 or the storage unit 120 in the evaluation database 125 in association with the user ID.
  • the CPU 111 registers the scores thus calculated and stored in the RAM 112 or the storage unit 120 in the evaluation database 125 in association with the user ID.
  • the time score based on the attribute information, the priority condition, and the like, as shown in FIG. 7, even in the same doctor, medical department, and hospital, different score values for each user are obtained in the evaluation database 125. Will be registered.
  • Step S1119 the CPU 111 determines whether the calculation of the evaluation value has been completed for all the hospitals indicated by the hospital ID list stored in the RAM 112 or the storage unit 120. If it is determined that there is a hospital for which the evaluation value has not been calculated yet (step S1119, NO), the CPU 111 returns the process to step S1111 and performs the process for the next hospital. If it is determined that the calculation of the evaluation values has been completed for all the listed hospitals (step S1119, YES), the CPU 111 advances the processing to step S112.
  • the CPU 111 reads out and sorts the evaluation results corresponding to the user ID of the user who made the evaluation request stored in the evaluation database 125 in accordance with 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 a hospital ID and a hospital score is read out and sorted in descending order of the hospital score. Further, for example, if the evaluation target condition is a doctor, a set of a doctor ID and a total score is read out and sorted in descending order of the total score. The CPU 111 stores the sorted result in the RAM 112 or the storage unit 120.
  • the CPU 111 determines a reservation candidate based on the sorted result stored in the RAM 112 or the storage unit 120, and transmits the reservation candidate to the user terminal 20 of the evaluation request source via the communication network NET by the communication interface 130. It is sufficient that the number of reservation candidates is at least one, but it is desirable that a plurality of reservation candidates be determined and transmitted in order to give the user options. Of course, the next candidates may be sequentially determined and transmitted according to a return instruction from the user terminal 20.
  • the reservation candidate is determined according to the evaluation target condition stored in the RAM 112 or the storage unit 120. For example, if the condition to be evaluated is a hospital, at least the hospital information including the name and address of the hospital and the score value of the hospital can be included.
  • the hospital information can be obtained from the hospital database 121. Also, for example, if the condition to be evaluated is a doctor, at least the doctor's name, gender, doctor information including the age and the score value of the doctor, and the hospital information of the hospital to which the doctor belongs and the score value of the hospital, Can be included. The doctor information and the hospital information can be obtained 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 via a user interface (not shown).
  • Step S114 After transmitting the reservation candidate in step S113, the CPU 111 of the service server 100 determines whether or not a reservation request from the user terminal 20 has been received by the communication interface 130 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 an end or reservation input by a user operation through a user interface (not shown).
  • the input of the reservation includes selection of a hospital or doctor who wants to make a reservation, and input of a desired date and time.
  • Step S2096 the processor of the user terminal 20 determines whether or not the received input is an end input. If it is determined that the accepted input is not an end input, that 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 Thereafter, the processor of the user terminal 20 waits to receive a 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 received (step S2098, NO), the processing of step S2098 is repeated.
  • Step S116 If the CPU 111 of the service server 100 determines that the reservation request has been received in step S114 (step S114, YES), the process proceeds to step S116, and the hospital server of the hospital is connected by the communication interface 130 via the communication network NET. A reservation request is transmitted to the user 30 together with the PHR of the user stored in the user database 122. The latest biometric data may be used instead of the PHR including all biometric data. At this time, the CPU 111 refers to the hospital ID in the user database 122, and if it is confirmed that the user is a user having a management number in the hospital, the management number is added to the reservation request. Can be included.
  • Step S117 Thereafter, the CPU 111 waits for reception of the reservation result from the hospital server 30 of the corresponding hospital via the communication network NET by the communication interface 130. That is, the CPU 111 determines whether or not the reservation result has been received, and when it is determined that the reservation result has not been received (step S117, NO), the step S117 is repeated.
  • the hospital server 30 that manages the reservation of the patient performs a reservation process according to the reservation request. Then, the result is returned to the service server 100 via the communication network NET.
  • step S118 If it is determined 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 of the reservation request source via the communication network NET by the communication interface 130. Thereafter, the CPU 111 returns the processing 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 via a user interface (not shown). Thereafter, the processor returns the process to step S2095.
  • step S2095 the user can reset another desired reservation date and time or select another hospital, another doctor, or the like. It is.
  • the user inputs an end to end the medical evaluation process.
  • Step S20910 If the processor (not shown) of the user terminal 20 determines that the input received in step S2096 is the end input (step S2096, YES), the process proceeds to step S20910, and the end request is sent via the communication network NET. Send to the service server 100. Then, the processor returns the process to step S201.
  • Step S115 If the CPU 111 of the service server 100 determines that the reservation request has not been received in step S114 (step S114, NO), the CPU 111 of the service terminal 100 further transmits an end request from the user terminal 20 via the communication network NET via the communication interface 130. Is determined. If it is determined that the termination 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.
  • Step S210 When the processor (not shown) of the control unit 21 of the user terminal 20 determines that the operation performed in step S208 is not a medical evaluation acquisition instruction (step S208, NO), the CPU executes other processing according to the operation. I do.
  • the other processing includes, for example, processing corresponding to a new registration operation or an information update operation of the user for performing the update processing of the user database 122 in the above-described step S104 of the service server 100. Then, after executing the processing, the processor returns the processing to step S201.
  • 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.
  • a history of biometric data of each of a plurality of users is collected for a certain period of time from the user terminal 20 of each user, and based on the collected information, at least for each hospital, and further, for each medical department of each hospital or a doctor of each hospital.
  • a time score based on at least the medical treatment time and the waiting time per patient, and a symptom improvement degree score based on the improvement degree of the symptom of each user are calculated and stored in the evaluation database 125.
  • the CPU 111 transmits the evaluation score to the user terminal 20 and presents the evaluation score to the user, so that the user refers to the hospital, medical department or doctor who is going to receive medical treatment with reference to the presented score. And it can be selected.
  • the evaluation result is obtained by the numerical value of the evaluation value, that is, the score
  • the evaluation results can be ordered by the numerical value, and as a result, the reservation candidate suitable for the user is easily determined. be able to.
  • the correspondence database 123 by using the correspondence database 123, it is possible to easily and quickly limit the hospitals or doctors to be evaluated.
  • the user's biometric data can be easily collected.
  • a candidate more suitable for the user can be provided by adding an evaluation based on the symptom improvement status, ie, the degree of symptom improvement, in addition to the temporal evaluation.
  • the index for selecting a hospital to be reserved by the user is provided. Can be provided, and user selection can be facilitated.
  • the doctor suitable for the user can be highly evaluated, and the user can be more suitable. Physician can be a candidate.
  • hospitals that the user can go to are limited according to the current position of the user requesting the evaluation and the designated position designated by the user, so that an inappropriate hospital is presented to the user as a candidate. Can be reduced.
  • the number of patients waiting for medical treatment at the present time and the future reservation status are referred to, and a hospital or a physician who can perform medical treatment immediately with a short waiting time is higher.
  • a hospital or a physician who can perform medical treatment immediately with a short waiting time is higher.
  • the point When searching for a hospital that can be treated immediately, the point can be specified when inputting the conditions in step S2091 on the user terminal 20, so that the number of patients waiting for medical treatment and the number of reserved patients in step S1115 can be determined.
  • the weight of the correction based on the number may be increased, that is, the score value may be increased.
  • the weight of the correction based on the attribute information in step S1113 or the correction based on the priority condition in step S1114 may be reduced, or the correction may be skipped.
  • the service server 100 may have a charging process that can collect an introduction fee from the reservation destination hospital.
  • the hospital may provide a service such that the letter of introduction is unnecessary or reduced for the user reserved by the processing procedure of the service server 100 as described above.
  • FIG. 15 is a flowchart illustrating an example of a processing procedure of the service server 100 in the second embodiment. The same processes as those in FIG. 8 are denoted by the same reference numerals.
  • Step S119 the CPU 111 of the service server 100 determines whether it is time to collect biometric data and electronic medical records.
  • biometric data and electronic medical records are collected at a predetermined timing, for example, once a day. If it is determined that it is not time to collect the biometric data and the electronic medical record (step S119, NO), the CPU 111 advances the processing to step S103. If it is determined that it is time to collect the biometric data and the electronic medical record (step S119, YES), the CPU 111 advances the processing to step S102.
  • step S102 If it is determined in step S101 that it is time to collect the biometric data and the electronic medical record (step S101, YES), the CPU 111 first executes the same biometric data collection processing as in the first embodiment.
  • Step S120 the CPU 111 executes an electronic medical record collection process.
  • the target hospital is not limited, and thus the CPU 111 collects the contents of the electronic medical records of all hospitals without limitation.
  • FIG. 16 is a flowchart illustrating an example of the 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 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 processing in step S1202 is the same as the processing in step S1102 in the first embodiment. That is, the CPU 111 refers to the hospital database 121 based on the hospital ID and reads out specific information for specifying the hospital, for example, 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 via the communication network NET via the communication interface 130 to transmit the contents described in the electronic medical record together with the specific information. The CPU 111 receives the contents of the electronic medical chart transmitted from the data server 40 in response to the request via the communication interface 130.
  • 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, the CPU 111 stores, in the collection database 124, information on each medical treatment described in the electronic medical record for each patient ID, that is, the appointment date and time, the reception, the medical treatment start, the doctor ID, the medical treatment end, the accounting end, the first medical examination flag, and the symptoms.
  • the CPU 111 stores, in the collection database 124, information on each medical treatment described in the electronic medical record for each patient ID, that is, the appointment date and time, the reception, the medical treatment start, the doctor ID, the medical treatment end, the accounting end, the first medical examination flag, and the symptoms.
  • Step S1204 the CPU 111 determines whether or not the collection of the contents of the electronic medical record has been completed for all the hospitals indicated by the hospital ID registered in the hospital database 121. If it is determined that there is a hospital that has not been collected yet (step S1204, NO), the CPU 111 returns the process to step S1201 and performs the process for the next hospital. If it is determined that the collection of the contents of the electronic medical record has been completed from all registered hospitals (step S1204, YES), the CPU 111 advances the processing to step S103.
  • step S103 determines in step S119 that it is not the time to collect the biometric data and the electronic medical record (step S119, NO), or after the electronic medical record collection processing in step S110 ends.
  • the CPU 111 determines The same processing of [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 an update process of the hospital database 121 and an update process of the user database 122. Then, the CPU 111 determines whether a PHR or an evaluation request has been received from any of the user terminals 20.
  • the CPU 111 returns the process to step S119. If it is determined that the PHR has been received, the CPU 111 updates the date and biometric data (“blood pressure”, “pulse”, etc.) of the corresponding user in the user database 122 based on the received PHR. . When determining that the evaluation request has been received, the CPU 111 performs user authentication using the user ID and the password included in the received evaluation request, and then includes the location information and the evaluation information included in the evaluation request. The user database 122 is updated according to the priority condition.
  • Step S109 After receiving the evaluation request and updating the user database 122, the CPU 111 limits the hospital to be evaluated as in the first embodiment.
  • Step S121 After that, the CPU 111 performs a number collection process of counting the number of patients waiting for medical treatment and the number of reserved patients at the current time in each hospital limited in step S109. That is, in step S120, the contents of the electronic medical record are collected at a predetermined timing, for example, once a day. Therefore, the number of patients waiting for medical treatment and the number of reserved patients are not counted. Therefore, the CPU 111 collects the numbers.
  • FIG. 17 is a flowchart illustrating an example of the number collecting process.
  • Step S1211 In the headcount collection process, the CPU 111 first selects one hospital ID from the list of limited hospital IDs stored in the RAM 112 or the storage unit 120 to determine the acquisition destination hospital.
  • the CPU 111 acquires the number of patients waiting for medical treatment and the number of reserved patients from the acquisition hospital via the communication network NET by the communication interface 130.
  • the CPU 111 reads the access information of the hospital by referring to the hospital database 121 based on the hospital ID, 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. Inquire about the number of patients waiting for medical treatment at the time and the number of reserved patients. Then, the CPU 111 receives, via the communication interface 130, information on the number of patients waiting for medical treatment and the number of reserved patients transmitted from the hospital server 30 in response to the inquiry.
  • Step S1213 Next, according to the received information on the number of patients waiting for medical treatment and the number of reserved patients for each doctor at the current point in time, the CPU 111 associates each of the doctor IDs in the hospital database 121 with the items of “waiting” and “reservation status”. Remember each person.
  • Step S1214 the CPU 111 determines whether or not the collection of the number of persons has been completed for all hospitals indicated by the hospital ID list stored in the RAM 112 or the storage unit 120. If it is determined that there is a hospital that has not been collected yet (step S1214, NO), the CPU 111 returns the process to step S1211 and performs the process for the next hospital. When it is determined that the collection of the number of persons from all the listed hospitals is completed (step S1214, YES), the CPU 111 advances the processing to step S111.
  • the CPU 111 performs the same processing of [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 out of the contents of the electronic medical record of each hospital stored in the collection database 124. After that, the CPU 111 reads out and sorts the evaluation result corresponding to the user ID of the user of the evaluation request source stored in the evaluation database 125 according to the evaluation target condition included in the evaluation condition, and sorts the sorted result and the evaluation target condition. The reservation candidates are determined in accordance with. Then, the CPU 111 transmits the determined reservation candidate to the user terminal 20 of the evaluation request source via the communication network NET by the communication interface 130.
  • FIG. 18 is a flowchart illustrating an example of a processing procedure of the service server 100 according to the third embodiment. The same processes as those in FIG. 15 are denoted by the same reference numerals.
  • Step S119 the CPU 111 of the service server 100 determines whether or not it is time to collect biometric data and electronic medical records, as in the second embodiment. If it is determined that it is time to collect the biometric data and the electronic medical record (step S119, YES), the CPU 111 performs the same processes of [step S102] and [step S120] as in the second embodiment. That is, the CPU 111 executes the same biological data collection processing as in the first embodiment and the same electronic medical record collection processing as in the second embodiment.
  • Step S122 Thereafter, the CPU 111 executes a first evaluation calculation process of calculating an evaluation value based on the contents of the electronic medical record of each hospital stored in the collection database 124.
  • a time score for each doctor is calculated as an evaluation value.
  • FIG. 19 is a flowchart illustrating an example of the first evaluation calculation process.
  • Step S1221 In the first evaluation calculation process, the CPU 111 first determines a hospital to be processed by selecting one hospital ID from hospital IDs registered in the hospital database 121.
  • the CPU 111 refers to the collection database 124 based on the hospital ID and calculates a time score for each doctor at the hospital to be processed.
  • the CPU 111 stores the calculated time score for each doctor in the RAM 112 or the storage unit 120.
  • Step S1222 the CPU 111 registers the calculated and stored time score of each doctor belonging to the hospital 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.
  • Step S1223 the CPU 111 determines whether the calculation of the evaluation value has been completed for all the hospitals indicated by the hospital IDs stored in the hospital database 121. If it is determined that there is a hospital for which an evaluation value has not yet been calculated (step S1223, NO), the CPU 111 returns the process to step S1211 and performs the process for the next hospital. When it is determined that the calculation of the evaluation values has been completed for all hospitals (step S1223, YES), the CPU 111 advances the processing to step S103.
  • Step S109 After receiving the evaluation request and updating the user database 122, the CPU 111 of the service server 100 determines the position in the information stored in the priority condition item of the corresponding user in the user database 122, as in the first embodiment. Limit the hospitals to be evaluated based on the specified information.
  • Step S121 the CPU 111 inquires about the number of patients waiting for medical treatment and the number of reserved patients in each of the hospitals limited in step S109, and registers the result in the hospital database 121. Perform collection processing.
  • Step S123 Thereafter, the CPU 111 executes a second evaluation calculation process of calculating an evaluation value based on the contents of the electronic medical record of each hospital stored in the collection database 124.
  • FIG. 20 is a flowchart illustrating an example of the 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, thereby obtaining the hospital to be processed. To determine.
  • Step S1231 the doctor ID of each doctor belonging to the hospital to be processed is acquired from the hospital database 121, the time score corresponding to the doctor ID is read out from the item of the total score corresponding to the doctor ID in the evaluation database 125, and the RAM 112 is read. Alternatively, it is stored in the storage unit 120.
  • Step S1113] to [Step S1119] Subsequent processes in [Step S1113] to [Step S1119] are the same as those 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 the priority condition, and further corrects based on the number of patients waiting for medical treatment and the number of reserved patients. Further, the CPU 111 refers to the user database 122 and the collection database 124 to calculate a symptom-based improvement degree score for each doctor. Then, the CPU 111 calculates an overall score from the symptom improvement degree score for each doctor and the corrected time score, and further calculates a medical department score and a hospital score from the comprehensive score for each doctor.
  • the obtained scores are registered in the evaluation database 125 in association with the user ID. Thereafter, the CPU 111 determines whether or not the calculation of the evaluation value has been completed for all the hospitals indicated by the hospital ID list stored in the RAM 112 or the storage unit 120. The process returns to step S1111 to perform the process for the next hospital. If it is determined that the calculation of the evaluation values has been completed for all the hospitals listed, the CPU 111 proceeds with the process to step S112.
  • the present invention is not limited to the above-described embodiments as they are, and can be embodied by modifying constituent elements in an implementation stage without departing from the scope of the invention.
  • Various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiment. Further, components of different embodiments may be appropriately combined.
  • processing procedure described with reference to the flowchart is merely an example, and each processing may be changed as much as possible. Further, in the processing procedure described above, steps can be omitted, replaced, and added as appropriate according to the embodiment.
  • An electronic medical record network (1) for sharing the electronic medical record among the plurality of hospitals;
  • An electronic medical record collection unit (11) for collecting the contents of the electronic medical record from the electronic medical record network;
  • a biometric data collection unit (12) for collecting biometric data of each of a plurality of users via a communication network (NET);
  • a receiving unit (13) for receiving a request from the user terminal (20) via the communication network;
  • a hospital control unit (31) provided at each of the plurality of hospitals for managing reservations of patients;
  • the reception unit receives the reservation request.
  • a hospital reservation system comprising:
  • Appendix 2 A hospital reservation method executed by a server device having a processor (111) and memories (112, 120), By the processor, in each of the plurality of hospitals, at least, patient information on the patient and, for each medical treatment, medical treatment information including reception date and time, medical treatment start date and time, medical treatment end date and time, medical doctor, and accounting end date and time are described.

Landscapes

  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Biomedical Technology (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

L'invention concerne un système de réservation pour hôpital comprenant : une unité de présentation qui a pour objectif de présenter des candidats à la réservation sur un terminal utilisateur source de demande, les candidats à la réservation étant déterminés par évaluation d'un hôpital ou d'un médecin au moyen de critères d'évaluation comprenant au moins un temps de consultation et un temps d'attente par patient, sur la base d'un contenu décrit dans des dossiers médicaux électroniques collectés à partir d'un réseau de dossiers médicaux électroniques, lesdits dossiers médicaux électroniques ayant été soumis à une restriction sur la base de données biométriques de l'utilisateur demandant l'évaluation, et des données biométriques d'une pluralité d'utilisateurs, collectées à l'avance; et une unité de réservation qui, en fonction d'une demande de réservation provenant du terminal utilisateur, envoie une demande de réservation à une unité de commande d'hôpital qui est présente dans l'hôpital correspondant et qui gère des réservations de patient.
PCT/JP2019/026079 2018-07-24 2019-07-01 Système de réservation pour hôpital et dispositif serveur WO2020021973A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2018-138465 2018-07-24
JP2018138465A JP7131164B2 (ja) 2018-07-24 2018-07-24 病院予約システム及びサーバ装置

Publications (1)

Publication Number Publication Date
WO2020021973A1 true WO2020021973A1 (fr) 2020-01-30

Family

ID=69181640

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2019/026079 WO2020021973A1 (fr) 2018-07-24 2019-07-01 Système de réservation pour hôpital et dispositif serveur

Country Status (2)

Country Link
JP (1) JP7131164B2 (fr)
WO (1) WO2020021973A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113241162A (zh) * 2021-05-11 2021-08-10 海南益丰互联网医院有限公司 一种互联网医院管理平台
WO2021199146A1 (fr) * 2020-03-30 2021-10-07 株式会社Ｐｅｃｏ Système, programme et procédé de réception de réservation
CN115641946A (zh) * 2022-09-29 2023-01-24 江苏省计算机技术服务有限公司 基于大数据的智慧医疗管理系统及方法
WO2023155437A1 (fr) * 2022-02-15 2023-08-24 康键信息技术（深圳）有限公司 Procédé de traitement de données basé sur une consultation en ligne, appareil, et dispositif informatique
CN116646065A (zh) * 2023-05-25 2023-08-25 浙江蕙康科技有限公司 互联网医院数据安全管理方法和装置

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7287613B2 (ja) * 2020-05-21 2023-06-06 株式会社eBase Solutions Laboratory 支援サーバ、患者向けコンピュータプログラム及びサービス支援方法
JP7005086B1 (ja) * 2020-06-12 2022-02-14 株式会社Peco 動物患者用待ち時間提供システム、動物患者用待ち時間提供方法、プログラム
KR102234025B1 (ko) * 2020-07-10 2021-03-31 진수진 전세계 통합 헬스케어 서비스 제공 시스템
JP7117688B1 (ja) * 2021-02-02 2022-08-15 株式会社iCARE 健康診断予約管理システム、健康診断管理方法及びプログラム
KR102382541B1 (ko) * 2021-07-15 2022-04-08 주식회사 에이더블유시스템즈 고객 정보를 처리하는 방법 및 디바이스
KR20230172367A (ko) 2022-06-14 2023-12-22 연세대학교 산학협력단 건강 기록에 기반한 생체 정보의 가용성 및 우선 순위 판단 장치 및 그 방법

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003303238A (ja) * 2002-04-09 2003-10-24 Oki Electric Ind Co Ltd 病院選択支援サービス提供システム
JP2004355275A (ja) * 2003-05-28 2004-12-16 Nippon Telegr & Teleph Corp <Ntt> 救急医療用車載装置、医療機関装置および救急医療機関検索システム
JP2005196510A (ja) * 2004-01-08 2005-07-21 Hitachi Ltd 医療機関検索システム
JP2018112941A (ja) * 2017-01-12 2018-07-19 株式会社ＩｎｔｅｒＭｅｄ 医療検索プログラム及びそのシステム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003303238A (ja) * 2002-04-09 2003-10-24 Oki Electric Ind Co Ltd 病院選択支援サービス提供システム
JP2004355275A (ja) * 2003-05-28 2004-12-16 Nippon Telegr & Teleph Corp <Ntt> 救急医療用車載装置、医療機関装置および救急医療機関検索システム
JP2005196510A (ja) * 2004-01-08 2005-07-21 Hitachi Ltd 医療機関検索システム
JP2018112941A (ja) * 2017-01-12 2018-07-19 株式会社ＩｎｔｅｒＭｅｄ 医療検索プログラム及びそのシステム

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021199146A1 (fr) * 2020-03-30 2021-10-07 株式会社Ｐｅｃｏ Système, programme et procédé de réception de réservation
JPWO2021199146A1 (fr) * 2020-03-30 2021-10-07
JP7093594B2 (ja) 2020-03-30 2022-06-30 株式会社Peco 予約受付システム、プログラムおよび方法
CN113241162A (zh) * 2021-05-11 2021-08-10 海南益丰互联网医院有限公司 一种互联网医院管理平台
CN113241162B (zh) * 2021-05-11 2022-03-08 海南益丰互联网医院有限公司 一种互联网医院管理平台
WO2023155437A1 (fr) * 2022-02-15 2023-08-24 康键信息技术（深圳）有限公司 Procédé de traitement de données basé sur une consultation en ligne, appareil, et dispositif informatique
CN115641946A (zh) * 2022-09-29 2023-01-24 江苏省计算机技术服务有限公司 基于大数据的智慧医疗管理系统及方法
CN115641946B (zh) * 2022-09-29 2023-10-31 江苏省计算机技术服务有限公司 基于大数据的智慧医疗管理系统及方法
CN116646065A (zh) * 2023-05-25 2023-08-25 浙江蕙康科技有限公司 互联网医院数据安全管理方法和装置
CN116646065B (zh) * 2023-05-25 2024-03-19 浙江蕙康科技有限公司 互联网医院数据安全管理方法和装置

Also Published As

Publication number Publication date
JP2020016994A (ja) 2020-01-30
JP7131164B2 (ja) 2022-09-06

Similar Documents

Publication Publication Date Title
WO2020021973A1 (fr) Système de réservation pour hôpital et dispositif serveur
JP5669250B2 (ja) 情報アクセス制御システムとそのサーバ装置及び情報アクセス制御方法
JPH09135816A (ja) 広域医療情報システム
JP2017079065A (ja) 医療機関マッチングシステム
JP2001297153A (ja) 個人医療情報の共有化方法及び個人医療情報のデータベース端末
JP6132639B2 (ja) 健康情報利用システム及びそれに用いるプログラム
KR20170043273A (ko) 통신망을 이용한 원격 헬스케어 시스템 및 방법
JP2020016995A (ja) 医療評価システム及びサーバ装置
CN111445984A (zh) 一种管理医生平台的方法及装置
JP6592321B2 (ja) 診診連携方法および診診連携用コンピュータプログラム
JP2008146170A (ja) 医療施設検索装置及び方法
JP2020016993A (ja) 医療評価システム及びサーバ装置
JP6100668B2 (ja) 医療管理装置、医療管理装置の制御方法、及びプログラム
JP2001265877A (ja) 検査予約サービス方法、検査・診断画像データサービス方法、検査データ解析処理サービス方法、画像・検査データサービス方法
JP7382741B2 (ja) 医療機関選定支援装置
JP2001299767A (ja) アレルギー疾患情報処理システム、アレルギー疾患情報処理方法およびその方法をコンピュータに実行させるプログラムを記録したコンピュータ読み取り可能な記録媒体
JP2018112941A (ja) 医療検索プログラム及びそのシステム
KR101919236B1 (ko) 스마트 요양간호를 지원하는 시스템 및 방법
JP2020052457A (ja) 利用者情報管理システム、利用者情報管理装置、権限管理装置、利用者端末装置、コンピュータプログラム、利用者情報管理方法及びシステムの構築方法
JPH11306261A (ja) 患者情報共有システム
KR20010088639A (ko) 네트워크를 이용한 원격 진료 시스템 및 그 방법
JP2003116796A (ja) 在宅医療適応患者の診察・指導支援システム及び診察・指導支援方法
JP2001282922A (ja) 患者医療情報の交換方法及び端末
KR20050049448A (ko) 인터넷 망을 기반으로 한 주거공간위주의 원격진료 시스템및 원격진료 방법
KR20200144678A (ko) 의료인 왕진예약 서비스 제공방법 및 이를 실행하는 서버

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19840168

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19840168

Country of ref document: EP

Kind code of ref document: A1