KR20200012371A - Medical Block Chain System - Google Patents

Abstract

According to one embodiment of the present invention, a medical blockchain system comprises: a communication unit for receiving medical information including patient information including information on a specific patient, a medical data header including information on a medical data creator or a requester, a medical data body including medical data, and prescription information including information on a prescription; an encryption unit for classifying the patient information, the medical data header, and the medical data body into a first medical block body, classifying the patient information and the prescription information into a second medical block body, and performing encryption by differentiating the difficulty of the encryption of the first medical block body and the second medical block body; and a storage unit for storing first and second medical blocks encrypted by the encryption unit.

Description

Medical Block Chain System

The present invention relates to a medical blockchain system and to a medical blockchain system with enhanced security.

A block chain may refer to a ledger technology that distributes and shares transaction details to all participants on a network without managing the transaction information in a centralized server. In other words, blockchain is a technology that records and manages transactions in a block by distributing authority for recording and managing transactions through a P2P network without a central authority.

The World Economic Forum (WEF, Davos Forum) is one of the 12 promising technologies (artificial intelligence and robotics, biotechnology, energy capture and storage technology, blockchain, geoengineering and neural technology) that require better science and technology policies in the global risk report. Blockchain was selected as one of ubiquitous sensors, advanced computing technology, advanced materials and nano materials, virtual augmented reality, space technology, and 3D printing.

Currently, many researches on blockchain technology have been conducted, but there is still a lack of research on medical blockchain technology. In particular, medical information is highly related to personal privacy because it requires high security.

Accordingly, the inventors have invented a medical blockchain system with enhanced security.

One technical problem to be solved by the present invention is to provide a medical block chain system with enhanced security.

Another technical problem to be solved by the present invention is to provide a medical block chain system for varying the difficulty of encryption according to the properties of medical information.

Another technical problem to be solved by the present invention is to provide a medical block chain system for integrally managing history information of medical information.

The technical problem to be solved by the present invention is not limited to the above.

According to an embodiment of the present invention, a medical blockchain system includes a patient data including information about a specific patient, a medical data header including information about a creator or requester of a medical data, a medical data body including medical data, and a prescription. A communication unit for receiving medical information including prescription information including information about the medical device, the patient information, the medical data header, and the medical data body are classified into a first medical block body, and the patient information and the prescription information are classified into second medical care. Including classified as a block body, the encryption unit for encrypting the first medical block body and the encryption difficulty of the first medical block body and the storage unit for storing the first and second medical blocks encrypted by the encryption unit Can be done.

According to an embodiment of the present disclosure, the encryption unit generates a first medical block header for the first medical block body and a second medical block header for the second medical block body, and includes one of the first and second medical block headers. One header may include a previous block hash value.

According to an embodiment of the present disclosure, when the communication unit receives the medical data of the medical information from the medical data request terminal, the first medical block body is transmitted, but when the first medical block body is transmitted, the encryption unit A third medical block body including a medical data head including patient information and information on the requestor requesting the medical data may be generated and encrypted.

According to an embodiment of the present disclosure, the third medical block body may further include a medical data body including the medical data.

According to an embodiment, the encryption unit may generate a third medical block header for the third medical block body.

According to an embodiment of the present disclosure, when the medical information request from the medical data request terminal is authenticated, the storage unit may generate the third medical block body.

According to an embodiment of the present disclosure, the medical data head of the first medical block body includes information about a creator that generated the medical data, and the medical data head of the third medical block body is a constructor of the first medical block body. In addition to the information on, it may further include information on the requestor who requested the medical data.

According to an embodiment of the present invention, a medical blockchain system includes a patient data including information about a specific patient, a medical data header including information about a creator or requester of a medical data, a medical data body including medical data, and a prescription. A communication unit for receiving medical information including prescription information including information about the medical device, the patient information, the medical data header, and the medical data body are classified into a first medical block body, and the patient information and the prescription information are classified into second medical care. Including a storage unit for classifying into a block body, the encryption unit for encrypting by varying the encryption difficulty of the first medical block body and the first medical block body and the first and second medical blocks encrypted by the encryption unit Can be done.

Accordingly, security of medical information may be enhanced.

According to an embodiment of the present disclosure, when the communication unit receives the medical data of the medical information from the medical data request terminal, the first medical block body is transmitted, but the encryption unit is configured to transmit the first medical block body. A third medical block body including a medical data head including patient information and information on the requestor requesting the medical data may be generated and encrypted.

Accordingly, the distribution process of medical information can be managed systematically.

1 is a diagram schematically illustrating a medical data generation terminal, a medical blockchain system, and a medical data request terminal according to an embodiment of the present invention.
2 is a block diagram illustrating a medical data generating terminal, a medical block chain system, and a medical data request terminal according to an exemplary embodiment of the present invention.
3 is a view for explaining an operating method according to an embodiment of the present invention.
4 is a view for explaining step S120 in detail according to an embodiment of the present invention.
5 is a view for explaining step S140 in detail according to an embodiment of the present invention.
6 is a view for explaining step S180 in detail according to an embodiment of the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. However, the technical idea of the present invention is not limited to the exemplary embodiments described herein and may be embodied in other forms. Rather, the embodiments introduced herein are provided to ensure that the disclosed contents are thorough and complete, and that the spirit of the present invention can be fully conveyed to those skilled in the art.

In the present specification, when a component is mentioned as being on another component, it means that it may be formed directly on the other component or a third component may be interposed therebetween. In addition, in the drawings, the shapes and thicknesses of the regions are exaggerated for the effective description of the technical content.

In addition, in various embodiments of the present specification, terms such as first, second, and third are used to describe various components, but these components should not be limited by these terms. These terms are only used to distinguish one component from another. Therefore, what is referred to as a first component in one embodiment may be referred to as a second component in another embodiment. Each embodiment described and illustrated herein also includes its complementary embodiment. In addition, the term 'and / or' is used herein to include at least one of the components listed before and after.

In the specification, the singular encompasses the plural unless the context clearly indicates otherwise. In addition, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, element, or combination thereof described in the specification, and one or more other features, numbers, steps, configurations. It should not be understood to exclude the possibility of the presence or addition of elements or combinations thereof. In addition, the term "connection" is used herein to mean both indirectly connecting a plurality of components, and directly connecting.

In addition, in the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

In the present specification, A or B may be understood as a concept including not only A and B but also both A and B.

1 is a view schematically showing a medical data generation terminal, a medical block chain system, a medical data request terminal according to an embodiment of the present invention, Figure 2 is a medical data generation terminal, a medical block according to an embodiment of the present invention A block diagram of a chain system and a medical data request terminal is shown.

Referring to FIG. 1, a medical network according to an embodiment of the present invention may include at least one of a medical data generation terminal 100, a medical blockchain system 200, and a medical data request terminal 300.

Referring to FIG. 2, the medical data generating terminal 100 may include at least one of a medical data generating unit 110 and a communication unit 120. The medical block chain system 200 may include a communication unit 210, It may include at least one of the encryption unit 220 and the storage unit 230, the medical data request terminal 300 may include at least one of the communication unit 310 and the decryption unit 320.

The medical data generating terminal 100 may mean a terminal for generating medical information or for storing the generated medical information in the medical blockchain system 200.

The medical data generating terminal 110 of the medical data generating terminal 100 may generate various medical information. For example, medical image information and medical examination information about a specific patient may be generated. The medical information may further include prescription information. The prescription information may refer to instructions written by a medical person to treat a patient's illness. The prescription information may include, but is not limited to, at least one of information on a patient's symptoms, disease name, prescription injection, and prescription medicine. Furthermore, the medical data generation terminal 110 may further manage patient information, for example, a patient name, a patient's birthday, and a resident's number of a patient.

The medical data generation terminal 100 may request to store the medical information in the blockchain system to enhance security. To this end, the communication unit 120 of the medical data generation terminal 100 may transmit medical information to the blockchain system 200. The blockchain system 200 may encrypt and store medical information received from the medical data generation terminal 100. In this case, the blockchain system 200 may improve the security of medical information by utilizing a distributed ledger technology.

The communication unit 210 of the blockchain system 200 may receive medical information from the communication unit 120 of the medical data generation terminal 100. The encryption unit 220 of the blockchain system 200 may encrypt the received medical information by using a blockchain technology. The storage 230 of the blockchain system 200 may store encrypted medical information.

The medical data request terminal 300 may mean any terminal for requesting medical information. The communication unit 310 of the medical data request terminal 300 may request transmission of specific medical information to the blockchain system 200. The decryption unit 320 of the medical data request terminal 300 may decrypt the encrypted medical information transmitted from the blockchain system 200.

The medical data generating terminal, the blockchain system, and the medical data request terminal according to an embodiment of the present invention have been described above with reference to FIGS. 1 and 2. Hereinafter, a method of operating a medical data generation terminal, a blockchain system, and a medical data request terminal according to an embodiment of the present invention will be described with reference to FIGS. 3 to 6.

3 is a view for explaining an operating method according to an embodiment of the present invention. 4 is a view for explaining step S120 in detail according to an embodiment of the present invention, Figure 5 is a view for explaining step S140 in detail according to an embodiment of the present invention, Figure 6 is a view of the present invention A diagram for describing step S180 according to an exemplary embodiment is described in detail.

Referring to FIG. 3, the operation method according to an embodiment of the present disclosure may include setting a difficulty level according to medical information generation step S110, medical information storage request step S120, medical information classification step S130, and classification. Generating and storing the first and second medical blocks (S140), requesting medical information (S150), determining authentication (S160), transmitting medical information (S170), medical information transmission history The method may include generating at least one of generating a third medical block (S180) and decoding (S190). Hereinafter, each step will be described in detail.

Step S110

The medical data generating terminal 100 may generate medical information (S110). This may be understood as a medical person generating medical information through the medical data generation terminal 100. Medical practitioners can be understood as including not only doctors and nurse pharmacists, but also health officials and medical scholars who utilize medical information. In addition, as described above, the medical information may be generated by the medical data generating unit 110 of the medical data generating terminal 100.

The medical information may include any information related to medical care. For example, as shown in FIG. 4, the medical information may include at least one of patient information, medical data head, medical data body, and prescription information. This is just an example, and of course, more information may be included.

The patient information may include at least one information of the nationality of the patient, the age of the patient, the name of the patient, the sex of the patient, the date of birth of the patient, the identification number of the patient (eg, social security number).

The medical data head may include metadata for the medical data body. In this case, the medical data head may include at least one of creation information and inquiry information of the medical data body. For example, the medical data head may include creation time information of when medical data was generated, creation information of which medical personnel were generated, and medical equipment identification information of which medical equipment was generated. At least one of the information may be included. The medical data head may include at least one of inquiry time information about when medical data is inquired and information about inquiry by which medical person.

That is, the medical data head may be used as an information field for managing the entire history that is utilized from the time when the medical data is generated. This can be used to check how medical data is being distributed.

Step S110 assumes the generation of the medical block and is not yet inquired, so only the generation information can be recorded in the medical data head.

The medical data body may include at least one of medical data, for example, medical image information and medical examination information. The medical image information may include, for example, at least one of X-ray image information, CT image information, MRI image information, ultrasound image information, and angiography image information. The medical examination information may include at least one of blood cholesterol information, blood pressure information, and blood inflammation value information.

The prescription information may include at least one of a disease name, injection information, and medicine information diagnosed by a medical person.

Step S120

Storage of the medical information may be requested through the communication unit 120 of the medical data generating terminal 100 (S120). This may be understood as a step in which a medical person requests to store the medical information generated by the medical data generating terminal 100 in the blockchain system 200.

Step S130 and Step S140

The encryption unit 220 of the blockchain system 200 may encrypt the received medical information.

At this time, the encryption difficulty may be defined according to the importance of the medical information. To this end, in step S130, the encryption unit 220 may be classified into a first medical block body composed of patient information, a medical data head, a medical data body and a second medical block body composed of patient information and prescription information. (See Figure 5).

In operation S140, the encryption unit 220 may encrypt the first medical block body and the second medical block body at different encryption difficulty levels. For example, the encryption unit 220 may set the encryption difficulty of the first medical block body to a high encryption difficulty of the second medical block body. This takes into account that the medical data body, for example, medical image information and medical examination information is medical data that is more closely related to the privacy of the patient. Thus, more sensitive medical information can provide enhanced security.

In another aspect, stability from hacking can be further enhanced because one medical information is stored divided into two medical block bodies.

Since the first medical block body and the second medical block body include patient information in common, even when the medical information receiving terminal receives one of the first medical block body and the second medical block body, There is an advantage that it is easy to identify which patient the medical information on the basis of the information.

In addition, the encryption unit 220 may further generate a medical block head in generating the encrypted first and second medical block bodies. As shown in FIG. 5, a first medical block head corresponding to the first medical block body may be generated, and a second medical block head corresponding to the second medical block body may be generated.

The medical block head may include a hash value of the previous medical block and a hash value of the medical block body. For example, when the second medical block body is continuously generated after generating the first medical block body, the second medical block head may include a hash value of the first medical block and a hash value of the second medical block body. have. In this way, the medical block bodies may form a chain.

The storage 230 of the blockchain system 200 may store the encrypted first medical block and the second medical block.

Step S150

The medical data request terminal 300 may request medical information from the blockchain system 200 (S150). For example, a user of the medical data request terminal 300 may request which medical information is required for which patient and transmit authentication information to the blockchain system 200.

Hereinafter, for convenience of description, a case where the medical data request terminal 300 requests a medical data body (eg, CT image information) of a specific patient will be assumed.

Step S160

The communication unit 210 of the blockchain system 200 may receive a request of the medical data request terminal 300. The blockchain system 200 may determine whether the request of the medical data request terminal 300 is authenticateable. If you are not certified, you can refuse to send medical information. Alternatively, if authentication is correct, step S170 may be performed.

Step S170

The communication unit 210 of the blockchain system 200 may transmit medical information requested by the medical data request terminal 300. As described above, when a medical data body (eg, CT image information) of a specific patient is requested in step S150, the communication unit 210 of the blockchain system 200 may transmit the encrypted first medical block. In another aspect, the second medical block does not transmit, thereby reducing communication traffic.

Step S180

When the blockchain system 200 transmits the medical information, the blockchain system 200 may manage the transmission history in the blockchain (S180).

To this end, the blockchain system 200 may generate a third medical block. As shown in FIG. 6, the third medical block may include a third medical block head and a third medical block body.

The third medical block head may include a hash value of the previous medical block and a hash value of the third medical block body.

The third medical block body may include patient information, a medical data head, and a medical data body.

Patient information of the third medical block body may be the same as patient information previously included in the first and second medical block bodies.

The medical data head of the third medical block body may be a field for managing generation and inquiry history of the medical data body. Accordingly, the medical data head of the third medical block body may include transmission information according to step S170. For example, the medical data head of the third medical block body may include at least one of a transmission time according to step S170, identification information of a recipient, that is, user of the medical data request terminal 300, and medical grade information of the recipient. .

Furthermore, the medical data head of the third medical block body may include medical data head information of the first medical block body as it is. Accordingly, at least one of the information on the generation time of the medical data body, the identification information of the creator, and the rating information of the creator may be further included.

In addition, the third medical block body may further include a medical data body. That is, as previously assumed, CT image information may be included.

Accordingly, since the third medical block includes generation and inquiry history information of the medical data body, how the medical information is distributed can be systematically managed.

In addition, since the third medical block is automatically generated when the medical block is transmitted, the convenience of managing the inquiry history information may be improved.

According to an example, the blockchain system 200 may determine whether to perform step S180. For example, the blockchain system 200 may perform step S180 only on the medical information having high importance based on the importance of the medical information. More specifically, the blockchain system 200 may generate a medical block for inquiry history information only when the first medical block determined to be more important among the first and second medical blocks is transmitted. That is, the blockchain system 200 may omit generating the medical block for the inquiry history information when the second medical block determined to be of low importance is transmitted.

On the other hand, the blockchain system 200 may generate a fourth medical block reflecting additional inquiry history information when the transmission of another first medical block later is performed. In this case, the fourth medical block may further include inquiry history information additionally generated in addition to the medical data head of the existing third medical block.

Step S190

The medical data request terminal 300 may decode the medical information received in step S170 (S190). That is, the medical data request terminal 300 may decode the first medical block (including CT image information) received in step S170.

The operation method according to an exemplary embodiment of the present invention has been described above with reference to FIGS. 3 to 6.

According to an embodiment of the present invention, since medical blocks encrypted at different difficulty levels may be generated based on the importance of the medical information, two conflicting purpose indicators of security and traffic may be achieved.

In addition, according to an embodiment of the present invention, even if the medical block is divided and stored, since it commonly includes patient information, whose medical information can be easily identified.

In addition, the blockchain system according to an embodiment of the present invention may automatically generate a medical block (ie, a third medical block) for managing inquiry history information after transmitting the medical block. As a result, the inquiry history information management medical block may provide systematic information about the generation and inquiry of the medical data body.

In particular, in the blockchain system according to an exemplary embodiment of the present invention, since the medical block inquiry history is automatically reflected as a block, the inquiry history information may also have high security. That is, even if the terminal requesting medical information does not make a separate request to the blockchain system, the medical block inquiry history may be reflected in the block. This means that even if the terminal requesting medical information does not belong to the blockchain network, the inquiry history information is managed by the blockchain, thereby providing high convenience.

Further, the inquiry history information management medical block (ie, the third medical block) may or may not be generated according to the importance of the medical information. That is, the inquiry history information management medical block is generated when the medical data body is transmitted, but the inquiry history information management medical block may not be generated when the prescription information is transmitted. Accordingly, two conflicting purpose indicators can be achieved, namely, tracking history and traffic.

Furthermore, although not described above, the medical data body of the third medical block may be replaced with simple indication information. For example, a hash value of the first medical block (medical data body generation block) may be recorded in the medical data body of the third medical block. That is, the medical data body managed in the third medical block may be indicated as being recorded in the medical data body of the first medical block. As a result, the data amount of the medical data body of the third medical block can be significantly reduced.

As mentioned above, although this invention was demonstrated in detail using the preferable embodiment, the scope of the present invention is not limited to a specific embodiment, Comprising: It should be interpreted by the attached Claim. In addition, those of ordinary skill in the art should understand that many modifications and variations are possible without departing from the scope of the present invention.

Claims (7)

Receive medical information consisting of patient information including information about a particular patient, a medical data header containing information about a medical data creator or requestor, a medical data body containing medical data, and prescription information including information about a prescription A communication unit;
Classify the patient information, the medical data header, and the medical data body into a first medical block body, and classify the patient information and the prescription information into a second medical block body, wherein the first medical block body and the first medical block body are classified. An encryption unit for encrypting at different encryption difficulty levels of the medical block body; And
And a storage unit for storing the first and second medical blocks encrypted by the encryption unit. According to claim 1,
The encryption unit,
Generate a first medical block header for the first medical block body and a second medical block header for the second medical block body,
The medical block chain system of claim 1, wherein one of the first and second medical block headers includes a previous block hash value. According to claim 1,
When the communication unit receives the medical data of the medical information from the medical data request terminal, and transmits the first medical block body,
When the first medical block body is transmitted, the encryption unit generates and encrypts a third medical block body including a medical data head including the patient information and information about the requestor who requested the medical data. . The method of claim 3, wherein
The third medical block body further comprises a medical data body including the medical data. The method of claim 3, wherein
The encryption unit is a medical block chain system for generating a third medical block header for the third medical block body. The method of claim 3, wherein
The storage unit, the medical block chain system for generating the third medical block body, the encryption unit when the medical information request from the medical data request terminal is authenticated. The method of claim 3, wherein
The medical data head of the first medical block body includes information about the creator that generated the medical data,
The medical data head of the third medical block body further includes information on the requestor who requested the medical data, in addition to the information about the creator of the first medical block body.

Images