KR101892161B1 - Method for managing electronic medical record and metadata storage system thereof - Google Patents

Method for managing electronic medical record and metadata storage system thereof Download PDF

Info

Publication number
KR101892161B1
KR101892161B1 KR1020150011482A KR20150011482A KR101892161B1 KR 101892161 B1 KR101892161 B1 KR 101892161B1 KR 1020150011482 A KR1020150011482 A KR 1020150011482A KR 20150011482 A KR20150011482 A KR 20150011482A KR 101892161 B1 KR101892161 B1 KR 101892161B1
Authority
KR
South Korea
Prior art keywords
mapping rule
medical record
data element
service system
medical
Prior art date
Application number
KR1020150011482A
Other languages
Korean (ko)
Other versions
KR20160091169A (en
Inventor
김주한
Original Assignee
주식회사 싸이퍼롬
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 주식회사 싸이퍼롬 filed Critical 주식회사 싸이퍼롬
Priority to KR1020150011482A priority Critical patent/KR101892161B1/en
Priority to PCT/KR2015/013627 priority patent/WO2016117826A1/en
Publication of KR20160091169A publication Critical patent/KR20160091169A/en
Application granted granted Critical
Publication of KR101892161B1 publication Critical patent/KR101892161B1/en

Links

Images

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F17/301—
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Z—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS, NOT OTHERWISE PROVIDED FOR
    • G16Z99/00—Subject matter not provided for in other main groups of this subclass

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Epidemiology (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

In embodiments, the method of managing a medical record is performed in a medical record service system connectable with a metadata repository managing metadata and mapping rules for at least one data element included in the medical record. The medical record management method includes: querying a mapping rule for at least one data element included in a first career record; and if the mapping rule does not exist, generating a mapping rule for the data element And a requesting step.

Description

METHOD FOR MANAGING ELECTRONIC MEDICAL RECORD AND METADATA STORAGE SYSTEM THEREOF BACKGROUND OF THE INVENTION [0001]

The disclosed technique relates to a medical record management technique, and more particularly, to a medical record management method and a metadata storage system for the same that can guarantee the semantic operability of a medical record using metadata.

The exchange of medical records can generate various benefits such as improvement of diagnosis accuracy, prevention of duplicate inspection, improvement of patient safety. Most medical institutions carry out information exchange, but this is only a one-time information exchange, such as the exchange of documents and films of radiation.

The invention of exchanging conventional medical records has a limitation in that it can be based on a one-to-one single information sharing scenario such as an institution-to-institution or a hospital-to-hospital or can only be exchanged between a limited number of medical record formats. However, there is a real need for a multilateral medical information exchange system capable of ensuring semantic operability between medical records having a continuous and different format, not a conventional disturbance or a limited exchange of individual medical records .

Continuous medical records are the standard of the American Society for Testing and Materials (SDS), the Standard Development Organization (SDO), which allows individuals to organically store and manage their lifelong health information The patient is able to carry his / her health information effectively to the doctor to manage the chronic diseases etc. in the long term, and the medical staff can quickly cope with the emergency situation.

Regarding these continuing medical records, Google and Microsoft are providing personal health record services based on continuous medical history records, Google health and HealthVault, and are preparing for continuous medical record services at many major hospitals both at home and abroad. As such, continuing medical records are becoming increasingly influential and are expected to become one of the most widely used health records in the near future.

Regarding records of continuing care, relevant standards have been established, but in practice each service provider is expanding or modifying this standard as needed to provide services. Due to these extensions or altered forms, the continuing care records between different service providers are syntactically consistent with the respective standards, but not semantically consistent, so that the continuing care records between these service providers are mutually semantically consistent There is a problem that it is difficult to exchange.

An embodiment of the present invention is to provide a medical record management method and a metadata repository for the medical record management method that can guarantee semantical operability of a medical record using metadata.

One embodiment of the present invention seeks to provide a method and a metadata repository for a method for managing and communicating persistent medical records between service providers that are semantically matched.

In embodiments, the method of managing a medical record is performed in a medical record service system connectable with a metadata repository managing metadata and mapping rules for at least one data element included in the medical record. The medical record management method includes: querying a mapping rule for at least one data element included in a first career record; and if the mapping rule does not exist, generating a mapping rule for the data element And a requesting step. In one embodiment, the method may further include converting the first medical record based on the mapping rule if the mapping rule exists as a result of the inquiry. In one embodiment, the transforming may include generating a transform rule using the mapping rule and transforming the first medical record using the generated transform rule.

Among the embodiments, the method of managing a medical record is performed in a first medical record service system connectable with a metadata repository managing metadata and mapping rules relating to at least one data element included in the medical record. The method comprising: requesting a second care record from a second care record service system; requesting the meta data store for a mapping rule for at least one element contained in the second care record; And converting the second medical record into a first medical record based on the one mapping rule. In one embodiment, requesting the second care record includes receiving a request for a care record from a user's terminal and requesting the first care record associated with the user to a second care record service system . In one embodiment, requesting the second care record may include designating the second care record service system from the terminal of the user. In one embodiment, the step of requesting the mapping rule comprises extracting the at least one element from the second care record and requesting the meta data store for a mapping rule for the extracted at least one element . In one embodiment, the transforming step includes generating a transformation rule for the first care record using the at least one mapping rule and generating the transformation rule based on the transformation rule using the first care record as the second care record And a step of converting the data.

Among embodiments, a method of operating a metadata store is performed in a metadata store that manages metadata for medical records stored in at least one medical record service system. The method comprising: receiving at least one data element included in the first care record from a first care record service system; retrieving a mapping rule for the at least one data element; As a result, if there is no mapping rule, generating a mapping rule for the corresponding data element. In one embodiment, the step of retrieving the mapping rule comprises the steps of: the at least one data element - the first data element - and concepts corresponding to each other and the submitter having a data element different from the first service, 2 data element, and retrieving a mapping rule for the first and second data elements. In one embodiment, the step of generating the mapping rule may include comparing the value fields of the first and second data elements to generate a mapping rule. In one embodiment, the step of retrieving the second data element may comprise comparing context values of the metadata for the first and second data elements. In one embodiment, the meta data store operating method may further include providing the mapping rule to the first care record service system if the mapping rule is found as a result of the search.

In embodiments, the metadata repository is connectable to at least one medical record service system. Wherein the metadata store comprises a storage unit for storing a mapping rule for at least one data element included in a medical record, and a mapping rule for a medical record stored in the at least one medical record service system is retrieved from the metadata storage unit And a controller.

The method of managing a medical record and the metadata repository for the method of the present invention can guarantee the semantic operability of a medical record using metadata.

The method of managing medical records and the metadata repository for the method according to an embodiment of the present invention can guarantee and exchange continuous medical records between semantically identical service providers.

1 is a block diagram for explaining an embodiment of a medical record management system to which the disclosed technique can be applied.
FIG. 2 is a block diagram for explaining an embodiment of the medical record service system of FIG. 1;
FIG. 3 is a block diagram for explaining one embodiment of a medical record management method performed in the medical record service system of FIG. 2;
4 is a flow chart for one embodiment of the method of managing care records of FIG.
FIG. 5 is a block diagram for explaining another embodiment of a medical record management method performed in the medical record service system of FIG. 2. FIG.
FIG. 6 is a block diagram for explaining an embodiment of the metadata repository of FIG. 1;
FIG. 7 is a block diagram illustrating an embodiment of a metadata repository operation method performed in the metadata repository of FIG. 6. Referring to FIG.

The description of the disclosed technique is merely an example for structural or functional explanation and the scope of the disclosed technology should not be construed as being limited by the embodiments described in the text. That is, the embodiments are to be construed as being variously embodied and having various forms, so that the scope of the disclosed technology should be understood to include equivalents capable of realizing technical ideas.

Meanwhile, the meaning of the terms described in the present application should be understood as follows.

The terms "first "," second ", and the like are intended to distinguish one element from another, and the scope of the right should not be limited by these terms. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

It should be understood that the term "and / or" includes all possible combinations from one or more related items. For example, the meaning of "first item, second item and / or third item" may be presented from two or more of the first, second or third items as well as the first, second or third item It means a combination of all the items that can be.

It is to be understood that when an element is referred to as being "connected" to another element, it may be directly connected to the other element, but there may be other elements in between. On the other hand, when an element is referred to as being "directly connected" to another element, it should be understood that there are no other elements in between. On the other hand, other expressions that describe the relationship between components, such as "between" and "between" or "neighboring to" and "directly adjacent to" should be interpreted as well.

It should be understood that the singular " include "or" have "are to be construed as including a stated feature, number, step, operation, component, It is to be understood that the combination is intended to specify that it does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

In each step, the identification code (e.g., a, b, c, etc.) is used for convenience of explanation, the identification code does not describe the order of each step, Unless otherwise stated, it may occur differently from the stated order. That is, each step may occur in the same order as described, may be performed substantially concurrently, or may be performed in reverse order.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the disclosed technology belongs, unless otherwise defined. Commonly used predefined terms should be interpreted to be consistent with the meanings in the context of the related art and can not be interpreted as having ideal or overly formal meaning unless explicitly defined in the present application.

The disclosed technique provides a methodology that satisfies syntactic and semantic interoperability for electronic medical records (hereinafter referred to as medical records). In order to satisfy such syntactic and semantic interoperability, the disclosed technique uses semantic data to ensure semantic interoperability for medical records having different formats. In general, metadata is a unit that describes the syntax and semantics of data. ISO / IEC 11179 is proposed by the International Standards Organization (ISO) as a standard for the management of metadata.

In the disclosed technique, the medical record is not necessarily limited to one format. In other words, the sender and recipient have different types of medical records, and the disclosed technique utilizes a metadata repository to ensure that one type of medical record maintains semantic consistency with other types of medical records So that they can be exchanged. These medical records may include continuing medical records. Therefore, hereinafter referred to collectively as a medical record, this medical record means including a continuous medical record.

The disclosed technique can implement metadata based on the international standard ISO / IEC 11179. Thus, the metadata storage system referred to by the disclosed technology (hereinafter referred to as the metadata store) may correspond to the MetaData Registry (MDR) according to the international standard ISO / IEC 11179. The disclosed technique describes a method of exchanging medical records and a metadata repository for the same, which can secure syntactic and semantic interoperability using such a metadata repository.

1 is a block diagram illustrating an embodiment of a medical record system to which the disclosed technology may be applied.

Referring to FIG. 1, a medical record system includes a user terminal 110, 111, a medical record service system 120, 121, and a metadata store 130. As shown, each of the care record service systems 110 and 111 can access at least one user terminal 120 or 121 simultaneously or sequentially. As shown, one user terminal may connect to a plurality of care record service systems. In addition, although two medical record service systems 120 and 121 are shown here, this is for convenience of description, and the disclosed technology can be applied to a case having three or more medical record service systems.

The user terminals 110 and 111 may access the medical record service systems 120 and 121 using wired / wireless communication. The user terminals 110 and 111 may display to the user a request related to the medical record of the user or a received response according to the input of the user.

The medical record service system 120,121 may use the metadata store 130 to provide a medical record (including a continuing medical record) to the user terminal 110,111. The medical record service system 120, 121 will be described in detail below with reference to Figs. 2 to 5.

The metadata store 130 may store and manage metadata for the medical record. The metadata store 130 may store at least a portion of the medical record and use it to manage the matching rules of the metadata. In one embodiment, the metadata store 130 may correspond to a MetaData Registry (MDR) constructed in accordance with the international standard ISO / IEC 11179. Such a metadata store 130 will be described in detail below with reference to FIGS. 6 to 8. FIG.

Here, the medical record may be configured in accordance with ISO / IEC 11179. Accordingly, the medical record may be composed of a data element, which is a basic unit of data managed in the metadata repository 130. A data element may comprise an object class, a property, and a representation. An object class is an idea, an abstract, or a set of objects in the real world, and an explicit range, meaning, attribute, and behavior are defined by the same rule. Properties represent the general characteristics of members within an object class. Representation is a question of how to represent data, which can mean value domain, data type, and so on.

FIG. 2 is a block diagram for explaining an embodiment of the medical record service system of FIG. 1; FIG. 3 is a block diagram for explaining an embodiment of a medical record management method performed in the medical record service system of FIG. 2, and FIG. 4 is a flowchart of another embodiment of the medical record management method of FIG. FIG. 5 is a block diagram for explaining another embodiment of a medical record management method performed in the medical record service system of FIG. 2. FIG.

Hereinafter, the medical record service system 120, 121 will be described with reference to FIG. 2 to FIG. For convenience of explanation, contents of the medical record service system 120 and 121 performed by the first medical record service system 120 and the second medical record service system 121 are separately described, It goes without saying that the recording service system 120, 121 can perform the operation of the medical record service system with respect to each other. Here, the medical record service system 120, 121 uses a different type of medical record, even though their operations correspond to each other. Hereinafter, the medical record used in the first medical record service system 120 is referred to as a first medical record, and the medical record used in the second medical record service system 121 is referred to as a second medical record.

Referring to FIG. 2, the medical record service system 120 may include a communication unit 210, a medical record storage unit 220, an authentication unit 230, and a control unit 240.

The communication unit 210 may communicate with at least one of the user terminal 110, the other medical record service system 121 and the metadata repository 130 under the control of the control unit 240.

The medical record storage unit 220 may store a first medical record for a user registered in the medical record service system 120. The medical care record storage unit 220 may temporarily store the second medical care record received from the second care record service system 121. [ Here, the received second medical care record may be converted into the first medical care record under the control of the control unit 240, and the medical care record storing unit 220 may store the converted first medical care record. A detailed description thereof will be described later with reference to Figs. 3 to 5.

The authentication unit 230 may perform authentication when communication is performed under the control of the control unit 240. [ For example, the authentication unit 230 may authenticate an authorized user to the user terminal 110 accessing the medical record service system 120. The authentication unit 230 may authenticate to the metadata store 130 that the medical record service system 120 is an authorized system when initiating communication with the metadata repository 130. [

The control unit 240 may control each component of the medical record service system 120 to perform a series of operations. The specific operation (the medical record management method) by the control unit 240 will be described with reference to Figs. 3 to 5. Fig.

Referring to FIG. 3, an embodiment of a method for managing a medical record includes requesting a second medical record from a second medical record service system (step S310), mapping rules for at least one element included in the second medical record To the metadata store 130 (step S320) and converting the second medical record to a first medical record based on the at least one mapping rule (step S320).

3, the method of managing a medical record can be performed by sequentially executing a medical record exchange process (steps S410 to S420) and a medical record conversion process (steps S40 to S40) +

The medical record exchange process can be performed in the following steps. Upon receiving a request for a care record from the user terminal 110, the first care record service system 120 may request the second care record service system 121 for the corresponding care record (second care record) S410). Here, the second care record service system 121 receives the designation of the second care record service system 121 from the user terminal 110, or can determine the second care record service system 121 according to predetermined contents have.

In one embodiment, a predetermined authentication procedure may be performed between the first and second care record service systems. More specifically, when the first care record service system 120 requests a connection to the second care record service system 121, the second care record service system 121 is connected to the first care record service system 120 You can verify that it is a pre-registered system and that you are performing a legitimate connection. If it is a pre-registered system and not a legitimate connection, the second care record service system 121 may send a reject message and forcibly block the connection. If the connection is permitted as a legitimate connection as the pre-registered system, the first care record service system 120 may transmit information on the user and information on the extent of the requested data to the second care record service system 121 . Here, the first and second care record service systems 120 and 121 may perform predetermined encryption and decryption to maintain security with respect to information on the user and information on the range of the requested data. The second medical record service system 121 confirms that the user has stored the data of the range of the legitimate and requested data, and if so, documents and encrypts the data after the retrieval, (120). If the user is not legitimate or the data of the requested data range is not stored, the second care record service system 121 may forcibly block the connection after transmitting the absence message. Here, the document refers to a process of transforming the type of data stored in the second care record service system 121 into a form suitable for a medical record standard (for example, a standard of continuous medical record). In performing the documentation, extensions within the range that do not significantly impair the standard may be tolerated according to the needs of the care record service system.

Upon receiving the second care record from the second care record service system 121, the first care record service system 120 may complete the exchange process by temporarily storing the received second care record (step S420).

Thereafter, the first care record service system 120 may perform the care record conversion process. The outline of the medical record conversion process occurs between the first medical record service system 120 and the metadata repository 130. The first care record service system 120 generates a conversion rule (a series of rules for converting the received second care record into the first care record) with reference to the data stored in the meta data store 130, And a procedure for applying the conversion rule to the temporarily stored second medical record to generate a medical record (first medical record) in a form suitable for the system of the user.

To describe the medical record conversion process in more detail, the first care record service system 120 may access the metadata store 130 to request a mapping rule for the medical record (step S430). Upon receiving the mapping rule from the meta data store 130, the first care record service system 120 generates a conversion rule based on the received mapping rule (step S440) The record can be converted into the first medical record (step S450). More specifically, in one embodiment, the first care record service system 120 converts the portion of the second care record corresponding to the data element to which the received mapping rule can be applied, using the received mapping rule The portion of the first medical record that is generated as part of the first medical record and that does not receive the mapping rule or does not correspond to the first medical record may be stored or discarded separately. The first care record service system 120 may apply the conversion rules to save the converted content into the first care record and terminate the care record conversion process by discarding the temporarily stored second care record.

In one embodiment, a procedure for predetermined authentication may be performed between the first care record service system 120 and the metadata repository 130. In more detail, when the first care record service system 120 attempts to access the metadata store 130, the metadata store 130 is the system in which the first care record service system 120 is registered, It is possible to confirm whether or not the connection is legitimate. If it is a registered system and it is confirmed that it is a legitimate connection, the following procedure is performed, otherwise the metadata store 130 may send a connection rejection message to the corresponding system 120 and forcibly block the connection.

In one embodiment, requesting a mapping rule (step S430) may include the following steps. The first care record service system 120 can identify the type of the second care record temporarily stored and extract at least one data element included in the second care record with reference to the corresponding standard. The first care record service system 120 may request a mapping rule for at least one extracted data element. For example, the first care record service system 120 may request an inquiry to the metadata store 130 sequentially for the extracted at least one data element. The meta data store 130 that has been requested to inquire about the data element checks whether the corresponding element is stored. If the element is stored, it performs the following procedure. If not, it performs the inquiry about the next data element after transmitting the absence message . This sequential inquiry can be repeated until all of the at least one requested data element is performed. If the data element is found to be stored, the meta data store 130 stores (i) the data element concept is the same as the corresponding data element (hereinafter, the first data element) and (ii) Data element) is present. If a second data element is present, the metadata store 130 may retrieve whether there is a mapping rule for the queried data element pair (first and second data elements). If a mapping rule exists, the metadata store 130 may provide the mapping rule to the first clinic service system 120. If a mapping rule does not exist, the metadata store 130 may create a mapping rule for that data element. For example, the metadata store 130 may compare the value fields of the first and second data elements to generate a mapping rule. Alternatively, the metadata store 130 may receive the mapping rules from the user terminal 110 being connected to the first care record service system 120, store the mapping rules and provide them to the first care record service system 120 . Here, the mapping rule may be created immediately after storing the data element received from the first care record service system 120 in the metadata store 130, or may be generated by the user at some point thereafter . If the mapping rules can not be created, the metadata store 130 may send a missed message to the system 120 and retrieve the mapping rules for the next data element. Once all data elements have been retrieved, the metadata store 130 may send a normal job completion message and terminate the connection to the system 120.

In one embodiment, a query on a data element may perform a query by performing a query on the context value of the metadata (e.g., Google health, MS vault, etc.). This is because the inquiry for the data element includes an inquiry for the service provider.

In one embodiment, a predetermined procedure may be performed to terminate this connection if an abnormal connection or termination occurs. For example, when the first care record service system 120 is connected to the metadata store 130, if an abnormal termination occurs or there is no response within a certain period of time, After the stored second medical record is destroyed, the procedure of exchanging the medical record with the second medical record service system 121 can be retried.

Referring to FIG. 5, another embodiment of the medical record management method includes a step S510 of querying the metadata storage 130 for a mapping rule for at least one data element included in the first career record (step S510) If the result mapping rule does not exist, requesting the metadata store 130 to generate a mapping rule for the data element (step S520). In one embodiment, the method may further include the step of converting the first medical care record into the second medical care record based on the mapping rule if the retrieved result mapping rule exists. 5 corresponds to the contents described with reference to FIG. 4, so that a more detailed description thereof will be omitted.

FIG. 6 is a block diagram illustrating an embodiment of the metadata repository of FIG. 1, and FIG. 7 is a block diagram illustrating an embodiment of a metadata repository management method performed in the metadata repository of FIG. Hereinafter, the metadata storage 130 will be described with reference to FIGS.

Referring to FIG. 6, the metadata repository 130 may include a communication unit 610, a metadata storage unit 620, an authentication unit 630, and a control unit 640. In one embodiment, the metadata store 130 may further include a matching rule generator 650.

The communication unit 610 may perform communication with at least one medical record service system 120 or 121 under the control of the control unit 640.

The metadata storage unit 620 may store metadata for at least one medical record. The metadata storage unit 620 may store at least one of at least one data element for the medical record and a mapping rule therefor.

The authentication unit 630 may perform authentication when communication is performed under the control of the control unit 640. [ For example, the authentication unit 630 may authenticate the medical record service system that accesses the metadata repository 130 as an authorized system.

The control unit 640 may control each component of the meta data store 130 to perform a series of operations. The control unit 240 may search the meta data storage unit 620 for a mapping rule for the medical record stored in the medical record service system 120 and provide the same. That is, when the mapping rule for at least one data element included in the medical record from the first care record service system 120 is retrieved from the metadata storage unit 620 and the corresponding mapping rule is retrieved, (120). The concrete operation (method of operating the metadata storage) by the control unit 240 will be described with reference to FIG.

The matching rule generation unit 650 may generate a matching rule for data elements under the control of the control unit 640. [ A detailed description thereof corresponds to the medical record conversion process with reference to FIG. 4, so that detailed description thereof will be omitted here.

Referring to FIG. 7, a method of operating a meta data store includes receiving at least one data element included in a first medical record from a first care record service system 120 (step S710) (Step S720) of generating a mapping rule for the corresponding data element if the mapping rule is not found (step S730).

In one embodiment, step S720 may be based on the assumption that at least one data element (first data element) and (i) concepts correspond to each other, and (ii) the submitter receives data from the first care record service system 120 and other data elements Element) and searching for a mapping rule for the first and second data elements. Here, the metadata store 130 may retrieve the second data element by comparing the context values of the metadata for the first and second data elements. In another embodiment, step S720 may include comparing the value fields of the first and second data elements to generate a mapping rule.

The disclosed technique may have the following effects. It is to be understood, however, that the scope of the disclosed technology is not to be construed as limited thereby, as it is not meant to imply that a particular embodiment should include all of the following effects or only the following effects.

The method of managing the medical records according to the disclosed technique may enable a multi-party exchange of continuous medical records that will be the most likely form of health record in the near future. Thus, it is possible to exchange and integrate personal health records scattered among various institutions, thereby satisfying the potential needs of users such as patients and doctors for the continuous medical records.

In addition, since the medical record management method according to the disclosed technology can perform the authentication procedure for the medical record at each stage of the invention, the user can conveniently use the medical information without worrying about leakage of his or her health information.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the following claims It can be understood that

110, 111:
120,121: Medical record service system
130: Metadata Repository

Claims (14)

delete delete delete delete delete delete delete delete A method of operating a meta data store performed in a meta data store managing meta data for a medical record stored in at least one medical record service system,
Receiving an inquiry request for at least one data element included in the first medical record from a first medical record service system;
Retrieving a mapping rule for the at least one data element;
Generating a mapping rule for the corresponding data element if the mapping rule is not found, and providing the mapping rule to the first care record service system if the mapping rule exists; And
If the mapping rule can not be generated, transmitting a missed message to the first care record service system and retrieving a mapping rule for the next data element.
10. The method of claim 9, wherein searching for the mapping rule
If it is determined that the at least one data element has been stored beforehand, the concept of the data element is the same as that of the corresponding data element (hereinafter referred to as a first data element) Searching for the presence or absence of the presence; And
And retrieving a mapping rule for the first and second data elements.
11. The method of claim 10, wherein generating the mapping rule comprises:
And generating a mapping rule by comparing the value areas of the first and second data elements with each other.
11. The method of claim 10, wherein the step of retrieving the second data element
Comparing the context values of the metadata for the first and second data elements.
delete In a metadata repository connectable with at least one medical record service system,
A metadata storage for storing a mapping rule for at least one data element included in the medical record;
Receiving an inquiry request for at least one data element included in the first care record from a first care record service system, searching the meta data store for a mapping rule for the at least one data element, As a result, if there is the mapping rule, the control unit provides the mapping rule to the first care record service system; And
Generating a mapping rule for the corresponding data element if the mapping rule is absent and generating a matching rule for searching the mapping rule for the next data element if the mapping rule is not generated, And a generating unit.
KR1020150011482A 2015-01-23 2015-01-23 Method for managing electronic medical record and metadata storage system thereof KR101892161B1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
KR1020150011482A KR101892161B1 (en) 2015-01-23 2015-01-23 Method for managing electronic medical record and metadata storage system thereof
PCT/KR2015/013627 WO2016117826A1 (en) 2015-01-23 2015-12-11 Medical record management method and metadata repository therefor

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020150011482A KR101892161B1 (en) 2015-01-23 2015-01-23 Method for managing electronic medical record and metadata storage system thereof

Publications (2)

Publication Number Publication Date
KR20160091169A KR20160091169A (en) 2016-08-02
KR101892161B1 true KR101892161B1 (en) 2018-10-04

Family

ID=56417315

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020150011482A KR101892161B1 (en) 2015-01-23 2015-01-23 Method for managing electronic medical record and metadata storage system thereof

Country Status (2)

Country Link
KR (1) KR101892161B1 (en)
WO (1) WO2016117826A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109411079B (en) * 2018-09-11 2023-07-07 平安科技（深圳）有限公司 Method, device, computer equipment and storage medium for generating auditing diagnosis and treatment rules

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013537326A (en) * 2011-08-31 2013-09-30 アピシオ，インク． Medical Information Navigation Engine (MINE) system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8065336B2 (en) * 2004-12-20 2011-11-22 Fujitsu Limited Data semanticizer
US8583694B2 (en) * 2005-05-09 2013-11-12 Atlas Development Corporation Health-care related database middleware
KR20120012923A (en) * 2010-08-03 2012-02-13 서울대학교산학협력단 System and method for managing medical infirmation using clinical contents model and apparatus for processing clinical contents model markup language
KR101320572B1 (en) * 2012-02-15 2013-10-28 주식회사 메타헬스 System and method for medical treatment pattern based on electronic medical record

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013537326A (en) * 2011-08-31 2013-09-30 アピシオ，インク． Medical Information Navigation Engine (MINE) system

Also Published As

Publication number Publication date
KR20160091169A (en) 2016-08-02
WO2016117826A1 (en) 2016-07-28

Similar Documents

Publication Publication Date Title
US20190268340A1 (en) Method and apparatus generating and applying security labels to sensitive data
KR101200814B1 (en) Method and system for personal health record management based on short range radio communication
US20160156630A1 (en) Cross-Enterprise Workflow
KR20200016458A (en) Blockchain-based phr platform server operating method and phr platform server operating system
US20140109239A1 (en) Collaborative cloud-based sharing of medical imaging studies with or without automated removal of protected health information
EP3891690B1 (en) Intelligent meta pacs system and server
CN102760206A (en) System and method for sharing cross-regional medical image information
US10216940B2 (en) Systems, methods, apparatuses, and computer program products for truncated, encrypted searching of encrypted identifiers
Ermakova et al. Security and Privacy System Requirements for Adopting Cloud Computing in Healthcare Data Sharing Scenarios.
KR20210067353A (en) Method and system for storing and providing medical records by strengthening individual's control over medical records with multi-signature smart contract on blockchain
Kilic et al. Providing interoperability of ehealth communities through peer-to-peer networks
Aboelfotoh et al. A mobile-based architecture for integrating personal health record data
KR20200134744A (en) Method and system for accessing information of medical treatment for patients
KR101892161B1 (en) Method for managing electronic medical record and metadata storage system thereof
KR20120115438A (en) Method for exchanging electronic health record and metadata storage system thereof
Kuhlisch et al. Electronic case records in a box: Integrating patient data in healthcare networks
US20150149209A1 (en) Remote/local reference sharing and resolution
KR101706183B1 (en) Method for managing integrated medical information
Rubio et al. A robust and simple security extension for the medical standard SCP-ECG
Ma et al. OpenID Connect as a security service in cloud-based medical imaging systems
JP6078459B2 (en) Information management system and its data linkage method
JP5499148B1 (en) Data access control apparatus and method
Gómez et al. Cloud architecture for electronic health record systems interoperability
Koutsoukos et al. Emergency Health Protocols Supporting Health Data Exchange, Cloud Storage, and Indexing.
Delgado et al. Security and Privacy in a DACS

Legal Events

Date Code Title Description
A201 Request for examination
N231 Notification of change of applicant
N231 Notification of change of applicant
E902 Notification of reason for refusal
E90F Notification of reason for final refusal
E902 Notification of reason for refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant