Program, image management device, and image management method

Abstract

To facilitate management of image data when an imaging apparatus is used.SOLUTION: A program causes a computer to execute processing of setting an imaging apparatus group consisting of a plurality of imaging apparatuses in response to a user's operation to select a plurality of imaging apparatuses, processing of registering identification information capable of identifying a subject in association with the imaging apparatus group, processing of acquiring a plurality of images picked up by the imaging apparatuses belonging to the imaging apparatus group, and processing of associating the plurality of acquired images with each other by using the identification information.SELECTED DRAWING: Figure 13

Description

[Technical field]

[0001] The present invention relates to a program, an image management device, and an image management method. [Background technology]

[0002] 2. Description of the Related Art Conventionally, there is known a technique for capturing images of a plurality of parts of a subject (such as a patient) using a single imaging device for capturing an image (for example, Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] However, the above-mentioned conventional technology is based on the assumption that a single imaging device is used for imaging, and has a problem in that it is not easy to manage image data when it is necessary to switch imaging devices.

[0005] An object of the present invention is to facilitate management of image data when using an imaging device. [Means for solving the problem]

[0006] In order to solve the above problems, the program according to the present invention comprises: On the computer, A process of setting an imaging device group consisting of a plurality of imaging devices in response to a user's operation of selecting the plurality of imaging devices; a process of registering identification information capable of identifying a subject in association with the group of image capture devices; A process of acquiring a plurality of images captured by an imaging device belonging to the imaging device group; A process of associating the acquired multiple images with the identification information; Execute the command. Effect of the Invention

[0007] According to the present invention, it is possible to easily manage image data when using an imaging device. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram showing a configuration of a medical image management system. [Diagram 2] FIG. 2 is a side view of the first camera. [Diagram 3] FIG. 4 is a side view of the second camera. [Figure 4] FIG. 2 is a block diagram showing a main functional configuration of the first camera. [Diagram 5] FIG. 4 is a block diagram showing a main functional configuration of the second camera. [Figure 6] 2 is a block diagram showing the main functional configuration of the medical image management apparatus. FIG. [Figure 7] FIG. 13 is a diagram showing a camera group setting screen. [Figure 8] FIG. 13 is a diagram showing a patient ID input screen for inputting a patient ID. [Figure 9] FIG. 13 is a diagram showing camera group management data associated with a patient ID. [Figure 10] FIG. 11 is a diagram showing the operation of transmitting medical images from the first camera and the second camera. [Figure 11] FIG. 4 is a diagram showing the contents of image management data. [Figure 12] 13 is a flowchart showing a control procedure of a camera group setting process. [Figure 13] 13 is a flowchart showing a control procedure for medical image registration processing. [Figure 14] 13 is a diagram showing a transmission operation of a medical image according to a modified example. [Figure 15] 13 is a flowchart showing a control procedure of medical image registration processing according to a modified example. [Figure 16]FIG. 13 is a diagram showing the contents of image management data according to a modified example. [Figure 17] FIG. 13 is a diagram showing a camera group setting screen. [Figure 18] 10 is a flowchart showing a control procedure of medical image registration processing according to the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0010] (First embodiment) <Configuration of medical image management system> FIG. 1 is a block diagram showing the configuration of a medical image management system 1. As shown in FIG. The medical image management system 1 (image management system) includes a first camera 10 (first imaging device), a second camera 20 (second imaging device), a third camera 30, and a medical image management device 40 (image management device). The medical image management system 1 is installed in a medical institution such as a hospital. The first camera 10, the second camera 20, and the third camera 30 are medical cameras used by a doctor to examine a patient (subject). The first camera 10, the second camera 20, and the third camera 30 are operated by a doctor to capture an image of a part of the patient such as an affected area and generate image data of a medical image (image). The number of cameras included in the medical image management system 1 is not limited to three, and may be two or four or more.

[0011] The medical image management device 40 is connected to the first camera 10, the second camera 20, and the third camera 30 by wireless or wired connection so as to be able to perform data communication. In FIG. 1, the medical image management device 40 is directly connected to the first camera 10, the second camera 20, and the third camera 30, but this is not limited thereto, and the medical image management device 40 may be indirectly connected to each camera. For example, in a configuration in which the medical image management device 40 is communicatively connected to an access point of a wireless LAN, the first camera 10, the second camera 20, and the third camera 30 may transmit and receive data to and from the medical image management device 40 via wireless communication with the access point. The medical image management device 40 manages image data of medical images captured by the first camera 10, the second camera 20, and the third camera 30 and transmitted to the medical image management device 40. Hereinafter, "image data of medical images" will also be simply referred to as "medical images".

[0012] Next, a description will be given of the configurations of the first camera 10 and the second camera 20. The configuration of the third camera 30 is arbitrary, and may be the same as the first camera 10 or the second camera 20, or may be different from the configurations of both the first camera 10 and the second camera 20. FIG. 2 is a side view of the first camera 10. As shown in FIG. FIG. 3 is a side view of second camera 20. As shown in FIG. As shown in FIG. 2, first camera 10 is capable of capturing an image at a viewing angle θ1 in the up-down direction (vertical direction) when first camera 10 is held horizontally. 3, the second camera 20 can capture an image at an angle of view θ2 larger than the angle of view θ1 in the vertical direction. In other words, the focal length of the second camera 20 is shorter than the focal length of the first camera 10. Therefore, the first camera 10 has a first imaging range R1 shown in FIG. 2, and the second camera 20 has a second imaging range R2 shown in FIG. 3, and the vertical length of the second imaging range R2 is longer than the vertical length of the first imaging range R1 (first imaging range). 2 and 3, the angle of view of the second camera 20 in the left-right direction (horizontal direction) when the first camera 10 and the second camera 20 are held horizontally is also larger than the angle of view of the first camera 10. Therefore, the length in the left-right direction of the second imaging range R2 of the second camera 20 is longer than the length in the left-right direction of the first imaging range R1 of the first camera 10. For the above reasons, the second imaging range R2 of the second camera 20 is larger than the first imaging range R1 of the first camera 10.

[0013] The first camera 10, which has a relatively small angle of view compared to the second camera 20, is preferably used to capture an image of an affected area (first region) inside the patient's body. In this embodiment, the first camera 10 is used to capture an image of the internal vulva (cervix, etc.) of a female patient as the first region. In other words, the first camera 10 is used to capture an image in colposcopy. On the other hand, the first camera 10 has a small angle of view and is therefore not suitable for imaging a part (e.g., the vulva) on the surface of the patient's body that is over a certain range or more. For this reason, the part on the surface of the patient's body is imaged by the second camera 20, which has a relatively large angle of view. In this embodiment, the second camera 20 is used to image the patient's vulva, which is a second part different from the first part.

[0014] 2, the first camera 10 includes a light-emitting unit 15 for illuminating the area of ​​the subject to be imaged when imaging. The light-emitting unit 15 has a normal light 151, a green light 152, and a polarized light 153, and one of these three lights is selected and used by the operator. The normal light 151 emits normal white light. The green light 152 emits green light that mainly contains visible light in the green wavelength range. After applying acetic acid to the cervix, the green light 152 is used as illumination to capture an image, thereby enabling a medical image that emphasizes the blood vessels of the cervix to be captured. The polarized light 153 emits linearly polarized light. The polarized light 153 may be a light that emits light with a random polarization direction and is equipped with a polarizer that transmits linearly polarized light. By using the polarized light 153 as illumination and capturing an image through a polarizing filter, surface reflection on mucous membranes, etc. can be suppressed. The brightness of normal light 151, green light 152, and polarized light 153 is higher than the brightness of light-emitting unit 25 of second camera 20. First camera 10 equipped with high-brightness light-emitting unit 15 is suitable for capturing images of the inner vulva, which is difficult for external light to reach.

[0015] 3, the second camera 20 includes a light-emitting unit 25 for illuminating a part of a subject to be imaged when imaging. The light-emitting unit 25 emits normal white light, similar to the normal light 151 of the first camera 10. Note that if there is a sufficient amount of external light when imaging, the light-emitting unit 25 does not need to be used.

[0016] Next, the functional configurations of the first camera 10, the second camera 20 and the medical image management device 40 will be described with reference to FIGS.

[0017] FIG. 4 is a block diagram showing the main functional configuration of first camera 10. As shown in FIG. The first camera 10 includes a CPU 11 (Central Processing Unit), a RAM 12 (Random Access Memory), a memory unit 13, an imaging unit 14, a light emitting unit 15, a display unit 16, an operation unit 17, a communication unit 18, etc., and each of these units is connected by a bus 19.

[0018] The CPU 11 is a processor that reads and executes the program 131 stored in the storage unit 13 and controls the operation of the first camera 10 by performing various arithmetic processing. The first camera 10 may have multiple processors (e.g., multiple CPUs), and the multiple processes performed by the CPU 11 of this embodiment may be executed by the multiple processors. In this case, the multiple processors may be involved in a common process, or the multiple processors may independently execute different processes in parallel. When imaging a patient, the CPU 11 causes the light emitting unit 15 to emit light in response to settings or a user operation, and causes the imaging unit 14 to perform imaging in response to a user operation that instructs imaging, thereby generating image data of a medical image of the patient. The CPU 11 can also assign a patient ID (identification information) that can identify the imaged patient to the generated medical image as incidental information. The patient ID may be included in, for example, EXIF ​​(Exchangeable image file format) information of the medical image. This patient ID is input by, for example, a doctor who is the operator of first camera 10, using operation unit 17 prior to imaging by first camera 10. The EXIF ​​information may include identification information such as the imaging date and time, the serial number of the camera that captured the image, various imaging conditions (shutter speed, aperture, ISO sensitivity, etc.), and information such as which of the three lights of light-emitting unit 15 was used.

[0019] The RAM 12 provides a working memory space for the CPU 11 and stores temporary data.

[0020] The storage unit 13 is a non-transitory recording medium readable by the CPU 11 as a computer, and is configured of a non-volatile storage device such as a flash memory. The storage unit 13 stores a program 131 executed by the CPU 11, various data, etc. The program 131 is stored in the storage unit 13 in the form of a computer-readable program code.

[0021] The imaging unit 14 includes an optical system that forms an image of incident light, an imaging element that detects the incident light formed by the optical system, and an image processing unit that generates image data based on a detection signal output from the imaging element. The optical system can be configured, for example, with a mirror and a lens group. The imaging element is not particularly limited as long as it is capable of photoelectrically converting the incident light, and may be, for example, a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor). The image processing unit amplifies and A / D converts the detection signal from the imaging element to generate image data of the captured subject. The image processing unit may also perform various image processing such as shading correction and color correction on the generated image data.

[0022] Light-emitting unit 15 emits light for illuminating a subject in the imaging direction of imaging unit 14. As described above, light-emitting unit 15 includes normal light 151, green light 152, and polarized light 153. The on / off state of light emission by light-emitting unit 15 is controlled by a control signal transmitted from CPU 11.

[0023] The display unit 16 includes a display device such as a liquid crystal display. In accordance with image data and control signals transmitted from the CPU 11, the display unit 16 displays captured images as live view images in real time on the display screen of the display device, plays back and displays captured images, and displays various operation icons.

[0024] Operation unit 17 has a touch panel superimposed on the display screen, and operation buttons provided on the housing of first camera 10. Operation unit 17 detects contact with a finger or the like on the touch panel and operation on the operation buttons, and outputs an operation signal to CPU 11 according to the detection result.

[0025] The communication unit 18 is composed of, for example, an antenna, a modulation / demodulation circuit, a signal processing circuit, etc. The communication unit 18 transmits and receives data to and from the medical image management device 40 or an access point of a wireless LAN, etc., in accordance with a predetermined communication standard.

[0026] FIG. 5 is a block diagram showing the main functional configuration of second camera 20. As shown in FIG. The second camera 20 includes a CPU 21, a RAM 22, a memory unit 23, an imaging unit 24, a light emitting unit 25, a display unit 26, an operation unit 27, a communication unit 28, etc., and each of these units is connected by a bus 29.

[0027] The CPU 21 is a processor that reads and executes the program 231 stored in the storage unit 23 and controls the operation of the second camera 20 by performing various arithmetic processing. The second camera 20 may have multiple processors (for example, multiple CPUs), and the multiple processors may execute the multiple processes executed by the CPU 21 of this embodiment. In this case, the multiple processors may be involved in a common process, or the multiple processors may independently execute different processes in parallel. When imaging a patient, the CPU 21 causes the light emitting unit 25 to emit light in response to settings or a user operation, and causes the imaging unit 24 to perform imaging in response to a user operation that instructs imaging, thereby generating image data of a medical image. The CPU 21 can also assign the patient ID of the imaged patient to the generated medical image as incidental information. The patient ID may be included in, for example, the EXIF ​​information of the medical image. For example, the patient ID is input by a doctor who is the operator of the second camera 20 using the operation unit 27 prior to imaging by the second camera 20.

[0028] The configurations of the RAM 22, memory unit 23, display unit 26, operation unit 27, and communication unit 28 are similar to the configurations of the RAM 12, memory unit 13, display unit 16, operation unit 17, and communication unit 18 of the first camera 10, so detailed explanations are omitted.

[0029] Similar to the imaging unit 14 of the first camera 10, the imaging unit 24 includes an optical system, an image sensor, an image processing unit, etc. However, as described above, the optical system of the imaging unit 24 is designed so that the angle of view is larger than the angle of view of the first camera 10 (so that the second imaging range R2 is larger than the first imaging range R1).

[0030] The light emitting unit 25 emits light for illuminating a subject in the imaging direction of the imaging unit 24. As described above, the light emitting unit 25 emits normal white light. The on / off state of the light emission by the light emitting unit 25 is controlled by a control signal transmitted from the CPU 21.

[0031] FIG. 6 is a block diagram showing the main functional configuration of the medical image management device 40. As shown in FIG. The medical image management device 40 includes a CPU 41, a RAM 42, a storage unit 43, a display unit 44, an operation unit 45, a communication unit 46, and the like, and these units are connected to each other via a bus 47.

[0032] The CPU 41 is a processor (processing unit, one or more processing units) that controls the operation of the medical image management device 40 by reading and executing a program 431 stored in the storage unit 43 and performing various arithmetic processing. The medical image management device 40 may have multiple processors (e.g., multiple CPUs), and the multiple processes performed by the CPU 41 of this embodiment may be executed by the multiple processors. In this case, one or more processing units are configured by the multiple processors. In this case, the multiple processors may be involved in a common process, or the multiple processors may independently execute different processes in parallel.

[0033] The RAM 42 provides a working memory space for the CPU 41 and stores temporary data.

[0034] The storage unit 43 is a non-transitory recording medium readable by the CPU 41 as a computer, and stores a program 431 executed by the CPU 41, various data, and the like. The storage unit 43 includes a non-volatile memory, such as a hard disk drive (HDD) or a solid state drive (SSD). The program 431 is stored in the storage unit 43 in the form of a computer-readable program code. The data stored in the storage unit 43 include image management data 432 for managing medical images received from the first camera 10, the second camera 20, and the third camera 30, and camera group management data 433 for managing the camera group, which will be described later.

[0035] The display unit 44 includes a display device such as a liquid crystal display. The display unit 44 displays a medical image management screen, a screen related to various statuses of the medical image management system 1, and the like on the display screen of the display device in accordance with the image data and control signals transmitted from the CPU 41.

[0036] The operation unit 45 has a keyboard, a mouse, a touch panel superimposed on a display screen, etc. The operation unit 45 detects operations on the keyboard, the mouse, the touch panel, etc., and outputs an operation signal according to the detection result to the CPU 41.

[0037] The communication unit 46 is configured, for example, by a network card or a communication module, and transmits and receives data between the first camera 10, the second camera 20, and the third camera 30, or an external device such as a wireless LAN access point, in accordance with a predetermined communication standard.

[0038] <Operation of medical image management system> Next, the operation of the medical image management system 1 will be described. Here, it is assumed that a doctor who is an operator of the medical image management system 1 takes an image of the inner genitalia using the first camera 10 and an image of the outer genitalia using the second camera 20 during an examination of a certain patient.

[0039] In the medical image management system 1 of this embodiment, a camera group (imaging device group) consisting of multiple cameras used to image the same patient can be set before imaging the patient. In addition, a patient ID, which is a unique code assigned to each patient, can be registered in association with the camera group. By registering the patient ID in association with the camera group, multiple medical images (multiple images) captured by one or more cameras belonging to the camera group can be automatically associated and managed by the patient ID. In other words, even if the patient ID is not input in some cameras, medical images captured by all cameras belonging to the camera group can be automatically associated as medical images captured by the same patient ID.

[0040] The camera group can be set on a camera group setting screen 441 displayed on the display unit 44 of the medical image management device 40 . FIG. 7 is a diagram showing the camera group setting screen 441. As shown in FIG. The camera group setting screen 441 displays a list of serial numbers and IP addresses of the first camera 10, the second camera 20, and the third camera 30 provided in the medical image management system 1. In addition, the camera group setting screen 441 is provided with a drop-down list 4411 for each camera to select the camera group to which each camera belongs. In FIG. 7, the drop-down list 4411 is selected so that the first camera 10 and the second camera 20 belong to the camera group GA, and the third camera 30 belongs to the camera group GB. Selecting the same camera group for multiple cameras using the drop-down list 4411 corresponds to a "user operation for selecting multiple cameras that constitute a camera group." When the decision button 4412 is selected, the configuration of the camera group is set with the contents reflecting the selection state using the drop-down list 4411 at that time, and is registered in the camera group management data 433. Instead of the drop-down list 4411, check boxes for selecting the cameras that make up the camera group may be displayed. In the following, the operation of the medical image management system 1 will be described using the camera group GA constituted by the first camera 10 and the second camera 20 as an example.

[0041] After the camera group GA is set, when a patient ID is input into one of the first camera 10 and the second camera 20 belonging to the camera group GA, the patient ID is transmitted from the one camera to the medical image management device 40 and registered in association with the camera group GA.

[0042] FIG. 8 is a diagram showing a patient ID input screen 161 for inputting a patient ID. The patient ID input screen 161 is displayed on the display unit 16 in response to a predetermined operation performed on the operation unit 17 of the first camera 10. The patient ID input screen 161 displays numeric keys 1611 for inputting the patient ID, a text box 1612 in which the inputted patient ID is displayed, and a decision button 1613. In the example shown in FIG. 8, the patient ID "18901" is inputted into the text box 1612 in response to the operation of the numeric keys 1611. When the decision button 1613 is selected with the patient ID inputted into the text box 1612, the CPU 11 of the first camera 10 stores the patient ID in the storage unit 13. The CPU 11 also transmits the patient ID to the medical image management device 40 via the communication unit 18. The patient ID can also be input into the second camera 20 using a similar patient ID input screen and transmitted to the medical image management device 40. However, if the patient ID is input into either the first camera 10 or the second camera 20, the patient ID is associated with the camera group GA, and so there is no need to input the patient ID into the other camera. In the following, an example will be described in which the patient ID "18901" is input into only the first camera 10.

[0043] When the CPU 41 of the medical image management device 40 receives the patient ID from the first camera 10, the CPU 41 registers the received patient ID in the camera group management data 433 in association with the camera group GA to which the first camera 10 belongs. FIG. 9 is a diagram showing the camera group management data 433 in a state where a patient ID is associated with the camera group management data 433. In the example shown in FIG. 9, a camera group GA consisting of the first camera 10 and the second camera 20 is associated with a patient ID "18901" and registered.

[0044] After the patient ID is registered in the camera group GA, when the doctor, who is the operator, captures images of the patient using the first camera 10 and the second camera 20, medical images are generated by each camera and transmitted to the medical image management device 40.

[0045] FIG. 10 is a diagram showing the operation of transmitting a medical image Im from the first camera 10 and the second camera 20. As shown in FIG. Here, it is assumed that the first camera 10 generates first medical images Im101-Im103 (first images) by the above-mentioned imaging, and the second camera 20 generates second medical images Im201 and Im202 (second images) by the above-mentioned imaging. In the following, any one medical image captured by the first camera 10 will be referred to as "first medical image Im1", and any one medical image captured by the second camera 20 will be referred to as "second medical image Im2". In addition, any one medical image captured by the first camera 10 or the second camera 20 will be referred to as "medical image Im".

[0046] The first medical image Im101 captured by the first camera 10 is captured using normal light 151, the first medical image Im102 is captured using green light 152, and the first medical image Im103 is captured using polarized light 153. In addition, the EXIF ​​data of the first medical images Im101 to Im103 captured by the first camera 10 includes the patient ID "18901" input to the first camera 10. On the other hand, the EXIF ​​information of the second medical images Im201 and Im202 captured by the second camera 20 does not include a patient ID. This is because the patient ID is not input to the second camera 20. When the first camera 10 and the second camera 20 capture images, the generated medical images Im are transmitted one by one to the medical image management device 40. After multiple medical images Im are captured by each camera, the multiple medical images Im may be transmitted collectively from each camera.

[0047] The CPU 41 of the medical image management device 40 registers the received medical image Im in the image management data 432 . FIG. 11 is a diagram showing the contents of the image management data 432. As shown in FIG. One data row of the image management data 432 corresponds to one medical image Im. The "imaging date and time" in each data row is information on the imaging date and time extracted from the EXIF ​​information of the medical image Im. "Camera" is information about the imaging device (the first camera 10 or the second camera 20) used to capture the medical image Im, extracted from the EXIF ​​information of the medical image Im. "Light" is information about the light used in capturing an image, extracted from the EXIF ​​information of the medical image Im.

[0048] The "patient ID" is the patient ID of the patient who is the subject of the medical image Im. The patient ID is identified by the following method and registered in association with each medical image Im. When the CPU 41 receives the medical image Im, the CPU 41 refers to the camera group management data 433 shown in FIG. 9 to identify the patient ID (here, "18901") associated with the camera group GA to which the first camera 10 or the second camera 20 that transmitted the medical image Im belongs. Then, the CPU 41 registers the identified patient ID in the image management data 432 in association with the received medical image Im. As a result, as shown in FIG. 11, the first medical images Im101 to Im103 received from the first camera 10 and the second medical images Im201 and Im202 received from the second camera 20 are all registered in association with the patient ID "18901". In this way, even if the patient ID is not input in the second camera 20, the patient ID registered in association with the camera group GA is automatically registered in association with the medical image Im captured by the second camera 20. This allows the medical images Im received from the first camera 10 and the second camera 20 to be managed in association with each other using the patient ID of the same patient. In addition, for the first medical images Im101 to Im103 received from the first camera 10, the patient ID "18901" contained in the EXIF ​​information of these medical images Im may be associated with each of the first medical images Im101 to Im103 and registered in the image management data 432.

[0049] When receiving a medical image Im captured before the camera group GA was registered from the first camera 10 and / or the second camera 20, the CPU 41 does not associate a patient ID with the medical image Im. That is, the CPU 41 associates a patient ID using the settings of the camera group described above only when the capture time included in the EXIF ​​information of the received medical image Im is later than the time when the camera group GA was registered. In addition, in the above, an example was described in which medical images Im were transmitted from all of the cameras belonging to the camera group GA, i.e., the first camera 10 and the second camera 20, but this is not limited to the above, and medical images Im may be transmitted from only some of the cameras belonging to the camera group GA. The contents of the image management data 432 shown in FIG.

[0050] When switching the patient to be imaged, for example, the patient ID of the new patient may be input in one of the first camera 10 and the second camera 20. Usually, the doctor who is the operator turns off the power of each camera when imaging of a certain patient is completed, so if the patient ID input screen 161 shown in Fig. 8 is displayed when the camera is turned on to image the next patient, the effort required for switching patients can be reduced.

[0051] The patient ID input at the time of switching patients is transmitted to the medical image management device 40. If the latest patient ID received is different from the patient ID already registered for the camera group GA, the CPU 41 of the medical image management device 40 overwrites and registers (updates) the latest patient ID in the camera group management data 433 in association with the camera group GA. When the CPU 41 receives a plurality of medical images Im captured by the first camera 10 and the second camera 20 after the registration of the latest patient ID, it associates the plurality of medical images Im with the latest patient ID. In this way, by inputting the post-switching patient ID to one camera belonging to the camera group GA, it is possible to switch the patient ID associated with the medical images Im captured by each camera of the camera group GA (i.e., it is possible to switch patients).

[0052] Next, a camera group setting process and a medical image registration process executed by the CPU 41 of the medical image management device 40 to realize the operation of the above-mentioned medical image management system 1 will be described.

[0053] FIG. 12 is a flowchart showing a control procedure of the camera group setting process. The camera group setting process is started when an operation for displaying the camera group setting screen 441 is performed on the medical image management device 40. When the camera group setting process is started, the CPU 41 of the medical image management device 40 causes the display unit 44 to display the camera group setting screen 441 of FIG. 7 (step S101). The CPU 41 repeatedly determines whether or not the decision button 4412 is selected when the cameras constituting the camera group are selected (step S102). If the CPU 41 determines that the operation has been performed ("YES" in step S102), the CPU 41 sets a camera group consisting of the selected cameras and registers it in the camera group management data 433 (step S103). When step S103 ends, the CPU 41 ends the camera group setting process.

[0054] FIG. 13 is a flowchart showing a control procedure of the medical image registration process. The medical image registration process is started when the camera group setting process is completed. The medical image registration process is executed for each camera group that is set. The medical image registration process corresponding to the camera group GA is exemplified below. When the medical image registration process is started, the CPU 41 determines whether or not a patient ID has been received from any of the cameras belonging to the camera group GA (step S201). If it is determined that a patient ID has not been received ("NO" in step S201), the CPU 41 determines whether or not a patient ID has already been associated with the camera group GA and registered in the camera group management data 433 (step S202). If it is determined that a patient ID has not been registered in the camera group GA ("NO" in step S202), the CPU 41 returns the process to step S201.

[0055] When it is determined that the patient ID has been received from any of the cameras ("YES" in step S201), the CPU 41 determines whether or not the patient ID has already been registered in association with the camera group GA in the camera group management data 433 (step S203). When it is determined that the patient ID has not been registered in the camera group GA ("NO" in step S203), the CPU 41 registers the received patient ID in association with the camera group GA in the camera group management data 433 (step S204). When it is determined that the patient ID has already been registered in the camera group GA in step S203 ("YES" in step S203), the CPU 41 determines whether or not the received patient ID is different from the registered patient ID (step S205). When it is determined that the received patient ID is different from the registered patient ID ("YES" in step S205), the CPU 41 advances the process to step S204, and overwrites and registers the received patient ID in association with the camera group GA in the camera group management data 433. Of the above, the flow proceeding in the order of steps S201, S203, and S204 corresponds to the process of initially registering a patient ID in association with the camera group GA after the camera group GA is set. Moreover, the flow proceeding in this order from step S201 to step S203, S205, and S204 corresponds to the processing when switching the patient (patient ID).

[0056] When step S204 is completed, the CPU 41 executes step S206. Also, when it is determined in step S202 that the patient ID has already been registered in the camera group GA ("YES" in step S202), or when it is determined in step S205 that the received patient ID is the same as the registered patient ID ("NO" in step S205), the CPU 41 executes step S206. In step S206, the CPU 41 determines whether or not the medical image Im has been received from any of the cameras belonging to the camera group GA. When it is determined that the medical image Im has not been received ("NO" in step S206), the CPU 41 returns the process to step S201. When it is determined that the medical image Im has been received ("YES" in step S206), the CPU 41 registers the received medical image Im in the image management data 432. Furthermore, the CPU 41 registers the patient ID corresponding to the camera group GA in association with the received medical image Im in the image management data 432 (step S207).

[0057] The CPU 41 determines whether or not the imaging by the camera group GA has ended (step S208). For example, the CPU 41 determines that the imaging has ended when the power of each camera belonging to the camera group GA has been turned off. If the CPU 41 determines that the imaging has not ended ("NO" in step S208), the process returns to step S201, and if the CPU 41 determines that the imaging has ended ("NO" in step S208), the medical image registration process ends.

[0058] <Modification> Next, a modified example of the first embodiment will be described. Below, differences from the first embodiment will be described, and a description of commonalities with the first embodiment will be omitted. In the above first embodiment, the patient ID associated with the medical image Im was switched by inputting the patient ID into the first camera 10 or the second camera 20. However, in this modified example, the patient ID can be switched by photographing an identification mark 50 that can identify the patient ID (or the patient) with the first camera 10 or the second camera 20.

[0059] FIG. 14 is a diagram showing a transmission operation of a medical image Im according to a modified example. After completing imaging of a certain patient, the doctor, who is the operator, images a predetermined identification marker 50 capable of identifying the patient ID of the next patient using the first camera 10 or the second camera 20 before imaging of the next patient. The identification marker 50 may be an image that can obtain the patient ID by decoding, such as a barcode or a two-dimensional code. The identification marker 50 may also be a code (a figure, a symbol, a character, or a combination thereof, etc.) that is associated one-to-one with the patient ID in a predetermined table data. The identification marker 50 may also be the patient ID itself. In the example shown in FIG. 14, it is assumed that after a medical image Im109 obtained by imaging a certain patient is generated by the first camera 10, an identification marker image ImX obtained by imaging the identification marker 50 is generated, and then first medical images Im111, Im112, and second medical images Im211, 212 obtained by imaging the next patient are generated. The series of medical images Im and identification marker images ImX are transmitted to the medical image management device 40 and registered in the image management data 432. The identification marker images ImX are used in the medical image registration process to register the patient ID for the camera group GA and to switch patients.

[0060] FIG. 15 is a flowchart showing a control procedure of medical image registration processing according to the modified example. The flowchart in Fig. 15 is obtained by adding steps S209 and S210 to the flowchart in Fig. 13. In the following, a description of the processes common to the flowchart in Fig. 13 will be omitted. When the CPU 41 of the medical image management device 40 determines that the patient ID has not been received from a camera belonging to the camera group GA (step S201: NO), the CPU 41 determines whether or not the identification marker image ImX has been received from any of the cameras (step S209). For example, the CPU 41 performs a known image recognition process for extracting the identification marker 50 on the image data of the received image, and determines that the identification marker image ImX has been received when the identification marker 50 is extracted. When the CPU 41 determines that the identification marker image ImX has not been received (step S209: NO), the CPU 41 shifts the process to step S202. When the CPU 41 determines that the identification marker image ImX has been received (step S209: YES), the CPU 41 identifies the patient ID from the extracted identification marker 50 (step S210). For example, when the identification marker 50 is a barcode or a two-dimensional code, the CPU 41 identifies the patient ID corresponding to the identification marker 50 by performing a known decoding process or the like on the identification marker 50. Furthermore, when the identification marker 50 is the above-mentioned code, the CPU 41 refers to the predetermined table data to identify the patient ID corresponding to the identification marker 50. When step S210 ends, the CPU 41 shifts the process to step S203. The subsequent process is the same as that in FIG.

[0061] According to the medical image registration process of this modified example, when an identification sign image ImX is received ("YES" in step S209) and a patient ID is not associated and registered with the camera group GA ("NO" in step S203), the patient ID identified from the identification sign 50 of the identification sign image ImX is associated and registered with the camera group GA (step S204). The flow proceeding in this order of steps S209, S210, S203, and S204 corresponds to the process of initially associating and registering a patient ID after setting the camera group GA. Furthermore, if a patient ID has already been registered in the camera group GA ("YES" in step S203) and the patient ID (received patient ID) identified from the identification label 50 of the identification label image ImX is different from the registered patient ID ("YES" in step S205), the patient ID identified from the identification label 50 is associated with the camera group GA and overwritten and registered (step S204). The flow proceeding in this order of steps S209, S210, S203, S205, and S204 corresponds to the processing when switching patients (patient IDs). In this modification, step S201 of receiving the patient ID from the first camera 10 or the second camera 20 may be omitted. In other words, only the patient ID identified from the identification mark 50 of the identification mark image ImX may be used for managing the medical image Im.

[0062] FIG. 16 is a diagram showing the contents of image management data 432 according to a modified example. By executing the medical image registration process shown in FIG. 15, the image management data 432 in FIG. 16 is generated. In the image management data 432 of this modification, a data item of "identification label" is provided, and when the image includes the identification label 50 (when the image is an identification label image ImX), the "identification label" is set to "present". When the patient ID (here, "18753") identified from the identification label 50 of this identification label image ImX is overwritten and registered in association with the camera group GA in the camera group management data 433, the patient ID is associated with the first medical images Im111, Im112 and the second medical images Im211, Im212 captured thereafter and registered. In this way, when a patient is switched, a plurality of medical images Im can be managed in association with the patient ID of the switched patient.

[0063] <Effects> As described above, the program 431 according to the first embodiment causes the CPU 41 of the medical image management device 40 to execute the following processes in response to a user's operation of selecting a plurality of cameras (the first camera 10 and the second camera 20): setting a camera group GA consisting of the plurality of cameras; registering a patient ID capable of identifying a patient in association with the camera group GA; acquiring a plurality of medical images Im captured by the cameras belonging to the camera group GA; and associating the acquired plurality of medical images Im by the patient ID. As a result, even when capturing images by switching between a plurality of cameras, the medical images Im captured by each camera can be appropriately associated as medical images Im of the same patient. Therefore, it is possible to easily manage the medical images Im when a plurality of cameras are used. This reduces the operator's workload and shortens the examination time.

[0064] Furthermore, the program 431 causes the CPU 41 to execute a process of acquiring a patient ID from a certain camera belonging to the camera group GA when the patient ID is input by a user to the certain camera and registering the patient ID in association with the camera group GA. This allows medical images Im captured by each camera belonging to the camera group GA to be associated with the same patient ID by a simple operation of inputting a patient ID into one of the cameras. This reduces the operator's efforts compared to the conventional method in which a patient ID had to be input into each camera used. In addition, it is possible to prevent the occurrence of a problem in which association of medical images Im is inappropriate due to forgetting to input a patient ID or an input mistake.

[0065] Furthermore, the program 431 causes the CPU 41 to execute, when the latest patient ID acquired from an arbitrary camera belonging to the camera group GA is different from the patient ID already registered in association with the camera group GA, a process of overwriting and registering the latest patient ID in association with the camera group GA, a process of acquiring multiple medical images Im captured by a camera belonging to the camera group GA after the latest patient ID was registered, and a process of associating the acquired multiple medical images Im with the latest patient ID. This makes it possible to switch the patient ID used for associating the medical images Im (switch patients) with a simple operation of inputting the patient ID into any one of the multiple cameras.

[0066] In a modified example, when an identification sign image ImX capturing an identification sign 50 capable of identifying a patient ID is acquired from a camera belonging to the camera group GA, the program 431 causes the CPU 41 to execute a process of identifying the patient ID based on the identification sign 50 and registering the patient ID in association with the camera group GA. According to this method, there is no need to manually input the patient ID, which further reduces the burden on the operator.

[0067] In addition, in a modified example, the program 431 causes the CPU 41 to execute, when the latest patient ID identified from the acquired identification sign image ImX is different from the patient ID already registered in association with the camera group GA, a process of overwriting and registering the latest patient ID in association with the camera group GA, a process of acquiring multiple medical images Im captured after capturing the identification sign image ImX by a camera belonging to the camera group GA, and a process of associating the acquired multiple medical images Im with the latest patient ID. This makes it possible to switch the patient ID used for associating the medical images Im (switch patients) by a simple operation of capturing an identification sign 50 with any one of the multiple cameras.

[0068] The medical image management system 1 also includes a first camera 10 having a first imaging range R1 and capturing a first medical image Im1 related to a first part of a patient, and a second camera 20 having a second imaging range R2 different from the first imaging range R1 and capturing a second medical image Im2 related to a second part different from the first part of the patient. The program 431 also causes the CPU 41 to execute a process of acquiring at least one first medical image Im1 and at least one second medical image Im2 captured by the first camera 10 and the second camera 20 belonging to the camera group GA, and a process of associating the acquired at least one first medical image Im1 and at least one second medical image Im2 by a patient ID. This allows the medical images Im captured by each camera to be appropriately associated as medical images Im of the same patient when it is necessary to switch the imaging device to be used between the first camera 10 and the second camera 20 depending on the part to be imaged.

[0069] Moreover, the medical image management device 40 according to the first embodiment includes a CPU 41, which, in response to a user's operation of selecting multiple cameras for capturing medical images Im, sets a camera group GA consisting of the multiple cameras, registers a patient ID capable of identifying a patient in association with the camera group GA, acquires multiple medical images Im captured by the cameras belonging to the camera group GA, and associates the acquired multiple medical images Im with the patient ID. This makes it possible to easily manage medical images Im when multiple cameras are used.

[0070] Moreover, the image management method according to the second embodiment sets a camera group GA consisting of multiple cameras in response to a user's operation to select the multiple cameras for capturing medical images Im, registers a patient ID capable of identifying a patient in association with the camera group GA, acquires multiple medical images Im captured by the cameras belonging to the camera group GA, and associates the acquired multiple medical images Im with the patient ID. This makes it possible to easily manage medical images Im when multiple cameras are used.

[0071] Second Embodiment Next, a second embodiment will be described. Below, differences from the first embodiment will be described, and descriptions of commonalities with the first embodiment will be omitted.

[0072] In the above first embodiment, the patient ID is input in the first camera 10 or the second camera 20, but in the second embodiment, the patient ID is input by a user operation in the medical image management device 40. In this embodiment, for example, when the decision button 4412 is selected in the camera group setting screen 441 shown in Fig. 7 to set the camera group, a patient ID input screen 442 for inputting a patient ID to be registered in association with the camera group is displayed on the display unit 44.

[0073] FIG. 17 is a diagram showing the patient ID input screen 442. Displayed on the patient ID input screen 442 are a drop-down list 4421 for selecting a camera group for which the patient ID is to be registered, a text box 4422 for inputting the patient ID, and an OK button 4423. When a camera group is selected using the drop-down list 4421 and the patient ID is input in the text box 4422, the input patient ID is registered in the camera group management data 433 in association with the selected camera group, as shown in FIG.

[0074] FIG. 18 is a flowchart showing a control procedure of medical image registration processing according to the second embodiment. When the medical image registration process is started, the CPU 41 repeatedly determines whether or not an operation to input a patient ID has been performed on the patient ID input screen 442 (step S301). If it is determined that the operation has been performed ("YES" in step S301), the CPU 41 registers the input patient ID in the camera group management data 433 in association with the selected camera group GA (step S302). The CPU 41 determines whether or not a medical image Im has been received from any camera belonging to the camera group GA (step S303). If it is determined that a medical image Im has been received ("YES" in step S303), the CPU 41 registers the received medical image Im in the image management data 432. Furthermore, the CPU 41 registers the patient ID corresponding to the camera group GA in association with the received medical image Im in the image management data 432 (step S304). When step S304 is completed, or when it is determined that the medical image Im has not been received ("NO" in step S303), the CPU 41 determines whether or not the image capturing by the camera group GA has been completed (step S305). When it is determined that the image capturing has not been completed ("NO" in step S305), the CPU 41 returns the process to step S303, and when it is determined that the image capturing has been completed ("NO" in step S305), the CPU 41 ends the medical image registration process.

[0075] <Effects> As described above, the program 431 according to the second embodiment causes the CPU 41 of the medical image management device 40 to execute a process of registering a patient ID in association with the camera group GA when the patient ID is input by the user in the medical image management device 40. This allows the medical images Im captured by each camera belonging to the camera group GA to be associated with the same patient ID by a simple operation of inputting the patient ID into the medical image management device 40. This reduces the operator's efforts compared to the conventional method in which the patient ID had to be input into each camera used. In addition, it is possible to prevent the occurrence of a problem in which the association of medical images Im is inappropriate due to forgetting to input the patient ID or an input error.

[0076] (others) The present invention is not limited to the above-described embodiment, but may be modified in various ways. For example, in the above embodiment, the medical image management system 1 is described as being applied to imaging of the internal and external genitalia in obstetrics and gynecology, but is not limited thereto. The medical image management system 1 can be used for any purpose in which multiple medical images Im are captured by multiple imaging devices. For example, when an image of the inside of a patient's mouth (the inside of the teeth and the throat) is captured by a first imaging device, and an image of the surface of the patient's teeth and part of the face is captured by a second imaging camera, the first medical image captured by the first imaging device and the second medical image captured by the second imaging device may be associated using the method of the above embodiment.

[0077] In addition, the imaging ranges of the multiple imaging devices are not limited to those different from each other. For example, in a case where one of two imaging devices having the same specifications is used as a main imaging device and the other is used as a sub imaging device, and the main imaging device and the sub imaging device are used by switching between them as necessary, the medical images captured by these two imaging devices may be associated with each other by the method of the above embodiment.

[0078] Furthermore, the processing executed by CPU 41 of medical image management device 40 in the above embodiment may be executed by CPU 11 of first camera 10 (or CPU 21 of second camera 20). In this case, first camera 10 (or second camera 20) corresponds to the "medical information management device", and CPU 11 (or CPU 21) corresponds to the "processing unit".

[0079] Furthermore, in the above embodiment, the medical image Im is exemplified as an image to be managed, but the image to be managed is not limited to this, and may be any image other than the medical image Im.

[0080] In the above description, an example has been disclosed in which the HDD or SSD of the storage unit 43 is used as a computer-readable medium for the program according to the present invention, but the present invention is not limited to this example. As other computer-readable media, information recording media such as flash memory and CD-ROM can be applied. In addition, a carrier wave is also applied to the present invention as a medium for providing data of the program according to the present invention via a communication line.

[0081] Furthermore, the detailed configuration and detailed operation of each component of the medical image management system 1 in the above embodiment can of course be modified as appropriate without departing from the spirit of the present invention.

[0082] Although the embodiments of the present invention have been described, the scope of the present invention is not limited to the above-described embodiments, but includes the scope of the invention described in the claims and its equivalents. [Explanation of symbols]

[0083] 1 Medical image management system 10 First camera (first imaging device) 20 Second camera (second imaging device) 30 Third Camera 40 Medical image management device (image management device) 41 CPU (processing unit) 431 Programs 50 Identification signs GA, GB camera group Im Medical Imaging (Images) Im1, Im101~Im103, Im111, Im112 First medical image (first image) Im2, Im201, Im202, Im211, Im212 Second medical image (second image) ImX identification sign image R1 First imaging range R2 Second imaging range

Claims

1. On the computer, A process of setting an imaging device group consisting of a plurality of imaging devices in response to a user's operation of selecting the plurality of imaging devices; a process of registering identification information capable of identifying a subject in association with the group of image capture devices; A process of acquiring a plurality of images captured by an imaging device belonging to the imaging device group; A process of associating the acquired multiple images with the identification information; A program that executes the following.

2. The computer includes: a process of acquiring, when a user inputs the identification information into an imaging device belonging to the imaging device group, the identification information from the imaging device and registering the identification information in association with the imaging device group; The program according to claim 1 .

3. The computer includes: When the latest identification information acquired from an arbitrary image capture device belonging to the image capture device group is different from the identification information already registered in association with the image capture device group, a process of overwriting and registering the latest identification information in association with the group of imaging devices; A process of acquiring a plurality of images captured by an imaging device belonging to the imaging device group after registration of the latest identification information; A process of associating the acquired plurality of images with the latest identification information; The program according to claim 2 .

4. The computer includes: a process of, when acquiring an identification sign image capturing an identification sign capable of locating the identification information from an imaging device belonging to the imaging device group, identifying the identification information based on the identification sign and registering the identification information in association with the imaging device group; The program according to claim 1 .

5. The computer includes: When the latest identification information identified from the acquired identification sign image is different from the identification information registered in association with the imaging device group, a process of overwriting and registering the latest identification information in association with the group of imaging devices; A process of acquiring a plurality of images captured by an imaging device belonging to the imaging device group after capturing the identification sign image; A process of associating the acquired plurality of images with the latest identification information; The program according to claim 4, which causes the program to execute the following:

6. The computer includes: a process of registering the identification information in association with the group of imaging devices when the identification information is input by a user; The program according to claim 1 .

7. the plurality of imaging devices include a first imaging device having a first imaging range and capturing a first image related to a first portion of a subject, and a second imaging device having a second imaging range different from the first imaging range and capturing a second image related to a second portion of the subject different from the first portion; The program causes the computer to A process of acquiring at least one of the first image and at least one of the second image captured by the first imaging device and the second imaging device belonging to the imaging device group; associating the acquired at least one first image and the acquired at least one second image by the identification information; The program according to claim 1 .

8. setting an imaging device group consisting of the plurality of imaging devices in response to a user operation of selecting the plurality of imaging devices; registering identification information capable of identifying a subject in association with the group of image capture devices; acquiring a plurality of images captured by imaging devices belonging to the imaging device group; Associating the acquired images with each other using the identification information; An image management device comprising a processing unit.

9. 1. A computer-implemented image management method, comprising: setting an imaging device group consisting of the plurality of imaging devices in response to a user operation of selecting the plurality of imaging devices; registering identification information capable of identifying a subject in association with the group of image capture devices; acquiring a plurality of images captured by imaging devices belonging to the imaging device group; Associating the acquired images with each other using the identification information; Image management methods.

Images