Method and device for monitoring service link, storage medium and computer device

Abstract

The application discloses a kind of service link monitoring method and device, storage medium, computer equipment, it is related to digital medical technology field, main purpose is to solve the problem of poor monitoring accuracy of existing service link. Including: in response to the behavior monitoring instruction of medical data, the behavior label of the medical data is acquired, the behavior label is used to represent the identification of the medical behavior in a complete service link to execute and generate the medical data;Determine the stack queue and queue index corresponding to the behavior label, and according to the queue index, the target medical behavior corresponding to the medical data is retrieved from the stack queue;According to the monitoring strategy of the service link, the target medical behavior is processed, and the monitoring result of the service link is obtained, and the monitoring strategy is used to represent the rule that different service links monitor the target medical behavior.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of digital medical technology, and in particular, to a service link monitoring method and device, a storage medium, and a computer device. BACKGROUND

[0002] With the rapid development of digital medical technology, Internet medical enterprises provide medical services for a large number of users through distributed deployment of service equipment. The deployed service equipment can be terminal, server, processor, and other devices. In order to ensure the smooth operation of medical services, it is necessary to monitor the distributed deployment service cluster containing the above-mentioned devices in the whole link.

[0003] At present, the existing whole-link monitoring of the distributed deployment service cluster is usually performed in series according to the service link to monitor the medical behavior. However, due to the large number of devices in the cluster, the series monitoring is time-consuming, and the cross-process service call or asynchronous call is difficult to be monitored in series, which greatly affects the monitoring efficiency of the service link and reduces the monitoring accuracy of the service link. SUMMARY

[0004] Therefore, the present application provides a service link monitoring method and device, a storage medium, and a computer device, which mainly aims to solve the problem of poor monitoring accuracy of the existing service link.

[0005] According to one aspect of the present application, a service link monitoring method is provided, which comprises:

[0006] In response to a behavior monitoring instruction of medical data, an action label of the medical data is obtained, and the action label is used to represent the identification of the medical data generated by the medical behavior in a complete service link;

[0007] A stack queue corresponding to the action label and a queue index are determined, and a target medical behavior corresponding to the medical data is called from the stack queue according to the queue index;

[0008] According to a monitoring strategy of the service link, the target medical behavior is processed to obtain a monitoring result of the service link, and the monitoring strategy is used to represent the rules for monitoring the target medical behavior in different service links.

[0009] Further, before obtaining the action label of the medical data, the method further comprises:

[0010] Based on an abstract class object, a label block for tracking medical data in a service link is created, and the service link contains a plurality of associated medical behaviors;

[0011] When detecting that the medical data is generated by performing the medical behavior, the label block is invoked to mark the medical behavior to obtain a behavior label;

[0012] The storage location of the medical behavior is recorded in the stack queue corresponding to the behavior label, and a matching queue index is generated. The stack queue is used to store the storage locations of all medical behaviors corresponding to the behavior labels obtained in a service link.

[0013] Further, the invoking of the label block to mark the medical behavior to obtain a behavior label comprises:

[0014] If the service link is determined to be a non-unique link based on the thread of the associated medical behavior, the label block is invoked to mark the medical behavior with a unique service link identifier to obtain a behavior label containing the unique service link identifier.

[0015] Further, the recording of the storage location of the medical behavior in the stack queue corresponding to the behavior label comprises:

[0016] When no created stack queue is found according to the behavior type of the behavior label, the generated initial stack queue is marked with the behavior type, and the storage location of the medical behavior is stored in the initial stack queue;

[0017] When a created stack queue is found according to the behavior type of the behavior label, and the stack queue is not full, the storage location of the medical behavior is stored in the stack queue;

[0018] The generation of the matching queue index comprises:

[0019] According to the storage location pointed to by the pointer in the stack queue and the behavior type, the behavior label generates a queue index.

[0020] Further, the invoking of the label block to mark the medical behavior to obtain a behavior label comprises:

[0021] If the target medical behavior corresponding to the behavior label is stored in the storage location pointed to by the first pointer based on the queue index, the target medical behavior is extracted from the storage location;

[0022] If it is determined based on the queue index that the target medical behavior corresponding to the behavior label is stored in a storage location pointed to by a second pointer, a storage location of a medical behavior in a storage location pointed to by the first pointer is cached in a preset cache storage space, and after the target medical behavior is retrieved from the storage location pointed to by the second pointer, the storage location of the medical behavior in the preset cache storage space is re-stored in the stack queue.

[0023] The storage location pointed to by the first pointer is at a top of the stack queue.

[0024] Further, the processing of the target medical behavior according to the monitoring policy of the service link to obtain a monitoring result of the service link includes:

[0025] Analyzing a service type of the service link, the service type including at least one of a medical project execution type, a medical product transaction type, and a medical information processing type;

[0026] Determining the monitoring policy corresponding to the service type based on a preset link monitoring mapping relationship, the link monitoring mapping relationship storing monitoring policies required by different service types, the monitoring policy including at least one of a behavior violation monitoring, a time limit monitoring, and a data authenticity monitoring;

[0027] Monitoring and processing the target medical behavior based on the monitoring policy to generate the monitoring result of the service link.

[0028] Further, the monitoring and processing of the target medical behavior based on the monitoring policy to generate the monitoring result of the service link includes:

[0029] If it is determined based on the behavior violation monitoring that the target medical behavior is a violation operation, a violation monitoring result of the service link is generated, and the violation monitoring result is reported; or,

[0030] If it is determined based on the time limit monitoring that the target medical behavior is a timeout behavior, and / or based on the data authenticity monitoring that the target medical behavior is a counterfeit behavior, an abnormal monitoring result of the service link is generated, and abnormal alarm information is sent to a medical client.

[0031] According to another aspect of the present application, a service link monitoring device is provided, including:

[0032] An acquisition module is configured to acquire a behavior label of medical data in response to a behavior monitoring instruction of the medical data, the behavior label being used to represent an identity of a medical behavior performed in a complete service link to generate the medical data;

[0033] determining a stack queue corresponding to the behavior tag and a queue index, and calling the target medical behavior corresponding to the medical data from the stack queue according to the queue index;

[0034] processing the target medical behavior according to a monitoring policy of the service link to obtain a monitoring result of the service link, the monitoring policy being used to represent a rule for monitoring the target medical behavior by different service links.

[0035] Further, the device further comprises:

[0036] creating a label block for tracking medical data in a service link based on an abstract class object, the service link comprising a plurality of associated medical behaviors;

[0037] calling the label block to mark the medical behavior to obtain a behavior tag when it is detected that the medical behavior generates the medical data;

[0038] generating a stack queue corresponding to the behavior tag and recording a storage location of the medical behavior in the stack queue, and generating a matching queue index, the stack queue being used to store storage locations of medical behaviors corresponding to all behavior tags obtained in a service link.

[0039] Further, the calling module is specifically configured to, if it is determined based on a thread for executing an associated medical behavior that the service link is a non-unique link, mark the medical behavior based on the label block to obtain a behavior tag comprising a unique service link identifier.

[0040] Further, the generating module is specifically configured to, if no stack queue has been created according to a behavior type of the behavior tag, mark an initial stack queue generated with the behavior type and store the storage location of the medical behavior in the initial stack queue; if a stack queue has been created according to the behavior type of the behavior tag and the stack queue is not full, store the storage location of the medical behavior in the stack queue; and generate a queue index according to the storage location of the medical behavior pointed to by a pointer in the stack queue, the behavior type and the behavior tag.

[0041] Further, the determining module is specifically configured to extract the target medical behavior from a storage location pointed to by a first pointer if the target medical behavior corresponding to the behavior label is determined to be stored in the storage location based on the queue index; if the target medical behavior corresponding to the behavior label is determined to be stored in a storage location pointed to by a second pointer, cache the storage location of the medical behavior in the storage location pointed to by the first pointer to a preset cache storage space, and after calling the target medical behavior from the storage location pointed to by the second pointer, re-store the storage location of the medical behavior in the preset cache storage space to the stack queue; wherein the storage location pointed to by the first pointer is at the top of the stack queue.

[0042] Further, the processing module comprises:

[0043] The parsing unit is configured to parse a service type of the service link, the service type comprising at least one of a medical item execution type, a medical product transaction type, and a medical information processing type;

[0044] The determining unit is configured to determine a monitoring strategy corresponding to the service type based on a preset link monitoring mapping relationship, the link monitoring mapping relationship storing monitoring strategies required by different service types, the monitoring strategy comprising at least one of a behavior violation monitoring, a time limit monitoring, and a data authenticity monitoring;

[0045] The generating unit is configured to monitor and process the target medical behavior based on the monitoring strategy, and generate a monitoring result of the service link.

[0046] According to another aspect of the present application, a storage medium is provided, the storage medium storing at least one executable instruction, the executable instruction causing a processor to perform operations corresponding to the above-mentioned service link monitoring method.

[0047] According to still another aspect of the present application, a computer device is provided, comprising a processor, a memory, a communication interface, and a communication bus, the processor, the memory, and the communication interface completing communication with each other through the communication bus.

[0048] The memory is configured to store at least one executable instruction, the executable instruction causing the processor to perform operations corresponding to the above-mentioned service link monitoring method.

[0049] Through the above technical solutions, the technical solutions provided by the embodiments of the present application have at least the following advantages:

[0050] The application provides a service link monitoring method and device, a storage medium and a computer device.

[0051] The above description is only a summary of the technical scheme of the application. In order to make the technical means of the application more clearly understood, the application can be implemented according to the content of the specification, and in order to make the above and other purposes, characteristics and advantages of the application more obvious and easy to understand, the specific embodiments of the application are described below. BRIEF DESCRIPTION OF DRAWINGS

[0052] Various other advantages and benefits will become apparent to those of ordinary skill in the art, upon reading the following detailed description of the preferred embodiments. The accompanying drawings are included to provide a description of preferred embodiments, and are not meant to limit the present application. Furthermore, the same reference numerals are intended to denote the same components throughout the accompanying drawings. In the drawings:

[0053] Figure 1 A service link monitoring method flow chart provided by an embodiment of the application is shown in FIG. 1;

[0054] Figure 2 Another service link monitoring method flow chart provided by an embodiment of the application is shown in FIG. 2;

[0055] Figure 3 Still another service link monitoring method flow chart provided by an embodiment of the application is shown in FIG. 3;

[0056] Figure 4 A service link monitoring device block diagram provided by an embodiment of the application is shown in FIG. 4;

[0057] Figure 5 A structure schematic diagram of a computer device provided by an embodiment of the application is shown in FIG. 5. DETAILED DESCRIPTION

[0058] Exemplary embodiments of the present disclosure will be described in greater detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it is understood that the present disclosure can be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure can be thoroughly and completely understood, and so that the scope of the present disclosure can be conveyed fully to those skilled in the art.

[0059] The full-link monitoring for the distributed deployment service cluster is usually performed by monitoring the medical behaviors in series according to the service link, but due to the large number of devices in the cluster, the series monitoring is time-consuming, and the cross-process service calling or asynchronous calling is difficult to be monitored in series, which greatly affects the monitoring efficiency of the service link and reduces the monitoring accuracy of the service link. The present embodiment provides a service link monitoring method as shown in the figure, which comprises the following steps: Figure 1

[0060] 101. In response to the behavior monitoring instruction of the medical data, the behavior label of the medical data is acquired.

[0061] In the present embodiment, the current execution end is a service end or a processing end of the digital medical system, after the medical service is published through the digital medical system, the user can execute the corresponding medical service through the client, at this time, the client or the service end generates the behavior monitoring instruction for monitoring the medical data, to instruct the current execution end to acquire the behavior label of the medical data. The medical data is all the data generated by the medical behavior of the user in the process of executing the medical service, including but not limited to registration data, medical examination data, medical project execution data, doctor consultation data, etc., which is not limited in the present embodiment. In addition, the behavior label can be composed of a main label and a corresponding auxiliary label, the main label is used to represent the medical service corresponding to a service link, and the auxiliary label is used to represent the behavior corresponding to each medical data under the service link, for example, A-3, which is the third medical behavior under the A service link, which is not limited in the present embodiment.

[0062] It should be noted that in the present embodiment, the medical data is generated based on the medical behavior in the process of executing the medical service, at this time, in order to facilitate the monitoring of the medical service, the medical data is labeled to obtain the behavior label, that is, the behavior label is used to represent the identification of the medical data generated by the medical behavior in a complete service link, so as to acquire the method in the execution step 102. In addition, in the present embodiment, each medical service will execute the corresponding medical behavior according to the complete link in the process of triggering the medical service, for example, the medical service is executed according to the service link corresponding to registration-consultation-prescription, to obtain the medical data according to the specific medical behavior in the process.

[0063] ​102, determine a stack queue corresponding to the behavior label and a queue index, and call the target medical behavior corresponding to the medical data from the stack queue according to the queue index.

[0064] In the embodiment of the present application, after determining the behavior label, the stack queue corresponding to the behavior label is first determined, that is, the main label of each behavior label corresponds to a stack queue, and the storage location of the medical behavior is recorded in the stack queue. Further, the stack position corresponding to the auxiliary label in the behavior label is searched based on the queue index, and the target medical behavior in the storage location to be processed by the monitoring strategy is determined from the position.

[0065] It should be noted that the stack queue in the current execution end is generated based on the medical behavior corresponding to each service link, and the storage location is stacked according to the specific medical behavior stored or cached, so that the queue index is obtained, and the index position corresponding to the stacking and de-stacking is executed by the pointer. The embodiment of the present application does not make specific limitation.

[0066] 103, processing the target medical behavior according to the monitoring strategy of the service link to obtain the monitoring result of the service link.

[0067] In the embodiment of the present application, after determining the target medical behavior to be processed, the monitoring strategy corresponding to the service link is obtained to process the target medical behavior based on the monitoring strategy, and the monitoring result is obtained. Different service links correspond to different monitoring strategies, that is, the monitoring strategy is used to represent the rule of monitoring the target medical behavior by different service links, so as to monitor and judge the complete service link based on the medical behavior. Specifically, the monitoring strategy includes but is not limited to medical service link time monitoring, medical service link rule violation operation monitoring, and the like, and the monitoring result of the complete service link is obtained, such as service link timeout, and the like. The embodiment of the present application does not make specific limitation.

[0068] In another embodiment of the present application, in order to further limit and illustrate, as shown in Figure 2 Before the step of obtaining the behavior label of the medical data, the method further includes:

[0069] 201, creating a label block for tracking medical data in a service link based on an abstract class object;

[0070] 202, when detecting that the medical behavior generates the medical data, calling the label block to mark the medical behavior to obtain a behavior label;

[0071] 203, recording the storage location of the medical behavior in the stack queue corresponding to the behavior label, and generating a matching queue index.

[0072] In order to extract target medical behaviors based on behavior tags, so as to accurately monitor the target medical behaviors, specifically, the medical behaviors generated in the medical service process are tagged by creating a tag block. The tag block is created based on an abstract class object, and an abstract tag block interface such as a tracking tag AbstractTagSpan is configured for the tag block, so that the operation-free Span tag is realized through the interface corresponding to the AbstractTagSpan, that is, the data does not need to be collected, and the memory and cost are reduced. When the user generates a medical behavior after performing a corresponding operation based on the medical service, all the medical behaviors generated in a service link have correlation, at this time, each service link contains the medical behaviors generated by the related services in different medical services, that is, the service link contains multiple associated medical behaviors, so that the service link has uniqueness whether it is cross-business or not, and the service link can be marked with a main tag based on the tag block, such as the service link can include the medical behavior a-1 corresponding to the medical service a and the medical behavior b-2 corresponding to the medical service b, so as to be marked, and the embodiment of the application does not make specific limitation. In addition, after the marking, since the medical behavior is composed of multiple data, the storage location of the medical behavior is put into a stack queue, and the queue index of the generated stack queue is combined to indicate the relationship between the behavior tag and the storage location, so as to be searched. The stack queue is used to store the storage location of the medical behavior corresponding to all the behavior tags obtained in a service link, that is, one service link corresponds to one stack queue, so as to facilitate searching, and the embodiment of the application does not make specific limitation.

[0073] It should be noted that when the tag block is marked based on the tag block, a method interceptor is created, and after the method of the monitoring strategy processing is executed, a post-processing algorithm is called to close the current tag block. In addition, a tracking scene management space can be set, the storage location of the corresponding medical behavior of the behavior tag marked by the active tag block in different scenes is stacked into the stack, if it is entered into the top of the stack, it will be added to the tracking service, and if the stack of the active tag block marked behavior tag is empty, the service ends listening is notified. When the tracking client is implemented, the listener interface is used, and when the tracking service is completed, the data producer is called to generate the index of the corresponding behavior tag of the corresponding tracking service by holding a plurality of queue buffer pools, so as to match the corresponding queue buffer pool.

[0074] In another embodiment of the application, in order to further limit and illustrate, the step of marking the medical behavior by the tag block to obtain the behavior tag includes:

[0075] If it is determined that the service link is a non-unique link based on the thread of performing the associated medical behavior, the medical behavior is marked with a label of unique service link identification based on the tag block, to obtain a behavior label containing the unique service link identification.

[0076] In order to mark the behavior label, when marking the medical data, specifically, first, it is determined whether the service link is a non-unique link based on the thread of performing the associated medical behavior, that is, whether the medical behavior in different medical services is operated, at this time, if the threads of performing the associated medical behavior are different threads, it indicates that the user adopts the medical behavior in different medical services. In order to unify the marking of the label and effectively manage the medical behavior, when the service link is a non-unique link, the medical behavior is marked with a label of unique service link identification based on the tag block, so as to classify the medical behavior in different medical services into one service.

[0077] In another embodiment of the present application, in order to further limit and illustrate, the step of recording the storage location of the medical behavior in the stack queue corresponding to the behavior label comprises:

[0078] When the created stack queue is not found according to the behavior type of the behavior label, the generated initial stack queue is marked with the behavior type, and the storage location of the medical behavior is stored in the initial stack queue;

[0079] When the created stack queue is found according to the behavior type of the behavior label, and the stack queue is not full, the storage location of the medical behavior is stored in the stack queue;

[0080] Correspondingly, the generated matching queue index comprises:

[0081] The queue index is generated according to the storage location pointed by the pointer of the medical behavior stored in the stack queue and the behavior type and the behavior label.

[0082] Since one service link is distinguished by a tag block according to a main tag, each main tag is determined according to a behavior type of a medical behavior, that is, when the medical behavior is marked based on the tag block, the behavior type of each medical behavior corresponds to a marked behavior tag, and therefore, the stack queue is created based on the behavior type corresponding to the behavior tag. The behavior type is used to represent a specific operation type of the medical behavior, including but not limited to a transaction or payment behavior, a download or query behavior, a change behavior, and the like, which are not limited in the embodiments of the present application. Specifically, in a specific implementation scenario, when the created stack queue is not found according to the behavior type of the behavior tag, it is indicated that there is no corresponding stack queue for storing the medical behavior corresponding to the behavior tag at this time, and therefore, the generated initial stack queue is marked with the behavior type, and the storage location of the medical behavior is stored in the initial stack queue. Specifically, in another specific implementation scenario, when the created stack queue is found according to the behavior type of the behavior tag, and the stack queue is not full, it is indicated that the medical behavior after the behavior tag of the medical behavior can be stored in the stack queue, and the storage location of the medical behavior is stored in the stack queue, that is, the stack top is in-stacked, which is not limited in the embodiments of the present application.

[0083] In another embodiment of the present application, in order to further limit and illustrate, the step of retrieving the target medical behavior corresponding to the medical data from the stack queue according to the queue index comprises:

[0084] If it is determined based on the queue index that the target medical behavior corresponding to the behavior tag is stored in the storage location pointed to by the first pointer, the target medical behavior is extracted from the storage location;

[0085] If it is determined based on the queue index that the target medical behavior corresponding to the behavior tag is stored in the storage location pointed to by the second pointer, the storage location of the medical behavior in the storage location pointed to by the first pointer is cached in a preset cache storage space, and after the target medical behavior is retrieved from the storage location pointed to by the second pointer, the storage location of the medical behavior in the preset cache storage space is re-stored in the stack queue.

[0086] In order to realize the calling of the target medical behavior based on the queue index, and since the queue index is the position of the specific queue pointer indicated by the behavior label, that is, the pointer of the behavior label is determined based on the queue index, so as to determine the storage position based on the pointer in the stack queue, wherein if the target medical behavior determined based on the queue index is in the storage position pointed to by the first pointer in the stack queue, at this time, the storage position pointed to by the first pointer is at the top of the stack queue, which means that the direct de-stacking is performed, then the pointer corresponding to the storage position is directly extracted, and the target medical data is called according to the storage position, therefore, the target medical behavior is extracted from the storage position after the storage position is determined. If the target medical behavior corresponding to the behavior label determined based on the queue index is stored in the storage position pointed to by the second pointer, the storage position of the medical behavior in the storage position pointed to by the first pointer is cached in the preset cache storage space, and the target medical behavior is called from the storage position pointed to by the second pointer, and then the medical behavior in the cache storage space is stored in the stack queue again, so as to complete the calling of the target medical behavior in the stack queue based on the storage position.

[0087] In another embodiment of the present application, in order to further limit and illustrate, as shown in Figure 3 The step of processing the target medical behavior according to the monitoring strategy of the service link to obtain the monitoring result of the service link includes:

[0088] 301, analyzing the service type of the service link;

[0089] 302, determining the monitoring strategy corresponding to the service type based on the preset link monitoring mapping relationship;

[0090] 303, monitoring and processing the target medical behavior based on the monitoring strategy, and generating the monitoring result of the service link.

[0091] In order to meet the monitoring demand of medical service, when monitoring and processing the service link according to the monitoring strategy, specifically, first, the service type of the service link to be monitored is analyzed, at this time, the service type includes at least one of the medical project execution type, the medical product transaction type and the medical information processing type, and the embodiment of the present application does not make specific limitation. When the service type is determined, the corresponding monitoring strategy is determined based on the pre-configured link monitoring mapping relationship, wherein the link monitoring mapping relationship stores the required monitoring strategies of different service types, and the monitoring strategy includes at least one of the behavior violation monitoring, the time limit monitoring and the data authenticity monitoring. The specific monitoring strategy can be configured by technical personnel according to the monitoring demand, so as to monitor the service link according to the monitoring strategy, and the embodiment of the present application does not make specific limitation.

[0092] It should be noted that in the specific scenario of medical service, in the embodiment of the application, the execution of the medical service is started by tracking the service interface TraceSegmentServiceClient. At this time, the user driver ConsumeDriver is created through the data carrier DataCarrier, and the medical service execution is realized through the user driver. ConsumeDriver is a user interface, which first allocates a service queue QueueBuffer to a user thread, and then starts the user thread to collect data. A user thread ConsumerThread is created, at this time, a list is allocated to store the data of the current thread to be executed in the medical service, the data in QueueBuffer is put into the list, and the real data processing logic is executed. At this time, the service monitoring processing method is executed by calling TraceSegmentServiceClient. Finally, the server TraceSegment is converted into an open source protocol format GRPC (Remote Procedure Calls) to define the protocol data (traceId, traceSegmentId, spans, etc.), and the collected data is transmitted to the server data collection service SK Collector through the GRPC call to the remote interface, and the monitoring of the medical behavior of the medical data in the whole medical service is completed.

[0093] In another embodiment of the application, in order to further limit and illustrate, the step of monitoring and processing the target medical behavior based on the monitoring strategy to generate the monitoring result of the service link includes:

[0094] If it is determined that the target medical behavior is a violation operation based on the behavior violation monitoring, a violation monitoring result of the service link is generated, and the violation monitoring result is reported; or,

[0095] If it is determined that the target medical behavior is a timeout behavior based on the time limit monitoring, and / or the target medical behavior is a counterfeit behavior based on the data authenticity monitoring, an abnormal monitoring result of the service link is generated, and abnormal alarm information is sent to the medical client.

[0096] In the embodiment of the present application, in order to meet more effective monitoring effect, in a specific application scenario, if it is determined that the target medical behavior is a rule violation operation based on behavior violation monitoring, a rule violation monitoring result of the service link is generated, and the rule violation monitoring result is reported. If it is determined that the target medical behavior is a timeout behavior based on time limit monitoring, and / or it is determined that the target medical behavior is a fake behavior based on data authenticity monitoring, an abnormal monitoring result of the service link is generated, and abnormal alarm information is sent to the medical client. The judgment of behavior violation monitoring can be based on pre-written behavior whitelist for monitoring judgment, the judgment of time limit monitoring can be based on pre-configured time limit for monitoring judgment, and the judgment of data authenticity monitoring can be based on pre-configured data abnormality threshold for monitoring judgment, which is not limited in the embodiment of the present application.

[0097] The embodiment of the present application provides a service link monitoring method, compared with the prior art, the embodiment of the present application acquires the behavior tag of the medical data in response to the behavior monitoring instruction of the medical data, the behavior tag is used to represent the identification of the medical behavior in a complete service link to generate the medical data; determines the stack queue corresponding to the behavior tag and the queue index, and retrieves the target medical behavior corresponding to the medical data from the stack queue according to the queue index; processes the target medical behavior according to the monitoring strategy of the service link to obtain the monitoring result of the service link, the monitoring strategy is used to represent the rule of monitoring the target medical behavior by different service links, realizes parallel monitoring processing of multiple service links under cross-process service, increases monitoring speed, reduces monitoring time consumption of medical service, and greatly improves the monitoring efficiency of service link in medical service.

[0098] Further, as an implementation of the method shown in the above Figure 1 The embodiment of the present application provides a service link monitoring device, as shown in the above Figure 4 The device comprises:

[0099] The acquisition module 41 is used to acquire the behavior tag of the medical data in response to the behavior monitoring instruction of the medical data, and the behavior tag is used to represent the identification of the medical behavior in a complete service link to generate the medical data;

[0100] The determination module 42 is used to determine the stack queue corresponding to the behavior tag and the queue index, and retrieve the target medical behavior corresponding to the medical data from the stack queue according to the queue index;

[0101] The processing module 43 is used to process the target medical behavior according to the monitoring strategy of the service link to obtain the monitoring result of the service link, and the monitoring strategy is used to represent the rule of monitoring the target medical behavior by different service links.

[0102] Further, the apparatus further comprises:

[0103] a creating module, configured to create a tag block for tracking medical data in a service link based on an abstract class object, the service link comprising a plurality of associated medical behaviors;

[0104] a calling module, configured to call the tag block to mark the medical behavior when it is detected that the medical behavior generates the medical data, to obtain a behavior tag;

[0105] a generating module, configured to record a storage location of the medical behavior in a stack queue corresponding to the behavior tag, and generate a matching queue index, the stack queue being used to store storage locations of medical behaviors corresponding to all behavior tags obtained in a service link.

[0106] Further, the calling module is specifically configured to, if it is determined based on a thread executing an associated medical behavior that the service link is a non-unique link, mark the medical behavior based on the tag block to obtain a behavior tag comprising a unique service link identifier.

[0107] Further, the generating module is specifically configured to, when a created stack queue is not found according to a behavior type of the behavior tag, mark an initial stack queue generated with the behavior type, and store the storage location of the medical behavior in the initial stack queue; when a created stack queue is found according to the behavior type of the behavior tag, and the stack queue is not full, store the storage location of the medical behavior in the stack queue; and generate a queue index according to the storage location of the medical behavior stored in a storage location pointed to by a pointer in the stack queue, the behavior type, and the behavior tag.

[0108] Further, the determining module is specifically configured to, if it is determined based on the queue index that the target medical behavior corresponding to the behavior tag is stored in a storage location pointed to by a first pointer, extract the target medical behavior from the storage location; if it is determined based on the queue index that the target medical behavior corresponding to the behavior tag is stored in a storage location pointed to by a second pointer, cache a storage location of a medical behavior in the storage location pointed to by the first pointer in a preset cache storage space, and after the target medical behavior is called from the storage location pointed to by the second pointer, re-store the storage location of the medical behavior in the preset cache storage space in the stack queue; wherein the storage location pointed to by the first pointer is at a top of the stack queue.

[0109] Further, the processing module comprises:

[0110] The parsing unit is used to parse the service type of the service link, wherein the service type includes at least one of medical project execution type, medical product transaction type, and medical information processing type.

[0111] The determining unit is used to determine the monitoring strategy corresponding to the service type based on a preset link monitoring mapping relationship. The link monitoring mapping relationship stores the monitoring strategies required for different service types. The monitoring strategy includes at least one of behavior violation monitoring, timeliness monitoring, and data authenticity monitoring.

[0112] The generation unit is used to monitor and process the target medical behavior based on the monitoring strategy and generate the monitoring results of the service link.

[0113] This invention provides a service link monitoring device. Compared with the prior art, this invention, in response to a behavior monitoring instruction for medical data, obtains the behavior tag of the medical data. The behavior tag is used to characterize the identifier that generates the medical data by performing a medical behavior in a complete service link. It determines the stack queue and queue index corresponding to the behavior tag, and retrieves the target medical behavior corresponding to the medical data from the stack queue according to the queue index. It then processes the target medical behavior according to the service link monitoring strategy to obtain the monitoring result of the service link. The monitoring strategy characterizes the rules for different service links to monitor the target medical behavior, realizing parallel monitoring processing of multiple service links under cross-process services, increasing monitoring speed, reducing the monitoring time of medical services, and thus greatly improving the monitoring efficiency of service links in medical services.

[0114] According to one embodiment of the present invention, a storage medium is provided, the storage medium storing at least one executable instruction, the computer-executable instruction being capable of executing the service link monitoring method in any of the above method embodiments.

[0115] Figure 5 The diagram illustrates a structural schematic of a computer device according to an embodiment of the present invention. The specific embodiments of the present invention do not limit the specific implementation of the computer device.

[0116] like Figure 5 As shown, the computer device may include: a processor 502, a communications interface 504, a memory 506, and a communications bus 508.

[0117] The processor 502, communication interface 504, and memory 506 communicate with each other via communication bus 508.

[0118] The communication interface 504 is configured to communicate with network elements such as clients or other servers.

[0119] The processor 502 is configured to execute the program 510, and in particular, execute the related steps in the embodiments of the method for monitoring a service link.

[0120] In particular, the program 510 can include program codes including computer operation instructions.

[0121] The processor 502 can be a central processing unit (CPU), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the computer device can be processors of the same type, such as one or more CPUs, or processors of different types, such as one or more CPUs and one or more ASICs.

[0122] The memory 506 is configured to store the program 510. The memory 506 can include a high-speed RAM memory, and can also include a non-volatile memory such as at least one disk memory.

[0123] The program 510 can be specifically configured to cause the processor 502 to perform the following operations:

[0124] In response to the behavior monitoring instruction of the medical data, obtain a behavior label of the medical data, the behavior label being used to represent an identity of a medical behavior performed in a complete service link to generate the medical data;

[0125] Determine a stack queue corresponding to the behavior label and a queue index, and according to the queue index, call a target medical behavior corresponding to the medical data from the stack queue;

[0126] According to a monitoring policy of the service link, process the target medical behavior to obtain a monitoring result of the service link, the monitoring policy being used to represent a rule of monitoring the target medical behavior by different service links.

[0127] It should be apparent to those skilled in the art that the modules or steps of the application described above can be implemented with a general purpose computing device, which can be centralized on a single computing device or distributed over a network of multiple computing devices, and optionally implemented with program code executable by a computing device, which can be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described can be performed in a different order than shown, or made into individual integrated circuit modules, or multiple modules or steps made into a single integrated circuit module. Thus, the application is not limited to any particular combination of hardware and software.

[0128] The preferred embodiments of the application described above are intended to be merely exemplary and those skilled in the art will recognize that changes can be made to the above-described embodiments without departing from the spirit and scope of the application. What is desired to be protected by letters patent is set forth in the appended claims.

Claims

1. A method for monitoring a service link, characterized in that, include: In response to a behavior monitoring instruction for medical data, the behavior tag of the medical data is obtained. The behavior tag is used to characterize the identifier that generates the medical data by performing medical behavior in a complete service link. The behavior tag includes a main tag and a corresponding secondary tag. The main tag is used to characterize the medical service corresponding to a service link, and the secondary tag is used to characterize the behavior corresponding to each piece of medical data under the service link. Determine the stack queue and queue index corresponding to the behavior label, and retrieve the target medical behavior corresponding to the medical data from the stack queue according to the queue index; The target medical behavior is processed according to the monitoring strategy of the service link to obtain the monitoring result of the service link. The monitoring strategy is used to characterize the rules for different service links to monitor the target medical behavior. Before acquiring the behavioral tags of the medical data, the method further includes: A tag block is created based on an abstract class object to track medical data in a service chain containing multiple associated medical actions; When the medical data is generated by performing the medical action, the tag block is retrieved to mark the medical action, thus obtaining an action tag; The storage location of the medical behavior is recorded in the stack queue corresponding to the behavior tag, and a matching queue index is generated. The stack queue is used to store the storage location of all medical behaviors corresponding to all behavior tags obtained in a service link.

2. The method according to claim 1, characterized in that, The step of retrieving the tag block to mark the medical behavior and obtaining behavior tags includes: If the service link is determined to be a non-unique link based on the thread executing the associated medical behavior, then the medical behavior is marked with a unique service link identifier based on the tag block to obtain a behavior tag containing the unique service link identifier.

3. The method according to claim 1, characterized in that, The step of recording the storage location of the medical action in the stack queue corresponding to the action tag includes: If no created stack queue is found based on the behavior type of the behavior tag, the behavior type is marked on the generated initial stack queue, and the storage location of the medical behavior is stored in the initial stack queue. When a created stack queue is found based on the behavior type of the behavior tag, and the stack queue is not full, the storage location of the medical behavior is stored in the stack queue. The queue index for generating the match includes: A queue index is generated based on the storage location pointed to by the pointer in the stack queue where the medical behavior is stored, as well as the behavior type and the behavior label.

4. The method according to claim 3, characterized in that, The step of retrieving the target medical action corresponding to the medical data from the stack queue according to the queue index includes: If the target medical behavior corresponding to the behavior label is determined to be stored in the storage location pointed to by the first pointer based on the queue index, then the target medical behavior is extracted from the storage location; If the target medical behavior corresponding to the behavior label is determined to be stored in the storage location pointed to by the second pointer based on the queue index, then the storage location of the medical behavior in the storage location pointed to by the first pointer is cached in the preset cache storage space, and after retrieving the target medical behavior from the storage location pointed to by the second pointer, the storage location of the medical behavior in the preset cache storage space is restored to the stack queue. The storage location pointed to by the first pointer is at the top of the stack queue.

5. The method according to claim 1, characterized in that, The process of processing the target medical behavior according to the monitoring strategy of the service link to obtain the monitoring results of the service link includes: The service type of the service link is analyzed, and the service type includes at least one of the following: medical project execution type, medical product transaction type, and medical information processing type. The monitoring strategy corresponding to the service type is determined based on the preset link monitoring mapping relationship. The link monitoring mapping relationship stores the monitoring strategies required for different service types. The monitoring strategy includes at least one of behavior violation monitoring, timeliness monitoring, and data authenticity monitoring. Based on the monitoring strategy, the target medical behavior is monitored and processed to generate the monitoring results of the service link.

6. The method according to claim 5, characterized in that, The monitoring and processing of the target medical behavior based on the monitoring strategy, and the generation of the monitoring results for the service link, include: If the target medical behavior is determined to be a violation based on the aforementioned violation monitoring, then a violation monitoring result for the service link is generated and reported; or, If the timeliness monitoring determines that the target medical behavior is a timeout behavior, and / or the data authenticity monitoring determines that the target medical behavior is a forged behavior, then an abnormal monitoring result of the service link is generated, and an abnormal alarm message is sent to the medical client.

7. A monitoring device for a service link, characterized in that, include: The acquisition module is used to acquire the behavior tags of the medical data in response to the behavior monitoring command of the medical data. The behavior tags are used to characterize the identifier of the medical data generated by the execution of medical behavior in a complete service link. The behavior tags include a main tag and a corresponding auxiliary tag. The main tag is used to characterize the medical service corresponding to a service link, and the auxiliary tag is used to characterize the behavior corresponding to each piece of medical data under the service link. The determination module is used to determine the stack queue and queue index corresponding to the behavior label, and retrieve the target medical behavior corresponding to the medical data from the stack queue according to the queue index; The processing module is used to process the target medical behavior according to the monitoring strategy of the service link to obtain the monitoring result of the service link. The monitoring strategy is used to characterize the rules for different service links to monitor the target medical behavior. The device further includes: A module is created to generate tag blocks based on abstract class objects for tracking medical data in a service chain containing multiple associated medical actions; The retrieval module is used to retrieve the tag block to mark the medical behavior and obtain behavior tags when it is detected that the medical data is generated by performing the medical behavior. The generation module is used to record the storage location of the medical behavior in the stack queue corresponding to the behavior tag, and generate a matching queue index. The stack queue is used to store the storage location of all medical behaviors corresponding to all behavior tags obtained in a service link.

8. A storage medium storing at least one executable instruction that causes a processor to perform an operation corresponding to the service link monitoring method as described in any one of claims 1-6.

9. A computer device, comprising: The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus. The memory is used to store at least one executable instruction, which causes the processor to perform the operation corresponding to the service link monitoring method as described in any one of claims 1-6.

Images