KR20090046290A - System and method for managing of medical information - Google Patents

Abstract

The present invention provides an integrated medical information management system and method for generating HL7 messages from data transmitted from medical institution terminals so that medical information can be shared among various medical institutions.

The integrated medical information management system of the present invention defines an HL7 message structure, has a HL7 engine for processing the defined HL7 message structure, monitors a medical institution terminal, and generates a new data from a medical institution terminal when a new data input event occurs. Extract the data to generate the HL7 message, monitor the medical device terminal, when the HL7 message request event occurs, receives and stores the HL7 message generated and stored in the message configuration module and message configuration module to extract and provide the HL7 message, Including a message exchange module that manages the history of HL7 messages, HL7 messages can be generated at high speed, and medical information generated as HL7 messages can be shared by various organizations and medical personnel.

Medical Information, HL7, Share

Description

System and Method for Managing of Medical Information

The present invention relates to a medical information management system and method, and more particularly, to a medical information integrated management system and method for generating a HL7 message from data transmitted from a medical institution terminal to share medical information in various medical institutions. will be.

In recent years, medical informatization projects have been actively promoted in an effort to improve the quality of medical services, and medical informatization at the level of computerization and integration of medical information in the medical services or healthcare market has been focused on large hospitals.

Medical informatization works by linking medical image information systems, prescription delivery systems, and electronic medical records to reduce costs, improve the stability of services, improve service quality, reduce patient waiting time, ease of information storage, and facilitate access to medical records for patients. Provides the benefits.

Accordingly, the necessity for information sharing in the health information field is increasing, awareness of international standards is increasing, and interest in the HL7 (Health Level 7) message, an international standard for health information sharing, is increasing.

HL7 is a set of rules that ensures that information is compatible between software applications in different healthcare sectors, and is becoming a global standard that, when used, makes all kinds of medical care available, regardless of the type or size of the medical institution. Business services will be available. In other words, HL7 is a network standard that can share patient's medical information.

The HL7 protocol specifies elements such as message structures, coding rules, and trigger events, where the message structure refers to the abstract definition of the message, the coding rule refers to the message representation for transmission, and the trigger event refers to the message. Means an application event to generate a. In HL7, when an event occurs by a trigger event, the event causes a path through the network between two or more systems to perform data exchange. Then, when data in the form of a message is transmitted from one system to another system, one cycle is completed by sending a response message confirming whether the message is received from the system that received the message to the system that sent the message.

HL7 defines messages related to the various tasks provided by medical institutions, including patient care, inquiry, prescription, prescription and observational reports on clinical results, product experiments, waveform results, patient referrals, accounting management, scheduling, etc. For example.

As such, if the patient's medical information is shared using HL7, the patient can be provided with higher quality of service, and the medical development can be expected based on the medical result of the important disease.

These HL7 messages are widely used internationally, with version 2.4 approved in 2000 and version 2.5 approved in 2003 as the American National Standard Institute (ANSI) standard, and version 3.0 based on the terminology and code based on XML (eXtensible Markup Language) Is being developed.

The HL7 message focuses on the US-based health care information system, where various independent systems must be linked, making it less useful for integrated systems based on databases in Korea. However, the database-driven order communication system (OCS) is also effective to use the HL7 message for linking with an independent system such as a picture archiving communication system (PACS). Here, OCS refers to a system that delivers orders from doctors, and PACS refers to a system that supports image sharing by storing and delivering images.

In addition, modern medical device systems are designed to provide test and measurement results in HL7 messages or to link test request information to HL7 messages. The introduction of these latest devices in health care information systems in Korea also requires the use of HL7 messages for quick and easy system integration. In addition, there is a demand for the construction of a real-time emergency computer network that shares patient information while transferring emergency patients, and the use of HL7 messages for information exchange.

The HL7 message server method is a method for generating HL7 messages with minimal changes to existing hospital information systems in Korea. This method is to share information by delivering a message to a message server when each developed system shares information. It is easy to link between systems because each system only needs to process messages without affecting the environment of other systems. There is one advantage.

On the other hand, when converting HL7 messages to XML for storage, retrieval and storage, there is a way to save storage space by eliminating duplicate data.

These methods focus on generating HL7 messages while operating in the form of a server in large systems such as hospital information systems. If the data type can be specially determined in such a server type of operation, a method in which the server operates independently of a heterogeneous database by generating a common view can also be used. However, linking a common view to a heterogeneous database is also difficult, and it is not easy to create a common view of data to be shared. It is also important to create a message on the server, but it is also important to verify the message and extract and process the data. It is also necessary to send the message.

In addition, there is a way to share the information with the HL7 based XML storage management system as a server in the center, but this method is difficult to implement at present because it requires the management of the state and the legal and institutional support. .

However, the Lifetime Electronic Health Record System (EHRs) and the Personal Lifetime Personal Health Record System (PHRs) ultimately ensure local, national, and global interoperability of health care information. It is evolving, and there is a need for reliable and efficient sharing of health information through HL7 messages.

As such, although it is necessary to link various systems and applications using the HL7 message in the healthcare information area, there is a disadvantage in that information on how to handle the HL7 message is effective. For this reason, when sharing information using HL7 messages in Korea, there is a problem that it is rather complicated and difficult, and does not obtain the advantages of the standard and is reluctant to use HL7 messages.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-mentioned disadvantages and problems, and provides a medical information integrated management system and method capable of easily and quickly generating data transmitted from a medical institution terminal as an HL7 message.

Another technical problem of the present invention is to provide a medical information integrated management system and method that can be efficiently linked to medical device terminals while efficiently and stably sharing medical information generated by HL7 messages.

The integrated medical information management system according to an embodiment of the present invention for achieving the above technical problem is a medical information integrated management system connected to at least one medical institution terminal through a communication network, and defines the HL7 message structure. A HL7 engine for processing the HL7 message structure, and monitoring the medical institution terminal, extracting new data from the medical institution terminal to generate an HL7 message when an event for inputting new data occurs, and monitoring the medical institution terminal. A message configuration module that extracts and provides an HL7 message when an HL7 message request event occurs; And a message exchange module configured to receive and store the HL7 message generated and stored by the message configuration module and to manage a history of the HL7 message.

In addition, the medical information integrated management method according to an embodiment of the present invention comprises a first step of the medical information integrated management system to generate the HL7 engine; A second step of the medical information integrated management system monitoring medical institution terminals to extract data to be stored from the medical institution terminal when a data storage event occurs; Generating a HL7 message by mapping data extracted from the medical institution terminal to an HL7 message using the HL7 engine; A fourth step of verifying the HL7 message; And a fifth process of storing the verified HL7 message.

In addition, the medical information integrated management method according to another embodiment of the present invention, if the medical information integrated management system monitors the medical institution terminal, when the medical information delivery request message is transmitted, the medical institution terminal that stores the medical information requested delivery; A first process of searching; A second step of extracting the requested medical information from the searched medical institution terminal and converting the medical information into an HL7 message; And a third step of transmitting the HL7 message to the medical information receiving destination requested to be delivered, with reference to the medical information delivery request message.

According to the present invention, by generating the HL7 message at high speed from the medical information transmitted from a plurality of medical institution terminal, the medical information generated in the HL7 message can be shared by various institutions and medical staff.

In addition, as the HL7 message is generated by the integrated medical information management system, medical information can be easily shared without changing or upgrading the medical device terminal, and when requested by the medical device terminal, by converting the structure of the HL7 message and providing the medical information, Efficient and reliable sharing of information is possible.

Hereinafter, with reference to the accompanying drawings will be described in detail a preferred embodiment of the present invention.

1 is an exemplary diagram of a communication network to which the integrated medical information management system according to the present invention is applied.

As shown, the medical information integrated management system 10 is connected to the plurality of medical institution terminal 20 through the communication network 30.

The integrated medical information management system 10 monitors the medical institution terminal 20 and, when new medical information data is generated, generates and verifies it as an HL7 message and stores it. In addition, when the specific medical institution terminal 20 requests medical information using the HL7 message, the medical institution terminal that searches for the requested medical information from another medical institution terminal connected to the integrated medical information management system 10 and requests the medical information. Provided by processing into a form that can be viewed by (20).

To this end, the medical information integrated management system 10 includes a message configuration module and a message exchange module, which will be described in detail with reference to FIG. 2.

2 is a detailed configuration diagram of a medical information integrated management system according to an embodiment of the present invention.

As shown in FIG. 2, the medical information integrated management system 10 includes a control unit 110, a message composition module 130, a message exchange module 150, a storage module 170, and an input / output processing module for controlling the overall operation. 190.

The message configuration module 130 monitors the medical institution terminal 20 at a specified cycle. When it is confirmed that input of new data occurs during monitoring, new data is extracted from the medical institution terminal 20, and the new data is generated as an HL7 message using the HL7 engine and then transmitted to the message exchange module 150.

To this end, the message construction module 130 should define the HL7 message structure and create an HL7 engine capable of processing the defined HL7 message structure.

Meanwhile, the message exchange module 150 receives the HL7 message generated and stored in the message composition module 130, checks where to send the HL7 message, and then transmits the HL7 message to the corresponding destination. Here, the destination of the HL7 message may be another medical institution terminal 20 or the message configuration module 130.

As a result of checking the message exchange module 150, when the message destination is the message constructing module 130, the message constructing module 130 receives and validates the HL7 message and stores the result in the storage module 170. The history of HL7 messages is managed in the message exchange module 150.

In addition, when the medical institution terminal 20 requests the message transmission, the message configuration module 130 performs a message conversion according to the type of the viewer or the medical information management program used in the terminal requesting the message transmission, the message transmission and reception application Allows sharing of information between systems without modification.

As such, the message constructing module 130 generates the HL7 message quickly, efficiently, and stably, and verifies, stores, and transmits the message. In addition, the message exchange module 150 enables efficient exchange and history management of HL7 messages, and in this sense, the medical information integrated management system of the present invention may be referred to as a health care message multi-center (HMMC).

3 is a detailed configuration diagram of the message configuration module shown in FIG. 2.

Referring to FIG. 3, the message composition module 130 according to the present invention generates a HL7 message and a message generation block 131 for transmitting the message exchange module 150 and the generated HL7 message to the message exchange module 150. Message processing block 132 for receiving from, verifying and storing in storage module 170.

In addition, the message generating block 131 includes a message structure editing unit 1301, an HL7 engine generating unit 1303, a program project 1305, and an HL7 engine 1307, and the message processing block 132 includes a message tester 1309. ), A project generation unit 1311, a message browser 1313, and a message structure management unit 1315.

First, each component of the message generating block 131 will be described as follows.

The message structure editing unit 1301 allows a developer to edit the HL7 message structure according to what events are to be generated, what messages to use when an event occurs, and whether there is information to be added to the message structure. The HL7 message includes a segment, and each segment includes at least one field. When a field has several values internally, these values are called components.

For example, the segment may include a segment containing patient information, a segment containing test results, and the segment including patient information may include a patient name field. In addition, the patient name field may include components such as a patient's last name, first name, and nickname.

Since there are many additional segments in the HL7 message, it is preferable to delete unnecessary segments in the message structure editing unit 1301 and simplify them. Elimination of these segments leaves only the essential content in the HL7 message, which improves the efficiency of communication and data processing. And since the user (medical staff) can create extended messages (messages that usually start with 'z') or segments that are not specified in the HL7 standard, they are included in the message structure. In addition, the HL7 standard expresses the values that can be included in a specific field as a table, which adds a new value or modifies an existing value. In addition, the message structure is easily expressed by the user, for example, a tree structure, and the data of segments and components are expressed in a tree or list structure so that the user can easily understand the HL7 message. These features improve the user's ability to understand and use HL7 messages, allowing applications to be developed quickly and accurately.

The HL7 engine generation unit 1303 generates an HL7 engine, which is a core module that handles HL7 messages, using the message structure edited by the message structure editing unit 1301. In other words, it creates a library with basic functions that the HL7 engine should perform. The HL7 engine is provided in the form of an object model, and when editing a message, it needs to be provided in an understandable form such as a tree structure. If the HL7 message is generated and parsed by mapping data in a simpler form than the object model, the mapping between the simplified form and the HL7 structure must be performed in the message structure editor 1301. For example, Chameleon commercial products set mapping information between the same structure as database tables and HL7 messages, and the HL7 engine simply sets and extracts values from the tables.

The program project 1305 is for performing mapping work between the HL7 engine and actual data, and includes a sender and a receiver. The sender monitors a medical device terminal at a set time interval (for example, 5 seconds or 10 seconds), and when an event occurs, the sender extracts data by querying data necessary for message generation or delivery and generates a HL7 message. Here, the event monitored by the program project 1305 may be a message generation event, a message delivery event. The message generation event is for generating a HL7 message when new medical information is added to a specific medical institution terminal, which will be described later with reference to FIG. 5. Meanwhile, the message delivery event is for retrieving and providing medical information from another medical institution terminal when a specific medical institution terminal requests medical information, which will be described later with reference to FIG. 7.

On the other hand, when the receiver receives the message, it can transmit an acknowledgment (Ack) message in two ways. The first method is the original mode, which is to verify the receipt of the message and send a response message after processing the data. The second method is an enhanced mode, in which, when a message is received, a message is stored, an acknowledgment message is sent, and an application acknowledgment message is transmitted when the message processing is completed. For stable message processing, it is preferable to use an enhanced mode that stores and processes a message.

The HL7 engine 1307 generates, verifies, and parses the HL7 message based on the message structure edited by the message structure editing unit 1301. To this end, the HL7 engine 1307 may be provided as a library for a specific language or implemented as a source file. When creating an HL7 message, it also provides the function to create an optimized message by removing unnecessary elements of the message, thereby improving efficiency in message transmission.

Next, each component of the message processing block 132 will be described.

The message tester 1309 also consists of two parts: a sender and a receiver. The sender is a program for transmitting an HL7 message to an external device or terminal (storage module, medical institution terminal, etc.). The sender can read the HL7 message from a character string or a file and transmit the message to TCP / IP. Meanwhile, the receiver receives the HL7 message from the message processing module 150 and transmits an acknowledgment message when it meets the standard. The message tester 1309 preferably operates based on the Low Layer Protocol (LLP) proposed by HL7.

The project generation unit 1311 generates a project having a minimum external interface required for sending and receiving messages using the HL7 engine and a basic framework for message processing. Here, a project may be defined as a combination of sources and libraries for generating a program, and it is preferable to create a project in multiple languages so that a developer can use a programming language that is familiar to them.

The message browser 1313 receives the HL7 message as a string or a file and verifies the contents. To this end, the message browser 1313 has a user interface and visually provides various input methods for the user to select or input a specific file, and the result is also displayed in a form that can be checked by the user.

Validation checks the composition of the message and segment, the message encoding rules, and whether the data type and the actual data are correct, and whether the data matches the values in the HL7 table. In addition, the message is represented in a tree form, representing the data fields and actual data values of the message structure. This is necessary to ensure that the actual data is in the fields you intended to put in. In addition, the message browser 1313 notifies the wrong part and provides correctable information (table list values) so that the developer can easily correct the wrong part. The verification function of the message browser 1313 is performed using the verification function of the HL7 engine 1307.

The message structure manager 1315 maintains and manages the structure according to the version of the HL7 message. For example, if a user wants to generate an HL7 V2.4 message, the message structure manager 1315 provides the HL7 V2.4 message structure. In addition, the message structure manager 1315 provides a changed message structure when the user wants to change the standard structure or add a new segment to change the message structure, and stores and reads the message structure information modified by the user. In addition, the HL7 message structure information is provided so that the message structure editing unit 1301 and the message browser 1313 can use the message structure information.

FIG. 4 is a detailed configuration diagram of the message exchange module shown in FIG. 2.

As shown, the message exchange module 150 includes an adapter 1501, a log manager 1503, a message queue 1505, a message converter 1507, a routing processor 1509, a message monitor 1511, and a message. And a tracking unit 1513.

First, the adapter 1501 is in charge of a communication protocol, and transmits and receives a message according to a protocol necessary for file input / output or HL7 message transmission. To this end, the adapter 1501 may include a file adapter, an FTP adapter, a TCP / IP adapter. The HL7 message is generally transmitted using TCP / IP, in which case the TCP / IP adapter receives the HL7 message and stores it in the storage module 170 via the message queue 1505. If the HL7 message is transmitted using FTP rather than TCP / IP, the FTP adapter receives the message and stores the message in the storage module 170 through the message queue 1505.

Next, the log manager 1503 manages all processes of receiving, storing, routing, and converting the message so that the process of processing the message can be confirmed. In this way, the state of the medical information integrated management system 10 can be monitored, and when an error occurs, the error occurrence point can be found and the problem can be solved.

The message queue 1505 sequentially stores the HL7 messages read through the adapter 1501 in the storage module 170. By storing the message as a file or a database through the message queue 1505, even if a problem occurs in the system, the message may not be lost.

When the medical institution terminal requests the HL7 message, the message converting unit 1507 converts the message into a form that can be processed by the medical institution terminal, and even when the versions of the HL7 message used by the medical institution terminal and the medical information integrated management system 10 are different. Perform message conversion. For this purpose, fixed data is set in specific fields of the message or specific data is converted.

The routing processor 1509 transfers the message to the corresponding location by using the names of the sender (the sender) and the receiver (the receiver) included in the HL7 message. For this purpose, the routing processing unit 1509 maintains / manages information for mapping a unique name of the system and an actual IP address. In this way, when the HL7 message is sent and received, it is possible to reduce the burden on the application development since it only needs to be sent to the routing processing unit 1509 without considering the position to be sent.

The message monitor 1511 provides a graphical user interface (GUI) that can monitor how many HL7 messages are accumulated in the message queue 1505, how many messages have been processed, and the time required to process them. The developer may grasp the overall state of the medical information integrated management system (10).

The message tracking unit 1513 tracks the process of delivering the message to the developer according to the message processing process managed by the log manager 1503 and provides the processed result for each delivery process. Accordingly, when an error occurs, the problem occurrence point can be found and solved.

5 is a flowchart illustrating a method of generating an HL7 message according to an embodiment of the present invention.

First, the HL7 engine generating unit 1303 of the integrated medical information management system 10 receives data from a medical institution terminal and generates a HL7 engine for generating the HL7 message in advance (S101). In addition, the program project 1305 monitors the medical institution terminals connected through the network 30 (S103), checks whether an event to store data occurs during the monitoring (S105), and if the event occurs, the corresponding medical institution terminal Data is extracted from the step (S107).

The program project 1305 generates the HL7 message by mapping the data extracted from the medical institution terminal to the HL7 message using the HL7 engine (S109).

Thereafter, the message browser 1313 displays the HL7 message generated in step S109 and verifies the HL7 message generated in step S109 using the verification function of the HL7 engine (S111). Validation checks the composition of the message and segment, the message encoding rules, and whether the data type and the actual data are correct, and whether the data matches the values in the HL7 table.

When the verification is completed, the generated HL7 message is stored in the storage module 170 through the message queue 1505, the program project 1305 informs the medical institution terminal the result of the HL7 message processing (S115).

Here, all processes of extracting data, generating, verifying, and storing the HL7 message are managed by the log manager 1503.

On the other hand, after the step S107, before performing the step S109, and stores the data extracted by the program project (1305) (S121), and transmits the response message to the medical institution terminal (S123) advantage that more stable data processing is possible There is this.

6 is a detailed flowchart of a process of generating an HL7 engine shown in FIG. 5.

The integrated medical information management system 10 of the present invention must generate a HL7 engine in order to generate data extracted from a medical institution terminal as an HL7 message.

More specifically, the developer collects which event is to be generated, which message to use if an event occurs, and whether there is information to be added to the message structure (S201).

The message structure is edited using the message structure editing unit 1301 with reference to the collected event information and additional information (S203). After the message structure is edited as described above, the HL7 engine generating unit 1303 generates an HL7 engine, which is a core module that handles the HL7 message (S205). In other words, it creates a library with basic functions that the HL7 engine should perform.

As such, the developer edits the message structure and generates the HL7 engine based on the message structure, and thus, the HL7 message may be generated by the mapping process of the program project 1305.

7 is a flowchart illustrating a HL7 message exchange method according to an embodiment of the present invention.

The message generating block 131 monitors the medical institution terminals or the message exchange module 150 connected through the communication network 30 (S301), and checks whether a medical information transmission event occurs during the monitoring (S303). Here, the medical information delivery request message is transmitted by the HL7 message, and the HL7 message includes a unique name of the medical institution terminal, that is, the medical information receiving side, which has requested the medical information delivery.

As a result of the check, when the specific medical institution terminal or the message exchange module 150 requests the HL7 message, the program project 1305 extracts data from the medical institution terminal in which the requested medical information exists and converts the data into the HL7 message (S305).

Thereafter, the message conversion unit 1507 converts the message into a form that can be processed by the medical institution terminal requesting medical information (S307). This conversion process can of course be omitted depending on the type and specification of the terminal of the medical institution.

Thereafter, the routing processor 1509 checks the unique name of the receiving party included in the HL7 message requesting the delivery of medical information, and confirms the receiving IP address mapped and stored with the unique name (S309), and the message tester ( 1309 transmits the corresponding HL7 message according to the IP address confirmed in step S309 (S311).

In the above-described message exchange process, the message request, extraction, conversion, and transmission process by the medical institution terminal is stored and managed by the log manager 1503.

Those skilled in the art to which the present invention pertains will understand that the present invention can be implemented in other specific forms without changing the technical spirit or essential features. Therefore, the above-described embodiments are to be understood as illustrative in all respects and not as restrictive. The scope of the present invention is shown by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included in the scope of the present invention. do.

According to the present invention, it is possible to provide an environment for rapidly developing various applications in a health care institution, and various centers that have developed applications can share information stably and effectively using messages. This enables applications between tertiary hospital-level OCS (Order Communication System) systems and laboratory systems, and information sharing between hospital information systems and home / portable medical devices.

1 is an exemplary diagram of a communication network to which a medical information integrated management system according to the present invention is applied;

2 is a detailed configuration diagram of a medical information integrated management system according to an embodiment of the present invention;

3 is a detailed configuration diagram of the message configuration module shown in FIG. 2;

4 is a detailed configuration diagram of the message exchange module shown in FIG. 2;

5 is a flowchart illustrating a method of generating an HL7 message according to an embodiment of the present invention;

6 is a detailed flowchart of a process of generating an HL7 engine illustrated in FIG. 5;

7 is a flowchart illustrating a HL7 message exchange method according to an embodiment of the present invention.

<Description of the symbols for the main parts of the drawings>

10: integrated medical information management system 110: control unit

130: message configuration module 150: message exchange module

170: storage module 190: input / output processing module

1301: message structure editing unit 1303: HL7 engine generation unit

1305: Program Project 1307: HL7 Engine

1309: message tester 1311: project generator

1313: message browser 1315: message structure management unit

1501: adapter 1503: log management unit

1505: message queue 1507: message conversion unit

1509: routing processing unit 1511: message monitoring unit

1513: message tracking unit

Claims (28)

An integrated medical information management system connected to at least one medical institution terminal through a communication network, A HL7 message structure is defined and includes an HL7 engine for processing the defined HL7 message structure, monitors the medical institution terminal, and extracts new data from the medical institution terminal when a new data input event occurs. A message configuration module configured to generate and store a message and to monitor the medical institution terminal and extract and provide an HL7 message when an HL7 message request event occurs; And A message exchange module which receives the HL7 message generated by the message composition module and manages the history of the HL7 message; Medical information integrated management system comprising a. The method of claim 1, The message construction module includes a message generation block and a message processing block, The message generating block includes: a message structure editing unit for editing the HL7 message structure according to an event to be generated and additional information; An HL7 engine generation unit generating the HL7 engine for generating an HL7 message using the message structure edited by the message structure editing unit; A program project for generating and storing an HL7 message by performing mapping between the HL7 engine and actual data; And An HL7 engine for generating, verifying, and parsing an HL7 message based on the message structure edited by the message structure editing unit; Medical information integrated management system comprising a. The method of claim 2, The HL7 message includes a plurality of segments, and the message structure editing unit deletes unnecessary segments of the segment. The method of claim 2, And the message structure editing unit includes an extended message or segment not included in the HL7 message standard in the HL7 message structure. The method of claim 2, And the message structure editing unit expresses the HL7 message structure in a tree structure and expresses data of segments and components included in the HL7 message in a tree or list structure. The method of claim 2, The program project may include: a sender that monitors the medical institution terminal, extracts data by querying data necessary for generating a message, and generates a HL7 message when a data storage event occurs; And A receiver for transmitting a response message after receiving data from the medical institution terminal; Medical information integrated management system comprising a. The method of claim 6, The receiver, when receiving data from the medical institution terminal, verifies the data, and after completing the generation of the HL7 message, the medical information integrated management system, characterized in that for transmitting to the medical institution terminal. The method of claim 6, When receiving data from the medical institution terminal, the receiver stores the data and transmits an acceptance response message to the medical institution terminal, and transmits a completion message when the generation of the HL7 message from the data is completed. Integrated management system. The method of claim 1, The message construction module includes a message generation block and a message processing block, The message processing block may include: a project generation unit configured to generate a project including an external interface for transmitting and receiving a message using the HL7 engine and a basic frame for processing the HL7 message; And A message structure management unit for maintaining and managing a message structure according to a version of an HL7 message, and providing the message structure to the message generation block; Medical information integrated management system comprising a. The method of claim 9, The message structure management unit stores and manages the changed message structure when the developer wants to change the standard structure of the HL7 message or add a new segment to change the message structure. The method of claim 9, The message processing block may further include a message browser that receives and displays the HL7 message, performs verification using the HL7 engine, and displays a verification result. The method of claim 11, The message browser checks the composition of the HL7 message and the segment, the HL7 message encoding rule, and checks whether the data type matches the actual data and whether the data matches the values in the HL7 table. Management system. The method of claim 11, And the message browser displays the HL7 in a tree form, and outputs a data field and an actual data value of the HL7 message structure. The method of claim 9, The message processing block, the medical information integrated management system further comprises a message tester for receiving a HL7 message to confirm whether it meets the HL7 standard, and transmits a response message if the standard. The method of claim 13, The message tester may include: a sender for transmitting an HL7 message to an external terminal; And A receiver that receives the HL7 message and confirms that it meets the standard, and sends a response message if the standard is met; Medical information integrated management system comprising a. The method according to claim 14 or 15, The message tester, the medical information integrated management system, characterized in that to operate based on the LLP (Low Layer Protocol). The method of claim 1, The message exchange module includes: an adapter in charge of a communication protocol for transmitting and receiving a message according to a protocol required for file input / output or HL7 message transmission; A log manager for storing and managing a process of the HL7 message; A message queue for sequentially storing the HL7 message; And A routing processor configured to store and manage a transceiving location name of the HL7 message with an IP address, and to deliver the HL7 message with reference to the IP address; Medical information integrated management system comprising a. The method of claim 17, The adapter, file adapter, FTP adapter, TCP / IP adapter, characterized in that the integrated medical information management system. The method of claim 17, The message exchange module further includes a message conversion unit for converting the HL7 message into a form that can be processed by the medical institution terminal when the medical institution terminal requests the HL7 message. The method of claim 17, The message exchange module further comprises a message monitoring unit for outputting the amount of the HL7 message stored in the message queue, the throughput of the HL7 message, the processing time of the HL7 message. The method of claim 17, The message exchange module tracks a process of delivering the HL7 message to a user according to the process of processing the HL7 message managed by the log manager, and provides a message tracking that provides a result processed for each process of delivering the HL7 message. Medical information integrated management system further comprising a wealth. A medical information integrated management method in a medical information integrated management system which is connected to a plurality of medical institution terminals through a communication network and manages integrated medical information, A first step of the medical information integrated management system generating an HL7 engine; A second step of the medical information integrated management system monitoring the medical institution terminals and extracting data to be stored from the medical institution terminal when a data storage event occurs; Generating a HL7 message by mapping data extracted from the medical institution terminal to an HL7 message using the HL7 engine; A fourth step of verifying the HL7 message; And A fifth step of storing the verified HL7 message; Medical information integrated management method comprising a. The method of claim 22, And a sixth step of notifying the medical institution terminal of the HL7 message processing result after the fifth step. The method of claim 22, A step 2-1 of storing data extracted from the terminal of the medical institution after performing the second step and before performing the third step; And The medical information integrated management method further comprises the step 2-2 of transmitting a response message to the medical institution terminal. The method of claim 22, The first process may include: a 1-1 process of collecting an event to occur and additional information; First and second steps of editing a message structure with reference to the event information and additional information; And First to third steps of generating a library having basic functions that the HL7 engine should perform; Medical information integrated management method comprising a. A medical information integrated management method in a medical information integrated management system which is connected to a plurality of medical institution terminals through a communication network and manages integrated medical information, A first step of the medical information integrated management system monitoring the medical institution terminal and searching for the medical institution terminal storing the medical information requested for delivery when the medical information delivery request message is transmitted; A second step of extracting the requested medical information from the searched medical institution terminal and converting the medical information into an HL7 message; A third step of transmitting the HL7 message to the medical information receiving destination requested for delivery by referring to the medical information delivery request message; Medical information integrated management method comprising a. The method of claim 26, And after the second process, before performing the third process, converting the extracted HL7 message into a form that can be processed by the medical institution terminal. The method of claim 26, The medical information delivery request message is a HL7 message including a unique name of the medical information receiving destination requested for delivery, and the integrated medical information management system manages an IP address mapped to each of the unique names. And wherein the third process is a process of extracting an IP address mapped to the distinguished name and transmitting medical information converted into the HL7 message according to the extracted IP address.

Images