KR102279377B1 - Medical information providing system with enhanced personal authority using blockchain - Google Patents

Abstract

The present invention relates to a medical information providing system based on personal authority using blockchain, which comprises: first user terminals transmitting diagnosis request information; a medical institution terminal encrypting and transmitting medical information on each of a plurality of patients included in the diagnosis request information received from the first user terminals; a data management server distributing the encrypted medical information on the plurality of patients to a first blockchain; a user management server distributing an identification key and a public key on each of the first user terminals to a second blockchain; blockchain nodes which configure the first blockchain and the second blockchain; and a second user terminal which requests for the information matched based on one or more of patient identifier, medical institution identifier, and disease information to the data management server, and when there is matched information, receives a reading permit from a terminal of a target user who is the target for the matched information among the first user terminals, and receives the matched information stored in the first blockchain from the data management server. The present invention aims to provide a medical information providing system based on personal authority using blockchain, which is able to achieve the effects of integrity and personal information security based on blockchain.

Description

Medical information provision system based on personal authority using blockchain {MEDICAL INFORMATION PROVIDING SYSTEM WITH ENHANCED PERSONAL AUTHORITY USING BLOCKCHAIN}

The technology to be described below relates to a system for providing medical information to a person who wants to read or use medical information using a block chain.

Personal medical information is generated and accumulated by medical institutions and individuals. The hospital manages medical information and clinical information about patients in an Electronic Medical Record (EMR) system. Individuals also use wearable devices and IoT devices to store and manage their health information or clinical information in personal devices and servers.

On the other hand, a decentralized system called blockchain has recently been attracting attention. The blockchain network guarantees the integrity of data, and various applications applying the blockchain are being studied.

PCT application WO2019/032089

Medical information is information required by various entities, such as individuals who want treatment for a specific disease, medical staff who want information for treatment, researchers for disease research, national institutions for medical expenses processing, and insurance companies for processing expenses under personal insurance. . Blockchain basically utilizes a method of opening data to all users. Therefore, blockchain is not suitable as a platform for providing personal information such as medical information. In addition, in blockchain, it is difficult to implement dynamic information disclosure according to individual authority settings.

The technology to be described below is intended to provide a system in which an individual can disclose his/her medical information to a specific target and to a specific scope. The technology described below intends to provide medical information to various entities such as individuals, medical institutions, and service companies who are permitted to use medical information.

A personal authority-based medical information providing system using a block chain provides medical information for each of the first user terminals that transmit the treatment request information and the plurality of patients included in the treatment request information received from the first user terminals. A medical institution terminal that encrypts and transmits, a data management server that distributes encrypted medical information about the plurality of patients to a first block chain, and an identification key and public key for each of the first user terminals in a second block chain A user management server that distributes, block chain nodes constituting the first block chain and the second block chain, and matching information based on at least one of patient identifier, medical institution identifier, and disease information to the data management server request, and if there is matching information, receive permission to read from the terminal of the target user, which is the source of the matching information among the first user terminals, and retrieve the matching information stored in the first block chain from the data management server and a second user terminal for receiving.

The technology described below provides medical information with guaranteed integrity to various entities who want to utilize medical information. The technology described below achieves the effect of personal information security with integrity based on blockchain. Furthermore, the technology to be described below can help a specific individual to select a medical institution by checking the medical information and health status of others for a specific disease.

1 is an example of a medical information providing system using a block chain.
2 is an example of a process of registering user information.
3 is an example of a process of providing medical information.
4 is an example of a medical information utilization contract process.
5 is an example of a process in which a specific subject receives information on a specific disease.
6 is an example of a drug prescription process for a patient.

The technology to be described below may have various changes and may have various embodiments, and specific embodiments will be illustrated in the drawings and described in detail. However, this is not intended to limit the technology described below to specific embodiments, and it should be understood to include all changes, equivalents, or substitutes included in the spirit and scope of the technology described below.

Terms such as first, second, A, and B may be used to describe various components, but the components are not limited by the above terms, and only for the purpose of distinguishing one component from other components. used only as For example, a first component may be named as a second component, and similarly, a second component may also be referred to as a first component without departing from the scope of the technology to be described below. and/or includes a combination of a plurality of related listed items or any of a plurality of related listed items.

In terms of terms used herein, the singular expression should be understood to include the plural expression unless the context clearly dictates otherwise, and terms such as "comprises" refer to the described feature, number, step, operation, element. , parts or combinations thereof are to be understood, but not to exclude the possibility of the presence or addition of one or more other features or numbers, step operation components, parts or combinations thereof.

Prior to a detailed description of the drawings, it is intended to clarify that the classification of the constituent parts in the present specification is merely a division according to the main function that each constituent unit is responsible for. That is, two or more components to be described below may be combined into one component, or one component may be divided into two or more for each more subdivided function. In addition, each of the constituent units to be described below may additionally perform some or all of the functions of the other constituent units in addition to the main function it is responsible for, and may additionally perform some or all of the functions of the other constituent units. Of course, it may be carried out by being dedicated to it.

In addition, in performing the method or the method of operation, each process constituting the method may occur differently from the specified order unless a specific order is clearly described in context. That is, each process may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the reverse order.

The medical information may include various information about the patient. The medical information may include an identifier of a specific patient, an identifier of a medical institution that has treated the patient, and clinical information of the patient.

Clinical information may include various items such as biometric information, medical treatment information, and prescription information about an individual (patient). For example, clinical information includes individual body information (age, gender, race, height, weight, etc.), examination information (blood test results, X-ray images, CT images, MRI images, electrocardiograms, genomic analysis results, etc.), diagnosis Outcomes (health status, outbreak information, etc.) may be included. Furthermore, the clinical information may include accumulating health status information over time for the patient. Accordingly, clinical information may also include a patient's survival period and cause of death.

A user terminal or terminal is a computer device and refers to a client device used by a specific user. A user refers to a specific entity such as a person or an institution, but in the system, a user refers to a user terminal.

The computer device refers to a device that analyzes input source data using an arithmetic device such as a CPU or an AP. A computer device generally includes an arithmetic unit, a memory, an input/output device, a communication interface device, and the like. The computer device may be implemented as a device such as a server, PC, tablet PC, smart phone, or the like.

Blockchain refers to a chain-type, link-based distributed data storage environment in which small data called 'blocks' are created based on the P2P method. Blockchain can be divided into public block chain, consortium block chain, and private block chain according to the type of disclosure. The technology described below can be implemented in various blockchains regardless of the type of disclosure. A blockchain can be composed of an on-chain where the main transaction occurs and an off-chain that is not a mail blockchain.

A blockchain consists of multiple blockchain nodes. A blockchain node can be composed of a combination of various devices such as servers, personal terminals, IoT devices, and the like.

A hash key is a value used to identify a user in the blockchain. It can be created in a variety of ways. Representative hash generation algorithms include MD5 and SHA-256. It is a value that exists uniquely for a specific user. A key consisting of strings of varying lengths to decrypt.

In a blockchain, data can be encrypted and stored. Various encryption methods are applicable. Hereinafter, a public key encryption method as a representative encryption method will be mainly described. A public key and a private key are keys used in public key encryption. The public key is a key that encrypts data, and the private key is a key that decrypts the encrypted data. A public key and a private key are paired with each other and can be randomly generated using various public key encryption methods (eg, RSA, elliptic curve cryptography, etc.).

1 is an example of a medical information providing system 100 using a block chain.

The system 100 may be accessed by terminals used by various subjects.

The first user terminal 111 is a terminal of a patient who wants medical treatment. 1 illustrates one user terminal, a plurality of first user terminals may exist. Hereinafter, the first user is defined as an individual patient who has received treatment and prescription.

The personal terminal 121 is a terminal of an individual who wants to check medical information of a patient who has received treatment. The personal terminal 121 is a terminal of an individual who wants to check a prescription for a specific disease, a medical institution's action for a specific disease, a patient survival rate at a specific medical institution, and a specific medical-based medical accident.

The medical institution terminal 122 is a terminal of a medical institution that accepts a patient's request for treatment and treats the patient. The medical institution terminal 122 transmits medical information about the patient. Furthermore, the medical institution terminal 122 may request information about a patient treated at another institution. That is, a specific medical institution can inquire information about a patient transferred from another medical institution.

The pharmacist terminal 123 is a pharmacist's terminal that prepares and provides medicines according to a prescription of a medical institution. The pharmacist terminal 123 provides medicines according to the prescription information of the medical institution, and transmits information related to the prescription.

The insurance company terminal 124 is a terminal used by the insurance company. The insurance company terminal 124 may request medical treatment information and prescription information for a specific patient. The insurance company terminal 124 may request overall medical information for a patient group of a specific disease. Through this, insurance companies can analyze insurance products considering the cost and survival period of patient care.

The research institution terminal 125 is a terminal of a research institution researching medical information. The research institution terminal 125 may request medical information about a specific patient or a specific disease.

As described above, the first user terminal 111 is a terminal of a patient receiving treatment and prescription. The medical institution terminal 122 is basically a terminal that provides medical information about a patient. Furthermore, the medical institution terminal 122 may be a terminal requesting medical information of a patient. Accordingly, the personal terminal 121 , the medical institution terminal 122 , the pharmacist terminal 123 , the insurance company terminal 124 , and the research institution terminal 125 are common in that they are terminals that request medical information for a specific patient or disease. . Hereinafter, a user requesting medical information is referred to as a second user. The second user terminal may include at least one of a personal terminal 121 , a medical institution terminal 122 , a pharmacist terminal 123 , an insurance company terminal 124 , and a research institution terminal 125 .

The user management server 151 provides medical information through the system 100 and manages users who request medical information. The user management server 151 generates an identifier (hash) of each user. The user management server 151 distributes each user's hash key and public key to the block chain 180 . The user management server 151 may distribute a hash key and a public key to the first block chain 181 used for storing user information.

The data management server 152 receives medical information from a medical institution terminal. The data management server 152 encrypts the medical information and distributes it to the block chain 180 . The data management server 152 may distribute medical information to the second block chain 182 used for storing medical information. The data management server 152 may transmit the requested medical information to the second user terminal requesting the medical information. The medical information is personal information of the first user. Accordingly, the data management server 152 may provide medical information within a reduced range when the first user permits his/her own medical information to be viewed.

The contract management server 153 manages a contract for generating and viewing medical information. The contract management server 153 may receive a medical treatment request from the first user terminal 111 and generate an initial medical information utilization contract. Thereafter, the contract management server 153 may receive the signed medical information utilization contract from the medical institution terminal 122 . The contract management server 153 distributes the medical information utilization contract to the block chain 180 . The contract management server 153 may distribute the medical information utilization contract to the third block chain 183 used for the purpose of storing the medical information utilization contract.

The second user may request medical information that he/she needs. When the second user requests medical information, the contract management server 153 receives the medical information utilization contract from the block chain 180 and delivers it to the second user, and the second user's signature is attached to the medical information utilization contract. It can be distributed to the blockchain 180 again. In this case, the first user may add information (additional signature) for consenting to the second user's reading and utilization of medical information to the medical information utilization contract. The contract management server 153 may distribute a medical information utilization contract to which all signatures of parties involved in sharing medical information are added to the blockchain 180 .

The data management server 152 may transmit related medical information to another user when all parties agree (sign) the medical information utilization contract.

1 illustrates an example of a path of information delivery in which the first user terminal 111 and the insurance company terminal 124 create a medical information utilization contract, and the insurance company terminal 124 receives the medical information.

The block chain 180 can manage user information, medical information, and medical information utilization contract with one block chain. Alternatively, as shown in FIG. 1, an individual block chain may be utilized according to the type of data to be managed.

Furthermore, the blockchain can be composed of on-chain and off-chain. In this case, information stored in on-chain and off-chain may be classified according to the type of information or the security level of the information. For example, the on-chain may store information with a low security level among medical information. On-chain can store an individual's identifier and basic clinical information of an individual (age, gender, age, etc.). Off-chain can store high-security information among medical information. Off-chain can store medical information, disease information, test results, prescription information, etc. Alternatively, in some cases, the system 100 may manage by providing a separate server for storing information requiring security.

2 is an example of a process 200 of registering user information. 2 is an example in which the user management server 151 registers information of each user. The first user and the medical institution must register as a user before generating medical information. The second user must register as a user before requesting medical information.

The first user terminal 111 may generate a user public key (Pu _k ) and a private key (Pr _k ) ( 201 ). The public key is used to encrypt certain data (user information, medical information, contract, etc.), and the private key is used to decrypt the data.

The first user terminal 111 transmits its public key (Pu _k ) together with its user information (PI) to the user management server 151 (202). _{The user management server 151 generates a hash key (H k} ) for the user based on the user information (PI) ( 211 ). The hash key (H _k ) is currently used as an identifier for the user (terminal) who has requested the hash key. Therefore, the hash key (H _k ) corresponds to user-specific unique information. _{The user management server 151 generates a hash key (H k} ) by inputting the input user information (PI) into a predetermined hash function. Algorithms or hash functions for generating hashes may vary. The user management server 151 transmits the generated hash key (H _k ) to the first user terminal 111 requesting the hash key ( 212 ). The first user terminal 111 stores the user public key (Pu _k ), the private key (Pr _k ) and the hash key (H _k ) in the storage medium ( 213 ).

The user management server 151 generates the encrypted user information PI' by encrypting the user information PI using the _{user public key Pu k (221).} The user management server 151 generates user block data by combining the encrypted user information (PI'), the user public key (Pu _k ), and the hash key (H _{k ) ( 222 ).}

The user management server 151 distributes the generated user block data to the first block chain 181 (231). The first block chain 181 stores user block data including encrypted user information (PI'), a user public key (Pu _k ), and a hash key (H _{k ) ( 232 ).}

In addition, the second user terminals 121 to 125 must also register user information in advance.

The second user terminals 121 to 125 may generate a user public key (Pu _k ) and a private key (Pr _k ) ( 251 ). The public key is used to encrypt certain data (user information, medical information, contract, etc.), and the private key is used to decrypt the data.

The second user terminals 121 to 125 transmit their public key Pu2 _k together with their user information PI to the user management server 151 ( 252 ). _{The user management server 151 generates a hash key H2 k} for the user based on the user information PI2 ( 261 ). The hash key (H2 _k ) is currently used as an identifier for the user (terminal) who has requested the hash key. Therefore, the hash key (H2 _k ) corresponds to user-specific unique information. The user management server 151 transmits the generated hash key H2 _k to the second user terminals 121 to 125 that have requested the hash key ( 262 ). The second user terminals 121 to 125 store the user public key (Pu2 _k ), the _{private key (Pr2 k} ), and the hash key (H2 _k ) in a storage medium ( 263 ).

The user management server 151 _{encrypts the user information PI2 using the user public key Pu2 k} to generate the encrypted user information PI2' ( 271 ). The user management server 151 generates user block data by combining the encrypted user information (PI2'), the user public key (Pu2 _k ), and the hash key (H2 _{k ) ( 272 ).}

The user management server 151 distributes the generated user block data to the first block chain 181 (281). The first block chain 181 stores user block data including encrypted user information (PI2'), a user public key (Pu2 _k ), and a hash key (H2 _{k ) ( 282 ).}

Meanwhile, the user terminal or user management server 151 may compare the reference block data stored in the first block chain 181 with the same block data registered in the user management server 151 to confirm whether user information has been changed.

3 is an example of a process 300 of providing medical information. FIG. 3 shows that the first user requests treatment to a medical institution, and the medical institution accepts the treatment. In this process, the first user terminal 111 and the medical institution terminal 122 approve the provision and sharing of medical information ( 301 ). This process may be performed through a process in which the first user terminal 111 and the medical institution terminal 122 sign a medical information utilization contract, as will be described later with reference to FIG. 4 .

The medical institution terminal 122 generates medical information M1 for the first user ( 311 ). The medical information may include medical treatment information about the first user, medical treatment results, disease information, prescription information, progress status, and the like. The medical institution terminal 122 transmits the medical information M1 to the data management server 152 (312).

The data management server 152 queries the first block chain 181 for the hash value of the first user terminal _{to receive the public key P1u k} of the first user ( 321 ).

The data management server 152 _{encrypts the medical information M1 with P1u k} to generate M1' (331). The data management server 152 distributes the generated M1' to the second block chain 182 (332). The second block chain 182 stores M1' (333). In this case, the data management server 152 may distribute M1' together with the identifier (hash value) of the first user to the second block chain 182 ( 332 ).

The second user terminal 121 wants to view the medical information of the first user. 3 illustrates the personal terminal 121 of FIG. 1 as an example of the second user terminal 121, other terminals 122 to 125 may receive medical information through the same process.

In this case, the second user must obtain approval from the first user who has the right to read medical information. The second user terminal 121 performs a medical information provision approval process with the first user terminal 111 ( 341 ). The data management server 152 receives the result of the medical information approval process between the first user and the second user. This process may be performed through a process in which the first user terminal 111 and the second user terminal 121 sign a medical information utilization contract, as will be described later with reference to FIG. 4 .

Meanwhile, the data management server 152 may acquire the secret key of the first user terminal 111 in the medical information provision approval process 341 . The data management server 152 requests a secret key from the first user terminal 111 , and the first user terminal 111 encrypts its private key with the public key of the data management server 152 to the data management server 152 . ) can be sent to The data management server 152 may obtain _{the secret key P1r k} of the first user terminal 111 by decrypting the received secret key with its own private key. Meanwhile, the data management server 152 may _{retain the secret key P1r k} only for a certain period of time, and delete the _{secret key P1r k} when the set time expires.

The second user terminal 121 requests the data management server 152 to provide medical information of the first user ( S351 ). This request may include the hash value of the second user terminal 121 stored in the first block chain 181 and information about the medical information of interest.

The data management server 152 searches whether there is medical information matching the requested medical information ( 352 ). If the request delivered by the second user terminal 121 includes a hash value of a specific user, the data management server 152 queries the second block chain 182 for the received hash value to receive the medical information immediately. may be However, if there is only specific disease information (identifier of disease) in the request transmitted by the second user terminal 121 , the data management server 152 must check whether there is medical information on the same disease as the requested disease. To this end, the data management server 152 may maintain a table for checking whether specific medical information is in the second block chain 182 . For example, the data management server 152 may manage a table for storing the existence of data and a storage location (a hash value of a block) of data according to the type of disease. The data management server 152 may search a table for a specific disease D1 requested by the second user terminal 121 to determine a location in which information on D1 is stored.

When the medical information requested by the second user terminal 121 is in the second block chain 182, the data management server 152 queries the first block chain 181 for the hash value of the second user terminal to obtain a second The user's public key (P2u _k ) is received (361). In addition, the data management server 152 receives from the second block chain 182 medical information matching the medical information requested by the second user terminal 121 from the above table ( 371 ). The data management server 152 may receive medical information by querying a location where the corresponding information is stored. The data management server 152 receives the encrypted data M1'.

The data management server 152 decrypts M1' with the first user's private key P1r _k to generate M1, and again encrypts the medical information M1 with the second user's public key P2u _k to generate M1'' (381). ). The data management server 152 transmits the generated M1'' to the second user terminal 121 (382). The second user terminal 121 decrypts M1'' with its private key to obtain M1 (391).

Meanwhile, the second user may request medical information that meets a specific condition based on the type of disease, the patient's identifier, the medical institution's identifier, or the type of medical information. Types of medical information include anatomical region (kidney, brain, lung, lumbar spine, etc.), data type (image data, questionnaire data, blood test data, genomic data, etc.), phase, patient group information (gender, age group, race, etc.) etc.) and the like. Accordingly, the data management server 152 may manage a table as shown in Table 1 below.

Item identifier storage location user hash value
disease D1 #595934 adggd35 D2 #571855 gdgoom ... ... ...
patient P1 #571855 12gdgd4 P2 #012550 adggd35 ... ... ...
medical institution H1 #912004 12gdegg H2 #571855 2151dgg ... ... ...
Types of medical information T1 #571855 adggd35 T2 #012550 ft5gdff ... ... ...

The data management server 152 refers to a table as shown in Table 1, and blocks corresponding information based on at least one of a disease type, a patient identifier, a medical institution identifier, and a medical information type included in the second user's request. You can find the location (hash value) of . Also, the data management server 152 may search for a hash value of the user (the first user) who provided matching medical information. The data management server 152 may obtain the public key of the first user from the first block chain by querying the hash value.

Generation of transferred medical information and provision of medical information may be performed through a contract between the parties. 4 is an example of a medical information utilization contract process 400 .

The first user terminal 111 requests a medical treatment to a specific medical institution through the contract management server 153 ( 401 ). In this case, the first user terminal 111 may encrypt and transmit its own hash value and its private key generated in the user registration process.

The contract management server 153 generates a medical information utilization contract C1 (simply referred to as a utilization contract) ( 411 ). The utilization contract is an electronic contract.

_{The contract management server 153 receives the first user's public key (P1u k} ) by querying the first block chain 181 for the hash value of the first user terminal ( 412 ). The contract management server 153 _{encrypts the utilization contract C1 with P1u k} to generate C1' (421). The contract management server 153 distributes the generated C1' to the third block chain 184 (422). The third block chain 183 stores C1' (423). At this time, the contract management server 153 may distribute C1' together with the identifier (hash value) of the first user to the third block chain 183 (422).

The contract management server 153 transmits the medical treatment request of the first user terminal 111 to the medical institution terminal 122 ( 431 ). The medical institution terminal 122 transmits the approval for the medical treatment request to the contract management server 153 ( 432 ). In this case, the medical institution terminal 122 may also transmit its own hash value.

The contract management server 153 receives C1' from the third block chain 183 (441). The contract management server 153 may receive C1' by querying the hash value of the first user terminal 111 . Alternatively, the contract management server 153 may be in a state where C1' generated in step 421 is temporarily stored. _{The contract management server 153 may receive the public key P2u k} of the medical institution terminal 122 from the first block chain 181 by querying the hash value of the medical institution terminal 122 ( 442 ).

Contract management server 153 is a first user and a secret key C1 the terminal 111, the decoding and re-encrypted by the utilization contract C1 C1 to P2u _k "generate" 443. The contract management server 153 transmits the generated C1'' to the medical institution terminal 122 (451). The medical institution terminal 122 decrypts C1'' with its private key, and adds its signature to the decrypted C1 (C1+a). The medical institution terminal 122 transmits the signed use contract C1+a to the contract management server 153 ( 453 ). In this case, the medical institution terminal 122 may encrypt and transmit C1+a with the public key of the contract management server, and in this case, the contract management server 153 may decrypt C1+a with its private key.

The contract management server 153 _{encrypts C1+a with the public key P1u k} of the first user (C(1+a)' generated), 454). The contract management server 153 distributes C(1+a)' to the third block chain 184 (461), and the third block chain 183 stores C(1+a)' (462). In this case, the contract management server 153 may distribute C(1+a)' together with the identifier (hash value) of the first user to the third block chain 183 ( 461 ).

Thereafter, another second user terminal 121 may request utilization of medical information for the first user. In this case, the second user must obtain approval from the first user who has the right to read medical information. The second user terminal 121 performs a medical information provision approval process with the first user terminal 111 ( 471 ). The contract management server 153 receives the result of the medical information approval process between the first user and the second user. The contract management server 153 may acquire the secret key of the first user terminal 111 in this process.

The second user terminal 121 requests the data management server 152 to utilize the medical information of the first user ( S481 ). This request may include the hash value of the second user terminal 121 stored in the first block chain 181 and information about the medical information of interest.

The contract management server 153 queries the first block chain 181 for the hash value of the second user terminal _{to receive the public key P3u k} of the second user ( 482 ). The contract management server 153 receives the utilization contract C(1+a)' for the first user from the third block chain 183 ( 483 ). The data management server 152 decrypts _{C(1+a)' with the private key P1r k} of the first user to generate C(1+a), and again C(1+ with _{the public key P2u k of the second user)} a) is encrypted to generate C(1+a)'' (484). The contract management server 153 transmits the generated C(1+a)'' to the second user terminal 121 (485). The second user terminal 121 decrypts C(1+a)'' with its private key to obtain C(1+a) ( 491 ). The second user terminal 121 generates C(1+a+b) by adding its own signature to the utilization contract ( 491 ). The second user terminal 121 transmits C (1 + a + b) to the contract management server 153 (492),

The contract management server 153 encrypts _{C(1+a+b) with the public key P1r k} of the first user to generate C(1+a+b)' (493). The contract management server 153 distributes C(1+a+b)' to the third block chain 183 . The third block chain 183 stores C(1+a+b)' ( 495 ).

As described in FIG. 4 , when information is transmitted to the first user ⇒ medical institution ⇒ second user, a utilization contract with each user's signature added is created and distributed on the blockchain. A user with a signature added to the usage agreement can be said to have been approved to view the relevant medical information.

The data management server 152 may check the utilization contract stored in the third block chain 183 to confirm whether the person currently requesting medical information is the person who has been approved for reading.

In addition, the first user may check the utilization contract (encrypted with the public key of the first user) stored in the third block chain 183 to determine the history to whom the medical information has been disclosed to what extent.

Meanwhile, the first user terminal 111 may approve disclosure of only a specific item of medical information while making a medical information utilization contract. In addition, the first user terminal 111 may approve disclosure of medical information only during a specific period. The first user terminal 111 may approve disclosure of a specific item of medical information for a specific second user for a specific period. Accordingly, the first user terminal 111 may set the disclosure range and disclosure period by different contract conditions for each second user. The specific item may be determined based on the type of disease, the identifier of the medical period, the data generation time, whether the data can be disclosed to a third party, etc.

5 is an example of a process in which a specific subject receives information on a specific disease.

The second user 120 requests specific medical information from the data management server 152 through his/her terminal (①). The second user may be various, such as an individual (patient, patient's family, etc.), a medical institution, an insurance company, a research institution, a pharmacist, and the like.

The data management server 152 searches in advance whether the medical information requested by the second user is in the block chain by referring to the information (table) it owns (②).

When the medical information requested by the second user is in the block chain, the data management server 152 checks whether reading of the medical information for the second user is approved (③). The data management server 152 may perform a protocol for confirming whether to approve the first user terminal 111 . Alternatively, the data management server 152 may check whether the second user is a person authorized to read the medical information of the first user through the contract management server 153 or directly by checking the utilization contract stored in the block chain 180 .

When the second user is a person whose medical information reading of the first user is approved, the data management server 152 extracts the approved medical information from the block chain 180 (④). The data management server 152 may select only the information within the range requested by the second user or the range approved by the first user among the medical information received from the block chain 180 . The data management server 152 provides the medical information received from the block chain 180 or the medical information selected based on additional criteria to the second user 180 (⑤).

The second user 180 utilizes the medical information according to the purpose of using the medical information (⑥). For example, (i) the second user 180, who is a patient, may check other patient's medical information for a disease in which he or she is interested. The second user 180 may check at least one of medical institution identification information, drug prescription information, patient health status information, patient survival period, and cause of death included in the medical information. Through this, the second user 180 may select an appropriate treatment method or medical institution for treating a disease of interest. (ii) The second user 180, which is a medical institution, may obtain information about a patient who has been treated at another hospital, and check the previous treatment result and progress in order to continuously treat the patient. (iii) The second user 180, which is a research institution, may collect medical information on a specific patient or a group of patients with a specific disease to conduct research on the disease. (iv) The second user 180, which is an insurance company, may collect medical information on a specific patient or a group of patients with a specific disease to check the medical treatment claimed by the insurance company, and check the cost to be borne by the insurance company. (v) The second user 180, who is a pharmacist, may check prescription details for a specific patient and dispense and provide medicines.

6 is an example of a drug prescription process 500 for a patient.

The medical institution terminal 122 requests a drug prescription through the contract management server 153 (501). It is assumed that the contract management server 153 knows the hash value of the first user through the previous medical request of the first user. The contract management server 153 generates a prescription contract C2 ( 511 ). The prescription contract is an electronic contract.

The contract management server 153 queries the first block chain 181 for the hash value of the first user terminal _{to receive the public key P1u k} of the first user (512). The contract management server 153 _{encrypts the utilization contract C2 with P1u k} to generate C2' (521). The contract management server 153 distributes the generated C2' to the third block chain 184 (522). The third block chain 183 stores C2' (523). In this case, the contract management server 153 may distribute C2' together with the identifier (hash value) of the first user to the third block chain 183 ( 522 ).

The medical institution terminal 122 or the contract management server 153 transmits a prescription request from the medical institution to the pharmacist terminal 123 ( 531 ). The pharmacist terminal 123 transmits the approval for the prescription request to the contract management server 153 ( 532 ). In this case, the pharmacist terminal 123 may also transmit its own hash value.

The contract management server 153 receives C2' from the third block chain 183 (541). The contract management server 153 may receive C2' by querying the hash value of the first user terminal 111 . Alternatively, the contract management server 153 may be in a state where C2' generated in step 521 is temporarily stored. _{The contract management server 153 may receive the public key P4u k} of the pharmacist terminal 122 from the first block chain 181 by querying the hash value of the pharmacist terminal 123 ( 542 ).

Contract management server 153 is a first user and a secret key C2 of the terminal 111, the decoded and re-encrypted C2 utilization contract C2 to P4u _k "generate" 543. The contract management server 153 transmits the generated C2'' to the pharmacist terminal 123 (551). The pharmacist terminal 123 decrypts C2'' with its private key, and adds its signature to the decrypted C2 (C2+d). The pharmacist terminal 123 transmits the signed prescription contract C2+d to the contract management server 153 (561). In this case, the pharmacist terminal 123 may encrypt and transmit C2+d with the public key of the contract management server, and in this case, the contract management server 153 may decrypt C2+d with its private key.

The contract management server 153 _{encrypts C2+d with the public key P1u k} of the first user (C(2+d)' generated), 562). The contract management server 153 distributes C(2+d)' to the third block chain 184 ( 563 ) The third block chain 183 stores C(2+d)' ( 564 ). At this time, the contract management server 153 may distribute C(2+d)' together with the identifier (hash value) of the first user to the third block chain 183 ( 563 ).

Thereafter, the first user terminal 111 may request confirmation of the prescription contract from the contract management server 153 ( 571 ). The contract management server 153 may transmit C(2+d)' received from the third block chain 183 to the first user terminal 111 ( 572 ). The first user terminal 111 may determine C(2+d) by decrypting the prescription contract C(2+d)' encrypted with its private key (574).

Meanwhile, the insurance company terminal 124 may also request confirmation of the prescription contract from the contract management server 153 ( 581 ). In this case, the insurance company terminal 124 may transmit its hash key together.

The contract management server 153 receives C(2+d)' from the third block chain 183 ( 582 ). _{The contract management server 153 may receive the public key P5u k} of the insurance company terminal 124 from the first block chain 181 by querying the hash value of the insurance company terminal 124 ( 583 ).

The contract management server 153 decrypts C(2+d)' with the secret key of the first user terminal 111, and encrypts the utilization contract C(2+d) with _{P5u k again to C(2+d)'} ' is created (591). The contract management server 153 transmits the generated C(2+d)'' to the insurance company terminal 124 (591). The insurance company terminal 124 may decrypt C(2+d)'' with its private key, and confirm the decrypted prescription contract (593). The insurer can check the prescription contract to determine what the insurer pays for the prescription drug.

Meanwhile, the National Health Insurance Corporation, a national institution, can use a separate terminal to check prescription contracts like insurance companies. The Health Insurance Corporation can determine the state's contribution to prescription drugs by checking the prescription contract.

In addition, the medical information providing method and the medical information utilization contract method as described above may be implemented as a program (or application) including an executable algorithm that can be executed in a computer. The program may be provided by being stored in a temporary or non-transitory computer readable medium.

The non-transitory readable medium refers to a medium that stores data semi-permanently, rather than a medium that stores data for a short moment, such as a register, cache, memory, etc., and can be read by a device. Specifically, the various applications or programs described above are CD, DVD, hard disk, Blu-ray disk, USB, memory card, ROM (read-only memory), PROM (programmable read only memory), EPROM (Erasable PROM, EPROM) Alternatively, it may be provided by being stored in a non-transitory readable medium such as an Electrically EPROM (EEPROM) or a flash memory.

Temporarily readable media include Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (Enhanced) SDRAM, ESDRAM), Synchronous DRAM (Synclink DRAM, SLDRAM) and Direct Rambus RAM (Direct Rambus RAM, DRRAM) refers to a variety of RAM.

This embodiment and the drawings attached to this specification merely clearly show a part of the technical idea included in the above-described technology, and within the scope of the technical idea included in the specification and drawings of the above-described technology, those skilled in the art can easily It will be apparent that all inferred modified examples and specific embodiments are included in the scope of the above-described technology.

Claims (14)

a first user terminal for transmitting treatment request information;
a medical institution terminal that encrypts and transmits medical information on a patient included in the medical request information received from the first user terminal, and transmits a prescription request for the patient;
a pharmacist terminal for receiving the prescription request and transmitting a prescription contract request for the prescription request;
an insurance company terminal requesting confirmation of the prescription request;
a first block chain for storing a first public key for the first user terminal, a second public key for the pharmacist terminal, and a third public key for the insurance company terminal;
a second block chain for storing encrypted medical information about the patient;
a third blockchain that stores encrypted prescription contracts;
generating a prescription contract upon receiving the prescription request from the medical institution terminal, encrypting the prescription contract using the first public key obtained from the first blockchain, and distributing it to the third blockchain; Upon receiving a prescription contract request from the pharmacist terminal, the prescription contract is decrypted with the secret key of the first user terminal and transmitted to the pharmacist terminal, and when a prescription contract with a signature is received from the pharmacist terminal, the first public key a contract management server for distributing an encrypted prescription contract to the third block chain; and
a data management server that distributes encrypted medical information about the patient to the second block chain;
a user management server distributing the first public key, the second public key, and the third public key to the first block chain;
The contract management server (i) when receiving a prescription contract confirmation request from the first user terminal, transmits the prescription contract encrypted with the first public key from the third block chain to the first user terminal, (ii) Upon receiving the prescription contract confirmation request from the insurance company terminal, the prescription contract encrypted with the first public key is received from the third block chain, decrypted with the private key of the first user terminal, and the decrypted prescription contract is converted into a first block encrypted with the third public key obtained from the chain and transmitted to the insurance company terminal;
Requests matching information to the data management server based on at least one of a patient identifier, a medical institution identifier, and disease information, and when there is matching information, receives a reading permission from the first user terminal, and from the data management server A second user terminal for receiving the matching information stored in the second block chain,
The insurance company terminal receives the prescription contract encrypted with the third public key, decrypts the prescription contract with its own private key, and checks the prescription to check the insurance company or the state's contribution,
The medical information includes a user identifier, a medical institution identifier, clinical information, and drug prescription information for each patient,
The clinical information is a personal authority-based medical information providing system using a block chain including at least one of a diagnosis result, disease information, examination information, health status information over time, survival period, and cause of death for a patient. According to claim 1,
The medical institution terminal uses a public key for the first user terminal stored in the first block chain to encrypt medical information for the first user terminals. A personal authority-based medical information providing system using a block chain. According to claim 1,
The data management server
When the first user terminal permits the reading of medical information of the second user terminal, the encrypted medical information of the first user terminal is received from the second block chain,
Personal authority-based medical care using a block chain that decrypts the encrypted medical information with the private key of the first user terminal, encrypts the decrypted medical information again with the public key of the second user terminal, and transmits it to the second user terminal Information provision system. 4. The method of claim 3,
The second user terminal receives the encrypted medical information about the first user terminal from the data management server, and decrypts the encrypted medical information with the secret key of the second user terminal,
At least one of the medical institution identification information included in the medical information, drug prescription information, the patient's health status information, the patient's survival period, and the cause of death of the patient for a specific disease, a specific patient, or a specific medical institution to be reviewed A personal authority-based medical information provision system using an identifying block chain. 4. The method of claim 3,
The data management server
A personal authority-based medical information providing system using a block chain that encrypts only the items allowed to be viewed by the second user terminal among the medical information of the first user terminal and transmits it to the second user terminal. delete delete delete delete delete According to claim 1,
The second block chain includes an on-chain for storing basic information and an off-chain for storing personal information according to the type of information or the security level of the information, and the personal information is A system for providing medical information based on personal authority using a blockchain including at least one of the clinical information. According to claim 1,
When the data management server receives a request for medical information of the first user terminal from the second user terminal, the data management server transmits the request to the first user terminal, and the access permission and the secret of the first user terminal A personal authority-based medical information provision system using a block chain that receives a key. According to claim 1,
The data management server classifies the disease information among the medical information by type of disease, and stores the location of medical information stored in the second block chain for each type of disease in a table based on personal authority using a block chain. of medical information provision system. 14. The method of claim 13,
The data management server
determining a disease identical to the disease information included in the request of the second user from among the diseases stored in the table;
Personal authority-based medical information using a block chain that extracts a user identifier from a location where the same disease is stored in the second block chain and transmits the second user's request to the first user terminal based on the extracted user identifier delivery system.

Images