Medical data processing device, medical data processing method, and program

Abstract

To reduce the data size when transferring or storing the results of medical data analysis. [Solution] The medical data processing device according to the embodiment comprises an acquisition unit, an analysis unit, and a generation unit. The acquisition unit acquires medical data. The analysis unit analyzes the medical data and outputs the analysis results. The generation unit generates restoration process definition information that defines a process capable of restoring at least a part of the analysis results.

Description

Technical Field

[0001] The embodiments disclosed in this specification and the drawings relate to a medical data processing device, a medical data processing method, and a program.

Background Art

[0002] Conventionally, in the medical field, techniques for analyzing medical data such as medical image data have been known. In recent years, due to reasons such as higher image quality of medical image data to be captured, improvement in temporal resolution, and changes in imaging methods, the size of medical data to be analyzed has been increasing. Furthermore, due to such an increase in the size of medical data, the data size of the analysis results also increases.

[0003] For this reason, when transferring the analysis results to another device, the transfer time may increase, or the capacity of the storage device for storing the analysis results may be strained. Also, if the analysis results are deleted to reduce the data size to be stored, when the analysis results are needed again, the same analysis process will have to be repeated, which takes time.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] One of the problems to be solved by the embodiments disclosed in this specification and the drawings is to reduce the data size when transferring or storing the analysis results of medical data. However, the problems to be solved by the embodiments disclosed in this specification and the drawings are not limited to the above problems. The problems corresponding to the respective effects of each configuration shown in the embodiments described later can also be regarded as other problems.

Means for Solving the Problems

[0006] The medical data processing device according to the embodiment comprises an acquisition unit, an analysis unit, and a generation unit. The acquisition unit acquires medical data. The analysis unit analyzes the medical data and outputs the analysis results. The generation unit generates restoration process definition information that defines a process capable of restoring at least a portion of the analysis results. [Brief explanation of the drawing]

[0007] [Figure 1] Figure 1 shows an example of the overall configuration of the information processing system according to the first embodiment. [Figure 2] Figure 2 shows an example of data input and output in the analysis process according to the first embodiment. [Figure 3] Figure 3 shows an example of data input and output during the recovery process using the recovery executable file according to the first embodiment. [Figure 4] Figure 4 shows an example of replacing variables with fixed values ​​in the generation of a recovery executable file according to the first embodiment. [Figure 5] Figure 5 shows an example of deleting paths that will not be executed in the generation of a recovery executable file according to the first embodiment. [Figure 6] Figure 6 shows an example of conditional branching in the analysis process according to the first embodiment. [Figure 7] Figure 7 shows an example of a state where all execution paths except for a specific one have been removed from Figure 6. [Figure 8] Figure 8 shows an example of omitting intermediate processing in the generation of the recovery executable file according to the first embodiment. [Figure 9] Figure 9 shows an example of partial substitution of binary data according to the first embodiment. [Figure 10] Figure 10 is a sequence diagram showing an example of the processing flow including the analysis of medical image data and the generation of an executable file for restoration according to the first embodiment. [Figure 11] Figure 11 shows an example of analysis processing using the analysis function according to the second embodiment. [Figure 12] Figure 12 shows an example of the process defined in the recovery executable file corresponding to the process in Figure 11. [Figure 13] Figure 13 shows an example of the overall configuration of the information processing system according to the third embodiment. [Figure 14] Figure 14 shows an example of the overall configuration of the information processing system according to the fifth embodiment. [Figure 15] Figure 15 is a sequence diagram showing an example of the processing flow including the analysis of medical image data and the generation of an executable file for restoration according to the fifth embodiment. [Figure 16] Figure 16 is a sequence diagram showing an example of the processing flow including the analysis of medical image data and the generation of an executable file for restoration according to the sixth embodiment. [Modes for carrying out the invention]

[0008] The embodiments of the medical data processing device, medical data processing method, and program will be described in detail below with reference to the drawings.

[0009] (First Embodiment) Figure 1 shows an example of the overall configuration of an information processing system S according to the first embodiment. As shown in Figure 1, the information processing system S includes, for example, a medical data processing device 100 and an image storage device 200. The information processing system S is installed, for example, in a medical institution such as a hospital. The medical data processing device 100 and the image storage device 200 are connected to each other via a network N1, such as an in-hospital LAN (Local Area Network).

[0010] Furthermore, the medical data processing device 100 and the image storage device 200 may be connected via network N2 to communicate with an information processing terminal 300 located outside the medical institution where the medical data processing device 100 and the image storage device 200 are installed. Network N2 may be the Internet or the like, or it may be a private network connecting the medical data processing device 100 and the image storage device 200.

[0011] The information processing terminal 300 is, for example, a computer such as a PC (Personal Computer), a server, or a workstation used in other medical institutions. The information processing terminal 300 includes, for example, a processing circuit such as a processor, a storage circuit, a NW (network) interface, an input interface, and a display. Also, the processing circuit of the information processing terminal 300 in the present embodiment has a transmission function for transmitting data to the medical data processing device 100 and a reception function for receiving data. The information processing terminal 300 is an example of another information processing device in the present embodiment. Note that the information processing terminal 300 may also be included in the information processing system S.

[0012] The image storage device 200 is a device that stores medical image data obtained by imaging a subject. The image storage device 200 includes, for example, a processing circuit such as a processor, a storage circuit, a NW (network) interface, an input interface, and a display. More specifically, the image storage device 200 is, for example, a server device of a PACS (Picture Archiving and Communication System), and stores medical image data in a format compliant with DICOM (Digital Imaging and Communications IN Medicine). The medical image data is, for example, CT (Computed Tomography) image data, magnetic resonance image data, ultrasonic diagnostic image data, etc., but is not limited thereto. Also, the medical image data may be data with a large size, such as CT image data obtained by a dual-energy (Dual-energy) CT device. The medical image data is an example of the medical data in the present embodiment.

[0013] The medical data processing device 100 is, for example, a computer such as a PC, a server, or a workstation. The medical data processing device 100 is operated by a user such as a doctor.

[0014] The medical data processing device 100 acquires medical image data from the image storage device 200 and analyzes the acquired medical image data.

[0015] The medical data processing device 100 includes a NW interface 110, a memory circuit 120, an input interface 130, a display 140, and a processing circuit 150.

[0016] The NW interface 110 is connected to the processing circuit 150 and controls the transmission and communication of various data performed between the medical data processing device 100, the image storage device 200, and the information processing terminal 300. The NW interface 110 is realized by a network card, a network adapter, a NIC (Network Interface Controller), or the like.

[0017] The memory circuit 120 stores various information used by the processing circuit 150 in advance. The memory circuit 120 also stores various programs. The memory circuit 120 is a nonvolatile storage device such as an HDD (Hard disk Drive), an SSD (Solid State Drive), or an integrated circuit storage device that stores various information. In addition to HDDs and SSDs, the memory circuit 120 may also be a drive device that reads and writes various information to and from portable storage media such as CDs (Compact Discs), DVDs (Digital Versatile Discs), flash memories, and semiconductor memory elements such as RAMs (Random Access Memories). The memory circuit 120 is an example of a storage unit.

[0018] The input interface 130 is implemented by a mouse, keyboard, pen tablet (combining a stylus and tablet that accept user input), trackball, switch buttons, touchpad (for input operations by touching the operating surface), touchscreen (integrating a display screen and touchpad), non-contact input circuit using an optical sensor, and audio input circuit, etc. The input interface 130 may include multiple devices that accept user operations. The input interface 130 is connected to the processing circuit 150 and converts the input operations received from the user into electrical signals and outputs them to the processing circuit 150. In this specification, the input interface is not limited to those equipped with physical operating components such as a mouse or keyboard. For example, an electrical signal processing circuit that receives electrical signals corresponding to input operations from an external input device provided separately from the device and outputs these electrical signals to the processing circuit 150 is also included as an example of an input interface.

[0019] The display 140 displays various information under the control of the processing circuit 150. For example, the display 140 outputs a screen containing analysis results generated by the processing circuit 150, or a GUI (Graphical User Interface) for accepting various operations from the user. Specifically, the display 140 is an LCD display or a CRT (Cathode Ray Tube) display, etc. The input interface 130 and the display 140 may be integrated. For example, the input interface 130 and the display 140 may be implemented by a touch panel. The display 140 is an example of a display unit.

[0020] The processing circuit 150 is a processor that reads programs from the memory circuit 120 and executes them to realize functions corresponding to each program. The processing circuit 150 in this embodiment includes a reception function 151, an acquisition function 152, an analysis function 153, a generation function 154, a receiving function 155, a transmission function 156, and a display control function 157. The reception function 151 is an example of a reception unit. The acquisition function 152 is an example of an acquisition unit. The analysis function 153 is an example of an analysis unit. The generation function 154 is an example of a generation unit. The reception function 155 is an example of a reception unit. The transmission function 156 is an example of a transmission unit. The display control function 157 is an example of a display control unit.

[0021] Here, for example, the processing functions of the processing circuit 150, namely the reception function 151, acquisition function 152, analysis function 153, generation function 154, receiving function 155, transmission function 156, and display control function 157, are stored in the memory circuit 120 in the form of programs that can be executed by a computer. The processing circuit 150 is a processor. For example, the processing circuit 150 reads the programs from the memory circuit 120 and executes them to realize the functions corresponding to each program. In other words, the processing circuit 150 in the state in which each program has been read will have the functions shown in the processing circuit 150 of Figure 1. In Figure 1, the processing functions performed by the reception function 151, acquisition function 152, analysis function 153, generation function 154, receiving function 155, transmission function 156, and display control function 157 are realized by a single processor, but it is also possible to configure the processing circuit 150 by combining multiple independent processors, and each processor will realize the functions by executing a program. Furthermore, although Figure 1 describes a single memory circuit 120 that stores programs corresponding to each processing function, it is also possible to have multiple memory circuits distributed and the processing circuit 150 read the corresponding programs from individual memory circuits.

[0022] The above description illustrates an example in which a "processor" reads and executes programs corresponding to each function from a memory circuit, but the embodiments are not limited to this. The term "processor" refers to circuits such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an Application Specific Integrated Circuit (ASIC), and a programmable logic device (e.g., a Simple Programmable Logic Device (SPLD), a Complex Programmable Logic Device (CPLD), and a Field Programmable Gate Array (FPGA)). If the processor is a CPU, for example, it realizes its functions by reading and executing programs stored in a memory circuit. On the other hand, if the processor is an ASIC, instead of storing the program in the memory circuit 120, the function is directly incorporated as a logic circuit within the processor's circuit. In this embodiment, each processor is not limited to being configured as a single circuit; multiple independent circuits may be combined to form a single processor and realize its functions. Furthermore, the multiple components shown in Figure 1 may be integrated into a single processor to realize its functions.

[0023] The reception function 151 accepts various user operations via the input interface 130. For example, the reception function 151 accepts user operations to start the analysis process and input operations for various setting values ​​related to the analysis process.

[0024] The acquisition function 152 acquires medical image data from the image storage device 200. The acquired medical image data is, for example, medical image data designated by the user as the target of analysis.

[0025] The analysis function 153 analyzes the medical image data acquired by the acquisition function 152 and outputs the analysis results. The processing performed by the analysis function 153 is called the analysis process. Examples of analysis processes performed by the analysis function 153 include, but are not limited to, perfusion analysis, vascular analysis, cardiac analysis, and pulmonary function analysis. In this embodiment, perfusion analysis will be mainly described as an example. The medical data processing device 100 is equipped with an analysis function 153 that performs at least one type of analysis process, but may be equipped with multiple types of analysis functions.

[0026] The generation function 154 generates a recovery executable file that defines a process capable of recovering at least a portion of the analysis results of the analysis process performed by the analysis function 153. The recovery executable file is an example of the recovery process definition information in this embodiment. In this embodiment, being able to recover the analysis results means that even if the analysis result data is not available, data similar to the analysis results can be generated. In other words, even if the generated analysis results have been deleted, it is possible to generate data similar to the analysis results using the recovery executable file without having to perform the analysis process again.

[0027] More specifically, the recovery executable file is an executable file containing a program (hereinafter referred to as the recovery program) that performs the process of recovering the analysis results. The format of the recovery executable file is, for example, an exe file with the extension "exe". In addition to the recovery executable file, the recovery process definition information may also include a configuration file that the recovery executable file can read. The configuration file may contain, for example, fixed values ​​used in the process of recovering the analysis results. In this embodiment, the term "program" includes both text-format source code that requires compilation to be in a format that can be executed by a computer, and scripts that do not require compilation.

[0028] The generation function 154 may, for example, be a function that generates a restoration program using a rule-based application program. Alternatively, the generation function 154 may generate a restoration program using artificial intelligence (AI) such as a large language model (LLM).

[0029] Figure 2 shows an example of data input and output in the analysis process according to the first embodiment. The analysis function 153 performs perfusion analysis based on the medical image data 900 acquired by the acquisition function 152 and various setting values ​​entered by the user (for example, specification of a vascular region in the medical image data 900, or arbitrary constants related to the analysis process). The medical image data 900 input as the target of analysis is, for example, 3DCT image data containing 320 image data images with an image size of 512 pixels * 512 pixels for 20 phases.

[0030] For example, the analysis function 153 calculates the temporal change in CT value density from the medical image data 900. From the calculated temporal change in CT value density, it generates a perfusion image that maps an index representing the blood flow dynamics passing through capillaries in the tissue onto the tissue. Then, as the analysis result 800 of the perfusion analysis, the analysis function 153 outputs perfusion image data corresponding to the 320 image data contained in the medical image data 900, and 3D MAP data. For each MAP type, the analysis function 153 generates 320 perfusion images with an image size of 512 pixels * 512 pixels. In Figure 2, the number of MAP types is assumed to be 5 as an example. Also, the 3D MAP data generally has a data size of about 1 gigabyte. The perfusion image data and 3D MAP data are examples of analysis image data.

[0031] Furthermore, the analysis function 153 may also generate numerical data 810 and a report 820 related to the analysis results 800. Numerical data 810 is text data containing numerical values ​​such as the coordinates of the ROI (Region of Interest) set during the perfusion analysis, and various statistical values. Report 820 is, for example, an image interpretation report related to the analysis results 800 of the perfusion analysis. Numerical data 810 and report 820 are smaller in data size than the analysis results 800. For example, numerical data 810 is generally a few kilobytes, and report 820 is generally no larger than 1 megabyte. Note that the generation of numerical data 810 and report 820 by the analysis function 153 is not mandatory.

[0032] Furthermore, the generation function 154 generates a recovery executable file 700 in which a process capable of restoring the analysis results 800 is defined. In this embodiment, the generation function 154 generates the recovery executable file 700 when the perfusion analysis is performed by the analysis function 153. Since the recovery executable file 700 is composed of text data, its data size is smaller than that of the analysis results 800. Moreover, in this embodiment, even if the data sizes of the recovery executable file 700, medical image data 900, numerical data 810, and report 820 are added together, they are still smaller than those of the analysis results 800.

[0033] The analysis function 153 may store in the memory circuit 120 the information necessary for the generation function 154 to generate the recovery executable file 700 during the analysis process. The information necessary for generating the recovery executable file 700 includes, but is not limited to, the values ​​set as arguments for the analysis process program identified from the medical image data 900, and the branch to which the medical image data 900 corresponds in the conditional branching.

[0034] Although Figure 1 shows the analysis function 153 and the generation function 154 as separate functional units, the analysis function 153 and the generation function 154 may function as a single unit. Alternatively, the analysis function 153 may also include the generation function 154.

[0035] Figure 3 shows an example of data input and output in the restoration process by the restoration executable file 700 according to the first embodiment. For example, the restoration executable file 700 restores the analysis result 800 based on the medical image data 900, which was the input data for the analysis process by the analysis function 153, and the numerical data 810 generated by the analysis process by the analysis function 153. In Figure 3, the result generated by the restoration executable file 700 is referred to as the restored analysis result 800a. The restoration executable file 700 generates 320 perfusion images with an image size of 512 pixels * 512 pixels for each MAP type, and 3D MAP data, without performing perfusion analysis.

[0036] In Figure 3, report 820 is not included in the recovery process using the recovery executable file 700, but report 820 may also be included in the recovery process.

[0037] The generation function 154 generates a recovery program to be included in the recovery executable file 700 based on the flow of the executed analysis process and the generated analysis results. In this process, the generation function 154 generates the recovery program by optimizing and specializing the contents of the program executed by the analysis function 153 for the recovery of the generated analysis results. The generation function 154 may, for example, generate the recovery program by reading the analysis process program stored in the memory circuit 120 and modifying a part of it. This optimization and specialization can shorten the execution time of the recovery process compared to the analysis process and reduce the size of the recovery executable file 700. Furthermore, by specializing the processing target of the recovery executable file 700 to the medical image data 900 that is the target of analysis, it is possible to suppress the reuse of the recovery executable file 700 for the analysis of other medical image data.

[0038] Figures 4 to 9 are used to illustrate specific examples of optimization and specialization in the restoration process.

[0039] Figure 4 shows an example of replacing variables with fixed values ​​in the generation of the recovery executable file 700 according to the first embodiment. As shown in Figure 4, part 601 of the analysis processing program includes a process to obtain the number of pixels in the width direction of the medical image data 900 that is to be analyzed. Since it is assumed that medical image data of various sizes will be input to the analysis process, a general description that is not limited to a specific number of pixels is used, as in part 601 of the analysis processing program. In contrast, in part 601a of the recovery program shown in Figure 4, the number of pixels in the width direction "512" identified from the medical image data 900 that is to be analyzed is directly described as a fixed value. Therefore, the processing time required to identify the number of pixels in the width direction from the medical image data 900 when the recovery executable file 700 is executed is reduced. Furthermore, since the recovery executable file 700 will not be able to process medical image data with a number of pixels in the width direction other than "512", it will be more difficult to apply the recovery program to the analysis of other medical image data compared to when such a replacement is not made.

[0040] The number of pixels in the width direction of the medical image data 900 is an example of information that can be identified from the medical image data 900 among the information used in the analysis process. The generation function 154 may include information that can be identified from the medical image data 900 as fixed values ​​in the restoration program, not limited to the number of pixels in the width direction. For example, examples of values ​​that can be uniquely identified from the medical image data 900 include image size, PixelSize, etc.

[0041] Figure 5 shows an example of deleting paths that are not executed in the generation of the recovery executable file 700 according to the first embodiment. As shown in Figure 5, part 602 of the analysis processing program has a conditional branch using an if statement. In this case, if the medical image data 900 to be analyzed satisfies the condition "is_image_enhanced_dicom", process A (funcA) is executed; otherwise, process B (funcB) is executed. Here, let's assume that in the analysis processing executed by the analysis function 153, process B was actually executed. That is, since the medical image data 900 does not satisfy the condition "is_image_enhanced_dicom", process A is not executed in the analysis processing. In this case, as shown in part 602a of the recovery program in Figure 5, the generation function 154 deletes the description of the branching condition "is_image_enhanced_dicom" and the description of process A, and describes only process B.

[0042] In this way, the generation function 154 reduces the processing time for branch determination by not including branches that were not used in the analysis of the medical image data 900 in the reconstruction program when branching processing is included in the analysis process. Furthermore, compared to cases where such branches are not deleted, it becomes more difficult to apply the reconstruction program to the analysis of other medical image data corresponding to other branches.

[0043] Figures 6 and 7 further illustrate the deletion of conditional branches. Figure 6 is a diagram showing an example of a conditional branch in the analysis process according to the first embodiment. Figure 7 is a diagram showing an example of a state in which all execution paths except a specific one have been deleted from Figure 6. Processes 1 to 3 shown in Figure 6 are all processes called from the same conditional branch. If the process actually executed in the analysis process targeting medical image data 900 is process 3, the generation function 154 does not include the description of the conditional branch and processes 1 and 2 in the restoration program, and writes the restoration program so that it proceeds directly from the process before the conditional branch ("Start" in Figures 6 and 7) to process 3.

[0044] The generation function 154 may, for example, determine from the information stored in the memory circuit 120 during the analysis process by the analysis function 153 that process 3 of processes 1 to 3 has been executed.

[0045] Furthermore, the generation function 154 may replace the intermediate processing included in the analysis process with fixed values ​​indicating the results of said intermediate processing and describe them in the reconstruction program. Examples of intermediate processing that can be omitted in perfusion analysis include the process of identifying the coordinates of arteries or veins, and the process of aligning the vascular region. The process of identifying the coordinates of arteries or veins can be omitted by replacing them with the values ​​of the identified coordinates. Similarly, the process of aligning the vascular region can be omitted by replacing it with an alignment matrix. Examples of values ​​obtained in intermediate processing include the coordinates identified in the intermediate processing, phase information, point sequence coordinates, etc.

[0046] Figure 8 shows an example of omitting intermediate processing in the generation of the restoration executable file 700 according to the first embodiment. For example, the generation function 154 may replace the intermediate processing that identifies the artery, as shown in part 603 of the analysis processing program in Figure 8, with the coordinate values ​​"100,200,0" actually obtained in the analysis processing, as shown in part 603a of the restoration program.

[0047] Furthermore, the generation function 154 may include values ​​entered by the user during the execution of the analysis process in the recovery program. This eliminates the need to process user input.

[0048] Furthermore, in Figures 4 to 8 above, the generation function 154 performed replacements with fixed values ​​at the text-format source code stage, but similar processing may be performed in the program that analyzes the binary-format state.

[0049] Figure 9 shows an example of partial replacement of binary data according to the first embodiment. For example, Figure 4 illustrates an example of replacing the process of obtaining the number of pixels in the width direction of medical image data 900 with a fixed value for the number of pixels in the width direction of medical image data 900, as an edit of text-format source code. In contrast, in Figure 9, the part of the binary-format analysis processing program 605 that represents the number of pixels in the width direction of medical image data 900 (underlined part) may be replaced with a fixed value for the number of pixels in the width direction (underlined part) in the corresponding part of the restoration program 605a. The generation function 154 is not limited to the example shown in Figure 9, but may also replace the area of ​​constants that can be uniquely determined from the medical image data 900 in the binary-format analysis processing program with a description of a fixed value in binary format.

[0050] Furthermore, the optimization and specialization methods shown in Figures 4 to 9 above are merely examples, and the optimization and specialization methods for the recovery program are not limited to these. For example, the generation function 154 may limit the analysis target by including a UID (unique identifier) ​​or hash value that can identify the medical image data 900 to be analyzed in the recovery program. Also, if the analysis process involves referencing a library, the generation function 154 includes a link to that library in the recovery program. Specifically, the generation function 154 may create a package that links to the target library, or it may compile the program including a link to that library. In addition, the generation function 154 may include the part of the library that is referenced in the analysis process in the recovery program.

[0051] Furthermore, the configuration of the medical image data 900 shown in Figures 2 to 9, and the source code of the program for analysis processing or restoration, are examples only and are not limited to these.

[0052] The generation function 154 may use one of the optimization and / or specialization methods, or it may use a combination of multiple optimization and specialization methods.

[0053] Furthermore, as mentioned above, the generation function 154 may also include fixed values ​​in a configuration file instead of the recovery executable file 700. In this case, the generation function 154 writes the recovery program to refer to the corresponding section of the configuration file.

[0054] Furthermore, although the recovery executable file 700 referenced the numerical data 810 in Figure 3 above, the numerical values ​​described in the numerical data 810 may also be directly described in the recovery executable file 700. In this case, the recovery executable file 700 can recover the analysis result 800 without referencing the numerical data 810.

[0055] Returning to Figure 1, the receiving function 155 receives data requests from the information processing terminal 300 via the network N2 and the NW interface 110. For example, the receiving function 155 receives requests from the information processing terminal 300 for medical image data and a recovery executable file 700. Alternatively, the data requested by the medical data processing device 100 from the information processing terminal 300 may consist only of the recovery executable file 700. In addition, a set of the recovery executable file 700, numerical data 810, and report 820 may be requested from the information processing terminal 300.

[0056] When the receiving function 155 receives a data request from the information processing terminal 300, the transmitting function 156 transmits the requested data to the information processing terminal 300 via the network N2 and the NW interface 110. For example, when the receiving function 155 receives a request for medical image data and a recovery executable file 700, the transmitting function 156 transmits the medical image data and the recovery executable file 700 to the information processing terminal 300 via the network N2 and the NW interface 110.

[0057] The display control function 157 controls the display 140 to display various screens. For example, the display control function 157 may display the analysis results 800 on the display 140.

[0058] Here, we will explain the processing flow executed by the information processing system S configured as described above.

[0059] Figure 10 is a sequence diagram showing an example of a processing flow including the analysis of medical image data 900 and the generation of an executable file for restoration according to the first embodiment. The processing in this sequence diagram starts, for example, when the reception function 151 of the medical data processing device 100 receives a user's instruction to specify the medical image data 900 to be analyzed and to start the analysis process.

[0060] First, the acquisition function 152 of the medical data processing device 100 acquires the medical image data 900 to be analyzed from the image storage device 200 (S1). The acquisition function 152 then stores the acquired medical image data 900 in, for example, the memory circuit 120.

[0061] The analysis function 153 of the medical data processing device 100 then performs analysis processing on the medical image data 900. At this time, the analysis function 153 generates, for example, analysis results 800, numerical data 810, and a report 820, as explained in Figure 2. The generation function 154 of the medical data processing device 100 also generates a recovery executable file 700 for restoring the analysis results 800 generated by the analysis function 153 (S2). The analysis function 153 saves the generated analysis results 800, numerical data 810, and report 820 to, for example, the memory circuit 120. The analysis function 153 also saves the generated recovery executable file 700 to, for example, the memory circuit 120. The analysis function 153 may save the generated analysis results 800 to the memory circuit 120, or it may delete the analysis results 800 after the recovery executable file 700 has been generated.

[0062] Here, the receiving function 155 of the medical data processing device 100 receives requests for medical image data 900 and a recovery executable file 700 from the information processing terminal 300 (S3). The timing of receiving the requests from the information processing terminal 300 is not particularly limited and can be after the processing in S2. In addition, the receiving function 155 may also receive requests for numerical data 810 and a report 820 at this time.

[0063] The transmission function 156 of the medical data processing device 100 transmits the medical image data 900 and the recovery executable file 700 requested in S3 to the information processing terminal 300 (S4). If numerical data 810 or a configuration file is required in addition to the medical image data 900 for the execution of the recovery executable file 700, the transmission function 156 transmits the numerical data 810 or the configuration file together with the medical image data 900 and the recovery executable file 700 to the information processing terminal 300. Furthermore, if the information processing terminal 300 has also requested numerical data 810 and a report 820, the transmission function 156 transmits the numerical data 810 and the report 820 to the information processing terminal 300 as well.

[0064] Then, the processing circuit of the information processing terminal 300 executes the recovery executable file 700 obtained from the medical data processing device 100 (S5). This generates the recovered analysis result 800a. The recovery executable file 700 may be executed automatically when it is sent from the medical data processing device 100 to the information processing terminal 300. Alternatively, the information processing terminal 300 may manually execute the recovery executable file 700 in response to user input.

[0065] Then, the processing circuit of the information processing terminal 300 displays the restored analysis result 800a on the display of the information processing terminal 300 (S6). This allows the user of the information processing terminal 300 to confirm the restored analysis result 800a of the medical image data 900. At this point, the processing in this sequence diagram is completed.

[0066] As described above, when the medical data processing device 100 of this embodiment analyzes medical image data 900, it generates a recovery executable file 700 in which a process capable of restoring the analysis results 800 is defined. In other words, with the medical data processing device 100 of this embodiment, even without transferring or saving the analysis results 800 themselves, the analysis results 800 can be restored and provided to the user as needed by transferring or saving the recovery executable file 700. For this reason, the medical data processing device 100 of this embodiment can reduce the data size when transferring or saving the analysis results 800 of the medical image data 900.

[0067] Furthermore, the medical data processing device 100 of this embodiment generates a restoration executable file 700 containing a restoration program that performs the process of restoring the analysis results 800. In addition, the medical data processing device 100 of this embodiment includes information identified from the medical image data 900 as fixed values ​​in the restoration program among the information used in the analysis process of the medical image data 900; branches that were not used in the analysis of the medical image data 900 when the analysis process includes branching; intermediate processes included in the analysis process are replaced with fixed values ​​indicating the results of the intermediate processes and described in the restoration program; and values ​​entered by the user during the execution of the analysis process are included in the restoration program. As a result, according to the medical data processing device 100 of this embodiment, the restoration executable file 700 is optimized and specific for restoring the medical image data 900 that is the target of analysis. Through such optimization and specialization, it is possible to shorten the processing time when restoring the analysis results 800 by executing the restoration executable file 700, reduce the size of the restoration executable file 700, and prevent the restoration executable file 700 from being repurposed for the analysis of other medical image data.

[0068] Furthermore, the medical data processing device 100 of this embodiment analyzes the medical image data 900 to generate analysis image data (perfusion image data and 3D MA) showing the analysis results of the medical image data 900, numerical data 810 containing numerical values ​​identified by the analysis process, and a report 820 concerning the analysis results. From these, it generates a recovery executable file 700 in which a process capable of restoring the analysis image data is defined. Since the numerical data 810 and report 820 are relatively small in size, deleting the numerical data 810 and report 820 and transferring or saving them instead of the recovery executable file 700 would have little effect on reducing the data size during transfer or saving. For this reason, the medical data processing device 100 of this embodiment targets only the analysis image data, which has a relatively large data size, for restoration, thus efficiently achieving a reduction in data size.

[0069] Furthermore, the medical data processing device 100 of this embodiment stores the generated recovery executable file 700 in the storage circuit 120, and when it receives a request for the recovery executable file 700 from the information processing terminal 300, it sends the recovery executable file 700 to the information processing terminal 300. The information processing terminal 300 obtains the recovered analysis result 800a by executing the recovery executable file 700. Therefore, the medical data processing device 100 of this embodiment can provide the recovered analysis result 800a to the information processing terminal 300 by sending the recovery executable file 700, without having to send the analysis result 800 itself to the information processing terminal 300. In other words, the medical data processing device 100 of this embodiment can reduce the size of the data to be transferred (transmitted).

[0070] For example, when providing data to an information processing terminal 300 located in a different medical institution than the medical data processing device 100, such as through collaboration with other hospitals, the bandwidth of the network N2 connecting the medical data processing device 100 and the information processing terminal 300 may be narrow. In such cases, the data transfer time can be reduced by reducing the size of the data to be transferred (transmitted).

[0071] (Second embodiment) In the first embodiment described above, the medical data processing device 100 optimized and specialized the reconstruction program by methods such as replacing a part of the analysis processing program with fixed values ​​identified from the medical image data 900. In this second embodiment, the reconstruction program is further optimized and specialized by making the algorithms of the analysis processing program and the reconstruction program different.

[0072] The information processing system S of this embodiment includes a medical data processing device 100 and an image storage device 200, similar to the first embodiment described in Figure 1. Furthermore, the medical data processing device 100 and the image storage device 200 are connected to the information processing terminal 300 in a communicative manner, similar to the first embodiment.

[0073] The medical data processing device 100 of this embodiment includes, similar to the first embodiment, an NW interface 110, a storage circuit 120, an input interface 130, a display 140, and a processing circuit 150.

[0074] The processing circuit 150 of the medical data processing device 100 in this embodiment includes a reception function 151, an acquisition function 152, an analysis function 153, a generation function 154, a receiving function 155, a transmission function 156, and a display control function 157, similar to the first embodiment.

[0075] The reception function 151, acquisition function 152, analysis function 153, receiving function 155, transmission function 156, and display control function 157 have the same functions as in the first embodiment.

[0076] In addition to the same functions as in the first embodiment, the generation function 154 of this embodiment generates a restoration executable file 700 that restores the analysis result 800 using an algorithm different from the analysis algorithm used in the analysis process. The purpose of the restoration executable file 700 is to restore the analysis result 800, not to analyze the medical image data 900. Therefore, the restoration program described in the restoration executable file 700 does not need to include processing for analyzing the medical image data 900.

[0077] Figure 11 shows an example of analysis processing by the analysis function 153 according to the second embodiment. In the example shown in Figure 11, the analysis function 153 performs segmentation analysis to search for tumor regions from medical image data 900. In the example shown in Figure 11, the segmentation data 801 generated by the tumor region search process in the segmentation analysis extracts two pixels 81 and 82 as tumor regions. The segmentation data 801 is an example of the analysis result of the analysis processing in this embodiment.

[0078] Figure 12 shows an example of the processing defined in the reconstruction executable file 700 corresponding to the processing in Figure 11. The generation function 154 does not include the algorithm for the tumor region search process in the reconstruction executable file 700, but instead includes the results of the tumor region search process in the reconstruction executable file 700. Specifically, the generation function 154 includes the coordinates of the two pixels 81 and 82 extracted by the tumor region search process shown in Figure 11 as fixed values ​​in the reconstruction program. As a result, the reconstruction executable file 700 can generate the reconstructed segmentation data 801a without performing the tumor region search process.

[0079] Thus, the medical data processing device 100 of this embodiment does not include the region extraction process included in the analysis process in the restoration executable file 700, but includes the coordinates on the medical image data 900 extracted by region extraction. Therefore, the medical data processing device 100 of this embodiment has the effects of the first embodiment, and further optimizes and specializes the restoration executable file 700 for the restoration of the medical image data 900 that is the target of analysis. This further enhances the optimization and specialization effects, such as shortening the processing time when restoring the analysis results 800 by executing the restoration executable file 700, reducing the size of the restoration executable file 700, and suppressing the reuse of the restoration executable file 700 for the analysis of other medical image data.

[0080] In this embodiment, the tumor region search process was described as an example, but the processes that are replaced with processing results when generating the recovery executable file 700 are not limited to this. The generation function 154 can replace various processes included in the analysis process with the results of those processes. Furthermore, the effect of reducing the processing time when restoring the analysis results 800 and reducing the size of the recovery executable file 700 by replacing such processes is higher the heavier the process being replaced and the smaller the size of the data obtained by that process. For example, in the examples shown in Figures 11 and 12, the fewer the number of pixels 81 and 82 of the tumor region obtained as a result of the tumor region search process, the greater the effect of reducing the processing time when restoring the analysis results 800 and reducing the size of the recovery executable file 700 by replacing the processes. For this reason, the generation function 154 may decide whether or not to replace a part of the analysis process with processing results when generating the recovery executable file 700, depending on the data size of the processing results. For example, the generation function 154 may replace the process for obtaining the processing results with a fixed value indicating the processing results if the data size of the processing results is below a threshold.

[0081] (Third embodiment) In this third embodiment, the medical data processing device 100 evaluates the validity of the generated recovery executable file 700.

[0082] Figure 13 shows an example of the overall configuration of the information processing system S according to the third embodiment. The information processing system S in this embodiment includes a medical data processing device 100 and an image storage device 200, similar to the first embodiment described in Figure 1. Furthermore, the medical data processing device 100 and the image storage device 200 are connected to the information processing terminal 300 for communication, similar to the first embodiment.

[0083] The medical data processing device 100 of this embodiment includes, similar to the first embodiment, an NW interface 110, a storage circuit 120, an input interface 130, a display 140, and a processing circuit 150.

[0084] The processing circuit 150 of the medical data processing device 100 in this embodiment includes a reception function 151, an acquisition function 152, an analysis function 153, a generation function 154, a receiving function 155, a transmission function 156, a display control function 157, a comparison function 158, and a deletion processing function 159. The comparison function 158 is an example of a comparison unit. The deletion processing function 159 is an example of a deletion processing unit.

[0085] The reception function 151, acquisition function 152, analysis function 153, generation function 154, receiving function 155, transmission function 156, and display control function 157 have the same functions as in the first embodiment.

[0086] The comparison function 158 compares the analysis result 800 produced by the analysis function 153 with the restored analysis result 800a, which is restored by the restoration executable file 700 generated by the generation function 154. More specifically, the comparison function 158 executes the restoration executable file 700 to generate the restored analysis result 800a. Then, the comparison function 158 compares the generated restored analysis result 800a with the analysis result 800 produced by the analysis function 153.

[0087] The comparison method used by the comparison function 158 may employ, for example, a known image comparison technique. Furthermore, the comparison method may differ depending on the type of data of the analysis result 800 and the restored analysis result 800a.

[0088] The timing for starting the comparison process between the analysis result 800 and the restored analysis result 800a may be, for example, immediately after the restoration executable file 700 is generated by the generation function 154. Alternatively, the comparison process may start when the reception function 151 receives a user's request to start the comparison process.

[0089] The deletion function 159 deletes the recovery executable file 700 according to the results of the comparison performed by the comparison function 158. For example, if the analysis result 800 and the recovered analysis result 800a do not match, the recovery executable file 700 is not valid because it has not been able to recover the analysis result 800. Therefore, the deletion function 159 deletes the recovery executable file 700 if the analysis result 800 and the recovered analysis result 800a do not match.

[0090] Furthermore, if the analysis result 800 and the restored analysis result 800a match, the restoration executable file 700 is valid because it has successfully restored the analysis result 800. For this reason, the deletion processing function 159 does not delete the restoration executable file 700 if the analysis result 800 and the restored analysis result 800a match. In this case, the restoration executable file 700 is stored, for example, in the memory circuit 120.

[0091] As described above, the medical data processing device 100 of this embodiment compares the analysis result 800 obtained by the analysis function 153 with the restored analysis result 800a restored by the restoration executable file 700 generated by the generation function 154. If the analysis result 800 and the restored analysis result 800a do not match, the restoration executable file 700 is deleted. Furthermore, if the analysis result 800 and the restored analysis result 800a match, the medical data processing device 100 of this embodiment does not delete the restoration executable file 700. Therefore, the medical data processing device 100 of this embodiment has the advantages of the first embodiment, and can also guarantee the validity of the restoration executable file 700.

[0092] Evaluating the validity of such a recovery executable file 700 is particularly useful when the recovery program is generated by a large-scale language model. Furthermore, for example, in the second embodiment described above, the recovery executable file 700 has a different configuration from the analysis processing algorithm, so it is useful to apply the configuration of this third embodiment to verify the validity of the recovery executable file 700.

[0093] Furthermore, the display control function 157 may display on the display 140 that the recovery executable file 700 is not valid if the analysis result 800 and the recovered analysis result 800a do not match. Also, the generation function 154 may generate the recovery executable file 700 again if the analysis result 800 and the recovered analysis result 800a do not match.

[0094] (Fourth embodiment) In the first embodiment described above, the medical data processing device 100 generated the recovery executable file 700 simultaneously with the analysis process. In contrast, in this fourth embodiment, the medical data processing device 100 generates the recovery executable file 700 when the specified processing conditions are met.

[0095] The information processing system S of this embodiment includes a medical data processing device 100 and an image storage device 200, similar to the first embodiment described in Figure 1. Furthermore, the medical data processing device 100 and the image storage device 200 are connected to the information processing terminal 300 in a communicative manner, similar to the first embodiment.

[0096] The medical data processing device 100 of this embodiment includes, similar to the first embodiment, an NW interface 110, a storage circuit 120, an input interface 130, a display 140, and a processing circuit 150.

[0097] The processing circuit 150 of the medical data processing device 100 in this embodiment includes a reception function 151, an acquisition function 152, an analysis function 153, a generation function 154, a receiving function 155, a transmission function 156, and a display control function 157, similar to the first embodiment.

[0098] The reception function 151, acquisition function 152, receiving function 155, transmission function 156, and display control function 157 have the same functions as in the first embodiment.

[0099] In addition to the same functions as in the first embodiment, the analysis function 153 of this embodiment stores the fixed values ​​obtained during the analysis process and the analysis results 800 in the memory circuit 120 during the analysis process of the medical image data 900.

[0100] For example, the analysis function 153 may store various data usable for optimizing and specializing the restoration process described in Figures 4 to 9 in the first embodiment in the memory circuit 120. Specifically, the analysis function 153 may store in the memory circuit 120 the image size, PixelSize and other numerical values ​​that can be uniquely identified from the medical image data 900, the results of intermediate processing included in the analysis process, and the conditional branch included in the analysis process to which the medical image data 900 actually corresponds. In addition, the analysis function 153 may store in the memory circuit 120 the results of the region extraction process described in Figures 12 and 13 in the second embodiment.

[0101] In addition to the same functions as in the first embodiment, the generation function 154 of this embodiment reads fixed values ​​and analysis results 800 stored in the memory circuit 120 from the memory circuit 120 when the specified processing conditions are met, and generates a recovery executable file 700 based on the read fixed values ​​and analysis results 800.

[0102] The specified processing conditions are, for example, that the processing resources of the medical data processing device 100 have a specified amount of available capacity. The processing resources of the medical data processing device 100 are represented, for example, by the CPU usage rate, the available capacity of the memory circuit 120 (memory / storage), etc. The specified processing conditions may also be defined by thresholds such as "CPU usage rate is n% or less" or "available memory capacity is m megabytes or more." The specified processing conditions may be predetermined or may be set by the user.

[0103] As described above, the medical data processing device 100 of this embodiment stores the fixed values ​​and analysis results 800 obtained during the analysis of medical image data 900 in the storage circuit 120, and when the prescribed processing conditions are met, reads the fixed values ​​and analysis results from the storage circuit 120 and generates a recovery executable file 700 based on the read fixed values ​​and analysis results. For this reason, the medical data processing device 100 of this embodiment can generate a recovery executable file 700 at an appropriate timing while having the advantages of the first embodiment.

[0104] For example, during the execution of an analysis process, it may be difficult to secure sufficient processing resources for the medical data processing device 100 for user operations or other analysis processes. In such cases, the medical data processing device 100 of this embodiment can generate a recovery executable file 700 after the state of the medical data processing device 100 is ready, regardless of the timing of the execution of the analysis process.

[0105] (Fifth embodiment) In the first embodiment described above, the medical data processing device 100 sends a recovery executable file 700 to the information processing terminal 300, and the recovery executable file 700 is executed by the receiving information processing terminal 300. In contrast, in this fifth embodiment, the medical data processing device 100 sends the recovered analysis results 800a, which were recovered by executing the recovery executable file 700, to the information processing terminal 300.

[0106] Figure 14 shows an example of the overall configuration of the information processing system S according to the fifth embodiment. The information processing system S in this embodiment includes a medical data processing device 100 and an image storage device 200, similar to the first embodiment described in Figure 1. Furthermore, the medical data processing device 100 and the image storage device 200 are connected to the information processing terminal 300 for communication, similar to the first embodiment.

[0107] The medical data processing device 100 of this embodiment includes, similar to the first embodiment, an NW interface 110, a storage circuit 120, an input interface 130, a display 140, and a processing circuit 150.

[0108] The processing circuit 150 of the medical data processing device 100 in this embodiment includes a reception function 151, an acquisition function 152, an analysis function 153, a generation function 154, a receiving function 155, a transmission function 156, a display control function 157, a deletion processing function 159a, and a restoration processing function 160. The deletion processing function 159a is an example of a deletion processing unit. The restoration processing function 160 is an example of a restoration processing unit.

[0109] The reception function 151, acquisition function 152, analysis function 153, generation function 154, receiving function 155, and display control function 157 have the same functions as in the first embodiment.

[0110] In this embodiment, the deletion processing function 159a deletes the analysis result 800 corresponding to the recovery executable file 700 after the recovery executable file 700 has been generated. Furthermore, the deletion processing function 159a deletes the recovered analysis result 800a after it has been sent to the information processing terminal 300.

[0111] The recovery processing function 160 recovers the analysis results 800 by executing the recovery executable file 700.

[0112] The transmission function 156 of this embodiment has the same functions as in the first embodiment, and transmits the restored analysis result 800a restored by the restoration processing function 160 to the information processing terminal 300.

[0113] Figure 15 is a sequence diagram showing an example of the processing flow including the analysis of medical image data 900 and the generation of an executable file 700 for restoration according to the fifth embodiment. From the acquisition of medical image data 900 in S11 to the analysis process and generation of the executable file 700 for restoration in S12 shown in Figure 15, the process is the same as that of the first embodiment described in Figure 10.

[0114] Next, the deletion processing function 159a deletes the analysis results 800 after the recovery executable file 700 has been generated. The generation function 154 saves the generated recovery executable file 700 to the memory circuit 120. The acquisition function 152 saves the medical image data 900 to the memory circuit 120 (S13).

[0115] Here, the receiving function 155 of the medical data processing device 100 receives a request for analysis results 800 from the information processing terminal 300 (S14). The timing of receiving the request from the information processing terminal 300 is not particularly limited and can be after the processing in S13.

[0116] In this case, the recovery processing function 160 of the medical data processing device 100 recovers the analysis results 800 by executing the recovery executable file 700 (S15).

[0117] Then, the transmission function 156 transmits the restored analysis result 800a, which has been restored by the restoration processing function 160, to the information processing terminal 300 (S16). The information processing terminal 300 receives the restored analysis result 800a from the medical data processing device 100.

[0118] Then, the processing circuit of the information processing terminal 300 displays the restored analysis results 800a on the display of the information processing terminal 300 (S17). This allows the user of the information processing terminal 300 to confirm the restored analysis results 800a of the medical image data 900.

[0119] The deletion function 159a deletes the restored analysis result 800a after it has been sent to the information processing terminal 300 (S18). At this point, the processing in this sequence diagram ends.

[0120] As described above, the medical data processing device 100 of this embodiment generates a recovery executable file 700 and then deletes the analysis result 800 corresponding to the recovery executable file 700. Furthermore, the medical data processing device 100 of this embodiment recovers the analysis result 800 by executing the recovery executable file 700 and transmits the recovered analysis result 800a to the information processing terminal 300. For this reason, the medical data processing device 100 of this embodiment can reduce the amount of data stored compared to the case where the analysis result 800 is saved. In addition, since the medical data processing device 100 of this embodiment transmits the recovered analysis result 800a to the information processing terminal 300, it is also applicable even when the information processing terminal 300 does not have an environment to execute the recovery executable file 700.

[0121] (Sixth embodiment) In the first embodiment described above, the information processing terminal 300 executed the recovery executable file 700. In the fifth embodiment described above, the medical data processing device 100 executed the recovery executable file 700. In contrast, in this sixth embodiment, the image storage device 200 executes the recovery executable file 700.

[0122] The information processing system S of this embodiment includes a medical data processing device 100 and an image storage device 200, similar to the first embodiment described in Figure 1. Furthermore, the medical data processing device 100 and the image storage device 200 are connected to the information processing terminal 300 in a communicative manner, similar to the first embodiment.

[0123] The medical data processing device 100 of this embodiment includes, similar to the first embodiment, an NW interface 110, a storage circuit 120, an input interface 130, a display 140, and a processing circuit 150.

[0124] The processing circuit 150 of the medical data processing device 100 in this embodiment includes a reception function 151, an acquisition function 152, an analysis function 153, a generation function 154, a receiving function 155, a transmission function 156, and a display control function 157, similar to the first embodiment.

[0125] Furthermore, the processing circuit of the image storage device 200 in this embodiment has the same functions as the deletion processing function 159a and the restoration processing function 160 of the medical data processing device 100 in the fifth embodiment. In addition, the processing circuit of the image storage device 200 in this embodiment has a transmission function for transmitting data between the medical data processing device 100 and the information processing terminal 300, and a reception function for receiving data.

[0126] Furthermore, the processing circuit of the information processing terminal 300 in this embodiment includes a transmission function for transmitting data to and from the medical data processing device 100 and the image storage device 200, and a reception function for receiving data.

[0127] Figure 16 is a sequence diagram showing an example of the processing flow including the analysis of medical image data 900 and the generation of an executable file for restoration according to the sixth embodiment. From the acquisition of medical image data 900 in S31 to the analysis process and generation of the executable file for restoration 700 in S32 shown in Figure 16, the process is the same as that of the first embodiment described in Figure 10.

[0128] Next, the transmission function 156 of the medical data processing device 100 transmits the recovery executable file 700 to the image storage device 200 (S33). The image storage device 200 receives the recovery executable file 700 and stores it in its memory circuit. In this embodiment, the processes S31 to S33 are performed on multiple medical image data stored in the image storage device 200.

[0129] Here, the processing circuit of the image storage device 200 receives a request from the information processing terminal 300 for a list of medical image data that meets the search criteria (S34). The timing at which the image storage device 200 receives the request from the information processing terminal 300 is not particularly limited and can be anytime after the processing in S33.

[0130] The search criteria are conditions for searching medical image data stored in the image storage device 200, and include, for example, the patient's name, the examination name (type of medical image data acquisition), etc. The search criteria may also be entered by, for example, the user of the information processing terminal 300.

[0131] The list of medical image data that meets the search criteria is, for example, a list of names of medical image data stored in the image storage device 200 that meet the search criteria. This list may also include, for example, the patient name or examination name corresponding to the medical image data.

[0132] When the processing circuit of the image storage device 200 receives a request from the information processing terminal 300 for a list of medical image data that meets the search criteria, it transmits a list of medical image data stored in the image storage device 200 that meets the search criteria to the information processing terminal 300 (S35). Furthermore, the processing circuit of the image storage device 200 includes in the list only medical image data for which the recovery executable file 700 is stored in the image storage device 200.

[0133] The processing circuit of the information processing terminal 300 selects from the list received from the image storage device 200 the target for which analysis results 800 are requested (S36). This selection may also be performed by the user of the information processing terminal 300.

[0134] Then, the processing circuit of the information processing terminal 300 requests the image storage device 200 to provide the analysis results 800 (S37).

[0135] In this case, the processing circuit of the image storage device 200 restores the analysis result 800 by executing the restoration executable file 700 (S38).

[0136] Then, the processing circuit of the image storage device 200 transmits the restored analysis results 800a to the information processing terminal 300 (S39). The information processing terminal 300 receives the restored analysis results 800a from the image storage device 200.

[0137] Then, the processing circuit of the information processing terminal 300 displays the restored analysis results 800a on the display of the information processing terminal 300 (S40). This allows the user of the information processing terminal 300 to confirm the restored analysis results 800a of the medical image data 900.

[0138] The processing circuit of the image storage device 200 deletes the restored analysis result 800a after it has been transmitted to the information processing terminal 300 (S41). At this point, the processing in this sequence diagram is completed.

[0139] Thus, the medical data processing device 100 of this embodiment provides the recovery executable file 700 to the image storage device 200. Therefore, even if the image storage device 200 does not have an analysis function and does not store the analysis results 800, it can still provide the recovered analysis results 800a to the information processing terminal 300. For this reason, according to this embodiment, the amount of data stored in the image storage device 200 can be reduced. In addition, since the frequency of access from the information processing terminal 300 to the image storage device 200 to request the analysis results 800 is generally low, even if the image storage device 200 performs the recovery process after receiving the request, the disadvantage in terms of processing time is small.

[0140] Furthermore, after the medical data processing device 100 sends the recovery executable file 700 to the image storage device 200, it may either save or delete the recovery executable file 700 and the analysis results 800. For example, the medical data processing device 100 may delete the recovery executable file 700 and analysis results 800 related to old medical image data that has been captured for a certain period of time or more. In this case, since the image storage device 200 also saves the recovery executable file 700 for old medical image data, the analysis results 800 can be recovered if needed.

[0141] (Variation 1) In the embodiments described above, medical image data 900 was used as the target of the analysis process. However, the target of analysis is not limited to medical image data, but may also be text data containing medical information. In this case, text data containing medical information is an example of medical data. Furthermore, medical data may include both medical image data 900 and text data. For example, the target of analysis may be patient interview results, diagnostic information, or test results. The medical data processing device 100 may acquire various types of medical data for analysis from an electronic medical record system, a hospital information system (HIS), a laboratory information system (LIS), etc.

[0142] (Modification 2) Furthermore, in the first embodiment, in Figure 2, only the perfusion image data and 3D MAP showing the analysis results were defined as the analysis results 800, but numerical data 810 and report 820 may also be included in the analysis results 800. If numerical data 810 and report 820 are included in the analysis results 800, the generation function 154 may also include the numerical data 810 and report 820 as targets for restoration by the restoration executable file 700.

[0143] Furthermore, the data to be restored by the restoration executable file 700 may be only a part of the analysis results 800. For example, if numerical data 810 and report 820 are included in the analysis results 800, the generation function 154 may not include the numerical data 810 and report 820 in the restoration executable file 700, and may only restore the perfusion image data and 3D MAP data.

[0144] (Variation 3) In the embodiments described above, perfusion analysis and segmentation analysis were given as examples of analysis processes, but the types of analysis processes are not limited to these. The analysis function 153 of the medical data processing device 100 may perform, for example, vascular analysis, cardiac analysis, pulmonary function analysis, etc.

[0145] Furthermore, for each analysis process, the intermediate processes that can be replaced with fixed values ​​representing the results differ in order to optimize and specialize the recovery executable file 700. For example, in vascular analysis, the process of identifying core line coordinates (sequence of points), in cardiac analysis, the process of identifying the optimal phase, and in pulmonary function analysis, the process of identifying the inspiratory or expiratory phase can be replaced with fixed values ​​representing the results for optimization and specialization.

[0146] (Modification 4) In the first embodiment described above, an exe file was given as an example of the recovery executable file 700, but the format and language of the recovery executable file 700 are not limited to the above example. For example, the recovery executable file 700 may be a file with the extension "dll", "jar", "apk", etc., or a package containing such a file. Since data with these extensions cannot be executed on their own and require an execution environment, it is a condition that an appropriate execution environment is installed in the environment in which the recovery executable file 700 is executed.

[0147] Furthermore, the recovery executable file 700 may also be a script file in JavaScript® or Python®.

[0148] (Variation 5) While the above embodiments primarily described data provision between different medical institutions as an application, the destination to which the recovery executable file 700 is provided from the medical data processing device 100 is not limited to this. For example, the technology of the above embodiments may also be applied to data transfer within the same medical institution.

[0149] In the embodiments described above, data transfer via network N2 was illustrated, but the techniques of the embodiments described above can also be applied when providing data by saving it to a portable storage medium such as a USB (Universal Serial Bus) memory, CD-ROM (Read Only Memory), CD-R, or DVD (Digital Versatile Disk). For example, saving the recovery executable file 700 requires less storage capacity than saving the analysis results 800 to a storage medium.

[0150] Furthermore, the destination for data transfer from the medical data processing device 100 may be a cloud environment. For example, when using a cloud service where usage fees vary depending on the amount of data transferred or stored, transferring the recovery executable file 700 can reduce service usage fees compared to transferring the analysis results 800.

[0151] The various types of data discussed in this specification are typically digital data.

[0152] According to at least one embodiment described above, the data size when transferring or storing the results of medical data analysis can be reduced.

[0153] While several embodiments have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These embodiments can be implemented in a variety of other forms, and various omissions, substitutions, modifications, and combinations of embodiments are possible without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents. [Explanation of Symbols]

[0154] 81,82 pixels 100 Medical data processing devices 110 NW Interfaces 120 Memory circuit 130 Input Interfaces 140 displays 150 Processing Circuits 151 Reception function 152 Acquisition function 153 Analysis Functions 154 Generation function 155 Receiving function 156 Transmission function 157 Display control function 158 Comparison Function 159,159a Deletion processing function 160 Recovery Processing Function 200 Image storage device 300 Information Processing Terminals 601-604 Part of the analysis processing program 601a~604a Part of the recovery program 700 Executable files for recovery 800 analysis results 800a Reconstructed Analysis Results 801 Segmentation Data 801a Restored segmentation data 810 Numerical data 820 Report 900 Medical Image Data N1, N2 Network S Information Processing System

Claims

1. A data acquisition unit that acquires medical data, An analysis unit analyzes the aforementioned medical data and outputs the analysis results, A generation unit that generates restoration process definition information that defines a process capable of restoring at least a portion of the aforementioned analysis results, A medical data processing device equipped with [a specific feature].

2. The aforementioned restoration process definition information includes a restoration executable file that contains a program for performing the process of restoring the analysis results, The generation unit includes in the program information identified from the medical data as a fixed value among the information used in the analysis process of the medical data performed by the analysis unit; if the analysis process includes branching, branches that were not used in the analysis of the medical data are not included in the program; intermediate processes included in the analysis process are replaced with fixed values ​​indicating the results of the intermediate processes and described in the program; and values ​​entered by the user during the execution of the analysis process are included in the program. The medical data processing device according to claim 1.

3. The analysis unit analyzes the medical data to generate analysis image data showing the analysis results, numerical data including numerical values ​​identified by the analysis process, and a report relating to the analysis results. The generation unit generates the restoration process definition information which defines a process that can restore the analyzed image data. The medical data processing device according to claim 1.

4. The aforementioned medical data includes medical image data, The analysis unit performs analysis processing including region extraction on the medical image data, The generation unit includes, in the restoration process definition information, the coordinates on the medical image data extracted by the region extraction, but does not include the process of extracting the region. The medical data processing device according to claim 1.

5. The analysis unit stores the fixed values ​​obtained from the analysis processing of the medical data and the analysis results in the storage unit. The generation unit reads the fixed value and the analysis result from the storage unit when the specified processing conditions are met, and generates the restoration processing definition information based on the read fixed value and the analysis result. The medical data processing device according to claim 1.

6. A comparison unit compares the analysis results from the analysis unit with the restored analysis results restored by the restoration process definition information generated by the generation unit. The system further includes a deletion processing unit that deletes the restoration process definition information if the aforementioned analysis results and the restored analysis results do not match. The medical data processing device according to claim 1.

7. A storage unit that stores the restoration process definition information generated by the generation unit, A receiving unit that receives a request for the restoration process definition information from another information processing device, The receiving unit further comprises a transmitting unit that transmits the restoration process definition information to the other information processing device when the receiving unit receives the request from the other information processing device. A medical data processing device according to any one of claims 1 to 6.

8. A storage unit that stores the restoration process definition information generated by the generation unit, After the restoration process definition information is generated by the generation unit, a deletion processing unit deletes the analysis results corresponding to the restoration process definition information. A restoration processing unit that restores the analysis results by executing the restoration process definition information, The system further comprises a transmission unit that transmits the restored analysis results to another information processing device. A medical data processing device according to any one of claims 1 to 5.

9. Acquisition steps for obtaining medical data, An analysis step which involves analyzing the aforementioned medical data and outputting the analysis results, A generation step that generates restoration process definition information that defines a process capable of restoring at least a portion of the analysis results, A medical data processing method including [the specified term].

10. Acquisition steps for obtaining medical data, An analysis step which involves analyzing the aforementioned medical data and outputting the analysis results, A generation step that generates restoration process definition information that defines a process capable of restoring at least a portion of the analysis results, A program that causes a computer to execute something.

Images