A medical data push method, node, system and storage medium

Abstract

The present application discloses a medical data push method, which is applied to a first node, wherein the first node is at least deployed with a data extraction service and a first data push service; the first node has a first connection established with a first database and a second connection established with a second node; the first database stores medical data generated by online diagnosis and treatment; the method includes: based on the data extraction service, extracting medical data from the first database through the first connection, and storing the medical data in the second database; based on the first data push service, obtaining medical data from the second database; based on the first data push service, pushing medical data to the second node through the second connection; the second node is used to push the medical data to the medical data management node. The present application also discloses a medical data push method applied to the second node, a first node, a second node, a medical data push system, and a storage medium.

Description

Technical Field

[0001] The present application relates to the field of online medical data processing, and in particular to a medical data push method, a first node, a second node, a medical data push system, and a computer-readable storage medium. Background Art

[0002] Online smart healthcare provides a full range of Internet diagnosis and treatment services for third-party hospitals and patients. The medical data corresponding to online smart healthcare needs to be pushed to the local health and health supervision center to accept the supervision and management of the local health and health supervision center. In related technologies, the medical data push operation to the local health and health supervision center is performed based on the database that stores the medical data generated by online smart healthcare in real time. Therefore, long-term and frequent medical data read and write operations consume too much database resources for storing medical data, which can easily lead to blockage of medical data storage and push, increasing the risk of medical data not being pushed normally. Summary of the invention

[0003] The present application provides a medical data push method, a first node, a second node, a medical data push system, and a computer-readable storage medium.

[0004] The medical data push method provided in the present application stores the medical data generated by online medical care in a first database, and synchronizes the medical data in the first database to a second database. The medical data pushed to the medical data management center is directly obtained from the second database, thereby reducing the resource consumption of frequent reading and writing of the first database, reducing the risk of medical data storage and push blockage, and improving the robustness of the medical data push process.

[0005] The technical solution provided by this application is as follows:

[0006] The present application provides a medical data push method, which is applied to a first node, wherein the first node is at least deployed with a data extraction service and a first data push service; the first node is connected to a first database and is connected to a second node; the first database stores medical data generated by online diagnosis and treatment; the method comprises:

[0007] Based on the data extraction service, extracting the medical data from the first database through the first connection, and storing the medical data in a second database;

[0008] Based on the first data push service, acquiring the medical data from the second database;

[0009] Based on the first data push service, the medical data is pushed to the second node through the second connection; the second node is used to push the medical data to a medical data management node.

[0010] In some implementations, extracting the medical data from the first database through the first connection based on the data extraction service includes:

[0011] Acquire the update frequency of the medical data in the first database;

[0012] When the update frequency is less than a frequency threshold, the medical data is extracted from the first database through the first connection based on the data extraction service.

[0013] In some implementations, the pushing the medical data to the second node through the second connection based on the first data push service includes:

[0014] Verifying the medical data;

[0015] When the medical data passes verification, the medical data is pushed to the second node through the second connection based on the first data push service.

[0016] In some implementations, verifying the medical data includes:

[0017] Acquire medical data management rules; wherein the medical data management rules represent rules for the medical data management node to manage the medical data;

[0018] Based on the medical data management rules, the medical data is verified.

[0019] In some embodiments, the method further comprises:

[0020] Obtaining, through the second connection, a push result of the medical data;

[0021] When the push result is a push failure, based on the first data push service, the medical data is pushed to the second node again through the second connection;

[0022] When the number of push failures is greater than or equal to the push number threshold, push failure information is output.

[0023] In some embodiments, the method further comprises:

[0024] receiving, through the second connection, state information of the second node sent by the second node; wherein the state information is sent by the second node at a specified frequency;

[0025] If the status information is not received within a specified time, it is determined that the second node is in an unavailable state.

[0026] In some implementations, receiving, through the second connection, the state information of the second node sent by the second node includes:

[0027] Determine first configuration information and second node identity information; wherein the first configuration information includes identity information of a second node that is allowed to access the first node;

[0028] In a case where the second node identity information successfully matches the first configuration information, the state information is received through the second connection.

[0029] The present application also provides a medical data push method, the method is applied to a second node; a second connection is established between the second node and the first node; the medical data is obtained by the first node from the second database and pushed to the second node through the second connection based on the first data push service; the medical data in the second database is obtained by the first node from the first database through the first connection based on the data extraction service; the first node has the first connection established with the first database and the second connection established with the second node; the first node is at least deployed with the data extraction service and the first data push service; the first database stores the medical data generated by online diagnosis and treatment; the method comprises:

[0030] receiving the medical data pushed by the first node through the second connection;

[0031] The medical data is pushed to a medical data management node.

[0032] In some implementations, the second node is deployed with a data high availability service and a second data push service; a third connection is established between the second node and the medical data management node; and pushing the medical data to the medical data management node includes:

[0033] Upon receiving the medical data, determining a target data push service from the second data push services based on the data high availability service;

[0034] Based on the target data push service, the medical data is pushed to the medical data management node through the third connection.

[0035] In some implementations, receiving the medical data pushed by the first node through the second connection includes:

[0036] Determine second configuration information and first node identity information; wherein the second configuration information includes identity information of the first node that is allowed to access the second node;

[0037] When the first node identity information matches the second configuration information successfully, the medical data pushed by the first node is received through the second connection.

[0038] In some embodiments, the method further comprises:

[0039] The status information of the second node is sent to the first node at a specified frequency through the second connection; wherein, if the first node does not receive the status information within a specified time, it can be determined that the second node is in an unavailable state.

[0040] The present application also provides a first node, wherein the first node is at least deployed with a data extraction service and a first data push service; the first node is connected to a first database and connected to a second node; the first database stores medical data generated by online diagnosis and treatment; the second node is used to push the medical data to a medical data management node; the first node includes a first receiving module, a first processing module and a first pushing module; wherein:

[0041] The first receiving module is used to extract the medical data from the first database through the first connection based on the data extraction service;

[0042] The first processing module is used to store the medical data in a second database;

[0043] The first push module is used to push the medical data to the second node through the second connection based on the first data push service.

[0044] The present application also provides a first node, the first node comprising a first processor, a first memory and a first communication bus; wherein:

[0045] The first communication bus is used to implement a communication connection between the first processor and the first memory;

[0046] The first processor is used to execute the computer program stored in the first memory to implement the medical data push method applied to the first node as described in any of the above.

[0047] The present application also provides a second node, a second connection is established between the second node and the first node; the medical data is obtained by the first node from the second database and pushed to the second node through the second connection based on the first data push service; the medical data in the second database is obtained by the first node from the first database through the first connection based on the data extraction service; the first node has the first connection established with the first database and the second connection established with the second node; the first node is at least deployed with the data extraction service and the first data push service; the first database stores the medical data generated by online diagnosis and treatment; the second node includes a second receiving module and a second pushing module; wherein:

[0048] The second receiving module is used to receive the medical data sent by the first node through the second connection;

[0049] The second pushing module is used to push the medical data to a medical data management node.

[0050] The present application also provides a second node, the second node comprising: a second processor, a second memory, and a second communication bus; wherein:

[0051] The second communication bus is used to realize the communication connection between the second processor and the second memory;

[0052] The second processor is used to execute the computer program stored in the second memory to implement the medical data push method applied to the second node as described in any of the above.

[0053] The present application also provides a medical data push system, which includes a first node as described in any of the above, and a second node as described in any of the above.

[0054] The present application also provides a computer-readable storage medium, in which a computer program is stored to implement the medical data push method applied to the first node as described in any of the above, or the medical data push method applied to the second node as described in any of the above.

[0055] In the medical data push method provided in the present application, medical data generated by online diagnosis and treatment are stored in a first database, and medical data are extracted from the first database through a data extraction service and stored in a second database. The actual medical data push operation is performed on the medical data stored in the second database through the first data push service.

[0056] Therefore, the medical data push method provided by the present application, during the medical data push process, realizes the isolation of the medical data storage database and the medical data push database, under the premise that the first database and the second database are synchronized, that is, realizes the decoupling between the medical data and the medical data to be pushed; and compared with the method of directly pushing the medical data in the first database to the medical data management center, it reduces the resource consumption of the first database, reduces the blocking probability of medical data push and storage, and improves the robustness of online smart medical services. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 A schematic diagram of the network structure for pushing medical data in related technologies;

[0058] Figure 2 A flowchart of a first medical data push method applied to a first node provided in the present application;

[0059] Figure 3 A flowchart of a second medical data push method applied to a first node provided in the present application;

[0060] Figure 4 A flowchart of the first medical data push method applied to the second node provided in this application;

[0061] Figure 5 A flowchart of a second medical data push method applied to a second node provided in the present application;

[0062] Figure 6 Schematic diagram of the network structure for pushing medical data provided by this application;

[0063] Figure 7 A schematic diagram of the structure of the first node provided by the present application;

[0064] Figure 8 A schematic diagram of the structure of the second first node provided in this application;

[0065] Fig. 9 A schematic diagram of the structure of the first second node provided in this application;

[0066] Fig.10 A schematic diagram of the structure of the second second node provided in this application;

[0067] Fig.11 A structural diagram of the medical data push system provided for this application. DETAILED DESCRIPTION

[0068] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0069] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0070] The present application relates to the field of online medical data processing, and in particular to a medical data push method, a first node, a second node, a medical data push system, and a computer-readable storage medium.

[0071] Online smart medical care provides third-party hospitals and patients with a full range of Internet medical services covering all processes. In the process of providing online medical services to patients, the online smart medical platform can generate medical data related to the patient's condition, age, gender, work, etc. These medical data need to be supervised and managed by various medical data management centers, such as the local health and health commission supervision center.

[0072] In practical applications, with the widespread use of online smart medical services, a large amount of medical data will be more strictly supervised and managed by local medical data management centers. Therefore, how to push a large amount of medical data to the medical data management center safely and securely is crucial.

[0073] Figure 1 This is a schematic diagram of the network structure for pushing medical data in related technologies.

[0074] from Figure 1 It can be seen that the network structure for pushing medical data in the related art may include three parts: business node 101, supervision push node 103 and medical data management node 105. Among them, business node 101 may be an internal node of the online smart medical network; supervision push node 103 and medical data management node 105 may be external nodes of the online smart medical network.

[0075] exist Figure 1 In the example, the service node 101 is used to obtain medical data generated during the execution of the online smart medical service. The service node 101 may include at least two services, such as a first service and a second service. Through at least two services, high availability of medical data acquisition can be achieved.

[0076] exist Figure 1 In the example, the business database 102 is used to store various medical data acquired by the business node 101, wherein the business database 102 may also include at least two databases, such as a master database (DataBase Master) and a slave database (DataBase Slave). Through at least two databases, a robust implementation of the medical data storage process can be achieved.

[0077] exist Figure 1In the example, the supervision push node 103 is used to obtain medical data from the business database 102 and push the medical data to the data transfer node 104.

[0078] In actual applications, the business node 101, the business database 102 and the supervision push node 103 can be called internal services of online smart medical care, and these services are deployed inside the online smart medical care network.

[0079] exist Figure 1 In the embodiment, the data transfer node 104 is used to transfer the medical data pushed by the supervision push node 103 to the medical data management node 105. In practical applications, the data transfer node 104 is usually a front-end server deployed in a hospital, which can not only realize the transfer and push of medical data, but also realize the adaptation with the medical data management node 105.

[0080] exist Figure 1 In the figure, the medical data management node 105 is used to receive the medical data transferred by the data transfer node 104 and supervise and manage the medical data. Exemplarily, the medical data management node 105 can be the node where the medical data management center mentioned above is located.

[0081] In related technologies, the medical data management node 105 may be an Internet hospital supervision platform led by a local government.

[0082] On the one hand, the medical data management node 105 inspects the medical data. Only when the medical data inspection and compliance verification are passed, the hospital that generates the medical data can apply for Internet hospital qualification; on the other hand, medical data is highly private data, so Figure 1 The data transfer node 104 shown is not open to the outside. In actual applications, the data transfer node 104 may be a service deployed in a front-end server of a hospital. That is, medical data can only be pushed and transferred through a front-end server deployed in a hospital.

[0083] And in Figure 1 In the present invention, the business node 101 and the supervision push node 103 share the business database 102, which will cause excessive consumption of resources provided by the business database 102 for data reading and writing, thereby affecting the performance of the business database 102, increasing the risk of data reading and writing in the business database 102, and further increasing the risk of failure in pushing medical data.

[0084] Based on the above problems, an embodiment of the present application provides a medical data push method. The method is applied in a first node.

[0085] In one implementation, the first node may be any node that can acquire online smart medical data.

[0086] In one implementation, the first node may be a physical device or a virtual device.

[0087] In one implementation, the first node may be Figure 1 The supervision push number node 103 in.

[0088] In one implementation, there may be multiple first nodes.

[0089] In an embodiment of the present application, the first node is deployed with at least a data extraction service and a first data push service; a first connection is established between the first node and the first database, and a second connection is established between the first node and the second node, and the first database stores medical data generated by online diagnosis and treatment.

[0090] In one implementation, the number of data extraction services and the number of first data push services may both be plural.

[0091] In one embodiment, the data extraction service is used to extract medical data from a first database.

[0092] In one embodiment, the first data push service is used to push the medical data to the second node.

[0093] In one embodiment, the second node may be Figure 1 The medical data management node 105 in the communication connection is established with a node, such as Figure 1 The data transfer node 104 in the embodiment. The second node may be a physical machine device or a virtual node in the physical machine device.

[0094] In one implementation, the second node may be a node where a front-end server deployed in a hospital is located.

[0095] In one implementation, the number of the second nodes may be multiple.

[0096] In one implementation, the number of first databases may be multiple.

[0097] In one embodiment, the first database may be Figure 1 The service database 102 in the service node 101 is used to store in real time the medical data generated by the service node 101. Exemplarily, the first database may be a relational database such as a MySQL database.

[0098] In one implementation, the first connection and the second connection may be established simultaneously.

[0099] In one embodiment, online diagnosis and treatment may be an online smart medical service applied for by the patient.

[0100] In one embodiment, the medical data may include at least one of the following data corresponding to online diagnosis and treatment: short-term medical advice, long-term medical advice, prescription, description of the condition, diagnosis result, whether it is the first visit, medical history, etc. For example, the medical data may include personal information of the patient, such as name, age, gender, date of birth, occupation, etc.

[0101] It should be noted that the medical data push method provided in the embodiment of the present application can be implemented by the processor of the first node, and the above-mentioned processor can be at least one of an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), a programmable logic device (PLD), a field programmable gate array (FPGA), a central processing unit (CPU), a controller, a microcontroller, and a microprocessor.

[0102] Figure 2 The flowchart of the first medical data push method applied to the first node provided in the embodiment of the present application is as follows. Figure 2 As shown, the method may include steps 201 to 203.

[0103] Step 201: Based on the data extraction service, extract medical data from the first database through the first connection, and store the medical data in the second database.

[0104] In one implementation, the second database may be directly set in the first node, or the second database is not set in the first node, but a communication connection is established between the second database and the first node.

[0105] In one embodiment, extracting medical data from the first database through the first connection and storing the medical data in the second database may be achieved in any of the following ways:

[0106] Based on the data extraction service (Extract-data Service), the first interface and the second interface are determined; the amount of medical data in the first database is detected through the first interface, and when the amount of data exceeds the first threshold, all medical data are extracted from the first database through the second interface, and the medical data is stored in the second database. The first interface is used to detect the amount of data in the first database; the second interface is used to extract medical data from the first database.

[0107] The amount of medical data in the first database is detected through the first interface. When the amount of medical data in the first database changes, newly added medical data is extracted from the first database through the second interface, and the medical data is stored in the second database.

[0108] Through the first connection, medical data is extracted from the first database, and the medical data is assembled to obtain first data, and then the first data is stored in the second database. Exemplarily, the medical data can be assembled according to the management rules of the medical data management center for medical data.

[0109] At fixed time intervals, medical data is extracted from the first database through the first connection and the medical data is stored in the second database.

[0110] In the embodiment of the present application, the medical data stored in the first database may also be referred to as business data. The medical data stored in the second database may also be referred to as medical data to be pushed, business data to be pushed, or supervision data to be pushed.

[0111] Accordingly, the first database may be referred to as a business database (Bussiness DataBase); the second database may be referred to as a supervision push database (Supervision DataBase).

[0112] Step 202: Based on the first data push service, obtain medical data from the second database.

[0113] In one implementation, obtaining medical data from the second database based on the first data push service may be achieved in any of the following ways:

[0114] After the data extraction service stores the medical data in the second database, it generates a first message, and the data extraction service sends the first message to the first data push service. After the first data push service receives the first message, it obtains the medical data from the second database through the third interface. The first message indicates that the medical data has been stored in the second database; the third interface is an interface for extracting medical data in the first data push service.

[0115] The first data push service detects the amount of medical data in the second database through the fourth interface, and obtains medical data from the second database through the third interface when the amount of medical data in the second database is greater than or equal to the second threshold. The fourth interface is an interface in the first data push service for detecting the storage status of medical data in the second database.

[0116] The first data push service detects the incremental change of the amount of medical data in the second database through the fourth interface, and obtains the medical data from the second database through the third interface when the incremental amount of medical data in a unit time is greater than or equal to a third threshold value. The unit time may be one hour or one day.

[0117] The medical data is obtained from the second database in real time or at fixed time intervals based on the first data push service.

[0118] Step 203: Based on the first data push service, push the medical data to the second node through the second connection.

[0119] The second node is used to push the medical data to the medical data management node.

[0120] In one embodiment, the medical data management node can be Figure 1 The medical data management node 105 in.

[0121] In one implementation, pushing the medical data to the second node through the second connection based on the first data push service may be implemented in any of the following ways:

[0122] After the first data push service obtains a certain amount of medical data, it directly pushes the medical data to the second node through the second connection.

[0123] A medical data push request is sent to the second node through the first data push service. When the second node returns information allowing medical data push, medical data is pushed to the second node through the second connection based on the first data push service.

[0124] From the above, it can be seen that in the medical data push method applied to the first node provided in the embodiment of the present application, the first database stores medical data generated by online diagnosis and treatment, and at the same time, the medical data is extracted from the first database through the data extraction service and stored in the second database, and the actual medical data push operation is performed on the medical data stored in the second database through the first data push service. Therefore, in the medical data push method applied to the first node provided in the embodiment of the present application, during the medical data push process, on the premise that the first database is synchronized with the second database, the isolation of the medical data storage database and the medical data push database is achieved, that is, the decoupling between the medical data and the medical data to be pushed is achieved; and, compared with the method of directly pushing the medical data in the first database to the medical data management center, the resource consumption of the first database is reduced, the blocking probability of medical data push and storage is reduced, and the robustness of the online smart medical service is improved.

[0125] Based on the foregoing embodiments, the embodiments of the present application provide a second medical data push method applied to a first node. Figure 3 The flowchart of the second medical data push method applied to the first node provided in the embodiment of the present application is as follows. Figure 3 As shown, the method may include steps 301 to 304:

[0126] Step 301: Obtain the update frequency of medical data in the first database.

[0127] In one implementation, obtaining the update frequency of the medical data in the first database may be achieved by any of the following methods:

[0128] Through the first connection, the update status of the medical data in the first database is obtained in real time, and the update frequency is determined according to the update status.

[0129] Based on the first interface in the data extraction service, the update frequency of the medical data in the first database is obtained in real time through the first connection.

[0130] In one embodiment, the update frequency of the medical data in the first database may be constantly changing. For example, the update frequency of the medical data in the first database is lower during a specified time period. For example, the update frequency of the medical data in the first database around midnight is lower than that at other times of the day.

[0131] Step 302: When the update frequency is less than the frequency threshold, extract medical data from the first database through the first connection based on the data extraction service.

[0132] In one implementation, the frequency threshold may be set according to different types of online diagnosis and treatment services.

[0133] In an embodiment of the present application, medical data is extracted from the first database through the first connection based on the data extraction service only when the update frequency of the medical data in the first database is less than the frequency threshold, thereby reducing the resource consumption corresponding to the frequent access to the first database and reducing the interference to the first database, thereby laying the foundation for the safe and stable push of medical data.

[0134] Step 303: Based on the first data push service, obtain medical data from the second database.

[0135] Step 304: Based on the first data push service, push the medical data to the second node through the second connection.

[0136] The second node is used to push the medical data to the medical data management node.

[0137] Exemplarily, step 304 can be implemented through steps A1 to A2:

[0138] Step A1: verify the medical data.

[0139] In one implementation, verifying the medical data may be an operation performed after the first data push service obtains the medical data from the second database.

[0140] Exemplarily, step A1 may be implemented through steps B1 to B2:

[0141] Step B1: Obtain medical data management rules.

[0142] Among them, the medical data management rules refer to the rules for the medical data management node to manage medical data.

[0143] In one embodiment, the medical data management rules may be obtained from the medical data management node in real time. Exemplarily, the medical data management rules of the medical data management node may be adjusted and changed. When the medical data management rules of the medical data management node are changed, the medical data management node may send the rules to the first node.

[0144] In one implementation, the medical data management rules may be obtained from the medical data management node after the hospital obtains online diagnosis and treatment qualifications.

[0145] Step B2: verify the medical data based on the medical data management rules.

[0146] In one implementation, the medical data may be verified by any of the following methods:

[0147] Part of the medical data is sampled from the medical data, and based on the medical data management rules, the sampled part of the medical data is verified.

[0148] Obtain medical data of a specified disease type, and verify the medical data of the specified disease type based on the medical data management rules. Exemplarily, in the event of an epidemic, the medical data corresponding to the epidemic may be verified.

[0149] The medical data of the specified drugs prescribed in the prescription is obtained, and the medical data of the specified drugs prescribed in the prescription is verified based on the medical data management rules.

[0150] All medical data that needs to be pushed by the first data push service are verified based on the medical data management rules.

[0151] Step A2: When the medical data verification is passed, the medical data is pushed to the second node through the second connection based on the first data push service.

[0152] Accordingly, when the medical data verification fails, the medical data may not be pushed. Exemplarily, the specific reason why the medical data is not pushed may also be output.

[0153] In related technologies, if a medical data management center detects medical data that does not comply with its management specifications, it will determine that there is a problem with the hospital's online diagnosis and treatment services, which will affect the hospital's online diagnosis and treatment qualifications.

[0154] In the medical data push method applied to the first node provided in the embodiment of the present application, through the above steps, the medical data can be verified in advance before pushing the medical data, so that the pushed medical data can meet the supervision requirements of the medical data management node; thereby weakening the impact of the medical data pushed to the medical data management node on the hospital's online diagnosis and treatment qualifications.

[0155] Exemplarily, the medical data push method applied to the first node provided in the embodiment of the present application may further include steps C1 to C3:

[0156] Step C1: Obtain push results of medical data through the second connection.

[0157] In one implementation, the push result of the medical data may represent at least one of the following:

[0158] Whether the medical data pushed by the first data push service is successfully transmitted to the second node;

[0159] Whether the second node successfully saves the medical data pushed by the first data push service;

[0160] Whether the second node rejects the medical data pushed by the first data push service.

[0161] In one implementation, the result of pushing the medical data may be returned synchronously after the first data push service finishes pushing the medical data, or may be returned asynchronously after the first data push service pushes the medical data multiple times.

[0162] In one implementation, obtaining the push result of the medical data may be achieved based on the first data push service through the second connection.

[0163] In one embodiment, the push result of medical data may be that when the first node does not receive the medical data push result within a specified time period, the first node sends a request for obtaining the medical data push result to the second node, and the second node sends the request to the first node after receiving the request.

[0164] Step C2: When the push result is a push failure, based on the first data push service, the medical data is pushed to the second node again through the second connection.

[0165] In one implementation, push failure may indicate at least one of the following: the second node rejects the medical data, the second node does not receive the medical data, the medical data received by the second node is incomplete (eg, medical data packet loss), etc.

[0166] Exemplarily, based on the first data push service, re-pushing the medical data to the second node through the second connection may be implemented through step 304 .

[0167] Step C3: When the number of push failures is greater than or equal to the push number threshold, output push failure information.

[0168] Accordingly, when the number of push failures is less than the push number threshold, the medical data can be pushed again through step C2.

[0169] In one implementation, the push failure information may be output in the following ways: a character string carrying the failure reason, sound information, light flashing information, etc.

[0170] In the related art, no processing is done for the failure problem in the process of pushing medical data, and no message reminder is given. However, in the medical data pushing method provided in the embodiment of the present application, if the push of medical data fails, you can try to push it again. If the number of push failures is too many, you can also output a prompt message of the push failure, so that professional technicians can intervene in the investigation in time, thereby reducing the risk of medical data loss caused by the failure of medical data push.

[0171] In some implementations, the medical data push method applied to the first node provided in the embodiment of the present application may further include steps D1 to D2:

[0172] Step D1, receiving the state information of the second node sent by the second node through the second connection;

[0173] The state information is sent by the second node at a specified frequency.

[0174] In one implementation, the state information of the second node may be sent under any of the following conditions:

[0175] Under the condition that the second node receives the liveness detection request sent by the first node;

[0176] Under the condition that the first node and the second node have agreed on a status message sending rule for the second node.

[0177] In one implementation, the specified frequency may be adjusted according to actual conditions.

[0178] In one embodiment, the status information of the second node may indicate the current usage status of the hardware and / or software resources of the second node, such as whether the port is occupied, the running status of the processes and threads related to the reception and processing of medical data, the remaining capacity of the storage space for storing medical data, whether the relevant interface in the second node is illegally called, whether there is illegal data uploaded, etc.

[0179] Exemplarily, step D1 can be implemented by steps E1 to E2:

[0180] Step E1: Determine first configuration information and second node identity information.

[0181] The first configuration information includes identity information of a second node that is allowed to access the first node.

[0182] In one implementation, the first configuration information includes identity information of multiple second nodes.

[0183] In one implementation, the first configuration information may only include the identity information of the second node that is capable of receiving and processing the medical data pushed by the first node.

[0184] In one implementation, the identity information of the second node may include at least one of a network address, a port number, identification information, etc. of the second node.

[0185] In one implementation, the first configuration information may be determined when the second connection is established between the first node and the second node.

[0186] In one implementation, the second node identity information may be obtained by parsing the status information sent by the second node after receiving the status information.

[0187] Step E2: When the second node identity information successfully matches the first configuration information, status information is received through the second connection.

[0188] Accordingly, when the second node identity information fails to match the first configuration information, the state information is discarded; and the reason for discarding the state information may also be sent to the second node.

[0189] Exemplarily, if the second node identity information successfully matches the first configuration information, it can indicate that the second node is a safe node for processing the medical data pushed by the first node, and the status information of the second node can be received at this time.

[0190] Step D2: If no status information is received within a specified time, determine that the second node is in an unavailable state.

[0191] Exemplarily, if the status information can be received at a specified frequency within a specified time, and the status information indicates that the second node is in good operating condition, it can be determined that the second node is in an available state.

[0192] In one embodiment, the unavailable state of the second node may include at least one of the following: the port for receiving medical data is blocked, the remaining storage capacity of the storage space for storing medical data is insufficient, the memory resources of the second node are insufficient, the second node is stuck, the process and / or thread for processing medical data in the second node is abnormal, the interface in the second node is illegally called, the related service in the second node is used to upload illegal data, the port between the second node and the health-specific network is disconnected, the network gate is blocked, etc. Among them, the process and / or thread for processing medical data in the second node is abnormal, which can indicate that the process and / or thread is in a blocked, suspended, etc. state.

[0193] In the related technology, the second node can be a front-end server deployed in a hospital. Since the front-end server deployed in a hospital is not open to the external network but is only connected to the health-specific network, it is impossible to monitor the survival of the hospital front-end server. Therefore, abnormal problems including failure of the hospital front-end server or unavailability of related services deployed in the hospital front-end server cannot be discovered in time, which increases the risk of medical data not being pushed normally.

[0194] In the medical data push method provided in the embodiment of the present application, through the above steps, on the one hand, it is possible to ensure in real time whether the second node is currently safe; on the other hand, it is also possible to monitor in real time whether the second node is alive. When the second node is in an abnormal state, the first node can be aware of the state of the second node in time, thereby reducing the risk of medical data not being pushed normally.

[0195] In an embodiment of the present application, the connection between nodes and databases, and between nodes, such as the communication connection between the first node and the first database, between the first node and the second database, between the first node and the second node, and between the second node and the medical data management node, can be realized through the HyperText Transfer Protocol (HTTP). In actual applications, the HTTP protocol runs on top of the Transmission Control Protocol (TCP).

[0196] Any service in the embodiments of the present application, such as the data extraction service, the first data push service, and the related services deployed in the second node, can be a type of WebService. Among them, WebService is a platform-independent, low-coupled, programmable Web application that can use the open eXtensible Markup Language (XML) standard to describe, publish, discover, coordinate and configure applications for developing distributed interactive applications.

[0197] From the above, it can be seen that the medical data push method applied to the first node provided in the embodiment of the present application monitors the update frequency of the medical data in the first database in the first node. When the update frequency of the medical data is less than the frequency threshold, the medical data is extracted from the first database through the first connection based on the data extraction service, and then the medical data is stored in the second database; the medical data is then obtained from the second database through the first data push service, and the medical data is pushed to the second node based on the first data push service, so that the second node can push the medical data to the medical data management node.

[0198] In this way, the medical data push method applied to the first node provided in the embodiment of the present application realizes the decoupling between the medical data generated by online diagnosis and treatment and the medical data to be pushed by storing the medical data generated by online diagnosis and treatment and the medical data to be pushed in different databases respectively. Moreover, the synchronization of medical data between the second database and the first database is performed only when the update frequency of the medical data in the first database is lower than the preset frequency, thereby further reducing the interference with the medical data stored in the first database and improving the stability of medical data push.

[0199] Based on the foregoing embodiments, the embodiments of the present application provide a medical data push method applied to a second node.

[0200] Among them, a second connection is established between the second node and the first node; the medical data is obtained by the first node from the second database and pushed to the second node through the second connection based on the first data push service; the medical data in the second database is obtained by the first node from the first database through the first connection based on the data extraction service; the first node establishes a first connection with the first database and a second connection with the second node; the first node is deployed with at least the data extraction service and the first data push service; the first database stores medical data generated by online diagnosis and treatment.

[0201] It should be noted that the medical data push method provided in the embodiment of the present application can be implemented by a processor of the second node, and the above-mentioned processor can be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, controller, microcontroller, and microprocessor.

[0202] Figure 4 The flowchart of the first medical data push method applied to the second node provided in the embodiment of the present application is as follows. Figure 4 As shown, the method may include steps 401 to 402:

[0203] Step 401: Receive medical data pushed by the first node through the second connection.

[0204] Step 402: Push the medical data to the medical data management node.

[0205] In one implementation, pushing the medical data to the medical data management node may be achieved by any of the following methods:

[0206] When the amount of medical data received and stored by the second node is greater than or equal to a fourth threshold, the medical data is pushed to the medical data management node;

[0207] The second node pushes the medical data to the medical data management node at a specified time interval;

[0208] The second node pushes the medical data to the medical data management node according to the data push method agreed upon by the medical data management node.

[0209] From the above, it can be seen that in the medical data push method applied to the second node provided in the embodiment of the present application, the medical data received by the second node is pushed by the first node, and the medical data pushed by the first node is obtained from the second database. The medical data in the second database is extracted from the first database by the data extraction service in the first node and the medical data is stored in the second database. The medical data pushed by the first node is obtained from the second database and pushed to the second node by the first data push service. After the second node receives the medical data, the medical data is pushed to the medical data management node. In this way, the first node realizes the decoupling between the medical data generated by the online diagnosis and treatment in real time and the medical data to be pushed by storing the medical data generated by the online diagnosis and treatment in two databases respectively, thereby reducing the data reading and writing pressure of the first database caused by data push based on the first database, and also reducing the risk of medical data push.

[0210] Based on the foregoing embodiments, the embodiments of the present application also provide a second medical data push method applied to a second node. Figure 5 A flowchart of a second method for pushing medical data applied to a second node provided in an embodiment of the present application.

[0211] Exemplarily, in the second node, a data high availability service and a second data push service may be deployed; and a third connection is established between the second node and the medical data management node.

[0212] In a real-time manner, the number of data high-availability services and the number of second data push services can be multiple.

[0213] like Figure 5 As shown, the method may include steps 501 to 503:

[0214] Step 501: Receive medical data pushed by the first node through the second connection.

[0215] Exemplarily, step 501 can be implemented through steps F1 to F2:

[0216] Step F1, determine the second configuration information and the first node identity information.

[0217] The second configuration information includes identity information of the first node that is allowed to access the second node.

[0218] In one implementation, the second configuration information may be determined before the second connection is established between the first node and the second node.

[0219] In one implementation, the identity information of the first node may include identification information, network address information, port number information, etc. of the first node.

[0220] In one implementation, the identity information of the first node may be determined by the second node based on a data request from the first node to push medical data to the second node, or a medical data push request sent by the first node to the second node.

[0221] Step F2: When the identity information of the first node matches the second configuration information successfully, the medical data pushed by the first node is received through the second connection.

[0222] Accordingly, when the identity information of the first node fails to match the second configuration information, the medical data pushed by the first node may not be received or rejected, and the reason for the failure to push the medical data may be returned to the first node.

[0223] For example, the second node may be a front-end server deployed in a hospital. In the related art, when the front-end server exposes an interface to the outside, there are security risks, for example, it may be called by an unsafe visitor to upload illegal data.

[0224] In the medical data push method provided in the embodiment of the present application, the second node can verify the identity information of the first node, thereby improving the security of the medical data push network.

[0225] Step 502: When medical data is received, a target data push service is determined from the second data push service based on the data high availability service.

[0226] In one embodiment, the data high availability service deployed in the second node also has the function of balanced processing of medical data.

[0227] In one embodiment, the data high availability service can be implemented through the combination of Nginx and Keepalived. Among them, Nginx (engine x) is a high-performance HTTP and reverse proxy web server, and also provides Internet Mail Access Protocol (IMAP) / Post Office Protocol Version 3 (Post Office Protocol-Version 3, POP3) / Simple Mail Transfer Protocol (SMTP); Keepalived provides a high-performance server high availability or hot standby solution, which can be used to prevent the occurrence of single point failure of the server. In an embodiment of the present application, the high availability of the second node can be achieved through the combination of Keepalived and Nginx.

[0228] In an embodiment of the present application, after the second node receives the medical data, the data high availability service can determine the target data push service that is ultimately used to push the medical data based on the status of each service in the second data push service.

[0229] Step 503: Based on the target data push service, the medical data is pushed to the medical data management node through the third connection.

[0230] In the embodiment of the present application, each second data push service can push the medical data to the medical data management node through the third connection.

[0231] In the related art, the second node may be a front-end server deployed by the hospital. If the front-end server is deployed alone, once a system downtime occurs, medical data cannot be pushed. Therefore, such a medical data push method has a high risk.

[0232] In the medical data push method provided in the embodiment of the present application, a high-availability service is deployed in the second node. When any second data push service is in poor operating condition, the current medical data can be smoothly sent to other available second data push services through the high-availability service, thereby improving the stability of medical data push.

[0233] Exemplarily, in an embodiment of the present application, if the second node fails to push data to the medical data management node, it may also return a message to the first node indicating that the medical data has failed to be pushed to the medical data management node.

[0234] In related technologies, since the regulatory rules and regulations of medical data management nodes are still in a state of continuous improvement, during the updating of the regulatory rules and regulations, the medical data management node services will also be updated synchronously. During the updating process, problems such as update failure and new version failure may occur, which may easily lead to failure in pushing medical data to the medical data management node.

[0235] In the embodiment of the present application, the second node returns the message of failure in pushing medical data to the medical data management node to the first node before the first node, which provides conditions for the first node to obtain the push status of medical data in real time, accurately and objectively, thereby reducing the risk of failure in pushing each medical data and the risk of push omissions.

[0236] In the embodiment of the present application, the medical data push method applied to the second node may also perform the following operations:

[0237] The status information of the second node is sent to the first node at a specified frequency through the second connection; wherein, if the first node does not receive the status information within the specified time, it can be determined that the second node is in an unavailable state.

[0238] From the above, it can be seen that the medical data push method applied to the second node provided in the embodiment of the present application realizes the decoupling between the medical data generated by the online diagnosis and treatment in real time and the medical data to be pushed in two databases in the first node, thereby reducing the pressure of reading and writing data on the first database due to data push based on the first database, and reducing the risk of medical data push; and, through the data high-availability service and the second data push service deployed in the second node, the second node can realize stable push of medical data.

[0239] Based on the foregoing embodiments, the embodiments of the present application provide a network structure in which internal nodes of an online smart medical network collaborate with hospital front-end nodes to complete medical data push. Figure 6 A schematic diagram of the network structure for pushing medical data provided in an embodiment of the present application.

[0240] exist Figure 6 In the embodiment, the service node 101 is used to store the medical data in the first database 102 when the first service and / or the second service generates medical data. The first service and the second service may be the online diagnosis and treatment service described in the above embodiment.

[0241] exist Figure 6In the embodiment, the medical data extraction service deployed in the supervisory push node 103 is used to extract medical data from the first database 102 and store the medical data in the second database. The medical data stored in the second master database and the second slave database in the second database are the same. Through data synchronization between the second master database and the second slave database, stable storage of medical data in the supervisory push node 103 can be achieved.

[0242] The first data push service deployed in the supervision push node 103 is used to obtain medical data from the second database. Exemplarily, the medical data can also be assembled and the assembled medical data can be pushed to the second node.

[0243] Exemplarily, the supervision push node 103 also has the following functions:

[0244] Verification: Before the supervision push node 103 pushes the medical data to the data transfer node 104, the medical data can also be verified. The medical data will be pushed to the data transfer node 104 only when the medical data verification passes.

[0245] Early warning: The early warning function is mainly reflected in the following three aspects:

[0246] When the supervision push node 103 receives the medical data push result returned by the data transfer node 104 as a push failure, it can output a warning message of the push failure;

[0247] Under the condition that the supervision push node 103 detects that the data transfer node 104 is unavailable, or does not receive the status information sent by the data transfer node 104, it can also output the warning information that the data transfer node 104 is unavailable;

[0248] When the number of failures in pushing medical data through the first data push service exceeds a push number threshold, a warning message indicating that the number of push failures is too many may be output.

[0249] Data push exception retry: under the condition that the supervision push node 103 receives the return of the data transfer node 104 indicating that the medical data push fails, the medical data can be pushed again based on the first data push service.

[0250] Setting a whitelist: By setting a whitelist, the identity information of the data transfer node 104 can be identified under the condition of the status information sent by the data transfer node 104, thereby ensuring the security of medical data push.

[0251] Hospital front-end service activity detection: used to send an activity detection request to the data transfer node 104 to trigger the data transfer node 104 to send its status information to the supervision push node 103.

[0252] Determine the push result: after the medical data is pushed, send a push result acquisition request to the data transfer node 104 and receive the push result.

[0253] exist Figure 6 In the data transfer node 104, at least two high-availability services and at least two data transfer services are included; wherein, the at least two high-availability services may include: a first high-availability service and a second high-availability service; the at least two data transfer services may include a first data transfer service, a second data transfer service and a third data transfer service; and, the at least two data transfer services may have the same function as the second data push service in the aforementioned embodiment.

[0254] The data transfer node 104 provides an access interface for at least one supervisory push node 103 through a unified virtual Internet Protocol Address (VIP). Among them, VIP is a type of Internet Protocol (IP) address set to achieve high availability. This type of IP address is not bound to a specific instance such as a server in a cluster, a router, or any network card in a server, and has high reliability.

[0255] When the data transfer node 104 receives medical data pushed by any supervisory push node 103 through VIP, any high-availability service can receive the medical data and determine the target data transfer service from multiple data transfer services based on the load of each data transfer service, such as the first data transfer service, thereby pushing the medical data to the medical data management node 105 through the first data transfer service.

[0256] The data transfer node 104 also has a whitelist setting function, which is used to verify the identity information of the supervisory push node 103 when receiving medical data pushed by any medical data management node 104, thereby improving the security of medical data push.

[0257] exist Figure 6 In the figure, the medical data management node 105 is used to supervise and manage the medical data pushed by the data transfer node 104.

[0258] Depend on Figure 6It can be seen that the medical data push method provided in the embodiment of the present application, through the coordinated cooperation of the first node and the second node, achieves the decoupling of pushed medical data and medical data generated by business services without changing the medical data push network structure in the relevant technology. It can also verify the medical data during the medical data push process, detect the medical data push results in real time, and detect the status of the data transfer node 104, thereby laying the foundation for the safe, stable and continuous push of medical data.

[0259] Based on the above embodiments, the embodiment of the present application further provides a first first node 7. The first node is deployed with at least a data extraction service and a first data push service; the first node has a first connection established with a first database and a second connection established with a second node; the first database stores medical data generated by online diagnosis and treatment; the second node is used to push the medical data to a medical data management node.

[0260] Figure 7 A schematic diagram of the structure of the first first node 7 provided in an embodiment of the present application.

[0261] like Figure 7 As shown, the first node 7 may include a first receiving module 701, a first processing module 702 and a first pushing module 703. Among them:

[0262] The first receiving module 701 is used to extract medical data from the first database through the first connection based on the data extraction service;

[0263] A first processing module 702 is used to store the medical data into a second database;

[0264] The first push module 703 is used to push the medical data to the second node through the second connection based on the first data push service.

[0265] In some embodiments, the first processing module 702 is used to obtain the update frequency of the medical data in the first database; when the update frequency is less than the frequency threshold, the medical data is extracted from the first database through the first connection based on the data extraction service.

[0266] In some implementations, the first processing module 702 is used to verify the medical data; if the medical data verification passes, the medical data is pushed to the second node through the second connection based on the first data push service.

[0267] In some implementations, the first processing module 702 is used to obtain medical data management rules; and verify the medical data based on the medical data management rules; wherein the medical data management rules represent the rules for the medical data management node to manage medical data.

[0268] In one implementation, the first receiving module 701 is used to obtain the push result of the medical data through the second connection;

[0269] The first processing module 702 is used to re-push the medical data to the second node through the second connection based on the first data push service when the push result is a push failure; and output push failure information when the number of push failures is greater than or equal to a push number threshold.

[0270] In one implementation, the first receiving module 701 is configured to receive, through a second connection, state information of a second node sent by the second node; wherein the state information is sent by the second node at a specified frequency;

[0271] The first processing module 702 is configured to determine that the second node is in an unavailable state if no state information is received within a specified time.

[0272] In some implementations, the first processing module 702 is configured to determine first configuration information and second node identity information; wherein the first configuration information includes identity information of the second node that is allowed to access the first node;

[0273] The first receiving module 701 is configured to receive status information through a second connection when the second node identity information successfully matches the first configuration information.

[0274] It should be noted that in actual applications, the first receiving module 701, the first processing module 702 and the first pushing module 703 can be implemented using a processor in an electronic device, and the above-mentioned processor can be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, controller, microcontroller, and microprocessor.

[0275] From the above, it can be seen that in the first node 7 provided in the embodiment of the present application, the medical data generated by online diagnosis and treatment is stored in the first database, and at the same time, the medical data is extracted from the first database through the data extraction service and the medical data is stored in the second database, and the actual medical data push operation is performed on the medical data stored in the second database through the first data push service. Therefore, in the process of pushing medical data, the first node 7 provided in the embodiment of the present application realizes the isolation of the medical data storage database and the medical data push database under the premise of synchronization between the first database and the second database, that is, the decoupling between the medical data and the medical data to be pushed is realized; and, compared with the method of directly pushing the medical data in the first database to the medical data management center, the resource consumption of the first database is reduced, the blocking probability of medical data push and storage is reduced, and the robustness of the online smart medical service is improved.

[0276] Based on the aforementioned embodiments, the present application also provides a second first node. Figure 8 This is a schematic diagram of the structure of the second first node 7 provided in the embodiment of the present application. Figure 8 As shown, the first node 7 may include:

[0277] A first processor 801, a first memory 802 and a first communication bus 803; wherein:

[0278] A first communication bus 803, used to implement a communication connection between the first processor 801 and the first memory 802;

[0279] The first processor 801 is used to execute the computer program stored in the first memory 802 to implement the medical data push method applied to the first node as in any of the previous embodiments.

[0280] The first processor 801 may be at least one of an application specific integrated circuit ASIC, a DSP, a DSPD, a PLD, an FPGA, a CPU, a controller, a microcontroller, and a microprocessor. It is understandable that the electronic device used to implement the functions of the processor may also be other, which is not specifically limited in the embodiment of the present invention.

[0281] The first memory 802 may be a volatile memory, such as a RAM; or a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD); or a combination of the above types of memories, and provide instructions and data to the first processor 801.

[0282] Based on the above embodiments, the embodiments of the present application provide a first second node. A second connection is established between the second node and the first node; the medical data is obtained by the first node from the second database and pushed to the second node through the second connection based on the first data push service; the medical data in the second database is obtained by the first node from the first database through the first connection based on the data extraction service; the first node has a first connection with the first database and a second connection with the second node; the first node is at least deployed with the data extraction service and the first data push service; the first database stores medical data generated by online diagnosis and treatment.

[0283] Fig. 9 This is a schematic diagram of the structure of the first second node 9 provided in the embodiment of the present application. Fig. 9 As shown, the second node 9 includes: a second receiving module 901 and a second pushing module 902; wherein:

[0284] A second receiving module 901, configured to receive medical data sent by the first node through a second connection;

[0285] The second pushing module 902 is used to push the medical data to the medical data management node.

[0286] In one embodiment, the second node is deployed with a data high availability service and a second data push service; a third connection is established between the second node and the medical data management node; the second node 9 also includes a second processing module; wherein:

[0287] A second processing module is used to determine a target data push service from the second data push service based on the data high availability service when the medical data is received;

[0288] The second push module is used to push the medical data to the medical data management node through the third connection based on the target data push service.

[0289] In one embodiment, the second processing module is used to determine the second configuration information and the identity information of the first node; wherein the second configuration information includes the identity information of the first node that is allowed to access the second node;

[0290] The second receiving module 901 is used to receive the medical data pushed by the first node through the second connection when the identity information of the first node matches the second configuration information successfully.

[0291] In one implementation, the second receiving module is configured to send the status information of the second node to the first node via the second connection at a specified frequency.

[0292] It should be noted that in actual applications, the second receiving module 901, the second processing module and the second pushing module 902 can be implemented using a processor in an electronic device, and the above-mentioned processor can be at least one of ASIC, DSP, DSPD, PLD, FPGA, CPU, controller, microcontroller, and microprocessor.

[0293] From the above, it can be seen that the medical data received by the second node 9 provided in the embodiment of the present application is pushed by the first node, and the medical data pushed by the first node is obtained from the second database, and the medical data in the second database is extracted from the first database by the data extraction service in the first node and the medical data is stored in the second database. The medical data pushed by the first node is obtained from the second database and pushed to the second node by the first data push service. After the second node receives the medical data, it pushes the medical data to the medical data management node. In this way, the first node realizes the decoupling between the medical data generated by the online diagnosis and treatment in real time and the medical data to be pushed by storing the medical data generated by the online diagnosis and treatment in two databases respectively, thereby reducing the data reading and writing pressure of the first database caused by data push based on the first database, and also reducing the risk of medical data push.

[0294] Based on the above embodiments, the present application embodiment provides a second second node 9, Fig.10 This is a schematic diagram of the structure of the second second node 9 provided in the embodiment of the present application. Fig.10 As shown, the second node 9 may include: a second processor 1001, a second memory 1002 and a second communication bus 1003; wherein:

[0295] The second communication bus 1003 is used to implement a communication connection between the second processor 1001 and the second memory 1002;

[0296] The second processor 1001 is used to execute the computer program stored in the second memory 1002 to implement the medical data push method applied to the second node as described in any of the previous embodiments.

[0297] The second processor 1001 may be at least one of an application specific integrated circuit ASIC, a DSP, a DSPD, a PLD, an FPGA, a CPU, a controller, a microcontroller, and a microprocessor. It is understandable that the electronic device used to implement the functions of the processor may also be other, which is not specifically limited in the embodiment of the present invention.

[0298] The second memory 1002 may be a volatile memory, such as a RAM; or a non-volatile memory, such as a ROM, a flash memory, a HDD or a SSD; or a combination of the above types of memories, and provide instructions and data to the second processor 1001.

[0299] Based on the foregoing embodiments, the present application also provides a medical data push system 11. Fig.11This is a schematic diagram of the structure of the medical data push system 11 provided in the embodiment of the present application. Fig.11 As shown, the medical data push system 11 includes the first node 7 as described in any of the previous embodiments, and the second node 9 as described in any of the previous embodiments.

[0300] Based on the description of the foregoing embodiments, it can be seen that the medical data push system 11 provided in the embodiments of the present application can achieve low coupling of medical data, high availability of medical data push services, and can also make the push of medical data safer and more compliant.

[0301] Based on the foregoing embodiments, the embodiments of the present application also provide a computer-readable storage medium, in which a computer program is stored to implement the medical data push method applied to the first node or the medical data push method applied to the second node as described in any of the foregoing.

[0302] The above description of various embodiments tends to emphasize the differences between the various embodiments. The same or similar aspects can be referenced to each other, and for the sake of brevity, they will not be repeated herein.

[0303] The methods disclosed in the various method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0304] The features disclosed in the various product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0305] The features disclosed in the various method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.

[0306] It should be noted that the above-mentioned computer-readable storage medium can be ROM, programmable read-only memory (Programmable Read-Only Memory, PROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), magnetic random access memory (Ferromagnetic Random Access Memory, FRAM), flash memory (Flash Memory), magnetic surface memory, optical disk, or compact disc read-only memory (CD-ROM) and other memories; it can also be various electronic devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0307] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0308] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0309] 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 necessary general hardware nodes, 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.

[0310] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0311] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0312] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0313] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A medical data push method, characterized in that: The method is applied to a first node, wherein the first node is at least deployed with a data extraction service and a first data push service; the first node is connected to a first database and is connected to a second node; The first database stores medical data generated by online diagnosis and treatment; the method comprises: Based on the data extraction service, extracting the medical data from the first database through the first connection, and storing the medical data in a second database; Based on the first data push service, acquiring the medical data from the second database; Based on the first data push service, the medical data is pushed to the second node through the second connection; the second node is used to push the medical data to the medical data management node; The pushing of the medical data to the second node through the second connection based on the first data push service includes: Verifying the medical data; When the medical data verification passes, based on the first data push service, the medical data is pushed to the second node through the second connection; The verifying of the medical data includes: Acquire medical data management rules; wherein the medical data management rules represent rules for the medical data management node to manage the medical data; Based on the medical data management rules, the medical data is verified.

2. The method according to claim 1, characterized in that The extracting the medical data from the first database through the first connection based on the data extraction service includes: Acquire the update frequency of the medical data in the first database; When the update frequency is less than a frequency threshold, the medical data is extracted from the first database through the first connection based on the data extraction service.

3. The method according to claim 1, characterized in that The method further comprises: Obtaining, through the second connection, a push result of the medical data; When the push result is a push failure, based on the first data push service, the medical data is pushed to the second node again through the second connection; When the number of push failures is greater than or equal to the push number threshold, push failure information is output.

4. The method according to claim 1, characterized in that The method further comprises: receiving, through the second connection, state information of the second node sent by the second node; wherein the state information is sent by the second node at a specified frequency; If the status information is not received within a specified time, it is determined that the second node is in an unavailable state.

5. The method according to claim 4, characterized in that The receiving, through the second connection, the state information of the second node sent by the second node includes: Determine first configuration information and second node identity information; wherein the first configuration information includes identity information of a second node that is allowed to access the first node; In a case where the second node identity information successfully matches the first configuration information, the state information is received through the second connection.

6. A medical data push method, characterized in that: The method is applied to a second node; a second connection is established between the second node and the first node; the medical data is obtained by the first node from a second database and pushed to the second node through the second connection based on a first data push service; the medical data in the second database is obtained by the first node from the first database through the first connection based on a data extraction service; the first node has the first connection established with the first database and the second connection established with the second node; the first node is at least deployed with the data extraction service and the first data push service; The first database stores the medical data generated by online diagnosis and treatment; the method comprises: Receiving the medical data pushed by the first node through the second connection; wherein the medical data is pushed when the medical data is verified based on the medical data management rule; The medical data is pushed to a medical data management node.

7. The method according to claim 6, characterized in that The second node is deployed with a data high availability service and a second data push service; A third connection is established between the second node and the medical data management node; and pushing the medical data to the medical data management node includes: Upon receiving the medical data, determining a target data push service from the second data push services based on the data high availability service; Based on the target data push service, the medical data is pushed to the medical data management node through the third connection.

8. The method according to claim 6, characterized in that The receiving, through the second connection, the medical data pushed by the first node includes: Determine second configuration information and first node identity information; wherein the second configuration information includes identity information of the first node that is allowed to access the second node; When the first node identity information successfully matches the second configuration information, the medical data pushed by the first node is received through the second connection.

9. The method according to claim 6, characterized in that The method further comprises: The status information of the second node is sent to the first node at a specified frequency through the second connection; wherein, if the first node does not receive the status information within a specified time, it can be determined that the second node is in an unavailable state.

10. A first node, characterized in that: The first node is at least deployed with a data extraction service and a first data push service; the first node has a first connection established with a first database and a second connection established with a second node; the first database stores medical data generated by online diagnosis and treatment; The second node is used to push the medical data to the medical data management node; the first node includes a first receiving module, a first processing module and a first pushing module; wherein: The first receiving module is used to extract the medical data from the first database through the first connection based on the data extraction service; The first processing module is used to store the medical data in a second database; The first push module is used to push the medical data to the second node through the second connection based on the first data push service; The pushing of the medical data to the second node through the second connection based on the first data push service includes: Verifying the medical data; When the medical data verification passes, based on the first data push service, the medical data is pushed to the second node through the second connection; The verifying of the medical data includes: Acquire medical data management rules; wherein the medical data management rules represent rules for the medical data management node to manage the medical data; Based on the medical data management rules, the medical data is verified.

11. A first node, characterized in that: The first node includes a first processor, a first memory and a first communication bus; wherein: The first communication bus is used to implement a communication connection between the first processor and the first memory; The first processor is used to execute the computer program stored in the first memory to implement the medical data push method applied to the first node as described in any one of claims 1 to 5.

12. A second node, characterized in that: A second connection is established between the second node and the first node; the medical data is obtained by the first node from the second database and pushed to the second node through the second connection based on the first data push service; the medical data in the second database is obtained by the first node from the first database through the first connection based on the data extraction service; the first node has the first connection established with the first database and the second connection established with the second node; the first node is at least deployed with the data extraction service and the first data push service; the first database stores the medical data generated by online diagnosis and treatment; The second node includes a second receiving module and a second pushing module; wherein: The second receiving module is used to receive the medical data sent by the first node through the second connection; wherein the medical data is pushed when the medical data is verified based on the medical data management rule; The second pushing module is used to push the medical data to a medical data management node.

13. A second node, characterized in that: The second node comprises: a second processor, a second memory and a second communication bus; wherein: The second communication bus is used to realize the communication connection between the second processor and the second memory; The second processor is used to execute the computer program stored in the second memory to implement the medical data push method applied to the second node as described in any one of claims 6 to 9.

14. A medical data push system, characterized in that: The medical data push system comprises the first node as described in any one of claims 10 to 11, and the second node as described in any one of claims 12 to 13.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program to implement the medical data pushing method as described in any one of claims 1 to 5 or 6 to 9.

Images