Metadata processing method, apparatus, device, and storage medium

Abstract

This specification provides a method, apparatus, device, and storage medium for processing metadata. The method includes: receiving medical data provided by a first database; the medical data including first metadata; determining second metadata relative to a second database based on a preset metadata mapping rule; the second metadata indicating the storage location of the medical data in the second database; storing the first and second metadata in a first storage medium, for retrieving the second metadata from the first storage medium in response to a query request for medical data including the first metadata, to obtain the medical data from the second database; wherein the first storage medium has better read performance than the second database. By storing the first metadata for the first database and the second metadata for the second database in the first storage medium during medical data synchronization, the rate of metadata query can be improved.

Description

Technical Field

[0001] The embodiments described in this specification relate to the field of data processing, specifically to a method, apparatus, device, and storage medium for processing metadata. Background Technology

[0002] Currently, due to the high sparsity of medical data, vertical tables are often used for storage. For example, medical data can be stored using an EAV database model, allowing for easy addition or removal of attributes. However, vertical tables are not conducive to data querying and analysis. Therefore, existing technologies extract medical data from the EAV database model and store it using a query-friendly data storage structure, allowing data retrieval within this structure. However, data analysis systems often use metadata specific to the original storage structure for data queries. To query medical data within a more readable data storage structure, metadata transformation is required, leading to frequent access to metadata and increased database read pressure.

[0003] Therefore, existing technologies present a technical problem of high access pressure on metadata during medical data querying. Summary of the Invention

[0004] In view of this, various embodiments of this specification aim to provide a method, apparatus, device, and medium for querying medical data tables, thereby improving the query speed of metadata to a certain extent.

[0005] This specification provides a method for processing metadata through multiple embodiments. The method includes: receiving medical data provided by a first database; wherein the medical data includes first metadata; the first metadata describes the data attributes of the medical data; determining second metadata of the first metadata relative to a second database according to a preset metadata mapping rule; wherein the second metadata indicates the storage location of the medical data in the second database; the first database and the second database have different storage methods; storing the first metadata and the second metadata in a first storage medium, for retrieving the second metadata from the first storage medium in response to a query request for the medical data including the first metadata, so as to obtain the medical data in the second database; wherein the read performance of the first storage medium is better than that of the second database.

[0006] One embodiment of this specification provides a metadata processing apparatus, the apparatus comprising: a receiving module for receiving medical data provided by a first database; wherein the medical data includes first metadata; the first metadata describes the data attributes of the medical data; a determining module for determining second metadata of the first metadata relative to a second database according to a preset metadata mapping rule; wherein the second metadata indicates the storage location of the medical data in the second database; the first database and the second database have different storage methods; and a storage module for storing the first metadata and the second metadata in a first storage medium, and for extracting the second metadata from the first storage medium in response to a query request for the medical data including the first metadata, so as to obtain the medical data in the second database; wherein the read performance of the first storage medium is better than that of the second database.

[0007] One embodiment of this specification provides a computer device including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program as any one of the above embodiments.

[0008] One embodiment of the specification provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in any one of the above embodiments.

[0009] The various embodiments provided in this specification involve receiving medical data with accompanying first metadata and determining second metadata relative to a second database according to a preset metadata mapping rule. Next, the first metadata and the corresponding second metadata are stored in a first storage medium. This storage medium is used to extract the second metadata corresponding to the first metadata upon receiving a query request for medical data with accompanying first metadata. Furthermore, the medical data is retrieved from the second database according to the second metadata and fed back to the medical data transmission method. Attached Figure Description

[0010] Figure 1 This is a schematic diagram of the architecture of a metadata processing system provided for one embodiment of this specification.

[0011] Figure 2 This is a flowchart illustrating a metadata processing method provided for one embodiment of this specification.

[0012] Figure 3 This is a schematic diagram illustrating a metadata processing method provided in one embodiment of this specification.

[0013] Figure 4 This is a schematic diagram illustrating a metadata processing method provided in one embodiment of this specification.

[0014] Figure 5 This is a schematic diagram of a metadata processing apparatus provided for one embodiment of this specification.

[0015] Figure 6 A schematic diagram of a computer device provided for one embodiment of this specification. Detailed Implementation

[0016] Overview

[0017] In related technologies, medical data, due to its strong sparsity, may require maintaining a large number of tables if stored in a horizontal relational database, with each table containing only a small amount of medical data, which is detrimental to data relationships. Therefore, medical data can be stored in vertical tables. For example, the EAV data model can be used to store medical data. However, medical data stored in the EAV data model faces the problem of cumbersome data querying. To address this, an easily readable data storage structure can be constructed from the medical data. This allows for data querying within this more accessible structure. However, data analysis systems often use metadata specific to the original storage structure for data queries. To query medical data in the more accessible structure, metadata conversion is required, leading to frequent access to metadata and increased database read pressure.

[0018] Therefore, it is necessary to propose a metadata processing method that receives medical data with accompanying first metadata and determines the second metadata of the first metadata relative to a second database according to a preset metadata mapping rule. Then, the first metadata and the corresponding second metadata are stored in a first storage medium. This storage medium is used to extract the second metadata corresponding to the first metadata when a query request for medical data with accompanying first metadata is received. Furthermore, the medical data is retrieved from the second database according to the second metadata and fed back to the medical data sending method.

[0019] System Architecture

[0020] Please see Figure 1This specification provides a metadata processing system. The metadata processing system may include multiple servers. Each server may be equipped with a data platform, a first database, a second database, and a second storage medium for storing metadata. In some embodiments, the data platform has a first storage medium. For example, the first storage medium may be the memory of the data platform. The data platform may receive medical data provided by the first database and store the medical data in a designated location within the second database.

[0021] The server can be an electronic device with a certain computing power. It may include a network communication module, a processor, and a memory. Alternatively, the server can refer to software running on the electronic device. The server can also be a distributed server, a system with multiple processors, memory, network communication modules, etc., operating collaboratively. Or, the server can be a server cluster formed by several servers. Furthermore, with the development of science and technology, the server can also be a new technological means capable of realizing the corresponding functions of the embodiments described in the specification. For example, it could be a new form of "server" based on quantum computing.

[0022] Example method

[0023] Please see Figure 2 This specification provides a method for processing metadata in one embodiment. The metadata processing method can be applied to a server. The server may be equipped with a data middleware platform. The metadata processing method may include the following steps.

[0024] Step S110: Receive medical data provided by a first database; wherein the medical data is accompanied by first metadata; the first metadata is used to describe the data attributes of the medical data.

[0025] In some cases, medical data stored in vertical tables in a first database can be periodically extracted to form wide tables for medical data querying and analysis. However, this may result in poor real-time performance of the medical data in the wide tables. Therefore, medical data in the first database can be synchronized to a second database in real time. Simultaneously, first metadata for the medical data is constructed, and second metadata for the second database is created. Both the first metadata and the corresponding second metadata are stored in a first storage medium. This allows the second metadata corresponding to the first metadata to be extracted from the first storage medium when a query request for medical data with the first metadata is received, enabling the retrieval of the medical data in the second database based on the second metadata. This reduces the read pressure on the metadata in the database.

[0026] The medical data can represent data from the medical field. Specifically, the medical data can be values ​​from data within the medical field. For example, the medical data can represent blood pressure values, red blood cell counts, etc.

[0027] The first database can represent a database storing medical data. Specifically, the first database may include multiple vertical tables. The medical data can be stored in the vertical tables of the first database. For example, the first database can be a database built using the EAV database model. The first database may include a value table for storing medical data, an attribute table for storing the medical attributes corresponding to the medical data, and an entity table for storing the medical entities corresponding to the medical data. Alternatively, the first database may be constructed using only a single vertical table, which may include the medical entities, medical attributes, and medical data.

[0028] The first metadata can be metadata specific to the first database. The first metadata can be used to describe the data attributes of the medical data. Specifically, the data attributes of the medical data may include medical attributes of the medical data, the medical entity corresponding to the medical data, and the generation time of the medical data, etc., used to describe the medical data. Based on the first metadata, the target medical data can be retrieved from the first database.

[0029] The method for receiving medical data provided by the first database can be that the server hosting the first database sends the medical data to a server with a data platform deployed thereon, and the server receives the data. Alternatively, the method can also be that the server hosting the first database sends the medical data to a server with a data platform deployed thereon via an intermediary server, and the server receives the data.

[0030] Step S120: Determine the second metadata of the first metadata relative to the second database according to the preset metadata mapping rules; wherein, the second metadata is used to indicate the storage location of the medical data in the second database; the storage methods of the first database and the second database are different.

[0031] In some cases, based on preset metadata mapping rules, the second metadata in the second database can be determined from the first metadata. Furthermore, storing the first metadata and its corresponding second metadata allows for retrieving the medical data corresponding to the first metadata from the second database upon receiving a query request containing the first metadata. This improves the convenience of medical data retrieval.

[0032] The second database can represent a database used to store the medical data and has a data storage structure that is easy to query. For example, the second database can be a columnar storage database. The second database may include an identifier field for storing logical table identifiers and a data field for storing medical data. At least one data field can be used to store multiple categories of medical data. For details, please refer to [link to relevant documentation]. Figure 3 Columns 1, 2, 3, and 4 can be data fields, while the logical table identifiers represent fields. In records with IDs 1 and 3, column 1 stores the medical data for the name "Zhang San" and ID number "3*****************X," respectively. This demonstrates that different types of medical data can be stored in the data fields. To distinguish the medical attributes corresponding to the medical data in the data fields of different records, logical table identifiers can be used. Specifically, a logical table identifier can correspond to a logical field, which can be used to indicate the medical data corresponding to the medical data in the same record as the corresponding logical table identifier. For example, for a record with logical table identifier T1, the medical data in columns 1, 2, 3, and 4 can represent name, gender, age, and height, respectively. In some embodiments, the second database can also be multiple wide tables. In some embodiments, the horizontal tables of the second database can also include identifier fields storing medical entity identifiers. Different entity identifiers can correspond to different logical fields.

[0033] Furthermore, the first database and the second database use different storage methods. Specifically, for example, the first database may store medical data using a vertical table, while the second database may store medical data using a horizontal table. Alternatively, the second database may be a columnar database, etc.

[0034] The second metadata can represent metadata specific to the second database. This second metadata is used to indicate the storage location of the medical data within the second database. For example, the second metadata can be used to indicate target data tables, target fields, and target records within the second database.

[0035] The metadata mapping rules can be pre-defined rules for determining the second metadata corresponding to the first metadata. For example, the first database can be an EAV database. The medical data in the first database can correspond to medical forms, medical entities, and medical attributes. The second database can be a columnar storage database. The second data can include two identification fields: an identification field storing medical entity identifiers and an identification field storing logical table identifiers. Accordingly, the metadata mapping rules can specify that medical forms in the first database are mapped to the identification field storing logical table identifiers in the second database, medical entities in the first database are mapped to the identification field storing medical entity identifiers in the second database, and medical data in the first database are mapped to data fields in the second database. Furthermore, in the data fields of records corresponding to the same medical entity and logical table, each data field can only be associated with one type of medical data. For example, please refer to... Figure 4 The first set of medical data provided by the first database can be the name "Zhang San" and blood sugar "6". Accordingly, the name can be associated with data field column 1, and blood sugar with column 2, forming logical fields in logical table T1. The medical forms provided by the first database correspond to the logical table identifiers in the second database. The medical entities provided by the first database correspond to the medical entity identifiers in the second database. Further, the second set of medical data provided by the first database can be the name "Zhang San" and blood pressure "100", and the second set of medical data corresponds to the same medical form and medical entity as the first set. Since the name is already associated with column 1, "Zhang San" from the second set of medical data can be stored in column 1. Blood pressure has no associated data field, and column 2 is associated with blood sugar. Therefore, the blood pressure value can be stored in the unassociated data field column 3.

[0036] After determining the storage location of the medical data in the first database in the horizontal table of the second database through metadata mapping rules, the second metadata of the first metadata relative to the second database can be determined according to the preset metadata mapping rules.

[0037] Step S130: The first metadata and the second metadata are stored in a first storage medium for retrieving the second metadata from the first storage medium in response to a query request for the medical data accompanied by the first metadata, so as to obtain the medical data in the second database; wherein the read performance of the first storage medium is better than that of the second database.

[0038] In some cases, medical data analysis systems or other systems that need to query medical data may frequently access metadata when accessing the medical data. Storing the metadata in a database could increase the pressure on the database. Therefore, the metadata can be stored on a first storage medium. The first storage medium has better read performance than a second database, thus effectively reducing the access pressure on the database.

[0039] The first storage medium can represent memory or a local cache. The read performance of the first storage medium can be superior to that of the second database. Alternatively, the read performance of the first storage medium can also be superior to that of the second database. Querying the first metadata and second metadata in the first storage medium takes less time. In some embodiments, medical data provided by the first database is synchronized to the second database. The first storage medium can store first metadata and second metadata corresponding to different medical data. Upon receiving a query request for target medical data, the second metadata corresponding to the first metadata can be retrieved from the first storage medium based on the first metadata attached to the query request, and the target medical data can be retrieved from the second database using the second metadata.

[0040] In some embodiments, the method for processing the metadata may further include: sending the medical data to the second database so that the medical data is stored in the second database at the storage location indicated by the second metadata.

[0041] In some cases, after determining the first metadata relative to the second metadata of the second database, the medical data can be sent to the second database so that the medical data is stored in the storage location indicated by the second metadata in the second database. The synchronization process of the medical data and the process of determining the first metadata and its corresponding second metadata are performed simultaneously, which can facilitate the construction of a metadata processing system. At the same time, it can also reduce the probability of mismatch between the medical data in the second database and the first and second metadata to a certain extent. Furthermore, performing the synchronization process of the medical data and the process of determining the first metadata and its corresponding second metadata simultaneously can also improve the real-time performance of the medical data.

[0042] In some embodiments, the method for processing the metadata may further include: persistently storing the first metadata and the second metadata in a second storage medium.

[0043] In some cases, the superior read performance of the first storage medium may lead to poor stability of the data stored there. Therefore, to avoid the loss of both the first and second metadata, they can be persistently stored in the second storage medium to improve the stability of medical data storage to some extent.

[0044] The second storage medium can represent a persistent storage unit. Specifically, for example, the second storage medium can be a Redis database. Of course, the second storage medium can also be a first database or a second database.

[0045] In some embodiments, the method for processing the metadata may further include: receiving a first query request for the medical data; wherein the first query request includes the first metadata; querying the second metadata corresponding to the first metadata in the first storage medium; if the second metadata is not present in the first storage medium, querying the second metadata in the second storage medium; and sending a second query request for the medical data including the second metadata to the second database, so as to return the medical data fed back by the second database to the sender of the first query request.

[0046] In some cases, the read performance of the first storage medium may be superior to that of the second storage medium. However, the data storage stability of the first storage medium may be slightly weaker than that of the second storage medium. Specifically, for example, the first storage medium could be memory, and the second storage medium could be a Redis database. Therefore, during medical data retrieval, based on the received first metadata, the corresponding second metadata can be queried from the first storage medium first. This can improve the metadata retrieval speed to some extent. If the second metadata is not present in the first storage medium, it can be retrieved from the second storage medium, thereby improving the reliability of metadata retrieval to some extent.

[0047] The method of sending a second query request to the second database containing the medical data along with the second metadata, and returning the medical data from the second database to the sender of the first query request, can, according to preset rules, transform a first query instruction including the first metadata in the first query request into a second query instruction including the second metadata. Specifically, for example, both the second and first query instructions can be constructed using SQL statements. For instance, the first query instruction might target a horizontal table storing medical data. The first query instruction could be "select a,b from form_1". Correspondingly, the second query instruction targets a second database containing only one horizontal table, form_0. This horizontal table can include an identifier field storing logical table identifiers. The logical table identifier can be used to indicate the medical form corresponding to each record in the target database's data table. Correspondingly, the second query instruction could be "select a,b from form_0 where form_id == 1". Furthermore, the second query instruction can be used to query target medical data in the second database. Alternatively, the method of constructing the second query instruction can be based on a preset template of correspondence between query instruction keywords. The second metadata corresponding to the first metadata is filled into the template to obtain the second query instruction.

[0048] In some embodiments, the metadata processing method may further include: if the second metadata corresponding to the first metadata does not exist in the first storage medium, reading the second metadata from the second storage medium and storing it in the first storage medium.

[0049] In some cases, where the second metadata corresponding to the first metadata does not exist in the first storage medium but the first metadata exists in the second storage medium, the first metadata and the corresponding second metadata can be read from the second storage medium and stored in the first storage medium. Upon receiving a medical data query request accompanied by the first metadata, the second metadata corresponding to the first metadata can be directly matched in the first storage medium. Furthermore, the target medical data can be retrieved from the second database based on the second metadata.

[0050] In some embodiments, the first storage medium is server memory, and the metadata processing method may further include: clearing the metadata in the server memory when the amount of metadata stored in the server memory is greater than a specified threshold.

[0051] In some cases, memory capacity is limited. Cached primary and secondary metadata in memory indefinitely can lead to memory overflow. To address this, some implementations set expiration times for the primary and secondary metadata in memory. However, even with a large amount of medical data, memory overflow can still occur. Therefore, memory monitoring can be implemented, and if memory usage exceeds a certain threshold, the primary and secondary metadata stored in server memory can be cleared. By preventing memory overflow, memory utilization can be significantly improved.

[0052] The cleanup process can involve deleting the oldest metadata stored in memory. Alternatively, it can involve deleting the least frequently used metadata. In some implementations, it can also involve issuing a warning.

[0053] In some implementations, the first metadata includes medical attributes of the medical data and the medical form to which the medical data belongs; the second database includes at least one horizontal table; the horizontal table includes at least one data field for storing medical data; the step of determining the second metadata of the first metadata relative to the second database according to a preset metadata mapping rule includes: selecting a data field that has not yet established a one-to-one association with a medical attribute belonging to the medical form as a target data field; and constructing the second metadata according to the position of the target data field in the first database.

[0054] In some cases, the second database may be a columnar storage database. Correspondingly, the second database may include at least one data field. The metadata mapping rules may specify a one-to-one association between medical attributes and data fields. Accordingly, if the medical attribute of the received medical data does not have an associated data field, a target data field can be selected from the unassociated data fields to be associated with the medical attribute. Further, the medical data can be stored in the data field in the second database associated with the medical attribute. Of course, the first metadata may also include the medical form to which the medical data belongs; correspondingly, a data field that has not yet established a one-to-one association with a medical attribute belonging to the medical form can be selected as the target data field.

[0055] In some implementations, the horizontal table of the second database may include, in addition to data fields, an identifier field for storing logical table identifiers. The logical identifier can be determined based on the medical form identifier to which the medical data in the first metadata belongs. Accordingly, during the process of storing medical data in the second database, the medical form identifier can be stored in the identifier field as a logical table identifier.

[0056] A method for constructing the second metadata based on the location of the target data field in the first database can be to determine the data field where the medical data is located after it is stored in the second database, based on the data fields associated with the medical attributes of the medical data. Therefore, the second metadata can be determined based on the location of the target data field in the first database. For example, please refer to... Figure 4 Blood glucose is associated with column 3. Therefore, based on column 3 in the horizontal table of the second database, the second metadata of the medical data can be determined. Of course, in some embodiments, the second metadata may also include the record where the medical data is located. Correspondingly, the second metadata can also be used to determine the record of the medical data to be stored based on the records already occupied by the medical data in the horizontal table of the second database, thereby determining the second metadata of the medical data.

[0057] Example devices, electronic devices, storage media, and software

[0058] Please see Figure 5 One embodiment of this specification also provides a metadata processing apparatus. The metadata processing apparatus may include a receiving module, a determining module, and a storage module.

[0059] A receiving module is used to receive medical data provided by a first database; wherein the medical data is accompanied by first metadata; the first metadata is used to describe the data attributes of the medical data.

[0060] The determining module is used to determine the second metadata of the first metadata relative to the second database according to a preset metadata mapping rule; wherein the second metadata is used to indicate the storage location of the medical data in the second database; the first database and the second database have different storage methods.

[0061] A storage module is configured to store the first metadata and the second metadata in a first storage medium, and to extract the second metadata from the first storage medium in response to a query request for medical data accompanied by the first metadata, so as to obtain the medical data in the second database; wherein the read performance of the first storage medium is better than that of the second database.

[0062] The specific functions and effects of the metadata processing device can be explained by referring to other embodiments in this specification, and will not be repeated here. Each module in the metadata processing device can be implemented entirely or partially through software, hardware, or a combination thereof. Each module can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0063] Please see Figure 6 This specification also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the metadata processing method in any of the above embodiments.

[0064] This specification also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer, causes the computer to perform the metadata processing method in any of the above embodiments.

[0065] This specification also provides a computer program product containing instructions that, when executed by a computer, cause the computer to perform the metadata processing method in any of the above embodiments.

[0066] It is understood that the specific examples in this document are only intended to help those skilled in the art better understand the embodiments described herein, and are not intended to limit the scope of the invention.

[0067] It is understood that in the various embodiments described in this specification, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments described in this specification.

[0068] It is understood that the various implementation methods described in this specification can be implemented individually or in combination, and the implementation methods in this specification are not limited in this respect.

[0069] Unless otherwise stated, all technical and scientific terms used in the embodiments of this specification have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of this specification. The term "and / or" as used in this specification includes any and all combinations of one or more of the associated listed items. The singular forms "a," "the," and "the" as used in the embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0070] It is understood that the processor in the embodiments of this specification can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this specification. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this specification can be directly implemented by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above methods.

[0071] It is understood that the memory in the embodiments of this specification may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM). It should be noted that the memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0072] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this specification.

[0073] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the aforementioned method implementations, and will not be repeated here.

[0074] In the several embodiments provided in this specification, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0075] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0076] In addition, the functional units in the various embodiments of this specification can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0077] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of this specification, in essence, or the parts that contribute to the prior art, or parts of the technical solutions, can be embodied in the form of software products. These computer software products are stored in a storage medium and include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this specification. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0078] The above description is merely a specific embodiment of this specification, but the scope of protection of this invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this specification should be included within the scope of protection of this specification. Therefore, the scope of protection of this invention should be determined by the scope of the claims.

Claims

1. A method for processing metadata, characterized in that, The method is applied to a server, and the method includes: The system receives medical data provided by a first database; wherein the medical data is accompanied by first metadata; the first metadata is used to describe the data attributes of the medical data; the first database stores the medical data using a vertical table. According to a preset metadata mapping rule, the second metadata of the first metadata relative to the second database is determined; wherein, the second metadata is used to indicate the storage location of the medical data in the second database; the first database and the second database have different storage methods; the second database includes at least one horizontal table; The first metadata and the second metadata are stored in a first storage medium for retrieving the second metadata from the first storage medium in response to a query request for the medical data accompanied by the first metadata, so as to obtain the medical data in the second database; wherein the read performance of the first storage medium is better than that of the second database.

2. The method according to claim 1, characterized in that, The method further includes: The medical data is sent to the second database so that the medical data is stored in the storage location indicated by the second metadata in the second database.

3. The method according to claim 1, characterized in that, The method further includes: The first metadata and the second metadata are persistently stored in the second storage medium.

4. The method according to claim 3, characterized in that, The method further includes: Receive a first query request for the medical data; wherein the first query request includes the first metadata; Query the second metadata corresponding to the first metadata in the first storage medium; If the second metadata is not present in the first storage medium, the second metadata is retrieved from the second storage medium. A second query request containing the second metadata is sent to the second database to return the medical data fed back by the second database to the sender of the first query request.

5. The method according to claim 3, characterized in that, The method further includes: If the second metadata corresponding to the first metadata does not exist in the first storage medium, the second metadata is read from the second storage medium and stored in the first storage medium.

6. The method according to claim 1, characterized in that, The first storage medium is server memory, and the method further includes: If the amount of metadata stored in the server memory exceeds a specified threshold, the metadata in the server memory will be cleared.

7. The method according to claim 1, characterized in that, The first metadata includes the medical attributes of the medical data and the medical form to which the medical data belongs; the horizontal table includes at least one data field for storing the medical data; The step of determining the second metadata of the first metadata relative to the second database according to the preset metadata mapping rules includes: Select the data field that has not yet established a one-to-one association with the medical attributes belonging to the medical form as the target data field; The second metadata is constructed based on the location of the target data field in the first database.

8. A metadata processing apparatus, characterized in that, The device includes: A receiving module is configured to receive medical data provided by a first database; wherein the medical data includes first metadata; the first metadata is used to describe the data attributes of the medical data; The determining module is used to determine the second metadata of the first metadata relative to the second database according to a preset metadata mapping rule; wherein the second metadata is used to indicate the storage location of the medical data in the second database; the first database and the second database have different storage methods; A storage module is configured to store the first metadata and the second metadata in a first storage medium, and to extract the second metadata from the first storage medium in response to a query request for medical data accompanied by the first metadata, so as to obtain the medical data in the second database; wherein the read performance of the first storage medium is better than that of the second database.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the method according to any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 6.

Images