CN112951437B - Medical data management method, medical data management device, storage medium and electronic equipment - Google Patents
Medical data management method, medical data management device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN112951437B CN112951437B CN201911264795.6A CN201911264795A CN112951437B CN 112951437 B CN112951437 B CN 112951437B CN 201911264795 A CN201911264795 A CN 201911264795A CN 112951437 B CN112951437 B CN 112951437B
- Authority
- CN
- China
- Prior art keywords
- data
- read
- database
- write
- modified
- 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.)
- Active
Links
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; when the data to be modified is determined to be 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 method and the device are based on the setting of the two databases, and the data requests in the aspects of reading and writing are processed in a targeted manner, so that 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 visibility of medical data, so that the amount of the medical data is explosive, and for example, a medium-scale hospital, the medical data can reach the magnitude of TB and PB.
In the related art, when modification of medical data is required, the data is copied in full quantity to be transferred and then modified at a new storage address. However, the cost of full replication of data is high, and more computing and storage resources are required.
It should be noted that the information disclosed in the above background section is only for enhancing 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 improving the problem that more resources are required to be consumed when modifying medical data in the related art at least to some extent.
Other features and advantages of the present disclosure will be apparent from the following detailed description, or may be learned in part by the 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; when the data to be modified is determined to be 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 comprises: 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 comprises: 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 inconsistent with the value 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 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 comprises: 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 correspondence; if the data with the same index as the data exists in the read-write database, copying the data with the same index in the read-write database to a preset update read-only database; if the read-write database does not contain the data with the same index as the data, copying the data in the read-only database to the updated 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; writing the data volume of the read-only database in a preset time to reach a second threshold; the difference between the current time and the time of building the read-only database reaches a third threshold.
According to a second aspect of the present disclosure, there is provided a medical data management apparatus comprising: the request receiving module is used for receiving a data modification request, wherein the data modification request is used for indicating modification of 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 read-only database; and the data modification module is used for copying the data to be modified to the read-write database when the data to be modified is determined to be only stored in the read-only database, and modifying the data to be modified in the read-write 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 indicate searching 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 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 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 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 correspondence; if the data with the same index as the data exists in the read-write database, copying the data with the same index in the read-write database to a preset update read-only database; if the read-write database does not contain the data with the same index as the data, copying the data in the read-only database to the updated 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 empty 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; writing the data volume of the read-only database in a preset time to reach a second threshold; the difference between the current time and the time of building the read-only database 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 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 medical data management methods described above via execution of the executable instructions.
The technical scheme of the present 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 read-write database and a read-only database which are preset, 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 a read-only database, and due to the characteristic that the read-only database is easy to search, the rapid search of a large amount of data can be realized, and a small amount of modified data is stored in a read-write database, so that the read-write database has the characteristic of light weight, the rapid modification of the data can be realized, and therefore data requests in the two aspects of reading and writing are processed in a targeted manner, and the flexibility and the efficiency of data management are improved. On the other hand, since the modification request of the medical data is usually concentrated on a small amount of data, the probability of repeated modification is higher, so that the read-write database can better respond to the data request and reduce invalid data storage, thereby further improving the efficiency.
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 disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely some embodiments of the present disclosure and that other drawings may be derived from these drawings without undue effort.
Fig. 1 shows a flowchart of a medical data management method in the present exemplary embodiment;
fig. 2 shows a sub-flowchart of a medical data management method in the present exemplary embodiment;
fig. 3 shows a sub-flowchart of another medical data management method in the present exemplary embodiment;
fig. 4 shows a block diagram of a medical data management apparatus in 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. However, the exemplary embodiments may be embodied in many 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 the 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 present disclosure. One skilled in the relevant art will recognize, however, that the aspects of the disclosure may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. 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 a repetitive description thereof 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 software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
In general, medical data has the following characteristics different from general data: the data volume is large, the accumulation is quick, and the data is mostly diagnosis and treatment records of patients and the like, so that the data needs to be stored for a long time; the data search requests are more, quick search is needed, but the data modification requests are less (diagnosis records generally do not allow tampering); the data modification request is relatively concentrated, a piece of data may be modified multiple times in a short time, and the data modification request is mostly aimed at comparing new data, such as a candid error in the data entry process. Therefore, the general data management method is often not applicable to medical data.
In view of one or more of the problems set forth above, exemplary embodiments of the present disclosure first provide a medical data management method. The method can be applied to a computer or a server which is responsible for 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 read-only business of the medical data, and the medical data in the read-write database simultaneously supports reading and writing and is responsible for read-write business (mainly data modification) of the medical data. Two databases are established, medical data is stored in two ways, and the requirements of different aspects can be met. The present exemplary embodiment may use various database systems to build a read-only database and a read-write database, for example, hive (Hadoop-based data warehouse tool) may be used to build a read-only database, mySQL (relational database system) may be used to build a read-write database, and so on.
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. The method considers that medical data in each period is usually required 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 as complete as possible, and the data searching requirement is met. In addition, in order to save system resources, the read-write database does not need to store all medical data, in this exemplary embodiment, the initial read-write database may be an empty database, or may pre-store part of hot data or recent data, and then mainly store modified data into the read-write database, so as to realize division of the two databases.
Based on the read-only database and the read-write database, referring to fig. 1, the present exemplary embodiment proposes a process of a medical data management method, which may include the following steps S110 to S130:
in step S110, a data modification request is received, where the data modification request is used to indicate modification of the data to be modified.
Wherein 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), etc., in order to determine which data or data to modify.
Step S120, searching the data to be modified corresponding to the data modification request in a preset read-write database and a read-only database.
The system may retrieve the data to be modified or its index in the read-write database and the read-only database, respectively, to find out whether there is data to be modified.
In step S130, when it is determined that the data to be modified is stored only 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, and the read-write database stores all or a substantial portion of the medical data, which may be considered a subset of the read-only database. Read-only databases do not support direct modification operations on data. In this 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 modified directly in the read-write database.
Thus, in step S130, the data to be modified is copied from the read-only database to the read-write database, which is the 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 of the data being modified again is high, and 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 modification of data to be modified is received, the data to be modified is searched in a read-write database and a read-only database that are set in advance, if the data to be modified is stored only 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 a read-only database, and due to the characteristic that the read-only database is easy to search, the rapid search of a large amount of data can be realized, and a small amount of modified data is stored in a read-write database, so that the read-write database has the characteristic of light weight, the rapid modification of the data can be realized, and therefore data requests in the two aspects of reading and writing are processed in a targeted manner, and the flexibility and the efficiency of data management are improved. On the other hand, since the modification request of the medical data is usually concentrated on a small amount of data, the probability of repeated modification is higher, so that the read-write database can better respond to the data request and reduce invalid data storage, thereby further improving the efficiency.
In an alternative embodiment, referring to 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;
step S230, when 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 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.
Wherein, the data searching request is generally used for searching the corresponding data to be searched according to the index (such as data ID or other query conditions) of the medical data. Since the data modification request is implemented in the read-write database, the medical data stored in the read-only database is a version before modification, and for the modified data, different versions are stored in the read-only database and the read-write database, and the versions in the read-write database should be used for the sake of convenience. For example, according to the index in the data search request, the value of the data found in the read-only database is a, the value of the data found in the read-write database is B, and if a and B are inconsistent, 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.
By the processing mode shown in fig. 2, the read-only database supports quick search, so that the data volume in the read-write database is small, the speed of searching data in the two databases is high, and compared with searching data in a large read-write database, the response time can be obviously reduced.
Further, when 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 data to be searched in the read-only database is stated to be old version data, and in order to prevent interference to subsequent data processing, the data to be searched can be deleted in the read-only database, so that the subsequent operation on the data to be searched is based on the data to be searched in the read-write database, and the consistency of data processing is ensured.
In another embodiment, when a data searching request is received, the data to be searched can be searched in the read-write database first, 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 searching request; when the data to be searched is not searched in the read-write database, the data to be searched is continuously searched in the read-only database, and the searched data is used as a processing result of the data searching request.
Since read-only databases do not allow direct modification of data, as more and more data modification requests are processed, more and more older versions of data may accumulate in the read-only database. To further improve management efficiency by reducing the impact of legacy data, in an alternative embodiment, referring to fig. 3, the read-only database may be updated by the following steps S310 to S340:
in step S310, when the read-only database meets the preset condition, 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, the index plays a role in uniquely identifying the data, for example, each piece of data can be a key value pair or a tuple in the database, and the index can be a main key or an identification field in the key or the tuple, and the like. For example, a piece of medical data a exists in the read-only database, the index is a1, whether the index a1 exists or not can be searched in the read-write database, and the data corresponding to the index a1 can be read.
In step S320, if there is data with the same index as the above data in the read-write database, the data with the same index in the read-write database is copied to the preset update read-only database. Wherein, the update read-only database is a new read-only database established, which is initially empty. For example, for the medical data a with index a1 in the read-only database, if the index a1 exists in the read-write database and the corresponding data is B, the data B in the read-write database is copied to the updated read-only database. And finishing the reading of the data and continuing to process the next data.
In step S330, if there is no data having the same index as the above data in the read-write database, the above data in the read-only database is copied to the updated 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 data is completed, and the next data is processed.
In step S340, when the reading of the data in the read-only database is completed, the read-only database is deleted.
In short, the above process is to copy the medical data in the read-only database one by one into the updated read-only database, and before copying, check whether the corresponding medical data (i.e. new version data) exists in the read-write database, and if so, copy the new version data, thereby ensuring that the version of the data copied into the new read-only database is up-to-date. Because the read-only database does not allow direct data modification, the method of replacing the read-only database is equivalent to that the medical data in the read-only database is completely updated in the read-only database.
Further, when the reading of the data in the read-only database is finished, that is, the updating of the read-only database is completed, step S350 may be further executed: and clearing the data in the read-write database. Since the latest version of medical data is stored in the updated read-only database, accurate data can be read from the read-only database later, and the data in the read-write database is not required to be reserved. Each time the update read-only database is established, which is equivalent to merging the old read-only database and the read-write database, clearing the data in the read-write database, and continuously copying the data in the update read-only database into the read-write database when the data modification request is processed subsequently, thereby realizing the periodic management of the read-write database, further ensuring that the read-write database stores less data, and improving the service response speed.
In the above process, the preset condition for determining whether to start the process of updating the read-only database may include:
(1) The data amount of the read-only database reaches a first threshold. The data volume of the read-only database is increased and new medical data is generated synchronously, and when the data volume is more, the first threshold value is reached, the data volume indicates that more new medical data is stored, and at the moment, the update of the read-only database can be executed once.
(2) And the data volume written into the read-only database reaches a second threshold value within a preset time. The preset time may be the last week, the last month, etc., as the case may be. The data quantity written into the read-only database in the preset time characterizes the recent data read-write frequency, and if the data quantity reaches the second threshold value, the data read-write is more frequent, so that the demand for updating the read-only database is higher, and the one-time updating process can be executed.
(3) The difference between the current time and the time of creating the read-only database reaches a third threshold, which may be a preset time period, for example 24 hours, one week, etc., corresponding to that the update of the read-only database is performed at regular intervals.
(4) The amount of data in the read-write database reaches a fourth threshold. Typically, the amount of data in the read-write database indicates how much data has been modified and also how much old version of data is in the read-only database. Therefore, the data amount of the read-write database is large, and when the fourth threshold is reached, the old version data 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 values thereof are not limited in this disclosure. In practical application, any one of the conditions can be selected or any plurality of the conditions can be selected to be combined according to scene requirements so as to judge whether to start updating the read-only database. The present disclosure is not limited in this regard.
In an alternative embodiment, the following steps may also be performed prior to step S310: medical data which is not searched in the read-only database is moved to the historical database. The read-only database may record the searched history of each piece of medical data, for example, a count index may be set to accumulate the number of times of searching for each piece of medical data, or two time indexes may be set, one records the time of initial storage of data, the other records the time of the last searching, and whether the medical data is searched or not is determined by comparing the two times. Medical data that is not searched for is typically more remote data or less hot data, and the like, which is stored in a history database, deleted from a read-only database, and subsequently, when the data is copied into an updated read-only database, the data is not processed, thereby substantially simplifying the data in the read-only database. The three databases are established in the exemplary embodiment, the read-only database and the read-write database are used for processing daily data service, and when data related to the service is not in the read-only database or the read-write database, corresponding data is searched from the history database for processing, so that the data search required by the daily service is limited to 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 modification of data to be modified;
the data searching module 420 is configured to search the data to be modified in a preset read-write database and a read-only database;
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 alternative embodiment, the data modification module 430 is further configured to, when it is determined that the data to be modified is stored in the read-write database, modify the data to be modified in the read-write database.
In an alternative embodiment, the request receiving module 410 is further configured to receive a data search request, where the data search request is used to indicate searching for data to be searched; the data searching module 420 is further configured to search for data to be searched in the read-only database and the read-write database, and when determining that the value of the data to be searched in the read-only database is inconsistent with the value 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.
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 in the read-write database.
In an alternative embodiment, the medical data management device 400 may further comprise 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 indexes and the data have a one-to-one correspondence;
if the data with the same index as the data exists in the read-write database, copying the data with the same index in the read-write database to a preset update read-only database;
if the data with the same index as the data does not exist in the read-write database, 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 alternative embodiment, 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 conditions may include any one or more of the following:
the data volume of the read-only database reaches a first threshold;
writing the data volume of the read-only database in a preset time to reach a second threshold;
the difference between the current time and the time of creating the read-only database reaches a third threshold.
The specific details of each module in the above apparatus are already described in the method section, and the details that are not disclosed can be referred to the embodiment of the method section, so that they will not be described in detail.
Those skilled in the art will appreciate that the various aspects of the present disclosure may be implemented as a system, method, or program product. Accordingly, various aspects of the disclosure may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may 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 method described above in the present specification. In some possible implementations, aspects of the present disclosure may also be implemented in the form of a program product comprising program code for causing an electronic device to carry out the steps according to the various exemplary embodiments of the disclosure as described in the "exemplary methods" section of this specification, when the program product is run on an electronic device.
Referring to fig. 5, a program product 500 for implementing the above-described 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. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. 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 of 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, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, 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., connected via the Internet using an Internet service provider).
The exemplary embodiment of the disclosure also provides an electronic device capable of implementing the method. An electronic device 600 according to such an exemplary embodiment of the present disclosure is described below with reference to fig. 6. The electronic device 600 shown in fig. 6 is merely an example and should not be construed to limit the functionality and scope of use of embodiments of the present disclosure in any way.
As shown in fig. 6, the electronic device 600 may be embodied in the form of a general purpose computing device. Components of 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 connecting the different system components (including the memory unit 620 and the processing unit 610), and a display unit 640.
The storage unit 620 stores program codes that can be executed by the processing unit 610, so that the processing unit 610 performs the steps according to various exemplary embodiments of the present disclosure described in the above "exemplary method" section of the present specification. For example, the processing unit 610 may perform the method steps shown in fig. 1, 2 or 3.
The storage unit 620 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 621 and/or cache memory 622, and may further include Read Only Memory (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 or some combination of which may include an implementation of a network environment.
Bus 630 may be a local bus representing one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or using any of a variety of bus architectures.
The electronic device 600 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 600, and/or any device (e.g., router, modem, etc.) that enables the electronic device 600 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 650. Also, electronic device 600 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 660. As shown, network adapter 660 communicates with other modules of electronic device 600 over bus 630. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 600, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, 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 (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the exemplary embodiments of the present disclosure.
Furthermore, the above-described figures are only schematic illustrations of processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with exemplary embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
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 adaptations, 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 is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (7)
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;
when the data to be modified is determined to be 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;
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.
2. The method according to claim 1, wherein the method further comprises:
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;
when the value of the data to be searched in the read-only database is inconsistent with the value 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, and deleting the data to be searched in the read-only database.
3. The method according to claim 1, wherein the method further comprises:
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-write database, and taking the data searched in the read-write database as a processing result of the data searching request when the data to be searched is searched in the read-write database;
when the data to be searched is not searched in the read-write database, searching in the read-only database, and taking the data searched in the read-only database as a processing result of the data searching request.
4. The method according to claim 1, wherein the method further comprises:
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 correspondence;
if the data with the same index as the data exists in the read-write database, copying the data with the same index in the read-write database to a preset update read-only database;
if the read-write database does not contain the data with the same index as the data, copying the data in the read-only database to the updated read-only database;
deleting the read-only database after the data in the read-only database is read, and clearing the data in the read-write database;
the preset condition is used for judging whether to start the process of updating the read-only database, and comprises any one or more of the following steps:
the data volume of the read-only database reaches a first threshold;
writing the data volume of the read-only database in a preset time to reach a second threshold;
the difference between the current time and the time of establishing the read-only database reaches a third threshold;
and the data volume of the read-write database reaches a fourth threshold value.
5. A medical data management apparatus, comprising:
the request receiving module is used for receiving a data modification request, wherein the data modification request is used for indicating modification of 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 read-only database;
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 determined to be stored in the read-only database only; 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.
6. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method of any of claims 1 to 4.
7. 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 one of claims 1 to 4 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 CN112951437A (en) | 2021-06-11 |
| CN112951437B true 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 |
| CN110019213A (en) * | 2017-12-04 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Data managing method, device, electronic equipment and storage medium |
| CN110019496A (en) * | 2017-07-27 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Data read-write method and system |
| 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 (1)
| Title |
|---|
| 基于Hadoop的医疗健康数据管理系统研究与设计;蔡全福;中国优秀硕士学位论文全文数据库 信息科技辑(第01期);第I138-428页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112951437A (en) | 2021-06-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114116613B (en) | Metadata query method, device and storage medium based on distributed file system | |
| CN109766362B (en) | Data processing method and device | |
| CN107122379B (en) | Collecting transaction data associated with a locally stored data file | |
| US11392567B2 (en) | Just-in-time multi-indexed tables in a shared log | |
| EP3579111A1 (en) | Flash file system and data management method thereof | |
| US20180364915A1 (en) | Method and system for distributed storage using client-side global persistent cache | |
| US8560496B2 (en) | Database query across processes with change notification | |
| CN109684270B (en) | Database archiving method, device, system, equipment and readable storage medium | |
| US9438672B2 (en) | Method for client specific database change propagation | |
| US10521611B2 (en) | Method and system for emergency data destruction | |
| CN115525221A (en) | Data updating method, device, equipment and medium | |
| CN115729912A (en) | Database access system, database access method, computer device, and storage medium | |
| US10671592B2 (en) | Self-maintaining effective value range synopsis in presence of deletes in analytical databases | |
| CN112951437B (en) | Medical data management method, medical data management device, storage medium and electronic equipment | |
| US20190114082A1 (en) | Coordination Of Compaction In A Distributed Storage System | |
| CN112764662B (en) | Method, apparatus and computer program product for storage management | |
| CN111176705A (en) | Feature library upgrading method and device | |
| CN110750268B (en) | File cleaning method and device, computer readable storage medium and electronic equipment | |
| CN115640280A (en) | Data migration method and device | |
| CN109815194B (en) | Indexing method, indexing device, computer readable storage medium, and electronic apparatus | |
| US9760485B2 (en) | Fast write and management of persistent cache in a system that includes tertiary storage | |
| CN112631741A (en) | Transaction processing method, device and storage medium | |
| CN111858144A (en) | Method, apparatus and computer program product for storage management | |
| US12079094B2 (en) | Data backup method, data recovery method, and electronic equipment | |
| CN112685378B (en) | Method, apparatus and computer readable storage medium for garbage collection |
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 |