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

Abstract

<P>PROBLEM TO BE SOLVED: To provide a medical image processing system capable of efficiently managing medical image files by a versatile and inexpensive device structure without restriction of an operation system. <P>SOLUTION: The system is for managing medical image files with image information consisting of a plurality of attributes. The system comprises a recording device 100 for recording information files with file names including image information in the medical information files, a conversion table 280 for correlating the character string constituting the name of each file, named by separating the plurality of attributes of the image information with separating characters and connecting the separated attributes in a predetermined order, to a conversion character string for compression, a compression part 282 for converting/compressing the character string constituting the name of each information file, and a storage part 243 for classifying the information files with the compressed file names into a plurality of directories with names including at least part of the plurality of attributes of the image information respectively and storing the classified information files in the recording device 100. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a medical information management apparatus, a medical information management system, a medical information management method, and a medical information management program, and more particularly to a management apparatus, system, method, and program for medical image information.

  In recent years, with the increasing demand for high-quality medical care, the introduction of information systems in the medical field has been accelerated against the background of advances in computer technology and standardization such as DICOM (Digital Imaging and Communication in Medicine). Is moving forward. In hospitals having various modality devices such as an ultrasonic diagnostic apparatus, an MR (Magnetic Resonance) apparatus, a CT (Computerized Tomography) apparatus, and a CR (Computed Radiography) apparatus, a system environment in which these are connected via a network is being prepared.

  In such a system environment, the state in the patient's body imaged by the modality device is stored as an image file in the server, and the doctor reads the image file from the server using the browsing device and makes a diagnosis (Patent Document 1).

  In general, DICOM-compliant servers are large and all-in-one PC type systems are rarely expandable. In addition, if a system failure occurs, all functions are down and operational reliability is low. It was. In addition, database such as SQL (Structured Query Language) and Oracle (registered trademark) is used for managing image data in the server. However, a system using these databases requires expensive hardware. Expensive hardware generally has a high failure rate due to the large number of parts. Therefore, the cost for maintenance inspection increases.

  Therefore, in order to provide a medical information management system capable of improving the stability, efficiency, and durability of the system, the plurality of attributes of the image information of the medical image file are separated from each other by a delimiter and connected to each other in a predetermined order. And classifying the information file having the file name attached to the plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, and storing the information file A medical information management system with a recording unit was proposed.

JP 2002-135499 A

  However, in the above-described conventional medical information management system, a file name in which a plurality of attributes of image information of a medical image file are separated by a delimiter character and connected to each other in a predetermined order increases the number of characters. Some operating systems of computers constituting the management system cannot be handled.

  In particular, in an operating system employed in a general-purpose inexpensive computer, there is a limitation on the character string of the file name, so that it has been desired to be compatible with various operating systems.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a medical image processing system that can efficiently manage medical image files with a general-purpose and inexpensive apparatus configuration without limitation of an operating system. There is to do.

According to the present invention, a device for managing a medical image file having image information consisting of a plurality of attributes,
An information storage unit for storing an information file having a file name including the image information of the medical image file;
A conversion table for associating a plurality of attributes of the image information of the medical image file with a delimiter character and composing a character string constituting a file name that is attached to each other in a predetermined order and associated with a conversion character string for compression;
A compression unit that converts the character string constituting the file name of the information file using the conversion table, and compresses the file name of the information file;
Classifying the information file with the file name compressed by the compression unit into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file; A storage unit for storing in the information storage unit;
A medical information management apparatus characterized by comprising:

  Here, the medical image file refers to, for example, imaging a patient using a modality device such as a CT (Computerized Tomography) device, an MR (Magnetic Resonance) device, or a CR (Computed Radiography) device in an examination at a medical site. It is the file of the obtained medical image data. The image information of the medical image file includes, for example, a plurality of attributes such as a patient ID, which is an identification number of a photographed patient, a patient name, a patient's gender, a patient's date of birth, and an age. Further, the image information of the medical image file includes the date and time of the taken examination, the examination reception number, the examination ID, the examination instance UID, and the like. These are, for example, attribute information of image data conforming to DICOM.

  According to the present invention, since the file name can be compressed, for example, the present apparatus can be applied even to an operating device in which the file name has a limited number of characters. Furthermore, the file search efficiency can be improved by compressing the file name.

  The medical information management apparatus may further include an image storage unit that stores a storage image file having a file name including the image information of the medical image file, and the compression unit includes the file of the storage image file. The character string of the name is converted using the conversion table, and the file name of the image file for storage is compressed, and the storage unit stores the file name with the file name compressed by the compression unit The image file can be classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, and stored in the image storage unit.

  In the medical information management apparatus, the compression unit can compress the directory name by converting a character string constituting the directory name using the conversion table.

  According to this configuration, since the directory name can be compressed, for example, this apparatus can be applied even to an operating apparatus in which the directory name has a limited number of characters. Furthermore, file search efficiency can be improved by compressing the directory name.

  In the medical information management device, the character string converted by the compression unit using the conversion table may be an instance UID among the plurality of attributes of the image information of the medical image file.

According to the present invention, a device for managing a medical image file having image information consisting of a plurality of attributes,
A predetermined character string constituting a file name obtained by connecting the plurality of attributes of the image information of the medical image file with a delimiter character and connecting them in a predetermined order is converted into a predetermined compression conversion character string. The converted information file is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, and an information storage unit in which the information file is stored; A predetermined character string that constitutes a file name that is connected to each other in a predetermined order by separating the plurality of attributes of the image information of the medical image file and converted into a predetermined compressed conversion character string. In a medical information management device comprising: an image storage unit that stores image files for classification and storage in the plurality of directories,
A search key receiving unit that receives a search key used when searching the medical image file;
A search path generator for generating a search path based on the search key;
A conversion table associating the predetermined character string with the conversion character string for compression;
A file name generation unit for generating a search file name based on the search key;
A conversion unit that converts a character string of the search file name generated by the file name generation unit using the conversion table;
Using the search path and the search file name converted by the conversion unit, an information search unit for searching the corresponding information file in the corresponding directory from the information storage unit;
An extraction unit for extracting the image information indicated by the file name of the information file acquired by the information search unit;
A medical information management apparatus characterized by comprising:

  According to the present invention, the search key specified in the format conforming to the DICOM standard is similarly code-converted by the conversion table used for compressing and converting the file name, and the corresponding file can be searched, so that it is compressed. The search can be performed with the file name as it is, and the character string to be searched is shortened.

  In the medical information management apparatus, a predetermined character string is converted into a predetermined compression conversion character string in advance in the directory name, and the conversion unit includes the search path generated by the search path generation unit. The character string of the directory name is converted using the conversion table, and the information search unit uses the search path and the search file name converted by the conversion unit to read from the information storage unit. The corresponding information file in the corresponding directory can be searched.

  In the medical information management device, an extraction unit that extracts the plurality of attributes of the image information from the information file obtained by the information search unit, and a character string that indicates the attributes extracted by the extraction unit A decoding unit that decodes the conversion character string for compression using the conversion table.

  In the medical information management apparatus, the predetermined character string of the conversion table may be an instance UID among the plurality of attributes of the image information of the medical image file.

According to the present invention, a system for managing medical image files having image information consisting of a plurality of attributes,
An information storage unit for storing an information file having a file name including the image information of the medical image file;
A conversion table for associating a plurality of attributes of the image information of the medical image file with a delimiter character and composing a character string constituting a file name that is attached to each other in a predetermined order and associated with a conversion character string for compression;
A compression unit that converts the character string constituting the file name of the information file using the conversion table, and compresses the file name of the information file;
Classifying the information file with the file name compressed by the compression unit into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file; A storage unit for storing in the information storage unit;
A medical information management system characterized by comprising:

According to the present invention, a system for managing medical image files having image information consisting of a plurality of attributes,
A predetermined character string constituting a file name obtained by connecting the plurality of attributes of the image information of the medical image file with a delimiter character and connecting them in a predetermined order is converted into a predetermined compression conversion character string. The converted information file is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, and an information storage unit in which the information file is stored; A predetermined character string that constitutes a file name that is connected to each other in a predetermined order by separating the plurality of attributes of the image information of the medical image file and converted into a predetermined compressed conversion character string. In a medical information management system comprising: an image storage unit for storing image files classified into the plurality of directories;
A search key receiving unit that receives a search key used when searching the medical image file;
A search path generator for generating a search path based on the search key;
A conversion table associating the predetermined character string with the conversion character string for compression;
A file name generation unit for generating a search file name based on the search key;
A conversion unit that converts a character string of the search file name generated by the file name generation unit using the conversion table;
Using the search path and the search file name converted by the conversion unit, an information search unit for searching the corresponding information file in the corresponding directory from the information storage unit;
An extraction unit for extracting the image information indicated by the file name of the information file acquired by the information search unit;
A medical information management system characterized by comprising:

According to the present invention, a method for managing a medical image file having image information composed of a plurality of attributes,
Preparing an information storage unit for storing an information file having a file name including the image information of the medical image file;
Preparing a conversion table for associating a plurality of attributes of the image information of the medical image file with a delimiter character and concatenating the character strings constituting the file name, which are linked together in a predetermined order, with the conversion character string for compression And steps to
Converting the character string constituting the file name of the information file using the conversion table and compressing the file name of the information file;
The information file with the file name compressed in the compressing step is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file. Storing in the information storage unit;
The medical information management method characterized by including this is provided.

According to the present invention, a method for managing a medical image file having image information composed of a plurality of attributes,
A predetermined character string constituting a file name obtained by connecting the plurality of attributes of the image information of the medical image file with a delimiter character and connecting them in a predetermined order is converted into a predetermined compression conversion character string. The converted information file is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, and an information storage unit storing the information file is prepared And steps to
A predetermined character string that constitutes a file name that is connected to each other in a predetermined order by separating the plurality of attributes of the image information of the medical image file and converted into a predetermined compressed conversion character string. A medical information management method comprising the steps of:
Receiving a search key used when searching the medical image file;
Generating a search path based on the search key;
Preparing a conversion table associating the predetermined character string with the conversion character string for compression;
Generating a search file name based on the search key;
Converting the character string of the search file name generated in the step of generating the file name using the conversion table;
Using the search path and the search file name converted in the converting step, searching the corresponding information file in the corresponding directory from the information storage unit;
Extracting the image information indicated by the file name of the information file acquired in the searching step;
The medical information management method characterized by including this is provided.

According to the present invention, a program for managing a medical image file having image information consisting of a plurality of attributes,
An information storage unit for storing an information file having a file name including the image information of the medical image file;
A conversion table for associating a plurality of attributes of the image information of the medical image file with a delimiter character and composing a character string constituting a file name that is attached to each other in a predetermined order and associated with a conversion character string for compression; On a computer with
Means for converting the character string constituting the file name of the information file using the conversion table and compressing the file name of the information file;
The information file with the file name compressed by the means for compressing is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, Means for storing in the information storage unit;
A medical information management program for functioning as

According to the present invention, a program for managing a medical image file having image information consisting of a plurality of attributes,
A predetermined character string constituting a file name obtained by connecting the plurality of attributes of the image information of the medical image file with a delimiter character and connecting them in a predetermined order is converted into a predetermined compression conversion character string. The converted information file is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, and an information storage unit in which the information file is stored; A predetermined character string that constitutes a file name that is connected to each other in a predetermined order by separating the plurality of attributes of the image information of the medical image file and converted into a predetermined compressed conversion character string. The image file is classified and stored in the plurality of directories, and the predetermined character string corresponds to the compressed conversion character string And kicking the conversion table,
On a computer with
Means for receiving a search key used when searching the medical image file;
Means for generating a search path based on the search key;
Means for generating a search file name based on the search key;
Means for converting the character string of the search file name generated by the means for generating the search file name using the conversion table;
Means for searching for a corresponding information file in a corresponding directory from the information storage unit using the search path and the search file name converted by the means for converting;
Means for extracting the image information indicated by the file name of the information file acquired by the means for searching;
A medical information management program for functioning as

  It should be noted that any combination of the above-described constituent elements and a conversion of the expression of the present invention between a method, an apparatus, a system, a recording medium, a computer program, etc. are also effective as an aspect of the present invention.

  According to the present invention, there is provided a medical image processing system that can efficiently manage medical image files with a general-purpose and inexpensive apparatus configuration without any limitation of an operating system.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In all the drawings, the same reference numerals are given to the same components, and the description will be omitted as appropriate.

(First embodiment)
FIG. 1 is a configuration diagram showing a medical information management system according to an embodiment of the present invention. The medical information management system includes a first modality device 12a (shown as “CT” in the drawing) and a second modality device 12b (shown as “MR” in the drawing) that acquire medical image data (hereinafter referred to as “MR”). Each device is simply referred to as “modality device 12”, and a first recording device 100a and a second recording device 100b that record image data acquired by the modality device 12 (hereinafter, each device is simply referred to as “recording device”). 100 ”), and an information management device 200 that transfers image data from the modality device 12 to the recording device 100 and manages the image data stored in the recording device 100.

  The information management device 200 has a server function and a router function, is connected to the modality device 12 via the network 50, and performs communication based on, for example, DICOM, and transmits / receives necessary information to / from each other. Further, the information management apparatus 200 is connected to the recording apparatus 100 via a network 52 such as a LAN. Further, the information management apparatus 200 is connected to a plurality of terminals 20a and 20b (hereinafter, each apparatus is simply referred to as “terminal 20”) that browses the image data of the recording apparatus 100 via a network 54 such as a LAN. Note that the information management apparatus 200 may include a hard disk for storing image data instead of the recording apparatus 100, or may include a hard disk. The information management apparatus 200 of this embodiment is configured not to include a hard disk.

  The modality device 12 is, for example, a CT device, an MR device, and a CR device. The terminal 20 is, for example, a personal computer. The recording device 100 is a general storage device such as NAS (Network Attached Storage) or SAN (Storage Area Network), for example, and an image file transferred from the modality device 12 via the information management device 200 to a recording medium such as a hard disk. Is stored. In the present embodiment, the three networks 50, 52, and 54 are provided. However, the present invention is not limited to this. For example, all may be provided on the same network, or only the recording device 100 may be a separate network, and the modality device 12 and the terminal 20 may be the same network.

  Each component of the medical information management system according to the present embodiment includes an arbitrary computer CPU, memory, a program that realizes the components shown in the figure loaded in the memory, a storage unit such as a hard disk that stores the program, and a network connection. It is realized by an arbitrary combination of hardware and software with a focus on the user interface. It will be understood by those skilled in the art that there are various modifications in the implementation method, program, and apparatus. Each figure described below shows functional unit blocks, not hardware unit configurations.

  FIG. 2 is a diagram illustrating an example of a directory structure of the recording apparatus 100 according to the present embodiment. The recording apparatus 100 according to the present embodiment includes a management information directory 110 (shown as “Info” in the figure) and a patient ID directory 120 (shown as “PIF” in the figure) immediately below the root directory (shown as “Root” in the figure). , Patient name directory 130 (shown as “PNF” in the figure), receipt number directory 150 (shown as “ACF” in the figure), and examination date directory 160 (shown as “DTF” in the figure). ), A series management information directory 170 (shown as “SIF” in the figure), and an image management directory 180 (shown as “Images” in the figure). In addition, in this embodiment, although it is set as the structure which has a some directory directly under a root directory, it is not limited to this.

  The management information directory 110 is a directory for storing information for storage management of the recording apparatus 100. For example, a system version information file, a storage management setting file, a log file such as error information, a storage use start date / time file, and a last access Stores date and time files.

  The patient ID directory 120 is a directory for storing information used for a search using the patient ID as a search key. The patient name directory 130 is a directory for storing information used for a search using the patient name as a search key. The reception number directory 150 is a directory for storing information used for search using the inspection reception number as a search key. The inspection date directory 160 is a directory for storing information used for search using the inspection date as a search key. The series management information directory 170 is a directory for storing information used for search using the inspection instance UID as a search key. The image management directory 180 stores image files 370 of examinations classified for each series instance UID. Details of each directory and file will be described later.

  FIG. 3 is a functional block diagram of the information management apparatus 200 of this embodiment. The information management apparatus (information management apparatus 200) of this embodiment is an apparatus that manages a medical image file having image information including a plurality of attributes, and an information file having a file name including the image information of the medical image file. For compressing a character string constituting a file name in which an information storage unit (recording device 100) to be stored and a plurality of attributes of image information of a medical image file are separated by a delimiter and connected to each other in a predetermined order A compression unit (compression unit 282) that converts a conversion table (conversion table 280) associated with the conversion character string and a character string constituting the file name of the information file using the conversion table, and compresses the file name of the information file. And the information file with the file name compressed by the compression unit includes at least some of the plurality of attributes of the image information of the medical image file Provided are classified into a plurality of directories with directory names, respectively, storage unit for storing in the information storage unit (information file storage section 243), the.

  In the present embodiment, the information management apparatus 200 transfers image data received from the modality apparatus 12 (see FIG. 1) via the network 50 to the recording apparatus 100 via the network 52, stores the image data in a predetermined directory, and stores the image data. Manage data.

  Specifically, the information management apparatus 200 includes an image file receiving unit 231, an image information acquiring unit 233, an information input receiving unit 235, a transfer destination receiving unit 236, a file generating unit 237, and an information storage path generating unit. 239, an image file storage unit 241, an information file storage unit 243, a conversion table 280, and a compression unit 282.

  The image file receiving unit 231 receives image data from the modality device 12 via the network 50. The image information acquisition unit 233 reads out and acquires information included in the image data received by the image file reception unit 231. For example, when information such as a patient ID and a patient name is recorded in an image, the information can be read and character information is obtained by identifying characters with an OCR (optical character reader) or the like. Or you may acquire information directly from the information input reception part mentioned later.

  The information input accepting unit 235 accepts input of image data information received by the image file receiving unit 231. Here, the image data information includes, for example, a patient ID, a patient name, an examination date, and the like. The transfer destination receiving unit 236 receives a selection as to which recording device 100 on the network 52 the image data received by the image file receiving unit 231 is transferred to. The information and the transfer destination received by the information input receiving unit 235 and the transfer destination receiving unit 236 are input and selected by the user via an operation unit (not shown). The information and the transmission destination received by the information input reception unit 235 and the transfer destination reception unit 236 are transferred to the image information acquisition unit 233.

  The file generation unit 237 generates an information storage file and a storage image file having a file name including the image information acquired by the image information acquisition unit 233. Details of each file and file name generated here will be described later.

  The information storage path generation unit 239 generates an information storage path based on the image information acquired by the image information acquisition unit 233. The path generated here is a path to a directory storing information files such as a patient route information file, an examination route information file, a series information file, and an image file, which will be described later. The information storage path generation unit 239 determines whether or not the directory indicated by the information storage path exists. If the directory does not exist, the information storage path generation unit 239 generates the corresponding directory. The conversion table 280 is a conversion table for associating the character strings constituting the file names and directory names of the files and paths generated by the file generation unit 237 and the information storage path generation unit 239 with the compression conversion character strings. Details of the conversion table 280 will be described later. The compression unit 282 converts the file generated by the file generation unit 237 and the information storage path generation unit 239, the file name of the path, and the character string of the directory name using the conversion table 280, and compresses the file.

  The image file storage unit 241 transfers the storage image file having the file name generated by the file generation unit 237 to the transfer destination received by the transfer destination reception unit 236 in the directory of the path generated by the information storage path generation unit 239. Are stored in the recording device 100.

  The information file storage unit 243 records the transfer destination received by the transfer destination reception unit 236 for each information file having the file name generated by the file generation unit 237 in the directory of the path generated by the information storage path generation unit 239. Store in device 100.

  Next, details of each directory and file of the recording apparatus 100 will be described below with reference to the drawings.

  FIG. 4 is a diagram showing an example of the directory structure of the patient ID directory 120 of FIG. The patient ID directory 120 includes a plurality of patient ID first n character directories 121a, 121b, and 121c (hereinafter referred to as individual directories), with the first n characters (in the figure, the first two characters) of the patient ID as subdirectory names. Simply called “patient ID first n character directory 121”), and two directories below it, PL directories 123a, 123b, and 123c (hereinafter, each directory is simply called “PL directory 123”) and an SL directory. 125a, 125b, and 125c (hereinafter, each directory is simply referred to as “SL directory 125”).

  Each patient ID first n character directory 121 has a name composed of alphabets A to Z, 0 to 9, and symbols, for example. Each directory name is actually represented by an underscore preceding these alphanumeric characters. The symbol is expressed by converting it to a 2-byte character code. These are measures for making symbol characters that cannot be used as file names or directory names, such as “?” Or “:”, represented by 2 bytes and usable. Thereafter, even if not specifically described, it is assumed that the file name and directory name including the patient name, patient ID, examination ID, modality name, and the like are similarly subjected to double-byte character conversion processing.

  In the PL directory 123 and the SL directory 125, a plurality of patient route information files 300 and a plurality of examination route information files 320 of the patient corresponding to the patient ID (patient ID first n characters) are stored.

  FIG. 5 is a diagram showing an example of the detailed structure of the patient route information file 300 and the examination route information file 320 stored under the patient ID directory 120 of FIG.

  In this embodiment, the patient route information file 300 and the examination route information file 320 are empty files having only file names, do not include actual image data, and have a data size of substantially 0 bytes. However, if necessary, information such as comments and history may be stored in the file.

The patient route information file 300 is, for example, a character string in which a patient ID 301, a patient name 303, a gender 305, and a date of birth 307 are concatenated in order by separating them with a delimiter character 302 “@ (at sign)”. Has a file name to be represented. As described above, the patient ID 301 and the patient name 303 use character strings expressed by performing a 2-byte character conversion process. The extension 309 of the patient route information file 300 is “PI”. As an example, the file name of the patient route information file 300 is shown as follows.
"_0_0_3_0_0_7 --_ 3 @ _Y_A_M_A_D_A_T_A_R_O @ M @ 19800101.PI"

  In this embodiment, “@ (at mark)” is used as the delimiter 302, but the present invention is not limited to this. For example, “| (pipe)”, “^ (hat)”, etc. can be used in a 1-byte code system.

The examination route information file 320 includes, for example, a patient ID 321, a patient name 323, a gender 325, a birth date 327, an age 329, an examination date 331, an examination time 333, an acceptance number 335, and an examination ID 337. , And the test instance UID 339 have a file name represented by a character string concatenated in order by separating them with a delimiter character “@”. Again, the patient ID 301, the patient name 303, and the examination ID 337 use character strings that are expressed by performing the above-described two-byte character conversion process. The extension 341 of the inspection route information file 320 is “PSI”. As an example, the file name of the inspection route information file 320 is shown as follows.
"_0_1_7_1_6_2 --_ 1 @ _S_A_T_O_U_H_A_N_A_K_O @ F @@ 078Y @ 20020214 @ 144935 @@ _ 4_4_2_1@1.2.392.200036.
9116.2.2.2.1762575864.1013665775.38601.PSI ''

  In this embodiment, as will be described later, compression conversion processing is performed on the character string portion of the inspection instance UID 339 among the attributes of the image information included in the file name of the inspection route information file 320. The above example is the file name before compression conversion processing of the character string portion of the inspection instance UID 339.

  FIG. 6 is a diagram showing an example of the directory structure of the patient name directory 130 of FIG. The patient name directory 130 is a directory for storing information used for a search using the patient name as a search key. Here, in the patient name directory 130, the patient name is a single-byte character. The patient name directory 130 includes a plurality of patient name first n-character directories 131a and 131b (hereinafter, each directory is simply referred to as “patient name first n-character directory 131”), and two directories further below it, a PL directory 133a. 133b (hereinafter each directory is simply referred to as “PL directory 133”) and SL directories 135a and 135b (hereinafter each directory is simply referred to as “SL directory 135”).

  Each patient name first n-character directory 131 has a name composed of, for example, alphabets A to Z, 0 to 9, and symbols, similarly to the patient ID first n-character directory 121. In the PL directory 133 and the SL directory 135, a plurality of patient route information files 300 and a plurality of examination route information files 320 of a plurality of patients corresponding to patient names (first n characters of patient names) are stored, respectively.

  FIG. 7 is a diagram showing an example of the directory structure of the receipt number directory 150 of FIG. The reception number directory 150 is a directory for storing information used for a search using the reception number as a search key. The reception number directory 150 includes a plurality of reception number first n-character directories 151a and 151b (hereinafter, each directory is simply referred to as “reception number first n-character directory 151”), and two directories further below it, a PL directory 153a. 153b (hereinafter each directory is simply referred to as “PL directory 153”) and SL directories 155a and 155b (hereinafter each directory is simply referred to as “SL directory 155”).

  Each reception number first n-character directory 151 has a name composed of alphabets A to Z, 0 to 9, and symbols, for example, similarly to the patient ID first n-character directory 121. In the PL directory 153 and the SL directory 155, a plurality of patient route information files 300 and a plurality of examination route information files 320 corresponding to the reception number (first n characters of the reception number) are stored, respectively.

  FIG. 8 is a diagram showing an example of the directory structure of the examination date directory 160 of FIG. The inspection date directory 160 is a directory for storing information used for search using the inspection date as a search key. The inspection date directory 160 includes a plurality of inspection date-specific directories 161a and 161b (hereinafter, each directory is simply referred to as “examination date-specific directory 161”), and two directories below it, PL directories 163a and 163b (hereinafter, referred to as “inspection date directories”). , Each directory is simply referred to as “PL directory 163”) and SL directories 165a and 165b (hereinafter, each directory is simply referred to as “SL directory 165”).

  Each inspection date directory 161 has a name indicated by “YYYYMMDD”, for example, when the inspection date is YYYY year MM month DD date. In the PL directory 163 and the SL directory 165, a patient route information file 300 and an examination route information file 320 corresponding to the examination date are stored, respectively.

  FIG. 9 is a diagram showing an example of the directory structure of the series management information directory 170 of FIG. The series management information directory 170 is a directory for storing information used for search using the inspection instance UID as a search key. The series management information directory 170 stores a plurality of inspection instance UID (1) directories 171a and inspection instance UID (n) directories 171b (hereinafter, each directory is simply referred to as “inspection instance UID directory 171”).

  The inspection instance UID directory 171 is a directory having the inspection instance UID as a folder name, but may be stored as a subdirectory of an upper directory having the inspection instance code as a folder name. Here, the inspection instance code can be defined as the last four digits obtained by adding the constituent elements of the inspection instance UID, that is, the numerical values separated by dots. In this embodiment, as will be described later, compression conversion processing is performed on the description of the inspection instance UID of the folder name in the inspection instance UID directory 171.

  Each inspection instance UID directory 171 stores a plurality of inspection series information files 350 corresponding to the inspection instance UID. In addition, a deletion lock folder 360 for prohibiting deletion of information in the inspection instance UID directory 171 can be stored. If it is desired to prohibit the deletion of information in the inspection instance UID directory 171, the deletion lock folder 360 is arranged in the corresponding inspection instance UID directory 171.

The series information file 350 includes a modality 351, an acquired AE name 353, a series instance UID 355, in addition to a patient ID, patient name, sex, date of birth, age, examination date, examination time, reception number, and examination ID. The file number is expressed by a character string in which the series number 357 is concatenated in order by being separated by the delimiter character 302 “@”. Here, as described above, the patient ID, the patient name, the examination ID, and the modality 351 use a character string expressed by performing a 2-byte character conversion process. The extension 359 of the series information file 350 is “SI”. In this embodiment, the series information file 350 is an empty file having only a file name, does not include actual image data, and has a data size of substantially 0 bytes. However, if necessary, information such as comments and history may be stored in the file. As an example, the file name of the series information file 350 is shown as follows.
"_5_3_1_6_0_8 --_ 1 @ ~ (omitted) ~ @ CT @ _P_O_P --_ N_e_t_S_e_r_v_e_r@1.2.392.200036.9116.
2.2.2.1762575864.1014268358.438705@2.SI ''

  In this embodiment, as will be described later, compression conversion processing is performed on the character string portion of the series instance UID 355 among the attributes of the image information included in the file name of the series information file 350. The above example is the file name before compression conversion processing of the character string portion of the series instance UID 355.

  FIG. 10 is a diagram showing an example of the directory structure of the image management directory 180 of FIG. The image management directory 180 stores image files 370 of examinations classified for each series instance UID. The image management directory 180 includes a plurality of series instance UID (1) directories 181a and series instance UID (n) directories 181b (hereinafter, each directory is simply referred to as “series instance UID directory 181”).

  The series instance UID directory 181 has a name corresponding to the series instance UID. The series instance UID directory 181 can also be stored as a subdirectory of a higher-level directory having a series instance code as a folder name. Here, the series instance code can be defined as the last four digits obtained by adding the constituent elements of the series instance UID, that is, the numerical values separated by dots. In this embodiment, as will be described later, compression conversion processing is performed on the description of the series instance UID of the folder name in the series instance UID directory 181.

  The plurality of image files 370 stored in the series instance UID directory 181 are represented by, for example, a character string in which an image number 371 of an image and an SOP instance 373 are separated by a delimiter 302 “@” and sequentially connected. Has a file name. The extension 375 of the image number 371 is “DCM”. The image file 370 contains actual image data. The image file 370 can also include attributes such as cluster instance and transfer syntax in the file name. In this embodiment, as will be described later, compression conversion processing is performed on the description of the SOP instance 373 of the image file 370.

  Further, each series instance UID directory 181 includes a test instance UID directory 183 corresponding to a plurality of test instance UIDs of a test having a series instance UID. The test instance UID directory 183 includes a plurality of corresponding series information files 350. Stored. As a result, the inspection instance UID can be reversed from the series instance UID, and the corresponding series information file 350 can be acquired. This makes it possible to acquire information at a higher speed. This inspection instance UID directory 183 is similar to the above-described inspection instance UID directory 171, and compression conversion processing is performed on the description of the inspection instance UID of the folder name in the inspection instance UID directory 183.

  Next, details of the conversion table 280 of FIG. 3 will be described below with reference to the drawings. FIG. 11 is a diagram illustrating an example of the structure of the conversion table 280. As shown in FIG. 11, the conversion table 280 stores an instance UID 294, a character 290 of a conversion character string for compression of the instance UID 294, and a hexadecimal code 292 of its ASCII character code in association with each other. In FIG. 11, for the sake of explanation, the conversion table 280 includes a character 290, but only the hexadecimal code 292 may be used.

  In the information management apparatus 200 of this embodiment, each instance UID is compression-converted using the conversion table 280 of FIG. The characters 290 converted by the conversion table 280 include only characters that can be used as file names and directory names by the operating system. In the present embodiment, the specific instance UID whose first character string is shown in FIG. 11A is converted so as to be expressed by 1 byte of “0x2n” (hereinafter, n is 1 to F) of the hexadecimal code 292. The

  The specific instance UID shown in FIG. 11A includes, for example, a code defined in the DICOM standard. For example, “1.2.” Is a code for identifying the ISO and the member institution (ANSI). The three-digit code following “1.2.” Is a code for identifying the country code of the member institution (ANSI). For example, “1.2.392.” Is a code for identifying Japan in ISO and ANSI. Further, the multi-digit code following “1.2.392.” Is, for example, a code for identifying a specific organization, and here is a code provided by ANSI.

  The codes included in these instance UIDs are fixed codes to some extent by the modality device 12 or the like, and are often the same codes when managed by the information management device 200. Therefore, here, conversion character codes are prepared in advance for these specific instance UIDs that are frequently used. Thereby, the instance UID can be efficiently compressed at a high compression rate.

  An instance UID of two characters “number + dot (.)” Shown in FIG. 11B as the first character string is converted so as to be expressed by 1 byte of “0x3n” of the hexadecimal code 292. An instance UID of two characters “dot (.) + Number” whose leading character string is shown in FIG. 11C is converted so as to be expressed by 1 byte of “0x4n” of the hexadecimal code 292. The instance UID whose number is one character in the first character string shown in FIG. 11D is converted so as to be represented by 1 byte of “0x5n” of the hexadecimal code 292. The instance UID having the three-character number shown in FIG. 11E as the first character string is converted so as to be expressed by 2 bytes of “0x6n” + “0x3n to 7n” of the hexadecimal code 292. The instance UID having the two-character number shown in FIG. 11F as the first character string is converted so as to be represented by 2 bytes of “0x7n” + “0x3n” of the hexadecimal code 292.

  As described above, the example of the conversion table 280 has been described with reference to FIG. 11, but the present invention is not limited to this, and it is understood by those skilled in the art that various modifications are possible.

  The operation of the information management apparatus 200 configured as described above will be described below. FIG. 12 is a flowchart showing an example of the operation of the information management apparatus 200 of this embodiment.

  First, the image file receiving unit 231 receives image data from the modality device 12 via the network 50 (step S201). Subsequently, the information input receiving unit 235 receives the input of the image data information received in step S201 (step S203). Further, the transfer destination receiving unit 236 receives selection of the transfer destination of the image data received in step S201 (step S205).

  Subsequently, the image information acquisition unit 233 acquires the image information received by the information input reception unit 235 (step S207). Alternatively, the image information acquisition unit 233 acquires image information from the image data received by the image file reception unit 231 in step S201.

  Subsequently, the file generation unit 237 generates an information storage file name based on the image information acquired in step S207 (step S209). Subsequently, the information storage path generation unit 239 generates an information storage path based on the image information acquired in step S207 (step S211). In step S209 and step S211, the instance UID included in the file name and path is compressed as will be described later.

  Subsequently, in the transfer destination recording apparatus 100 received in step S205, the image file is stored with the file name generated in step S209 added to the directory of the path generated in step S211 by the image file storage unit 241. (Step S213). The information file storage unit 243 adds each information file to the directory indicated by the path generated by the image file storage unit 241 in step S211 with the file name generated in step S209, and records the transfer destination received in step S205. The data is stored in the device 100 (step S215).

  Hereinafter, details of the processing of the file generation unit 237 and the information storage path generation unit 239 in step S209 and step S211 will be described. First, in step S209, the file generation unit 237 generates file names of the patient route information file 300, the examination route information file 320, the series information file 350, and the image file 370 based on the acquired image information. For example, as shown in FIG. 5, the patient route information file 300 has an extension 309 to a character string obtained by concatenating a patient ID 301, a patient name 303, a sex 305, and a date of birth 307 separated by a delimiter 302 “@”. The file name with “PI” is generated by the file generation unit 237. Since the compression target instance UID is not included in the file name of the patient route information file 300, the compression process of the file name by the compression unit 282 is not performed, and the patient route information file 300 is generated as an empty file with the generated file name as it is. Is generated.

  The inspection route information file 320, the series information file 350, and the image file 370 are subjected to the following file name compression processing for the instance UID included in the file name of each file. Here, the image file 370 will be described as an example.

  The file generation unit 237 generates a file name in which “DCM” of the extension 375 is added to a character string obtained by connecting the image number 371 and the SOP instance 373 by separating them with the delimiter 302 “@”. Here, the compression unit 282 performs a compression process on the SOP instance 373. For example, when the SOP instance 373 as shown in FIG. 13 is converted, the notation that was 32 characters (32 bytes) before the conversion is compressed and converted to the notation of 17 characters (17 bytes) after the conversion.

  The image file 370 is generated by attaching the file name compressed and converted by the compression unit 282 to the image data received by the image file receiving unit 231.

  In step S211, the information storage path generation unit 239 generates a path indicating the storage destination directory of the recording apparatus 100 that is the transfer destination of each information file and image file generated by the file generation unit 237. For example, the patient route information file 300 includes a plurality of directories, such as the patient ID directory 120, the first patient name directory 130, the second patient name directory 140, the reception number directory 150, and the examination date directory 160. Patient ID first n character directory 121, patient name first n character directory 131, receipt number first n character directory 151, and PL directory 123, PL directory 133, PL directory 153, and PL under the examination date directory 161 Stored in the directory 163. Therefore, for example, when the patient route information file 300 is stored in the patient ID directory 120, a path of “/ root / PIF / patient ID first n characters / PL /” is generated. Similarly, a path to a storage destination directory is generated for each information file and image file.

  In this embodiment, in step S211, when the instance UID is included in the directory name included in the path generated by the information storage path generation unit 239, the instance UID is converted using the conversion table 280, and compression processing is performed. Is done. That is, when the generated path includes the inspection instance UID directory 171, the series instance UID directory 181, the inspection instance UID directory 183, etc., the information storage path generation unit 239 determines the instance UID included in these directory names. Perform compression conversion processing.

  As described above, according to the information management apparatus 200 of the present embodiment, file names and directory names can be compressed. For example, even in an operating system in which the file name or directory name has a limited number of characters, It becomes possible to apply. Furthermore, file search efficiency can be improved by compressing file names and directory names.

(Second embodiment)
FIG. 14 is a functional block diagram showing the configuration of the information management apparatus of this embodiment. The information management apparatus (information management apparatus 200) of this embodiment is an apparatus that manages a medical image file having image information composed of a plurality of attributes, and delimits the plurality of attributes of the image information of the medical image file with a delimiter character. An information file obtained by previously converting a predetermined character string forming a file name concatenated in a predetermined order into a predetermined compression conversion character string is at least one of the plurality of attributes of the image information of the medical image file. The information is classified into a plurality of directories each having a directory name including a part, and the information storage unit (recording apparatus 100) in which the information file is stored and the plurality of attributes of the image information of the medical image file are separated and determined in advance. A storage image file obtained by previously converting a predetermined character string that constitutes a file name concatenated with each other in order into a predetermined conversion character string for compression, A search key receiving unit (search for receiving a search key used when searching for a medical image file in a medical information management device including an image storage unit (recording device 100) that is classified and stored in a number of directories A key reception unit 201), a search path generation unit (search path generation unit 207) that generates a search path based on the search key, and a conversion table (conversion) that associates a predetermined character string with a conversion character string for compression. Table 280), a file name generation unit (search file name generation unit 209) that generates a search file name based on the search key, and a character string of the search file name generated by the file name generation unit is converted Using the conversion unit (conversion unit 380) for conversion using the table, the search path and the search file name converted by the conversion unit, the corresponding data is stored from the information storage unit. An information search unit (file search unit 211) for searching for a corresponding information file in the directory; and an extraction unit (information extraction unit 215) for extracting image information indicated by the file name of the information file acquired by the information search unit. .

  Specifically, the information management apparatus 200 includes a search key reception unit 201, a type reception unit 202, a determination unit 203, a table storage unit 205, a search path generation unit 207, and a search file name generation unit 209. A file search unit 211, a list management unit 213, an information extraction unit 215, a transmission unit 217, an image file acquisition unit 219, a conversion table 280, a conversion unit 380, and a decoding unit 382. Since the conversion table 280 can be the same as that in the above embodiment, the same reference numerals are given and detailed description is omitted.

  The search key receiving unit 201 receives input of information serving as a search key when searching for image data to be browsed. For example, the search key includes a patient ID, an examination instance UID, a series instance UID, and an examination date. Here, a search key input from the terminal 20 via the network 54 is accepted. Specifically, since the terminal 20 inquires in a format according to the DICOM standard, information serving as a search key is extracted from the inquiry information and accepted as a search key.

  The type receiving unit 202 receives the type of information to be acquired, which is designated from the terminal 20 via the network 54. For example, the type of information is any of patient information, examination information, series information, and an image file.

  The determination unit 203 determines the attribute of the search key received by the search key reception unit 201 and determines a file to be searched according to the type of information received by the type reception unit 202. For example, when acquisition of patient information is accepted, the search file is the patient route information file 300. When the acquisition of the inspection information is accepted, the search file becomes the inspection route information file 320. When the acquisition of series information is accepted, the search file becomes the series information file 350. When the acquisition of the image file is accepted, the search file is the image file 370. In the following description, the information management apparatus 200 is determined to perform processing for each information or image file based on the type of information received by the type receiving unit 202, and to perform each operation. To do.

  The table storage unit 205 stores a table having a path structure associated with the search key attribute for each type of information. FIG. 15A is a diagram illustrating an example of the structure of a patient route search table 221 used when acquiring patient information. The patient route search table 221 stores path generation information when a patient ID, a patient name (full-width characters), and a patient name (half-width characters) are accepted as search keys. For example, the path when the patient ID is accepted as a search key is “/ root / PIF / first n characters of patient ID / PL”.

  FIG. 15B is a diagram illustrating an example of the structure of the inspection route search table 223 used when acquiring inspection information. The examination route search table 223 stores path generation information when a patient ID, a patient name (full-width characters), a patient name (half-width characters), an examination date, and an acceptance number are accepted as retrieval keys. For example, the path when the examination date is accepted as a search key is “/ root / DTF / YYYYMMDD / SL”.

  FIG. 15C is a diagram showing an example of the structure of the series information search table 225 used when acquiring series information. The series information search table 225 stores path generation information when an inspection instance UID is received as a search key. A path generated by receiving the inspection instance UID as a search key is “/ root / SIF / inspection instance UID”.

  FIG. 15D is a diagram showing an example of the structure of the image information search table 227 used when acquiring image information. The image information search table 227 stores path generation information when a series instance UID and an inspection instance UID are received as search keys. A path generated by receiving the series instance UID and the inspection instance UID as a search key is “/ root / Images / series instance UID /”.

  FIG. 15E is a diagram illustrating an example of the structure of the image file search table 229 used when acquiring an image file. The image file search table 229 stores path generation information when a series instance UID is received as a search key. For example, the path when a series instance UID is accepted as a search key is “/ root / Images / series instance UID”.

  Returning to FIG. 14, the search path generation unit 207 accesses the table storage unit 205, refers to the table corresponding to the type of information determined by the determination unit 203, acquires the structure of the generated path, and searches for the path. Is generated. When the type of information is patient information, examination information, series information, image information, and image file, the patient route search table 221, examination route search table 223, series information search table 225, and image information search in the table storage unit 205, respectively. The table 227 and the image file search table 229 are referred to. Of the generated paths, a path including the instance UID is once transferred to the conversion unit 380 described later and subjected to conversion processing.

  The search file name generation unit 209 generates a search file name based on the type of information determined by the determination unit 203 and the search key received by the search key reception unit 201. When the information type is patient information, examination information, series information, image information, and an image file, the corresponding file name extensions are PI, PSI, SI, DCM, and DCM, respectively. As the search file name, a wild card is used to generate a file name including the search key received by the search key receiving unit 201. For example, when patient information is acquired using a patient ID as a search key, the search file name is “patient ID * .PI”. Of the generated file names, the file name including the instance UID is once transferred to the conversion unit 380 described later and subjected to conversion processing.

  The file search unit 211 uses the search path and search file name generated by the search path generation unit 207 and the search file name generation unit 209 to search for a corresponding file from the recording device 100. The list management unit 213 creates a list of files acquired by the file search unit 211 and transmits information based on the list.

  The information extraction unit 215 sequentially extracts necessary information from the file acquired by the file search unit 211. Here, when the acquired file includes an instance UID that has been compressed and converted, the information extraction unit 215 delivers the instance UID to a decryption unit 382 described later. Furthermore, the information extraction unit 215 converts the code into a format that conforms to the DICOM standard. The transmission unit 217 transmits the information extracted by the information extraction unit 215 to the terminal 20 (FIG. 1) via the network 54.

  The conversion unit 380 converts the instance UID in the character string of the search file name generated by the search file name generation unit 209 using the conversion table 280 and transfers the converted instance UID to the search file name generation unit 209. Further, the conversion unit 380 converts the instance UID in the character string of the directory name of the search path generated by the search path generation unit 207 using the conversion table 280 and passes it to the search path generation unit 207. . The decryption unit 382 decrypts the instance UID passed from the information extraction unit 215 using the conversion table 280 and returns it to the information extraction unit 215.

  The operation of the information management apparatus 200 configured as described above will be described below.

  FIG. 16 is a flowchart illustrating an example of an operation when acquiring examination information from a patient ID in the information management apparatus 200 of the present embodiment. First, the search key receiving unit 201 receives a patient ID input from the terminal 20 via the network 54 as a search key (step S101). The patient ID accepted here is the first n characters of the patient ID. Here, it is assumed that the determination unit 203 is operating in advance to determine that the inspection information is acquired and perform this processing.

  Subsequently, the search path generation unit 207 accesses the table storage unit 205, refers to the inspection route search table 223, and generates a search path (step S103). The path generated here is "/ root / PIF / patient ID first n characters / SL /".

  Subsequently, the search file name generation unit 209 generates a PSI file name (step S105). The file name generated here is “patient ID * .PSI”. Subsequently, the file search unit 211 uses the search path and search file name generated in steps S103 and S105 to search for and acquire the corresponding file from the recording device 100 (step S107). Further, the file search unit 211 creates a list of acquired files.

  The list management unit 213 refers to the list created in step S107 to determine whether there is an acquired file. If there is no file (NO in step S109), the list management unit 213 ends the process. When there is a file (YES in step S109), the information extraction unit 215 extracts necessary information from the file (step S111). For example, the patient ID 321 and the examination instance UID 339 are extracted from the examination route information file 320 acquired here. Then, the information extraction unit 215 passes the extracted inspection instance UID 339 to the decoding unit 382, and the decoding unit 382 decodes the inspection instance UID 339 using the conversion table 280 and returns it to the information extraction unit 215. The information extracting unit 215 converts the decrypted examination instance UID 339 and patient ID 321 into a format conforming to the DICOM standard, and passes the result to the transmitting unit 217. Then, the transmission unit 217 transmits to the terminal 20 via the network 54.

  Subsequently, the list management unit 213 deletes the file that transmitted the information from the list created in step S107 (step S113), and returns to step S109. In this manner, file information can be extracted and transmitted sequentially from the list created in step S107.

  FIG. 17 is a flowchart illustrating an example of an operation when the information management apparatus 200 according to the present embodiment acquires series information from a patient ID and an examination instance UID. First, the search key receiving unit 201 receives a patient ID and an examination instance UID input from the terminal 20 via the network 54 as a search key (step S121). Or you may receive patient ID and test | inspection instance UID which the information management apparatus 200 acquired by FIG.16 S111. Here, it is assumed that the determination unit 203 is operating in advance to determine that series information is acquired and perform this processing.

  Subsequently, the search path generation unit 207 accesses the table storage unit 205, refers to the series information search table 225, and generates a search path (step S123). The path generated here is “/ root / SIF / inspection instance UID /”. Since this path includes an instance UID, the path is temporarily transferred to the conversion unit 380, and the inspection instance UID is compressed and converted using the conversion table 280.

  Subsequently, the search file name generation unit 209 generates an SI file name (step S125). The file name generated here is “patient ID * .SI”. Hereinafter, since it operates in the same manner as Step S107 to Step S113 in FIG.

  The file search unit 211 uses the search path and search file name generated in steps S123 and S125 to search for and acquire the corresponding file from the recording device 100 (step S107). Further, the file search unit 211 creates a list of acquired files.

  The list management unit 213 refers to the list created in step S107 to determine whether there is an acquired file. If there is no file (NO in step S109), the list management unit 213 ends the process. When there is a file (YES in step S109), the information extraction unit 215 extracts necessary information from the file (step S111). For example, the series instance UID 355 is extracted from the series information file 350 acquired here and transferred to the decryption unit 382. The decryption unit 382 decrypts the series instance UID 355 using the conversion table 280 and returns it to the information extraction unit 215. The information extraction unit 215 converts the decrypted series instance UID 355 into a format according to the DICOM standard. Then, the transmission unit 217 transmits to the terminal 20 via the network 54.

  Subsequently, the list management unit 213 deletes the file that transmitted the information from the list created in step S107 (step S113), and returns to step S109. In this manner, file information can be extracted and transmitted sequentially from the list created in step S107.

  Next, a function for acquiring the image file of the corresponding examination from the patient ID will be described. FIG. 18 is a partial functional block diagram showing the information management apparatus 200 of the present embodiment. The information management device 200 includes an image file acquisition unit 219 that reads out a corresponding image file from the recording device 100 based on the information acquired by the information extraction unit 215. The image file acquired by the image file acquisition unit 219 is transmitted from the transmission unit 217 to the terminal 20 via the network 54.

  Next, a function for acquiring the image file of the corresponding examination from the patient ID will be described. FIG. 18 is a partial functional block diagram showing the information management apparatus 200 of the present embodiment. The information management device 200 includes an image file acquisition unit 219 that reads out a corresponding image file from the recording device 100 based on the information acquired by the information extraction unit 215. The image file acquired by the image file acquisition unit 219 is transmitted from the transmission unit 217 to the terminal 20 via the network 54.

  FIG. 19 and FIG. 20 are flowcharts showing an example of an operation when acquiring an image file of an examination corresponding to a certain patient ID in the information management apparatus 200 of the present embodiment. 19, step S101 to step S105 are the same as step S101 to step S105 in FIG. 16, and step S123 and step S125 are the same as step S123 and step S125 in FIG. It is attached.

  First, the search key receiving unit 201 receives a patient ID input from the terminal 20 via the network 54 as a search key (step S101). Here, it is assumed that the determination unit 203 operates in advance to determine that an image file is acquired and perform this processing.

  Subsequently, the search path generation unit 207 accesses the table storage unit 205, refers to the inspection route search table 223, and generates a search path (step S103). The path generated here is "/ root / PIF / patient ID first n characters / SL /".

  Subsequently, the search file name generation unit 209 generates a PSI file name (step S105). Subsequently, the file search unit 211 searches and acquires the corresponding file from the recording apparatus 100 using the search path and the search file name generated in steps S103 and S105. The file search unit 211 creates a check list for the acquired file (step S141).

  The list management unit 213 refers to the examination list created in step S141, determines whether there is an acquired file, and ends the process if there is no file (NO in step S143). If there is a file (YES in step S143), the information extraction unit 215 extracts the inspection instance UID 339 from the corresponding file, and the list management unit 213 deletes the corresponding file from the inspection list (step S145).

  Subsequently, the search path generation unit 207 accesses the table storage unit 205, refers to the series information search table 225, and generates a search path (step S123). The path generated here is “/ root / SIF / inspection instance UID /”. Since this path includes an instance UID, the path is temporarily transferred to the conversion unit 380, and the inspection instance UID is compressed and converted using the conversion table 280. Subsequently, the search file name generation unit 209 generates an SI file name (step S125).

  Subsequently, the file search unit 211 uses the search path and search file name generated in steps S123 and S125 to search for and acquire the corresponding file from the recording device 100 (step S151). Further, the file search unit 211 creates a series list of the acquired files.

  The list management unit 213 refers to the series list created in step S151 and determines whether there is an acquired file. If there is no file (NO in step S153), the list management unit 213 returns to step S143. If there is a file (YES in step S153), the information extraction unit 215 extracts the series instance UID 355 from the corresponding file, and the list management unit 213 deletes the corresponding file from the series list (step S155).

  Subsequently, as shown in FIG. 20, the search path generation unit 207 accesses the table storage unit 205, refers to the image information search table 227, and generates a search path (step S133). The path generated here is “/ root / Images / series instance UID /”. Since the instance UID is included in this path, it is once transferred to the conversion unit 380, and the series instance UID is compressed and converted using the conversion table 280.

  Subsequently, the search file name generation unit 209 generates a DCM file name (step S135). The file name generated here is “* .DCM”. Then, the file search unit 211 searches for and acquires the corresponding file from the recording apparatus 100 using the search path and the search file name generated in steps S133 and S135. The file search unit 211 creates an image list of the acquired file (step S161).

  The list management unit 213 refers to the image list created in step S161 to determine whether there is an acquired file. If there is no file (NO in step S163), the list management unit 213 returns to step S153 in FIG. . If there is a file (YES in step S163), the transmission unit 217 transmits the corresponding file (step S165). The list management unit 213 deletes the corresponding file from the image list (step S167) and returns to step S163.

  As described above, in the medical information management system of the present embodiment, for example, an image file can be acquired using a patient ID as a search key. In the above processing, the instance UID included in the directory name and the file name is searched in a compressed format, so that the search efficiency is improved.

  As mentioned above, although embodiment of this invention was described with reference to drawings, these are the illustrations of this invention, Various structures other than the above are also employable.

It is a lineblock diagram showing the medical information management system concerning an embodiment of the invention. It is a figure which shows an example of the directory structure of the recording device of this embodiment. It is a functional block diagram of the information management device of this embodiment. It is a figure which shows an example of the directory structure of the patient ID directory of FIG. It is a figure which shows an example of the detailed structure of the patient route information file and examination route information file which are stored under the patient ID directory of FIG. It is a figure which shows an example of the directory structure of the patient name directory of FIG. It is a figure which shows an example of the directory structure of the receipt number directory of FIG. It is a figure which shows an example of the directory structure of the inspection date directory of FIG. It is a figure which shows an example of the series management information directory directory structure of FIG. It is a figure which shows an example of the image management directory directory structure of FIG. It is a figure which shows an example of the structure of the conversion table of FIG. It is a flowchart which shows an example of operation | movement of the information management apparatus of this embodiment. It is a figure for demonstrating compression of the instance UID in the information management apparatus of this embodiment. It is a functional block diagram which shows the structure of the information management apparatus of this embodiment. It is a figure which shows an example of the structure of each table memorize | stored in the table memory | storage part of FIG. In the information management device of this embodiment, it is a flow chart which shows an example of operation in case examination information is acquired from patient ID. It is a flowchart which shows an example of operation | movement in the case of acquiring series information from patient ID and test | inspection instance UID in the information management apparatus of this Embodiment. It is a partial functional block diagram which shows the information management apparatus of this embodiment. It is a flowchart which shows an example of operation | movement in the case of acquiring the image file of the test | inspection applicable to a certain patient ID in the information management apparatus of this Embodiment. 20 is a flowchart illustrating an example of a continuation of FIG. 19.

Explanation of symbols

12 Modality device 20 Terminal 50, 52, 54 Network 100 Recording device 110 Management information directory 120 Patient ID directory 121 Patient ID first n character directory 123 PL directory 130 Patient name directory 131 Patient name first n character directory 133 PL directory 150 Accession number directory 151 Reception number first n character directory 153 PL directory 160 Inspection date directory 161 Inspection date directory 163 PL directory 170 Series management information directory 171 Inspection instance UID directory 180 Image management directory 181 Series instance UID directory 183 Inspection instance UID directory 200 Information management device 201 Search key Attachment unit 202 Type reception unit 203 Discrimination unit 205 Table storage unit 207 Search path generation unit 209 Search file name generation unit 211 File search unit 213 List management unit 215 Information extraction unit 217 Transmission unit 219 Image file acquisition unit 221 Patient route search Table 223 Inspection route search table 225 Series information search table 227 Image information search table 229 Image file search table 231 Image file reception unit 233 Image information acquisition unit 235 Information input reception unit 236 Transfer destination reception unit 237 File generation unit 239 Information storage path Generation unit 241 Image file storage unit 243 Storage unit 243 Information file storage unit 280 Conversion table 282 Compression unit 290 Character 292 Hexadecimal code 294 Instance UID
300 Patient route information file 320 Examination route information file 350 Series information file 360 Delete lock folder 370 Image file 380 Conversion unit 382 Decoding unit

Claims (14)

A device for managing medical image files having image information consisting of a plurality of attributes,
An information storage unit for storing an information file having a file name including the image information of the medical image file;
A conversion table for associating a plurality of attributes of the image information of the medical image file with a delimiter character and composing a character string constituting a file name that is attached to each other in a predetermined order and associated with a conversion character string for compression;
A compression unit that converts the character string constituting the file name of the information file using the conversion table, and compresses the file name of the information file;
Classifying the information file with the file name compressed by the compression unit into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file; A storage unit for storing in the information storage unit;
A medical information management device comprising: The medical information management device according to claim 1,
An image storage unit for storing a storage image file having a file name including the image information of the medical image file;
The compression unit converts the character string of the file name of the storage image file using the conversion table, and compresses the file name of the storage image file,
The storage unit includes a plurality of directory names each including at least a part of the plurality of attributes of the image information of the medical image file, the storage image file having the file name compressed by the compression unit. A medical information management apparatus that is classified into a directory and stored in the image storage unit. In the medical information management device according to claim 1 or 2,
The said compression part converts the character string which comprises the said directory name using the said conversion table, The medical information management apparatus characterized by the above-mentioned. The medical information management apparatus according to any one of claims 1 to 3,
The medical information management apparatus, wherein the character string converted by the compression unit using the conversion table is an instance UID among the plurality of attributes of the image information of the medical image file. A device for managing medical image files having image information consisting of a plurality of attributes,
A predetermined character string constituting a file name obtained by connecting the plurality of attributes of the image information of the medical image file with a delimiter character and connecting them in a predetermined order is converted into a predetermined compression conversion character string. The converted information file is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, and an information storage unit in which the information file is stored; A predetermined character string that constitutes a file name that is connected to each other in a predetermined order by separating the plurality of attributes of the image information of the medical image file and converted into a predetermined compressed conversion character string. In a medical information management device comprising: an image storage unit that stores image files for classification and storage in the plurality of directories,
A search key receiving unit that receives a search key used when searching the medical image file;
A search path generator for generating a search path based on the search key;
A conversion table associating the predetermined character string with the conversion character string for compression;
A file name generation unit for generating a search file name based on the search key;
A conversion unit that converts a character string of the search file name generated by the file name generation unit using the conversion table;
Using the search path and the search file name converted by the conversion unit, an information search unit for searching the corresponding information file in the corresponding directory from the information storage unit;
An extraction unit for extracting the image information indicated by the file name of the information file acquired by the information search unit;
A medical information management device comprising: In the medical information management device according to claim 5,
In the directory name, a predetermined character string is previously converted into a predetermined compression conversion character string,
The conversion unit converts the character string of the directory name of the search path generated by the search path generation unit using the conversion table,
The information search unit uses the search path and the search file name converted by the conversion unit to search for a corresponding information file in a corresponding directory from the information storage unit. Information management device. In the medical information management device according to claim 5 or 6,
An extraction unit for extracting the plurality of attributes of the image information from the information file obtained by the information search unit;
Among the character strings indicating the attributes extracted by the extraction unit, a decoding unit that decodes the conversion character string for compression using the conversion table;
A medical information management device comprising: The medical information management apparatus according to any one of claims 5 to 7,
The medical information management apparatus, wherein the predetermined character string of the conversion table is an instance UID among the plurality of attributes of the image information of the medical image file. A system for managing medical image files having image information consisting of a plurality of attributes,
An information storage unit for storing an information file having a file name including the image information of the medical image file;
A conversion table for associating a plurality of attributes of the image information of the medical image file with a delimiter character and composing a character string constituting a file name that is attached to each other in a predetermined order and associated with a conversion character string for compression;
A compression unit that converts the character string constituting the file name of the information file using the conversion table, and compresses the file name of the information file;
Classifying the information file with the file name compressed by the compression unit into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file; A storage unit for storing in the information storage unit;
A medical information management system characterized by comprising: A system for managing medical image files having image information consisting of a plurality of attributes,
A predetermined character string constituting a file name obtained by connecting the plurality of attributes of the image information of the medical image file with a delimiter character and connecting them in a predetermined order is converted into a predetermined compression conversion character string. The converted information file is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, and an information storage unit in which the information file is stored; A predetermined character string that constitutes a file name that is connected to each other in a predetermined order by separating the plurality of attributes of the image information of the medical image file and converted into a predetermined compressed conversion character string. In a medical information management system comprising: an image storage unit for storing image files classified into the plurality of directories;
A search key receiving unit that receives a search key used when searching the medical image file;
A search path generator for generating a search path based on the search key;
A conversion table associating the predetermined character string with the conversion character string for compression;
A file name generation unit for generating a search file name based on the search key;
A conversion unit that converts a character string of the search file name generated by the file name generation unit using the conversion table;
Using the search path and the search file name converted by the conversion unit, an information search unit for searching the corresponding information file in the corresponding directory from the information storage unit;
An extraction unit for extracting the image information indicated by the file name of the information file acquired by the information search unit;
A medical information management system characterized by comprising: A method for managing medical image files having image information comprising a plurality of attributes,
Preparing an information storage unit for storing an information file having a file name including the image information of the medical image file;
Preparing a conversion table for associating a plurality of attributes of the image information of the medical image file with a delimiter character and concatenating the character strings constituting the file name, which are linked together in a predetermined order, with the conversion character string for compression And steps to
Converting the character string constituting the file name of the information file using the conversion table and compressing the file name of the information file;
The information file with the file name compressed in the compressing step is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file. Storing in the information storage unit;
A medical information management method comprising: A method for managing medical image files having image information comprising a plurality of attributes,
A predetermined character string constituting a file name obtained by connecting the plurality of attributes of the image information of the medical image file with a delimiter character and connecting them in a predetermined order is converted into a predetermined compression conversion character string. The converted information file is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, and an information storage unit storing the information file is prepared And steps to
A predetermined character string that constitutes a file name that is connected to each other in a predetermined order by separating the plurality of attributes of the image information of the medical image file and converted into a predetermined compressed conversion character string. A medical information management method comprising the steps of:
Receiving a search key used when searching the medical image file;
Generating a search path based on the search key;
Preparing a conversion table associating the predetermined character string with the conversion character string for compression;
Generating a search file name based on the search key;
Converting the character string of the search file name generated in the step of generating the file name using the conversion table;
Using the search path and the search file name converted in the converting step, searching the corresponding information file in the corresponding directory from the information storage unit;
Extracting the image information indicated by the file name of the information file acquired in the searching step;
A medical information management method comprising: A program for managing medical image files having image information consisting of a plurality of attributes,
An information storage unit that stores an information file having a file name that includes the image information of the medical image file, and a plurality of attributes of the image information of the medical image file that are separated from each other in a predetermined order by a delimiter A computer having a conversion table that associates a character string that constitutes a concatenated file name with a conversion character string for compression,
Means for converting the character string constituting the file name of the information file using the conversion table and compressing the file name of the information file;
The information file with the file name compressed by the means for compressing is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, Means for storing in the information storage unit;
Medical information management program to function as A program for managing medical image files having image information consisting of a plurality of attributes,
A predetermined character string constituting a file name obtained by connecting the plurality of attributes of the image information of the medical image file with a delimiter character and connecting them in a predetermined order is converted into a predetermined compression conversion character string. The converted information file is classified into a plurality of directories each having a directory name including at least a part of the plurality of attributes of the image information of the medical image file, and an information storage unit in which the information file is stored; A predetermined character string that constitutes a file name that is connected to each other in a predetermined order by separating the plurality of attributes of the image information of the medical image file and converted into a predetermined compressed conversion character string. The image file is classified and stored in the plurality of directories, and the predetermined character string corresponds to the compressed conversion character string And kicking the conversion table,
On a computer with
Means for receiving a search key used when searching the medical image file;
Means for generating a search path based on the search key;
Means for generating a search file name based on the search key;
Means for converting the character string of the search file name generated by the means for generating the search file name using the conversion table;
Means for searching for a corresponding information file in a corresponding directory from the information storage unit using the search path and the search file name converted by the means for converting;
Means for extracting the image information indicated by the file name of the information file acquired by the means for searching;
Medical information management program to function as

Images