KR101763827B1 - System, method and program for transmitting health data by block-chain - Google Patents

Abstract

The present invention relates to block-chain based medical data transmission method and program with improved security. The block-chain based medical data transmission method according to an embodiment of the present invention includes: a block data receiving step (S100) in which a relay server receives one or more pieces of block data from a first node server; a step (S200) in which the relay server combines the one or more pieces of block data into a block chain and store the same; and a block data transmission step (S300) of transmitting the one or more pieces of block data to a second node server. According to the present invention, block data (i.e., medical data) stored in a plurality of node servers can be compared to determine whether the medical data requested to be transmitted by the user has been forged or falsified, and thus it is possible to transmit original data which is not forged or falsified to a desired node server.

Description

SYSTEM, METHOD AND PROGRAM FOR TRANSMITTING HEALTH DATA BY BLOCK-CHAIN BACKGROUND OF THE INVENTION 1. Field of the Invention [0001]

The present invention relates to a block-chain-based medical data transmission system, a method and a program, and more particularly to a block-chain-based medical data transmission system, method and program for preventing blockage / The present invention relates to a medical information data transmission system, method, and program.

As interest in people's health care has increased, interest and demand for medical IT services, such as medical data platforms, are increasing. As a result, related companies are continuing to work on data and patient privacy enhancement.

However, accidents of hacking of medical information are occurring frequently, and the anxiety of users who use the service is amplified. In addition, as the number of users of related services increases, the amount of medical information leaked at the time of hacking is also increasing. Therefore, it is necessary to develop a system, a method, and a program capable of sharing or transmitting medical information between hospitals while preventing security information leakage from a user (or a patient) by hacking by improving security.

(That is, sending and receiving of medical data) in a peer-to-peer (P2P) manner between each node server through a relay server to transmit medical data of all medical institution servers from a specific main server The present invention provides a block chain-based medical data transmission system, method, and program that prevents unauthorized access and leakage of all medical data by hacking a particular server. That is, simply, on the main server, medical data of all users or data of each node server (for example, a data server storing biometric data of a user acquired through a hospital server or a wearable device storing EMR data in a hospital, etc. The present invention provides a block chain-based medical data transmission system, method, and program for preventing the leakage of all important medical data due to a specific server security, because metadata for all of the medical data in the database is not stored in a specific main server.

The present invention also provides a block chain-based medical data transmission system, method, and program for verifying whether or not data stored in a specific node server is falsified data when transmitting medical data in a P2P manner and transmitting the original data to another node server desired by the user Program.

In addition, in order to prevent medical data from being leaked to another person when medical data is transmitted from a specific first node server to a second node server according to a request of a user, security is improved by applying a public key based encryption method , A block chain based medical data transmission system, a method and a program.

The block chain-based medical data transmission method according to an embodiment of the present invention is characterized in that the relay server receives one or more block data from a first node server, and the block data is medical data within a specific period of time for a specific user, Wherein the first node server is extracted from the first node server according to a request from a client; The relay server combining the one or more pieces of block data into a block chain and storing the block data; And a block data transmission step of transmitting the at least one block data to a second node server, wherein the first node server transmits block data according to a request received from the user client.

In addition, when receiving a request for confirmation of falsification of specific block data, reference block data extracted in the block chain and first block data and second block data received from the first node server and the second node server Wherein the reference block data, the first block data, and the second block data are data within the same period for the same user; And discriminating different block data among the reference block data, the first block data, and the second block data, and determining that the block data is forged or falsified.

The relay server receives specific block data from the transfer node server in response to the block data transfer request from the specific transfer node server to the third node server received from the client, Server or a second node server; Extracting, within the block chain, reference block data corresponding to the same condition as the block data received from the transmission node server; Receiving block data by requesting a node server other than the transmission node server which satisfies the same condition as the block data received from the transmission node server; A block data comparison step of comparing the reference block data, the first block data, and the second block data; And transmitting the block data determined as the original to the third node server, wherein the first block data is block data received from the first node server, and the second block data is the block data received from the second node server, And may be block data received from the node server.

If the three or more node servers store specific block data, the relay server may delete the block data in the stored block chain.

The relay server stores address information of each node server. In the block data receiving step, the second identification information input by the user client is received from the first node server, And the block data transmitting step searches the second address information corresponding to the second identification information and transmits the block data, wherein the second identification information is the identification information of the second node server, The second address information may be address information of the second node server.

The relay server may further store transmission history of specific block data.

If the reference format in the relay server is set for each piece of information included in the block data, and the format of the information included in the block data is different from the reference format, the relay server converts the reference format into the reference format And requesting a subsequent transmission.

In addition, when the node server is a medical institution server, the block data includes electronic medical record data within a specific patient unit period, and the first node server is a server of a first medical institution storing a user's existing electronic medical record And the second node server may be a server of a second medical institution where transmission of electronic medical record data of the first medical institution is requested by the user.

In addition, when the node server is a biometric data server, the block data may include measurement data within a unit period for a user of the specific biometric data measurement device.

In addition, the block data may be encrypted based on a public key provided by the relay server.

The method may further include, when the medical data is large-capacity data, deleting the block data corresponding to the medical data when the specific storage period has elapsed, And receiving metadata corresponding to the medical data.

The relay server receives the specific block data and the metadata corresponding to the block data from the transmission node server in response to the block data transmission request to the third node server received from the client by the specific transmission node server , The transmitting node server being either a first node server or a second node server; Extracting reference metadata corresponding to the reference block data when the reference block data corresponding to the same condition as the block data received from the transmission node server is deleted by a lapse of a storage period; Receiving metadata corresponding to block data by requesting a node server other than the transfer node server corresponding to the same condition as the block data received from the transmission node server; And comparing the reference metadata, the first metadata, and the second metadata to determine whether the block data requested to be transmitted is falsified or not, wherein the first block data is received from the first node server Block data, and the second block data may be block data received from the second node server.

A block-chain-based medical data transmission program according to another embodiment of the present invention is implemented in combination with a computer that is hardware, executes the aforementioned security-enhanced medical information data transmission method, and is stored in a medium.

According to the present invention as described above, the following various effects are obtained.

First, since the first node server and the second node server can share the encrypted medical data through the relay server, the security can be enhanced. In other words, since the P2P transmission of the medical data encrypted through the relay server is enabled, not all the medical data can be concentrated in one server, and a large amount of medical information can be prevented from being leaked due to the hacking of the specific server.

Second, since data is distributed and distributed to each node server and transmission / reception is performed when necessary, a specific server does not need to store all data, thereby reducing the burden on a specific server. That is, unlike the medical care information exchange system based on IHE XDS.b, one embodiment of the present invention does not need to store all the data (e.g., metadata) for each medical institution server in one central server, The burden on the relay server can be reduced. In addition, since the same block data can be deleted when the same block data is stored in three or more node servers, the relay server can further reduce the burden on the relay server.

Third, it is possible to compare the block data (i.e., medical data) stored in the plurality of node servers to check whether the medical data requested to be transmitted by the user has been forged or falsified, so that the unauthorized original data can be transmitted to the desired node server. This allows the user (ie, the patient) to receive continuity-of-care services at other hospitals based on his / her medical records that have not been tampered with.

1 is a connection diagram of a first node server, a second node server, and a relay server according to an embodiment of the present invention.
2 is a flowchart of a block-chain-based medical data transmission method according to an embodiment of the present invention.
3 is a flowchart of a block-chain-based medical data transfer method for performing forgery verification of specific block data according to an embodiment of the present invention.
4 is a flowchart of a block chain-based medical data transmission method for searching for and transmitting original data in response to a specific block data transmission request according to an embodiment of the present invention.
FIG. 5 is a flowchart of a block-chain-based medical data transmission method in which three or more node servers delete corresponding block data in a relay server when specific block data is stored according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention and the manner of achieving them will become apparent with reference to the embodiments described in detail below with reference to the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. To fully disclose the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

Unless defined otherwise, all terms (including technical and scientific terms) used herein may be used in a sense commonly understood by one of ordinary skill in the art to which this invention belongs. Also, commonly used predefined terms are not ideally or excessively interpreted unless explicitly defined otherwise.

The terminology used herein is for the purpose of illustrating embodiments and is not intended to be limiting of the present invention. In the present specification, the singular form includes plural forms unless otherwise specified in the specification. The terms " comprises "and / or" comprising "used in the specification do not exclude the presence or addition of one or more other elements in addition to the stated element.

In this specification, medical data refers to data that can be utilized in determining the health status of a specific user (e.g., a patient). For example, the medical data may include electronic medical record (EMR) data in the hospital. That is, the medical data may include a test result using a medical device or a diagnosis result by a medical staff. Further, for example, the medical data may include medical image data or the like measured or photographed by the medical equipment. Further, for example, the medical data may include biometric signal data obtained by a mobile terminal (e.g., a healthcare device) capable of measuring a biological signal.

In this specification, block data refers to data including medical data within a specific period of time for a specific user. For example, if the medical data is an electronic medical record, the block data may include a record of a particular patient ' s examination or care within a certain period of time. In addition, for example, the result of diagnosis of a specific patient by examination in the hospital A can be formed into one block data. Further, for example, when biometric signal data measured by a mobile terminal (for example, a healthcare device) is used as medical information data, each block data includes biometric signal data of a specific user acquired and accumulated for a specific time interval As a basic unit. In addition, the block data can be formed as a block chain, and can be stored in the form of a block chain in the form of a block chain to the relay server 100 or the node server 200 or 300. [

Hereinafter, a block chain-based medical data transmission system, method, and program according to embodiments of the present invention will be described with reference to the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a diagram of a block chain based medical data transmission system in accordance with an embodiment of the present invention.

Referring to FIG. 1, a block-chain-based medical data transmission system according to an embodiment of the present invention includes a relay server 100 and a plurality of node servers 200 and 300.

The relay server 100 transmits block data received from a specific node server to another node server. The first node server 200 can P2P block data to the second node server 300 through the relay server 100. [

In addition, the relay server 100 may include an authentication module. That is, the relay server 100 may store data (for example, key data) necessary for improving the security of transmitted medical data and transmit the data to each node server.

Also, the relay server 100 may store the block data provided by each node server in an internal storage space. The relay server 100 stores the block data received from the first node server 200 therein and can use the block data for checking whether a forgery or falsification is to be made later. Since three or more block data corresponding to the same condition (i.e., the same period of time of the same user) is required for checking whether a forgery or falsification has been made, comparison with the block data stored in the first node server 200 and the second node server 300 The block data stored as the reference block data can be utilized.

In addition, the relay server 100 may connect and store the block data in a block chain. The relay server 100 may connect and transmit all block data received for delivery, or may form and store block chains separately for each user. The relay server 100 may store block data corresponding to each medical data by forming a relationship with previous or subsequent blocks and storing them in a block chain.

The node servers 200 and 300 are specific servers that contain medical data. For example, the node server may be a hospital server storing electronic medical record (EMR) data corresponding to the results of a patient's examination. Also, for example, the node server may correspond to a database server that stores biometric signal data of users acquired by a mobile terminal (e.g., a wearable device having a sensor capable of measuring biometric signal data) . That is, the node server may include a database server that stores biometric signal data obtained from a user while being operated by a manufacturer of a specific wearable device.

The node server may search the corresponding medical data according to a specific medical data transmission request of the user and generate block data. The node server encrypts the block data to be transmitted based on the public key provided by the relay server 100 to enhance security and the node server that receives the block data from the relay server 100 decrypts can do.

Each of the node servers converts the medical data requested by the user into a reference format required by the relay server 100 and converts the reference format to a format used in each hospital upon receipt of the block data including the medical data Conversion agent. For example, the medical image data may be formatted differently depending on the type of device used in each hospital, so the relay server 100 needs to convert it into a specific format and store it. Accordingly, the node server can generate and transmit the node server in a specific format required by the relay server 100.

2 is a flowchart of a block-chain-based medical data transmission method according to an embodiment of the present invention.

2, a block chain-based medical data transmission method according to an embodiment of the present invention includes a step (S100) of receiving one or more block data from a first node server 200 by a relay server 100 Receiving step); The relay server 100 combining the at least one block data into a block chain (S200); And transmitting the one or more block data to the second node server 300 (S300: block data transmission step). A block chain-based medical data transmission method according to an embodiment of the present invention will be described in order.

The relay server 100 receives one or more block data from the first node server 200 (S100; block data receiving step). The first node server 200 receives a request for transmission of specific medical data from a user client. The first node server 200 generates or extracts block data for specific medical data according to a request received from the user client and transmits the block data to the relay server 100.

In one embodiment, the first node server 200 may be a server of a first medical institution (i.e., a first medical institution server) in which a user who is a patient has been treated, and the second node server 300 may be a server (I. E., The block data includes electronic medical record data within a particular patient ' s unit period, and the first node server < RTI ID = 0.0 > 200 is a server of a first medical institution that stores a user's existing electronic medical record, and the second node server 300 is a server of a second medical institution that is requested to transmit electronic medical record data of the first medical institution by a user .) The first medical institution server may be requested by the user client to transfer his or her electronic medical record to the second medical institution server. The first medical institution server may be requested to transmit the entire electronic medical record of the user from the user client and may be requested to transmit the electronic medical record for a specific period or a specific disease.

The first node server 200 (i.e., the first medical institution server) can extract the medical data (i.e., electronic medical record data) corresponding to the request of the user client from the internal database and extract the extracted medical data Medical record data) can be generated as block data and transmitted. For example, block data can be generated by dividing the extracted electronic medical record into specific unit periods. Accordingly, the first node server 200 may transmit a plurality of block data to the relay server 100 according to the period range requested by the user.

In addition, the node server can generate the block data form for each unit period when the medical data (for example, medical record data) is stored therein, and when the request for transmission of the medical data is received from the user, And transmits the block data to the relay server 100.

Also, in another embodiment, the first node server 200 may correspond to a biometric data storage server receiving and storing biometric data from a specific user's healthcare device, and the second node server 300 may be a cumulative A server of a medical institution that receives the biometric data and wants to check the physical condition of the user (i.e., the patient) may be applicable. In other words, biometrics data within a specific period may be required for the medical staff of the medical institution to reliably grasp the health status of the user, and accordingly, the user may request the first node server 200 (i.e., biometrics data storage server) It is possible to request the provision of medical data of a specific period (i.e., biometric data). The first node server 200 extracts the biometric data within the requested period range, generates block data, and transmits the biometric data to the second node server 300 (i.e., the medical institution server) To the server (100).

In addition, the first node server 200 may encrypt and transmit block data based on a Public Key Infrastructure (PKI) provided by the relay server 100. In the process of transmitting block data from the first node server 200 to the relay server 100 and transmitting block data from the relay server 100 to the second node server 300, , It is possible to encrypt and transmit data based on a public key provided by the relay server 100 in order to enhance security. The method of encrypting the block data is not limited to the public key method, and various methods such as the SSL method can be applied.

The relay server 100 combines the one or more pieces of block data into a block chain and stores the combined data in a block chain (S200). That is, the relay server 100 may store one or more block data received for transmission to the second node server 300.

The block data stored in the relay server 100 can be used for confirmation of forgery or falsification as described later. When the same block data is stored in two node servers as block data is transmitted from the first node server 200 to the second node server 300, if block data stored in either node server is forged, Can not be confirmed as the original data. Accordingly, the relay server 100 internally stores the block data received from the first node server 200 and transmitted to the second node server 300, extracts the block data when it is necessary to check whether the falsification has been made, (I.e., the same period of time of the same user) stored in the first node server 200 and the second node server 300 to determine whether the block data to be transmitted is falsified data.

In the case of block data already received by the first node server 200, the relay server 100 does not receive the same block data again from the first node server 200, Can be extracted and transmitted. For example, when a history that the first node server 200 transmits the block data requested to be transmitted is recorded, the relay server 100 receives only the identification information of the corresponding block data from the first node server 200 And may extract the stored block data corresponding to the identification information and transmit the extracted block data to the second node server 300.

The relay server 100 may form and store a block chain for each user when the block data is formed into a block chain. Since the relay server 100 forms a block chain by dividing the user data into the internal storage space, the required block data can be quickly searched.

Thereafter, the relay server 100 transmits the one or more block data to the second node server 300 (S300: block data transmission step).

Also, the relay server 100 may store address information of each node server. That is, when the first node server 200 receives a block data transmission request from the user client to a specific node server (i.e., the second node server 300), the relay server 100 transmits the block data to the second node server 300, (E.g., the name or identification code of the medical institution corresponding to the second node server 300). The relay server 100 may search the address information of the node server corresponding to the received identification information and transmit the block data to the corresponding address. Specifically, the block data receiving step S100 receives the second identification information (i.e., the identification information of the second node server 300) input by the user client from the first node server 200 , The block data transmission step S300 may search the second address information corresponding to the second identification information (i.e., the address information of the second node server 300) to transmit the block data.

3, when receiving a request for confirmation of forgery or falsification of specific block data, reference block data extracted in the block chain and reference block data extracted from the first node server 200 and the second node server 300 A block data comparison step (S400) of comparing received first block data and second block data; And determining (S500) that the different block data among the reference block data, the first block data, and the second block data is identified and determined to be forged (S500). The reference block data, the first block data, and the second block data may be data within the same period for the same user.

The relay server 100 may receive a request to confirm whether specific block data included in a specific node server is falsified data. The relay server 100 can receive one or more block data (e.g., first block data) that is desired to be falsified from a specific node server (e.g., the first node server 200) (E.g., second block data) of the same condition by requesting transmission of the second block data (e.g., the second node server 300). Also, the relay server 100 can search and extract reference block data having the same condition stored therein. Thereafter, the relay server 100 can compare the reference block data, the first block data, and the second block data (S400), and determine whether the data is forged or not (S500). For example, when the first block data is block data for which falsification check is requested, the relay server 100 determines that the first block data is different from the second block data and the reference block data, The server 200 can transmit the determination result. If the first block data, the second block data, and the reference block data are different from each other, the relay server 100 may transmit that it is impossible to determine whether a forgery or falsification is possible.

If the block data having the same condition is transmitted to and stored in three or more node servers, the number of block data that can be compared increases, and it is easy to determine whether specific block data is forged or not.

In addition, as shown in FIG. 4, the relay server 100 receives specific block data from the transmission node server according to the block data transmission request from the specific node to the third node server , The transmitting node server is one of a first node server 200 and a second node server 300 (S600); Extracting, in the block chain, reference block data corresponding to the same condition as the block data received from the transmission node server (S700); (S800) receiving block data by requesting a node server other than the transmission node server that satisfy the same condition as the block data received from the transmission node server; A block data comparing step (S900) of comparing the reference block data, the first block data, and the second block data; And transmitting the block data determined as the original to the third node server (S1000). The first block data may be block data received from the first node server, the second block data may be block data received from the second node server, and the reference block data may be stored in the relay server 100 May be stored block data.

In step S600, the relay server 100 may receive specific block data from the transmission node server according to the block data transmission request from the specific node to the third node server. The transmission node server may be either the first node server 200 or the second node server 300. That is, the first node server 200 or the second node server 300 can transmit the specific block data to the relay server 100 according to a request from the user client. Then, the relay server 100 can extract reference block data corresponding to the same condition as the block data received from the transmitting node server (that is, the same period of time of the same user) in the block chain (S700) (I.e., the second node server 300 in the case where the first node server 200 is a transfer node server) other than the transfer node server corresponding to the same condition as the block data received from the transfer node server Block data can be received (S800). Thereafter, the relay server 100 can compare the reference block data, the first block data, and the second block data (S900). Thereafter, the relay server 100 may transmit the block data determined as the original to the third node server (S1000). That is, when the block data received from the transmission node server is falsified data, the relay server 100 determines whether the block data (i.e., the block data stored in the node server other than the transmission node server, (I.e., reference block data stored in the base station 100) to the third node server. In this way, the original medical data of a specific user can be transmitted to the node server (i.e., the third node server) desired by the user, so that the user can continue the medical care based on the original data.

5, when the three or more node servers store specific block data, the relay server 100 may delete the block data stored in the block chain (S1100). When the relay server 100 stores the block data corresponding to the medical data, the leakage of the medical data may occur due to the hacking of the relay server 100. [ Accordingly, the relay server 100 requires at least three pieces of block data stored on other servers under the same conditions for the purpose of confirmation of forgery and falsification. Therefore, when the relay server 100 is stored only in the first node server 200 and the second node server 300 It may be stored in the database in the relay server 100 for the forgery confirmation. If block data of the same condition is stored in three or more node servers as the block data is transmitted to the third node server at the request of the user, the forgery-and-fake determination is performed without reference block data included in the relay server 100 Therefore, it is possible to delete the corresponding block data in the relay server 100. When the relay server 100 connects and stores the block data in a block chain, the block data may be separated and removed from the block chain, and the remaining data may be concatenated to form a block chain again.

The relay server 100 may further store transmission history of specific block data. That is, when the relay server 100 receives the transmission request to the specific node server and transmits the transmission request to the node server, the relay server 100 can store the transmission history of the specific block data. The transmission history data may include identification information of the node server to be transmitted to the relay server 100 and identification information of the node server to be transmitted from the relay server 100.

Various methods can be applied as a method of storing the transmission details in the relay server 100. [ In one embodiment, when the block data is stored in the relay server 100, node server identification information that stores block data having the same condition as the corresponding block data may be stored.

In another embodiment. When the relay server 100 does not store the block data (for example, when it deletes the block data in the relay server 100 as it is transmitted to three or more node servers), identification information is assigned for each block data, The block data identification information may be stored in the relay server 100 and the block data identification information may be matched with the identification information of the node server that stores the block data.

As the relay server 100 stores the transfer history information, the relay server 100 can determine to which node server the block data to be compared with block data requested to be transmitted is requested when the forgery or falsification is confirmed. For example, when specific block data is transmitted from the first node server 200 to the second node server 300 and transmitted from the second node server 300 to the third node server, the relay server 100 And may store the identification information of the first node server 200, the second node server 300, and the third node server in the transmission history. Thereafter, when the transmission from the user client to the third node server is requested to the fourth node server, the relay server 100 receives the block data requested to be transmitted from the third node server, It is possible to request the first node server 200 and the second node server 300, which are included in the transmission history, to provide block data of the same condition.

In addition, when the format of the information included in the block data is different from the reference format, the relay server 100 may request the first node server 200 to convert the information into the reference format and then transmit the reference format. The reference format in the relay server 100 may be determined according to the information type included in the block data. For example, when the medical data included in the block data is medical image data, the medical image data obtained by the same type of apparatus may have different extensions. The relay server 100 may request each node server to generate the medical data included in the block data in a predetermined reference format.

If the block data is a large amount of data, the relay server deletes the block data after a specific storage period has elapsed. For example, if the block data is a medical image (e.g., a CT image or an MR image) as the medical data, if the relay server continues to accumulate large-capacity block data, the burden on the server may increase. Accordingly, the relay server can set a period (i.e., a storage period) for storing the block data of a specific capacity or more inside, and delete the block data when the storage period is exceeded.

The relay server may directly compare the medical data included in the block data received from the plurality of node servers with the medical data having the same condition stored in the relay server to confirm whether the data is forged or not. The received metadata can be compared with each other to check whether the data is forged or not. That is, the block data reception step S100 may include receiving metadata corresponding to the medical data in the block data. The metadata may include information such as a diagnosis hospital, diagnosis name, and patient name of corresponding medical data.

Particularly, when the medical data is large-capacity data, the block data including the large-capacity medical data can be deleted in the relay server when the specific storage period elapses, and the relay server compares the large- It can take a lot of time. At this time, the relay server can compare the metadata corresponding to the medical data in place of the medical data itself included in the block data, and judge whether the data is forged or not.

For example, when medical image data (for example, CT image, MR image) is transmitted as medical data, if the medical image data, which is large-capacity data, is deleted after a lapse of a specific storage period, Only the server stores the medical image data, so it is impossible to judge which medical data has been modulated through the comparison of the two medical data, so it is impossible to directly compare the medical data and judge whether the data is forged or not. Accordingly, the relay server can receive the metadata including the diagnostic results and the like determined by the radiology medical staff when receiving the block data including the medical image data from the node server. The relay server can compare the metadata of the specific medical data stored in each server (i.e., the plurality of node servers and the relay server) to determine whether the user forged or falsified by comparing metadata. When the information in the metadata received from each server differs, the relay server can determine that the medical data is highly likely to be forged or falsified.

Specifically, the analysis of forgery or falsification during the process of transmitting medical data, which is large-volume data, can be performed as follows. First, in response to the block data transmission request from the specific node to the third node server received from the client, the relay server receives the specific block data and the metadata corresponding to the block data from the transmission node server . The transmission node server may be either a first node server or a second node server. Thereafter, when the reference block data corresponding to the same condition as the block data received from the transmission node server is deleted by the lapse of the storage period, the relay server can extract the reference metadata corresponding to the reference block data. Thereafter, the relay server may request the node server other than the transfer node server that corresponds to the block data received from the transfer node server to receive the metadata corresponding to the block data. Thereafter, the relay server may compare the reference metadata, the first metadata, and the second metadata to determine whether the block data requested to be transmitted is forged or not. The first block data may be block data received from the first node server, and the second block data may be block data received from the second node server. The relay server determines whether the metadata corresponding to the block data requested to be transmitted (e.g., the first metadata when the first node server receives the transmission request from the client) is stored in the other node server and the relay server For example, the reference metadata and the second metadata), it may be determined that there is a possibility that the block data requested to be transmitted (for example, the first block data) has been forged or falsified.

Also, the relay server can perform the forgery or falsification determination using the transmission history data instead of the medical data itself included in the block data. That is, when it is difficult for the relay server to directly compare the medical data in the block data (for example, in the case where the medical data is large-capacity data such as the image data and thus the direct comparison is difficult or the corresponding medical data is deleted in the relay server The number of data can not be three or more), the transmission file format, the file capacity, the transmission destination information, the transmission time, and the like. For example, when the file capacity of the medical data stored in the first node server (or the block data including the specific medical data) is different from the file capacity recorded in the second node server and the relay server, It can be determined that the possibility that the medical data stored in the server has been forged or corrupted is high.

The method of transmitting block-based medical data according to an embodiment of the present invention described above may be implemented as a program (or application) to be executed in combination with a computer, which is hardware, and stored in a medium.

The above-described program may be stored in a computer-readable medium such as C, C ++, JAVA, machine language, or the like that can be read by the processor (CPU) of the computer through the device interface of the computer, And may include a code encoded in a computer language of the computer. Such code may include a functional code related to a function or the like that defines necessary functions for executing the above methods, and includes a control code related to an execution procedure necessary for the processor of the computer to execute the functions in a predetermined procedure can do. Further, such code may further include memory reference related code as to whether the additional information or media needed to cause the processor of the computer to execute the functions should be referred to at any location (address) of the internal or external memory of the computer have. Also, when the processor of the computer needs to communicate with any other computer or server that is remote to execute the functions, the code may be communicated to any other computer or server remotely using the communication module of the computer A communication-related code for determining whether to communicate, what information or media should be transmitted or received during communication, and the like.

The medium to be stored is not a medium for storing data for a short time such as a register, a cache, a memory, etc., but means a medium that semi-permanently stores data and is capable of being read by a device. Specifically, examples of the medium to be stored include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, but are not limited thereto. That is, the program may be stored in various recording media on various servers to which the computer can access, or on various recording media on the user's computer. In addition, the medium may be distributed to a network-connected computer system so that computer-readable codes may be stored in a distributed manner.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, You will understand. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive.

100: Relay server 200: First node server
300: second node server

Claims (13)

Wherein the relay server receives one or more block data from a first node server, wherein the block data is extracted from the first node server at a request of a user client as medical data within a specific time range for a particular user, Receiving data;
The relay server combining the one or more pieces of block data into a block chain and storing the block data;
And a block data transmission step of transmitting the one or more block data to a second node server,
Wherein the first node server transmits block data according to a request received from the user client,
Wherein the relay server receives specific block data from the sender node server in order for the particular sender node server to send the block data to the third node server according to a request received from the client, Server or a second node server;
Extracting, within the block chain, reference block data corresponding to the same condition as the block data received from the transmission node server;
Receiving block data by requesting a node server other than the transmission node server which satisfies the same condition as the block data received from the transmission node server;
A block data comparison step of comparing the reference block data, the first block data, and the second block data; And
And transmitting the block data determined to be the original to the third node server,
Wherein the first block data is block data received from the first node server,
And the second block data is block data received from the second node server. The method according to claim 1,
When receiving a request for confirmation of forgery or falsification of specific block data,
Comparing the reference block data extracted in the block chain with the first block data and the second block data received from the first node server and the second node server, wherein the reference block data, the first block data, The block data being data within the same period for the same user; And
Further comprising determining different block data among the reference block data, the first block data, and the second block data to determine that the block data is forged. delete The method according to claim 1,
Further comprising: if the three or more node servers store specific block data, the relay server deletes the block data in a stored block chain. The method according to claim 1,
Wherein the relay server stores address information of each node server,
Wherein the block data receiving step comprises:
And receives second identification information input by the user client from a first node server,
Wherein the block data transfer step comprises:
And searching for second address information corresponding to the second identification information to transmit the block data,
The second identification information is identification information of the second node server,
And the second address information is address information of the second node server. The method according to claim 1,
And storing the transmission history of the specific block data by the relay server. The method according to claim 1,
If the reference format in the relay server is set for each piece of information included in the block data and the format of the information included in the block data is different from the reference format,
Further comprising the step of the relay server requesting transmission to the first node server after conversion to the reference format. The method according to claim 1,
When the first node server and the second node server are medical institution servers,
Wherein the block data includes electronic medical record data within a unit period of a specific patient,
Wherein the first node server is a server of a first medical institution that stores a user's existing electronic medical record,
Wherein the second node server is a server of a second medical institution that is requested by the user to transmit electronic medical record data of the first medical institution. The method according to claim 1,
When the first node server and the second node server are biometric data servers,
Wherein the block data comprises measurement data within a unit period for a user of a particular biometric data measurement device. The method according to claim 1,
Wherein the block data is encrypted and transmitted based on a public key provided by the relay server. The method according to claim 1,
When the medical data is large-capacity data,
And deleting the block data corresponding to the medical data when the specific storage period has elapsed,
Wherein the block data receiving step comprises:
And receiving metadata corresponding to the medical data in the block data. 12. The method of claim 11,
The relay server receives the specific block data and the metadata corresponding to the block data from the transmission node server in order to transmit the block data to the third node server according to the request received from the client by the specific transmission node server , The transmitting node server being either a first node server or a second node server;
Extracting reference metadata corresponding to the reference block data when the reference block data corresponding to the same condition as the block data received from the transmission node server is deleted by a lapse of a storage period;
Receiving metadata corresponding to block data by requesting a node server other than the transfer node server corresponding to the same condition as the block data received from the transmission node server; And
Comparing the reference metadata, the first metadata, and the second metadata to determine whether the block data requested to be transmitted is forged or not,
Wherein the first metadata is metadata for the first block data,
The second metadata is metadata for the second block data,
Wherein the first block data is block data received from the first node server,
And the second block data is block data received from the second node server. A block chain-based medical data transfer program, stored in a non-transitory computer readable storage medium, for executing the method of any one of claims 1, 2, 4 to 10, in combination with a relay server which is hardware.

Images