WO2008059778A1

WO2008059778A1 - Medium management system, medium management device, and program

Info

Publication number: WO2008059778A1
Application number: PCT/JP2007/071883
Authority: WO
Inventors: Takafumi Nanjyo
Original assignee: Konica Minolta Medical & Graphic, Inc.
Priority date: 2006-11-13
Filing date: 2007-11-12
Publication date: 2008-05-22
Also published as: JP2010029223A

Abstract

A medium management system for easily managing receipt of a medium by the receiver when data on a medical image is transferred by using the medium. A server (3) creates medium registration information according to patient information LID and examination information LID contained in medical image data stored in a medium (9) when the medium (9) is created and transmits the medium registration information to a PDI managing device (11). The PDI managing device (11) stores the transmitted medium registration information in a medium management table. When the medium (9) is received at another medical institute, the receipt date and time of the medium management table (114) is updated according to the medium receipt information transmitted from the server (3) of the hospital, and the receipt of the medium (9) is registered.

Description

Specification

Media management system, media management apparatus and program

Technical field

The present invention relates to a media management system, a media management device, and a program.

Background art

In recent years, digitizing and handling medical images has become mainstream. Specifically, a medical image is digitized by a medical image generation apparatus (hereinafter referred to as “modality”) such as a CT (Computed Tomography) apparatus, an MRI (Magnetic Resonance Imaging) apparatus, and the like. It is stored and managed by a medical image management system called ror medical application;

[0003] Medical images are digitized as medical image data including patient information and examination information in a data format conforming to the DICOM (Digital Imaging and Communication in Medicine) standard. DICOM is a standard for communication and storage formats for medical images. By complying with this standard, mutual communication between different medical devices is ensured.

[0004] However, the current situation is that medical images cannot always be communicated properly just because they conform to the DICOM standard. This is because interpretation to the DICOM standard is left to each vendor (manufacturer), and the support range of the DICOM standard may vary from vendor to vendor.

[0005] Therefore, in recent years, IHE (Int egrating Healthcare Enterprise) for applying standards such as DICOM standard and medical information standardization standard (Health Level 7; hereinafter referred to as “HL 7”) in accordance with the workflow in clinical practice. ) And IHE-J (IHE-Japan) guidelines have been established and implemented. Hereinafter, IHE and IHE-J will be collectively referred to as “IHE”. By complying with this IHE, intercommunication between medical devices has been improved, and it has become possible to construct a low-cost system using multi-vendors, making it easier to provide medical image data via a network.

[0006] In addition, as a method for providing medical image data, data is transferred offline using various portable storage media (hereinafter referred to as "media") such as MO disks and CD-Rs. The data structure for storing medical image data on media is also defined by IHE. This makes it easier to provide medical image data using the media. As a technique for storing medical image data in various media, a technique for storing medical image data whose findings have been created by a doctor in a medium is known (see Patent Document 1).

).

Patent Document 1: Japanese Patent Application Laid-Open No. 2002-153427

Disclosure of the invention

Problems to be solved by the invention

[0007] By the way, since medical image data written on media includes patient personal information such as patient information and examination information, it is necessary to clarify the location of the media from the viewpoint of personal information. is there. However, when medical image data is stored in a portable medium as in Patent Document 1, in order to confirm whether the medium has been received by the data transfer destination, the user himself / herself cannot communicate via telephone or e-mail. It was necessary to communicate manually by means, which was complicated.

[0008] Further, in medical diagnosis, it is important to make a diagnosis in comparison with past medical images, or to make a diagnosis using the latest medical images. The medical images that can be referred to in the above are limited to the medical images in the media. For this reason, when a past medical image or the latest medical image is required rather than the medical image in the medium, it is necessary to create a new medium and transfer the data.

[0009] However, in this case where additional media must be created for media that has already been data-transferred, the user investigates patient information and examination information related to medical images stored in the media, and those Based on the information! / And you have to request the creation of the media! /, So it is very cumbersome. Also, multiple media will be created for a single patient, and it will be very cumbersome to manage whether these media are reliably delivered to the data transfer destination.

[0010] The present invention has been made in view of the above-described problems, and an object of the present invention is to easily receive a medium at a transfer destination in data transfer of a medical image using the medium. It is to realize a media management system that can be managed. Means for solving the problem

[0011] In order to solve the above problems, according to a first aspect of the present invention,

A media creation device that writes medical image data including identification information to a storage medium, a media playback device that reads and plays back the medical image data written to the storage medium, and the media creation device that is the storage medium for the media playback device In a media management system configured to allow data communication with a media management device that manages the transport status of

The media creation device includes:

A creator transmission means for extracting identification information from the medical image data written in the storage medium and transmitting the identification information to the media management device;

The media playback device includes:

Transport destination transmission means for extracting identification information from medical image data written on a storage medium transported from the media creation device and transmitting it to the media management device, the media management device comprising:

A creation source receiving means for receiving identification information of medical image data from the media creation device;

Storage means for storing unacknowledged information in association with identification information received by the creator receiving means;

A transfer destination receiving means for receiving identification information of medical image data from the media playback device;

Updating means for reading unreceived information associated with the identification information received by the transfer destination receiving means from the storage means, changing the unreceived information to received information and updating the storage means;

It is characterized by having!

[0012] Further, the media management device includes:

The media playback device power further comprises re-transfer request means for transmitting the received identification information to the media creating device and requesting re-transfer of the storage medium,

The media creation device includes: Medical image storage means for storing a plurality of medical image data;

Re-transfer request receiving means for receiving identification information transmitted in response to a request for re-transfer of the storage medium;

Media recreating means for reading medical image data including the same identification information as the identification information received by the retransfer request receiving means from the medical image storage means, and writing the medical image data to a new storage medium;

Identification information retransmission means for transmitting the identification information of the medical image data written by the media re-creation means to the media management device;

Is preferably further provided.

[0013] The media management device includes:

Notification means for transmitting notification information indicating that the storage medium has been received by the media playback device to the media creation device when the unacknowledged information is changed to received information by the updating means. It is preferable to further provide.

[0014] Further, according to the second aspect of the present invention,

The media management device

A creator receiving means for receiving identification information of the medical image data from a creator of the storage medium in which the medical image data is written;

Transfer destination receiving means for receiving identification information of medical image data stored in the storage medium from the transfer destination of the storage medium;

It is characterized by having!

[0015] Further, according to the third aspect of the present invention,

Program, computer,

Identification of the medical image data from the creator of the storage medium on which the medical image data is written Creator receiving means for receiving information,

Update means for reading unacknowledged information associated with the identification information received by the transfer destination receiving means from the storage means, changing the unreceived information to received information and updating the storage means;

As a special feature, let's make it happen!

The invention's effect

According to the present invention, when identification information is received from a media creation device that is a creation source of a storage medium that stores medical image data, unacknowledged information is associated with the identification information and stored in the storage means. Remember. When the same identification information as the identification information stored in the storage means is received from the media playback device to which the storage medium is transferred, the unreceived information associated with the identification information is changed to received information. .

[0017] Therefore, in the media management apparatus, information indicating whether or not the storage medium is received at the transfer destination of the medical image data is updated. Therefore, in data transfer of medical images using a storage medium, it is possible to realize a media management system or the like that can easily manage reception of the storage medium at the transfer destination.

[0018] When a request for re-transfer of the storage medium from the media playback device is made, the media creation device receives medical image data including the same identification information as the identification information transmitted by the request. Write to a new storage medium and send the identification information contained in the medical image data to the media management device.

Thereby, the information indicating whether or not the medical image data including the same identification information is received by the media management apparatus is also updated for the storage medium. For this reason, even if an additional storage medium is created and a plurality of storage media are created for a single patient, it is easy to manage the receipt of these storage media at the transfer destination.

[0020] Further, when the unacknowledged information is changed to received information by the updating means, the media management The device may send the notification information to the media creation device. As a result, the media creation device that created the storage medium can confirm whether or not the storage medium has been received at the data transfer destination.

Brief Description of Drawings

FIG. 1 is an example of a system configuration diagram of a medical image providing system.

[Figure 2] An example of a PACS system configuration.

FIG. 3A is a diagram showing a data configuration example of medical image data.

FIG. 3B is a diagram showing a data configuration example of the header information shown in FIG. 3A.

FIG. 4A is a diagram showing a data configuration example of patient information shown in FIG. 3B.

FIG. 4B is a diagram showing a data configuration example of the inspection information shown in FIG. 3B.

FIG. 4C is a diagram showing a data configuration example of the series information shown in FIG. 3B.

4D is a diagram showing a data configuration example of the detailed image information shown in FIG. 3B.

FIG. 5 is a block diagram showing an example of a functional configuration of a server.

FIG. 6 is a diagram showing an example of a data structure of media corresponding to IHE.

FIG. 7 is a block diagram showing an example of a functional configuration of a PDI management apparatus.

FIG. 8 is a diagram showing a data configuration example of a media management table.

FIG. 9 is a sequence diagram for explaining a specific operation of the medical image providing system.

[Figure 10] An example of the server display screen.

BEST MODE FOR CARRYING OUT THE INVENTION

[0022] Hereinafter, the media management system of the present invention is the medical image providing system S of FIG. 1, the media creation device and the media playback device are the server 3 of FIG. 2, and the media management device is the PDI (Portable Data for Imaging of FIG. 1). ) An embodiment applied to the management apparatus 11 will be described with reference to FIGS.

[Outline of Medical Image Providing System]

First, an outline of the medical image providing system S shown in FIG. 1 will be described. FIG. 1 is a block diagram showing an example of the system configuration of the medical image providing system S. As shown in FIG. According to FIG. 1, the medical image providing system S is configured such that the PACS 1 for each hospital and the PDI management apparatus 11 can communicate with each other via the public network N1. In Fig. 1, Hospital A and Hospital B Each is provided with PACS1.

[0024] Medical image data stored and managed in PACS 1 is transferred to PACS 1 in another hospital via public network N1 or media 9. The data structure for storing data in the media 9 is predetermined by the IHE, and each PACS1 is compatible with the IHE, which makes it easy to read medical image data from the media 9.

FIG. 2 shows an example of the system configuration of PACS 1. According to FIG. 2, the PACS 1 is configured so that data communication is possible by connecting the server 3 and the client 5 via the in-hospital network N3. The in-hospital network N3 is an in-hospital dedicated network to which various modalities M and film output devices 7 are connected. In-hospital network N3 is secured with a firewall etc. between public network N1

Yes

[0026] Modality M is a CT, CR, MRI, mammography device, ultrasound diagnostic device, etc., and converts the data signal of the image obtained according to the operation of the radiographer to digital data in accordance with the DICOM standard Then, medical image data is generated. Modality M sends the generated medical image data to server 3.

For example, CR irradiates a subject with radiation, and the radiation transmitted through the subject is absorbed by the plate-like stimulable phosphor. Then, the stimulable phosphor is excited while being scanned with, for example, laser light, thereby causing the radiation energy stored in the stimulable phosphor to emit light, and the radiation obtained by photoelectrically converting the emitted light. The image data signal is digitally converted to generate image data of the subject.

[0028] FIGS. 3A and 3B show an example of the data structure of the medical image data D1. According to FIG. 3A, the medical image data D1 includes header information D3 and image data D5 as supplementary information. As shown in FIG. 3B, the header information D3 includes patient information D30, examination information D32, series information D34, and detailed image information D36, and is described according to the DICOM standard, for example.

[0029] The header information D3 is set by the modality M when generating the medical image based on the order information issued from HIS (Hospital Information System) or RIS (Radiological Information System). Is done. still The header information D3 shown in FIG. 3B is a schematic representation of the main data in this embodiment, and the other data is not shown.

As shown in FIG. 4A, patient information D30 includes patient information LID (Link Identification) 31 and various information related to the patient such as the patient's name, patient, date of birth, and sex.

[0031] Examination information D32 includes examination information LID33, examination instance UID (Unique Identification) issued for image management, and patient information LID associated with examination information D32, as shown in FIG. 4B. And various information related to inspection such as inspection date and inspection ID.

[0032] As shown in FIG. 4C, the series information D34 includes the series information LID35, the series instance UID issued for image management, the examination information LID associated with the series information D34, and the medical image. It includes the name indicating the type of modality M that was taken, the series number of that modality M, the modality M such as the examination site, and various information related to the radiography.

[0033] As shown in Fig. 4D, the detailed image information D36 is an SOP (Service Object Pair) instance UID configured by combining the detailed image information LID37, the series instance UID, and the address indicating the file storage location of the medical image. It is comprised including. The detailed image information D36 includes the series information LID associated with the detailed image information D36, the image number assigned when the medical image is generated, and the image management such as the image time when the image is generated. It includes various information related to image generation.

These patient information LID31, examination information LID33, and series information LID35 are identification information for associating various types of information included in the header information D3 and for identifying the medical image data D1. That is, the patient information LID31 is associated with the examination information D32, and the examination information LID33 is associated with the series information D34.

[0035] Further, the series information LID 35 is associated with the examination information D32 and the image detailed information D36, and the image detailed information LID is associated with the series information D34. It is possible to identify the medical image data D1 individually based on the identification information such as the patient information LID31, the examination information LID33, and the series information LID35.

[0036] The server 3 uses the medical image data D1 transmitted from the modality M as the medical image data. Database management based on header information D3 included in data Dl. Also, the medical image data D1 selected based on the user operation is written to the media 9 in the data format based on IHE.

[0037] The client 5 is a terminal device that includes an LCD (Liquid Crystal Display) or the like and reproduces and displays a medical image based on the medical image data D1. When the user designates medical image data D1 to be reproduced and displayed, the medical image data D1 is read from the server 3 or the media 9 and reproduced and displayed.

[0038] The film output device 7 is an image forming device configured by a film digitizer or the like, and forms and outputs a medical image based on the medical image data D1 on a recording medium. When the user designates medical image data D1 for film output, the medical image data D1 is read from the server 3 or the media 9, and the medical image is formed on a recording medium such as a heat-sensitive film and output. .

[Server functional configuration]

Next, the functional configuration of the server 3 will be described with reference to FIGS. FIG. 5 is a block diagram showing an example of the functional configuration of the server 3. As shown in FIG. 5, the control unit 30, the input unit 31, the display unit 32, the communication unit 33, the storage unit 34, I / F part 35 is comprised.

[0040] The control unit 30 includes a CPU (Central Processing Unit), a ROM (Read Only Memory),

This is a control unit that is composed of RAM (Random Access Memory), etc., and that manages and controls the server 3 by controlling the operation of each functional unit and controlling data input / output between the functional units.

Specifically, a program stored in the ROM or the storage unit 34 is read according to an operation signal input from the input unit 31, and processing according to the program is executed. Based on the processing result, the display screen of the display unit 32 is updated, the data is stored in the storage unit 34, data communication with an external device is performed via the communication unit 33, and the like.

[0042] The input unit 31 includes various key groups such as cursor keys and numeric keys, and a pointing device such as a mouse touch panel. The input unit 31 outputs to the control unit 30 an operation signal corresponding to the key pressed by the user or an operation signal corresponding to the coordinate position on the screen designated by the pointing device. [0043] The display unit 32 includes a CRT (Cathode-ray Tube), an LCD, and the like, and displays a display screen based on the control of the control unit 30, reproduces and displays the medical image data D1, and the like. The communication unit 33 is configured by a LAN interface, a modem, and the like, and is a functional unit that performs data communication with an external device via the hospital network N3 or the public line network N1. The I / F unit 35 is a functional unit that performs data communication with the media drive 40 based on a predetermined communication method, and is configured by, for example, USB or SCSI.

[0044] The media drive 40 is a device that reads / writes data from / to various media. If it is a CD drive, it writes data to a CD-R or CD-RW, and if it is an MO drive, writes data to the MO disk. Read. In the present embodiment, other electronic media such as DVD-R, DVD-RW, and HDD may be adopted as an example of a portable storage medium such as a CD-R or MO disk. /.

The storage unit 34 is a functional unit that reads / writes data from / to a magnetic or optical storage medium, and includes a HDD (Hard Disk Drive) or the like. According to FIG. 5, the storage unit 34 stores a medical image DB 340, a basic information DB 341, media registration information 342, and media receipt information 343.

The medical image DB 340 is a database that stores image data D5 included in the medical image data D1 received from the modality M in a searchable manner. The basic information DB 341 is a database that stores the header information D3 included in the medical image data D1 received from the modality M in a searchable manner.

[0047] Upon receiving the medical image data D1, the control unit 30 separates the header information D3 and the image data D5, and stores them in the basic information DB 341 and the medical image DB 340, respectively. At this time, a pair of header information D3 and image data D5 are associated with each other by adding address information or the like for associating paired header information D3 and image data D5.

[0048] For example, when the user designates header information D3 stored in the basic information DB 341, image data D5 associated with the header information D3 is read from the medical image DB 340 and reproduced and displayed. When an instruction to write the medical image on the medium 9 is input, the medical image data D1 is written on the medium 9.

[0049] The data structure for writing the medical image data D1 to the media 9 is the same as the IHE as shown in FIG. Shell data structure is desirable. The data structure shown in FIG. 6 is a profile called PDI related to data operation when medical image data D1 is stored in media 9, and is defined by IHE.

According to FIG. 6, the DICOMDIR file 90, the DIC OM directory 91, the OTHER file 92, and the OTHER directory 93 are stored in the root directory of the medium 9.

[0051] The DICOM directory 91 is a directory for storing medical image data D1 conforming to the DICOM standard, and an index of the directory is stored in the DICOMDIR file 90.

Remembering the DICOMDIR file 90 and DICOM directory 91 is a mandatory requirement for PDI.

[0052] The OTHER directory 93 is a directory for storing an application program 94 such as a browsing application for simply reproducing and displaying the medical image data D1, and a setting file 95 required for executing the application program 94. The OTHER file 92 stores an index of the OT HER directory 93, an initial setting for automatic startup of the application program 94, and the like.

[0053] When storing the medical image data D1 in the medium 9, the control unit 30 generates a data structure as shown in Fig. 6 in the medium 9, and stores various data. By storing medical image data D1 and the like with such a data structure defined by IHE, medical image data D1 can be easily read by PACS1 of other medical institutions that support IHE. It comes to be.

The media registration information 342 in the storage unit 34 in FIG. 5 is data generated for registering the media 9 created by the server 3 in the PDI management apparatus 11. The control unit 30 ends the storage of the medical image data D1 in the medium 9 based on the user operation, and when the creation of the medium 9 is completed, the patient information LID31 is obtained from the header information D3 of the stored medical image data D1. Then, the inspection information LID33 is extracted.

Then, the date and time when the medium 9 is created (creation date and time) and the type of media 9 (media type) are acquired, and these pieces of information are temporarily stored in the storage unit 34 as the media registration information 342. The control unit 30 transmits the media registration information 342 to the PDI management device 11 to Then, the creation of the media 9 is registered in the PDI management device 11.

Further, the media reception information 343 is data generated for registering in the PDI management apparatus 11 that the media 9 sent from another medical institution has been received. When the control unit 30 detects an instruction input indicating that the medium 9 has been received based on the user operation, the control unit 30 reads the header information D3 of the medical image data D1 stored in the medium 9 and reads the header information. Extract patient information LID31 and examination information LID33 from D3.

[0057] Then, the patient information LID31 and the examination information LID33 are temporarily stored in the storage unit 34 as the media receipt information 343, and the media receipt information 343 is transmitted to the PDI management device 11 so that the media 9 Is registered in the PDI management device 11.

[Functional configuration of PDI management device]

Next, the functional configuration of the PDI management apparatus 11 will be described with reference to FIGS. FIG. 7 is a block diagram showing an example of the functional configuration of the PDI management device 11. As shown in FIG. 7, the control unit 110, the input unit 111, the display unit 112, the storage unit 113, and the communication unit 115 It is configured with. The functional configurations of the control unit 110, the input unit 111, the display unit 112, the storage unit 113, and the communication unit 115 that constitute the PDI management apparatus 11 are the control unit 30, the input unit 31, the display unit 32, and the storage unit of the server 3. Since the functional configurations of the unit 34 and the communication unit 33 are the same, detailed description thereof is omitted.

The storage unit 113 of the PDI management apparatus 11 stores a media management table 114 as shown in FIG. FIG. 8 shows a data configuration example of the media management table 114. As shown in FIG. 8, the media management table 114 includes a media management LID 114a, a patient information LID 114b, an examination Toshiyuki UD114c, a media type further lJ114d, a creation date 114e, and a receipt date 114f. It is a data table that is stored in association.

[0060] The media management LID 114a is an identifier for managing the media 9 created by the PACS1, and a unique ID is generated and set when the creation of the media 9 is registered. Patient information LID 114b, examination information LID 114c, media type 114d, and creation date 114e are media registration information 342 transmitted from server 3 of PACS 1. In the media management table 114, the media management LID 114a is a primary key, and the patient information LID 114b and the examination information LID 114c are external reference keys. [0061] The reception date and time 114f is information indicating whether or not the medium 9 for which creation has been registered has been received by another medical institution, and is set to either unreceived information or received information. The unacknowledged information is information indicating that the created media 9 is still received by the destination PACS 1! /, N! /, For example, invalid data (for example, “FFFF”) force S is set. The The received information is information indicating that the media 9 has been received in the destination PACS1, and information on the date and time of reception is set.

[0062] Upon receiving the media registration information 342 from the PACS1 from which the media 9 is created, the control unit 110 generates a new media management LIDl 14a and associates the media registration information 342 with the media management LIDl 14a. Store in the media management table 114. At this time, unacknowledged information is set in the reception date 1 14f.

[0063] Then, when the media receipt information 343 is received from the PACS 1 to which the media 9 is sent, the media management table 114 is searched for a record that matches the patient information LID and the examination information LID included in the media receipt information 343. When searching for a record that matches the patient information LID and the detection information LID, the control unit 110 acquires the current date and time. Then, the media management table 114 is updated by rewriting the unacknowledged information set in the received date and time 114f in the retrieved record with the current date and time as the received information.

[0064] The media management table 114 in FIG. 8 shows that the media 9 indicated by '12345678, of the media management LIDl 14a is received at' 2002/9/27 10:42 '. The media 9 indicated by '12345679' indicates that it has not been received yet.

[Specific Operation of Medical Image Providing System]

Next, specific operations of the medical image providing system S will be described with reference to FIGS. FIG. 9 is a sequence diagram showing processing performed by the hospital A server 3 (referred to as server 3a), hospital B server 3 (referred to as server 3b), and the PDI management apparatus 11 in FIG. These are display screen examples of the servers 3a and 3b.

[0066] In the following description, each functional unit constituting the server 3a of the hospital A is given a symbol "a", such as a control unit 30a, an input unit 31a, a display unit 32a. The functional units constituting the hospital 3 server 3b include a control unit 30b, an input unit 31b, a display unit 32, etc. The description will be given with the symbol “b” attached. In addition, the subject of the processing of the sequence diagram of FIG. 9 is the power that is the control unit of the server 3 and the PDI management device 11, and for simplicity of explanation, the subject is the server 3a, the server 3b, and the PDI management device 11. To do.

First, the server 3a that is the media creation source displays a medical image list screen 320 as shown in FIG. 10 on the display unit 32a. The medical image list screen 320 is a screen that displays a list 321 of medical image data D1 stored in the medical image DB 340, basic information DB 341, and media 9a. For example, a list of header information D3 is displayed. . The user operates the input unit 31a on the medical image list screen 320 to select a desired medical image and designates the media creation button 323.

[0068] Upon detecting the designation of the media creation button 323, the server 3a reads the medical image data D1 selected on the medical image list screen 320 from the medical image DB 340 and basic information DB 341, and writes it to the media 9a. (Step Al). Then, the media registration information 342 is generated based on the header information D3 of the medical image data D1 written on the media 9a, and is transmitted to the PDI management device 11, thereby registering the creation of the media 9a ( Step A2).

[0069] At this time, when receiving the media registration information 342 from the server 3a (step C1), the PDI management apparatus 11 generates a new media management LIDl 14a and registers the media in association with the media management LIDl 14a. Information 342 is stored in the media management table 114 (step C2). At this time, invalid data as unreceived information is set in the reception date 114f.

[0070] The user of the server 3a sends the created media 9a to the hospital B that is the media delivery destination.

The user on the hospital B side who received the media 9a loads the media 9a into the media drive 40b and displays a list of medical image data D1 stored in the media 9a as shown in FIG. Then, the media receipt button 322 in the medical image list screen 320 is designated by the operation of the input unit 31b, and the receipt of the media 9a is registered in the PDI management apparatus 11.

[0071] When the server 3b detects the designation of the media reception button 322, the server 3b generates media reception information 343 from the header information D3 of the medical image data D1 stored in the media 9a, and transmits it to the PDI management apparatus 11 (step S3). B1).

[0072] Upon receiving the media receipt information 343 (step C3), the PDI management device 11 receives the media receipt information 343. The patient information LID and the examination information included in the receipt information 343 The same patient information LID11 4b and the examination information LIDl 14c are associated with the media management LIDl 14a as the media management table 114 (step C4). .

[0073] Then, if the media management LIDl 14a is stored in the media management table 114, the current date and time are acquired, and the current date and time are set in the reception date and time 114f associated with the media management LIDl 14a. To change the unacknowledged information to received information (Step C5).

[0074] The PDI management device 11 transmits data indicating that the medium 9 has been received by the server 3b (for example, reception date 114f) to the server 3a and notifies the server 3a of the reception (step C6). . At this time, the server 3a receives a notification from the PDI management device 11 and displays a message to the effect that the media 9 has been received on the display unit 32a (step A3).

[0075] Next, the server 3b performs a PDI management to query and match the medical images related to the medical image data D1 stored in the received media 9a (hereinafter referred to as "related images"! /). Proceed to server 3a via device 11. Here, the related images include a past image and a latest image. The past image is a medical image of the same modality and the same part taken in the past than the medical image stored in the media 9. The latest image is a medical image of the same modality and the same part, which is taken after the medical image stored in the medium 9.

The server 3b extracts the patient information LID from the medical image data D1 stored in the medium 9a, and transmits the patient information LID to the PDI management apparatus 11 (step B2). On the other hand, when receiving the patient information LID (step C7), the PDI management apparatus 11 reads the examination information LID associated with the patient information L ID from the media management table 114 and sends it to the server 3a together with the patient information LID. By transmitting, a related image search request is made (step C8).

[0077] When the server 3a receives a search request for related images for the patient information LID and the examination information LID from the PDI management device 11 (step A4), the server 3a searches the basic information DB 341 for header information D3 including each LID. (Step A5). Based on the patient ID, examination date, examination time, examination site, modality, etc. included in the retrieved header information D3, a related image of the same patient, the same modality, and the same examination site is searched for. Search results The result is transmitted to the server 3b via the PDI management device 11 (steps A6, C9 to C10).

[0078] When the server 3b receives the search result from the PDI management apparatus 11 (step B5) and determines that there is a related image from the search result, the server 3b again receives the patient information LID in order to request transmission of the related image. The data is transmitted to the server 3a via the PDI management device 11 (step B6). At this time, the PDI management apparatus 11 reads the detection information LID associated with the patient information LID received from the server 3b from the media management table 114, and transmits it to the server 3a together with the patient information LID (step C1). ; ~ C12).

[0079] When the server 3a receives the patient information LID and the examination information LID from the PDI management apparatus 11 (step A7), the server 3a reads out the header information D3 of the related image from the basic information DB 341 based on each LID, and the header information The image data D5 associated with D3 is read from the medical image DB 340, and written as new medical image data 9b as medical image data D1 to create additional calorie media (step A8).

[0080] Then, in order to register the creation of the media 9b, the media registration information 342 is generated based on the medical image data D1 stored in the media 9a, and transmitted to the PDI management apparatus 11 (step S1). A9). It should be noted that steps A9 to A16, B7, and C13 to C18 of each device for registering the creation of the additional media 9b by the server 3a and registering and notifying the receipt of the media 9b by the server 3b are the above-described steps A2 to A3. , Bl, C1 to C6, and the explanation is omitted.

Thus, for example, as shown in FIG. 8, the media 9a having the patient information LID '11111111' and the examination information LID '56789012' is registered in the PDI management apparatus 11, and the related image is received after receipt by the server 3b. Is stored in the patient information LID '11111112' and examination information LID '34567890' force S media management table 114 of the medical image data D1 stored in the medium 9b.

As described above, according to the present embodiment, when the media 9 of the server 3 is created, the media registration information 342 is stored in the PDI management device 11 and when the media 9 is received by another medical institution. Updates the receipt date and time of the media management table 114 with the media receipt information 343 transmitted from the server 3 of the hospital, and registers that the media 9 has been received. This allows the PDI management device 11 to check whether the created media 9 has been received by another medical institution. It can be managed centrally.

[0083] When there is a related image of the medical image stored in the received media 9, the request is made to create the media 9 storing the related images, and the creation and reception of the media 9 is also a PDI management device. 11 can be registered. For this reason, even when a plurality of additional media 9 are created, the PDI management device 11 is surely managed! Therefore, in the medical image data transfer using the media 9, it is possible to realize the medical image providing system S that can easily manage whether or not the media has arrived at the transfer destination.

The above-described embodiment is an example to which the present invention is applied, and the applicable range is not limited to the above-described example. For example, when the PDI management device 11 receives the media registration information 342 from the server 3, the PDI management device 11 counts the number of days elapsed from the received date and time, and the elapsed number of days is the predetermined number of days without registering the receipt of the media 9. If it exceeds (for example, 7 days), a warning may be sent to the creator of the media 9. As a result, if the media 9 has not arrived at the destination of the media within a predetermined number of days, it is possible to use the power S to notify the media creator.

[0085] Further, the PDI management apparatus 11 has been described as being realized as a separate apparatus from the server 3. However, the PDI management apparatus 11 and the server 3 may be configured integrally or in the same hospital. It may be arranged on the network N3. As a result, the creation and receipt of the media 9 can be managed within the medical institution that created the media 9.

Further, the power described in the media management table 114 as the data configuration shown in FIG. 8 is not limited to the illustrated example. For example, comment information may be stored in association with the media management LID 114a. Good. Here, the comment information is data indicating comments including the purpose of creation and special notes for the media 9 and is input by the user of the server 3.

In this case, the server 3 transmits the media registration information 342 to the media reception information 343 in association with the comment information when the medium 9 is created and received, and transmits it to the PDI management apparatus 11. As a result, it is also possible to manage comments on the media 9 by the PDI management device 11. Further, the invalid data is set as unreceived information and the current date and time is set as received information. However, for example, a flag indicating whether or not the media 9 has been received may be set. . In this case, the flag OFF indicates unacknowledged information, and ON indicates received information. Thus, the data configuration example of the media management table 114 is not limited to that shown in FIG. 8, and can be changed as appropriate.

[0089] The entire disclosure of Japanese Patent Application No. 2006-306678, filed on November 13, 2006, including the description, claims, drawings, and abstract, is incorporated in part in this application as it is. It is.

Industrial applicability

[0090] The present invention may be used in the medical field where data transfer of medical images using media is performed.

Explanation of symbols

S Medical image provision:

1 PACS

3 Sano

5 clients

9 Media

30 Control unit

31 Input section

32 Display

33 Communication Department

34 Memory

342 Media Registration Information

343 Media receipt information

35 I / F section

40 Media drive

11 PDI management device

110 Control unit 11 1 Input section

112 Display

113

114 Media management table

Dl Medical image data

D3 header information

D5 image data

31 Patient information LID

33 Inspection information LID

35 Series Information LID

37 Detailed image information LID

Claims

The scope of the claims

[1] A media creation device that writes medical image data including identification information to a storage medium, a media playback device that reads and plays back the medical image data written to the storage medium, and the media creation device power to the media playback device In a media management system configured to allow data communication with a media management device that manages the transfer state of the storage medium,

The media creation device includes:

The media playback device includes:

A media management system comprising:

[2] The media management device includes:

The media creation device includes:

Medical image storage means for storing a plurality of medical image data; Re-transfer request receiving means for receiving identification information transmitted in response to a request for re-transfer of the storage medium;

The media management system according to claim 1, further comprising:

[3] The media management device includes:

Notification means for transmitting notification information indicating that the storage medium has been received by the media playback device to the media creation device when the unacknowledged information is changed to received information by the updating means. The media management system according to claim 1, further comprising:

[4] A creator receiving means for receiving identification information of the medical image data from the creator of the storage medium in which the medical image data is written;

A media management apparatus comprising:

[5] Computer

A source receiving means for receiving identification information of the medical image data from the source of the storage medium in which the medical image data is written;

Storage means for storing unacknowledged information in association with identification information received by the creator receiving means; Transfer destination receiving means for receiving identification information of medical image data stored in the storage medium from the transfer destination of the storage medium;

Program to function as.