KR102120942B1 - Medical Block Chain System - Google Patents

Abstract

The medical blockchain system according to an embodiment of the present invention includes patient information including information about a specific patient, a medical data header including information about a medical data creator or a requester, and a medical data body and a prescription including medical data. A communication unit for receiving medical information consisting of prescription information including information on, the patient information, the medical data header and the medical data body is classified into a first medical block body, and the patient information and the prescription information are second It is classified as a medical block body, and includes an encryption unit for encrypting the encryption difficulty of the first medical block body and the first medical block body at different levels, and a storage unit for storing the first and second medical blocks encrypted by the encryption unit. Can be achieved.

Description

Medical Block Chain System{Medical Block Chain System}

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

Block chain can mean distributed ledger technology that distributes and shares transaction history information to all participants on the network without managing it in a centralized server. In other words, blockchain is a technology that records and manages the authority to record and manage transactions through a P2P network without a central authority.

The World Economic Forum (WEF, Davos Forum) has 12 promising technologies (Artificial Intelligence and Robotics, Biotechnology, Energy Capture and Storage Conversion Technology, Blockchain, Geotechnology, Neurotechnology) that require better science and technology policies in the Global Risk Report. ,'Ubiquitous Sensor, Advanced Computing Technology, Advanced Materials and Nano Materials, Virtual Augmented Reality, Space Technology, 3D Print) was selected as'Blockchain'.

Currently, many researches on blockchain technology have been conducted, but there is still insufficient research on medical blockchain technology. In particular, in the case of medical information, it can be considered that a high level of security is required because it is closely related to the personal privacy. However, in the related art, as in the prior art document (Korean Patent Publication No. 10-2006-0010947), medical information is centrally stored and managed in a single hospital information system, so even if a security element is provided, there is a vulnerability in security.

Accordingly, the present inventor has invented a medical blockchain system with enhanced security.

Korean Patent Publication No. 10-2006-0010947

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

Another technical problem to be solved by the present invention is to provide a medical blockchain system having a different encryption difficulty according to the properties of medical information.

Another technical problem to be solved by the present invention is to provide a medical blockchain system that comprehensively manages historical information of medical information.

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

The medical blockchain system according to an embodiment of the present invention includes a patient data including information about a specific patient, a medical data header including information about a medical data creator or a requester, and a medical data body and a prescription including medical data. A communication unit for receiving medical information consisting of prescription information including information on the patient, the patient information, the medical data header and the medical data body is classified into a first medical block body, and the patient information and the prescription information is second medical Classified as a block body, including an encryption unit for encrypting the encryption difficulty of the first medical block body and the first medical block body differently, and a storage unit for storing the first and second medical blocks encrypted by the encryption unit It 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, among the first and second medical block headers. One header may include a previous block hash value.

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

According to an embodiment, 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, 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 one embodiment, the medical data head of the first medical block body includes information on the creator that generated the medical data, and the medical data head of the third medical block body is the constructor of the first medical block body In addition to the information about, it may further include information about the requester who requested the medical data.

The medical blockchain system according to an embodiment of the present invention includes a patient data including information about a specific patient, a medical data header including information about a medical data creator or a requester, and a medical data body and a prescription including medical data. A communication unit for receiving medical information consisting of prescription information including information on the patient, the patient information, the medical data header and the medical data body is classified into a first medical block body, and the patient information and the prescription information is second medical Classified as a block body, including an encryption unit for encrypting the encryption difficulty of the first medical block body and the first medical block body differently, and a storage unit for storing the first and second medical blocks encrypted by the encryption unit It can be done.

Accordingly, security of medical information may be enhanced.

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

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

1 is a view schematically showing 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 of a medical data generating terminal, a medical blockchain system, and a medical data request terminal according to an embodiment of the present invention.
3 is a view for explaining an operation method according to an embodiment of the present invention.
4 is a view for explaining in detail step S120 according to an embodiment of the present invention.
5 is a view for explaining in detail step S140 according to an embodiment of the present invention.
6 is a view for explaining in detail step S180 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. However, the technical spirit of the present invention is not limited to the 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 is sufficiently conveyed to those skilled in the art.

In the present specification, when a component is referred to as being on another component, it means that it may be formed directly on another component, or a third component may be interposed between them. In addition, in the drawings, the shape and the thickness of the regions are exaggerated for 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 component. Therefore, what is referred to as the first component in one embodiment may be referred to as the second component in another embodiment. Each embodiment described and illustrated herein also includes its complementary embodiment. In addition, in this specification,'and/or' is used to mean including at least one of the components listed before and after.

In the specification, a singular expression includes a plural expression unless the context clearly indicates otherwise. Also, terms such as “include” or “have” are intended to indicate the presence of features, numbers, steps, elements, or combinations thereof described in the specification, and one or more other features, numbers, steps, or configurations. It should not be understood as excluding the possibility of the presence or addition of elements or combinations thereof. In addition, in this specification, "connecting" is used in a sense to include both indirectly connecting a plurality of components, and directly connecting.

In addition, in the following description of the present invention, when it is determined that detailed descriptions of related known functions or configurations may unnecessarily obscure the subject matter of the present invention, detailed descriptions thereof will be omitted.

In this specification, A or B may be understood as a concept including both A and B as well as A and B only.

1 is a diagram schematically showing a medical data generating terminal, a medical blockchain system, and a medical data request terminal according to an embodiment of the present invention, and FIG. 2 is a medical data generating terminal and medical block according to an embodiment of the present invention. It is a block diagram of a chain system and a request terminal for medical data.

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 generation terminal 100 may include at least one of a medical data generation unit 110 and a communication unit 120, and the medical blockchain system 200 may include a communication unit 210, At least one of the encryption unit 220 and the storage unit 230 may be included, and the medical data request terminal 300 may include at least one of the communication unit 310 and the decryption unit 320.

The medical data generation terminal 100 may mean a terminal that generates medical information or wants to store the generated medical information in the medical blockchain system 200.

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

The medical data generation terminal 100 may request to store medical information in a 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 generating terminal 100. At this time, the blockchain system 200 may improve the security of medical information by utilizing 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 using blockchain technology. The storage unit 230 of the blockchain system 200 may store encrypted medical information.

The medical data request terminal 300 may refer to any terminal that requests medical information. The communication unit 310 of the medical data request terminal 300 may request the blockchain system 200 to transmit specific medical information. 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 generation 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, an operation method of 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 operation method according to an embodiment of the present invention. 4 is a view for explaining in detail step S120 according to an embodiment of the present invention, Figure 5 is a view for explaining in detail step S140 according to an embodiment of the present invention, Figure 6 is a diagram for the present invention This is a view for explaining in detail step S180 according to an embodiment.

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

Step S110

The medical data generation 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. The term "medical person" can be understood as a concept that includes not only doctors and nurse pharmacists, but also health officials and medical scholars who use medical information. In addition, as described above, medical information may be generated by the medical data generation unit 110 of the medical data generation terminal 100.

The medical information may include any medical-related information. For example, as illustrated in FIG. 4, the medical information may include at least one of patient information, medical data head, medical data body, and prescription information. Of course, this is only an example, and more information may be included.

The patient information may include at least one of a patient's nationality, a patient's age, a patient's name, a patient's gender, a patient's date of birth, and a patient's identification number (eg, social security number).

The medical data head may include metadata about the medical data body. At this time, 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 on when medical data was generated, creation information on which medical personnel generated the medical data, and medical device identification information on which medical equipment was generated. It may include at least one of the information. On the other hand, the medical data head may include at least one of inquiry time information about when medical data is searched and inquiry information about which medical data is searched for in connection with the inquiry information.

That is, the medical data head may be used as an information field for managing the entire history utilized from the time the medical data is generated. Accordingly, it can be checked how the medical data is distributed.

In step S110, assuming the creation of the medical block and before it is inquired, only the creation 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 angiographic image information. The medical examination information may include at least one of blood cholesterol information, blood pressure information, and blood inflammation level information.

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

Step S120

Storage of medical information may be requested through the communication unit 120 of the medical data generation terminal 100 (S120). This can be understood as a step in which the medical person requests to store the medical information generated by the medical data generation 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 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, and a medical data body, and a second medical block body composed of patient information and prescription information. (See Figure 5).

In step S140, the encryption unit 220 may encrypt the first medical block body and the second medical block body with different encryption difficulty. For example, the encryption unit 220 may set the encryption difficulty of the first medical block body as high as that of the second medical block body. This considers that the medical data body, for example, medical image information and medical checkup information is medical data more closely related to the patient's privacy. Therefore, the more sensitive the medical information, the more secure it can be provided.

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

Since the first medical block body and the second medical block body commonly include patient information, the patient may be received even if either the first medical block body or the second medical block body is received by the medical information receiving terminal. There is an advantage in that it is possible to easily identify which patient is medical information based on the information.

Furthermore, the encryption unit 220 may further generate a medical block head in generating the encrypted first and second medical block bodies. As illustrated 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 the first medical block body is generated, the second medical block head may include a hash value of the first medical block body and a hash value of the second medical block body. have. Thereby, the medical block body can form a chain.

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

Step S150

The medical data request terminal 300 may request medical information from the blockchain system 200 (S150). For example, the 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, it is assumed that the medical data request terminal 300 requests a medical data body (ex. CT image information) of a specific patient.

Step S160

The communication unit 210 of the blockchain system 200 may receive a request from the medical data request terminal 300. The blockchain system 200 may determine whether the request of the medical data request terminal 300 is authenticable. If it is not authenticated, you may 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. When the medical data body (ex. CT image information) of a specific patient is requested in step S150 as previously described, the communication unit 210 of the blockchain system 200 may transmit the encrypted first medical block. In another aspect, since the second medical block is not transmitted, communication traffic can be reduced.

Step S180

When the medical information is transmitted, the blockchain system 200 may manage the transmission history as a blockchain (S180).

To this end, the blockchain system 200 may generate a third medical block. As illustrated 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.

The patient information of the third medical block body may be the same as the patient information 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 the creation 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 in step S170, identification information of a recipient, that is, a 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 creation 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, CT image information may be included as previously described.

Accordingly, since the third medical block includes history data for generating and querying a 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, convenience of managing 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 for medical information having high importance based on the importance of 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, when the second medical block determined to have low importance is transmitted, the blockchain system 200 may omit the creation of the medical block for the inquiry history information.

On the other hand, of course, when the transmission to another first medical block is performed later, the blockchain system 200 may generate a fourth medical block reflecting additional inquiry history information. At this time, the fourth medical block may further include inquiry history information 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 requesting terminal 300 may decode the first medical block (including CT image information) received in step S170.

The operation method according to an 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 with different difficulty levels may be generated based on the importance of the medical information, two conflicting purpose indicators such as security and traffic can be achieved.

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

In addition, the blockchain system according to an embodiment of the present invention may automatically generate a medical block (that is, a third medical block) for managing inquiry history information after transmitting the medical block. In this way, the inquiry history information management medical block can provide systematic information about the creation and inquiry of the medical data body.

In particular, in the blockchain system according to an embodiment of the present invention, the medical block inquiry history is automatically reflected as a block, so that the inquiry history information can 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 can be reflected in the block. This means that even if the terminal requesting medical information does not belong to the blockchain network, it means that the inquiry history information is managed by the blockchain, so it can provide high convenience.

Furthermore, the inquiry history information management medical block (that is, the third medical block) may or may not be generated according to the importance of the medical information. That is, when the medical data body is transmitted, the inquiry history information management medical block is generated, but when the prescription information is transmitted, the inquiry history information management medical block may not be generated. Accordingly, two conflicting objective indicators such as inquiry history management and traffic can be achieved.

Furthermore, although not described above, the medical data body of the third medical block may be replaced with simple indication information. For example, the hash value of the first medical block (the 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. Accordingly, the data amount of the medical data body of the third medical block can be significantly reduced.

As described above, the present invention has been described in detail using preferred embodiments, but the scope of the present invention is not limited to specific embodiments, and should be interpreted by the appended claims. In addition, those skilled 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 specific patient, medical data headers containing information about medical data producers or requesters, medical data bodies containing medical data, and prescription information including information about prescriptions Communication unit;
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 a second medical block body, wherein the first medical block body and the second An encryption unit that encrypts the encryption difficulty by varying the encryption difficulty 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,
Generating a first medical block header for the first medical block body and a second medical block header for the second medical block body,
The header of one of the first and second medical block headers includes a previous block hash value, a medical blockchain system. According to claim 1,
When the communication unit receives medical data among the medical information from the medical data request terminal, 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 consisting of a medical data head including the patient information and information about the requester requesting the medical data, and encrypts the medical blockchain system. . According to claim 3,
The third medical block body, a medical blockchain system further comprising a medical data body containing the medical data. According to claim 3,
The encryption unit, a medical blockchain system for generating a third medical block header for the third medical block body. According to claim 3,
The storage unit, if the medical information request from the medical data request terminal is authenticated, the medical block chain system for the encryption unit generates the third medical block body. According to claim 3,
The medical data head of the first medical block body includes information on the creator who generated the medical data,
The medical data head of the third medical block body further includes information about a requester requesting the medical data, in addition to information about a creator of the first medical block body.

Images