KR101434608B1 - Apparatus and Method for Managing Information, and Computer-Readable Recording Medium - Google Patents

Abstract

The present invention relates to an information management apparatus, an information management method, and a computer-readable recording medium, and an information management apparatus according to an embodiment of the present invention includes a parsing unit parsing input first information to decompose fields, A mapping unit for generating mapping data using a GUI-based tool to generate second information based on the mapping information, a conversion unit for converting the first information with reference to the mapping data, And the like.

Description

[0001] The present invention relates to an information management apparatus, an information management method, and a computer-readable recording medium,

The present invention relates to an information management apparatus, an information management method, and a computer-readable recording medium. More particularly, the present invention relates to a medical information system, such as a medical information system such as HL7 (Health Level Seven) An information management method, and a computer-readable recording medium capable of generating and managing a new message using a GUI (Graphical User Interface) -based exchange standard message and further linking with a database.

Many medical information systems related to EMR (Electronic Medical Record) and EHR (Electronic Health Record) are being developed due to the efforts for computerization of information in medical and health care fields. However, since information structures in hospital-run medical information systems, such as databases and data structures, are often different from these standards, a commitment to information exchange is needed. Therefore, the CDM (Clinical Document Architecture) [g] of HL7, DICOM, and HL7, the Continuity of Care Document (HL7 CDA R2) of HL7, and the CCR (Continuity of ASTM) of the HL7 are used for interoperability between existing medical information systems. of Care Document) have been developed. The information exchange between medical information systems can be smoothly performed by transmitting and receiving the medical information generated through the medical information system according to the medical standard.

In particular, various HL7 parsers developed by research institutes and companies for the past decades and an HL7 interface engine (Interface Engine) have been developed based on the need for tools to generate and interpret HL7 V. 2 messages for information exchange using HL7 . These interface engines are developed in computer programming languages. Intervention of program experts is essential to develop a separate application program that generates actual HL7 messages using these engines and operate them in conjunction with the actual hospital information system. That is, in order to generate HL7 message, only necessary data among a lot of data stored in the information system should be selected, and these data should be designed to be located at a specific position of the HL7 message. HL7 message engine And transmits it through the network. In addition, the receiving side information system performs parsing of the received HL7 message using the HL7 interface engine, and it is necessary to modify or store the parsed data into a specific form. Therefore, even if the information system of each hospital uses the HL7 interface engine, intervention of the program specialist is essential to utilize the transmitted information according to the characteristics of the information system of each institution.

However, the conversion of medical information should use the subjective requirements of medical practitioners and various conversion methods according to the situation. These requirements should be applied to the hospital information system. Therefore, although a series of development tasks that transfer these needs to the program developer and develop them can be stable, it requires a lot of time and effort. For example, agency work may be dependent on program professionals, or development may be delayed due to conceptual differences that arise during the course of task presentation.

In order to solve these problems, it has been possible to minimize the intervention of programmers through products such as Orion's Symphony, Interfaceware's IGUANA and Altova's Mapforce, and to easily exchange information using a convenient GUI (Graphical User Interface) .

However, these tools use a proprietary HL7 parser as a commercial tool, and there is a problem that a customizing work is required to apply to the hospital information system which is being developed and operated.

For example, in the medical information system according to the embodiment of the present invention, a medical person directly generates a health information exchange standard message such as HL7 based on his medical knowledge, generates and manages a new message using a GUI-based tool, And an object of the present invention is to provide an information management apparatus, an information management method, and a computer readable recording medium.

The information management apparatus according to an exemplary embodiment of the present invention includes a parsing unit parsing input first information to decompose a field, a graphical user interface (GUI) -based parser for generating second information by the first information, A mapping unit for generating mapping data using a tool, a conversion unit for converting the first information with reference to the mapping data, and an integration unit for integrating the converted first information to generate the second information.

The information management apparatus further includes an interface unit for encoding and outputting the generated second information.

The information management apparatus may further include a field mapper converting the connection information between the fields expressed in a tree structure using the tool into a program code and providing the converted code to the conversion unit. do.

And the converting unit changes the field order of the first information.

The information management method according to an embodiment of the present invention includes parsing the input first information to decompose fields, generating mapping data using a GUI-based tool to generate second information based on the first information, Converting the first information with reference to the mapping data, and generating the second information by integrating the converted first information.

The information management method may further include encoding and outputting the generated second information.

The information management method further includes converting the connection information between the fields expressed in a tree structure using the tool into a program code, and providing the converted code at the time of converting the first information. do.

Further, the step of converting the first information is characterized by changing the field order of the first information.

A computer-readable recording medium according to an embodiment of the present invention is a computer-readable recording medium including a program for executing an information management method, the information management method comprising the steps of: parsing input first information to decompose a field Generating mapping information by using a GUI-based tool to generate second information based on the first information, converting the first information with reference to the mapping data, And generating the second information by integrating.

1 shows a medical information system according to an embodiment of the present invention,
FIG. 2 is a diagram illustrating a GUI screen displayed on the first terminal of FIG. 1;
FIG. 3 is a block diagram illustrating the structure of the first or second information management apparatus of FIG. 1,
4 is a diagram showing a conceptual model of the transmitter of FIG. 1,
5 is a diagram specifically illustrating the operation of FIG. 4,
Figure 6 is a diagram illustrating a conceptual model of the receiver of Figure 1;
FIG. 7 is a diagram specifically illustrating the operation of FIG. 6,
8 is a view for explaining the architecture of the HL7 toolkit according to the embodiment of the present invention,
9 is a diagram illustrating a data structure for graphical display of a field mapper,
10 shows a group diagram of information items,
11 is a partial group diagram of the HL7 interface engine,
12 illustrates an exemplary message according to an embodiment of the present invention,
13 is a diagram for explaining the connection between the HL7 toolkit and the HL7 interface engine according to the embodiment of the present invention, and
14 is a flowchart illustrating an information management method according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a view showing a medical information system according to an embodiment of the present invention, FIG. 2 is a view illustrating a GUI screen displayed on the first terminal of FIG. 1, FIG. 2 is a block diagram illustrating a structure of an information management apparatus. FIG. 4 is a diagram showing a concrete example of the operation of FIG. 4, FIG. 6 is a diagram showing a conceptual model of the receiver of FIG. 1, and FIG. 7 is a diagram 6 is a view specifically expressing the operation of FIG.

As shown in FIG. 1, the medical information system according to the embodiment of the present invention includes a transmitter 100 and a receiver 110.

Here, the HL7 message is generated and transmitted based on the transmitter 100, that is, the database of the sender information system. The receiver 110 analyzes the received HL7 message and stores it in the database, You can return a message. For example, the following scenario may be assumed for the generation of a message. "Adds new allergies to penicillin, a 1953 outpatient named Hune Cho." To this end, the transmitting side may generate an HL7 message in the form of ADT_A60 (update adverse reaction information) and send it to the receiver to request the update of the information.

The transmitter 100 may include some or all of the first terminal 101, the first information management device 103, and the first database 105 to perform the above functions. Here, the part or all of the information is included in the first terminal 101 under the name of the information generating section, or the first database 105 is stored in the first terminal 101 under the name of the storage section, Information management apparatus 103 and further that the first database 105 may be integrated into the first terminal 101 under the name of a memory section, Explain that they are all included to help.

The first terminal 101 is a device for displaying a GUI screen for generating a medical information message such as a desktop computer, a notebook computer, a mobile phone, etc., for example, mapping data for generating an HL7 message. 2, a non-programmer who can not participate in the generation of an unprofessional, more precisely, an HL7 message by using a GUI screen displayed on the first terminal 101, It is reference information that enables to generate and transmit a desired message.

2, the first terminal 101 provides a user-friendly GUI for generating mapping data between fields, thereby making it possible for the program specialist to conveniently manage data. Most of the computer programs are composed of text, so in order to use a program, it is necessary to understand the grammar of a specific program. However, one of the easiest ways for people to understand such a structure is how to express information in a graph or tree structure. Therefore, the embodiment of the present invention expresses the information structure in the form of a graph and a tree as shown in FIG. 2, and connects the lines simply by using a mouse to generate connection information between the fields represented by the tree. The connection information generated graphically by the user is automatically converted into program code through a field mapper so that it can be referred to by a computer program, a data translator. We will discuss this in more detail later.

For example, as shown in FIG. 2, the GUI of the HL7 toolkit according to the embodiment of the present invention can be divided into four areas for each function. (1) is a menu and a shortcut button necessary for program operation, and is a control panel (or control area) for functions related to program storage, retrieval, database connection, and start and end of parsing. ② is a panel for user to generate mapping data. In this panel, mapping information between fields is represented by a line, and a specific information structure is expressed in a tree form. ③ indicates the elements of information that can generate mapping data. For example, if the input HL7 message is ADT_A01, you can select the ADT_A01 item in this panel, insert it in ② panel, and perform the mapping operation. ④ is a panel that provides information on program usage. Through this panel, the user can check information such as data input / output information, system status, and usage history.

Also, the first information management device 103 may be a kind of server, and may be linked to the first database 105. [ The first information management apparatus 103 may include a controller, not shown separately in the figure, and may store a HL7 toolkit, a kind of program or algorithm, for example, as shown in FIG. 1, And a first interface unit 103_2 for performing communication with an external device. For example, the toolkit according to the embodiment of the present invention may be configured as an independent program in the first information generating unit 103_1 as shown in FIG. 2, Or as an attachment module of the system.

3, the first information management apparatus 103 according to the embodiment of the present invention includes an input unit 300, a parsing unit 310, a mapping unit 320, a conversion unit 330 ), An integrating unit 340, and an output unit 350. [0035] The inclusion of some or all of them in this specification means that some of the constituent elements may be omitted or integrated into other constituent elements, and the description is made to include all of them in order to facilitate a sufficient understanding of the invention.

As will be described later, the first information management apparatus 103 according to the embodiment of the present invention can receive medical information, that is, first information, about the patient through the input unit 300. In this case, the medical information is, for example, medical information provided from another server through the Internet in the form of an existing HL7 message, or medical information that can be provided in various ways. For example, it may be medical information provided in the first database 105 of FIG. 1, or medical information provided through network communication with the outside via a socket.

The parsing unit 310 parses or decomposes the input message. Here, parsing of a message may be understood as distinguishing between fields.

The mapping unit 320 generates mapping data based on a tree structure created by a user, that is, a program non-expert, connecting lines on the screen through a GUI screen displayed on the screen. The mapping data may be data to be referred to when generating new medical information, that is, second information, within a range that does not deviate from standard specifications of the medical system, for example, using the medical information input to the input unit 300, i.e., first information.

The conversion unit 330 converts the parsed message in the parsing unit 310 based on the mapping data provided by the mapping unit 320 and outputs the message. Here, the conversion may mean converting the order between fields, rearranging the data in the field, or the like, and may also mean creating a new field between fields. Therefore, in the embodiment of the present invention, the meaning of conversion is not particularly limited.

The integrating unit 340 integrates the inter-field data converted by the converting unit 330. Here, the integration means that the first information input to the input unit 300 is converted into new second information. That is, a data format for outputting data to the outside is newly formed. However, such an integration unit 340 may be omitted in the first information management apparatus 103. [ In other words, the conversion unit 330 may directly output the converted second information.

The output unit 330 outputs the second information generated by the integration unit 340 to the first interface unit 103_2 of FIG. The output unit 330 may include a connector for connection with the first interface unit 103_2, but may be omitted from the first information management apparatus 100. [

The first interface unit 103_2 of the first information management apparatus 103 may convert and transmit the second information provided by the output unit 330. [ For example, the first interface 103_2 can be transmitted to the network after the process as shown in FIG. The basic information necessary for the generation of the HL7 message is transformed using the information of the database of the medical information system and the functions provided by the HL7 toolkit when the data type differs from the data type of the HL7 message. The additional information not included in the database is directly input by the user. This information could be used to generate HL7 messages in string form via the HL7 encoder.

FIG. 5 is a diagram showing in detail the operation concept of FIG. 4. FIG. 5 (a) designates an input form, which means information is extracted from the database of the medical information system. (b) and (c) show patient information and physician information related to HL7 message generation in the database of the medical information system, respectively. And (c) are functions provided by the HL7 toolkit for modifying data in the database to fit the HL7 data type. For example, in a transmitting-side information system, the patient's gender should be expressed as M: 1, F: 0, while in HL7, M: M, F: F. Thus, a function called Equals (ie, if the input data is equal to 1, the output is changed to M, otherwise it is defined by the user). Then, the user directly inputs information through (f). This information is combined with the fields of (e) indicating the message structure of ADT_A60 to perform encoding for generating the HL7 message. However, since the structure of the HL7 message is complex, fields to be created for convenience can be separately created through (f). And (g) means that the generated HL7 message is transmitted through the network. In some cases, as shown in FIG. 5, it may be confirmed in the form of text through the GUI.

The first database 105 may store the medical information of the patient created by the medical person through the first terminal 101 or may store the medical information of the patient provided by communication with the outside. The stored information may be output at the request of the first terminal 101. In addition, the first database 105 may further provide necessary information when the first information management apparatus 103 performs a process such as information conversion.

On the other hand, the receiving unit 110 may include some or all of the second information management apparatus 111, the second terminal 113, and the second database 115. Here, it is not so different from what is described in the transmitter 100 that some or all of them are included, and further explanation will be omitted.

The second information management apparatus 111 may receive the second information, for example, the HL7 message, which is newly generated and transmitted by the transmission unit 100, and may perform a decoding process or the like through the second interface unit 111_1. And stores the resultant in the second database 115 and returns an acknowledgment (ACK) message to the transmitter 100. In this regard, the second information management apparatus 111 may further include an acknowledgment message generating unit for generating an acknowledgment message unlike the first information managing apparatus 103. [

6, the HL7 message transmitted to the network is analyzed through the HL7 decoder as shown in FIG. 6 and then reflected in the database, that is, the second database 115 do. Then, an acknowledgment message of the transmitted message is generated and transmitted to the sender. This may be achieved by a method in which a separate control unit transmits the response message generated by the acknowledgment message generating unit through the second interface unit 111_1.

FIG. 7 is a diagram specifically showing the operation of FIG. 6, wherein (h) means input of data through a network. (i) decodes and expresses the HL7 message transmitted over the network. (j) shows a table of the database connected as a sequence for searching a record related to a patient (Hune Cho) to be modified in the database of the receiving-side medical information system. The contents of the selected record and the contents related to the transmitted allergy are merged in (k) to modify the database through (g). In the IAM segment, Union and Equals functions are used to transform (A: addition, D: delete, etc.) the contents of existing data according to Allergy Action Code (eg, Allergy Action Code A is in the chartcontent table modify the database by merging the allergy information sent to the allergy information). (m), when the modification of the database is completed according to the transmitted message, the transmitting side generates a receiving response message and transmits the receiving response message to the transmitting side of the ACK-A60 message through the network at (n).

According to this process, the second terminal 113 can transmit the data stored in the second database 115 or the updated data stored in the second database 113 to check the recent medical records of a specific patient.

The second interface 111_1 and the second information generation unit 111_1, the second terminal 113 and the second database 115 of the second information management apparatus 111 of the other reception unit 110 except for this point, Is not much different from the first terminal 101 of the transmitter 100, the first information generator 103_1 and the first interface 103_2 of the first information management apparatus 103, and the first database 105, The above description is omitted. Here, the second information generation unit 111_1 may include an analysis unit for performing information analysis.

As a result of the above configuration, it is not easy to develop the HL7 message management program due to the difference in recognition of the medical information between the existing computer program developer and the medical person. However, according to the present invention, It is possible to directly generate the information, which facilitates information exchange.

FIG. 8 is a view for explaining the architecture of the HL7 toolkit according to the embodiment of the present invention, FIG. 9 is a diagram illustrating a data structure for graphical display of a field mapper, and FIG. 10 is a group diagram of information items. 11 is a partial group diagram of an HL7 interface engine, FIG. 12 is a diagram illustrating a message according to an embodiment of the present invention, and FIG. 13 is a diagram illustrating a connection between an HL7 toolkit and an HL7 interface engine according to an embodiment of the present invention FIG. 14 is a flowchart illustrating an information management method according to an embodiment of the present invention.

The HL7 toolkit according to the embodiment of the present invention is basically a tool for exchanging information between the HL7 message and the database of the medical information system. Therefore, this toolkit can be used not only to store the information contained in the HL7 message in the database of the medical information system but also to generate the HL7 message based on the information of the medical information system database or to generate another form of HL7 message from the HL7 message, It is also possible to exchange information between databases.

As can be seen from Fig. 8, the HL7 toolkit can input and output information in four forms. In the GUI context, it is possible to input and output HL7 message in the form of string such as keyboard input, data stored in file, network via socket, and HL7 message stored in database. In order to exchange information of the medical information system, it is possible to not only input and output information through the connection of the database but also a simple structure, for example, parsing and generating a string of structures separated by delimiters.

The HL7 toolkit is intended for parsing and generation of HL7 messages, and may therefore, for example, include an HL7 interface engine. However, the structure of the HL7 interface engine and the program need not be understood by the user, and only the structure of the information to be converted, such as the HL7 structure in the HL7 structure and the relational database of the information system, Only the connection information between the fields indicating the data to be converted in each information structure is designed through the field mapper represented by the GUI. The mapping data thus designed can be stored independently and this mapping data is used as basic information for information exchange in an information system in which a data translator is installed as shown in FIG. 8, An information exchange operation is performed in which data is reconstructed to generate new data. Here, the field represents a column of a table in the relational database, and may refer to a primitive data type for representing actual data in HL7.

FIG. 9 shows a data structure for graphical display of a field mapper. Since the mapping information designed by a user in the graphic panel must be converted into a computer-understandable format and stored, the components of the field mapper are It can be designed by dividing into branches. A graphical component for allowing a user to conceptually generate mapping data, an element for expressing mapping information designed by a user, that is, a NodeBean for representing each field information, An instance bean for representing information related to a specific information structure, and a LinkageBean for representing inter-field connection information, all of which can be managed by a single object included in the MappingDataBean. Also, the mapping data represented by one MappingDataBean object can be stored in a file by distributing Serializable Interface. In addition, this information enables graphical representations of information structure, connection information, and global mapping information through InstancePane, LinkagePane, and DesignPane graphical representation objects, respectively.

The HL7 toolkit according to the embodiment of the present invention basically deals with four kinds of information items (hereinafter referred to as information items). That is, IO-related items for specifying information input / output channels, Database-related items for representing table information through connection with databases, items for displaying messages in HL7 structure, Tool-related items that represent various tools for generating data. These items are classified into categories and can be selected and used by the user as shown in panel 3 of FIG. In addition, the items object overrides the encode () and decode () methods of the ItemBean so that each item object can perform encoding and decoding according to its own characteristics. For example, in the itemMaker_HL7_2_4 group item, the decode () method parses the HL7 message, and the decode () method creates the HL7 message. On the other hand, in the item object contained in the ItemMaker_Database group, the decode () method performs the operation of retrieving the database with a specific SQL query, and the encode () method performs the operation of storing the input data in the database. In addition, these items are designed to enable graphical representation using ItemPanel object, and to be able to add various kinds of information items in the future.

In order to use the mapping information designed by the HL7 toolkit, it is necessary to interwork with the HL7 interface engine as it must be able to parse and generate HL7 V.2.x messages. That is, it is necessary to display the result of parsing the inputted HL7 message through the HL7 interface engine on the user's screen in real time, or to transmit the data inputted by the user through the HL7 toolkit to the HL7 interface engine to generate the HL7 message. Therefore, it is effective to configure the object structure of the HL7 related module of the HL7 toolkit to be the same as the object structure of the HL7 interface engine. The data structure of the HL7 interface engine is designed to be similar to that of the HL7 standard message structure as shown in FIG.

FIG. 11 shows an object structure for a part of the ADT_A01 message structure of FIG. Here, the MSH segment is required and non-repeatable in ADT_A01, but in the HL7 interface engine, it is expressed as 1: n for consistency of the program, and only one MSH object needs to be programmed to exist as a policy. In addition, ADT_A01_INSURANCE is a group of [{IN1 [IN2] [{IN3}] [{ROL}]}] segments, and the attribute of this group is optional and repeatable. Here, the symbol '[]' means optional, and '{}' means repeatable.

The HL7 toolkit follows the same object structure as the message of the Interface Engine as shown in FIG. That is, by connecting the value of each field expressed by Tree to Node as an item of HL7 toolkit directly with the object of HL7 Interface Engine, the message can be parsed and generated effectively. However, in the HL7 toolkit, various information items such as database, IO, and tool exist in addition to HL7, so they are classified into a group of ItemBean in order to maintain consistency with them. .

14 is a flowchart illustrating an information management method according to an embodiment of the present invention.

For convenience of description, FIG. 14 is described with reference to FIG. 1 or FIG. 8, where the first information management apparatus 103 according to the embodiment of the present invention parses input first information to decompose fields (S1400). Here, the first information may be, for example, the first database 105 in which the first information management apparatus 103 cooperates as medical information of the patient, and may be information input via network communication with the outside.

Next, the first information management device 103 generates mapping data using a GUI-based tool (S1410). Here, the GUI-based tool may be a tool for a program non-specialist such as a medical person to construct a tree structure of information by simply connecting lines with a mouse using a graph displayed on the screen of the user's own terminal have.

Also, the first information management device 103 converts the decomposed first information, e.g., a message, based on the mapping data (S1420). Here, the conversion may mean changing the field order, changing the data structure in the field, or reordering the data, creating a new field in the field, and so on.

Thereafter, the first information management apparatus 103 merges the converted data to generate new second information, i.e., a new message (S1430). Of course, it is desirable that the newly generated message does not deviate from the standard of the medical system. Based on this, it is preferable that the process of converting the message in step S1420 satisfies this.

The first information management apparatus 103 may transmit the newly generated message to the reception unit 110 of the second information management apparatus 111 through an information conversion process such as encoding.

15 to 24 are diagrams for explaining a database management method (or an information management method) according to an embodiment of the present invention.

A database management method according to an embodiment of the present invention includes a method of sequentially searching for, modifying, and deleting a database by simply linking fields in a database table in a graphical interface (or an interface window). Here, the search may mean that the HL7 toolkit according to the embodiment of the present invention calls and processes the data stored in the table of the database 105 at the request of the user, for example, a physician.

Referring to FIGS. 15 to 24 together with FIG. 1 and FIG. 2, the information management apparatus according to the embodiment of the present invention clicks a specific item in a database table item list (see 3 of FIG. 2) A new item is created that can retrieve and modify the data stored in the table of the database 105 shown in FIG. 15 shows a screen in which an item of a table named patient is registered in the phr database.

If you right-click the [RECORDS] node in the table item (see 2 in FIG. 2) of FIG. 15, a new window is displayed. Through this window, all the records stored in the current table can be checked . For example, you can enter the SQL Query directly in the upper text input window of FIG. 16 and check the result.

There are two ways to retrieve records from an item in a table. The first is to pass SQL Query as input of phr.patient node and the second is to automatically generate SQL Query based on user defined rules through [QUERY] node and its subordinate Input Query node Method. Of course, adding a record to a table in an item, or modifying an existing record may also be the same as bringing the above record.

First, in the data retrieval method, a method of inputting SQL Query directly to a database node from an input item will be described. In this method, as shown in FIG. 17, a plurality of records can be obtained as a search result. In the current item, only one result can be stored in each node. Therefore, in this case, the first output result is stored in the node. You can directly type "Select * from patient where code = 1" in the text input window that appears when you right-click the Database node defined in the Input item to search the database node.

Next, the automatic generation of the query according to the situation will be described. In this method, as shown in FIG. 18, the SQL Query is directly input to the Input Query node in the Input Item. However, if SQL Query needs to be changed according to the situation, a query is generated in the form of # (number) such as (# 1, # 2, ...) Input sub. Enter the nodes in order. For example, the input query node is "SELECT * from patient where code = # 1", input sub. When the node enters "11", a database search query of "SELECT * from patient where code = 11" is automatically generated. Here, input sub. You can enter the value directly into the node, but the value to be used for retrieval is often received from an HL7 message or another database. You may also be able to get the value passed through the node's input.

Here, input sub. The method of adding a node is input sub. When a right mouse button is clicked on a node, a pop-up menu as shown in FIG. 22 is displayed. In this menu, ADD New menu is clicked.

Referring to FIG. 19 to FIG. 23, an Item is basically a tree form as shown in FIG. And the nodes that make up the tree are important. That is, when data is input to the node and the input data is processed, the result is stored in the specific node, and the processed data can be fetched from the node. This data flow can be performed by simple connection between nodes. To set up a data transfer path between nodes in two items, move the mouse cursor over the rectangle next to the node and click the right mouse button. Moving the mouse in that state will create a solid line from the selected rectangle to the mouse. Move to the rectangle next to the node of the other item you want to connect and release the mouse button to create the path. However, the output of one node can be connected to a number of node inputs. To delete a connection line, click on the specific connection line and click the right button of the mouse and click the "DELETE" button.

Referring to FIG. 20, an item named Division, Union in the Input, Output, and Functions groups in the I / O group will be described as an example.

The Input Item has five data output nodes (the right square box of the node) and the Output Item has four data input nodes (the square box on the left of the node). In addition, a Division Item has one input node and two output nodes (data, data). There is also a delimiter where input and output are not specified. In contrast to the Division Item, the direction of input / output of a node is determined for a Union Item. As shown in FIG. 20, each node is connected by a line, and this line is a path through which data in the node can move. The node at the top of the tree in each Item is used to process the input data or to generate the data to be output, and the nodes below it correspond to the temporary storage space where the analyzed individual data will be stored.

FIG. 20 is a flowchart showing a process of decomposing a letter " A | B " directly input by a user into a delimiter " | & . The Union Item creates the "A-B" by reassembling the data stored in the data node using the delimiter "-" specified by the user and passes the result to the Text node of the Output Item. This Text node is a node that stores the transferred data and allows the user to check it directly.

In the Item, the top node of the tree is used as an output for encoding for generating a new message by combining the data for decoding the data or the data stored in the lower node.

To input data to each node or to check the stored data, place the mouse cursor on the node and click the right mouse button to open the window for inputting and outputting. This is shown in FIG. 21 and FIG.

There are also various buttons in the window that allow you to manage (or create and delete) nodes in the tree. The "ADD New" button means to add a new node to the bottom of the current node, and "Remove" to delete the current node. "SAVE" means storing currently input data, "CLEAR" means deleting data and making its value null. "Close" button can be used to close the current window.

Also, as shown in FIG. 23, each item can be resized with a mouse. Position the mouse cursor on the title of the item and click the left button to activate the item. A dark square line is created around the Item, meaning it is activated. In that state, when the mouse cursor is moved to the upper, lower, left, right, center, or diagonal corner, the mouse cursor is deformed so that the box size can be adjusted. In this state, click the left mouse button and adjust the size.

Continue to look for the search for the value of a particular field. Such a method is an easy-to-use method for retrieving data associated with a database connection. That is, it is used when a specific value in a field set to FK in a specific table of the database is to be sequentially retrieved in the PK field of another table. This method can perform a cascade search by passing the output of the field node of the table Item to the input of another table.

In FIG. 24, a record of a patient is retrieved through a query input by a user, and the value is stored in each node. In this state, the output of the person_code node of the patient Item is passed to the input of the code node of the person Item, so that the person item retrieves the record corresponding to the received value and stores the result. In the case of FIG. 24, the person_code is FK in the patient table and the code is PK in the person table. However, it is possible to do this, but there may be no result, and if more than one exists, the first output value is displayed.

Meanwhile, regarding data modification and addition, there is a method of directly inputting SQL Query to the database node in the input item and a method of automatically generating a query according to the situation, which has already been mentioned above.

Here, as a method of directly inputting SQL Query, it is possible to input SQL Query directly from among the methods of inserting or modifying the records in the table. Since this is not so different from the portion described in the data retrieval portion, do.

Also, the automatic generation method of the query according to the situation is not much different from the method described in the data retrieval section above, but the user inputs the query about the modification and insertion of the data in the table into the output query node, sub. But it can be directly input to the node or input from the outside or processed.

While the present invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not limited to the disclosed embodiments. That is, within the scope of the present invention, all of the components may be selectively coupled to one or more of them. In addition, although all of the components may be implemented as one independent hardware, some or all of the components may be selectively combined to perform a part or all of the functions in one or a plurality of hardware. As shown in FIG. The codes and code segments constituting the computer program may be easily deduced by those skilled in the art. Such a computer program may be stored in a computer readable medium and read and executed by a computer to implement an embodiment of the present invention. As the storage medium of the computer program, a magnetic recording medium, an optical recording medium, a carrier wave medium, or the like may be included.

While the invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention.

100: transmission unit 101: first terminal
103: first information management apparatus 103_1: first information generating unit
103_2: first interface unit 105: first database
110: Receiver 111: Second information management device
111_1: second interface unit 111_2: second information generating unit
113: second terminal 115: second database
300: input unit 310: parsing unit
320: mapping unit 330: conversion unit
340: Integrated unit 350: Output unit

Claims (9)

A parser for parsing the input first information to decompose the field;
A mapping unit for generating mapping data using a graphical user interface (GUI) -based tool to generate second information based on the first information;
A conversion unit for converting the first information with reference to the mapping data;
A field mapper for converting connection information between each field represented by a tree structure using the tool into a program code and providing the converted code to the conversion unit; And
And an integration unit for integrating the converted first information to generate the second information
The information management apparatus comprising: The method according to claim 1,
And an interface unit for encoding and outputting the generated second information. (delete) The method according to claim 1,
Wherein the converting unit changes the field order of the first information. Parsing the input first information to decompose the field;
Generating mapping data using a graphical user interface (GUI) -based tool to generate second information based on the first information;
Converting the first information with reference to the mapping data;
Converting connection information between fields expressed in a tree structure into program codes using the tool;
Providing the converted code during the conversion of the first information; And
Integrating the converted first information to generate the second information;
Included information management methods. 6. The method of claim 5,
Encoding the generated second information, and outputting the encoded second information. (delete) 6. The method of claim 5,
Wherein the converting the first information comprises:
And changing the field order of the first information. A computer-readable recording medium containing a program for executing an information management method,
The information management method includes:
Parsing the input first information to decompose the field;
Generating mapping data using a graphical user interface (GUI) -based tool to generate second information based on the first information;
Converting the first information with reference to the mapping data;
Converting connection information between fields expressed in a tree structure into program codes using the tool;
Providing the converted code during the conversion of the first information; And
Integrating the converted first information to generate the second information; To
/ RTI >

Images