Medical system and method for controlling the same, and program

Abstract

To provide a device that links an affected part image picked up by a medical worker and patient information of a patient to each other.SOLUTION: A medical system has an electronic medical chart terminal, and an imaging apparatus having imaging means. The medical system has: photographer specification means that specifies a photographer of the imaging apparatus; acquisition means that acquires patient information related to a patient whose medical chart information is displayed in the electronic medical chart terminal being operated by the photographer specified by the photographer specification means; and means that associates an affected part image obtained by the imaging means through imaging and the patient information acquired by the acquisition means with each other.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to a medical system, a control method thereof, and a program thereof. [Background technology]

[0002] In the medical field, a patient's affected area is photographed with a digital camera, and the image of the affected area is kept as a treatment record or medical record. In order to keep the image of the affected area as a treatment record or medical record, the photographer needs to link the patient information such as the patient's name and sex written in the electronic medical record to the image of the affected area. Specifically, the photographer logs into an electronic medical record terminal, displays the medical record information of the patient to be photographed, and photographs the affected area after confirming the identity of the photographer. Then, the photographer links the patient information displayed on the electronic medical record terminal to the image of the affected area. For example, Patent Document 1 discloses a method for authenticating an operator of an X-ray diagnostic device and permitting the operation. [Prior art documents] [Patent documents]

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

[0004] However, the conventional techniques disclosed in the above-mentioned patent documents can authenticate and identify the operator of an X-ray diagnostic apparatus, which is an imaging apparatus, but cannot acquire patient information and link it to an image of the affected area.

[0005] SUMMARY OF THE PRESENT EMBODIMENT An object of the present invention is to provide a device that links an image of an affected area captured by a medical professional with patient information of the patient. [Means for solving the problem]

[0006] One aspect of the present invention is a medical system having an electronic medical record terminal and an imaging device having an imaging means, a photographer identification means for identifying a photographer of the imaging device; an acquiring means for acquiring patient information related to a patient whose medical record information is displayed on the electronic medical record terminal being operated by the photographer identified by the photographer identifying means; and a means for associating an image of the affected area obtained by the imaging means with the patient information obtained by the acquisition means. The medical system is characterized by the above. Effect of the Invention

[0007] According to the present invention, it is possible to provide a device that links an image of an affected area of ​​a patient captured by a medical professional with the patient information of the patient. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a system configuration diagram of an imaging system. [Diagram 2] FIG. 1 is a block diagram of an imaging apparatus. [Diagram 3] FIG. 1 is a block diagram of an information processing device. [Figure 4] FIG. 2 is a diagram showing the imaging device as viewed from behind. [Figure 5A] 3 shows a display screen of the imaging device according to the first embodiment. [Figure 5B] 3 shows a display screen of the imaging device according to the first embodiment. [Figure 5C] 3 shows a display screen of the imaging device according to the first embodiment. [Figure 6A] 3 shows a patient information table of the electronic medical record management device in the first embodiment. [Figure 6B] 3 shows a medical staff information table of the electronic medical record management device in the first embodiment. [Figure 6C] 3 shows a patient examination information table of the electronic medical record management device in the first embodiment. [Figure 7] FIG. 2 is a process sequence diagram of the imaging system according to the first embodiment. [Figure 8A] 4 is a flowchart of the imaging apparatus according to the first embodiment. [Figure 8B] 5 is a flowchart of the imaging device management apparatus according to the first embodiment. [Figure 8C] 4 is a flowchart of the electronic medical record terminal device according to the first embodiment. [Figure 8D] 4 is a flowchart of the electronic medical record management device according to the first embodiment. [Figure 9A] 1 shows an example of operation of the first embodiment. [Figure 9B] 1 shows an example of operation of the first embodiment. [Figure 9C] 1 shows an example of operation of the first embodiment. [Figure 9D] 1 shows an example of operation of the first embodiment. [Figure 10A] FIG. 11 is a block diagram of an imaging apparatus according to a second embodiment. [Figure 10B] 13 shows a display screen of an imaging device according to the second embodiment. [Figure 11] FIG. 11 is a process sequence diagram when capturing an image of a patient ID barcode in the imaging system according to the second embodiment. [Figure 12] 10 is a flowchart of an imaging apparatus according to a second embodiment. [Figure 13] FIG. 11 is a process sequence diagram of an imaging system according to a third embodiment. [Figure 14] 10 is a flowchart of an imaging apparatus according to a third embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, the embodiments will be described in detail with reference to the attached drawings. Note that the following embodiments do not limit the invention according to the claims. Although the embodiments describe a number of features, not all of these features are essential to the invention, and the features may be combined in any manner. Furthermore, in the attached drawings, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.

[0010] (First embodiment) First, an overview of the imaging system of the embodiment will be described. The imaging system of the embodiment is a medical imaging system. The imaging system has an imaging device and an imaging device control device as components. When a medical professional authenticates with the imaging device, the imaging device, which also functions as a photographer identification unit, identifies the authenticated medical professional as the photographer, and obtains patient information of the patient to be photographed by the medical professional from an electronic medical record management device and sets it in the imaging device. After that, when the medical professional photographs the affected part of the patient using the imaging device, the image of the affected part is linked to the patient information and stored in the imaging device. When the medical professional completes photographing the affected part, the imaging device transmits the image of the affected part linked to the patient information to the imaging device control device. Furthermore, the imaging device control device transmits the received image of the affected part to the image management device.

[0011] Moreover, the imaging system of the embodiment has an electronic medical record terminal device, an electronic medical record management device, and an image management device as its constituent devices. When a medical professional logs in to the electronic medical record terminal using login information or the like, the patient's medical record information (patient information and patient examination information) stored in the electronic medical record management device can be displayed on the electronic medical record terminal. Furthermore, the electronic medical record management device can read the affected area image stored in the image management device, and when a display of the affected area image is requested from the electronic medical record terminal, the affected area image is displayed on the electronic medical record terminal device. That is, in the imaging system of the embodiment, the affected area image captured by the imaging device is stored in the image management device. Then, the medical professional uses the affected area image stored in the image management device by displaying it on the display of the electronic medical record terminal device to examine the patient.

[0012] 1 is a system configuration diagram of an imaging system according to an embodiment. The imaging system is an example of a medical system. The imaging device control device 102, the electronic medical record management device 104, and the image management device 105 are examples of a management system. The imaging device 101 and the electronic medical record terminal device 103 are examples of a terminal system.

[0013] The imaging device 101 is a device that captures an image of a subject and generates image data. The imaging device 101 is a small, portable imaging device, similar to a commercially available digital camera, and is provided with an interface, such as a display device that allows the captured image to be checked and buttons and a touch panel for various operations. In this embodiment, the imaging device 101 is a digital camera, and the imaging device 101 is used by a medical professional, such as a doctor or a nurse, to capture an image of an affected area of ​​a patient and generate an image of the affected area. The imaging device 101 transmits a set of an image of the affected area and patient information, which is information about the patient.

[0014] The imaging device control device 102 is an information processing device such as a computer, and acts as an intermediary between the imaging device 101, the electronic medical record management device 104, and the image management device 105. The imaging device control device 102 functions as a part of a patient information transmission unit, acquiring medical staff information and patient information from the electronic medical record management device 104 and transmitting the information to the imaging device 101, and transmitting images of the affected area to the image management device 105.

[0015] The electronic medical record terminal device 103 is, for example, an information processing device, and operates as an electronic medical record display device when a medical professional logs in. The electronic medical record terminal device 103 can download patient information from the electronic medical record management device 104 and display it as an electronic medical record, and can upload information updated in the electronic medical record terminal device 103 to the electronic medical record management device 104. In this embodiment, a medical professional such as a doctor or nurse operates the electronic medical record terminal device 103 to display a captured image of the affected area of ​​the patient, and enter the examination results such as the medical condition in the electronic medical record.

[0016] The electronic medical record management device 104 is, for example, an information processing device that stores patient information (patient ID, name, age, sex), patient examination information (patient ID, medical department, medical condition, medical history, etc.), and medical professional information (authentication information such as medical professional ID, name, and password). The patient ID is an example of patient identification information. The medical professional ID is also called medical professional identification information. The electronic medical record management device 104 also authenticates authentication requests for medical professionals from the imaging device control device 102 and the electronic medical record terminal device 103, and provides information in response to requests to obtain patient information and medical professional information. Furthermore, the electronic medical record management device 104 receives information updated by the electronic medical record terminal device 103, and updates and stores the patient information and medical professional information.

[0017] The image management device 105 is, for example, an information processing device, and is a device that stores affected area images, photographer information linked to the affected area images, and patient information linked to the affected area images.

[0018] The network 106 is an inter-device network for wireless data transmission, wired data transmission, various controls, etc. Various communication protocols are possible, such as Hypertext Transfer Protocol (HTTP), File Transfer Protocol (FTP), Picture Transfer Protocol (PTP), Universal Serial Bus (USB), Local Area Network (LAN), Health Level Seven (HL7), Digital Imaging and Communications in Medicine (DICOM), and any of them may be used as long as image data, text, control data, etc. can be communicated.

[0019] 2 is a block diagram of the image capture device 101 according to the embodiment. The image capture device 101 executes a predetermined control program to realize image capture processing, which will be described below, and functions as an image capture device.

[0020] The CPU 201 controls the entire imaging apparatus 101 .

[0021] The ROM 202 is a ROM that stores the operation processing procedures of the CPU 201 (for example, programs for processing when the power supply of the imaging device 101 is turned on, basic input / output processing, etc.).

[0022] The RAM 203 is a random access memory (RAM) that functions as the main memory of the CPU 201, but may be another memory device. For example, the RAM 203 may be configured with a non-volatile memory device such as a read only memory (ROM) or an electrically erasable programmable read-only memory (EEPROM). Various programs including a control program for implementing the processes described below are loaded from the ROM 202 or the like into the RAM 203 and executed by the CPU 201. The RAM 203 also provides a work area when the CPU 201 executes various processes.

[0023] The input unit 204 is an input unit such as buttons for performing various operations. For example, it is a release button located at the top of the digital camera, a cross key and setting keys located on the back, etc. In addition, a touch panel provided on the display unit 205 is also included in the input device. A user (photographer) can input various instructions to the digital camera (imaging device 101) by operating the input unit 204 on the input device.

[0024] The display unit 205 is a display device and performs various displays under the control of the CPU 201. For example, the display unit 205 displays an image captured by the imaging unit 209 in response to input of a shooting instruction by operating the release button, and displays various setting screens, etc. The display unit 205 may also display an image based on image data stored in the RAM 203 or the external storage device 207, and a live view image captured by the imaging unit 209.

[0025] The external I / F 206 is an I / F for reading and writing data from and to an external storage device 207 such as an SD card or a USB memory.

[0026] The external storage device 207 is an external storage medium such as an SD card or a USB memory.

[0027] A network I / F 208 is a network interface, and is connected to the network 106. In this embodiment, the imaging device 101 transmits and receives data to and from the imaging device control device 102 via the network 106.

[0028] The imaging unit 209 reads an optical image using a solid-state imaging element, and performs analog-to-digital conversion to generate electrical image data.

[0029] The image processing unit 210 executes various types of image processing. The CPU 201 stores the image data generated by the imaging unit 209 and the attribute information at that time in the RAM 203. Then, as necessary, a series of image processing is performed to create image data suited to the purpose of shooting, such as data including human visual characteristics, three-dimensional data, or both.

[0030] The file generation unit 211 executes file generation processing. The CPU 201 converts the image data generated by the image processing unit 210 into a general-purpose still image format to generate an image file. In addition, the CPU 201 can add or change EXIF ​​information to the image data generated by the image processing unit 210 and the image file generated by the file generation unit 211.

[0031] The CPU bus 212 includes an address bus, a data bus, and a control bus, and connects the CPU 201, the ROM 202, the RAM 203, the input unit 204, the display unit 205, the external I / F 206, the network I / F 208, the imaging unit 209, the image processing unit 210, and the file generation unit 211 to one another.

[0032] 3 is a block diagram of an information processing device according to an embodiment of the present invention, which performs the processes described below by executing a predetermined control program.

[0033] In the embodiment, the imaging device control device 102, the electronic medical record terminal device 103, the electronic medical record management device 104, and the image management device 105 are each an information processing device.

[0034] The CPU 301 controls the entire information processing apparatus.

[0035] The ROM 302 is a ROM that stores the operation processing procedures of the CPU 301 (for example, programs for processing the information processing device, basic input / output processing, etc.).

[0036] The RAM 303 is a random access memory (RAM) and functions as the main memory of the CPU 301, but may be another memory device. The RAM 303 may be configured with a non-volatile memory device such as a read only memory (ROM) or an electrically erasable programmable read-only memory (EEPROM). Various programs including a control program for implementing the processes described below are loaded from the ROM 302 or the like into the RAM 303 and executed by the CPU 301. The RAM 303 also provides a work area when the CPU 301 executes various processes.

[0037] The input unit 304 is a pointing device such as a keyboard having various keys for inputting characters, or a mouse. For example, the input unit 304 is used for operations such as inputting setting information for a program, or selecting icons, menus, and the like displayed on the display unit 305.

[0038] The display unit 305 is a display that displays images for interfacing with an operator, such as windows, icons, messages, and menus.

[0039] The external I / F 306 is an I / F for reading and writing data from and to an external storage device 307 such as an external HDD or a USB memory.

[0040] The external storage device 307 is an external storage medium such as an external HDD or a USB memory.

[0041] The HDD 308 is a non-volatile storage device, and is a HDD (Hard Disk Drive) that stores data.

[0042] The network I / F 309 is a network interface and is connected to the network 106. In this embodiment, the imaging device 101, the imaging device control device 102, the electronic medical record terminal device 103, the electronic medical record management device 104, and the image management device 105 are connected to each other via the network 106 so as to be able to communicate with each other and transmit and receive data.

[0043] The CPU bus 310 includes an address bus, a data bus, and a control bus, and connects the CPU 301, the ROM 302, the RAM 303, the input unit 304, the display unit 305, the external I / F 306, the HDD 308, and the network I / F 309 to one another.

[0044] Here, we will provide additional information about the data stored in the electronic medical record management device 104 in this embodiment. The electronic medical record management device 104 stores in the HDD 308 patient information (patient ID, name, age, sex), patient examination information (patient ID, medical department, medical condition, medical history, etc.), and medical staff information (medical staff ID, name, password, and other authentication information).

[0045] The patient information is information for identifying a patient, and a unique patient ID is defined for each patient. In this embodiment, the patient information is a patient information table (described later).

[0046] The patient examination information is information in which the patient's condition is accumulated and recorded. The patient examination information is stored in a patient examination information table (not shown) in association with the patient ID. Therefore, if the patient ID is known, the patient's medical department, condition, medical history, etc. can be known. In other words, the patient ID is used as a key to combine the patient information obtained from the patient information table with the patient examination information obtained from the patient examination information table, thereby generating electronic medical record information.

[0047] The medical worker information is information for identifying a medical worker, and a unique medical worker ID is defined for each medical worker. In this embodiment, the medical worker information is a medical worker information table (described later).

[0048] 4 is a diagram showing the rear view of the imaging device 101. The input unit 204 and the display unit 205 of the imaging device 101 will be described with reference to FIG.

[0049] The input unit 204 is made up of a power button 401 , a release button 402 , an up button 403 , a right button 404 , a down button 405 , a left button 406 , and an enter button 407 .

[0050] The power button 401 is a power button that switches the power ON / OFF. When the photographer presses the power button 401 while the imaging device 101 is not powered on, the CPU 201 determines that the photographer has instructed the imaging device 101 to turn the power ON, and turns the power ON. When the photographer presses the power button 401 while the imaging device 101 is powered on, the CPU 201 determines that the photographer has instructed the imaging device 101 to turn the power OFF, and turns the power OFF.

[0051] Release button 402 is a button that the photographer presses when photographing a subject. When the photographer presses release button 402, CPU 201 determines that an instruction to capture a still image or a video has been issued, and generates an image showing the subject using imaging unit 209, image processing unit 210, and file generation unit 211. In this embodiment, the subject is an affected area of ​​a patient, so when the photographer presses release button 402, an image of the affected area of ​​the patient is generated.

[0052] An up button 403 , a right button 404 , a down button 405 , a left button 406 , and a confirm button 407 are buttons used when the photographer selects and confirms an item displayed on a display 408 .

[0053] The display 408 functions as the display unit 205. The display 408 is a display device for displaying an input screen that prompts the photographer to enter various inputs and for displaying captured images.

[0054] 5A, 5B, and 5C are screens displayed on the display 408 of the imaging device 101. FIG.

[0055] 5A is a photographer authentication screen. The medical staff ID input area 501 is an area for inputting the ID of the medical staff who will be photographed using the imaging device 101. The password input area 502 is an area for inputting the password of the medical staff who will be photographed using the imaging device 101. When inputting the ID and password, a software keyboard screen (not shown) is displayed, allowing alphabets, numbers, etc. to be input. The photographer authentication button 503 is a button that is pressed when performing photographer authentication using the medical staff ID input in the medical staff ID input area 501 and the password input in the password input area 502.

[0056] 5B is a patient information display screen. A patient information display area 511 is an area of ​​the patient information display screen that displays patient information. In the patient information display area 511, a patient ID, a patient name, a patient age, and a patient sex are displayed.

[0057] FIG. 5C is an affected area image display screen. In the affected area image display screen, a patient information display area 521, an OK button 523, a cancel button 524, and an end button 525 are superimposed on the captured affected area image. The patient information display area 521 is an area for displaying patient information similar to the patient information display area 511. The affected area 522 is the imaged affected area of ​​the patient. The OK button 523 is a button to be pressed when the next affected area image is to be captured without deleting the affected area image displayed on the affected area image display screen. The cancel button 524 is a button to be pressed when the next affected area image is to be captured after deleting the affected area image displayed on the affected area image display screen. The end button 525 is a button to be pressed when the affected area image capture is to be ended.

[0058] 6A, 6B, and 6C are information tables that the electronic medical record management device 104 stores in the HDD 308. FIG.

[0059] FIG. 6A is a patient information table. The patient information table manages patient information. The patient information table is composed of a patient ID 601, name (Kanji) 602, age 603, and gender 604. The patient ID 601 is an ID capable of identifying a patient, composed of, for example, four digits. The name (Kanji) 602 is the Kanji notation of the patient's name. Age 603 is the patient's age. Gender 606 is the patient's gender. The patient information table stores records for each patient. In the example of FIG. 6A, patient records for three IDs are registered. Taking FIG. 6A as an example, the patient's name with patient ID 0001 is registered as Shimomaruko Hanako, her age is 35, and her gender is female.

[0060] FIG. 6B is a medical worker information table. The medical worker information table manages information on medical workers. The medical worker information table is composed of a medical worker ID 611, a name (Kanji) 612, and a password 613. The medical worker ID 611 is an ID that can identify a medical worker, for example, composed of four digits. The name (Kanji) 612 is the Kanji notation of the medical worker's name. The password 613 is a password corresponding to the medical worker ID. The medical worker information table stores records for each medical worker. In the example of FIG. 6B, medical worker records for two IDs are registered. Taking FIG. 6B as an example, it is registered that the name of the medical worker with a medical worker ID of 1001 is Yokohama Ichiro and the password is 1.

[0061] FIG. 6C is a patient examination information table. The patient examination information table is a table for managing patients examined by medical professionals. The patient examination information table is composed of a medical professional ID 611 and a patient ID. The medical professional ID 621 is an ID consisting of four digits that can identify a medical professional, and the ID registered in the medical professional ID 611 in the medical professional information table is registered. The patient ID 622 is an ID consisting of four digits that can identify a patient, and the ID registered in the patient ID 601 in the patient information table is registered. In the example of FIG. 6C, two records are registered. Taking FIG. 6C as an example, it can be seen that the medical professional with a medical professional ID of 1001 is examining a patient with a patient ID of 0001.

[0062] Fig. 7 is a process sequence diagram of the imaging system in this embodiment. In the explanation of Fig. 7, the medical staff is assumed to be a doctor. Fig. 7 explains the flow of operations in which, when a doctor logs in to an electronic medical record terminal to display a patient's electronic medical record and uses an imaging device to photograph an affected part of the patient, the doctor who is the photographer identifies the patient he is examining, and the imaging device associates an image of the affected part with patient information and stores the image in an image management device.

[0063] S701 to S711 are a processing sequence in which a doctor, who is a medical professional, logs in to the electronic medical record terminal device 103 and displays the electronic medical record of a patient.

[0064] In S701, the doctor logs in by inputting a medical staff ID and a password to the electronic medical record terminal device 103. At this time, the electronic medical record terminal device 103 may accept the medical staff ID and password from the doctor while displaying, for example, the photographer authentication screen shown in Fig. 5A.

[0065] In S702, the electronic medical record terminal device 103 transmits to the electronic medical record management device 104 a request for authentication (login authentication) of the medical staff ID and password entered by the doctor.

[0066] In S703, the electronic medical record management device 104 performs authentication processing for the received authentication request. In the authentication processing, the electronic medical record management device 104 determines whether or not the combination of the medical staff ID and password included in the medical staff information table in FIG. 6B is correct.

[0067] In S704, if the combination of the medical staff ID and password is correct, the electronic medical record management device 104 transmits an authentication response indicating successful authentication to the electronic medical record terminal device 103. If the combination of the medical staff ID and password is incorrect, the electronic medical record management device 104 transmits an authentication response indicating unsuccessful authentication to the electronic medical record terminal device 103.

[0068] In S705, if the authentication response indicates successful authentication, the electronic medical record terminal device 103 displays the electronic medical record screen. If the authentication response indicates unsuccessful authentication, the electronic medical record terminal device 103 displays a screen for inputting the medical staff ID and password again and waits for the doctor to log in (return to S701).

[0069] In S706, the doctor inputs information capable of identifying the patient to be examined to the electronic medical record terminal device 103. Here, the information capable of identifying the patient is the patient ID included in the patient information table in FIG. 6A.

[0070] In S707, the electronic medical record terminal device 103 transmits to the electronic medical record management device 104 a request to obtain medical record information for the patient ID input by the doctor.

[0071] In S708, the electronic medical record management device 104 performs a medical record information acquisition process in response to the received medical record information acquisition request. In the medical record information acquisition process, the electronic medical record management device 104 performs a process of generating electronic medical record information including the patient ID, name, age, sex, and the like included in the patient information table in FIG. 6A.

[0072] In S709, the electronic medical record management device 104 registers the doctor's medical staff ID and the patient's patient ID as a pair in the examined patient information table of Fig. 6C. If a record of the medical staff ID already exists, the electronic medical record management device 104 updates only the patient ID. In other words, the examined patient information table contains data that can identify the patient ID of a patient being examined by a doctor if the doctor's medical staff ID is known.

[0073] In S710, the electronic medical record management device 104 transmits the electronic medical record information of the patient generated in the processing of S708 to the electronic medical record terminal device 103 as a medical record information acquisition response.

[0074] In S711, the electronic medical record terminal device 103 converts the received medical record information acquisition response into an electronic medical record display format and displays the electronic medical record screen.

[0075] S712 to S724 are a processing sequence until the patient ID 601, name (kanji) 602, age 603, and sex 604 contained in the patient information table are set in the imaging device 101 after the doctor has confirmed the identity of the patient.

[0076] In S712, the doctor verifies that the electronic medical record information displayed on the electronic medical record terminal device 103 in S711 is the patient's own electronic medical record information. If the electronic medical record information is not the patient's own electronic medical record information, the doctor re-inputs the information of the patient to be examined into the electronic medical record terminal device 103 (return to S706), and the electronic medical record terminal device 103 displays the patient's own electronic medical record information newly acquired from the electronic medical record management device 104. If the electronic medical record information is the patient's own electronic medical record information, the doctor proceeds to S713.

[0077] In S713, the doctor enters a medical staff ID and a password in the medical staff ID input field 501 and the password input field 502, respectively, of the photographer authentication screen of FIG. 5A displayed on the display unit of the imaging device 101, and presses the photographer authentication button 503.

[0078] In S714, the imaging device 101 transmits to the imaging device control device 102 an authentication request for the medical staff ID and password entered by the doctor.

[0079] In S715, the imaging device control device 102 transmits the received authentication request to the electronic medical record management device 104.

[0080] In S716, the electronic medical record management device 104 performs authentication processing for the received authentication request. In the authentication processing, the electronic medical record management device 104 determines whether or not the combination of the medical staff ID and password included in the medical staff information table in FIG. 6B is correct.

[0081] In S717, if the combination of the medical staff ID and password is correct, the electronic medical record management device 104 transmits an authentication response indicating successful authentication to the imaging device control device 102. If the combination of the medical staff ID and password is incorrect, the electronic medical record management device 104 transmits an authentication response indicating failed authentication to the imaging device control device 102.

[0082] In S718, the imaging device control device 102 transmits the received authentication response to the imaging device 101. Then, the imaging device 101, which has received the authentication response, proceeds to S719 if the authentication response indicates successful authentication. If the authentication response indicates unsuccessful authentication, the imaging device 101 displays a screen for inputting a medical professional ID and password again, and waits for input of a medical professional ID and password from the doctor (return to S713).

[0083] In S719, the imaging device 101 transmits to the imaging device control device 102 a patient information acquisition request for the medical staff ID input by the doctor in S713.

[0084] In S720, the imaging device control device 102 transmits the received patient information acquisition request to the electronic medical record management device 104.

[0085] In S721, the electronic medical record management device 104 performs a patient information acquisition process in response to the received patient information acquisition request. In the patient information acquisition process, the electronic medical record management device 104 acquires the medical staff ID included in the patient information acquisition request, and acquires the patient ID associated with the medical staff ID from the examined patient information table of Fig. 6C. Then, the electronic medical record management device 104 acquires the patient information linked to the acquired patient ID from the patient information table of Fig. 6A.

[0086] In S722, the electronic medical record management device 104 transmits a patient information acquisition response including the patient information acquired in S721 to the imaging device control device 102.

[0087] In S723, the imaging device control device 102 transmits a patient information acquisition response including the received patient information to the imaging device 101.

[0088] In S724, the image capturing apparatus 101 acquires the patient information from the patient information acquisition response and sets the patient information in the image capturing apparatus 101.

[0089] S725 to S733 are a processing sequence in which a doctor photographs an affected part of a patient, and the imaging device 101 transmits the photographed image of the affected part to the image management device 105 in association with patient information.

[0090] In S725, the doctor points the imaging device 101 toward the affected area of ​​the patient and presses the release button 402 of the imaging device 101.

[0091] In S726, the imaging device 101 captures an image of the affected area of ​​the patient and generates affected area image data.

[0092] In S727, the imaging device 101 performs processing to link the patient information acquired by the imaging device 101 in S724 with the affected area image data generated in S726. In this embodiment, the imaging device 101 converts the affected area image data into a JPEG image, and sets the patient information (such as the patient ID and the patient name) in the EXIF ​​information of the JPEG image.

[0093] In S728, the doctor presses the end button 525 displayed on the display unit 205 of the imaging device 101 to end imaging of the affected area.

[0094] In S729, the imaging device 101 transmits to the imaging device control device 102 an image storage request for the affected area image linked to the patient information in S727.

[0095] In S730, the imaging device control device 102 performs processing for the received image storage request. The imaging device control device 102 stores in the image management device 105 the image of the affected area included in the image storage request.

[0096] In S731, when the imaging device control device 102 completes saving the affected area image in the image management device 105, it transmits an image save response indicating successful saving to the imaging device 101. If the saving of the affected area image in the image management device 105 cannot be completed, the imaging device control device 102 transmits an image save response indicating unsuccessful saving to the imaging device 101. If the image save response indicates successful saving, the imaging device 101 performs the process of S732. If the image save response indicates unsuccessful saving, the imaging device 101 makes an image save request again (return to S729).

[0097] In S732, the imaging apparatus 101 deletes the patient information set in S724.

[0098] In S733, the imaging device 101 deletes the image of the affected area transmitted in S729.

[0099] S734 to S738 are a processing sequence when a doctor who is a medical professional logs off from the electronic medical record terminal device 103 and finishes examining a patient.

[0100] In S734, the doctor logs off from the electronic medical record terminal device 103.

[0101] In S735, the electronic medical record terminal device 103 transmits a logoff request for the logged-in medical staff ID to the electronic medical record management device 104.

[0102] In S736, the electronic medical record management device 104 performs a medical patient information update process in response to the received logoff request. In the medical patient information update process, the electronic medical record management device 104 deletes the record of the medical staff ID included in the logoff request from the medical patient information table in Fig. 6C. In other words, the doctor is no longer examining the patient.

[0103] In S737, the electronic medical record management device 104 sends a logoff response to the electronic medical record terminal device 103.

[0104] In S738, when the electronic medical record terminal device 103 receives the log-off response, it waits for input of a medical staff ID and password from the doctor (return to S701).

[0105] A supplementary explanation will be given for the processing sequence in Fig. 7. For the sake of simplicity, the processing sequence in Fig. 7 is described assuming that the affected area is photographed once, but the affected area may be photographed multiple times. In that case, the processing of S726 and S727 is repeated the number of times the affected area is photographed, and then the processing of S728 is performed.

[0106] A supplementary note about the processing sequence in Fig. 7. For simplicity of explanation, the processing sequence in Fig. 7 is described assuming that there is one patient, but a doctor may examine multiple patients between logging in and logging off the electronic medical record terminal device 103. In that case, the processing from S706 to S733 is repeated for each patient, and then the processing in S734 is performed.

[0107] 8A, 8B, 8C, and 8D are flowcharts of the imaging device 101, imaging device control device 102, electronic medical record terminal device 103, and electronic medical record management device 104 for realizing the processing sequence of the imaging system described in FIG.

[0108] Fig. 8A will be described. The processing of the flowchart in Fig. 8A is stored as software in the ROM 202 of the imaging device 101. The software stored in the ROM 202 is expanded in the RAM 203 and executed by the CPU 201, and is realized by the CPU 201 controlling each unit of the imaging device 101.

[0109] When the power button 401 of the imaging device 101 is pressed to turn the power on, the CPU 201 starts the process of this flowchart.

[0110] In S8001, the CPU 201 displays the photographer authentication screen of FIG. 5A on the display 408, and proceeds to S8002.

[0111] In S8002, the CPU 201 waits for the photographer to input a medical staff ID and password into the photographer authentication screen in Fig. 5A and press the photographer authentication button 503. If the photographer authentication button 503 is pressed (S713 in Fig. 7), the CPU 201 proceeds to S8003. If not, the CPU 201 returns to S8002 and performs loop processing.

[0112] In S8003, the CPU 201 transmits an authentication request to the imaging device control device 102 (S714 in FIG. 7). The authentication request includes the medical staff ID and password entered by the photographer. When the CPU 201 receives an authentication response from the imaging device control device 102 (S718 in FIG. 7), the process proceeds to S8004.

[0113] In S8004, the CPU 201 checks the result of the authentication response. If the content of the authentication response indicates successful authentication, the CPU 201 proceeds to S8005, and if the content of the authentication response indicates unsuccessful authentication, the CPU 201 returns to S8002.

[0114] In S8005, the CPU 201 transmits a patient information acquisition request to the imaging device control device 102 (S719 in FIG. 7). The patient information acquisition request includes a medical staff ID. When the CPU 201 receives a patient information acquisition response from the imaging device control device 102 (S723 in FIG. 7), the process proceeds to S8006.

[0115] In S8006, CPU 201 extracts patient ID 601, name (Kanji) 602, age 603, and gender 604 included in the patient information acquisition response as patient information, stores them in RAM 203 (S724 in FIG. 7), displays the patient information display screen of FIG. 5B on display 408, and proceeds to S8007. In the example of FIG. 5B, the patient information displayed is that patient ID 601 is 0001, name (Kanji) 602 is Shimomaruko Hanako, age 603 is 35, and gender 604 is female.

[0116] In S8007, the CPU 201 performs loop processing and waits for the photographer to press the release button 402, which is an example of an image capture instruction. If the release button 402 is pressed (S725 in FIG. 7), the CPU 201 proceeds to S8008, and if not, returns to S8007.

[0117] In S8008, the CPU 201 reads out the captured image obtained by pressing the release button 402 from the RAM 203. Then, the CPU 201 uses the file generation unit 211 to generate an affected area image by adding the patient ID 601, name (Kanji) 602, age 603, and gender 604 saved in the RAM 203 in S8006 as EXIF ​​information to the captured image, and stores the image in the RAM 203 (S727 in FIG. 7). Then, the CPU 201 displays the affected area image display screen of FIG. 5C on the display 408, and proceeds to S8009.

[0118] In S8009, the CPU 201 performs loop processing and waits for the photographer to press any one of the OK button 523, the cancel button 534, or the end button 525. When any one of the buttons is pressed, the CPU 201 proceeds to S8010.

[0119] In S8010, if the end button 525 indicating the end of imaging of the affected area has been pressed (S728 in FIG. 7), the CPU 201 proceeds to S8013, and if not, proceeds to S8011.

[0120] In S8011, if the OK button 523 is pressed, the CPU 201 returns to S8007, and if the OK button 523 is not pressed and the cancel button 524 is pressed, the CPU 201 proceeds to S8012.

[0121] In S8012, the CPU 201 deletes the affected area image generated in S8008 from the RAM 203. When the deletion is completed, the CPU 201 returns to S8007.

[0122] In S8013, the CPU 201 transmits an image storage request to the imaging device control device 102 (S729 in FIG. 7). The image storage request includes the affected area image stored in the RAM 203 in S8008. When the CPU 201 receives an image storage response from the imaging device control device 102 (S731 in FIG. 7), the process proceeds to S8014.

[0123] In S8014, if the image save response indicates successful save, the CPU 201 proceeds to S8015, and if not, returns to S8013 and transmits the image save request to the imaging device control device 102 again.

[0124] In S8015, the CPU 201 deletes the affected area image generated in S8008 from the RAM 203 (S732 in FIG. 7), and the process proceeds to S8016.

[0125] In S8016, the CPU 201 deletes the patient ID 601, the name (Kanji) 602, the age 603, and the gender 604 stored in S8006 from the RAM 203 (S733 in FIG. 7), and ends the process.

[0126] Fig. 8B will be described. The processing of the flowchart in Fig. 8B is stored as software in the ROM 302 of the imaging device control device 102. The software stored in the ROM 302 is expanded in the RAM 303 and executed by the CPU 301, and is realized by the CPU 301 controlling each unit of the imaging device control device 102.

[0127] When a power button (not shown) of the imaging device control device 102 is pressed to turn the power on, the CPU 301 starts the process of this flowchart.

[0128] In S8101, if the power button (not shown) of the imaging device control device 102 is pressed to turn the power off, the CPU 301 ends the process. If not, the CPU 301 proceeds to S8102.

[0129] In S8102, the CPU 301 determines whether or not it has received any of an authentication request (S714 in FIG. 7), a patient information acquisition request (S719 in FIG. 7), and an image storage request (S729 in FIG. 7) from the imaging device 101. If any of the requests has been received, the CPU 301 proceeds to S8103, and if not, returns to S8101 and performs loop processing.

[0130] In S8103, if the CPU 301 receives an authentication request (S714 in FIG. 7), the process proceeds to S8104. Otherwise (if a patient information acquisition request or an image storage request has been received), the CPU 301 proceeds to S8106.

[0131] In S8104, the CPU 301 transmits the authentication request received from the image capture device 101 to the electronic medical record management device 104 (S715 in FIG. 7), and proceeds to S8105.

[0132] In S8105, when the CPU 301 receives the authentication response from the electronic medical record management device 104 (S717 in FIG. 7), it transmits the authentication response to the imaging device 101 (S718 in FIG. 7) and returns to S8101.

[0133] In S8106, if the CPU 301 has received a patient information acquisition request (S719 in FIG. 7), the process proceeds to S8107. If not (if an image storage request has been received), the CPU 301 proceeds to S8109.

[0134] In S8107, the CPU 301 transmits the patient information acquisition request received from the imaging device 101 to the electronic medical record management device 104 (S721 in FIG. 7), and proceeds to S8108.

[0135] In S8108, when the CPU 301 receives a patient information acquisition response from the electronic medical record management device 104 (S722 in FIG. 7), it transmits an authentication response to the imaging device 101 (S723 in FIG. 7) and returns to S8101.

[0136] In S8109, the CPU 301 acquires the affected area image included in the image storage request received from the imaging device 101, and stores it in the image management device 105. If the affected area image is successfully stored in the image management device 105, the CPU 301 transmits an image storage response indicating that storage was successful. If not, the CPU 301 transmits an image storage response indicating that storage was unsuccessful, and returns to S8101.

[0137] Now, referring to Fig. 8C, the process of the flowchart in Fig. 8C is stored as software in the ROM 302 of the electronic medical record terminal device 103. The software stored in the ROM 302 is expanded in the RAM 303 and executed by the CPU 301, which then controls each unit of the electronic medical record terminal device 103 to realize the process.

[0138] When the power button (not shown) of the electronic medical record terminal device 103 is pressed to turn the power ON, the CPU 301 starts the processing of this flowchart.

[0139] In S8201, the CPU 301 waits for a doctor, who is a medical professional, to input a medical professional ID and a password. If the medical professional ID and password are input, the CPU 301 proceeds to S8202, and if not, returns to S8201 and performs loop processing.

[0140] In S8202, the CPU 301 transmits an authentication request to the electronic medical record management device 104 (S702 in FIG. 7). The authentication request includes a medical staff ID and password entered by a doctor who is a medical staff member. When the CPU 301 receives an authentication response from the electronic medical record management device 104 (S704 in FIG. 7), the process proceeds to S8203.

[0141] In S8203, the CPU 301 checks the result of the authentication response. If the authentication is successful, the CPU 301 proceeds to S8204, and if the authentication is unsuccessful, the CPU 301 returns to S8201.

[0142] In S8204, the CPU 301 waits for a doctor, who is a medical professional, to input a patient ID. When the patient ID is input, the CPU 301 proceeds to S8205. If not, the CPU 301 returns to S8204 and performs loop processing.

[0143] In S8205, the CPU 301 transmits a request to obtain medical record information to the electronic medical record management device 104 (S707 in FIG. 7). The request to obtain medical record information includes a medical staff ID and a patient ID. When the CPU 301 receives a response to obtain medical record information from the electronic medical record management device 104 (S710 in FIG. 7), the CPU 301 proceeds to S8206.

[0144] In S8206, the CPU 301 acquires the medical chart information from the medical chart information acquisition response, displays the medical chart information on the display unit 305 of the electronic medical chart terminal device 103, and proceeds to S8207.

[0145] In S8207, the CPU 301 performs a loop process and waits for an input from the doctor as a medical practitioner as to whether he / she will examine the next patient or log off to finish the medical treatment. If the CPU 301 receives an input from the doctor as a medical practitioner, the CPU 301 proceeds to S8208, otherwise, the CPU 301 returns to S8207.

[0146] In S8208, the CPU 301 determines whether or not a logoff input has been received. If a logoff input has been received (S734 in FIG. 7), the process proceeds to S8209. If not, the CPU 301 returns to S8204.

[0147] In S8209, the CPU 301 transmits a logoff request to the electronic medical record management device 104 (S735 in FIG. 7). When the CPU 301 receives a logoff response from the electronic medical record management device 104 (S738 in FIG. 7), the CPU 301 ends the process.

[0148] Now, Fig. 8D will be described. The processing of the flowchart in Fig. 8D is stored as software in ROM 302 of electronic medical record management device 104. The software stored in ROM 302 is expanded in RAM 303 and executed by CPU 301, and is realized by CPU 301 controlling each unit of electronic medical record management device 104.

[0149] When the power button (not shown) of the electronic medical record management device 104 is pressed to turn the power ON, the CPU 301 starts the processing of this flowchart.

[0150] In S8301, if the power button (not shown) of the electronic medical record management device 104 is pressed to turn the power off, the CPU 301 ends the process. If not, the CPU 301 proceeds to S8302.

[0151] In S8302, the CPU 301 determines whether or not any of the following has been received: an authentication request from the electronic medical record terminal device 103 (S703 in FIG. 7), a request to acquire medical record information from the electronic medical record terminal device 103 (S707 in FIG. 7), an authentication request from the imaging device control device 102 (S715 in FIG. 7), a request to acquire patient information from the imaging device control device 102 (S720 in FIG. 7), or a logoff request from the electronic medical record terminal device 103 (S735 in FIG. 7). If any of the requests has been received, the CPU 301 proceeds to S8303, and if not, returns to S8301 and performs loop processing.

[0152] In S8303, if the CPU 301 has received an authentication request (S702 or S715 in FIG. 7), the process proceeds to S8304, and if not, the process proceeds to S8306.

[0153] In S8304, the CPU 301 determines whether or not the medical staff ID and password included in the received authentication request match the combination of the medical staff ID 611 and password 613 in the medical staff information table of FIG. 6B, and proceeds to S8305.

[0154] In S8305, if the medical staff ID and password included in the received authentication request match the medical staff ID 611 and password 613 in the medical staff information table, the CPU 301 transmits an authentication response indicating successful authentication (S704 or S717 in FIG. 7). If they do not match, the CPU 301 transmits an authentication response indicating unsuccessful authentication (S704 or S717 in FIG. 7). Then, when the CPU 301 finishes the authentication response transmission process, it returns to S8301.

[0155] In S8306, if the CPU 301 has received a medical record information acquisition request (S707 in FIG. 7), the process proceeds to S8307, and if not, the process proceeds to S8310.

[0156] In S8307, the CPU 301 acquires the patient information table (FIG. 6A) and the patient examination information table (not shown) stored in the HDD 308 of the electronic medical record management device 104, generates medical record information, and proceeds to S8308.

[0157] In S8308, the CPU 301 updates the examined patient information table (FIG. 6C) stored in the HDD 308 of the electronic medical record management device 104. Specifically, the CPU 301 acquires the medical staff ID and the patient ID from the medical record information acquisition request, and registers the combination of the medical staff ID and the patient ID in the examined patient information table. If the medical staff ID has already been registered in the examined patient information table, the CPU 301 updates the patient ID of the registered medical staff ID. When the CPU 301 finishes updating the examined patient information table (FIG. 6C), the process proceeds to S8309.

[0158] In S8309, the CPU 301 transmits the medical chart information acquisition response including the medical chart information generated in S8307 (S710 in FIG. 7), and when the transmission is completed, the process returns to S8301.

[0159] In S8310, if the CPU 301 has received a patient information acquisition request (S720 in FIG. 7), the process proceeds to S8311. Otherwise (if a logoff request (S735 in FIG. 7) has been received), the CPU 301 proceeds to S8313.

[0160] In S8311, the CPU 301 acquires a medical staff ID from the patient information acquisition request. The CPU 301 acquires a patient ID associated with the acquired medical staff ID from the examined patient information table (FIG. 6C) stored in the HDD 308 of the electronic medical record management device 104. The CPU 301 then acquires patient information (patient ID 601, name (Kanji) 602, age 603, gender 604) of the acquired patient ID from the patient information table (FIG. 6A) stored in the HDD 308 of the electronic medical record management device 104, and proceeds to S8312.

[0161] In S8312, the CPU 301 transmits a patient information acquisition response including the patient information acquired in S8311 (S723 in FIG. 7), and upon completion of the transmission, returns to S8301.

[0162] In S8313, the CPU 301 acquires the medical staff ID included in the logoff request, deletes the record of the medical staff ID from the examined patient information table (FIG. 6C) stored in the HDD 308 of the electronic medical record management device 104, and proceeds to S8314.

[0163] In step S8314, CPU 301 transmits a logoff response (S737 in FIG. 7). Then, when the process of transmitting the logoff response ends, the process returns to step S8301.

[0164] As described above, the patient ID of the patient whose medical record information is displayed (viewed) on the electronic medical record terminal device 103 that the medical worker is operating (logging in) is associated with the medical worker operating the electronic medical record terminal device 103, and the information is managed as a patient examination information table. Then, from the patient examination information table, the patient ID of the patient whose medical record information is displayed (viewed) on the electronic medical record terminal device that the same medical worker as the medical worker identified as the photographer of the imaging device 101 is operating (logging in) is identified, and the patient information of the identified patient ID is transmitted to the imaging device. The imaging device 101 transmits the affected area image and the patient image as a set to the imaging device control device 102 of the management system, so that the affected area image captured by the medical worker can be easily linked to the patient information of the patient.

[0165] Since the electronic medical record management device 104 links the medical staff ID of the doctor with the patient ID of the patient under examination, the doctor who opens the electronic medical record of the patient who will be photographing the affected part can simply request authentication with the imaging device 101 and set the patient information in the authenticated imaging device 101. Therefore, the patient information of the photographer photographing the affected part can be linked with the photographed image of the affected part.

[0166] When a medical professional presses the release button to instruct imaging, the imaging device 101 generates an image of the affected area of ​​the patient and links the image of the affected area to the patient information. This allows the medical professional to link the image of the affected area to the patient information without having to perform a separate operation to link the image of the affected area to the patient information.

[0167] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the present invention.

[0168] In the embodiment, an example was shown in which authentication of medical personnel in the imaging device 101 is performed by the electronic medical record management device 104, but information in the medical personnel information table may be stored in the imaging device 101, and authentication of medical personnel may be performed by the imaging device 101.

[0169] In the embodiment, password authentication has been shown as an example of authentication of medical personnel in the imaging device 101, but any authentication method may be used as long as authentication can be performed. In addition to memory authentication such as password authentication, medical personnel may be authenticated by possession authentication using an IC card, or biometric authentication such as fingerprint authentication, face authentication, or iris authentication. Furthermore, medical personnel may be authenticated by multi-factor authentication that combines a plurality of authentication methods including memory authentication, possession authentication, and biometric authentication.

[0170] In the embodiment, a doctor is shown as an example of a medical professional, but the medical professional may be a nurse, a radiologist, or any other medical professional who takes images of the affected area of ​​a patient.

[0171] Further, a supplementary explanation will be given regarding this embodiment.

[0172] For the sake of simplicity, the present embodiment has been described with respect to a configuration in which there is one imaging device 101 and one electronic medical record terminal device 103, but there may be a plurality of imaging devices 101 and a plurality of electronic medical record terminal devices 103.

[0173] The configuration of one imaging device 101 and one electronic medical record terminal device 103 described in this embodiment is specifically assumed to be used in a clinic with one doctor. The configuration when one imaging device 101 is used to capture images of the affected area is as shown in FIG. 9A. Also, the configuration when a derm camera for taking close-up images of the skin is also used as the imaging device 101 is as shown in FIG. 9B. Even in the operation as shown in FIG. 9B, the patient information of the patient being examined by the doctor can be set in each imaging device 101, so this embodiment is effective.

[0174] 9C shows an example of operation in which two doctors share one imaging device 101. In FIG. 9C, a doctor who needs to photograph an affected area picks up the imaging device 101 and photographs the affected area of ​​each patient. Even in the case of operation as shown in FIG. 9C, the present embodiment is effective because the patient information of the patient being examined by the doctor can be set in the imaging device 101. Also, even if multiple patients are being examined at the same time, there is an advantage that the patient information of the patient being examined by the doctor can be appropriately set in the single imaging device 101.

[0175] Also, Fig. 9D assumes operation in a large hospital where a doctor examines patients in each of a plurality of examination rooms. In such a case, an imaging device 101 and an electronic medical record terminal device 103 are arranged in each of a plurality of examination rooms. Even in an operation such as Fig. 9D, the present embodiment is effective because patient information of a patient examined by a doctor can be set in any of the imaging devices 101. In addition, even if a plurality of patients are examined at the same time, there is an effect that the patient information of a patient examined by a doctor can be appropriately set in the imaging device 101 that captures an image of an affected part from among the plurality of imaging devices 101.

[0176] When a doctor logs in to the electronic medical record terminal device 103 and requests and obtains medical record information of a patient to be examined from the electronic medical record management device 104, the electronic medical record terminal device 103 may display the contents of the corresponding patient's medical record on its screen, and may also display a selection item for selecting "take an image" or "not take an image". When the electronic medical record terminal device 103 selects "take an image", it transmits that information to the electronic medical record management device 104. When the electronic medical record management device 104 detects the reception of information indicating that "take an image" has been selected, it holds the operated doctor ID and patient ID, and information indicating that imaging will be performed, and waits for login from the imaging device 101. When there is login from the imaging device 101, the electronic medical record management device 104 performs authentication processing. Then, when authentication is successful and the user ID input when logging in to the imaging device 101 matches the doctor ID previously held, the electronic medical record management device 104 may transmit information about the patient (patient ID, name, sex, age, imaging part, etc.) to the imaging device 101 that has logged in. As a result, when a doctor who operates the imaging device 101 logs in from the imaging device 101, the doctor can immediately check whether or not there is an error in the patient about to be imaged.

[0177] Second embodiment The second embodiment is an extension of the first embodiment. In the second embodiment, an example will be described in which not only a medical professional logs in to the electronic medical record terminal device 103 to examine a patient, but also a patient ID that identifies the patient is photographed and the patient information is linked to an image of the affected area by the imaging device 101.

[0178] FIG. 10A is a block diagram of an imaging device according to the second embodiment. In the second embodiment, the imaging device 101 further includes a barcode analysis unit 213 connected to the CPU bus 212. The barcode analysis unit 213 analyzes an image file including a barcode image in a general-purpose still image format generated by the file generation unit 211, and acquires a barcode character string. The CPU 201 performs barcode analysis using the barcode analysis unit 213 on an image file obtained by converting image data generated by the image processing unit 210 into a general-purpose still image format by the file generation unit 211. If the analysis is successful, the barcode analysis unit 213 returns a barcode character string. In the second embodiment, the barcode analysis is performed on a barcode image of a patient ID, and if the analysis is successful, the barcode image returns the patient ID. The barcode image is also called an identification information image. The barcode analysis unit 213 may be realized as a function of the CPU 201 that executes software for analyzing barcodes.

[0179] FIG. 10B shows a photographer authentication screen displayed on the display 408 of the imaging device 101. As shown in FIG.

[0180] A description of the medical staff ID input area 1001 will be omitted since it is similar to the medical staff ID input area 501. A description of the password input area 1002 will be omitted since it is similar to the password input area 502. A description of the photographer authentication button 1003 will be omitted since it is similar to the photographer authentication button 503. A patient authentication button 1004 is a button that is pressed when acquiring patient information by photographing a patient ID barcode.

[0181] 11 is a process sequence diagram of the imaging system when capturing an image of a patient ID barcode. In the second embodiment, the display 408 of the imaging device 101 displays the photographer authentication screen of FIG.

[0182] In the second embodiment, when a doctor inputs a medical staff ID and a password on the photographer authentication screen in Fig. 10B and presses a photographer authentication button 1003, S713 starts. When the doctor presses a patient authentication button 1004, S1101 in Fig. 11 starts.

[0183] In S1102, the doctor verifies the identity of the patient who is to undergo the imaging of the affected area.

[0184] In S1103, the doctor points the imaging device 101 at the patient ID barcode and presses the release button 402 of the imaging device 101. Note that the patient ID barcode is a piece of paper on which the patient ID 601 for each patient is printed as a barcode, and is carried by the patient himself / herself when in the hospital.

[0185] In S1104, the imaging device 101 captures an image of the patient ID barcode and generates barcode image data.

[0186] In S1105, the imaging device 101 performs processing to analyze the image data of the patient ID barcode generated in S1104 and acquire the patient ID. In this embodiment, the barcode image data is converted into a JPEG image, and the JPEG image is analyzed by the barcode analysis unit 213 to acquire the patient ID.

[0187] In S1106, the imaging device 101 transmits to the imaging device control device 102 a patient information acquisition request for the patient ID acquired in S1105.

[0188] In S1107, the imaging device control device 102 transmits the received patient information acquisition request to the electronic medical record management device 104.

[0189] In S1108, the electronic medical record management device 104 performs a patient information acquisition process in response to the received patient information acquisition request. In the patient information acquisition process, the electronic medical record management device 104 acquires the patient ID included in the patient information acquisition request, and acquires the patient information corresponding to the patient ID from the patient information table in FIG. 6A.

[0190] In S1109, the electronic medical record management device 104 transmits the patient information acquired in S1108 to the imaging device control device 102 as a patient information acquisition response.

[0191] In S1110, the imaging device control device 102 transmits the received patient information acquisition response to the imaging device 101.

[0192] S1111 to S1120 are similar to S724 to S733, so the description will be omitted.

[0193] FIG. 12 is a flowchart of the imaging device 101 according to the second embodiment.

[0194] 12 is stored as software in the ROM 202 of the imaging device 101. The software stored in the ROM 202 is expanded into the RAM 203 and executed by the CPU 201, and is realized by the CPU 201 controlling each unit of the imaging device 101.

[0195] When the power button 401 of the imaging device 101 is pressed to turn the power on, the CPU 201 starts the process of this flowchart.

[0196] In S1201, the CPU 201 displays the photographer authentication screen of FIG. 10B on the display 408, and proceeds to S1202.

[0197] In S1202, the CPU 201 checks whether the photographer has pressed the patient authentication button 1004 on the photographer authentication screen (FIG. 10B). If the patient authentication button 1004 has been pressed (S1101 in FIG. 11), the CPU 201 proceeds to S1203, and if not, the CPU 201 proceeds to S1207.

[0198] In S1203, the CPU 201 performs loop processing and waits for the photographer to press the release button 402. If the release button 402 is pressed (S1103 in FIG. 11), the CPU 201 proceeds to S1204, and if not, returns to S1203.

[0199] In S1204, the CPU 201 performs processing to analyze the captured image data of the patient ID barcode and acquire the patient ID, and then proceeds to S1205.

[0200] In S1205, if the CPU 201 performs the barcode analysis and successfully acquires the patient ID, the process proceeds to S1206, and if not, the process returns to S1203.

[0201] In S1206, the CPU 201 transmits a patient information acquisition request to the imaging device control device 102 (S1106 in FIG. 11). The patient information acquisition request includes a patient ID. When the CPU 201 receives a patient information acquisition response from the imaging device control device 102 (S1110 in FIG. 11), the process proceeds to S1212.

[0202] In S1207, the CPU 201 checks whether the photographer has pressed the photographer authentication button 1003 on the photographer authentication screen (FIG. 10B). If the photographer authentication button 1003 has been pressed (S713 in FIG. 7), the CPU 201 proceeds to S1208, and if not, returns to S1202.

[0203] Since steps S1208 to S1221 are the same as steps S8003 to S8016, the description thereof will be omitted.

[0204] The flow chart of the process of the imaging device control device 102 in the second embodiment is similar to that in the first embodiment, and therefore a description thereof will be omitted.

[0205] The flow chart of the processing of the electronic medical record terminal device 103 in the second embodiment is similar to that in the first embodiment, so the explanation will be omitted.

[0206] The flowchart of the process of the electronic medical record management device 104 in the second embodiment is almost the same as that in the first embodiment. In the second embodiment, the process of S8311 is changed as follows.

[0207] In S8311, if the patient information acquisition request includes a medical staff ID, the CPU 301 of the electronic medical record management device 104 acquires the medical staff ID and acquires the patient ID from the examined patient information table (FIG. 6C) stored in the HDD 308 of the electronic medical record management device 104. Then, the CPU 301 acquires the patient information (patient ID 601, name (kanji) 602, age 603, gender 604) of the acquired patient ID from the patient information table (FIG. 6A) stored in the HDD 308 of the electronic medical record management device 104, and proceeds to S8312. If the patient information acquisition request includes a patient ID, the CPU 301 acquires the patient ID and acquires the patient information (patient ID 601, name (kanji) 602, age 603, gender 604) of the acquired patient ID from the patient information table (FIG. 6A) stored in the HDD 308 of the electronic medical record management device 104, and proceeds to S8312.

[0208] The processes other than S8311 are similar to those in the first embodiment, and therefore the description thereof will be omitted.

[0209] As a result, the imaging device 101 can link patient information with images of the affected area not only when a medical professional logs in to the electronic medical record terminal device 103 to examine a patient, but also by photographing the barcode of the patient ID that identifies the patient.

[0210] By using the imaging device 101 of the second embodiment, when a medical professional carries the imaging device 101, the medical professional can easily link patient information and images of the affected area. Specifically, when a patient's medical record is displayed on an electronic medical record terminal in a treatment room or the like, the imaging device 101 acquires patient information using medical professional authentication as in the first embodiment. For example, when a bedsore (pressure ulcer) is discovered in a patient's hospital ward and an image of the affected area is urgently captured, the imaging device 101 acquires patient information by capturing an image of the patient ID carried by the patient as in the second embodiment. This has the effect of enabling a medical professional to link patient information and images of the affected area.

[0211] (Third embodiment) The third embodiment is an extension of the first embodiment. In the third embodiment, when the photographer authentication in S714 in the first embodiment fails due to a communication failure and the patient information cannot be acquired before capturing an image of the affected area, the patient information is linked to the captured image after the image of the affected area is captured.

[0212] 13 is a process sequence diagram of the imaging system. S1301 to S1313 are similar to S701 to S713, and therefore the description will be omitted.

[0213] In S1314, the imaging device 101 transmits an authentication request for the medical staff ID and password entered by the doctor to the imaging device control device 102, but the request fails due to a communication failure. For example, if the imaging device 101 does not receive an authentication response to the authentication request from the imaging device control device 102 even after waiting for a predetermined time, the imaging device 101 may determine that a communication failure has occurred.

[0214] In step S1315, the imaging apparatus 101 stores in the RAM 203 the authentication request transmitted in step S1314.

[0215] S1316 to S1318 are similar to S724 to S726, and therefore the description thereof will be omitted.

[0216] In S1319, the imaging device 101 converts the image data captured in S1318 into a general-purpose still image format to generate an image file. In this embodiment, the imaging device 101 converts the affected area image data into a JPEG image.

[0217] In S1320, the doctor performs personal identification to verify that the electronic medical record information displayed on the electronic medical record terminal device 103 in S1311 is the electronic medical record information of the patient himself / herself.

[0218] In S1321, the doctor presses the end button 525 displayed on the display unit 205 of the imaging device 101 to end imaging of the affected area.

[0219] In S1322, the imaging apparatus 101 reads the authentication request stored in the RAM 203 in S1315 in order to make the authentication request in S1323.

[0220] S1323 to S1332 are similar to S714 to S723, and therefore the description thereof will be omitted.

[0221] In S1333, the imaging device 101 performs processing to link the patient information acquired in S1332 with the image file generated in S1319. In this embodiment, the imaging device 101 sets the patient information (such as the patient ID and the patient name) in the EXIF ​​information of the image file.

[0222] S1334 to S1343 are similar to S729 to S738, and therefore the description thereof will be omitted.

[0223] FIG. 14 is a flowchart of the imaging device 101 for implementing the processing sequence of the imaging system described with reference to FIG.

[0224] 14 is stored as software in the ROM 202 of the imaging device 101. The software stored in the ROM 202 is expanded in the RAM 203 and executed by the CPU 201, and is realized by the CPU 201 controlling each unit of the imaging device 101.

[0225] When the power button 401 of the imaging apparatus 101 is pressed to turn the power ON, the processing of this flowchart is started by the CPU 201. S1401 to S1402 are similar to S8001 to S8002, and therefore a description thereof will be omitted.

[0226] In S1403, the CPU 201 transmits an authentication request to the imaging device control device 102 (S714 in FIG. 7). The authentication request includes the medical staff ID and password entered by the photographer. When the CPU 201 receives an authentication response from the imaging device control device 102 (S718 in FIG. 7) or when a communication failure such as a communication timeout occurs (S1314 in FIG. 13), the process proceeds to S1404.

[0227] In step S1404, the CPU 201 checks the result of the authentication response. If the communication is not good, the CPU 201 proceeds to step S1405, and if not, the CPU 201 proceeds to step S1406.

[0228] In S1405, the CPU 201 stores the authentication request of S1403 in the RAM 203, and proceeds to S1409.

[0229] S1406 to S1409 are similar to S8004 to S8007, and therefore the description will be omitted.

[0230] In S1410, the CPU 201 checks whether or not the patient information has been set in the RAM 203 in S1408. If the patient information has not been set due to poor communication or the like, the CPU 201 proceeds to S1411, and if the patient information has been set due to successful authentication, the CPU 201 proceeds to S1412.

[0231] In S1411, the CPU 201 reads out captured image data obtained by pressing the release button 402 from the RAM 203. Then, the CPU 201 uses the file generation unit 211 to convert the captured image data into a general-purpose still image format, stores it in the RAM 203 (S1319 in FIG. 13), and proceeds to S1413.

[0232] S1412 to S1416 are similar to S8008 to S8012, and therefore the description will be omitted.

[0233] In S1417, the CPU 201 checks whether patient information is linked to the image file stored in the RAM 203. If the image file is not linked to the patient information, the CPU 201 proceeds to S1418, and if linked, the CPU 201 proceeds to S1423.

[0234] In S1418, the CPU 201 reads the authentication request stored in the RAM 203 in S1405, and proceeds to S1419.

[0235] In S1419, the CPU 201 transmits an authentication request to the imaging device control device 102 (S1323 in FIG. 13). When the CPU 201 receives an authentication response from the imaging device control device 102 (S1327 in FIG. 13), the process proceeds to S1420.

[0236] In step S1420, the CPU 201 checks the result of the authentication response. If the authentication is successful, the CPU 201 proceeds to step S1421, and if the authentication is unsuccessful, the CPU 201 returns to step S1419 and executes the authentication request process, including transmitting the authentication request again.

[0237] In S1421, the CPU 201 transmits a patient information acquisition request to the imaging device control device 102 (S1328 in FIG. 13). The patient information acquisition request includes a medical staff ID. When the CPU 201 receives a patient information acquisition response from the imaging device control device 102 (S1336 in FIG. 13), the process proceeds to S1422.

[0238] In S1422, the CPU 201 extracts the patient ID 601, name (Kanji) 602, age 603, and gender 604 included in the patient information acquisition response, and stores them in the RAM 203. Then, the CPU 201 uses the file generation unit 211 to generate an affected area image in which the patient ID 601, name (Kanji) 602, age 603, and gender 604 stored in the RAM 203 are added as EXIF ​​information to the image file stored in the RAM 203 in S1411, and stores the image in the RAM 203 (S1333 in FIG. 13). When the patient information linking process ends, the CPU 201 proceeds to S1423.

[0239] S1423 to S1426 are similar to S8013 to S8016, and therefore the description will be omitted.

[0240] As a result, even if the authentication of the photographer fails due to poor communication, the imaging device 101 can store the authentication request and easily resend the authentication request after completing the imaging of the affected area, obtain the patient information, and link the patient information to the captured image.

[0241] (Other Examples) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.

[0242] The disclosure of this specification includes the following medical system, its control method, and program. (Item 1) A medical system having an electronic medical record terminal and an imaging device having an imaging means, a photographer identification means for identifying a photographer of the imaging device; an acquiring means for acquiring patient information related to a patient whose medical record information is displayed on the electronic medical record terminal being operated by the photographer identified by the photographer identifying means; and a means for associating an image of the affected area obtained by the imaging means with the patient information obtained by the acquisition means. A medical system characterized by: (Item 2) 2. The medical system according to item 1, further comprising a transmitting means for transmitting an image of the affected area captured by the imaging means and patient information acquired by the acquiring means to an image management device in association with each other. (Item 3) 3. The medical system according to claim 1, further comprising a patient information transmission unit that transmits the patient information acquired by the acquisition unit to the imaging device. (Item 4) 4. The medical system according to item 3, wherein the imaging device has a recording means for recording the transmitted patient information and an image of the affected area obtained by imaging by the imaging means in association with each other. (Item 5) the photographer identification means identifies a photographer based on information input by the photographer to the imaging device; The medical system described in item 1, characterized in that the acquisition means identifies a patient whose medical record information is displayed on the electronic medical record terminal being operated by the photographer identified by the photographer identification means, based on information about the photographer identified by the photographer identification means and login information of the electronic medical record terminal, and acquires patient information of the identified patient. (Item 6) 6. The medical system according to item 5, further comprising a management means for associating and managing a user who has successfully logged in to the electronic medical record terminal with a patient whose medical record information is displayed on the electronic medical record terminal. (Item 7) The medical system described in item 6, wherein the acquisition means identifies a patient associated with the same user as the photographer identified by the photographer identification means based on the information managed by the management means, and acquires patient information corresponding to the patient. (Item 8) When the patient information cannot be acquired before the image of the affected area is captured, the acquisition means stores the photographer information identified by the photographer identification means, and acquires the patient information based on the photographer information after the image of the affected area is captured. 8. The medical system according to any one of items 1 to 7, (Item 9) 9. The medical system according to any one of claims 1 to 8, wherein the imaging device images the affected area using the imaging means in response to an instruction to capture an affected area image, generates the affected area image, and links the patient information to the affected area image. (Item 10) The medical system according to any one of claims 1 to 9, further comprising a management device for managing patient chart information and information about medical personnel, and an image management device for managing images of the affected area of ​​the patient. (Item 11) 11. The medical system according to item 10, wherein the photographer identification means identifies the photographer based on information about medical personnel managed by the management device. (Item 12) The medical system described in item 11, characterized in that the electronic medical record terminal performs login authentication based on information about the medical personnel managed by the management device, and controls the management device to display the medical record information managed by the management device if the login authentication is successful. (Item 13) A method for controlling a medical system having an electronic medical record terminal and an imaging device having an imaging means, comprising: a photographer identification step of identifying a photographer of the imaging device; an acquiring step of acquiring patient information related to a patient whose medical record information is displayed on the electronic medical record terminal being operated by the photographer identified by the photographer identifying step; and associating the image of the affected area captured by the imaging means with the patient information acquired by the acquisition step. A control method comprising: (Item 14) A program for causing a computer to execute each step of the control method according to item 13 by reading and executing the program by the computer.

[0243] The invention is not limited to the above-described embodiments, and various modifications and variations are possible without departing from the spirit and scope of the invention. Accordingly, the following claims are appended to apprise the public of the scope of the invention. [Explanation of symbols]

[0244] 101 imaging device, 102 imaging device control device, 103 electronic medical record terminal device, 104 electronic medical record management device, 105 image management device, 106 network

Claims

1. A medical system having an electronic medical record terminal and an imaging device having an imaging means, a photographer identification means for identifying a photographer of the imaging device; an acquiring means for acquiring patient information related to a patient whose medical record information is displayed on the electronic medical record terminal being operated by the photographer identified by the photographer identifying means; and a means for associating an image of the affected area obtained by the imaging means with the patient information obtained by the acquisition means. A medical system characterized by:

2. 2. The medical system according to claim 1, further comprising a transmission means for transmitting the image of the affected area captured by said imaging means and the patient information acquired by said acquisition means in association with each other to an image management device.

3. The medical system according to claim 1 , further comprising a patient information transmitting unit that transmits the patient information acquired by the acquiring unit to the imaging device.

4. 4. The medical system according to claim 3, wherein the imaging device further comprises a recording unit that records the transmitted patient information and an image of the affected area obtained by imaging using the imaging unit in association with each other.

5. the photographer identification means identifies a photographer based on information input by the photographer to the imaging device; The medical system according to claim 1, characterized in that the acquisition means identifies a patient whose medical record information is displayed on the electronic medical record terminal being operated by the photographer identified by the photographer identification means, based on information about the photographer identified by the photographer identification means and login information of the electronic medical record terminal, and acquires patient information of the identified patient.

6. 6. The medical system according to claim 5, further comprising a management means for managing a user who has successfully logged in to the electronic medical record terminal and a patient whose medical record information is displayed on the electronic medical record terminal in association with each other.

7. The medical system according to claim 6, characterized in that the acquisition means identifies a patient associated with the same user as the photographer identified by the photographer identification means based on the information managed by the management means, and acquires patient information corresponding to the patient.

8. When the patient information cannot be acquired before the image of the affected area is captured, the acquisition means stores the photographer information identified by the photographer identification means, and acquires the patient information based on the photographer information after the image of the affected area is captured. The medical system according to claim 1 .

9. The medical system according to claim 1 , wherein the imaging device images the affected area using the imaging means in response to an instruction to capture an affected area image, generates the affected area image, and links the patient information to the affected area image.

10. 2. The medical system according to claim 1, further comprising: a management device for managing medical record information of patients and information on medical staff; and an image management device for managing images of affected areas of patients.

11. 11. The medical system according to claim 10, wherein the photographer identifying means identifies the photographer based on information about medical staff managed by the management device.

12. The medical system described in claim 11, characterized in that the electronic medical record terminal performs login authentication based on information regarding the medical personnel managed by the management device, and controls the display of the medical record information managed by the management device upon successful login authentication.

13. A method for controlling a medical system having an electronic medical record terminal and an imaging device having an imaging means, comprising: a photographer identification step of identifying a photographer of the imaging device; an acquiring step of acquiring patient information related to a patient whose medical record information is displayed on the electronic medical record terminal being operated by the photographer identified by the photographer identifying step; and associating the image of the affected area captured by the imaging means with the patient information acquired by the acquisition step. A control method comprising:

14. A program for causing a computer to execute each step of the control method according to claim 13 by reading and executing the program.

Images