Medical record data extraction script generation method and device, computer equipment and medium

Abstract

The invention provides a medical record data extraction script generation method and device, computer equipment and a medium, and relates to the technical field of medical informationization, and the method comprises the steps: extracting information of a plurality of three-party medical record fields in a three-party medical service system from an interface document of a medical record data interface in the three-party medical service system, according to the identification information of each three-party medical record field, determining identification information of a target structured medical record field matched with the three-party medical record field in a target medical service system and target library table information to which the target structured medical record field belongs, and according to a current field mapping relationship between the identification information of the three-party medical record field and the identification information of the target structured medical record field, and the target library table information, generating a target medical record data extraction script for the three-party medical service system. According to the method, automatic generation does not need to be performed by professional medical personnel, the target medical record data extraction efficiency is improved, the labor cost is reduced, and the data extraction accuracy is improved.

Description

Technical Field

[0001] The present application relates to the field of medical information technology, and in particular to a method, apparatus, computer equipment, and storage medium for generating a medical record data extraction script. Background Art

[0002] The application of electronic medical record systems in medical institutions enables medical personnel to more conveniently query and retrieve patient medical records, improving the accuracy of diagnosis and treatment plans. Furthermore, electronic medical record systems can be used to build clinical decision support systems, assisting medical personnel in making better decisions. Therefore, the medical information technology field has long been seeking methods to improve the efficiency of medical record data extraction.

[0003] Currently, medical personnel must manually copy the information of third-party medical record fields from the medical record data interface document in the third-party medical business system, and then manually compare them according to the field descriptions, and then write corresponding scripts to extract medical record data.

[0004] However, manually copying third-party medical record field information from the medical record data interface document in the third-party medical business system requires medical personnel to operate and requires a long time to generate the corresponding script. This process consumes a lot of time and human resources. However, manual extraction is prone to inaccurate or incorrect field descriptions in the copied interface document, and it cannot handle large amounts of medical record data, which reduces the efficiency of medical record data extraction. Summary of the Invention

[0005] The purpose of this application is to address the deficiencies in the above-mentioned prior art and provide a method, device, equipment and medium for generating medical record data extraction scripts, which automatically generate medical record data extraction scripts without the need for medical personnel to operate, thereby realizing the extraction of a large amount of target medical record data from the target medical business system, improving the efficiency of extracting target medical record data, reducing labor costs, and improving the accuracy of data extraction.

[0006] To achieve the above objectives, the technical solutions adopted in the embodiments of the present application are as follows:

[0007] In a first aspect, an embodiment of the present application provides a method for generating a medical record data extraction script, the method comprising:

[0008] Extracting information of a plurality of third-party medical record fields in the third-party medical business system from an interface document of a medical record data interface in the third-party medical business system, wherein the information of each third-party medical record field includes identification information of the third-party medical record field;

[0009] Determine, based on the identification information of each of the three-party medical record fields, the identification information of a target structured medical record field in the target medical service system that matches the three-party medical record field, and the target library table information to which the target structured medical record field belongs;

[0010] Generate a target medical record data extraction script for the third-party medical business system based on the current field mapping relationship between the identification information of the third-party medical record field and the identification information of the target structured medical record field, as well as the target library table information;

[0011] Among them, the target medical record data extraction script is used to extract the structured medical record data under the target structured medical record field in the target medical business system, and use the current field mapping relationship to map the structured medical record data to the corresponding third-party medical record field to obtain the target structured data extraction file for the third-party medical business system.

[0012] Optionally, determining, based on the identification information of each of the three-party medical record fields, the identification information of a target structured medical record field in a target medical service system that matches the three-party medical record field, and target library table information to which the target structured medical record field belongs, includes:

[0013] Matching the identification information of the three-party medical record fields with the identification information of multiple preset structured medical record fields in a preset medical record structured dictionary library to obtain field matching results between the three-party medical record fields and each preset structured medical record field; wherein the preset medical record structured dictionary library also stores: library table information to which each preset structured medical record field belongs;

[0014] Determining, based on the field matching result, whether there is a preset structured medical record field among the plurality of preset structured medical record fields whose matching degree satisfies a preset matching condition;

[0015] If there is a preset structured medical record field that meets the preset matching condition, the identification information of the preset structured medical record field that meets the preset matching condition is determined as the identification information of the target structured medical record field, and the target library table information is determined from the preset medical record structured dictionary library.

[0016] Optionally, the determining, based on the identification information of each of the three-party medical record fields, identification information of a target structured medical record field in a target medical service system that matches the three-party medical record field, and target library table information to which the target structured medical record field belongs, further includes:

[0017] If there is no preset structured medical record field that meets the preset matching condition, then based on the identification information of the three-party medical record field, using the preset historical medical record field mapping relationship table, determine that the identification information of the target historical structured medical record field corresponding to the three-party medical record field is the identification information of the target structured medical record field, and determine that the library table information to which the target historical structured medical record field belongs is the target library table information;

[0018] The preset historical medical record field mapping relationship table stores: historical field mapping relationships between identification information of multiple historical three-party medical record fields and identification information of historical structured medical record fields, as well as library table information to which each historical structured medical record field belongs.

[0019] Optionally, before determining, based on the identification information of the three-party medical record fields, using a preset historical medical record field mapping relationship table to determine that the identification information of the target historical structured medical record field corresponding to the three-party medical record field is the identification information of the target structured medical record field, and determining that the library table information to which the target historical structured medical record field belongs is the target library table information, the method further includes:

[0020] Extract the identification information of all medical record fields and the database table information to which all medical record fields belong from the script file of the historical medical record data extraction script;

[0021] Determining the historical field mapping relationship between the identification information of each historical three-party medical record field and the identification information of the historical structured medical record field from the identification information of all medical record fields;

[0022] The historical field mapping relationship and the library table information to which each historical structured medical record field belongs are stored in the preset historical medical record field mapping relationship table.

[0023] Optionally, the information of the three-party medical record field further includes: field type and field length information of the three-party medical record field, wherein the identification information of the three-party medical record field includes at least: field code, field name and field description information of the three-party medical record field;

[0024] The method further comprises:

[0025] Generate an original medical record field list for the third-party medical service system based on the information of the plurality of third-party medical record fields;

[0026] The original medical record field list is displayed in the interface.

[0027] Optionally, the identification information of the target structured medical record field includes at least: field code, field name and field description information of the target structured medical record field;

[0028] The method further comprises:

[0029] Generate a target medical record field list for the third-party medical business system based on the original medical record field list, the current field mapping relationship, and the target library table information;

[0030] The target medical record field list is displayed in the interface.

[0031] Optionally, the method further includes:

[0032] Extracting information of the historical medical record data interface, type information of the historical medical service targeted, and historical script content from the script file of the historical medical record data extraction script;

[0033] The information of the historical medical record data interface and the historical script content are stored in the historical three-party medical record interface record table.

[0034] In a second aspect, another embodiment of the present application provides a device for generating a medical record data extraction script, the device comprising:

[0035] An extraction module is used to extract information of multiple third-party medical record fields in the third-party medical business system from an interface document of a medical record data interface in the third-party medical business system, wherein the information of each third-party medical record field includes identification information of the third-party medical record field;

[0036] a determination module configured to determine, based on the identification information of each of the three-party medical record fields, identification information of a target structured medical record field in a target medical service system that matches the three-party medical record field, and target library table information to which the target structured medical record field belongs;

[0037] A generation module, configured to generate a target medical record data extraction script for the third-party medical business system based on the current field mapping relationship between the identification information of the third-party medical record field and the identification information of the target structured medical record field, as well as the target library table information;

[0038] Among them, the target medical record data extraction script is used to extract the structured medical record data under the target structured medical record field in the target medical business system, and use the current field mapping relationship to map the structured medical record data to the corresponding third-party medical record field to obtain the target structured data extraction file for the third-party medical business system.

[0039] In the third aspect, another embodiment of the present application provides a computer device, comprising: a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor. When the computer device is running, the processor and the storage medium communicate through the bus, and the processor executes the machine-readable instructions to perform the steps of the medical record data extraction script generation method as described in any of the first aspects above.

[0040] In a fourth aspect, another embodiment of the present application provides a storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the medical record data extraction script generation method as described in any one of the first aspects above are executed.

[0041] The beneficial effects of this application are:

[0042] The present application provides a method, device, computer equipment and storage medium for generating a medical record data extraction script. The method extracts information of multiple third-party medical record fields in a third-party medical business system from an interface document of a medical record data interface in the third-party medical business system, and determines the identification information of a target structured medical record field in the target medical business system that matches the third-party medical record field and the target library table information to which the target structured medical record field belongs based on the identification information of each third-party medical record field, thereby generating a target medical record data extraction script for the third-party medical business system based on the current field mapping relationship between the identification information of the third-party medical record field and the identification information of the target structured medical record field, as well as the target library table information. The target medical record data extraction script is used to extract structured medical record data under a target structured medical record field in the target medical business system, and uses the current field mapping relationship to map the structured medical record data to the corresponding third-party medical record field to obtain a target structured data extraction file for the third-party medical business system. In this application, based on the information of multiple third-party medical record fields extracted from the interface document of the medical record data interface in the third-party medical business system, the information extraction of the three-party medical record fields can be realized without the operation of medical personnel, and the identification information of the target structured medical record field that matches the three-party medical record field and the target library table information to which the target structured medical record field belongs are determined from the target medical business system. There is no need for medical personnel to manually match, and multiple third-party medical record fields can be matched with the target structured database field, and the target medical record data extraction script for the third-party medical business system can be directly generated. The method in this application can quickly generate a medical record data extraction script, which not only saves medical record data extraction time, but also significantly improves the efficiency of medical record data extraction script generation compared to traditional manual methods, reduces manual work, reduces labor costs, and alleviates personnel pressure. At the same time, it reduces the risk of human error, improves the accuracy of medical record data extraction, and ensures the quality of extracted data. In addition, the steps for generating the medical record data extraction script in this application are simple, the development cycle is short, and it can be put into use quickly. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other relevant drawings can be obtained based on these drawings without paying any creative work.

[0044] Figure 1 A schematic diagram of the structure of a medical record data extraction script generation system provided in an embodiment of the present application;

[0045] Figure 2A flowchart of a method for generating a medical record data extraction script provided in an embodiment of the present application;

[0046] Figure 3 A schematic diagram of the process of determining target database table information in a method for generating a medical record data extraction script provided in an embodiment of the present application;

[0047] Figure 4 A flowchart illustrating a storage mapping relationship in a method for generating a medical record data extraction script provided in an embodiment of the present application;

[0048] Figure 5 A schematic diagram of a process for displaying a list of original medical record fields in a method for generating a medical record data extraction script provided in an embodiment of the present application;

[0049] Figure 6 A flowchart of displaying a target medical record field list in a method for generating a medical record data extraction script provided in an embodiment of the present application;

[0050] Figure 7 A schematic diagram of a process for storing historical scripts in a method for generating a medical record data extraction script provided in an embodiment of the present application;

[0051] Figure 8 A schematic diagram of the structure of a medical record data extraction script generation device provided in an embodiment of the present application;

[0052] Figure 9 A schematic diagram of the computer device structure provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It should be understood that the drawings in the present application only serve the purpose of illustration and description and are not used to limit the scope of protection of the present application. In addition, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate the operations implemented according to some embodiments of the present application. It should be understood that the operations of the flowcharts can be implemented out of sequence, and steps without logical context can be reversed or implemented simultaneously. In addition, those skilled in the art, under the guidance of the contents of this application, can add one or more other operations to the flowchart, or remove one or more operations from the flowchart.

[0054] In addition, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of the present application.

[0055] It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the existence of the features declared thereafter, but does not exclude the addition of other features.

[0056] With the continuous development of the medical industry, a large amount of medical record data has accumulated in medical business systems. Medical record data is of great significance for medical research, clinical decision support, and medical service quality assessment. Currently, medical record data extraction is required in multiple medical-related scenarios. Existing methods require medical personnel to manually copy the information of third-party medical record fields from the medical record data interface of the third-party medical business system, and then manually compare and determine the corresponding target structured medical record fields from the medical business system. However, when the amount of data is large, it increases the workload of medical professionals, resulting in low data extraction efficiency and inaccurate extracted data.

[0057] To this end, the present application provides a method for generating a medical record data extraction script, which is executed by a medical record data extraction script generation system. It is worth noting that the medical business system in the present application can be any medical business system that stores patient medical records, such as an electronic medical record system, a hospital information system, a patient portal system, etc. The embodiments of the present application are not limited to this. The third-party medical business system can be any system that does not store medical record data but needs to obtain medical record data, such as an electronic health record system, a health exchange information platform, an electronic prescription system, etc.

[0058] Figure 1 This is a schematic diagram of the structure of a medical record data extraction script generation system provided in an embodiment of the present application, such as Figure 1As shown, the system includes: a basic data module, a historical script import module, an interface document extraction module, a medical record structured element intelligent matching module and a script automatic generation module, wherein the basic data module includes a medical record structured dictionary library and a predefined rule library, the medical record structured element dictionary library stores multiple medical record structured element data, the predefined rule library includes predefined rules for three-party field extraction and script generation rules, and the data in the specific medical record structured dictionary library and the predefined rule library are set according to the corresponding medical business system; the historical script import module is used to import multiple historical medical record data extraction scripts, and use the script parsing tool to parse the multiple historical medical record data extraction scripts to obtain a three-party medical record interface record table and a historical medical record field mapping relationship table, and the script parsing component can also verify the medical record data extraction script to verify whether the syntax in the medical record data extraction script is correct. The three-party medical record interface record table and the historical medical record field mapping relationship table are a one-to-many relationship, wherein the script parsing component can be Microsoft SqlServerScriptDom component; the interface document extraction module is used to extract information of multiple third-party medical record fields in the third-party medical business system from the interface document of the medical record data interface in the third-party medical business system; the medical record structured element intelligent matching module is used to match the identification information of the third-party medical record field in the third-party medical business system with the identification information of the target structured medical record field in the target medical business system, and determine the target library table information to which the target structured medical record field belongs; the script automatic generation module is used to automatically write scripts for data extraction and conversion based on the matching results of the medical record structured element intelligent matching module, based on script generation rules and accumulated experience, using the code generation engine. Among them, the medical record data extraction script generation system is a software system. The medical record data extraction script generation system can verify, adjust and optimize the generated medical record data extraction script, and allow users to optimize and customize scripts according to specific medical record structuring requirements to meet the special needs of different medical institutions and applications. The medical record data extraction script generation system is deployed with the medical record data extraction script generation method provided in the embodiment of the present application, so that the medical record data extraction script generation system executes the steps of the medical record data extraction script generation method provided in the embodiment of the present application to realize the generation of the medical record data extraction script.

[0059] For example, when a hospital receives a regional health statistics reporting instruction file and needs to upload the patient's in-process medical record homepage data to summarize the process, the patient's medical record data requires uploading about 1,000 fields of data. The user opens the interface document of the medical record data interface in the third-party medical business system to extract the interface copy form content that needs to be uploaded, and starts the interface document extraction module in the medical record data extraction script generation system. The medical record data extraction script generation system automatically analyzes and extracts the field definition, and generates the original medical record field list for user confirmation. After the user confirms, the medical record structured element intelligent matching module is started for double matching to generate the mapping relationship between the third-party medical record field and the target structured medical record field. Finally, the medical record data extraction script generation work can be completed through the script automatic generation module.

[0060] Figure 2 A flowchart of a method for generating a medical record data extraction script provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the method includes:

[0061] S201. Extract information of multiple third-party medical record fields in the third-party medical business system from the interface document of the medical record data interface in the third-party medical business system.

[0062] Among them, the information of each third-party medical record field includes: identification information of the third-party medical record field; the identification information is used to indicate the corresponding third-party medical record field, and the identification information of the third-party medical record field can be a field description of the third-party medical record field or other field identification related information, and the embodiment of the present application does not limit this. A plurality of third-party medical record fields are stored in the interface document of the medical record data interface in the third-party medical business system. According to the current requirements of the generated script, the information of the plurality of third-party medical record fields is extracted from the interface document of the medical record data interface in the third-party medical business system. The third-party medical record field can be a structure name, name, health card number, and other medical record-related fields. The method of extracting information of multiple third-party medical record fields can be to copy the information.

[0063] Optionally, according to the requirements of the current medical record data extraction script, locate in the interface document of the medical record data interface of the third-party medical business system, determine multiple third-party medical record fields corresponding to the requirements of the current generated script, and extract information of multiple third-party medical record fields.

[0064] For example, if a script for extracting admission record data needs to be generated, multiple third-party medical record fields about the admission record are determined from the interface document of the medical record data interface in the third-party medical business system, and information of the multiple third-party medical record fields is extracted.

[0065] S202. Determine, based on the identification information of each of the three-party medical record fields, the identification information of the target structured medical record field that matches the three-party medical record field in the target medical service system and the target library table information to which the target structured medical record field belongs.

[0066] The identification information of the target structured medical record field may be a field description or other information of the target structured field.

[0067] For example, based on the identification information of each third-party medical record field and the field information in the target medical business system, the identification information of the target structured medical record field that matches the third-party medical record field is determined from the target medical business system. When the identification information of the third-party medical record field matches the identification information of the target structured medical record field, the target library table information to which the target structured medical record field belongs is determined based on the identification information of the target structured medical record field.

[0068] S203. Generate a target medical record data extraction script for the third-party medical business system based on the current field mapping relationship between the identification information of the third-party medical record fields and the identification information of the target structured medical record fields, as well as the target library table information.

[0069] The target medical record data extraction script is used to extract structured medical record data under the target structured medical record fields from the target medical business system. Using the current field mapping relationship, the structured medical record data is mapped to the corresponding third-party medical record fields, resulting in a target structured data extraction file for the third-party medical business system. The target library table information indicates the specific location in the target library table corresponding to the target structured medical record field.

[0070] Optionally, the target medical record data extraction script generated for the third-party medical business system includes identification information of the third-party medical record fields and target library table information. The target medical record data extraction script generated for the third-party medical business system in this application is generated according to script generation rules and accumulated experience. The script generation rules include script rules generated based on the patient dimension, for example: associating the patient's visit information table with all business information tables generated by the patient based on the patient's serial number for each visit, distinguishing the scope of the business table based on the outpatient or inpatient type selected by the patient, judging whether the data to be extracted is code or text based on the identification information of the third-party medical record field so as to compile the corresponding script statements in a targeted manner, and automatically truncating the length according to the length required by the field in the interface document of the medical record data interface in the third-party medical business system. It is worth noting that the script generation rules in this application can also include other rules. The specific script generation rules can be set according to actual conditions, and the embodiments of this application do not require this.

[0071] Optionally, based on the identification information of the third-party medical record fields and the identification information of the target structured medical record fields, the mapping relationship between the third-party medical record fields and the target structured medical record fields is determined, and based on the target library table information corresponding to the target structured medical record fields, the information of the target library table corresponding to the mapped third-party medical record fields is determined, thereby generating a target medical record data extraction script for the third-party medical business system using a code generation engine based on script generation rules and accumulated experience.

[0072] For example, if the identification information of the third-party medical record field is RYRQ, through the mapping relationship between RYRQ and the identification information of the target structured medical record field, it is determined that the identification information of the target structured medical record field that matches the third-party medical record field in the target medical business system and the target library table information to which the target structured medical record field belongs are the inpatient homepage library. Then the target medical record data extraction script generated for the third-party medical business system is: SELECT RYRQ FROM inpatient homepage library.

[0073] The present application provides a method for generating a medical record data extraction script, which first extracts information of multiple third-party medical record fields in a third-party medical business system from the interface document of the medical record data interface in the third-party medical business system, and determines the identification information of the target structured medical record field in the target medical business system that matches the third-party medical record field and the target library table information to which the target structured medical record field belongs based on the identification information of each third-party medical record field, thereby generating a target medical record data extraction script for the third-party medical business system based on the current field mapping relationship between the identification information of the third-party medical record field and the identification information of the target structured medical record field, as well as the target library table information. The target medical record data extraction script is used to extract structured medical record data under the target structured medical record field in the target medical business system, and uses the current field mapping relationship to map the structured medical record data to the corresponding third-party medical record field to obtain a target structured data extraction file for the third-party medical business system. In this application, based on the information of multiple third-party medical record fields extracted from the interface document of the medical record data interface in the third-party medical business system, the information extraction of the three-party medical record fields can be achieved without the operation of medical professionals. The identification information of the target structured medical record field that matches the three-party medical record field and the target library table information to which the target structured medical record field belongs are determined from the target medical business system. There is no need for medical professionals to manually match, and multiple third-party medical record fields can be matched with the target structured pie field, and the target medical record data extraction script for the third-party medical business system can be directly generated. The method in this application only takes a small amount of time to import the document interface and generate the initial script, which can quickly generate the medical record data extraction script and save medical record data extraction time. In addition, the traditional manual method requires a lot of manual copying, pasting and comparison. Compared with the traditional manual method, the efficiency of generating medical record data extraction scripts in this application is significantly improved, reducing the need for manual work, reducing labor costs, and alleviating the burden on medical institutions. At the same time, it reduces the risk of human error, improves the accuracy of medical record data extraction, and ensures the quality of extracted data. In addition, the steps for generating the medical record data extraction script in this application are simple, and the development cycle is greatly shortened, allowing medical information technology projects to be put into use more quickly and providing the medical industry with faster service response speeds.

[0074] Based on the above embodiments of the present application, the following embodiments of the present application illustrate the steps of determining target library table information in the method for generating a medical record data extraction script. Figure 3 This is a flow chart of determining target database table information in a method for generating a medical record data extraction script provided in an embodiment of the present application, such as Figure 3 As described above, in S202 above, based on the identification information of each third-party medical record field, the identification information of the target structured medical record field in the target medical business system that matches the third-party medical record field, as well as the target library table information to which the target structured medical record field belongs, are determined, including:

[0075] S301. Match the identification information of the three-party medical record fields with the identification information of multiple preset structured medical record fields in the preset medical record structured dictionary library to obtain field matching results of the three-party medical record fields and each preset structured medical record field.

[0076] The preset medical record structured dictionary also stores the table information for each preset structured medical record field. The specific field content in the preset medical record structured dictionary is set based on the needs of the current medical business system. The preset medical record structured element dictionary includes patient information, medical consultation information, and medical record content structured elements, which are used to match the medical record data interface in the third-party medical business system. Patient information can include patient-related information such as name, age, and address. Medical consultation information can include patient-related data such as admission date, admission department, registration date, and registration department. Medical record content structured elements can include structured element information of medical record content such as the chief complaint, current medical history, and family history.

[0077] Optionally, the description information of each third-party medical record field and the description information of multiple preset structured medical record fields in the preset medical record structured dictionary library are matched according to the short text similarity method to obtain a matching result, and then the target library table information of the target structured medical record field that matches the third-party medical record field is determined from the library table information to which each preset structured medical record field belongs based on the matching result, wherein the short text similarity method can be the Levenshtein distance algorithm.

[0078] S302. Determine, based on the field matching result, whether there is a preset structured medical record field among the multiple preset structured medical record fields whose matching degree meets the preset matching condition.

[0079] Among them, the preset matching condition can be a preset threshold. By setting the preset threshold and comparing it with the matching result, when the matching result is greater than the preset threshold, the preset matching condition is met; when the matching result is less than the preset threshold, the preset matching condition is not met. The preset threshold can be 0.85, 0.9, 0.95 or any other number, and the embodiment of the present application does not limit this.

[0080] For example, the matching result after matching according to the short text similarity method is compared with the preset threshold. When the matching result is greater than the preset threshold, then there is a preset structured medical record field among the multiple preset structured medical record fields whose matching degree meets the preset matching conditions. When there is a matching result less than the preset threshold, then there is a preset structured medical record field among the multiple preset structured medical record fields whose matching degree does not meet the preset matching conditions.

[0081] If there is a preset structured medical record field that meets the preset matching condition, execute S303.

[0082] S303: Determine the identification information of the preset structured medical record field that meets the preset matching condition as the identification information of the target structured medical record field, and determine the target library table information from the preset medical record structured dictionary library.

[0083] Optionally, when there is a preset structured medical record field among multiple preset structured medical record fields that meets the preset matching conditions, the identification information of the corresponding preset structured medical record field is used as the identification information of the target structured medical record field, and the target library table information is determined from the preset medical record structured dictionary library based on the identification information of the corresponding preset structured medical record field.

[0084] In an embodiment of the present application, by setting preset matching conditions, the identification information that meets the preset structured medical record field is determined from the preset medical record structured dictionary library as the identification information of the target structured medical record field, and the target library table information is determined from the preset medical record structured dictionary library, thereby reducing the risk of human error, improving the accuracy of data extraction and structuring, ensuring the quality of the data, and can be set according to the specific medical business system to meet the needs of different medical business systems.

[0085] Based on the above embodiments of the present application, the following embodiments of the present application illustrate another step of determining target library table information in the method for generating a medical record data extraction script. For example, in the above S303, the identification information of the target structured medical record field that matches the third-party medical record field in the target medical business system, as well as the target library table information to which the target structured medical record field belongs, is determined based on the identification information of each third-party medical record field. The method also includes:

[0086] If there is no preset structured medical record field that meets the preset matching conditions, then based on the identification information of the three-party medical record field, the preset historical medical record field mapping relationship table is used to determine the identification information of the target historical structured medical record field corresponding to the three-party medical record field as the identification information of the target structured medical record field, and determine the library table information to which the target historical structured medical record field belongs as the target library table information.

[0087] The preset historical medical record field mapping relationship table stores the historical field mapping relationships between the identification information of multiple historical third-party medical record fields and the identification information of historical structured medical record fields, as well as the library table information to which each historical structured medical record field belongs. The identification information of the third-party fields can be one or more of the field name or field description.

[0088] Optionally, if there is no preset structured medical record field that meets the preset matching conditions, it is necessary to determine the frequency of the mapping relationship between multiple target historical structured medical record fields and the library table information to which the target historical structured medical record fields belong, sort the mapping relationships between multiple target historical structured medical record fields and the library table information to which the target historical structured medical record fields belong according to the frequency, and determine the library table information with the highest frequency corresponding to the mapping relationship corresponding to each target historical structured medical record field. Based on the identification information of the three-party medical record fields, the preset historical medical record field mapping relationship table is used to determine that the identification information of the target historical structured medical record field corresponding to the three-party medical record field is the identification information of the target structured medical record field, and determine that the library table information with the highest frequency corresponding to the mapping relationship corresponding to each target historical structured medical record field is the target library table information.

[0089] In an embodiment of the present application, by using a preset historical medical record field mapping relationship table based on the identification information of the three-party medical record fields, the identification information of the target historical structured medical record field corresponding to the three-party medical record field is determined as the identification information of the target structured medical record field, thereby determining the target library table information. This can ensure that when there is no preset structured medical record field that meets the preset matching conditions, all three-party medical record fields are matched with the structured medical record field, thereby improving the matching efficiency and reducing the matching error rate.

[0090] Based on the above embodiments of the present application, the following embodiments of the present application illustrate the steps of storing mapping relationships in the method for generating a medical record data extraction script. Figure 4 A flowchart of a storage mapping relationship in a method for generating a medical record data extraction script provided in an embodiment of the present application is shown as follows: Figure 4 As shown, before determining the identification information of the target historical structured medical record field corresponding to the three-party medical record field as the identification information of the target structured medical record field based on the identification information of the three-party medical record field and determining the library table information to which the target historical structured medical record field belongs as the target library table information, the following steps are also included:

[0091] S401. Extract identification information of all medical record fields and library table information to which all medical record fields belong from the script file of the historical medical record data extraction script.

[0092] Among them, the historical medical record data extraction script is the medical record data extraction script for all interface documents that have been connected to the medical record data interface in different third-party medical business systems. The script file includes the identification information of the medical record field and the library table to which the medical record field belongs.

[0093] Optionally, the historical data extraction script is parsed by the script parsing component to obtain a script file of the historical medical record data extraction script, and identification information of the medical record fields and library table information to which all medical record fields belong are extracted from the script file.

[0094] S402: Determine, from the identification information of all medical record fields, a historical field mapping relationship between the identification information of each historical three-party medical record field and the identification information of the historical structured medical record field.

[0095] The mapping relationship is the correspondence between the identification information of the medical record field and the identification information of the historical three-party medical record field, which can be defined by a specific medical business system to be applicable to different medical business systems.

[0096] Optionally, the historical field mapping relationship between the identification information of each historical three-party medical record field and the identification information of the historical structured medical record field is determined from the identification information of the three-party medical record field and the identification information of each historical structured medical record field.

[0097] S403: Store the historical field mapping relationship and the library table information to which each historical structured medical record field belongs into a preset historical medical record field mapping relationship table.

[0098] Among them, the preset historical medical record field mapping relationship table includes: the number of the preset historical medical record field mapping relationship table, the name of the historical three-party medical record field, the description of the historical three-party medical record field, the historical structured medical record field, the historical structured medical record field name and the library table information to which the historical structured medical record field belongs.

[0099] Optionally, based on the historical field mapping relationship between the identification information of each historical three-party medical record field and the identification information of the historical structured medical record field, as well as the library table information to which all medical record fields belong, the library table information to which each historical structured medical record field in the historical mapping relationship belongs is determined, and the historical field mapping relationship and the library table information to which each historical structured medical record field belongs are stored in a preset historical medical record field mapping relationship table.

[0100] For example, when the identification information of the historical three-party medical record field is the name of the historical three-party medical record field and the description name of the historical three-party medical record field, the identification information of the historical structured medical record field is the historical structured medical record field HZXM. At this time, the library table information corresponding to the historical structured medical record field HZXM is the inpatient homepage library, and it is stored in the preset historical medical record field mapping relationship table.

[0101] In an embodiment of the present application, by extracting the identification information of all medical record fields and the library table information to which all medical record fields belong from the script file of the historical medical record data extraction script, the historical field mapping relationship and the library table information to which each historical structured medical record field belongs are stored in a preset historical medical record field mapping relationship table, thereby improving the generation speed of the medical record data extraction script and the accuracy of the three-party medical record matching.

[0102] Based on the above embodiment of the present application, the information of the three-party medical record field also includes: the field type and field length information of the three-party medical record field, wherein the identification information of the three-party medical record field includes at least: the field code, field name and field description information of the three-party medical record field; the following embodiment of the present application describes the step of displaying the original medical record field list in the medical record data extraction script generation method, Figure 5 This is a flow chart showing the original medical record field list in a medical record data extraction script generation method provided in an embodiment of the present application, such as Figure 5 As shown, based on the above S201-S203, the method further includes:

[0103] S501. Generate an original medical record field list for a third-party medical service system based on various information of multiple third-party medical record fields.

[0104] Among them, the various information of the three-party medical record field includes: the three-party medical record field identification, the three-party medical record field type, and the three-party medical record field length. The three-party field identification includes: the three-party medical record field code, the three-party medical record field name, and the three-party medical record field description information.

[0105] Optionally, the various information of the third-party fields also includes: the precision of the third-party medical record field and the number of decimal places of the third-party medical record field, and other information related to the third-party medical record field.

[0106] Optionally, based on the information related to the three-party medical record fields, such as the three-party medical record field name, three-party medical record field code, three-party medical record field description, three-party medical record field type, three-party medical record field length, three-party medical record field precision and three-party medical record field decimal places of multiple three-party medical record fields, a corresponding original medical record field list is generated, and the three-party medical record field name, three-party medical record field code, three-party medical record field description, three-party medical record field type, three-party medical record field length, three-party medical record field precision and three-party medical record field decimal places of each three-party medical record field correspond to the information related to the three-party medical record field.

[0107] S502. Display the original medical record field list in the interface.

[0108] Among them, the fields and field information can be adjusted and corrected through the displayed original medical record field list.

[0109] For example, Table 1 is a schematic diagram of an original medical record field list provided in an embodiment of the present application. As shown in Table 1, the original medical record field list includes a third-party medical record field code, a third-party field name, a third-party medical record field type, whether it is allowed to be empty, a third-party medical record field description, and an allowed value or description. Among them, the third-party medical record field code is used to indicate the unique definition of the third-party medical record field, which is usually a short, easy-to-identify and process code used to represent specific data content; the third-party medical record field name may include the patient's personal information, condition information, and other information related to the patient's medical record, for example, it can be: USERNAME, XM and other name information; the three-party medical record field description is used to explain the meaning of each field in detail. For example, when the third-party medical record field name is USERNAME, the corresponding third-party medical record field The description is the name of the organization. When the name of the third-party medical record field is XM, the corresponding third-party medical record field description is the name; the third-party medical record field type is the type and length of the third-party field. The type of the third-party field can be any character type such as character type (String), numeric type (Numeric) or floating point type (FLOAT); the third-party medical record field can be 100 or 12, etc. The embodiment of the present application does not limit this. Whether the original medical record field list is allowed to be empty usually depends on the specific application requirements and data integrity constraints. In some cases, some fields may need to be set to N to ensure the integrity and accuracy of the data; the allowed values ​​or descriptions in the original medical record field list refer to the range of acceptable data values ​​for the field or the text description of the field. The specific data is determined according to the script generation requirements.

[0110]

[0111] Table 1 Schematic table of the original medical record field list

[0112] In an embodiment of the present application, by generating an original medical record field list for a third-party medical business system based on various information of multiple third-party medical record fields and displaying the original medical record field list in the interface, the original medical record field list can be used to determine the erroneous information in the third-party medical record fields, thereby correcting the errors and ensuring the accuracy of subsequent medical record data extraction.

[0113] Based on the above embodiment of the present application, the identification information of the target structured medical record field includes at least: the field code, field name and field description information of the target structured medical record field; the following embodiment of the present application describes the step of displaying the target medical record field list in the medical record data extraction script generation method. Figure 6 This is a flow chart of displaying a target medical record field list in a medical record data extraction script generation method provided in an embodiment of the present application, such as Figure 6 As shown, based on the above S201-S203, the method further includes:

[0114] S601. Generate a target medical record field list for the third-party medical business system based on the original medical record field list, the current field mapping relationship, and the target library table information.

[0115] Optionally, because the field definitions in the interface documents of the medical record data interfaces in the third-party medical business system vary significantly, it is necessary to convert the column names of the original medical record field list into the target column names of the target medical business system according to predefined rules for third-party field extraction. The predefined rules for third-party field extraction primarily include processing rules for converting column names in the interface document tables of the medical record data interfaces in the third-party medical business system into the system's internal field definition list. For example, if the identification information of a third-party medical record field is field name, field name, field, it is converted to field name; if the identification information of a third-party medical record field is segment description, field description, it is converted to field description; if the identification information of a third-party medical record field is data type, field type, it is converted to type, such as string, number, date, etc. Alternatively, information such as field length and whether a field is required in the identification information of the third-party medical record field may be converted, which is not limited in the present embodiment. Furthermore, based on the predefined rules for third-party field extraction and accumulated experience, field types, such as text, number, date, etc., are automatically analyzed to provide a basis for subsequent data processing.

[0116] Optionally, according to the predefined rules for third-party field extraction, the column names of the original medical record field list are converted into target column names that can be recognized by the target business system, and the information of the third-party medical record fields and the identification information of the target structured medical record fields are used to determine the current field mapping relationship, thereby generating a target medical record field list for the third-party medical business system based on the converted original medical record field list, the current mapping relationship and the target library table information.

[0117] S602. Display the target medical record field list in the interface.

[0118] Among them, the fields and mapping relationships therein can be adjusted and corrected by displaying the target medical record field list.

[0119] For example, Table 2 is a schematic diagram of a target medical record field list provided in an embodiment of the present application. As shown in Table 2, the target medical record field list includes a target medical record field code, a target medical record field name, a target medical record field description, a target medical record field type, a target medical record field length, a target medical record field precision, and a target medical record field decimal place. The target medical record field code is used to indicate the unique definition of the target medical record field, which is usually a short, easy-to-identify and process code used to represent specific data content; the target medical record field name may include the patient's personal information name, condition information name, and other information names related to the patient's medical record, such as name information such as USERNAME and XM; the target medical record field description is used to explain the meaning of each field in detail, for example, when the medical record field name When it is USERNAME, the corresponding target medical record field description is the organization name. When the party medical record field name is XM, the corresponding target medical record field description is the name. The target medical record field type can be any character type such as character type (String), numeric type (Numeric) or floating point type (FLOAT); the target medical record field length is used to indicate the maximum amount of data that the target medical record field can store, which can be 60, 100 or 12, etc. The embodiment of the present application does not limit this. The target medical record field precision is used to indicate the number of decimal places that the target medical record field can accurately represent, which is determined according to the field. For example, it can be 0, 12 or other values; the target medical record field decimal places refers to the number of digits after the decimal point that the target medical record field can represent in the database, which can affect the target medical record field precision.

[0120]

[0121] Table 2 Schematic diagram of target medical record field list

[0122] In this embodiment of the present application, a target medical record field list for a third-party medical service system is generated and displayed based on the original medical record field list, the current field mapping relationships, and the target library table information. This target medical record field list allows for adjustment and correction, and both the target medical record fields and field mapping relationships are customizable to suit specific medical data structures. This ensures accurate and reliable medical record data extraction based on inter-field correlation and data integrity, reducing matching error rates.

[0123] Based on the above embodiments of the present application, the following embodiments of the present application illustrate the steps of storing historical scripts in the method for generating medical record data extraction scripts. Figure 7 A flowchart of a historical script storage process in a method for generating a medical record data extraction script provided in an embodiment of the present application is shown as follows: Figure 7 As shown, based on the above S401-S403, the method further includes:

[0124] S701 , extracting historical medical record data interface information, targeted historical medical service type information, and historical script content from a script file of a historical medical record data extraction script.

[0125] Among them, the information of the historical medical record data interface is the medical record data interface name and interface query parameter type in the third-party medical business system. The query type can be the medical number or time period, and the type information of the historical medical business is the inpatient or outpatient type.

[0126] Optionally, the script parsing component is used to parse the historical data extraction script to obtain a script file of the historical medical record data extraction script, and the script file also stores or views the script file. Figure 3 The name of the medical record data interface in the third-party medical business system is extracted from the script file, and the interface record table number of the medical record data interface in the third-party medical business system, the interface name of the medical record data interface in the third-party medical business system, the inpatient or outpatient type, the interface query parameter type, the data extraction script content or other information related to the medical record data interface and the data extraction script in the third-party medical business system are extracted.

[0127] For example, by importing the historical data extraction script and adapting the script parsing component to parse the historical data extraction script to obtain the script file of the historical medical record data extraction script, the interface name of the medical record data interface in the third-party medical business system can be determined to be usp_emr_adminfo and the content of the medical record data extraction script.

[0128] S702. Store the information of the historical medical record data interface and the historical script content into the historical three-party medical record interface record table.

[0129] The historical three-party medical record interface record table stores: the number of the historical script file, the interface name corresponding to the historical script file, the interface query parameter type, the type information of the historical medical business targeted, and the historical script content.

[0130] Optionally, the script file of the historical medical record data extraction script obtained by parsing the historical data extraction script through the script parsing component is stored in the interface record table of the medical record data interface in the third-party medical service system.

[0131] In one possible implementation, during the process of extracting medical record data, it is determined from the historical third-party medical record interface record table whether information identical to the medical record data interface in the third-party medical business system is stored. If so, the medical record data can be extracted directly by calling the historical data extraction script corresponding to the medical record data interface in the third-party medical business system.

[0132] In an embodiment of the present application, by parsing the historical medical record data extraction script and storing the information of the historical medical record data interface and the historical script content in the historical three-party medical record interface record table, the corresponding script file can be directly called during the subsequent medical record data script generation process, thereby improving the generation efficiency of the medical record data extraction script.

[0133] Based on the same inventive concept, the embodiment of the present application also provides a medical record data extraction script generation device corresponding to the medical record data extraction script generation method. Since the principle of solving the problem by the device in the embodiment of the present application is similar to the above-mentioned medical record data extraction script generation method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0134] Figure 8 A schematic diagram of the structure of a medical record data extraction script generation device provided in an embodiment of the present application, the device comprising: an extraction module 81, a determination module 82, and a generation module 83;

[0135] The extraction module 81 is used to extract information of multiple third-party medical record fields in the third-party medical business system from the interface document of the medical record data interface in the third-party medical business system, and the information of each third-party medical record field includes: identification information of the third-party medical record field;

[0136] A determination module 82 is configured to determine, based on the identification information of each of the three-party medical record fields, the identification information of a target structured medical record field in the target medical service system that matches the three-party medical record field, as well as target library table information to which the target structured medical record field belongs;

[0137] A generating module 83 is used to generate a target medical record data extraction script for the third-party medical business system based on the current field mapping relationship between the identification information of the third-party medical record field and the identification information of the target structured medical record field, as well as the target library table information;

[0138] Among them, the target medical record data extraction script is used to extract the structured medical record data under the target structured medical record field in the target medical business system, and use the current field mapping relationship to map the structured medical record data to the corresponding third-party medical record field to obtain the target structured data extraction file for the third-party medical business system.

[0139] In one possible implementation, the determination module 82 is specifically configured to match identification information of the medical record fields of the three parties with identification information of multiple preset structured medical record fields in a preset medical record structured dictionary library to obtain field matching results between the medical record fields of the three parties and each preset structured medical record field; wherein the preset medical record structured dictionary library further stores library table information to which each preset structured medical record field belongs;

[0140] Determine, based on the field matching result, whether there is a preset structured medical record field among the multiple preset structured medical record fields whose matching degree meets the preset matching condition;

[0141] If there is a preset structured medical record field that meets the preset matching conditions, the identification information of the preset structured medical record field that meets the preset matching conditions is determined as the identification information of the target structured medical record field, and the target library table information is determined from the preset medical record structured dictionary library.

[0142] In one possible implementation, the determination module 82 is specifically configured to: if there is no preset structured medical record field that meets the preset matching condition, determine, based on the identification information of the three-party medical record field, using a preset historical medical record field mapping relationship table, the identification information of the target historical structured medical record field corresponding to the three-party medical record field as the identification information of the target structured medical record field, and determine the library table information to which the target historical structured medical record field belongs as the target library table information;

[0143] The preset historical medical record field mapping relationship table stores: the historical field mapping relationship between the identification information of multiple historical third-party medical record fields and the identification information of historical structured medical record fields, as well as the library table information to which each historical structured medical record field belongs.

[0144] In a possible implementation, the determination module 82 is further configured to: extract identification information of all medical record fields and library table information to which all medical record fields belong from a script file of a historical medical record data extraction script;

[0145] Determine, from the identification information of all medical record fields, a historical field mapping relationship between the identification information of each historical third-party medical record field and the identification information of the historical structured medical record field;

[0146] The historical field mapping relationship and the library table information to which each historical structured medical record field belongs are stored in a preset historical medical record field mapping relationship table.

[0147] In one possible implementation, the information of the third-party medical record fields further includes: field type and field length information of the third-party medical record fields, wherein the identification information of the third-party medical record fields includes at least: field code, field name, and field description information of the third-party medical record fields; the apparatus further includes: a first display module, the first display module being specifically configured to: generate a list of original medical record fields for the third-party medical business system based on various information of the plurality of third-party medical record fields;

[0148] Display the original medical record field list in the interface.

[0149] In one possible implementation, the identification information of the target structured medical record field includes at least: a field code, a field name, and a field description of the target structured medical record field; the apparatus further includes: a second display module, the second display module being specifically configured to: generate a target medical record field list for the third-party medical business system based on the original medical record field list, the current field mapping relationship, and the target library table information;

[0150] Display the target medical record field list in the interface.

[0151] In one possible implementation, the determination module 82 is further configured to extract information about a historical medical record data interface, information about the type of historical medical services targeted, and content of the historical script from a script file of a historical medical record data extraction script;

[0152] The information of the historical medical record data interface and the historical script content are stored in the historical three-party medical record interface record table.

[0153] For descriptions of the processing flow of each module in the device and the interaction flow between each module, reference can be made to the relevant descriptions in the above method embodiment, which will not be described in detail here.

[0154] The embodiment of the present application also provides a computer device, Figure 9 A schematic diagram of the computer device structure provided in the embodiment of the present application is shown in FIG. Figure 9 As shown, the computer device includes: a processor 91, a memory 92, and optionally, a bus 93. The memory 92 stores machine-readable instructions executable by the processor 91. When the computer device is running, the processor 91 communicates with the memory 92 via the bus 93. When the machine-readable instructions are executed by the processor 91, the steps of the above-mentioned medical record data extraction script generation method are performed.

[0155] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the above-mentioned method for generating a medical record data extraction script are executed.

[0156] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system and device described above can refer to the corresponding process in the method embodiment, and will not be repeated in this application. In the several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0157] In addition, the functional units in the various embodiments of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0158] The above is only a specific implementation method of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the protection scope of the present application.

Claims

1. A method for generating a medical record data extraction script, characterized in that: The method comprises: Extracting information of a plurality of third-party medical record fields in the third-party medical business system from an interface document of a medical record data interface in the third-party medical business system, wherein the information of each third-party medical record field includes identification information of the third-party medical record field; Determine, based on the identification information of each of the three-party medical record fields, the identification information of a target structured medical record field in the target medical service system that matches the three-party medical record field, and the target library table information to which the target structured medical record field belongs; Generate a target medical record data extraction script for the third-party medical business system based on the current field mapping relationship between the identification information of the third-party medical record field and the identification information of the target structured medical record field, as well as the target library table information; Among them, the target medical record data extraction script is used to extract the structured medical record data under the target structured medical record field in the target medical business system, and use the current field mapping relationship to map the structured medical record data to the corresponding third-party medical record field to obtain the target structured data extraction file for the third-party medical business system.

2. The method for generating a medical record data extraction script according to claim 1, wherein: The step of determining, based on the identification information of each of the three-party medical record fields, the identification information of the target structured medical record field in the target medical service system that matches the three-party medical record field, and the target library table information to which the target structured medical record field belongs, includes: Matching the identification information of the three-party medical record fields with the identification information of multiple preset structured medical record fields in a preset medical record structured dictionary library to obtain field matching results between the three-party medical record fields and each preset structured medical record field; wherein the preset medical record structured dictionary library also stores: library table information to which each preset structured medical record field belongs; Determining, based on the field matching result, whether there is a preset structured medical record field among the plurality of preset structured medical record fields whose matching degree satisfies a preset matching condition; If there is a preset structured medical record field that meets the preset matching condition, the identification information of the preset structured medical record field that meets the preset matching condition is determined as the identification information of the target structured medical record field, and the target library table information is determined from the preset medical record structured dictionary library.

3. The method for generating a medical record data extraction script according to claim 2, wherein: The method further includes determining the identification information of a target structured medical record field in a target medical service system that matches the third-party medical record field and target library table information to which the target structured medical record field belongs based on the identification information of each of the third-party medical record fields: If there is no preset structured medical record field that meets the preset matching condition, then based on the identification information of the three-party medical record field, using the preset historical medical record field mapping relationship table, determine that the identification information of the target historical structured medical record field corresponding to the three-party medical record field is the identification information of the target structured medical record field, and determine that the library table information to which the target historical structured medical record field belongs is the target library table information; The preset historical medical record field mapping relationship table stores: historical field mapping relationships between identification information of multiple historical three-party medical record fields and identification information of historical structured medical record fields, as well as library table information to which each historical structured medical record field belongs.

4. The method for generating a medical record data extraction script according to claim 3, wherein: Before determining, based on the identification information of the medical record fields of the three parties and using a preset historical medical record field mapping relationship table to determine that the identification information of the target historical structured medical record field corresponding to the medical record fields of the three parties is the identification information of the target structured medical record field, and determining that the library table information to which the target historical structured medical record field belongs is the target library table information, the method further includes: Extract the identification information of all medical record fields and the database table information to which all medical record fields belong from the script file of the historical medical record data extraction script; Determining the historical field mapping relationship between the identification information of each historical three-party medical record field and the identification information of the historical structured medical record field from the identification information of all medical record fields; The historical field mapping relationship and the library table information to which each historical structured medical record field belongs are stored in the preset historical medical record field mapping relationship table.

5. The method for generating a medical record data extraction script according to claim 1, wherein: The information of the three-party medical record field also includes: field type and field length information of the three-party medical record field, wherein the identification information of the three-party medical record field includes at least: field code, field name and field description information of the three-party medical record field; The method further comprises: Generate an original medical record field list for the third-party medical service system based on the information of the plurality of third-party medical record fields; The original medical record field list is displayed in the interface.

6. The method for generating a medical record data extraction script according to claim 5, wherein: The identification information of the target structured medical record field includes at least: the field code, field name and field description information of the target structured medical record field; The method further comprises: Generate a target medical record field list for the third-party medical business system based on the original medical record field list, the current field mapping relationship, and the target library table information; The target medical record field list is displayed in the interface.

7. The method for generating a medical record data extraction script according to claim 4, wherein: The method further comprises: Extracting information of the historical medical record data interface, type information of the historical medical service targeted, and historical script content from the script file of the historical medical record data extraction script; The information of the historical medical record data interface and the historical script content are stored in the historical three-party medical record interface record table.

8. A device for generating a medical record data extraction script, characterized in that: The device comprises: An extraction module is used to extract information of multiple third-party medical record fields in the third-party medical business system from an interface document of a medical record data interface in the third-party medical business system, wherein the information of each third-party medical record field includes identification information of the third-party medical record field; a determination module configured to determine, based on the identification information of each of the three-party medical record fields, identification information of a target structured medical record field in a target medical service system that matches the three-party medical record field, and target library table information to which the target structured medical record field belongs; A generation module, configured to generate a target medical record data extraction script for the third-party medical business system based on the current field mapping relationship between the identification information of the third-party medical record field and the identification information of the target structured medical record field, as well as the target library table information; Among them, the target medical record data extraction script is used to extract the structured medical record data under the target structured medical record field in the target medical business system, and use the current field mapping relationship to map the structured medical record data to the corresponding third-party medical record field to obtain the target structured data extraction file for the third-party medical business system.

9. A computer device, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores program instructions executable by the processor. When the computer device is running, the processor and the storage medium communicate through the bus, and the processor executes the program instructions to perform the steps of the medical record data extraction script generation method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The storage medium stores a computer program, which, when executed by a processor, executes the steps of generating a medical record data extraction script as described in any one of claims 1 to 7.

Images