Inspection data processing program and inspection data processing system

Abstract

We provide a test data processing program and a test data processing system that enable appropriate billing of patients for medical expenses related to the tests performed. [Solution] The control unit of the examination data processing system acquires examination data of examinations performed on patients (S1). The control unit identifies the patient who was examined using the acquired examination data (S2). The control unit stores the acquired examination data in a database, associating it with the patient who was examined (S3). Based on the acquired examination data, the control unit generates examination implementation information that can be used to bill the patient for medical expenses for the examinations that have been performed (S9). The control unit outputs the examination implementation information, associating it with the patient who was examined, to an electronic medical record system that records the patient's medical information (S10).

Description

Technical Field

[0001] The present disclosure relates to a test data processing program for processing test data, which is data of test results for patients, and a test data processing system.

Background Art

[0002] Various techniques for appropriately processing test data obtained from patients have been proposed. For example, the medical information management system described in Patent Document 1 stores the test data displayed on the electronic medical record screen and determines whether to bill the medical expenses for the test items corresponding to the stored test data. Further, the medical information management system aims to facilitate the understanding of the medical expense billing process by highlighting and displaying the test items for which the medical expenses are not to be billed on the electronic medical record screen.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] As described in Patent Document 1, if the same system can handle not only the storage of test data and the display of requested test data, but also the accounting processing for patients, it is possible to improve the efficiency of medical expense billing based on the stored test data. However, in actual medical settings, the test data processing system (sometimes called a "filing system") that performs the storage and display of test data and the medical expense billing system that performs the medical expense billing process are often different. For example, an electronic medical record system that records the patient's clinical information may be set up separately from the test data processing system, and the electronic medical record system may perform the medical expense billing process (i.e., the electronic medical record system may function as the medical expense billing system). In addition, a medical expense billing system set up separately from the test data processing system and the electronic medical record system may perform the medical expense billing process based on the information provided by the electronic medical record system. In this case, medical professionals must manually input the information necessary to bill the patient for the medical expenses related to the tests performed into the electronic medical record system. As a result, it is difficult to reduce the workload of medical professionals, and there have been many cases where the medical expenses that should have been billed were not properly billed to the patient. Therefore, there is a need for technology that can appropriately bill patients for the medical expenses incurred for the tests performed.

[0005] A typical purpose of this disclosure is to provide a test data processing program and a test data processing system that can appropriately bill patients for medical expenses related to the tests performed. [Means for solving the problem]

[0006] A typical embodiment of the present disclosure provides an examination data processing program which is executed by an examination data processing system that processes examination data which is data of examination results for a patient, wherein the examination data processing program is executed by a controller of the examination data processing system, causing the examination data processing system to perform the following processes: acquiring examination data of examinations performed on a patient; identifying the patient who was examined using the acquired examination data; storing the acquired examination data in a database in association with the patient who was examined; generating examination implementation information that can be used to bill the patient for medical expenses for the examinations that have been performed, based on the acquired examination data; and outputting the examination implementation information in association with the patient who was examined to an electronic medical record system that records the patient's clinical information.

[0007] A typical embodiment of the present disclosure provides a test data processing system for processing test data, which is data of test results for a patient. The control unit of the test data processing system performs the following processes: acquiring test data of tests performed on a patient; identifying the patient who was tested using the acquired test data; storing the acquired test data in a database in association with the patient who was tested; generating test implementation information based on the acquired test data that can be used to bill the patient for medical expenses for the tests that have been performed; and outputting the test implementation information in association with the patient who was tested to an electronic medical record system that records the patient's clinical information.

[0008] According to the test data processing program and test data processing system described herein, it becomes easier to appropriately bill patients for medical expenses related to the tests performed. [Brief explanation of the drawing]

[0009] [Figure 1] This is a block diagram showing the schematic configuration of the medical information processing system 1 of this embodiment. [Figure 2] This is a flowchart of the inspection data processing performed by the inspection data processing system 10 of the first embodiment. [Figure 3] This is a flowchart of the inspection data processing performed by the inspection data processing system 10 of the second embodiment. [Figure 4] This is a flowchart of the inspection data processing performed by the inspection data processing system 10 of the third embodiment. [Modes for carrying out the invention]

[0010] <Overview> The laboratory data processing system processes laboratory data, which is data representing the results of examinations performed on patients. The laboratory data processing program is executed by the system's controller. The control unit of the laboratory data processing system acquires laboratory data for examinations performed on patients. The control unit identifies the patients who were examined based on the acquired laboratory data. The control unit stores the acquired laboratory data in a database, associating it with the patients who were examined. Based on the acquired laboratory data (e.g., laboratory data stored in the database), the control unit generates laboratory implementation information that can be used to bill the patients for medical expenses related to the completed examinations. The control unit outputs the laboratory implementation information, associating it with the patients who were examined, to the electronic medical record system that records the patients' clinical information.

[0011] According to the technology disclosed herein, the test data of performed tests is stored by the test data processing system, and test implementation information that can be used to bill patients for medical expenses for the completed tests is generated based on the test data. The generated test implementation information is automatically output from the test data processing system to the electronic medical record system, corresponding to the patient who underwent the test. Therefore, even if the test data processing system that performs processing such as saving test data and the medical expense billing system that performs medical expense billing are different, the medical expense billing system (which may also be an electronic medical record system) can automatically and appropriately bill patients for medical expenses based on the test implementation information entered into the electronic medical record system from the test data processing system. Thus, the workload of medical professionals required to input the information necessary to bill for medical expenses is appropriately reduced, and the possibility of incorrect medical expenses being billed is also reduced.

[0012] The test data includes various types of data, such as image data captured by a medical imaging device, measurement data measured by a medical information measuring device, and data on the results of tests performed by healthcare professionals (e.g., doctors or medical technologists). The test data may be input into the test data processing system from the test device (e.g., a medical imaging device or a medical information measuring device) or by healthcare professionals. Note that the test data processing system is a different system from the electronic medical record system.

[0013] The information regarding the implementation of tests only needs to be information that can be used by the electronic medical record system, or a medical billing system (such as an accounting system) connected to the electronic medical record system, to bill the patient for medical expenses. Therefore, the specific content of the information regarding the implementation of tests can be selected as appropriate. For example, the information regarding the implementation of tests may include information indicating the content of the tests performed, which can be used to calculate medical expenses. In addition, the information regarding completed medical procedures may include information such as points set according to the tests performed, which can be used to calculate medical expenses.

[0014] The test data processing system may display the results of processes such as generating test information and outputting the generated test information to the electronic medical record system on the display unit. In this case, the processing results may be displayed on the display unit according to instructions entered by healthcare professionals. Alternatively, the test data processing system may perform processes such as generating test information and outputting the generated test information to the electronic medical record system in the background without displaying the processing results on the display unit. In this case, the test information is output to the electronic medical record system appropriately without interfering with the original processes performed by the test data processing system (for example, the process of displaying saved test data on the display unit).

[0015] The test data processing system may periodically (for example, at regular intervals) determine whether there is any test data among the acquired test data for which the process of generating test implementation information (test information generation process) and the process of outputting the test implementation information to the electronic medical record system in association with the patient being tested (test information output process) have not yet been performed. If the periodic determination determines that there is test data for which the process of outputting test implementation information has not yet been performed, the test information generation process and the test information output process may be executed based on the unprocessed test data. In other words, the test information generation process and the test information output process may be executed by polling.

[0016] In this case, the inspection data processing system only needs to execute the inspection information generation process and the inspection information output process when a periodic processing timing arrives and new, unprocessed inspection data is available, making the process easy. Furthermore, if multiple unprocessed inspection data sets exist when a periodic processing timing arrives, the inspection data processing system can also execute the inspection information generation process and the inspection information output process collectively based on each of the multiple unprocessed inspection data sets. In addition, the inspection data processing system also needs to perform processes such as displaying the stored inspection data on the display unit. However, by executing the inspection information generation process and the inspection information output process by polling, unlike when the process is executed every time inspection data is acquired (i.e., when an interrupt process is performed), it is possible to suppress the stopping or delay of other processes that were already running (for example, the display process of stored inspection data on the display unit). Therefore, inspection performance information that can be used for medical expense billing is output to the electronic medical record system more appropriately.

[0017] The laboratory data processing system may, after first saving laboratory data in a database and associating it with the patient being tested, identify a patient different from the patient previously saved in the laboratory data as a patient being tested for the same test (for example, a test performed by the same testing device). In this case, the control unit of the laboratory data processing system may perform a process to generate laboratory execution information based on the previously saved laboratory data, and a process to output the generated laboratory execution information to the electronic medical record system, associating it with the previously identified patient.

[0018] If the patient being tested for a specific test (in this disclosure, a test performed by the same testing device) is changed to another patient, it is unlikely that the specific test will be performed again on the original patient. Therefore, when the patient being tested changes, test implementation information for the original patient is generated and output, ensuring that accurate test implementation information is appropriately output to the electronic medical record system.

[0019] In addition, a specific method for the inspection data processing system to recognize that the patient to be inspected for a specific inspection has been changed can be selected as appropriate. For example, the inspection data processing system may determine that the patient to be inspected for a specific inspection has been changed when the patient to be inspected is changed from the previous patient to a new patient in the inspection data processing system itself or in the inspection device that acquires inspection data. In this case, information for identifying the new patient to be inspected may be input by medical staff into the inspection data processing system or the inspection device. Also, information for identifying the new patient to be inspected may be input by newly reading an identifier for identifying the patient. Further, after the inspection data processing system associates inspection data with the patient to be inspected and stores it in the database, when the inspection data processing system newly acquires specific inspection data that has been executed for a patient different from the patient to be inspected for the previously stored inspection data, the inspection data processing system may determine that the patient to be inspected for the specific inspection has been changed.

[0020] After the inspection data processing system associates inspection data with the patient to be inspected and stores it in the database, the state of the patient to be inspected for the stored inspection data may be different from the state during the execution of the same inspection. In this case, the control unit of the inspection data processing system may execute a process of generating inspection implementation information based on the stored inspection data and a process of outputting the generated inspection implementation information to the electronic medical record system in association with the patient to be inspected.

[0021] For example, if a patient who has undergone one test is then subjected to another test, the likelihood of another similar test being performed on the same patient is low. Similarly, if a patient who has undergone a test changes their status to one such as being under examination or awaiting examination, the likelihood of another similar test being performed on the same patient is low. Furthermore, if billing is initiated for a patient who has undergone a test, the likelihood of another similar test being performed on the same patient is low. In summary, if a patient's status changes, it can be determined that the likelihood of another similar test being performed is low. Therefore, by generating and outputting test implementation information regarding the patient when the patient's status changes from one during the execution of the same test, accurate test implementation information is more likely to be appropriately output to the electronic medical record system.

[0022] Specific methods for the inspection data processing system to grasp that the state of the patient under inspection who has undergone a certain inspection has changed can be appropriately selected. For example, when the patient under inspection of the inspection data previously saved is identified as the subject of inspection by an inspection device that performs another inspection, the inspection data processing system may determine that the state of the patient under inspection has changed. Also, when an instruction to perform medical treatment on the patient under inspection of the inspection data previously saved, or information indicating that the patient is in a state of waiting for medical treatment, etc. is input into the inspection data processing system or the like, the inspection data processing system may determine that the state of the patient under inspection has changed. The inspection data processing system may determine that the state of the patient under inspection has changed when it obtains information indicating that the patient under inspection of the inspection data previously saved has moved to a location different from the location of the inspection previously performed. In this case, for example, it may be determined whether the patient under inspection has moved based on the position information of the terminal possessed by the patient under inspection or a medical staff member who performs the inspection on the patient under inspection. Also, when an instruction to start accounting processing for the patient under inspection of the inspection data previously saved is input, the inspection data processing system may determine that the state of the patient under inspection has changed. The inspection data processing system may obtain information indicating that the state of the patient under inspection has changed from another system or device.

[0023] After the control unit of the inspection data processing system associates the inspection data with the patient under inspection and saves it in the database, when a predetermined time has elapsed, based on one or a plurality of inspection data that have been acquired and saved within the predetermined time for the patient under inspection and whose inspection types are the same, the control unit may generate inspection implementation information. The control unit may output the generated inspection implementation information to the electronic medical record system in association with the patient under inspection.

[0024] When the same type of test is performed multiple times on a patient, the multiple tests are often completed within a certain time frame. Therefore, after the test data is saved to the database, the test implementation information for the patient is generated and output after a predetermined period of time has elapsed, making it easier for accurate test implementation information to be appropriately output to the electronic medical record system.

[0025] Furthermore, the average time required for an inspection often varies depending on the type of inspection. Therefore, a predetermined time for deciding whether or not to generate and output inspection information may be set for each type of inspection (for example, for each type of inspection device). In this case, inspection information is more likely to be generated and output at an appropriate timing according to the type of inspection.

[0026] The control unit of the examination data processing system may, if the examination data obtained for the patient being examined from another examination date or other type of examination data is examination data for both eyes, store the examination data for one eye in the database in association with the patient being examined, and then generate examination implementation information and output it to the electronic medical record system when either a predetermined time has elapsed or the acquisition of examination data for both eyes of the patient being examined is completed. Alternatively, if the examination data obtained for the patient being examined from another examination date or other type of examination data is examination data for one eye, the control unit may generate examination implementation information and output it to the electronic medical record system at a time after the acquisition of examination data for one eye of the patient being examined.

[0027] If other examination data obtained for the same patient are binocular examination data, it is highly likely that subsequent examination data will also be binocular examination data. In this case, waiting a predetermined amount of time after obtaining binocular examination data, or waiting until binocular examination data has been completed, will make it easier to output more accurate examination information. Also, if other examination data obtained for the same patient are binocular examination data, it is highly likely that subsequent examination data will also be binocular examination data. In this case, generating and outputting examination information after obtaining binocular examination data will ensure that the examination information is output appropriately at an earlier stage. Therefore, it becomes easier to output more accurate examination information to the electronic medical record system.

[0028] The test data processing system may, after outputting test implementation information to the electronic medical record system in association with the patient being tested, also save new test data for similar tests performed on the same patient to the database. In this case, the control unit of the test data processing system may output a deletion instruction to the electronic medical record system for previously outputted test implementation information. The control unit may generate new test implementation information based on multiple similar test data, including the newly saved test data. The control unit may output the newly generated test implementation information to the electronic medical record system in association with the patient being tested. If a deletion instruction for test implementation information is input to the control unit of the electronic medical record system, it will delete the specified test implementation information.

[0029] In this case, even if additional test data for the same patient is newly saved (for example, if test data for the left eye for the same patient is saved after test data for the right eye has been saved), the test performance information for all the test data, including the additional data, will be appropriately entered into the electronic medical record system. Therefore, accurate test performance information will be more appropriately obtained by the electronic medical record system.

[0030] Furthermore, the electronic medical record system can delete inaccurate test implementation information at its discretion. In other words, if, after entering test implementation information, the control unit of the electronic medical record system enters new test implementation information for the same type of test associated with the same patient, it may delete the previously entered information and use the newly entered information as the patient's test implementation information. In this case as well, medical expenses will be appropriately billed to the patient based on accurate test implementation information.

[0031] Furthermore, the test data processing system may, after outputting the test implementation information to the electronic medical record system, associate it with the patient being tested, and then, if an instruction is received to delete the test data from the database that generated the outputted test implementation information, output an instruction to delete the test implementation information generated and output based on the test data to be deleted to the electronic medical record system. In this case, the possibility of the patient being billed for medical expenses related to the deleted test data is appropriately reduced.

[0032] <Embodiment> (System Configuration) Hereinafter, one typical embodiment of the present disclosure will be described with reference to the drawings. First, with reference to Figure 1, an example of the system configuration of the medical information processing system 1 in this embodiment will be described in general terms. In this embodiment, the medical information processing system 1 used in ophthalmology will be described as an example. However, at least a part of the technology exemplified in this disclosure can also be adopted in medical information processing systems used in medical departments other than ophthalmology (for example, internal medicine, surgery, orthopedics, dermatology, etc.) or in health checkup facilities, etc. The medical information processing system 1 of this embodiment includes an examination data processing system 10, a database 15, an electronic medical record system 20, an examination device 30 (30A, 30B), and a user terminal 40 (40A, 40B). Within the medical information processing system 1, the examination data processing system 10, the database 15, the electronic medical record system 20, the examination device 30, and the user terminal 40 can be connected to each other via at least one of the following: a network 5 (for example, the Internet), wireless communication, and wired communication.

[0033] The examination data processing system 10 processes data (hereinafter referred to as "examination data") obtained from examinations performed on a patient (in this embodiment, the patient's eyes, etc.) by the examination device 30, etc. As an example, the examination data processing system 10 of this embodiment can store the examination data obtained from the examination device 30, etc., in the database 15, associating it with the patient from whom the examination data was obtained. Furthermore, the examination data processing system 10 of this embodiment can also extract examination data specified by a user (e.g., a medical professional, etc.) of the user terminal 40 from among multiple examination data stored in the database 15 and display it on the display unit 46 (46A, 46B) of the user terminal 40. In other words, the examination data processing system 10 of this embodiment can also be described as a filing system for filing examination data. In addition, the examination data processing system 10 of this embodiment can also generate examination implementation information that can be used to bill the patient for medical expenses and output it to the electronic medical record system 20. Details of this will be described later.

[0034] The test data processing system 10 may be a single device (for example, a server or a personal computer). Alternatively, multiple devices (for example, two or more such as a server, a personal computer, and a user terminal 40) may cooperate to function as the test data processing system 10. If a server is used in at least part of the test data processing system 10, the server may be, for example, a server of a manufacturer that provides cloud services (a so-called cloud server), or a server other than a cloud server (for example, a server installed in a medical institution, or a server of a manufacturer that provides a test data processing program). The test data processing system 10 includes a control unit 11 that performs various control processing. The control unit 11 includes a CPU 12, which is a controller that manages the control, and a storage device 13 that can store programs and data. The storage device 13 may store a test data processing program for executing at least part of the test data processing described later (see Figures 2 to 4).

[0035] Database 15 stores various data and information, such as inspection data. In this embodiment, cloud storage (a database on the cloud) is used for database 15. However, it is possible to change the configuration of the database. For example, the database may be connected to the inspection data processing system 10. Alternatively, a storage device 13 or the like provided by the inspection data processing system 10 may be used as the database.

[0036] The electronic medical record system 20 performs processing to manage (store, extract, and output, etc.) medical information (for example, at least one of the following: interview content, examination results, and prescribed medications). Furthermore, the electronic medical record system 20 of this embodiment can also perform medical expense billing processing to bill patients for medical expenses. In other words, the electronic medical record system 20 of this embodiment also functions as a medical expense billing system that performs medical expense billing processing. The medical expense billing system of this embodiment can bill patients for medical expenses for completed tests based on the test implementation information output from the test data processing system 10. However, a separate medical expense billing system may be provided in addition to the electronic medical record system 20. In this case, the medical expense billing system may perform medical expense billing processing based on information obtained from the electronic medical record system 20.

[0037] The electronic medical record system 20 may be a single device (e.g., a server or a personal computer). Alternatively, multiple devices (e.g., two or more such as a server, a personal computer, and a user terminal 40) may work together to function as the electronic medical record system 20. If a server is used in at least part of the electronic medical record system 20, the server may be a cloud server or a server other than a cloud server (e.g., a server installed in a medical institution, or a server of a manufacturer that provides the electronic medical record program). The electronic medical record system 20 includes a control unit 21 that performs various control processing. The control unit 21 includes a CPU 22, which is a controller that manages the control, and a storage device 23 that can store programs and data. The storage device 23 may store an electronic medical record program for executing at least part of the processing of recording patient medical information.

[0038] In this embodiment, the laboratory data processing system 10 and the electronic medical record system 20 are different systems. That is, the laboratory data processing program executed in the laboratory data processing system 10 and the electronic medical record program executed in the electronic medical record system 20 are different. More specifically, in this embodiment, the manufacturer providing the laboratory data processing program and the manufacturer providing the electronic medical record program are different. However, even if the laboratory data processing program and the electronic medical record program are executed on the same device (e.g., a server), at least some of the technologies illustrated in this disclosure can be adopted. For example, if the application implemented by the laboratory data processing program and the application implemented by the electronic medical record program are different, adopting at least some of the technologies illustrated in this disclosure can make it easier to appropriately bill patients for medical expenses.

[0039] The examination device 30 (30A, 30B) performs an examination (including imaging and measurement, etc.) of the patient (in this embodiment, the patient's eye to be examined). The examination device 30 in this embodiment can employ at least one of the following: an OCT device, a scanning laser ophthalmoscope (SLO), a fundus camera, a corneal endothelial cell imaging device, an axial length measuring device, an ocular power measuring device, an intraocular pressure measuring device, etc. The examination device 30 includes a control unit 31 (31A, 31B) that performs various control processing. The control unit 31 includes a CPU 32 (32A, 32B) which is a controller that manages the control, and a storage device 33 (33A, 33B) that can store programs and data, etc. The examination device 30 also includes an examination unit 34 (34A, 34B), an operation unit 35 (35A, 35B), and a display unit 36 ​​(36A, 36B). The examination unit 34 includes various components necessary for the examination device 30 to perform the examination of the patient. Various operation instructions are input to the operation unit 35. The display unit 36 ​​displays various images. The operation unit 35 and the display unit 36 ​​may be integrated with the inspection device 30, or they may be provided separately from the inspection device 30. Multiple inspection devices 30 can be connected to the inspection data processing system 10.

[0040] The user terminals 40 (40A, 40B) are used by users (for example, medical professionals such as doctors, nurses, laboratory technicians, and medical office staff). Various information processing terminals such as mobile terminals, smartphones, desktop PCs, and notebook PCs can be used as user terminals 40. The user terminals 40 are equipped with control units 41 (41A, 41B) that perform various control processing. The control units 41 include a CPU 42 (42A, 42B), which is a controller that manages the control, and a storage device 43 (43A, 43B) capable of storing programs and data. The user terminals 40 also include an operation unit 45 (45A, 45B) and a display unit 46 (46A, 46B). The operation unit 45 and the display unit 46 may be integrated with the user terminal 40 or may be provided separately. Multiple user terminals 40 can be connected to the examination data processing system 10 and the electronic medical record system 20.

[0041] In this disclosure, the term "processor" refers to one or more hardware processors configured to execute program code contained in a program (i.e., one or more instructions of a program). In other words, a "processor" is a hardware device capable of performing one or more programmed operations. For example, a "processor" may be a general-purpose or application-specific processor and may be at least one of a CPU, microprocessor, GPU, and DFP (Data Flow Processor).

[0042] In this disclosure, the term “memory” refers to one or more hardware memories that are non-transitional tangible recording media configured to record at least one of computer program code and data in a manner accessible from a processor. “Memory” can be implemented by memory technologies such as SRAM, SDRAM, non-volatile / flash type memory, or other types of memory. The computer program code that constitutes the program is recorded in memory and executed by the processor to realize various functions in the inspection data processing system 10, etc.

[0043] In this disclosure, the term "circuit" refers to one or more logic circuits as hardware, configured to allow a test data processing system 10, etc., to perform functions. In other words, "circuit" refers to one or more non-programmable devices. For example, "circuit" could be a custom IC, etc., designed to be non-programmable for a specific application.

[0044] In this disclosure, at least one of a circuit and a processor having memory storing computer program code enables the inspection data processing system 10, etc. The expression "at least one of a circuit and a processor" should be interpreted as a disjunctive (logical OR) and not as at least one circuit and at least one processor.

[0045] (Inspection data processing) Referring to Figures 2 to 4, the examination data processing performed by the examination data processing system 10 will be explained. In the examination data processing shown in Figures 2 to 4, the focus will be on the process of generating examination implementation information that can be used to bill patients for medical expenses and outputting it to the electronic medical record system 20, among the various processes performed by the examination data processing system 10. The examination data processing exemplified in Figures 2 to 4 is executed by the CPU 12 of the examination data processing system 10 according to the examination data processing program stored in the storage device 13.

[0046] (First Embodiment) Referring to Figure 2, the inspection data processing performed by the inspection data processing system 10 of the first embodiment will be described. First, the CPU 12 determines whether or not inspection data for an inspection performed on a patient has been input (S1). The inspection data includes various types of data, such as image data taken by the inspection device 30 (medical image acquisition device), measurement data measured by the inspection device 30 (medical information measurement device), and data on the results of an inspection performed by a medical professional (e.g., a doctor or laboratory technician). The inspection data may be input to the inspection data processing system 10 from the inspection device 30, for example, or input to the inspection data processing system 10 by a medical professional. If no inspection data has been input (S1: NO), the process proceeds directly to S7.

[0047] When test data is input and acquired (S1:YES), the CPU 12 identifies the patient who was tested (i.e., the patient from whom the test data was acquired) (S2). Information for identifying the patient may be input, for example, from the testing device 30 or a healthcare professional along with the test data. Alternatively, information for identifying the patient may be input separately from the test data. For example, information for identifying the patient may be input when a patient identifier is read. Alternatively, information for identifying the patient may be input to the test data processing system 10 by a healthcare professional operating the operation unit 45 of the user terminal 40 or the operation unit 35 of the testing device 30, etc.

[0048] Next, the CPU 12 associates the test data acquired in S1 with the patient identified in S2 and saves it to the database 15 (S3). As a result, the test data processing system 10 can extract the saved test data and display it on the display unit, among other processing. After that, processing in S5 and S6 is performed, and the process moves on to S7. The processing in S5 and S6 will be explained later.

[0049] The CPU 12 determines whether a periodic timing (so-called polling timing) has arrived to determine whether there is any test data for which the generation and output processing of test implementation information has not yet been performed (S7). The test data processing system 10 of this embodiment periodically (for example, at regular intervals) determines whether there is any test data among the test data acquired in S1 for which the processing to generate test implementation information (processing in S9 described later) and the processing to output the test implementation information to the electronic medical record system 20 in association with the patient being tested (processing in S10 described later) have not yet been performed (hereinafter referred to as "unprocessed test data"). If the polling timing has not arrived (S7: NO), the process returns to S1. If the polling timing has arrived (S7: YES), the CPU 12 determines whether the test data acquired in S1 contains any unprocessed test data (S8). If it does not contain any (S8: NO), the process returns to S1.

[0050] If there is unprocessed test data (S8:YES), the CPU 12 generates test execution information based on the unprocessed test data obtained in S1 (S9). Test execution information is information that can be used to bill the patient for medical expenses for the tests that have been performed. For example, the test execution information may include information indicating the content of the tests that have been performed, which can be used to calculate medical expenses. The test execution information may also include information such as points set according to the tests performed in order to calculate medical expenses.

[0051] The CPU 12 outputs the test implementation information generated in S9 to the electronic medical record system 20, associating it with the patient identified in S2 (S10). Therefore, even if the test data processing system 10, which performs processing such as saving test data, and the medical expense billing system (e.g., the electronic medical record system 20) that performs medical expense billing are different, the medical expense billing system can automatically and appropriately bill the patient for medical expenses based on the test implementation information entered into the electronic medical record system 20 from the test data processing system 10. Thus, the workload of medical professionals required to input the information necessary to bill for medical expenses is appropriately reduced, and the possibility of incorrect medical expenses being billed is also reduced.

[0052] The inspection data processing system 10 of this embodiment is easy to use because, when a periodic processing timing (polling timing) arrives, if there is unprocessed inspection data, it only needs to execute the inspection information generation process (S9) and the inspection information output process (S10). Furthermore, if there are multiple unprocessed inspection data when the polling timing arrives, the inspection data processing system 10 can execute the inspection information generation process (S9) and the inspection information output process (S10) collectively based on each of the multiple unprocessed inspection data. In addition, the inspection data processing system 10 also needs to perform processes such as displaying the stored inspection data on the display unit. However, by executing the inspection information generation process (S9) and the inspection information output process (S10) by polling, unlike when the inspection information generation process and the inspection information output process are executed each time inspection data is acquired (i.e., when interrupt processing is performed), it is possible to suppress the stopping or delay of other processes that were already being executed (for example, the display process of stored inspection data on the display unit). Therefore, the test implementation information that can be used for medical expense claims is output to the electronic medical record system 20 more appropriately.

[0053] In this embodiment, the examination data processing system 10 performs examination data processing (see Figures 2 to 4) in the background without displaying the processing results on the display unit. Therefore, other processes performed by the examination data processing system 10 (for example, the process of displaying saved examination data on the display unit) are not interfered with, and the examination performance information is appropriately output to the electronic medical record system 20.

[0054] Returning to the explanation of S5 in Figure 2, once the examination data is acquired (S1: YES) and saved in database 15 in association with the patient being examined (S3), the CPU 12 determines in S3 whether examination data for the same patient and type of examination has already been output in S10 on the same day (S5). In other words, after outputting the examination data for the same patient to the electronic medical record system 20, the CPU 12 determines in S3 whether it has newly saved examination data for the same type of examination performed on the same patient to database 15 (S5). For example, if the CPU 12 saves examination data for the right eye of a patient in S3, and then newly saves examination data for the left eye of the same patient in S3, it determines that it has newly saved examination data for the same patient and type of examination. When new test data with the same patient and test type is saved (S5:YES), the CPU 12 outputs an instruction to the electronic medical record system 20 to delete previously outputted test implementation information based on the test data that has the same patient and test type as the newly saved test data. The electronic medical record system 20 in this embodiment (or a medical billing system other than the electronic medical record system 20) deletes the instructed test implementation information when it receives an instruction to delete test implementation information.

[0055] Subsequently, the CPU 12 generates new test execution information based on multiple similar test data, including the newly saved test data (S9). The CPU 12 outputs the newly generated test execution information from S9 to the electronic medical record system 20, associating it with the patient being tested (S10). Therefore, even if additional test data for the same patient is newly saved (for example, if test data for the left eye for the same patient is newly saved after test data for the right eye has been saved), the test execution information based on multiple test data, including the additional test data, is appropriately entered into the electronic medical record system 20. Thus, accurate test execution information is more appropriately obtained by the electronic medical record system 20.

[0056] (Second Embodiment) Referring to Figure 3, the inspection data processing performed by the inspection data processing system 10 of the second embodiment will be described. Some of the processing in the second and third embodiments described below can be the same as the processing in the first embodiment described above, and the same effects can be obtained. Therefore, for the processing in the second and third embodiments that can be the same as the processing in the first embodiment, the same step numbers as those assigned in the first embodiment will be used, and their detailed explanations will be omitted or simplified.

[0057] The CPU 12 determines whether or not test data for tests performed on a patient has been entered (S1). If test data has not been entered (S1: NO), the process proceeds directly to S7. If test data has been entered and acquired (S1: YES), the CPU 12 identifies the patient for whom the acquired test data was performed (i.e., the patient for whom the test data was acquired) (S2). The CPU 12 associates the test data acquired in S1 with the patient identified in S2 and saves it to the database 15 (S3). The processes in S5 and S6 are the same as in the first embodiment (see Figure 2), so their explanation is omitted.

[0058] CPU12 determines whether a periodic timing (so-called polling timing) has arrived to determine whether there is any inspection data for which the generation and output processing of inspection performance information has not yet been performed (S7:NO). If the polling timing has not arrived (S7:YES), the process returns to S1. If the polling timing has arrived (S7:YES), CPU12 determines whether the inspection data acquired in S1 contains any unprocessed inspection data (S8). If it does not contain any (S8:NO), the process returns to S1.

[0059] If there is unprocessed test data (S8:YES), the CPU 12 determines whether the patient being tested for the specific test from which the unprocessed test data was acquired (in this embodiment, the test performed by the testing device 30 that acquired the unprocessed test data) has been changed to another patient (S21). In other words, after the CPU 12 has first saved the unprocessed test data in the database 15 in association with the patient being tested, it determines whether a patient different from the patient being tested for the previously saved test data has been identified as the patient being tested for the same test (in this embodiment, the test performed by the testing device 30 that acquired the unprocessed test data). If the patient being tested for a specific test has been changed (S21:YES), it is unlikely that the specific test will be performed again on the patient from whom the test data was previously saved. In this case, the CPU 12 generates test execution information based on the unprocessed test data acquired in S1 (S9), and outputs the generated test execution information to the electronic medical record system 20 in association with the patient being tested (S10). As a result, accurate test execution information is output appropriately.

[0060] The specific method by which the test data processing system 10 recognizes a change in the target patient for a particular test can be selected as appropriate. For example, the CPU 12 may determine that the target patient for a particular test has changed when the test data processing system 10 itself, or a particular testing device 30, changes from the previous patient to a new patient. In this case, information to identify the new target patient may be entered into the test data processing system 10 or the testing device 30 by a healthcare professional. Alternatively, information to identify the new target patient may be entered when a new patient identifier is read. Furthermore, the CPU 12 may determine that the target patient for a particular test has changed when, after previously saving the test data in the database 15 in association with the target patient, it acquires new specific test data (in this embodiment, test data for a test performed by the same testing device 30) that was performed on a patient different from the target patient of the previously saved test data.

[0061] If the patient being tested for a specific test has not changed (S21:NO), the CPU 12 determines whether the patient's condition has changed (S22). In other words, after the CPU 12 stores the test data in the database 15, associating it with the patient being tested, it determines whether the patient's condition in the stored test data is different from the condition during the execution of the same test (S22). If the patient's condition has changed (S22:YES), it can be determined that the likelihood of performing an additional test of the same type is low. In this case, the CPU 12 generates test execution information based on the unprocessed test data acquired in S1 (S9), and outputs the generated test execution information to the electronic medical record system 20, associating it with the patient being tested (S10). As a result, accurate test execution information is output appropriately.

[0062] The specific method by which the test data processing system 10 can determine that the condition of a patient who has undergone a particular test has changed can be selected as appropriate. For example, the CPU 12 may determine that the condition of a patient has changed when the patient whose test data was previously saved is identified as a target for another test by the testing device 30 that performs other tests. Alternatively, the CPU 12 may determine that the condition of a patient has changed when information such as an instruction to perform medical treatment for the patient whose test data was previously saved, or information indicating that the patient is awaiting treatment, is input to the test data processing system 10. The CPU 12 may also determine that the condition of a patient has changed when it obtains information indicating that the patient whose test data was previously saved has moved to a different location from the location of the previously performed test. In this case, for example, whether or not the patient has moved may be determined based on location information of the user terminal 40 held by the patient or the medical professional performing the test on the patient. Furthermore, the CPU 12 may determine that the condition of a patient has changed when an instruction to start accounting processing for the patient whose test data was previously saved is input. The examination data processing system 10 may obtain information from other systems or devices indicating a change in the condition of the patient being examined.

[0063] If the patient's condition has not changed since the acquisition of unprocessed test data (S22: NO), the CPU 12 determines whether a predetermined time has elapsed since the unprocessed test data was stored in the database 15 in association with the patient (S23). If the predetermined time has not elapsed (S23: NO), the process returns to S1. If the predetermined time has elapsed (S23: YES), the CPU 12 generates test implementation information based on the unprocessed test data acquired in S1 (S9), and outputs the generated test implementation information to the electronic medical record system 20 in association with the patient (S10). When the same type of test is performed multiple times on a patient, the multiple tests are often completed within a certain time. Therefore, by generating and outputting test implementation information regarding the patient after a predetermined time has elapsed since the test data was stored in the database 15, accurate test implementation information is more likely to be appropriately output to the electronic medical record system 20.

[0064] (Third embodiment) Referring to Figure 4, the inspection data processing performed by the inspection data processing system 10 of the third embodiment will be described. Since the processing of S1 to S3, S7, and S8 in the third embodiment is the same as the processing of S1 to S3, S7, and S8 in the first and second embodiments, the explanation will be omitted or simplified.

[0065] When the polling timing arrives (S7:YES), and the test data acquired in S1 includes unprocessed test data (S8:YES), the CPU 12 determines whether the test data from other test dates or other types of test data acquired for the patient whose test data is unprocessed is test data for both eyes (S31). If the other test data acquired for the patient whose test data is not for both eyes but for one eye (S31:NO), then it is highly likely that the unprocessed test data is also test data for one eye. Therefore, at any timing after acquiring the unprocessed test data in S1 (in this embodiment, the polling timing), the CPU 12 generates test implementation information based on the unprocessed test data (S9), and outputs the generated test implementation information to the electronic medical record system 20, associating it with the patient whose test data is being performed (S10). As a result, the test implementation information is output appropriately at an early stage.

[0066] On the other hand, if other examination data obtained for the patient being examined is bilateral examination data (S31:YES), then it is highly likely that the unprocessed examination data is also part of the bilateral examination data. Therefore, the CPU 12 determines whether or not the acquisition of bilateral examination data for the patient being examined has been completed (S32). If the acquisition of bilateral examination data has been completed (S32:YES), the CPU 12 generates examination implementation information based on the unprocessed bilateral examination data (S9), and outputs the generated examination implementation information to the electronic medical record system 20, associating it with the patient being examined (S10). As a result, accurate examination implementation information for both eyes is output.

[0067] If the acquisition of examination data for both eyes is not complete (S32: NO), the CPU 12 determines whether a predetermined time has elapsed since the unprocessed examination data (examination data for one eye in this embodiment) was acquired and saved (S33). If the predetermined time has not elapsed (S33: NO), the process returns to S1. If the predetermined time has elapsed (S33: YES), examination implementation information is generated based on the unprocessed examination data for one eye (S9), and the generated examination implementation information is associated with the patient being examined and output to the electronic medical record system 20 (S10). Through the above process, the examination implementation information is more likely to be output appropriately based on the predicted nature of the examination data (the possibility that it is data for both eyes).

[0068] The technologies disclosed in the above embodiments are merely examples. Therefore, it is possible to modify the technologies exemplified in the above embodiments. For example, it is possible to implement only a part of the technologies exemplified in the above embodiments. Specifically, it is possible to omit processes S5 and S6 from the inspection data processing shown in Figures 2 and 3. It is also possible to omit process S7 from the inspection data processing shown in Figures 2 and 3. Furthermore, it is possible to omit one or two of processes S21, S22, and S23 from the inspection data processing of the second embodiment shown in Figure 3.

[0069] Furthermore, in the first embodiment (see Figure 2) and the second embodiment (see Figure 3) described above, if test implementation information has already been output on the same day for test data that is identical in terms of the patient being tested and the type of test, the test data processing system 10 issues a command to the electronic medical record system 20 to delete the already outputted inaccurate test implementation information. However, it is also possible for the electronic medical record system 20 to delete the inaccurate test implementation information at its own discretion. In other words, if the CPU 22 of the electronic medical record system 20 inputs new test implementation information for the same type of test associated with the same patient being tested after inputting the test implementation information, it may delete the previously input test implementation information and execute the medical expense billing process based on the newly input test implementation information. In this case as well, the medical expenses will be appropriately billed to the patient based on the accurate test implementation information. [Explanation of Symbols]

[0070] 10. Inspection Data Processing System 12 CPU 15 Databases 20 Electronic Medical Record System 22 CPU 30 (30A, 30B) Inspection device

Claims

1. A test data processing program executed by a test data processing system that processes test data, which is data of test results for patients, The inspection data processing program is executed by the controller of the inspection data processing system, The process of obtaining test data from tests performed on a patient, The process of identifying the patient to be tested from the acquired test data, The process involves storing the acquired test data in a database, associated with the patient being tested. Based on the acquired test data, a process is performed to generate test implementation information that can be used to bill the patient for medical expenses for the tests that have been performed. The process involves outputting the aforementioned test implementation information to an electronic medical record system that records the patient's clinical information, in association with the patient being tested. An inspection data processing program characterized by causing the inspection data processing system to execute the above.

2. A test data processing program according to claim 1, It is periodically determined whether there is any of the acquired test data for which the process of generating the test implementation information and the process of outputting the test implementation information to the electronic medical record system in association with the patient being tested have not yet been performed. A test data processing program characterized in that, if the aforementioned periodic judgment determines that there is test data for which the process of outputting the test implementation information has not yet been performed, the test data processing system performs a process of generating the test implementation information based on the test data, and a process of outputting the test implementation information to the electronic medical record system in association with the patient being tested.

3. A test data processing program according to claim 1 or 2, After the aforementioned test data has been saved in the database in association with the aforementioned patient, if a patient different from the patient previously saved in the aforementioned test data is identified as a patient for the same test, A process to generate the inspection implementation information based on the previously saved inspection data, The process involves outputting the generated test implementation information to the electronic medical record system, associating it with the aforementioned patient who underwent the test. An inspection data processing program characterized by causing the inspection data processing system to execute the above.

4. A test data processing program according to any one of claims 1 to 3, After the aforementioned test data has been stored in the database in association with the patient being tested, if the patient's condition in the stored test data changes from a condition that occurred during the execution of the same test, A process for generating the inspection implementation information based on the saved inspection data, The process involves outputting the generated test implementation information to the electronic medical record system, associating it with the patient being tested. An inspection data processing program characterized by causing the inspection data processing system to execute the above.

5. A test data processing program according to any one of claims 1 to 4, After the aforementioned test data has been stored in the database in association with the aforementioned patients, a predetermined period of time has elapsed, A process for generating the test implementation information based on one or more of the test data obtained and stored within the predetermined time for the patient subject to the test, and of the same test type; The process involves outputting the generated test implementation information to the electronic medical record system, associating it with the patient being tested. An inspection data processing program characterized by causing the inspection data processing system to execute the above.

6. A test data processing program according to claim 5, If the examination data obtained for the aforementioned patient from other examination dates or other types of examination data is for both eyes, the examination data for one eye is stored in the database in association with the aforementioned patient. After a predetermined time has elapsed, or upon completion of obtaining the examination data for both eyes of the aforementioned patient, the examination implementation information is generated and output to the electronic medical record system. A test data processing program characterized in that, if the test data obtained for the aforementioned patient on another test day or of another type of test data is the aforementioned test data for one eye, the program generates the test implementation information and outputs it to the electronic medical record system at a time after the aforementioned test data for one eye of the aforementioned patient has been obtained.

7. A test data processing program according to any one of claims 1 to 6, If, after outputting the aforementioned test implementation information to the electronic medical record system in association with the patient being tested, the test data for the same type of test performed on the same patient being tested is newly saved to the database on the same day, A process to output a deletion instruction for the previously outputted examination information to the electronic medical record system, A process for generating new inspection implementation information based on multiple identical inspection data, including the newly saved inspection data, The process involves outputting the newly generated test information to the electronic medical record system, associating it with the patient being tested. An inspection data processing program characterized by causing the inspection data processing system to execute the above.

8. A test data processing system that processes test data, which is data of test results for patients, The control unit of the aforementioned inspection data processing system is: The process of obtaining test data from tests performed on a patient, The process of identifying the patient to be tested from the acquired test data, The process involves storing the acquired test data in a database, associated with the patient being tested. Based on the acquired test data, a process is performed to generate test implementation information that can be used to bill the patient for medical expenses for the tests that have been performed. The process involves outputting the aforementioned test implementation information to an electronic medical record system that records the patient's clinical information, in association with the patient being tested. A test data processing system characterized by performing the following actions.

Images