KR20200016458A - Blockchain-based phr platform server operating method and phr platform server operating system - Google Patents

Abstract

Disclosed are a blockchain-based PHR platform server management method and a PHR platform server management system. According to an embodiment of the present invention, the blockchain-based PHR platform server management method includes the following steps: collecting a first medical treatment record document written from an EMR terminal, thereby retaining the document in a multi-distributed storage; extracting patient information from the first medical treatment record document, thereby recording the information in a registry as a header for the first medical treatment record document; blocking a storage position value of the first medical treatment record document in the multi-distributed storage and a hash value about the header based on a blockchain core, thereby connecting the values to a blockchain; and searching the blockchain for a block designated by the hash value selected from a header list listing a plurality of hash values in interconnection with the occurrence of an inquiry request, and then, providing a storage position value of the found block to the EMR terminal having created the inquiry request. Therefore, the present invention is capable of safely storing or inquiring into medical treatment records and health data of patients.

Description

Blockchain based PHR platform server operating method and PHR platform server operating system {BLOCKCHAIN-BASED PHR PLATFORM SERVER OPERATING METHOD AND PHR PLATFORM SERVER OPERATING SYSTEM}

The present invention provides a blockchain-based PHR platform server operating method and PHR to securely look up the treatment information from any EMR terminal by maintaining the medical information created and shared in the EMR terminal of the medical institution based on the block chain A platform server operating system.

The present invention allows the EMR terminal set to be opened by the patient to allow the patient's medical information inquiry, thereby enabling the exchange of medical information centered on the patient, block chain based PHR platform server operating method and PHR platform server It is about an operating system.

Currently, medical institutions are allowed to exchange their medical records with other medical institutions on the basis of the government's standard notices.

However, in the existing online medical care information exchange system, medical care information is individually exchanged between medical institutions. For this reason, if any medical institution wants to search all the patient's medical records, it is cumbersome to request each medical institution visited by the patient individually. Records can be difficult to transfer.

In addition, since medical information is exchanged between medical institutions in a state where patients are excluded, it is difficult for a patient to actively select a medical institution to disclose his / her medical information, and there is no method of selecting some medical information to be disclosed.

Accordingly, it is necessary to reorganize existing online medical care exchanges conducted between medical institutions with the exception of patients into medical care exchanges centering on patients.

In addition, in the existing on-line medical information exchange system, the patient's medical records are stored in the central server and base medical institution, and the patient records are included in each medical record. have.

Therefore, it is necessary to reinforce the safety of the online medical care information exchange system by using distributed storage technology.

In addition, in the current medical information exchange system, medical records are encrypted and delivered using an official certificate, so terminals of each medical institution that share or search medical records (eg, PCs with an EMR system) must install an official certificate. There is a hassle to renew the certificate after the expiration date.

Therefore, the medical information exchange system needs to be able to exchange medical information conveniently without the inconvenience of installing and renewing the certificate.

In addition, in the past, patients have to submit their medical records to medical institutions and receive them by mail, etc., or submit them to other medical institutions, insurance companies, or companies that are planning to join companies. Therefore, it is necessary for the patient to easily access all his / her medical records through the health care application being used, and to use the inquiry or the submission of medical records. At this time, it is necessary to allow the patient to designate whether to submit the medical record submission form as the original or hide some items or submit them anonymously.

Accordingly, there is a demand for a technology that enables simple and safe online exchange of medical information created by a large number of medical institutions, centering on patients.

An embodiment of the present invention collects the medical records written about the patient from a plurality of medical institutions to maintain on the blockchain-based PHR platform server, and supports a secure inquiry service of the medical records maintained on the PHR platform server using the blockchain For the purpose of

Embodiment of the present invention by blocking the storage location value of the medical record maintained in the multi-distributed storage to connect to the blockchain, by checking the storage location value of the medical record requested from the block chain to provide to the EMR terminal, It is aimed at ensuring high security in the exchange of medical records between medical institutions.

In addition, an embodiment of the present invention is another object to allow the exchange of medical records between the medical institutions, the patient center by allowing the inquiry of the patient's own medical records only to the EMR terminal set to be open by the patient.

In addition, the embodiment of the present invention maintains various health data (eg, life log, steps, distance, prescription, etc.) of the patient collected through the PHR application of the patient terminal to the blockchain-based PHR platform server, and lookup By providing the patient's health data to the EMR terminal requesting the, it is another object to support the comprehensive understanding of the patient's condition by using the health data.

In addition, an embodiment of the present invention is another object to make it easy to view the patient's own medical records and health data at any time on the PHR application through the inquiry request.

The method for operating a blockchain-based PHR platform server according to an embodiment of the present invention includes collecting first medical record documents created from an EMR terminal and maintaining them in multiple distributed storages, and patient information in the first medical record documents. Extracting and recording the data as a header for the first medical record document in a registry, based on a blockchain core, a storage location value of the first medical record document in the multi-distributed storage, and Blocking hash values, connecting them to the blockchain, and retrieving a block designated by a hash value selected from a header list that lists a plurality of hash values in association with the occurrence of an inquiry request from the blockchain. And providing the storage location value constituting the block to the generated EMR terminal.

According to another embodiment of the present invention, a blockchain-based PHR platform server operating method converts a patient function extracted as a header into a first hash value from patient records extracted as headers from medical records maintained in multiple distributed storages at regular intervals. Generating a header list by listing the first hash value, transmitting the header list created to the EMR terminal generating the inquiry request, and using a selection hash value selected from the header list. Retrieving the selected block from the blockchain, and displaying, on the EMR terminal, a third medical record document identified from the multiple distributed storages by a storage location value included in the block.

In addition, the blockchain-based PHR platform server operating system according to an embodiment of the present invention, collects the first medical record document created from the EMR terminal, and maintains it in multiple distributed storage, the patient information in the first medical record document Extracts a recording unit for recording in the registry as a header for the first medical record document, and a storage location value of the first medical record document in the multi-distributed storage based on a blockchain core, and A block block unit for blocking hash values and connecting them to the block chain, and a block designated by a hash value selected from a header list in which a plurality of hash values are listed in association with occurrence of an inquiry request, searching from the block chain; And a processing unit which provides the storage location value constituting the retrieved block to the EMR terminal which generated the inquiry request.

In addition, the blockchain-based PHR platform server operating system according to another embodiment of the present invention, the first hash value by applying a hash function to the patient information extracted as a header from the medical record document maintained in multiple distributed storage at regular intervals The patient information by using a conversion unit for converting the data into a header, a delivery unit for transmitting the header list created by listing the first hash value to an EMR terminal generating an inquiry request, and a selection hash value selected from the header list. And a processing unit for retrieving a block generated in association with the blockchain, and displaying, on the EMR terminal, a third medical record document identified from the multiple distributed storages by a storage location value included in the block.

According to an embodiment of the present invention, the header and the body constituting the medical record are stored separately in the registry and multiple distributed storage in the PHR platform server, and the storage location value is blocked and connected to the blockchain, thereby providing patient information and Compared with the existing centralized medical information exchange system that keeps medical records together, the risk of information leakage can be greatly reduced, thus maintaining high security.

In addition, according to an embodiment of the present invention, whether or not the forgery of the medical record identified using the storage location value can be easily confirmed by comparing the hash value to which a hash function is applied to each of the header and the body constituting the medical record. .

In addition, according to an embodiment of the present invention, without the need to install a separate certificate for the storage of medical records in the EMR terminal, by utilizing a simple encryption method called blockchain, the patient's medical records and health data safely stored or retrieved can do.

1 is a block diagram showing the configuration of a blockchain-based PHR platform server operating system according to an embodiment of the present invention.
2 is a block diagram showing a blockchain-based PHR platform server operating system according to another embodiment of the present invention.
3 is a diagram illustrating an example of a medical record document in the PHR platform server operating system according to embodiments of the present invention.
4A and 4B are tables showing an example of data fields recorded in a registry in a PHR platform server operating system according to embodiments of the present invention.
5 is a diagram illustrating a process of storing a medical record document in the PHR platform server operating system according to another embodiment of the present invention.
6 is a diagram illustrating a process of providing a medical record document to an EMR terminal according to an inquiry request in a PHR platform server operating system according to another embodiment of the present invention.
7 is a diagram illustrating a process of providing a medical record document to a patient terminal according to an inquiry request in the PHR platform server operating system according to another embodiment of the present invention.
8 is a diagram illustrating a procedure of a blockchain-based PHR platform server operating method according to an embodiment of the present invention.

Hereinafter, exemplary embodiments will be described in detail with reference to the accompanying drawings. However, various changes may be made to the embodiments so that the scope of the patent application is not limited or limited by these embodiments. It is to be understood that all changes, equivalents, and substitutes for the embodiments are included in the scope of rights.

The terminology used herein is for the purpose of description and should not be construed as limiting. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, terms such as "comprise" or "have" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described on the specification, one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art, and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

In addition, in the description with reference to the accompanying drawings, the same components will be given the same reference numerals regardless of the reference numerals and duplicate description thereof will be omitted. In the following description of the embodiment, if it is determined that the detailed description of the related known technology may unnecessarily obscure the gist of the embodiment, the detailed description thereof will be omitted.

Blockchain-based Personal Health Record (PHR) platform server operating system of the present invention, in connection with the EMR of the medical institution, through the PHR application of the patient terminal on the blockchain, inquiry, submission of the PHR information of the patient Can provide services.

Through the PHR application, patients can view PHR information such as information received from medical institutions and lifelogs (health data) such as activity volume, blood pressure, blood sugar, and diet information collected by their smartphones. You can set the visibility of the

1 is a block diagram showing the configuration of a blockchain-based PHR platform server operating system according to an embodiment of the present invention.

Referring to FIG. 1, a blockchain-based PHR platform server operating system 100 according to an embodiment of the present invention may include a recording unit 110, a blocker 120, and a processor 130. . In addition, according to an embodiment, the PHR platform server operating system 100 may include a conversion unit 140, a delivery unit 150, a confirmation unit 160, an output unit 170, a registry 101, and multiple distributed repositories 102. ) Can be added separately.

The recorder 110 collects the first medical record document created from the EMR terminal at regular intervals and maintains it in the multi-distributed storage 102.

In addition, the recording unit 110 extracts the patient information in the first medical record document, and records it in the registry 101 as a header for the first medical record document.

For example, the recorder 110, when a request for storing a medical record document is generated in the EMR terminal, access granted to the medical institution identification information (eg, 'care institution number', 'EMR ID') in the storage request is authenticated. The token may be used to collect the first medical record document transmitted from the EMR terminal.

The recorder 110 records the header in the registry 101 provided separately from the multi-distributed storage 102, and diagnoses the diagnosis, findings, precautions, prescriptions, and tests of the first medical record document except the header. At least one data of the record, the treatment record, the operation record, and the inoculation record may be extracted as a body and maintained in the multiple distributed reservoirs 102. That is, the recording unit 110 may further classify and store the patient information of the collected first medical record document and the actual medical data, thereby further securing the security.

At this time, the recording unit 110 is an index for the first medical record document (body) maintained in the multi-distributed storage 102, and by assigning a new document ID instead of the header of the first medical record document, Even if the distributed storage 102 is all hacked, it is possible to increase the security by not knowing the association between the data held in the multiple distributed storage 102 corresponds to the patient's medical record.

In addition, the recorder 110 divides and maintains the body extracted from the first medical record document in any one of the multi-distributed storage 102 distributed storage randomly, so that even if one distributed storage is hacked, all the medical records of the patient This can be prevented from leaking.

According to an embodiment, the PHR platform server operating system 100 may further include a conversion unit 140.

The conversion unit 140 converts the first hash value by applying a hash function to the header extracted from the first medical record document. In addition, the conversion unit 140 converts the second hash value by applying a hash function to the body extracted from the first medical record document.

The hash function is a function that converts one string into another value or key that symbolizes the string, and may be used to reduce the length of the string or to hide the contents of the string.

The recording unit 110 may record the header and the first hash value in the registry 101 in association with the patient identification key. The patient identification key may be a key value to which a hash function is applied to a string combining patient information.

In this case, the recording unit 110 may block the header through the blocker 120 to be described later without recording the header in the registry 101. In this case, the registry 101 records only the first hash value in association with the patient identification key, and does not store the header (patient information) by itself, thereby increasing security.

In addition, the PHR platform server operating system 100 by blocking the storage location value of the first medical record document (body) maintained in the multi-distributed storage 102 through the blocker 120 to be stored in the block chain, security Can increase.

The blocker 120 blocks and stores the storage location value of the first medical record document and the first hash value of the header in the multi-distributed storage 102 based on the blockchain core and connects the blockchain to the blockchain. .

Here, the storage location value may include the document ID assigned as the first medical record document (that is, the body) is maintained in the multiple distributed storage 102 and the access URL of the distributed storage where the first medical record document is maintained. Can be.

The blocker 120 generates a block including the storage location value, the first hash value of the header, and the second hash value of the body based on a blockchain core, and distributes the generated block to each node. It can be synchronized and connected (added) to the blockchain composed of the second medical records collected in the previous cycle.

In this case, when the header is not maintained in the registry 101 provided separately from the multi-distributed storage 102, the blocker 120 may further include the header to generate the block. In this case, since only the first hash value of the header is recorded in the registry 101, there is no risk of hacking of the header (patient information), thereby improving security.

According to an embodiment, the blocker 120 may use the storage location value as a first data key ('plain data key') of a plurality of data generated using a key management service (KMS) of Amazon Web Service (AWS). And a block including an encrypted storage location value, a second data key ('encrypted data key') to be used for decryption, a first hash value of the header, and a second hash value of the body.

In this case, each EMR terminal can safely and easily store the medical record document based on the blockchain without installing a separate authorized certificate for encryption.

In response to the occurrence of the inquiry request, the processor 130 searches for the block designated by the hash value selected from a header list that lists a plurality of hash values from the block chain, and retrieves a storage location value constituting the retrieved block. It provides the inquiry request to the generated EMR terminal.

For example, the EMR terminal generates an inquiry request including medical institution identification information (eg, 'nursing institution number' and 'EMR ID'), and the processor 130 authenticates the medical institution identification information to provide an access token to the EMR terminal. It can be given. The EMR terminal may request a medical record list of a patient who wants to inquire the medical record document using the access token.

According to an embodiment, the PHR platform server operating system 100 delivers a list of medical records maintained for a specific patient to the EMR terminal that generated the inquiry request, and is not limited to the medical institution that created the medical records. In order to be able to select a medical record document to be searched from the record document, it may be configured to further include a delivery unit 150.

The conversion unit 140 converts the hash value by applying a hash function to the patient information extracted from the second medical record document previously held in the multiple distributed storage 102. In this case, the list of hash values may mean a list of patients.

In this case, the conversion unit 140 may further extract data fields, such as medical institution information and treatment name and creation date and time, which can identify a nursing institution for which the medical record document is created, as a header, and convert the data field into a hash value to which a hash function is applied. . In this case, the list of hash values may mean a list of medical record documents for each patient.

The delivery unit 150 delivers the header list that lists a plurality of hash values to the EMR terminal.

That is, the delivery unit 150 may deliver, as the header list, a list of all medical record documents (first and second medical record documents) of a specific patient maintained in the multi-distributed storage 102 until the inquiry request occurs. have.

The processor 130 retrieves a block including a hash value selected from the header list from the blockchain, and retrieves a medical record document identified from the multi-distributed storage 102 by a storage location value constituting the retrieved block. It can be displayed on the EMR terminal.

In this case, the storage unit 120, the storage location value is encrypted with a first data key of a plurality of data keys generated using a Key Management Service (KMS) of Amazon Web Service (AWS) is included in the block In this case, the processor 130 may provide (return) the storage location value decoded using the second data key of the plurality of data keys, which is further included in the block, to the EMR terminal.

Accordingly, the EMR terminal can access and display the medical record document to be queried in the multiple distributed storage 102 according to the storage location value.

For example, when the medical institution information or form type information in the medical record document is further extracted as the header and converted into a hash value together with the patient information by the conversion unit 140, the processing unit 130 generates the information related to the patient information. Among the blocks, the block further associated with the specific care institution or the specific format according to the selected hash value may be selected, and the storage position value of the medical record document included in the selected block may be provided to the EMR terminal.

Through this, the processor 130 EMR among the medical record documents of the same patient, the medical record document created or sent or received at a specific medical institution selected by the EMR terminal or a medical record document of a specific type (eg, a medical request, etc.) It can be provided to the terminal.

According to an embodiment, the PHR platform server operating system 100 may further include a check unit 160.

Confirmation unit 160 confirms whether the forgery for the medical record document, before displaying to the EMR terminal.

For example, the processor 130 may provide the EMR terminal with the storage location value, the hash value of the body identified from the searched block, and the header identified from the registry 101 or the searched block.

The identification unit 160 checks whether the hash value to which the hash function is applied to the body checked according to the storage location value matches the hash value of the body, and the hash value to which the hash function is applied to the header is determined from the header list. You can check whether it matches the hash value you selected.

The processor 130 may determine that the medical record document combining the header and the body is not forged or tampered with, and display the medical record document on the EMR terminal.

According to an embodiment, the PHR platform server operating system 100 may further configure the output unit 170 so that the patient can designate the EMR terminal or the patient terminal to allow the inquiry of his or her medical records.

The recorder 110 may collect the health data of at least one of the prescription and the life log recorded in the terminal of the patient at regular intervals through a PHR application installed in the terminal of the patient, and may further maintain the multiple data in the distributed storage 102.

As the output unit 170 maintains at least one PHR information among the health data and the medical record document in the multi-distributed storage 102, the output unit 170 sets an EMR terminal or a disclosure range of the PHR information to be released. The interface can be output to a PHR application.

The processor 130, in response to the inquiry request, when the terminal generating the inquiry request is an EMR terminal of a medical institution or a server of a research institute set to be open on the interface by the terminal of the patient, the multi-distributed storage 102 Access to the PHR information may be allowed (for example, inquiry of medical record information or health data, submission of medical record documents, etc.).

For example, if the processor 130 wants to receive PHR information such as a patient's medical record document or health data from a research institute, the research unit converts the medical record document confirmed in the multi-distributed storage 102 into the FHIR form to study the study. Can be transferred to the institution's system.

In addition, the processor 130 may allow access to the PHR information when the inquiry request is generated in the PHR application of the patient set to be public in the interface.

Specifically, the conversion unit 140 converts the patient information input when generating a login account for the PHR application in the terminal of the patient to a hash value by applying a hash function, and the recording unit 110 converts the hash value into the PHR application. Apart from the login account maintained in the app server managing the, it can be maintained on the terminal of the patient. When the inquiry request is received from the terminal of the patient through the PHR application, the processing unit 130 searches for a block from the blockchain using the hash value converted into the patient information as the selected hash value, and searches for the storage location value in the retrieved block. Accordingly, the patient's medical record document identified from the multiple distributed repositories 102 can be displayed in the PHR application.

As described above, according to the present invention, the security value can be improved by maintaining the hash value of the patient's login account and patient information in a separate space, and the terminal of the medical institution, family, or acquaintance designated by the patient's terminal through the PHR application. The patient's medical records or health data can be securely provided to support the exchange of patient-centered medical information.

In addition, the processor 130 checks the storage location value associated with the hash value selected from the header list (list of patient's medical record documents) from the blockchain when the patient terminal is requested to submit the medical record document through the PHR application. By transmitting the body of the electronic record document in the multi-distributed storage 102 identified by the storage location value at the terminal of the patient to an input destination such as another medical institution, insurance company, company to be joined, etc., the submission to the PHR application is completed. Can be informed.

At this time, the processor 130 according to the submission form (for example, the original, hidden some items, anonymous processing) and the form used in the transmission destination set through the PHR application in the terminal of the patient, medical records document / health data (PHR information) Format can be converted to FHIR format and submitted.

Through this, according to the present invention, it is possible to support the exchange of medical information created by a plurality of medical institutions, the various institutions set to be disclosed by the patient, easy and safe and online exchange centering around the patient.

2 is a block diagram showing a blockchain-based PHR platform server operating system according to another embodiment of the present invention.

2, the blockchain-based PHR platform server operating system 200 according to another embodiment of the present invention, the registry server 201, distributed storage server 202, blockchain app server 203, PHR It may be configured to include an app server 204, a registry 205, multiple distributed repositories 206, and a user information DB 207.

The registry server 201 extracts a header from health data such as a form-based medical record document transmitted from the EMR terminal 210 or a life log and a prescription transmitted from the PHR application 220. (205).

Specifically, the registry server 201 records the header and the first hash value converted by applying a hash function to the header in the registry 205 in association with the patient identification key. When searching for maintained medical records or health data, it can serve as an index. The patient identification key may be a key value obtained by applying a hash function to a string including patient information.

According to an embodiment, the header is not recorded in the registry 205, and the header may be blocked by the blockchain app server 203, thereby enhancing security.

The EMR 210 is an EMR system (Electronic Medical Recording System) installed in a terminal of a medical institution, and can create a medical record of a patient based on the contents input by a doctor in charge.

When the registry server 201 is requested to store the medical record document from the EMR 210, the registry server 201 may authenticate the care institution number and the EMR ID of the EMR 210 to grant access rights.

The distributed repository server 202 extracts a body from health data such as a medical record document transmitted from the EMR 210 or a life log and a prescription transmitted through the PHR application 220, and stores multiple distributed repositories ( 206).

In this case, the distributed storage server 202 may be stored in a distributed storage arbitrarily selected among the multiple distributed storages 206, so that all the medical records of the patient may be leaked even if the distributed storage of any one is hacked.

The blockchain app server (BAS) 203 may include a second hash value converted by applying a hash function to a body stored in the multi-distributed storage 206, a storage location value of the body, and the header. The first hash value is blocked using a blockchain core as one transaction (transaction record).

The storage location value may include a document ID generated when the body is stored and a URL of a distributed storage in which the body is stored.

As such, the blockchain app server 203 blocks the entire body and stores the blockchain in the blockchain. Therefore, the blockchain app server 203 blocks the second hash value converted by applying a hash function to the body and stores the blockchain in the blockchain. (Connect), the actual data (body) can be stored in the multiple distributed storage 206 by the distributed storage server 202.

In blockchain, rather than storing transactions in a centralized server, individual servers gather to maintain and manage the network. This individual server, or participant, is called a node.

The node may play a role of generating a block through the blockchain applications 211 and 221 and distributing it to each node, and may record all transaction information of the blockchain network.

For example, when the EMR terminal 210 of each medical institution participates in the blockchain service to block the medical record, the blockchain applications 211 and 221 including the blockchain core are installed, and the blockchain applications 211 and 221. Each EMR terminal 210 installed) may serve as one node.

Each node may communicate with the blockchain app server 203 through blockchain applications 211 and 221. For example, the blockchain app server 203 may provide an API for querying, deleting, and modifying the blocked data to each node in which the blockchain applications 211 and 221 are installed.

The blockchain applications 211 and 221 may include a blockchain core and a blockchain.

The blockchain core may be an engine that implements a blockchain protocol that blocks a transaction transmitted from the blockchain app server 203 using an actual consensus algorithm and propagates it to each node.

For example, the blockchain core can exemplify Bitcoin open platforms such as Ethereum Open Platform, Hyperledger, or Multichain.

The blockchain core can maintain the same blockchain in each node by synchronizing by distributing it to another node when a block is generated in one node.

The PHR app server 204 maintains a variety of setting information, including a user's login account and disclosure range, in the user information DB 207, and provides a service (eg, inquiry of a medical record document) requested through the PHR application 220. It communicates with the blockchain app server 203 and provides it to the PHR application 220.

Prior to the implementation of the invention, the PHR app server 204 may produce and distribute a PHR application 220 for a query and management service of medical records and health data to a terminal of a patient requesting a download. Alternatively, various health care apps already installed in the patient terminal may be utilized as the PHR application 220.

The PHR application 220 may include functions such as recording and retrieving and deleting health data such as a patient's medical record document or a life log, submitting to other institutions, and setting a public authority.

Here, the disclosure authority is set in the form of submission when setting the EMR terminal of the medical institution to disclose medical record documents, setting some information to be disclosed among the medical record documents, or submitting the medical record document to another institution (original, partial Hidden, anonymization, etc.).

The PHR platform server operating system 200 of the present invention separately stores the header and the body constituting the medical record document in the registry 205 and the multi-distributed storage 206 in the PHR platform server, respectively, and stores the storage location value. By blocking and connecting to the blockchain, the risk of information leakage can be significantly lowered compared to the existing centralized medical information exchange system that keeps patient information and medical records together, thus maintaining high security.

In addition, according to an embodiment of the present invention, whether or not the forgery of the medical record identified using the storage location value can be easily confirmed by comparing the hash value to which a hash function is applied to each of the header and the body constituting the medical record. .

In addition, according to an embodiment of the present invention, without the need to install a separate certificate for the storage of medical records in the EMR terminal, by utilizing a simple encryption method called blockchain, the patient's medical records and health data safely stored or retrieved can do.

3 is a diagram illustrating an example of a medical record document in the PHR platform server operating system according to embodiments of the present invention.

In the EMR terminal, a form is prepared for each type of medical record document, and an item related to the patient is included in each item in the form selected by the attending physician. Form-based medical records can be prepared. Form-based medical record documents can be prepared based on the Fast Healthcare Interoperability Resource (FHIR), an HL7 international standard.

3, a medical request form is shown as an example of a form-based medical record document.

Referring to FIG. 3, the PHR platform server operating system of the present invention may extract data in a medical request form collected from a plurality of EMR terminals by dividing it into a header 310 and a body 320. have.

PHR platform server operating system, the personal information of the patient (eg, name, gender, date of birth, contact, address, etc.) and the information of the care institution that created the medical record (eg, name of the care institution, the number of care institutions, contact information, address, The data field related to the type of medical record document, medical name, etc.) can be extracted as the header 310.

In this case, in the case of a document created during the exchange between hospitals, such as a medical request form, the PHR platform server operating system includes a header 310 containing information of the nursing institution receiving the medical request and information of the nursing institution sending the medical request, respectively. Can be extracted as).

In addition, the PHR platform server operating system may extract, as the body 320, at least one data field of a diagnosis history, a finding of a doctor, a precaution, a prescription, a test record, a treatment record, a surgery record, and an inoculation record. .

The PHR platform server operating system records the extracted header 310 in a registry, maintains the body 320 in any distributed storage selected arbitrarily from among the multiple distributed storages, and stores the storage location value of the body 320 and the header ( The first hash value and the second hash value to which the hash function is applied to the 310 and the body 320 may be blocked and maintained in the blockchain.

Alternatively, the PHR platform server operating system blocks and stores the header 310 together with the storage location value, the first hash value, and the second hash value of the body 320 without storing the header 310 in the registry, thereby securing security. Can be further strengthened.

4A and 4B are tables illustrating examples of data fields recorded in a registry in a PHR platform server operating system according to embodiments of the present invention.

FIG. 4A shows a table 410 showing data fields recorded in the registry when the header extracted from the medical record document is recorded in the registry. FIG. 4B does not record the header extracted from the medical record document in the registry. In the case of blocking, a table 420 is shown showing the data fields written to the registry.

Referring to the table 410 of FIG. 4A, the PHR platform server operating system is a header 401 in the case of an 'electronic medical chart', and care institution information 402 such as a care institution number and an EMR ID, and patient information 403. ) Can be extracted and written to the registry.

At this time, the PHR platform server operating system converts the patient identification key (eg, “2aca1d770381b ~~ b40456” of the table 410) by applying a hash function to the string combining the resident number, name and gender of the patient in the patient information 403 ") Can be recorded in the registry as the header 401.

In addition, the PHR platform server operating system, in the case of a 'medical request form', as a header 404, nursing institution information 405 for receiving a medical request, nursing institution information 406 for sending a medical request, and patient information ( 407, the request number 408, and the transmission date and time 409 can be extracted and recorded in the registry.

In addition, the PHR platform server operating system, in the case of the 'medical record summary', as a header 410, care institution information 411, patient information 412, document number 413 and the date of creation of the medical record summary ( 414) can be extracted and written to the registry.

In addition, the PHR platform server operating system records the first hash value converted by applying a hash function to the header, as shown in Table 420 of FIG. 4B, instead of recording the header extracted from the medical record document into the registry. In addition, the header may be blocked and stored in the blockchain.

The first hash value may be a document header hash key (eg, “33028657537d to b7b8d161” in the table 420) in which a header of a medical form is converted into a hash function. That is, the PHR platform server operating system may record the medical institution information 421, the patient identification key as the patient information 422, and the document header hash key and the registration date as the document information 423 in the registry.

In this case, even if the medical record is hacked, since the personal information of the patient is not recorded in the registry as it is, it is not possible to know which patient's medical record is unless the blockchain is hacked. Can be.

5 is a diagram illustrating a process of storing a medical record document in the PHR platform server operating system according to another embodiment of the present invention.

Referring to FIG. 5, the PHR platform server operating system according to another embodiment of the present invention may collect, maintain, and manage medical record documents created in an EMR terminal using a blockchain-based PHR platform server. Here, the PHR platform server may be configured to include a registry server, distributed storage server, blockchain app server.

In step 501, the EMR terminal, if the medical record document is created based on the contents input from the doctor in charge of the medical institution (nursing institution), the request for storage including the medical institution information such as 'nursing institution number', 'EMR ID' Occurs.

In step 502, the registry server authenticates the 'care institution number' and 'EMR ID' in the storage request to check whether the EMR terminal is an institution capable of storing medical records.

In step 503, the registry server grants an access token (AccessToken) to the EMR terminal if the authentication process is successful. Here, the access token may be generated by using 'OAuth 2.0' as an example.

In step 504, if the access token is granted by the registry server, the EMR terminal transmits the medical record document to the registry server.

Specifically, the EMR terminal may transmit the patient identification key and the medical record document together with the access token to the registry server. Here, the patient identification key (Patient Key) is a key converted by applying the hash function to a string combining the patient's social security number and name and gender, for example, "2aca1d770381b to b40456" in Table 410. have.

That is, in the steps 501 to 504, the EMR terminal may transmit the medical record document after being authenticated by the registry server.

In step 505, the registry server records the header extracted from the medical record document transmitted from the EMR terminal and the first function value converted by applying a hash function to the header, in association with the patient identification key, in the registry.

According to an embodiment, the registry server may record only the first function value in association with the patient identification key in the registry without recording the header in the registry.

In step 506, the registry server transmits the body extracted from the medical record document along with the first hash value to the distributed storage server.

In step 507, the distributed storage server stores the body of the medical record document in a randomly selected distributed storage among the multiple distributed storages, and generates a document ID according to the storage.

At this time, the distributed storage server does not use the first hash value as an index to link the body, but generates the document ID to thereby recognize the association between the header and the body even if both the header in the registry and the body in the multiple distributed storages are hacked. Since it is impossible to know which patient's medical records have been hacked, the security can be enhanced.

In step 508, the distributed storage server transmits the storage location value of the body to the blockchain app server to request blocking.

Specifically, the distributed storage server generates a storage location value of the body including a document ID, a connection URL to the multiple distributed storages, and a document ID, and stores the storage location value with a first hash value (hash value of the header). In addition, a hash function may be applied to the body and transmitted along with the converted second hash value to the blockchain app server.

In step 509, the blockchain app server encrypts the storage location value transmitted from the distributed storage server using a Key Management Service (KMS) of Amazon Web Service (AWS).

Specifically, according to KMS of AWS, the blockchain app server determines a master key to be used through a master key provider, and generates two data keys (plain text data key and encrypted data) using the master key. Key to encrypt the storage location value using a plain text data key, delete the plain text data key when encryption is completed, and encrypt the string and the remaining data key (encrypted data key) that encrypted the storage location value for decryption. Can be returned.

In step 510, the blockchain app server transmits the encrypted storage location value and the data key to the blockchain core together with the first hash value of the header and the second hash value of the body.

In this case, the blockchain app server may further transmit the header not recorded in the registry to the blockchain core to be stored in the blockchain, thereby further enhancing security.

In step 511, the blockchain core generates a block including an encrypted storage location value, the encrypted data key, a first hash value of a header, and a second hash value of a body as a new transaction, and generates the block. It is distributed to each node and synchronized to connect (store) to the blockchain. In this case, the blockchain core may further block the transferred header.

In step 512, the blockchain app server notifies the EMR terminal of the completion of storing the medical record document when the generated block is connected to the blockchain.

As such, the PHR platform server operating system can further enhance the safety of online medical information exchange by maintaining medical information using blockchain and distributed storage technology.

6 is a diagram illustrating a process of providing a medical record document to an EMR terminal according to an inquiry request in a PHR platform server operating system according to another embodiment of the present invention.

Referring to Figure 6, the PHR platform server operating system of the present invention, by using a blockchain-based PHR platform server, it is possible to securely provide the medical records document requested to the EMR terminal. Here, the PHR platform server may be configured to include a registry server, distributed storage server, blockchain app server.

The PHR platform server operating system of the present invention, in conjunction with the EMR terminal of the medical institution and the health care app of the patient, medical records documents scattered in a number of medical institutions, and the amount of activity of the patient collected through the smart terminal (steps, moving distance Health data, such as body weight, blood sugar, and diet information, can be collected and made available for viewing, submission to other institutions, and setting up disclosure.

In step 601, the EMR terminal generates an inquiry request including care institution information ('care institution number', 'EMR ID').

In step 602, the registry server authenticates the 'care agency number', 'EMR ID' in the inquiry request, and confirms whether the EMR terminal can query the medical record document.

In step 603, the registry server grants an access token (AccessToken) to the EMR terminal if the authentication process is successful.

In step 604, if the access token is granted by the registry server, the EMR terminal requests a header list (medical record list) of a specific patient.

Specifically, the EMR terminal may transmit the patient identification key converted by applying the hash function to the patient information to the registry server so that the patient's medical record document is not leaked.

In step 605, the registry server searches for the first hash value of the header related to the specific patient in the registry using the patient identification key, and lists the searched first hash values and transmits the header list to the EMR terminal.

In step 606, the EMR terminal transmits the first hash value selected from the header list to the blockchain app server, and requests a storage location value of the medical record document associated with the first hash value.

That is, the EMR terminal may designate a medical record document to be inquired in consideration of the age at the time of the patient's treatment, the type or name of the medical institution or the medical form, and the registration date of the medical record document among the various medical record documents of the specific patient.

In steps 607 and 608, the blockchain app server retrieves a block including the selected first hash value from the blockchain, and retrieves an encrypted storage location value, a data key, and a second hash value of the body from the retrieved block. Check it. In this case, the blockchain app server may further check a header corresponding to the first hash value from the block.

In steps 609 and 610, the blockchain app server decrypts the storage location value encrypted according to the KMS of AWS using the data key, and provides the decrypted storage location value and the second hash value of the body to the EMR terminal. . In this case, the blockchain app server may provide a header of the medical record document together with the EMR terminal.

In step 611, the EMR terminal requests the body of the medical record document stored in the storage location value to the distributed storage server.

In step 612, the distributed storage server identifies the body of the medical record document stored in the storage location value from the multiple distributed storage, and transmits to the EMR terminal.

In step 613, the EMR terminal checks the forgery of the medical record document through the registry server.

In detail, the EMR terminal checks whether a value obtained by applying a hash function to the header provided from the blockchain app server in step 610 matches the first hash value selected in step 606, and in step 612. The medical record composed by combining the header and the body by confirming that the value of applying the hash function to the body transmitted from the distributed storage server in step 610 matches the second hash value provided from the blockchain app server in step 610. Integrity of the document can be verified.

In step 614, if all the EMR terminals match, the EMR terminal confirms that the medical record document is not forged or tampered with and displays it.

As such, according to an embodiment of the present invention, the medical records written about the patient are collected from a plurality of medical institutions and maintained on a blockchain-based PHR platform server, and the blockchain is used to maintain the medical records maintained on the PHR platform server. Can support secure inquiry service.

7 is a diagram illustrating a process of providing a medical record document to a patient terminal according to an inquiry request in a PHR platform server operating system according to another embodiment of the present invention.

Referring to FIG. 7, the PHR platform server operating system according to another embodiment of the present invention uses a blockchain-based PHR platform server, and a PHR application (hereinafter, 'PHR app') in which a patient is executed in his terminal. Through this, you can easily search your medical records. In this case, the PHR platform server may further comprise a PHR app server.

In step 701, the PHR app attempts to log in to the PHR app server using the login account (ID, PW) created by the patient terminal.

In steps 702 and 703, the PHR app generates an inquiry request of the medical record document if the login is successful.

In steps 704 and 705, when the user authentication is processed using the patient identification key, the PHR app server grants an access token to the PHR app.

That is, if the PHR app logs in successfully, the PHR app may obtain an access token using the patient identification key stored in the patient terminal. Here, the patient identification key is a key converted by applying a hash function to the patient information input when creating the login account, and the PHR app maintains the patient identification key in the patient terminal separately from the login account maintained on the PHR app server. It can increase.

In step 706, the PHR app requests a list of medical records of a specific patient to the registry server through the PHR app server.

In this case, the PHR app may request a list of the patient's medical records using the patient identification key, or may request a list of the patient's medical records using the patient's family identification key. If you have obtained informed consent, you may request a list of acquaintances' medical records.

In step 707, the registry server delivers a header list listing headers of a specific patient to the PHR app through the PHR app server.

In step 708, the PHR app requests the medical record document by transmitting the first hash value of the header selected in the header list to the PHR app server.

In step 709, the PHR app server requests the blockchain app server for the storage location value of the medical record document requested by the PHR app.

In steps 710 and 711, the blockchain app server searches for the block including the first hash value from the blockchain and checks the encrypted storage location value, the data key, and the second hash value of the body from the found block. .

In steps 712 and 713, the blockchain app server decrypts the encrypted storage location value with the data key and provides the PHR app server with the second hash value of the body.

In step 714, the PHR app server requests the body of the medical record document stored in the storage location value to the distributed storage server.

In steps 715 and 716, when the body of the medical record document is transmitted from the distributed storage server, the PHR app server verifies the forgery.

In detail, the PHR app server checks whether the first hash value coincides with the value of the hash function applied to the header selected in the step 708, and the second hash and the value applying the hash function to the body transmitted in the step 715. By checking whether the values match, it is possible to check whether the medical record document combining the header and the body is forged or tampered with.

In step 717, the PHR app server provides the patient's PHR app with a medical record document that has been verified as not forged or tampered with.

Accordingly, the patient can easily view the medical record along with the health data through the health care app installed in his terminal.

Hereinafter, the workflow of the PHR platform server operating system 100 according to embodiments of the present invention will be described in detail.

8 is a diagram illustrating a procedure of a blockchain-based PHR platform server operating method according to an embodiment of the present invention.

The PHR platform server operating method according to the present embodiment may be performed by the PHR platform server operating system 100 described above.

Referring to FIG. 8, in step 810, the PHR platform server operating system 100 collects medical record documents created by the EMR terminal at regular intervals and maintains them in multiple distributed repositories.

In step 820, the PHR platform server operating system 100 records the header extracted from the medical record document in a registry provided separately from the multiple distributed storage.

In operation 830, the PHR platform server operating system 100 blocks the storage location value of the medical record document along with the first hash value to which the hash function is applied to the header based on the blockchain core. Connect to the chain.

The PHR platform server operating system 100 generates a block including a storage location value of the medical record document and a first hash value of the header, and connects the blockchain configured in a previous cycle.

In step 840, the PHR platform server operating system 100 checks whether an inquiry request is generated from the EMR terminal. At this time, the PHR platform server operating system 100 may check whether the authenticated EMR terminal subscribed to the blockchain-based PHR platform server.

As a result of the check, when the inquiry request is generated in the authenticated EMR terminal, in step 850, the PHR platform server operating system 100, the EMR terminal to the header list (medical record list) to select the medical record document to be inquired To pass on.

In this case, if the inquiry request includes a patient identification key for a specific patient, the PHR platform server operating system 100 may transmit a header list of the specific patient to the EMR terminal after the authentication process.

In steps 860 to 870, the PHR platform server operating system 100 retrieves, from the blockchain, the block designated by the selected hash value selected by the EMR terminal, and returns the storage location value in the block to the EMR terminal. Returns.

The EMR terminal checks whether or not forgery through the registry server for the medical record document in the multiple distributed storage identified by the storage location value, and displays on the screen when it is confirmed that the forgery is not forged.

As such, the PHR platform server operating system 100 utilizes blockchain and distributed storage technology to collect and safely store not only the patient's medical records but also the health data, and the medical records that are being kept when requesting inquiry from a hospital or a patient. Or health data can be provided securely.

The method according to the embodiment may be embodied in the form of program instructions that can be executed by various computer means and recorded in a computer readable medium. The computer readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the media may be those specially designed and constructed for the purposes of the embodiments, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, such as floppy disks. Magneto-optical media, and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

The software may include a computer program, code, instructions, or a combination of one or more of the above, and may configure the processing device to operate as desired, or process independently or collectively. You can command the device. Software and / or data may be any type of machine, component, physical device, virtual equipment, computer storage medium or device in order to be interpreted by or to provide instructions or data to the processing device. Or may be permanently or temporarily embodied in a signal wave to be transmitted. The software may be distributed over networked computer systems so that they may be stored or executed in a distributed manner. Software and data may be stored on one or more computer readable recording media.

Although the embodiments have been described with reference to the accompanying drawings, those skilled in the art may apply various technical modifications and variations based on the above. For example, the described techniques may be performed in a different order than the described method, and / or components of the described systems, structures, devices, circuits, etc. may be combined or combined in a different form than the described method, or other components. Or, even if replaced or substituted by equivalents, an appropriate result can be achieved.

Therefore, other implementations, other embodiments, and equivalents to the claims are within the scope of the following claims.

100: PHR platform server operating system
101: Registry 102: Multiple Distributed Repositories
110: recording unit 120: block
130: processor 140: converter
150: delivery unit 160: confirmation unit
170: output unit

Claims (18)

Collecting a first medical record document prepared from an EMR terminal and maintaining the first medical record document in multiple distributed repositories;
Extracting patient information in the first medical record document and recording it in a registry as a header for the first medical record document;
Based on a blockchain core, blocking a storage location value of the first medical record document and a hash value of the header in the multi-distributed storage, and connecting the blockchain with a blockchain; And
In conjunction with the occurrence of the inquiry request,
Retrieving a block designated by a hash value selected from a header list of a plurality of hash values from the blockchain, and providing a storage location value constituting the retrieved block to the generated EMR terminal;
Blockchain-based PHR platform server operating method comprising a. The method of claim 1,
Extracting patient information from a second medical record document previously held in the multiple distributed storage;
Converting the patient information into a hash value by applying a hash function;
Delivering the header list listing a plurality of hash values to the EMR terminal;
Retrieving, from the blockchain, a block designated by a hash value selected from the header list; And
Displaying, on the EMR terminal, a second medical record document identified from the multiple distributed storages by a storage location value constituting the retrieved block.
PHR platform server operating method comprising more. Converting the patient information extracted as a header into a first hash value from the medical record document held in the multi-distributed storage at regular intervals;
Delivering the header list created by listing the first hash value to an EMR terminal generating an inquiry request;
Retrieving a block generated in association with the patient information from the blockchain using a selection hash value selected from the header list; And
Displaying, on the EMR terminal, a third medical record document identified from the multiple distributed storages by a storage location value included in the block.
Blockchain-based PHR platform server operating method comprising a. The method of claim 3,
When the storage location value is encrypted by a first data key among a plurality of data keys generated using a key management service (KMS) of Amazon Web Service (AWS) and included in the block,
Displaying on the EMR terminal,
Identifying the third medical record document from the multiple distributed storages using the storage location value decrypted using a second data key of the plurality of data keys, further included in the block.
PHR platform server operating method comprising a. The method of claim 3,
Collect the medical record document based on at least one of the electronic medical chart, medical record summary, medical request form and medical report form at regular intervals from the EMR terminal installed in the nursing institution, and distribute any one selected randomly from the multiple distributed storage. Maintaining in the reservoir; And
Generating a block including a storage location value of the medical record document and the first hash value based on a blockchain core and connecting the blockchain configured in a previous cycle;
PHR platform server operating method comprising more. The method of claim 5,
The PHR platform server operating method,
Recording the header in a registry provided separately from the multiple distributed repositories;
More,
Maintaining in the distributed storage,
The medical record document extracts at least one data of a diagnosis history, a medical opinion, a precaution, a prescription, a test record, a treatment record, a surgical record, and an inoculation record except the header, and distributes any one of the data. Steps to keep in the store
Including,
Connecting to the blockchain,
Generating the block further including a second hash value converted by applying the hash function to the body;
PHR platform server operating method comprising more. The method of claim 6,
If the header is not maintained in a registry provided separately from the multiple distributed repositories,
Connecting to the blockchain,
Generating the block further comprising the header
PHR platform server operating method comprising more. The method of claim 6,
The PHR platform server operating method,
Confirming whether the third medical record document is forged or altered before displaying to the EMR terminal;
More,
If, as a result of the above confirmation, is not forged,
Displaying on the EMR terminal,
Displaying, on the EMR terminal, the third medical record document configured by combining the first header associated with the selection hash value with the first body identified by the storage location value.
PHR platform server operating method comprising a. The method of claim 8,
Checking whether the forgery,
Checking whether a hash value to which the hash function is applied to the first header matches the selected hash value, and a hash value to which the hash function is applied to the first body is consistent with a second hash value further included in the searched block. step
PHR platform server operating method comprising a. The method of claim 3,
In the case of converting medical institution information or form type information in the medical record document further extracted as the header into the first hash value together with the patient information,
Among the blocks generated in relation to the patient information, a block further related to a specific nursing institution or a specific form according to the selected hash value is selected, and a storage position value of the third medical record document included in the selected block is selected. Transmitting to the EMR terminal
PHR platform server operating method comprising more. The method of claim 3,
Collecting at least one health data of a prescription and a life log recorded in the terminal of the patient at regular intervals through a PHR application installed in the terminal of the patient and further maintaining the health data in the multiple distributed storage;
Outputting, to the PHR application, an interface for setting the disclosure range of the information and the EMR terminal to publish the information, as at least one of the health data and the medical record document is maintained in the multiple distributed storage; And
If the EMR terminal is set to public through the interface,
In response to the inquiry request, allowing access to the information in the multiple distributed repositories
PHR platform server operating method comprising more. The method of claim 9,
Converting patient information input when a login account for the PHR application is generated at the terminal of the patient to a hash value by applying a hash function;
Maintaining the hash value in a terminal of the patient, separately from the login account maintained in an app server managing the PHR application;
When the inquiry request is received from the terminal of the patient through the PHR application,
Retrieving the block from the blockchain using the hash value as the selected hash value; And
Displaying, on the PHR application, a third medical record of the patient identified from the multiple distributed storages according to the storage location value in the block.
PHR platform server operating method comprising more. A recording unit which collects the first medical record document created from the EMR terminal, maintains it in multiple distributed storages, extracts patient information in the first medical record document, and records it in the registry as a header for the first medical record document;
A block unit configured to block a storage position value of the first medical record document and a hash value of the header based on a block chain core and connect the block value to a block chain; And
In conjunction with the occurrence of the inquiry request,
A processing unit for retrieving a block designated by a hash value selected from a header list of a plurality of hash values from the blockchain, and providing a storage location value constituting the retrieved block to the generated EMR terminal;
Blockchain-based PHR platform server operating system comprising a. The method of claim 13,
A converting unit converting the patient information extracted from the second medical record document pre-stored in the multiple distributed storages into a hash value by applying a hash function; And
A transfer unit for transmitting the header list listing a plurality of hash values to the EMR terminal
More,
The processing unit,
The EMR terminal retrieves a block designated by a hash value selected from the header list from the blockchain, and a second medical record document identified from the multiple distributed storages by a storage location value constituting the retrieved block. Displayed on
PHR platform server operating system. A conversion unit for converting the patient information extracted as a header from the medical record documents held in the multiple distributed storages at regular intervals to a first hash value by applying a hash function;
A transfer unit for transferring the header list created by listing the first hash values, to the EMR terminal generating the inquiry request; And
A third medical treatment identified from the multi-distributed storage by retrieving a block generated in association with the patient information from the blockchain using a selection hash value selected from the header list, and a storage location value included in the block; A processing unit for displaying the recorded document on the EMR terminal
Blockchain-based PHR platform server operating system comprising a. The method of claim 15,
Collect the medical record document based on at least one of the electronic medical chart, medical record summary, medical request form and medical report form at regular intervals from the EMR terminal installed in the nursing institution, and distribute any one selected randomly from the multiple distributed storage. A recording unit held in the storage; And
Based on a blockchain core, a blocker for generating a block including a storage location value of the medical record document and the first hash value, and connecting the blockchain configured in a previous cycle
PHR platform server operating system further comprising. The method of claim 16,
The recording unit,
Record the header in a registry provided separately from the multiple distributed repositories,
The medical record document extracts at least one data of a diagnosis history, a medical opinion, a precaution, a prescription, a test record, a treatment record, a surgical record, and an inoculation record except the header, and distributes any one of the data. Keep in the store,
The block unit,
Generating the block by further including a second hash value converted by applying the hash function to the body;
PHR platform server operating system. The method of claim 17,
If the header is not maintained in a registry provided separately from the multiple distributed repositories,
The block unit,
Generating the block further including the header
PHR platform server operating system.

Images