A medical data processing method and device

Abstract

The application discloses a medical data processing method and device, and relates to the technical field of Internet medical treatment. A specific embodiment of the method comprises the following steps: obtaining first medical data from a private domain server, and obtaining second medical data from a target public domain server; determining first target data corresponding to the private domain server and second target data corresponding to the target public domain server according to the activity degrees of the first medical data and the second medical data; determining to-be-synchronized data from the first medical data according to the matching relationship between the second target data and the first medical data and the first target data; and synchronizing the to-be-synchronized data to the target public domain server. Thus, the medical product data with high activity degrees in the private domain server and the public domain server can be integrated and shared, so that the medical product data with high activity degrees in the private domain server and the public domain server can be uniformly managed, and the value of the medical product can be more fully tapped and utilized.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet medical treatment, and in particular to a medical data processing method and device. BACKGROUND

[0002] In the context of medical health, a public platform refers to an Internet hospital relying on social public traffic, and a private platform refers to an Internet hospital established by an entity hospital, the main traffic of which comes from offline patients of the hospital or online patients of the hospital.

[0003] Generally, the traffic of a public platform is huge, and the supply of high-quality medical resources (for example, high user attention, good sales of drug services, diagnosis and treatment services, etc.) of the public platform is slightly insufficient, which cannot fully guarantee the service quality. In comparison, due to the limited traffic of most private platforms, many high-quality medical resources of the private platforms cannot be fully utilized.

[0004] In the implementation process of the present application, the inventors have found that at least the following problems exist in the related art:

[0005] The medical resources of the public platform and the private platform exist in different data systems respectively, so that the high-quality medical resources of the two platforms cannot be integrated, resulting in a low overall utilization rate of resources. SUMMARY

[0006] Therefore, the present application provides a medical data processing method and device, which obtains first medical data from one or more private servers, and obtains second medical data from a target public server; determines first target data corresponding to the one or more private servers and second target data corresponding to the target public server according to the activity of medical products corresponding to the first medical data and the second medical data; determines to-be-synchronized data from the first medical data according to the matching between the second target data and the first medical data and the first target data; and synchronizes the to-be-synchronized data to the target public server. In this way, the medical product data with high activity in the private server and the public server is integrated and shared, so that the medical product data with high activity in the private server and the public server is uniformly managed, and the value of the medical product can be more fully tapped and utilized.

[0007] To achieve the above object, according to one aspect of the present application, a medical data processing method is provided.

[0008] The medical data processing method of the embodiment includes: obtaining first medical data from one or more private domain servers respectively, and obtaining second medical data from a target public domain server; determining first target data corresponding to the one or more private domain servers respectively and second target data corresponding to the target public domain server according to the activity of medical products corresponding to the first medical data and the second medical data respectively; determining to-be-synchronized data from the first medical data according to the matching between the second target data and the first medical data and the first target data; and synchronizing the to-be-synchronized data to the target public domain server.

[0009] Optionally, the determining of the first target data corresponding to the one or more private domain servers respectively and the second target data corresponding to the target public domain server according to the activity of medical products corresponding to the first medical data and the second medical data respectively includes: determining the activity of medical products corresponding to the first medical data and the second medical data according to one or more of the click situation, the browsing situation, the consultation situation, and the order generation situation of medical products corresponding to the one or more private domain servers and the target public domain server respectively; taking the first medical data corresponding to a medical product with an activity greater than a preset first threshold as the first target data, and taking the second medical data corresponding to a medical product with an activity greater than a preset second threshold as the second target data.

[0010] Optionally, the second target data and the first medical data both include medical product labels, and the determining of the to-be-synchronized data from the first medical data according to the matching between the second target data and the first medical data and the first target data includes: for the first medical data obtained from each private domain server: matching a second product label in the second target data with a first product label in the first medical data; and determining to-be-synchronized data from the first medical data according to the matching result and the first target data respectively.

[0011] Optionally, the determining of the to-be-synchronized data from the first medical data according to the matching result and the first target data includes: in a case where the second product label and the first product label are all successfully matched, determining medical data matched with the second product label from the first medical data; and taking the union of the medical data matched with the second product label in the first medical data and the first target data as the to-be-synchronized data.

[0012] Optionally, the determining the to-be-synchronized data from the first medical data according to the matching result and the first target data further includes: in a case where the second product labels do not all match the first product labels successfully, determining, from the second target data, second product labels that do not match the first product labels successfully; generating new data corresponding to the second product labels that do not match the first product labels successfully according to the second product labels that do not match the first product labels successfully; and taking a union of medical data corresponding to the second product labels that match the first product labels successfully in the first medical data, the first target data, and the new data as the to-be-synchronized data.

[0013] Optionally, the method provided in the present application further includes: obtaining, from the target public server, data synchronization strategies corresponding to the one or more private servers respectively, the data synchronization strategies corresponding to the one or more private servers respectively being not completely same; the data synchronization strategies indicating drug information and / or diagnosis and treatment information allowed to be synchronized by the target public server; determining, from the to-be-synchronized data corresponding to the one or more private servers respectively, target synchronization data conforming to the data synchronization strategies according to the data synchronization strategies; and synchronizing the target synchronization data to the target public server respectively.

[0014] Optionally, before the to-be-synchronized data is synchronized to the target public server, the method provided in the present application further includes: marking the to-be-synchronized data corresponding to the one or more private servers respectively with sources, so that the to-be-synchronized data corresponding to different private servers respectively correspond to different private domain marks.

[0015] To achieve the above object, according to a further aspect of the embodiments of the present application, a medical data processing device is provided.

[0016] The medical data processing device provided in the embodiments of the present application includes: a data acquisition module, configured to acquire first medical data from one or more private servers respectively, and acquire second medical data from a target public server; a data screening module, configured to determine first target data corresponding to the one or more private servers respectively and second target data corresponding to the target public server according to activity degrees of medical products corresponding to the first medical data and the second medical data respectively; a data determination module, configured to determine to-be-synchronized data from the first medical data according to a matching condition between the second target data and the first medical data and the first target data; and a data synchronization module, configured to synchronize the to-be-synchronized data to the target public server.

[0017] To achieve the above object, according to a further aspect of the embodiments of the present application, a server is provided.

[0018] A server according to an embodiment of the present application includes one or more processors; and a storage device storing one or more programs, which when executed by the one or more processors, cause the one or more processors to implement a medical data processing method according to an embodiment of the present application.

[0019] To achieve the above object, according to another aspect of the present application, a computer readable storage medium is provided.

[0020] A computer readable storage medium according to an embodiment of the present application has a computer program stored thereon, which when executed by a processor, implements a medical data processing method according to an embodiment of the present application.

[0021] An embodiment of the above invention has the following advantages or beneficial effects: by obtaining first medical data from one or more private domain servers respectively, and obtaining second medical data from a target public domain server; determining first target data corresponding to the one or more private domain servers respectively, and second target data corresponding to the target public domain server, according to the activity of the medical products corresponding to the first medical data and the second medical data respectively; determining the to-be-synchronized data from the first medical data according to the matching between the second target data and the first medical data, and the first target data; synchronizing the to-be-synchronized data to the target public domain server. Thus, the medical product data with high activity in the private domain server and the public domain server is integrated and shared, so that the medical product data with high activity in the private domain server and the public domain server is uniformly managed, and the value of the medical product can be more fully mined and utilized.

[0022] The further effects of the above non-conventional optional mode will be described in the following combined with the specific embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0023] The accompanying drawings are used to better understand the present application, and do not constitute an improper limitation on the present application. Among them:

[0024] Figure 1 is a schematic diagram of the main steps of a medical data processing method according to an embodiment of the present application;

[0025] Figure 2 is a schematic diagram of the main steps of determining the to-be-synchronized data of a medical data processing method according to an embodiment of the present application;

[0026] Figure 3 is a schematic diagram of the main steps of a medical data processing method according to an embodiment of the present application;

[0027] Figure 4is a schematic diagram of main modules of a medical data processing apparatus according to an embodiment of the present application;

[0028] Figure 5 is an exemplary system architecture diagram in which embodiments of the present application can be applied;

[0029] Figure 6 is a structural schematic diagram of a computer system of a terminal device or a server suitable for implementing embodiments of the present application. DETAILED DESCRIPTION

[0030] Exemplary embodiments of the present application are described below with reference to the accompanying drawings, which include various details of the embodiments of the present application to assist in understanding, which should be considered in their context only. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Also, for the sake of clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0031] It should be noted that in the technical solutions of the present disclosure, the collection, collection, update, analysis, processing, use, transmission, storage, etc. of user personal information involved in the technical solutions comply with relevant laws and regulations, are used for legal purposes, and do not violate public order and good customs. Necessary measures are taken to prevent illegal access to user personal information data, and to maintain user personal information security, network security and national security.

[0032] Embodiments of the present application can be related to Internet medical care, smart medical care, medical supply chain and other scenarios.

[0033] It should be noted that in the case of no conflict, the embodiments of the present application and the technical features in the embodiments can be combined with each other.

[0034] Figure 1 is a schematic diagram of main steps of a medical data processing method according to an embodiment of the present application.

[0035] As shown in Figure 1 , the medical data processing method of the present application mainly includes the following steps:

[0036] Step S101: obtaining first medical data from one or more private domain servers respectively, and obtaining second medical data from a target public domain server.

[0037] In the embodiments of the present application, the private domain server is a special computer providing data storage and processing and other background support services for the private domain Internet medical platform (referred to as the private domain platform); the public domain server is a special computer providing data storage and processing and other background support services for the public domain Internet medical platform (referred to as the public domain platform); the private domain platform is a private domain Internet medical platform that intends to enter the public domain platform; the target public domain platform is a public domain Internet medical platform that can accept the entry of the private domain platform; and the target public domain server refers to a special computer providing data storage and processing and other background support services for a public domain Internet medical platform that can accept the entry of the private domain platform.

[0038] In order to realize the sharing of medical resources of the public domain platform and the private domain platform, in the case of obtaining the authorization of the private domain Internet medical platform, the medical data of the private domain Internet platform is obtained from the private domain server, and the obtained medical data of the private domain platform is synchronized to the target public domain platform, i.e., to the public domain server, thereby realizing the sharing of medical resources of the public domain platform and the private domain platform. However, in order to make the medical resources of the public domain platform and the private domain platform realize resource sharing while highlighting the advantages of complementation, it is necessary to analyze and screen the medical resources of the public domain platform and the private domain platform, determine the high-quality medical resources of the public domain platform and the private domain platform according to the preference of users for the medical resources of the two platforms, and integrate the high-quality medical resources, thereby realizing the sharing of high-quality medical resources of the public domain platform and the private domain platform.

[0039] Under the authorization of a plurality of private domain platforms, the medical data of the plurality of private domain platforms is obtained, and the medical data includes drug service data and doctor diagnosis service data; under the authorization of a target public domain platform, the medical data of the target public domain platform is obtained, and the medical data also includes drug service data and doctor diagnosis service data.

[0040] Step S102: determining the first target data corresponding to the one or more private domain servers and the second target data corresponding to the target public domain server according to the activity degrees of the medical products corresponding to the first medical data and the second medical data.

[0041] According to the clicking, browsing, consulting and order generation of the medical products in the public domain platform and the private domain platform, the first target data corresponding to the medical products with high activity degrees in the private domain platform and the second target data corresponding to the medical products with high activity degrees in the public domain platform can be determined, and the medical products with high activity degrees refer to the medical products with high preference degrees (high clicking amount, browsing amount and consulting amount), which are referred to as high-quality medical resources in the embodiments of the present application.

[0042] In an embodiment of the present application, the determining of the first target data corresponding to the one or more private domain servers and the second target data corresponding to the target public domain server according to the activity of the medical products corresponding to the first medical data and the second medical data respectively comprises: determining the activity of the medical products corresponding to the first medical data and the second medical data according to one or more of the click situation, the browsing situation, the consultation situation and the order generation situation of the medical products corresponding to the one or more private domain servers and the target public domain server respectively; taking the first medical data corresponding to the medical product with an activity greater than a preset first threshold as the first target data, and taking the second medical data corresponding to the medical product with an activity greater than a preset second threshold as the second target data.

[0043] According to the click, browsing, consultation and / or order generation situation of the medical products respectively, such as daily click volume, daily browsing volume, daily consultation volume and / or daily order volume, the product activity of the medical data is determined respectively, such as setting the weight of the daily click volume, the daily browsing volume, the daily consultation volume and the daily order volume as 0.1, 0.3, 0.6 and 1 respectively, and in the case of calculating the product activity according to the daily click volume, the daily browsing volume, the daily consultation volume and the daily order volume, the product activity is daily click volume*0.1+daily browsing volume*0.3+daily consultation volume*0.6+daily order volume*1. It can be understood that the product activity can be calculated according to any one or more of the daily click volume, the daily browsing volume, the daily consultation volume and the daily order volume. In addition, it can be understood that the weight of the daily click volume, the daily browsing volume, the daily consultation volume and the daily order volume can be set according to actual needs.

[0044] In the case of determining the product activity of the medical data respectively, a preset threshold is set, and the medical data with a product activity higher than the preset threshold is determined as the medical data with a higher product activity, i.e. the first target data corresponding to the private domain platform data and the second target data corresponding to the public domain platform data. It can be understood that the preset threshold can be set according to the traffic situation of the platform, and generally, the higher the traffic, the higher the preset threshold.

[0045] Step S103: determining the to-be-synchronized data from the first medical data according to the matching situation between the second target data and the first medical data and the first target data.

[0046] In the case that the first target data of the private domain platform product with high activity and the second target data of the public domain platform product with high activity have been determined, the medical data to be synchronized to the public domain platform is determined from the medical data of the private domain platform. The first target data with high user preference in the private domain platform can be directly used as part of the to-be-synchronized data. Then, according to the second target data with high user preference in the public domain platform, a part of the medical data of the private domain platform is selected as another part of the to-be-synchronized data. Finally, in the case that the second target data with high user preference in the public domain platform does not exist in the private domain platform, the medical data corresponding to the second target data can be generated in the private domain platform, and the generated medical data is also used as part of the to-be-synchronized data.

[0047] In an embodiment of the present application, the second target data and the first medical data both include medical product labels, and the determining of the to-be-synchronized data from the first medical data according to the matching between the second target data and the first medical data and the first target data includes: for the first medical data obtained from each private domain server: matching the second product label in the second target data with the first product label in the first medical data; and determining the to-be-synchronized data from the first medical data according to the matching result and the first target data.

[0048] The first target data can be directly used as part of the to-be-synchronized data, and the other to-be-synchronized data can be determined from the first medical data according to the second target data. The medical product labels included in the second target data and the first medical data can refer to drug service labels or diagnosis and treatment service labels. The medical product labels corresponding to the second target data with high product activity in the public domain platform are matched with the medical product labels of the first medical data of the private domain platform. If the matching is successful, it indicates that the drug service or diagnosis and treatment service exists in the private domain platform, and the medical data corresponding to the medical product labels that match successfully in the first medical data is used as part of the to-be-synchronized data. If the matching is unsuccessful, new data corresponding to the medical product label that does not match successfully in the second target data is generated, and the generated new data is also used as part of the to-be-synchronized data.

[0049] In an embodiment of the present application, the determining of the to-be-synchronized data from the first medical data according to the matching result and the first target data includes: in the case that the second product label and the first product label are all matched successfully, determining the medical data matched with the second product label from the first medical data; and using the medical data matched with the second product label in the first medical data and the union of the first target data as the to-be-synchronized data.

[0050] In a case where the second product labels in the second target data are all successfully matched with the first product labels in the first medical data, medical data corresponding to the medical product labels that are successfully matched in the first medical data is merged with the first target data, and a union of the two is the to-be-synchronized data to be synchronized to the public platform.

[0051] In an embodiment of the present application, the determining the to-be-synchronized data from the first medical data according to the matching result and the first target data further includes: in a case where the second medical product labels are not all successfully matched with the first product labels, determining second product labels that are not successfully matched from the second target data; generating new data corresponding to the second product labels that are not successfully matched according to the second product labels; and taking a union of the medical data corresponding to the second product labels that are successfully matched in the first medical data, the first target data, and the new data as the to-be-synchronized data.

[0052] In a case where the second product labels in the second target data are partially successfully matched with the first product labels in the first medical data, medical data corresponding to the medical product labels that are successfully matched in the first medical data is taken as another part of the to-be-synchronized data; new medical data corresponding to the medical product labels that are not successfully matched in the second target data is generated, and the new medical data belongs to the private platform. The first target data, the first medical data corresponding to the medical product labels that are successfully matched, and the new medical data are merged, and a union of the three is taken as the to-be-synchronized data to be synchronized to the public platform.

[0053] Figure 2 FIG. 1 is a schematic diagram of main steps of determining the to-be-synchronized data according to the medical data processing method of an embodiment of the present application.

[0054] As shown in FIG. 2, the medical data processing method of an embodiment of the present application mainly includes the following steps: Figure 2

[0055] Step S201: obtaining first medical data of a private domain server and second medical data of a public domain server.

[0056] Step S202: calculating activity degrees of medical products corresponding to the first medical data and the second medical data, respectively.

[0057] Step S203: determining first target data and second target data corresponding to medical products with activity degrees greater than a preset threshold, respectively.

[0058] Step S204: determining whether medical product labels of each second target data and the first medical data are matched, if yes, performing step S205; if no, performing step S206.​

[0059] Step S205: Taking the union of the first target data and the second target data, and performing step S208.

[0060] Step S206: Generating new data according to the medical product label of the second target data.

[0061] Step S207: Taking the union of the first target data and the new data.

[0062] Step S208: Obtaining the to-be-synchronized data.

[0063] The above is a simple summary of the process of determining the to-be-synchronized data in the embodiments of the present application, and the explanations of the terms involved can refer to the detailed description of the method.

[0064] Step S104: Synchronizing the to-be-synchronized data to the target public server.

[0065] In an embodiment of the present application, the method further comprises: obtaining, from the target public server, data synchronization strategies respectively corresponding to the one or more private servers, the data synchronization strategies respectively corresponding to the one or more private servers being not completely same; the data synchronization strategies indicating drug information and / or diagnosis and treatment information allowed to be synchronized by the target public server; determining, according to the data synchronization strategies, target synchronization data respectively conforming to the data synchronization strategies from the to-be-synchronized data respectively corresponding to the one or more private servers; and synchronizing the target synchronization data respectively to the target public server.

[0066] In order to avoid the medical resources of multiple private platforms from forming fierce homogenization competition in the public platform, different data synchronization strategies can be formulated for different private platforms, so that the drug services or diagnosis and treatment services of different private platforms synchronized to the public platform have a certain degree of difference. For example, drug 1, 2, 3 and diagnosis and treatment service department 1, 2, 3 of private platform A, drug 4, 5, 6 and diagnosis and treatment service department 4, 5, 6 of private platform B, and drug 7, 8, 9 and diagnosis and treatment service department 7, 8, 9 of private platform C are allowed to be synchronized to the public platform. It can be understood that this example is only one of the data synchronization strategies, but is not limited thereto, and the medical services provided by the private platforms can have a certain degree of overlap. It should be noted that the drugs in the embodiments of the present application can include not only products for treating diseases, but also products having health care and tonifying effects on the body, such as vitamin C tablets, protein powder, etc. It should be further noted that the diagnosis and treatment services can be divided according to the qualifications of doctors in addition to being divided according to departments. The drug information and diagnosis and treatment information in the data synchronization strategy correspond to the drug services and diagnosis and treatment services indicated by the medical product label in the to-be-synchronized data.

[0067] In an embodiment of the present application, the method further comprises: before synchronizing the to-be-synchronized data to the target public domain server, respectively marking the to-be-synchronized data corresponding to the one or more private domain servers with sources, so that the to-be-synchronized data corresponding to different private domain servers correspond to different private domain marks respectively.

[0068] After the medical resources of the public domain platform and the private domain platform are integrated, in order to make the public domain platform users have a clear understanding of the source of the medical service they will purchase, the source mark of the medical service can be displayed on the public domain platform. In order to realize the medical service source mark, before synchronizing the to-be-synchronized data to the public domain platform, mark the to-be-synchronized data with a source mark, such as marking the to-be-synchronized data of the private domain platform A as private A, and marking the to-be-synchronized data of the private domain platform B as private B. After data synchronization, on the public domain platform, when a user sees a medical service marked as private A, it can be known that the medical service is provided by the private domain platform A.

[0069] Figure 3 is a schematic diagram of the main steps of the medical data processing method according to an embodiment of the present application.

[0070] As shown in Figure 3 , the medical data processing method according to an embodiment of the present application mainly comprises the following steps:

[0071] Step S301: acquiring first medical data from one or more private domain servers respectively, and acquiring second medical data from a target public domain server.

[0072] Under the authorization of a plurality of private domain platforms, medical data of the plurality of private domain platforms is acquired, and the medical data includes drug service data and doctor diagnosis service data; under the authorization of a target public domain platform, medical data of the target public domain platform is acquired, and the medical data also includes drug service data and doctor diagnosis service data.

[0073] Step S302: determining first target data corresponding to the one or more private domain servers respectively, and second target data corresponding to the target public domain server.

[0074] According to the clicking, browsing, consulting and order generation of the medical products in the public domain platform and the private domain platform, the first target data with higher product activity of the private domain platform and the second target data with higher product activity of the public domain platform can be determined. The medical data with higher product activity corresponds to the medical product with higher user preference, that is, the high-quality medical resource in the embodiment of the present application.

[0075] Step S303: determining the to-be-synchronized data from the first medical data according to the matching between the second target data and the first medical data and the first target data.

[0076] The first target data with a high degree of favor of users in the private domain platform can be directly used as part of the to-be-synchronized data. Then, according to the second target data with a high degree of favor of users in the public domain platform, a part of medical data in the private domain platform is selected as another part of the to-be-synchronized data. Finally, if the second target data with a high degree of favor of users in the public domain platform does not exist in the private domain platform, medical data corresponding to the second target data can be generated in the private domain platform, and the generated medical data is also used as part of the to-be-synchronized data.

[0077] Step S304: obtaining, from the target public domain server, data synchronization strategies corresponding to the plurality of private domain servers.

[0078] The data synchronization strategies corresponding to the one or more private domain platforms are not completely same in order to make the drug services or diagnosis and treatment services synchronized from different private domain platforms to the public domain platform have a certain degree of difference. The data synchronization strategy indicates the drug information and / or diagnosis and treatment information allowed to be synchronized by the target public domain platform.

[0079] Step S305: determining target synchronization data meeting the data synchronization strategy according to the data synchronization strategy.

[0080] Different data synchronization strategies are formulated for different private domain platforms, such as allowing drug 1, 2, and 3 and diagnosis and treatment service departments 1 and 2 of the private domain platform A, drug 4, 5, and 6 and diagnosis and treatment service departments 4 and 5 of the private domain platform B, and drug 7, 8, and 9 and diagnosis and treatment service departments 7 and 8 of the private domain platform C to be synchronized to the public domain platform. According to the data synchronization strategy, target synchronization data meeting the data synchronization strategy is determined from the to-be-synchronized data corresponding to the one or more private domain platforms.

[0081] Step S306: respectively marking the to-be-synchronized data corresponding to the one or more private domain servers with sources.

[0082] Before the to-be-synchronized data is synchronized to the public domain platform, the to-be-synchronized data is marked with a source mark, such as marking the to-be-synchronized data of the private domain platform A as private A and marking the to-be-synchronized data of the private domain platform B as private B. After data synchronization, on the public domain platform, a user can know that the medical service marked as private A is provided by the private domain platform A.

[0083] Step S307: synchronizing the marked to-be-synchronized data to the target public server.

[0084] After the to-be-synchronized data is synchronized to the target public platform, on the public platform, the user sees the medical service marked as private A, and can know that the medical service is provided by the private platform A.

[0085] According to the medical data processing method of the embodiment of the application, the first medical data is obtained from one or more private servers, and the second medical data is obtained from a target public server. According to the activity of the medical products corresponding to the first medical data and the second medical data, the first target data corresponding to the one or more private servers and the second target data corresponding to the target public server are determined. According to the matching between the second target data and the first medical data and the first target data, the to-be-synchronized data is determined from the first medical data. The to-be-synchronized data is synchronized to the target public server. Thus, the medical product data with high activity in the private server and the public server is integrated and shared, so that the medical product data with high activity in the private server and the public server is uniformly managed, and the value of the medical product can be more fully mined and utilized.

[0086] Figure 4 is a schematic diagram of the main modules of the medical data processing device according to the embodiment of the application.

[0087] As shown in Figure 4 , the medical data processing device 400 of the embodiment of the application comprises:

[0088] The data acquisition module 401 is configured to obtain first medical data from one or more private servers and obtain second medical data from a target public server.

[0089] The data filtering module 402 is configured to determine first target data corresponding to the one or more private servers and second target data corresponding to the target public server according to the activity of the medical products corresponding to the first medical data and the second medical data.

[0090] The data determination module 403 is configured to determine to-be-synchronized data from the first medical data according to the matching between the second target data and the first medical data and the first target data.

[0091] The data synchronization module 404 is configured to synchronize the to-be-synchronized data to the target public server.

[0092] In an embodiment of the present application, the data screening module 402 is further configured to determine, according to one or more of click conditions, browsing conditions, consultation conditions, and order generation conditions of medical products corresponding to the one or more private domain servers and the target public domain server respectively, activity degrees of the medical products corresponding to the first medical data and the second medical data respectively; and determine, as the first target data, the first medical data corresponding to a medical product whose activity degree is greater than a preset first threshold, and determine, as the second target data, the second medical data corresponding to a medical product whose activity degree is greater than a preset second threshold.

[0093] In an embodiment of the present application, the data determination module 403 is further configured to, in a case where the second target data and the first medical data both contain medical product labels, for the first medical data obtained from each private domain server: match a second product label in the second target data with a first product label in the first medical data; and determine, according to a matching result and the first target data, to-be-synchronized data from the first medical data respectively.

[0094] In an embodiment of the present application, the data determination module 403 is further configured to, in a case where the second product label and the first product label are all successfully matched, determine, from the first medical data, medical data matched with the second product label; and determine, as the to-be-synchronized data, a union of the medical data matched with the second product label in the first medical data and the first target data.

[0095] In an embodiment of the present application, the data determination module 403 is further configured to, in a case where the second product label and the first product label are not all successfully matched, determine, from the second target data, a second product label that is not successfully matched; generate, according to the second product label that is not successfully matched, new data corresponding to the second product label; and determine, as the to-be-synchronized data, a union of medical data corresponding to the second product label that is successfully matched in the first medical data, the first target data, and the new data.

[0096] In an embodiment of the present application, the data synchronization module 404 is further configured to obtain, from the target public domain server, data synchronization strategies corresponding to the one or more private domain servers respectively, the data synchronization strategies corresponding to the one or more private domain servers respectively being not completely same; the data synchronization strategies indicating drug information and / or diagnosis and treatment information allowed to be synchronized by the target public domain server; determine, according to the data synchronization strategies, target synchronization data that conforms to the data synchronization strategies from the to-be-synchronized data corresponding to the one or more private domain servers respectively; and synchronize the target synchronization data to the target public domain server respectively.

[0097] In an embodiment of the present application, the data synchronization module 404 is further configured to mark the to-be-synchronized data corresponding to the one or more private domain servers respectively with different private domain marks before synchronizing the to-be-synchronized data to the target public domain server.

[0098] According to the medical data processing apparatus provided in the embodiments of the present application, the first medical data is acquired from the one or more private domain servers respectively, and the second medical data is acquired from the target public domain server; the first target data corresponding to the one or more private domain servers and the second target data corresponding to the target public domain server are determined according to the activity levels of the medical products to which the first medical data and the second medical data correspond respectively; the to-be-synchronized data is determined from the first medical data according to the matching between the second target data and the first medical data and the first target data; and the to-be-synchronized data is synchronized to the target public domain server. Thus, the medical product data with high activity levels in the private domain servers and the public domain server can be integrated and shared, so that the medical product data with high activity levels in the private domain servers and the public domain server can be uniformly managed, and the value of the medical products can be more fully tapped and utilized.

[0099] Figure 5 An exemplary system architecture 500 to which the medical data processing method or the medical data processing apparatus provided in the embodiments of the present application can be applied is shown.

[0100] As shown in Figure 5 The system architecture 500 can include private domain servers 501, 502, 503, networks 504, 506, a data synchronization server 505, and a public domain server 507. The networks 504, 506 are media that provide communication links between the private domain servers 501, 502, 503, the data synchronization server 505, and the public domain server 507. The networks 504, 506 can include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

[0101] A user can use the data synchronization server 505 to interact with the private domain servers 501, 502, 503 and the public domain server 507 through the networks 504, 506 to receive or send medical data, etc. Various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. can be installed on the data synchronization server 505.

[0102] The data synchronization server 505 can be a server providing various services, for example, a background management server providing support for data synchronization of the private domain servers 501, 502, and 503 to the public domain server 507. The background management server can analyze and process the obtained medical data, and feed back the processing result (for example, to-be-synchronized data) to the public domain server 507.

[0103] It should be noted that the medical data processing method provided in the embodiments of the present application is generally executed by the data synchronization server 505, and correspondingly, the medical data processing apparatus is generally arranged in the data synchronization server 505.

[0104] It should be understood that, Figure 5 The number of networks and servers in the foregoing system is merely illustrative. According to the needs of implementation, there can be any number of terminal devices, networks, and servers.

[0105] Reference is made below to Figure 6 which shows a structural schematic diagram of a computer system 600 suitable for implementing the terminal device of the embodiments of the present application. Figure 6 The terminal device shown is merely an example, and should not bring any limitation to the functions and use range of the embodiments of the present application.

[0106] As shown in Figure 6 , the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes according to programs stored in a read-only memory (ROM) 602 or programs loaded from a storage portion 608 to a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the system 600 are also stored. The CPU 601, the ROM 602, and the RAM 603 are connected to each other through a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0107] The following components are connected to the I / O interface 605: an input portion 606 including a keyboard, a mouse, and the like; an output portion 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), and the like, and a speaker, and the like; a storage portion 608 including a hard disk, and the like; and a communication portion 609 including a network interface card such as a LAN card, a modem, and the like. The communication portion 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, and the like is mounted on the drive 610 as needed, so that a computer program read therefrom is installed in the storage portion 608 as needed.

[0108] In particular, the processes described above with reference to the flow charts can be implemented as a computer software program in accordance with the embodiments of the present application. For example, the embodiments of the present application include a computer program product which includes a computer program tangibly embodied on a computer readable medium, the computer program containing program code for executing the methods illustrated by the flow charts. In such embodiments, the computer program can be downloaded and installed from a network via the communication section 609, and / or installed from the removable media 611. When the computer program is executed by the central processing unit (CPU) 601, the above-described functions defined in the system of the present application are executed.

[0109] It should be noted that the computer readable medium shown in the present application can be a computer readable signal medium or a computer readable storage medium or any combination of the two. The computer readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination of the above. More specific examples of the computer readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, the computer readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus. In the present application, the computer readable signal medium can include a data signal carried in a baseband or as a carrier wave in a propagated data signal, which carries the computer readable program code. Such a propagated data signal can take many forms, including but not limited to an electromagnetic signal, an optical signal or any suitable combination of the above. The computer readable signal medium can also be any computer readable medium other than the computer readable storage medium that can send, propagate or transmit the program for use by or in connection with an instruction execution system, device or apparatus. The program code contained on the computer readable medium can be transmitted by any suitable medium, including but not limited to wireless, wire, optical cable, RF or the like, or any suitable combination of the above.

[0110] The computer program product of the present application can be a computer program embodied on a computer readable medium. The computer program product can be stored in the memory 130 and executed by the processor 120 under the control of the operating system. The computer program product can include a program instruction that, when being executed by the processor 120, enables the processor 120 to perform the methods described in the embodiments of the present application. The computer readable medium can be a tangible computer readable storage medium. For example, the computer readable medium can include: a ROM, a RAM, a flash memory, or a hard disk.

[0111] The modules described in the embodiments of the present application can be implemented by software, or can be implemented by hardware. The described modules can also be arranged in a processor, for example, a processor can be described as: a processor includes a data acquisition module, a data screening module, a data determination module, and a data synchronization module. In some cases, the names of these modules do not constitute a limitation on the modules themselves, for example, the data synchronization module can also be described as: a module that synchronizes the to-be-synchronized data to the target public server.

[0112] As another aspect, the present application also provides a computer readable medium, which can be included in the device described in the above embodiments, or can exist independently without being assembled into the device. The computer readable medium carries one or more programs, which, when executed by the device, cause the device to include: acquiring first medical data from one or more private servers respectively, and acquiring second medical data from a target public server; determining first target data corresponding to the one or more private servers respectively, and second target data corresponding to the target public server, according to the activity of the medical products corresponding to the first medical data and the second medical data respectively; determining to-be-synchronized data from the first medical data according to the matching between the second target data and the first medical data, and the first target data; and synchronizing the to-be-synchronized data to the target public server.

[0113] According to the technical scheme of the embodiment of the present application, the first medical data is respectively acquired from one or more private domain servers, and the second medical data is acquired from a target public domain server; the first target data corresponding to the one or more private domain servers and the second target data corresponding to the target public domain server are determined according to the activity of the medical products corresponding to the first medical data and the second medical data respectively; the to-be-synchronized data is determined from the first medical data according to the matching between the second target data and the first medical data and the first target data; and the to-be-synchronized data is synchronized to the target public domain server. In this way, the medical product data with high activity in the private domain server and the public domain server is integrated and shared, so that the medical product data with high activity in the private domain server and the public domain server is uniformly managed, and the value of the medical product can be more fully mined and utilized.

[0114] The above detailed description does not constitute a limitation on the protection scope of the present application. Those skilled in the art should understand that various modifications, combinations, sub-combinations and substitutions can occur depending on design requirements and other factors. Any modification, equivalent replacement and improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A medical data processing method, characterized by, The method comprises the following steps: obtaining first medical data from one or more private domain servers respectively, and obtaining second medical data from a target public domain server; determining first target data corresponding to the one or more private domain servers respectively and second target data corresponding to the target public domain server according to the activity of medical products corresponding to the first medical data and the second medical data respectively; determining to-be-synchronized data from the first medical data according to the matching between the second target data and the first medical data and the first target data; synchronizing the to-be-synchronized data to the target public domain server.

2. The method of claim 1, wherein, The method comprises the following steps: determining the activity of medical products corresponding to the first medical data and the second medical data according to one or more of the click situation, the browsing situation, the consultation situation and the order generation situation of medical products corresponding to the one or more private domain servers and the target public domain server respectively; taking the first medical data corresponding to the medical products with the activity greater than a preset first threshold as the first target data, and taking the second medical data corresponding to the medical products with the activity greater than a preset second threshold as the second target data.

3. The method of claim 1, wherein, The second target data and the first medical data both contain medical product labels, and the to-be-synchronized data is determined from the first medical data according to the matching between the second target data and the first medical data and the first target data. For the first medical data obtained from each private domain server: matching the second product labels in the second target data with the first product labels in the first medical data; determining to-be-synchronized data from the first medical data according to the matching result and the first target data.

4. The method of claim 3, wherein, The method comprises the following steps: in the case that the second product labels and the first product labels are all successfully matched, determining medical data matched with the second product labels from the first medical data; taking the union of the medical data matched with the second product labels in the first medical data and the first target data as the to-be-synchronized data.

5. The method of claim 3, wherein, The method further comprises the following steps: in the case that the second product labels and the first product labels are not all successfully matched, determining second product labels that are not successfully matched from the second target data; generating new data corresponding to the second product labels according to the second product labels that are not successfully matched; the new data belongs to the one or more private domain servers. A union of the medical data in the first medical data corresponding to the second product label with which the matching succeeds, the first target data, and the new data is taken as the to-be-synchronized data.

6. The method of claim 1, wherein, Further comprising: Obtaining, from the target public server, a data synchronization strategy corresponding to each of the one or more private servers, the data synchronization strategy corresponding to each of the one or more private servers being different; the data synchronization strategy indicating drug information and / or medical treatment information allowed to be synchronized by the target public server; According to the data synchronization strategy, target synchronization data meeting the data synchronization strategy is determined from the to-be-synchronized data corresponding to each of the one or more private servers; Synchronizing the target synchronization data to the target public server respectively.

7. The method of claim 1, wherein, Before synchronizing the to-be-synchronized data to the target public server, further comprising: Respectively marking the to-be-synchronized data corresponding to each of the one or more private servers with a source mark, so that the to-be-synchronized data corresponding to different private servers correspond to different private marks respectively.

8. A medical data processing apparatus characterized by comprising: Comprising: A data acquisition module configured to acquire first medical data from one or more private servers and second medical data from a target public server; A data screening module configured to determine first target data corresponding to each of the one or more private servers and second target data corresponding to the target public server according to an activity level of a medical product corresponding to the first medical data and the second medical data respectively; A data determination module configured to determine, from the first medical data, to-be-synchronized data according to a matching between the second target data and the first medical data and the first target data; A data synchronization module configured to synchronize the to-be-synchronized data to the target public server.

9. A server, characterized by Comprising: One or more processors; A storage device configured to store one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method of any one of claims 1-7.

10. A computer readable medium having stored thereon a computer program, characterized in that, The program is executed by the processor to implement the method of any one of claims 1-7.

Images