CN114664398B - A medical database system - Google Patents

Abstract

The invention relates to the technical field of database systems, in particular to a medical database system, which comprises: the public database is used for storing personal information of patients; the operation end is connected with the public database, and a plurality of pre-generated script programs are pre-stored in the operation end; the operation end responds to an external access instruction, and calls the script program corresponding to the access instruction according to the access instruction to operate the personal information in the public database. The invention has the beneficial effects that: by adding the script program for operating the data in the operation end, the integrated process of data operation is realized, the problem of low efficiency in operating the database through the middleware in the prior art is avoided, higher operation efficiency is realized, and the pressure of the rear end is further reduced.

Description

A medical database system

Technical Field

The present invention relates to the technical field of database systems, and in particular to a medical database system.

Background Art

Database refers to a computer program that organizes, stores and manages data according to data structure. It is a collection of large amounts of data that is stored in a computer for a long time, organized, shareable and uniformly managed. Digital medicine refers to a modern medical method based on computer technology and information technology applied to the medical process. In order to achieve better digital medical results, it is necessary to integrate, analyze and process the large amount of data generated in the digital medical process to meet the needs of doctors for diagnosis and treatment.

In the prior art, there are related technologies that apply database technology to medical systems. For example, a medical database system based on NOSQL is usually deployed in the hospital system and combined with medical information to establish relationship mapping between medical information, design table structure and query tools for master and sub-tables. Finally, a personal archive database for patients is established, so as to collect data generated during the diagnosis and treatment process and provide data support for digital medicine.

However, in the actual implementation process, the inventors found that the database system implemented based on the existing technology needs to rely on middleware to operate the database in order to reduce the consumption of hardware resources due to the large number of tables and large amount of data in the medical scenario. This leads to low management efficiency of the database system as a whole during the processing process and a cumbersome operation process.

Summary of the invention

In view of the above problems existing in the prior art, a medical database system is now provided.

The specific technical solutions are as follows:

A medical database system, comprising:

A public database storing personal information of patients;

An operation terminal, the operation terminal is connected to the public database, and a plurality of pre-generated script programs are pre-stored in the operation terminal;

The operating end responds to an external access instruction and calls the script program corresponding to the access instruction according to the access instruction to operate the personal information in the public database.

Preferably, the medical database system further includes:

A plurality of partition databases, each of which is connected to the public database;

Different diagnostic data corresponding to the patients are respectively stored in the partition databases;

The script program obtains the diagnostic data from the partition database according to the personal information.

Preferably, the operation terminal includes a script generation module;

The script generation module obtains the fields in the partition database, and generates the corresponding script program according to the fields and the access instructions.

Preferably, the public database includes:

An information storage module storing the patient's personal information

A patient search module is connected to the information storage module. The patient search module responds to the access instruction, obtains the personal information from the information storage module, and returns the personal information to the operation end.

Preferably, the public database further includes:

An information push module, the information push module is connected to the patient search module and the partition database, and the information push module pushes the personal information to the partition database;

The partition database includes:

A data storage module, wherein the diagnostic data is stored in the data storage module;

A data reading module, wherein the data reading module is connected to the information pushing module, and the data reading module obtains the diagnostic data according to the personal information.

Preferably, the public database further includes:

A view generation module, wherein the view generation module generates a public information view according to the personal information;

The partition database includes:

a positioning module, the positioning module receiving the public information view sent from the public database;

The positioning module returns the diagnostic data corresponding to the personal information to the public database according to the public information view.

Preferably, the partition database further includes:

A data description module, the data description module is connected to the data storage module;

The data description module acquires the diagnostic data in the data storage module, and the data description module generates a partition view corresponding to the partition database according to the diagnostic data;

Then the public database also includes:

A view acquisition module, wherein the view acquisition module is connected to a data description module of the partition database;

The view acquisition module acquires the partition view and returns the partition view to the operation end.

Preferably, the medical database system further comprises a database construction end;

The database construction end is connected to an in-hospital system, and the in-hospital system is provided with a plurality of department collection ends, and the department collection ends are used to collect the diagnostic data corresponding to the patient;

The database construction end responds to an external construction instruction to obtain the diagnostic data;

The database construction end generates the partition database according to the type of the diagnostic data.

The above technical solution has the following advantages or beneficial effects: by adding a script program to operate data in the operation end, an integrated process of data operation is realized, avoiding the low efficiency problem of operating the database through middleware in the prior art, achieving higher operating efficiency, and thus reducing the pressure on the back end.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments of the present invention will be described more fully with reference to the attached drawings, which are provided for illustration and description only and are not intended to limit the scope of the present invention.

FIG1 is an overall schematic diagram of an embodiment of the present invention;

FIG2 is a schematic diagram of the interaction between the public database 2 and the partition database 3A in an embodiment of the present invention;

FIG3 is a schematic diagram of the interaction between the public database 2 and the partition database 3A in another embodiment of the present invention;

FIG. 4 is a schematic diagram of a database construction end in an embodiment of the present invention.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other.

The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments, but they are not intended to limit the present invention.

The present invention comprises:

A medical database system, comprising:

Public database 2, in which the patient's personal information is stored;

An operation terminal 1, the operation terminal is connected to a public database 2, and a plurality of pre-generated script programs are pre-stored in the operation terminal 1;

The operating terminal 1 responds to an external access instruction and calls a script program corresponding to the access instruction to operate the personal information in the public database 2 according to the access instruction.

Specifically, in order to solve the problem of low efficiency in operating the database by relying on middleware in the prior art, this embodiment implements a simpler process of operating the database by pre-writing and storing a script program for operating the database in the operation terminal.

In the implementation process, the public database is an independent database or database partition implemented based on the existing technology, which is used to store the patient's personal information, including name, number, gender, age, etc. The operation terminal 1 is embodied as the front-end part of the database system, which receives access instructions from external input through a visual interface or a command line interface. The access instruction is a SQL-like statement, such as insert, drop, update, which calls the relevant script program to perform operations such as adding, deleting, modifying, and checking the back-end database, avoiding the tediousness of operating the database through the middleware.

In a preferred embodiment, the medical database system further includes:

A plurality of partition databases 3A, 3B, 3C, wherein the partition databases 3A, 3B, 3C are respectively connected to a public database;

Different diagnostic data corresponding to the patients are stored in the partition databases 3A, 3B, and 3C respectively;

The script program obtains diagnostic data from the partitioned databases 3A, 3B, 3C based on the personal information.

Specifically, in view of the problem that the database system in the prior art cannot cope well with large amounts of data, in this embodiment, multiple partitioned databases 3A, 3B, and 3C are set up to respectively store different diagnostic data, thereby improving the reading and writing efficiency of large amounts of data in the medical database system.

During the implementation process, the partition databases 3A, 3B, and 3C are partitions in multiple databases or an independent database, which store different diagnostic data according to preset storage rules. For example, in one embodiment, the partition database includes: an MRI database, a CT database, and an ultrasound database, which are used to store different types of image data respectively, so as to achieve optimized storage of different types of data, thereby improving the read and write efficiency of each partition database. Or, in another embodiment, the partition database is set according to the department, such as an orthopedic medical database, a circulatory medical database, an upper respiratory medical database, etc., to achieve centralized storage of relevant inspection and diagnostic data generated during the treatment process according to the different diagnosis and treatment needs of the patient, so that the script program uses personal information to access the data generated by a certain visit. The script program is a script program pre-generated in the operating terminal 1, which has relevant instructions according to the different settings of the partition databases 3A, 3B, and 3C, such as using personal information to obtain data in a specific field or data range in a database to implement the database operation process.

In a preferred embodiment, the operating terminal 1 includes a script generating module 11;

The script generation module 11 obtains the fields in the partition database and generates corresponding script programs according to the fields and access instructions.

Specifically, in order to solve the problem that the database system in the prior art is operated through middleware, the process is relatively cumbersome and the instructions are lengthy, in this embodiment, a script generation module 11 is set to generate a corresponding script program according to the fields in the partitioned database and the access instructions required to access the fields, so that the user can achieve simple access to the database system through the corresponding script program, thereby simplifying the operation process.

During the implementation process, the operation terminal 1 is implemented using VUE, so that the script program can directly operate the public database 2 and the partition databases 3A, 3B, and 3C. The script program is implemented based on PostgREST, so that the operation terminal 1 can process the underlying code of the database through sql-like scripts to achieve the operations of adding, deleting, modifying, and checking.

In a preferred embodiment, as shown in FIG2 , the public database 2 includes:

Information storage module 21, which stores the patient's personal information

The patient search module 22 is connected to the information storage module 21 . The patient search module 22 responds to the access instruction, obtains the personal information from the information storage module 21 , and returns the personal information to the operation terminal 1 .

Specifically, in order to solve the problem of low efficiency in processing large amounts of data in the medical database in the prior art, in this embodiment, the information storage module 21 and the patient retrieval module 22 are set up to obtain personal information and return it to the operation end, thereby achieving higher processing efficiency.

In a preferred embodiment, as shown in FIG2 , the public database 2 further includes:

An information push module 23, the information push module 23 is connected to the patient search module 22 and the partition database 3A, and the information push module 23 pushes personal information to the partition database;

The partition database 3A includes:

A data storage module 31, wherein the data storage module 31 stores diagnostic data;

The data reading module 32 is connected to the information pushing module 23 , and the data reading module obtains the diagnostic data according to the personal information.

Specifically, in order to address the problem of low cross-database query efficiency in the prior art, this embodiment achieves the capture of diagnostic data based on personal information by setting an information push module 23 in the public database 2 and a data reading module 32 in the partitioned database 3A, thereby improving the query efficiency.

In a preferred embodiment, the public database 2 also includes:

A view generation module 24, the view generation module 24 generates a public information view according to the personal information;

The partition database 3A includes:

A positioning module 33, the positioning module 33 receives the public information view sent from the public database 2;

The positioning module 33 returns the diagnostic data corresponding to the personal information to the public database 2 according to the public information view.

Specifically, in order to address the problem of low efficiency of cross-database queries in the prior art, in this embodiment, a public information view is generated through the public database 2 and pushed to the partitioned database 3A, so that the partitioned database 3A can locate specific patients and their diagnostic data based on the key fields in the public information view.

In the implementation process, after the partition databases 3A, 3B, and 3C are constructed, SQL is used to establish tables and indexes in the partition databases 3A, 3B, and 3C, thereby generating a public information view. The public information view is a virtual table generated based on personal information, which includes query statements that map personal information and diagnostic data corresponding to the personal information to the virtual table, and is used to locate relevant diagnostic data in the partition databases 3A, 3B, and 3C.

In a preferred embodiment, as shown in FIG3 , the partition database 3A further includes:

A data description module 34, the data description module 34 is connected to the data storage module 31;

The data description module 34 obtains the diagnostic data in the data storage module, and the data description module 34 generates a partition view corresponding to the partition database 3A according to the diagnostic data;

The public database 2 also includes:

A view acquisition module 25, the view acquisition module 25 is connected to a data description module 34 of the partition database 3A;

The view acquisition module 25 acquires the partition view and returns the partition view to the operation terminal 1 .

Specifically, in view of the problem in the prior art that cross-database queries in medical database systems sometimes require the opening of super administrator privileges and have low security, in this embodiment, a data description module 34 is set to generate a partitioned view corresponding to the diagnostic data in the partitioned database 3A, thereby realizing the description of the data in the database, thereby realizing the query process at a lower authority level, and improving the security of the database system.

In the implementation process, the partition view is a table index established based on the partition database 3A, which is used to locate the diagnostic data in the partition database 3A, so that the control terminal 1 can call, add, delete, modify and query the diagnostic data.

In a preferred embodiment, as shown in FIG4 , the medical database system further includes a database construction terminal 4;

The database construction terminal 4 is connected to an in-hospital system 5, and a plurality of department collection terminals 6A, 6B, and 6C are provided in the in-hospital system 5. The department collection terminals 6A, 6B, and 6C are used to collect the diagnosis data corresponding to the patient;

The database construction terminal 5 responds to an external construction instruction to obtain diagnostic data;

The database construction terminal 5 generates partition databases 3A, 3B, 3C according to the type of diagnostic data.

Specifically, in view of the problem of low efficiency of the medical database system in the prior art, in this embodiment, a database construction terminal 4 is set to model the diagnostic data that may be generated in the hospital system 5 to describe the diagnostic data generated by different department collection terminals 6A, 6B, and 6C. And according to the modeling results, partition databases 3A, 3B, and 3C are generated, thereby achieving a better classification effect on the diagnostic data and improving the management efficiency of the database system.

In the actual implementation process, the database construction end 4 is implemented using PowerDesigner, which generates relevant data modeling based on the data actually generated in the connected in-hospital system 5, and then describes the diagnostic data generated by the in-hospital system 5 during operation according to the established model to generate different partitioned databases 3A, 3B, and 3C to store the generated diagnostic data.

As an optional implementation, after the database construction end 4 generates the partition databases 3A, 3B, 3C, an index corresponding to the table in each partition database 3A, 3B, 3C can be further generated according to the difference in fields in the partition databases 3A, 3B, 3C, and the index is used to describe the fields in the partition databases 3A, 3B, 3C. The public database 2 can generate a corresponding public information view according to the index to locate specific fields in the partition databases 3A, 3B, 3C.

The beneficial effect of the present invention is that by adding a script program for operating data in the operation terminal, an integrated process of data operation is realized, avoiding the low efficiency problem of operating the database through middleware in the prior art, achieving higher operating efficiency, and thus reducing the pressure on the back end.

The above are only preferred embodiments of the present invention, and are not intended to limit the implementation methods and protection scope of the present invention. Those skilled in the art should be aware that all solutions obtained by equivalent substitutions and obvious changes made using the description and illustrations of the present invention should be included in the protection scope of the present invention.

Claims (3)

1. A medical database system, comprising:

the public database is used for storing personal information of patients;

The operation end is connected with the public database, and a plurality of pre-generated script programs are pre-stored in the operation end;

the operation end responds to an external access instruction and calls the script program corresponding to the access instruction to operate the personal information in the public database according to the access instruction;

The medical database system further comprises:

A plurality of partitioned databases, the partitioned databases being respectively connected to the common database;

The partition database stores therein different diagnostic data corresponding to the patient, respectively;

the script program obtains the diagnosis data from the partition database according to the personal information;

the public database comprises:

The personal information retrieval module of the patient is stored in the information storage module, the patient retrieval module is connected with the information storage module, the patient retrieval module responds to the access instruction, acquires the personal information from the information storage module, and returns the personal information to the operation end;

the public database further includes:

The information pushing module is connected with the patient retrieval module and the partition database and is used for pushing the personal information to the partition database;

the partitioned database includes:

the data storage module is used for storing the diagnosis data;

The data reading module is connected with the information pushing module and acquires the diagnosis data according to the personal information;

the public database further includes:

a view generation module which generates a public information view according to the personal information;

the partitioned database includes:

The positioning module is used for receiving the public information view sent from the public database; the positioning module returns the diagnosis data corresponding to the personal information to the public database according to the public information view;

the partitioned database further includes:

the data description module is connected with the data storage module;

the data description module acquires the diagnosis data in the data storage module, and generates a partition view corresponding to the partition database according to the diagnosis data;

the public database further comprises:

The view acquisition module is connected with the data description module of the partition database;

and the view acquisition module acquires the partition view and returns the partition view to the operation end.

2. The medical database system of claim 1, wherein the operator terminal comprises a script generation module;

and the script generation module acquires the fields in the partition database and generates the corresponding script program according to the fields and the access instruction.

3. The medical database system of claim 1, further comprising a database construction site;

the database construction end is connected with an intra-hospital system, a plurality of department acquisition ends are arranged in the intra-hospital system, and the department acquisition ends are used for acquiring the diagnosis data corresponding to the patient;

the database construction end responds to an external construction instruction to acquire the diagnosis data;

and the database construction end generates the partition database according to the type of the diagnosis data.