JP7412927B2 - Medical information management system, medical information management device, and medical information management method - Google Patents

Description

Embodiments of the present invention relate to a medical information management system, a medical information management device, and a medical information management method.

When a patient is transported to a hospital by an ambulance or the like, there is a desire to use medical information such as images and vital signs of the patient acquired in the vehicle during transport at the destination hospital. As a technology to meet this demand, for example, based on patient identification information given before being transported to a hospital, medical information acquired in the vehicle during transportation and test data obtained at the destination hospital can be combined. Techniques for associating are known.

However, the above technology has a problem in that it is not possible to associate an order issued in a hospital with data related to a patient that is collected not based on the order.

Japanese Patent Application Publication No. 2016-136386 JP2016-200968A

The problem to be solved by the present invention is to easily associate data regarding a patient that is collected not based on an order at a destination hospital.

The medical information management system of the embodiment includes a storage device and a medical information management device. The storage device stores patient medical information collected by an off-order device that collects medical information not based on an order issued by a hospital. The medical information management device acquires medical information of a patient using the hospital from among the medical information stored in the storage device. The medical information management device includes a medical information acquisition section and an association section. The medical information acquisition unit acquires medical information of a patient using the hospital from among the medical information stored in the storage device. The association unit obtains patient identification information that uniquely identifies a patient using the hospital within the hospital, and associates the obtained medical information of the patient with the patient identification information.

FIG. 1 is a diagram showing an example of the configuration of a medical information management system. FIG. 2 is a diagram for explaining processing before patient arrival according to the first embodiment. FIG. 3 is a diagram for explaining processing after the patient arrives according to the first embodiment. FIG. 4 is a block diagram of the medical information management system according to the first embodiment. FIG. 5 is a diagram showing an example of a patient table according to the first embodiment. FIG. 6 is a diagram showing an example of an image table according to the first embodiment. FIG. 7 is a diagram showing another example of the image table according to the first embodiment. FIG. 8 is a block diagram showing part of the hospital information system according to the first embodiment. FIG. 9 is a diagram showing an example of a DICOM table according to the first embodiment. FIG. 10 is a sequence diagram showing an example of processing before patient arrival according to the first embodiment. FIG. 11 is a sequence diagram showing an example of processing after patient arrival according to the first embodiment. FIG. 12 is a diagram for explaining processing before patient arrival according to the second embodiment. FIG. 13 is a diagram for explaining processing after patient arrival according to the second embodiment. FIG. 14 is a diagram showing an example of a patient table according to the second embodiment. FIG. 15 is a diagram showing an example of an image table according to the second embodiment. FIG. 16 is a sequence diagram showing an example of processing before patient arrival according to the second embodiment. FIG. 17 is a sequence diagram showing an example of processing after patient arrival according to the second embodiment. FIG. 18 is a diagram for explaining processing before patient arrival according to the third embodiment. FIG. 19 is a block diagram of a medical information management system according to the third embodiment. FIG. 20 is a diagram illustrating an example of an image table according to the third embodiment. FIG. 21 is a sequence diagram showing an example of processing before patient arrival according to the third embodiment. FIG. 22 is a flowchart illustrating an example of image data acquisition processing according to the third embodiment. FIG. 23 is a diagram for explaining processing before patient arrival according to the fourth embodiment. FIG. 24 is a diagram illustrating an example of medical information data according to the fourth embodiment. FIG. 25 is a block diagram of a medical information management system according to the fourth embodiment. FIG. 26 is a diagram showing an example of a patient table according to the fourth embodiment. FIG. 27 is a diagram illustrating an example of an application log according to the fourth embodiment. FIG. 28 is a diagram illustrating an example of a device table according to the fourth embodiment. FIG. 29A is a diagram illustrating an example of a medical information table according to the fourth embodiment. FIG. 29B is a diagram illustrating an example of a medical information table according to the fourth embodiment. FIG. 30 is a sequence diagram illustrating an example of medical information acquisition processing according to the fourth embodiment. FIG. 31 is a flowchart illustrating an example of medical information update processing according to the fourth embodiment.

Embodiments of a medical information management system, a medical information management device, and a medical information management method will be described in detail below with reference to the drawings. The medical information management system according to the present embodiment associates medical information such as images of a patient collected from an ambulance under the jurisdiction of a fire department headquarters, fire union, etc. with medical information at a hospital, etc. to which the patient is transported. .

FIG. 1 is a diagram showing an example of the configuration of a medical information management system. As shown in FIG. 1, the medical information management system 1 according to the present embodiment includes management devices 10a and 10b, transport devices 20a and 20b, an image server 30, RIS (Radiology Information System) 40a and 40b, and PACS. (Picture Archiving and Communication Systems) 50a and 50b.

In the medical information management system 1, the management devices 10a and 10b, the transport devices 20a and 20b, and the image server 30 are connected to each other via a wired or wireless network NW so as to be able to communicate with each other. Further, the management device 10a, the RIS 40a, and the PACS 50a are each connected to a hospital information system (not shown) configured in the hospital HPa via a wired or wireless in-hospital network NWa so as to be able to communicate with each other. Similarly, the management device 10b, the RIS 40b, and the PACS 50b are connected to a hospital information system (not shown) configured in the hospital HPb so as to be able to communicate with each other via a wired or wireless in-hospital network NWb. The in-hospital networks NWa and NWb include server devices (not shown) included in modalities, which will be explained later, and other systems in the hospital such as a hospital accounting system (not shown) and an electronic medical record system (not shown). ) are also connected.

The medical information management system 1 shown in FIG. 1 includes two management devices 10a and 10b and two transport devices 20a and 20b, but the number of each device is arbitrary. For example, three or more management devices may be used. may be connected to the network NW. In addition, below, when expressing the management apparatuses 10a and 10b without distinguishing them, they may be simply written as "management apparatus 10." Similarly, regarding the transport devices 20a and 20b, RIS40a and 40b, PACS50a and 50b, hospitals HPa and HPb, and hospital networks NWa and NWb, "transport device 20", "RIS40", "PACS50", "hospital HP", It may be written as "in-hospital network NW".

The management device 10 shown in FIG. 1 is, for example, a computer installed in hospitals HPa and HPb. For example, the management device 10a acquires, from the image server 30, medical information including an image of the patient being transported that was acquired before arriving at the hospital HPa, and information that identifies the patient at the hospital HPa that is acquired from the RIS 40a. to associate with. The management device 10a also converts the acquired medical information into a DICOM (Digital Imaging and Communications in Medicine) format and outputs it to the PACS 50a. In addition, in the following, the patient's medical information obtained before arriving at the hospital will be referred to as "pre-arrival medical information", and the identifier that uniquely identifies the patient at the hospital will be referred to as "emergency ID (Identifer)". There is.

The transport device 20 shown in FIG. 1 is, for example, a device mounted on a moving body such as an ambulance that transports a patient. The transport device 20 takes images of the patient being transported, and transmits pre-arrival medical information including the images to the image server 30. Note that the transport device 20 is an example of a non-ordered device. Moreover, in this embodiment, one transport device 20 is mounted on each mobile body such as an ambulance, and the mobile body and the transport device 20 correspond to each other on a one-to-one basis.

The image server 30 shown in FIG. 1 is a computer installed at, for example, a fire department headquarters. The image server 30 acquires pre-arrival medical information including images from the transport device 20 and the like, and stores it in a storage device. The image server 30 transmits the stored pre-arrival medical information in response to requests from the management devices 10a and 10b, for example. Note that the image server 30 is an example of a storage device.

The RIS 40 shown in FIG. 1 is a known computer that is installed, for example, in hospitals HPa and HPb and manages orders regarding tests, diagnoses, etc. performed at the hospitals. For example, when the RIS 40a receives an input of a schedule for transporting an emergency patient to the hospital HPa, it issues an emergency ID as an identifier that uniquely identifies the patient corresponding to the order, and outputs it to the management device 10a and the PACS 50a.

The PACS 50 shown in FIG. 1 is a computer installed in, for example, hospitals HPa and HPb. The PACS 50 is a known computer that acquires medical information in DICOM format and stores it in a storage device. The PACS 50a, for example, acquires medical information converted into DICOM format from the management device 10a and stores it in a storage device. Furthermore, the PACS 50a acquires medical information including images of the patient acquired after arriving at the hospital HPa from modalities such as CR (Computed Radiography), CT (Computed Tomography), and MRI (Magnetic Resonance Imaging). Note that medical information of a patient acquired after arriving at a hospital may be referred to as "post-arrival medical information." Furthermore, pre-arrival medical information is an example of medical information collected before the hospital issues an order, that is, patient medical information collected by a non-ordered device such as the transport device 20 and not based on an order issued by the hospital. It is. Further, the post-arrival medical information is an example of patient medical information collected based on an order issued by a hospital.

(First embodiment)
First, a first embodiment will be described. In the first embodiment, the management device 10a stores the patient's pre-arrival medical information as a "Device ID" that uniquely identifies the transport device 20a that captured the patient's image, and information regarding the patient's arrival time at the hospital. Specify using Note that "Device ID" is an example of identification information of the non-ordered device, and "Arrival time" is an example of the arrival status. For example, the Device ID of the transport device 20a is "Camera-A", and the Device ID of the transport device 20b is "Camera-B". Note that the DeviceID may also be assigned to devices other than the transport device 20, as described below.

First, the process until the patient arrives at the hospital HPa will be explained. FIG. 2 is a diagram for explaining processing before patient arrival according to the first embodiment. Note that the order of processes shown in the following figures is an example, and the order of execution of some processes may be reversed, or a plurality of processes may be executed in parallel at the same time.

As shown in FIG. 2, first, the transport device 20a mounted on the ambulance transporting the patient takes an image of the patient at the time "12:00" and uses an "image ID" which is an identifier that uniquely identifies the image. (1. Photography). The transport device 20a transmits the photographed image to the image server 30 along with the "image ID" and "Device ID" (2. Transfer). The image server 30 stores the image transmitted from the transport device 20a in association with an image ID and a Device ID.

On the other hand, the hospital HPa is notified of the schedule for transporting the patient by ambulance together with the Device ID of the transport device 20a mounted on the ambulance. Note that the transportation schedule is notified, for example, from the transportation device 20a, but is not limited to this, and may be notified from the image server 30 or other devices. In this case, the management device 10a of the hospital HPa refers to the image stored in the image server 30 (see 3. Image). At this time, the management device 10a refers to images whose arrival time is not associated, that is, whose arrival time is "unregistered" among the images associated with the notified Device ID.

Next, the RIS 40a issues an "emergency ID" for identifying the patient in the hospital HPa, and transmits it to the management device 10a (4. Emergency ID numbering). The management device 10a associates the acquired emergency ID with the DeviceID and arrival time (4. Patient association). Note that the "emergency ID" is an example of patient identification information. Moreover, "3. Image reference", "4. Emergency ID numbering", and "4. Patient association" may be executed simultaneously in parallel, or may be executed in reverse order.

Next, processing after the patient arrives at the hospital HPa will be explained. FIG. 3 is a diagram for explaining processing after the patient arrives according to the first embodiment. As shown in FIG. 3, the patient transported by the ambulance equipped with the transport device 20a arrives at the hospital HPa at time "12:10" (5. Arrival). At this time, the transport device 20a transmits the arrival time "12:10" to the image server 30 (5. Registration).

On the other hand, at the hospital HPa, an examination is performed on the arriving patient using a modality to which an emergency ID and a worklist have been assigned in advance from the RIS 40a (6. Examination). The patient's image acquired through the examination is transmitted to the PACS 50a as DICOM format data associated with the emergency ID (6. Transfer). The PACS 50a stores the acquired DICOM format data as medical information after arrival.

Furthermore, when the patient arrives, the management device 10a downloads pre-arrival medical information including the patient's image from the image server 30 (7. Download). At this time, the management device 10a downloads an image whose arrival time matches the patient's arrival time, that is, an image whose arrival time is "12:10" from among the images associated with the Device ID notified in advance.

Next, the management device 10a converts the downloaded image into DICOM format data together with the associated image ID, emergency ID, and Device ID (8. Conversion), and sends it to the PACS 50a as pre-arrival medical information (9. .transfer). The PACS 50a stores the received pre-arrival medical information converted to DICOM format. Thereby, in the PACS 50a, the pre-arrival medical information and the post-arrival medical information are associated with the same emergency ID.

Next, the functions of the medical information management system 1 that executes the processes shown in FIGS. 2 and 3 will be explained. FIG. 4 is a block diagram of the medical information management system according to the first embodiment. As shown in FIG. 4, the management device 10a connected to the hospital network NWa of the hospital HPa includes a communication I/F (Interface) 11, an input I/F 12, a display 13, a storage circuit 14, and a processing circuit 15. Equipped with. Note that the management device 10b connected to the hospital network NWb of the hospital HPb also has the same configuration as the management device 10a, so hereinafter the management devices 10a and 10b may be described as the management device 10 without distinguishing them. .

The communication I/F 11 is connected to the processing circuit 15 and controls transmission and communication of various data performed with various devices connected via the network NW and the in-hospital network NWa. For example, the communication I/F 11 is realized by a network card, a network adapter, a NIC (Network Interface Controller), or the like.

The input I/F 12 is connected to the processing circuit 15 , converts an input operation received from the administrator (not shown) of the management device 10 into an electrical signal, and outputs the electric signal to the processing circuit 15 . For example, the input I/F 12 is a switch button, a mouse, a keyboard, a touch panel, or the like.

The display 13 is connected to the processing circuit 15 and displays various information and various image data output from the processing circuit 15. For example, the display 13 is realized by a liquid crystal monitor, a CRT (cathode ray tube) monitor, a touch panel, or the like.

The storage circuit 14 is connected to the processing circuit 15 and stores various data. For example, the memory circuit 14 is realized by a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, a hard disk, an optical disk, or the like. In this embodiment, the storage circuit 14 stores, for example, a patient table 141.

The patient table 141 stores information that associates the pre-arrival medical information obtained from the image server 30 with the emergency ID obtained from the RIS 40. In this embodiment, the patient table 141 stores, for example, information regarding images included in the pre-arrival medical information. Information stored in the patient table 141 is stored, for example, by a first acquisition function 151, a second acquisition function 152, a conversion function 153, and a registration function 154, which will be described later.

FIG. 5 is a diagram showing an example of a patient table according to the first embodiment. For example, as shown in FIG. 5, the patient table 141 associates "image ID", "Device ID", "emergency ID", "arrival time", and "image ID (after conversion)". It is information. Here, "image ID" in FIG. 5 indicates an identifier that uniquely identifies an image included in the pre-arrival medical information. “DeviceID” indicates an identifier that uniquely identifies the transport device 20 that acquired the image. “Emergency ID” indicates the emergency ID acquired from the RIS 40. "Arrival time" indicates the time when the patient identified by the emergency ID arrived at the hospital. “Image ID (after conversion)” indicates an identifier that uniquely identifies the image specified by the image ID that has been converted into the DICOM format.

For example, the first record shown in Figure 5 indicates that the pre-arrival medical information including the image with image ID "Pic0002" was acquired by the transport device with Device ID "Camera-A" and was given the emergency ID "EM011". Show that. Furthermore, the first record shown in FIG. 5 indicates that the patient identified by the emergency ID arrived at the hospital on "7/31 12:10." Further, the first record shown in FIG. 5 indicates that the image with the image ID "Pic0002" has been converted to the image with the image ID "Dic01102." Similarly, the second record shown in Figure 5 also includes pre-arrival medical information including the image with image ID "Pic0003", as well as pre-arrival medical information with Device ID "Camera-A", as well as the pre-arrival medical information in the first record. This indicates that it was acquired by the transport device and that the emergency ID "EM011" was assigned. That is, since the second record shown in FIG. 5 is a record regarding pre-arrival medical information regarding the same patient as the first record, the arrival time is also the same as that of the first record. Furthermore, the second record shown in FIG. 5 indicates that the image with image ID "Pic0003" has been converted to the image with image ID "Dic01103."

Note that in FIG. 5, unregistered items in each record are, for example, blank fields. For example, if the patient identified by the Device ID "Camera-A" and the emergency ID "EM011" has not yet arrived at the hospital, the arrival time item is blank. Further, for example, if each image has not yet been converted to the DICOM format, the image ID (after conversion) item 1411 will be blank.

Returning to FIG. 4, the processing circuit 15 controls the overall operation of the management device 10 by executing a first acquisition function 151, a second acquisition function 152, a conversion function 153, and a registration function 154. Here, the first acquisition function 151 is an example of a first acquisition unit. The second acquisition function 152 is an example of a second acquisition unit. The conversion function 153 is an example of a conversion unit. Further, the registration function 154 is an example of an association unit. Here, for example, each processing function of a first acquisition function 151, a second acquisition function 152, a conversion function 153, and a registration function 154, which are components of the processing circuit 15 shown in FIG. 4, is in the form of a program executable by a computer. is recorded in the memory circuit 14. The processing circuit 15 reads each program from the storage circuit 14 and executes each read program to implement a function corresponding to each program. In other words, the processing circuit 15 in a state where each program has been read has each function shown in the processing circuit 15 of FIG.

Note that all the processing functions of the first acquisition function 151, the second acquisition function 152, the conversion function 153, and the registration function 154 may be recorded in the storage circuit 14 in the form of one program executable by a computer. For example, such a program is also referred to as a medical information management program. In this case, the processing circuit 15 reads the medical information management program from the storage circuit 14 and executes the read medical information management program to perform the first acquisition function 151, the second acquisition function 152, and the conversion function corresponding to the medical information management program. A function 153 and a registration function 154 are realized.

The first acquisition function 151 in the processing circuit 15 acquires pre-arrival medical information from the image server 30. For example, the first acquisition function 151 accesses the image server 30 via the network NW using input of the notified Device ID as a start trigger. The first acquisition function 151 refers to an image stored in the image server 30 and associated with the Device ID. The first acquisition function 151 also outputs the image ID of the acquired image and the arrival time associated with the image to the registration function 154.

The first acquisition function 151 also downloads image data from the image server 30 using input of a patient arrival notification as a trigger. The first acquisition function 151 downloads pre-arrival medical information including image data corresponding to the image ID and Device ID registered in the patient table 141 and outputs it to the conversion function 153.

The second acquisition function 152 acquires the emergency ID from the RIS 40a. For example, the second acquisition function 152 receives the emergency ID from the RIS 40a and outputs it to the registration function 154.

The conversion function 153 converts image data into DICOM format data. Upon receiving the output of the pre-arrival medical information including image data from the first acquisition function 151, the conversion function 153 converts the image into DICOM format data along with the associated image ID, Device ID, and emergency ID. The conversion function 153 transmits the converted pre-arrival medical information to the PACS 50a.

The registration function 154 associates the pre-arrival medical information of the transported patient with the emergency ID. When the registration function 154 receives the output of the image ID and arrival time from the first acquisition function 151, it determines whether or not the "arrival time" of the pre-arrival medical information with the matching Device ID is unregistered. The registration function 154 stores the image ID and Device ID of the pre-arrival medical information whose arrival time is determined to be unregistered in the patient table 141 in association with the emergency ID output from the second acquisition function 152.

Next, the transport device 20 includes a camera 21, a transmission data generation section 22, and a communication I/F 23, as shown in FIG. Note that since the transport devices 20a and 20b have the same configuration, hereinafter, the transport devices 20a and 20b may be described as the transport device 20 without distinguishing between them.

The camera 21 of the transport device 20 acquires an image of the patient and outputs the image data to the transmission data generation section 22. The camera 21 is, for example, an optical camera, but is not limited to this, and may be other devices such as an X-ray CT device or an ultrasonic diagnostic device.

The transmission data generation unit 22 adds identification information to image data and generates pre-arrival medical information to be transmitted to the image server 30 . The transmission data generation unit 22 issues an image ID to the image data, assigns it to the image data together with the Device ID assigned to the transport device 20, and transmits it to the image server 30 via the communication I/F 23. Further, the transmission data generation unit 22 transmits the patient's transportation schedule including the Device ID to the hospital HPa via the communication I/F 23.

The communication I/F 23 controls the transmission and communication of various data performed with other devices connected via the network NW. The communication I/F 23 transmits, for example, the pre-arrival medical information output from the transmission data generation unit 22 to the image server 30. For example, the communication I/F 23 is realized by a network card, a network adapter, or the like.

The image server 30 includes a communication I/F 31, an input I/F 32, a display 33, a storage circuit 34, and a processing circuit 35, as shown in FIG.

The communication I/F 31 is connected to the processing circuit 35 and controls transmission and communication of various data performed with various devices connected via the network NW. For example, the communication I/F 31 is realized by a network card, a network adapter, or the like.

The input I/F 32 is connected to the processing circuit 35 , converts an input operation received from an administrator (not shown) of the image server 30 into an electrical signal, and outputs the electrical signal to the processing circuit 35 . For example, the input I/F 32 is a switch button, a mouse, a keyboard, a touch panel, or the like.

The display 33 is connected to the processing circuit 35 and displays various information outputted from the processing circuit 35. For example, the display 33 is realized by a liquid crystal monitor, a CRT monitor, a touch panel, or the like.

The storage circuit 34 is connected to the processing circuit 35 and stores various data. For example, the storage circuit 34 is realized by a semiconductor memory element such as a RAM or a flash memory, a hard disk, an optical disk, or the like. In this embodiment, the storage circuit 34 stores, for example, an image table 341.

The image table 341 stores information regarding pre-arrival medical information acquired from the transport device 20. In this embodiment, the image table 341 is set, for example, by an acquisition function 351 and a registration function 352, which will be described later. For example, as shown in FIG. 6, the image table 341 stores "image ID," "Device ID," and "arrival time" in association with each other.

FIG. 6 is a diagram showing an example of an image table according to the first embodiment. Each item shown in FIG. 6 is the same as each item shown in FIG. 5, so detailed explanation will be omitted. In the example shown in FIG. 6, the arrival times 3411 corresponding to the image IDs "Pic0002" and "Pic0003" and the Device ID "Camera-A" are unregistered. That is, the image table 341 shown in FIG. 6 indicates that the patient corresponding to the image ID and Device ID has not yet arrived at the hospital.

Returning to FIG. 4, the processing circuit 35 controls the overall operation of the image server 30 by executing an acquisition function 351 and a registration function 352. Here, for example, each processing function, such as an acquisition function 351 and a registration function 352, which are components of the processing circuit 35 shown in FIG. 4, is recorded in the storage circuit 34 in the form of a computer-executable program. The processing circuit 35 reads each program from the storage circuit 34 and executes each read program to implement a function corresponding to each program. In other words, the processing circuit 35 in a state in which each program has been read has each function shown in the processing circuit 35 of FIG.

Note that all the processing functions of the acquisition function 351 and the registration function 352 may be recorded in the storage circuit 34 in the form of one program executable by a computer. In this case, the processing circuit 35 realizes the acquisition function 351 and the registration function 352 by reading a program from the storage circuit 34 and executing the read program.

The acquisition function 351 in the processing circuit 35 acquires pre-arrival medical information from the transport device 20. For example, upon receiving pre-arrival medical information including image data from the transport device 20 via the network NW, the acquisition function 351 stores the image data in the storage circuit 34 and also stores the image data associated with the pre-arrival medical information. Information such as the ID and Device ID is output to the registration function 352.

The registration function 352 registers information regarding pre-arrival medical information in the image table 341. The registration function 352 registers the image ID and Device ID output from the acquisition function 351 in the image table 341 shown in FIG. Further, when the registration function 352 acquires information regarding the arrival time from the transport device 20, as shown in FIG. 7, the registration function 352 stores the information in association with the image ID and Device ID stored in the image table 341.

FIG. 7 is a diagram showing another example of the image table according to the first embodiment. In the "arrival time" item 3412 shown in FIG. 7, "7/31 12:10" is registered in the arrival time column that was blank in FIG. That is, the image table 341-1 shown in FIG. 7 indicates that the patients corresponding to the image IDs "Pic0002" and "Pic0003" and the device ID "Camera-A" arrived at the hospital at "7/31 12:10". show.

Next, the functions of the medical information management system 1 that executes the processing shown in FIG. 3 will be explained. FIG. 8 is a block diagram showing part of the hospital information system according to the first embodiment. As shown in FIG. 8, in addition to the management device 10a, an RIS 40a and a PACS 50a are communicably connected to the in-hospital network NWa within the hospital HPa included in the medical information management system 1. Note that since the RIS 40b and the PACS 50b are similarly connected to the in-hospital network NWb of the hospital HPb, the RIS 40a and 40b or the PACS 50a and 50b may be described below without distinguishing between them.

As shown in FIG. 8, the RIS 40a includes a communication I/F 41, an input I/F 42, a display 43, a storage circuit 44, and a processing circuit 45.

The communication I/F 41 is connected to the processing circuit 45 and controls transmission and communication of various data performed with various devices connected via the in-hospital network NWa. For example, the communication I/F 41 is realized by a network card, a network adapter, or the like.

The input I/F 42 is connected to the processing circuit 45 , converts an input operation received from the administrator (not shown) of the RIS 40 a into an electrical signal, and outputs the electric signal to the processing circuit 45 . For example, the input I/F 42 is a switch button, a mouse, a keyboard, a touch panel, or the like.

The display 43 is connected to the processing circuit 45 and displays various information outputted from the processing circuit 45. For example, the display 43 is realized by a liquid crystal monitor, a CRT monitor, a touch panel, or the like.

The storage circuit 44 is connected to the processing circuit 45 and stores various data. For example, the storage circuit 44 is realized by a semiconductor memory element such as a RAM or a flash memory, a hard disk, an optical disk, or the like.

The processing circuit 45 controls the overall operation of the RIS 40a by executing the issuing function 451. Here, for example, the issuing function 451, which is a component of the processing circuit 45 shown in FIG. 8, is recorded in the storage circuit 44 in the form of a computer-executable program. The processing circuit 45 reads each program from the storage circuit 44 and executes each read program to implement a function corresponding to each program. In other words, the processing circuit 45 in a state where each program has been read has each function shown in the processing circuit 45 of FIG.

Note that all the processing functions of the issuing function 451 may be recorded in the storage circuit 44 in the form of one program executable by a computer. In this case, the processing circuit 45 realizes the issuing function 451 by reading a program from the storage circuit 44 and executing the read program.

The issuing function 451 in the processing circuit 45 issues an emergency ID. For example, the issuing function 451 issues an emergency ID using the input of the notified Device ID as a trigger, and outputs the emergency ID to the management device 10a and the PACS 50a via the hospital network NWa.

The registration function 452 registers information regarding pre-arrival medical information in the image table 441. The registration function 452 registers the image ID and Device ID output from the issuing function 451 in the image table 441. Further, when the registration function 452 acquires information regarding the arrival time from the transport device 20, as shown in FIG. 7, the registration function 452 stores the information in association with the image ID and Device ID stored in the image table 441.

As shown in FIG. 8, the PACS 50a includes a communication I/F 51, an input I/F 52, a display 53, a storage circuit 54, and a processing circuit 55.

The communication I/F 51 is connected to the processing circuit 55 and controls transmission and communication of various data performed with various devices connected via the in-hospital network NWa. For example, the communication I/F 51 is realized by a network card, a network adapter, or the like.

The input I/F 52 is connected to the processing circuit 55 , converts an input operation received from the administrator (not shown) of the PACS 50 a into an electrical signal, and outputs the electrical signal to the processing circuit 55 . For example, the input I/F 52 is a switch button, a mouse, a keyboard, a touch panel, or the like.

The display 53 is connected to the processing circuit 55 and displays various information outputted from the processing circuit 55. For example, the display 53 is realized by a liquid crystal monitor, a CRT monitor, a touch panel, or the like.

The storage circuit 54 is connected to the processing circuit 55 and stores various data. For example, the memory circuit 54 is realized by a semiconductor memory element such as a RAM or a flash memory, a hard disk, an optical disk, or the like. In this embodiment, the storage circuit 54 stores, for example, a DICOM table 541.

The DICOM table 541 stores information regarding DICOM format data. In this embodiment, the DICOM table 541 is set, for example, by an acquisition function 551 that will be described later. Note that the DICOM table 541 is an example of a storage unit.

FIG. 9 is a diagram showing an example of a DICOM table according to the first embodiment. For example, as shown in FIG. 9, the DICOM table 541 stores "image ID," "Device ID," "emergency ID," and "arrival time" in association with each other. For example, the first record shown in FIG. 9 indicates that the image with the image ID "Dic01102" was acquired by the transport device with the Device ID "Camera-A" and was given the emergency ID "EM011". Furthermore, the first record shown in FIG. 9 indicates that the patient identified by the emergency ID arrived at the hospital on "7/31 12:10." The same applies to the image whose image ID is "Dic01103" shown in the second row record shown in FIG. Note that these images are images that have been output from the management device 10a and converted into DICOM format data, and are stored in the image ID (after conversion) item 1411 of the patient table 141 shown in FIG. 5, for example. It can be specified by the image ID.

The DICOM table 541 also stores information regarding images acquired from modalities other than the management device 10a, as shown in the third record and fourth record 5411 shown in FIG. For example, the third record shown in FIG. 9 is an image whose image ID is "Dic01102" and which is associated with the image ID "CT0101" acquired by a modality (not shown) whose Device ID is "CT-A". and the same emergency ID and arrival time as the image whose image ID is "Dic01103" are registered. In the fourth record shown in FIG. 9, a similar emergency ID and arrival time are registered in the image ID "MR0201" acquired by a modality (not shown) whose Device ID is "MR-A". That is, the DICOM table 541 shown in FIG. 9 includes an image whose image ID is "Dic01102" and an image whose image ID is "Dic01103" obtained from the management device 10a, and an image whose image ID obtained from the modality is "CT0101". ” and the image whose image ID is “MR0201” are related to the same transported patient.

Returning to FIG. 8, the processing circuit 55 controls the overall operation of the PACS 50a by executing the acquisition function 551. Here, for example, the acquisition function 551, which is a component of the processing circuit 55 shown in FIG. 8, is recorded in the storage circuit 54 in the form of a computer-executable program. The processing circuit 55 reads each program from the storage circuit 54 and executes each read program to implement a function corresponding to each program. In other words, the processing circuit 55 in a state where each program has been read has each function shown in the processing circuit 55 of FIG.

Note that all the processing functions of the acquisition function 551 may be recorded in the storage circuit 54 in the form of one program executable by a computer. In this case, the processing circuit 55 realizes the acquisition function 551 by reading a program from the storage circuit 54 and executing the read program.

The acquisition function 551 in the processing circuit 55 acquires image data and stores information regarding the image data in the DICOM table 541. For example, the acquisition function 551 acquires image data converted into DICOM format from the management device 10a via the hospital network NWa. Similarly, the acquisition function 551 acquires DICOM format image data from the modality, for example, via the in-hospital network NWa. The acquisition function 551 then stores the image ID, Device ID, emergency ID, and arrival time associated with the acquired image data in the DICOM table 541.

Next, the procedure of processing by the medical information management system 1 according to the first embodiment will be explained using FIGS. 10 and 11. FIG. 10 is a sequence diagram showing an example of processing before patient arrival according to the first embodiment. Here, steps S31 and S32 in FIG. 10 are realized, for example, by the processing circuit 15 of the management device 10a reading out the program corresponding to the first acquisition function 151 from the storage circuit 14 and executing it. Further, step S43 is realized, for example, by the processing circuit 15 reading out a program corresponding to the second acquisition function 152 from the storage circuit 14 and executing it. Further, step S44 is realized, for example, by the processing circuit 15 reading out a program corresponding to the registration function 154 from the storage circuit 14 and executing it.

For example, as shown in FIG. 10, in the medical information management system 1 according to the present embodiment, first, the transport device 20a uses the camera 21 to take an image of a patient being transported (step S11). The transport device 20a associates the image ID and Device ID with the photographed image data and transmits the data to the image server 30 (step S21).

Subsequently, upon acquiring the image data, image ID, and Device ID, the image server 30 registers the image ID and Device ID in the image table 341 (step S22). Next, upon acquiring the Device ID, the processing circuit 15 refers to the image stored in the image server 30 using the Device ID (step S31). The processing circuit 15 acquires image data and image ID corresponding to the Device ID (step S32).

On the other hand, upon acquiring the Device ID, the RIS 40a issues an emergency ID that identifies the patient being transported (step S41). The RIS 40a transmits the issued emergency ID to the PACS 50a (step S42) and also to the management device 10a (step S43). The processing circuit 15 stores the emergency ID obtained from the RIS 40a in association with the image data obtained from the image server 30 (step S44).

Next, the processing in the medical information management system 1 after the patient arrives will be explained. FIG. 11 is a sequence diagram showing an example of processing after patient arrival according to the first embodiment. Here, step S71 in FIG. 11 is realized, for example, by the processing circuit 15 of the management device 10a reading out the program corresponding to the first acquisition function 151 from the storage circuit 14 and executing it. Further, step S72 is realized, for example, by the processing circuit 15 reading out a program corresponding to the registration function 154 from the storage circuit 14 and executing it. Further, steps S81 and S91 are realized, for example, by the processing circuit 15 reading out a program corresponding to the conversion function 153 from the storage circuit 14 and executing it.

First, when the patient arrives at the hospital (step S51), the transport device 20a transmits the arrival time to the image server 30 (step S52). The image server 30 associates the received arrival time with the Device ID and the image ID and registers it in the image table 341 (step S53).

On the other hand, the PACS 50a acquires an examination image of a patient who has arrived at the hospital from another modality (step S61). The PACS 50a stores the acquired inspection image in the DICOM table 541 in association with the emergency ID (step S62).

The processing circuit 15 accesses the image server 30 and downloads the image data in which the arrival time has been newly registered together with the arrival time (step S71). Next, the processing circuit 15 registers the acquired arrival time in the patient table 141 in association with the emergency ID (step S72). Then, the processing circuit 15 converts the acquired image data into DICOM format (step S81), associates the emergency ID with the converted DICOM data, and transmits it to the PACS 50a (step S91). The PACS 50a stores the DICOM data received from the management device 10a in the DICOM table 541 in association with the emergency ID (step S92).

As described above, according to the first embodiment, the first acquisition function 151 acquires pre-arrival medical information that is medical information of the patient acquired before the patient arrives at the hospital. The second acquisition function 152 acquires patient identification information associated with post-arrival medical information, which is information that identifies a patient at the hospital and is medical information acquired after the patient arrives at the hospital. The registration function 154 then associates the pre-arrival medical information with the patient identification information. Therefore, the medical information management system 1 according to the first embodiment can easily associate data regarding a patient that is collected not based on an order at a destination hospital.

At this time, the first acquisition function 151 may further acquire arrival information regarding the patient's arrival at the hospital as information associated with the pre-arrival medical information. Furthermore, the registration function 154 may associate the pre-arrival medical information that is not associated with the arrival information indicating that the patient has arrived at the hospital with the patient identification information. This can prevent confusion with information about patients who have already arrived at the hospital. Note that the arrival information is an example of the arrival status.

Further, according to the first embodiment, the medical information management system 1 includes a storage device (image server 30) and a management device 10. The storage device stores patient medical information collected by a non-order device that collects medical information not based on an order issued by the hospital HP. A processing circuit 15 of the medical information management device acquires medical information of a patient using the hospital from among the medical information stored in the storage device. A processing circuit 15 of the medical information management device acquires medical information of a patient who uses the hospital from among the medical information stored in the storage device, and uniquely identifies the patient who uses the hospital within the hospital. The present invention includes a processing circuit that acquires patient identification information (emergency ID) and associates the acquired medical information of the patient with the patient identification information. Thereby, data regarding the patient that is collected not based on an order can be easily correlated at the destination hospital.

Further, in the first embodiment, the storage device includes identification information (DeviceID) of the non-ordered device, arrival status (arrival time) at the hospital, and medical information based on the non-ordered device (transport device 20). and may be stored in association with each other. The processing circuit 15 of the medical information management device acquires the identification information of the non-ordered equipment, and acquires the medical information of the patient using the hospital based on the arrival status at the hospital associated with the identification information. You may.

Furthermore, in the first embodiment, the patient identification information may be issued to an order issued by the hospital. The processing circuit 15 of the medical information management device converts the acquired medical information of the patient into medical information based on the in-hospital equipment used for the patient associated with the patient identification information acquired based on the order. The medical information may be converted into the same data format as the information, and the converted medical information may be associated with the patient identification information.

Note that the image ID and device ID in the first embodiment do not need to be able to uniquely identify a patient. For example, the image ID does not need to include information such as a name or identification number for identifying the patient, or be associated with these information in advance.

Although FIG. 5 shows a configuration in which "arrival time" is stored as the arrival status, the embodiment is not limited to this. For example, the patient table 141 may store information on whether or not the patient has already arrived at the hospital. It may be configured such that Alternatively, the patient table 141 or the image table 341 may store information indicating that the patient has not yet arrived at the hospital, and the information may be deleted when the patient arrives at the hospital. Furthermore, although a configuration has been described in which the transport device 20a transmits the arrival time to the image server 30, the embodiment is not limited to this, and the transport device 20a transmits only the arrival notification, and the image server 30 receives the arrival notification. The configuration may be such that the current time is stored as the arrival time. Furthermore, although a configuration has been described in which the arrival time is transmitted to the image server 30 by the transport device 20a, the present invention is not limited to this, and a configuration in which the management device 10a transmits the arrival time may be used.

(Second embodiment)
In the first embodiment described above, a configuration was described in which a transported patient is identified using a combination of the Device ID of the transport device 20a and the arrival time at which the patient arrived at the hospital. In contrast, in the second embodiment, a configuration will be described in which a transported patient is identified using a combination of the Device ID of the transport device 70a, which will be described later, and a transport ID that uniquely identifies the patient transport procedure. . Note that the "conveyance ID" is an example of issue identification information. As the transportation ID, for example, metadata added based on the well-known EBIW (Encounter-Based Imaging Workflow) is used.

First, in the second embodiment, a process until a patient arrives at the hospital HPa shown in FIG. 1 will be described. FIG. 12 is a diagram for explaining processing before patient arrival according to the second embodiment. In the following embodiments, the same parts as those shown in the drawings described above are denoted by the same reference numerals, and redundant explanation will be omitted. Also, regarding the differences in functions between the management device 60a, transport device 70a, and image server 80 shown in FIG. 12 according to the second embodiment and the management device 10a, transport device 20a, and image server 30 according to the first embodiment. will be explained separately later.

As shown in FIG. 12, a transport device 70a mounted on an ambulance transporting a patient photographs an image of the patient and assigns an "image ID" (1. Photographing). At this time, the transport device 70a issues a transport ID "trans002" and transmits it to the hospital HPa (1a. transport ID number).

Further, the transport device 70a transmits the photographed image to the image server 80 along with the "image ID", "Device ID", and "transport ID" (2a. Transfer). The image server 80 stores the image transmitted from the transport device 70a in association with the image ID, Device ID, and transport ID.

On the other hand, the hospital HPa is notified of the schedule for transporting the patient by ambulance together with the Device ID and transport ID of the transport device 70a mounted on the ambulance. In this case, the management device 60a of the hospital HPa refers to the image stored in the image server 80 (see 3a. Image). At this time, the management device 60a refers to the image associated with the notified Device ID and transportation ID. The management device 60a associates the Device ID and transportation ID of the referenced image with the emergency ID acquired from the RIS 40a (4a. Patient association).

Next, processing after the patient arrives at the hospital HPa in the second embodiment will be described. FIG. 13 is a diagram for explaining processing after patient arrival according to the second embodiment. When a patient transported by an ambulance equipped with the transport device 70a arrives at the hospital HPa, the management device 60 downloads pre-arrival medical information including the patient's image from the image server 80 (7a. Download). At this time, the management device 10a downloads the image associated with the Device ID and transport ID notified in advance. The subsequent processing is the same as that in FIG. 3.

Next, the functions of the medical information management system 2 that executes the processes shown in FIGS. 12 and 13 will be explained. The management device 60a in the medical information management system 2 includes a communication I/F (Interface) 11, an input I/F 12, a display 13, a storage circuit 64, and a processing circuit 65. Note that the management device 60b connected to the hospital network NWb of the hospital HPb also has the same configuration as the management device 60a, so hereinafter the management devices 60a and 60b may be described as the management device 60 without distinguishing between them. .

The storage circuit 64 is connected to the processing circuit 65 and stores various data. In this embodiment, the storage circuit 64 stores, for example, a patient table 641.

Similar to the patient table 141, the patient table 641 stores information that associates the pre-arrival medical information acquired from the image server 80 with the emergency ID acquired from the RIS 40. Information stored in the patient table 641 is stored, for example, by a first acquisition function 651, a second acquisition function 152, a conversion function 153, and a registration function 654, which will be described later.

FIG. 14 is a diagram showing an example of a patient table according to the second embodiment. For example, as shown in FIG. 14, the patient table 641 associates "Image ID", "Device ID", "Emergency ID", "Transportation ID", and "Image ID (after conversion)". It is information. The patient table 641 differs from the patient table 141 according to the first embodiment shown in FIG. 5 in that it stores a "transport ID" instead of an "arrival time." The patient table 641 shown in FIG. 14 stores, for example, a "transport ID" 6412 issued by the transport device 70a.

The processing circuit 65 controls the overall operation of the management device 60 by executing a first acquisition function 651, a second acquisition function 152, a conversion function 153, and a registration function 654.

The first acquisition function 651 in the processing circuit 65 acquires pre-arrival medical information from the image server 80 . For example, the first acquisition function 651 accesses the image server 80 via the network NW using input of the notified Device ID and transportation ID as a trigger to start. The first acquisition function 651 refers to the image stored in the image server 80 and associated with the Device ID and the transport ID. Further, the first acquisition function 651 outputs the image ID and transportation ID of the acquired image to the registration function 654.

Further, the first acquisition function 651 downloads image data from the image server 80 using input of a patient's arrival notification as a trigger to start. The first acquisition function 651 downloads pre-arrival medical information including image data registered in the patient table 641, Device ID, and image data corresponding to the transport ID, and outputs it to the conversion function 153.

The registration function 654 associates the pre-arrival medical information of the transported patient with the emergency ID. When the registration function 654 receives the output of the image ID and transport ID from the first acquisition function 651, the registration function 654 inputs the image ID of the pre-arrival medical information whose Device ID and transport ID match with the emergency ID output from the second acquisition function 152. The data are stored in the patient table 641 in association with each other.

Next, the transport device 70 includes a camera 21, a transmission data generation section 72, and a communication I/F 23. Note that since the transport devices 70a and 70b each have the same configuration, hereinafter, the transport devices 70a and 70b may be described as the transport device 70 without distinguishing between them.

The transmission data generation unit 72 of the transport device 70 adds identification information to the image data, issues a transport ID, and generates pre-arrival medical information to be transmitted to the image server 80 . The transmission data generation unit 72 issues an image ID to the image data, assigns it to the image data together with the Device ID assigned to the transportation device 70 and the transportation ID, and transmits the image ID to the image server 80 via the communication I/F 23. Send to. Further, the transmission data generation unit 72 transmits the patient transportation schedule including the Device ID and the transportation ID to the hospital HPa via the communication I/F 23.

The image server 80 includes a communication I/F 31, an input I/F 32, a display 33, a storage circuit 84, and a processing circuit 85, as shown in FIG.

The storage circuit 84 is connected to the processing circuit 85 and stores various data. The storage circuit 84 stores, for example, an image table 841.

The image table 841 stores information regarding the pre-arrival medical information acquired from the transport device 70. In this embodiment, the image table 841 is set, for example, by an acquisition function 851 and a registration function 852, which will be described later.

FIG. 15 is a diagram showing an example of an image table according to the second embodiment. As shown in FIG. 15, the image table 841 stores, for example, "image ID", "Device ID", and "conveyance ID" in association with each other. The image table 841 differs from the image table 341 according to the first embodiment shown in FIG. 6 in that it stores "conveyance ID" instead of "arrival time."

In the image table 841 shown in FIG. 15, for example, "Transport ID" 8412 is associated with Device ID "Camera-A" of the transport device 70a, and "Transport ID" 8413 is associated with Device ID "Camera-B" of the transport device 70b. It is associated with That is, the image table 841 shown in FIG. 15 stores that both the "transport ID" 8412 issued by the transport device 70a and the "transport ID" 8413 issued by the transport device 70b are "trans002". do. In this manner, in this embodiment, the same transport ID may be issued for different transport devices 70.

Returning to FIG. 4, the processing circuit 85 controls the overall operation of the image server 80 by executing an acquisition function 851 and a registration function 852.

The acquisition function 851 in the processing circuit 85 acquires pre-arrival medical information from the transport device 70 . For example, upon receiving pre-arrival medical information including image data from the transport device 70 via the network NW, the acquisition function 851 stores the image data in the storage circuit 84 and also stores the image data associated with the pre-arrival medical information. Information such as the ID, Device ID, and transport ID is output to the registration function 852.

The registration function 852 registers information regarding pre-arrival medical information in the image table 841. The registration function 852 registers the image ID, Device ID, and transportation ID output from the acquisition function 851 in the image table 841.

Next, the procedure of processing by the medical information management system 2 according to the second embodiment will be explained using FIGS. 16 and 17. FIG. 16 is a sequence diagram showing an example of processing before patient arrival according to the second embodiment. For example, as shown in FIG. 16, in the medical information management system 2 according to the present embodiment, the transport device 70a first captures an image of the patient being transported (step S11), and issues a transport ID ( Step S12). The transport device 70a notifies the management device 60a of the hospital HPa of the issued transport ID (step S13). Next, the transport device 70a associates the image ID, Device ID, and transport ID with the photographed image data, and transmits the data to the image server 80 (step S21-1).

Subsequently, upon acquiring the image data, image ID, Device ID, and transport ID, the image server 80 registers the image ID, Device ID, and transport ID in the image table 341 (step S26). Next, upon acquiring the Device ID, the processing circuit 65 refers to the image stored in the image server 80 by specifying the Device ID and transport ID (step S31-1). The processing circuit 65 acquires image data, Device ID, and image ID corresponding to the Device ID and transport ID (step S32). The subsequent processing is similar to the processing shown in FIG.

Next, the processing in the medical information management system 2 after the patient arrives will be explained. FIG. 17 is a sequence diagram showing an example of processing after patient arrival according to the second embodiment. First, when the patient arrives at the hospital (step S51), the processing circuit 15 accesses the image server 80 without receiving notification of the arrival time, and downloads the image data in which the arrival time is newly registered together with the arrival time. (Step S73). The subsequent processing is similar to the processing shown in FIG. 11.

As described above, according to the second embodiment, the pre-arrival medical information includes an image taken of the patient. According to the second embodiment, the first acquisition function 651 captures transport identification information, which is information that identifies a procedure for transporting a patient to a hospital, and images of the patient, as information associated with the pre-arrival medical information. and device identification information that identifies the device that has been used. The registration function 654 according to the second embodiment associates the pre-arrival medical information specified by the transport identification information and the device identification information with the patient identification information. Therefore, also in the medical information management system 2 according to the second embodiment, data regarding a patient being transported to a hospital can be easily correlated at the destination hospital.

Note that, according to the second embodiment, a patient being transported is identified using a combination of a transport ID and a Device ID. Thereby, even if the transport ID issued by the transport device 70a overlaps with a transport ID issued by another different transport device 70b, the patient being transported can be uniquely identified. Therefore, according to the second embodiment, it is possible to assign a unique transport ID to each transport device 70 without collectively controlling the assignment of transport IDs among a plurality of transport devices 70.

Further, in the second embodiment, the storage device (image server 80) stores issued identification information (transportation ID) issued by the non-ordered device (transportation device 70) and uniquely identifies the patient who used the non-ordered device. ) and medical information based on the non-ordered device may be stored in association with each other. The processing circuit 15 of the medical information management device may obtain the issue identification information and obtain the medical information associated with the issue identification information as medical information of a patient using the hospital.

(Third embodiment)
In the second embodiment described above, a configuration was described in which a transported patient is identified using a combination of the Device ID of the transport device 70a and the transport ID that uniquely identifies the patient transport procedure. The off-order equipment to be used is not limited to transport devices. For example, a configuration may be adopted in which medical information acquired by the transport device 70a and medical information acquired by an external non-order device such as a smartphone or a drone are associated. In the third embodiment, a configuration will be described in which pre-arrival medical information acquired by an external non-order device is further associated with post-arrival medical information before a transport device Ca (described later) acquires an image of a patient.

First, in the third embodiment, a process until a patient arrives at the hospital HPa shown in FIG. 1 will be described. FIG. 18 is a diagram for explaining processing before patient arrival according to the third embodiment. In the following embodiments, parts that are the same as those shown in the drawings described above are denoted by the same reference numerals, and redundant explanations will be omitted. In addition, in the following, when expressing the smartphone Aa and the drone Ba, which are external non-order devices, without distinguishing them, they may be simply written as "external device." Further, in the following, when expressing a transport device and an external device without distinguishing them, they may be simply written as a "device". Furthermore, when expressing the Device ID of the external device to distinguish it from the Device ID of the transport device 70, it may be written as "external device ID." In this embodiment, the smartphone Aa is given an external device ID "Phone-X", and the drone Ba is given an external device ID "Drone-Y". Note that the external device is an example of other non-ordered equipment.

As shown in FIG. 18, before the ambulance equipped with the transport device Ca arrives, the smartphone Aa takes an image of the patient, assigns it an "image ID" (A1. Capture), and adds the transport ID "trans002". (A2. Transport ID numbering). Then, the smartphone Aa transmits the photographed image to the image server E0 along with the "image ID", "external device ID", and "conveyance ID" (A3. Transfer).

Next, when the drone Ba arrives at the patient before the arrival of the ambulance carrying the transport device Ca, the drone Ba acquires the transport ID and external device ID issued by the smartphone Aa (B1. Transport ID handover). When the drone Ba takes an image of the patient and assigns it an "image ID" (B2. Shooting), the taken image is stored in the "image ID", the external device ID of the drone Ba, and the "external device ID of the smartphone Aa". It is sent to the image server E0 together with "Transportation ID: trans002" (B3. Transfer).

Next, when the ambulance carrying the transport device Ca arrives at the patient, the transport device Ca acquires the transport ID and external device ID issued by the smartphone Aa (C1. Transport ID handover). Then, the transport device Ca photographs the patient's image, assigns it an "image ID" (1. Photography), and transmits the acquired transport ID "trans002" to the hospital HPa (C2. Transport ID: trans002). Then, the transport device Ca transmits the photographed image to the image server E0 along with "image ID", "Device ID of transport device Ca", "external device ID of smartphone Aa", and "transport ID: trans002" (2b .transfer). The image server E0 stores the image transmitted from the transport device 70a in association with the image ID, Device ID, external device ID, and transport ID.

On the other hand, the hospital HPa is notified of the patient's transportation schedule by an ambulance, along with the Device ID of the transportation device Ca installed in the ambulance, the external device ID of the smartphone Aa, and the transportation ID. In this case, the management device Da of the hospital HPa refers to the image stored in the image server E0 (see 3b. Image). At this time, the management device Da refers to the image associated with the notified Device ID or external device ID and transport ID. The subsequent processing is the same as in FIGS. 12 and 13.

Next, the functions of the medical information management system 3 that executes the process shown in FIG. 18 will be explained. FIG. 19 is a block diagram of a medical information management system according to the third embodiment. As shown in FIG. 19, the medical information management system 3 according to the present embodiment includes a smartphone Aa, a drone Ba, management devices Da and Db, transport devices Ca and Cb, and an image server E0. Further, the management device Da is communicably connected to the RIS 40a (not shown) and the PACS 50a (not shown) via the hospital network NWa. Similarly, the management device Db is communicably connected to the RIS 40b (not shown) and the PACS 50b (not shown) via the hospital network NWb. Although FIG. 19 describes a configuration including one smartphone Aa and one drone Ba, the configuration is not limited to this, and may include a plurality of smartphones or drones.

The smartphone Aa takes an image of the patient before the arrival of the ambulance carrying the transport device Ca, and transmits pre-arrival medical information including the image to the image server E0. As shown in FIG. 19, the smartphone Aa includes a camera A1, a transmission data generation section A2, a communication I/FA3, and an ID output section A4. Note that the smartphone Aa is realized, for example, by installing an application having functions corresponding to the transmission data generation section A2 and the ID output section A4 into an existing smartphone having a camera function and a communication function.

Camera A1 of smartphone Aa, like camera 21 of transport device 20, acquires an image of the patient and outputs image data to transmission data generation section A2.

Similar to the transmission data generation unit 22 of the transport device 20, the transmission data generation unit A2 adds identification information to image data, issues a transport ID, and generates pre-arrival medical information for transmission to the image server E0. generate. The transmission data generation unit A2 issues an image ID to the image data, assigns it to the image data together with the Device ID and transportation ID assigned to the smartphone Aa, and sends it to the image server E0 via the communication I/FA3. Send. Furthermore, the transmission data generation unit A2 transmits the patient's transportation schedule including the Device ID and the transportation ID to the hospital HPa via the communication I/FA 3.

The communication I/FA 3 controls the transmission and communication of various data with other devices connected via the network NW. The communication I/FA 3 transmits, for example, the pre-arrival medical information output from the transmission data generation unit 22 to the image server E0. For example, the communication I/FA 3 is realized by a network card, a network adapter, or the like. Further, the communication I/FA 3 may adopt a short-range wireless communication standard such as Wi-Fi or Bluetooth (registered trademark) as the communication standard.

The ID output unit A4 outputs the external device ID and the issued transport ID to the drone Ba, the transport device Ca, etc. The ID output unit A4 may display a two-dimensional code, such as a QR code (registered trademark), on a display (not shown) that includes information regarding the external device ID and the transportation ID. It may also be output through the communication I/FA3.

Next, the drone Ba arrives at the scene before the arrival of the ambulance carrying the transport device Ca, takes an image of the patient, and transmits pre-arrival medical information including the image to the image server E0. As shown in FIG. 19, the drone Ba includes a camera B1, a transmission data generation section B2, a communication I/FB3, an ID acquisition section B4, and an ID output section B5. Note that the drone Ba is realized, for example, by installing an application having functions corresponding to the transmission data generation section B2, ID acquisition section B4, and ID output section B5 into an existing drone having a camera function and a communication function.

Camera B1 of drone Ba, like camera A1 of smartphone Aa, acquires an image of a patient and outputs image data to transmission data generation section B2.

Similar to the transmission data generation unit A2 of the smartphone Aa, the transmission data generation unit B2 adds identification information to the image data, issues a transport ID, and generates pre-arrival medical information to be transmitted to the image server E0. generate. The transmission data generation unit B2 issues an image ID to the image data, adds it to the image data together with the Device ID of the drone Ba and the transport ID, and transmits it to the image server E0 via the communication I/FB3. Furthermore, the transmission data generation unit B2 transmits the patient's transportation schedule including the Device ID and the transportation ID to the hospital HPa via the communication I/FB3.

Note that when the ID acquisition unit B4 acquires the external device ID and the transportation ID from the smartphone Aa, for example, the transmission data generation unit B2 converts the external device ID of the smartphone Aa and the acquired transportation ID into the image ID and the Device ID of the drone Ba. and is added to the image data and transmitted to the image server E0 via the communication I/FB3. The transmission data generation unit B2 also transmits the patient transportation schedule including the Device ID, the external device ID of the smartphone Aa, and the transportation ID acquired from the smartphone Aa to the hospital HPa via the communication I/FB3.

The communication I/FB 3 controls various data transmissions and communications performed with other devices connected via the network NW. For example, the communication I/FB 3 transmits the pre-arrival medical information output from the transmission data generation unit 22 to the image server E0. For example, the communication I/FB 3 is realized by a network card, a network adapter, or the like. Further, the communication I/FB 3 may adopt a short-range wireless communication standard such as Wi-Fi or Bluetooth (registered trademark) as a communication standard.

The ID acquisition unit B4 acquires an external device ID and a transport ID from another external device such as a smartphone Aa. The ID acquisition unit B4 acquires the external device ID and the transport ID by, for example, photographing the two-dimensional code displayed on the display of the smartphone Aa, or by receiving information transmitted from the smartphone Aa through the communication I/FB3. .

The ID output unit B5 outputs the Device ID and the issued transport ID to the transport device Ca, etc., similarly to the ID output unit A4 of the smartphone Aa. Note that, for example, when the ID acquisition unit B4 acquires the external device ID and the transportation ID from the smartphone Aa, the ID output unit B5 may output information regarding the external device ID of the smartphone Aa and the acquired transportation ID.

Next, as shown in FIG. 19, the transport device Ca includes a camera 21, a transmission data generation section C2, a communication I/F 23, and an ID acquisition section C4. Note that since the transport devices Ca and Cb each have the same configuration, hereinafter, the transport devices Ca and Cb may be described as the transport device C without distinguishing between them.

Like the transmission data generation section 22, the transmission data generation section C2 adds identification information to image data and generates pre-arrival medical information to be transmitted to the image server E0. Note that, for example, when the ID acquisition unit C4 acquires the external device ID and the transportation ID from the smartphone Aa or the drone Ba, the transmission data generation unit C2 adds the external device ID and the acquired transportation ID to the image data and performs communication. It may also be transmitted to the image server E0 via the I/F 23. The transmission data generation unit C2 may also transmit the patient transportation schedule including the external device ID and the acquired transportation ID to the hospital HPa via the communication I/F 23.

The ID acquisition unit C4 acquires an external device ID and a transportation ID from an external device such as a smartphone Aa or a drone Ba. The ID acquisition unit C4 acquires the external device ID and the transport ID, for example, by photographing a two-dimensional code displayed on the display of the external device or by receiving information transmitted from the external device through the communication I/FB3. .

The management device Da includes a communication I/F 11, an input I/F 12, a display 13, a storage circuit D4, and a processing circuit D5. Note that the management device Db connected to the in-hospital network NWb of the hospital HPb also has the same configuration as the management device Da, so hereinafter, the management devices Da and Db may be described as the management device D without distinguishing them. .

The storage circuit D4 is connected to the processing circuit D5 and stores various data. In this embodiment, the storage circuit D4 stores, for example, a patient table D41. Similar to the patient table 641, the patient table D41 is information that associates "image ID", "Device ID", "emergency ID", "transportation ID", and "image ID (after conversion)". be. Note that the patient table D41 may store an external device ID instead of the Device ID of the transport device Ca, as the Device ID associated with the pre-arrival medical information acquired by the external device, for example.

The processing circuit D5 controls the overall operation of the management device D by executing a first acquisition function D51, a second acquisition function 152, a conversion function 153, and a registration function D54.

The first acquisition function D51 in the processing circuit D5 acquires pre-arrival medical information from the image server E0. For example, the first acquisition function D51 accesses the image server E0 via the network NW using input of the notified Device ID, external device ID, transport ID, etc. as a start trigger. The first acquisition function D51 refers to an image associated with the Device ID or the external device ID and the transport ID, which is stored in the image server E0. Further, the first acquisition function D51 outputs the image ID and transportation ID of the acquired image to the registration function D54.

Further, the first acquisition function D51 downloads image data from the image server E0 using the input of a patient's arrival notification as a trigger. The first acquisition function D51 downloads pre-arrival medical information including image data corresponding to the image ID and Device ID registered in the patient table D41 or the external device ID and transport ID, and outputs it to the conversion function 153.

The registration function D54 associates the pre-arrival medical information of the transported patient with the emergency ID. When the registration function D54 receives the output of the image ID and transport ID from the first acquisition function D51, the registration function D54 outputs the image ID of the pre-arrival medical information whose Device ID or external device ID and transport ID match from the second acquisition function 152. It is stored in the patient table D41 in association with the emergency ID.

As shown in FIG. 4, the image server E0 includes a communication I/F 31, an input I/F 32, a display 33, a storage circuit E4, and a processing circuit E5.

The storage circuit E4 is connected to the processing circuit E5 and stores various data. The storage circuit E4 stores, for example, an image table E41.

The image table E41 stores information regarding the pre-arrival medical information acquired from the transport device 70. In this embodiment, the image table E41 is set, for example, by an acquisition function E51 and a registration function E52, which will be described later.

FIG. 20 is a diagram illustrating an example of an image table according to the third embodiment. As shown in FIG. 20, the image table E41 further associates, for example, "Image ID", "Device ID", and "Transportation ID" with "Transportation ID takeover source" shown in column E414. Remember. "Transport ID takeover source" E414 is the issue source of the transport ID when the transport device or external device indicated in "Device ID" takes over the transport ID from another external device instead of issuing the transport ID itself. Indicates the external device ID of the external device.

In the image table E41 shown in FIG. 20, the Device ID registered in the three records E413 corresponding to the image IDs "Pic0002", "Pic0003", and "Pic0004" is not "Camera-A" but "Phone-X" or " Drone-Y”. That is, the three records E413 indicate that the corresponding pre-arrival medical information was acquired not by the transport device Ca but by the external device smartphone Aa or drone Ba.

In the image table E41 shown in FIG. 20, for example, the record with the image ID "Pic0004" is a record regarding an image acquired by the drone Ba whose Device ID is "Drone-Y", and the transport ID is a record with the Device ID "Phone-Y". It remembers that it was issued by smartphone Aa, which is "X". Similarly, for example, a record with image ID "Pic0005" is a record regarding an image acquired by transport device Ca whose Device ID is "Camera-A", and the transport ID is a smartphone whose Device ID is "Phone-X". It is remembered that it was issued by Aa.

Returning to FIG. 4, the processing circuit E5 controls the overall operation of the image server E0 by executing an acquisition function E51 and a registration function E52.

The acquisition function E51 in the processing circuit E5 acquires pre-arrival medical information from the transport device 70. For example, upon receiving pre-arrival medical information including image data from the smartphone Aa, drone Ba, or transport device Ca via the network NW, the acquisition function E51 stores the image data in the storage circuit E4, and also stores the image data in the storage circuit E4. Information such as the image ID, Device ID, external device ID, and transportation ID associated with the information is output to the registration function E52.

The registration function E52 registers information regarding pre-arrival medical information in the image table E41. The registration function E52 registers, for example, the image ID, Device ID, external device ID, and transportation ID output from the acquisition function E51 in the image table E41. If the acquisition function E51 further outputs an external device ID in addition to the Device ID, the registration function E52 stores the external device ID in the image table E41 as the "transportation ID takeover source."

Next, the procedure of processing by the medical information management system 3 according to the third embodiment will be explained using FIGS. 21 and 22. FIG. 21 is a sequence diagram showing an example of processing before patient arrival according to the third embodiment. For example, as shown in FIG. 21, in the medical information management system 3 according to the present embodiment, the smartphone Aa first captures an image of the patient before the arrival of the transport device Ca (step SA1), and An ID is issued (step SA2). The smartphone Aa associates the image ID, Device ID, and transport ID with the photographed image data, and transmits the data to the image server E0 (step SA3).

Next, when the drone Ba arrives at the patient before the arrival of the transport device Ca, it acquires the external device ID and transport ID from the smartphone Aa, and takes over the transport ID (step SB1). Then, the drone Ba takes an image of the patient (step SB2), associates the taken image data with the image ID and Device ID, as well as the external device ID and transport ID acquired from the smartphone Aa, and sends it to the image server E0 ( Step SB3).

Next, when the transport device Ca arrives at the patient, it acquires an external device ID and a transport ID from the smartphone Aa, and takes over the transport ID (step SC1). Then, the transport device Ca photographs an image of the patient (step S11), associates the photographed image data with the image ID and Device ID, and the transport ID and external device ID acquired from the smartphone Aa, and transmits it to the image server E0. (Step S21-1). The following processing is similar to the processing shown in FIGS. 16 and 17.

Next, a process in which the management device Da acquires image data from the image server E0 in step S73 shown in FIG. 17 will be described. FIG. 22 is a flowchart illustrating an example of image data acquisition processing according to the third embodiment. Here, steps S100 to S130 in FIG. 22 are realized, for example, by the processing circuit D5 of the management device Da reading out a program corresponding to the registration function D54 from the storage circuit D4 and executing it.

First, the processing circuit D5 waits until it receives an instruction to acquire image data (step S100: No). When the processing circuit D5 receives the image data acquisition instruction (step S100: Yes), it accesses the image server E0 and reads out the record with the matching transport ID from the image table E41 (step S101).

Next, the processing circuit D5 determines whether the takeover source ID is registered in the read record (step S110). If the processing circuit D5 determines that the takeover source ID is not registered in the read record (step S110: No), the processing circuit D5 determines whether the Device ID registered in the read record matches the acquired Device ID. (Step S111). When the processing circuit D5 determines that the Device ID registered in the read record matches the acquired Device ID (step S111: Yes), the processing circuit D5 downloads and acquires the image data corresponding to the record (step S121). After that, the process moves to step S130. On the other hand, if the processing circuit D5 determines that the Device ID registered in the read record does not match the acquired Device ID (step S111: No), the processing circuit moves to step S130.

Returning to step S110, if the processing circuit D5 determines that the takeover source ID is registered in the read record (step S110: Yes), the processing circuit D5 determines whether the takeover source ID matches the acquired external device ID. (Step S112).

If the processing circuit D5 determines that the external device ID matches the acquired external device ID (step S112: Yes), the processing circuit D5 downloads the image data corresponding to the record (step S121). After that, the process moves to step S130. On the other hand, if the processing circuit D5 determines that the external device ID does not match the acquired external device ID (step S112: No), the processing circuit moves to step S130.

Then, the processing circuit D5 determines whether the read record is the last record of the image table E41 (step S130). If the processing circuit D5 determines that the read record is not the last record of the image table E41 (step S130: No), the process returns to step S101 and reads the next record. On the other hand, if the processing circuit D5 determines that the read record is the last record of the image table E41 (step S130: Yes), it ends the process.

As described above, according to the third embodiment, the pre-arrival medical information includes an image of the patient taken by an external device other than a transport device associated with a mobile body that transports the patient to the hospital. further including. According to the third embodiment, the first acquisition function D51 further acquires device identification information of the external device and transportation identification information associated with the external device as information associated with the pre-arrival medical information. do. The registration function D54 according to the third embodiment transfers the pre-arrival medical information specified by the device identification information of the external device and the transport identification information associated with the external device to the device associated with the mobile object. and the device identification information and the patient identification information. Therefore, in the medical information management system 3 according to the third embodiment, data regarding the patient acquired before the arrival of the ambulance can also be easily correlated at the destination hospital.

Furthermore, in the third embodiment, the non-ordered device (transport device C) may inherit the issuance identification information issued by another non-ordered device (external device). The storage device (image server E0) associates and stores issued identification information (transportation ID) that uniquely identifies a common patient among a plurality of non-order devices and medical information based on the non-order device. It's okay. The processing circuit 15 of the medical information management device may obtain the issue identification information and obtain the medical information associated with the issue identification information as medical information of a patient using the hospital.

Note that, according to the third embodiment, a patient being transported is identified using a combination of a transport ID and a Device ID, or a combination of a transport ID and an external device ID. According to the third embodiment, the transport ID and external device ID given to the pre-arrival medical information by the external device are taken over by the transport device Ca and are also given to the pre-arrival medical information acquired by the transport device Ca. be done. That is, even if the transport ID given to the pre-arrival medical information by the external device is the same as the transport ID already issued by the transport device Ca, the patient being transported can be uniquely identified.

Note that in the third embodiment, the configuration for uniquely identifying a patient being transported is not limited to this. For example, the image server E0 may replace the transport ID that the transport device Ca inherited from the external device with a transport ID newly issued by the transport device Ca. Alternatively, the external device may issue a transport ID that does not overlap with the transport ID issued by the transport device Ca, and the transport device Ca may use the transport ID as is. Furthermore, the external device may use the external device ID as the transport ID instead of issuing a new transport ID.

Furthermore, the transport ID issued by the external device may also be a unique transport ID for other external devices or transport devices. In this case, the patient being transported can be uniquely identified without specifying the Device ID, so even if the transport device Ca does not acquire an external device ID from the smartphone Aa or drone Ba, the management device Can identify information.

(Fourth embodiment)
By the way, the information included in the medical information is not limited to images, but may also be other information such as an electrocardiogram or vital signs. Similarly, non-ordered equipment such as transport devices and external devices that collect medical information are not limited to cameras that take images, but also devices that collect other information such as those that measure electrocardiograms and pulse rates. Good too. Furthermore, although we have described a configuration in which a transport device and a mobile object correspond one-to-one, the present invention is not limited to this, and multiple transport devices mounted on one mobile object such as an ambulance or an emergency helicopter can each correspond to a mobile object. It may be configured such that it can be attached. Further, the configuration in which information identifying a patient corresponding to medical information is handed over is not limited to the one using the transport ID and Device ID in the third embodiment. In the fourth embodiment, by associating medical information including information other than images without relying on the transport ID or Device ID in the third embodiment, information regarding the same patient collected by the same or different out-of-order equipment can be obtained. A configuration for identifying multiple pieces of medical information will be described.

First, in the fourth embodiment, a process until a patient arrives at the hospital HPa shown in FIG. 1 will be described. FIG. 23 is a diagram for explaining processing before patient arrival according to the fourth embodiment. In FIG. 23, a patient (not shown) is transported from point (1) to hospital HPa shown at point (3). The patient's medical information is acquired by, for example, external devices Device-A and Device-B until the ambulance V1 arrives at point (1). Device-A is, for example, a smartphone, and Device-B is, for example, a drone.

Thereafter, when the ambulance V1 arrives at point (1) at 12:03, the patient is transported by the ambulance V1 from point (1) to point (2), for example. At that time, the patient's medical information is acquired, for example, by Device-C and Device-D, which are transport devices mounted on the ambulance V1. Device-C is, for example, a heart rate monitor, and Device-D is, for example, a camera.

Then, when the ambulance V1 arrives from the point (1) to the point (2) at 12:30, the patient is transferred to the emergency helicopter V2 and further transported to the hospital HPa. At that time, the patient's medical information is acquired, for example, by Device-E and Device-F, which are transport devices mounted on the emergency helicopter V2. Device-E is, for example, a heart rate monitor, and Device-F is, for example, a camera. Thereafter, the patient arrives at the hospital HPa shown at point (3) at 12:50.

As shown in FIG. 23, when medical information is acquired by multiple different devices, if the times and locations at which each piece of medical information is acquired are similar to each other, each piece of medical information acquired by the different devices , it can be assumed that they correspond to the same patient. In addition, if the timing of starting an application (app) for transmitting medical information on one device is close to the timing of closing the application on another device, each medical information acquired on the different device will be can be assumed to correspond to the same patient. Furthermore, if the medical information acquired by different devices matches the biometric information such as the patient's fingerprint or iris, or the identification information given to each patient, the medical information acquired by the different devices will be , it can be identified that they correspond to the same patient.

The medical information collected in the pre-arrival process shown in FIG. 23 will be explained using FIG. 24. FIG. 24 is a diagram illustrating an example of medical information data according to the fourth embodiment. Note that the medical information data shown in FIG. 24 is stored, for example, in a medical information table I41 that will be described later.

In FIG. 24, "data ID" indicates an identifier that is given to the acquired medical information and uniquely identifies the medical information. "DeviceID" indicates an identifier that uniquely identifies the transport device or external device that acquired the medical information. "Collection time" and "collection location" respectively indicate the time when the medical information was acquired and the location information indicating the point where the medical information was collected. “Patient Gr” indicates an identifier that identifies a patient and is temporarily assigned to the medical information. Note that the collection time may include, for example, the date, and the collection location may be registered in another format such as an address or longitude/latitude. Furthermore, if the location information at the time the medical information was collected cannot be obtained, the "Collection location" field will be blank. Note that the patient Gr is an example of issued identification information.

In the example shown in FIG. 24, the device whose Device ID is "Device-A" acquires the patient's medical information at "point (1)" at "12:00" and "12:01" respectively. are doing. Moreover, the patient Gr "Patient001" is assigned to the two acquired medical information. Similarly, the device whose Device ID is "Device-B" acquires the patient's medical information at "point (1)" at "12:01" and "12:02," respectively. Moreover, the patient Gr "Patient002" is assigned to the two acquired medical information. Furthermore, the device whose Device ID is “Device-C” acquires the patient's medical information at “point (1)” at “12:05.” A patient Gr "Patient003" is assigned to the acquired medical information. Additionally, a device whose Device ID is "Device-D" acquires the patient's medical information at "12:15" at an unknown location, and obtains the patient's medical information at "point (2)" at "12:30". Information is being obtained. Moreover, the patient Gr "Patient003" is assigned to the two acquired medical information. Furthermore, the device whose Device ID is "Device-E" acquires the patient's medical information at "12:40" and "12:42" at an unknown location. A patient Gr "Patient004" is assigned to the two acquired medical information. Similarly, a device whose Device ID is "Device-F" obtains the patient's medical information at "12:40" at an unknown location, and obtains the patient's medical information at "Point (3)" at "12:50". Obtaining medical information. Furthermore, the patient Gr "Patient004" is assigned to the two acquired medical information.

As mentioned above, in this embodiment, the medical information acquired by "Device-C" and the medical information acquired by "Device-D" mounted on the same moving body, ambulance V1, are Each is assigned to the same patient Gr. Similarly, medical information acquired by "Device-E" and "Device-F" mounted on the same mobile emergency helicopter V2 are assigned to the same patient Gr. ing. That is, in this embodiment, medical information acquired at similar times by devices associated with the same moving object is assigned to the same patient Gr. This is because medical information acquired at similar times by the same moving object can be presumed to have been acquired from the same patient.

Next, the configuration of the medical information management system that processes the medical information shown in FIG. 24 will be described using FIG. 25. FIG. 25 is a block diagram of a medical information management system according to the fourth embodiment. In the following embodiments, parts that are the same as those shown in the drawings described above are denoted by the same reference numerals, and redundant explanations will be omitted.

As shown in FIG. 25, the medical information management system 4 according to this embodiment includes six devices Device-A to Device-F, two management devices Ga and Gb, and a medical information server Ia. Furthermore, the management device Ga is communicably connected to the RIS 40a (not shown) and the PACS 50a (not shown) via the hospital network NWa. Similarly, the management device Gb is communicably connected to the RIS 40b (not shown) and the PACS 50b (not shown) via the hospital network NWb. Note that although FIG. 25 describes a configuration including six devices, the number of devices is not limited to this.

In FIG. 25, the management device Ga connected to the in-hospital network NWa of the hospital HPa includes a communication I/F 11, an input I/F 12, a display 13, a storage circuit G4, and a processing circuit G5. The storage circuit G4 is connected to the processing circuit G5 and stores various data. In this embodiment, the storage circuit G4 stores, for example, a patient table G41.

The patient table G41 stores information that associates the medical information obtained from the medical information server Ia with the emergency ID obtained from the RIS 40. In this embodiment, the information stored in the patient table G41 is stored or updated by, for example, a first acquisition function G51, a second acquisition function 152, a conversion function G53, and a registration function G54, which will be described later.

FIG. 26 is a diagram showing an example of a patient table according to the fourth embodiment. For example, as shown in FIG. 26, the patient table G41 associates "data ID", "Device ID", "emergency ID", "patient Gr", and "data ID (after conversion)". It is information. Here, "Data ID" and "Device ID" in FIG. 26 indicate identifiers that uniquely identify the medical information and the device that acquired the medical information, respectively. “Emergency ID” indicates the emergency ID acquired from the RIS 40. “Patient Gr” indicates an identifier that identifies a patient and is temporarily assigned to the medical information. “Data ID (after conversion)” indicates an identifier that uniquely identifies the medical information converted to the DICOM format. For example, in the record shown in FIG. 26, emergency ID "EM022" is assigned to medical information of data ID "Data0001" whose patient Gr is "Patient001" acquired by a device whose Device ID is "Device-A". indicates that it has been done. It also indicates that the medical information has been converted to DICOM format data, and "Dic02001" has been assigned as the converted data ID.

Returning to FIG. 25, the processing circuit G5 controls the entire operation of the management device Ga by executing the first acquisition function G51, the second acquisition function 152, the conversion function G53, and the registration function G54.

The first acquisition function G51 in the processing circuit G5 acquires medical information from the medical information server Ia. For example, the first acquisition function G51 accesses the medical information server Ia via the network NW using the input of the notified Device ID as a start trigger. The first acquisition function G51 refers to medical information stored in the medical information server Ia and associated with the Device ID. Further, the first acquisition function G51 downloads medical information data from the medical information server I0 using input of a patient's arrival notification as a trigger. The first acquisition function G51 downloads medical information including medical information data corresponding to the medical information ID and Device ID registered in the patient table G41, and outputs it to the conversion function G53.

The conversion function G53 converts medical information data into DICOM format data. Upon receiving the output of the medical information from the first acquisition function G51, the conversion function G53 converts the medical information into DICOM format data along with the associated data ID, Device ID, and emergency ID. The conversion function G53 transmits the converted medical information to the PACS 50a.

The registration function G54 associates the medical information of the patient to be transported with the emergency ID. Upon receiving the output of the medical information ID and patient Gr from the first acquisition function G51, the registration function G54 associates the data ID, Device ID and patient Gr with the emergency ID output from the second acquisition function 152, and creates the patient table G41. Store in.

Next, as shown in FIG. 25, the Device-A 9a includes a camera A1, a transmission data generation section 9a2, a communication I/FA 3, and a GPS (Global Positioning System) 9a4. Note that the Device-A 9a is realized, for example, by installing an application (app) having a function corresponding to the transmission data generation unit 9a2 into an existing smartphone having a camera function, a communication function, and a GPS function.

The transmission data generation unit 9a2 adds a data ID and a patient Gr as identification information to the image data acquired by the camera A1. The transmission data generation unit 9a2 also acquires position information from the GPS 9a4 and adds it to the image data. Then, the transmission data generation unit 9a2 adds a DeviceID to the image data, generates medical information to be transmitted to the medical information server Ia, and transmits it to the medical information server Ia via the communication I/FA 3.

In addition, when the transmission data generation unit 9a2 detects the activation or termination of an application installed on the Device-A 9a, the transmission data generation unit 9a2 transmits the time when the application was activated or terminated and the position information at that time via the communication I/FA 3. and transmits it to the medical information server Ia.

The GPS 9a4 detects the position information of the Device-A 9a and outputs it to the transmission data generation section 9a2.

Next, as shown in FIG. 25, Device-B9b includes a camera B1, a transmission data generation section 9b2, a communication I/FB3, and a GPS 9b4. Note that the Device-B 9b is realized, for example, by installing an application (app) having a function corresponding to the transmission data generation unit 9b2 into an existing drone having a camera function, a communication function, and a GPS function.

The transmission data generation unit 9b2, like the transmission data generation unit 9a2 of the Device-A 9a, adds a data ID and a patient Gr as identification information to the image data acquired by the camera B1. The transmission data generation unit 9b2 also acquires position information from the GPS 9b4 and adds it to the image data. Then, the transmission data generation unit 9b2 adds a DeviceID to the image data, generates medical information to be transmitted to the medical information server Ia, and transmits it to the medical information server Ia via the communication I/FB3.

In addition, when the transmission data generation unit 9b2 detects the activation or termination of the application installed on the Device-B 9b, the transmission data generation unit 9b2 transmits the time when the application was activated or terminated and the position information at that time via the communication I/FB 3. and transmits it to the medical information server Ia.

The GPS 9b4 detects the position information of Device-B and outputs it to the transmission data generation section 9b2.

Next, as shown in FIG. 25, the Device-C9c includes a heartbeat sensor 9c1, a transmission data generation section 9c2, and a communication I/F 9c3. Device-C9c is, for example, a heartbeat sensor mounted on the ambulance V1. Note that Device-C and Device-E have similar configurations, except that they are equipped with different moving objects. Therefore, the configuration of Device-C will be explained below, and the detailed configuration of Devicec-E will be explained below. The explanation will be omitted.

The heartbeat sensor 9c1 is, for example, a known heartbeat sensor, detects the patient's heartbeat, and outputs it to the transmission data generation unit 9c2.

The transmission data generation unit 9c2 adds a data ID and a patient Gr as identification information to the heartbeat data acquired from the heartbeat sensor 9c1. The transmission data generation unit 9c2 also acquires position information from the GPS installed in the ambulance V1 and adds it to the heartbeat data. Then, the transmission data generation unit 9c2 adds a DeviceID to the heartbeat data, generates medical information to be transmitted to the medical information server Ia, and transmits it to the medical information server Ia via the communication I/F 9c3.

The communication I/F 9c3 controls the transmission and communication of various data performed with other devices connected via the network NW. For example, the communication I/F 9c3 transmits the medical information output from the transmission data generation unit 9c2 to the medical information server Ia. For example, the communication I/F 9c3 is realized by a network card, a network adapter, or the like.

Next, as shown in FIG. 25, the Device-D 9d includes a camera 21, a transmission data generation section 9d2, and a communication I/F 23. Note that Device-D9d and Device-F9f have similar configurations, only the mobile objects they are mounted on are different. Therefore, the configuration of Device-D will be explained below, and the detailed configuration of Deviec-F will be explained below. The explanation will be omitted.

The transmission data generation unit 9d2 adds a data ID and a patient Gr as identification information to the image data acquired by the camera 21. The transmission data generation unit 9d2 also acquires position information from the GPS installed in the ambulance V1 and adds it to the image data. Then, the transmission data generation unit 9d2 adds a DeviceID to the image data, generates medical information to be transmitted to the medical information server Ia, and transmits it to the medical information server Ia via the communication I/F 23.

As shown in FIG. 25, the medical information server Ia includes a communication I/F 31, an input I/F 32, a display 33, a storage circuit I4, and a processing circuit I5. Note that the medical information server Ia is an example of a storage device.

The storage circuit I4 is connected to the processing circuit I5 and stores various data. The storage circuit I4 stores, for example, a medical information table I41, an application log I42, and a device table I43.

The medical information table I41 stores information regarding medical information acquired from Device-A to Device-F. The medical information table I41 stores information as shown in FIG. 24, for example. In this embodiment, the medical information table I41 is set or updated, for example, by an acquisition function I51 and a registration function I52, which will be described later.

The application log I42 stores information regarding the activation status of applications installed in each of the devices Device-A to Device-F for transmitting medical information to the medical information server Ia. FIG. 27 is a diagram illustrating an example of an application log according to the fourth embodiment. As shown in FIG. 27, the application log I42 stores, for example, "Device ID", "time", "action", and "point" in association with each other. The application log I42 is set, for example, by the registration function I52. Note that, similar to the collection time and collection location of the medical information data shown in FIG. 24, the time shown in the application log I42 in FIG. May be registered. Furthermore, if the location information at the time the action occurs cannot be obtained, the "Location" item may be left blank.

For example, the first record shown in FIG. 27 indicates that the application of the device whose Device ID is "Device-A" was "launched" at "point (1)" at "11:59". Similarly, the second record shown in FIG. 27 indicates that the application of the device whose Device ID is "Device-B" was "launched" at "point (1)" at "12:00". Similarly, the third row of records shown in Figure 27 shows that the application of the device whose Device ID is "Device-A" is "terminated" at "Point (1)" at "12:02", and as shown in Figure 27. The record shown in the fourth row indicates that the application of the device whose Device ID is "Device-B" was "ended" at "point (1)" at "12:05".

The device table I43 stores the correspondence between each device and the mobile body on which the device is mounted. FIG. 28 is a diagram illustrating an example of a device table according to the fourth embodiment. As shown in FIG. 28, the device table I43 stores, for example, "Device ID" and "mobile ID" in association with each other. The device table I43 is set, for example, by an administrator (not shown) of the medical information server Ia.

In FIG. 28, "mobile object ID" is an identifier that uniquely identifies a moving object such as an ambulance or an emergency helicopter. In the device table I43 shown in FIG. 28, a mobile body ID is stored in a device mounted on a mobile body in association with a DeviceID, and a mobile body ID is not registered in other devices. For example, in the device table I43 shown in FIG. 28, the Device IDs "Device-A" and "Device-B" are not associated with a mobile ID. That is, the device table I43 shown in FIG. 28 indicates that the device whose Device ID is "Device-A" and the device whose Device ID is "Device-B" are not mounted on the mobile object. Further, the device table I43 shown in FIG. 28 indicates that the device whose Device ID is "Device-C" and the device whose Device ID is "Device-D" are mounted on the ambulance V1. Similarly, the device table I43 shown in FIG. 28 indicates that the device whose Device ID is "Device-E" and the device whose Device ID is "Device-F" are mounted on the emergency helicopter V2. As shown in FIG. 28, in this embodiment, one mobile ID may be associated with a plurality of Device IDs.

Returning to FIG. 25, the processing circuit I5 controls the entire operation of the medical information server Ia by executing an acquisition function I51 and a registration function I52. Note that the registration function I52 is an example of an updating section.

An acquisition function I51 in the processing circuit I5 acquires medical information from each device Device-A to Device-F. For example, when the acquisition function I51 receives medical information including image data from each device Device-A, Device-B, Device-D, or Device-F via the network NW, the acquisition function I51 stores the image data in the storage circuit I4. At the same time, information such as the data ID, Device ID, collection time, collection location, and patient Gr associated with the medical information is output to the registration function I52. Similarly, upon receiving medical information including data related to heartbeat from each device Device-C or Device-E via the network NW, the acquisition function I51 stores the data related to heartbeat in the storage circuit I4, and also stores the medical information Information such as the data ID, Device ID, collection time, collection location, and patient Gr associated with is output to the registration function I52.

The registration function I52 registers information related to medical information in the medical information table I41, and updates the patient Gr registered in the medical information table I41. The registration function I52 registers, for example, the data ID, Device ID, collection time, collection location, and patient Gr output from the acquisition function I51 in the medical information table I41.

Furthermore, the registration function I52 updates the patient Gr associated with each piece of medical information based on the information registered in the medical information table I41. For example, the registration function I52 extracts medical information collected by different devices registered in the medical information table I41, and determines whether the collection time and collection location of the medical information match or are similar. The registration function I52 determines, for example, whether the difference between the collection times of two pieces of medical information is "within 5 minutes" and whether the difference between the collection locations is "within 50 meters." If the registration function I52 determines that the collection time and collection location of the medical information match or are similar to the collection time and collection location of other medical information, the registration function I52 selects the patient Gr whose medical information was collected later among the two pieces of medical information. is updated to the patient Gr of the previously collected medical information.

Processing by the registration function I52 will be explained using FIGS. 29A and 29B. 29A and 29B are diagrams showing an example of a medical information table according to the fourth embodiment. In the medical information as shown in FIG. 29A, the registration function I52 can, for example, combine medical information with data ID "Data0002" collected by Device-A and medical information with data ID "Data0003" collected by Device-B. Compare collection times and locations. In this case, as shown by reference numeral I411 in FIG. 29A, the collection time matches "12:01" and the collection location also matches "point (1)", so the medical information with data ID "Data0002" It is presumed that this and the medical information with the data ID "Data0003" are related to the same patient. In this case, the registration function I52 updates the patient Gr with the data ID "Data0003" to the patient Gr "Patient001" with the data ID "Data0002".

Next, in the medical information as shown in FIG. 29A, the registration function I52 stores medical information with data ID "Data0004" collected by Device-B and medical information with data ID "Data0005" collected by Device-C, for example. Compare the collection time and collection location with the information. In this case, as shown by reference numeral I412 in FIG. 29A, the collection times "12:02" and "12:05" are close, and the collection locations match at "point (1)." , it is estimated that the medical information with the data ID "Data0004" and the medical information with the data ID "Data0005" are related to the same patient. In this case, the registration function I52 updates the patient Gr with the data ID "Data0005" to the updated patient Gr "Patient001" with the data ID "Data0004".

Furthermore, the registration function I52 refers to the device table I43 shown in FIG. 28, and determines whether the device with the Device ID "Device-C" and the device with the Device ID "Device-D" shown in the reference numeral I413 in FIG. It is determined that the vehicle is mounted on the ambulance V1, which is the vehicle. In this case, it is presumed that the medical information collected by the device Device-C and the medical information collected by the device Device-D are related to the same patient. In this case, the registration function I52 updates the patient Gr in the medical information with the data ID "Data0007" collected by the device of Device-D to the updated patient Gr "Patient001" with the data ID "Data0005".

On the other hand, in the medical information shown in FIG. 24, the registration function I52 stores, for example, the collection time and collection location of the medical information with data ID "Data0007" and the collection time and collection location of the medical information with data ID "Data0008". Compare. In this case, the two medical information collection times are "12:30" and "12:40" and are not close to each other. Furthermore, the two medical information collection locations are "point (2)" and "unknown", and are presumed not to be close to each other. In this case, it is unclear whether the medical information with the data ID "Data0007" and the medical information with the data ID "Data0008" can be estimated to be related to the same patient. In this case, the registration function I52 does not update the patient Gr with the data ID "Data0008".

Through each process by the registration function I52 described above, the patient Gr of each medical information is updated, for example, as shown by reference numeral I414 in FIG. 29A. That is, the same patient Gr is set for each piece of medical information as information indicating that the medical information acquired by Device-A to Device-D is estimated to have been acquired from the same patient.

Note that the information used by the registration function I52 for determination is not limited to the collection time and point of time when the medical information was acquired, but may also be configured such that, for example, the time or point of activation or termination of an application installed in each device is used. It may be. For example, as shown by reference numeral I421 in FIG. 27, the application on the device with Device ID "Device-B" is terminated on the device with Device ID "Device-A" two minutes before the application on the device with Device ID "Device-A" ends. The application is started at the same "point (1)" where the application starts and ends. In this case, the device "Device-A" acquires the patient's medical information until the device "Device-B" arrives, and the device "Device-B" acquires the patient's medical information until the device "Device-B" arrives. It can be assumed that he took over after that. In this case, the registration function I52 may update the patient Gr with the Device ID "Device-B" with the patient Gr "Patient001" with the Device ID "Device-A".

Furthermore, if the medical information includes information that can identify each individual patient, such as biometric information such as a patient's fingerprint or iris, or identification information given to each patient, the registration function I52 can identify the individual patient. It is further determined whether or not the identifiable information matches among a plurality of pieces of medical information. If the registration function I52 determines that the information that can identify an individual patient included in the medical information matches the information that can identify an individual patient included in other medical information, the registration function I52 selects the medical information that was collected later among the two medical information. The information patient Gr is updated to the patient Gr of the previously collected medical information. Note that in the following, information that can identify each individual patient may be simply referred to as "individual identifying information." Moreover, personal identification information is an example of information that identifies a patient.

In the example shown in FIG. 29B, the medical information "Data0005" collected by the device Device-C includes personal identification information I415 such as a fingerprint, iris, and patient ID. Similarly, the medical information "Data0009" collected by Device-E also includes personal identification information I416. In this case, the registration function I52 determines whether the personal identification information I415 and I416 match. When the registration function I52 determines that the personal identification information I415 and I416 match, as shown by reference numeral I417 in FIG. The patient Gr corresponding to the medical information collected by either is updated to the patient Gr of the medical information collected by Device-C. Thereby, the registration function I52 can set a patient Gr indicating that the medical information collected from each of the devices Device-A to Device-F was acquired from the same patient.

Furthermore, when determining whether medical information has been obtained from the same patient, it is better to determine based on personally identifying information than to determine based on time and location, since there is less possibility of patient mix-up. small. Therefore, if the registration function I52 determines that the personal identification information does not match each other, the registration function I52 may be configured not to update the patient Gr, regardless of the determination result of the time and location.

Next, the procedure of processing by the medical information management system 4 according to the fourth embodiment will be explained using FIGS. 30 and 31. FIG. 30 is a sequence diagram illustrating an example of medical information acquisition processing according to the fourth embodiment. Note that although FIG. 30 shows only two devices, Device-A and Device-B, the configuration may be such that similar processing is performed for Device-C to Device-F.

For example, as shown in FIG. 30, in the medical information management system 4 according to the present embodiment, Device-A9a, which is a smartphone, first stores medical information before the arrival of Device-B9b, which is a drone. An application for transmitting data to the information server Ia is launched (step SX1), and the Device ID and the time and location at which the application was launched are transmitted to the medical information server Ia (step SX2). The medical information server Ia receives the Device ID and the time and location at which the application was started, and registers the start of the application by the Device-A9a in the application log I42 (step SZ1).

Next, when Device-A9a acquires the patient's medical information (step SX3), the medical information including the Device ID, data ID, personal identification information, and the time and location at which the medical information was acquired is transferred to the medical information server. Ia (step SX4). The medical information server Ia stores information regarding the received medical information in the medical information table I41 (step SZ2).

Next, when the Device-B9b starts an application for transmitting medical information to the medical information server Ia (step SY1), it transmits the Device ID and the time and position at which the application was started to the medical information server Ia (step SY2). ). The medical information server Ia receives the Device ID and the time and location at which the application was started, and registers the start of the application by the Device-B 9b in the application log I42 (step SZ3).

On the other hand, when the Device-A 9a ends the application (step SX5), it transmits the Device ID and the time and location at which the application was ended to the medical information server Ia (step SX6). The medical information server Ia receives the Device ID and the time and location at which the application ended, and registers the end of the application by the Device-A 9a in the application log I42 (step SZ4).

Next, when the Device-B9b acquires the patient's medical information (step SY3), the medical information including the Device ID, data ID, personal identification information, and the time and location at which the medical information was acquired is transferred to the medical information server. Ia (step SY4). The medical information server Ia stores information regarding the received medical information in the medical information table I41 (step SZ5).

Through the above processing, information as shown in FIG. 24 is registered in the medical information table I41, and information as shown in FIG. 27 is registered in the application log I42.

Next, a process will be described in which the medical information server Ia updates the information in the registered medical information table I41 to identify a plurality of pieces of medical information regarding the same patient. FIG. 31 is a flowchart illustrating an example of medical information update processing according to the fourth embodiment. Here, steps S200 to S250 in FIG. 31 are realized, for example, by the processing circuit I5 of the medical information server Ia reading a program corresponding to the registration function I52 from the storage circuit I4 and executing it. Furthermore, the medical information update process shown in FIG. 31 is executed at any timing, such as when new medical information is received or when a medical information acquisition request is received from the management device Ga. For example, when the medical information server Ia updates the information in the medical information table I41 every time new medical information is transmitted from each device Device-A to Device-F, when the patient arrives at the hospital HPa, , all medical information has been identified. Thereby, the management device Ga can collectively associate all medical information with the patient identification information corresponding to the order.

First, the processing circuit I5 extracts target medical information from the medical information table I41 in which information as shown in FIG. 24 is registered (step S200). Next, the processing circuit I5 extracts medical information to be compared from the medical information table I41 (step S201).
c Next, the processing circuit I5 determines whether each piece of medical information includes personal identification information (step S210). If the processing circuit I5 determines that each piece of medical information includes personal identification information (step S210: Yes), it determines whether or not the individual identification information included in each piece of medical information matches (step S220). .

If the processing circuit I5 determines that the personal identification information matches (step S220: Yes), it updates the patient Gr corresponding to the medical information (step S240), and proceeds to step S250. On the other hand, if the processing circuit I5 determines that the personal identification information does not match (step S220: No), the processing circuit I5 moves to step S250.

Returning to step S210, if the processing circuit I5 determines that personal identification information is not included in at least one of the medical information (step S210: No), the time and place included in each piece of medical information match or are similar. It is determined whether the following conditions are met (step S230). If the processing circuit I5 determines that the condition is met (step S230: Yes), it updates the patient Gr corresponding to the medical information (step S240), and proceeds to step S250. On the other hand, if the processing circuit I5 determines that the condition is not met (step S230: No), the processing circuit I5 moves to step S250.

Then, the processing circuit I5 determines whether processing has been completed for all medical information (step S250). When the processing circuit I5 determines that the processing is not completed yet (step S250: No), the processing circuit I5 returns to step S200 and repeats the processing. On the other hand, when the processing circuit I5 determines that the processing is completed (step S250: Yes), it ends the processing.

As described above, according to the fourth embodiment, the update unit (registration function I52) of the storage device (medical information server Ia) updates medical information acquired by different non-ordered devices (Device-A to Device-F). It is determined whether the time at which the information was acquired (collection time) and the place at which the information was acquired (collection location) match or are similar to each other, and if it is determined that they match or are similar to each other, at least one of the medical The issuing identification information (patient Gr) corresponding to the information is updated. Further, the medical information management device associates the medical information whose issued identification information has been updated with the patient identification information (emergency ID). Therefore, the medical information management system 4 according to the fourth embodiment can easily associate medical information acquired by a non-ordered device without relying on the transport ID or Device ID. Thereby, the medical information management system 4 can identify a plurality of pieces of medical information regarding the same patient collected by the same or different out-of-order devices.

Further, according to the fourth embodiment, the update unit (registration function I52) of the storage device identifies each patient included in the medical information acquired by different non-ordered devices (Device-A to Device-F). Determine whether the information (personal identification information) matches, and if it is determined that the information identifying the patient matches, update the issued identification information (patient Gr) corresponding to at least one of the medical information. You can. The updating unit (registration function I52) of the medical information management device associates the medical information whose issued identification information has been updated with the patient identification information (emergency ID). Thereby, the medical information management system 4 according to the fourth embodiment can accurately associate medical information acquired by a non-ordered device.

Further, the off-order device may be an off-order device (Device-C to Device-F) associated with a mobile body (ambulance V1, emergency helicopter V2) that transports a patient to a hospital.

In addition, if medical information of multiple patients is acquired using one device due to a large-scale disaster, etc., there is a high possibility that patients will be confused, so it is recommended not to update patient Gr based on time and location. It may be a configuration.

Further, the off-order equipment is not limited to equipment associated with a mobile object, equipment outside the hospital such as a smartphone, or a drone, but may be other medical equipment installed within the hospital HP. In addition, even if the medical information is collected by a modality installed on the hospital website, medical information collected not based on the order issued by the hospital website is the same as medical information collected by equipment outside the order. may be processed.

Further, for example, although a configuration has been described in which an application for transmitting medical information is installed on the external devices Device-A and Device-B, the embodiment is not limited to this. For example, the configuration may be such that the same applications as Device-A and Device-B are installed on Device-C to Device-F, which are transport devices.

In addition, although the configuration has been described in which the registration function I52 updates the patient Gr in a manner that the patient Gr corresponding to the medical information acquired earlier is handed over to the patient Gr corresponding to the medical information acquired later, the configuration is not limited to this. For example, the registration function I52 may issue a new patient Gr.

Further, the data stored in the PACS 50 is not limited to the DICOM format, but may be data in the HL7 format used in electronic medical record systems, for example. Furthermore, the emergency ID may be anything that can uniquely identify a patient in the hospital HPa, and may not be newly issued by the RIS 40a, but may be already registered patient identification information.

The term "processor" used in the description of each embodiment above refers to, for example, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an Application Specific Integrated Circuit (ASIC), a programmable Refers to circuits such as logic devices (e.g., Simple Programmable Logic Device (SPLD), Complex Programmable Logic Device (CPLD), and Field Programmable Gate Array (FPGA)). do. Here, instead of storing the program in the memory, the program may be directly incorporated into the circuit of the processor. In this case, the processor realizes its functions by reading and executing a program built into the circuit. Furthermore, each processor of this embodiment is not limited to being configured as a single circuit for each processor, but may also be configured as a single processor by combining multiple independent circuits to realize its functions. good.

Here, the program to be executed by the processor is provided by being pre-installed in a ROM (Read Only Memory), a storage unit, or the like. This program is a file in a format that can be installed or executable on these devices, such as CD (Compact Disk)-ROM, FD (Flexible Disk), CD-R (Recordable), DVD (Digital Versatile Disk), etc. It may be provided recorded on a computer readable storage medium. Further, this program may be stored on a computer connected to a network such as the Internet, and may be provided or distributed by being downloaded via the network. For example, this program is composed of modules including each functional section. In actual hardware, a CPU reads a program from a storage medium such as a ROM and executes it, so that each module is loaded onto the main storage device and generated on the main storage device.

Further, the configuration of the medical information management system in each embodiment is not limited to that described above; for example, other computers such as the RIS 40 or the PACS 50 may implement part or all of the functions of the processing circuit 15; A part or all of the contents stored in the storage circuit 14 may be stored. Further, each function included in the processing circuit 15 of the management device 10 may be implemented on the cloud, and the contents stored in the storage circuit 14 may be stored on the cloud.

According to at least one embodiment described above, data regarding a patient that is collected not based on an order can be easily associated at a destination hospital.

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

1 Medical information management system 10a, 10b Management device 11 Communication I/F
12 Input I/F
13 Display 14 Memory circuit 141 Patient table 15 Processing circuit 151 First acquisition function 152 Second acquisition function 153 Conversion function 154 Registration function 20a, 20b Transport device 30 Image server 40a, 40b RIS
50a, 50b PACS

Claims (11)

a storage device in which patient medical information collected by a device outside the order without being based on an order issued by the hospital is stored;
A system comprising: a medical information management device that acquires medical information of patients using the hospital from among the medical information stored in the storage device,
The medical information management device includes:
a medical information acquisition unit that acquires medical information of patients using the hospital from among the medical information stored in the storage device;
an association unit that acquires patient identification information that uniquely identifies a patient using the hospital within the hospital, and associates the patient's medical information acquired by the medical information acquisition unit with the patient identification information;
Equipped with
The medical information acquisition unit of the medical information management device acquires issued identification information that uniquely identifies a common patient among a plurality of non-ordered devices, and the medical information associated with the issued identification information, A medical information management system that obtains medical information of patients using the hospital . The storage device associates and stores identification information of the non-ordered device, arrival status at the hospital, and medical information based on the non-ordered device,
The medical information acquisition unit of the medical information management device acquires the identification information of the non-ordered device and the arrival status at the hospital, and stores the medical information associated with the identification information and the arrival status at the hospital. , acquired as medical information of patients using the hospital;
The medical information management system according to claim 1. The storage device associates and stores issued identification information issued by the non-order device and that uniquely identifies a patient who used the non-order device, and medical information based on the non-order device;
The medical information acquisition unit of the medical information management device acquires the issue identification information, and acquires the medical information associated with the issue identification information as medical information of a patient using the hospital.
The medical information management system according to claim 1 or 2. The non-ordered device inherits the issuing identification information issued by another non-ordered device,
The storage device stores the issue identification information and medical information based on the out-of-order device in association with each other.
The medical information management system according to claim 3. The patient identification information is associated with an order issued by the hospital,
The association unit of the medical information management device associates the patient's medical information acquired by the medical information acquisition unit with a data format of the medical information acquired based on the order and associated with the patient identification information. converting into the same data format and associating the converted medical information with the patient identification information;
A medical information management system according to any one of claims 1 to 4. The storage device further includes an update unit that identifies a plurality of medical information of the same patient acquired by the same or different out-of-order equipment,
The association unit of the medical information management device acquires a plurality of identified medical information of the same patient as medical information of a patient using the hospital, and associates it with the patient identification information.
A medical information management system according to any one of claims 1 to 5. The storage device determines whether the times and locations at which the medical information acquired by different out-of-order devices match or approximate each other, and determines whether the times at which the medical information was acquired and the locations at which the medical information was acquired are determined. Further comprising an updating unit that updates issuing identification information corresponding to at least one of the medical information when it is determined that the locations match or are similar to each other,
The association unit of the medical information management device associates the medical information whose issued identification information has been updated with the patient identification information.
A medical information management system according to any one of claims 1 to 5. The storage device determines whether information identifying a patient included in each of the medical information acquired by different off-order devices matches, and when it is determined that the information identifying the patient matches, at least further comprising an update unit that updates issue identification information corresponding to any of the medical information,
The association unit of the medical information management device associates the medical information whose issued identification information has been updated with the patient identification information.
A medical information management system according to any one of claims 1 to 5. The off-order device is an off-order device associated with a mobile body that transports a patient to a hospital;
A medical information management system according to any one of claims 1 to 7. a medical information acquisition unit that acquires medical information of patients using the hospital among the medical information of patients stored in the storage device and collected not based on orders issued by the hospital;
an association unit that acquires patient identification information that uniquely identifies a patient using the hospital within the hospital, and associates the patient's medical information acquired by the medical information acquisition unit with the patient identification information. ,
The medical information acquisition unit acquires issuing identification information that uniquely identifies a common patient among a plurality of non-ordered devices, and transmits the medical information associated with the issuing identification information to patients using the hospital. Obtained as medical information of
Medical information management device. The medical information management device
Obtaining medical information of a patient using the hospital from among patient medical information stored in a storage device and collected not based on an order issued by a hospital;
obtaining patient identification information that uniquely identifies a patient using the hospital within the hospital;
obtaining issued identification information that uniquely identifies a common patient among a plurality of non-ordered devices, and obtaining the medical information associated with the issued identification information as medical information of a patient using the hospital; A medical information management method that executes a process of associating the acquired medical information of the patient with the patient identification information.

Images