Derivative metadata construction method and device

Abstract

The embodiment of the present invention discloses a method and device for constructing derived metadata. The method determines a derived data source and each native metadata selected from the derived data source, and obtains a preset derivation strategy corresponding to the derived metadata, and then determines the described data corresponding to the derived metadata based on the preset derivation strategy and the described data corresponding to each native metadata in the derived data source, thereby realizing automatic construction of derived metadata. The method determines the described data corresponding to the derived metadata through the preset derivation strategy, so that the construction of the derived metadata meets the predefined calculation rules, solves the result deviation caused by subjective reasons when constructing the derived metadata manually, improves the creation accuracy of the derived metadata, and ensures the consistency of the derived metadata.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of metadata technology, and in particular to a method and device for constructing derived metadata. Background Art

[0002] Metadata can be data that describes data, while derived metadata cannot be directly obtained, that is, it does not exist directly in the database and needs to be derived according to business needs. In the original medical business software database, multi-dimensional data centered on patients is provided. After users obtain data for scientific research or other purposes, they often need to organize it by themselves and calculate data that meets the needs of the current scenario.

[0003] For example, the first preoperative hemoglobin value does not exist in the metadata. Therefore, the detailed data corresponding to the first preoperative hemoglobin value cannot be directly extracted, and the user needs to customize and complete the corresponding calculation workload. However, this method of manually defining and calculating the described data corresponding to the derived metadata may result in different derived metadata results due to subjective cognitive bias when different users need to obtain the same derived metadata, which in turn affects the development of subsequent related businesses. Summary of the invention

[0004] The embodiments of the present invention provide a method and device for constructing derived metadata to solve the technical problem that the creation result of derived metadata is biased due to subjective reasons.

[0005] In a first aspect, an embodiment of the present invention provides a method for constructing derived metadata, the method comprising:

[0006] Determine a derived data source and each native metadata selected from the derived data source, wherein the derived data source includes described data corresponding to each native metadata;

[0007] Get the preset derivation strategy corresponding to the derived metadata;

[0008] Based on the preset derivation strategy and the described data corresponding to each of the native metadata, the described data corresponding to the derived metadata is determined.

[0009] Optionally, the method further includes:

[0010] Get the derived configuration information corresponding to the derived metadata;

[0011] A preset derivation strategy corresponding to the derived metadata is determined based on the derived configuration information.

[0012] Optionally, the determining, based on the derived configuration information, a preset derivation strategy corresponding to the derived metadata includes:

[0013] Determine a sample data source and each sample metadata selected from the sample data source, wherein the sample data source includes described data corresponding to each sample metadata;

[0014] Determining preview information corresponding to the derived metadata based on the derived configuration information and the described data corresponding to each of the sample metadata;

[0015] A verification result of the preview information is obtained, and if the verification result is that the verification passes, the derived configuration information is determined as a preset derivation strategy corresponding to the derived metadata.

[0016] Optionally, the determining, based on the derived configuration information and the described data corresponding to each of the sample metadata, preview information corresponding to the derived metadata includes:

[0017] Determine a data operation statement corresponding to the derived metadata based on the derived configuration information;

[0018] Based on the data operation statement and the described data corresponding to each of the sample metadata, the preview information corresponding to the derived metadata is determined.

[0019] Optionally, determining the data operation statement corresponding to the derived metadata based on the derived configuration information includes:

[0020] Acquire keyword information configured by the user for the operation keyword in the technical view interface, and determine the keyword information as derived configuration information;

[0021] A data operation statement corresponding to the derived metadata is generated based on the derived configuration information.

[0022] Optionally, the method further includes:

[0023] Determine the number of calls of the preset derivative strategy corresponding to each of the derivative metadata;

[0024] Based on each of the call counts, determining precipitation metadata in each of the derived metadata;

[0025] The sedimentation metadata is added as native metadata to the technical view interface.

[0026] Optionally, determining the precipitation metadata in each of the derived metadata based on each of the call times includes:

[0027] For each of the derived metadata, the derived metadata whose call times meet a preset number threshold is determined as the deposited metadata; or,

[0028] The derived metadata are sorted in descending order of the number of calls, and the deposited metadata is determined based on the sorting result.

[0029] Optionally, the determining of the derived data source and each native metadata selected from the derived data source includes:

[0030] Displaying each preset data source in a technical view interface, obtaining a drag operation or a creation operation performed by a user in the technical view interface, and determining a derived data source based on the drag operation or the creation operation;

[0031] The native metadata included in the derived data source is displayed in the technical view interface, a selected operation performed by the user in the technical view interface is obtained, and the native metadata selected by the user from the derived data source is determined based on the selected operation.

[0032] Optionally, displaying each preset data source in the technical view interface includes:

[0033] In the technical view interface, each preset data source included in at least one logical layer is displayed;

[0034] Among them, the logical layer is a data lake layer, a data center layer, a data domain layer or a data mart layer.

[0035] In a second aspect, an embodiment of the present invention further provides a derived metadata construction device, the device comprising:

[0036] A metadata determination module, used to determine a derived data source and each native metadata selected from the derived data source, wherein the derived data source includes described data corresponding to each native metadata;

[0037] A strategy acquisition module, used to acquire a preset derivation strategy corresponding to the derived metadata;

[0038] The policy execution module is used to determine the described data corresponding to the derived metadata based on the preset derived policy and the described data corresponding to each of the native metadata.

[0039] In a third aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising:

[0040] one or more processors;

[0041] a storage device for storing one or more programs,

[0042] When the one or more programs are executed by the one or more processors, the one or more processors implement the derived metadata construction method provided by any embodiment of the present invention.

[0043] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a derivative metadata construction method as provided in any embodiment of the present invention.

[0044] The embodiments of the above invention have the following advantages or beneficial effects:

[0045] By determining a derived data source and each native metadata selected from the derived data source, and obtaining a preset derivation strategy corresponding to the derived metadata, and then determining the described data corresponding to the derived metadata based on the preset derivation strategy and the described data corresponding to each native metadata in the derived data source, the automatic construction of the derived metadata is realized. The method determines the described data corresponding to the derived metadata through the preset derivation strategy, so that the construction of the derived metadata meets the predefined calculation rules, solves the result deviation caused by subjective reasons when constructing the derived metadata manually, improves the creation accuracy of the derived metadata, and ensures the consistency of the derived metadata. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the following briefly introduces the drawings required to describe the embodiments. Obviously, the drawings introduced are only drawings of a part of the embodiments to be described in the present invention, rather than all the drawings. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0047] Figure 1A A schematic diagram of a flow chart of a method for constructing derived metadata provided in the first embodiment of the present invention;

[0048] Figure 1B A schematic diagram of a display interface provided in Embodiment 1 of the present invention;

[0049] Figure 2 A schematic diagram of a flow chart of a method for constructing derived metadata provided in the second embodiment of the present invention;

[0050] Figure 3 A schematic diagram of a flow chart of a method for constructing derived metadata provided by Embodiment 3 of the present invention;

[0051] Figure 4 A schematic diagram of a flow chart of a method for constructing derived metadata provided by Embodiment 4 of the present invention;

[0052] Figure 5 A schematic diagram of the structure of a derived metadata construction device provided in Embodiment 5 of the present invention;

[0053] Figure 6This is a structural schematic diagram of an electronic device provided in Embodiment 6 of the present invention. DETAILED DESCRIPTION

[0054] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0055] Embodiment 1

[0056] Figure 1A A flowchart of a derived metadata construction method provided in the first embodiment of the present invention is provided. This embodiment is applicable to the case where described data corresponding to derived metadata is determined according to a derived data source selected by a user and each native metadata selected by the user in the derived data source. It is particularly applicable to pre-constructing a preset derivation strategy corresponding to the derived metadata for each derived metadata. Then, when the user selects the derived data source and each native metadata, the derived metadata is constructed by the preset derivation strategy corresponding to the derived metadata, that is, determining the described data corresponding to the derived metadata. The method can be executed by a derived metadata construction device, which can be implemented by hardware and / or software. The method specifically includes the following steps:

[0057] S110: Determine a derived data source and each native metadata selected from the derived data source, wherein the derived data source includes described data corresponding to each native metadata.

[0058] Among them, the derived data source can be a database or data set of native data needed to create derived metadata. Exemplarily, the derived data source can be provided by a clinical data center, a scientific research data center, an operation data center, or an indicator data center. Specifically, the derived data source stores the described data corresponding to each native metadata; the described data corresponding to the native metadata can be the data described by the native metadata, for example, if the native metadata is the patient's name, then the described data corresponding to the native metadata is the actual patient names stored in the derived data source, such as Zhang San, Li Si, etc.

[0059] In this embodiment, determining the derived data source may include: monitoring the operation events of the user on the display interface or the triggering controls of the user on the display interface, and determining the derived data source based on the monitored operation events or triggering controls. That is, this embodiment may determine the data source currently created or selected by the user as the derived data source. For example, Figure 1BAs shown, a schematic diagram of a display interface is shown, on the left side of the display interface, controls corresponding to various existing data sources can be displayed, such as test report data source, surgical record data source, hospitalization information data source, patient information data source, payment record data source, etc., and on the right side of the display interface, various native metadata contained in the currently selected derived data source can be displayed. Specifically, the controls triggered by the user can be monitored, and the derived data source can be determined based on the controls triggered by the user, such as when the user selects the test report data source. Of course, the user's creation operation on the display interface can also be monitored, and a derived data source can be generated based on the user's creation operation. For example, if the existing data sources currently displayed cannot meet the user's selection requirements, the user can generate a new derived data source by triggering the creation control.

[0060] After the derived data source is determined, the native metadata selected by the user from the derived data source can be further determined. Exemplarily, if the derived data source is determined, that is, it is determined that the user selects or creates the derived data source, all the native metadata included in the derived data source can be displayed to the user, and then the native metadata selected by the user from all the displayed native metadata can be determined. The native metadata selected from the derived data source can be the metadata required to create the derived metadata. Figure 1B , Figure 1B The right side of the data shows the various native metadata contained in the test report data source (the derived data source selected by the user), such as verification sub-item name = white blood cells, white blood cell test value, test time, verification sub-item name = platelet, platelet test value, etc. The user selected verification sub-item name = white blood cells, white blood cell test value and test time from the displayed native metadata.

[0061] It should be noted that the number of derived data sources can be one or more, that is, this embodiment does not limit the number of derived data sources selected by the user. For example, the derived metadata that the user currently needs to create is the preoperative white blood cell count, however, the metadata of "preoperative white blood cell count" does not exist in any of the existing data sources. Therefore, based on the derived metadata construction method provided in this embodiment, the test report data source and the surgical record data source can be selected as the derived data sources in turn, and metadata such as white blood cells, white blood cell test value, and test time of the test sub-item name are selected from the test report data source, and metadata such as surgical time are selected from the surgical record data source, and then the derived metadata is constructed based on the selected metadata.

[0062] S120: Obtain a preset derivation strategy corresponding to the derived metadata.

[0063] The preset derivation strategy may be a calculation rule of the predefined derived metadata. Specifically, for each derived metadata, a corresponding preset derivation strategy may be formulated in advance for the derived metadata, and the preset derivation strategy corresponding to each derived metadata may be stored in a strategy database. If it is necessary to create derived metadata, the preset derivation strategy corresponding to the derived metadata may be read from the strategy database.

[0064] In this embodiment, the preset derivation strategy can specifically be a data operation statement, such as a SQL (Structured Query Language) statement. By pre-establishing the preset derivation strategy corresponding to each derived metadata, when constructing the derived metadata, the user only needs to select the derived data source and the native metadata to realize the automatic construction of the derived metadata.

[0065] It should be noted that this embodiment does not limit the execution order of S110 and S120. That is, S110 and S120 may be executed simultaneously, or S120 may be executed before S110, etc.

[0066] S130 : Determine the described data corresponding to the derived metadata based on the preset derivation strategy and the described data corresponding to each native metadata.

[0067] Specifically, this embodiment can perform data processing on the described data corresponding to each native metadata through the calculation rules in the preset derivation strategy corresponding to the derived metadata, obtain the described data corresponding to the derived metadata, and realize the construction of the derived metadata.

[0068] Exemplarily, after obtaining the derived data source, each native metadata selected in the derived data source, and the preset derivation strategy corresponding to the derived metadata, the described data corresponding to each native metadata can be read from the derived data source, and the SQL statement corresponding to the derived metadata can be executed on the read data to obtain a result set returned after executing the SQL statement, wherein the result set includes the described data corresponding to the derived metadata. Alternatively, the SQL statement can be directly executed in the derived data source, and the described data corresponding to each native metadata selected in the derived data source can be processed through the calculation rules in the SQL statement to obtain a returned result set, i.e., the described data corresponding to the derived metadata.

[0069] Among them, the calculation rule may refer to a rule for processing the described data corresponding to each selected native metadata to generate the described data corresponding to the derived metadata. Exemplarily, the derived metadata may be the total cost of a patient's visit, the derived data source is the patient test data source, the patient registration data source, and the patient hospitalization data source, the native metadata includes metadata such as patient test costs, patient registration costs, and patient hospitalization costs, and the calculation rule in the preset derivative strategy may be to add the described data corresponding to the metadata such as patient test costs, patient registration costs, and patient hospitalization costs in each derived data source, that is, to add the actual values ​​of each patient's patient test costs, patient registration costs, and patient hospitalization costs, and obtain the actual value of each patient's total cost of visit, that is, the described data corresponding to the derived metadata.

[0070] For example, if the derived metadata is the preoperative prothrombin test value, the preset derivation strategy (SQL statement) corresponding to the derived metadata may be as follows:

[0071] SELECT"Empiid"AS empiId,patientname AS valueCol,lastimportdttm AScreateTime,lastupdatedttm AS lastUpdateTime,"Empiid"AS primaryCol

[0072] FROM pa_patientinfo

[0073] WHERE sexname = 'Coagulation Routine'

[0074] OR sexname = 'Prothrombin time'

[0075] For another example, if the derived metadata is a self-paying patient during hospitalization, the preset derived strategy (SQL statement) corresponding to the derived metadata may be as follows:

[0076] SELECT a.medicalrecordno AS vkey,a."Empiid"AS empiId,a.ybname ASvalueCol,a.lastimportdttm AS createTime,a.lastupdatedttm AS lastUpdateTime

[0077] ,a."Empiid"AS primaryCol

[0078] FROM pa_patientinfo a

[0079] WHERE a.ybname = 'Self-paid hospitalization'

[0080] In this embodiment, S110-S130 may be performed by a derived data configuration component. Specifically, the derived data configuration component may include a derived data source docking function, a data source dragging function, a derived strategy generation function, a derived strategy search function, and a derived metadata generation function. Among them, the data source dragging function may be to obtain the derived data source and native metadata selected by the user's dragging operation; the derived data source docking function may be to connect the derived data source; the derived strategy generation function may be to obtain the preset derived strategy configured by the user; the derived strategy search function may be to search for the preset derived strategy corresponding to the derived metadata that the user currently needs to generate; the derived metadata generation function may be to generate the described data corresponding to the derived metadata according to the derived data source, native metadata, and preset derived strategy.

[0081] That is, this embodiment can provide a derived data configuration component, which can obtain the derived data source selected by the user and the native metadata selected from the derived data source, and calculate the described data corresponding to the derived metadata according to the preset derivative strategy corresponding to the derived metadata, and feedback the described data corresponding to the derived metadata.

[0082] The technical solution of this embodiment realizes automatic construction of derived metadata by determining a derived data source and each native metadata selected from the derived data source, and obtaining a preset derivation strategy corresponding to the derived metadata, and then determining the described data corresponding to the derived metadata based on the preset derivation strategy and the described data corresponding to each native metadata in the derived data source. This method realizes the determination of the described data corresponding to the derived metadata through the preset derivation strategy, so that the construction of the derived metadata meets the predefined calculation rules, solves the result deviation caused by subjective reasons when constructing the derived metadata manually, improves the creation accuracy of the derived metadata, and ensures the consistency of the derived metadata.

[0083] Embodiment 2

[0084] Figure 2 This is a flow chart of a method for constructing derived metadata provided by Embodiment 2 of the present invention. Based on the above embodiments, this embodiment optionally further includes: obtaining derived configuration information corresponding to the derived metadata; and determining a preset derived strategy corresponding to the derived metadata based on the derived configuration information. Explanations of terms that are the same or corresponding to the above embodiments are not repeated here. Figure 2 The derived metadata construction method provided in this embodiment includes the following steps:

[0085] S210: Obtain derivative configuration information corresponding to the derived metadata, and determine a preset derivative strategy corresponding to the derived metadata based on the derivative configuration information.

[0086] The derived configuration information may be predefined configuration information required to generate derived metadata. Optionally, the derived configuration information may be a SQL statement; or, the derived configuration information may be keyword information used to generate a SQL statement, the keywords including but not limited to select, from, where, having, orderby and groupby.

[0087] It should be noted that, in this embodiment, the user can pre-configure each derived metadata to construct a corresponding preset derivation strategy for each derived metadata. That is, the derivative configuration information corresponding to each derived metadata can be obtained, and the preset derivation strategy corresponding to each derived metadata can be determined based on the derivative configuration information corresponding to each derived metadata.

[0088] In one implementation, the derived configuration information corresponding to the derived metadata entered by the user may be obtained, and the data operation statement (such as SQL statement) corresponding to the derived configuration information may be directly determined as the preset derived strategy corresponding to the derived metadata.

[0089] In another embodiment, after obtaining the derived configuration information entered by the user, the derived configuration information may be verified, and if the verification is passed, the data operation statement corresponding to the derived configuration information is determined as the preset derived strategy. Exemplarily, the method of determining the preset derived strategy corresponding to the derived metadata based on the derived configuration information includes: determining a sample data source and each sample metadata selected from the sample data source, wherein the sample data source includes the described data corresponding to each sample metadata; determining the preview information corresponding to the derived metadata based on the derived configuration information and the described data corresponding to each sample metadata; obtaining the verification result of the preview information, and if the verification result is that the verification is passed, determining the derived configuration information as the preset derived strategy corresponding to the derived metadata.

[0090] The sample data source may be a database or data set of sample native data selected or constructed by the user, and the sample metadata may be metadata selected by the user from the sample data source. Exemplarily, the step of determining preview information corresponding to the derived metadata based on the derived configuration information and the described data corresponding to each sample metadata includes: determining data operation statements corresponding to the derived metadata based on the derived configuration information; and determining preview information corresponding to the derived metadata based on the data operation statements and the described data corresponding to each sample metadata.

[0091] Specifically, the described data corresponding to the sample metadata selected in the sample data source can be processed according to the data operation statement, and the result of the processing can be determined as the described data corresponding to the derived metadata, that is, the preview information corresponding to the derived metadata. The derived configuration information can be a data operation statement or keyword information. Optionally, the data operation statement corresponding to the derived metadata based on the derived configuration information can be: obtaining keyword information configured by the user for the operation keyword in the technical view interface, determining the keyword information as the derived configuration information; and generating a data operation statement corresponding to the derived metadata based on the derived configuration information.

[0092] The operation keywords include but are not limited to select, from, where, having, orderby, and groupby. The technical view interface can display each keyword, and the user can configure at least one keyword; further, the keyword information configured by the user is used as derived configuration information, and data operation statements are automatically generated according to the derived configuration information (keyword information).

[0093] Furthermore, based on the processing results of the described data corresponding to each sample metadata selected in the sample data source by the data operation statement, the described data corresponding to the derived metadata, that is, the preview information corresponding to the derived metadata, is obtained, the preview information is displayed, and the verification result of the preview information fed back by the user is obtained. When the verification result is passed, it indicates that the derived configuration information complies with the calculation rules of the derived metadata, and the preset derivation strategy can be determined based on it.

[0094] Through the above optional implementation, it is also possible to achieve: if there is no preset derivative strategy corresponding to the derived metadata that the user currently needs to construct, the derived configuration information entered by the user can be obtained, and the described data corresponding to the derived metadata can be determined based on the derived configuration information currently entered by the user; and the described data corresponding to the derived metadata can also be displayed, and the verification result fed back by the user can be obtained. If the verification result is that the verification passes, the preset derivative strategy can be determined based on the derived configuration information.

[0095] That is, in the process of constructing derived metadata, users can select derived data sources, select native metadata, and set derived configuration information to realize the construction of derived metadata. If the construction result of derived metadata is correct, a preset derivative strategy can be generated according to the derived configuration information. The preset derivative strategy can be provided to third-party applications (such as big data search engines, hospital platforms, etc.), and third-party applications can quickly realize the construction of derived metadata by calling the preset derivative strategy, so that users no longer need to manually configure the calculation rules of derived metadata.

[0096] In this optional implementation, preview information corresponding to the derived metadata, that is, the described data corresponding to the derived metadata, is generated through the derived configuration information, and then a preset derivative strategy is generated based on the verification result of the preview information, thereby realizing automatic verification of the preset derivative strategy; and, the preset derivative strategy can also be determined according to the derived configuration information defined by the user in real time, thereby realizing automatic generation of the preset derivative strategy, thereby realizing subsequent rapid construction of the derived metadata.

[0097] S220: Determine a derived data source and each native metadata selected from the derived data source, wherein the derived data source includes described data corresponding to each native metadata.

[0098] S230: Obtain a preset derivation strategy corresponding to the derived metadata, and determine the described data corresponding to the derived metadata based on the preset derivation strategy and the described data corresponding to each of the native metadata.

[0099] The technical solution of this embodiment determines the preset derivation strategy corresponding to the derived metadata through the derived configuration information corresponding to the derived metadata, thereby realizing the pre-construction of the preset derivation strategy. Through the method provided by this embodiment, the preset derivation strategy corresponding to each derived metadata can be generated in advance, and then the derived metadata can be quickly constructed through each preset derivation strategy, so that the construction of the derived metadata meets the pre-defined calculation rules, solves the result deviation caused by subjective reasons when constructing the derived metadata manually, improves the creation accuracy of the derived metadata, and ensures the consistency of the derived metadata.

[0100] Embodiment 3

[0101] Figure 3 This is a flowchart of a method for constructing derived metadata provided by Embodiment 3 of the present invention. Based on the above embodiments, this embodiment optionally further includes: determining the number of calls of a preset derivative strategy corresponding to each derived metadata; determining the sedimentation metadata in each derived metadata based on each call number; and adding the sedimentation metadata as native metadata to the technical view interface. The explanations of the terms that are the same or corresponding to the above embodiments are not repeated here. Figure 3 , the derivative metadata construction method provided in this embodiment includes the following steps:.

[0102] S310: Obtain derivative configuration information corresponding to the derived metadata, and determine a preset derivative strategy corresponding to the derived metadata based on the derivative configuration information.

[0103] S320: Determine a derived data source and each native metadata selected from the derived data source, wherein the derived data source includes described data corresponding to each native metadata.

[0104] S330: Obtain a preset derivation strategy corresponding to the derived metadata, and determine the described data corresponding to the derived metadata based on the preset derivation strategy and the described data corresponding to each native metadata.

[0105] S340: Determine the number of calls of the preset derivative strategy corresponding to each derivative metadata, determine the sedimentation metadata in each derivative metadata based on the number of calls, and add the sedimentation metadata as native metadata to the technical view interface.

[0106] Specifically, in this embodiment, after generating corresponding preset derivative strategies for each derived metadata in advance, the number of calls of each preset derivative strategy can be counted. If the number of calls of the preset derivative strategy is greater, it indicates that the derived metadata corresponding to the preset derivative strategy has more application scenarios in business needs (such as application scenarios of clinical business, application scenarios of scientific research business, etc.).

[0107] In this embodiment, data precipitation processing can be performed on each derived metadata according to the number of calls of each preset derivative strategy. Specifically, the derived metadata corresponding to the preset derivative strategy with a large number of calls can be determined as precipitation metadata, wherein the precipitation metadata can be the derived metadata added to the technical view interface as native metadata. In other words, this embodiment can determine the derived metadata corresponding to the preset derivative strategy with a large number of calls as native metadata, and display it as native metadata in the technical view interface, so that the user can use the native metadata to construct other derived metadata.

[0108] Exemplarily, determining the sedimentation metadata in each derived metadata based on each call count includes: for each derived metadata, determining the derived metadata whose call count meets a preset number threshold as the sedimentation metadata; or sorting the derived metadata in descending order of each call count, and determining the sedimentation metadata based on the sorting result.

[0109] The preset number threshold may be a preset threshold for depositing derived metadata, such as 10 times, 15 times, etc., which is not limited in this application. Derived metadata with a call count greater than or equal to the preset number threshold may be determined as deposited metadata; or, the derived metadata may be sorted in descending order according to the call count, and the top N derived metadata in the sorting result may be taken as deposited metadata.

[0110] In this embodiment, while adding the precipitation metadata as native metadata to the technical view interface, the storage location of the precipitation metadata can also be customized, and the associated database or associated data table of the precipitation metadata can be saved in the library table specified by the user.

[0111] The technical solution of this embodiment counts the number of calls of the preset derivative strategy corresponding to each derived metadata, determines the sedimented metadata in each derived metadata based on the number of calls, and adds the sedimented metadata as native metadata to the technical view interface, thereby realizing the conversion of derived metadata with many application scenarios. By sedimenting the derived metadata with many application scenarios into native metadata, the user no longer needs to construct such derived metadata, and the user can quickly use such derived metadata, such as selecting such derived metadata to construct other derived metadata.

[0112] Embodiment 4

[0113] Figure 4 A flowchart of a method for constructing derived metadata is provided for the fourth embodiment of the present invention. In this embodiment, based on the above embodiments, optionally, the determination of the derived data source and the native metadata selected from the derived data source includes: displaying each preset data source in the technical view interface, obtaining the drag operation or creation operation performed by the user in the technical view interface, and determining the derived data source based on the drag operation or creation operation; displaying each native metadata included in the derived data source in the technical view interface, obtaining the selected operation performed by the user in the technical view interface, and determining each native metadata selected by the user from the derived data source based on the selected operation. The explanations of the terms that are the same or corresponding to the above embodiments are not repeated here. See. Figure 4 The derived metadata construction method provided in this embodiment includes the following steps:

[0114] S410: Display each preset data source in the technical view interface, obtain a drag operation or a creation operation performed by the user in the technical view interface, and determine a derived data source based on the drag operation or the creation operation.

[0115] The preset data source may be any pre-created data source. The technical view interface may be such as Figure 1B The display interface shown can display each preset data source and each native metadata contained in each preset data source. This embodiment does not limit the display form of the technical view interface. Specifically, this embodiment can display each existing preset data source in the technical view interface, and determine the derived data source according to the user's drag operation or creation operation on each preset data source in the technical view interface.

[0116] Optionally, the display of each preset data source in the technical view interface includes: in the technical view interface, displaying each preset data source contained in at least one logical layer; wherein the logical layer is a data lake layer, a data center layer, a data domain layer or a data mart layer. The preset data source in the data lake layer can be a complete copy of the real-time business library of each hospital site; the preset data source in the data center layer can be the data after the preliminary integration of the preset data sources in the data lake layer; the preset data source in the data domain layer can be the data after the preset data sources of different logical layers are processed according to preset standards and the preset data sources in the data center layer are integrated together; the preset data source in the data mart layer can be the derivative data generated when the hospital project is used.

[0117] In this embodiment, illustratively, the preset data source targeted by the user's drag operation in the technical view interface may be determined as the derived data source; or the preset data source generated by the user's creation operation may be determined as the derived data source.

[0118] S420: Display each native metadata included in the derived data source in the technical view interface, obtain a selected operation performed by the user in the technical view interface, and determine each native metadata selected by the user from the derived data source based on the selected operation.

[0119] Specifically, after determining the derived data source, all native metadata contained in the derived data source can be displayed in the technical view interface, and the user's operation events in the technical view interface can be monitored to obtain the selected operations performed by the user in the technical view interface, and the native metadata selected by the user from the derived data source can be determined based on the selected operations.

[0120] S430: Obtain a preset derivation strategy corresponding to the derived metadata, and determine the described data corresponding to the derived metadata based on the preset derivation strategy and the described data corresponding to each native metadata.

[0121] The technical solution of this embodiment, by displaying various preset data sources in a technical view interface, obtaining a drag operation or a creation operation performed by a user in the technical view interface, determining a derived data source based on the drag operation or the creation operation, and further displaying various native metadata included in the derived data source in the technical view interface, obtaining a selection operation performed by a user, and determining various native metadata selected by the user from the derived data source based on the selection operation, realizes the determination of the derived data source and the native metadata required for constructing the derived metadata, and further realizes the automatic construction of the derived metadata based on the derived data source and the native metadata selected by the user.

[0122] Embodiment 5

[0123] Figure 5A schematic diagram of the structure of a derived metadata construction device provided in Embodiment 5 of the present invention. This embodiment is applicable to determining the described data corresponding to the derived metadata according to the derived data source selected by the user and the native metadata selected by the user in the derived data source, and is particularly applicable to pre-constructing a preset derivation strategy corresponding to the derived metadata for each derived metadata, and then constructing the derived metadata according to the preset derivation strategy corresponding to the derived metadata when the user selects the derived data source and the native metadata, that is, determining the described data corresponding to the derived metadata. The device specifically includes: a metadata determination module 510, a strategy acquisition module 520 and a strategy execution module 530.

[0124] The metadata determination module 510 is used to determine a derived data source and each native metadata selected from the derived data source, wherein the derived data source includes the described data corresponding to each native metadata;

[0125] A strategy acquisition module 520, used to acquire a preset derivation strategy corresponding to the derived metadata;

[0126] The policy execution module 530 is used to determine the described data corresponding to the derived metadata based on the preset derived policy and the described data corresponding to each of the native metadata.

[0127] Optionally, the device also includes a policy generation module, which includes a configuration acquisition unit and a policy generation unit; the configuration acquisition unit is used to acquire derived configuration information corresponding to the derived metadata; the policy generation unit is used to determine a preset derived policy corresponding to the derived metadata based on the derived configuration information.

[0128] Optionally, the strategy generation unit includes an acquisition unit, a preview unit and a verification unit, wherein the acquisition unit is used to determine a sample data source and each sample metadata selected from the sample data source, wherein the sample data source includes described data corresponding to each sample metadata; the preview unit is used to determine preview information corresponding to the derived metadata based on the derived configuration information and the described data corresponding to each sample metadata; the verification unit is used to obtain a verification result of the preview information, and if the verification result is a passed verification, the derived configuration information is determined as a preset derivative strategy corresponding to the derived metadata.

[0129] Optionally, the preview unit includes a statement generation unit and a preview generation unit, the statement generation unit is used to determine the data operation statement corresponding to the derived metadata based on the derived configuration information; the preview generation unit is used to determine the preview information corresponding to the derived metadata based on the data operation statement and the described data corresponding to each of the sample metadata.

[0130] Optionally, the statement generation unit is specifically used to obtain keyword information configured by the user for the operation keyword in the technical view interface, determine the keyword information as derived configuration information; and generate a data operation statement corresponding to the derived metadata based on the derived configuration information.

[0131] Optionally, the device also includes a sedimentation module, which includes a number statistics unit, a sedimentation unit and an adding unit; wherein the number statistics unit is used to determine the number of calls of the preset derivative strategy corresponding to each of the derived metadata; the sedimentation unit is used to determine the sedimentation metadata in each of the derived metadata based on the number of calls; the adding unit is used to add the sedimentation metadata as native metadata to the technical view interface.

[0132] Optionally, the frequency statistics unit is specifically used to determine, for each of the derived metadata, the derived metadata whose call times meet a preset time threshold as the sedimentation metadata; or, to sort the derived metadata in descending order of the call times, and determine the sedimentation metadata based on the sorting result.

[0133] Optionally, the metadata determination module 510 includes a first determination unit and a second determination unit; wherein the first determination unit is used to display each preset data source in the technical view interface, obtain the drag operation or creation operation performed by the user in the technical view interface, and determine the derived data source based on the drag operation or creation operation; the second determination unit is used to display each native metadata contained in the derived data source in the technical view interface, obtain the selected operation performed by the user in the technical view interface, and determine each native metadata selected by the user from the derived data source based on the selected operation.

[0134] Optionally, the first determination unit is specifically used to display various preset data sources contained in at least one logical layer in the technical view interface; wherein the logical layer is a data lake layer, a data center layer, a data domain layer or a data mart layer.

[0135] In this embodiment, the metadata determination module determines the derived data source and each native metadata selected from the derived data source, and the policy acquisition module obtains the preset derivation policy corresponding to the derived metadata. Then, the policy execution module determines the described data corresponding to the derived metadata based on the preset derivation policy and the described data corresponding to each native metadata in the derived data source, thereby realizing automatic construction of the derived metadata. This method realizes the determination of the described data corresponding to the derived metadata through the preset derivation policy, so that the construction of the derived metadata meets the predefined calculation rules, solves the result deviation caused by subjective reasons when constructing the derived metadata manually, improves the creation accuracy of the derived metadata, and ensures the consistency of the derived metadata.

[0136] The derived metadata construction device provided in the embodiment of the present invention can execute the derived metadata construction method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0137] It is worth noting that the various units and modules included in the above system are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present invention.

[0138] Embodiment 6

[0139] Figure 6 It is a structural schematic diagram of an electronic device provided in Embodiment 6 of the present invention. Figure 6 A block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention is shown. Figure 6 The electronic device 12 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention. The device 12 is typically an electronic device that is responsible for determining the derivative metadata creation function.

[0140] like Figure 6 As shown, the electronic device 12 is in the form of a general purpose computing device. The components of the electronic device 12 may include, but are not limited to: one or more processors or processing units 16, a memory 28, and a bus 18 connecting the various components (including the memory 28 and the processing unit 16).

[0141] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. For example, these architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0142] The electronic device 12 typically includes a variety of computer readable media. These media can be any available media that can be accessed by the electronic device 12, including volatile and non-volatile media, removable and non-removable media.

[0143] The memory 28 may include computer device readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The electronic device 12 may further include other removable / non-removable, volatile / non-volatile computer storage media. By way of example only, the storage device 34 may be used to read and write non-removable, non-volatile magnetic media ( Figure 6 not shown, usually called a "hard drive"). Although Figure 6 Not shown, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a read-only optical disk (Compact Disc-Read Only Memory, CD-ROM), a digital video disk (Digital Video Disc-Read Only Memory, DVD-ROM) or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The memory 28 may include at least one program product 40, which has a set of program modules 42, which are configured to perform the functions of various embodiments of the present invention. The program product 40 may be stored in, for example, the memory 28, and such program modules 42 include, but are not limited to, one or more application programs, other program modules, and program data, each of which or some combination may include the implementation of a network environment. The program module 42 generally performs the functions and / or methods in the embodiments described in the present invention.

[0144] The electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, mouse, camera, etc., and display), may also communicate with one or more devices that enable a user to interact with the electronic device 12, and / or communicate with any device that enables the electronic device 12 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 22. In addition, the electronic device 12 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN) and / or a public network, such as the Internet) through a network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 12 through a bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, disk arrays (Redundant Arrays of Independent Disks, RAID) devices, tape drives, and data backup storage devices.

[0145] The processor 16 executes various functional applications and data processing by running the program stored in the memory 28, for example, implementing the derived metadata construction method provided in the above embodiment of the present invention, including:

[0146] Determine a derived data source and each native metadata selected from the derived data source, wherein the derived data source includes described data corresponding to each native metadata;

[0147] Get the preset derivation strategy corresponding to the derived metadata;

[0148] Based on the preset derivation strategy and the described data corresponding to each of the native metadata, the described data corresponding to the derived metadata is determined.

[0149] Of course, those skilled in the art can understand that the processor can also implement the technical solution of the derivative metadata construction method provided by any embodiment of the present invention.

[0150] Embodiment 7

[0151] Embodiment 7 of the present invention further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps of the method for constructing derived metadata provided in any embodiment of the present invention are implemented. The method includes:

[0152] Determine a derived data source and each native metadata selected from the derived data source, wherein the derived data source includes described data corresponding to each native metadata;

[0153] Get the preset derivation strategy corresponding to the derived metadata;

[0154] Based on the preset derivation strategy and the described data corresponding to each of the native metadata, the described data corresponding to the derived metadata is determined.

[0155] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0156] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0157] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0158] Computer program code for performing the operation of embodiments of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0159] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for constructing derived metadata, characterized in that: The method comprises: Determine a derived data source and each native metadata selected from the derived data source, wherein the derived data source includes described data corresponding to each native metadata; Get the preset derivation strategy corresponding to the derived metadata; Based on the preset derivation strategy and the described data corresponding to each native metadata, determining the described data corresponding to the derived metadata includes: reading the described data corresponding to each native metadata from the derived data source, executing the preset derivation strategy on the described data, and obtaining a result set returned after executing the preset derivation strategy; the result set includes the described data corresponding to the derived metadata.

2. The method according to claim 1, characterized in that: The method further comprises: Get the derived configuration information corresponding to the derived metadata; A preset derivation strategy corresponding to the derived metadata is determined based on the derived configuration information.

3. The method according to claim 2, characterized in that The determining, based on the derived configuration information, a preset derivation strategy corresponding to the derived metadata includes: Determine a sample data source and each sample metadata selected from the sample data source, wherein the sample data source includes described data corresponding to each sample metadata; Determining preview information corresponding to the derived metadata based on the derived configuration information and the described data corresponding to each of the sample metadata; A verification result of the preview information is obtained, and if the verification result is that the verification passes, the derived configuration information is determined as a preset derivation strategy corresponding to the derived metadata.

4. The method according to claim 3, characterized in that The determining, based on the derived configuration information and the described data corresponding to each sample metadata, preview information corresponding to the derived metadata includes: Determine a data operation statement corresponding to the derived metadata based on the derived configuration information; Based on the data operation statement and the described data corresponding to each of the sample metadata, the preview information corresponding to the derived metadata is determined.

5. The method according to claim 4, characterized in that The determining, based on the derived configuration information, a data operation statement corresponding to the derived metadata includes: Acquire keyword information configured by the user for the operation keyword in the technical view interface, and determine the keyword information as derived configuration information; A data operation statement corresponding to the derived metadata is generated based on the derived configuration information.

6. The method according to claim 2, characterized in that The method further comprises: Determine the number of calls of the preset derivative strategy corresponding to each of the derivative metadata; Based on each of the call counts, determining the precipitation metadata in each of the derived metadata; The sedimentation metadata is added as native metadata to the technical view interface.

7. The method according to claim 6, characterized in that The step of determining the precipitation metadata in each of the derived metadata based on each of the call times includes: For each of the derived metadata, the derived metadata whose call times meet a preset number threshold is determined as the deposited metadata; or, The derived metadata are sorted in descending order of the number of calls, and the deposited metadata is determined based on the sorting result.

8. The method according to claim 1, characterized in that The determining of the derived data source and each native metadata selected from the derived data source includes: Displaying each preset data source in a technical view interface, obtaining a drag operation or a creation operation performed by a user in the technical view interface, and determining a derived data source based on the drag operation or the creation operation; The native metadata included in the derived data source is displayed in the technical view interface, a selected operation performed by the user in the technical view interface is obtained, and the native metadata selected by the user from the derived data source is determined based on the selected operation.

9. A derivative metadata construction device, characterized in that: The device comprises: A metadata determination module, used to determine a derived data source and each native metadata selected from the derived data source, wherein the derived data source includes described data corresponding to each native metadata; A strategy acquisition module, used to acquire a preset derivation strategy corresponding to the derived metadata; A policy execution module, configured to determine the described data corresponding to the derived metadata based on the preset derived policy and the described data corresponding to each of the native metadata; The policy execution module is specifically used to read the described data corresponding to each native metadata from the derived data source, execute the preset derived policy on the described data, and obtain a result set returned after executing the preset derived policy; the result set includes the described data corresponding to the derived metadata.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the derived metadata construction method as described in any one of claims 1 to 8 is implemented.

Images