A medical event triggering execution method and system

By designing a medical event trigger execution system in the medical information system, and using the platform layer to achieve linkage between multiple business applications, the problems of high management costs and long information construction cycle in the existing technology are solved, and information resources are realized Unified management and data compatibility.

CN114613483BActive Publication Date: 2024-11-08SUZHOU ZHENQU INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210381195.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-04-12
Publication Date
2024-11-08
Estimated Expiration
2042-04-12

AI Technical Summary

Technical Problem

The lack of linkage between existing medical information systems among multiple business applications has led to high management costs and long information construction cycles, and the inability to achieve unified information compatibility, which has the pain points of fragmented management.

Method used

Design a medical event trigger execution system, including the platform layer, application layer and terminal layer, realize the medical event trigger execution between multiple business applications through the platform layer, and use registration instructions, monitoring data sets and rules sets to trigger medical events. Judgment and execution.

Benefits of technology

It has achieved linkage between multiple business applications, shortened the information construction cycle, reduced the information upgrading cost, solved the pain points of fragmented management, and realized the unified management of information resources and the orderly opening of data.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114613483B_ABST
    Figure CN114613483B_ABST
Patent Text Reader

Abstract

The present invention relates to a method and system for triggering and executing a medical event. The system includes a platform layer, an application layer, and a terminal layer. The application layer initiates a registration instruction of at least one business application to the platform layer; the platform layer registers according to the registration instruction of at least one business application to obtain at least one target business application; the terminal layer obtains a monitoring data set of a terminal corresponding to each target business application, and reports each monitoring data set to the platform layer; the platform layer obtains a rule set for each target business application, and triggers and executes a medical event for each target business application according to the rule set and monitoring data set corresponding to each target business application. The present invention is based on a universal platform to realize the triggering and execution of medical events between multiple business applications, connect and link various business applications, open information in an orderly manner, and make data unified and compatible, so as to solve the pain points of fragmented management of various business applications and realize the unified management of information resources.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of medical information technology, and in particular to a medical event triggering execution method and system. Background Art

[0002] With the development of information technology, medical information systems are installed in hospitals and nursing homes, which are applied to various IoT devices and involve a wide range of business applications, including comprehensive monitoring, hospital security, and nursing care. With the continuous expansion of hospitals and nursing homes, as well as the continuous development of Internet IT technology and digital transformation, the importance of medical information management has gradually become apparent.

[0003] However, the existing medical information systems in these scenarios are all designed for a specific need (or business application) in the process of medical information management. For example, the energy consumption management system only manages energy consumption medical information, and the infusion management system only manages infusion medical information. If medical information management is required for multiple business applications, different suppliers are usually required to complete the management systems of the corresponding business applications. The management systems of these business applications are separated from each other in terms of business and information independence, and each system is independently developed and deployed, resulting in high development and management and maintenance costs. The management systems of each business application often need to spend a lot of time on their own to study the triggering and execution of medical events such as alarms, but cannot achieve linkage, nor can they focus on the development of business applications. The information construction cycle is long and the upgrade cost is high. Summary of the invention

[0004] The technical problem to be solved by the present invention is to address the deficiencies of the above-mentioned prior art and to provide a medical event triggering execution method and system, which realizes the triggering execution of medical events between multiple business applications based on a common platform, connects and links each independent business application, allows each system to focus on business application development, shortens the information construction cycle, effectively reduces the cost of information upgrade, and makes information open in an orderly manner and data unified and compatible, thereby solving the pain points of fragmented management of various business applications and realizing unified management of information resources.

[0005] The technical solution of the present invention to solve the above technical problems is as follows:

[0006] A medical event trigger execution system comprises a platform layer, an application layer and a terminal layer, wherein the platform layer is respectively connected to the application layer and the terminal layer for communication;

[0007] The application layer is used to initiate a registration instruction of at least one business application to the platform layer;

[0008] The platform layer is used to register corresponding business applications according to the registration instruction of at least one business application, and obtain at least one target business application;

[0009] The terminal layer is used to obtain a monitoring data set of a terminal corresponding to each target business application, and report the monitoring data set corresponding to each target business application to the platform layer;

[0010] The platform layer is also used to obtain the rule set of each target business application, and trigger the execution of medical events for each target business application according to the rule set and monitoring data set corresponding to each target business application.

[0011] According to another aspect of the present invention, a medical event trigger execution method is also provided, which uses the medical event trigger execution system of the present invention to perform medical event trigger execution, including the following steps:

[0012] Using the application layer, initiate a registration instruction of at least one business application to the platform layer;

[0013] Using the platform layer, registering corresponding business applications respectively according to the registration instruction of at least one business application to obtain at least one target business application;

[0014] Using the terminal layer, obtaining a monitoring data set of the terminal corresponding to each target business application, and reporting the monitoring data set corresponding to each target business application to the platform layer;

[0015] The platform layer is used to obtain the rule set of each target business application, and the medical event trigger execution is performed on each target business application according to the rule set and monitoring data set corresponding to each target business application.

[0016] The beneficial effects of the medical event triggering execution method and system of the present invention are as follows: the application layer includes multiple business applications, each business application is for a specific demand in the medical information management process; in the medical information management process, the application layer is first used to initiate a registration instruction of at least one business application to the platform layer, so as to facilitate the registration of the business application that needs to trigger the execution of medical events (specifically including the triggering judgment of medical events and the determination of execution actions) at the platform layer; then the platform layer performs application registration according to the registration instruction of at least one business application, and the at least one target business application obtained is the registered business application, which facilitates the subsequent triggering and execution of medical events for the registered business application (i.e., the target business application), and also facilitates the terminals in the terminal layer (the terminal layer includes multiple terminals) to report the corresponding monitoring data set according to the target business application; finally, the platform layer is used to obtain the rule set of each target business application, and based on the rule set, the triggering judgment of medical events and the determination of execution actions can be realized in combination with the monitoring data set reported by the terminal layer, thereby realizing the triggering and execution of medical events for the target business application;

[0017] The medical event triggering and execution method and system of the present invention implement the triggering and execution judgment of medical events corresponding to all business applications by the platform layer, and implement the triggering and execution of medical events between multiple business applications based on the universal platform, which can connect and link each independent business application, allowing each system to focus on business application development, shortening the information construction cycle, and effectively reducing the cost of information upgrades. Information is opened in an orderly manner, and data is unified and compatible, solving the pain points of fragmented management of various business applications and realizing unified management of information resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 This is a structural diagram of a medical event triggering execution system in Embodiment 1 of the present invention;

[0019] Figure 2 This is a structural diagram of another medical event triggering execution system in Embodiment 1 of the present invention;

[0020] Figure 3 This is a flow chart of a method for triggering execution of a medical event in Embodiment 2 of the present invention;

[0021] Figure 4 This is a flow chart of performing medical event triggering execution judgment on each target business application in the second embodiment of the present invention;

[0022] Figure 5 This is a flow chart of determining whether the i-th target business application satisfies the medical event triggering condition in the second embodiment of the present invention. DETAILED DESCRIPTION

[0023] The principles and features of the present invention are described below in conjunction with the accompanying drawings. The examples given are only used to explain the present invention and are not used to limit the scope of the present invention.

[0024] The present invention will be described below in conjunction with the accompanying drawings.

[0025] Embodiment 1: Figure 1 As shown, a medical event trigger execution system includes a platform layer, an application layer and a terminal layer, wherein the platform layer is communicatively connected with the application layer and the terminal layer respectively;

[0026] The application layer is used to initiate a registration instruction of at least one business application to the platform layer;

[0027] The platform layer is used to register corresponding business applications according to the registration instruction of at least one business application, and obtain at least one target business application;

[0028] The terminal layer is used to obtain a monitoring data set of a terminal corresponding to each target business application, and report the monitoring data set corresponding to each target business application to the platform layer;

[0029] The platform layer is also used to obtain the rule set of each target business application, and trigger the execution of medical events for each target business application according to the rule set and monitoring data set corresponding to each target business application.

[0030] The application layer contains multiple business applications, and the terminal layer contains multiple terminals; each business application in the application layer corresponds to the terminal in the terminal layer, that is, one business application corresponds to one business terminal (i.e. one-to-one, the number of business applications and terminals is the same), for example, when the terminal is a smart positioning card (worn by medical staff), the corresponding business application is a medical staff management application; for example, when the terminal is a smart positioning bracelet (worn by patients), the corresponding business application is a patient management application. It can also be that one business application corresponds to multiple terminals (i.e. one-to-many, the number of business applications and terminals is different), for example, when the business application is a vital signs monitoring application, the corresponding terminals include a temperature patch terminal (for monitoring patient temperature), a wireless oximeter (for monitoring patient blood oxygen), a wireless sphygmomanometer (for monitoring patient blood pressure), and a smart mattress (for monitoring patient breathing, heart rate, body movement, etc.).

[0031] It should be noted that in the above-mentioned one-to-many situation, the multiple terminals corresponding to one business application may overlap or overlap with the multiple terminals corresponding to another business application. For example, when the terminal is a temperature patch terminal, it can correspond to both a vital signs monitoring application and a patient management application.

[0032] In this embodiment, the correspondence between the above-mentioned terminals and business applications is pre-set before the medical event triggers the execution judgment.

[0033] In this embodiment, each business application is for a specific demand in the medical information management process; in the medical information management process, the application layer is first used to initiate a registration instruction of at least one business application to the platform layer, so as to facilitate the registration of business applications that need to trigger and execute medical events (specifically including trigger judgment of medical events and determination of execution actions) at the platform layer; then the platform layer registers the application according to the registration instruction of at least one business application, and the at least one target business application obtained is the registered business application, which facilitates the subsequent triggering and execution of medical events for the registered business application (i.e., the target business application), and also facilitates the terminals in the terminal layer to report the corresponding monitoring data set according to the target business application; finally, the platform layer is used to obtain the rule set of each target business application, and based on the rule set, it can be combined with the monitoring data set reported by the terminal layer to realize the trigger judgment of medical events and the determination of execution actions, etc., thereby realizing the triggering and execution of medical events for the target business application.

[0034] In the medical event triggering and execution system of this embodiment, the triggering and execution judgment of medical events corresponding to all business applications are implemented by the platform layer. The triggering and execution of medical events between multiple business applications are realized based on this common platform, which can connect and link each independent business application, allowing each system to focus on business application development, shortening the information construction cycle, and effectively reducing the cost of information upgrade. Information is opened in an orderly manner, and data is unified and compatible, which solves the pain points of fragmented management of various business applications and realizes unified management of information resources.

[0035] Preferably, the application layer is further used to create a rule set for each target business application and send each rule set to the platform layer;

[0036] The platform layer is specifically used to receive and save the rule set of each target business application.

[0037] In the above embodiment, the process of creating a rule set for each target business application is completed by the application layer, and the platform layer only needs to receive, save and manage the rule set, which can reduce the resources occupied by the platform layer to a certain extent and is conducive to ensuring the accuracy of the platform layer in subsequent medical event triggering judgments.

[0038] Preferably, the platform layer is specifically used to create a rule set for each target business application.

[0039] In the above embodiment, the platform layer itself can also create a rule set, which can further realize the linkage between various business applications, solve the pain points of fragmented management of various business applications, and realize unified management of information resources.

[0040] Preferably, the platform layer is also specifically used for:

[0041] Receive the monitoring data set reported by the terminal corresponding to each target business application, and parse each monitoring data set respectively to obtain the parsed data set corresponding to each target business application;

[0042] For the i-th target business application, judging whether the i-th target business application meets the preset medical event triggering condition according to the parsing data set and rule set corresponding to the i-th target business application, where i is a positive integer;

[0043] When the i-th target business application meets the medical event triggering condition, judging whether the i-th target business application meets the preset medical event execution condition according to the corresponding parsing data set and rule set;

[0044] When the i-th target business application meets the medical event execution condition, the medical event execution action corresponding to the i-th target business application is determined from a preset action execution mode set according to the corresponding parsed data set and rule set;

[0045] Traverse each target business application and determine the medical event execution action for each target business application.

[0046] By parsing the monitoring data set reported by the terminal corresponding to each target business application, the subsequent platform layer can perform triggering and execution judgments on medical events based on the obtained parsed data set, thereby improving the efficiency and accuracy of triggering and execution judgments. For each target business application, the platform layer is based on the parsed data set and rule set, and follows the above three steps to determine whether a medical event has occurred (i.e., whether the medical event triggering conditions have been triggered), whether the medical event execution conditions have been met, and the corresponding medical event execution actions have been determined. This can more accurately realize the triggering and execution judgments of medical events in medical scenarios such as hospitals or nursing homes, thereby improving medical information management and information construction.

[0047] It should be noted that, since each terminal usually monitors multiple data, a monitoring data set is used to represent all data monitored by each terminal.

[0048] Specifically, when parsing the monitoring data set reported by each terminal, the data requirement standard of the business application corresponding to each terminal is used for parsing, and the data requirement standard can be set in advance. It should be noted that in addition to reporting the monitoring data set generated by actual monitoring, each terminal can also report pre-bound basic information, such as medical staff information, patient information, and equipment information.

[0049] Specifically, the rule set corresponding to each target business application includes a trigger judgment rule, an execution judgment rule and an action determination rule.

[0050] Specifically, a rule engine is provided in the platform layer, and the rule engine includes an event trigger condition judgment module, an event execution condition judgment module and an event execution action determination module which are executed in sequence;

[0051] For the i-th target business application, the event trigger condition judgment module is used to judge whether the i-th target business application meets the corresponding medical event trigger condition according to the trigger judgment rule and the parsed data set corresponding to the i-th target business application; the event execution condition judgment module is used to judge whether the i-th target business application meets the corresponding medical event execution condition according to the execution judgment rule and the parsed data set corresponding to the i-th target business application; the event execution action determination module is used to determine the medical event execution action corresponding to the i-th target business application from the action execution method set according to the action determination rule and the parsed data set corresponding to the i-th target business application.

[0052] The above rule set makes it easier for the rule engine in the platform layer to trigger execution judgments for medical events for each business application according to the rules provided by the rule set, thereby realizing the management of medical information and improving the management and informatization of medical scenarios such as hospitals or nursing homes.

[0053] It should be noted that the number of conditions in the medical event triggering conditions and the medical event execution conditions can include one or more. When the medical event triggering conditions are set with multiple conditions, as long as the platform layer determines that the i-th target business application meets one of the conditions, it can be determined that the i-th target business application meets the medical event triggering conditions, and the next step of the medical event execution condition determination process can be carried out. When the medical event execution conditions are set with multiple conditions, only when the platform layer determines that the i-th target business application meets all conditions can it be determined that the i-th target business application meets the medical event execution conditions, and the next step of the medical event execution action determination process can be carried out.

[0054] Specifically, the medical event triggering conditions include first-type event triggering conditions and second-type event triggering conditions;

[0055] The platform layer determines whether the i-th target business application meets the medical event triggering condition, specifically including:

[0056] Determine whether the parsed data set corresponding to the i-th target business application belongs to the positioning data type;

[0057] If yes, the parsed data set corresponding to the i-th target business application is processed to obtain the positioning coordinate information and event information corresponding to the i-th target business application; and according to the positioning coordinate information and event information corresponding to the i-th target business application, it is determined whether the i-th target business application meets the first type of event triggering condition;

[0058] If not, it is determined whether the selected target business application meets the second type of event triggering condition according to the parsed data set corresponding to the i-th target business application.

[0059] In the process of judging whether the target business application meets the triggering condition of the medical event in the above platform layer, the judgment process is divided into two categories according to the data type of the parsed data set. The data type includes a positioning data type and a non-positioning data type. When it is a positioning data type, it is necessary to first obtain the positioning coordinate information and event information from the parsed data set, and then judge whether to trigger a medical event based on the positioning coordinate information and event information and the corresponding first-class event triggering condition (i.e., the event triggering condition preset for the positioning data class); and when it is a non-positioning data type, directly judge whether to trigger a medical event based on the parsed data set and the corresponding second-class event triggering condition (i.e., the event triggering condition preset for the non-positioning data class). The above judgment method can make a medical event trigger judgment based on different scenarios and environments in actual situations, is applicable to various medical scenarios and different situations in medical scenarios, and the trigger judgment is more accurate.

[0060] In a specific embodiment, the parsed data set is processed to obtain positioning coordinate information (X, Y) and event information; by pre-addressing the coordinate information, when the positioning coordinate information is obtained, the address corresponding to the positioning coordinate information will first be determined according to the pre-addressing. For example, when the coordinate information is specifically (X1, Y1), and the event information is "a one-key alarm is initiated", according to the preset addressing, the address corresponding to the coordinate information is Ward 210, Area A, Floor 2, Building 3, which means "a one-key alarm is initiated in Ward 210, Area A, Floor 2, Building 3"; for another example, when the coordinate information is specifically (X2, Y2), the event information is "a one-key alarm is initiated", and the address corresponding to the coordinate information is obtained in the same way as the elderly leisure area, which means "a one-key alarm is initiated in the elderly leisure area". Afterwards, a judgment is made based on the obtained address and event information, combined with the preset first-class event triggering conditions.

[0061] In another specific embodiment, for example, in a hospital hospitalization scenario, when the parsed data set is specifically the temperature data sent by a temperature patch terminal, for example, the temperature data is 38.1 degrees Celsius, which is a non-positioning data type, it is directly determined whether the temperature data meets the second type of event triggering condition.

[0062] Specifically, the medical event execution conditions include event duration, event triggering time, event interval time and event triggering position.

[0063] Through the above-mentioned medical event execution conditions, false triggering or abnormal reporting can be effectively avoided before the medical event is executed.

[0064] Specifically, the duration of an event refers to how long the device continues to be triggered (or the duration of the medical event trigger condition being met), which can filter abnormal reporting situations. The event trigger time refers to the time range within which the device is triggered (or the time when the medical event trigger condition is met), such as being able to set it to trigger only on weekdays. The event interval time refers to how long it has been since the last trigger (or the time interval since the last time the medical event trigger condition was met), to prevent continuous alarms; the event trigger location refers to when the device is triggered in certain specific places (or the location of occurrence when the medical event trigger condition is met), which can be specified in advance.

[0065] Preferably, the action execution mode set includes a first execution mode, a second execution mode and a third execution mode;

[0066] For the i-th target business application, the first execution mode is specifically: the platform layer sends the corresponding parsed data set to the i-th target business application in the application layer, and the i-th target business application executes according to the corresponding parsed data set; the second execution mode is specifically: the platform layer generates an execution instruction according to the parsed data set corresponding to the i-th target business application, and sends the corresponding execution instruction to the terminal corresponding to the i-th target business application in the terminal layer, and the terminal corresponding to the i-th target business application executes according to the corresponding execution instruction; the third execution mode is specifically: the platform layer directly executes according to the preset execution content corresponding to the i-th target business application.

[0067] Through the above-mentioned multiple execution methods, when a medical event is triggered and the execution conditions of the medical event are met, the medical event can be executed from multiple perspectives to ensure that the medical event can be executed normally and improve the entire medical information system.

[0068] It should be noted that the medical event execution action determined by the platform layer can be any one of the three execution methods mentioned above, that is, it can be executed according to any one execution method, or it can be three, that is, the three execution methods are executed simultaneously.

[0069] Specifically, when the determined medical event execution action includes the second execution mode, the terminal issued by the platform layer is one or more terminals closest to the platform layer (for example, the one or more terminals can be obtained using the shortest path planning algorithm). For example, when the platform layer parses and processes the monitoring data set reported by a terminal to obtain the information "a one-button alarm was triggered in the bathroom of Room 101", a caregiver closest to the terminal is selected, and an execution instruction of an event processing notification is sent to the work card worn by the caregiver; or, multiple caregivers at the caregiver station closest to the terminal are selected, and an execution instruction of an event processing notification is sent to the work cards they wear.

[0070] In a specific embodiment, the preset execution content can be sending a text message or email notification to the responsible person, or monitoring linkage, recording abnormal log records, and displaying them on the operation and maintenance screen in the medical information system. The execution content of the business application in the first execution mode and the execution content of the terminal in the second execution mode are similar to the preset execution content.

[0071] Specifically, the structure of the medical event trigger execution system and the functions performed by each unit in this embodiment are as follows: Figure 2 shown.

[0072] Embodiment 2: Figure 3 As shown, a medical event triggering execution method, using the medical event triggering execution system in embodiment 1 to trigger and execute medical events, includes the following steps:

[0073] S1: Using the application layer, initiate a registration instruction for at least one business application to the platform layer;

[0074] S2: using the platform layer, registering corresponding business applications respectively according to the registration instruction of at least one business application, to obtain at least one target business application;

[0075] S3: using the terminal layer, obtaining a monitoring data set of the terminal corresponding to each target business application, and reporting the monitoring data set corresponding to each target business application to the platform layer;

[0076] S4: Utilize the platform layer to obtain the rule set of each target business application, and trigger the execution of medical events for each target business application according to the rule set and monitoring data set corresponding to each target business application.

[0077] In the process of medical information management, the application layer is first used to initiate a registration instruction of at least one business application to the platform layer, so as to facilitate the registration of business applications that need to trigger and execute medical events (specifically including trigger judgment of medical events and determination of execution actions) at the platform layer; then, the platform layer is used to register applications according to the registration instruction of at least one business application, and the at least one target business application obtained is a registered business application, which is convenient for subsequent triggering and executing medical events for registered business applications (i.e., target business applications), and also convenient for terminals in the terminal layer to report corresponding monitoring data sets according to target business applications; finally, the platform layer is used to obtain a rule set for each target business application, and based on the rule set, the trigger judgment of medical events and the determination of execution actions can be realized in combination with the monitoring data set reported by the terminal layer, thereby realizing the triggering and execution of medical events for the target business application;

[0078] In the medical event triggering execution method of this embodiment, the triggering and execution judgment work of medical events corresponding to all business applications are implemented by the platform layer. Based on this universal platform, the triggering and execution of medical events between multiple business applications can be realized, and each independent business application can be linked together, so that each system can focus on business application development, shorten the information construction cycle, effectively reduce the cost of information upgrade, orderly open information, unified and compatible data, solve the pain points of fragmented management of various business applications, and realize unified management of information resources. .

[0079] Preferably, in S4, the specific steps of using the platform layer to obtain the rule set of each target business application include:

[0080] Using the application layer, creating a rule set for each target business application, and sending each rule set to the platform layer;

[0081] Using the platform layer, receiving and saving a rule set for each target business application;

[0082] or

[0083] Using the platform layer, a rule set for each target business application is created.

[0084] Preferably, if Figure 4 As shown, in S4, using the platform layer, the specific steps of performing medical event triggering execution judgment on each target business application according to the rule set and monitoring data set corresponding to each target business application include:

[0085] S41: using the platform layer, receiving the monitoring data set reported by the terminal corresponding to each target business application, and parsing each monitoring data set respectively to obtain the parsed data set corresponding to each target business application;

[0086] S42: for the i-th target business application, using the platform layer, according to the parsing data set and the rule set corresponding to the i-th target business application, determining whether the i-th target business application meets the preset medical event triggering condition, where i is a positive integer;

[0087] S43: When the i-th target business application meets the medical event triggering condition, judging whether the i-th target business application meets the preset medical event execution condition according to the corresponding parsing data set and rule set;

[0088] S44: when the i-th target business application meets the medical event execution condition, determining the medical event execution action corresponding to the i-th target business application from a preset action execution mode set according to the corresponding parsed data set and rule set;

[0089] S45: Utilizing the platform layer, traverse each target business application and determine the medical event execution action of each target business application.

[0090] By parsing the monitoring data set reported by the terminal corresponding to each target business application, the subsequent platform layer can perform triggering and execution judgments on medical events based on the obtained parsed data set, thereby improving the efficiency and accuracy of triggering and execution judgments. For each target business application, the platform layer is based on the parsed data set and rule set, and follows the above three steps to determine whether a medical event has occurred (i.e., whether the medical event triggering conditions have been triggered), whether the medical event execution conditions have been met, and the corresponding medical event execution actions have been determined. This can more accurately realize the triggering and execution judgments of medical events in medical scenarios such as hospitals or nursing homes, thereby improving medical information management and information construction.

[0091] Preferably, if Figure 5 As shown, the medical event triggering condition includes a first type of event triggering condition and a second type of event triggering condition;

[0092] Then in S42, the platform layer is used to determine whether the i-th target business application meets the medical event triggering condition, specifically including:

[0093] S421: Determine whether the parsed data set corresponding to the i-th target business application belongs to the positioning data type;

[0094] S422: If yes, process the parsed data set corresponding to the i-th target business application to obtain the location coordinate information and event information corresponding to the i-th target business application; and determine whether the i-th target business application meets the first type of event triggering condition according to the location coordinate information and event information corresponding to the i-th target business application;

[0095] S423: If not, determine whether the selected target business application meets the second type of event triggering condition according to the parsed data set corresponding to the i-th target business application.

[0096] In the above process of using the platform layer to determine whether the target business application meets the medical event triggering conditions, the judgment process is divided into two categories according to the data type of the parsed data set. The data type includes a positioning data type and a non-positioning data type. When it is a positioning data type, it is necessary to first obtain the positioning coordinate information and event information from the parsed data set, and then judge whether to trigger a medical event based on the positioning coordinate information and event information and the corresponding first-class event triggering conditions; and when it is a non-positioning data type, directly judge whether to trigger a medical event based on the parsed data set and the corresponding second-class event triggering conditions. The above judgment method can make medical event triggering judgments based on different scenarios and environments in actual situations, and is applicable to various medical scenarios and different situations in medical scenarios, and the triggering judgment is more accurate.

[0097] Preferably, the medical event execution conditions include event duration, event triggering time, event interval time and event triggering position.

[0098] Through the above-mentioned medical event execution conditions, false triggering or abnormal reporting can be effectively avoided before the medical event is executed.

[0099] Preferably, the action execution mode set includes a first execution mode, a second execution mode and a third execution mode;

[0100] For the i-th target business application, the first execution mode is specifically: the platform layer sends the corresponding parsed data set to the i-th target business application in the application layer, and the i-th target business application executes according to the corresponding parsed data set; the second execution mode is specifically: the platform layer generates an execution instruction according to the parsed data set corresponding to the i-th target business application, and sends the corresponding execution instruction to the terminal corresponding to the i-th target business application in the terminal layer, and the terminal corresponding to the i-th target business application executes according to the corresponding execution instruction; the third execution mode is specifically: the platform layer directly executes according to the preset execution content corresponding to the i-th target business application.

[0101] Through the above-mentioned multiple execution methods, when a medical event is triggered and the execution conditions of the medical event are met, the medical event can be executed from multiple perspectives to ensure that the medical event can be executed normally and improve the entire medical information system.

[0102] For details not included in this embodiment, please refer to Embodiment 1 and Figure 1 to Figure 2 The specific description content will not be repeated here.

[0103] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A medical event trigger execution system, characterized in that: It includes a platform layer, an application layer and a terminal layer, wherein the platform layer is communicatively connected with the application layer and the terminal layer respectively; The application layer is used to initiate a registration instruction of at least one business application to the platform layer; The platform layer is used to register corresponding business applications according to the registration instruction of at least one business application, and obtain at least one target business application; The terminal layer is used to obtain a monitoring data set of a terminal corresponding to each target business application, and report the monitoring data set corresponding to each target business application to the platform layer; The platform layer is also used to obtain a rule set for each target business application, and trigger execution of a medical event for each target business application according to the rule set and monitoring data set corresponding to each target business application; The platform layer is also specifically used for: Receive the monitoring data set reported by the terminal corresponding to each target business application, and parse each monitoring data set respectively to obtain the parsed data set corresponding to each target business application; For the i-th target business application, judging whether the i-th target business application meets the preset medical event triggering condition according to the parsing data set and rule set corresponding to the i-th target business application, where i is a positive integer; When the i-th target business application meets the medical event triggering condition, judging whether the i-th target business application meets the preset medical event execution condition according to the corresponding parsing data set and rule set; When the i-th target business application meets the medical event execution condition, the medical event execution action corresponding to the i-th target business application is determined from a preset action execution mode set according to the corresponding parsed data set and rule set; Traverse each target business application and determine the medical event execution action for each target business application; The medical event triggering conditions include first-category event triggering conditions and second-category event triggering conditions; The platform layer determines whether the i-th target business application meets the medical event triggering condition, specifically including: Determine whether the parsed data set corresponding to the i-th target business application belongs to the positioning data type; If yes, the parsed data set corresponding to the i-th target business application is processed to obtain the positioning coordinate information and event information corresponding to the i-th target business application; and according to the positioning coordinate information and event information corresponding to the i-th target business application, it is determined whether the i-th target business application meets the first type of event triggering condition; If not, judging whether the selected target business application meets the second type of event triggering condition according to the parsed data set corresponding to the i-th target business application; The medical event execution conditions include event duration, event triggering time, event interval time, and event triggering position; The action execution mode set includes a first execution mode, a second execution mode and a third execution mode; For the i-th target business application, the first execution mode is specifically: the platform layer sends the corresponding parsed data set to the i-th target business application in the application layer, and the i-th target business application executes according to the corresponding parsed data set; the second execution mode is specifically: the platform layer generates an execution instruction according to the parsed data set corresponding to the i-th target business application, and sends the corresponding execution instruction to the terminal corresponding to the i-th target business application in the terminal layer, and the terminal corresponding to the i-th target business application executes according to the corresponding execution instruction; the third execution mode is specifically: the platform layer directly executes according to the preset execution content corresponding to the i-th target business application.

2. The medical event trigger execution system according to claim 1, characterized in that: The application layer is also used to create a rule set for each target business application and send each rule set to the platform layer; The platform layer is specifically used to receive and save the rule set of each target business application.

3. The medical event trigger execution system according to claim 1, characterized in that: The platform layer is specifically used to create a rule set for each target business application.

4. A medical event trigger execution method, characterized in that: Using the medical event trigger execution system as described in any one of claims 1 to 3 to trigger execution of medical events, comprising the following steps: Using the application layer, initiate a registration instruction of at least one business application to the platform layer; Using the platform layer, registering corresponding business applications respectively according to the registration instruction of at least one business application to obtain at least one target business application; Using the terminal layer, obtaining a monitoring data set of the terminal corresponding to each target business application, and reporting the monitoring data set corresponding to each target business application to the platform layer; Using the platform layer, a rule set of each target business application is obtained, and a medical event trigger execution is performed on each target business application according to the rule set and monitoring data set corresponding to each target business application; Using the platform layer, the specific steps of performing medical event triggering execution judgment on each target business application according to the rule set and monitoring data set corresponding to each target business application include: Using the platform layer, receiving the monitoring data set reported by the terminal corresponding to each target business application, and parsing each monitoring data set respectively to obtain the parsed data set corresponding to each target business application; For the i-th target business application, using the platform layer, according to the parsed data set and rule set corresponding to the i-th target business application, determine whether the i-th target business application meets the preset medical event trigger condition, where i is a positive integer; When the i-th target business application meets the medical event triggering condition, judging whether the i-th target business application meets the preset medical event execution condition according to the corresponding parsing data set and rule set; When the i-th target business application meets the medical event execution condition, the medical event execution action corresponding to the i-th target business application is determined from a preset action execution mode set according to the corresponding parsed data set and rule set; Using the platform layer, traverse each target business application and determine the medical event execution action of each target business application; The medical event triggering conditions include first-category event triggering conditions and second-category event triggering conditions; Using the platform layer, determining whether the i-th target business application meets the medical event triggering condition specifically includes: Determine whether the parsed data set corresponding to the i-th target business application belongs to the positioning data type; If yes, the parsed data set corresponding to the i-th target business application is processed to obtain the positioning coordinate information and event information corresponding to the i-th target business application; and according to the positioning coordinate information and event information corresponding to the i-th target business application, it is determined whether the i-th target business application meets the first type of event triggering condition; If not, judging whether the selected target business application meets the second type of event triggering condition according to the parsed data set corresponding to the i-th target business application; The medical event execution conditions include event duration, event triggering time, event interval time, and event triggering position; The action execution mode set includes a first execution mode, a second execution mode and a third execution mode; For the i-th target business application, the first execution mode is specifically: the platform layer sends the corresponding parsed data set to the i-th target business application in the application layer, and the i-th target business application executes according to the corresponding parsed data set; the second execution mode is specifically: the platform layer generates an execution instruction according to the parsed data set corresponding to the i-th target business application, and sends the corresponding execution instruction to the terminal corresponding to the i-th target business application in the terminal layer, and the terminal corresponding to the i-th target business application executes according to the corresponding execution instruction; the third execution mode is specifically: the platform layer directly executes according to the preset execution content corresponding to the i-th target business application.

5. The medical event triggering execution method according to claim 4, characterized in that: Using the platform layer, the specific steps of obtaining the rule set of each target business application include: Using the application layer, creating a rule set for each target business application, and sending each rule set to the platform layer; Using the platform layer, receiving and saving a rule set for each target business application; or Using the platform layer, a rule set for each target business application is created.