Imaging device, control method for imaging device, and program

Abstract

This aims to reduce the workload of administrators who associate image data of subjects with information about those subjects. [Solution] An imaging device 110 configured to communicate with a medical information system management device 120 acquires a list containing subject reception information from the medical information system management device 120, identifies a predetermined reception information from the acquired list, and performs control to associate the identified predetermined reception information with the image data of the subject in that predetermined reception information and store it.

Description

Technical Field

[0001] The present invention relates to an imaging device, a control method for an imaging device, and a program.

Background Art

[0002] Conventionally, an imaging system that captures (images) an image of a target part of a subject (for example, an affected part of a patient) to record the progress or assist in diagnosis is known. For example, Patent Document 1 describes a technique for attaching information based on the state of an affected part of a subject (for example, the chief complaint of a patient or the findings of a photographer) to image data generated by imaging processing.

[0003] In addition, a medical information processing system that manages a series of operations from patient reception to examination and billing, and manages a series of business data so that the data can be effectively utilized later is also known. For example, Patent Document 2 describes a technique for updating the status of an electronic medical record of a patient to "received" based on the patient reception information required for the visit, and generating new medical fee details data based on the above-described reception information.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] In medical settings and similar environments, administrators need to perform certain tasks to manage image data obtained by imaging patients by associating it with information about those patients (such as their names). The technology described in Patent Document 1 required administrators to identify patients by referring to patient registration information as needed and then associate the patient information with the image data, which was a relatively time-consuming process. Furthermore, the technology described in Patent Document 2 did not include the management of patient image data as part of the overall workflow, and effective management, including the image data of the subjects, required a relatively time-consuming process by administrators, similar to that described in Patent Document 1.

[0006] This invention has been made in view of these problems, and aims to reduce the workload of administrators who perform the task of associating image data of a subject with information related to that subject. [Means for solving the problem]

[0007] The imaging device of the present invention is an imaging device configured to communicate with a management device, and includes: an acquisition means for acquiring a list containing subject reception information from the management device; an identification means for identifying predetermined reception information from the list acquired by the acquisition means; and a storage control means for performing control to store in association the predetermined reception information identified by the identification means and the image data of the subject in the predetermined reception information. [Effects of the Invention]

[0008] According to the present invention, the workload of administrators who perform the task of associating image data of a subject with information related to that subject can be reduced. [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example of a schematic configuration of the imaging system according to the first embodiment. [Figure 2] This figure shows an example of the hardware configuration of the imaging device according to the first embodiment. [Figure 3] This figure shows an example of the hardware configuration of a medical information system management device according to the first embodiment. [Figure 4] This figure shows an example of the external configuration of the imaging device according to the first embodiment, as viewed from the rear. [Figure 5] This figure shows an example of a list of medical management information managed by a medical information system management device according to the first embodiment. [Figure 6] This flowchart shows an example of a processing procedure in the control method for the imaging device according to the first embodiment. [Figure 7] This flowchart shows a first embodiment and is an example of a detailed processing procedure in step S601 of Figure 6. [Figure 8] This figure shows an example of a display screen that can be displayed on the display unit (display) in the imaging device according to the first embodiment. [Figure 9] This flowchart shows a first embodiment and is an example of a detailed processing procedure in step S603 of Figure 6. [Figure 10] This figure shows an example of a display screen that may be displayed on the display unit (display) in the imaging device according to the second embodiment. [Figure 11] This flowchart shows a second embodiment and is an example of a detailed processing procedure in step S603 of Figure 6. [Figure 12] This figure shows an example of a display screen that may be displayed on the display unit (display) in the imaging device according to the third embodiment. [Figure 13] This flowchart shows a third embodiment and is an example of a detailed processing procedure in step S603 of Figure 6. [Figure 14] This flowchart shows an example of a processing procedure in the control method for an imaging device according to the fourth embodiment. [Figure 15] Figure 1 shows a patient's queue number ticket and an example of the display screen shown on the medical information system terminal in the waiting room when the patient is called into the examination room.

Best Mode for Carrying Out the Invention

[0010] Hereinafter, embodiments (implementation forms) for carrying out the present invention will be described with reference to the drawings. Note that each of the embodiments described below does not limit the present invention according to the claims. Furthermore, not all of the plurality of features described in each embodiment are essential to the present invention, and the plurality of features may be arbitrarily combined. Also, in the drawings, the same or similar components are given the same reference numerals, and duplicate explanations are omitted.

[0011] (First Embodiment) First, the first embodiment will be described.

[0012] In this embodiment, as an example, an imaging system used for photographing (imaging) a target site of a subject (for example, an affected part of a patient) at a medical site and assisting medical diagnosis will be described. For example, the imaging system of this embodiment uses a reception number, which is reception information described on a reception number ticket distributed at the time of patient reception, for a doctor to photograph (image) the affected part of the patient. Then, for example, the imaging system of this embodiment is used to attach and store patient information including the reception number (reception information) and doctor information of the doctor who is the photographer as imaging information (metadata) to the image data of the affected part of the patient obtained by photographing.

[0013] FIG. 1 is a diagram showing an example of the schematic configuration of an imaging system 100 according to the first embodiment. The imaging system 100 shown in FIG. 1 is an application of a medical imaging system as an example of this embodiment. The imaging system 100 shown in FIG. 1 includes a function as an information system that performs processing such as associating information related to a patient P and a reception number (for example, a reception number ticket P2 held by the patient P) with the image data obtained by photographing.

[0014] As shown in FIG. 1, the imaging system 100 includes an imaging device 110, a medical information system management device 120, a medical information system terminal device 130, a data management device 140, a photographing system control device 150, and a network 160.

[0015] The imaging device 110 is an imaging device configured to be communicable with the medical information system management device 120, the medical information system terminal device 130, the data management device 140, and the photographing system control device 150 via a communication line 111 and the network 160. The imaging device 110, for example, photographs (images) a diseased part P1 of a patient P who is a subject to generate image data. In the present embodiment, it is assumed that the image data obtained by the imaging device 110 through photographing (imaging) is visible light image data. That is, in the present embodiment, an imaging device (digital camera) capable of photographing visible light is applied as the imaging device 110. However, in the present invention, the type of the imaging device is not particularly limited. Other examples of the imaging device 110 include a multi-spectral camera capable of photographing different wavelength regions according to diagnostic purposes and photographing purposes, a polarization camera having a polarizer that transmits only light vibrating in a certain direction, an infrared camera capable of photographing from infrared to near-infrared regions, and the like. Further, other examples of the imaging device 110 include a three-dimensional shape measurement camera capable of photographing a three-dimensional shape, a microscope-type camera, a dermoscope (skin magnifier)-type camera, a camera having a plurality of photographing functions, and the like. Also, similar to a commercially available digital camera, the imaging device 110 is a portable small-sized imaging device, and is provided with a display device capable of confirming the photographed image and an interface such as buttons and a touch panel for various operations.

[0016] The medical information system management device 120 is a management device configured to communicate with the imaging device 110, the medical information system terminal device 130, the data management device 140, and the imaging system control device 150 via the network 160. The medical information system management device 120 stores patient information of patient P (ID, name, medical department, age, gender, reception number, reception status, medical history, lesions, etc.) and physician information (ID, name, affiliation information such as medical department, biometric authentication information that can identify the individual, information of the examination room the physician is currently in, etc.). The medical information system management device 120 also verifies and authenticates the physician's login / logoff information entered into the medical information system terminal device 130. Furthermore, the medical information system management device 120 can provide physician information to the medical information system terminal device 130 and provide patient information to the medical information system terminal device 130 in the form of an electronic medical record. Furthermore, the medical information system management device 120 stores, in association with each physician, the time when physician information and patient information were provided to the medical information system terminal device 130, and the time when patient P was called from the waiting room to the examination room using a reception number, in order to manage operation information for each physician. In addition, the medical information system management device 120 stores, in association with each physician, the time spent viewing the patient information provided to the medical information system terminal device 130 (the time until the displayed patient information is closed), and the screen display of that patient information (specified examination date, etc.). The medical information system management device 120 can also store data updated by the medical information system terminal device 130. This medical information system management device 120 can be implemented as a personal computer (PC), a hospital server, or a cloud server.

[0017] The medical information system terminal device 130 is a terminal device configured to communicate with the imaging device 110, the medical information system management device 120, the data management device 140, and the imaging system control device 150 via the network 160. The medical information system terminal device 130 is a terminal device used by doctors to download a list of patients P waiting in the waiting room from the medical information system management device 120 and to check their reception status (checked in, called, paid for, etc.) when a doctor is examining a patient P. Furthermore, the medical information system terminal device 130 has a function to call a designated patient P to the examination room, for example by displaying the patient P on a display in the waiting room. In addition, the medical information system terminal device 130 has an electronic medical record function that downloads the doctor's information of the logged-in doctor and the patient P to be examined from the medical information system management device 120, and enables the display, editing, and updating of the electronic medical record.

[0018] The data management device 140 is a management device configured to communicate with the imaging device 110, the medical information system management device 120, the medical information system terminal device 130, and the imaging system control device 150 via the network 160. The data management device 140 is a management device that can store, update, and delete image data, as well as physician information, which is the photographer information associated with the image data, and patient information, which is the patient P and the reception status associated with the patient P. Furthermore, the data management device 140 is a management device that can store, update, and delete consultation schedule information, which associates physicians, patient P, consultation rooms, and the location and time of the consultation rooms. In addition, the data management device 140 is a management device that can store, update, and delete equipment reservation management information, which associates equipment such as the imaging device 110 with the medical departments that hold it and the physicians scheduled to use it. Furthermore, the data management device 140 is also equipped with data search functions as needed.

[0019] The imaging system control device 150 is a control device configured to communicate with the imaging device 110, the medical information system management device 120, the medical information system terminal device 130, and the data management device 140 via the network 160. The imaging system control device 150 acquires the aforementioned physician information and patient information from the medical information system terminal device 130 and transmits the acquired information to the imaging device 110. The imaging device 110 reads information that indirectly identifies the patient P and the physician and transmits the read information to the imaging system control device 150. Here, information that indirectly identifies the patient P and the physician refers to information that identifies the physician and patient P obtained by analyzing or decrypting information that includes encryption such as one-dimensional codes, two-dimensional codes, and RFID, whose content is not immediately apparent. In this case, RFID is an abbreviation for "Radio Frequency Identification." For example, patient information is information printed or embedded on the registration slip or wristband, and physician information is information printed or embedded on the physician's license. Furthermore, when imaging the affected area P1 of patient P, the imaging device 110 can associate and store the image data obtained by imaging with physician information and patient information transmitted from the imaging system control device 150. Subsequently, the imaging system control device 150 detects various events such as imaging events of the imaging device 110 and receives various information associated with the image data obtained by imaging. The imaging system control device 150 then transmits the received image data and other various information (including data) to the medical information system terminal device 130 and the data management device 140.

[0020] In Figure 1, the imaging device 110, medical information system management device 120, medical information system terminal device 130, data management device 140, and imaging system control device 150 are shown as separate devices. However, this embodiment is not limited to the configuration shown in Figure 1. The functions of two or more devices shown in Figure 1 may be realized in a single device. For example, at least a part of the medical information system management device 120, medical information system terminal device 130, data management device 140, and imaging system control device 150 may be constructed in the same housing (device). Alternatively, for example, the imaging device 110 may be configured to have the functions of the imaging system control device 150. Therefore, the imaging device 110 in this embodiment may include the imaging system control device 150, as long as it is not technically contradictory. In this way, a system with an appropriate cost can be configured to match the load and capacity required by the imaging system 100. Furthermore, the above examples are not limited to those described above, as long as it is possible to send and receive information (including data) between the imaging device 110, the medical information system management device 120, the medical information system terminal device 130, the data management device 140, and the imaging system control device 150. For example, the connection between the imaging device 110 and the network 160 may be via a wired communication line 111.

[0021] Network 160 is a communication network that enables communication between the imaging device 110, the medical information system management device 120, the medical information system terminal device 130, the data management device 140, and the imaging system control device 150. For example, when the imaging device 110 is powered on by the operator, it connects to network 160 via communication line 111, and becomes able to communicate with other devices within the imaging system 100 via network 160. Network 160 performs wireless and wired data transmission, as well as various control functions. The communication protocol used for communication via network 160 is not particularly limited, but examples include HTTP (Hypertext Transfer Protocol) and FTP (File Transfer Protocol). Other examples of the above-mentioned communication protocols include PTP (Picture Transfer Protocol), USB (Universal Serial Bus), and LAN (Local Area Network). Furthermore, other examples of the above-mentioned communication protocols include HL7 (Health Level Seven) and DICOM (Digital Imaging and Communications in Medicine). In this embodiment, any communication protocol may be used as long as it enables the communication of image data, text, control data, etc.

[0022] In this embodiment, each device of the imaging system 100, including the imaging device 110, will maintain a state where communication is possible until the power is turned off. Furthermore, although the above description details the connection and communication method between the imaging device 110 and the network 160, the same applies to the connection and communication method of each device of the imaging system 100. That is, the same applies to the connection and communication method of each device of the imaging system 100, such as the medical information system management device 120, the medical information system terminal device 130, the data management device 140, and the imaging system control device 150. In addition, although not shown in Figure 1, if necessary, an illumination device consisting of halogen lighting or light-emitting diode lighting may be installed in conjunction with the imaging device 110 for imaging.

[0023] Figure 2 shows an example of the hardware configuration of the imaging device 110 according to the first embodiment. Using Figure 2, a digital still camera operating as an example of the imaging device 110 will be described.

[0024] As shown in Figure 2, the imaging device 110 includes an imaging unit 201, a CPU 202, a ROM 203, a RAM 204, a display unit 205, an input unit 206, a media drive 207, a network interface 208, an image processing unit 209, a file generation unit 210, and a bus 211.

[0025] The imaging unit 201 uses a solid-state image sensor to read an optical image of the affected area P1 of the patient P, which is the subject, and generates electrical image data by converting it from analog to digital.

[0026] The CPU 202 is a processor that performs overall control of the imaging device 110 and various processing in the imaging device 110 by executing programs stored in the ROM 203, for example.

[0027] The ROM (Read Only Memory) 203 stores programs executed by the CPU 202, as well as various information (including data) used by the CPU 202 when controlling the entire imaging device 110 and performing various processing tasks.

[0028] The RAM (Random Access Memory) 204 functions as the main memory (primary temporary storage) of the CPU 202. The main memory of the CPU 202 may be a different storage unit from the RAM 204. For example, the main memory may be composed of a non-volatile memory device such as an EEPROM (Electrically Erasable Programmable Read-Only Memory). Another example of the CPU 202's main memory is the use of a file area or virtual memory area of ​​an external storage device (not shown) connected via a network 160 or the like. Programs are loaded into the RAM 204 from the ROM 203, and the programs loaded into the RAM 204 are executed by the CPU 202. The RAM 204 also provides a work area for the CPU 202 when performing various processes.

[0029] The display unit 205 displays various information based on the control of the CPU 202. For example, the display unit 205 displays various information (including data) stored in the ROM 203, RAM 204, or media drive 207. The display unit 205 also displays live view images captured by the imaging unit 201, captured images taken by the imaging unit 201 in response to a shooting command being input by operating the release button included in the input unit 206, and various setting screens.

[0030] The input unit 206 includes buttons, etc., for the photographer (physician) to perform various operations. Here, buttons, etc., are, for example, the release button located on the top of the imaging device 110, and the directional keys and setting keys located on the back. The touch panel etc. provided on the display unit 205 is also included in the input unit 206. The photographer (physician) can input various instructions to the imaging device 110 by operating the input unit 206.

[0031] The media drive 207 includes a mounting section for attaching a removable storage medium to the imaging device 110. The media drive 207 is configured to store various types of information (including data) on the storage medium and to read out the stored information (including data).

[0032] The network interface (network I / F) 208 is an interface for communication via the communication line 111 and the network 160. The imaging device 110 sends and receives various information (including data) to and from external devices (120-150) via the network I / F 208. Here, the communication line 111 is a wired or wireless communication line. The imaging device 110 is connected to the network 160 via the communication line 111.

[0033] The image processing unit 209 performs image processing on the image data of the affected area P1 of patient P, which is the subject captured (imaged) by the imaging unit 201. The CPU 202 temporarily stores the image data and its attribute information generated by the imaging unit 201 in the RAM 204. The image processing unit 209 then performs a series of image processing operations as needed to obtain image data suitable for the purpose of acquisition, such as data containing human visual characteristics data, three-dimensional data, or both. Furthermore, if the processing load is large, the image processing unit 209 may divide the data processing and share the processing with the imaging system control device 150.

[0034] The file generation unit 210 generates various image files. For example, the file generation unit 210 converts image data of the affected area P1 of patient P, which is the subject, into a general-purpose still image format to generate an image file.

[0035] Bus 211 connects the imaging unit 201, CPU 202, ROM 203, RAM 204, display unit 205, input unit 206, media drive 207, network interface 208, image processing unit 209, and file generation unit 210 so that they can communicate with each other. Here, bus 211 is a system bus that includes an address bus, a data bus, a control bus, etc.

[0036] Figure 3 shows an example of the hardware configuration of the medical information system management device 120 according to the first embodiment. Using Figure 3, a computer operating as an example with the medical information system management device 120 will be described. In this case, the computer may be located and function on a server such as a local network or cloud. In this embodiment, Figure 3 is described as the hardware configuration of the medical information system management device 120, but it may also be the hardware configuration of the medical information system terminal device 130 or the imaging system control device 150, as long as there is no technical inconsistency.

[0037] As shown in Figure 3, the medical information system management device 120 includes a CPU 301, ROM 302, RAM 303, display unit 304, HDD 305, input unit 306, media drive 307, network I / F 308, and bus 309.

[0038] The CPU 301 is a processor that performs overall control of the medical information system management device 120 and various processing tasks within the medical information system management device 120 by executing programs stored, for example, in the ROM 302 or HDD 305.

[0039] ROM302 stores programs executed by CPU301, as well as various information (including data) used by CPU301 when controlling the medical information system management device 120 as a whole and performing various processes.

[0040] RAM303 functions as the main memory of CPU301. Programs are loaded into RAM303 from ROM302 or HDD305, and the programs loaded into RAM303 are executed by CPU301. RAM303 also provides a work area for CPU301 to perform various processes.

[0041] The display unit 304 displays various information based on the control of the CPU 301. For example, the display unit 304 displays information on a screen installed in the waiting room of a hospital to call patient P into the examination room.

[0042] The HDD (hard disk drive) 305 stores, as needed, programs executed by the CPU 301, and various information (including data) used by the CPU 301 when controlling the medical information system management device 120 as a whole and performing various processes. The HDD (hard disk drive) 305 also stores various information (including data) obtained by the CPU 301 when controlling the medical information system management device 120 as a whole and performing various processes.

[0043] The input unit 306 includes a pointing device, a keyboard, and the like.

[0044] The media drive 307 includes a mounting section for attaching a removable storage medium to the medical information system management device 120. The media drive 307 is configured to store various types of information (including data) on the storage medium and to read out the stored information (including data).

[0045] The network interface (network I / F) 308 is an interface for communication via the network 160. The medical information system management device 120 sends and receives various information (including data) to and from external devices (110, 130~150) via the network I / F 308. In this embodiment, the medical information system management device 120 communicates with the imaging device 110 via the network I / F 308 and sends and receives various information (including data) to and from the imaging device 110. The medical information system management device 120 also communicates with the medical information system terminal device 130 via the network I / F 308 and sends and receives various information (including data) to and from the medical information system terminal device 130. Here, examples of communication between the medical information system management device 120 and the medical information system terminal device 130 include communication of a list of patients P who have completed registration and are waiting in the waiting room, and communication of the result of calling a designated patient P into the examination room. Furthermore, the medical information system management device 120 communicates with the data management device 140 via the network I / F 308 and obtains patient information and physician information associated with the patient number (reception number) of the patient P who has completed registration from the data management device 140. The medical information system management device 120 may also obtain patient ID, physician ID, and consultation schedule information from the data management device 140 as the patient information and physician information to be obtained.

[0046] Bus 309 connects the CPU 301, ROM 302, RAM 303, display unit 304, HDD 305, input unit 306, media drive 307, and network interface 308 so that they can communicate with each other. Here, bus 309 is a system bus that includes an address bus, data bus, control bus, etc.

[0047] Figure 4 shows an example of the external configuration of the imaging device 110 according to the first embodiment, viewed from the rear. Details of the various buttons and user interface of the imaging device 110 will be explained using Figure 4.

[0048] As shown in Figure 4, the imaging device 110 has a power button 401, a shutter release button 402, an up button 403, a right button 404, a down button 405, a left button 406, a select button 407, and a display 410. Here, the power button 401, shutter release button 402, up button 403, right button 404, down button 405, left button 406, and select button 407 shown in Figure 4 are one component of the input unit 206 shown in Figure 2. The display 410 is also one component of the display unit 205 and input unit 206 shown in Figure 2. In the following description, all buttons except the power button 401 shown in Figure 4 will be described in terms of their operation when the imaging device 110 is powered on.

[0049] The power button 401 is a button that switches the power of the imaging device 110 ON / OFF. When the imaging device 110 is not powered on, if the photographer (doctor) presses the power button 401, the CPU 202 determines that the photographer (doctor) has instructed the operator to turn the power ON and processes the operation to turn on the power of the imaging device 110. Conversely, when the imaging device 110 is powered on, if the photographer (doctor) presses the power button 401, the CPU 202 determines that the photographer (doctor) has instructed the operator to turn the power OFF and processes the operation to turn off the power of the imaging device 110.

[0050] The release button 402 is a button that instructs the imaging unit 201 to take a picture (image). When the photographer (doctor) presses the release button 402, the CPU 202 determines that, for example, a still image has been instructed to be taken.

[0051] When the photographer (doctor) presses any of the up direction button 403, right direction button 404, down direction button 405, or left direction button 406, the CPU 202 determines that the photographer (doctor) has instructed the camera to switch the selected target. The CPU 202 then performs a process to switch the display of the selected target on the display 410 according to the direction button (403-406) that was pressed.

[0052] When the photographer (doctor) presses the confirmation button 407, the CPU 202 determines that a confirmation instruction has been given by the photographer (doctor), stores the set information in the RAM 204, and performs processing to set the state of the imaging device 110 based on the set information.

[0053] The display 410 performs various displays based on the control of the CPU 202. The display 410 has the display function of the display unit 205 shown in Figure 2 and the touch panel input function of the input unit 206 shown in Figure 2. In the display 410 shown in Figure 4, an image based on image data of the affected area P1 of patient P, the subject, is displayed in the central area. The display 410 shown in Figure 4 is also provided with a patient information display unit 411, a shooting date display unit 412, a photographer information display unit (doctor information display unit) 413, an OK button 414, a cancel button 415, and an exit button 416. For example, if the photographer (doctor) touches any point on the display 410 with their finger, the CPU 202 determines that there has been an input instruction from the photographer (doctor), determines the content of the input instruction from the touched position, and performs various processes such as display updates and setting updates.

[0054] The patient information display unit 411 is an area that displays patient information, which is information related to patient P. In the example shown in Figure 4, the patient information display unit 411 displays the patient's name, gender, and age as patient information. In this embodiment, the patient information displayed in the patient information display unit 411 is received from the medical information system management device 120.

[0055] The shooting date display section 412 is an area that displays the shooting date on which the image of the affected area P1 of patient P was taken.

[0056] The photographer information display unit 413 is an area that displays photographer information (physician information), which is information about the photographer (physician). In the example shown in Figure 4, the photographer information display unit 413 displays the photographer's (physician's) name and the name of the examination room indicating the location of the photograph as photographer information (physician information). In this embodiment, the photographer information (physician information) displayed in the photographer information display unit 413 is received from the medical information system management device 120.

[0057] The OK button 414 is the button that the photographer (doctor) operates to approve the current settings.

[0058] The cancel button 415 is used by the photographer (doctor) to cancel the current settings.

[0059] The end button 416 is the button that the photographer (doctor) operates when they want to end the process.

[0060] In the display 410 shown in Figure 4, patient information is displayed in the patient information display unit 411, photographer information (physician information) is displayed in the photographer information display unit 413, and an image based on image data of the affected area P1 of patient P, the subject of the photograph, is displayed in the central area, thus creating an overlaid display. By performing such an overlaid display on the display 410 shown in Figure 4, the photographer (physician) can avoid making mistakes in associating patient information with the patient P being photographed. The information displayed on the display 410 may be switched according to the operational status and priority within the hospital.

[0061] Figure 5 shows an example of a medical management information list 500 managed by the medical information system management device 120 according to the first embodiment. The data of the medical management information list 500 shown in Figure 5 is stored and managed, for example, on the HDD 305 of the medical information system management device 120. In this embodiment, it is assumed that the medical management information list 500 shown in Figure 5 is collected and managed by the medical information system management device 120 from the data management device 140. In addition to the information listed in the medical management information list 500 shown in Figure 5, it is also conceivable to manage information on various processing times by doctors, such as the time when patients are called from the waiting room, the start / end times of consultations, the start / end times of imaging, and the time when electronic medical records are updated.

[0062] Identification number (No.) information 501 indicates header name information representing a unique sequential number used to identify data in medical management information list 500.

[0063] Consultation date information 502 shows the header name information representing the consultation date of patient P.

[0064] The reception number information 503 indicates the header name information representing the reception number issued on the diagnosis date described in the consultation date information 502. The medical information system management device 120 issues and manages reception numbers for each patient P that is received. In this embodiment, the reception number described in the reception number information 503 is assumed to be a unique sequential number only for that day. Therefore, combining the consultation date information 502 and the reception number information 503 results in unique data. Depending on the hospital's reception management status, it may also be possible to create unique data by combining the consultation date information 502 and the reception number information 503 with the department information 508 described later.

[0065] User ID (Patient ID) information 504 indicates the header name information representing the User ID (Patient ID) used to uniquely identify Patient P.

[0066] Patient name information 505 indicates the header name information representing the patient name associated with user ID (patient ID) information 504.

[0067] Gender information 506 indicates the header name representing gender, which is associated with user ID (patient ID) information 504.

[0068] The birth date information 507 indicates the header name information representing the birth date associated with the user ID (patient ID) information 504.

[0069] The department information 508 indicates the header name information representing the department associated with the user ID (patient ID) information 504. Specifically, the department information 508 indicates the information of the department to which patient P was admitted. In this embodiment, the medical management information list 500 shown in Figure 5 manages the department information 508 as a string, but it may also be managed as a number such as a department ID.

[0070] The examination room information 509 indicates the header name information representing the examination room where patient P will receive treatment. In the medical management information list 500 shown in Figure 5, examination rooms are managed as a single location in the examination room information 509, but this embodiment is not limited to this. For example, if patient P has to move between multiple examination rooms, multiple examination room information may be managed as examination room information 509, separated by commas, or the information may be managed by overwriting and updating so that only the most recent examination room information remains.

[0071] The physician ID information 510 indicates the header name information representing the physician ID used to uniquely identify the physician who will be treating patient P.

[0072] The physician name information 511 indicates the header name information representing the physician's name associated with the physician ID information 510.

[0073] Status information 512 indicates the header name information representing the reception status of patient P. In this embodiment, status information 512 first shows a status indicating reception completed when patient P has completed registration, then shows a status indicating called when the doctor calls patient P into the examination room. Finally, status information 512 shows a status indicating paid when patient P has completed payment. Note that status information 512 is not limited to the types of statuses described above, and statuses may be managed in cooperation with a medical information system terminal device 130 (e.g., an electronic medical record terminal device). For example, after a doctor calls patient P from the waiting room, if the medical record data of patient P is updated in the medical information system terminal device 130, the status may be updated to indicate waiting for payment.

[0074] Medical management information 513 indicates that patient P, Akira Toriyama, registered at the dermatology department on December 21, 2023, under registration number 58, was examined by physician Takashi Sato in examination room 1, and paid the bill (status information 512 indicates payment completed).

[0075] Medical management information 514 indicates that patient P, Taro Shimomaruko, was registered with the plastic surgery department on December 21, 2023, under registration number 59, and was called to the imaging room by physician Hanako Kawasaki (status information 512 indicates "called").

[0076] Medical management information 515 indicates that patient P, Hanako, was registered at the dermatology department on December 21, 2023, with registration number 60, and was called to examination room 1 by physician Takashi Sato (status information 512 indicates "called").

[0077] Medical management information 516 indicates that patient P, Jiro Tanaka, registered at the dermatology department on December 21, 2023, as registration number 61, and is waiting in the waiting room until he is called to examination room 1 by physician Takashi Sato (status information 512 indicates registration completed).

[0078] Medical management information 517 indicates that patient P, Saburo Sato, registered with the plastic surgery department on December 21, 2023, under registration number 62, and waited in the waiting room until he was called to examination room 2 by physician Emi Kamata (status information 512 indicates registration completed).

[0079] Medical management information 518 indicates that patient P, Shiro Kato, registered at the dermatology department on December 21, 2023, with registration number 63, and is waiting in the waiting room until he is called into examination room 1 by physician Takashi Sato (status information 512 indicates registration completed).

[0080] Figure 6 is a flowchart showing an example of a processing procedure in the control method of the imaging device 110 according to the first embodiment. Figure 6 also shows an example of a display screen that is displayed on the display 410 of the imaging device 110 in some processing steps.

[0081] The imaging process performed by the imaging unit 201 of the imaging device 110 is carried out, for example, to record the condition of the affected area P1 in a patient P's injury or illness. In the following description, the person taking the image is assumed to be a physician, but it may also be a technician, assistant, or nurse designated by the physician. Prior to performing the imaging process, the physician taking the image is assumed to have logged in to the medical information system terminal device 130 (e.g., an electronic medical record terminal device). When the physician logs in to the medical information system terminal device 130, the medical information system terminal device 130 obtains patient information and physician information from the medical information system management device 120. At this time, the patient information includes ID (504), name (505), medical department (508), age, gender (506), reception number (503), reception status (512), medical history, lesions, etc. Furthermore, physician information includes ID (510), name (511), department affiliation information (508, 509), personally identifiable biometric authentication information, and information about the examination room the physician is currently in. The medical information system terminal device 130 can display the electronic medical record based on the information (patient information and physician information) obtained from the medical information system management device 120. Once the physician has finished displaying the electronic medical record and is ready for the examination, the physician uses the medical information system terminal device 130 (for example, a patient calling terminal device) to call patient P who is waiting in the waiting room. The medical information system terminal device 130 displays a predetermined message on the waiting room display to call patient P into the examination room. The medical information system terminal device 130 then reflects the result of calling patient P into the examination room in the medical management information list 500 (for example, status information 512) managed by the medical information system management device 120. This allows for filtering of patient information and other processing to be performed on the imaging device 110, which will be described later.

[0082] Unless otherwise specified, the processing performed by the imaging device 110 is achieved by the CPU 202 of the imaging device 110 executing a program stored, for example, in the ROM 203. The timing for executing the processing shown in the flowchart in Figure 6 is when the power of the imaging device 110 is turned ON, when the imaging device 110 wakes up from sleep mode (power saving mode), when the stop button 416 is pressed, or when a new imaging of the affected area P1 is started. Furthermore, for example, the processing described below as being performed by the imaging device 110 may be performed by other devices such as the imaging system control device 150 or the medical information system terminal device 130, if technically possible. Moreover, multiple devices in the imaging system 100 may perform the same processing. For example, the processing described below as being performed by the imaging device 110 may be performed by both the imaging device 110 and the imaging system control device 150, if technically possible.

[0083] When the flowchart shown in Figure 6 is initiated, the process first proceeds to step S601. When the process proceeds to step S601 in Figure 6, the CPU 202 and other components of the imaging device 110 acquire various information for the first display mode (reception number selection mode) from the medical information system management device 120, as shown in the display screen 610, and display it on the display 410. The display screen 610 shown in Figure 6 corresponds to the display screen 610 in Figure 8(a), which will be described later, and is designed to accept button selection operations by the photographer (doctor). In this embodiment, the detailed processing of step S601 in Figure 6 will be described later with reference to Figure 7.

[0084] When the CPU 202 detects an operation by the photographer (doctor) on the display screen 610 shown in Figure 6, it proceeds to step S602. When the process proceeds to step S602 in Figure 6, the CPU 202 of the imaging device 110 determines whether the imaging preparation is OK (ready). In this embodiment, the imaging preparation is determined to be OK if the display screen 610 has transitioned to the imaging screen, or if all or part of the imaging information, including patient information and physician information to be stored in association with the image data, has been finalized. The imaging information described here may also be interpreted as the medical management information described using Figure 5. The timing at which the imaging information to be associated with the image data is finalized can be a button operation on the imaging device 110 by the photographer (physician) (for example, a patient selection operation). Alternatively, it may be a patient call operation on the medical information system terminal device 130 (for example, a patient calling terminal device), and if the information is finalized at this timing, the operation of the imaging device 110 may be skipped.

[0085] In step S602 of Figure 6, if the CPU 202 of the imaging device 110 determines that the imaging preparation is not OK (S602 / NO), the process proceeds to step S603. When the process proceeds to step S603 in Figure 6, the CPU 202 of the imaging device 110 acquires various information on the display screen 620 in response to the operator's (physician's) operations on the display screen 610 and displays it on the display 410. The display screen 620 shown in Figure 6 corresponds to the display screen 620 in Figure 8(b), which will be described later, and is capable of accepting button selection operations by the operator (physician). In this embodiment, the detailed processing of step S603 in Figure 6 will be described later with reference to Figure 9.

[0086] Once the process in step S603 in Figure 6 is completed, the process proceeds to step S604. When the process proceeds to step S604 in Figure 6, the CPU 202 of the imaging device 110 determines whether the imaging preparation is OK (ready) or not, similar to step S602 in Figure 6. If the CPU 202 of the imaging device 110 determines in step S604 that the imaging preparation is NOT OK (S604 / NO), the process returns to step S601.

[0087] Furthermore, if the CPU 202 of the imaging device 110 determines in step S604 that it is ready for shooting (S604 / YES), the process proceeds to step S605. Additionally, if the CPU 202 of the imaging device 110 determines in step S602 that it is ready for shooting (S602 / YES), the process proceeds to step S605. When the process proceeds to step S605 in Figure 6, the CPU 202 of the imaging device 110 displays at least a portion of the imaging information (such as patient information and physician information) specified in step S601 or step S603 on the display 410. For example, in step S605 in Figure 6, the display screen 630 shown on the display 410 in Figure 4 is displayed. As shown in Figure 4, this display screen 630 displays patient information (name, gender, and age of patient P) displayed on the patient information display unit 411 and photographer information (name of photographer, such as a physician, and location of imaging) displayed on the photographer information display unit 413. The photographer, such as a physician, confirms that the patient P and physician indicated by the imaging information displayed on the display screen 630 match the patient P and photographer themselves. If the patient P and physician indicated by the medical record information do not match the patient P and physician displayed on the display screen 630, the photographer selects the cancel button 415 in Figure 4. The following are possible scenarios in which discrepancies may occur between the patient P and doctor indicated in the medical record information and the patient P and doctor displayed on the display screen 630. For example, a doctor might forget to switch the patient P being displayed in the electronic medical record on the medical information system terminal device 130 (e.g., an electronic medical record terminal device) and then call in a new patient P from the waiting room. Another possibility is that a communication error in the imaging system 100 prevents the correct imaging information from being transmitted to the imaging device 110.

[0088] Next, in step S606 of Figure 6, the CPU 202 of the imaging device 110 performs imaging processing of the affected area P1 of the patient P, which is the subject, in response to the press of the release button 402 by the photographer (doctor). The CPU 202 then temporarily stores the image data obtained from the imaging processing in the RAM 204 or media drive 207. The CPU 202 also adds some or all of the imaging information determined in S602 or S604 to the image data obtained from the imaging processing, and stores the image data and imaging information (including reception information included in patient information) in association with each other in the media drive 207, etc. Here, the method of associating the image data and imaging information is not particularly limited, but the CPU 202 can associate the image data and imaging information by, for example, writing the imaging information to the metadata area of ​​the image data. Alternatively, the CPU 202 may control the file generation unit 210 to generate a metadata file (sidecar file) containing the imaging information, and associate the image data file with the metadata file. By processing the images in this way, the burden of associating patient information about patient P and photographer information about the photographer with the image data obtained by photographing patient P can be reduced.

[0089] Once the process in step S606 in Figure 6 is completed, the process shown in the flowchart in Figure 6 is finished.

[0090] In the flowchart shown in Figure 6, the CPU 202 of the imaging device 110 is assumed to associate imaging information with the image data obtained through the imaging process. However, instead of the CPU 202 of the imaging device 110, the CPU 301 of the imaging system control device 150 may acquire the image data obtained from the imaging device 110 and associate the imaging information with it. In this case, the CPU 301 of the imaging system control device 150 acquires imaging information from the medical information system terminal device 130, but it is not necessary to transmit all of the acquired imaging information to the imaging device 110; only the imaging information to be displayed on the imaging device 110 needs to be transmitted. This reduces the amount of data transmitted.

[0091] Furthermore, the CPU 202 of the imaging device 110 may display a user interface including the acquired image data and a cancellation option in response to the acquisition of image data during the imaging process in step S606 of Figure 6. In this case, the cancellation option is an option that can be selected by the photographer (physician), such as the cancel button 415 shown in Figure 4. If the cancellation option is selected in the displayed user interface, the CPU 202 of the imaging device 110 will stop transmitting the image data to the imaging system control device 150. If a predetermined time has elapsed without the cancellation option being selected in the displayed user interface, the CPU 202 of the imaging device 110 will transmit the image data to the imaging system control device 150. This makes it possible to prevent the imaging system control device 150 from acquiring image data that the photographer (physician) considers unnecessary.

[0092] Furthermore, the CPU 202 of the imaging device 110 can transmit the series of image data processed up to this point to the medical information system terminal device 130 (for example, an electronic medical record terminal device). This may cause the medical information system terminal device 130 to display a user interface for selecting the image data to be stored. Alternatively, the CPU 202 of the imaging device 110 may display the user interface for selecting the image data to be stored on the display unit 205 (display 410). The physician can then confirm the image data on the user interface displayed on the medical information system terminal device 130 or the display unit 205 (display 410) and select the image data to be stored. In such a case, the medical information system terminal device 130 or the CPU 202 of the imaging device 110 can store the selected image data and corresponding imaging information in the data management device 140. In this way, only the image data that is significant to the physician can be selected, saved, and managed from among multiple image data, thereby reducing the time required to search for image data and saving storage space.

[0093] As described above, by appropriately collecting and storing image data and imaging information, it is possible to eliminate the need to connect the imaging device 110 to the data management device 140, or to remove the storage medium from the media drive 207 of the imaging device 110 to collect and organize image data. Furthermore, based on the imaging information, image data can be re-examined at a later date using various search conditions or used in conferences, so physicians can easily access the desired image data.

[0094] Figure 7 shows a first embodiment and is a flowchart illustrating an example of a detailed processing procedure in step S601 of Figure 6. Specifically, Figure 7 is a flowchart illustrating an example of the process for acquiring display data on the display screen 610 of the imaging device 110 and the processing during various button selection operations.

[0095] First, in step S701 of Figure 7, the CPU 202 of the imaging device 110 requests the medical information system management device 120 to provide a medical management information list 500, which includes, for example, the reception number information 503 shown in Figure 5. If a search key is to be used in the request, for example, the data of the clinical department information 508 shown in Figure 5 can be included as the search key when requesting the medical management information list 500, which includes the reception number information 503, from the medical information system management device 120. In addition to the information shown in Figure 5, any information that the medical information system management device 120 can technically manage may also be used as a search key. For example, various processing time data by a physician, such as the time when a patient is called from the waiting room, the start / end times of the consultation, the start / end times of imaging, and the time the electronic medical record is updated, can be used as a search key.

[0096] <Effectiveness of the method for identifying patient P using the reception number> In this embodiment, the imaging device 110 is configured to request a medical management information list 500, including reception number information 503, from the medical information system management device 120. With this configuration, for example, patient P associated with the reception number information 503 in Figure 5 can be identified. Another possible configuration is to identify patient P from the medical record information being viewed by the doctor on the medical information system terminal device 130 (e.g., an electronic medical record terminal device). This method also allows for the identification of patient P during examination while reducing the burden on the doctor. However, with the method of identifying patient P using medical record information being viewed by the doctor, it becomes difficult to easily identify patient P in a room where an electronic medical record terminal device does not exist (for example, an imaging room in a clinic that is not a large hospital). In contrast, with the method of identifying patient P using the reception number information 503 in this embodiment, even in a room where an electronic medical record terminal device does not exist, patient P to be photographed can be identified with a simple operation of selecting the reception number on the imaging device 110 when photographing patient P.

[0097] Next, in step S702 of Figure 7, the CPU 301 of the medical information system management device 120 retrieves, for example, the medical management information 513-518 (including the reception number information 503) shown in Figure 5 from the HDD 305 in response to the list request for reception numbers from the imaging device 110. At this time, if the request from the imaging device 110 includes a search key, the CPU 301 of the medical information system management device 120 retrieves the corresponding medical management information.

[0098] Next, in step S703 of Figure 7, the CPU 301 of the medical information system management device 120 returns the medical management information acquired in step S702 to the imaging device 110. At this time, for example, if no target medical management information exists, the CPU 301 returns information to the imaging device 110 indicating that there were 0 target medical management records.

[0099] Next, in step S704 of Figure 7, the CPU 202 of the imaging device 110 determines whether or not it was able to obtain the medical management information list 500, which includes the reception number information 503, based on the information returned from the medical information system management device 120. For example, if the medical management information 513 to 518 shown in Figure 5 has been obtained, it is determined that the medical management information list 500, which includes the reception number information 503, has been obtained. Note that the medical management information list 500, which includes the reception number information 503, may not be obtained if there are no medical management information entries that include the reception number information 503, or if a communication error, including a timeout error, occurs.

[0100] In step S704 in Figure 7, if the CPU 202 of the imaging device 110 determines that it has been able to obtain the medical management information list 500, which includes the reception number information 503 (S704 / YES), the process proceeds to step S705. When the process proceeds to step S705 in Figure 7, the CPU 202 of the imaging device 110 narrows down the medical management information list 500, which includes the reception number information 503 that it determined to have been acquired in S704, so that it displays the information with the highest display value on the display unit 205 (display 410). Specifically, step S705 describes an example of narrowing down to patient P who has been called (status information 512 indicates called) from the waiting room. Note that depending on the imaging operator, it may be better to narrow down to the medical management information of reception number information 503 associated with a specific doctor using the doctor name information 511, but in that case, the medical management information to be narrowed down should be associated and stored in advance using the settings of the imaging device 110, etc.

[0101] <How to identify the reception number associated with patient P from the status information> The CPU 202 of the imaging device 110 identifies the medical management information list 500 (e.g., medical management information 513-518), which includes the acquired reception number information 503, using the called status information 512. In the medical management information list 500 shown in Figure 5, the status information 512 identifies the called medical management information 514 and 515. By identifying the patient P waiting in the waiting room using the called status information 512 in this way, it becomes unnecessary to display all medical management information on the display unit 205 (display 410) of the imaging device 110 from the beginning. This helps the photographer to smoothly select the desired patient P.

[0102] Next, in step S706 of Figure 7, the CPU 202 of the imaging device 110 displays a list of medical management information, including the reception number information 503 identified in step S705, on the display unit 205 (display 410).

[0103] Figure 8 shows an example of display screens 610 to 630 that can be displayed on the display unit 205 (display 410) in the imaging device 110 according to the first embodiment. In Figure 8, components similar to those shown in Figures 4 and 6 are given the same reference numerals, and their detailed explanations are omitted. Specifically, the display screen 610 shown in Figure 8(a) corresponds to the display screen 610 shown in Figure 6. Also, the display screen 620 shown in Figure 8(b) corresponds to the display screen 620 shown in Figure 6. Also, the display screen 630 shown in Figure 8(c) corresponds to the display screen 630 shown in Figure 6.

[0104] [First display mode (reception number selection mode)] The display screen 610 shown in Figure 8(a) is displayed, for example, during the process in step S706 of Figure 7. Furthermore, the display screen 610 shown in Figure 8(a) is displayed, for example, when the power of the imaging device 110 is turned ON, when the imaging device 110 returns to normal operation from sleep state (power saving state), or when the exit button 416 shown in Figure 4 is pressed. In other words, the display screen 610 shown in Figure 8(a) is displayed when a new image of the affected area P1 of the patient P, which is the subject, is started. The mode in which this display screen 610 shown in Figure 8(a) is displayed corresponds to the first display mode in this embodiment.

[0105] In the display screen 610 shown in Figure 8(a), the update button 801 is operated when re-acquiring a list of medical management information, including reception number information 503, which can be obtained from the medical information system management device 120. In the display screen 610 shown in Figure 8(a), medical management information 802 shows an example of medical management information obtained from the medical information system management device 120. Specifically, medical management information 802 is medical management information corresponding to medical management information 514, for which status information 512 shown in Figure 5 has been called. More specifically, medical management information 802 indicates that patient P, Taro Shimomaruko, whose reception number is 59, has been called to the imaging room by physician Dr. Kawasaki. In the display screen 610 shown in Figure 8(a), medical management information 803 shows an example of medical management information obtained from the medical information system management device 120. Specifically, medical management information 803 is medical management information corresponding to medical management information 515, for which status information 512 shown in Figure 5 has been called. More specifically, medical management information 803 indicates that patient Hanako, patient P with reception number 60, has been called to examination room 1 by physician Dr. Sato. Furthermore, medical management information 803 is accompanied by an icon 807 indicating that patient Hanako, patient P, is being photographed using an imaging device other than the imaging device 110. Medical management information 803 accompanied by the icon 807 indicating that imaging is being performed by another imaging device 110 can be managed by the medical information system management device 120. This is because the imaging device 110 and the medical information system management device 120 are linked, so once patient P to be photographed is determined, the fact that imaging is in progress can be managed in patient P's medical management information along with unique information such as the serial number of the other imaging device. Also, when the end of imaging is detected for patient P (e.g., by pressing the end button 416 or turning off the power), the information indicating that imaging is in progress (including the icon 807) can be deleted from the medical management information. In the display screen 610 shown in Figure 8(a), the "Show All" button 804 is operated to display all patients P currently being accepted. When this "Show All" button 804 is operated, the display screen 620 shown in Figure 8(b) is displayed, and the target patient P can be selected from all patients P currently being accepted.In the display screen 610 shown in Figure 8(a), the manual input button 805 is operated when the photographer (doctor) manually enters the reception number, etc. In the display screen 610 shown in Figure 8(a), the scan button 806 is operated when scanning and entering the reception number, patient ID, etc.

[0106] The display screen 610 shown in Figure 8(a) shows the lists of medical management information 802 and medical management information 803 that are displayed in step S706 of Figure 7.

[0107] Now, let's return to the explanation of Figure 7. If the processing in step S706 in Figure 7 is completed, the process proceeds to step S707. Also, if the CPU 202 of the imaging device 110 determines in step S704 in Figure 7 that it was not able to obtain the medical management information list 500 including the reception number information 503 (S704 / NO), the process proceeds to step S707. When the process proceeds to step S707 in Figure 7, the CPU 202 of the imaging device 110 displays menu buttons that can be operated by the physician on the display unit 205 (display 410). The menu buttons displayed in step S707 correspond to the all-in-one button 804, manual input button 805, and scan button 806 shown in Figure 8(a).

[0108] Next, in step S708 in Figure 7, the CPU 202 of the imaging device 110 determines whether or not the update button 801 shown in Figure 8(a) has been selected. In the event of an abnormality such as a disconnection between the imaging device 110 and the network 160, the system may be configured not to accept the selection of the update button 801 shown in Figure 8(a). In such a case, the system may, for example, gray out the update button 801 shown in Figure 8(a) to make it easier for the photographer to understand. If the CPU 202 of the imaging device 110 determines in step S708 in Figure 7 that the update button 801 shown in Figure 8(a) has been selected (S708 / YES), the system returns to step S701.

[0109] Furthermore, in step S708 of Figure 7, if the CPU 202 of the imaging device 110 determines that the update button 801 shown in Figure 8(a) has not been selected (S708 / NO), the process proceeds to step S709. When the process proceeds to step S709 in Figure 7, the CPU 202 of the imaging device 110 determines whether or not medical management information 802 or medical management information 803 on the display screen 610 shown in Figure 8(a) has been selected.

[0110] In step S709 in Figure 7, if the CPU 202 of the imaging device 110 determines that either medical management information 802 or medical management information 803 on the display screen 610 shown in Figure 8(a) has been selected (S709 / YES), the process proceeds to step S710. If medical management information 802 or medical management information 803 is selected in step S709 (S709 / YES), the patient P of the selected medical management information is confirmed as the patient P to be imaged. When the process proceeds to step S710 in Figure 7, the CPU 202 of the imaging device 110 identifies the selected medical management information reception number information 503 as predetermined reception information. The CPU 202 of the imaging device 110 then temporarily stores the imaging information (which may be interpreted as medical management information) including patient information and physician information of patient P associated with the reception number information 503 identified as predetermined reception information in the RAM 204. The imaging information temporarily stored in the RAM 204 is used to display on the display unit 205 (display 410) in step S605 in Figure 6. The imaging information temporarily stored in the RAM 204 is also associated with the image data obtained in the imaging process in step S606 in Figure 6 and stored in the media drive 207, etc.

[0111] Furthermore, in step S709 in Figure 7, if the CPU 202 of the imaging device 110 determines that medical management information 802 or medical management information 803 on the display screen 610 shown in Figure 8(a) has not been selected (S709 / NO), the process proceeds to step S711. When the process proceeds to step S711 in Figure 7, the CPU 202 of the imaging device 110 determines whether or not the menu buttons (show all button 804, manual input button 805, and scan button 806) on the display screen 610 shown in Figure 8(a) have been selected.

[0112] In step S711 in Figure 7, if the CPU 202 of the imaging device 110 determines that the menu button on the display screen 610 shown in Figure 8(a) has not been selected (S711 / NO), the process proceeds to step S712. When the process proceeds to step S712 in Figure 7, the CPU 202 of the imaging device 110 determines whether or not the cancel button 415 on the display screen 610 shown in Figure 8(a) has been selected. If, in step S712 of Figure 7, the CPU 202 of the imaging device 110 determines that the cancel button 415 on the display screen 610 shown in Figure 8(a) has not been selected (S712 / NO), the process returns to step S708.

[0113] Furthermore, in step S712 of Figure 7, if the CPU 202 of the imaging device 110 determines that the cancel button 415 on the display screen 610 shown in Figure 8(a) has been selected (S712 / YES), the process proceeds to step S713. Also, if the processing in step S710 of Figure 7 is completed, the process proceeds to step S713. When the process proceeds to step S713 in Figure 7, the CPU 202 of the imaging device 110 transitions the display screen of the display unit 205 (display 410) to the shooting screen. The shooting screen here is, for example, the screen displayed on the display 410 as shown in Figure 4.

[0114] Furthermore, in step S711 in Figure 7, if the CPU 202 of the imaging device 110 determines that a menu button on the display screen 610 shown in Figure 8(a) has been selected (S711 / YES), the process proceeds to step S714. When the process proceeds to step S714 in Figure 7, the CPU 202 of the imaging device 110 transitions the display screen of the display unit 205 (display 410) to the screen corresponding to the selected menu button. For example, if the "Show All" button 804 shown in Figure 8(a) is selected, the display transitions to the display screen 620 shown in Figure 8(b), which will be described later. Also, for example, if the "Manual Input" button 805 shown in Figure 8(a) is selected, the display transitions to the display screen 1010 shown in Figure 10(b), which will be described later. Also, for example, if the "Scan" button 806 shown in Figure 8(a) is selected, the display transitions to the display screen 1210 shown in Figure 12(b), which will be described later.

[0115] When the process in step S713 in Figure 7 is completed, or when the process in step S714 in Figure 7 is completed, the process in the flowchart shown in Figure 7 is completed. Then, when the process in the flowchart shown in Figure 7 is completed, the process in step S601 in Figure 6 is completed, and the process proceeds to step S602 in Figure 6.

[0116] Next, we will explain the display screen 620 shown in Figure 8(b). In the display screen 620 shown in Figure 8(b), the same reference numbers are used for components that are the same as those in the display screen 610 shown in Figure 8(a), and their detailed explanations will be omitted.

[0117] The display screen 620 shown in Figure 8(b) is the screen displayed on the display 410 when, for example, the "Show All" button 804 is selected on the display screen 610 shown in Figure 8(a). In the display screen 620 shown in Figure 8(b), the medical management information 808 shows an example of medical management information obtained from the medical information system management device 120. Specifically, the medical management information 808 corresponds to the medical management information 516 shown in Figure 5. More specifically, the medical management information 808 indicates that patient P, Jiro Tanaka, with reception number 61, is awaiting a call from a doctor. In the display screen 620 shown in Figure 8(b), the medical management information 809 shows an example of medical management information obtained from the medical information system management device 120. Specifically, the medical management information 809 corresponds to the medical management information 517 shown in Figure 5. More specifically, the medical management information 809 indicates that patient P, Saburo Sato, with reception number 62, is awaiting a call from a doctor. In the display screen 620 shown in Figure 8(b), the medical management information 810 shows an example of medical management information obtained from the medical information system management device 120. Specifically, the medical management information 810 corresponds to the medical management information 518 shown in Figure 5. More specifically, the medical management information 810 indicates that patient P, Shiro Kato, whose reception number is 63, is awaiting a call from a doctor. Note that the display screen 620 shown in Figure 8(b) does not display the medical management information corresponding to the medical management information 513 shown in Figure 5 (status information 512 indicates that payment has been completed). In this regard, if it is desirable to also display the medical management information 513 for patient P who has completed payment, the data to be displayed can be associated with the settings of the imaging device 110 in advance and stored so that the medical management information 513 can be displayed.

[0118] Next, we will explain the display screen 630 shown in Figure 8(c). In the display screen 630 shown in Figure 8(c), the same reference numbers are used for components that are the same as those shown in Figure 4, and their detailed explanations will be omitted.

[0119] The display screen 630 shown in Figure 8(c) is, for example, a display screen that shows information about patient P in the medical management information selected from among the medical management information 802-803 and 808-810 in the display screen 620 shown in Figure 8(b).

[0120] Figure 9 shows a first embodiment and is a flowchart illustrating an example of a detailed processing procedure in step S603 of Figure 6. Specifically, Figure 9 is a flowchart illustrating an example of the process for acquiring display data when the "Show All" button 804 is selected on the display screen 610 shown in Figure 8(a), and the processing for various button selection operations. In the flowchart shown in Figure 9, the same step numbers are used for processing steps that are the same as those shown in Figure 7, and their detailed explanations are omitted.

[0121] First, in step S901 in Figure 9, the CPU 202 of the imaging device 110 determines whether or not the "Show All" button 804 shown in Figure 8(a) has been selected.

[0122] In step S901 in Figure 9, if the CPU 202 of the imaging device 110 determines that the "Show All" button 804 shown in Figure 8(a) has been selected (S901 / YES), the process proceeds to step S902. When the process proceeds to step S902 in Figure 9, the CPU 202 of the imaging device 110 transitions the display screen in preparation for displaying all reception numbers. For example, it transitions to a display screen in which the update button 801 in Figure 8(a), which is not needed when displaying all reception numbers, is hidden.

[0123] Next, in step S903 in Figure 9, the CPU 202 of the imaging device 110 clears the filter results from step S705 in Figure 7, which narrowed down the reception numbers (narrowing down to only those with status information 512 marked as "called"). For example, in step S903, the medical management information 516-518 in Figure 5, which was hidden in Figure 8(a), is made available for display.

[0124] Next, in step S706 of Figure 9, the CPU 202 of the imaging device 110 displays a list of medical management information, including the reception number information 503 acquired from the medical information system management device 120 in response to the request in S701 of Figure 7, on the display unit 205 (display 410). In this embodiment, the processing in step S706 of Figure 9 displays, for example, the display screen 620 shown in Figure 8(b). Thus, in the processing in step S706 of Figure 9, basically, a list of medical management information, including all reception number information 503 acquired from the medical information system management device 120, is displayed on the display unit 205 (display 410). As a result, the photographer (doctor) can complete the preparation for imaging simply by selecting any patient P from among the patients P currently being examined.

[0125] Once the process in step S706 in Figure 9 is completed, the process is then basically the same as in steps S709 to S710 and S713 in Figure 7.

[0126] In step S709 of Figure 9, if the CPU 202 of the imaging device 110 determines that medical management information 802-803 and 808-810 on the display screen 620 shown in Figure 8(b) has not been selected (S709 / NO), the process proceeds to step S904. When the process proceeds to step S904 in Figure 9, the CPU 202 of the imaging device 110 determines whether or not the cancel button 415 on the display screen 620 shown in Figure 8(b) has been selected. If, in step S904 of Figure 9, the CPU 202 of the imaging device 110 determines that the cancel button 415 on the display screen 620 shown in Figure 8(b) has not been selected (S904 / NO), the process returns to step S709.

[0127] Furthermore, in step S904 of Figure 9, if the CPU 202 of the imaging device 110 determines that the cancel button 415 on the display screen 620 shown in Figure 8(b) has been selected (S904 / YES), the process proceeds to step S905. When the process proceeds to step S905 in Figure 9, the CPU 202 of the imaging device 110 performs a process to return the display screen to the previous display screen in response to the selection operation of the cancel button 415 in step S904 in Figure 9. In this embodiment, for example, the display screen 620 shown in Figure 8(b) is returned to the display screen 610 shown in Figure 8(a).

[0128] When the process in step S905 in Figure 9 is completed, or when the process in step S713 in Figure 9 is completed, the process in the flowchart shown in Figure 9 is completed. Then, when the process in the flowchart shown in Figure 9 is completed, the process in step S603 in Figure 6 is completed, and the process proceeds to step S604 in Figure 6.

[0129] The imaging device 110 according to the first embodiment described above is an imaging device configured to communicate with the medical information system management device 120. The CPU 202 of the imaging device 110 according to the first embodiment performs the process of acquiring a medical management information list 500, which includes the reception information (reception number information 503) of the patient P, the subject of the imaging, from the medical information system management device 120 (for example, S704 / YES in Figure 7). The CPU 202 that performs the process of acquiring this medical management information list 500 constitutes the acquisition means in this embodiment. Furthermore, the CPU 202 of the imaging device 110 according to the first embodiment performs the process of identifying medical management information that includes predetermined reception information (reception number information 503) from the acquired medical management information list 500 (for example, S710 in Figure 7). The CPU 202 that performs the process of identifying medical management information that includes predetermined reception information (reception number information 503) constitutes the identification means in this embodiment. In the first embodiment, the CPU 202 of the imaging device 110 performs control to associate and store predetermined reception information (reception number information 503) with image data of patient P, which is the subject of the predetermined reception information (for example, S606 in Figure 6). This CPU 202, which performs control to associate and store predetermined reception information with image data of patient P, which is the subject of the predetermined reception information, constitutes the storage control means in this embodiment. According to the imaging device 110 of this first embodiment, the workload of the administrator who performs the task of associating image data of the patient P, which is the subject, with information related to that subject can be reduced.

[0130] Furthermore, the imaging device 110 according to the first embodiment has a display unit 205 (display 410) that displays information from the medical management information list 500 acquired by the CPU 202. This display unit 205 (display 410) that displays information from the medical management information list 500 constitutes the display means in this embodiment. The CPU 202 of the imaging device 110 according to the first embodiment identifies medical management information, including reception information selected from the information of the medical management information list 500 displayed on the display unit 205 (display 410), as medical management information including predetermined reception information.

[0131] Furthermore, when the CPU 202 of the imaging device 110 according to the first embodiment identifies medical management information containing predetermined reception information from the information in the medical management information list 500, it may exclude medical management information containing reception information being captured by another imaging device from the identified target. Specifically in this embodiment, one example is to exclude medical management information 803, which is marked with an icon 807 indicating that it is being captured by another imaging device, as shown in Figures 8(a) and 8(b), from the identified target of medical management information containing predetermined reception information. In this embodiment, as shown in Figures 8(a) and 8(b), the display unit 205 (display 410) displays medical management information 803 containing reception information being captured by another imaging device in an identifiable manner by marking it with an icon 807.

[0132] Furthermore, when the CPU 202 of the imaging device 110 according to the first embodiment identifies medical management information containing predetermined reception information from the information in the medical management information list 500, it may exclude medical management information containing reception information that has already been examined from the identified target. Specifically, in this embodiment, the medical management information 513 containing reception information that has already been examined and whose status information 512 shown in Figure 5 is accounted for is not displayed in Figures 8(a) and 8(b), and is excluded from the identified target of medical management information containing predetermined reception information. When displaying the medical management information 513 containing reception information that has already been examined on the display unit 205 (display 410), it may be possible to display it in a form that can be identified by attaching a predetermined icon to the medical management information 513 containing reception information that has already been examined.

[0133] (Second embodiment) Next, a second embodiment will be described. In the description of the second embodiment below, matters common to the first embodiment described above will be omitted, and matters that differ from the first embodiment described above will be explained.

[0134] The schematic configuration of the imaging system according to the second embodiment is the same as the schematic configuration of the imaging system 100 according to the first embodiment shown in Figure 1. The hardware configuration of the imaging device 110 according to the second embodiment is the same as the hardware configuration of the imaging device 110 according to the first embodiment shown in Figure 2. The hardware configuration of the medical information system management device 120 according to the second embodiment is the same as the hardware configuration of the medical information system management device 120 according to the first embodiment shown in Figure 3. The external appearance of the imaging device 110 according to the second embodiment, viewed from the rear, is the same as the external appearance of the imaging device 110 according to the first embodiment, viewed from the rear, shown in Figure 4. The medical management information list managed by the medical information system management device 120 according to the second embodiment is the same as the medical management information list 500 managed by the medical information system management device 120 according to the first embodiment shown in Figure 5. The processing procedure in the control method of the imaging device 110 according to the second embodiment is the same as the flowchart showing an example of the processing procedure in the control method of the imaging device 110 according to the first embodiment shown in Figure 6.

[0135] Figure 10 shows an example of display screens 610 and 1010-1030 that can be displayed on the display unit 205 (display 410) in the imaging device 110 according to the second embodiment. In Figure 10, components similar to those shown in Figures 4, 6, and 8 are given the same reference numerals, and their detailed explanations are omitted. Specifically, the display screen 610 shown in Figure 10(a) corresponds to the display screen 610 shown in Figures 6 and 8(a).

[0136] [Second display mode (manual input mode)] The display screen 1010 shown in Figure 10(b) is the screen displayed on the display 410 when, for example, the manual input button 805 is selected on the display screen 610 shown in Figure 10(a). The mode in which the display screen 1010 shown in Figure 10(b) is displayed corresponds to the second display mode in this embodiment. However, for example, if the imaging device 110 is disconnected from the network 160, the display of the display screen 610 shown in Figure 10(a) may be omitted and the display screen 1010 shown in Figure 10(b) may be displayed instead. That is, the display unit 205 (display 410) switches between a first display mode, which displays the display screen 610 shown in Figure 10(a), and a second display mode, which displays the display screen 1010 shown in Figure 10(b), depending on the communication status between the imaging device 110 and the network 160. By performing such display processing, the number of operations performed by the physician can be reduced.

[0137] In the display screen 1010 shown in Figure 10(b), the reception number input display section 1011 is an area that displays the reception number of the patient P entered by the photographer (doctor). In the display screen 1010 shown in Figure 10(b), the numeric button group 1012 is a group of numeric buttons for the photographer (doctor) to input the reception number displayed in the reception number input display section 1011. This numeric button group 1012 is provided with numeric buttons for inputting numbers from 0 to 9.

[0138] In the display screen 1010 shown in Figure 10(b), the delete button 1013 is operated to delete a number that has been entered via the numeric button group 1012 and is displayed on the reception number input display unit 1011. Each time the photographer (doctor) presses this delete button 1013, they can delete one number displayed on the reception number input display unit 1011. If no numbers are displayed on the reception number input display unit 1011, it is preferable to gray out the delete button 1013 or otherwise make the display screen 1010 easier for the photographer to understand.

[0139] The display screen 1020 shown in Figure 10(c) is the screen displayed on the display 410 when, for example, the OK button 414 is selected on the display screen 1010 shown in Figure 10(b). In the display screen 1020 shown in Figure 10(c), the reception number display unit 1021 is an area that displays the reception number that was displayed on the reception number input display unit 1011 when the OK button 414 was selected on the display screen 1010 shown in Figure 10(b). As shown in the display screen 1020 in Figure 10(c), by displaying the reception number on the display unit 205 (display 410) of the imaging device 110 during imaging, the photographer (doctor) can take images while confirming the reception number displayed on the reception number display unit 1021. In this embodiment, the display screen 1020 shown in Figure 10(c) is an example of the display when the imaging device 110 is disconnected from the network 160 (offline). If the imaging device 110 is connected to the network 160, then patient information linked to the reception number information 503 can be obtained and displayed from the medical management information list 500 shown in Figure 5.

[0140] The display screen 1030 shown in Figure 10(d) is the screen displayed on the display 410 when, for example, the end button 416 is selected on the display screen 1020 shown in Figure 10(c). On the display screen 1030 shown in Figure 10(d), the reception number selection button 1031, when selected, transitions to the display screen 610 shown in Figure 10(a). By transitioning the display screen in this way, preparations for starting the imaging of the second patient P can begin immediately after the imaging of the first patient P is completed.

[0141] Figure 11 shows a second embodiment and is a flowchart illustrating an example of a detailed processing procedure in step S603 of Figure 6. Specifically, Figure 11 is a flowchart illustrating an example of the process for acquiring display data when the manual input button 805 is selected on the display screen 610 shown in Figure 10(a), and the processing for various button selection operations. In the flowchart shown in Figure 11, the same step numbers are used for processing steps that are the same as those shown in Figure 9 (including Figure 7), and their detailed explanations are omitted.

[0142] First, in step S1101 in Figure 11, the CPU 202 of the imaging device 110 determines whether or not the manual input button 805 shown in Figure 10(a) has been selected.

[0143] In step S1101 in Figure 11, if the CPU 202 of the imaging device 110 determines that the manual input button 805 shown in Figure 10(a) has been selected (S1101 / YES), the process proceeds to step S1102. When the process proceeds to step S1102 in Figure 11, the CPU 202 of the imaging device 110 transitions the display screen in preparation for manually entering the reception number. For example, it transitions to the display screen 1010 shown in Figure 10(b), which displays the reception number input display unit 1011 and the numerical button group 1012. If the imaging device 110 is disconnected from the network 160 and the system is to automatically transition to the display screen 1010 shown in Figure 10(b), then, for example, the connection status between the imaging device 110 and the network 160 can be determined in step S1102.

[0144] Next, in step S1103 of Figure 11, the CPU 202 of the imaging device 110 determines whether the photographer (physician) has selected the numerical button group 1012 or the delete button 1013 on the display screen 1010 shown in Figure 10(b).

[0145] In step S1103 of Figure 11, if the CPU 202 of the imaging device 110 determines that the photographer (physician) has selected either the numerical button group 1012 or the delete button 1013 shown in Figure 10(b) (S1103 / YES), the process proceeds to step S1104. When the process proceeds to step S1104 in Figure 11, the CPU 202 of the imaging device 110 reflects the processing corresponding to the numerical button group 1012 or delete button 1013 that it determined was selected in step S1103 on the display screen 1010 of the display unit 205 (display 410). For example, it reflects this on the display of the reception number input display unit 1011 in Figure 10(b). When the processing in step S1104 is completed, the process returns to step S1103. In this way, by repeating the processing in step S1103 and step S1104, the photographer (doctor) can input the desired reception number into the imaging device 110.

[0146] Furthermore, in step S1103 of Figure 11, if the CPU 202 of the imaging device 110 determines that the photographer (physician) has not selected the numerical button group 1012 or the delete button 1013 shown in Figure 10(b) (S1103 / NO), the process proceeds to step S1105. When the process proceeds to step S1105 in Figure 11, the CPU 202 of the imaging device 110 determines whether the photographer (doctor) has selected the OK button 414 on the display screen 1010 shown in Figure 10(b).

[0147] In step S1105 of Figure 11, if the CPU 202 of the imaging device 110 determines that the photographer (doctor) has selected the OK button 414 shown in Figure 10(b) (S1105 / YES), the process proceeds to step S1106. When the process proceeds to step S1106 in Figure 11, the CPU 202 of the imaging device 110 identifies the reception number entered in steps S1103 and S1104 as predetermined reception information and temporarily stores it in RAM 204 as imaging information. The imaging information temporarily stored in RAM 204 is used to display on the display unit 205 (display 410) in step S605 in Figure 6. In the example of screen transitions in Figure 10, it is used for the display of the reception number display unit 1021 shown in Figure 10(c).

[0148] Once the process in step S1106 in Figure 11 is completed, the same process as in step S713 in Figure 9 (including Figure 7) is performed.

[0149] Furthermore, in step S1105 of Figure 11, if the CPU 202 of the imaging device 110 determines that the photographer (doctor) has not selected the OK button 414 shown in Figure 10(b) (S1105 / NO), the process proceeds to step S904. Then, when the process proceeds to step S904 of Figure 11, the same processing as in step S904 of Figure 9 is performed, and then when the process proceeds to step S905 of Figure 11, the same processing as in step S905 of Figure 9 is performed.

[0150] When the process in step S713 in Figure 11 is completed, or when the process in step S905 in Figure 11 is completed, the process in the flowchart shown in Figure 11 is completed. Furthermore, in step S1101 in Figure 11, if the CPU 202 of the imaging device 110 determines that the manual input button 805 shown in Figure 10(a) has not been selected (S1101 / NO), the process in the flowchart shown in Figure 11 is completed. Once the process in the flowchart shown in Figure 11 is completed, the process in step S603 in Figure 6 is completed, and the process proceeds to step S604 in Figure 6.

[0151] The imaging device 110 according to the second embodiment described above includes a reception number input display unit 1011, a group of numerical buttons 1012, and a delete button 1013, which correspond to input means for inputting patient P's reception information. The CPU 202 of the imaging device 110 according to the second embodiment identifies the reception information input by the input means as the predetermined reception information described above.

[0152] Furthermore, the display unit 205 (display 410) of the imaging device 110 according to the second embodiment includes a first display mode that displays the display screen 610 shown in Figure 10(a) and a second display mode that displays the display screen 1010 shown in Figure 10(b). The display unit 205 (display 410) of the imaging device 110 according to the second embodiment switches between the first display mode and the second display mode described above depending on the communication status between the imaging device 110 and the network 160.

[0153] (Third embodiment) Next, a third embodiment will be described. In the description of the third embodiment below, matters common to the first and second embodiments described above will be omitted, and matters that differ from the first and second embodiments described above will be explained.

[0154] The schematic configuration of the imaging system according to the third embodiment is the same as the schematic configuration of the imaging system 100 according to the first embodiment shown in Figure 1. The hardware configuration of the imaging device 110 according to the third embodiment is the same as the hardware configuration of the imaging device 110 according to the first embodiment shown in Figure 2. The hardware configuration of the medical information system management device 120 according to the third embodiment is the same as the hardware configuration of the medical information system management device 120 according to the first embodiment shown in Figure 3. The external appearance of the imaging device 110 according to the third embodiment, viewed from the rear, is the same as the external appearance of the imaging device 110 according to the first embodiment, viewed from the rear, shown in Figure 4. The medical management information list managed by the medical information system management device 120 according to the third embodiment is the same as the medical management information list 500 managed by the medical information system management device 120 according to the first embodiment shown in Figure 5. The processing procedure in the control method of the imaging device 110 according to the third embodiment is the same as the flowchart showing an example of the processing procedure in the control method of the imaging device 110 according to the first embodiment shown in Figure 6.

[0155] Figure 12 shows examples of display screens 610, 1210, and 630 that can be displayed on the display unit 205 (display 410) in the imaging device 110 according to the third embodiment. In Figure 12, components similar to those shown in Figures 4, 6, 8, and 10 are given the same reference numerals, and their detailed explanations are omitted. Specifically, the display screen 610 shown in Figure 12(a) corresponds to the display screen 610 shown in Figures 6, 8(a), and 10(a).

[0156] [Third display mode (scan mode)] The display screen 1210 shown in Figure 12(b) is the screen displayed on the display 410 when, for example, the scan button 806 is selected on the display screen 610 shown in Figure 12(a). Note that while Figure 10(b) describes the manual input method, Figure 12(b) describes the scan input method. Here, the scan input method is particularly effective when the string to be entered is long. For example, the effect of scan input is minimal for a small number of digits, such as a reception number, but it can reduce the operational burden on the photographer (doctor) for a relatively large number of digits, such as a patient ID.

[0157] In the display screen 1210 shown in Figure 12(b), the code reading assistance frame 1211 is an assistance frame intended to support the photographer (physician) when reading a two-dimensional code (which may also be a one-dimensional code) with the imaging device 110. In the display screen 1210 shown in Figure 12(b), the two-dimensional code 1212 is a two-dimensional code provided within the code reading assistance frame 1211 and read by the imaging device 110. In this embodiment, the specifications of the two-dimensional code 1212 (which may also be a one-dimensional code) are not particularly limited. If there is a code that is already in use in the medical field, it is sufficient to enable code analysis in accordance with the specifications of that code.

[0158] The display screen 630 shown in Figure 12(c) is, for example, the screen displayed on the display 410 when the two-dimensional code 1212 shown in Figure 12(b) is read by the imaging device 110 and patient information is acquired.

[0159] Figure 13 shows a third embodiment and is a flowchart illustrating an example of a detailed processing procedure in step S603 of Figure 6. Specifically, Figure 13 is a flowchart illustrating an example of the process for acquiring display data when the scan button 806 is selected on the display screen 610 shown in Figure 12(a), and the processing for various button selection operations. In the flowchart shown in Figure 13, the same step numbers are used for processing steps similar to those shown in Figures 7 and 9, and their detailed explanations are omitted.

[0160] First, in step S1301 in Figure 13, the CPU 202 of the imaging device 110 determines whether or not the scan button 806 shown in Figure 12(a) has been selected.

[0161] In step S1301 in Figure 13, if the CPU 202 of the imaging device 110 determines that the scan button 806 shown in Figure 12(a) has been selected (S1301 / YES), the process proceeds to step S1302. When the process proceeds to step S1302 in Figure 13, the CPU 202 of the imaging device 110 transitions the display screen in preparation for scanning and inputting the reception number, patient ID, doctor ID, etc. For example, it transitions to a display screen 1210 having a code reading auxiliary frame 1211 in which the two-dimensional code 1212 shown in Figure 12(b) is positioned.

[0162] Next, in step S1303 of Figure 13, the CPU 202 of the imaging device 110 determines whether or not it was possible to read a two-dimensional code 1212, which indicates patient P, the patient being photographed, from the live view image displayed on the display unit 205 (display 410).

[0163] In step S1303 of Figure 13, if the CPU 202 of the imaging device 110 determines that it has read the two-dimensional code 1212, which contains patient information such as that of the patient P to be photographed (S1303 / YES), the process proceeds to step S1304. In this embodiment, the patient information such as that of the patient P to be photographed is obtained, for example, by reading and analyzing the two-dimensional code 1212 from the live view image. The CPU 202 of the imaging device 110 then uses the information such as the reception number, patient ID, and physician ID obtained by reading the two-dimensional code 1212 to identify the patient P to be photographed and the physician who is taking the image from the medical management information list 500 shown in Figure 5. In this case, as shown in Figure 12(c), the CPU 202 of the imaging device 110 displays the information of the identified patient P and the physician who is taking the image on the display unit 205 (display 410). Therefore, a change in the patient P to be photographed occurs in response to the operator's operation of reading the two-dimensional code 1212. Furthermore, the information and detection methods used to identify the specific patient P in step S1303 of Figure 13 are not particularly limited. For example, any appropriate method can be used, such as one-dimensional codes (barcodes), biometric information (personally identifiable information such as voice, fingerprints, or face), voice input, OCR (Optical Character Reader), or RFID detection.

[0164] When the process proceeds to step S1304 in Figure 13, the CPU 202 of the imaging device 110 determines whether the information from the two-dimensional code 1212 read in step S1303 matches the information from the medical management information list 500 obtained in response to the request in step S701 in Figure 7. For example, if the reception number is 60 as a result of reading the two-dimensional code 1212, then according to the medical management information list 500 shown in Figure 5, medical management information 515 can be identified. Also, for example, if the patient ID is 00004 as a result of reading the two-dimensional code 1212, then according to the medical management information list 500 shown in Figure 5, medical management information 516 can be identified. Furthermore, for example, if the physician ID is 0001 as a result of reading the two-dimensional code 1212, then according to the medical management information list 500 shown in Figure 5, medical management information 513, 515, 516, and 518 are the corresponding entries. When multiple pieces of medical management information are applicable, for example, the display screen 620 shown in Figure 8(b) can be displayed on the display 410 after the display screen 1210 shown in Figure 12(b), allowing the photographer to select the medical management information for the patient P being photographed.

[0165] In S1304 in Figure 13, if the CPU 202 determines that the information of the two-dimensional code 1212 read in S1303 does not match the information of the medical management information list 500 obtained in response to the request in S701 in Figure 7 (S1304 / NO), the process proceeds to S1305. When the process proceeds to step S1305 in Figure 13, the CPU 202 of the imaging device 110 transmits the information of the two-dimensional code 1212 read in step S1303 to the medical information system management device 120 and requests the acquisition of patient information, etc., based on the information of the two-dimensional code 1212. The information transmitted in step S1305 is assumed to be the patient ID, but it may also be medical record information recorded in the electronic medical record of the patient P being photographed. Examples of this medical record information include physician ID, physician's name, medical department, patient ID, patient's name, age, gender, medical history, imaging history, affected area, and lesion.

[0166] Next, in step S1306 of Figure 13, the CPU 301 of the medical information system management device 120 acquires information about the patient P to be photographed based on the information transmitted from the imaging device 110 in step S1305. The information about the patient P to be photographed acquired in step S1306 is not particularly limited, but it is assumed to be the medical record information of the patient P to be photographed as described above.

[0167] Next, in step S1307 of Figure 13, the CPU 301 of the medical information system management device 120 returns the information about the patient P to be photographed, which was acquired in step S1306, to the imaging device 110.

[0168] Next, in step S1308 in Figure 13, the CPU 202 of the imaging device 110 determines whether or not it was able to obtain information about the patient P to be imaged, based on the information returned from the medical information system management device 120. If the CPU 202 of the imaging device 110 determines in step S1308 in Figure 13 that it was not possible to obtain information about the patient P to be imaged (S1308 / NO), the process returns to step S1302. In cases where information about the patient P to be imaged could not be obtained, it may occur if a patient ID or other information that does not exist in the relevant medical record is received, or if a communication error, including a timeout error, occurs.

[0169] Furthermore, in step S1308 in Figure 13, if the CPU 202 of the imaging device 110 determines that it has obtained information about the patient P to be photographed (S1308 / YES), the process proceeds to step S710. Also, in S1304 in Figure 13, if the CPU 202 determines that the information of the two-dimensional code 1212 read in S1303 matches the information of the medical management information list 500 obtained in response to the request in S701 in Figure 7 (S1304 / YES), the process proceeds to S710. Proceeding to step S710 in Figure 13, the same process as in step S710 in Figure 7 is performed. Then, proceeding to step S713 in Figure 13, the same process as in step S713 in Figure 7 is performed.

[0170] Furthermore, in step S1303 of Figure 13, if the CPU 202 of the imaging device 110 determines that it could not read the two-dimensional code 1212, which represents patient P, the patient to be photographed (S1303 / NO), the process proceeds to step S904. When the process proceeds to step S904 in Figure 13, the CPU 202 of the imaging device 110 determines whether the cancel button 415 has been selected, similar to step S904 in Figure 9. If the CPU 202 of the imaging device 110 determines that the cancel button 415 has been selected in step S904 of Figure 13 (S904 / YES), the process proceeds to step S905. Then, when the process proceeds to step S905 in Figure 13, the same processing as in step S905 in Figure 9 is performed.

[0171] Furthermore, in step S904 of Figure 13, if the CPU 202 of the imaging device 110 determines that the cancel button 415 has not been selected (S904 / NO), the process proceeds to step S1309. When the process proceeds to step S1309 in Figure 13, the CPU 202 of the imaging device 110 determines whether or not the manual input button 805 shown in Figure 12(a) has been selected. If, in step S1309 of Figure 13, the CPU 202 of the imaging device 110 determines that the manual input button 805 shown in Figure 12(a) has not been selected (S1309 / NO), the process returns to step S1302.

[0172] Furthermore, in step S1309 in Figure 13, if the CPU 202 of the imaging device 110 determines that the manual input button 805 shown in Figure 12(a) has been selected (S1309 / YES), the process proceeds to step S1310. When the process proceeds to step S1310 in Figure 13, the CPU 202 of the imaging device 110 performs the processing shown in the flowchart in Figure 11 (manual input processing).

[0173] When the process in step S1310 in Figure 13 is completed, when the process in step S905 in Figure 13 is completed, or when the process in step S713 in Figure 13 is completed, the process in the flowchart shown in Figure 13 is completed. Furthermore, in step S1301 in Figure 13, if the CPU 202 of the imaging device 110 determines that the scan button 806 shown in Figure 12(a) has not been selected (S1301 / NO), the process in the flowchart shown in Figure 13 is completed. Once the process in the flowchart shown in Figure 13 is completed, the process in step S603 in Figure 6 is completed, and the process proceeds to step S604 in Figure 6.

[0174] According to the imaging device 110 of the third embodiment described above, similar to the imaging device 110 of the first embodiment, the workload of the administrator who associates image data of the patient P, which is the subject, with information related to that subject can be reduced.

[0175] (Fourth embodiment) Next, a fourth embodiment will be described. In the description of the fourth embodiment below, matters common to the first to third embodiments described above will be omitted, and only matters that differ from the first to third embodiments described above will be explained.

[0176] The schematic configuration of the imaging system according to the fourth embodiment is the same as the schematic configuration of the imaging system 100 according to the first embodiment shown in Figure 1. Furthermore, the hardware configuration of the imaging device 110 according to the fourth embodiment is the same as the hardware configuration of the imaging device 110 according to the first embodiment shown in Figure 2. Also, the hardware configuration of the medical information system management device 120 according to the fourth embodiment is the same as the hardware configuration of the medical information system management device 120 according to the first embodiment shown in Figure 3. Furthermore, the external appearance of the imaging device 110 according to the fourth embodiment, viewed from the rear, is the same as the external appearance of the imaging device 110 according to the first embodiment, viewed from the rear, shown in Figure 4. Also, the medical management information list managed by the medical information system management device 120 according to the fourth embodiment is the same as the medical management information list 500 managed by the medical information system management device 120 according to the first embodiment shown in Figure 5.

[0177] Figure 14 is a flowchart showing an example of a processing procedure in the control method of the imaging device 110 according to the fourth embodiment. Specifically, Figure 14 is a flowchart showing an example of a processing procedure for limited additional processing to omit physician operations. While the flowchart processing preferred in the first to third embodiments described above has been explained, it is also conceivable to omit some of the processing in the flowcharts of the first to third embodiments described above in order to reduce the number of physician operations. For example, in the filtering process in step S705 of Figure 7, if there is one patient P that has been called, that patient P is confirmed as the subject of imaging, and then the process proceeds to the saving of imaging information in step S710 of Figure 7. This allows for the omission of, for example, the processing in step S709 of Figure 7 (the patient P selection operation), thereby reducing the workload on the physician's operations.

[0178] In the following explanation of the flowchart shown in Figure 14, first, the patient P to be photographed is narrowed down based on several conditions (steps S1402 to S1404). Next, it is determined whether the physician's operational procedures can be omitted based on conditions that allow for the unique identification of patient P (steps S1407 to S1409). As needed, the explanation will refer to the information in the medical management information list 500 shown in Figure 5. In addition, even if it is not described in this embodiment, information (including data) obtainable from, for example, the status of the imaging device 110, the medical information system management device 120, the medical information system terminal device 130, and the data management device 140 can be used. Then, depending on this available information (including data), the process may be shortened by combining the means for narrowing down patient P (filtering method) and the means for uniquely identifying patient P, thereby reducing the number of operations performed by the physician.

[0179] First, in step S1401 in Figure 14, the CPU 202 of the imaging device 110 obtains information from the medical information system management device 120, including, for example, the reception number information 503 in Figure 5, from the medical management information list 500. Note that this step S1401 can be achieved by performing the same processing as steps S701 to S704 in Figure 7, for example, so the explanation of that process is omitted.

[0180] <Method for identifying the registration number associated with patient P after a predetermined period of time has elapsed> Next, in step S1402 of Figure 14, the CPU 202 of the imaging device 110 determines whether or not there is a patient P for whom a predetermined time has elapsed since being called from the waiting room. The predetermined time can be set in advance, for example, in the ROM 203 of the imaging device 110. The time when patient P was called from the waiting room can be, for example, the time when the operation to call patient P was performed from the medical information system terminal device 130 (for example, the patient calling terminal device). In this case, the time when patient P was called from the waiting room can be stored in the RAM 303 of the medical information system management device 120 so that it can be added to the medical management information list 500 shown in Figure 5.

[0181] The CPU 202 of the imaging device 110 identifies, for example, a patient P who has been called for a predetermined time, from the medical management information list 500 shown in Figure 5, which is temporarily stored in the RAM 204. The filtering process for the identified information is performed in step S1405, which will be described later. This allows for the exclusion of patient P from the patients to be imaged if, as a result of calling patient P who should be in the waiting room, they have not actually entered the designated examination room (when patient P is absent). Information indicating the absence of patient P from other imaging devices can be easily obtained because the imaging device 110 and the medical information system management device 120 are linked. For example, by managing the time when patient P is called from the waiting room, the CPU 202 of the imaging device 110 can display the reception information of patient P, etc., in an identifiable manner if a predetermined time has elapsed since patient P was called from the waiting room. An example of this identifiable display is that the display 410 displays an icon (for example, an icon like icon 807) indicating that a predetermined amount of time has elapsed since the time patient P was called from the waiting room. In the process of step S1402, although it is possible to narrow down the patient P to be photographed, it is anticipated that it may be difficult to identify a single person. To prepare for such cases, the processes of steps S1403 and S1404, which will be described later, are performed. In order to proceed to steps S1403 and S1404, which will be described later, the CPU 202 first performs the processes of steps S1405 and S1406, which will be described later.

[0182] In step S1402 of Figure 14, if the CPU 202 of the imaging device 110 determines that there is no patient P for whom a predetermined time has elapsed since calling patient P from the waiting room (S1402 / NO), the device proceeds to step S1403. When the process proceeds to step S1403 in Figure 14, the CPU 202 of the imaging device 110 determines whether or not there is a patient P being imaged by another imaging device 110. Specifically, the CPU 202 determines, for example, whether or not there is information (not shown) indicating that the patient is being imaged by another imaging device in the medical management information list 500 shown in Figure 5. This makes it possible to exclude patient P, who should be being imaged in another examination room, from the imaging target. However, depending on the imaging method used in the medical setting, it may be necessary to perform imaging with multiple devices. To prepare for such cases, for example, whether or not to perform the processing in step S1403 can be stored in the ROM 203 of the imaging device 110 as a pre-set value.

[0183] Furthermore, information indicating that imaging is in progress on another imaging device can be easily obtained because the imaging device 110 and the medical information system management device 120 are linked. For example, at the time when the patient P to be imaged is determined, such as in step S710 (saving imaging information) in Figure 7, it is conceivable to add information indicating that imaging is in progress on another imaging device to the patient P's information (for example, the information in the medical management information list 500 shown in Figure 5) and save it. In this case, the information indicating that imaging is in progress on another imaging device can be saved in the medical information system management device 120 along with unique information such as the serial number of the other imaging device. By saving it in this way, for example, the CPU 202 of the imaging device 110 can display an icon (an icon like icon 807) on the display unit 205 (display 410) to indicate this. Furthermore, similar to step S1402, in the processing of step 1403, although it is possible to narrow down the patient P to be imaged, it is anticipated that it may be difficult to identify a single person. To prepare for such cases, the processing of step S1404, which will be described later, is performed. Furthermore, in order to proceed to step S1404, which will be described later, the CPU 202 first performs the processes of steps S1405 and S1406, which will be described later.

[0184] In step S1403 of Figure 14, if the CPU 202 of the imaging device 110 determines that there is no patient P being imaged by another imaging device 110 (S1403 / NO), the process proceeds to step S1404. When the process proceeds to step S1404 in Figure 14, the CPU 202 of the imaging device 110 determines whether or not there are patients P waiting to be billed. Patients P waiting to be billed refer to patients P who have finished their examination, returned to the waiting room, and are waiting for processing such as the calculation of medical fee points. Specifically, the CPU 202 determines, for example, whether or not there is information (not shown) indicating patients waiting to be billed in the medical management information list 500 shown in Figure 5. This makes it possible to exclude patients P who should have finished their examination from the imaging target. The method for updating to the "waiting for billing (examined)" status is, for example, by updating the status information 512 in the medical management information list 500 shown in Figure 5. In this case, for example, after calling patient P from the waiting room, the status information 512 can be updated when the medical record information of patient P to be imaging is updated on the electronic medical record terminal device, when the doctor completes the examination, or when the next patient P is called in. Alternatively, the status information 512 may be updated not by a doctor's operation, but by an operation of the medical information system terminal device 130 (for example, a medical accounting system terminal device) by a reception staff member targeting patient P. By updating the status information 512 to indicate that payment is pending, for example, the CPU 202 of the imaging device 110 can display an icon (such as icon 807) on the display unit 205 (display 410) of the imaging device 110 to indicate this.

[0185] In this embodiment, if there are no patients P waiting to be paid (S1404 / NO), the CPU 202 can proceed directly to step S1407 without issue. However, if the number of criteria for narrowing down patients P, such as steps S1402 to S1404, increases, this can be handled by modifying only step S1406, which will be described later. For this reason, in the description of this embodiment, even if there are no patients P waiting to be paid (S1404 / NO), the processing of step S1406 is performed.

[0186] In step S1402 of Figure 14, if the CPU 202 of the imaging device 110 determines that there is a patient P who has been called from the waiting room for a predetermined amount of time (S1402 / YES), the process proceeds to step S1405. Also, in step S1403 of Figure 14, if the CPU 202 of the imaging device 110 determines that there is a patient P being photographed by another imaging device 110 (S1403 / YES), the process proceeds to step S1405. Furthermore, in step S1404 of Figure 14, if the CPU 202 of the imaging device 110 determines that there is a patient P waiting to be paid (S1404 / YES), the process proceeds to step S1405. When the process proceeds to step S1405 in Figure 14, the CPU 202 of the imaging device 110 filters out the patient P identified in steps S1402 to S1404. At this time, the CPU 202 excludes the patient P by, for example, deleting the medical management information of the target patient P, as shown in Figure 5, which is temporarily stored in the RAM 204 of the imaging device 110. Note that the method of excluding the medical management information of the target patient P is not limited to deleting the relevant medical management information from RAM 204. For example, a logical deletion method can be considered in RAM 204, such as managing with a deletion flag, so that it can be re-referenced later. If management is done with a deletion flag, for example, an icon indicating this (an icon like icon 807) can be displayed on the display unit 205 (display 410) of the imaging device 110, providing an auxiliary function for the physician when selecting patient P. In this case, although the number of operations performed by the physician cannot be reduced, the status of patient P can be displayed on the display unit 205 (display 410) of the imaging device 110, thus reducing the search burden on the physician. Furthermore, examples of icons indicating the deletion flag mentioned above include the patient absence icon, which indicates that a predetermined time has elapsed while the call is in progress, as processed in step S1402, and the examined icon, which indicates patient P waiting for payment, as processed in step S1404. If, as a result of filtering the target patient P in step S1405, there is only one target patient P, the processing in steps S1406 and S1407 described later may be omitted, and the process may proceed to step S710 in Figure 14. By omitting such processing steps, the same effect can be obtained while reducing the number of processing steps.

[0187] If the process in step S1405 in Figure 14 is completed, the process proceeds to step S1406. Also, in step S1404 in Figure 14, if the CPU 202 of the imaging device 110 determines that there are no patients P waiting for payment (S1404 / NO), the process proceeds to step S1406. When the process proceeds to step S1406 in Figure 14, the CPU 202 of the imaging device 110 determines whether the patient filtering process (steps S1402 to S1404) has been executed at least once. The execution history can be managed, for example, by the RAM 204, to track whether the process has been executed or not. In step S1406 of Figure 14, if the CPU 202 of the imaging device 110 determines that the patient filtering process (steps S1402 to S1404) has not been executed even once (S1406 / NO), the process returns to step S1402. In this way, by making a determination in step S1406, the patient filtering process (steps S1402 to S1404) can be repeated.

[0188] <Method for identifying the reception number associated with patient P based on the number of people being called> In step S1406 of Figure 14, if the CPU 202 of the imaging device 110 determines that it has performed patient filtering processing (steps S1402 to S1404) at least once (1406 / YES), the process proceeds to step S1407. When the process proceeds to step S1407 in Figure 14, the CPU 202 of the imaging device 110 determines, based on the results of the patient filtering process described above (steps S1402 to S1404), whether it has been possible to identify one patient P who is being called from the waiting room. For example, if patient P in medical management information 515 of the medical management information list 500 shown in Figure 5 is currently being photographed, the CPU 202 can refer to status information 512 to identify patient P in medical management information 514 as the one patient P to be identified. By processing in this way, the patient P narrowed down by the patient filtering process described above (steps S1402 to S1404) can be immediately set as the target for imaging in the imaging device 110.

[0189] <Method for identifying the reception number associated with patient P using information from the previous photo shoot> In step S1407 of Figure 14, if the CPU 202 of the imaging device 110 determines that it could not identify one patient P who was being called from the waiting room (S1407 / NO), the process proceeds to step S1408. When the process proceeds to step S1408 in Figure 14, the CPU 202 of the imaging device 110 determines whether the room that was previously photographed matches the room currently being called. For example, the room information 509 in Figure 5 can be stored in the RAM 204 for the previously photographed room. Furthermore, if it is necessary to be able to determine the previously photographed room information even after the imaging device 110 is powered off, unique information such as the serial number of the imaging device 110 and the time information of when the imaging was completed can be stored in the medical information system management device 120. By processing in this way, in a medical setting where the imaging device 110 is continuously used in the same examination room, even if there are two or more patients P being called to different examination rooms, the system can automatically set patient P to be called to the same room, thus reducing the amount of manual processing required from the doctor.

[0190] <Method for identifying the reception number linked to patient P using the previous photographer's information> In step S1408 of Figure 14, if the CPU 202 of the imaging device 110 determines that the room previously photographed does not match the room currently being called (S1408 / NO), the process proceeds to step S1409. When the process proceeds to step S1409 in Figure 14, the CPU 202 of the imaging device 110 determines whether the person who took the previous image matches the physician being called. For example, the physician ID information 510 in Figure 5 can be stored in the RAM 204 to determine the person who took the previous image (physician information). Furthermore, if it is necessary to be able to determine the person who took the previous image (physician information) even after the imaging device 110 is powered off, the unique information such as the serial number of the imaging device 110 and the person who took the image (physician information) can be stored in the medical information system management device 120. By processing in this way, in medical settings where physicians take the imaging device 110 with them, the patient P being called, which is linked to the previous person who took the image, can be automatically set, thus reducing the number of operations that physicians have to perform.

[0191] In step S1407 of Figure 14, if the CPU 202 of the imaging device 110 determines that it has identified one patient P being called from the waiting room (S1407 / YES), the process proceeds to step S710. Also, in step S1408 of Figure 14, if the CPU 202 of the imaging device 110 determines that the room that was previously photographed matches the room that is currently being called (S1408 / YES), the process proceeds to step S710. Furthermore, in step S1409 of Figure 14, if the CPU 202 of the imaging device 110 determines that the person who was previously photographed matches the doctor who is currently being called (S1409 / YES), the process proceeds to step S710. When the process proceeds to step S710 in Figure 14, the same processing as in step S710 in Figure 7 is performed. Then, when the process proceeds to step S713 in Figure 14, the same processing as in step S713 in Figure 7 is performed. After the processing in step S713 in Figure 14 is completed, the process shown in the flowchart in Figure 14 is completed. Also, in step S1409 in Figure 14, if the CPU 202 of the imaging device 110 determines that the person who took the previous image and the physician being called do not match (S1409 / NO), the process shown in the flowchart in Figure 14 is completed. If a negative determination is made in step S1409 in Figure 14 (S1409 / NO), the process then transitions to a display screen (for example, the display screen 610 shown in Figure 8(a)) that allows the physician to select patient P.

[0192] Figure 15 shows a reception number ticket P2 held by patient P, as shown in Figure 1, and an example of the display screen shown on the medical information system terminal device 130 in the waiting room when patient P is called into the examination room. In a hospital, when patient P, who is waiting in the waiting room and holds a reception number ticket P2, is called, call information may be displayed on the medical information system terminal device 130. The explanation of Figure 15 is given below.

[0193] Specifically, Figure 15(a) shows an example of a reception number ticket P2 held by patient P, as shown in Figure 1. In the reception number ticket P2, hospital name information 1501 indicates the name of the hospital that issued the reception number ticket P2. Also, in the reception number ticket P2, reception date and time information 1502 indicates the date and time when patient P was registered at the hospital listed in hospital name information 1501. Furthermore, in the reception number ticket P2, reception number information 1503 indicates the number issued by the hospital listed in hospital name information 1501 in the order of registration. Note that the reception number listed in reception number information 1503 is a unique number valid only for that day. Therefore, by combining the reception number listed in reception number information 1503 with the reception date and time listed in reception date and time information 1502, unique information is obtained even if it is not for that day. In addition, in the reception number ticket P2, patient ID information 1504 indicates a patient ID that is a unique number valid for identifying patient P within the hospital. Furthermore, on the reception ticket P2, patient name information 1505 indicates the name of patient P who has completed registration. Also, on the reception ticket P2, doctor name information 1506 indicates the name of the doctor who will be in charge of examining patient P.

[0194] Figure 15(b) shows an example of a display screen shown on the medical information system terminal device 130 in the waiting room when patient P is called into the examination room. In the display screen of the medical information system terminal device 130 shown in Figure 15(b), room name information 1511 is information indicating the name of the room to which patient P has been called. In the example shown in Figure 15(b), room name information 1511 is information used by the doctor to prompt patient P, who is waiting in the waiting room, to enter the examination room. In the display screen of the medical information system terminal device 130 shown in Figure 15(b), department information 1512 is information indicating the name of the department. In the example shown in Figure 15(b), department information 1512 is information directed to patient P who has registered for plastic surgery. In the display screen of the medical information system terminal device 130 shown in Figure 15(b), doctor name information 1513 is information indicating the name of the doctor in charge of examining patient P. In the display screen of the medical information system terminal device 130 shown in Figure 15(b), the reception number information 1514 is information indicating a number issued by the hospital in the order of reception. In the example shown in Figure 15(b), the reception number information 1514 is information for calling patient P, whose reception number is 59.

[0195] The CPU 202 of the imaging device 110 according to the fourth embodiment described above performs the following processing. First, the CPU 202 identifies the medical management information containing the currently called reception information from the medical management information list 500, which includes the reception number information 503 in Figure 5, as medical management information containing predetermined reception information for patient P to be photographed (S1402 / YES in Figure 14).

[0196] Furthermore, the CPU 202 identifies the medical management information containing the reception information for the location where the previous image was taken, which is currently being called from the medical management information list 500 in Figure 5, as medical management information containing the predetermined reception information (S1408 / YES in Figure 14).

[0197] Furthermore, the CPU 202 identifies the medical management information containing the reception information of the photographer who matches the photographer who took the previous image, from the medical management information list 500 in Figure 5, as medical management information containing the predetermined reception information (S1409 / YES in Figure 14).

[0198] Furthermore, when the CPU 202 identifies medical management information containing predetermined reception information from the medical management information list 500 in Figure 5, it performs the following processing. Specifically, the CPU 202 excludes medical management information from the medical management information list 500 in Figure 5 that contains reception information that is being called and for which a predetermined time has elapsed from the target for identifying predetermined reception information (S1402 / YES and S1405 in Figure 14).

[0199] Furthermore, the imaging device 110 according to the fourth embodiment includes a display unit 205 (display 410) that displays information from the medical management information list 500 in Figure 5. The display unit 205 (display 410) displays medical management information from the medical management information list 500 in Figure 5, including reception information that is being called and for which a predetermined time has elapsed, in an identifiable manner by adding an icon (not shown).

[0200] According to the imaging device 110 of the fourth embodiment described above, similar to the imaging device 110 of the first embodiment, the workload of the administrator who associates image data of the patient P, which is the subject, with information related to that subject can be reduced.

[0201] (Other embodiments) The present invention can also be realized by supplying a program that implements one or more of the functions of the above-described embodiments to a system or device via a network or storage medium, and by having one or more processors in the computer of that system or device read and execute the program. It can also be realized by a circuit (e.g., an ASIC) that implements one or more functions. This program and a computer-readable storage medium storing said program are included in the present invention.

[0202] The embodiments of the present invention described above are merely examples of how the invention can be implemented, and the technical scope of the invention should not be interpreted as being limited by them. In other words, the present invention can be implemented in various forms without departing from its technical concept or its main features.

[0203] This embodiment includes the following configurations, methods, and programs. [Configuration 1] An imaging device configured to communicate with a management device, An acquisition means for acquiring a list containing subject reception information from the management device, A means for identifying predetermined reception information from the list acquired by the acquisition means, A storage control means that performs control to store in association the predetermined reception information identified by the identification means and the image data of the subject in the predetermined reception information, An imaging device characterized by having the following features. [Configuration 2] The system further includes a display means for displaying the list acquired by the acquisition means, The identification means identifies the reception information selected from the list displayed on the display means as the predetermined reception information. The imaging apparatus according to configuration 1, characterized by the features described above. [Configuration 3] The system further includes an input means for inputting the aforementioned reception information, The identification means identifies the reception information entered by the input means as the predetermined reception information. The imaging apparatus according to configuration 1, characterized by the features described above. [Structure 4] The aforementioned identification means identifies the currently called reception information from the list as the predetermined reception information. The imaging apparatus according to configuration 1, characterized by the features described above. [Composition 5] The identification means identifies the reception information from the list that is currently being called and matches the location where the previous photo was taken as the predetermined reception information. The imaging apparatus according to configuration 1, characterized by the features described above. [Composition 6] The aforementioned identification means identifies the reception information of a photographer who is currently being called from the list and who matches the photographer who took the previous photograph, as the predetermined reception information. The imaging apparatus according to configuration 1, characterized by the features described above. [Composition 7] When the identification means identifies the predetermined reception information from the list, it excludes reception information from the list that is currently being called and for which a predetermined time has elapsed from the target of identifying the predetermined reception information. An imaging apparatus according to any one of configurations 1 to 6, characterized by the above. [Structure 8] The system further includes a display means for displaying the list acquired by the acquisition means, The display means displays the incoming call information from the list that is currently being called and for which the predetermined time has elapsed, in a way that allows for identification. The imaging device according to configuration 7, characterized by the features described above. [Composition 9] When the aforementioned identification means identifies the predetermined reception information from the list, it excludes reception information being captured by other imaging devices different from the said imaging device from the target of identifying the predetermined reception information. An imaging apparatus according to any one of configurations 1 to 6, characterized by the above. [Configuration 10] The system further includes a display means for displaying the list acquired by the acquisition means, The display means displays the reception information being captured by the other imaging device in an identifiable manner. The imaging apparatus according to configuration 9, characterized by the features described herein. [Composition 11] The aforementioned identification means, when identifying the predetermined reception information from the list, excludes reception information that has already been examined from the target of identifying the predetermined reception information. An imaging apparatus according to any one of configurations 1 to 6, characterized by the above. [Composition 12] The system further includes a display means for displaying the list acquired by the acquisition means, The display means displays the completed consultation registration information in an identifiable manner. The imaging apparatus according to configuration 11, characterized by the features described above. [Composition 13] The imaging device is configured to communicate with the management device via a network, The display means further comprises a first display mode for displaying the list acquired by the acquisition means, and a second display mode for displaying the reception information for input. The display means switches between the first display mode and the second display mode depending on the communication status between the imaging device and the network. An imaging apparatus according to any one of configurations 1 to 12, characterized by the features described herein. [Composition 14] The aforementioned management device is a medical information system management device, The subject in question is a patient, The aforementioned reception information is the reception number. An imaging apparatus according to any one of configurations 1 to 13, characterized by the features described herein. [Method 1] A control method for an imaging device configured to communicate with a management device, The acquisition step involves obtaining a list containing subject reception information from the management device, A selection step to identify predetermined reception information from the list obtained in the acquisition step, A storage control step that performs control to store in association the predetermined reception information identified in the specified step and the image data of the subject in the predetermined reception information, A control method for an imaging device, characterized by having the following features. [Program 1] A program for causing a computer to function as one of the means of the imaging apparatus described in any one of configurations 1 to 14. [Explanation of Symbols]

[0204] 100: Imaging system, 110: Imaging device, 111: Communication line, 120: Medical information system management device, 130: Medical information system terminal device, 140: Data management device, 150: Imaging system control device, 160: Network, 201: Imaging unit, 202, 301: CPU, 203, 302: ROM, 204, 303: RAM, 205, 304: Display unit, 206, 306: Input unit, 207, 307: Media drive, 208, 308: Network I / F, 209: Image processing unit, 210: File generation unit, 211, 309: Bus, 305: HDD, P: Patient, P1: Affected area, P2: Reception number ticket

Claims

1. An imaging device configured to communicate with a management device, An acquisition means for acquiring a list containing subject reception information from the management device, A means for identifying predetermined reception information from the list acquired by the acquisition means, A storage control means that performs control to store in association the predetermined reception information identified by the identification means and the image data of the subject in the predetermined reception information, An imaging device characterized by having the following features.

2. The system further includes a display means for displaying the list acquired by the acquisition means, The identification means identifies the reception information selected from the list displayed on the display means as the predetermined reception information. The imaging apparatus according to feature 1.

3. The system further includes an input means for inputting the aforementioned reception information, The identification means identifies the reception information entered by the input means as the predetermined reception information. The imaging apparatus according to feature 1.

4. The aforementioned identification means identifies the currently called reception information from the list as the predetermined reception information. The imaging apparatus according to feature 1.

5. The identification means identifies the reception information from the list that is currently being called and matches the location where the previous photo was taken as the predetermined reception information. The imaging apparatus according to feature 1.

6. The aforementioned identification means identifies the reception information of a photographer who is currently being called from the list and who matches the photographer who took the previous photograph, as the predetermined reception information. The imaging apparatus according to feature 1.

7. When the identification means identifies the predetermined reception information from the list, it excludes reception information from the list that is currently being called and for which a predetermined time has elapsed from the target of identifying the predetermined reception information. The imaging apparatus according to feature 1.

8. The system further includes a display means for displaying the list acquired by the acquisition means, The display means displays the incoming call information from the list that is currently being called and for which the predetermined time has elapsed, in a way that allows for identification. The imaging apparatus according to feature 7.

9. When the aforementioned identification means identifies the predetermined reception information from the list, it excludes reception information being captured by other imaging devices different from the said imaging device from the target of identifying the predetermined reception information. The imaging apparatus according to feature 1.

10. The system further includes a display means for displaying the list acquired by the acquisition means, The display means displays the reception information being captured by the other imaging device in an identifiable manner. The imaging apparatus according to feature 9.

11. The aforementioned identification means, when identifying the predetermined reception information from the list, excludes reception information that has already been examined from the target of identifying the predetermined reception information. The imaging apparatus according to feature 1.

12. The system further includes a display means for displaying the list acquired by the acquisition means, The display means displays the completed consultation registration information in an identifiable manner. The imaging apparatus according to feature 11.

13. The imaging device is configured to communicate with the management device via a network, The display means further comprises a first display mode for displaying the list acquired by the acquisition means, and a second display mode for displaying the reception information for input. The display means switches between the first display mode and the second display mode depending on the communication status between the imaging device and the network. The imaging apparatus according to feature 1.

14. The aforementioned management device is a medical information system management device, The subject in question is a patient, The aforementioned reception information is the reception number. The imaging apparatus according to feature 1.

15. A control method for an imaging device configured to communicate with a management device, The acquisition step involves obtaining a list containing subject reception information from the management device, A selection step to identify predetermined reception information from the list obtained in the acquisition step, A storage control step that performs control to store in association the predetermined reception information identified in the specified step and the image data of the subject in the predetermined reception information, A control method for an imaging device, characterized by having the following features.

16. A program for causing a computer to function as one of the means of an imaging apparatus according to any one of claims 1 to 14.

Images