JP2012247905A - Medical information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a medical information processing system which is adaptable to an emergency patient using a clinical application.SOLUTION: The medical information processing system includes a server device which provides a clinical application, and a plurality of client devices. The server device includes an application part, a selection part, and a proxy request part. The application part imparts permission to use the clinical application to a first client device which requests use of the clinical application when the number of client devices connected simultaneously to the server device does not reach a limit number of simultaneous use. The selection part selects one or more client devices capable of using the clinical application as second client devices among the plurality of client devices when the number of the client devices connected simultaneously to the server device reaches the limit number of simultaneous use. The proxy request part requests the second client devices to act for operation specified by the first client device.

Description

  Embodiments described herein relate generally to a medical information processing system having a license management function.

  There is a multi-user medical information processing system in which a server device and a plurality of client devices are connected via a communication network. This medical information processing system uses, for example, a thin client network system. In such a thin client environment, the server device manages a plurality of clinical applications for processing medical information, and the client device refers to the medical information by using the clinical application activated on the server device. can do. In one example, the client device is installed in a location (for example, an examination room) different from the installation location of the server device, and is used when performing image diagnosis using the function of the server device.

  In such a medical information processing system, at least one of the upper limit number of client devices allowed to be connected to the server device at the same time and the upper limit number of client devices allowed to use the clinical application simultaneously is determined in advance. There may be. In a medical information processing system that manages clinical applications where the maximum number of client devices that can be used simultaneously is defined, if the number of client devices using clinical applications reaches the maximum number, The use permission (license) of the clinical application is not given to the client apparatus that has requested the use of the application. In another medical information processing system, when the number of client devices using a clinical application has reached the upper limit, instead of being given permission to use the client device that has requested the use of the clinical application, for example, Other client devices with low priority are randomly deprived of permission to use.

JP-A-5-346851 JP 2002-328741 A

  In the medical information processing system described above, there is a problem that a situation in which it is impossible to deal with an emergency patient using the clinical application occurs because the use permission of the clinical application is not given. However, it is difficult to accept a form in which the use permission is randomly taken from other client devices. Therefore, in the medical information processing system, the number of client devices that are permitted to connect to the server device has reached a predetermined upper limit number, or the client devices that are permitted to use clinical applications. Even when the number reaches a predetermined upper limit, it is required to be able to respond to emergency patients using clinical applications.

  The purpose is that the number of client devices that are permitted to connect to the server device has reached a predetermined upper limit, or the upper limit that the number of client devices that are permitted to use clinical applications is predetermined. It is to provide a medical information processing system that can respond to emergency patients using clinical applications even when the number has been reached.

  A medical information processing system according to an embodiment includes a server device that provides a clinical application for processing medical information, and a plurality of client devices that can communicate with the server device via a communication network. The server device includes a determination unit, a license grant unit, a selection unit, and a proxy request unit. The determination unit determines whether or not the number of client devices to which use permission of the clinical application is given has reached a simultaneous usable number indicating the upper limit number of client terminals allowed to use the clinical application simultaneously. Determine. The granting unit is a first client that requests use of the clinical application among the plurality of client devices when the number of client devices to which use permission of the clinical application is not reached the simultaneous usable number The device is authorized to use the clinical application. When the number of client devices to which use permission of the clinical application is given reaches the number that can be used at the same time, the selection unit selects one of the plurality of client devices that can use the clinical application. The above client device is selected as the second client device. When the second client device is selected by the selection unit, the proxy requesting unit requests the second client device to perform the work specified by the first client device.

1 is a block diagram schematically showing a medical information processing system according to a first embodiment. The flowchart which shows an example of operation | movement of the medical information processing system of FIG. The figure which shows an example of the database which the connection management part shown in FIG. 1 hold | maintains. The block diagram which shows roughly the medical information processing system which concerns on 2nd Embodiment. The flowchart which shows an example of operation | movement of the medical information processing system of FIG. The block diagram which shows roughly the medical information processing system which concerns on 3rd Embodiment. The flowchart which shows an example of operation | movement of the medical information processing system of FIG.

  Hereinafter, a medical information processing system according to an embodiment will be described with reference to the drawings as necessary. Note that, in the following embodiments, the same numbered portions are assumed to perform the same operation, and repeated description is omitted.

(First embodiment)
FIG. 1 schematically shows a medical information processing system 100 according to the first embodiment. This medical information processing system 100 uses a computer network system called a thin client system. As illustrated in FIG. 1, the medical information processing system 100 includes a server device 110 and a plurality of client devices 150A and 150B. These client apparatuses 150A and 150B can communicate with the server apparatus 110 via a communication network. In FIG. 1, two client apparatuses 150A and 150B are shown for ease of explanation, but three or more client apparatuses may be provided. Hereinafter, the server device is simply referred to as a server, and the client device is simply referred to as a client. Further, when the clients 150A and 150B are not particularly distinguished, the subscript (alphabet) attached to the reference numerals is omitted and described as the client 150.

  The server 110 is a medical information processing apparatus that centrally manages medical information such as patient information (patient information) and provides one or more clinical applications 117 for processing the medical information to the client 150. The patient information is, for example, medical image data photographed by a medical image photographing device, examination data, an electronic medical record, and the like. Examples of the medical imaging apparatus include an X-ray diagnostic apparatus, an X-ray computed tomography (CT) apparatus, and a magnetic resonance imaging (MRI) apparatus. Examples of the clinical application 117 installed in the server 110 include a 3D image display application for processing medical image data and displaying a 3D image, a clinical analysis application for analyzing examination data, and the like. There is. The client 150 can refer to the medical information by accessing the server 110 and using the clinical application 117.

  In the medical information processing system 100 of the present embodiment, the server 110 manages licenses for connection (logon) to the server 110 by the client 150 and use of the clinical application 117 by the client 150. Specifically, the upper limit number of clients 150 allowed to connect to the server 110 at the same time and the upper limit number of clients 150 allowed to use each clinical application simultaneously are determined in advance. The upper limit number of clients that are allowed to be connected to the server 110 at the same time is referred to as a simultaneously connectable number, and the upper limit number of clients 150 that are allowed to use a clinical application simultaneously is referred to as a simultaneously usable number. Both the simultaneous connection possible number and the simultaneous usable number are also referred to as the number of licenses.

  The client 150 is a user terminal device operated by users such as doctors and laboratory technicians. The client 150 is, for example, a general-purpose computer device. The client 150 may be a medical image photographing apparatus such as an X-ray CT apparatus and an MRI apparatus. As shown in FIG. 1, the client 150 includes a communication unit 151, an operation unit 152, a display unit 153, a connection request unit 154, and a proxy request message creation unit 155.

  The communication unit 151 transmits various signals (for example, a connection request signal and an operation signal) generated in the client 150 to the server 110, and various signals (for example, a connection permission signal, a connection rejection signal, and an image signal) from the server 110. Etc.). The operation unit 152 includes an input device such as a keyboard and a mouse. The operation unit 152 receives an input from the user and generates an operation signal corresponding to the input. The display unit 153 displays an image corresponding to the image signal. As the display unit 153, for example, a CRT (cathode-ray tube) display, a liquid crystal display, an organic EL (electroluminescence) display, or the like can be used.

  The connection request unit 154 requests connection to the server 110. Specifically, the connection request unit 154 generates a connection request signal for establishing a connection with the server 110 and using the clinical application 117, and transmits the connection request signal to the server 110 via the communication unit 151. In the present embodiment, assuming that the client 150 makes a use request for the clinical application 117 simultaneously with the connection request, the connection request signal includes an application identifier for identifying the clinical application 117 that the client 150 desires to use. . That is, the connection request unit 154 requests the server 110 for permission to connect to the server 110 and permission to use the clinical application 117 by generating and transmitting a connection request signal including the application identifier of the desired clinical application 117. Even when the connection between the server 110 and the client 150 has already been established and only the use permission of the clinical application 117 is obtained, the connection request unit 154 transmits a connection request signal including the application identifier to the server 110. In this case, however, the processing related to connection permission described later is omitted.

  The proxy request message creation unit 155 provides a user with a graphical user interface (GUI) for creating a proxy request message when permission to use the clinical application 117 is not given. The proxy request message is for requesting a user of another client 150 to perform a task scheduled to be performed by the user using the own client 150.

  The server 110 includes a communication unit 111, a connection management unit 112, a license management unit 113, an application control unit 114, a proxy request unit 115, a selection unit 116, a clinical application 117, a data saving unit 118, and a medical information database (DB) 119. Prepare. In FIG. 1, the connection management unit 112, the substitution request unit 115, and the selection unit 116 are shown as separate components, but the connection management unit 112 has at least one function of the substitution request unit 115 and the selection unit 116. May be.

  The communication unit 111 transmits various signals (for example, a connection permission signal, a connection rejection signal, and an image signal) generated in the server 110 to the client 150, and various signals (for example, a connection request signal and an operation signal) from the client 150. Etc.). The connection management unit 112 manages the connection with the client 150, and performs control such as establishment and disconnection of the connection with the client 150. The connection management unit 112 holds a connection status database (DB) in which information about each client 150 with which the connection with the server 110 is established (that is, logged on) is described. In the connection status DB, for example, information such as a host name, an IP address, and a port number is described.

  The license management unit 113 determines whether to permit connection to the server 110 and further determines whether to permit use of the clinical application 117 specified by the application identifier included in the connection request signal. When permitting both the connection to the server 110 and the use of the clinical application 117, the license management unit 113 gives the use permission of the clinical application 117 to the client 150 of the connection request source, and connects to the server 110 and the clinical application 117. In the case where at least one of the use is not permitted, the use permission of the clinical application 117 is not given to the connection request source client 150. In the present embodiment, connection permission for the clinical application 117 includes connection permission for the server 110. Specifically, the license management unit 113 includes a determination unit 113A and a license grant unit 113B.

  The determination unit 113A determines whether or not the number of clients 150 connected to the server 110 has reached the number that can be used simultaneously. The determination unit 113A permits connection to the server 110 when the number of clients 150 currently connected to the server 110 has not reached the number that can be used simultaneously, and refuses connection otherwise. Further, the determination unit 113A determines whether the number of clients using the clinical application 117 specified by the application identifier in the connection request signal has reached the number that can be used simultaneously, and the client using the clinical application 117. When the number of 150 does not reach the simultaneously usable number, the use of the clinical application 117 is permitted, and otherwise, the use is not permitted. When both the connection to the server 110 and the use of the clinical application 117 are permitted by the determination unit 113A, the license grant unit 113B gives the use permission of the clinical application 117 to the connection request source client 150.

  The application control unit 114 performs control such as activation and termination of the clinical application 117.

  The proxy request unit 115 requests another client (for example, the client 150B) to perform the task scheduled to be performed by the connection requesting client (for example, the client 150A). Specifically, when the license management unit 113 does not give the connection request source client 150A permission to use the clinical application 117, the proxy request unit 115 instructs the client 150A to create a proxy request message, and the client 150A The proxy request message created by the client is transmitted to the other client 150B.

  The selection unit 116 selects the client 150B that is the transmission target of the proxy request message. The data saving unit 118 temporarily saves data during the work of the client 150 that has accepted the proxy. The medical information DB 119 stores medical information including patient information as described above.

  In the present embodiment, the clinical application 117 is executed on the server 110 in order to process medical information stored in the medical information DB 119. The clinical application 117 generates a display image including the processed medical information and a GUI for the user of the client 150 to operate. This display image is sent to the client 150 as an image signal. A GUI is displayed on the display unit 153 of the client 150 together with the medical information. The user of the client 150 can display desired medical information by operating the GUI with the operation unit 152, and can perform treatment (for example, treatment, surgery, etc.) on the patient while confirming the displayed medical information. it can.

Next, the operation of the medical information processing system 100 will be described with reference to FIG.
FIG. 2 shows an example of proxy request processing of the server 110. Here, it is assumed that the client 150A attempts to use the clinical application 117 by establishing a connection with the server 110, and the client 150B uses the clinical application 117 that the client 150A desires to use.

  First, in step S201, the connection request unit 154 of the client 150A transmits a connection request signal to the server 110 in order to request permission to use the desired clinical application 117. The connection request signal of this embodiment includes client information, an emergency flag, and an application identifier. This client information is information related to the connection request source client 150A, and includes, for example, a host name, an IP address, and a port number. The urgent flag is information for identifying whether or not the use of the clinical application 117 is urgent. The emergency flag is set to ON when the clinical application 117 needs to be used urgently, for example, when a suddenly ill patient occurs. The application identifier is information for identifying the clinical application 117 for which the connection requesting client 150A requests use permission. The connection request signal includes basic patient information (for example, a patient ID or name for identifying a patient) and information about a user who is operating the connection request source client 150A (for example, a user ID, a password, etc.). May be further included.

  In step S202, the connection management unit 112 of the server 110 receives a connection request signal from the client 150A. Upon receiving the connection request signal, the connection management unit 112 determines whether or not to connect to the client 150A and determines whether or not the clinical application 117 specified by the application identifier in the connection request signal can be used. The unit 113 is instructed.

  In step S <b> 203, the determination unit 113 </ b> A determines whether to permit connection of the client 150 </ b> A based on the number of clients connected to the server 110 and the number of simultaneously connectable clients. Specifically, the determination unit 113A permits connection when the number of connected clients does not reach the number of simultaneously usable clients, and connects when the number of connected clients reaches the number of simultaneously usable clients. Not allowed. If the connection is permitted, the process proceeds to step S204. If the connection is not permitted, the process proceeds to step S206. It should be noted that the determination unit 113A preliminarily calculates and holds a value obtained by subtracting the number of clients connected to the server 110 from the simultaneously connectable number as the remaining connectable number, and determines whether the remaining connectable number is 1 or more. It may be determined whether connection is possible by determining.

  In step S <b> 204, the determination unit 113 </ b> A determines whether to permit the use of the clinical application 117 based on the number of clients that are using the clinical application 117 and the number that can be used simultaneously. Specifically, the license management unit 113 permits the use when the number of clients that are using the clinical application 117 has not reached the number that can be used simultaneously, and the number of clients that are using the clinical application 117 is the number that can be used simultaneously. Use is not permitted when it has reached. As an example, the license management unit 113 holds a data table 300 that describes the number of simultaneously usable clients and the number of clients in use in association with the clinical applications APP1, APP2,..., APPn as shown in FIG. In this example, the license management unit 113 refers to the data table 300 in the clinical application identified by the application identifier, for example, the clinical application APP2, and the number of simultaneous use and the number in use associated with the clinical application APP2. Whether the clinical application APP2 can be used is determined by comparing the number of clients. If the use of the clinical application 117 is permitted, the process proceeds to step S205. If the use of the clinical application 117 is not permitted, the process proceeds to step S206.

  Note that the license management unit 113 pre-calculates and holds a value obtained by subtracting the number of clients in use from the simultaneously usable number as the remaining usable number, and the remaining usable number when the connection request signal is received. Whether or not connection is possible may be determined by determining whether or not is 1 or more. In this embodiment, any clinical application 117 can be used by all clients 150, but a client that can be used for each clinical application 117 may be set.

  When the connection to the server 110 is permitted in step S203 and the use of the clinical application 117 is permitted in step S204, the license grant unit 113B issues and gives the use permission of the clinical application 117 to the client 150A that is the connection request source. The connection management unit 112 is notified of permission to use. Further, the determination unit 113A increments the number of clients that are using the clinical application 117, and increments the number of clients that are connected to the server 110. The number of clients that are using the clinical application 117 indicates the number of clients 150 that are permitted to use the clinical application 117, and is also referred to as a first license issuance number. The number of clients connected to the server 110 indicates the number of clients 150 to which connection permission is given, and is also referred to as a second license issuance number.

  Upon receiving the use permission notification from the license management unit 113, the connection management unit 112 instructs the application control unit 114 to start the clinical application 117 for the client 150A that is the connection request source. The application control unit 114 activates the clinical application 117 for the connection requesting client 150A. Thereafter, the application control unit 114 notifies the connection management unit 112 that the activation of the clinical application 117 has been completed. Upon receiving the activation completion notification from the application control unit 114, the connection management unit 112 transmits a connection permission signal including the connection port number to the client 150A, and updates the connection status database.

  In step S205, when the client 150A receives a connection permission signal from the server 110 as a response to the connection request signal, the connection between the client 150A and the server 110 is established, and the clinical application 117 can be used by the client 150A. become.

  On the other hand, if the connection to the server 110 is not permitted in step S203, or if the use of the clinical application 117 is not permitted in step S204, the license management unit 113 prohibits the use of the clinical application 117. Notify the connection management unit 112. In step S206, when the connection management unit 112 receives the use non-permission notification from the license management unit 113, the connection management unit 112 determines whether the emergency flag in the connection request signal is on or off. When the urgent flag is off, that is, when it is not urgent, the connection management unit 112 transmits a connection rejection signal indicating that the use permission of the clinical application 117 is not given to the client 150A, and the series of processing ends.

  When the urgent flag is on, that is, in the case of an emergency, the connection management unit 112 instructs the selection unit 116 to select a target client that transmits the proxy request message. In step S207, the selection unit 116 refers to, for example, the connection status DB held by the connection management unit 112 and can use one or more clinical applications 117 identified by the application identifier from the connected clients 150. Client 150 (for example, client 150B) is selected as the destination of the proxy request message. When the number of clients that are using the clinical application 117 is equal to the number that can be used simultaneously, the client 150 that can use the clinical application 117 refers to a client 150 that is granted permission to use the clinical application 117. When the number of clients using the clinical application 117 is less than the number that can be used simultaneously, the clients 150 that can use the clinical application 117 indicate all the clients 150 that are connected to the server 110. This is because, if the number of clients using the clinical application 117 is less than the number that can be used simultaneously, any client 150 that is connected to the server 110 can obtain permission to use the clinical application 117. Because it can.

  As a method for selecting a client to which a proxy request message is to be transmitted, a priority table in which priorities are set for each connected client is prepared, and the priority is the highest among the clients 150 that can use the clinical application 117. There is a method of selecting a low client or one or more clients whose priority is lower than a threshold. In another selection method, users are grouped in advance, and the client 150 used by a user belonging to the same group as the user of the connection request source client 150A is selected. In still another selection method, the client 150A is selected who is permitted to use the same clinical application 117 as the clinical application 117 that the client 150A desires to use. Further, the destination of the proxy request message may be selected by appropriately combining these selection methods. Alternatively, the proxy request message may be transmitted to all clients 150 that can use the clinical application 117.

  The selection unit 116 sends information regarding the connection request source client 150A and information regarding the selected client (or client group) 150B (eg, host name, IP address, port number, etc.) to the proxy request unit 115. Information regarding the connection request source client 150 </ b> A may be transmitted to the proxy request unit 115 by the connection management unit 112.

  In step S208, the proxy request unit 115 instructs the connection request source client 150A to generate a proxy request message. When the proxy request message creating unit 155 of the client 150 </ b> A receives the proxy request message creation instruction from the server 110, the proxy request message creating unit 155 displays a message prompting the user to create the proxy request message on the display unit 153. For example, a message such as “A desired application cannot be used due to a limitation on the number of licenses. Would you like to ask another user to perform the work?” Is displayed on the display unit 153, for example.

  When the user of the client 150A requests a substitute for work, the substitute request message creating unit 155 provides the user with a GUI for creating a substitute request message. In step S209, the user creates a proxy request message using the provided GUI. The proxy request message creation unit 155 transmits the proxy request message created by the user to the server 110 via the communication unit 151. The proxy request message includes client information, patient basic information, requested work content information, comments, and the like. The requester information is information regarding the user who is using the connection requesting client 150A, and includes, for example, a group (department), name, and contact information. The basic patient information is information indicating a patient ID and a name for identifying a patient. The requested work content information is information regarding the requested work such as the clinical application 117 to be used and the treatment content.

  In step S210, upon receiving the proxy request message from the client 150A, the proxy request unit 115 transmits the received proxy request message to the client 150B or the client group selected by the selection unit 116. The proxy request message is displayed on the display unit 153 of the client 150B that has received the proxy request message from the server 110. In addition to the proxy request message, display unit 153 displays a selection button for selecting whether to accept or reject the proxy for the work specified by the proxy request message. The user of the client 150B responds to the proxy request message by selecting either acceptance or rejection using the operation unit 152.

  In step S211, the proxy request unit 115 of the server 110 receives a response (acceptance or rejection) from the requested client 150B, and determines whether there is an accepted client. If no client has accepted, the proxy request unit 115 notifies the client 150A that the proxy has not been accepted. In this case, on the display unit 153 of the client 150A, for example, a message such as “The work substitution has not been accepted” is displayed, and the series of processing ends. On the other hand, when the proxy is accepted by a certain client 150B, the proxy request unit 115 notifies the client 150A that the proxy of the work has been accepted, and the process proceeds to step S212. In this case, for example, a message such as “A substitute for work has been received by Mr. XXX” is displayed on the display unit 153 of the client 150A. “XXX” indicates a user ID (for example, a login name) of a user who uses the client 150B who has accepted the proxy.

  In step S212, the clinical application 117 interrupts the work currently being performed by the client 150B that accepted the substitution, and temporarily saves data in the middle of the work of the client 150B to the data saving unit 118. Furthermore, the clinical application 117 reads out patient information specified by the patient basic information from the medical information DB 119. In step S213, the client 150B performs work designated by the proxy request message from the client 150A, for example, treatment for an emergency patient. After the substitution work is completed, in step S214, the client 150B instructs the server 110 to resume the suspended work. In the server 110, the clinical application 117 reads the data stored in the data saving unit 118, and the work is performed. Restore the interrupted state.

  As described above, in the medical information processing system 100, when the client 150A that is the connection request source is not permitted to use the clinical application, the server 110 requests the other client 150B to perform the work, and thereby the clinical information is processed. It is possible to respond to an emergency patient using the application 117.

  In the present embodiment, an example has been described in which both the simultaneously connectable number and the simultaneously usable number are determined, but only one of the simultaneously connectable number and the simultaneously usable number may be determined. In the example in which only the simultaneous use number is determined, the license granting unit 113B provides the clinical request to the connection request source client 150 when the number of clients to which the use permission of the clinical application 117 is not reached the simultaneous use number. The use permission of the application 117 is given.

  In addition, the number of simultaneous usages may not be determined for all clinical applications 117, but the number of simultaneous usages may be determined only for a specific clinical application.

  Each unit of the server 110 and the client 150 described above can be realized by hardware, software, or a combination of hardware and software. The server 110 has a large-scale hardware resource as compared with the client 150. As a specific hardware configuration, the server 110 includes a CPU (Central Processing Unit), a RAM (Random Access Memory), a hard disk drive (HDD), a network device, and the like. The HDD functions as a storage unit that stores a control program for controlling each unit of the server 110, a program for the clinical application 117, a connection status DB, a medical information DB 119, and the like. Further, the HDD is also used as the data saving unit 118. The CPU develops a control program on the RAM and controls the operation of the server 110 according to the control program. Further, the CPU develops and executes the clinical application 117 on the RAM. The network device is a communication unit 111 that communicates with the client 150 via a communication network under the control of the CPU.

  The client 150 includes a CPU, ROM, RAM, network device, keyboard, mouse, display, and the like. The ROM stores a control program for controlling each unit of the client 150 and the like. The CPU expands the control program on the RAM and controls the operation of the client 150 according to the control program. The network device is a communication unit 151 that communicates with the server 110 via a communication network under the control of the CPU. From the viewpoint of improving management cost and security, the client 150 preferably does not include an information recording / reproducing apparatus using a recording medium such as an HDD or an optical disk, but includes such an HDD, an information recording / reproducing apparatus, and the like. Also good.

  As described above, in the medical information processing system 100 according to the present embodiment, the number of clients who are permitted to use the clinical application 117 has reached the number that can be used simultaneously, or the connection to the server 110. Even if the client 150A that has requested use of the clinical application 117 is not permitted to use the clinical application 117 because the number of clients to which permission has been granted has reached the number of simultaneous connections, the server 110 The clinical application 117 can be used to address an urgent patient by requesting the other client 150B to perform the work.

(Second Embodiment)
In the second embodiment, the use permission of the clinical application 117 is given to the connection request source client 150A because the number of clients to which the use permission of the clinical application 117 is given has reached the simultaneous use number in an emergency. If not, the use of the clinical application 117 on the client 150A is temporarily enabled by temporarily stopping the use of the clinical application 117 on the other client 150B.

  FIG. 4 schematically shows a medical information processing system 400 according to the second embodiment. The difference between the medical information processing system 400 in FIG. 4 and the medical information processing system 100 in FIG. 1 is that the server 110 of the medical information processing system 400 includes a switching unit 401 instead of the proxy request unit 115. The switching unit 401 temporarily switches the connection destination of the clinical application 117. Specifically, the switching unit 401 changes the transmission destination of the image signal of the clinical application 117 from the client 150B that is using the clinical application 117 to the connection request source client 150A, and after the work in the client 150A is completed. The transmission destination of the image signal is returned to the client 150B. In other words, the use permission of the clinical application 117 is temporarily transferred from the client 150B to the connection requesting client 150A, and then the use permission is returned to the client 150B.

Next, the operation of the medical information processing system 400 will be described with reference to FIG.
FIG. 5 shows an example of the switching process of the server 110. Here, it is assumed that the client 150A makes a use request for a specific clinical application 117, and the client 150B uses the clinical application 117. Furthermore, it is assumed that only the number that can be used simultaneously is determined. Steps S501 to S505 in FIG. 5 are the same processes as steps S201, S202, and S204 to S206 in FIG. 2, respectively, and thus detailed description thereof is omitted.

  In step S <b> 501, the client 150 </ b> A transmits a connection request signal including the application identifier to the server 110 in order to obtain permission to use the desired clinical application 117. In step S502, the server 110 receives a connection request signal from the client 150A. In step S503, the determination unit 113A in the license management unit 113 determines whether to permit the use of the clinical application 117 specified by the application identifier in the connection request signal. When the use of the clinical application 117 is permitted, the license grant unit 113B grants the use permission of the clinical application 117 to the connection request source client 150A. In step S504, the application control unit 114 activates the clinical application 117 for the client 150A. Thus, when the number of clients using the clinical application 117 is less than the number that can be used simultaneously, the client 150A can use the desired clinical application 117.

  When the number of clients that are using the clinical application 117 is equal to the number that can be used simultaneously, the use permission of the clinical application 117 is not given. In step S505, the connection management unit 112 determines whether the emergency flag in the connection request signal is on or off. If the emergency flag is off, the client 150A cannot use the desired clinical application 117.

  On the other hand, when the emergency flag is on, the connection management unit 112 instructs the selection unit 116 to select the client 150 to be switched. In step S506, the selection unit 116 refers to the connection status DB held by the connection management unit 112 and selects one client (for example, client) to be switched from among the clients 150 using the clinical application 117. 150B) is selected. As a selection method, for example, there is a method of preparing a priority table in which priority is set for each connected client, and selecting a client having the lowest priority among clients using the clinical application 117. . In another selection method, users are grouped in advance, and a client used by a user belonging to the same group as the user of the connection request source client 150A is selected. The selection unit 116 sends information regarding the connection request source client 150A and information regarding the client 150B selected as a switching target to the switching unit 401.

  In step S507, the switching unit 401 switches the connection destination of the clinical application 117 from the selected client 150B to the connection request source client 150A. Specifically, first, the switching unit 401 sends a switching command to the application control unit 114. When receiving the switching command, the application control unit 114 controls the clinical application 117 as follows. That is, the clinical application 117 generates an image signal including a screen in which the GUI cannot be operated (for example, a screen in which all buttons cannot be pressed) and a use interruption message, and transmits the image signal to the client 150B. The intermediate data is temporarily saved in the data saving unit 118. On the display unit 153 of the client 150B, for example, a use interruption message such as “Urgent use request has occurred. Temporary use will be interrupted” is displayed, and the clinical application 117 cannot be operated on the client 150B.

  Next, the application control unit 114 prepares the clinical application 117 for the client 150A, and notifies the connection management unit 112 of the completion of preparation via the switching unit 401. The connection management unit 112 transmits a connection permission signal to the client 150A and updates the connection status DB. The connection permission signal of the present embodiment includes a message indicating that it is in a temporarily borrowed state together with the connection port number.

  In step S508, the client 150A receives the connection permission signal and connects to the connection port specified by the connection permission signal. As a result, the clinical application 117 can be used by the client 150A. When the basic patient information is included in the connection request signal in step S501, the patient information specified by the basic patient information is read from the medical information DB 119, and the clinical application 117 is activated with the patient information already input. It may be.

  When the emergency work is finished, a notification indicating that the use of the clinical application 117 is finished is sent from the client 150A to the application control unit 114 of the server 110. The application control unit 114 notifies the connection management unit 112 of the end of use of the clinical application 117 by the client 150A. The connection management unit 112 disconnects the connection with the client 150A and instructs the switching unit 401 to perform switching again. Furthermore, the connection management unit 112 updates the connection status DB.

  In step S509, the switching unit 401 receives a re-switching instruction from the connection management unit 112 and performs re-switching processing. Specifically, the switching unit 401 sends a re-switching command to the application control unit 114, and the application control unit 114 that has received the re-switching command prepares the clinical application 117 for the client 150B. The clinical application 117 reads the data temporarily stored in the data saving unit 118 and restores the state at the time of the work interruption. Thereafter, the clinical application 117 generates an image signal including an operable GUI screen and medical information, and transmits the generated image signal to the client 150B. This again allows the clinical application 117 to be used by the client 150B.

  As described above, in the medical information processing system 400 according to the present embodiment, since the number of clients to which the use permission of the clinical application 117 is given reaches the number that can be used simultaneously, the use permission of the clinical application 117 is given to the client 150A. Is not provided, the server 110 temporarily stops the use of the clinical application 117 by the other client 150B, and enables the use of the clinical application 117 by the connection requesting client 150A during the stop. This allows an emergency patient to be addressed using the clinical application 117 at the client 150A.

  In the present embodiment, the case where the use permission of the clinical application 117 is not given to the client 150A has been described. However, even when the connection permission is not given to the client 150A, the switching unit 401 is similar to the switching process described above. Processing can be performed. In brief, when connection permission is not given to the client 150A, the switching unit 401 temporarily disconnects the connection with the client 150B selected by the selection unit 116 and temporarily connects with the client 150A. The connection management unit 112 is instructed to establish it. Then, after the emergency work by the client 150A is completed, the switching unit 401 instructs the connection management unit 112 to disconnect the connection with the client 150A and reestablish the connection with the client 150B. Therefore, when the connection permission is not given to the client 150A of the connection request source because the number of clients connected to the server 110 has reached the simultaneous connection possible number, the server 110 disconnects the connection with the other client 150B. An emergency patient can be dealt with by temporarily permitting connection with the client 150A.

(Third embodiment)
In the third embodiment, the use permission of the clinical application 117 is given to the connection request source client 150A because the number of clients to which the use permission of the clinical application 117 is given has reached the simultaneous use number in an emergency. If not, by temporarily suspending the clinical application 117 used by the other client 150B, the clinical application 117 can be temporarily used by the client 150A of the connection request source. Even when the use permission of the clinical application 117 is not given to the connection requesting client 150A, in the case of an emergency, the clinical application 117 can be temporarily used in the connection requesting client 150A. The third embodiment is the same. However, in the second embodiment, the number of activations of the clinical application 117 is always less than or equal to the number that can be used at the same time, whereas in the third embodiment, the clinical application 117 used by the client 150B is suspended. Since the clinical application 117 is newly activated for the client 150A, the number of activations of the clinical application 117 may exceed the number that can be used simultaneously. However, also in the third embodiment, the number of clients 150 that can simultaneously operate the clinical application 117 is limited to a number that can be used simultaneously.

  FIG. 6 schematically shows a medical information processing system 600 according to the third embodiment. The server 110 of this embodiment has a configuration in which the switching unit 401 is deleted from the server 110 of the second embodiment shown in FIG. Hereinafter, the operation of the medical information processing system 600 according to the third embodiment will be described focusing on differences from the second embodiment.

  FIG. 7 shows an example of the operation of the medical information processing system 600. Steps S701 to S705 in FIG. 7 are the same as steps S201, S202, and S204 to S206 in FIG.

  In step S <b> 706, the selection unit 116 selects one client to be suspended from the clients 150 that are using the clinical application 117. In this embodiment, when an emergency use request is generated in a state where the number of clients 150 to which use permission of the clinical application 117 is given is equal to the number of simultaneous use, the selection unit 116 connects the connection held by the connection management unit 112. With reference to the situation DB, one client (for example, client 150B) to be suspended is selected from the clients 150 using the clinical application 117. The selection method can be the same as the method described with reference to step S506 in FIG. The selection unit 116 sends information related to the connection request source client 150A and information related to the client 150B selected as a suspension target to the application control unit 114.

  In step S707, the application control unit 114 places the clinical application 117 activated for the client 150B selected by the selection unit 116 into a pause state. In step S708, the application control unit 114 activates the clinical application 117 for the connection request source client 150A. In the client 150B, as in the case of the second embodiment, the clinical application 117 becomes inoperable and a use interruption message is displayed. However, in this embodiment, the image signal transmission destination of the dormant clinical application 117 remains set in the client 150B. The clinical application 117 temporarily saves data during the operation of the client 150B in the data saving unit 118.

  Thereafter, the application control unit 114 notifies the connection management unit 112 that the clinical application 117 for the connection requesting client 150A has been started. The connection management unit 112 transmits a connection permission signal including a message indicating a temporary borrowing state and a connection port number to the client 150A. In step S709, the client 150A connects to the connection port specified by the connection permission signal, and as a result, the client 150A can use the clinical application 117.

  When the emergency work of the client 150A ends, the connection between the client 150A and the server 110 is disconnected. In step S710, the application control unit 114 ends the clinical application 117 for the client 150A. In step S711, the application control unit 114 resumes (resumes) the clinical application 117 for the client 150B. The clinical application 117 for the client 150B reads the data saved in the data saving unit 118 and restores the state at the time of the work interruption. Further, the clinical application 117 generates an image signal including an operable GUI and medical information, and transmits the image signal to the client 150B. This again allows the clinical application 117 to be used by the client 150B.

  As described above, in the medical information processing system 600 according to the present embodiment, since the number of clients that are permitted to use the clinical application 117 has reached the number that can be used simultaneously, the connection request source client 150A receives the clinical application. When the use permission of 117 is not given, the server 110 puts the clinical application 117 activated for the other client 150B into a dormant state and activates the clinical application 117 for the connection requesting client 150A. An emergency patient can be addressed using the clinical application 117 at 150A.

  Note that the above-described first to third embodiments may be combined. For example, when the proxy is rejected by all clients 150B that transmitted the proxy request message in the first embodiment, the processing described in the second embodiment or the third embodiment may be executed. .

  Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

DESCRIPTION OF SYMBOLS 100 ... Medical information processing system, 110 ... Server apparatus, 111 ... Communication part, 112 ... Connection management part, 113 ... License management part, 113A ... Determination part, 113B ... License grant part, 114 ... Application control part, 115 ... Proxy request 116: Selection unit, 117 ... Clinical application, 118 ... Data saving unit, 119 ... Medical information database, 150, 150A, 150B ... Client device, 151 ... Communication unit, 152 ... Operation unit, 153 ... Display unit, 154 ... Connection request unit, 155... Proxy request message creation unit, 400... Medical information processing system, 401... Switching unit, 600.

Claims (7)

A medical information processing system comprising a server device that provides a clinical application for processing medical information, and a plurality of client devices that can communicate with the server device via a communication network,
The server device
Determining whether or not the number of client devices that are permitted to use the clinical application has reached the number that can be used simultaneously indicating the upper limit number of client terminals that are allowed to use the clinical application simultaneously And
The first client device that requests use of the clinical application among the plurality of client devices when the number of client devices to which use permission of the clinical application is granted does not reach the simultaneously usable number, A granting section that grants permission to use clinical applications;
One or more client devices that can use the clinical application from among the plurality of client devices when the number of client devices to which use permission of the clinical application is granted reaches the simultaneously usable number A selection unit for selecting as a second client device;
An agent requesting unit for requesting the second client device to perform an operation designated by the first client device when the second client device is selected by the selecting unit;
A medical information processing system comprising: The determination unit determines whether or not the number of client devices connected to the server device at the same time has reached the number of simultaneously connectable devices indicating the upper limit number of client devices allowed to be connected to the server device at the same time. Further determine
In the selection unit, when the number of client devices connected to the server device at the same time has reached the simultaneously usable number, and the number of client devices connected to the server device at the same time are the number of simultaneously connectable devices. The at least one client device that can use the clinical application is selected as the second client device from the plurality of client devices in at least one of the cases where the second client device is reached. The medical information processing system according to 1.   3. The server device according to claim 1, further comprising a data saving unit that temporarily saves data in the middle of the work of the client device that has accepted the work substitution of the second client device. 4. The medical information processing system described. The server device further includes a switching unit that temporarily switches the connection destination of the clinical application,
When the substitution of the work is rejected from any of the second client devices, the switching unit switches the connection destination of the clinical application from any one of the second client devices to the first client device. The medical information processing system according to claim 1. The server device further includes an application control unit that controls the clinical application,
The application control unit temporarily puts a clinical application used by any one of the second client devices into a dormant state when substitution of the work is rejected from any of the second client devices, The medical information processing system according to claim 1, wherein the clinical application is temporarily activated for the first client device. A medical information processing system comprising a server device that provides a clinical application for processing medical information, and a plurality of client devices that can communicate with the server device via a communication network,
The server device
Determining whether or not the number of client devices that are permitted to use the clinical application has reached the number that can be used simultaneously indicating the upper limit number of client terminals that are allowed to use the clinical application simultaneously And
The first client device that requests use of the clinical application among the plurality of client devices when the number of client devices to which use permission of the clinical application is granted does not reach the simultaneously usable number, A granting section that grants permission to use clinical applications;
One of the plurality of client devices to which use permission of the clinical application is given when the number of client devices to which use permission of the clinical application is given reaches the simultaneously usable number A selecting unit for selecting the client device of the second client device as a second client device;
A switching unit that temporarily switches the connection destination of the clinical application from the second client to the first client when the second client device is selected by the selection unit;
A medical information processing system comprising: A medical information processing system comprising a server device that provides a clinical application for processing medical information, and a plurality of client devices that can communicate with the server device via a communication network,
The server device
Determining whether or not the number of client devices that are permitted to use the clinical application has reached the number that can be used simultaneously indicating the upper limit number of client terminals that are allowed to use the clinical application simultaneously And
The first client device that requests use of the clinical application among the plurality of client devices when the number of client devices to which use permission of the clinical application is granted does not reach the simultaneously usable number, A granting section that grants permission to use clinical applications;
One of the plurality of client devices to which use permission of the clinical application is given when the number of client devices to which use permission of the clinical application is given reaches the simultaneously usable number A selecting unit for selecting the client device of the second client device as a second client device;
When the second client device is selected by the selection unit, the clinical application used by the second client device is temporarily suspended and the clinical application is temporarily activated for the first client device. An application control unit,
A medical information processing system comprising:

Images