Medicine transaction data synchronization system based on ERP (Enterprise Resource Planning) integration

Abstract

The invention relates to the technical field of medical information, and particularly discloses an ERP (Enterprise Resource Planning) integration-based medicine transaction data synchronization system, which comprises a data acquisition module, a mapping analysis module, a data fusion module, a trend analysis module and a center console module. According to the scheme, the multi-dimensional feature space is constructed, the field structures in different service systems are identified and mapped to the uniform target field set to construct the dynamic mapping table, and the adaptability to different service systems is enhanced; a dynamic updating mechanism based on event driving is designed, complex business logic is flexibly handled, the system load is reduced, the system operation efficiency is improved, the compliance of a business process is ensured through cooperation of a rule engine, and the problem of data conflict possibly occurring in the data synchronization process of multiple business departments is solved; and a center console is arranged to monitor efficient circulation of medicine transaction data, so that the stability and safety of data exchange are ensured, a reliable tracing basis is provided for medicine supervision, and subsequent analysis and maintenance are facilitated.

Description

Technical Field

[0001] The present invention relates to the field of medical information technology, and specifically refers to a pharmaceutical transaction data synchronization system based on ERP integration. Background Art

[0002] With the rapid development of medical information Internet technology, it is particularly important to synchronize pharmaceutical transaction data between the merchant-side ERP system and business systems such as hospitals, pharmacies, drug regulatory authorities, logistics, and payment systems. Existing data synchronization technical solutions have deficiencies in adaptability, real-time performance, and function support in specific scenarios of the pharmaceutical industry. When synchronizing pharmaceutical transaction data across different business systems, issues such as the integration of multi-source heterogeneous data, feedback of real-time transaction data, and efficient product information synchronization are not fully considered; traditional business logic processing solutions usually cannot dynamically adjust synchronization strategies according to actual business needs, and are prone to data conflicts, resulting in data inconsistency; traditional pharmaceutical data management solutions are usually carried out independently by each business system, with insufficient security mechanisms, a risk of data leakage, and a lack of data traceability capabilities. Summary of the Invention

[0003] In view of the above situation, to overcome the defects of the prior art, the present invention provides a pharmaceutical transaction data synchronization system based on ERP integration. Aiming at the deficiencies of existing data synchronization technical solutions in adaptability, real-time performance, and function support in specific scenarios of the pharmaceutical industry, when synchronizing pharmaceutical transaction data across different business systems, issues such as the integration of multi-source heterogeneous data, feedback of real-time transaction data, and efficient product information synchronization are not fully considered. This solution constructs a multi-dimensional feature space, identifies the field structures in different business systems, and maps them to a unified target field set to construct a dynamic mapping table, improving the accuracy of data mapping, enhancing the adaptability to different business systems, and effectively ensuring data consistency and comprehensibility; aiming at the problem that traditional business logic processing solutions usually cannot dynamically adjust synchronization strategies according to actual business needs, and are prone to data conflicts, resulting in data inconsistency, this solution designs an event-driven dynamic update mechanism to flexibly handle complex business logics, reduce system load, improve system operation efficiency, ensure the compliance of business processes through the coordination of a rule engine, and solve data conflict problems that may occur during the data synchronization process of multiple business departments; aiming at the problem that traditional pharmaceutical data management solutions are usually carried out independently by each business system, with insufficient security mechanisms, a risk of data leakage, and a lack of data traceability capabilities, this solution sets up a central console to monitor the efficient flow of pharmaceutical transaction data, ensuring the stability and security of data exchange, providing a reliable traceability basis for drug supervision, facilitating subsequent analysis and maintenance, and providing an effective guarantee for the safety of public drug use.

[0004] A pharmaceutical transaction data synchronization system based on ERP integration provided by the present invention includes a data acquisition module, a mapping and parsing module, a data fusion module, a trend analysis module, and a central control console module;

[0005] The data acquisition module docks with each business system through a standardized interface, acquires pharmaceutical transaction data and performs preprocessing, and sends the pharmaceutical transaction data to the mapping and parsing module;

[0006] The mapping and parsing module reads the data field definition tables of each business system, maps the pharmaceutical transaction data from different business departments into standard fields, and generates a dynamic mapping table to send to the data fusion module;

[0007] The data fusion module integrates the business logics from different business systems according to the dynamic mapping table and stores them in the database;

[0008] The trend analysis module periodically conducts in-depth analysis on the database, generates a pharmaceutical transaction trend report and sends it to the central control console module;

[0009] The central control console module docks with the merchant-side ERP system, synchronizes the database to the merchant-side ERP system, manages the coordinated work of each module, and records the traceability information of each pharmaceutical transaction data.

[0010] Further, the mapping and parsing module reads the data field definition tables from each business system, analyzes the semantic features in the data field tables, sets the feature dimensions to convert the pharmaceutical transaction data in different formats into a unified standard format, generates a dynamic mapping table, and the mapping rules of the dynamic mapping table are as follows:

[0011] F = {f1, f2, …, f i , …, f n};

[0012] G = {g1, g2, …, g j , …, g m};

[0013]

[0014] In the formula, M represents the dynamic mapping table, F represents the data field table of the business system, f i represents the data field, G represents the target field set, g j represents the target field, k represents the index of the feature dimension, K represents the total number of dimensions, represents the similarity between the field f i and g j on the k-th feature dimension, and w k is the weight of the k-th feature dimension.

[0015] Furthermore, the data fusion module includes an event-driven unit, a rule engine unit, a conflict detection unit, and a database construction unit;

[0016] The event-driven unit monitors the triggering of business logic, detects the synchronization requirements of pharmaceutical transaction data, and invokes the corresponding synchronization processing flow;

[0017] The rule engine unit sets up a rule library, conducts compliance checks on the triggered business logic, and sends the compliant pharmaceutical transaction data to the database construction unit. The formula used is as follows:

[0018]

[0019] In the formula, R represents the compliance check result, j represents the rule index, C j represents the j-th rule, A j represents the rule execution action, m represents the total number of rules, and ∧· represents the logical AND operation;

[0020] The conflict detection unit detects data conflicts in different business systems during the synchronization process of pharmaceutical transaction data, and sends the finally synchronized pharmaceutical transaction data to the database construction unit;

[0021] The database construction unit maps the pharmaceutical transaction data according to the dynamic mapping table and stores it in the database.

[0022] Furthermore, the console module includes a system docking unit, a coordination management unit, and a data traceability unit;

[0023] The system docking unit establishes a data synchronization connection with the merchant-side ERP system, monitors the data transmission status, and processes the exceptions feedback by the ERP system;

[0024] The coordination management unit monitors the data flow of each module in real time, dynamically adjusts the data transmission frequency according to the business load and traffic conditions, and records the data flow transmission logs and exceptions;

[0025] The data traceability unit records the traceability information of each pharmaceutical transaction data, provides multi-dimensional data queries, and generates transaction logs and data integrity reports.

[0026] The beneficial effects achieved by the present invention using the above solution are as follows:

[0027] (1) In view of the deficiencies in the adaptability, real-time performance, and function support of existing data synchronization technical solutions in specific scenarios of the pharmaceutical industry, when synchronizing pharmaceutical transaction data in different business systems, the issues of integration of multi-source heterogeneous data, feedback of real-time transaction data, and efficient product information synchronization are not fully considered. This solution constructs a multi-dimensional feature space, identifies the field structures in different business systems, and maps them to a unified set of target fields to construct a dynamic mapping table, improving the accuracy of data mapping, enhancing the adaptability to different business systems, and effectively ensuring data consistency and comprehensibility.

[0028] (2) In view of the problem that traditional business logic processing solutions usually cannot dynamically adjust synchronization policies according to actual business requirements and are prone to data conflicts, resulting in data inconsistency, this solution designs an event-driven dynamic update mechanism to flexibly handle complex business logics, reduce system load, improve system operation efficiency, ensure the compliance of business processes through the coordination of a rule engine, and solve the possible data conflict problems in the data synchronization process of multiple business departments.

[0029] (3) In view of the problem that traditional pharmaceutical data management solutions are usually carried out independently by each business system, with insufficient security mechanisms, a risk of data leakage, and a lack of data traceability capabilities, this solution sets up a central control console to monitor the efficient flow of pharmaceutical transaction data, ensure the stability and security of data exchange, provide a reliable traceability basis for drug supervision, facilitate subsequent analysis and maintenance, and provide effective protection for the safety of public medication. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 FIG. is a schematic diagram of a pharmaceutical transaction data synchronization system based on ERP integration proposed by the present invention;

[0031] Figure 2 FIG. is a schematic diagram of a data fusion module.

[0032] The drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation to the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0033] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments; based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0034] Example 1, Refer to Figure 1, A pharmaceutical transaction data synchronization system based on ERP integration provided by the present invention includes a data collection module, a mapping and parsing module, a data fusion module, a trend analysis module, and a central control console module; the pharmaceutical transaction data comes from different business systems, including product data and transaction data: product data includes pharmaceutical product information, price, and batch. When each business system updates the product data, the update result will be synchronized to the data collection module; transaction data includes purchase orders, inventory changes, sales records, and logistics tracking. When new transaction data is generated, the corresponding business logic is triggered, and the generated transaction data is synchronized to the data collection module, and the business logic trigger situation is synchronized to the data fusion module;

[0035] The data collection module docks with each business system through a standardized interface, obtains pharmaceutical transaction data, performs preliminary cleaning and classification, and sends the pharmaceutical transaction data to the mapping and parsing module;

[0036] The mapping and parsing module reads the data field definition tables of each business system, maps the pharmaceutical transaction data from different business departments into standard fields, and generates a dynamic mapping table to send to the data fusion module;

[0037] The data fusion module integrates the business logics from different business systems according to the dynamic mapping table and stores them in the database;

[0038] The trend analysis module regularly conducts in-depth analysis on the database, generates a pharmaceutical transaction trend report, and sends it to the central control console module;

[0039] The central control console module docks with the merchant-side ERP system, synchronizes the database to the merchant-side ERP system, manages the coordinated work of each module, and records the traceability information of each pharmaceutical transaction data through a distributed ledger.

[0040] Embodiment 2, refer to Figure 1 , Based on the above embodiment, the data collection module adopts an incremental synchronization algorithm based on timestamps. Each time it reads pharmaceutical transaction data, it only collects the data that has changed since the previous synchronization; a breakpoint resumption function is set. When a network anomaly causes the synchronization to fail, the failure time point is recorded, and the unfinished synchronization task continues after the network resumes. The formula used is as follows:

[0041] T sync =T current -ΔT;

[0042] In the formula, T sync represents the synchronization time point, T current represents the current system time, and ΔT represents the preset time window length;

[0043] Assume that the current time of the system is 10:00 and the preset time window length ΔT is 5 minutes. Then, the synchronization time point T is calculated every 5 minutes. sync , that is, the synchronization time point is 9:55, and all pharmaceutical transaction data that has changed between 9:55 and 10:00 is screened out for synchronization.

[0044] Example 3, refer to Figure 1 . Based on the above example, the mapping and parsing module reads the data field definition tables from each business system, analyzes the semantic features in the data field tables, sets feature dimensions to convert pharmaceutical transaction data in different formats into a unified standard format. The feature dimensions include field name, data type, and value range, and a dynamic mapping table is generated. The mapping rules of the dynamic mapping table are as follows:

[0045] F = {f1, f2, …, f i , …, f n};

[0046] G = {g1, g2, …, g j , …, g m};

[0047]

[0048] In the formula, M represents the dynamic mapping table, F represents the data field table of the business system, f i represents the data field, G represents the set of target fields, g j represents the target field, k represents the index of the feature dimension, K represents the total number of dimensions, represents the similarity between field f i and g j in the k-th feature dimension, and w k is the weight of the k-th feature dimension.

[0049] By performing the above operations, there are deficiencies in the adaptability, real-time performance, and function support of the existing data synchronization technical solutions in the specific scenarios of the pharmaceutical industry. When synchronizing pharmaceutical transaction data in different business systems, the integration of multi-source heterogeneous data, the feedback of real-time transaction data, and the efficient synchronization of product information are not fully considered. This solution constructs a multi-dimensional feature space, identifies the field structures in different business systems, and maps them into a unified set of target fields to construct a dynamic mapping table, improving the accuracy of data mapping, enhancing the adaptability to different business systems, and effectively ensuring data consistency and comprehensibility.

[0050] Example 4, refer to Figure 1 and Figure 2, this embodiment is based on the above embodiment, and the data fusion module includes an event-driven unit, a rule engine unit, a conflict detection unit, and a database construction unit;

[0051] The event-driven unit monitors the triggering of business logic, detects the synchronization requirements of pharmaceutical transaction data, and invokes the corresponding synchronization processing flow;

[0052] The rule engine unit sets up a rule library, performs compliance checks on the triggered business logic, and sends the compliant pharmaceutical transaction data to the database construction unit. The formula used is as follows:

[0053]

[0054] In the formula, R represents the compliance check result, j represents the rule index, C j represents the jth rule, A j represents the rule execution action, m represents the total number of rules, and ∧· represents the logical AND operation;

[0055] During the synchronization process of pharmaceutical transaction data, the conflict detection unit detects data conflicts in different business systems, sets the weight value for each conflict data, and uses weighted average to calculate the finally synchronized pharmaceutical transaction data and sends it to the database construction unit. The formula used is as follows:

[0056]

[0057] In the formula, V f represents the weight calculation result, n represents the total number of conflicting data, i represents the index of the conflict data, V i represents the original value of the conflict data, and w i represents the weight value of the ith conflict data;

[0058] The database construction unit maps the pharmaceutical transaction data according to the dynamic mapping table and stores it in the database.

[0059] By performing the above operations, for the problem that traditional business logic processing solutions usually cannot dynamically adjust the synchronization strategy according to actual business needs and are prone to data conflicts, resulting in data inconsistencies, this solution designs an event-driven dynamic update mechanism to flexibly handle complex business logic, reduce system load, improve system operation efficiency, ensure the compliance of business processes through the cooperation of the rule engine, and solve the possible data conflict problems during the data synchronization process of multiple business departments.

[0060] Embodiment Five, refer to Figure 1, this embodiment is based on the above embodiment. The trend analysis module regularly reads the database, models the pharmaceutical transaction data using time series analysis algorithms, and predicts the pharmaceutical transaction trends in the next period of time. The formula used is as follows:

[0061] D t = α·S t +(1 - α)·D t-1 ;

[0062] In the formula, D t and D t-1 respectively represent the short-term predicted trading volumes at the current moment and the previous moment, S t represents the actual trading volume at the current moment, and α represents the smoothing factor.

[0063] Embodiment Six, refer to Figure 1 , this embodiment is based on the above embodiment. The central control console module includes a system docking unit, a coordination management unit, and a data traceability unit;

[0064] The system docking unit establishes a data synchronization connection with the merchant-side ERP system, monitors the data transmission status, and processes the abnormal situations feedback by the ERP system;

[0065] The coordination management unit monitors the data streams of each module in real time, dynamically adjusts the data transmission frequency according to the business load and traffic conditions, and records the data stream transmission logs and abnormal situations;

[0066] The data traceability unit records the traceability information of each pharmaceutical transaction data in the distributed ledger, provides multi-dimensional data queries, and generates transaction logs and data integrity reports.

[0067] By performing the above operations, for the problems that the traditional pharmaceutical data management solutions are usually independently carried out by each business system, with insufficient security mechanisms, risks of data leakage, and lack of data traceability capabilities, this solution sets up a central control console to monitor the efficient flow of pharmaceutical transaction data, ensure the stability and security of data exchange, provide a reliable traceability basis for drug supervision, facilitate subsequent analysis and maintenance, and provide an effective guarantee for the safety of public medication.

[0068] It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or also includes elements inherent to such process, method, article or device.

[0069] Although embodiments of the present invention have been shown and described, it will be understood by those of ordinary skill in the art that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of the present invention, and the scope of the present invention is defined by the appended claims and their equivalents.

[0070] The present invention and its embodiments have been described above. Such description is not restrictive. What is shown in the drawings is only one of the embodiments of the present invention, and the actual structure is not limited thereto. Generally speaking, if those of ordinary skill in the art are inspired by it and, without departing from the gist of the present invention, design similar structural modes and embodiments to this technical solution without creative efforts, they shall fall within the protection scope of the present invention.

Claims

1. A pharmaceutical transaction data synchronization system based on ERP integration, characterized in that: It includes a data acquisition module, a mapping and parsing module, a data fusion module, a trend analysis module, and a console module; The data acquisition module docks with each business system through a standardized interface, obtains pharmaceutical transaction data and preprocesses it, and sends the pharmaceutical transaction data to the mapping and parsing module; The mapping and parsing module reads the data field definition tables of each business system, maps the pharmaceutical transaction data from different business departments into standard fields, generates a dynamic mapping table and sends it to the data fusion module; The data fusion module integrates the business logics from different business systems according to the dynamic mapping table and stores them in the database; The trend analysis module periodically conducts in-depth analysis on the database, generates a pharmaceutical transaction trend report and sends it to the console module; The console module docks with the merchant-side ERP system, synchronizes the database to the merchant-side ERP system, manages the coordinated work of each module, and records the traceability information of each pharmaceutical transaction data.

2. The pharmaceutical transaction data synchronization system based on ERP integration according to claim 1, wherein: The mapping and parsing module reads the data field definition tables from each business system, analyzes the semantic features in the data field tables, sets feature dimensions to convert pharmaceutical transaction data in different formats into a unified standard format, generates a dynamic mapping table, and the mapping rules of the dynamic mapping table are as follows: where M represents the dynamic mapping table, f i represents the data field, g j represents the target field, k represents the index of the feature dimension, K represents the total number of dimensions, represents the field f i and g j on the k-th feature dimension, w k is the weight of the k-th feature dimension.

3. A pharmaceutical transaction data synchronization system based on ERP integration according to claim 1, characterized in that: The data fusion module includes an event-driven unit, a rule engine unit, a conflict detection unit, and a database construction unit; The event-driven unit monitors the triggering of business logics, detects the synchronization requirements of pharmaceutical transaction data, and invokes the corresponding synchronization processing flow; The rule engine unit sets a rule library, conducts compliance checks on the triggered business logics, and sends the pharmaceutical transaction data that complies with the rules to the database construction unit; The conflict detection unit detects data conflicts in different business systems during the synchronization process of pharmaceutical transaction data, and sends the finally synchronized pharmaceutical transaction data to the database construction unit; The database construction unit maps the pharmaceutical transaction data according to the dynamic mapping table and stores it in the database.

4. A pharmaceutical transaction data synchronization system based on ERP integration according to claim 1, characterized in that: The console module includes a system docking unit, a coordination and management unit, and a data traceability unit; The system docking unit establishes a data synchronization connection with the merchant-side ERP system, monitors the data transmission status, and processes the exceptions feedback by the ERP system; The coordination and management unit real-time monitors the data streams of each module, dynamically adjusts the data transmission frequency according to the business load and traffic conditions, and records the data stream transmission logs and exceptions; The data traceability unit records the traceability information of each pharmaceutical transaction data, provides multi-dimensional data query, and generates transaction logs and data integrity reports.

Images