Information processing device, information processing method, information processing program

Abstract

This information processing device comprises at least one processor. The processor: acquires a medical document to which treatment department information that indicates a treatment department of a creator and date information that indicates the creation date are granted; and generates list information in which information pertaining to the medical document is recorded in a format in which an identification name of the treatment department is represented in a first axis and a date is represented in a second axis, which crosses the first axis.

Description

Information processing device, information processing method, and information processing program

[0001] The disclosed technology relates to an information processing device, an information processing method, and an information processing program.

[0002] The following technology is known as a technology for facilitating understanding of a patient's medical treatment status. For example, Japanese Patent Application Laid-Open No. 2020-4244 describes a medical support device that includes a display screen generation unit that generates a display screen for multiple patients, which displays patient identification information and medical treatment processes in association with each other, and an unread management unit that displays a status on the display screen that indicates whether the medical treatment process is unread, read, or includes both of these pieces of information. The display screen generation unit generates a timeline display screen that displays the medical treatment process for a specific patient in chronological order, and the unread management unit displays the status of the medical treatment process on the timeline display screen.

[0003] Medical documents such as radiology reports and electronic medical records are created or updated daily. Being able to check the information contained in these medical documents at a glance would be convenient, as it would allow for a bird's-eye view of the patient's condition. In particular, when a patient visits multiple medical departments, a system that allows for a bird's-eye view of the information for each department is desirable.

[0004] The disclosed technology aims to enable an overview of information regarding medical documents created by multiple medical departments.

[0005] The information processing device according to the disclosed technology includes at least one processor. The processor acquires medical documents to which department information indicating the department that created them and date information indicating the date they were created are assigned. The processor generates list information that records information about the corresponding medical documents in a format that has the identification name of the department on a first axis and the date on a second axis that intersects with the first axis.

[0006] The disclosed technology makes it possible to obtain an overview of information regarding medical documents created by multiple medical departments.

[0007] 1 is a diagram showing an example of the configuration of a medical information management system according to an embodiment of the disclosed technology. FIG. 2 is a diagram showing an example of the hardware configuration of an information processing server according to an embodiment of the disclosed technology. FIG. 3 is a functional block diagram showing an example of the functional configuration of an information processing server according to an embodiment of the disclosed technology. FIG. 4 is a flowchart showing an example of the flow of processing performed by a CPU according to an embodiment of the disclosed technology executing an information processing program. FIG. 5 is a functional block diagram showing an example of the functional configuration of an information processing server according to an embodiment of the disclosed technology. FIG. 6 is a flowchart showing an example of the flow of processing performed by a CPU according to an embodiment of the disclosed technology executing an information processing program. FIG. 7 is a diagram showing an example of the flow of processing performed by a CPU according to an embodiment of the disclosed technology executing an information processing program. FIG. 8 is a diagram showing an example of the list information according to an embodiment of the disclosed technology.

[0008] An example of an embodiment of the present invention will be described below with reference to the drawings. In the drawings, the same or equivalent components and parts are designated by the same reference numerals, and redundant description will be omitted.

[0009] 1 is a diagram illustrating an example of the configuration of a medical information management system 1 according to an embodiment of the disclosed technology. The medical information management system 1 includes an information processing server 10, a report server 20, an electronic medical record server 30, and a user terminal device 40.

[0010] The report server 20 is a server computer equipped with a storage medium on which medical documents such as an image interpretation report 21 and an examination report 22 are stored. The image interpretation report 21 contains information about diseases extracted from medical images such as plain X-ray images, CT images, mammography images, and MRI images. The examination report 22 contains information about the results of examinations performed on tissues or organs collected from a patient. The image interpretation report 21 and the examination report 22 are created for each patient. In some cases, multiple image interpretation reports 21 and multiple examination reports 22 are created for a single patient. In some cases, multiple different medical departments create image interpretation reports 21 and examination reports 22 for a single patient. The image interpretation report 21 and the examination report 22 are created for each medical department.

[0011] The radiology report 21 and the examination report 22 are each assigned a patient ID (identification) for identifying the patient, department information for identifying the department that prepared the report, and date information indicating the date the report was prepared. When the radiology report 21 and the examination report 22 are not distinguished from each other or are referred to collectively, they will be simply referred to as "report 23" below. The report 23 is an example of a "medical document" in the disclosed technology.

[0012] The electronic medical record server 30 is a server computer equipped with a storage medium that stores an electronic medical record 31 created for each patient. The electronic medical record 31 contains information about treatment for the patient's illness or information about the progress of the patient's illness. "Information about treatment" includes, for example, subjective information about the illness, objective information, assessment, plan, medication status, test results, test orders, etc.

[0013] The doctor creating the electronic medical record 31 uses a registration system (not shown) to register the illness described in the report 23 as an illness that should be treated for the patient. The registered illness is recorded in the electronic medical record 31 through system integration. The electronic medical record 31 is updated daily. In some cases, electronic medical records 31 are created for a single patient by multiple different medical departments. An electronic medical record 31 is created for each medical department.

[0014] The electronic medical record 31 is assigned a patient ID (identification) for identifying the patient, department information for identifying the department that created the electronic medical record 31, and date information indicating the date on which the electronic medical record 31 was created. The electronic medical record 31 is an example of a "medical document" in the disclosed technology.

[0015] The information processing server 10 generates list information 200 (see FIG. 4 ) that aggregates information related to the reports 23 and electronic medical records 31 for a specific patient designated by the user terminal device 40. Details of the list information 200 will be described later. The information processing server 10 is an example of an "information processing device" in the disclosed technology.

[0016] The user terminal device 40 is a computer that is expected to be used by a doctor. The user terminal device 40 requests the information processing server 10 to present list information 200 for a specific patient. The target patient is specified by the user terminal device 40. In response to the request from the user terminal device 40, the information processing server 10 generates list information 200 for the specified patient and transmits this to the user terminal device 40. The list information 200 transmitted from the information processing server 10 is displayed on a display (not shown) of the user terminal device 40 that has received the list information 200.

[0017] 2 is a diagram showing an example of the hardware configuration of the information processing server 10. The information processing server 10 includes a CPU (Central Processing Unit) 101, a RAM (Random Access Memory) 102, a non-volatile memory 103, an input device 104, a display 105, and a network interface 106. These pieces of hardware are connected to a bus 107.

[0018] The display 105 is, for example, a liquid crystal display or an LED (Light Emitting Diode) display. The input device 104 includes, for example, a keyboard and a mouse, and may also include a proximity input device such as a touch panel display, a voice input device such as a microphone, or a non-contact input device such as a camera or sensor. The network interface 106 is an interface for connecting the information processing server 10 to the report server 20, the electronic medical record server 30, and the user terminal device 40 via a network.

[0019] The nonvolatile memory 103 is a nonvolatile storage medium such as a hard disk or flash memory. An information processing program 110 is stored in the nonvolatile memory 103. The RAM 102 is a work memory for the CPU 101 to execute processing. The CPU 101 loads the information processing program 110 stored in the nonvolatile memory 103 into the RAM 102 and executes processing in accordance with the information processing program 110. The CPU 101 is an example of a "processor" in the disclosed technology.

[0020] 3 is a functional block diagram showing an example of the functional configuration of the information processing server 10. The information processing server 10 has a report acquisition unit 11, an electronic medical record acquisition unit 12, and a list information generation unit 13. When the CPU 101 executes the information processing program 110, the CPU 101 functions as the report acquisition unit 11, the electronic medical record acquisition unit 12, and the list information generation unit 13.

[0021] The report acquisition unit 11 accesses the report server 20 and acquires reports 23 related to a specific patient from among those stored in a storage medium provided in the report server 20. The specific patient is specified by the user terminal device 40. A patient ID is assigned to the radiology report 21 and the examination report 22. The report acquisition unit 11 sends a report acquisition request including the patient ID to the report server 20. The report server 20 extracts reports 23 stored in its storage medium that have been assigned the patient ID related to the acquisition request, and sends them to the information processing server 10. The report acquisition unit 11 acquires the reports 23 sent from the report server 20. Note that if reports 23 for one patient have been created in multiple different medical departments, all of the reports 23 created by each of the multiple medical departments are acquired.

[0022] The report server 20 may be provided with a report database (not shown) that associates patient IDs with identification information (report IDs) of the radiology reports 21 and the examination reports 22. In this case, the report server 20 may extract the reports 23 related to a specific patient using the report database.

[0023] The electronic medical record acquisition unit 12 accesses the electronic medical record server 30 and acquires electronic medical records 31 related to a specific patient from among the electronic medical records 31 stored in a storage medium provided in the electronic medical record server 30. A patient ID is assigned to each electronic medical record 31. The electronic medical record acquisition unit 12 sends an electronic medical record acquisition request including the patient ID to the electronic medical record server 30. The electronic medical record server 30 extracts, from the electronic medical records 31 stored in its own storage medium, the electronic medical record 31 to which the patient ID related to the acquisition request is assigned, and sends this to the information processing server 10. The electronic medical record acquisition unit 12 acquires the electronic medical records 31 sent from the electronic medical record server 30. Note that if electronic medical records 31 have been created for one patient in multiple medical departments, all of the electronic medical records 31 created by each of the multiple medical departments are acquired.

[0024] The electronic medical record server 30 may be provided with an electronic medical record database (not shown) that associates patient IDs with identification information (electronic medical record IDs) of the electronic medical records 31. In this case, the electronic medical record server 30 may use the electronic medical record database to extract the electronic medical records 31 related to a specific patient.

[0025] The list information generation unit 13 generates list information 200 that is edited so that the information contained in the report 23 acquired by the report acquisition unit 11 and the electronic medical record 31 acquired by the electronic medical record acquisition unit 12 can be viewed at a bird's-eye view.

[0026] 4 is a diagram showing an example of list information 200 generated by the list information generating unit 13. The list information 200 is a matrix format in which the first axis (horizontal axis) represents the identification name of the medical department and the second axis (vertical axis) intersecting the first axis represents the date, and information written in the corresponding report 23 and electronic medical record 31 is recorded.

[0027] The list information generator 13 identifies the record fields in the format for the information contained in the reports 23 acquired by the report acquisition unit 11 and the electronic medical record 31 acquired by the electronic medical record acquisition unit 12 based on the department information and date information provided in each of these medical documents, and records the information corresponding to the identified record fields. This generates list information 200, in which information contained in medical documents created by each of multiple departments for a specific patient is presented in chronological order for each department. In the example list information 200 shown in FIG. 4 , information contained in reports 23 or electronic medical records 31 created by the internal medicine, thoracic surgery, and orthopedic surgery departments is presented in chronological order for each department. The user may be allowed to specify the departments whose information is presented in the list information 200. In this case, the list information generator 13 generates list information 200, in which the corresponding information is recorded in a format that uses the identification name of the department specified on the first axis.

[0028] In this embodiment, the list information generation unit 13 generates a summary of the information described in the report 23 or electronic medical record 31 and records the generated summary in the corresponding record field of the format. The information can be summarized using existing natural language analysis technology. The list information generation unit 13 transmits the generated list information 200 to the user terminal device 40. The list information 200 is displayed on the display of the user terminal device 40 that has received the list information 200.

[0029] Because the information presented in the list information 200 is a summary of the information contained in the report 23 or electronic medical record 31, the user may wish to confirm the details of the information contained in the report 23 or electronic medical record 31. The list information generating unit 13 presents the details of the information contained in the report 23 or electronic medical record 31 in response to a request from the user terminal device 40. For example, the user can request the details of the information contained in the cell from the information processing server 100 by clicking on any cell containing summary information in the list information 200 displayed on the display of the user terminal device 40. Upon receiving this request, the information processing server 100 transmits details (detailed information) of the information contained in the requested report 23 or electronic medical record 31 to the user terminal device 40. The detailed information may be, for example, the original text of the report 23 or electronic medical record 31. The detailed information transmitted from the information processing server 100 is displayed on the display of the user terminal device 40. The detailed information may be displayed together with the list information 200 in the form of a mouse-over pop-up.

[0030] 5 is a flowchart showing an example of the flow of processing performed by the CPU 101 when the CPU 101 executes the information processing program 110. The information processing program 110 is executed, for example, when a request for presentation of the list information 200 is received from the user terminal device 40.

[0031] In step S1, the report acquisition unit 11 accesses the report server 20 and acquires reports 23 related to a specific patient from among the reports 23 stored in a storage medium provided in the report server 20. Specifically, the report acquisition unit 11 transmits a report acquisition request including a patient ID to the report server 20. The report server 20 extracts reports 23 stored in its own storage medium that have the patient ID related to the acquisition request assigned to them, and transmits them to the information processing server 10. The report acquisition unit 11 acquires the reports 23 transmitted from the report server 20. If reports 23 have been created in multiple different medical departments for the patient related to the acquisition request, all of the reports 23 created for the patient by each of the multiple medical departments are acquired.

[0032] In step S2, the electronic medical record acquisition unit 12 accesses the electronic medical record server 30 and acquires electronic medical records 31 related to a specific patient from among the electronic medical records 31 stored in the storage medium of the electronic medical record server 30. Specifically, the electronic medical record acquisition unit 12 sends an electronic medical record acquisition request including a patient ID to the electronic medical record server 30. The electronic medical record server 30 extracts the electronic medical records 31 stored in its storage medium that are assigned the patient ID related to the acquisition request and sends them to the information processing server 10. The electronic medical record acquisition unit 12 acquires the electronic medical records 31 sent from the electronic medical record server 30. If electronic medical records 31 have been created in multiple different medical departments for the patient related to the acquisition request, all electronic medical records 31 created for that patient by each of the multiple medical departments are acquired. Note that, although an example has been given of the case where the electronic medical records 31 are acquired after the report 23 has been acquired, this is not limited to this. The report 23 may be acquired after the electronic medical record 31 is acquired, or the report 23 and the electronic medical record 31 may be acquired in parallel.

[0033] In step S3, the list information generator 13 records summaries of the information contained in the report 23 obtained in step S1 and the electronic medical record 31 obtained in step S2 in a matrix format with the identification name of the medical department on the first axis (horizontal axis) and the date on the second axis (vertical axis) intersecting the first axis. The list information generator 13 identifies recording fields within the format for the information contained in these medical documents based on the medical department information and date information provided to the report 23 and the electronic medical record 31, respectively, and records the information corresponding to the identified recording fields. This generates list information 200 in which the information contained in medical documents created by each of multiple medical departments for a specific patient is presented in chronological order for each medical department.

[0034] In step S4, the list information generating unit 13 transmits the list information 200 generated in step S3 to the user terminal device 40. Upon receiving the list information 200, the list information 200 is displayed on the display 41 of the user terminal device 40.

[0035] Since the information presented in the list information 200 is a summary of the text written in the report 23 or the electronic medical record 31, the user may wish to check the details of the information written in the report 23 or the electronic medical record 31. For example, the user can click on any cell in the list information 200 displayed on the display of the user terminal device 40, in which summary information is written, to request the information processing server 100 for details of the information written in that cell.

[0036] In step S5, the list information generator 13 determines whether there is a request for presentation of details (detailed information) of the information presented in the list information 200. If it is determined that there is a request for presentation of detailed information, the process proceeds to step S6. On the other hand, if it is determined that there is no request for presentation of detailed information, this routine ends.

[0037] In step S6, the list information generating unit 13 transmits details (detailed information) of the information described in the requested report 23 or electronic medical record 31 to the user terminal device 40. The detailed information transmitted from the information processing server 100 is displayed on the display of the user terminal device 40.

[0038] As described above, the information processing server 100 according to this embodiment acquires medical documents (reports 23 and electronic medical records 31) that are assigned department information indicating the department that created them and date information indicating the date they were created. The information processing server 100 generates list information 200 that records information contained in the corresponding medical documents in a format in which the identification name of the department is represented on the first axis and the date is represented on the second axis that intersects with the first axis. The information processing server 100 according to this embodiment generates list information 200 that presents information contained in medical documents created by multiple departments for a specific patient in chronological order, organized by department. This allows for an overview of the information contained in medical documents created by multiple departments for a specific patient.

[0039] [Second Embodiment] A doctor belonging to a certain medical department (hereinafter referred to as the first medical department) may request another medical department (hereinafter referred to as the second medical department) to handle findings discovered during an examination, etc. In this case, the electronic medical records 31 of the first medical department and the second medical department may contain cross-department response information indicating matters that should be handled by the second medical department. Therefore, the cross-department response information may also be recorded in the list information 200. In order to prevent the cross-department response information from being overlooked, the information processing server 100 according to this embodiment presents the cross-department response information in the list information 200 in a format different from other information.

[0040] 6 is a functional block diagram showing an example of the functional configuration of the information processing server 100 according to the second embodiment. The information processing server 100 according to the second embodiment differs from the information processing server 100 according to the first embodiment in that the information processing server 100 according to the second embodiment includes an analysis unit 14.

[0041] The analysis unit 14 extracts information about other departments being handled from the electronic medical record 31 by performing text analysis on the electronic medical record 31 acquired by the electronic medical record acquisition unit 12. The information about other departments being handled from the electronic medical record 31 is given a display label such as [Other Department Handled] that clearly indicates that the information is information about other departments being handled. The analysis unit 14 extracts information about other departments being handled from the electronic medical record 31 based on such a display label. Note that information about other departments being handled may also be extracted based on a portion of the electronic medical record 31 other than the display label that indicates that a request for assistance from another department is being made.

[0042] The list information generator 13 generates list information including the other-department correspondence information extracted by the analyzer 14. In the example of the list information 200 shown in FIG. 4 , the other-department correspondence information 201 requested by the internal medicine department, "chest CT," is listed in a column corresponding to the internal medicine department that made the request and a column corresponding to the respiratory surgery department that received the request. The list information generator 13 presents the other-department correspondence information 201 in the list information 200 in a format different from other information by highlighting it, for example. For example, if the first electronic medical record of a first medical department contains other-department correspondence information introducing a second medical department, the other-department correspondence information may be displayed for both the first medical department and the second medical department. In this case, the other-department correspondence information in the column for the first medical department associated with the first electronic medical record and the other-company correspondence information in the column for the second medical department not associated with the first electronic medical record may be displayed in different ways. Note that different display modes refer to changing the saturation, brightness, luminance, or pattern of cells, characters, or character backgrounds, or adding boxes or underlines to make them visually distinguishable. In this way, it is easy to identify the department that actually filled out the first electronic medical record and the departments listed in the first electronic medical record of other departments. Furthermore, the display mode of the other-department correspondence information of the first electronic medical record may be changed depending on whether a diagnosis for the disease listed in the first electronic medical record was made in a second electronic medical record in which the second department was associated after the first electronic medical record. For example, the information processing server 10 stores a corresponding department table that indicates the corresponding department information for each disease. The information processing server 10 extracts diseases listed in each electronic medical record 31 and determines whether the extracted disease corresponds to the department corresponding to the electronic medical record 31 based on the corresponding department table. Therefore, descriptions of diseases in other departments other than the department corresponding to the electronic medical record 31 from which the disease was extracted are displayed as other-department correspondence information in the other department column to which the other-department disease is associated in the corresponding department table. Thereafter, when a description of a disease of another department is extracted from the electronic medical record 31 to which the other department is associated, the display mode of the information associated with the other department is made different from the display mode before the extraction.In this way, it is possible to determine whether a disease found in a department other than the one that handles the disease has been appropriately treated in the department that handles the disease.

[0043] 7 is a flowchart showing an example of the flow of processing performed by the CPU 101 according to this embodiment by executing the information processing program 110. This flowchart has step S2A added to the flowchart shown in FIG. 5. Only steps that are different from the flowchart shown in FIG. 5 will be described below, and descriptions of other steps will be omitted.

[0044] In step S2A, the analysis unit 14 performs an extraction process for each medical department to extract information corresponding to other departments written in the electronic medical record 31 by performing text analysis on the electronic medical record 31 acquired in step S2.

[0045] In step S3, the list information generating unit 13 generates list information 200 including the other department correspondence information extracted in step S2A. In the list information 200, the list information generating unit 13 presents the other department correspondence information 201 in a form different from other information by highlighting or otherwise emphasizing the other department correspondence information 201.

[0046] According to the information processing server 100 of this embodiment, the other department correspondence information 201 is presented in a form different from other information in the list information 200, so that the other department correspondence information 201 can be prevented from being overlooked.

[0047] [Third Embodiment] In an examination performed by a certain medical department (hereinafter referred to as the first medical department), a lesion other than the target lesion may be discovered. Findings related to such a lesion are called incidental findings. Incidental findings discovered by the first medical department may be recorded in the report 23 created by the first medical department, but may not be recorded in the electronic medical record 31. Findings not recorded in the electronic medical record 31 may be left untreated without appropriate treatment. Therefore, the information processing server 100 according to this embodiment records information about incidental findings in the list information 200 to prevent incidental findings from being overlooked.

[0048] In the information processing server 100 according to this embodiment, the analysis unit 14 performs extraction processing for each medical department to extract, as incidental findings, findings that are recorded in the report 23 but not in the electronic medical record 31. The analysis unit 14 further identifies the medical department that should be responsible for the extracted incidental finding. For example, the analysis unit 14 identifies the medical department that should be responsible for the incidental finding based on a portion of the report 23 that includes a description of the incidental finding, which describes the site of occurrence or the diagnosis of the incidental finding. The analysis unit 14 may identify the responsible medical department using a table that associates the site of occurrence or the diagnosis of the incidental finding with the medical department that should be responsible for the incidental finding.

[0049] The list information generation unit 13 generates list information 200 including information about the incidental findings extracted by the analysis unit 14. Specifically, the list information generation unit 13 records the information about the incidental findings extracted by text analysis of the medical document created in the first medical department in a column corresponding to the first medical department in the format of the list information 200, and also records the information in a column corresponding to the second medical department identified by the analysis unit 14 as being responsible for the incidental finding. In the list information 200 illustrated in FIG. 4 , the incidental finding 202, "rib fracture," discovered in the thoracic surgery department is entered in the column corresponding to the thoracic surgery department and the column corresponding to the orthopedic surgery department in the format of the list information 200. The orthopedic surgery department is the medical department responsible for the "rib fracture" incidental finding 202.

[0050] The list information generator 13 highlights or otherwise emphasizes information about incidental findings recorded in a field corresponding to a first medical department in the format (hereinafter referred to as first incidental finding information) and information about incidental findings recorded in a field corresponding to a second medical department in the format (hereinafter referred to as second incidental finding information), thereby presenting them in a form different from other information in the list information 200. The list information generator 13 may present the first incidental finding information and the second incidental finding information in different forms. For example, the first incidental finding information and the second incidental finding information may have different text, cell colors, or background colors.

[0051] Fig. 8 is a flowchart showing an example of the flow of processing performed by the CPU 101 according to this embodiment by executing the information processing program 110. This flowchart has steps S2B and S2C added to the flowchart shown in Fig. 5. Only the steps that are different from the flowchart shown in Fig. 5 will be described below, and descriptions of the other steps will be omitted.

[0052] In step S2B, the analysis unit 14 performs text analysis on the report 23 obtained in step S1 and the electronic medical record 31 obtained in step S2, and performs an extraction process for each medical department to extract findings described in the report 23 that are not recorded in the electronic medical record 31 as incidental findings.

[0053] In step S2C, the analysis unit 14 identifies the department that should be in charge of the incidental finding extracted in step S2B.

[0054] In step S3, the list information generator 13 generates list information 200 including information about the incidental findings extracted in step S2B. Specifically, the list information generator 13 records information about the incidental findings extracted by text analysis of the medical document created by the first medical department in a column of the format corresponding to the first medical department, and also records information about the incidental findings in a column of the format corresponding to the second medical department identified in step S2C that should be responsible for the incidental findings. The list information generator 13 highlights the first incidental finding information recorded in the column of the format corresponding to the first medical department and the second incidental finding information recorded in the column of the format corresponding to the second medical department, thereby presenting them in a form different from other information in the list information 200. The list information generator 13 presents the first incidental finding information and the second incidental finding information in different forms.

[0055] According to the information processing server 100 of this embodiment, information regarding incidental findings extracted by text analysis of medical documents created in a first medical department is recorded in a column corresponding to the first medical department and a column corresponding to the second medical department that should be responsible for the incidental finding in the format of the list information 200, thereby preventing incidental findings from being overlooked.

[0056] [Fourth embodiment]

[0057] FIG. 9 is a diagram illustrating an example of list information 200A generated by the information processing server 100 according to the fourth embodiment of the disclosed technology.

[0058] The list information generation unit 13 in this embodiment generates list information 200A in a matrix format with the identification name of the medical department on the first axis (vertical axis) and the date on the second axis (horizontal axis) that intersects the first axis, and records markers 210 corresponding to the report 23 and the electronic medical record 31.

[0059] The list information generator 13 identifies the recording position of the marker 210 within the format based on the medical department information and date information assigned to the report 23 acquired by the report acquisition unit 11 and the electronic medical record 31 acquired by the electronic medical record acquisition unit 12, and records the marker 210 at the identified recording position. This generates list information 200A that presents, in chronological order, the creation or update of medical documents for a specific patient for each medical department.

[0060] In the list information 200A, two markers 210 corresponding to two medical documents that were created or updated by different medical departments and that contain common cross-department correspondence information are connected by a line segment. That is, a marker 210A corresponding to a medical document that was created by a first medical department and contains cross-department correspondence information indicating matters that should be addressed by a second medical department is connected by a line segment to a marker 210B corresponding to a medical document that was created by the second medical department and contains the same cross-department correspondence information as the above-mentioned cross-department correspondence information.

[0061] The list information 200A according to this embodiment allows users to check information about medical documents created by multiple medical departments at a high level. Furthermore, the time of creation or update of a medical document is indicated by a marker 210, making it easy to understand the interval between creation or update of a medical document. Furthermore, it is easy to identify medical documents that contain the same cross-department correspondence information. Furthermore, it is possible to visualize the state of collaboration between multiple medical departments.

[0062] The list information 200A may limit the medical documents to which the marker 210 is recorded. For example, the list information 200A may record the marker 210 only for medical documents that include information about a specific disease.

[0063] In each of the above embodiments, the following various processors can be used as the hardware structure of the processing units that perform various processes, such as the report acquisition unit 11, electronic medical record acquisition unit 12, list information generation unit 13, and analysis unit 14. As described above, the various processors include CPUs and GPUs, which are general-purpose processors that execute software (programs) and function as various processing units, as well as dedicated electrical circuits, such as programmable logic devices (PLDs) that are processors whose circuit configuration can be changed after manufacture, such as FPGAs, and application-specific integrated circuits (ASICs), which are processors with a circuit configuration designed specifically to perform specific processes.

[0064] A single processing unit may be configured with one of these various processors, or may be configured with a combination of two or more processors of the same or different types (for example, a combination of multiple FPGAs, or a combination of a CPU and an FPGA). Also, multiple processing units may be configured with a single processor.

[0065] Examples of configuring multiple processing units with a single processor include: first, a form in which one processor is configured with a combination of one or more CPUs and software, and this processor functions as multiple processing units, as typified by computers such as client and server; second, a form in which a processor is used to realize the functions of an entire system including multiple processing units with a single IC (Integrated Circuit) chip, as typified by systems on chips (SoCs); thus, various processing units are configured using one or more of the above-mentioned various processors as a hardware structure.

[0066] Furthermore, more specifically, the hardware structure of these various processors can be an electric circuit that combines circuit elements such as semiconductor elements.

[0067] Furthermore, in the above embodiment, the information processing program 110 is described as being pre-stored (installed) in the non-volatile memory 103, but this is not limiting. The information processing program 110 may be provided in a form recorded on a recording medium such as a CD-ROM (Compact Disc Read Only Memory), a DVD-ROM (Digital Versatile Disc Read Only Memory), or a USB (Universal Serial Bus) memory. The information processing program 110 may also be downloaded from an external device via a network. In other words, the program described in this embodiment (i.e., the program product) may be provided on a recording medium or may be distributed from an external computer.

[0068] The following supplementary note is further disclosed regarding the above first to fourth embodiments: (Supplementary note 1) An information processing device including at least one processor, wherein the processor acquires medical documents to which department information indicating the department that created the medical document and date information indicating the date of creation are attached, and generates list information that records information about the corresponding medical document in a format in which a first axis represents an identifier of the medical department and a second axis intersecting the first axis represents the date.

[0069] (Supplementary Note 2) The information processing device according to Supplementary Note 1, wherein the information related to the medical document is a summary of information contained in the medical document.

[0070] (Supplementary Note 3) The information processing device according to Supplementary Note 2, wherein the processor presents details of information contained in the medical document upon request.

[0071] (Appendix 4) The information processing device described in any one of Appendices 1 to 3, wherein the processor presents, in the list information, inter-department response information that is included in the medical document created in the first medical department and indicates matters that should be addressed in the second medical department, in a format that is different from other information.

[0072] (Supplementary Note 5) The information processing device according to Supplementary Note 4, wherein the processor extracts the other department correspondence information by text analysis of the medical document created in the first medical department.

[0073] (Supplementary Note 6) The information processing device described in any one of Supplementary Note 1 to Supplementary Note 5, wherein the processor records information regarding incidental findings extracted by text analysis of the medical document created in a first medical department in a column of the format corresponding to the first medical department and a column of the format corresponding to a second medical department that should be responsible for the incidental findings.

[0074] (Supplementary Note 7) The information processing device described in Supplementary Note 6, wherein the processor presents information regarding the incidental findings recorded in a field corresponding to the first medical department in the format and information regarding the incidental findings recorded in a field corresponding to the second medical department in the format in different formats in the list information.

[0075] (Supplementary Note 8) The information processing device according to Supplementary Note 1, wherein the processor generates the list information in which markers corresponding to the medical documents are recorded in the format.

[0076] (Appendix 9) The information processing device described in Appendix 8, wherein the processor generates the list information by connecting, with a line segment, a first marker corresponding to a medical document created in a first medical department and including interdepartmental correspondence information indicating matters that should be addressed in a second medical department, and a second marker corresponding to a medical document created in the second medical department and including information corresponding to the interdepartmental correspondence information.

[0077] (Supplementary Note 10) An information processing method performed by at least one processor included in an information processing device, which performs the following process: acquire medical documents to which department information indicating the department that created them and date information indicating the date they were created are assigned; and generate list information that records information about the corresponding medical documents in a format that has the identification name of the department on a first axis and the date on a second axis that intersects with the first axis.

[0078] (Appendix 11) An information processing program for causing at least one processor provided in an information processing device to execute the following process: acquire a medical document to which department information indicating the department that created it and date information indicating the date it was created are assigned; and generate list information that records information about the corresponding medical document in a format that has the identification name of the department on a first axis and the date on a second axis that intersects with the first axis.

[0079] The disclosure of Japanese Patent Application No. 2022-068442, filed on April 18, 2022, is incorporated herein by reference in its entirety. In addition, all documents, patent applications, and technical standards described herein are incorporated herein by reference to the same extent as if each individual document, patent application, and technical standard were specifically and individually indicated to be incorporated by reference.

Claims

1. An information processing device having at least one processor, which acquires medical documents to which department information indicating the department that created them and date information indicating the date they were created are attached, and generates list information that records information about the corresponding medical documents in a format that takes the identification name of the department on a first axis and the date on a second axis that intersects with the first axis.

2. The information processing device according to claim 1, wherein the information related to the medical document is a summary of the information contained in the medical document.

3. The information processing device according to claim 2, wherein the processor presents details of the information contained in the medical document upon request.

4. An information processing device as claimed in any one of claims 1 to 3, wherein the processor presents, in the list information, information on other departments that is included in the medical document created in the first department and indicates matters that should be addressed in the second department, in a form that is different from other information.

5. The information processing device according to claim 4, wherein the processor extracts the information related to other departments by text analysis of the medical document created in the first medical department.

6. An information processing device as claimed in any one of claims 1 to 3, wherein the processor records information relating to incidental findings extracted by text analysis of the medical document created in a first medical department in a column of the format corresponding to the first medical department and a column corresponding to a second medical department responsible for the incidental findings.

7. The information processing device described in claim 6, wherein the processor presents the information regarding the incidental findings recorded in the column corresponding to the first medical department in the format and the information regarding the incidental findings recorded in the column corresponding to the second medical department in the format in different forms in the list information.

8. The information processing device according to claim 1, wherein the processor generates the list information in which markers corresponding to the medical documents are recorded in the format.

9. The information processing device described in claim 8, wherein the processor generates the list information by connecting, with a line segment, a first marker corresponding to a medical document created in a first medical department and including interdepartmental correspondence information indicating matters that should be addressed in a second medical department, and a second marker corresponding to a medical document created in the second medical department and including information corresponding to the interdepartmental correspondence information.

10. An information processing method performed by at least one processor included in an information processing device, which performs the following process: acquires medical documents to which department information indicating the department that created them and date information indicating the date they were created; and generates list information that records information about the corresponding medical documents in a format that has the identification name of the department on the first axis and the date on the second axis that intersects with the first axis.

11. An information processing program for causing at least one processor provided in an information processing device to execute the following process: acquire medical documents to which department information indicating the department that created them and date information indicating the date they were created are assigned; and generate list information that records information about the corresponding medical documents in a format in which the identification name of the department is on the first axis and the date is on the second axis that intersects with the first axis.

Images