CN116401303A - Hospital multi-database data management method and related device for kidney disease treatment - Google Patents
Hospital multi-database data management method and related device for kidney disease treatment Download PDFInfo
- Publication number
- CN116401303A CN116401303A CN202310395669.4A CN202310395669A CN116401303A CN 116401303 A CN116401303 A CN 116401303A CN 202310395669 A CN202310395669 A CN 202310395669A CN 116401303 A CN116401303 A CN 116401303A
- Authority
- CN
- China
- Prior art keywords
- data table
- field
- bit
- group
- topology
- 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
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/256—Integrating or interfacing systems involving database management systems in federated or virtual databases
-
- 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
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- 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)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Business, Economics & Management (AREA)
- Business, Economics & Management (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Biomedical Technology (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The application relates to a hospital multi-database data management method and a related device for kidney disease treatment, wherein the method comprises the following steps: creating a new data table, presetting an operation field in the new data table, and selecting a target data table based on the current operation bit; resetting a preset field of an operation field after an operation bit based on the record information of the historical data table; matching operation fields from a topology table group of the target data table and establishing a mapping relation with the operation fields of the newly built data table; pre-inputting the data of the mapped operation field to be used as the data of the operation field of the newly built data table and displaying the data; and acquiring user determination information to determine an operation field, returning to the previous step when acquiring the user revision information, and ending until the operation bit moves to the last bit of the field group. The method has the advantage of being capable of effectively integrating different data tables of different databases such as medical record tables, medical consumable tables, medical process tables and the like for query.
Description
Technical Field
The present application relates to the field of medical information management systems, and more particularly, to a hospital multi-database data management method for kidney disease treatment and related devices.
Background
The kidney disease treatment is an important field in a modern medical system, effectively integrates and analyzes medical records of kidney disease patients, medical consumable use conditions and data of various diagnosis and treatment processes, and has important significance for improving treatment quality, reducing medical cost and optimizing resource allocation. However, in the prior art, these data are often distributed among systems of various departments, and communication and cooperation with each other are not smooth.
The operation fields of the data tables in different databases often have differences, and are relatively cumbersome because of the unfamiliarity of databases in other departments, it is difficult to find a corresponding table when using join or the like, and it is difficult to learn or accurately correspond to a certain operation field. In addition, because of privacy requirements, databases of different departments are not properly and completely open to the outside, so it is more difficult to learn the corresponding operation field names and data table names.
In order to solve this problem, a related method capable of effectively integrating different data tables of different databases such as a medical record table, a medical consumable table, a medical procedure table and the like to perform deeper data analysis and information sharing is needed.
Disclosure of Invention
In order to effectively integrate different data tables of different databases such as a medical record table, a medical consumable table, a medical process table and the like for query, the application provides a hospital multi-database data management method for kidney disease treatment and a related device.
In a first aspect, the application provides a hospital multi-database data management method for kidney disease treatment, which adopts the following technical scheme:
a hospital multi-database data management method for kidney disease treatment, comprising the steps of:
s1, creating a new data table, and presetting operation fields in the new data table, wherein the operation fields in the new data table are combined to form a field group, and the first bit of the field group is the current operation bit;
s2, selecting a target data table based on the current operation bit, wherein the target data table corresponds to a topology table group, the topology table group comprises a plurality of data tables establishing a topological relation with the target data table, and the topology table group of the target data table is used for providing information required to be input into a newly-built data table;
s3, matching the operation bits and a plurality of continuous operation fields in front of the operation bits in the record information of the historical data table, and resetting the preset fields of the operation fields behind the operation bits based on a matching result;
S4, matching operation fields from a topology table group of the target data table based on the newly built data table and establishing a mapping relation;
s5, pre-inputting data of the operation field mapped in the topology table group corresponding to the current target data table to serve as data of the operation field of the newly built data table corresponding to the current operation bit and the field group after the current operation bit and displaying the data;
s6, acquiring user determination information to control the operation bits to move backwards along the operation fields of the field groups until the user revision information is acquired, returning to S2, or ending when the operation bits move to the last bit of the field groups, wherein the user determination information corresponds to the movement of the operation bits, and each movement of the operation bits corresponds to at least one operation field.
By adopting the technical scheme, the preset operation field is utilized to preset after the new data table is built, and the set operation field is temporary and can be adjusted in real time based on the later operation. After the target data table is selected, the preset operation field in the newly built data table will automatically match the operation field recommended preferentially from the topology table group of the target data table. Because the selection of the operation fields has continuity, based on the continuous selection of the operation fields, the operation bits and the fields after the operation bits can be recommended better. After readjusting the operation field, corresponding data is obtained from the topology table group for pre-display so as to facilitate the operator to determine the correctness of the operation field matched with the operation bit. If the operation field matched by the operation bit is incorrect, the user inputs user revision information to redefine the target data table or manually reselect the operation field with lower recommendation degree, thereby adjusting the topology table group. By performing the above operation on each operation bit, the user can be prevented from directly reading all information of the database, and the data security is ensured. In addition, the management method can avoid the direct modification of the database by the user by additionally establishing the topological relation outside the database, thereby ensuring the safety of the data. Meanwhile, the method can effectively integrate different data tables of different databases such as a medical record table, a medical consumable table, a medical process table and the like for inquiring based on the use habit of the user, and improves the working efficiency.
Optionally, the step S1 includes the following steps:
s11, acquiring historical data table recording information, and selecting a field group based on the historical data table recording information, wherein the historical data table recording information comprises a field group generated by a current user account history creation data table;
s12, creating a new data table, and taking the selected field set as a preset operation field of the new data table.
By adopting the technical scheme, as users have different requirements, the required field groups can be preselected in the initial stage. However, since the operation fields of the data tables in different databases are different, a later correction is required. The pre-selection in the early stage can better improve the accuracy of the later-stage selected operation field and reduce the operation amount of the later-stage user.
Optionally, the topology table group includes a target data table, a topology data table and a topology table group of associated data tables, where the target data table and the associated data table are at least connected to one topology data table in a key manner, the topology data table is at least connected to one topology data table or the target data table or the associated data table in a key manner, the priority of the target data table is the highest level, the priority of the topology data table connected to the target data table is three levels, and the priority of each data table in the topology table group of the associated data table in the topology table group of the target data table is the original priority in the topology table group of the associated data table plus one level.
By adopting the technical scheme, because different data tables are usually associated through the main key and the external key, it can be considered that the data tables in a single database are not isolated, and can be associated through key connection, namely, the topological connection relationship between the topological data tables and the association relationship between the topological data tables and the target data tables. Meanwhile, because data which can be associated with each other exist between different databases, such as product data of dialysate and use of the dialysate by a user on a medical record table, the data tables cannot be associated with each other through key connection, so that in the application, in the process of associated use, the data tables record association relations through a topology table group, and later use is facilitated. While different data tables have different priorities, i.e. the "distance" of the required operation field from the target data table is related to the probability of occurrence of the required operation field.
Optionally, the step S3 includes the following steps:
s31, taking operation bits and a plurality of continuous operation fields in front of the operation bits for a plurality of times with different bits to respectively serve as fields to be screened, wherein the more the operation fields are contained, the higher the weight is, and the weight is taken as the screening weight;
S32, calculating the occurrence frequency of different screening fields in the historical data record information, and calculating to obtain the field to be screened with the highest priority based on the frequency and the corresponding screening weight;
s33, determining a corresponding field group based on the field to be screened with the highest priority, and resetting the field of the field group after the operation field corresponding to the operation bit as the operation field after the operation bit.
By adopting the technical scheme, the operation field where the operation bit is located can be subjected to continuous multiple adjustment in the moving process of the operation bit, so that continuous adjustment is avoided to be continuously carried out later, and the operation field before the operation bit is subjected to integral matching again, thereby being beneficial to matching to obtain a more proper field group. When the priority of the continuous operation field that can be matched is higher, it is explained that the field group that is more likely to be required by the current user.
Optionally, the step S4 includes the following steps:
s41, judging whether a data table corresponding to an operation field of the last operation bit and a data table corresponding to an operation field of the current operation bit are in the same topology table group or not; if not, adding the target data table corresponding to the last operation bit into the topology table group of the target data table corresponding to the current operation bit to serve as an associated data table of the target data table, and updating the topology table group of the target data table corresponding to the current operation bit; if so, the priority of the target data table corresponding to the current operation bit in the expansion table group of the target data table corresponding to the previous operation bit is increased by one level until the highest, and the priority of the target data table corresponding to the previous operation bit in the expansion table group of the target data table corresponding to the current operation bit is increased by one level until the highest;
S42, respectively acquiring operation fields of each current and subsequent operation bit in a topology table group of a target data table corresponding to the current operation bit, and respectively recommending one or more operation fields to the current operation bit and the subsequent operation bit based on a recommendation level of the operation field; the recommendation level of the operation field is determined based on the priority of the data table in which the operation field is located in the corresponding topology table group and the recommendation level of the operation field in the data table in which the operation field is located;
s43, pre-establishing the mapping relation between the operation fields of the current operation bit and the operation fields with the highest corresponding recommended priorities.
By adopting the technical scheme, the topology table group can be continuously adjusted in the operation process, so that the topology table group can be more suitable for the use habit of the current user account.
Optionally, the step S42 includes the following steps:
s421, respectively acquiring operation fields of each current and subsequent operation bit in a topology table group of a target data table corresponding to the current operation bit;
s422, judging whether each operation bit in the current and subsequent operation bits corresponds to an operation field in the topology table group, if not, marking a mark to be matched in the corresponding operation bit, and if so, entering the next step;
S423, reading the historical mapping times of each operation field in a topology table group corresponding to a target data table corresponding to the current operation bit, wherein the historical mapping times are the total mapping times of the corresponding operation field of the topology table group of one data table in a newly created data table created by the current user account for fifty times;
s424, calculating to obtain the reference frequency of each operation field in the data table based on the historical mapping times of each operation field in the data table, and determining the recommended level of the operation field in the data table based on the reference frequency;
s425, calculating the reference frequency of the data table in the topology table group based on the sum of the historical mapping times of each operation field in the data table, and determining the priority of each data table in the topology table group based on the reference frequency;
s426, determining the recommended level of the operation field in the corresponding topology table group based on the priority of the data table in which the operation field is located in the topology table group and the recommended level of the operation field in the data table in which the operation field is located;
s427, recommending one or more operation fields to the current operation bit and the following operation bits respectively based on the recommendation level of the operation fields.
By adopting the technical scheme, the operation field most likely to be used by the user can be recommended.
Optionally, the step S6 includes the following steps:
s61, acquiring user determination information, and increasing the historical mapping times of corresponding operation fields in a topology table group corresponding to the target data table based on the user determination information;
s62, judging whether field mapping record times of an operation field with highest field mapping record times in each data table in a target topology table group are smaller than table mapping times of all data tables with lower priority in the target topology table group, if so, reducing the corresponding first-level priority of the data tables, wherein the target topology table group is a topology table group corresponding to the operation field of an operation bit, the field mapping record times are total mapping times of a certain operation field in all new data tables created in the last fifty times, and the table mapping record times are total mapping times of all operation fields in a certain data table in all new data tables created in the last fifty times;
s63, judging whether the field mapping record times of the operation field with the highest field mapping record times in each data table in the target topology table group exceeds the table mapping times of the data table with the lowest table mapping record times in all data tables with higher priority in the target topology table group, if so, increasing the corresponding data table primary priority;
S64, controlling the operation bit to move backwards along the field group of the newly built data table based on the user determination information, wherein the moving step length is an operation field;
s65, detecting whether the operation bit moves to move backwards to the last bit along the field set of the newly built data table, if not, entering the next step, and if so, inquiring whether the next bit is newly added: if yes, adding the next bit to enter the next step, and if not, directly entering the next step;
s66, detecting whether user revision information is received, if yes, returning to S2, and if not, ending.
By adopting the technical scheme, the topology table group can be continuously adjusted in the operation process, so that the topology table group can be more suitable for the use habit of the current user account.
In a second aspect, the application provides a multi-database data management system for a hospital for treating kidney diseases, which adopts the following technical scheme:
a hospital multi-database data management system for kidney disease treatment, comprising:
the table creation module is used for creating a new data table and presetting operation fields in the new data table, wherein the operation fields in the new data table are combined to form a field group, and the first bit of the field group is the current operation bit;
The target data table selecting module is used for selecting a target data table based on the current operation bit, wherein the target data table corresponds to a topology table group, the topology table group comprises a plurality of data tables establishing a topological relation with the target data table, and the topology table group of the target data table is used for providing information needing to be input into a newly-built data table;
the matching setting module is used for matching the operation bits and a plurality of continuous operation fields in front of the operation bits in the record information of the historical data table, and resetting the preset fields of the operation fields behind the operation bits based on a matching result;
the matching mapping module is used for matching operation fields from the topology table group of the target data table based on the newly built data table and establishing a mapping relation;
the pre-input display module is used for pre-inputting the data of the mapped operation field in the topology table group corresponding to the current target data table to be used as the data of the operation field of the newly built data table corresponding to the current operation bit and the field group after the current operation bit and displaying the data;
and the information determining module is used for acquiring user determining information to control the operation bits to move backwards along the operation fields of the field groups until the user revision information is acquired, returning to be processed by the target data table selecting module, or ending when the operation bits move to the last bit of the field groups, wherein the user determining information corresponds to the movement of the operation bits, and each movement of the operation bits corresponds to at least one operation field.
In a third aspect, the present application provides a computer device, which adopts the following technical scheme:
a computer apparatus, comprising:
one or more processors;
a memory;
one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to: the hospital multi-database data management method for kidney disease treatment described above is performed.
In a fourth aspect, the present application provides a computer readable storage medium, which adopts the following technical scheme:
a computer readable storage medium storing a computer program capable of being loaded by a processor and executing the method as described above.
The storage medium stores at least one instruction, at least one program, a set of codes, or a set of instructions that are loaded and executed by the processor to implement: the hospital multi-database data management method for kidney disease treatment.
Drawings
Fig. 1 is a schematic view of an application environment of a hospital database data management method for kidney disease treatment according to an embodiment of the invention.
FIG. 2 is a flow chart of a method for managing multi-database data in a hospital for kidney disease treatment according to an embodiment of the invention.
FIG. 3 is a block diagram showing the steps S1 in an embodiment of the invention.
FIG. 4 is a block diagram showing the flow of the step S3 according to an embodiment of the invention.
FIG. 5 is a block diagram showing the flow of the step S4 according to an embodiment of the invention.
FIG. 6 is a block diagram showing the steps S42 according to an embodiment of the invention.
FIG. 7 is a block diagram showing the flow of the step S6 according to an embodiment of the invention.
FIG. 8 is a schematic diagram of a computer device according to an embodiment of the invention.
Detailed Description
The present application is described in further detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the inventive concepts. As part of this specification, some of the drawings of the present disclosure represent structures and devices in block diagram form in order to avoid obscuring the principles of the disclosure. In the interest of clarity, not all features of an actual implementation are necessarily described. Furthermore, the language used in the present disclosure has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the requisite claims to determine such inventive subject matter. Reference in the present disclosure to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment, and multiple references to "one embodiment" or "an embodiment" should not be understood as necessarily all referring to the same embodiment.
The terms "a," "an," and "the" are not intended to refer to a singular entity, but rather include the general class of which a particular example may be used for illustration, unless clearly defined. Thus, the use of the terms "a" or "an" may mean any number of at least one, including "one", "one or more", "at least one", and "one or more than one". The term "or" means any of the alternatives and any combination of alternatives, including all alternatives, unless alternatives are explicitly indicated as mutually exclusive. The phrase "at least one of" when combined with a list of items refers to a single item in the list or any combination of items in the list. The phrase does not require all of the listed items unless specifically so defined.
In the field of kidney disease treatment, the role of the medical information database is of paramount importance. Through maintenance and management of various databases, better, more convenient and faster medical services can be provided for patients.
Medical institution database: for the field of kidney disease treatment, the database records information about specialized kidney disease treatment hospitals, such as hospital name, hospital type, hospital grade, address, contact phone, hospital profile, and hospital department. This information helps the patient find the appropriate kidney disease treatment hospital while also helping the medical facility to better manage the resources.
Medical device database: the field of kidney disease treatment requires specialized medical equipment such as hemodialysis machines, renal ultrasound, and the like. The database records information about the devices, including device names, device models, manufacturers, date of purchase, warranty period, maintenance personnel, etc. The information is helpful for medical institutions to maintain and replace equipment in time, and normal operation of the equipment and safety of patients are ensured.
Medical staff database: for the field of kidney disease treatment, the database records information of medical staff, such as name, gender, job title, age of use and department (such as nephrology department, kidney transplantation department, etc.). The information is helpful for medical institutions to effectively train and manage medical staff, and improves the professional level of kidney disease treatment.
Medical resource scheduling database: in the field of renal disease treatment, the course of treatment of patients involves multiple departments and doctors. The database records patient information, medical departments of medical treatment, doctor information, diagnosis results, medical resource allocation conditions and the like. The information is helpful for medical institutions to better utilize medical resources, and ensures that patients are timely and effectively treated.
Through the maintenance and management of the database, more specialized and efficient treatment services can be provided for the patient suffering from the kidney disease, so that the treatment effect and the patient satisfaction are improved.
For example, a medical institution is developing a comprehensive treatment regimen for chronic kidney disease patients in order to find an optimal treatment method, reduce the incidence of kidney disease and improve the quality of life of the patients. To complete this study, existing databases of various types need to be recalled and combined.
First, by calling the medical institution database, all hospitals having the kidney disease treatment ability can be screened out so as to analyze the treatment effect and cases of each hospital.
Secondly, the condition of kidney disease treatment equipment used by each hospital can be known by calling a medical equipment database, including equipment model, manufacturers and the like, so as to evaluate the influence of equipment quality and technical level on the treatment effect.
Next, by calling the medical staff database, the professional conditions of the kidney disease treatment field of each hospital, such as job title, service life, etc., can be known to analyze the influence of doctor skills on the treatment effect.
Finally, patient visit information, diagnosis results, treatment schemes, etc. can be collected by calling the medical resource scheduling database to evaluate the efficacy and safety of various treatment methods.
However, it is now true that these data are often distributed among systems of various departments, and communication and cooperation with each other are not smooth. The operation fields of the data tables in different databases often have differences, and are relatively cumbersome because of the unfamiliarity of databases in other departments, it is difficult to find a corresponding table when using join or the like, and it is difficult to learn or accurately correspond to a certain operation field. In addition, because of privacy requirements, databases of different departments are not properly and completely open to the outside, so it is more difficult to learn the corresponding operation field names and data table names.
Accordingly, embodiments of the present application disclose a hospital multi-database data management method for kidney disease treatment. The multi-database data management method for the kidney disease treatment provided by the embodiment of the invention can be applied to an application environment as shown in fig. 1, wherein the multi-database data management method for the kidney disease treatment is applied to a multi-database data management system for the kidney disease treatment, and the multi-database data management system for the kidney disease treatment comprises a client and a server, wherein the client communicates with the server through a network. The client is also called a client, and refers to a program corresponding to a server and providing local services for the client. Further, the client is a computer-side program, an APP program of the intelligent device or a third party applet embedded with other APP. The client may be installed on, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, portable wearable devices, and other computer devices. The server may be implemented as a stand-alone server or as a server cluster composed of a plurality of servers.
Referring to fig. 2, the hospital multi-database data management method for kidney disease treatment includes at least S1 to S6.
S1, creating a new data table, and presetting operation fields in the new data table, wherein the operation fields in the new data table are combined to form a field group, and the first bit of the field group is the current operation bit.
The operation fields in the field set have an order, and the elements in the analog array may be included in the operation fields in the field set, but in different embodiments, the field set may be generated by different data structures to store the operation fields, where the operation fields in the field set may be arranged in a predetermined order. The operation bit is a certain bit in the field group, and in different steps, the operation bit can be different and can be moved.
Specifically, referring to fig. 3, in one embodiment, S1 includes two steps S11 and S12.
S11, acquiring historical data table recording information, and selecting a field group based on the historical data table recording information, wherein the historical data table recording information comprises a field group generated by a current user account history creation data table.
S12, creating a new data table, and taking the selected field set as a preset operation field of the new data table.
Since the users have different needs, the required field sets can be pre-selected in the initial stage. However, since the operation fields of the data tables in different databases are different, a later correction is required. The pre-selection in the early stage can better improve the accuracy of the later-stage selected operation field and reduce the operation amount of the later-stage user.
S2, selecting a target data table based on the current operation bit, wherein the target data table corresponds to a topology table group, the topology table group comprises a plurality of data tables establishing a topological relation with the target data table, and the topology table group of the target data table is used for providing information required to be input into a newly-built data table.
The topology table group comprises a target data table, a topology data table and a topology table group of associated data tables, wherein the target data table and the associated data table are at least connected with one topology data table in a key way, the topology data table is at least connected with one topology data table or the target data table or the associated data table in a key way, the priority of the target data table is the highest level, the priority of the topology data table which is connected with the target data table in a topology way is three levels, and the priority of each data table in the topology table group of the associated data table in the topology table group of the target data table is the original priority in the topology table group of the associated data table plus one level.
Since different data tables are usually associated by a primary key and a foreign key, it can be considered that the data tables in a single database are not usually isolated, and can be associated by key connection, that is, the topological connection relationship between the topological data tables and the association relationship between the topological data tables and the target data tables. Meanwhile, because data which can be associated with each other exist between different databases, such as product data of dialysate and use of the dialysate by a user on a medical record table, the data tables cannot be associated with each other through key connection, so that in the application, in the process of associated use, the data tables record association relations through a topology table group, and later use is facilitated. While different data tables have different priorities, i.e. the "distance" of the required operation field from the target data table is related to the probability of occurrence of the required operation field.
For example, the topology table group has A, B, C, D, E five tables, wherein A is a target data table, B is in topological connection with A through an external key, C is in topological connection with B through an external key, and both B and C are topology data tables; d is an associated data table, E is connected with the D topology through an external key, and D and E are topology table groups of the associated data table of the target data table.
S3, matching the operation bits and a plurality of continuous operation fields in front of the operation bits in the record information of the historical data table, and resetting the preset fields of the operation fields behind the operation bits based on a matching result.
Because the operation field where the operation bit is located may face continuous multiple adjustments during the moving process, in order to avoid continuous adjustments from continuously occurring in the following, the operation field before the operation bit is subjected to overall matching again, which is beneficial to obtaining a more suitable field set. When the priority of the continuous operation field that can be matched is higher, it is explained that the field group that is more likely to be required by the current user.
By way of example, referring to FIG. 4, S3 includes three steps S31-S33 in one embodiment.
S31, taking the operation bits and a plurality of continuous operation fields in front of the operation bits for a plurality of times with different bits to respectively serve as fields to be screened, wherein the more the operation fields are contained, the higher the weight is, and the weight is taken as the screening weight.
For example, if the operation field preceding the operation bit is ABCDE, E, DE, CDE, BCDE, ABCDE is the continuous operation field. The screening weights of E, DE, CDE, BCDE, ABCDE can be set to a1, b1, c1, d1, e1, and a1< b1< c1< d1< e1.
S32, calculating the occurrence frequency of different screening fields in the historical data record information, and calculating the fields to be screened with the highest priority based on the frequency and the corresponding screening weight.
In the example of the reception S31, the frequencies of occurrence of E, DE, CDE, BCDE, ABCDE in the history information are different, and the frequencies of E, DE, CDE, BCDE, ABCDE are a2, b2, c2, d2, and e2, respectively, and it is confirmed that a2> b2> c2> d2> e2. At this time, the sizes of a1a2, b1b2, c1c2, d1d2, e1e2d are calculated, and the maximum value corresponds to the field to be screened with the highest priority.
S33, determining a corresponding field group based on the field to be screened with the highest priority, and resetting the field of the field group after the operation field corresponding to the operation bit as the operation field after the operation bit.
In the example of adapting S31, if the CDE is the field to be screened with the highest priority, since the CDE may correspond to a plurality of different field groups, the field group with the highest frequency of use in the field group corresponding to the CDE is taken. Then the field of the field set corresponding to the CDE after the operation field corresponding to the operation bit is reset to the operation field after the operation bit.
S4, matching operation fields from the topology table group of the target data table based on the newly built data table and establishing a mapping relation.
Specifically, referring to FIG. 5, S4 includes three steps S41-S43 in one embodiment.
S41, judging whether a data table corresponding to an operation field of the last operation bit and a data table corresponding to an operation field of the current operation bit are in the same topology table group or not; if not, adding the target data table corresponding to the last operation bit into the topology table group of the target data table corresponding to the current operation bit to serve as an associated data table of the target data table, and updating the topology table group of the target data table corresponding to the current operation bit; if so, the priority of the target data table corresponding to the current operation bit in the expansion table group of the target data table corresponding to the previous operation bit is increased by one level until the highest, and the priority of the target data table corresponding to the previous operation bit in the expansion table group of the target data table corresponding to the current operation bit is increased by one level until the highest.
For example, if the operation field of the operation bit is F and the operation field preceding the operation bit is ABCDE, the operation field of the operation bit immediately preceding the operation bit is E, and the data tables corresponding to E and F are not in the same topology table group, which means that the target data table is replaced in the current operation bit. And adding the topology table group of the target data table corresponding to the E into the topology table group of the target data table corresponding to the F to serve as the associated data table of the target data table and the topology table group of the associated data table.
Because the field set is continuously adjusted, and the recommendation level of the operation field in the field set is also continuously changed, if the data tables corresponding to E and F are in the same topology table group, the data tables corresponding to E and F may be the data tables with lower priority in the topology table group manually selected by the user, for example, the data tables which need to be connected by external keys for a plurality of times from the target data table. When the data table is used once, the possibility of acquiring required data in the data table is generally high, so that the accuracy of data recommendation can be improved through the scheme.
S42, respectively acquiring operation fields of each current and subsequent operation bit in a topology table group of a target data table corresponding to the current operation bit, and respectively recommending one or more operation fields to the current operation bit and the subsequent operation bit based on a recommendation level of the operation field; the recommendation level of the operation field is determined based on the priority of the data table where the operation field is located in the corresponding topology table group and the recommendation level of the operation field in the data table where the operation field is located.
Specifically, S42, in one embodiment, referring to fig. 6, includes seven steps S421-S427.
S421, respectively acquiring operation fields of each current operation bit and each subsequent operation bit in a topology table group of the target data table corresponding to the current operation bit.
S422, judging whether each operation bit in the current and subsequent operation bits corresponds to an operation field in the topology table group, if not, marking a mark to be matched in the corresponding operation bit, and if so, entering the next step.
The flag to be matched means that the relevant operation field cannot be matched from the topology table group at the position, and the user is required to re-determine or newly select the target data table.
S423, reading the historical mapping times of each operation field in the topology table group corresponding to the target data table corresponding to the current operation bit, wherein the historical mapping times are the total mapping times of the corresponding operation field of the topology table group of one data table in the newly created data table created by the current user account for fifty times.
For example, if the operation field corresponding to the current operation bit is F, the F has five data tables in the topology table group corresponding to the corresponding target data table, four data tables in the five data tables include the operation field F, and the total mapping times in the new data table created by the current user account for fifty times are 1 time, 3 times, 0 time and 2 times respectively. The total number of mappings is 6. It should be noted that, although five data tables are topologically connected and four data tables include the operation field F, the F fields of the four data tables are not necessarily the primary key and the foreign key, that is, the internal data are not necessarily the same.
It should be noted that if the user account is a new user and the number of times of creating the new data table is not more than fifty times, the total mapping number of the corresponding operation field of the topology table group of one data table in the new data table of all times of creating the current user account is taken as the historical mapping number.
S424, calculating the reference frequency of each operation field in the data table based on the historical mapping times of each operation field in the data table, and determining the recommended level of the operation field in the data table based on the reference frequency.
The reference frequency herein refers to a ratio of a historical mapping number of a single operation field in a single data table to a total historical mapping number of each operation field, and is used to reflect how frequently an operation field is used in the data table.
S425, calculating the reference frequency of the data table in the topology table group based on the sum of the historical mapping times of each operation field in the data table, and determining the priority of each data table in the topology table group based on the reference frequency.
The reference frequency refers to the ratio of the historical mapping times of a single data table to the total historical mapping times of all data tables in the topology table group where the data table is located.
S426, determining the recommendation level of the operation field in the corresponding topology table group based on the priority of the data table in which the operation field is located in the topology table group and the recommendation level of the operation field in the data table.
In different embodiments, the calculation method of the recommended level of the operation field in the corresponding topology table group may be different, for example, the priority of the data table in which the operation field is located in the topology table group is utilized to perform multiplication, and the recommended level of the operation field in the data table in which the operation field is located is utilized to perform multiplication.
S427, recommending one or more operation fields to the current operation bit and the following operation bits respectively based on the recommendation level of the operation fields.
For example, the recommended best operation field may be displayed directly in a field set of a data table pre-displayed in a screen, and suboptimal several operation fields may exist as a drop-down menu of the best operation field.
S43, pre-establishing the mapping relation between the operation fields of the current operation bit and the operation fields with the highest corresponding recommended priorities.
S5, pre-inputting the data of the operation field mapped in the topology table group corresponding to the current target data table to serve as the data of the operation field corresponding to the current operation bit and the field group after the current operation bit of the new data table, and displaying the data.
For example, join, unit, or other database query may be used to assist in displaying the data of the mapped operation fields in a pre-displayed data table on the screen.
S6, acquiring user determination information to control the operation bits to move backwards along the operation fields of the field groups until the user revision information is acquired, returning to S2, or ending when the operation bits move to the last bit of the field groups, wherein the user determination information corresponds to the movement of the operation bits, and each movement of the operation bits corresponds to at least one operation field.
Specifically, in one embodiment, referring to FIG. 7, S6 may include steps S61-S66.
S61, acquiring user determination information, and increasing the historical mapping times of corresponding operation fields in the topology table group corresponding to the target data table based on the user determination information.
S62, judging whether field mapping record times of an operation field with highest field mapping record times in each data table in a target topology table group are smaller than table mapping times of all data tables with lower priority in the target topology table group, if so, reducing the priority of the corresponding data table, wherein the target topology table group is a topology table group corresponding to the operation field of an operation bit, the field mapping record times are total mapping times of a certain operation field in all new data tables created in the last fifty times, and the table mapping record times are total mapping times of all operation fields in a certain data table in all new data tables created in the last fifty times.
S63, judging whether the field mapping record times of the operation field with the highest field mapping record times in each data table in the target topology table group exceeds the table mapping times of the data table with the lowest table mapping record times in all the data tables with higher priority levels in the target topology table group, if so, increasing the corresponding data table with the first priority level.
S64, controlling the operation bit to move backwards along the field group of the newly built data table based on the user determination information, wherein the moving step length is one operation field.
S65, detecting whether the operation bit moves to move backwards to the last bit along the field set of the newly built data table, if not, entering the next step, and if so, inquiring whether the next bit is newly added: if yes, the next bit is added and the next step is carried out, and if not, the next step is directly carried out.
S66, detecting whether user revision information is received, if yes, returning to S2, and if not, ending.
By adopting the technical scheme, the topology table group can be continuously adjusted in the operation process, so that the topology table group can be more suitable for the use habit of the current user account.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present invention.
In one embodiment, a multi-database data management system for kidney disease treatment is provided, which corresponds to the multi-database data management method for kidney disease treatment in the above embodiment one by one. The hospital multi-database data management system for kidney disease treatment comprises a table creation module, a target data table selection module, a matching setting module, a matching mapping module, a pre-input display module and an information determination module. The functional modules are described in detail as follows:
the table creation module is used for creating a new data table and presetting operation fields in the new data table, wherein the operation fields in the new data table are combined to form a field group, and the first bit of the field group is the current operation bit;
the target data table selecting module is used for selecting a target data table based on the current operation bit, wherein the target data table corresponds to a topology table group, the topology table group comprises a plurality of data tables establishing a topological relation with the target data table, and the topology table group of the target data table is used for providing information needing to be input into a newly-built data table;
the matching setting module is used for matching the operation bits and a plurality of continuous operation fields in front of the operation bits in the record information of the historical data table, and resetting the preset fields of the operation fields behind the operation bits based on a matching result;
The matching mapping module is used for matching operation fields from the topology table group of the target data table based on the newly built data table and establishing a mapping relation;
the pre-input display module is used for pre-inputting the data of the mapped operation field in the topology table group corresponding to the current target data table to be used as the data of the operation field of the newly built data table corresponding to the current operation bit and the field group after the current operation bit and displaying the data;
and the information determining module is used for acquiring user determining information to control the operation bits to move backwards along the operation fields of the field groups until the user revision information is acquired, returning to be processed by the target data table selecting module, or ending when the operation bits move to the last bit of the field groups, wherein the user determining information corresponds to the movement of the operation bits, and each movement of the operation bits corresponds to at least one operation field.
Specific limitations regarding the hospital multi-database data management system for the treatment of kidney disease can be found in the above description of the method of hospital multi-database data management for the treatment of kidney disease, and will not be repeated here. The various modules in the hospital multi-database data management system for kidney disease treatment described above may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 8. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for data related to a hospital multi-database data management method for treating kidney diseases. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by a processor, implements a hospital multi-database data management method for kidney disease treatment.
In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the hospital multi-database data management method for kidney disease treatment of the above embodiment, such as S1 to S6 shown in fig. 2. To avoid repetition, no further description is provided here.
In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, which when executed by a processor implements the hospital multi-database data management method for kidney disease treatment of the above embodiment, such as S1 to S6 shown in fig. 2. To avoid repetition, no further description is provided here.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments of the present application may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions.
The above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention, and are intended to be included in the scope of the present invention.
Claims (10)
1. A hospital multi-database data management method for kidney disease treatment, comprising the steps of:
s1, creating a new data table, and presetting operation fields in the new data table, wherein the operation fields in the new data table are combined to form a field group, and the first bit of the field group is the current operation bit;
S2, selecting a target data table based on the current operation bit, wherein the target data table corresponds to a topology table group, the topology table group comprises a plurality of data tables establishing a topological relation with the target data table, and the topology table group of the target data table is used for providing information required to be input into a newly-built data table;
s3, matching the operation bits and a plurality of continuous operation fields in front of the operation bits in the record information of the historical data table, and resetting the preset fields of the operation fields behind the operation bits based on a matching result;
s4, matching operation fields from a topology table group of the target data table based on the newly built data table and establishing a mapping relation;
s5, pre-inputting data of the operation field mapped in the topology table group corresponding to the current target data table to serve as data of the operation field of the newly built data table corresponding to the current operation bit and the field group after the current operation bit and displaying the data;
s6, acquiring user determination information to control the operation bits to move backwards along the operation fields of the field groups until the user revision information is acquired, returning to S2, or ending when the operation bits move to the last bit of the field groups, wherein the user determination information corresponds to the movement of the operation bits, and each movement of the operation bits corresponds to at least one operation field.
2. The hospital multi-database data management method for kidney disease treatment according to claim 1, wherein S1 comprises the steps of:
s11, acquiring historical data table recording information, and selecting a field group based on the historical data table recording information, wherein the historical data table recording information comprises a field group generated by a current user account history creation data table;
s12, creating a new data table, and taking the selected field set as a preset operation field of the new data table.
3. The hospital multi-database data management method for kidney disease treatment according to claim 1 or 2, wherein the topology table group comprises a target data table, a topology data table and a topology table group of associated data tables, wherein the target data table and the associated data table are at least keyed to one topology data table, the topology data table is at least keyed to one topology data table or the target data table or the associated data table, the priority of the target data table is the highest level, the priority of the topology data table of which the target data table is topologically connected is three levels, and the priority of each data table in the topology table group of the associated data table in the topology table group of the target data table is the original priority in the topology table group of the associated data table plus one level.
4. The hospital multi-database data management method for kidney disease treatment according to claim 3, wherein said S3 comprises the steps of:
s31, taking operation bits and a plurality of continuous operation fields in front of the operation bits for a plurality of times with different bits to respectively serve as fields to be screened, wherein the more the operation fields are contained, the higher the weight is, and the weight is taken as the screening weight;
s32, calculating the occurrence frequency of different screening fields in the historical data record information, and calculating to obtain the field to be screened with the highest priority based on the frequency and the corresponding screening weight;
s33, determining a corresponding field group based on the field to be screened with the highest priority, and resetting the field of the field group after the operation field corresponding to the operation bit as the operation field after the operation bit.
5. The hospital multi-database data management method for kidney disease treatment according to claim 4, wherein said S4 comprises the steps of:
s41, judging whether a data table corresponding to an operation field of the last operation bit and a data table corresponding to an operation field of the current operation bit are in the same topology table group or not; if not, adding the target data table corresponding to the last operation bit into the topology table group of the target data table corresponding to the current operation bit to serve as an associated data table of the target data table, and updating the topology table group of the target data table corresponding to the current operation bit; if so, the priority of the target data table corresponding to the current operation bit in the expansion table group of the target data table corresponding to the previous operation bit is increased by one level until the highest, and the priority of the target data table corresponding to the previous operation bit in the expansion table group of the target data table corresponding to the current operation bit is increased by one level until the highest;
S42, respectively acquiring operation fields of each current and subsequent operation bit in a topology table group of a target data table corresponding to the current operation bit, and respectively recommending one or more operation fields to the current operation bit and the subsequent operation bit based on a recommendation level of the operation field; the recommendation level of the operation field is determined based on the priority of the data table in which the operation field is located in the corresponding topology table group and the recommendation level of the operation field in the data table in which the operation field is located;
s43, pre-establishing the mapping relation between the operation fields of the current operation bit and the operation fields with the highest corresponding recommended priorities.
6. The hospital multi-database data management method for kidney disease treatment according to claim 5, wherein S42 comprises the steps of:
s421, respectively acquiring operation fields of each current and subsequent operation bit in a topology table group of a target data table corresponding to the current operation bit;
s422, judging whether each operation bit in the current and subsequent operation bits corresponds to an operation field in the topology table group, if not, marking a mark to be matched in the corresponding operation bit, and if so, entering the next step;
s423, reading the historical mapping times of each operation field in a topology table group corresponding to a target data table corresponding to the current operation bit, wherein the historical mapping times are the total mapping times of the corresponding operation field of the topology table group of one data table in a newly created data table created by the current user account for fifty times;
S424, calculating to obtain the reference frequency of each operation field in the data table based on the historical mapping times of each operation field in the data table, and determining the recommended level of the operation field in the data table based on the reference frequency;
s425, calculating the reference frequency of the data table in the topology table group based on the sum of the historical mapping times of each operation field in the data table, and determining the priority of each data table in the topology table group based on the reference frequency;
s426, determining the recommended level of the operation field in the corresponding topology table group based on the priority of the data table in which the operation field is located in the topology table group and the recommended level of the operation field in the data table in which the operation field is located;
s427, recommending one or more operation fields to the current operation bit and the following operation bits respectively based on the recommendation level of the operation fields.
7. The hospital multi-database data management method for kidney disease treatment according to claim 6, wherein S6 comprises the steps of:
s61, acquiring user determination information, and increasing the historical mapping times of corresponding operation fields in a topology table group corresponding to the target data table based on the user determination information;
s62, judging whether field mapping record times of an operation field with highest field mapping record times in each data table in a target topology table group are smaller than table mapping times of all data tables with lower priority in the target topology table group, if so, reducing the corresponding first-level priority of the data tables, wherein the target topology table group is a topology table group corresponding to the operation field of an operation bit, the field mapping record times are total mapping times of a certain operation field in all new data tables created in the last fifty times, and the table mapping record times are total mapping times of all operation fields in a certain data table in all new data tables created in the last fifty times;
S63, judging whether the field mapping record times of the operation field with the highest field mapping record times in each data table in the target topology table group exceeds the table mapping times of the data table with the lowest table mapping record times in all data tables with higher priority in the target topology table group, if so, increasing the corresponding data table primary priority;
s64, controlling the operation bit to move backwards along the field group of the newly built data table based on the user determination information, wherein the moving step length is an operation field;
s65, detecting whether the operation bit moves to move backwards to the last bit along the field set of the newly built data table, if not, entering the next step, and if so, inquiring whether the next bit is newly added: if yes, adding the next bit to enter the next step, and if not, directly entering the next step;
s66, detecting whether user revision information is received, if yes, returning to S2, and if not, ending.
8. A hospital multi-database data management system for the treatment of kidney disease, comprising:
the table creation module is used for creating a new data table and presetting operation fields in the new data table, wherein the operation fields in the new data table are combined to form a field group, and the first bit of the field group is the current operation bit;
The target data table selecting module is used for selecting a target data table based on the current operation bit, wherein the target data table corresponds to a topology table group, the topology table group comprises a plurality of data tables establishing a topological relation with the target data table, and the topology table group of the target data table is used for providing information needing to be input into a newly-built data table;
the matching setting module is used for matching the operation bits and a plurality of continuous operation fields in front of the operation bits in the record information of the historical data table, and resetting the preset fields of the operation fields behind the operation bits based on a matching result;
the matching mapping module is used for matching operation fields from the topology table group of the target data table based on the newly built data table and establishing a mapping relation;
the pre-input display module is used for pre-inputting the data of the mapped operation field in the topology table group corresponding to the current target data table to be used as the data of the operation field of the newly built data table corresponding to the current operation bit and the field group after the current operation bit and displaying the data;
and the information determining module is used for acquiring user determining information to control the operation bits to move backwards along the operation fields of the field groups until the user revision information is acquired, returning to be processed by the target data table selecting module, or ending when the operation bits move to the last bit of the field groups, wherein the user determining information corresponds to the movement of the operation bits, and each movement of the operation bits corresponds to at least one operation field.
9. A computer device, comprising:
one or more processors;
a memory;
one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to:
a hospital multi-database data management method for kidney disease treatment according to any one of claims 1 to 8 is performed.
10. A computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, the at least one instruction, the at least one program, the code set, or instruction set being loaded and executed by the processor to implement:
a hospital multi-database data management method for kidney disease treatment as claimed in any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310395669.4A CN116401303B (en) | 2023-04-12 | 2023-04-12 | Hospital multi-database data management method and related device for kidney disease treatment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310395669.4A CN116401303B (en) | 2023-04-12 | 2023-04-12 | Hospital multi-database data management method and related device for kidney disease treatment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116401303A true CN116401303A (en) | 2023-07-07 |
| CN116401303B CN116401303B (en) | 2023-11-10 |
Family
ID=87012054
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310395669.4A Active CN116401303B (en) | 2023-04-12 | 2023-04-12 | Hospital multi-database data management method and related device for kidney disease treatment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116401303B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190005086A1 (en) * | 2017-07-02 | 2019-01-03 | Equalum Ltd. | System and method for system for determining database relations based on data monitoring |
| CN110109897A (en) * | 2019-04-15 | 2019-08-09 | 深圳壹账通智能科技有限公司 | Database script generation method, device, computer equipment and storage medium |
| CN110457288A (en) * | 2019-07-04 | 2019-11-15 | 平安科技（深圳）有限公司 | Data model construction method, device, equipment and computer readable storage medium |
| WO2020185899A1 (en) * | 2019-03-14 | 2020-09-17 | Elekta, Inc. | Automated cancer registry record generation |
| CN111897818A (en) * | 2020-07-31 | 2020-11-06 | 平安普惠企业管理有限公司 | Data storage method and device, electronic equipment and storage medium |
| CN112685415A (en) * | 2020-12-30 | 2021-04-20 | 平安普惠企业管理有限公司 | Data import method and device, computer equipment and storage medium |
| CN113505128A (en) * | 2021-06-30 | 2021-10-15 | 平安科技（深圳）有限公司 | Method, device and equipment for creating data table and storage medium |
-
2023
- 2023-04-12 CN CN202310395669.4A patent/CN116401303B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190005086A1 (en) * | 2017-07-02 | 2019-01-03 | Equalum Ltd. | System and method for system for determining database relations based on data monitoring |
| WO2020185899A1 (en) * | 2019-03-14 | 2020-09-17 | Elekta, Inc. | Automated cancer registry record generation |
| CN110109897A (en) * | 2019-04-15 | 2019-08-09 | 深圳壹账通智能科技有限公司 | Database script generation method, device, computer equipment and storage medium |
| CN110457288A (en) * | 2019-07-04 | 2019-11-15 | 平安科技（深圳）有限公司 | Data model construction method, device, equipment and computer readable storage medium |
| CN111897818A (en) * | 2020-07-31 | 2020-11-06 | 平安普惠企业管理有限公司 | Data storage method and device, electronic equipment and storage medium |
| CN112685415A (en) * | 2020-12-30 | 2021-04-20 | 平安普惠企业管理有限公司 | Data import method and device, computer equipment and storage medium |
| CN113505128A (en) * | 2021-06-30 | 2021-10-15 | 平安科技（深圳）有限公司 | Method, device and equipment for creating data table and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 雷磊;王莉;舒雅;魏巍;刘珂炜;贺斌彦;: "利用Access2010数据库建立疼痛科患者信息管理系统", 中国疼痛医学杂志, no. 12 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116401303B (en) | 2023-11-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10824758B2 (en) | System and method for managing enterprise data | |
| CA2605278C (en) | System and method for using and maintaining a master matching index | |
| US11250951B2 (en) | Feature engineering method, apparatus, and system | |
| CN110246554B (en) | Method and computer for controlling operation of user equipment | |
| WO2019108131A1 (en) | Dashboard interface, platform, and environment for intelligent subscription product selection | |
| US10515060B2 (en) | Method and system for generating a master clinical database and uses thereof | |
| CN109684947A (en) | Mark quality control method, device, computer equipment and storage medium | |
| US11379452B2 (en) | Database tool | |
| US11250000B2 (en) | Database tool | |
| CN114186961A (en) | Business approval process configuration method and device, computer equipment and storage medium | |
| US20160232298A1 (en) | Method, Apparatus, And Computer Program Product For Facilitating Query Initiation And Query Response | |
| CN109472707B (en) | Medical intelligent nuclear protection method, device, computer equipment and storage medium | |
| CN116401303B (en) | Hospital multi-database data management method and related device for kidney disease treatment | |
| CN115687826A (en) | Page refreshing method and device, computer equipment and storage medium | |
| US20230126896A1 (en) | Method for providing basic data for diagnosis, and system therefor | |
| US12020825B2 (en) | Computer system and method for determining efficacy of a medical treatment for a medical condition | |
| CN112967809B (en) | Method, device, equipment and storage medium for determining follow-up user | |
| CN113537631B (en) | Forecasting methods, devices, electronic equipment and storage media for drug demand | |
| JP2006301760A (en) | Medical information providing apparatus and medical information providing method | |
| US12547769B2 (en) | Systems and methods for configuring and operating de-identification systems | |
| US20240028762A1 (en) | Systems and methods for configuring and operating de-identification systems | |
| US20230125634A1 (en) | Method for predicting developmental disease and system therefor | |
| US20230131979A1 (en) | Discomfort graph generating method and system | |
| CN117520819A (en) | Algorithm recommendation method, device, equipment and medium based on data waveform characteristics | |
| KR20250164354A (en) | Ai-based cancer survivor care plan system and method thereof |
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 |