Medical information processing device, medical information processing system, medical information processing method, and program
The medical information processing device addresses inefficiencies in integrating new analysis applications by using an acquisition and update unit to modify workflows, resulting in improved analysis efficiency and performance.
Patent Information
- Application Number
- JP2024232368
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-12-27
- Publication Date
- 2026-07-09
AI Technical Summary
Existing systems face challenges in efficiently incorporating new analysis applications into medical image processing workflows, leading to difficulties in improving the efficiency of analysis work.
The medical information processing device includes an acquisition unit to gather update trigger information and an update unit to modify workflows based on this information, enabling the integration of new analysis applications and enhancing workflow efficiency.
This approach allows for the generation of new workflows that improve analysis performance, resource utilization, and accuracy, thereby enhancing the overall efficiency of medical image analysis processes.
Smart Images

Figure 2026115579000001_ABST
Abstract
Description
Technical Field
[0001] The embodiments disclosed in this specification and the drawings relate to a medical information processing apparatus, a medical information processing system, a medical information processing method, and a program.
Background Art
[0002] Medical information obtained by a modality, for example, a medical image captured by a medical imaging device, is transmitted to a medical information processing apparatus. The medical information processing apparatus performs processes such as analyzing the received medical image along a workflow. The workflow for processing a medical image is determined by, for example, an identification label attached to the medical image. The workflow is configured to include, for example, one or more analysis applications (hereinafter referred to as "apps"). The setting of the workflow defines the flow of processing by the analysis application and the relationship of input / output data.
[0003] The development of analysis applications is carried out every day, and new analysis applications may be released or existing analysis applications may be upgraded. By incorporating these new analysis applications and the like into the workflow, the efficiency of the workflow can be improved. However, it is difficult to determine how to incorporate a new analysis application into the workflow to obtain a great effect, and it is difficult to improve the efficiency of the analysis work.
Prior Art Documents
Patent Documents
[0004]
Patent Document 1
Patent Document 2
Summary of the Invention
Problems to be Solved by the Invention
[0005] The problem that the embodiments disclosed in this specification and drawings aim to solve is to improve the efficiency of analysis work. However, the problems that the embodiments disclosed in this specification and drawings aim to solve are not limited to the above problem. Problems corresponding to the effects of each configuration shown in the embodiments described later can also be positioned as other problems. [Means for solving the problem]
[0006] The medical information processing device of this embodiment includes an acquisition unit and an update unit. The acquisition unit acquires update trigger information related to updating the workflow for processing medical information. The update unit updates the workflow based on the update trigger information. [Brief explanation of the drawing]
[0007] [Figure 1] A block diagram showing an example of the configuration of medical information processing system 1. [Figure 2] A diagram illustrating the flow of medical image analysis in medical information processing system 1. [Figure 3] A diagram showing an example of the configuration of the medical information processing device 100. [Figure 4] A diagram showing an example of the contents of Workflow DB151. [Figure 5] A flowchart illustrating an example of the processing performed by the medical information processing device 100. [Figure 6] A flowchart illustrating an example of the processing performed by the medical information processing device 100. [Figure 7] A flowchart illustrating an example of the processing performed by the medical information processing device 100. [Figure 8] A diagram showing an example of what is displayed on display 130. [Figure 9] A flowchart showing another example of the processing performed by the medical information processing device 100. [Modes for carrying out the invention]
[0008] The following describes the embodiment of the medical information processing device, medical information processing system, medical information processing method, and program with reference to the drawings.
[0009] (First embodiment) Figure 1 is a block diagram showing an example of the configuration of a medical information processing system 1. The medical information processing system 1 includes, for example, a Hospital Information System (HIS) 10, a Radiology Information System (RIS) 20, a medical imaging diagnostic device (modality) 30, a Picture Archiving and Communication System (PACS) 40, and a medical information processing device 100. The medical information processing system 1 is also called an in-hospital system.
[0010] In the medical information processing system 1, HIS10, RIS20, modality30, PACS40, and medical information processing device 100 can communicate with each other via a network NW such as a LAN (Local Area Network). The network NW may include, in addition to or instead of a LAN, the Internet, a cellular network, a Wi-Fi network, a WAN (Wide Area Network), etc. RIS20, modality30, and PACS40 are examples of external devices.
[0011] HIS10 is a computer system that provides operational support within hospitals. Specifically, HIS10 has various subsystems. These subsystems include, for example, an electronic medical record system, a medical accounting system, an appointment scheduling system, a patient registration system, and an admission / discharge management system.
[0012] HIS10 is a computer system that provides operational support within hospitals. Specifically, HIS10 has various subsystems. These subsystems include, for example, an electronic medical record system, a medical accounting system, an appointment scheduling system, a patient registration system, and an admission / discharge management system.
[0013] HIS10 includes computers such as server devices and client terminals that include a processor such as a CPU (Central Processing Unit), a memory such as a ROM (Read Only Memory) and a RAM (Random Access Memory), a display, an input interface, and a communication interface.
[0014] The user inputs or refers to information regarding the patient using the electronic medical record system included in HIS10. The user issues an imaging examination order to HIS10. HIS10 transfers order information corresponding to the imaging examination order to another system such as RIS20.
[0015] RIS20 is a computer system that supports operations in the imaging diagnosis department. In addition to reservation management of imaging examination orders in cooperation with HIS10, RIS20 performs reservation information cooperation with examination devices and management of examination information. RIS20 includes computers such as server devices and client terminals that include a processor such as a CPU, a memory such as a ROM and a RAM, a display, an input interface, and a communication interface.
[0016] RIS20 is a management device that creates or manages an examination workflow indicating the examination procedure of a patient (subject) in the hospital. RIS20 updates, for example, an examination workflow whose processing procedure varies according to a new workflow provided by the medical information processing device 100. The examination workflow is an example of an external workflow.
[0017] Modality 30 executes imaging (shooting) according to shooting conditions (shooting protocol) determined based on, for example, an imaging examination instruction. Examples of Modality 30 include an X-ray computed tomography device (X-ray CT device), an X-ray diagnostic device, a magnetic resonance imaging device, an ultrasonic diagnostic device, a nuclear medicine diagnostic device, and the like. Medical images are, for example, X-ray CT images, magnetic resonance images, echo images, and the like.
[0018] The modality 30 is, for example, operated by a user. The medical image (image data) generated by imaging of the modality 30 is transmitted to the PACS 40 or the medical information processing apparatus 100. The modality 30 executes an examination for acquiring examination information regarding the examination. The examination information is, for example, a medical image, and the execution of the examination is, for example, imaging of a medical image. The modality 30 is an example of an examination apparatus.
[0019] The PACS 40 is a computer system that receives the medical images transmitted by the modality 30 or the medical information processing apparatus 100 and stores them in a database. The PACS 40 transmits (transfers) the medical images stored in the database in response to a request from a client.
[0020] The PACS 40 includes a server computer including a processor such as a CPU, a memory such as a ROM and a RAM, a display, an input interface, and a communication interface. The PACS 40 stores a plurality of medical images. The plurality of medical images include, for example, medical images imaged at different times for each of a plurality of subjects. The PACS 40 is an example of an image storage apparatus.
[0021] The configuration of the in-hospital system H is not limited to the above. The in-hospital system H may include, for example, a radiology report creation apparatus or the like. Also, some elements of the in-hospital system H may be integrated. For example, the HIS 10 and the RIS 20 may be integrated into one system.
[0022] The medical information processing system 1 is, for example, a system that performs image processing and the like on a medical image imaged by the modality 30 to generate an analysis result (analysis image) and provides it to the modality 30 or the PACS 40. FIG. 2 is a diagram for explaining the flow of analysis of a medical image in the medical information processing system 1.
[0023] In the medical information processing system 1, first, medical images (pre-analysis images) acquired by modality 30 or stored in PACS 40 are transmitted as analysis information from modality 30 or PACS 40 to the medical information processing device 100. The medical information processing device 100 performs analysis on the transmitted pre-analysis images using image processing and other methods to generate an analysis image as the analysis result. The medical information processing device 100 then transmits the generated analysis image to the developer terminal 50 used by the developer, PACS 40, modality 30, etc.
[0024] The viewer included in the developer terminal 50, the PACS viewer 45 included in the PACS 40, and the modality viewer 35 included in the modality 30 each display the transmitted analysis images on a monitor or display. Developers using the developer terminal 50, and hospital staff, technicians, and doctors using the PACS 40 and modality 30, can view the analysis images displayed on a display or monitor using the PACS viewer 45 or modality viewer 35.
[0025] Next, the medical information processing device 100 will be described. Figure 3 shows an example of the configuration of the medical information processing device 100. The medical information processing device 100 includes, for example, a communication interface 110, an input interface 120, a display 130, a processing circuit 140, and a memory 150.
[0026] The communication interface 110 communicates with external devices such as client terminals 200 on a LAN via a network NW (Figure 1). The communication interface 110 includes, for example, a communication interface such as a NIC (Network Interface Card).
[0027] The input interface 120 receives various input operations from administrators and others who manage the medical information processing device 100. The input interface 120 converts the received input operations into electrical signals and outputs them to the processing circuit 140. When an input operation is performed by an administrator or others, the input interface 120 generates information corresponding to the input operation. The input interface 120 outputs the generated information corresponding to the input operation to the processing circuit 140.
[0028] The input interface 120 includes, for example, a mouse, keyboard, trackball, switch, button, joystick, touch panel, etc. The input interface 120 may also be a user interface that accepts audio input, such as a microphone. If the input interface 120 is a touch panel, the input interface 120 may also have the display function of the display 130.
[0029] 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 an electrical signal corresponding to an input operation from an external input device located separately from the device and outputs this electrical signal to the processing circuit 140 is also included as an example of an input interface.
[0030] The display 130 displays various types of information. For example, the display 130 displays images generated by the processing circuit 140, or a GUI (Graphical User Interface) for receiving various input operations from the operator. For example, the display 130 may be an LCD (Liquid Crystal Display), a CRT (Cathode Ray Tube) display, or an organic EL (Electro Luminescence) display.
[0031] The processing circuit 140 includes, for example, an acquisition function 141, an analysis function 142, an update function 143, and a provision function 144. The processing circuit 140 realizes these functions, for example, by a hardware processor (computer) executing a program stored in the memory (storage circuit) 150.
[0032] Hardware processors refer to circuits such as CPUs, GPUs (Graphics Processing Units), Application Specific Integrated Circuits (ASICs), and programmable logic devices (e.g., Simple Programmable Logic Devices (SPLDs), Complex Programmable Logic Devices (CPLDs), and Field Programmable Gate Arrays (FPGAs)).
[0033] Instead of storing the program in memory 150, the system may be configured to directly incorporate the program into the hardware processor's circuitry. In this case, the hardware processor performs its function by reading and executing the program incorporated into the circuitry. The program may be stored in memory 150 beforehand, or it may be stored on a non-temporary storage medium such as a DVD or CD-ROM, and installed from the non-temporary storage medium to memory 150 when the non-temporary storage medium is mounted on the drive device (not shown) of the medical information processing device 100.
[0034] The hardware processor is not limited to being configured as a single circuit; it may be configured as a single hardware processor by combining multiple independent circuits to realize each function. Alternatively, multiple components may be integrated into a single hardware processor to realize each function. The hardware processor and memory in the medical information processing device 100 are provided separately from the hardware processor and memory in the HIS 10, but they may be common to each other.
[0035] Memory 150 stores a workflow database (hereinafter referred to as DB) 151. The workflow DB 151 stores multiple workflows for image processing of medical images by the medical information processing device 100. For example, a workflow is set for each identification label assigned to a medical image. One of the workflows stored in the workflow DB 151 is assigned to the image processing of the medical image.
[0036] Figure 4 shows an example of the contents of Workflow DB151. Workflow DB151 contains information about each item for each WF name. These items include, for example, an identification label, the analysis application used in the workflow (hereinafter referred to as the application used), the manufacturer, modality, slice thickness, processing time, resources, and accuracy. In addition, Workflow DB151 may also contain information such as the amount (cost), number of executions, and trends, and this information may be updated as needed.
[0037] The acquisition function 141 includes, for example, a medical information acquisition function 147 and an update trigger acquisition function 148. The medical information acquisition function 147 acquires medical images transmitted by modality 30 or PACS 40. The medical information acquisition function 147 also acquires supplementary information to fill in any missing data when creating a new workflow. The acquisition function 141 is an example of an acquisition unit.
[0038] The update trigger acquisition function 148 acquires update trigger information regarding updates to the workflow for processing medical information. The update trigger information includes, for example, change information. The change information includes, for example, information on changes to at least one of the following: identification labels included in the workflow, applications used, modality information regarding the modality from which the medical information was acquired, workflow processing time, resources, accuracy, cost, number of executions, trends, or user reviews. The change information includes changes to the inspection workflow managed by RIS20. The update trigger acquisition function 148 acquires update trigger information, for example, after a certain period or a specified period has elapsed.
[0039] The analysis function 142 analyzes medical information according to the workflow. For example, based on medical images acquired by the medical information acquisition function 147, the analysis function 142 selects an appropriate workflow for analysis from the workflows included in the workflow DB 151. The analysis function 142 then analyzes the medical images using the selected workflow. The analysis function 142 is an example of an analysis unit.
[0040] The update function 143 updates the workflow based on update trigger information. For example, when update trigger information is obtained by the update trigger acquisition function 148, the update function 143 updates the workflow based on the acquired update trigger information. Workflow updates include updates that modify a part of an existing workflow and updates that create a new workflow. The update function 143 is an example of an update unit.
[0041] The provided function 144 provides comparison information to compare the status before and after a workflow update. For example, when the update function 143 updates a workflow or attempts to update a workflow, the provided function 144 displays the status before and after the workflow update on the display 130, outputs audio, or transmits it to external devices such as the RIS20 or a user terminal used by the user.
[0042] The comparison information provided by the provisioning function 144 includes information comparing at least some of the elements of the workflow before and after the update. The update function 143 switches the workflow assigned to the processing of medical images based, for example, on the response to the comparison information provided by the provisioning function 144. The provisioning function 144 is an example of a provisioning unit.
[0043] The update function 143 can create a new workflow that includes the missing data. The provision function 144 sends supplementation request information to the RIS20, modality 30, PACS40, etc., when it is possible to request supplementation of the missing data from the RIS20, modality 30, PACS40, etc. Missing data includes, for example, the results of examinations performed by modality 30 and medical images stored in PACS40. Supplementation request information includes, for example, a request for the provision of examination information obtained as a result of examinations performed by modality 30 and a request for the provision of medical images stored in PACS40.
[0044] Next, the processing of the medical information processing device 100 of the embodiment will be described. Figures 5 to 7 are flowcharts showing examples of the processing of the medical information processing device 100. The medical information processing device 100 is a device that analyzes medical images (pre-analysis images) acquired by modality 30 or stored in PACS 40. The medical information processing device 100 of the embodiment also has a function to appropriately update the workflow used for analyzing pre-analysis images. Therefore, the processing of medical images in the medical information processing device 100 will first be explained with reference to Figure 5.
[0045] When analyzing medical images, the medical information processing device 100 first determines, using the medical information acquisition function 147, whether or not it has acquired the pre-analysis image, which will be transmitted as analysis information by modality 30 or PACS 40 (step S101). If it determines that it has not acquired the analysis information, the medical information acquisition function 147 repeats the process in step S101.
[0046] When the medical information acquisition function 147 determines that analysis information has been acquired, the analysis function 142 selects a workflow to be used for analysis based on the identification label information attached to the acquired analysis information (pre-analysis image) (step S103). The workflow selection may also be based on information other than the identification label information, for example, on any information that can define the workflow, such as the data type or DICOM (Digital Imaging and Communication in Medicine) tags. The workflow selection is performed by the analysis function 142, but it may also be performed by the user specifying a workflow by operating the input interface 120.
[0047] Next, the analysis function 142 performs an analysis on the pre-analysis image acquired by the medical information acquisition function 147 according to the selected workflow (step S105) and generates an analysis image. Subsequently, the provision function 144 provides the analysis image generated by the analysis function 142 as the analysis result (step S107). In this way, the medical information processing device 100 completes the process shown in Figure 5.
[0048] Next, the process of updating the workflow using the medical information processing device 100 will be described. Figure 6 shows the procedure for updating the workflow in the medical information processing device 100. When updating the workflow, the medical information processing device 100 first determines whether a certain period has elapsed for updating the workflow using the update trigger acquisition function 148 (step S201). The certain period can be any period, for example, it can be one day, one week, or one month. Instead of a certain period, it can be a specified period designated by the user.
[0049] If it is determined that a certain period of time has elapsed, the update trigger acquisition function 148 checks for the presence or absence of update trigger information (step S203). The update trigger acquisition function 148 checks for update trigger information by, for example, checking with the provider of the analysis application for updates to the application used in the workflow or for the presence or absence of an analysis application that can replace the application used, or by checking for replacement or version upgrade of modality 30, or changes in the workflow or operations within the hospital.
[0050] The update trigger acquisition function 148 checks for updates to the application being used or the availability of alternative analysis applications. For example, it checks whether an unpurchased analysis application has been released on the app store. The update trigger acquisition function 148 also checks for the release of a new version of the application being used, when common processes such as image alignment are separated into a separate analysis application, and when a post-processing application is integrated with that analysis application.
[0051] These analytics apps can be verified not only from the app store, but also by obtaining information about the analytics apps through other means, such as checking the website of the provider of the analytics app. If it is determined that a certain period of time has not elapsed, the update trigger acquisition function 148 skips the processing in step S203.
[0052] Next, the update trigger acquisition function 148 determines whether or not it has acquired update trigger information (step S205). In addition to checking the update trigger information in step S203, the update trigger acquisition function 148 also acquires update trigger information, for example, by receiving notification from the provider of the application that the application has been updated.
[0053] If the update trigger acquisition function 148 determines that it has not acquired update trigger information, the medical information processing device 100 terminates the process shown in Figure 6. If the update trigger acquisition function 148 determines that it has acquired update trigger information, the update function 143 updates the existing workflow and generates a new workflow based on the update trigger information acquired by the update trigger acquisition function 148 (step S207). The update function 143 generates a new workflow that, for example, improves performance, resources, and accuracy compared to the existing workflow. In addition, the update function 143 may generate a new workflow by replacing the applications used in the existing workflow with applications that have received positive reviews from users.
[0054] Next, the provision function 144 registers the new workflow, generated by updating the existing workflow via the update function 143, in the memory 150 (step S209). In the memory 150, the provision of the new workflow updates the workflow DB 151, adding the new workflow to the workflow DB 151, and, if necessary, deleting the existing workflow from the workflow DB 151. In this way, the medical information processing device 100 completes the process shown in Figure 6.
[0055] Next, the processing in the medical information processing device 100 after a new workflow has been registered will be explained with reference to Figure 7. Figure 7 shows the procedure for processing in the medical information processing device 100 after a new workflow has been registered. First, the medical information processing device 100 determines whether or not there is a newly registered workflow in the update function 143 (step S301).
[0056] If the update function 143 determines that there are no registered new workflows, the medical information processing device 100 terminates the process shown in Figure 7. If the update function 143 determines that there are registered new workflows, the provision function 144 displays an update confirmation screen on the display 130 (step S303). The update confirmation screen is confirmed, for example, by a user operating the medical information processing device 100.
[0057] Figure 8 shows an example of the content displayed on display 130. Display 130, which displays the update confirmation screen, shows the existing workflow image GA11, the new workflow image GA12, the user review image GA21, the data type image GA22, the change explanation image GA23, and the switch instruction image GA24. The update confirmation screen is comparison information provided by the provided function 144.
[0058] Image GA11 of the existing workflow is an image that explains the processing flow of the pre-update workflow (existing workflow). Image GA11 shows, for example, the process in which the pre-analysis image is analyzed by apps A and B to generate the analyzed image. Image GA12 of the new workflow is an image that explains the processing flow of the updated workflow (new workflow). Image GA12 shows, for example, the process in which the pre-analysis image is pre-processed by a pre-processing app, and then analyzed by apps A and B to generate the analyzed image.
[0059] The user review image GA21 displays ratings and reviews of the new workflow and the analysis apps used in the new workflow, such as App A and App B, from users who have previously used the new workflow or the analysis apps used in the new workflow. In the example shown in Figure 8, the rating of the new workflow is shown with a number of stars. The user review image GA21 may also include text data.
[0060] The data type image GA22 displays information such as the name of the company that manufactured the analysis application and modality 30 used in the new workflow, the type of modality 30 used for image generation (image acquisition), and the slice thickness of the image to be acquired. The data type may display information related to the data type, as well as other information.
[0061] The change explanation image GA23 displays information such as the changes in the existing workflow, the new workflow, and various other items. These items include processing time, resources, accuracy, cost, number of executions, and trends. In the example shown in Figure 8, processing time was reduced by 5 minutes, resource usage was reduced by 5 MB, accuracy became moderate, and cost was reduced by 100 yen per execution. The number of executions shows the number of times the new workflow was executed (including executions by other hospitals, etc.), and the trend shows an increase of 100 executions per week, indicating a sharp rise in usage.
[0062] The switching instruction image GA24 includes information that allows the user to choose whether or not to send switching information to the update function 143 to switch the processing assigned to the existing workflow from the existing workflow to the new workflow. The switching information is the response to the comparison information provided by the provision function 144. The switching instruction image GA24 displays the text information, "Switching to the new workflow will reduce the total processing time by 5 minutes. Do you want to switch?", along with "Yes" and "No" button images.
[0063] The user can specify a button image by operating the input interface 120. The user decides whether to switch the process assigned to the existing workflow to the new workflow while viewing the update confirmation screen. If the user wants to switch the process to the new workflow, they input "Yes," and the input interface 120 sends the switching information to the update function 143 in response to the user's input. If the user wants to keep the process in the existing workflow, they input "No." In this case, no switching information is sent, and the existing workflow is maintained.
[0064] Returning to the flow shown in Figure 7, the update function 143 determines whether or not it has acquired the switching information transmitted by the input interface 120 (step S305). If it determines that it has acquired the switching information, the update function 143 switches the workflow assigned to the processing of the medical image (image before analysis) (step S307). In this way, the medical information processing device 100 terminates the process shown in Figure 7. If the update function 143 determines that it has not acquired the switching information, the medical information processing device 100 terminates the process shown in Figure 7.
[0065] The medical information processing device 100 of the first embodiment updates the workflow when it receives update trigger information, such as the release of a new analysis application. Therefore, it can generate a new workflow that enables efficient analysis, or update and generate an existing workflow. Consequently, the efficiency of analysis work can be improved.
[0066] (Second embodiment) Next, a medical information processing device of the second embodiment will be described. The medical information processing device 100 of the second embodiment has the same configuration as the medical information processing device 100 of the first embodiment, but the processing in the processing circuit 140 is the main difference. The medical information processing device 100 of the second embodiment will be described below, focusing on the differences from the first embodiment.
[0067] Figure 9 is a flowchart showing an example of the processing of the medical information processing device 100 in the second embodiment. First, the medical information processing device 100 in the second embodiment determines whether a certain period has elapsed for updating the workflow using the update trigger acquisition function 148 (step S401). If it is determined that a certain period has elapsed, the update trigger acquisition function 148 checks for the presence or absence of update trigger information (step S403).
[0068] If it is determined that a certain period of time has not elapsed, the update trigger acquisition function 148 skips the process in step S303. Next, the update trigger acquisition function 148 determines whether or not it has acquired update trigger information (step S405). If the update trigger acquisition function 148 determines that it has not acquired update trigger information, the medical information processing device 100 terminates the process shown in Figure 9. Up to this point, the medical information processing device 100 performs the same processing as in the first embodiment.
[0069] Next, the update function 143 plans the update of the workflow (step S407). Planning the update of the workflow involves, for example, generating candidate workflows that could become the new workflow using the procedure used to generate the new workflow in the first embodiment. Subsequently, the update function 143 determines whether there is any missing data that would be missing when executing the candidate workflow (step S409).
[0070] Missing data is, for example, when an existing workflow and a candidate workflow are executed by App B on the current medical image (the result of the current examination). In this case, the candidate workflow will use the examination results of App A for past examinations that were not used in the existing workflow. In this case, if the examination results of App A are not used in the existing workflow, the update function 143 will determine that the examination results of App A are missing data. Similarly, the update function 143 will determine that data is missing if there is data that, if present, would enable the candidate workflow to be implemented.
[0071] Next, the update function 143 performs a process to replenish the missing data (step S411). The process to replenish the missing data is a process to supplement the process for obtaining the missing data. For example, if the test results of app A are determined to be missing data, the process to obtain past test results of app A for the subject being tested is supplemented from modality 30 or PACS 40. The process to replenish the missing data may, for example, supplement the process to retrieve and obtain existing past data, or, if it is necessary to obtain new data instead of existing data, supplement the process to request a test from modality 30 and obtain the test results.
[0072] If it is determined in step S409 that there is no missing data, the update function 143 skips the processing in step S411. Subsequently, the update function 143 processes the missing data and then updates the workflow by generating the candidate workflow as a new workflow (step S413).
[0073] Next, the provisioning function 144 determines whether or not there is any information to provide to the external devices (step S415). The information to provide includes, for example, supplementary request information that requests the transmission of missing data to PACS40 or requests a new test from Modality 30, and new workflows when the hospital's test workflow managed by RIS20 is changed due to an update in the workflow. The provisioning function 144 sends the supplementary request information as information to the external devices such as RIS20, Modality 30, and PACS40.
[0074] If the provision function 144 determines that there is information to be provided, it provides the information to external devices such as RIS20, modality 30, and PACS by transmitting the information using the communication interface 110 (step S417). If the provision function 144 determines that there is no information to be provided, it skips the process in step S417. Subsequently, the update function 143 registers the new workflow in the workflow DB 151 (step S419). In this way, the medical information processing device 100 completes the process shown in Figure 9.
[0075] The medical information processing device 100 of the second embodiment provides the same effects as the medical information processing device 100 of the first embodiment. Furthermore, the medical information processing device 100 of the second embodiment requests an external device to provide any missing data when generating a new workflow. This increases the number of types of new workflows that can be generated.
[0076] In the above embodiment, an example of updating a workflow from an existing workflow to a new workflow was described. However, the medical information processing device 100 may create the new workflow and compare it with the existing workflow before registering the new workflow in the workflow DB 151. In this case, the medical information processing device 100 can display the update confirmation screen shown in Figure 8 to provide the user with comparison information between the existing workflow and the new workflow. Therefore, when a new application is released or an existing application is updated, the system can generate a new workflow and display the comparison results with the existing workflow to provide the user with information to consider whether or not to introduce the new or updated application.
[0077] According to at least one embodiment described above, the medical information processing device has an acquisition unit that acquires update trigger information relating to the update of the workflow for processing medical information, and an update unit that updates the workflow based on the update trigger information, thereby improving the efficiency of the analysis work.
[0078] 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 carried out in a variety of other forms, and various omissions, substitutions, and modifications can be made 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]
[0079] 1. Medical Information Processing System 30 Modalities 35 Modality Viewer 45 PACS Viewer 40 PACS 50 Developer terminals 100 Medical Information Processing Devices 110 Communication Interface 120 Input Interfaces 130 displays 140 Processing Circuits 141 Acquisition function 142 Analysis Functions 143 Update function 144 Provided functions 147 Medical information acquisition function 148 Update trigger acquisition function 150 memory 151 Workflow DB 200 client terminals GA11 Existing Workflow Image GA12 New Workflow Image GA21 User Review Images GA22 Data Type Image GA23 Change Explanation Image GA24 Switching Instruction Image H Hospital System NW Network
Claims
1. An acquisition unit that acquires update trigger information related to updates to the workflow for processing medical information, The system includes an update unit that updates the workflow based on the update trigger information, Medical information processing device.
2. The update trigger information includes an identification label included in the workflow, the application used, modality information relating to the modality from which the medical information was obtained, and change information relating to at least one of the following changes: workflow processing time, resources, accuracy, cost, number of runs, trend, or user review. The medical information processing device according to claim 1.
3. The acquisition unit acquires the update trigger information at regular intervals or specified intervals. The medical information processing device according to claim 1.
4. The system further includes a unit that provides comparative information to compare the status before and after the update of the aforementioned workflow. The update unit updates the workflow based on the response to the comparison information. The medical information processing device according to claim 1.
5. The comparison information includes information comparing at least some of the elements of the workflow before and after the update. The medical information processing device according to claim 4.
6. The system further includes an analysis unit that analyzes the medical information in accordance with the aforementioned workflow. The medical information processing device according to claim 1.
7. The aforementioned update unit can create a new workflow that includes the missing data. The system further includes a provision unit that provides supplement request information requesting the supplementation of the aforementioned missing data. The acquisition unit acquires supplementary information corresponding to the supplementary request information. The medical information processing device according to claim 1.
8. A medical information processing device according to claim 7, The medical information processing device comprises an external device capable of communicating with the aforementioned medical information processing device, The medical information processing device further comprises a providing unit that provides the supplement request information to the external device, The external device provides the medical information processing device with Medical information processing system.
9. The aforementioned supplementary information is a medical image. The external device includes an image storage device for storing a plurality of the medical images. The medical information processing system according to claim 8.
10. The aforementioned supplement request information includes inspection information related to the inspection, The external device includes an inspection device that performs the inspection, The medical information processing system according to claim 8.
11. A medical information processing device according to claim 1, The system includes an external device that can communicate with the aforementioned medical information processing device and manages an external workflow whose processing procedure varies according to the workflow, The supply unit provides the external device with information regarding the updated workflow. Medical information processing system.
12. Computers Retrieve update trigger information related to updates in the medical information processing workflow. Based on the update trigger information, update the workflow. Medical information processing method.
13. On the computer, Retrieve update trigger information related to updates in the medical information processing workflow. The workflow is updated based on the update trigger information. program.
Citation Information
Patent Citations
Workflow generation server and method
JP2014048673A
Medical image processing device, medical image processing method, and processing program for use in the same
JP2019054896A
