JP2018133080A - Block chain data management system, program, and data structure - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow a content data ID for accessing content data to be shared by a plurality of information processing devices even when content data and meta data are managed in association with each other.SOLUTION: Each of supplementary information management servers 25A to 25D generates an image ID indicating the identification information of pixel information on the basis of supplementary information in a DICOM image including the pixel information and supplementary information of a medical image. A data management server 3 includes a user information database 33 in which each of image IDs generated by each of the plurality of supplementary information management servers 25A to 25D and pixel information corresponding to each of the image IDs are stored in association with each other; and when receiving a specific request signal, outputs pixel information corresponding to the request signal out of the pixel information stored in the user information database 33.SELECTED DRAWING: Figure 2

Description

  The present invention relates to a data management system, a program, and a data structure.

  Conventionally, methods for managing data have been proposed. For example, for medical images used in the medical field, a standard called DICOM standard corresponding to medical images and incidental information is used, and medical images of patients are managed in each medical institution based on the DICOM standard. . DICOM is an abbreviation for Digital Imaging and Communication in Medicine, and is an international standard that defines storage and communication methods for medical images.

  As a management method for medical images and supplementary information, for example, a diagnostic system is known that enables image data obtained by a plurality of inspection apparatuses to be identified as image data of the same inspection (for example, Patent Document 1). ). In this diagnosis system, inspection order information to which inspection identification information is added is sent from an RIS (radiation department management system) to an inspection apparatus, and each inspection apparatus performs an inspection based on the inspection order information. Then, the diagnosis system creates image data and stores the created image data and examination identification information.

  Also, a medical image management apparatus that changes a medical image and attribute information registered in association with a database is known (for example, Patent Document 2). The medical image management apparatus stores and manages the medical image based on incidental information attached to the medical image obtained by photographing the patient. Specifically, the medical image management apparatus analyzes the relationship of the information included in the incidental information, classifies the information by hierarchy, adds related information associated with the upper layer to the information classified by hierarchy, and creates a hierarchical group. It is generated for each patient and stored in the management information database. When the medical image management apparatus moves the information included in the group to another group, the related information added to the information included in the group that is the movement source is transferred to the group that is the movement destination of the same layer as the information. Rewrite related information.

  Also, a processing device that provides a user with information related to items that are not included in the incidental information acquired from the server is known (for example, Patent Document 3). This processing apparatus extracts information related to items included in the incidental information transmitted from the DICOM image server and related to items not included in the acquired incidental information from the storage unit. Then, the processing device generates a display image representing the information included in the acquired supplementary information and the extracted information.

  There is also known a medical image set processing system that easily and accurately sets an image set composed of image data selected from a large amount of image data (for example, Patent Document 4). This medical image collection processing system stores image data of a patient to be diagnosed and its accompanying information. Then, the medical image set processing system classifies the incidental information hierarchically and generates an incidental information management list. On the other hand, the medical image set processing system creates an image set conditional expression for setting a desired image set based on the auxiliary information in the auxiliary information management list. Next, the medical image set processing system reads image data constituting the image set from the image data storage unit based on the image set conditional expression, supplies an image set constituted by the obtained image data, and supplies desired image data. Perform processing.

JP 2007-7190 A JP 2007-313219 A JP 2008-206687 A JP 2005-110974 A

  However, when content data and metadata are managed in association with each other, there is a problem that it is difficult for a plurality of users to share data.

  For example, in the DICOM standard medical image, the pixel information of the medical image as an example of content data and the incidental information as an example of metadata are managed in a combined form. Therefore, for example, when a medical image of a patient imaged in the medical institution A is to be used also in the medical institution B, the DICOM standard medical image imaged in the medical institution A can be transmitted to the medical institution B by any communication means. Etc. need to be transmitted.

  However, since the incidental information given to the DICOM medical image includes personal information of the patient, it is necessary to use highly confidential communication means. Therefore, when content data and metadata are managed in association with each other as in the case of a DICOM standard medical image, there is a problem that it is difficult for a plurality of users to share content data.

  The present invention has been made in view of the above circumstances, and even when content data and metadata are managed in association with each other, the content data ID for accessing the content data is a plurality of information. It is an object to provide a data management system, a program, and a data structure that can be shared by processing devices.

  In order to achieve the above object, a data management system according to the present invention is a data management system including a plurality of information processing devices and a data management device, and each of the plurality of information processing devices includes content data and the content A generation unit that generates content data ID representing identification information of the content data based on at least one of the metadata and the content data of data including metadata of the data, and a plurality of the information processing devices An ID database in which the content data ID generated by each of the generation units is stored, and the data management device includes: each of the content data IDs generated by a plurality of the information processing devices; and the content The content data corresponding to each data ID is associated with each other. And an output unit that outputs the content data corresponding to the request signal among the content data stored in the content database when a request signal related to the specific content data is received. .

  In addition, the first program of the present invention enables the computer to identify the content data based on at least one of the metadata and the content data among the data including the content data and the metadata of the content data. It is a program for functioning as a production | generation part which produces | generates content data ID showing.

  Further, the second program of the present invention, when the computer receives a request signal related to content data ID representing identification information of specific content data, and each of the content data IDs generated by the plurality of information processing devices And functioning as an output unit that outputs the content data corresponding to the request signal from the content data ID stored in the content database in which the content data corresponding to each of the content data IDs is stored in association with each other. It is a program for.

  The first data structure of the present invention is the identification information of the content data generated based on at least one of the metadata and the content data among data including content data and metadata of the content data. Is a data structure in which the content data ID representing the content data and the content data corresponding to the content data ID are associated with each other.

  Further, the second data structure of the present invention is the identification information of the content data generated based on at least one of the metadata and the content data among data including content data and metadata of the content data. This is a data structure representing a series of blocks including a content data ID representing.

  According to the present invention, even when content data and metadata are managed in association with each other, content data IDs for accessing content data can be shared by a plurality of information processing devices. The effect is obtained.

It is a figure which shows an example of schematic structure of the data management system of this Embodiment. It is a figure which shows the detailed structural example of the data management system of this Embodiment. It is a figure which shows the structural example of a user information database. It is a figure which shows an example of a user table. It is explanatory drawing for demonstrating the process performed at the time of the imaging of the medical image group for the first time. It is a figure which shows an example of a DICOM image. It is a figure which shows an example of an incidental information table. It is explanatory drawing for demonstrating the block chain stored in the incidental information management server of each medical institution. It is a figure which shows an example of a block information table. It is a figure which shows an example of an image table. It is explanatory drawing for demonstrating the process performed at the time of imaging of the medical image group after the 2nd time. It is a figure which shows an example of the medical institution database in which medical institution information is stored, and the block information database in which block information is stored. It is a figure for demonstrating the block chain stored in a block information database. It is explanatory drawing for demonstrating the process performed when acquiring the pixel information of a medical image. It is a schematic block diagram of the computer which functions as each apparatus of a data management system. It is a sequence diagram which shows the content of the registration process of a user and a medical institution. It is a sequence diagram which shows the content of a medical image acquisition process. It is a sequence diagram which shows the content of a block information generation process. It is a sequence diagram which shows the content of a pixel information acquisition process. It is explanatory drawing for demonstrating the data structure of the block chain of this embodiment.

  Hereinafter, embodiments will be described in detail with reference to the drawings. In the present embodiment, an example is described in which a DICOM image representing information including pixel information and incidental information of a medical image conforming to the DICOM standard is targeted, content data is pixel information, and metadata is incidental information. Explained.

<System configuration of data management system>

  FIG. 1 is a block diagram illustrating a data management system 1 according to the embodiment. As shown in FIG. 1, the data management system 1 includes a plurality of medical institution systems 2 </ b> A to 2 </ b> D, a data management server 3, and a user terminal 4. The plurality of medical institution systems 2A to 2D, the data management server 3, and the user terminal 4 are connected by a network 5 such as the Internet. The data management server 3 is an example of a data management device.

  The medical institution A includes the medical institution system 2A, the medical institution B includes the medical institution system 2B, the medical institution C includes the medical institution system 2C, and the medical institution D includes the medical institution system 2D. To do.

  FIG. 2 shows a detailed configuration example of the data management system 1. In the example illustrated in FIG. 2, a specific configuration of the medical institution system 2A included in the medical institution A and a specific configuration example of the data management server 3 are illustrated.

  The medical institution system 2A includes a hospital terminal 19A, an RIS (Radiology Information System) server 20A, an image diagnostic apparatus 21A, a processing server 22A, and an incidental information management server 25A. The data management server 3 includes a communication unit 30, a control unit 31, a medical institution database 32, and a user information database 33. The incidental information management server 25A is an example of an information processing device. The user information database 33 is an example of a content database. The processing server 22A is an example of a dividing device. The control unit 31 is an example of an output unit.

  A user who plans to use a medical institution operates the user terminal 4 and performs user registration with the data management server 3. Below, the scene of user registration is demonstrated first.

  When the user wants to receive an image diagnosis at a predetermined medical institution, the user operates the user terminal 4 to transmit / receive information to / from the data management server 3. Specifically, the user operates the user terminal 4 and transmits a control signal indicating that user registration is desired to the data management server 3. The control signal includes, for example, a user name.

  The communication unit 30 of the data management server 3 receives the control signal transmitted from the user terminal 4 and outputs it to the control unit 31. Next, the control unit 31 of the data management server 3 generates a user ID according to the control signal output from the communication unit 30. Then, the control unit 31 stores the user ID and the user name included in the control signal in the user information database 33 in association with each other.

  As shown in FIG. 3, the user information database 33 stores a user table and an image table. In the user table, a user ID and a user name are stored in association with each other. The image table stores each of image IDs generated by a plurality of additional information management servers 25A to 25D, which will be described later, and pixel information of a medical image corresponding to each of the image IDs. FIG. 4 shows an example of the user table. The image table will be described later.

  Further, the control unit 31 of the data management server 3 transmits the user ID to the user terminal 4 via the communication unit 30. The user ID is stored in a predetermined storage unit (not shown) of the user terminal 4.

  Next, a scene of medical institution registration performed between the medical institution system 2A and the data management server 3 will be described. The medical institution registration process is similarly performed for the medical institution systems 2B to 2D.

  The hospital terminal 19 </ b> A of the medical institution system 2 </ b> A receives operation information from a person in charge of the medical institution and transmits a control signal indicating that the medical institution is desired to be registered to the data management server 3. The control signal includes, for example, a medical institution name.

  The communication unit 30 of the data management server 3 receives the control signal transmitted from the hospital terminal 19A of the medical institution system 2A and outputs the control signal to the control unit 31. The control unit 31 of the data management server 3 generates a medical institution ID according to the control signal output from the communication unit 30. Then, the control unit 31 stores the medical institution database 32 in association with the medical institution ID and the medical institution name included in the control signal.

  In addition, the control unit 31 of the data management server 3 transmits the medical institution ID to the hospital terminal 19A via the communication unit 30. The medical institution ID is stored in a predetermined storage unit (not shown) of the hospital terminal 19A.

  Next, a scene where the user receives an image diagnosis in the medical institution A will be described.

  The user visits the medical institution A and presents the patient information including the user's personal information and the user ID stored in the storage unit (not shown) of the user terminal 4 to the medical institution A. The person in charge of the medical institution A acquires patient information and a user ID. The person in charge of the medical institution A inputs patient information to the RIS server 20A. In addition, the person in charge of the medical institution A inputs the user ID to the processing server 22A.

  The RIS server 20A receives patient information input by the person in charge. Then, the RIS server 20A registers registration information representing patient information, reservation information, diagnosis result information, and the like in a storage unit (not shown) based on patient information.

  Hereinafter, with reference to FIG. 5, a scene where the user undergoes image diagnosis will be described.

  The diagnostic imaging apparatus 21A captures a medical image of the user 10 in (A-1) of FIG. In FIG. 5A-1, it is assumed that a medical image is captured for the first time after the data management system 1 is operated. The medical image is captured by an image diagnostic device such as X-ray CT (Computed Tomography) or MRI (Magnetic Resonance Imager). A plurality of medical images are imaged by one imaging by the image diagnostic apparatus 21A. Then, the image diagnostic apparatus 21A generates incidental information of an image group representing a plurality of medical images obtained by one imaging based on the registration information registered by the RIS server 20A. Then, the diagnostic imaging apparatus 21A generates a DICOM image representing information in a format in which pixel information of the image group and incidental information are combined.

  FIG. 6 shows an example of a DICOM image. As shown in FIG. 6, the DICOM image includes supplementary information X and pixel information Y of a medical image. The incidental information is information for communicating and linking with other systems such as the RIS server 20A or HIS (Hospital Information System). The incidental information is encoded in a prescribed format. Further, the incidental information is information generated based on registration information representing patient information, reservation information, diagnosis result information, and the like, and thus includes highly confidential personal information and the like. Note that the pixel information is an example of content data. Further, the incidental information is an example of metadata.

  The processing server 22A includes a processing control unit 23A and a communication unit 24A.

  The processing control unit 23A receives a user ID input by a person in charge of the medical institution A. In FIG. 5A-2, the process control unit 23A divides the DICOM image generated by the image diagnostic apparatus 21A into incidental information and pixel information.

  Then, the processing control unit 23A outputs the incidental information and the user ID to the incidental information management server 25A in (A-3) of FIG. Further, the processing server 22A transmits the pixel information and the user ID to the data management server 3 via the communication unit 24A in (A-4) of FIG.

  The communication unit 30 of the data management server 3 receives the pixel information and the user ID transmitted from the processing server 22A. The control unit 31 of the data management server 3 stores the pixel information and user ID received by the communication unit 30 in the image table of the user information database 33.

  The incidental information management server 25A generates an image ID from the incidental information obtained by the processing server 22A in (A-5) of FIG. The incidental information management server 25A includes an incidental information control unit 26A, an incidental information database 27A, a block information database 28A, and a communication unit 29A. The image ID is an example of a content data ID. The incidental information control unit 26A is an example of a generation unit. The block information database 28A is an example of an ID database.

  The accompanying information control unit 26A acquires the accompanying information and user ID output from the processing server 22A. Then, the incidental information control unit 26A stores the incidental information and the user ID in the incidental information table of the incidental information database 27A.

  In the incidental information database 27A, incidental information and a user ID output from the processing server 22A are stored. In the incidental information table stored in the incidental information database 27A, as shown in FIG. 7, the user ID and the incidental information are stored in association with each other.

  The incidental information control unit 26A obtains incidental information and a user ID stored in the incidental information database 27A. Then, the incidental information control unit 26A generates an image ID representing identification information of the pixel information of the image group captured by the image diagnostic apparatus 21A by hashing the incidental information in (A-5) of FIG. To do. The generation of the image ID 1 in (A-5) of FIG. 5 is an image ID generated for the first time after the data management system 1 is operated for the first time. Therefore, the incidental information control unit 26A obtains the block 0 including the image ID0 which is dummy data generated in advance by the data management server 3, and generates the image ID1 by hashing the image ID0 and the incidental information. The image ID is used for managing pixel information of the image group.

  Here, a method for managing DICOM images in a medical institution will be described.

  When a patient undergoes a medical examination at a medical institution, a medical image that has already been imaged at another medical institution may play an equivalent role as the patient's medical record, and thus can be said to be an important information asset. In addition, it is desirable to use medical images that have already been captured in other medical institutions from the viewpoints of cost, time, medical burden reduction for the patient, and patient follow-up.

  In an actual medical field, when a medical image that has been taken once is used in another medical institution, a medical institution that has taken the medical image must create a letter of introduction, and some medical images can be transferred to other medical institutions. Most of them are brought into institutions. However, there are few cases where a medical image captured in a specific medical institution is used in another medical institution due to the trouble of obtaining a referral letter, and medical images captured in the past are not efficiently used.

  For this reason, a method of preparing an external database shared by each medical institution and centrally managing medical images of patients can be considered. By using this method, the medical institution can refer to all medical images of the patient. However, since medical images contain highly confidential personal information, a method of using an external database is not widespread because it is not appropriate to store medical images in an external database. Even if a medical image from which personal information has been deleted is stored in an external database, the patient cannot be specified and cannot be used for diagnosis.

  Therefore, in the present embodiment, each medical institution manages incidental information of medical images by using a block chain (for example, refer to a reference document (Satoshi Nakamoto, “Bitcoin: A Peer-to-Peer Electronic Cash System”)). In the present embodiment, supplementary information for medical images is managed by each medical institution, and pixel information for medical images is stored in an external database. Each medical institution manages incidental information including the patient's personal information, so that the patient's personal information is managed safely and medical images are used efficiently.

  Specifically, as shown in FIG. 8, a block chain representing a series of blocks including supplementary information and image IDs of medical images is managed by the supplementary information management servers 25A to 25D included in the plurality of medical institutions A to D. Is done. With the distributed ledger technology in the block chain, the same information is stored in the block information databases 28A to 27D of the medical institutions A to D that are participants of the system.

  For example, in each of the block information databases 28A to 27D of the incidental information management servers 25A to 25D, as shown in FIG. 8, a series of blocks including the incidental information and the image ID is stored as a block chain. By managing the incidental information and the image ID as a block chain, the incidental information including personal information can be managed separately from the pixel information of the medical image. Thereby, the image ID for accessing the pixel information of the medical image can be shared by a plurality of medical institutions. Further, by managing the incidental information and the image ID using the block chain, it becomes difficult to tamper with the data, and the integrity of the data of the incidental information and the image ID is ensured.

  Specifically, when a medical image is taken at a specific medical institution, the image ID and accompanying information are spread to all medical institutions. For example, when a medical image is captured in the medical institution A, the incidental information control unit 26A of the incidental information management server 25A performs hashing of the image ID 0 and the incidental information in (A-5) of FIG. , Image ID1 is generated. Then, the incidental information control unit 26A of the incidental information management server 25A transmits a block including the incidental information and the image ID1 to the other medical institution systems 2B to 2D.

  The incidental information management servers 25B to 25D of the medical institutions B to D acquire the blocks including the auxiliary information of the image group of the medical image captured at the medical institution A and the image ID1, and the acquired blocks are stored in the block information database 28A to 28A. Store in the 27D block information table. Further, the incidental information control unit 26A stores the generated block in the block information table of the block information database 28A. Thereby, the generation of a block chain representing a sequence of blocks corresponding to the image ID of the pixel information is started.

  The block information table of the block information database 28A stores a block chain representing a series of blocks including image IDs generated by the plurality of incidental information management servers 25A to 25D. Specifically, for example, when a medical image of a user is captured in a medical institution B to C different from the medical institution A, the block information table in the block information database 28A includes an image generated by the auxiliary information control unit 26A. A block chain representing a block including an ID and a series of blocks including an image ID generated by the other incidental information processing servers 25B to 25D is stored.

  FIG. 9 shows an example of the block information table. As shown in FIG. 9, in the block information table, block information representing an image ID and incidental information, and a block ID for identifying the block information are stored in association with each other.

  Next, the incidental information control unit 26A associates the generated image ID1 with the user ID in (A-6) of FIG. 5, and sends the image ID1 and the user ID to the data management server 3 via the communication unit 29A. To send.

  The communication unit 30 of the data management server 3 receives the image ID and user ID transmitted from the incidental information management server 25A. The control unit 31 of the data management server 3 acquires the image ID and user ID received by the communication unit 30. Then, the control unit 31 associates the image ID with the pixel information based on the image ID and user ID transmitted from the incidental information management server 25A and the pixel information and user ID transmitted from the processing server 22A. Specifically, the image ID and the pixel information corresponding to the user ID are associated with each other. Then, the control unit 31 stores the associated image ID and pixel information in the image table of the user information database 33.

  As shown in FIG. 5, among the image ID, pixel information, and user ID stored in the image table, the user ID is stored as an external key (FK). Therefore, the user ID and the image ID stored in the user table have a one-to-N relationship. FIG. 10 shows an example of the image table.

  When a medical image of a user is captured in medical institutions B to C different from the medical institution A, each of the image IDs stored in the image table of the user information database 33 is generated by a plurality of incidental information management servers 25A to 25D. It has been done. In addition, pixel information of a medical image associated with each image ID is captured by a plurality of medical institutions A to D.

  Next, the image diagnostic apparatus 21A captures the second group of medical images after the data management system 1 operates in (B-1) of FIG. Then, the image diagnostic apparatus 21A generates supplementary information of the image group of the medical image based on the registration information registered by the RIS server 20A. Then, the diagnostic imaging apparatus 21A generates a DICOM image of an image group of medical images obtained by the second imaging.

  In FIG. 11B-2, the processing control unit 23A of the processing server 22A converts the DICOM image of the image group obtained by the second imaging generated by the image diagnostic apparatus 21A into the incidental information and the pixel information. To divide. The process control unit 23A outputs the incidental information to the incidental information management server 25A in (B-3) of FIG. Further, the processing server 22A transmits the pixel information and the user ID to the data management server 3 in (B-4) of FIG.

  When the auxiliary information control unit 26A of the auxiliary information management server 25A generates the image ID of the pixel information of the medical image to be generated in (B-5) of FIG. 11, the image ID 1 generated last time and the generation target The image ID 2 is generated based on the accompanying information of the medical image. Specifically, the incidental information control unit 26A hashes the incidental information output by the processing server 22A and the image ID1 of the previous image group, thereby image ID2 of the image group obtained by the second imaging. Is generated.

  Then, the incidental information control unit 26A of the incidental information management server 25A transmits blocks including the incidental information and the image ID2 to the medical institution systems 2B to 2D.

  Each incidental information management server 25B-25D of medical institution B-D acquires the block containing incidental information and image ID2 of the image group of the medical image imaged in medical institution A, and uses the acquired block for block information database 28B- It is added to the block chain of the 27D block information table. Further, the incidental information control unit 26A adds the generated block to the block chain of the block information table of the block information database 28A.

  Thus, for example, as shown in FIG. 12, information related to the medical institution A is registered in the medical institution database 32 of the data management server 3, and the block information database provided in the incidental information management server 25A of the medical institution system 2A of the medical institution A Block information is stored in the block information table 28A.

  Note that the information stored in the block information table of the block information database 28A is stored as a block chain representing a sequence of a plurality of blocks including an image ID and accompanying information, as shown in FIG.

  Next, a scene where a medical institution B different from the medical institution A acquires pixel information of a medical image of the user 10 captured by the medical institution A will be described with reference to FIG.

  In (C-1) of FIG. 14, the user 10 visits the medical institution B and presents the patient information including the personal information of the user 10 and the user ID to the medical institution B. The person in charge of the medical institution B acquires the patient information of the user 10 and the user ID. The person in charge of the medical institution B inputs the user ID to the incidental information management server 25B.

  The incidental information control unit 26B of the incidental information management server 25B acquires the user ID. Then, the incidental information control unit 26B transmits a specific request signal including the user ID to the data management server 3 in (C-2). The specific request signal including the user ID is an example of a request signal related to specific content data.

  The control unit 31 of the data management server 3 receives the request signal received by the communication unit 30. Next, the control unit 31 refers to the image table of the user information database 33 and acquires all the image IDs and pixel information corresponding to the user IDs included in the request signal. And the control part 31 transmits all the acquired image ID and pixel information via the communication part 30 to the incidental information management server 25B of the medical institution system 2B.

  The incidental information control unit 26B of the incidental information management server 25B acquires the image ID and pixel information transmitted from the data management server 3. The incidental information control unit 26B refers to the block information table of the incidental information database 27B, and acquires incidental information corresponding to the image ID transmitted from the data management server 3. Then, the incidental information control unit 26B restores the DICOM image of the user 10 by associating the incidental information with the pixel information transmitted from the data management server 3. Thereby, the medical institution B can acquire a medical image of the user 10 captured in another medical institution A. Note that the auxiliary information and the pixel information may be simply associated without restoring the DICOM image.

  The data management server 3, the hospital terminal 19A, the RIS server 20A, the image diagnostic device 21A, the processing server 22A, and the incidental information management server 25A of the data management system 1 can be realized by a computer 50 shown in FIG. 15, for example. The computer 50 includes a CPU 51, a memory 52 as a temporary storage area, and a nonvolatile storage unit 53. Further, the computer 50 includes an input / output interface (I / F) 54 to which an input / output device or the like (not shown) is connected, and a read / write (R / W) unit that controls reading and writing of data with respect to the recording medium 59 55. The computer 50 also includes a network I / F 56 connected to a network such as the Internet. The CPU 51, memory 52, storage unit 53, input / output I / F 54, R / W unit 55, and network I / F 56 are connected to each other via a bus 57.

  The storage unit 53 can be realized by a hard disk drive (HDD), a solid state drive (SSD), a flash memory, or the like. A program for causing the computer 50 to function is stored in the storage unit 53 as a storage medium. The CPU 51 reads out the program from the storage unit 53 and develops it in the memory 52, and sequentially executes processes included in the program. A processor that executes a program that is software is hardware.

<Operation of Data Management System 1>
Next, the operation of the data management system 1 of the present embodiment will be described with reference to FIGS. The data management server 3, user terminal 4, hospital terminals 19A to 19D, image diagnostic device 21A, processing server 22A, and incidental information management servers 25A to 25B of the data management system 1 execute programs corresponding to the following processes.

<User and medical institution registration processing>
First, the process of user registration and medical institution registration will be described with reference to FIG.

  In step S <b> 100, the user operates the user terminal 4 and transmits a control signal including user information such as a user name to the data management server 3.

  In step S102, the communication unit 30 of the data management server 3 receives the control signal transmitted from the user terminal 4 in step S100. Next, the control unit 31 of the data management server 3 generates a user ID according to user information included in the control signal received by the communication unit 30. Then, the control unit 31 registers the user ID and the user name included in the user information in the user information database 33 in association with each other.

  In step S104, the control unit 31 of the data management server 3 transmits the user ID generated in step S102 to the user terminal 4.

  In step S <b> 106, the user terminal 4 acquires the user ID transmitted from the data management server 3 in step S <b> 104 and stores it in a predetermined storage unit (not shown) of the user terminal 4.

  In step S <b> 108, the hospital terminal 19 </ b> A of the medical institution system 2 </ b> A receives operation information from the person in charge of the medical institution and transmits a control signal including medical institution information such as the name of the medical institution to the data management server 3.

  In step S110, the communication unit 30 of the data management server 3 receives the control signal transmitted from the hospital terminal 19A in step S108. The control unit 31 of the data management server 3 generates a medical institution ID according to the medical institution information included in the control signal output from the communication unit 30. The control unit 31 registers the medical institution ID and the medical institution name included in the medical institution information in association with each other in the medical institution database 32.

  In step S112, the control unit 31 of the data management server 3 transmits the medical institution ID generated in step S110 to the hospital terminal 19A.

  In step S114, the hospital terminal 19A acquires the medical institution ID transmitted from the hospital terminal 19A in step S112, and stores it in a predetermined storage unit (not shown) of the hospital terminal 19A.

  Next, medical image acquisition processing and block information generation processing in the medical institution A will be described. In the present embodiment, a case where the medical image acquisition process and the block information generation process are performed at different timings will be described as an example. Specifically, a time zone in which the block information generation process is performed is set in advance. For example, the time zone in which the block information generation process is performed is preset as AM00: 00 to AM8: 00, and the incidental information management servers 25A to 25D execute the block information generation process between AM00: 00 and AM8: 00. . Therefore, the block chain is not updated during the time zone AM8: 0 to PM12: 00 different from the preset time zone.

<Medical image acquisition processing>
First, with reference to FIG. 17, the process performed in the scene in which a medical image is imaged in the medical institution A will be described.

  The user visits the medical institution A and presents the patient information including the user's personal information and the user ID stored in the storage unit (not shown) of the user terminal 4 to the medical institution A. The person in charge of the medical institution A acquires patient information and a user ID. The person in charge of the medical institution A inputs patient information to the RIS server 20A. In addition, the person in charge of the medical institution A inputs the user ID to the processing server 22A.

  The RIS server 20A receives patient information input by the person in charge. Then, the RIS server 20A registers registration information representing patient information, reservation information, diagnosis result information, and the like in a storage unit (not shown) based on patient information.

  In step S200, the diagnostic imaging apparatus 21A captures a plurality of medical images for the user. Then, the image diagnostic apparatus 21A generates incidental information of an image group representing a plurality of medical images based on the registration information registered by the RIS server 20A. Then, the diagnostic imaging apparatus 21A generates a DICOM image representing information in a format in which pixel information of the image group and incidental information are combined. Then, the diagnostic imaging apparatus 21A outputs the DICOM image to the processing server 22A.

  In step S202, the process control unit 23A of the process server 22A divides the DICOM image output from the image diagnostic apparatus 21A in step S200 into incidental information and pixel information.

  In step S204, the process control unit 23A outputs the incidental information obtained in step S202 and the user ID input by the person in charge at the medical institution A to the incidental information management server 25A. Further, the processing control unit 23A transmits the pixel information obtained in step S202 and the user ID input by the person in charge of the medical institution A to the data management server 3 via the communication unit 24A.

  In step S206, the communication unit 30 of the data management server 3 receives the pixel information and the user ID transmitted from the processing server 22A in step S204.

  In step S208, the control unit 31 of the data management server 3 stores the pixel information and user ID received by the communication unit 30 in step S206 in the image table of the user information database 33.

  In step S210, the incidental information control unit 26A of the incidental information management server 25A acquires the incidental information and user ID output from the processing server 22A in step S204.

  In step S212, the incidental information control unit 26A stores the incidental information and the user ID acquired in step S210 in the incidental information table of the incidental information database 27A.

<Block information generation processing>
Next, block information generation processing in the medical institution A will be described with reference to FIG. For example, in the time zone when the block information generation process is performed, the incidental information management server 25A executes the block information generation process shown in FIG.

  In the present embodiment, an example will be described in which the incidental information management servers 25A to 25D of each medical institution perform block information generation processing according to a preset order. For example, the data management server 3 assigns numbers representing the order of the block information generation processing to the medical institution IDs of the medical institutions A to D (medical institution A: 1, medical institution B: 2, medical institution C: 3. Medical institution D: 4).

  For example, the data management server 3 transmits an instruction signal for instructing execution of the block information generation process to the incidental information management servers 25A to 25D according to a preset order. And the incidental information management server which received the instruction | indication signal performs a block information generation process.

  For example, when the incidental information management server 25A of the medical institution A assigned number 1 receives the instruction signal, generation of a new block is started using the image ID included in the last block of the block information table. Next, when the incidental information management server 25B of the medical institution B assigned number 2 receives the instruction signal, a new block is generated using the last block generated by the incidental information management server 25A of the medical institution A. Start.

  Hereinafter, block information generation processing executed by the incidental information management server 25A will be described.

  In step S214, the control unit 31 of the data management server 3 transmits an instruction signal to the incidental information management server 25A via the communication unit 30 according to a preset order.

  In step S216, the incidental information control unit 26A of the incidental information management server 25A receives the instruction signal transmitted from the data management server 3. And the incidental information control part 26A will perform each process of the following step S218-step S228, if the instruction | indication signal received by the communication part 29A is acquired.

  In step S218, the incidental information control unit 26A acquires a set of incidental information and user ID among the incidental information and user ID stored in the incidental information database 27A.

  In step S220, the incidental information control unit 26A acquires the last block information from the block information table of the block information database 28A. The block information includes an image ID.

  In step S222, the supplementary information control unit 26A generates an image ID by hashing the supplementary information acquired in step S214 and the image ID included in the block information acquired in step S216.

  In step S222, when the image ID is generated for the first time after the data management system 1 is operated for the first time, the supplementary information control unit 26A determines the image ID 0 generated in advance by the data management server 3 and the above-described step S214. Image ID1 is generated by hashing the acquired auxiliary information.

  In step S224, the incidental information control unit 26A transfers the block including the incidental information acquired in step S214 and the image ID generated in step S218 to the medical institution systems 2B to 2D of the other medical institutions B to D. It transmits via the communication part 29A.

  In step S226, the communication units 29B to 29D of the incidental information management servers 25B to 25D of the medical institutions B to D receive the block including the incidental information and the image ID transmitted in step S224.

  In step S228, the incidental information control units 26B to 26D of the incidental information management servers 25B to 25D add the blocks received in step S226 to the block chains of the block information tables of the block information databases 28A to 27D.

  Next, in step S230, the supplementary information control unit 26A stores the block including the supplementary information acquired in step S218 and the image ID generated in step S222 in the block information table of the block information database 28A. Specifically, the block is added to the block chain of the block information table.

  In step S232, the supplementary information control unit 26A associates the image ID generated in step S222 with the user ID acquired in step S218, and sends the image ID and user ID to the data management server 3 via the communication unit 29A. To send through.

  In step S234, the communication unit 30 of the data management server 3 receives the image ID and user ID transmitted from the incidental information management server 25A.

  In step S236, the control unit 31 of the data management server 3 receives the image ID and user ID received in step S234, and the pixel information stored in the image table of the user information database 33 in step S208 of the medical image acquisition process. The image ID is associated with the pixel information based on the user ID. Specifically, the image ID and pixel information corresponding to the user ID are associated with each other and stored in the image table of the user information database 33.

  The incidental information control unit 26A repeats the processing from step S218 to step S232 for all the incidental information and user ID stored in the incidental information database 27A. Thereby, a block chain including the supplementary information and the image ID of the medical image captured in the medical institution A is generated.

  In addition, although the block information generation process performed in the incidental information management server 25A of the medical institution A has been described, the block information generation process is similarly performed in the incidental information management servers 25B to 25D of other medical institutions.

<Pixel information acquisition processing>
Next, a process in which the medical institution B acquires pixel information of a user's medical image captured by the medical institution A will be described with reference to FIG.

  The user visits the medical institution B and presents the patient information including the user's personal information and the user ID to the medical institution B. The person in charge of the medical institution B acquires the patient information of the user 10 and the user ID. The person in charge of the medical institution B inputs the user ID to the incidental information management server 25B.

  In step S400, the incidental information control unit 26B of the incidental information management server 25B acquires a user ID.

  In step S402, the incidental information control unit 26B transmits a specific request signal including the user ID acquired in step S400 to the data management server 3.

  In step S404, the control unit 31 of the data management server 3 acquires the request signal transmitted in step S402. The control unit 31 refers to the image table of the user information database 33 and acquires an image ID and pixel information corresponding to the user ID included in the request signal. And the control part 31 transmits image ID and pixel information via the communication part 30 to the incidental information management server 25B of the medical institution system 2B.

  In step S406, the incidental information control unit 26B of the incidental information management server 25B acquires the image ID and pixel information transmitted from the data management server 3 in step S404.

  In step S408, the incidental information control unit 26B refers to the block information table in the block information database 28B, and acquires incidental information corresponding to the image ID transmitted from the data management server 3. Then, the incidental information control unit 26B restores the DICOM image of the user 10 by associating the incidental information with the pixel information transmitted from the data management server 3. Thereby, the medical institution B can acquire a medical image of the user 10 captured in another medical institution A.

  As described above, the incidental information management servers 25A to 25D of the data management system according to the present embodiment are based on the incidental information of the DICOM image including the pixel information of the medical image and the incidental information. An image ID representing identification information of pixel information is generated. The data management server 3 of the data management system stores each of the image IDs generated by the plurality of incidental information management servers 25A to 25D in association with the pixel information of the medical image corresponding to each of the image IDs. When a specific request signal including the user ID is received, pixel information corresponding to the request signal is output from the pixel information of the medical image stored in the user information database. Thereby, even when the pixel information of the medical image and the incidental information are managed in association with each other, the image ID for accessing the pixel information of the medical image can be shared by a plurality of medical institutions. . In addition, by managing the incidental information of the medical image in the medical institution and managing the pixel information of the medical image in the external server, while managing the incidental information including the personal information of the patient who is the user in the medical institution, Pixel information of a medical image can be shared by a plurality of medical institutions.

  In this embodiment, a series of blocks including the image ID generated last time and the image ID generated from the accompanying information is managed as a block chain. Thereby, it becomes difficult to tamper with the data, and the integrity of the data of the incidental information and the image ID is ensured.

  In this embodiment, when managing a DICOM image including pixel information and supplementary information of a medical image, the pixel information of the medical image is divided into the image ID and the user ID. At the same time, it is managed by the data management server 3. Further, the incidental information is managed so as to be shared by the plural incidental information management servers 25A to 25D together with the image ID. When any one of the plurality of incidental information management servers 25A to 25D refers to a medical image for a specific user, the data management server 3 uses the user ID of the specific user to obtain pixel information of the medical image and The DICOM image can be restored by acquiring the image ID and using the accompanying information associated with the image ID.

  In the present embodiment, as shown in FIG. 20, incidental information and pixel information in a DICOM image are linked via an image ID. A series of blocks including the image ID and the accompanying information is managed as a block chain, and the accompanying information, the image ID, and the pixel information are associated with each other on a one-to-one basis. Thereby, the pixel information corresponding to each block of the block chain can be specified.

  Since a medical institution that uses the data management system of the present embodiment can acquire medical images that have already been captured by other medical institutions, an improvement in diagnostic accuracy is expected. This reduces the chance of taking a medical image, leading to a reduction in medical costs, a reduction in patient exposure dose, and a reduction in the burden on the doctor.

  In addition, medical images can be securely shared, and medical images captured in the past can be used for diagnosis in a plurality of medical institutions.

  Note that the present invention is not limited to the above-described embodiment, and various modifications and applications are possible without departing from the gist of the present invention.

  For example, in the present embodiment, the medical institutions A to D have been described as a plurality of medical institutions, but the present invention is not limited to this, and more or fewer medical institutions may be targeted.

  In the present exemplary embodiment, an example in which content data is pixel information of a medical image and metadata is incidental information has been described as an example. However, the present invention is not limited to this. For example, the content data is an image, and the metadata may be information representing the content shown in the image. Further, the content data may be document information, and the metadata may be information indicating the name of the user who created the document.

  In this embodiment, when a medical institution acquires a medical image captured by another medical institution, in the pixel information acquisition process, the medical institution transmits a request signal including a user ID to the data management server 3, and the data management server Although the case where the image ID and the pixel information corresponding to the user ID included in the request signal are output is described as an example in FIG. 3, the present invention is not limited to this. For example, the user ID may be stored in advance in association with the image ID in the incidental information database of the incidental information management server of the medical institution. In this case, when the incidental information management server receives the user ID input from the person in charge of the medical institution, the incidental information control unit of the incidental information management server refers to the block information table in the block information database and corresponds to the user ID. The attached image ID is acquired, and a request signal including the image ID is transmitted to the data management server 3. Then, the data management server 3 may output pixel information corresponding to the image ID included in the request signal to the incidental information management server. The request signal may include both a user ID and an image ID.

  In the present embodiment, the case where the image ID is generated based on the incidental information in the DICOM image has been described as an example, but the present invention is not limited to this. For example, the image ID may be generated based on pixel information in the DICOM image. Further, the image ID may be generated based on the incidental information and the pixel information.

  In the present embodiment, the case where the medical image acquisition process and the block information generation process are performed at different timings has been described as an example, but the present invention is not limited to this. For example, each time a medical image is captured in the medical image acquisition process, a block including supplementary information and an image ID may be generated in real time, the block information may be rewritten, and the block chain may be updated. In this case, it is necessary to preset the last block of the block chain in a predetermined manner. For example, it may be set so that other servers cannot update while a specific server is updating block information. Further, based on a consensus algorithm in the block chain technology, a process such as determining a correct branch of the block chain may be used.

  In the present specification, the embodiment has been described in which the program is installed in advance. However, the program can be provided by being stored in a computer-readable recording medium.

DESCRIPTION OF SYMBOLS 1 Data management system 2A-2D Medical institution system 3 Data management server 4 User terminal 5 Network 10 User 19A-19D Hospital terminal 20A-20D RIS server 21A-21D Diagnostic imaging apparatus 22A-22D Processing server 23A-23D Processing control part 24A- 24D communication units 25A to 25D incidental information management servers 26A to 26D incidental information control units 27A to 27D incidental information databases 28A to 28D block information database 30 communication unit 31 control unit 32 medical institution database 33 user information database 50 computer

Claims (9)

A block chain data management system including a plurality of information processing devices and a data management device,
Each of the plurality of information processing devices
A generating unit that generates content data ID representing identification information of the content data based on at least one of the metadata and the content data of data including content data and metadata of the content data;
An ID database storing the content data ID generated by the generation unit of each of the plurality of information processing devices,
The data management device includes:
A content database in which each of the content data IDs generated by a plurality of the information processing devices and the content data corresponding to each of the content data IDs are stored in association with each other;
An output unit that outputs the content data corresponding to the request signal among the content data stored in the content database when a request signal related to the specific content data is received;
Blockchain data management system. The content data is content data related to a user,
The metadata includes metadata about the user,
In the content database of the data management device, a user ID representing the user identification information, the content data ID, and the content data are stored in association with each other,
The output unit outputs the content data corresponding to the request signal based on the request signal including at least one of the content data ID and a user ID representing the identification information of the user.
The block chain data management system according to claim 1. When generating the content data ID of the content data to be generated, the generation unit of the information processing apparatus generates the content data ID generated last time and the meta data of the data corresponding to the content data to be generated. Generating the content data ID based on the data;
The block chain data management system according to claim 1 or 2. A block chain representing a sequence of blocks including the content data ID is stored in the ID database of the plurality of information processing apparatuses,
The generation units of the plurality of information processing devices add the block including the content data ID to the block chain;
The block chain data management system according to any one of claims 1 to 3. An image diagnostic apparatus for acquiring a DICOM image according to the DICOM standard by imaging a user;
A dividing device that divides the DICOM image acquired by the diagnostic imaging device into pixel information of a medical image as the content data and incidental information including information about the user as the metadata;
The generating unit of the information processing device generates an image ID as the content data ID based on at least one of the incidental information and the pixel information divided by the dividing device,
In the content database of the data management device, each of the image IDs is stored in association with the pixel information of the DICOM image corresponding to each of the image IDs.
The output unit, when receiving the request signal, outputs the pixel information corresponding to the request signal among the pixel information stored in the content database.
The block chain data management system according to any one of claims 1 to 4. Computer
To function as a generation unit that generates content data ID representing identification information of the content data based on at least one of the metadata and the content data among data including content data and metadata of the content data Program. Computer
Content in which each of content data IDs generated by a plurality of information processing devices and content data corresponding to each of the content data IDs are stored in association with each other when a request signal related to specific content data is received A program for functioning as an output unit that outputs the content data corresponding to the request signal among the content data stored in a database.   Content data ID representing identification information of the content data generated based on at least one of the metadata and content data of data including content data and metadata of the content data, and the content data ID A data structure in which the corresponding content data is associated.   Represents a series of blocks including content data ID representing identification information of the content data generated based on at least one of the metadata and the content data among data including content data and metadata of the content data data structure.