Service system correction method and device, computer equipment and storage medium

Abstract

The embodiment of the invention belongs to the field of digital medical treatment, and relates to a service system correction method and device, computer equipment and a storage medium, and the method comprises the following steps: obtaining exit request information; querying corresponding medical service node request information according to the exit request information; acquiring a corresponding medical service node state according to the medical service node request information; checking whether the state of the medical service node is a safe state or not; and if the state of the medical service node is not the safe state, determining a corresponding medical service node according to the state of the medical service node, calling a corresponding node correction scheme according to the medical service node, and correcting the medical service node based on the node correction scheme. And obtaining the corrected medical service node state again for checking until the corrected medical service node state is the safe state. According to the invention, the accuracy and efficiency of node correction in the medical service system can be effectively improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, specifically to the field of digital medicine, and in particular to a service system correction method, device, computer equipment and storage medium. Background Art

[0002] In the modern medical service system, with the continuous improvement of the degree of medical informatization, various medical service systems are composed of multiple medical service nodes, forming a complex and huge service network. While promoting efficient and accurate medical services, these nodes also face challenges caused by their large number and frequent interactions. In particular, due to the large number and wide distribution of medical service nodes, abnormal situations are prone to occur during data processing, transmission and storage between different nodes, such as system crashes, data loss, network delays, etc. These abnormalities directly affect the continuity and quality of medical services.

[0003] Whenever a node anomaly occurs, traditional practices often rely on manual verification mechanisms, which requires professional technicians to check each node one by one to locate and confirm the source of the anomaly. This process is not only time-consuming and labor-intensive, but also highly dependent on the experience and ability of the operator, which can easily lead to low diagnostic efficiency and increased risk of misdiagnosis. In addition, manual verification is often difficult to respond in real time, especially in emergency medical scenarios, where any delay may have an immeasurable impact on the patient's health. Therefore, this inefficient exception handling method seriously restricts the normal operation of the medical service system and the improvement of medical service quality. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a service system correction method, apparatus, computer equipment and storage medium to solve the problem of being unable to accurately and quickly correct service nodes in a medical service system.

[0005] In order to solve the above technical problems, the embodiment of the present application provides a service system correction method, which adopts the following technical solution:

[0006] Get export request information;

[0007] Querying corresponding medical service node request information according to the export request information;

[0008] Obtain the corresponding medical service node status according to the medical service node request information;

[0009] Check whether the medical service node is in a safe state;

[0010] If the medical service node status is not the safe status, the corresponding medical service node is determined according to the medical service node status, and the corresponding node correction plan is called according to the medical service node. The medical service node is corrected based on the node correction plan, and the corrected medical service node status is re-obtained for inspection until the corrected medical service node status is the safe status.

[0011] Furthermore, before the step of obtaining the export request information, the following steps are also included:

[0012] Get access request information;

[0013] generating an access request field according to the access request information;

[0014] Obtain the node request information corresponding to the medical service node, and use the access request field as the primary key and the node request information as the value to generate a key-value pair, save the key-value pair into a predetermined information memory, and obtain the medical service node request information.

[0015] Furthermore, the step of obtaining the export request information specifically includes:

[0016] Real-time detection of whether the preset traffic outlet has received the export request;

[0017] If the preset traffic outlet receives the export request, the export request is intercepted, and the intercepted export request is sent to the preset filter for processing to obtain the export request information.

[0018] Furthermore, the step of intercepting the egress request and sending the intercepted egress request to a preset filter for processing specifically includes:

[0019] Obtaining a list of egress request events for the preset traffic egress;

[0020] Obtain a current timestamp, and search for a current egress event in the egress request event list according to the current timestamp;

[0021] Calling a preset service agent to intercept the export request according to the current export event;

[0022] Determining the preset filter according to the preset service agent;

[0023] Based on the preset service proxy, the intercepted egress request is forwarded to the preset filter for processing.

[0024] Further, the step of querying the corresponding medical service node request information according to the export request information specifically includes:

[0025] Extracting a corresponding export request information identifier from the export request information;

[0026] Acquire a corresponding export request information list from a database according to the export request information identifier;

[0027] Obtain a list of medical service nodes, search the export request list according to the list of medical service nodes, and obtain the medical service node request information.

[0028] Furthermore, the step of obtaining the corresponding medical service node status according to the medical service node request information specifically includes:

[0029] Accessing a corresponding medical service node according to the medical service node request information;

[0030] Obtaining a node status table corresponding to the medical service node;

[0031] Acquire preset extraction time information, extract corresponding node status information from the node status table according to the extraction time information, and use the extracted node status information as the medical service node status.

[0032] Furthermore, before the step of calling the corresponding node correction scheme according to the medical service node and correcting the medical service node based on the node correction scheme, the following steps are also included:

[0033] Get historical status information of medical service nodes;

[0034] Determine the error problem of the medical service node according to the historical status information of the medical service node;

[0035] Extracting corresponding solutions from a pre-built service knowledge base according to the medical service node error problem;

[0036] Conduct simulation tests on the solution to obtain simulation results;

[0037] Determine whether the simulation result of the solution meets the preset successful solution conditions;

[0038] If the solution simulation result meets the preset solution success condition, the solution is saved as the node correction solution.

[0039] In order to solve the above technical problems, the embodiment of the present application further provides a service system correction device, which adopts the following technical solution:

[0040] An information acquisition module, used for acquiring export request information;

[0041] An information query module, used to query corresponding medical service node request information according to the export request information;

[0042] A status acquisition module, used to acquire the corresponding medical service node status according to the medical service node request information;

[0043] A status verification module, used to verify whether the status of the medical service node is a safe status;

[0044] A node correction module is used to determine the corresponding medical service node according to the medical service node status if the medical service node status is not the safe status, and call the corresponding node correction plan according to the medical service node, correct the medical service node based on the node correction plan, and re-acquire the corrected medical service node status for inspection until the corrected medical service node status is the safe status.

[0045] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution:

[0046] A computer device comprises a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of any one of the above service system correction methods when executing the computer-readable instructions.

[0047] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:

[0048] A computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the steps of the service system correction method as described in any one of the above items are implemented.

[0049] Compared with the prior art, the embodiment of the present application has the following beneficial effects: the embodiment obtains the export request information; queries the corresponding medical service node request information according to the export request information; obtains the corresponding medical service node status according to the medical service node request information; verifies whether the medical service node status is in a safe state; if the medical service node status is not in the safe state, determines the corresponding medical service node according to the medical service node status, and calls the corresponding node correction scheme according to the medical service node, corrects the medical service node based on the node correction scheme, re-obtains the corrected medical service node status for verification, until the corrected medical service node status is in the safe state. Thus, the service nodes in the medical service system are effectively detected and corrected to ensure the normal operation of the medical service system. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the scheme in the present application, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0051] Figure 1 is an exemplary system architecture diagram to which the present application may be applied;

[0052] Figure 2 A flowchart of an embodiment of a service system correction method according to the present application;

[0053] Figure 3 yes Figure 2 A flowchart of a specific implementation of step S10;

[0054] Figure 4 yes Figure 3 A flowchart of a specific implementation of step S102;

[0055] Figure 5 yes Figure 2 A flowchart of a specific implementation of step S20;

[0056] Figure 6 yes Figure 2 A flowchart of a specific implementation of step S30;

[0057] Figure 7 is a structural diagram of an embodiment of a service system correction device according to the present application;

[0058] Figure 8 It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION

[0059] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by technicians in the technical field of the present application; the terms used in the specification of the application herein are only for the purpose of describing specific embodiments and are not intended to limit the present application; the terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of the present application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0060] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor does it refer to non-related or alternative embodiments that are mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0061] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0062] like Figure 1 As shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0063] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0064] Terminal devices 101, 102, 103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III), MP4 (Moving Picture Experts Group Audio Layer IV) players, laptop computers, desktop computers, etc.

[0065] The server 105 may be a server that provides various services, such as a background server that provides support for web pages displayed on the terminal devices 101 , 102 , and 103 .

[0066] It should be noted that the service system correction method provided in the embodiment of the present application is generally executed by a server, and accordingly, the service system correction device is generally set in the server.

[0067] It should be understood that Figure 1The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0068] Continue to refer Figure 2 , shows a flow chart of an embodiment of the image recognition method according to the present application. The service system correction method comprises the following steps:

[0069] Step S10, obtaining export request information;

[0070] In this embodiment, the export request information refers to the request information of the traffic received by the traffic export of the medical service system and returned to the external data terminal. The traffic export is the data export point of the medical service system, that is, the place where the medical service system sends data to the outside. The export request information corresponds to the export traffic data, and the export traffic data corresponds to the data or operation results required by the access request information.

[0071] Step S20, querying corresponding medical service node request information according to the export request information;

[0072] In this embodiment, the medical service node request information refers to the request header corresponding to the medical service node. The request header is a request identifier that uniquely identifies the medical service node in the distributed system. The request identifier corresponds to the medical service node and is used to locate the medical service node to access it, thereby obtaining the status information corresponding to the medical service node.

[0073] Step S30, obtaining the corresponding medical service node status according to the medical service node request information;

[0074] In this embodiment, the medical service node status is the node status corresponding to the medical service node, and the node status is the health status corresponding to the medical service node. The health status refers to the medical service node encountering errors or abnormalities during business processing. The health status includes normal operation and abnormal operation. Normal operation means that the medical service node is working normally, without encountering any errors or abnormalities, and can process incoming requests and return correct responses; abnormal operation means that the medical service node encounters an error when processing a request, resulting in the inability to correctly process the request, or the medical service node may still be running, but some services or functions are temporarily unavailable for some reason, or the medical service node is completely unable to process any requests due to serious errors, crashes or network problems.

[0075] Step S40, checking whether the medical service node is in a safe state;

[0076] In this embodiment, the security status corresponds to the normal operating status of the above-mentioned medical service node, which means that the medical service node is in a normal operating state and no errors, intrusions or risks occur within a certain period of time. The certain time period can be set and adjusted according to actual conditions. In this embodiment, the time period corresponding to the security status is 1 hour.

[0077] Step S50, if the state of the medical service node is the safe state, returning the flow data corresponding to the export request information to the external data terminal;

[0078] In this embodiment, the traffic data corresponding to the export request information refers to the response data after the request is processed by the corresponding medical service node. The response data includes the data pointed to by the export request information, which may specifically include: medical records, patient medical records, patient insurance information, medical equipment information, medical knowledge data, etc. The external data end refers to the entity end that sends a request to the medical service node and waits for the medical service node to respond and return data, including other medical institutions, third-party service providers, patients or user devices, regulatory agencies, etc.

[0079] Step S60: If the medical service node status is not the safe status, determine the corresponding medical service node according to the medical service node status, call the corresponding node correction plan according to the medical service node, correct the medical service node based on the node correction plan, and re-obtain the corrected medical service node status for inspection until the corrected medical service node status is the safe status.

[0080] In this embodiment, the node correction scheme is a correction scheme pre-set for the corresponding medical service node. The node correction scheme is stored in a database and can be searched and extracted from the database according to the node identification information of the medical service node.

[0081] In this embodiment, the above method can be applied to the patient medical treatment procedure of the medical service system. In the patient medical treatment procedure, through online operations, the service node jumps step by step, and finally completes the medical treatment and payment. The above medical service nodes are set in the medical service system. Specifically, in this embodiment, the medical service nodes may include an appointment registration node: providing online or offline appointment registration services to facilitate patients to arrange medical treatment time in advance; a consultation node: providing patients with medical guidance, department distribution, doctor information and other consulting services; a waiting queue node: managing the patient waiting order and reducing the patient's waiting time; a diagnosis and treatment service node: doctors communicate with patients face to face, diagnose the disease, prescribe, etc.; an inspection and testing node: patients undergo various inspections or tests according to the doctor's requirements to obtain more diagnostic information; a treatment and rehabilitation node: based on the diagnosis results, the doctor formulates a treatment plan, and the patient undergoes corresponding treatment or rehabilitation training; a drug collection and payment node: patients collect drugs with prescriptions and pay medical expenses.

[0082] This embodiment obtains the export request information; queries the corresponding medical service node request information according to the export request information; obtains the corresponding medical service node status according to the medical service node request information; verifies whether the medical service node status is a safe state; if the medical service node status is the safe state, returns the flow data corresponding to the export request information to the external data terminal; if the medical service node status is not the safe state, determines the corresponding medical service node according to the medical service node status, calls the corresponding node correction scheme according to the medical service node, corrects the medical service node based on the node correction scheme, re-obtains the corrected medical service node status for verification, until the corrected medical service node status is the safe state. Thus, the service nodes in the medical service system are effectively detected and corrected to ensure the normal operation of the medical service system.

[0083] In some optional implementations of this embodiment, before step S10, the following steps are further included:

[0084] Get access request information;

[0085] In this embodiment, the access request information is an access request initiated by an external data terminal to a medical service node. The access request points to one or more medical service nodes and is used to call the business corresponding to the medical service node. When the external data terminal initiates an access request to a medical service node in the medical service system, the service agent (such as Envoy) intercepts the access request and forwards it to a preset filter (such as External Filter) for processing, thereby obtaining the access request information.

[0086] generating an access request field according to the access request information;

[0087] In this embodiment, the access request field is an identification field generated by the service agent according to the access request information. The identification field corresponds to the access request information and is a unique identifier corresponding to a single access request information.

[0088] Obtain the node request information corresponding to the medical service node, and use the access request field as the primary key and the node request information as the value to generate a key-value pair, save the key-value pair into a predetermined information memory, and obtain the medical service node request information.

[0089] In this embodiment, the predetermined information list is a dictionary in the system memory, in which each key is a unique access request field and each value is a node request information. The dictionary storing the key-value pairs of access request fields and node request information is used as medical service node request information.

[0090] This embodiment obtains access request information; generates an access request field according to the access request information; obtains node request information corresponding to the medical service node, and generates a key-value pair with the access request field as the primary key and the node request information as the value, and saves the key-value pair into a predetermined information memory, thereby effectively obtaining the medical service node request information to facilitate subsequent query and acquisition based on the export request information.

[0091] Continue to refer Figure 3 In some optional implementations of this embodiment, step S10 includes the following steps:

[0092] Step S101, real-time detection of whether a preset traffic outlet receives an outlet request;

[0093] In this embodiment, the export request refers to a request generated by the medical service node to send a return data request to the external data terminal. The preset traffic export refers to the key points defined in the network architecture. These key points are responsible for processing or forwarding data flows related to each service node. Specifically, it may include the traffic export of the appointment registration node: including a Web server or API interface that processes patient appointment requests. When a patient submits an appointment request through an online platform (such as a hospital official website, a mobile application), the data will be sent to the backend system through these exports for processing, including checking the doctor's schedule, available number sources, etc., and returning the appointment result; the traffic export of the guidance and consultation node: involves interaction with a chat robot, online customer service or a self-service inquiry system. The traffic export here can be a server or API that processes these interaction requests. They are responsible for receiving patients' questions, querying databases (such as department information, doctor's schedule, etc.), and returning corresponding answers or guidance; the traffic export of the waiting queue node: including a server or message queue system responsible for updating the waiting queue status and sending waiting notifications (such as text messages, APP push). These exits ensure that patients can understand their waiting status in a timely manner and reduce unnecessary waiting; traffic exit of diagnosis and treatment service node: during the diagnosis and treatment process, it may be necessary to access the patient's electronic medical records. These medical record data are transmitted through the hospital's internal network or cloud storage service, and the relevant server or API interface can be regarded as the traffic exit; traffic exit of inspection and testing node: including servers that handle inspection applications and result inquiries, interfaces that communicate with inspection equipment, and middleware or services that may be used for data transmission; traffic exit of treatment and rehabilitation node: the treatment and rehabilitation process may involve the formulation of treatment plans, tracking of treatment progress, and execution of rehabilitation plans. These operations may need to be completed through specific software systems, and the data exchange between these systems and other systems (such as electronic medical record systems, payment systems, etc.) constitutes the traffic exit; traffic exit of medication and payment node: including payment gateways that process payment requests, interfaces that communicate with pharmacy systems (used to send prescription information, receive medication confirmation, etc.), and servers or message queue systems that may be used to send payment success notifications.

[0094] Step S102: if the preset traffic outlet receives the export request, the export request is intercepted, and the intercepted export request is sent to a preset filter for processing to obtain the export request information;

[0095] In this embodiment, the service proxy (such as Envoy) intercepts the egress request and forwards it to a preset filter (such as External Filter) for processing, thereby obtaining the egress request information. The above steps specifically include configuring the service proxy (Envoy): defining interception rules, in the Envoy configuration file, defining the matching rules for the egress requests that need to be intercepted, these rules can be set based on the URL of the request, header information, HTTP method and other conditions; setting the filter chain, configuring the filter chain in Envoy, specifying which filters will be applied to the intercepted requests; enabling the HTTP connection manager, ensuring that the HTTP connection manager of Envoy is enabled and correctly configured to handle HTTP / HTTPS traffic. Configure external filters: Determine the filter location, determine the deployment location of the external filter, which is usually an independent server or service that can receive requests from Envoy; define the processing logic, define the logic for processing intercepted requests in the external filter, including logging, authentication, request modification, security checks and other operations; set the communication protocol, and ensure that the communication protocol between Envoy and the external filter (such as HTTP / HTTPS, gRPC, etc.) is correctly configured so that they can communicate with each other. Interception, forwarding and processing: When Envoy receives an egress request that meets the interception rules, it will intercept the request according to the configuration; request forwarding, the intercepted request is then forwarded to the preset external filter for processing, usually implemented through the filter chain in Envoy, one of which is responsible for sending the request to the external filter; process the request, after the external filter receives the request, it processes it according to the predefined logic. After the processing is completed, the external filter returns the processing result to Envoy to obtain the egress request information.

[0096] Step S103, if the preset flow outlet does not receive the outlet request, detection is performed again after a preset time interval until the preset flow outlet receives the outlet request, or the preset flow outlet receives a stop detection command.

[0097] In this embodiment, the preset time interval is 1 second, which can be set and adjusted accordingly according to actual conditions to obtain better detection effect.

[0098] This embodiment detects in real time whether the preset flow outlet receives the export request; if the preset flow outlet receives the export request, the export request is intercepted, and the intercepted export request is sent to the preset filter for processing to obtain the export request information; if the preset flow outlet does not receive the export request, the detection is performed again after a preset time interval until the preset flow outlet receives the export request, or the preset flow outlet receives a stop detection command. This effectively realizes the acquisition of export request information, so as to facilitate the subsequent query and processing of medical service node request information.

[0099] Continue to refer Figure 4 In some optional implementations of this embodiment, step S102 includes the following steps:

[0100] Step S1021, obtaining the egress request event list of the preset traffic egress;

[0101] In this embodiment, the egress request event list includes egress request events that occurred in the preset traffic egress history, and each event contains sufficient information to identify it (such as event ID, timestamp, request details, etc.).

[0102] Step S1022, obtaining a current timestamp, and searching for a current egress event in the egress request event list according to the current timestamp;

[0103] In this embodiment, the current timestamp can be obtained by the medical service system calling a system time function or using a network time protocol (NTP) service.

[0104] Step S1023, calling a preset service agent according to the current egress event to intercept the egress request;

[0105] In this embodiment, the current timestamp is used as a reference to search the export request event list for the export event that best matches the current timestamp. The export request event list can be traversed and the timestamp of each event can be compared to the closeness of the current timestamp to perform the matching. When the current export event is obtained, the medical service system will call the preset service agent (such as Envoy) according to the event to intercept the export request to be issued. Step S1024, determine the preset filter according to the preset service agent;

[0106] In this embodiment, after the service proxy intercepts the egress request, the corresponding filter can be determined by checking the header information, URL path, request body content, etc. of the request.

[0107] Step S1025: forwarding the intercepted egress request to the preset filter for processing based on the preset service proxy.

[0108] In this embodiment, the preset service agent executes the step of forwarding the intercepted egress request to the preset filter for processing according to its preset logic, and the above preset logic corresponds to the above step of configuring the service agent.

[0109] This embodiment obtains the preset export request event list of the traffic export; obtains the current timestamp, searches for the current export event in the export request event list according to the current timestamp; calls the preset service agent to intercept the export request according to the current export event; determines the preset filter according to the preset service agent; and forwards the intercepted export request to the preset filter for processing based on the preset service agent. This effectively implements the interception and processing according to the export request to obtain the corresponding export request information.

[0110] Continue to refer Figure 5 In some optional implementations of this embodiment, step S20 includes the following steps:

[0111] Step S201, extracting a corresponding export request information identifier from the export request information;

[0112] In this embodiment, the export request information includes an export request information identifier, and the export request information identifier is a unique identifier corresponding to the export request information.

[0113] Step S202, acquiring a corresponding export request information list from a database according to the export request information identifier;

[0114] In this embodiment, the export request information list is an information list containing multiple medical service node request information. The extracted export request information identifier is used as a query condition to retrieve the corresponding export request information list in the database, and the retrieved export request information list is extracted to obtain the export request information list.

[0115] Step S203, obtaining a list of medical service nodes, searching in the export request list according to the list of medical service nodes, and obtaining the medical service node request information.

[0116] In this embodiment, the medical service node list is a list of all medical service nodes in the medical service system, and the node identifier of the medical service node is used to search in the export request list to obtain the corresponding medical service node request information. In this embodiment, the medical service node request information is the tracking request header corresponding to the medical service node, and the medical service node can be accessed and information can be obtained through the medical service node request information.

[0117] This embodiment extracts the corresponding export request information identifier from the export request information; obtains the corresponding export request information list from the database according to the export request information identifier; obtains the medical service node list, and searches the export request list according to the medical service node list, thereby effectively obtaining the medical service node request information corresponding to the export request information, so as to facilitate the subsequent acquisition of the corresponding medical service node status according to the medical service node request information.

[0118] Continue to refer Figure 6 In some optional implementations of this embodiment, step 30 includes the following steps:

[0119] Step S301, accessing a corresponding medical service node according to the medical service node request information;

[0120] In this embodiment, the medical service node request information is a tracking request header pointing to the medical service node. A communication connection with the medical service node can be established through the information provided by the medical service node request information (such as URL, port, API key, etc.), thereby achieving access to the medical service node.

[0121] Step S302, obtaining a node status table corresponding to the medical service node;

[0122] In this embodiment, the node status table is a snapshot of the node event table corresponding to the medical service node, and the node status corresponding to the current medical service node is determined through the snapshot of the node event table.

[0123] Step S303, obtaining preset extraction time information, extracting corresponding node status information from the node status table according to the extraction time information, and using the extracted node status information as the medical service node status.

[0124] In this embodiment, the preset extraction time information refers to a preset extraction time period, which is from the current time to ten minutes before the current time. The node status table records the node processing events corresponding to the medical service node. The node processing events within the time period are extracted through the preset extraction time period, and the processing status corresponding to the node processing event is used as the medical service node status. The above preset extraction time period can be set and adjusted according to actual conditions.

[0125] This embodiment accesses the corresponding medical service node according to the medical service node request information; obtains the node status table corresponding to the medical service node; obtains the preset extraction time information, extracts the corresponding node status information from the node status table according to the extraction time information, and uses the extracted node status information as the medical service node status. This effectively achieves the acquisition of the corresponding medical service node status according to the medical service node request information, so as to facilitate the subsequent security inspection and processing according to the medical service node status.

[0126] In some optional implementations of this embodiment, before step S60, the following steps are further included:

[0127] Get historical status information of medical service nodes;

[0128] In this embodiment, the historical status information of the medical service node is a record of the node status at different time points in the history of the medical service node, and the historical information record or log of the medical service node can be extracted from a database.

[0129] Determine the error problem of the medical service node according to the historical status information of the medical service node;

[0130] In this embodiment, based on the historical status information of the medical service node, a data analysis method (such as statistical analysis, trend prediction, pattern recognition, etc.) is used to identify possible error problems of the service node.

[0131] Extracting corresponding solutions from a pre-built service knowledge base according to the medical service node error problem;

[0132] In this embodiment, the pre-built service knowledge base is a system that integrates a large amount of information and knowledge to support the rapid identification, diagnosis and resolution of error problems in medical service nodes. The pre-built service knowledge base includes: Problem description and classification: Detailed record of the specific manifestations of each known problem, including error messages, abnormal symptoms, user feedback, etc.; classify problems according to type, scope of impact, severity and other dimensions for quick retrieval. Solutions and steps: For each problem, provide detailed solution steps, configuration adjustments, code fixes or workflow changes, etc.; solution prerequisites, required resources, expected impact, safety precautions, etc. Related knowledge documents: product manuals, API documents, system architecture diagrams, configuration guides, etc., to provide technical support for problem solving; previous cases of handling similar problems, including problem descriptions, solution processes, lessons learned, etc.

[0133] Conduct simulation tests on the solution to obtain simulation results;

[0134] In this embodiment, the simulation test includes the following steps: building a simulation environment, which should be as close to the actual environment as possible to accurately test the effect of the solution; implementing the extracted solution in the simulation environment to ensure that all necessary steps are executed; recording all outputs and results during the simulation test, including performance indicators, error logs, etc.

[0135] Determine whether the simulation result of the solution meets the preset successful solution conditions;

[0136] In this embodiment, the preset successful solution condition is that no abnormality or error occurs within ten minutes after the abnormal medical service node is corrected with the solution. The preset successful solution condition can be set and adjusted according to actual conditions.

[0137] If the solution simulation result meets the preset successful solution condition, the solution is saved as the node correction solution;

[0138] If the solution simulation result does not meet the preset solution success condition, the solution is adjusted until the solution simulation result of the adjusted solution meets the preset solution success condition.

[0139] In this embodiment, adjusting the solution includes the following steps: Analyze simulation results: Review the results of the simulation test, including performance indicators, error logs, system behavior, etc., to determine the problem; Compare the simulation results with the preset success conditions to find out the differences and non-compliance items. Identify the root cause of the problem: Based on the analysis of the simulation results, further explore the root cause of the problem, which may require consulting technical documents, consulting experts or conducting additional tests; clarify which part of the solution the problem lies in, whether it is caused by configuration errors, code defects, resource limitations or other factors. Design adjustment plans: According to the root cause of the problem, design adjustment plans, including modifying configuration parameters, optimizing code logic, increasing resource allocation, changing workflows, etc.; Consider multiple possible adjustment plans and evaluate the feasibility, risks and expected effects of each plan. Implement adjustments: Make corresponding modifications to the solution in the simulation environment. Ensure that the modified plan can cover the root cause of the problem and reduce the impact on other parts; After the modification, re-test in the simulation environment to verify whether the adjustment is effective. Evaluate results: Compare the retested solution simulation results with the preset solution success conditions to evaluate whether the adjustments have achieved the expected results; if the solution simulation results still do not meet the success conditions, repeat the above steps (starting from analyzing the simulation results) to make iterative adjustments.

[0140] This embodiment obtains the historical status information of the medical service node; determines the error problem of the medical service node according to the historical status information of the medical service node; extracts the corresponding solution from the pre-built service knowledge base according to the error problem of the medical service node; simulates and tests the solution to obtain the solution simulation result; determines whether the solution simulation result meets the preset solution success condition; if the solution simulation result meets the preset solution success condition, the solution is saved as the node correction solution; if the solution simulation result does not meet the preset solution success condition, the solution is adjusted until the solution simulation result of the adjusted solution meets the preset solution success condition. In this way, a node correction solution corresponding to the error state of the medical service node is effectively generated to facilitate subsequent correction processing according to the node correction solution.

[0141] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0142] It should be understood that, although the steps in the flowchart of the accompanying drawings are displayed in sequence as indicated by the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least a part of the steps in the flowchart of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.

[0143] Further references Figure 7 , as a response to the above Figure 1 The present application provides an embodiment of a service system correction device, and the device embodiment is similar to Figure 1 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0144] like Figure 7 As shown, the service system correction device 700 described in this embodiment includes: an information acquisition module 701, an information query module 702, a state acquisition module 703, a state inspection module 704, a flow output module 705, and a node correction module 706. Among them:

[0145] Information acquisition module 701, used to acquire export request information;

[0146] An information query module 702 is used to query corresponding medical service node request information according to the export request information;

[0147] The status acquisition module 703 is used to acquire the corresponding medical service node status according to the medical service node request information;

[0148] A status checking module 704 is used to check whether the medical service node status is a safe status;

[0149] The flow output module 705 is used to return the flow data corresponding to the export request information to the external data terminal if the state of the medical service node is the safe state;

[0150] The node correction module 706 is used to determine the corresponding medical service node according to the medical service node status if the medical service node status is not the safe status, and call the corresponding node correction plan according to the medical service node, correct the medical service node based on the node correction plan, and re-obtain the corrected medical service node status for inspection until the corrected medical service node status is the safe status.

[0151] By adopting the above-mentioned device, this embodiment can obtain the export request information; query the corresponding medical service node request information according to the export request information; obtain the corresponding medical service node status according to the medical service node request information; check whether the medical service node status is a safe state; if the medical service node status is the safe state, return the flow data corresponding to the export request information to the external data terminal; if the medical service node status is not the safe state, determine the corresponding medical service node according to the medical service node status, call the corresponding node correction plan according to the medical service node, correct the medical service node based on the node correction plan, re-acquire the corrected medical service node status for inspection, until the corrected medical service node status is the safe state. Thereby, the service nodes in the medical service system are effectively detected and corrected to ensure the normal operation of the medical service system.

[0152] To solve the above technical problems, the present application also provides a computer device. Figure 8 , Figure 8 This is a basic structural block diagram of the computer device in this embodiment.

[0153] The computer device 8 includes a memory 81, a processor 82, and a network interface 83 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 8 with components 81-83, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable gate arrays (Field-Programmable Gate Array, FPGA), digital processors (Digital Signal Processor, DSP), embedded devices, etc.

[0154] The computer device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The computer device may interact with a user through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device.

[0155] The memory 81 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 81 can be an internal storage unit of the computer device 8, such as a hard disk or memory of the computer device 8. In other embodiments, the memory 81 can also be an external storage device of the computer device 8, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (FlashCard), etc. equipped on the computer device 8. Of course, the memory 81 can also include both the internal storage unit of the computer device 8 and its external storage device. In this embodiment, the memory 81 is generally used to store the operating system and various application software installed on the computer device 8, such as computer-readable instructions of the service system correction method, etc. In addition, the memory 81 can also be used to temporarily store various types of data that have been output or are to be output.

[0156] The processor 82 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips in some embodiments. The processor 82 is generally used to control the overall operation of the computer device 8. In this embodiment, the processor 82 is used to run computer-readable instructions stored in the memory 81 or process data, such as computer-readable instructions for running the service system correction method.

[0157] The network interface 83 may include a wireless network interface or a wired network interface. The network interface 83 is generally used to establish a communication connection between the computer device 8 and other electronic devices.

[0158] By adopting the above-mentioned computer device, this embodiment can obtain the export request information; query the corresponding medical service node request information according to the export request information; obtain the corresponding medical service node status according to the medical service node request information; check whether the medical service node status is a safe state; if the medical service node status is the safe state, return the flow data corresponding to the export request information to the external data terminal; if the medical service node status is not the safe state, determine the corresponding medical service node according to the medical service node status, call the corresponding node correction plan according to the medical service node, correct the medical service node based on the node correction plan, re-acquire the corrected medical service node status for inspection, until the corrected medical service node status is the safe state. Thereby, the service nodes in the medical service system are effectively detected and corrected to ensure the normal operation of the medical service system.

[0159] The present application also provides another embodiment, namely, providing a computer-readable storage medium, wherein the computer-readable storage medium stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the service system correction method as described above.

[0160] By adopting the above-mentioned computer-readable storage medium, this embodiment can obtain the export request information; query the corresponding medical service node request information according to the export request information; obtain the corresponding medical service node status according to the medical service node request information; check whether the medical service node status is a safe state; if the medical service node status is the safe state, return the flow data corresponding to the export request information to the external data terminal; if the medical service node status is not the safe state, determine the corresponding medical service node according to the medical service node status, call the corresponding node correction plan according to the medical service node, correct the medical service node based on the node correction plan, re-acquire the corrected medical service node status for inspection, until the corrected medical service node status is the safe state. Thereby, the service nodes in the medical service system are effectively detected and corrected to ensure the normal operation of the medical service system.

[0161] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0162] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application is described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions recorded in the aforementioned specific implementation methods, or to perform equivalent replacement of some of the technical features therein. Any equivalent structure made using the contents of the specification and drawings of this application, directly or indirectly used in other related technical fields, is similarly within the scope of patent protection of this application.

Claims

1. A service system correction method, characterized in that: The steps include: Get export request information; Querying corresponding medical service node request information according to the export request information; Obtain the corresponding medical service node status according to the medical service node request information; Check whether the medical service node is in a safe state; If the medical service node status is not the safe status, the corresponding medical service node is determined according to the medical service node status, and the corresponding node correction plan is called according to the medical service node. The medical service node is corrected based on the node correction plan, and the corrected medical service node status is re-obtained for inspection until the corrected medical service node status is the safe status.

2. The service system correction method according to claim 1, characterized in that: Before the step of obtaining the export request information, the method further includes the following steps: Get access request information; generating an access request field according to the access request information; Obtain the node request information corresponding to the medical service node, and use the access request field as the primary key and the node request information as the value to generate a key-value pair, save the key-value pair into a predetermined information memory, and obtain the medical service node request information.

3. The service system correction method according to claim 1, characterized in that: The step of obtaining the export request information specifically includes: Real-time detection of whether the preset traffic outlet has received the export request; If the preset traffic outlet receives the export request, the export request is intercepted, and the intercepted export request is sent to the preset filter for processing to obtain the export request information.

4. The service system correction method according to claim 3, characterized in that: The step of intercepting the egress request and sending the intercepted egress request to a preset filter for processing specifically includes: Obtaining a list of egress request events for the preset traffic egress; Obtain a current timestamp, and search for a current egress event in the egress request event list according to the current timestamp; Calling a preset service agent to intercept the export request according to the current export event; Determining the preset filter according to the preset service agent; Based on the preset service proxy, the intercepted egress request is forwarded to the preset filter for processing.

5. The service system correction method according to claim 1, characterized in that: The step of querying the corresponding medical service node request information according to the export request information specifically includes: Extracting a corresponding export request information identifier from the export request information; Acquire a corresponding export request information list from a database according to the export request information identifier; Obtain a list of medical service nodes, search the export request list according to the list of medical service nodes, and obtain the medical service node request information.

6. The service system correction method according to claim 1, characterized in that: The step of obtaining the corresponding medical service node status according to the medical service node request information specifically includes: Accessing a corresponding medical service node according to the medical service node request information; Obtaining a node status table corresponding to the medical service node; Acquire preset extraction time information, extract corresponding node status information from the node status table according to the extraction time information, and use the extracted node status information as the medical service node status.

7. The service system correction method according to claim 1, characterized in that: Before the step of calling the corresponding node correction scheme according to the medical service node and correcting the medical service node based on the node correction scheme, the following steps are also included: Get historical status information of medical service nodes; Determine the error problem of the medical service node according to the historical status information of the medical service node; Extracting corresponding solutions from a pre-built service knowledge base according to the medical service node error problem; Conduct simulation tests on the solution to obtain simulation results; Determine whether the simulation result of the solution meets the preset successful solution conditions; If the solution simulation result meets the preset solution success condition, the solution is saved as the node correction solution.

8. A service system correction device, characterized in that: include: An information acquisition module, used for acquiring export request information; An information query module, used to query corresponding medical service node request information according to the export request information; A status acquisition module, used to acquire the corresponding medical service node status according to the medical service node request information; A status inspection module, used to inspect whether the medical service node is in a safe state; A node correction module is used to determine the corresponding medical service node according to the medical service node status if the medical service node status is not the safe status, and call the corresponding node correction plan according to the medical service node, correct the medical service node based on the node correction plan, and re-acquire the corrected medical service node status for inspection until the corrected medical service node status is the safe status.

9. A computer device, characterized in that: The method comprises a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the service system correction method according to any one of claims 1 to 7 when executing the computer-readable instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by a processor, the steps of the service system correction method according to any one of claims 1 to 7 are implemented.

Images