Health checkup result management system

Abstract

This system enables strict management of health checkup results, and, in turn, improves the convenience of handling health checkup results while maintaining strict management. [Solution] The health check result management system of the present invention comprises a core DB server 10, an internal device 20 connected to it by LAN 1, and an external write storage device 30 connected to it by an external bus 21. When an ID and password are entered from the internal device 20 to the core DB server 10, access between the internal device 20 and the core DB server 10 is permitted. When an ID and password are entered from the internal device 20 to the external write storage device 30, access between the internal device 20 and the external write storage device 30 is permitted, and new health check result information and management information are sent from the external write storage device 30 to the core DB server 10 via the internal device 20 and stored in the core DB server 10.

Description

Technical Field

[0001] The present invention relates to a medical examination result management system capable of managing the medical examination results of examinees obtained in medical examinations.

Background Art

[0002] With the progress of digitization, medical information such as medical examination results and medical records has come to be stored and managed as electronic information in medical institutions, medical examination institutions, etc.

[0003] For example, in a medical examination such as a dental examination, a doctor such as a dentist diagnoses an examinee on site, and the medical examination results obtained by the diagnosis are transferred from a local PC (Personal Computer) to a server, and the transferred medical examination results are stored and managed in the server. Also, the past medical examination results of the examinee are extracted from the medical examination result data stored and managed in the server, the extracted medical examination results are transferred from the server to the local PC, and the transferred medical examination results may be used for on-site diagnosis.

[0004] It is extremely important to strictly manage such medical examination results to prevent information leakage, information tampering, etc. On the other hand, it is also desired to improve the handling convenience such as making it easier for examinees, doctors, etc. of medical examinations to view the medical examination results. Therefore, various medical examination result management technologies have been proposed to meet such requirements.

[0005] For example, as a first example of medical examination result management technology, it has a database for storing medical information such as medical examination results of examinees and a computer terminal that can be accessed via a network to the database, and the computer terminal can transmit medical information such as examination data and image data to the database and can view the medical information in the database.

[0006] In this medical information management technology, when a computer terminal accesses a database, the operator of the computer terminal obtains authentication by entering login information, and only if the operator has a pre-set level of authority can they update and input medical information on the server. (See, for example, Patent Document 1)

[0007] For example, a second example of health checkup result management technology involves storing medical information, including patient examination results such as fetal images obtained at a medical institution, on a dedicated USB (Universal Serial Bus) provided by the medical institution. This dedicated USB is then connected to a smartphone, and once the dedicated USB is authenticated as a legitimate USB from the medical institution, the medical information on the dedicated USB is transmitted from the smartphone to a server of a service provider or distribution contractor via a network such as a telephone network, mobile communication network, CATV (Cable Television) communication network, or satellite communication network. (See, for example, Patent Document 2.)

[0008] For example, a third example of health checkup result management technology is a medical information sharing system that includes a server capable of sharing patient medical information among multiple affiliated hospitals and multiple non-affiliated hospitals, a dedicated VPN (Virtual Private Network) line for affiliated hospitals to connect to the server, and a software VPN line for non-affiliated hospitals to connect to the server via the network.

[0009] More specifically, the medical information sharing system includes a server with a comprehensive medical record that can be entered and viewed by affiliated and non-affiliated hospitals, a common patient ID assignment means for assigning a common patient ID (Identifier) ​​to patients whose medical information is shared, a patient ID linking means for linking a patient's patient IDs from multiple affiliated hospitals and multiple patient IDs from multiple non-affiliated hospitals to the common patient ID, an affiliated hospital identification means for identifying whether a hospital is affiliated or non-affiliated based on the type of VPN line or login ID used to connect to the server, and an authorization granting means for granting predetermined viewing and input privileges to the comprehensive medical record to affiliated and non-affiliated hospitals identified by the affiliated hospital identification means.

[0010] In this medical information sharing system, a common patient ID assignment means assigns a common patient ID to a patient, and a patient ID linking means links the patient IDs of multiple affiliated hospitals and multiple non-affiliated hospitals assigned to that patient to the common patient ID. Affiliated and non-affiliated hospitals can share only the medical information of patients assigned a common patient ID. Affiliated hospitals are granted the authority to view all medical information entered into the comprehensive medical record, and a non-affiliated hospital is granted the authority to view the medical information entered into the comprehensive medical record by an affiliated hospital for a particular patient, as well as the medical information of that particular patient entered as text into the comprehensive medical record by that non-affiliated hospital. However, medical information of a particular patient entered as text into the comprehensive medical record by other non-affiliated hospitals cannot be viewed by a non-affiliated hospital. (See, for example, Patent Document 3) [Prior art documents] [Patent Documents]

[0011] [Patent Document 1] Japanese Patent Publication No. 2010-113504 [Patent Document 2] Japanese Patent Publication No. 2021-140659 [Patent Document 3] Japanese Patent Publication No. 2018-132903 [Overview of the project] [Problems that the invention aims to solve]

[0012] However, in the first example of the health checkup result management technology described above, if one login code for accessing the database is obtained from a computer terminal, medical information can be acquired via a general network. Therefore, the protection of medical information on a general network is insufficient, and measures against leakage and tampering of medical information are not adequate.

[0013] In the second example of the health checkup result management technology described above, once the dedicated USB is authenticated as a legitimate USB belonging to a medical institution, the medical information contained within the dedicated USB is transmitted to the server via a general network. Therefore, the protection of medical information on a general network is insufficient, and measures against leakage and tampering of medical information are not adequate.

[0014] In the third example of health checkup result management technology, access to the server from affiliated hospitals is only protected by a dedicated VPN line, and access to the server from non-affiliated hospitals is only protected by a software VPN line. Therefore, if someone obtains a single login ID and secures an environment where they can access the server within an affiliated or non-affiliated hospital, anyone can access the server, meaning that measures against leakage and tampering of medical information are insufficient.

[0015] Furthermore, in the third example of health checkup result management technology, only the hospital is able to view the medical information; patients are not able to view it. Therefore, the convenience of handling medical information is not good.

[0016] Considering these circumstances, it is desirable that the health checkup result management system be able to strictly manage health checkup results. Furthermore, it is desirable that the health checkup result management system be able to improve the convenience of handling health checkup results while also being able to strictly manage them. [Means for solving the problem]

[0017] To solve the above problems, a health check result management system according to one embodiment is a health check result management system configured to manage the health check results of a patient obtained in a health check, comprising: a core DB server configured to store the patient's health check results and management information including the patient's name, affiliated group and management number; an internal device configured to be connectable to the core DB server by LAN; and an external write storage device configured to store new information and management information of the patient's health check results and configured to be connectable to the internal device by its external bus, wherein the core DB server has its database ID and corresponding to the database ID The system is configured to allow access to the internal device when a database password is entered from the internal device, and the external write storage device is configured to allow access to the internal device when its write ID and the write password corresponding to the write ID are entered from the internal device, and with the internal device permitted to access the core DB server and the external write storage device, new information and management information of the patient's health check results are sent from the external write storage device to the core DB server via the internal device and can be stored in the core DB server.

[0018] A health check result management system according to one embodiment comprises a file server configured to store the health check results and management information of the examinee and connected to the internal device by the LAN, and an external browsing storage device configured to store past information and management information of the examinee's health check results and connected to the internal device by its external bus, wherein the file server is configured to allow the internal device to access the file server when its file ID and file password corresponding to the file ID are input to the file server from the internal device, the external browsing storage device is configured to allow the internal device to access the external browsing storage device when its browsing ID and browsing password corresponding to the browsing ID are input to the external browsing storage device from the internal device, and the internal device is configured to acquire health check target group information relating to a predetermined group undergoing a health check, and corresponding to the health check target group information The system is configured to allow selection of past health check results of a patient associated with management information including the group to which the patient belongs, from multiple or all past health check results stored in the core DB server, and the internal device is permitted to access the core DB server and the file server. The internal device selects past health check results of a patient associated with management information including the group to which the patient belongs, corresponding to the health check target group information, from multiple or all past health check results, and sends them from the core DB server to the file server via the internal device, where they are configured to be stored and managed for viewing. The system is configured to allow selection of past health check results of a patient associated with management information including the group to which the patient belongs, corresponding to the health check target group information, from the file server to the external viewing storage device via the internal device, where they are configured to be stored in the external viewing storage device.

[0019] A health check result management system according to one embodiment includes an external device configured to be connectable to the file server via VPN and to the external write and read storage device via an external bus of the external device, wherein the file server is configured to allow access to the external device when the file ID and password are input from the external device, the external write storage device is configured to allow access to the external device when the write ID and password are input from the external device, and with the external device permitted to access the file server and the external write storage device, new information and management information of the patient's health check results are sent from the external write storage device to the file server via the external device and can be stored in the file server, and with the internal device permitted to access the core DB server and the file server, new information and management information of the patient's health check results are sent from the file server to the core DB server via the internal device and can be stored in the core DB server.

[0020] A health check result management system according to one embodiment comprises a health check device configured to be connectable by an external bus between the external write and read storage device and the health check device, the health check device being configured to display past information and management information of the examinee's health check results and to input new information of the examinee's health check results, the external write storage device being configured to allow access to the health check device when the write ID and password are input from the health check device, and the external read storage device being configured when the read ID and password are input from the health check device In such a case, the system is configured to allow access to the health check device, and when the health check device is able to access both the external write and read / store the patient, past information and management information of the patient's health check results stored in the external read / store the patient are sent from the external read / store the patient to the health check device so that they can be displayed on the health check device, and new information of the patient's health check results entered in the health check device is sent from the health check device to the external write / store the patient together with the management information so that it can be stored on the external write / store the patient.

[0021] A health check result management system according to one embodiment comprises a reader device configured to read codes and a reservation management system configured to accept health check reservations from the patient, wherein the reservation management system has a web server configured to communicate with the patient's terminal device and is configured to transmit the code containing the patient's reservation information from the web server to the patient's terminal device, the reader device is connected to the health check device so that it can send the code displayed on the terminal device to the health check device, the health check device is configured to acquire the patient's reservation information contained in the code sent from the reader device, and past information of the patient's health check results associated with the management information corresponding to the reservation information is stored in the external viewing storage device. The device is configured to determine whether or not a condition exists, and if the health check device determines that past information of the patient's health check results associated with the management information corresponding to the reservation information is stored in the external browsing storage device, the health check device is configured to access both the external writing and browsing storage devices, and the past information of the patient's health check results and the management information stored in the external browsing storage device are sent from the external browsing storage device to the health check device and displayed on the health check device. Furthermore, new information of the patient's health check results entered in the health check device is associated with the management information modified by the health check device based on the patient's reservation information and sent together with the management information from the health check device to the external writing storage device for storage in the external writing storage device.

[0022] In one embodiment of the health check result management system, if the health check device determines that past information of the patient's health check results corresponding to the reservation information is not stored in the external viewing storage device, the health check device, with access to both the external writing and viewing storage devices, assigns a new management number to the patient, and the new information of the patient's health check results entered in the health check device is associated with management information created in the health check device based on the patient's reservation information and including the newly assigned management number, and is sent from the health check device to the external writing storage device together with the management information, so that it can be stored in the external writing storage device.

[0023] The health check result management system according to one aspect includes an AP server connected to the backbone DB server via the LAN. The reservation management system has a distribution DB server configured to be connectable to the AP server via the Internet and also connectable to the web server, and is configured to be able to receive a request for distributing the health check result when accepting a reservation from the examinee. The reservation information and the management information modified or created based on the reservation information include distribution permission information that allows the distribution of the distribution information of the examinee's health check result including at least the new information of the examinee's health check result to the examinee when the reservation management system receives the request for distributing the examinee's health check result. Access from the AP server to the distribution DB server is allowed, while access from the distribution DB server to the AP server is restricted. The AP server is configured to manage the transmission of the distribution information of the examinee's health check result from the backbone DB server to the distribution DB server via the AP server when the reservation information includes the distribution permission information. The distribution DB server is configured to be able to acquire and store the distribution information of the examinee's health check result transmitted from the backbone DB server via the AP server. The reservation management system is configured to be able to distribute the distribution information of the examinee's health check result associated with the management information corresponding to the examinee's reservation information from the distribution DB server to the examinee's terminal device via the web server.

Advantages of the Invention

[0024] In the health check result management system according to one aspect, the health check results can be strictly managed. Consequently, in the health check result management system according to one aspect, while the health check results can be strictly managed, the convenience of handling the health check results can be improved.

Brief Description of the Drawings

[0025] [Figure 1] FIG. 1 is a schematic diagram showing a health check result management system according to an embodiment. [Figure 2]Figure 2 is a block diagram showing a core DB server, internal device, file server, external device, and AP server according to one embodiment. [Figure 3] Figure 3 is a block diagram showing an internal device and an external write and read storage device according to one embodiment. [Figure 4] Figure 4 is a block diagram showing an external device and an external write and read / store device according to one embodiment. [Figure 5] Figure 5 is a block diagram showing a health checkup device, an external writing, reading and storage device, and a reading device according to one embodiment. [Figure 6] Figure 6 is a front view showing a terminal device according to one embodiment, with an example of a code image displayed. [Figure 7] Figure 7 is a block diagram showing a core DB server, AP server, reservation management system, and terminal device according to one embodiment. [Figure 8] Figure 8 is a front view showing a terminal device according to one embodiment, with an example of a health checkup result image displayed. [Figure 9] Figure 9 is a flowchart illustrating an example of the process of acquiring past health checkup results and management information within an organization in a health checkup result management method according to one embodiment. [Figure 10] Figure 10 is a flowchart illustrating an example of the process of acquiring new health checkup results and management information at the health checkup site in a health checkup result management method according to one embodiment. [Figure 11] Figure 11 is a flowchart illustrating an example of the process of storing new health check result information and management information within an organization in a health check result management method according to one embodiment. [Figure 12] Figure 12 is a flowchart illustrating an example of the process of storing new health check result information and management information from outside the organization in a health check result management method according to one embodiment. [Figure 13] Figure 13 is a flowchart showing an example of the process of booking a health checkup in a health checkup result management method according to one embodiment. [Figure 14] Figure 14 is a flowchart showing an example of the process of distributing health checkup result information in a health checkup result management method according to one embodiment. [Modes for carrying out the invention]

[0026] A health checkup result management system according to one embodiment will be described below. In the following, the "health checkup result management system" will be simply referred to as the "system" as needed.

[0027] In this embodiment, the health check results are those of a dental checkup. However, the health check results in this embodiment are not limited to those of a dental checkup. For example, the health check results can be those of a general periodic health checkup, a comprehensive medical examination, an internal medicine checkup, a surgical checkup, an ophthalmology checkup, an otolaryngology checkup, a dermatology checkup, a gynecological checkup, an obstetrician-gynecologist checkup, an infant health checkup, etc.

[0028] "Outline of the Health Checkup Result Management System" Referring to Figures 1-8, the health check result management system according to this embodiment is generally configured as follows. The health check result management system according to this embodiment is configured to manage the health check results of patients obtained during dental checkups.

[0029] Referring to Figures 1-3, the system includes a core DB server (core database server) 10 configured to store the health check results of the patient, as well as management information including the patient's name, affiliated group, and management number. The system also includes internal devices 20 configured to be connectable to the core DB server 10 via a first LAN (Local Area Network) 1.

[0030] The system includes an external write storage device (hereinafter referred to as the "write device") 30 configured to store new health check results and management information of patients. The write device 30 is configured to be connectable to the internal device 20 via the external bus 21 of the internal device 20.

[0031] The core DB server 10 is configured to register its database ID (Identifier) ​​and the database password corresponding to that database ID. The core DB 10 is also configured to determine whether or not the database ID and password were entered from an external device connected to it.

[0032] The core DB10 is configured to allow access to the internal device 20 if it determines that the database ID and password were entered from the internal device 20. The core DB10 is configured to restrict access to the internal device 20 if it determines that at least one of the database ID and password were not entered from the internal device 20.

[0033] The writing device 30 is configured to register its write ID and the write password corresponding to the write ID. The writing device 30 is configured to determine whether or not the write ID and password were entered from an external device connected to it.

[0034] The writing device 30 is configured to allow access to the internal device 20 if it determines that the write ID and password have been entered from the internal device 20. The writing device 30 is configured to restrict access to the internal device 20 if it determines that at least one of the write ID and password has not been entered from the internal device 20.

[0035] With the internal device 20 permitted to access the core DB server 10 and the writing device 30, new information and management information of the patient's health check results can be sent from the writing device 30 to the core DB server 10 via the internal device 20 and stored in the core DB server 10.

[0036] Referring to Figures 1-3, the system includes a file server 40 configured to store the patient's health check results and management information. The file server 40 is configured to be connectable to the internal device 20 via a first LAN 1.

[0037] The system includes an external browsing and storage device (hereinafter referred to as the "browsing device") 50 configured to store past and management information of the patient's health check results. The browsing device 50 is configured to be connectable to the internal device 20 via its external bus 21.

[0038] The file server 40 is configured to register file IDs and file passwords corresponding to those file IDs. The file server 40 is also configured to determine whether or not the file ID and password were entered from an external device connected to it.

[0039] The file server 40 is configured to allow access to the internal device 20 if it determines that the file ID and password were entered from the internal device 20. The file server 40 is configured to restrict access to the internal device 20 if it determines that at least one of the file ID and password was not entered from the internal device 20.

[0040] The browsing device 50 is configured to register its browsing ID and the browsing password corresponding to that browsing ID. The browsing device 50 is also configured to determine whether or not the browsing ID and password were entered from an external device connected to it.

[0041] The browsing device 50 is configured to allow access to the internal device 20 if it determines that the browsing ID and password were entered from the internal device 20. The browsing device 50 is configured to restrict access to the internal device 20 if it determines that at least one of the browsing ID and password was not entered from the internal device 20.

[0042] The internal device 20 is configured to acquire health check target group information for a predetermined group of people undergoing health checkups. The internal device 20 is configured to select past health checkup results of examinees associated with management information including the group to which they belong corresponding to the health check target group information, from multiple or all past health checkup results stored in the core DB server 10.

[0043] With the internal device 20 permitted to access the core DB server 10 and the file server 40, past health check results of examinees associated with management information, including the group to which they belong corresponding to the health check target group information, are selected by the internal device 20 from multiple or all past health check results and sent from the core DB server 10 to the file server 40 via the internal device 20, where they can be stored and managed for viewing. Furthermore, with the internal device 20 permitted to access the file server 40 and the viewing device 50, past health check results of examinees associated with management information, including the group to which they belong corresponding to the health check target group information, are sent from the file server 40 to the viewing device 50 via the internal device 20, where they can be stored on the viewing device 50.

[0044] Referring to Figures 1, 2, and 4, the system has an external device 60 that is configured to be connectable to the file server 40 via a VPN (Virtual Private Network) 2. The external device 60 is configured to be connectable to write and read devices 30 and 50 via its external bus 61.

[0045] The file server 40 is configured to allow access to the external device 60 if it determines that the file ID and password were entered from the external device 60. The file server 40 is configured to restrict access to the external device 60 if it determines that at least one of the file ID and password was not entered from the external device 60.

[0046] The writing device 30 is configured to allow access to the external device 60 if it determines that the write ID and password were entered from the external device 60. The writing device 30 is configured to restrict access to the external device 60 if it determines that at least one of the write ID and password was not entered from the external device 60.

[0047] With the external device 60 permitted to access the file server 40 and the writing device 30, new and management information of the patient's health check results can be sent from the writing device 30 to the file server 40 via the external device 60 and stored in the file server 40. Furthermore, with the internal device 20 permitted to access the core DB server 10 and the file server 40, new and management information of the patient's health check results can be sent from the file server 40 to the core DB server 10 via the internal device 20 and stored in the core DB server 10.

[0048] Referring to Figures 1, 2, and 5, the system includes a health check device 70 that is connected to the write and view devices 30 and 50 via an external bus 71 of the health check device 70. The health check device 70 is configured to display past and management information of the patient's health check results. The health check device 70 is configured to allow input of new information of the patient's health check results.

[0049] The writing device 30 is configured to allow access to the health checkup device 70 if it determines that the writing ID and password have been entered from the health checkup device 70. The writing device 30 is configured to restrict access to the health checkup device 70 if it determines that at least one of the writing ID and password has not been entered from the health checkup device 70.

[0050] The viewing device 50 is configured to allow access to the health checkup device 70 if it determines that the viewing ID and password have been entered from the health checkup device 70. The viewing device 50 is configured to restrict access to the health checkup device 70 if it determines that at least one of the viewing ID and password has not been entered from the health checkup device 70.

[0051] With the health check device 70 in a state where it can access both the write and view devices 30 and 50, past information and management information of the patient's health check results stored in the view device 50 are sent from the view device 50 to the health check device 70 and become available for display on the health check device 70.

[0052] In addition, new information about the patient's health check results entered in the health check device 70 is sent from the health check device 70 to the writing device 30 along with management information, and becomes available for storage in the writing device 30. In this case, the storage of new information about the patient's health check results and management information in the viewing device 50 and the health check device 70 is restricted.

[0053] Referring to Figures 1, 2, 5, and 6, the system has a reading device 80 configured to read code C. The core DB server 10 and the write and read devices 30 and 50 are configured to store the patient's health check results in association with the patient's management information.

[0054] The system includes a reservation management system 100 configured to accept health checkup reservations from patients. The reservation management system 100 includes a web server 110 configured to communicate with the patient's terminal device 200. The reservation management system 100 is configured to send a code C containing the patient's reservation information from the web server 110 to the patient's terminal device 200.

[0055] The reading device 80 is connected to the health check device 70 so that it can send the code C displayed on the terminal device 200 to the health check device 70. The health check device 70 is configured to be able to acquire the patient's reservation information contained in the code C sent from the reading device 80. The health check device 70 is configured to be able to determine whether or not past information of the patient's health check results associated with management information corresponding to the reservation information is stored in the viewing device 50.

[0056] If the health check device 70 determines that past health check results of a patient, associated with management information corresponding to the reservation information, are stored in the viewing device 50, the health check device 70 will have access to both the writing and viewing devices 30 and 50. The past health check results and management information of the patient stored in the viewing device 50 will then be sent from the viewing device 50 to the health check device 70, and the information will be made available for display on the health check device 70, associated with the patient's reservation information.

[0057] In addition, new information about the patient's health check results entered in the health check device 70 is associated with management information modified in the health check device 70 based on the patient's reservation information, and together with that management information, it is sent from the health check device 70 to the writing device 30, where it can be stored. However, the storage of new information about the patient's health check results and management information in the viewing device 50 and the health check device 70 is restricted.

[0058] On the other hand, if the health check device 70 determines that past health check results information for a patient corresponding to the reservation information is not stored in the viewing device 50, then, only if the health check device 70 has access to both the writing and viewing devices 30 and 50, the health check device 70 will assign a new management number to the patient, and the new health check result information for the patient entered in the health check device 70 will be associated with management information that includes the management number created in the health check device 70 based on the patient's reservation information, and sent from the health check device 70 to the writing device 30 together with that management information, so that it can be stored in the writing device 30. However, viewing and storing the new health check result information and management information for the patient in the health check devices 50 and 70 is restricted.

[0059] Referring to Figures 1, 2, 7, and 8, the system has an AP server (application server) 90 connected to the core DB server 10 by a first LAN 1. The reservation management system 100 has a distribution DB server (distribution database server) 120 configured to be connectable to the AP server 90 via the Internet 3. The distribution DB server 120 is configured to be connectable to the web server 110.

[0060] The reservation management system 100 is configured to accept requests from patients for delivery of their health check results when they make a reservation. The reservation management system 100 is configured to determine whether or not it has received a request from a patient for delivery of their health check results.

[0061] If the reservation management system 100 determines that it has received a request from a patient to receive their health checkup results, it includes the request information in the reservation information. In this case, the management information modified or created based on the reservation information will include information allowing the delivery of the patient's health checkup results, including new information about the patient's health checkup results, to the patient.

[0062] If the reservation management system 100 determines that it has not received a request from a patient to receive their health checkup results, it will either omit the request information from the management system or include information indicating that the patient does not need to receive the results. In this case, the management system modified or created based on the reservation information will either omit the information allowing delivery or include information restricting delivery of the patient's health checkup results to the patient.

[0063] Access from AP server 90 to distribution DB server 120 is permitted, while access from distribution DB server 120 to AP server 90 is restricted. AP server 90 is configured to manage the transmission of the patient's health checkup results from core DB server 10 to distribution DB server 120 via AP server 90 when the reservation information includes information that allows distribution.

[0064] The distribution DB server 120 is configured to acquire and store distribution information of the patient's health check results transmitted from the core DB server 10 via the AP server 90. The reservation management system 100 is configured to distribute the distribution information of the patient's health check results, which is associated with management information corresponding to the patient's reservation information, from the distribution DB server 120 to the patient's terminal device 200 via the web server 110.

[0065] "Details of the health checkup result management system" Referring to Figures 1-8, the health checkup result management system according to this embodiment can be configured in detail as follows.

[0066] Dental checkup results may include information about the condition of the patient's teeth. This information may include symbols representing the condition of multiple teeth. The checkup results may also include information about periodontal disease, periodontal pocket measurements, caries, tartar buildup, oral hygiene, special checkup results, oral condition, and estimated dental age.

[0067] The information regarding the affiliated group and the group subject to health checkups can include health insurance associations, health checkup institutions, health checkup venues, companies, etc. If the information regarding the affiliated group and the group subject to health checkups is a company, it may further include its business offices, factories, departments, etc.

[0068] Patient management information may include name, affiliated group, and management number. In addition to these, management information may also include insurance card number, appointment number, address, residence, telephone number, email address, date of birth, etc.

[0069] A patient's management number is assigned to identify that patient within the system and is maintained semi-permanently. The management information includes one or more numbers. In addition to numbers, this management information may include letters, symbols, hiragana, katakana, kanji, etc.

[0070] Patient appointment information may include appointment date and time, name, affiliated group, and preference for receiving health checkup results. In addition to these, appointment information may also include insurance card number, appointment number, address, residence, telephone number, email address, date of birth, etc.

[0071] Referring to Figure 6, code C is a matrix-type two-dimensional code. However, the code is not limited to this; it can also be a one-dimensional code, a stack-type two-dimensional code, etc.

[0072] Referring to Figures 3-5, each of the writing and viewing devices 30 and 50 is configured to be connectable to a computer or other device via an external bus, and is an external device separate from that device. In particular, each of the writing and viewing devices 30 and 50 should be configured to be portable on its own. Each of the writing and viewing devices 30 and 50 should be a so-called external portable device.

[0073] Referring to Figures 1, 2, and 4, the browsing device 50 is configured to be connectable to the external device 60 via its external bus 61. The browsing device 50 is configured to allow access to the external device 60 if the browsing ID and password are entered from the external device 60. The browsing device 50 is configured to restrict access to the external device 60 if at least one of the browsing ID and password is not entered from the external device 60.

[0074] With the internal device 20 permitted to access the core DB server 10 and the file server 40, and the external device 60 permitted to access the file server 40 and the viewing device 50, past information on the health check results of examinees, associated with management information including the group to which they belong corresponding to the health check target group information, is sent from the file server 40 to the viewing device 50 via the external device 60 and can be stored on the viewing device 50.

[0075] Referring to Figures 1, 5, and 6, the reading device 80 can be a camera, a code reader, or the like. The health check device 70 is configured to acquire the information contained in the code C read by the reading device 80.

[0076] The health check device 70 is configured to determine whether or not the examinee has presented code C. If the health check device 70 determines that the examinee has presented code C, it starts reading code C.

[0077] On the other hand, if the health check device 70 determines that the examinee has not presented code C, the health check device 70 will assign a new management number to the examinee, provided that the health check device 70 has access to both the write and view devices 30 and 50. New information regarding the examinee's health check results entered into the health check device 70 will be created by the health check device 70 based on the examinee's reservation information and associated with the management information including the newly assigned management number. This information will then be sent from the health check device 70 to the write device 30, where it will be available for storage.

[0078] Referring to Figures 1, 4, and 5, the external device 60 and the health check device 70 are different. However, the external device 60 and the health check device 70 can also be the same.

[0079] Referring to Figures 1 and 7, the AP server 90 is configured to individually determine whether or not each piece of new health checkup result information stored in the core DB server 10 is associated with reservation information including a request for delivery of health checkup results.

[0080] AP server 90 selects new health checkup results if they are associated with reservation information that includes a request for delivery of health checkup results. AP server 90 does not select new health checkup results if they are not associated with reservation information that includes a request for delivery of health checkup results.

[0081] The AP server 90 sends the distribution information of health check results, including the new information of health check results selected by this determination, from the core DB server 10 to the distribution DB server 120 via the AP server 90. In addition to the new information of the health check results of the examinee, the distribution information of health check results may also include past information of the examinee's health check results obtained up to one year ago, two years ago, or three years ago or more.

[0082] The reservation management system 100 is configured to determine whether or not a patient requested delivery of their health checkup results when making a reservation. If the reservation management system 100 determines that the patient requested delivery of their health checkup results when making a reservation, it includes the delivery request information in the reservation information. If the reservation management system 100 determines that the patient did not request delivery of their health checkup results when making a reservation, it either does not include the delivery request information in the reservation information or includes information indicating that delivery is not required.

[0083] The reservation management system 100 has a second LAN 101 installed inside it. In the reservation management system 100, the web server 110 and the DB server 120 can be connected via the second LAN 101. The web server 110 and the DB server 120 can also be connected via the Internet 3.

[0084] "network" Referring to Figures 1-5 and 7, the network used in the health checkup result management system according to this embodiment can be configured as follows.

[0085] The first LAN1 is a network managed within a specific, limited area A, such as a facility, building, or room of an organization, such as a company or group, that manages health checkup results. The second LAN101 is a network managed within the reservation management system 100. The first and second LANs1 and 101 may be either wired or wireless LANs, but a wired LAN is preferable, especially from the standpoint of preventing unauthorized access. The first and second LANs1 and 101 are distinct entities.

[0086] VPN2 can be an Internet VPN, IP (Internet Protocol)-VPN, entry-level VPN, or wide-area Ethernet. If VPN2 is an Internet VPN, it can be IPsec (Internet Protocol Security)-VPN, TLS (Transport Layer Security) / SSL (Secure Sockets Layer)-VPN, L2TP (Layer 2 Tunneling Protocol) / IPsec, OpenVPN, etc.

[0087] The Internet of Things (3) is a global computer network connected using the TCP (Transmission Control Protocol) / IP protocol, and is an open network accessible to anyone.

[0088] Hardware configuration Referring to Figures 1 to 8, the hardware configuration of the components of the health checkup result management system according to this embodiment can be as follows in detail.

[0089] As described above, the internal device 20, the external device 60, and the health check device 70 each have external buses 21, 61, and 71, respectively. External buses 21 to 71 are paths that connect equipment such as servers and devices to their external devices.

[0090] Each of the core DB server 10, internal device 20, write device 30, file server 40, browsing device 50, external device 60, health check device 70, AP server 90, web server 110, distribution DB server 120, and terminal device 200 has internal buses 12, 22, 32, 42, 52, 62, 72, 92, 112, 122, 202, control units 13, 23, 33, 43, 53, 63, 73, 93, 113, 123, 203, and storage units 14, 24, 34, 44, 54, 64, 74, 94, 114, 124, 204.

[0091] Internal buses 12-202 are paths that connect internal components of equipment such as servers and devices to each other. Control units 13-203 can be controllers configured to manage data transfer in the case of write and read devices 30 and 50, and in the case of devices other than write and read devices 30 and 50, they can be CPUs (Central Processing Units) configured to enable data management, calculations, control of equipment such as servers and devices.

[0092] When the control units 13-203 are in particular CPUs, they execute programs, software, processes, calculations, etc., stored in the memory units 14-204 according to commands based on input to devices, procedures defined in software, programs, etc., stored in the memory units 14-204, thereby controlling devices such as various components of the system and external devices connected to them. Through this control by the control units 13-203, various operations, operations, processes, and processes of the system can be executed.

[0093] The storage units 14-204 can store data such as health checkup results, programs, software, processes, and calculation formulas. The storage units 14-204 are configured to store information such as health checkup results. The storage units 14-204 can be, for example, SSDs (Solid State Drives), HDDs (Hard Disk Drives), flash memory, flash memory chips, etc.

[0094] Each of the internal device 20, writing device 30, viewing device 50, external device 60, and health check device 70 has input / output units 25, 35, 55, 65, and 75, respectively. External devices connected to input / output units 25 to 75 are connected to the device by external buses 21 to 71 and are capable of at least one of input and output to the device.

[0095] The input / output sections 25-75 can be ports, terminals, etc., for connecting equipment such as servers and devices to external equipment. For example, the input / output sections 25-75 can be ports, terminals, etc., such as USB (Universal Serial Bus) and HDMI (High-Definition Multimedia Interface). Although not specifically shown in the diagrams, input means that enable input to equipment such as servers and devices can be connected to the input / output sections 25-75. These input means can be keyboards, mice, etc.

[0096] Each of the core DB server 10, internal device 20, file server 40, external device 60, health check device 70, AP server 90, web server 110, distribution DB server 120, and terminal device 200 has communication units 16, 26, 46, 66, 76, 96, 116, 126, and 206, respectively.

[0097] Communication units 16-206 are configured to enable servers, devices, and other equipment to communicate with external equipment. Communication units 16-206 can be ports, devices, etc., that enable communication connections via wired LAN, wireless LAN, Bluetooth, internet lines, 4G, 5G, and other mobile communication networks using, for example, Ethernet ports, USB ports, etc.

[0098] Within the server, device, and other equipment, the control units 13-203, storage units 14-204, input / output units 25-75, and communication units 16-206 are connected to each other by internal buses 12-202.

[0099] Each of the internal, external, and health check devices 20, 60, 70 and terminal device 200 has a display unit 27, 67, 77, 207. The display units 27, 67, 77, 207 are configured to visually display information. The display units 27, 67, 77, 207 can be, for example, liquid crystal displays, organic EL (Electro-Luminescence) displays, and can also be touch panels that also serve as input means.

[0100] For example, the display units 27, 67, and 77 of the internal, external, and health check devices 20, 60, and 70 can be connected externally to the internal, external, and health check devices 20, 60, and 70 by external buses 21, 61, and 71 and input / output units 25, 65, and 75, respectively. For example, the display unit 207 of the terminal device 200 can also be connected internally to other internal components by an internal bus 202. However, the connections of the display units are not limited to these.

[0101] The health check device 70 is also connected to the reading device 80 by its external bus 71. However, the health check device may also be connected to the reading device by a LAN.

[0102] The core DB server 10, file server 40, AP server 90, web server 110, and distribution DB server 120 are all physical servers consisting of computers. The internal, external, health checkup devices, and terminal devices 20, 60, and 70 can each be, for example, PCs (Personal Computers), tablet computers, etc.

[0103] In particular, terminal device 200 can be, for example, a smartphone. Writing and viewing devices 30 and 50 can each be, for example, flash memory such as a USB flash memory, SSD, or SD card.

[0104] "Methods for managing health checkup results" Referring to Figures 9-14, an example of a health check result management method using the health check result management system according to this embodiment will be described.

[0105] Referring to Figure 9, the process of acquiring past and management information of health checkup results within the organization will be explained. The internal device 20 is connected to the core DB server 10 and the file server 40 by the first LAN 1, and is also connected to the viewing device 50 by the external bus 21 of the internal device 20 (step S11).

[0106] Step S12 determines whether the administrator correctly entered the database ID and password from the internal device 20 into the core DB server 10, correctly entered the file ID and password from the internal device 20 into the file server 40, and correctly entered the browsing ID and password from the internal device 20 into the browsing device 50.

[0107] If at least one of the database ID and password, file ID and password, or browsing ID and password is entered incorrectly (NO), the internal device 20 is restricted from accessing the core DB server 10, file server 40, and browsing device 50 (step S13). The process is then terminated.

[0108] If the database ID and password, file ID and password, and browsing ID and password are entered correctly (YES), the internal device 20 is allowed to access the core DB server 10, file server 40, and browsing device 50 (step S14).

[0109] When it is decided that a health checkup will be conducted for a designated group, the administrator inputs the health checkup target group information for the designated group that will undergo the health checkup into the internal device 20 (step S15). The internal device 20 acquires the health checkup target group information (step S16). The internal device 20 selects past health checkup results of examinees associated with management information including the group to which the health checkup target group information belongs from multiple or all of the past health checkup results stored in the core DB server 10 (step S17).

[0110] The internal device 20 sends past health check results information of selected patients, along with their management information, from the core DB server 10 to the file server 40 via the internal device 20 (step S18). The file server 40 stores and manages the sent past health check results information and management information for viewing purposes (step S19).

[0111] The internal device 20 sends past and management information of patient health check results, which are stored and managed for viewing on the file server 40, from the file server 40 to the viewing device 50 via the internal device 20 (step S20). The viewing device 50 stores the past and management information of patient health check results that has been sent (step S21). After that, the operation is completed.

[0112] Referring to Figure 10, the process of acquiring new and management information of health check results at the health check site will be explained. The health check device 70 is connected to the write and view devices 30 and 50 by the external bus 71 of the health check device 70 (step S31).

[0113] The system determines whether a physician such as a dentist, or an on-site operator such as a health checkup staff member, has correctly entered the write ID and password from the health checkup device 70 into the write device 30, and whether they have correctly entered the view ID and password into the view device 50 (step S32).

[0114] If at least one of the write ID and password, or the view ID and password, is entered incorrectly (NO), access to the write and view devices 30 and 50 is restricted from the health check device 70 (step S33). The operation is then terminated.

[0115] If the write ID and password, and the view ID and password are entered correctly (YES), the health check device 70 is allowed to access the write and view devices 30 and 50 (step S34).

[0116] The health check device 70 determines whether the patient has presented code C to the on-site operator (step S35). If the health check device 70 determines that the patient has presented code C to the on-site operator (YES), the reading device 80 reads code C (step S36). The health check device 70 obtains the reservation information contained in code C (step S37). The health check device 70 determines whether past information of the patient's health check results, associated with management information corresponding to the reservation information, is stored in the viewing device 50 (step S38).

[0117] If the health check device 70 determines that past health check results of a patient associated with management information corresponding to the reservation information are stored in the viewing device 50 (YES), the health check device 70 displays the past health check results and management information of that patient stored in the viewing device 50 on the display unit 77, associated with the reservation information (step S39).

[0118] The on-site operator inputs the new health check results information for the patient into the health check device 70 (step S40). The health check device 70 modifies the new health check results information for the patient based on the patient's reservation information and associates it with management information including the existing management number, and sends it to the writing device 30 together with the management information (step S41). The writing device 30 stores the new health check results information and management information for the patient (step S42).

[0119] If the health check device 70 determines in step S35 that the examinee has not presented code C to the on-site operator (NO), or if it determines in step S38 that past information of the examinee's health check results associated with management information corresponding to the reservation information is not stored in the viewing device 50 (NO), the health check device 70 assigns a new management number to that examinee (step S43).

[0120] The on-site operator inputs the new health check results information for the patient into the health check device 70 (step S44). The health check device 70 associates the new health check results information for the patient with management information, which is created based on the patient's reservation information and includes a newly assigned management number, and sends the management information together with the new health check results information to the writing device 30 (step S45). The writing device 30 stores the new health check results information and management information for the patient (step S46). The operation is then completed.

[0121] Referring to Figure 11, the process of storing new and management information of health check results within the organization will be explained. The internal device 20 is connected to the core DB server 10 by the first LAN 1, and is also connected to the write device 30 by the external bus 21 of the internal device 20 (step S51).

[0122] The administrator determines whether they have entered the database ID and password from the internal device 20 into the core DB server 10, and whether they have entered the write ID and password from the internal device 20 into the write device 30 (step S52).

[0123] If at least one of the database ID and password, or the write ID and password, is entered incorrectly (NO), the internal device 20 is restricted from accessing the core DB server 10 and the write device 30 (step S53). The process is then terminated.

[0124] If the database ID and password, as well as the write ID and password, are entered correctly (YES), the internal device 20 is allowed to access the core DB server 10 and the write device 30 (step S54).

[0125] The administrator gives instructions or performs operations on the internal device 20 to send new information and management information of the patient's health check results from the writing device 30 to the core DB server 10 via the internal device 20 (step S55). The core DB server 10 stores the new information, reservation information, and management information of the patient's health check results (step S56). After that, the operation is completed.

[0126] Referring to Figure 12, the process of storing new health checkup results and management information from outside the organization will be explained. The internal device 20 is connected to the core DB server 10 via the first LAN 1 and is also connected to the file server 40 via the first LAN 1 (step S61).

[0127] The administrator determines whether they have correctly entered the database ID and password from the internal device 20 into the core DB server 10, and whether they have correctly entered the file ID and password from the internal device 20 into the file server 40 (step S62).

[0128] If at least one of the database ID and password, or the file ID and password, is entered incorrectly (NO), the internal device 20 is restricted from accessing the core DB server 10 and the file server 40 (step S63). The process is then terminated.

[0129] If the database ID and password, and the file ID and password are entered correctly (YES), the internal device 20 is allowed to access the core DB server 10 and the file server 40 (step S64).

[0130] External device 60 is connected to file server 40 via VPN2 and is also connected to write device 30 via external bus 61 of external device 60 (step S65).

[0131] The on-site operator, such as a doctor or health checkup staff member, determines whether they have correctly entered the file ID and password from the external device 60 into the file server 40, and whether they have correctly entered the write ID and password from the external device 60 into the write device 30 (step S66).

[0132] If at least one of the file ID and password, or the write ID and password, is entered incorrectly (NO), access by the external device 60 to the file server 40 and the write device 30 is restricted (step S67). The process is then terminated.

[0133] If the file ID and password, as well as the write ID and password, are entered correctly (YES), the external device 60 is allowed to access the file server 40 and the write device 30 (step S68).

[0134] The on-site staff member gives instructions or performs operations on the external device 60 to send new information and management information of the patient's health check results from the writing device 30 to the file server 40 via the external device 60 (step S69). The file server 40 stores the new information and management information of the patient's health check results (step S70).

[0135] The administrator instructs or operates the internal device 20 to send new and management information of the patient's health check results from the file server 40 to the core DB server 10 via the internal device 20 (step S71). The core DB server 10 stores the new and management information of the patient's health check results (step S72). After that, the operation is completed.

[0136] Referring to Figure 13, the process of booking a health checkup will be explained. The patient accesses the reservation management system 100 from the terminal device 200 to book a health checkup (step S81). The patient selects whether or not they wish to receive the health checkup results via the operation of the terminal device 200 (step S82).

[0137] If the user does not select to receive the health checkup results (NO), the terminal device 200 sends reservation information that does not include the information requested for delivery or reservation information that does not include the information requested for delivery to the web server 110 (step S83). If the user selects to receive the health checkup results (YES), the terminal device 200 sends reservation information that includes the information requested for delivery to the web server 110 (step S84).

[0138] Following steps S83 and S84, the reservation management system 100 determines whether the reservation information includes the information to be distributed (step S85). If the reservation management system 100 determines that the reservation information does not include the information to be distributed (NO), the operation is terminated.

[0139] If the reservation management system 100 determines that the reservation information includes information to be distributed (YES), the web server 110 creates a code C containing the reservation information (step S86). The web server 110 sends code C to the terminal device 200 (step S87). The terminal device 200 displays code C on the display unit 207 (step S88). The process then ends.

[0140] Referring to Figure 14, the process of distributing health checkup result information will be explained. The AP server 90 individually determines whether any new health checkup result information, whether multiple or all of it, stored in the core DB server 10 is associated with reservation information that includes the information to be distributed (step S91).

[0141] If the AP server 90 determines that new information regarding a patient's health check results is associated with reservation information that includes information requested for distribution (YES), it selects the new information regarding that patient's health check results, and if necessary, further selects the past information (step S92).

[0142] The AP server 90 sends distribution information, which includes the health check results of the selected patients and, in some cases, their past information, from the core DB server 10 to the distribution DB server 120 via the AP server 90 (step S93). The distribution DB server 120 stores the distribution information of the patients' health check results that it has received (step S94).

[0143] The web server 110 sends the distribution information of the patient's health check results, stored in the distribution DB server 120, from the distribution DB server 120 to the patient's terminal device 200 via the web server 110 (step S95). The terminal device 200 displays the distribution information of the patient's health check results on its display unit 207 (step S96). The process then ends.

[0144] If the AP server 90 determines in step S91 that the new information regarding the patient's health check results is not associated with the reservation information that includes the information to be distributed (NO), the process is terminated.

[0145] As described above, according to the health check result management system of this embodiment, new information and management information of the examinee's health check results are sent from the write device 30 to the core DB server 10 via the internal device 20 and can be stored in the core DB server 10 only when the database ID and password are correctly entered from the internal device 20 to the core DB server 10 and the write ID and password are correctly entered from the internal device 20 to the write device 30.

[0146] Therefore, in order to store new and management information of the patient's health check results from the writing device 30 in the core DB server 10, dual authentication using an ID and password is required. Furthermore, since access from the writing device 30 to the core DB server 10 is performed using physically managed connection means such as the first LAN1 and external bus 21, information leakage and information tampering can be efficiently prevented. Thus, health check results can be strictly managed.

[0147] According to the health check result management system of this embodiment, only when the database ID and password are correctly entered from the internal device 20 to the core DB server 10, the file ID and password are correctly entered from the internal device 20 to the file server 40, and the viewing ID and password are correctly entered from the internal device 20 to the viewing device 50, past health check result information and management information of the examinee associated with management information including the group to which they belong corresponding to the health check target group information are selected from multiple or all past health check result information stored in the core DB server 10, sent from the core DB server 10 to the file server 40 via the internal device 20, and made available for viewing and management in the file server 40. Furthermore, such past health check result information of the examinee is sent from the file server 40 to the viewing device 50 via the internal device 20, and made available for storage in the viewing device 50.

[0148] Therefore, in order to store past and management information of the patient's health check results in the viewing device 50, triple authentication using an ID and password is required. Furthermore, since access between the core DB server 10, internal device 20, viewing device 50, and file server 40 is performed using physically managed connection means such as the first LAN1 and external bus 21, information leakage and information tampering can be efficiently prevented. Thus, health check results can be strictly managed.

[0149] According to the health check result management system of this embodiment, new information and management information of the examinee's health check results are sent from the write device 30 to the core DB server 10 via the external device 60, file server 40, and internal device 20, and can be stored in the core DB server 10, only when the database ID and password are correctly entered from the internal device 20 to the core DB server 10, the file ID and password are correctly entered from the internal and external devices 20 and 60 to the file server 40, and the write ID and password are correctly entered from the external device 60 to the write device 30.

[0150] Therefore, in order to store new and management information of patient health check results sent from outside the organization in the core DB server 10, quadruple authentication using IDs and passwords is required. Furthermore, since access from the writing device 30 to the core DB server 10 is performed using communication means that encrypt and send / receive data, such as VPN2, and connection means that are physically managed within the organization, such as the first LAN1 and external buses 21 and 61, information leakage and information tampering can be efficiently prevented even when it becomes necessary to send new and management information of health check results from outside the organization.

[0151] Therefore, it is possible to send new and managed information of the patient's health check results from the writing device 30 to the core DB server 10 while strictly managing it within the organization and storing it in the core DB server 10, as well as to send new and managed information of the patient's health check results from the writing device 30 to the core DB server 10 while strictly managing it outside the organization and storing it in the core DB server 10.

[0152] According to the health check result management system of this embodiment, both the writing and viewing devices 30 and 50 are connected to the health check device 70 by their external bus 71. Only when the writing ID and password are correctly entered from the health check device 70 to the writing device 30, and the viewing ID and password are correctly entered from the health check device 70 to the viewing device 50, past information and management information of the patient's health check results stored in the viewing device 50 can be displayed on the health check device 70, and new information and management information of the patient's health check results can be stored only in the writing device 30.

[0153] Therefore, in order to store new and management information of health check results in the writing device 30, three specific devices are required: the writing and viewing devices 30 and 50, and the health check device 70. Since dual authentication using an ID and password is required, it is difficult for outsiders to store data other than legitimate health check results in the writing device 30. Thus, information leakage and information tampering can be effectively prevented, and as a result, health check results can be strictly managed.

[0154] According to the health check result management system of this embodiment, when a patient makes a reservation for a health check using the reservation management system 100, they can obtain a code C containing reservation information and present that code C at the health check site, thereby easily and reliably informing on-site operators such as doctors and health check staff of the reservation information. Furthermore, if the patient has undergone a health check managed by the health check result management system, the on-site operator can obtain new health check result information along with management information corrected based on the reservation information, while displaying past information of the patient's health check results associated with the management information corresponding to the reservation information.

[0155] Therefore, it is possible to reliably prevent misidentification of patients at health checkup sites and improve the convenience of handling health checkup results.

[0156] According to the health check result management system of this embodiment, even if a patient has not previously undergone a health check managed by the health check result management system, new health check result information can be obtained at the health check site, along with management information including a newly assigned management number created based on the reservation information.

[0157] Therefore, it is possible to reliably prevent misidentification of patients at health checkup sites and improve the convenience of handling health checkup results.

[0158] According to the health check result management system of this embodiment, if a patient requests to receive their health check results when making a reservation for a health check, only the health check result distribution information associated with that reservation information can be sent from the core DB server 10 to the distribution DB server 120 via the AP server 90, and the patient can receive their health check result distribution information from the distribution DB server 120 via the web server 110 on the terminal device 200.

[0159] In this case, access from the distribution DB server 120 to the AP server 90 is restricted, and information cannot be sent from the distribution DB server 120 to the core DB server 10. Therefore, it is possible to reliably prevent the unauthorized sending of patients' health check results from the core DB server 10 to the distribution DB server 120, thereby preventing information leakage. Thus, while strictly managing all health check results within the core DB server 10, it is possible to improve the convenience of handling the distribution information of recipients' health check results at the request of patients.

[0160] Although embodiments of the present invention have been described so far, the present invention is not limited to the embodiments described above, and the present invention can be modified and changed based on its technical concept. [Explanation of Symbols]

[0161] 1…LAN (First LAN), 2…VPN, 3…Internet, 10…Core DB Server, 20…Internal Device, 21…External Bus, 30…External Write / Storage Device (Write Device), 40…File Server, 50…External Read / Read / Storage Device (Read / Read Device), 60…External Device, 61…External Bus, 70…Health Check Device, 71…External Bus, 80…Read Device, 90…AP Server 100...Reservation management system, 110...Web server, 120...Distribution DB server 200... Terminal device, C... Code

Claims

1. A health checkup result management system configured to manage the health checkup results of patients obtained during health checkups, A core DB server configured to store the health check results of the aforementioned patient, as well as management information including the patient's name, affiliated group, and management number, An internal device configured to be connectable to the aforementioned core DB server via LAN, An external write storage device is configured to store new information and management information of the patient's health check results, and is configured to be connectable to the internal device via its external bus. Equipped with, The core DB server is configured to allow access to the internal device when its database ID and the database password corresponding to the database ID are entered from the internal device. The external write storage device is configured to allow access to the internal device when its write ID and the write password corresponding to the write ID are input from the internal device. A health checkup result management system is configured such that, with the internal device permitted to access the core DB server and the external write storage device, new information and management information of the patient's health checkup results are sent from the external write storage device to the core DB server via the internal device and can be stored in the core DB server.

2. A file server configured to store the health check results and management information of the aforementioned patient, and configured to be connectable to the internal device via the LAN, An external browsing and storage device is configured to store past information and management information of the patient's health check results, and is configured to be connectable to the internal device via its external bus. Equipped with, The file server is configured to allow the internal device to access the file server when the file ID and the file password corresponding to the file ID are entered into the file server from the internal device. The external browsing storage device is configured to allow the internal device to access the external browsing storage device when its browsing ID and the browsing password corresponding to the browsing ID are input to the external browsing storage device from the internal device. The internal device is configured to acquire health check target group information relating to a predetermined group undergoing a health check, and is configured to select past health check result information of the examinee associated with management information including the group to which the examinee belongs, from multiple or all past health check result information stored in the core DB server. With the internal device permitted to access the core DB server and the file server, past health check results of examinees associated with management information including the group to which they belong corresponding to the health check target group information are selected by the internal device from the past health check results of multiple or all of the past health check results, sent from the core DB server to the file server via the internal device, and configured to be stored and managed for viewing on the file server. The health check result management system according to claim 1, wherein the internal device is permitted to access the file server and the external browsing and storage device, and past information of the health check results of a patient associated with management information including the group to which the patient belongs corresponding to the health check target group information is sent from the file server to the external browsing and storage device via the internal device and is configured to be stored in the external browsing and storage device.

3. The file server is configured to be connectable via VPN, and the external device is configured to be connectable to the external write and read storage device via the external bus of the external device, The file server is configured to allow access to the external device when the file ID and password are entered from the external device. The external write storage device is configured to allow access to the external device when the write ID and password are input from the external device. With the external device permitted to access the file server and the external write storage device, new information and management information of the patient's health check results are configured to be sent from the external write storage device to the file server via the external device and stored in the file server. The health check result management system according to claim 2, wherein the internal device is permitted to access the core DB server and the file server, and new information and management information of the patient's health check results are sent from the file server to the core DB server via the internal device and are configured to be stored in the core DB server.

4. The health check device is configured to be connectable to the external write and read storage device via an external bus of the health check device, The health check device is configured to display past and management information of the patient's health check results, and to allow input of new information of the patient's health check results. The external write storage device is configured to allow access to the health check device when the write ID and password are entered from the health check device. The external browsing storage device is configured to allow access to the health check device when the browsing ID and password are entered from the health check device. The health check result management system according to claim 2, wherein the health check device is in a state where it can access both the external write and read / store storage devices, past information and management information of the patient's health check results stored in the external read / store storage device are sent from the external read / store storage device to the health check device so that they can be displayed on the health check device, and new information of the patient's health check results entered in the health check device is sent from the health check device to the external write / store storage device together with the management information so that it can be stored on the external write / store storage device.

5. A reading device configured to read the code, A reservation management system configured to allow the aforementioned patient to make a health checkup reservation, Equipped with, The reservation management system has a web server configured to communicate with the patient's terminal device, and is configured to transmit the code containing the patient's reservation information from the web server to the patient's terminal device. The reading device is connected to the health check device so that it can send the code displayed on the terminal device to the health check device. The health check device is configured to acquire the patient's reservation information contained in the code sent from the reading device, and to determine whether or not past information of the patient's health check results associated with the management information corresponding to the reservation information is stored in the external viewing storage device. The health check result management system according to claim 4, wherein when the health check device determines that past information of the patient's health check results associated with the management information corresponding to the reservation information is stored in the external viewing storage device, the health check device is configured to access both the external writing and viewing storage devices, and the past information of the patient's health check results and the management information stored in the external viewing storage device are sent from the external viewing storage device to the health check device and displayed on the health check device, and new information of the patient's health check results entered in the health check device is associated with the management information modified by the health check device based on the patient's reservation information and sent together with the management information from the health check device to the external writing storage device so that it can be stored in the external writing storage device.

6. The health check result management system according to claim 5, wherein if the health check device determines that past information of the patient's health check results corresponding to the reservation information is not stored in the external viewing storage device, the health check device, with access to both the external writing and viewing storage devices, assigns a new management number to the patient at the health check device, and the new information of the patient's health check results entered at the health check device is associated with management information created at the health check device based on the patient's reservation information and including the newly assigned management number, and is sent from the health check device to the external writing storage device together with the management information, so that it can be stored in the external writing storage device.

7. The core DB server is equipped with an AP server connected via the LAN, The aforementioned reservation management system is configured to be connectable to the AP server via the Internet, and has a distribution DB server configured to be connectable to the web server, and is configured to accept requests from patients for the distribution of their health check results when a reservation is made. The aforementioned reservation information and the management information modified or created based on the aforementioned reservation information include, when the reservation management system receives a request from the patient to deliver the patient's health check results, delivery permission information that allows the delivery of the patient's health check results, including at least new information about the patient's health check results, to be delivered to the patient. The system is configured such that access from the AP server to the distribution DB server is permitted, while access from the distribution DB server to the AP server is restricted. The AP server is configured to manage the transmission of the patient's health checkup results from the core DB server to the distribution DB server via the AP server when the reservation information includes the distribution permission information. The distribution DB server is configured to acquire and store the distribution information of the patient's health check results transmitted from the core DB server via the AP server. The health check result management system according to claim 5 or 6, wherein the reservation management system is configured to enable the distribution of distribution information of the patient's health check results, associated with the management information corresponding to the patient's reservation information, from the distribution DB server to the patient's terminal device via the web server.

Images