Medical information processing system, determination method, and program

Abstract

The present disclosure relates to a medical information processing system, a determination method, and a program for preventing inappropriate use of medical device software. A list management unit manages a software list in which contraindication information is set for each registered software. An information acquiring unit acquires patient information regarding a patient for which requested software requested to be started is used, and device information regarding an electronic device used for the patient. A contraindication determination unit determines whether the starting of the requested software should be considered contraindicated, depending on whether the patient information or the device information corresponds to the contraindication information set for the requested software in the software list. The present disclosure is applicable to a operating room system.

Description

[Technical Field]

[0001] The present disclosure relates to a medical information processing system, a determination method, and a program, and more particularly to a medical information processing system, a determination method, and a program that can prevent inappropriate use of medical device software. [Background technology]

[0002] In the operating room, measures are taken to prevent serious mistakes by double-checking at many points, such as confirming the name of the surgeon entering the room, the medication being administered to the patient, and the surgical procedure and surgical site at the start of surgery.

[0003] A medical procedure that is prohibited because it is inappropriate for a particular disease and has adverse effects is called a contraindication. The various checks mentioned above are also carried out to prevent contraindications.

[0004] For example, Patent Document 1 describes a method of detecting drugs and instruments used in an endoscopic examination by image processing, and determining whether the detected drugs and instruments violate the patient's contraindication information. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2018-92673 Summary of the Invention [Problem to be solved by the invention]

[0006] With the recent spread of medical device software, it is expected that certain software will become contraindicated for certain diseases in the future. It is desirable that such software contraindications be checked by a system.

[0007] The present disclosure has been made in light of these circumstances, and is capable of preventing inappropriate use of medical device software. [Means for solving the problem]

[0008] The medical information processing system disclosed herein is a medical information processing system that includes a list management unit that manages a software list in which contraindication information is set for each registered software, an information acquisition unit that acquires patient information regarding the patient in whose system the requested software requested to be started is used and device information regarding the electronic device used by the patient, and a contraindication determination unit that determines whether or not the start-up of the requested software should be contraindicated depending on whether or not the patient information or the device information corresponds to the contraindication information set for the requested software in the software list.

[0009] The determination method disclosed herein is a determination method in which a medical information processing system manages a software list in which contraindication information is set for each registered software, acquires patient information about a patient who will use the requested software whose startup is requested, and device information about an electronic device used by the patient, and determines whether or not the startup of the requested software should be contraindicated depending on whether or not the patient information or the device information corresponds to the contraindication information set for the requested software in the software list.

[0010] The program disclosed herein is a program that manages a software list on a computer in which contraindication information is set for each registered software, acquires patient information about a patient for whom requested software to be launched is used and device information about an electronic device used by the patient, and determines whether or not the launch of the requested software should be contraindicated depending on whether or not the patient information or the device information corresponds to the contraindication information set for the requested software in the software list.

[0011] In the present disclosure, a software list in which contraindication information is set for each registered software is managed, patient information regarding the patient on whose behalf the requested software is to be launched and device information regarding the electronic device used by the patient are obtained, and whether or not the launch of the requested software should be contraindicated is determined depending on whether or not the patient information or the device information corresponds to the contraindication information set for the requested software in the software list. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram showing an overview of an operating room system to which the technology disclosed herein can be applied. [Figure 2] FIG. 2 is a block diagram illustrating an example of a functional configuration of a medical information processing system. [Figure 3] 10 is a flowchart illustrating a flow of a software activation determination process. [Figure 4] FIG. 10 is a diagram illustrating an example of a software list. [Figure 5] FIG. 10 is a block diagram showing another example of the functional configuration of the medical information processing system. [Figure 6] 10 is a flowchart illustrating a flow of a software activation determination process. [Figure 7] FIG. 10 is a diagram illustrating an example of a warning screen. [Figure 8] 10 is a flowchart illustrating a flow of a software activation determination process. [Figure 9] FIG. 10 is a diagram illustrating another example of a software list. [Figure 10] FIG. 10 is a block diagram showing yet another example of the functional configuration of the medical information processing system. [Figure 11] 10 is a flowchart illustrating the flow of a list update process. [Figure 12] 10 is a flowchart illustrating a flow of a software activation determination process. [Figure 13] FIG. 10 is a block diagram showing yet another example of the functional configuration of the medical information processing system. [Figure 14] 10 is a flowchart illustrating a flow of a software activation determination process. [Figure 15] 10 is a flowchart illustrating a flow of a software activation determination process. [Figure 16] FIG. 1 illustrates an example of the configuration of a computer. DETAILED DESCRIPTION OF THE INVENTION

[0013] Modes for carrying out the present disclosure (hereinafter referred to as embodiments) will be described below in the following order.

[0014] 1. Background 2. Overview of Operating Room System 3. First embodiment (Determination of software activation based on taboo information) 4. Second embodiment (software activation determination including warning display) 5. Third embodiment (Determination of software activation in an emergency) 6. Fourth embodiment (updating software list and software activation determination) 7. Fifth embodiment (Determination of software activation in response to updates of contraindication information and patient information) 8. Sixth embodiment (Determination of software activation based on conditional taboo information) 9. Computer configuration example

[0015] <1. Background> In the operating room, measures are taken to prevent serious mistakes by double-checking at many points, such as confirming the name of the surgeon entering the room, the medication being administered to the patient, and the surgical procedure and surgical site at the start of surgery.

[0016] A medical procedure that is prohibited because it is inappropriate for a particular disease and has adverse effects is called a contraindication. The various checks mentioned above are also carried out to prevent contraindications.

[0017] However, even in today's world where double-checking by doctors and nurses has become common practice, there are still many cases where patients suffer serious harm due to the performance of contraindicated procedures caused by human error.

[0018] With the recent widespread use of medical device software, it is expected that in the future, certain software will become contraindicated for certain diseases, i.e., the use of medical device software itself will become a contraindication for patients.

[0019] It is desirable that such software-related taboos be checked by a system in order to eliminate human error.

[0020] Therefore, the technology disclosed herein prevents inappropriate use of medical device software by determining whether the startup of the medical device software should be prohibited due to concerns that the startup may have adverse effects due to patient-specific factors, and then controlling the startup of the software.

[0021] <2. Overview of Operating Room System> FIG. 1 is a diagram showing an overview of an operating room system 100 to which the technology according to the present disclosure can be applied.

[0022] In the operating room system 100 shown in Fig. 1, a group of devices installed in an operating room are connected to each other so that they can cooperate with each other via an operating room controller (OR Controller) 107 and an input / output controller (I / F Controller) 109. The operating room system 100 is configured with an IP (Internet Protocol) network capable of sending and receiving 4K / 8K images, and input / output images and control information for each device are sent and received via the IP network.

[0023] A variety of devices may be installed in an operating room.

[0024] 1 shows a group of various devices 101 for endoscopic surgery, a ceiling camera 187 that captures images of the surgeon's hands, an operating room camera 189 that captures images of the entire operating room, multiple display devices 103A to 103D, a patient bed 183, and lighting 191. Both the ceiling camera 187 and the operating room camera 189 are installed on the ceiling of the operating room. In addition to the endoscope shown in the figure, the group of devices 101 may include various medical devices that acquire images, such as a master-slave endoscopic surgery robot or an X-ray device.

[0025] The display devices 103A to 103C, the device group 101, the ceiling camera 187, and the operating room camera 189 are connected to the input / output controller 109 via IP converters 115A to 115F, respectively. Hereinafter, when there is no need to distinguish between the IP converters 115A to 115F, they will simply be referred to as IP converters 115.

[0026] IP converters 115D, 115E, and 115F on the input source side (camera side) that input images convert images from individual medical imaging devices (endoscopes, surgical microscopes, X-ray imaging devices, operating room cameras, pathology imaging devices, etc.) into IP formats and transmit them over the network. IP converters 115A to 115C on the image output side (monitor side) that output images convert images transmitted over the network into a format specific to the monitor and output them. The IP converter 115 on the input source side functions as an encoder, and the IP converter 115 on the image output side functions as a decoder. Input sources include, for example, video sources.

[0027] The IP converter 115 can have various image processing functions. For example, the IP converter 115 can have functions to perform resolution conversion processing according to the output destination, rotation correction and image stabilization of the endoscopic image, object recognition processing, partial processing such as feature information extraction for analysis in the server described later, and the like.

[0028] These image processing functions may be inherent to the connected medical imaging device, or may be externally upgradeable. The IP converter 115 on the image output side (monitor side) can also perform processing such as combining multiple images (such as PinP processing) and superimposing annotation information.

[0029] The protocol conversion function of the IP converter 115 is a function of converting a received signal into a converted signal that conforms to a communication protocol that can be communicated over a network such as the Internet. Any communication protocol may be set as the communication protocol. Furthermore, the protocol-convertible signal received by the IP converter 115 is a digital signal, such as an image signal or a pixel signal. The IP converter 115 may be incorporated inside a device on the input source side or inside a device on the image output side.

[0030] The device group 101, for example, belongs to an endoscopic surgery system and includes an endoscope and a display device that displays images captured by the endoscope. On the other hand, the display devices 103A to 103D, the patient bed 183, and the lighting 191 are devices installed in an operating room separately from the endoscopic surgery system. These devices used for surgery or diagnosis are also called medical devices. The operating room controller 107 and / or the input / output controller 109 control the operation of these medical devices in a coordinated manner. Furthermore, if the operating room includes a surgical robot (surgical master-slave) system, a medical image acquisition device such as an X-ray device, or the like, these devices may also be connected to the device group 101.

[0031] The operating room controller 107 comprehensively controls the processing related to image display in the medical equipment.

[0032] Among the devices included in the operating room system 100, the device group 101, the ceiling camera 187, and the operating room camera 189 may be devices (hereinafter also referred to as source devices) that have the function of transmitting information to be displayed during surgery (hereinafter also referred to as display information). Also, the display devices 103A to 103D may be devices (hereinafter also referred to as destination devices) that output display information.

[0033] The operating room controller 107 has the function of controlling the operation of the source device and the destination device, acquiring display information from the source device, and transmitting the display information to the destination device for display or recording. The display information includes various images captured during surgery and various information related to the surgery (for example, physical information about the patient, past test results, information about the surgical procedure, etc.).

[0034] Specifically, the operating room controller 107 may receive, as display information from the device group 101, information about an image of the operating site inside the patient's body cavity captured by an endoscope. The operating room controller 107 may also receive, as display information from the ceiling camera 187, information about an image of the surgeon's hands captured by the ceiling camera 187. The operating room controller 107 may also receive, as display information from the operating room camera 189, information about an image showing the overall state of the operating room captured by the operating room camera 189. If other devices with imaging capabilities are present in the operating room system 100, the operating room controller 107 may also obtain, as display information, information about images captured by the other devices from the other devices.

[0035] The operating room controller 107 displays the acquired display information (i.e., images captured during surgery and various pieces of information related to the surgery) on at least one of the display devices 103A to 103D, which are output destination devices. In the example of FIG. 1, the display device 103A is a display device hung from the ceiling of the operating room, and the display device 103B is a display device installed on a wall of the operating room. The display device 103C is a display device installed on a desk in the operating room, and the display device 103D is a mobile device with a display function (for example, a tablet PC (Personal Computer) or a smartphone).

[0036] The input / output controller 109 is configured as one of the input / output controllers that control the input / output of image signals to the connected devices. For example, the input / output controller 109 controls the input / output of image signals based on the control of the operating room controller 107. The input / output controller 109 is configured, for example, as an IP switcher, and controls high-speed transfer of image signals between devices arranged on an IP network.

[0037] The operating room system 100 may also include devices external to the operating room. Such devices may include, for example, a server connected to a network established inside or outside the hospital, a PC used by medical staff, or a projector installed in a hospital conference room. When such external devices are located outside the hospital, the operating room controller 107 can display information on a display device in another hospital via a video conference system or the like for remote medical care.

[0038] The external server 113 may be, for example, an in-hospital server or a cloud server outside the operating room, and may be used for image analysis, data analysis, etc. In this case, image information from within the operating room is transmitted to the external server 113, and additional information may be generated by the external server 113 through big data analysis or recognition and analysis processing using AI (machine learning), and fed back to a display device within the operating room. At this time, an IP converter 115H connected to an input / output controller 109 within the operating room transmits data to the external server 113 and analyzes the image. The transmitted data may be the surgical image itself, such as an endoscopic image, metadata extracted from the image, or data indicating the operating status of connected equipment.

[0039] The operating room system 100 is provided with a centralized operation panel 111. A user can issue instructions to the operating room controller 107 regarding input / output control of the input / output controller 109 and instructions regarding the operation of connected devices via the centralized operation panel 111. The user can also switch image displays via the centralized operation panel 111. The centralized operation panel 111 is configured by providing a touch panel on the display surface of a display device. The centralized operation panel 111 and the input / output controller 109 are connected via an IP converter 115J.

[0040] In the operating room system 100, the IP network may be configured as a wired network, or part or all of the IP network may be configured as a wireless network. For example, an IP converter 115 on the input source side having a wireless communication function may transmit a received image to an IP converter 115 on the image output side via a wireless communication network such as a fifth generation mobile communication system (5G) or a sixth generation mobile communication system (6G).

[0041] An example of the functional configuration of the operating room system 100 according to an embodiment of the present disclosure will be described below.

[0042] 3. First Embodiment (Example of functional configuration of operating room system) FIG. 2 is a diagram illustrating an example of the functional configuration of the operating room system 100 according to the first embodiment of the present disclosure.

[0043] The operating room system 100 of FIG. 2 is configured to include an electronic medical record system 210, an endoscopic camera 220, an operating room camera 230, and a medical information processing system 300.

[0044] The electronic medical record system 210, the endoscope camera 220, and the operating room camera 230 are examples of electronic devices configured as an information management system for inputting information about patients (patient information), or as input sources for inputting the above-mentioned images and information about each electronic device (device information). Hereinafter, these electronic devices are collectively referred to as sources.

[0045] The electronic medical record system 210 manages electronic medical records, which are medical information for each patient, and inputs the records into the medical information processing system 300.

[0046] The endoscopic camera 220 is one of the medical imaging devices included in the above-mentioned device group 101 that constitutes the endoscopic surgery system, and inputs the captured endoscopic images into the medical information processing system 300.

[0047] The operating room camera 230 is one of the imaging devices that capture images of the inside of an operating room, such as the ceiling camera 187 and the operating room camera 189 described above, and inputs the captured images of the operating room into the medical information processing system 300.

[0048] The medical information processing system 300 is configured as a medical platform system capable of executing multiple installed medical device software programs. In response to a request to start medical device software programs from users, such as doctors and nurses, who are surgical staff, the medical information processing system 300 controls the start of the medical device software programs based on data such as electronic medical records and images acquired from the above-mentioned sources. Hereinafter, patient information and device information such as electronic medical records and images acquired from the sources are also referred to as acquired information.

[0049] The medical device software in this context refers to application software that is executed to realize various functions related to surgery performed in the operating room. The execution of the medical device software uses information obtained from various sources as necessary.

[0050] The medical information processing system 300 may be realized by a single device such as the operating room controller 107 or the external server 113 described above, or may be realized by these multiple devices operating in cooperation with each other.

[0051] The medical information processing system 300 is configured to include a software list management unit 311 , a source identification unit 312 , an information acquisition unit 313 , an analysis processing unit 314 , a contraindication determination unit 315 , and a startup processing unit 316 .

[0052] The software list management unit 311 manages a software list, which is a list of various software programs executed by the medical information processing system 300. The software list is managed for each patient. Software registered in the software list (registered software) is set with contraindication information, which serves as a criterion for determining whether the startup of the software should be contraindicated. For example, when medical device software is installed in the medical information processing system 300, the contraindication information that has been compressed and saved is expanded and set.

[0053] In addition, the software list includes a reference source (electronic device) for each registered software. Whether or not the activation of each registered software should be prohibited is determined based on information obtained from the source set in the software list.

[0054] In response to a software activation request from a user, the source identification unit 312 identifies a source (a source from which to obtain acquired information) to be referenced by the software requested to be activated (requesting software). Specifically, the source identification unit 312 identifies a source set in the requesting software to be referenced by the requesting software, based on the software list managed by the software list management unit 311. Information indicating the identified source is supplied to the information acquisition unit 313.

[0055] The information acquisition unit 313 acquires information (patient information and device information) from the source to be referenced by the requesting software based on information from the source identification unit 312. The patient information includes, for example, patient condition information relating to the patient's condition, and the device information includes, for example, device condition information relating to the condition of the source (electronic device). The information acquisition unit 313 includes an electronic medical record acquisition unit 313a, an endoscopic image acquisition unit 313b, and an operating room image acquisition unit 313c.

[0056] When the source represented by the information from the source identification unit 312 is the electronic medical record system 210, the electronic medical record acquisition unit 313a acquires, as acquired information, an electronic medical record including patient information from the electronic medical record system 210. When the source represented by the information from the source identification unit 312 is the endoscopic camera 220, the endoscopic image acquisition unit 313b acquires, as acquired information, endoscopic images and the endoscopic observation mode from the endoscopic camera 220. Endoscopic observation modes include a white light observation mode and an infrared light observation mode. When the source represented by the information from the source identification unit 312 is the operating room camera 230, the operating room image acquisition unit 313c acquires, as acquired information, operating room images from the operating room camera 230.

[0057] The information thus obtained is supplied to the analysis processing unit 314 .

[0058] The analysis processing unit 314 generates analysis information by analyzing the information acquired from the information acquisition unit 313. The analysis processing unit 314 includes a patient information analysis unit 314a and an image analysis unit 314b.

[0059] When the patient information analysis unit 314a receives an electronic medical record from the information acquisition unit 313, it analyzes the patient information included in the electronic medical record and outputs the analysis results as analysis information. In this case, the analysis information includes the patient's condition, such as the patient's medical history and allergy history. When the image analysis unit 314b receives an endoscopic image, an endoscopic observation mode, or an operating room image from the information acquisition unit 313, it analyzes this information and outputs the analysis results as analysis information. In this case, the analysis information includes the patient's surgical site, the surgeon's movements, the surgical equipment, and other surgical conditions, as well as the status of the source (electronic device).

[0060] The analytical information thus generated is supplied to the taboo determination unit 315 .

[0061] The taboo determination unit 315 determines whether or not the startup of the requested software is taboo according to the taboo information set for the requested software, based on the software list managed by the software list management unit 311. Specifically, the taboo determination unit 315 determines whether or not the startup of the requested software is taboo according to whether or not the analysis information from the analysis processing unit 314 (and therefore the acquired information acquired by the information acquisition unit 313) corresponds to the taboo information set for the requested software.

[0062] For example, the contraindication information includes the patient's condition for which the requested software should not be used, such as the patient's allergies or surgical conditions, etc. The contraindication information also includes the observation mode of the endoscope (infrared observation mode) as the condition of the source (electronic device) for which the requested software should not be used.

[0063] The result of the determination as to whether or not the activation of the requested software is taboo is supplied to the activation processing unit 316 .

[0064] The activation processing unit 316 controls the activation of the requested software based on the determination result from the contraindication determination unit 315. Specifically, the activation processing unit 316 activates the requested software when the determination result from the contraindication determination unit 315 indicates that it has not been determined that the activation of the requested software should be contraindicated. On the other hand, the activation processing unit 316 stops the activation of the requested software when the determination result from the contraindication determination unit 315 indicates that it has been determined that the activation of the requested software should be contraindicated.

[0065] (Flow of software startup determination process) Next, the flow of software activation determination processing by the medical information processing system 300 of Fig. 2 will be described with reference to the flowchart of Fig. 3. The processing of Fig. 3 is triggered by a software activation request from the user.

[0066] In step S11, the source identification unit 312 identifies the source referenced by the requesting software in response to the start-up request.

[0067] In step S12 , the information acquisition unit 313 acquires information from each source identified by the source identification unit 312 .

[0068] In step S13, the analysis processing unit 314 analyzes the acquired information acquired by the information acquisition unit 313 to generate analysis information.

[0069] In step S14, the contraindication determination unit 315 determines, based on the software list in the software list management unit 311, whether or not the analysis information generated by the analysis processing unit 314 corresponds to the contraindication information set in the requested software.

[0070] FIG. 4 is a diagram illustrating an example of a software list.

[0071] In the software list AL shown in FIG. 4, a source d1 and taboo information d2 are set for each registered software.

[0072] For example, in a medication administration management app (application), which is software for managing medications administered to patients, an "electronic medical record system" is set as the source d1. In addition, the same app also has a "history of allergies to specific medications" set as contraindication information d2.

[0073] In this case, it is determined whether or not the analysis result of the electronic medical record from the electronic medical record system 210 includes a "history of allergy to a specific drug."

[0074] In addition, the line keeping assistance app, which is software that assists in securing blood vessels for infusions and injections, has "electronic medical record system" and "operating room camera" set as source d1. The same app also has "history of shunt insertion in the right arm" and "procedure performed on the right arm" set as contraindication information d2.

[0075] In this case, it is determined whether or not the analysis result of the electronic medical record from the electronic medical record system 210 includes "a history of shunt addition to the right arm." It is also determined whether or not the analysis result of the operating room image from the operating room camera 230 includes "a record of treatment performed on the right arm."

[0076] Furthermore, the surgical procedure management app, which is software that guides surgeons through surgical procedures, has "electronic medical record system" and "operating room camera" set as sources d1. The same app also has "history of latex allergy" and "use of latex gloves by medical personnel" set as contraindication information d2.

[0077] In this case, it is determined whether or not the analysis result of the electronic medical record from the electronic medical record system 210 includes "history of allergy to latex." It is also determined whether or not the analysis result of the operating room image from the operating room camera 230 includes "worn latex gloves by the surgeon."

[0078] In addition, the partial lung resection assistance app, which is software that assists in partial lung resection, has "electronic medical record system," "audio at timeout," and "endoscopic camera" set as source d1. Timeout refers to confirming the surgical procedure, including the patient's name, surgical method, and surgical site (left or right), before the start of surgery. Therefore, in this case, "audio at timeout" as source d1 refers to a microphone or the like that can input the surgeon's voice before the start of surgery. In addition, the app has "surgical site" and "approach to the wrong site" set as contraindication information d2.

[0079] In this case, based on the analysis results of the electronic medical record from the electronic medical record system 210 and the "surgical site" contained in the analysis results of the audio from the microphone, it is determined whether the analysis results of the endoscopic image from the endoscopic camera 220 include an "approach to the wrong site (different from the surgical site)."

[0080] In this way, the contraindication determination unit 515 determines, based on the software list, whether or not the analysis information corresponds to the contraindication information set for the requested software.

[0081] Returning to the flowchart of FIG. 3, if it is determined in step S14 that the analysis information corresponds to the taboo information set in the requested software, the process proceeds to step S15, where the activation processing unit 316 stops the activation of the requested software.

[0082] On the other hand, if it is determined in step S14 that the analysis information does not correspond to the taboo information set in the requested software, the process proceeds to step S16, where the activation processing unit 316 activates the requested software.

[0083] According to the above process, the system checks whether activation of medical device software should be prohibited due to the risk of adverse effects caused by factors specific to the patient, thereby preventing inappropriate use of medical device software. As a result, it is possible to prevent invasive damage to the patient due to the activation of prohibited medical device software.

[0084] 4. Second embodiment In the operating room system 100 according to the embodiment described above, even if it is determined that the activation of a certain piece of software is contraindicated, there may be a case where the software must be activated at the discretion of a doctor.

[0085] Therefore, the following describes the configuration of the operating room system 100 that allows a doctor (user) to start software whose start-up has been determined to be taboo.

[0086] (Example of functional configuration of operating room system) FIG. 5 is a diagram illustrating an example of the functional configuration of the operating room system 100 according to the second embodiment of the present disclosure.

[0087] The operating room system 100 in FIG. 5 differs from the operating room system 100 in FIG. 2 in that a presentation control unit 317 is newly provided in the medical information processing system 300.

[0088] The presentation control unit 317 presents selection information that allows the user to select whether or not to start the requested software based on the determination result from the taboo determination unit 315. Specifically, the presentation control unit 317 presents the selection information when the determination result from the taboo determination unit 315 indicates that it has been determined that the start of the requested software should be taboo. The selection information is displayed, for example, on the centralized operation panel 111 or any of the display devices 103A to 103D.

[0089] When the selection information is presented, the activation processing unit 316 controls the activation of the requested software in accordance with the selection result for the selection information.

[0090] (Flow of software startup determination process) Next, the flow of the software activation determination process by the medical information processing system 300 of Fig. 5 will be described with reference to the flowchart of Fig. 6. The process of Fig. 6 is also started in response to a software activation request from the user.

[0091] The processing in steps S31 to S34 in the flowchart of FIG. 6 is the same as the processing in steps S11 to S14 in the flowchart of FIG. 3, and therefore a description thereof will be omitted.

[0092] That is, if it is determined in step S34 that the analysis information corresponds to the contraindication information set in the requested software, the process proceeds to step S35, where the presentation control unit 317 presents a warning screen including the selection information.

[0093] FIG. 7 is a diagram showing an example of a warning screen.

[0094] The warning screen 330 shown in FIG. 7 displays a warning message such as "Starting this software may be prohibited. Do you still want to start it?" as well as a NO button 331 and a YES button 332 as the selection information described above.

[0095] The NO button 331 is a button selected to stop the launch of requested software determined to be taboo, while the YES button 332 is a button selected to launch requested software determined to be taboo.

[0096] In step S36, the presentation control unit 317 determines whether or not activation of the requested software has been selected.

[0097] If it is determined in step S36 that the activation of the requested software has not been selected, that is, if the NO button 331 is selected on the warning screen 330, the process proceeds to step S37, where the activation processing unit 316 stops the activation of the requested software.

[0098] On the other hand, if it is determined in step S36 that activation of the requested software has been selected, that is, if the YES button 332 has been selected on the warning screen 330, the process proceeds to step S38, where the activation processing unit 316 activates the requested software.

[0099] Note that even if it is determined in step S34 that the analysis information corresponds to the taboo information set in the requested software, the process proceeds to step S38, and the activation processing unit 316 activates the requested software.

[0100] According to the above processing, even if the startup of the requested software is determined to be taboo, the user can decide at their own discretion whether to start the software or stop the startup of the software.

[0101] 5. Third Embodiment In the operating room system 100 of the above-described embodiment, if the medical information processing system 300 cannot connect to external devices such as the electronic medical record system 210, the endoscopic camera 220, or the operating room camera 230, there may be cases where the doctor has to decide to start the required software.

[0102] Therefore, the following describes the operation of the operating room system 100, which can start requested software at the discretion of a doctor (user) in an emergency such as when the medical information processing system 300 cannot connect to an external device.

[0103] (Flow of software startup determination process) The flow of software activation determination processing in emergency mode by the medical information processing system 300 of Fig. 5 will be described with reference to the flowchart of Fig. 8. The processing of Fig. 8 is started when the contraindication determination unit 315 acquires contraindication information set for the requested software based on the software list in the software list management unit 311, triggered by a software activation request from the user.

[0104] In step S51, the presentation control unit 317 displays the contraindication information of the requested software acquired by the contraindication determination unit 315.

[0105] In step S52, the presentation control unit 317 presents a confirmation screen including the selection information. The confirmation screen is a screen that displays a NO button and a YES button as the selection information described above, similar to the warning screen described with reference to FIG.

[0106] In step S53, the presentation control unit 317 determines whether or not activation of the requested software has been selected.

[0107] If it is determined in step S54 that activation of the requested software has not been selected, that is, if the NO button is selected on the confirmation screen, the process proceeds to step S55, where the activation processing unit 316 stops activation of the requested software.

[0108] On the other hand, if it is determined in step S53 that activation of the requested software has been selected, that is, if the YES button has been selected on the confirmation screen, the process proceeds to step S55, where the activation processing unit 316 activates the requested software.

[0109] According to the above processing, in an emergency such as when the medical information processing system 300 cannot connect to an external device, the user can check the patient's condition and situation and then decide whether to start the requested software or stop the software from starting.

[0110] 6. Fourth Embodiment In the operating room system 100 according to the embodiment described above, whether or not the start of requested software should be contraindicated is determined by referring to the contraindication information set in the software list. However, this is not limited to this, and contraindication candidate information that is a candidate for contraindication information may be generated based on software currently running for a specific patient.

[0111] In this case, activation permission information indicating whether or not software registered in the software list for the patient is executable is set based on the generated contraindication candidate information.

[0112] FIG. 9 is a diagram showing an example of a software list in which activation permission information is set.

[0113] In the software list AL' shown in Figure 9, in addition to the source d1 and taboo information d2 set for each registered software as in the software list AL of Figure 4, startup permission information d3 is also set for each registered software.

[0114] The activation permission information d3 is set to either "OK" which means that the activation of the software is not prohibited for the patient, or "NG" which means that the activation of the software is prohibited. In the example of Fig. 9, the activation permission information d3 is set to "NG" for the medicine administration management app, and the activation permission information d3 is set to "OK" for each of the line keeping assist app, surgical procedure management app, and lung partial resection assist app.

[0115] The activation permission information d3 in the software list AL' is updated based on the contraindication candidate information generated by the running software that is running for the target patient.

[0116] Therefore, the following describes the configuration of the operating room system 100 that updates the activation permission information in the software list based on the contraindication candidate information generated by the running software.

[0117] (Example of functional configuration of operating room system) FIG. 10 is a diagram illustrating an example of the functional configuration of an operating room system 100 according to the fourth embodiment of the present disclosure.

[0118] The operating room system 100 of Figure 10 differs from the operating room system 100 of Figure 2 in that in the medical information processing system 300, instead of the software list management unit 311, the contraindication determination unit 315, and the startup processing unit 316, a software list management unit 311', a contraindication determination unit 315', and a startup processing unit 316' are provided.

[0119] The software list management unit 311′ manages a software list for each patient, in which activation permission information is set for each registered software, as described with reference to Fig. 9. In the initial software list, it is assumed that "OK" is set as the activation permission information for each registered software.

[0120] Taboo determination section 315' has the same function as taboo determination section 315 in FIG. 2, and determines whether or not requested software should be taboo according to activation permission information set in the requested software.

[0121] When contraindication candidate information is generated by running software running on a target patient, the startup processing unit 316′ supplies the generated contraindication candidate information to the software list management unit 311′. The software list management unit 311′ updates the startup permission information in the software list based on the contraindication candidate information supplied from the startup processing unit 316′.

[0122] (List update process flow) Next, the flow of the list update process by the medical information processing system 300 of Fig. 10 will be described with reference to the flowchart of Fig. 11. The process of Fig. 11 starts in a state where the software is running for a predetermined patient.

[0123] In step S71, the activation processing unit 316' determines whether or not contraindication candidate information has been generated by the running software running on the target patient. Step S71 is repeated until it is determined that contraindication candidate information has been generated. If it is determined that contraindication candidate information has been generated, the process proceeds to step S72.

[0124] In step S72, the software list management unit 311' determines whether or not there is software in the software list of the target patient for which the contraindication candidate information generated by the running software is set as contraindication information. If it is determined that there is software for which the generated contraindication candidate information is set as contraindication information, the process proceeds to step S73.

[0125] In step S73, the software list management unit 311' updates the activation permission information of the corresponding software (software for which contraindication candidate information is set as contraindication information) in the software list of the target patient from OK to NG.

[0126] If it is determined in step S72 that the generated contraindication candidate information does not include software that is set as contraindication information, step S73 is skipped.

[0127] In this manner, the activation permission information in the software list is updated based on the contraindicated candidate information generated by the running software.

[0128] (Flow of software startup determination process) Next, the flow of the software activation determination process by the medical information processing system 300 of Fig. 10 will be described with reference to the flowchart of Fig. 12. The process of Fig. 12 is also started in response to a software activation request from the user.

[0129] In step S91, the contraindication determination unit 315' determines whether or not the activation permission information of the requested software is set to "NG" in the software list of the target patient managed by the software list management unit 311'.

[0130] If it is determined in step S91 that the activation permission information of the requested software is set to NG, the process proceeds to step S92, where the activation processing unit 316' stops the activation of the requested software.

[0131] On the other hand, if it is determined in step S91 that the activation permission information of the requested software is not set to NG, the process proceeds to step S93, where the activation processing unit 316' activates the requested software.

[0132] The above process also allows the system to check whether activation of medical device software should be prohibited due to concerns that activation may have adverse effects due to factors specific to the patient, making it possible to prevent inappropriate use of medical device software. As a result, it becomes possible to prevent invasive damage to patients caused by the activation of prohibited medical device software.

[0133] In the above-described processing, if the startup information for the requested software is set to NG, a warning screen may be displayed as in the processing of Figure 6, so that the user can decide whether or not to start the software.

[0134] In addition, for software in the software list that has once had its startup information set to NG, there may be software for which the startup information is permanently set to NG for the patient, and software for which the startup information is temporarily set to NG.

[0135] For example, for software related to conditions or situations that continue to occur once they have been treated, such as shunt formation or allergies, the activation permission information for that patient will remain set to "NG" permanently. Also, for software related to temporary conditions or situations, such as medicine that is expected to be effective for a specific period of time, the activation permission information for that patient will be set to "NG" temporarily.

[0136] In this case, the medical information processing system 300 periodically refers to the source and determines whether the activation permission information of the corresponding software is OK or NG.

[0137] 7. Fifth Embodiment In the operating room system 100 of the embodiment described above, after it is determined that the startup of a certain piece of software is not contraindicated, there may be a case where the software is updated or the patient's condition is updated while the software is running.

[0138] Therefore, the following describes the configuration of the operating room system 100 that determines whether or not to activate software when contraindication information or patient information for the software currently being executed is updated.

[0139] (Example of functional configuration of operating room system) FIG. 13 is a diagram illustrating an example of the functional configuration of an operating room system 100 according to the fifth embodiment of the present disclosure.

[0140] The operating room system 100 in FIG. 13 differs from the operating room system 100 in FIG. 2 in that a contraindication determining unit 315'' is provided in place of the contraindication determining unit 315 in the medical information processing system 300.

[0141] The taboo determination unit 315'' has the same functions as the taboo determination unit 315 in FIG.

[0142] The update detection unit 411 detects updates to contraindication information of registered software in the software list managed by the software list management unit 311 and updates to patient information acquired by the information acquisition unit 313 .

[0143] For example, the update detection unit 411 detects an update to the contraindication information of registered software in response to a medical device software update notification from an external device to the software list management unit 311. The update detection unit 411 also detects an update to patient information based on the patient's condition output by the analysis processing unit 314 as analysis information obtained by analyzing a patient image obtained by capturing the patient.

[0144] Then, the contraindication determining unit 315'' determines whether or not the activation of the requested software that is currently running should be contraindicated based on the contraindication information and the updated content of the patient information.

[0145] (Flow of software startup determination process) The flow of the software activation determination process in the medical information processing system 300 of Fig. 13 will be described with reference to the flowchart of Fig. 14. The process of Fig. 14 is executed, for example, after the currently running software is activated.

[0146] In step S111, the update detection unit 411 determines whether or not an update of the taboo information of the running software has been detected.

[0147] If it is determined in step S111 that an update of the contraindication information of the running software has been detected, the process proceeds to step S112.

[0148] In step S112, the contraindication determination unit 315'' determines whether or not the patient information or device information acquired by the information acquisition unit 313 corresponds to the updated contraindication information.

[0149] If it is determined in step S112 that the acquired information corresponds to the updated taboo information, the process proceeds to step S113, where the activation processing unit 316' stops the activation of the currently running software.

[0150] On the other hand, if it is determined in step S112 that the acquired information does not match the updated taboo information, the process returns to step S111, and the subsequent processes are repeated while the running software continues to run.

[0151] Now, if it is determined in step S111 that an update of the contraindication information of the running software has not been detected, the process proceeds to step S114, where the update detection unit 411 determines whether an update of the patient information has been detected.

[0152] If it is determined in step S114 that an update of the patient information has been detected, the process proceeds to step S115.

[0153] In step S115, the contraindication determining section 315'' determines whether or not the updated patient information corresponds to contraindication information.

[0154] If it is determined in step S115 that the updated patient information corresponds to contraindication information, the process proceeds to step S113, where the activation processing unit 316' stops the activation of the currently running software.

[0155] On the other hand, if it is determined in step S115 that the updated patient information does not correspond to the contraindication information, the process returns to step S111, and the subsequent processes are repeated while the running software continues to run.

[0156] Also, if it is determined in step S114 that no update to the patient information has been detected, i.e., no update to either the contraindication information of the running software or the patient information has been detected, the process returns to step S111, and the subsequent processing is repeated while the running software continues to run.

[0157] According to the above process, the system checks whether the running medical device software should be stopped due to the risk of adverse effects caused by updating contraindication information or patient information, thereby preventing inappropriate use of the medical device software. As a result, it is possible to prevent invasive damage to patients caused by the running of contraindicated medical device software.

[0158] 8. Sixth Embodiment In the operating room system 100 of the above-described embodiment, for software registered in the software list, either first contraindication information indicating that the software should not be used, or second contraindication information indicating that the software can be used under certain conditions may be set as contraindication information.

[0159] For example, the second contraindication information includes, as conditions, the state of the patient or the state of the equipment under which the software should not be used.

[0160] In this case, when second contraindication information is set for the software currently running, whether to continue or stop the software from running is determined based on changes in the patient information and device information acquired as acquired information.

[0161] (Flow of software startup determination process) With reference to the flowchart in Fig. 15, the flow of software start determination processing when second contraindication information is set in running software in, for example, the medical information processing system 300 in Fig. 13 will be described. The processing in Fig. 15 is executed, for example, at regular time intervals (periodically) after the running software is started.

[0162] In step S131, the analysis processing unit 314 analyzes the acquired patient information or device information to determine whether there has been a certain level of change in the patient information or device information. The change in the patient information or device information here refers to a change in the patient condition or device condition that does not satisfy the conditions included in the second contraindication information.

[0163] If it is determined in step S131 that there is no change in the patient information or device information of a certain level or more, the process proceeds to step S132, where the activation processing unit 316 continues to activate the currently running software.

[0164] On the other hand, if it is determined in step S131 that there has been a certain amount of change in the patient information or device information, the process proceeds to step S133.

[0165] In step S133, the contraindication determination unit 315'' determines whether or not the patient information or device information analyzed by the analysis processing unit 314 corresponds to the second contraindication information of the running software.

[0166] If it is determined in step S133 that the patient information or the device information does not correspond to the second contraindication information of the running software, the process proceeds to step S132, where the startup processing unit 316 continues to start the running software.

[0167] On the other hand, if it is determined in step S133 that the patient information or the device information corresponds to the second contraindication information of the running software, the process proceeds to step S134, where the startup processing unit 316 stops the startup of the running software.

[0168] According to the above process, the system checks whether the running medical device software should be stopped due to the risk of adverse effects caused by changes in the patient's condition or the device's condition, thereby preventing inappropriate use of the medical device software. As a result, it is possible to prevent invasive damage to the patient due to the running of prohibited medical device software.

[0169] <9. Computer configuration example> The above-described series of processes can be executed by hardware or software. When the series of processes is executed by software, the program constituting the software is installed from a program recording medium into a computer incorporated in dedicated hardware or a general-purpose personal computer.

[0170] FIG. 16 is a block diagram showing an example of the hardware configuration of a computer that executes the above-described series of processes using a program.

[0171] A medical information processing system 300 to which the technology according to the present disclosure can be applied can be realized by a computer having the configuration shown in FIG.

[0172] A CPU 501 , a ROM (Read Only Memory) 502 , and a RAM (Random Access Memory) 503 are interconnected by a bus 504 .

[0173] An input / output interface 505 is also connected to the bus 504. An input unit 506 including a keyboard, a mouse, etc., and an output unit 507 including a display, a speaker, etc. are connected to the input / output interface 505. In addition, a storage unit 508 including a hard disk, a nonvolatile memory, etc., a communication unit 509 including a network interface, etc., and a drive 510 that drives removable media 511 are also connected to the input / output interface 505.

[0174] In the computer configured as above, the CPU 501 loads a program stored in the storage unit 508 into the RAM 503 via the input / output interface 505 and the bus 504 and executes the program, thereby performing the above-described series of processes.

[0175] The program executed by the CPU 501 is installed in the storage unit 508 by being recorded on a removable medium 511, or provided via a wired or wireless transmission medium such as a local area network, the Internet, or digital broadcasting.

[0176] The program executed by the computer may be a program that processes in chronological order according to the order described in this specification, or may be a program that processes in parallel or at the required timing, such as when called.

[0177] The embodiments of the present disclosure are not limited to the above-described embodiments, and various modifications are possible within the scope of the gist of the present disclosure.

[0178] Furthermore, the effects described in this specification are merely examples and are not limiting, and other effects may also be present.

[0179] Furthermore, the present disclosure can be configured as follows. (1) a list management unit that manages a software list in which taboo information is set for each registered software; an information acquisition unit that acquires patient information about a patient who uses the requested software whose activation has been requested, and device information about an electronic device used by the patient; a contraindication determination unit that determines whether or not activation of the requested software should be contraindicated depending on whether or not the patient information or the device information corresponds to the contraindication information set for the requested software in the software list; A medical information processing system comprising: (2) a detection unit that detects an update of the contraindication information or the patient information of the registered software; The contraindication determination unit determines whether or not activation of the requested software should be contraindicated based on the contraindication information or the updated content of the patient information. (1) A medical information processing system according to the present invention. (3) When an update of the contraindication information is detected, the contraindication determination unit determines whether the patient information or the device information corresponds to the updated contraindication information. (2) A medical information processing system according to the present invention. (4) When an update of the patient information is detected, the contraindication determination unit determines whether the updated patient information corresponds to the contraindication information. (2) A medical information processing system according to the present invention. (5) the contraindication information includes a condition of the patient that prevents the use of the registration software; The information acquisition unit acquires patient condition information relating to the condition of the patient as the patient information. A medical information processing system according to any one of (2) to (4). (6) The patient's condition includes an allergy or a surgical condition. (5) A medical information processing system according to (5). (7) An analysis processing unit is further provided that outputs a state of the patient as analysis information obtained by analyzing a patient image obtained by capturing the patient, The detection unit detects an update of the patient information based on the analysis information. (6) A medical information processing system according to (6). (8) the contraindication information includes a state of the electronic device in which the registered software should not be used; The information acquisition unit acquires, as the device information, device status information relating to a status of the electronic device. A medical information processing system according to any one of (2) to (4). (9) The state of the electronic device includes an observation mode of the endoscope. (8) A medical information processing system according to (8). (10) the taboo information includes first taboo information indicating that the registered software must not be used and second taboo information indicating that the registered software can be used under certain conditions; The contraindication determination unit determines whether the patient information or the device information corresponds to the second contraindication information. A medical information processing system according to any one of (1) to (9). (11) The contraindication determination unit determines whether the patient information or the device information corresponds to the second contraindication information when a certain or greater change occurs in the patient information or the device information. (10) A medical information processing system according to (10). (12) a startup processing unit that executes processing related to the startup of the requested software; The startup processing unit stops startup of the requested software when it is determined that startup of the requested software should be prohibited. A medical information processing system according to any one of (1) to (11). (13) a presentation control unit that presents selection information for allowing the user to select whether or not to start the requested software when it is determined that the start of the requested software should be prohibited; The startup processing unit starts the requested software when the selection information indicates that the requested software needs to be started. (12) A medical information processing system according to (12). (14) Medical information processing system Manage a software list with contraindication information for each registered software. Acquire patient information regarding a patient for whom the requested software to be activated is used and device information regarding an electronic device used by the patient; Whether or not the activation of the requested software should be contraindicated is determined depending on whether or not the patient information or the device information corresponds to the contraindication information set for the requested software in the software list. Judgment method. (15) On the computer, Manage a software list with contraindication information for each registered software. Acquire patient information regarding a patient for whom the requested software to be activated is used and device information regarding an electronic device used by the patient; Whether or not the activation of the requested software should be contraindicated is determined depending on whether or not the patient information or the device information corresponds to the contraindication information set for the requested software in the software list. A program for executing a process. [Explanation of symbols]

[0180] 100 Operating room system, 300 Medical information processing system, 311, 311' Software list management unit, 312 Source determination unit, 313 Information acquisition unit, 314 Analysis processing unit, 315, 315', 315'' Contraindication determination unit, 316, 316' Startup processing unit, 317 Presentation control unit, 411 Update detection unit

Claims

1. a list management unit that manages a software list in which taboo information is set for each registered software; an information acquisition unit that acquires patient information about a patient who uses the requested software whose activation has been requested, and device information about an electronic device used by the patient; a contraindication determination unit that determines whether or not activation of the requested software should be contraindicated depending on whether or not the patient information or the device information corresponds to the contraindication information set for the requested software in the software list; A medical information processing system comprising:

2. a detection unit that detects an update of the contraindication information or the patient information of the registered software; The contraindication determination unit determines whether or not activation of the requested software should be contraindicated based on the contraindication information or the updated content of the patient information. The medical information processing system according to claim 1 .

3. When an update of the contraindication information is detected, the contraindication determination unit determines whether the patient information or the device information corresponds to the updated contraindication information. The medical information processing system according to claim 2 .

4. When an update of the patient information is detected, the contraindication determination unit determines whether the updated patient information corresponds to the contraindication information. The medical information processing system according to claim 2 .

5. the contraindication information includes a condition of the patient that prevents the use of the registration software; The information acquisition unit acquires patient condition information relating to the condition of the patient as the patient information. The medical information processing system according to claim 2 .

6. The patient's condition includes an allergy or a surgical condition. The medical information processing system according to claim 5 .

7. An analysis processing unit is further provided that outputs a state of the patient as analysis information obtained by analyzing a patient image obtained by capturing the patient, The detection unit detects an update of the patient information based on the analysis information. The medical information processing system according to claim 6.

8. the contraindication information includes a state of the electronic device in which the registered software should not be used; The information acquisition unit acquires, as the device information, device status information relating to a status of the electronic device. The medical information processing system according to claim 2 .

9. The state of the electronic device includes an observation mode of the endoscope. The medical information processing system according to claim 8.

10. the taboo information includes first taboo information indicating that the registered software must not be used, and second taboo information indicating that the registered software can be used under certain conditions; The contraindication determination unit determines whether the patient information or the device information corresponds to the second contraindication information. The medical information processing system according to claim 1 .

11. The contraindication determination unit determines whether the patient information or the device information corresponds to the second contraindication information when a certain or greater change occurs in the patient information or the device information. The medical information processing system according to claim 10.

12. a startup processing unit that executes processing related to the startup of the requested software; The startup processing unit stops startup of the requested software when it is determined that startup of the requested software should be prohibited. The medical information processing system according to claim 1 .

13. a presentation control unit that presents selection information for allowing the user to select whether or not to start the requested software when it is determined that the start of the requested software should be prohibited; The startup processing unit starts the requested software when the selection information indicates that the requested software needs to be started. The medical information processing system according to claim 12.

14. Medical information processing system Manage a software list with contraindication information for each registered software. Acquire patient information regarding a patient for whom the requested software to be activated is used and device information regarding an electronic device used by the patient; Whether or not the activation of the requested software should be contraindicated is determined depending on whether or not the patient information or the device information corresponds to the contraindication information set for the requested software in the software list. Judgment method.

15. On the computer, Manage a software list with contraindication information for each registered software. Acquire patient information regarding a patient for whom the requested software to be activated is used and device information regarding an electronic device used by the patient; Whether or not the activation of the requested software should be contraindicated is determined depending on whether or not the patient information or the device information corresponds to the contraindication information set for the requested software in the software list. A program for executing a process.

Images