Medical information processing device and medical information processing system

Abstract

To prevent erroneous operation of a medical device that should not be operated by an operator in a medical information processing system in which at least one or more medical devices and an operation device are connected to a common network.SOLUTION: A medical information processing device 30 according to an embodiment includes: an operator information acquisition unit 33a which acquires operator information for identifying an operator of an operation device 20; a device information acquisition unit 33b which acquires device information representing a medical device that can be operated by the operator on the basis of the acquired operator information; and a provision unit 33c which provides the acquired device information to the operation device 20.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The embodiments disclosed in this specification and the drawings relate to a medical information processing device and a medical information processing system. [Background technology]

[0002] When multiple medical devices and multiple operation devices are connected via a shared network, multiple medical devices can be used from one operation device, or one medical device can be used from multiple operation devices. However, there is a possibility that a medical device that should not be operated by an operator of the operation device may be operated by mistake. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2006-122197 A Summary of the Invention [Problem to be solved by the invention]

[0004] One of the problems to be solved by the embodiments disclosed in this specification and the drawings is to prevent a medical device that should not be operated by an operator of an operation device from being mistakenly operated in a medical information processing system in which at least one medical device and an operation device are communicably connected via a shared network. However, the problems to be solved by the embodiments disclosed in this specification and the drawings 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]

[0005] The medical information processing device according to the embodiment includes an acquisition unit that acquires operator information that identifies an operator of an operating device, a device information acquisition unit that acquires device information representing medical devices that can be operated by the operator based on the acquired operator information, and a provision unit that provides the acquired device information to the operating device. [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is a block diagram showing the configuration of a medical information processing system according to the first embodiment. [Diagram 2] FIG. 2 is a block diagram showing the configuration of the medical image processing apparatus according to the first embodiment. [Diagram 3] FIG. 3 is a diagram showing an example of a list of medical information according to the first embodiment. [Figure 4] FIG. 4 is a block diagram showing the configuration of the operation device according to the first embodiment. [Diagram 5] FIG. 5 is a schematic diagram showing communication processing performed in the medical information processing system according to the first embodiment. [Figure 6] FIG. 6 is a sequence diagram showing communication processing performed in the medical information processing system according to the first embodiment. [Figure 7] FIG. 7 is a diagram showing an example of a display screen of authentication information according to the first embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a display screen of device information according to the first embodiment. [Figure 9] FIG. 9 is a diagram showing an example of a display screen of device information according to a modification of the first embodiment. [Figure 10] FIG. 10 is a block diagram showing the configuration of a medical image processing apparatus according to the second embodiment. [Figure 11] FIG. 11 is a schematic diagram showing communication processing performed in the medical information processing system according to the second embodiment. [Figure 12] FIG. 12 is a sequence diagram showing communication processing performed in the medical information processing system according to the second embodiment. [Figure 13]FIG. 13 is a diagram showing an example of a display screen of device information according to a modification of the second embodiment. [Figure 14] FIG. 14 is a schematic diagram showing communication processing performed in the medical information processing system according to the third embodiment. [Figure 15] FIG. 15 is a diagram showing an example of a display screen of authentication information according to the third embodiment. [Figure 16] FIG. 16 is a schematic diagram showing communication processing performed in the medical information processing system according to the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Hereinafter, an embodiment of a medical information processing system will be described in detail with reference to the drawings. In the following description, components having substantially the same functions and configurations are denoted by the same reference numerals, and repeated description will be given only when necessary.

[0008] (First embodiment) FIG. 1 is a diagram showing the configuration of a medical information processing system 1. The medical information processing system 1 is a system in which components are arranged on a shared network. The medical information processing system 1 includes a medical device 10 (medical device 10a-10n), an operation device 20 (operation device 20a-20n), and a medical information processing device 30, which are communicatively connected to each other via the shared network. The shared network is, for example, Ethernet (registered trademark) such as a LAN (Local Area Network). Note that the connection to the shared network may be either wired or wireless. Also, as long as security is ensured by a VPN (Virtual Private Network) or the like, the connection line is not limited to a LAN, and may be connected to a public communication line such as the Internet. One or more medical devices 10 and one or more operation devices 20 are provided.

[0009] The medical information processing system 1 has high system scalability by connecting each component (medical device 10, operation device 20, medical information processing device 30) to a shared network. For example, the system can be constructed with the same design even if the scale is different, such as by hospital department, hospital, or region, and a medical system architecture that consistently supports all medical scenes from in-hospital medical care to community medical care and home medical care can be realized. In addition, the medical information processing system 1 can share the computing resources arranged on the shared network, and can achieve cost and space saving by optimization through flexible allocation according to the operation situation. In addition, the medical information processing system 1 has a flexible physical configuration (flexible deployment) in which the components can be arranged anywhere on the shared network.

[0010] In this way, when multiple medical devices 10 and multiple operation devices 20 are connected via a shared network, multiple medical devices 10 can be used from one operation device 20, or one medical device 10 can be used from multiple operation devices 20. On the other hand, there is a possibility that a medical device 10 that should not be operated by an operator of the operation device 20 may be operated by mistake.

[0011] The medical information processing system 1 provides medical information including a medical device 10 that can be operated by an operator of the operation device 20 from a medical information processing device 30 to the operation device 20. The medical information processing system 1 prevents the operator of the operation device 20 from erroneously operating the medical device 10 that should not be operated.

[0012] The medical device 10 communicates with an operation device 20 or a medical information processing device 30. The medical device 10 is operated by the operation device 20 via a shared network. The medical device 10 is, for example, a medical image diagnostic device, a radiation therapy device, a surgical instrument, etc. The medical image diagnostic device is, for example, an X-ray computed tomography (CT) device, a magnetic resonance imaging (MRI) device, an ultrasonic diagnostic device, an X-ray diagnostic device, a PET (Positron Emission Tomography) device, etc. The multiple medical devices 10a-10n may be located in the same room or different rooms in the same medical facility, or may be located in different medical facilities.

[0013] The medical information processing device 30 communicates with the medical device 10 or the operation device 20 via a shared network. The medical information processing device 30 is composed of, for example, a server. The medical information processing device 30 communicates with the operation device 20 and provides the operation device 20 with a list of medical information including the medical device 10 that can be operated by the operator of the operation device 20.

[0014] As shown in FIG. 2, the medical information processing device 30 includes a memory 31, a communication interface 32, and a processing circuit 33.

[0015] The communication interface 32 is realized by a communication device such as a network card, a network adapter, a NIC (Network Interface Controller), etc. The communication interface 32 communicates with the medical device 10 and the operation device 20 via a network.

[0016] The memory 31 is realized by, for example, a semiconductor memory element such as a RAM (Random Access Memory), a flash memory, a hard disk, an optical disk, etc. The memory 31 stores various data and programs necessary for the processing performed by the processing circuit 33, and various data obtained by the processing performed by the processing circuit 33. The memory 31 is an example of a storage unit.

[0017] The memory 31 also stores a list of medical information in which an operator is associated with a medical device that can be operated by the operator. The list of medical information is managed, for example, for each medical order. Medical orders include, for example, examination orders, treatment orders, image reading orders, and consultation orders. The list of medical information is periodically acquired, for example, from a hospital information system or an electronic medical record system via a network. The list of medical information indicates the medical devices 10 that the operator can operate. A medical device that the operator can operate refers to a medical device for which the operator has been granted operating authority.

[0018] The medical information may be generated by the medical information processing device 30. For example, the medical information processing device 30 may assign an operator to a medical device included in a medical order based on the schedule of the operator managed by the schedule management device and the medical order issued by the medical order device, and generate medical information. In addition, when the schedule management device manages the skills of the operator in addition to the schedule of the operator, the medical information processing device 30 may assign an appropriate operator to the medical device 10 included in the medical order according to the schedule and skill of the operator, and generate medical information. The list of medical information generated by the medical information processing device 30 is stored in the memory 31.

[0019] As shown in Fig. 3, the medical information stored in the memory 31 includes a medical order ID, medical device information, operator information, scheduled date and time, patient information, order information, etc. The medical order ID is information that uniquely identifies a medical order. The medical device information is information that identifies the medical device 10, and includes a device ID that uniquely identifies the medical device 10, the type of the medical device 10, the name of the medical device 10, etc. The medical device information includes information about one or more medical devices 10 depending on the contents of the medical order. The medical device information also includes connection information (link information) for connecting to the medical device 10, such as a Uniform Resource Locator (URL) or Internet Protocol (IP) address of the medical device 10.

[0020] The operator information includes a user ID and password for uniquely identifying the operator, the name of the operator, and the like. The operator information includes information on one or more operators depending on the contents of the medical order. That is, the operation authority of one medical device 10 may be given to one operator or to multiple operators. Also, the operation authority of multiple medical devices 10 may be given to one operator or to multiple operators. Specifically, when one examination is performed using multiple medical devices 10, such as an angio-CT examination, the medical device information includes multiple medical devices 10 and the operator information includes multiple operators for one medical order ID.

[0021] The scheduled date and time is information that identifies the scheduled date and time for executing the order. The patient information is information that identifies the patient who is to receive the medical procedure, and includes, for example, a patient ID that uniquely identifies the patient, the patient's name, sex, date of birth, and blood type. The patient information may also include information that identifies physical characteristics such as height and weight, and medical history. The order information includes, for example, the contents of the order such as examination, treatment, image interpretation, and consultation, the date and time the order was issued, etc.

[0022] The processing circuitry 33 is realized by a processor such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit). The processing circuitry 33 controls each part of the medical information processing device 30 to thereby control the entire medical information processing device 30. The processing circuitry 33 reads out and executes a program stored in the memory 31, thereby functioning as an operator information acquisition unit 33a, a device information acquisition unit 33b, and a provision unit 33c.

[0023] The operation device 20 communicates with the medical device 10 or the medical information processing device 30. The operation device 20 is, for example, a terminal such as a PC (Personal Computer). The operator of the operation device 20 is, for example, a medical professional such as a doctor in charge, a radiologist, a radiologist, a clinical laboratory technician, or a nurse. The operation devices 20a-20n may be arranged in the same room or different rooms in the same medical facility, or may be arranged in different medical facilities. The operation device 20 may be arranged in the same room (examination room) as the room in which the medical device 10 is installed, or in a different room. The different room may be, for example, a room adjacent to the examination room in which the medical device 10 is installed and in which the operator can directly view the medical device 10, or a room far away from the place where the medical device 10 is installed and which monitors the place where the medical device 10 is installed via a shared network.

[0024] As shown in FIG. 4, the operation device 20 includes a memory 21, a communication interface 22, a display 23, an input interface 24, and a processing circuit 25.

[0025] The memory 21 is realized by, for example, a semiconductor memory element such as a RAM or a flash memory, a hard disk, an optical disk, etc. The memory 21 stores various data and programs necessary for the processing performed by the processing circuitry 25, and various data obtained by the processing performed by the processing circuitry 25. The memory 21 stores various information used to operate the medical device 10, a list of medical information obtained from the medical information processing device 30, etc. The memory 21 is an example of a storage unit.

[0026] The communication interface 22 is realized by a communication device such as a network card, a network adapter, a NIC, etc. The communication interface 22 communicates with the medical device 10 and the medical information processing device 30 via a network.

[0027] The display 23 is realized by a display device such as a liquid crystal display or a CRT (Cathode Ray Tube) display. The display 23 displays medical information generated by the processing circuit 25, a GUI (Graphical User Interface) for receiving various operations from the operator, and the like. The display 23 also displays a list of medical devices 10 that the operator can operate. The display 23 is an example of a display unit.

[0028] The input interface 24 receives various input operations from an operator, converts the received input operations into electrical signals, and outputs the electrical signals to the processing circuit 25. For example, the input interface 24 receives input of medical information, input of various command signals, and the like from the operator. The input interface 24 is realized by a mouse, a keyboard, a trackball, a switch button, a touch screen in which a display screen and a touch pad are integrated, a non-contact input circuit using an optical sensor, and a voice input circuit, etc., for performing various processes of the processing circuit 25. The input interface 24 is connected to the processing circuit 25, and converts the input operations received from the operator into electrical signals and outputs them to the control circuit. Note that the input interface is not limited to those having physical operating parts such as a mouse and a keyboard. For example, an electrical signal processing circuit that receives an electrical signal corresponding to an input operation from an external input device provided separately from the device and outputs the electrical signal to the processing circuit 25 is also included as an example of the input interface. The input interface 24 is an example of an input unit.

[0029] The processing circuitry 25 is realized by a processor such as a CPU or a GPU. The processing circuitry 25 controls the operation of the entire operation device 20. The processing circuitry 25 also displays various information on the display 23. For example, the processing circuitry 25 displays a login screen for authenticating an operator, a list of medical orders, and various operation screens for operating the medical device 10 on the display 23. The processing circuitry 25 also reads out and executes a program stored in the memory 21, thereby functioning as an input receiving unit 25a, an operator information providing unit 25b, a device information notifying unit 25c, and a connecting unit 25d.

[0030] The operation of the medical information processing system 1 configured as above will be described below with reference to Fig. 5 to Fig. 8. Fig. 5 is a diagram showing communication processing performed between components of the medical information processing system 1. Fig. 6 is a sequence diagram for explaining the operation of the medical information processing system 1. Fig. 7 is a diagram showing an example of a display screen for authentication information. Fig. 8 is a diagram showing an example of a display screen for device information.

[0031] 7 on the display 23, and receives input of operator information (operator ID, password, operator name, etc.) for identifying the operator (step S101). The operator information providing unit 25b provides the operator information received by the input receiving unit 25a to the medical information processing device 30 via the shared network (step S102).

[0032] The operator information acquiring unit 33a of the medical information processing device 30 acquires the operator information provided from the operation device 20 (step S103). The device information acquiring unit 33b acquires device information representing the medical device 10 that can be operated by the operator of the operation device 20, based on the operator information acquired by the operator information acquiring unit 33a. Specifically, upon acquiring the operator information, the device information acquiring unit 33b acquires a list of medical information stored in the memory 31 as device information (step S104).

[0033] The providing unit 33c provides the device information acquired by the device information acquiring unit 33b in a manner that allows the medical device 10 that can be operated by the operator of the operation device 20 to be distinguished from other medical devices 10. For example, the providing unit 33c extracts medical information including the operator information acquired in step S103 from the device information (list of medical information). The providing unit 33c changes the extracted medical information to a manner that allows the operator to distinguish that the medical information can be operated.

[0034] Furthermore, the providing unit 33c provides the device information (list of medical information) acquired by the device information acquiring unit 33b in a manner that allows connection to the medical device 10 that can be operated by the operator of the operation device 20. For example, when connection information (link information) for connecting to the medical device 10, such as the URL of the medical device 10, is included (attached) for each piece of medical information in the list acquired by the device information acquiring unit 33b, the providing unit 33c deletes the connection information included in the medical information other than the medical information extracted from the list of medical information.

[0035] On the other hand, for example, when the connection information (link information) for connecting to the medical device 10 is not included for each medical information in the list acquired by the device information acquisition unit 33b, the provision unit 33c adds the connection information only to the medical information extracted from the list of medical information. As a result, the connection information is added only to the medical device 10 that can be operated by the operator of the operation device 20. The provision unit 33c provides the device information (list of medical information) that has been subjected to the above various processes to the operation device 20, which is the sender of the operator information, via the shared network (step S105).

[0036] The device information notifying unit 25c of the operation device 20 notifies the device information (list of medical information) provided from the medical information processing device 30. Specifically, the device information notifying unit 25c displays the device information provided from the medical information processing device 30 on the display 23 (step S106). For example, the device information shown in FIG. 8 is displayed on the display 23. The device information is displayed in a manner that allows the operator of the operation device 20 to distinguish between the medical devices 10 that can be operated by the operator of the operation device 20 and the medical devices 10 that cannot be operated by the operator of the operation device 20. More specifically, medical information including the medical devices 10 that can be operated by the operator of the operation device 20 is highlighted by a manner such as highlighting or bolding. This allows the operator of the operation device 20 to understand the medical order to be executed by the operator of the operation device 20 and to distinguish the medical devices 10 that can be operated by the operator of the operation device 20 from other medical devices 10.

[0037] The connection unit 25d accepts an operation to select the medical device 10 (step S107). For example, the operator selects a medical order (e.g., medical order ID 1) to be executed by the operator from the device information (list of medical information) displayed on the display 23 by operating via the input interface 24. As a result, the connection unit 25d recognizes that the medical device 10 (medical device 10 represented by the medical device information 10a) corresponding to the medical order selected by the operator is to be operated by the operator.

[0038] The connection unit 25d performs a process of connecting to the selected medical device 10 (step S108). Specifically, the connection unit 25d connects to the medical device 10 selected by the operator based on the connection information (link information) included in the medical information corresponding to the selected medical order (step S108).

[0039] When the operation device 20 is connected to the medical device 10, an operation screen for operating the selected medical device 10 is displayed on the display 23 of the operation device 20. The operation device 20 performs a medical procedure corresponding to the medical order in response to an operation by an operator via the input interface 24.

[0040] As described above, according to this embodiment, device information (list of medical information) including medical devices that can be operated by the operator of the operation device 20 can be provided from the medical information processing device 30 to the operation device 20. The operator of the operation device 20 can confirm the medical devices 10 that he / she can operate by checking the device information provided from the medical information processing device 30, and therefore it is possible to prevent the operator of the operation device 20 from erroneously operating a medical device 10 that should not be operated.

[0041] Furthermore, the medical information processing device 30 provides the device information to the operation device 20 in a manner that allows the operator of the operation device 20 to identify the medical device 10 that can be operated by the operator of the operation device 20. This makes it possible to prevent the operator of the operation device 20 from erroneously operating a medical device 10 that should not be operated.

[0042] Furthermore, the medical information processing device 30 provides device information to the operation device 20 for medical devices 10 that can be operated by the operator of the operation device 20 in a manner that allows the operation device 20 to connect to the medical device 10. This allows the operator of the operation device 20 to easily access the medical device 10 that he or she is operating, and prevents the operator of the operation device 20 from erroneously operating a medical device 10 that should not be operated.

[0043] (Modification of the first embodiment) In the above embodiment, the medical device 10 operable by the operator of the operation device 20 is provided in a manner that allows connection from the operation device 20 to the medical device 10, but the medical device 10 does not have to be provided in such a connectable manner. For example, the operation device 20 may search for a medical device 10 operable by the operator from among a plurality of medical devices 10a to 10n connected to a shared network, and connect to the corresponding medical device 10.

[0044] In the above embodiment, the medical device 10 operable by the operator of the operation device 20 is provided in a manner that makes it possible to distinguish it from other medical devices 10. However, the medical device 10 does not have to be provided in such a manner that makes it possible to distinguish it. For example, the device information acquisition unit 33b of the medical information processing device 30 may read out device information including operator information (the same operator) provided from the operation device 20 from the memory 31, and the providing unit 33c may provide the device information (list of medical information) to the operation device 20. In this case, the display 23 of the operation device 20 displays device information (list of medical information) indicating the medical device 10 operable by the operator of the operation device 20, as shown in FIG. 9. This makes it possible to prevent the medical device 10 that should not be operated by the operator of the operation device 20 from being operated by mistake.

[0045] In the above embodiment, an example has been described in which the operator information (operator) and the medical device information (medical device 10) are associated with each other for each medical order in the medical information processing device 30. However, the operator information and the medical device information do not have to be associated with each medical order. For example, the medical information processing device 30 may store the operator information and the medical device information in association with each other, and provide the operation device 20 with a list of medical information (device information) including the medical device information associated with the operator information received from the operation device 20.

[0046] In the above embodiment, the medical information processing device 30 stores medical information indicating the medical device 10 that the operator can operate for each medical order. However, a workflow of medical processing (a series of medical processing consisting of one or more steps) determined according to a medical order may be stored as medical information. In this case, the operator information acquisition unit 33a acquires the operator information provided from the operation device 20, and the device information acquisition unit 33b acquires a workflow having the operator information acquired by the operator information acquisition unit 33a. The workflow includes device information indicating the medical device 10 that the operator can operate. The provision unit 33c provides the workflow having the device information acquired by the device information acquisition unit 33b to the operation device 20 (the sender of the operator information).

[0047] Second embodiment The second embodiment will be described below. In this embodiment, device information that takes into account the usage status of the medical device 10 is provided.

[0048] Fig. 10 is a diagram showing the configuration of the medical information processing apparatus 30 according to this embodiment. The medical information stored in the memory 31 includes usage information in addition to the various information shown in Fig. 3. The usage information includes information that indicates the usage status of the medical device 10. The usage status of the medical device 10 specifically includes information on the progress rate of a medical order, the waiting time until the medical device 10 becomes available, the operator operating the medical device 10, and the operation device 20 used by the operator. The usage information is transmitted from each medical device 10 to the medical information processing apparatus 30 at regular intervals, for example.

[0049] The processing circuitry 33 reads out and executes the programs stored in the memory 31, thereby functioning as an operator information acquisition unit 33a, a device information acquisition unit 33b, a providing unit 33c, and a usage information acquisition unit 33d.

[0050] 11 and 12, the usage information acquiring unit 33d acquires usage information from each medical device 10 via the network (step S204), and includes the acquired usage information in the corresponding medical information in the memory 31. Specifically, the usage information acquiring unit 33d updates the usage information associated with the medical device 10 that is the transmission source of the usage information in the medical information list to the acquired usage information.

[0051] The providing unit 33c provides the operation device 20 with a list of medical information (device information) including the medical device information associated with the operator information received from the operation device 20 (step S206). The medical information includes usage information indicating the latest usage status of the medical device 10.

[0052] The medical information processing device 30 may also acquire usage information from the medical device 10 at predetermined time intervals, and repeat the processes from step S205 to step S208 every time new usage information is acquired. This provides the operation device 20 with device information reflecting the latest usage status.

[0053] According to this embodiment, the medical information processing device 30 can provide the operation device 20 operated by the operator with device information having usage information that indicates the usage status of the medical device 10. This prevents the operator of the operation device 20 from accidentally operating the medical device 10 that should not be operated, and allows the operator of the operation device 20 to operate the medical device 10 while taking into consideration the usage status of the medical device 10.

[0054] (Modification of the second embodiment) The medical information processing device 30 may provide the medical device 10 that the operator of the operation device 20 can operate in a manner that allows the operator to identify the medical device 10 based on the usage information. This makes it possible to prevent the operator from erroneously operating the medical device 10 that should not be operated by the operator, even if the operator has been granted operation authority for the medical device 10, depending on the usage status of the medical device 10. In this case, for example, as shown in FIG. 13, the operator may be notified that the medical device 10 is being used in another medical order. At this time, the operation device 20 and the operator currently operating the selected medical device 10 may also be notified. In addition, the medical information processing device 30 may assign a priority order to the medical device 10 that the operator of the operation device 20 can operate, based on the usage information (usage status of the medical device 10). This makes it possible to select the medical device 10 depending on the usage status of the medical device 10, even if the operator has been granted operation authority for the medical device 10. The medical information processing device 30 may provide the medical device 10 that the operator of the operation device 20 can operate, depending on the usage information. This makes it possible to prevent an operator from accidentally operating a medical device 10 that should not be operated by the operator, even if the operator has been granted operation authority for the medical device 10, depending on the usage status of the medical device 10.

[0055] In the above embodiment, an example is shown in which the medical device 10 notifies the medical information processing device 30 of the usage status of the medical device 10, but the usage status of the medical device 10 may also be notified to the operating device 20 that operates the medical device 10.

[0056] (Third embodiment) A third embodiment will be described below. In this embodiment, an example will be described in which, when the medical device 10 is accessed from the operation device 20, authentication information of the operator is requested from the medical device 10.

[0057] 14 is a diagram showing communication processing performed between components of the medical information processing system 1 of this embodiment. A list of medical information in which operators and medical devices that the operators can operate are associated with each other is stored in the memory of each medical device 10. The list of medical information is periodically provided to each medical device 10 from the medical information processing device 30 via a network, for example.

[0058] As in the first embodiment, a list of medical information is provided from the medical information processing device 30 to the operation device 20. When the list of medical information is displayed on the operation device 20, the operator of the operation device 20 performs an operation to select the medical device 10 to be operated by the operator from among the displays of multiple medical devices connected to the network. The operation device 20 communicates with the medical device 10 selected by the operator. In response to an access from the operation device 20, the medical device 10 requests operator information. In response to a request from the medical device 10, the operation device 20 displays an input screen for operation manual information on the display 23. FIG. 15 is a diagram showing an example of the input screen for operator information. The input screen for operator information displays fields for inputting, for example, an operator ID, a password, a patient ID, and a patient name. When information is input to the input screen for operator information, the operator information providing unit 25b of the operation device 20 transmits the input information to the medical device 10 via the network.

[0059] The medical device 10 uses the information transmitted from the operation device 20 and a list of medical information stored in the memory to identify the operator of the operation device 20, determines whether the identified operator is associated with the medical device 10, and transmits the determination result to the operation device 20 via the network.

[0060] If the identified operator is not associated with the medical device 10 in the list of medical information, the medical device 10 determines that the accessing operator is an operator who cannot operate the medical device 10, and does not accept operations from that operator. On the other hand, if the identified operator is associated with the medical device 10 in the list of medical information, the medical device 10 determines that the accessing operator is an operator who can operate the medical device 10, and accepts operations from that operator.

[0061] In this embodiment, a list of medical information is stored in the medical device 10, and when an operator accesses the medical device 10, the accessed medical device 10 authenticates whether the accessing operator is an operator capable of operating the medical device 10, thereby more effectively preventing the operator from operating an unintended medical device 10.

[0062] In addition, when an operator accesses the medical device 10 from a certain operation device 20, the medical device 10 may only accept operations from the operation device 20 that was last accessed. For example, when an operator accesses the medical device 10 from the operation device 20 and tries to access and operate the medical device 10 from another operation device 20, the medical device 10 only accepts operations from the newly accessed operation device 20b, but does not accept operations from the operation device 20 that was previously logged in. With this configuration, for example, when the operation device 20 that is being operated after starting a medical order breaks down and the medical device 10 is accessed from another operation device 20 to continue the operation, the operation from the broken operation device 20 is invalid, so that erroneous operation due to the failure of the operation device 20 can be prevented.

[0063] (Fourth embodiment) The fourth embodiment will be described below. In this embodiment, the medical device 10 notifies the medical information processing device 30 of the results of medical orders one by one.

[0064] 16 is a diagram showing communication processing performed between components of the medical information processing system 1 of this embodiment. In this embodiment, the medical information processing device 30 acquires the results of medical orders (hereinafter referred to as order results) executed using the medical devices 10 from each medical device 10 via a shared network. The order results are, for example, image data generated by a medical image diagnostic device, examination data, and memory address information indicating the location (storage destination) of the examination data. The order results are transmitted from each medical device 10 to the medical information processing device 30 at regular intervals, for example.

[0065] The medical information processing device 30 stores the acquired order results in the memory 31. At this time, the acquired order results may be stored in association with a list of medical orders, or may be stored as standalone information. However, even when storing the order results as standalone information, it is preferable to assign identification information (e.g., a medical order ID) to the order results to associate them with the list of medical orders.

[0066] The order result may be generated by each operation device 20. In this case, the order result is transmitted from each operation device 20 to the medical information processing device 30.

[0067] According to at least one of the embodiments described above, in a medical information processing system in which at least one medical device and operating device are connected to a shared network, it is possible to prevent an operator from accidentally operating a medical device that should not be operated by the operator.

[0068] In the above description, an example has been described in which the medical information processing device 30 is a device independent of the medical device 10 and the operation device 20. However, the medical device 10 and the operation device 20 may be provided with various configurations provided in the medical information processing device 30. For example, the functions of each unit executed by the processing circuitry 33 of the medical information processing device 30 may be executed by the processing circuitry of each medical device 10 or the processing circuitry 25 of each operation device 20. In this case, the medical information stored in the memory 31 of the medical information processing device 30 is stored in advance in the memory of each medical device 10 or the memory 21 of each operation device 20.

[0069] 2, 4, and 10, each unit is realized by a single processing circuit 25, 33. However, a processing circuit may be configured by combining multiple independent processors, and each processor may realize each unit by executing a program. Also, each unit of the processing circuits 25, 33 may be implemented as an individual hardware circuit.

[0070] In addition, the operation device 20 and the medical information processing device 30 have been described as each performing multiple functions on a single console, but the multiple functions may be performed by different devices. For example, each part of the processing circuits 25 and 33 may be distributed and installed in different devices.

[0071] The term "processor" used in the above description means a circuit such as a central processing unit (CPU), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a programmable logic device (e.g., a simple programmable logic device (SPLD)), a complex programmable logic device (CPLD), and a field programmable gate array (FPGA)). When the processor is, for example, a CPU, the processor realizes a function by reading and executing a program stored in a memory circuit. On the other hand, when the processor is, for example, an ASIC, instead of storing the program in a memory circuit, the function is directly incorporated as a logic circuit in the circuit of the processor. Note that each processor in this embodiment is not limited to being configured as a single circuit for each processor, and may be configured as one processor by combining multiple independent circuits to realize the function. Furthermore, multiple components may be integrated into one processor to realize the function. The above description of the "processor" is the same for each of the following embodiments and modifications.

[0072] Although some embodiments have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, modifications, and combinations of embodiments can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope of the invention and its equivalents as described in the claims, as well as in the scope and spirit of the invention. [Explanation of symbols]

[0073] 1. Medical information processing system 10(10a-10n)…Medical equipment 20(20a-20n)…Operating device 30...Medical information processing device 21, 31…Memory 22, 32…Communication interface 23…Display 24…Input interface 25, 33...Processing circuit 25a…Input reception section 25b...Operator information provision department 25c…Device information notification section 25d…Connection 33a...Operator information acquisition section 33b…Device information acquisition unit 33c…Providing Department 33d…Usage information acquisition unit

Claims

1. A medical information processing device connected to an operation device and a plurality of medical devices connected to the operation device via a network, an operator information acquisition unit that acquires operator information identifying an operator of the operation device from the operation device; a device information acquiring unit that acquires device information that associates an operator with a medical device that the operator can operate; a providing unit that extracts, from among a plurality of medical devices that can be operated from the operation device, a medical device that can be operated by the operator identified by the operator information, based on the operator information and the device information, and provides the device information to the operation device in a manner that allows the extracted medical device to be identified; Each of the plurality of medical devices is a medical image diagnostic device, a radiation therapy device, or a surgical device. Medical information processing equipment.

2. a storage unit that stores a plurality of pieces of medical information in which operators are associated with medical devices that can be operated by the operators; the device information acquiring unit acquires, from the plurality of pieces of medical information stored in the storage unit, device information representing a medical device associated with an operator identified by the operator information acquired by the operator information acquiring unit; The medical information processing device according to claim 1 .

3. a storage unit that stores a plurality of pieces of medical information in which operators are associated with medical devices that can be operated by the operators; the device information acquisition unit acquires the plurality of pieces of medical information stored in the storage unit as the device information in response to the acquisition of the operator information; The medical information processing device according to claim 1 .

4. the providing unit provides the acquired device information in a manner connectable to a medical device that can be operated by the operator. The medical information processing device according to claim 1 .

5. a usage information acquisition unit that acquires usage information representing a usage status of the medical device; the device information acquisition unit acquires device information representing a medical device that can be operated by the operator based on the operator information and the usage information. The medical information processing device according to claim 1 .

6. a usage information acquisition unit that acquires usage information representing a usage status of the medical device; the providing unit provides the acquired device information in a manner that enables identification of a usage status of a medical device that can be operated by the operator. The medical information processing device according to claim 1 .

7. A medical information processing system including an operation device, a plurality of medical devices connected to the operation device via a network, and a medical information processing device connected to the operation device and each of the plurality of medical devices via the network, The operating device is an input receiving unit that receives input of operator information that identifies an operator; an operator information providing unit that provides the operator information to the medical image processing device, The medical information processing device includes: an acquisition unit that acquires the operator information provided from the operation device; a device information acquiring unit that acquires device information in which the operator is associated with a medical device that the operator can operate, based on the acquired operator information; a providing unit that extracts, from among a plurality of medical devices that can be operated from the operation device, a medical device that can be operated by the operator identified by the operator information, based on the operator information and the device information, and provides the device information to the operation device in a manner that allows the extracted medical device to be identified. Medical information processing system.

8. The operating device is a device information notifying unit that notifies the device information provided from the medical information processing device; The medical information processing system according to claim 7 .

9. The operating device is a connection unit that receives an operation by the operator to select a medical device to be operated from the device information and connects to the medical device selected by the operation via the network; The medical information processing system according to claim 8.

Images