CN112951437A - Medical data management method and device, storage medium and electronic equipment - Google Patents
Medical data management method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN112951437A CN112951437A CN201911264795.6A CN201911264795A CN112951437A CN 112951437 A CN112951437 A CN 112951437A CN 201911264795 A CN201911264795 A CN 201911264795A CN 112951437 A CN112951437 A CN 112951437A
- Authority
- CN
- China
- Prior art keywords
- data
- read
- database
- modified
- write
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/70—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for mining of medical data, e.g. analysing previous cases of other patients
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Public Health (AREA)
- Biomedical Technology (AREA)
- Databases & Information Systems (AREA)
- Pathology (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The disclosure provides a medical data management method, a medical data management device, a storage medium and electronic equipment, and relates to the technical field of data processing. The method comprises the following steps: receiving a data modification request, wherein the data modification request is used for indicating modification of data to be modified; searching the data to be modified in a preset read-write database and a read-only database; and when the data to be modified is only stored in the read-only database, copying the data to be modified to the read-write database, and modifying the data to be modified in the read-write database. The data management system and the data management method have the advantages that based on the arrangement of the two databases, data requests in reading and writing are processed in a targeted mode, and the flexibility and the efficiency of medical data management are improved.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a medical data management method, a medical data management apparatus, a computer-readable storage medium, and an electronic device.
Background
With the application of technologies such as big data and artificial intelligence in the medical field, people improve the degree of gravity of medical data, so that the amount of the medical data is increased explosively, and the medical data of a medium-scale hospital can often reach the magnitude of TB and even PB.
In the related art, when medical data needs to be modified, the whole data needs to be copied for unloading and then modified at a new storage address. However, the cost of the full-scale data replication is high, and more computing resources and storage resources are consumed.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
The present disclosure provides a medical data management method, a medical data management apparatus, a computer-readable storage medium, and an electronic device, thereby at least to some extent improving the problem that more resources are required to be consumed when medical data is modified in the related art.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.
According to a first aspect of the present disclosure, there is provided a medical data management method comprising: receiving a data modification request, wherein the data modification request is used for indicating modification of data to be modified; searching the data to be modified in a preset read-write database and a read-only database; and when the data to be modified is only stored in the read-only database, copying the data to be modified to the read-write database, and modifying the data to be modified in the read-write database.
Optionally, the method further includes: and when the data to be modified is determined to be stored in the read-write database, modifying the data to be modified in the read-write database.
Optionally, the method further includes: receiving a data searching request, wherein the data searching request is used for indicating to search data to be searched; searching the data to be searched in the read-only database and the read-write database; and when the value of the data to be searched in the read-only database is determined to be inconsistent with the value of the data to be searched in the read-write database, taking the value of the data to be searched in the read-write database as the data to be searched corresponding to the data searching request.
Optionally, when it is determined that the value of the data to be searched in the read-only database is inconsistent with the value of the data to be searched in the read-write database, the method further includes: and deleting the data to be searched in the read-only database.
Optionally, the method further includes: when the read-only database meets a preset condition, reading data in the read-only database one by one, and searching data with the same index as the data in the read-write database, wherein the index and the data have a one-to-one corresponding relation; if the read-write database has data with the same index as the data, copying the data with the same index in the read-write database to a preset updating read-only database; if the read-write database does not have data with the same index as the data, copying the data in the read-only database to the update read-only database; and deleting the read-only database after the data in the read-only database is read.
Optionally, after the reading of the data in the read-only database is finished, the method further includes: and clearing the data in the read-write database.
Optionally, the preset condition includes any one or more of the following: the data volume of the read-only database reaches a first threshold value; the data volume written into the read-only database in the preset time reaches a second threshold value; the difference between the current time and the time at which the read-only database was established reaches a third threshold.
According to a second aspect of the present disclosure, there is provided a medical data management apparatus comprising: the device comprises a request receiving module, a data modification module and a data modification module, wherein the request receiving module is used for receiving a data modification request which is used for indicating to modify data to be modified; the data searching module is used for searching the data to be modified in a preset read-write database and a preset read-only database; and the data modification module is used for copying the data to be modified to the read-write database and modifying the data to be modified in the read-write database when the data to be modified is only stored in the read-only database.
Optionally, the data modification module is further configured to modify the data to be modified in the read-write database when it is determined that the data to be modified is stored in the read-write database.
Optionally, the request receiving module is further configured to receive a data search request, where the data search request is used to instruct to search for data to be searched; the data searching module is further configured to search the data to be searched in the read-only database and the read-write database, and when it is determined that the value of the data to be searched in the read-only database is inconsistent with the value of the data to be searched in the read-write database, the value of the data to be searched in the read-write database is used as the data to be searched corresponding to the data searching request.
Optionally, the data searching module is further configured to delete the data to be searched from the read-only database when it is determined that the value of the data to be searched in the read-only database is inconsistent with the value of the data to be searched in the read-write database.
Optionally, the apparatus further includes a database update module, configured to update the read-only database by performing the following method: when the read-only database meets a preset condition, reading data in the read-only database one by one, and searching data with the same index as the data in the read-write database, wherein the index and the data have a one-to-one corresponding relation; if the read-write database has data with the same index as the data, copying the data with the same index in the read-write database to a preset updating read-only database; if the read-write database does not have data with the same index as the data, copying the data in the read-only database to the update read-only database; and deleting the read-only database after the data in the read-only database is read.
Optionally, the database updating module is further configured to clear the data in the read-write database after the data in the read-only database is read.
Optionally, the preset condition includes any one or more of the following: the data volume of the read-only database reaches a first threshold value; the data volume written into the read-only database in the preset time reaches a second threshold value; the difference between the current time and the time at which the read-only database was established reaches a third threshold.
According to a third aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements any one of the above-described medical data management methods.
According to a fourth aspect of the present disclosure, there is provided an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform any of the above-described medical data management methods via execution of the executable instructions.
The technical scheme of the disclosure has the following beneficial effects:
according to the medical data management method, the medical data management device, the storage medium and the electronic equipment, a data modification request for indicating modification of data to be modified is received, the data to be modified is searched in a preset read-write database and a preset read-only database, if the data to be modified is only stored in the read-only database, the data is copied from the read-only database to the read-write database, and the data is modified in the read-write database. On one hand, a large amount of medical data generated in actual management is stored in the read-only database, due to the characteristic that the read-only database is easy to retrieve, the quick retrieval of a large amount of data can be realized, and a small amount of modified data is stored in the read-write database, so that the read-write database has the characteristic of light weight and can realize the quick modification of the data, thereby performing targeted processing on data requests in the read and write aspects and improving the flexibility and the efficiency of data management. On the other hand, the modification request of the medical data is usually concentrated on a small amount of data, and the probability of repeated modification is high, so that the read-write database can better respond to the data modification request, invalid data storage is reduced, and the efficiency is further improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is apparent that the drawings in the following description are only some embodiments of the present disclosure, and that other drawings can be obtained from those drawings without inventive effort for a person skilled in the art.
Fig. 1 shows a flowchart of a medical data management method in the present exemplary embodiment;
FIG. 2 illustrates a sub-flow diagram of a medical data management method in the present exemplary embodiment;
FIG. 3 illustrates a sub-flow diagram of another method of medical data management in the present exemplary embodiment;
fig. 4 is a block diagram showing the structure of a medical data management apparatus according to the present exemplary embodiment;
FIG. 5 illustrates a computer-readable storage medium for implementing the above-described method in the present exemplary embodiment;
fig. 6 shows an electronic device for implementing the above method in the present exemplary embodiment.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
Generally, medical data has the following characteristics that are different from general data: the data volume is large, the accumulation is fast, most data are diagnosis and treatment records of patients and the like, and the data need to be stored for a long time; the data search requests are more, rapid retrieval is needed, but the data modification requests are less (diagnosis and treatment records are generally not allowed to be tampered); data modification requests are relatively centralized, one piece of data may be modified many times in a short time, and data modification requests are mostly directed to comparing new data, such as mistakes during data entry. Therefore, the general data management method is not suitable for medical data.
In view of one or more of the problems described above, an exemplary embodiment of the present disclosure first provides a medical data management method. The method can be applied to a computer or a server which is in charge of data management in a hospital or a medical institution, and can also be applied to a cluster formed by a plurality of devices.
In the present exemplary embodiment, a read-only database and a read-write database for medical data may be set in advance. The medical data in the read-only database only supports reading and is mainly responsible for the read-only service of the medical data, the medical data in the read-write database simultaneously supports reading and writing, and the read-write service of the medical data is responsible (mainly modified by data). Two databases are established, and medical data are stored in two ways, so that requirements in different aspects can be met. The exemplary embodiment may use various database systems to build the read-only database and the read-write database, for example, may use Hive (data warehouse tool based on Hadoop) to build the read-only database, MySQL (relational database system) to build the read-write database, and the like.
When a data write request (or data storage request) is received, the new data requested to be written may be stored to the read-only database. In consideration of the fact that medical data of each period usually needs to be searched in practical application, each piece of medical data can be read, and the read-only database is used as a main database for storing the medical data, so that the medical data in the read-only database is complete as much as possible to meet the data searching requirement. In addition, in order to save system resources, the read-write database does not need to store all medical data, in the exemplary embodiment, the initial read-write database may be an empty database, or may pre-store partial hot data or recent data, and then mainly store the modified data in the read-write database, so as to implement division of labor of the two databases.
Based on the read-only database and the read-write database, referring to fig. 1, the present exemplary embodiment provides a flow of a medical data management method, which may include the following steps S110 to S130:
step S110, a data modification request is received, where the data modification request is used to instruct to modify data to be modified.
The data modification request may specify the data to be modified or an index of the data to be modified, such as a data ID (Identity, index data identifier), etc., so as to determine which data or data to modify.
And step S120, searching the data to be modified corresponding to the data modification request in a preset read-write database and a preset read-only database.
The system can retrieve the data to be modified or the index thereof in the read-write database and the read-only database respectively to find out whether the data to be modified exists.
Step S130, when the data to be modified is only stored in the read-only database, the data to be modified is copied to the read-write database, and the data to be modified is modified in the read-write database.
Typically, the read-write database stores a portion of the medical data, the read-only database stores all or the main medical data, and the medical data in the read-write database can be regarded as a subset of the read-only database. But read-only databases do not support direct modification operations on data. In the exemplary embodiment, when the data to be modified is found in the read-only database and the data to be modified is not found in the read-write database, the data to be modified may be copied to the read-write database (the data to be modified may be copied from the read-only database or the data to be modified in the data modification request may be copied), and then the data may be modified in the read-write database.
In an alternative embodiment, when it is determined that the data to be modified is stored in the read-write database, the data to be modified may be directly modified in the read-write database.
Therefore, in step S130, the data to be modified is copied from the read-only database to the read-write database, which is a main source of the data in the read-write database. In other words, in the actual management process of the medical data, the medical data written into the read-write database is mainly modified data, the probability that the part of the data is modified again is high, and the part of the data is stored in the read-write database, so that the efficiency of data searching is improved.
Based on the above, in the present exemplary embodiment, a data modification request for instructing to modify data to be modified is received, the data to be modified is searched in the preset read-write database and the read-only database, and if the data to be modified is only stored in the read-only database, the data is copied from the read-only database to the read-write database, and the data is modified in the read-write database. On one hand, a large amount of medical data generated in actual management is stored in the read-only database, due to the characteristic that the read-only database is easy to retrieve, the quick retrieval of a large amount of data can be realized, and a small amount of modified data is stored in the read-write database, so that the read-write database has the characteristic of light weight and can realize the quick modification of the data, thereby performing targeted processing on data requests in the read and write aspects and improving the flexibility and the efficiency of data management. On the other hand, the modification request of the medical data is usually concentrated on a small amount of data, and the probability of repeated modification is high, so that the read-write database can better respond to the data modification request, invalid data storage is reduced, and the efficiency is further improved.
In an alternative embodiment, as shown in fig. 2, the medical data management method may further include the following steps S210 to S230:
step S210, receiving a data searching request, wherein the data searching request is used for indicating to search data to be searched;
step S220, searching data to be searched in a read-only database and a read-write database;
in step S230, when it is determined that the value of the data to be searched in the read-only database is inconsistent with the value of the data to be searched in the read-write database, the value of the data to be searched in the read-write database is used as the data to be searched corresponding to the data search request.
The data search request is usually to search for corresponding data to be searched according to an index of the medical data (such as a data ID or other query conditions). Because the data modification request is implemented in the read-write database, the medical data stored in the read-only database is the version before modification, and different versions are stored in the read-only database and the read-write database for the modified data, the version in the read-write database should be used as the standard at this time. For example, the value of the data found in the read-only database is a according to the index in the data search request, the value of the data found in the read-write database is B, and if a and B are not consistent, B is used as the search result. When the value of the data to be searched in the read-only database is consistent with the value of the data to be searched in the read-write database, the value of any data can be used as a data searching result.
Through the processing mode shown in fig. 2, since the read-only database supports fast retrieval, the amount of data in the read-write database is small, the speed of searching data in the two databases is high, and the response time can be obviously reduced compared with the case of searching data in a large-scale read-write database.
Furthermore, when the value of the data to be searched in the read-only database is determined to be inconsistent with the value of the data to be searched in the read-write database, the data to be searched in the read-only database is indicated to be old version data, and in order to prevent interference on subsequent data processing, the data to be searched can be deleted in the read-only database, so that subsequent operations on the data to be searched are subject to reading and writing of the data to be searched in the database, and the consistency of data processing is ensured.
In another embodiment, when a data search request is received, the data to be searched can be searched in the read-write database, and when the data to be searched is searched in the read-write database, the data is directly output as a processing result of the data search request; and when the data to be searched is not searched in the read-write database, continuously searching in the read-only database, and taking the searched data as a processing result of the data searching request.
Since read-only databases do not allow direct modification of data, read-only databases may accumulate more and more old versions of data as more and more data modification requests are processed. In order to reduce the influence of the old version data and further improve the management efficiency, in an alternative embodiment, as shown in fig. 3, the read-only database may be updated through the following steps S310 to S340:
step S310, when the read-only database meets the preset conditions, the data in the read-only database is read one by one, and the data with the same index as the data is searched in the read-write database. The index and the data have a one-to-one correspondence relationship, and the index plays a role in uniquely identifying the data, for example, each piece of data may be a key value pair or a tuple in the database, and the index may be a key or a primary key or an identification field in the tuple, and the like. For example, if there is a piece of medical data a in the read-only database with an index a1, it can be found whether there is an index a1 in the read-write database, and read the data corresponding to the index a 1.
Step S320, if there is data with the same index as the above data in the read-write database, copying the data with the same index in the read-write database to a preset update read-only database. Wherein, the update read-only database is a new read-only database which is initially empty. For example, for medical data a with an index of a1 in the read-only database, if the read-write database has an index a1 and the corresponding data is B, the data B in the read-write database is copied to the update read-only database. And finishing reading the piece of data and continuously processing the next piece of data.
Step S330, if the read-write database does not have the data with the same index as the data, copying the data in the read-only database to the update read-only database. For example, if the index a1 does not exist in the read-write database, the data a in the read-only database is copied to the update read-only database, the reading of the piece of data is completed, and the next piece of data is processed continuously.
Step S340, deleting the read-only database after the data in the read-only database is read.
In short, the above process is to copy the medical data in the read-only database to the update read-only database one by one, before copying, check whether the read-write database has corresponding medical data (i.e. new version data), if so, copy the new version data, thereby ensuring that the data version copied to the new read-only database is up-to-date. Because the read-only database does not allow direct modification of the data, the medical data in the read-only database is completely updated in the update read-only database in a read-only database replacement mode.
Further, when the reading of the data in the read-only database is finished, that is, the update of the read-only database is completed, step S350 may be further executed: and emptying the data in the read-write database. Because the latest version of medical data is stored in the updated read-only database, accurate data can be read from the read-only database subsequently, and the data in the read-write database does not need to be reserved. The method comprises the steps of establishing an update read-only database every time, namely merging an old read-only database and a read-write database, emptying data in the read-write database, and continuously copying data in the update read-only database into the read-write database when a data modification request is processed subsequently, so that the periodic management of the read-write database is realized, the small data amount stored in the read-write database is further ensured, and the service response speed is improved.
In the foregoing process, the preset condition is used to determine whether to start a process of updating the read-only database, and may include:
(1) the amount of data in the read-only database reaches a first threshold. The data volume increase of the read-only database and the generation of new medical data are synchronous, when the data volume is large and reaches a first threshold value, the fact that more new medical data are stored is indicated, and at the moment, the update of the read-only database can be executed once.
(2) The data amount written into the read-only database in the preset time reaches a second threshold value. Wherein, the preset time can be the last week, the last month and the like, as the case may be. The data volume written into the read-only database in the preset time represents the recent data read-write frequency, and if the recent data read-write frequency reaches the second threshold value, the data read-write frequency is more frequent, so that the requirement for updating the read-only database is higher, and an updating process can be executed once.
(3) The difference between the current time and the time for establishing the read-only database reaches a third threshold, which may be a preset time period, such as 24 hours, a week, etc., and is equivalent to performing the update of the read-only database once every certain time.
(4) The amount of data in the read-write database reaches a fourth threshold. Typically, the amount of data read from and written to the database indicates how much data has been modified and also indicates how much old version data is in the read-only database. Therefore, the amount of data read from and written to the read-only database is large, and when the fourth threshold is reached, the amount of data read from and written to the read-only database means that the amount of data of the old version in the read-only database is large, and at this time, the update of the read-only database can be performed once.
The first, second, third and fourth thresholds are parameters set according to experience or actual requirements, and the numerical values thereof are not limited in the present disclosure. In practical application, any one of the above conditions may be selected or any multiple of the above conditions may be selected and combined according to the scene requirements to determine whether to start updating the read-only database. The present disclosure is not limited thereto.
In an alternative embodiment, before step S310, the following steps may also be performed: and moving the medical data which is not searched in the read-only database to the historical database. The read-only database may record the history of being searched for each piece of medical data, for example, a count index may be set to cumulatively record the number of queries for each piece of medical data, two time indexes may be set, one records the time of initial storage of data, and the other records the time of the last query, and the comparison between the two times determines whether the query has been made. The medical data which are not searched are usually long-term data or data with low heat degree, and the like, the data are stored in a historical database, deleted from the read-only database, and then the data are not processed when being copied into the updated read-only database, so that the data in the read-only database are substantially simplified. In the exemplary embodiment, three databases, namely a read-only database and a read-write database, are established for processing daily data services, and when data related to the services is not in the read-only database or the read-write database, corresponding data is searched from a historical database for processing, so that data retrieval required by the daily services is limited within a smaller range, and the efficiency is further improved.
Exemplary embodiments of the present disclosure also provide a medical data management apparatus. As shown in fig. 4, the medical data management apparatus 400 may include:
a request receiving module 410, configured to receive a data modification request, where the data modification request is used to indicate that data to be modified is modified;
the data searching module 420 is configured to search for data to be modified in a preset read-write database and a preset read-only database;
and the data modification module 430 is configured to copy the data to be modified to the read-write database and modify the data to be modified in the read-write database when it is determined that the data to be modified is only stored in the read-only database.
In an optional implementation, the data modification module 430 is further configured to modify the data to be modified in the read-write database when it is determined that the data to be modified is stored in the read-write database.
In an optional implementation manner, the request receiving module 410 is further configured to receive a data search request, where the data search request is used to instruct to search for data to be searched; the data searching module 420 is further configured to search the read-only database and the read-write database for the data to be searched, and when it is determined that the value of the data to be searched in the read-only database is inconsistent with the value of the data to be searched in the read-write database, take the value of the data to be searched in the read-write database as the data to be searched corresponding to the data searching request.
In an alternative embodiment, the data searching module 420 is further configured to delete the data to be searched in the read-only database when it is determined that the value of the data to be searched in the read-only database is inconsistent with the value of the data to be searched in the read-write database.
In an alternative embodiment, the medical data management apparatus 400 may further include a database update module for performing a read-only database update by performing the following method:
when the read-only database meets the preset condition, reading the data in the read-only database one by one, and searching the data with the same index as the data in the read-write database, wherein the index and the data have a one-to-one corresponding relation;
if the read-write database has data with the same index as the data, copying the data with the same index in the read-write database to a preset updating read-only database;
if the read-write database does not have data with the same index as the data, copying the data in the read-only database to an updated read-only database;
and deleting the read-only database after the data in the read-only database is read.
In an optional implementation manner, the database updating module is further configured to empty the data in the read-write database after the data in the read-only database is read.
In an alternative embodiment, the preset condition may include any one or more of the following:
the data volume of the read-only database reaches a first threshold value;
the data volume written into the read-only database in the preset time reaches a second threshold value;
the difference between the current time and the time at which the read-only database was built reaches a third threshold.
The specific details of each module in the above apparatus have been described in detail in the method section, and details that are not disclosed may refer to the method section, and thus are not described again.
As will be appreciated by one skilled in the art, aspects of the present disclosure may be embodied as a system, method or program product. Accordingly, various aspects of the present disclosure may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
Exemplary embodiments of the present disclosure also provide a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, various aspects of the disclosure may also be implemented in the form of a program product comprising program code for causing an electronic device to perform the steps according to various exemplary embodiments of the disclosure described in the above-mentioned "exemplary methods" section of this specification, when the program product is run on the electronic device.
Referring to fig. 5, a program product 500 for implementing the above method according to an exemplary embodiment of the present disclosure is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on an electronic device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a 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.
Program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The exemplary embodiment of the present disclosure also provides an electronic device capable of implementing the above method. An electronic device 600 according to this exemplary embodiment of the present disclosure is described below with reference to fig. 6. The electronic device 600 shown in fig. 6 is only an example and should not bring any limitations to the function and scope of use of the embodiments of the present disclosure.
As shown in fig. 6, electronic device 600 may take the form of a general purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one memory unit 620, a bus 630 that couples various system components including the memory unit 620 and the processing unit 610, and a display unit 640.
The storage unit 620 stores program code that may be executed by the processing unit 610, such that the processing unit 610 performs the steps according to various exemplary embodiments of the present disclosure described in the above-mentioned "exemplary methods" section of this specification. For example, processing unit 610 may perform the method steps shown in fig. 1, fig. 2, or fig. 3.
The storage unit 620 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)621 and/or a cache memory unit 622, and may further include a read only memory unit (ROM) 623.
The storage unit 620 may also include a program/utility 624 having a set (at least one) of program modules 625, such program modules 625 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 600, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 600 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 650. Also, the electronic device 600 may 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) via the network adapter 660. As shown, the network adapter 660 communicates with the other modules of the electronic device 600 over the bus 630. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the exemplary embodiments of the present disclosure.
Furthermore, the above-described figures are merely schematic illustrations of processes included in methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit, according to exemplary embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is to be limited only by the terms of the appended claims.
Claims (10)
1. A medical data management method, comprising:
receiving a data modification request, wherein the data modification request is used for indicating modification of data to be modified;
searching the data to be modified in a preset read-write database and a read-only database;
and when the data to be modified is only stored in the read-only database, copying the data to be modified to the read-write database, and modifying the data to be modified in the read-write database.
2. The method of claim 1, further comprising:
and when the data to be modified is determined to be stored in the read-write database, modifying the data to be modified in the read-write database.
3. The method of claim 1, further comprising:
receiving a data searching request, wherein the data searching request is used for indicating to search data to be searched;
searching the data to be searched in the read-only database and the read-write database;
and when the value of the data to be searched in the read-only database is determined to be inconsistent with the value of the data to be searched in the read-write database, taking the value of the data to be searched in the read-write database as the data to be searched corresponding to the data searching request.
4. The method of claim 3, wherein when it is determined that the value of the data to be searched in the read-only database is not consistent with the value in the read-write database, the method further comprises:
and deleting the data to be searched in the read-only database.
5. The method of claim 1, further comprising:
when the read-only database meets a preset condition, reading data in the read-only database one by one, and searching data with the same index as the data in the read-write database, wherein the index and the data have a one-to-one corresponding relation;
if the read-write database has data with the same index as the data, copying the data with the same index in the read-write database to a preset updating read-only database;
if the read-write database does not have data with the same index as the data, copying the data in the read-only database to the update read-only database;
and deleting the read-only database after the data in the read-only database is read.
6. The method of claim 5, wherein when the reading of the data in the read-only database is finished, the method further comprises:
and clearing the data in the read-write database.
7. The method according to claim 5 or 6, wherein the preset conditions comprise any one or more of:
the data volume of the read-only database reaches a first threshold value;
the data volume written into the read-only database in the preset time reaches a second threshold value;
the difference between the current time and the time at which the read-only database was established reaches a third threshold.
8. A medical data management apparatus, comprising:
the device comprises a request receiving module, a data modification module and a data modification module, wherein the request receiving module is used for receiving a data modification request which is used for indicating to modify data to be modified;
the data searching module is used for searching the data to be modified in a preset read-write database and a preset read-only database;
and the data modification module is used for copying the data to be modified to the read-write database and modifying the data to be modified in the read-write database when the data to be modified is only stored in the read-only database.
9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method of any one of claims 1 to 7.
10. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the method of any of claims 1 to 7 via execution of the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911264795.6A CN112951437B (en) | 2019-12-11 | 2019-12-11 | Medical data management method, medical data management device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911264795.6A CN112951437B (en) | 2019-12-11 | 2019-12-11 | Medical data management method, medical data management device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112951437A true CN112951437A (en) | 2021-06-11 |
| CN112951437B CN112951437B (en) | 2023-08-08 |
Family
ID=76226282
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911264795.6A Active CN112951437B (en) | 2019-12-11 | 2019-12-11 | Medical data management method, medical data management device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112951437B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102402596A (en) * | 2011-11-07 | 2012-04-04 | 北京搜狗科技发展有限公司 | Reading and writing method and system of master slave separation database |
| CN103793432A (en) * | 2012-11-01 | 2014-05-14 | 深圳中兴网信科技有限公司 | Method and device for splitting database reading and writing |
| US9613120B1 (en) * | 2014-11-11 | 2017-04-04 | Amazon Technologies, Inc. | Replicated database startup for common database storage |
| CN106649412A (en) * | 2015-11-04 | 2017-05-10 | 阿里巴巴集团控股有限公司 | Data processing method and device |
| CN106815218A (en) * | 2015-11-27 | 2017-06-09 | 华为技术有限公司 | Data bank access method, device and Database Systems |
| CN108959548A (en) * | 2018-07-02 | 2018-12-07 | 阿里巴巴集团控股有限公司 | The processing method and processing device of service request |
| CN109344142A (en) * | 2018-08-22 | 2019-02-15 | 中国平安人寿保险股份有限公司 | Data processing method, device, electronic equipment and storage medium |
| CN110019496A (en) * | 2017-07-27 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Data read-write method and system |
| CN110019213A (en) * | 2017-12-04 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Data managing method, device, electronic equipment and storage medium |
| US10417212B1 (en) * | 2015-01-15 | 2019-09-17 | Qad, Inc. | Database modification replay |
-
2019
- 2019-12-11 CN CN201911264795.6A patent/CN112951437B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102402596A (en) * | 2011-11-07 | 2012-04-04 | 北京搜狗科技发展有限公司 | Reading and writing method and system of master slave separation database |
| CN103793432A (en) * | 2012-11-01 | 2014-05-14 | 深圳中兴网信科技有限公司 | Method and device for splitting database reading and writing |
| US9613120B1 (en) * | 2014-11-11 | 2017-04-04 | Amazon Technologies, Inc. | Replicated database startup for common database storage |
| US10417212B1 (en) * | 2015-01-15 | 2019-09-17 | Qad, Inc. | Database modification replay |
| CN106649412A (en) * | 2015-11-04 | 2017-05-10 | 阿里巴巴集团控股有限公司 | Data processing method and device |
| CN106815218A (en) * | 2015-11-27 | 2017-06-09 | 华为技术有限公司 | Data bank access method, device and Database Systems |
| CN110019496A (en) * | 2017-07-27 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Data read-write method and system |
| CN110019213A (en) * | 2017-12-04 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Data managing method, device, electronic equipment and storage medium |
| CN108959548A (en) * | 2018-07-02 | 2018-12-07 | 阿里巴巴集团控股有限公司 | The processing method and processing device of service request |
| CN109344142A (en) * | 2018-08-22 | 2019-02-15 | 中国平安人寿保险股份有限公司 | Data processing method, device, electronic equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| MANISH KUMAR PANDEY，等: "A Novel Storage Architecture for Facilitating Efficient Analytics of Health Informatics Big Data in Cloud", 2016 IEEE INTERNATIONAL CONFERENCE ON COMPUTER AND INFORMATION TECHNOLOGY, pages 578 - 585 * |
| 蔡全福: "基于Hadoop的医疗健康数据管理系统研究与设计", 中国优秀硕士学位论文全文数据库 信息科技辑, no. 01, pages 138 - 428 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112951437B (en) | 2023-08-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20160078079A1 (en) | Statement based migration for adaptively building and updating a column store database from a row store database based on query demands using disparate database systems | |
| CN109657174B (en) | Method and device for updating data | |
| US20170293649A1 (en) | Automatically revising synopsis table structure | |
| US20160196295A1 (en) | Rendezvous-based optimistic concurrency control | |
| WO2016079629A1 (en) | Optimizing database deduplication | |
| CN111190882B (en) | Target template creation method and device, electronic equipment and storage medium | |
| CN109684270B (en) | Database archiving method, device, system, equipment and readable storage medium | |
| US11687525B2 (en) | Targeted sweep method for key-value data storage | |
| CN118113663A (en) | Method, apparatus and computer program product for managing a storage system | |
| JP2022137281A (en) | Data query method, device, electronic device, storage medium, and program | |
| CN114741335A (en) | Cache management method, device, medium and equipment | |
| JP2017027326A (en) | Storage system and program for the same | |
| EP3552122B1 (en) | Distributed index searching in computing systems | |
| CN114330272A (en) | Medical record template generation method and device, electronic equipment and storage medium | |
| US20190114082A1 (en) | Coordination Of Compaction In A Distributed Storage System | |
| CN103793401A (en) | Method and device for creating sharing indexes of a plurality of database tables | |
| CN112764662B (en) | Method, apparatus and computer program product for storage management | |
| CN112951437B (en) | Medical data management method, medical data management device, storage medium and electronic equipment | |
| CN110597830B (en) | Real-time index generation method and system, electronic equipment and storage medium | |
| US20230043307A1 (en) | Replicating Changes Written by a Transactional Virtual Storage Access Method | |
| CN110750268B (en) | File cleaning method and device, computer readable storage medium and electronic equipment | |
| CN113760600B (en) | Database backup method, database restoration method and related devices | |
| CN113127238B (en) | Method and device for exporting data in database, medium and equipment | |
| CN114116613B (en) | Metadata query method, device and storage medium based on distributed file system | |
| CN117009439B (en) | Data processing method, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |