Medical multi-source heterogeneous data acquisition method and system and readable storage medium

Abstract

The invention provides a medical multi-source heterogeneous data collection method and system and a readable storage medium, and the method comprises the steps: building a standard ward theme library model, and determining a data quality standard and a data governance rule according to the standard ward theme library model; obtaining a medical heterogeneous data source, and accessing the medical heterogeneous data source to a local paste source library through an ETL process to obtain access data; performing data governance on the access data according to a data governance rule to obtain data in a unified format, and writing the data in the unified format into a standard ward theme library; and performing data synchronization on the standard ward theme library. By means of the technical scheme, data from different sources can be effectively integrated, the accuracy, integrity and consistency of the data are ensured, and therefore daily nursing work and nursing decision making of a ward are effectively supported.

Description

Technical Field

[0001] The present application relates to the technical field of multi-source heterogeneous data acquisition, and in particular to a medical multi-source heterogeneous data acquisition method and system, and a readable storage medium. Background Art

[0002] At present, most of the data collected by hospitals are collected in traditional ways, and it is still difficult to obtain high-quality data. This is specifically reflected in the following reasons: there are many data sources, various data connection methods, various data structure standards, and lack of complete data governance. Traditional data collection methods focus more on data access and synchronization, and lack effective data governance methods, resulting in doubts about data quality and consistency. Summary of the invention

[0003] This application aims to solve or improve the above technical problems.

[0004] To this end, the first objective of the present application is to provide a method for collecting medical multi-source heterogeneous data.

[0005] The second objective of the present application is to provide a medical multi-source heterogeneous data acquisition system.

[0006] The third objective of the present application is to provide a medical multi-source heterogeneous data acquisition system.

[0007] The fourth object of the present application is to provide a readable storage medium.

[0008] To achieve the first purpose of the present application, the technical solution of the first aspect of the present application provides a method for collecting medical multi-source heterogeneous data, including: establishing a standard ward subject library model, and determining data quality standards and data governance rules based on the standard ward subject library model; obtaining a medical heterogeneous data source, and connecting the medical heterogeneous data source to a local source library through an ETL process to obtain access data; performing data governance on the access data according to data governance rules to obtain data in a unified format, and writing the data in a unified format into a standard ward subject library; and synchronizing data in the standard ward subject library.

[0009] According to the medical multi-source heterogeneous data collection method provided by this application, a standard ward theme library model is first established. According to different standard ward theme library models, relevant data quality standards and data governance rules are formulated as the processing basis for data access and data governance. Then, medical heterogeneous data sources are obtained, and multiple medical heterogeneous data sources are connected to the local source library through a flexible ETL (Extract-Transform-Load) process to obtain access data. Medical heterogeneous data sources can include relational databases, non-relational databases, API (Application Programming Interface, Application Programming Interface) interface data, file data, etc. Then, data governance is performed on the access data according to the data governance rules to ensure the quality and consistency of the data, and the nodes and operators in the data development are used to process the data, such as data cleaning, data fusion, data association and other operations, to convert heterogeneous data into data in a unified format, which is convenient for subsequent analysis and processing, and the unified format data is written into the standard ward theme library. Finally, the synchronous sharing of ward theme data can be completed through file, interface, and DB data exchange methods to ensure that the data can be effectively used. The medical multi-source heterogeneous data collection method provided in this application can effectively integrate medical data from different sources to ensure the accuracy, completeness and consistency of the data, thereby effectively supporting daily nursing work in the ward and the making of nursing decisions.

[0010] In addition, the technical solution provided by this application may also have the following additional technical features: In some technical solutions, optionally, a medical heterogeneous data source is obtained, and the medical heterogeneous data source is connected to a local source library through an ETL process to obtain access data, including: obtaining a medical heterogeneous data source, and determining a calling method, calling frequency, and interface type according to the access method of the medical heterogeneous data source; determining a source library model according to the data interface standard of the medical heterogeneous data source, and determining basic governance rules for adding new data into the source library according to data governance rules; determining data cleaning and conversion rules according to the source library model and the standard ward subject library model; and connecting the medical heterogeneous data source to a local source library through an ETL process according to the calling method, calling frequency, interface type, and basic governance rules to obtain access data.

[0011] In this technical solution, a medical heterogeneous data source is obtained, and the medical heterogeneous data source is connected to the local source library through the ETL process to obtain access data. Specifically, the medical heterogeneous data source is first obtained, and the calling method, calling frequency and interface type are determined according to the access method of the medical heterogeneous data source. Then, according to the data interface standard of the medical heterogeneous data source, the source library model is determined, and at the same time, the basic governance rules for adding new data to the source library are determined according to the data governance rules. Then, the data cleaning and conversion rules are determined according to the source library model and the standard ward theme library model. Finally, according to the calling method, calling frequency, interface type and basic governance rules, the medical heterogeneous data source is connected to the local source library through the ETL process to obtain access data. It can be understood that the access methods of each source are first sorted out to determine whether the calling method is active or passive, the calling frequency, and the specific interface type, namely, http (Hypertext Transfer Protocol, Hypertext Transfer Protocol) interface method, file method, DB (DataBase, database) method, TCP / IP (Transmission Control Protocol / Internet Protocol, Transmission Control Protocol / Internet Protocol) method, message, etc. Then the data interface standards provided by each source are sorted out to define the source library model. At the same time, according to the requirements of the topic model rules, define the basic governance rules for adding new data into the post source library. Compare the post source library model with the topic library model, and sort out the new data cleaning and conversion rules. Based on the sorted information, configure the data collection tasks of each source and complete the integration of data from each source into the post source library.

[0012] In some technical solutions, optionally, data governance is performed on the access data according to data governance rules to obtain data in a unified format, including: data governance is performed on the access data according to data cleaning and conversion rules to obtain data in a unified format, and data governance includes data filtering, data conversion, data loading, data specification, data cleaning, data verification and data updating.

[0013] In this technical solution, data governance is performed on the access data according to the data governance rules to obtain data in a unified format. Specifically, data filtering, data conversion, data loading, data reduction, data cleaning, data verification and data update are performed on the access data according to the data cleaning and conversion rules to obtain data in a unified format. Specifically, data filtering should initially implement filtering operations on data that does not conform to application rules or is invalid, so that data standards or representative content are unified. Data conversion should implement conversion of conflicts in data formats, information codes, and values. The main operations performed in the data loading process are insert operations and modify operations. A database environment is built to insert clean data and dirty data into different data tables respectively. Data reduction is used to obtain a reduced representation of the data set, which is much smaller, but still close to maintaining the integrity of the original data. The results before and after reduction are the same or almost the same, solving the problem of very large data volume during data processing. Data cleaning converts dirty data into data that meets data quality requirements or application requirements according to data cleaning rules, preparing for data verification. Data verification verifies the cleaned data according to relevant standards or specifications. If the verification fails, it returns and re-cleans the data. When the data passes the verification, it means that the data meets the requirements and the service interface can be provided to users. However, a data update plan should be established before the data is updated. The plan content includes the frequency and cycle of the update, the content, scope and total amount of the data update, etc.

[0014] In some technical solutions, data synchronization is optionally performed on the standard ward subject library, including: data synchronization and sharing of the standard ward subject library in a scheduled manner or in real time to obtain the final standard ward subject library, and the data synchronization and sharing methods include one of the following or a combination thereof: data file method, http interface method, and database exchange method.

[0015] In this technical solution, data synchronization is performed on the standard ward theme library, specifically, data synchronization and sharing of the standard ward theme library is performed in a scheduled manner or in real time to obtain the final standard ward theme library. Data synchronization can be scheduled or real-time. The appropriate synchronization method is selected according to actual needs to ensure that the data can be effectively used. The medical data written into the standard theme library has application value. According to different data application situations, data synchronization sharing in the form of data files, data synchronization sharing in the form of http interfaces, and data synchronization sharing in the form of database exchange are provided.

[0016] In some technical solutions, optionally, the final standard ward subject library includes one of the following or a combination thereof: a patient subject library, a medical order subject library, a medical care subject library, a test report subject library, an inspection report subject library, a patient payment record subject library, and a patient expense details subject library.

[0017] In this technical solution, the final standard ward subject library includes the patient subject library, the doctor's order subject library, the medical care subject library, the test report subject library, the examination report subject library, the patient payment record subject library, and the patient expense details subject library.

[0018] In some technical schemes, optionally, the medical heterogeneous data source includes one of the following or a combination thereof: relational database, non-relational database, API interface data, file data; and / or the interface type of the medical heterogeneous data source includes one of the following or a combination thereof: http interface method, file method, DB method, TCP / IP method, message; and / or the data format of the medical heterogeneous data source includes one of the following or a combination thereof: Json, Xml, Tcp / Ip data packet, HL7, message string.

[0019] In this technical solution, medical heterogeneous data sources include relational databases, non-relational databases, API interface data, and file data. The interface types of medical heterogeneous data sources include http interface mode, file mode, DB mode, TCP / IP mode, and message. The data formats of medical heterogeneous data sources include Json (JavaScript Object Notation), Xml (Extensible Markup Language), TCP / IP data packets, HL7 (Health Level 7, health information exchange standard), and message strings.

[0020] In some technical solutions, optionally, the data governance rules include one of the following or a combination thereof: null value check, value range check, specification check, business logic check, duplicate data check, record authenticity check, code rationality check, update timeliness check, and data volume consistency check.

[0021] In this technical solution, data governance rules include null value check, value range check, specification check, business logic check, duplicate data check, record authenticity check, code rationality check, update timeliness check, and data volume consistency check.

[0022] To achieve the second purpose of the present application, the technical solution of the second aspect of the present application provides a medical multi-source heterogeneous data acquisition system, including: a model building module, used to establish a standard ward subject library model, and determine data quality standards and data governance rules based on the standard ward subject library model; a data access module, used to obtain medical heterogeneous data sources, and connect the medical heterogeneous data sources to the local source library through the ETL process to obtain access data; a data governance module, used to perform data governance on the access data according to data governance rules, obtain unified format data, and write the unified format data into the standard ward subject library; a data synchronization module, used to synchronize data with the standard ward subject library.

[0023] According to the medical multi-source heterogeneous data acquisition system provided by the present application, it includes a model building module, a data access module, a data governance module and a data synchronization module. Among them, the model building module is used to establish a standard ward subject library model, and determine the data quality standards and data governance rules according to the standard ward subject library model. The data access module is used to obtain medical heterogeneous data sources, and connect the medical heterogeneous data sources to the local source library through the ETL process to obtain access data. The data governance module is used to perform data governance on the access data according to the data governance rules, obtain unified format data, and write the unified format data into the standard ward subject library. The data synchronization module is used to synchronize data with the standard ward subject library. Through the medical multi-source heterogeneous data acquisition system provided by the present application, medical data from different sources can be effectively integrated to ensure the accuracy, completeness and consistency of the data, thereby effectively supporting the daily nursing work in the ward and the formulation of nursing decisions.

[0024] To achieve the third purpose of the present application, the technical solution of the third aspect of the present application provides a medical multi-source heterogeneous data acquisition system, including: a memory and a processor, wherein the memory stores programs or instructions that can be run on the processor, and when the processor executes the program or instruction, it implements the medical multi-source heterogeneous data acquisition method of any one of the technical solutions of the first aspect, and thus has the technical effect of any one of the technical solutions of the first aspect, which will not be repeated here.

[0025] In order to achieve the fourth purpose of the present application, the technical solution of the fourth aspect of the present application provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by the processor, the steps of the medical multi-source heterogeneous data acquisition method of any one of the technical solutions of the first aspect are implemented, and thus it has the technical effect of any one of the technical solutions of the first aspect mentioned above, which will not be repeated here.

[0026] Additional aspects and advantages of the present application will become apparent in the following description or will be learned through practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which: Figure 1 This is a schematic diagram of the steps of a method for collecting medical multi-source heterogeneous data according to an embodiment of the present application; Figure 2 This is a schematic diagram of the steps of a method for collecting medical multi-source heterogeneous data according to an embodiment of the present application; Figure 3 This is a schematic diagram of the steps of a method for collecting medical multi-source heterogeneous data according to an embodiment of the present application; Figure 4 This is a schematic diagram of the steps of a method for collecting medical multi-source heterogeneous data according to an embodiment of the present application; Figure 5 This is a schematic block diagram of the structure of a medical multi-source heterogeneous data acquisition system according to an embodiment of the present application; Figure 6 This is a schematic block diagram of the structure of a medical multi-source heterogeneous data acquisition system according to an embodiment of the present application; Figure 7 This is a schematic diagram of the steps of a method for collecting medical multi-source heterogeneous data according to an embodiment of the present application; Figure 8 This is a schematic diagram of the steps of a method for collecting medical multi-source heterogeneous data according to an embodiment of the present application; Fig. 9 This is a flowchart of the steps of a method for collecting medical multi-source heterogeneous data according to one embodiment of the present application.

[0028] in, Figure 5 and Figure 6 The corresponding relationship between the reference numerals and component names in the figure is: 10: Medical multi-source heterogeneous data acquisition system; 110: Model building module; 120: Data access module; 130: Data governance module; 140: Data synchronization module; 20: Medical multi-source heterogeneous data acquisition system; 300: Memory; 400: Processor. DETAILED DESCRIPTION

[0029] In order to more clearly understand the above-mentioned purposes, features and advantages of the present application, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. It should be noted that the embodiments of the present application and the features in the embodiments can be combined with each other without conflict.

[0030] In the following description, many specific details are set forth to facilitate a full understanding of the present application. However, the present application may also be implemented in other ways different from those described herein. Therefore, the scope of protection of the present application is not limited to the specific embodiments disclosed below.

[0031] Refer to the following Figures 1 to 9 Describe the medical multi-source heterogeneous data acquisition method and system, and readable storage medium of some embodiments of the present application.

[0032] like Figure 1 As shown, the embodiment of the first aspect of the present application provides a method for collecting medical multi-source heterogeneous data, comprising the following steps: Step S102: Establish a standard ward subject library model, and determine data quality standards and data governance rules based on the standard ward subject library model; Step S104: Obtain medical heterogeneous data sources, and connect the medical heterogeneous data sources to the local source database through the ETL process to obtain access data; Step S106: Perform data governance on the access data according to the data governance rules to obtain data in a unified format, and write the data in the unified format into the standard ward subject library; Step S108: Synchronize the data of the standard ward subject library.

[0033] According to the medical multi-source heterogeneous data acquisition method provided by this embodiment, firstly, a standard ward theme library model is established, and according to different standard ward theme library models, relevant data quality standards and data governance rules are formulated as the processing basis for data access and data governance. Then, a medical heterogeneous data source is obtained, and a variety of medical heterogeneous data sources are connected to the local source library through a flexible ETL process to obtain access data. The medical heterogeneous data source may include a relational database, a non-relational database, an API interface data, a file data, etc. Then, data governance is performed on the access data according to the data governance rules to ensure the quality and consistency of the data, and the nodes and operators in the data development are used to process the data, such as data cleaning, data fusion, data association and other operations, to convert the heterogeneous data into data in a unified format, which is convenient for subsequent analysis and processing, and the unified format data is written into the standard ward theme library. Finally, the synchronous sharing of ward theme data can be completed through files, interfaces, and DB data exchange methods to ensure that the data can be effectively used. Through the medical multi-source heterogeneous data acquisition method provided by this application, medical data from different sources can be effectively integrated to ensure the accuracy, completeness and consistency of the data, thereby effectively supporting the daily nursing work and nursing decision-making of the ward.

[0034] like Figure 2 As shown, according to a medical multi-source heterogeneous data collection method according to an embodiment of the present application, a medical heterogeneous data source is obtained, and the medical heterogeneous data source is connected to a local source library through an ETL process to obtain access data, including the following steps: Step S202: Acquire a medical heterogeneous data source, and determine a calling method, calling frequency, and interface type according to the access method of the medical heterogeneous data source; Step S204: Determine the source library model according to the data interface standard of the medical heterogeneous data source, and determine the basic governance rules for adding new data into the source library according to the data governance rules; Step S206: determining data cleaning and conversion rules according to the post source library model and the standard ward theme library model; Step S208: Connect the medical heterogeneous data source to the local source library through the ETL process according to the calling method, calling frequency, interface type and basic governance rules to obtain the access data.

[0035] In this embodiment, a medical heterogeneous data source is obtained, and the medical heterogeneous data source is connected to the local source library through the ETL process to obtain access data. Specifically, the medical heterogeneous data source is first obtained, and the calling method, calling frequency and interface type are determined according to the access method of the medical heterogeneous data source. Then, according to the data interface standard of the medical heterogeneous data source, the source library model is determined, and the basic governance rules for the newly added data to the source library are determined according to the data governance rules. Then, the data cleaning and conversion rules are determined according to the source library model and the standard ward theme library model. Finally, according to the calling method, calling frequency, interface type and basic governance rules, the medical heterogeneous data source is connected to the local source library through the ETL process to obtain access data. It can be understood that first, the access methods of each source are sorted out to determine whether it is an active or passive calling method, calling frequency, and specific interface type, that is, http interface method, file method, DB method, TCP / IP method, message, etc. Then the data interface standards provided by each source are sorted out to define the source library model. At the same time, according to the requirements of the theme model rules, the basic governance rules for the newly added data to the source library are defined. Compare the source library model and the theme library model, and sort out the new data cleaning and conversion rules. According to the sorted information, configure the data collection tasks from each source and complete the integration of data from each source into the source library.

[0036] like Figure 3 As shown, according to a medical multi-source heterogeneous data collection method according to an embodiment of the present application, data governance is performed on the access data according to the data governance rules to obtain unified format data, which specifically includes the following steps: Step S302: Perform data governance on the access data according to data cleaning and conversion rules to obtain data in a unified format. Data governance includes data filtering, data conversion, data loading, data specification, data cleaning, data verification and data updating.

[0037] In this embodiment, data governance is performed on the access data according to the data governance rules to obtain data in a unified format, specifically, data filtering, data conversion, data loading, data reduction, data cleaning, data verification and data update are performed on the access data according to the data cleaning and conversion rules to obtain data in a unified format. Specifically, data filtering should initially implement filtering operations on data that does not conform to application rules or is invalid, so that data standards or representative content are unified. Data conversion should implement conversion of conflicts in data formats, information codes, and values. The main operations performed in the data loading process are insert operations and modify operations. A database environment is built to insert clean data and dirty data into different data tables respectively. Data reduction is used to obtain a reduced representation of the data set, which is much smaller, but still close to maintaining the integrity of the original data. The results before and after reduction are the same or almost the same, which solves the problem of very large data volume during data processing. Data cleaning converts dirty data into data that meets data quality requirements or application requirements according to data cleaning rules, and prepares for data verification. Data verification verifies the cleaned data according to relevant standards or specifications. If the verification fails, it returns and re-cleans the data. When the data passes the verification, it means that the data meets the requirements and the service interface can be provided to users. However, a data update plan should be established before the data is updated. The plan content includes the frequency and cycle of the update, the content, scope and total amount of the data update, etc.

[0038] like Figure 4 As shown, according to a medical multi-source heterogeneous data collection method according to an embodiment of the present application, data synchronization is performed on a standard ward subject library, including the following steps: Step S402: Synchronize and share data of the standard ward theme library in a scheduled manner or in real time to obtain a final standard ward theme library. The data synchronization and sharing methods include one of the following or a combination thereof: data file method, http interface method, and database exchange method.

[0039] In this embodiment, data synchronization is performed on the standard ward theme library, specifically, data synchronization and sharing of the standard ward theme library is performed in a scheduled manner or in a real-time manner to obtain the final standard ward theme library. Data synchronization can be scheduled or real-time. The appropriate synchronization method is selected according to actual needs to ensure that the data can be effectively used. The medical data written into the standard theme library has application value. According to different data application situations, data synchronization sharing in the form of data files, data synchronization sharing in the form of http interfaces, and data synchronization sharing in the form of database exchange are provided.

[0040] In some technical solutions, optionally, the final standard ward subject library includes a patient subject library, a doctor's order subject library, a medical care subject library, a test report subject library, an examination report subject library, a patient payment record subject library, and a patient expense details subject library.

[0041] In some technical solutions, optionally, the medical heterogeneous data source includes a relational database, a non-relational database, API interface data, and file data. The interface types of the medical heterogeneous data source include http interface mode, file mode, DB mode, TCP / IP mode, and message. The data formats of the medical heterogeneous data source include Json, Xml, TCP / IP data packet, HL7, and message string.

[0042] In some technical solutions, optionally, data governance rules include null value check, value range check, specification check, business logic check, duplicate data check, record authenticity check, code rationality check, update timeliness check, and data volume consistency check.

[0043] like Figure 5 As shown, an embodiment of the second aspect of the present application provides a medical multi-source heterogeneous data acquisition system 10, including: a model building module 110, used to establish a standard ward subject library model, and determine data quality standards and data governance rules according to the standard ward subject library model; a data access module 120, used to obtain medical heterogeneous data sources, and connect the medical heterogeneous data sources to the local source library through the ETL process to obtain access data; a data governance module 130, used to perform data governance on the access data according to data governance rules, obtain unified format data, and write the unified format data into the standard ward subject library; a data synchronization module 140, used to synchronize data with the standard ward subject library.

[0044] The medical multi-source heterogeneous data acquisition system 10 provided according to this embodiment includes a model building module 110, a data access module 120, a data governance module 130 and a data synchronization module 140. Among them, the model building module 110 is used to establish a standard ward theme library model, and determine the data quality standards and data governance rules according to the standard ward theme library model. The data access module 120 is used to obtain medical heterogeneous data sources, and connect the medical heterogeneous data sources to the local source library through the ETL process to obtain access data. The data governance module 130 is used to perform data governance on the access data according to the data governance rules, obtain unified format data, and write the unified format data into the standard ward theme library. The data synchronization module 140 is used to synchronize data with the standard ward theme library. Through the medical multi-source heterogeneous data acquisition system provided by this application, medical data from different sources can be effectively integrated to ensure the accuracy, completeness and consistency of the data, thereby effectively supporting the daily nursing work and nursing decision-making of the ward.

[0045] like Figure 6As shown, an embodiment of the third aspect of the present application provides a medical multi-source heterogeneous data acquisition system 20, comprising: a memory 300 and a processor 400, wherein the memory 300 stores a program or instruction that can be run on the processor 400, and when the processor 400 executes the program or instruction, it implements the steps of the medical multi-source heterogeneous data acquisition method of any one of the embodiments of the first aspect, and thus has the technical effect of any one of the embodiments of the first aspect mentioned above, which will not be repeated here.

[0046] The embodiment of the fourth aspect of the present application provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the medical multi-source heterogeneous data acquisition method of any one of the embodiments of the first aspect are implemented, and thus it has the technical effect of any one of the embodiments of the first aspect mentioned above, which will not be repeated here.

[0047] like Figures 7 to 9 As shown, a medical multi-source heterogeneous data collection method according to a specific embodiment provided by the present application aims to collect medical-related information from data of multiple different sources and structures, including structured and unstructured data, such as patient order data, examination and test reports, educational imaging materials, etc. These data may be stored in different systems or platforms and have different format structures. By effectively integrating data from different sources, the accuracy, completeness and consistency of the data are ensured, thereby effectively supporting daily nursing work in the ward and the making of nursing decisions.

[0048] ‌Data access‌: Through a flexible ETL (extraction, transformation, loading) process, multiple heterogeneous data sources can be connected to the data platform with one click. These data sources may include relational databases, non-relational databases, API interface data, file data, etc.

[0049] ‌Data cleaning and conversion‌: Clean and convert the accessed data to ensure data quality and consistency. Use the nodes and operators in data development to process the data, such as data cleaning, data fusion, data association, etc., to convert heterogeneous data into data in a unified format for subsequent analysis and processing.

[0050] ‌Data synchronization‌: During the data processing process, data synchronization also needs to be considered. Data synchronization can be scheduled or real-time. Choose the appropriate synchronization method according to actual needs to ensure that the data can be effectively used.

[0051] Through data access, data cleaning and conversion, and data synchronization, medical data from different sources can be effectively collected to provide support for daily nursing work applications and nursing decisions.

[0052] Based on the experience and understanding of ward information construction, this embodiment will pre-formulate a set of unified standard ward theme library models, and at the same time, formulate relevant data quality standards and data governance rules for different data models as the basis for data access and data governance. Then use powerful data integration tools widely used in the medical field to adapt heterogeneous data sources and complete the access of heterogeneous source data to the local source library. Then, according to the pre-made data governance rules, the data that has been connected to the source library is subjected to a series of cleaning and conversion processes such as deduplication, fusion, conversion, and labeling, and the processed high-quality data is written into a unified standard theme library to form a standard and unified medical enterprise ward theme data asset. Finally, the synchronous sharing of ward theme data can be completed through files, interfaces, and DB data exchange methods.

[0053] Specifically, the standard subject library is defined as follows: Based on relevant medical information standards, computer information system standards and information security standards, combined with many years of practical experience in smart ward information construction projects in medical enterprises, a complete, business-scalable and secure medical enterprise ward subject library model is defined and solidified.

[0054] Prefabricated common governance rules: For common quality issues in the data collection process, a set of general governance rules are prefabricated, including null value check, value range check, specification check, business logic check, duplicate data check, record authenticity check, code rationality check, update timeliness check, data volume consistency check, etc.

[0055] Source library definition: Based on the data structure standards provided by various data sources of medical enterprises, define the corresponding data model and complete the data access of each data source.

[0056] Data access: Through the data integration tools widely used in the medical field, the access of medical data from different data sources, different access methods (http interface method, file method, DB method, TCP / IP method, message, etc.), and different data formats (Json, Xml, TCP / IP data packet, HL7, message string, etc.) of medical enterprises is completed. At the same time, the data will be checked for consistency, timeliness, and other basic verifications during the access process, and then entered into the source library.

[0057] Data governance rules: The medical data that has been entered into the source database still has quality issues and is not very usable. It is necessary to perform cleaning and conversion processing such as deduplication, fusion, conversion, and labeling on the source database data according to the pre-made common governance rules and newly defined governance rules, and finally write it into the standard subject database.

[0058] Data synchronization and sharing: The medical data written into the standard subject database has application value. According to different data application situations, data synchronization and sharing in the form of data files, data synchronization and sharing in the form of http interface, and data synchronization and sharing in the form of database exchange are provided.

[0059] The medical multi-source heterogeneous data collection method includes the following steps: Sort out the access methods of each source, determine whether it is active or passive calling method, calling frequency, and specific interface type (http interface method, file method, DB method, TCP / IP method, message, etc.); Sort out the data interface standards provided by various sources and define the source library model. At the same time, according to the requirements of the topic model rules, define the basic governance rules for adding new data into the source library; Compare the post source library model and the topic library model, and sort out the new data cleaning and conversion rules; According to the sorted information, configure the data collection tasks of each source and complete the integration of data from each source into the source library; According to the cleaning and conversion rules, configure the governance tasks of the post source library to the theme library.

[0060] Based on the data that has been governed to the subject library model, the corresponding data services are published and a default data synchronization and sharing method is provided.

[0061] The system function modules of this embodiment include: The data integration module provides functions such as heterogeneous source data access adaptation, input and output data conversion, and data collection job orchestration.

[0062] The metadata management module manages metadata, including metadata collection, maintenance, publishing and analysis functions, clarifies the source data dictionary, and understands the origin and development of the data.

[0063] Data governance rule management module defines data cleansing and data transformation rules.

[0064] Data quality management module, data quality detection and quality report output make data as clear as water.

[0065] Data service API module, providing data synchronization and sharing API services.

[0066] Data monitoring module, data integration and data sharing monitoring.

[0067] like Figure 7 As shown, the data integration process of this embodiment is S502: visual modeling; S504: model resource retrieval; S506: ETL process design; S508: ETL process flow design; S510: data desensitization; S512: scheduling management.

[0068] like Figure 8As shown, the data governance process of this embodiment is S602: data filtering; S604: data conversion; S606: data loading; S608: data reduction; S610: data cleaning; S612: data verification; S614: data update. It can be understood that the data governance steps mainly include data filtering, data conversion, data loading, data reduction, data cleaning, data verification and data update. Data filtering should initially implement filtering operations on data that does not conform to application rules or is invalid, so that data standards or representative content are unified. Data conversion should achieve conversion of data formats, information codes, and value conflicts. The main operations performed in the data loading process are insert operations and modify operations. Build a database environment to insert clean data and dirty data into different data tables respectively. Data reduction is used to obtain a reduced representation of the data set, which is much smaller, but still close to maintaining the integrity of the original data. The results before and after reduction are the same or almost the same, solving the problem of very large data volume during data processing. Data cleaning converts dirty data into data that meets data quality requirements or application requirements according to data cleaning rules, and prepares for data verification. Data verification verifies the cleaned data according to relevant standards or specifications. If the verification fails, it returns to re-clean the data. When the data verification passes, it means that the data meets the requirements, and a service interface can be provided for users to use. However, a data update plan should be established before the data is updated. The plan content includes the frequency and cycle of the update, the content, scope and total amount of the data update, etc. Finally, a unified data standard is formed, including the patient theme library, the doctor's order theme library, the medical care theme library, the test report theme library, the inspection report theme library, the patient payment record theme library, the patient expense details theme library, etc.

[0069] like Fig. 9 As shown, the data synchronization and sharing process is S702: data retrieval service; S704: service sharing application; S706: service sharing approval; S708: data synchronization configuration; S710: my sharing service.

[0070] In summary, the beneficial effects of the embodiments of the present application are: 1. Improve the quality and efficiency of ward services in medical enterprises.

[0071] 2. Provide ward service decision-making for medical enterprises.

[0072] 3. Improve patient satisfaction in the ward.

[0073] 4. Improve nurses’ work efficiency.

[0074] 5. Improve the efficiency of doctors’ ward rounds.

[0075] 6. The utilization rate of medical enterprise information systems is higher.

[0076] In this application, the terms "first", "second", and "third" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance; the term "plurality" refers to two or more, unless otherwise expressly defined. Terms such as "installed", "connected", "connected", and "fixed" should be understood in a broad sense. For example, "connected" can be a fixed connection, a detachable connection, or an integral connection; "connected" can be a direct connection or an indirect connection through an intermediate medium. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to the specific circumstances.

[0077] In the description of the present application, it should be understood that the terms "upper", "lower", "front", "rear", etc., indicating directions or positional relationships, are based on the directions or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present application and simplifying the description, rather than indicating or implying that the device or module referred to must have a specific direction, be constructed and operated in a specific direction, and therefore, should not be understood as a limitation on the present application.

[0078] In the description of this specification, the description of the terms "one embodiment", "some embodiments", "specific embodiments", etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0079] The above are only preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A medical multi-source heterogeneous data collection method, characterized in that: include: Establish a standard ward subject library model, and determine data quality standards and data governance rules based on the standard ward subject library model; Obtain medical heterogeneous data sources, and connect the medical heterogeneous data sources to the local source database through the ETL process to obtain access data; Performing data governance on the access data according to the data governance rules to obtain data in a unified format, and writing the data in the unified format into a standard ward subject library; The standard ward subject library is synchronized with data.

2. The medical multi-source heterogeneous data collection method according to claim 1 is characterized in that: The obtaining of the medical heterogeneous data source and connecting the medical heterogeneous data source to the local source library through the ETL process to obtain the access data includes: Acquire a medical heterogeneous data source, and determine a calling method, a calling frequency, and an interface type according to an access method of the medical heterogeneous data source; Determine the source library model according to the data interface standard of the medical heterogeneous data source, and determine the basic governance rules for adding new data into the source library according to the data governance rules; Determine data cleaning and conversion rules based on the post source library model and the standard ward theme library model; According to the calling mode, the calling frequency, the interface type and the basic governance rules, the medical heterogeneous data source is connected to the local source library through the ETL process to obtain the access data.

3. The medical multi-source heterogeneous data collection method according to claim 2 is characterized in that: The step of performing data governance on the access data according to the data governance rules to obtain data in a unified format includes: The access data is governed according to the data cleaning and conversion rules to obtain data in a unified format, wherein the data governance includes data filtering, data conversion, data loading, data specification, data cleaning, data verification and data updating.

4. The medical multi-source heterogeneous data collection method according to claim 1, characterized in that: The data synchronization of the standard ward subject library includes: The standard ward subject library is synchronized and shared in a scheduled manner or in a real-time manner to obtain a final standard ward subject library. The data synchronization and sharing methods include one of the following or a combination thereof: data file method, http interface method, and database exchange method.

5. The medical multi-source heterogeneous data acquisition method according to claim 4 is characterized in that: The final standard ward subject library includes one of the following or a combination thereof: a patient subject library, a doctor's order subject library, a medical care subject library, a test report subject library, an examination report subject library, a patient payment record subject library, and a patient expense details subject library.

6. The medical multi-source heterogeneous data acquisition method according to any one of claims 1 to 5, characterized in that: The medical heterogeneous data source includes one of the following or a combination thereof: a relational database, a non-relational database, an API interface data, and file data; and / or The interface type of the medical heterogeneous data source includes one of the following or a combination thereof: http interface mode, file mode, DB mode, TCP / IP mode, message; and / or The data format of the medical heterogeneous data source includes one of the following or a combination thereof: Json, Xml, Tcp / Ip data packet, HL7, message string.

7. The medical multi-source heterogeneous data acquisition method according to any one of claims 1 to 5, characterized in that: The data governance rules include one of the following or a combination thereof: null value check, value range check, specification check, business logic check, duplicate data check, record authenticity check, code rationality check, update timeliness check, and data volume consistency check.

8. A medical multi-source heterogeneous data acquisition system, characterized in that: include: A model building module (110), used to build a standard ward subject library model, and determine data quality standards and data governance rules according to the standard ward subject library model; A data access module (120) is used to obtain a medical heterogeneous data source, and access the medical heterogeneous data source to a local source library through an ETL process to obtain access data; A data governance module (130) is used to perform data governance on the access data according to the data governance rules to obtain data in a unified format, and write the data in the unified format into a standard ward subject library; The data synchronization module (140) is used to synchronize data on the standard ward subject library.

9. A medical multi-source heterogeneous data acquisition system, characterized in that: include: A memory (300) and a processor (400), wherein the memory (300) stores a program or instruction that can be run on the processor (400), and when the processor (400) executes the program or the instruction, the steps of the medical multi-source heterogeneous data acquisition method as described in any one of claims 1 to 7 are implemented.

10. A readable storage medium having a program or instruction stored thereon, characterized in that: When the program or the instruction is executed by a processor, the steps of the medical multi-source heterogeneous data acquisition method as described in any one of claims 1 to 7 are implemented.

Images