Specimen testing system
The specimen inspection system addresses high introduction costs by reusing existing equipment and implementing access control, achieving cost reduction and improved confidentiality in multi-facility data exchange.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-02-01
- Publication Date
- 2026-04-01
AI Technical Summary
The introduction cost of specimen inspection systems is high when the specimen inspection function of one medical facility is made available in other medical facilities, due to the need for new equipment and infrastructure.
A specimen inspection system that reuses existing testing server computers and information terminals from core medical facilities, with access control mechanisms to manage access requests from both core and non-core medical facilities, ensuring secure and confidential data exchange.
Reduces the introduction cost of specimen inspection systems by reusing existing equipment and enhances data confidentiality through controlled access, preventing information leakage between facilities.
Smart Images

Figure 0007839206000001 
Figure 0007839206000002 
Figure 0007839206000003
Abstract
Description
Technical Field
[0001] The present invention relates to a specimen inspection system for inspecting a specimen collected from a subject in a special medical facility.
Background Art
[0002] As conventional specimen inspection systems, as shown in Patent Document 1 and Patent Document 2, there are those that enable the use of the specimen inspection function possessed by one medical facility (special medical facility) in other medical facilities (specific medical facilities).
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Patent Document 2
Summary of the Invention
Problems to be Solved by the Invention
[0004] In recent years, due to improvements in the convenience of regional medical care and the effective utilization of medical resources, etc., attention has been increasing regarding the co-use of the specimen inspection function of one medical facility (special medical facility) with other medical facilities (specific medical facilities). However, when the specimen inspection function is made available in other medical facilities as in the specimen inspection systems described in Patent Document 1 and Patent Document 2, there is a problem that the introduction cost of the specimen inspection system becomes large.
[0005] The present invention has been made paying attention to such problems, and an object thereof is to provide a specimen inspection system capable of reducing the introduction cost.
Means for Solving the Problems
[0006] In order to solve the above-described problems, the specimen inspection system according to claim 1 of the present invention is A testing server computer located within a core medical facility that has a specimen testing facility capable of performing specimen testing, A special information terminal is provided within the aforementioned core medical facility and is connected to the aforementioned testing server computer in a manner that allows access to it. Equipped with, The aforementioned testing server computer has an internal testing request acceptance function for receiving requests for specimen testing from the aforementioned special information terminal, and is an already operational specimen testing system, A medical facility smaller than the aforementioned core medical facility and not having the aforementioned specimen testing facility is located within a non-core medical facility, and further comprises a specific information terminal connected to the aforementioned testing server computer in a manner that allows access to it. The aforementioned test server computer is: It has a storage means capable of storing information related to specimen testing, A new program for accepting external test requests is installed to provide an external test request acceptance function that accepts requests for specimen testing from the aforementioned specific information terminal. The system further includes access control means that, when the special information terminal accesses the inspection server computer, allows access only to information related to specimen testing requested by the core medical facility. 、 before The special information terminal and the specified information terminal are capable of transmitting access request information to request access to information related to specimen testing. The access control means is capable of determining whether the source of the access request information is the special information terminal or the specific information terminal, based on the terminal identification information contained in the received access request information. The aforementioned terminal identification information is in a format in which the information format of the terminal identification information used in the already operational specimen testing system is supplemented with the information assigned to the non-core medical facility. It is characterized by the following. According to this characteristic, Since existing testing server computers and special information terminals installed within core medical facilities can be reused, the cost of introducing a specimen testing system can be reduced.This makes it possible to reuse terminal identification information from existing special information terminals installed in core medical facilities for special information terminals installed in non-core medical facilities, enabling access control without significantly altering existing specimen testing systems.
[0007] The specimen testing system described in means 1 of the present invention is A specimen testing system for testing specimens collected from subjects within a special medical facility (for example, core hospital H01), A testing server computer (for example, testing server 103) installed within the aforementioned special medical facility, A special information terminal (for example, in-hospital clients 121, 122, 123, 124C, 125C, 126C) is installed within the special medical facility and connected to the testing server computer so as to be able to access it, A specific information terminal (for example, an off-site client C01CA, C02CA, C02CB, C03CA) is installed in a specific medical facility different from the aforementioned special medical facility (for example, off-site facilities C01, C02, C03) and is connected to the aforementioned testing server computer in a manner that allows it to access the testing server computer, Equipped with, The aforementioned test server computer is: A storage means (for example, storage unit 103d) including a special storage unit (for example, an in-hospital specimen testing information storage area) capable of storing specimen testing information related to specimen testing requested by the special medical facility, and a specific storage unit (for example, a first off-site facility specimen testing information storage area, a second off-site facility specimen testing information storage area, and a third off-site facility specimen testing information storage area) capable of storing specimen testing information related to specimen testing requested by the specific medical facility, Access control means (for example, a control unit 103a using an access control module) capable of controlling whether or not access to the special memory unit and the specified memory unit is permitted, It has, The special information terminal and the specific information terminal are capable of transmitting access request information (e.g., test request information, test result inquiry information, test result request information) to request access to the specimen test information. When the access control means receives the access request information from the special information terminal, it executes special access control that allows the special information terminal to access the special storage unit but prevents the special information terminal from accessing the specific storage unit. When the access request information is received from the specific information terminal, it executes specific access control that allows the specific information terminal to access the specific storage unit but prevents the specific information terminal from accessing the special storage unit. (For example, when the control unit 103a receives test request information, test result inquiry information, and test result request information from in-hospital clients 121, 122, and 123, it enables the in-hospital clients 121, 122, and 123 to access the in-hospital specimen test information storage area.) In both cases, access to the first, second, or third external facility specimen testing information storage area by in-hospital clients 121, 122, and 123 is disabled. However, if test request information, test result inquiry information, or test result request information is received from external clients C01CA, C02CA, C02CB, and C03CA, access to the first, second, or third external facility specimen testing information storage area by external clients C01CA, C02CA, C02CB, and C03CA is enabled, while access to the in-hospital specimen testing information storage area by external clients C01CA, C02CA, C02CB, and C03CA is disabled. It is characterized by the following. This feature makes it possible to prevent the leakage of specimen testing information from special medical facilities to designated medical facilities, and vice versa, thereby improving the confidentiality of the specimen testing system.
[0008] The specimen testing system described in means 2 of the present invention is the specimen testing system described in means 1, The access control means is formed by an access control program installed on a test server computer equipped with the storage means, in which the specific storage unit is added to the existing special storage unit. It is characterized by the following. According to this feature, it becomes possible to divert the existing inspection server computer and the existing special information terminal installed in the special medical facility, so that the introduction cost of the specimen inspection system can be reduced.
[0009] The specimen inspection system according to means 3 of the present invention is the specimen inspection system according to means 1 or means 2, The access request information includes terminal identification information that can identify whether the source of the access request information is the special information terminal or the specific information terminal, When the access control means determines that the source of the access request information specified from the terminal identification information included in the received access request information is the special information terminal, the special access control is executed, and when the source of the access request information specified from the terminal identification information included in the received access request information is the specific information terminal, the specific access control is executed. It is characterized by the following. According to this feature, the access control means can execute special access control or specific access control based on the terminal identification information included in the access request information, so that the processing load of the access control means can be significantly reduced, and the occurrence of access delay can be prevented.
[0010] The specimen inspection system according to means 4 of the present invention is the specimen inspection system according to means 3, The terminal identification information that can identify the specific information terminal is in a format in which additional information given to the specific medical facility is added to the information format of the terminal identification information that can identify the special information terminal. It is characterized by the following. According to this feature, it becomes possible to divert the terminal identification information of the existing specimen inspection system provided in the existing special medical facility, and the load of changing the existing specimen inspection system can be reduced, so that the introduction cost of the specimen inspection system can be further reduced.
[0011] The specimen inspection system described in means 5 of the present invention is the specimen inspection system described in any of means 1 to 4, and the specific information terminal includes a first specific information terminal provided in a first specific medical facility included in the specific medical facility, and a second specific information terminal provided in a second specific medical facility different from the first specific medical facility, the specific storage unit includes a first specific storage unit capable of storing specimen inspection information related to a specimen inspection requested from the first specific medical facility, and a second specific storage unit capable of storing specimen inspection information related to a specimen inspection requested from the second specific medical facility, when the access control means receives the access request information from the first specific information terminal to the specimen inspection information, it enables access to the first specific storage unit by the first specific information terminal but disables access to the second specific storage unit by the first specific information terminal, and when it receives the access request information from the second specific information terminal to the specimen inspection information, it enables access to the second specific storage unit by the second specific information terminal but disables access to the first specific storage unit by the second specific information terminal is characterized by this. According to this feature, it is possible to prevent the specimen inspection information of the first specific medical facility from leaking to the second specific medical facility or the specimen inspection information of the second specific medical facility from leaking to the first specific medical facility, and the confidentiality of the specimen inspection system can be further improved.
Brief Description of the Drawings
[0012] [Figure 1] It is a schematic diagram showing the specimen inspection system in the embodiment. [Figure 2] (A) is a configuration diagram of the inspection server, and (B) is an explanatory diagram of the data stored in the storage unit. [Figure 3](A) is a schematic diagram showing the operation of the control unit when an in-hospital client accesses the testing server, (B) is a schematic diagram showing the operation of the control unit when an external client accesses the testing server, (C) is a diagram showing the configuration of data received by the testing server from an in-hospital client, and (D) is a diagram showing the configuration of data received by the testing server from an external client. [Figure 4] This is an explanatory diagram of the patient data table, test request data table, and test result data table stored in the hospital's internal database. [Figure 5] This is an explanatory diagram of the patient data table, test request data table, and test result data table stored in the external database. [Figure 6] This diagram shows the in-hospital user information table and the out-of-hospital user information table stored in the user database. [Figure 7] This is a diagram illustrating the interaction when a test request is sent from an in-hospital client or an external client to the test server. [Figure 8] This is a diagram illustrating the interaction when a test request is sent from an in-hospital client or an external client to the test server. [Figure 9] This diagram illustrates the interaction process when a sample is tested in the laboratory and then stored on the testing server. [Figure 10] This diagram illustrates the interaction that occurs when an in-hospital client or an external client receives a test completion notification from the test server after submitting a test request. [Figure 11] This diagram illustrates the interaction that occurs when an in-hospital client or an external client receives a test completion notification from the test server after submitting a test request. [Figure 12] This diagram illustrates the interaction between an in-hospital client and an external client when they receive test result data from the test server after the test is completed. [Figure 13] This diagram illustrates the interaction between an in-hospital client and an external client when they receive test result data from the test server after the test is completed. [Modes for carrying out the invention]
[0013] The embodiments for implementing the specimen testing system according to the present invention will be described below based on examples. [Examples]
[0014] The sample testing system according to the example will be described with reference to Figures 1 to 13.
[0015] First, let's describe the core hospital H01, which has a specimen testing function. As shown in Figure 1, the core hospital H01 is equipped with an electronic medical record server 120, which is a server computer with a built-in storage unit (hard disk drive or solid-state drive) that stores the electronic medical record data of patients who have visited the core hospital H01. In this embodiment, the electronic medical record server 120 is a server computer specifically built to store electronic medical record data in a database within the core hospital H01, but the present invention is not limited to this, and the electronic medical record server 120 may be built using a commercially available personal computer.
[0016] The electronic medical record server 120 is connected to the in-hospital clients 121, 122, and 123, which are client computers installed in each examination room, via the in-hospital LAN (Local Area Network). These in-hospital clients 121, 122, and 123 are commercially available personal computers equipped with display devices such as displays capable of displaying images, input devices such as keyboards and mice, and relatively high-speed communication capabilities with the electronic medical record server 120 and the examination server 103 (described later) via the in-hospital LAN. Therefore, in each examination room, users such as doctors can operate the in-hospital clients 121, 122, and 123 to view the electronic medical records of each patient being examined stored in the electronic medical record server 120, and update the examination information stored in the electronic medical records as needed by operating the keyboard and mouse. The electronic medical record system is composed of these in-hospital clients 121, 122, and 123 and the electronic medical record server 120.
[0017] In this embodiment, the electronic medical record system is exemplified by a configuration in which a dedicated server computer (electronic medical record server 120) is installed within the core hospital H01 to database and record electronic medical record data. However, the present invention is not limited to this, and the electronic medical record server 120 may be a server computer installed outside the core hospital H01.
[0018] Furthermore, the core hospital H01 is equipped with a specimen collection room for collecting specimens from patients and wards for accommodating inpatients. These specimen collection rooms and wards are equipped with in-house clients 124C, 125C, and 126C, which are generally commercially available client computers (personal computers) similar to the in-house clients 121, 122, and 123 installed in each examination room, and which have relatively high-speed communication capabilities with the electronic medical record server 120 and the laboratory server 103 (described later) via the in-house LAN. These in-house clients 124C, 125C, and 126C are connected to barcode readers 124R, 125R, and 126R for reading barcode labels (described later) used for specimen testing. Each examination room, specimen collection room, and ward is also equipped with printers 131, 132, 133, 124P, 125P, and 126P, which can print barcode labels including one-dimensional barcodes upon instruction from the laboratory server 103 (described later).
[0019] The barcode readers 124R, 125R, and 126R are commercially available scanning devices that extract data by shining light onto a one-dimensional barcode, capturing the reflected light, and converting it into a binary digital signal. In this embodiment, the barcode readers 124R, 125R, and 126R are illustrated as being capable of reading one-dimensional barcodes, but the present invention is not limited to this, and may also be capable of reading two-dimensional barcodes.
[0020] Furthermore, while the printers 131, 132, 133, 124P, 125P, and 126P in this embodiment are commercially available printers capable of printing on materials other than barcode labels, the present invention is not limited to these, and may also be dedicated printers for printing barcode labels. Moreover, the printing method of printers 131, 132, 133, 124P, 125P, and 126P may be a laser type that fixes toner powder to paper by melting it with heat, or an inkjet type that sprays droplets of ink onto paper.
[0021] Furthermore, within the core hospital H01, there are multiple laboratories (Laboratory 1, Laboratory 2, Laboratory 3, etc.) for testing specimens collected from patients in the specimen collection room. These laboratories are equipped with laboratory clients 104C, 105C, and 106C, which allow for confirmation of test details and input of specimen test results. These laboratory clients 104C, 105C, and 106C are commercially available client computers (personal computers) similar to the in-hospital clients 121, 122, and 123, and are connected to barcode readers 104R, 105R, and 106R, similar to the barcode readers 124R, 125R, and 126R.
[0022] Furthermore, each laboratory is equipped with printers 104P, 105P, and 106P that can print barcode labels in response to instructions from the testing server 103 (described later), as well as testing preparation systems 104S, 105S, and 106S that automatically attach the barcode labels printed by these printers 104P, 105P, and 106P to the sample containers.
[0023] Furthermore, the inspection clients 104C, 105C, and 106C, like the in-hospital clients 121, 122, 123, 124C, 125C, and 126C, are commercially available client computers (personal computers) that have a display device such as a display, an input device such as a keyboard or mouse, and a relatively high-speed communication function with the inspection server 103 via the LAN within the inspection system. Furthermore, the barcode readers 104R, 105R, and 106R only need to have the same functions as the barcode readers 124R, 125R, and 126R, and the printers 104P, 105P, and 106P only need to have the same functions as the printers 131, 132, 133, 124P, 125P, and 126P.
[0024] Furthermore, the test sample preparation systems 104S, 105S, and 106S differ from the test clients 104C, 105C, and 106C, the barcode readers 104R, 105R, and 106R, and the printers 104P, 105P, and 106P. They are specifically designed for situations such as when performing a large number of sample tests at once, and automatically affix barcode labels to sample containers.
[0025] Furthermore, the core hospital H01 is equipped with a server computer, the laboratory server 103. This laboratory server 103 is connected via the hospital LAN to the electronic medical record server 120, hospital clients 121, 122, 123, 124C, 125C, 126C, and printers 131, 132, 133, 124P, 125P, and 126P. It is also connected via the laboratory system's LAN (local area network) to laboratory clients 104C, 105C, 106C, printers 104P, 105P, 106P, and laboratory sample preparation systems 104S, 105S, and 106S, enabling bidirectional communication. These components—the inspection server 103, in-hospital clients 121, 122, 123, 124C, 125C, 126C, inspection clients 104C, 105C, 106C, barcode readers 124R, 125R, 126R, 104R, 105R, 106R, printers 131, 132, 133, 124P, 125P, 126P, 104P, 105P, 106P, and sample collection preparation systems 104S, 105S, 106S—constitute a specimen testing system for performing specimen testing within the core hospital H01.
[0026] In this embodiment of the specimen testing system, specimen collection and testing can be performed from patients in the following order. 1. When a request for specimen testing is made from in-hospital clients 121, 122, and 123 in each examination room, the testing server 103 prints barcode labels containing information such as the patient from whom the specimen is to be collected and the specimen testing items from printers 131, 132, and 133 corresponding to the in-hospital clients 121, 122, and 123 that made the request for specimen testing. 2. Have the patient take a test form indicating that they are eligible for specimen testing, along with a printed barcode label, and have them proceed to the specimen collection room. 3. In the specimen collection room, the user of the in-hospital client 124C receives the test form and barcode label from the patient to be tested, and attaches the received barcode label to the specimen container. The user of the in-hospital client 124C also uses the barcode reader 124R to read the specimen test items from the barcode label attached to the specimen container, and collects the specimen corresponding to the read specimen test items. At this time, the collected specimen is transported to each laboratory in the specimen container. 4. In each laboratory, users of the testing clients 104C, 105C, and 106C use the barcode readers 104R, 105R, and 106R to read the test items from the barcode labels attached to the sample containers, and perform the test for the read test items. After the test is completed, the test result data is transmitted to the testing server 103.
[0027] Furthermore, once all items of each specimen test requested by in-hospital clients 121, 122, and 123 have been completed and the data of the test results has been transmitted to and stored in the testing server 103, the in-hospital clients 121, 122, and 123 can access the testing server 103 and view the results of each specimen test.
[0028] Thus, the specimen testing system of the present invention is a system that receives test requests from in-hospital clients 121, 122, and 123 within the core hospital H01, performs specimen testing within the core hospital H01, and makes the results of said specimen testing available to in-hospital clients 121, 122, and 123 within the core hospital H01. However, it also has a function that allows specimen testing to be performed on specimens collected at external facilities C01, C02, and C03, which are different from the core hospital H01, and makes the results of said specimen testing available to external clients C01CA, C02CA, and C03CA installed at each of the external facilities C01, C02, and C03.
[0029] Specifically, as shown in Figure 1, outside the core hospital H01, there are several off-site facilities C01, C02, and C03, which are relatively smaller in scale than the core hospital H01, such as clinics. Within these off-site facilities C01, C02, and C03, there are one or more off-site clients (in the example shown in Figure 1, off-site facility C01 has off-site client C01CA, off-site facility C02 has off-site client C02CA and off-site client C02CB, and off-site facility C03 has off-site client C03CA) and printers C01P, C02P, and C03P that can print barcode labels.
[0030] The external clients C01CA, C02CA, C02CB, and C03CA are generally commercially available personal computers that, like the internal clients 121, 122, 123, 124C, 125C, and 126C, and the examination clients 104C, 105C, and 106C, have display devices such as displays, input devices such as keyboards and mice, and relatively high-speed communication capabilities with the examination server 103 via the internet. Printers C01P, C02P, and C03P only need to have the same functions as printers 131, 132, 133, 124P, 125P, 126P, 104P, 105P, and 106P.
[0031] These external clients C01CA, C02CA, C02CB, C03CA and printers C01P, C02P, C03P are connected to the internet via routers C01L, C02L, C03L, which are relay and transfer devices for the computer network. Similarly, the testing server 103 is also connected to the internet via router 102, which is the same router as C01L, C02L, C03L. Therefore, the external clients C01CA, C02CA, C02CB, C03CA and printers C01P, C02P, C03P can communicate bidirectionally with the testing server 103 via the internet, and the testing server 103 can receive requests for specimen testing from each external facility C01, C02, and C03 via the internet.
[0032] The specimen testing system is capable of receiving and performing specimen testing requests from external facilities C01, C02, and C03 in the following order. 1. When a request for specimen testing is made from the external clients C01CA, C02CA, C02CB, and C03CA located at each external facility C01, C02, and C03, the testing server 103 prints a barcode label containing information such as the patient from whom the specimen is to be collected and the specimen testing items from the printers C01P, C02P, and C03P corresponding to the external facility C01, C02, and C03 that made the request for specimen testing. 2. Users of external clients C01CA, C02CA, C02CB, and C03CA collect samples from patients and place the collected samples into sample containers. The sample containers and barcode labels are then transported to the respective laboratories of the core hospital H01 by means such as mail. 4. In each laboratory, users of the testing clients 104C, 105C, and 106C attach barcode labels to the sample containers and read the sample test items from the barcode labels attached to the sample containers using barcode readers 104R, 105R, and 106R. They also perform the sample tests for the read sample test items. After the tests are completed, the test result data is transmitted to the testing server 103.
[0033] Furthermore, after all specimen tests requested by external clients C01CA, C02CA, C02CB, and C03CA have been completed, it is possible to view the specimen test results by accessing the test server 103 from external clients C01CA, C02CA, C02CB, and C03CA.
[0034] The configuration of the inspection server 103 will now be described. As shown in Figure 2(A), the inspection server 103 includes a control unit 103a for executing various controls in the inspection server 103, an operation unit 103b for receiving input operations from the administrator of the inspection server 103, a display unit 103c for displaying the results of input operations from the operation unit 103b and various processing results in the inspection server 103, and a storage unit 103d in which various programs and data used in the inspection server 103 are stored. In this embodiment, the storage unit 103d is a commercially available hard disk drive.
[0035] Furthermore, the inspection server 103 has a first communication unit 103e connected to the internet via a router 102, a second communication unit 103f connected to the LAN within the inspection system, and a third communication unit 103g connected to the hospital LAN. In other words, the inspection server 103 in the present invention is capable of bidirectional communication with external clients C01CA, C02CA, C02CB, and C03CA installed at each external facility C01, C02, and C03 using the first communication unit 103e, and is capable of bidirectional communication with inspection clients 104C, 105C, 106C, printers 104P, 105P, 106P, and sample collection preparation systems 104S, 105S, and 106S installed in each laboratory (first laboratory, second laboratory, and third laboratory) within the core hospital H01 using the second communication unit 103f, and is capable of bidirectional communication with internal clients 121, 122, 123, 124C, 125C, and 126C, as well as printers 131, 132, 133, 124P, 125P, and 126P installed in each examination room, sample collection room, and each ward using the third communication unit 103g.
[0036] In this embodiment, the inspection server 103 has three communication units (first communication unit 103e, second communication unit 103f, and third communication unit 103g). The first communication unit 103e is connected to external clients C01CA, C02CA, C02CB, and C03CA in a bidirectional manner, and the second communication unit 103f is connected to inspection clients 104C, 105C, and 106C, printers 104P, 105P, and 106P, and inspection sample preparation systems 104S, 105S, and 106S in a bidirectional manner. Since the third communication unit 103g is connected to the in-hospital clients 121, 122, 123, 124C, 125C, 126C and printers 131, 132, 133, 124P, 125P, 126P in a bidirectional manner, even if either the first communication unit 103e or the third communication unit 103g fails, the in-hospital clients 121, 122, 123 and the external clients C01CA, C02CA, C02CB, C03CA can continue to use the examination server 103.
[0037] In this embodiment, the inspection server 103 has three communication units (first communication unit 103e, second communication unit 103f, and third communication unit 103g). The first communication unit 103e is connected to external clients C01CA, C02CA, C02CB, and C03CA in a bidirectional manner, and the second communication unit 103f is connected to inspection clients 104C, 105C, 106C, printers 104P, 105P, 106P, and the inspection sample preparation unit. The present invention illustrates a configuration in which the third communication unit 103g is connected bidirectionally to stems 104S, 105S, and 106S, and is connected bidirectionally to in-hospital clients 121, 122, 123, 124C, 125C, 126C and printers 131, 132, 133, 124P, 125P, and 126P. However, the present invention is not limited to this configuration, and the inspection server 103 may have only one communication unit. In this case, where the inspection server 103 has only one communication unit, the security of the specimen testing system can be improved simply by implementing security measures such as a firewall for the communication unit.
[0038] Furthermore, as shown in Figure 2(B), the memory unit 103d stores a program for performing specimen tests, an in-hospital database containing test data (patient data, test request data, test result data) related to specimen tests requested from each examination room and ward within the core hospital H01, an external database containing test data (patient data, test request data, test result data) related to specimen tests requested from each external facility C01, C02, and C03, a user database containing user information that can access the testing server 103, and an access control module.
[0039] Of these, the external database is a database newly added to the storage unit 103d because, in addition to the function of performing specimen testing based on test requests from each internal client 121, 122, and 123 within the core hospital H01, the specimen testing system has been equipped with a function to perform specimen testing based on test requests from each external client C01CA, C02CA, C02CB, and C03CA located at external facilities C01, C02, and C03.
[0040] Furthermore, the access control module is a program that, when an access is made to the examination server 103 due to the addition of an external database to the storage unit 103d, determines whether the access is from an internal client 121, 122, or 123, or an external client C01CA, C02C, or C03CA, and controls whether to allow access to the internal or external database.
[0041] As shown in Figure 2(B), the in-hospital database consists of an in-hospital specimen testing information storage area that stores data for all specimen tests requested from within the core hospital H01, while the external database consists of multiple external facility specimen testing information storage areas (1st external facility specimen testing information storage area, 2nd external facility specimen testing information storage area, 3rd external facility specimen testing information storage area, etc.) that store specimen testing data for each external facility that requested the specimen tests. Each external facility specimen testing information storage area is accessible only from the external clients C01CA, C02CA, C02CB, and C03CA of the corresponding external facilities C01, C02, and C03.
[0042] In this embodiment, the storage unit 103d is configured with one hard disk drive, and an in-hospital database and an external database are provided on this hard disk drive. However, the present invention is not limited to this configuration, and the storage unit 103d may be configured with multiple hard disk drives, with the in-hospital database and the external database provided on different hard disks. In this way, even if either the hard disk drive containing the in-hospital database or the hard disk containing the external database fails, the use of the examination server 103 by either the in-hospital clients 121, 122, 123 or the external clients C01CA, C02CA, C02CB, C03CA can continue.
[0043] As shown in Figures 3(A) to 3(D), in the inspection server 103 of the present invention, when access is received from in-hospital clients 121, 122, 123 or external clients C01CA, C02CA, C02CB, C03CA (when data is received from in-hospital clients 121, 122, 123 or external clients C01CA, C02CA, C02CB, C03CA), the control unit 103a uses an access control module to identify the terminal ID from among the IP header, TCP header, terminal ID, and data to be transmitted that constitute the received data, and executes a process to determine whether the identified terminal ID contains a facility code indicating that the source of the received data is one of the external clients C01CA, C02CA, C02CB, or C03CA.
[0044] In this case, if the identified terminal ID does not include a facility code, that is, if the source of the received data is one of the in-hospital clients 121, 122, or 123, the control unit 103a allows in-hospital clients 121, 122, and 123 to access the in-hospital specimen testing information storage area (in-hospital database), while preventing in-hospital clients 121, 122, and 123 from accessing the first, second, and third external facility specimen testing information storage areas (external databases), thereby preventing the leakage of specimen testing data requested by each external facility C01, C02, and C03 into the core hospital H01 via in-hospital clients 121, 122, and 123.
[0045] On the other hand, if the identified terminal ID includes a facility code, that is, if the source of the received data is one of the external clients C01CA, C02C, or C03CA, the control unit 103a allows external clients C01CA, C02C, and C03CA to access the external facility specimen testing information storage area corresponding to the facility code among the first external facility specimen testing information storage area, the second external facility specimen testing information storage area, and the third external facility specimen testing information storage area (external database), while preventing external clients C01CA, C02C, and C03CA from accessing the in-hospital specimen testing information storage area (in-hospital database). This prevents the leakage of specimen testing data related to specimen testing requested by each in-hospital client 121, 122, and 123 to external facilities C01, C02, and C03 via external clients C01CA, C02C, and C03CA.
[0046] As shown in Figures 4(A) to 4(C), the in-hospital database (in-hospital specimen testing information storage area) of the storage unit 103d includes a patient data table for storing patient data of patients who are the subject of specimen testing, a test request data table for storing data of specimen tests requested by each in-hospital client 121, 122, and 123, and a test result data table for storing data of completed specimen tests.
[0047] The patient data table shown in Figure 4(A) is a data table that stores the 8-digit patient ID, which is pre-assigned to each patient within the core hospital H01, along with the patient's name, gender, and date of birth. The test request data table shown in Figure 4(B) is a data table that stores the date and time of receipt of the test request from each in-hospital client 121, 122, and 123 at the test server 103, the patient ID, the order number created for each test request, and the specific test items of the test request. The order number is created by adding the 4-digit numbers corresponding to the "month" and "day" from the date and time of receipt of the test request from each in-hospital client 121, 122, and 123 at the test server 103 to the beginning of the patient ID.
[0048] The test result data table shown in Figure 4(C) is a data table for storing the order number, specific numerical values and test results for each test item, and a test completion flag to determine whether all requested test items have been completed. Initially, the value of the test completion flag is set to "0" to indicate that the sample test is not yet complete, and it is set to "1" to indicate that the sample test is complete when all sample tests corresponding to the order number have been completed.
[0049] Furthermore, as mentioned above, the off-site database consists of multiple off-site facility specimen testing information storage areas, such as the first off-site facility specimen testing information storage area for storing specimen testing information requested by off-site facility C01, the second off-site facility specimen testing information storage area for storing specimen testing information requested by off-site facility C02, and the third off-site facility specimen testing information storage area for storing specimen testing information requested by off-site facility C03. Below, the off-site facility specimen testing information storage areas will be explained using the first off-site facility specimen testing information storage area as an example.
[0050] As shown in Figures 5(A) to 5(C), the first external facility specimen testing information storage area includes a patient data table for storing patient data (patient data) of patients who are the subject of specimen testing, a test request data table for storing data (test request data) of specimen tests requested by external client C01CA installed at external facility C01, and a test result data table for storing data of completed specimen tests (test result data).
[0051] The patient data table shown in Figure 5(A) is a data table that stores the 8-digit patient ID assigned to the patient at the off-site facility C01, with the facility code added to the beginning. As shown in Figures 4(A) and 5(A), the patient data table in the off-site database (in-hospital facility specimen testing information storage area) stores the patient ID in association with the patient's name, gender, and date of birth, whereas the patient data table in the first off-site facility specimen testing information storage area only stores the patient ID with the facility code. Therefore, even if the data in the patient data table in the first off-site facility specimen testing information storage area is viewed by an administrator of the testing server 103, personal information such as the patient's name, gender, and date of birth will not be leaked.
[0052] The test request data table shown in Figure 5(B) is a data table that stores the date and time the test request was received by the test server 103 from the external client C01CA located at the external facility C01, the patient ID with the facility code, the order number created for each test request, and the specific test items of the test request. The order number is created by adding the four-digit numbers corresponding to the "month" and "day" from the date and time the test request was received by the test server 103 from the external client C01CA to the beginning of the patient ID.
[0053] The test result data table shown in Figure 5(C) is a data table for storing the order number, specific numerical values and test results for each test item, and a test completion flag to determine whether all requested test items have been completed. Initially, the value of the test completion flag is set to "0" to indicate that the sample test is not yet complete, and it is set to "1" to indicate that the sample test is complete when all sample tests corresponding to the order number have been completed.
[0054] As shown in Figures 6(A) and 6(B), the user database stores an in-hospital user information table that stores the user ID and password assigned to each user of in-hospital clients 121, 122, and 123 within the core hospital H01, along with a terminal ID to identify each in-hospital client 121, 122, and 123, and an external user information table that stores the user ID and password assigned to each user of external clients C01CA, C02CA, C02CB, and C03CA at each external facility C01, C02, and C03, along with a terminal ID to identify each external client C01CA, C02CA, C02CB, and C03CA.
[0055] The terminal IDs stored in the in-hospital user information table include serial numbers that can identify the in-hospital clients 121, 122, and 123 used by each user, but do not include facility codes. On the other hand, as shown in Figure 6(B), the terminal IDs stored in the external user information table include serial numbers that can identify the external clients C01CA, C02CA, C02CB, and C03CA used by each user, as well as facility codes that can identify the external facilities C01, C02, and C03 where each external client C01CA, C02CA, C02CB, and C03CA is installed. Specifically, the external client C01CA installed in external facility C01 includes the facility code "C01", the external clients C02CA and C02CB installed in external facility C02 include the facility code "C02", and the external client C03CA installed in external facility C03 includes the facility code "C03".
[0056] As shown in Figure 6(C), these user IDs and passwords are public information that is individually notified to users of in-hospital clients 121, 122, and 123, and to users of external clients C01CA, C02CA, C02CB, and C03CA, respectively. In contrast, the terminal ID is confidential information that is not notified to users of in-hospital clients 121, 122, and 123, and to users of external clients C01CA, C02CA, C02CB, and C03CA.
[0057] In other words, while users of the external clients C01CA, C02CA, C02CB, and C03CA can access the testing server 103 by entering the user ID and password they are individually notified with, they cannot recognize the facility codes assigned to each external facility C01, C02, and C03. Therefore, it is difficult for them to view the results of specimen tests requested by other external facilities C01, C02, and C03.
[0058] Next, the interactions that occur when requesting specimen testing from the in-hospital clients 121, 122, and 123 in each examination room, or from the external clients C01CAA, C02A, and C03CAA of each external facility C01, C02, and C03, to the testing server 103 will be explained based on Figures 7 and 8.
[0059] First, when in-hospital clients 121, 122, 123 or external clients C01CAA, C02CA, C03CAA receive login information (user ID and password) from the user (step S101), they transmit the received login information to the inspection server 103 (step S102).
[0060] When the inspection server 103 (control unit 103a) receives login information (step S103), it identifies in-hospital user information that matches the received user ID and password (step S104). Specifically, the control unit 103a identifies a user ID and password combination that matches the received user ID and password combination from the user ID and password combinations stored as in-hospital user information shown in Figure 6(A).
[0061] If, at this point, a user ID and password combination that matches the received user ID and password combination is not found among the user ID and password combinations stored as in-hospital user information shown in Figure 6(A) (step S105; N), then the system further identifies external user information that matches the received user ID and password (step S106). Specifically, the control unit 103a identifies a user ID and password combination that matches the received user ID and password combination from the user ID and password combinations stored as external user information shown in Figure 6(B).
[0062] If, at this point, the combination of user ID and password that matches the received user ID and password is not found among the user ID and password combinations stored as external user information shown in Figure 6(B) (step S107;N), the control unit 103a sends access denied information to the in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA that sent login information to the examination server 103, indicating that they are not permitted to access the storage unit 103d (step S108).
[0063] If in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA receive access denied information (step S109), they will notify the user that access to the storage unit 103d was denied (access denied notification) by, for example, displaying it on an attached display device or outputting sound from a speaker (step S110).
[0064] On the other hand, if the control unit 103a finds a user ID and password combination that matches the received user ID and password combination among the user ID and password combinations stored as in-hospital user information shown in Figure 6(A) (step S105; Y), or if the user ID and password combination that matches the received user ID and password combination is among the user ID and password combinations stored as out-of-hospital user information shown in Figure 6(B) (step S107; Y), it further identifies the terminal ID stored in association with the received user ID and password from the in-hospital user information shown in Figure 6(A) or the out-of-hospital user information shown in Figure 6(B) (step S111).
[0065] Then, access permission information, including the identified terminal ID, is sent to the in-hospital clients 121, 122, 123 or the external clients C01CAA, C02A, C03CAA that have sent login information to the inspection server 103, granting them permission to access the storage unit 103d (step S112).
[0066] When in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA receive access permission information (step S113), they temporarily store the terminal ID included in the access permission information in a specific memory area of RAM (not shown) (step S114), and also notify the user that access to the memory unit 103d has been permitted (access permission notification) by, for example, displaying it on an attached display device or outputting sound from a speaker (step S115).
[0067] After the access permission notification is issued, in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA accept input from the user for the specimen test items and patient ID (step S116). At this time, the patient ID accepted from in-hospital clients 121, 122, 123 is an 8-digit ID that has been previously assigned to the patient at core hospital H01 (an ID stored in the electronic medical record server 120 in association with each patient's name, gender, date of birth, medical history, etc.), while the patient ID accepted from external clients C01CAA, C02A, C03CAA is an ID that external clients C01CAA, C02A, C03CAA have independently assigned to the patient.
[0068] After receiving the patient ID and test items, the in-hospital clients 121, 122, 123 or the external clients C01CAA, C02A, C03CAA transmit the test request information, including the patient ID, test items, and terminal ID received, to the test server 103 (step S117).
[0069] When the control unit 103a receives the test request information (step S118), it determines whether the terminal ID included in the test request information includes the facility code (step S119). If the terminal ID includes the facility code (step S119; Y), the patient ID included in the received test request information is added to the patient data table of the off-site facility specimen test information storage area indicated by the facility code (see Figure 5(A)) as patient data in the off-site database (step S120).
[0070] Furthermore, the control unit 103a generates an order number from the patient ID included in the received test request information and the date and time the test request information was received (step S121), and adds the test items, patient ID, order number, and date and time of receipt included in the received test request information as test request data in the external database to the test request data table in the external facility specimen test information storage area indicated by the facility code (see Figure 5(B)) (step S122).
[0071] On the other hand, if the terminal ID does not include a facility code (step S119;N), the control unit 103a identifies patient data with a patient ID that matches the patient ID included in the received examination request information from the patient data table in the hospital database (see Figure 4(A)) (step S123). At this time, if there is no patient data with a patient ID that matches the patient ID included in the received examination request information in the patient data table in the hospital database (step S124;N), the control unit 103a identifies the patient name, gender, date of birth, etc. stored in the electronic medical record server 120 from the patient ID included in the received examination request information, associates these identified patient name, gender, date of birth, etc. with the patient ID, and adds them to the patient data table in the hospital database (see Figure 4(A)) as patient data (step S125).
[0072] If there is patient data in the hospital database's patient data table that has a patient ID that matches the patient ID included in the received test request information (step S124; Y), or after the processing in step S125, the control unit 103a generates an order number from the patient ID included in the received test request information and the date and time the test request information was received (step S127), and adds the test items, patient ID, order number, and date and time of receipt included in the received test request information to the test request data table shown in Figure 4(B) as test request data in the hospital database (step S128).
[0073] After step S122 or step S128 is executed, the control unit 103a identifies the printer to be printed from the serial number in the terminal ID included in the received inspection request information, and sends barcode label print instruction information including the inspection items, patient ID, and order number to the printer to be printed (step S129). It also identifies the in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA that sent the inspection request information from the serial number in the terminal ID included in the received inspection request information, and sends inspection request completion information including the order number to the identified in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA (step S132).
[0074] When a printer receives barcode label printing instruction information (either printers 131, 132, or 133 installed in each examination room of the core hospital H01, or printers C01P, C02P, or C03P installed in each of the external facilities C01, C02, or C03), it prints a barcode label based on the examination items, patient ID, and order number included in the barcode label printing instruction information (step S130) (step S131).
[0075] Furthermore, when in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA receive information on the completion of a test request (step S133), they store the order number included in the received information (step S134).
[0076] Furthermore, when barcode labels are printed using printers 131, 132, and 133 installed in each examination room of the core hospital H01, these barcode labels are affixed to the specimen containers used to hold the specimens to be tested in each examination room. After the barcode labels are affixed, the specimen containers are placed in the specimen collection room, and then transported to one of the testing rooms (Testing Room 1 to Testing Room 3).
[0077] Furthermore, when a barcode label is printed using printer C01P, C02P, or C03P installed at each of the external facilities C01, C02, or C03, the barcode label is affixed to the sample container for the sample to be tested at each external facility C01, C02, or C03. After the sample is placed inside the sample container with the barcode label attached, it is transported to one of the laboratories (laboratory 1 to laboratory 3) within the core hospital H01.
[0078] Next, we will explain, based on Figure 9, the process by which the sample test results are stored in the test server 103 after each test laboratory has performed the test.
[0079] First, the test clients 104C, 105C, and 106C installed in each laboratory read the barcode labels attached to the sample containers by operating the barcode readers 104R, 105R, and 106R by the user (step S201), and identify the test items, patient ID, and order number from the read barcode labels (step S202). Then, they perform the sample test based on the identified test items (step S203), input the test results of the performed sample test (step S204), and transmit test completion information, including the test results, patient ID, and order number, to the test server 103 (step S205).
[0080] When the control unit 103a receives inspection completion information (step S206), it determines whether the terminal ID included in the inspection completion information contains the facility code (step S207). If the terminal ID contains the facility code (step S207; Y), it associates the inspection result and order number included in the received inspection completion information and adds it to the inspection result data table shown in Figure 5(C) as inspection result data in the external database (step S208). If the terminal ID included in the inspection completion information does not contain the facility code (step S207; N), it associates the inspection result and order number included in the received inspection completion information and adds it to the inspection result data table shown in Figure 4(C) as inspection result data in the internal database (step S209).
[0081] Then, after processing in step S208 or step S209, a test completion flag is set as test result data, associated with the order number added to the test result data table, to indicate that the sample test has been completed (step S210).
[0082] Next, the interactions that occur when the in-hospital clients 121, 122, and 123 in each examination room, or the external clients C01CAA, C02A, and C03CAA of each external facility C01, C02, and C03, receive test completion notification information from the test server 103 indicating that the specimen test has been completed, will be explained based on Figures 10 and 11.
[0083] First, when in-hospital clients 121, 122, 123 or external clients C01CAA, C02CA, C03CAA receive login information (user ID and password) from the user (step S301), they transmit the received login information to the inspection server 103 (step S302).
[0084] When the inspection server 103 (control unit 103a) receives login information (step S303), it identifies in-hospital user information that matches the received user ID and password (step S304). Specifically, the control unit 103a identifies a user ID and password combination that matches the received user ID and password combination from the user ID and password combinations stored as in-hospital user information shown in Figure 6(A).
[0085] If, at this point, a user ID and password combination that matches the received user ID and password combination is not found among the user ID and password combinations stored as in-hospital user information shown in Figure 6(A) (step S305; N), then the system further identifies external user information that matches the received user ID and password (step S306). Specifically, the control unit 103a identifies a user ID and password combination that matches the received user ID and password combination from the user ID and password combinations stored as external user information shown in Figure 6(B).
[0086] If, at this point, the combination of user ID and password that matches the received user ID and password is not found among the user ID and password combinations stored as external user information shown in Figure 6(B) (step S307;N), the control unit 103a sends access denied information to the internal clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA that sent login information to the examination server 103, indicating that they are not permitted to access the storage unit 103d (step S308).
[0087] If in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA receive access denied information (step S309), they will notify the user that access to the storage unit 103d was denied (access denied notification) by, for example, displaying it on an attached display device or outputting sound from a speaker (step S310).
[0088] On the other hand, if the control unit 103a finds a user ID and password combination that matches the received user ID and password combination among the user ID and password combinations stored as in-hospital user information shown in Figure 6(A) (step S305; Y), or if the user ID and password combination that matches the received user ID and password combination is among the user ID and password combinations stored as out-of-hospital user information shown in Figure 6(B) (step S307; Y), it further identifies the terminal ID stored in association with the received user ID and password from the in-hospital user information shown in Figure 6(A) or the out-of-hospital user information shown in Figure 6(B) (step S311).
[0089] Then, access permission information, including the identified terminal ID, is sent to the in-hospital clients 121, 122, 123 or the external clients C01CAA, C02A, C03CAA that have sent login information to the inspection server 103, granting them permission to access the storage unit 103d (step S312).
[0090] When in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA receive access permission information (step S313), they temporarily store the terminal ID included in the access permission information in a specific memory area of RAM (not shown) (step S314), and notify the user that access to the memory unit 103d has been permitted (access permission notification) by, for example, displaying it on an attached display device or outputting sound from a speaker (step S315).
[0091] Here, in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA determine whether or not they have stored the order number (whether or not they stored the order number in step S134 of Figure 8) (step S316). If they do not have stored the order number (step S316; N), they perform processing according to other inputs (step S317). If they do have stored the order number (step S316; Y), they send inspection result inquiry information including the terminal ID and order number to the inspection server 103 (step S318).
[0092] When the control unit 103a receives a test result inquiry information (step S323), it determines whether the terminal ID included in the received test result inquiry information includes a facility code (step S324). If the terminal ID included in the received test result inquiry information includes a facility code (step S324; Y), it identifies the test result data with the matching order number from the test result data stored in the test result data table of the off-site facility specimen test information storage area indicated by the facility code (see Figure 5(C)) (step S325). If the terminal ID included in the received test result inquiry information does not include a facility code (step S324; N), it identifies the test result data with the matching order number from the test result data stored in the test result data table of the in-hospital database (see Figure 4(C)) (step S326).
[0093] After step S325 or step S326 is executed, the control unit 103a determines whether the test completion flag is set as the identified test result data, that is, whether all requested sample tests have been completed (step 327). If the test completion flag is not set as the identified test result data (step S327; N), it sends incomplete test information to the in-hospital clients 121, 122, 123 or the external clients C01CAA, C02A, C03CAA that sent the test result inquiry information to the test server 103, indicating that all requested sample tests have not been completed (step S328). If the test completion flag is set as the identified test result data (step S327; Y), it sends complete test information to the in-hospital clients 121, 122, 123 or the external clients C01CAA, C02A, C03CAA that sent the test result inquiry information to the test server 103, indicating that all requested sample tests have been completed (step S329).
[0094] When in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA receive information that an examination is incomplete (step S319), they set the examination result inquiry waiting timer according to a predetermined period (step S320). Then, after performing a subtraction process on the examination result inquiry waiting timer (a process that subtracts 1 from the value of the examination result inquiry waiting timer) (step S321), they determine whether the examination result inquiry waiting timer has timed out or not (step S322). If the examination result inquiry waiting timer has not timed out (step S322; N), the processes of steps S321 and S322 are repeated.
[0095] Furthermore, if the timer for waiting for the test result inquiry expires (step S322; Y), the S318no process is executed again to send the test result inquiry information to the test server 103. In other words, in this embodiment, if the in-hospital clients 121, 122, 123 or the external clients C01CAA, C02A, C03CAA log back into the test server 103 after requesting a specimen test from the test server 103, they will inquire with the test server 103 at the time of the login and at predetermined intervals whether the requested specimen test has been completed.
[0096] Furthermore, if in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA receive information about incomplete testing (step S330), they clear the memory of the order number corresponding to the received test completion information (step S331), and notify that all requested specimen tests have been completed (specimen test completion notification), for example, by displaying it on an attached display device or outputting sound from a speaker (step S332).
[0097] Next, the interactions between the in-hospital clients 121, 122, and 123 in each examination room, or the external clients C01CAA, C02A, and C03CAA of each external facility C01, C02, and C03, when they receive test results from the testing server 103 after the completion of specimen testing, will be explained based on Figures 12 and 13.
[0098] First, when in-hospital clients 121, 122, 123 or external clients C01CAA, C02CA, C03CAA receive login information (user ID and password) from the user (step S401), they transmit the received login information to the inspection server 103 (step S402).
[0099] When the inspection server 103 (control unit 103a) receives login information (step S403), it identifies in-hospital user information that matches the received user ID and password (step S404). Specifically, the control unit 103a identifies a user ID and password combination that matches the received user ID and password combination from the user ID and password combinations stored as in-hospital user information shown in Figure 6(A).
[0100] If, at this point, a user ID and password combination that matches the received user ID and password combination is not found among the user ID and password combinations stored as in-hospital user information shown in Figure 6(A) (step S405; N), then the system further identifies an external user information that matches the received user ID and password (step S406). Specifically, the control unit 103a identifies a user ID and password combination that matches the received user ID and password combination from the user ID and password combinations stored as external user information shown in Figure 6(B).
[0101] If, at this point, the combination of user ID and password that matches the received user ID and password is not found among the user ID and password combinations stored as external user information shown in Figure 6(B) (step S407;N), the control unit 103a sends access denied information to the internal clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA that sent login information to the examination server 103, indicating that they are not permitted to access the storage unit 103d (step S408).
[0102] If in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA receive access denied information (step S409), they will notify the user that access to the storage unit 103d was denied (access denied notification) by, for example, displaying it on an attached display device or outputting sound from a speaker (step S410).
[0103] On the other hand, if the control unit 103a finds a user ID and password combination that matches the received user ID and password combination among the user ID and password combinations stored as in-hospital user information shown in Figure 6(A) (step S405; Y), or if the user ID and password combination that matches the received user ID and password combination is among the user ID and password combinations stored as out-of-hospital user information shown in Figure 6(B) (step S407; Y), it further identifies the terminal ID stored in association with the received user ID and password from the in-hospital user information shown in Figure 6(A) or the out-of-hospital user information shown in Figure 6(B) (step S411).
[0104] Then, access permission information, including the identified terminal ID, is sent to the in-hospital clients 121, 122, 123 or the external clients C01CAA, C02A, C03CAA that have sent login information to the inspection server 103, granting them permission to access the storage unit 103d (step S412).
[0105] When in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA receive access permission information (step S413), they temporarily store the terminal ID included in the access permission information in a specific memory area of RAM (not shown) (step S414), and notify that access to the memory unit 103d has been permitted (access permission notification) by, for example, displaying it on an attached display device or outputting sound from a speaker (step S415). They also send inspection result request information including the terminal ID and order number to the inspection server 103 (step S416).
[0106] When the control unit 103a receives a test result request information (step S417), it determines whether the terminal ID included in the received test result request information includes a facility code (step S418). If the terminal ID included in the received test result request information includes a facility code (step S418; Y), it identifies the test result data with the matching order number from the test result data stored in the test result data table (see Figure 5(C)) of the off-site facility specimen test information storage area indicated by the facility code (step S419). If the terminal ID included in the received test result request information does not include a facility code (step S418; N), it identifies the test result data with the matching order number from the test result data stored in the test result data table (see Figure 4(C)) of the in-hospital database (step S420).
[0107] After step S419 or step S420 is performed, the control unit 103a sends data for each test item stored as identified test result data to the in-hospital clients 121, 122, 123 or the out-of-hospital clients C01CAA, C02A, C03CAA that sent the test result request information to the test server 103 (step S422).
[0108] Then, when in-hospital clients 121, 122, 123 or external clients C01CAA, C02A, C03CAA receive data for each test item (step S423), they display the test results based on the data for each test item, for example, on the attached display device (step S424).
[0109] As described above, the specimen testing system in the present invention includes in-hospital clients 121, 122, and 123 located within the core hospital H01 that can access the testing server 103, and specimen testing is performed within the core hospital H01 based on testing requests from these in-hospital clients 121, 122, and 123. Furthermore, the testing server 103 is also accessible from external clients C01CA, C02CA, C02CB, and C03CA located at each external facility C01, C02, and C03, and specimen testing is also performed within the core hospital H01 based on testing requests from these external clients C01CA, C02CA, C02CB, and C03CA.
[0110] Furthermore, the inspection server 103 can determine whether the access to the inspection server 103 is from in-hospital clients 121, 122, 123 or from external clients C01CA, C02CA, C02CB, C03CA by using the access control module stored in the memory unit 103d.
[0111] In this case, if access to the testing server 103 is from in-hospital clients 121, 122, and 123, access to the in-hospital database is enabled while access to the external database is disabled. If access to the testing server 103 is from external clients C01CA, C02CA, C02CB, and C03CA, access to the external database is enabled while access to the in-hospital database is disabled. This prevents information on specimen tests requested by core hospital H01 from being leaked to external facilities C01, C02, and C03, and prevents information on specimen tests requested by external facilities C01, C02, and C03 from being leaked to core hospital H01, thereby improving the confidentiality of the specimen testing system.
[0112] Furthermore, the specimen testing system of the present invention has a new external database in the storage unit 103d that is different from the internal database, in order to receive test requests from external facilities C01, C02, and C03, and an access control module has been newly installed in the storage unit 103d. In other words, the specimen testing system of the present invention can be configured by reusing the existing test server 103 and internal clients 121, 122, and 123 that have been set up within the core hospital H01 as a system that performs specimen testing based on test requests from within the core hospital H01, so the implementation cost can be reduced compared to newly introducing a system that can also perform specimen testing based on test requests from external facilities C01, C02, and C03.
[0113] Furthermore, as shown in Figure 6, in-hospital clients 121, 122, 123 and external clients C01CA, C02CA, C02CB, C03CA can send inspection request information, inspection result inquiry information, and inspection result request information to the inspection server 103 as access request information according to the present invention. This inspection result inquiry information and inspection result request information includes a terminal ID that can identify whether the sender is an in-hospital client 121, 122, 123 or an external client C01CA, C02CA, C02CB, C03CA.
[0114] Here, as shown in Figure 6, the terminal IDs included in the test result inquiry information and test result request information transmitted from in-hospital clients 121, 122, and 123 to the test server 103 consist of serial numbers that can identify these in-hospital clients 121, 122, and 123, while the terminal IDs included in the test result inquiry information and test result request information transmitted from external clients C01CA, C02CA, C02CB, and C03CA to the test server 103 consist of serial numbers that can identify these external clients C01CA, C02CA, C02CB, and C03CA, and facility codes that can identify the external facilities C01, C02, and C03 where each external client C01CA, C02CA, C02CB, and C03CA is installed.
[0115] More precisely, the terminal IDs included in the test result inquiry information and test result request information transmitted from the external clients C01CA, C02CA, C02CB, and C03CA to the test server 103 are information in which a facility code that identifies the external facility C01, C02, and C03 where each external client C01CA, C02CA, C02CB, and C03CA is installed is added to the beginning of a serial number that identifies the external clients C01CA, C02CA, C02CB, and C03CA. Therefore, in the specimen testing system of the present invention, it is possible to reuse the terminal IDs of the internal clients 121, 122, and 123 that are provided as part of the specimen testing system provided in the existing core hospital H01, thereby reducing the burden of changing the existing specimen testing system, and thus further reducing the introduction cost of the specimen testing system of the present invention.
[0116] Furthermore, the control unit 103a of the inspection server 103 can determine whether or not the received inspection result inquiry information or inspection result request information contains a facility code. If the received inspection result inquiry information or inspection result request information does not contain a facility code, the special access control in this invention allows access to the in-hospital database but prevents access to the external database. If the received inspection result inquiry information or inspection result request information contains a facility code, the specific access control in this invention allows access to the external database but prevents access to the in-hospital database.
[0117] In other words, in the specimen testing system of the present invention, when the control unit 103a receives test result inquiry information or test result request information, it can enable access to the in-hospital database but disable access to the external database, or enable access to the external database but disable access to the in-hospital database, depending on the presence or absence of a facility code. This significantly reduces the processing load on the control unit 103a and prevents delays caused by access to the testing server 103 from in-hospital clients 121, 122, 123 and external clients C01CA, C02CA, C02CB, C03CA.
[0118] Furthermore, as shown in Figure 6(B), the terminal IDs of the external clients C01CA, C02CA, C02CB, and C03CA include the facility code "C01" for external client C01CA installed at external facility C01, the facility code "C02" for external client C02CA and external client C02CB installed at external facility C02, and the facility code "C03" for external client C03CA installed at external facility C03. In other words, when the control unit 103a receives inspection request information, inspection result inquiry information, or inspection result request information as access request information, it can identify the facility code and determine whether the access request information was transmitted from external facility C01, C02, or C03.
[0119] Furthermore, when the control unit 103a receives inspection request information, inspection result inquiry information, or inspection result request information as access request information, it allows access only to the off-site facility specimen testing information storage area indicated by the facility code corresponding to the facility code, and disables access to the off-site facility specimen testing information storage area indicated by other facility codes. This prevents, for example, information on specimen tests requested at off-site facility C01 from being leaked to off-site facility C02 or off-site facility C03, information on specimen tests requested at off-site facility C02 from being leaked to off-site facility C01 or off-site facility C03, and information on specimen tests requested at off-site facility C03 from being leaked to off-site facility C01 or off-site facility C02, thereby further improving the control of the specimen testing system.
[0120] Although embodiments of the present invention have been described above with reference to the drawings, the specific configurations are not limited to these embodiments, and any changes or additions that do not depart from the spirit of the present invention are also included.
[0121] For example, in the above embodiment, a configuration was illustrated in which requests for specimen testing could be made to the testing server 103 from in-hospital clients 121, 122, and 123 installed in each examination room within the core hospital H01. However, the present invention is not limited to this, and requests for specimen testing may also be made to the testing server 103 from in-hospital clients 125C and 126C installed in each ward. In this way, patients admitted to each ward can request specimen testing from the testing server 103 from within their respective wards without having to go to an examination room, thereby reducing the burden on patients subject to specimen testing. Furthermore, when the testing server 103 receives a request for specimen testing from in-hospital clients 125C and 126C installed in each ward, a barcode label may be printed from printers 125P and 126P set up in each ward, and the barcode labels printed from these printers 125P and 126P can be affixed to specimen containers by the users of the in-hospital clients 125C and 126C.
[0122] Furthermore, within the core hospital H01, an example was given in which a user of the in-hospital client 124C reads the specimen test items from the barcode label attached to the specimen container using a barcode reader 124R in the specimen collection room and collects the specimen corresponding to the read specimen test items. However, the present invention is not limited to this, and users of the in-hospital clients 125C and 126C installed in each ward may read the specimen test items from the barcode label attached to the specimen container using barcode readers 125R and 126R and collect the specimen corresponding to the read specimen test items. In this way, patients admitted to each ward can have specimens collected within their respective wards without having to go to the specimen collection room, thereby reducing the burden on patients subject to specimen testing.
[0123] Furthermore, while the above embodiment illustrates a configuration in which users of the inspection clients 104C, 105C, and 106C read the sample test items from the barcode labels attached to the sample containers using the barcode readers 104R, 105R, and 106R, and perform sample testing on the read sample test items, the present invention is not limited thereto. The inspection clients 104C, 105C, and 106C may transmit information including the sample test items read by the barcode readers 104R, 105R, and 106R to the inspection server 103, and the inspection server (control unit 103a) may perform sample testing by operating various testing equipment installed in each laboratory using a sample testing program based on the receipt of this information.
[0124] Furthermore, while the above embodiment illustrates a configuration in which users of the inspection clients 104C, 105C, and 106C perform sample testing and store the test results in the inspection server 103 through operation of the inspection clients 104C, 105C, and 106C, the present invention is not limited thereto. For example, each laboratory may be equipped with a sample testing device having the functions of a barcode reader 104R, 105R, and 106R, and the sample testing device may be connected to the inspection server 103 in a communicative manner. The sample testing device may then automatically read barcode labels and automatically transmit the results of the sample testing to the inspection server 103 based on the information identified from the barcode labels.
[0125] Furthermore, while the above embodiment illustrates a configuration in which users of each in-hospital client 121, 122, and 123 affix barcode labels printed from printers 131, 132, and 133 to specimen containers, the present invention is not limited thereto. For example, if the number of patients receiving specimen tests and the number of test items are known in advance, the barcode labels printed by printers 104P, 105P, and 106P installed in each laboratory may be automatically affixed in advance by the specimen preparation systems 104S, 105S, and 106S.
[0126] Furthermore, in the above embodiment, after requesting a specimen test from in-hospital clients 121, 122, 123 and external clients C01CA, C02CA, C02CB, C03CA to the test server 103, the in-hospital clients 121, 122, 123 and external clients C01CA, C02CA, C02CB, C03CA can notify the test server 103 of the completion of the specimen test by receiving test completion information. However, the present invention is not limited to this, and if a barcode label attached to a specimen container is read by a barcode reader 104R, 105R, 106R in any of the laboratories, the test server 103 can notify the laboratory that the specimen container has been transported (transportation has been completed) by receiving barcode label reading completion information from the in-hospital clients 121, 122, 123 and external clients C01CA, C02CA, C02CB, C03CA indicating that the barcode label on the specimen container has been read.
[0127] Furthermore, while the above embodiment illustrates a configuration in which the in-hospital clients 121, 122, 123, 124C, 125C, 126C, the testing clients 104C, 105C, 106C, and the external clients C01CA, C02CA, C02CB, C03CA are commercially available personal computers, the present invention is not limited thereto. These in-hospital clients 121, 122, 123, 124C, 125C, 126C, the testing clients 104C, 105C, 106C, and the external clients C01CA, C02CA, C02CB, C03CA may be dedicated clients (dedicated terminals) built specifically for the specimen testing system of the present invention.
[0128] Furthermore, while the above embodiment illustrates a configuration in which the testing server 103 is installed within the core hospital H01 as part of the specimen testing system, the present invention is not limited thereto, and the testing server 103 may be installed outside the core hospital H01.
[0129] Furthermore, although the above embodiment illustrates a configuration in which the electronic medical record server 120 and the laboratory server 103 are provided as separate server computers within the core hospital H01, the present invention is not limited thereto. A server computer having the functions of both the electronic medical record server 120 and the laboratory server 103 may be provided, and this server computer may be configured as part of the electronic medical record system and the specimen testing system.
[0130] Furthermore, in the above embodiment, the control unit 103a enables in-hospital clients 121, 122, and 123 to access the in-hospital specimen testing information storage area, while preventing in-hospital clients 121, 122, and 123 from accessing any of the first, second, or third external facility specimen testing information storage area, or enables external clients C01CA, C02CA, C02CB, and C03CA to access any of the first, second, or third external facility specimen testing information storage area, while preventing external clients C01CA, C02CA, C02CB, and C03CA from accessing the in-hospital specimen testing information storage area. In this way, even when a large number of client computers transmit test request information, test result inquiry information, and test result request information to the test server 103, the specimen testing system can be operated while suppressing a decrease in communication speed. However, the present invention is not limited to this, and in cases where the number of client computers transmitting test request information, test result inquiry information, and test result request information to the test server 103 is small, the system determines whether the access is from an external facility C01, C02, or C03 based on the user ID and password used during login, and then transmits the information to the in-hospital specimen testing information storage area via in-hospital clients 121, 122, and 123. Access to the first external facility specimen testing information storage area, the second external facility specimen testing information storage area, and the third external facility specimen testing information storage area may be made available to in-hospital clients 121, 122, and 123, while access to the in-hospital specimen testing information storage area may be made available to external clients C01CA, C02CA, C02CB, and C03CA, while access to the in-hospital specimen testing information storage area may be made available to external clients C01CA, C02CA, C02CB, and C03CA.
[0131] Furthermore, in the above embodiment, when accessing the testing server 103 from in-hospital clients 121, 122, 123 or external clients C01CA, C02CA, C02CB, C03CA (sending testing request information, testing result inquiry information, and testing result request information), it is possible to determine whether the access is from in-hospital clients 121, 122, 123 or external clients C01CA, C02CA, C02CB, C03CA by first sending a user ID and password to the sample server 103. However, the present invention is not limited to this, and it is not necessary to send a user ID and password to the sample server 103 when accessing the testing server 103 from in-hospital clients 121, 122, 123 or external clients C01CA, C02CA, C02CB, C03CA. In this case, the facility code can be stored in the memory of the external clients C01CA, C02CA, C02CB, and C03CA in advance, allowing the control unit 103a to identify the presence or absence of the facility code from the test request information, test result inquiry information, and test result request information. [Explanation of symbols]
[0132] 103 Inspection Server 103a Control Unit 103d Storage section 121, 122 In-hospital clients 123 In-hospital clients 124C In-hospital client 125C In-hospital client 126C In-hospital client C01 Off-site facilities C01CA External Client C02 Off-site facilities C02CA External Clients C02CA External Clients C03 Off-site facilities C03CA External Client H01 Core Hospital
Claims
[Claim 1] A testing server computer located within a core medical facility that has a specimen testing facility capable of performing specimen testing, A special information terminal is provided within the aforementioned core medical facility and is connected to the aforementioned testing server computer in a manner that allows access to it. Equipped with, The aforementioned testing server computer has an internal testing request acceptance function for receiving requests for specimen testing from the aforementioned special information terminal, and is an already operational specimen testing system, A medical facility smaller than the aforementioned core medical facility and not having the aforementioned specimen testing facility is located within a non-core medical facility, and further comprises a specific information terminal connected to the aforementioned testing server computer in a manner that allows access to it. The aforementioned test server computer is: It has a storage means capable of storing information related to specimen testing, A new program for accepting external test requests is installed to provide an external test request acceptance function that accepts requests for specimen testing from the aforementioned specific information terminal. The system further includes access control means that, when the special information terminal accesses the inspection server computer, allows access only to information related to specimen testing requested by the core medical facility, The special information terminal and the specific information terminal are capable of transmitting access request information to request access to information related to specimen testing. The access control means is capable of determining whether the source of the access request information is the special information terminal or the specific information terminal, based on the terminal identification information contained in the received access request information. The aforementioned terminal identification information is in a format in which the information format of the terminal identification information used in the already operational specimen testing system is supplemented with the information assigned to the non-core medical facility. A specimen testing system characterized by the following features.
Citation Information
Patent Citations
Medical image communication system
JP2000067136A
Medical examination reservation network system, relay device used for it, and medical examination schedule management method
JP2008234381A
Measurement result managing method, system, and apparatus
JP2009037497A
Inspection data management device and method, and medical network system
JP2009176173A
Advertisement distribution device and method, and medical network system
JP2009205457A