KR20220152505A - Managing method for EHR based on block chain - Google Patents

Abstract

The present invention relates to a method of managing a blockchain-based electronic health record, which enables easy electronic health record management in a common way regardless of the type of blockchain by using a standardized system. To this end, the present invention provides a method of managing a blockchain-based electronic health record, the method comprising: a step of generating a table structure including a table name and a column name by using a user-defined tag; a step of constructing a smart contract corresponding to the table structure by a migrator; a step of installing the smart contract constructed by the migrator on an abstract blockchain unit; and a step of allowing the migrator to parse electronic health record data converted into a standardized format and store the data in a corresponding table name and column name. Therefore, according to the present invention, an environment may be provided, which allows general administrators who are not computer experts to be able to easily use electronic health record data on a blockchain.

Description

Blockchain-based electronic medical record management method {Managing method for EHR based on block chain}

The present invention relates to a blockchain-based electronic medical record management method, and specifically, a blockchain-based electronic medical record that can be easily managed in a common way regardless of the type of blockchain using a standardized system. It is about record management method.

An Electronic Health Record (EHR) is a digital data connection of health information generated by medical institutions and health promotion institutions. Such an electronic medical record has an advantage in that medical records can be used at any hospital by exchanging data between medical institutions through a network. In addition, there are advantages such as automating medical appointments and improving administrative work efficiency such as billing for medical expenses.

However, since electronic medical records are important personal information, security is important, and forgery or alteration must be prevented. In order to satisfy these requirements, an expensive data system is required, which inevitably increases the cost burden for medical institutions.

In order to prevent such forgery and alteration and security, studies have recently been conducted to transmit medical records using block chain technology.

According to the prior art Registered Patent No. 10-1763827 (blockchain-based medical data transmission system), the relay server receives one or more block data from the first node server; A relay server combining and storing the one or more block data in a block chain; and transmitting the at least one block data to a second node server.

According to this configuration, there is an advantage in that it is possible to compare block data (i.e., medical data) stored in multiple node servers to check whether the medical data requested by the user has been forged or falsified. There is a problem that it is difficult to commercialize it because it is difficult to store, transmit, and modify operations, so general medical managers who are not blockchain experts have limitations in managing these systems.

The present invention is to solve the above problems, and specifically, to provide a blockchain middleware system that allows general users to easily use electronic medical record data on a blockchain as if handling a general database.

In order to achieve the above object, the present invention includes the steps of generating a table structure including table names and column names using user-defined tags; Forming a smart contract corresponding to the table structure by the migrator; Installing a smart contract configured by the migrator in an abstract blockchain unit; The migrator provides a blockchain-based electronic medical record management method that parses electronic medical record data converted into a standardized format and stores the data in corresponding table names and column names.

Creating a table object having the same columns as the table stored in the smart contract at the Ledger Master at the request of the client; A data management API is provided by the Ledger Master to manipulate data stored in the table object, and a step of storing or retrieving data in the target blockchain is performed at the request of a client using the data management API. It is desirable to do

transmitting a query string provided from the Ledger Master by the client;

The Ledger Master parses the query string and passes it to the smart contract as an argument, and the smart contract can perform a step of storing data in the target blockchain or retrieving the data in response to the argument.

The user-defined tag preferably includes a create tag for creating a table, an input tag for inputting data into the table, a change tag for changing data stored in the table, and a delete tag for deleting data stored in the table.

The migrator may install a smart contract in the abstract block chain unit, generate a smart contract address corresponding to a table structure configured by the client, and transmit the smart contract to the abstract block chain unit.

The table structure includes table names, column names, indexes, and constraints.

Preferably, the smart contract generates a hash code using the table name and column name corresponding to the data stored in the target blockchain.

The table structure includes one primary column name among a plurality of column names, and the smart contract uses the data corresponding to the first index among the primary column names as a root node and determines the size of data belonging to the primary column. It is desirable to determine the position of the child node by comparison.

According to the present invention, it is possible to provide an environment in which a general manager, not a computer expert, can easily use electronic medical record data on a blockchain.

In addition, it provides a middleware function that enables the use of blockchain as a storage for FHIR, and makes it easier to electronically share and communicate medical records between multiple medical providers.

1 is a diagram for explaining a blockchain system according to an embodiment of the present invention.
2 is a flowchart for explaining a method for mapping a blockchain database according to an embodiment of the present invention.
3 is a block diagram showing the configuration of a blockchain-based electronic medical record management system according to an embodiment of the present invention.

The configuration and operation of specific embodiments according to the present invention will be described in detail with reference to the drawings.

1 is a diagram for explaining a blockchain system according to an embodiment of the present invention. Referring to FIG. 1 , a blockchain system according to an embodiment of the present invention includes a client 100, a middleware system 200, an abstract blockchain unit 230, and a blockchain 300.

The client 100 creates a table structure using a user-defined tag set by a user, and receives a target block chain to know which block chain the target block chain is targeting.

The table structure set by the user includes table configuration such as table name meaning table name, column name indicating table item, index indicating order in table, and constraints such as input text type of table item. At this time, processing such as B TREE and HASH INDEX is performed based on the table name and column name on the blockchain.

User-defined tags include various tags such as a create tag to create a table, an input tag to input data into a table, a change tag to change data stored in a table, and a delete tag to delete data stored in a table. These tags are in XML format. can be made with

The middleware system 200 includes a migrator 210 and a leisure master 220 .

The migrator 210 installs a smart contract in the abstract blockchain unit 230, and the migrator 210 generates the address of the smart contract corresponding to the table structure configured by the client 100, and the abstract blockchain unit 230 ) is sent to In addition, matters transmitted to the abstract blockchain 230 by the migrator 210 further include settings such as block size and block generation cycle.

First, the migrator 210 creates a table structure based on user-defined tags in XML, and configures a smart contract corresponding to the table structure by mapping the table structure to a smart contract. At this time, the address of at least one smart contract can be mapped to the table structure created based on the XML user-defined tag. In the case of the present invention, the table structure can be created using XML defined by the user, so it has the advantage that it can be easily used without acquiring a high level of blockchain knowledge.

The migrator 210 installs the infrastructure smart contract on the blockchain based on the columns, indexes, and constraints defined by the user in XML, and configures the smart contract for the user-defined table format. Accordingly, in the abstract blockchain 230 to be described later, when the target blockchains are different, user convenience can be increased by not requiring modification according to each target block chain.

The Ledger Master unit 220 makes it possible to create an object having columns such as a table stored in a smart contract.

The Ledger Master 220 includes an object mapper unit 221 and a query DSL unit 222.

The object mapper unit 221 enables the Ledger Master to create an object having the same columns as a table stored in a smart contract using an API at the request of the client 100 . Based on a plurality of defined classes, at the time of execution, a table with the same columns as the properties of the corresponding class is automatically created as a table by a series of smart contract groups stored inside.

In addition, the object mapper 221 has a data management API in the form of Java methods such as insert, query, count, findBy, addColumn, and addIndex to perform various functions such as table form and content and search.

The object mapper 221 can store or retrieve data from the target blockchain at the request of a client using the data management API as described above. Users can easily manage the data on the blockchain ledger through commands using the data management API prepared in advance without knowledge of a separate program.

The query DSL unit 222 generates a query through a user-defined functional query. When the query string provided by the query DSL unit 222 is transmitted by the client 100, the query DSL unit 222 parses the query string and passes it to the smart contract as an argument, and the smart contract responds to the argument to the target block You can store data on the chain or retrieve that data.

The query DSL unit 120 is for utilizing something other than the prescribed API used in the object mapper 110, and can identify problems in the query at the time of compilation through a user-defined functional query, and can perform various combinations of queries. be able to

If only the object mapper 110 is used, it becomes difficult to utilize anything other than the designated API, and in the case of other than the API, there is a problem in that it must be directly manipulated. On the other hand, if a query is written directly, a string is used, and the problem exists that the string can be verified only at the time of execution. Through the user-defined functional query through the query DSL unit 120 of the present invention, it is possible to identify the problem of the corresponding query at the time of compilation, and to perform queries in various combinations.

The abstract block chain unit 230 is not a target block chain, but is for performing DB-related functions and includes a test server function and an interface function.

When a command using the API is transmitted from the Ledger Master 220, the abstract block chain unit 230 that receives the command transmitted using the API, for example, a command to search the index C of item B of table A, It interprets the command using the API provided in and transmits it to the blockchain 300 according to the interpreted command. If the abstract block chain unit 230 does not exist, a command must be issued using a specialized program that can be applied to the target block chain 300, but in the case of the present invention, the abstract block chain unit 230 interprets DB-related commands. Since it is transmitted to the target block chain 300, there is no need to use a specific programming language for manipulating the target block chain 300.

The abstract blockchain unit includes a common API unit that provides a common API regardless of the type of blockchain, an individual API unit that provides an API of a target blockchain, and an API matching unit, and the API matching unit can respond appropriately to the common API. Detect and respond to the API of the target blockchain that can be used. At this time, the number of APIs of the target blockchain to be detected may be plural.

In addition, the abstract blockchain unit 230 provides a coding test function. A developer may perform a coding test on both the abstract block chain unit 230 and the block chain 300 during an overall test that tests the entire coding. Meanwhile, in the case of a unit test in which a test is performed for each line of coding, a developer may perform a coding test only for the abstract block chain unit 230, not for the block chain. In the case of blockchain, the setting file must be installed for each unit test, but in the case of the abstract block chain unit 230, installation of the setting file by the migrator 210 can be omitted during successive unit tests. Accordingly, unit tests of coding can be quickly performed by the abstract block chain unit 230 .

The abstract blockchain unit 230 includes an interface 231 capable of transmitting data corresponding to a target blockchain. The interface 231 corresponding to the received target block chain performs data transmission between the abstract block chain unit and the target block chain.

Although the use method of each of the enterprise blockchain, Ethereum-based Quorom and Hyperledger Fabric is different, each usage method is different, but the present invention manages through the abstract block chain unit 230 so that the migrator 210 and the ledger master ( 230), it is possible to commonize and provide the blockchain API required.

Convex chain 300 is more related to a consortium-type block chain that can be used in the enterprise area than Bitcoin, which is money transfer, and is for reliable distributed data sharing, that is, for use as a distributed database.

On the other hand, in order to efficiently manage data stored in the distributed ledger, processes such as B tree/Hash Index, which are widely known to efficiently search and update large-capacity files, may be included.

In this regard, in the blockchain 300, the smart contract can set the data corresponding to the first index of the primary column names in the table structure as the root node, and compare the size of the data belonging to the primary column to determine the location of the child node. have. In the above case, an equal search speed can be guaranteed and the efficiency of the storage device can be increased.

2 is a flowchart for explaining a method for mapping a blockchain database according to an embodiment of the present invention.

Referring to FIG. 2, the blockchain database mapping method includes the steps of creating a table structure by using a user-defined tag by a client (S110); Step of receiving an input of the target blockchain set and used by the client (S120); A step of constructing a smart contract corresponding to the table structure by the migrator (S130); A step of installing a smart contract configured by the migrator in an abstract blockchain unit that provides a common API (S140); and transmitting data between the abstract block chain unit and the target block chain through an interface corresponding to the received target block chain (S150).

In the step of generating a table structure by inputting a user-defined tag by the client (S110), the table structure set by the user includes a table name indicating a table name, a column name indicating an item in the table, an index indicating an order in the table, Includes table configuration such as constraints such as input text type of table item.

On the other hand, these user-defined tags include various tags such as a create tag for creating a table, an input tag for inputting data into a table, a change tag for changing data stored in a table, and a delete tag for deleting data stored in a table. These may be made in XML format.

As a user-defined tag defined by the user, a table structure can be created using XML, so it has the advantage of being easy to use without acquiring a high level of blockchain knowledge.

In step S120 of inputting the target block chain to be set and used by the client, the block chain set as the target among various block chains is input by the user.

In the step of configuring the smart contract corresponding to the table structure by the migrator (S130), the table structure is created based on the user-defined tags of XML, and the smart contract corresponding to the table structure is mapped to the smart contract. make up

The smart contract configured by the migrator is installed in the abstract blockchain unit that provides a common API (S140), and data is transmitted between the abstract blockchain unit and the target blockchain by the interface corresponding to the received target blockchain. A point to note in the transmission step (S150) is that the abstract blockchain unit 230 provides a common API that commonizes APIs required by the migrator and ledger master for various blockchains. According to the different usage methods of Ethereum-based Quorom and Hyperledger Fabric, which are enterprise blockchains, the APIs required by the Migrator and Ledger Master according to each usage method must be configured differently. In the case of the present invention, the common API of the abstract block chain unit 230 can save time and effort required to set different APIs according to various block chains.

Referring to FIG. 3, Electronic Health Record (EHR) managed by each medical institution is called through the standardization API and transmitted to the medical record standardization management unit, and the medical record standardization management unit parses the document or data and then It is newly formatted and transmitted to the middleware system 200 in a standard form such as XML or JSON.

The documents or data may include clinical data as well as medical related administrative, public health and research data.

The medical record standardization management unit may be provided in the form of a server and defines a standardized data format for medical data. In addition, standardized data for each resource is stored in the resource storage.

For example, if the resource is 'prescription', the template may contain a form including 'date of birth', 'gender', 'diagnosis name', 'drug name', 'prescription date', etc. These resource data are stored in the resource repository. is stored in

The reliability of data exchanged in the EHR system environment is secured by utilizing the block chain for the physical configuration space of the resource storage, and the distributed environment, which is a fundamental characteristic of the block chain, is utilized to ensure that the EHR, pharmacy system, and HIS are subject to information exchange. A flexible diffusion system can be prepared.

The electronic medical record data standardized by the medical record standardization management unit is transmitted to the middleware system and processed before being recorded on the blockchain ledger. The migrator of the middleware system serves to map the table structure set in the web standard form to the smart contract. If the user defines columns, indexes, constraints, etc., the migrator installs the base environment smart contract on the blockchain and configures the smart contract that conforms to the table format defined by the user. At this time, additional functions such as B-Tree and hash index are implemented to efficiently manage medical data to be stored in the blockchain ledger.

A common API implemented in the middleware system allows you to create an object with the same column as a table stored in a smart contract. If the class is defined, the table is automatically created at the time of execution by a series of smart contract groups that have tables with the same columns as the properties of the class stored inside. In addition, through Java methods such as insert, query, count, findBy, addColumn, and addIndex, data on the blockchain ledger can be easily managed. In addition, by implementing the QueryDSL function, problems in the query can be identified at the time of compilation through user-defined functional queries, and queries in various combinations can be executed.

The migrator parses the electronic medical record data converted into a standardized format and stores the data in corresponding table names and column names.

In addition, Abstract Blockchain provides an abstract layer for various blockchain platforms. For example, among various blockchains, Ethereum Quorum and Hyperledger Fabric have different usage methods. By managing them as an abstraction layer, a common API can be provided by commonizing the blockchain APIs required by migrators and middleware.

In this way, the electronic medical record data that differs for each medical institution is converted into a standardized format with versatility through the medical record standardization management unit, which is processed and systematized in a form that can efficiently manage data on the blockchain through the middleware system, and processed data When moving to a blockchain network, it is possible to safely manage medical data on a blockchain under similar usage conditions to existing RDBs by being able to select a blockchain platform suitable for the environment that handles electronic medical record data.

According to the present invention, as a storage of electronic medical record data in which electronic medical record data providers can share patient data electronically, reliability is secured through the use of blockchain technology, and blocks are configured to configure the RDB environment of the blockchain ledger. With the implementation of chain middleware and the standard format of medical data, it is possible to increase the efficiency of data sharing through resource utilization of the medical record standardization management department.

In addition, it implements a middleware function that enables data structure definition, including a smart contract authoring function to improve the efficiency of blockchain-based data management.

In addition, a method for exchanging electronic medical record data through the medical record standardization management unit is prepared, and a middleware system that enables the use of blockchain as a storage of the medical record standardization management unit is provided.

The medical record standardization management unit may utilize, for example, Fast Healthcare Interoperability Resource (FHIR).

Although the above has been described with reference to the embodiments of the present invention, those skilled in the art can variously modify and modify the present invention within the scope not departing from the spirit and scope of the present invention described in the claims below. You will understand that it can be changed.

100: client
200: middleware system
210: migrator
220: leisure master
230: abstraction blockchain
300: Blockchain
500: Medical record standardization management department

Claims (7)

generating a table structure including table names and column names using user-defined tags;
Forming a smart contract corresponding to the table structure by the migrator;
Installing a smart contract configured by the migrator in an abstract blockchain unit;
A block chain-based electronic medical record management method in which the migrator parses the electronic medical record data converted into a standardized format and stores the corresponding data in the corresponding table name and column name.
According to claim 1,
Creating a table object having the same columns as the table stored in the smart contract at the Ledger Master at the request of the client;
A data management API is provided by the Ledger Master to manipulate data stored in the table object, and a step of storing or retrieving data in the target blockchain is performed at the request of a client using the data management API. Blockchain-based electronic medical record management method.
According to claim 1,
transmitting a query string provided from the Ledger Master by the client;
Blockchain-based electronic medical care in which the Ledger Master parses the query string and passes it to the smart contract as an argument, and the smart contract performs a step of storing data in the target blockchain or retrieving the corresponding data in response to the argument Records management method.
According to claim 1,
The user-defined tag includes a create tag for creating a table, an input tag for inputting data into the table, a change tag for changing data stored in the table, and a delete tag for deleting data stored in the table. Electronic medical record management method.
According to claim 1,
The migrator installs a smart contract in the abstract blockchain unit, generates an address of the smart contract corresponding to the table structure configured by the client, and transmits it to the abstract blockchain unit. Blockchain-based electronic medical care Records management method.
According to claim 1,
The table structure includes table names, column names, indexes, and constraints.
The smart contract generates a hash code using table names and column names corresponding to data stored in the target blockchain.
According to claim 6,
The table structure includes one primary column name among a plurality of column names,
The smart contract sets the data corresponding to the first index of the primary column names as a root node, and compares the size of data belonging to the primary column to determine the location of the child node. Blockchain-based electronic medical record management Way.

Images