Inspection data processing program and inspection data processing system

Abstract

This invention provides a test data processing program and a test data processing system that enable the editing of document data managed in an electronic medical record system with simple operations. [Solution] The CPU 12 of the examination data processing system 10 performs the following operations: download monitoring (S4) to monitor whether there is any document data to be downloaded from the electronic medical record system 20 that is to be edited; editing display (S6) to detect that document data has been downloaded from the electronic medical record system 20 and to display an editing screen for the document data; extraction (S7) to extract the medical information of the patient based on the patient identification information associated with the document data; insertion (S7) to insert the extracted medical information into the document data; and saving (S10) to save the document data as data to be uploaded to the electronic medical record system 20.

Description

Technical Field

[0001] The present disclosure relates to an inspection data processing program for editing document data managed by an electronic medical record system and the like.

Background Art

[0002] As a technique for transferring inspection data to an electronic medical record, for example, the medical information management system described in Patent Document 1 is known. The medical information management system described in Patent Document 1 is a medical information management system that manages medical information in electronic data, and includes an inspection screen for acquiring inspection data of a patient, and a transcription operation control means for performing a transcription operation for transcribing the inspection data acquired on the inspection screen to the electronic medical record based on a trigger signal for storing the inspection data.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a medical field, there may be a case where an inspection data processing system (which may also be referred to as a "filing system" or the like) that executes processes such as storage and display of inspection data, and an electronic medical record system that records clinical information of a patient are provided separately. In this case, when a medical staff edits document data managed by the electronic medical record system using the inspection data processing system, the medical staff needs to perform a download operation on the document data to be edited once, and then start and edit the editing software or editing application on the inspection data processing system side by himself / herself. In addition, after the editing is completed, an operation of uploading the document data to the electronic medical record system is also required.

[0005] To illustrate an example of user operations expected in an existing system, for instance, a user might download a template of document data managed on the electronic medical record system. The user then needs to open the downloaded document data with editing software or an editing application and perform editing operations on the document data. After completing the editing process, the user needs to close the editing software or application and perform the necessary preparation and saving operations to save the document data on the electronic medical record system.

[0006] In other words, the need to perform the cumbersome procedures described above when editing document data resulted in a decrease in the work efficiency of healthcare professionals who were the users.

[0007] This disclosure aims to provide a test data processing program and a test data processing system that enable the editing of document data managed in an electronic medical record system with simple operations. [Means for solving the problem]

[0008] A typical embodiment of the present disclosure provides a test data processing program which is executed by a test data processing system that processes medical information including test data showing test results for a patient, and which causes the computer of the test data processing system to execute the following: document data monitoring process which monitors whether or not a predetermined operation has been performed on document data to be edited, which is managed by an electronic medical record system that records the patient's clinical information; extraction process which, when the predetermined operation on the document data is detected, extracts the patient's medical information based on the patient's identification information associated with the document data; insertion process which inserts the extracted medical information into the document data; and storage process which saves the edited document data as document data managed by the electronic medical record system.

[0009] A typical embodiment of the present disclosure provides a test data processing system for processing medical information including test data showing test results for a patient, comprising: a document data monitoring processing unit that monitors whether a predetermined operation has been performed on document data to be edited, which is managed by an electronic medical record system that records the patient's clinical information; an extraction processing unit that, when the predetermined operation on the document data is detected, extracts the patient's medical information based on the patient's identification information associated with the document data; an insertion processing unit that inserts the extracted medical information into the document data; and a storage processing unit that stores the edited document data as document data managed by the electronic medical record system.

[0010] According to the inspection data processing program and inspection data processing system related to this disclosure, document data managed by the electronic medical record system can be edited with simple operations. [Brief explanation of the drawing]

[0011] [Figure 1] This is a block diagram showing the schematic configuration of the medical information processing system in this embodiment. [Figure 2] This is a sequence diagram showing the operation of the examination data processing system and the electronic medical record system according to the first embodiment. [Figure 3] This is a diagram illustrating the procedure for processing document data in the examination data processing system and electronic medical record system according to the first embodiment. [Figure 4] This figure shows an example of a display screen showing the editing screen for medical information and document data in the inspection data processing system according to the first embodiment. [Figure 5] This figure shows an example of the state before medical information is inserted into document data in the inspection data processing system according to the first embodiment. [Figure 6] This figure shows an example of the state after medical information has been inserted into document data in the inspection data processing system according to the first embodiment. [Figure 7]This is a sequence diagram showing the operation of the examination data processing system and the electronic medical record system according to the second embodiment. [Figure 8] This is a sequence diagram showing the operation of the examination data processing system and the electronic medical record system according to the third embodiment. [Modes for carrying out the invention]

[0012] <Overview> The laboratory data processing program described herein monitors whether a predetermined operation has been performed on the document data to be edited, which is managed by the electronic medical record system. If a predetermined operation is detected, it extracts the patient's medical information based on the patient's identification information associated with the document data. The extracted medical information is inserted into the document data, and the computer of the laboratory data processing system is operated to save the edited document data as document data managed by the electronic medical record system.

[0013] Thus, in the examination data processing program relating to this disclosure, when a predetermined operation is performed on document data managed by the electronic medical record system, the program extracts the patient's medical information from the medical information managed by the examination data processing system based on the patient's identification information associated with the document data, inserts the extracted medical information into the document data, and saves the edited document data as document data managed by the electronic medical record system. This allows the user to edit the document data with simple operations.

[0014] Furthermore, since only editing operations will be performed on document data managed by the electronic medical record system, there will be no need to allocate storage space for storing document data in the examination data processing system.

[0015] The document data includes, for example, a referral letter in which the course of illness and test results are described, an operation record to which image data at the time of the operation is attached, a consent form before the operation, a questionnaire including test data, and summary information of the disease. The document data includes at least text data, and may further include information including still images and moving images.

[0016] In addition, the medical information includes various data such as data of images taken by a medical image capturing device, measurement data measured by a medical information measuring device, data of the results of tests performed by medical staff (for example, doctors or medical technicians, etc.). These medical information may be input into the test data processing system from a medical image capturing device, a medical information measuring device, etc., or may be input into the test data processing system by medical staff. Note that the test data processing system is a system different from the electronic medical record system.

[0017] Furthermore, the predetermined operation may include, for example, a download operation of document data, an operation of opening a file of document data, etc. That is, an operation that triggers the start of editing of the document data managed by the electronic medical record system may be included.

[0018] The test data processing program according to the present disclosure operates the computer of the test data processing system to display an editing screen of the document data when a predetermined operation on the document data is detected as necessary.

[0019] Thus, in the test data processing program according to the present disclosure, since the editing screen of the document data is displayed when a predetermined operation is performed, the user's operation can be reduced, the user can easily confirm the edited content of the document data, and the accuracy of editing in the document data can be improved.

[0020] The inspection data processing program according to the present disclosure operates a computer of an inspection data processing system to display medical information of a patient based on the identification information of the patient when a predetermined operation on document data is detected as necessary.

[0021] Thus, in the inspection data processing program according to the present disclosure, when a predetermined operation on document data is detected, in order to display the medical information of the corresponding patient, it is possible to synchronize the patient associated with the document data to be edited and the patient of the medical information to be displayed as the same patient, and it is possible to prevent the document data from describing information of different patients.

[0022] The inspection data processing program according to the present disclosure operates a computer of an inspection data processing system to display medical information related to the type according to the type of document data as necessary.

[0023] Thus, in the inspection data processing program according to the present disclosure, since the medical information corresponding to the type of document data is automatically displayed, the operations of the user are reduced and the user can edit the document data with simple operations.

[0024] The type of document data is, for example, types such as referrals, surgical records, consent forms, questionnaires or summary information as described above.

[0025] The inspection data processing program according to the present disclosure operates a computer of an inspection data processing system to extract medical information related to the type according to the type of document data as necessary.

[0026] Thus, in the inspection data processing program according to the present disclosure, the medical information related to the type of document data is automatically extracted, saving the trouble of the user to search for it himself / herself, and reducing the work of the user.

[0027] The inspection data processing program relating to this disclosure, if necessary, detects a predetermined string of characters contained within the document data and operates the computer of the inspection data processing system to insert medical information that has been pre-associated with that string of characters.

[0028] Thus, in the inspection data processing program related to this disclosure, medical information corresponding to a predetermined string of characters contained in the document data is automatically inserted, reducing the effort required for the user to search for the information and perform tasks such as copying and pasting.

[0029] The specified string is pre-set for each piece of medical information to be inserted, and may include alphanumeric characters, kana characters, symbols, etc.

[0030] The inspection data processing program relating to this disclosure, if necessary, when it detects a predetermined operation on document data associated with a different patient, such as when medical information of another patient is already displayed, operates the computer of the inspection data processing system to switch from a state where medical information of another patient is displayed to a state where medical information of a specific patient is displayed.

[0031] Thus, in the inspection data processing program relating to this disclosure, when a predetermined operation on document data corresponding to one patient is detected while the medical information of another patient is being displayed, the program switches to a state where the medical information of one patient is displayed. This allows the document data to be edited and the displayed medical information to be synchronized, preventing the inclusion of information of a different patient in the document data.

[0032] The test data processing program relating to this disclosure, if necessary, will operate the computer of the test data processing system so that medical information of a patient other than the patient associated with that patient is not displayed when it detects a predetermined operation on document data associated with a patient.

[0033] Thus, in the inspection data processing program relating to this disclosure, when a predetermined operation is detected on document data associated with one patient, medical information of other patients is prevented from being displayed. This prevents the document data being edited and the displayed medical information from relating to different patients, thus preventing the document data from containing information of a different patient.

[0034] The inspection data processing program relating to this disclosure, when displaying an editing screen for document data associated with a patient through editing and display processing, will, if necessary, cause medical information for a patient other than the patient to be displayed, to terminate the editing of the document data and save it.

[0035] Thus, in the inspection data processing program relating to this disclosure, when the editing screen for document data associated with a single patient is displayed through the editing and display process, if medical information for another patient is displayed, the editing of the document data is terminated and saved. This prevents the document data being edited and the displayed medical information from relating to different patients, thus preventing the inclusion of information for a different patient in the document data.

[0036] <First Embodiment> A test data processing program and a test data processing system according to the first embodiment will be described with reference to Figures 1 to 6. In the following embodiments, a test data processing program and a test data processing system for ophthalmology will be described, but at least a part of the technology exemplified in this disclosure can also be applied to other medical departments (e.g., internal medicine, surgery, orthopedics, dermatology, etc.) or to health checkup facilities, etc.

[0037] Figure 1 is a block diagram showing the system configuration of a medical information processing system using the examination data processing system according to the first embodiment. In Figure 1, the medical information processing system 1 comprises an examination data processing system 10, a database 15, an electronic medical record system 20, examination devices 30 (30A, 30B), and user terminals 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 devices 30, and the user terminals 40 can communicate with each other via at least one of the following: a network 5 (e.g., the Internet), wireless communication, and wired communication.

[0038] The examination data processing system 10 processes data (hereinafter referred to as "examination data") obtained from examinations performed on a patient (in the first embodiment, the patient's eyes, etc.) by the examination device 30, etc., as medical information. As an example of examination data processing, the examination data processing system 10 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. The examination data processing system 10 can also extract examination data specified by the user of the user terminal 40 (for example, a medical professional, etc.) 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 can also be described as a filing system that files examination data.

[0039] 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).

[0040] Database 15 stores various data and information, such as inspection data. Cloud storage (a database on the cloud) is used for database 15. However, the database configuration can be changed. For example, the database may be connected to the inspection data processing system 10. Alternatively, the storage device 13 or other components of the inspection data processing system 10 may be used as the database.

[0041] The electronic medical record system 20 manages (stores, retrieves, and outputs, etc.) medical information (for example, at least one of the following: interview content, examination results, and prescribed medications), as well as various document data as described above. Templates are provided for the various document data, and they can be output with the patient's basic information (patient ID, name, age, gender, etc.) inserted as needed.

[0042] 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.

[0043] In the first embodiment, the examination data processing system 10 and the electronic medical record system 20 are independent and different systems. That is, the examination data processing program executed in the examination data processing system 10 and the electronic medical record program executed in the electronic medical record system 20 are different. More specifically, in the first embodiment, the manufacturer providing the examination data processing program and the manufacturer providing the electronic medical record program are different. However, even when the examination 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, even if the application implemented by the examination data processing program and the application implemented by the electronic medical record program are different, common document data can be edited and managed by adopting at least some of the technologies illustrated in this disclosure.

[0044] The examination device 30 (30A, 30B) performs an examination (including imaging and measurement, etc.) of the patient (in the first embodiment, the patient's eye to be examined). The examination device 30 in the first 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.

[0045] 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.

[0046] 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).

[0047] 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.

[0048] 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.

[0049] 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.

[0050] The document data editing process, from editing document data managed by the electronic medical record system 20 using medical information (specifically, test data) managed by the test data processing system 10, to saving the edited document data to the electronic medical record system 20, will be explained below using Figures 2 and 3. Figure 2 is a sequence diagram showing the operation of the test data processing system and the electronic medical record system according to the first embodiment, and Figure 3 is a configuration diagram showing the document data processing procedure in the test data processing system and the electronic medical record system according to the first embodiment. Here, we will explain the case where the electronic medical record system 20 is operated on the cloud and the test data processing system 10 is operated on-premise.

[0051] In Figure 2, first, a user such as a healthcare professional downloads a template of necessary document data for a specific patient (hereinafter referred to as "a patient") from the web browser of user terminals 40A and 40B (S1). Specifically, the user selects a patient and the type of document data to download, and this information is entered into the electronic medical record system 20.

[0052] The CPU 22 of the electronic medical record system 20, which has been inputted with information about a patient and the type of document data, reads the basic information of the patient (for example, at least one of the following pieces of information, such as name, age, gender, disease, etc., which can be obtained in the electronic medical record system 20) from the storage device 23 and inserts it into the document data to be downloaded (S2). At this time, the CPU 22 determines the file name of the document data so that it includes at least the patient ID. In addition to the patient ID, the file name may also include an ID indicating the type of document data (hereinafter referred to as the type ID). The CPU 22 downloads the document data, into which the basic information of the patient has been inserted and in which at least the patient ID is included in the file name, to a predetermined download folder or a download folder specified by the user (S3). The processing up to this point corresponds to the processing indicated by arrows A and B in Figure 3. The template of the document data may be stored and managed in the storage device 23 of the electronic medical record system 20, as described above, or it may be stored and managed in the database 15. In addition to including patient ID and type ID information in the file name, it may also be included within the document data itself, or specified in the file properties.

[0053] The CPU 12 of the examination data processing system 10 functions as a document data monitoring processing unit and performs document data monitoring processing to periodically or irregularly monitor whether document data downloaded from the electronic medical record system 20 exists in a predetermined download folder or a download folder specified by the user. If the CPU 12 detects that document data is in the download folder, it moves the document data to an editing folder predetermined in the examination data processing system 10 (S4). The processing from S3 to this point corresponds to the processing indicated by arrow C in Figure 3.

[0054] CPU 12 functions as a medical information display processing unit, extracting the patient ID of a patient from the file name of the document data, and executing medical information display processing (S5) to read the medical information (test data, etc.) of the patient corresponding to that patient ID from the database 15 and display it on the user terminals 40A and 40B. If the file name of the document data includes a type ID, it is desirable that the medical information necessary for editing the document data, which is pre-configured for each type ID, be displayed in a way that is easily accessible to the user and appears at the forefront.

[0055] Furthermore, the CPU 12 functions as an editing and display processing unit and executes an editing and display process (S6) to display the editing screen of the downloaded document data using editing software. Specifically, it launches editing software corresponding to the file extension of the document data. At this time, the editing software to be launched may be selected according to the type ID. These editing software may be general-purpose software installed on user terminals 40A and 40B, or system-specific software corresponding to the functions of the inspection data processing system 10, and may be editing software that supports not only text character editing but also images and videos. The processes in S5 and S6 correspond to the processes shown by arrow D in Figure 3.

[0056] Here, we will explain the display screens on user terminals 40A and 40B with specific examples. Figure 4 is a diagram showing an example of a display screen in which the medical information and document data editing screens are displayed in the inspection data processing system according to the first embodiment. The CPU 12 of the inspection data processing system 10 executes the processes S5 and S6 described above, thereby displaying a display screen like the one in Figure 4 on the display units 46A and 46b of the user terminals 40A and 40B. Note that the medical information and document data editing screens do not necessarily have to be displayed simultaneously; a display configuration in which only one of them is displayed is also acceptable. For example, when it is detected that document data is in the download folder, only S5 may be executed and the medical information may be automatically displayed, or only S6 may be executed and the document data editing screen may be automatically displayed, or both S5 and S6 may be executed and the medical information and document data editing screens may be automatically displayed at the same time.

[0057] In Figure 4, the editing screen for the document data to be edited is displayed on the left side of the screen, and the medical information necessary for editing the document data (medical information of the patient corresponding to the patient ID included in the document data) is displayed on the right side of the screen. These two screens are displayed by the CPU 12 when the document data is downloaded from the electronic medical record system 20 in response to user operation, thus reducing cumbersome processing for the user and preventing medical information for different patient IDs from being displayed side by side for the document data being edited. Note that the arrangement of each screen shown in Figure 4 is merely an example, and they can be arranged arbitrarily according to the user's convenience.

[0058] Returning to Figure 2, CPU 12 functions as an extraction processing unit and performs an extraction process to extract medical information to be inserted into the document data from database 15 based on the patient ID included in the file name of the document data and the keywords that have been pre-inserted into the document data that is open for editing. Then, CPU 12 functions as an insertion processing unit and performs an insertion process to insert the extracted medical information into the document data (for example, in place of the keywords in the document data) (S7). This S7 process corresponds to the process indicated by arrow E in Figure 3.

[0059] Here, we will explain a specific example of inserting medical information into document data. Figures 5 and 6 show how medical information is inserted into document data in the examination data processing system according to the first embodiment. Figure 5 is an example of document data (in this case, a referral letter) before medical information is inserted, and Figure 6 is an example of document data (in this case, a referral letter) after some medical information has been inserted.

[0060] As shown in Figure 5, the referral letter downloaded from the electronic medical record system 20 contains pre-filled information such as the patient's basic information and disease name, which are managed by the electronic medical record system 20, in addition to standard phrases. On the other hand, for sections where medical information such as test results, which are not managed by the electronic medical record system 20, is to be inserted, predetermined keywords (for example, data names such as "XX test image", predetermined medical information codes such as "A01-0001", and unique ID information such as "XXXX (patient ID) + XXXX (image ID)") are pre-embedded.

[0061] When the process in S7 described above is executed, the corresponding medical information is extracted and inserted into the referral letter in Figure 5, creating a referral letter as shown in Figure 6. This eliminates the need for the user to perform operations such as copying and pasting medical information, thus improving work efficiency. If the editing of the document file is completed in the state shown in Figure 6, the process in S8 described below may be omitted and the process proceeds to S9. If the editing of the document file is not completed in the state shown in Figure 6, the process proceeds to S7 described below, allowing the user to manually edit the document file.

[0062] Furthermore, if no keywords are inserted into the document data, and the document data file name includes the type ID, the system may extract the medical information necessary for editing the document data, which is pre-configured for each type ID. As a result of extracting the medical information corresponding to the type ID, for example, in a display screen like the one shown in Figure 4, only the portion of the medical information related to the type ID of the document data may be displayed in a different display manner from the rest (for example, by changing the text format such as color or font, making it blink, or by adding marks or patterns), or a separate summary screen containing only the extracted medical information may be displayed. In addition, the medical information corresponding to the type ID may be arbitrarily set on the examination data processing system 10 side.

[0063] Returning to Figure 2, users such as healthcare professionals operate user terminals 40A and 40B to perform any necessary editing operations on the document data other than those performed in S7 (S8). For example, in S7, users can paste missing test data or edit the text of the document data using the respective operation units 45A and 45B on user terminals 40A and 40B. In particular, if keywords are not inserted into the document data and the file name of the document data contains a type ID, operations such as pasting medical information extracted according to the type ID into the document data are performed. This processing in S8 corresponds to the processing indicated by arrow F in Figure 3.

[0064] Once the user has finished editing the document data, they end the editing work and close the document data editing screen (i.e., exit the editing software) (S9).

[0065] CPU 12 functions as a save processing unit, saving the edited content performed on the document data and moving the document data to a predetermined upload folder (S10). In other words, it saves the document data after editing is complete to the upload folder as data to be uploaded to the electronic medical record system 20. This process in S10 corresponds to the process indicated by arrow G in Figure 3.

[0066] The CPU 22 of the electronic medical record system 20 uploads the document data stored in the upload folder to the storage device 23 of the electronic medical record system 20 (S11), and then terminates processing. This processing in S11 corresponds to the processing indicated by arrows H and A in Figure 3.

[0067] The destination for uploading the edited document data may be the storage device 23 of the electronic medical record system 20, or it may be the database 15.

[0068] Alternatively, the CPU 22 of the electronic medical record system 20 may periodically or irregularly monitor whether document data exists in the upload folder, and if document data exists, the upload process of S11 may be performed. Alternatively, the CPU 12 of the examination data processing system 10 may periodically or irregularly monitor whether document data exists in the upload folder, and if document data exists, execute a predetermined procedure for performing the upload function of the electronic medical record system 20 (generating an operation signal corresponding to the predetermined operation and inputting it to the electronic medical record system 20), and the upload process of S11 may be performed.

[0069] Furthermore, while the above description focused on the case where a download operation is performed as a predetermined operation on the document data to be edited, any operation that triggers the start of editing the document data is acceptable, such as opening a template file of the document data.

[0070] Thus, in the examination data processing program according to the first embodiment, the computer of the examination data processing system 10 is instructed to perform the following: a document data monitoring process (S4) to monitor whether or not there is document data to be edited that is downloaded from the electronic medical record system 20; an extraction process (S7) to extract the patient's medical information based on the patient's identification information associated with the document data when a download operation for the document data is detected; an insertion process (S7) to insert the extracted medical information into the document data; and a saving process (S10) to save the edited document data as document data managed by the electronic medical record system 20. As a result, users such as medical professionals can easily edit document data managed by the electronic medical record system 20 by reflecting the patient's medical information managed by the examination data processing system 10, which is a separate system.

[0071] Furthermore, based on the patient identification information associated with the document data, the medical information of the patient is extracted, the extracted medical information is inserted into the document data, and the edited document data is saved as document data managed by the electronic medical record system 20, allowing users to edit the document data with simple operations.

[0072] Furthermore, since only editing operations will be performed on document data managed by the electronic medical record system 20, there will be no need to allocate storage space in the examination data processing system 10 for storing document data.

[0073] Furthermore, the examination data processing program according to the first embodiment, if necessary, detects that document data has been downloaded from the electronic medical record system 20, and instructs the computer of the examination data processing system 10 to execute an editing display process (S6) that displays the document data editing screen. This reduces user operation, makes it easier for the user to confirm the edited content of the document data, and improves the accuracy of editing the document data.

[0074] Furthermore, the examination data processing program according to the first embodiment, if necessary, detects that document data has been downloaded from the electronic medical record system 20, and instructs the computer of the examination data processing system 10 to execute a medical information display process (S5) that displays the patient's medical information together with the document data editing screen based on the patient's identification information. This allows the document data being edited and the displayed medical information to be synchronized for the same patient, preventing the inclusion of information for a different patient in the document data.

[0075] Furthermore, the inspection data processing program according to the first embodiment operates the computer of the inspection data processing system 10 to display medical information related to the type of document data along with the document data editing screen as needed, so that medical information according to the type of document data is automatically displayed, reducing user operation and allowing the user to edit the document data with simple operations.

[0076] Furthermore, the inspection data processing program according to the first embodiment, if necessary, operates the computer of the inspection data processing system to extract medical information related to a given type according to the type ID contained in the document data during the extraction process. As a result, medical information related to the document data is automatically extracted, saving the user the trouble of searching for it themselves and reducing the user's workload.

[0077] Furthermore, the inspection data processing program according to the first embodiment, if necessary, detects a predetermined string of characters contained in the document data during the insertion process and operates the computer of the inspection data processing system to insert pre-associated medical information in place of the string. As a result, medical information corresponding to the predetermined string of characters contained in the document data is automatically inserted, reducing the effort required for the user to search for the information and perform tasks such as copying and pasting.

[0078] <Second Embodiment> A second embodiment of the inspection data processing program and inspection data processing system will be described with reference to Figure 7. In the second embodiment, explanations that overlap with the first embodiment will be omitted.

[0079] Figure 7 is a sequence diagram showing the operation of the examination data processing system and the electronic medical record system according to the second embodiment. In the process shown in Figure 7, the difference from the first embodiment is that when the CPU 12 in the examination data processing system 10 displays the medical information of one patient corresponding to the patient ID included in the document data on the user terminals 40A and 40B in S5, if the medical information of another patient is already displayed, it closes the medical information of the other patient and switches to displaying the medical information of the one patient.

[0080] Specifically, when document data is moved to the editing folder in S4, CPU 12 determines whether the medical information of other patients is already displayed on user terminals 40A and 40B (S4a). If it is not displayed, the process proceeds directly to S5. If it is displayed, CPU 12 closes the medical information of other patients (S4b) and then proceeds to S5. Note that the other processes are the same as in Figure 2, so the explanation is omitted.

[0081] Thus, in the examination data processing program and examination data processing system according to the second embodiment, when medical information for another patient is already displayed, and document data corresponding to one patient is downloaded, the system switches to a state where the medical information for one patient is displayed. This synchronizes the document data to be edited with the displayed medical information, preventing the document data from containing information for a different patient.

[0082] <Third Embodiment> A third embodiment of the inspection data processing program and inspection data processing system will be described with reference to Figure 8. In the third embodiment, explanations that overlap with the above embodiments will be omitted.

[0083] Figure 8 is a sequence diagram showing the operation of the examination data processing system and the electronic medical record system according to the second embodiment. In the processing shown in Figure 8, the difference from the first embodiment is that when the CPU 12 in the examination data processing system 10 performs the processing from S6 to S9 while displaying the medical information of one patient corresponding to the patient ID included in the document data on the user terminals 40A and 40B in S5, the medical information of other patients is not displayed.

[0084] Specifically, in S5, when the medical information of one patient corresponding to the patient ID included in the document data is displayed on user terminals 40A and 40B, the CPU 12 enters a locked state where it does not accept access information for the medical information of other patients (S5a). Processing in S6 to S9 is executed while in this locked state. In S9, when editing of the document data is completed, the CPU 12 releases the lock on access information for the medical information of other patients that was set in S5a (S9a). Note that the other processing is the same as in Figure 2, so the explanation is omitted.

[0085] Thus, in the examination data processing program and examination data processing system according to the third embodiment, when an editing screen for document data associated with one patient is displayed, medical information of other patients is not displayed. This prevents the document data being edited and the displayed medical information from relating to different patients, thus preventing the document data from containing information of a different patient.

[0086] <Fourth Embodiment> A test data processing program and a test data processing system according to the fourth embodiment will be described. In the fourth embodiment, descriptions that overlap with the above embodiments will be omitted.

[0087] In the fourth embodiment of the examination data processing system and electronic medical record system, the difference from the first embodiment is that when the CPU 12 in the examination data processing system 10 performs the processing in S6 to S9 while displaying the medical information of one patient corresponding to the patient ID included in the document data on the user terminals 40A and 40B in S5, if an instruction is given to display the medical information of another patient, the CPU 12 terminates editing the document data and saves it.

[0088] Specifically, in the sequence diagram in Figure 2, in S5, the medical information of one patient corresponding to the patient ID included in the document data is displayed on user terminals 40A and 40B, and then the processes S6 to S9 are executed. However, if access information for another patient's medical information is entered at any point during S6 to S9, the CPU 12 interrupts the editing of the document data at that point, regardless of whether the editing of the document data is complete, and executes the processes from S9 onwards. Then, the CPU 12 displays the medical information of the other patient on user terminals 40A and 40B according to the entered access information.

[0089] Furthermore, if the editing process is interrupted before the editing of the document data is completed and processing from S9 onwards is executed, it is desirable that the examination data processing system 10 remember that the document file was updated to the electronic medical record system 20 in an incomplete (under editing) state, and that the CPU 12 displays on user terminals 40A and 40B that the document data is incomplete (under editing) so that the user can recognize this when the same document file (a document file with the same patient ID and the same type ID, or, if document files are managed by ID, a document file with the same unique document ID) is downloaded and moved to the editing folder. For example, when the document data is displayed in the editing software, it is desirable to display a note such as "Under Editing" or "Editing Incomplete" after the file name displayed in the file header.

[0090] Thus, in the examination data processing program and examination data processing system according to the fourth embodiment, when an editing screen for document data associated with one patient is displayed, if medical information for another patient is displayed, the editing of the document data is terminated and saved. This prevents the document data being edited and the displayed medical information from relating to different patients, and prevents the document data from containing information for a different patient. [Explanation of Symbols]

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

Claims

1. A test data processing program executed by a test data processing system that processes medical information including test data showing test results for a patient, A document data monitoring process that monitors whether a predetermined operation has been performed on document data that is subject to editing and managed by an electronic medical record system that records patients' clinical information, When the predetermined operation on the document data is detected, an extraction process is performed to extract the patient's medical information based on the patient's identification information associated with the document data. An insertion process for inserting the extracted medical information into the document data, A saving process that saves the edited document data as document data managed by the electronic medical record system, An inspection data processing program characterized by causing the computer of the inspection data processing system to execute it.

2. The inspection data program according to claim 1, When the predetermined operation on the document data is detected, an editing display process is performed to display the editing screen for the document data, An inspection data processing program characterized by causing the computer of the inspection data processing system to execute it.

3. A test data processing program according to claim 1 or 2, When the predetermined operation on the document data is detected, a medical information display process is performed to display the patient's medical information based on the patient's identification information. An inspection data processing program characterized by causing the computer of the inspection data processing system to execute it.

4. A test data processing program according to claim 3, The medical information display process displays the medical information related to the type of document data according to the type of document data. A test data processing program characterized by the following features.

5. A test data processing program according to claim 1 or 2, The extraction process extracts the medical information related to the type of document data according to the type of document data. A test data processing program characterized by the following features.

6. A test data processing program according to claim 1 or 2, The insertion process detects a predetermined string of characters contained within the document data and inserts the medical information that has been pre-associated with that string of characters. A test data processing program characterized by the following features.

7. A test data processing program according to claim 3, The medical information display process, when medical information for another patient is already displayed, switches from a state where the medical information for the other patient is displayed to a state where the medical information for the one patient is displayed when the document data monitoring process detects a predetermined operation on the document data associated with a patient different from the other patient. A test data processing program characterized by the following features.

8. A test data processing program according to claim 3, The medical information display process, when it detects a predetermined operation on the document data associated with a particular patient, prevents the display of medical information for a patient other than the one associated with that patient. A test data processing program characterized by the following features.

9. A test data processing program according to claim 3, When the predetermined operation on the document data is detected, the computer of the inspection data processing system is instructed to execute an editing display process that displays the editing screen for the document data. The aforementioned saving process, when displaying the editing screen for the document data associated with a particular patient, terminates editing and saves the document data if medical information for a patient other than the first patient is displayed. A test data processing program characterized by the following features.

10. A test data processing system that processes medical information including test data showing test results for patients, A document data monitoring processing unit monitors whether a predetermined operation has been performed on document data to be edited, which is managed by an electronic medical record system that records patient clinical information. When the predetermined operation on the document data is detected, an extraction processing unit extracts the patient's medical information based on the patient's identification information associated with the document data. An insertion processing unit that inserts the extracted medical information into the document data, A storage processing unit that saves the edited document data as document data managed by the electronic medical record system, A test data processing system characterized by comprising the following features.

Images