CN106600499B - Hospital information integration method based on bus form - Google Patents
Hospital information integration method based on bus form Download PDFInfo
- Publication number
- CN106600499B CN106600499B CN201611207539.XA CN201611207539A CN106600499B CN 106600499 B CN106600499 B CN 106600499B CN 201611207539 A CN201611207539 A CN 201611207539A CN 106600499 B CN106600499 B CN 106600499B
- Authority
- CN
- China
- Prior art keywords
- information
- integration
- message
- engine
- endpoint
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/22—Social work
-
- 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
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
Abstract
The invention relates to a hospital information integration method based on a bus form, which comprises the following steps: each business information system in at least one business information system and the hospital information integration platform form a one-to-one integration relationship, each business information system is used as a source information system and a target information system, information of the source information system is sent to the hospital information integration platform in a message form, an integration engine of the hospital information integration platform triggers integration project execution according to the type of the received message, sends the integration project execution to the target information system, and records the processing process of the whole message and the return result of the target information system. The information interaction among all the service information systems of the hospital is realized through the integration engine, the service information systems only manage and send the messages to the integration platform, the integration platform is responsible for forwarding the messages, and the information interaction among the service systems is realized through graphically configuring the integration items.
Description
Technical Field
The invention relates to the technical field of computer information, in particular to a hospital information integration method based on a bus form.
Background
With the development of computer software technology and the continuous development of enterprise informatization, software used by medical institutions, such as: there are also increasing applications and management systems such as HIS (Hospital Information System), financial management, LIS (Laboratory Information System), and EMR (Electronic Medical Record). Although these systems are applied in different fields and manage different objects, there are many pieces of information and data that cross each other and even repeat. And each application system runs independently, so that the internal systems are equivalent to individual information islands, and have no smooth information exchange and sharing among the systems.
To solve these contradictions, hospitals have reversed one approach to the existing systems: all information systems of an enterprise are updated to be a unified management system, and all departments work on the unified system (for example, all applications of the whole hospital run on the system of one manufacturer), but the system is not a feasible solution in consideration of cost, implementation period and difficulty factors. The other method is that the enterprise considers the whole information system of the enterprise from the whole, carries out overall planning on each application system according to the actual requirement, selects a proper integration platform and integrates the related different department system software. Such a solution is feasible both from implementation difficulty and from implementation cost, cycle time and technical considerations. In this context, integrated platform data transfer is taking place.
Disclosure of Invention
In order to solve the above problems, the present invention provides a hospital information integration method based on a bus format, so as to solve the problem of data transmission and reception of each business system in the hospital at present.
In order to achieve the purpose, the invention provides a hospital information integration method based on a bus form, which comprises the following steps: each business information system in at least one business information system and the hospital information integration platform form a one-to-one integration relation, the at least one business information system is respectively used for processing one or more business objects related to hospital business, each business information system is used as a source information system and a target information system, information of the source information system is sent to the hospital information integration platform in a message form, an integration engine of the hospital information integration platform triggers integration project execution according to the type of the received message, sends the integration project execution to the target information system, and records the processing process of the whole message and the return result of the target information system.
The invention discloses a hospital information integration method based on a bus form, wherein a hospital information integration platform comprises an integrated development environment, an integrated engine and an integrated monitoring system; the hospital information integration platform realizes the hospital information integration process in a bus form and comprises the following steps: forming an integrated development environment; the integration engine performs background analysis execution on the integrated projects submitted and released in the integrated development environment; and the integrated monitoring system monitors the process of executing the integrated project by the integrated engine.
The hospital information integration method based on the bus form disclosed by the invention has the advantages that the integrated development environment is formed by an information configuration process and an information integration flow configuration process.
The hospital information integration method based on the bus form disclosed by the invention comprises the following information configuration processes: maintaining endpoint information, namely taking at least one service information system on line in a hospital as an endpoint of a source information system and a target information system, arranging and registering hospital services on a hospital information integration platform by configuring the endpoint information, wherein the endpoint information comprises endpoint basic information and Inbound message receiving service information, the endpoint basic information comprises an endpoint name, an endpoint version, an endpoint service manufacturer and an endpoint contact person, and the Inbound message receiving service information comprises a service name, a protocol type, a service IP address, a port number, a service method, a method parameter, a parameter type and timeout setting; maintaining integrated engine information, and configuring one or more integrated engines, wherein the configuration information of the integrated engines comprises IP addresses, port numbers, CPU information, memory information and thread maximum quantity setting of a server where engine software is located; maintaining message information, configuring interactive messages among service information systems, specifying XML Schema of the messages, setting endpoint information capable of sending the message type, and limiting the sending of the messages; and maintaining component information, namely configuring information of a component formed by a message processing unit to realize the registration of the component, wherein the information of the component comprises a display name of the component, component configuration window information and component processing engine information.
The invention discloses a hospital information integration method based on a bus form, which comprises the following components: the format conversion component is used for converting the message format of the incoming message; a router component for configuring routing rules for messages incoming to the router; the term conversion component is used for carrying out term conversion between the service information systems; the filter component is used for filtering the message according to the judgment of the message content; an HL7 converter, which is used for converting non-HL 7 standard messages into HL7 standard messages; the DICOM converter is used for converting the message content into the DICOM standard protocol; the sequencer is used for sequencing a plurality of incoming messages and sending the messages to the next component in sequence; and the aggregator is used for carrying out content aggregation on the plurality of incoming messages and generating new message content.
The hospital information integration method based on the bus form disclosed by the invention comprises the following steps of: creating a new integrated project, and designating the integrated project as an interface engine mode to enable a business information system to actively send a message to an integrated engine interface; setting a message type sent to an integration engine interface in an integration engine interface configuration window; configuring a receiving endpoint in an integration project window; configuring a processing component of a processing flow in the integrated project window; setting a message flow direction; processing and configuring each component; performing message receiving configuration on a receiving endpoint; submitting an integration project; the hospital information integration platform detects the configuration of the submitted integration project; the successful submission is detected when the configuration of the submitted integration item is correct.
The hospital information integration method based on the bus form, disclosed by the invention, comprises the following steps that an integration engine performs background analysis execution on an integration project submitted and issued in an integrated development environment: the integration engine interface receives the message sent by the service information system, completes format verification, authority verification and validity verification of the message, and then stores the message in a message cache to wait for the integration engine instance to process; locking a batch of messages by the integration engine instance, and retrieving all integration items matched with the message types according to the configuration information of the integration items; executing integration items by Free threads in the integration engine thread pool respectively; the integration engine loads the corresponding component processing module according to the integration flow and transmits message instance information and profile information; the component processing module processes the input message and returns the output message to the integration engine; when executing to a target receiving endpoint, the integration engine tries to call an access interface configured by the target receiving endpoint; after the target receiving end point finishes processing, if the interface is provided with a return value, the integration engine is responsible for receiving the return value, calling a callback interface of a service system for sending a message according to the interface record of the access integration engine and transmitting parameter information; the integration engine records log information of all execution processes in the whole integration project, and returns final execution success or failure result information to the cluster manager; the cluster manager updates the execution result of the message, and if the engine processing of one message exceeds a preset time range, the cluster manager forcibly unlocks the message processing and waits for the processing of other integrated engines; the cluster manager periodically transfers the messages exceeding a certain time range to the historical message library, so that the number of cache records of the online message library is reduced, and the access speed of the database is increased.
According to the hospital information integration method based on the bus form, disclosed by the invention, the integration engine captures and records the abnormal condition of the component processing module in the processing process.
According to the hospital information integration method based on the bus form, when the integration engine tries to call the access interface configured by the target receiving endpoint, if the call of the access interface fails, the integration engine retries to call the access interface configured by the target receiving endpoint within the set failed call frequency range.
The hospital information integration method based on the bus form, disclosed by the invention, is characterized in that the integrated monitoring system monitors the integrated project process executed by the integrated engine and comprises the following steps: displaying the log information in a classified manner; graphically displaying the message sending quantity, the message receiving quantity, the processing performance consumption, the processing bottleneck point and the execution process of a single integrated project in a certain time period; and sending the index exceeding the warning value to a hospital information integration platform administrator in the form of short message and mail.
The invention has the following advantages:
(1) point-to-point integration among all service information systems of the hospital is avoided, the number of interfaces is reduced, and the information integration efficiency is improved;
(2) the whole interactive process has complete and uniform log records, and message flow can be tracked and counted;
(3) a message driving mechanism is adopted to reduce the pressure and risk of the database of the opposite side service information system;
(4) the hospital can quickly obtain which service information systems are affected by replacing one service information system, and a strategy is made in advance;
(5) the construction speed of a newly-built service information system is increased, and the overall informatization construction investment cost of the hospital is reduced.
Drawings
Fig. 1 is a schematic logic block diagram of a hospital information integration method based on a bus form in the invention.
FIG. 2 is a flow chart of the hospital information integration process implemented by the hospital information integration platform in the form of bus in the present invention.
FIG. 3 is a flow chart of forming an integrated development environment in the present invention.
Fig. 4 is a schematic diagram of a configuration window of a format conversion component of the hospital information integration platform according to an example of the present invention.
Fig. 5 is a schematic diagram of a sample router component configuration window of the hospital information integration platform according to the present invention.
Fig. 6 is a schematic diagram of a sample routing rule logic processing display window of the router component of the hospital information integration platform according to the present invention.
Fig. 7 is a flowchart of an information integration flow configuration process in the present invention.
Fig. 8 is a schematic diagram of a sample of the configuration window invoked by the receiving endpoint of the hospital information integration platform according to the present invention.
Fig. 9 is a schematic diagram of an example of an integration process configuration window of the hospital information integration platform according to the present invention.
FIG. 10 is a flowchart of the background parsing execution of the integration project submitted and released in the integrated development environment by the integration engine in the present invention.
FIG. 11 is a diagram of the integrated monitoring system for monitoring the integrated project process executed by the integration engine in the present invention.
Fig. 12 is a schematic diagram of an integration engine operating architecture of the hospital information integration platform in the present invention.
Detailed Description
The following examples are intended to illustrate the invention but are not intended to limit the scope of the invention.
Example 1
Referring to fig. 1, the hospital information integration method based on the bus form provided in this embodiment includes: each business information system in the at least one business information system and the hospital information integration platform form a one-to-one integration relationship, wherein the hospital information integration platform comprises an integrated development environment, an integrated engine and an integrated monitoring system, and the integrated development environment is not shown in fig. 1; at least one service information system is used for processing one or more service objects related to hospital services respectively, each service information system is used as a source information system and a target information system, the service information system is used as a source information system and is connected with a hospital information integration platform through a source adapter to convert the service objects of the source information system into communication messages, thus, the information of the source information system is sent to the hospital information integration platform in a message form, an integration engine of the hospital information integration platform triggers an integration project to execute according to the received message type, the message type is converted into the same type as the target information system, the service information system is used as a target information system and is connected with the hospital information integration platform through the target adapter, thus, the target adapter converts the message after the message type conversion into the service objects with the same type as the target information system and sends the service objects to the target information system, and simultaneously, the integration engine records the processing process of the whole message and the return result of the target information system.
Referring to fig. 2, the hospital information integration platform implements a hospital information integration process in a bus form, including:
s201: forming an integrated development environment;
s202: the integration engine performs background analysis execution on the integrated projects submitted and released in the integrated development environment; and
s203: the integrated monitoring system monitors the integrated project process executed by the integrated engine.
Further, referring to fig. 3, forming an integrated development environment includes:
s301: an information configuration process; and
s302: and (5) configuring an information integration process.
The information configuration process comprises the following steps:
maintaining Endpoint (Endpoint) information, namely taking at least one service information system on line in the hospital as an Endpoint (Endpoint) of a source information system and a target information system, arranging and registering hospital services by configuring Endpoint information on a hospital information integration platform, wherein the Endpoint information comprises Endpoint basic information and Endpoint message receiving service information (the Endpoint message receiving service, which means that a service interface provided by an Endpoint is in a webservice form and comprises two technical forms of SOAP and RESTFUL), the Endpoint basic information comprises an Endpoint name, an Endpoint version, an Endpoint service manufacturer and an Endpoint contact person, and the Endpoint message receiving service information comprises a service name, a protocol type, a service IP address, a port number, a service method, a method parameter, a parameter type and timeout setting;
maintaining integrated engine information, and configuring one or more integrated engines, wherein the configuration information of the integrated engines comprises IP addresses, port numbers, CPU information, memory information and thread maximum quantity setting of a server where engine software is located; background software can be called to start, stop and suspend the configured engine, the current engine can be switched to be in a debugging state during operation, and the engine only executes the specified integrated project in the debugging state;
maintaining message information, configuring interactive messages among service information systems, specifying XML Schema (extensible markup language architecture) of the messages, setting endpoint information capable of sending the message type, and limiting the sending of the messages;
and maintaining component information, namely configuring information of a component formed by a message processing unit to realize the registration of the component, wherein the information of the component comprises a display name of the component, component configuration window information and component processing engine information.
Wherein, the subassembly includes: a format conversion component, configured to perform message format conversion on an incoming message and output another XML Schema (extensible markup language architecture) message, where the component performs graphical processing, and may dynamically add a conversion output XSD Schema node (an XSD Schema refers to a structure of XML and may be changed to XML Schema, and a Schema node of XML refers to certain node information in XML and is usually in an XPATH manner), and may perform function processing on conversion between nodes, where an actual configuration of the format conversion component is shown in fig. 4; a router component, configured to configure a routing rule for a message transmitted to a router, make a result judgment according to the content of the message, and set a message flow direction according to the judgment result, specifically referring to fig. 5 and 6; the term conversion component is used for carrying out term conversion between the service information systems; the filter component is used for filtering the messages according to the judgment of the message content, shielding the messages meeting the conditions, and sending the messages not meeting the conditions to the next component; an HL7(Health Level 7) converter, which is used for converting non-HL 7(Health Level 7) standard messages into HL7(Health Level 7) standard messages; a DICOM (Digital Imaging and Communications in Medicine) converter for converting message contents to comply with DICOM (Digital Imaging and Communications in Medicine) standard protocol; the sequencer is used for sequencing a plurality of incoming messages and sending the messages to the next component in sequence; and the aggregator is used for carrying out content aggregation on the plurality of incoming messages and generating new message content.
Referring to fig. 7, the information integration flow configuration process further includes:
s701: creating a new integrated project, and designating the integrated project as an interface engine mode to enable a business information system to actively send a message to an integrated engine interface;
s702: setting a message type sent to an integration engine interface in an integration engine interface configuration window;
s703: configuring a receiving Endpoint (Endpoint) in the integrated project window, calling the configuration window by the receiving Endpoint (Endpoint) as shown in fig. 8, selecting an Endpoint from a receiving Endpoint (Endpoint) list on the right side of the window, dragging to a Target receiving Endpoint (Target Endpoint) area, repeating the operation, and setting a plurality of Target receiving endpoints (Target endpoints);
s704: configuring processing components of a processing flow in an integrated project window, selecting components from a Component list on the right side of the window, and designing a message Component processing sequence;
s705: setting a message flow direction;
s706: processing and configuring each component;
s707: performing message receiving configuration on a receiving endpoint;
s708: submitting an integration project;
s709: the hospital information integration platform detects the configuration of the submitted integration project;
s710: detecting that the configuration of the submitted integrated project is correct and the submission is successful;
s711: if a configuration error is detected, the configuration error needs to be modified until the configuration is successfully submitted, as shown in fig. 9, the configuration window is a sample schematic diagram of the integration process configuration window of the hospital information integration platform in the present invention.
Referring to fig. 10, the background parsing execution of the integration project submitted and released in the integrated development environment by the integration engine further includes:
s1001: an integrated engine interface receives a message sent by a service information system;
s1002: completing format verification, authority verification and validity verification of the message;
s1003: storing the information into a message cache to wait for the integrated engine instance to process;
s1004: the integration engine instance locks a batch of messages, and retrieves all integration items matched with message types according to configuration information of the integration items, wherein 200 messages can be processed in a single batch;
s1005: free threads in the integrated engine thread pool (the Free threads refer to idle threads in the engine and are in an idle state in a waiting task) respectively execute integrated items;
s1006: the integration engine loads a corresponding component processing module according to an integration flow, and transmits message instance information and profile information (the profile information refers to context information of an object, generally, when the component processes the information, some parameter data need to be known for processing, the engine is responsible for transmitting the parameter data to the component, and the component processes the information according to the information and then outputs the information to the engine);
s1007: the component processing module processes the input message and returns the output message to the integration engine, and if the component is in an abnormal condition in the processing process, the integration engine captures and records the input message;
s1008: when executing to a Target receiving Endpoint (Target Endpoint), an integration engine tries to call an access interface configured by the Target receiving Endpoint (Target Endpoint), and if the access interface is failed to call, the integration engine retries to call the access interface configured by the Target receiving Endpoint (Target Endpoint) within a set failed call frequency range;
s1009: after the Target receiving Endpoint (Target Endpoint) finishes processing, if the interface is provided with a return value, the integration engine is responsible for receiving the return value and calling a callback interface of a service system for sending messages and transmitting parameter information according to the interface record of accessing the integration engine;
s1010: the integration engine records log information of all execution processes in the whole integration project, and returns final execution success or failure result information to the cluster manager;
s1011: the cluster manager updates the execution result of the message, and if the engine processing of one message exceeds a preset time range, the cluster manager forcibly unlocks the message processing and waits for the processing of other integrated engines;
s1012: the cluster manager periodically transfers the messages exceeding a certain time range to the historical message library, reduces the number of cache records of the online message library, and accelerates the access speed of the database, as shown in fig. 11, the cluster manager is a schematic diagram of an integrated engine operation architecture of the hospital information integration platform.
Referring to fig. 12, the monitoring of the integration engine executing the integration project process by the integration monitoring system further comprises: displaying the log information in a classified manner; graphically displaying the message sending quantity, the message receiving quantity, the processing performance consumption, the processing bottleneck point and the execution process of a single integrated project in a certain time period; and sending the index exceeding the warning value to a hospital information integration platform administrator in the form of short message and mail.
In summary, the information interaction among the service information systems of the hospital is realized through the integration engine, the service information systems only manage to send the messages to the integration platform, the integration platform is responsible for forwarding the messages, and the information interaction among the service systems is realized through graphically configuring the integration project; creating a flow language corresponding to the integrated project, realizing description of the integrated project, wherein legal configuration rules of the integrated flow can be dynamically set according to the flow language, for example, messages can only flow from an integrated engine interface to a Target receiving Endpoint (Target Endpoint), collocation rationality among components and the like; the format conversion component completes the format conversion of the message in a graphical connection mode; the router component selects the output component to realize the trend of the message by processing the content of the message; the HL7 conversion component is internally provided with a simple structure message Schema (the message Schema exists in an XML form, and the message Schema refers to the structure of the message, namely the structure information described in XSD) to convert and configure the format of the complex HL7 international standard message, so that the implementation workload can be greatly reduced; the term conversion component completes conversion between terms through codeSystem (dictionary name) and code (dictionary code) according to a Target Endpoint (Target Endpoint) object of a message; returning the message of a Target receiving Endpoint (Target Endpoint), taking the integrated engine as a proxy of a message sending system, receiving a message processing return value and sending the message processing return value to the message sending system; the integration engine can be hot-plugged at any time without configuration processing of a central manager; the integration engine can be switched from the running state to the debugging state to carry out debugging on the specified integration project; the integrated knowledge base accumulates the interface modes of various service manufacturers, and can call the interface configuration of the service manufacturers according to the informatization construction condition of the hospital, thereby reducing the implementation workload.
Although the invention has been described in detail above with reference to a general description and specific examples, it will be apparent to one skilled in the art that modifications or improvements may be made thereto based on the invention. Accordingly, such modifications and improvements are intended to be within the scope of the invention as claimed.
Claims (6)
1. A hospital information integration method based on a bus form is characterized by comprising the following steps: each business information system in at least one business information system and a hospital information integration platform form a one-to-one integration relationship, the at least one business information system is respectively used for processing one or more business objects related to hospital business, each business information system is used as a source information system and a target information system, information of the source information system is sent to the hospital information integration platform in a message form, an integration engine of the hospital information integration platform triggers integration project execution according to the type of the received message, sends the integration project execution to the target information system, and records the processing process of the whole message and the return result of the target information system; the hospital information integration platform comprises an integrated development environment, an integrated engine and an integrated monitoring system; information interaction among all service information systems of a hospital is realized through an integration engine, the service information systems only manage and send messages to an integration platform, the integration platform is responsible for forwarding the messages, and the information interaction among the service systems is realized through graphically configuring integration items; the hospital information integration platform realizes the hospital information integration process in a bus form and comprises the following steps: forming an integrated development environment; the integration engine performs background analysis execution on the integrated projects submitted and released in the integrated development environment; the integrated monitoring system monitors the process of executing the integrated project by the integrated engine; the forming of the integrated development environment comprises an information configuration process and an information integration flow configuration process; the information configuration process comprises the following steps: maintaining endpoint information, namely taking at least one service information system on line in the existing hospital as an endpoint of a source information system and a target information system, and arranging and registering hospital services by configuring endpoint information on a hospital information integration platform; integration engine information maintenance, configuring one or more integration engines; maintaining message information, configuring interactive messages among service information systems, specifying XML Schema of the messages, setting endpoint information capable of sending the message type, and limiting the sending of the messages; maintaining component information, configuring information of a component formed by a message processing unit to realize registration of the component; the information integration process configuration process comprises the following steps: creating a new integrated project, and designating the integrated project as an interface engine mode to enable a business information system to actively send a message to an integrated engine interface; setting a message type sent to an integration engine interface in an integration engine interface configuration window; configuring a receiving endpoint in the integrated project window, calling a receiving endpoint list on the right side of the configuration window from the receiving endpoint to select the endpoint, dragging the endpoint to a target receiving endpoint area, repeating the operation, and setting a plurality of target receiving endpoints; configuring a processing component of a processing flow in the integrated project window, selecting a component from a component list on the right side of the integrated project window, and designing a message component processing sequence; setting a message flow direction; processing and configuring each component; performing message receiving configuration on a receiving endpoint; submitting an integration project; the hospital information integration platform detects the configuration of the submitted integration project; detecting that the configuration of the submitted integrated project is correct and the submission is successful; the background analysis and execution of the integration project submitted and released in the integrated development environment by the integration engine comprises the following steps: the integration engine interface receives the message sent by the service information system, completes format verification, authority verification and validity verification of the message, and then stores the message in a message cache to wait for the integration engine instance to process; locking a batch of messages by the integration engine instance, and retrieving all integration items matched with the message types according to the configuration information of the integration items; executing integration items by Free threads in the integration engine thread pool respectively; the integration engine loads the corresponding component processing module according to the integration flow and transmits message instance information and profile information; the component processing module processes the input message and returns the output message to the integration engine; when executing to a target receiving endpoint, the integration engine tries to call an access interface configured by the target receiving endpoint; after the target receiving end point finishes processing, if the interface is provided with a return value, the integration engine is responsible for receiving the return value, calling a callback interface of a service system for sending a message according to the interface record of the access integration engine and transmitting parameter information; the integration engine records log information of all execution processes in the whole integration project, and returns final execution success or failure result information to the cluster manager; the cluster manager updates the execution result of the message, and if the engine processing of one message exceeds a preset time range, the cluster manager forcibly unlocks the message processing and waits for the processing of other integrated engines; the cluster manager periodically transfers the messages exceeding a certain time range to the historical message library, so that the number of cache records of the online message library is reduced, and the access speed of the database is increased.
2. The hospital information integration method according to claim 1, wherein the endpoint information includes endpoint basic information and Inbound message receiving service information, the endpoint basic information includes an endpoint name, an endpoint version, an endpoint service vendor and an endpoint contact, the Inbound message receiving service information includes a service name, a protocol type, a service IP address, a port number, a service method, a method parameter, a parameter type and a timeout setting;
the configuration information of the integrated engine comprises an IP address, a port number, CPU information, memory information and the maximum thread number of a server where engine software is located;
the information of the component includes a display name of the component, component configuration window information, and component processing engine information.
3. The hospital information integration method of claim 2, wherein the component comprises:
the format conversion component is used for converting the message format of the incoming message;
a router component for configuring routing rules for messages incoming to the router;
the term conversion component is used for carrying out term conversion between the service information systems;
the filter component is used for filtering the message according to the judgment of the message content;
an HL7 converter, which is used for converting non-HL 7 standard messages into HL7 standard messages;
the DICOM converter is used for converting the message content into the DICOM standard protocol;
the sequencer is used for sequencing a plurality of incoming messages and sending the messages to the next component in sequence; and
and the aggregator is used for performing content aggregation on the incoming messages and generating new message content.
4. The hospital information integration method of claim 1, wherein the integration engine captures and records anomalies occurring during the processing of the component handling modules.
5. The hospital information integration method according to claim 1, wherein when the integration engine attempts to invoke the access interface configured by the target receiving endpoint, if the access interface is invoked in a failure, the integration engine retries to invoke the access interface configured by the target receiving endpoint within a set failure invocation time range.
6. The hospital information integration method of claim 1, wherein the monitoring of the integration engine executing the integration project process by the integration monitoring system comprises:
displaying the log information in a classified manner;
graphically displaying the message sending quantity, the message receiving quantity, the processing performance consumption, the processing bottleneck point and the execution process of a single integrated project in a certain time period; and
and sending the index exceeding the warning value to a hospital information integration platform administrator in the form of short message and mail.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611207539.XA CN106600499B (en) | 2016-12-23 | 2016-12-23 | Hospital information integration method based on bus form |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611207539.XA CN106600499B (en) | 2016-12-23 | 2016-12-23 | Hospital information integration method based on bus form |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106600499A CN106600499A (en) | 2017-04-26 |
| CN106600499B true CN106600499B (en) | 2021-08-24 |
Family
ID=58601254
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611207539.XA Active CN106600499B (en) | 2016-12-23 | 2016-12-23 | Hospital information integration method based on bus form |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106600499B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110021413A (en) * | 2019-03-01 | 2019-07-16 | 医利捷(上海)信息科技有限公司 | A kind of information for hospital integrated system |
| CN110022358A (en) * | 2019-03-11 | 2019-07-16 | 宸瑞普惠(广州)科技有限公司 | Data processing method and integrating engine towards medical data exchange |
| CN110047579A (en) * | 2019-04-08 | 2019-07-23 | 安徽汇迈信息科技有限公司 | A kind of information for hospital integrated platform system |
| CN111125200A (en) * | 2019-11-12 | 2020-05-08 | 华志微创医疗科技（北京）有限公司 | HL7 message processing method and system based on database query |
| CN113808723B (en) * | 2021-09-30 | 2023-08-22 | 北京蓝海医信科技有限公司 | Service system information integration platform |
| CN113806394A (en) * | 2021-09-30 | 2021-12-17 | 北京蓝海医信科技有限公司 | Query system based on SQL (structured query language) querier |
| CN113806182B (en) * | 2021-09-30 | 2024-04-05 | 北京蓝海医信科技有限公司 | Interactive flow monitoring method based on information integration platform and computer equipment |
| CN117725569A (en) * | 2024-02-06 | 2024-03-19 | 中科云谷科技有限公司 | Security management system for data computation |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101021912A (en) * | 2006-02-13 | 2007-08-22 | 中山市人民医院 | Hospital information system |
| CN101286953A (en) * | 2008-06-02 | 2008-10-15 | 杭州创业软件股份有限公司 | Medical system information integration platform |
| CN101350041A (en) * | 2008-08-19 | 2009-01-21 | 杭州创业软件股份有限公司 | High speed data caching digitalization hospital information system integrated platform |
| CN102316169A (en) * | 2011-09-29 | 2012-01-11 | 北京邮电大学 | Method for realizing quick service convergence and general service platform |
| CN103944968A (en) * | 2014-03-28 | 2014-07-23 | 云浮南风数字科技有限公司 | Heterogeneous medical data information integration and sharing system based on home-based care for the aged |
| CN104991817A (en) * | 2015-06-25 | 2015-10-21 | 国网山东省电力公司 | Configurable integration method and system for information system |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9183064B2 (en) * | 2011-12-30 | 2015-11-10 | General Electric Company | Intelligent mediation of messages in a healthcare product integration platform |
| US20140107499A1 (en) * | 2012-10-12 | 2014-04-17 | True Process, Inc. | Medical Information Management System |
-
2016
- 2016-12-23 CN CN201611207539.XA patent/CN106600499B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101021912A (en) * | 2006-02-13 | 2007-08-22 | 中山市人民医院 | Hospital information system |
| CN101286953A (en) * | 2008-06-02 | 2008-10-15 | 杭州创业软件股份有限公司 | Medical system information integration platform |
| CN101350041A (en) * | 2008-08-19 | 2009-01-21 | 杭州创业软件股份有限公司 | High speed data caching digitalization hospital information system integrated platform |
| CN102316169A (en) * | 2011-09-29 | 2012-01-11 | 北京邮电大学 | Method for realizing quick service convergence and general service platform |
| CN103944968A (en) * | 2014-03-28 | 2014-07-23 | 云浮南风数字科技有限公司 | Heterogeneous medical data information integration and sharing system based on home-based care for the aged |
| CN104991817A (en) * | 2015-06-25 | 2015-10-21 | 国网山东省电力公司 | Configurable integration method and system for information system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106600499A (en) | 2017-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106600499B (en) | Hospital information integration method based on bus form | |
| US8984535B2 (en) | System and method for facilitating the exchange of information among applications | |
| US7673029B2 (en) | Grid automation bus to integrate management frameworks for dynamic grid management | |
| US7565662B2 (en) | Program agent initiated processing of enqueued event actions | |
| US7970823B2 (en) | System for sharing data objects among applications | |
| EP3446440B1 (en) | Multi-stage network discovery | |
| JP6514687B2 (en) | Flexible node configuration method and system in local or distributed computer system | |
| US8266630B2 (en) | High-performance XML processing in a common event infrastructure | |
| JP2005196767A (en) | Scheduler supporting web service invocation | |
| WO2020036772A1 (en) | Software acceleration platform for supporting decomposed, on-demand network services | |
| EP1393171A2 (en) | Method and system for incorporating legacy applications into a distributed data processing environment | |
| WO2006044721A2 (en) | Interfacing disparate software applications | |
| CN104468299A (en) | Enterprise service bus system based on user rule | |
| US20070233876A1 (en) | Interprocess communication management using a socket layer | |
| KR100704300B1 (en) | Jointly use system for arranged server in network and operation-method it | |
| US9906604B2 (en) | System and method for dynamic discovery of web services for a management console | |
| CN109951370B (en) | Hierarchical interconnection method and device for big data centers | |
| US9374416B2 (en) | Universal architecture for client management extensions on monitoring, control, and configuration | |
| US9442746B2 (en) | Common system services for managing configuration and other runtime settings of applications | |
| US20220101962A1 (en) | Enabling distributed semantic mashup | |
| CN107347024A (en) | A kind of method and apparatus for storing Operation Log | |
| US8930523B2 (en) | Stateful business application processing in an otherwise stateless service-oriented architecture | |
| US20220191167A1 (en) | Organizational modelling for routing rpa related services of an rpa cloud suite | |
| CN116880970A (en) | Application function calling method and device, terminal equipment and storage medium | |
| EP1789878B1 (en) | Systems and methods enabling interoperability between network centric operation (nco) environments |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |