JP6021517B2 - Medical image processing system - Google Patents

Description

  Embodiments described herein relate generally to a medical image processing system.

  In recent years, with the increase in the volume of medical data generated in hospitals, especially medical image data generated by imaging a subject with a modality such as an X-ray CT (Computed Tomography) apparatus or an MRI (Magnetic Resonance Imaging) apparatus Efforts are being made to store medical data in storage outside the hospital.

  As storage outside the hospital, for example, cloud storage can be used. Here, the cloud storage is a cloud system belonging to a form called IaaS (Infrastructure as a Service) that provides a server with server machines and network infrastructure included in the cloud, and mainly provides a data storage function.

  Now, in the medical field, a doctor (external interpretation doctor) located outside the hospital may be requested to interpret an image taken with a modality arranged in the hospital. In particular, in the case of a patient who is transported urgently due to a brain disorder or the like, it is necessary to quickly determine whether or not to perform an operation and to determine an operation method, and therefore, it is important to provide data to an external interpretation doctor promptly.

JP 2006-260301 A

  The problem to be solved by the present invention is to provide a medical image processing system capable of speeding up the provision of medical images to external interpretation doctors.

A medical image processing system according to an embodiment includes a medical image capturing device that captures a patient and generates medical image data, a cloud-type storage unit that provides a storage function of the medical image data, and the medical image data And a data storage unit, a determination unit, a storage processing unit, a data providing unit, and a notification unit .

The determination unit determines whether the medical image capturing by the medical image capturing apparatus is emergency capturing or normal capturing that is not emergency capturing. The storage processing unit stores the medical image data received from the medical image capturing device in the cloud storage unit when the determination unit determines that the emergency imaging is not performed, and determines that the determination unit performs emergency imaging. In this case, the medical image data received from the medical image photographing apparatus is stored in the data storage unit . When the provision of medical image data is requested from the terminal device , or when the provision of medical image data related to normal imaging is requested from the terminal device, the data providing unit is stored in the cloud storage unit The medical image data is provided to the terminal device, and the medical image data stored in the data storage unit is provided to the terminal device when the terminal device is requested to provide medical image data related to emergency imaging. . When the determination unit determines that the emergency imaging is performed, the notifying unit starts the emergency imaging before the medical image data is provided to the terminal device by the data providing unit. Notify the terminal device.

The conceptual diagram for demonstrating the PACS system which concerns on one Embodiment. The conceptual diagram which shows the state which has arrange | positioned the system in the hospital. The block diagram which shows the structure of the system. The flowchart which shows schematic operation | movement of the system etc. The figure which shows an example of the input screen displayed on the modality which concerns on the embodiment. The figure which shows an example of the imaging | photography setting information which concerns on the embodiment. The flowchart of the notification process in FIG. The figure which shows an example of the provision destination setting information which concerns on the same embodiment. The figure which shows an example of the provision destination setting information which concerns on the same embodiment. The figure which shows an example of the provision destination setting information which concerns on the same embodiment. The flowchart of the reception preparation process in FIG. The figure which shows an example of the mapping table which concerns on the same embodiment. The flowchart of the reception / storage process in FIG. The flowchart of the data provision process in FIG. The flowchart of the deletion process in FIG. The figure which shows the transition of the screen displayed on the terminal device which concerns on the same embodiment. The block diagram which shows the structure of the PACS system which concerns on a modification. The figure which shows the transition of the screen displayed on a terminal device in the embodiment.

An embodiment will be described with reference to the drawings.
In the present embodiment, a PACS (Picture Archiving and Communication System) system is disclosed as an example of a medical image processing system.

FIG. 1 is a conceptual diagram for explaining a PACS system 1 according to the present embodiment.
The PACS system 1 is connected to one or a plurality of modalities 2 (medical imaging devices) arranged in a hospital A, one or a plurality of terminal devices 3, one or a plurality of servers arranged in another hospital B or a doctor's home. Is connected to the cloud 4 configured as described above.

  Communication among the PACS system 1, modality 2, terminal device 3, and cloud 4 is performed via a network such as a local area network (LAN), a wide area network (WAN), or the Internet in each hospital.

  The PACS system 1 includes one or a plurality of servers and workstations. The PACS system 1 may be installed outside the hospital A where the modality 2 is installed as shown in FIG. 1, for example, or may be installed inside the hospital A as shown in FIG.

  The modality 2 is a medical device that images a subject and generates medical image data (tomographic image, volume data, etc.) conforming to, for example, DICOM (Digital Imaging and Communication in Medicine) standards. Examples of the modality 2 include an X-ray diagnostic apparatus, an X-ray CT apparatus, an MRI apparatus, and an ultrasonic diagnostic apparatus.

  The terminal device 3 is a workstation arranged in the hospital B, a personal computer arranged in the doctor's home, a notebook type personal computer or tablet terminal carried by the doctor, and the medical image generated by the modality 2 Functions such as a DICOM image viewer for browsing data are installed.

  The cloud 4 provides the PACS system 1 with a cloud storage 5 (cloud-type storage unit) that stores medical data such as medical image data. That is, the cloud 4 is a cloud system belonging to the form of IaaS.

  The PACS system 1 stores medical image data captured by the modality 2 in the cloud storage 5. In addition, the PACS system 1 transmits medical image data to the terminal device 3 in response to a request from the terminal device 3.

  An arrow P1 in FIGS. 1 and 2 indicates the flow of medical image data in a normal state. On the other hand, an arrow P2 in FIGS. 1 and 2 shows the flow of medical image data in an emergency. Here, for example, an emergency refers to a case where an emergency diagnosis is performed on a patient who has been transported urgently, and a normal time refers to a case where a diagnosis other than an emergency is performed.

  As can be seen from the arrow P <b> 1, in normal times, the medical image data generated by the modality 2 is first stored in the cloud storage 5 via the PACS system 1. Thereafter, the medical image data stored in the cloud storage 5 is provided to the terminal device 3 via the PACS system 1.

  On the other hand, as can be seen from the arrow P2, in an emergency, the medical image data generated by the modality 2 is directly provided from the PACS system 1 to the terminal device 3 without going through the cloud storage 5.

  The configuration of the PACS system 1 for realizing such a flow of medical image data is shown in the block diagram of FIG. The PACS system 1 includes an emergency photographing determination unit 10, an access key issuing unit 11, an access key providing unit 12, an emergency data ID issuing unit 13, a data receiving unit 14, an emergency data storage unit 15, a data providing unit 16, and the like. The data receiving unit 14 functions as a storage processing unit according to the present embodiment.

  The emergency photographing determination unit 10 determines whether the medical image photographing by the modality 2 is urgent or non-urgent. The access key issuing unit 11 issues an access key for accessing the medical image data generated by the modality 2. The access key providing unit 12 provides (transmits) the access key issued by the access key issuing unit 11 to the terminal device 3. The emergency data ID issuing unit 13 issues an emergency data ID for attaching to medical image data generated by emergency imaging by the modality 2.

  The data receiving unit 14 receives medical image data from the modality 2, and when the received medical image data relates to emergency imaging, attaches the emergency data ID issued by the emergency data ID issuing unit 13 to the data. And stored in both the emergency data storage unit 15 and the cloud storage 5. On the other hand, when the medical image data received from the modality 2 relates to normal imaging that is not emergency imaging, the data reception unit 14 stores the data only in the cloud storage 5.

  The data providing unit 16 provides (transmits) medical image data stored in the emergency data storage unit 15 or the cloud storage 5 to the terminal device 3 in response to a request from the terminal device 3.

  Each of the units 10 to 16 includes a processor such as a CPU (Central Processing Unit), a memory such as a ROM (Read Only Memory) and a RAM (Random Access Memory), an HDD (Hard Disk Drive), and an SSD (Solid State Drive). It may be a hardware provided with a communication unit that communicates with an auxiliary storage device such as a LAN or the Internet, or may be a software function realized by one or a plurality of processors executing a computer program. .

Next, details of the operation of the PACS system 1 will be described.
FIG. 4 shows the operations of doctors and engineers in hospital A (“hospital flow”), the operation of modality 2 (“modality flow”), and the operation of PACS system 1 (“PACS system flow”) regarding the storage and provision of medical image data. ). The operations and processes shown in this flowchart are specialized for emergency shooting.

  When the patient is urgently transported to the hospital A, a doctor or an engineer prepares for emergency imaging by the modality 2. In this preparatory work, a doctor or an engineer who is an operator of the modality 2 inputs various conditions for photographing through an input screen displayed on the display of the modality 2.

  An example of the input screen is shown in FIG. The input screen 60 includes a list box 61 for designating a test type (imaging target part, etc.) from previously prepared options, patient information (patient ID, name, date of birth, height, weight, blood type). Etc.) includes a patient information area 62 provided with an input area for inputting, a switching button 63 for switching the imaging mode between the emergency imaging mode and the normal imaging mode, a start button 64 for instructing the start of imaging, and the like.

  At the time of normal imaging, the operator selects the type of examination in the list box 61, inputs patient information into the patient information area 62, and then operates the start button 64 to start imaging in the normal imaging mode. On the other hand, at the time of emergency shooting, the operator selects the type of examination from the list box 61, operates the switch button 63 to switch the shooting mode to the emergency shooting mode, and then operates the start button 64 to perform emergency shooting. Start shooting in mode. In photographing in the emergency photographing mode, patient information can be omitted.

  When the start button 64 is operated, the modality 2 transmits a start notification informing the PACS system 1 of the start of shooting. This start notification includes identification information indicating whether the imaging mode is the normal imaging mode or the emergency imaging mode, examination type information indicating the examination type selected in the list box 61, and the like. Further, the start notification related to the normal imaging mode includes the patient information input in the patient information area 62.

  When the PACS system 1 receives the start notification from the modality 2, the PACS system 1 executes emergency shooting determination processing for determining whether the shooting is emergency shooting or normal shooting (step S1).

  In the case of emergency imaging, the PACS system 1 executes a notification process for notifying the external radiographer of the start of emergency imaging (step S2). Further, the PACS system 1 executes a preparation process for receiving medical image data from the modality 2 (step S3).

  When the modality 2 operator instructs the start of imaging via the operation panel or the like of the modality 2, the modality 2 starts imaging processing according to the examination type selected in the list box 61, and medical images such as a tomogram of the patient. Generate data. Eventually, when the operator operates the modality 2 to instruct the end of imaging, the modality 2 ends imaging and transmits medical image data generated by the imaging to the PACS system 1.

  After Step S3, the PACS system 1 receives the medical image data transmitted from the modality 2 and executes reception / storage processing for storing the received medical image data in the emergency data storage unit 15 or the cloud storage 5. (Step S4).

  After step S4, the PACS system 1 executes a data providing process for providing the medical image data stored in step S4 to the external interpretation doctor (step S5).

  After step S5, the PACS system 1 executes a process for deleting the medical image data stored in the emergency data storage unit 15 in step S4 (step S6).

  The external interpretation doctor interprets the medical image data provided in step S5 and displayed on the display of the terminal device 3, and returns the report to the hospital A.

  Hereinafter, details of each process of steps S1 to S6 will be described with reference to FIGS. FIG. 16 shows the transition of the screen displayed on the display of the terminal device 3 by the DICOM image viewer.

[Step S1: Emergency shooting determination process]
The emergency shooting determination process is mainly executed by the emergency shooting determination unit 10. The determination as to whether shooting by the modality 2 is emergency shooting or normal shooting is made based on a start notification from the modality 2, for example.

  That is, the emergency shooting determination unit 10 determines that shooting by the modality 2 is normal shooting if the shooting mode identification information included in the start notification indicates normal shooting mode, and if the identification information indicates the emergency shooting mode. For example, it is determined that shooting by modality 2 is emergency shooting.

  The determination of emergency shooting or normal shooting may be performed based on the part to be shot. In this case, for example, shooting setting information 70 as shown in FIG. 6 is stored in a memory included in the PACS system 1. This imaging setting information 70 defines the presence / absence (existence / absence) of emergency imaging for a region to be imaged (head, chest, abdomen, etc.). When the imaging target part indicated by the examination type information included in the start notification is a part set to emergency imaging “none” in the imaging setting information 70, the emergency imaging determination unit 10 performs imaging by modality 2 for normal imaging. It is judged that. On the other hand, the emergency imaging determination unit 10 performs imaging by the modality 2 when the imaging target part indicated by the examination type information included in the start notification is the part set to emergency imaging “present” in the imaging setting information 70. Judged as emergency shooting.

[Step S2: Notification processing to external interpretation doctor]
The notification process to the external interpretation doctor is mainly executed by the access key issuing unit 11 and the access key providing unit 12. FIG. 7 is a flowchart of the notification process. The notification process is started when the emergency shooting determination unit 10 determines that the shooting is emergency shooting.

  First, the access key issuing unit 11 issues an emergency data access key (step S21). The emergency data access key is a key for accessing the medical image data generated by the emergency imaging from the terminal device 3. The emergency data access key in the present embodiment is a 4-digit numeric string such as “1234”. However, the emergency data access key may have any format as long as it is a character string that does not overlap between the medical image data stored in the emergency data storage unit 15.

  After the emergency data access key is issued, the access key providing unit 12 provides (transmits) the access key and a message notifying the start of imaging to the doctor's terminal device 3 as the interpretation request destination (step S22).

  The provision destination terminal device 3 makes a decision based on provision destination setting information 80 as shown in FIG. 8, for example. The provision destination setting information 80 associates doctors (doctors D1 to D3) who are candidates for interpretation of medical image data and addresses (addresses AD1 to AD3) of the terminal device 3 corresponding to the doctors. The access key providing unit 12 transmits an emergency data access key to the address of each doctor's terminal device 3 included in the provision destination setting information 80.

  Further, for example, the provision destination terminal device 3 may be determined based on the provision destination setting information 81 as illustrated in FIG. 9. The provision destination setting information 81 includes doctors (doctors D1 to D3) who are candidates for interpretation of medical image data, states (locations) of the doctors, and addresses (addresses AD1 to AD3) of the terminal devices 3 corresponding to the doctors. AD3). The state of each doctor is “in hospital” indicating that the doctor is located in hospital A, “hospital ...” (“hospital B” in FIG. 9) indicating that the doctor is located in another hospital, For example, “home” indicating that the doctor is at home. Such a state of each doctor can be grasped from a management system for managing the attendance and leaving of the doctor who works at the hospital A and the place where he / she goes out. The PACS system 1 grasps the state of each doctor from the management system at an appropriate timing, and updates the provision destination setting information 81. In such provision destination setting information 81, the access key providing unit 12 has doctors other than the medical facility (hospital A) where the modality 2 is installed, that is, doctors D2 and D3 whose states are not “in-hospital”. The emergency data access key is transmitted to the address of the terminal device 3.

Further, for example, the provision destination terminal device 3 may be determined based on the provision destination setting information 82 as shown in FIG. The provision destination setting information 82 includes doctors (doctors D1 to D3) who are candidates for interpretation of medical image data, specialized fields (brain surgery, internal medicine, anesthesiology, etc.) of each doctor, and a terminal device corresponding to each doctor. 3 addresses (addresses AD1 to AD3). The access key providing unit 12 determines a doctor suitable for interpretation based on the examination type information included in the start notification received from the modality 2 and the specialized fields of each doctor included in the provision destination setting information 82, and the doctor's An emergency data access key is transmitted to the address of the terminal device 3. For example, when the region to be imaged is the brain, the access key providing unit 12 transmits an emergency data access key to the address of the terminal device 3 of the doctor D1 who specializes in brain surgery.
With the step S22, the processing shown in the flowchart of FIG. 7 is completed.

  The terminal device 3 that has received the emergency data access key or the like displays a pop-up 100 as shown in FIG. This pop-up 100 includes a message notifying emergency shooting such as “shooting has been started...” And a URL generated based on the received emergency data access key. In this URL, “http: // toshiba-pacs-viewer /” indicates the address of the PACS system 1 in a network such as the Internet, and “12% 235 & 35% 1234” is an address where medical image data is stored in the PACS system 1 Indicates. In this example, the last four digits of the URL indicate the access key.

[Step S3: Preparation processing for receiving medical image data]
The medical data reception preparation process is mainly executed by the emergency data ID issuing unit 13. FIG. 11 is a flowchart of the reception preparation process. The processing shown in this flowchart is started when the emergency shooting determination unit 10 determines that the shooting is emergency shooting.

  First, the emergency data ID issuing unit 13 issues an emergency data ID (step S31). The emergency data ID is an identifier attached to medical image data generated by the emergency imaging. The emergency data ID in the present embodiment is a 4-digit character string such as “ABCD”. However, the emergency data ID may have any format as long as it is a character string that does not overlap between medical image data stored in the emergency data storage unit 15.

After issuing the emergency data ID, the emergency data ID issuing unit 13 maps the emergency data ID and the emergency data access key issued by the access key issuing unit 11 in step S21 (step S32). Specifically, the emergency data ID issuing unit 13 stores the emergency data ID issued in step S31 and the emergency data access issued by the access key issuing unit 11 in step S21 in the mapping table 90 as shown in FIG. Write in association with the key.
With step S32, the processing shown in the flowchart of FIG. 11 is completed.

[Step S4: Medical Image Data Reception / Storage Processing]
The reception / storage process of medical image data is mainly executed by the data receiving unit 14. FIG. 13 is a flowchart of the reception / storage process. This flowchart shows the flow of processing both when the emergency shooting determination unit 10 determines that the shooting is emergency shooting and when it is determined that the shooting is normal shooting.

  First, the data receiving unit 14 waits for reception of medical image data from the modality 2 (step S41). If the medical image data is received, the data receiving unit 14 determines whether or not the emergency data ID is issued by the emergency data ID issuing unit 13 (step S42).

  If the emergency data ID has been issued through step S31, the process of the data receiving unit 14 proceeds to a process corresponding to emergency shooting. That is, the data receiving unit 14 adds the emergency data ID to the received medical image data and stores it in the emergency data storage unit 15 (step S43). Thereafter, the data receiving unit 14 stores the received medical image data in association with the patient information and examination type information included in the start notification received from the modality 2 in the cloud storage 5 (step S44). With the step S44, the processing shown in the flowchart of FIG.

  On the other hand, if the emergency data ID has not been issued, the processing of the data receiving unit 14 proceeds to processing corresponding to normal imaging. That is, the data receiving unit 14 stores the received medical image data in association with the patient information and examination type information included in the start notification received from the modality 2 in the cloud storage 5 (step S45). With step S45, the processing shown in the flowchart of FIG. 13 is completed.

[Step S5: Data provision processing to an external interpretation doctor]
Data provision processing to the external interpretation doctor is mainly executed by the data provision unit 16. When an interpreting physician who is an operator of the terminal device 3 operates the URL in the pop-up 100 shown in FIG. 16A with a mouse or the like, the terminal device 3 tries to access medical image data indicated by the URL. . When receiving access from the terminal device 3, the data providing unit 16 starts the processing shown in the flowchart of FIG.

  First, the data providing unit 16 determines whether or not an emergency data access key (for example, the last four digits of the URL) included in the URL that the terminal device 3 is trying to access is mapped in the mapping table 90 (step S51).

  If mapped (Yes in step S51), the data providing unit 16 determines whether or not the medical image data to which the emergency data ID corresponding to the emergency data access key has been stored in the emergency data storage unit 15. Is determined (step S52).

  If step S43 is completed and the medical image data has already been stored in the emergency data storage unit 15 (Yes in step S52), the data providing unit 16 sends the medical image data to the terminal device 3 that is attempting access. Provide (transmit) (step S53).

On the other hand, if the medical image data is not already stored in the emergency data storage unit 15 (No in step S52), the data providing unit 16 waits until the medical image data is stored in the emergency data storage unit 15 (step S54). . At this time, the data providing unit 16 notifies the terminal device 3 of the progress of data storage. The progress status is, for example, a numerical value indicating the stored size with respect to the entire size of the medical image data as a percentage. The terminal device 3 displays a viewer screen 101 as shown in FIG. 16B on the display of its own device, and notifies the progress status notified from the PACS system 1. Eventually, when the storage of the medical image data in the emergency data storage unit 15 is completed, the data providing unit 16 transmits the medical image data to the terminal device 3 (step S53).
With step S53, the process shown in the flowchart of FIG. 14 ends.

  The terminal device 3 that has received the medical image data transmitted in step S53 displays a viewer screen 102 including a medical image based on the medical image data on the display of the own device, as shown in FIG. The interpretation doctor interprets the medical image displayed on the viewer screen 102 to create a report and feeds it back to the hospital A. This feedback may be performed, for example, by transmitting a report from the terminal device 3 via the PACS system 1, or may be performed by directly transmitting the terminal device 3 to the hospital A by e-mail or the like. .

  In step S51, if the emergency data access key included in the URL is not mapped in the mapping table 90 (No in step S51), the data providing unit 16 sends a notification that the access from the terminal device 3 is denied. It transmits to the terminal device 3 (step S55). Upon receiving this notification, the terminal device 3 displays a message indicating that access is not possible, for example, on its own display. In this case, the process shown in the flowchart of FIG. 14 is completed through step S55.

[Step 6: Medical Image Data Deletion Process]
The deletion process of medical image data is mainly executed by the data providing unit 16. An interpretation doctor who is an operator of the terminal device 3 transmits an interpretation completion notification to the PACS system 1 via the terminal device 3 when the interpretation is completed. When the completion notification is received, the data providing unit 16 starts the process shown in the flowchart of FIG.

  First, the data providing unit 16 determines whether or not the medical image data provided to the terminal device 3 that is the transmission source of the completion notification has been stored in the cloud storage 5 (step S61).

  When the storage is completed (Yes in step S61), the data providing unit 16 deletes the medical image data stored in the emergency data storage unit 15 (step S62). Further, the data providing unit 16 deletes the emergency data access key and the emergency data ID related to the medical image data from the mapping table 90 (step 63).

On the other hand, when the storage of the medical image data in the cloud storage 5 has not been completed (No in step S61), the data providing unit 16 waits until the medical image data is reflected (stored) in the cloud storage 5 ( Step S64). Eventually, when step S45 in the reception / storage process is completed, the storage of the medical image data in the cloud storage 5 is completed. At this time, the data providing unit 16 deletes the medical image data stored in the emergency data storage unit 15 (step S62), and deletes the emergency data access key and the emergency data ID related to the medical image data from the mapping table 90. (Step 63).
With the step S63, the process shown in the flowchart of FIG. 15 is completed.

  Even if the completion notification is not received from the terminal device 3, the medical image data is deleted from the emergency data storage unit 15 when a predetermined time has elapsed since the medical image data was provided to the terminal device 3. You may do it.

  In the case of normal imaging, for example, an external interpretation doctor operates the terminal device 3 to transmit the patient ID of the patient to be diagnosed and the type of medical image (examination type) to the PACS system 1. In the PACS system 1, the medical image data associated with the patient ID and examination type received from the terminal device 3 by the data providing unit 16 is read from the cloud storage 5 and returned to the terminal device 3. The external interpretation doctor browses the medical image data returned in this way on the display of the terminal device 3, creates a report, and transmits it to the hospital A.

The operation of the configuration according to this embodiment will be described.
During normal imaging, medical image data generated by the modality 2 is stored in the cloud storage 5 via the PACS system 1, and this medical image data is provided to the terminal device 3 via the PACS system 1. If medical image data is stored in the cloud storage 5 in this way, there is no need to provide a large-scale storage device in the PACS system 1, and thus the system 1 can be reduced in size (hardened in hardware). However, since the cloud storage 5 may be configured using the memory of a plurality of servers, the data upload speed is slow, and it takes a long time until the medical image data can be read out. there is a possibility.

  On the other hand, for emergency imaging, medical image data generated by the modality 2 is directly provided from the emergency data storage unit 15 of the PACS system 1 to the terminal device 3. With such a flow, it is possible to provide medical image data to the terminal device 3 more quickly than the above-described normal flow.

  Further, the medical image data stored in the emergency data storage unit 15 is deleted by the data deletion process when the interpretation by the external interpretation doctor is completed. Therefore, the capacity of the emergency data storage unit 15 can be small, and even if an expensive storage device having a high writing / reading speed is used, the cost does not increase significantly.

  Furthermore, since the medical image data stored in the emergency data storage unit 15 is also stored in the cloud storage 5, the medical image data can be browsed even after the interpretation by the external interpretation doctor is completed. .

  Conventionally, medical image data is attached to an e-mail and transmitted to an external interpretation doctor. However, since there is a limit on the data size that can be attached to an e-mail, there has been a problem that a large image cannot be transmitted. With the configuration of the present embodiment, there is no need to worry about the size of medical image data requested to be interpreted by an external interpreting doctor.

  In addition to these, various suitable effects can be obtained from the configuration disclosed in the present embodiment.

(Modification)
The configuration disclosed in the above embodiment can be modified in various ways.

  For example, when the patient ID of the patient to be urgently taken is known and there is medical image data taken in the past with respect to the patient, the terminal is used together with the medical image data related to the emergency shoot using the medical image data as a reference image. It may be provided to the device 3.

Details of this modification will be described with reference to FIGS.
As illustrated in FIG. 17, the PACS system 1 according to the modification further includes a past data acquisition unit 17. The past data acquisition unit 17 may be hardware including a processor such as a CPU, a memory such as a ROM or a RAM, a communication unit that communicates with a LAN or the Internet, or one or a plurality of processors execute a computer program. It may be a software function realized by doing so.

  The operator of the modality 2 inputs patient information such as a patient ID in the patient information area 62 in the input screen 60 of FIG. Further, the operator selects the type of examination from the list box 61, operates the switching button 63 to switch the imaging mode to the emergency imaging mode, and then operates the start button 64. With this operation as a trigger, the modality 2 sends a start notification including patient information, examination type information, and identification information indicating the emergency imaging mode to the PACS system 1.

  In the PACS system 1 that has received this start notification, medical image data (hereinafter referred to as past data) taken in the past by the past data acquisition unit 17 based on the patient information and examination type information included in the start notification. Is stored in the emergency data storage unit 15 with the emergency data ID issued by the emergency data ID issuing unit 13 in step S31. The past data acquired from the cloud storage 5 by the past data acquisition unit 17 includes, for example, a patient ID that matches the patient ID included in the patient information and examination type information of the same type as the examination type indicated by the examination type information. This is the attached medical image data.

  Further, in step S22, the access key providing unit 12 is included in the emergency data access key for accessing the medical image data related to the emergency imaging, the message notifying the start of imaging, and the start notification received from the modality 2. The patient information is transmitted to the terminal device 3 of the doctor requesting interpretation. The terminal device 3 that has received the emergency data access key or the like displays a pop-up 200 as shown in FIG. This pop-up 200 is obtained by adding the patient information (patient name) received from the access key providing unit 12 to the pop-up 100 shown in FIG.

  When the URL in the pop-up 200 is operated, the terminal device 3 tries to access medical image data indicated by the URL. Upon receiving access from the terminal device 3, the data providing unit 16 confirms that the emergency data access key (for example, the last four digits of the URL) included in the URL is mapped to the mapping table 90, and then The past data attached with the emergency data ID corresponding to the data access key is read from the emergency data storage unit 15 and transmitted to the terminal device 3. In particular, while waiting until medical image data is stored in the emergency data storage unit 15 (step S54), the terminal device 3 displays a viewer screen 201 as shown in FIG. The viewer screen 201 further displays a medical image based on patient information (patient name) received from the access key providing unit 12 and past data received from the data providing unit 16 with respect to the viewer screen 101 shown in FIG. It is added.

  Eventually, when receiving medical image data related to emergency imaging, the terminal device 3 displays a viewer screen 202 as shown in FIG. 18C on its own display. The viewer screen 202 further displays a medical image based on patient information (patient name) received from the access key providing unit 12 and past data received from the data providing unit 16 with respect to the viewer screen 102 shown in FIG. It is added.

  In the deletion process, the data providing unit 16 deletes the past data to which the same emergency data ID as the medical image data is attached together with the medical image data related to emergency imaging.

  If past data is provided to the terminal device 3 together with medical image data related to emergency imaging as in this modification, the external interpretation doctor can interpret the medical image data while comparing both images. In addition, it cannot be overemphasized that the effect | action similar to the said embodiment is acquired.

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

  DESCRIPTION OF SYMBOLS 1 ... PACS system, 2 ... Modality, 3 ... Terminal device, 4 ... Cloud, 5 ... Cloud storage, 10 ... Emergency photography judgment part, 11 ... Access key issuing part, 12 ... Access key provision part, 13 ... Emergency data ID issue , 14 ... Data receiving part, 15 ... Emergency data storage part, 16 ... Data providing part, 17 ... Past data acquiring part, 70 ... Shooting setting information, 80 to 81 ... Provision destination setting information, 90 ... Mapping table, 100 ... Pop-up, 101 ... viewer screen, 102 ... viewer screen.

Claims (11)

A medical image capturing apparatus that captures a patient and generates medical image data, a cloud-type storage unit that provides a storage function of the medical image data, and a terminal device that browses the medical image data can be communicated via a network A connected medical image processing system,
A data storage unit for storing medical image data;
A determination unit for determining whether the medical image capturing by the medical image capturing apparatus is emergency capturing or normal capturing other than emergency capturing;
When the determination unit determines that it is not emergency imaging, the medical image data received from the medical image imaging device is stored in the cloud storage unit, and when the determination unit determines emergency imaging, the medical image A storage processing unit for storing medical image data received from the imaging apparatus in the data storage unit ;
When provision of medical image data is requested from the terminal device , when provision of medical image data related to normal imaging is requested from the terminal device, the medical image data stored in the cloud storage unit is A data providing unit that provides the terminal device with the medical image data stored in the data storage unit when the terminal device is requested to provide medical image data related to emergency imaging from the terminal device ;
When it is determined that the emergency imaging is performed by the determination unit, the terminal device is notified of the start of the emergency imaging before the medical image data is provided to the terminal device by the data providing unit. A notification unit;
A medical image processing system comprising: When the provision of medical image data related to emergency imaging is requested, if the medical image data related to emergency imaging is not already stored in the data storage unit, the data providing unit stores the medical image data in the data storage 2. The medical image processing system according to claim 1, wherein the medical image data is read from the data storage unit and provided to the terminal device when the storage is completed . Wherein the data providing unit, after providing medical image data stored in the data storage unit to the terminal device, to claim 1, characterized in that to remove the medical image data stored in the data storage unit The medical image processing system described. When the determination unit determines that emergency imaging is performed, the storage processing unit stores the medical image data received from the medical image capturing apparatus in the data storage unit and also stores the medical image data in the cloud storage unit. The medical image processing system according to any one of claims 1 to 3 .   The determination unit receives identification information indicating whether medical imaging is emergency imaging or normal imaging from the medical imaging apparatus, and based on the received identification information, the imaging is emergency imaging or normal imaging. The medical image processing system according to claim 1, wherein the medical image processing system is determined.   The determination unit receives information indicating a part of a patient to be imaged from the medical image capturing apparatus from the medical image capturing apparatus, and when the part indicated by the information is a predetermined part for emergency imaging, The medical image processing system according to claim 1, wherein the medical image is determined to be emergency shooting. Issuing an access key for issuing an access key for the terminal device to access medical image data related to emergency imaging when the determination unit determines that imaging of the medical image by the medical imaging device is emergency imaging And
An access key providing unit that provides the terminal device with an access key issued by the access key issuing unit;
Further including
The said data provision part provides the medical image data corresponding to the said access key preserve | saved in the said data storage part with respect to the terminal device which tries access using the said access key. 6. The medical image processing system according to claim 1.   The access key providing unit refers to setting information that defines a terminal device corresponding to a candidate for interpreting a medical image, and provides the access key to the terminal device defined in the setting information. The medical image processing system according to claim 7.   The access key providing unit refers to setting information that defines the location of a candidate who interprets a medical image and a terminal device corresponding to each candidate, and among the terminal devices defined in the setting information, the medical key 8. The medical image processing system according to claim 7, wherein the access key is provided to a terminal device corresponding to a candidate located in a place other than a medical facility where the image photographing apparatus is installed.   The access key providing unit refers to setting information that defines a specialized field of a candidate who interprets a medical image and a terminal device corresponding to each candidate, and among the terminal devices defined in the setting information, 8. The medical image processing system according to claim 7, wherein the access key is provided to a terminal device corresponding to a candidate in a specialized field suitable for interpretation of medical image data related to imaging.   The data providing unit provides the medical image data stored in the data storage unit to the terminal device when the provision of medical image data related to emergency imaging is requested from the terminal device. The medical image processing system according to any one of claims 1 to 9, wherein medical image data captured in the past with respect to the patient related to the emergency imaging stored in the storage unit is provided to the terminal device. .

Images